Tj5500-Tj5100 Im Guide

NMS TJ5500 & EMS TJ5100
Infrastructure Management Guide

Version: 1.0
Issue Date: 16-Apr-2021
www.tejasnetworks.com
Copyright Notice
Copyright © 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

This document is a guide for using Tejas Networks products. 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 guide contains Tejas Networks
proprietary and confidential information and may not be disclosed, used, or copied without the
prior written consent of Tejas Networks or set forth in the applicable license agreement. 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. The users are solely responsible for the
proper use of the software and the application of the results obtained. TEJAS NETWORKS MAKES
NO WARRANTY OR REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO
THIS DOCUMENTATION, ITS QUALITY, PERFORMANCE, MERCHANTABILITY, OR FITNESS
FOR A PARTICULAR PURPOSE.
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
- Fax: +91 80 26591079
- Email: support@india.tejasnetworks.com
- Skype: tscsupport123
- Web: www.tejasnetworks.com
Additional Learning Resources

The help content for all our products including this content is available online at
https://tejdocs.india.tejasnetworks.com/. Please contact our Sales team to get access to this
content or to organize any onsite and/or offsite trainings related to our products or technologies.
Feedback
Your opinion is of great value and will help us improve the quality of our documentation and related
learning resources. Drop a note to docs@tejasnetworks.com and let us know how we can assist you
in your learning.
Revision History
Version Document ID Modifications Made
1.0 400-DOC000191-E Standard Release
Issue Date: 16-Apr-2021
Table of Contents
Document overview 5
Additional resources .............................................................................. 5
Target audience.................................................................................... 5
Get started with installation 7

Prerequisite for Installing RHEL 8.2 ......................................................... 7
Server requirements ............................................................................. 8
Server partitions .................................................................................. 10
TCP/UDP ports used by TJ5500 .............................................................. 11
Installation procedure 13
Installing Virtual Environment................................................................ 13
Installing Proxmox Server...................................................................... 13
Preparing installation USB media on Linux ............................................... 18
Installing RHEL 8.2 .............................................................................. 21
Set the host name ............................................................................... 30
Post installation procedure .................................................................... 30
Installing additional packages 31

Enabling Network in RHEL 8.2 33
Disabling SE Linux and Firewall in RHEL 8.2 35
Whitelists in the firewall ........................................................................ 35
Changing the Time Zone 37

Checks on Linux Server 39
Apply IP tables 41
Installing EMS/NMS/RAS 45
Cloning 47
Cloning Virtual Machines ....................................................................... 47
Cloning RHEL 8.2 Server ....................................................................... 48
iv
Document overview
This section describes who must read this guide, how it is organized, and what
conventions are used in the document.
Additional resources
The guide listed below is published and shared as a zip bundle: NMS TJ5500 EMS
TJ5100 8.1.1.0 Guides.zip
Document Name and ID Description
Installed RHEL packages for 8 This document provides the list of RHEL
update 2 packages need to be installed and run for
TJ5100 and TJ5500
Target audience
This document is intended for Technician or Field engineers who install and commission
hardware or software at customer premises.
5
NMS TJ5500 & EMS TJ5100 Infrastructure Management Guide
This page is intentionally left blank
6
Get started with installation
This chapter provides an overview of pre-requisites, server requirements, server partition
details and TCP/UDP ports required during installation of RHEL 8.2.
Prerequisite for Installing RHEL 8.2

For fresh installation of RHEL 8.2, ensure that you have access to the following:
 Server through a local console.

 Internet to update packages and update the subscription.
 Installation media- USB stick
 Location on the network to get ISO file for installation.
NOTE: As per the installation requirement, identify the correct interface on the
server to connect to the internet.
If installation media is in the form of a DVD, the server must have a built in DVD
drive, or an external DVD drive is required.
For upgrading an existing installation, ensure that you take backup of the following:
 Any user data

 NMS Database backup
 Current EMS backup (which includes EMS DB, EMS config data, etc)
 PM Data
 Node backup folder
 Node software build folder
 Past EMS backup
 EMS logs
Save all the above mentioned backups at a remote location.
7
Server requirements
Before installing Linux OS, ensure that server meets the following hardware requirements
for different TJ5100/TJ5500 Installation modes.
Standalone mode
Table 1: Hardware requirements for TJ5100
Components 3k NEQs 6k NEQs
Memory 32 GB Physical memory 32 GB Physical memory (RAM)

(RAM)
2 x 600 GB Hard Disk in RAID1
2 x 500 GB Hard Disk in
RAID1
Processor 8 8 Core
Table 2: Hardware requirement for TJ5500
Components 15k NEQs 30k NEQs (10 EMS with 3k NEQs

each)
Memory 32 GB Physical memory 64 GB Physical memory (RAM)

