MGate 5103 Series User Manual

Version 1.1, September 2023

www.moxa.com/products

© 2023 Moxa Inc. All rights reserved.

 MGate 5103 Series User Manual
The software described in this manual is furnished under a license agreement and may be used only in accordance
with the terms of that agreement.

Copyright Notice
© 2023 Moxa Inc. All rights reserved.

Trademarks
The MOXA logo is a registered trademark of Moxa Inc.
All other trademarks or registered marks in this manual belong to their respective manufacturers.

Disclaimer
• Information in this document is subject to change without notice and does not represent a commitment
on the part of Moxa.
• Moxa provides this document as is, without warranty of any kind, either expressed or implied, including,
but not limited to, its particular purpose. Moxa reserves the right to make improvements and/or
changes to this manual, or to the products and/or the programs described in this manual, at any time.
• Information provided in this manual is intended to be accurate and reliable. However, Moxa assumes no
responsibility for its use, or for any infringements on the rights of third parties that may result from its
use.
• This product might include unintentional technical or typographical errors. Changes are periodically
made to the information herein to correct such errors, and these changes are incorporated into new
editions of the publication.

Technical Support Contact Information

www.moxa.com/support
 Table of Contents
1. Introduction ......................................................................................................................................... 5
Overview .............................................................................................................................................. 5
Package Checklist .................................................................................................................................. 5
Product Features ................................................................................................................................... 6
2. Hardware .............................................................................................................................................. 7
Power Input and Relay Output Pinouts...................................................................................................... 7
LED Indicators ....................................................................................................................................... 7
Dimensions ........................................................................................................................................... 8
Pin Assignments .................................................................................................................................... 8
Mounting the Unit .................................................................................................................................. 9
Specifications ........................................................................................................................................ 9
Reset Button ......................................................................................................................................... 9
Pull-Up, Pull-Down, and Terminator for RS-485 ....................................................................................... 10
MicroSD.............................................................................................................................................. 10
3. Getting Started ................................................................................................................................... 12
Connecting the Power .......................................................................................................................... 12
Connecting Serial Devices ..................................................................................................................... 12
Connecting to a Network ...................................................................................................................... 12
Installing DSU Software ........................................................................................................................ 13
Logging in to the Web Console .............................................................................................................. 14
Quick Setup ........................................................................................................................................ 14
Quick Setup—System Setting......................................................................................................... 15
Quick Setup—Select Protocol ......................................................................................................... 15
Quick Setup—Role 1 and Role 2 of MGate 5103 ................................................................................ 15
Quick Setup—Finish ...................................................................................................................... 17
4. Web Console Configuration and Troubleshooting ...............................................................................18
Overview ............................................................................................................................................ 18
Basic Settings ..................................................................................................................................... 18
Network Settings ................................................................................................................................. 19
Serial Settings ..................................................................................................................................... 20
Protocol Settings (Agent Mode) ............................................................................................................. 20
Protocol Settings—Protocol Conversion ........................................................................................... 21
Protocol Settings—Modbus TCP Client (Master) Settings .................................................................... 22
Protocol Settings—Modbus RTU/ASCII Master Settings ...................................................................... 25
Protocol Settings—Modbus TCP Server (Slave) Settings .................................................................... 27
Protocol Settings—Modbus RTU/ASCII Slave Settings........................................................................ 27
Protocol Settings—PROFINET IO Device Settings .............................................................................. 28
Protocol Settings—EtherNet/IP Adapter Settings .............................................................................. 29
Protocol Settings—I/O Data Mapping .............................................................................................. 29
System Management............................................................................................................................ 31
System Management—Accessible IP List.......................................................................................... 31
System Management—DoS Defense ............................................................................................... 32
System Management—System Log Settings ..................................................................................... 32
System Management—Auto Warning Settings .................................................................................. 33
System Management—Email Alert .................................................................................................. 34
System Management—SNMP Trap .................................................................................................. 34
System Management—SNMP Agent ................................................................................................ 35
System Management—LLDP Settings .............................................................................................. 36
System Management—Certificate ................................................................................................... 36
System Management—Misc. Settings .............................................................................................. 37
System Management—Maintenance ................................................................................................ 39
System Monitoring (Troubleshooting) ..................................................................................................... 41
System Monitoring—System Status ................................................................................................ 41
System Monitoring—Protocol Status................................................................................................ 43
Status Monitoring ................................................................................................................................ 46
5. Configuration (Text Mode Console) .................................................................................................... 48
6. Network Management Tool (MXstudio)............................................................................................... 49
A. SNMP Agents with MIB II and RS-232-Like Groups ............................................................................50
RFC1213 MIB-II Supported SNMP Variables ............................................................................................ 50
RFC1317 RS-232-Like Groups ............................................................................................................... 51
 1. Introduction

Welcome to the MGate 5103 line of Modbus/EtherNet/IP-to-PROFINET gateways. All models feature easy
protocol conversion between Modbus RTU/ASCII/TCP, EtherNet/IP, and PROFINET protocols. This chapter is
an introduction to the MGate 5103.

Overview
The MGate 5103 is an industrial Ethernet gateway for Modbus RTU/ASCII/TCP, EtherNet/IP, and PROFINET
network communications. To integrate existing Modbus devices and an EtherNet/IP control system into a
PROFINET network, use the MGate 5103 as a Modbus client/master/server/slave or EtherNet/IP adapter to
collect data and exchange data with PROFINET I/O controllers. The latest exchange data will be stored in
the gateway. The gateway converts stored Modbus or EtherNet/IP data into PROFINET packets so the
PROFINET IO controller can control or monitor field devices.

Package Checklist
All models of the MGate 5103 Series are shipped with the following items:

Standard Accessories:
• MGate 5103 gateway
• Serial cable: DBL-RJ45F9-150
• Quick installation guide (printed)
• Warranty card

NOTE
Please notify your sales representative if any of the above items are missing or damaged.

Optional Accessories (can be purchased separately)

• CBL-F9M9-150: DB9-female-to-DB9-male serial cable, 150 cm
• CBL-F9M9-20: DB9-female-to-DB9-male serial cable, 20 cm
• CBL-RJ45SF9-150: RJ45-to-DB9-female shielded serial cable, 150 cm
• ADP-RJ458P-DB9F: DB9-female-to-RJ45 connector
• ADP-RJ458P-DB9F-ABC01: DB9-female-to-RJ45 connector
• Mini DB9F-to-TB: DB9-female-to-terminal-block connector

MGate 5103 Series User Manual 5

Product Features
• Supports PROFINET IO devices
• Supports Modbus RTU/ASCII/TCP client/master/server/slave
• Supports an EtherNet/IP adapter
• Step-by-step guide with wizard configuration
• Complete packet analysis and diagnostic information for maintenance
• Embedded Modbus RTU/ASCII/TCP traffic monitoring
• microSD card for configuration backup and event logs
• -40 to 75°C wide operating temperature models available
• Serial port with 2 kV built-in isolation protection
• Built-in Ethernet cascading for easy wiring
• Security features based on IEC-62443 standards

