
Copyright © 2011, Juniper Networks, Inc. 13
APPLICATION NOTE - Deploying IP Telephony with EX Series Ethernet Switches
The configuration is performed as follows:
user@switch# set vlans voice-and-data vlan-id 100
user@switch# set interfaces ge-0/0/1 unit 0 family ethernet-switching port-mode
access
user@switch# set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan member
voice-and-data
user@switch# commit
Although this method is technically feasible, it is not a recommended configuration because placing both data and
voice traffic on the same VLAN leaves the voice traffic prone to potential jitter, delay and packet loss—conditions that
are introduced by “bursty” data traffic.
Using Trunk Port with Native-VLAN Option
Using a switch trunk port where the VoIP phone and endpoint host are connected will create the desired separation
between voice and data traffic, but it requires some additional configuration on both the switch and the VoIP phone.
Figure 13: Trunk port with Native-VLAN option
A sample trunk configuration is provided below:
Untagged VoIP VLAN 99
Non-LLDP-MED
Trunk Port with
Native VLAN-
VoIP VLAN
Data
VoIP
EX Series
user@switch# set vlans voip-only vlan-id 99
user@switch# set vlans data-only vlan-id 10
user@switch# set interfaces ge-0/0/1 unit 0 family ethernet-switching port-mode
trunk
user@switch# set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan member
[ voip-only ]
user@switch# set interfaces ge-0/0/1 unit 0 family Ethernet-switching native-
vlan-id data-only
user@switch# commit
Let’s look at this particular configuration in greater detail. Similar to the Voice VLAN feature, two VLANs are configured
here: voip-only and data-only.
user@switch# set interfaces ge-0/0/1 unit 0 family ethernet-switching port-mode
trunk
user@switch# set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan member
[ voip-only ]
Comentários a estes Manuais