Engineering Guidelines
216
this range. As a general rule, VLAN 0 is treated in different ways by different vendors.
The recommendation is
not
to use VLAN 0. Cisco also reserves VLAN 1000 and
upward for Cisco purposes, so ensure there is not a conflict when using these higher
VLAN numbers.
•
Multi-VLAN port
-
Cisco devices provide this as another port configuration. However, on some of the
access switches it is not possible to use multi-VLAN ports and trunk ports on the same
unit. Unfortunately, the multi-VLAN port type is needed in order to work with other
vendor products. A trunk port can be used, but it also removes tagging from the
configured native VLAN, which may not be what is required. An example is a port
configured with the native_VLAN to 1. On ingress, tagging is added, but on egress it
is removed. Tagging information should be maintained through the network, only
being modified at the access points. Removing tagging between switches is not
desirable. There are two possible ways out of this situation:
a.
Run Cisco ISL between the two units (but then they both need to be Cisco).
or
b.
Create a dummy native_VLAN (tag native_VLAN) that is not used anywhere else
in the network to ensure compatibility with other vendor units and allow products
to be mixed. The dummy VLAN does not carry data since there are no end devices
configured with this VLAN. This effectively turns the trunk port into a multi-VLAN
port for the desired VLAN connections.
HP port examples
The HP switch uses a similar RS232 connection, but the user interface is more menu-driven
making the configuration more intuitive. The following figure shows a typical screen display.
Figure 31: HP Screen Display Example
The default_vlan is VLAN1. The VLAN numbers are assigned names to help follow which
function is assigned to which VLAN. The voice_vlan is VLAN2, the video_vlan is VLAN3, and
test4 is VLAN4. The default VLAN is used by the data devices and also by the IP phones when
they first start up and look for their correct VLAN configuration. (See the section “Startup
Sequence for Phones” on page 234.)
Содержание MiVOICE BUSINESS
Страница 1: ...Mitel MiVoice Business RELEASE 7 2 ENGINEERING GUIDELINES ...
Страница 15: ...Chapter 1 ABOUT THIS DOCUMENT ...
Страница 16: ......
Страница 22: ...Engineering Guidelines 8 ...
Страница 23: ...Chapter 2 SYSTEM OVERVIEW ...
Страница 24: ......
Страница 28: ...Engineering Guidelines 14 ...
Страница 29: ...Chapter 3 TYPICAL CONFIGURATIONS ...
Страница 30: ......
Страница 73: ...Chapter 4 PHONES AND VOICE APPLICATIONS ...
Страница 74: ......
Страница 95: ...Phones and Voice Applications 81 Figure 9 ICP Connection Paths and Limitations ...
Страница 100: ...Engineering Guidelines 86 ...
Страница 101: ...Chapter 5 POWER ...
Страница 102: ......
Страница 128: ...Engineering Guidelines 114 ...
Страница 129: ...Chapter 6 PERFORMANCE ...
Страница 130: ......
Страница 135: ...Chapter 7 APPLICATIONS ...
Страница 136: ......
Страница 142: ...Engineering Guidelines 128 ...
Страница 143: ...Chapter 8 EMERGENCY SERVICES ...
Страница 144: ......
Страница 151: ...Chapter 9 IP NETWORKING ...
Страница 152: ......
Страница 167: ...Chapter 10 LICENSING ...
Страница 168: ......
Страница 183: ...Chapter 11 BANDWIDTH CODECS AND COMPRESSION ...
Страница 184: ......
Страница 209: ...Chapter 12 NETWORK CONFIGURATION CONCEPTS ...
Страница 210: ......
Страница 244: ...Engineering Guidelines 230 ...
Страница 245: ...Chapter 13 NETWORK CONFIGURATION SPECIFICS ...
Страница 246: ......
Страница 309: ...Appendix A CAT 3 WIRING ...
Страница 310: ......
Страница 315: ...CAT 3 Wiring 301 Figure 55 CX MX MXe AX and LX Minimum Cable Standard ...
Страница 316: ...Engineering Guidelines 302 ...
Страница 317: ...Appendix B INSTALLATION EXAMPLES ...
Страница 318: ......
Страница 335: ...Appendix C LLDP AND LLDP MED CONFIGURATION EXAMPLES ...
Страница 336: ......
Страница 347: ...Appendix D VOIP AND VLANS ...
Страница 348: ......
Страница 353: ...Appendix E VOIP SECURITY ...
Страница 354: ......
Страница 381: ... ...