OMC Installation Guide

(1)

Installation Guide

2.4.3 2.4.3

(2)

Copyright

Disclaimer

No part of this document may be reproduced in any form No part of this document may be reproduced in any form without the written permission of the copyright owner. without the written permission of the copyright owner. The contents of this

The contents of this document are subject to revisiondocument are subject to revision without notice due to

without notice due to continued progress in methodology,continued progress in methodology, design, and manufacturing. VNL

design, and manufacturing. VNL®® shall have no liability for shall have no liability for any error or damage of any kind resulting from the use of any error or damage of any kind resulting from the use of this document.

this document.

Tra

Trademark List

demark List

WorldGSM

WorldGSMTMTM is a trademark owned by Vihaan Networks is a trademark owned by Vihaan Networks Limited. All other product or service names mentioned in this Limited. All other product or service names mentioned in this document are trademarks of their

document are trademarks of their respective companies.respective companies.

Document

Document Re

Reference Number

ference Number

Agile # VNL-OMC-ITG-000001 Agile # VNL-OMC-ITG-000001

(3)

Copyright

Disclaimer

No part of this document may be reproduced in any form No part of this document may be reproduced in any form without the written permission of the copyright owner. without the written permission of the copyright owner. The contents of this

The contents of this document are subject to revisiondocument are subject to revision without notice due to

without notice due to continued progress in methodology,continued progress in methodology, design, and manufacturing. VNL

design, and manufacturing. VNL®® shall have no liability for shall have no liability for any error or damage of any kind resulting from the use of any error or damage of any kind resulting from the use of this document.

this document.

Tra

Trademark List

demark List

WorldGSM

WorldGSMTMTM is a trademark owned by Vihaan Networks is a trademark owned by Vihaan Networks Limited. All other product or service names mentioned in this Limited. All other product or service names mentioned in this document are trademarks of their

document are trademarks of their respective companies.respective companies.

Document

Document Re

Reference Number

ference Number

Agile # VNL-OMC-ITG-000001 Agile # VNL-OMC-ITG-000001

(4)

Figures

Figure 1: OMC Installation ... 14

Figure 2: OMC Installation Wizard ... 14

Figure 3: OMC Installation Location ... 15

Figure 4: Browse Location ... 16

Figure 5: Destination Location to Install Third Party Tools ... 16

Figure 6: Database Information ... 17

Figure 7: Server Information ... 19

Figure 8: Servlet Information ... 20

Figure 9: Supported Nodes ... 21

Figure 10: Copy Files ... 22

Figure 11: Unpacking Files ... 22

Figure 12: Successful Installation of OMC ... 23

Figure 13: OMC Uninstallation ... 30

Figure 14: Deleting OMC Home Directory ... 31

Figure 15: Removing the Files ... 32

Figure 16: OMC Uninstallation Complete ... 32

Figure 17: Communication between BSC Node and Remote OMC ... 37

Figure 18: MLPPP Installation Procedure ... 38

Figure 19: Kernel Version Check ... 39

Figure 20: Untar MLPPP-1.1.0.003.tar.gz ... 40

(7)

Figure 22: Bin Folder Contents ... 41

Figure 23: Wanpipe Hardware Information ... ... 42

Figure 24: Wanpipe Package ... 42

Figure 25: Rpmbuild Wanpipe ... 48

Figure 26: Searching Files ... 49

Figure 27: md5sum Check ... 50

Figure 28: md5sum Comparison ... 51

Figure 29: PPPD Version Check ... 53

Figure 30: Spawn Output ... 54

Figure 31: PPP Drivers Check ... 54

Figure 32: Wanrouter Hwprobe Output ... 55

Figure 33: Wanrouter Status ... 57

Figure 34: ifconfigpppX Output... 59

(8)

Tables

Table 1: Document Conventions ... 8

Table 2: Terms and Abbreviations ... 9

Table 3: Database Information ... 17

Table 4: Server Fields Description ... 19

Table 5: Servlet Fields Description ... 20

(9)

1. About This Document

1.1 Purpos e

This document describes how to install operations

management center (OMC) package on a Linux system.

1.2 Intended Audience

The intended target groups for this document are:

• OMC Application Users

• OMC Network and System Administrators

1.3 Docum ent Convention s

The different conventions used in this document are explained in the following table:

Table 1: Document Conventions

Convention Description

Note: Provides information about important features or instructions.