(RAM)
2 x 1.2 Tera Bytes Hard Disk in RAID1
RAID1
Processor 16 Core 32 Core
Co-residency mode
Table 3: Hardware requirements for TJ5100 and TJ5500
Components 1k NEQs
Memory 32 GB Physical memory (RAM)

RAID1
Processor 8 Core
Clustering mode
Table 4: Hardware requirement for TJ5500
Components 60k NEQs (10 EMS with 6K NEQ or 20 EMS with 3K NEQ)
Memory Application Server Database Server

64 GB Physical memory 64 GB Physical memory (RAM)
(RAM)
2 x 600 GB HDD in RAID1/Server
2 x 600 GB HDD in
RAID1/Server
Processor 32 Core 16 Core
8
Radius Administration Service (RAS)
Components 60k NEQs
Memory 32 GB Physical memory (RAM)

2 x 600GB Hard Disk in RAID1
Processor 8 Core
NOTE: RAS server can be co-resident with EMS/NMS, or with EMS alone or NMS
alone.
9
Server partitions
Following table lists the recommended partitioning of the HDD in the Linux server. The
partition scheme shown is an example, any disk size which is either lower or higher
should proportionately change the allocations as mentioned in the example.
Table 5: Server Partitions for TJ5100 server
Partition Disk Allocation in GB (For 500 Application

GB HDD for Maximum 6000
NEQ)
/ 50 Linux OS
/var 160 TJ5100 Database
/opt 160 TJ5100 Software
/home 114 User Area
/swap 64 Paging of processes
Table 6: Server Partitions for TJ5500 server
Partition Disk Allocation in GB (for 600 Application

GB HDD)
/ 50 Linux OS
/var 190 TJ5500 Database
/opt 190 TJ5500 Software
/home 154 User Area
/swap 64 Paging of processes
NOTE: Make sure that swap area is always double the RAM size of the system.
The partitioning scheme is the same for a solid state drive based storage
medium. Currently, servers are being used with solid state drive based storage
media.
When TJ5100/TJ5500 detects disk usage percentage of a partition exceeding the

limit, a disk utilization alarm will get raised against that partition level. The
alarm gets reported under System Generated tab on Manage Alarms page of
NMS WUI. For disk utilization of 80%, the alarm with critical severity gets raised.
This alarm is applicable for /opt, /var, /home, and /temp partitions. After the
disk usage is rectified, the alarm will get cleared only when the next NMS check
for disk usage is scheduled.
In case of extra hard disk space availability, it can be assigned or extended to

the /home partition.
10
TCP/UDP ports used by TJ5500

In case of firewall between TJ5100 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 TJ5100 Server and the node, all ports with direction
of establishment of connection as node to TJ5100 Server or TJ5100 Server to node
should be open for proper TJ5100 operation.
The following table lists the ports used by TJ5100 server:
Table 7: TCP/UDP Ports of TJ5100
Protocol Port Service Name Establishment of

Connection
TCP 20800 TJ5500 TJ5100 Co-Resident port TJ5500 and TJ5100 server
UDP 162 and TJ5500 SNMP Trap listener port TJ5100 and Nodes
163
UDP 10162 TJ5100 SNMPv3 trap listener TJ5100 and nodes
UDP 10059 Notification from NE to TJ5100 TJ5100 and nodes
TCP 20080 HTTP port for Node (If http is TJ5100 and nodes
used)
TCP 55300- SSL enabled CORBA between TJ5100 and TJ5500
55501 TJ5100 and TJ5500
TCP 13000,1300 Kannel TJ5100 and TJ5500
1,13013
TCP 465 and SMTP to send mail notifications TJ5100 and TJ5500
587
The following table lists the ports used by the TJ5500 server:
Table 8: TCP/UDP Ports of TJ5500

Connection
TCP 22 Hotstandby DBDump transfer TJ5500 master and slave

through SFTP servers
TCP 20801 TJ5500 Hot standby port TJ5500 master and slave
servers
TCP 8080 TJ5500 application server port TJ5500 server and TJ5500
client
TCP 21001 TJ5500 web client port for MTOSI TJ5500 server and TJ5500
NBI(tomcat) client
TCP 8081 TJ5500 web client port (tomcat) TJ5500 server and TJ5500
client
TCP 443 HTTPS port for TJ5500 web client TJ5500 server and TJ5500
client
11

Connection
TCP 444 HTTPS port for MTOSI NBI web TJ5500 server and TJ5500
client client
TCP 3306 MySQL DB connection port TJ5500 server and DB
server
TCP 9999 TMF notification listener port TJ5500 and TJ5100 servers
TCP 30443 Launch EMS context in TJ5500 TJ5500 and TJ5100
Topology View
UDP 1812 Radius communication Between Radius and TJ5100
and TJ5500
TCP 21004 TJ5500 to RAS communication port TJ5500 and RAS server
(if Tejas RAS is deployed)
TCP 1221 Analytics Server in TJ5500 TJ5500
TCP 20900 Naming Service port Client and Server
UDP 123 NTP Time sync
TCP 1099 RMI port for Communication Client and Server
TCP 446 REST API REST API Port
TCP 34456 NMS client app webswing TJ5500 Webswing client
port
12
Installation procedure
This chapter covers the following:
 Installation steps for creating Virtual Environment (VE)

 Preparing installation USB media on Linux
 Installation procedure for RHEL 8.2
