Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Software Install - FTP/DHCP

The procedure below describes how to configure a separate FTP/DHCP Server to download the system software to the IMG 2020. The procedure first sets up a user profile and then creates the directories required. Once the user profile and directories are created, the system software is then downloaded from Dialogic BBS (Bulletin Board System) and transferred into the directory created. A dhcpd.conf file on the FTP/DHCP server tells the IMG 2020 where to go to retrieve the system software and license file.

Once configured, the IMG 2020 boots from the FTP/DHCP Server and retrieves both the IP address of the CTRL 0 interface on the IMG 2020 and the location of the system software and license files. This information is all acquired from the dhcpd.conf file.

When choosing an FTP/DHCP Server, any server that has the required services can be used as the FTP/DHCP Server. If the user already has an FTP/DHCP Server in their network, that server can be used. If the Server with the EMS software was purchased through Sangoma, that server has all the services required so that server could be used as well. It is up to the user to decide which server will be used to download the software.

If the VM image which is running on a VM server is being used for running EMS software, for security purposes, it is not recommended that this server be used for transferring log or call tracing files to. Enabling the NFS Service lessens the security and makes the server more vulnerable. In this case, a separate server running the NFS Service must be utilized to transfer log and call tracing files.

Create User Profile on FTP/DHCP Server

The FTP/DHCP Server must have a Sangoma profile configured on it. If the server being used for FTP/DHCP was purchased from Sangoma, the Sangoma user profile and associated directories have already been created. Skip to the Download Software from Sangoma BBS (Bulletin Board System) section below if server had been purchased from Dialogic. Follow the next few steps to create the profile.

The example below describes the initial process of setting up a user profile when deploying a server running Red Hat Enterprise Linux 6.2 as the BootP/FTP server. If running an operating system other than Red Hat Enterprise Linux 6.2 then it is up to the administrator to know the processes required to configuring user profiles, dhcp services, and any other functions required. The procedures below in those instances can only be used as a template.

  • Login to the Linux machine as a root user.

  • As a root user, create a group labeled dialogic. The example will create a group profile labeled dialogic in /home. Refer to example below.

[root@localhost ftpBuilds]# groupadd dialogic

  • Create a user labeled dialogic under the group dialogic.

[root@localhost ftpBuilds]# useradd -g dialogic dialogic

  • Add a password of Dial0gic (Capital D, Zero for o) to the dialogic user just created.

[root@localhost etc]# passwd dialogic
New password: <Dial0gic>
Retype new password: <Dial0gic>

  • Verify the group and user got created by entering the following command.

[root@localhost etc]# more passwd | grep /home
dialogic:x:500:500::/home/dialogic:/bin/bash

  • Using SSH, log into the profile created by entering the appropriate credentials.

Create ftpBuilds Directory


The ftpBuilds directory will store the system software file and license file. Follow procedure below to create the ftpBuilds directory. The server sold through Sangoma will already have the ftpBuilds directory created on it. If the ftpBuilds directory is not already created, it will have to be manually created. Follow the example below to create the ftpBuilds directory.

  • 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 from Sangoma BBS (Bulletin Board System)


The IMG 2020 is shipped without software loaded on it. The latest version of system software can be obtained from the Sangoma BBS (Bulletin Board System) http://excelbbs.sangoma.com.

Obtain system software from Dialogic BBS (Bulletin Board System)

  • Go to https://wiki.freepbx.org/display/DIMG/Manuals.

  • Select IMG 2020.

  • 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_ver230xxx_id0201.bin (xxx=build number) - System Software file

Transfer System Software to ftpBuilds Directory

To load the system software to the IMG 2020, the bdn2020_ver230xxx_id0201.bin file must first be transferred and then installed. Follow steps below.

  • Using SFTP, login to the server using the login credentials created above.

Login Credentials

Username: dialogic 
Password: Dial0gic (Capital D, Zero for o)

  • Transfer the bdn2020_ver230xxx_id0201.bin file acquired from Sangoma BBS (Bulletin Board System) to the /home/dialogic/ftpBuilds directory. When transferring the file, verify it is being transferred using the binary format.

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 Sangoma BBS (Bulletin Board System) to the common name created. Enter the commands below to create the link.

  • As a superuser, 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_ver230xxx_id0201.bin bdn2020_id0201.bin

  • 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_ver230xxx_id0201.bin

  • 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 Licensing. Below is a screen capture of the license listing in the ftpBuilds directory.

Verify the license being downloaded has been created for the version of software (Release 2.3.0) being loaded. 

-rwxrwxrwx    1     dialogic   dialogic    5 Jul 12  2010  10308302_201007121443704.cfg

Configure FTP/DHCP Services

Once the user profile and associated directories have been created, the server will now be configured to function as a FTP/DHCP Server for loading the system software and license files. The procedure below will describe setting up to load software.

Create dhcpd.conf File

The Create user profile on FTP/DHCP Server section above configures a user profile and password. The next step is to configure and start the DHCP and FTP Services.

  • Create a dhcpd.conf file and load it into the /etc/dhcp directory.

To aid in the creation of the dhcpd.conf file, Dialogic 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 sample dhcpd.conf 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 FTP/DHCP server.

-rw-r--r--    1 root too       2352 Nov 4 13:00 dhcp.conf

Start the FTP and DHCP Services


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

  • Enter the following commands as a root or superuser to start the 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

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, Dialogic 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 Sample ntp.conf file. The sample file can be copied and used as a template when creating this file. Once the ntp.conf file has been created and modified for your network, it can be transferred to 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.

  • 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 Sample ntp.conf and Configure SNTP topics for more information.

Configure NFS Share (Separate Server)

The IMG 2020 runs an NFS client that can be configured to retrieve files such as call tracing files and log 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.

If the VM image which is running on a VM server is being used for running EMS software, for security purposes, it is not recommended that this server be used for transferring log or call tracing files to. Enabling the NFS Service lessens the security and makes the server more vulnerable. In this case, a separate server running the NFS Service must be utilized to transfer log and call tracing files.

  • As a superuser, create a directory labeled calltracing under the /opt/dialogic/common directory. This will be the mount point for all the NFS shares that will need to be configured.

mkdir calltracing

  • Verify the NFS got loaded into the kernel by entering the following command. If NFS is not returned as displayed in example below, refer to step 3 and then repeat verification.

Below is the response that should be returned

  • To load the NFS into the kernel, enter the following command.

modprobe nfs

  • Using vi, edit the /etc/exports file and add the share directory created above. To find the dialogic user id and dialogic group id enter the following command:

[root@localhost etc]# id dialogic
uid=500(dialogic) gid=500(dialogic) groups=500(dialogic)

vi entry

/opt/dialogic/common/calltracing *(rw,sync,anonuid=500, anongid=500)

  • As a superuser, 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

Power On System to Load Software

  • 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 slow down after software is loaded. The LED's on front panel will blink at a set pattern during the software loading process. The table below displays the sequence the LEDs will go through during the loading process.

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. Refer to the information below that describes the LED sequencing when loading software utilizing 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 Web GUI - Functionality topic for information on how to connect to IMG 2020 through the supported browsers.

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

Troubleshooting

Below is a list of bulleted items describing what the issues might be if software is not loading. Check each bulleted item in the list below and verify they are not the problem.

  • 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_ver230xxx_id0201.bin

 

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.

  • No labels

Return to Documentation Home I Return to Sangoma Support