Alcatel OmniPCX Enterprise

802.1p/Q and VLAN

NOTE:

Product specifications contained in this document are subject to change

without notice. Products and services described in this document may not be
offered in every country. For the most current information, please contact
your Alcatel representative or your Alcatel equipment provider.

Copyright (c) 2006 Alcatel. All rights reserved for all countries. This
document may not be reproduced in whole or in part without the express
written permission of Alcatel.

Alcatel® and the Alcatel logo are registered trademarks of Alcatel. All other
trademarks are the property of their respective owners.

The CE mark indicates that this product conforms to the following Council
Directives:
- 89/336/CEE (concerning electro-magnetic compatibility)
- 73/23/CEE (concerning electrical safety)
- 1999/5/CE (R&TTE)
   


   

Chapter 1
Overview

 Overview .................................................................................................... 1.1

 Level 2 QoS: 802.1p/Q .......................................................................... 1.1
 Ethernet Header (802.1Q not used): RFC894 ............................................ 1.1
 Ethernet Header (802.1Q used) .................................................................. 1.1
 User priority (802.1p) ................................................................................... 1.2
 Level 3 QoS (IP) ...................................................................................... 1.3

Chapter 2
Configuration procedure

 Document purpose ................................................................................ 2.1

 Using the ToS / DiffServ field ............................................................. 2.1
 IP Quality of Service categories ................................................................. 2.1
 IP-Phones ..................................................................................................... 2.2
 Boards .......................................................................................................... 2.2
 INT-IP B board .............................................................................................. 2.2
 GD board ...................................................................................................... 2.3

Signaling TOS on hybrid link over IP ........................................................ 2.3
 802.1p/Q tagging ..................................................................................... 2.3
 Call Server .................................................................................................... 2.4


    0-1

   

 A4645 Voice Mail ......................................................................................... 2.5

 GD board ...................................................................................................... 2.6
 GA board ...................................................................................................... 2.6
 INT-IP B board .............................................................................................. 2.6

IP Phone ....................................................................................................... 2.7
 Configuration in the MAO ........................................................................... 2.8
 Example of operation .................................................................................. 2.9
 Summary ................................................................................................... 2.9
 TOS/Diffserv configuration ......................................................................... 2.9
 802.1p/Q configuration ............................................................................... 2.10

Chapter 3
VLAN description

 What is a virtual local area network (VLAN)? .............................. 3.1

 Types of VLANs ...................................................................................... 3.1
 VLAN for OmniPCX Enterprise IP devices .................................... 3.1
 802.1p and 802.1Q for OmniPCX Enterprise IP devices .......................... 3.1
 Implementation on IP-Phones .................................................................... 3.2

Chapter 4
VLAN (Configuration Example)

 First configuration ................................................................................. 4.1

 Switch configuration ................................................................................... 4.1
 Configuring IP equipment ........................................................................... 4.2
 Initializing the IP-Phone .............................................................................. 4.2
 After initializing the IP-Phone ..................................................................... 4.3
 Second configuration ........................................................................... 4.3
 Switch configuration ................................................................................... 4.4

0-2 
   
 
   

 Configuring IP equipment ........................................................................... 4.4

 Initializing the IP-Phone .............................................................................. 4.5
 After initializing the IP-Phone ..................................................................... 4.5
 Precedence .................................................................................................. 4.6
 Summary ................................................................................................... 4.6


    0-3

   

0-4 
   
 

1 

1.1 Overview
The Quality of Service allows flows on the data network to be assigned a priority. QoS applies
to:
- VoIP flows
- Signaling (ABC signaling on hybrid link, IP-Phone UA signaling, H.323 signaling between
gateways)
- Initialization (IP-Phone, GD and INT-IP B board download)
IP Quality of Service can be implemented at two levels:
- Level 2 QoS (Ethernet) or 802.1p/Q.
- Level 3 QoS (IP), using the ToS or DiffServ field.

1.2 Level 2 QoS: 802.1p/Q

Level 2 QoS is defined in the 802.1Q standard.
The 802.1Q standard provides a frame marking mechanism enabling network elements to be
classified according to the desired quality. This marking contains a certain number of data
items, concerning in particular frame priorities, which are defined in further detail in the
802.1p standard, and the VLAN number to which the station belongs. All this data allows the
quality of service for a specific flow to be improved.
When level 2 QoS is implemented, it must be implemented on all network equipment. This is
because a 4-byte field is added in the Ethernet frame header, which renders it incompatible
with the 802.3 or Ethernet standard.

1.2.1 Ethernet Header (802.1Q not used): RFC894

6 bytes 6 bytes 2 bytes

Destination address Originating address Ethertype field

1.2.2 Ethernet Header (802.1Q used)

802.1Q frames are marked with data items located in the Ethernet frame header just after the
MAC addresses.

          ! 1-1

Chapter 1   !

- TPID: Field indicating that the frame is 802.1Q marked. Field value is 8100 in hexadecimal
- TCI: Field described below:
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
User Priority CFI VID: VLAN Identifier

• User_priority: Frame priority (8 levels ). This field is defined by the 802.1p standard
• The CFI field (1 bit) indicates the presence of the RIF (Routing Information Field), used
for Token Ring frames transiting via an Ethernet network:
• 0 (default): RIF field absent.
• 1 : RIF field present.
• The VLAN Identifier field, on 12 bits (3 hexa digits), indicates VLAN No. Values 000,
001 and FFF are reserved. A VID at 0x000 indicates that the TCI field contains only
one priority data item (only 802.1p is used).