Installing Virtual Environment

This section covers procedure to install Proxmox server and creating Virtual machine
using Proxmox.
Proxmox server is an open source KVM based virtualization mechanism which can be
used to setup multiple virtual machines in a single bare metal server.
Installing Proxmox Server

The installation of Proxmox server includes:
 Preparing installation media

 Installing Proxmox server
Preparing installation media
1. Download the installer ISO image from:

https://www.proxmox.com/en/downloads/category/iso-images-pve
2. Proxmox VE Installer is a hybrid ISO image which can be used in one of the following
ways:
An ISO image file ready to burn to a CD or DVD.

A raw sector (IMG) image file ready to copy to a USB flash drive.
NOTE: It is recommended to use USB flash drive to perform installation quickly.
3. On the Linux system, use the dd command to copy the ISO image to the USB flash
drive.
NOTE: Make sure to replace /dev/XYZ with the correct device name and adapt
the input filename (if) path.
13
4. Connect the USB flash drive to the server and make sure that booting from USB is
enabled.
Installing Proxmox Server
1. Insert the prepared installation media into the system and boot from it. Proxmox VE
menu is displayed.
Figure 1: Proxmox VE menu
2. Select Install Proxmox VE from the menu. A prompt to select target hard disk is
displayed.
3. Click options and select the target file system.
Figure 2: Target hard disk
Proxmox VE can be installed on ZFS, as it offers several software RAID levels. The
target disks must be selected in the Options dialog. More ZFS specific settings can be
changed under Advanced Options.
4. Select target disk and click OK.
14
5. Click Next. The Location and Time Zone selection page is displayed. Select the
Country, Time Zone and the Keyboard layout from the drop-down.
Figure 3: Location and Time Zone
6. Click Next, the Administration Password and E-mail Address page is displayed.
Provide the root password and the e-mail address.
Figure 4: Administration Password and E-mail Address
NOTE:
Use a minimum password length of 12 to 14 characters.
Include lowercase and uppercase alphabetic characters, numbers, and symbols.
7. Click Next, the Management Network Configuration page is displayed. Provide

the Hostname, IP Address, Netmask, Gateway and DNS Server.
15
Figure 5: Management Network Configuration
8. Click Next, the Summary of options selected is displayed.
Figure 6: Summary of changes
9. Click Install. The installation starts by formatting the disks and copies packages to
the target. Wait until this step is completed and then remove the installation medium
and restart your system.
10. Open web browser and enter the IP address provided during installation (https://IP:
8006). Proxmox home page is displayed.
16
Creating Virtual Machine using Proxmox
NOTE: Place the RHEL ISO Image under the location /var/lib/vz/template/iso.
The image placed in the mentioned location appears in the UI of Create: Virtual
Machine.
To create Virtual Machine (VM) using Proxmox, perform the following:
1. In the Proxmox home page, click Create VM. The Create: Virtual Machine page is
displayed.
Figure 7: Create: Virtual Machine
2. In the General tab, select the VM ID from the drop-down, provide Name in the text
box and click Next.
3. Under the OS tab, select the ISO image from the drop down. Click Next.
Figure 8: OS tab- virtual machine
4. Verify Hard disk, CPU and Memory details under respective tabs. For more
information refer Server requirements on page 8.
5. Select the desired network mode under the Network tab. Click Next.
17
6. The confirmation page is displayed, verify the changes made.
Figure 9: Confirmation page
7. Click Finish, The VM will be created with the ID. To start the VM, right click on the
VM and click Start.
8. To access the VM, double click the VM or right click the VM > Console.
To start with RHEL installation on the created VM, refer to Installing RHEL 8.2 on page
21.
Preparing installation USB media on Linux

Perform the following steps to use USB flash drive as installation media on the bare metal
machine.
1. Connect the USB flash drive to the system and execute the dmesg | grep us
command to get the details of the USB device.
2. Login as root and provide the root password when prompted.
3. Ensure that device is not mounted by executing the command findmnt /dev/device
name. If the device is mounted, unmount the device.
4. Use dd command to write the installation ISO image directly to the USB device.
NOTE: Replace /image_directory/image.iso with the full path of downloaded ISO