MGate 5103 Series User Manual 6

 2. Hardware

Power Input and Relay Output Pinouts

V2+ V2- V1+ V1-

Shielded DC Power DC Power DC Power DC Power

N.O. Common N.C.
Ground Input 2 Input 2 Input 1 Input 1

LED Indicators
Agent Mode:
LED Color Description
Off Power is off or a fault condition exists
Green Steady: Power is on, and the MGate is functioning normally
Steady: Power is on, and the MGate is booting up
Ready
Blinking slowly: Indicates an IP conflict, or the DHCP or BOOTP server is not
Red
responding properly
Flashing quickly: microSD card failed
Modbus: No communication with Modbus device
Off
EtherNet/IP: No I/O data exchange
Modbus: Communication is in progress
Green (Blinking)
EtherNet/IP: I/O data is exchanging
Communication error
When the MGate 5103 acts as a Modbus Client/Master:
1. Server/Slave device returned an error (exception)
2. Received a frame error (parity error, checksum error)
MB/EIP 3. Timeout (server/slave device is not responding or the TCP connection
timed out)
Red (Blinking)
When the MGate 5103 acts as a Modbus Server/Slave:
1. Received invalid function code
2. Client/Master accessed invalid register address or coil addresses
3. Received frame error (parity error, checksum error)

When the MGate 5103 acts as an EtherNet/IP adapter:

1. Refuses connection due to incorrect configuration
Off No connection with the PROFINET IO controller
PN Green (Blinking) The PROFINET IO is connected, and the controller is in RUN mode
Red (Blinking) The PROFINET IO is connected, but the controller is in STOP mode

MGate 5103 Series User Manual 7

Dimensions
Unit: mm (inch)

Pin Assignments
Serial Port (Male DB9)
Pin RS-232 RS-422/RS-485 (4W) RS-485 (2W)
1 DCD TxD-(A) –
2 RXD TxD+(B) –
3 TXD RxD+(B) Data+(B)
4 DTR RxD-(A) Data-(A)
5* GND GND GND
6 DSR – –
7 RTS – –
8 CTS – –
9 – – –

*Signal ground

Ethernet Port (RJ45)

Pin Signal
1 Tx+
2 Tx-
3 Rx+
6 Rx-

Console Port (RS-232)

The MGate 5103 Series can use an RJ45 serial port to connect to a PC for device configuration.

Pin RS-232
1 DSR
2 RTS
3 GND
4 TXD
5 RXD
6 DCD
7 CTS
8 DTR

MGate 5103 Series User Manual 8

Mounting the Unit
1. Connect the power adapter. Connect the 12-48 VDC power line or DIN-rail power supply to the MGate
5103’s terminal block.
2. Use a serial cable to connect the MGate to the Modbus device.
3. Use an Ethernet cable to connect the MGate to the Modbus, PROFINET or EtherNet/IP device.
4. The MGate 5103 is designed to be attached to a DIN rail or mounted on a wall. For DIN-rail mounting,
push down the spring and properly attach it to the DIN rail until it snaps into place. For wall mounting,
install the wall-mounting kit (optional) first and then screw the device onto the wall.

The following figure illustrates the two mounting options:

Specifications
NOTE
The latest specifications for Moxa's products can be found at https://www.moxa.com.

Reset Button

Restore the MGate to factory default settings by using a pointed object (such as a straightened paper clip)
to hold the reset button down until the Ready LED stops blinking (approx. five seconds).

MGate 5103 Series User Manual 9

Pull-Up, Pull-Down, and Terminator for RS-485
Remove the MGate 5103’s top cover, and you will find DIP switches to adjust each serial port’s pull-up
resistor, pull-down resistor, and terminator.

SW 1 2 3
Pull-up resistor Pull-down resistor Terminator
ON 1 kΩ 1 kΩ 120 Ω
OFF 150 kΩ* 150 kΩ* –*
*Default

MicroSD
The MGate 5103 provides users with an easy way to backup, copy, replace, or deploy. The MGate is
equipped with a microSD card slot. Users can plug in a microSD card to backup data, including the system
configuration setting, and system data log.

First time using the MGate gateway with a new microSD card
1. Format the microSD card as FAT file system through a PC.
2. Power off the MGate and insert the microSD card (ensure that the microSD card is empty).
3. Power on the MGate. The default settings will be copied to the microSD card.
4. Manually configure the MGate via web console, and all the stored changes will copy to the microSD card
for synchronization.

First time using the MGate with a microSD card containing a configuration file
1. Power off the MGate and insert the microSD card.
2. Power on the MGate.
3. The configuration file stored in the microSD card will automatically copy to the MGate.

Duplicating current configurations to another MGate gateway

1. Power off the MGate and insert a new microSD card.
2. Power on the MGate.
3. The configuration will be copied from the MGate to the microSD card.
4. Power off the MGate and insert the microSD card to the other MGate.
5. Power on the second MGate.
6. The configuration file stored in the microSD card will automatically copy to the MGate.

Malfunctioning MGate replacement

1. Replace the malfunctioning MGate with a new MGate.
2. Insert the microSD card into the new MGate.
3. Power on the MGate.
4. The configuration file stored on the microSD card will automatically copy to the MGate.

MGate 5103 Series User Manual 10

 MicroSD card writing failure
The following circumstances may cause the microSD card to experience a writing failure:

1. The microSD card has less than 20 Mbytes of free space remaining.
2. The microSD card is write-protected.
3. The file system is corrupted.
4. The microSD card is damaged.

The MGate will stop working in case of the above events, accompanied by a flashing Ready LED and beeping
alarm. When you replace the MGate gateway’s microSD card, the microSD card will synchronize the
configurations stored on the MGate gateway. Note that the replacement microSD card should not contain
any configuration files on it; otherwise, the out-of-date configuration will copy to the MGate device.

MGate 5103 Series User Manual 11

 3. Getting Started

Connecting the Power

The unit can be powered by connecting a power source to the terminal block:

1. Loosen or remove the screws on the terminal block.

2. Turn off the power source and then connect a 12–48 VDC power line to the terminal block.
3. Tighten the connections, using the screws on the terminal block.
4. Turn on the power source.

NOTE
The unit does not have an on/off switch. It automatically turns on when it receives power. The PWR LED
on the top panel will glow to indicate that the unit is receiving power. For power terminal block pin
assignments, refer to the Power Input and Relay Output Pinouts section in chapter 2.

Connecting Serial Devices

The MGate 5103 supports Modbus serial devices. Before connecting or removing the serial connection, first
make sure the power is turned off. For the serial port pin assignments, see the Pin Assignments section in
chapter 2.

Connecting to a Network
Connect one end of the Ethernet cable to the MGate’s 10/100M Ethernet port and the other end of the cable
to the Ethernet network. The MGate will indicate a valid connection to the Ethernet in the following ways:

