EcoStruxure IT forum
Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-03-30 05:17 AM
Is MOXA ioLogik E2210 compatible with DCE 7.8.0 over SNMP v1 or over any protocol for that matter?
I'm not able to get the DCE to discover it on SNMP v1 or SNMP v3 but I can get it on ModBus TCP but with no relevant info just the staus of the link to MOXA.
Both DDF for SNMP and ModBus are uploaded on DCE.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-03-30 06:21 AM
Yes that device should be compatible with DCE using snmp or modbus. Regarding SNMP, are you able to do a device walk from DCE? You can run this from the DCE status webpage http://<dce_ip>/nbc/status/SnmpWalk
However since this is custom IO to snmp/modbus gateway, be aware that with snmp you'll get generic data back, eg DI1 off/on or DI1 and then the value instead of the actual sensor name. Looking at tha modbus ddf, it is set for function code 1, coils and registers 0-12, so if you have something different programmed on your Moxa then that would explain why it doesn't return any sensors.
If you would like a custom modbus ddf, it can be created using the Asset Definition service
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-03-30 06:33 AM
Also the last time I encountered a moxa 2510 back in 2019, the customer tried to use snmpv3 but was unable to due to a bug with the moxa device and how it implemented the snmpv3 protocol. It wasn't compliant with RFC3414, section 3.2(7)) and would go offline in DCE anytime it was rebooted since it wouldn't update EngineBoots argument of oid .1.3.6.1.2.1.1.4.
Moxa may have fixed this bug by now, but just wanted to make you aware of it incase you are trying to use snmpv3.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.