CONFIGURATION OF LAG FOR DISCOVERY IN

LAGEMS/NGEMS

Following procedure is to follow for proper discovery of

LAG nodes in IEMS and NGEMS.

1) LOGIN TO LAG NODE

ssh root@10.187.212.34 (Physical IP of LAG)
Passwd- root
root@NGTK>
i) Go to mmc by “chroot’ command.
$ chroot / mmc

ii) Go to directory /usr/local/bin/lag/AGENT/lagagent.

Sh-2.05b#cd /usr/local/bin/lag/AGENT/lagagent

iii) Open LAGSystemInfo.txt file and modify it.

sh-2.05b# vi LAGSystemInfo.txt
Replace the “C-DOT Campus” entry with desired region
code. For example North_HA_124_245
(zone_circle_Area_Exchange level) is the region code of
Haryana and remove last line “15”.
Note- this region code should be configured in NGEMS
North-Zone or region
HA-circle
124- Area code
245- Exchange Level
For example :
Default file
CDOT LineAccessGateway
1.1.3.6.1.4.1.5380.1.1.2
Group Leader MAX-NG CDOT Delhi
lagdomain
 CDOT-CAMPUS
15

Modified file
CDOT LineAccessGateway
1.1.3.6.1.4.1.5380.1.1.2
Group Leader MAX-NG CDOT Delhi
lagdomain
North_HA_124_245

(To save vi file press “Esc” key and type “:wq!”)

Initialize the LAG system to get above changes effective.

2) REQUIRED CONFIGURATION IN IEMS FOR

DISCOVERY OF LAG NODE

 Login iems (lagems )server by user account

 ssh admin@<iems ip address>
 login-admin
 passwd-xxxxxx
 cd AdventNet/WebNms/conf
 Edit in file “NmsProcessBe.conf” in last according to
below

PROCESS com.cdot.iems.IMNNorthInterfaceProcess
ARGS NGEMS_SERVER_IP <NGEMS IP > NGEMS_SERVER_PORT 3652
#ARGS NULL

After these steps (To save vi file press “Esc” key and type “:wq!”)
 Service iemsd stop ( to stop iems application).
Enter following
User-root
Passwd-teamimoa
 Service iemsd start ( to start IEMS application)
 One can verify whether IEMS application is started or not
using folloiwng
$ps –ef |grep java
java application should be run

Note –This configuration should be done in both iems servers of PR

setup and GR setup

3) CONFIGURATION OF DOMAIN NAME OF LAG (BM

NAME))

To configure domain name of LAG in lagems , following steps

needs to be done

Login to lagems with admin account

Login- admin
Passwd-xxxxxxxxxx
$cd /etc
and edit the hosts file , define the LAG with name as follows
Floating ip address of LAG lagname lagname
(For example)
$vi hosts
192.168.103.194 lagems lagems
192.168.103.115 bmtwentyone bmtwentyone
192.168.103.27 bmtwentytwo bmtwentytwo
And save this file

and rediscover the lag node with ip address .It will be reflected
with name in lag ems and ngems.
 NOTE: Pls note that while naming LAG , following points needs
to take care
1) Name should not be BM-1 , BM-11 , BM-12 etc . It should be
BMone,BMeleven…..like that means no numerical digit/under
score /dash should be used.

After this configuration

 Open browser and insert the ip address of iems server
 10.187.0.21:9090
 Enter user-root
 Passwd- teamimoa
 Select site and exchange
 Run “Add node “ command
 Node successfully added
 LAG node should be reflected on NGEMS automatically
 Verify the lag node on NGEMS in access node
 Open NGEMS <10.187.0.41:9090

4) CONFIGURATION IN IEMS SERVER FOR DISCOVERY

IN NGEMS

Steps for installation of core agent in IEMS

 ssh root@<ip address of iems server>
 Passwd-xxxxxxxx
 Copy coreagent tar file from PC to all IEMS servers by FTP(PR
and GR site) in root path
 “PATCH7-Over-COREAGENTSL3_1_1.8_1-SNMP-PRGR”
 Untar the tar file by command
 tar –xvf PATCH7-Over-COREAGENTSL3_1_1.X_1-SNMP-