• The Ethernet LED maintains a solid green color when connected to a 100 Mbps Ethernet network.
• The Ethernet LED maintains a solid orange color when connected to a 10 Mbps Ethernet network.
• The Ethernet LED will flash when Ethernet packets are being transmitted or received.

MGate 5103 Series User Manual 12

Installing DSU Software
If you do not know the MGate gateway’s IP address when setting it up for the first time (default IP is
192.168.127.254); use an Ethernet cable to connect the host PC and MGate gateway directly. If you
connect the gateway and host PC through the same Ethernet switch, make sure there is no router between
them. You can then use the Device Search Utility (DSU) to detect the MGate gateways on your network.

The following instructions explain how to install the DSU, a utility to search for MGate 5103 units on a
network.

1. Insert the Document and Software CD into the CD-ROM drive. Locate and run the following setup
program to begin the installation process:
dsu_setup_[Version]_Build_[DateTime].exe
This version might be named dsu_setup_Ver2.x_Build_xxxxxxxx.exe
2. You will be greeted by the Welcome window. Click Next to continue.
3. When the Select Destination Location window appears, click Next to continue. You may change the
destination directory by first clicking on Browse....
4. When the Select Additional Tasks window appears, click Next to continue. You may select Create a
desktop icon if you would like a shortcut to the DSU on your desktop.
5. Click Install to start copying the software files.
6. A progress bar will appear. The procedure should take only a few seconds to complete.
7. A message will indicate that the DSU is successfully installed. You may choose to run it immediately by
selecting Launch DSU.
8. You may also open the DSU through Start > Programs > MOXA > DSU.

The DSU window should appear as shown below.

Click Search and a new Search window will pop up.

MGate 5103 Series User Manual 13

Logging in to the Web Console
Use the Web console to configure the MGate through Ethernet or verify the MGate’s status. Use a web
browser, such as Microsoft Internet Explorer or Google Chrome to connect to the MGate, using the
HTTP/HTTPS protocol.

When the MGate gateway appears on the DSU device list, select the gateway and use the right-click the
mouse button to open a web console to configure the gateway.

On the first page of the web console, enter admin for the default Account name and moxa for the default
Password.

When you log in the web console for the first time, a message will pop up. Emphasizing a higher security
level, we suggest you to change the password. The password can be changed in the following path:

System Management > Misc. Settings > Account Management

Quick Setup
The MGate series now provides a Quick Setup wizard, an illustrated guide specifically designed to make the
configuration process easy. The Quick Setup wizard takes you through the configuration process from start
to finish so that you do not miss any step. The following agent modes are supported in the Quick Setup:

Device 1 Device 2
PROFINET IO controller Modbus RTU/ASCII slave
PROFINET IO controller Modbus RTU/ASCII master
PROFINET IO controller Modbus TCP client
PROFINET IO controller Modbus TCP server
PROFINET IO controller EtherNet/IP scanner

MGate 5103 Series User Manual 14

Quick Setup—System Setting
First, configure the Server Settings to identify the units and Network Settings of the MGate.

Quick Setup—Select Protocol

Then, you should select your devices' protocols on each side. After selection, the MGate will change its role
to the correct one. For example, if the device is set as a PROFINET IO controller, the MGate will then
automatically configure as a PROFINET IO device by itself. Regarding protocol configuration, refer to chapter
4.

Quick Setup—Role 1 and Role 2 of MGate 5103

After finishing the device protocol selection, Role 1 and Role 2 of MGate will be confirmed. You will need to
configure the roles on each side by the following steps. Here is an example of Role 1 as a PROFINET IO
controller, and Role 2 as a Modbus RTU/ASCII Slave.

MGate 5103 Series User Manual 15

 PROFINET settings: Set MGate Unit ID and TCP port.

Modbus RTU/ASCII settings: Set Mode selection, Serial Parameters Settings and Modbus Commands.

Modbus Command settings: For configuration details, refer to Chapter 4.

MGate 5103 Series User Manual 16

Quick Setup—Finish
Once all the configurations are done, you can check if the parameters are correct on this webpage. Click
Save to make the parameters effective. To view PROFINET and Modbus mapping data, click I/O data
mapping. To export GSDML for PLC use, click PROFINET IO Settings, and go to the Protocol Settings >
I/O Data Mapping page. For additional details, refer to chapter 4, Protocol Settings—I/O Data Mapping.

MGate 5103 Series User Manual 17

 4. Web Console Configuration and
Troubleshooting

This chapter provides a quick overview of how to configure the MGate 5103 by web console.

Overview
This section gives an overview of the MGate 5103 status.

Basic Settings
On this webpage, you can change the name of the device and time zone settings.

Server Setting
Parameter Value Description
You can enter a name to help you identify the unit, such as
Server Name (an alphanumeric string)
the function, etc.
You can enter a name to help you identify the unit location.
Server Location (an alphanumeric string)
Such as “Cabinet A001.”

MGate 5103 Series User Manual 18

 Time Settings

The MGate 5103 has a built-in Real-Time Clock for time calibration functions. Functions such as the log
function can add real-time information to the message.

ATTENTION
First-time users should select the time zone first. The console will display the “real time” according to the
time zone relative to GMT. If you would like to modify the real-time clock, select Local time. MGate’s
firmware will modify the GMT time according to the Time Zone.

Parameter Value Description

This field shows the currently selected time zone and
Time Zone User’s selectable time zone
allows you to select a different time zone.
Local Time User’s adjustable time. (1900/1/1-2037/12/31)
This optional field specifies your time server’s IP address or
IP or Domain address domain name if a time server is used on your network. The
Time Server (e.g., 192.168.1.1 or module supports SNTP (RFC-1769) for automatic time
time.stdtime.gov.tw) calibration. The MGate will request time information from
the specified time server every 10 minutes.

ATTENTION
If the dispersion of the time server is higher than the client (MGate), the client will not accept NTP
messages from the time server. MGate's dispersion is 1 second. You must configure your time server with
a dispersion value lower than 1 sec for the NTP process to complete.

Network Settings
The Network Settings is where the unit’s network settings are configured. You can modify the IP
Configuration, IP Address, Netmask, Default Gateway, and DNS.

Parameter Value Description

Select Static IP if you are using a fixed IP address. Select
IP Configuration Static IP, DHCP, BOOTP one of the other options if the IP address is set
dynamically.
192.168.127.254 The IP (Internet Protocol) address identifies the server on
IP Address
(or other 32-bit number) the TCP/IP network.
255.255.255.0 This identifies the server as belonging to a Class A, B, or C
Netmask
(or other 32-bit number) network.
0.0.0.0 This is the IP address of the router that provides network
Gateway
(or other 32-bit number) access outside the server’s LAN.
0.0.0.0
DNS Server 1 This is the IP address of the primary domain name server.
(or other 32-bit number)
0.0.0.0 This is the IP address of the secondary domain name
DNS Server 2
(or other 32-bit number) server.

