P58-Ngems-Not-Release Ngemsl3 1 1.18 1

Note
MAXNG-NGEMS-SRN-3_1_1.18_1
Software Release Notice

for
NGEMSL3_1_1.18_1
Released on: 25-Apr-2018
Any hardcopy unless authorised or a softcopy in a directory other than the central repository
is an Uncontrolled Copy.
This hardcopy of the document is a Controlled Copy only when signed by an authorized signatory.
Issued to: ___________________________

Signature and Date
C
E
N
T
COPYRIGHT © 2013, C-DOT. All rights reserved.

No part of this document may be reproduced in any form without prior written permission from C-DOT.
Participation
This document has been authored/modified by
Leena Ambwani
with contributions from

NGEMS Development Team
Comments, suggestions and queries pertaining to this document should be addressed to
Group Leader
Name: Meenu Gupta
e-mail: meenu@cdotd.ernet.in
COPYRIGHT © 2015, C-DOT. All rights reserved.

No part of this document may be reproduced in any form without prior written permission from C-DOT.
Software Release Notice for NGEMS3_1_1.18_1
Table of Contents
1. Introduction..............................................................................................................................................1
1.1. Objective and background................................................................................................................1
1.2. Features.............................................................................................................................................1
1.3. Known exceptions in the Release.....................................................................................................3
1.4. Status of pending Change Requests and Failures.............................................................................3
1.5. Software Release details...................................................................................................................3
1. Included modules..............................................................................................................................4
1.6. Other Dependency............................................................................................................................4
1.7. Pre-Installation procedure................................................................................................................4
1.8. Installation procedure.......................................................................................................................4
1.9. Notes.................................................................................................................................................6
1.10. Annexure –A................................................................................................................................8
CDOT-NGEMS-SRN-1_1
iii
Copyright © 2013, C-DOT.
Software Release Notice for MAXNGEMS with Release no. MAXNGEMS1_1_1.18_1
MAXNG-NGEMS-SRN-16
iv
Software Release Notice for NGEMSL3_1_1.18_1
1. INTRODUCTION
1.1. Objective and background
The release NGEMSL3_1_1.18_1 is the patch release generated to include patches over
NGEMSL3_1_1.17_1 and patches- patch1, patch2, patch3
1.2. Features
This release includes following features in addition to those given in NGEMSL3_1_1.17_1 +
patches (1,2,3)
1. SG TARs reported by validation for NGEMS17 + patch3 release (Details in Section 1.4)
2. CACU Tars reported by validation for NGEMS17 + patch3 release
3. Policy changes for WebNms backup (7 days + auto schedule)
4. TAR: Event reports does not have time option selection
5. Mysql Connections were not getting closed after taking the count of IR alarms from Database. It was
incrementing DB connection as one connects to client.
6. TAR: Region code related issue for core modules
7. DB syncing strategy (PR-GR) removed from MAATkit to Mysql slave replication
8. Dependency of client pinging PR/GR site DNS servers removed
9. Client CACU code optimization
10. Mapretrofit utility needs to be run in case of existing NGEMSDB data in field. Procedure also given in
the Patch3
11. SG code optimizations
12. For testing Audio alarms, ENVIRONMENT deliverable was modified dated 7th Feb 2018 in CRS
13. Details of release/patch given in XEyeP2.12 (NGEMSL3_1_1.12_1 + patches) and earlier is shifted to
Annexure-A
MAXNG-NGEMS-SRN-3_1_1.18_1
1
Important: Procedure to run optimization scripts and MapRetrofit for BSNL
Step 1: ShutDown NGEMS Active and standby servers both.

Step 2: Install manager release
Step 3: At both the blades, run the script as follows:
(pls note that server should be down at this time)
$ cd /opt/ngems/AdventNet/WebNMS/bin
$ ./RunOptimizationForBSNL.sh
(This script is to be run for client optimization for BSNL. This needs to be run on both blades)
$ cd /opt/ngems/ngemsMapBE/conf
$ vim mapBE.properties
(Edit the entries of SERVER_HOST, masterSSIP, prSite, drSite and save)
SERVER_HOST=10.187.0.39
masterSSIP=10.187.0.15
userName=ngcpe
passWord=ngcpe
prSite=GGN
drSite=CHD
$ cd /opt/ngems/ngemsMapBE/scripts
$ ./MapRetrofit.sh
(this utility shall convert all circle and city mapnames to uppercase)
(Pls note: The MapRetrofit utility may be run on primary blade only, if DB replication is working,
else to be run on both blades)
Step 4: Start both the NGEMS servers in Primary and standby mode.
Important: (Procedure to add C5/SBC SNMP node)
As the core chassis node data expected in field will be earlier data (created
using NGEMSL3_1_1.12_1) and shall not be discovered again, it is required
to use the following configuration steps at client with XEyeP13 release.
These configuration steps are to be done one time only for all discovered
chassis.
The client screenshots for the configuration steps are attached.
1. Right click on core HP chassis, to view core modules (screenshot attached)
2. Double Left click, on the blank screen to open Map Properties panel
3. Click on Criteria in the left panel, to open Map Criteria window
4. Add C5V2,SBCV2 (capital letters) in the type field (screenshot attached)

5. Select checkbox (Save changes on server) and click on Modify to save the
changes (screenshot attached)
6. Repeat steps 1,2,3 to verify the changes done
7. Delete earlier discovered C5 XML Node and Add C5 node via SNMP, it shall be
visible now
The above procedure needs to be verified and conveyed in the field for XEyeP13
If core chassis is deleted and added for XEyeP13 release, no such steps will
be required, SNMP C5 node can be added directly.
(Following were also part of NGEMSL3_1_1.17_1+PATCH3-Over-NGEMSL3_1_1.17_1-

ILD_MISC_CLNT_CACUMAP changes)
1. CACU chassis loading time improved by using MapChassis.

