Cancelling stuck NCIR alarms

manually in NetAct
Data Center and Cloud Infrastructure

TS-NCIR-SW-0023
Issue 1.0
Approved on 2022-05-06

Platform Products
Nokia AirFrame Cloud Infrastructure (NCIR)

© 2022 Nokia. Nokia Condential Information

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

Nokia is committed to diversity and inclusion. We are continuously reviewing our customer
documentation and consulting with standards bodies to ensure that terminology is inclusive
and aligned with the industry. Our future customer documentation will be updated
accordingly.

This document includes Nokia proprietary and condential information, which may not be
distributed or disclosed to any third parties without the prior written consent of Nokia. This
document is intended for use by Nokia’s customers (“You”/”Your”) in connection with a
product purchased or licensed from any company within Nokia Group of Companies. Use this
document as agreed. You agree to notify Nokia of any errors you may nd in this document;
however, should you elect to use this document for any purpose(s) for which it is not
intended, You understand and warrant that any determinations You may make or actions
You may take will be based upon Your independent judgment and analysis of the content of
this document.

Nokia reserves the right to make changes to this document without notice. At all times, the
controlling version is the one available on Nokia’s site.

No part of this document may be modied.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT,
REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE
FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF
ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

Copyright and trademark: Nokia is a registered trademark of Nokia Corporation. Other

product names mentioned in this document may be trademarks of their respective owners.

© 2022 Nokia.

2 © 2022 Nokia. Nokia Confidential Information Issue 1.0

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

Table of Contents

1 Technical Note Information ......................................................................................................... 5

2 Summary of changes .................................................................................................................... 7

3 Contact ........................................................................................................................................... 8

4 Purpose .......................................................................................................................................... 9

5 Validity .......................................................................................................................................... 10
5.1 Impacted technology ...................................................................................................... 10
5.2 Impacted system and SW releases ............................................................................... 10
5.3 Impacted products .......................................................................................................... 11

6 Keywords ...................................................................................................................................... 12

7 Executive summary .................................................................................................................... 13

8 Detailed description ................................................................................................................... 14

9 Solution and correction instructions ....................................................................................... 15

9.1 Instructions for the correction ...................................................................................... 15
9.1.1 Cancelling active NCIR alarms in NetAct ........................................................... 15

Issue 1.0 . © 2022 Nokia. Nokia Confidential Information 3

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

List of Figures
Figure 1 Example of nokiacli alarm list active command usage ............................................ 15
Figure 2 NetAct Monitor alarm example ................................................................................... 17
Figure 3 Cancel all alarms option in NetAct Monitor .............................................................. 21
Figure 4 Example where no alarms are present ...................................................................... 21

4 © 2022 Nokia. Nokia Confidential Information Issue 1.0

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

1. Technical Note Information

Technical Support Note

TS-NCIR-SW-0023

Cancelling stuck NCIR alarms manually in NetAct

Data Center and Cloud Infrastructure

Platform Products

Nokia AirFrame Cloud Infrastructure (NCIR)

Approval date: 2022-05-06

This document contains following type of information

Informative

Preventive

Corrective X

Additional categorization

Urgent

Security

Release Upgrade

SW Update

Parametrization

Information is classified as

Internal

All Customers X

Issue 1.0 . © 2022 Nokia. Nokia Confidential Information 5

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

Information is classified as

Customer Specific

6 © 2022 Nokia. Nokia Confidential Information Issue 1.0

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

2. Summary of changes

Date Version Change

2022-05-06 1.0 Approved version

Issue 1.0 . © 2022 Nokia. Nokia Confidential Information 7

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

3. Contact
Contact your local Nokia support.

For additional information related to this Technical Support Note contact

anna.dworzynska@nokia.com.

8 © 2022 Nokia. Nokia Confidential Information Issue 1.0

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

4. Purpose
This document contains generic information about products. These can be instructions that
explain problem situations in the field, instructions on how to prevent or how to recover
from problem situations, announcements about changes or preliminary information as
requirements for new features or releases.

Issue 1.0 . © 2022 Nokia. Nokia Confidential Information 9

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

5. Validity

5.1 Impacted technology

Technology Impact

GSM/EDGE

WCDMA

Small Cells

Single RAN

Nokia Core

Nokia Public Sector

Data Center and Cloud Infrastructure X

5G

Wi-Fi

5.2 Impacted system and SW releases

Tip:

The presented validity information includes the currently active software. The section
is re-assessed prior to every new System Release availability.

