IMG 1010 - Sample dhcpd.conf
- Kelli Higdon
Â
The following is a sample dhcpd.conf file. To create the dhcpd.conf file, run the xldhcp script located in /opt/dialogic/common/osconfig and then transfer this file to the /etc or /etc/dhcp directory (depending on OS version). If the xldhcp file is not available, modify the existing dhcpd.conf file manually. The lines in the dhcpd.conf need to be modified to equal your particular network settings.
#################################################################
# File: dhcpd.conf
# Generated by: xldhcp Revision: 1.4
# Dialogic Corporation, Inc. 11/11/09_09:13:42
# Customer Technical Support: www.dialogic.com
#################################################################
ddns-update-style ad-hoc;
# which logfile group... log to /var/log/messages
LogFile = messages;
allow bootp;
# declare global vender options
option Host_1010_Flag code 134 = signed integer 32;
option Host_1004_Flag code 134 = signed integer 32;
#Calculate boot flag by adding values based on desired system attributes
#For a T1 system: add 0
#For a E1 system: add 2
#To boot from FTP server: add 0
#To boot from SD Card: add 32
#For LBR Codecs (512 ch/mod): add 0
#For LBR + AMR codecs (480 ch/mod): add 8
#For LBR + ILBC codecs (336 ch/mod): add 16
#For LBR + ILBC codecs + wireless codecs (336 ch/mod): add 24
# option routers is the same as the default gateway
option routers 192.168.1.1; #(Default Gateway)
option subnet-mask 255.255.255.224; #(Default Gateway Subnet Mask)
# subnet IP address usually default gateway address minus 1
subnet 192.168.1.0 netmask 255.255.255.224 #(Usually Default Gateway minus 1)
{
  host IMG_CPU1_0
    {
      hardware ethernet 00:20:1c:00:00:00; #(MAC ADDRESS OF CTRL 0 PORT)
      fixed-address 192.168.1.5; #(IP Address being configured on IMG CTRL 0 Port)
      # ftp server name (IP Address of the LINUX PC running FTP)
      next-server 192.168.1.100; #(IP Address of Server that IMG will get system software from)
      # IMG bin file (software load)
      filename "ftpBuilds/img1010_id0101.bin";
      option Host_1010_Flag 0; #(Configured Host Flag which is precalculated due to codecs etc being configured)
    }
  host IMG_CPU1_1
    {
      hardware ethernet 00:20:1c:00:00:01; #(MAC ADDRESS OF CTRL 1 PORT)
      fixed-address 192.168.1.5; #(IP Address being configured on IMG CTRL 1 Port)
      # ftp server name (IP Address of the LINUX PC running FTP)
      next-server 192.168.1.100; #(IP Address of Server that IMG will get system software from)
      # IMG bin file (software load)
      filename "ftpBuilds/img1010_id0101.bin";
      option Host_1010_Flag 0; #(Configured Host Flag which is precalculated due to codecs etc being configured)
    } |
FTP Redundancy
The IMG supports configuring redundant FTP Servers for downloading system software. When downloading the system software, if one FTP Server fails, a second configured FTP Server can take over. As displayed in the diagram below, the IMG 1010 normally gets its software load from the FTP Server labeled BootP/FTP Server A. If BootP/FTP Server A fails then the IMG 1010 can get the load from BootP/FTP Server B. In order for the redundant FTP Servers to function as displayed below, the following must be true:
The BootP/FTP functionality on FTP Server A and FTP Server B must both be configured on a server that is running the GCEMS application.
The servers do not have to be configured for host redundancy for the redundant FTP functionality to work.
FTP Redundancy is supported when using a server that has both BootP and FTP functionality. In these cases, the dhcpd.conf file can be modified.
FTP Redundancy is not supported when using a single FTP Server with a bootup.cfg file pointing to it.
There must be a dhcpd.conf file configured on each BootP/FTP Server.
The next-server line of the dhcpd.conf file on BootP/FTP Server A contains the IP Address of BootP/FTP Server A.
The next-server line of the dhcpd.conf file on BootP/FTP Server B contains the IP Address of BootP/FTP Server B.
Both BootP/FTP Servers must be loading the exact same version of system software (.bin) and build number. Loading two different versions of software will cause unexpected results if a switchover occurs.
Â