2. Steps taken to improve Client loading time (extra jars, maplayout classes removed, emsresource.jar
reduced, image sizes reduced)
3. Solution for LAG form opening issue at thin client
4. Client termination is proper now
5. Idle client termination is increased to 24 hours
6. HP chassis related alarms to be generated at the time of discovery/rediscovery
7. Scripts to be run for BSNL
(Following were also part of NGEMSL3_1_1.17_1+PATCH2-Over-NGEMSL3_1_1.17_1-ILD_MISC

changes)
Patch2 changes (includes patch1)
1. Changes related to thin client Audio

2. Policy adding and Scheduling process
3. Changes corresponding to Agent modifications (NGEMS, IEMS, SP)-single card discovery and alarm db
correction
4. Bug fixes(C5 traps, method for getting SERVERID from client).
5. Utility to delete maps
6. Reinitialize nms script change
7. Map names to be made in upper case
8. Issue of MapUserAdmin crash sometimes
9. CACU API domain name related changes to improve the Chassis GUI performance
10. Core node refresh changes
(Following were also part of NGEMSL3_1_1.17_1+PATCH1-Over-NGEMSL3_1_1.17_1-

ILD_FEATURECODE changes)
Patch1 changes
1. Webmgr changes: Patch is for ILD Tariff implementation and Length change for Feature Code.
(Following were also part of NGEMSL3_1_1.16_1 + PATCH2-Over-NGEMSL3_1_1.16_1-V5AG-AI-

CDR-save-with-fieldpatch-Manager_Module_Changes)
Patch2 changes:
1. Changes given in field release (patch11), patch12, patch13, patch14 over NGEMS1.12
2. At NGEMS Frontpage, Ratingengine is corrected as ratingengine in urls.xml
3. CDR save command headers related changes
4. alert_counts panel disabled to improve client performance for thin clients
5. Solution for C4 DNC update command time scheduling bug reported.
6. Solution for correct port numbers for HP Ethernet port alarms
7. LIS PIC card related input fields removed from LIS add node form
8. Infrastructure alarms region code changed as per core site
9. Solution for EBM postdated alarms
(Following were also part of NGEMSL3_1_1.16_1 + PATCH1-Over-NGEMSL3_1_1.16_1-V5AG-AI-
Range-Manager_Module_Changes)
Patch1 changes:
Manager Module Changes:

Change to support v5ag commands for increased AI range (from 25 to 150) and minimum L3 address value
(0)
1.3. Known exceptions in the Release
 CACU discovery time is more if number of region maps are too high. Pls delete the maps of other
zones which may not be required using DeleteMaps Utility.
 If LMG chassis (for MTNL) connectivity goes down, and comes up after some time, the LMG
chassis loading time may be increased to 15-20 sec, if screen is switched between Alarms view
and chassis view. This behavior may continue till connectivity/status of all the cards is completely
restored and updated in EMS. Hence it is advised not to switch to Alarms view, when the test case
is in progress.
1.4. Status of pending Change Requests and Failures
SOLVED in NGEMS1.18:
Failures reported are as
96661: solved in 1.18

96662 : shown to validation team (success/failure pop up added ) 1.18
96656 : Not repeatable
96659 : Not repeatable
96660 : solved in 1.18
96635, 96636: solved in 1.18
Following tars are marked SOLVED in SWIM -
1. CACU SLM tars to be solved at 95963, 95213,91692

Device
2. V5,/PRI/SG device issues 95965, 95885,94230,96168,96658,96657
3. TAR Solved ( configuration issue) 95969,

96680,96678,96677,96676,96675,96674,96673
4. Tars Solved ( already fixed) 95966,

95205,95221,91298,91364,96560,96661,96660,96662
5. tars not repeatable 96631,96632,96638,96659,
96000
C4 Configuration commands: 95491, 95490, 95489, 95488, 95487, 95486, 95485, 95484, 95483, 95482,
95481, 95480, 95479, 95478, 95477, 95476, 95475, 95474, and 95473
TARs: 95659, 95217, 95211, 92382
Also solved in patch over NGEMS1.12
SOLVED in NGEMS1.14: 91575, 92154, 92157, 92224, 93586, 93342, 93723, 94143, 94144, 94145,
94146, 94263, 94230
SOLVED in NGEMS1.13: 93342, 93339, 94143, 94144, 94145, 94146
1.5. Software Release details
1. Included modules
# Name of the CI ID of the CI Size of Deliverable( in bytes)

describing type
1 NGEMS manager NGEMSL3_1_1.18_1-mgr.tar 48343040
2 Web manager NGEMSL3_1_1.18_1-WebMgr.tar 23429120
3 Front page NGEMSL3_1_1.18_1_FrontPage.tar 15441920
4 Map User Admin NGEMSL3_1_1.18_1- 9984000

MapUserAdminUI.tar
5 Map Back End NGEMSL3_1_1.18_1-ngemsMapBE.tar 593920
6 Access Gateway NGEMSL3_1_1.18_1- 25702400

Mgr AccessGatewayMgr.tar
7 NGEMS Installer NGEMSL3_1_1.18_1-ngems- 215040
Installer.tar
8 ENV deliverable Environment deliverable is provided in 927662080
NGEMS1.8 release. Pls use the same. It (modified on 7th Feb 2018)
is not repeated in new releases. Changes related to audio alarms
for Thin Client
1.6. Other Dependency
This release is a part of XEYEPL2.13 release and has dependency on:
SG release SGL1_3_1.9_1
CoreAgents COREAGENTSL3_1_1.2_2 + patch release (SG agent, NGEMS agent, IEMS agent, SP
agent)
Gateway agents GWYAGENTL3_1_1.6_1 + patch release
Pls note: RE agent deliverable of (COREAGENTSL3_1_1.2_2 release) to be installed only if compatible

RE device release PATCH2-Over-REL1_1_1.25_1-ISD
C5 device release SS-VL1_1_1.39_1 are installed
1.7. Pre-Installation procedure

Environment installation and Mysql DB replication steps, for duplex setup need to be done (before
release installation) on the blades.
untar ngems3_1_1.18_1-mgr.tar to view NGEMS-HELP directory .

