How it Works
Interlogix
Loading...
POC2502-16CXP-2T-2S
Quick Start Guide
6 pgs493.77 Kb0
Specsheet
4 pgs958.77 Kb0
User Manual
349 pgs6.46 Mb0
Table of contents
Loading...

Interlogix POC2502-16CXP-2T-2S, POC2502-8CXP-2T-2S User Manual

Download
POC2502 Series User Manual
P/N 1073045 • REV A • ISS 27AUG15
1
© Interlogix
Technolog
Th Other trade names used in this document may
trademarks of the manufacturers or vendors of the respective products.
Interlogix 3211 Progress Drive,
Lincolnton, NC 28092 USA
Authorized EU manufacturing representative: UTC Climate Controls & Security B.V., Kelvinstraat 7, 6003 DH Weert, Netherlands
Use this product onl y for the purpose i t was designed for; r e fer to the data sheet and user documentation for details. For the latest product information, contact your
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 desi the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the inst interference to radio communications.
You are cautioned tha t any changes or modifications not ex pr es sl y approved by the party responsible for compliance could void the user's authority to operate the equipment.
Notice! 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.
This Class A digital apparatus complies with Canadian ICES Cet app
Canada.
2004/108/EC (EMC Di rectiv e):
UTC Building & Industri al Syst ems, Inc.
declares that this device is in compliance with the essential requirements and other relevant provisions of Directive 2004/108/EC.
For contact information, see
www.utcfssecurityproducts.eu
C
2015 United Technol og i es Corpor at ion
is part of UTC Building & Industrial Systems,Inc. a unit of United
ies Corporation. All rights reserved.
e POC2502 Series name and logo are trademarks of United Technologies.
be trademarks or registered
local supplier or visit us online at www.interlogix.com.
N4131
gned to provide reasonable protection against harmful inter fer en c e w hen
ruction manual, may cause harmful
ACMA compl
areil numérique de la classe A est conforme á la norme NMB-003du
Hereby,
-003.
www.interlogix.com or
.
2
TABLE OF CONTENTS
1. INTRODUCTION .................................................................................................................... 10
1.1 Packet Contents ....................................................................................................................................... 10
1.2 Product Description ................................................................................................................................. 11
1.3 How to Use This Manual .......................................................................................................................... 16
1.4 Product Features ...................................................................................................................................... 16
1.5 Product Specifications ............................................................................................................................ 19
2. INSTALLATION ...................................................................................................................... 25
2.1 Hardware Description .............................................................................................................................. 25
2.1.1 Switch Front Panel ............................................................................................................................................... 25
2.1.2 LED Indications .................................................................................................................................................... 26
2.1.3 Switch Rear Panel ............................................................................................................................................... 28
2.2 Installing the Switch ................................................................................................................................. 29
2.2.1 Desktop Installation .............................................................................................................................................. 29
2.2.2 Rack Mounting ..................................................................................................................................................... 30
2.2.3 Installing the SFP transceiver .............................................................................................................................. 31
2.2.4 Installing the Long Reach PoE Communication ................................................................................................... 33
3. SWITCH MANAGEMENT ...................................................................................................... 38
3.1 Requirements ........................................................................................................................................... 38
3.2 Management A ccess Overvie w ............................................................................................................... 39
3.3 Administration Console ........................................................................................................................... 40
3.4 Web Management ..................................................................................................................................... 41
3.5 SNMP-based Network Management ....................................................................................................... 42
3.6 IFS Smart Discovery Utility ..................................................................................................................... 42
4. WEB CONFIGURATION ........................................................................................................ 44
4.1 Main Web Page ......................................................................................................................................... 47
4.1.1 Save Button ......................................................................................................................................................... 48
4.1.2 Configuration Manager ........................................................................................................................................ 49
4.1.2.1 Saving Configuration ................................................................................................................................. 50
3
4.2 System ...................................................................................................................................................... 51
4.2.1 System Information .............................................................................................................................................. 51
4.2.2 IP Configurations .................................................................................................................................................. 52
4.2.3 IPv6 Configuration ............................................................................................................................................... 54
4.2.4 User Configuration ............................................................................................................................................... 56
4.2.5 Time Settings ....................................................................................................................................................... 57
4.2.5.1 System Time .............................................................................................................................................. 57
4.2.5.2 SNTP Server Settings ................................................................................................................................ 60
4.2.6 Log Management ................................................................................................................................................. 61
4.2.6.1 Local Log ................................................................................................................................................... 61
4.2.6.2 Local Log ................................................................................................................................................... 62
4.2.6.3 Remote Syslog .......................................................................................................................................... 64
4.2.6.4 Log Message ............................................................................................................................................. 65
4.2.7 SNMP Management ............................................................................................................................................. 68
4.2.7.1 SNMP Overview ......................................................................................................................................... 68
4.2.7.2 SNMP System Information ......................................................................................................................... 69
4.2.7.3 SNMP View ................................................................................................................................................ 70
4.2.7.4 SNMP Access Group ................................................................................................................................. 72
4.2.7.5 SNMP Community ..................................................................................................................................... 73
4.2.7.6 SNMP User ................................................................................................................................................ 75
4.2.7.7 SNMPv1, 2 Notification Recipients ............................................................................................................ 76
4.2.7.9 SNMPv3 Notification Recipients ................................................................................................................ 77
4.2.7.10 SNMP Engine ID ...................................................................................................................................... 79
4.2.7.11 SNMP Remote Engine ID ........................................................................................................................ 80
4.3 Port Management ..................................................................................................................................... 82
4.3.1 Port Configuration ................................................................................................................................................ 82
4.3.2 POC Port Configuration ....................................................................................................................................... 84
4.3.3 Port Counters ....................................................................................................................................................... 85
4.3.4 Bandwidth Utilization ............................................................................................................................................ 90
4.3.5 Port Mirroring ....................................................................................................................................................... 91
4.3.6 Jumbo Frame ....................................................................................................................................................... 93
4.3.7 Port Error Disabled Configuration ........................................................................................................................ 94
4.3.8 Port Error Disabled............................................................................................................................................... 96
4.3.9 Protected Ports .................................................................................................................................................... 96
4.3.10 EEE .................................................................................................................................................................... 99
4.4 Link Aggregation .................................................................................................................................... 101
4.4.1 LAG Setting ........................................................................................................................................................ 103
4.4.2 LAG Managment ................................................................................................................................................ 104
4.4.3 LAG Port Setting ................................................................................................................................................ 105
4.4.4 LACP Setting ...................................................................................................................................................... 107
4
4.4.5 LACP Port Setting .............................................................................................................................................. 108
4.4.6 LAG Status ......................................................................................................................................................... 109
4.5 VLAN ....................................................................................................................................................... 112
4.5.1 VLAN Overview ................................................................................................................................................... 112
4.5.2 IEEE 802.1Q VLAN ............................................................................................................................................. 113
4.5.3 Management VLAN ............................................................................................................................................. 116
4.5.4 Create VLAN ....................................................................................................................................................... 117
4.5.5 Interface Settings ................................................................................................................................................ 118
4.5.6 Port to VLAN ...................................................................................................................................................... 123
4.5.7 Port VLAN Membership ..................................................................................................................................... 124
4.5.8 Protocol VLAN Group Setting ............................................................................................................................ 125
4.5.9 Protocol VLAN Port Setting ................................................................................................................................ 126
4.5.10 GVRP Setting ................................................................................................................................................... 128
4.5.11 GVRP Port Setting ........................................................................................................................................... 130
4.5.12 GVRP VLAN ..................................................................................................................................................... 132
4.5.13 GVRP Statistics ................................................................................................................................................ 132
4.5.14 VLAN setting example: .................................................................................................................................... 134
4.5.14.1 Two Separate 802.1Q VLANs ................................................................................................................ 134
4.5.14.2 VLAN Trunking between Two 802.1Q Aware Switches ......................................................................... 137
4.6 Spanning Tree Protocol ......................................................................................................................... 140
4.6.1 Theory ................................................................................................................................................................ 140
4.6.2 STP Global Settings ........................................................................................................................................... 146
4.6.3 STP Port Setting ................................................................................................................................................ 148
4.6.4 CIST Instance Setting ........................................................................................................................................ 151
4.6.5 CIST Port Setting ............................................................................................................................................... 153
4.6.6 MST Instance Configuration ............................................................................................................................... 154
4.6.7 MST Port Setting ................................................................................................................................................ 157
4.6.8 STP Statistics ..................................................................................................................................................... 159
4.7 Multicast .................................................................................................................................................. 160
4.7.1 Properties ........................................................................................................................................................... 160
4.7.2 IGMP Snooping .................................................................................................................................................. 162
4.7.2.1 IGMP Setting ............................................................................................................................................ 166
4.7.2.2 IGMP Querier Setting ............................................................................................................................... 168
4.7.2.3 IGMP Static Group ................................................................................................................................... 169
4.7.2.4 IGMP Group Table ................................................................................................................................... 170
4.7.2.5 IGMP Router Setting ................................................................................................................................ 171
4.7.2.6 IGMP Router Table .................................................................................................................................. 172
4.7.2.7 IGMP Forward All ..................................................................................................................................... 173
4.7.3 IGMP Snooping Statics ...................................................................................................................................... 174
4.7.4 MLD Snooping ................................................................................................................................................... 176
5
4.7.4.1 MLD Setting ............................................................................................................................................. 176
4.7.4.2 MLD Static Group..................................................................................................................................... 178
4.7.4.3 MLD Group T able ..................................................................................................................................... 179
4.7.4.4 MLD Router Setting ................................................................................................................................. 179
4.7.4.5 MLD Router T able .................................................................................................................................... 181
4.7.4.6 MLD Forward All ...................................................................................................................................... 182
4.7.5 MLD Snooping Statics ........................................................................................................................................ 183
4.7.6 Multicast Throttling Setting ................................................................................................................................. 185
4.7.7 Multicast Filter .................................................................................................................................................... 186
4.7.7.1 Multicast Profile Setting ........................................................................................................................... 187
4.7.7.2 IGMP Filter Setting ................................................................................................................................... 188
4.7.7.3 MLD Filter Setting .................................................................................................................................... 189
4.8 Quality of Service ................................................................................................................................... 191
4.8.1 Understand QoS ................................................................................................................................................ 191
4.8.2 General .............................................................................................................................................................. 192
4.8.2.1 QoS Properties ........................................................................................................................................ 192
4.8.2.2 QoS Port Settings .................................................................................................................................... 193
4.8.2.3 Queue Settings ........................................................................................................................................ 194
4.8.2.4 CoS Mapping ........................................................................................................................................... 195
4.8.2.5 DSCP Mapping ........................................................................................................................................ 197
4.8.2.6 IP Precedence Mapping ........................................................................................................................... 199
4.8.3 QoS Basic Mode ................................................................................................................................................ 200
4.8.3.1 Global Settings ........................................................................................................................................ 200
4.8.3.2 Port Settings ............................................................................................................................................ 201
4.8.4 Rate Limit ........................................................................................................................................................... 202
4.8.4.1 Ingress Bandwidth Control ....................................................................................................................... 202
4.8.4.2 Egress Bandwidth Control ....................................................................................................................... 204
4.8.4.3 Egress Queue .......................................................................................................................................... 205
4.8.5 Voice VLAN ........................................................................................................................................................ 207
4.5.8.1 Introduction to Voice VLAN ...................................................................................................................... 207
4.8.5.2 Properties................................................................................................................................................. 207
4.8.5.3 Telephony OUI MAC Setting .................................................................................................................... 209
4.8.5.4 Telephony OUI Port Setting ...................................................................................................................... 211
4.9 Security ................................................................................................................................................... 213
4.9.1 802.1X ................................................................................................................................................................ 213
4.9.1.1 Understanding IEEE 802.1X Port-based Authentication .......................................................................... 214
4.9.1.2 802.1X Setting ......................................................................................................................................... 217
4.9.1.3 802.1X Port Setting .................................................................................................................................. 218
4.9.1.4 Guest VLAN Setting ................................................................................................................................. 220
4.9.1.5 Authenticated Host ................................................................................................................................... 223
6
4.9.2 RADIUS Server .................................................................................................................................................. 223
4.9.3 T ACACS+ Server ............................................................................................................................................... 226
4.9.4 AAA .................................................................................................................................................................... 229
4.9.4.1 Login List ................................................................................................................................................. 230
4.9.4.2 Enable List ............................................................................................................................................... 231
4.9.5 Access ................................................................................................................................................................ 232
4.9.5.1 Telnet ....................................................................................................................................................... 232
4.9.5.2 SSH.......................................................................................................................................................... 233
4.9.5.3 HTTP........................................................................................................................................................ 235
4.9.5.4 HTTPs ...................................................................................................................................................... 237
4.9.6 Management Access Method ............................................................................................................................. 238
4.9.6.1 Profile Rules............................................................................................................................................. 238
4.9.6.2 Access Rules ........................................................................................................................................... 239
4.9.7 DHCP Snooping ................................................................................................................................................. 241
4.9.7.1 DHCP Snooping Overview ....................................................................................................................... 241
4.9.7.2 Global Setting .......................................................................................................................................... 242
4.9.7.3 VLAN Setting ........................................................................................................................................... 243
4.9.7.4 Port Setting .............................................................................................................................................. 245
4.9.7.5 Statistics ................................................................................................................................................... 246
4.9.7.6 Database Agent ....................................................................................................................................... 247
4.9.7.7 Rate Limit ................................................................................................................................................. 249
4.9.7.8 Option 82 Global Setting .......................................................................................................................... 251
4.9.7.9 Option 82 Port Setting ............................................................................................................................. 252
4.9.7.10 Option 82 Circuit-ID Setting ................................................................................................................... 254
4.9.8 Dynamic ARP Inspection .................................................................................................................................... 255
4.9.8.1 Global Setting .......................................................................................................................................... 255
4.9.8.2 VLAN Setting ........................................................................................................................................... 256
4.9.8.3 Port Setting .............................................................................................................................................. 257
4.9.8.4 Statistics ................................................................................................................................................... 259
4.9.8.5 Rate Limit ................................................................................................................................................. 260
4.9.9 IP Source Guard ................................................................................................................................................ 261
4.9.9.1 Port Settings ............................................................................................................................................ 262
4.9.9.2 Binding T able ........................................................................................................................................... 263
4.9.10 Port Security..................................................................................................................................................... 265
4.9.11 DoS .................................................................................................................................................................. 267
4.9.11.1 Global DoS Setting ................................................................................................................................. 267
4.9.11.2 DoS Port Setting .................................................................................................................................... 270
4.9.12 Storm Control ................................................................................................................................................... 272
4.9.12.1 Global Setting ........................................................................................................................................ 272
4.9.12.2 Port Setting ............................................................................................................................................ 273
4.10 ACL ........................................................................................................................................................ 275
7
4.10.1 MAC-based ACL .............................................................................................................................................. 275
4.10.2 MAC-based ACE .............................................................................................................................................. 276
4.10.3 IPv4-based ACL ............................................................................................................................................... 279
4.10.4 IPv4-based ACE ............................................................................................................................................... 279
4.10.5 IPv6-based ACL ............................................................................................................................................... 284
4.10.6 IPv6-based ACE ............................................................................................................................................... 285
4.10.7 ACL Binding ..................................................................................................................................................... 290
4.11 MAC Address Table .............................................................................................................................. 291
4.11.1 Static MAC Setting ........................................................................................................................................... 292
4.11.2 MAC Filtering .................................................................................................................................................... 293
4.11.3 Dynamic Address Setting ................................................................................................................................. 294
4.11.4 Dynamic Learned ............................................................................................................................................. 295
4.12 LLDP ...................................................................................................................................................... 297
4.12.1 Link Layer Discovery Protocol ......................................................................................................................... 297
4.12.2 LLDP Global Setting ......................................................................................................................................... 297
4.12.3 LLDP Port Setting ............................................................................................................................................ 300
4.12.4 LLDP Local Device ........................................................................................................................................... 303
4.12.5 LLDP Remote Device ....................................................................................................................................... 304
4.12.6 MED Network Policy ........................................................................................................................................ 306
4.12.7 MED Port Setting ............................................................................................................................................. 309
4.12.8 LLDP Overloading ............................................................................................................................................ 312
4.12.9 LLDP Statistics ................................................................................................................................................. 313
4.13 Diagnostics ........................................................................................................................................... 314
4.13.1 Cable Diagnostics ............................................................................................................................................ 315
4.13.2 Ping .................................................................................................................................................................. 317
4.13.3 Ping T est .......................................................................................................................................................... 317
4.13.4 IPv6 Ping Test .................................................................................................................................................. 318
4.13.5 Trace Router .................................................................................................................................................... 319
4.14 RMON .................................................................................................................................................... 320
4.14.1 RMON Statistics ............................................................................................................................................... 320
4.14.2 RMON Event .................................................................................................................................................... 322
4.14.3 RMON Event Log ............................................................................................................................................. 323
4.14.4 RMON Alarm .................................................................................................................................................... 324
4.14.5 RMON History .................................................................................................................................................. 327
4.14.6 RMON History Log ........................................................................................................................................... 328
4.15 Power over Ethernet ............................................................................................................................ 329
4.15.1 Long Reach Power over Ethernet Powered Device ......................................................................................... 330
4.15.2 System Configuration ....................................................................................................................................... 331
4.15.3 Power over Ethernet Configuration .................................................................................................................. 331
8
4.15.4 PoE Schedule .................................................................................................................................................. 334
4.15.5 PoE Alive Check Configuration ........................................................................................................................ 337
4.16 Maintenance ......................................................................................................................................... 339
4.16.1 Factory Default ................................................................................................................................................. 339
4.16.2 Reboot Switch .................................................................................................................................................. 339
4.16.3 Backup Manager .............................................................................................................................................. 340
4.16.4 Upgrade Manager ............................................................................................................................................ 341
4.16.5 Dual Image ....................................................................................................................................................... 342
5. SWITCH OPERATION ......................................................................................................... 343
5.1 Address Table ......................................................................................................................................... 343
5.2 Learning .................................................................................................................................................. 343
5.3 Forwarding & Filtering ........................................................................................................................... 343
5.4 Store-and-Forward ................................................................................................................................. 343
5.5 Auto-Negotiation .................................................................................................................................... 345
6. TROUBLESHOOTING ......................................................................................................... 346
APPENDIX A ............................................................................................................................ 348
A.1 Switch's RJ45 Pin Assignments ........................................................................................................... 348
A.2 10/100Mbps, 10/100BASE-TX ................................................................................................................ 348
9

