RFL IMUX 2000 User manual

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
RFL Electronics Inc.
IMUX 2000
SNMP Access Gateway
User’s Manual
RFL Electronics Inc.
353 Powerville Road
Boonton Township, NJ 07005
[phone]
Publication No. MC2000SNMP
Printed In U.S.A.
Revised August 10, 2009

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Table of Contents
TABLE OF CONTENTS - SNMP ACCESS GATEWAY USER’S MANUAL
CHAPTER 1 - PRODUCT OVERVIEW 1
Figure 1. - SNMP Access Gateway Connectivity Overview 1
1.1 -- Introduction 1
1.2 -- IMUX 2000 Information 2
CHAPTER 2 - INSTALLATION 3
2.1 - Mounting 3
2.2 - Power Input 3
Figure 2. - SNMP Access Gateway Module and MA-810 Module Adapter 3
2.3 - Serial Ports 4
Figure 3. - SNMP Access Gateway DB9 Pin Out 4
2.4 - Ethernet 4
2.5 - Front Panel Items 5
Figure 5. - SNMP Access Gateway Front Panel Layout 5
CHAPTER 3 - BASIC SETUP FOR OPERATION 7
3.1 - Network Setup 7
3.2 - Local Command Mode 7
3.3 - Connections 8
CHAPTER 4 - COMMAND CONTROL 9
4.1 - Command Processor Mode 9
4.2 - General Commands 10
4.2.1 - EXIT 10
4.2.2 - BYE 10
4.2.3 -? (question mark) 10
4.2.4 - SETUP 10
4.2.5 - EVENTS 11
4.2.6 - DEFAULT 11
4.2.7 - COLDSTART 11
4.2.8 - HELP 11
4.2.9 - PING 11
4.3 - Pseudo-SNMP Commands 11
4.3.1 - GET 11
4.3.2 - GETNEXT 12
4.3.3 - GETX 12
4.3.4 - SET 12
4.3.5 - WALK 12

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Table of Contents
CHAPTER 5 - USE OF THE SETUP MENU 13
5.1 - Networking 13
5.1.1 - Network Access Enabled 13
5.1.2 - Get IP Address 13
5.1.3 - IP Address 14
5.1.4 - Network Mask 14
5.1.5 - Default Router 14
5.1.6 - FTP AutoDelete 14
5.1.7 - SNMP Manager Setup 14
5.1.8 - SNMP Trap Setup 14
5.1.9 - SNMP Community Setup 15
5.1.10 - IP Address Restrictions 15
5.1.11 - Ping Router every 10 Mins 15
5.1.12 - PPP Dialout Setup 15
5.1.13 - PPP Hosting Setup 15
5.2 - Serial/Input Ports 15
5.3 - Passwords 16
5.4 - Event Definitions 16
5.4.1 - Set Up Sensor/Analog Events 16
5.4.2 - Upload New Alarm File 17
5.4.3 - View Alarm File 17
5.4.4 - Alarm Evaluator Enabled 18
5.4.5 - Store Data Record Events 18
5.4.6 - Store Alarm Record Events 18
5.4.7 - Store Sensor Events 18
5.4.8 - Store Reset Events 18
5.4.9 - Store Command Log Events 18
5.5 - Action Definitions 18
5.5.1 - Traps 19
5.5.2 - Pagers 19
5.6 - System Date/Time 20
5.7 - General Settings 20
5.7.1 - Set UnitID 20
5.7.2 - Operational Settings 21
5.7.3 - Character Mask 21
CHAPTER 6 - PASS THROUGH MODE 22
CHAPTER 7 - CONSOLE MODE 24
CHAPTER 8 - MANAGEMENT INFORMATION BASE (MIB) 25
CHAPTER 9 - SNMP CONFIGURATION AND CONTROL 29
CHAPTER 10 - USING FTP 40

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Table of Contents
CHAPTER 11 - PROGRAMMING DATA ALARMS 41
11.1 - Alarms are the same as Events 41
11.2 - Alarm Actions 41
11.3 - How Data Alarms Are Set Up 41
11.4 - Defining Data Alarms 41
11.5 - Field Section 42
11.6 - Operators for Formulas 42
11.7 - Macro Section 43
11.8 - Data Alarm Section 43
11.9 - End Section 44
11.10 - Defining Alarm Actions 44
CHAPTER 12 - USE OF THE EVENTS COMMAND 45
12.1 - List Events File 45
12.2 - Clear Events File 45
12.3 - View Active Alarms 45
12.4 - Acknowledge Active Alarms 46
12.5 - View Alarm Action Detail 46
12.6 - View Data Alarm Counters 46
12.7 - View Action History 46
12.8 - Clear Action History 47
CHAPTER 13 - RESETTING THE SNMP ACCESS GATEWAY 48

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Table of Contents
CHAPTER 14 - APPLICATION NOTES 49
APP NOTE A. USE OF IP RESTRICTIONS 50
APP NOTE B: MONITORING RS232 LEVELS AS ALARMS 51
Figure 8. Schematic for Sensor Inputs 51
Figure 9. Illustration of Connecting for Monitoring RS232 Control Lines 51
APP NOTE C: IMUX TRAP MESSAGES 52
C.1 Trap Format 52
C.2 Trap Codes 52
C.3 Trap Configuration Information 53
C.4 MIB Information 53
CHAPTER 15 - WARRANTY INFORMATION 54
CHAPTER 16 - CANADIAN DEPT. OF COMM. NOTICE 55
"Portions of this document are provided by and used with permission of
Omnitronix, 760 Harrison, Seattle, WA, [phone]. Unauthorized
reproduction, distribution, or sale of this user manual is prohibited
"

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Chapter 1 - Product Overview
SNMP Access Gateway User’s Manual - v1.0 -- 11/99 - Page 1
Chapter 1 - Product Overview
1.1 - Introduction
The SNMP Access Gateway monitors serial (RS232) data streams for alarm conditions, and provides notification of
alarm conditions by audible alarm, pager messages and SNMP traps. The SNMP Access Gateway may be used to
provide legacy (non-network) equipment with the ability to generate SNMP traps when alarm conditions occur.
Additionally, the SNMP Access Gateway can provide pass-through access to devices connected to the serial ports of
the SNMP Access Gateway, thereby providing remote access to programming or maintenance ports of equipment.
The SNMP Access Gateway has two serial ports, and one ethernet 10BaseT network port. Front panel LEDs provide
status information about the ethernet connection, serial port activity, and power status.
Figure 1. - SNMP Access Gateway Connectivity Overview
The serial ports can operate from 300 to 19,200 baud, and are used to monitor serial data streams and/or provide
remote pass-through access to connected equipment. These serial ports are labeled IMUX (I/O 1) and REMOTE
(I/O 2). An alarm configuration file can be loaded into the memory of the SNMP Access Gateway, and the SNMP
Access Gateway can then monitor the data received on the serial ports for alarm conditions.
The two serial ports may also be used in a ‘console’ mode, in which the SNMP Access Gateway is placed in-line
between two pieces of equipment. In this mode the alarm configuration file may still be used to monitor the data
streams for alarm conditions, but the SNMP Access Gateway, in this case, passes data received on each serial port to
the other port, so that the SNMP Access Gateway does not disrupt the data flowing between the two devices.
LOCAL
ACCESS
LAPTOP
NETWORK
MANAGER
PC
CM3 SAG
IMUX
RS232 ETHERNET
RS232

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Chapter 1 - Product Overview
SNMP Access Gateway User’s Manual - v1.0 -- 11/99 - Page 2
The serial ports may be used for pass-through access to connected serial devices, similar to a terminal server. A
TCP/IP connection is made to the SNMP Access Gateway, and then characters received from the network
connection is passed to the serial port, and characters received on the serial port are passed to the network
connection. This pass-through mode may be used to remotely access the maintenance ports of equipment, etc.
When more than one connection is made to the SNMP Access Gateway for access to the same pass-through port,
then users may be allowed to ‘join’ connections. This feature can be useful in providing technical support in the use
of the connected equipment. Two remote users, at different locations, can both have access to the same pass-through
port. This allows a person providing technical support to see what commands or data is actually being sent and
received, which can be quite useful when providing technical support.
One of the serial ports (I/O 2) may also be used as a local command port, for configuration or checking on the status
of the device. ‘Local Command Port Mode’ may be entered by using either a push-button located on the front panel
of the SNMP Access Gateway or by entering a pre-defined escape sequence on the serial port itself. This local
command port is especially useful when performing static allocation of network IP addresses, in which case the
SNMP Access Gateway needs to be configured with an IP address prior to it its use on the network.
An Events file is maintained by the SNMP Access Gateway which contains logged events, such as received alarm
records, etc. Each type of item which may be recorded in the events log is enabled by its own configuration setting,
so that the events file usage can be customized as appropriate for the installation site.
All settings and configuration of the SNMP Access Gateway may be made remotely, using either commands via a
TCP/IP or modem connection, or by SNMP. The SNMP Access Gateway contains a customized management
information base (MIB) which may be used to configure and control the SNMP Access Gateway. Configuration
settings are stored in non-volatile memory for preservation in the event of a power loss.
1.2 -- IMUX 2000 Information
When used with the IMUX 2000 the SNMP Access Gateway connects to the remote port of the IMUX using port 1.
Port 2 is used as a craft interface to both the IMUX and SNMP Access Gateway. A serial cable is supplied for
connection from I/O 1 to the REMOTE port on the IMUX CM3R. The power for the gateway is supplied via the
IMUX motherboard.
The unit is programmed from the factory for the proper setup for most IMUX applications. The only required setup
by the user is to program in the proper IP address for the gateway and the destination IP address for the SNMP traps.
The gateway has been designed to work specifically with version 23 of the IMUX CM3C software or any version of
the CM3R software. When used with any of these versions, RS232 trap messages are created by the IMUX. This
allows the gateway to generate SNMP traps as a result of a message from the IMUX. These traps will contain data
that defines the fault condition on the IMUX. More information on these traps is contained in Application note C.

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Chapter 2 - Installation
SNMP Access Gateway User’s Manual - v1.0 -- 11/99 - Page 3
Chapter 2 - Installation
2.1 - Mounting
The SNMP Access Gateway module is packaged in a plug-in module, for mounting in an IMUX 2000 chassis.
When installing the SNMP Access Gateway module, a location should be selected in the front of the IMUX 2000
chassis which is directly in line with the MA-810 module adapter which is mounted in the back of the chassis. Make
sure the serial port cable can reach the CM3R remote port. This cable should have enough slack so it is not in danger
of being pulled out of place. Some serial port cables, especially hanging cables of any significant length, may have
enough hanging weight to pull the SNMP Access Gateway out of place. In such a case, the serial port cables may
need to be tied in place to provide the SNMP Access Gateway with relief from such strain.
2.2 - Power Input
The SNMP is powered through the IMUX 2000 chassis motherboard. The SNMP Access Gateway uses a maximum
power input of approximately 5 watts, so the maximum current from the IMUX 2000 power supply is about 1 amp.
Figure 2. - SNMP Access Gateway Back Panel View
SNMP SNMP Module MA-810 Module Adapter MA-810
Front Rear
Panel Panel
View View
Figure 2A. – SNMP Access Gateway Module and MA-810 Module Adapter
MA810
LAN
IMUX
REMOTE
1 TP_TX+
2 TP_TX-
3 TP_RX+
4
5
6 TP_RX-
7
8
1 TXD1
2 RXD1
3
4
5 GND
6
RJ-12 PINOUTS
RJ-45 PINOUTS
Figure 2B. – MA-810 Module Adapter Connectors
(LAN Connector)
Ethernet 10BaseT network port
I/O 1
I/O 2
MA810
LAN
IMUX
REMOTE
Use RFL Cable
No. 106016 to
connect to IMUX

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Chapter 2 - Installation
SNMP Access Gateway User’s Manual - v1.0 -- 11/99 - Page 4
2.3 - Serial Ports
The I/O 2 serial port is configured as a DTE port using a male, DB-9 connector. The I/O 1 serial port is configured
as a DTE port using an RJ-12 connector which is similar to that used on the COM ports of an IBM-compatible
personal computer. Figure 3 shows the pin configuration of the I/O 2 port. Figure 2B shows the pin configuration of
the I/O 1 port.
Figure 3. - SNMP Access Gateway DB9 Pin Out
The main pins which must be noted are the received data signal line on pin 2 and the signal ground on pin 5. When
receiving serial data, these are the only two connections which the SNMP Access Gateway needs. However, if pass-
through access to connected serial devices is required, then the transmitted data signal line on pin 3 must be
connected as well. Additionally, some equipment may require an RS-232 high signal on one or more of its signal
lines in order to transmit or accept data. Consult the manual for your other equipment as needed.
The DCE, DB-9 female cable ends which mate with the serial port connectors of the SNMP Access Gateway will
often have a pair of screw-down cable locks. These cable locks should be used to assure a solid connection of the
cable with the SNMP Access Gateway serial port connectors.
2.4 - Ethernet
The ethernet 10BaseT connector is an RJ-45 connector. This connector is the commonly used 10BaseT connector,
which would connect the SNMP Access Gateway to an ethernet hub or switch.