TECHNICAL COMMUNICATION No. TC0601 Ed.

03

OmniPCX Enterprise Nb of pages : 22 Date : 06 November 2006

URGENT

NOT URGENT TEMPORARY PERMANENT

SUBJECT : AUTOMATIC VLAN ASSIGNMENT (AVA) IMPLEMENTATION GUIDE AND

RESTRICTIONS

Please find hereafter the documentation regarding the AVA feature (Automatic VLAN Assignment).

1
 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

Historic
Edition 1: Creation of the document
Edition 2:
3 : Adding of validated devices.
4.2 : Adding of a paragraph.
Adding of the 4.3 Configuration of the DHCP relay on the routers.

Edition 3 :
Global modification dealing with AVA on external DHCP (all chapters are concerned)

CONTENTS

1. AVA DESCRIPTION ......................................................................3

1.1. AVA sequence quick description ............................................................... 3
1.2. AVA sequence detailed description........................................................... 3
1.3. Network capture snapshots to illustrate the latest AVA mechanism .......... 5

2. RESTRICTIONS ...........................................................................10

3. AVA COMPATIBILITY..................................................................11

4. CONFIGURATION GUIDE ..........................................................11

4.1. Terminal configuration ........................................................................... 11
4.2. OmniPCX Enterprise configuration.......................................................... 11
4.3. Example of a Windows 2003 DHCP server configuration ........................ 15
4.4. Example of a DHCP ISC (Unix / Linux) server configuration .................... 16
4.5. Example of Alcatel router switch configuration (with Vlan Mobility) ........ 17
4.6. Example of Cisco router switch configuration ......................................... 18
4.7. Configuration of the DHCP relay on the routers ..................................... 18

Ed. 03 / 06 November 2006 1 TC0601

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

TC0601 2 Ed. 03 / 06 November 2006

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

1. AVA DESCRIPTION
The purpose of AVA is to avoid having to configure VLAN on the Alcatel IP terminals (IP Phones V2,
IP Touch). During the boot sequence the IP Phone gets its VLAN configuration and then performs a
DHCP request on this VLAN. This feature is based on DHCP protocol, and as a result the IP Phone
must be configured in dynamic mode.
The AVA feature is available in the OmniPCX Enterprise from Release 5.1 and works only with
eReflexes and IP Touch terminals (in this document, they will be called IP Phones).
From OmniPCX Enterprise Release 6.2, you can also configure AVA on an external DHCP (third
party DHCP).

1.1. AVA sequence quick description

During the initialization phase, the IP Phone asks for a VLAN ID on the native VLAN using DHCP
protocol.
The OmniPCX (or the external DHCP) replies with a DHCP offer, giving the VLAN ID and an IP
address taken from the IP address plan of the native VLAN, from which the DHCP request came.
If the AVA is managed on OmniPCX Enterprise, an IP address has to be reserved on each VLAN
in which at least one IP Phone makes an AVA request. If the AVA is managed on external DHCP,
an address of the range of native VLAN will be used.
The IP Phone then makes a second DHCP request on the VLAN (802.1Q tagged frames) using
the VLAN ID given.
The OmniPCX or third party DHCP server replies and gives an IP address on the VLAN in
question.

1.2. AVA sequence detailed description

Here is the detailed diagram of the AVA DHCP sequence. In this diagram the AVA DHCP server and
a non AVA DHCP server could be an OmniPCX Enterprise or an external DHCP server.

Ed. 03 / 06 November 2006 3 TC0601

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

DHCP Action
AVA DHCP
IP Phone
Servers
Non AVA
DHCP Server
DHCP Discover: IP Phone sends its first DHCP frame.

DHCP offer from non AVA DHCP server: If no other

frames are received within ten seconds, the offer will be
accepted and the process continues normally. The IP
Phone will not dialog with tagged traffic.
Note: If a third party DHCP server is used, the frame is
accepted only if the IP Phone is set in "dynamic" mode
and not "dynamic Alcatel" mode.
DHCP offer from AVA DHCP server: VLAN ID is
present in the offer. VLAN ID offer frames are received
by the IP Phone in priority.
DHCP Request: The IP Phone accepts the AVA offer.
Before version 3.17 / 3.60.72(1), the IP Phone tells the
other DHCP servers to release the IP address by
specifying the Call Server address which is in the Next
Server field. There will not be DHCP ACK.
DHCP ACK: The chosen DHCP server confirms the
allocated IP address (after 3.17 / 3.60.72(1))
DHCP Release : The IP Phone releases the address
which is useless, from the DHCP server.
Note: The "DHCP release" is only available from version
3.17 / 3.60.72(1) of IP Touch.
DHCP Discover: IP Phone executes a second discover
DHCP request, this one is in the tagged VLAN using the
previously given VLAN ID.
DHCP Offer from DHCP server which handles the IP
network (there can be one or more than one answer)
(the answer could have been made by the AVA Server).
DHCP Request: The IP Phone accepts the offer from
the server and tells the other DHCP servers it has made
a choice.
DHCP ACK: The chosen DHCP server confirms the IP
address allocated to the IP Phone.