Caution: Alerts you to potential damage to a program, device, or system.



Warning: Alerts you to potential injury or fatality.

(10)

Fi l e/ di r ect or y names

All courier new

Any option that needs to be selected or typed in the user interface is represented using bold font.

Bold font

1.4 Terms and Ab breviation s

The different terms and abbreviations used in this document are explained in the following table:

Table 2: Terms and Ab breviatio ns

Terms / Abbreviations Descripti on / Expansion

DHCP Dynamic Host Configuration

Protocol

HA High Availability

MLPPP Multilink Point-to-Point Protocol

NCP Network Control Protocol

OMC Operations Management Center

RPM Red Hat Package Manager

1.5 References

• X3550M2 1U Rack Mountable Server • x3550m2 HW Installation User Guide

(11)

2. Overview

This document describes how to install the operations

management center (OMC) package using user-friendly and completely GUI driven installation wizard. The OMC

package includes OMC server, OMC client, OMC servlet, and all the third party tools.

Note: The OMC client might be installed either on the OMC server system or on a separate system.

You are required to install multilink point-to-point protocol (MLPPP) drivers in case you are using the E1 interface for establishing connectivity between base station controller (BSC) and remote OMC. To know how to install MLPPP, please refer “ Appendix.B-MLPPP Installation”

In case of Ethernet, you are not required to install MLPPP drivers.

2.1 System Requirements

• Refer “X3550M2 1U Rack Mountable Server” to know

the system requirements for installing and running the OMC server.

• Refer “x3550m2 HW Installation User Guide” for OMC

hardware installation. Note:

(12)

3. Pre-Installation Settings

This section describes the steps you need to perform before starting the OMC installation wizard.

Perform the following steps before installing OMC:

1. Uninstall any previous installation of OMC. Please refer “OMC Uninstallation Procedure”.

2. Reboot the OMC server after successfully uninstalling the OMC.

3. Logon as a root user.

4. Check the status of the FTP server and ensure that the file transfer protocol (FTP) server is running on the system by executing the following command:

# service vsftpd status

The following output appears in case FTP server is running:

[root@localhost archive]# service vsftpd status vsftpd (pid 24305) is running...

a. If FTP server is not responding or ‘vsftpd is stopped’ message appears on console, execute the following command to start the FTP server:

# service vsftpd start

5. Type the following command to check whether the classpath environment variable is unset or not:

(13)

# echo $CLASSPATH

a. If it is set then execute the following command to unset the classpath environment variables:

(14)

4. OMC Installation Procedure

This section describes the procedure to install OMC

installation package on server system (Linux system) using installation wizard. The OMC package includes the

following information:

• OMC server

• OMC client • OMC servlet

• OMC database • Third party tools

The installation wizard guides you through the installation process and prompts you wherever information is required. This section also describes how to install OMC client on a separate system.

4.1 Installing OMC using Installation Wizard

OMC installation wizard is available as an executable file. For example, OMC- 5. 6. 3. 002- Li nux- x86- I nst al l .

Note: Assume that the executable file is available in the current directory.

Perform the following steps to start executing the installer: 1. Execute the following command to start the OMC

installation wizard: Syntax:

(15)

Example:

# ./OMC-5.6.3.002-Linux-x86-Install The following message appears:

Figure 1: OMC Installatio n

2. Click Yes to continue installation.

The OMC installation wizard screen appears. Figure 2: OMC Inst allation Wizard

Note: Click Cancel to exit the installation wizard. 3. Click Next > to continue.

(16)

The following screen appears that allows you to select the location where you want to install OMC:

Figure 3: OMC Installatio n Locati on

Note: Click < Back to return to previous wizard screen. 4. Click Next > to install the OMC in the default location

(/ usr / l ocal / OMC). Otherwise, you can click the Browse button to choose a desired location where you want to install OMC.

(17)

Figure 4: Br owse Location

Note: Click Make New Fol der to create a new folder. The following screen appears that allows you to choose a destination location for installing third party softwares: Figure 5: Destination Location to Install Third Party Tools

(18)

5. Click Next > to install at the default location or click

Browse to select the desired location to install third party tools (if selected).

The following screen appears that allows you to enter information of the database:

Figure 6: Database Infor mation

6. Provide the information of the database in the given fields:

Table 3: Database Informati on

Field Name Descr ipt ion

Type To Be Supported Specify the type of the database such as Postgres.