1. INTRODUCTION

Thank you for purchasing IFS POC2502 Managed Switch, which comes with multiple POC female BNC connectors, Gigabit Ethent copper and SFP fiber optic connectibility and robust layer 2 and layer 4 features. The description of this model is shown below:
POC2502-8CXP-2T-2S
8-port Coax + 2-port 10/100/1000T + 2-port 100/1000X SFP PoE over Coaxial Managed Switch
POC2502-16CXP-2T-2S
“POC Managed Switch” is used as an alternative name in this user’s manual.
16-port Coax + 2-port 10/100/1000T + 2-port 100/1000X SFP PoE over Coaxial Managed Switch

1.1 Packet Contents

Open the box of the POC Managed Switch and carefully unpack it. The box should contain the following items:
The Power Over Coax Managed Switch x 1
Quick Installation Guide x 1
Rubber Feet x 4
Power Cord x 1
RS232 to RJ45 Console Cable x 1
SFP Dust Cap x 2
BNC Female Dust Cap x 8 (POC2502-8CXP-2T-2S)
BNC Female Dust Cap x 16 (POC2502-16CXP-2T-2S)
Warning Sticker x 8 (POC2502-8CXP-2T-2S)
Warning Sticker x 16 (POC2502-16CXP-2T-2S)
Rack-mount Accessory Kit x 1
If any item is found missing or damaged, please contact your local reseller for replacement.
10

1.2 Product Description

Power Over Coax Solution enables all enterprises and network service providers to set up an IP inf rastructure in a remote
location where 802.3af/at PoE compliant powered devices can receive both data and power via IFS switches, and IFS POC2502 extenders and injectors over a long distance but not limited to the normal 100 meters.
Intelligent POC Switch on Coaxial-based Network
IFS POC2502 Managed Switch, a brand-new Multi-channel Power Over Coax Switch, features an extended Ethernet and PoE networking of up to 1,000 meters over the existing coaxial cables going to multiple PoE IP cameras. It provides IPv6 / IPv4 dual stack management and built-in L2/L4 Gigabit Switching engine along with multi-BNC ports with Long Reach PoE Injector function, 2 Gigabit copper ports and 2 extra 100/1000BASE-X SFP fiber slots. As an advanced PoE switch, the IFS POC2502 Managed Switch features intelligent PoE functions to improve the availability of critical applications. It provides a quick, safe and cost-effective PoE network solution to upgrading the existing coaxial cable infrastructure from the analog system to the HD IP surveillance system.
Multi-channel Long Reach Power over Ethernet
To support the enterprises in easily building a multi-channel and centrally-controlled Long Reach PoE system, the POC2502 works with the Long Reach PoE Extenders, POC252-1CX-1P, via its BNC ports being the Long Reach PoE injectors for all connected POC Extenders. Each of the BNC port features long range data and power transmission for distance up to 1,000m (3,280ft) over coaxial cable to the POC Extender, and another 100m over Ethernet cable to remote PoE IP camera, PoE wireless AP or access control systems complied with 802.3af/at PoE.
Typical POC to IP Camera Configuration
11
Centralized Power Managemen t
IFS POC2502 Managed Switch eliminates the need for an additional remote site power while allowing a single power source to provide power to both POC extenders and the PoE powered devices at long range. The Long Reach PoE capabilities provided help to reduce installation time and deployment costs for network devices as a result of freeing from restrictions of power outlet locations.
Daisy-chaining Multiple Nodes
IFS Long Reach PoE solution can easily build a power system for centrally-controlled IP cameras in a high availability network infrastructure. It gives users the flexibility to expand small area network with BNC T-connector for sharing four nodes per port when needed.
Built-in Unique PoE Functions for Powered Devices Management
As a managed PoE switch for surveillance, wireless and VoIP networks, the IFS POC2502 Managed Switch particularly features the following special PoE Management functions to accomplish a highly-efficient Long Reach network:
PD Alive Check Scheduled Power Recycling PoE Schedule PoE Usage Monitoring
Intelligent Powered Device Alive Check
The IFS POC2502 Managed Switch can be configured to monitor connected PD (Powered Device) status in real time via ping action. Once the PD stops working and responding, the IFS POC2502 Managed Switch will resume the PoE port power and bring the PD back to work. It will greatly enhance the network reliability through the PoE port resetting the PD’s power source and reducing administrator management burden.
12
Scheduled Power Recycling
The IFS POC2502 Managed Switch allows each of the connected PoE IP cameras or PoE wireless access points via the POC252-1CX-1P to reboot at a specific time each week. Therefore, it will reduce the chance of IP camera or wireless AP crash resulting from buffer overflow.
PoE Schedule for Energy Saving
Under the trend of energy saving worldwide and contributing to environmental protection, the IFS POC2502 Managed Switch can effectively control the power supply besides its capability of giving high watts power. The “PoE schedule” function helps you to enable or disable PoE power feeding for each PoE port during specified time intervals and it is a powerful function to help SMBs or enterprises save power and money. It also increases security by powering off PDs that should not be in use during non-business hours.
PoE Usage Monitoring
Via the power usage chart in the web management interface, the IFS POC2502 Managed Switch enables the administrator to monitor the status of the power usage of the connected PDs in real time. Thus, it greatly enhances the management efficiency of the facilities.
PoE Over-temperature Protection System
The over-temperature protection of the IFS POC2502 Managed Switch offers a safe and stable PoE operation by limiting the output power in order to avoid destructive breakdown due to unexpected overheating.
13
Environment-friendly, Smart Fan Design for Silent Operation
The IFS POC2502 Managed Switch features a 19-inch metal housing, a low noise design and an effective ventilation system. It supports the smart fan technology to automatically control the speed of the built-in fan to reduce noise and maintain the temperature of the PoE switch for optimal power output capability. The IFS POC2502 Managed Switch is able to operate reliably, stably and quietly in any environment without affecting its performance.
IPv6 / IPv4 Dual Stack
Supporting both IPv6 and IPv4 protocols, the IFS POC2502 Managed Switch the SMBs to step in the IPv6 era with the lowest investment as its network facilities need not be replaced or overhauled if the IPv6 FTTx edge network is set up.
Robust Layer 2 Features
The IFS POC2502 Managed Switch can be programmed for advanced switch management functions such as dynamic port link aggregation, 802.1Q VLAN and Q-in-Q VLAN, Multiple Spanning Tree Protocol (MSTP), Loop and BPDU Guard, IGMP Snooping, and MLD Snooping. Via the link aggregation, the IFS POC2502 Managed Switch allows the operation of a high-speed trunk to combine with multiple ports such as an 8Gbps fat pipe, a nd supports fail-over as well. Also, the Link Layer Discovery Protocol (LLDP) is the Layer 2 Protocol included to help discover basic information about neighboring devices on the local broadcast domain.
Efficient Traffic Control
The IFS POC2502 Managed Switch is loaded with robust QoS features and powerful traffic management to enhance services to business-class data, voice, and video solutions. The functionality includes broadcast / multicast storm control, per port bandwidth control, IP DSCP QoS priority and remarking. It guarantees the best performance for VoIP and video stream transmission, and empowers the enterprises to take full advantage of the limited network resources.
Powerful Security
IFS IFS POC2502 Mana ged Switch offer s comprehensive IPv4 / IPv6 L ayer 2 to Layer 4 Access Control List (ACL) for enforcing security to the edge. It can be used to restrict network access by denying packets based on source and destination IP address, TCP/UDP ports or defined typical network applications. Its protection mechanism also comprises 802.1X port-based user and device authentication, which can be deployed with RADIUS to ensure the port level security and block illegal users. With the Protected Port function, communication between edge ports can be prevented to guarantee user privacy. Furthermore, Port Security function allows limiting the number of network devices on a given port.
14
Advanced Network Security
The IFS POC2502 Managed Switch also provides DHCP Snooping, IP Source Guard and Dynamic ARP Inspection functions to prevent IP snooping from attack and discard ARP packets with invalid MAC address. The network administrators can now build highly-secured corporate networks with considerably less time and effort than before.
Friendly and Secure Management
For efficient management, the IFS POC2502 Managed Switch is equipped with console, Web, Telnet and SNMP management interfaces. With the built-in Web-based management interface, the IFS POC2502 Managed Switch offers an easy-to-use, platform-independent management and configuration facility. By supporting the standard Simple Network Management Protocol (SNMP), the switch can be managed via any standard management software. For text-based management, the switch can be accessed via T elnet and the console port. Moreover, the IFS POC2502 Managed Switch offers secure remote management by supporting SSH, SSL and SNMP v3 connections which encrypt the packet content at each session.
Flexibility and Long-distance Extension Solution
The IFS POC2502 Managed Switch provides two Gigabit TP interfaces supporting 10/100/1000BASE-T RJ45 copper to be connected with surveillance network devices such as NVR, Video Streaming Server or NAS to facilitate surveillance management. Or through another two dual-speed fiber SFP slots, it can connect with the 100BASE-FX / 1000BASE-SX/LX SFP (Small Form-factor Pluggable) fiber transceiver to uplink to backbone switch and monitoring center in long distance. The distance can be extended from 550 meters to 2 kilometers (multi-mode fiber) and up to 10/20/30/40/50/70/120 kilometers (single-mode fiber or WDM fiber). The IFS POC2502 Managed Switch is well suited for applications within the enterprise data centers and distributions.
Intelligent SFP Diagnosis Mechanism
The IFS POC2502 Managed Switch also supports SFP-DDM (Digital Diagnostic Monitor) function that can easily monitor real-time parameters of the SFP for network administrator, such as optical output power, optical input power, temperature, laser bias current and transceiver supply voltage.
15

