Configure FTP/DHCP Server_old

 

When loading system software through a BootP/FTP server, a user profile needs to be created on a server configured to run the  BootP/FTP services. The profile being created will be used when retrieving the system software binary file. In addition to the binary file, the server can also be used to download information such as IP, ntp, and any announcements or treatments to be played. The procedure below creates a profile using appropriate passwords etc. If a user profile has already been created during the Red Hat Enterprise Linux installation then steps 1-6 can be skipped since the user was already created. Start with step 7 to assign permissions to FTP and SSHD.

Note: The example below describes the initial process of setting up a user profile when deploying a server running Red Hat Enterprise Linux 5 as the BootP/FTP server. The procedures below can be utilized if the BootP/FTP server being configured is running Red Hat Enterprise Linux 5. If running an operating system other than Red Hat Enterprise Linux 5 then it is up to the administrator to know and set up the processes required to load the software to the IMG 2020. The procedures below in those instances can only be used as a template.

  1. From the Red Hat GUI main toolbar, select System > Administration > Users and Groups to open the User Manager. A query box opens asking for the User and Password.

  2. Enter the root password that was configured during operating system installation and select OK.

  3. A User Manager screen appears. Select Add User and a Create New User dialog box appears.

  4. In the User Name field enter: dialogic

  5. In the Full Name field enter a description of the account. In this example, BorderNet User was added.

  6. In the Password field, enter: Dial0gic (Capital D, Zero for o) and then enter same password in the Confirm Password field. Below is a screen capture of the Create New User dialog box.

  7. Create the Home Directory by adding the path to the dialogic user profile. In this example, /home/dialogic was used.

  8. Use the screen capture below for reference on any checked or unchecked boxes.

  9. SelectOK.

  10. The User Manager screen now has the new user added to the Users Tab.

  11. From the User Manager screen, assign the user dialogic permissions to use FTP and SSHD.

 

  • Select dialogic user and select properties. The User Properties screen appears.* Select Groups Tab and enable ftp, ntp, and sshd, by checking each service.* Select OK to exit the Users Properties screen.

  1. Close the User Manager Screen.

  2. Log Out from administrator user and logon as user:dialogic password:Dial0gic (Capital D and Zero for o).

  3. The next step is to load software. Refer to the topic for more information.
     

 

Once the Linux User Profile is created, the server can be configured to function as a BootP/FTP Server for loading the system software binary file to the IMG 2020. Also, the NFS and NTP services can be configured on the server as well. The procedure below will describe setting up to load software and configure any services needed.

Note: The procedures below can be utilized if the BootP/FTP server being configured is running Red Hat Enterprise Linux 5. If running an operating system other than Red Hat Enterprise Linux 5 then it is up to the administrator to know and set up the processes required to load the software to the IMG 2020. The procedures below in those instances can only be used as a template.

Create dhcpd.conf file

The initial topic labeled configures a server running Red Hat Enterprise Linux with a User profile and user password. Once the user profile has been created, the server can now be used to configure IP addresses and other configuration information on the IMG 2020. To achieve this, a DHCP client must be configured on the server. One of the first steps in configuring DHCP is to create a dhcpd.conf file and load it into the /etc/dhcp directory. To aid in the creation of the dhcpd.conf file, Sangoma has created a sample dhcpd.conf file which can be copied, modified for the new network, and loaded into the /etc/dhcp directory. Refer to the topic file. Once the dhcpd.conf file has been completed, ftp it into the /etc/dhcp directory as a root user. Below is an example of the listing of the dhcpd.conf file after being copied to the BootP/FTP server.

 

 

Start the DHCP and FTP Services

Once the dhcpd.conf file has been created and loaded into its proper location, the DHCP and FTP services can be either started or restarted. Follow the procedure below to either start or restart the service.

 

  1. Enter the following commands to start dhcpd service:

[root@rootuser ftpBuilds]# /sbin/service dhcpd start    (Start the dhcpd service)

 

[root@rootuser ftpBuilds]# /sbin/service dhcpd status   (Verify whether dhcpd is running or not)

 

[root@rootuser ftpBuilds]# /sbin/chkconfig dhcpd on     (Configure dhcpd to restart after a reboot of server)

 

[root@rootuser ftpBuilds]# /sbin/chkconfig dhcpd --list (Verify that runlevels 3,4, and 5 are all on.)

 

Example:  dhcpd                0:off     1:off     2:on     3:on     4:on     5:on     6:off

 

Start the FTP Service

Enter the following commands to start vsftpd service:


[root@rootuser ftpBuilds]# /sbin/service vsftpd start    (Start the vsftpd service)