image.
5. Wait for completion of data transfer. The data transfer is complete when the #
prompt is displayed.
6. Logout from the root account and unplug the USB.
18
Booting the installation from USB stick
1. Disconnect any drives which are not required for installation.
2. Insert the USB device to the server.
3. Power off the server device with USB connected to the system.
4. Power on the system and press specific keys to boot from USB or configure system's
Basic Input/Output System (BIOS) to boot from USB. After a short delay, boot screen
appears. The Installation program automatically begins.
NOTE: To create a USB stick which can be used as an installation media, on any
Windows/MAC computer, follow the given link
For Windows: https://access.redhat.com/documentation/en-

us/red_hat_enterprise_linux/7/html/installation_guide/sect-making-usb-
media#sect-making-usb-media-windows
For MAC: https://access.redhat.com/documentation/en-

us/red_hat_enterprise_linux/7/html/installation_guide/sect-making-usb-
media#sect-making-usb-media-macosx
19
20
Installing RHEL 8.2
Once the System boots up with RHEL ISO image, RHEL 8.2 Home page is displayed.
Figure 10: RHEL Home page
Wait for Automatic reboot and perform the following steps to install RHEL 8.2
1. The Language Selection screen is displayed, select the required language to use
during installation.
Figure 11: Language selection
2. Click Continue, the Installation Summary window is displayed.
21
Figure 12: Installation Summary
3. Click Time & Date, the Time & Date window is displayed. Select the desired time,
date and timezone.
Figure 13: Select time and date
4. Click Done, the Installation Summary window is displayed.
5. Click Language Support, the Language Support window is displayed. Select the
additional language to be installed.
22
Figure 14: Langauage Support
NOTE: The application is not supported in other languages, therefore select

English (UK) must be selected as OS language.
7. Click Keyboard Layout, the Keyboard Layout window is displayed. Choose the
keyboard layout.
Figure 15: Keyboard Layout
23
8. Click Software Selection, the Software Selection window is displayed. Select the
button against the desired option from the below list.
To launch client and the server, select Server with GUI.

To launch server alone, select Server.
Under Add-Ons for Selected Environment tab, select the required packages. The
minimum required packages are Development Tools, FTP Server, Hardware
Monitoring Utilities, Load Balancer, Large Systems performance,Remote Management
for Linux, and Performance Tools.
10. Click Installation Destination, select Custom.
Figure 16: Installation Destination
24
11. Click Done, the Manual Partitioning window is displayed. Click "+" to add the
partition manually. For partition details refer Server partitions on page 10. Device
type -lvm and filesystem-xfs, are set by default.
Figure 17: Manual Partitioning
12. Click Done, the Summary of changes is displayed.
Figure 18: Summary of changes
13. Click Accept Changes.
25
15. Click Network & Host Name, The Network and Host Name window is displayed.
Select the required network card. Click IPv4 Settings tab, assign IPv4 address,
netmask and default gateway.
Figure 19: Network and Host Name
16. Click Save, enter the host name.
18. Click Begin Installation at the bottom of installation summary window, the
Configuration window is displayed.
26
Figure 20: Configuration Page
19. Click Root Password, the Root Password page is displayed. Type the password.
NOTE: Root user must be configured with strong password.
Figure 21: Root Password
20. Click Done, the Configuration window is displayed.
21. Wait for completion of installation, click Finish Configuration.
22. Click reboot. The Initial Setup page is displayed.
27
Figure 22: Initial Setup
23. Click License information, the License Information page is displayed.
Figure 23: License Information
24. Select "Yes, I agree to the License Agreement".
25. Click Done, the Initial Setup page is displayed.
26. Click User Creation, type Full Name, Username and Password for non-root user.
28
Figure 24: Create User
27. Click Done, the Initial Setup page is displayed.
28. Click Finish Configuration at the bottom of the page. The Login page is displayed.
Figure 25: Login page
29. Login as root user, click Sign-In.
29
Set the host name

Do the following steps to assign TJ5500 IP address to the host name of the server:
1. Login to the server as root user and perform the following tasks:
a. Edit the /etc/hosts file using the command: # vi /etc/hosts. Enter the IP address
configured on the server and the hostname. For format refer to the example
below. Save the file by pressing Esc key and typing :wq!
b. Edit the /etc/hostname file using the command: # vi /etc/hostname. Enter the
host name of server. Save the file by pressing Esc key and typing :wq!
c. Open the etc/sysconfig/network file using the command: # vi
/etc/sysconfig/network. Enter the host name. Format for entering the host name is
shown below; underscore ("_") symbol is not supported. Save the file by pressing
Esc key and typing :wq!
Figure 26: Setting Host Name
2. Execute the command # service network restart to update the changes.
The output is displayed as follows:

Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
3. To verify the change made, execute the following command:
To display the IP address of the server: # hostname -i

To display the server host name: # hostname
Post installation procedure

Prior continuing the next phase of installation,
1. Make sure IP Address of the server is set appropriately along with mask and routes.
Default route to gateway must exist if applicable.
2. Make sure the host name is set correctly.
3. Check the RAM allocation of the server, make sure the same is allocated.
4. Check the disk space allocation, this should be same as allocated during installation.
30
Installing additional packages
To install additional packages, do one of the following:
 Create repository using internet

 Create local repository
