Important nas alarm became invisible
search cancel

Important nas alarm became invisible

book

Article ID: 264011

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)

Issue/Introduction

An important alarm came invisible and there was no notification for it in either UIM nor mail

This is the original info for same alarm from nas probe

It came with the sever name in the host name and the ip in the source

On the other hand this is the info for the same alarm which became invisible,

It became invisible because the host name changed to the ip address

We need to know how could this happened and we need a solution for this as the host name must contain the name of the machine not the ip to match our UIM rules to send alarms and be visible

 

Environment

Release : 20.4

nas :9.36

Resolution

Add a new key "skip_non_ip_ns_lookup" in NAS's setup section and set this value as "yes"

skip_non_ip_ns_lookup will avoid unnecessary lookup if NAS already has the hostname available. 

Check if correct hostname /ip present in NAS nameservices for this robot, so no nslookup is required or remove the incorrect entry if present 

After this acknowledge the old alarm and restart the target robot.

Additional Information

Alerts triggered with IP-address instead of hostname

 

IP Address instead of Hostname in IM alarms windows.