TECHNICAL COMMUNICATION No. TC0931 Ed.

01

OmniPCX Enterprise Nb of pages : 16 Date : 22 June 2007

URGENT

NOT URGENT TEMPORARY PERMANENT

SUBJECT: TFTP SERVERS REDUNDANCY SUPPORT ON IP TOUCH WITH AN EXTERNAL DHCP

SERVER

CONTENTS

1. HISTORY......................................................................................3

2. REFERENCES................................................................................3

3. GOAL ..........................................................................................3
3.1 OmniPCX Enterprise DHCP and TFTP servers ............................................ 3
3.2 External DHCP server ................................................................................ 4
3.3 Redundant TFTP server ............................................................................. 5
3.3.1 External TFTP server..........................................................................................5
3.3.2 TFTP servers hosted on the OmniPCX Enterprise CPUs......................................5

4. SOLUTION IMPLEMENTATION .....................................................5

5. EXAMPLES....................................................................................7
5.1 External TFTP servers ................................................................................ 7
5.2 Redundant OmniPCX Enterprise TFTP servers in Spatial Redundancy........ 7

6. DHCP SERVER CONFIGURATION EXAMPLES ................................8

6.1 Windows Server 2003 DHCP server .......................................................... 8
6.2 Linux ISC DHCP server ............................................................................ 14
6.3 Network trace ......................................................................................... 15

7. MINIMAL SOFTWARE VERSIONS ................................................16

1
 OmniPCX Enterprise
TFTP SERVERS REDUNDANCY SUPPORT ON
IP TOUCH WITH AN EXTERNAL DHCP
SERVER

1. HISTORY
Edition 1: Creation

2. REFERENCES
TC0601: Automatic Vlan Assignment (AVA) – Implementation guide and restrictions

3. GOAL
The goal of this document is to explain how to set up TFTP servers redundancy (for getting the
lanpbx.cfg configuration file) with IP Touch using an external DHCP server (not the OmniPCX
Enterprise DHCP server one).
It includes following cases:
• External TFTP servers (not the OmniPCX Enterprise TFTP servers) or
• OmniPCX Enterprise TFTP servers with spatial redundancy.

3.1 OmniPCX Enterprise DHCP and TFTP servers

OXE PBX OXE PBX

CPU 1 CPU 2
TFTP server redundancy when using
OmniPCX Enterprise DHCP and TFTP
servers is solved by using CPU
redundancy.

DHCP and TFTP DHCP and TFTP Each CPU will host a DHCP and a
TFTP server.
Only one DHCP server is active and
or
will provide to the phone the active
TFTP server address.

If a CPU is down, the other one takes

over (DHCP and TFTP server).

Ed. 01 / 22 June 2007 3 TC0931

 OmniPCX Enterprise
TFTP SERVERS REDUNDANCY SUPPORT ON
IP TOUCH WITH AN EXTERNAL DHCP
SERVER

3.2 External DHCP server

External First Second

DHCP external external If an external DHCP server (not the
server TFTP Server TFTP Server OmniPCX Enterprise DHCP server) is
used, this one can provide only one
TFTP server IP address to the IP Touch
using the siaddr field (aka next-
server).
siaddr = TFTP 1 ? It is impossible to provide the two
siaadr = TFTP 2 ? TFTP servers IP addresses.

Frame 229 (345 bytes on wire, 345 bytes captured)

Ethernet II, Src: 00:80:9f:33:3c:3a (00:80:9f:33:3c:3a), Dst: ff:ff:ff:ff:ff:ff
(ff:ff:ff:ff:ff:ff)
Internet Protocol, Src: 192.168.27.5 (192.168.27.5), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68)
Bootstrap Protocol
Message type: Boot Reply (2)
Hardware type: Ethernet
Hardware address length: 6
Hops: 0
Transaction ID: 0xb6b6699c
Seconds elapsed: 0
Bootp flags: 0x0000 (Unicast)
Client IP address: 0.0.0.0 (0.0.0.0)
Your (client) IP address: 192.168.27.29 (192.168.27.29)
Next server IP address: 192.168.27.5 (192.168.27.5)
Relay agent IP address: 192.168.27.5 (192.168.27.5)
Client MAC address: 00:80:9f:56:52:05 (00:80:9f:56:52:05)
Server host name not given
Boot file name not given
Magic cookie: (OK)
Option: (t=53,l=1) DHCP Message Type = DHCP Offer
Option: (t=54,l=4) Server Identifier = 192.168.27.5
Option: (t=51,l=4) IP Address Lease Time = 1 hour
Option: (t=1,l=4) Subnet Mask = 255.255.255.0
Option: (t=3,l=4) Router = 192.168.27.1
Option: (t=28,l=4) Broadcast Address = 192.168.27.255
Option: (t=43,l=15) Vendor-Specific Information
Option: (t=58,l=4) Renewal Time Value = 30 minutes
Option: (t=59,l=4) Rebinding Time Value = 52 minutes, 30 seconds
End Option

