net_connect alarm coming in as long hostname even with profile set as alarm source using short name

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We have configured ping profile to trigger alarm with profile name (short hostname), but in alarms we are getting domain name being add.

Environment

Release: 20.4
Component: nas

Cause

Nas had the system under name services set to long name and was locked.

Resolution

In nas > Names Services, verify that the host is not listed there as locked using the long name FQDN. If it is right click on the source, unlock and rename the name to the desired name.