Refer to CDOT-NGEMS-ENVIRONMENT-INSTALL.doc and CDOT-NGEMS-DBREPLICATION-
FAILOVER.doc
1.8. Installation procedure
Pre-requisites:
Following to be checked at mysql:
1. select user,host from mysql.user where user='root'
2. check if an entry for user='root'& host =% exists, if not, create user 'root' and
grant privileges as below
mysql> select host,user from mysql.user where user='root';
+-----------+------+
| host | user |
+-----------+------+
| 127.0.0.1 | root |
| ::1 | root |
| localhost | root |
| test3 | root |
+-----------+------+
4 rows in set (0.00 sec)

mysql> create user 'root'@'%' identified by '';
Query OK, 0 rows affected (0.00 sec)
mysql> grant all privileges on *.* to 'root'@'%';
Query OK, 0 rows affected (0.00 sec)
mysql> select host,user from mysql.user where user='root';
+-----------+------+
| host | user |
+-----------+------+
|% | root |
| 127.0.0.1 | root |
| ::1 | root |
| localhost | root |
| test3 | root |
+-----------+------+
5 rows in set (0.00 sec)
Steps for running installer module
1. untar the release namely <relid>-ngems-Installer.tar by

tar -xvf <relid>-ngems-Installer.tar
A folder with name <relid>-ngems will be created in the same directory.
2. Get into the directory
cd <relid>-ngems
3. Important: Run following commands at the prompt
$ type java
java is hashed (/usr/bin/java)
For exporting JDK_HOME, use jdk1.6.0_12 (as provided in the ENVIRONMENT_NGEMS3)
(example)
$ export JDK_HOME=/opt/jdk1.6.0_12
$ export PATH=$JDK_HOME/bin:$PATH
$ type java
/opt/jdk1.6.0_12/bin/java
Now, this is the correct path
4.run ./setEnv.sh
It will ask for JAVA_HOME:enter the JAVA_HOME of the current machine
It will ask to change webnms home: the default WebNMS home

is:/opt/ngems/Adventnet/WebNMS, press 'n' if you donot wish to change it
It will ask to change apache home: the default WebNMS home

is:/opt/ngems/WebServer/apache, press 'n' if you do not wish to change it
5. run ./runInst.sh
It will ask for JAVA_HOME, enter JAVA_HOME
and if everything works fine, then the Installation GUI gets working.
In the input form, select ‘reinitialize the DB’ option as Database Schema related changes have been
provided in this release.
Use following login/passwd to login to NGEMS manager after successful installation:
User: super
passwd: Admin123
1.9. Notes
For NGEMS release related documentation and configuration procedures and other help documents,
untar ngems3_1_1.18_1-mgr.tar to view NGEMS-HELP directory.
1.10. Annexure –A
Following were offered in XEyeP2.12
(Following were also part of NGEMSL3_1_1.12_1 + PATCH14-Over-NGEMSL3_1_1.12_1-

Manager_Module_Changes)
Patch14 changes (this is not an integrated patch and has to be installed
only upon patch3 + patch7+patch8+patch9+patch10+
patch11+patch12+patch13)
Changes:
 EBM card alarms postdated time solution.
 Infrastructure alarms, region code related changes.
 Input fields for LIS SS7 card not required in add LIS node form.


only upon patch3 + patch7+patch8+patch9+patch10+patch11+patch12)
Changes:
 Solution for HP Chassis Eth Port alarms in case of aggregation.


only upon patch3 + patch7+patch8+patch9+patch10+patch11)
Changes:
 Solution to add LIS module in core chassis.
 A Utility AddSwitch.sh is provided to add corechassis switch ips on NGEMS server DB
in case they were not configured at the time of corechassis discovery. This utility is
installed in /opt/ngems/AdventNet/WebNMS/bin/ path. Execute this utility and give the
parameters as chassis ip and switch ip.

only upon patch3 + patch7+patch8+patch9+patch10)
Changes:
 Solution to reset password for user super. A utility
/opt/ngems/AdventNet/WebNMS/bin/UnlockSuperUser.sh is provided for this.
 Solutions for NOC(Core Module versus Slot Report,NGEMS FrontPage,SG and LMG
commands)
 Change to support v5ag commands for increased AI range (from 25 to 150) and
minimum L3 address value (0)
(Following were offered in NGEMSL3_1_1.16_1)
1. Refresh SG node,
2. Delete interface before add node ( for add chassis and add core module )
3. SG module chassis not to be opened if SG is down
4. Modifying severity to 6 for IL-Interface down ALARM added
5. Webmgr Process Error CDR at Rating Engine
6. MLS, Aggregator Port ID issue for Layer 3 switch, V5AG discovery Events handling
7. HW details updation for cacu and node IP added for power and fan alarms
8. Fault Optimization for repeated and toggling events,
9. Manage/Unmanage PR/GR sites on PR/GR switchover
10. C4 configuration commands modifications (also mentioned in solved TARs)
11. Transaction logging to happen even if there is no self IP entry in /etc/hosts client machine
12. HELP docs for client, Region codes, GR guide, User guide updated
13. XML session related bug
14. LAGEMS hostname is used instead of Physical IP for opening LAGEMS client from LAG node.
15. All field patches as mentioned below.

only upon patch3 + patch7+patch8+patch9)
Changes:
 Solution for corruption of Session between Manger and Agent.
Patch9 changes (this is not an integrated patch and has to be installed only
upon patch3 + patch7+patch8)

1. Port id -1 in SG refresh sometime and controller card status updated on SG refresh
2. MO null exception in Fault optimization
3. RepeatedTogggling Process to wait for upDateProperties on Switchover
gateway Alarm source null in one of TRAP of SGL2

Manager_SwitchOver_Changes)
Patch8 changes (this is not an integrated patch and has to be installed only
upon patch3 + patch7)