1.3 How to Use This Manual

This User Manual is structured as follows:
Section 2, INSTALLATION
The section explains the functions of the Switch and how to physically install the POC Managed Switch.
Section 3, SWITCH MANAGEMENT
The section contains the information about the software function of the POC Managed Switch.
Section 4, WEB CONFIGURATION
The section explains how to manage the POC Managed Switch by Web interface.
Section 5, SWITCH OPERATION
The chapter explains how to do the switch operation of the POC Managed Switch.
Section 6, TROUBLESHOOTING
The chapter explains how to troubleshoot of the POC Managed Switch.
Appendix A
The section contains cable information of the POC Managed Switch.

1.4 Product Features

Physical Port
■ 100Mbps BNC female ports with Long Reach PoE Injector function
■ 2 10/100/1000BASE-T Gigabit RJ45 copper ports
■ 2 100/1000BASE-X mini-GBIC/SFP slots
■ RJ45 console interface for switch basic management and setup
Long Reach Power over Ethernet
■ Supports PoE power up to 36 watts for each PoE port
■ Remote power feeding up to 1 kilometer with low impedance 75Ω coaxial cable
■ Long Reach PoE Management
− Total Long Reach PoE power budget control
− Per port Long Reach PoE function enable/disable
− Long Reach PoE port power feeding priority
− Per Long Reach PoE port power limitation
− Long Reach PD alive check
− Long Reach PoE schedule
16
Layer 2 Features
■ Prevents packet loss with back pressure (half-duplex) and IEEE 802.3x pause frame flow control (full-duplex)
■ High performance Store and Forward architecture, broadcast storm control, runt/CRC filtering that eliminates
erroneous packets to optimize the network bandwidth
■ Supports VLAN
- IEEE 802.1Q tagged VLAN
- Provider Bridging (VLAN Q-in-Q) support (IEEE 802.1ad)
- Protocol VLAN
- Voice VLAN
- Private VLAN
- Management VLAN
- GVRP
■ Supports Spanning Tree Protocol
- STP (Spanning Tree Protocol)
- RSTP (Rapid Spanning T ree Protocol)
- MSTP (Multiple Spanning Tree Protocol)
- STP BPDU Guard, BPDU Filtering and BPDU Forwarding
■ Supports Link Aggregation
− IEEE 802.3ad Link Aggregation Control Protocol (LACP)
− Cisco ether-channel (static trunk)
− Maximum 4 trunk groups, up to 4 ports per trunk group
■ Provides port mirror (many-to-1)
■ Loop protection to avoid broadcast loops
Quality of Service
■ Ingress / Egress rate limit per port bandwidth control
■ Storm control support
− Broadcast / Unknown unicast / Unknown multicast
■ Traffic classification
- IEEE 802.1p CoS
- ToS / DSCP / IP Precedence of IPv4/IPv6 packets
■ Strict priority and Weighted Round Robin (WRR) CoS policies
Multicast
■ Supports IGMP snooping v2 and v3
■ Supports MLD snooping v1, v2
■ IGMP querier mode support
■ IGMP snooping port filtering
■ MLD snooping port filtering
17
Security
■ Authentication
− IEEE 802.1x port-based network access authentication
− Built-in RADIUS client to co-operate with the RADIUS servers
− RADIUS / TACACS+ login user access authentication
■ Access Control List
− IPv4 / IPv6 IP-based ACL
− MAC-based ACL
■ MAC Security
− Static MAC
− MAC filtering
■ Port security for source MAC address entries filtering
■ DHCP snooping to filter untrusted DHCP messages
■ Dynamic ARP inspection discards ARP packets with invalid MAC address to IP address binding
■ IP source guard prevents IP spoofing attacks
■ DoS attack prevention
■ SSH / SSL
Management
■ IPv4 and IPv6 dual stack management
■ Switch management interface
- Web switch management
- Telnet command line interface
- SNMP v1, v2c and v3
- SSH / SSL secure access
■ User privilege levels control
■ Built-in Trivial File Transfer Protocol (TFTP) client
■ BOOTP and DHCP for IP address assignment
■ System maintenance
- Firmware upload/download via HTTP / TFTP
- Configuration upload/download through Web interface
- Dual images
- Hardware reset button for system reboot or reset to factory default
■ SNTP Network Time Protocol
■ Cable diagnostics
■ Link Layer Discovery Protocol (LLDP) and LLDP-MED
■ SNMP trap for interface linkup and linkdown notification
■ Event message logging to remote Syslog server
■ Four RMON groups (history, statistics, alarms and events)
■ IFS Smart Discovery utility
■ Smart fan with speed control
18
Model
POC2502-8CXP-2T-2S
POC2502-16CXP-2T-2S
Hardware Specifications
Supports 100/1000Mbps dual mode and DDM
BNC shield : DC - / Lo
Total POE Budget
Max. 1200m with data output only (3,937ft.)
Ethernet Standard
Security

1.5 Product Specifications

Ethernet Interfaces
Long Reach PoE Interfaces
Copper
Fiber Optic
Jumbo Frame
Connectivity
Power Output
Cabling
Maximum Distance
Long Reach
2 x 10/100/1000BASE-T RJ45 Auto-negotiation/ Auto-MDI/MDI-X
2 x 100/1000BASE-X SFP slot
10Kbytes with GE1 to GE4 POC2502-8CXP-2T-2S: 8 x BNC female connectors
POC2502-16CXP-2T-2S:16 x BNC female connectors
Long Reach PoE over coaxial PSE (Power Source Equipment)
BNC center pole : DC+ / Hi
Per port 54V DC, 36 watts max. Per port 52V DC, 36 watts max. 240 watts (max.) 380 watts (max.) Coaxial cable: 75 ohm Low Impedance RG-6/U cable (Recommended) Max. 200m with PoE+ output (1,640ft.)
Max. 400m with PoE output (2,624ft.) Max. 1000m with PoE output (3,280ft.)
IEEE 1901
Modulation Type Wavelet-OFDM
128-bit AES encryption
Frequency Band 2 ~ 28MHz
19
Type
Data Rate*
PoE Output*
TX**
RX**
Type
Data Rate*
PoE Output*
TX**
RX**
Up to 3 POC extenders within 1km RG-6/U coaxial cable*
environmental factors.
Extender
Console
1 x RS232-to-RJ45 serial port (115200, 8, N, 1)
Switch Architecture
Switch Fabric
9.6Gbps / non-blocking
11.2Gbps / non-blocking
Address Tabl e
8K entries
Shared Data Buffer
4.1 megabits
> 5 sec: Factory default
[POC2502-8CXP-2T-2S]
Cable
Distance
POC252-1CX-1P
RG6
200m
400m RG6 600m RG6 800m RG6 1000m RG6
[POC2502-16CXP-2T-2S]
Distance
Performance
200m
400m RG6 600m RG6 800m RG6 1000m RG6
* The actual data rate and PoE output vary on the quality of the copper wire and environmental factors. The performance result above is based on the testing via the RG-6/U coaxial cable.
** TX: POC2502-8CXP-2T-2S to POC252-1CX-1P; RX: POC252-1CX-1P to POC2502-8CXP-2T-2S.
RG59
Cable
RG6
RG59
91.8Mbps 81.1Mbps
92.4Mbps 85.6Mbps
85.5Mbps 66.9Mbps 18.4W
76.5Mbps 54.2Mbps 13.6W
67.9Mbps 49.2Mbps 10.47W
26.6Mbps 25.6Mbps 8.45W
87.1Mbps 77.6Mbps
89.3Mbps 82.5Mbps
82.5Mbps 63.7Mbps 15.4W
72.8Mbps 51.1Mbps 10.6W
63.4Mbps 45.2Mbps 7.47W
20.2Mbps 19.8Mbps 5.45W
22.9W
16.33W
POC252-1CX-1P
19.9W
13.33W
Multiple Nodes
POC Compatibility
Flow Control
Reset Button
LED
20
* The actual extender nodes vary on the quality of the copper wire and
POC252-1CX-1P: 1-Port 10/100TX PoE PSE + 1-Port Coax Long Reach PoE
Store-and-Forward
IEEE 802.3x pause frame for full-duplex Back pressure for half-duplex
< 5 sec: System reboot
PWR, SYS, LNK, PoE-in-Use, 1000, LNK/ACK, Fan 1 Alert, Fan 2 Alert,
PoE PWR Alert
Dimensions (W x D x H)
440 x 300 x 44.5 mm, 1U height
Weight
Power Requirements
AC 100~240V, 50/60Hz, auto-sensing
ESD Protection
6KV DC
Power Consumption
270 watts / 926 BTU
495 watts / 1698 BTU
Enclosure
Layer 2 Functions
Many-to-1 monitor
GVRP
Spanning Tree Protocol
STP / RSTP / MSTP
Up to 256 multicast groups
Traffic classification based, strict priority and WRR
IP source guard
Management Functions
4282g 4430g
Metal
Port Mirroring
VLAN
Link Aggregation
IGMP Snooping
MLD Snooping Access Control List
QoS
TX / RX / both
802.1Q tagged-based VLAN Up to 256 VLAN groups, out of 4094 VLAN IDs
802.1ad Q-in-Q tunneling Voice VLAN
Protocol VLAN Private VLAN (Protected port)
IEEE 802.3ad LACP and static trunk Supports 4 groups of 4-port trunk
IGMP (v2/v3) Snooping IGMP Querier
MLD (v1/v2) Snooping, up to 256 multicast groups IPv4/IPv6 IP-based ACL / MAC-based ACL 8 mapping ID to 8 level priority queues
- Port number
- 802.1p priority
- 802.1Q VLAN tag
- DSCP field in IP packet
Security
21
IEEE 802.1X– Port-based authentication Built-in RADIUS client to co-operate with RADIUS server RADIUS / TACACS+ user access authentication IP-MAC port binding MAC filter Static MAC address DHCP Snooping and DHCP Option 82 STP BPDU guard, BPDU filtering and BPDU forwarding DoS attack prevention ARP inspection
SNTP
RFC 3635 Ethernet-like MIB
Standards Conformance
RFC 3810 MLD version 2
Environment
Temperature: -10 ~ 70 degrees C Relative Humidity: 5 ~ 95% (non-condensing)
Basic Management Interfaces
Web browser / Telnet / SNMP v1, v2c Firmware upgrade by HTTP / TFTP protocol through Ethernet network Remote / Local Syslog System log LLDP protocol
Secure Management Interfaces
SNMP MIBs
Regulation Compliance
Standards Compliance
SSH, SSL, SNMP v3 RFC 1213 MIB-II
RFC 1215 Generic Traps RFC 1493 Bridge MIB RFC 2674 Bridge MIB Extensions RFC 2737 Entity MIB (Version 2) RFC 2819 RMON (1, 2, 3, 9) RFC 2863 Interface Group MIB
FCC Part 15 Class A, CE IEEE 1901 Broadband Power Line
IEEE 802.3 10BASE-T IEEE 802.3u 100BASE-TX/100BASE-FX IEEE 802.3z Gigabit SX/LX IEEE 802.3ab Gigabit 1000T IEEE 802.3x flow control and back pressure IEEE 802.3ad port trunk with LACP IEEE 802.1D Spanning Tree Protocol IEEE 802.1w Rapid Spanning Tree Protocol IEEE 802.1s Multiple Spanning Tree Protocol IEEE 802.1p Class of Service IEEE 802.1Q VLAN tagging IEEE 802.1X Port Authentication Network Control IEEE 802.1ab LLDP RFC 768 UDP RFC 793 TFTP RFC 791 IP RFC 792 ICMP RFC 2068 HTTP RFC 1112 IGMP version 1 RFC 2236 IGMP version 2 RFC 3376 IGMP version 3 RFC 2710 MLD version 1
Operating
Storage
22
Temperature: 0 ~ 50 degrees C Relative Humidity: 5 ~ 95% (non-condensing)
Additional PoE output vs cable type information:
RG-59 Bare Copper Coaxial Cable
Item
No.
1 100 30 27.7 27.0 2 200 61 27.7 27.0 3 300 91 27.0 26.0 4 400 122 25.9 25.2 5 500 152 25.8 25.0 6 600 183 25.2 24.2 7 700 213 24.4 23.5 8 800 244 24.0 23.0
9 900 274 23.6 22.3 10 1000 305 22.9 21.8 11 1100 335 22.3 21.2 12 1200 366 21.8 20.6 13 1300 396 21.2 20.0 14 1400 427 20.7 19.8
Coaxial Cable Length POC252-1CX Maximum PoE Output (W)
Feet Meters POC2502-8CXP POC2502-16CXP
15 1500 457 19.7 18.9 16 1600 488 19.3 18.5 17 1700 518 18.9 18.1 18 1800* 549* 18.2 18.0 19 1900* 579* 17.5 17.0 20 2000* 610* 17.0 16.1 21 2100* 640* 16.6 22 2200* 671* 15.7 23 2300* 701* 14.8 24 2400* 732* 14.4 25 2500* 762* 13.9 26 2600* 792* 13.8 27 2700* 823* 13.0 28 2800* 853* 12.6 29 2900* 884* 12.1 30 3000* 914* 11.7
15.3
14.7
14.2
13.8
13.5
13.0
12.3
12.0
11.5
11.0
31 3100* 945* 11.4 32 3200* 975* 10.7 33 3300* 1006* 10.3
Above PoE outputs are based on RG-59 Bare Copper, 10Ω/1000FT DC Resistance coaxial cable at 25°C operation.
23
10.7
10.3
10.0
RG-59 Copper-Clad Steel Coaxial Cable
Item
No.
Coaxial Cable Length POC252-1CX Maximum PoE Output (W)
Feet Meters POC2502-8CXP POC2502-16CXP
1 100 30 26.1 24.4
2 200 61 25.4 24.0
3 300 91 22.4 21.4
4 400 122 19.8 19.1
5 500* 152* 14.3 13.6
6 600* 183* 12.8 12.1
7 700* 213* 10.6 10.5
8 800* 244* 9.5 10.1
9 900* 274* 9.3 8.7 10 1000* 305* 7.9 7.4 11 1100* 335* 7.1 6.7 12 1200* 366* 6.4 5.8 13 1300* 396* 5.5 5.3 14 1400* 427* 5.4 5.1 15 1500* 457* 4.9 4.6
Above PoE outputs are based on RG-59 CCS, 46Ω/1000FT DC Resistance coaxial cables at 25°C operation.
The PoE output may reduce 1W at high temp operating.
*The long coaxial cable may not support 720P/1080P camera because long coaxial cable has high DC Resistance which reduces data rate/bandwidth.
24