System Release Product SW Release(s)

Nokia AirFrame Cloud Infrastructure (NCIR) NCI R19 SW: all product SW releases

10 © 2022 Nokia. Nokia Confidential Information Issue 1.0

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

5.3 Impacted products

Product

Nokia AirFrame Cloud Infrastructure (NCIR)

Issue 1.0 . © 2022 Nokia. Nokia Confidential Information 11

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

6. Keywords
Alarm | NCI R19 SW | NetAct | Joma

12 © 2022 Nokia. Nokia Confidential Information Issue 1.0

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

7. Executive summary
This document instructs on how to cancel stuck NCIR alarms in NetAct manually, when
NetAct shows active alarms that are no longer active in the NCIR instance.

Issue 1.0 . © 2022 Nokia. Nokia Confidential Information 13

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

8. Detailed description
Sometimes, after NCIR update, NCIR alarms might get stuck in NetAct, even though they are
no longer active in the NCIR instance. This document instructs on how to cancel stuck NCIR
alarms in NetAct manually.

14 © 2022 Nokia. Nokia Confidential Information Issue 1.0

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

9. Solution and correction instructions

9.1 Instructions for the correction

This procedure involves changing configuration file parameters and database content. You
need to have admin access rights to both NCIR and NetAct. There is a risk for severe syntax
errors. If in doubt, contact your local Nokia support. Follow the below procedure to cancel
active NCIR alarms in NetAct.

9.1.1 Cancelling active NCIR alarms in NetAct

Procedure
1 Check NCIR active alarm

Checking NCIR active alarms is done with entering nokiacli alarm list active or
nokiacli alarm list history command.
Example where the NCIR active alarms list is empty
Figure 1: Example of nokiacli alarm list active command usage

Example of nokiacli alarm list historycommand usage, where the NCIR

alarm history shows that in the past there were alarms:

[csadmin@controller-2 ~(admin)]$ nokiacli alarm list history

+--------------------------------------+----------+---------------------------

-----------+-------------------------+-------------------+----------+---------

---+-----------+---------------------------------------------+----------------

----------------------------------+

| UUID | Alarm-ID | Event-ID | Time | Domain | Severity | AlarmState | Ack-

State | Alarm-Origin | Message |

+--------------------------------------+----------+---------------------------

-----------+-------------------------+-------------------+----------+---------

Issue 1.0 . © 2022 Nokia. Nokia Confidential Information 15

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

---+-----------+---------------------------------------------+----------------

----------------------------------+

| d14f867b-daae-4cc7-a5aa-045a45a60be5 | 31006 | d05d951b-6300-4651-a384-

c15e057d6d5b | 2020-04-14 12:27:41.467 | high availability | critical |

cancelled

| unack | NODE-controller-1/SERVICE-ntpd | Service failure |

| e1971d18-5855-417a-bfcd-8bd750ee2cba | 31005 |

89772a27-762a-40b5-92b8-41569b8940a8 | 2020-04-14 12:27:41.454 | high

availability | major | cancelled

| unack | SG-ntpd | Service-group degraded |

| 715e7369-0836-4c46-a6bc-0020d1638b1c | 31003 | 0c6b9fe8-40ef-4d21-

b83c-483be1b02d38 | 2020-04-14 12:27:41.427 | high availability | major |

cancelled

| unack | NODE-controller-1 | Node degraded |

| cc132839-75b0-4b1e-aa5c-b72a7e16a638 | 31001 | 5dcfe087-1463-41a8-

ab2d-4287960aedf7 | 2020-04-14 12:27:41.390 | high availability | major |

cancelled

| unack | | Cluster degraded |

| d35738c9-7c85-4f80-a835-543c890b7306 | 31006 | d05d951b-6300-4651-a384-

c15e057d6d5b | 2020-04-14 12:27:41.357 | high availability | critical | active

| unack | NODE-controller-1/SERVICE-ntpd | Service failure |

| 44622fb5-b2f9-46a0-ab19-d910320a15be | 31005 |

89772a27-762a-40b5-92b8-41569b8940a8 | 2020-04-14 12:27:41.345 | high

availability | major | active

| unack | SG-ntpd | Service-group degraded |

| 548a756d-fffd-402f-940e-2cc19de12b30 | 31003 | 0c6b9fe8-40ef-4d21-

b83c-483be1b02d38 | 2020-04-14 12:27:41.331 | high availability | major |

active

| unack | NODE-controller-1 | Node degraded |

| 09fa4cd4-7b41-401d-b40c-84c6438f0359 | 31001 | 5dcfe087-1463-41a8-

ab2d-4287960aedf7 | 2020-04-14 12:27:41.313 | high availability | major |

active

| unack | | Cluster degraded |

….

2 Perform alarm upload in NetAct Monitor

16 © 2022 Nokia. Nokia Confidential Information Issue 1.0

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

Upload alarms from NCIR.

In NetAct Start Page, click Monitoring ► Monitor
In NetAct Monitor, open Object Explorer by selecting Tools ► Managed
Objects ► Object Explorer
Expected outcome: The Objects pane appears.
Right-click the NCIR-<instance ID> object and select Alarm Upload.
Expected outcome: The alarm upload process starts. When alarm upload process
ends, the alarms which were not available or visible before, are uploaded.
The NetAct Monitor shows 19 alarms visible
Figure 2: NetAct Monitor alarm example

3 Check the alarm table in NCIR

Check the alarm table by executing the command:

sudo mysql -u joma -p$(sudo grep -i DatabasePassword \

/opt/nokia/joma/extras/esymacstarter/esymac_config.txt|cut -d"=" -f2) \

joma -vvse "SELECT * FROM PERSISTENTQUEUE;

SELECT * FROM ALARMTABLE;"

In the following example the alarm table shows records visible.

Issue 1.0 . © 2022 Nokia. Nokia Confidential Information 17

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

$ sudo mysql -u joma -p$(sudo grep -i DatabasePassword

/opt/nokia/joma/extras/esymacstarter/esymac_config.txt|cut -d"=" -f2) joma -

vvse "SELECT * FROM PERSISTENTQUEUE; SELECT * FROM ALARMTABLE;"

--------------

SELECT * FROM PERSISTENTQUEUE

--------------

Empty set

--------------

SELECT * FROM ALARMTABLE

--------------

ENTRY_INDEX ESYMACCOMPONENTID NOIALARMEVENTTYPE NOIALARMPROBABLECAUSE

NOIALARMADDITIONALTEXT

NOIALARMPERCEIVEDSEVERITY NOIALARMTEXT NOIALARMACKUSERID NOIALARMSPECIFICPROBLEM

NOIALARMEVENTTIME

NOIALARMACKTIME NOIALARMSYSTEMDN NOIALARMACKSTATE NOIALARMID

NOIALARMNOTIFICATIONID INTERNALALARMID

ALARMINSERTIONTIME NOIALARMCOUNT

3828 esymacID01 5 522 A hardware sensor detected that the voltage deviation

passed the critical threshold in the

server\nwhere the alarm was originated. This requires immediate actions because

critical voltage deviation can cause\nhardware

damage. For further information please refer to BMC event log and hardware

troubleshooting guide.\nHardware sensor output is also

collected by performance metrics, therefore it is highly recommended to\ninspect

performance monitoring history when this alarm is

active. 1 Critical voltage 1050005 1638210890000 NULL NCIR-estcra091/NODE-

compute-35/SENSOR-PVCCIO_CPU1

2 3870 6 0ac85f57-03c4-40fe-9ac0-805592c00154 1638210890372 NULL

4407 esymacID01 2 346 Creating a VM instance was unsuccessful. For the VM

instance and Openstack exception

details please\nrefer to the supplementary information field of the

alarm.2Creating instance failed 1020006

1639045759000 NULL NCIR-estcra091/VM-EIPU-5 2 4449 1161 abf1bed7-

dffc-4602-97bf-2291d6cb7c58

1639045759953 NULL

2 rows in set

Bye

18 © 2022 Nokia. Nokia Confidential Information Issue 1.0

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

4 Change NetAct parameters in NetAct dmgr node.

Note:

Take care to avoid syntax errors

Change the following NetAct parameters in two files present in the following location:

/d/oss/global/var/NSN-
integrationmanager/integration_metadata_template/com.nokia.ncir

manualCancelForwardingSupported
patchLevel
timestamp

[system@srnclab12node18 com.nokia.ncir]$ vi com.nokia.ncir.fmb.tpl

<?xml version="1.0" encoding="UTF-8"?>

<com.nokia.oss.fm.fmbasic:FMBasicAdaptation xmi:version="2.0"

xmlns:xmi="http://www.omg.org/XMI"

xmlns:com.nokia.oss.fm.fmbasic="http:///com/nokia/oss/fm/fmb