Create repository using internet
To create repository using internet, Red Hat subscriptions are necessary.
1. Subscribe to Red Hat using no-cost Red Hat developer account or by procuring valid
license for an organization.
2. Register the server to Red Hat CDN.
For developer account, use the command subscription-manager register.

Enter the developer account username and password.
For organization license, use the command subscription-manager register -
-org="<org_id>" --activationkey=<key>
3. Activate Red Hat product using the command subscription-manager attach --auto
NOTE: Use the command subscription-manager status to check subscription

status.
4. Enable the repository using the command subscription-manager repos --enable=*
Create local repository using RHEL DVD ISO
NOTE: The following procedure must be performed as root user, as it involves

installation of software in the server
1. Do one of the following,
If ISO is available in the server, perform the following:

Plug in the USB drive to the server which has the RHEL DVD ISO
Check that the USB drive has been detected using the command fdisk –l .
The command adds new block device into /dev/directory
Mount the USB drive to /mnt
Create a local directory to hold the ISO using the command mkdir
/root/ISO
Copy the rhel dvd iso from /mnt to the local directory using the command
cp /mnt/<rhel-dvd.iso> /root/ISO
If the ISO is available over the network,
31
Download the rhel dvd iso either through sftp or scp to a local directory in
the server /root/ISO
2. Once the ISO is present at /root/ISO, mount the ISO to a directory
mkdir /media/localrepo
mount -o loop /root/ISO/<RHELX8u2.iso> /media/localrepo
3. Make sure there are two directories- BaseOS and Appstream in /media/localrepo/ to
hold all the packages.
4. Backup all the repo files at /etc/yum.repos.d/ using the command
cd /etc/yum.repos.d/
mv * /tmp
5. Create new repo file and insert the following:
vi /etc/yum.repos.d/local.repo
[base]
name=RHEL8Base
baseurl=file:///media/localrepo/BaseOS
enabled=1
gpgcheck=0
[apps]
name=RHEL8Apps
baseurl=file:///media/localrepo/AppStream
enabled=1
gpgcheck=0
6. Update the local repository using the command
Yum clean all
7. Make sure local repository is getting listed using the command
yum repolist
8. Install the packages using the command
yum install
32
Enabling Network in RHEL 8.2
NOTE: By default, RHEL 8.2 will not enable network interface.
Enable the network in RHEL8.2 using the below command:
 vi /etc/sysconfig/network-scripts/ifcfg-ethX
 Change ONBOOT to “yes” from “no”
33


34
Disabling SE Linux and Firewall in RHEL
8.2
1. Login as a root on RHEL 8.2 and execute the following command: vi
/etc/selinux/config
2. In the config file, change the value for SELINUX=disabled
3. Disable firewall using the command: service firewalld stop
4. Disable starting firewall service during bootup using the command: systemctl disable
firewalld.service
5. Reboot RHEL8.2 system.
Whitelists in the firewall

Whitelists in firewall allows the user to allow client and node access in NMS in order to
avoid disabling of the firewall completely.
 To allow the incoming connections from 192.168.0.1, use the command # iptables -A
INPUT -s 192.168.0.1 -j ACCEPT
 To allow outgoing connection from 192.168.0.1, use the command # iptables -A
OUTPUT -d 192.168.0.1 -j ACCEPT
35
36
Changing the Time Zone
In order to set the time zone on the server, execute the command: ln -sf
/usr/share/zoneinfo/<time zone/area > /etc/localtime where <time zone/area > is the
time zone and the location where the server is installed. For example, ln -sf
/usr/share/zoneinfo/Asia/Kolkata /etc/localtime
37
38
Checks on Linux Server
Ensure that the below protocols and softwares are installed.
 gcc*
 libXfont2
 xorg-x11*
 cpan
 libvirt-client
 openssl-devel
 httpd
 mod_ssl
 mod_session
 perl-LWP-Protocol-https
 perl-devel
 perl-Time-HiRes