2. INSTALLATION

This section describes the hardware features and installation of the POC Managed Switch on the desktop or rack mount. For easier management and control of the POC Managed Switch, familiarize yourself with its display indicators, and ports. Front panel illustrations in this chapter display the unit LED indicators. Before connecting any network device to the POC Managed Switch, please read this chapter completely.

2.1 Hardware Description

2.1.1 Switch Front Panel

The front panel provides a simple interface monitoring of the POC Managed Switch. Figure 2-1-1A ~ 2-1-1B shows the front panel of the POC Managed Switch.
Front Panel
Figure 2-1-1A POC2502-8CXP-2T-2S Front Panel
Front Panel
Figure 2-1-1B POC2502-16CXP-2T-2S Front Panel
■ Long Reach PoE BNC Interface
BNC female port, RG59U/RG6 75Ω coaxial cable: Up to 1 kilometer. (Distance is based on cable impedance)
■ Gigabit TP Interface
10/100/1000BASE-T Copper, RJ45 Twist-Pair: Up to 100 meters.
■ 100/1000BASE-X SFP Slots
Each of the SFP (Small Form-factor Pluggable) slots supports dual-speed, 1000BASE-SX / LX or 100BASE-FX
- For 1000BASE-SX/LX SFP transceiver module: From 550 meters (multi-mode fiber) to 10/30/50/70/120 kilometers (single-mode fiber).
- For 100BASE-FX SFP transceiver module: From 2 kilometers (multi-mode fiber) to 20/40/60 kilometers (single-mode fiber).
25
Reset Button Pressed and Released
Function
reboot and
Default Gateway: 192.168.0.254
Note
: Power at BNC ports are off by default. To enable POC powe r at each BNC connector, please consult the manual.
For connection to P OC Ex tenders only. NOT for direct camer a connections.
■ Console Port
The console port is a RJ45 port connector. It is an interface for connecting a terminal directly. Through the console port, it provides rich diagnostic information including IP Address setting, factory reset, port management, link status and system setting. Users can use the attached DB9 to RJ45 console cable in the package and connect to the console port on the device. After the connection, users can run any terminal emulation program (Hyper Terminal, ProComm Plus, T elix, Winterm and so on) to enter the startup screen of the device.
■ Reset Button
On the left of the front pa nel, the reset button is designed to reboot the POC Managed Switch without turning off and on the power. The following is the summary table of the Reset button functions:
< 5 sec: System Reboot Reboot the POC Managed Switch.
Reset the POC Managed Switch to the Factory Default configuration. The POC Managed Switch will then load the default settings shown below:
> 5 sec: Factory Default
。 Default Username: admin 。 Default Password: admin 。 Default IP Address: 192.168.0.100 。 Subnet Mask: 255.255.255.0
。

2.1.2 LED Indications

The front panel LEDs indicates instant status of port links, data activity and system power; it helps monitor and troubleshoot when needed. Figure 2-1-2A ~ 2-1-2B shows the LED indications of these POC Managed Switches.
POC2502-8CXP-2T-2S LED Indication
Figure 2-1-2 POC2502-8CXP-2T-2S LED Panel
26
■ System / Alert
LED Color Function
PWR Green
SYS Green
FAN 1 Red FAN 2 Red FAN 3 Red
PWR Red
■ Long Reach PoE Interfaces (Port-1 to Port-8)
LED Color Function
LNK Green Lights: PoE Orange Lights:
■ 10/100/1000BASE-T interfaces (GE1 to GE2)
LED Color Function
Lights to indicate that the Switch has power. Lights to indicate the system is working.
Off to indicate the system is booting. Lights to indicate that Fan 1 is down. Lights to indicate that Fan 2 is down. Lights to indicate that Fan 3 is down. Lights to indicate that the PoE Power is down.
To indicate the link through that port is successfully established. To indicate the port is providing 56VDC in-line power.
LNK/ACT Green
1000 Orange
■ 1000BASE-SX/LX SFP interfaces (GE3 to GE4)
LED Color Function
LNK/ACT Green
1000 Orange
Lights: Blink: Lights: To indicate that the port is operating at 1000Mbps. Lights: When LNK/ACT LED lights up, it indicates that the port is operating at 10/100Mbps. Off:
Lights: Blink: Lights: indicate that the port is operating at 1000Mbps. Lights: When LNK/ACT LED lights up, it indicates that the port is operating at 10/100Mbps. Off:
To indicate the link through that port is successfully established. To indicate that the switch is actively sending or receiving data over that port.
When LNK/ACT LED is Off, it indicates that the port is linkdown.
To indicate the link through that port is successfully established. To indicate that the switch is actively sending or receiving data over that port.
When LNK/ACT LED is Off, it indicates that the port is linkdown.
27
POC2502-16CXP-2T-2S LED Indication
Figure 2-1-2B POC2502-16CXP-2T-2S LED Panel

2.1.3 Switch Rear Panel

The rear panel of the POC Managed Switch indicates an AC inlet power socket, which accepts input power from 100 to 240V AC, 50-60Hz. Figure 2-1-3 shows the rear panel of these POC Managed Switches
Rear Panel
Figure 2-1-3 Rear Panel of POC2502-8CXP-2T-2S / POC2502-16CXP-2T-2S
■ AC Power Receptacle
For compatibility with electric service in most areas of the world, the POC Managed Switch’s power supply automatically adjusts to line power in the range of 100-240V AC and 50/60 Hz.
Plug the female end of the power cord firmly into the receptalbe on the rear panel of the POC Managed Switch. Plug the other end of the power cord into an electrical outlet and the power will be ready.
The device is a power-required device, which means it will not work till it is powered. If your networks
Power Notice:
should be active all the time, please consider using UPS (Uninterrupted Power Supply) for your device. It will prevent you from network data loss or network downtime.
In some areas, installing a surge suppression device may also help to protect your POC Managed
Power Notice:
Switch from being damaged by unregulated surge or current to the POC Managed Switch.
28
Chapter 1,
requires UTP Category 5 network cabling with RJ45 tips. For

2.2 Installing the Switch

This section describes how to install your POC Managed Switch and make connections to the POC Managed Switch. Please read the following topics and perform the procedures in the order being presented. To install your POC Managed Switch on a desktop or shelf, simply complete the following steps.

2.2.1 Desktop Inst al lation

To install the POC Managed Switch on desktop or shelf, please follow these steps:
Step 1: Attach the rubber feet to the recessed areas on the bottom of the POC Managed Switch. Step 2: Place the POC Managed Switch on the desktop or the shelf near an AC power source, as shown in Figure 2-1-4.
Figure 2-1-4 Place the POC Managed Switch on the desktop
Step 3: Keep enough ventilation space between the POC Managed Switch and the surrounding objects.
When choosing a location, please keep in mind the environmental restrictions discussed in Section 4 under specifications.
Step 4: Connect the POC Managed Switch to network devices.
Connect one end of a standard network cable to the 10/100/1000 RJ45 ports and standard coaxial cable to POC ports on the front of the POC Managed Switch. Connect the other end of the cable to the network devices such as printer server, workstation or router.
Connection to the POC Managed Switch more information, please see the Cabling Specification in Appendix A.
29
the screws supplied with the mounting brackets. Damage caused to the parts by
Step 5: Supply power to the POC Managed Switch.
Connect one end of the power cable to the POC Managed Switch. Connect the power plug of the power cable to a standard wall outlet. When the POC Managed Switch receives power, the Power LED should remain solid Green.

2.2.2 Rack Mounting

To install the POC Managed Switch in a 19-inch standard rack, please follow the instructions described below.
Step 1: Place the POC Managed Switch on a hard flat surface, with the front panel positioned towards the front side. Step 2: Attach the rack-mount bracket to each side of the POC Managed Switch with supplied screws attached to the package.
Figure 2-1-5 shows how to attach brackets to one side of the POC Managed Switch.
Figure 2-1-5 Attach Brackets to the POC Managed Switch.
You must use using incorrect screws would invalidate the warranty.
Step 3: Secure the brackets tightly.
Step 4: Follow the same steps to attach the second bracket to the opposite side.
Step 5: After the brackets are attached to the POC Managed Switch, use suitable screws to securely attach the brackets to the
rack, as shown in Figure 2-1-6.
Figure 2-1-6 Mounting POC Managed Switch in a Rack
30
Step 6: Proceeds with Steps 4 and 5 of session 2.2.1 Desktop Installation to connect the network cabling and supply power to
the POC Managed Switch.

2.2.3 Install i ng the SF P transceiver

The sections describe how to insert an SFP transceiver into an SFP slot. The SFP transceivers are hot-pluggable and hot-swappable. You can plug in and out the transceiver to/from any SFP port without having to power down the POC Managed Switch, as the Figure 2-1-7 shows.
Figure 2-1-7 Plug in the SFP transceiver
Approved IFS SFP Transceivers
IFS POC2502 Managed Switch supports both single mode and multi-mode SFP transceiver. The following list of approved IFS SFP transceivers is correct at the time of publication:
SFP Transceiver Modules
Fast Ethernet Transceiver (100Base-X SFP)
31
transceiver
,
Gigabit Ethernet Transceiver (1000BASX-LX-BX, Fiber Bi-Directional SFP)
It is recommended to use IFS SFP on the POC Managed Switch. If you insert an SFP that is not supported, the POC Managed Switch will not recognize it.
In the installation steps below, this Manual uses Gigabit SFP transceiver as an example. However the steps for Fast Ethernet SFP transceiver are similar.
1. Before we connect POC Managed Switch to the other network device, we have to make sure both sides of the SFP
transceivers are with the same media type, for example, 1000BASE-SX to 1000BASE-SX, 1000BASE-LX to 1000BASE-LX.
2. Check whether the fiber-optic cable type matches with the SFP transceiver requirement.
To connect to 1000BASE-SX SFP transceiver, please use the multi-mode fiber cable with one side being the male
duplex LC connector type.
To connect to 1000BASE-LX SFP transceiver, please use the single-mode fiber cable with one side being the male
duplex LC connector type.
32
Managed
Connect the Fiber Cable
1. Insert the duplex LC connector into the SFP transceiver.
2. Connect the other end of the cable to a device with SFP transceiver installed.
3. Check the LNK/ACT LED of the SFP slot on the front of the POC Managed Switch. Ensure that the SFP transceiver is
operating correctly.
4. Check the Link mode of the SFP port if the link fails. To function with some fiber-NICs or media converters, user has to set
the port Link mode to “1000 Force” or “100 Force”.
Remove the Transceiver Module
1. Make sure there is no network activity anymore.
2. Remove the fiber-optic cable gently.
3. Lift up the lever of the MGB module and turn it to a horizontal position.
4. Pull out the module gently through the lever.
Figure 2-1-8 How to Pull Out the SFP Transceiver Never pull out the module without lifting up the lever of the module and turning it into a horizontal position. Directly pulling out the module could damage the module and the SFP module slot of the POC Managed Switch.

2.2.4 Installing the Long Reach PoE Communication

The sections describe how to insert a coaxial cable into a BNC female port. Y ou can plug in and out the coaxial cable to/from any BNC female port port without having to power down the POC Managed Switch.
Approved IFS Long Reach PoE Extenders
The following list of approved IFS Long Reach PoE extenders is correct at the time of publication:
Long Reach Ethernet Coaxial Extenders
POC252-1CX-1P
It is recommended to use IFS Long Reach Ethernet coaxial extenders on the POC
1-Port 10/100TX PoE PSE + 1-Port Coax Long Reach PoE Extender
Switch. If you insert a coaxial extender that is not supported, the POC Managed Switch may damage it.
33
lease
Coaxial Cable Type
RG-6/U
Less than 12Ω/1000 ft
1. Before we connect POC Managed Switch to the other network device, we have to make sure both sides of the Long Reach Ethernet coaxial extender / transceiver are with the same media type.
2. Check whether the coaxial cable type matches with the Long Reach Ethernet coaxial extender / transceiver requirement. To connect to POC Managed Switch, please use the coaxial cable with 75Ω BNC plug with one side being the BNC
plug connector type.
To connect to Long Reach Ethernet coaxial extenders, please use the coaxial cable with one side being the 75Ω
BNC plug connector type.
Because there are various resistance values in the category of RG-59/U or RG-6/U cables, p take care of the conditions of the resistance value of cables as follows:
RG-59/U Less than 30Ω/1000 ft.
In the installation steps below, this Manual uses Long Reach Ethernet coaxial extender as an example.
Connect the Coaxial Cable
1. Insert the coaxial cable with one side being the 75Ω BNC plug connector into the Long Reach Ethernet coaxial interface.
2. Connect the other end of the cable to a device with Long Reach Ethernet coaxial extender installed.
3. Tighten the BNC male connector gently.
4. Enable Long Reach Power over Ethernet function for the all POC ports from WebUI
5. We suggest that all unused ports be turned off, as output voltage will be at the BNC connector output And should have BNC cap installed for safety.
34
Figure 2-1-8 How to insert the coaxial cable from POC Managed Switch
6. Check the LNK LED of the Long Reach Power over Ethernet interface on the front of the POC POC Managed Switch. Ensure that the Long Reach Power over Ethernet interface is operating correctly.
35
e
Note
: Power at BNC ports are off by default. To enable POC powe r at each BNC connector, please consult the manual.
For connection to P OC Ex tenders only. NOT for direct camer a connections.
Remove the connected the Coaxial Cable
1. Make sure there is no network activity anymore.
2. Disable Long Reach Power over Ethernet function for the all POC ports from WebUI.
3. Loosen the BNC male connector gently.
4. Pull out the coaxial cable gently.
Figure 2-1-8 How to pull out the coaxial cable from POC Managed Switch
Never pull out the coaxial cable without disabling Long Reach Power over Ethernet function for th port from WebUI. Directly pulling out the coaxial cable could damage the Long Reach Ethernet coaxial extender and the BNC female connector of the POC Managed Switch.
If you are uninstalling a port, we suggest that you turn that port off as voltage will be live at the output of the BNC connector and place BNC cap that shipped with unit back on to open BNC.
1. The package contains eight warning stickers, which should be stuck on the coaxial cable connector before using IFS POC2502 Managed Switch and POC extender. If connected with non-IFS POC2502 extender equipment, it might cause damage to the equipment.
2. After the POC PoE port is enabled, the pin center of the coaxial cable has electricity. Do not touch the pin center or connect this end to any non- IFS POC2502 equipment.
36
Note
: Power at BNC ports are off by default. To enable POC powe r at each BNC connector, please consult the manual.
For connection to P OC Ex tenders only. NOT for direct camer a connections.
To Dis able unused ports or all ports.
37
It is recom

