GS-5220-Series (V4) User Manual
Table Of Contents
- 1. INTRODUCTION
- 2. INSTALLATION
- 3. SWITCH MANAGEMENT
- 4. WEB CONFIGURATION
- 4.1 Main Web Page
- 4.2 System
- 4.2.1 Management
- 4.2.1.1 System Information
- 4.2.1.2 IP Configuration
- 4.2.1.3 IP Status
- 4.2.1.4 Users Configuration
- 4.2.1.5 Privilege Levels
- 4.2.1.6 NTP Configuration
- 4.2.1.6.1 System Time Correction Manually
- 4.2.1.7 Time Configuration
- 4.2.1.8 UPnP
- 4.2.1.9 DHCP Relay
- 4.2.1.10 DHCP Relay Statistics
- 4.2.1.11 CPU Load
- 4.2.1.12 System Log
- 4.2.1.13 Detailed Log
- 4.2.1.14 Remote Syslog
- 4.2.1.15 SMTP Configuration
- 4.2.2 Simple Network Management Protocol
- 4.2.3 RMON
- 4.2.4 DHCP server
- 4.2.1 Management
- 4.3 Switching
- 4.3.1 Port Management
- 4.3.2 Link Aggregation
- 4.3.3 VLAN
- 4.3.3.1 VLAN Overview
- 4.3.3.2 IEEE 802.1Q VLAN
- 4.3.3.3 VLAN Port Configuration
- 4.3.3.4 VLAN Membership Status
- 4.3.3.5 VLAN Port Status
- 4.3.3.6 Private VLAN
- 4.3.3.7 Port Isolation
- 4.3.3.8 VLAN setting example:
- 4.3.3.8.1 Two Separate 802.1Q VLANs
- 4.3.3.8.2 VLAN Trunking between two 802.1Q aware switches
- 4.3.3.8.3 Port Isolate
- 4.3.3.9 MAC-based VLAN
- 4.3.3.10 Protocol-based VLAN
- 4.3.3.11 Protocol-based VLAN Membership
- 4.3.4 Spanning Tree Protocol
- 4.3.5 IGMP Snooping
- 4.3.6 MLD Snooping
- 4.3.7 MVR (Multicast VLAN Registration)
- 4.3.8 LLDP
- 4.3.9 MAC Address Table
- 4.3.10 Loop Protection
- 4.3.11 UDLD
- 4.3.12 GVRP
- 4.3.13 Link OAM
- 4.4 Routing
- 4.5 Quality of Service
- 4.6 Security
- 4.7 Power over Ethernet
- 4.8 Ring
- 4.9 ONVIF
- 4.10 Maintenance
- 5. SWITCH OPERATION
- 6. TROUBLESHOOTING
- APPENDIX A: Networking Connection
- APPENDIX B : GLOSSARY
User’s Manual of GS-5220 PoE Series Managed Switch
221
5. Streaming Video
6. Control / Signaling (conditionally support a separate network policy for the media types above)
A large network may support multiple VoIP policies across the entire organization, and different policies per application type.
LLDP-MED allows multiple policies to be advertised per port, each corresponding to a different application type. Different ports
on the same Network Connectivity Device may advertise different sets of policies, based on the authenticated user identity or
port configuration.
It should be noted that LLDP-MED is not intended to run on links other than between Network Connectivity Devices and
Endpoints, and therefore does not need to advertise the multitude of network policies that frequently run on an aggregated link
interior to the LAN.
Object Description
• Delete
Check to delete the policy. It will be deleted during the next save.
• Policy ID
ID for the policy. This is auto generated and shall be used when selecting the
polices that shall be mapped to the specific ports.
• Application Type
Intended use of the application types:
Voice - for use by dedicated IP Telephony handsets and other similar
appliances supporting interactive voice services. These devices are
typically deployed on a separate VLAN for ease of deployment and
enhanced security by isolation from data applications.
Voice Signaling (conditional) - for use in network topologies that
require a different policy for the voice signaling than for the voice
media. This application type should not be advertised if all the same
network policies apply as those advertised in the Voice application
policy.
Guest Voice - support a separate 'limited feature-set' voice service for
guest users and visitors with their own IP Telephony handsets and
other similar appliances supporting interactive voice services.
Guest Voice Signaling (conditional) - for use in network topologies
that require a different policy for the guest voice signaling than for the
guest voice media. This application type should not be advertised if all
the same network policies apply as those advertised in the Guest
Voice application policy.
Softphone Voice - for use by softphone applications on typical data
centric devices, such as PCs or laptops. This class of endpoints
frequently does not support multiple VLANs, if at all, and are typically
configured to use an 'untagged’ VLAN or a single 'tagged’ data specific
VLAN. When a network policy is defined for use with an 'untagged’
VLAN (see Tagged flag below), then the L2 priority field is ignored and