1. Polling of Core Modules and Chassis ischeduled in separate threads.
2. Utility to shutdown ngems server is being provided. Utility is shutngems.sh in path
/opt/ngems/AdventNet/WebNMS/bin/
3. View Module Status strategy changed.
4. Default ngems server down message reverted.
5. NGEMS Switchover provided.
6. GR to PR restoration procedure MAXNG-NGEMS-GR-PR.doc document updated.
A Utility agentAlmDbCleanup.sh is provided to be executed at PR NGEMS when shifting from GR to PR.

Procedure is provided in MAXNG-NGEMS-GR-PR.doc document.
Path of utility is /opt/ngems/AdventNet/WebNMS/bin

Patch7 changes (this is an integrated patch with patch4, patch5 and patch6
and to be installed directly after patch3 has been installed)

 Utility to delete Interface in case of Node already exists message
 SG Node Refresh Command
 Upon PR DNS Server down or NGEMS SERVER down, a message will be flashed on
NGEMS Client “IMPORTANT MESSAGE: NGEMS PR SITE IS NOT REACHABLE.
PLEASE RE-LOGIN”
 Sync status between PR and GR can be checked with utility SyncStatus.sh availabe at
/opt/ngems/AdventNet/WebNMS/bin path.
 GR to PR restoration procedure as mentioned in MAXNG-NGEMS-GR-PR.doc
document.
 Client messages at PR-GR setups modified
 Multiple core chassis alarms for multiple power supply, fan failure etc.
 HP Ethernet port alarms provided.
o (pre-requisite: HP chassis to have default user/password as cdot/cdot1234)
 View module status disabled if management agent down, as module status view may be
misleading.
 Status Polling and Restricting module status
on SG node Down
 CACU - inventory related and entity related changes
 Status Polling for SG Node
 Restricting Module status when SG node down
 Delete Non Node Interface Utility
 SG Junk Delete Utility
 SG Node Refresh
 Upon PR to DR switchover all core chassis located at PR Site will get unmanaged and
chassis view will not open.
 All Children of PR Site Chassis in the hierarchy will get unmanaged.
 All existing Alerts of above unmanaged Chassis and children nodes will get deleted
 Chassis not located at PR Site will get refreshed
 Upon DR to PR switchover all chassis located at PR Site and children will get managed
and refreshed.
 Fault Optimization module suppresses Repeated and Toggling (only non-Topology)
Alarms
 It also generates a 'TOGGLING' alarm for toggled entities.
 After an entity stops toggling, its status will be refreshed and its 'TOGGLING' alarm
will be cleared.
 Patch Release Name is written in
/opt/ngems/AdventNet/WebNMS/conf/ReleaseName.conf file
 Proper Cacu Chassis hardware details updation like MAC address, Serial no, Modelno.
 Node Ip appended in Cacu Fan and Power alarms entity
 Node Ip and alarm source appended for V5ag,Priag,TMG alarms entity
 Proper status for MLS Ports in cacu chassis
 Fault Optimization: If same Event is received with different text or same text but after 30
min, it will NOT be suppressed by event filter.
 While PR-GR switch-over if any exception (Transaction/timout/rollback/due to lock)
occurs in getting MO or in updating 'managed', process will retry until all MOs are
fetched/updated successfully or retry-count exceeds
 Aggregator Port Alarms issue resolved
 Proper Mac id displayed for Aggregator
 JMX Agent related changes: Module delete information to be propagated to NOC.
(Following were also part of NGEMSL3_1_1.12_1 + PATCH6-Over-NGEMSL3_1_1.12_1-PR-

GR_UNMANAGE_ALERT-DEL)
Patch6 changes (this is not an integrated patch, to be installed only after patch5 has been
installed)

 Upon PR to DR switchover all chassis located at PR Site will get unmanaged
and chassis view will not open.
 All Children of PR Site Chassis in the hierarchy will get unmanaged.
 All existing Alerts of above unmanaged Chassis and children nodes will get
deleted
 Chassis not located at PR Site will get refreshed
 Upon DR to PR switchover all chassis located at PR Site and children will get
managed and refreshed.
(Following were also part of NGEMSL3_1_1.12_1 + PATCH5-Over-NGEMSL3_1_1.12_1-PR-GR_SG-

IFDEL-UNMANAGE)
installed)

1. Utility to delete Interface in case of Node already exists message
2. SG Node Refresh Command
3. Upon PR DNS Server down, a message will be flashed on NGEMS Client
“IMPORTANT MESSAGE: NGEMS PR SITE IS NOT REACHABLE. PLEASE
RE-LOGIN”
4. Upon PR to DR switchover all chassis located at PR Site will get unmanaged and
chassis view will not open.
5. Sync status between PR and GR can be checked with utility SyncStatus.sh
available at /opt/ngems/AdventNet/WebNMS/bin path.
6. GR to PR restoration procedure as mentioned in MAXNG-NGEMS-GR-PR.doc
document.
(Following were also part of NGEMSL3_1_1.12_1 + PATCH4-Over-NGEMSL3_1_1.12_1-PR-

GR_HPethalms_Viewchassis_SG)
installed)

 Client messages at PR-GR setups modified
 Multiple core chassis alarms for multiple power supply, fan failure etc.
 HP Ethernet port alarms provided.
(pre-requisite: HP chassis to have default user/password as cdot/cdot1234)
 View module status disabled if management agent down, as module status view may be
misleading.
 Status Polling and Restricting module status

on SG node Down
 CACU - inventory related and entity related changes
 Important: All core modules need to be rediscovered after installing this patch

JMXAGENT_SBCCommands_LMGChassisReport_C4DNC)
Patch3 changes (also includes earlier patch1, patch2 )
1. C4 DNC commands
2. SBC command changes (XML agent) - correct values displayed in modify commands.
(Following are offered in NGEMSL3_1_1.15_1)
1. Support for SNGL (compatible with COREAGENTSL3_1_1.1_2 and SG release SGL1_3_1.9_1 in

XeyeP2.13)
2. TMG enhancements for optimization of discovery and status polling
3. Core module SNMPv2 interface deletion in case of unsuccessful discovery
4. Bugfix for SBC pending alarm.
5. Frontpage LAGEMS port corrected to 9090 in file urls.xml
6. Region check in discovery of standalone TMG node, if user region does not match with device region,
discovery will fail.
7. Status icon changed for cdot tmg, cdot aggr
(Following were also part of NGEMSL3_1_1.14_1)
1. LMG polling message modified (PATCH4-Over-CLMGLL1_1_1.14_1-status_cmd) patch

