
Local Area Network (LAN) Architecture
Page 25 of 51
VLAN Switch and Phone Configuration for Network 3.1
When Network Design 3.1 is used as a deployment solution, special consideration will
need to be applied to the configuration of the SIP devices as well as the LAN switch. Network
3.1 is based-upon the use of VLAN tagging, or 802.1q. This allows for the ability to connect 2
IP devices ( for example, a PC and an IP phone) to the same physical Cat-5 cable but logically
separate traffic onto 2 unique IP subnets. By doing this, separate routing and security can be
applied to each IP subnet. So, of particular concern is that the LAN switch utilized is able to
support the use 802.1q VLAN technology.
VOIP2320 has not chosen to require the use of
specific VLAN switch equipment, however this functional will need to be available when using
this network design.
VLAN tagging uses the insertion of an ancillary header in the Ethernet frame that
identifies the appropriate VLAN to associate a packet to. The IEEE has defined an optional
tag for 802.x networks which can convey additional Layer 2 information. This four-byte tag is
inserted between the MAC addresses and Ethertype fields of the Ethernet frame, and the
Maximum Transmission Unit (MTU) of a tag-enabled interface is increased by four so that the
use of tags does not cause a decrease in the MTU available to Layer 3 protocols (such as IP).
The first two bytes of the tag are statically defined to the Ethertype for tags, so that tagged
frames can be distinguished from untagged frames. Twelve bits optionally encode a VLAN
number (0-4095), and three bits encode the QoS value (0-7). Each Ethernet link has a “native
VLAN” which is assumed for all frames which do not have a tag or which have a VLAN number
of 0 in the tag.
So when configuring the 3.1 Network for the first time, before the phones and PCs will
properly function you will need to verify that the proper VLAN configurations are setup in your
phones and VLAN switch. First, the phones will need to be setup to function on VLAN ID #1,
as it is defined as the Voice VLAN. Secondly, because the PCs generally will not support
VLAN tagging your switch will need to be setup to default untagged packets to the Data VLAN
assignment of VLAN ID #500. Lastly, you will need to create a VLAN trunk port on your switch
to aggregate traffic back to the EdgeMarc. This port will need to be associated with all 3
VLANs, #1-Voice, #500-Data & #600
VOIP2320 (if applicable).
Pre-Configuration Requirements for Network 3.1
• Phones need to be setup to VLAN ID #1
• VLAN Switch needs to default Untagged Packets to VLAN ID #500 for all PCs
connected to it.
• Configure a VLAN trunk port on your switch. Assign to VLAN #1, #500, and
#600(if applicable). All VLANs packets should be tagged on the VLAN Trunk
port. Connect this switch port to physical LAN port #1 of the EdgeMarc.
Comentarios a estos manuales