AnsweredAssumed Answered

SNMPCOLLECTOR - publish alarms based on IP or Alias instead of SNMP sysname

Question asked by benzaam on Apr 18, 2016
Latest reply on Oct 14, 2016 by cotton_gin1

Hi everyone,

 

Currently, the SNMPCOLLECTOR Probe Configuration UI allows to generate profiles from the discovery server based on SysNames (SNMP).

The thing is that whenever Data or Alarms are published for one of those profiles, the source will always be the SysName.

 

Sometimes, you would want to generate those alarms using another source: custom name (like the alias in USM) or even the IP address of the device (then we could make use of the NAS naming resolution to resolve that IP back to a name that is in DNS).

 

I could find that article here :http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec000005241.aspx  explaining that such a functionality would come, but I am not aware if this is the case already.

 

I also tried to raw edit the snmpcollector probe, and to set the flag publishByHostname to False, then rediscovered the devices in snmpcollector Probe Configuration window, but the alarms are still generated with the SysName, and not the IP address.

 

Does anyone have the same issue? Or is that the way it's supposed to be?

Have you found a workaround to this? Changing the sysname on all devices to match the dns name is not an option... This would be way too much work.

 

Thanks,

Benjamin

Outcomes