1.2.3 User priority (802.1p)

The User Priority field, on 3 bits, is described by the 802.1p standard, itself defined within the
802.1Q standard. It enables traffic management and control.
Eight classes of traffic are designed for this purpose.
- 0 to 3: low priorities.
- 4 to 7: high priorities.
table 1.3: 802.1p Classes of Traffic
Priority Type of traffic
0 Best Effort
1 Background
2 Spare
3 Excellent effort
4 Controlled Load
5 Video
6 Voice
7 Network Control

The IEEE provides the following description for the seven traffic levels:
- 0: Best Effort traffic: traffic carried without constraint.
- 1: Background traffic: traffic that can be carried on the network without any impact on users
and applications.
- 2: Reserved for future use.
- 3: Excellent Effort traffic: traffic carried with optimum effort.
- 4: Controlled Load traffic: major applications traffic.
- 5: Video traffic: traffic requiring a transmission delay lower than 100 ms.
- 6: Voice traffic: traffic requiring a delay and jitter lower than 10 ms.

1-2           !

   !

- 7: Network Control traffic: traffic required for network management.

1.3 Level 3 QoS (IP)

Level 3 QoS was planned from the start of the Ipv4 standard with ToS field, on 1 byte. This
field, which was not used for a long time because it was not actually needed, was replaced in
the standard by the DiffServ or DSCP (Differenciated Services Code Point) fields. This field
only uses the 6 first bits of the byte reserved for ToS:
0 1 2 3 4 5 6 7
DSCP Not used

          ! 1-3

Chapter 1   !

1-4           !

 

2
  

2.1 Document purpose

This document describes how to configure the QoS parameters of the various OmniPCX
Enterprise IP devices (equipment).

2.2 Using the ToS / DiffServ field

The ToS/Diffserv field value is managed by MAO. For IP-Phones and IP boards, management
is performed via Quality of Service categories.
For signaling on hybrid logical links over IP, the ToS value is managed separately.
For GD and INT-IP B boards, it is also possible to specify a priority level directly on the board.
This is used during board initialization to download binaries.

2.2.1 IP Quality of Service categories

The ToS field value is managed in the IP Quality of Service category (COS).
Object name: IP > IP Quality Of Service COS
Attributes:
IP QoS COS ID : Enter IP QoS COS number (between 0 and 15).
TOS/diffServ : This value must be specified by the person in
charge of the client network.
To calculate the value to be entered, the fact that
TOS value is coded on the first three most
significant bits of the TOS field, whereas Diffserv
occupies the first six bits of this field, must be taken
into consideration (see the examples below).

- Example 1 (TOS): in client routers/switches, the TOS field is to be used for VoIP flows,
and the value to be used is 5. This means that the "precedence" mechanism is used.
To obtain the value to be entered on the Call Server:
• Convert the hexadecimal value to binary: 5 : 101.
• As the precedence level is coded on the first 3 most significant bits of the TOS field,
add three zeros to the previous result, as follows: 101000.
• Convert 101000 into decimal : 40.
40 is thus the value to be entered in the TOS/diffServ attribute.
- Example 2 (Diffserv): in client routers/switches, the TOS field is to be used for VoIP flows
and the value to be used is B8. This means that the “Diffserv” mechanism is used.
To obtain the value to be entered on the Call Server:
• Convert the hexadecimal value to binary: B8 : 10111000.
• Since IP marking only uses the first 6 bits of the TOS field, remove the last 2 bits from
the previous result as follows: 101110.

""        #$ %&'($ $"' 2-1

Chapter 2 #$ %&'($ $"'

• Convert 101110 into decimal : 46.

46 is thus the value to be entered in the TOS/diffServ attribute.
Note: Whether TOS or Diffserv is used, the recommended value is 46.

2.2.2 IP-Phones
On IP-Phones, the Quality of Service COS is linked to the IP domain. The Quality of Service
COS previously modified must therefore be assigned to the IP domain of the IP-Phone.
Object name: IP > IP Domain
Attributes:
IP Domain Number : Enter the IP domain number of the IP-Phone.
IP Quality of service : Enter the number of the Quality of Service COS previously
modified.

2.2.3 Boards
For INT-IP A, INT-IP B, Call Server, GA, and GD boards, the Quality of Service is managed in
the Ethernet parameters of the board.
Object name: Shelf > Boards > Ethernet Parameters
Attributes:
Shelf Address : Enter shelf number.
Board Address : Enter board number.
IP Quality of service : Enter the number of the IP Quality Of Service COS
previously modified.

Note:
- For the Call Server, the Quality of Service COS number is managed in the Ethernet parameters of
the virtual INT-IP A boards, located in shelf 19, in positions 1 and 2.
- For A4645 voice mail, the Quality of Service COS number is managed on the Call Server in the
Ethernet parameters of the GD board, located in shelf 18, in position 0.

Caution: Changing the number of the IP Quality of service COS causes the board to be reset
automatically.

2.2.4 INT-IP B board

For voice calls and signaling, the values are managed via MAO, as described above.
To download binaries, it is possible to specify a TOS/Diffserv value directly on the INT-IP B
board when it is started:
- Start the board as described in the module ACT Media Gateway - Commissioning .
- Connect the 3BA 28112 cable to the front panel of the board.
- During the boot phase, press "Enter" to stop start-up and to access the IP configuration
menu of the board (this menu is used to specify the start mode of the board (static or

2-2 ""        #$ %&'($ $"'

 #$ %&'($ $"'

dynamic), to configure the IP parameters in static mode as well as the QoS parameters):
- Enter  to configure TOS/Diffserv (DSCP):

 
    
    
     
   !"   #$
    %#
&'    
    

- Save the configuration, then reset the board.

2.2.5 GD board
For voice calls and signaling, the values are managed via MAO, as described above.
To download binaries, it is possible to specify a TOS/Diffserv value directly on the GD board
before it is started:
- Either, by using the   command, while logged onto the board with the 
account:
Select &( )*+, , then #(
  - 
,
then reboot the board.
- Or, on one of the UA sets of a Media Gateway rack, if the GD board is started without an
IP connection cable to the LAN.

2.2.6 Signaling TOS on hybrid link over IP

Signaling on hybrid link over IP may include TOS information. TOS value is entered in the
parameter IP Tos Sig.
Object name: IP > IP Parameters
Attributes:
System Option : Select IP Tos Sig.
IP TOS Sig : Enter the TOS value (between 0 and 63) used for
signaling on hybrid links. The value to be entered
is the decimal value of the TOS coded on 6 bits.
Example: TOS value is 5:
- Converting this to binary gives 101
- On 6 bits, this gives 101000
- Converting this to decimal gives 40
Note: Default value: 46 (101110).
The meaning is:
- 3 most significant digits: Precedence (priority) = 5
- LowDelay bit: set
- Throughput bit: set
- Reliability bit: not set

2.3 802.1p/Q tagging

""        #$ %&'($ $"' 2-3

Chapter 2 #$ %&'($ $"'

802.1p/Q includes two Quality of Service principles, at level 2 (Ethernet):

- The tagging of the VLAN No., or VLAN ID (802.1Q).
- The priority field associated with VLAN (802.1p).
802.1p/Q tagging is managed by the MAO. For IP-Phones and IP and Call Server boards,
management is performed via Quality of Service categories.
For hybrid link over IP signaling, 802.1p/Q tagging is managed separately.
For devices that retrieve their IP address via DHCP (IP-Phones, GD, INT-IP B), for the DHCP
request to be tagged with the correct VLAN number, VLAN No. and priority information is
directly configurable on the devices.
From R5.1, a VLAN number may be configured in the parameters of each subnetwork on the
DHCP server: it is used by IP-Phones initializing via the DHCP server. This avoids having to
manually configure each set.
802.1p/Q configurations must be mutually consistent (i.e VLAN number must be the same).
The VLAN value must also be managed in the same way at the level of the switch port to
which the device is connected.

Figure 2.1: Example

2.3.1 Call Server

- 802.1p/Q activation and VLAN number management are performed by netadmin.
Caution 1:
• Enabling or modifying VLAN number may result in loss of the network, this should
therefore be done via V24 port and not via telnet.
• If the Call Server is duplicated, enabling or modifying VLAN number must be done
manually on both Call Servers. The netadmin Copy Setup menu must not be used.
Run the command   . , select %( /)*  /, then '(

2-4 ""        #$ %&'($ $"'

 #$ %&'($ $"'

/)* /
)*  
00000000000000000
  "  - &'(    1     // 2 
3  )* 4   .%5%6      $

- Priority level management is performed via MAO in the Ethernet parameters of the virtual
INT-IP A boards, (shelf 19, couplers 1 and 2).
Caution 2: If 802.1p/Q has not been activated by netadmin, priority level management via MAO
has no impact.
Operation
- Outgoing frames: when 802.1q tagging is enabled on the Call Server, outgoing frames are
tagged with the configured number.
- Incoming frames: all incoming frames are accepted, even if tagged with a different VLAN
number to that of the Call Server.

Figure 2.2: Example configuration

Frames leaving the Call Server have VLAN number set to 1, they are accepted by ports 2, 3
and 4 of the switch.
Frames leaving telephone equipment (GD board, IP-Phone) have VLAN number set to 2, they
are accepted by ports 1, 2 and 3 of the switch.
Frames leaving the PC do not have a VLAN number. When they reach the switch, they are
tagged with VLAN 4 (primary port VLAN) and thus accepted by port 1.
Conclusion: The Call Server can dialog with telephone equipment and the PC, but telephone
equipment cannot dialog with the PC.

2.3.2 A4645 Voice Mail

- If the voice mail service is on a dedicated CPU: activate 802.1p/Q and manage the VLAN
number by netadmin on this CPU.
Run the command   . , select %( /)*  /, then '(
/)* /

""        #$ %&'($ $"' 2-5

Chapter 2 #$ %&'($ $"'

)*  

00000000000000000
  "  - &'(    1     // 2 
3  )* 4   .%5%6      $

- Manage priority level on the Call Server via MAO in the Ethernet parameters of the GD
board, (shelf 18, coupler 0).
Caution: If 802.1p/Q has not been activated by netadmin, priority level management via MAO
has no impact.

2.3.3 GD board
- VLAN number management must be performed directly on the GD board before board
start-up:
• Either, by using the   command, while logged onto the board with the 
account:
Select &( )*+, , then '(
 -  ,