required from device team for the same).
2. Node addition to be failed if:
a) Node name contains special characters.
b) Node region ends with "_" character
3. Help documents enhanced for help in node name, dns entries, region codes
4. SBC modify commands – modification of specific field allowed now
5. IR alarm handling shifted to a separate thread
6. Delete Chassis double confirmation related
7. C5V2 added in map criteria in service provisioning (for C5 SNMP nodes)
8. Logged in applet client users information in “root” login
9. SG status poll and rediscovery optimization
10. Standalone cards (aggregator, TMG, SNGL) status poll optimization and other bug fixes
11. CACU enhancements and optimization
12. Optimizaton in Event reports- Event logs region bug/ duplicate entries for some chassis bug resolved
13. RE WebManager: Zone related changes

 Support of C5,SBC and MS in SNMP-V2
 C4 DNC commands
 Alarm to be generated for change in region code and display name (generic).
 Prevent addition of LMG chassis through shelf manager Physical IP
 If LMG card is jacked-out and then, jacked-in in different slot, it should show proper status in the
chassis
 LMG polling changed to XML/SNMP polling instead of ping and polling interval increased to 5
mins.
 Snmp Ping used instead of ping in AMM Status Polling(Core Chassis), Polling interval for CORE
SNMP nodes changed to 5 mins, polling schedule for IEMS/SP changed to 5 mins
 Status poll time for NGTJ/EBM/MLS card has been increased to 2 minutes from 1 minute
and for SHM card 2 mins. to 3 mins
 Status polling of each module handled in separate thread.
 Alarm propagation in LAG chassis corrected to set color of node based on LAG alarms severity.
 Default BE alarms and not-required processes removed from ems for performance optimization
 Solution for tar 93342, 93339 ( Prompt before PRI restart command , change in V5 Command
response message)
 Warning notification generated if region modification is observed during rediscovery of CACU
chassis and clearing of notification if region at CACU chassis is as same as at EMS
 status polling of SLM card in separate thread ( for improve performance)
 Prompt before submission of Reboot NGTJ reboot, Refresh NGTJ/EBM/MLS card ( so that
command is not submitted just on click of menu)
 handling of CACU cards (NGTJ/EBM/MLS) with same IP to be moved to other similar SLOT in
chassis
 SG EMS enhancements for optimization
 SG DATA refresh command to refresh SG layer data on EMS from device if some in-consistency
is observed at EMS w.r.t device
 SG dependent data fetching from device moved in separate thread from discovery so that
discovery thread will not lead to hang in NGEMS server if some getBulk API is hanged during
data fetch from device
 Status polling of SG node at interval of 3 min, if SG AGENT is down, node will be marked down
and on starting SG Agent, down event will be clear and SG rediscovery will be called to refresh
status of controller cards
 On stack delete, dependent line cards, port type of SGL2 in CACU EMS and SGTK-SGL2 will be
marked un-Equipped and all layer data of SG at EMS will be deleted.
 SG discovery code optimization
 SG discovery to be stopped if SG node is discovered with physical IPaddress
(Following were also part of NGEMSL3_1_1.12_1 +patch2)

Patch1 changes (also includes earlier jmxagent patch):
 Change in jmxagent for correct source to be sent for CACU/C4 Traps to NOC
 SBC Configuration commands enhancements for XML agent
 SGL2/TMG discovery issue
 LMG GUI line card status at chassis level report with hyperlinks
 Last count clear alarm change for IEMS/NGEMS blades
 NGEMS Core module menu correction
 Preventing shutdown of NGEMS server when Mysql DB is down for less than 100 secs
Installer Module Changes:

 Installer changes for JAVA_HOME variable setting
 Installer changes regarding Modification in Subscription Management IP
MapUserAdminUI module changes:

 ProgressImage in Map creation using MapuserAdminUI module
 Adventnet server running check changed
 Code optimization in event reports
FrontPage Changes:
 LAG EMS port corrected to 9090
(Following were also part of NGEMSL3_1_1.12_1 +jmxagent patch)

 Change in jmxagent for correct source to be sent for CACU/C4 Traps to NOC
1. LMG chassis wise subscriber report

2. SG-TMG port equip/Unequip issue
3. Proper Error message for create pddi failure
4. TARs list in Sec 1.4
(Following were also part of NGEMSL3_1_1.11_1 +patch1)

 Manager enhancements for MS,SP and add core module form modification
 SBC (display sig, display media commands removed)
 Cacu Fault category for all discovery, status poll events
 LMG chassis fan/ powers supply IP address removed from 0.0.0.0
 Node wise Events menu label changed to important notifications
MapUserAdmin Changes:
 Event reports / Reachability reports bugs and enhancements
WebMgr changes:
Web Mgr Charge Band Association, Role Name changes
1. Discovery: Status Polling to be enabled only after adding complete Node and its children.
2. Name of LAG MO changed to its hostname
3. LMG Polling bug resolved
4. Category of LMG discovery alarms set as Fault
5. JMX Agent: Log deletion activity made offline
6. Code optimization(multiple updates)
7. Extra code deletion
8. chassis region kept in memory hash table.
9. Node status Polling strategy changed, AlertApi used
10. Map Filter strategy changed
11. persist_data_in_XML flag sat as false in NmsProcessesBE.conf
12. IR alarms implementation
13. Media server ems
14. Area user is created with Admin privileges. User is able to delete Core node from the
map.
15. SG discovery issue – stop/start. Multiple issues reported from validation.
(Integration testing of SG/TMG)
16. Too many connections review and changes (V5/PRI)
17. MAP criteria for CORE nodes – include aggregator, sgcard and stbr
18. SP related changes in manager
19. Core module event down on down on status polling
20. C4 GUI bugs
21. SSP command enhancements
22. Load testing observation related optimizations
23. User admin related tars (role name in rater GUI 91979)
24. MapUserAdminUI : While map creation PR & DR Site name drop down to be shown in case maps
already exists in the database
25. Status polling in separate thread to resolve user transaction timeout issue
26. Card Ip is added in entity and in event text for ngtj Ethernet proc alert

 Support of EMS for SNGL card (TMG, SGL2)
 Support of Pri D-Channel status command in PRI EMS
 CACU optimization
 GR related helpdoc added, client related helpdoc enhanced w.r.t PCRJ in NGEMS HELP
 Mysql connection related bug in reachability reports
 User Admin Password Reset tar -91979
 SG tars – 92580
 Rating Engine WebMgr Tar – 93230,93231
 Access MAP disabled bug
 Event report/ Reachability report: Chassis types SNGLchassis, cdotTMGType2, cdotAggr,