TC0601 4 Ed. 03 / 06 November 2006

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

(1) Version 3.17 is available from version F3.301.22

Version 3.60.72 is available from version F4.401.19.b
CAUTION : If a set in 3.17 or 3.60.72 makes AVA requests on an OmniPCX Enterprise DHCP using
a version lower than F4.401.17, the OmniPCX Enterprise will not reply ACK and the IP Touch will not
restart.
Note: In versions 1.59 to 1.60, 2.55 and 3.12 to 3.14 of IP Touch, a "DHCP Decline" has been
introduced, it can raise problem in certain network architectures, this method was abandoned.

1.3. Network capture snapshots to illustrate the latest AVA mechanism

The following traffic capture snapshots show the AVA sequence in more detail. In these traffic
captures the following were used (see Figure 1):
One switch router which hosts and routes:
10.10.1.0/24 (on native VLAN 1)
10.10.3.0/24 (on native VLAN 3)
10.10.30.0/24 (tagged VLAN 30)
10.10.100.0/24 (on native VLAN 100).
All the router addresses are set at x.x.x.254 and they forward DHCP traffic to the DHCP servers
10.100.1.1.
One IP Phone on a switch port configured with native VLAN 3 (and IP address network
10.10.3.0/24) and tagged VLAN 30 (10.10.30.0/24).
One DHCP server 10.100.1.1 configured for AVA and for giving IP addresses of tagged
network.

Switch Router Configuration Layer 3 :

- Interface Vlan1: 10.10.1.254
- Interface Vlan3: 10.10.3.254 & DHCP Relay to 10.100.1
- Interface Vlan30: 10.10.30.254 & DHCP Relay to 10.100.1
- Interface Vlan 100: 10.100.1.253

OXE PBX 10.10.1.0/24

Port Switch 1 (Native Vlan 1)
10.10.30.0/24
IP : 10.10.1.20
(Taggued Vlan 30)

