TJ5100 R6.1.3.5 Installation and Commissioning Guide

TJ5100 R6.
1 Installation and
Commissioning Guide
Document ID: 400-DOC000090-E Release: Standard Release Version: 1.0
www.tejasnetworks.com
Copyright Notice
Copyright 2000-2017. Tejas Networks Ltd. All rights reserved. No part of this book or manual may be
reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying,
recording, or by any information storage and retrieval system, without the express written permission from
Tejas Networks Ltd.
Warning and Disclaimer
While every effort has been made to make this document as complete and as accurate as possible, Tejas
Networks does not accept any responsibility for poorly designed or malfunctioning networks. The information
provided in this document is on an as is basis and is subject to change without prior notice. The author,
Tejas Networks, shall have neither liability nor responsibility to any person or entity with respect to any loss or
damage arising from the information contained in this document or from the use of equipment or software
that might accompany it. The opinions expressed in this document are not necessarily those of Tejas Networks.
Trademark Acknowledgments
All terms mentioned in this book that are known trademarks or service marks have been appropriately
capitalized. All trademarks duly acknowledged. Tejas Networks cannot attest to the accuracy of third-party
information. Use of a term in this document should not be regarded as affecting the validity of any trademark
or service mark.
Technical Support Information
Tejas customers can contact Tejas Support Center (TSC) 24x7x365 for any assistance through helpline, fax or
email.
- Phone(s): +91 80 41719090/91/92/93/94/95
- Email: support@tejasnetworks.com
- Skype: tscsupport123
- Web: www.tejasnetworks.com
Revision History
Version Date Modifications Made
1.0 20-Feburary-2017 R6.1.3.5, Standard Release

Your Feedback is valuable to us!
Your opinion is of great value and will help us improve the quality of our product documentation
and offer better services to you. Please take few moments to provide us your opinion of this
document. Send your comments to docs@tejasnetworks.com
Presentation: (Introductions, Procedures, Illustrations, Completeness, Level of
Detail, Organization, Appearance)
Good Fair Average Poor Bad N/A
Your evaluation of this Intelligibility: (Language, Vocabulary, Readability and Clarity, Technical
document Accuracy, Content)
Accessibility: (Contents, Index, Headings, Numbering, Glossary)
Improve the Make it more Improve the

overview/introduction concise/brief Contents
Add more step-by-step Improve the Add more
Your suggestions for procedures/ tutorials organization troubleshooting
improving this information
document Include more figures Make it less technical Add more examples
Add more/better Add more detail Improve the index

quick reference aids
Other Suggestions:
If you wish to be contacted regarding your comments, please provide your contact details:
Name: Company:
Postcode: Address:
Telephone: Email:
Table of Contents
Using This Guide 9
What This Guide Covers ............................................................................................................... 9
Who This Guide Is For ................................................................................................................. 9
What You Should Already Know ................................................................................................ 9
Mouse Operation Conventions .................................................................................................. 10
Safety Signs Conventions ............................................................................................................ 11
Typographical Conventions ........................................................................................................ 12
Chapter Organization................................................................................................................... 12
Using Tejas Product Documentation ........................................................................................ 13
Related Documents ...................................................................................................................... 13
Understanding Hardware and Software Requirements 15

TJ5100/TJ5500 Installation Modes and Scalability ................................................................. 16
Software Installation Package ..................................................................................................... 18
Server System Requirements ....................................................................................................... 19
Client System Requirements ....................................................................................................... 19
VMWare ESX Server and vSphere 5.0 Client Installation 21

Assigning a VMWare License using vSphere 5.0 Client ......................................................... 21
Configuring and Setting Up VMs ............................................................................................... 22
HT Disabled Mode .................................................................................................................. 23
HT Enabled Mode ................................................................................................................... 25
Linux Server Configuration 29

Server Partition ............................................................................................................................. 29
TCP/UDP Ports Used by EMS ................................................................................................. 30
Configuring IP Address ............................................................................................................... 31
Setting Host Name ....................................................................................................................... 31
Prerequisites for launching the EMS application ..................................................................... 33
TJ5100 R6.1 Server Installation 35

Before Installation ........................................................................................................................ 35
Installing TJ5100 R6.1 Server Software..................................................................................... 35
Post-Installation Tasks ................................................................................................................. 41
Installing TJ5100/TJ5500 in Co-Residency Mode .................................................................. 42
Installation Guidelines .............................................................................................................. 42
iv
Installation Procedure ................................................................................................................ 42
Points to Remember................................................................................................................... 51
Uninstalling TJ5100 in Standalone Mode ................................................................................. 52
Uninstalling TJ5500/TJ5100 Server Software in Co-Residency Mode ................................ 53
TJ5100 Server (Start/Stop/Status) ............................................................................................. 55
License Management .................................................................................................................... 58
TJ5100 R6.1 Client Installation 59

Installing TJ5100 R6.1 Client Software ..................................................................................... 60
Java Installation ........................................................................................................................ 60
GNOME User ........................................................................................................................ 60
KDE User ............................................................................................................................... 60
Launching TJ5100 R6.1 Client ............................................................................................... 60
Launching TJ5100 R6.1 Java Web Client .................................................................................. 61
Launching the TJ5100 EMS Web Client ................................................................................ 62
Viewing Server Process Status ................................................................................................... 63
EMS Health Check ................................................................................................................. 64
NTP Chaining 65
Configuring a Linux Machine as the NTP Server .................................................................... 66
Configuring a Linux Machine as an NTP Client Syncing to Another Standard NTP Sever67
Configuring a Linux Machine as an NTP Client Syncing to Another Linux Server .......... 68
Configuring the Tejas NEs to Sync to a Linux Server ............................................................ 68
Troubleshooting NTP Synchronization .................................................................................... 69
Querying Any Time Server Status ............................................................................................. 69
Verifying if Packets are Going Out and Coming Back .............................................................. 70
Configuring NTP at Startup..................................................................................................... 70
Starting and Stopping the ntpd Service ....................................................................................... 71
Comparing the Time Difference Between the NTP Server and the Client .................................... 71
Manually Setting the Date and Time......................................................................................... 71
Build Details 73
Glossary of Terms 75
Index 79
v
List of Figures
Figure 1: Assigning License ................................................................................................................ 22
Figure 2: Standard License Features .................................................................................................. 23
Figure 3: Machine Configuration with HT Disabled ...................................................................... 23
Figure 4: Core Assignment in HT Disabled Mode ......................................................................... 24
Figure 5: Top Output of VM Listing 8 Cores .................................................................................. 24
Figure 6: Licensed Features ................................................................................................................ 25
Figure 7: Processors Configuration ................................................................................................... 26
Figure 8: Core Assignment ................................................................................................................. 27
Figure 9: Top Output of 16 Cores ..................................................................................................... 28
Figure 10: Setting Host Name ............................................................................................................ 32
Figure 11: TJ5100 Installation Files ................................................................................................... 35
Figure 12: Running script & setting Ethernet interface .................................................................. 36
Figure 13: Install EMS ......................................................................................................................... 36
Figure 14: MySQL Version 5.7 Installation ...................................................................................... 36
Figure 15: Setting EMS Name ............................................................................................................ 37
Figure 16: Setting EMS application mode ........................................................................................ 37
Figure 17: Allowing Concurrent user login ...................................................................................... 37
Figure 18: NBI over NAT prompt .................................................................................................... 37
Figure 19: Running TJ5100 service at startup .................................................................................. 38
Figure 20: TJ5100 installation mode.................................................................................................. 38
Figure 21: Setting Hot Standby type.................................................................................................. 38
Figure 22: Setting IP Addresses for Hot Standby mode ................................................................ 38
Figure 23: Setting Hot Standby priority ............................................................................................ 38
Figure 24: Setting Ethernet Interface ................................................................................................ 39
Figure 25: Setting Virtual IP Address ................................................................................................ 39
Figure 26: Setting Net Mask Address ................................................................................................ 39
Figure 27: Setting Mac Address for NIC .......................................................................................... 39
Figure 28: Setting EIA number .......................................................................................................... 39
Figure 29: Checking MySQL-Perl module status ............................................................................ 39
Figure 30: Kannel Installation message ............................................................................................. 40
Figure 31: Background map selection ............................................................................................... 40
Figure 32: Copying License file .......................................................................................................... 40
Figure 33: Running TJ5100 service.................................................................................................... 40
Figure 34: EMS Installation Successful ............................................................................................. 40
Figure 35: TJ5100 Installation Files ................................................................................................... 42
Figure 36: Setting Ethernet interface ................................................................................................. 43
Figure 37: Selecting Installation Option ........................................................................................... 43
Figure 38: Running TJ5100 TJ5500 services at startup .................................................................. 43
Figure 39: Reconfiguring MySQL password .................................................................................... 44
Figure 40: Setting EMS Name ............................................................................................................ 44
Figure 41: Setting EMS application mode ........................................................................................ 44
Figure 42: User EMS password .......................................................................................................... 44
Figure 43: Setting concurrent user login ........................................................................................... 44
vi
Figure 44: Setting NAT over NBI ..................................................................................................... 45
Figure 45: Installing TJ5100 in HotStandBy mode ......................................................................... 45
Figure 46: Installing TJ5100 in Standalone mode............................................................................ 45
Figure 47: Setting type for Hot Stanby mode .................................................................................. 45
Figure 48: Setting Hot Standby server IP Addresses ...................................................................... 45
Figure 49: Setting Hot Standby priority ............................................................................................ 46
Figure 53: Setting MAC Address ....................................................................................................... 46
Figure 54: Setting Ethernet Interface Alias Number for TJ5100 .................................................. 46
Figure 55: MySQL-Perl Module status.............................................................................................. 47
Figure 56: Kannel Installation message ............................................................................................. 47
Figure 57: Background map selection ............................................................................................... 47
Figure 58: TJ5100 Installation completed successfully message ................................................... 47
Figure 59: Initiation of TJ5500 installation....................................................................................... 48
Figure 63: Setting MAC Address ....................................................................................................... 49
Figure 64: Setting Ethernet Interface Alias Number for TJ5500 .................................................. 49
Figure 65: Finalization & installation completed successfully ....................................................... 50
Figure 66: Copying the license file ..................................................................................................... 50
Figure 67: Running TJ5100 uninstallation script ............................................................................. 52
Figure 68: Deleting TJ5100 database prompt .................................................................................. 52
Figure 69: Clearing Log files prompt ................................................................................................ 52
Figure 70: Uninstalling ActiveMQ prompt ...................................................................................... 52
Figure 71: TJ5100 uninstallation complete message ....................................................................... 52
Figure 72: Running Uninstallation script .......................................................................................... 53
Figure 73: Removing Database prompt ............................................................................................ 53
Figure 75: Uninstalling Activemq prompt ........................................................................................ 53
Figure 76: TJ5100 uninstallation complete message ....................................................................... 54
Figure 77: TJ5500 Uninstallation initiation ...................................................................................... 54
Figure 79: Clearing configuration files prompt ................................................................................ 54
Figure 80: Clearing documentation files prompt ............................................................................. 54
Figure 81: Uninstalling Activemq prompt ........................................................................................ 54
Figure 82: Uninstalling tomcat prompt ............................................................................................. 55
Figure 83: TJ5500 Uninstallation complete message ...................................................................... 55
Figure 84: Checking TJ5100/TJ5500 service status ........................................................................ 55
Figure 85: TJ5100 Element Management System (EMS) Application window .......................... 61
Figure 86: Server Process Status ........................................................................................................ 63
Figure 87: NTP Client Configuration................................................................................................ 67
Figure 88: NTP Server Configuration ............................................................................................... 68
Figure 89: NE as NTP Client ............................................................................................................. 69
Figure 90: NTP Server Status ............................................................................................................. 69
Figure 91: Starting and Stopping the ntpd service........................................................................... 71
Figure 92: Checking Time Difference ............................................................................................... 71
vii
List of Tables
Table 1: Mouse Operation ............................................................................................................... 10
Table 2: Safety Sign Convention..................................................................................................... 11
Table 3: Typographical Conventions ............................................................................................. 12
Table 4: Supported configurations based on number of NEQs in Standalone mode ........... 16
Table 5: Supported configurations based on number of NEQs in Virtualized mode............ 17
Table 6: Supported configurations based on number of NEQs in Multiple Standalone mode17
Table 7: Supported configurations based on number of NEQs in Clustering mode ............. 17
Table 8: Supported configurations based on number of NEQs in Co-Residency mode ...... 18
Table 9: Software Installation Package .......................................................................................... 18
Table 10: Server System Requirements (64-Bit) ............................................................................. 19
Table 11: Client System Requirements ............................................................................................ 19
Table 12: Server Partition .................................................................................................................. 29
Table 13: List of commands .............................................................................................................. 33
Table 14: Generic Commands .......................................................................................................... 56
Table 15: Process Management ........................................................................................................ 56
Table 16: Server Process Status parameters .................................................................................... 64
Table 17: Build Details ....................................................................................................................... 73
viii
Chapter 1
Using This Guide

