Installation Guide for packetfenceFull description
Full description
After reading the tips of Installation (for technicians and engineers only) will be able to fit kits at your own risk successfully. these tips only for the persons who have knowledge about the wiri...Full description
Descripción: Tru64 Unix Installation Guide
this guide describe in detail how to install openbts.Full description
Full description
tutorial siae
Software installation guide for SimulaytFull description
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 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 Reference Number Agile # VNL-OMC-ITG-000001
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 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 Reference Number Agile # VNL-OMC-ITG-000001
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.
Any option that needs to be selected or typed in the user interface is represented using 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
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
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:
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:
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.
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
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.
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:
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”.
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:
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 group tag. 5. Replace the tag
name=" openwi r e" ur i =" t cp: / / l ocal host : 61616" di scover yUr i =" mul t i cast : / / def aul t " / >with
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 minutes (approx. 1 minute).
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:
The above output confirms that the server is running successfully. ®
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 third party software application is running on the system as this can disrupt the performance of the scripts. You
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
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
Note: Click No to stop the OMC uninstallation procedure.
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:
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 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 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
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:
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).
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 b etween 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. The following figure provides you the connection layout of the BSC node and remote OMC system:
Note: MLPPP 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 Versi Versi on Check
B.4 MLPPP Deliverable VNL®L provides you the MLPPP- 1. 1. 1. 0. 003. 003. t ar . gz file, which contains the following folders in the Bi n directory: config
•
dhcpd_util
•
etc
•
modules
•
pppd
•
rpmbuild
•
wanpipe-3.3.1
•
•
install_el5.sh
pppd_spawn_port(1..4)
•
Save the MLPPPLPPP- 1. 1. 1. 0. 0. 00 003. t ar . gz gz t ar . gz gz file at the desired location, for example, in the / hom home/ ML PPP directory.
B.4.1 B.4.1 Extracti Extracti ng B in Folder You need to untar the MLPPP- 1. 2. 2. 0. 005. 005. t ar . gz file to extract the Bi n folder. 1. Execute the following command command to untar the file: Syntax: