Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Add a new idea Subscribe
Status Under review
Workspace IBM Cloud Pak for AIOps
Created by Guest
Created on Apr 8, 2024

RELATED IDEAS

New functionality in Tejas NMS for Event Loss occurred/cleared Notification

Dear team,

Section 2.2.3.3 of the attached document refers to Notification for "Event Loss occurred/cleared Notification"

Following is the description of functionality:

NMS will send the Event Loss occurred/cleared event in case of the following scenarios.

1. Add new EMS and Alarms are added/deleted in Alarm Table.

2. Add new MEs and Alarms are added/deleted in Alarm Table.

3. Force resync of EMS for Alarms.

4. Force resync of MEs for Alarms.

However the event loss occurred / cleared notifications shall be not be sent in case of add/delete of EMS/ME without alarm update. In such case the resync of alarms to be done after getting the object creation/deletion notification from inventory OSS.

 Event Loss occurred Notification

Once the event loss is detected in NMS the event loss occurred event shall be sent.

: NotificationConsumerHttp.wsdl

API:notify (Sends the notification Message of type ‘EventLossOccured’)

Parameter

Description

Example

Topic

The Topic on which the event loss occured.

Alarm

objectType

Type of object where EventLoss occured. Currently supported types are EMS , MANAGED_ELEMENT

EMS

MANAGED_ELEMENT

objectName

RDN List of Object name

<ns13:objectName>

                <ns5:rdn>

                    <ns5:type>MD</ns5:type>

                    <ns5:value>EMS-159</ns5:value>

                </ns5:rdn>

                <ns5:rdn>

                    <ns5:type>OS</ns5:type>

                    <ns5:value>EMS-159</ns5:value>

                </ns5:rdn>

            </ns13:objectName>

(Table 1.2 Event  Loss occured Event format)

Event Loss Cleared Notification

Once the event loss is detected in NMS the event loss occurred event shall be sent and the corresponding Event Loss cleared event shall be sent once all the Alarms are updated with the latest entries in NMS system. The OSS client should resync the alarms for retrieving the missing events once it received the Event Loss cleared event.

WSDL : NotificationConsumerHttp.wsdl

API:notify (Sends the notification Message of type ‘EventLossCleared’)

Parameter

Description

Example

Topic

The Topic on which the event loss occured.

Alarm

objectType

Type of object where EventLoss occured. Currently supported types are EMS , MANAGED_ELEMENT

EMS

MANAGED_ELEMENT

objectName

RDN List of Object name

<ns13:objectName>                <ns5:rdn>                       <ns5:type>MD</ns5:type>

<ns5:value>EMS-159</ns5:value>

 </ns5:rdn>

<ns5:rdn>

 <ns5:type>OS</ns5:type>

      <ns5:value>EMS-159</ns5:value>

 </ns5:rdn>

            </ns13:objectName>

Solution Document of Tejas is attached for the same.

SolutionDoc_FMA...
SolutionDoc_FMAndPMDataRetrieval-V1 1.doc
Open full size
SolutionDoc_FMAndPMDataRetrieval-V1 1.doc
Idea priority Urgent

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.