10.10.3.0/24 IP Phone
(Native Vlan 3 Port Switch 3
IP : DHCP

10.100.1.0/24
(Native Vlan 100) Switch Router Configuration Layer 2 :
- Port 1 : Native Vlan 1
- Port 2 : Native Vlan 100
- Port 3 : Native Vlan 3 & tagged vlan 30
DHCP and AVA server
Port Switch 2
IP : 10.100.1.1

Figure 1

Ed. 03 / 06 November 2006 5 TC0601

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

Complete sequence:

Frame No. 1 (DHCP Discover): IP Phone requests a VLAN Id

Vendor Specific
Information

TC0601 6 Ed. 03 / 06 November 2006

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

The equipment that is able to handle the AVA feature is identifiable by the presence of an explicit
request in the frame (Vendor Specific Information). Option 43 is used in this request.
Option 43 (0x2B) is also called "Encapsulate Vendor Options" described in RFC 2132.
This field is built as follows:

DHCP Option Option VLAN VLAN ID End of

VLAN Option
Option Length Length Value (1) Option
Value (hexa) 2B 5 3A 2 xxxx FF
Length (byte) 1 1 1 1 2 1

(1) VLAN ID value is set to "FFFF" for the VLAN request.

VLAN ID value is set to the VLAN number ID for an AVA DHCP server response.
Frame No. 2 (DHCP offer): DHCP offer by the AVA DHCP server

VLAN ID 0x001E (Vlan 30 in decimal)

(See above for the description)

Ed. 03 / 06 November 2006 7 TC0601

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

Frame No. 3 (DHCP Request): IP Phone accepts the DHCP offer

Frame No. 4 (DHCP ACK): DHCP server confirms the offer

Frame No. 5 (DHCP Release): IP Phone releases the IP address

This request is used to release from the DHCP server the IP address it used only to supply the VLAN
Id. Without this request, the addresses are not available during all the duration of the lease while
they are not used by the IP Touch

Frame No. 6 (DHCP Discover): Request an IP address on the tagged VLAN

802.1Q tagged frame: VLAN 30 which

was given by the AVA feature

TC0601 8 Ed. 03 / 06 November 2006

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

Frame No. 7 (DHCP Offer): Reply of the DHCP server on tha VLAN 30

802.1Q tagged frame: VLAN 30 which

was given by the AVA feature

IP address assigned to IP Phone

Frame No. 8 (DHCP Request) : The IP address assigned by the DHCP server is accepted
(communication still done on the tagged Vlan)

Frame No. 9 (DHCP ACK) : Confirmation from DHCP server (the IP address is assigned
permanently) (communication still done on the tagged Vlan)

Ed. 03 / 06 November 2006 9 TC0601

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

2. RESTRICTIONS
This feature is compatible with switches supporting untagged and 802.1Q tagged frames on the
same port and with routers supporting DHCP relay.
Network design restriction in implementing AVA: If non Alcatel switches are used, there must be
at least one source IP network per assigned voice VLAN: the VLAN request (using DHCP frames) is
coming from a IP subnetwork and only one VLAN can be configured and assigned per IP range.
Examples for a design based on non Alcatel switches
One native VLAN for one Voice VLAN: OK (Figure 2).
Two or more native VLANs for one Voice VLAN: OK in this case, there must be as many IP
scope setup as native VLANs in the DHCP server. In each of them, the option 43 will be
configured to assign the Vlan Id (Figure 2).
One native VLAN for two or more Voice VLAN: NOK (1) in this case, it is not possible to
differentiate between the DHCP source request and so to attribute the correct Voice VLAN Id
(Figure 3).
(1)
NOK for non Alcatel switches. For Alcatel switches handling the Vlan Mobile, this design
is also OK.

- Correct Network Design - - Bad Network Design -

Router with DHCP Forward to

AVA DHCP server and, if Router with DHCP Forward to
exists 3rd party DHCP Server 3rd paty DHCP Server AVA DHCP server and, if
exists 3rd party DHCP Server 3rd paty DHCP Server

OXE AVA DHCP Server

OXE AVA DHCP Server

IP Network D on Tagged Vlan Y IP Network E on Tagged Vlan Z

IP Network B on Tagged Vlan Y IP Network C on Tagged Vlan Z

IP Network A on IP Network B on native
Second DH

native Vlan V Vlan W

IP Network A on native Vlan X
request

Second DH

reques P

IP Network C on native
request
ue P

d DHC
req DHC

Vlan X
ue P
Second DHCP
CP

t
st

re q D H C

Firs quest
st

Switch supporting
request
st

ues CP

re

Secon
tD
Fir

reque P

CP

Tagged and Untagged Vlan

st
Fir eque

Switch supporting Tagged

H
HC

F ir
st

st D st

HC
t
D

and Untagged Vlan

First D

ond

P
HC
req
Sec

IP Phone booting in Native Vlan

V and next in Voice Vlan Y
IP Phone booting in Native Vlan
IP Phone booting in Native Vlan X X and next in Voice Vlan Y
IP Phone booting in Native Vlan W and next in Voice Vlan Z IP Phone booting in Native Vlan
and next in Voice Vlan Z X and next in Voice Vlan Z

Figure 2 Figure 3

TC0601 10 Ed. 03 / 06 November 2006

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

3. AVA COMPATIBILITY
Since the AVA feature is based on the DHCP protocol, it should work correctly on all network
equipment supporting the features described in paragraph 2 RESTRICTIONS and all third party
DHCP servers.
CAUTION
If AVA is implemented on an third party DHCP server and for IP Phone versions lower than 3.17
(F3.301.22 and below) or 3.60.72 (F4.401.19.b), the release problem of the IP addresses used for
the Vlan allocation is raised. Indeed if a minimal configuration is performed, the addresses used to
supply the Vlan Id are reserved on the server during all the duration of the lease, while they are not
really used. Certain DHCP servers (as ICS) allows to identify the requests resulting from Alcatel IP
Phone and to reduce the lease in some seconds for the addresses used to deliver the Vlan Id. If the
third party DHCP server does not allow such a management, the TFTP server address must be
configured at a different address then the DHCP server's one (we recommend to set up the Call
Server address). This configuration allows to set up the release mechanism of the addresses used for
the Vlan allocation.
There are no more problems from versions 3.17 for OmniPCX Enterprise R6.2 and 3.60.72 for
OmniPCX Enterprise R7.0.