3. SWITCH MANAGEMENT

This chapter explains the methods that you can use to configure management access to the POC Managed Switch. It describes the types of management applications and the communication and management protocols that deliver data between your management device (workstation or personal computer) and the system. It also contains information about port connection options.
This chapter covers the following topics:
Requirements  Management Access Overview  Administration Console Access  Web Management Access  SNMP Access  Standards, Protocols, and Related Reading

3.1 Requirements

Workstations running Windows 2000/XP, 2003, Vista/7/8, 2008, MAC OS9 or later, Linux, UNIX or other platforms
are compatible with TCP/IP protocols.
Workstation is installed with Ethernet NIC (Network Interface Card) Serial Port connect (Terminal)
• The above PC with COM Port (DB9 / RS232) or USB-to-RS232 converter
Ethernet Port connection
• Network cables -- Use standard network (UTP) cables with RJ45 connectors.
The above Workstation is installed with Web browser and JAVA runtime environment plug-in
mended to use Internet Explore 8.0 or above to access POC Managed Switch.
38

3.2 Management Access Overview

The POC Managed Switch gives you the flexibility to access and manage it using any or all of the following methods:
An administration console Web browser interface  An external SNMP-based network management application
The administration console and Web browser interface support are embedded in the POC Managed S witch software and are available for immediate use. Each of these management methods has their own advantages. Table 3-1 compares the three management methods.
Method Advantages Disadvantages
Console
Web Browser
SNMP Agent
• No IP address or subnet needed
• Text-based
• Telnet functionality and HyperTerminal
built into Windows 95/98/NT/2000/ME/XP operating systems
• Secure
• Ideal for configuring the switch remotely
• Compatible with all popular browsers
• Can be accessed from any location
• Most visually appealing
• Communicates with switch functions at
the MIB level
• Based on open standards
• Must be near the switch or use dial-up
connection
• Not convenient for remote users
• Modem connection may prove to be unreliable
or slow
• Security can be compromised (hackers need only know the IP address and subnet mask)
• May encounter lag times on poor connections
• Requires SNMP manager software
• Least visually appealing of all three methods
• Some settings require calculations
• Security can be compromised (hackers only
need to know the community name)
Table 3-1 Comparison of Management Methods
39

3.3 Administration Console

The administration console is an internal, character-oriented, and command line user interface for performing system administration such as displaying statistics or changing option settings. Using this method, you can view the administration console from a terminal, personal computer, Apple Macintosh, or workstation connected to the POC Managed Switch's console port.
Figure 3-1-1: Console Management
Direct Access
Direct access to the administration console is achieved by directly connecting a terminal or a PC equipped with a terminal-emulation program (such as HyperTerminal) to the POC Managed Switch console (serial) port. When using this management method, a straight RS232 to RJ45 cable is required to connect the switch to the PC. After making this connection, configure the terminal-emulation program to use the following parameters: The default parameters are:
115200 bps 8 data bits No parity 1 stop bit
Figure 3-1-2: Terminal Parameter Settings
You can change these settings, if desired, after you log on. This management method is often preferred because you can remain connected and monitor the system during system reboots. Also, certain error messages are sent to the serial port,
40
regardless of the interface through which the associated action was initiated. A Macintosh or PC attachment can use any terminal-emulation program for connecting to the terminal serial port. A workstation attachment under UNIX can use an emulator such as TIP.

3.4 Web Management

The POC Managed Switch offers management features that allow users to manage the POC Managed Switch from anywhere on the network through a standard browser such as Microsoft Internet Explorer. After you set up your IP address for the switch, you can access the POC Managed Switch's Web interface applications directly in your Web browser by entering the IP address of the POC Managed Switch.
Figure 3-1-3 Web Management
You can then use your Web browser to list and manage the POC Managed Switch configuration parameters from one central location, just as if you were directly connected to the POC Managed Switch's console port. Web Management requires either
Microsoft Internet Explorer 8.0 or later, Google Chrome, Safari or Mozilla Firefox 1.5 or later.
Figure 3-1-4 Web Main Screen of POC Managed Switch
41

3.5 SNMP-based Network Management

You can use an external SNMP-based application to configure and manage the POC Managed Switch, such as SNMPc Network Manager, HP Openview Network Node Management (NNM) or What’s Up Gold. This management method requires the SNMP agent on the switch and the SNMP Network Management Station to use the same community string. This management method, in fact, uses two community strings: the get community string and the set community string. If the SNMP Net-work management Station only knows the set community string, it can read and write to the MIBs. However, if it only knows the get community string, it can only read MIBs. The default gets and sets community strings for the POC Managed Switch are public.
Figure 3-1-5 SNMP management

3.6 IFS Smart Discovery Utility

For easily listing the POC Managed Switch in your Ethernet environment, the IFS Smart Discovery Utility from user’s manual CD-ROM is an ideal solution. The following installation instructions are to guide you to running the IFS Smart Discovery Utility.
1. Deposit the IFS Smart Discovery Utility in administrator PC.
2. Run this utility as the following screen appears.
Figure 3-1-6: IFS Smart Discovery Utility Screen
42
two LAN cards or above in the same administrator PC, choose a different LAN card
If there are by using the “Select Adapter” tool.
3. Press the “Refresh” button for the currently connected devices in the discovery list as the screen shows below:
Figure 3-1-7: IFS Smart Discovery Utility Screen
1. This utility shows all necessary information from the devices, such as MAC Address, Device Name, firmware version and Device IP Subnet address. It can also assign new password, IP subnet address and description to the devices.
2. After setup is completed, press the “Update Device”, “Update Multi” or “Update All” button to take effect. The meaning of the 3 buttons above are shown below:
Update Device: use the current setting on one single device. Update Multi: use the current setting on multi-devices. Update All: use the current setting on whole devices in the list.
The same functions mentioned above also can be found in “Option” tools bar.
3. To click the “Control Packet Force Broadcast” function, it allows you to assign a new setting value to the Web Smart Switch under a different IP subnet address.
4. Press the “Connect to Device” button and the Web login screen appears in Figure 3-1-4.
5. Press the “Exit” button to shut down the IFS Smart Discovery Utility.
43
.0 or later version does not allow Java Applets to open sock ets. The user has to

4. WEB CONFIGURATION

This section introduces the configuration and functions of the Web-based management.
About Web-based Management
The POC Managed Switch offers management features that allow users to manage the POC Managed Switch from anywhere on the network through a standard browser such as Microsoft Internet Explorer.
The Web-based Management supports Internet Explorer 8.0. It is based on Java Applets with an aim to reduce network bandwidth consumption, enhance access speed and present an easy viewing screen.
By default, IE8 explicitly modify the browser setting to enable Java Applets to use network ports.
The POC Managed Switch can be configured through an Ethernet connection, making sure the manager PC must be set on the same IP subnet address as the POC Managed Switch.
For example, the default IP address of the POC Managed Switch is 192.168.0.100, then the m anager PC should be set at
192.168.0.x (where x is a number between 1 and 254, except 100), and the default subnet mask is 255.255.255.0.
If you have changed the default IP address of the POC Managed Switch to 192.168.1.1 with subnet mask 255.255.255.0 via console, then the manager PC should be set at 192.168.1.x (where x is a number between 2 and 254) to do the relative configuration on manager PC.
Figure 4-1-1 Web Management
Logging on the switch
1. Use Internet Explorer 8.0 or above Web browser. Enter the factory-default IP address to access the Web interface. The
factory-default IP address is as follows:
http://192.168.0.100
44
2. When the following login screen appears, please enter the default username "admin" with password “admin” (or the
username/password you have changed via console) to login the main screen of POC Managed Switch. The login screen in Figure 4-1-2 appears.
Figure 4-1-2 Login screen
Default User Name: admin Default Password: admin
After entering the username and password, the main screen appears as Figure 4-1-3.
Figure 4-1-3 Default Main Page Now, you can use the Web management interface to continue the switch management or manage the POC Managed Switch by Web interface. The Switch Menu on the left of the web page lets you access all the commands and statistics the POC Managed
45
ou need to
Switch provides.
It is recommended to use Internet Explore 8.0 or above to access POC Managed Switch. The changed IP address takes effect immediately after clicking on the Save button. Y
use the new IP address to access the Web interface.
For security reason, please change and memorize the new password after this first setup. Only accept command in lowercase letter under Web interface.
46

4.1 Main Web Page

The POC Managed Switch provides a Web-based browser interface for configuring and managing it. This interface allows you to access the POC Managed Switch using the Web browser of your choice. This chapter describes how to use the POC Managed Switch’s Web browser interface to configure and manage it.
Main Functions Menu
Copper Port Link Status POC Port Link Status
SFP Port Link Status
Figure 4-1-4 Main Page
Panel Display
The Web agent displays an image of the POC Managed Switch’s ports. The Mode can be set to display different information for the ports, including Link up or Link down. Clicking on the image of a port opens the Port Statistics page. The port states are illustrated as follows:
State Disabled Down Link
POC Ports
RJ45 Ports
SFP Ports
Main Menu
Using the onboard Web agent, you can define system parameters, manage and control the POC Managed Switch, and all its ports, or monitor network conditions. Via the Web-Management, the administrator can set up the POC Managed Switch by
47
selecting the functions those listed in the Main Function. The screen in Figure 4-1-5 appears.
Figure 4-1-5 POC Managed Switch Main Functions Menu
Buttons
: Click to save changes or reset to default.
: Click to logout the POC Managed Switch.
: Click to reboot the POC Managed Switch.
: Click to refresh the page.

4.1.1 Save Button

This save button allows save the running / startup / backup configuration or reset switch in default parameter. The screen in
Figure 4-1-6 appears.
48
Figure 4-1-6 Save Button Screenshot
The page includes the following fields:
Object Description
• Save Confiuration to
FLASH
• Restore to Default
Click to save the configuration. For more detailed information, please refer to chapter 4.1.2 Click to reset switch in default parameter. For more detailed information, please refer to chapter 4.15.1

4.1.2 Configuration Manager

The system file folder contains configuration settings. The screen in Figure 4-1-7 appears.
The page includes the following fields:
Object Description
• Running Configuration
• Startup Configuration
Figure 4-1-7 Save Button Screenshot
Refers to the running configuration sequence use in the switch. In switch, the running configuration file stores in the RAM. In the current version, the running configuration sequence running-config can be saved from the RAM to FLASH by saving “Source File = Running Configuration” to “Destination File = Startup Configuration”, so that the running configuration sequence becomes the startup configuration file, which is called configuration save. To prevent illicit file upload and easier configuration, switch mandates the name of running configuration file to be running-config. Refers to the configuration sequence used in switch startup. Startup configuration file stores in nonvolatile storage, corresponding to the so-called configuration save. If the device supports multi-config file, name the configuration file to be .cfg file, the default is startup.cfg. If the device does not support multi-config file, mandates the name of startup configuration file to be startup-config.
49
• Backup Configuration
Buttons
: Click to save configuration.
The backup configuration is empty in FLASH; please save the backup configuration first by “Maintenance > Backup Manager”.
4.1.2.1 Saving Configuration
In the POC Managed Switch, the running configuration file stores in the RAM. In the current version, the running configuration sequence of running-config can be saved from the RAM to FLASH by ”Save Configurations to FLASH” function, so that the running configuration sequence becomes the startup configuration file, which is called configuration save.
To save all applied changes and set the current configuration as a startup configuration. The startup-configuration file will be loaded automatically across a system reboot.
1. Click ”Save > Save Configurations to FLASH” to login the “Configuration Manager” page.
2. Select “Source File = Running Configuration” and “Destination File = Startup Configuration”.
3. Press the “Apply” button to save running configuration to start up configuration.
50

4.2 System

Use the System menu items to display and configure basic administrative details of the POC Managed Switch. Under System the following topics are provided to configure and view the system information. This section has the following items:
■ System Information The switch system information is provided here.
■ IP Configurations Configure the switch-managed IP information on this page.
■ IPv6 Configuration
■ User Configuration
■ Time Settings Configure SNTP on this page.
■ Log Management The switch log information is provided here.
■ SNMP Management Configure SNMP on this page.
Configure the switch-managed IPv6 information on this page. Configure new user name and password on this page.

4.2.1 System Information

The System Info page provides information for the current device information. System Info page helps a switch administrator to identify the hardware MAC address, software version and system uptime. The screens in Figure 4-2-1 & Figure 4-2-2 appear.
The page includes the following fields:
Object Description
• System Name
• System Location
• System Contact
Figure 4-2-1 System Information Page Screenshot
Display the current system name Display the current system location
Display the current system contact
51
Buttons
• MAC Address
• IP Address
• Subnet Mask
• Gateway
• Loader Version
• Loader Date
• Firmware Version
• Firmware Date
• System Object ID
• System Up Time
• PCN/HW Version
: Click to edit parameter.
The MAC address of this POC Managed Switch. The IP address of this POC Managed Switch.
The subnet mask of this POC Managed Switch. The gateway of this POC Managed Switch.
The loader version of this POC Managed Switch. The loader date of this POC Managed Switch.
The firmware version of this POC Managed Switch. The firmware date of this POC Managed Switch. The system object ID of the POC Managed Switch. The period of time the device has been operational. The hardware version of this POC Managed Switch.

