OMC
Installation Guide
2.4.3
OMC I
NST AL L ATI O N
UI DE
Copyright
VNL 2010-2011 All Rights Reserved
Disclaimer
No part of this document may be reproduced in any form
without the written permission of the copyright owner.
The contents of this document are subject to revision
without notice due to continued progress in methodology,
design, and manufacturing. VNL shall have no liability for
any error or damage of any kind resulting from the use of
this document.
Trademark List
WorldGSMTM is a trademark owned by Vihaan Networks
Limited. All other product or service names mentioned in this
document are trademarks of their respective companies.
Document Reference Number
Agile # VNL-OMC-ITG-000001
Page 2
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
Contents
1. About This Document ....................................................... 8
1.1 Purpose ............................................................................ 8
1.2 Intended Audience ............................................................ 8
1.3 Document Conventions..................................................... 8
1.4 Terms and Abbreviations .................................................. 9
1.5 References ....................................................................... 9
2. Overview ........................................................................... 10
2.1 System Requirements..................................................... 10
3. Pre-Installation Settings .................................................. 11
4. OMC Installation Procedure ............................................ 13
4.1 Installing OMC using Installation Wizard......................... 13
5. Post-Installation Settings ................................................ 24
5.1 Host Entries .................................................................... 24
5.2 FTP Server ..................................................................... 24
5.3 ActiveMQ Manual Configuration ..................................... 25
6. OMC Scripts ..................................................................... 26
6.1 The rstrl Script ................................................................ 26
6.2 The omcStatus Script...................................................... 27
6.3 The stopOMC Script ....................................................... 28
6.4 Client Startup Script ........................................................ 28
6.5 Basic Checks .................................................................. 28
7. OMC Uninstallation Procedure ....................................... 30
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 3
OMC I
NST AL L ATI O N
UI DE
Appendix.A Installing OMC Client on a Separate System 33
Appendix.B MLPPP Installation.......................................... 36
Page 4
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
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
Figure 21: MLPPP Directory Contents ..................................... 41
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 5
OMC I
NST AL L ATI O N
UI DE
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
Figure 35: Wanpipemon Output ............................................... 61
Page 6
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
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
Table 6: Supported Versions .................................................... 38
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 7
OMC I
NST AL L ATI O N
UI DE
1. About This Document
1.1 Purpose
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 Document Conventions
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.
Page 8
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
File/directory
All courier new
names
Bold font
Any option that needs to be
selected or typed in the user
interface is represented using
bold font.
1.4 Terms and Abbreviations
The different terms and abbreviations used in this document
are explained in the following table:
Table 2: Terms and Abbreviations
Terms / Abbreviations
Description / 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
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 9
OMC I
NST AL L ATI O N
UI DE
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
Note: 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.
Page 10
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
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:
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 11
OMC I
NST AL L ATI O N
UI DE
# echo $CLASSPATH
a. If it is set then execute the following command to
unset the classpath environment variables:
# unset $CLASSPATH
Page 12
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
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-Linux-x86-Install.
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:
# ./<file_name>
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 13
OMC I
NST AL L ATI O N
UI DE
Example:
# ./OMC-5.6.3.002-Linux-x86-Install
The following message appears:
Figure 1: OMC Installation
2. Click Yes to continue installation.
The OMC installation wizard screen appears.
Figure 2: OMC Installation Wizard
Note: Click Cancel to exit the installation wizard.
3. Click Next > to continue.
Page 14
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
The following screen appears that allows you to select the
location where you want to install OMC:
Figure 3: OMC Installation Location
Note: Click < Back to return to previous wizard screen.
4. Click Next > to install the OMC in the default location
(/usr/local/OMC). Otherwise, you can click the
Browse button to choose a desired location where you
want to install OMC.
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 15
OMC I
NST AL L ATI O N
UI DE
Figure 4: Browse Location
Note: Click Make New Folder 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
Page 16
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
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 Information
6. Provide the information of the database in the given
fields:
Table 3: Database Information
Field Name
Description
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.
Administrative Password
VNL 2010-2011, All rights reserved
Password for Postgres user created
Commercial in Confidence
Page 17
OMC I
NST AL L ATI O N
UI DE
while installing Postgres.
Port where DB is
Specify the port number where Postgres
Running
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/local/pgsql/omcdata.
7. Click Next >.
The following screen appears that allows you to provide the
server related information:
Page 18
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
Figure 7: Server Information
8. Provide the information of the server in the given fields:
Table 4: Server Fields Description
Field Name
Description
OMC Server
Specify the OMC server name.
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.
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 19
OMC I
NST AL L ATI O N
UI DE
ACTIVE MQ
Specify IP address of the system where
Server IP
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: Servlet Fields Description
Field Name
Description
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.
11. Click Next >.
Page 20
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
The following screen appears that allows you to select the
nodes that you want to support:
Figure 9: Supported 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:
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 21
OMC I
NST AL L ATI O N
UI DE
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
Page 22
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
After successfully unpacking and copying the program files,
the following screen appears:
Figure 12: Successful Installation 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.
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 23
OMC I
NST AL L ATI O N
UI DE
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 servers /etc/hosts 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:
Page 24
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
# chkconfig gssftp off
5.3 ActiveMQ Manual Configuration
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 activemq home path by executing the following
command:
# cd $ACTIVEMQ_HOME/conf
3. Open the activemq 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 <transportConnector
name="openwire"
uri="tcp://localhost:61616"
discoveryUri="multicast://default"/> with
<transportConnector name="openwire"
uri="tcp://localhost:61616?wireFormat.
maxInactivityDuration=0"/>
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 25
OMC I
NST AL L ATI O N
UI DE
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 Server folder of
OMC installation directory.
This section also describes how to start and stop the OMC
client.
6.1 The rstrl Script
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 rstrl, go to Server 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
minutes (approx. 1 minute).
Page 26
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
6.2 The omcStatus Script
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 omcStatus, go to Server folder of the OMC
installation directory and execute the following command:
Command:
# ./omcStatus
Output:
The above output confirms that the server is running successfully.
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 27
OMC I
NST AL L ATI O N
UI DE
6.3 The stopOMC Script
You can use this script to stop all the OMC processes,
including the rstrl script.
1. To start stopOMC, go to Server 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 Client 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 Server and Client folder of the OMC
installation directory.
Always execute the scripts as a root user.
After running the OMC scripts, ensure sure that no other
third party software application is running on the system
as this can disrupt the performance of the scripts. You
Page 28
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
can use the following debugging tools to debug the
network errors:
o Wireshark
o Ethereal
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 29
OMC I
NST AL L ATI O N
UI DE
7. OMC Uninstallation Procedure
This section describes the procedure to uninstall the 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_Install_Dir 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 Uninstallation
Note: Click No to stop the OMC uninstallation procedure.
Page 30
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
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.
The following screen appears:
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 31
OMC I
NST AL L ATI O N
UI DE
Figure 15: Removing the Files
The following screen appears after successfully uninstalling
the OMC:
Figure 16: OMC Uninstallation Complete
5. Click Finish to complete OMC uninstallation and to close
the wizard.
Page 32
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
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 Requirements
The system requirements for installing OMC client on a
separate system are as follows:
Hardware Requirement
2 GB RAM
Software Requirement
JRE: 1.6.0 Update 12
OS: Windows (XP, 2000), Linux PC (RHEL 5.5
Enterprise Edition)
A.2 Prerequisites
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
system.
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 33
OMC I
NST AL L ATI O N
UI DE
A.3 Steps to Install OMC Client
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/local/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 /etc/hosts file to ensure that the first line in the
file is:
Page 34
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
<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).
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 35
OMC I
NST AL L ATI O N
UI DE
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 Communication 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 cards driver and wanpipe communicates with
the PPP drivers, which communicate with BSC node by
using E1.
The following figure provides you the connection layout of
the BSC node and remote OMC system:
Page 36
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
Figure 17: Communication 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.
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 37
OMC I
NST AL L ATI O N
UI DE
Figure 18: MLPPP Installation Procedure
B.3 Drivers Supported Versions
The subsequent table lists the supported versions of the
following components:
Table 6: Supported Versions
Page 38
Component
Version
EL5 Kernel Version
2.6.18-194PAE.el5
PPP version
2.4.4.4
Platform
i386
Wanpipe
3.3.1
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
Note: MLPPP installation is supported only for kernel
version specified in the above table.
You can verify the kernel version of your Linux operating
system by executing the following command:
# uname -r
The output of the above command should be as shown
below:
Figure 19: Kernel Version Check
B.4 MLPPP Deliverable
VNLL provides you the MLPPP-1.1.0.003.tar.gz file,
which contains the following folders in the Bin directory:
config
dhcpd_util
etc
modules
pppd
rpmbuild
wanpipe-3.3.1
install_el5.sh
pppd_spawn_port(1..4)
Save the MLPPP-1.1.0.003.tar.gz tar.gz file at the
desired location, for example, in the /home/MLPPP
directory.
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 39
OMC I
NST AL L ATI O N
UI DE
B.4.1 Extracting Bin Folder
You need to untar the MLPPP-1.2.0.005.tar.gz file to
extract the Bin folder.
1. Execute the following command to untar the file:
Syntax:
# tar <option> <filename>
Example:
# -xvf MLPPP-1.1.0.003. tar-xvf
The output of the above command is as shown in the
following figure:
Figure 20: Untar MLPPP-1.1.0.003.tar.gz
After executing the above command, the Bin folder is
created in the MLPPP directory.
2. Execute the following command to view the contents of
the MLPPP directory:
# ls -l
Page 40
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
The output shows the Bin folder.
Figure 21: MLPPP Directory Contents
3. Go to Bin directory and execute the following command:
# ls -l
The output is as shown below:
Figure 22: Bin Folder Contents
B.5 Wanpipe Drivers Installation
This section describes the installation procedure of wanpipe
drivers.
B.5.1 Uninstalling Previous version
You should check for the previous installation of wanpipe in
the system before starting a new installation.
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 41
OMC I
NST AL L ATI O N
UI DE
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 Information
B.5.1.1 Check Previous Wanpipe Installation using 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.
Figure 24: Wanpipe Package
Page 42
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
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:
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 43
OMC I
NST AL L ATI O N
UI DE
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:
Page 44
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
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 Wanpipe Installation without using 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:
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 45
OMC I
NST AL L ATI O N
UI DE
# 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>
X refers to wanpipe1, wanpipe2, wanpipe3, or wanpipe4
depending upon the respective running wanpipe.
Page 46
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
Example:
# wanrouter stop wanpipe2
ii. Execute the following command to go to
wanpipe 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 Installing Wanpipe
Perform the following steps to install the wanpipe:
1. Open the terminal, go to Bin 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
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 47
OMC I
NST AL L ATI O N
UI DE
Example:
# rpm -ivh --force rpmbuild/wanpipe3.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: Rpmbuild Wanpipe
B.6 PPP Installation
This section describes the installation procedure of the PPP
daemon. You need to install the PPP drivers before
installing the PPP daemon.
B.6.1 Installing PPP Drivers
Perform the following steps to install the PPP drivers:
1. Go to Bin directory by executing the following command:
# cd Bin
2. Execute the following command to install the ppp drivers:
Page 48
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
# . ./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_generic.ko, ppp_synctty.ko, and
slhc.ko files in lib/modules directory. Perform the
following steps to search these files:
a. Go to /lib/modules/<EL5 kernel
version>/extra/ directory and execute the
following command:
# find . -name ppp_generic.ko *
The output of the above command is as shown below:
Figure 26: Searching Files
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 49
OMC I
NST AL L ATI O N
UI DE
Similarly, execute the find command to search the remaining
two files.
2. Compare checksum of these files with the files stored in
the Bin/modules directory.
The md5sum of the above listed modules should match with
the modules contained in modules directory in the Bin
folder. Perform the following steps to compare checksum of
files:
a. Go to lib/modules/extra 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: md5sum Check
b. Go to Bin/modules directory and execute the
following command:
# md5sum ppp_generic.ko
The output of the above command is as shown below:
Page 50
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
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 Installing 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 Bin 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/include/pppd to
/usr/local/include/pppd/ by using the following
command:
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 51
OMC I
NST AL L ATI O N
UI DE
# 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/lib/pppd/<version> to
/usr/local/lib/pppd/<version> 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/sbin/ to
/usr/local/sbin/ by executing the following
command:
# cp -f pppd/sbin/* /usr/local/sbin/
Page 52
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
8. Copy all the files from location
/pppd/share/man/man8 to
/usr/local/share/man/man8/ by executing the
following command:
# cp -f pppd/share/man/man8/*
/usr/local/share/man/man8
B.6.2.1 Basic Checks
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
pppd_spawn utilities are running:
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 53
OMC I
NST AL L ATI O N
UI DE
# 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:
Page 54
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
Figure 32: Wanrouter Hwprobe Output
Note: Here, the X and Y refer to the respective systems
slot number and bus number on which Sangoma card is
installed.
B.7 MLPPP Configuration
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 Bin directory and execute the following command:
# unalias cp
2. Copy all the files from location
config/wanpipe_config/wanpipe/wanpipe to
/etc/wanpipe by executing the following command:
# cp -f
config/wanpipe_config/wanpipe/wanpipe/*.conf
/etc/wanpipe
3. Execute the following command:
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 55
OMC I
NST AL L ATI O N
UI DE
# 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 /etc/wanpipe/wanpipeZ.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 Configuring PPPD
1. Execute the following commands to copy all files from
Bin directory to etc 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 Wanpipe
1. Execute the following command to start the wanpipe:
#
#
#
#
wanrouter
wanrouter
wanrouter
wanrouter
start
start
start
start
wanpipe1
wanpipe2
wanpipe3
wanpipe4
2. Execute the following command to view the status of
wanpipe:
# wanrouter status
Page 56
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
The output of the above command is as shown below:
Figure 33: Wanrouter 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/mlppp_scripts/dhcpd_util directory.
The format in sample dhcpd.conf file for subnet range is
as follows:
subnet X.Y.Z.0 netmask 255.255.255.0{range
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
already be created as mentioned in above steps.
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 57
OMC I
NST AL L ATI O N
UI DE
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.
B.7.4.1 Basic Checks
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:
# ps -ef | grep pppd
Page 58
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
3. Check for pppd instances with particular isp_wanpipeX as
follows:
a. If PORT 1 is connected : isp_wanpipe range is <131>
b. If PORT 2 is connected : isp_wanpipe range is <3262>
c. If PORT 3 is connected: isp_wanpipe range is <6393>
d. If PORT 4 is connected: isp_wanpipe range is <94124>
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: ifconfigpppX Output
B.8 Wanpipe Utilities
In order to trace the wanpipe incoming packets, you can use
the wanpipemon utililty at the host side. For example,
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 59
OMC I
NST AL L ATI O N
UI DE
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
The notation is same as above and the output is:
Page 60
Commercial in Confidence
VNL 2010-2011, All rights reserved
OMC I
NST AL L ATI O N
UI DE
Figure 35: Wanpipemon Output
Note: The wanrouter status command shows connected
if all the alarms are off. Otherwise, check the trunkport
connectivity.
VNL 2010-2011, All rights reserved
Commercial in Confidence
Page 61