4. CONFIGURATION GUIDE

4.1. Terminal configuration

To implement the AVA feature, the IP Phone must be configured in "dynamic" mode or "dynamic
Alcatel" mode. In "dynamic Alcatel" mode the IP Phone will ignore DHCP responses from third party
DHCP servers only for the first VLAN request (except if the external DHCP server is set up to allocate
Vlan), it means that even if "dynamic Alcatel" is set up on the IP Phone, it can obtain its definitive IP
address from a third party DHCP server.
To use the AVA feature, the IP Phone must use the "Tagged VLAN" option set to OFF in the IP
configuration menu.

4.2. OmniPCX Enterprise configuration

Using mgr or the OmniVista 4760 management tool, the AVA feature must be configured in the
DHCP configuration option.
To deliver a VLAN Id to the IP Phones, an IP range on the OmniPCX Enterprise must be created for
the native VLAN (from which the VLAN request will come from). This IP range must fit the IP network
of the native VLAN.
In the DHCP configuration/All sub network menu, create (if it does not exist) an IP range
with the following options (this IP range must fit the IP network (network and mask) from which the
DHCP VLAN requests will come from):
Specify the VLAN id to give to the IP Phone ("VLAN ID" option).

Ed. 03 / 06 November 2006 11 TC0601

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

Specify an IP address to be used during the VLAN attribution process ("VLAN address"). This
address is given to each IP Phone requesting a VLAN ID for RFC compatibility purposes but is
not used by the IP Phone. This address must be a free and valid address in the IP
subnetwork.
Note
Do not forget, if it's not already the case, to enable DHCP Server: in the DHCP Configuration set
the Configuration option to DHCP Server.
CAUTION
If OmniPCX Enterprise IP security is on (only declared Trusted hosts are authorized to access the
OmniPCX Enterprise), every router network IP address from which a DHCP request comes from, must
be declared in the "Trusted Hosts".

TC0601 12 Ed. 03 / 06 November 2006

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

Example of configuration via mgr

(In reference to the figure 1 regarding the IP addresses)

+-Select an object-----------------+

Shelf
Media Gateway
PWT/DECT System
System
Translator
Classes of Service
Attendant
Users
Users by profile
Set Profile
Groups
Speed Dialing
Phone Book
Entities
Trunk Groups
External Services
Inter-Node Links
X25
DATA
Applications
Specific Telephone Services
ATM
Events Routing Discriminator
Security and Access Control
IP
SIP +-Select an object--------+
-> DHCP Configuration +-All Subnetworks------------------+
Classes
Alcatel 8&9 Series
CPU Main Subnetwork Descend hierarchy

+----------------------------------+ -> All Subnetworks Review/Modify
Review/Modify Object profile
+-------------------------+ -> Create
Create Object Limit(s)
Modify
Modify Object Limits
Delete
Features

+----------------------------------+

Creation of the scope corresponding to non tagged network

+-Review/Modify: All Subnetworks-------------------------------------------------------+

Node Number (reserved) : 331
DHCP Configuration : 1

Subnetwork

Subnet address : 10.10.3.0
Subnet mask : 255.255.255.0

IP Phone will tag in this Vlan
Broadcast address : 10.10.3.255
Default router address : -----------------------------------------------
TFTP Server address : -----------------------------------------------
VLan ID : 30 IP address only used for the AVA
VLan Address : 10.10.3.100 transaction but not used by IP Phones

+--------------------------------------------------------------------------------------+

Ed. 03 / 06 November 2006 13 TC0601

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

In this case, it is not necessary to create a range of addresses or to specify a default router address
(except if OmniPCX Enterprise has to allocate addresses to the other equipment then the Alcatel IP
Phones). The TFTP server address is either not necessary because the IP Phone will not restart on this
network.

Creation of the scope corresponding to tagged Vlan

+-Review/Modify: All Subnetworks-------------------------------------------------------+

Node Number (reserved) : 331
DHCP Configuration : 1

Subnetwork

Subnet address : 10.10.30.0
Subnet mask : 255.255.255.0

Broadcast address : 10.10.30.255 No Vlan Id is specify
Default router address : 10.10.30.254
TFTP Server address : 10.10.1.10
VLan ID : ----
VLan Address : -----------------------------------------------

+--------------------------------------------------------------------------------------+