TC0931 4 Ed. 01 / 22 June 2007

 OmniPCX Enterprise
TFTP SERVERS REDUNDANCY SUPPORT ON
IP TOUCH WITH AN EXTERNAL DHCP
SERVER

3.3 Redundant TFTP server

The redundant TFTP severs may be external to the OmniPCX Enterprise or hosted on the redundant
OmniPCX Enterprise CPUs.
TFTP server redundancy is only supported by the IP Touch.
Old IP Phone models (eReflex, IP enabler) do not support it. In order for these old models to be able
to connect to the OmniPCX Enterprise (without redundancy), it is mandatory to use the next-server
field containing the main TFTP server IP address.

3.3.1 External TFTP server

If the TFTP servers have two different IP addresses, the external DHCP server has to provide both
addresses to the IP Touch.
The servers have also to host the lanpbx.cfg configuration file containing the OmniPCX Enterprise
CPU list.

3.3.2 TFTP servers hosted on the OmniPCX Enterprise CPUs

In case of simple redundancy (same main IP address for both CPUs), the external DHCP server has
to send only one IP address to the IP Touch (this main address). Thus, the next-server field will be
used.
In case of spatial redundancy (the TFTP servers have two different IP addresses), the external DHCP
server has to provide both IP address to the IP Touch.

4. SOLUTION IMPLEMENTATION
New proprietary sub options are added to Vendor-Specific information option 43 (which was used
today only for Automatic VLAN Assignation, aka AVA). These new sub options will be used to tell to
the IP Touch the two TFTP servers IP addresses.
Option 43 may contain following sub options:

Option Opcode Length (bytes) Content

AVA 58 (0x3A) 2 VLAN number
IP Touch TFTP1 64 (0x40) 4 Address IPv4
IP Touch TFTP2 65 (0x41) 4 Address IPv4
During the AVA step, sub option 64 and 65 are ignored.
Sub option 64 takes precedence over the next-server field.
Sub option 65 is used as secondary TFTP server address in addition to first TFTP server (sub option
64 or next-server).
The IP Touch will send two TFTP requests to both TFTP servers IP addresses.
First request is sent to first TFTP server (sub option 64 or next-server).
Second request is sent a little bit later to second TFTP server (sub option 65) if first TFTP server has
not sent any response to the first request.
First response is selected by the IP Touch.

Ed. 01 / 22 June 2007 5 TC0931

 OmniPCX Enterprise
TFTP SERVERS REDUNDANCY SUPPORT ON
IP TOUCH WITH AN EXTERNAL DHCP
SERVER

External First TFTP Second

DHCP server TFTP
server server OXE PBX OXE PBX
CPU 1 CPU 2

Main Stand-By

DHCP Discover

DHCP Offer

TFTP 1 / TFTP2

DHCP Request

DHCP Ack

TFTP1 / TFTP2

TFTP Request

lanpbx.cfg

TFTP Request

lanpbx.cfg

TFTP Data

lanpbx.cfg (CPU1 & CPU2)

TFTP Request

startnoe

TC0931 6 Ed. 01 / 22 June 2007

 OmniPCX Enterprise
TFTP SERVERS REDUNDANCY SUPPORT ON
IP TOUCH WITH AN EXTERNAL DHCP
SERVER

5. EXAMPLES

5.1 External TFTP servers

External TFTP 1 TFTP 2

DHCP server server
server

10.9.1.5 10.9.2.5

In its offer, the DHCP server will add Vendor-Specific information option 43 containing sub option
64 and 65:

2b 0c 40 04 0a 09 01 05 41 04 0a 09 02 05

Option 43 (0x2b), length 12 (0x0c)

First TFTP server IP address: sub option 64 (0x40), length 4, value 10.9.1.5

Seconf TFTP server IP address: sub option 65 (0x41), length 4, value 10.9.2.5

Each TFTP server will host lanpbx.cfg configuration file.

5.2 Redundant OmniPCX Enterprise TFTP servers in Spatial Redundancy

The configuration is the same as the one described in section 5.1 with filling as sub options 64 and
65 the OmniPCX Enterprise CPU IP addresses.

Ed. 01 / 22 June 2007 7 TC0931

 OmniPCX Enterprise
TFTP SERVERS REDUNDANCY SUPPORT ON
IP TOUCH WITH AN EXTERNAL DHCP
SERVER

6. DHCP SERVER CONFIGURATION EXAMPLES

6.1 Windows Server 2003 DHCP server

In this example we have two TFTP servers (172.26.165.152 and 172.26.165.151).
The DHCP server (172.26.165.152) provides to the IP Touch an IP address in the range
172.26.165.200 to 182.26.165.210 (network mask 255.255.248.0 and router 172.26.160.8).
• Add of a vendor class alcatel.noe.0.