TPM1100 added in drop down lists for filtering events, source IPs for those Managed objects
which were not relevant are changed to not applicable.
 Code optimization: Cleanup of is-sdcn flag related code, connection pool reduced to 80 from
150.
Also provided in NGEMSL3_1_1.9_1 + Patch2:

 C4 Tars related to AddM3UAPSP , AddM3UAPS and others solved
Dynamic generation of emsresourcexml.jar
 NGEMS switchover option through GUI
 CACU Fault optimization and optimization enhancements
 SG TARS 92580 & 91622
Installer Module Changes:

 Bug related to VIP not properly getting written solved
 Linux Version upgraded to 6.7 in minimum system requirements
 MapUserAdmin IP passed directly
 RE installation Option removed from Installer
MapBE changes:
 MapBE optimization enhancements - map not to be created if already created
WebMgr changes:
 WebMGR security user to be created manually
Also provided in NGEMSL3_1_1.9_1 + Patch1:

Manager Module Changes

 installManagerRelease.sh changed to take care of various OS versions
 installation environment procedure to copy blank EMSWebServer.conf
Enhancement:
1. Compiled on RHEL6.7
2. CACU enhancements optimized status polling and bug fixing for reported issues
3. Fault optimization
5. MAP UserAdmin DB issue for large names (DB to be re-initialized while release installation)
6. INSSP command enhancements (treatment commands, treatment table commands, charge band
number commands, charge band periodicity commands, tariff class commands)
7. Core/site name changes (as per feedback from field) in NGEMS Installer module
(Important note: One need not give "_" underscore character in cityname/state
name/zonename/node name as Underscore char is used as separator internally in map code
and Command code in NGEMS, So it is mandate instruction to be followed by
validation/fieldSupport/internal testing while giving names to cityname/state
name/zonename/node.)
1. CACU EMS - new requirement related to Fuse Status and MLS connectivity , New Alarm
introduced for FUSE status of SLM card
2. Refresh command introduced in CACU EMS for Cards to resolve inconsistency.
3. C4 new command sets – ORNP, ORNP-SEN, BWLIST
4. C4, SSP command related TARs. (Detailed TAR list in Section 1.4)
5. Event and Reachability reports bugfixing
6. Output of Transaction Logs improved and made more readable to user
7. Problem faced in installation of MapUserAdminUI on RHEL 6.7 and MapBE module resolved
Resolved following issues at Manager –
7. Resolved SG Standalone discovery on SGTK card

8. TMG port channel status issue for SGTK card
9. PRI Port type not updated on UnEquip Port
10. jmxagent changes to send snmp notifications to NMS using virtual IP (to be checked on
NMS/NOC)
11. Installation Environment change (a new PPM to be installed). CDOT-NGEMS-ENVIRONMENT-
INSTALL procedure doc is enhanced. Installation Environment to be downloaded from CRS.
12. Logging of Delete chassis also logged in transaction logs now.
13. Core chassis / module (status polling fail) alarms will be raised with critical (red) severity instead
of major (yellow) severity
Enhancements at Installer module–

1. NMS PR VIP and NMS DR VIP both will be asked during manager installation. Earlier only NMS
PR VIP was asked in input
WebManager module–
1. RE related TARs
1. RE Web Mgr Enhancement - Centrex display all, display/modify centrex charge band
2. Resolved following issues at Manager –
1) Gateway Agent commands stopped working after card reboot

2) TMG channel status command not working
3) SHM switchover handling for status notification without refresh
4) Events to be replaced with Imp Notification on node to display category = 'Fault' and
severity = 6
5) Add node issue is discovery
6) User admin changes are not reflected on release installation
7) In tool bar, Map and User Admin renamed as Map, UserAdmin and Reports
8) Abrupt shutdown of manager on closing terminal resolved using nohup
9) ngemsd scripts enhanced
10) Important notifications shall be available for the nodes for past 7 days.
11) Fault related document provided in HELP.
12) LMG chassis hang and chassis refresh multiple times resolved (TAR-92171)
13) LMG Shelf manager GUI password issue resolved. Procedure document is enhanced for the same
(TAR-90741)
14) LMG- Alarm Codes and severity modified as follows: (TAR-92167, 92170)
1. UNIT-HS of Card Jackout/JackIN
2. UNIT-POLL for card Polling
3. UNIT for Software status
Severity details now:

Critical for Jackout, polling failure and software down
15) V5AG Block/Unblock Subscriber issue [Block/Unblock value changed as per device team]
3. Enhancements at MapUserAdminUI –
1) Reachability Reports added
2) Event Reports enhanced with fields like chassis type
3) Delete User issue - after deleting user dependent user operations/region operations were
getting deleted because of which those regions were not visible in further Add user and
CACU security was not working
4. At FrontPage, Map and User Admin renamed as Map, UserAdmin and Reports
5. Bug fixing at Installer Module
(Following were also offered in NGEMSL3_1_1.5_1+patch1)

 jmxagent changes for bulk addition in NMS

 TMG channels status display
 Linkset and MTP attributes display issue from ACCESS
 Route and Timer profile not updated in Manager
 Event hang
 Gateway agent command stop working after card reboot
 LMG- portgroup command bugfixing (TAR- 92166)
 LMG- Alarm Codes and severity modified as follows: (TAR-92167, 92170)
