Avaya Application Solutions Deployment Manual page 403

8. Administer Option 66 (TFTP Server Name).
Note:
Microsoft DHCP servers support only dotted decimal format for TFTP addresses, not
Note:
symbolic names. Option 66 need not be used if the TFTP server is identified in the
Site Specific Option string (Option 176). However, to simplify configuration, we
recommend that you use Option 66. If you use both Option 66 and Option 176 to
identify TFTP servers, the values in Option 176 will override the values in Option 66.
9. Administer the IP Telephone-specific DHCP options specifying information, such as TFTP
server and DEFINITY C-LAN IP addresses. Use the site-specific option (SSON) at #176.
The value for this option should be set to either of the following strings:
MCIPADD=xxx.xxx.xxx.xxx,MCPORT=yyyy,TFTPSRVR=zzz.zzz.zzz.zzz,TFTPDIR=<
path>
or
MCIPADD={list of DNS names},MCPORT=yyyy,TFTPSRVR={list of DNS
names},TFTPDIR=<path>
Where xxx.xxx.xxx.xxx is one or more IP addresses for the C-LAN IP circuit pack, yyyy is
the C-LAN port (1719), zzz.zzz.zzz.zzz is one or more IP addresses for TFTP servers, and
<path> is the location of the location of the upgrade script and application files on the TFTP
server.
Each list can contain up to 127 total ASCII characters, with IP addresses separated by
commas with no intervening spaces, and with quotes on either end (see the example in the
NOTES below). If you use DNS, note that the system value DOMAIN is appended to the
hostname that you specify. If DOMAIN is null, the DNS names must be fully qualified. In
configurations where the upgrade script and application files are in the default directory, the
TFTPDIR=<path> should not be used. You do not have to use Option 176. For example, if
the DNS server is specified in Option 6, and the Domain Name is specified in Option 15,
you can use the configured names "AvayaTFTPServer" and "Avaya Call Server" for
TFTPSRVR and MCIPADD, respectively. The Call Server Name, TFTP Server Name, and
SMTP Server Name must each be no more than 32 characters in length. Examples of good
DNS administration include the following:
Option 6: aaa.aaa.aaa.aaa
Option 15: dnsexample.yourco.com
Option 66: tftpserver.yourco.com,zzz.zzz.zzz.zzz
Option 176: MCIPADD=xxxx.xxx.xxx.xxx
Depending on the DHCP application you choose, be aware of the fact that the application
most likely will not immediately recycle expired DHCP leases. An expired lease may remain
reserved for the original client for a day or more (for example, Windows NT DHCP reserves
expired leases for about 1 day). The intent of this reservation period is to protect a client's
lease in case the client and the DHCP server are in two different time zones, the computers'
clocks are not in sync, or the client is not on the network when the lease expires.
Issue 3.4.1 June 2005
DHCP
403