Administrative User ID User name for Postgres user created while installing Postgres.

(19)

while installing Postgres. Port where DB is

Running

Specify the port number where Postgres is running. The default port number is 5432.

User Name Specify the name used by FLEX-NM

servers to access the database. The default user name is vnet.

Password Specify the password used by FLEX-NM

servers to access the database. Note: The above fields have default values and are read only.

During installation, the database (Postgres) is installed in

/ usr / l ocal / pgsql / omcdat a.

7. Click Next >.

The following screen appears that allows you to provide the server related information:

(20)

Figure 7: Server Informati on

8. Provide the information of the server in the given fields: Table 4: Server Fields Descrip tio n

Field Name Descr ipt ion OMC Server

Name

Specify the OMC server name.

OMC Server IP IP address of the system where OMC is to be installed.

RMI Registry Port Specify RMI registry port. The default port is 2222.

FTP User ID: Specify the user ID to logon to the FTP server running on the OMC server.

FTP Password Specify the password to logon to the FTP server running on the OMC server.

(21)

ACTIVE MQ Server IP

Specify IP address of the system where Active MQ server is running.

9. Click Next >.

The following screen appears: Figure 8: Servlet Information

10. Provide the information of the servlet in given fields. Table 5: Servl et Fields Descrip tio n

Field Name Descri pti on

IP or Hostname Specify the IP address of the system where Tomcat is running. By default, it is the same IP address where OMC is being installed.

Port used by Tomcat Specify port used by Tomcat. The default port is 8080.

(22)

The following screen appears that allows you to select the nodes that you want to support:

Figure 9: Support ed Nodes

12. Select the checkboxes to select the desired node types. Note: The cross mark ‘X’ indicates that the particular node is selected.

13. Click Next >.

The following screen appears that allows you to confirm the specified settings:

(23)

Figure 10: Copy Files

14. Click Next > to begin the process of unpacking and copying the program files.

The following screen appears: Figure 11: Unpacking Files

(24)

After successfully unpacking and copying the program files, the following screen appears:

Figure 12: Successfu l Installati on of OMC

15. Click Finish to complete OMC Installation.

The above-mentioned steps will install the entire OMC package such as server, client, and servlet on a same system. To install the OMC client on a separate system, please refer “ Appendix.A-Installing OMC Client on a Separate System”.

(25)

5. Post-Installation Settings

This section provides information about the settings that you need to do after installing the OMC.

5.1 Host Entries

The OMC server’s / et c/ host s file requires the following settings:

• IP of machine: This refers the IP address, for example,

127.0.0.1.

• Hostname: This refers to the hostname of the OMC

server, for example, localhost.localdomain localhost. Note: You should provide these entries if the OMC client is running on a remote system and these settings are also required for the NBI interface.

5.2 FTP Server

Terminate the FTP server on the Linux system before

starting the OMC server as the OMC comes up with its own FTP server. For example,

1. If vsftpd is used as FTP server then use the following commands to stop FTP service:

# service vsftpd stop # service xinetd stop

2. If gssftp is used as FTP server then use the following commands to stop the FTP service:

(26)

# chkconfig gssftp off

5.3 Act iveMQ Manual Conf igur ation

ActiveMQ is a JMS implementation third party software. OMC requires this for its log manager component.

You need to do the following configuration after successfully installing the OMC:

1. Logon as root user.

2. Go to act i vemq home path by executing the following command:

# cd $ACTIVEMQ_HOME/conf

3. Open the act i vemq xml file in the vi editor by executing the following command:

vi activemq.xml

4. Go to the <transportConnectors> group tag. 5. Replace the tag <t r anspor t Connect or

name=" openwi r e"

ur i =" t cp: / / l ocal host : 61616"

di scover yUr i =" mul t i cast : / / def aul t " / >with

(27)

6. OMC Scripts

This section describes how to start, stop, and check the status of the OMC server by using the following scripts:

• rstrl

• stopOMC

• omcStatus

Note: These scripts are available in the Ser ver folder of OMC installation directory.

This section also describes how to start and stop the OMC client.

6.1 The rst rl Scri pt

It is a startup script for all OMC server related processes. The script terminates all the active OMC server processes and then restarts all the processes one by one.

After starting the required processes, it keeps on checking the state of the OMC processes. In case any process that relates to OMC is terminated, the script checks the

association and restarts all the required processes. 1. To start r s t r l , go to Ser ver folder of the OMC

