New Ranks & Badges For The Community!
Notice something different? The ranks and associated badges have gone "Star Fleet". See what they all mean HERE
Highlighted
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class
320 views

Ping Availability ETI in node down events

Jump to solution

Hi All,

We have integrated OMW to OMi. A node down message coming from OMW has ETI "Ping Availability: Unavailable" automatically, which sets the status of "System Availability" KPI to critical. This is ok.

But when node up message comes (normal), it acknowledges the node down message, but it does not have any ETI. Thus the CI status (its KPI) remain to be critical even if the node has come up.

The question is how I can put ETI "Ping Availability: Available" in the normal message so the it sets the KPI as normal/green in OMi dahsboards.

 

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Micro Focus Expert
Micro Focus Expert

Hello,

This issue can be resolved by creating a new filter called "PingAvailabilityFilter" which is a copy of the "PingUnAvailabilityFilter". The new "PingAvailabilityFilter" should be configured for messages of severity "Normal" where the title contains the words "is now running” and then the "Ping Availability" indicator can be modifed to use the "PingUnAvailabilityFilter" and new "PingAvailabilityFilter".

This should resolve the problem you see.

Regards,

Colin

Micro Focus Support
If you find this or any post resolves your issue, please make sure to mark it as an "Accepted Solution".
If you liked the reply then please show this with KUDOs.

View solution in original post

0 Likes
4 Replies
Micro Focus Expert
Micro Focus Expert

Hello,

This issue can be resolved by creating a new filter called "PingAvailabilityFilter" which is a copy of the "PingUnAvailabilityFilter". The new "PingAvailabilityFilter" should be configured for messages of severity "Normal" where the title contains the words "is now running” and then the "Ping Availability" indicator can be modifed to use the "PingUnAvailabilityFilter" and new "PingAvailabilityFilter".

This should resolve the problem you see.

Regards,

Colin

Micro Focus Support
If you find this or any post resolves your issue, please make sure to mark it as an "Accepted Solution".
If you liked the reply then please show this with KUDOs.

View solution in original post

0 Likes
Highlighted
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

Hi Colin,

Thnks for your reply. To implement this, we need to have node-up normal messages fwd to OMi. But as they are directly going to ack msg browser in OMW, so they are not getting fwded to OMi. In OMi, the node-down message is just closed due to "message corelation".

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Hello,

Even though OMW receives the message in the acknowledged message browser, the message is still forwarded to OMi and if you look in the closed events (using the "Received" option in the Closed Event Browser Configuration UI) then you will see the "(MS733) OV Control Daemon on node "xxxx" is now running." event.

Regards,

Colin

Micro Focus Support
If you find this or any post resolves your issue, please make sure to mark it as an "Accepted Solution".
If you liked the reply then please show this with KUDOs.
Highlighted
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

Many Thanks Colin. Finally we are getting ETI PingAvailability:Available in node up events. That was really helpful.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.