CDM (MCS) alarm coming in as a different name than the robot that generated it

Products

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

Issue/Introduction

We are getting cdm alerts for some devices in an MCS Group where the name is different than the actual robot name and we are not sure why. This is resulting in additional devices being created in our spectrum alarm integration and causing issues.

Environment

• Release: 20.4
• cdm 6.81 (MCS), cdm-MC

Cause

- DNS alias

Resolution

1. Resolved the hostname using nslookup and discovered that those robots in the Group where cdm is showing the wrong Host Name, have a DNS Alias.

2. Workaround is to set the specific name (override) in the robot (robotname in the raw config),so that the Host Name and the Source are the same.

ALIAS records are used when you want the domain itself (not a subdomain) to “point” to a hostname. The ALIAS record is similar to a CNAME record, which is used to point subdomains to a hostname. The CNAME record only can be used for subdomains, so the ALIAS record fills this gap. Alias records make it possible to alias the root domain to another service and to use an alias system that can coexist with other data.