Hello - We are running SMARTS 9.4.1 and have configured Notif Editor to process a new trap but it is failing to publish the notification. Does anyone know exactly what the errors in the trap log are specifically pointing to? I have included a screenshot of the errors that occurred in the trap log.
Sean, I was able to resolve the issue by changing the ElementClassName field (picture attached) from "Host" to "LoadBalancer" and it resolved the issue. We are now publishing those traps that were failing.
Just for future reference and in the event others run into this problem down the road....can you provide some more insight on why having "Host" as the ElementClassName would cause this issue?
Does it have to do with already having the device discovered in AM-PM (IP) as a "Host"?
Thank you for contacting Dell EMC Community Support forums. We are researching your question and will provide an update later today or tomorrow morning.
Ok thank you. From what I have been able to research....it appears to be complaining about a duplicate class name in the repos file (*.rps) but I don't want to remove a class from this file without knowing why there would be duplicates or knowing how to determine which duplicate should be removed....that is....if my findings are accurate. Will wait to hear back on what you find.
No I am not. We don't have a large amount of traps coming through. Maybe 15-20 in a given day. All other traps come through just fine but for whatever reason this specific one complains about DUPLICATENAME and fails to create/publish the trap.
The error means the code was trying to create an instance of name “jaxdctloadbalancervl18a.csx.com” for class “Host”, and it failed because there already existed an instance with this name in the “Host" class.
When you changed the ElementClassName field in Notif to "LoadBalancer", you have changed the class name regarding "jaxdctloadbalancervl18a.csx.com" and since there is no other instance of "jaxdctloadbalancervl18a.csx.com" with "LoadBalancer" as the class, it doesn't error with Duplicate name. That is why changing the class name “fixed” the issue.
Jon131
7 Posts
5361
0
Posted January 24th, 2018 07:00
Just for future reference and in the event others run into this problem down the road....can you provide some more insight on why having "Host" as the ElementClassName would cause this issue?
Does it have to do with already having the device discovered in AM-PM (IP) as a "Host"?
Thanks,
Jonathan