LLDP and LLDP-MED Configuration Examples
325
•
The lowest value voice VLAN ID that is enabled at the port will be used. If a voice VLAN is
not identified, LLDP-MED will not be advertised.
•
If the voice VLAN is assigned as "untagged", then the default priority is sent over
LLDP-MED. The DSCP information also uses the default value.
•
If the voice VLAN is identified as "tagged" then the QoS settings can come from one of the
following locations:
-
·through Policy Enforcement of a VLAN QoS Priority setting that applies to the
particular voice VLAN. The DSCP information will come from the default.
-
·through Policy Enforcement of a VLAN QoS DSCP setting that applies to the
particular voice VLAN. This also uses the DSCP Map to obtain Priority information, if
available.
The information in the remaining parts of this appendix provide more details on a number of
different network switch parameters that can be used to configure and adjust LLDP-MED values
for more custom operation.
QUICK START – GETTING LLDP-MED RUNNING QUICKLY
To get LLDP-MED working quickly, all that is required is to identify the appropriate VLAN with
the "voice" services as part of the normal switch configuration procedures. The example, below
uses VLAN 63, but this can be replaced with any valid VLAN ID value.
By default, LLDP and LLDP-MED are enabled, and default Priority and DSCP values are already
defined for voice services. All that is required is to identify the voice VLAN with "voice" service
and enable this at the required port.
LLDP-MED FOR NETWORK POLICY INFORMATION (VLAN & QOS)
For MiVoice IP Phones to be fully operational for QoS, three network policy parameters need
to be configured. These are:
•
VLAN ID
•
Layer 2 Priority (IEEE 802.1p) (CoS)
•
DSCP (Diff Serv Code Point)
This information can be learned from LLDP-MED compliant network switches.
To ensure that the correct settings are applied, use the following sequence of commands:
•
Define Voice VLAN and assigned ports.
•
Define DSCP to Priority Mapping (optional) or voice VLAN priority settings (optional).
•
Define QoS Policy Enforcement at the access port (optional).
•
Ensure that LLDP is enabled.
HP ProCurve Switch 5304XL(config)#
vlan 63 voice
Summary of Contents for MiVOICE BUSINESS
Page 1: ...Mitel MiVoice Business RELEASE 7 2 ENGINEERING GUIDELINES ...
Page 15: ...Chapter 1 ABOUT THIS DOCUMENT ...
Page 16: ......
Page 22: ...Engineering Guidelines 8 ...
Page 23: ...Chapter 2 SYSTEM OVERVIEW ...
Page 24: ......
Page 28: ...Engineering Guidelines 14 ...
Page 29: ...Chapter 3 TYPICAL CONFIGURATIONS ...
Page 30: ......
Page 73: ...Chapter 4 PHONES AND VOICE APPLICATIONS ...
Page 74: ......
Page 95: ...Phones and Voice Applications 81 Figure 9 ICP Connection Paths and Limitations ...
Page 100: ...Engineering Guidelines 86 ...
Page 101: ...Chapter 5 POWER ...
Page 102: ......
Page 128: ...Engineering Guidelines 114 ...
Page 129: ...Chapter 6 PERFORMANCE ...
Page 130: ......
Page 135: ...Chapter 7 APPLICATIONS ...
Page 136: ......
Page 142: ...Engineering Guidelines 128 ...
Page 143: ...Chapter 8 EMERGENCY SERVICES ...
Page 144: ......
Page 151: ...Chapter 9 IP NETWORKING ...
Page 152: ......
Page 167: ...Chapter 10 LICENSING ...
Page 168: ......
Page 183: ...Chapter 11 BANDWIDTH CODECS AND COMPRESSION ...
Page 184: ......
Page 209: ...Chapter 12 NETWORK CONFIGURATION CONCEPTS ...
Page 210: ......
Page 244: ...Engineering Guidelines 230 ...
Page 245: ...Chapter 13 NETWORK CONFIGURATION SPECIFICS ...
Page 246: ......
Page 309: ...Appendix A CAT 3 WIRING ...
Page 310: ......
Page 315: ...CAT 3 Wiring 301 Figure 55 CX MX MXe AX and LX Minimum Cable Standard ...
Page 316: ...Engineering Guidelines 302 ...
Page 317: ...Appendix B INSTALLATION EXAMPLES ...
Page 318: ......
Page 335: ...Appendix C LLDP AND LLDP MED CONFIGURATION EXAMPLES ...
Page 336: ......
Page 347: ...Appendix D VOIP AND VLANS ...
Page 348: ......
Page 353: ...Appendix E VOIP SECURITY ...
Page 354: ......
Page 381: ... ...