4.2.2 IP Configurations

The IP Configuration includes the IP Address, Subnet Mask and Gatew ay. The configured column is used to view or change the IP configuration. Fill out the IP Address, Subnet Mask and Gateway for the device. The screens in Figure 4-2-2 & F igure 4-2-3 appear.
The page includes the following fields:
Object Description
Figure 4-2-2 IP Address Setting Page Screenshot
52
• Mode
• IP Address
• Subnet Mask
• Gateway
• DNS Server 1/2
Indicates the IP address mode operation. Possible modes are: Static: Enable NTP mode operation.
When enabling NTP mode operation, the agent forwards and transfers NTP messages between the clients and the server when they are not on the same subnet domain.
DHCP: Enable DHCP client mode operation.
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. Provide the IP address of this switch in dotted decimal notation. Provide the subnet mask of this switch in dotted decimal notation. Provide the IP address of the router in dotted decimal notation. Provide the IP address of the DNS Server in dotted decimal notation.
Buttons
: Click to apply changes.
The page includes the following fields:
Object Description
Figure 4-2-3 IP Information Page Screenshot
• DHCP State
• IP Address
• Subnet Mask
• Gateway
• DNS Server 1/2
Display the current DHCP state. Display the current IP address. Display the current subnet mask. Display the current gateway. Display the current DNS server.
53

4.2.3 IPv6 Configuration

The IPv6 Configuration includes Auto Conf iguration, IPv6 Address and Gateway. The configured column is used to view or change the IPv6 configuration. Fill out the Auto Configuration, IPv6 Address and Gateway for the device. The screens in Figure
4-2-4 & Figure 4-2-5 appear.
Figure 4-2-4 IPv6 Address Setting Page Screenshot
The page includes the following fields:
Object Description
• Auto Configuration
• IPv6 Address
• Gateway
Enable IPv6 auto-configuration by checking this box. If it 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.
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 also uses the following legally IPv4 address. For example, '::192.1.2.34'.
Provide the IPv6 Prefix of this switch. The allowed range is 1 through 128. Provide the IPv6 gateway address of this switch.
• DHCPv6 Client
To enable this POC Managed Switch to accept a configuration from a Dynamic Host Configuration Protocol version 6 (DHCPv6) server. By default, the POC Managed Switch does not perform DHCPv6 client actions. DHCPv6 clients request the delegation of long-lived prefixes that they can push to individual local hosts.
54
Buttons
: Click to apply changes.
The page includes the following fields:
Object Description
• Auto Configuration
• IPv6 In Use Address
• IPv6 In Use Router
• IPv6 Static Address
• IPv6 Static Router
• DHCPv6 Client
Figure 4-2-5 IPv6 Information Page Screenshot
Display the current auto configuration state Display the current IPv6 in-use address Display the current in-use gateway Display the current IPv6 static address Display the current IPv6 static gateway Display the current DHCPv6 client status
55
Maximum number of users: 8
(Range: 0-32 characters plain text, case sensitive)
Other

4.2.4 User Configuration

This page provides an overview of the current users and privilege type. Currently the only way to login as another user on the Web server is to close and reopen the browser. After the setup is completed, please press the “Apply” button to take effect. Please login Web interface with a new user name and password; the screens in Figure 4-2-6 & Figure 4-2-7 appear.
Figure 4-2-6 Local User Information Page Screenshot
The page includes the following fields:
Buttons
Object Description
• Username
• Password Type
• Password
• Retype Password
• Privilege Type
: Click to apply changes.
The name identifying the user. Maximum length: 32 characters;
The password type for the user. Enter the user’s new password here.
Please enter the user’s new password here again to confirm. The privilege type for the user.
Options:
• Admin
• User
•
56
Figure 4-2-7 Local User Page Screenshot
The page includes the following fields:
Object Description
• Username
• Password Type
• Privilege Type
• Modify
Display the current username Display the current password type Display the current privilege type Click to modify the local user entry
: Delete the current user

4.2.5 Time Settings

4.2.5.1 System Time
Configure SNTP on this page.
SNTP is an acronym for Simple Network Time Protocol, a network protocol for synchronizing the clocks of computer systems. You can specify SNTP Servers and set GMT Time zone. The SNTP Configuration screens in Figure 4-2-8 & Figure 4-2-9 appear.
The page includes the following fields:
Object Description
• Enable SNTP
Figure 4-2-8 SNTP Setup Page Screenshot
Enabled: Enable SNTP mode operation.
When enabling SNTP mode operation, the agent forwards and transfers
57
Disabled: Disable SNTP mode operation.
SNTP messages between the clients and the server when they are not on the same subnet domain.
• Manual Time
• Time Zone
• Daylight Saving Time
• Daylight Saving Time
Offset
To set time manually.
Year - Select the starting Year.  Month - Select the starting month.  Day - Select the starting day.  Hours - Select the starting hour.  Minutes - Select the starting minute.  Seconds - Select the starting seconds.
Allows to select the time zone according to the current location of switch.
This is used to set the clock forward or backward according to the configurations set below for a defined Daylight Saving Time duration. Select 'Disable' to disable the Daylight Saving Time configuration. Select 'Recurring' and configure the Daylight Saving Time duration to repeat the configuration every year. Select 'Non-Recurring' and configure the Daylight Saving Time duration for single time configuration. (Default : Disabled ).
Enter the number of minutes to add during Daylight Saving Time. ( Range: 1 to
1440 )
• Recurring From • Week - Select the starting week number.
• Day - Select the starting day.
• Month - Select the starting month.
• Hours - Select the starting hour.
• Minutes - Select the starting minute.
• Recurring To • Week - Select the starting week number.
• Day - Select the starting day.
• Month - Select the starting month.
• Hours - Select the starting hour.
• Minutes - Select the starting minute.
• Non-recurring From • Week - Select the starting week number.
• Day - Select the starting day.
• Month - Select the starting month.
• Hours - Select the starting hour.
• Minutes - Select the starting minute.
• Non-recurring To • Week - Select the starting week number.
• Day - Select the starting day.
• Month - Select the starting month.
• Hours - Select the starting hour.
• Minutes - Select the starting minute.
58
Buttons
: Click to apply changes.
The page includes the following fields:
Object Description
• Current Data/Time
• SNTP
• Time Zone
• Daylight Saving Time
• Daylight Saving Time
Offset
• From
• To
Figure 4-2-9 Time Information Page Screenshot
Display the current data/time
Display the current SNTP state
Display the current time zone
Display the current daylight saving time state
Display the current daylight saving time offset state
Display the current daylight saving time from
Display the current daylight saving time to
59
4.2.5.2 SNTP Server Settings
The SNTP Server Configuration screens in Figure 4-2-10 & Figure 4-2-11 appear.
Figure 4-2-10 SNTP Setup Page Screenshot
The page includes the following fields:
Object Description
Buttons
• SNTP Server Address
• Server Port
: Click to apply changes.
Figure 4-2-11 SNTP
Type the IP address or domain name of the SNTP server Type the port number of the SNTP
Server Information Page Screenshot
The page includes the following fields:
Object Description
• SNTP Server Address
• Server Port
Display the current SNTP server address
Display the current SNTP server port
60

4.2.6 Log Management

The POC Managed Switch log management is provided here. The local logs allow you to configure and limit system messages that are logged to flash or RAM memory. The default is for event levels 0 to 3 to be logged to flash and levels 0 to 6 to be logged to RAM. The following table lists the event levels of the POC Managed Switch:
Level Severity Name Description
7
Debug
6
Informational
5
Notice
4
Warning
3
Error
2
Critical
1
Alert
0
Emergency
Debugging messages Informational messages only Normal but significant condition, such as cold start Warning conditions (e.g., return false, unexpected return) Error conditions (e.g., invalid input, default used) Critical conditions (e.g., memory allocation, or free memory error - resource exhausted) Immediate action needed System unusable
4.2.6.1 Local Log
The switch system local log information is provided here. The local Log screens in Figure 4-2-12 & Figure 4-2-13 appear.
The page includes the following fields:
Object Description
• Logging Service
Buttons
: Click to apply changes.
Figure 4-2-12 Logging Settings Page Screenshot
Enabled: Enable logging service operation. Disabled: Disable logging service operation.
61
Figure 4-2-13 Logging Information Page Screenshot
The page includes the following fields:
Object Description
• Logging Service
Display the current logging service status
4.2.6.2 Local Log
The switch system local log information is provided here. The local Log screens in Figure 4-2-14 & Figure 4-2-15 appear.
Figure 4-2-14 Local Log Target Setting Page Screenshot
The page includes the following fields:
Object Description
• Target
• Severity
The target of the local log entry. The following target types are supported:
Buffered: Target the buffer of the local log. File: Target the file of the local log.
The severity of the local log entry. The following severity types are supported:
emerg: Emergency level of the system unsable for local log. alert: Alert level of the immediate action needed for local log. crit: Critical level of the critical conditions for local log. error: Error level of the error conditions for local log. warning: Warning level of the warning conditions for local log. notice: Notice level of the normal but significant conditions for local log. info: Informational level of the informational messages for local log. debug: Debug level of the debugging messages for local log.
62
Buttons
: Click to apply changes.
Figure 4-2-15 Local Log Setting Status Page Screenshot
The page includes the following fields:
Object Description
• Status
• Target
• Severity
• Action
Display the current local log state
Display the current local log target
Display the current local log severity
: Delete the current status
63
4.2.6.3 Remote Syslog
Configure remote syslog on this page. The Remote Syslog page allows you to configure the logging of messages that are sent to syslog servers or other management stations. You can also limit the event messages sent to only those messages below a specified level.
The Remote Syslog screens in Figure 4-2-16 & Figure 4-2-17 appear.
Figure 4-2-16 Remote Log Target Page Screenshot
The page includes the following fields:
Object Description
• Server Address
• Server Port
Provide the remote syslog IP address of this switch.
Provide the port number of remote syslog server. Default Port no.: 514
• Severity
The severity of the local log entry. The following severity types are supported:
emerg: Emergency level of the system unsable for local log. alert: Alert level of the immediate action needed for local log. crit: Critical level of the critical conditions for local log.
64
error: Error level of the error conditions for local log. warning: Warning level of the warning conditions for local log. notice: Notice level of the normal but significant conditions for local log. info: Informational level of the informational messages for local log. debug: Debug level of the debugging messages for local log.
• Facility
Buttons
: Click to apply changes.
Figure 4-2-17 Remote Log Setting Status Page Screenshot
The page includes the following fields:
Object Description
• Status
• Server Info
Local0~7: local user 0~7
Display the current remote syslog state Display the current remote syslog server information
• Severity
• Facility
• Action
Display the current remote syslog severity Display the current remote syslog facility
: Delete the remote server entry
4.2.6.4 Log Message
The switch log view is provided here. The Log View screens in Figure 4-2-18, Figure 4-2-19 & Figure 4-2-20 appear.
Figure 4-2-18 Log Information Select Page Screenshot
The page includes the following fields:
65
Object Description
• Target
• Severity
• Category
The target of the log view entry . The following target types are supported:
Buffered: Target the buffered of the log view. File: Target the file of the log view.
The severity of the log view entry. The following severity types are supported:
emerg: Emergency level of the system unsable for log view. alert: Alert level of the immediate action needed for log view. crit: Critical level of the critical conditions for log view. error: Error level of the error conditions for log view. warning: Warning level of the warning conditions for log view. notice: Notice level of the normal but significant conditions for log view. info: Informational level of the informational messages for log view. debug: Debug level of the debugging messages for log view.
The category of the log view includes: AAA, ACL, CABLE_DIAG, DAI, DHCP_SNOOPING, Dot1X, GVRP, IGMP_SNOOPING, IPSG, L2, LLDP, Mirror, MLD_SNOOPING, Platform, PM, Port, PORT_SECURITY, QoS, Rate, SNMP and STP
Buttons
: Click to view log.
The page includes the following fields:
Object Description
• Target
Figure 4-2-19 Logging Information Page Screenshot
Display the current log target
• Severity
• Category
• Total Entries
Display the current log severity Display the current log category Display the current log entries
66
Figure 4-2-20 Logging Messages Page Screenshot
The page includes the following fields:
Object Description
Buttons
• No.
• Timestamp
• Category
• Severity
• Message
: Click to clear the log.
: Click to refresh the log.
This is the number for logs Display the time of log Display the category type Display the severity type Display the log message
67
：

4.2.7 SNMP Management