TC0931 8 Ed. 01 / 22 June 2007

 OmniPCX Enterprise
TFTP SERVERS REDUNDANCY SUPPORT ON
IP TOUCH WITH AN EXTERNAL DHCP
SERVER

• Set predefined options TFTP1 and TFTP2

Ed. 01 / 22 June 2007 9 TC0931

 OmniPCX Enterprise
TFTP SERVERS REDUNDANCY SUPPORT ON
IP TOUCH WITH AN EXTERNAL DHCP
SERVER

TC0931 10 Ed. 01 / 22 June 2007

 OmniPCX Enterprise
TFTP SERVERS REDUNDANCY SUPPORT ON
IP TOUCH WITH AN EXTERNAL DHCP
SERVER

• Creation of a new scope

Ed. 01 / 22 June 2007 11 TC0931

 OmniPCX Enterprise
TFTP SERVERS REDUNDANCY SUPPORT ON
IP TOUCH WITH AN EXTERNAL DHCP
SERVER

• Configuration of the scope options

TC0931 12 Ed. 01 / 22 June 2007

 OmniPCX Enterprise
TFTP SERVERS REDUNDANCY SUPPORT ON
IP TOUCH WITH AN EXTERNAL DHCP
SERVER

Ed. 01 / 22 June 2007 13 TC0931

 OmniPCX Enterprise
TFTP SERVERS REDUNDANCY SUPPORT ON
IP TOUCH WITH AN EXTERNAL DHCP
SERVER

6.2 Linux ISC DHCP server

In this example, we have two TFTP servers (192.168.23.61 and 192.168.23.5).
The DHCP server (192.168.23.61) provides to the IP Touch an IP address in the range
192.168.26.201 to 192.168.26.205 (network mask 255.255.255.0 and router 192.168.26.1).
dhcpd.conf configuration file:

#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.sample
#

ddns-update-style ad-hoc;

class "Alcatel-Lucent_IPTouch" {
match if option vendor-class-identifier = "alcatel.noe.0";
}

subnet 192.168.26.0 netmask 255.255.255.0 {

option routers 192.168.26.1;

pool {
allow members of "Alcatel-Lucent_IPTouch";
next-server 192.168.23.5;
range 192.168.26.201 192.168.26.205;

if exists vendor-encapsulated-options {

ddns-updates off;

# Two TFTP servers: 192.168.23.61 & 192.168.23.5

option vendor-encapsulated-options 40:04:c0:a8:17:3d:41:04:c0:a8:17:05;

option server.default-lease-time 36000;

option server.max-lease-time 36000;
option server.min-lease-time 3600;
}
}

pool {
range 192.168.26.100 192.168.26.110;
next-server 192.168.23.5;
option server.default-lease-time 36000;
option server.max-lease-time 36000;
option server.min-lease-time 3600;
}
}

subnet 192.168.23.0 netmask 255.255.255.0 {

}

TC0931 14 Ed. 01 / 22 June 2007

 OmniPCX Enterprise
TFTP SERVERS REDUNDANCY SUPPORT ON
IP TOUCH WITH AN EXTERNAL DHCP
SERVER

6.3 Network trace

This is the trace of the example described at section 6.2.
The main TFTP server has been put out of service in order to see both TFTP requests to both TFTP
servers.

Ed. 01 / 22 June 2007 15 TC0931

 OmniPCX Enterprise
TFTP SERVERS REDUNDANCY SUPPORT ON
IP TOUCH WITH AN EXTERNAL DHCP
SERVER

In above trace, we can see:

• Frame n°16 IP Touch DHCP Discover request

• Frame n°20 DHCP server DHCP offer including option 43 providing the two TFTP servers
IP addresses (192.168.23.61 and 192.168.23.5),
• Frame n°30 IP Touch TFTP request (lanpbx.cfg) sent to first TFTP server (192.168.23.61),
• Frame n°31 Error message because first TFTP server is out of order
• Frame n°32 IP Touch TFTP request (lanpbx.cfg) sent to second TFTP server
(192.168.23.5)
• Frames n°33 to 36 TFTP exchanges between the IP Touch and the second TFTP server. The
phone receives the lanpbx.cfg file
• Frame n°38 IP Touch TFTP request (startnoe) sent to selected TFTP server (after analyze
of the lanpbx.cfg file)

7. MINIMAL SOFTWARE VERSIONS

TFTP server redundancy is taken into account by the IP Touch starting IP Touch binary 3.71.20
(3.76.20 for the Thales encrypted version). These binaries are embedded in the OmniPCX Enterprise
starting F5.401.18.a (R7.1) and G1.302.A (R8.0).

TC0931 16 Ed. 01 / 22 June 2007