MGate 5103 Series User Manual 19

Serial Settings
The MGate 5103’s serial interface supports RS-232, RS-422, and RS-485 interfaces. You must configure the
baudrate, parity, data bits, and stop bits before using the serial interface with Modbus RTU/ASCII protocol.
Incorrect settings will result in communication failures.

Parameter Value Description

Supports standard baudrates (bps):
50/75/110/134/150/300/600/
Baudrate 1200/1800/2400/4800/7200/
9600/19200/38400/57600/115200/
230.4k/460.8k/921.6k
Parity None, Odd, Even, Mark, Space
Data bits 7,8
Stop bits 1, 2
The RTS Toggle will turn off RTS
signal when there is no data to be
sent. If there is data to be sent, the
None,
RTS toggle will turn on the RTS
Flow control RTS/CTS,
signal before a data transmission
RTS Toggle
and off after the transmission is
completed.

The internal buffer of UART.

Disabling FIFO can reduce the
latency time when receiving data
FIFO Enable, Disable
from serial communications, but
this will also slow down the
throughput.
RS-232, RS-422,
Interface RS-485 2 wire,
RS-485 4 wire
RTS on delay 0-100 ms Only available for RTS Toggle
RTS off delay 0-100 ms Only available for RTS Toggle

RTS Toggle

The RTS Toggle function is used for RS-232 mode only. This flow-control mechanism is achieved by
toggling the RTS pin in the transmission direction. When activated, data will be sent after the RTS pin is
toggled ON for the specified time interval. After the data transmission is finished, the RTS pin will toggle
OFF for the specified time interval.

Protocol Settings (Agent Mode)

A typical MGate 5103 application consists of a SCADA/PLC as a client/master and a field device as a
server/slave. Both these components use different protocols and hence need a gateway in between to
exchange data. The MGate can do the role of a gateway by acting as the server/slave when it is connected
to SCADA/PLC and the client/master when it is connected to a field device. Therefore, to configure an
MGate, you must:

1. Select the correct protocols in the Protocol Conversion setting after which the details of both sides of
the MGate’s role is shown below the selection.
2. Configure MGate’s roles for both sides. Configure the master side first followed by the slave side.
3. After the MGate configuration is completed, click I/O data mapping to view details on exchanging
data with the SCADA/PLC.

MGate 5103 Series User Manual 20

 The following sections contain detailed MGate configuration instructions organized as per the above outline.

Protocol Settings—Protocol Conversion

The MGate 5103 supports Modbus RTU/ASCII, Modbus TCP, EtherNet/IP, and PROFINET protocols. The
MGate fulfills a different role on each of its sides. Each role is determined by your device’s settings.
Therefore, set the role of each of your devices correctly. PROFINET IO controller, Modbus RTU/ASCII
Master/Slave, Modbus TCP Client/Server, EtherNet/IP Scanner can be selected.

Below is the selection table of the MGate 5103.

Device 1 Device 2
PROFINET IO controller Modbus TCP client
PROFINET IO controller Modbus TCP server
PROFINET IO controller Modbus RTU/ASCII master
PROFINET IO controller Modbus RTU/ASCII slave
PROFINET IO controller EtherNet/IP scanner

The MGate 5103 runs agent mode when it is used for various different protocol conversions. In agent mode,
the MGate 5103 uses an internal memory to exchange data.

The MGate’s internal memory is divided into two parts—one for input and the other for output as shown in
the illustration below. The internal memory concept is shown in the figure below:

To learn more about MGate’s internal memory, refer to Protocol Settings—I/O Data Mapping.

MGate 5103 Series User Manual 21

 After protocol selection, we have to configure each side of MGate’s role. In a typical application, one side of
MGate will be set as a server/slave and the other side will be set as a client/master. The following
configuration settings are possible:

A1. Modbus TCP Client (Master) Settings

A2. Modbus RTU/ASCII Master Settings

A3. Modbus TCP Server (Slave) Settings

A4. Modbus RTU/ASCII Slave Settings

A5. PROFINET IO Device Settings

A6. EtherNet/IP Adapter Settings

Protocol Settings—Modbus TCP Client (Master) Settings

Client Settings
Parameter Value Default Description
Some Modbus servers/slaves may take more time to boot up than
other devices. In some environments, this may cause the entire
Initial delay 0-30000 ms 0 system to suffer from repeated exceptions during the initial boot-up.
After booting up, you can force the MGate to wait before sending the
first request with the Initial Delay setting.
This is used to configure how many times the MGate will try to
Max. retry 0-5 3
communicate with the Modbus server/slave.
The time taken by a server/slave device to respond to a request is
defined by the device manufacturer based on the Modbus standard.
A Modbus client/master can be configured to wait a certain amount
of time for a server/slave’s response. If no response is received
within the specified time, the client/master will disregard the request
Response
10-120000 ms 1000 and continue operation. This allows the Modbus system to continue
timeout
the operation even if a server/slave device is disconnected or faulty.
On the MGate 5103, the Response timeout field is used to
configure how long the gateway will wait for a response from a
Modbus server/slave. Refer to your device manufacturer’s
documentation to manually set the response timeout

MGate 5103 Series User Manual 22

 Add Modbus Commands

Parameter Value Default Description

Name (an alphanumeric string) Command1 Max. 32 characters
0.0.0.0 - The IP address of a remote server/slave
Slave IP address 0.0.0.0
255.255.255.255 device.
The TCP port number of a remote
Port 1-65535 502
server/slave device.
Slave ID 1-255 1 The Modbus slave ID
1 – Read Coils
2 – Read Discrete Inputs
3 – Read Holding Registers
4 – Read Inputs Registers When a message is sent from a Client to
5 – Write Single Coil a Server device, the function code field
Function
6 – Write Single Register tells the server what kind of action to
15 – Write Multiple Coils perform.
16 – Write Multiple Registers
23 – Read/Write Multiple
Registers
Disable: The command is never sent
Cyclic: The command is sent cyclically at
the interval specified in the Poll Interval
Cyclic
parameter.
Trigger Data Change
Data change: The data area is polled for
Disable
changes at the time interval defined by
Poll Interval. A command is issued when
a change in data is detected.
Polling intervals are in milliseconds. Since
the module sends all requests in turns,
the actual polling interval also depends
Poll interval 100-1200000 ms 1000
on the number of requests in the queue
and their parameters. The range is from
100 to 1,200,000 ms.

MGate 5103 Series User Manual 23

 Parameter Value Default Description