If the above protocols and softwares are not installed, execute the following commands
for the installation in the command prompt:
To install gcc*
Command: yum install gcc*
To install libXfont2
Command: yum install libXfont2
To install xorg-x11*
Command: yum install xorg-x11*
To install cpan
Command: yum install cpan
To install libvirt-client
Command: yum install libvirt-client
To install openssl-devel
Command: yum install openssl-devel
39
To install httpd
Command: yum install httpd
To install mod_ssl
Command: yum install mod_ssl
To install mod_session
Command: yum install mod_session
To install perl-LWP-Protocol-https
Command: yum install perl-LWP-Protocol-https
To install perl-devel
Command: yum install perl-devel
To install perl-Time-HiRes
Command: yum install perl-Time-HiRes
Install the following dependencies:
cpan install Test::More
cpan install Devel::CheckLib
cpan install Test::Deep
cpan install LWP::Protocol::https
NOTE: cpan modules require internet to be installed (no subscription required).
40
Apply IP tables
This procedure enables iptables in the RHEL server where TJ5100/TJ5500 services are
running. This will apply iptables DROP INPUT rules allowing access to few IP addresses or
a range of IP addresses and restricts MySQL access to localhost and TJ5100/TJ5500
servers only. This procedure is based on IP address only, irrespective of the ports or the
protocol.
Before applying iptables rules in TJ5100, TJ5500 and TJ5500 DB server, TJ5100/TJ5500
client access, SSH to the servers and MySQL connection from any other system would be
allowed. After applying iptables rules, only whitelisted Client IP addresses will be able to
access the servers. MySQL access through port 3306 will be restricted to localhost,
TJ5100/TJ5500 servers and its Hotstandby servers.
IP addresses to be whitelisted to allow access to the server database:
TJ5100 Master and Slave IP address including Virtual IP address

Router IPs of all nodes, Ethernet IP and Router IP Address of gateway
nodes
TJ5500 Master and Slave IP address including Virtual IP. Additionally, IP
address of DB server in case clustering mode
TJ5100/TJ5500 Client IP addresses
IP addresses to be whitelisted to allow access to MySQL:
TJ5100 Master and Slave IP address including Virtual IP address

TJ5500 Database servers: Master, Slave and DB server (Master and Slave)
IP address including Virtual IP address
TJ5500 Application Server
Procedure
Apply iptables rules on a RHEL server with following steps:
NOTE: Do not copy and paste the commands mentioned in this procedure.
1. Login to the RHEL server as "root" user where TJ5100/TJ5500 is running.
2. Stop and disable firewall service on the server by executing the commands:
systemctl stop firewalld.service

systemctl disable firewalld.service
41
3. Apply iptables rules by executing the following commands:
Command Description
iptables -P INPUT ACCEPT ; iptables -F Flushes out the existing iptables rule.
iptables -P FORWARD DROP Drops the forward packets. This command is
applicable for a router.
iptables -P OUTPUT ACCEPT Accepts/allows all outgoing packets.
iptables -A INPUT -m state --state Drops all invalid connections established to the
INVALID -j DROP RHEL server.
iptables -A INPUT -i lo -j ACCEPT Allows full access to localhost communication.
iptables -A INPUT -s <Server IPs> -j Here <Server IPs> indicates IP address of
ACCEPT TJ5100/TJ5500 Master, Slave servers and the
Virtual IP address. Only these IP address can
access the RHEL server.
iptables -A INPUT -s <Server IP> -j Here <Server IP> indicates IP address of the
ACCEPT server itself i.e. TJ5500 Database server in case of
Clustering mode. Only these IP address can access
the RHEL server.
iptables -A INPUT ! -s <Server IPs> -p Here <Server IPs> indicates IP address of
tcp --dport 3306 -j DROP TJ5100/TJ5500 Master, Slave servers and the
Virtual IP address.
Except these IPs entered here, all other IP address
trying to access MySQL through TCP port 3306 will
get dropped.
iptables -A INPUT ! -s <Server IP> -p Here <Server IP> indicates IP address of TJ5500
tcp --dport 3306 -j DROP Database servers in case of Clustering mode.
Except these IPs entered here, all other IP address
trying to access MySQL through TCP port 3306 will
get dropped.
iptables -A INPUT -s Here <IPAddress> indicates Client IP address with
<IPAddress/mask> -j ACCEPT subnet mask defining the range of IP addresses to
access the RHEL server.
iptables -A INPUT -s <IPAddress> -j Here <IPAddress> indicates Client IP address to
ACCEPT access the RHEL server.
iptables -P INPUT DROP Drops everything except the above rules.
4. Save applied iptables rules by executing the command: /sbin/iptables-save >

/etc/sysconfig/iptables
5. To restore iptables manually, execute the command /sbin/iptables-restore

6. To restore iptables automatically across server reboot, append a line /sbin/iptables-

restore > /etc/sysconfig/iptables in /etc/rc.local file in the server.
42
Apply IP tables
Guidelines
 Wrong application of iptables rules may block Hot StandBy replication or TJ5100
communication to TJ5500/nodes and server access from client PC.
 Iptables is based on access/deny IPlist and restrict MySQL access to only
TJ5100/TJ5500 servers.
 Command to check the applied iptables rules is: iptables -L INPUT -v -n --line-
number.
 After applying iptables rules:
There will be no response for ping from clients to TJ5100 or TJ5500 or
TJ5500 DB servers except whitelisted client IPs added in iptables rules.
No client will be able to access TJ5100 or TJ5500 except those IPs added in
iptables rules.
TJ5500 MYSQL Database via port 3306 will get restricted to TJ5500 servers
only.
MySQL restriction is not necessary in TJ5500 Application server.
 To append one or more rule in iptables in order to allow access to TJ5100/TJ5500
