VLAN (Virtual Local Area Network) is used to logically divide a physical network into several broadcast domains. VLAN membership can be configured through software instead of physically relocating devices or connections. VLANs address issues such as scalability, security, and network management. Routers in VLAN topologies provide broadcast filtering, security, address summarization, and traffic-flow management. By using VLANs, one can control traffic patterns and react quickly to relocations. VLANs provide the flexibility to adapt to changes in network requirements and allow for simplified administration.
IEEE 802.1Q is the networking standard that supports VLANs on an Ethernet network. The specification defines a standard method for tagging Ethernet packets with VLAN membership information. Portions of the network which are VLAN-aware (i.e., IEEE 802.1Q conformant) can include VLAN tags. Traffic on a VLAN-unaware (i.e., IEEE 802.1D conformant) portion of the network will not contain VLAN tags. When a frame enters the VLAN-aware portion of the network, a tag is added to represent the VLAN membership of the frame's port or the port/protocol combination, depending on whether port-based or port-and-protocol-based VLAN classification is being used. Each frame must be distinguishable as being within exactly one VLAN. A frame in the VLAN-aware portion of the network that does not contain a VLAN tag is assumed to be flowing on the native (or default) VLAN.
802.1Q adds a 4-byte tag between the source MAC address and the Ethernet type fields of the Ethernet frame. Two bytes are used for the tag protocol identifier (TPID), the other two bytes for tag control information (TCI). The TCI field is further divided into PCP(Priority Code Point), CFI (Canonical Format Indicator), and VID (VLAN ID).
As voice traffic is delay and jitter sensitive for the IP phone, it requires higher priority over data traffic to reduce delay and packet loss during transmission. To simplify configuration procedures and better manage voice transmission policies, the connected switch can be configured to provide voice VLAN function and transmit the voice traffic of the IP phone in a dedicated VLAN, called voice VLAN.
Voice VLAN is a special access port feature of the switch which allows IP phones to be automatically configured and easily associated with a logically separate VLAN. This feature provides various benefits, but one particular benefit is that when voice VLAN is enabled on a switch port, this port is also enabled to allow simultaneous access for a PC.
This feature allows a PC to be daisy chained to an IP phone and the connection for both PC and IP phone to be trunked through the same physical Ethernet cable.The purpose of VLAN configurations on the IP phone is to insert tag with VLAN information to the packets generated by the IP phone. When VLAN is properly configured for the ports (Internet port and PC port) on the IP phone, the IP phone will tag all packets from these ports with the VLAN ID. The switch receives and forwards the tagged packets to the corresponding VLAN according to the VLAN ID in the tags described in IEEE Std 802.3.
VLANs offer many benefits that are not found in typical LANs. Major benefits of segregating IP phones into VLAN(s) are listed as below:
There are three ways to get VLAN ID for Internet (WAN) port, but the VLAN used is chosen by priority of each method. The priority is:
LLDP (Link Layer Discovery Protocol) allows Ethernet network devices to receive and/or transmit device-related information to directly connected devices on the network that are also using the protocol, and store the information that is learned about other devices. Information gathered with LLDP is stored in the device as a management information database (MIB) and can be queried with the Simple Network Management Protocol (SNMP) as specified in RFC 2922. LLDP transmits information as packets called LLDP Data Units (LLDPDUs). An LLDPDU consists of a set of Type-Length- Value (TLV) elements, each of which contains a particular type of information about the device or port transmitting it.
Each of the TLV components has the following basic structure:
Type | Length | Value |
---|---|---|
7 bits | 9 bits | 0 - 510 octets |
LLDP supports advertising the following TLVs:
The LLDP frame ends with a special TLV, named end of LLDPDU in which both the type and length fields are 0.
LLDP -MED (Media Endpoint Discovery) is published by the Telecommunications Industry Association (TIA). It is an extension to LLDP that operates between endpoint devices and network connectivity devices. LLDP -MED specifically provides support for voice over. IP (VoIP) applications and provides the following capabilities:
In addition to the TLVs advertised by LLDP, LLDP -MED also supports advertising the following TLVs:
It should be noted that either LLDP or LLDP -MED—but not both—can be used at any given time on an interface between two devices.
LLDP provides exceptional interoperability benefits, IP telephony troubleshooting, automatic deployment of policies and advanced PoE (Power over Ethernet). When LLDP feature is enabled on IP phones, the IP phones periodically advertise their own information to the directly connected LLDP -enabled switch. The IP phones can also receive LLDP packets from the connected switch. When the application type is "voice", IP phones decide whether to update the VLAN configurations obtained from the LLDP packets. When the VLAN configurations on the IP phones are different from the ones sent by the switch, the IP phones perform an update immediately. This allows IP phones to be plugged into any switch, obtain their VLAN IDs, and then start communications with the call control.
TLVs supported by IP phones are summarized in this table:
TLV Name | TLV Type | Description |
---|---|---|
Mandatory TLVs | Chassis ID | Specifies the IP address of the sending port. |
Port ID | Specifies the MAC address of the IP phone. | |
Time To Live | Specifies the life of the transmitted information on the IP phone. The default value is 180 seconds. | |
End of LLDPDU | Marks the end of the TLV sequence in the LLDPDU. No further processing of TLVs after this is necessary. This is a mandatory TLV and therefore must be present at the end of the data stream. | |
Optional TLVs | System Name | Specifies the administratively-assigned name for the IP phone The default value is "UCxxx". |
System Description | Specifies the description of the IP phone. The default value is IP Phone. | |
System Capabilities | Specifies the supported and enabled capabilities of the IP phone. The supported capabilities are Bridge, Router and Telephone. The enabled capabilities are Bridge and Telephone by default. | |
Port Description | Specifies the description of the sending port. The default value is "WAN PORT". | |
IEEE Std 802.3 Organizationally Specific TLV | MAC/PHY Configuration/Status |
Specifies duplex and bit rate settings of the IP phone. The Auto Negotiation is supported and enabled by default. The advertised capabilities of PMD Auto-Negotiation are: 100BASE-TX (full duplex mode) 100BASE-TX (half duplex mode) 10BASE- T (full duplex mode) 10BASE- T (half duplex mode) |
LLDP -MED TLVs | Media Capabilities |
Specifies the MED device type of the IP phone and the supported LLDP -MED TLV type can be encapsulated in LLDPDU. The supported LLDP -MED TLV types are:
|
Network Policy | Specifies the port VLAN ID, application type, L2 priority and DSCP value. | |
Extended Power-via-MDI | Specifies power type, source, priority and value. | |
Inventory – Firmware Revision | Specifies the firmware revision of IP phone. | |
Inventory – Serial Number | Specifies the serial number of IP phone. | |
Inventory – Manufacturer Name | Manufacturer name of IP phone. |
LLDP is disabled on IP phones by default. You can configure LLDP via web interface, phone interface or using the configuration file. You can also configure the sending frequency of LLDP packet. The default sending frequency is 120s.
To configure LLDP feature via web interface:
To configure LLDP feature via phone interface:
After LLDP feature is enabled, the IP phone performs the following:
The following figure shows the LLDP packets sent and received by the IP phone, each packet contains multiple TLVs.
IP phones support VLAN discovery via DHCP. When the VLAN Discovery method is set to DHCP, the IP phone will detect DHCP option for a valid VLAN ID. The predefined option 132 is used to supply the VLAN ID by default. You can customize the DHCP option used to detect the VLAN ID. Besides, you can use the DHCP option 133 to get the 802.1p priority of VLAN. In addition, we also support configure multiple configurations with only one option. Option 43 is a comprehensive configuration item. You can put option 132, option 133 and so on into it. The IP Phone will get the information you configured from option 43. The specific configuration method will be described in detail later.
Before using DHCP VLAN feature on IP phones, you must make sure that the DHCP option on the DHCP server is configured properly. This section provides instructions on how to configure a DHCP option for windows using an application that provides TFTP and DHCP services installed on your computer (e.g. Tftpd32).
To configure DHCP option 132 using Tftpd32:
DHCP VLAN is disabled on IP phones by default. The DHCP option is 132.
To configure DHCP VLAN feature via web interface:
To configure DHCP VLAN feature via phone interface:
When the IP phone is configured to use DHCP for VLAN discovery, and the DHCP option is set to 132, the following processes occur:
The following figure shows the DHCP messages sent and received by the IP phone:
You can configure this option the same way as option 132, this option contains the WAN Port priority. When you configure this option on the server, and change the state of DHCP Vlan to enable, you can see the priority you set in the web interface.
You can configure this option the same way as option 132. This option mainly introduces the data format. Because this option can contain multiple configurations, some special formatting is required when configuring the data to distinguish between the various configurations.
Suppose you want to configure the option 132 and option 133 together, the data format for each option is as follow:
OPTION ID + ( Length of configuration (Bit) +1 ) + configuration + 00
To configure the option 132 as 31, the data is:
132 + 3 + 31 + 00
where
The data type of option 43 is hexadecimal, so we need to make some changes to the above data.
Original | Hexadecimal |
---|---|
132 (integer) | 84 |
3 (integer) | 03 |
31 (string) | 3331 |
00 (hexadecimal) | 00 |
The data to configure option 132 as 31 will look like this:
84 03 33 31 00
Using the same method as above, we now calculate the data to configure option 133 as 5.
Start off with the data value:
133 + 2 + 5 + 00
Next, change the data to hexadecimal
85 02 35 00
The data for option 132 and option 133 can now be put together as:
84 03 33 31 00 85 02 35 00
Now the option 43 contains information for both option 132 and 133. when the IP phone gets the data for option 43, it knows the option 132 is 31 and option 133 is 5.
Except for options 132 and 133 above, option 43 also supports option 66, 67 128 and 150.
Option 43 has the highest priority. If you have configured both options 43 (contains option 132,133,66,67,128,150) and 132,133,66,67,128,150 at the same time. The configuration will be based on option 43.
When using Bridge Mode, PC Port VID is supported. When your PC is connected to LAN Port, data (from your PC to switch) will be tagged with " PC Port VID ".
Network -> Advanced page
With the above configuration, VOIP (SIP RTP) packets sent from the device will be tagged with VLAN ID 66, data packets sent from your PC to switch will be tagged with VLAN ID 18.
Or with the above configuration, VOIP (SIP RTP) packets sent from the device will be tagged with VLAN ID 66, while data packets sent from your PC to switch will be tagged with UNTAG VLAN ID.
When using NAT mode, VLAN ID is port based, you cannot set Data VLAN ID. If the VLAN ID arranged for the device is 66, then the VLAD ID must be set to the same value.
Network -> Advanced page
In this case, all ethernet packets sent out from the device will be tagged with VLAN ID 66.