asic.ecore" patchLevel="${patchLevel}">

<annotations>

<elements name="dnMappingStrategy" value="overlap"/>

<elements name="mediationId"

value="com.nsn.oss.mediation.south.ne3soapfm"/>

<type href="../core/core.common#//southMediationInterface"/>

</annotations>

<Adaptation href="com.nokia.ncir.common#/"/>

<supportedFeatures alarmSynchronizationSupported="true"

ackSynchronizationSupported="false"

cooperativeAcknowledgementSupported="false"

manualCancelForwardingSupported="true"/>

<agentData agentClass="NCIR" agentVersion="${version}"

adaptationID="com.nokia.ncir">

</agentData>

</com.nokia.oss.fm.fmbasic:FMBasicAdaptation>

[system@srnclab12node18 com.nokia.ncir]$ vi params.properties

patchLevel=19.001

timestamp=20200121T072103

Issue 1.0 . © 2022 Nokia. Nokia Confidential Information 19

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

5 Execute the ads_client.sh command in NetAct dmgr node.

To activate the basic network element release support metadata on NetAct using
Adaptation Deployment Suite (ADS), execute the following command in NetAct dmgr
node as system user

sh /opt/oss/NOKIA-integrationmanager/bin/ads_client.sh \

-nt NCIR -v 19.2

6 Check if manualCancelForwardingSupported in com.nokia.ncir.fmb is updated.

The configuration file can only be changed by the ads_client.sh command in step 5.

[system@srnclab12node18 content]$ more com.nokia.ncir.fmb

<?xml version="1.0" encoding="UTF-8"?>

<com.nokia.oss.fm.fmbasic:FMBasicAdaptation xmi:version="2.0"

xmlns:xmi="http://www.omg.org/XMI"

xmlns:com.nokia.oss.fm.fmbasic="http:///com/nokia/oss/fm/fmb

asic.ecore" patchLevel="19.001">

<annotations>

<elements name="dnMappingStrategy" value="overlap"/>

<elements name="mediationId" value="com.nsn.oss.mediation.south.ne3soapfm"/>

<type href="../core/core.common#//southMediationInterface"/>

</annotations>

<Adaptation href="com.nokia.ncir.common#/"/>

<supportedFeatures alarmSynchronizationSupported="true"

ackSynchronizationSupported="false" cooperativeAcknowledgementSupported="false"

manualCancelForwardingSupported="true"/>
<agentData agentClass="NCIR" agentVersion="19.2" adaptationID="com.nokia.ncir">

</agentData>

</com.nokia.oss.fm.fmbasic:FMBasicAdaptation>

7 Cancel all alarms

To cancell all alarms select Cancel All Alarms ► Cancel Alarms for Objects
And Its Subnetwork in NetAct Monitor.

20 © 2022 Nokia. Nokia Confidential Information Issue 1.0

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

Figure 3: Cancel all alarms option in NetAct Monitor

8 Upload alarms again and check that all old alarms are cleared

Upload alarms again and check that all old alarms are cleared

Figure 4: Example where no alarms are present

9 Check the NCIR alarm table content again

There should be no records in alarm table anymore.

Check the alarm table by executing the command:

Issue 1.0 . © 2022 Nokia. Nokia Confidential Information 21

Use subject to agreed restrictions on disclosure and use.

Cancelling stuck NCIR alarms manually in NetAct

sudo mysql -u joma -p$(sudo grep -i DatabasePassword \

/opt/nokia/joma/extras/esymacstarter/esymac_config.txt|cut -d"=" -f2) \

joma -vvse "SELECT * FROM PERSISTENTQUEUE;

SELECT * FROM ALARMTABLE;"

$ sudo mysql -u joma -p$(sudo grep -i DatabasePassword

/opt/nokia/joma/extras/esymacstarter/esymac_config.txt|cut -d"=" -f2) joma -vvse

"SELECT * FROM PERSISTENTQUEUE; SELECT * FROM ALARMTABLE;"

--------------

SELECT * FROM PERSISTENTQUEUE

--------------

Empty set

--------------

SELECT * FROM ALARMTABLE

--------------

Empty set

Bye

10 Check NCIR active alarms and alarm history

The NCIR active alarms and NetAct active alarms should now be the same.

nokiacli alarm list active

22 © 2022 Nokia. Nokia Confidential Information Issue 1.0

Use subject to agreed restrictions on disclosure and use.