This question was originally posted on DCIM Support by Kaloyan Georgiev on 2018-06-28
The ticketing system of our customer is receiving traps from our NetBotz and DCE.
Recently they received two traps from the NetBotz:
126.96.36.199.4.1.55188.8.131.52.0.14 and 184.108.40.206.4.1.55220.127.116.11.0.114 which are not listed in the Netbotz410.mib which is the last one I found.
Can you help me finding a new MIB or explaining what these mean?
This answer was originally posted on DCIM Support by Steven Marchetti on 2018-06-28
The MIB on the newest firmware (4.1) has no definition for this (5518.104.22.168.0.14).
I can say that usually something like .14 and .114 will be the event itself and the clearing of that event.
NetBotz traps do come across with text as well as the OID. What were the text values that were sent with this trap? I can add a report on this issue but it would be easier if I could verify what this trap equates to so that I could provide my testing in this report.
If your system is stripping out the text, perhaps you could look on the appliance itself. At the time you see the trap was sent, what alarm(s) occurred on the appliance.
What NetBotz device sent the trap and what firmware is it running?
Just an FYI, the MIB is available on the NetBotz itself so the newest firmware will have the newest MIB (which should have the newest version number). It's available on the appiance at http://<NetBotz_IP>/netbotzv3.mib
This comment was originally posted on DCIM Support by Kaloyan Georgiev on 2018-07-10
I forwarded your answer to the customer. In the attached file log.txt there is the log they sent me.
Can you check if we can help?
This comment was originally posted on DCIM Support by VIktor on 2018-07-12
Can you please advise if there is any feedback regarding the comment above? In attached file you can find the warning that is sending this trap.
This comment was originally posted on DCIM Support by Steven Marchetti on 2018-07-16
Apologies for not getting back to you sooner as I was away.
What version of DCE are you running?
So in this case it appears to be a low load alarm, I can not say with any certainty that it is the only event that will initiate this specific trap. I am entering a report on this issue and the engineers will have to look at the issue and update the MIB in a future revision. I can not say when it may be actually addressed.
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!