4.2.7.1 SNMP Overview
The Simple Network Management Protocol (SNMP) is an application layer protocol that facilitates the exchange of management information between network devices. It is part of the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol suite. SNMP enables network administrators to manage network performance, find and solve network problems, and plan for network growth.
An SNMP-managed network consists of four components: Network management stations (NMSs), SNMP agent, management information base (MIB) and network-management protocol: 。 Network management stations (NMSs): Sometimes called consoles, these devices execute m anagem ent applications
that monitor and control network elements. Physically, NMSs are usually engineering workstation-caliber computers with fast CPUs, megapixel color displays, substantial memory, and abundant disk space. At least one NMS must be present in each managed environment.
。 Agents
。 Management information base (MIB)：A MIB is a collection of managed objects residing in a virtual information store.
。 Network-management protocol：A management protocol is used to convey management information between agents
SNMP Operations
SNMP itself is a simple request/response protocol. NMSs can send multiple requests without receiving a response.
。 Get -- Allows the NMS to retrieve an object instance from the agent. 。 Set -- Allows the NMS to set values for object instances within an agent. 。 Trap -- Used by the agent to asynchronously inform the NMS of some event. The SNMPv2 trap m essage is designed t o
SNMP Community
An SNMP community is the group that devices and management stations running SNMP belong to. It helps define where information is sent. The community name is used to identify the group. An SNMP device or agent may belong to more than one SNMP community. It will not respond to requests from management stations that do not belong to one of its communities.
Agents are software modules that reside in network elements. They collect and store management information
such as the number of error packets received by a network element.
Collections of related managed objects are defined in specific MIB modules.
and NMSs. SNMP is the Internet community's de facto standard management protocol.
replace the SNMPv1 trap message.
SNMP default communities are:
。 Write = private 。 Read = public
68
4.2.7.2 SNMP System Information
Configure SNMP setting on this page. The SNMP System global setting screens in Figure 4-2-21 & Figure 4-2-22 appear.
Figure 4-2-21 SNMP Global Setting Page Screenshot
The page includes the following fields:
Object Description
Buttons
• Status
: Click to apply changes.
Indicates the SNMP mode operation. Possible modes are:
Enabled: Enable SNMP mode operation. Disabled: Disable SNMP mode operation.
The page includes the following fields:
Object Description
• SNMP
Figure 4-2-22 SNMP Information Page Screenshot
Display the current SNMP status
69
4.2.7.3 SNMP View
Configure SNMPv3 view table on this page. The entry index keys are View Name and OID Subtree. The SNMPv3 View Table Setting screens in Figure 4-2-23 and Figure 4-2-24 appear.
Figure 4-2-23 SNMPv3 View Table Setting Page Screenshot
The page includes the following fields:
Buttons
Object Description
• View Name
• Subtree OID
• Subtree OID Mask
• View Type
A string identifying the view name that this entry should belong to. The allowed string length is 1 to 16. The OID defining the root of the subtree to add to the named view. The allowed string content is digital number or asterisk(*). The bitmask identifies which positions in the specified object identifier are to be regarded as "wildcards" for the purpose of pattern-matching. Indicates the view type that this entry should belong to. Possible view type are:
included: An optional flag to indicate that this view subtree should be included. excluded: An optional flag to indicate that this view subtree should be excluded.
General, if a view entry's view type is 'excluded', it should exist another view entry in which view type is 'included' and its OID subtree oversteps the 'excluded' view entry.
: Click to add a new view entry.
70
Figure 4-2-24 SNMP View Table Status Page Screenshot
The page includes the following fields:
Object Description
• View Name
• Subtree OID
• OID Mask
• View Type
• Action
Display the current SNMP view name
Display the current SNMP subtree OID
Display the current SNMP OID mask
Display the current SNMP view type
: Delete the view table entry.
71
4.2.7.4 SNMP Access Group
Configure SNMPv3 access group on this page. The entry index keys are Group Name, Security Model and Security Level. The SNMPv3 Access Group Setting screens in Figure 4-2-25 & Figure 4-2-26 appear.
Figure 4-2-25 SNMPv3 Access Group Setting Page Screenshot
The page includes the following fields:
Object Description
• Group Name
• Security Model
• Security Level
• Read View Name
A string identifying the group name that this entry should belong to. The allowed string length is 1 to 16. Indicates the security model that this entry should belong to. Possible security models are:
v1: Reserved for SNMPv1. v2c: Reserved for SNMPv2c. V3: Reserved for SNMPv3 or User-based Security Model (USM)
Indicates the security model that this entry should belong to. Possible security models are:
Noauth: None authentication and none privacy security levels are
assigned to the group.
auth: Authentication and none privacy. priv: Authentication and privacy.
Note: The Security Level applies to SNNPv3 only.
Read view name is the name of the view in which you can only view the contents of the agent. The allowed string length is 1 to 16.
• Write View Name
• Notify View Name
Write view name is the name of the view in which you enter data and configure the contents of the agent. The allowed string length is 1 to 16. Notify view name is the name of the view in which you specify a notify, inform, or trap.
72
Buttons
: Click to add a new access entry.
: Check to delete the entry.
Figure 4-2-26 SNMP View Table Status Page Screenshot
The page includes the following fields:
Object Description
• Group Name
• Security Model
• Security Level
• Read View Name
• Write View Name
• Notify View Name
• Action
Display the current SNMP access group name
Display the current security model
Display the current security level
Display the current read view name
Display the current write view name
Display the current notify view name
: Delete the access group entry.
4.2.7.5 SNMP Community
Configure SNMP Community on this page. The SNMP Community screens in Figure 4-2-27 & Figure 4-2-28 appear.
Figure 4-2-27 Community Setting Page Screenshot
73
The page includes the following fields:
Object Description
Buttons
• Community Name
• Community Mode
• Group Name
• View Name
• Access Right
: Click to apply changes.
Indicates the community read/write access string to permit access to SNMP agent. The allowed string length is 0 to 16. Indicates the SNMP community supported mode. Possible versions are:
Basic: Set SNMP community mode supported version 1 and 2c. Advanced: Set SNMP community mode supported version 3.
A string identifying the group name that this entry should belong to. The allowed string length is 1 to 16. A string identifying the view name that this entry should belong to. The allowed string length is 1 to 16. Indicates the SNMP community type operation. Possible types are:
RO=Read-Only: Set access string type in read-only mode. RW=Read-Write: Set access string type in read-write mode.
The page includes the following fields:
Object Description
• Community Name
• Group Name
• View Name
Figure 4-2-28 Community Status Page Screenshot
Display the current community type Display the current SNMP access group’s name
Display the current view name
• Access Right
• Delete
Display the current access type
: Delete the community entry
74
4.2.7.6 SNMP User
Configure SNMPv3 users table on this page. Each SNMPv3 user is defined by a unique name. Users must be configured with a specific security level and assigned to a group. The SNMPv3 group restricts users to a specific read, write, and notify view. The entry index key is User Name. The SNMPv3 User Setting screens in Figure 4-2-29 & Figure 4-2-30 appear.
Figure 4-2-29 SNMPv3 Users Configuration Page Screenshot
The page includes the following fields:
Object Description
• User Name
• Group
• Privilege Mode
• Authentication
Protocol
A string identifying the user name that this entry should belong to. The allowed string length is 1 to 16. The SNMP Access Group. A string identifying the group name that this entry should belong to. Indicates the security model that this entry should belong to. Possible security models are:
NoAuth: None authentication and none privacy. Auth: Authentication and none privacy. Priv: Authentication and privacy.
The value of security level cannot be modified if entry already exists. That means you must first ensure that the value is set correctly. Indicates the authentication protocol that this entry should belong to. Possible authentication protocols are:
None: None authentication protocol. MD5: An optional flag to indicate that this user using MD5
authentication protocol.
SHA: An optional flag to indicate that this user using SHA
authentication protocol. The value of security level cannot be modified if entry already exist. That means you must first ensure that the value is set correctly.
• Authentication
Password
• Encryption Protocol
A string identifying the authentication pass phrase. For both MD5 and SHA authentication protocol, the allowed string length is 8 to 16. Indicates the privacy protocol that this entry should belong to. Possible privacy protocol are:
None: None privacy protocol.
75
DES: An optional flag to indicate that this user using DES
authentication protocol.
• Encryption Key
Buttons
: Click to add a new user entry.
Figure 4-2-30 SNMPv3 Users Status Page Screenshot
The page includes the following fields:
Object Description
• User Name
A string identifying the privacy pass phrase. The allowed string length is 8 to 16.
Display the current user name
• Group
• Privilege Mode
• Authentication Protocol
• Encryption Protocol
• Access Right
• Action
Display the current group Display the current privilege mode Display the current authentication protocol Display the current encryption protocol Display the current access right
: Delete the user entry
4.2.7.7 SNMPv1, 2 Notification Reci pients
Configure SNMPv1 and 2 notification recipients on this page. The SNMPv1, 2 Notification Recipients screens in Figure 4-2-31 &
Figure 4-2-32 appear.
Figure 4-2-31 SNMPv1, 2 Notification Recipients Page Screenshot
The page includes the following fields:
Object Description
76
Buttons
• Server Address
• SNMP Version
Indicates the SNMP trap destination address. It allow a valid IP address in dotted decimal notation ('x.y.z.w'). It can also represent a legally valid IPv4 address. For example, '::192.1.2.34'. Indicates the SNMP trap supported version. Possible versions are:
SNMP v1: Set SNMP trap supported version 1. SNMP v2c: Set SNMP trap supported version 2c.
• Notif y Type
• Community Name
• UDP Port
• Time Out
• Retries
: Click to add a new SNMPv1, 2 host entry.
Set the notify type in traps or informs. Indicates the community access string when send SNMP trap packet. Indicates the SNMP trap destination port. SNMP Agent will send SNMP message via this port, the port range is 1~65535. Indicates the SNMP trap inform timeout. The allowed range is 1 to 300. Indicates the SNMP trap inform retry times. The allowed range is 1 to 255.
Figure 4-2-32 SNMPv1, 2 Host Status Page Screenshot
The page includes the following fields:
Object Description
• Server Address
• SNMP Version
• Notif y Type
• Community Name
• UDP Port
• Time Out
• Retries
Display the current server address Display the current SNMP version Display the current notify type Display the current community name Display the current UDP port Display the current time out Display the current retry times
• Action
: Delete the SNMPv1, 2 host entry.
4.2.7.9 SNMPv3 Not i fication Recipients
Configure SNMPv3 notification recipients on this page. The SNMPv1, 2 Notification Recipients screens in Figure 4-2-33 &
Figure 4-2-34 appear.
77
Figure 4-2-33 SNMPv3 Notification Recipients Page Screenshot
The page includes the following fields:
Object Description
Buttons
• Server Address
• Notif y Type
• User Name
• UDP Port
• Time Out
• Retries
: Click to add a new SNMPv3 host entry.
Indicates the SNMP trap destination address. It allows a valid IP address in dotted decimal notation ('x.y.z.w'). It can also represent a legally valid IPv4 address. For example, '::192.1.2.34'. Set the notify type in traps or informs. Indicates the user string when send SNMP trap packet. Indicates the SNMP trap destination port. SNMP Agent will send SNMP message via this port, the port range is 1~65535. Indicates the SNMP trap inform timeout. The allowed range is 1 to 300. Indicates the SNMP trap inform retry times. The allowed range is 1 to 255.
Figure 4-2-34 SNMPv3 Host Status Page Screenshot
The page includes the following fields:
Object Description
• Server Address
• Notif y Type
• User Name
• UDP Port
• Time Out
• Retries
Display the current server address Display the current notify type Display the current user name Display the current UDP port Display the current time out Display the current retry times
78
• Action
: Delete the SNMPv3 host entry
4.2.7.10 SNMP Engine ID
Configure SNMPv3 Engine ID on this page. The entry index key is Engine ID. The remote engine ID is used to compute the security digest for authenticating and encrypting packets sent to a user on the remote host. The SNMPv3 Engine ID Setting screens in Figure 4-2-35 & Figure 4-2-36 appear.
Figure 4-2-35 SNMPv3 Engine ID Setting Page Screenshot
The page includes the following fields:
Object Description
• Engine ID
Buttons
: Click to apply changes.
An octet string identifying the engine ID that this entry should belong to. The string must contain an even number between 10 and 64 hexadecimal digits, but all-zeros and all-'F's are not allowed.
Figure 4-2-36 SNMPv3 Engine ID Status Page Screenshot
The page includes the following fields:
Object Description
• User Default
Display the current status
79
• Engine ID
Display the current engine ID
4.2.7.11 SNMP Remote Engine ID
Configure SNMPv3 remote Engine ID on this page. The SNMPv3 Remote Engine ID Setting screens in Figure 4-2-37 & Figure
4-2-38 appear.
Figure 4-2-37 SNMPv3 Remote Engine ID Setting Page Screenshot
The page includes the following fields:
Object Description
• Remote IP Address
• Engine ID
Buttons
: Click to apply changes.
Figure 4-2-38 SNMPv3 Remote Engine ID Status Page Screenshot
Indicates the SNMP remote engine ID address. It allows a valid IP address in dotted decimal notation ('x.y.z.w'). An octet string identifying the engine ID that this entry should belong to.
The page includes the following fields:
Object Description
• Remote IP Address
Display the current remote IP address
80
• Engine ID
• Action
Display the current engine ID
: Delete the remote IP address entry
81

4.3 Port Management

Use the Port Menu to display or configure the POC Managed Switch's ports. This section has the following items:
Port Configuration POC Port Configuration Port Counters Bandwidth Utilization Port Mirroring Jumbo Frame Port Error Disable
Configuration
Port Error Disabled Status Protected Ports EEE SFP Module Information
Configures port configuration settings Configures POC port configuration settings Lists Ethernet and RMON port statistics Displays current bandwidth utilization Sets the source and target ports for mirroring Sets the jumbo frame on the switch
Configures port error disable settings
Disables port error status Configures protected ports settings Configures EEE settings Displays SFP module information.

4.3.1 Port Configuration

This page displays current port configurations and status. Ports can also be configured here. The table has one row for each port on the selected switch in a number of columns, which are: The Port Configuration screens in Figure 4-3-1A & Figure 4-3-2A appear.
Figure 4-3-1A Port Settings Page Screenshot
The page includes the following fields:
Object Description
• Port Select
• Enabled
Select port number from this drop-down list.
Indicates the port state operation. Possible states are:
Enabled - Start up the port manually.
82
Disabled – Shut down the port manually.
• Speed
• Duplex
• Flow Control
Select any available link speed for the given switch port. Draw the menu bar to select the mode.
Auto - Setup Auto negotiation. Auto-10M - Setup 10M Auto negotiation. Auto-100M - Setup 100M Auto negotiation. Auto-1000M - Setup 1000M Auto negotiation. Auto-10/100M - Setup 10/100M Auto negotiation. 10M - Setup 10M Force mode. 100M - Setup 100M Force mode. 1000M - Setup 1000M Force mode.
Select any available link duplex for the given switch port. Draw the menu bar to select the mode.
Auto - Setup Auto negotiation. Full - Force sets Full-Duplex mode. Half - Force sets Half-Duplex mode.
When Auto Speed is selected for a port, this section indicates the flow control capability that is advertised to the link partner. When a fixed-speed setting is
Buttons
selected, that is what is used. Current Rx column indicates whether pause frames on the port are obeyed. 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.
: Click to apply changes.
Figure 4-3-2A Port Status Page Screenshot
83
The page includes the following fields:
Object Description
• Port
• Description
• Enable State
• Link Status
• Speed
• Duplex
• Flow Control Configuration
• Flow Control Status
This is the logical port number for this row
Click
Display the current port state Display the current link status
Display the current speed status of the port Display the current duplex status of the port Display the current flow control configuration of the port Display the current flow control status of the port
to indicate the port name