server:
iptables -A INPUT -s <IPAddress> -j ACCEPT
iptables -A INPUT -s <IPAddress/mask> -j ACCEPT
 To remove iptables rules, execute the command:
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -F
Save iptables rules by executing the command: /sbin/iptables-save >
43
44
Installing EMS/NMS/RAS
To install EMS/NMS/RAS refer to NMS TJ5500 Installation and Commissioning Guide.
45
46
Cloning
Cloning is performed when there are multiple EMS to be configured in a single virtual
environment that are similar in terms of hardware requirement.
Cloning Virtual Machines

Perform the following steps to clone Proxmox Virtual Machine
Clone the VM
Perform the following steps to clone the VM:
1. Select the VM from Proxmox GUI.
2. Right-click and select clone, cloning dialog box is displayed.
3. Select target node, VM ID and VM name from the dialog box, click on clone.
Post cloning, change the host name and mac address.
Change the VM host name
Perform the following steps on the On Linux guest OSes to change the host name:
1. log into a vm terminal as root.
2. change the /etc/hostname file content to the new hostname (eg: "#nano
/etc/hostname")
3. change the /etc/hosts file content accordingly (eg: "#nano /etc/hosts")
4. reboot the vm ("#reboot now")
Change the MAC address
When an existing VM is duplicated, the mac address also gets duplicated. If VM has only
one virtual NIC, perform the following steps:
1. Stop the VM.
2. Remove the virtual nic (eg: eth0) from pve web interface.
3. Create a new virtual nic, this obtains a new MAC and VM always refers to this as eth0.
4. Restart the VM to check everything is working fine.
47
This is done at the host level, so is guest OS independent.
NOTE: Since it is a 1:1 disk to disk cloning, the Hard disk space cannot be
changed post cloning, but the RAM/CPU parameters can be modified.
Cloning RHEL 8.2 Server

Before cloning RHEL 8.2 server, perform the following:
 Install RHEL 8.2 in Virtual Machine using RHEL 8.2 iso image.
 Install the required packages.
Refer to the Prerequisite for Installing RHEL 8.2 and Installation procedure sections for
installing RHEL 8.2 server.
NOTE 1: Make sure that no EMS, NMS or RAS servers and MySQL are installed
in the virtual machine which is being used for OS cloning.
NOTE 2: Snapshots depicted in this procedure is only for reference.
Perform the following steps for cloning RHEL R8.2 server:
1. Download VMware vCenter Converter Standalone.
2. Once you have installed VMware vCenter Converter Standalone, run the converter.
The converter should be launched in a new window.
Figure 27: Selecting Convert machine
3. Click Convert machine menu. The conversion wizard is launched. On the Source
System screen, select one of the following:
Powered on state: for remote Windows machine, a remote Linux

machine, or this local machine for the source type.
Powered off state: for a VMware Infrastructure virtual machine, a
VMware Workstation virtual machine, another VMware virtual machine, or
Hyper-V Server for the source type.
For our purpose, the Powered off option is selected and VMware
Infrastructure virtual machine is chosen from the drop-down menu.
4. Specify the server connection information by entering the IP address of your

VMware Infrastructure virtual machine, and input the User name and Password of
an account with administrative permissions for the VMware Infrastructure virtual
machine. Click Next to continue.
48
Cloning
Figure 28: Conversion wizard
5. Select the source VMware Infrastructure virtual machine to which we have to clone.
After selecting your source VM, click Next.
49
Figure 29: Selecting your source VM
6. Set the host for the new virtual machine by selecting your destination system as
VMware Infrastructure virtual machine from the drop-down menu and, specify
the VMware Infrastructure server details by entering the IP address of destination
VMware Infrastructure virtual machine, then input the User name and Password of
an account with administrative permissions. Click Next to proceed.
50
Cloning
Figure 30: Select destination VM
7. A security warning pop-up message is displayed. Click Ignore to continue.
Figure 31: Security warning
8. Set the parameters for the destination virtual machine by entering the Name and
selecting the location of the destination VM. Then click Next to continue.
51
Figure 32: Set the Destination VM parameters
9. Select the location on which the new VM should run. Select the datastore attached to
that server and specify the virtual machine version. Click Next.
52
Cloning
Figure 33: Selecting the location for the new VM
10. Set the parameters for the conversion task. Click on the edit link displayed against
each of the parameters with the required values given in the following:
a. Data to Copy: You can select,

i) The data copy type as disk-based or volume-based.
ii) The disk provisioning type as Thick or Thin. The Thick disk type is selected by
default.
iii) The destination datastore for your virtual disks.
b. Devices: You can set the amount of virtual memory, the number of virtual
processors, the number of cores per processor, and the disk controller for the VM.
c. Networks: You can select the number of virtual network adapters for the VM and
specify the networks to which they should be connected, as well as virtual network
controller type.
d. Advanced options: These options can be configured for Windows OS machines.
Tick the appropriate checkboxes for powering on the destination VM, installing
VMware Tools, customizing guest preferences, removing System Restore
checkpoints, and/or reconfiguring the destination VM after conversion.
e. Throttling: You can set up CPU throttling if you want to control the CPU resources
used by the converter for the current task. This option lets you preserve enough
processor resources to run other tasks, if needed. Network bandwidth throttling
allows you to control network bandwidth; this can be useful in cases where you
want to keep your network-related services and applications functioning properly
during conversion.
53
After configuring the parameters to suit your needs, click Next.