1. UNIT-HS of Card Jackout/JackIN

2. UNIT-POLL for card Polling
3. UNIT for Software status
Severity details now:

Critical for Jackout
Major for Polling failure
Minor for Software down
Map User Admin Changes

 Bug fixing for Event Reports.
Installer Changes
 Bug fixing
 RE Web Manager to be installed on a different blade, hence option is disabled
in case of full installation.
(Following were also offered in NGEMSL3_1_1.5_1)

Map Module Changes
1. addition of TMG nodes in map criteria
2. Nodes shall also be visible in Core and Access Maps
3. Enhancement in NGEMS for support SGTK/PICSD2 TMG node addition and TMG
gateway command
4. Support of SGTK SGL2 Card
5. MLS jackout related problem
6. SG Equip/UnEquip Line Card, Equip/UnEquip Ports, Display All ports in a card.
7. Client hanging problem
8. If SLM card ping fails or SLM agent or SLM process gets killed, Then whenever it comes
up properly still its status is being shown down
9. If NGTJ/MLS/EBM card IP is valid then all sub element's status of card have to be shown
red by default if card is not pingable or agent is not running.
10. One MLS card is jacked out. Alarm comes and slot becomes red but after sometime the
slot becomes green automatically although the card is still in jack out condition.(Tar -91973)
11. standalone mls ems : discovery , status polling , faults and menus
12. First Login Password Change in NGEMS applet client.
13. LMG temperature threshold alarm related changes.

14. In MapUserAdminUI transaction logging Solution to Server IP being logged in place of
client IP
15. MAC Address Field Not shown.
16. First Login Password Change.
17. Resequence of fields of output of Display Transaction Log.
18. System logs only to root user.
19. AuditedObj & type field for useradmin set.
20. Event Report available
Installer Changes
21. Bug fixing, installation logs in a separate file
22. DB replication script and PR-DR Core site name input added
Web Manager Changes
23. RE Database Name Changed & Release Id related Changes
Help Document Changes

24. DB replication Procedure document enhanced
25. Document added for DNS Entries, Transaction Logs, MapUserAdmin and NGEMS User
guide
26. LMG prerequisite document changed w.r.t alert filter configuration
(Following were also offered in NGEMSL3_1_1.4_1+patch1)
Map Module Changes

1. addition of TMG nodes in map criteria
2. Nodes shall also be visible in Core and Access Maps
3. Enhancement in NGEMS for support SGTK/PICSD2 TMG node addition and TMG
gateway command
4. Support of SGTK SGL2 Card
5. MLS jackout related problem
6. SG Equip/UnEquip Line Card, Equip/UnEquip Ports, Display All ports in a card.

7. In MapUserAdminUI transaction logging Solution to Server IP being logged in place of
client IP
Installer Changes
8. Bug fixing, installation logs in a separate file
(Following were also offered in NGEMSL3_1_1.4_1)

1. Support for LMG controller card (LSC) backup and alarms
2. Service Provisioning blades discovery/ alarms support for duplex
3. Installer module introduced for NGEMS modules installation through GUI
4. Following Policy can be scheduled from EMS GUI for User super:
 EMS DB backup (backup shall be made at /opt/ngems/AdventNet/WebNMS/backup directory)

 Delete transaction logs (earlier than 3 months)
(Following were also offered in NGEMSL3_1_1.3_1 + Patch1)

5. TMG configuration command changes
6. TMG backup/restore
7. Security feature for Access Gateway commands
8. CardIP on CACU chassis tool-tip
9. Enhancement in Slot vs Device Core Module Report to incorporate Physical IP address
10. C4 Security feature offered for new users.
11. Manager Side support of Active Reboot for CORE nodes
12. Adding Region code for Node Polling Events.
13. Unmanaging the Node in case Agent Configuration is tempered
14. LMG: to show virtual IP in tool tip of LSC and Shelf Manager cards
15. LMG: LCC card is renamed as LSC(local switching card) in NGEMS
16. Manager Redundant configuration : Bug fixes (latest my.cnf to be taken from environment)
17. DB replication procedure doc enhanced
18. WebEMS DB replication provided (latest my.cnf to be taken from environment).
(Environment deliverable is provided with NGEMSL3_1_1.1_1)
19. LAG card inventory related information provided at NGEMS
Map Module Changes (also offered in NGEMSL3_1_1.3_1 + Patch1)

20. addition of custom view scope for event/alert to show user specific events/alerts
21. addition of Important info Events in fault management
User Admin Module Changes (also offered in NGEMSL3_1_1.3_1 + Patch1)

22. Dialog box which prompts updates the password while change password not shown
23. User login locked after 5 wrong attempts
24. Change Password Verification
25. On login Reason for failure shown whether due to wrong password, user not present etc
26. User Hierarchy changes to show same level users of view type to admin and self only to view type
operator.
27. User name and password cannot be the same
Status of pending Change Requests and Failures (offered in XEyeP2.12)
SOLVED in NGEMS1.12: 93396, 93232, 92545, 92547, 93336, 93340, 93334, 91724, 92545, 92544,
93498, 91591
As per design: 92381, 92525
Already solved: 93397, 93343, 93341, 93338, 93337, 93333, 93231, 93230, 93384, 93349, 91260, 91193,
91230, 91322, 91608, 92380, 92429
SOLVED in NGEMS1.11: 93348, 93349,91608,91724,91260
STATUS put to SOLVED (wrong observation): 93384

STATUS put to SOLVED (configuration issue): 93397
STATUS put to SOLVED, To be solved from device side: 93337, 93336
Solved in gwyagent release 1.4: 93338
SOLVED in NGEMS1.10: 93503, SG TARS 92580 & 91622

