User`s manual

RNAS-1200 Series Modify Network Settings
6-8
and controlling many elements of IP and IP routing.
icmp 1.3.6.1.2.1.5 The ICMP group monitors internal system reports of IP errors,
discards, and the like.
tcp 1.3.6.1.2.1.6 This group reports on TCP states, returning whether the interface is
closed, listening, synSent, and so forth.
udp
1.3.6.1.2.1.7
The UDP group returns statistics on UDP performance.
egp 1.3.6.1.2.1.8 The EGP group provides objects useful for EGP monitoring, like an EGP
neighbor table.
transmission 1.3.6.1.2.1.10 MIB-I lacked any way of distinguishing types of transmission media.
While the transmission group currently has no defined objects, this
subtree allows the creation of media-specific MIBs. When
Internet-standard definitions for managing transmission media are
defined, the transmission group is used to provide a prefix for the
names of those objects.
snmp 1.3.6.1.2.1.11 The SNMP group measures SNMP performance on the local device by
logging and calculating such things as the number of SNMP packets
sent and received.
For more information, visit http://www.ietf.org/rfc/rfc1213.txt, or refer to the O’Reilly book, Essential SNMP,
available for free viewing online.
Moxa’s SNMP Control Interface
The RNAS-1200 comes with a customized MIB file that provides a proprietary monitoring and control
environment. This custom software utilizes SNMP to provide a much more convenient means of remotely
controlling and monitoring a device. Using Moxa’s SNMP control interface, you may create custom automations
for most RNAS-1200 processes by calling SNMP objects in simple, standardized shell scripts.
Brief Introduction
Refer to the following base OIDs for the RNAS-1200 MIB subtree.
Moxa MODULE-IDENTITY ::= { enterprises 8691}
Linux OBJECT IDENTIFIER ::= { moxa 12 }
rnas1200 OBJECT IDENTIFIER ::= { Linux 1200 }
mxControlManager OBJECT IDENTIFIER ::= { rnas1200 1 }
rnas1200Setting OBJECT-TYPE ::= { mxControlManager 1 }
rnas1200Commit OBJECT-TYPE ::= { mxControlManager 2 }
rnas1200Query OBJECT-TYPE ::= { mxControlManager 3 }
Finally, keep in mind that for many NMS implementations, all OIDs must be appended with a final value
indicating whether it is a scalar value (0), or a columnar value (i.e., a simple table). While some NMS suites
do allow the final .0 to be dropped, it is good practice to include these values in your SNMP commands.
Currently, all of Moxa’s proprietary OIDs are scalar values, and so should be completed with a final zero (.0).
Below, a simple SNMP tree showing the relationships between the Moxa enterprise OIDs is provided.