PRGR
 we will get some tar files, select following tar file
 “coreagents3_1_1.8_1_iems_agent.tar”
 Again untar this tar file by using command
 tar –xvf coreagents3_1_1.8_1_iems_agent.tar
 we will get following files
 iems & install
 run install script on PR site
 ./install
 Enter the path
 /AGENT
 Enter the Physical IP address of the device :
 10.187.0.19(physical copy -0 IEMS server)
 DEVICE_INTERNAL_IP = 10.187.0.19
 Enter the Virtual IP address of the device :
 10.187.0.21(virtual copy of IEMS server)
 DEVICE_EXTERNAL_IP = 10.187.0.21
 Do you want to configure agent in Simplex or Duplex Mode :
 1 : Simplex Mode
 2 : Duplex Mode
 2
 Enter the MATE AGNET IP address :
 10.187.0.20 (physical copy -1 IEMS server )
 MATE_IP = 10.187.0.20
 Enter IP address of the Advanced Management Module :
 10.187.0.110
 AMM_IP[] = 10.187.0.110
 Is this site configured as PR or GR ?? Please enter choice :
 1 : PR
 2 : GR
 1
 You have listed this site as PR
 Do u want to configure IPs for GR Manager as well ?? Please
enter choice
 1 : NO @@ only PR present @@
 2 : YES @@ Corresponding GR is also present @@
 2
 Enter the Physical IP address of first GR Manager :
 10.187.1.147(physical copy -0 IEMS server of GR site)
 GR1_IP[] = 10.187.1.147
 Enter the Physical IP address of second GR Manager :
 10.187.1.148(physical copy -1 IEMS server of GR site)
 GR2_IP[] = 10.187.1.148
 Enter the Virtual IP address of GR Site :
 10.187.1.149 (Virtual IEMS server of GR site)
 GR_VIP[] = 10.187.1.149
 Enter Number of EMS Managers Supported
 4
 NO_OF_EMS_MANAGERS = 4
 Enter the IP address of the EMS Manager :
 10.187.0.39 (copy-0 PR NGEMS)
 EMS_MANAGER_IP[0] = 10.187.0.39
 Enter the IP address of the EMS Manager :
 10.187.0.40 (copy-1 NGEMS of PR site )
 EMS_MANAGER_IP[1] = 10.187.0.40
 Enter the IP address of the EMS Manager :
 10.187.1.167(copy-0 NGEMS of GR site )
 EMS_MANAGER_IP[2] = 10.187.1.167
 Enter the IP address of the EMS Manager :
 10.187.1.168 (copy-1 NGEMS of GR site)
 EMS_MANAGER_IP[3] = 10.187.1.168
 Enter Number of GR Managers Supported
 6
 NO_OF_DEVCONF_MANAGERS = 6
 Enter the IP address of the GR Manager :
 10.187.0.10 (SBC-0 of PR site)
 DEVCONF_MANAGER_IP[0] = 10.187.0.10
 Enter the IP address of the GR Manager :
 10.187.0.11 (SBC-1 of PR site)
 DEVCONF_MANAGER_IP[1] = 10.187.0.12
 Enter the IP address of the GR Manager :
 10.187.0.12(SBC floating of PR site)
 DEVCONF_MANAGER_IP[2] = 10.187.0.12

 Enter the IP address of the GR Manager :

 10.187.0.27 (c4-0 of PR site)
 DEVCONF_MANAGER_IP[3] = 10.187.0.27
 Enter the IP address of the GR Manager :
 10.187.0.28(c4-1 of Pr site)
 DEVCONF_MANAGER_IP[4] = 10.187.0.28

 Enter the IP address of the GR Manager :
 10.187.0.29 (c4-floating of PR site)
 DEVCONF_MANAGER_IP[5] = 10.187.0.29

 do you want to enable EMS Manager service (y/n) :

 y
 do you want to enable Device Configuration Manager service
(y/n) :
 y
 Enter the Region Code for the Device :
 North_PR_xxx
 Enter the Display Name for the Device :
  IEMS_PR
Note- Follow the same configuration of second copy of
PR site

5) INSTALLATION OF CORE AGENT IN GR SITE

 run install script on GR site
 ./install
 Enter the path
 /AGENT
 Enter the physical IP address of the device :
 10.187.147 (physical copy -0 IEMS server of GR site)
 DEVICE_INTERNAL_IP = 10.187.1.147
 Enter the Virtual IP address of the device :
 10.187.1.149 (Virtual IEMS server of GR site)
 DEVICE_EXTERNAL_IP = 10.187.1.149
 Do you want to configure agent in Simplex or Duplex Mode :
 1 : Simplex Mode
 2 : Duplex Mode
 2
 Enter the MATE AGNET IP address :
 10.187.1.148 (physical copy -1 IEMS server of GR site)
 MATE_IP = 10.187.1.148
 Enter IP address of the Advanced Management Module :
 10.187.1.220
 AMM_IP[] = 10.187.1.220

 Is this site configured as PR or GR ?? Please enter choice :
 1 : PR
 2 : GR
 2
 You have listed this site as GR
 Do u want to configute IPs for PR Manager as well ?? Please