Data Byte Swapping
None: Don't need to swap
Byte: 0x0A, 0x0B, 0x0C, 0x0D becomes
0x0B, 0x0A, 0x0D, 0x0C
Word: 0x0A, 0x0B, 0x0C, 0x0D becomes
None 0x0C, 0x0D, 0x0A, 0x0B.
Byte ByteWord: 0x0A, 0x0B, 0x0C, 0x0D
Endian swap None
Word becomes 0x0D, 0x0C, 0x0B, 0x0A.
Byte and Word There are two phases in changing
ByteWord:
1) 0x0A, 0x0B, 0x0C, 0x0D becomes
0x0B, 0x0A, 0x0D, 0x0C
2) 0x0B, 0x0A, 0x0D, 0x0C becomes
0x0D, 0x0C, 0x0B, 0x0A
Read starting
0-65535 0 Modbus register address.
address
Read Coils: 1 - 2000
Read Discrete Inputs: 1 -
2000
Read Inputs Registers: 1 -
Read quantity 125 10 Specifying how many items to read.
Read Holding Registers:
1 - 125
Read/Write Multiple Registers:
1 - 125
Write starting
0-65535 0 Modbus register address.
address
Write Multiple Coils: 1 - 1968
Write Multiple Registers:
Write quantity 1 - 123 1 Specifying how many items to write into.
Read/Write Multiple Registers:
1 - 123
If MGate’s connection to the other side
(server/slave) fails, the gateway will not
be able to receive data, but the gateway
will continuously send output data to the
Keep latest data
Modbus TCP server device. To avoid
Fault protection Clear all data bits to 0
problems in this case, the MGate 5103
Set to user defined value
can be configured to react in one the
following three ways: Keep latest data,
clear data to zero, set the data bits to
user-defined values.
The user-defined values to write into the
Fault value 00 00 data bits when the Set to user defined
value option is selected.
Defines the communication timeout for
Fault timeout 1-86400 s 3600
the opposite side.

MGate 5103 Series User Manual 24

Protocol Settings—Modbus RTU/ASCII Master Settings

Master Settings
Parameter Value Default Description
Mode RTU or ASCII RTU The Modbus protocol type
Some Modbus servers/slaves may take more time to boot
up than other devices. In some environments, this may
cause the entire system to suffer from repeated
Initial delay 0-30000 ms 0
exceptions during the initial boot-up. After booting up,
you can force the MGate to wait before sending the first
request with the Initial Delay setting.
The number of times the client/master will retry the same
Max. retry 0-5 3
request when the response times out.
According to the Modbus standard, the time it takes for a
server/slave device to respond to a request is defined by
the device manufacturer. Based on this response time, a
client/master can be configured to wait a certain amount
of time for a server/slave’s response. If no response is
received within the specified time, the client/master will
disregard the request and continue operation. This allows
Response timeout 10-120000 ms 1000
the Modbus system to continue operations even if a
server/slave device is disconnected or faulty. On the
MGate 5103, the Response timeout field is used to
configure how long the gateway will wait for a response
from a Modbus ASCII or RTU server/slave. Refer to your
device manufacturer’s documentation to manually set the
response time.

MGate 5103 Series User Manual 25

 Parameter Value Default Description
Defines the time interval between an RTU response and
the next RTU request. When the baudrate is lower than
19200 bps, the default value is 0, which is 3.5 character
time. When the baudrate is larger than 19200 bps, the
MGate uses a predefined fixed value that is not user-
configurable. This function solves the issue that some
devices can't handle the RTU requests that quickly, so the
MGate opens to user-defined values.

How to calculate Modbus character time?

E.g., if the baudrate is 9600 bps, 1 character time is
about 1 ms. In a serial frame (11 bits, including start bit,
data, parity bit, and stop bit), 9600 bps approximately
Inter-frame delay equals to 960 characters/s, so transmitting 1 character
(only for Modbus 10-500 ms 0 needs about 1/960 = 1 ms.
RTU)

The time interval between characters in one frame. When

the baudrate is lower than 19200 bps, the default value is
Inter-character 0, which is 1.5 character time. When the baudrate is
timeout larger than 19200 bps, the MGate uses a predefined fixed
10-500 ms 0
(only for Modbus value that is not user-configurable. When the serial side
RTU) of the MGate receives one character, and the next one
comes after the “inter-character timeout” defined, the
frame will be discarded because of timeout.

Add Modbus Commands

Refer to Modbus TCP Client (Master) Settings.

MGate 5103 Series User Manual 26

Protocol Settings—Modbus TCP Server (Slave) Settings

Server Settings
Parameter Value Default Description
The Modbus slave ID that this server/slave module will
Unit ID 1-255 1
accept.
TCP port 1-65535 502 The TCP port number.

Protocol Settings—Modbus RTU/ASCII Slave Settings

Slave Settings
Parameter Value Default Description
Mode RTU or ASCII RTU The Modbus protocol type
The Modbus slave ID that this server/slave module will
Slave ID 1-255 2
accept.

MGate 5103 Series User Manual 27

Protocol Settings—PROFINET IO Device Settings
The PROFINET IO Device settings are very simple. For PROFINET IO communication, the IO controller only
needs to input the Device Name to exchange data.

Parameter Value Description

Enter the PROFINET server name (if you type the name
Device Name <alphanumeric string>
incorrectly, the connection will fail).

The function of Export GSDML is used for easy configuration when setting the PROFINET IO controller
system. Typically, users waste lots of time in importing MGate 5103 general GSDML files and then setting
the IO modules, respectively. If we import the specified GSDML, which is based on Modbus settings, we just
need to pull the module to the PROFINET system. Then the IO modules will be set, and you can run the
communication.

MGate 5103 Series User Manual 28

Protocol Settings—EtherNet/IP Adapter Settings
The MGate 5103 supports Adapter mode for EtherNet/IP protocol. In Adapter mode, you should configure O
 T (Originator to Target) and T  O (Target to Originator) data sizes to exchange data with the
PROFINET IO controller.

Parameter Value Default Description

If there is no encapsulation activity for a specific
EIP encapsulation 0 – 300 sec,
120 time, the Ethernet/IP session will be cleaned and the
inactivity timeout 0 for disable
TCP connection will be disconnected.
O  T instance The O  T (output size) should the same as
0 – 496 bytes 0
(Output) data size EtherNet/IP Scanner
T  O instance The T  O (Input size) should the same as
0 – 496 bytes 0
(Input) data size EtherNet/IP Scanner

Protocol Settings—I/O Data Mapping

After you have configured Role 1 and Role 2 (client/master and server/slave) of the MGate settings, the
PLC/SCADA in the client/master role will start monitoring and controlling the remote server/slave device.
MGate uses its internal memory to facilitate data exchange. The I/O Data Mapping page shows the
complete mapping status.

MGate 5103 Series User Manual 29

 The following examples illustrate Role 1 and Role 2 configurations of MGate:

Example - MGate 5103 as PROFINET IO Device (Role 1) and Modbus RTU/ASCII Master (Role 2)

If the PROFINET IO controller wants to set the Modbus RTU command, Room1_Breaker2, the PROFINET IO
controller must use the second byte to do the changes. The MGate will then trigger a Room1_Breaker2 write
request to the Modbus RTU server/slave device.