4.3.2 POC Port Configuration

This page displays current POC port configurations and status. Ports can also be configured here. The table has one row for each port on the selected switch in a number of columns, which are: The Port Configuration screens in Figure 4-3-1B & Figure 4-3-2B appear.
The page includes the following fields:
Object Description
• Port Select
• Enabled
Figure 4-3-1B POC Port Settings Page Screenshot
Select port number from this drop-down list.
Indicates the port state operation. Possible state are:
Enabled - Start up the port manually. Disabled – Shut down the port manually.
84
Buttons
: Click to apply changes.
Figure 4-3-2B Port Status Page Screenshot
The page includes the following fields:
Object Description
• Port
• Description
• Enable State
• Link Status
This is the logical port number for this row
Click
Display the current port state Display the current link status
to indicate the port name

4.3.3 Port Counters

This page provides an overview of traffic and trunk statistics for all switch ports. The Port Statistics screens in Figure 4-3-3,
Figure 4-3-4, Figure 4-3-5 & Figure 4-3-6 appear.
The page includes the following fields:
Figure 4-3-3 Port MIB Counters Page Screenshot
85
Object Description
• Port
• Mode
Select port number from this drop-down list. Select port counters mode. Option:
All  Interface  Ether-link  RMON
Figure 4-3-4 Interface Counters Page Screenshot
Object Description
• Received Octets
• Received Unicast
Packets
• Received Unknown
Unicast Packets
• Received Discarded
Packets
• Transmit Octets
The total number of octets received on the interface, including framing characters. The number of subnetwork-unicast packets delivered to a higher-layer protocol.
The number of packets received via the interface which is discarded because of an unknown or unsupported protocol. The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space. The total number of octets transmitted out of the interface, including framing characters.
• Transmit Unicast
Packets
The total number of packets that higher-level protocols requested is transmitted to a subnetwork-unicast address, including those that were discarded or not sent.
86
• Transmit Unknown
Unicast Packets
• Transmit Discarded
Packets
• Received Multicast
Packets
• Received Broadcast
Packets
• Transmit Multicast
Packets
• Transmit Broadcast
Packets
The total number of packets that higher-level protocols requested is transmitted to a subnetwork-unicast address, including those that were discarded or not sent. The number of inbound packets which is chosen to be discarded even though no errors have been detected to prevent from being delivered to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space. The number of packets, delivered by this sub-layer to a higher (sub-) layer, is addressed to a multicast address at this sub-layer. The number of packets, delivered by this sub-layer to a higher (sub-) layer, addressed to a broadcast address at this sub-layer. The total number of packets that higher-level protocols requested is transmitted and is addressed to a multicast address at this sub-layer, including those that were discarded or not sent. The total number of packets that higher-level protocols requested is transmitted, and addressed to a broadcast address at this sub-layer, including those that were discarded or not sent.
Figure 4-3-5 Ethernet link Counters Page Screenshot
Object Description
• Alignment Errors
• FCS Errors
• Single Collision
Frames
The number of alignment errors (missynchronized data packets).
A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. This count does not include frames received with frame-too-long or frame-too-short error. The number of successfully transmitted frames for which transmission is inhibited by exactly one collision.
87
• Multiple Collision
Frames
• Deferred
Transmissions
• Late Collision
• Excessive Collision
• Frame Too Long
• Symbol Errors
• Control In Unknown
Opcodes
• In Pause Frames
• Out Pause Frames
A count of successfully transmitted frames for which transmission is inhibited by more than one collision. A count of frames for w hich the first transmission attempt on a p articula r interface is delayed because the medium was busy. The number of times that a collision is detected later than 512 bit-times into the transmission of a packet. A count of frames for which transmission on a particular interface fails due to excessive collisions. This counter does not increase when the interface is operating in full-duplex mode. A count of frames received on a particular interface that exceeds the maximum permitted frame size. The number of received and transmitted symbol errors
The number of received control unknown opcodes
The number of received pause frames
The number of transmitted pause frames
Figure 4-3-6 RMON Counters Page Screenshot
Object Description
• Drop Events
The total number of events in which packets were dropped due to lack of
88
resources.
• Octets
• Packets
• Broadcast Packets
• Multicast Packets
• CRC / Alignment
Errors
• Undersize Packets
• Oversize Packets
• Fragments
The total number of octets received and transmitted on the interface, including framing characters. The total number of packets received and transmitted on the interface.
The total number of good frames received that were directed to the broadcast address. Note that this does not include multicast packets. The total number of good frames received that were directed to this multicast address. The number of CRC/alignment errors (FCS or alignment errors).
The total number of frames received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed. The total number of frames received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed. The total number of frames received that were less than 64 octets in length (excluding framing bits, but including FCS octets) and had either an FCS or alignment error.
• Jabbers
• Collisions
• 64 Bytes Frames
• 65-127 Byte Frames
128-255 Byte Frames 256-511 Byte Frames 512-1023 Byte Frames 1024-1518 Byte Frames
The total number of frames received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either an FCS or alignment error. The best estimate of the total number of collisions on this Ethernet segment.
The total number of frames (including bad packets) received and transmitted that were 64 octets in length (excluding framing bits but including FCS octets). The total number of frames (including bad packets) received and transmitted where the number of octets falls within the specified range (excluding framing bits but including FCS octets).
89
10 sec

4.3.4 Bandwidth Utilization

The Bandwidth Utilization page displays the percentage of the total available bandwidth being used on the ports. Bandwith utilization statistics can be viewed using a line graph. The Bandwidth Utilization screen in Figure 4-3-7 appears.
To view the port utilization, click on the Port Management folder and then the Bandwidth Utilization link:
Figure 4-3-7 Port Bandwidth Utilization Page Screenshot
The page includes the following fields:
Object Description
• Refresh Period
• IFG
This shows the period interval between last and next refresh. Options:
2 sec 5 sec
Allow user to enable or disable this function
90

4.3.5 Port Mirroring

Configure port Mirroring on this page. This function provides monitoring of network traffic that forwards a copy of each incoming or outgoing packet from one port of a network switch to another port where the packet can be studied. It enables the manager to keep close track of switch performance and alter it if necessary.
• To debug network problems, selected traffic can be copied, or mirrored, to a mirror port where a frame analyzer can be attached to analyze the frame flow.
• The POC Managed Switch can unobtrusively mirror traffic from any port to a monitor port. You can then attach a protocol analyzer or RMON probe to this port to perform traffic analysis and verify connection integrity.
Figure 4-3-8 Port Mirror Application
The traffic to be copied to 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).
Mirror Port Configuration
The Port Mirror Configuration screens in Figure 4-3-9 & Figure 4-3-10 appear.
91
Figure 4-3-9 Port Mirroring Settings Page Screenshot
The page includes the following fields:
Buttons
Object Description
• Session ID
• Monitor Session State
• Destination Port
• Allow-ingress
• Sniffer TX Ports
• Sniffer RX Ports
: Click to apply changes.
Set the port mirror session ID. Possible ID are: 1 to 4. Enable or disable the port mirroring function. Select the port to mirror destination port. Frames from ports that have either source (RX) or destination (TX) mirroring enabled are mirrored to this port. Frames transmitted from these ports are mirrored to the mirroring port. Frames received are not mirrored. Frames received at these ports are mirrored to the mirroring port. Frames transmitted are not mirrored.
Figure 4-3-10 Mirroring Status Page Screenshot
92
The page includes the following fields:
Object Description
• Session ID
• Destination Port
• Ingress State
• Source TX Port
• Source RX Port
Display the session ID This is the mirroring port entry Display the ingress state Display the current TX ports Display the current RX ports

4.3.6 Jumbo Frame

This page provides to select the maximum frame size allowed for the switch port. The Jumbo Frame screens in Figure 4-3-11 &
Figure 4-3-12 appear.
Figure 4-3-11 Jumbo Frame Setting Page Screenshot
The page includes the following fields:
Object Description
• Jumbo Frame (Bytes)
Buttons
: Click to apply changes.
Figure 4-3-12 Jumbo Frame Information Page Screenshot
Enter the maximum frame size allowed for the switch port, including FCS. The allowed range is 64 bytes to 9216 bytes.
The page includes the following fields:
Object Description
• Jumbo
Display the current maximum frame size
93

4.3.7 Port Error Disabled Configuration

This page provides to set port error disable function. The Port Error Disable Configuration screens in Figure 4-3-13 & Figure
4-3-14 appear.
Figure 4-3-13 Error Disabled Recovery Page Screenshot
The page includes the following fields:
Object Description
• Recovery Interval
• BPDU Guard
• Self Loop
• Broadcast Flood
• Unknown Multicast
Flood
• Unicast Flood
• ACL
• Port Security
The period (in seconds) for which a port will be kept disabled in the event of a port error is detected (and the port action shuts down the port). Enable or disable the port error disabled function to check status by BPDU guard. Enable or disable the port error disabled function to check status by self loop. Enable or disable the port error disabled function to check status by broadcast flood. Enable or disable the port error disabled function to check status by unknown multicast flood. Enable or disable the port error disabled function to check status by unicast flood. Enable or disable the port error disabled function to check status by ACL. Enable or disable the port error disabled function to check status by port security
Violation
• DHCP Rate Limit
• ARP Rate Limt
violation. Enable or disable the port error disabled function to check status by DHCP rate limit Enable or disable the port error disabled function to check status by ARP rate limit
94
Buttons
: Click to apply changes.
Figure 4-3-14 Error Disabled Information Page Screenshot
The page includes the following fields:
Object Description
• Recovery Interval
• BPDU Guard
• Self Loop
• Broadcast Flood
• Unknown Multicast
Flood
• Unicast Flood
• ACL
• Port Security Violation
• DHCP Rate Limit
Display the current recovery interval time Display the current BPDU guard status Display the current self loop status Display the current broadcst flood status Display the current unknown multicast flood status
Display the current unicast flood status Display the current ACL status
Display the current port security violation status Display the current DHCP rate limit status
• ARP Rate Limt
Display the current ARP rate limit status
95

4.3.8 Port Error Disabled

This page provides disable that transitions a port into error disable and the recovery options. The ports were disabled by some protocols such as BPDU Guard, Loopback and UDLD. The Port Error Disable screen in Figure 4-3-15 appears.
Figure 4-3-15 Port Error Disable Page Screenshot
The displayed counters are:
Object Description
• Port Name
• Error Disable Reason
• Time Left (Seconds)
Display the port for error disable
Display the error disabled reason of the port
Display the time left

4.3.9 Protected Ports

Overview
When a switch port is configured to be a member of protected group (also called Private VLAN), communication between protected ports within that group can be prevented. Two application examples are provided in this section:
• Customers connected to an ISP can be members of the protected group, but they are not allowed to communicate with each other within that VLAN.
• Servers in a farm of web servers in a Demilitarized Zone (DMZ) are allowed to communicate with the outside world and with database servers on the inside segment, but are not allowed to communicate with each other
96
For protected port group to be applied, the POC Managed Switch must first be configured for standard VLAN operation. Ports in a protected port group fall into one of these two groups: Promiscuous (Unprotected) ports
— Ports from which traffic can be forwarded to all ports in the private VLAN — Ports which can receive traffic from all ports in the private VLAN
Isolated (Protected) ports
— Ports from which traffic can only be forwarded to promiscuous ports in the private VLAN — Ports which can receive traffic from only promiscuous ports in the private VLAN
The configuration of promiscuous and isolated ports applies to all private VLANs. When traffic comes in on a promiscuous port in a private VLAN, the VLAN mask from the VLAN table is applied. When traffic comes in on an isolated port, the private VLAN mask is applied in addition to the VLAN mask from the VLAN table. This reduces the ports to which forwarding can be done to just the promiscuous ports within the private VLAN.
The port settings relate to the currently unit, as reflected by the page header. The Port Isolation Configuration screens in Figure
4-3-16 & Figure 4-3-17 appear.
97
Figure 4-3-16 Protected Ports Settings Page Screenshot
The page includes the following fields:
Object Description
Buttons
• Port List
• Port Type
: Click to apply changes.
Select port number from this drop-down list.
Displays protected port types.
- Protected: A single stand-alone VLAN that contains one promiscuous port and one or more isolated (or host) ports. This VLAN conveys traffic between the isolated ports and a lone promiscuous port.
- Unprotected: A promiscuous port can communicate with all the interfaces within a private VLAN. This is the default setting.
The page includes the following fields:
Object Description
• Protected Ports
• Unprotected Ports
Figure 4-3-17 Port Isolation Status Page Screenshot
Display the current protected ports
Display the current unprotected ports
98

4.3.10 EEE

What is EEE
EEE is a power saving option that reduces the power usage when there is low or no traffic utilization. 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 wakeup time information using the LLDP protocol. EEE works for ports in auto-negotiation mode, where the port is negotiated to either 1G or 100 Mbit full duplex mode. For ports that are not EEE-capable the corresponding EEE checkboxes are grayed out and thus impossible to enable EEE for. The EEE port settings relate to the currently unit, as reflected by the page header.
When a port is powered down for saving power, outgoing traffic is stored in a buffer until the port is powered up again. Because there are some overhead in turning the port down and up, more power can be saved if the traffic can be buffered up until a large burst of traffic can be transmitted. Buffering traffic will give some latency in the traffic. The EEE Port Sttings screens in Figure 4-3-18 & Figure 4-3-19 appear.
Figure 4-3-18 EEE Port Settings Page Screenshot
The page includes the following fields:
Object Description
• Port
Select port number from this drop-down list
Buttons
• Enable
Enable or disable the EEE function
99
: Click to apply changes.
Figure 4-3-19 EEE Enable Status Page Screenshot
The page includes the following fields:
Object Description
• Port
• EEE State
The switch port number of the logical port Display the current EEE state
100
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use