installation directory and execute the following command:

# ./rstrl

Note: In case any of the OMC server related processes are not working, they automatically start working after few

(28)

6.2 The omcStatus Scrip t

You can use this script to check the status of all the OMC server services, processes, and overall system memory. It executes in a loop and pauses for 5 seconds.

1. To start omcSt at us, go to Ser ver folder of the OMC installation directory and execute the following command: Command:

# ./omcStatus Output:

(29)

6.3 The stopOMC Scrip t

You can use this script to stop all the OMC processes, including the rstrl script.

1. To start st opOMC, go to Ser ver folder of the OMC

installation directory and execute the following command:

# ./stopOMC

Note: To stop the scripts, you can either logout or exit from the OMC.

6.4 Client Startup Script

To start the client, go to the Cl i ent folder of the OMC installation directory and execute the following command:

# . /run.sh

Note: Ensure that all the OMC services are up and running before starting the OMC client.

6.5 Basic Checks

You need to perform certain basic checks to ensure that scripts are functioning properly.

• Ensure that the server and client scripts are available

under Ser ver and Cl i ent folder of the OMC installation directory.

• Always execute the scripts as a root user.

• After running the OMC scripts, ensure sure that no other

(30)

can use the following debugging tools to debug the network errors:

o Wireshark

(31)

7. OMC Uninstallation Procedure

This section describes the procedure to uninstall t he OMC application.

1. Execute the following command to go to the directory where OMC is installed:

Syntax:

# cd <directory name> Example:

# cd OMC_Install_Dir

The OMC_I nst al l _Di r refers to the directory where OMC is installed.

2. Execute the following command to uninstall the OMC:

# ./uninstall

The following message appears: Figure 13: OMC Uninstallati on

(32)

3. Click Yes to continue OMC uninstallation. The following message appears:

Figure 14: Deleting OMC Home Directory

4. Click Yes to delete / home/ omc directory and to continue the uninstallation procedure.

Note: Click No to continue the uninstallation procedure without deleting the / home/ omc directory. The / home/ omc

directory contains alarm files, performance files, and CER files sent by the node.

(33)

Figure 15: Removing the Files

The following screen appears after successfully uninstalling the OMC:

(34)

Appendix.A Installing OMC Client

on a Separate System

This section describes the procedure to install OMC client on a separate system.

A.1 System Requ iremen ts

The system requirements for installing OMC client on a separate system are as follows:

Hardw are Requir ement

• 2 GB RAM

Softw are Requirement

• JRE: 1.6.0 Update 12

• OS: Windows (XP, 2000), Linux PC (RHEL 5.5

Enterprise Edition)

A.2 Prerequis ites

Before installing the OMC client on a separate system, ensure the following:

• JDK is installed on the client system (Linux system).

• OMC server system is reachable from the OMC client

(35)

A.3 Steps to Install OMC Cli ent

Perform the following steps to install the OMC client on Linux or Windows operating system:

1. Logon to the OMC server system as a root user. 2. Go to the OMC installation directory by executing the

following command:

cd <OMC_Home>

• OMC_Home refers to the path of the OMC installation

directory. For example, / usr / l ocal / OMC. 3. Zip the client folder under the same directory by

executing the following command:

zip –r <OMC_Client>

• OMC_Client refers to name of the OMC client folder.

4. Transfer the client zipped file from OMC server system to OMC client system and unzip it. Execute the following command to unzip the OMC client folder:

unzip <OMC_Client.zip>

You need to make the following modifications to connect to the external OMC:

1. Logon to the OMC server system as root user.

2. Open / et c/ host s file to ensure that the first line in the file is:

(36)

<IP> <System name> localhost.localdomain localhost

• IP is the reachable public IP of OMC server. • System name is the system hostname.

3. Check if there is any firewall between the client and server.

i. If yes, then you need to open the following port: 8080 (http), 61716 (JMS), 4445 (Event).

(37)

Appendix.B MLPPP Installation

Multilink point-to-point protocol (MLPPP) is a communication protocol that enables a computer to use two point-to-point (PPP) ports as a single port of greater bandwidth. PPP is a full-duplex protocol that uses a serial interface for

communicating between two systems. PPP offers error correction and can handle synchronous as well as asynchronous data. For example, if you combine two

modems and connect to the Internet then the data transfer rate increases. Similarly, MLPPP increases the data transfer rate. The data transfer rates of the two links should be

