User's Manual
Table Of Contents
- 1. INTRODUCTION
- 2. INSTALLATION
- 3. SWITCH MANAGEMENT
- 4. WEB CONFIGURATION
- 4.1 Main Web Page
- 4.2 System
- 4.3 Port Management
- 4.4 Link Aggregation
- 4.5 VLAN
- 4.5.1 VLAN Overview
- 4.5.2 IEEE 802.1Q VLAN
- 4.5.3 Management VLAN
- 4.5.4 Create VLAN
- 4.5.5 Interface Settings
- 4.5.6 Port to VLAN
- 4.5.7 Port VLAN Membership
- 4.5.8 Protocol VLAN Group Setting
- 4.5.9 Protocol VLAN Port Setting
- 4.5.10 GVRP Setting
- 4.5.11 GVRP Port Setting
- 4.5.12 GVRP VLAN
- 4.5.13 GVRP Statistics
- 4.5.14 VLAN setting example:
- 4.6 Spanning Tree Protocol
- 4.7 Multicast
- 4.8 Quality of Service
- 4.9 Security
- 4.10 ACL
- 4.11 MAC Address Table
- 4.12 LLDP
- 4.13 Diagnostics
- 4.14 RMON
- 4.15 Power over Ethernet
- 4.16 Maintenance
- 5. SWITCH OPERATION
- 6. TROUBLESHOOTING
- APPENDIX A
- EC Declaration of Conformity
User’s Manual of LRP-822CS/LRP-1622CS
308
4.12.6 MED Network Policy
Network scovery enables the ry and diagnosis of mismatch issues with the VLAN configuration, along
r 2 and Layer et of specific protocol applications on that port. Improper
very hat frequently result in voice quality degradation
se with a network policy requirements, such as interactive
ervices.
ed are:
1. Layer 2 VLAN ID (IEEE 802.1Q-2003)
802
3. Layer 3 Diffserv code point (DSCP) value (IETF RFC 2474)
ork policy is potentially advertised and associated with multiple sets of application types supported on a given port.
The application types specifically addressed are:
1. Voic
2. Guest Voice
3. Softph
4. Video Conferencing
5. Streaming Video
6. Control / Signaling (conditionally support a separate network policy for the media types above)
A large network may support multiple VoIP policies across the entire organization, and different policies per application type.
LLDP-MED allows multiple policies to be advertised per port, each corresponding to a different application type. Different ports
on the same Network Connectivity Device may advertise different sets of policies, based on the authenticated user identity or
port configuration.
It should be noted that LLDP-MED is not intended to run on links other than between Network Connectivity Devices and
Endpoints, and therefore does not need to advertise the multitude of network policies that frequently run on an aggregated link
interior to the LAN.
The Voice Auto Mode Configuration, Network Policy Configuration and LLDP MED Network Policy Table screens in Figure
4-12-10 & Figure 4-12-11 appear.
Policy Di efficient discove
with the associated Laye 3 attributes, which apply for a s
network policy configurations are a significant issue in VoIP environments t
or loss of service.
Policies are only intended for u pplications that have specific 'real-time’
voice and/or video s
The network policy attributes advertis
2. Layer 2 priority value (IEEE .1D-2004)
This netw
e
one Voice