100% found this document useful (1 vote)
132 views

SWTCH Manual

Uploaded by

Kleng Kleng
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
132 views

SWTCH Manual

Uploaded by

Kleng Kleng
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 324

User’s Manual

V1.01

Management PoE Switch


SW1024
Copyright
The contents of this publication may not be reproduced in any part or as a whole, stored,

transcribed in an information retrieval system, translated into any language, or

transmitted in any form or by any means, mechanical, magnetic, electronic, optical,

photocopying, manual, or otherwise, without the prior written permission of 4IPNET,

INC.

Disclaimer
4IPNET, INC. does not assume any liability arising out the application or use of any

products, or software described herein. Neither does it convey any license under its

parent rights nor the parent rights of others. 4IPNET further reserves the right to make

changes in any products described herein without notice. The publication is subject to

change without notice.

Trademarks
4IPNET (4ipnet) is a registered trademark of 4IPNET, INC. Other trademarks mentioned

in this publication are used for identification purposes only and may be properties of

their respective owners.

2
FCC Caution

This Equipment has been tested and found to comply with the limits for a
Class-A digital device, pursuant to Part 15 of the FCC rules. These limits are
designed to provide reasonable protection against harmful interference in a
residential installation. This equipment generates, uses, and can radiate radio
frequency energy. It may cause harmful interference to radio
communications if the equipment is not installed and used in accordance with
the instructions. However, there is no guarantee that interference will not
occur in a particular installation. If this equipment does cause harmful
interference to radio or television reception, which can be determined by
turning the equipment off and on, the user is encouraged to try to correct the
interference by one or more of the following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and receiver.
- Connect the equipment into an outlet on a circuit different from that to
which the receiver is connected.
- Consult the dealer or an experienced radio/TV technician for help.

CE Mark Warning
This is a Class-A product. In a domestic environment this product may cause
radio interference in which case the user may be required to take adequate
measures.

3
Table of Contents
CHAPTER 1. PRODUCT OVERVIEW .......................................................................................................... 10

1.1 MAJOR MANAGEMENT FEATURES .............................................................................................................. 10


1.2 PRODUCT SPECIFICATION .......................................................................................................................... 12
1.3 PACKAGE CONTENTS ................................................................................................................................ 15

CHAPTER 2. HARDWARE......................................................................................................................... 16

CHAPTER 3. GETTING STARTED ............................................................................................................... 19

3.1 ACCESS VIA THE SERIAL CONSOLE INTERFACE ................................................................................................ 19


3.2 PREPARATION FOR WEB INTERFACE............................................................................................................. 21
3.3 PREPARATION FOR TELNET/SSH INTERFACE .................................................................................................. 23

CHAPTER 4. SYSTEM CONFIGURATION ................................................................................................... 25

4.1 NETWORK PLANNING .............................................................................................................................. 25


4.2 SYSTEM INFORMATION ............................................................................................................................. 26
4.2.1 System Name.............................................................................................................................. 26
4.2.2 IP Configuration...........................................................................................................................27
4.2.3 System Time ................................................................................................................................27

CHAPTER 5. VIRTUAL LAN ...................................................................................................................... 29

5.1 VLAN MEMBERSHIP ............................................................................................................................... 31


5.2 VLAN PORTS ......................................................................................................................................... 33

CHAPTER 6. POWER OVER ETHERNET ..................................................................................................... 41

CHAPTER 7. LOOP PROTECTION.............................................................................................................. 44

7.1 GENERAL LOOP PROTECTION SETTING ......................................................................................................... 44


7.2 SPANNING TREE PROTOCOL (STP) .............................................................................................................. 46

CHAPTER 8. IP MULTICASTING................................................................................................................ 49

8.1 IGMP SNOOPING ................................................................................................................................... 49


8.1.1 Basic Configuration .................................................................................................................... 49
8.1.2 IGMP Snooping VLAN Configuration .......................................................................................... 50
8.1.3 IGMP Snooping Port Group Filtering Configuration ................................................................... 51
8.2 MLD SNOOPING..................................................................................................................................... 52

CHAPTER 9. AGGREGATION .................................................................................................................... 53

9.1 STATIC AGGREGATION .............................................................................................................................. 53


9.2 DYNAMIC AGGREGATION .......................................................................................................................... 54

4
CHAPTER 10. UTILITIES FOR MAINTENANCE ........................................................................................... 56

10.1 ADMINISTRATOR ACCOUNTS.................................................................................................................... 56


10.2 CONFIGURATION BACKUP AND RESTORE .................................................................................................... 58
10.3 FIRMWARE UPGRADE............................................................................................................................. 58
10.4 SYSTEM RESTART AND RESET ................................................................................................................... 59

APPENDIX A. UI REFERENCE INDEX ........................................................................................................ 61

1. SYSTEM CONFIGURATION ............................................................................................................................ 61

1.1. SYSTEM INFORMATION ................................................................................................................. 61

1.2. IP CONFIGURATION ....................................................................................................................... 62

1.3. IPV6 CONFIGURATION ................................................................................................................... 63

1.4. NTP CONFIGURATION:................................................................................................................... 64

1.5. SYSTEM LOG CONFIGURATION: ..................................................................................................... 65

2. POWER REDUCTION................................................................................................................................... 67

2.1. EEE CONFIGURATION: ................................................................................................................... 67

3. PORT CONFIGURATION: .............................................................................................................................. 69


4. SECURITY CONFIGURATION:......................................................................................................................... 71

4.1. SECURITY / SWITCH ....................................................................................................................... 71

4.1.1. Security / Switch / Users Configuration ..................................................................................... 71


4.1.2. Security / Switch / Privilege Levels Configuration: .................................................................... 72
4.1.3. Security / Switch / Auth Method ............................................................................................... 74
4.1.4. Security /Switch / SSH Configuration ........................................................................................ 75
4.1.5. Security / Switch / HTTPS Configuration ................................................................................... 76
4.1.6. Security / Switch / Access Management Configuration............................................................. 77
4.1.7. Security / Switch / SNMP ........................................................................................................... 78
4.1.8. RMON Statistics Configuration .................................................................................................. 87

4.2. SECURITY /NETWORK .................................................................................................................... 93

4.2.1. Port Security Limit Control Configuration .................................................................................. 93


4.2.2. Security / Network / Network Access Server Configuration ...................................................... 96
4.2.3. Security / Network / Access Control List Configuration ........................................................... 102
4.4.2.4 Switch / Network / DHCP Configuration ................................................................................ 115
4.2.5. IP Source Guard Configuration ................................................................................................ 117
4.2.6. ARP Inspection ........................................................................................................................ 119

4.3. SECURITY / AAA AUTHENTICATION SERVER CONFIGURATION .................................................... 122

5
5. AGGREGATION CONFIGURATION ................................................................................................................. 125

5.1 STATIC AGGREGATION .................................................................................................................. 125

5.2 LACP - DYNAMIC AGGREGATION .................................................................................................. 126

6. LOOP PROTECTION .................................................................................................................................. 128


7. SPANNING TREE ...................................................................................................................................... 130

7.1. SPANNING TREE / BRIDGE SETTING ............................................................................................ 130

7.2 SPANNING TREE / MSTI MAPPING ............................................................................................... 132

7.3. SPANNING TREE / MSTI PRIORITIES............................................................................................. 134

7.4. SPANNING TREE / CIST PORTS ..................................................................................................... 135

7.5. SPANNING TREE MSTI PORTS ...................................................................................................... 137

8. MVR (MULTICAST VLAN REGISTRATION) ................................................................................................... 139


9. IPMC (IP MULTICAST)............................................................................................................................. 141

9.1. IGMP SNOOPING CONFIGURATION ............................................................................................. 141

9.1.1. Basic Configuration ................................................................................................................. 141


9.1.2. IGMP Snooping VLAN Configuration ....................................................................................... 143
9.1.3. IGMP Snooping / Port Group Filtering .................................................................................... 144

9.2. MLD SNOOPING CONFIGURATION .............................................................................................. 145

9.2.1. Basic Configuration ................................................................................................................. 145


9.2.2. MLD Snooping VLAN Configuration ........................................................................................ 146
9.2.3. IPMC / MLD Snooping / Port Group Filtering .......................................................................... 148
10. LLDP PARAMETERS ............................................................................................................................... 149
10.1. LLDP Configuration ................................................................................................................... 149
10.2. LLDP Media Configuration ........................................................................................................ 151
11. POE CONFIGURATION ............................................................................................................................ 158
12. MAC ADDRESS TABLE CONFIGURATION..................................................................................................... 160
13. VLAN (VIRTUAL LAN)........................................................................................................................... 163
13.1. VLAN Membership Configuration............................................................................................. 163
13.2. VLAN Port Configuration .......................................................................................................... 164
14. PRIVATE VLANS ................................................................................................................................... 167
14.1. Private VLAN Membership Configuration ................................................................................ 167
14.2. Port Isolation Configuration ..................................................................................................... 168
15. VCL ................................................................................................................................................... 170
15.1. VCL / MAC-Based VLAN Configuration ..................................................................................... 170
15.2. VCL / Protocol-based VLAN ...................................................................................................... 171

6
15.3. VCL / IP Subnet-based VLAN ......................................................................................................174
16. VOICE VLAN CONFIGURATION .................................................................................................................176
16.1. Voice VLAN / Configuration .......................................................................................................176
16.2. Voice VLAN / OUI Configuration ............................................................................................... 177
17. QOS ................................................................................................................................................... 179
17.1. QoS / Ingress Port Classification ............................................................................................... 179
17.2. QoS / Ingress Port Policer Config .............................................................................................. 180
17.3. QoS / Port Scheduler ................................................................................................................ 181
17.4. QoS / Egress Port Shapers ........................................................................................................ 182
17.5. QoS / Port Tag Remarking ........................................................................................................ 183
17.6. QoS / Port DSCP Configuration ................................................................................................. 184
17.7. QoS / DSCP based QoS Ingress Classification ........................................................................... 185
17.8. QoS / DSCP Translation ............................................................................................................ 187
17.9. QoS / DSCP Classification ......................................................................................................... 188
17.10. QoS / Control List Configuration ............................................................................................. 190
17.11. QoS / Storm Control Configuration ........................................................................................ 193
18. MIRRORING CONFIGURATION .................................................................................................................. 195
19. UPNP CONFIGURATION.......................................................................................................................... 196
20. SFLOW CONFIGURATION ......................................................................................................................... 198
21. MONITOR ............................................................................................................................................ 199
21.1. Monitor / System ...................................................................................................................... 199
21.1.1. Monitor / System / Information ............................................................................................ 199
21.1.2. CPU Load ............................................................................................................................... 200
21.1.3. System Log Information ........................................................................................................ 200
21.1.4. System / Detailed Log ............................................................................................................ 202
21.2 Monitor / Port State .................................................................................................................. 202
21.2.1. Port State............................................................................................................................... 202
21.2.2. Traffic Overview .................................................................................................................... 203
21.2.3. QoS Statistics ......................................................................................................................... 204
21.2.4. QCL Status ............................................................................................................................. 205
21.2.5. Detailed Port Statistics .......................................................................................................... 207
21.3. Monitor / Security .................................................................................................................... 209
21.3.1. Security / Access Management Statistics .............................................................................. 209
21.3.2. Security / Network ................................................................................................................ 210
21.3.3. Security / AAA ....................................................................................................................... 230
21.3.4. Switch / SNMP / RMON ......................................................................................................... 236
21.4. LACP System Status .................................................................................................................. 243
21.4.1. System Status ........................................................................................................................ 243

7
21.4.2. LACP Port Status .................................................................................................................... 243
21.4.3. LACP statistics ....................................................................................................................... 245
21.5. Loop Protection ........................................................................................................................ 245
21.6. STP Bridge Status ..................................................................................................................... 246
21.6.1. Bridge Status ......................................................................................................................... 247
21.6.2. STP Port Status ...................................................................................................................... 248
21.6.3. STP Port Statistics .................................................................................................................. 248
21.7. MVR Status ............................................................................................................................... 250
21.7.1. Statistics ................................................................................................................................ 250
21.7.2. MVR Group Table .................................................................................................................. 251
21.8. Monitor / IPMC / IGMP Snooping ............................................................................................ 252
21.8.1. IGMP Snooping ...................................................................................................................... 252
21.8.2. MLD Snooping Status ............................................................................................................ 256
21.9. Monitor / LLDP ......................................................................................................................... 260
21.9.1 LLDP / Neighbour ................................................................................................................... 260
21.9.2. LLDP MED Neighbours........................................................................................................... 262
21.9.3. LLDP PoE ................................................................................................................................ 266
21.9.4. LLDP EEE ................................................................................................................................ 267
21.9.5. LLDP Statistics ....................................................................................................................... 269
21.10. Power Over Ethernet Status ................................................................................................... 271
21.11. Dynamic MAC Table ................................................................................................................272
21.12. VLAN Membership Status .......................................................................................................274
21.13. VCL MAC-Based VLAN Status ..................................................................................................278
21.14. sFlow ...................................................................................................................................... 279
22. Diagnostic.................................................................................................................................... 280
22.1. Ping .......................................................................................................................................... 280
22.2. Ping6 ........................................................................................................................................ 280
22.3. VeriPHY Cable Diagnostic ......................................................................................................... 281
23. Maintenance ............................................................................................................................... 283
23.1. Restart Device ........................................................................................................................... 283
23.2. Factory Defaults ....................................................................................................................... 283
23.3. Software Upload....................................................................................................................... 284
23.3.1. Firmware Update .................................................................................................................. 284
23.3.2. Image Select .......................................................................................................................... 285
23.4. Configuration ........................................................................................................................... 286

APPENDIX B. FEATURE CONFIGURATION - CLI .................................................................................... 288

1. SYSTEM CONFIGURATION .......................................................................................................................... 288


2. POWER REDUCTION................................................................................................................................. 292

8
3. PORT CONFIGURATION ............................................................................................................................. 293
4. SECURITY CONFIGURATION........................................................................................................................ 295
5. AGGREGATION CONFIGURATION ................................................................................................................. 306
6. LOOP PROTECTION .................................................................................................................................. 306
7. SPANNING TREE ...................................................................................................................................... 307
8. MVR.................................................................................................................................................... 309
9. IPMC ................................................................................................................................................... 310
10. LLDP CONFIGURATION .......................................................................................................................... 311
11. POWER OVER ETHERNET CONFIGURATION.................................................................................................. 312
12. MAC ADDRESS TABLE CONFIGURATION..................................................................................................... 313
13. VLAN CONFIGURATION ......................................................................................................................... 314
14. PRIVATE VLAN CONFIGURATION .............................................................................................................. 315
15. VCL CONFIGURATION ............................................................................................................................ 315
16. VOICE VLAN CONFIGURATION ................................................................................................................ 316
17. QOS CONFIGURATION ............................................................................................................................ 317
18. MIRRORING CONFIGURATION .................................................................................................................. 320
19. UPNP CONFIGURATION.......................................................................................................................... 320
20. SFLOW CONFIGURATION ......................................................................................................................... 321
21. DIAGNOSTIC COMMANDS ....................................................................................................................... 322
22. MAINTENANCE COMMANDS ................................................................................................................... 323

9
Chapter 1. Product Overview
The 4ipnet SW1024 is a 26-Port Layer 2 Full Management Gigabit PoE Switch, equipped with
24-port 10/100/1000M RJ-45 plus 2 Gigabit SFP Open Slot. The Ethernet Ports support
standard IEEE 802.3at PoE, capable of supplying up to 500W with each port supporting up to
30W. The SFP open slots support various SFP transceivers types, perfect for extending
transmission distance up to a hundred kilometers. The 4ipnet SW1024 is capable of providing
non-blocking wired-speeds of up to 52Gbps switch fabric. Standard packaging comes with
rack-mount brackets, making the standard 19" fit easily into your rack.

The 4ipnet SW1024 comes packed with powerful Layer 2 software supporting Web
Management, SNMP, IPv4/v6, IEEE 802.1Q VLAN, Private VLAN, Protocol VLAN, Voice VLAN,
up to 4 priority queue QoS, up to 13 Link Aggregation groups, Multiple Spanning Tree Protocol,
IGMPv4/v6 IP Multicast Forwarding and Filtering, MVR, Bandwidth control, Loop Protection,
LLDP, PoE Configuration and abundant security features such as IEEE 802.1X, AAA, IP
Source Guard, Port Security and Access Management. With these advanced L2 management
features, the switch works in perfect complement with the 4ipnet Gateway and is ideal for
medium or large network environments.

1.1 Major Management Features


24 10/100/1000Base RJ-45 plus 2 1000Base SFP
24 10/100/1000Base RJ-45 are all built with PoE functionality
Up to 52Gbps switching capacity, 8K MAC Address Table
Up to 500W PoE Power, each port supports up to 30W per IEEE 802.3af/at
Per-Port Power Management Feature supports Enable/Disable, Priority Setting,
Overloading Protection and Power Level settings
IEEE 802.1D STP and IEEE 802.1w RSTP
IEEE 802.1Q VLAN, up to 4K VLAN Group
Port Based VLAN, MAC Based VLAN, Protocol Based VLAN, MVRP and QinQ
IEEE 802.2ad LACP, Static Trunk support up to 13 trunks, up to 16 ports per trunk
IGMP Snooping V1/V2/V3 and Querier port
Up to 9K Jumbo Frame
Rate Control and Strom Control for Broadcast/Multicast/Un-known Unicast
QoS supports up to 8 priority queues per port, 802.1p/IP Precedence, IP ToS, IP DSCP,
DiffServ, the queue scheduling supports WRR, Strict Priority and Hybrid
Advanced Security supports IEEE 802.1x, RADIUS, TACAS+, IP/MAC Filter

10
Support Command Line, Web Management, SNMP V1/V2c/V3, RMON, Secured
Management supports HTTPS, SSL and SSHv2
sFlow, NTP, LLDP, Port Mirroring, Cable Diagnostic, UPnP...
IPv6 Features

11
1.2 Product Specification
Hardware Specification
Total Port 26
10/100/1000 Mbps 24
Gigabit SFP 2
Interface Auto negotiation and Auto-MDIX Yes
Backpressure for half duplex,
Flow Control 802.3x for full duplex
Console (RJ-45) Yes
System (State / Color) Y
LED Port (State: Link/Act / Color) Y
PoE (State: On / Color) Y
CPU 416MHz
Flash 16MB
SDRAM 128MB
Packet Buffer 4MB
System Switching Capacity 52Gbps non-blocking
Forwarding Architecture Store and forward

Package Forwarding Rate 38.7Mpps (@ 64bytes)


MAC Address Table 8K
Jumbo Frame 9K
Port Volume 24
PoE Capability 30W (802.3at)
PSE Ports
Total PSE Power 500W (Current Share)
Power through RJ-45 pin Pair1,2 / 3,6
AC Input 100-240V AC, 50/60Hz
Power Requirement
Consumption - not include PSE 25W
/ Consumption
Consumption - include PSE 500W (Current Share)
Operating Temperature/ Degree C 0~40

Relative Humidity (operating) 5~90% (non-condensing)


Environment
Storage Temperature / Degree C -20~80
Relative Humidity (storage) 5~90% (non-condensing)
Dimension (H*W*D) 45mm x 220mm x 40mm
Mechanical
Weight 3.0kg
Regular Compliance CE, FCC Part 15 Class A Yes

12
Software Specification
IEEE 802.3 - 10Base-T
IEEE 802.3u - 100Base-TX
IEEE 802.3ab - 1000Base-T
IEEE 802.3z - 1000Base-SX/LX
IEEE 802.3x - Flow Control
IEEE 802.1Q - VLAN
IEEE 802.1p - Class of Service
IEEE 802.1D - Spanning Tree
Standard
IEEE 802.1w - Rapid Spanning Tree
IEEE 802.1s - Multiple Spanning Tree
IEEE 802.3ad - Link Aggregation Control Protocol (LACP)
IEEE802.1v - Protocol VLAN
IEEE 802.1AB - LLDP (Link Layer Discovery Protocol)
IEEE 802.1X - Access Control
IEEE 802.3at - Power over Ethernet
IEEE 802.3af - Power over Ethernet
Link Status, Speed/Duplex (automatic negotiation/ flow control)
Port Configuration
Rate control/ limit
Port-based and 802.1Q tag-based VLAN
Maximum 4K VLAN Groups, 4096 VLANs
VLAN 802.1Q-in-Q
Private/ MAC-Based/ IP-Subnet/ Voice/ 802.1v Protocol VLAN
Multicast VLAN Registration (MVR)
4 physical priority queues
Scheduling - WRR, Strict, WRR+SP
QoS
Class of Service: Port based, 802.1p, DSCP, TCP/UDP Port-based
Storm control over broadcast, multicast, and/or unicast traffic
Max: 13 groups (LAG); up to 16 ports/ group
Hashing Algorithms: destination and/or source address, MAC-based, SIP
Link Aggregation
Static trunk
Static and 802.3ad LACP
Loop Protection Shutdown of ports when network loops are detected
IEEE 802.1D - Legacy Spanning Tree
IEEE 802.1w - Rapid Spanning Tree
Spanning tree
IEEE 802.1s - Multiple Spanning Tree
BPDU guard and filtering support

13
IGMP Snooping v1/v2/v3, MLD (IPv6) Snooping v1/v2
Multicast Up to 8K Multicast Groups
IGMP/MLD Querier, Router Port, Proxy, Immediate Leave messages
Port Mirroring (1 to 1, 1 to N, N to 1)
Traffic Mirroring
sFlow
Dynamic MAC address management
MAC Address Table
Static MAC address support
Port Security (MAC-Port, P-MAC-Port Binding)
802.1x authentication (MAC-based, port-based)
Username/password permission control
User accounts with 15 permission levels
Management IP address listing
IP Source Guard
Security
RADIUS/TACACS+ Authentication
Guest VLAN
DoS protection
SSHv1/SSHv2
SSLv2/SSLv3/TLSv1
Access Control List (L2/L3/L4)
Browser-based / Command line interface management (Console/Telnet/SSH)
DHCP Client, Snooping, Relay/Option 82, BOOTP
SNMP V1/V2c/V3, Trap, RMON
Firmware upgrades by TFTP/HTTP
Management
Configuration backup and restoration
IPv4/ IPv6 Link Layer Discovery Protocol (LLDP)
Event logging
NTP

VeriPHY Diagnostics
Maintenance IPv4/ v6 Ping
CPU Monitoring
Per-port power supply monitoring with constraints
PoE Specification Per-port supply priority setting
Power device (PD) monitoring

14
1.3 Package Contents
- SW1024 x 1
- Power Cord x 1
- Quick Installation Guide (QIG) x 1
- User Manual (CD) x 1
- Rack-Mount kit x 1
- Console Cable x 1

15
Chapter 2. Hardware

This section describes the hardware of the L2 Management Network Switch SW1024 and
gives a physical and functional overview of the switch.

Front Panel
The front panel of the L2 management switch SW1024 consists of 24 10/100/1000 Base-TX
RJ-45 ports and 2 gigabit uplink SFP ports. The LED Indicators are also located on the front
panel.

LED Display RJ-45 Port SFP Console

LED Indicators
The LED Indicators present real-time information of systematic operation status. The
following table provides description of LED status and their meaning.

LED Color Description


Power Green On when system is operating normally
Link/ Act. Green On when link is on; blinks when system is transmitting/ receiving data

PoE Green Indicates that power supply is present

16
SFP Green On when link is on; blinks when system is transmitting/ receiving data

LED Color / Status Description No. of LEDs

Power Amber On Power on Power

Green On Link Up
10/100/1000M 24(1~24)
Green Blinking Data Activating
PoE Amber On PD is connected 24 (1~24)
Green On linked to Power Device 25~26
SFP
Green Blinking Data Activating 25~26

Rear Panel
The 3-pronged power plug is placed at the rear panel on the switch’s right as shown below.

Hardware Installation

The switch is usually mounted on a 19” rack installed in the IT room or in a secured place.
The 4ipnet SW1024 supports AC power input, PoE delivery and rack mount mounting. Make
sure all the power cables, Ethernet cables, screws and heat dissipation are well prepared
and installed as described below.

AC Power Input
Attach the power cord to the AC power input connector, the available AC power input ranges
from 100-264VAC.
There are 2 power modules in the switch, each of them supports up to 250W. With the
current sharing technology, the 2 modules can deliver power up to 500W.

Ethernet cable Request


The wiring cable types are as below.
10 Base-T: 2-pair UTP/STP Cat. 3, 4, 5 cable, EIA/TIA-568 100-ohm (Max. 100m)
100 Base-TX: 2-pair UTP/STP Cat. 5 cable, EIA/TIA-568 100-ohm (Max. 100m)
1000 Base-T: 4-pair UTP/STP Cat. 5 cable, EIA/TIA-568 100-ohm (Max. 100m)

PoE: For optimized performance, the Cat 5e and Cat 6 cable is suggested. Higher quality

17
Ethernet cable reduces loss during power transmission.

SFP Installation

While installing the SFP transceiver, make sure the SFP type of the 2 ends are the same and
the transmission distance, wavelength, fiber cable can meet your requirements. It is
suggested that SFP transceivers be purchased with the switch provider to avoid any
incompatibility.
Plug in the SFP fiber transceiver first. The SFP transceiver has 2 plugs for the fiber cable;
one is for TX (transmit), and the other for RX (receive). Cross-connect the transmit channel
at each end to the receive channel at the opposite end.

Rack-mount Installation

Attach the brackets to the device by using the screws provided in the Rack Mount kit.
Mount the device in the 19‟ rack by using four rack-mounting screws provided by the rack
manufacturer.

18
Chapter 3. Getting Started
The 4ipnet SW1024 provides both in-band and out-band configuration methods.

Out-band Management: The switch can be configured via the RS232 console interface
when not connected to your network or when connection with the switch is lost.

In-Band Management: You can remotely manage the switch via a Web browser, such as
Microsoft Internet Explorer, or Mozilla Firefox and etc. to configure and monitor the switch
from anywhere on the network.

3.1 Access via the Serial Console Interface


Included in the package, there is a RS-232 console cable. Please attach one end of the
console cable to your PC COM port, the other end to the console port of the switch.
1. Go to Start -> Program -> Accessories -> Communication -> Hyper Terminal
2. Give a name to the new console connection.
3. Choose the COM name
4. Select the correct serial settings. The serial settings of the switch are as below:
Baud Rate: 115200 / Parity: None / Data Bit: 8 / Stop Bit: 1
5. When connected, a Login prompt will appear
6. Login to the switch. The default username is “admin”, password, “admin”.

Figure 3-1 Hyper Terminal Console Screen

19
NOTE
1. Microsoft Win 7 or later OS versions do not provide Console Terminal tools. Please
download the tool, Hyper Terminal from Microsoft web site or other terminal tools, such as
PuTTY for console connection.

Figure 3-2 Putty Configuration

Figure 3-3 Putty Login Screen

20
3.2 Preparation for Web Interface
The web management interface allows you to use a standard web-browser such as
Microsoft Internet Explorer, Google Chrome or Mozilla Firefox, to configure and monitor the
switch from anywhere on the network.

Before you attempt to use the web user interface to manage switch operation, verify that
your switch is properly installed on your network and that every PC on this network can
access the switch via the web browser.

1. Verify that your network interface card (NIC) is operational, and that your operating
system supports TCP/IP protocol.

2. Power on the switch and connect your computer to the switch.

3. The default IP address for the switch is 192.168.2.1. The Switch and the connected PC
should be within the same IP Subnet.

4. Change your computer's IP address to 192.168.2.XX or another IP address on the


192.168.2.x (For example: IP Address: 192.168.2.30; Subnet Mask: 255.255.255.0)
subnet.

Launch the web browser and Login.

21
5. Launch the web browser (Internet Explorer or Mozilla Firefox) on the PC.
6. Type http://192.168.2.1 (or the IP address of the switch). And then press Enter.
7. The login screen will appear.
8. Enter the username and password. The default user name and password are both admin.

If you cannot login to the switch, the following steps can help you to identify the problem.
1. Switch to DOS command mode and type the "ipconfig" to check the NIC's setting. Type the
"ping 192.168.2.1" to verify a normal response time.
2. Check the security & firewall settings of your computer.
3. Try different Web-browser, such as Mozilla Firefox.

22
3.3 Preparation for Telnet/SSH Interface
If you are operating Win XP, Win 2000 or earlier, you may access the Telnet console by the
default command. If your OS version is Window 7 or later, please download the terminal tool,
such as HyperTeminal or Putty.

The switch supports both Telnet and SSH console. The SSH console can be treated as a
secured Telnet connection.

Telnet Connection

1. Go to Start -> Run -> cmd. And then press Enter


2. Type the Telnet 192.168.2.1 (or the IP address of the switch). And then press Enter.

Access Telnet or SSH by Terminal tool, Putty.

1. Open Telnet/SSH Client/PuTTY

In the Session tab, choose Telnet/SSH in the Protocol field.

In the Session tab, enter the Host Name (IP Address of your switch) and Port number
(default Telnet =23, SSH = 22).

Then click on “Open” to start the SSH session console.

2. After click on Open, then you can see the cipher information in the popup screen. Press Yes
to accept the Security Alert.

23
If you choose Telnet connection, there is no such cipher information and window. It goes to
next step directly.

3. After the Telnet/SSH connection is established, login with the same credentials admin/admin.
The command line of Telnet, SSH and console are operated the same way.

24
Chapter 4. System Configuration
The 4ipnet SW1024 provides abundant software features. Once logged in to the switch, you may
start configuring the settings or monitoring the status.

The following provides detailed instructions on configuring the SW1024.

4.1 Network Planning


Before installing the 4ipnet SW1024 Switch, careful network planning is required in order to meet
the networking needs with the most efficient utilization of network resources. IT staff of any
organization should assess the available network resources at hand, and design a suitable
network topology with resiliency, capacity, and survivability in mind.

The following are simple graphical illustrations of how the SW1024 can be deployed with the
4ipnet WHG Controllers.

【Graphical Illustration of Layer 2 Topology】

25
【Graphical Illustration of Layer 3 Topology】

4.2 System Information


4.2.1 System Name
It is important to determine a mnemonic System Name and also enter System Location for your system. This

comes in handy for easy future references.

Configuration path: Configuration >> System >> Information

26
4.2.2 IP Configuration
The SW1024 switch requires an IP address for management, and there are a couple options to determine its

IP address.

Configuration path: Configuration >> System >> IP

1) The SW1024 can obtain IP from an upstream DHCP server. Click the ‘Renew’ button to get an IP

address automatically.

2) The administrator can manually specify a static IP address, IP Mask (Subnet Mask), IP Router (Default

Gateway), and DNS Server for the system

The “Current” column shows the present configurations, and the factory default values are shown in the
above figure.

Check the ‘DNS Proxy’ button if you wish to enable the SW1024’s function as a proxy for the configured DNS
Server.

4.2.3 System Time


The SW1024 supports both manual system time configuration option and automatic time synchronization by

specifying external NTP servers.

Configuration path: Configuration >> System >> NTP

27
Up to 5 NTP Servers (IP Address) can be saved on the system.

Configuration path: Configuration >> System >> Time

Select the appropriate time zone for your region from the drop-down list. Recurring or Non-recurring Daylight

Saving can also be enabled for the system.

28
Chapter 5. Virtual LAN

In general network application, traffic that stations generate is transmitted to all other stations in a
logical Ethernet segment on Layer 2 Switch. With VLAN network topology, it could help Layer2
Switch provide better administration, security, and management of multicast traffic within such
segmentation.
When VLANs are used, there is no physical barrier between different locations. Furthermore,
users can be grouped by logical function instead of physical location, and all ports that
communicate with each other are assigned with the same VLAN. That is how VLAN technology to
create multiple distinct broadcast domains, which are mutually isolated.
4ipnet SW1024 Managed Switch, following IEEE 802.1Q and IEEE 802.1ad QinQ standard, can
create port-based or tag-based virtual local area networks for different application.

IEEE 802.1Q

IEEE 802.1Q is the networking standard that supports VLANs on an Ethernet network. The
standard defines a system of VLAN tagging for Ethernet frames which is defined as a 32-bit
field between MAC address and EthernetType/ Size field of the untagged one as the following
figures.

The 802.1Q header in tagged Ethernet frame is composed of several sectors as identifiers.

 Tag protocol identifier (TPID): a 16-bit field set to a value of 0x8100 in order to identify
the frame as an IEEE 802.1Q-tagged frame. This field is located at the same position as
the EtherType/length field in untagged frames, and is thus used to distinguish the frame
from untagged frames.
 Priority code point (PCP): a 3-bit field which refers to the classification and maps to the
frame priority level.

29
 Drop eligible indicator (DEI): a 1-bit field. (formerly CFI) which is used separately or in
conjunction with PCP to indicate frames eligible to be dropped in the presence of
congestion.
 VLAN identifier (VID): a 12-bit field specifying the VLAN to which the frame belongs. All
other values may be used as VLAN identifiers, allowing up to 4,094 VLANs. (VID 0x000
and 0xFFF are reserved)

IEEE 802.1ad QinQ

The IEEE 802.1ad QinQ Support feature adds another layer of IEEE 802.1Q tag (called "metro
tag" or "PE-VLAN") to the 802.1Q tagged packets that enter the network. The purpose is to
expand the VLAN space by tagging the tagged packets, thus producing a "double-tagged" frame.
The expanded VLAN space allows the service provider to provide certain services, such as
Internet access on specific VLANs for specific customers, yet still allows the service provider to
provide other types of services for their other customers on other VLANs.

The 802.1ad QinQ VLAN tagged frame format is like below

30
 Tag protocol identifier (TPID): The QinQ frame contains the modified tag protocol identifier
(TPID) value of VLAN Tags. By default, the VLAN tag uses the TPID field to identify the
protocol type of the tag. The TPID value is 0x8100 IEEE 802.1Q, while 0x8a88 for IEEE
802.1 ad QinQ.

The device determines whether a received frame carries a service provider VLAN tag or a
customer VLAN tag by checking the corresponding TPID value. After receiving a frame, the device
compares the compares the configured TPID value with the value of the TPID field in the frame. If
the two match, the frame carries the corresponding VLAN tag. For example, if a frame carries
VLAN tags with the TPID values of 0x9100 and 0x8100, respectively, while the configured TPID
value of the service provider VLAN tag is 0x9100 and that of the VLAN tag for a customer network
is 0x8200, the device considers that the frame carries only the service provider VLAN tag but not
the customer VLAN tag.

In addition, the systems of different vendors might set the TPID of the outer VLAN tag of QinQ
frames to different values. For compatibility with these systems, you can modify the TPID value so
that the QinQ frames, when sent to the public network, carry the TPID value identical to the value
of a particular vendor to allow interoperability with the devices of that vendor. The TPID in an
Ethernet frame has the same position with the protocol type field in a frame without a VLAN tag. In
order to avoid problems in packet forwarding and handling in the network, you cannot set the TPID
value to any of the values in this table:

Protocol Type TPID Value


ARP 0x0806
PUP 0x0200
RARP 0x8035
IP 0x0800
IPv6 0x86DD
PPPoE 0x8863/0x8864
MPLS 0x8847/0x8848
IS-IS 0x8000
LACP 0x8809
802.1x 0x888E

5.1 VLAN Membership

The 4ipnet SW1024 supports up to 4000 VLANs and supports IEEE 802.1Q tagging available for
each port. Ports are grouped into broadcast domains by assigning them to the same VLAN ID.

31
Once the VLAN assigned, it establishes network segmentation, which is composed of one or
several physical ports.

Configuration path: Configuration >> VLANs >> VLAN Membership

Using the above illustration as an example, there are 6 VLANs configured on the SW1024.
Ports 1~9 and 15~26 are members of VLAN 1.
Ports 10~12 are members of VLAN 20 and VLAN 21.
Port 13 is a member of VLAN 20.
Port 14 is a member of VLAN 21.
Port 2 is a member of VLAN 1, VLAN 2000, VLAN 2001 and VLAN 2002.

Use the VLAN Membership Configuration page to enable VLANs for this switch by
assigning each port to the VLAN group(s) in which it will participate.

When adding a VLAN, enter the desired VLAN ID with corresponding VLAN Name and the port
members. Click “Save” button to save settings. Up to 4096 VLANs are supported on 4ipnet
SW1024.

Port overlapping can be used to allow access to commonly shared network resources

32
among different VLAN groups, such as file servers or printers. Note that if you
implement VLANs which do not overlap, but still need to communicate, you must
connect them through a router

5.2 VLAN Ports

With 4ipnet SW1024, administrators can use the VLAN Port Configuration page to
configure VLAN attributes for specific interfaces, including processing Queue-in-Queue
frames with embedded tags, enabling ingress filtering, setting the accepted frame
types, and configuring the default VLAN identifier (PVID).

Configuration path: Configuration >> VLANs >> Ports

 Port VLAN ID (PVID): PVID is a default VLAN ID that is assigned to a port to designate the
virtual LAN segment to which this port is connected. The PVID places the port into the set of
ports that are connected under the designated VLAN ID.
 Ethertype for Custom S-ports - When Port Type is set to S-customport, the
EtherType (also called the Tag Protocol Identifier or TPID) of all frames received on
the port is changed to the specified value. By default, the EtherType is set to 0x88a8
(IEEE 802.1ad). IEEE 802.1ad outlines the operation of Queue-in-Queue tagging
which allows a service provider to use a Virtual Bridged Local Area Network to

33
provide separate VLAN instances to multiple independent customers over the same
medium using double tagged frames. When Port Type is set to S-port or
S-custom-port, the port will change the EtherType of all frames received to indicate
that double-tagged frames are being forwarded across the switch. The switch will
pass these frames on to the VLAN indicated in the outer tag. It will not strip the
outer tag, nor change any components of the tag other than the EtherType field.

 Port Type – Configures how a port processes the VLAN ID in ingress frames. (Default:
Unaware)
 Unaware – All frames are classified to the Port VLAN ID and tags are not
removed.
 C-port – For customer ports, each frame is assigned to the VLAN indicated in
the VLAN tag, and the tag is removed.
 S-port – For service ports, the EtherType of all received frames is changed to
0x88a8 to indicate that double-tagged frames are being forwarded across the
switch. The switch will pass these frames on to the VLAN indicated in the outer
tag. It will not strip the outer tag, nor change any components of the tag other
than the EtherType field.
 S-custom-port – For custom service ports, the EtherType of all received frames
is changed to value set in the Ethertype for Custom S-ports field to indicate
that double-tagged frames are being forwarded across the switch. The switch
will pass these frames on to the VLAN indicated in the outer tag. It will not
strip the outer tag, nor change any components of the tag other than the
EtherType field.

Ingress action Egress action


Unaware  When the port receives an untagged frame, it The TPID of frame
obtains a tag (based on PVID) and is transmitted by Unaware
(Used in QinQ forwarded. port will be set to
double tag).  When the port receives a tagged frame, 0x8100.
1. if the tagged frame has TPID=0x8100, it
becomes a double-tag frame, and is
forwarded.
2. if the TPID of tagged frame is not 0x8100
(ex. 0x88A8), it will be discarded.
C-port  When the port receives an untagged frame, it The TPID of frame
obtains a tag (based on PVID) and is transmitted by C-port
forwarded. will be set to 0x8100.

34
 When the port receives a tagged frame,
1. if the tagged frame has TPID=0x8100, it is
forwarded.
2. if the TPID of tagged frame is not 0x8100
(ex. 0x88A8), it will be discarded.
S-port  When the port receives an untagged frame, it The TPID of frame
obtains a tag (based on PVID) and is transmitted by S-port
forwarded. will be set to 0x88A8.
 When the port receives a tagged frame,
1. if an tagged frame has TPID=0x88A8, it is
forwarded.
2. if the TPID of tagged frame is not 0x88A8
(ex. 0x8100), it will be discarded.
S-custom-port  When the port receives an untagged frame, it The TPID of frame
obtains a tag (based on PVID) and is transmitted by
forwarded. S-custom-port will be
 When the port receives a tagged frame, set to a self-determined
1. if an tagged frame has TPID=0x88A8, it is value, which can be set
forwarded. by the user at Ethertype
2. if the TPID of tagged frame is not 0x88A8 for Custom S-ports on
(ex. 0x8100), it will be discarded. top.

In summary, the different Port Type Ingress behaviors can be illustrated as such:

35
36
Egress behavior in the meantime, can be configured on the last 3 columns under Port VLAN and
Tx Tag.

 Port VLAN Mode


This option determines how to process VLAN tags for ingress and egress traffic
 When None is selected, a VLAN tag with the classified VLAN ID is inserted in frames
transmitted on the port. This mode is normally used for ports connected to VLAN aware
switches.
 When Specific (the default value) is selected, a Port VLAN ID can be configured (see
below). Untagged frames received on the port are classified to the Port VLAN ID. If
VLAN awareness is disabled, all frames received on the port are classified to the Port
VLAN ID. If the classified VLAN ID of a frame transmitted on the port is different from
the Port VLAN ID, a VLAN tag with the classified VLAN ID is inserted in the frame.

 Tx Tag
This option determines the Egress Behavior of the selected Port.
 Untag_pvid - All VLANs except the configured PVID will be tagged.
 Tag_all - All VLANs are tagged.
 Untag_all - All VLANs are untagged.

37
5.3 VLAN Communication Example
Consider the below VLAN Port Configuration as an example. This example displays the procedure
how the DHCP Client accesses the IP address from DHCP Server which is 4ipnet WHG-series
WLAN Controller important application .Port 1 is set as the Trunk Port that shares the same VLAN
Membership with Port 5, Port 9 and Port 13.

38
1. A DHCP client is connected to Port 5. Because of Port 5 configured as C-Port, untagged
packets will be tagged 3106 (according to the PVID). The Trunk Port Port 1 has Tx Tag
configured as “Tag_all” hence sends the packet to the DHCP Server with VLAN 3106.

2. Port 1 in turn sends the DHCP Offer to all ports of the same VLAN Membership. And
because Ports 5, 9, and 13 are all set to “Untag_pvid”, DHCP Offer to Port 5 will become
untagged, while Ports 9 and 13 will forward packets with the 3106 tag.

39
3. Therefore, the DHCP Client connected to Port 5 replies with a unicast untagged DHCP
request packet

4. Finally, the DHCP Client successfully obtains an IP Address from the DHCP Server.

40
Chapter 6. Power over Ethernet

The 4ipnet SW1024 is capable of supplying Power over Ethernet (PoE) following IEEE 802.3af/ at
standard. Besides, the 4ipnet SW1024 act as a PSE (Power Sourcing Equipment) that delivers
electrical power with maximum total power budget up to 500W. The connected PD (Powered
Devices) like Enterprise Access Points, IP cameras, or IP phones, can be powered over existing
copper cables without interfering with the network traffic, updating the physical network or
modifying the network infrastructure.

This chapter provides detailed instructions on how power can be configured and managed on the
Web Management Interface.

Configuration path: Configuration >> PoE

 Power over Ethernet Configuration


Power reserved for each port can be configured in a variety of ways.

Reserve Power by Class: Negotiation between the Power Sourcing Equipment PSE) and
the Powered Device (PD) commences after the Detection stage. Power reserved to each
port is determined according to the Class negotiation. There are four different classes including 4,
7, 15.4, or 30Watts.
p.s. In this mode, the Maximum Power fields have no effect.

Reserve Power by Allocation: The amount of power that each port may reserve is
specified manually by administrators. When the “Allocation” option is selected, the administrator
will be able to enter the desired Maximum Power (W) in the table below.

Reserve Power by LLDP-MED: This mode is similar to the Class mode expect that each
port determines the amount power it reserves by exchanging PoE information using the
LLDP protocol and reserves power accordingly. If no LLDP information is available for a
port, the port will reserve power using the class mode.
p.s. In this mode, the Maximum Power fields have no effect.

41
For all modes, if a port uses more power than the power reserved for that port, it is shut
down.

 Power Management Mode


There are 2 modes for Power Management for the system

Actual Consumption: The system calculates the total actual power consumed for the system.
When this value exceeds 500W, the ports begin to shut down beginning from the ports with the
lowest priority. When 2 ports have the same priority level, the higher port number is shut down.
When a port’s actual power consumption is higher than the set reserved Maximum Power, this
also triggers the port to shut down.

Reserved Power: In this mode, when the total reserved power exceeds 500W, the ports are shut
down.

 PoE Mode

42
4ipnet SW1024 provide three Power over Ethernet operating modes including,

Disabled: PoE feature is disabled for the port


PoE: Enable PoE IEEE 802.3af (Class 4 PDs limited up to 15.4W)
PoE+: Enable PoE IEEE 802.3at (Class 4 PDs limited up to 30W)

 Priority
Port priority is used when remote devices require more power than the 4ipnet SW1024
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. (Priority options: Low, High,
Critical)

 Maximum Power
The maximum power can be delivered to a remote device.

43
Chapter 7. Loop Protection

A network loop is caused by switches or hubs being plugged into themselves, causing networking
packets to be bounced between the ports infinitely. Loop protection is a crucial mechanism to
maintain network stability on your switch.

7.1 General Loop Protection Setting


The SW1024’s Loop Protection mechanism allows us to shut down or log information per port
when network loop is detected.

Configuration path: Configuration >> Loop Protection

Enable Loop Protection: This is the global control for the system (Enable/Disable).
Transmission Time: A Loop Protection data unit (PDU) is sent on each port when Loop
Protection is enabled. The interval between each PDU can be configured (1 ~ 10 seconds).
Shutdown Time: The time period for which the port will be shut down in case a loop is detected.
Valid shutdown time values are from 0 to 604800 seconds, where 0 will disable the port until
system restarts.

44
We are able to determine if the loop protection mechanism is to be applied for each port, and also
the corresponding action when loop is detected. The administrator can also determine if each port
is to generate loop protection PDUs or just passively listen for these PDUs.

We may check the status for Loop Protection in Monitor >> Loop Protection

45
7.2 Spanning Tree Protocol (STP)
The Spanning Tree Protocol is a network protocol designed to ensure a loop-free bridged Ethernet
local area network (Layer 2). Besides the basic bridge loops protection, STP also assigns backup
paths should an active link fail.

Configuration path: Configuration >> Spanning Tree >> Bridge Settings

The SW1024 supports 3 types of STP Protocol versions:

Spanning Tree Protocol (STP), specified in IEEE 802.1D 1998

Rapid Spanning Tree Protocol (RSTP), specified in IEEE 802.1w; standardized in IEEE 802.1D
2004

Multiple Spanning Tree Protocol (MSTP), specified in IEEE 802.1s; standardized in IEEE
802.1Q 2003

46
Port operation for STP and RSTP are the same, except that RSTP provides a faster
re-convergence time than STP.

MSTP enables multiple VLANs to be mapped to the same spanning-tree instance. This is
important especially for a network with a large number of VLANs. In MSTP, all of the
interconnected bridges that have the same MSTP configuration comprise of an MST region. An
MSTP configuration consists of the configuration name, the configuration revision, and the
mapping of VLANs to MSTIs (Multiple Spanning Tree Instance).

General STP Bridge Settings

Bridge Priority: Consists of 16 sets of numeric values. The lower the Bridge Priority number, the
higher the priority.
Forward Delay: The time spent (between 4 – 30 seconds) in the listening and learning states
Max Age: The default max age timer is 20 seconds. The max age timer is how long a BPDU
(Bridge Protocol Data Unit) is stored before it is flushed. If this timer expires before the interface
receives a new BPDU, the interface transitions to the listening state. An expired max age
parameter is usually caused by a link failure.
Maximum Hop Count: In the MSTP protocol, this value is used for the IST (Internal Spanning
Tree) and the MSTI (Multiple Spanning Tree Instance) topology as a hop count limit on how far the

47
Spanning Tree protocol packet can propagate inside of a MSTP Region.
Transmit Hold Count: The number of BPDU's a bridge port can send per second.

For guide on Advanced Settings and MSTI for MSTP configurations, please refer to Appendix A.

48
Chapter 8. IP Multicasting

The SW1024 supports both IPv4 and IPv6 multicast forwarding and filtering. IGMP Snooping
defines how IPv4 multicast traffic is managed, while MLD defines how IPv6 multicast traffic is
managed.

8.1 IGMP Snooping


Internet Group Management Protocol Snooping (IGMP Snooping) is a multicast constraining
mechanism that runs on Layer 2 devices to manage and control multicast groups. By listening to
conversations between the router and the hosts, the switch maintains a map of which links need
which IP multicast streams. Multicasts may be filtered from the links which do not need them and
thus controls which ports receive specific multicast traffic.

8.1.1 Basic Configuration

Configuration path: Configuration >> IPMC >> IGMP Snooping >> Basic Configuration

Snooping Enabled: The global Enable/Disable switch for IGMP Snooping


Unregistered IPMCv4 Flooding Enabled: Unregistered IPMCv4 traffic is unknown multicast
traffic. The flooding control takes effect only when IGMP Snooping is enabled.
IGMP SSM Range: SSM (Source-Specific Multicast) Range allows the SSM-aware hosts and
routers run the SSM service model for the groups in the address range.
Leave Proxy Enable: Enable to avoid unnecessary leave messages to the router.
Proxy Enabled: Enable to avoid forwarding unnecessary join and leave messages to the router.

49
Determine the Router Ports, Fast Leave and Throttling function on the SW1024.

A Router Port is a port on the SW1024 that connects to the Layer 3 multicast device (L3 Router or
IGMP Querrier).

Fast Leave enables the software to remove the group state when it receives an IGMP Leave
report without sending an IGMP query message.

Throttling can be used to limit the number of multicast groups to which a switch port can belong.

8.1.2 IGMP Snooping VLAN Configuration

VLAN can be enabled for IGMP Snooping (up to 64 VLANs). This feature registers multiple hosts
on different VLANs to one single multicast VLAN, which eliminates the need for the router to send

50
out multiple packets to hosts on different VLANs.

Configuration path: Configuration >> IPMC >> IGMP Snooping >> VLAN Configuration

VLAN ID: The set VLAN ID for the entry.


Snooping Enabled: Check to enable IGMP Snooping per-VLAN.
IGMP Querier: Check to enable IGMP Querier in the VLAN. The responsibility of the Querier is to
send out IGMP group membership queries on a timed interval, to retrieve IGMP membership
reports from active members, and to allow updating of the group membership tables.
Compatibility: Determine the IGMP version on the selected VLAN entry.
RV: The Robustness Variable allows tuning for the expected packet loss on a network. The
allowed range is 1 to 255.
QI (sec): The Query Interval is the interval between General Queries sent by the Querier. The
allowed range is 1 to 31744 seconds.
QRI (0.1sec): Query Response Interval. The Maximum Response Delay used to calculate the
Maximum Response Code inserted into the periodic General Queries. The allowed range is 0
to 31744 in tenths of seconds.
LLQI (0.1sec): Last Member Query Interval. The Last Member Query Time is the time value
represented by the Last Member Query Interval, multiplied by the Last Member Query Count. The
allowed range is 0 to 31744 in tenths of seconds.
URI (sec): Unsolicited Report Interval. The Unsolicited Report Interval is the time between
repetitions of a host's initial report of membership in a group. The allowed range is 0 to 31744
seconds.

8.1.3 IGMP Snooping Port Group Filtering Configuration

Different IP Multicast Groups can be filtered on selected ports.

Configuration path: Configuration >> IPMC >> IGMP Snooping >> Port Group Filtering

51
Enter the Filtering Groups for the desired ports and click “Save” to apply settings.

8.2 MLD Snooping


MLD Snooping (Multicast Listener Discovery Snooping) shares the same configuration concept as
IGMP Snooping but in IPv6. MLD is a protocol used by IPv6 multicast routers to discover the
presence of multicast listeners (nodes configured to receive IPv6 multicast packets) on its directly
attached links and to discover which multicast packets are of interest to neighboring nodes. MLD
is derived from IGMP; MLD version 1 (MLDv1) is equivalent to IGMPv2, and MLD version 2
(MLDv2) is equivalent to IGMPv3.

Configuration path: Configuration >> IPMC >> MLD Snooping

For detailed configuration instructions, please refer to Chapter 8.1 or Appendix A.

52
Chapter 9. Aggregation

Link Aggregation is the concept of combining multiple network connections in parallel to increase
throughput, and also to provide redundancy should one link fail. There are two types of
aggregation supported on the SW1024, namely Static Aggregation and Dynamic Aggregation.

9.1 Static Aggregation

Static Aggregation can be done on the current selected SW1024 unit by allocating ports to Groups
(Up to 13 Groups). The below example gives a clear illustration on how ports can be assigned to
different groups for aggregation.

Configuration path: Configuration >> Aggregation >> Static

Port 1, Port 2 and Port 3 are allocated for link aggregation (Group 1).
Port 4 and Port 5 are allocated for link aggregation (Group 2).
Port 6 and Port 7 are allocated for link aggregation (Group 3).
Port 8 and Port 9 are allocated for link aggregation (Group 4).
The remaining ports (Port 10 to Port 26) are set in normal mode.

53
Clicking “Save” applies the configured settings, while clicking “Reset” removes all aggregations
and set all ports to Normal Mode.

Hash Code Contributors are global parameters for the system, used to calculate the destination
port for the frame. Hash Code Contributors include “Source MAC Address”, “Destination MAC
Address”, “IP Address”, and “TCP/IP Port Number”.

9.2 Dynamic Aggregation

LACP (Link Aggregation Control Protocol) can be enabled on the SW1024 for dynamic bundling of
several physical ports to form one port channel. LACP works by sending frames (LACPDUs) down
all links that have the protocol enabled. If it finds a device on the other end of the link that also has
LACP enabled, it will also independently send frames along the same links enabling the two units
to detect multiple links between themselves and then combine them into a single logical link.
LACP can be configured in Active Mode or Passive Mode. In Active Mode it will always send
frames along the configured links. Whereas in Passive Mode it acts as a standby “speak when
spoken to” role and is used as a way of controlling accidental loops

Configuration path: Configuration >> Aggregation >> LACP

Use the checkbox to determine which Ports to enable LACP. The “Key” value can be set per port
within the 1 – 65535 range. When set in “Auto”, physical link speeds 10Mbps is set as 1, 100Mbps
(Fast Ethernet) is set as 2, 1000Mbps (GbE) is set as 3. When set in “Specific”, a user-defined

54
value can be entered, and ports with the same Key value are in the same aggregation group.

Status for aggregation can be checked at

Configuration path: Monitor >> LACP >> Port Status

55
Chapter 10. Utilities for Maintenance

10.1 Administrator Accounts

The SW1024’s root management account is the “admin” account with full access, modification and
nd
application privilege and authority. There are however, 2 tier accounts with less authority which
may be created for management personnel to access their designated assigned areas of authority,
a necessary feature for large scale deployment requiring multiple management personnel.

Configuration path: Configuration >> Security >> Switch >> Users

There is only one management account under default status. Group Permission Settings will
allow you to customize the accessible Web Interface pages for a particular management group
and in turn, create management accounts for that group.

To add a new Admin Account, click “Add New User”, determine the Account Username, Password,
and the corresponding admin Privilege Level.

56
There are 15 Privilege Levels for the system. Different Privilege Levels on different pages of the
management interface can be set for each Admin Account. All Admin Accounts can be configured
with different read-only or read-write access.

For more detailed configurations on Switch Management, please refer to Appendix A.

57
10.2 Configuration Backup and Restore
This function is used to backup/restore the SW1024 settings.

Configuration path: Maintenance >> Configuration >> Save / Upload

Click “Save Configuration” to download an XML file to your local drive. Vice Versa, to upload an
XML configuration file, select the file from your local drive and click “Upload”.

10.3 Firmware Upgrade


This function is used to backup/restore the SW1024 settings.

Configuration path: Maintenance >> Software >> Upload

The administrator can obtain the latest firmware from 4ipnet’s website or 4ipnet’s Support Team
and upgrade the system. Click Browse to search for the firmware file on your local drive and click
Upload to firmware upgrade. It might take a few minutes before the upgrade process completes
and the system needs to be restarted afterwards to activate the new firmware.

58
The system is capable of saving two images, and one can be a backup alternate image.

10.4 System Restart and Reset


This function allows the administrator to safely restart the switch, and the process might take
several minutes to complete. Click Yes to restart. If the power needs to be turned off, it is highly
recommended to restart the switch first and then turn off the power after completing the restart
process.

Configuration path: Maintenance >> Restart Device

The administrator may reset the system to factory default from the following configuration path.

59
Configuration path: Maintenance >> Factory Defaults

Note that the IP address is retained after a reset to factory default.

NOTE
Administrators can restore factory defaults by cabling between Port 1 and Port 2 and
then turn on the power for dozens of seconds. 4ipnet SW1024 could reset to factory
default including the IP address and administration password.

Detail operating procedures:


1. Turning off switch power
2. Unplugging all the RJ-45 cable on switches
3. Using ONE RJ-45 cable connect port one and port two
4. Turning on switch power for 1~2 minutes
5. It will then be back to factory default settings

60
Appendix A. UI Reference Index
The switch provides abundant software features. Once logged on to the switch, you may
start configuring the settings or monitoring the status.

The following provides a detailed Web UI configuration guide.

1. System Configuration
1.1. System Information
This page shows the system information and allows you to configure the new settings.

System 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 255, and the allowed content is the ASCII
characters from 32 to 126.

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-Za-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 255.

System Location

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

Time zone Offset

Provide the time zone offset relative to UTC/GMT.


The offset is given in minutes east of GMT. The valid range is from -720 to 720 minutes.

61
Buttons:
Save: Click to save changes

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

1.2. IP Configuration

Configure the switch-managed IP information on this page.

The Configured column is used to view or change the IP configuration.

The Current column is used to show the active IP configuration.

DHCP Client

Enable the DHCP client by checking this box. If DHCP fails and the configured IP address is zero, DHCP
will retry. If DHCP fails and the configured IP address is non-zero, DHCP will stop and the configured IP
settings will be used. The DHCP client will announce the configured System Name as hostname to
provide DNS lookup.

IP Address

Provide the IP address of this switch in dotted decimal notation.

IP Mask

Provide the IP mask of this switch dotted decimal notation.

IP Router

Provide the IP address of the router in dotted decimal notation.

NTP Provide the IP address of the NTP Server in dotted decimal notation.

62
DNS Server

Provide the IP address of the DNS Server in dotted decimal notation.

VLAN ID

Provide the managed VLAND ID. The allowed range is 1 to 4095.

DNS Proxy

When DNS proxy is enabled, the switch will relay DNS requests to the current configured DNS server on
the switch, and reply as a DNS resolver to the client device on the network.

Buttons
Save: Click to save changes

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

Renew: Click to renew DHCP. This button is only available if DHCP is enabled.

1.3. IPv6 Configuration

Configure the switch-managed IPv6 information on this page:

The Configured column is used to view or change the IPv6 configuration.

The Current column is used to show the active IPv6 configuration.

Auto Configuration

Enable IPv6 auto-configuration by checking this box. If fails, the configured IPv6 address is zero. The
router may delay responding to a router solicitation for a few seconds, the total time needed to complete
auto-configuration can be significantly longer.

63
Address

Provide the 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'.

Prefix

Provide the IPv6 Prefix of this switch. The allowed range is 1 to 128.

Router

Provide the IPv6 gateway 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'.

Buttons

Save: Click to save changes

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

Renew: Click to renew IPv6 AUTOCONF. This button is only available if IPv6 AUTOCONF is enabled.

1.4. NTP Configuration:

NTP is short of Network Time Protocol. Network Time Protocol (NTP) is used to synchronize time
clocks on the internet. You can configure NTP Servers' IP address here to synchronize the clocks of the

remote time server on the network.

This page indicates the NTP mode operation:

64
Mode

The Possible modes are:


Enable NTP mode operation. When NTP mode operation is enabled, the agent forwards NTP messages
between the clients and the server when they are not on the same subnet domain.
Disable NTP mode operation.

Server #

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

Buttons
Save: Click to save changes

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

1.5. System Log Configuration:


System Log is useful to provide system administrator monitor switch events history. The switch
supports syslog server mode. User can install the syslog server in one computer, then
configure the server address and event types in the switch's system log configuration. When
the events occur, the switch will send information or warning message to the syslog server.

65
The administrator can analysis the system logs recorded in the syslog server to find out the
cause of the issues.
The switch Web UI allows you to Enable the Syslog Server, assign the IP address and assign
the syslog level.

Server Mode

Indicates 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:
Enable server mode operation.
Disable server mode operation.

Server Address

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

Syslog Level

Indicates what kind of message will send to syslog server. Possible modes are:
Info: Send information, warnings and errors.
Warning: Send warnings and errors.
Error: Send errors.

Buttons

Save: Click to save changes

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

66
2. Power Reduction
2.1. EEE Configuration:

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.

For maximizing the power saving, the circuit isn't started at once transmit data are ready for a port, but is
instead queued until 3000 bytes of data are ready to be transmitted. For not introducing a large delay in
case that data less than 3000 bytes shall be transmitted, data are always transmitted after 48 us, giving a
maximum latency of 48 us + the wakeup time.

If desired it is possible to minimize the latency for specific frames, by mapping the frames to a specific
queue (done with QOS), and then mark the queue as an urgent queue. When an urgent queue gets data
to be transmitted, the circuits will be powered up at once and the latency will be reduced to the wakeup
time.

Port

The switch port number of the logical EEE port.

EEE Enabled

Controls whether EEE is enabled for this switch port.

EEE Urgent Queues

67
Queues set will activate transmission of frames as soon as any data is available. Otherwise the queue will
postpone the transmission until 3000 bytes are ready to be transmitted.

Buttons

Save: Click to save changes

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

68
3. Port Configuration:
This page displays current port configurations and link status. Some of the Ports' settings can also be
configured here.

Port

This is the 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.

Ex: 1Gfdx: 1G indicates the Gigabit Speed, fdx indicates the Full Duplex Mode.

Configured Link Speed

Select any available link speed for the given switch port.

Auto Speed: selects the highest speed that is compatible with a link partner.

Disabled: disables the switch port operation.

Fiber Speed

Configure speed for fiber port.

Note: Port speed for the Copper ports will automatically be set to Auto when dual media is selected.

Disable SFPs (Copper port only).

SFP-Auto automatically determines the speed at 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.
1000-X force SFP speed to 1000-X.

69
100-FX force SFP speed to 100-FX.

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.

Maximum Frame Size

Enter the maximum frame size allowed for the switch port, including FCS.

The switch supports up to 9K Jumbo Frame.

Excessive Collision Mode

Configure port transmit collision behavior.


Discard: Discard frame after 16 collisions (default).
Restart: Restart back-off algorithm after 16 collisions.

Power Control

The Usage column shows the current percentage of the power consumption per port. The Configured
column allows for changing the power savings mode parameters per port.
Disabled: All power savings mechanisms disabled.
ActiPHY: Link down power savings enabled.
PerfectReach: Link up power savings enabled.
Enabled: Both link up and link down power savings enabled.

Buttons

Save: Click to save changes

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

Refresh: Click to refresh the page. Any changes made locally will be undone.

70
4. Security Configuration:
The Security Configuration feature includes 3 sub-titles, Switch, Network and AAA.

4.1. Security / Switch


The switch settings includes User Database, Privilege Levels, Authentication Method, SSH, HTTPS, Access
Management, SNMP and RMON setting. Following are the topic and configuration guide.

4.1.1. Security / Switch / Users Configuration


This page provides an overview of the current users. Currently the only way to login as another user on the
web server is to close and reopen the browser.

This page configures a user: This is also a link to Add User & Edit User

Add New User/Edit User

Click "Add New User", the configuration page goes to "Add User" screen. You can see the User Setting
table, follow the below instruction to fill the table.

Click the created User Name, the page goes to "Edit User" screen, you can change the settings on it.

71
User Name

A string identifying the user name that this entry should belong to. The allowed string length is 1 to 32.
The valid user name is a combination of letters, numbers and underscores.

Password

The password of the user. The allowed string length is 0 to 32.

Privilege Level

The privilege level of the user. The allowed range is 1 to 15.

If the privilege level value is 15, it can access all groups, i.e. that is granted the fully control of the device.
But others value need to refer to each group privilege level. User's privilege should be same or greater
than the group privilege level to have the access of that group.

By default setting, privilege level 5 has read-only access and privilege level 10 has read-write access.
And system maintenance (software upload, factory defaults and etc.) requires a user privilege level of 15.
Generally, privilege level 15 is used for an administrator account, privilege level 10 for a standard user
account and privilege level 5 for a guest account.

Check the next section to see how privilege level can be configured.

Buttons

Add new user: Click to add a new user.

4.1.2. Security / Switch / Privilege Levels Configuration:

This page provides an overview of privilege levels.

72
Group Name

The name identifying the privilege group. In most cases, a privilege level group consists of a single
module (e.g. LACP, RSTP or QoS), but a few of them contains more than one.

The following description defines these privilege level groups in details:


System: Contact, Name, Location, Time zone, Log.
Security: Authentication, System Access Management, Port (contains Dot1x port, MAC based and the
MAC Address Limit), ACL, HTTPS, SSH, ARP Inspection and IP source guard.
IP: Everything except 'ping'.
Port: Everything except 'VeriPHY'.
Diagnostics: 'ping' and 'VeriPHY'.
Maintenance: CLI- System Reboot, System Restore Default, System Password, Configuration Save,
Configuration Load and Firmware Load. Web- Users, Privilege Levels and everything in Maintenance.
Debug: Only present in CLI.

Privilege Levels

Every group has an authorization Privilege level for the following sub groups: configuration read-only,
configuration/execute read-write, status/statistics read-only, status/statistics read-write (e.g. for clearing
of statistics).

User Privilege should be same or greater than the authorization Privilege level to have the access to that
group.

Insufficient Privilege Level: If you login with lower level privilege and try to access the high privilege
level configuration feature, the following message, Insufficient Privilege Level will appear. If you want
continue, be sure that you have the privilege.

73
Buttons

Save: Click to save changes

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

4.1.3. Security / Switch / Auth Method


This page allows you to configure how a user is authenticated when he logs into the switch via one of the
management client interfaces.
The table has one row for each client type and a number of columns, which are:

Client

The management client for which the configuration below applies.

Authentication Method

Authentication Method can be set to one of the following

74
values:

none: authentication is disabled and login is not possible.

local: use the local user database on the switch for authentication.

RADIUS: use a remote RADIUS server for authentication.

TACACS+ : use a remote TACACS server for authentication.

Fallback

Enable fallback to local authentication by checking this box.


If none of the configured authentication servers are alive, the local user database is used for
authentication.
This is only possible if the Authentication Method is set to a value other than 'none' or 'local'.

Buttons

Save: Click to save changes

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

4.1.4. Security /Switch / SSH Configuration


With SSH, you can remotely connect to the switch by command line interface. The SSH connection can
secure all the configuration commands you sent to the switch. It is also known as secured Telnet console.

To access the switch by SSH, you should install SSH client on your computer, such as PuTTy console
tool. In the switch side, the switch acts as SSH server for user login, and you can Enable or Disable SSH
on this page.

Please check the chapter 3.3 Preparation for Telnet/SSH connection to see how to manage the switch
through SSH console.

75
Mode

Indicates the SSH mode operation. Possible modes are:

Enable: Enable SSH mode operation.

Disabled: Disable SSH mode operation.

Buttons

Save: Click to save changes

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

4.1.5. Security / Switch / HTTPS Configuration


The web management page also provides secured management HTTPS login. All the configuration
commands will be secured and will be hard for the hackers to sniff the login password and configuration
commands.

This page allows you to configure HTTPS mode.

Mode

Indicates the HTTPS mode operation. Possible modes are:


Enable: Enable HTTPS mode operation.
Disabled: Disable HTTPS mode operation.

Automatic Redirect

Indicates the HTTPS redirect mode operation. Automatically redirect web browser to HTTPS when
HTTPS mode is enabled. Possible modes are:

76
Enable: Enable HTTPS redirect mode operation.

Disabled: Disable HTTPS redirect mode operation.

Buttons

Save: Click to save changes

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

4.1.6. Security / Switch / Access Management Configuration


The Access Management mode allows user to limit the switch access with specific range of IP address
and disable some remote management service, such HTTP, HTTPS, SNMP, Telnet and SSH. This
feature is important while user installed the switch on network. After enabled the Access Management,
only the pre-configured IP address or a range of IP address can access the switch management interface,
and only the available service can be accessed.

Configure access management table on this page. The maximum entry number is 16. If the application's
type match any one of the access management entries, it will allow access to the switch.

Example of the below figure, only the IP Addresses range from 192.168.2.101 to 192.168.2.200 can
access the switch's management interface. The available services are HTTP, HTTPS, SNMP, Telnet and
SSH. If there is one IP address, 192.168.2.201 try to open the web management interface, it is not
allowed.

Mode

Indicates the access management mode operation. Possible modes are:


Enable: Enable access management mode operation.
Disabled: Disable access management mode operation.

Delete

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

Start IP address

Indicates the start IP address for the access management entry.

End IP address

Indicates the end IP address for the access management entry.

With the Start and End IP address, you can assign a range of IP addresses.

HTTP/HTTPS

Indicates that the host can access the switch from HTTP/HTTPS interface if the host IP address matches
the IP address range provided in the entry.

77
SNMP

Indicates that the host can access the switch from SNMP interface if the host IP address matches the IP
address range provided in the entry.

TELNET / SSH

Indicates that the host can access the switch from TELNET/SSH interface if the host IP address matches
the IP address range provided in the entry.

Buttons

Add New Entry: Click to add a new group entry

Save: Click to save changes

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

4.1.7. Security / Switch / SNMP


Simple Network Management Protocol (SNMP) is a protocol used for exchanging management
information between network devices. The switch supports SNMP and equips lots of OIDs for remote
management. All the OIDs are unique and corresponding to one feature/command.

The switch can support SNMP V1, V2c and V3. The following commands show how to configure SNMP
and its related parameters.

78
Mode

Indicates the SNMP mode operation. Possible modes are:


Enable: Enable SNMP mode operation.
Disabled: Disable SNMP mode operation.

Version

Indicates the SNMP supported version. Possible versions are:


SNMPv1: Set SNMP supported version 1.
SNMPv2c: Set SNMP supported version 2c.
SNMPv3: Set SNMP supported version 3.

Read Community

Indicates the community read access string to permit access to SNMP agent. The allowed string length is
0 to 255, and the allowed content is the ASCII characters from 33 to 126.

The field is applicable only when SNMP version is SNMPv1 or SNMPv2c. If SNMP version is SNMPv3,
the community string will be associated with SNMPv3 communities table. It provides more flexibility to
configure security name than a SNMPv1 or SNMPv2c community string. In addition to community string,
a particular range of source addresses can be used to restrict source subnet.

Write Community

Indicates the community write access string to permit access to SNMP agent. The allowed string length is
0 to 255, and the allowed content is the ASCII characters from 33 to 126.

The field is applicable only when SNMP version is SNMPv1 or SNMPv2c. If SNMP version is SNMPv3,
the community string will be associated with SNMPv3 communities table. It provides more flexibility to
configure security name than a SNMPv1 or SNMPv2c community string. In addition to community string,
a particular range of source addresses can be used to restrict source subnet.

Engine ID

Indicates the SNMPv3 engine ID. The string must contain an even number (in hexadecimal format) with
number of digits between 10 and 64, but all-zeros and all-'F's are not allowed. Change of the Engine ID
will clear all original local users.

SNMP Trap Configuration


Configure SNMP trap on this page.

Trap Mode

Indicates the SNMP trap mode operation. Possible modes are:


Enable: Enable SNMP trap mode operation.
Disabled: Disable SNMP trap mode operation.

Trap Version

Indicates the SNMP trap supported version. Possible versions are:


SNMPv1: Set SNMP trap supported version 1.
SNMPv2c: Set SNMP trap supported version 2c.
SNMPv3: Set SNMP trap supported version 3.

Trap Community

Indicates the community access string when sending SNMP trap packet. The allowed string length is 0 to
255, and the allowed content is ASCII characters from 33 to 126.

Trap Destination Address

79
Indicates the SNMP trap destination address.

Trap Destination IPv6 Address

Provide the trap destination 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'.

Trap Authentication Failure

Indicates that the SNMP entity is permitted to generate authentication failure traps. Possible modes are:
Enable: SNMP trap authentication failure.
Disabled: Disable SNMP trap authentication failure.

Trap Link-up and Link-down

Indicates the SNMP trap link-up and link-down mode operation. Possible modes are:
Enable: Enable SNMP trap link-up and link-down mode operation.
Disabled: Disable SNMP trap link-up and link-down mode operation.

Trap Inform Mode

Indicates the SNMP trap inform mode operation. Possible modes are:
Enable: Enable SNMP trap inform mode operation.
Disabled: Disable SNMP trap inform mode operation.

Trap Inform Timeout (seconds)

Indicates the SNMP trap inform timeout. The allowed range is 0 to 2147.

Trap Inform Retry Times

Indicates the SNMP trap inform retry times. The allowed range is 0 to 255.

Trap Probe Security Engine ID

Indicates the SNMP trap probe security engine ID mode of operation. Possible values are:
Enable: Enable SNMP trap probe security engine ID mode of operation.
Disabled: Disable SNMP trap probe security engine ID mode of operation.

Trap Security Engine ID

Indicates the SNMP trap security engine ID. SNMPv3 sends traps and informs using USM for
authentication and privacy. A unique engine ID for these traps and informs is needed. When "Trap Probe
Security Engine ID" is enabled, the ID will be probed automatically. Otherwise, the ID specified in this field
is used. The string must contain an even number (in hexadecimal format) with number of digits between
10 and 64, but all-zeros and all-'F's are not allowed.

Trap Security Name

Indicates the SNMP trap security name. SNMPv3 traps and informs using USM for authentication and
privacy. A unique security name is needed when traps and informs are enabled.

Buttons

Save: Click to save changes

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

80
SNMPv3 Community Configuration
In SNMP V3, it is start to support User Name and its privilege. You can configure SNMPv3 community
table on this page:

The entry index key is Community.

Delete

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

Community

Indicates the community access string to permit access to SNMPv3 agent. The allowed string length is 1
to 32, and the allowed content is ASCII characters from 33 to 126. The community string will be treated as
security name and map a SNMPv1 or SNMPv2c community string.

Source IP

Indicates the SNMP access source address. A particular range of source addresses can be used to
restrict source subnet when combined with source mask.

Source Mask

Indicates the SNMP access source address mask.

Buttons

81
Add new community: Click to add a new community entry

Save: Click to save changes

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

SNMPv3 User Configuration

Configure SNMPv3 user table on this page. The entry index keys are Engine ID and User Name.

Delete

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

Engine ID

An octet string identifying the engine ID that this entry should belong to. The string must contain an even
number (in hexadecimal format) with number of digits between 10 and 64, but all-zeros and all-'F's are not
allowed. The SNMPv3 architecture uses the User-based Security Model (USM) for message security and
the View-based Access Control Model (VACM) for access control. For the USM entry, the usm User
Engine ID and usm User Name are the entry's keys. In a simple agent, usm User Engine ID is always that
agent's own snmp Engine ID value. The value can also take the value of the snmp Engine ID of a remote
SNMP engine with which this user can communicate. In other words, if user engine ID equal system
engine ID then it is local user; otherwise it's remote user.

User Name

A string identifying the user name that this entry should belong to. The allowed string length is 1 to 32,
and the allowed content is ASCII characters from 33 to 126.

Security Level

Indicates the security model that this entry should belong to. Possible security models are:

NoAuth, NoPriv: No authentication and no privacy.

82
Auth, NoPriv: Authentication and no privacy.

Auth, Priv: Authentication and privacy.


The value of security level cannot be modified if entry already exists. That means it must first be ensured
that the value is set correctly.

Authentication Protocol

Indicates the authentication protocol that this entry should belong to. Possible authentication protocols
are:
None: No authentication protocol.
MD5: An optional flag to indicate that this user uses MD5 authentication protocol.
SHA: An optional flag to indicate that this user uses SHA authentication protocol.
The value of security level cannot be modified if entry already exists. That means must first ensure that
the value is set correctly.

Authentication Password

A string identifying the authentication password phrase. For MD5 authentication protocol, the allowed
string length is 8 to 32. For SHA authentication protocol, the allowed string length is 8 to 40. The allowed
content is ASCII characters from 33 to 126.

Privacy Protocol

Indicates the privacy protocol that this entry should belong to. Possible privacy protocols are:
None: No privacy protocol.
DES: An optional flag to indicate that this user uses DES authentication protocol.

Privacy Password

A string identifying the privacy password phrase. The allowed string length is 8 to 32, and the allowed
content is ASCII characters from 33 to 126.

Buttons

Add new user: Click to add a new user entry

Save: Click to save changes

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

SNMPv3 Group Configuration

Configure SNMPv3 group table on this page:

The entry index keys are Security Mode and Security Name.

83
Delete

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

Security Model

Indicates the security model that this entry should belong to. Possible security models are:
v1: Reserved for SNMPv1.
v2c: Reserved for SNMPv2c.
usm: User-based Security Model (USM).

Security Name

A string identifying the security name that this entry should belong to. The allowed string length is 1 to 32,
and the allowed content is ASCII characters from 33 to 126.

Group Name

A string identifying the group name that this entry should belong to. The allowed string length is 1 to 32,
and the allowed content is ASCII characters from 33 to 126.

Buttons

Add new group: Click to add a new group entry

Save: Click to save changes

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

SNMPv3 View Configuration

Configure SNMPv3 view table on this page.

84
The entry index keys are View Name and OID Sub-tree.

Delete

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

View Name

A string identifying the view name that this entry should belong to. The allowed string length is 1 to 32,
and the allowed content is ASCII characters from 33 to 126.

View Type

Indicates the view type that this entry should belong to. Possible view types are:

Included: An optional flag to indicate that this view sub-tree should be included.
Excluded: An optional flag to indicate that this view sub-tree should be excluded.
In general, if a view entry's view type is 'excluded', there should be another view entry existing with view
type as 'included' and it's OID sub-tree should overstep the 'excluded' view entry.

OID Subtree

The OID defining the root of the sub-tree to add to the named view. The allowed OID length is 1 to 128.
The allowed string content is digital number or asterisk (*).

Buttons

Add new view: Click to add a new view entry

85
Save: Click to save changes

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

SNMPv3 Access Configuration

Configure SNMPv3 access table on this page. The entry index keys are Group Name, Security Model,

and Security Level.

Delete

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

Group Name

A string identifying the group name that this entry should belong to. The allowed string length is 1 to 32,
and the allowed content is ASCII characters from 33 to 126.

Security Model

Indicates the security model that this entry should belong to. Possible security models are:

Any: Any security model accepted(v1|v2c|usm).

V1:Reserved for SNMPv1.

V2c: Reserved for SNMPv2c.

Usm: User-based Security Model (USM).


Security Level : Indicates the security model that this entry should belong to.

Possible security models are:

NoAuth, NoPriv: No authentication and no privacy.

Auth, NoPriv: Authentication and no privacy.

Auth,Priv: Authentication and privacy.

86
Read View Name

The name of the MIB view defining the MIB objects for which this request may request the current values.
The allowed string length is 1 to 32, and the allowed content is ASCII characters from 33 to 126.

Write View Name

The name of the MIB view defining the MIB objects for which this request may potentially set new values.
The allowed string length is 1 to 32, and the allowed content is ASCII characters from 33 to 126.

Buttons

Add new access: Click to add a new access entry

Save: Click to save changes

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

4.1.8. RMON Statistics Configuration


RMON is short of Remote Monitoring On Network. An RMON implementation typically operates in a
client/server model. Monitoring device (Probe) contains RMON software agents that collect information of
the system and ports. The RMON software agent acts as server, and the network management system
(NMS) that communicate with it acts as client. The RMON agent of the switch supports 4 groups, such as
the Statistics, History, Alarm and Event.

RMON Group Function Elements

Statistics Contains statistics measured Packets dropped, packets sent, bytes


by the probe for each sent (octets), broadcast packets,
monitored interface on this multicast packets, CRC errors, undersize
device. packets, oversize packets, fragments,
jabbers, collisions, and counters for
Real-time LAN statistics e.g.
packets ranging from 64, 65 to 127, 128
utilization, collisions, CRC errors
to 255, 256 to 511, 512 to 1023, and 1024
to 1518 bytes.
History Records periodic statistical History of above Statistics.
samples from a network and
stores for retrieval.
Alarm Definitions for RMON SNMP Interval for sampling, particular variable,
traps to be sent when statistics sample type, value of statistics during the
exceed defined thresholds last sampling period, startup alarm, rising
threshold, rising index, falling threshold,
falling index.
Events Controls the generation and Event index, log index, event log time,
notification of events from this event description
device.

The NMS can get the above information through remotely polling. The information from the switch can be
collected, analyzed and displayed as table or graphic...etc.

87
RMON Statistics Configuration

Configure RMON Statistics table on this page. The entry index key is ID.

Delete

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

ID

Indicates the index of the entry. The range is from 1 to 65535.

Data Source

Indicates the port ID which wants to be monitored. If in stacking switch, the value must add 1000*(switch
ID-1), for example, if the port is switch 3 port 5, the value is 2005

Buttons

Add new entry: Click to add a new community entry

Save: Click to save changes

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

RMON History Configuration

Configure RMON History table on this page. The entry index key is ID

88
Delete

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

ID

Indicates the index of the entry. The range is from 1 to 65535.

Data Source

Indicates the port ID which wants to be monitored. If in stacking switch, the value must add 1000*(switch
ID-1), for example, if the port is switch 3 port 5, the value is 2005.

Interval

Indicates the interval in seconds for sampling the history statistics data. The range is from 1 to 3600,
default value is 1800 seconds.

Buckets

Indicates the maximum data entries associated this History control entry stored in RMON. The range is
from 1 to 3600, default value is 50.

Buckets Granted

The number of data shall be saved in the RMON.

Buttons

Add new entry: Click to add a new community entry.

Save: Click to save changes.

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

RMON Alarm Configuration

Configure RMON Alarm table on this page. The entry index key is ID.

89
Delete

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

ID

Indicates the index of the entry. The range is from 1 to 65535.

Interval

Indicates the interval in seconds for sampling and comparing the rising and falling threshold. The range is
from 1 to 2^31-1.

Variable

Indicates the particular variable to be sampled, the possible variables are:

InOctets:The total number of octets received on the interface, including framing characters.

InUcastPkts:The number of uni-cast packets delivered to a higher-layer protocol.

InNUcastPkts: The number of broad-cast and multi-cast packets delivered to a higher-layer protocol.

InDiscards: The number of inbound packets that are discarded even the packets are normal.

InErrors:The number of inbound packets that contained errors preventing them from being deliverable to
a higher-layer protocol.

InUnknownProtos: The number of the inbound packets that were discarded because of the unknown or
un-support protocol.

OutOctets: The number of octets transmitted out of the interface, including framing characters.

OutUcastPkts: The number of unicast packets that request to transmit.

OutNUcastPkts: The number of broad-cast and multi-cast packets that request to transmit.

OutDiscards: The number of outbound packets that are discarded event the packets is normal.

OutErrors: The number of outbound packets that could not be transmitted because of errors.

OutQlen: The length of the output packet queue (in packets).

90
Sample Type

The method of sampling the selected variable and calculating the value to be compared against the
thresholds, possible sample types are:

Absolute: Get the sample directly.


Delta: Calculate the difference between samples (default).

Value

The value of the statistic during the last sampling period.

Startup Alarm

The method of sampling the selected variable and calculating the value to be compared against the
thresholds, possible sample types are:

Rising Trigger alarm when the first value is larger than the rising threshold.

Falling Trigger alarm when the first value is less than the falling threshold.

RisingOrFalling Trigger alarm when the first value is larger than the rising threshold or less than the
falling threshold (default).

Rising Threshold

Rising threshold value (-2147483648-2147483647).

Rising Index

Rising event index (1-65535).

Falling Threshold

Falling threshold value (-2147483648-2147483647)

Falling Index

Falling event index (1-65535).

Buttons

Add new entry: Click to add a new community entry.

Save: Click to save changes.

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

RMON Event Configuration

Configure RMON Event table on this page. The entry index key is ID.

91
Delete

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

ID

Indicates the index of the entry. The range is from 1 to 65535.

Desc

Indicates this event, the string length is from 0 to 127, default is a null string.

Type

Indicates the notification of the event, the possible types are:


None: The total number of octets received on the interface, including framing characters.

Log: The number of unicast packets delivered to a higher-layer protocol.

SNMPtrap: The number of broad-cast and multi-cast packets delivered to a higher-layer protocol.

LogAndTrap: The number of inbound packets that are discarded even the packets are normal.

Community

Specify the community when trap is sent, the string length is from 0 to 127, default is "public".

Event Last Time

Indicates the value of sysUp Time at the time this event entry last generated an event.

Buttons

Add new entry: Click to add a new community entry.

Save: Click to save changes.

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

4.2. Security /Network

4.2.1. Port Security Limit Control Configuration

This page allows you to configure the Port Security Limit Control system and port settings.

Limit Control allows for limiting the number of users on a given port. A user is identified by a MAC address
and VLAN ID. If Limit Control is enabled on a port, the limit specifies the maximum number of users on
the port. If this number is exceeded, an action is taken. The action can be one of the four different actions
as described below.
The Limit Control module utilizes a lower-layer module, Port Security module, which manages MAC
addresses learnt on the port.

The Limit Control configuration consists of two sections, a system- and a port-wide.

System Configuration

Mode

Indicates if Limit Control is globally enabled or disabled on the switch. If globally disabled, other modules
may still use the underlying functionality, but limit checks and corresponding actions are disabled.

93
Aging Enabled

If checked, secured MAC addresses are subject to aging as discussed under Aging Period.

Aging Period

If Aging Period is checked, then the aging period is controlled with this input. If other modules are using
the underlying port security for securing MAC addresses, they may have other requirements to the aging
period. The underlying port security will use the shorter requested aging period of all modules that use the
functionality.
The Aging Period can be set to a number between 10 and 10,000,000 seconds.
To understand why aging may be desired, consider the following scenario: Suppose an end-host is
connected to a 3rd party switch or hub, which in turn is connected to a port on this switch on which Limit
Control is enabled. The end-host will be allowed to forward if the limit is not exceeded. Now suppose that
the end-host logs off or powers down. If it wasn't for aging, the end-host would still take up resources on
this switch and will be allowed to forward. To overcome this situation, enable aging. With aging enabled, a
timer is started once the end-host gets secured. When the timer expires, the switch starts looking for
frames from the end-host, and if such frames are not seen within the next Aging Period, the end-host is
assumed to be disconnected, and the corresponding resources are freed on the switch.

Port Configuration
The table allows you to configure the Port Configuration parameters, which are:

Port

The port number to which the configuration below applies.

Mode

Controls whether Limit Control is enabled on this port. Both this and the Global Mode must be set to
Enabled for Limit Control to be in effect. Notice that other modules may still use the underlying port
security features without enabling Limit Control on a given port.

Limit

The maximum number of MAC addresses that can be secured on this port. This number cannot exceed
1024. If the limit is exceeded, the corresponding action is taken.

94
The switch is "born" with a total number of MAC addresses from which all ports draw whenever a new
MAC address is seen on a Port Security-enabled port. Since all ports draw from the same pool, it may
happen that a configured maximum cannot be granted, if the remaining ports have already used all
available MAC addresses.

Action

If Limit is reached, the switch can take one of the following actions:

None: Do not allow more than Limit MAC addresses on the port, but take no further action.

Trap: If Limit+ 1 MAC addresses is seen on the port, send an SNMP trap. If Aging is disabled, only one
SNMP trap will be sent, but with Aging enabled, new SNMP traps will be sent every time the limit gets
exceeded.

Shutdown: If Limit + 1 MAC addresses is seen on the port, shut down the port. This implies that all
secured MAC addresses will be removed from the port, and no new address will be learned. Even if the
link is physically disconnected and reconnected on the port (by disconnecting the cable), the port will
remain shut down. There are three ways to re-open the port:
1) Boot the switch,
2) Disable and re-enable Limit Control on the port or the switch,
3) Click the Reopen button.

Trap & Shutdown: If Limit + 1 MAC addresses is seen on the port, both the "Trap" and the "Shutdown"
actions described above will be taken.

State

This column shows the current state of the port as seen from the Limit Control's point of view. The state
takes one of four values:

Disabled: Limit Control is either globally disabled or disabled on the port.

Ready: The limit is not yet reached. This can be shown for all actions.

Limit Reached: Indicates that the limit is reached on this port. This state can only be shown if Action is
set to None or Trap.
Shutdown: Indicates that the port is shut down by the Limit Control module. This state can only be shown
if Action is set to Shutdown or Trap & Shutdown.

Re-open Button

If a port is shut down by this module, you may reopen it by clicking this button, which will only be enabled
if this is the case. For other methods, refer to Shutdown in the Action section.
Note that clicking the reopen button causes the page to be refreshed, so non-committed changes will be
lost.

Buttons

Refresh: Click to refresh the page. Note that non-committed changes will be lost.

Save: Click to save changes.

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

95
4.2.2. Security / Network / Network Access Server Configuration

This page allows you to configure the IEEE802.1X and MAC-based authentication system and port

settings.

The IEEE 802.1X standard defines a port-based access control procedure that prevents unauthorized
access to a network by requiring users to first submit credentials for authentication. One or more central
servers, the backend servers, determine whether the user is allowed access to the network. These
backend (RADIUS) servers are configured on the "Configuration→Security→AAA" page. The
IEEE802.1X standard defines port-based operation, but non-standard variants overcome security
limitations as shall be explored below.

MAC-based authentication allows for authentication of more than one user on the same port, and doesn't
require the user to have special 802.1X supplicant software installed on his system. The switch uses the
user's MAC address to authenticate against the backend server. Intruders can create counterfeit MAC
addresses, which makes MAC-based authentication less secure than 802.1X authentication.

The NAS configuration consists of two sections, a system- and a port-wide.

System Configuration

Mode

Indicates if NAS is globally enabled or disabled on the switch. If globally disabled, all ports are allowed
forwarding of frames.

Re-authentication Enabled

If checked, successfully authenticated supplicants/clients are re-authenticated after the interval specified
by the Re-authentication Period. Re-authentication for 802.1X-enabled ports can be used to detect if a
new device is plugged into a switch port or if a supplicant is no longer attached.

For MAC-based ports, re-authentication is only useful if the RADIUS server configuration has changed. It
does not involve communication between the switch and the client, and therefore doesn't imply that a
client is still present on a port (see Aging Period below).

96
Re-authentication Period

Determines the period, in seconds, after which a connected client must be re-authenticated. This is only
active if the Re-authentication Enabled checkbox is checked. Valid values are in the range 1 to 3600
seconds.

EAPOL Timeout

Determines the time for retransmission of Request Identity EAPOL frames.


Valid values are in the range 1 to 65535 seconds. This has no effect for MAC-based ports.

Aging Period

This setting applies to the following modes, i.e. modes using the Port Security functionality to secure
MAC addresses:
• Single 802.1X
• Multi 802.1X
• MAC-Based Auth.
When the NAS module uses the Port Security module to secure MAC addresses, the Port Security
module needs to check for activity on the MAC address in question at regular intervals and free resources
if no activity is seen within a given period of time. This parameter controls exactly this period and can be
set to a number between 10 and 1000000 seconds.
If re-authentication is enabled and the port is in an 802.1X-based mode, this is not so critical, since
supplicants that are no longer attached to the port will get removed upon the next re-authentication, which
will fail. But if re-authentication is not enabled, the only way to free resources is by aging the entries.
For ports in MAC-based Auth. mode, re-authentication doesn't cause direct communication between the
switch and the client, so this will not detect whether the client is still attached or not, and the only way to
free any resources is to age the entry.

Hold Time

This setting applies to the following modes, i.e. modes using the Port Security functionality to secure
MAC addresses:
• Single 802.1X
• Multi 802.1X
• MAC-Based Auth.
If a client is denied access - either because the RADIUS server denies the client access or because the
RADIUS server request times out (according to the timeout specified on the
"Configuration→Security→AAA" page) - the client is put on hold in the Unauthorized state. The hold timer
does not count during an on-going authentication.
In MAC-based Auth. mode, the switch will ignore new frames coming from the client during the hold time.
The Hold Time can be set to a number between 10 and 1000000 seconds.

RADIUS-Assigned QoS Enabled

RADIUS-assigned QoS provides a means to centrally control the traffic class to which traffic coming from
a successfully authenticated supplicant is assigned on the switch. The RADIUS server must be
configured to transmit special RADIUS attributes to take advantage of this feature (see
RADIUS-Assigned QoS Enabled below for a detailed description).
The "RADIUS-Assigned QoS Enabled" checkbox provides a quick way to globally enable/disable
RADIUS-server assigned QoS Class functionality. When checked, the individual ports' ditto setting
determine whether RADIUS-assigned QoS Class is enabled on that port. When unchecked,
RADIUS-server assigned QoS Class is disabled on all ports.

RADIUS-Assigned VLAN Enabled

RADIUS-assigned VLAN provides a means to centrally control the VLAN on which a successfully
authenticated supplicant is placed on the switch. Incoming traffic will be classified to and switched on the
RADIUS-assigned VLAN. The RADIUS server must be configured to transmit special RADIUS attributes
to take advantage of this feature (see RADIUS-Assigned VLAN Enabled below for a detailed description).

97
The "RADIUS-Assigned VLAN Enabled" checkbox provides a quick way to globally enable/disable
RADIUS-server assigned VLAN functionality. When checked, the individual ports' ditto setting determine
whether RADIUS-assigned VLAN is enabled on that port. When unchecked, RADIUS-server assigned
VLAN is disabled on all ports.

Guest VLAN Enabled

A Guest VLAN is a special VLAN - typically with limited network access - on which 802.1X-unaware
clients are placed after a network administrator-defined timeout. The switch follows a set of rules for
entering and leaving the Guest VLAN as listed below.

The "Guest VLAN Enabled" checkbox provides a quick way to globally enable/disable Guest VLAN
functionality. When checked, the individual ports' ditto setting determines whether the port can be moved
into Guest VLAN. When unchecked, the ability to move to the Guest VLAN is disabled on all ports.

Guest VLAN ID

This is the value that a port's Port VLAN ID is set to if a port is moved into the Guest VLAN. It is only
changeable if the Guest VLAN option is globally enabled.
Valid values are in the range [1; 4095].

Max. Reauth. Count

The number of times the switch transmits an EAPOL Request Identity frame without response before
considering entering the Guest VLAN is adjusted with this setting. The value can only be changed if the
Guest VLAN option is globally enabled.
Valid values are in the range [1; 255].

Allow Guest VLAN if EAPOL Seen

The switch remembers if an EAPOL frame has been received on the port for the life-time of the port. Once
the switch considers whether to enter the Guest VLAN, it will first check if this option is enabled or
disabled. If disabled (unchecked; default), the switch will only enter the Guest VLAN if an EAPOL frame
has not been received on the port for the life-time of the port. If enabled (checked), the switch will
consider entering the Guest VLAN even if an EAPOL frame has been received on the port for the life-time
of the port.
The value can only be changed if the Guest VLAN option is globally enabled.

Port Configuration
The table has number of columns which allows you to configure the port mode based on IEEE 802.1X
standard. Select the port and configure the settings.

98
Port

The port number for which the configuration below applies.

Admin State

If NAS is globally enabled, this selection controls the port's authentication mode. The following modes are
available:

Force Authorized
In this mode, the switch will send one EAPOL Success frame when the port link comes up, and any client
on the port will be allowed network access without authentication.

Force Unauthorized
In this mode, the switch will send one EAPOL Failure frame when the port link comes up, and any client
on the port will be disallowed network access.

Port-based 802.1X
In the 802.1X-world, the user is called the supplicant, the switch is the authenticator, and the RADIUS
server is the authentication server. The authenticator acts as the man-in-the-middle, forwarding requests
and responses between the supplicant and the authentication server. Frames sent between the
supplicant and the switch are special 802.1X frames, known as EAPOL (EAP Over LANs) frames.

EAPOL frames encapsulate EAP PDUs (RFC3748). Frames sent between the switch and the RADIUS
server are RADIUS packets. RADIUS packets also encapsulate EAP PDUs together with other attributes
like the switch's IP address, name, and the supplicant's port number on the switch. EAP is very flexible, in
that it allows for different authentication methods, like MD5-CHALLENGE, PEAP, and TLS. The important
thing is that the authenticator (the switch) doesn't need to know which authentication method the
supplicant and the authentication server are using, or how many information exchange frames are
needed for a particular method. The switch simply encapsulates the EAP part of the frame into the
relevant type (EAPOL or RADIUS) and forwards it.
When authentication is complete, the RADIUS server sends a special packet containing a success or
failure indication. Besides forwarding this decision to the supplicant, the switch uses it to open up or block
traffic on the switch port connected to the supplicant.

Note: Suppose two backend servers are enabled and that the server timeout is configured to X seconds
(using the AAA configuration page), and suppose that the first server in the list is currently down (but not
considered dead). Now, if the supplicant retransmits EAPOL Start frames at a rate faster than X seconds,
then it will never get authenticated, because the switch will cancel on-going backend authentication
server requests whenever it receives a new EAPOL Start frame from the supplicant. And since the server
hasn't yet failed (because the X seconds haven't expired), the same server will be contacted upon the
next backend authentication server request from the switch. This scenario will loop forever. Therefore, the
server timeout should be smaller than the supplicant's EAPOL Start frame retransmission rate.

Single 802.1X
In port-based 802.1X authentication, once a supplicant is successfully authenticated on a port, the whole
port is opened for network traffic. This allows other clients connected to the port (for instance through a
hub) to piggy-back on the successfully authenticated client and get network access even though they
really aren't authenticated. To overcome this security breach, use the Single 802.1X variant.
Single 802.1X is really not an IEEE standard, but features many of the same characteristics as does
port-based 802.1X. In Single 802.1X, at most one supplicant can get authenticated on the port at a time.
Normal EAPOL frames are used in the communication between the supplicant and the switch. If more
than one supplicant is connected to a port, the one that comes first when the port's link comes up will be
the first one considered. If that supplicant doesn't provide valid credentials within a certain amount of time,
another supplicant will get a chance. Once a supplicant is successfully authenticated, only that supplicant
will be allowed access. This is the most secure of all the supported modes. In this mode, the Port Security
module is used to secure a supplicant's MAC address once successfully authenticated.

99
Multi 802.1X
Multi 802.1X is - like Single 802.1X - not an IEEE standard, but a variant that features many of the same
characteristics. In Multi 802.1X, one or more supplicants can get authenticated on the same port at the
same time. Each supplicant is authenticated individually and secured in the MAC table using the Port
Security module.
In Multi 802.1X it is not possible to use the multicast BPDU MAC address as destination MAC address
for EAPOL frames sent from the switch towards the supplicant, since that would cause all supplicants
attached to the port to reply to requests sent from the switch. Instead, the switch uses the supplicant's
MAC address, which is obtained from the first EAPOL Start or EAPOL Response Identity frame sent by
the supplicant. An exception to this is when no supplicants are attached. In this case, the switch sends
EAPOL Request Identity frames using the BPDU multicast MAC address as destination - to wake up any
supplicants that might be on the port.
The maximum number of supplicants that can be attached to a port can be limited using the Port
Security Limit Control functionality.MAC-based Auth.
Unlike port-based 802.1X, MAC-based authentication is not a standard, but merely a best-practices
method adopted by the industry. In MAC-based authentication, users are called clients, and the switch
acts as the supplicant on behalf of clients. The initial frame (any kind of frame) sent by a client is snooped
by the switch, which in turn uses the client's MAC address as both username and password in the
subsequent EAP exchange with the RADIUS server. The 6-byte MAC address is converted to a string on
the following form "xx-xx-xx-xx-xx-xx", that is, a dash (-) is used as separator between the lower-cased
hexadecimal digits. The switch only supports the MD5-Challenge authentication method, so the RADIUS
server must be configured accordingly.
When authentication is complete, the RADIUS server sends a success or failure indication, which in turn
causes the switch to open up or block traffic for that particular client, using the Port-Security module. Only
then will frames from the client be forwarded on the switch. There are no EAPOL frames involved in this
authentication, and therefore, MAC-based Authentication has nothing to do with the 802.1X standard.
The advantage of MAC-based authentication over 802.1X-based authentication is that the clients don't
need special supplicant software to authenticate. The disadvantage is that MAC addresses can be
spoofed by malicious users - equipment whose MAC address is a valid RADIUS user can be used by
anyone. Also, only the MD5-Challenge method is supported. The maximum number of clients that can be
attached to a port can be limited using the Port Security Limit Control functionality.

RADIUS-Assigned QoS Enabled

When RADIUS-Assigned QoS is both globally enabled and enabled (checked) on a given port, the switch
reacts to QoS Class information carried in the RADIUS Access-Accept packet transmitted by the RADIUS
server when a supplicant is successfully authenticated. If present and valid, traffic received on the
supplicant's port will be classified to the given QoS Class. If (re-)authentication fails or the RADIUS
Access-Accept packet no longer carries a QoS Class or it's invalid, or the supplicant is otherwise no
longer present on the port, the port's QoS Class is immediately reverted to the original QoS Class (which
may be changed by the administrator in the meanwhile without affecting the RADIUS-assigned).
This option is only available for single-client modes, i.e.
• Port-based 802.1X
• Single 802.1X0ˋ

RADIUS attributes used in identifying a QoS Class:


The User-Priority-Table attribute defined in RFC4675 forms the basis for identifying the QoS Class in an
Access-Accept packet.
Only the first occurrence of the attribute in the packet will be considered, and to be valid, it must follow
this rule:
• All 8 octets in the attribute's value must be identical and consist of ASCII characters in the range '0' - '3',
which translates into the desired QoS Class in the range [0; 3].

RADIUS-Assigned VLAN Enabled

When RADIUS-Assigned VLAN is both globally enabled and enabled (checked) for a given port, the
switch reacts to VLAN ID information carried in the RADIUS Access-Accept packet transmitted by the
RADIUS server when a supplicant is successfully authenticated. If present and valid, the port's Port VLAN

100
ID will be changed to this VLAN ID, the port will be set to be a member of that VLAN ID, and the port will
be forced into VLAN unaware mode. Once assigned, all traffic arriving on the port will be classified and
switched on the RADIUS-assigned VLAN ID.
If (re-)authentication fails or the RADIUS Access-Accept packet no longer carries a VLAN ID or it's invalid,
or the supplicant is otherwise no longer present on the port, the port's VLAN ID is immediately reverted to
the original VLAN ID (which may be changed by the administrator in the meanwhile without affecting the
RADIUS-assigned).
This option is only available for single-client modes, i.e.
• Port-based 802.1X
• Single 802.1X
For trouble-shooting VLAN assignments, use the "Monitor→VLANs→VLAN Membership and VLAN Port"
pages. These pages show which modules have (temporarily) overridden the current Port VLAN
configuration.

RADIUS attributes used in identifying a VLAN ID:


RFC2868 and RFC3580 form the basis for the attributes used in identifying a VLAN ID in an
Access-Accept packet. The following criteria are used:
• The Tunnel-Medium-Type, Tunnel-Type, and Tunnel-Private-Group-ID attributes must all be present at
least once in the Access-Accept packet.
• The switch looks for the first set of these attributes that have the same Tag value and fulfil the following
requirements (if Tag == 0 is used, the Tunnel-Private-Group-ID does not need to include a Tag):
- Value of Tunnel-Medium-Type must be set to "IEEE-802" (ordinal 6).
- Value of Tunnel-Type must be set to "VLAN" (ordinal 13).
- Value of Tunnel-Private-Group-ID must be a string of ASCII chars in the range '0' - '9', which is
interpreted as a decimal string representing the VLAN ID. Leading '0's are discarded. The final value must
be in the range [1; 4095].

Guest VLAN Enabled

When Guest VLAN is both globally enabled and enabled (checked) for a given port, the switch considers
moving the port into the Guest VLAN according to the rules outlined below.
This option is only available for EAPOL-based modes, i.e.:
• Port-based 802.1X
• Single 802.1X
• Multi 802.1X
For trouble-shooting VLAN assignments, use the "Monitor→VLANs→VLAN Membership and VLAN Port"
pages. These pages show which modules have (temporarily) overridden the current Port VLAN
configuration.

Guest VLAN Operation:


When a Guest VLAN enabled port's link comes up, the switch starts transmitting EAPOL Request Identity
frames. If the number of transmissions of such frames exceeds Max,. Reauth., Count and no EAPOL
frames have been received in the meanwhile, the switch considers entering the Guest VLAN. The interval
between transmission of EAPOL Request Identity frames is configured with EAPOL Timeout. If

Allow guest VLAN if EAPOL Seen is enabled, the port will now be placed in the Guest VLAN. If disabled,
the switch will first check its history to see if an EAPOL frame has previously been received on the port
(this history is cleared if the port link goes down or the port's Admin State is changed), and if not, the port
will be placed in the Guest VLAN. Otherwise it will not move to the Guest VLAN, but continue transmitting
EAPOL Request Identity frames at the rate given by EAPOL Timeout.
Once in the Guest VLAN, the port is considered authenticated, and all attached clients on the port are
allowed access on this VLAN. The switch will not transmit an EAPOL Success frame when entering the
Guest VLAN.
While in the Guest VLAN, the switch monitors the link for EAPOL frames, and if one such frame is
received, the switch immediately takes the port out of the Guest VLAN and starts authenticating the
supplicant according to the port mode. If an EAPOL frame is received, the port will never be able to go
back into the Guest VLAN if the "Allow Guest VLAN if EAPOL Seen" is disabled.

Port State

101
The current state of the port. It can undertake one of the following values:
Globally Disabled: NAS is globally disabled.
Link Down: NAS is globally enabled, but there is no link on the port.
Authorized: The port is in Force Authorized or a single-supplicant mode and the supplicant is authorized.
Unauthorized: The port is in Force Unauthorized or a single-supplicant mode and the supplicant is not
successfully authorized by the RADIUS server.
X Auth/Y Unauth: The port is in a multi-supplicant mode. Currently X clients are authorized and Y are
unauthorized.

Restart

Two buttons are available for each row. The buttons are only enabled when authentication is globally
enabled and the port's Admin State is in an EAPOL-based or MAC-based mode.
Clicking these buttons will not cause settings changed on the page to take effect.
Reauthenticate: Schedules a re-authentication whenever the quiet-period of the port runs out
(EAPOL-based authentication).For MAC-based authentication, re-authentication will be attempted
immediately.
The button only has effect for successfully authenticated clients on the port and will not cause the clients
to get temporarily unauthorized.
Reinitialize: Forces a re-initialization of the clients on the port and thereby a re-authentication
immediately. The clients will transfer to the unauthorized state while the re-authentication is in progress.

Buttons

Refresh: Click to refresh the page.

Save: Click to save changes.

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

4.2.3. Security / Network / Access Control List Configuration


Configure the ACL parameters (ACE) of each switch port. These parameters will affect frames received
on a port unless the frame matches a specific ACE.

The settings relate to the currently selected stack unit, as reflected by the page header.

Port

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

Policy ID

Select the policy to apply to this port. The allowed values are 0 through 255. The default value is 0.

Action

Select whether forwarding is permitted ("Permit") or denied ("Deny"). The default value is "Permit".

Rate Limiter ID

Select which rate limiter to apply on this port. The allowed values are Disabled or the values 1 through 16.
The default value is "Disabled".

Select DisabledPort Copy

Select which port frames are copied on. The allowed values are Disabled or a specific port number. The
default value is "Disabled".

Mirror

Specify the mirror operation of this port. The allowed values are:
Enabled: Frames received on the port are mirrored.
Disabled: Frames received on the port are not mirrored.
The default value is "Disabled".

Logging

Specify the logging operation of this port. The allowed values are:
Enabled: Frames received on the port are stored in the System Log.
Disabled: Frames received on the port are not logged.
The default value is "Disabled". Please note that the System Log memory size and logging rate is limited.

Shutdown

Specify the port shut down operation of this port. The allowed values are:
Enabled: If a frame is received on the port, the port will be disabled.
Disabled: Port shut down is disabled.
The default value is "Disabled".

Counter

Counts the number of frames that match this ACE.

Buttons

Save: Click to save changes.

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

Refresh: Click to refresh the page. Any changes made locally will be undone..

Clear: Click to clear the counter

ACL Rate Limiters Configuration


Configure the rate limiter for the ACL of the switch

103
Rate Limiter ID

The rate limiter ID for the settings contained in the same row.

Rate

The allowed values are: 0-3276700 in pps

Or 0,100,200,300,…,1000000 in kbps.

Unit

Specify the rate unit. The allowed values are:


pps: packets per second.
kbps: Kbits per second.

Buttons

Save: Click to save changes.

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

104
Access Control List Configuration
This page shows the Access Control List (ACL), which is made up of the ACEs defined on this switch.
Each row describes the ACE that is defined. The maximum number of ACEs is 256 on each switch.

Click on the lowest plus sign to add a new ACE to the list. The reserved ACEs used for internal protocol,
cannot be edited or deleted, the order sequence cannot be changed and the priority is highest.

Ingress Port

Indicates the ingress port of the ACE. Possible values are:


All: The ACE will match all ingress port.
Port: The ACE will match a specific ingress port.

Policy / Bitmask

Indicates the policy number and bitmask of the ACE.

Frame Type

Indicates the frame type of the ACE. Possible values are:

Any: The ACE will match any frame type.

EType: The ACE will match Ethernet Type frames. Note that an Ethernet Type based ACE will not get
matched by IP and ARP frames.

ARP: The ACE will match ARP/RARP frames.

IPv4: The ACE will match all IPv4 frames.


IPv4/ICMP: The ACE will match IPv4 frames with ICMP protocol.
IPv4/UDP: The ACE will match IPv4 frames with UDP protocol.
IPv4/TCP: The ACE will match IPv4 frames with TCP protocol.
IPv4/Other: The ACE will match IPv4 frames, which are not ICMP/UDP/TCP.

IPv6: The ACE will match all IPv6 standard frames.

Action

Indicates the forwarding action of the ACE.

Permit:: Frames matching the ACE may be forwarded and learned.

Deny: Frames matching the ACE are dropped.

Rate Limiter

105
Indicates the rate limiter number of the ACE. The allowed range is 1 to 16. When Disabled is displayed,
the rate limiter operation is disabled.

Port Copy

Indicates the port copy operation of the ACE. Frames matching the ACE are copied to the port number.
The allowed values are Disabled or a specific port number. When Disabled is displayed, the port copy
operation is disabled.

Mirror

Specify the mirror operation of this port. Frames matching the ACE are mirrored to the destination mirror
port. The allowed values are:
Enabled: Frames received on the port are mirrored.
Disabled: Frames received on the port are not mirrored.
The default value is "Disabled".

Counter

The counter indicates the number of times the ACE was hit by a frame.

Modification Buttons

You can modify each ACE (Access Control Entry) in the table using the following buttons:

: Inserts a new ACE before the current row.

: Edits the ACE row.

: Moves the ACE up the list.

: Moves the ACE down the list.

: Deletes the ACE.

: The lowest plus sign adds a new entry at the bottom of the ACE listings.

Buttons

Auto-refresh: Check this box to refresh the page automatically. Automatic refresh occurs at regular
intervals.

Refresh: Click to refresh the page. Note that non-committed changes will be lost.

Clear: Click to clear the counter

Remove All: Click to remove all ACEs

ACE Configuration
Configure an ACE (Access Control Entry) on this page.

An ACE consists of several parameters. These parameters vary according to the frame type that you
select. First select the ingress port for the ACE, and then select the frame type. Different parameter
options are displayed depending on the frame type selected.

A frame that hits this ACE matches the configuration that is defined here.

106
Ingress Port

Select the ingress port for which this ACE applies.


All: The ACE applies to all port.
Port n: The ACE applies to this port number, where n is the number of the switch port. You can select one
port or select multiple ports for the entry.

Policy Filter

Specify the policy number filter for this ACE. The policy ID should be the same when you want apply it to
the ACL or Port.
Any: No policy filter is specified. (policy filter status is "don't-care".)
Specific: If you want to filter a specific policy with this ACE, choose this value. Two field for entering an
policy value and bitmask appears.

Policy Value

When "Specific" is selected for the policy filter, you can enter a specific policy value. The allowed range is
0 to 255.

Policy Bitmask

When "Specific" is selected for the policy filter, you can enter a specific policy bitmask. The allowed range
is 0x0 to 0xff.

Select the switch to which this ACE applies. This parameter is reserved to the Stacking model. If the
switch doesn't support stacking, the parameter will not display here.
Any: The ACE applies to any port.
Switch n: The ACE applies to this switch number, where n is the number of the switch.

Frame Type

Select the frame type for this ACE. These frame types are mutually exclusive.
Any: Any frame can match this ACE.
Ethernet Type: Only Ethernet Type frames can match this ACE. The IEEE 802.3 describes the value of

107
Length/Type Field specifications to be greater than or equal to 1536 decimal (equal to 0600 hexadecimal).
ARP: Only ARP frames can match this ACE. Notice the ARP frames won't match the ACE with ethernet
type.
IPv4: Only IPv4 frames can match this ACE. Notice the IPv4 frames won't match the ACE with ethernet
type.

IPv6: Only IPv6 frames can match this ACE. Notice the IPv6 frames won't match the ACE with ehternet
type.

Action

Specify the action to take with a frame that hits this ACE.
Permit: The frame that hits this ACE is granted permission for the ACE operation.
Deny: The frame that hits this ACE is dropped.

Rate Limiter

Specify the rate limiter in number of base units. The allowed range is 1 to 16. Disabled indicates that the
rate limiter operation is disabled.

Select Port Copy

Frames that hit the ACE are copied to the port number specified here. The allowed range is the same as
the switch port number range. Disabled indicates that the port copy operation is disabled.

Mirror

Specify the mirror operation of this port. Frames matching the ACE are mirrored to the destination mirror
port. The allowed values are:
Enabled: Frames received on the port are mirrored.
Disabled: Frames received on the port are not mirrored.
The default value is "Disabled".

Logging

Specify the logging operation of the ACE. The allowed values are:
Enabled: Frames matching the ACE are stored in the System Log.
Disabled: Frames matching the ACE are not logged.
Please note that the System Log memory size and logging rate is limited.

Shutdown

Specify the port shut down operation of the ACE. The allowed values are:
Enabled: If a frame matches the ACE, the ingress port will be disabled.
Disabled: Port shut down is disabled for the ACE.

Counter

The counter indicates the number of times the ACE was hit by a frame.

MAC Parameters

SMAC Filter

(Only displayed when the frame type is Ethernet Type or ARP.)


Specify the source MAC filter for this ACE.
Any: No SMAC filter is specified. (SMAC filter status is "don't-care".)
Specific: If you want to filter a specific source MAC address with this ACE, choose this value. A field for
entering an SMAC value appears.

108
SMAC Value

When "Specific" is selected for the SMAC filter, you can enter a specific source MAC address. The legal
format is "xx-xx-xx-xx-xx-xx". A frame that hits this ACE matches this SMAC value.

DMAC Filter

Specify the destination MAC filter for this ACE.


Any: No DMAC filter is specified. (DMAC filter status is "don't-care".)
MC: Frame must be multicast.
BC: Frame must be broadcast.
UC: Frame must be unicast.
Specific: If you want to filter a specific destination MAC address with this ACE, choose this value. A field
for entering a DMAC value appears.

DMAC Value

When "Specific" is selected for the DMAC filter, you can enter a specific destination MAC address. The
legal format is "xx-xx-xx-xx-xx-xx". A frame that hits this ACE matches this DMAC value.

VLAN Parameters

802.1Q Tagged

Specify whether frames can hit the action according to the 802.1Q tagged. The allowed values are:
Any: Any value is allowed ("don't-care").
Enabled: Tagged frame only.
Disabled: Untagged frame only.
The default value is "Any".

VLAN ID Filter

Specify the VLAN ID filter for this ACE.


Any: No VLAN ID filter is specified. (VLAN ID filter status is "don't-care".)
Specific: If you want to filter a specific VLAN ID with this ACE, choose this value. A field for entering a
VLAN ID number appears.

VLAN ID

When "Specific" is selected for the VLAN ID filter, you can enter a specific VLAN ID number. The allowed
range is 1 to 4095. A frame that hits this ACE matches this VLAN ID value.

Tag Priority

Specify the tag priority for this ACE. A frame that hits this ACE matches this tag priority. The allowed
number range is 0 to 7. The value Any means that no tag priority is specified (tag priority is "don't-care".)

ARP Parameters

The ARP parameters can be configured when Frame Type "ARP" is selected.

ARP/RARP

Specify the available ARP/RARP opcode (OP) flag for this ACE.

109
Any: No ARP/RARP OP flag is specified. (OP is "don't-care".)
ARP: Frame must have ARP/RARP opcode set to ARP.
RARP: Frame must have ARP/RARP opcode set to RARP.
Other: Frame has unknown ARP/RARP Opcode flag.

Request/Reply

Specify the available ARP/RARP opcode (OP) flag for this ACE.
Any: No ARP/RARP OP flag is specified. (OP is "don't-care".)
Request: Frame must have ARP Request or RARP Request OP flag set.
Reply: Frame must have ARP Reply or RARP Reply OP flag.

Sender IP Filter

Specify the sender IP filter for this ACE.


Any: No sender IP filter is specified. (Sender IP filter is "don't-care".)
Host: Sender IP filter is set to Host. Specify the sender IP address in the SIP Address field that appears.
Network: Sender IP filter is set to Network. Specify the sender IP address and sender IP mask in the SIP
Address and SIP Mask fields that appear.

Sender IP Address

When "Host" or "Network" is selected for the sender IP filter, you can enter a specific sender IP address in
dotted decimal notation.

Sender IP Mask

When "Network" is selected for the sender IP filter, you can enter a specific sender IP mask in dotted
decimal notation.

Target IP Filter

Specify the target IP filter for this specific ACE.


Any: No target IP filter is specified. (Target IP filter is "don't-care".)
Host: Target IP filter is set to Host. Specify the target IP address in the Target IP Address field that
appears.
Network: Target IP filter is set to Network. Specify the target IP address and target IP mask in the Target
IP Address and Target IP Mask fields that appear.

Target IP Address

When "Host" or "Network" is selected for the target IP filter, you can enter a specific target IP address in
dotted decimal notation.

Target IP Mask

When "Network" is selected for the target IP filter, you can enter a specific target IP mask in dotted
decimal notation.

ARP SMAC Match

Specify whether frames can hit the action according to their sender hardware address field (SHA) settings.
0: ARP frames where SHA is not equal to the SMAC address.
1: ARP frames where SHA is equal to the SMAC address.
Any: Any value is allowed ("don't-care").

RARP DMAC Match

Specify whether frames can hit the action according to their target hardware address field (THA) settings.
0: RARP frames where THA is not equal to the DMAC address.
1: RARP frames where THA is equal to the DMAC address.
Any: Any value is allowed ("don't-care").

110
IP/Ethernet Length

Specify whether frames can hit the action according to their ARP/RARP hardware address length (HLN)
and protocol address length (PLN) settings.
0: ARP/RARP frames where the HLN is not equal to Ethernet (0x06) or the (PLN) is not equal to IPv4
(0x04).
1: ARP/RARP frames where the HLN is equal to Ethernet (0x06) and the (PLN) is equal to IPv4 (0x04).
Any: Any value is allowed ("don't-care").

IP

Specify whether frames can hit the action according to their ARP/RARP hardware address space (HRD)
settings.
0: ARP/RARP frames where the HLD is not equal to Ethernet (1).
1: ARP/RARP frames where the HLD is equal to Ethernet (1).
Any: Any value is allowed ("don't-care").

Ethernet

Specify whether frames can hit the action according to their ARP/RARP protocol address space (PRO)
settings.
0: ARP/RARP frames where the PRO is not equal to IP (0x800).
1: ARP/RARP frames where the PRO is equal to IP (0x800).
Any: Any value is allowed ("don't-care").

IP Parameters
The IP parameters can be configured when Frame Type "IPv4" is selected.

IP Protocol Filter

Specify the IP protocol filter for this ACE.


Any: No IP protocol filter is specified ("don't-care").
Specific: If you want to filter a specific IP protocol filter with this ACE, choose this value. A field for
entering an IP protocol filter appears.
ICMP: Select ICMP to filter IPv4 ICMP protocol frames. Extra fields for defining ICMP parameters will
appear. These fields are explained later in this help file.
UDP: Select UDP to filter IPv4 UDP protocol frames. Extra fields for defining UDP parameters will appear.
These fields are explained later in this help file.
TCP: Select TCP to filter IPv4 TCP protocol frames. Extra fields for defining TCP parameters will appear.
These fields are explained later in this help file.

IP Protocol Value

When "Specific" is selected for the IP protocol value, you can enter a specific value. The allowed range is
0 to 255. A frame that hits this ACE matches this IP protocol value.

IP TTL

Specify the Time-to-Live settings for this ACE.


zero: IPv4 frames with a Time-to-Live field greater than zero must not be able to match this entry.
non-zero: IPv4 frames with a Time-to-Live field greater than zero must be able to match this entry.
Any: Any value is allowed ("don't-care").

IP Fragment

Specify the fragment offset settings for this ACE. This involves the settings for the More Fragments (MF)
bit and the Fragment Offset (FRAG OFFSET) field for an IPv4 frame.
No: IPv4 frames where the MF bit is set or the FRAG OFFSET field is greater than zero must not be able
to match this entry.

111
Yes: IPv4 frames where the MF bit is set or the FRAG OFFSET field is greater than zero must be able to
match this entry.
Any: Any value is allowed ("don't-care").

IP Option

Specify the options flag setting for this ACE.


No: IPv4 frames where the options flag is set must not be able to match this entry.
Yes: IPv4 frames where the options flag is set must be able to match this entry.
Any: Any value is allowed ("don't-care").

SIP Filter

Specify the source IP filter for this ACE.


Any: No source IP filter is specified. (Source IP filter is "don't-care".)
Host: Source IP filter is set to Host. Specify the source IP address in the SIP Address field that appears.
Network: Source IP filter is set to Network. Specify the source IP address and source IP mask in the SIP
Address and SIP Mask fields that appear.

SIP Address

When "Host" or "Network" is selected for the source IP filter, you can enter a specific SIP address in
dotted decimal notation.

SIP Mask

When "Network" is selected for the source IP filter, you can enter a specific SIP mask in dotted decimal
notation.

DIP Filter

Specify the destination IP filter for this ACE.


Any: No destination IP filter is specified. (Destination IP filter is "don't-care".)
Host: Destination IP filter is set to Host. Specify the destination IP address in the DIP Address field that
appears.
Network: Destination IP filter is set to Network. Specify the destination IP address and destination IP
mask in the DIP Address and DIP Mask fields that appear.

DIP Address

When "Host" or "Network" is selected for the destination IP filter, you can enter a specific DIP address in
dotted decimal notation.

DIP Mask

When "Network" is selected for the destination IP filter, you can enter a specific DIP mask in dotted
decimal notation.

ICMP Parameters

ICMP Type Filter

Specify the ICMP filter for this ACE.


Any: No ICMP filter is specified (ICMP filter status is "don't-care").
Specific: If you want to filter a specific ICMP filter with this ACE, you can enter a specific ICMP value. A
field for entering an ICMP value appears.

ICMP Type Value

When "Specific" is selected for the ICMP filter, you can enter a specific ICMP value. The allowed range
is0 to 255. A frame that hits this ACE matches this ICMP value.

112
ICMP Code Filter

Specify the ICMP code filter for this ACE.


Any: No ICMP code filter is specified (ICMP code filter status is "don't-care").
Specific: If you want to filter a specific ICMP code filter with this ACE, you can enter a specific ICMP code
value. A field for entering an ICMP code value appears.

ICMP Code Value

When "Specific" is selected for the ICMP code filter, you can enter a specific ICMP code value. The
allowed range is 0 to 255. A frame that hits this ACE matches this ICMP code value.

TCP/UDP Parameters

TCP/UDP Source Filter

Specify the TCP/UDP source filter for this ACE.


Any: No TCP/UDP source filter is specified (TCP/UDP source filter status is "don't-care").
Specific: If you want to filter a specific TCP/UDP source filter with this ACE, you can enter a specific
TCP/UDP source value. A field for entering a TCP/UDP source value appears.
Range: If you want to filter a specific TCP/UDP source range filter with this ACE, you can enter a specific
TCP/UDP source range value. A field for entering a TCP/UDP source value appears.

TCP/UDP Source No.

When "Specific" is selected for the TCP/UDP source filter, you can enter a specific TCP/UDP source
value. The allowed range is 0 to 65535. A frame that hits this ACE matches this TCP/UDP source value.

TCP/UDP Source Range

When "Range" is selected for the TCP/UDP source filter, you can enter a specific TCP/UDP source range
value. The allowed range is 0 to 65535. A frame that hits this ACE matches this TCP/UDP source value.

TCP/UDP Destination Filter

Specify the TCP/UDP destination filter for this ACE.


Any: No TCP/UDP destination filter is specified (TCP/UDP destination filter status is "don't-care").
Specific: If you want to filter a specific TCP/UDP destination filter with this ACE, you can enter a specific
TCP/UDP destination value. A field for entering a TCP/UDP destination value appears.
Range: If you want to filter a specific range TCP/UDP destination filter with this ACE, you can enter a
specific TCP/UDP destination range value. A field for entering a TCP/UDP destination value appears.

TCP/UDP Destination Number

When "Specific" is selected for the TCP/UDP destination filter, you can enter a specific TCP/UDP
destination value. The allowed range is 0 to 65535. A frame that hits this ACE matches this TCP/UDP
destination value.

TCP/UDP Destination Range

When "Range" is selected for the TCP/UDP destination filter, you can enter a specific TCP/UDP
destination range value. The allowed range is 0 to 65535. A frame that hits this ACE matches this
TCP/UDP destination value.

TCP FIN

Specify the TCP "No more data from sender" (FIN) value for this ACE.
0: TCP frames where the FIN field is set must not be able to match this entry.

113
1: TCP frames where the FIN field is set must be able to match this entry.
Any: Any value is allowed ("don't-care").

TCP SYN

Specify the TCP "Synchronize sequence numbers" (SYN) value for this ACE.
0: TCP frames where the SYN field is set must not be able to match this entry.
1: TCP frames where the SYN field is set must be able to match this entry.
Any: Any value is allowed ("don't-care").

TCP RST

Specify the TCP "Reset the connection" (RST) value for this ACE.
0: TCP frames where the RST field is set must not be able to match this entry.
1: TCP frames where the RST field is set must be able to match this entry.
Any: Any value is allowed ("don't-care").

TCP PSH

Specify the TCP "Push Function" (PSH) value for this ACE.
0: TCP frames where the PSH field is set must not be able to match this entry.
1: TCP frames where the PSH field is set must be able to match this entry.
Any: Any value is allowed ("don't-care").

TCP ACK

Specify the TCP "Acknowledgment field significant" (ACK) value for this ACE.
0: TCP frames where the ACK field is set must not be able to match this entry.
1: TCP frames where the ACK field is set must be able to match this entry.
Any: Any value is allowed ("don't-care").

TCP URG

Specify the TCP "Urgent Pointer field significant" (URG) value for this ACE.
0: TCP frames where the URG field is set must not be able to match this entry.
1: TCP frames where the URG field is set must be able to match this entry.
Any: Any value is allowed ("don't-care").

Ethernet Type Parameters


The Ethernet Type parameters can be configured when Frame Type "Ethernet Type" is
selected.

EtherType Filter

Specify the Ethernet type filter for this ACE.


Any: No EtherType filter is specified (EtherType filter status is "don't-care").
Specific: If you want to filter a specific EtherType filter with this ACE, you can enter a specific EtherType
value. A field for entering a EtherType value appears.

Ethernet Type Value

When "Specific" is selected for the EtherType filter, you can enter a specific EtherType value. The
allowed range is 0x600 to 0xFFFF but excluding 0x800(IPv4), 0x806(ARP) and 0x86DD (IPv6). A frame
that hits this ACE matches this EtherType value.

Buttons
Save: Click to save changes.
Reset: Click to undo any changes made locally and revert to previously saved values.
Cancel: Return to the previous page.

114
4.4.2.4 Switch / Network / DHCP Configuration

DHCP Snooping Configuration

Configure DHCP Snooping on this page.

Snooping Mode

Indicates the DHCP snooping mode operation. Possible modes are:


Enabled: Enable DHCP snooping mode operation. When DHCP snooping mode operation is enabled,
the DHCP request messages will be forwarded to trusted ports and only allow reply packets from trusted
ports.
Disabled: Disable DHCP snooping mode operation.

Port Mode

Indicates the DHCP snooping port mode. Possible port modes are:
Trusted: Configures the port as trusted source of the DHCP messages.
Untrusted: Configures the port as untrusted source of the DHCP messages.

Buttons

Save: Click to save changes.


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

DHCP Relay Configuration

115
Configure DHCP Relay on this page.

Relay Mode

Indicates the DHCP relay mode operation. Possible modes are:


Enabled: Enable DHCP relay mode operation. When DHCP relay mode operation is enabled, the agent
forwards and transfers DHCP messages between the clients and the server when they are not in the
same subnet domain. And the DHCP broadcast message won't be flooded for security considerations.
Disabled: Disable DHCP relay mode operation.

Relay Server

Indicates the DHCP relay server IP address. A DHCP relay agent is used to forward and to transfer
DHCP messages between the clients and the server when they are not in the same subnet domain.

Relay Information Mode

Indicates the DHCP relay information mode option operation. The option 82 circuit ID format as
"[vlan_id][module_id][port_no]". The first four characters represent the VLAN ID, the fifth and sixth
characters are the module ID(in standalone device it always equal 0, in stackable device it means switch
ID). ), and the last two characters are the port number. For example, "00030108" means the DHCP
message receive form VLAN ID 3, switch ID 1, port No 8. And the option 82 remote ID value is equal the
switch MAC address.
Possible modes are:

Enabled: Enable DHCP relay information mode operation. When DHCP relay information
mode operation is enabled, the agent inserts specific information (option 82) into a DHCP

116
message when forwarding to DHCP server and removes it from a DHCP message when
transferring to DHCP client. It only works when DHCP relay operation mode is enabled.
Disabled: Disable DHCP relay information mode operation.

Relay Information Policy

Indicates the DHCP relay information option policy. When DHCP relay information mode operation is
enabled, if agent receives a DHCP message that already contains relay agent information it will enforce
the policy. And it only works under DHCP if relay information operation mode is enabled. Possible policies
are:
Replace: Replace the original relay information when a DHCP message that already contains it is
received.
Keep: Keep the original relay information when a DHCP message that already contains it is received.
Drop: Drop the package when a DHCP message that already contains relay information is received.

Buttons

Save: Click to save changes.

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

4.2.5. IP Source Guard Configuration


IP Source Guard Configuration

This page provides IP Source Guard related configuration.

117
Mode of IP Source Guard Configuration

Enable the Global IP Source Guard or disable the Global IP Source Guard. All configured ACEs will be
lost when the mode is enabled.

Port Mode Configuration

Specify IP Source Guard is enabled on which ports. Only when both Global Mode and Port Mode on a
given port are enabled, IP Source Guard is enabled on this given port.

Max Dynamic Clients

Specify the maximum number of dynamic clients that can be learned on given port. This value can be 0, 1,
2 or unlimited. If the port mode is enabled and the value of max dynamic client is equal to 0, it means only
allow the IP packets forwarding that are matched in static entries on the specific port.

Buttons

Save: Click to save changes.


Reset: Click to undo any changes made locally and revert to previously saved values.
Translate dynamic to static: Click to translate all dynamic entries to static entries.

Static IP Source Guard Table

Delete

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

Port

The logical port for the settings.

VLAN ID

The VLAN ID for the settings.

IP Address

Allowed Source IP address.


used MAC address

Allowed Source MAC address.

Adding new entry

Click to add a new entry to the Static IP Source Guard table. Specify the Port, VLAN ID, IP address, and
IP Mask for the new entry. Click "Save".

Buttons

Save: Click to save changes.

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

4.2.6. ARP Inspection


ARP Inspection

119
This page provides ARP Inspection related configuration.

120
Port Mode Configuration

Specify ARP Inspection is enabled on which ports. Only when both Global Mode and Port Mode on a
given port are enabled, ARP Inspection is enabled on this given port.

Buttons

Save: Click to save changes.


Reset: Click to undo any changes made locally and revert to previously saved values.
Translate dynamic to static: Click to translate all dynamic entries to static entries.

Static ARP Inspection Table

Delete

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

Port

The logical port for the settings.

VLAND ID

The VLAN ID for the settings.

121
MAC Address

Allowed Source MAC address in ARP request packets.

IP Address

Allowed Source IP address in ARP request packets.

Adding new entry

Click to add a new entry to the Static ARP Inspection table. Specify the Port, VLAN ID, MAC address, and
IP address for the new entry. Click "Save".

Buttons

Save: Click to save changes.


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

4.3. Security / AAA Authentication Server Configuration


This page allows you to configure the Authentication Servers.

Common Server Configuration


These setting are common for all of the Authentication Servers.

Timeout

The Timeout, which can be set to a number between 3 and 3600 seconds, is the maximum time to wait
for a reply from a server. If the server does not reply within this timeframe, we will consider it to be dead

122
and continue with the next enabled server (if any).

RADIUS servers are using the UDP protocol, which is unreliable by design. In order to cope with lost
frames, the timeout interval is divided into 3 subintervals of equal length. If a reply is not received within
the subinterval, the request is transmitted again. This algorithm causes the RADIUS server to be queried
up to 3 times before it is considered to be dead.

Dead Time

The Dead Time, which can be set to a number between 0 and 3600 seconds, is the period during which
the switch will not send new requests to a server that has failed to respond to a previous request. This will
stop the switch from continually trying to contact a server that it has already determined as dead.
Setting the Dead Time to a value greater than 0 (zero) will enable this feature, but only if more than one
server has been configured.

RADIUS Authentication Server Configuration


The table has one row for each RADIUS Authentication Server and a number of columns, which
are:

The RADIUS Authentication Server number for which the configuration below applies.

Enabled

Enable the RADIUS Authentication Server by checking this box.

IP Address/Hostname

The IP address or hostname of the RADIUS Authentication Server. IP address is expressed in dotted

decimal notation.

Port

The UDP port to use on the RADIUS Authentication Server. If the port is set to 0 (zero), the default port

(1812) is used on the RADIUS Authentication Server.

Secret

The secret - up to 29 characters long - shared between the RADIUS Authentication Server and the switch.

RADIUS Accounting Server Configuration


The table has one row for each RADIUS Accounting Server and a number of columns, which are:

The RADIUS Accounting Server number for which the configuration below applies.

Enabled

Enable the RADIUS Accounting Server by checking this box.

123
IP Address/Hostname

The IP address or hostname of the RADIUS Accounting Server. IP address is expressed in dotted decimal

notation.

Port

The UDP port to use on the RADIUS Accounting Server. If the port is set to 0 (zero), the default port (1813)

is used on the RADIUS Accounting Server.

Secret

The secret - up to 29 characters long - shared between the RADIUS Accounting Server and the switch.

TACACS+ Authentication Server Configuration


The table has one row for each TACACS+ Authentication Server and a number of columns, which are:

The TACACS+ Authentication Server number for which the configuration below applies.

Enabled

Enable the TACACS+ Authentication Server by checking this box.

IP Address/Hostname

The IP address or hostname of the TACACS+ Authentication Server. IP address is expressed in dotted

decimal notation.

Port

The TCP port to use on the TACACS+ Authentication Server. If the port is set to 0 (zero), the default port

(49) is used on the TACACS+ Authentication Server.

Secret

The secret - up to 29 characters long - shared between the TACACS+ Authentication Server and the

switch.

Buttons

Save: Click to save changes.

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

124
5. Aggregation Configuration
Link Aggregation is also known as Port Trunking. It allows user using multiple ports in parallel to
increase the link speed beyond the limits of a port and to increase the redundancy for higher
availability. The switch support both Static and Dynamic link aggregation, LACP. The switch
also supports different Hash mechanism to forward traffic according to the MAC address or IP,
Protocol Port Number.

5.1 Static Aggregation


This page is used to configure the Aggregation hash mode and the aggregation group.

The aggregation hash mode settings are global, whereas the aggregation group relate to the
currently selected stack unit, as reflected by the page header.

Hash Code Contributors

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.

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 Address

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

TCP/UDP Port Number

The TCP/UDP port number can be used to calculate the destination port for the frame. Check to enable

the use of the TCP/UDP Port Number, or uncheck to disable. By default, TCP/UDP Port Number is

enabled.

Aggregation Group Configuration

Group ID

Indicates the group ID for the settings contained in the same row. Group ID "Normal" indicates there is no

aggregation. Only one group ID is valid per port.

Port Members

Each switch port is listed for each group ID. Select a radio button to include a port in an aggregation, or

clear the radio button to remove the port from the aggregation. By default, no ports belong to any

aggregation group. Only full duplex ports can join an aggregation and ports must be in the same speed in

each group.

Buttons

Save: Click to save changes.

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

5.2 LACP - Dynamic Aggregation


This page allows the user to inspect the current LACP port configurations, and possibly change them as
well.

126
Port

The switch port number.

LACP Enabled

Controls whether LACP is enabled on this switch port. LACP will form an aggregation when 2 or more
ports are connected to the same partner. LACP can form max 12 LLAGs per switch and 2 GLAGs per
stack.

Key

The Key value incurred by the port, range 1-65535 . The Auto setting will set the key as appropriate by the
physical link speed, 10Mb = 1, 100Mb = 2, 1Gb = 3. Using the Specific setting, a user-defined value can
be entered. Ports with the same Key value can participate in the same aggregation group, while ports with
different keys cannot.

Role

The Role shows the LACP activity status. The Active will transmit LACP packets each second, while
Passive will wait for a LACP packet from a partner (speak if spoken to).

Buttons

Save: Click to save changes.

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

127
6. Loop Protection
This page allows the user to inspect the current Loop Protection configurations, and possibly
change them as well. The loop protection feature is very important to protect the unexpected
network loop, especially when you install the switch on the internet. The incorrect installation,
failure media, or hacker attacking may create network loop.

The switch supports the Loop Protection feature, the port can be shut down or log information
per your configuration when the switch do detect the network loop. After the port is shutdown, it
may hard to manually reconnect it, so that there is a shutdown time timeout design can help
re-enable the port link automatically. With the Loop Protection feature, it can help you to avoid
the failure and protect your network.

General Settings

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

128
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. The valid values are:

Shutdown Port: Shutdown the port until the Shutdown Time timeout.

Shutdown Port and Log: Shutdown the port and log the status.

Log Only: Only log the status.

Tx Mode

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

Button

Save: Click to save changes.


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

129
7. Spanning Tree
The switch supports Multiple Spanning Tree Protocol (MSTP), Rapid Spanning Tree Protocol
(RSTP) and Legacy Spanning Tree Protocol (STP).

The STP and RSTP is combined and defined in IEEE 802.1D-2004, Rapid Spanning Tree
Protocol. The RSTP protocol is applied to single network domain no matter how many VLANs in
your network. In RSTP domain, one of the switch acts as the Root Switch and block one of the
link with highest path cost to avoid network loop. There are maximum 23 level switches within
one RSTP domain, the network size may be limited.

Multiple Spanning Tree Protocol (MSTP) is a direct extension of RSTP. It can provide an
independent spanning tree for different VLANs. With the Spanning Tree and VLAN mapping,
each VLAN has its own root and blocking path, the STP region size becomes lower, the
convergence time of topology change becomes faster as well.

There are some important abbreviation as below.

Common Spanning Tree (CST): Common Spanning Tree (CST) interconnects all adjacent
MST regions and acts as a virtual bridge node for communications with STP or RSTP nodes in
the global network.

Common and Internal Spanning Tree (CIST): MSTP connects all bridges and LAN segments
with a single Common and Internal Spanning Tree (CIST). The CIST is formed as a result of the
running spanning tree algorithm between switches that support the STP, RSTP, MSTP
protocols.

MSTI: Multiple Spanning Tree Instance: One VLAN can be mapped to a MSTI. Each instance
has its own root switch, forwarding path, blocking path and table. An MST Region may contain
multiple MSTI.

7.1. Spanning Tree / Bridge Setting


This page allows you to configure STP system settings. The settings are used by all STP Bridge
instances in the Switch.

130
Basic Settings

Protocol Version

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

Bridge Priority

Controls the bridge priority. Lower numeric values have better priority. The bridge priority plus the MSTI
instance number, concatenated with the 6-byte MAC address of the switch forms a Bridge Identifier.
For MSTP operation, this is the priority of the CIST. Otherwise, this is the priority of the STP/RSTP bridge.

Forward Delay

The delay used by STP Bridges to transit Root and Designated Ports to Forwarding (used in STP
compatible mode). Valid values are in the range 4 to 30 seconds.

Max Age

The maximum age of the information transmitted by the Bridge when it is the Root Bridge. Valid values are
in the range 6 to 40 seconds, and MaxAge must be <= (FwdDelay-1)*2.

Maximum Hop Count

This defines the initial value of remaining Hops for MSTI information generated at the boundary of an
MSTI region. It defines how many bridges a root bridge can distribute its BPDU information to. Valid
values are in the range 6 to 40 hops.

Transmit Hold Count

131
The number of BPDU's a bridge port can send per second. When exceeded, transmission of the next
BPDU will be delayed. Valid values are in the range 1 to 10 BPDU's per second.

Advanced Settings

This section descript the advanced settings of the Spanning Tree Protocol.

Edge Port BPDU Filtering

Control whether a port explicitly configured as Edge will transmit and receive BPDUs.

Edge Port BPDU Guard

Control whether a port explicitly configured as Edge will disable itself upon reception of a BPDU. The port
will enter the error-disabled state, and will be removed from the active topology.

Port Error Recovery

Control whether a port in the error-disabled state automatically will be enabled after a certain time. If
recovery is not enabled, ports have to be disabled and re-enabled for normal STP operation. The condition
is also cleared by a system reboot.

Port Error Recovery Timeout

The time to pass before a port in the error-disabled state can be enabled. Valid values are between 30 and
86400 seconds (24 hours).

Buttons

Save: Click to save changes.

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

7.2 Spanning Tree / MSTI Mapping


This page allows the user to inspect the current STP MSTI bridge instance priority configurations, and
possibly change them as well.

132
Configuration Identification

Configuration Name

The name identifying the VLAN to MSTI mapping. Bridges must share the name and revision (see below),
as well as the VLAN-to-MSTI mapping configuration in order to share spanning trees for MSTI's
(Intra-region). The name is at most 32 characters.

Configuration Revision

The revision of the MSTI configuration named above. This must be an integer between 0 and 65535.

MSTI Mapping

MSTI

The bridge instance. The CIST is not available for explicit mapping, as it will receive the VLANs not
explicitly mapped.

VLANs Mapped

The list of VLANs mapped to the MSTI. The VLANs must be separated with comma and/or space. A VLAN
can only be mapped to one MSTI. An unused MSTI should just be left empty. (I.e. not having any VLANs
mapped to it.)

Buttons

Save: Click to save changes.

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

133
7.3. Spanning Tree / MSTI Priorities
This page allows the user to inspect the current STP MSTI bridge instance priority configurations, and
possibly change them as well.

MSTI

The bridge instance. The CIST is the default instance, which is always active

Priority

Controls the bridge priority. Lower numeric values have better priority. The bridge priority plus the MSTI
instance number, concatenated with the 6-byte MAC address of the switch forms a Bridge Identifier.

Buttons

Save: Click to save changes.

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

134
7.4. Spanning Tree / CIST Ports

This page allows the user to inspect the current STP CIST port configurations, and possibly change them
as well.

This page contains settings for physical and aggregated ports.

The STP port settings relate to the currently selected stack unit, as reflected by the page header.

Port

The switch port number of the logical STP port.

STP Enabled

Controls whether STP is enabled on this switch port.

Path Cost

Controls the path cost incurred by the port.

The Auto setting will set the path cost as appropriate by the physical link speed, using the 802.1D
recommended values.

Using the Specific setting, a user-defined value can be entered. The path cost is used when establishing
the active topology of the network. Lower path cost ports are chosen as forwarding ports in favor of higher
path cost ports. Valid values are in the range 1 to 200000000.

Priority

Controls the port priority. This can be used to control priority of ports having identical port cost. (See
above).

operEdge (state flag)

135
Operational flag describing whether the port is connecting directly to edge devices. (No Bridges attached).
Transition to the forwarding state is faster for edge ports (havingoperEdge true) than for other ports. The
value of this flag is based on AdminEdge and AutoEdge fields. This flag is displayed as Edge in
Monitor->Spanning Tree -> STP Detailed Bridge Status.

Admin Edge

Controls whether the operEdge flag should start as set or cleared. (The initial operEdge state when a port
is initialized).

Auto Edge

Controls whether the bridge should enable automatic edge detection on the bridge port. This allows
operEdge to be derived from whether BPDU's are received on the port or not.

Restricted Role

If enabled, causes the port not to be selected as Root Port for the CIST or any MSTI, even if it has the best
spanning tree priority vector. Such a port will be selected as an Alternate Port after the Root Port has been
selected. If set, it can cause lack of spanning tree connectivity. It can be set by a network administrator to
prevent bridges external to a core region of the network influence the spanning tree active topology,
possibly because those bridges are not under the full control of the administrator. This feature is also
known as Root Guard.

Restricted TCN

If enabled, causes the port not to propagate received topology change notifications and topology changes
to other ports. If set it can cause temporary loss of connectivity after changes in a spanning tree's active
topology as a result of persistently incorrect learned station location information. It is set by a network
administrator to prevent bridges external to a core region of the network, causing address flushing in that
region, possibly because those bridges are not under the full control of the administrator or the physical
link state of the attached LANs transits frequently.

BPDU Guard

If enabled, causes the port to disable itself upon receiving valid BPDU's. Contrary to the similar bridge
setting, the port Edge status does not effect this setting.

A port entering error-disabled state due to this setting is subject to the bridge Port Error Recovery setting
as well.

Point2Point

Controls whether the port connects to a point-to-point LAN rather than to a shared medium. This can be
automatically determined, or forced either true or false. Transition to the forwarding state is faster for
point-to-point LANs than for shared media.

Buttons

Save: Click to save changes.

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

136
7.5. Spanning Tree MSTI Ports

STP MSTI Port Configuration

This page allows the user to inspect the current STP MSTI port configurations, and possibly
change them as well.

An MSTI port is a virtual port, which is instantiated separately for each active CIST (physical) port for each
MSTI instance configured on and applicable to the port. The MSTI instance must be selected before
displaying actual MSTI port configuration options.

This page contains MSTI port settings for physical and aggregated ports.

Apart from the selected MSTI, the STP MSTI port settings also relate to the currently selected stack unit,
as reflected by the page header.

Port

The switch port number of the corresponding STP CIST (and MSTI) port.

Path Cost

Controls the path cost incurred by the port. The Auto setting will set the path cost as appropriate by the
physical link speed, using the 802.1D recommended values. Using the Specific setting, a user-defined
value can be entered. The path cost is used when establishing the active topology of the network. Lower
path cost ports are chosen as forwarding ports in favor of higher path cost ports. Valid values are in the
range 1 to 200000000.

137
Priority

Controls the port priority. This can be used to control priority of ports having identical port cost. (See
above).

Buttons

Save: Click to save changes.

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

138
8. MVR (Multicast VLAN Registration)
MVR is shot of Multicast VLAN Registration. The MVR is a protocol for layer 2 network that enables

multicast traffic from a source VLAN to be shared with client/subscriber VLANs. MVR is typically used for

IPTV-like service. In non-MVR environment, the IPTV source to different VLAN would be copied multiple
copies based on how many client/subscriber VLANs it would deliver.

The IPTV actually delivers the same source with multiple the same content IP streams, the duplicated

traffic occupies the bandwidth of the uplink port. Once the traffic is heavy, some unexpected lost or lag

appears. However, after MVR enabled, the client/subscriber VLANs are registered to the same source
VLAN, then there is only one source stream will be delivered to the registered VLANs.

This page provides MVR related configurations.

Most of the settings are global, whereas the Router Port configuration is related to the currently selected
stack unit, as reflected by the page header.

The MVR feature enables multicast traffic forwarding on the Multicast VLAN. In a multicast television
application, a PC or a television with a set-top box can receive the multicast stream. Multiple set-top boxes
or PCs can be connected to one subscriber port, which is a switch port configured as an MVR receiver port.
When a subscriber selects a channel, the set-top box or PC sends an IGMP join message to Switch A to
join the appropriate multicast. Uplink ports that send and receive multicast data to and from the multicast
VLAN are called MVR source ports.

MVR Mode

Enable/Disable the Global MVR.


VLAN ID

Specify the Multicast VLAN ID.

Mode

Enable MVR on the port.

Type

Specify the MVR port type on the port.

Immediate Leave

Enable the fast leave on the port.

Buttons

Save: Click to save changes.

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

140
9. IPMC (IP Multicast)
IPMC is short of IP Multicast, the switch support IPv4 and IPv6 multicast forwarding and
filtering. The IGMP Snooping defines how to manage IPv4 multicast traffic, the MLD defines
how to manage IPv6 multicast traffic.

9.1. IGMP Snooping Configuration


Internet Group Management Protocol Snooping (IGMP Snooping) is a multicast constraining mechanism
that runs on Layer 2 devices to manage and control multicast groups. By listening to and analyzing IGMP
messages, a Layer 2 device running IGMP Snooping establishes mappings between ports and multicast
MAC addresses and forwards multicast data based on these mappings.

9.1.1. Basic Configuration

This page provides IGMP Snooping related configuration.

Global Configuration

Snooping Enabled

Enable the Global IGMP Snooping.

Unregistered IPMCv4 Flooding enabled

141
Enable unregistered IPMCv4 traffic flooding. Unregistered IPMCv4 traffic is so-called unknown multicast.
After selected, the unregistered multicast stream will be forwarded like normal packets. Once you
un-selected it, such stream will be discarded.

IGMP SSM Range

SSM (Source-Specific Multicast) Range allows the SSM-aware hosts and routers run the SSM service
model for the groups in the address range.

Leave Proxy Enabled

Enable IGMP Leave Proxy. This feature can be used to avoid forwarding unnecessary leave messages to
the router side.

Proxy Enabled

Enable IGMP Proxy. This feature can be used to avoid forwarding unnecessary join and leave messages
to the router side.

Port Related Configuration

Router Port

Specify which ports act as router ports. A router port is a port on the Ethernet switch that leads towards the
Layer 3 multicast device or MLD querier. Normally, the router port is the uplink port to the upper L3 Router
or IGMP Querier. For example in below figure, the green port of the 2 switches are Router port.

If an aggregation member port is selected as a router port, the whole aggregation will act as a router port.

Fast Leave

Enable the fast leave on the port.


Multicast snooping Fast Leave processing allows the switch to remove an interface from the
forwarding-table entry without first sending out group specific queries to the interface. The VLAN interface
is pruned from the multicast tree for the multicast group specified in the original leave message.
Fast-leave processing ensures optimal bandwidth management for all hosts on a switched network, even
when multiple multicast groups are in use simultaneously. This processing applies to IGMP and MLD

Throttling

Enable to limit the number of multicast groups to which a switch port can belong.

Buttons

Save: Click to save changes.

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

142
9.1.2. IGMP Snooping VLAN Configuration

Navigating the IGMP Snooping VLAN Table


Each page shows up to 99 entries from the VLAN table, default being 20, selected through the "entries per
page" input field. When first visited, the web page will show the first 20 entries from the beginning of the
VLAN Table. The first displayed will be the one with the lowest VLAN ID found in the VLAN Table.
The "VLAN" input fields allow the user to select the starting point in the VLAN Table. Clicking the button
will update the displayed table starting from that or the next closest VLAN Table match.
The will use the last entry of the currently displayed entry as a basis for the next lookup. When the end is
reached the text "No more entries" is shown in the displayed table. Use the button to start over.

IGMP Snooping VLAN Table Columns

VLAN ID

The VLAN ID of the entry.

IGMP Snooping Enabled

Enable the per-VLAN IGMP Snooping. Only up to 64 VLANs can be selected.

IGMP Querier

Enable the IGMP Querier in the VLAN.

Compatibility

Compatibility is maintained by hosts and routers taking appropriate actions depending on the versions of
IGMP operating on hosts and routers within a network. The allowed selection is IGMP-Auto, Forced
IGMPv1, Forced IGMPv2, Forced IGMPv3, default compatibility value is IGMP-Auto.

RV

Robustness Variable. The Robustness Variable allows tuning for the expected packet loss on a network.
The allowed range is 1 to 255, default robustness variable value is 2.

QI

Query Interval. The Query Interval is the interval between General Queries sent by the Querier. The
allowed range is 1 to 31744 seconds, default query interval is 125 seconds.

QRI

Query Response Interval. The Max Response Time used to calculate the Max Resp Code inserted into the
periodic General Queries. The allowed range is 0 to 31744 in tenths of seconds, default query response
interval is 100 in tenths of seconds (10 seconds).

LLQI (LMQI for IGMP)

143
Last Member Query Interval. The Last Member Query Time is the time value represented by the Last
Member Query Interval, multiplied by the Last Member Query Count. The allowed range is 0 to 31744 in
tenths of seconds, default last member query interval is 10 in tenths of seconds (1 second).

URI

Unsolicited Report Interval. The Unsolicited Report Interval is the time between repetitions of a host's
initial report of membership in a group. The allowed range is 0 to 31744 seconds, default unsolicited report
interval is 1 second.

Buttons

Refresh: Refreshes the displayed table starting from the “VLAN” input fields.
<< : Updates the table starting from the first entry in the VALN Table, i.e. the entry with the lowest VLAND
ID.
>>: Update the table, staring with the entry after the last entry currently displayed.
Save: To save the configuration.
Reset: Click to undo any changes made locally and revert to previously saved values.

9.1.3. IGMP Snooping / Port Group Filtering


IGMP Snooping Port Group Filtering Configuration

Delete

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

Port

The logical port for the settings.

Filtering Groups

144
The IP Multicast Group that will be filtered.

Adding New Filtering Group

Click to add a new entry to the Group Filtering table. Specify the Port, and Filtering Group of the new entry.
Click "Save".

Warning message about the Filtering Group.


The range of the IP Multicast is 224.0.0.0 ~239.255.255.255

Buttons

Save: Click to save changes.

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

9.2. MLD Snooping Configuration


This section provides MLD Snooping related configuration. The MLD is for IPv6 Multicast Snooping. The
difference between the 2 IGMP and MLD is that the IGMP is applied to IPv4 Multicast stream, the MLD is
applied to IPv6 Multicast stream. While configuring the MLD Snooping configuration, the only thing you
need to understand is the IPv6 packet format.

9.2.1. Basic Configuration


This basic configuration of the MLD, IPv6 Multicast Routing.
Most of the settings are global, whereas the Router Port configuration is related to the currently selected
stack unit, as reflected by the page header.

Snooping Enabled

Enable the Global MLD Snooping.

Unregistered IPMCv6 Flooding enabled

Enable unregistered IPMCv6 traffic flooding. Please note that disabling unregistered IPMCv6 traffic
flooding may lead to failure of Neighbour Discovery.

SSM Range

145
SSM (Source-Specific Multicast) Range allows the SSM-aware hosts and routers run the SSM service
model for the groups in the address range.

Leave Proxy Enabled

Enable MLD Leave Proxy. This feature can be used to avoid forwarding unnecessary leave messages to
the router side.

Proxy Enabled

Enable MLD Proxy. This feature can be used to avoid forwarding unnecessary join and leave messages to
the router side.

Router Port

Specify which ports act as router ports. A router port is a port on the Ethernet switch that leads towards the
Layer 3 multicast device or MLD querier. Normally, the router port is the uplink port to the upper L3 Router
or IGMP Querier. For example in below figure, the green port of the 2 switches are Router port.

If an aggregation member port is selected as a router port, the whole aggregation will act as a router port.

Fast Leave

Enable the fast leave on the port.

Throttling

Enable to limit the number of multicast groups to which a switch port can belong.

Buttons

Save: Click to save changes.


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

9.2.2. MLD Snooping VLAN Configuration

Navigating the MLD Snooping VLAN Table

Each page shows up to 99 entries from the VLAN table, default being 20, selected through the "entries
per page" input field. When first visited, the web page will show the first 20 entries from the beginning of
the VLAN Table. The first displayed will be the one with the lowest VLAN ID found in the VLAN Table.
The "VLAN" input fields allow the user to select the starting point in the VLAN Table. Clicking the button
will update the displayed table starting from that or the next closest VLAN Table match.
The will use the last entry of the currently displayed entry as a basis for the next lookup. When the end is
reached the text "No more entries" is shown in the displayed table. Use the button to start over.

146
MLD Snooping VLAN Table Columns

VLAN ID

The VLAN ID of the entry.

MLD Snooping Enabled

Enable the per-VLAN MLD Snooping. Only up to 64 VLANs can be selected.

MLD Querier

Enable the IGMP Querier in the VLAN.

Compatibility

Compatibility is maintained by hosts and routers taking appropriate actions depending on the versions of
MLD operating on hosts and routers within a network. The allowed selection is MLD-Auto, ForcedMLDv1,
Forced MLDv2, default compatibility value is MLD-Auto.

RV

Robustness Variable. The Robustness Variable allows tuning for the expected packet loss on a link. The
allowed range is 1 to 255, default robustness variable value is 2.

QI

Query Interval. The Query Interval variable denotes the interval between General Queries sent by the
Querier. The allowed range is 1 to 31744 seconds, default query interval is 125 seconds.

QRI

Query Response Interval. The Maximum Response Delay used to calculate the Maximum Response
Code inserted into the periodic General Queries. The allowed range is 0 to 31744 in tenths of seconds,
default query response interval is 100 in tenths of seconds (10 seconds).

LLQI

Last Listener Query Interval. The Last Listener Query Interval is the Maximum Response Delay used
to calculate the Maximum Response Code inserted into Multicast Address Specific Queries sent in
response to Version 1 Multicast Listener Done messages. It is also the Maximum Response Delay used
to calculate the Maximum Response Code inserted into Multicast Address and Source Specific Query
messages. The allowed range is 0 to 31744 in tenths of seconds, default last listener query interval is 10
in tenths of seconds (1 second).

URI

Unsolicited Report Interval. The Unsolicited Report Interval is the time between repetitions of a node's
initial report of interest in a multicast address. The allowed range is 0 to 31744 seconds, default
unsolicited report interval is 1 second.

Buttons

Refresh: Refreshes the displayed table starting from the “VLAN” input fields.

<< : Updates the table starting from the first entry in the VALN Table, i.e. the entry with the lowest

147
VLAND ID.

>>: Update the table, staring with the entry after the last entry currently displayed.

9.2.3. IPMC / MLD Snooping / Port Group Filtering

MLD Snooping Port Group Filtering Configuration

Delete

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

Port

The logical port for the settings.

Filtering Groups

The IP Multicast Group that will be filtered.

Adding New Filtering Group

Click to add a new entry to the Group Filtering table. Specify the Port and Filtering Group for the new
entry. Click "Save".

Buttons

Save: Click to save changes.

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

148
10. LLDP Parameters
The Link Layer Discovery Protocol (LLDP) is a vendor-neutral link layer protocol. LLDP information
is sent by devices from each of their interfaces at a fixed interval, in the form of an Ethernet Frame.
Each frame contains one LLDP Data Unit (LLDPDU). Each LLDPDU is a sequence of
Type-Length-Value (TLV) structures. Each LLDP frame starts with the following mandatory TLVs:
Chassis ID, Port ID, and Time-to-Live. The mandatory TLVs are followed by any number of optional
TLVs.
This section allows the user to inspect and configure the current LLDP port settings.

10.1. LLDP Configuration

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

149
When a port is disabled, LLDP is disabled or the switch is rebooted, an LLDP shutdown frame is
transmitted to the neighbouring 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 stack unit, 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 neighbour units is
analyzed.

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

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

Enabled The switch will send out LLDP information, and will analyze LLDP information received from
neighbours.

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 neighbours' 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 neighbours' 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 neighbours 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 neighbours' table.

If all ports have CDP awareness disabled the switch forwards CDP frames received from neighbour
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 removed when the hold time is exceeded.

150
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

Save: Click to save changes.

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

10.2. LLDP Media Configuration

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

151
Fast start repeat count

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

152
Map Datum

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

WGS84: (Geographical 3D) - World Geodesic System 1984, CRS Code 4327, 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, perish, 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

153
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

154
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:

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. Soft phone Voice
4. Video Conferencing
5. Streaming Video
6. Control / Signaling ( 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

155
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 policies 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 Signaling (conditional) - for use in network topologies that require a different policy for the
voice signaling 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 Signaling (conditional) - for use in network topologies that require a different policy for
the guest voice signaling 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 Signaling (conditional) - for use in network topologies that require a separate policy for the
video signaling 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

156
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 behavior 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.

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 "Save".

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

Save: Click to save changes.

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

157
11. PoE Configuration
Use the Power over Ethernet Configuration page to set the maximum PoE power provided to a port, the

maximum power budget for the switch (power available to all RJ-45 ports), the port PoE operating mode,

power allocation priority, and the maximum power allocated to each port. If the power demand from devices

connected to the switch exceeds the power budget, the switch uses port power priority settings to limit the

supplied

power.

Power over Ethernet Configuration

Reserved Power determined by

There are three modes for configuring how the ports/PDs may reserve power.

1. Class mode: In this mode each port automatically determines how much power to reserve
according to the class the connected PD belongs to, and reserves the power accordingly. Four
different port classes exist and one for 4, 7, 15.4 or 30 Watts.

In this mode the Maximum Power fields have no effect.

2. Allocation mode: In this mode the administrators can allocate the amount of power that each
port may reserve. The allocated/reserved power for each port/PDs specified in the Maximum
Power fields.

3. LLDP-MED mode: This mode is similar to the Class mode except that each port determine the
amount power it reserves by exchanging PoE information using the LLDP protocol and reserves
power accordingly. If no LLDP information is available for a port, the port will reserve power using
the class mode

In this mode the Maximum Power fields have no effect

For all modes: If a port uses more power than the reserved power for the port, the port is shut down.

Power Management Mode

158
There are 2 modes for configuring when to shut down the ports:

1. Actual Consumption: In this mode the ports are shut down when the actual power consumption
for all ports exceeds the amount of power that the power supply can deliver or if the actual power
consumption for a given port exceeds the reserved power for that port. The ports are shut down
according to the ports priority. If two ports have the same priority the port with the highest port
number is shut down.

2. Reserved Power: In this mode the ports are shut down when total reserved powered exceeds
the amount of power that the power supply can deliver. In this mode the port power is not turned
on if the PD requests more power than available from the power supply.

PoE Power Supply Configuration

Primary Power Supply (W)

The valid range of power supply for the SW1024 is from 0 to 500W.

PoE Port Configuration

Port

This is the logical port number for this row.

Ports that are not PoE-capable are grayed out and thus impossible to configure PoE for.

PoE Mode

The PoE Mode represents the PoE operating mode for the port.

 Disabled: PoE disabled for the port.

 PoE: Enables PoE IEEE 802.3af (Class 4 PDs limited to 15.4W)

 PoE+: Enables PoE+ IEEE 802.3at (Class 4 PDs limited to 30W)

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 require 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

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

Save: Click to save changes.

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

159
12. MAC Address Table Configuration
The MAC Address Table is configured on this page. Set timeouts for entries in the dynamic
MAC Table and configure the static MAC table here.

Aging Configuration

By default, dynamic entries are removed from the MAC table after 300 seconds. This removal is also
called aging.

Configure aging time by entering a value here in seconds; for example, Age time seconds.
The allowed range is 10 to 1000000 seconds.

Disable the automatic aging of dynamic entries by checking Disable automatic aging.

MAC Table Learning

If the learning mode for a given port is greyed out, another module is in control of the mode, so that it
cannot be changed by the user. An example of such a module is the MAC-Based Authentication under
802.1X.
Each port can do learning based upon the following settings:

Auto

Learning is done automatically as soon as a frame with unknown SMAC is received.

Disable

No learning is done.

Secure

Only static MAC entries are learned, all other frames are dropped.

160
Note: Make sure that the link used for managing the switch is added to the Static Mac Table before
changing to secure learning mode, otherwise the management link is lost and can only be restored by
using another non-secure port or by connecting to the switch via the serial interface.

Static MAC Table Configuration

The static entries in the MAC table are shown in this table. The static MAC table can contain 64 entries.

The table is sorted first by VLAN ID and then by MAC address.

Delete

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

161
VLAN ID

The VLAN ID of the entry

MAC Address

The MAC address of the entry

Port Members

Checkmarks indicate which ports are members of the entry. Check or uncheck as needed to modify the
entry.

Adding a New Static Entry

Click to add a new entry to the static MAC table. Specify the VLAN ID, MAC address, and port
members for the new entry. Click "Save".

Buttons

Save: Click to save changes.

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

162
13. VLAN (Virtual LAN)
The VLAN is short of Virtual LAN (Local Area Network.) The VLAN technology allows you to
divide the physical ports to different logical groups. With network segmentation, each switch
port connects to a segment which could be a single broadcast domain.

There are 2 typical types of VLAN technology, Port-Based and Tag Based. The Port-based
VLAN is the simplest approach of LAN implementation, which is to assign certain ports of
switch to different VLANs. On the other hand, tag-based VLAN follows IEEE 802.1Q
technology to tag VLAN ID to the packets. The tagged VLAN ID is not only applied to the
switch, but also be forwarded toward other devices within the whole network.

13.1. VLAN Membership Configuration

The VLAN Membership Configuration for the switch can be monitored and modified here. Up to 4096
VLANs are supported. This page allows for adding and deleting VLANs as well as adding and deleting
port members of each VLAN.

Navigating the VLAN Table

Each page shows up to 99 entries from the VLAN table, default being 20, selected through the "entries
per page" input field. When first visited, the web page will show the first 20 entries from the beginning of
the VLAN Table. The first displayed will be the VLAN ID with the lowest value found from the VLAN
Table. The "VLAN" input fields allow administrators to revise which to start in the VLAN Table after
clicking the “Refresh” button.

Delete

To delete a VLAN entry by selecting the checkbox and clicking “Save”

VLAN ID

To Indicate the ID of the particular VLAN

VLAN Name

To remark the name for the VLAN tags

Maximum length of the VLAN Name String is 32 with alphabets and/ or numbers (at least one alphabet).
Besides, VLAN name can be edited for the existing VLAN entries or added by the new entries.

163
Port Members

A row of check boxes for each port is displayed for each VLAN ID.
To include a port in a VLAN, check the box as .
To include a port in a forbidden port list, check the box as shown .
To remove or exclude the port from the VLAN, make sure the box is unchecked as shown .
By default, no ports are members, and for every new VLAN entry all boxes are unchecked.

Adding a New VLAN

Click to add a new VLAN ID. An empty row is added to the table, and the VLAN can be configured as
needed. Legal values for a VLAN ID are 1 through 4095.

The VLAN is enabled when you click on "Save". A VLAN without any port members will be deleted
when you click "Save".

Buttons

Save: Click to save changes.

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

Refresh: Refreshes the displayed the table starting from the “VLAND ID” input fields.

<<: Updates the table starting from the first entry in the VALN Table, i.e. the entry with the lowest
VLAND ID.

>>: Update the table, staring with the entry after the last entry currently displayed.

13.2. VLAN Port Configuration

This page is used for configuring the selected stack switch unit port VLAN.

This page is used for configuring the switch port VLAN.

164
Ether type for Custom S-ports

This field specifies the ether type used for Custom S-ports. This is a global setting for all the Custom
S-ports.

Port

This is the logical port number of this row.

Port Type

Port can be one of the following types: Unaware, Customer port(C-port), Service port(S-port),
Custom Service port(S-custom-port)

If Port Type is Unaware, all frames are classified to the Port VLAN ID and tags are not removed.

Ingress Filtering

To determine how to process frames tagged for VLANs for which the ingress port is not a member.

(Default: Disabled)

 Ingress filtering only affects tagged frames.

 If ingress filtering is enabled and a port receives frames tagged for VLANs for which it is not a

member, these frames will be discarded.

 If ingress filtering is disabled and a port receives frames tagged for VLANs for which it is not a

member, these frames will be flooded to all other ports.

Frame Type

This field sets the interface to accept all frame types, including tagged or untagged frames, only tagged

frames, or only untagged frames. When set to receive all frame types, any received frames that are

untagged are assigned to the default VLAN. When set to receive only tagged frames, all untagged frames

received on the interface are discarded. (Option: All, Tagged, Untagged; Default: All)

Port VLAN Mode

To configure the Port VLAN Mode which affects VLAN ingress and egress processing.

165
If None is selected, a VLAN tag with the classified VLAN ID is inserted in frames transmitted on the port.
This mode is normally used for ports connected to VLAN aware switches.

If Specific (the default value) is selected, a Port VLAN ID can be configured (see below). Untagged
frames received on the port are classified to the Port VLAN ID. If VLAN awareness is disabled, all
frames received on the port are classified to the Port VLAN ID. If the classified VLAN ID of a frame
transmitted on the port is different from the Port VLAN ID, a VLAN tag with the classified VLAN ID is
inserted in the frame.

Port VLAN ID

To configure the VLAN identifier for the port

The allowed values are 1 through 4095. The default value is 1.


Note: The port must be a member of the same VLAN as the Port VLAN ID.

Tx Tag

To determine egress tagging of a port

 Untag_pvid - All VLANs except the configured PVID will be tagged.

 Tag_all - All VLANs are tagged.

 Untag_all - All VLANs are untagged.

Buttons

Save: Click to save changes.

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

166
14. Private VLANs
The Private VLAN feature provides the ability to extend the capabilities of a "standard" VLAN. The
additional concepts, Primary VLAN, Community VLAN and Isolated VLAN are introduced in Private
VLAN.

The Primary VLAN can be considered the master in the master/slave relationship with the other 2
sub-types, Community VLAN and Isolated VLAN. The switch Ports assigned with the primary VLAN are
able to access the ports in the 2 sub-types.

Both the Community VLN and Isolated VLAN can be considered slaves in the master/slave
relationship with the primary VLAN. The switch ports assigned to a Community VLAN can see traffic
from all other devices in the same Community. The switch ports assigned to an Isolated VLAN can
send traffic to the primary VLAN, but CANNOT see traffic from other devices in the same Isolated
VLAN.

In this section, the switch allows you to assign Private VLAN Member Configuration and Port Isolation
Configuration.

14.1. Private VLAN Membership Configuration

The Private VLAN membership configurations for the switch can be monitored and modified here.
Private VLANs can be added or deleted here. Port members of each Private VLAN can be added or
removed here.

Private VLANs are based on the source port mask, and there are no connections to VLANs. This
means that VLAN IDs and Private VLAN IDs can be identical.

A port must be a member of both a VLAN and a Private VLAN to be able to forward packets. By default,
all ports are VLAN unaware and members of VLAN 1 and Private VLAN 1.

A VLAN unaware port can only be a member of one VLAN, but it can be a member of multiple Private
VLANs.

167
Private VLANs do not work across the stack.

Delete

To delete a private VLAN entry, check this box. The entry will be deleted during the next save.

Private VLAN ID

Indicates the ID of this particular private VLAN.

Port Members

A row of check boxes for each port is displayed for each private VLAN ID. To include a port in a Private
VLAN, check the box. To remove or exclude the port from the Private VLAN, make sure the box is
unchecked. By default, no ports are members, and all boxes are unchecked.

Adding a New Private VLAN

Click to add a new private VLAN ID. An empty row is added to the table, and the private VLAN can be
configured as needed. The allowed range for a private VLAN ID is the same as the switch port number
range. Any values outside this range are not accepted, and a warning message appears. Click "OK" to
discard the incorrect entry, or click "Cancel" to return to the editing and make a correction.

The Private VLAN is enabled when you click "Save".

The button can be used to undo the addition of new Private VLANs.

Buttons

Save: Click to save changes.

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

14.2. Port Isolation Configuration

Overview

This page is used for enabling or disabling port isolation on ports in a Private VLAN.

168
A port member of a VLAN can be isolated to other isolated ports on the same VLAN and Private VLAN.

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

This feature works across the stack.

Configuration

Port Members

A check box is provided for each port of a private VLAN. When checked, port isolation is enabled on
that port. When unchecked, port isolation is disabled on that port.
By default, port isolation is disabled on all ports.

Buttons

Save: Click to save changes.

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

169
15. VCL

15.1. VCL / MAC-Based VLAN Configuration

The MAC-based VLAN entries can be configured here. This page allows for adding and deleting
MAC-based VLAN entries and assigning the entries to different ports. This page shows only static
entries.

Delete

To delete a MAC-based VLAN entry, check this box and press save. The entry will be deleted in the
stack.

MAC Address

Indicates the MAC address.

VLAN ID

Indicates the VLAN ID.

Port Members

A row of check boxes for each port is displayed for each MAC-based VLAN entry. To include a port in a
MAC-based VLAN, check the box. To remove or exclude the port from the MAC-based VLAN, make
sure the box is unchecked. By default, no ports are members, and all boxes are unchecked.

Adding a New MAC-based VLAN

Click to add a new MAC-based VLAN entry. An empty row is added to the table, and the MAC-based
VLAN entry can be configured as needed. Any unicast MAC address can be configured for the
MAC-based VLAN entry. No broadcast or multicast MAC addresses are allowed. Legal values for a
VLAN ID are 1 through 4095.

The MAC-based VLAN entry is enabled when you click on "Save". A MAC-based VLAN without any
port members will be deleted when you click "Save".

170
The button can be used to undo the addition of new MAC-based VLANs.

Buttons

Save: Click to save changes.

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

Refresh: Refreshes the displayed the table starting from the “VLAND ID” input fields.

<< : Updates the table starting from the first entry in the VALN Table, i.e. the entry with the lowest
VLAND ID.

>>: Update the table, staring with the entry after the last entry currently displayed.

15.2. VCL / Protocol-based VLAN

Protocol to Group Mapping Table

This page allows you to add new protocols to Group Name (unique for each Group) mapping entries as
well as allow you to see and delete already mapped entries for the switch.

The displayed settings are:

Delete

To delete a Protocol to Group Name map entry, check this box. The entry will be deleted on the switch
during the next Save.

Frame Type

Frame Type can have one of the following values:

1. Ethernet

171
2. LLC

3. SNAP

Note: On changing the Frame type field, valid value of the following text field will vary depending on the
new frame type you selected.

Value

Valid value that can be entered in this text field depends on the option selected from the preceding
Frame Type selection menu.
Below is the criteria for three different Frame Types:

For Ethernet: Values in the text field when Ethernet is selected as a Frame Type is called etype. Valid
values for etype ranges from 0x0600-0xffff

For LLC: Valid value in this case is comprised of two different sub-values.
a. DSAP: 1-byte long string (0x00-0xff)
b. SSAP: 1-byte long string (0x00-0xff)

For SNAP: Valid value in this case also is comprised of two different sub-values.
a OUI: OUI (Organizationally Unique Identifier) is value in format of xx-xx-xx where each pair (xx) in
string is a hexadecimal value ranges from 0x00-0xff.
b. PID: If the OUI is hexadecimal 000000, the protocol ID is the Ethernet type (EtherType) field value
for the protocol running on top of SNAP; if the OUI is an OUI for a particular organization, the protocol
ID is a value assigned by that organization to the protocol running on top of SNAP.

In other words, if value of OUI field is 00-00-00 then value of PID will be etype (0x0600-0xffff) and if
value of OUI is other than 00-00-00 then valid value of PID will be any value from 0x0000 to 0xffff.

Group Name

A valid Group Name is a unique 16-character long string for every entry which consists of a
combination of alphabets (a-z or A-Z) and integers (0-9).

Note: special character and underscore are not allowed.

Adding a New Group to VLAN mapping entry

Click to add a new entry in mapping table. An empty row is added to the table; Frame Type, Value and
the Group Name can be configured as needed.
The button can be used to undo the addition of new entry.

Buttons

Save: Click to save changes.

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

172
VLC / Protocol-based VLAN / Group Name to VLAN mapping Table

This page allows you to map an already configured Group Name to a VLAN for the switch. The
displayed settings are:

Delete

To delete a Group Name to VLAN map entry, check this box. The entry will be deleted on the switch
during the next Save

Group Name

A valid Group Name is a string of at most 16 characters which consists of a combination of alphabets
(a-z or A-Z) and integers (0-9), no special character is allowed. Whichever Group name you try map to
a VLAN must be present in Protocol to Group mapping table and must not be used by any other
existing mapping entry on this page.

VLAD ID

Indicates the ID to which Group Name will be mapped. A valid VLAN ID ranges from 1-4095.

Port Members

A row of check boxes for each port is displayed for each Group Name to VLAN ID mapping. To include
a port in a mapping, check the box. To remove or exclude the port from the mapping, make sure the
box is unchecked. By default, no ports are members, and all boxes are unchecked.

Adding a New Group to VLAN mapping entry

Click to add a new entry in mapping table. An empty row is added to the table, the Group Name, VLAN
ID and port members can be configured as needed. Legal values for a VLAN ID are 1 through 4095.

The button can be used to undo the addition of new entry.

173
Buttons

Save: Click to save changes.

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

15.3. VCL / IP Subnet-based VLAN

The IP subnet-based VLAN entries can be configured here. This page allows for adding, updating and
deleting IP subnet-based VLAN entries and assigning the entries to different ports. This page shows
only static entries.

Delete

To delete an IP subnet-based VLAN entry, check this box and press save. The entry will be deleted in
the stack.

VCE ID

Indicates the index of the entry. It is user configurable. Its value ranges from 0-256. If a VCE ID is 0,
application will auto-generate the VCE ID for that entry. Deletion and lookup of IP subnet-based VLAN
are based on VCE ID.

IP Address

Indicates the IP address.

Mask Length

Indicates the network mask length.

174
VLAN ID

Indicates the VLAN ID. VLAN ID can be changed for the existing entries.

Port Members

A row of check boxes for each port is displayed for each IP subnet-based VLAN entry. To include a port
in an IP subnet-based VLAN, check the box. To remove or exclude the port from the IP subnet-based
VLAN, make sure the box is unchecked. By default, no ports are members, and all boxes are
unchecked.

Adding a New IP subnet-based VLAN

Click "Add New Entry" to add a new IP subnet-based VLAN entry. An empty row is added to the table,
and the IP subnet-based VLAN entry can be configured as needed. Any IP address/mask can be
configured for the IP subnet-based VLAN entry. Legal values for a VLAN ID are 1 through 4095.

The IP subnet-based VLAN entry is enabled when you click on "Save". The "Delete" button can be
used to undo the addition of new IP subnet-based VLANs.

Buttons

Save: Click to save changes.

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

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

Refresh: Refreshes the displayed table.

175
16. Voice VLAN Configuration

16.1. Voice VLAN / Configuration

The Voice VLAN feature enables voice traffic forwarding on the Voice VLAN, then the switch can
classify and schedule network traffic. It is recommended that there be two VLANs on a port - one for
voice, one for data. Before connecting the IP device to the switch, the IP phone should configure the
voice VLAND ID correctly. It should be configured through its own interface.

Mode

Indicates the Voice VLAN mode operation. We must disable MSTP feature before we enable Voice
VLAN. It can avoid the conflict of ingress filtering. Possible modes are:
Enabled: Enable Voice VLAN mode operation.

Disabled: Disable Voice VLAN mode operation.

VLAN ID

Indicates the Voice VLAN ID. It should be a unique VLAN ID in the system and cannot equal each port
PVID. It is a conflict in configuration if the value equals management VID, MVR VID, PVID etc. The
allowed range is 1 to 4095.

Aging Time

Indicates the Voice VLAN secure learning aging time. The allowed range is 10 to 1000000 seconds. It
is used when security mode or auto detect mode is enabled. In other cases, it will be based on
hardware aging time. The actual aging time will be situated between the [age time; 2 * age time]
interval.

Traffic Class

176
Indicates the Voice VLAN traffic class. All traffic on the Voice VLAN will apply this class.

Port Mode

Indicates Voice VLAN port mode.

Possible modes are:

Disabled: from Voice VLAN.


Auto: Enable auto detect mode. It detects whether there is VoIP phone attached to the specific port
and configures the Voice VLAN members automatically.
Forced: Force join to Voice VLAN.

Port Security

This is the Voice VLAN port security mode. When the function is enabled, all non-telephonic MAC
addresses in the Voice VLAN will be blocked for 10 seconds. Possible port modes are:
Enabled: Enable Voice VLAN security mode operation.

Disabled: Disable Voice VLAN security mode operation.

Port Discovery Protocol

Indicates the Voice VLAN port discovery protocol. It will only work when auto detect mode is enabled.
We should enable LLDP feature before configuring discovery protocol to "LLDP" or "Both". Changing
the discovery protocol to "OUI" or "LLDP" will restart the auto detect process. Possible discovery
protocols are:
OUI: Detect telephony device by OUI address.
LLDP: Detect telephony device by LLDP.
Both: Both OUI and LLDP.

Buttons

Save: Click to save changes.

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

16.2. Voice VLAN / OUI Configuration

Configure VOICE VLAN OUI table on this page. The maximum entry number is 16. Modifying the OUI
table will restart auto detection of OUI process.

177
Delete

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

Telephony OUI

A telephony OUI address is a globally unique identifier assigned to a vendor by IEEE. It must be 6
characters long and the input format is "xx-xx-xx" (x is a hexadecimal digit).

Description

The description of OUI address. Normally, it describes which vendor telephony device it belongs to.
The allowed string length is 0 to 32.

Buttons

Add new entry: Click to add a new access management entry.

Save: Click to save changes.

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

Refresh: Refreshes the displayed the table starting from the “VLAND ID” input fields.

<< : Updates the table starting from the first entry in the VALN Table, i.e. the entry with the lowest
VLAND

178
17. QoS
17.1. QoS / Ingress Port Classification

This page allows you to configure the basic QoS Ingress Classification settings for all switch ports.

The settings relate to the currently selected stack unit, as reflected by the page header.

The displayed settings are:

Port

The port number for which the configuration below applies.

QoS class

Controls the default QoS class, i.e., the QoS class for frames not classified in any other way. There is a
one to one mapping between QoS class, queue and priority. A QoS class of 0 (zero) has the lowest
priority.

DP level

Controls the default Drop Precedence Level i.e., the DP level for frames not classified in any other way.

PCP

Controls the default PCP for untagged frames.

DEI

179
Controls the default DEI for untagged frames.

Tag Class.

Shows the classification mode for tagged frames on this port.

Disabled: Use default QoS class and DP level for tagged frames.
Enabled: Use mapped versions of PCP and DEI for tagged frames.
Click on the mode in order to configure the mode and/or mapping.

DSCP Based

Click to Enable DSCP Based QoS Ingress Port Classification.

Buttons

Save: Click to save changes.

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

17.2. QoS / Ingress Port Policer Config

This page allows you to configure the Policer settings for all switch ports. The settings relate to the
currently selected stack unit, as reflected by the page header.

The displayed settings are:

Port

The port number for which the configuration below applies.

180
Enabled

Controls whether the policer is enabled on this switch port.

Rate

Controls the rate for the policer. The default value is 500. This value is restricted to 100-1000000 when
the "Unit" is "kbps" or "fps", and it is restricted to 1-3300 when the "Unit" is "Mbps" or "kfps".

Unit

Controls the unit of measure for the policer rate as kbps, Mbps, fps or kfps. The default value is "kbps".

Buttons

Save: Click to save changes.

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

17.3. QoS / Port Scheduler

This page provides an overview of QoS Egress Port Schedulers for all switch ports.

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

The displayed settings are:

181
Port

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

Mode

Shows the scheduling mode for this port.

Qn

Shows the weight for this queue and port.

17.4. QoS / Egress Port Shapers

This page provides an overview of QoS Egress Port Shapers for all switch ports.

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

The displayed settings are:

Port

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

Qn

182
Shows "disabled" or actual queue shaper rate - e.g. "800 Mbps".

Port

Shows "disabled" or actual port shaper rate - e.g. "800 Mbps".

17.5. QoS / Port Tag Remarking

This page provides an overview of QoS Egress Port Tag Remarking for all switch ports.

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

The displayed settings are:

Port

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

Mode

Shows the tag remarking mode for this port.


Classified: Use classified PCP/DEI values.
Default: Use default PCP/DEI values.
Mapped: Use mapped versions of QoS class and DP level..

183
QoS / DSCP

17.6. QoS / Port DSCP Configuration

This page allows you to configure the basic QoS Port DSCP Configuration settings for all switch ports.

The settings relate to the currently selected stack unit, as reflected by the page header.

The displayed settings are:

Port

The Port column shows the list of ports for which you can configure DSCP ingress and egress settings.

Ingress

In Ingress settings you can change ingress translation and classification settings for individual ports.
There are two configuration parameters available in Ingress:
1. Translate
2. Classify

1. Translate

To Enable the Ingress Translation click the checkbox.

2. Classify

184
Classification for a port have 4 different values.

Disabled: No Ingress DSCP Classification.

DSCP=0: Classify if incoming (or translated if enabled) DSCP is 0.

Selected: Classify only selected DSCP for which classification is enabled as specified in DSCP
Translation window for the specific DSCP.

All: Classify all DSCP.

Egress

Port Egress Rewriting can be one of -

Disabled: No Egress rewrite.

Enable: Rewrite enabled without remapping.

Remap DP Unaware: DSCP from analyzer is remapped and frame is remarked with remapped DSCP
value. The remapped DSCP value is always taken from the 'DSCP Translation->Egress Remap DP0'
table.

Remap DP Aware: DSCP from analyzer is remapped and frame is remarked with remapped DSCP
value. Depending on the DP level of the frame, the remapped DSCP value is either taken from the
'DSCP Translation->Egress Remap DP0' table or from the 'DSCP Translation->Egress Remap DP1'
table.

Buttons

Save: Click to save changes.

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

17.7. QoS / DSCP based QoS Ingress Classification

This page allows you to configure the basic QoS DSCP based QoS Ingress Classification settings for
all switches.

The displayed settings are:

185
DSCP

Maximum number of supported DSCP values are 64.

Trust

Controls whether a specific DSCP value is trusted. Only frames with trusted DSCP values are mapped
to a specific QOs class and Drop Precedence Level. Frames with un- trusted DSCP values are treated
as a non-IP frame.

QoS Class

QoS class value can be any of (0-7)

DPL

Drop Precedence Level (0-1)

Buttons

Save: Click to save changes.

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

186
17.8. QoS / DSCP Translation

This page allows you to configure the basic QoS DSCP Translation settings for all switches. DSCP
translation can be done in Ingress or Egress.

The displayed settings are:

DSCP

Maximum number of supported DSCP values are 64 and valid DSCP value ranges from 0 to 63.

Ingress

Ingress side DSCP can be first translated to new DSCP before using the DSCP for QoS class and DPL

map.

There are two configuration parameters for DSCP Translation -

1. Translate

2. Classify

1. Translate

DSCP at Ingress side can be translated to any of (0-63) DSCP values.

2. Classify

Click to enable Classification at Ingress side.

187
Egress

There are the following configurable parameters for Egress side -

1. Remap DP0 Controls the remapping for frames with DP level 0.

2. Remap DP1 Controls the remapping for frames with DP level 1.

1. Remap DP0

Select the DSCP value from select menu to which you want to remap. DSCP value ranges from 0 to 63.

2. Remap DP1

Select the DSCP value from select menu to which you want to remap. DSCP value ranges from 0 to 63.

Buttons

Save: Click to save changes.

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

17.9. QoS / DSCP Classification

This page allows you to configure the mapping of QoS class and Drop Precedence Level to DSCP
value.

The settings relate to the currently selected stack unit, as reflected by the page header.

The displayed settings are:

188
QoS Class

Actual QoS class.

DPL

Actual Drop Precedence Level.

189
DSCP

Select the classified DSCP value (0-63).

Buttons

Save: Click to save changes.

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

17.10. QoS / Control List Configuration

QoS Control List Configuration

This page shows the QoS Control List (QCL), which is made up of the QCEs. Each row describes a
QCE that is defined. The maximum number of QCEs is 256 on each switch.
Click on the lowest plus sign to add a new QCE to the list.

190
QCE#

Indicates the index of QCE.

Indicates Port

Indicates the list of ports configured with the QCE.

Frame Type

Indicates the type of frame to look for incoming frames. Possible frame types are:
Any: The QCE will match all frame type.
Ethernet: Only Ethernet frames (with Ether Type 0x600-0xFFFF) are allowed.
LLC: Only (LLC) frames are allowed.
SNAP: Only (SNAP) frames are allowed.
IPv4: The QCE will match only IPV4 frames.
IPv6: The QCE will match only IPV6 frames.

SMAC

Displays the OUI field of Source MAC address, i.e. first three octet (byte) of MAC address.

DMAC

Specify the type of Destination MAC addresses for incoming frame. Possible values are:
Any: All types of Destination MAC addresses are allowed.
Unicast: Only Unicast MAC addresses are allowed.
Multicast: Only Multicast MAC addresses are allowed.
Broadcast: Only Broadcast MAC addresses are allowed.
The default value is 'Any'.

191
VID

Indicates (VLAN ID), either a specific VID or range of VIDs. VID can be in the range 1-4095 or 'Any'

PCP

Priority Code Point: Valid value PCP are specific (0, 1, 2, 3, 4, 5, 6, 7) or range (0-1, 2-3, 4-5, 6-7, 0-3,
4-7) or 'Any'.

DEI

Drop Eligible Indicator: Valid value of DEI can be any of values between 0, 1 or 'Any'.

Conflict

Displays QCE status. It may happen that resources required to add a QCE may not available, in that
case it shows conflict status as 'Yes', otherwise it is always 'No'. Please note that conflict can be
resolved by releasing the resource required by the QCE and pressing 'Refresh' button.

Action

Indicates the classification action taken on ingress frame if parameters configured are matched with the
frame's content.
There are three action fields: Class, DPL and DSCP.
Class: Classified QoS class..
DPL: Classified Drop Precedence Level.
DSCP: Classified DSCP value.

Modification Buttons

You can modify each QCE (QoS Control Entry) in the table using the following buttons:

192
: Inserts a new QCE before the current row.

: Edits the QCE.

: Moves the QCE up the list.

: Moves the QCE down the list.

: Deletes the QCE.

: The lowest plus sign adds a new entry at the bottom of the QCE listings.
Buttons

Refresh: Click to refresh the page. This will help to check the latest conflict status after releasing the
resources.

17.11. QoS / Storm Control Configuration

Storm control for the switch is configured on this page.

There is a unicast 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

193
Address table.
The configuration indicates the permitted packet rate for unicast, multicast or broadcast traffic across
the switch.

Note: Frames, which are sent to the CPU of the switch are always limited to approximately 4 kpps. For
example, broadcasts in the management VLAN are limited to this rate. The management VLAN is
configured on the IP setup page.

Frame Type

The settings in a particular row apply to the frame type listed here: Unicast, Multicast or Broadcast.

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,1024K,2048K,4096K,

8192K,16384K or 32768K.

Buttons

Save: Click to save changes.

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

194
18. Mirroring Configuration
Configure port Mirroring on this page.

To debug network problems, selected traffic can be copied, or mirrored, on a mirror port where a
frame analyzer can be attached to analyze the frame flow.

The traffic to be copied on the mirror port is selected as follows:

All frames received on a given port (also known as ingress or source mirroring).

All frames transmitted on a given port (also known as egress or destination mirroring).

Port to mirror on

Port to mirror also known as the mirror port. Frames from ports that have either source (rx) or
destination (tx) mirroring enabled are mirrored on this port. Disabled disables mirroring.

Mirror Port Configuration

The following table is used for Rx and Tx enabling.

Port

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

Mode

Select mirror mode.


Rx only Frames received on this port are mirrored on the mirror port. Frames transmitted are not
mirrored.
Tx only Frames transmitted on this port are mirrored on the mirror port. Frames received are not
mirrored.

195
Disabled: Neither frames transmitted nor frames received are mirrored.
Enabled Frames received and frames transmitted are mirrored on the mirror port.

Note: For a given port, a frame is only transmitted once. It is therefore not possible to mirror Tx frames
on the mirror port. Because of this, mode for the selected mirror port is limited to Disabled or Rx
only.

Buttons

Save: Click to save changes.

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

19. UPnP Configuration


Configure UPnP on this 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.

196
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

Save: Click to save changes.

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

197
20. sFlow Configuration
Sampled Flow (sFlow) is a traffic monitoring technology mainly used to collect and analyze traffic
statistics. The switch supports sFlow feature. The sFlow software agent collects traffic statistics and
packet information from the sFlow-enabled interfaces on the switch, encapsulates them into sFlow
packets. The sFlow agent then sends the packet to a specified sFlow collector, the IP Address you
assigned in the switch UI. The sFlow collector analyzes the sFlow packets and displays the result.

sFlow has the following two sampling mechanisms:

* Flow sampling: Packet-based sampling, used to obtain packet content information.

* Counter sampling: Time-based sampling, used to obtain port traffic statistics.

Type the IP address of sFlow collector in the Receiver Configuration. The sFlow agent will send the
collected information to it.

198
21. Monitor
21.1. Monitor / System

21.1.1. Monitor / System / Information

The switch system information is provided here.

Contact

The system contact configured in Configuration | System | Information | System Contact.

Name

The system name configured in Configuration | System | Information | System Name.

Location

The system location configured in Configuration | System | Information | System Location.

MAC Address

The MAC Address of this switch.

Chip ID

The Chip ID of this switch.

System Date

The current (GMT) system time and date. The system time is obtained through the configured NTP

Server, if any.

System Uptime

199
The period of time the device has been operational.

Software Version

The software version of this switch.

Software Date

The date when the switch software was produced.

Buttons

Auto-refresh: Check this box to enable an automatic refresh of the page at regular intervals.

Refresh: Click to refresh the page; any changes made locally will be undone.

21.1.2. CPU Load

This page displays the CPU load, using an SVG graph.

The load is measured as averaged over the last 100ms, 1sec and 10 seconds intervals. The last 120
samples are graphed, and the last numbers are displayed as text as well.

Buttons:

Auto-refresh: Check this box to enable an automatic refresh of the page at regular intervals.

21.1.3. System Log Information

The switch system log information is provided here.

200
Level

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

Info: Information level of the system log.

Warning: Warning level of the system log.

Error: Error level of the system log.

All: All levels.

Time

The time of the system log entry.

Message

The message of the system log entry.

Buttons

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.
Refresh: Updates the system log entries, starting from the current entry ID.

Clear: Flushes all system log entries.

|<<: Updates the system log entries, starting from the first available entry ID.

<<: Updates the system log entries, ending at the last entry currently displayed.

>>: Updates the system log entries, starting from the last entry currently displayed.

>>|: Updates the system log entries, ending at the last available entry ID.

201
21.1.4. System / Detailed Log

The switch system

detailed log information is provided here.

ID

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

Message

The detailed message of the system log entry.

Buttons

Refresh: Updates the system log entry to the current entry ID.

/<<: Updates the system log entry to the first available entry ID.

<<: Updates the system log entry to the previous available entry ID.

>>: Updates the system log entry to the next available entry ID.

>>/: Updates the system log entry to the last available entry ID.

21.2 Monitor / Port State

21.2.1. Port State

This page provides an overview of the current switch port states.

202
The port states are illustrated as follows:

RJ45 ports

SFP ports

State Disabled Down Link

Buttons

Auto-refresh : Check this box to refresh the page automatically. Automatic refresh occurs at
regular intervals.

Refresh: Click to refresh the page; any changes made locally will be undone.

21.2.2. Traffic Overview

This page provides an overview of general traffic statistics for all switch ports.

The displayed counters are:

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

Filtered

The number of received frames filtered by the forwarding process.

Buttons

Refresh: Click to refresh the page immediately.

Clear: Clears the counters for all ports.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.

21.2.3. QoS Statistics

This page provides statistics for the different queues for all switch ports.

204
The displayed counters are:

Port

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

Qn

There are 8 QoS queues per port. Q0 is the lowest priority queue.

Rx/Tx

The number of received and transmitted packets per queue.

Buttons

Refresh: Click to refresh the page immediately.

Clear: Clears the counters for all ports.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.

21.2.4. QCL Status


This page shows the QCL status by different QCL users. Each row describes the QCE that is defined. It

is a conflict if a specific QCE is not applied to the hardware due to hardware limitations. The maximum

number of QCEs is 256 on each switch.

205
User

Indicates the QCL user.

QCE#

Indicates the index of QCE.

Frame Type

Indicates the type of frame to look for incoming frames. Possible frame types are:

Any: The QCE will match all frame type.

Ethernet: Only Ethernet frames (with Ether Type 0x600-0xFFFF) are allowed.

LLC: Only (LLC) frames are allowed.

SNAP: Only (SNAP) frames are allowed.

IPv4: The QCE will match only IPV4 frames.

IPv6: The QCE will match only IPV6 frames.

Port

Indicates the list of ports configured with the QCE.

Action

Indicates the classification action taken on ingress frame if parameters configured are matched with the

frame's content.

There are three action fields: Class, DPL and DSCP.

Class: Classified QoS class; if a frame matches the QCE it will be put in the queue.

DPL: Drop Precedence Level; if a frame matches the QCE then DP level will set to value displayed

under DPL column.

DSCP: If a frame matches the QCE then DSCP will be classified with the value displayed under DSCP

column.

Conflict

206
Displays Conflict status of QCL entries. As H/W resources are shared by multiple applications. It may

happen that resources required to add a QCE may not be available, in that case it shows conflict status

as 'Yes', otherwise it is always 'No'. Please note that conflict can be resolved by releasing the H/W

resources required to add QCL entry on pressing 'Resolve Conflict' button.

Buttons

: Select the QCL status from this drop down list.

Auto-refresh : Check this box to refresh the page automatically. Automatic refresh occurs at
regular intervals.

Resolve Conflict: Click to release the resources required to add QCL entry, incase conflict status for

any QCL entry is 'yes'.

Refresh: Click to refresh the page; any changes made locally will be undone

21.2.5. Detailed Port Statistics

This page provides detailed traffic statistics for a specific switch port. Use the port select box to select
which switch port details to display.

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.

207
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 and Transmit Queue Counters


The number of received and transmitted packets per input and output queue.

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

1
The number of short frames received with valid CRC.

Rx Oversize

208
2
The number of long frames received with valid CRC.

Rx Fragments

1
The number of short 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.

1
Short frames are frames that are smaller than 64 bytes.

2
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

The port select box determines which port is affected by clicking the buttons.

Refresh: Click to refresh the page immediately.

Clear: Clears the counters for the selected port.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular
intervals.

21.3. Monitor / Security

21.3.1. Security / Access Management Statistics

This page provides statistics for access management.

209
Interface

The interface type through which the remote host can access the switch.

Received Packets

Number of received packets from the interface when access management mode is enabled.

Allowed Packets

Number of allowed packets from the interface when access management mode is enabled.

Discarded Packets

Number of discarded packets from the interface when access management mode is enabled.

Buttons

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

Refresh: Click to refresh the page immediately.

Clear: Clear all statistics.

21.3.2. Security / Network

Port Security Switch Status

This page shows the Port Security status. Port Security is a module with no direct configuration.
Configuration comes indirectly from other modules - the user modules. When a user module has
enabled port security on a port, the port is set-up for software-based learning. In this mode, frames from
unknown MAC addresses are passed on to the port security module, which in turn asks all user modules
whether to allow this new MAC address to forward or block it. For a MAC address to be set in the
forwarding state, all enabled user modules must unanimously agree on allowing the MAC address to
forward. If only one chooses to block it, it will be blocked until that user module decides otherwise.
The status page is divided into two sections - one with a legend of user modules and one with the actual
port status.

210
User Module Legend

The legend shows all user modules that may request Port Security services.

User Module Name

The full name of a module that may request Port Security services.

Abbr

A one-letter abbreviation of the user module. This is used in the Users column in the port status table.

Port Status

The table has one row for each port on the switch and a number of columns, which are:

Port

The port number for which the status applies. Click the port number to see the status for this particular

port.

Users

Each of the user modules has a column that shows whether that module has enabled Port Security or

not. A '-' means that the corresponding user module is not enabled, whereas a letter indicates that the

user module abbreviated by that letter (see Abbr) has enabled port security.

State

Shows the current state of the port. It can take one of four values:

211
Disabled: No user modules are currently using the Port Security service.

Ready: The Port Security service is in use by at least one user module, and is awaiting frames from

unknown MAC addresses to arrive.

Limit Reached: The Port Security service is enabled by at least the Limit Control user module, and that

module has indicated that the limit is reached and no more MAC addresses should be taken in.

Shutdown: The Port Security service is enabled by at least the Limit Control user module, and that

module has indicated that the limit is exceeded. No MAC addresses can be learned on the port until it is

administratively re-opened on the Limit Control configuration Web-page.

MAC Count (Current, Limit)

The two columns indicate the number of currently learned MAC addresses (forwarding as well as

blocked) and the maximum number of MAC addresses that can be learned on the port, respectively.

If no user modules are enabled on the port, the Current column will show a dash (-).

If the Limit Control user module is not enabled on the port, the Limit column will show a dash (-).

Buttons

Refresh: Click to refresh the page immediately.

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

Port Security Port Status

This page shows the MAC addresses secured by the Port Security module. Port Security is a module
with no direct configuration. Configuration comes indirectly from other modules - the user modules.
When a user module has enabled port security on a port, the port is set-up for software-based learning.
In this mode, frames from unknown MAC addresses are passed on to the port security module, which in
turn asks all user modules whether to allow this new MAC address to forward or block it. For a MAC
address to be set in the forwarding state, all enabled user modules must unanimously agree on allowing
the MAC address to forward. If only one chooses to block it, it will be blocked until that user module
decides otherwise.

212
MAC Address & VLAN ID

The MAC address and VLAN ID that is seen on this port. If no MAC addresses are learned, a single
row stating "No MAC addresses attached" is displayed.

State

Indicates whether the corresponding MAC address is blocked or forwarding. In the blocked state, it will
not be allowed to transmit or receive traffic.

Time of Addition

Shows the date and time when this MAC address was first seen on the port.

Age/Hold

If at least one user module has decided to block this MAC address, it will stay in the blocked state until
the hold time (measured in seconds) expires. If all user modules have decided to allow this MAC
address to forward, and aging is enabled, the Port Security module will periodically check that this MAC
address still forwards traffic. If the age period (measured in seconds) expires and no frames have been
seen, the MAC address will be removed from the MAC table. Otherwise a new age period will begin.
If aging is disabled or a user module has decided to hold the MAC address indefinitely, a dash (-) will
be shown.

Buttons

Refresh: Click to refresh the page immediately.

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

213
Security / Network / NAS

This page provides an overview of the current NAS port states.

Port

The switch port number. Click to navigate to detailed NAS statistics for this port.

Admin State

The port's current administrative state. Refer to NAS Admin State for a description of possible values.

Port State

The current state of the port. Refer to NAS Port State for a description of the individual states.

Last Source

The source MAC address carried in the most recently received EAPOL frame for EAPOL-based

authentication, and the most recently received frame from a new client for MAC-based authentication.

Last ID

The user name (supplicant identity) carried in the most recently received Response Identity EAPOL

frame for EAPOL-based authentication, and the source MAC address from the most recently received

frame from a new client for MAC-based authentication.

QoS Class

QoS Class assigned to the port by the RADIUS server if enabled.

Port VLAN ID

The VLAN ID that NAS has put the port in. The field is blank, if the Port VLAN ID is not overridden by

NAS.

If the VLAN ID is assigned by the RADIUS server, "(RADIUS-assigned)" is appended to the VLAN ID.

214
Read more about RADIUS-assigned VLANs here.

If the port is moved to the Guest VLAN, "(Guest)" is appended to the VLAN ID. Read more about Guest

VLANs here.

Buttons

Refresh: Click to refresh the page immediately.

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

Port State

Admin State

The port's current administrative state. Refer to NAS Admin State for a description of possible values.

Port State

The current state of the port. Refer to NAS Port state for a description of the individual states.

QoS Class

The QoS class assigned by the RADIUS server. The field is blank if no QoS class is assigned.

Port VLAN ID

The VLAN ID that NAS has put the port in. The field is blank, if the Port VLAN ID is not overridden by

NAS.

If the VLAN ID is assigned by the RADIUS server, "(RADIUS-assigned)" is appended to the VLAN ID.

Read more about RADIUS-assigned VLANs here.

If the port is moved to the Guest VLAN, "(Guest)" is appended to the VLAN ID. Read more about Guest

VLANs here.

Port Counters

EAPOL Counters

These supplicant frame counters are available for the following administrative states:

• Force Authorized

• Force Unauthorized

• Port-based 802.1X

• Single 802.1X

• Multi 802.1X

215
EAPOL Counters

Direction Name IEEE Name Description

The number of valid EAPOL frames

Rx Total dot1xAuthEapolFramesRx of any type that have been received

by the switch.

The number of valid EAPOL


Response
Rx dot1xAuthEapolRespIdFramesRx Response Identity frames that have
ID
been received by the switch.

The number of valid EAPOL

response frames (other than


Rx Responses dot1xAuthEapolRespFramesRx
Response Identity frames) that have

been received by the switch.

The number of EAPOL Start frames

Rx Start dot1xAuthEapolStartFramesRx that have been received by the

switch.

The number of valid EAPOL Logoff

Rx Logoff dot1xAuthEapolLogoffFramesRx frames that have been received by

the switch.

The number of EAPOL frames that

Invalid have been received by the switch in


Rx dot1xAuthInvalidEapolFramesRx
Type which the frame type is not

recognized.

The number of EAPOL frames that

Invalid have been received by the switch in


Rx dot1xAuthEapLengthErrorFramesRx
Length which the Packet Body Length field

is invalid.

The number of EAPOL frames of

Tx Total dot1xAuthEapolFramesTx any type that have been transmitted

by the switch.

The number of EAPOL Request

Tx Request ID dot1xAuthEapolReqIdFramesTx Identity frames that have been

transmitted by the switch.

The number of valid EAPOL

Request frames (other than Request


Tx Requests dot1xAuthEapolReqFramesTx
Identity frames) that have been

transmitted by the switch.

216
Backend Server Counters

These backend (RADIUS) frame counters are available for the following administrative states:

• Port-based 802.1X

• Single 802.1X

• Multi 802.1X

• MAC-based Auth.

Backend Server Counters

Direction Name IEEE Name Description

802.1X-based:

Counts the number of

times that the switch

receives the first

request from the


backend server

following the first

response from the

supplicant. Indicates

that the backend


Access
Rx dot1xAuthBackendAccessChallenges server has
Challenges
communication with

the switch.

MAC-based:

Counts all Access


Challenges received

from the backend

server for this port

(left-most table) or

client (right-most

table).

802.1X-based:

Counts the number of

times that the switch

Other sends an EAP


Rx dot1xAuthBackendOtherRequestsToSupplicant
Requests Request packet

following the first to the

supplicant. Indicates

that the backend

217
server chose an

EAP-method.

MAC-based:

Not applicable.

802.1X- and

MAC-based:

Counts the number of

times that the switch

receives a success
Auth.
Rx dot1xAuthBackendAuthSuccesses indication. Indicates
Successes
that the

supplicant/client has

successfully

authenticated to the

backend server.

802.1X- and

MAC-based:

Counts the number of

times that the switch

Auth. receives a failure


Rx dot1xAuthBackendAuthFails
Failures message. This

indicates that the

supplicant/client has

not authenticated to
the backend server.

802.1X-based:

Counts the number of

times that the switch

attempts to send a

supplicant's first

response packet to the

Tx Responses dot1xAuthBackendResponses backend server.

Indicates the switch

attempted

communication with

the backend server.

Possible

retransmissions are

218
not counted.

MAC-based:

Counts all the backend

server packets sent

from the switch

towards the backend

server for a given port

(left-most table) or

client (right-most

table). Possible

retransmissions are

not counted.

Last Supplicant/Client Info

Information about the last supplicant/client that attempted to authenticate. This information is available

for the following administrative states:

• Port-based 802.1X

• Single 802.1X

• Multi 802.1X

• MAC-based Auth.

Last Supplicant/Client Info

Name IEEE Name Description

MAC
dot1xAuthLastEapolFrameSource The MAC address of the last supplicant/client.
Address

The VLAN ID on which the last frame from the last


VLAN ID -
supplicant/client was received.

802.1X-based:

The protocol version number carried in the most

Version dot1xAuthLastEapolFrameVersion recently received EAPOL frame.

MAC-based:

Not applicable.

802.1X-based:

The user name (supplicant identity) carried in the

Identity - most recently received Response Identity EAPOL

frame.

MAC-based:

219
Not applicable.

Selected Counters

Selected Counters

The Selected Counters table is visible when the port is in one of the following administrative states:

• Multi 802.1X

• MAC-based Auth.

The table is identical to and is placed next to the Port Counters table, and will be empty if no MAC

address is currently selected. To populate the table, select one of the attached MAC Addresses from

the table below.

Attached MAC Addresses

Identity

Shows the identity of the supplicant, as received in the Response Identity EAPOL frame.

Clicking the link causes the supplicant's EAPOL and Backend Server counters to be shown in the
Selected Counters table. If no supplicants are attached, it shows No supplicants attached.

This column is not available for MAC-based Auth.

MAC Address

For Multi 802.1X, this column holds the MAC address of the attached supplicant.

For MAC-based Auth., this column holds the MAC address of the attached client.

Clicking the link causes the client's Backend Server counters to be shown in the Selected Counters
table. If no clients are attached, it shows No clients attached.

VLAN ID

This column holds the VLAN ID that the corresponding client is currently secured through the Port

Security module.

State

The client can either be authenticated or unauthenticated. In the authenticated state, it is allowed to

forward frames on the port, and in the unauthenticated state, it is blocked. As long as the backend

server hasn't successfully authenticated the client, it is unauthenticated. If an authentication fails for

one or the other reason, the client will remain in the unauthenticated state for Hold Time seconds.

Last Authentication

Shows the date and time of the last authentication of the client (successful as well as unsuccessful).

220
Buttons
The port select box determines which port is affected when clicking the buttons.

Auto-refresh

Check this box to enable an automatic refresh of the page at regular intervals.

Click to refresh the page immediately.

This button is available in the following modes:

• Force Authorized

• Force Unauthorized

• Port-based 802.1X

• Single 802.1X

Click to clear the counters for the selected port.

This button is available in the following modes:

• Multi 802.1X

• MAC-based Auth.X

Click to clear both the port counters and all of the attached client's counters. The "Last Client" will not

be cleared, however.

This button is available in the following modes:

• Multi 802.1X

• MAC-based Auth.X

Click to clear only the currently selected client's counters.

221
Network / ACL Status

This page shows the ACL status by different ACL users. Each row describes the ACE that is defined. It

is a conflict if a specific ACE is not applied to the hardware due to hardware limitations. The maximum
number of ACEs is 256 on each switch.

User

Indicates the ACL user.

Ingress Port

Indicates the ingress port of the ACE. Possible values are:

All: The ACE will match all ingress port.

Port: The ACE will match a specific ingress port.

Frame Type

Indicates the frame type of the ACE. Possible values are:

Any: The ACE will match any frame type.

EType: The ACE will match Ethernet Type frames. Note that an Ethernet Type based ACE will not get

matched by IP and ARP frames.

ARP: The ACE will match ARP/RARP frames.

IPv4: The ACE will match all IPv4 frames.

IPv4/ICMP: The ACE will match IPv4 frames with ICMP protocol.

IPv4/UDP: The ACE will match IPv4 frames with UDP protocol.

IPv4/TCP: The ACE will match IPv4 frames with TCP protocol.

IPv4/Other: The ACE will match IPv4 frames, which are not ICMP/UDP/TCP.

222
IPv6: The ACE will match all IPv6 standard frames.

Action

Indicates the forwarding action of the ACE.

Permit: Frames matching the ACE may be forwarded and learned.

Deny: Frames matching the ACE are dropped.

Rate Limiter

Indicates the rate limiter number of the ACE. The allowed range is 1 to 16. When Disabled is displayed,

the rate limiter operation is disabled.

Port Copy

Indicates the port copy operation of the ACE. Frames matching the ACE are copied to the port number.

The allowed values are Disabled or a specific port number. When Disabled is displayed, the port copy

operation is disabled.

Mirror

Specify the mirror operation of this port. The allowed values are:

Enabled: Frames received on the port are mirrored.

Disabled: Frames received on the port are not mirrored.

The default value is "Disabled".

CPU

Forward packet that matched the specific ACE to CPU.

CPU Once

Forward first packet that matched the specific ACE to CPU.

Counter

The counter indicates the number of times the ACE was hit by a frame.

Conflict

Indicates the hardware status of the specific ACE. The specific ACE is not applied to the hardware due

to hardware limitations.

223
Buttons

: Select the ACL status from this drop down list.

Refresh: Click to refresh the page immediately.

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

DHCP Snooping Statistics

This page provides statistics for DHCP snooping. The statistics show only packet counters when DHCP
snooping mode is enabled and relay mode is disabled. And it doesn't count the DHCP packets for
DHCP client.

Receive and Transmit Packets

224
Rx and Tx Discover

The number of discover (option 53 with value 1) packets received and transmitted.

Rx and Tx Offer

The number of offer (option 53 with value 2) packets received and transmitted.

Rx and Tx Request

The number of request (option 53 with value 3) packets received and transmitted.

Rx and Tx Decline

The number of decline (option 53 with value 4) packets received and transmitted.

Rx and Tx ACK

The number of ACK (option 53 with value 5) packets received and transmitted.

Rx and Tx NAK

The number of NAK (option 53 with value 6) packets received and transmitted.

Rx and Tx Release

The number of release (option 53 with value 7) packets received and transmitted.

Rx and Tx Inform

The number of inform (option 53 with value 8) packets received and transmitted.

Rx and Tx Lease Query

The number of lease query (option 53 with value 10) packets received and transmitted.

Rx and Tx Lease Unassigned

The number of lease unassigned (option 53 with value 11) packets received and transmitted.

Rx and Tx Lease Unknown

The number of lease unknown (option 53 with value 12) packets received and transmitted.

Rx and Tx Lease Active

The number of lease active (option 53 with value 13) packets received and transmitted.

Buttons

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

Refresh: Click to refresh the page immediately.

Clear: Clears the counters for the selected port.

225
DHCP Relay Statistics

This page provides statistics for DHCP relay.

Server Statistics

Transmit to Server

The number of packets that are relayed from client to server.

Transmit Error

The number of packets that resulted in errors while being sent to clients.

Receive from Server

The number of packets received from server.

Receive Missing Agent Option

The number of packets received without agent information options.

Receive Missing Circuit ID

The number of packets received with the Circuit ID option missing.

Receive Missing Remote ID

The number of packets received with the Remote ID option missing.

Receive Bad Circuit ID

The number of packets whose Circuit ID option did not match known circuit ID.

226
Receive Bad Remote ID

The number of packets whose Remote ID option did not match known Remote ID.

Client Statistics

Transmit to Client

The number of relayed packets from server to client.

Transmit Error

The number of packets that resulted in error while being sent to servers.

Receive from Client

The number of received packets from server.

Receive Agent Option

The number of received packets with relay agent information option.

Replace Agent Option

The number of packets which were replaced with relay agent information option.

Keep Agent Option

The number of packets whose relay agent information was retained.

Drop Agent Option

The number of packets that were dropped which were received with relay agent information.

Buttons

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

Refresh: Click to refresh the page immediately.

Clear: Clears statistics.

Network / Dynamic ARP Inspection Table

Entries in the Dynamic ARP Inspection Table are shown on this page. The Dynamic ARP Inspection
Table contains up to 1024 entries, and is sorted first by port, then by VLAN ID, then by MAC address,
and then by IP address.

Navigating the ARP Inspection Table

Each page shows up to 99 entries from the Dynamic ARP Inspection table, default being 20, selected
through the "entries per page" input field. When first visited, the web page will show the first 20 entries

227
from the beginning of the Dynamic ARP Inspection Table.
The "Start from port address", "VLAN", "MAC address" and "IP address" input fields allow the user to
select the starting point in the Dynamic ARP Inspection Table. Clicking the button will update the
displayed table starting from that or the closest next Dynamic ARP Inspection Table match. In addition,
the two input fields will - upon a button click - assume the value of the first displayed entry, allowing for
continuous refresh with the same start address.
The will use the last entry of the currently displayed table as a basis for the next lookup. When the end
is reached the text "No more entries" is shown in the displayed table. Use the button to start over.

ARP Inspection Table Columns

Port

Switch Port Number for which the entries are displayed.

VLAN ID

VLAN-ID in which the ARP traffic is permitted.

MAC Address

228
User MAC address of the entry.

IP Address

User IP address of the entry.

Buttons

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

Refresh: Click to refresh the page immediately.

Clear: Flushes all dynamic entries.

/<<: Updates the table starting from the first entry in the Dynamic ARP Inspection Tables.

>>: Updates the table, starting with the entry after the last entry currently displayed.

Network / Dynamic IP Source Guard Table

Entries in the Dynamic IP Source Guard Table are shown on this page. The Dynamic IP Source Guard
Table is sorted first by port, then by VLAN ID, then by IP address, and then by MAC address.

Navigating the IP Source Guard Table

Each page shows up to 99 entries from the Dynamic IP Source Guard table, default being 20, selected
through the "entries per page" input field. When first visited, the web page will show the first 20 entries
from the beginning of the Dynamic IP Source Guard Table.
The "Start from port address", "VLAN" and "IP address" input fields allow the user to select the starting
point in the Dynamic IP Source Guard Table. Clicking the button will update the displayed table starting
from that or the closest next Dynamic IP Source Guard Table match. In addition, the two input fields will
- upon a button click - assume the value of the first displayed entry, allowing for continuous refresh with
the same start address.
The will use the last entry of the currently displayed table as a basis for the next lookup. When the end
is reached the text "No more entries" is shown in the displayed table. Use the button to start over.

229
IP Source Guard Table Columns

Port

Switch Port Number for which the entries are displayed.

VLAN ID

VLAN-ID in which the IP traffic is permitted.

IP Address

User IP address of the entry.

MAC Address

Source MAC address.

Buttons

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

Refresh: Click to refresh the page immediately.

Clear: Flushes all dynamic entries.

/<<: Updates the table starting from the first entry in the Dynamic IP Source Guard Tables.

>>: Updates the table, starting with the entry after the last entry currently displayed.

21.3.3. Security / AAA


This page provides an overview of the status of the RADIUS servers configurable on the Authentication

configuration page.

RADIUS Authentication Servers

230
#

The RADIUS server number. Click to navigate to detailed statistics for this server.

IP Address

The IP address and UDP port number (in <IP Address>:<UDP Port> notation) of this server.

State

The current state of the server. This field takes one of the following values:

Disabled: The server is disabled.

Not Ready: The server is enabled, but IP communication is not yet up and running.

Ready: The server is enabled, IP communication is up and running, and the RADIUS module is ready

to accept access attempts.

Dead (X seconds left): Access attempts were made to this server, but it did not reply within the

configured timeout. The server has temporarily been disabled, but will get re-enabled when the

dead-time expires. The number of seconds left before this occurs is displayed in parentheses. This

state is only reachable when more than one server is enabled.

RADIUS Accounting Servers

The RADIUS server number. Click to navigate to detailed statistics for this server.

IP Address

The IP address and UDP port number (in <IP Address>:<UDP Port> notation) of this server.

State

The current state of the server. This field takes one of the following values:

Disabled: The server is disabled

Not Ready: The server is enabled, but IP communication is not yet up and running.

Ready: The server is enabled, IP communication is up and running, and the RADIUS module is ready

to accept accounting attempts.

Dead (X seconds left): Accounting attempts were made to this server, but it did not reply within the

configured timeout. The server has temporarily been disabled, but will get re-enabled when the

dead-time expires. The number of seconds left before this occurs is displayed in parentheses. This

state is only reachable when more than one server is enabled.

Buttons

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

Refresh: Click to refresh the page immediately.

231
RADIUS Authentication Statistics
This page provides detailed statistics for a particular RADIUS server.

RADIUS Authentication Statistics

The statistics map closely to those specified in RFC4668-RADIUS.Authentication Client MIB.

Use the server select box to switch between the backend servers to show details for.

Packet Counters

RADIUS authentication server packet counter. There are seven receive and four transmit counters.

Direction Name RFC4668 Name Description

radiusAuthClientExtAccess The number of RADIUS Access-Accept packets


Rx Access Accepts
Accepts (valid or invalid) received from the server.

radiusAuthClientExtAccess The number of RADIUS Access-Reject packets


Rx Access Rejects
Rejects (valid or invalid) received from the server.

The number of RADIUS Access-Challenge


Access radiusAuthClientExtAcc
Rx packets (valid or invalid) received from the
Challenges essChallenges
server.

The number of malformed RADIUS


Malformed radiusAuthClientExtMalf Access-Response packets received from

Rx Access ormedAccessResponse the server. Malformed packets include


Responses s packets with an invalid length. Bad

authenticators or Message Authenticator

232
attributes or unknown types are not included

as malformed access responses.

The number of RADIUS Access-Response

Bad radiusAuthClientExtBad packets containing invalid authenticators or


Rx
Authenticators Authenticators Message Authenticator attributes received

from the server.

The number of RADIUS packets that were


radiusAuthClientExtUnk
Rx Unknown Types received with unknown types from the server
nownTypes
on the authentication port and dropped.

The number of RADIUS packets that were


Radius Auth Client received from the server on the
Rx Packets Dropped
Ext-Packets Dropped authentication port and dropped for some

other reason.

Radius The number of RADIUS Access-Request

Tx Access Requests AuthClientExtAccess packets sent to the server. This does not
Requests include retransmissions.

Access The number of RADIUS Access-Request


radiusAuthClientExtAcc
Tx Retransmission packets retransmitted to the RADIUS
essRetransmissions
s authentication server.

The number of RADIUS Access-Request

packets destined for the server that have not

yet timed out or received a response. This

Pending radiusAuthClientExtPen variable is incremented when an


Tx
Requests dingRequests Access-Request is sent and decremented
due to receipt of an Access-Accept,

Access-Reject, Access-Challenge, timeout,

or retransmission.

The number of authentication timeouts to

the server. After a timeout, the client may

retry to the same server, send to a different


radiusAuthClientExtTimeou
Tx Timeouts server, or give up. A retry to the same server
ts
is counted as a retransmit as well as a

timeout. A send to a different server is

counted as a Request as well as a timeout.

Other Info

This section contains information about the state of the server and the latest round-trip time.

233
Name RFC4668 Name Description

Shows the state of the server. It takes one of the following values:

Disabled: The selected server is disabled.

Not Ready: The server is enabled, but IP communication is not yet up

and running.

Ready: The server is enabled, IP communication is up and running, and

the RADIUS module is ready to accept access attempts.


State -
Dead (X seconds left): Access attempts were made to this server,

but it did not reply within the configured timeout. The server has

temporarily been disabled, but will get re-enabled when the dead-time

expires. The number of seconds left before this occurs is displayed in

parentheses. This state is only reachable when more than one server is

enabled.

The time interval (measured in milliseconds) between the most recent

Radius Access-Reply/Access-Challenge and the Access-Request that matched


Round-Trip
AuthClientExtRoundTrip it from the RADIUS authentication server. The granularity of this
Time
Time measurement is 100 ms. A value of 0 ms indicates that there hasn't been

round-trip communication with the server yet.

RADIUS Accounting Statistics

The statistics map closely to those specified in RFC4670-RADIUS.Accounting Client MIB.


Use the server select box to switch between the backend servers to show details for.

Packet Counters

RADIUS accounting server packet counter. There are five receive and four transmit counters.

Direction Name RFC4670 Name Description

234
radiusAccClientExtRespons The number of RADIUS packets (valid or
Rx Responses
es invalid) received from the server.

The number of malformed RADIUS packets

received from the server. Malformed

Malformed radiusAccClientExtMalform packets include packets with an invalid


Rx
Responses edResponses length. Bad authenticators or unknown

types are not included as malformed access

responses.

The number of RADIUS packets containing


Bad radiusAcctClientExtBadAut
Rx invalid authenticators received from the
Authenticators henticators
server.

The number of RADIUS packets of unknown


radiusAccClientExtUnknow
Rx Unknown Types types that were received from the server on
nTypes
the accounting port.

The number of RADIUS packets that were


Packets radiusAccClientExtPackets
Rx received from the server on the accounting
Dropped Dropped
port and dropped for some other reason.

The number of RADIUS packets sent to the


radiusAccClientExtRequest
Tx Requests server. This does not include
s
retransmissions.

The number of RADIUS packets


radiusAccClientExtRetrans
Tx Retransmissions retransmitted to the RADIUS accounting
missions
server.

The number of RADIUS packets destined

for the server that have not yet timed out or

Pending radiusAccClientExtPending received a response. This variable is


Tx
Requests Requests incremented when a Request is sent and

decremented due to receipt of a Response,

timeout, or retransmission.

The number of accounting timeouts to the

server. After a timeout, the client may retry

to the same server, send to a different


radiusAccClientExtTimeout
Tx Timeouts server, or give up. A retry to the same server
s
is counted as a retransmit as well as a

timeout. A send to a different server is

counted as a Request as well as a timeout.

Other Info

235
This section contains information about the state of the server and the latest round-trip time.

Name RFC4670 Name Description

Shows the state of the server. It takes one of the following values:

Not Ready:
Disabled: The selected server is disabled.

Not Ready: The server is enabled, but IP communication is not yet

up and running.

aReady: The server is enabled, IP communication is up and

running, and the RADIUS module is ready to accept accounting


State -
attempts.
Dead (X seconds left): Accounting attempts were made to this

server, but it did not reply within the configured timeout. The server

has temporarily been disabled, but will get re-enabled when the

dead-time expires. The number of seconds left before this occurs is

displayed in parentheses. This state is only reachable when more

than one server is enabled.

The time interval (measured in milliseconds) between the most

recent Response and the Request that matched it from the


Round-Trip radiusAccClientExtRoun
RADIUS accounting server. The granularity of this measurement is
Time dTripTime
100 ms. A value of 0 ms indicates that there hasn't been round-trip

communication with the server yet.

Buttons
The server select box determines which server is affected by clicking the buttons.

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

Refresh: Click to refresh the page immediately.

Clear: Clears the counters for the selected server. The “Pending Requests” counter will not be cleared

by this operations..

21.3.4. Switch / SNMP / RMON

RMON Statistics Overview

This page provides an overview of RMON statistics entries.

236
The displayed counters are:

Data Source

The port ID which wants to be monitored.

Drop

The total number of events in which packets were dropped by the probe due to lack of resources.

Octets

The total number of octets of data (including those in bad packets) received on the network.

Pkts

The total number of packets (including bad packets, broadcast packets, and multicast packets)

received.

Broad-cast

The total number of good packets received that were directed to the broadcast address.

Multi-cast

The total number of good packets received that were directed to a multicast address.

CRC Errors

The total number of packets received that had a length (excluding framing bits, but including FCS

octets) of between 64 and 1518 octets.

Under-size

The total number of packets received that were less than 64 octets.

Over-size

237
The total number of packets received that were longer than 1518 octets.

Frag.

The number of frames which size is less than 64 octets received with invalid CRC.

Jabb.

The number of frames which size is larger than 64 octets received with invalid CRC.

Coll.

The best estimate of the total number of collisions on this Ethernet segment.

64

The total number of packets (including bad packets) received that were 64 octets in length.

65~127

The total number of packets (including bad packets) received that were between 65 to 127 octets in

length.

128~255

The total number of packets (including bad packets) received that were between 128 to 255 octets in

length.

256~511

The total number of packets (including bad packets) received that were between 256 to 511 octets in

length.

512~1023

The total number of packets (including bad packets) received that were between 512 to 1023 octets in

length.

1024~1588

The total number of packets (including bad packets) received that were between 1024 to 1588 octets in

length.

Buttons

Refresh: Click to refresh the page immediately.

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

238
RMON History Overview

This page provides an overview of RMON history entries.

The displayed fields are:

History Index

Indicates the index of History control entry.

Sample Index

Indicates the index of the data entry associated with the control entry

Sample Start

The total number of events in which packets were dropped by the probe due to lack of resources.

Drops

The total number of events in which packets were dropped by the probe due to lack of resources.

Octets

The total number of octets of data (including those in bad packets) received on the network.

Pkts

The total number of packets (including bad packets, broadcast packets, and multicast packets)

received.

Broadcast

The total number of good packets received that were directed to the broadcast address.

Multicast

239
The total number of good packets received that were directed to a multicast address.

CRCErrors

The total number of packets received that had a length (excluding framing bits, but including FCS

octets) of between 64 and 1518 octets.

Undersize

The total number of packets received that were less than 64 octets.

Oversize

The total number of packets received that were longer than 1518 octets.

Frag.

The number of frames which size is less than 64 octets received with invalid CRC.

Jabb.

The number of frames which size is larger than 64 octets received with invalid CRC.

Coll.

The best estimate of the total number of collisions on this Ethernet segment.

Utilization

The best estimate of the mean physical layer network utilization on this interface during this sampling

interval, in hundredths of a percent.

Buttons

Refresh: Click to refresh the page immediately.

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

RMON Alarm Overview

This page provides an overview of RMON alarm entries.

The displayed fields are:

240
ID

Indicates the index of Alarm control entry.

Interval

Indicates the interval in seconds for sampling and comparing the rising and falling threshold.

Variable

Indicates the particular variable to be sampled

Sample Type

The method of sampling the selected variable and calculating the value to be compared against the

thresholds, possible sample types are:

Rising Threshold

Rising threshold value.

Rising Index

Rising event index.

Falling Threshold

Falling threshold value.

Falling Index

Falling event index.

Buttons

Refresh: Click to refresh the page immediately.

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

241
RMON Event Overview

This page provides an overview of RMON event entries.

The displayed fields are:

Event Index

Indicates the index of the event entry.

Log Index

Indicates the index of the log entry.

Log Time

Indicates Event log time

Log Description

Indicates the Event description.

Buttons

Refresh: Click to refresh the page immediately.

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

242
21.4. LACP System Status

21.4.1. System Status


This page provides a status overview for all LACP instances.

Aggr ID

The Aggregation ID associated with this aggregation instance. For LLAG the id is shown as

'isid:aggr-id' and for GLAGs as 'aggr-id'

Partner System ID

The system ID (MAC address) of the aggregation partner.

Partner Key

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

Last changed

The time since this aggregation changed.

Local Ports

Shows which ports are a part of this aggregation for this switch.

Buttons

Refresh: Click to refresh the page immediately.

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

21.4.2. LACP Port Status

This page provides a status overview for LACP status for all ports.

243
Port

The switch port number.

LACP

'Yes' means that LACP is enabled and the port link is up. 'No' means that LACP is not enabled or that

the port link is down. 'Backup' means that the port could not join the aggregation group but will join if

other port leaves. Meanwhile its LACP status is disabled.

Key

The key assigned to this port. Only ports with the same key can aggregate together.

Aggr ID

The Aggregation ID assigned to this aggregation group.

Partner System ID

The partner's System ID (MAC address).

Partner Port

The partner's port number connected to this port.

Buttons

Refresh: Click to refresh the page immediately.

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

244
21.4.3. LACP statistics

This page provides an overview for LACP statistics for all ports.

Port

The switch port number.

LACP Received

Shows how many LACP frames have been received at each port.

LACP Transmitted

Shows how many LACP frames have been sent from each port.

Discarded

Shows how many unknown or illegal LACP frames have been discarded at each port.

Buttons

Auto-refresh: Click this box to enable an automatic refresh of the page at regular intervals.

Refresh: Click to refresh the page immediately.

Clear: Clears the counters for all ports.

21.5. Loop Protection

This page displays the loop protection port status the ports of theswitch.

245
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

Refresh: Click to refresh the page immediately.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.

21.6. STP Bridge Status

This page provides a status overview of all STP bridge instances.

246
21.6.1. Bridge Status

The displayed table contains a row for each STP bridge instance, where the column displays the

following information:

MSTI

The Bridge Instance. This is also a link to the STP Detailed Bridge Status

Bridge ID

The Bridge ID of this Bridge instance.

Root ID

The Bridge ID of the currently elected root bridge.

Root Port

The switch port currently assigned the root port role.

Root Cost

Root Path Cost. For the Root Bridge it is zero. For all other Bridges, it is the sum of the Port Path Costs

on the least cost path to the Root Bridge.

Topology Flag

The current state of the Topology Change Flag of this Bridge instance.

Topology Change Last

The time since last Topology Change occurred.

Buttons

Refresh: Click to refresh the page immediately.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.

247
21.6.2. STP Port Status

This page displays the STP CIST port status for physical ports of the switch.

STP port status is:

Port

The switch port number of the logical STP port.

CIST Role

The current STP port role of the CIST port. The port role can be one of the following values:

AlternatePort BackupPort RootPort DesignatedPort Disabled.

CIST State

The current STP port state of the CIST port. The port state can be one of the following values:

Discarding Learning Forwarding.

Uptime

The time since the bridge port was last initialized.

Buttons

Refresh: Click to refresh the page immediately.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.

21.6.3. STP Port Statistics


This page displays the STP port statistics counters of bridge ports in the switch.

248
The STP port statistics counters are:

Port

The switch port number of the logical STP port.

MSTP

The number of MSTP Configuration BPDU's received/transmitted on the port.

RSTP

The number of RSTP Configuration BPDU's received/transmitted on the port.

STP

The number of legacy STP Configuration BPDU's received/transmitted on the port.

TCN

The number of (legacy) Topology Change Notification BPDU's received/transmitted on the port.

Discarded Unknown

The number of unknown Spanning Tree BPDU's received (and discarded) on the port.

Discarded Illegal

The number of illegal Spanning Tree BPDU's received (and discarded) on the port.

Buttons

Refresh: Click to refresh the page immediately.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.

249
21.7. MVR Status

21.7.1. Statistics

This page provides MVR Statistics information.

VLAN ID

The Multicast VLAN ID.

V1 Reports Received

The number of Received V1 Reports.

V2 Reports Received

The number of Received V2 Reports.

V3 Reports Received

The number of Received V3 Reports.

V2 Leaves Received

The number of Received V2 Leaves.

Buttons

Refresh: Click to refresh the page immediately.

Clear: Clears all Statistics counters.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.

250
21.7.2. MVR Group Table

Entries in the MVR Group Table are shown on this page. The MVR Group Table is sorted first by VLAN

ID, and then by group.

Navigating the MVR Group Table

Each page shows up to 99 entries from the MVR Group table, default being 20, selected through the
"entries per page" input field. When first visited, the web page will show the first 20 entries from the
beginning of the MVR Group Table.
The "Start from VLAN", and "group" input fields allow the user to select the starting point in the MVR
Group Table. Clicking the Refresh button will update the displayed table starting from that or the
closest next MVR Group Table match. In addition, the two input fields will - upon a Refresh button click
- assume the value of the first displayed entry, allowing for continuous refresh with the same start
address.
The >> will use the last entry of the currently displayed table as a basis for the next lookup. When the
end is reached the text "No more entries" is shown in the displayed table. Use the |<< button to start
over.

MVR Group Table Columns

VLAN ID

VLAN ID of the group.

Groups

Group ID of the group displayed.

Port Members

Ports under this group.

Buttons

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.
Refresh: Refreshes the displayed table starting from the input fields.

|<<: Updates the table starting from the first entry in the MVR Group Table.

251
>>: Updates the table, starting with the entry after the last entry currently displayed.

21.8. Monitor / IPMC / IGMP Snooping

21.8.1. IGMP Snooping

IGMP Snooping Status

This page provides IGMP Snooping status.

VLAND ID

The VLAN ID of the entry.

Querier Version

Working Querier Version currently.

Host Version

Working Host Version currently.

Querier Status

Shows the Querier status is "ACTIVE" or "IDLE".

"DISABLE" denotes the specific interface is administratively disabled.

Queries Transmitted

The number of Transmitted Queries.

Queries Received

The number of Received Queries.

252
V1 Reports Received

The number of Received V1 Reports.

V2 Reports Received

The number of Received V2 Reports.

V3 Reports Received

The number of Received V3 Reports.

V2 Leaves Received

The number of Received V2 Leaves.

Router Port

Display which ports act as router ports. A router port is a port on the Ethernet switch that leads towards

the Layer 3 multicast device or IGMP querier.

Static denotes the specific port is configured to be a router port.

Dynamic denotes the specific port is learnt to be a router port.

Both denotes the specific port is configured and learnt to be a router port.

Buttons

Refresh: Click to refresh the page immediately.

Clear: Clears all Statistics counters.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.

IGMP Group Information

Entries in the IGMP Group Table are shown on this page. The IGMP Group Table is sorted first by

VLAN ID, and then by group.

253
Navigating the IGMP Group Table

Each page shows up to 99 entries from the IGMP Group table, default being 20, selected through the
"entries per page" input field. When first visited, the web page will show the first 20 entries from the
beginning of the IGMP Group Table.
The "Start from VLAN", and "group" input fields allow the user to select the starting point in the IGMP
Group Table. Clicking the Refresh button will update the displayed table starting from that or the
closest next IGMP Group Table match. In addition, the two input fields will - upon a Refresh button
click - assume the value of the first displayed entry, allowing for continuous refresh with the same start
address.
The >> will use the last entry of the currently displayed table as a basis for the next lookup. When the
end is reached the text "No more entries" is shown in the displayed table. Use the |<< button to start
over.

IGMP Group Table Columns

VLAN ID

VLAN ID of the group.

Groups

Group address of the group displayed.

Port Members

Ports under this group.

Buttons

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.
Refresh: Refreshes the displayed table starting from the input fields.

|<<: Updates the table, starting with the first entry in the IGMP Group Table.

>>: Updates the table, starting with the entry after the last entry currently displayed.

254
IGMP SFM Information Table

Entries in the IGMP SFM Information Table are shown on this page. The IGMP SFM (Source-Filtered

Multicast) Information Table also contains the SSM (Source-Specific Multicast) information. This table

is sorted first by VLAN ID, then by group, and then by Port No. Different source addresses belong to

the same group are treated as single entry.

Navigating the IGMP SFM Information Table

Each page shows up to 99 entries from the IGMP SFM Information table, default being 20, selected

through the "entries per page" input field. When first visited, the web page will show the first 20 entries

from the beginning of the IGMP SFM Information Table.


The "Start from VLAN", and "group" input fields allow the user to select the starting point in the IGMP

SFM Information Table. Clicking the Refresh button will update the displayed table starting from that or

the closest next IGMP SFM Information Table match. In addition, the two input fields will - upon a

Refresh button click - assume the value of the first displayed entry, allowing for continuous refresh with

the same start address.

The >> will use the last entry of the currently displayed table as a basis for the next lookup. When the

end is reached the text "No more entries" is shown in the displayed table. Use the |<< button to start
over.

IGMP SFM Information Table Columns

VLAN ID

VLAN ID of the group.

Group

255
Group address of the group displayed.

Port

Switch port number.

Mode

Indicates the filtering mode maintained per (VLAN ID, port number, Group Address) basis. It can be

either Include or Exclude.

Source Address

IP Address of the source. Currently, system limits the total number of IP source addresses for filtering to

be 128.

Type

Indicates the Type. It can be either Allow or Deny.

Buttons

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.
Refresh: Refreshes the displayed table starting from the input fields.

|<<: Updates the table starting from the first entry in the IGMP SFM Information Table.

>>: Updates the table, starting with the entry after the last entry currently displayed.

21.8.2. MLD Snooping Status

This page provides MLD Snooping status.

256
VLAND ID

The VLAN ID of the entry.

Querier Version

Working Querier Version currently.

Host Version

Working Host Version currently.

Querier Status

Show the Querier status is "ACTIVE" or "IDLE".

"DISABLE" denotes the specific interface is administratively disabled.

Queries Transmitted

The number of Transmitted Queries.

Queries Received

The number of Received Queries.

V1 Reports Received

The number of Received V1 Reports.

V2 Reports Received

The number of Received V2 Reports.

V1 Leaves Received

The number of Received V1 Leaves.

Router Port

Display which ports act as router ports. A router port is a port on the Ethernet switch that leads towards

the Layer 3 multicast device or IGMP querier.

Static denotes the specific port is configured to be a router port.

Dynamic denotes the specific port is learnt to be a router port.

Both denotes the specific port is configured and learnt to be a router port.

Buttons

Refresh: Click to refresh the page immediately.

Clear: Clears all Statistics counters.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.

257
MLD Group Table

Entries in the MLD Group Table are shown on this page. The MLD Group Table is sorted first by VLAN

ID, and then by group.

Navigating the MLD Group Table

Each page shows up to 99 entries from the MLD Group table, default being 20, selected through the

"entries per page" input field. When first visited, the web page will show the first 20 entries from the

beginning of the MLD Group Table.

The "Start from VLAN", and "group" input fields allow the user to select the starting point in the MLD

Group Table. Clicking the Refresh button will update the displayed table starting from that or the next
closest MLD Group Table match. In addition, the two input fields will - upon a Refresh button click -

assume the value of the first displayed entry, allowing for continuous refresh with the same start

address.

The >> will use the last entry of the currently displayed as a basis for the next lookup. When the end is
reached the text "No more entries" is shown in the displayed table. Use the |<< button to start over.

Buttons

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.
Refresh: Refreshes the displayed table starting from the input fields.

|<<: Updates the table starting from the first entry in the MLD Group Table.

>>: Updates the table, starting with the entry after the last entry currently displayed.

258
MLD SFM Information Table

Entries in the MLD SFM Information Table are shown on this page. The MLD SFM (Source-Filtered

Multicast) Information Table also contains the SSM (Source-Specific Multicast) information. This table

is sorted first by VLAN ID, then by group, and then by Port No. Different source addresses belong to the
same group are treated as single entry.

Navigating the MLD SFM Information Table

Each page shows up to 64 entries from the MLD SFM Information table, default being 20, selected

through the "entries per page" input field. When first visited, the web page will show the first 20 entries

from the beginning of the MLD SFM Information Table.


The "Start from VLAN", and "group" input fields allow the user to select the starting point in the MLD

SFM Information Table. Clicking the button will update the displayed table starting from that or the

closest next MLD SFM Information Table match. In addition, the two input fields will - upon a button

click - assume the value of the first displayed entry, allowing for continuous refresh with the same start

address.

The will use the last entry of the currently displayed as a basis for the next lookup. When the end is
reached the text "No more entries" is shown in the displayed table. Use the button to start over.

MLD SFM Information Table Columns

VLAN ID

VLAN ID of the group.

Group

Group address of the group displayed.

259
Port

Switch port number.

Mode

Indicates the filtering mode maintained per (VLAN ID, port number, Group Address) basis. It can be

either Include or Exclude.

Source Address

IP Address of the source. Currently, system limits the total number of IP source addresses for filtering to

be 128.

Type

Indicates the Type. It can be either Allow or Deny.

Buttons

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.
Refresh: Refreshes the displayed table starting from the input fields.

|<<: Updates the table starting from the first entry in the MLD SFP Information Table.

>>: Updates the table, starting with the entry after the last entry currently displayed.

21.9. Monitor / LLDP

21.9.1 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:

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

Remote Port ID

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

System Name

System Name is the name advertised by the neighbour unit.

Port Description

Port Description is the port description 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. WAN 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 (-).

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

Refresh: Click to refresh the page immediately.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular
intervals.

261
21.9.2. LLDP MED Neighbours

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:

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.

262
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

263
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 neighbour 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.

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 Signaling - for use in network topologies that require a different policy for the voice signaling
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 Signaling - for use in network topologies that require a different policy for the guest
voice signaling than for the guest voice media.

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

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 Signaling - for use in network topologies that require a separate policy for the video signaling
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

265
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).

Buttons

Refresh: Click to refresh the page immediately.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.

21.9.3. LLDP PoE

This page provides a status overview for all LLDP PoE neighbours. The displayed table contains a row

for each port on which an LLDP PoE neighbour is detected. The columns hold the following
information:

Local Port

The port for this switch on which the LLDP frame was received.

Power Type

The Power Type represents whether the device is a Power Sourcing Entity (PSE) or Power Device

(PD).

If the Power Type is unknown it is represented as "Reserved".

266
Power Source

The Power Source represents the power source being utilized by a PSE or PD device.

If the device is a PSE device it can either run on its Primary Power Source or its Backup Power Source.

If it is unknown whether the PSE device is using its Primary Power Source or its Backup Power Source
it is indicated as "Unknown"

If the device is a PD device it can either run on its local power supply or it can use the PSE as power
source. It can also use both its local power supply and the PSE.

If it is unknown what power supply the PD device is using it is indicated as "Unknown"

Power Priority

Power Priority represents the priority of the PD device, or the power priority associated with the PSE

type device's port that is sourcing the power. There are three levels of power priority. The three levels
are: Critical, High and Low. If the power priority is unknown it is indicated as "Unknown"

Maximum Power

The Maximum Power Value contains a numerical value that indicates the maximum power in watts

required by a PD device from a PSE device, or the minimum power a PSE device is capable of
sourcing over a maximum length cable based on its current configuration.

The maximum allowed value is 102.3 W. If the device indicates value higher than 102.3 W, it is
represented as "reserved"

Buttons

Auto-refresh : Check this box to refresh the page automatically. Automatic refresh occurs every 3

seconds.

Refresh: Click to refresh the page.

21.9.4. LLDP EEE


By using EEE power savings can be achieved at the expense of traffic latency. This latency occurs due

to that the circuits EEE turn off to save power, need time to boot up before sending traffic over the link.

This time is called "wakeup time". To achieve minimal latency, devices can use LLDP to exchange

information about their respective tx and rx "wakeup time ", as a way to agree upon the minimum

wakeup time they need.

This page provides an overview of EEE information exchanged by LLDP.

267
LLDP Neighbours EEE Information
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 Tw

The link partner's maximum time that transmit path can hold off sending data after deassertion of LPI.

Rx Tw

The link partner's time that receiver would like the transmitter to hold off to allow time for the receiver to

wake from sleep.

Fallback Receive Tw

The link partner's fallback receive Tw.

A receiving link partner may inform the transmitter of an alternate desired Tw_sys_tx. Since a receiving

link partner is likely to have discrete levels for savings, this provides the transmitter with additional

information that it may use for a more efficient allocation. Systems that do not implement this option
default the value to be the same as that of the Receive Tw_sys_tx.

Echo Tx Tw

The link partner's Echo Tx Tw value

The respective echo values shall be defined as the local link partner’s reflection (echo) of the remote

link partners respective values. When a local link partner receives its echoed values from the remote

link partner it can determine whether or not the remote link partner has received, registered and

268
processed its most recent values. For example, if the local link partner receives echoed parameters

that do not match the values in its local MIB, then the local link partner infers that the remote link
partners request was based on stale information.

Echo Rx Tw

The link partner's Echo Rx Tw value.

Resolved Tx Tw

The resolved Tx Tw for this link. Note: NOT the link partner

The resolved value that is the actual "tx wakeup time" used for this link (based on EEE information
exchanged via LLDP).

Resolved Rx Tw

The resolved Rx Tw for this link. Note: NOT the link partner

The resolved value that is the actual "tx wakeup time" used for this link (based on EEE information
exchanged via LLDP).

EEE activated

Show if the switch and the link partner have agree upon which wakeup times to use.

Red - Switch and link partner have not agreed upon wakeup time.

Green - Switch and link partner have agreed upon wakeup time.

Buttons

Refresh: Click to refresh the page immediately.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.

21.9.5. LLDP Statistics

This page provides an overview of all LLDP traffic.

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.

269
Global Counters

Neighbour entries were last changed on

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

270
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

Refresh: Click to refresh the page immediately.

Clear: Clears the local counters. All counters (including global counters) are cleared upon reboot.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.

21.10. Power Over Ethernet Status

This page provides an overview on the current PoE status for all ports.

271
21.11. Dynamic MAC Table

Entries in the MAC Table are shown on this page. The MAC Table contains up to 8192 entries, and is

sorted first by VLAND ID, then by MAC address.

Navigating the MAC Table


Each page shows up to 999 entries from the MAC table, default being 20, selected through the "entries

per page" input field. When first visited, the web page will show the first 20 entries from the beginning of

the MAC Table. The first displayed will be the one with the lowest VLAN ID and the lowest MAC

address found in the MAC Table.

The "Start from MAC address" and "VLAN" input fields allow the user to select the starting point in the

MAC Table. Clicking the button will update the displayed table starting from that or the closest next

MAC Table match. In addition, the two input fields will - upon a button click - assume the value of the

first displayed entry, allowing for continuous refresh with the same start address.

The will use the last entry of the currently displayed VLAN/MAC address pairs as a basis for the next

lookup. When the end is reached the text "No more entries" is shown in the displayed table. Use the

button to start over.

272
MAC Table Columns

Switch (stack only)

The stack unit where the entry is learned.

Type

Indicates whether the entry is a static or a dynamic entry.

MAC address

The MAC address of the entry.

VLAN

The VLAN ID of the entry.

Port Members

The ports that are members of the entry.

Buttons

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.
Refresh: Refreshes the displayed table starting from the "Start from MAC address" and "VLAN" input

fields.

Clear: Flushes all dynamic entries.

|<<: Updates the table starting from the first entry in the MAC Table, i.e. the entry with the lowest VLAN

ID and MAC address.

>>: Updates the table, starting with the entry after the last entry currently displayed.

273
21.12. VLAN Membership Status

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

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.

Port Members

A row of check boxes for each port is displayed for each VLAN ID.

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

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.

Navigating the VLAN Monitor page

Each page shows up to 99 entries from the VLAN table, default being 20, selected through the "entries

per page" input field. When first visited, the web page will show the first 20 entries from the beginning of

the VLAN Table. The first displayed will be the one with the lowest VLAN ID found in the VLAN Table.

The "VLAN" input fields allow the user to select the starting point in the VLAN Table. Clicking the button

will update the displayed table starting from that or the closest next VLAN Table match. The will use the

last entry of the currently displayed VLAN entry as a basis for the next lookup. When the end is reached
the text "No more entries" is shown in the displayed table. Use the button to start over.

Navigating the VLAN Monitor page

Each page shows up to 99 entries from the VLAN table, default being 20, selected through the "entries

per page" input field. When first visited, the web page will show the first 20 entries from the beginning of

the VLAN Table. The first displayed will be the one with the lowest VLAN ID found in the VLAN Table.

The "VLAN" input fields allow the user to select the starting point in the VLAN Table. Clicking the button

will update the displayed table starting from that or the closest next VLAN Table match. The will use the

last entry of the currently displayed VLAN entry as a basis for the next lookup. When the end is reached
the text "No more entries" is shown in the displayed table. Use the button to start over.

Buttons

: Select VLAN Users from this drop down list.

Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.
Refresh: Click to refresh the page immediately.

275
VLAN Port Status

This page provides VLAN Port Status.

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.

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.

Port

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

PVID

Shows the VLAN identifier for that port. The allowed values are 1 through 4095. The default value is 1.

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.

Tx Tag

Shows egress filtering frame status whether tagged or untagged.

UVID

Shows UVID (untagged VLAN ID). Port's UVID determines the packet's behavior at the egress side.

Conflicts

Shows status of Conflicts whether exists or not. When a Volatile VLAN User requests to set VLAN

membership or VLAN port configuration, the following conflicts can occur:

Functional Conflicts between features.

Conflicts due to hardware limitation.

Direct conflict between user modules.

Buttons

: Select VLAN Users from this drop down list.

277
Auto-refresh : Check this box to enable an automatic refresh of the page at regular intervals.
Refresh: Click to refresh the page immediately.

21.13. VCL MAC-Based VLAN Status

This page shows MAC-based VLAN entries configured by various MAC-based VLAN users. 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.

MAC Address

Indicates the MAC address.

VLAN ID

Indicates the VLAN ID.

Port Members

Port members of the MAC-based VLAN entry.

Buttons

Refresh: Refreshes the displayed table.

278
21.14. sFlow

This page shows the sFlow Statistics.

Flow Sampling

Packet flow sampling refers to arbitrarily choosing some packets out of a specified number, reading the
first "Max Hdr Size" bytes and exporting the sampled datagram for analysis.
The attributes associated with the flow sampling are: sampler type, sampling rate, maximum header
size.

Counter Sampling

Counter sampling performs periodic, time-based sampling or polling of counters associated with an
interface enabled for sFlow.
Attribute associated with counter sampling is polling interval.

sFlow Ports

List of the port numbers on which sFlow is configured.

Sampler Type

Configured sampler type on the port and could be any of the types: None, RX,TX, ALL.

279
22. Diagnostic
This section provides some convenient tool for user to do switch diagnostic from remote site.

22.1. Ping

This page allows you to issue ICMP PING packets to troubleshoot IP connectivity issues.

Type the IP Addree, ping length (default = 56 bytes), ping count (default=5) and ping interval (default

=1). Then press "Start" to start ping remote host. After you press Start, 5 ICMP packets are transmitted,

and the sequence number and roundtrip time are displayed upon reception of a reply. The page
refreshes automatically until responses to all packets are received, or until a timeout occurs.

ICMP Ping Output Result


PING server 192.168.2.100, 56 bytes of data.

64 bytes from 192.168.2.100: icmp_seq=0, time=0ms

64 bytes from 192.168.2.100: icmp_seq=1, time=0ms

64 bytes from 192.168.2.100: icmp_seq=2, time=0ms

64 bytes from 192.168.2.100: icmp_seq=3, time=0ms

64 bytes from 192.168.2.100: icmp_seq=4, time=0ms

Sent 5 packets, received 5 OK, 0 bad

IP Address

The destination IP Address.

Ping Length

The payload size of the ICMP packet. Values range from 2 bytes to 1452 bytes.

Ping Count

The count of the ICMP packet. Values range from 1 time to 60 times.

Ping Interval

The interval of the ICMP packet. Values range from 0 second to 30 seconds.

22.2. Ping6

This page allows you to issue ICMPv6 PING packets to troubleshoot IPv6 connectivity issues.

Type the IPv6 Address, ping length (default = 56 bytes), ping count (default=5) and ping interval

(default =1). Then press "Start" to start ping remote host. After you press Start, 5 ICMPv6 packets are

280
transmitted, and the sequence number and roundtrip time are displayed upon reception of a reply. The
page refreshes automatically until responses to all packets are received, or until a timeout occurs.

ICMPv6 Ping Output

PING6 server ::10.10.132.20

64 bytes from ::10.10.132.20: icmp_seq=0, time=0ms

64 bytes from ::10.10.132.20: icmp_seq=1, time=0ms

64 bytes from ::10.10.132.20: icmp_seq=2, time=0ms

64 bytes from ::10.10.132.20: icmp_seq=3, time=0ms

64 bytes from ::10.10.132.20: icmp_seq=4, time=0ms

Sent 5 packets, received 5 OK, 0 bad

You can configure the following properties of the issued ICMP packets:

IP Address

The destination IP Address.

Ping Length

The payload size of the ICMP packet. Values range from 2 bytes to 1452 bytes.

Ping Count

The count of the ICMP packet. Values range from 1 time to 60 times.

Ping Interval

The interval of the ICMP packet. Values range from 0 second to 30 seconds.

22.3. VeriPHY Cable Diagnostic

This page is used for running the VeriPHY Cable Diagnostics.

Select the port and then press Start to run the diagnostics. This will take approximately 5 seconds. If all

ports are selected, this can take approximately 15 seconds. When completed, the page refreshes

automatically, and you can view the cable diagnostics results in the cable status table. Note that

VeriPHY is only accurate for cables of length 7 - 140 meters.

10 and 100 Mbps ports will be linked down while running VeriPHY. Therefore, running VeriPHY on a 10
or 100 Mbps management port will cause the switch to stop responding until VeriPHY is complete.

281
Port

The port where you are requesting VeriPHY Cable Diagnostics.

Cable Status

Port: Port number.

Pair: The status of the cable pair.


The status of the cable pair.
OK - Correctly terminated pair
Open - Open pair
Short - Shorted pair
Short A - Cross-pair short to pair A
Short B - Cross-pair short to pair B
Short C - Cross-pair short to pair C
Short D - Cross-pair short to pair D
Cross A - Abnormal cross-pair coupling with pair A
Cross B - Abnormal cross-pair coupling with pair B
Cross C - Abnormal cross-pair coupling with pair C
Cross D - Abnormal cross-pair coupling with pair D
Length: The length (in meters) of the cable pair.

282
23. Maintenance
The section allows user to maintain the switch, such as Reset Factory Default, Firmware upgrading,

Configuration Save/Restore and Restart the device.

23.1. Restart Device

You can restart the switch on this page. After restart, the switch will boot normally.

Yes: Click to restart device.

No: Click to return to the Port State page without restarting.

23.2. Factory Defaults

You can reset the configuration of the switch on this page. Only the IP configuration is retained.

The new configuration is available immediately, which means that no restart is necessary.

Yes: Click to reset the configuration to Factory Defaults.

No: Click to return to the Port State page without resetting the configuration.

283
Note: Restoring factory default can also be performed by making a physical loopback between port 1

and port 2 within the first minute from switch reboot. In the first minute after boot, 'loopback' packets will

be transmitted at port 1. If a 'loopback' packet is received at port 2 the switch will do a restore to default .

23.3. Software Upload

23.3.1. Firmware Update

This page facilitates an update of the firmware controlling the switch.

"Browse" to the location of a software image, you can see the file name in the right of the Browse
command. Click "Upload" to start the process.

After the software image is uploaded, a page announces that the firmware update is initiated. After
about a minute, the firmware is updated and the switch restarts.

Warning: While the firmware is being updated, Web access appears to be defunct. The front
LED flashes Green/Off with a frequency of 10 Hz while the firmware update is in progress.
Do not restart or power off the device at this time or the switch may fail to function.

284
23.3.2. Image Select
There are 2 image saved within the switch.

This page provides information about the active and alternate (backup) firmware images in the device,
and allows you to revert to the alternate image.

The web page displays two tables with information about the active and alternate firmware images.

Note:

1. In case the active firmware image is the alternate image, only the "Active Image" table is shown. In
this case, the Activate Alternate Image button is also disabled.
2. If the alternate image is active (due to a corruption of the primary image or by manual intervention),
uploading a new firmware image to the device will automatically use the primary image slot and
activate this.
3. The firmware version and date information may be empty for older firmware releases. This does not
constitute an error.

Image Information

Image

The flash index name of the firmware image. The name of primary (preferred) image is image, the

alternate image is named image.bk.

Version

The version of the firmware image.

Date

The date where the firmware was produced.

Buttons

285
Activate Alternate Image: Click to use the alternate image. This button may be disabled depending on
system state.

Cancel: Cancel activating the backup image. Navigates away from this page.

23.4. Configuration

You can save/view or load the switch configuration. The configuration file is in XML format with a
hierarchy of tags:

Header tags: <?xml version="1.0"?> and <configuration>. These tags are mandatory and must be
present at the beginning of the file.

Section tags: <platform>, <global> and <switch>. The platform section must be the first section tag and
this section must include the correct platform ID and version. The global section is optional and
includes configuration which is not related to specific switch ports. The switch section is optional and
includes configuration which is related to specific switch ports.

Module tags: <ip>, <mac>, <port> etc. These tags identify a module controlling specific parts of the
configuration.

Group tags: <port table>, <vlan table> etc. These tags identify a group of parameters, typically a table.

Parameter tags: <mode>, <entry> etc. These tags identify parameters for the specific section, module
and group. The <entry> tag is used for table entries.

Configuration parameters are represented as attribute values. When saving the configuration from the
switch, the entire configuration including syntax descriptions is included in the file. The file may then be
modified using an editor and loaded to a switch.

The example below shows a small configuration file only including configuration of the MAC address
age time and the learning mode per port. When loading this file, only the included parameters will be
changed. This means that the age time will be set to 200 and the learn mode will be set to automatic.

< ?xml version="1.0"?>


<configuration>
<platform>
<pid val="3"></pid>
<version val="1"></version>
</platform>
<global>
<mac>
<age val="200"></age>>
</mac>
</global>
<switch sid="1">
<mac>

286
<entry port="1-24" learn mode="auto"></entry>
</mac>
</switch>
< /configuration>

Save: Click to save the configuration file.

Upload: Click to upload the configuration file.

287
Appendix B. Feature Configuration - CLI
The Command Line Interface (CLI) is the user interface to the switch’s embedded software
system. You can view the system information, show the status, configure the switch and
receive a response back from the system by keying in a command.

After login the switch through console CLI, you can see the ">" mark. You can type the
command after it. There are some useful command, such as:
Type '<group>' to enter command group, e.g. 'port' to the port configuration.
Type '<group> ?' to get list of group commands, e.g. 'port ?'. You can follow the instruction
step by step to finish the command.
Type '<command> ?' to get help on a command, e.g. 'port mode ?'.
Type 'up' to move up one level or '/' to go to root level
Type "logout" in root level to leave the command line interface
Click "Enter" key after finish the command.
Click "Up" key to repeat the previous commands
Commands may be abbreviated, e.g. 'por co' instead of 'port configuration'. For quick
configuration, the abbreviated typo is helpful.

Example: Configure the System Contact to Orwell


You can go to system group or type the full name in root level. Both of the methods can
meet your need.

In system group mode:


System>contact Orwell
In root level:
>sys contact Orwell

Note: This chapter just lists the relevant command lines of the feature settings for your
reference. You can see the detail explanation of the commands and features through the
chapter 4.

1. System Configuration
Feature Command Line
System Information
System Group Enter the System Configuration Group to do further
configuration.

>system
Type 'up' to move up one level or '/' to go to root level
System>

System Contact Syntax:


System Name [<name>]

288
Parameters:
<name>: System name string. (1-255)

Example: Contact Name = Orwell


System>contact Orwell

System Name Syntax:


System Name [<name>]

Parameters:
<name>: System name string. (1-255)

Example: Contact Name = poeswitch


System>name poeswitch
poeswitch:/>
(After given system name, the prompt character will be
changed automatically.)
System Location Syntax:
System Location [<location>]

Parameters:
<location>: System location string. (1-255)

Example: Location Name


poeswitch:/System>loca fll_01

Time Zone Offset Syntax:


System Timezone [<offset>]

Parameters:
<offset>: Time zone offset in minutes (-720 to 720) relative to
UTC

Example: Time Zone = 100


poeswitch:/System>time 100
IP Configuration
IP Group Enter the IP Configuration Group

poeswitch:/>ip
Type 'up' to move up one level or '/' to go to root level
poeswitch:/IP>
DHCP Client Syntax:
IP DHCP [enable|disable]

poeswitch:/IP>dhcp en
IP Setting (Address, Syntax:

Mask, Gateway, IP Setup [<ip_addr>] [<ip_mask>] [<ip_router>] [<vid>]


Example: IP=192.168.2.2, Mask=255.255.255.0, Gateway:
Managed VID)
192.168.2.254, VID=1

poeswitch:/IP>setup 192.168.2.2 255.255.255.0 192.168.2.254 1

NTP Enable NTP Mode by below command:

poeswitch:/IP>ntp mode en

289
Type the NTP Server address settings by below command:

Syntax:

IP NTP Server Add <server_index> <ip_addr_string>

IP NTP Server Ipv6 Add <server_index> <server_ipv6>

IP NTP Server Delete <server_index>

Example:

poeswitch:/IP>ntp ser add 1 192.168.100.1

poeswitch:/IP>ntp ser add 2 168.95.1.1

Check the NTP Server settings by below command:


poeswitch:/IP>ntp conf

IP NTP Configuration:
=====================

NTP Mode : Enabled


Idx Server IP host address (a.b.c.d) or a host name string
--- ------------------------------------------------------
1 192.168.100.1
2 168.95.1.1
3
4
5

DNS Server Syntax:


IP DNS [<ip_addr>]
Parameters:
<ip_addr>: IP address (a.b.c.d), default: Show IP address
Example:
poeswitch:/IP>dns 168.95.1.1
DNS Proxy Syntax: IP DNS_Proxy [enable|disable]
poeswitch:/IP>dns_proxy en
IPv6 Configuration
IPv6 Commands Syntax:
IP IPv6 AUTOCONFIG [enable|disable]
IP IPv6 Setup [<ipv6_addr>] [<ipv6_prefix>] [<ipv6_router>]
IP IPv6 State <ipv6_addr> [enable|disable]
IP IPv6 Ping6 <ipv6_addr> [(Length <ping_length>)] [(Count
<ping_count>)] [(Interval <ping_interval>)]

Auto Configuration Syntax:


IP IPv6 AUTOCONFIG [enable|disable]
Example:
poeswitch:/IP>ipv6 auto en

IPv6 Address Setting Syntax:

290
(Address, Prefix, IP IPv6 Setup [<ipv6_addr>] [<ipv6_prefix>] [<ipv6_router>]
Router) Example:
poeswitch:/IP>ipv6 setup 2001:DB8::250:8bff:fee8:f800 48
2001:DB8::250:8bff:fee8:f8ff
IPv6 Ping Test Syntax:
IP IPv6 Ping6 <ipv6_addr> [(Length <ping_length>)] [(Count
<ping_count>)] [(Interval <ping_interval>)]
Example:
poeswitch:/IP>ipv6 ping6 2001:DB8::250:8bff:fee8:f800
NTP
NTP Mode Enable NTP Mode by below command:
poeswitch:/IP>ntp mode en

NTP Server Address Syntax:


Setting Type the NTP Server address settings by below command:
IP NTP Server Add <server_index> <ip_addr_string>
IP NTP Server Ipv6 Add <server_index> <server_ipv6>
IP NTP Server Delete <server_index>
Example:
poeswitch:/IP>ntp ser add 1 192.168.100.1
poeswitch:/IP>ntp ser add 2 168.95.1.1

NTP Setting Status Check the NTP Server settings by below command:

poeswitch:/IP>ntp conf

IP NTP Configuration:
=====================

NTP Mode : Enabled


Idx Server IP host address (a.b.c.d) or a host name string
--- ------------------------------------------------------
1 192.168.100.1
2 168.95.1.1
3
4
5
System Log
Server Mode Syntax:
System Log Server Mode [enable|disable]
Example:
poeswitch:/System>log server mode en

Server Address Syntax:


System Log Server Address [<ip_addr_string>]
Example:
poeswitch:/System>log server add 192.168.2.100

291
Syslog Level Syntax:
System Log Level [info|warning|error]

Information:
poeswitch:/System>log level inf

Warning:
poeswitch:/System>log level war

Error:
poeswitch:/System>log level err

Clear Syslog Syntax:


System Log Clear [all|info|warning|error]

poeswitch:/System>log clear all

System Log poeswitch:/System>log conf

Configuration System Log Configuration:


=========================

System Log Server Mode : Enabled


System Log Server Address : 192.168.2.100
System Log Level : Error

2. Power Reduction

Feature Command Line


LED Power Reduction
LED Intensity Times Syntax:
led_power timers [<hour>] [<intensity>]

Parameters:
<hour> : The hour (0-24) at which to change LEDs intensity
<intensity>: The LED intensity in % (0-100)

Example: (Time=2:00, Intensity: 30%)


led_power>timer 2 30

Maintenance Syntax:
led_power maintenance [<maintenance_time>]
[on_at_errors|leave_at_errors]

Parameters:
<maintenance_time> : Time in seconds (0-65535) that the
LEDs shall be turned on, when any port changes link state
on_at_errors|leave_at_errors: on_at_error if LEDs shall be
turned on if any errors has been detected. leave_at_errors if
no LED change shall happen when errors have been detected

Example:
led_power>main 20

292
led_power>main 20 on (20 sec., on_ad_errors enabled)

EEE Configuration
EEE Port Syntax:
EEE Mode [<port_list>] [enable|disable]
Configuration
Parameters:
<port_list>: Port list or 'all', default: All ports
enable : Enable EEE
disable: Disable EEE

Example: Enable Port 1-5


EEE>mode 1-5 en

Urgent Queue of Port Syntax:


EEE Urgent_queues [<port_list>] [<queue_list>]

Parameters:
<port_list> : Port list or 'all', default: All ports
<queue_list>: List of queues to configure as urgent queues
(1-8 or none)

Example: Enable Urgent_Queue on Port 1-5


EEE>urge 1-5 2

3. Port Configuration
Feature Command Line
Port Configuration
Port Group poeswitch:/>port
Type 'up' to move up one level or '/' to go to root level
poeswitch:/Port>
Link State Syntax:
Port State [<port_list>] [enable|disable]

Example: Enable/Disable Port 1 State. After port 1 disabled,


the port can't access the switch.
Port>state 1 en
Port>state 1 dis

Link Speed and Syntax:


Port Mode [<port_list>]
Duplex [auto|10hdx|10fdx|100hdx|100fdx|1000fdx|sfp_auto_ams|100
0x_ams|100fx_ams|1000x|100fx]

Example:
Port>mode 2 1000fdx (Configure port 2 to 1000 Full Duplex)
Port>mode 1-4 1000fdx (Configure port 1-4 to 1000 Full
Duplex)

Flow Control Syntax:


Port Flow Control [<port_list>] [enable|disable]

293
Example:
Port>flow cont 1 en (Enable Flow Control on Port 1)
Port>flow cont 1 dis (Disable Flow Control on Port 2)

Maximum Frame Size Syntax:


Port MaxFrame [<port_list>] [<max_frame>]

Example: Set port 1-24's maximum frame size to 9K jumbo


frame

Port>maxf 1-24 9600

Port Status
Port Status Port>conf 1-2

Port Configuration:

===================

Port State Mode Flow Control MaxFrame Power Excessive Link

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

1 Enabled Auto Disabled 9600 Disabled Discard Down

2 Enabled Auto Disabled 9600 Disabled Discard 1Gfdx

.............

Port Mode Port>mode 2

Port Mode Link

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

2 Auto 1Gfdx

Port Status - All poeswitch:/Port>config

Information Port Configuration:

===================

Port State Mode Flow Control MaxFrame Power Excessive Link

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

1 Enabled Auto Disabled 9600 Disabled Discard Down

2 Enabled Auto Disabled 9600 Disabled Discard 1Gfdx

3 Enabled Auto Disabled 9600 Disabled Discard Down

..............

Status of Link UP poeswitch:/Port>conf all up

ports Port Configuration:

===================

Port State Mode Flow Control MaxFrame Power Excessive Link

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

2 Enabled Auto Disabled 9600 Disabled Discard 1Gfdx

Port Statistic poeswitch:/Port>statistic 1


Port 1 Statistics:

Rx Packets: 0 Tx Packets: 0

Rx Octets: 0 Tx Octets: 0

Rx Unicast: 0 Tx Unicast: 0

...................

294
4. Security Configuration

Feature Command Line


Security-Switch Configuration
Security -Switch >securi swi
Type 'up' to move up one level or '/' to go to root level
Group Security/Switch>?

Command Groups:
---------------
Security Switch Users : User management
Security Switch Privilege: Privilege level
Security Switch Auth : Authentication
Security Switch SSH : Secure Shell
Security Switch HTTPS : Hypertext Transfer Protocol over Secure Socket
Layer
Security Switch Access : Access management
Security Switch SNMP : Simple Network Management Protocol
Security Switch RMON : Remote Network Monitoring
User Configuration Security/Switch>user ?
Available Commands:

Security Switch Users Configuration


Security Switch Users Add <user_name> <password>
<privilege_level>
Security Switch Users Delete <user_name>

Add New User Syntax:


Security Switch Users Add <user_name> <password>
<privilege_level>

Example: Add New User Name, Password with highest


privilege, Name: Orwell, Password: possword, Privilege: 15

Security/Switch>users add Orwell password 15

Delete the User Syntax:


Security Switch Users Delete <user_name>

Example: Delete the User, Orwell from User Name database

Security/Switch>users del Orwell

User Name Database Security/Switch>users conf

Users Configuration:
====================

User Name Privilege Level


-------------------------------- ---------------
admin 15
Orwell 15

Privilege Level Syntax:

295
Security Switch Privilege Level Group <group_name>
[<cro>] [<crw>] [<sro>] [<srw>]
(cro=Configuration Read-Only, crw=Configuration/Excute
Read/Write, sro=Status/Statistics Read-Only,
srw=Status/Statistics Read/Write)

Example: Set Privilege level of VLAN Group

Security/Switch/Privilege>level group VLANs 10 10 10 10


(cro=10, crw=10, sro=10, srw=10)

Privilege Level Security/Switch>pri level conf

Configuration Table Privilege Level Configuration:


==============================

Privilege Current Level: 15


Group Name Privilege Level
CRO CRW SRO SRW
-------------------------------- --- --- --- ---
Aggregation 5 10 5 10
Debug 15 15 15 15
Diagnostics 5 10 5 10
Authentication Syntax:
Security Switch Auth Method [console|telnet|ssh|web]
Method [none|local|radius|tacacs+] [enable|disable]

Example: Configure Telnet Authentication method to Radius


Enable

Security/Switch>auth method telnet radius en

Authentication Security/Switch>auth conf

Configuration Auth Configuration:


===================

Client Authentication Method Local Authentication Fallback


------- ---------------------- -----------------------------
console local Disabled
telnet local Disabled
ssh local Disabled
web local Disabled
SSH Syntax:
Security Switch SSH Mode [enable|disable]

Example:
Security/Switch>ssh mode en
Security/Switch>ssh mode dis

HTTPS Syntax:
Security Switch HTTPS Mode [enable|disable]
Security/Switch>https mode en
Security/Switch>https mode dis

Security Switch HTTPS Redirect [enable|disable]


Security/Switch>https mode en (Must enabled HTTPS)

296
Security/Switch>https redi en

Result:
Security/Switch>https conf

HTTPS Configuration:
====================

HTTPS Mode : Enabled


HTTPS Redirect Mode : Enabled

Access Management Syntax:


Security Switch Access Add <access_id> <start_ip_addr>
<end_ip_addr> [web] [snmp
] [telnet]

Example: Limit the IP range from the 192.168.2.1 to


192.168.2.10 can access the web UI.

Security/Switch>access add 1 192.168.2.1 192.168.2.10 web

SNMP System Syntax:


Security Switch SNMP Mode [enable|disable]
Configuration Security Switch SNMP Version [1|2c|3]
(Mode, Version, Read Security Switch SNMP Read Community [<community>]
Security Switch SNMP Write Community [<community>]
/Write Community)
Example:
Security/Switch>snmp mode en
Security/Switch>snmp ver 2c
Security/Switch/SNMP>read com abc
Security/Switch/SNMP>write com orwell

Result:
SNMP Configuration:
===================

SNMP Mode : Enabled


SNMP Version : 2c
Read Community : abc
Write Community : orwell

SNMP Community Syntax:


Security Switch SNMP Community Add <community>
[<ip_addr>] [<ip_mask>]
Security Switch SNMP Community Delete <index>
Security Switch SNMP Community Lookup [<index>]

Example:
Security/Switch>snmp commu add abc
Security/Switch>snmp commu add test 192.168.2.100
255.255.255.0

SNMP Trap Server Enter the SNMP Trap Configuration Group

Setting Security/Switch/SNMP>trap

297
Type 'up' to move up one level or '/' to go to root level
Security/Switch/SNMP/Trap>

Syntax:
Security Switch SNMP Trap Mode [enable|disable]
Security Switch SNMP Trap Version [1|2c|3]
Security Switch SNMP Trap Community [<community>]
Security Switch SNMP Trap Destination [<ip_addr_string>]
Security Switch SNMP Trap IPv6 Destination [<ipv6_addr>]

Example:
Security/Switch/SNMP/Trap>mode ena
Security/Switch/SNMP/Trap>version 2c
Security/Switch/SNMP/Trap>community public
Security/Switch/SNMP/Trap>destination 192.168.2.100

Result:
Trap Mode : Enabled
Trap Version : 2c
Trap Community : public
Trap Destination : 192.168.2.100
Trap IPv6 Destination : ::

SNMP Trap Event Syntax:


Security Switch SNMP Trap Authentication Failure
Setting [enable|disable]
Security Switch SNMP Trap Link-up [enable|disable]
Security Switch SNMP Trap Inform Mode [enable|disable]
Security Switch SNMP Trap Inform Timeout [<timeout>]
Security Switch SNMP Trap Inform Retry Times [<retries>]

Example:
Security/Switch/SNMP>trap auth fai en
Security/Switch/SNMP>trap link-up en
Security/Switch/SNMP>trap info mode en
Security/Switch/SNMP>trap info time 5
Security/Switch/SNMP>trap info ret times 5

Result:
Trap Authentication Failure : Enabled
Trap Link-up and Link-down : Enabled
Trap Inform Mode : Enabled
Trap Inform Timeout (seconds) : 5
Trap Inform Retry Times :5

SNMPv3 User Syntax:


Security Switch SNMP User Add <engineid> <user_name>
[MD5|SHA] [<auth_password>] [DES] [<priv_password>]

Example:
Security/Switch/SNMP>user add 800007e5017f000001 orwell
Security/Switch/SNMP>user add 800007e5017f000001 andy
md5 andy123

Result:
SNMPv3 Users Table:
Idx Engine ID User Name Level Auth Priv

298
--- --------- -------------------------------- -------------- ---- ----
1 Local default_user NoAuth, NoPriv None None
2 Local orwell NoAuth, NoPriv None None
3 Local andy Auth, NoPriv MD5 None

Number of entries: 3

RMON In Security/Switch Group, the system supports 4 types RMON


groups, please follow the RMON Syntax to add the entries.

Syntax:
Security/Switch>rmon ?

Statistics:
Security Switch RMON Statistics Add <stats_id>
<data_source>
Security Switch RMON Statistics Delete <stats_id>
Security Switch RMON Statistics Lookup [<stats_id>]

Histroy:
Security Switch RMON History Add <history_id>
<data_source> [<interval>] [<buckets>]
Security Switch RMON History Delete <history_id>
Security Switch RMON History Lookup [<history_id>]

Alarm:
Security Switch RMON Alarm Add <alarm_id> <interval>
<alarm_vairable> [absolute|delta] <rising_threshold>
<rising_event_index> <falling_threshold>
<falling_event_index> [rising|falling|both]
Security Switch RMON Alarm Delete <alarm_id>
Security Switch RMON Alarm Lookup [<alarm_id>]

Event:
Security Switch RMON Event Add <event_id>
[none|log|trap|log_trap] [<community>] [<description>]
Security Switch RMON Event Delete <event_id>
Security Switch RMON Event Lookup [<event_id>]
Security-Network Configuration
Limit Control
Limit Control - Syntax:
Security Network Limit Configuration [<port_list>]
System Configuration Security Network Limit Mode [enable|disable]
Security Network Limit Aging [enable|disable]
Security Network Limit Agetime [<age_time>]

Example:
Security/Network>limit mode enable
Security/Network>limit agin enable
Security/Network>limit agetim 1000

Result:
Port Security Limit Control Configuration:
==========================================

Mode : Enabled
Aging : Disabled
Age Period: 3600

299
Limit Control - Port Syntax:
Security Network Limit Port [<port_list>] [enable|disable]
Configuration Security Network Limit Limit [<port_list>] [<limit>]
Security Network Limit Action [<port_list>]
[none|trap|shut|trap_shut]
Security Network Limit Reopen [<port_list>]

Example:
Security/Network>limit port 1 enabl
Security/Network>limit limit 1 5
Security/Network>limit action 1 trap

Network Access Server Configuration (also known as IEEE 802.1X)


NAS System Syntax:
Mode:
Configuration Security Network NAS Mode [enable|disable]
Security Network NAS Reauthentication [enable|disable]

Time Settings
Security Network NAS ReauthPeriod [<reauth_period>]
Security Network NAS EapolTimeout [<eapol_timeout>]
Security Network NAS Agetime [<age_time>]
Security Network NAS Holdtime [<hold_time>]

Radius-Assigned
Security Network NAS RADIUS_QoS [global|<port_list>]
[enable|disable]
Security Network NAS RADIUS_VLAN [global|<port_list>]
[enable|disable]

Guest VLAN
Security Network NAS Guest_VLAN [global|<port_list>]
[enable|disable] [<vid>] [<reauth_max>]
[<allow_if_eapol_seen>]

Example:
Guest_VLAN Global Enabled, Guest VLAN ID=100,
Max. Re-Authentication Count = 10,
Allow Guest VLAN if EAPOL See = Enable

Security/Network>nas gues glob en 100 10 en

NAS Port Syntax:


Security Network NAS State [<port_list>]
Configuration [auto|authorized|unauthorized|single|multi|macbased]

auto= Port-based 802.1X


authorized = Force Authorized
unauthorized = Force Unauthorized
single = Single 802.1X
multi= Multi 802.1X
macbased = MAC_Based Authentication

Example:
Security/Network>nas state 2 auto

300
ACL (Access Control List)
ACL Port Syntax:
Security Network ACL Action [<port_list>] [permit|deny]
Configuration [<rate_limiter>] [<port_redirect>] [<mirror>] [<logging>]
[<shutdown>]

Parameters:
<port_list> : Port list or 'all', default: All ports
permit : Permit forwarding (default)
deny : Deny forwarding
<rate_limiter> : Rate limiter number (1-15) or 'disable'
<port_redirect>: Port list for copy of frames or 'disable'
<mirror> : Mirror of frames: enable|disable
<logging> : System logging of frames: log|log_disable
<shutdown> : Shut down ingress port: shut|shut_disable

Example:
Security/Network/ACL>Action 1 permit 10 dis en log shut

Result:
ACL Configuration:
==================
Port Policy Action Rate L. Port C. Mirror Logging Shutdown Counter
---- ------ ------ ------- ------- -------- -------- -------- -------
1 0 Permit 10 Disabled Enabled Enabled Enabled 0

Rate Limiter Syntax:


Security Network ACL Rate [<rate_limiter_list>] [<rate_unit>]
[<rate>]

Parameters:
<rate_limiter_list>: Rate limiter list (1-16), default: All rate
limiters
<rate_unit> : IP flags: pps|kbps, default: pss
<rate>: Rate in pps (0-100) or kbps (0, 100, 2*100, 3*100, ...,
1000000)

Example: Rate Limiter ID=10, Rate = 300kbps


Security/Network/ACL>rate 10 kbps 300

Result:
Rate Limiter Rate
------------ ----
..........
9 1 PPS
10 300 KBPS
.......
ACL Policy Syntax:
Security Network ACL Policy [<port_list>] [<policy>]

Example:
Security/Network/ACL>policy 1 2

Access Control List Syntax:


Security Network ACL Add [<ace_id>] [<ace_id_next>] [(port
<port_list>)] [(policy <policy> <policy_bitmask>)]
[<tagged>] [<vid>] [<tag_prio>] [<dmac_type>] [(etype
[<etype>] [<smac>] [<dmac>]) |

301
(arp [<sip>] [<dip>] [<smac>] [<arp_opcode>] [<arp_flags>]) |
(ip [<sip>] [<dip>] [<protocol>] [<ip_flags>]) |
(icmp [<sip>] [<dip>] [<icmp_type>] [<icmp_code>]
[<ip_flags>]) |
(udp [<sip>] [<dip>] [<sport>] [<dport>] [<ip_flags>]) |
(tcp [<sip>] [<dip>] [<sport>] [<dport>] [<ip_flags>]
[<tcp_flags>])]
[permit|deny] [<rate_limiter>] [<port_redirect>] [<mirror>]
[<logging>][<shutdown>]

Parameters:
<ace_id> : ACE ID (1-256), default: Next available ID
<ace_id_next> : Next ACE ID (1-256), default: Add ACE last
port : Port ACE keyword
<port_list> : Port list or 'all', default: All ports
policy : Policy ACE keyword
<policy> : Policy number (0-255)
<policy_bitmask>: Policy number bitmask (0x0-0xFF)
<tagged> : Tagged of frames: any|enable|disable
<vid> : VLAN ID (1-4095) or 'any'
<tag_prio> : VLAN tag priority (0-7) or 'any'
<dmac_type> : DMAC type:
any|unicast|multicast|broadcast
etype : Ethernet Type keyword
<etype> : Ethernet Type: 0x600 - 0xFFFF or 'any' but
excluding 0x800(IPv4) 0x806(ARP) and 0x86DD(IPv6)
<smac> : Source MAC address ('xx-xx-xx-xx-xx-xx'
or 'xx.xx.xx.xx.xx.xx' or 'xxxxxxxxxxxx', x is a hexadecimal
digit) or 'any'
<dmac> : Destination MAC address
('xx-xx-xx-xx-xx-xx' or 'xx.xx.xx.xx.xx.xx' or 'xxxxxxxxxxxx', x is
a hexadecimal digit) or 'any'
arp : ARP keyword
<sip> : Source IP address (a.b.c.d/n) or 'any'
<dip> : Destination IP address (a.b.c.d/n) or 'any'
<arp_opcode> : ARP operation code: any|arp|rarp|other
<arp_flags> : ARP flags: request|smac|tmac|len|ip|ether
[0|1|any]
ip : IP keyword
<protocol> : IP protocol number (0-255) or 'any'
<ip_flags> : IP flags: ttl|options|fragment [0|1|any]
icmp : ICMP keyword
<icmp_type> : ICMP type number (0-255) or 'any'
<icmp_code> : ICMP code number (0-255) or 'any'
udp : UDP keyword
<sport> : Source UDP/TCP port range (0-65535) or
'any'
<dport> : Destination UDP/TCP port range (0-65535)
or 'any'
tcp : TCP keyword
<tcp_flags> : TCP flags: fin|syn|rst|psh|ack|urg [0|1|any]
permit : Permit forwarding (default)
deny : Deny forwarding
<rate_limiter> : Rate limiter number (1-15) or 'disable'
<port_redirect> : Port list for copy of frames or 'disable'
<mirror> : Mirror of frames: enable|disable
<logging> : System logging of frames: log|log_disable
<shutdown> : Shut down ingress port: shut|shut_disable

302
Example:
Add one ACE:
Security/Network/ACL>add 2 port 6-10 policy 3 8 ip
ACE ID 2 added last

Edit one ACE:


Security/Network/ACL>add 1 port 1-5 policy 2 8 any
ACE ID 1 modified last

Result:
ID Type Port Policy Frame Action Rate L. Port C. Mirror Counter
-- ------- -------- -------- ----- ------ -------- -------- -------- -------
1 User 1-5 2 /0x8 Any Permit Disabled Disabled Disabled 0
2 User 6-10 3 /0x8 IP Permit Disabled Disabled Disabled 0

DHCP
DHCP Snooping Syntax:
Security Network DHCP Snooping Mode [enable|disable]
Security Network DHCP Snooping Port Mode [<port_list>]
[trusted|untrusted]
Security Network DHCP Snooping Statistics [<port_list>]
[clear]

Example:
Security/Network>dhcp snooping mode en
Security/Network>dhcp snooping port mode 1 tru (Port 1)
Security/Network>dhcp snooping port mode 1-10 tru (Port
1-10)

DHCP Relay Syntax:


Security Network DHCP Relay Mode [enable|disable]
Security Network DHCP Relay Server [<ip_addr>]
Security Network DHCP Relay Information Mode
[enable|disable]
Security Network DHCP Relay Information Policy
[replace|keep|drop]

Example:
Security/Network>dhcp relay server 192.168.2.100
Security/Network>dhcp relay mode en
(Assign one Server IP before enable the Relay mode)

Security/Network>dhcp rel info mode en


Security/Network>dhcp rel info policy keep

IP Source Guard
IP Source Guard Syntax:
Security Network IP Source Guard Configuration
Configuration Security Network IP Source Guard Mode [enable|disable]
Security Network IP Source Guard Port Mode [<port_list>]
[enable|disable]
Security Network IP Source Guard limit [<port_list>]
[<dynamic_entry_limit>|unlimited]
Security Network IP Source Guard Entry [<port_list>]
add|delete <vid> <allowed_ip> <allowed_mac>
Security Network IP Source Guard Status [<port_list>]

303
Security Network IP Source Guard Translation

Example:
Security/Network>ip source guard mode en
Security/Network>ip source guard port mode 1-10 en (Port
1-10)
Security/Network>ip source guard limit 1-10 2 (limit 2 MAC
Address)

IP Source Guard Syntax:


Security Network IP Source Guard Entry [<port_list>]
Static Table add|delete <vid> <allowed_ip> <allowed_mac>

Example:
Security/Network>ip source guard entry 5 add 2
192.168.2.101 001122334455

Result:
IP Source Guard Entry Table:

Type Port VLAN IP Address MAC Address


------- ---- ---- --------------- -----------------
Static 1 1 192.168.2.10 11-22-33-44-55-66
Static 5 2 192.168.2.101 00-0b-16-21-2c-37

ARP Inspection
ARP Inspection Syntax:
Security Network ARP Inspection Configuration
Security Network ARP Inspection Mode [enable|disable]
Security Network ARP Inspection Port Mode [<port_list>]
[enable|disable]
Security Network ARP Inspection Entry [<port_list>]
add|delete <vid> <allowed_mac> <allowed_ip>
Security Network ARP Inspection Status [<port_list>]
Security Network ARP Inspection Translation

Example:
Security/Network>arp inspection mode en
Security/Network>arp inspection port mode 1-10 en
Security/Network>arp inspection entry 1 add 10
112233445566 192.168.2.10

Security/Network>arp inspection status

ARP Inspection Entry Table:

Type Port VLAN MAC Address IP Address


------- ---- ---- ----------------- -------------
Static 1 10 0b-16-21-2c-37-42 192.168.2.10

Security-AAA Configuration
Common Server Syntax:
Security AAA Timeout [<timeout>]
Configuration Security AAA Deadtime [<dead_time>]

RADIUS Syntax:
Security AAA RADIUS [<server_index>] [enable|disable]

304
Authentication Server [<ip_addr_string>] [<secret>] [<server_port>]

Example:
Security>aaa radi 1 en 192.168.2.200 password 1812

RADIUS Accounting Syntax:


Security AAA ACCT_RADIUS [<server_index>]
Server [enable|disable] [<ip_addr_string>] [<secret>] [<server_port>]

Example:
Security>aaa ACCT_radi 1 en 192.168.2.200 password 1813

TACACS+ Syntax:
Security AAA TACACS+ [<server_index>] [enable|disable]
Authentication Server [<ip_addr_string>] [<secret>] [<server_port>]

Example:
Security>aaa tacacs+ 1 en 192.168.2.200 password 49

AAA Configuration Security>aaa con

AAA Configuration:

==================

Server Timeout : 15 seconds

Server Dead Time : 300 seconds

RADIUS Authentication Server Configuration:

===========================================

Server Mode IP Address Secret Port

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

1 Enabled 192.168.2.200 ******** 1812

2 Disabled 1812

3 Disabled 1812

4 Disabled 1812

5 Disabled 1812

RADIUS Accounting Server Configuration:

=======================================

Server Mode IP Address Secret Port

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

1 Enabled 192.168.2.200 ******** 1813

2 Disabled 1813

3 Disabled 1813

4 Disabled 1813

5 Disabled 1813

TACACS+ Authentication Server Configuration:

============================================

Server Mode IP Address Secret Port

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

1 Enabled 192.168.2.200 ******** 49

2 Disabled 49

3 Disabled 49

4 Disabled 49

5 Disabled 49

Security>

305
5. Aggregation Configuration

Feature Command Line


Static Aggregation Configuration
Aggregation Group Syntax:
Aggr Add <port_list> [<aggr_id>]
Configuration
Example: Add port 5-8 to Group 1
>aggr add 5-8 1

>aggr del 1 (Delete the group 1)

Hash Code Syntax:


Aggr Mode [smac|dmac|ip|port] [enable|disable]
Contributors
smac = Source MAC Address
dmac = Destination MAC Address
ip = IP Address
port = TCP/UDP Port Number

Example: Only the Source MAC Hash is enabled. The rest


mode are disabled.

>agg mode smac en


>agg mode dmac dis
>agg mode ip dis
>agg mode port dis

LACP
LACP Port Syntax:
LACP Configuration [<port_list>]
Configuration LACP Mode [<port_list>] [enable|disable]
LACP Key [<port_list>] [<key>]
LACP Role [<port_list>] [active|passive]
LACP Status [<port_list>]
LACP Statistics [<port_list>] [clear]

Example: Configure port 5-8 to a LACP group


>lacp mode 5-8 en (Mode = Enable)
>lacp key 5-8 100 (Key = 100)
>lacp role 5-8 act (Role = Enable)

6. Loop Protection

Feature Command Line


General Settings
Enable Loop Syntax:
Loop Protect Mode [enable|disable]

306
Protection Loop Protect Transmit [<transmit-time>]
Loop Protect Shutdown [<shutdown-time>]

Example:
>loop protect mode en
Transmission Time >loop protect trans 10 (10 seconds)
Shutdown Time >loop protect shut 200 (200 seconds)
Port Configuration
Loop Protection - Port Syntax:
Loop Protect Port Mode [<port_list>] [enable|disable]
Configuration Loop Protect Port Action [<port_list>] [shutdown|shut_log|log]
Loop Protect Port Transmit [<port_list>] [enable|disable]

Example:
Loop/Protect>port mode 1 en
Loop/Protect>port action 1 shut_log (Shutdown Port and Log)
Loop/Protect>port transmit 1 en

7. Spanning Tree

Feature Command Line


Bridge Configuration
Protocol Version Syntax:
STP Version [<stp_version>]

Parameters:
<stp_version>: mstp|rstp|stp

Example:
STP>ver rstp

Bridge Priority Syntax:


STP Msti Priority [<msti>] [<priority>]

Example:
STP>msti pri
MSTI# Bridge Priority
----- ---------------
CIST 32768

STP>msti pri 4096

(The available priority parameter includes: 0, 4096, 8192,


12288, 16384, 20480, 24576, 28672, 32768, 36864, 40960,
45056, 49152, 53248, 57344, 61440)
Forward Delay Syntax:
STP FwdDelay [<delay>]
(Valid values are in the range 4 to 30 seconds)

307
Max. Age Syntax:
STP MaxAge [<max_age>]
(Valid values are in the range 6 to 40 seconds, and MaxAge must be
<= (FwdDelay-1)*2.)
Maximum Hop Count Syntax:
STP MaxHops [<maxhops>]
(Valid values are in the range 6 to 40 hops)
Transmit Hold Count Syntax:
STP Txhold [<holdcount>]
(Valid values are in the range 1 to 10 BPDU's per second.)
Advanced Setting Syntax:
STP bpduFilter [enable|disable]
STP bpduGuard [enable|disable]
STP recovery [<timeout>]
(After recovery timeout time is set, the recovery is enabled
automatically.)
MSTI Mapping
MSTI/VLAN Mapping Syntax:
STP Msti Add <msti> <vid-range>

Example:
STP>mst add 1 100
Add VLAN 100 to MSTI1

STP>mst map
MSTI VLANs mapped to MSTI
---- --------------------
MSTI1 100
MSTI2 No VLANs mapped
MSTI3 No VLANs mapped
MSTI4 No VLANs mapped
MSTI5 No VLANs mapped
MSTI6 No VLANs mapped
MSTI7 No VLANs mapped

Port Setting
STP Port Mode Syntax:
STP Port Mode [<port_list>] [enable|disable]
STP Port Edge [<port_list>] [enable|disable]
STP Port AutoEdge [<port_list>] [enable|disable]
STP Port P2P [<port_list>] [enable|disable|auto]
STP Port RestrictedRole [<port_list>] [enable|disable]
STP Port RestrictedTcn [<port_list>] [enable|disable]
STP Port bpduGuard [<port_list>] [enable|disable]
STP Port Statistics [<port_list>] [clear]

Example:
STP>port mode 1-24 dis (Disable STP on port 1-24)
STP>port edge 1-24 en (Enable Edge port on port 1-24)
STP>port autoedge 1-24 en (Enable Auto Edge on P1-24)
STP>port p2p 1-24 en (Enable P2P mode on P1-24)
STP>port p2p 1-24 auto (Enable Automatic P2P detection)
STP>port bpdu 1-24 en (Enable BPDUGuard on P1-24)

308
Port Path Cost Syntax:
STP Msti Port Cost [<msti>] [<port_list>] [<path_cost>]

Parameters:
<msti> : STP bridge instance no (0-7, CIST=0, MSTI1=1, ...)
<port_list>: Port list or 'all'. Port zero means aggregations.
<path_cost>: STP port path cost (1-200000000) or 'auto'

Example: Configure CIST 0 Port Path Cost


STP>msti port cost 0 all auto (Path cost = auto)
STP>msti port cost 0 all 100000 (Path cost = 100000)

Port Priority Syntax:


STP Msti Port Priority [<msti>] [<port_list>] [<priority>]

Parameters:
<msti> : STP bridge instance no (0-7, CIST=0, MSTI1=1, ...)
<port_list>: Port list or 'all'. Port zero means aggregations.
<priority> : STP port priority (0/16/32/48/.../224/240)

Example: Configure CIST 0 Port Priority


STP Msti Port Priority [<msti>] [<port_list>] [<priority>]
STP>msti port priority 0 5 240 (Port 5 Priority = 240)
STP>msti port priority 0 all 128 (All Ports' priority = 128)

Example: Configure MSTI 1 Port Priority


STP>msti port priority 1 5 240 (MSTI1 port 5 priority=240)

8. MVR

Feature Command Line


MVR Configuration
MVR Mode Syntax:
MVR Mode [enable|disable]
MVR - VLAN Syntax:
Interface Setting MVR VLAN Setup [<mvid>] [add|del|upd] [(Name
<mvr_name>)]
Example: MVR VLAN 2, MVR Name = Source2
MVR>vlan setup 2 add Name Source2
MVR - Port Role Syntax:
MVR VLAN Port [<vid>|<mvr_name>] [<port_list>]
[source|receiver|inactive]

Example: Port 2 = Source Port, Port 6-7 = Receiver Port


MVR>vlan port 2 2 source
MVR>vlan port 2 6-7 rec
Immediately Leave Syntax:
MVR Immediate Leave [<port_list>] [enable|disable]

309
Example:
MVR>immedi leave 1-10 en
MVR Configuration MVR>conf (View the settings of above configuration)

MVR Configuration:
==================
MVR Mode: Enabled
MVR Interface Setting
VID Name Mode Tagging Priority LLQI
---- -------------------------------- ---------- -------- -------- -----
2 Source2 Dynamic Tagged 0 5
[Port Setting of Source2(VID-2)]
Source Port :2
Receiver Port: 6,7
Inactive Port: 1,3-5,8-26
[Channel Setting of Source2(VID-2)]
<Empty Channel Table>
MVR Immediate Leave Setting
Port Immediate Leave
---- ---------------
1 Enabled
2 Enabled
3 Enabled
4 Enabled
5 Enabled
6 Enabled
7 Enabled
8 Enabled
9 Enabled
10 Enabled
11 Disabled
12 Disabled

9. IPMC

Feature Command Line


IGMP Snooping Configuration
IGMP Snooping Syntax:
Enable IPMC Mode [mld|igmp] [enable|disable]
Example:
IPMC>mode igmp en
Unregistered IPMCv4 Syntax:
Flooding Enabled IPMC Flooding [mld|igmp] [enable|disable]
Example:
IPMC>flood igmp en
IGMP SSM Range Syntax:
(Source-Specific IPMC SSM [mld|igmp] [(Range <prefix> <mask_len>)]
Multicast) Example:
IPMC>ssm igmp range 239.0.0.0 8
(Range from 239.0.0.0, mask length=8)

310
Leave Proxy Enable Syntax:
IPMC Leave Proxy [mld|igmp] [enable|disable]
Example:
IPMC>leave proxy igmp en (Enable)
IPMC>leave proxy igmp dis (Disable)
Proxy Enable Syntax:
IPMC Proxy [mld|igmp] [enable|disable]
Example:
IPMC>proxy igmp en (Enable)
IPMC>proxy igmp dis (Disable)
Port Related Syntax:
Configuration IPMC Router [mld|igmp] [<port_list>] [enable|disable]
IPMC Fastleave [mld|igmp] [<port_list>] [enable|disable]
(Router Port, Fast IPMC Throttling [mld|igmp] [<port_list>] [limit_group_number]
Leave, Throttling) Example:
IPMC>router igmp 25-26 en (Port 25-26 are router ports)
IPMC>Fast igmp 1-24 en (Enable IGMP Fast Leave on P1-24)
IPMC>thro igmp 1-2 5 (Throtting of Port 1, 2 is 5 groups.)
VLAN Configuration Syntax:
IPMC State [mld|igmp] [<vid>] [enable|disable]
IPMC Querier [mld|igmp] [<vid>] [enable|disable]
IPMC Compatibility [mld|igmp] [<vid>] [auto|v1|v2|v3]

IPMC Parameter RV [mld|igmp] [<vid>] [ipmc_param_rv]


IPMC Parameter QI [mld|igmp] [<vid>] [ipmc_param_qi]
IPMC Parameter QRI [mld|igmp] [<vid>] [ipmc_param_qri]
IPMC Parameter LLQI [mld|igmp] [<vid>] [ipmc_param_llqi]
IPMC Parameter URI [mld|igmp] [<vid>] [ipmc_param_uri]

Example:
IPMC>state igmp 2 en (Enable IGMP Snooping on VLAN 2)
IPMC>quer igmp 2 en (Enable IGMP Querier on VLAN 2)
IPMC>compa igmp 2 v2 (Enable IGMPv2 on VLAN 2)

MLD Snooping
MLD Snooping Note: The MLD Snooping is applied to IPv6 Multicast. The
commands are the same as above IGMP Snooping (IPv4)
Commands. Just chooses mld instead of igmp when seeing
[mld|igmp] in the syntax. The IP Address should be IPv6
format for sure.

10. LLDP Configuration

311
Feature Command Line
LLDP Parameters
LLDP Timers Syntax:
LLDP Interval [<interval>]
LLDP Hold [<hold>]
LLDP Delay [<delay>]
LLDP Reinit [<reinit>]
Example:
LLDP>interval 30
LLDP>hold 4
LLDP>delay 2
LLDP>reini 2
LLDP Mode Syntax:
LLDP Mode [<port_list>] [enable|disable|rx|tx]
(rx=RX Only, tx=TX Only)

Example: Enable LLDP on Ports


LLDP>mode 1-10 en (Port 1-10 are enabled)
LLDP>mode 1-26 en (Port 1-26 are enabled)
CDP aware Syntax:
LLDP cdp_aware [<port_list>] [enable|disable]

Example: Enable CDP on Port 1-5


LLDP>cdp_a 1-5 en (CDP on Port 1-5 are enabled)
LLDP Optional_TLV Syntax:
Parameters LLDP optional_TLV [<port_list>]
[port_descr|sys_name|sys_descr|sys_capa|mgmt_addr]
[enable|disable]
Example:
LLDP>option 1-3 port en
LLDP>option 1-3 sys_name en
LLDP>option 1-3 sys_desc en
LLDP>option 1-3 sys_capa en
LLDP>option 1-3 mgmt_add en

11. Power over Ethernet Configuration

Feature Command Line


PoE Configuration
PoE Configuration Syntax:
PoE Mgmt_mode
[class_con|class_res|al_con|al_res|lldp_res|lldp_con]
Parameters:
class_con : Class + Actual Consumption
class_res : Class + Reserved Power
al_con : Allocation + Actual Consumption
al_res : Allocation + Reserved Power
lldp_con : LLDP-MED + Actual Consumption
lldp_res : LLDP-MED + Reserved Power

Example:
PoE>mgmt class_con

312
PoE Power Supply Syntax:
Configuration PoE Maximum_Power [<port_list>] [<port_power>]
(Warning: The default Parameters:
value is for reference <port_list> : Port list or 'all', default: All ports
only. If the value is <port_power>: PoE maximum power for the port (0-15.4 Watt
not comfort to your for PoE mode, 0-30.0 Watt for PoE+ mode)
product specification,
please give the Example:
correct value before PoE>max 1-24 10 (Max. power of Port 1-24 to 10Watt)
you start using PoE PoE>max 1-24 15.4 (Max. power of Port 1-24 to 15.4 Watt)
function.)
PoE Port Syntax:
Configuration PoE Mode [<port_list>] [disabled|poe|poe+]

Parameters:
<port_list>: Port list or 'all', default: All ports
disables : Disable PoE
poe: Enables PoE IEEE 802.3af (Class 4 limited to 15.4W)
poe+: Enables PoE+ IEEE 802.3at (Class 4 limited to 30W)
(default: Show PoE's mode)

Example: Set Port 1-24 ro PoE+ mode


PoE>mode 1-24 poe+

PoE Status Primary Power Supply


PoE>prim
Primary Power Supply
---------------------
200 [W]

Port Status
PoE>sta
Port PD Class Port Status Power Used [W] Current Used [mA]

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

1 - No PD detected 0.0 0

2 - No PD detected 0.0 0

12. MAC Address Table Configuration

Feature Command Line


MAC Address Table Configuration
Aging Time Syntax:
Configuration MAC Agetime [<age_time>]
Parameters:
<age_time>: MAC address age time (0,10-1000000)
0=disable
Example:

313
MAC>age 100 (change aging time to 100 seconds, the aging
time range is 10-1000000)
MAC>age 0 (0 = Disable Aging time)
MAC Learning Syntax:
Configuration MAC Learning [<port_list>] [auto|disable|secure]
Example:
MAC>lear 1-8 sec
MAC>lear 9-12 dis
MAC>learn 1-12 auto
Static MAC Table Syntax:
MAC Add <mac_addr> <port_list> [<vid>]
Example:
MAC>add 0b16212c3742 1-5 1 (This type will be changed to
hexadecimal automatically.)
MAC>add 0b-16-21-2c-37-42 1-10 1 (This type is
hexadecimal, it will not be changed.)

Result:
Non-volatile static:
VID MAC Address Ports
--- ----------------- -----
1 00-10-15-02-25-2a 1-5
1 0b-16-21-2c-37-42 1-10

13. VLAN Configuration

Feature Command Line


VLAN Configuration
VLAN Membership Syntax:
VLAN Add <vid>|<name> [<ports_list>]
VLAN Name Add <name> <vid>
Example:
VLAN>add 3 5-8 (Add port 5-8 to VLAN 3)
VLAN>name add vlan3 3 (vlan3 is the name of VLAN 3)

Port Configuration Syntax:


VLAN FrameType [<port_list>] [all|tagged|untagged]
VLAN IngressFilter [<port_list>] [enable|disable]
VLAN tx_tag [<port_list>] [untag_pvid|untag_all|tag_all]
VLAN PortType [<port_list>]
[unaware|c-port|s-port|s-custom-port]
Example:
VLAN>framety 1-3 all
VLAN>ingr 1-3 en
VLAN>tx_t 1-3 untag_pvid
VLAN>portty 1-3 un

314
14. Private VLAN Configuration

Feature Command Line


PVLAN Configuration
PVLAN Configuration Syntax:
PVLAN Configuration [<port_list>]
PVLAN Add <pvlan_id> [<port_list>]
PVLAN Delete <pvlan_id>
PVLAN Lookup [<pvlan_id>]
PVLAN Isolate [<port_list>] [enable|disable]
Example:
PVLAN>add 10 9-12
PVLAN>add 10 1-2
PVLAN>add 20 1-2
PVLAN>add 20 13-18
PVLAN>iso 9-18 en (Enable Isolated Ports)
Result:
PVLAN ID Ports
-------- -----
1 1-8,17-26
10 1,2
20 13-18

15. VCL Configuration


Feature Command Line
MAC-based VLAN Configuration
MAC-based VLAN Syntax:
Configuration VCL Macvlan Add <mac_addr> <vid> [<port_list>]
Example:
VCL/Macvlan>add 001122334455 10 1-4
Result:
VCL/Macvlan>conf
MAC Address VID Ports
----------------- ---- -----
00-0b-16-21-2c-37 10 1-4

Protocol-based VLAN Configuration


Protocol to Group Syntax:
VCL ProtoVlan Protocol Add Eth2 <ether_type>|arp|ip|ipx|at
<group_id>
Example:
VCL/ProtoVlan>protocol add Eth2 0x0808 E4

Group to VLAN Syntax:


VCL ProtoVlan Vlan Add [<port_list>] <group_id> <vid>

315
Example:
VCL/ProtoVlan>vlan add 1-8 E4 10

Protocol VLAN Result:


Configuration VCL/ProtoVlan>conf
Protocol Type Protocol (Value) Group ID
------------- ------------------------ --------
EthernetII ETYPE:0x808 E4
LLC_Other DSAP:0xff; SSAP:0xff L3
LLC_SNAP OUI-00:e0:2b; PID:0x1 S2
EthernetII ETYPE:0x800 E1

Group ID VID Ports


---------------- ---- -----
E4 10 1-8
E1 10 5-8

IP Subnet-based VLAN Configuration


IP Subnet-based Syntax:
VLAN Configuration VCL IPVlan Add [<vce_id>] <ip_addr_mask> <vid>
[<port_list>]

Parameters:
<vce_id> : Unique VCE ID for each VCL entry
<ip_addr_mask>: Source IP address and mask (Format:
a.b.c.d/n).
<vid> : VLAN ID (1-4095)
<port_list> : Port list or 'all', default: All ports

Example:
VCL/IPVlan>add 1 192.168.10.0/24 10 1-10

Result:
VCE ID IP Address Mask Length VID Ports
------ --------------- ----------- ---- -----
1 192.168.10.0 24 10 1-10

16. Voice VLAN Configuration

Feature Command Line


Voice VLAN Configuration
Voice VLAN Syntax:
Configuration Voice VLAN Mode [enable|disable]
Voice VLAN ID [<vid>]
Voice VLAN Agetime [<age_time>]
Voice VLAN Traffic Class [<class>]
Example:
Voice>vlan mode en
Voice>vlan id 100
Voice>vlan age 86400
Voice>vlan traff class 7
Result:
Voice VLAN Configuration:

316
=========================

Voice VLAN Mode : Enabled


Voice VLAN VLAN ID : 100
Voice VLAN Age Time(seconds) : 86400
Voice VLAN Traffic Class :7
Port Configuration Syntax:
Voice VLAN Port Mode [<port_list>] [disable|auto|force]
Voice VLAN Security [<port_list>] [enable|disable]
Voice VLAN Discovery Protocol [<port_list>] [oui|lldp|both]
Example:
Voice/VLAN>port mode 1-4 auto
Voice/VLAN>security 1-4 en
Voice/VLAN>disco pro 1-4 both
Result:
Voice VLAN Port Configuration:
==============================

Port Mode Security Discovery Protocol


---- -------- -------- ------------------
1 Auto Enabled Both
2 Auto Enabled Both
3 Auto Enabled Both
4 Auto Enabled Both

OUI Configuration Syntax:


Voice VLAN OUI Add <oui_addr> [<description>]
Voice VLAN OUI Delete <oui_addr>
Voice VLAN OUI Clear
Voice VLAN OUI Lookup [<oui_addr>]
Example:
Voice/VLAN>oui add 00-12-08 hello
Result:
Voice/VLAN>oui lookup

Voice VLAN OUI Table:


=====================

Telephony OUI Description


------------- -----------
00-01-E3 Siemens AG phones
00-03-6B Cisco phones
00-0F-E2 H3C phones
00-60-B9 Philips and NEC AG phones
00-D0-1E Pingtel phones
00-E0-75 Polycom phones
00-E0-BB 3Com phones
00-12-77 e10
00-12-08 hello

17. QoS Configuration

Feature Command Line


QoS Configuration

317
Port Syntax:
Classification QoS Port Classification Class [<port_list>] [<class>]
QoS Port Classification DPL [<port_list>] [<dpl>]
QoS Port Classification PCP [<port_list>] [<pcp>]
QoS Port Classification DEI [<port_list>] [<dei>]
QoS Port Classification Tag [<port_list>] [enable|disable]
QoS Port Classification Map [<port_list>] [<pcp_list>] [<dei_list>]
[<class>] [<dpl>]
QoS Port Classification DSCP [<port_list>] [enable|disable]
Range of the Value:
<class>: QoS class (0-7)
<dpl>: Drop Precedence Level (0-1)
<pcp>: Priority Code Point (0-7)
<dei>: Drop Eligible Indicator (0-1)

Example:
QoS/Port/Classification>clas 1-2 7
QoS/Port/Classification>dpl 1-2 1
QoS/Port/Classification>pcp 1-2 7
QoS/Port/Classification>dei 1-2 1
QoS/Port/Classification>tag 1-2 en
QoS/Port/Classification>dscp 1-2 en

QoS Ingress Port Syntax:


Tag QoS Port Classification Map [<port_list>] [<pcp_list>] [<dei_list>]
[<class>] [<dpl>]
Classification
Port Policing Syntax:
QoS Port Policer Mode [<port_list>] [enable|disable]
QoS Port Policer Rate [<port_list>] [<rate>]
QoS Port Policer Unit [<port_list>] [kbps|fps]
QoS Port Policer FlowControl [<port_list>] [enable|disable]

<rate> : Rate in kbps or fps (100-3300000)


Example:
QoS/Port/Policer>mode 1-2 en
QoS/Port/Policer>rate 1-2 300
QoS/Port/Policer>unit 1-2 kbps
QoS/Port/Policer>flow 1-2 en

Port Scheduler Syntax:


Syntax:
QoS Port Scheduler Mode [<port_list>] [strict|weighted]
Example:
QoS/Port/Scheduler>mode 1-2 stric (Strict Priority)
QoS/Port/Scheduler>mode 1-2 wei (Weighted)

QoS Egress Port Scheduler and Shapers


QoS/Port/Scheduler>wei 1-2 1 30 (Port 1-2, Q1=30)
QoS/Port/Scheduler>wei 1-2 2 30 (Port 1-2, Q2=30)

318
Port Shaping Syntax:
Port Shaper:
QoS Port Shaper Mode [<port_list>] [enable|disable]
QoS Port Shaper Rate [<port_list>] [<bit_rate>]

Queue Shaper:
QoS Port QueueShaper Mode [<port_list>] [<queue_list>]
[enable|disable]
QoS Port QueueShaper Rate [<port_list>] [<queue_list>]
[<bit_rate>]
QoS Port QueueShaper Excess [<port_list>] [<queue_list>]
[enable|disable]

Parameters:
<port_list>: Port list or 'all', default: All ports
<bit_rate> : Rate in kilo bits per second (100-3300000)

Example:
QoS/Port/Shaper>rate 1-2 1000
QoS/Port/QueueShaper>mode 1-2 all en (Queue Shaper)
QoS/Port/QueueShaper>rate 1-2 all 600 (Queue Shaper)

DSCP Syntax:
Configuration QoS Port DSCP Translation [<port_list>] [enable|disable]
QoS Port DSCP Classification [<port_list>] [none|zero|selected|all]
QoS Port DSCP EgressRemark [<port_list>]
[disable|enable|remap_dp_unaware|remap_dp_aware]

Note: DSCP is an advanced QoS setting, please follow the DSCP


table of upper access/core switch to configure the table. The table
of the whole network must be unified.
Storm Configuration
Strom Control Syntax:
QoS Storm Unicast [enable|disable] [<packet_rate>]

319
QoS Storm Multicast [enable|disable] [<packet_rate>]
QoS Storm Broadcast [enable|disable] [<packet_rate>]

<packet_rate>: Rate in fps (1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1k,
2k, 4k, 8k, 16k, 32k, 64k, 128k, 256k, 512k, 1024k, 2048k, 4096k,
8192k, 16384k, 32768k)

Example:
QoS/Storm>unic en 32768k
QoS/Storm>multi en 4096k
QoS/Storm>broad en 4k

18. Mirroring Configuration

Feature Command Line


Mirroring Configuration
Mirror Configuration Syntax:
Mirror Port [<port>|disable]
Mirror Mode [<port_cpu_list>] [enable|disable|rx|tx]
Example:
Mirror>port 5
Mirror>mode 6-8 en
Result:
Mirror Configuration:
=====================

Mirror Port: 5

Port Mode
---- --------
1 Disabled
2 Disabled
3 Disabled
4 Disabled
5 Disabled
6 Enabled
7 Enabled
8 Enabled

19. UPnP Configuration


Feature Command Line
UPnP Configuration
UPnp Configuration Syntax:
UPnP Configuration
UPnP Mode [enable|disable]
UPnP TTL [<ttl>]
UPnP AdvertisingDuration [<duration>]

320
Example:
UPnP>mode en
UPnP>ttl 5 (Default=4)
UPnP>adver 200 (Default=100)
Result:
UPnP Configuration:
===================

UPnP Mode : Enabled


UPnP TTL :5
UPnP Advertising Duration : 200

20. sFlow Configuration

Feature Command Line


sFlow Configuration
Receiver Syntax:
Configuration sFlow Receiver [release] [<timeout>] [<ip_addr_host>]
[<udp_port>] [<datagram_size>]
Example:
sFlow>receiver 10 192.168.2.100 6343 1400

Result:
Receiver Configuration:
=======================

Owner : <none>
Receiver : 192.168.2.100
UDP Port : 6343
Max. Datagram: 1400 bytes
Time left : 0 seconds
Receiver Release sFlow>receiver
Port Configuration Syntax:
sFlow Receiver [release] [<timeout>] [<ip_addr_host>]
[<udp_port>] [<datagram_size>]
sFlow FlowSampler [<port_list>] [<sampling_rate>]
[<max_hdr_size>]
sFlow CounterPoller [<port_list>] [<interval>]
sFlow Statistics Receiver [clear]
sFlow Statistics Samplers [<port_list>] [clear]
Example:

sFlow>flow 1-2 10 128 (Enable FlowSample on port 1-2,


rate=10, max. size=128)

sFlow>coun 1-2 5 (Enable CounterPoller of port 1-2, and


set interval to 5)

sFlow>statistic sample 1-2

Per-Port Statistics:

321
====================
Port Rx Flow Samples Tx Flow Samples Counter Samples
---- --------------- --------------- ---------------
1 0 0 0
2 0 0 0

21. Diagnostic Commands


Feature Command Line
Ping
Ping Test Syntax:
IP Ping <ip_addr_string> [(Length <ping_length>)] [(Count
<ping_count>)] [(Interval <ping_interval>)]

Parameters:
<ip_addr_string>: IPv4 host address (a.b.c.d) or a host name
string
length : PING Length keyword
<ping_length> : Ping ICMP data length (2-1452; Default is
56), excluding MAC,
IP and ICMP headers
count : PING Count keyword
<ping_count> : Transmit ECHO_REQUEST packet count
(1-60; Default is 5)
interval : PING Interval keyword
<ping_interval> : Ping interval (0-30; Default is 0)

Example: Ping IP 192.168.2.100


IP>ping 192.168.2.100
PING server 192.168.2.100, 56 bytes of data.
64 bytes from 192.168.2.100: icmp_seq=0, time=0ms
64 bytes from 192.168.2.100: icmp_seq=1, time=0ms
64 bytes from 192.168.2.100: icmp_seq=2, time=0ms
64 bytes from 192.168.2.100: icmp_seq=3, time=0ms
64 bytes from 192.168.2.100: icmp_seq=4, time=0ms
Sent 5 packets, received 5 OK, 0 bad

IPv6 Ping Test Syntax:


IP IPv6 Ping6 <ipv6_addr> [(Length <ping_length>)] [(Count
<ping_count>)] [(Interval <ping_interval>)]
Example:
poeswitch:/IP>ipv6 ping6 2001:DB8::250:8bff:fee8:f800
VeriPHY Syntax:
Port VeriPHY [<port_list>]
Example:
Port>veriphy 24

Starting VeriPHY, please wait

Port Pair A Length Pair B Length Pair C Length Pair D Length

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

322
24 OK 0 OK 0 OK 0 OK 0

22. Maintenance Commands


Feature Command Line
Maintenance Commands
Restart Device Syntax:
System Reboot
Example:
System>reb
System will reboot in a few seconds

Factory Defaults Syntax:


System Restore Default [keep_ip]

Example:

Software/Firmware Syntax:
(Firmware Version, Firmware Information
Firmware Swap
Firmware Swapping, Firmware Load <ip_addr_string> <file_name>
Parameters of Firmware Load:
Firmware Update)
<ip_addr_string>: IP host address (a.b.c.d) or a host name
string
<file_name> : Firmware file name

Example:
Firmware Swapping
Firmware>sw
... Erase from 0x40fd0000-0x40fdffff: .
... Program from 0x87ff0000-0x88000000 to 0x40fd0000: .
... Program from 0x87ff000a-0x87ff000c to 0x40fd000a: .
Alternate image activated, now rebooting.
Firmware Update
Firmware>load 192.168.2.100 SMBStaX.dat
Downloaded "SMBStaX.dat", 3415213 bytes
Master initiated software updating starting
Waiting for firmware update to complete
Starting flash update - do not power off device!
Erasing image...
Programming image...
Note 1:
The switch process the firmware upgrading through TFTP
protocol. When running firmware upgrading, please open the
TFTP tool as TFTP server for the switch.
For example: TFTPd32 is a freeware TFTP server, you can
download it from the internet. Browse the directory of the
firmware file and select correct server interface.
If you failed to upload file, remember to shut down the
firewall of your computer. The process may be terminated by
your firewall.

323
Note 2: While firmware uploading process is started,
please don't shutdown the switch!

P/N: V10120140507

324

You might also like