and, if necessary, %(
  .
Then reboot the board.
• Or, on one of the UA sets of the main shelf, if the GD board is started without an IP
connection cable to the LAN.
- A priority level can be managed directly on the GD board, by using one of the two methods
described above.
- A priority level can also be managed via MAO: this level applies after board start-up for
RTP/RTCP flows, Call Server/GD signaling, IP-Phones GD and H.323.

2.3.4 GA board
A Quality of Service COS number must be managed at the level of the board Ethernet
parameters, and a VLAN number as well as a priority level in this COS must be specified.

2.3.5 INT-IP B board

- VLAN number and, if necessary, priority level must be managed directly on the board
when it is started:
• Start the board as described in the module ACT Media Gateway - Commissioning .
• Connect the 3BA 28112 cable to the front panel of the board.
• During the boot phase, press "Enter" to stop the startup and to access board IP
configuration menu:
• Type  to configure VLAN number and priority:

2-6 ""        #$ %&'($ $"'

 #$ %&'($ $"'

 
         
&'         
     )  4   !"   %57     '
        !"   8     7

 -
,"
  -(
9+:,4,; 
   !   <   "
 
  "     " = 1

  "   7  =

- A Quality of Service COS number must also be managed at the level of board Ethernet
parameters and VLAN number and priority level in this COS must be specified.

2.3.6 IP Phone
- VLAN number can be configured in two ways:
• Dynamic start (dynamic allocation): VLAN number is directly assigned by the DHCP
server at set initialization.
Requirement:
• The set must be initialized in dynamic mode.
• VLAN number must be configured on the DHCP server : see module DHCP server
- Detailed description § Automatic VLAN Assignment (AVA) and module DHCP
server - Configuration procedure .
• The switches must accept untagged frames as, in this case, the DHCP request is
not tagged.
No operation is performed on the set.
• Static start (manual allocation): VLAN number is assigned in the supervisor menu at
set startup (only possible on IPTouch, IP-Phones V1S and V2 sets):
• To configure VLAN number on an IP Touch set:
1. At set initialization, successively press the [i] and # keys to access the
supervisor menu.
2. Select IP Parameters, then scroll down the list using the navigation key.
The following screen is displayed:
___change-begin___
___change-end___
""        #$ %&'($ $"' 2-7
Chapter 2 #$ %&'($ $"'

3. Select the Use Vlan box by pressing the corresponding dynamic key.
4. Enter the VLAN number below it.
5. If required, select the Strict VLAN box by pressing the corresponding dynamic
key.
6. Confirm by pressing the top left key.
• To configure VLAN number on an IP4035:
1. At set initialization, successively press the [i] or Menu key, then the # key to
access the supervisor menu.
2. Select 2. IP Parameters, then 7. Default VLAN.
By default, there is no managed VLAN, the display indicates: 1. tag disabled.
3. Enter 1.
4. Enter VLAN number (0 to 4095).
5. Confirm by pressing # (to cancel, press *).
The display indicates, for example:

6. Press 0 several times to exit the supervisor menu.

Note: Priority is not managed via the set menu as downloading does not have precedence over voice
frames.
- Priority level is configured via the MAO.

2.3.7 Configuration in the MAO

802.1Q tagging is managed in the MAO via Quality of Service COS. This setting is used by the
Call Server, the GA boards and also by remote devices (IP-Phones, INT-IP B et GD boards),
once they have been initialized.
2.3.7.1 IP Quality of Service COS
Object name: IP > IP Quality Of Service COS
Attributes:
IP QoS COS ID : Enter IP QoS COS number (between 0 and 15).
802.1Q Used : Select Yes to activate 802.1Q tagging.
802.1Q Priority : Enter the level of priority to be assigned to
datagrams using the access. Priority level is a
number between 0 and 7. Priority 0 is the lowest
priority. This value must be specified by the person
in charge of the client network.

2-8 ""        #$ %&'($ $"'

 #$ %&'($ $"'

VLAN ID : Enter the virtual LAN network identifier. Entering "0"

disables the VLAN mechanism. This value must be
specified by the person in charge of the client
network.
Note: For GD and INT-IP B boards, 802.1Q Priority and
VLAN ID are configured locally (directly on the boards).
For IP-Phones, VLAN ID is configured locally.

2.3.7.2 IP-Phones
On IP-Phones, the Quality of Service COS is linked to the IP domain. The Quality of Service
COS previously modified must therefore be assigned to the IP domain of the IP-Phone.
2.3.7.3 Boards
For INT-IP A, INT-IP B, Call Server, GA, and GD boards, the Quality of Service COS is
configured in the Ethernet parameters of the board.
Note:
- For the Call Server, the Quality of Service COS number is configured in the Ethernet parameters of
the virtual INT-IP A boards, located in shelf 19, in positions 1 and 2.
- For A4645 voice mail, the Quality of Service COS number is configured on the Call Server in the
Ethernet parameters of the GD board, located in shelf 18, in position 0.

Caution: Changing the number of the IP Quality of service COS causes the board to be reset
automatically.

2.3.7.4 Signaling on hybrid link over IP

For signaling on hybrid logical links over IP, priority value is managed separately.
Object name: IP > IP Parameters
Attributes:
System Option : Select 802.1Q Prio Sig Hyb.
802.1Q Prio Sig Hyb : Enter level of priority, between 0 and 7 (default
value: 0).

2.3.8 Example of operation

For an example of VLAN use with IP-Phones, see the module 802.1p/Q and VLAN - VLAN
(Configuration Example) .

2.4 Summary

2.4.1 TOS/Diffserv configuration

- Call Server: Manage a Quality of Service COS at the level of shelf 19, couplers 1 and 2.
Configure in this COS the TOS/diffserv field (recommended value: 46).

""        #$ %&'($ $"' 2-9

Chapter 2 #$ %&'($ $"'

- 4645 Voice mail: Manage a Quality of Service COS at the level of shelf 18, coupler 0.
Configure in this COS the TOS/diffserv field (recommended value: 46).
- GD Board:
• Configure TOS/Diffserv level via the mgconfig command (or via the UA set
configuration menu).
• Manage a Quality of Service COS in board Ethernet parameters. Configure the
TOS/diffserv field for this COS (recommended value: 46).
- GA Board: Configure a Quality of Service COS in board Ethernet parameters. Configure
the TOS/diffserv field for this COS (recommended value: 46).
- INT-IP A Board: Configure a Quality of Service COS in board Ethernet parameters.
Configure the TOS/diffserv field for this COS (recommended value: 46).
- INT-IP B Board:
• During the boot phase, configure the TOS/Diffserv level directly on the board, using the
 command.
• Configure a Quality of Service COS in board Ethernet parameters and configure the
TOS/diffserv field for this COS (recommended value: 46).
- IP-Phone: Configure a Quality of Service COS in the parameters of the domain assigned
to the board. Configure the TOS/diffserv field for this COS (recommended value: 46).
Note: For an IP board, the Quality of Service COS configured for the corresponding domain is not taken
into account. The COS used is that specified in board Ethernet parameters.

2.4.2 802.1p/Q configuration

- Call Server:
• Enable 802.1p/Q via netadmin.
• Configure VLAN number via netadmin.
• Repeat the operation on the duplicated Call Server.
• Configure a Quality of Service COS number in the Ethernet parameters of the INT-IP A
virtual boards (shelf 19, couplers 1 and 2), and configure the desired priority and VLAN
number for this COS.
- 4645 Voice mail:
• If the voice mail service is on a dedicated CPU, enable 802.1p/Q and configure VLAN
number for this CPU via netadmin.
• On the Call Server, configure a Quality of Service COS number at the level of shelf 18,
coupler 0; configure the desired priority and VLAN number for this COS.
- GD Board:
• Configure VLAN number and, if required, a priority level using the mgconfig command
(or via the configuration menu on a UA set).
• Configure a Quality of Service COS number in board Ethernet parameters and
configure VLAN number and priority level for this COS.
- GA Board:
• Configure a Quality of Service COS number in board Ethernet parameters and
configure VLAN number and priority level for this COS.
- INT-IP A Board:

2-10 ""        #$ %&'($ $"'

 #$ %&'($ $"'

• Configure a Quality of Service COS number at the level of the board Ethernet
parameters, and configure VLAN number and priority level for this COS.
- INT-IP B board
• During the boot phase, configure VLAN number and priority level using the 
command.
• Configure a Quality of Service COS number in board Ethernet parameters and
configure VLAN number and priority level for this COS.
- IP-Phone:
• For IP-Phones in dynamic initialization mode: configure VLAN number in DHCP server
parameters.
• For IP-Phones in static initialization mode: at set initialization, configure VLAN number
using the supervisor menu.
• Configure a Quality of Service COS number for the set's domain and configure VLAN
number and priority level for this COS.
Note: For an IP board, the Quality of Service COS configured for the corresponding domain is not taken
into account. The COS used is that specified in board Ethernet parameters.

""        #$ %&'($ $"' 2-11

Chapter 2 #$ %&'($ $"'

2-12 ""        #$ %&'($ $"'

 

3  

3.1 What is a virtual local area network (VLAN)?

A local network (LAN) is based on the broadcast principle. Any information transmitted by a
device connected to the LAN is received by all the others. When a large number of devices are
connected to the LAN, saturation occurs. The more stations there are, the greater the risks of
collisions.
Hence the "VLAN" concept, that allows the traffic on local networks to be restricted.
A VLAN represents a broadcast domain.
VLANs are thus logical groups of users or stations. All the members of a same VLAN are
authorized to inter-communicate and constitute the broadcast domain. Broadcast domains can
thus be configured within a switch without using routers (the advantage of the switch over the
router lies in the swift transmission of the frames). VLANs are independent from one another,
and can only be reached by routing (that is, by a router or switch/router).

3.2 Types of VLANs

There are several ways of managing VLANs:
- VLANs by port (level 1 of the ISO model).
They group systems according to the port on which they are connected. A given port of the
switch is associated with a given port number. The main disadvantage of this method is
that it does not allow user mobility without requiring VLAN reconfiguration by an
administrator. This is the type of VLAN that is described in the documentation.
- VLANs configured as lists of stations identified by their MAC address (level 2).
This is a more flexible approach, the lists allow you to specify the VLAN to which each
station belongs, whatever its "geographical" position in the network.
- VLANs by protocol type (level 2 of the ISO model). VLANs are specified using the
"Protocol type" field in the level 2 header.
Example 1: By IP protocol on one port and IPX on another port.
- VLANs by network address (level 3 of the ISO model).
This type of VLANs associate IP subnetworks with groups.
The main problem is slow packet transmission in relation to the use of MAC addresses.
- VLANs by service or application (level 4 or higher of the ISO model).
Example 2: Use tftp on one VLAN and telnet on another.
VLANs are defined by the 802.1Q standard developed by IEEE. This is a media access control
protocol. A switch is required to develop a VLAN.

3.3 VLAN for OmniPCX Enterprise IP devices

3.3.1 802.1p and 802.1Q for OmniPCX Enterprise IP devices

)*)         +" ($ 3-1