[root@rootuser ftpBuilds]# /sbin/service vsftpd status  (Verify whether vsftpd is running or not)

[root@rootuser ftpBuilds]# /sbin/chkconfig vsftpd on    (Configure vsftpd to restart after a reboot of server)

[root@rootuser ftpBuilds]# /sbin/chkconfig vsftpd --list (Verify that runlevels 3,4, and 5 are all on.)

 

Example:  vsftpd                0:off     1:off     2:on     3:on     4:on     5:on     6:off

 

Create ftpBuilds directory

Create a directory under the user profile created earlier where the system software file and any other required files and links may be loaded. Follow procedure below.

  1. Within the /home/dialogic directory created earlier, create a new directory labeled ftpBuilds. Open a terminal window and go to /home/dialogic. Create the ftpBuilds directory as a dialogic user.
    [dialogic@dialogicuser ftpBuilds]$ mkdir ftpBuilds

 

Download Software to IMG 2020

  1. Once the DHCP and FTP services are running, the IMG 2020 software build can be downloaded. The IMG 2020 is shipped without software loaded on it. The latest version of software can be obtained from the Sangoma Technical Support BBS (Bulletin Board System) Website.

Obtain system software from BBS (Bulletin Board System) server

Go to https://wiki.freepbx.org/display/DIMG/Manuals. For login information refer to the welcome letter e-mailed after purchase of product or contact Sangoma Support for information on getting a logon username and password.* Download the latest IMG 2020 software file. Below displays an example of the file needed.bdn2020_ver220xxx_id0201.bin (xxx = Build Number) - System Software file

Create Link to System Software File Using ln -sf Command

To simplify the loading process, a common name will be used when loading the system software. This will simplify the process of loading newer builds in the future if required. The common name will be labeled bdn2020_id0201.bin and a link will be created linking the system software file downloaded from the BBS to the common name created. Enter the commands below to create the link.

  1. As a Super User, go to /home/dialogic/ftpBuilds directory. This is the directory that the system software file is loaded. Enter the following command:[root@rootuser ftpBuilds]# ln -sf bdn2020_ver220xxx_id0201.bin bdn2020_id0201.bin

  2. Confirm the link has been created, enter the command:[root@rootuser ftpBuilds]# ls -la

Response:

lrwxrwxrwx  1 root  root   27  Jun 21 09:27 bdn2020_id0201.bin -> bdn2020_ver220xxx_id0201.bin

 

  1. Verify the link created, points to the correct binary file for loading.

 

Load License File

The license file for the IMG 2020 was sent separately by e-mail and should be transferred into the directory that the system software file was loaded. In this example, the license file was loaded into /home/dialogic/ftpBuilds. If loading from a different directory or loading off an SD Card, verify the license file is loaded in correct directory. For more information, refer to . Below is a screen capture of the license listing in the ftpBuilds directory.

 

  

Optional Services

The services below are optional depending on the functionality being utilized. Follow procedure below to create/configure any of the services below.

 

Create the ntp.conf file

The IMG 2020 will need to get its time from a server. To aid in the creation of the ntp.conf file, Sangoma has created a sample ntp.conf file which can be copied, modified for the new network, and loaded into the /etc directory. Refer to the topic file. The sample file can be copied and used as a template when creating this file. Once the ntp.conf file has been completed, ftp it into the /etc directory as a root user. Below is an example of the listing of the ntp.conf file after being copied to the BootP/FTP server.

 

 

  1. Enter the following commands to start ntpd service

[root@rootuser ftpBuilds]# /sbin/service ntpd start    (Start the ntpd service)

[root@rootuser ftpBuilds]# /sbin/service ntpd status  (Verify whether ntpd is running or not)

[root@rootuser ftpBuilds]# /sbin/chkconfig ntpd on    (Configure ntpd service to restart after a reboot of server)

[root@rootuser ftpBuilds]# /sbin/chkconfig ntpd --list (Verify that runlevels 3,4, and 5 are all on.)

 

Example:  ntpd                0:off     1:off     2:on     3:on     4:on     5:on     6:off

Refer to the and topics for more information.

 

Configure NFS share