similar. Otherwise, the slower link decreases the overall throughput.

This section describes the drivers that are required to install and configure MLPPP. This section also lists the supported versions of all the pre-requisite drivers.

B.1 Comm uni cation between BSC and Remote OMC

OMC, installed on the remote system, communicates with the onsite BSC node through E1 interface. You need to install the Sangoma card to configure the MLPPP.

Note: By default, MLPPP is installed on the BSC node. The Sangoma card’s driver and wanpipe communicates with the PPP drivers, which communicate with BSC node by using E1.

(38)

Figure 17: Communi cation between BSC Node and Remote OMC

B.2 Pre-requisite Drivers

You need to install the following drivers to install and configure MLPPP:

• Wanpipe drivers • PPP drivers

• PPP daemon

• MLPPP drivers

You need to follow the given below procedure to

successfully install and configure MLPPP on the OMC remote system.

(39)

Figure 18: MLPPP Installatio n Proc edure

B.3 Drivers Support ed Versions

The subsequent table lists the supported versions of the following components:

Table 6: Support ed Version s

Component Version

EL5 Kernel Version 2.6.18-194PAE.el5

PPP version 2.4.4.4

Platform i386

(40)

Note:

Note: MLPPP installation is supported only MLPPP installation is supported only for kernelfor kernel version specified in the above table.

version specified in the above table.

You can verify the kernel version of your Linux operating You can verify the kernel version of your Linux operating system by executing the following command:

system by executing the following command:

# uname -r # uname -r

The output of the

The output of the above command should be as shownabove command should be as shown below:

below:

Figure 19: Kernel Ve

Figure 19: Kernel Versirsi on Checkon Check

B.4 MLPPP Deliverable

VNL

VNL®®L provides you theL provides you the MMLPPP-LPPP- 1. 11. 1. 0. . 0. 00003. t3. t arar . gz. gz file, file, which contains the following folders in the

which contains the following folders in the BBi ni n directory: directory:

• • config config • • dhcpd_util dhcpd_util • • etc etc • • modules modules • • pppd pppd • • rpmbuild rpmbuild • • wanpipe-3.3.1 wanpipe-3.3.1 • • install_el5.shinstall_el5.sh • • pppd_spawn_port(1..4) pppd_spawn_port(1..4) Save the

Save the MMLPPPLPPP-- 11. 1. 1. 0. 0. 0. 0003. 3. tt arar . g. gz z tt arar . g. gzz file at the file at the desired location, for example, in the

desired location, for example, in the / / hohomme/ e/ MMLLPPPPPP

directory. directory.

(41)

B.4 B.4.1 E

.1 Extracti

xtracti ng B

ng B in

in Folder

Folder

You need to untar the

You need to untar the MMLPPP-LPPP- 1. 21. 2. 0. . 0. 00005. t5. t arar . gz. gz file tofile to extract the

extract the BBi ni n folder. folder. 1.

1. Execute the Execute the following commafollowing command to nd to untar the untar the file:file: Syntax:

Syntax:

# tar <option> <filename> # tar <option> <filename> Example:

Example:

# -xvf MLPPP-1.1.0.003. tar-xvf # -xvf MLPPP-1.1.0.003. tar-xvf

The output of the above command is as shown in the The output of the above command is as shown in the following figure:

following figure: Figu

Figure re 20: Unt20: Unt ar ar MLPPPMLPPP-1.-1.1.01.0.00.003.tar.gz3.tar.gz

After executing the above comm

After executing the above command, theand, the BBi ni n folder is folder is created in the

created in the MMLLPPPPPP directory. directory. 2.

2. Execute the Execute the following commanfollowing command to d to view the view the contents ocontents off the

(42)

The output shows the

The output shows the BBi ni n folder. folder. Figure 21: MLP

Figure 21: MLPPP DPP Directirect ory ory ContentsContents

3.

3. Go Go toto BBi ni n directory and execute the directory and execute the following command:following command:

# ls -l # ls -l

The output is as shown below: The output is as shown below: Figure 22

Figure 22: Bi: Bi n Folder Contentsn Folder Contents

B.5 W

B.5 Wanpipe Drivers Inst

anpipe Drivers Inst allation

allation

This section describes the installation procedure of

This section describes the installation procedure of wanpipewanpipe drivers.

drivers.

B.5

B.5.1 .1 Uninstalling

Uninstalling Pre

vious version

version