Likewise, if the PROFINET IO controller wants to read the Modbus RTU command, Room1_Voltage1, the
PROFINET IO controller must use the first two bytes to collect the data. The other side of the MGate will
periodically update the value in the internal memory through cyclic polling to the Modbus RTU server/slave
device.

MGate 5103 Series User Manual 30

System Management
System Management—Accessible IP List

These settings are used to restrict access to the module by the IP address. Only IP addresses on the list will
be allowed access to the device. You may add a specific address or range of addresses by using a
combination of an IP address and a netmask as follows:

To allow access to a specific IP address: Enter the IP address in the corresponding field; enter
255.255.255.255 for the netmask.

To allow access to hosts on a specific subnet: For both the IP address and netmask, use 0 for the last
digit (e.g., “192.168.1.0” and “255.255.255.0”).

To allow access to all IP addresses: Make sure that Enable the accessible IP list is not checked.

Additional configuration examples are shown in the following table:

Allowed hosts Entered IP address/Netmask

Any host Disable “Accessible IP List” function
192.168.1.120 192.168.1.120 / 255.255.255.255
192.168.1.1 to 192.168.1.254 192.168.1.0 / 255.255.255.0
192.168.0.1 to 192.168.255.254 192.168.0.0 / 255.255.0.0
192.168.1.1 to 192.168.1.126 192.168.1.0 / 255.255.255.128
192.168.1.129 to 192.168.1.254 192.168.1.128 / 255.255.255.128

MGate 5103 Series User Manual 31

System Management—DoS Defense
Users can select from several options to enable DoS Defense in order to fend off cybersecurity attacks. A
denial-of-service (DoS) attack is an attempt to make a machine or a network resource unavailable. Users
can select from the following options to counter DoS attacks.

System Management—System Log Settings

The system log settings enable the MGate firmware to record important events, which can be record in two
ways: Syslog and Local Log (stored in the MGate).

MGate 5103 Series User Manual 32

 The available information that can be recorded includes the following events:

Event Group Description

System System Cold Start, System Warm Start
DHCP/BOOTP Get IP/Renew, NTP Connect Fail, IP Conflict,
Network
Network Link Down
Login Fail, IP Changed, Password Changed, Firmware Upgrade,
Configuration SSL Certificate Import, Configuration Import/Export,
Configuration Change, Clear Event Log
PROFINET PROFINET communication logs
Modbus TCP Modbus TCP communication logs
EtherNet/IP EtherNet/IP communication logs

Local Log Settings Description

Enable log capacity warning When the log amount exceeds the warning percentage, it will
(%) trigger an event to SNMP Trap or Email.
SNMP Trap
Warning by
Email
Overwrites the oldest event log
Event log oversize action
Stops recording event log

Syslog Settings Description

Syslog server IP IP address of a server which will record the log data
Syslog server port 514

System Management—Auto Warning Settings

Auto Warning is triggered by different events. When a checked trigger condition occurs, the MGate can send
email alerts, SNMP Trap messages, or open/close the circuit of the relay output and trigger the Fault LED to
start blinking. To enable an email alert, configure the email address on the Email Alert page. Likewise, to
enable SNMP trap alerts, configure SNMP trap server on the SNMP Trap page.

MGate 5103 Series User Manual 33

System Management—Email Alert

Parameters Description
Mail server (SMTP) The mail server’s domain name or IP address.
User name This field is for your mail server’s user name, if required.
Password This field is for your mail server’s password, if required.
From email address This is the email address from which automatic email warnings will be sent.
To email address 1 to 4 Email addresses to which automatic email warnings will be sent.

System Management—SNMP Trap

Parameters Description
SNMP trap server IP Use this field to indicate the IP address to use for receiving SNMP traps.
Trap version Use this field to select the SNMP trap version.
Trap community Use this field to designate the SNMP trap community.

MGate 5103 Series User Manual 34

System Management—SNMP Agent

Parameters Description
To enable the SNMP Agent function, select the Enable option, and enter a
SNMP
community name (e.g., public).
The optional SNMP contact information usually includes an emergency contact
Contact name
name and telephone number.
This is a text password mechanism that is used to weakly authenticate queries
Read community string
to agents of managed network devices.
This is a text password mechanism that is used to weakly authenticate changes
Write community string
to agents of managed network devices.
SNMP agent version The MGate 5103 supports SNMP V1, V2c, and V3.

Read-only and Read/write access control

The following fields allow you to define user names, passwords, and authentication parameters for two
levels of access: read-only and read/write. The name of the field will indicate which level of access it refers
to. For example, Read-only authentication mode allows you to configure the authentication mode for read-
only access, whereas Read/write authentication mode allows you to configure the authentication mode for
read/write access. For each level of access, you may configure the following:

Parameters Description
User name Use this optional field to identify the user name for the specified level of access.
Use this field to select MD5 or SHA as the method of password encryption for the
Authentication mode
specified level of access, or to disable authentication.
Use this field to enable or disable DES_CBC data encryption for the specified level
Privacy mode
of access.
Password Use this field to set the password for the specified level of access.
Privacy Use this field to define the encryption key for the specified level of access.

MGate 5103 Series User Manual 35

System Management—LLDP Settings
The Link Layer Discovery Protocol (LLDP) standardizes the method that devices on a network use to
periodically send information on their configuration and status. This self-identification method keeps all LLDP
devices on a network informed of each other's status and configuration. You can use SNMP protocol to then
send the LLDP information on the network devices to Moxa's MXview to create auto network topology and
for network visualization.

The MGate web interface lets you enable or disable LLDP, and set the LLDP transmit interval. In addition,
you can go to System Monitoring—System Status—LLDP Table to view the MGate’s neighbor-list, which is
created based on the information reported by neighboring devices on the network.

Parameters Values Description

MGate will send information on the
5–16383 secs (Default:30 configuration and status of devices in a network
Message transmit interval
secs) at regular intervals based on the value
configured here.

System Management—Certificate

Use this function to load the Ethernet SSL certificate. Select or browse for the certificate file in the Select
SSL certificate/key file field. This function is only available in the web console

MGate 5103 Series User Manual 36

System Management—Misc. Settings
This page includes console settings, password and relay output.

System Management—Misc. Settings—Console Settings

Configuration Value Description

This setting is to enable/disable the web console. For security
HTTP/HTTPS Enable/Disable
issues, users can only enable the HTTPS or just disable all
settings.
Telnet/SSH Enable/Disable The MGate telnet/SSH function can be enabled or disabled.
Serial console Enable/Disable The MGate serial console function can be enabled or disabled.
MGate provides the reset button to clear password or load
factory default settings. But for security issues, users can
Reset button Disable after 60 sec,
disable this function. In disabled mode, MGate will still enable
protect Always enable
this function within 60 seconds after boot-up, just in case users
really need to reset this function.
The MGate can be searched by the DSU. If you have any
MOXA command Enable/Disable security concerns, you can choose Disable to deny the DSU the
right to access.