Other Tars - 92581, 93230, 91979
Tar to be solved from device end: 92581
Previous TARS already solved marked as SOLVED in SWIM interface: 90715, 91313, 91627, 92874,
93585, 93587, 93231
Previous Tars “AS PER DESIGN” marked as SOLVED in SWIM interface: 91322, 92231
SOLVED in NGEMS1.9: Tar: 91067, 92380, 92154, 92223, 91056, 91231, 91230, 91531, 92381, 92157,
92321, 92448, 92789, 92702
Tar solved with procedure error for jdk version - 91576
Not repeatable: 92319, 92320, 92854
SOLVED in NGEMS1.8:
Tar: 92013,92014,91778,91770,92527,92525,92523,92173,92172,92264
Tar: 91228, 91193,91231,91531,91596
C4 related TARs: 92641, 92642, 92643, 92644, 92645, 92646, 92647, 92648, 92649, 92650, 92651, 92652,
92653, 92655, 92656, 92657, 92662, 92665, 92666
C4 TARs: SOLVED (As per design) - 92654, 92658, 92659, 92664

C4 TARs: NOT REPEATABLE: 92660, 92661, 92663
SSP related TARs: 92790, 92791, 92792, 92793

Solved at device: 91230
SOLVED in NGEMS1.7: 92524, 90966, 91083, 92469, 91664

Tar solved from signaling team: 92581

Tar Solved from Gateway Agent -91296, 92261, 91294, 91598 (all related tar)
Tar solved from EBM - 92156, 92155
SOLVED in NGEMS1.6:
92166,92167,92431,92430,92377,92378,92379,92301,91238,92227,92228,92229,91061,92169,92170,
92322,92323,92171
Already fixed TARs: 91595, 91271, 91421, 92429
As Events have been removed from left tree and provided in event report: following TARs related to Events
are not relevant now and have been marked as solved: 91255, 91256, 91760,
Not repeatable: 91916, 91868, 92262, 91570, 91532, 91312, 91772, 92230
Tars to be solved from Signaling Team: 92225
Solved in 1.5+ patch1: 92227,92226,91628,91571,91983,91599,91532
[END OF DOCUMENT]

P58-Ngems-Not-Release Ngemsl3 1 1.18 1

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

P58-Ngems-Not-Release Ngemsl3 1 1.18 1

Caricato da

Copyright:

Formati disponibili

Note

Software Release Notice

Released on: 25-Apr-2018

Issued to: ___________________________

COPYRIGHT © 2013, C-DOT. All rights reserved.

with contributions from

Comments, suggestions and queries pertaining to this document should be addressed to

COPYRIGHT © 2015, C-DOT. All rights reserved.

1.1. Objective and background

Step 1: ShutDown NGEMS Active and standby servers both.

(Edit the entries of SERVER_HOST, masterSSIP, prSite, drSite and save)

Important: (Procedure to add C5/SBC SNMP node)

The client screenshots for the configuration steps are attached.

1. Right click on core HP chassis, to view core modules (screenshot attached)

3. Click on Criteria in the left panel, to open Map Criteria window

4. Add C5V2,SBCV2 (capital letters) in the type field (screenshot attached)

6. Repeat steps 1,2,3 to verify the changes done

(Following were also part of NGEMSL3_1_1.17_1+PATCH3-Over-NGEMSL3_1_1.17_1-

1. CACU chassis loading time improved by using MapChassis.

(Following were also part of NGEMSL3_1_1.17_1+PATCH2-Over-NGEMSL3_1_1.17_1-ILD_MISC

1. Changes related to thin client Audio

(Following were also part of NGEMSL3_1_1.17_1+PATCH1-Over-NGEMSL3_1_1.17_1-

(Following were also part of NGEMSL3_1_1.16_1 + PATCH2-Over-NGEMSL3_1_1.16_1-V5AG-AI-

Manager Module Changes:

1.3. Known exceptions in the Release

1.4. Status of pending Change Requests and Failures

96661: solved in 1.18

Following tars are marked SOLVED in SWIM -

1. CACU SLM tars to be solved at 95963, 95213,91692

2. V5,/PRI/SG device issues 95965, 95885,94230,96168,96658,96657

3. TAR Solved ( configuration issue) 95969,

4. Tars Solved ( already fixed) 95966,

5. tars not repeatable 96631,96632,96638,96659,

Also solved in patch over NGEMS1.12

SOLVED in NGEMS1.13: 93342, 93339, 94143, 94144, 94145, 94146

1.5. Software Release details

# Name of the CI ID of the CI Size of Deliverable( in bytes)

2 Web manager NGEMSL3_1_1.18_1-WebMgr.tar 23429120

3 Front page NGEMSL3_1_1.18_1_FrontPage.tar 15441920

4 Map User Admin NGEMSL3_1_1.18_1- 9984000

6 Access Gateway NGEMSL3_1_1.18_1- 25702400

This release is a part of XEYEPL2.13 release and has dependency on:

Pls note: RE agent deliverable of (COREAGENTSL3_1_1.2_2 release) to be installed only if compatible

1.7. Pre-Installation procedure

untar ngems3_1_1.18_1-mgr.tar to view NGEMS-HELP directory .

1.8. Installation procedure

Following to be checked at mysql:

1. select user,host from mysql.user where user='root'

mysql> select host,user from mysql.user where user='root';

4 rows in set (0.00 sec)

mysql> create user 'root'@'%' identified by '';

Query OK, 0 rows affected (0.00 sec)

mysql> grant all privileges on *.* to 'root'@'%';

Query OK, 0 rows affected (0.00 sec)

mysql> select host,user from mysql.user where user='root';

5 rows in set (0.00 sec)

Steps for running installer module

1. untar the release namely <relid>-ngems-Installer.tar by

3. Important: Run following commands at the prompt

For exporting JDK_HOME, use jdk1.6.0_12 (as provided in the ENVIRONMENT_NGEMS3)

Now, this is the correct path

It will ask to change webnms home: the default WebNMS home

It will ask to change apache home: the default WebNMS home

mysql> grant all privileges on . to 'root'@'%';