The IMG 2020 runs an NFS client that can be configured to retrieve files such as call tracing files, announcements files, and treatment files from an NFS server. The procedures below describes how to configure the server so that the files can be shared between the NFS server and the NFS Client (IMG 2020). Follow the instructions below to create each of the shares needed.

 

  1. As a SuperUser, create a directory under the /home/dialogic directory labeled shares. This will be the mount point for all the NFS shares that will need to be configured.
    [root@rootuser ftpBuilds]# mkdir shares

 

  1. On Linux Red Hat GUI, go to System > Administration > Server Settings > NFS. See screen capture below.

  1. Enter root password. The NFS Server Configuration box will appear.

  2. To add the new directory labeled shares, select the + Add button. Browse to the /home/dialogic/shares directory. Select OK.

  3. Set Basic permissions to either Read-Only or Read/Write. Read/Write is not necessary but can be set for future use.

  4. In the Host(s) field, either enter IP address of IMG 2020 or enter the wildcard * symbol which will allow multiple devices the ability to access the share. Below are a few different methods of selecting multiple devices.

    1. Multiple IMG 2020 IP addresses can be added by putting a space between each address#* Entering a wild card * symbol will allow any 2020 SBCs.# Click on the General Options tab. Accept the default value Sync write operations on request.

  5. Click on the User Access tab and check the Treat all client users as anonymous users.

  6. Enter the User and Group ID. The User ID and Group ID are found by going to the Linux Red Hat start menu and selecting Systems and Settings > Users and Groups.

  7. The User ID is displayed in the User ID Tab under the dialogic user. Enter that number.

  8. The Group ID is displayed in the Group ID Tab under the dialogic user. Enter that number.

  9. Select OK. After selecting OK the entry created should appear in the window.

  10. As a Super User, start or restart the NFS service and configure it to restart when server is rebooted. Enter the following commands to start the nfs server:

[root@rootuser ftpBuilds]# /sbin/service nfs start    (Start the nfs service)

[root@rootuser ftpBuilds]# /sbin/service nfs status   (Verify whether nfs is running or not)

[root@rootuser ftpBuilds]# /sbin/chkconfig nfs on     (Configure nfs service to restart after a reboot of server)

[root@rootuser ftpBuilds]# /sbin/chkconfig nfs --list (Verify that runlevels 3,4 and 5 are all on.)

 

Example:  nfs                0:off     1:off     2:on     3:on     4:on     5:on     6:off

 

Power on

  1. Once software is downloaded and links etc have been configured, Power-Up the IMG 2020. The cooling fans within the unit will initially run at full speed and quickly slow down. The LED's on front panel will blink at a set pattern while software is loading. Below is table displaying the sequence the LEDs go through while loading software.Note: When loading software, the LEDs on the front panel of the IMG 2020 are flashed in a specific sequence to display which function of the software loading procedure is being executed. See information below that describes the sequencing when loading software using BootP and FTP.

 

  • Power on the IMG 2020 and all the Span LEDs flash red three times indicating the startup procedure is beginning.

  • If using bootp, Span2 and Span3 LEDs light solid green for a few seconds.

  • If file is being loaded through use of FTP server, Span1 will light solid green for a few seconds.

  • Once software starts loading, Span1 will stay lit a solid green. Spans 4, 5, 6, and 7 will then start scanning starting with the Span4 LED. This indicates software is being loaded.

  • After software loads, the LEDs from Span1 to Span7 will all flash a solid green.

  • The IMG 2020 begins using software by going to the starting address of the software. All LEDs go OFF for a few seconds while this occurs.

  • When the software load is complete, Span1 through Span 7  LEDs flash to indicate unit is ready for configuration.

 

The loading of software and configuring of network information is now complete. To connect to the IMG 2020, open a web browser and connect. Refer to the topic for information on how to connect to IMG 2020 through the supported browsers.

 

Note: If system software file doesn't load, refer to the Troubleshooting section below.

 

Troubleshooting

Below is a list of bulleted items describing what may be the issues as to why the software is not loading to the IMG 2020. Check each bulleted item in the list below and verify they are not the issue.

  • Verify that the firewall is disabled. In some instances, the firewall setting on the server will not allow files to be transferred in or out of the server.

  • Verify that DHCP and FTP services are running. Use the commands below to verify

[dialogic@dialogicuser ftpBuilds]$ /sbin/service NFS status

[dialogic@dialogicuser ftpBuilds]$ /sbin/service dhcpd status

  • Verify that the dhcpd.conf file is correct. A colon or semi-colon in the wrong place could be the issue.

  • Verify that the switch bin file is in the correct location (/home/dialogic/ftpBuilds).

  • Verify that the link to the switch bin created in /home/dialogic/ftpBuilds is correct.
    Example:  bdn2020_id0201.bin -> bdn2020_ver210xxx_id0201.bin

 

Note: If the system software image gets corrupted during the download process, the IMG 2020 will not load the corrupt image. Instead, the IMG 2020 will flash the code below and then execute a reset.

Diagram

The following illustration shows the transfer of the IMG 2020 system software using FTP from an FTP server to each IMG 2020 with a local BootP Server.

Return to Documentation Home I Return to Sangoma Support