Session Settings Value Description

Maximum Login Users The number of users that can access the MGate at the same
1-10
for HTTP+HTTPS time.
Auto Logout Setting 0-1440 min. Sets the auto logout time period.

MGate 5103 Series User Manual 37

 System Management—Misc. Settings—Notification Message

Users can input a message for Login or for Login authentication failure message.

System Management—Misc. Settings—Account Management

Parameters Value Description

Users can modify the password for different accounts. MGate
provides two different level accounts: admin and user. Admin
Account admin, user account can access and modify all the settings through the web
console. User account can only view the setting and can’t change
anything.

MGate 5103 Series User Manual 38

 System Management—Misc. Settings—Login Password Policy

Account Password Policy Value Description

Minimum length 4-16 The minimum password length
Enable password complexity
Select how the MGate checks the password’s strength
strength check
Password lifetime 90-180 days Set the password’s lifetime period.

Account Login Failure Lockout Value Description

Indicates the number of login failures before the MGate
Retry failure threshold 1-10 time
locks out.
When the number of login failures exceeds the threshold,
Lockout time 1-60 min
the MGate will lock out for a period of time.

System Management—Maintenance

System Management—Maintenance—Ping
This network testing function is available only in the web console. The MGate gateway will send an ICMP
packet through the network to a specified host, and the result can be viewed in the web console
immediately.

MGate 5103 Series User Manual 39

 System Management—Maintenance—Firmware Upgrade
Firmware updates for the MGate 5103 are located at www.moxa.com. After you have downloaded the new
firmware onto your PC, you can use the web console to write it onto your MGate 5103. Select the desired
unit from the list in the web console and click Submit to begin the process.

ATTENTION
DO NOT turn off the MGate power before the firmware upgrade process is completed. The MGate will be
erasing the old firmware to make room for the new firmware to flash memory. If you power off the MGate
and terminate the progress, the flash memory will contain corrupted firmware and the MGate will fail to
boot. If this happens, call Moxa RMA services.

System Management—Maintenance—Configuration Import/Export

There are three main reasons for using the Import and Export functions:

• Applying the same configuration to multiple units. The Import/Export configuration function is a
convenient way to apply the same settings to units located in different sites. You can export the
configuration as a file and then import the configuration file onto other units at any time.
• Backing up configurations for system recovery. The export function allows you to export
configuration files that can be imported onto other gateways to restore malfunctioning systems within
minutes.
• Troubleshooting. Exported configuration files can help administrators to identify system problems that
provide useful information for Moxa’s Technical Service Team when maintenance visits are requested.

MGate 5103 Series User Manual 40

 System Management—Maintenance—Load Factory Default
To clear all the settings on the unit, use the Load Factory Default to reset the unit to its initial factory
default values.

ATTENTION
Load Default will completely reset the configuration of the unit, and all of the parameters you have saved
will be discarded. Do not use this function unless you are sure you want to completely reset your unit.

System Monitoring (Troubleshooting)

MGate 5103 provides easy-to-use and useful troubleshooting tools. If a communication issue occurs, we
suggest that you first check the Protocol Status > Diagnosis page for the status of the protocol. To
analyze the Modbus RTU/ACSII/TCP traffic in detail, view the network logs available at Protocol Status >
Traffic.

System Monitoring—System Status

System Monitoring—System Status—Network Connections

Go to Network Connections under System Status to view network connection information.

MGate 5103 Series User Manual 41

 System Monitoring—System Status—System Log
Go to Network Connections under System Status to view network connection information.

System Monitoring—System Status—Relay State

The MGate gateway includes a built-in relay circuit that is triggered in the event of a power failure or if the
Ethernet link is down. You can view the relay status on this page.

System Monitoring—System Status—LLDP Table

You can see LLDP related information, including Port, Neighbor ID, Neighbor Port, Neighbor Port Description,
and Neighbor System.

MGate 5103 Series User Manual 42

System Monitoring—Protocol Status

System Monitoring—Protocol Status—I/O Data View

This page displays the internal memory information for input and output data transfers. View updated
values for communication verification here. This function is only available in the web console.

System Monitoring—Protocol Status—Diagnose

The MGate provides status information for Modbus RTU/ASCII/TCP, EtherNet/IP, and PROFINET
troubleshooting. Verify data or packet counters to make sure the communications are running smoothly.

Modbus RTU/ASCII Diagnose (Master)

Modbus RTU/ASCII Diagnose (Slave)

MGate 5103 Series User Manual 43

 Modbus TCP Diagnose (Client/Master)

Modbus TCP Diagnose (Slave/Server)

PROFINET Diagnose (IO Device)

MGate 5103 Series User Manual 44

 EtherNet/IP Diagnose (Adapter)

System Monitoring—Protocol Status—Traffic

Modbus RTU/ASCII/TCP Traffic
In order to troubleshoot efficiently, the MGate provides a traffic monitoring function that can capture both
Modbus RTU/ASCII and Modbus TCP communication logs, respectively. These logs present the data in an
intelligent, easy-to-understand format with clearly designated fields, including source, destination, function
code, and data. The complete log can be saved in a file by clicking Export for later analysis.

MGate 5103 Series User Manual 45

Status Monitoring
For gateways in agent mode, if a server/slave device fails or a cable comes loose, generally the gateway
won’t be able to receive up-to-date data from the server/slave device. The out-of-date data will be stored in
the gateway’s memory and will be retrieved by the PROFINET IO controller, which will not be aware that the
server/slave device is not providing up-to-date data. The 5103 supports the Status Monitoring function,
which provides a warning mechanism to report the list of server/slave devices that are still active

The MGate can set up to 128 Modbus commands. The MGate 5103 allocates one bit of the gateway’s
specified memory address to indicate the status of each Modbus command as being normal or abnormal. In
other words, the MGate allocates 128 bits of memory to indicate the status of all Modbus commands. If a
command has run successfully, the status value will continue to be 1. On the contrary, if a command has
failed, the status will be set to 0. These statuses can be monitored by the PROFINET IO controller, using the
way of acyclic read. On how to monitor the status, we take SIMATIC STEP 7 Engineering Software as an
example.

Step 1: If we have set eight Modbus commands in the MGate 5103.

Step 2: We want to monitor the command status through STEP 7. In STEP 7 OB1, we use SFB52 to read
the status of the Modbus commands as below.

MGate 5103 Series User Manual 46

 Step 3: Create Variable Table to monitor “DB128”. Then, set M1.0 as true. It would trigger SFB52 to
read the Modbus command status. DB128.DBB 0 indicates the first to eighth commands status.
If the value is 0xFF, it means the status of all commands is normal.
If the value is 0x7F, it means the status of the eighth command is abnormal. Then, you have to
resort to troubleshooting.

MGate 5103 Series User Manual 47

 5. Configuration (Text Mode Console)