Chapter 3  +" ($

In order to have the frames marked from the beginning of the initialization process, a VLAN
(Virtual Local Area Network) number can be configured in the flash memory of IPTouch sets,
IP-Phones V2 e-Reflexes, TSC-IP V1S (Fast IP Enabler; reference: 4098 FRE), and also GD
and INT-IP B boards.
If marking has not been enabled in the flash memory of the IP devices 802.1p frames for
outgoing flows (signaling and voice) are only marked after initialization of the IP devices.
It is then the configuration settings made at PCX management level that are used.
On the PCX, 802.1Q activation and priority value are configured in IP categories of service.
The value of the category of service is entered:
- For an IP-Phone, in the parameters of the IP domain to which it belongs.
- For a board, in its Ethernet parameters.

3.3.2 Implementation on IP-Phones

The IP-Phones can send the following frames:
- Ethernet RFC 894: no managed VLAN-Id.
- With the 802.1Q field with a VLAN-Id equal to 0.
- With the 802.1Q field with a VLAN-Id other than 0.
3.3.2.1 VLAN marking
The VLAN number that is stored in the flash memory of an IP-Phone. It can be configured .
- In the set's supervisor menu: see the module 802.1p/Q and VLAN - Configuration
procedure § IP Phone
- For sets initializing dynamically, the VLAN number can also be assigned dynamically:
• As of R5.1, by the OmniPCX Enterprise DHCP server (see module 802.1p/Q and
VLAN - Automatic VLAN Assignment )
• As of R6.2, by an external DHCP server
Important: The VLAN cannot be configured in the flash memory of the TSC-IP V1s (IP Enabler;
Reference: 4098 RE).