In this scope, you should specify the default router address and the TFTP address so that the IP
Phones recover the lanpbx.cfg.

Creation of the range of IP addresses used by IP Phones on the tagged Vlan

+-All Subnetworks------------------+

-> Descend hierarchy +-Select an object------+
Review/Modify
Review/Modify Object profile -> IP Address Range +-IP Address Range-----------------+
Create Static IP Address
Create Object Limit(s) Review/Modify
Modify +-----------------------+ Review/Modify Object profile
Modify Object Limits -> Create
Delete Create Object Limit(s)
Features Modify
Modify Object Limits
+----------------------------------+ Delete
Features

+----------------------------------+
+-Review/Modify: IP Address Range------------------------------------------------------+

Node Number (reserved) : 331
DHCP Configuration : 1

Subnetwork

Subnet address : 10.10.30.0
Subnet mask : 255.255.255.0

First address in range : 10.10.30.100

End of address range : 10.10.30.199

+ +

TC0601 14 Ed. 03 / 06 November 2006

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

4.3. Example of a Windows 2003 DHCP server configuration

(In reference to the figure 1 regarding the IP addresses).
Creation of the scope corresponding to non tagged network

For IP Phone versions lower than 3.16 or

3.60.72, you need to configure the options 66
and 67. The option 66 must not correspond to
the DHCP server address (we recommend to
set up the Call Server address) See the table above for the description of
the field: 3A 02 00 1E FF --> in red the
Vlan Id in Hexa: 1E = Vlan30

Creation of the scope corresponding to the tagged network

Do not forget to configure the TFTP server so that

the IP Phones can recover the lanpbx.cfg

Ed. 03 / 06 November 2006 15 TC0601

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

4.4. Example of a DHCP ISC (Unix / Linux) server configuration

(In reference to the figure 1 regarding the IP addresses).

class "Alcatel_IP Phone" {

match if option vendor-class-identifier = "alcatel.tsc-ip.0"
or option vendor-class-identifier = "alcatel.noe.0";
}

# IP Scope corresponding to the Untagged Vlan

subnet 10.10.3.0 netmask 255.255.255.0 {
option routers 10.10.3.254;

pool {
allow members of "Alcatel_IP Phone";
next-server 10.10.1.20;

# Only send the VLAN ID option for sets asking for it

if exists vendor-encapsulated-options {

# During Vlan id assignment phase IP Phone

# doesn't nead to be registerd in the DNS
ddns-updates off;

# Sending VLAN ID (0x1E ==> 30 in decimal)

option vendor-encapsulated-options 3a:02:00:1E:ff;

# To release addesses after assigning the VLAN ID (not

# necessary for the IP Phone release greater then 3.17 and 3.60.72)
option server.default-lease-time 30;
option server.max-lease-time 30;
option server.min-lease-time 30;
}
range 10.10.3.100 10.10.3.199;
}
}

# IP Scope corresponding to the Tagged Vlan