This section describes who should read this guide, how it is organized, and what conventions are
used in the document.
IN THIS CHAPTER
What This Guide Covers .................................................................................. 9
Who This Guide Is For .................................................................................... 9
What You Should Already Know ................................................................... 9
Mouse Operation Conventions .....................................................................10
Safety Signs Conventions ...............................................................................11
Typographical Conventions ...........................................................................12
Chapter Organization .....................................................................................12
Using Tejas Product Documentation ...........................................................13
Related Documents .........................................................................................13
What This Guide Covers

TJ5100 is the Element Management Software (EMS) for Tejas Network Elements (NE)
products. This document provides information on hardware and software requirements for EMS
installation and also provides the procedure for EMS installation on the server.
Who This Guide Is For

This document is intended for Technician or Field engineers who install Element Management
Software (EMS) at the customer premises.
What You Should Already Know

Before you read this Guide you need to be comfortable working with:
Network Element Software (NES)
None of these topics are covered in this Guide. For information about these topics, refer to
respective user documentation.
9
TJ5100 R6.1 Installation and Commissioning Guide Document ID: 400-DOC000090-E
Mouse Operation Conventions

Table 1: Mouse Operation
Convention Description
Click Refers to pressing and releasing a mouse button to select a screen object.
Double-click Refers to pressing and releasing a mouse button twice in succession while the cursor
is positioned over an object on-screen.
Drag Refers to the function of the mouse by which an element on the screen of a monitor
is moved with the cursor, while holding down the mouse button and moving the
mouse.
Right-click Refers to pressing the right button on a two-button mouse.
Wheel button Refers to the third (middle) button on the mouse.
10
Chapter 1 Using This Guide
Safety Signs Conventions

To prevent personal injury, equipment damage, and service interruptions, you must follow all
precautionary messages given in the document in addition to all the local safety standards
required by your company. The following symbols inserted in the document at various places
represent important situations.
Table 2: Safety Sign Convention
Symbols Meaning Represents

Caution Situations that could result in equipment damage or loss of
data.
Danger Situation that could cause bodily injury. Failure to observe

this precaution may result in personal injury, death, or
equipment damage.
Hot Surface Situation that could result in bodily burns.
Optical Safety Staring directly into the optical connector output beam may
cause irreparable damage to your eyes and even leading to
loss of eye sight.
Electric Shock Risk Failure to observe this precaution may result in personal
injury, death, or equipment damage.
Static Discharge Handle the equipment wearing a grounding wrist strap to

Warning discharge the static buildup. Failure to observe this
precaution may result in equipment damage.
Rotating Part Keep fingers, screwdrivers, and other objects away from the
openings in the fan tray assembly. The fans might still be
turning when you remove the fan assembly from the chassis.
11
Typographical Conventions
Before you start using this guide, it is important to understand the terms and typographical
conventions used in the document. The following kinds of formatting in the text identify special
information.
Table 3: Typographical Conventions
Formatting Convention Type of Information
Procedures Step-by-step procedures. You can follow these instructions to

complete a specific task.
Special Bold Items you must select, such as menu options, command buttons,
or items in a list.
Emphasis Use to emphasize the importance of a point or for variable
expressions such as parameters.
CAPITALS Names of keys on the keyboard, for example, SHIFT, CTRL, or

ALT.
KEY+KEY Key combinations for which the user must press and hold down
one key and then press another, for example, CTRL+P, or
ALT+F4.
Means reader take note. Notes contain helpful suggestions or
NOTE: references to materials not contained in this manual.
Chapter Organization
This document is organized as follows:
Chapter Scope
Understanding Hardware and This chapter details the Server Hardware and the Software
Software Requirements on page 15 specifications for installing TJ5100 R6.1 software.
VMWare ESX Server and vSphere This chapter details the installation options and configurations
5.0 Client Installation on page 21 you need to do in case of TJ5100 running on VMware.
Linux Server Configuration on page This chapter describes the server partitions, configuring IP
29 address, and setting host name.
TJ5100 R6.1 Server Installation on This chapter describes procedure to install TJ5100 R6.1 server
page 35 software.
TJ5100 R6.1 Client Installation on This chapter describes procedure to install TJ5100 R6.1 client
page 59 software and to launch Java Web Client.
NTP Chaining on page 65 This chapter details NTP chaining configuration.
12
Chapter 1 Using This Guide
Using Tejas Product Documentation

The following Tejas product documentation set helps you use the range of Tejas products:
The Installation and Commissioning document provides information on installing the software
and to initially configuring it to the point of verifying its proper operation in the network.
The User Interface Guide introduces and orients service providers to the content, function, and
organization of EMS user interface.
Not all of the documents mentioned above may be applicable to the product you are using.
Please contact Tejas Support Center for any clarification in this regard.
Related Documents
Related documents need to be used in conjunction with the Customer Release Notes (CRN)
defining the scope of the release.
Document Name Tejas Part Number Description

TJ5100 R6.1 User 400-DOC000091-E This document introduces and orients service providers to
Interface Guide the content, function, and organization of the TJ5100 user
interface that support the network elements.
13
Chapter 2
Understanding Hardware and Software

Requirements
This chapter details the installation requirements for the EMS server and client systems.
IN THIS CHAPTER
TJ5100/TJ5500 Installation Modes and Scalability ...................................16
Software Installation Package ........................................................................18
Server System Requirements..........................................................................19
Client System Requirements ..........................................................................19
15
TJ5100/TJ5500 Installation Modes and Scalability

This section describes the various installation modes and the scalability supported by
TJ5100/TJ5500 based on the number of Node Element Equivalents (NEQs). The number of
NEQs for a node is calculated based on LO/HO, the number of STM/OC connections, VCGs,
E1 connections, and L2 features supported by the node, irrespective of the current traffic
through the node. To know the current weighted NEQs for the nodes managed by EMS, select
Tools > Nodes Information page.
You can install TJ5100/TJ5500 in the following modes:
Standalone Mode
In standalone mode, you can have only one instance of TJ5100/TJ5500 running on one physical
server. The number of NEQs supported by one instance of TJ5100/TJ5500 depends on the
hardware and software configuration of the physical server. The hardware requirements such as
RAM, HDD/RAID, and CPU Cores (with two sockets per processor) increase when the number
of NEQs that need to be managed increases.
Table 4: Supported configurations based on number of NEQs in Standalone mode
Maximum Recommended Minimum Minimum Minimum Disk Space EMS/NMS

Number of Server CPU Cores RAM Required Supported
NEQs Required Required
1000 IBM x3500 M4 or 8 8 GB 2*146GB HDD in RAID1 1 EMS only
higher
2000 IBM x3500 M4 or 8 8 GB 2*300 GB HDD in RAID1 1 EMS only
higher
3000 IBM x3500 M4 or 8 16 GB 2*300 GB HDD in RAID1 1 EMS only
higher
15000 IBM x3850 X6 or 16 40 GB 2*600 GB HDD in RAID1 1 NMS only
higher
30000 IBM x3850 X6 or 32 72 GB 2*1200 GB HDD in 1 NMS only
higher RAID1
Virtualized Mode
In virtualization mode using VMWare ESX Server, you can install more than one instance of
TJ5100/TJ5500 on a physical server. This mode supports virtualization of RAM, HDD/RAID,
and CPU Cores in one physical server by dividing the server into multiple virtual servers. Using
this technology, you can run different server applications such as TJ5100, TJ5500, or any other
third party software on a single physical server as though they are independent servers. However,
the hardware and software requirements have to match the standalone mode, for each instance of
TJ5100 or TJ5500.
16
Chapter 2 Understanding Hardware and Software Requirements
Table 5: Supported configurations based on number of NEQs in Virtualized mode
Recommended Cores RAM Disk Space Sockets per Minimum EMS/NMS Maximum
Server per per per Server Processor NIC Cards Instances Number of
Server Server Required Supported NEQs
1 IBM x3850 16 40 GB 4* 300GB 2 2 2 EMS 3000 per
X5 HDD in EMS
RAID1
1 IBM x3850 32 72 GB 8* 300GB 4 4 4 EMS (or) 3000 per
X5 HDD in EMS and
2 EMS +
RAID1 15000 per
1 NMS
NMS
Multiple Standalone Modes
You can have multiple standalone TJ5100 installed on a single blade center installing multiple
blade servers.
Table 6: Supported configurations based on number of NEQs in Multiple Standalone mode
Maximum Recommended Minimum Minimum Minimum Minimum EMS/NMS