Caution: The VLAN value configured on the PCX is not taken into account by IP phones.
Once marking has been enabled on the IP-Phone, this VLAN number is applied to any
outgoing traffic.
3.3.2.2 Strict VLAN
As of R6.1, strict VLAN can be configured on IP Touch sets.
The role of strict VLAN is presented in the table below:
Set configuration Outgoing frames Accepted incoming frames
- Use VLAN: yes Tagged with VLAN x - Frames with VLAN x
- VLAN ID: x - Frames with default VLAN
- Strict VLAN: no - Untagged frames

3-2 )*)         +" ($

  +" ($

Set configuration Outgoing frames Accepted incoming frames

- Use VLAN: yes Tagged with VLAN x - if x <> 0, frames with VLAN x
- VLAN ID: x - if x = 0, untagged frames
- Strict VLAN: yes

3.3.2.3 802.1.p marking

The priority (802.1p) cannot be specified at the level of the IP-Phone. The default value (0) is
used during initialization.
The PCX returns the 802.1 p information contained in the IP category of service associated
with the set. This information is only used after set initialization. It is not recorded in the
IP-Phone's flash memory.

)*)         +" ($ 3-3

Chapter 3  +" ($

3-4 )*)         +" ($

 

4  
  

The following two configurations aim to demonstrate the advantages of configuring VLANs on
a switch and at IP Phone level.
The switch is an Alcatel OmniStack 6024. On this switch, VLANs cannot be configured by
MAC address. The VLANs have therefore been configured by port. By default, all ports belong
to VLAN1, the default VLAN (PVID - Primary VLAN-ID) is configured at 1, and priority at 0. The
6024 is a level-2 switch (thus, no routing).
The 6024s are able to simultaneously receive and transmit marked (tagged) and
unmarked frames on the same port.
REMINDER OF THE FRAME MARKING RULE
Incoming traffic
When an unmarked frame or frame with VLAN number at 0 arrives on a port, it is processed
by the "X" PVID (Primary VLAN-ID) of the port. This means that the switch searches for the
destination port of this frame among those belonging to VLAN X.
Outgoing traffic
If the VLAN number of the frame that must exit a port of the switch is equal to the PVID of this
port, the frame is transmitted unmarked; otherwise, it is transmitted marked.

Note: The PCs used in the examples below are unmarked.

4.1 First configuration

The following configuration aims to demonstrate why different VLANs are configured on
the ports of a switch.

4.1.1 Switch configuration

)*)  *  , ( *   -#$ %&'($  . 4-1
Chapter 4  -#$ %&'($  .

Port 1 Port 4 Port 5 Port 7 Port 8

PVID 3 3 3 2 2
VLAN 3 3 3 2 2

4.1.2 Configuring IP equipment

The IP board and the IP-Phone are, by default, in "IP Domain" 0 related to "IP category of
service" 0.
Configuring QoS on the OmniPCX Enterprise:
Object name: IP > IP Quality Of Service COS
Attributes:
IP Quality Of Service COS : Enter IP quality of service category number
(between 0 and 15).
802.1Q Used : Yes (default value: no)
802.1Q Priority : 5 (default value = 7)
VLAN ID : (default value = 0)
TOS/diffServ : 0 (default value = 0)

No VLAN-Id has been configured on the IP-Phone.

The VLAN is managed by the switch (implicit marking) and not by the frame (explicit marking).

4.1.3 Initializing the IP-Phone

1. The IP-Phone attempts to reach its TFTP server. An ARP request is made by the IP-Phone
to obtain the MAC address corresponding to the IP address of the TFTP (broadcast)
server. The incoming frames on port 1 are not marked. Port 1 will mark them with its PVID
number, that is 3 (implicit marking). This ARP request is transmitted to all ports of the
switch that have a VLAN set at 3. In the example, this request is transmitted to ports 5 and
4; the VLAN number of the frame is equal to the PVID of ports 5 and 4: thus, outgoing
frames from ports 4 and 5 are not marked. Other devices - here the PCs - are not
needlessly affected by this request. They are connected to ports belonging to VLAN 2.
If all the ports of the switch were in the same VLAN-Id, this request would be carried out on
all the ports of the switch.
This first request already demonstrates the benefit of configuring VLANs on a switch: it
restricts the transmission of frames to a specific group.
2. The TFTP server answers (here, the Call Server).
The Call Server does not perform marking. Port 5, the port to which it is connected, will
mark this ARP request answer frame with a VLAN number corresponding to port PVID, i.e.
3. This frame, which is not a broadcast frame, is directly transmitted to port 1.
3. The IP-Phone sends TFTP requests to the Call Server in order to retrieve its 3 files
(lanpbx.cfg, bintscipS, starttscip). Its frames are directly sent to the port where the Call
Server is located. The Call Server response frames are directly sent to the port where the
IP-Phone is located.
4. The Call Server informs the IP board that the IP-Phone with address 10.30.4.50 is ready to

4-2 )*)  *  , ( *   -#$ %&'($  .
  -#$ %&'($  .

dialog with it.

5. The IP board makes an ARP request to obtain the MAC address corresponding to the IP
address of the IP-Phone. The incoming frames on port 4 are marked 0. The port marks
them with its PVID number, i.e. 3. This ARP request is transmitted to all the ports of the
switch with a VLAN set at 3. In the example, this request is sent to ports 5 (to which the
Call Server is connected) and 1 (to which the IP-Phone is connected). Other devices are
not needlessly affected by this request. The IP-Phone's response frame is directly sent to
the port of the IP board (as it is not a broadcast frame).
Note: The PCs cannot "ping" the IP devices of the OmniPCX Enterprise as the frames coming from
PC1 are not marked frames. Port 7, on which it is connected, will mark its frames with its PVID
number, i.e. 2. The switch sends the frames to the switch ports that have a VLAN number at 2. No
OmniPCX Enterprise IP device is connected to a port with VLAN number at 2. PC1 cannot dialog
with voice devices. It can only dialog with PC2, which is also connected to a port with a VLAN
number at 2.

4.1.4 After initializing the IP-Phone

Signaling between the IP board and the IP-Phone:
- Port 4 receives UDP frames marked with a VLAN at 0 and with an 802.1p field at 5 by the
IP board. Port 4 marks these frames with the PVID 3 and sends this marked frame to port
1 on which the IP-Phone is connected (it is not a broadcast frame, it is therefore directly
transmitted to the destination port).
- Port 1 receives UDP frames marked with a VLAN at 0 and with an 802.1p field at 5 by the
IP-Phone: this marking originates from the '"IP category of service" entered in the
OmniPCX Enterprise. Port 1 marks these frames with the PVID 3 and sends this marked
frame to port 4 behind which the IP board is connected (it is not a broadcast frame, it is
therefore directly transmitted to the destination port).
DIFFERENT VLANS CAN BE CONFIGURED ON A SWITCH TO RESTRICT BROADCAST
FRAMES TO A SPECIFIC GROUP. CONFIGURING VOICE AND DATA VLANS ENABLES
YOU TO COMPLETELY SEPARATE VOICE FLOW FROM DATA FLOW.

4.2 Second configuration

This configuration aims to demonstrate why VLAN numbers are configured on
IP-Phones.
We saw (above) that by configuring different VLANs on the ports of a switch, we could restrict
(at IP device initialization) the transmission of frames to a specific group.
Let us now connect a PC behind the IP-Phone located on port 1 of the switch

)*)  *  , ( *   -#$ %&'($  . 4-3
Chapter 4  -#$ %&'($  .

4.2.1 Switch configuration

Port 1 Port 4 Port 5 Port 7 Port 8

PVID 2 3 3 2 2
VLAN 2,3 3 3 2,3 2

4.2.2 Configuring IP equipment

By default, the IP board is in the "IP Domain" 0 related to the "IP service category" 0.
It is not possible to configure on the IP-Phone the VLAN number of the port of the mini switch
(integrated in the IP-Phone) that may be used by a PC. The voice flows and data flows will end
up in the same LAN.
If the data traffic from PCs must belong to a VLAN other than that used for IP-Phone voice
traffic:
- The first solution is to perform the marking at PC level.
It is then not necessary to configure a VLAN number on the IP-Phone.
The switch port will mark the frames from the IP-Phone with its PVID and will not modify
the marking of frames from the PC.
- However, in most cases, the PCs are not able to perform marking; therefore we need a
second solution. We need to configure a VLAN number at IP-Phone level.
Frames from the PC are marked with the PVID of the port to which the PC is connected
and are sent to all ports with a VLAN equal to this PVID.

4-4 )*)  *  , ( *   -#$ %&'($  .
  -#$ %&'($  .

Frames from the IP-Phone are marked "X" and sent to ports with a VLAN equal to "X".
In the example, since PC1 is not able to manage the 802.1q, marking is managed at the level
of the IP-Phone's flash memory. The configured value is equal to 3.
The 6024 receives on the same port:
- On the one hand, marked frames from the IP-Phone. This VLAN identifier is that which will
be used.
- And, on the other hand, non marked frames from the PC. These frame are then marked
with the switch port's PVID.

4.2.3 Initializing the IP-Phone

1. The IP-Phone attempts to reach its TFTP server.
An ARP request is made by the IP-Phone to obtain the MAC address corresponding to the
IP address of the TFTP (broadcast) server. The incoming frames on port 1 are marked with
VLAN number 3 and with priority 0. Port 1 broadcasts this ARP frame to all the ports of the
switch with a VLAN set at 3. In the example, this request is sent to ports 5 (to which the
Call Server is connected) and 4 (to which the IP board is connected).
Other devices - here the PCs - are not needlessly affected by this request.
2. The TFTP server answers (here, the Call Server).
The Call Server does not perform marking. Port 5, to which it is connected, will mark this
ARP request response frame with a VLAN number corresponding to the PVID of the port,
i.e. 3. This frame is not sent to all switch ports with a VLAN set at 3 (ports 1, 4 and 7), but
is directly sent to port 1. The marking of this frame arriving on port 1 is different from the
PVID of this port: the outgoing frame of port 1 is a marked frame.
3. The IP-Phone sends TFTP requests to the Call Server in order to retrieve its 3 files
(lanpbx.cfg, bintscipS, starttscip). Its frames are directly sent to the port where the Call
Server is located. The Call Server response frames are directly sent to the port where the
IP-Phone is located.
4. The Call Server informs the IP board that the IP-Phone with address 10.30.4.50 is ready to
dialog with it.
5. The IP board makes an ARP request to obtain the MAC address corresponding to the IP
address of the IP-Phone. The incoming frames on port 4 are marked 0 with priority 5. The
port marks them with its PVID number, i.e. 3. This ARP request is transmitted to all switch
ports with a VLAN set at 3. In the example, this request is sent to ports 5 (to which the Call
Server is connected), 1 (to which the IP-Phone is connected), and 7. Other devices are not
needlessly affected by this request. The IP-Phone's response frame is directly sent to the
port of the IP board (not to the Call server's port). This is due to the fact that it is not a
broadcast frame.
The PCs cannot "ping" the IP devices. This is because the frames from PC2 are not
marked frames. Port 7, to which it is connected, marks its frames with its PVID number, i.e.
2. The switch sends the frames to the switch ports with a VLAN number at 2, i.e. ports 1
and 8. Port 1 receives a frame marked 2, which corresponds to the number of its PVID: the
outgoing frame from port 1 is not a marked frame. The IP-Phone sends a response frame
marked 3 to port 1. This frame exits port 7 still marked 3. The PC does not understand
marked frames and will therefore reject them. On the other hand, the PCs can
intercommunicate.

4.2.4 After initializing the IP-Phone

)*)  *  , ( *   -#$ %&'($  . 4-5
Chapter 4  -#$ %&'($  .

Signaling between the IP board and the IP-Phone:

- Port 4 receives UDP frames marked 0 by the IP board. Port 4 marks these frames with the
PVID 3 and sends this marked frame to port 1 on which the IP-Phone is connected (it is
not a broadcast frame, it is therefore directly transmitted to the destination port).
- Port 1 receives UDP frames marked 3 by the IP-Phone. Port 1 sends this marked frame
directly to port 4 on which the IP board is connected (it is not a broadcast frame, it is
therefore transmitted directly to the destination port).
CONFIGURING A VLAN ON AN IP-PHONE ENABLES YOU TO SEPARATE THE VOICE
FLOW FROM THE DATA FLOW OF A PC CONNECTED BEHIND AN IP-PHONE (this is
meaningful only if the VLANs on the switches are configured by port and not by MAC
address).

4.2.5 Precedence
The priority bit on the 6024 can be managed by port. By default, it is set to 0.
The 6024 has two waiting queues in order to store slow traffic in a low priority queue while
urgent traffic transits via a higher priority waiting queue.
In the case of a PC connected behind an IP-Phone, the 6024 processes voice flow with priority
over data flow. Since the PC is not able to perform marking, the port processes its frames with
priority 0.
The IP-Phone marks its frames with the 802.1p field at 5 (according to the management
performed in the OmniPCX Enterprise).

4.3 Summary
DIFFERENT VLANS CAN BE CONFIGURED ON A SWITCH TO RESTRICT BROADCAST
FRAMES TO A SPECIFIC GROUP. CONFIGURING VOICE AND DATA VLANS ENABLES
YOU TO COMPLETELY SEPARATE VOICE FLOW FROM DATA FLOW.
CONFIGURING A VLAN ON AN IP-PHONE ENABLES YOU TO SEPARATE THE VOICE
FLOW FROM THE DATA FLOW OF A PC CONNECTED BEHIND AN IP-PHONE

4-6 )*)  *  , ( *   -#$ %&'($  .