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.

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 5
2.5 - Front Panel Items
The front panel of the SNMP Access Gateway module has two push-buttons and 8 LED indicators representing
status information about the SNMP Access Gateway.
The reset (RST) button (S2) is used to reset the SNMP Access Gateway. After the RST button is held in for about 5
seconds, the SNMP Access Gateway will start sounding its audible alarm. At this point the RST button may be
released. The SNMP Access Gateway will remain in reset while the RST button is pressed, and will begin operation
again once the RST button is released.
The program (PRG) button (S1) is used to silence audible alarms and to enter local command (programming) mode.
When an audible (buzzer) alarm is active, pressing the PRG button clears the alarm, so that the audible alarm is
silenced. If the PRG button is held in for about 3 seconds, the SNMP Access Gateway enters local command
(programming) mode. In this mode serial port I/O 2 operates as a local command port. Either a time-out of no
command for five minutes, an EXIT or BYE command, or a reset will take the SNMP Access Gateway out of local
command mode.
The ethernet status is shown as three LEDs. The yellow Link LED lights whenever an ethernet 10BaseT network
link connection is found. The green Transmit LED lights briefly whenever an ethernet frame is being transmitted.
The green NET LED lights whenever a TCP socket is opened to the unit, whether telnet or FTP. SNMP activity
causes this NET LED to blink once per second. These LEDs can be used to see that a network cable connection is
made, and when some network activity has caused the SNMP Access Gateway to transmit on the network.
Reset Button
Program Button
Network LED
Link LED
Network TX LED
Port 1 RX LED
Port 1 TX LED
Port 2 RX LED
Port 2 TX LED
Power LED
Figure 5. – SNMP Access Gateway Module Layout

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 6
Each RS-232 port has two LEDs associated with it. The left LED is a received data (RXD) LED. The right LED is
a transmitted data (TXD) LED. The TXD LED is normally on and green. The RXD LED is off when no cable is
connected to the serial port, and on when a cable is connected. Normally the RXD LED will be green as well. When
an RS-232 line is idle, the voltage is negative, and the LED shows green. When data is transmitted, the voltage goes
between positive and negative voltages and the LED turns red and green, so when data is transmitted or received on
a serial port the corresponding LED will flicker between red and green, which sometimes makes the LED look
yellow. These LEDs can be used to see that a cable is connected (the LED is lit) and that data is being transmitted or
received (the LEDs flicker between red and green).
The power LED has two uses. Normally the power led is lit constantly, with a quick flash once every ten seconds.
This ‘heartbeat’ signal on the power LED provides a quick indication that the SNMP Access Gateway is operating.
A second mode of use of the power LED is when the SNMP Access Gateway is in local command mode. When the
local serial port is in command mode, the power led flashes on and off at about a 1/2 second on, 1/2 second off rate.

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Chapter 3 - Basic Setup for Operation
SNMP Access Gateway User’s Manual - v1.0 -- 11/99 - Page 7
Chapter 3 - Basic Setup for Operation
3.1 - Network Setup
As with all TCP/IP- or SNMP-based devices, the SNMP Access Gateway requires an IP address to be assigned to
each unit in order to send and receive TCP/IP or SNMP data. The SNMP Access Gateway may operate with either a
statically or dynamically allocated IP address.
When statically allocated, the SNMP Access Gateway must be configured with an IP address, network address mask,
and default router prior to being used on the network. This configuration may be made by a local command port. It
can not be made via a TCP/IP (network) connection, as use of such connections would first require the setting of the
IP address.
The IP address may be dynamically allocated using either BOOTP or DHCP. By default, the SNMP Access
Gateway is configured to use BOOTP or DHCP to dynamically obtain its IP address, network address mask, default
router, etc. When booting, the SNMP Access Gateway transmits a BOOTP/DHCP request. This request is
responded to by any BOOTP or DHCP servers configured to allocate an IP address to the SNMP Access Gateway.
When the SNMP Access Gateway receives its first response from the BOOTP/DHCP request, then the SNMP
Access Gateway either uses the BOOTP reply or engages in a DHCP session to dynamically establish the network
settings of the SNMP Access Gateway.
The SNMP Access Gateway expects to be on a local area network, or to use the default router in the case where an
IP destination is determined to not be a local address. The SNMP Access Gateway uses the destination IP address
and the network address mask to determine if the destination IP address is a local address or not. If so, then the IP
frame is sent to the destination IP address on the local network. If not, then the IP frame is sent via the default
router. If no default router is configured (the address is 0.0.0.0) then no IP frame is sent when the SNMP Access
Gateway determines that the IP frame must be routed and no router exists. If an SNMP management station will be
used which is not on the local network, then the configuration of the default router should be verified. See the use of
the PING command in verification that a route to each management station exists and is usable.
The SNMP Access Gateway provides TCP/IP connections using ports 23 and 2000. Up to three concurrent
connections may be made using these port numbers. When a port address of 23 is used, the telnet character
processing (interpretation of IAC codes, option negotiation, etc.) is performed in both directions of data flow. When
a port address of 2000 is used, no telnet character processing is performed. Other than this difference, the use of port
23 or port 2000 is identical. The SNMP Access Gateway also uses ports 20 and 21 when providing the FTP server
functions.
The SNMP Access Gateway has a configurable list of IP restrictions. This list may be used to restrict IP access to
the SNMP Access Gateway to only certain networks or certain IP addresses, reject connection from certain IP
networks or addresses, etc. This may be used to provide greater security features than a password alone. The IP
restriction table is established using the SETUP command on the NETWORKING menu. If the IP restriction table is
empty, then all networks and IP addresses are allowed to connect to the SNMP Access Gateway. By entering IP
restrictions in the table, then certain networks or IP addresses can be restricted. See the App Note A. Use of IP
Restrictions for more information on the use of IP restrictions. By default, no IP restrictions are established.
3.2 - Local Command Mode
The serial port labeled I/O 2 may be used for local command mode. This mode is entered by either holding in the
PRG button on the front panel for about five seconds, until the power LED starts flashing on at off, or by entering the
(programmable) escape character three times within 3 seconds on the I/O 2 serial port.
When in local command mode, the baud rate and serial port parameters of I/O 2 remain the same.
A user may exit local command mode by four methods. Using the EXIT or BYE command will terminate local
command mode. Waiting five minutes without entering a command will also terminate local command mode.
Additionally, resetting the SNMP Access Gateway with the RST button will also exit local command mode.

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Chapter 3 - Basic Setup for Operation
SNMP Access Gateway User’s Manual - v1.0 -- 11/99 - Page 8
3.3 - Connections
A connection may be made to the SNMP Access Gateway via a network connection. When a connection is made,
the user is provided with a menu from which the desired mode of the connection is established. The user may select
to enter a command processor mode of operation, or may select a pass-through mode of operation. The user selects
the desired mode of operation from the menu, and then the user is prompted for the password for that mode of
access. If the user enters the proper password, then the desired mode of the connection is established.
A connection may be in one of four states. A first state is an idle state, in which no active connection for that
possible connection has been established. In the second state, a user has established a connection and the menu
selection for which type of connection is desired has not yet been made. In the third state the user has entered the
command processor. In the fourth state the user has entered pass-through access mode.
Three concurrent network connections, one local command port connection, plus an FTP server connection may all
exist with the SNMP Access Gateway. SNMP is connectionless, and may be use concurrently with any combination
of connections. The FTP server connection does not affect the other connections or use of command or pass-through
mode.
Only one valid command processor connection may exist at a time. Thus, if I/O 2 is in the local command port
mode, then requests to enter command processor mode via any of the network connections must be denied.
Similarly, if one of the network connections has been established as a command processor connection, then other
network connection cannot access the command processor until it has been made available once again. If a network
connection is in command processor mode, then the local command port mode on I/O 2 is also not allowed until the
command processor is available for re-assignment.
When a user opens a connection to the SNMP Access Gateway the user is provided with a menu from which the
mode of operation is selected, as shown below.
SNMP Access Gateway Model Version 1.00
0. Enter Command Processor
1. Enter Pass-Through to Port 1
2. Enter Pass-Through to Port 2
X. Exit (end connection)
A network connection can be broken by using the ‘X’ selection from the main menu. The network connection is then
placed into the idle state.
A network connection may also be broken from the client side using the disconnect feature of the client software.
Closing of the network connection places that connection into the idle state.
When a connection has been established and is in either the command processor or pass-through mode of operation,
the current operating mode should be terminated and the user should return to the main menu before closing the
connection to the SNMP Access Gateway. Closing a network connection should not result in any extra characters
being transmitted to either the command processor or a pass-through port.

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Chapter 4 - Command Control
SNMP Access Gateway User’s Manual - v1.0 -- 11/99 - Page 9
Chapter 4 - Command Control
4.1 - Command Processor Mode
The command processor may be accessed from a network connection. A user enters command processor mode from
the main menu by selecting the ‘0’ option.
SNMP Access Gateway Model Version 1.00
0. Enter Command Processor
1. Enter Pass-Through to Port 1
2. Enter Pass-Through to Port 2
X. Exit (end connection)
<user enters 0>
Command Processor Password: ---- <user enters password>
Command Password Accepted
Enter Command (Setup, Events, ?, Help or other command)
>
The > is the command prompt. At this point the user may enter any of the commands for the SNMP Access
Gateway. After a command is executed, a new prompt > is provided. The command reminder line is only provided
again if a blank (enter only) line is entered.
If the command processor is currently in use by any of the other connections, then after the user has entered the
command processor password the user gets a message as below:
Command Processor Currently In Use. Access Denied
Thus, only one command processor connection may be made at a time. In this case the user is returned to the main
selection menu.
The EXIT command is used to exit the command processor and return to the main menu. The BYE may also be
used to exit the command processor. However, the BYE command also terminates the connection after the
command processor access is terminated.
If no command is entered for 4 minutes and 30 seconds then a reminder message is sent out, followed by the prompt:
Command Processor Time-out in 30 seconds
>_
If no command is entered within this 30 seconds then the BYE command is executed, terminating the command
processor access and terminating the connection, due to no command in 5 minutes. This automatic logout occurs on
any of the command connections, including all network connections, and the local command port.
Command may be entered in upper, lower or mixed case. Only a few commands are needed to control and manage
the SNMP Access Gateway. The commands available are:
Session control commands
EXIT Exit command processor back to main menu
BYE Exit command processor and close connection
Setup and status commands
? Shows the SNMP Access Gateway status
SETUP Most SNMP Access Gateway setup is done with this command
EVENTS List, clear events file
RELAYS Setup and status of relays
DEFAULT Set settings to defaults

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Chapter 4 - Command Control
SNMP Access Gateway User’s Manual - v1.0 -- 11/99 - Page 10
COLDSTART Clear events file, all settings to default
Other commands
HELP Show list of commands
PING Ping an IP Address for testing
Pseudo-SNMP Commands
GET Get the value of an object with a specific object ID
GETNEXT Get the value of the next object after an object ID
GETX Get the value of the object last retrieved
SET Set the value of an object
WALK Get the value of the object after the last retrieved
4.2 - General Commands
4.2.1 - EXIT
The EXIT command terminates the command processor access and returns the user to the main menu. This
command can be used if the user wants to change the access mode from command processor mode to pass-through
access mode. If the user wants to simply exit the command processor and then terminate the connection, the BYE
command may be used instead to perform both these actions with one command.
4.2.2 - BYE
The BYE command terminates both the command processor access and the connection being used to access the
command processor. The BYE command can be used at the end of a command session to exit the command
processor and terminate the command connection. Alternatively, the EXIT command could be used to exit the
command processor and return to the main menu, and then the ‘X’ main menu command can be used to terminate the
connection which was used for command access.
4.2.3 -? (question mark)
The ? command provides a status display for the SNMP Access Gateway. This display shows the firmware version,
unit ID, current date and time, setup of the serial ports, sensor and relay status, etc. This command can be used to
check the operational status and configuration of the SNMP Access Gateway unit.
SNMP->Link V0.50m #
Unit ID : SNMP->Link
Date : MON 04/06/98 Time : 17:55:38
Modem : 33600 8,N,1
Network : Yes FAFile : Yes
IP Add : 192.168.100.131
MAC Add : 00:10:A3:00:00:09
----------------------------------------------------------
I/O 1 I/O 2
Baud Rate 19200 19200
Parity, etc. 8,N,1 8,N,1
----------------------------------------------------------
Event Records 0
Current Event Status:
Data Alarms ------------------------------
Sensors A1 :Open A2 :Open A3 :Open A4 :Open A5 :Open A6 :Open
Relays A8 :Open A9 :Open
4.2.4 - SETUP
The SETUP command provides a series of menus from which the user may select configuration items for setup and
configuration purposes. These setup menus include setup items for the networking settings, serial port settings,

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Chapter 4 - Command Control
SNMP Access Gateway User’s Manual - v1.0 -- 11/99 - Page 11
password settings, event (alarm) definition settings, alarm action settings, and other settings. See Chapter 5 - Use of
the SETUP Menu for further details of the use of the SETUP command.
4.2.5 - EVENTS
The EVENTS command is used to view the current status of the events (alarms), view the contents of the events log
file, clear contents of the events log file, view the current active alarm actions, acknowledge alarms, and view the
history log of alarm actions. See Chapter 12 - Use of the EVENTS Command for further details of the use of the
EVENTS command.
4.2.6 - DEFAULT
The DEFAULT command resets certain variables and settings to their default values. The network settings and
serial ports settings are not affected by the use of the DEFAULT command. The events log file is not cleared. The
configuration variables and settings affected by the DEFAULT command are:
Setting Value Set To
Store data record events 1 (on)
Store alarm record events 1 (on)
Store command log 1 (on)
Store reset events 1 (on)
Store sensor events 1 (on)
4.2.7 - COLDSTART
The COLDSTART command is used to completely re-initialize the SNMP Access Gateway. All network and other
settings are re-initialized to their default values. The events log file is cleared.
4.2.8 - HELP
The HELP command provides a list of the command available with the SNMP Access Gateway. The display looks
something like this:
? SETUP EVENTS RELAYS EXIT
GET GETNEXT GETX SET
4.2.9 - PING
The PING command executes an ICMP PING test to determine if an IP address is reachable and responding. The
PING command may be used to test the network connectivity of the SNMP Access Gateway. For example, if a
default router is used, the SNMP Access Gateway should be able to PING the default router, which demonstrates
network connectivity and proper network connections.
4.3 - Pseudo-SNMP Commands
The pseudo-SNMP commands are manual commands which can be entered via a dialup or telnet connection and
which may be used with the object IDs developed for SNMP for setting and retrieving the value of SNMP-
manageable objects. These objects may be part of the standard (MIB-II) MIB (as described in RFC 1213), or part of
the custom MIB of the SNMP Access Gateway. The pseudo-SNMP management section of this manual provides
further details and examples of use of the pseudo-SNMP commands.
4.3.1 - GET
The GET command is used with a specific object ID to obtain the value of that object.

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Chapter 4 - Command Control
SNMP Access Gateway User’s Manual - v1.0 -- 11/99 - Page 12
4.3.2 - GETNEXT
The GETNEXT command is used with an object ID, and the value returned is the object ID and value of the object
which follows the object ID included with the GETNEXT command.
4.3.3 - GETX
The GETX command is used without an object ID, and the value returned is that of the last object retrieved by
pseudo-SNMP.
4.3.4 - SET
The SET command is used with an object ID and a value, and the object with the object ID included with the
command is set to the value included with the command.
4.3.5 - WALK
The WALK command is used without an object ID, and may be used to ‘walk’ through the MIB. The WALK
command acts like the GETNEXT command, but uses the object ID of the last object retrieved by pseudo-SNMP as
the included address. Thus, repeated uses of the WALK command allow the user to progress through all items of the
MIB.

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Chapter 5 - Use of the SETUP Menu
SNMP Access Gateway User’s Manual - v1.0 -- 11/99 - Page 13
Chapter 5 - Use of the SETUP Menu
Upon selecting ‘Enter Command Mode’ from the main SNMP Access Gateway menu, the password prompt as
shown below is presented for entry of the Command Mode Password.
Command Processor Password: ----
Command Password Accepted
Upon entry of a valid password the Command Mode Prompt (a ‘greater than’ sign) is shown and commands can be
entered. The first time the command prompt is presented, an additional line is printed (as shown below) to remind
the user of a few basic commands and this prompt can be redisplayed by pressing ENTER on a blank line of the
command prompt. The SETUP command presents the user with a menu of basic setup functions.
>SETUP
Setup Main Menu
A. Networking
B. Serial/Input Ports
C. Passwords
D. Event Definitions
E. Action Definitions
F. System Date/Time
G. Other Settings
Selection?
Many of the above menu items have extensive sub-menus for configuration of all the possible SNMP Access
Gateway settings. The following sections take each of the above menu items and go through the possible options and
selections.
5.1 - Networking
Selecting the Menu Letter of NETWORKING from the Setup Main Menu presents the following submenu for setting
various network related options. The Networking menu appears as follows. Each of the menu items shown below is
discussed in order in this section.
Setup: Networking
A. Network Access Enabled [Y]
B. Get IP Address via [BOOTP/DHCP]
C. IP Address [192.168.100.131]
D. Network Mask [255.255.255.0]
E. Default Router [192.168.100.254]
F. FTP AutoDelete [N]
G. SNMP Manager Setup
H. SNMP Trap Setup
I. SNMP Community Setup
J. IP Address Restrictions
K. Ping Router every 10 Mins [N]
L. PPP Dialout Setup
M. PPP Hosting Setup
5.1.1 - Network Access Enabled
This option is toggled by pressing its Menu Letter. The default for this option is Y but communication via the
ethernet interface can be inhibited by disabling this selection.
5.1.2 - Get IP Address
This option is toggled by pressing its Menu Letter. The default selection is BOOTP/DHCP and the alternate
selection is STATIC. The default selection has the SNMP Access Gateway request and respond to BOOTP/DCHP

Because RFL™ and Hubbell® have a policy of continuous product improvement, we reserve the right to change designs and specifications without notice.
Chapter 5 - Use of the SETUP Menu
SNMP Access Gateway User’s Manual - v1.0 -- 11/99 - Page 14
assignment for the unit IP Address. STATIC implies that the IP address is manually entered and in this mode the
BOOTP/DHCP sequence is not initiated or allowed by the SNMP Access Gateway.
5.1.3 - IP Address
By pressing the Menu Letter of this option a prompt is presented for entry of the Static IP address. Note that after
changing the IP address and exiting the SETUP menu the SNMP Access Gateway will reboot itself and any current
network connections will be terminated (unless Get IP Address Via is set to Bootp/DHCP in which case the IP
address change will not be accepted).
5.1.4 - Network Mask
By pressing the Menu Letter of this option a prompt is presented for entry of the Network Mask.
5.1.5 - Default Router
By pressing the Menu Letter of this option a prompt is presented for entry of the Default Router.
5.1.6 - FTP AutoDelete
This option is toggled by pressing its Menu Letter. FTP AutoDelete controls whether data is automatically deleted
as TCP packets are acknowledged during an FTP transfer of the Events File data. The default is N.
5.1.7 - SNMP Manager Setup
Selecting the Menu Letter of this option presents the following submenu for entry of the IP addresses of up to eight
possible SNMP managers. The addresses entered here will be referred to in other setup and alarm parameters as T1,
T2, etc., to specify which managers traps should be sent to.
Setup: Networking: SNMP Managers
1. Manager 1 [192.168.100.20]
2. Manager 2 [192.168.100.1]
3. Manager 3 []
4. Manager 4 []
5. Manager 5 []
6. Manager 6 []
7. Manager 7 []
8. Manager 8 []
Selection?
5.1.8 - SNMP Trap Setup
Selecting the Menu Letter of this option presents the following submenu for selection of various options relating to
sending SNMP traps.
Setup: Networking: SNMP Traps
A. SNMP Traps Enabled? [Y]
B. SNMP Authentification Failure Traps Enabled? [Y]
C. SNMP Traps Repeat Time (0 for no repeat) [2]
D. Enterprise-Specific Traps Enabled? [Y]
Selection?
A. This selection enables/disables the sending of SNMP Traps in general. The default is ‘Y’.
This selection enables the sending of a trap to all SNMP Managers if an invalid community name is used in an
SNMP GET or SET. The default is ‘N’.
C. This selection enables and selects the interval at which SNMP Traps will repeat being sent until the alarm
generating the trap is explicitly acknowledged. See Chapter 12 - Use of the EVENTS Command for more on
Acknowledging Alarms.