Number of Server CPU Cores RAM Disk Space NIC Cards Supported
NEQs Required Required Required Required
3000 per 1 IBM HS22 8 per Blade 16 GB per 2* 300GB 1 per Blade 1 EMS per
Blade for Blade Center Blade HDD in Blade.
EMS RAID1 per (Up to 14
Blade Blades/Blade
Center
NOTE: In standalone mode, one instance of TJ5500 can manage only up to a maximum of
ten instances of TJ5100 or 30,000 NEQs whichever is higher.
Clustering Mode (Only for TJ5500)
Clustering mode is to scale NMS to manage beyond 30,000 NEQs and up to 60,000 NEQs. In
clustering mode, two physical servers work as one logical server. One physical server is used to
run the database and the second physical server is used to run the application. Database and
Application servers are components of the TJ5500 Network Management System.
Table 7: Supported configurations based on number of NEQs in Clustering mode

60,000 per 2 IBM x3850 32 per Server 72 GB per 2*1200 GB 1 per Server 1 NMS
NMS X5 Servers Server HDD in Instance
RAID1 per
Server
17
NOTE: In clustering mode, one instance of TJ5500 can manage only up to a maximum of
twenty instances of TJ5100 or 60,000 NEQs whichever is higher. To support more than
60,000 NEQs or more than twenty TJ5100 instances, you need to have multiple TJ5500
instances.
Clustering mode of installation cannot be used with co-residency mode.
Co-Residency Mode (TJ5100 and TJ5500 in One Server)
In co-residency mode, you can have both TJ5100 and TJ5500 installed on the same server. The
hardware and software requirements for such installation has to be double the capacity of a
standalone TJ5100 server or a standalone TJ5500 server. The hardware requirements such as
RAM, HDD/RAID, and CPU Cores (with two sockets per processor) increase when the number
of NEQs that need to be managed increases. For TJ5100 server software and hardware
requirements refer Server System Requirements. For TJ5500 server software and hardware
requirements refer "Chapter 3: Hardware/Software Requirements" of the document TJ5500
Installation and Commissioning Guide, TPN: 400-DOC000084-E.
Table 8: Supported configurations based on number of NEQs in Co-Residency mode

1000 1 IBM x3400 8 16 GB 2* 300GB 1 1 EMS and 1
M3 Server HDD in NMS
RAID1
Hot Standby Modes
In Hot Standby Mode, the active EMS/NMS setup can be replicated exactly to provide disaster
recovery. The server requirements should be exactly the same as for the active setup based on the
NEQ calculation.
Software Installation Package

Table below lists the software packages required in a 64-bit operating systems of the server for
EMS installation.
Table 9: Software Installation Package
Software 64-Bit O.S

Operating System RHEL server release 7.1
Java Development Kit (JDK) JDK 1.8.0_66
Java Runtime Environment (JRE) JRE 1.8.0_66
MySQL MySQL Version 5.7
Kannel kannel-1.4.2-1.el5.rf.x86_64.rpm
18
Chapter 2 Understanding Hardware and Software Requirements
Server System Requirements

Before you start installing EMS, ensure that your server meets the following hardware and
software requirements. The requirements vary based on the number of node equivalents (NEQs)
you want to manage using this version of EMS.
Table 10: Server System Requirements (64-Bit)
Components Specifications
Operating System RHEL server release 7.1

Web server Apache
Software
JDK(Java Development Kit) JDK 1.8.0_66
Database MySQL 5.7
Memory 8 GB physical memory (RAM) for 2000 NEQs
16 GB physical memory (RAM) for 3000 NEQs
Hardware Processor Dual processor Quad Core Intel 3.0 GHz or higher
8 cores each for 2000 and 3000 NEQs
Drive Configuration 2 * 300 GB 7200 RPM SCSI disk drive in RAID1
configuration
NOTE: For Hot Standby setup, you need to have two servers with same requirements as
mentioned in the above table. After installation of OS compare the Mozilla, Java and MySQL
versions with recommended versions. If the version is different, un-install the default versions
before installing the recommended versions.
Client System Requirements

Table 11: Client System Requirements
Minimum Client Specification Component Specification

Processor Intel Pentium Core 2 Duo E7500 (2.93 GHz,1066
MHz FSB, 3 MB L2 Cache)
Memory 4 GB Physical Memory (RAM)
Hardware 40 GB Hard Disk Drive
Client 19 inch TFT monitor supporting 1280x1024x87
Configuration resolution with "true color" graphics card of
1280x1024x87 resolution.
Client Software Recommended browser: Mozilla Firefox 38.8.0
for both Windows and RHEL platforms.
Software Platform JRE 1.8.0_66
Operating System Windows XP/Windows Vista/ Windows 7/Red
Hat Enterprise Linux 7.1
19
NOTE: If the machine is 64 bit, it will take 64-bit setup files for java, MySQL and Kannel
respectively.
20
Chapter 3
VMWare ESX Server and vSphere 5.0

Client Installation
To support virtualization of server hardware, you need to have VMWare ESX Server installed on
your EMS and NMS server before installing Linux OS. The version of the ESX server will
depend on the hardware configuration of the server and the VMWare ESX server requirements.
For more information on the version of ESX server software required, refer to the server
hardware and VMWare vendor documentation.
The sequence of installation is as follows:

1. Install VMWare ESX Server.
2. Install the corresponding VMWare vSphere Client and partition the physical server into
virtual servers.
3. Install Red Hat Linux OS (refer Linux OS RHEL7 update 1, TPN: 400-DOC000070-E).
4. Install TJ5100 (EMS) and/or TJ5500 (NMS).
This chapter provides the details of VMWare ESX server licensing changes, core assignment as
per recommendations for the TJ5100/TJ5500 application, steps to configure and test a couple
for feasible options for deployment of TJ5100/TJ5500 using vSphere 5.0 client.
IN THIS CHAPTER
Assigning a VMWare License using vSphere 5.0 Client............................21
Configuring and Setting Up VMs .................................................................22
Assigning a VMWare License using vSphere 5.0 Client

To assign license using vSphere 5.0 client,
1. Install vSphere 5.0 on the client.
2. Launch the vSphere 5.0 Client.
3. Go to Configuration page, select Licensed Features under Software group.
21
4. Click on Edit. The following window appears for assigning a license.

Figure 1: Assigning License
5. Select Assign a new license key to this host.

6. Click Enter Key and enter the key in the text box.
7. Click OK.
8. Reboot the Server.
Configuring and Setting Up VMs

VMWare supports the following deployment scenarios:
HT Disabled Mode: Assign 8 Cores to a VM with Hyper Threading (HT) Disabled (8 vCPUs)
using Standard License.
This scenario is recommended if you are already using EMS on VMWare.
HT Enabled Mode: Assign 8 Cores to a VM with HT Enabled (16 vCPUs) using Enterprise
Plus License.
This scenario is recommended for all deployments.
22
Chapter 3 VMWare ESX Server and vSphere 5.0 Client Installation
HT Disabled Mode
To set up VMWare in HT disabled mode using the Standard License, follow these steps:
2. Select the Licensed Features as shown below.
Figure 2: Standard License Features
3. Select the Processors configuration as shown below. For example, HP Server with 4
Processors of 4 Core. This means, 16 cores in total.
Figure 3: Machine Configuration with HT Disabled
23
4. Select the core assignments as below. It is recommended to select only 8 vCPUs. Even
though 16 vCPUs are listed in the drop-down list, the system gives an error if you select 16
vCPUs while using the Standard License.
Figure 4: Core Assignment in HT Disabled Mode
5. Verify that on Guest OS 8 cores are seen in top output.

Figure 5: Top Output of VM Listing 8 Cores
24
HT Enabled Mode
To set up VM Ware in HT enabled mode using the Enterprise Plus License, follow these steps:
2. Select the Licensed Features as shown below.
Figure 6: Licensed Features
25
3. Select the Processors Configuration as shown below. For example, HP Server with 4
Processors of 4 Core. This means, 16 cores in total. In HT Enabled Mode, the number of
logical processors that can be enabled is up to 32.
Figure 7: Processors Configuration
26
4. Select the number of cores. You can assign up to 16 cores in HT Enabled mode.
Figure 8: Core Assignment
27
5. Verify that there are up to 16 cores seen in top output.

Figure 9: Top Output of 16 Cores
28
Chapter 4
Linux Server Configuration

This chapter describes about the set of operations to be done before installing the TJ5100
software. You have to follow the below mentioned partitioning on the server during installation.
The TJ5100 R6.1 installation requires RHEL server release 6.4 (Santiago) for 64 Bit Operating
System with the partitions as mentioned in the partition table. For installing Linux OS, refer to
the document, Linux OS RHEL7 update 1, TPN: 400-DOC000070-E.
IN THIS CHAPTER
Server Partition ................................................................................................29
TCP/UDP Ports Used by EMS ....................................................................30
Configuring IP Address ..................................................................................31
Setting Host Name ..........................................................................................31
Prerequisites for launching the EMS application .......................................33
Server Partition
Partition the Linux server HDD (Hard Disk Drive) as shown below:
Table 12: Server Partition
Partition Data Stored Size (Recommended Size for Recommended ratio for other
300 GB HDD for 2000/3000 NEQ in Percentage (%)
NEQ (GB)
/ OS related file and 100 GB 40
temporary directory
/var EMS Database, 60 GB 16
Performance monitoring
data, and MySQL/Syslog
log files
/opt EMS Software and EMS 40 GB 16
log files
/home Hot Standby backup, NE 60 GB 16
scripts, and user data
/swap For paging of processes Minimum of double the RAM Minimum of double the RAM
Size Size
29
TCP/UDP Ports Used by EMS

In case of firewall between EMS Server and clients, all ports with direction of establishment of
connection as Client to Server or Server to Client need to be opened up. Similarly, in case of
firewall between EMS Server and the node, all ports with direction of establishment of
connection as node to EMS Server or EMS Server to node need to be opened up.
The following table lists the ports used by the EMS Server:
Protocol Port Service Name Direction of Establishment of Connection

TCP 21 VSFTP Node to server , Server to Node, Between
servers in Hot Standby setup
UDP 161, 162 SNMP Traps Node to server
TCP 61513 ActiveMQ EMS to north bound
TCP 10990 ActiveMQ ActiveMQ JMX server internal
TCP 55300-55501 EMSServer, TMFDomain, Client to Server and Server to Client
Performance Domain
TCP 20900 NamingService Client to Server
TCP 10000 NotifyService Server Internal
TCP 10001 EMSServer Server Internal
TCP 10005 Hot Standby Server Internal
TCP 8501 EMSServer Server Internal
TCP 8502 Hot Standby Server Internal
TCP 10003 TMFDomain Server Internal
TCP 8552 TMFDomain Server Internal
TCP 10004 PerformanceDomain Server Internal
TCP 8560 PerformanceDomain Server Internal
TCP 22 Secure Shell Client to Server for debugging
TCP 443 HTTPs Server to Node and Client to Node
TCP 20080 HTTP Server to Node and Client to Node
TCP 2023 Telnet Server to Node and Client to Node
TCP 30000 EMSServer Slave to Master
TCP 3306 MySQL Server Internal
TCP 2100 AppManager Server Internal
TCP 20800 HotStandby Between Servers
TCP 80 HTTPD Client to Server
30
Chapter 4 Linux Server Configuration
Protocol Port Service Name Direction of Establishment of Connection

TCP 10059 Node debugging port EMSServer to Node and Client to Node (for
debugging)
TCP 13000 Kannel Client to Server
TCP 13001 Kannel Client to Server
TCP 13013 Kannel Clint to Server for debugging, Server internal,
one EMS server to other EMS server where
Kannel is running.
Kannel Port on which http request can be sent
for sending SMS
Configuring IP Address
IP address of the server should be set before the installation of the application. This is done as
the default IP address of the server is dynamic which has to be set to static IP address.
To configure the IP Address,

1. Login as a "root" user.
2. Execute the following command for setting IP Address of the system. System-config-network
takes you to a prompt asking if you want Device Configuration or DNS configuration.
3. Select Device Configuration and click Enter; choose your network card to change IP address.
Click on Save after making changes.
4. Select DNS Configuration and click Enter to change DNS server configuration. Click on Save
after making changes.
5. Execute the command $ service network restart to update the changes in the IP address.
6. Execute the command $ ifconfig eth0 to verify the change in the IP address. The inet addr
displays the IP address set to the PC.
7. Edit Network configuration file and make ONBOOT=yes, vi /etc/sysconfig/network-script/ifcfg-
ethX.
Setting Host Name

This procedure details the assignment of IP address of the EMS PC to the host name of the
servers.
NOTE: The user should set a host name for the server before installing EMS.
1. To set the host name for the server, execute the following command:
$ vi /etc/sysconfig/network
31
2. Enter the PC name. The format for entering the host name is shown below.
Figure 10: Setting Host Name
NOTE: Hostname should not contain "underscore" character style.
3. Save the file after the entry.

4. Execute the command:
$ hostname 'host_name' where host_name is same as entry made in /etc/sysconfig/network for
HOSTNAME.
5. Execute the command:
$ service network restart
6. To set the Hostname and corresponding IP, execute the following command:
$ vi /etc/hosts
The format should be IP hostname where the 'IP' is the IP address assigned to the EMS PC
and 'hostname' is same as in step 1 and 4.
7. Save the file after entering the IP address and PC name.
8. To get the name of the PC, re-login and execute the following command:
$ hostname
9. To get the IP of the PC, execute the following command:
$ hostname -i
32
Chapter 4 Linux Server Configuration
Prerequisites for launching the EMS application

Ensure that the below protocols and softwares are installed.
Telnet- server
vsftpd
Httpd
sshd
ftp
gcc
Perl-DBD-Sqlite
group install development tools
Execute the following commands for the installation of the above protocols and software in the
command prompt.
Table 13: List of commands
To Command
Install the Telnet server yum install telnet-server
Enable the Telnet server chkconfig --level 35 telnet on
Install the vsftpd yum install vsftpd
Enable the vsftpd chkconfig --level 35 vsftpd on
Install ftp yum install ftp
Install the httpd yum install httpd
Enable the httpd chkconfig --level 35 httpd on
Install the sshd yum install sshd
Enable the sshd chkconfig --level 35 sshd on
Install gcc yum install gcc
Install perl DBD-SQlite yum install perl DBD-Sqlite
Install the group install Development tools yum group install development tools
33
Chapter 5
TJ5100 R6.1 Server Installation

This chapter describes the procedure to install TJ5100 R6.1 server software.
NOTE: The images displayed in this section are for reference purpose only. Ensure that you
follow the steps mentioned in order to execute the task.
IN THIS CHAPTER
Before Installation ...........................................................................................35
Installing TJ5100 R6.1 Server Software .......................................................35
Post-Installation Tasks....................................................................................41
Installing TJ5100/TJ5500 in Co-Residency Mode.....................................42
Uninstalling TJ5100 in Standalone Mode ....................................................51
Uninstalling TJ5500/TJ5100 Server Software (Co-Residency Mode) ....53
TJ5100 Server (Start/Stop/Status) ...............................................................55
License Management.......................................................................................58
Before Installation
1. Prior to EMS/NMS installation, disable firewall by typing:
systemctl stop firewalld.service
2. Disable selinux.by typing:
vi /etc/selinux/config --> SELINUX=disabled.
3. Save and reboot the RHEL server.
Installing TJ5100 R6.1 Server Software

To install the TJ5100 R6.1 software, perform the following steps,
1. Login to the server as "root" user.
2. Insert the TJ5100 R6.1 installation CD. The required files shown in Figure below will be
available in the CD.
Figure 11: TJ5100 Installation Files
35
3. Input the ./install_all.sh script and press Enter to run the installation script file.
Installation of TJ5100 initiates. A prompt to select the Ethernet interface to be used appears.
Press Enter to select the default value eth0 displayed in brackets.
Figure 12: Running script & setting Ethernet interface
A list of options is displayed. A prompt to enter the value for installation from the displayed
options appears. To install TJ5100, type "1" and press Enter. Option '1' stands for "Install
EMS.". Default option '3' stands for "exit".
Figure 13: Install EMS
4. Verification of MySQL version is performed next. If any older version of MySQL is installed,
then system will prompt the customer to upgrade the MySQL version to 5.7, as shown below.
Press Enter. The system will take the default value as "y".
Figure 14: MySQL Version 5.7 Installation
36
Chapter 5 TJ5100 R6.1 Server Installation
A prompt to reconfigure the default MySQL password appears. To retain the default
password, press Enter (default value is 'n') or to change the password, input "y" and press
Enter. A prompt to specify the root password for database server appears. Input the default
password (iltwat) and press Enter. If password change is selected, in prompt messages
following, input the desired password as the new root password and re-enter the same new
password and press Enter. ActiveMQ software installation is performed next.
5. A prompt to input the TJ5100 name appears, as shown Figure below. Input the TJ5100 name
and press Enter. Acceptable values are any alphanumeric characters and under special
characters only - (hyphen), and _ (underscore).
Figure 15: Setting EMS Name
6. A prompt to select the application mode for TJ5100 appears, as shown in Figure below. Press
Enter for SDH mode (default value is 'SDH') or input "SONET" and press Enter for
SONET mode.
Figure 16: Setting EMS application mode
7. A prompt to input the password for EMS user appears, as shown in Figure below. Input the
password (default 'iltwat') and press Enter. or, if EMS user is unavailable, then system will
create new EMS user automatically and then the prompt to enter the password for user EMS.
8. A prompt to allow concurrent-user logins appears. Type "true" and press Enter if the user
desires to allow concurrent logins to the server. If the user desire not to allow, only press
Enter (default value is 'false').
Figure 17: Allowing Concurrent user login
9. A prompt to allow NBI over NAT appears, as shown in the figure. Input "true" and press
Enter for enabling NATing. NATing is used to enable NBI interface of EMS on public
network. Or press only Enter if the user desires to not allow NBI over NAT (default value is
'false').
Figure 18: NBI over NAT prompt
10. If the user allowed NBI over NAT, then a prompt to enter the NATing IP appears. Enter the
IP address and press Enter.
37
11. A prompt to run the TJ5100 services at startup appears, as shown in Figure below. Press
Enter to run TJ5100 service at startup (default value is 'y') or input "n" and press Enter if the
service is not desired to run at startup.
Figure 19: Running TJ5100 service at startup
12. A prompt to install TJ5100 in Hot Standby mode appears, as shown below. Do one of the
following:
For installing TJ5100 in Hot Standby mode, input "y" and press Enter. Go to step
13; Or
If Hot Standby mode is not desired, only press Enter (default value is 'n'). The
application will get installed in non-HotStandby mode. Go to step 21.
Figure 20: TJ5100 installation mode
13. If Hot Standby mode is selected, a prompt to select the type of Hot Standby mode appears.
Type "SameSubnet" or "DifferentSubnet" as desired and press Enter.
For both options, further steps remain the same [except step 17, which is only displayed if
SameSubnet option is selected].
Figure 21: Setting Hot Standby type
14. A prompt to input the IP address/hostname of the Master and the Slave servers to be used in
Hot Standby mode appears, as shown in Figure below. Type the IP addresses/hostnames of
the servers separated by comma (for example: 192.168.20.xx,192.168.20.xx) and press Enter.
Figure 22: Setting IP Addresses for Hot Standby mode
15. A prompt to enter the priority for the presently logged-in server appears, as shown in Figure
below. Input the value (range- 1 to 10, default- 1) and press Enter. This value determines
which server acts as Master or Slave in Hot Standby mode. Higher the value, higher will be
the priority of that server. The priority number assigned to the servers in Hot Standby mode
must be different, hence the server having highest priority will become Master server (in case
when servers are up and running simultaneously).
Figure 23: Setting Hot Standby priority
38
16. A prompt to input the Ethernet interface appears, as shown in below. Input the Ethernet
interface to be used for Hot Standby and press Enter. Eth0 value will be selected by default if
the user press Enter only.
Figure 24: Setting Ethernet Interface
17. A prompt to input the Virtual IP address appears, as shown in Figure below. Input the
Virtual IP address to be used by TJ5100 client to access the server and press Enter.
Figure 25: Setting Virtual IP Address
NOTE: The IP Address of Master, Slave, and Virtual IPs must be in the same subnet. This
step is displayed only if the user selected SameSubnet option in step 13.
18. A prompt to input the Net Mask appears, as shown in Figure below. Press Enter to select
the net mask address displayed in brackets. In case if the user desires to change the Net Mask
Address, input the respective Net Mask address and press Enter.
Figure 26: Setting Net Mask Address
19. A prompt to input the MAC address of the NIC used for Hot Standby appears, as shown in
Figure below. For the Ethernet interface (eth0/eth1/..) entered in step 16, the corresponding
MAC Address is displayed by default in brackets. Press Enter to select this MAC Address.
The MAC address will be of the format: 00:00:00:00:00:00.
Figure 27: Setting Mac Address for NIC
20. A prompt to input the Ethernet Interface Alias Number appears, as shown in Figure below.
Input the Alias number to be used by TJ5100 for Hot Standby mode and press Enter. For
reference to Ethernet Interface Alias Number, go to Installing TJ5100/TJ5500 in Co-
Residency Mode.
Figure 28: Setting EIA number
21. Checking MySQL-Perl Module status message appears, as shown in the Figure below.
Figure 29: Checking MySQL-Perl module status
39
22. Checking for Kannel installation message appears, as shown in the Figure below.
Figure 30: Kannel Installation message
23. A prompt to select a map as a default background image on GUI for all users is displayed
along with five options. Input the number corresponding to the desired option and press
Enter. If no background image change is desired, press Enter to skip; option 5, 'Blank Map'
is selected by default.
Figure given below shows setting Asia map as a default background image for Topology
View.
Figure 31: Background map selection
24. If the license file is not present at the specified location /opt/ems/release/license/, a prompt to
copy the TJ5100 license file appears, as shown in Figure below. Press Enter to continue.
Copy the license file at the specified location /opt/ems/release/license.
Figure 32: Copying License file
25. A prompt to start TJ5100 service appears. Press ENTER to start the service at that instant
(default value is 'y') or type "n" and press ENTER if service start is not desired.
Figure 33: Running TJ5100 service
26. Installation completed successfully message appears, as shown below.

Figure 34: EMS Installation Successful
For TJ5100 R6.1 installation in Hot Standby mode, repeat the installation procedure on the other
server also; setting a different Hot Standby priority for that server.
40
NOTE: Configuring Hot Standby in different subnet does not require a virtual IP address.
Logging in to the EMS can be either through IP address of Master or the Slave.
Post-Installation Tasks
Complete the following tasks after installing EMS and before starting/launching EMS:
EMS client with multiple IPs (multi-homed client) running on Windows OS should be
configured to use the correct IP as the first one to reach the server. Changes in hosts file do
not affect the binding order of network interfaces. To change the network binding order you
need to edit network settings as instructed in http://support.microsoft.com/kb/894564
http://support.microsoft.com/kb/894564. Once this is done, network binding happens in the
specified order and the desired IP is considered first for connection to the server.
Update the EMS servers /etc/hosts file with the clients' IP addresses, client Name and IP
addresses of the Hot Standby servers.
To disable SELinux, go to /etc/selinux file, type vi config and press Enter. Set
SELINUX=disabled and save the file.
To prevent auto-login to the node page (when launching node view from EMS GUI), run the
script ModifyProperties.tgz after the EMS installation.
For mapping profile to the user, following script is required to be executed after installation
and services running on the server:
java -cp /opt/ems/release/ems.jar:/opt/ems/release/libs/*:/opt/ems/release/data/
com.tejas.ems.common.security.PopulateProfile
In order to login to EMS using Firefox ESR 38.8.0, following soft links are required to be
created:
ln -s /usr/java/jdk1.8.0_66 /jre/lib/amd64/libjavaplugin_jni.so
/usr/lib/mozilla/plugins/libjavaplugin_jni.so
ln -s /usr/java/jdk1.8.0_66 /jre/lib/amd64/libnpjp2.so
/usr/lib/mozilla/plugins/libnpjp2.so
NOTE: For a 64 bit machine, these soft links are required to be created in the corresponding
/usr/lib64 folder.
Do the following configurations to receive SMS alert when EMS is installed on a VM server:
Changed device to /dev/ttyS0 in /etc/kannel.config file
port /dev/ttyS0 : same as port on which VM server is connecting to host server
baudrate 38400 (based on RF modem support)
41
Installing TJ5100/TJ5500 in Co-Residency Mode

The following versions of TJ5100 and TJ5500 can be installed together:
EMS NMS
TJ5100 R6.1 TJ5500 R6.1
Installation Guidelines
The following guidelines must be considered when EMS and NMS is installed in co-residency
mode:
If you force EMS to switchover, NMS is also forced to switchover and vice versa.
If TJ5100 and TJ5500 is installed separately on same server, the service will be emsnms i.e.
co-residency mode.
If EMS is already installed and you are installing NMS, then if EMS is in Hot Standby mode,
the NMS will also get installed in Hot Standby mode with the same set of Server IPs and vice
versa.
If EMS is already installed and you are installing NMS, then if EMS is in non-Hot Standby
mode, then the NMS will also get installed in non-Hot Standby mode and vice versa.
When EMS and NMS are installed in co-residency Hot Standby mode, if you start EMS or
NMS, both EMS and NMS will be started. Similarly, if you stop EMS or NMS, both EMS
and NMS will be stopped.
In Co-Residency mode, both same subnet and different subnet IPs for Hot Standby mode
are supported.
The MySQL password of both master and slave servers should be same in the case of Hot
Standby mode.
NMS does not support 1:N Hot Standby configuration.
In EMS credentials window, for Hot Standby in Different Subnet, only two IPs are shown
since only 1:1 configuration is supported.
While managing EMS from NMS, the user cannot add Hot Standby EMS in same subnet by
giving the virtual IP as HAIP.
Installation Procedure
Perform the steps given below to install both TJ5100 and TJ5500 simultaneously on the same
sever (co-residency mode).
1. Insert the installation CD. The required files shown in Figure below will be available in the
CD.
Figure 35: TJ5100 Installation Files
42
2. Input the ./install_all.sh script and press Enter to run the installation script file; installation
initiates. A prompt to select the Ethernet interface to be used appears. Press Enter to select
the default value eth0 displayed in brackets.
Figure 36: Setting Ethernet interface
A list of options is displayed. A prompt to enter the value for installation from the displayed
options appears. To install TJ5100 and TJ5500 in Co-Residency mode, type "3" and press
Enter. Option '3' stands for "Install EMS & NMS in co-residency. Default value is option '7'
which stands for "exit".
Figure 37: Selecting Installation Option
3. Prompts to run the TJ5100 and the TJ5500 services at startup appears, as shown in Figure
below. If the user desires to run the services at startup, press Enter (default value is 'y') or, if
the user does not want to run the services at startup, type "n" and press Enter. Verification of
Java and MySQL version is performed next.
Figure 38: Running TJ5100 TJ5500 services at startup
4. A prompt to reconfigure the MySQL password appears. To retain the default password, press
Enter (default value is 'n') or to change the password, input "y" and press Enter. If password
change is selected, a prompt to specify the root password for database server appears. Input
the default password (iltwat) and press Enter. In prompt messages following, input the
43
desired password as the new root password and re-enter the same new password and press
Enter.
Figure 39: Reconfiguring MySQL password
5. A prompt to input TJ5100 name appears, as shown Figure below. Input the TJ5100 name
and press Enter. Acceptable values are any alphanumeric characters and under special
characters only - (hyphen), and _ (underscore).
Figure 40: Setting EMS Name
6. After entering the name for TJ5100, a prompt to enter the application mode for TJ5100
appears, as shown in Figure below. Press Enter for SDH mode (default value is "SDH") or
input "SONET" and press Enter for SONET mode.
Figure 41: Setting EMS application mode
7. A prompt to enter the password for the EMS user appears, as shown in the Figure below.
Input the default password 'iltwat' and press Enter.
Figure 42: User EMS password
8. A prompt to allow concurrent-user logins appears, as shown in the Figure below. Type "true"
and press Enter if the user wants to allow concurrent logins to the server. If the user desire
not to allow, only press Enter (default value is 'false').
Figure 43: Setting concurrent user login
44
9. A prompt to allow NBI over NAT appears, as shown in the Figure below. Input "true" and
press Enter for enabling NATing. NATing is used to enable NBI interface of EMS on public
network. Or press only Enter if the user desires not to allow NBI over NAT (default value is
'false').
Figure 44: Setting NAT over NBI
10. If the user allows NBI over NAT, a prompt to enter the NATing IP will appear. Type the IP
address and press Enter.
11. A prompt to install the application in Hot Standby mode appears, as shown in the Figure
below. Do one of the following:
For installing TJ5100 in Hot Standby mode, input "y" and press Enter. Then go
to step 12; Or
Figure 45: Installing TJ5100 in HotStandBy mode
If Hot Standby mode is not desired, only press Enter (default value is 'n'). The
application will get installed in Standalone mode. Go to step 20 if Standalone
mode is selected.
Figure 46: Installing TJ5100 in Standalone mode
12. If Hot Standby mode is selected, a prompt to select the type for Hot Standby mode appears.
Type "SameSubnet" or "DifferentSubnet" as desired and press Enter.
For both options, further steps remain the same [except step 16, which is only displayed if
SameSubnet option is selected].
Figure 47: Setting type for Hot Stanby mode
13. A prompt to input the IP address/hostname of the Master and the Slave servers to be used in
Hot Standby mode appears, as shown in Figure below. Type the IP addresses/hostnames of
the servers separated by comma (for example: 192.168.20.xx,192.168.20.xx) and press Enter.
Figure 48: Setting Hot Standby server IP Addresses
45
14. A prompt to enter the priority for the presently logged-in server appears, as shown in Figure
below. Input the value (range- 1 to 10, default- 1) and press Enter. This value determines
which server acts as Master or Slave in Hot Standby mode. Higher the value, higher will be
the priority of that server. The priority number assigned to the servers in Hot Standby mode
must be different, hence the server having highest priority will become Master server.
Figure 49: Setting Hot Standby priority
15. A prompt input the Ethernet interface appears, as shown in below. Input the Ethernet
interface to be used for Hot Standby and press Enter. eth0 value will be selected by default if
the user press Enter only.
NOTE: This step is displayed only if the user selected SameSubnet option in step 12.
the Net Mask Address displayed in brackets. In case if the user desires to change the Net
Mask Address, input the respective Net Mask address and then press Enter.
18. A prompt to input the MAC address of the NIC used for Hot Standby appears, as shown in
Figure below. For the ethernet interface- eth0/eth1 entered in step 15, the corresponding
Figure 53: Setting MAC Address
Input the Alias number to be used by TJ5100 for Hot Standby mode and press Enter. The
default value is displayed in brackets.
Figure 54: Setting Ethernet Interface Alias Number for TJ5100
46
20. Checking MySQL-Perl Module status message appears, as shown in the Figure below.
Figure 55: MySQL-Perl Module status
21. Checking Kannel installation message appears, as shown in Figure below.

Figure 56: Kannel Installation message
22. A prompt to select a map as a default background image on GUI for all users is displayed
along with five options. Input the number corresponding to the desired option and press
Enter. If the no background image change is desired, press Enter to skip; option 5, 'Blank
Map' is selected by default.
Figure 57: Background map selection
23. TJ5100 installation completed successfully message appears, as shown in Figure below.
Figure 58: TJ5100 Installation completed successfully message
47
24. After successful completion of TJ5100 installation, TJ5500 software installation initiates. The
Figure below shows the initiation details.
Figure 59: Initiation of TJ5500 installation
25. A prompt to input the Ethernet interface appears, as shown in below. Input the Ethernet
interface used for Hot Standby and press Enter. This value is same for TJ5100 and TJ5500
on same machine.
48
the Net Mask Address displayed in brackets. In case if the user desires to change the Net
Mask Address, input the respective Net Mask address and then press Enter.
28. A prompt to input the MAC Address of the NIC used for Hot Stanby appears, as shown in
Figure below. For the ethernet interface- eth0/eth1 entered in step 25, the corresponding
Figure 63: Setting MAC Address
Input the Alias number to be used in TJ5500 for Hot Standby mode and press Enter. Default
value is displayed in brackets.
Figure 64: Setting Ethernet Interface Alias Number for TJ5500
49
30. Hot Standby details will be stored in the /opt/nms/release/config/Hotstandby.properties location.

Finally, installation completed successfully message is displayed as shown in Figure below.
Figure 65: Finalization & installation completed successfully
31. If TJ5100 and TJ5500 is installed for the first time in co-residency mode and the license files
are not present, then the system will prompt you to copy the license file. Copy the NMS
license file under /opt/nms/release/license folder and EMS license file under
/opt/ems/release/license folder before starting EMS and NMS.
Figure 66: Copying the license file
32. A prompt to start TJ5100 and TJ5500 services appears. Press Enter to start the services
(default value as 'y') or input "n" and press Enter.
50
Points to Remember
Ensure the following when installing TJ5500 and TJ5100 in Hot Standby mode on same
machine:
Virtual IP: It must be non-pingable IP in the LAN. The virtual IP for TJ5100 and TJ5500 in
Co-residency mode on the same machine must be different. Also, TJ5500 on Master and
Slave servers must have same Virtual IP address and same is applicable to TJ5100.
Hot Standby machine IPs/Names: IP Address or hostname of the servers in Hot Standby
mode. In co-residency mode, TJ5500 installed on different servers must have the same IP
addresses/hostnames.
Priority: Priority assigned to the servers in Hot Standby mode. The value range from 1 to 10.
10 is the highest priority value.
Password for EMS user on the machine.
MAC Address of the NIC used for Hot Standby: MAC Address of the ethernet interface
(eth0/eth1) on the server in use. In co-residency mode, the ethernet interface for TJ5100 and
TJ5500 is same. Hence, the MAC address of the ethernet interface to be entered in EMS and
NMS installation remains the same.
Ethernet Interface: Ethernet Interface (eth0/eth1) which ever is being used by machine. To
check the ethernet interface of the server machine being used for Hot Standby mode, type
the command /sbin/ifconfig. TJ5100 and TJ5500 installed on same server must have same
Ethernet Interface value.
Ethernet Interface Alias Number: The value is in number 1, 2, or 3 or more. TJ5500 and
TJ5100 installed in co-residency mode on same machine must have a different alias number.
Also, TJ5500 on Master and Slave server must have same Ethernet Interface Alias number
and same is applicable to TJ5100.
51
Uninstalling TJ5100 in Standalone Mode

To uninstall TJ5100 server software,
1. Login to the TJ5100 server as "root" user.
2. Stop the EMS service by executing the /sbin/service ems stop command.
3. Input the command cd /opt/ems/release/install/ and press ENTER. Execute the script
./ems_uninstall.sh. Uninstallation of TJ5100 initiates as shown in Figure below.
Figure 67: Running TJ5100 uninstallation script
4. A prompt to delete TJ5100 database appears, as shown in Figure below. Press ENTER to
retain the database (default value is 'n') or input "y" and press ENTER to remove the TJ5100
database.
Figure 68: Deleting TJ5100 database prompt
5. A prompt to clear log files appears, as shown in Figure below. Press ENTER to clear the log
files (default value is 'y') or input "n" and press ENTER to retain the log files.
Figure 69: Clearing Log files prompt
6. A prompt to uninstall ActiveMQ software appears, as shown in Figure below. Press ENTER
to uninstall the ActiveMQ software (default value is 'y') or input "n" and press ENTER to
retain the ActiveMQ software.
Figure 70: Uninstalling ActiveMQ prompt
7. After successful uninstallation of TJ5100, message as shown in Figure below appears.

Figure 71: TJ5100 uninstallation complete message
52
Uninstalling TJ5500/TJ5100 Server Software in Co-

Residency Mode
To uninstall TJ5500 and TJ5100 server software,
1. Login to the server as "root" user.
2. Stop the emsnms service by executing the command /sbin/service emsnms stop.
3. Input the command cd /opt/ems/release/install/ and press Enter. Execute the script
./uninstall_all.sh. TJ5100 uninstallation initiates as shown in Figure below.
Figure 72: Running Uninstallation script
4. A prompt to delete TJ5100 database appears, as shown in Figure below. Press Enter to retain
the database (default value is 'n') or input "y" and press Enter to remove the TJ5100 database.
Figure 73: Removing Database prompt
5. A prompt to clear log files appears, as shown in Figure below. Press Enter to clear the log
files (default value is 'y') or input "n" and press Enter to retain the log files.
6. A prompt to uninstall activemq software appears, as shown in Figure below. Press Enter to
uninstall the activemq software (default value is 'y') or input "n" and press Enter to retain the
activemq software.
Figure 75: Uninstalling Activemq prompt
53

Figure 76: TJ5100 uninstallation complete message
8. TJ5500 uninstallation initiates. Message as shown in the Figure below appears.

Figure 77: TJ5500 Uninstallation initiation
9. A prompt to clear log files appears, as shown in Figure below. Press Enter to clear the log
files (default value is 'y') or input "n" and press Enter to retain the log files.
10. A prompt to clear configuration files appears, as shown in Figure below. Press Enter to clear
the configuration files (default value is 'y') or input "n" and press Enter to retain the
configuration files.
Figure 79: Clearing configuration files prompt
11. A prompt to clear documentation files appears, as shown in Figure below. Press Enter to
clear the documentation files (default value is 'y') or input "n" and press Enter to retain the
documentation files.
Figure 80: Clearing documentation files prompt
12. A prompt to uninstall activemq software appears, as shown in Figure below. Press Enter to
uninstall the activemq software (default value is 'y') or input "n" and press Enter to retain the
activemq software.
Figure 81: Uninstalling Activemq prompt
54
13. A prompt to uninstall tomcat software appears, as shown in Figure below. Press Enter to
uninstall tomcat software (default value is 'y') or input "n" and press Enter to retain the
tomcat software.
Figure 82: Uninstalling tomcat prompt
Figure 83: TJ5500 Uninstallation complete message
TJ5100 Server (Start/Stop/Status)

Input the following command to check the status of the TJ5100 and TJ5500 simultaneously.
Figure 84: Checking TJ5100/TJ5500 service status
55
The generic commands performed on the servers are listed in the table below:
Table 14: Generic Commands
Operation Command
To start the TJ5100 servers $/sbin/service ems start
To stop the TJ5100 servers $/sbin/service ems stop
To know the status of the TJ5100 servers $/sbin/service ems status
To start TJ5100/TJ5500 server (co-residency mode) $/sbin/service emsnms start
To stop the TJ5100/TJ5500 server (co-residency mode) $/sbin/service emsnms stop
To know the status of the TJ5100/TJ5500 servers (co-residency mode) $/sbin/service emsnms status
NOTE: User should login as super user to execute the commands mentioned in the above
table.
Table 15: Process Management
Process Name Description Normal Hot Standby Process Dependent

Process State State (slave server) Process
Naming Service CORBA Running Not Running NA
implementation from
JacORB. This provides
standard way to bind
names to object
references for later
lookups
ClearChannel Process to clean up Not Running Not Running NotifyService
channel information
stored in DB
NotifyService Process that distributes Running Not Running NamingService
CORBA events to north
bound consumers like
TejNMS
ActiveMQ JMS 1.1 implementation Running Not Running NamingService
from Apache. Used as
messaging service
EMSDomain Collects/Configures Running Not Running NamingService,
management NotifyService,
information from/to the ActiveMQ
network.
TMFDomain Exposes management Running Not Running NamingService,
information through NotifyService,
TMF standard API(s) ActiveMQ
for NB consumers
56
Process Name Description Normal Hot Standby Process Dependent

Process State State (slave server) Process
Performance Collects performs Running Not Running NamingService,
Domain information from the NotifyService
network element
HotStandby Hot Standby heart beat Running Running NA
managing processes.
NOTE: This
process is
applicable only in
case of Hot
Standby setup.
Starting a Process
In case of troubleshooting, a particular process can be started by following the below steps:
Login as root and input the following command:
/opt/ems/release/bin/AppClient start <process name>
NOTE: All other dependent process needs to be manually started.
Stopping a Process
Login as root and input the following command:
/opt/ems/release/bin/AppClient stop <process name>
NOTE: Dependent processes will be automatically stopped on stopping the parent processes.
Process Logs
Log folder: /opt/ems/release/logs/
TJ5100 application startup logs will be done in AppManager.log and AppManager.out
TMFDomain related logs will be logged in to TMFDomain/TMFDomain.*.log with different log

levels.
57
License Management
The list below indicates the following limitations:
If the license is not present in the path /opt/ems/release/license/license.dat, TJ5100 will not start.
The same can be verified from AppManager.log.
If the license is present and not valid, then TJ5100 will not start.
The path to save the license.dat file after TJ5100 installation is /opt/ems/release/license folder.
Number of TJ5100 clients that can be launched is limited by the license file. Refer the
License file for more information.
VNE and Circuit Management support is dependent on the license file. Refer the License file
for more information.
Number of Network elements enrolled depends on the TJ5100 License file. Refer the License
file for more information.
Support for Centralized User Management, RADIUS and Token based GCT depends on the
license file. Refer the License file for more information.
58
Chapter 6
TJ5100 R6.1 Client Installation

This chapter describes the procedure to install TJ5100 R6.1 client software and launch Java Web
Client.
IN THIS CHAPTER
Installing TJ5100 R6.1 Client Software ........................................................60
Launching TJ5100 R6.1 Java Web Client ....................................................61
59
Installing TJ5100 R6.1 Client Software

This section describes the installation of TJ5100 client software.
Java Installation
As mentioned in the pre requisites, we need installation of jre. The binary file is in the Java CD.
Double click on jre-1_8_0-windows.
GNOME User
The command cp /opt/ems/release/bin/tejTJ5100.desktop ~/.gnome-desktop/ displays a shortcut icon
on the desktop.
KDE User
The command cp /opt/ems/release/bin/tejTJ5100.desktop ~/Desktop/ displays a shortcut icon on the
desktop.
Launching TJ5100 R6.1 Client

Launch the web browser and specify the URL of the primary TJ5100 R6.1 Server as mentioned
below:
http://<emsip>/web/Ems.html
Security settings (.java.policy file) are required for client to run. If settings differ from what is
required new browser window will appear with the instructions.
You can directly launch this page using following URL as mentioned below.
http://<virtualip>/web/Ems.jnlp
Virtual IP instead of EMS IP is applicable only if the EMS is installed in same subnet Hot
Standby mode. After the client is launched, in order to log on to the TJ5100, the default
username is 'administrator' and the password is 'tejas'.
60
Chapter 6 TJ5100 R6.1 Client Installation
Launching TJ5100 R6.1 Java Web Client

This procedure details the launching of TJ5100 client,
1. Open a web browser and type the URL: http://ip_address/web/Ems.html where ip_address is
the IP address of the machine where the TJ5100 server is running. The TJ5100 Element
Management System(EMS) Application window is displayed.
Figure 85: TJ5100 Element Management System (EMS) Application window
2. Click here to download the certificate and import it into JControl (java control) under
Security->Manage Certificates->Signer CA.
3. Open Control Panel. Click JAVA > Security > Edit site list. The Exception Site List window
is displayed.
4. Type the required http://<emsip> under the tab location.
5. Click Add.
6. Click OK. The JAVA Control Panel window is displayed.
7. Select the security level for applications as High.
8. Click JAVA > Advanced. Under the Java Console, select the option Show console.
9. Ensure that the Show Console option is enabled in control panel of the client and the java
console is kept open while the EMS client is getting launched.
10. Click on Click here to launch the EMS application button. Opening Ems.jnlp window is
displayed when launching TJ5100 application for the first time. Save the file.
61
Launching the TJ5100 EMS Web Client

To launch the EMS Web Client follow the steps given below:
the IP address of the machine where the TJ5100 server is running. On TJ5100 Element
Management System (EMS) Application page, select Click here to launch the EMS
application button.
or
Open a web browser and type the URL: http://ip_address/web/Ems.jnlp where ip_address is
the IP address of the machine where the TJ5100 server is running.
2. Welcome to TJ5100:: Login window is displayed. Input the username, password, and server IP
address in the corresponding boxes.
NOTE: When EMS is in Hot Standby mode with different subnet, input the IP address for
different subnet under Server IP #1 and Server IP #2 on the login page.
3. To save the password entered, select the save password check box.
4. Click Login. The TJ5100 window is launched.
5. To exit from the application, click Exit.
EMS application can also be launched using Command Prompt (cmd.exe) by executing either of
the two commands given below:
Type the command javaws http://ip_address/web/Ems.jnlp where ip_address is the IP address of
the machine where the TJ5100 server is running. The login page is displayed. Enter the
required details and press Login.
If the user desires to avoid executing the two step process described above, type the
command: javaws -open -login:ip_address:username:password http://ip_address/web/Ems.jnlp where
ip_address is the IP address of the server, username is 'administrator' and password is 'tejas'.
TJ5100 window is launched directly.
62
Chapter 6 TJ5100 R6.1 Client Installation
Viewing Server Process Status

To view the status of the server where EMS is installed, follow the steps given below:
2. Select Click here to see the server process status link on TJ5100 Element Management
System(EMS) Application window. The Server Process Status window is displayed with current
status of the processes running on the server.
Figure 86: Server Process Status
63
Table 16: Server Process Status parameters
Parameter Description
Count Displays the number of times the corresponding process was restarted.
ProcessName Displays the name of the processes on the server.
PID Stands for Process Identifier. Displays the PID assigned to the corresponding
ProcessName.
Status Displays the 'status' of the corresponding process on server. The values
displayed are:
In Standby mode: Running;
In HotStandby mode: Running, Stopped on Request, and Never Started
Last Refresh Time Displays the last date and time when the user refreshed the server status to
display the current information.
Home Click on the link to redirect to the TJ5100 Element Management System(EMS)
Application window.
Refresh Click to display the current status of the server.
Enable AutoRefresh Select the check box to enable automatic refresh of the html page to obtain the
server process status information after every 30 seconds (approximately).
EMS Health Check

To perform the EMS health check, follow the steps given below:
2. Select Click here to run EMS health check link on TJ5100 Element Management
System(EMS) Application window. While the health check is being performed, a message is
displayed "Collecting EMS health status .. Relax(Larger database wait for moretime)". After the
operation is complete, report is generated which is available as EMS Health Report link.
Click on this link to view the report.
64
Chapter 7
NTP Chaining
NTP chaining involves either all or a combination of the following configurations:
Configuring a Linux machine as NTP Server.
Configuring a Linux machine as NTP Client syncing to another Standard NTP Sever.
Configuring a Linux machine as NTP Client syncing to another Linux Server.
Configuring the Tejas NEs to sync to a Linux Server.
For example, in the following scenario, both the EMS and NMS Servers act as an NTP Server
and a Client:
Tejas NE ---> EMS Server ---> NMS Server ---> Standard Time Server
IN THIS CHAPTER
Configuring a Linux Machine as the NTP Server ......................................66
Configuring a Linux Machine as an NTP Client Syncing to Another Standard
NTP Sever ........................................................................................................67
Configuring a Linux Machine as an NTP Client Syncing to Another Linux
Server .................................................................................................................68
Configuring the Tejas NEs to Sync to a Linux Server ..............................68
Troubleshooting NTP Synchronization ......................................................69
65
Configuring a Linux Machine as the NTP Server

You can use NTP to synchronize the system clock with a remote server. RHEL comes with a
sample /etc/ntp.conf file. If you use server 127.127.1.0, the system will use your local clock. You
can also specify any other server to sync time with other public servers. Choose your preferred
NTP server. Note that some servers are not available to the public, and some servers are too
busy to handle new requests.
/etc/ntp.conf (complete sample file)
# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.
restrict default nomodify notrap noquery
# Permit all access over the loopback interface. This could

# be tightened as well, but to do so would affect some of
# the administrative functions.
restrict 127.0.0.1
# --- OUR TIMESERVERS -----
server 0.pool.ntp.org
# --- NTP MULTICASTCLIENT ---

#multicastclient # listen on default 224.0.1.1
# restrict 224.0.1.1 mask 255.255.255.255 nomodify notrap
# restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap
# --- GENERAL CONFIGURATION ---

# Undisciplined Local Clock. This is a fake driver intended for
backup
# and when no outside source of synchronized time is available. The
# default stratum is usually 3, but in this case we elect to use
stratum
# 0. Since the server line does not have the prefer keyword, this
driver
# is never used for synchronization, unless no other
# synchronization source is available. In case the local host is
# controlled by some external source, such as an external oscillator
or
# another protocol, the prefer keyword would cause the local host to
# disregard all other synchronization sources, unless the kernel
# modifications are in use and declare an unsynchronized condition.
server 127.127.1.0 # local clock

fudge 127.127.1.0 stratum 10
# Drift file. Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the
file
# by creating a temporary in the same directory and then rename()'ing
# it to the file.
driftfile /var/lib/ntp/drift
66
Chapter 7 NTP Chaining
broadcastdelay 0.008
# Keys file. If you want to diddle your server at run time, make a
# keys file (mode 600 for sure) and define the key number to be
# used for making requests.
# PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote
# systems might be able to reset your clock at will. Note also that
# ntpd is started with a -A flag, disabling authentication, that
# will have to be removed as well.
keys /etc/ntp/keys
Configuring a Linux Machine as an NTP Client Syncing to

Another Standard NTP Sever
You can configure a Linux machine as an NTP client, and sync this NTP client to another
Standard NTP server. To configure your Linux machine (NTP client) to sync with another
machine (NTP server), edit the /etc/ntp.conf file to contain the IP address of the NTP server.
For example,
server 192.168.132.181 # NTP Server IP address
For example, see the following figure:
Figure 87: NTP Client Configuration
NOTE: If you list multiple NTP server IP addresses, the one at the top level will have highest
priority. If the server with highest priority is not reachable, then, the system will try to reach
the server with next highest priority.
67
You can also use the GUI to add the NTP server IP address. To use the GUI, click Add, enter
the NTP server IP, and click OK. The system will try to connect with the NTP server and update
the /etc/ntp.conf file. For example, see the following figure:
Figure 88: NTP Server Configuration
Configuring a Linux Machine as an NTP Client Syncing to

Another Linux Server
You can configure the Linux machine as an NTP Client to another Linux server, and sync the
Linux server to another Standard NTP server. The configuration procedure is same as that of the
previous option of configuring a Linux Machine as an NTP Client Syncing to Another Standard
NTP Sever.
Configuring the Tejas NEs to Sync to a Linux Server

You can configure the Tejas network element as NTP client, and sync it to a Linux server.
To configure the Tejas network element as NTP client, do the following:

1. Open the node GUI, and then select System Time > Set Time Server in the Navigation
pane.
2. Select Enable from NTP Client Enable drop-down menu.
3. Add the NTP server IP under NTP Server-0.
68
You can add up to 5 NTP servers in the order of priority from higher to lower, as seen the
Figure below.
Figure 89: NE as NTP Client
Troubleshooting NTP Synchronization

The following section guides you through verifying the configuration, functionality, and the
status of NTP servers and clients.
Querying Any Time Server Status

To know the local time server status, use the ntpq -p command.
To know a remote time server status, use the ntpq -p <hostname> command.
For example, refer to the Figure below.
Figure 90: NTP Server Status
69
The field values in the status output are described in the following table:
Field Description
* Indicates the NTP server to which the client is currently synchronized.
remote The IP address or DNS name of the remote server.
refid An identification of the type of the reference clock.
when The number of seconds since the server was last heard from. After a couple of minutes
of operation the server should start to report numeric values here.
poll The current polling interval in seconds. When remote servers are responding, "when"
should not be greater than "poll".
delay The recent average round trip time in milliseconds from request to response.
offset The estimated differential between your system clock and the time server's clock, in
milliseconds.
jitter A measure of the variability of the delays between request and receipt of a response, in
milliseconds. High jitter tends to limit your server's ability to synchronize accurately.
Verifying if Packets are Going Out and Coming Back

To check if packets are going out from your system and coming back to your system, the
tcpdump command is used. NTP uses port 123, and hence, you can enter the following
command as root:
# tcpdump udp port 123
Configuring NTP at Startup

To configure NTP at start up, run the following commands to initialize:
# chkconfig add ntpd
# chkconfig ntpd on
70
Starting and Stopping the ntpd Service

To start, stop, and check the service status of ntpd, use the following commands:
# /sbin/service ntpd start
# /sbin/service ntpd stop
# /sbin/service ntpd restart
Figure 91: Starting and Stopping the ntpd service
Comparing the Time Difference Between the NTP Server and the
Client
To compare the time difference between the NTP server and the client, or to check if the client
is connected to the respective NTP server, you can use the following command:
# date; rdate -p <hostname>
Figure 92: Checking Time Difference
Manually Setting the Date and Time

To manually set the date and time, stop the ntpd service and then use the following command:
# ntpdate <hostIP> <DateToSet>
71
Appendix I
Build Details
This section provides the build details for this release.
Table 17: Build Details
Node Platform Oldest Build Latest Build

LT LT REL_3_5_2_a13_1 REL_3_5_2_a13_1
MC1-R1 MC1 REL_4_2_3_a22 REL_4_2_3_a22
MC1-R2 MC1 REL_4_2_3_a24_1 REL_4_2_3_a37
MC1-R3 MC1 REL_4_5_3_a23 REL_4_5_3_a23
MC1-R4 MC1 REL_4_5_3_a13_1 REL_4_5_3_a21
MC1-R5 MC1 REL_4_5_3_a21 REL_4_5_3_a21
MC1-R6/TJ1220 TJ1220 REL_4_7_1_a24_2 REL_4_7_1_a24_7
TJ100MC/TJ1400 TJ1400 REL_4_7_1_a24_6 REL_4_7_1_a24_7
CP CP REL_4_2_2_a8_1 REL_4_2_3_a38
CP-R2 CP REL_4_5_3_a12 REL_4_5_3_a12
CP-R4/TJ1100 PXAT REL_4_7_1_a24_7 REL_4_7_1_a24_9
TJ1100-R2 PXAT REL_4_7_1_a29 REL_4_7_1_a35
TJ1200/CPE TXC1 REL_4_6_11_a16 REL_5_0_5_a51_1
TJ1210 TXC1 REL_4_3_2_a38 REL_5_0_5_a51_1
TJ1250/CPE4 TXC5 REL_4_6_11_a17 REL_5_0_5_a51_1
TJ1260 TXC5 REL_4_6_11_a17 REL_5_0_5_a51_1
TJ1310 TXC5 REL_4_6_7_a9_15 REL_4_6_15_a14_27
MC4 XC4 REL_4_2_3_a27 REL_4_5_1_a19_12
MC4L XCC16L REL_4_5_1_a19_2 REL_4_5_6_a14_11
TJ1270 TXC8 REL_5_0_5_a51 REL_5_3_19_a10_2
TJ1405 ePXAT REL_5_3_10_a25 REL_5_3_16_a9_2
TJ1410 XA14ET REL_6_0_0_a76_19_1 REL_6_0_0_a76_19_18
TJ1410 XA14OT5 REL_6_0_0_a76_19_1 REL_6_0_0_a76_19_18
TJ1420 XA14ET REL_6_0_0_a76_19_1 REL_6_2_0_a75
TJ1420 XA14OT5 REL_6_0_0_a76_19_1 REL_6_2_0_a75
TJ1420 XA10G REL_6_0_0_a76_21 REL_6_2_0_a75
73
Node Platform Oldest Build Latest Build

TJ1420 XA20G REL_6_0_0_a76_21_1 REL_6_2_0_a75
TJ1420 XA20G-R2 REL_6_2_0_a59_4 REL_6_2_0_a75
TJ1420 XA60G REL_6_0_0_a76_22 REL_6_2_0_a75
TJ1420 CEF4C REL_6_2_6_a36_2 REL_6_2_6_a45_1
TJ100ME TXC4-1P REL_5_0_5_a49 REL_5_3_11_a68
TJ100ME TXC4-2P REL_5_0_5_a49 REL_5_3_11_a68
TJ100ME TXC6 REL_5_0_5_a51 REL_5_0_20_a6
TJ100ME TXC7 REL_5_0_5_a51 REL_5_3_11_a68
TJ1500 XCC01 REL_4_5_7_a13_7 REL_4_5_7_a13_9
TJ1500 XCC02 REL_4_5_7_a32 REL_4_6_15_a32
TJ1500 XCC03 REL_4_6_15_a32 REL_5_1_2_a54_1
MC16/MC16X XCC64L REL_4_5_1_a22 REL_4_5_5_a29_22
MC16/MC16X XCC128L REL_4_5_1_a22 REL_4_5_5_a29_22
MADM XCC05 REL_4_6_9_a4 REL_4_6_9_a5
ADM XCC04 REL_4_6_9_a4 REL_4_6_9_a4
TJ1600/TJ1610 XCC12G5 REL_4_8_1_a39_1 REL_5_1_2_a35_4
TJ1600/TJ1610 XCC40G/40GE REL_4_8_1_a39_1 REL_5_1_2_a47_1
TJ1600-11 XCC80G REL_6_0_12_a59 REL_8_0_1_a66_1_79
TJ1600-11 XCC320G REL_6_0_12_a69 REL_8_0_1_a66_1_79
TJ1600-6 OSMC REL_8_0_1_a66_1_79 REL_8_0_1_a66_1_79
TJ3301 OSMC REL_9_0_2_a17_8 REL_9_0_2_a17_8
TJ3500 OSMC REL_9_0_2_a17_8 REL_9_0_2_a17_8
TJ2030 CE01 REL_5_0_1_a26 REL_5_0_9_a33_1
TJ2031 CE02 REL_5_1_3_a30_4 REL_5_1_3_a30_4
TJ2050 CE01 REL_5_0_9_a33_1 REL_5_0_9_a33_1
TJ2051 CE02 REL_5_1_3_a30_4 REL_5_1_3_a30_4
TJ14xxN MainA REL_6_0_0_a81_21_9 REL_6_0_0_a81_25_1
TJ14xxN MainB REL_6_0_0_a81_21_8 REL_6_0_0_a81_24_34
74
Glossary of Terms
E I
EMS IP
Element Management System (EMS) is an Internet Protocol (IP) is the primary protocol in
integrated management of network elements the internet layer of the Internet Protocol
across an intelligent optical network. EMS Suite and performs the task of delivering
collects and represents management data datagrams from the source host to the
from geographically dispersed network destination host solely based on their
elements on to a centralized database addresses. It is a 32-bit address assigned to
(console) in a centralized Network host using TCP/IP. An IP address belongs
Operations Center (NOC). to one of five classes (A, B, C, D, or E) and
is written as 4 octets separated by periods
H (dotted decimal format). Each address
HO consists of a network number, an optional
sub-network number, and a host number.
Higher Order (HO) is a virtual container in
SDH multiplexing process including a range
of overhead functions for management and
error monitoring. L
HTTP LO
Hyper Text Transfer Protocol (HTTP) is a set of Lower Order (LO) is a virtual container in
standards that allow users of the World SDH multiplexing process including a range
Wide Web to exchange information found of overhead functions for management and
on web pages. error monitoring.
M
MAC
Media Access Control (MAC) is a unique
identifier assigned to network interfaces for
communication on the physical network
segment. MAC addresses are used for
numerous network technologies and most
IEEE 802 network technologies, including
Ethernet. MAC address is 48 bits long. The
MAC address is commonly written as a
sequence of 12 hexadecimal digits.
75
N S
NES SDH
Network Element Software (NES) is the Synchronous Digital Hierarchy (SDH) is an
embedded software present in each of the international standard for high speed
network element that provides control and synchronous data transmission over
management support for individual network optical/electrical networks which can
elements. Service providers can individually transport digital signals in variable capacities.
configure and control network elements It is a synchronous system which intend to
through the browser interface using widely provide a more flexible and simple network
used and popular HTTP protocol. infrastructure.
NMS
Network Management System (NMS) provides SONET
an integrated management of Element
Management Systems (EMS) across an Synchronous Optical Network (SONET) is an
intelligent optical network. NMS collects American National Standards Institute
and represents management data from (ANSI) standard for high speed
geographically dispersed EMSs on to a communication over fiber-optic networks.
centralized database. SONET uses time division multiplexing to
send multiple data streams simultaneously.
NTP
STM
Network Time Protocol (NTP) is a protocol that
is used to synchronize the time of different Synchronous Transport Module (STM) is the
network element in a network. It also allows Synchronous Digital Hierarchy (SDH) ITU-
the transfer and maintenance of time T fiber optic network transmission standard.
functions over distributed network. It is the basic building block of SDH.
O T
OC TCP/IP
Optical Carrier (OC) is a group of signal Transmission Control Protocol/Internet Protocol
bandwidth in a Synchronous Optical (TCP/IP) is a method of packet-switched
Network (SONET) with many defined data transmission used on the Internet.
levels. It is typically denoted as OC-n, where TCP/IP model represents communication
n is the multiplexing factor of the basic rate network in five conceptual layers. Each of
of 51.8 Mbps. these layers performs different functions, all
of which collectively enable information
exchange between computers through the
network.
76
Glossary of Terms
V
VNE
Virtual Network Elements (VNE) are used to
depict elements which are virtual in nature.
For example, VNE refers to another
vendor's node which cannot be managed by
the NMS. They are helpful in indicating the
complete topology of the customer network
constituting of both Tejas and non-Tejas
network elements.
77
Index
A L
Assigning a VMWare License using vSphere Launching TJ5100 R6.1 Java Web Client 61
5.0 Client 21 License Management 58
Linux Server Configuration 12, 29
B
List of Figures vi
Before Installation 35 List of Tables viii
Build Details 73 LO 75
C M
Chapter Organization 12 MAC 75
Client System Requirements 19 Manually Setting the Date and Time 71
Comparing the Time Difference Between the Mouse Operation Conventions 10
NTP Server and the Client 71
N
Configuring a Linux Machine as an NTP
Client Syncing to Another Linux Server 68 NES 76
Configuring a Linux Machine as an NTP NMS 76
Client Syncing to Another Standard NTP NTP 76
Sever 67 NTP Chaining 12, 65
Configuring a Linux Machine as the NTP
O
Server 66
Configuring and Setting Up VMs 22 OC 76
Configuring IP Address 31
P
Configuring NTP at Startup 70
Configuring the Tejas NEs to Sync to a Linux Post-Installation Tasks 41
Server 68 Prerequisites for launching the EMS
application 33
E
Q
EMS 75
Querying Any Time Server Status 69
H
R
HO 75
HT Disabled Mode 23 Related Documents 13
HT Enabled Mode 25 S
HTTP 75
Safety Signs Conventions 11
I SDH 76
Installing TJ5100 R6.1 Client Software 60 Server Partition 29
Installing TJ5100 R6.1 Server Software 35 Server System Requirements 19
Installing TJ5100/TJ5500 in Co-Residency Setting Host Name 31
Mode 42 Software Installation Package 18
IP 75 SONET 76
Starting and Stopping the ntpd Service 71
STM 76
79
T
TCP/IP 76
TCP/UDP Ports Used by EMS 30
TJ5100 R6.1 Client Installation 12, 59
TJ5100 R6.1 Server Installation 12, 35
TJ5100 Server (Start/Stop/Status) 55
TJ5100/TJ5500 Installation Modes and
Scalability 16
Troubleshooting NTP Synchronization 69
Typographical Conventions 12
U
Understanding Hardware and Software
Requirements 12, 15
Uninstalling TJ5100 in Standalone Mode 52
Uninstalling TJ5500/TJ5100 Server Software
(Co-Residency Mode) 53
Using Tejas Product Documentation 13
Using This Guide 9
V
Verifying if Packets are Going Out and
Coming Back 70
VMWare ESX Server and vSphere 5.0 Client
Installation 12, 21
VNE 77
W
What This Guide Covers 9
What You Should Already Know 9
Who This Guide Is For 9
80

TJ5100 R6.1.3.5 Installation and Commissioning Guide

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

TJ5100 R6.1.3.5 Installation and Commissioning Guide

Încărcat de

Drepturi de autor:

Formate disponibile

TJ5100 R6.

Document ID: 400-DOC000090-E Release: Standard Release Version: 1.0

Warning and Disclaimer

Technical Support Information

- Phone(s): +91 80 41719090/91/92/93/94/95

Version Date Modifications Made

1.0 20-Feburary-2017 R6.1.3.5, Standard Release

Accessibility: (Contents, Index, Headings, Numbering, Glossary)

Good Fair Average Poor Bad N/A

Improve the Make it more Improve the

Add more/better Add more detail Improve the index

Understanding Hardware and Software Requirements 15

VMWare ESX Server and vSphere 5.0 Client Installation 21

Linux Server Configuration 29

TJ5100 R6.1 Server Installation 35

TJ5100 R6.1 Client Installation 59

Using This Guide

What This Guide Covers

Who This Guide Is For

What You Should Already Know

Mouse Operation Conventions

Safety Signs Conventions

Table 2: Safety Sign Convention

Symbols Meaning Represents

Danger Situation that could cause bodily injury. Failure to observe

Hot Surface Situation that could result in bodily burns.

Static Discharge Handle the equipment wearing a grounding wrist strap to

Table 3: Typographical Conventions

Formatting Convention Type of Information

Procedures Step-by-step procedures. You can follow these instructions to

CAPITALS Names of keys on the keyboard, for example, SHIFT, CTRL, or

Using Tejas Product Documentation

Document Name Tejas Part Number Description

Understanding Hardware and Software

TJ5100/TJ5500 Installation Modes and Scalability

You can install TJ5100/TJ5500 in the following modes:

Table 4: Supported configurations based on number of NEQs in Standalone mode

Maximum Recommended Minimum Minimum Minimum Disk Space EMS/NMS

Table 5: Supported configurations based on number of NEQs in Virtualized mode

Table 6: Supported configurations based on number of NEQs in Multiple Standalone mode

Maximum Recommended Minimum Minimum Minimum Minimum EMS/NMS

Clustering Mode (Only for TJ5500)

Table 7: Supported configurations based on number of NEQs in Clustering mode

Maximum Recommended Minimum Minimum Minimum Minimum EMS/NMS

Clustering mode of installation cannot be used with co-residency mode.

Co-Residency Mode (TJ5100 and TJ5500 in One Server)

Table 8: Supported configurations based on number of NEQs in Co-Residency mode

Maximum Recommended Minimum Minimum Minimum Minimum EMS/NMS

Software Installation Package

Table 9: Software Installation Package

Software 64-Bit O.S

Server System Requirements

Table 10: Server System Requirements (64-Bit)

Operating System RHEL server release 7.1

Client System Requirements

Minimum Client Specification Component Specification

VMWare ESX Server and vSphere 5.0

The sequence of installation is as follows:

Assigning a VMWare License using vSphere 5.0 Client

4. Click on Edit. The following window appears for assigning a license.

5. Select Assign a new license key to this host.

Configuring and Setting Up VMs

5. Verify that on Guest OS 8 cores are seen in top output.

5. Verify that there are up to 16 cores seen in top output.