Figure 34: Setting parameters for conversion
11. Check the summary. If you are satisfied that all the settings are correct, click Finish
to start conversion.
54
Cloning
Figure 35: Summary- Reviewing conversion parameters
12. You can now see the status of your conversion job in the main windows of VMware
vCenter Converter. Similarly, you can add more conversion jobs.
Figure 36: Status of the conversion
55
Post-cloning procedure
1. Start the cloned VM; let the source VM in powered off mode to avoid duplicate
IP/MAC issues in the network.
2. Change IP address, MAC address, Device name, Gateway, DNS parameters in the
cloned VM by performing the following steps:
In RHEL terminal, enter the command: nmtui

edit a connection
select active interface
update IP address, MAC address, Device name, Gateway, DNS and press
OK.
3. Change HOSTNAME by updating the /etc/hostname file.
4. Update /etc/hosts file with IP and hostname of the VM.
5. Restart the VM.
6. EMS/NMS/RAS servers can be installed, when VM server comes up.
56
Cloning
NOTE:
• Make sure that IP and MAC address should not be same across the OS and
VMs.
• The given cloning steps are applicable to only VMWare’s ESXI based
virtualization
57

Tj5500-Tj5100 Im Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tj5500-Tj5100 Im Guide

Uploaded by

Copyright:

Available Formats

NMS TJ5500 & EMS TJ5100

Infrastructure Management Guide

Issue Date: 16-Apr-2021

Warning and Disclaimer

Technical Support Information

Additional Learning Resources

Get started with installation 7

Installing additional packages 31

Changing the Time Zone 37

Document Name and ID Description

This page is intentionally left blank

Prerequisite for Installing RHEL 8.2

 Server through a local console.

 Any user data

Save all the above mentioned backups at a remote location.

Table 1: Hardware requirements for TJ5100

Components 3k NEQs 6k NEQs

Memory 32 GB Physical memory 32 GB Physical memory (RAM)

Table 2: Hardware requirement for TJ5500

Components 15k NEQs 30k NEQs (10 EMS with 3k NEQs

Memory 32 GB Physical memory 64 GB Physical memory (RAM)

Table 3: Hardware requirements for TJ5100 and TJ5500

Memory 32 GB Physical memory (RAM)

Table 4: Hardware requirement for TJ5500

Memory Application Server Database Server

Radius Administration Service (RAS)

Components 60k NEQs

Memory 32 GB Physical memory (RAM)

Table 5: Server Partitions for TJ5100 server

Partition Disk Allocation in GB (For 500 Application

Table 6: Server Partitions for TJ5500 server

Partition Disk Allocation in GB (for 600 Application

When TJ5100/TJ5500 detects disk usage percentage of a partition exceeding the

In case of extra hard disk space availability, it can be assigned or extended to

TCP/UDP ports used by TJ5500

The following table lists the ports used by TJ5100 server:

Table 7: TCP/UDP Ports of TJ5100

Protocol Port Service Name Establishment of

Table 8: TCP/UDP Ports of TJ5500

Protocol Port Service Name Establishment of

TCP 22 Hotstandby DBDump transfer TJ5500 master and slave

Protocol Port Service Name Establishment of

 Installation steps for creating Virtual Environment (VE)

Installing Virtual Environment

Installing Proxmox Server

 Preparing installation media

Preparing installation media

1. Download the installer ISO image from:

An ISO image file ready to burn to a CD or DVD.

NOTE: It is recommended to use USB flash drive to perform installation quickly.

Installing Proxmox Server

Figure 1: Proxmox VE menu

3. Click options and select the target file system.

Figure 2: Target hard disk

4. Select target disk and click OK.

Figure 3: Location and Time Zone

Figure 4: Administration Password and E-mail Address

Use a minimum password length of 12 to 14 characters.

Include lowercase and uppercase alphabetic characters, numbers, and symbols.

7. Click Next, the Management Network Configuration page is displayed. Provide

Figure 5: Management Network Configuration

8. Click Next, the Summary of options selected is displayed.

Figure 6: Summary of changes

Creating Virtual Machine using Proxmox