You should check for the

You should check for the previous installation of wanpipe inprevious installation of wanpipe in the system before starting a new installation.

(43)

1. Execute the following command to check that wanpipe is installed or not:

# wanrouter hwprobe

The following output confirms that wanpipe exists on the system:

Figure 23: Wanpipe Hardware Infor mation

B.5.1.1 Check Previous Wanpi pe Installatio n u sing RPM

1. Check whether the previous version of wanpipe exists or not in the system by using the rpm command by

executing the following command:

# rpm -qa | grep wanpipe

The above command shows the wanpipe rpm package, if it is installed.

(44)

a. If wanpipe exists then remove it before installing the current version. Perform the following steps to

remove wanpipe:

i. Check for ppp interface by executing the following command:

Syntax:

# ifconfig ppp<X>

Here X represents the interface. It has to be a numeric value.

Example:

# ifconfig ppp1

ii. Executing the following commands terminate the pppX process:

# pkill -9 pppd_spawn # pkill -9 pppd

iii. Execute the following command to verify that no pppd instances are running:

# ps -ef | grep pppd # ps -ef | grep spawn

iv. In case the pppd instances are running then you need to forcefully kill the pppd instances by using the following command:

(45)

Syntax:

# kill -9 <PID>

Note: PID refers to process identifier.

Executing the following command to find out the process PID:

Syntax:

# ps -ef|grep <process_name> Example:

# ps -ef|grep pppd

The above command provides the PID of the pppd. Execute the following command to kill the pppd instances:

Example:

# kill -9 4

Note: In the above command 4 refers to PID.

v. Execute the following command to verify whether any wanpipe is running or not:

# wanrouter status

vi. In case any wanpipe is running, then execute the following command to stop them:

(46)

Syntax:

# wanrouter stop <X>

X refers to wanpipe1, wanpipe2, wanpipe3, or wanpipe4 depending upon the respective running wanpipe.

Example:

# wanrouter stop wanpipe1

vii. Execute the following command to uninstall or remove the wanpipe package:

Syntax:

# rpm -e <wanpipe-package> Example:

# rpm -e <wanpipe-3.3.1-0>

B.5.1.2 Check Previous Wanpi pe Installation wit hout usin g RPM

1. If you have installed wanpipe directly by using setup script of Sangoma then follow the below given steps to uninstall wanpipe.

a. Check for ppp interface by executing the following command:

# ifconfig pppX

b. Terminate the pppX process. Execute the following commands to terminate the process:

(47)

# pkill -9 pppd_spawn # pkill -9 pppd

c. Execute the following command to verify that no pppd instances are running:

# ps -ef | grep pppd # ps -ef | grep spawn

i. In case the pppd instances are running then you need to forcefully kill the pppd instances by using the following command:

Syntax:

# kill -9 <PID> Example:

# kill -9 5

d. Execute the following command to verify whether any wanpipe is running or not:

# wanrouter status

i. In case any wanpipe is running, then execute the following command to stop them:

Syntax:

# wanrouter stop <X>

(48)

Example:

# wanrouter stop wanpipe2

ii. Execute the following command to go to

wanpi pe 3. 3. 1 directory:

# cd Bin/wanpipe-3.3.1

iii. Execute the following command to remove wanpipe:

# ./Setup remove

iv. Press the Y key to perform uninstallation.

B.5.2 Inst alling Wanpi pe

Perform the following steps to install the wanpipe:

1. Open the terminal, go toBi n directory by executing the following command:

# cd Bin

2. Execute the following command to install wanpipe: Syntax:

# rpm -ivh --force rpmbuild/wanpipe-<version>-0.<platform>.rpm

(49)

Example:

# rpm -ivh --force rpmbuild/wanpipe-3.3.1.0.i386.rpm

In the above command the <version> and <platform> refers to the currently supported version and platform. The output of the above command is as shown below:

Figure 25: Rpmbui ld Wanpipe

B.6 PPP Installatio n

This section describes the installation procedure of t he PPP daemon. You need to install the PPP drivers before

installing the PPP daemon.

B.6.1 Inst alling PPP Drivers

Perform the following steps to install the PPP drivers:

1. Go to Bi n directory by executing the following command:

(50)

# . ./install_el5.sh

Note: Do not consider “unalias cp failure” as error during execution of install_el5.sh.

If you want to run dynamic host configuration protocol

(DHCP) server, execute the following command to make the lease file for DHCPD server:

# touch /home/mlppp_scripts/dhcpd_util/dhcpd.leases The lease file stores the configuration details such as IP

address, client name, and time period for which the lease is given to the client.

B.6.1.1 Basic Checks

After installing the PPP drivers perform the following checks: 1. Search the ppp_gener i c. ko, ppp_synct t y. ko, and

sl hc. ko files in l i b/ modul es directory. Perform the following steps to search these files:

a. Go to / l i b/ modul es/ <EL5 ker nel

ver si on>/ ext r a/ directory and execute the following command:

# find . -name ppp_generic.ko *

The output of the above command is as shown below: Figure 26: Searchin g Files

(51)

Similarly, execute the find command to search the remaining two files.

2. Compare checksum of these files with the files stored in theBi n/ modul es directory.

The md5sum of the above listed modules should match with the modules contained in modul es directory in the Bi n

folder. Perform the following steps to compare checksum of files:

a. Go to l i b/ modul es/ ext r a directory and execute the following command to check md5sum:

# md5sum ppp_generic.ko

The output of the above command is as shown below: Figure 27: md 5sum Check

b. Go to Bi n/ modul es directory and execute the following command:

# md5sum ppp_generic.ko

(52)

Figure 28: md5sum Comparison

The above output shows that the md5sum of both files is same. Similarly, check the md5sum of the other two files.

B.6.2 Install ing PPP Daemon

Perform the following steps to install PPP daemon:

1. Check the version by executing the following command:

# ls /home/MLPPP/Bin/pppd/lib/pppd

2. Go to Bi n directory and create a PPPD directory (if none exist) by using the following command:

# mkdir /usr/local/include/pppd

3. You can suppress the prompt so that it does not prompt you for input by executing the following command:

# unalias cp

4. Copy all the files from location pppd/ i ncl ude/ pppd to

(53)

# cp -f pppd/include/pppd/* /usr/local/include/pppd/

5. Execute the following command to create a directory (if none exist):

Syntax:

# mkdir -p /usr/local/lib/pppd/<version>/ Example:

# mkdir -p /usr/local/lib/pppd/2.4.4.4/ 6. Copy all the files from location

pppd/ l i b/ pppd/ <ver si on>to

/ usr / l ocal / l i b/ pppd/ <ver si on>by executing the following command: Syntax: # cp -f pppd/lib/pppd/<version>/* /usr/local/lib/pppd/<version>/ Example: # cp -f pppd/lib/pppd/2.4.4.4/* /usr/local/lib/pppd/2.4.4.4/

7. Copy all the files from location pppd/ sbi n/ to

/ usr / l ocal / sbi n/ by executing the following command:

(54)

8. Copy all the files from location

/ pppd/ s har e/ man/ man8 to

/usr / l oc al / shar e/ man/ man8/ by executing the following command:

# cp -f pppd/share/man/man8/* /usr/local/share/man/man8

1. After installing pppd, open the terminal and execute the following command:

Syntax:

# pppd <-version> Example:

# pppd 2.4.4.4

The above command provides the output as shown below that confirm the installation of ppp daemon:

Figure 29: PPPD Version Check

After the installation is confirmed, reboot the system, and perform some basic checks using the following steps: 2. Execute the following command to check that all

(55)

# ps -ef | grep spawn

The above command displays all 4 pppd_spawn utilities. Figure 30: Spawn Output

3. Execute the following commands sequentially to check whether all the ppp drivers are installed or not:

# lsmod | grep ppp_generic # lsmod | grep ppp_synctty # lsmod | grep slhc

The output of the above commands is as shown below: Figure 31: PPP Drivers Check

4. Execute the following command to check whether the wanrouter is properly installed or not:

# wanrouter hwprobe

The wanrouter command is used to start/stop/restart and display wanpipe current status and environment. The above command displays the following output:

(56)

Figure 32: Wanrouter Hwpro be Outp ut

Note: Here, the X and Y refer to the respective system’s slot number and bus number on which Sangoma card is installed.

B.7 MLPPP Configu ration

This section describes the procedure to configure MLPPP drivers.

B.7.1 Configuring MLPPP Drivers

Perform the following steps to configure MLPPP drivers: 1. Go to Bi n directory and execute the following command:

# unalias cp

2. Copy all the files from location

conf i g/ wanpi pe_conf i g/ wanpi pe/ wanpi pe to