enter choice
 1 : NO @@ only GR present @@
 2 : YES @@ Corresponding PR is also present @@

 Enter the Physical IP address of first PR Manager :

 10.187.0.19(physical copy -0 IEMS server of PR site)
 PR1_IP[] = 10.187.0.19

 Enter the Physical IP address of second PR Manager :

 10.187.0.20(physical copy -1 IEMS server of PR site)
 PR2_IP[] = 10.187.0.20

 Enter the Virtual IP address of PR Site :

 10.187.0.21 (Virtual IEMS server of PR site)
 PR_VIP[] = 10.187.0.21
 Enter Number of EMS Managers Supported
 4
 NO_OF_EMS_MANAGERS = 4
 Enter the IP address of the EMS Manager :
 10.187.0.39 (copy-0 NGEMS of PR site )
 EMS_MANAGER_IP[0] = 10.187.0.39

 Enter the IP address of the EMS Manager :

 10.187.0.40 (copy-1 NGEMS of PR site )
 EMS_MANAGER_IP[1] = 10.187.0.40

 Enter the IP address of the EMS Manager :

 10.187.1.167 (copy-0 NGEMS of GR site )
 EMS_MANAGER_IP[2] = 10.187.1.167

 Enter the IP address of the EMS Manager :
 10.187.1.168 (copy-1 NGEMS of GR site)
 EMS_MANAGER_IP[3] = 10.187.1.168
 Enter Number of GR Managers Supported
 6
 NO_OF_DEVCONF_MANAGERS = 6
 Enter the IP address of the GR Manager :
 10.187.1.138 (copy-0 SBC of GR site)
 DEVCONF_MANAGER_IP[0] = 10.187.1.138

 Enter the IP address of the GR Manager :
 10.187.1.139 (copy-1 SBC of GR site )
 DEVCONF_MANAGER_IP[1] = 10.187.1.139

 Enter the IP address of the GR Manager :
 10.187.1.140 (Virtual SBC of GR site)
 DEVCONF_MANAGER_IP[2] = 10.187.1.140

 Enter the IP address of the GR Manager :
 10.187.1.155 (C4-0 of GR site)
 DEVCONF_MANAGER_IP[3] = 10.187.1.155

 Enter the IP address of the GR Manager :
 10.187.1.156 (C4 -1 of GR site)
 DEVCONF_MANAGER_IP[4] = 10.187.1.156

 Enter the IP address of the GR Manager :
 10.187.1.157( Virtual C4 of GR site)
 DEVCONF_MANAGER_IP[5] = 10.187.1.157

 do you want to enable EMS Manager service (y/n) :
 y
  do you want to enable Device Configuration Manager service
(y/n) :
 y
 Enter the Region Code for the Device :
 North_DR_xxxx
 Enter the Display Name for the Device :
 IEMS_DR

Note- Follow the same configuration for second

copy of GR site
 start the process for agent
 #> cd /AGENT/cagent/bin
 #> ./agentd &
 We can check the status of agent
 /AGENT/cagent/bin/xmlagent
 /bin/bash /AGENT/cagent/agentdService
 If you want to stop agent process forcefully
 To Stop agentdService by command
 Kill -15 process id of agentdService
 Kill -15 process id of xmlagent

6) ENVIRONMENT FOR PR-GR DB/FILES REPLICATION

REQUIRES:
 Installation for matkit
 Go to root account
 Login-root
 Passwd-xxxxxxx

 copy ngems environment tar file in root path of iems servers
(PR and GR)
 tar –xvf ENVIRONMENT_NGEMS3.tar
 we will get ENVIRONMENT_NGEMS3
  cd ENVIRONMENT_NGEMS3
 cd prgr
 run script
 ./mat_uni.sh
 to verify the maatkit
 $ type mk-table-sync
 When Maatkit is installed
 Usage: mk-table-sync [OPTION...] DSN [DSN...]

 Errors in command-line arguments:
 * Specify at least one of --print, --execute or --dry-run
 * At least one DSN is required, and at least two are required
unless --sync-to-master or --replicate is specified

DNS configuration for LAG

For DNS following entries should be configured during installation.
DNS Based routing to be done? Enter your choice{yes/no]
yes
Enter the search domain
maxng.bsnl.in
Enter the IP address of primary DNS server
192.168.103.75
Enter the IP address of secondary DNS server
192.168.60.78
Enter the DNS Name for Soft switch
sbc.maxng.bsnl.in