NB 250 not reporting SNMP Trap to Data Center Expert

[DCIM_Support]

This question was originally posted on DCIM Support by Matthew Wren on 2017-10-10

---

Hi All,

We have an issue at the moment that the NB 250, will detect the change of state for dry contact either open/close events but this will not report the event occurring to our Data Center Expert server.  As this doesn't occur we do not receive critical alerts from UPS, or MOV when power issues occur.

DCE version 7.4.3 and Netbotz 250 version 6.4.6  SNMP Trap configuration is correct and working.

Earlier this year, support had issued a DDF file update to DCE to bring the Dry Contact inputs to DCE as it did not work directly.

Can anyone shed any light?

(CID:126161743)

[DCIM_Support]

This answer was originally posted on DCIM Support by Jezreel Muyargas on 2017-10-10

---

Hi Matthew,

I tested Netbotz250 dry contact state change and worked perfectly fine.

[DCE 7.4.3 - Netbotz 250(ddf v16)]

As we can see from the active alarm window, it's reporting similar status like what we have on Netbotz 250 web interface.

In addition, critical alerts from UPS or other devices would not originate from the Netbotz 250 device but from the devices themselves.

Kindly clarify what would you like to achieve with your setup and how were they configured so we could help you further with the configuration.

(CID:126161868)

[DCIM_Support]

This comment was originally posted on DCIM Support by Steven Marchetti on 2017-10-10

---

Matthew,

Please also make sure that priority scanning is enabled in DCE for that device. Once done, change the state and verify in DCE if the sensor has changed when you view sensors. If not, right click the device and request a device scan. Does the state show changed? Does the alarm appear in DCE?

Also, does DCE show alerts for this device in the alarm configuration tab?

Steve

(CID:126161999)

[DCIM_Support]

This answer was originally posted on DCIM Support by Jezreel Muyargas on 2017-10-11

---

Hi Matthew/Steve,

This issue has been resolved.

Issue is due to wrong settings of NTP server from Netbotz 250.

This has been changed and confirmed by Laurence.

Also, I gave procedure on how to set the date format to dd.mm.yyy as per requested.

Thank you for the incessant assistance Steve.

BFO Reference # 43004145.

(CID:126162344)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.