subnet 10.10.30.0 netmask 255.255.255.0 {
option routers 10.10.30.254;
pool {
allow members of "Alcatel_IP Phone";
next-server 10.10.1.20;
range 10.10.30.100 10.10.30.199;
}

TC0601 16 Ed. 03 / 06 November 2006

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

4.5. Example of Alcatel router switch configuration (with Vlan Mobility)

(In reference to the figure 1 regarding the IP addresses and Vlan Id).
In this case, we use an explicit Vlan (Vlan 33 ) which is used only for allocating the Vlan Id for AVA
and is not used by the other data equipment.
This mechanism allows to allocate different non tagged Vlan to IP Phones according to there Mac-
Address and thus avoid allocating tagged Vlan from the data Vlan. This design allows the voice Vlan
to be completely separated from the data architecture contrary to the other switches of the market.
Router part

vlan 1 router ip 10.10.1.254 255.255.255.0 e2

vlan 3 router ip 10.10.3.254 255.255.255.0 e2
vlan 30 router ip 10.10.30.254 255.255.255.0 e2
vlan 33 router ip 10.10.33.254 255.255.255.0 e2
vlan 100 router ip 10.100.1.254 255.255.255.0 e2

ip helper per-vlan only

ip helper address 10.100.1.1 vlan 3
ip helper address 10.100.1.1 vlan 30
ip helper address 10.100.1.1 vlan 33

Switch part

vlan 1 port default 1/1

vlan 100 port default 1/3

Port on which is connected the IP Phone

vlan 30 mobile-tag enable
vlan port mobile 1/2

Alcatel equipment will be switched to the non tagged vlan 33 while the other
equipment will be switched to the non tagged vlan 3
vlan 33 DHCP mac range 00:80:9F:00:00:00 00:80:9F:FF:FF:FF
vlan 3 DHCP port 1/2

Ed. 03 / 06 November 2006 17 TC0601

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

4.6. Example of Cisco router switch configuration

(In reference to the figure 1 regarding the IP addresses and Vlan Id).

Switch part

interface FastEthernet0/1
switchport access vlan 1

interface FastEthernet0/2
switchport access vlan 3
switchport voice vlan 30

interface FastEthernet0/3
switchport access vlan 100

Router part

interface Vlan1
ip address 10.10.1.254 255.255.255.0

interface Vlan3
ip address 10.10.3.254 255.255.255.0
ip helper-address 10.100.1.1

interface Vlan30
ip address 10.10.30.254 255.255.255.0
ip helper-address 10.100.1.1

interface Vlan100
ip address 10.100.1.253 255.255.255.0

4.7. Configuration of the DHCP relay on the routers

The DHCP relay feature (also known as "bootp forward" or "ip helper") must be set up on one or
more interface(s) of the router(s) if at least one DHCP server is not directly attached to the IP network
of the native VLAN or the IP network of the voice VLAN.
The following table describes the different possible cases:

TC0601 18 Ed. 03 / 06 November 2006

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

Role of each DHCP server: A DHCP server can be on native Vlans, on TheDHCP relay must be set up (if needed) on router
role shared between OXE tagged Vlan, or both (except OXE) or on an interfaces on native or tagged Vlans.
DHCP and third party DHCP other network. Configuration of the DHCP relay for the network
(4 scenarios) DHCP server(s) with network interface on: interface of the router on:
Native Vlan Voice Vlan Native Vlan Voice Vlan
Scenario I - - Relay to OXE DHCP Relay to OXE DHCP

Stand Alone OXE: OXE - - Relay to OXE DHCP

delivering VLAN Ids (AVA)
and IP addresses of IP - OXE Relay to OXE DHCP -
Phones
OXE OXE The OXE cannot belong to both Vlans

Scenario II - - Relay to OXE DHCP Relay to 3rd party DHCP

OXE delivering only the OXE - - Relay to 3rd party DHCP

VLAN Ids
3rd party - Relay to OXE DHCP Relay to 3rd party DHCP
Third party DHCP server
OXE, 3rd party - - Relay to 3rd party DHCP
delivering IP addresses only
for IP Phones but not for - OXE Relay to OXE DHCP Relay to 3rd party DHCP
other devices (PC, etc.)
- 3rd party Relay to OXE DHCP -

- OXE, 3rd party Relay to OXE DHCP -

OXE, 3rd party 3rd party - -

3rd party OXE, 3rd party Relay to OXE DHCP -

Scenario III Relay to OXE DHCP

- - Relay to 3rd party DHCP
Relay to 3rd party DHCP
Same case as the OXE - Relay to 3rd party DHCP Relay to 3rd party DHCP
previous one but the third
party DHCP server 3rd party - Relay to OXE DHCP Relay to 3rd party DHCP
delivering IP addresses also
for other devices (PC, etc.). OXE, 3rd party - - Relay to 3rd party DHCP
In this case, we assume that Relay to OXE DHCP
these devices are attached - OXE Relay to 3rd party DHCP
Relay to 3rd party DHCP
to the IP network of the Relay to OXE DHCP
native Vlan. - 3rd party -
Relay to 3rd party DHCP
Relay to OXE DHCP
- OXE, 3rd party -
Relay to 3rd party DHCP
OXE, 3rd party 3rd party - -

3rd party OXE, 3rd party Relay to OXE DHCP -

Scenario IV - - Relay to 3rd party DHCP Relay to 3rd party DHCP

3rd party - - Relay to 3rd party DHCP

Stand Alone third party
DHCP: delivering the Vlan - 3rd party Relay to 3rd party DHCP -
Ids (AVA) and IP addresses
of IP Phones (and possibly 3rd party 3rd party - -
other devices)

Ed. 03 / 06 November 2006 19 TC0601

 OmniPCX Enterprise
AUTOMATIC VLAN ASSIGNMENT (AVA)
IMPLEMENTATION GUIDE AND
RESTRICTIONS

TC0601 20 Ed. 03 / 06 November 2006