/ et c/ wanpi pe by executing the following command:

# cp -f

config/wanpipe_config/wanpipe/wanpipe/*.conf /etc/wanpipe

(57)

# wanrouter hwprobe

The values of X and Y depend upon the slot and bus of the system on which you are configuring MLPPP.

4. Open / et c/ wanpi pe/ wanpi peZ. conf (where Z =1-4) files one by one and replace the two variables PCISLOT and PCIBUS with X and Y variables.

The MLPPP configuration is completed after performing the above steps.

B.7.2 Config uri ng PPPD

1. Execute the following commands to copy all files from

Bi n directory to et c directory:

# mkdir -p /etc/ppp/ (if not exists)

# cp -f config/pppd_config/ppp/options /etc/ppp # cp -f config/pppd_config/ppp/ip-up.local /etc/ppp # cp -f config/pppd_config/ppp/ip-down.local /etc/ppp # cp -f config/pppd_config/ppp/peers/* /etc/ppp/peers/

B.7.3 Starting Wanpi pe

1. Execute the following command to start the wanpipe:

# wanrouter start wanpipe1 # wanrouter start wanpipe2 # wanrouter start wanpipe3 # wanrouter start wanpipe4

2. Execute the following command to view the status of wanpipe:

(58)

The output of the above command is as shown below: Figure 33: Wanrout er Status

B.7.4 Configuring DHCP/DHCPD Server

DHCPD server runs automatically when PPP interface starts. However, the subnet range of PPP IP needs to be configured manually in DHCP configuration file. You can view the sample configuration file dhcpd. conf in the

/ home/ ml ppp_s cr i pt s/ dhcpd_ut i l directory.

The format in sample dhcpd. conf file for subnet range is as follows:

subnet X. Y. Z. 0 net mask 255. 255. 255. 0{r ange X. Y. Z. 50 X. Y. Z. 80; }

For example, if your PPP IP is 19.1.1.2 then add a subnet entry in dhcpd. conf file as follows:

subnet 19.1.1.0 netmask 255.255.255.0{ range 19.1.1.50 19.1.1.80;}

The above entry provides the IP in range of 19.1.1.50 to 19.1.1.80. This is an important entry, which is required to run the DHCPD server. In addition, dhcpd lease file should

(59)

For the first time, if configuration needs to be changed and PPP interface is already working; this indicates that the DHCP server is not responding for that interface. Therefore, you have to start the DHCP server manually by executing the following command:

# /home/mlppp_scripts/dhcpd_util/dhcpd -cf

# /home/mlppp_scripts/dhcpd_util/dhcpd.conf -lf # /home/mlppp_scripts/dhcpd_util/dhcpd.leases pppX

Note: In pppX, the X refers to the corresponding PPP interface. You can execute the following command to check the interface:

# ifconfig pppX

After that, the DHCP server restarts automatically with PPP interface.

After successfully configuring the DHCP server, you need to perform the following checks:

1. Every time you restart the system, execute the following command:

# iptables stop

2. In case any port of wanpipe shows the connected status, then you need to check whether corresponding pppd instances for that port is started or not by executing the following command:

(60)

3. Check for pppd instances with particular isp_wanpipeX as follows:

a. If PORT 1 is connected : isp_wanpipe range is <1-31>

b. If PORT 2 is connected : isp_wanpipe range is <32-62>

c. If PORT 3 is connected: isp_wanpipe range is <63-93>

d. If PORT 4 is connected: isp_wanpipe range is <94-124>

4. After successful configuration from BSC (or peer node), check whether pppX interface is created on host side or not. Here, X can be any integer starting from zero.

Generally, X is 0 or 1.

Execute the following command:

# ifconfig ppp0

The output of the above command is as shown below: Figure 34: ifconfi gpppX Output

B.8 Wanpipe Utilit ies

In order to trace the wanpipe incoming packets, you can use the wanpipemon utililty at the host side. For example,

(61)

Syntax:

# wanpipemon -i w<X>g<N> -u 9000 -c ti where X denotes Sangoma port number (1-4) and N denotes timeslots (currently, 1-8 are valid).

Example:

# wanpipemon -i w1g1 -u 9000 -c ti

For probing trunkport alarms, there is another command that uses wanpipemon utililty:

Syntax:

# wanpipemon -i w<X>g<N> -u 9000 -c ta Example:

# wanpipemon -i w1g1 -u 9000 -c ta