 |
| |
| |
SNMP I/O Solution |
|
| |
Moxa's ioLogik E2000, E4200, and W5300 series products are both industrial remote terminal units (RTU) and intelligent SNMP environmental monitoring devices, and they support all versions of SNMP protocols, including SNMP v1, v2c, and v3. To connect to the network management system (NMS), the ioLogik I/O is specifically designed for information field applications that use the SNMP protocol, such as IT server room monitoring, unmanned facility monitoring, and the integration of intrusion detection and device monitoring of a telecom base station. By working together with the built-in Click&Go™ control logic, you are able to get/set/walk to the remote I/O status, and create an SNMP trap to the NMS. Moreover, the SNMP trap can be user-defined, and interact with the local I/O controllers to provide system managers with a clear status report when there is an event. |
|
|
| |
|
|
| |
Fully Compatible with SNMPv1/v2c/v3 |
|
| |
The SNMP protocol is now used across a wide variety of platforms and network environments, and Moxa's environmental monitoring devices support all three SNMP versions—v1, v2c, and v3. SNMP is used as a unified protocol to monitor the status and operation of a diverse range of equipment. No matter which version of SNMP protocol is being used by your existing NMS, Moxa's environmental monitoring devices can be employed with ease. |
|
|
| |
| |
Secure Communication with SNMPv3 |
|
| |
SNMPv3 introduced an encryption technology that prevents system crashes. It is the most secure version of SNMP, with messages safeguarded by encryption to protect them from intercept traps. SNMPv3 encrypts messages using CBC-DES encryption, which belongs to the Universal Security Model (USM). |
|
|
| |
 |
| |
User-definable SNMP Trap also Includes I/O Status |
|
|
| |
Secure Communication with SNMPv3 |
|
| |
When a remote device records a local event, SNMP provides a trap message to notify the administrator at the central site. The event could be an alarm, a clear, or simply a status message. Working with the Click&Go local control logic, the ioLogik micro controllers deliver the SNMP traps when a pre-defined event occurs, or can be reported periodically by timer functions. |
|
| |
|
|
| |
SNMP Trap Can Bind I/O Status Information |
|
| |
A standard SNMP trap has seven trap numbers, and each trap number represents a special event and trap ID. An SNMP NMS does not keep a standing alarm list, so it can be difficult to tell what is happening on your network by looking at a list of traps. The ioLogik E2000 also supports Moxa's private SNMP trap format, which is called variable binding. For example, the SNMP information may show "Door Open." It provides users with greater flexibility when using alarms. The built-in intelligence I/O initiates an SNMP Trap activity in real time, and can be defined by user-defined events and messages. |
|
| |
|
|
| |
| User-definable SNMP Trap |
|
| When an event occurs at the site, the SNMP issues a trap message to notify the administrator at the central site. Moxa's microcontroller provides an advanced SNMP Trap that not only binds I/O status, date, time, and IP address, but also the user-defined message. The string-type message provides the best way to indicate the current situation instead of using trap ID. The network manager can then receive the message directly without converting the ID with a program. For example, the SNMP information may show "Intrusion Alert," plus date, time, and server name. |
|
|
| |
|
| |
Create and Maintain Systems with Ease |
|
| |
SNMP is easy to implement. After compiling a private MIB file in the NMS, each SNMP device can be read from or written to by the NMS. In addition, SNMP devices are almost plug and play. Moxa now provides a high quality, industrial design and full function support of SNMP solutions using the ioLogik environmental monitoring series. |
|
|
| |
| |
| |