The MGate 5103 supports a text-mode console with serial interface, telnet, and SSH protocol. The user
interface is the same in all text mode consoles. Note that the text mode console does not support all
configuration items. Some parameters must be configured through the web console.

You must use a DB9-to-RJ45 cable to connect the serial console port on the MGate gateway’s front panel to
the serial port on the host. The serial console parameters are 115.2 kbps; parity: none; 8 data bits; and
one stop bit.

For telnet and SSH, use HyperTerminal or PuTTY to connect to the MGate. Note that the telnet protocol will
transfer the account and password information over the Internet using plain text, so telnet is essentially
obsolete and should be replaced by the SSH protocol.

To connect to the MGate telnet/SSH console, load the telnet/SSH program and connect to the MGate IP
address.

For the serial interface, use a null modem (crossover) cable to connect the serial port on the host to the
serial console port on the MGate’s front of panel. The serial console parameters are 115.2kbps, none for
parity, 8 data bits, and one stop bit. You can use a terminal program such as PComm Terminal Emulator or
PuTTY to connect to the MGate serial console.

On the first page, input the account and password. The account supports two types of users: admin and
user. An “admin” account can modify all of the settings, but a “user” account can only review the settings.
A “user” account cannot modify the configuration. The default password for admin is moxa.

The text mode console will display the menu driven interface. Users can use arrow key to move the menu
bar. To select the option, press the “Enter” key to go next level menu. To go previous level menu, press
“Esc” key to quit. If necessary, MGate will need to restart to activate the setting.

MGate 5103 Series User Manual 48

 6. Network Management Tool (MXstudio)

Moxa’s MXstudio industrial network management suite includes tools such as MXconfig, MXview and N-
Snap. MXconfig is for industrial network configuration; MXview is for industrial management software; and
N-Snap is for industrial network snapshot. The MXstudio suite in MGate 5103 includes MXconfig and
MXview, which are used for mass configuration of network devices and monitoring network topology,
respectively. The following functions are supported:

Tool Function Support

1. System name and login password modification
2. Network settings
MXconfig
3. Configuration import/export
4. Firmware upgrade
1. Configuration import/export
MXview 2. LLDP for topology analysis
3. Security View**

** Security View can check the security level of devices in accordance with the IEC62443-4-2 standard.
MGate 5103 supports Level 2 of the IEC-62443-4-2 standard.

MGate 5103 Series User Manual 49

 A. SNMP Agents with MIB II and RS-232-
Like Groups

The MGate 5103 has built-in Simple Network Management Protocol (SNMP) agent software that supports
SNMP Trap, RFC1317 and RS-232-like groups, and RFC 1213 MIB-II.

RFC1213 MIB-II Supported SNMP Variables

System MIB Interfaces MIB IP MIB ICMP MIB
sysDescr ifNumber ipForwarding icmpInMsgs
sysObjectID ifIndex ipDefaultTTL icmpInErrors
sysUpTime ifDescr ipInReceives icmpInDestUnreachs
sysContact ifType ipInHdrErrors icmpInTimeExcds
sysName ifMtu ipInAddrErrors icmpInParmProbs
sysLocation ifSpeed ipForwDatagrams icmpInSrcQuenchs
sysServices ifPhysAddress ipInUnknownProtos icmpInRedirects
ifAdminStatus ipInDiscards icmpInEchos
ifOperStatus ipInDelivers icmpInEchoReps
ifLastChange ipOutRequests icmpInTimestamps
ifInOctets ipOutDiscards icmpTimestampReps
ifInUcastPkts ipOutNoRoutes icmpInAddrMasks
ifInNUcastPkts ipReasmTimeout icmpInAddrMaskReps
ifInDiscards ipReasmReqds icmpOutMsgs
ifInErrors ipReasmOKs icmpOutErrors
ifInUnknownProtos ipReasmFails icmpOutDestUnreachs
ifOutOctets ipFragOKs icmpOutTimeExcds
ifOutUcastPkts ipFragFails icmpOutParmProbs
ifOutNUcastPkts ipFragCreates icmpOutSrcQuenchs
ifOutDiscards ipAdEntAddr icmpOutRedirects
ifOutErrors ipAdEntIfIndex icmpOutEchos
ifOutQLen ipAdEntNetMask icmpOutEchoReps
ifSpecific ipAdEntBcastAddr icmpOutTimestamps
ipAdEntReasmMaxSize icmpOutTimestampReps
ipRouteDest icmpOutAddrMasks
ipRouteIfIndex icmpOutAddrMaskReps
ipRouteMetric1
ipRouteMetric2
ipRouteMetric3
ipRouteMetric4
ipRouteNextHop
ipRouteType
ipRouteProto
ipRouteAge
ipRouteMask
ipRouteMetric5
ipRouteInfo
ipNetToMediaIfIndex
ipNetToMediaPhysAddress
ipNetToMediaNetAddress
ipNetToMediaType
ipRoutingDiscards

MGate 5103 Series User Manual 50

 Address
TCP MIB UDP MIB SNMP MIB
Translation MIB
atIfIndex tcpRtoAlgorithm udpInDatagrams snmpInPkts
atPhysAddress tcpRtoMin udpNoPorts snmpOutPkts
atNetAddress tcpRtoMax udpInErrors snmpInBadVersions
tcpMaxConn udpOutDatagrams snmpInBadCommunityNames
tcpActiveOpens udpLocalAddress snmpInBadCommunityUses
tcpPassiveOpens udpLocalPort snmpInASNParseErrs
tcpAttemptFails snmpInTooBigs
tcpEstabResets snmpInNoSuchNames
tcpCurrEstab snmpInBadValues
tcpInSegs snmpInReadOnlys
tcpOutSegs snmpInGenErrs
tcpRetransSegs snmpInTotalReqVars
tcpConnState snmpInTotalSetVars
tcpConnLocalAddress snmpInGetRequests
tcpConnLocalPort snmpInGetNexts
tcpConnRemAddress snmpInSetRequests
tcpConnRemPort snmpInGetResponses
tcpInErrs snmpInTraps
tcpOutRsts snmpOutTooBigs
snmpOutNoSuchNames
snmpOutBadValues
snmpOutGenErrs
snmpOutGetRequests
snmpOutGetNexts
snmpOutSetRequests
snmpOutGetResponses
snmpOutTraps
snmpEnableAuthenTraps
snmpSilentDrops
snmpProxyDrops

RFC1317 RS-232-Like Groups

RS-232 MIB Async Port MIB
rs232Number rs232AsyncPortIndex
rs232PortIndex rs232AsyncPortBits
rs232PortType rs232AsyncPortStopBits
rs232PortInSigNumber rs232AsyncPortParity
rs232PortOutSigNumber
rs232PortInSpeed
rs232PortOutSpeed

Input Signal MIB Output Signal MIB

rs232InSigPortIndex rs232OutSigPortIndex
rs232InSigName rs232OutSigName
rs232InSigState rs232OutSigState

MGate 5103 Series User Manual 51