Remote RMM 1400 Version 5 Configuration Guide

Remote RMM-1400
Intelligent Remote Site Management Device

Configuration Guide
Version 5.0x
Part Number 65-000131

2013 by Kentrox, Inc. All rights reserved.
Copyright 2013 by Kentrox, Inc. All Rights Reserved. The material discussed in this publication
is the proprietary property of Kentrox, Inc. Kentrox retains all rights to reproduction and
distribution of this publication.
Kentrox is a registered trademark of Kentrox, Inc. Kentrox, the Kentrox logo, Applied Innovation,
Applied Innovation Inc., the AI logo, and other names are the intellectual property of Kentrox. All
other product names are trademarks or registered trademarks of their respective owners.
Information published here is current as of this documents date of publication, but is subject to
change without notice. You may verify product information by contacting our headquarters.
Kentrox is an Equal Opportunity/Affirmative Action employer.
Kentrox, Inc.
5800 Innovation Dr.
Dublin, Ohio USA 43016-3271
Toll Free: (800) 247-9482
International: +1 (614) 798-2000
Fax: +1 (614) 798-1770
About this Document

This document explains how to install, configure and operate the Remote RMM-1400 intelligent
remote site management device and RMB peripheral units.
Remote RMM-1400 system administrators should have a working knowledge of:
Telecommunications networks, TCP/IP networking, including Telnet and FTP
FTP tools
SNMP
DHCP
IP tables
Remote RMM-1400 Version 5.0xx Configuration Guide

About this Document: Document Conventions
Document Conventions
Table 1 describes the text conventions used in this document.
Table 1 Document Conventions
ii
Convention
Meaning
Screen Text, Menu

Items, System
Prompts, Messages
and Reports
This style indicates Kentrox configuration screen text,

menu items, system prompts, messages and reports.
Static Command Text
In a command statement, this style indicates text that

should be entered exactly as shown at a command line.
Variable Command
Text
In a command statement, this style indicates

user-specified text.
...
In a command statement, ellipses (...) signify that the

preceding parameter can be repeated a number of
times.
[ ]
[ | ]
In a command statement, square brackets indicate an

optional parameter. Two or more parameters in square
brackets with a vertical bar ( | ) between them indicate a
choice of optional parameters.
{ | }
In a command statement, two or more parameters in

braces with a vertical bar ( | ) between them indicate a
choice of required parameters.
Menus and Menu

Commands
This style indicates menu and menu commands. A right

arrow ( > ) separates the menus from the submenus or
menu commands. The right arrow also indicates the
order in which you should click the menus, submenus
and menu commands.
Dialog Boxes, Tabs,

Fields, Check Boxes
and Command Buttons
This style indicates dialog boxes, tabs, fields, check

boxes and command buttons.
Variable Field Text
This style indicates variable information you type in a

dialog box field.
KEYS
Uppercase body text indicates keys on a keyboard,

such as the TAB or ENTER keys. Keys used in
combination are connected with a plus symbol (+).

About this Document: Document Conventions
Table 1 Document Conventions (Continued)

Labels
Note:
Important:
Tip:
CAUTION:
This style designates physical components on Kentrox

products such as jumpers, switches and cable
connectors.
Note messages emphasize or supplement important
points of the main text.
Important messages provide information that is
essential to the completion of a task.
Tip messages provide information that assists users in
operating equipment more effectively.
Caution messages indicate that failure to take a
specified action could result in loss of data and/or harm
to the software or hardware.
iii

About this Document: Cautions and Warnings
Cautions and Warnings

Electrostatic Discharge Caution
CAUTION: Kentrox equipment and its peripherals contain electrostatic sensitive
components. Proper handling, shipping and storage precautions must be
exercised:
You must remove and install cards in a static-free environment. Wear

an antistatic wrist strap that is plugged into the Kentrox equipment so
you are grounded at the same point as the equipment.
Do not remove cards from their antistatic plastic bags until you are
ready to install them into the chassis.
Immediately after you remove a card from the chassis, you must
insert it into its antistatic bag.
When the cards are not in use, keep them in their antistatic plastic
bags.
Do not ship or store cards near strong electrostatic, electromagnetic,

or radioactive fields.
Ground Caution
CAUTION: For Kentrox equipment to operate safely and correctly, there must be a
safety ground strap between the equipment ground bolts and the office
ground.
FCC Warning
The Federal Communications Commission has set limits for emitted radio
interference and Remote RMM-1400 is constructed with this electromagnetic
interference (EMI) limitation in mind. Remote RMM-1400 is classified under FCC
regulations as a Class A device, that is, a device for use in commercial environments
and not in residential areas. This device has been tested and shown to comply with
the following FCC rule: Part 15 Subpart J. Operation of this equipment in a residential
area may cause interference to radio and TV reception, requiring the user to take
whatever steps are necessary to correct the interference.
Information is available from the FCC describing possible corrective actions. To
maintain low EMI levels, we suggest that you use only metal connectors and shielded
cable grounded to the frame.
Specifications are subject to change without notice.
iv

About this Document: Customer Assistance
Customer Assistance
All customers, partners and resellers who have a valid Kentrox Support and Services
Agreement have complete access to the technical support resources.
Kentrox offers technical support from 8 a.m. to 8 p.m. Eastern time, Monday - Friday.
Before you contact Kentrox for assistance, please have the following information
available:
The version of hardware and software you are currently running
The error number and exact wording of any messages that appeared on your
screen
What happened and what you were doing when the problem occurred
How you tried to solve the problem
Kentrox Online Knowledge Base

The Kentrox Online Knowledge Base provides online documents and tools to help
troubleshoot and resolve technical issues with Kentrox products and technologies.
To access the Kentrox Online Knowledge Base, use this URL:
http://kb.kentrox.com
Email Support
Email support is available. You may send email at any time during the day; however,
responses will be only be provided during normal business hours, in accordance with
your Service and Support Agreement.
To contact Technical Support, send email to:
support@kentrox.com
Telephone Support
Pre-sales support
Available, at no charge, to anyone who needs technical assistance in determining
how Kentrox products or solutions can help solve your technical needs.
Phone number: 800-733-5511, option 2
Hours of Operation: 8 a.m. 8 p.m. Eastern Time
Post-sales support
Available to qualified Kentrox customers or partners who have not been able to
resolve their technical issue by using our online services. To qualify for support, you
must have a valid Support and Services Agreement.
v

About this Document: Customer Assistance
Phone number: 800-733-5511, option 3

Normal Business Hours: 8 a.m. to 8 p.m. Eastern time
After-Hours Support: Available to qualified customers who are experiencing serviceaffecting outages that cannot wait until the next business day. To qualify for afterhours support, you must have a valid 24x7 Support and Services Agreement. Call the
number above, option 3 and follow the prompts for after-hours service.
Product Documentation
You can also access and view the most current versions of Kentrox product
documentation on our Web site at:
http://www.kentrox.com
vi
Table of Contents
Chapter 1: Remote RMM-1400 Product Overview .................................1-1
Remote Product Overview ........................................................................................... 1-2
Summary of Remote RMM-1400 Functions ..................................................... 1-2
Remote Features .............................................................................................. 1-3
Remote RMM-1400 Hardware Configuration ............................................................... 1-4
RMB Peripheral Units ................................................................................................... 1-5
RMB-1 Peripheral Unit ..................................................................................... 1-5
RMB-2 Peripheral Unit ..................................................................................... 1-6
Chapter 2: Getting Started .....................................................................2-1

Accessing the CLI Using a Local Connection .............................................................. 2-2
Setting Up the Initial Remote RMM-1400 Configuration .............................................. 2-4
Accessing the CLI Using a Remote Connection .......................................................... 2-7
Accessing the Web Interface ....................................................................................... 2-8
Chapter 3: Configuring Users in the CLI ................................................3-1

Adding a New User ...................................................................................................... 3-2
Enabling the Strong Password Feature ....................................................................... 3-3
Changing a User Password ......................................................................................... 3-4
Deleting a User ............................................................................................................ 3-5
Creating a Custom Profile ............................................................................................ 3-6
Chapter 4: Saving and Applying Configurations ....................................4-1

Saving the Running Configuration ............................................................................... 4-2
Applying Configuration Fragments to an Existing Configuration File ........................... 4-3
Restoring Factory Defaults ........................................................................................... 4-4
Restoring Basic Network Settings ................................................................................ 4-5
Chapter 5: Configuring Network Setup Parameters ...............................5-1

Configuring the Domain Name, DNS Servers and IP Forwarding ............................... 5-2
Configuring an IPv6 Address ....................................................................................... 5-4
Configuring NTP ........................................................................................................... 5-5
Configuring System Clock Settings .............................................................................. 5-7
Configuring Default Settings ............................................................................. 5-7
Configuring Custom System Clock Settings ..................................................... 5-8
TOC-1
Table of Contents
Configuring a Timezone Definition File .......................................................... 5-10

Configuring RAS Settings .......................................................................................... 5-11
Configuring SNMP ..................................................................................................... 5-13
Chapter 6: Understanding Controllers and Interfaces ............................6-1

Controller Descriptions ................................................................................................. 6-2
Bridge Controllers ............................................................................................. 6-2
Ethernet Controllers ......................................................................................... 6-2
OpenVPN Controllers ....................................................................................... 6-2
Serial Controllers .............................................................................................. 6-3
Interface Descriptions .................................................................................................. 6-3
Bridge Interfaces .............................................................................................. 6-3
Ethernet Interfaces ........................................................................................... 6-3
OpenVPN Interfaces ........................................................................................ 6-4
Serial Interfaces ............................................................................................... 6-4
Chapter 7: Configuring Static Routes .....................................................7-1

Adding an IPv4 Static Route to the IP Routing Table .................................................. 7-2
Adding a Default IPv4 Static Route to the IP Routing Table ........................................ 7-3
Adding an IPv6 Static Route to the IP Routing Table .................................................. 7-4
Adding a Default IPv6 Static Route to the IP Routing Table ........................................ 7-5
Chapter 8: Configuring a Wireless Network with Remote RMM-1400 ...8-1

Getting Started ............................................................................................................. 8-2
Wireless Network Overview ............................................................................. 8-2
Required Components ..................................................................................... 8-2
Initial Setup ....................................................................................................... 8-3
Sample Configuration ................................................................................................... 8-4
Configuring the Wireless Modem ................................................................................. 8-5
Configuring the VPN .................................................................................................... 8-8
Chapter 9: Configuring a Site VPN Connection .....................................9-1

Getting Started ............................................................................................................. 9-2
Configuration Requirements ............................................................................. 9-2
Optima .............................................................................................................. 9-2
Redirect ............................................................................................................ 9-2
Configuration Example ................................................................................................. 9-3
Configuring the Site LAN .............................................................................................. 9-5
Configuring the Site VPN ............................................................................................. 9-6
Verifying the VPN Connection from the Client ............................................................. 9-8
Chapter 10: Configuring Actions, Events and Responses ...................10-1

TOC-2
Table of Contents
Overview .................................................................................................................... 10-2

Event Components ..................................................................................................... 10-3
Response Components .............................................................................................. 10-4
Action Components .................................................................................................... 10-5
Configuring an Event, Response and Action ............................................................. 10-6
Chapter 11: Configuring Technician Laptop Access for Remote RMM-1400

11-1
Configuration Overview .............................................................................................. 11-2
Assigning IP Addresses to Technician Laptops ......................................................... 11-4
Configuring IPTables for Network Address Translation ............................................. 11-6
Chapter 12: Configuring Event Correlations ........................................12-1

Overview .................................................................................................................... 12-2
Event Correlation Components ...................................................................... 12-2
Correlation Expression Components ......................................................................... 12-3
Originator Types and States ........................................................................... 12-3
Operators ....................................................................................................... 12-4
Expression Evaluation .................................................................................... 12-4
Configuring a Time Period (Optional) ............................................................. 12-5
Configuring an Event Correlation ............................................................................... 12-6
Chapter 13: Configuring Alarm Entries in the Central Alarm Table ......13-1
Overview .................................................................................................................... 13-2
Alarm Protocol Formats ............................................................................................. 13-3
Raw ................................................................................................................ 13-3
SNMP ............................................................................................................. 13-3
Configuring an Alarm Entry for a Temperature Sensor .............................................. 13-4
Configuring Analog Input Values .................................................................... 13-6
Configuring an Alarm Entry for a Discrete Input ......................................................... 13-9
Configuring an Alarm Entry for a Serial Connection Failure .................................... 13-11
Configuring an Alarm Entry for a TCP Connection that Goes Down ........................ 13-13
Configuring an Alarm Entry for a Telnet Connection that Comes Up ....................... 13-15
Testing Alarm Table Configurations ......................................................................... 13-17
Chapter 14: Configuring Measurements and the Measurement Table 14-1

Overview .................................................................................................................... 14-2
Use with Alarm Table Entries ......................................................................... 14-3
Use with Event Correlations ........................................................................... 14-3
Use with Proxied SNMP NEs ......................................................................... 14-3
Configuring a Measurement Table Entry for a Temperature Sensor ......................... 14-4
TOC-3
Table of Contents
Sample Configuration for SiteBus Temperature Sensor ................................ 14-5

Configuring an Alarm Entry for a Measurement ......................................................... 14-6
Configuring an Event Correlation for a Measurement ................................................ 14-9
Chapter 15: Configuring Mediation Connections .................................15-1

Overview .................................................................................................................... 15-2
Secure Terminal Server Access ................................................................................. 15-3
Terminal Server User Access ......................................................................... 15-3
Configuring a TCP to Asynchronous Serial Connection ............................................ 15-4
Configuring a Telnet to Asynchronous Serial Connection .......................................... 15-6
Configuring a SSH to Asynchronous Serial Connection ............................................ 15-8
Configuring an Asynchronous Serial to Asynchronous Serial Connection ............... 15-10
Configuring an Asynchronous Serial to TCP Connection ........................................ 15-13
Chapter 16: Configuring the DHCP Server ..........................................16-1

DHCP Server Overview ............................................................................................. 16-2
Configuring a DHCP Server ....................................................................................... 16-4
Configuring a DHCP Server Subnet ........................................................................... 16-6
Configuring a Host on a DHCP Server ....................................................................... 16-8
Configuring BOOTP/DHCP Relay .............................................................................. 16-9
Configuring DHCP Client Support ............................................................................ 16-10
Chapter 17: Configuring the Peripheral Management Subsystem .......17-1

Peripheral Management Subsystem Overview .......................................................... 17-2
RMB-1 Peripheral Unit ................................................................................... 17-2
RMB-2 Peripheral Unit ................................................................................... 17-3
Expansion Peripheral Unit Discovery ......................................................................... 17-4
Expansion Peripheral States ...................................................................................... 17-5
Configuring Remote RMM-1400 to Manage an Expansion Peripheral ...................... 17-7
Configuring Discrete I/O Points on an Expansion Peripheral ..................................... 17-9
Configuring Alarms for an Expansion Peripheral ..................................................... 17-11
Configuring SNMP to Operate a Relay Output ........................................................ 17-13
Directly Controlling a Relay Output .......................................................................... 17-15
Configuring SiteBus Devices for an Expansion Peripheral ...................................... 17-16
Disconnecting a Managed Expansion Peripheral .................................................... 17-18
Chapter 18: Configuring the SNMP Proxy ............................................18-1

SNMP Proxy Feature Overview ................................................................................. 18-2
SNMP Proxy Configuration Information ..................................................................... 18-3
SNMP Templates ........................................................................................... 18-3
SNMP NE ....................................................................................................... 18-4
SNMP Manager .............................................................................................. 18-4
TOC-4
Table of Contents
Configuring a Mediation SNMP Event Template ........................................................ 18-5

Configuring a Mediation SNMP Point Template ......................................................... 18-6
Configuring a Mediation SNMP NE Template ............................................................ 18-9
Configuring a Mediation SNMP Measurement Template ......................................... 18-11
Configuring a Mediation SNMP Network Element ................................................... 18-15
Configuration Results ............................................................................................... 18-17
Chapter 19: Configuring Jobs ..............................................................19-1

Job Configuration Overview ....................................................................................... 19-2
Script Package Components .......................................................................... 19-2
Configuring Access to a Central FTP Package Server .............................................. 19-4
Installing a Script Package ......................................................................................... 19-5
Configuring a Job with a Script Package and Script .................................................. 19-7
Configuring a Job with a Job Property ....................................................................... 19-8
Configuring a Job with a Job Task ........................................................................... 19-10
Configuring Job Start Times ..................................................................................... 19-12
Configuring Dynamic Memory for a Job ................................................................... 19-13
Chapter 20: Configuring Modules ........................................................20-1

Module Configuration Overview ................................................................................. 20-2
Installing Modules ...................................................................................................... 20-3
Realizing and Configuring Network Elements ............................................................ 20-4
Configuring an NE Set ............................................................................................... 20-6
Initiating a Control Action ........................................................................................... 20-8
Chapter 21: Using Configuration Wizards ............................................21-1

Configuration Wizard Overview .................................................................................. 21-2
Using the initsetup Wizard ......................................................................................... 21-3
Using the bistate-alarms Wizard ................................................................................ 21-6
Using the serial-port Wizard ....................................................................................... 21-8
Appendix A: Command Identifications .................................................. A-1

Glossary .......................................................................................Glossary-1
TOC-5
Table of Contents
TOC-6
1
Remote RMM-1400 Product
Overview
This chapter provides a high level overview of Remote product features and functionality. In
addition, the hardware architecture and components of the Remote RMM-1400 and RMB
peripheral units are described.
Guide to this Chapter

Remote Product Overview
Remote RMM-1400 Hardware Configuration
RMB Peripheral Units
1-1
Remote RMM-1400 Version 5.0x Configuration Guide

Remote RMM-1400 Product Overview: Remote Product Overview
Remote Product Overview

The Remote product family includes Remote, Remote RMM-1400, Remote RMX3200 and Remote RMM-1200 (previously known as Remote Mini). The Remote
lineup consists of several models that provide various features, as well as a number
of peripheral units that provide additional functionality. In general, the Remote
products are monitoring and control devices that provide IP management connectivity
to remote sites, including environmentally hardened locations.
An integral part of the Kentrox Optima Site Manager solution, the Remote products
reside at your networks remote locations and connect to each element via a wide
variety of interface options. The Remote RMM-1400 performs protocol mediation and
interface conversion, collects alarms and monitoring data and supports bi-directional
management control with the Optima Management Portal via Ethernet or wireless
communication options. Together, Remote and the Optima Management Portal
provide detailed monitoring, remote control and management for virtually all remote
site devices. Figure 1-1 depicts Remote and Optima Management Portal functionality.
Figure 1-1 Remote and Optima Integration for Remote Site Management
Summary of Remote RMM-1400 Functions

Remote RMM-1400 product functions include:
1-2
Compatibility with Optima Management Portal or any standard SNMP-based

management system
Intelligent connectivity to remote network elements
Powerful event-response subsystem
Custom application extension support
Security and network access control

Remote RMM-1400 Product Overview: Remote Product Overview
Remote Features
All Remote products include the following features:
Telnet to asynchronous craft and alarm ports
Discrete and analog input alarm mediation and reporting
Operations Support Systems (OSS) to relay output mediation
Aggregation of performance data
Mediation between OSS equipment and network elements
Scripts designed for performing corrective actions on monitored equipment
1-3

Remote RMM-1400 Product Overview: Remote RMM-1400 Hardware Configuration
Remote RMM-1400 Hardware Configuration

Figure 1-2 shows the Remote RMM-1400 unit, which incorporates the following
connectors and counts:
Four Ethernet ports provide for connections to your network. Ports 1 and 2 can be
used as standard ports and can also provide 48V PoE to 802.3af-compliant
devices.
Four serial ports provide connectivity to any asynchronous device and can be
used as part of the Telnet to asynchronous protocol mediation application. Serial
ports 1 and 2 operate only in RS-232 mode. Serial ports 3 and 4 operate in RS422 mode or RS-485 mode. Serial port 4 can serve as a console port to provide
local asynchronous access for configuration and diagnostics from a laptop or PC.
Tx/Rx and Diversity antenna connections for the optional wireless modem.
Dual 20-60 VDC power inputs with voltage monitoring.
An auxiliary 0-60 VDC voltage monitoring input.
Figure 1-2 Remote RMM-1400
1-4

Remote RMM-1400 Product Overview: RMB Peripheral Units
RMB Peripheral Units

RMB-1 Peripheral Unit
The RMB-1 peripheral unit (shown in Figure 1-3) can be connected to and powered
from one of Remote RMM-1400s PoE-capable Ethernet ports. RMB-1 adds the
following connectors and counts:
64 digital bistate inputs
Four relay outputs
Four current inputs (4-20 mA)
Four voltage inputs (0-10V, positive only)
A four-terminal SiteBus
Four sets of auxiliary terminals, which are not electrically connected to other
RMB-1 I/O terminals
Built-in temperature and humidity sensors
For details on physically connecting to RMB-1 terminals, see the Remote RMM-1400
Installation Guide.
Figure 1-3 RMB-1 Peripheral Unit
1-5

Remote RMM-1400 Product Overview: RMB Peripheral Units

The RMB-2 peripheral unit (shown in Figure 1-4) offers similar capabilities to RMB-1
in a chassis that is sized to be easily mounted in a standard 19-inch, 21-inch, or 23inch rack. RMB-2s digital bistate inputs support both wet and dry contacts, while
RMB-1s digital bistate inputs support dry contacts only.

For technical specifications on RMB-1 and RMB-2 and for details on physically
connecting to RMB terminals, see the Remote RMM-1400 Installation Guide.
1-6
2
Getting Started
This chapter provides information on getting started with Remote RMM-1400. It includes step-bystep scenarios on how to access the CLI, set up the initial configuration and access the Web
interface.

Accessing the CLI Using a Local Connection
Setting Up the Initial Remote RMM-1400 Configuration
Accessing the CLI Using a Remote Connection
Accessing the Web Interface
2-1

Getting Started: Accessing the CLI Using a Local Connection
Accessing the CLI Using a Local Connection

In this scenario, you will:
Connect and log into Remote RMM-1400 locally
(optional) Access help information
Note: When a new Remote RMM-1400 is booted for the first time, it does not have
a configured IP address. As a result, the initial configuration for Remote
RMM-1400 must be performed onsite. For information about configuring an
IP address for remote logins, refer to Setting Up the Initial Remote RMM1400 Configuration on page 2-4.
To access the CLI using a local connection:
1. If you havent already done so, install Kentrox Redirect software on your laptop or
PC. When the installation is complete, Kentrox Redirect and Kentrox Kickstart
icons appear on your desktop.
2. Use a standard CAT5 Ethernet cable (such as Kentrox part number CAB182-10)
to connect the PC or laptop to an Ethernet port on Remote RMM-1400.
3. Launch Kentrox Kickstart. Kickstart discovers the Remote RMM-1400 device, as
shown below.
Note: If the Remote RMM-1400 device is not discovered within one minute,
select Help > About in Kentrox Kickstart, then click the Network
Troubleshooting Guide link for instructions.
4. Click Telnet Terminal (or select Tools > Telnet Terminal). A Telnet window
opens, displaying the Remote RMM-1400 login prompt.
5. At the login prompt, enter your user name:
admin
2-2

Getting Started: Accessing the CLI Using a Local Connection
6. At the password prompt, enter your password:

password
Notes: Passwords are case-sensitive.
admin is the default user name and password is the default password.
Remote RMM-1400 allows you to log in only five times using the default
password. On your sixth login, Remote RMM-1400 will prompt you to
change the default password to a new password.
The main CLI prompt appears.
_
__
| | / /
| |/ /
|
(
| |\ \
|_| \_\
_____ _
_ _______ _____
____ __
__
| ___|| \ | ||___ ___|| _ \ /
\ \ \ / /
| |___ | \ \| |
| |
| (_) || -- | \ \/ /
| ___|| |\ \ |
| |
| _ / | ( ) | ) (
| |___ | | \ |
| |
| | \ \ | -- | / /\ \
|_____||_| \_|
|_|
|_| \_\ \____/ /_/ \_\
RMM-1400
login: admin
Password:
You have 4 grace logins remaining using the default user password.
(Kentrox)>
7. (optional) Access help information:

help
or
?
Note: For more information on using the CLI, refer to section CLI Overview in the
Remote RMM-1400 Command Reference Guide.
2-3

Getting Started: Setting Up the Initial Remote RMM-1400 Configuration
Setting Up the Initial Remote RMM-1400 Configuration

Configure a new user with a supervisor profile
Configure the login banner
Configure a CLI session timeout
Configure a hostname
Configure an IP address for remote logins
Configure a default route (gateway)
Configure the remote access protocol to accept Telnet and FTP connections
To set up the initial Remote RMM-1400 configuration:

1. At the main prompt, add user janedoe and assign the supervisor profile:
config users add janedoe supervisor
2. At the password prompt, enter the password mypassword. For security purposes,
the characters that you enter do not display, but appear as asterisks as shown
below:
**********
3. When prompted to confirm, re-enter the password. Again, the characters that you
enter appear as asterisks:
**********
4. Configure a banner with # as the delimiting character:

config banner #
The following message appears:

Enter the banner text.
End the banner with a # character.
5. Configure the banner with display text This is my banner and the current date
and time:
This is my banner.
\d
\t
#
The prompt re-appears.
2-4

6. Configure the CLI session timeout as 20 minutes:

config timeout 20
7. Configure the host name as Dub:

config hostname Dub
8. Configure IP address.
Note: The Remote RMM-1400 supports IPv4 and IPv6 and provides the ability to
configure both IP protocols at the same time. Refer to Chapter 5: Configuring
Network Setup Parameters for more information on how to configure an IPv6
address.
For this scenario, use IP address 10.40.57.90 and subnet mask 255.255.0.0:
config interface bridge switch ip address 10.40.57.90 255.255.0.0
Note: The bridge switch interface forwards IP packets to the switched Ethernet
ports. You must assign an IP address to allow remote access to Remote
RMM-1400. This IP address is the primary Remote RMM-1400 IP
address.
9. Add a default route with gateway address 10.40.0.1:
config ip route default 10.40.0.1
10. Configure the remote access protocol as telnet-ftp.

config remote-access telnet-ftp enable
Note: Additional remote access protocols supported include SSH-SFTP, HTTP

and HTTPS. Refer to the remote access configuration commands in the
Remote RMM-1400 Command Reference Guide for more information.
2-5

11. (optional) Verify that the user environment has been set up properly:
running-config
The command response similar to the following displays:

(Dub)>running-config
# Product: Remote RMM-1400
# Version: 2.00
# Created: 2010-11-11,12:52:06.0,-05:00
# User:
janedoe
# Bootloader Version: 1.00
config banner #
This is my banner.
\d
\t
#
config hostname Dub
config timeout 20
config users add janedoe supervisor -e$1$KwadE3g5$OzZeYQxk1CqLoyvm8/5pU. -e$1$Kw
adE3g5$OzZeYQxk1CqLoyvm8/5pU.
config interface bridge switch ip address 10.40.57.90/16
(Dub)>
Notes: The preceding example was obtained using a supervisor profile, which
displays the entire configuration; users with management and status
profiles can view limited configuration data.
The -e preceding the encrypted text indicates that the password and
password confirmation have been encrypted.
12. Save the configuration. (Refer to Saving the Running Configuration on page 4-2.)
2-6

Getting Started: Accessing the CLI Using a Remote Connection
Accessing the CLI Using a Remote Connection

In this scenario, you will connect and log into Remote RMM-1400 remotely using
either a Telnet or an SSH connection.
Note: You can also connect remotely to Remote RMM-1400 using the HTTP or
HTTPS protocols.
To access the CLI using a remote connection:
1. Use a PC or laptop with terminal emulation software to connect to Remote RMM1400. For information on operating your particular terminal emulation software,
refer to the documentation provided with the program.
2. Set up your terminal emulation software to connect using either a Telnet or an
SSH connection.
Notes: Individual procedures for making this connection will vary based on the
type of software you are using.
To log into Remote RMM-1400 via SSH, you must execute command
config remote-access ssh-sftp enable
3. Enter the IP address of the Remote RMM-1400 to which you want to connect.
4. At the login prompt, enter your user name:
janedoe
5. At the password prompt, enter your password:

mypassword
Notes: Passwords are case-sensitive.
admin is the default user name and password is the default password.
Remote RMM-1400 lets you log in only five times using the default
password. On your sixth login, Remote RMM-1400 will prompt you to
change the default password to a new password.
2-7

Getting Started: Accessing the Web Interface
Accessing the Web Interface

From the Remote RMM-1400 Web interface, you can perform the following functions:
Enable/disable alarm test mode
Save, restore or erase system configuration
View system log
Manage jobs, packages and scripts
Display system information including version number
Before you can access the Remote RMM-1400 Web interface you must:
Enable the remote access protocol (either HTTP or HTTPS).
Configure the IP address. For more information, refer to Setting Up the Initial
Remote RMM-1400 Configuration on page 2-4.
Important: If using the HTTPS protocol and accessing the Web interface for the first
time, an error page will display indicating that there is a problem with the
website's security certificate. Click Continue to this website to accept
the security certificate and continue with the acceptance options as
prompted.
Enable remote access (either HTTP or HTTPS).
Open a Web browser and access Remote RMM-1400 using a specific IP

address.
To access the Remote RMM-1400 Web interface:

1. Open a Web browser.
2. In the URL address field, enter the Remote RMM-1400 IP address:
http://10.40.57.90
The login window appears.

3. Enter your user name:
janedoe
2-8

4. Enter your password:

mypassword
The Web interface opens to the Home page as shown in Figure 2-1.
5. To display the system information, click the System button on the left side of the
screen, or click the System Info link.
Figure 2-1 Remote RMM-1400 Web Interface Home Page
2-9

2-10
3
Configuring Users in the CLI
This chapter provides step-by-step scenarios on how to configure users.

Adding a New User
Enabling the Strong Password Feature
Changing a User Password
Deleting a User
Creating a Custom Profile
3-1

Configuring Users in the CLI: Adding a New User
Adding a New User

In this scenario, you will add a new user.
To add a new user:
1. At the main prompt, add a new user with user name johndoe and assign profile
status:
config users add johndoe status
2. At the password prompt, enter the new password. Note that the characters that
you enter do not display, but appear as asterisks:
**********
3. When prompted to confirm, enter the same password. Again, the characters that
you enter appear as asterisks:
**********
Notes: User names and passwords are case-sensitive.
Available profiles are status, management, supervisor and

restricted. For more information on these profiles, refer to the Remote
RMM-1400 Command Reference Guide.
4. (optional) Verify that the new user has been added properly:
show users

(Dub)>show users
Login Name
1.
janedoe
2.
johndoe
3.
test
(Dub)>
5. Save the configuration.
3-2
Profile
supervisor
status
supervisor

Configuring Users in the CLI: Enabling the Strong Password Feature
Enabling the Strong Password Feature

The strong password is an optional security feature that enforces additional
validations on new or changed user passwords. The password validations apply to
passwords entered for local users only.
The strong password feature is disabled by default.
Enable the strong password feature.
Change an existing user password.
To enable the strong password feature:

1. At the main prompt, enable the strong password:
config users strong-password enable
2. (optional) Verify that the strong-password feature is enabled:

show users

(Dub)>show users
Strong Password Support: enabled
1.
2.
3.
4.
5.
(Dub)>
Login Name
bob
ebh
jeff
tech
test
Profile
restricted
restricted
status
management
supervisor
3. Change the existing password for user ebh. The following example shows the
additional restrictions of the strong password feature.
(Dub)>config users password ebh
Please enter the new password. ********
Please confirm the new password. ********
[ATHM0029] Password must contain at least one character from three of the
following types: upper-case, lower-case, numerical and special
punctuation.
(Dub)>config users password ebh
Please enter the new password. *********
Please confirm the new password. *********
(Dub)>
3-3

Configuring Users in the CLI: Changing a User Password
Changing a User Password

In this scenario, you will change the password for an existing user.
To change a user password:
1. At the main prompt, change the password for user johndoe to oldguy:
config users password johndoe
The following message displays:

Please enter the new password.
2. Enter the new password:

oldguy
Note: Passwords are case-sensitive and appear as asterisks (*) on the screen
as you type them.
The following message displays:
Please confirm the new password.
3. Re-enter the new password.

oldguy
Note: Passwords always appear in an encrypted format within the system.

There is no way to verify that the user password has been changed.
3-4

Configuring Users in the CLI: Deleting a User
Deleting a User
In this scenario, you will delete a user.
To delete a user:
1. At the main prompt, delete user johndoe:
config users delete johndoe
2. (optional) Verify that the user has been deleted properly:

show users

(Dub)>show users
Login Name
1.
janedoe
2.
test
(Dub)>
Profile
supervisor
supervisor
Note: If the user has been deleted, it will no longer appear in the list of users.
3-5

Configuring Users in the CLI: Creating a Custom Profile
Creating a Custom Profile

Create a custom user profile to include and exclude specific command sets
(IDs) for that profile.
Add a user to the newly created custom profile.
To configure a custom profile:

1. At the main prompt, configure a new profile with the name tech and privilege level
5 (status):
config profile tech priv-lvl 5
2. Configure the base type for the new tech profile as status:
config profile tech copy status
3. Include the command sets /config/controller/eth (config controller ethernet)

and /config/interface/eth (config interface ethernet) in the tech profile:
config profile tech include /config/controller/eth
config profile tech include /config/interface/eth
Note: For a list of valid command identifications, see Appendix A : Command

Identifications.
4. Exclude the command set /show/resource-tracking from the tech profile:
config profile tech exclude /show/resource-tracking
5. Add user ebh to the newly created tech profile with password technician:
config users add ebh tech technician technician
6. (optional) Verify that the custom profile has been configured properly:
show profile tech

(Dub)>show profile
Name:
Base Type:
Privilege Level:
tech
tech
status
5
Command ID
/config/controller/eth
/config/interface/eth
/show/resource-tracking
(Dub)>
7. (Optional) Save the configuration.

3-6
Action
include
include
exclude
4
Saving and Applying
Configurations
This chapter provides information on saving and applying configurations.

Saving the Running Configuration
Applying Configuration Fragments to an Existing Configuration File
Restoring Factory Defaults
Restoring Basic Network Settings
4-1

Saving and Applying Configurations: Saving the Running Configuration
Saving the Running Configuration

In this scenario, you will save the running configuration.
Note: You should save the configuration each time you make a change that you
want to keep. If you reset Remote RMM-1400 without first saving the
configuration, any unsaved changes will be lost.
To save the configuration, copy the running configuration to the startup configuration:
copy running-config startup-config
You can also save the running configuration from the Remote RMM-1400 Web
interface as follows:
1. Click the Configuration button on the left side of the screen or Configuration
from the Main Menu.
2. In the Save section of the screen, click one of the three options and make the
appropriate selection or entry as required.
3. Click the Save link. The screen refreshes and confirms your selection.
See Accessing the Web Interface on page 2-8 for details.
4-2

Saving and Applying Configurations: Applying Configuration Fragments to an Existing Configuration File
Applying Configuration Fragments to an Existing

Configuration File
In this scenario, you will apply a configuration fragment (patch file) to an existing
configuration file. This feature lets you apply a group of configuration commands
without individually entering each one in the CLI.
Patch files are transferred to their own directory on Remote RMM-1400
(/config/patches) with an FTP utility. Once a patch file is in this directory, the
user can show, copy, or erase it using the existing CLI commands.
Note: Patches are separated into supervisor and non-supervisor groups. A user
with a supervisor profile can read, upload and apply supervisor patches
only. Non-supervisor users have a separate set of patches to read, upload
and apply. Remote checks user permissions to ensure appropriate
safeguards for uploading and applying all patch files.
Important: Before you begin this procedure, you must obtain or create a
configuration patch file with a .pat extension. Files without this
extension cannot be saved in the patch file directory. The patch file
cannot have the same name as any configuration file already loaded on
Remote RMM-1400.
To apply a configuration fragment to an existing configuration file:
1. Using an FTP utility, transfer the patch file (patch1.pat) to Remote RMM-1400
directory /config/patches.
2. At the CLI prompt, apply patch file patch1 to file running-config:
config apply-patch patch1 running-config
The individual command lines are displayed as the patch file is applied:
(Dub)>config apply-patch patch1 running-config
config users add manager1 manage test test
config no timeout
config ntp disable
config clock daylight-savings DST
(Dub)>
4-3

Saving and Applying Configurations: Restoring Factory Defaults
Restoring Factory Defaults

In this scenario, you will restore Remote RMM-1400s factory default settings.
Important: When you copy the factory configuration to the running configuration, all
configured settings are removed. You need a console port connection to
re-establish communications with Remote RMM-1400.
To restore the factory default settings, copy the factory configuration to the running
configuration:
copy factory-config running-config
4-4

Saving and Applying Configurations: Restoring Basic Network Settings
Restoring Basic Network Settings

In this scenario, you will restore Remote RMM-1400s basic network settings.
These settings are entered in the initsetup wizard. The running-config file is now
automatically saved to a network-recovery file when the you run the initsetup
wizard and apply the output to the running-config file. If the running configuration
is lost, users can save file network-recovery to file running-config to restore
the initial system configuration.
Note: For more information on the initsetup wizard, refer to Using the initsetup
Wizard on page 21-3.
To restore the basic network settings, copy the network recovery file to the running
configuration:
copy network-recovery running-config
You can also restore the network settings from the Remote Web interface as follows:
1. Click the Configuration button on the left side of the screen or Configuration
from the Main Menu.
2. In the Restore section of the screen, click From backup file:, then select
network-recovery from the drop-down menu.
3. Click the Restore link. The screen refreshes and confirms your selection.
See Accessing the Web Interface on page 2-8 for details.
4-5

Saving and Applying Configurations: Restoring Basic Network Settings
4-6
5
Configuring Network Setup
Parameters
This chapter provides step-by-step scenarios on how to configure network setup parameters for
Remote RMM-1400.

Configuring the Domain Name, DNS Servers and IP Forwarding
Configuring an IPv6 Address
Configuring NTP
Configuring System Clock Settings
Configuring Custom System Clock Settings
Configuring a Timezone Definition File
Configuring RAS Settings
Configuring SNMP
5-1

Configuring Network Setup Parameters: Configuring the Domain Name, DNS Servers and IP Forwarding
Configuring the Domain Name, DNS Servers and IP

Forwarding
Configure a domain name
Configure a primary and secondary DNS server
Enable IP forwarding
To configure the IP settings:

1. At the main prompt, configure domain name www.kentrox.com:
config ip domain-name www.Kentrox.com
2. Configure the primary DNS server with IP address 10.25.2.5:

config ip name-server 10.25.2.5
3. Configure the secondary DNS server with IP address 10.25.2.20:

4. Enable IP forwarding:
config ip forward
5-2

Configuring Network Setup Parameters: Configuring the Domain Name, DNS Servers and IP
Forwarding
5. (optional) Verify that the IP settings have been configured properly:

running-config
The command response appears similar to the following display:

# Version: 2.00
# Created: 2010-11-22,16:46:13.0,+0000
# User:
janedoe
config banner #
This is my banner.
\d
\t
#
config hostname Dub
config ip forward
config timeout 20
(Dub)>
Tip: You can also use the show ip domain-name, show ip forward and show
ip name-server commands to verify the individual IP configurations.
5-3

Configuring Network Setup Parameters: Configuring an IPv6 Address
Configuring an IPv6 Address

In this scenario, you will configure an IPv6 address.
To configure an IPv6 address:
1. Configure interface bridge switch IPv6 address fd10::39:0:0:100/64
config interface bridge switch ipv6 address fd10::39:0:0:100/64
Note: If an IPv6 router is advertising itself on the network and IPv6 is enabled on
the interface, the Remote RMM-1400 may acquire an IPv6 address from
the router in addition to the address configured.
2. (Optional) Verify that the interface bridge switch has been configured properly
with the IPv6 address:
show interfaces bridge
Note: The command response will also contain the link-local IPv6 address.
(Dub)>show interfaces bridge
bridge switch system-name=br_switch status=enabled link-state=up
address=10.39.50.10/16
link-local-address=169.254.166.87/16
ipv6 admin-state=enabled oper-state=enabled
address=fc10::39:240:72ff:fe0e:678d/64
valid=2591993sec preferred=604793sec dynamic
address=fd10::39:0:0:100/64
valid=forever preferred=forever
address=fd::39:0:0:100/64
address=fe80::240:72ff:fe0e:678d/64
(Dub)>
5-4

Configuring Network Setup Parameters: Configuring NTP
Configuring NTP
Configure a primary and secondary NTP server
Configure a minimum and maximum NTP polling interval
Enable NTP
To configure system clock parameters using the common clock time maintained by
the Remote RMM-1400 NTP server:
1. At the main prompt, configure the preferred NTP server with IP address
10.50.18.32:
config ntp server 10.50.18.32
Tip: The first server configured becomes the preferred server and the second
server configured becomes the secondary server, unless indicated
otherwise by entering prefer as in step 2.
2. Configure the second NTP server with IP address 10.50.18.33 and set it as the
preferred server:
config ntp server 10.50.18.33 prefer
3. Define the minimum NTP polling interval as 7 (128 seconds) and maximum NTP
polling interval as 12 (4096 seconds):
config ntp poll-interval 7 12
Tip: The value for the interval is 2 raised to the power of the value entered.
4. Enable NTP on Remote RMM-1400:
config ntp enable
5-5

Configuring Network Setup Parameters: Configuring NTP
5. (optional) Verify that the clock parameters have been configured properly:
running-config

# Version: 2.00
# Created: 2010-11-22,16:46:13.0,+0000
# User:
janedoe
config banner #
This is my banner.
\d
\t
#
config hostname Dub
config ip forward
config ntp enable
config ntp poll-interval 7 12
config ntp server 10.50.18.33 prefer
config ntp server 10.50.18.32
config timeout 20
(Dub)>
Tip: You can also use the show ntp command to verify the NTP configuration.
5-6

Configuring Network Setup Parameters: Configuring System Clock Settings
Configuring System Clock Settings

Remote RMM-1400 lets you configure timezones and daylight savings rules for any
location. Three methods are available for configuring timezone and daylight savings
settings:
Configure a timezone and use the default daylight savings settings. See
Configuring Default Settings for details.
Configure a timezone and define custom daylight savings settings. See

Configuring Custom System Clock Settings for details.
Apply daylight savings rules from a timezone definition file. See Configuring a
Timezone Definition File for details.
Each method has a specific format for configuring a timezone. Depending upon the
format used, the daylight savings command will have different usages.
Configuring Default Settings

Configure the timezone in default mode
Enable daylight savings default parameters
Configure the local time and date
Important: You must disable NTP before you can configure the Remote RMM-1400
system clock locally.
1. At the config clock prompt, configure the timezone as EST with an offset of
-5:00. This puts the daylight savings configuration into default mode:
config clock timezone EST -5:00
2. Enable U.S. daylight savings rules and configure the name that displays when
daylight savings time is in effect:
config clock daylight-savings EDT
3. Configure the local time as 11:22:30 and the local date as 01/20/2010:
config clock local-time 11:22:30 01/20/2010
5-7

show clock

(Dub)>show clock
Wed Jan 20 11:22:30 EDT 2010
Uptime 4 days, 0:17
The timezone is named EST and has an offset of -05:00 GMT.
Daylight savings time is named EDT and using default U.S rules.
Log timestamps are using GMT.
(Dub)>
Tip: In the command response for show clock, the name assigned to indicate
that daylight savings is enabled will appear in the timestamp during daylight
savings. After daylight savings, the name of the configured timezone will
appear in the timestamp.
Configuring Custom System Clock Settings

If you configure the timezone in custom mode, you can use subcommands to
customize the daylight savings parameters.
Configure the timezone in custom mode
Enable daylight savings in custom mode
Configure custom daylight savings time parameters
Important: You must disable NTP before you can configure the Remote RMM-1400
system clock locally.
1. At the config clock prompt, configure the timezone as EST with an offset of
-5:00 and set the daylight savings configuration in the custom mode:
config clock timezone custom EST -5:00
5-8

2. Set the following custom daylight savings time parameters:

(Dub)>config
(Dub) config>clock
(Dub) config clock>daylight-savings
(Dub) config clock daylight-savings
->indicator EDT
->start-month march
->start-day 23
->start-time 01:00:00
->end-month november
->end-time 02:00:00
->save-amount 01:45:00
->
show clock

(Dub)>show
(Dub) show>clock
Fri Feb 12 14:18:24 EST 2010
Uptime 9 days, 17:48
Daylight savings time is named EDT and using custom rules:
Starts on 23 of March at 01:00:00, saving 01:45:00.
Ends on 23 of November at 02:00:00.
Log timestamps are using GMT.
(Dub) show>
5-9

Configuring a Timezone Definition File

You can load and apply daylight savings rules to your system from a timezone
definition file. A timezone definition file is derived from the public domain timezone
database and consists of:
Zone entries, which identify the available timezones with their GMT offsets
and any applicable rules
Rules, which define valid date and time ranges and the amount of time saved.
Install the timezone definition file
Apply daylight savings rules from the timezone definition file
1. To install a timezone definition file, establish an FTP connection into the system
and upload the definition file from your local workstation. A new directory will be
added under the config directory with a single file named timezones.def.
2. At the config clock prompt, apply the installed timezone definition file:
config clock timezone from-file EST
show clock

(Dub)>show
(Dub) show>clock
Wed Jan 20 11:22:30 EDT 2010
Uptime 4 days, 0:17
Daylight savings time is currently active and is saving 01:00.
These settings were loaded from the timezone definition file.
(Dub) show>
5-10

Configuring Network Setup Parameters: Configuring RAS Settings
Configuring RAS Settings

Configure the RAS server type
Configure the RAS server address and settings
Enable RAS accounting
Configure the RAS authorization mode
Configure the number of times Remote RMM-1400 attempts to connect to the

RAS server
Configure the RAS timeout period for a remote authentication attempt
To configure RAS settings:

1. At the main prompt, configure the RAS server type as tacacs+ with fallback
enabled:
config ras shell tacacs+ fallback
Note: A message displays indicating that the shell type configuration will not
take effect until the server is configured.
2. Configure the primary RAS server with the following settings:
IP address 10.50.18.32
Port 100
Secret tserver1
Phases accounting, authentication and authorization:
config ras server 10.50.18.32 port 100

config ras server 10.50.18.32 secret tserver1
config ras server 10.50.18.32 phase accounting authentication
authorization
3. Enable RAS accounting:

config ras accounting enable
4. Configure privilege level RAS authorization:

config ras authorization privilege
Note: RAS accounting and authorization take effect only when TACACS+ is
configured as the server type.
5-11

Configuring Network Setup Parameters: Configuring RAS Settings
5. Configure Remote RMM-1400 to make 5 connection attempts to the RAS server

before failing:
config ras retry 5
6. Configure how long Remote RMM-1400 waits for a response from the RAS server
before falling back on local authentication:
config ras timeout 30
7. (optional) Verify that the remote authentication settings have been configured
properly:
show ras

(Dub)>show ras
Shell RAS option: TACACS+ with Local Fallback
RAS Accounting: enabled
RAS Authorization: privilege
RAS Retry: 5
RAS Timeout: 30
RAS Servers
IP
10.50.18.32
Port
100
(Dub)>
5-12
Secret
tserver1
Phases
authen author account

Configuring Network Setup Parameters: Configuring SNMP
Configuring SNMP
Configure an SNMP version 1 community string
Configure an IPv4 SNMP management station
Configure an IPv6 SNMP management station for version 2 inform requests
Enable authentication trap transfer
Enable the SNMP trap queue
Configure the priority level on a trap OID
Note: This scenario applies only when an SNMP management system is used to
manage Remote RMM-1400.
Note: The following management information bases (MIBs) are available for Remote
RMM-1400:
aiiDefs.mib
aiMediationV2.mib
aiPeriphDiscrete.mib
aiPeripheral.mib
aiSysCfg.mib
aiSysCfgConfig.mib
aiSystem.mib
aiSystemInv.mib
aiRosetta.mib
ktxMeasurement.mib
To access the available MIBs for Remote RMM-1400, go to:

http://www3.kentrox.com/Support/Documentation-Library.aspx.
To configure SNMP:
1. At the main prompt, configure an SNMP version 1 community string named
newadministrator and assign read-only access to objects in the MIB:
config snmp community public v1 readonly
5-13

2. Configure a management station with IPv4 address 10.34.3.84, port number

162 and community string public for sending SNMP traps:
config snmp host 10.34.3.84 162 public v1
3. Configure an IPv6 management station for version 2 inform requests:

config snmp host fd10::39:0:0:200 162 public v2-inform
4. Enable the sending of authentication traps:

config snmp auth-trap enable
5. Enable the SNMP trap queue:

config snmp trap-queue enable
Notes: The queuing state occurs on an SNMP host when a ping fails and traps are
waiting to be sent. The sending state occurs on an SNMP host for all other
conditions related to trap queuing.
Trap queuing is always enabled for v2-inform type hosts, however ping is
not used. Instead, the oldest request in the queue is retried until a response
is received.
6. Assign a high priority for a linkDown trap with OID .1.3.6.1.6.3.1.1.5.3:

config snmp trap-queue priority .1.3.6.1.6.3.1.1.5.3 high
7. (optional) Verify that SNMP has been configured properly:

show snmp summary
The command response similar to the following displays: verify the response
(Dub)>show snmp summary
Authentication traps: enabled
Trap queue: enabled
Communities:
Name
User
administrator
public
V3 Users:
Username
Auth
Hosts:
IP Address
Port Type
10.34.3.84
162
v1
fd10::39:0:0:200
162
v2-inform
Priority:
Trap OID
.1.3.6.1.6.3.1.1.5.3
(Dub)>
5-14
Type
v1
v1
Auth
noauth
noauth
Mode
readwrite
readonly
Priv
Auth
Community/User
noauth public
Queue
sending
noauth public
sending
Priority
high

Configure an SNMP version 3 user
Configure an SNMP v3 community
Configure an SNMP v3 host
1. At the main prompt, configure a v3 user (eric) with md5 authentication

(passphrase: ericauthphrase) and des encryption (passphrase:
ericprivphrase):
config snmp user eric md5 ericauthphrase des ericprivphrase
2. Configure a community (dublinusers)with a v3 user (eric) that has

authentication and encryption (priv) with read and write access (readwrite):
config snmp community dublinusers v3 user eric priv readwrite
3. Configure a host with the ip address of 12.34.56.78, port number 2, user name
eric, community type v3, with authentication (auth) but no encryption:
config snmp host 12.34.56.78 2 eric v3 auth
4. (optional) Verify that SNMP has been configured properly:

show snmp summary

(Dub)>show snmp summary
Authentication traps: enabled
Trap queue: disabled
Communities:
Name
User
Type
administrator
v1
dublinusers
eric
v3
public
v1
v3comm
v3user
v3
V3 Users:
Username
Auth Priv
eric
md5
des
v3user
md5
aes-128
Hosts:
IP Address
Port Type
Auth
Community/User
192.168.7.2
162
v1
noauth administrator
12.34.56.78
2
v3
auth
eric
Priority:
Trap OID
Priority
(Dub)>
Auth
noauth
priv
noauth
priv
Mode
readwrite
readwrite
readonly
readwrite
Queue
sending
sending
5-15

5-16
6
Understanding Controllers and
Interfaces
This chapter provides information about controllers and interfaces and how they operate on
Remote RMM-1400.

Controller Descriptions
Interface Descriptions
6-1

Understanding Controllers and Interfaces: Controller Descriptions
Controller Descriptions
A controller is a software object on Remote RMM-1400 that serves as a destination
for a data bit stream. There are four types of controllers that can be configured in the
Remote RMM-1400 CLI:
Bridge Controllers
Ethernet Controllers
OpenVPN Controllers
Serial Controllers
Bridge Controllers
There is only one bridge controller on Remote RMM-1400. The controller is named
bridge switch because it is a bridge that (by default) includes all four of the Ethernet
switch ports. Controller bridge switch can be configured to include or exclude
individual Ethernet ports.
This and the next section imply that Ethernet controllers are always on the bridge.
Ethernet Controllers
There are four Ethernet controllers on every Remote RMM-1400 model. They
represent the four local switched Ethernet ports and can be included or excluded on
the bridge controller.
The Remote RMM-1400 supports up to 12 optional RME-E8 expansion cards. The
RME-E8 ports are automatically included on the bridge controller with the on-board
Ethernet ports. The RME-E8 ports cannot be excluded from the bridge controller but
they can be disabled.
Each individual controller on the RME-E8 can be enabled or disabled. Disabled ports
are unable to carry traffic preventing unauthorized access to the network. Each
controller is set to enable by default and can be managed separately. The controllers
are created when the RME-E8 peripheral type is configured on a unit and removed
when the type is removed. The controllers have a limited set of configuration options
compared to on-board Ethernet controllers.
OpenVPN Controllers
OpenVPN controllers use the OpenVPN software package to manage VPN
connections. The Remote RMM-1400 OpenVPN controllers can be configured for
either client mode or site-server mode.
An OpenVPN controller in the client mode is used to establish a VPN connection
between a Remote RMM-1400 client and the Connect SCS server. This VPN
connection provides a secure link between remote sites and the protected customer
management network.
6-2

Understanding Controllers and Interfaces: Interface Descriptions
An OpenVPN controller in the site-server mode establishes a VPN connection

between a technician's laptop running the Kentrox Redirect application and a Remote
RMM-1400. This VPN connection provides a secure link for accessing network
elements at a remote site from the technician's laptop.
Serial Controllers
Remote RMM-1400 has four asynchronous serial controllers. In addition, Remote
RMM-1400 can be equipped with an EvDO or UMTS phone module. The phone is
identified as serial modem.
Interface Descriptions
An interface is an entity to which you can route IP packets. Interfaces must be
associated with controllers, which may be underlying physical ports. There are four
types of interfaces that can be configured in the Remote RMM-1400 CLI:
Bridge Interfaces
Ethernet Interfaces
OpenVPN Interfaces
Serial Interfaces
Bridge Interfaces
The bridge interface works in conjunction with the bridge controller switch. It is used
to bridge Ethernet ports and initially includes the four switched Ethernet ports. An IP
address can be assigned to the bridge switch interface, providing a mechanism to
route IP packets to the four switched Ethernet ports on Remote RMM-1400. The IP
address assigned to the bridge interface is Remote RMM-1400s primary IP address.
For more information, refer to Setting Up the Initial Remote RMM-1400 Configuration
on page 2-4.
Ethernet Interfaces
Ethernet interfaces are individually configurable on Remote RMM-1400, allowing you
to set them up with static routes. By default, Ethernet interfaces are part of the bridge
switch. To configure an Ethernet interface with its own IP address, you must first
remove it from the bridge switch with the command:
config controller ethernet port no bridge
Refer to the Remote RMM-1400 Command Reference Guide for details on using this
command.
6-3

Understanding Controllers and Interfaces: Interface Descriptions
OpenVPN Interfaces
Like Ethernet interfaces, OpenVPN interfaces are individually configurable on
Remote RMM-1400. This capability lets users set them up with static routes.
The OpenVPN interface can be associated with two types of OpenVPN controller
modes, client and site-server.
Serial Interfaces
Interfaces are not configurable for Remote RMM-1400s four asynchronous serial
ports. However, an interface can be configured for the wireless phone module
(serial modem).
The modem interface works in conjunction with the serial controller connected to the
wireless modem. By configuring an IP address for the modem interface, IP packets
can be routed through the modem.
6-4
7
Configuring Static Routes
This chapter provides step-by-step scenarios on how to configure static routes in the IP routing
table.

Adding an IPv4 Static Route to the IP Routing Table
Adding a Default IPv4 Static Route to the IP Routing Table
7-1

Configuring Static Routes: Adding an IPv4 Static Route to the IP Routing Table

In this scenario, you will add an IPv4 static route to the IP routing table.
To add an IPv4 static route to the IP routing table:
1. At the main prompt, add an IPv4 static route with destination address
128.14.0.0, subnet mask length 16 and gateway address 10.40.2.18:
config ip route 128.14.0.0/16 10.40.2.18
2. (optional) Verify that the IPv4 static route has been added properly:
show ip route

(Dub)>show ip route
Destination
Gateway
10.40.0.0/16
0.0.0.0
127.0.0.0/8
0.0.0.0
127.0.0.1/32
0.0.0.0
128.14.0.0/16
10.40.2.18
(Dub)>
7-2
Interface
bridge switch
*
lo
bridge switch
Flags
Up
Reject Up
Host Up
Up

Configuring Static Routes: Adding a Default IPv4 Static Route to the IP Routing Table

In this scenario, you will add a default IPv4 static route to the IP routing table.
To add a default IPv4 static route to the IP routing table:
1. At the main prompt, add the default IPv4 static route with gateway address
10.40.0.1:
2. (optional) Verify the default static route has been added properly:
show ip route

(Dub)>show ip route
Destination
0.0.0.0/0
10.40.0.0/16
127.0.0.0/8
127.0.0.1/32
128.14.0.0/16
192.228.36.48/32
(Dub)>
Gateway
10.40.0.1
0.0.0.0
0.0.0.0
0.0.0.0
10.40.2.18
0.0.0.0
Interface
openvpn client
bridge switch
*
lo
bridge switch
serial wan/1
Flags
Up
Up
Reject Up
Up Host
Up
Up Host
7-3

Configuring Static Routes: Adding an IPv6 Static Route to the IP Routing Table

In this scenario, you will add an IPv6 static route to the IP routing table.
To add an IPv6 static route to the IP routing table:
1. At the main prompt, add an IPv6 static route with destination address
fd11:0:0:40::, subnet mask length 64 and gateway address
fd10::39:0:0:0:1:
config ip route-v6 fd11:0:0:40::/64 fd10::39:0:0:1:1
2. (optional) Verify that the IPv6 static route has been added properly:
show ip route

(Dub)>show ip route
Destination
0.0.0.0/0
10.39.0.0/16
127.0.0.0/8
127.0.0.1/32
169.254.0.0/16
fc10:0:0:39::/64
fd10:0:0:39::/64
fd11:0:0:40::/64
fe80::/64
ff00::/8
ff02::fb/128
ff02::1:ffcb:4e8b/128
(Dub)>
7-4
Gateway
10.39.0.1
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
Interface
bridge switch
bridge switch
*
lo
bridge switch
::
::
fd10::39:0:0:1:1
::
::
ff02::fb
ff02::1:ffcb:4e8b
bridge
bridge
bridge
bridge
bridge
bridge
bridge
switch
switch
switch
switch
switch
switch
switch
Flags
Up
Up
Up Reject
Up Host
Up
Up
Up
Up
Up
Up
Up
Up


In this scenario, you will add a default IPv6 static route to the IP routing table.
To add a default IPv6 static route to the IP routing table:
1. At the main prompt, add the default static route with an IPv6 address
fd10::39:0:0:1
config ip route-v6 default fd10::39:0:0:1
2. (optional) Verify the default IPv6 static route has been properly added:
show ip route

(Dub)>show ip route
Destination
0.0.0.0/0
10.39.0.0/16
127.0.0.0/8
127.0.0.1/32
169.254.0.0/16
192.168.101.0/32
192.168.101.0/24
192.168.101.1/32
default
::/0
fc10:0:0:39::/64
fd10::/64
fe80::/64
ff00::/8
ff02::1/128
(Dub)>
Gateway
10.39.0.1
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
127.0.0.1
Interface
bridge switch
bridge switch
*
lo
bridge switch
openvpn site
openvpn site
lo
fe80::e611:5bff:fecb:4e8b
bridge
fd10::39:0:0:1
bridge
::
bridge
::
bridge
::
bridge
::
bridge
ff02::1
bridge
switch
switch
switch
switch
switch
switch
switch
Flags
Up
Up
Up Reject
Up Host
Up
Up Host
Up
Up Host
Up
Up
Up
Up
Up
Up
Up
Note: If an IPv6 router is advertising itself on the network and IPv6 is enabled on
the interface, the Remote RMM-1400 route table may include a route
which uses the routers link-local IPV6 address as the default IPv6 static
route.
7-5

7-6
8
Configuring a Wireless Network
with Remote RMM-1400
This chapter provides information about configuring a wireless network with Remote RMM-1400.

Getting Started
Sample Configuration
Configuring the Wireless Modem
Configuring the VPN
8-1

Configuring a Wireless Network with Remote RMM-1400: Getting Started
Getting Started
This section discusses the following topics:
Wireless Network Overview
Required Components
Initial Setup
Wireless Network Overview

Remote RMM-1400 models can be equipped with EvDO or UMTS modules. These
modules allow users to locate Remote RMM-1400s in areas that do not have
traditional WAN connectivity. Additionally, Remote RMM-1400s located at cell sites do
not require a dedicated T1/E1 channel for management. Full T1/E1 bandwidth is
available for wireless customers and management data can be carried over the
customer network.
A wireless Remote RMM-1400 should appear as if it is a wired extension of the
management network. The goal is to provide two-way, reliable connections with no
restrictions on protocols over the network.
The wireless Remote RMM-1400 communicates with the service providers
management network by delivering alarms to it. The management network tries to
establish connections to Remote RMM-1400 or to network elements connected to the
Remote RMM-1400.
Required Components
When operating in a wireless network, Remote RMM-1400 works in conjunction with
the following Kentrox products:
Connect SCS
Connect SCS acts as the VPN server for Remote RMM-1400. For more information
about Connect SCS, refer to the Connect SCS Configuration Guide.
Director SCD
Director SCD manages VPN clients and servers. It uses Director models and
protocols to identify NEs as VPN clients or servers and manages associations
between the clients and servers. Additionally, Director SCD manages client and
server tokens.
Note: A token is created by the SCD for each VPN client or server. The token must
be installed on the client or server before it can connect to the VPN. The token
is contained in a configuration bundle with a patch file for configuring the VPN.
8-2

Configuring a Wireless Network with Remote RMM-1400: Getting Started
The Client OpenVPN controller on the Remote RMM-1400 uses OpenVPN software
to establish the VPN between Connect SCS and Remote RMM-1400. SSL is used to
manage the VPN connection and encrypted UDP packets are used for data
transmission. Both the management and data traffic are passed as UDP packets on a
single port and are able to travel through the customers firewalls. The customers
external firewall needs to open one port to the Connect SCS for all connected client
network elements.
Keep-alive packets are sent by both the Remote RMM-1400 and Connect SCS to
detect connection failures and to keep an active firewall state.
Initial Setup
Users must set up the following configurations for Remote RMM-1400 to operate in a
wireless network.
To set up the initial configurations:
1. Connect to Remote RMM-1400, log into the CLI and run the initsetup wizard using
command config use-wizard initsetup.
2. Configure the standard configuration parameters (such as users, SNMP,
networking and time).
3. (optional) If the management network is available, then connect to it and run the
Director SCD client application. Once the Director SCD client application is
running, the technician must:
Add Remote RMM-1400 as a new client
Create an association between Remote RMM-1400 and the appropriate

Connect SCS VPN server
Generate a new token for Remote RMM-1400
4. (optional) If management network access is not available, then the technician

must:
Access the SCD client from a location that has network access.
Add the Remote RMM-1400 to be installed
Generate a new token
Save the token as a file on the laptop
Use a local Ethernet connection to the Remote RMM-1400 bridge to transfer

the token via FTP/SFTP to file /config/openvpn/bundle/bundle.cfg on
the Remote RMM-1400.
5. Verify that Remote RMM-1400 is connected to the management network.
8-3

Configuring a Wireless Network with Remote RMM-1400: Sample Configuration
Sample Configuration
Figure 8-1 displays Remote RMM-1400 being used in a wireless network with
Connect SCS, which acts as the VPN server and Director SCD, which manages the
VPN client and server.
Figure 8-1 Wireless Network Example

Sections Configuring the Wireless Modem on page 8-5 and Configuring the VPN on
page 8-8 provide procedures for making the above configurations on
Remote RMM-1400.
8-4

Configuring a Wireless Network with Remote RMM-1400: Configuring the Wireless Modem
Configuring the Wireless Modem

Important: If you use the initsetup wizard to provision the wireless modem, then this
procedure is unnecessary.
Note: This procedure configures a UMTS wireless modem. The same procedure can
be used to configure an EvDO wireless modem with the addition of the
activation step (see note below).
Configure a description for the wireless modem
Configure a connection string for the wireless modem
Assign the wireless modem as a resource
Configure the PPP encapsulation settings
Configure the UMTS wireless modem interface
Activate an EvDO wireless modem.
To configure the UMTS wireless modem settings:

1. Configure description UMTS wireless modem for controller serial modem:
config controller serial modem description UMTS wireless modem
2. Configure the modem serial controllers connection string as AT+CGDCONT=1,

"IP", "i2gold" AT ATD*99***1#:
config controller serial modem connect string AT+CGDCONT=1, "IP",
"i2gold" AT ATD*99***1#
3. Assign controller serial modem as a resource:

config controller serial modem assign
Note: For an EvDO modem only, activate the network name:

diag controller serial modem activate <network name>
8-5

4. Configure the following ppp encapsulation settings:
Remote method pap
Remote username isp@providerx.com and password PROVIDER1
A default route that uses the same subnet as the corresponding interface
Notes: This command overrides the default route assigned to Remote RMM1400 via command config ip route default. PPP configured with
the default route option and command config ip route default are
mutually exclusive. You should not have both configured.
PPP username and password may vary by wireless carrier. Consult your
network provider for the proper identification information.
Disabled LCP requests
config controller serial modem encapsulation ppp

config controller serial modem encapsulation ppp remote method pap
config controller serial modem encapsulation ppp remote identity
isp@providerx.com PROVIDER1
config controller serial modem encapsulation ppp defaultroute
config controller serial modem encapsulation ppp lcp-requests
disable
5. (optional) Verify that the UMTS serial controller has been configured properly:
show controllers serial modem

(Dub)>show controllers serial modem
serial modem status=enabled link-state=up encapsulation=ppp
init-string=AT+CGDCONT=1, "IP", "i2gold" AT ATD*99***1#
resource-state=assigned
signal-strength=fair (-82 dBm)
prl-version=51281 prl-size=5736
Next PRL update in: (unavailable)
description=UMTS wireless modem
ppp defaultroute=true
local-method=none local-identity=
remote-method=pap remote-identity=isp@providerx.com
mru=1520 mtu=1520
lcp-requests=disabled
(Dub)>
6. Enable interface serial modem:

config interface serial modem enable
Note: The IP address of the serial modem interface is assigned automatically by

PPP.
8-6

7. (optional) Verify that the UMTS serial interface has been configured properly:
show interfaces serial modem

(Dub)>show interface serial modem
serial modem name=serial modem system-name=ppp_umts
status=enabled link-state=up
address=167.214.133.56 pointopoint=10.0.0.1
Stats:
Bytes
Packets
Errors
Dropped
Rx
31242388
182608
0
0
Tx
29748523
173100
0
0
(Dub)>
Overrun
0
0
Framing
0
0
8-7

Configuring a Wireless Network with Remote RMM-1400: Configuring the VPN
Configuring the VPN

Important: Most users will use the Director SCD extension to either configure the
VPN, or to send a configuration bundle (containing the VPN
configuration) to Remote RMM-1400. If you used one of these methods
to configure the VPN, then you do not need to do this procedure.
Configure an OpenVPN controller
Configure an OpenVPN interface
To configure the VPN:

1. Enable OpenVPN controller client:
config controller openvpn client enable
2. Configure encryption option aes-256 for OpenVPN controller client:

config controller openvpn client cipher aes-256
Note: The cipher configured for Remote RMM-1400 must match what is
configured on the Connect SCS. If there's a mismatch, the VPN will not be
established.
3. Configure server IP address 205.245.180.48 and port number 1194 for
OpenVPN controller client:
config controller openvpn client server 205.245.180.48 1194
4. (optional) Verify that the OpenVPN controller has been configured properly:
show controllers openvpn

(Dub)>show controllers openvpn
openvpn client system-name=ovpn_client status=enabled link-state=up
hardware-address=00:FF:8C:A5:63:89
default-address=00:FF:8C:A5:63:89
mode=client server=205.245.180.48:1194 cipher=aes-256
vpn-state=connected, Tue Feb 9 15:52:03 EST 2010
cert-subject=/O=AI/CN=VPN-client3
cert-validity-start=Mon Sep 18 04:00:00 GMT 2006
cert-validity-end=Sun Sep 18 04:00:00 GMT 2011
vpn-rx-bytes=10993237 vpn-tx-bytes=11163685
(Dub)>
8-8

5. Configure IP address 192.168.100.80 and subnet mask length 24 for OpenVPN

interface client:
config interface openvpn client ip address 192.168.100.80/24

(Dub)>show interfaces openvpn
openvpn client system-name=ovpn_client status=enabled link-state=up
address=192.168.100.80/24
(Dub)>
8-9

8-10
9
Configuring a Site VPN Connection
This chapter provides a detailed site VPN configuration example. Also included in this chapter
are step-by-step scenarios on how to configure the site LAN, the site VPN and how to establish
the VPN from the client using the Remote RMM-1400.

Getting Started
Configuration Example
Configuring the Site LAN
Configuring the Site VPN
Verifying the VPN Connection from the Client
9-1

Configuring a Site VPN Connection: Getting Started
Getting Started
A major feature of the Remote RMM-1400 is the ability to provide secure remote
access to site network elements.
A site VPN connection can be temporarily established between a client and the
Remote RMM-1400. The Remote RMM-1400 uses the OpenVPN software package
to establish the VPN connection. A VPN connection from the client to the site allows
IP connectivity without the problems of using port based NAT.
A firewall is implemented on the Remote RMM-1400 to restrict the traffic to approved
IP addresses and ports at the site.
Configuration Requirements
The Remote RMM-1400 uses an OpenVPN controller instance configured in the
site-server mode to establish the site VPN connection from the client. An
OpenVPN controller instance in the site-server mode can be used in addition to an
OpenVPN controller instance in the client mode for secure wireless backhaul.
Optima
Optima is a web-based software application that provides complete visibility and
control of network infrastructure sites, such as cell sites, substations and remote
communication huts and all its systems including power, environmental, security and
networking.
Optima provides a Remote RMM-1400 connectivity page that displays detailed
information (protocol, port and cipher) about the site VPN. Redirect uses the site VPN
information passed by Optima to establish the site VPN connection before launching
applications to the site network elements.
Redirect
The Redirect software manages the site VPN connection to the Remote RMM-1400
that enables access to the network elements on the site's private LAN. Redirect
bundles OpenVPN client and supporting Kentrox data (e.g. server authentication
certificates) to perform the site VPN connection.
Redirect supports one VPN connection at a time. To establish a new VPN connection
to a different site, Redirect automatically disconnects the previous connection and
establishes the new connection.
9-2

Configuring a Site VPN Connection: Configuration Example
Configuration Example
Figure 9-1 provides a detailed example of how the site VPN connection between
Client 1 and Remote RMM-1400 is configured.
In the following example, both Client 1 and Remote RMM-1400 are connected to the
Intranet. Redirect on Client 1 uses the IP address on the Remote RMM-1400 on the
Intranet to establish the site VPN connection to access Site NE 1 and Site NE 2.
Figure 9-1 Site VPN Connection between Client 1 and the Remote RMM-1400
The site LAN network in this example is 192.168.111.0/24. The IP address of Site
NE 1 is 192.168.111.100/24 and the IP address of Site NE 2 is
192.168.111.101/24.
The IP address of the site VPN interface on the Remote RMM-1400 is
192.168.101.1/24.
9-3

Configuring a Site VPN Connection: Configuration Example
After the site VPN connection is established between Client 1 and the Remote RMM1400, the client is assigned a point-to-point (site VPN) IP address
192.168.101.6/30.
The peers IP address is 192.168.101.5/30 on the Remote RMM-1400. The routes
to the site LAN network are pushed to Client 1. These routes are listed in the Routes
added box at the top of the diagram. The firewall rules are added based on the allowaccess configurations on the Remote RMM-1400 defined by the user.
The Remote RMM-1400 must be configured with the IP address, protocol and port
number that will be used when making connections from the clients to the site network
elements. All other traffic will be blocked by the firewall on the Remote RMM-1400.
9-4

Configuring a Site VPN Connection: Configuring the Site LAN
Configuring the Site LAN
Note: The type of interface to be used for the site LAN must be decided upon before
a site VPN connection can be configured. In the following scenario, ethernet
port 3 interface is used.
Remove the ethernet controller from bridge group
Configure the IP address for the ethernet controller
Enable IP forwarding
Note: In order to configure the site LAN, first remove the ethernet controller from the
bridge group.
To configure the site LAN:
1. Remove controller ethernet 3 from bridge group:
config controller ethernet 3 no bridge
2. Configure IP address 192.168.111.1/24 for ethernet port 3:

config interface ethernet 3 ip address 192.168.111.1/24
3. Enable IP forwarding:
config ip forward
9-5

Configuring a Site VPN Connection: Configuring the Site VPN
Configuring the Site VPN

Configure the site VPN controller
Configure the interface for client routes
Configure the IP address and ports to access over the site VPN
Verify the configuration
Show the number of clients connected to the site VPN
To configure the site VPN:

1. Configure the site VPN controller with instance name site with default cipher,
keep-alive, port and protocol.
config controller openvpn site mode site-server
2. Configure site interface with IP address 192.168.101.1/24

config interface openvpn site ip address 192.168.101.1/24
3. Configure the routes for the site VPN clients to reach the site LAN:
config controller openvpn site client-route ethernet 3
4. Configure the IP addresses and ports of the site NEs to be accessed over the site
VPN:
config controller openvpn allow-access 192.168.111.100 tcp 20-80
tcp 443 udp 161
config controller openvpn allow-access 192.168.111.101 tcp 20-80
tcp 443 udp 161
Notes: By default, the Remote RMM-1400 blocks all traffic to the site LAN.
9-6
ICMP ping requests and replies are automatically allowed for each IP
address specified.

Configuring a Site VPN Connection: Configuring the Site VPN
5. Verify the configuration:

show controllers openvpn site

(Dub)>show controllers openvpn site
openvpn site system-name=ovpn_site
mode=site-server protocol=udp port=1194 cipher=blowfish-128
keep-alive-inactive=30 keep-alive-disconnect=120
client-route=ethernet 3
vpn-state=connected, Thu Jan 10 14:00:45 EDT 2013
cert-subject=/C=US/ST=OH/O=Kentrox, Inc./CN=openvpn token
cert-validity-start=Wed Oct 10 14:42:32 ex 2012
cert-validity-end=Wed Jan 31 17:13:31 EDT 2029
allow-access=192.168.111.100 tcp 20-80 tcp 443 udp 161
allow-access=192.168.111.101 tcp 20-80 tcp 443 udp 161
(Dub)>
6. Show the number of clients that are currently connected to the site VPN:
show controllers openvpn site client-count

(Dub)>show controllers openvpn site client-count
Number of known clients: 0
Number of authenticated clients: 0
(Dub)>
9-7

Configuring a Site VPN Connection: Verifying the VPN Connection from the Client
Verifying the VPN Connection from the Client

The VPN connection between the client and the Remote RMM-1400 can be
established in two ways. The connection can be made by launching an application
from Optima or by manually opening a connection from Redirect running on the client
computer. In either case, Optima or Redirect must be configured to use the site VPN.
Note: Refer to the Optima and Redirect documentation for additional information on
how to establish VPN connections.
Verify that a client is connected
Verify the number of clients that are connected
Note: A connection from the client to the Remote RMM-1400 using Optima or
Redirect must first be opened before performing the following procedure.
To verify that a client is connected:
show controllers openvpn site clients

(Dub)>show controllers openvpn site clients
>test addr10.39.7.1194 virtual-addr=192.168.101.6
connected=Mon Dec 10 13:27:30 EST 2012
rx-bytes=24617 tx-bytes=32053
(Dub)>
To verify the number of clients that are connected:

show controllers openvpn site client-count

(Dub)>show controllers openvpn site client-count
Number of known clients: 1
Number of authenticated clients: 1
(Dub)>
Note: From the client, site NE 1 (IP address 192.168.111.100) and site NE 2
(192.168.111.101) can be accessed using ping, telnet, ssh, http, https or
snmp.
9-8
10
Configuring Actions, Events and
Responses
This chapter provides information about actions, events and responses.

Overview
Event Components
Response Components
Action Components
Configuring an Event, Response and Action
10-1

Configuring Actions, Events and Responses: Overview
Overview
Actions are rules in Remote RMM-1400 that provide a flexible mechanism for
managing system mediation by letting users associate events and responses. Actions
provide the ability to configure an extensive range of behavior in response to external
or internal events. Actions consist of three components:
EventsSystem occurrences related to changes in Remote RMM-1400s

equipment or the environment.
ResponsesBehaviors that are executed in response to system events.
ActionsRules that create associations between responses and events.
During normal Remote RMM-1400 operation, internal event messages are generated.
A subsystem called the Action Manager keeps a list of actions and monitors all the
event messages. When an event message matches an event configured in an action,
the Action Manager generates the corresponding response message. Each
responder in the system monitors the response messages and executes responses
directed to it.
Note: Several commands exist in the Remote RMM-1400 CLI that display diagnostic
information related to actions: show actions, show events, show
responses, show audit actions, show audit events, show audit
responses and diag mmdisplay. For more information about display and
diagnostic commands, refer to the Remote RMM-1400 Command Reference
Guide.
10-2

Configuring Actions, Events and Responses: Event Components
Event Components
Figure 10-1 illustrates a sample event configuration:
event name
originator
event type
config event MyEvent content input 1/1 close
Figure 10-1 Example of the Event Command

Event declarations consist of the following elements:
An event name, which is a user-defined name for the event.
An event originator, which is a system component that generates the event.
An event type, which is a system occurrence that signifies the event. Options for
the event type vary based on the event originator.
Note: For more information about event configuration commands and parameters,
refer to the Remote RMM-1400 Command Reference Guide.
10-3

Configuring Actions, Events and Responses: Response Components
Response Components
Figure 10-2 illustrates a sample response configuration:
response name
responder
response type
config response MyResponse content output 1/3 close
Figure 10-2 Example of the Response Command

Response declarations consist of the following elements:
A response name, which is a user-defined name for the response.
A responder, which is a system component that processes the response.
A response type, which defines what the response does when the associated
event occurs. Options for the response type vary based on the responder.
Note: For more information about response configuration commands and

parameters, refer to the Remote RMM-1400 Command Reference Guide.
10-4

Configuring Actions, Events and Responses: Action Components
Action Components
Figure 10-3 illustrates a sample action configuration:
action name
event name
response name
config action MyAction event MyEvent response MyResponse
Figure 10-3 Example of the Action Command

Action declarations consist of the following elements:
An action name, which is a user-defined name for the action.
An event name, which is a previously user-defined name of an event.
The response name, which is a previously user-defined name of a response.
Note: For more information about this command, refer to the Remote RMM-1400
Command Reference Guide.
10-5

Configuring Actions, Events and Responses: Configuring an Event, Response and Action
Configuring an Event, Response and Action

Configure an event that occurs when the temperature on RMB goes above a
high threshold
Configure a response that opens a relay output point
Configure an action that associates the event with the response.
To configure the event, response and action:

1. At the main prompt, configure event High_Temp with event originator analog
1/temperature and event type high:
config event High_Temp content analog 1/temperature high
Note: For information about specific event originators and event types, refer to
command config event content in the Remote RMM-1400 Command
Reference Guide.
2. Configure response Output1_3 with responder output 1/3 and response type
open:
config response Output1_3 content output 1/3 open
Note: For information about specific responders and response types, refer to the
response configuration commands in the Remote RMM-1400 Command
Reference Guide.
3. Configure action Chassis_Temp_High with event High_Temp and response
Output1_3:
config action Chassis_Temp_High event High_Temp response Output1_3
10-6

4. (optional) Verify that the action has been configured properly:

show actions Chassis_Temp_High

(Dub)>show actions Chassis_Temp_High
Action Name
: Chassis_Temp_High
Action Description
:
Event
Event
Event
Event
Name
Description
Originator
Type
: High_Temp
:
: analog 1/temperature
: high
Response Name
: Output1_3
Response Description :
Response Responder
: output 1/3
Response Type
: open
Response Parameters :
No parameters configured for this response.
(Dub)>
10-7

10-8
11
Configuring Technician Laptop
Access for Remote RMM-1400
This chapter provides information on configuring Remote RMM-1400 network access to locallyconnected technician laptops.

Configuration Overview
Assigning IP Addresses to Technician Laptops
Configuring IPTables for Network Address Translation
11-1
Draft - For internal review only. Do not distribute.

Configuring Technician Laptop Access for Remote RMM-1400: Configuration Overview
Configuration Overview
Figure 11-1 displays what happens when a technicians laptop accesses the network
by connecting to Remote RMM-1400.
64.152.3.27
(Public Address)
IP Network
Server
IPTables rules allow laptops
on the private network to
send packets to the WAN with
Remote RMM-1400s public address.
(184.155.22.36)
DHCP Server
IPTables
The DHCP Server

assigns a private IP
address to the
technician laptop.
Remote RMM-1400
10.10.10.12 (Private Address)

Technician Laptop
Figure 11-1 Technician Laptop Access via Remote RMM-1400
11-2

Configuring Technician Laptop Access for Remote RMM-1400: Configuration Overview
When the technicians laptop is connected to one of the Ethernet ports on Remote
RMM-1400, the DHCP server automatically assigns an IP address to the laptop. IP
addresses that may be assigned to the technicians laptop are configured using
DHCP server configuration commands in the Remote RMM-1400 CLI. For more
information on configuring the DHCP server, refer to section Assigning IP Addresses
to Technician Laptops on page 11-4.
IPTables is configured for Network Address Translation (NAT) to allow multiple
laptops to use private IP addresses on the local network and a single public IP
address on the WAN. For more information on configuring IPTables and NAT, refer to
section Configuring IPTables for Network Address Translation on page 11-6.
Tip: If you have available public IP addresses, DHCP can assign them to connected
laptops, which lets you skip the IPTables configuration.
11-3

Configuring Technician Laptop Access for Remote RMM-1400: Assigning IP Addresses to Technician
Laptops
Assigning IP Addresses to Technician Laptops

Remote RMM-1400 uses the DHCP server to assign IP addresses to network
devices. CLI commands are entered to specify valid ranges of IP addresses that
may be assigned.
Important: For a laptop to access the network through Remote RMM-1400 using
this procedure, the laptop must be configured to obtain its IP address
automatically.
Enable the DHCP server
Configure a secondary bridge switch IP address
Configure the DHCP server interface
Configure the DHCP server subnet
Configure the DHCP server router
Configure the DHCP server IP address range
Configure the default time that a network device can keep a DHCP
server-assigned IP address
Configure the maximum time that a network device can keep a DHCP
server-assigned IP address.
To configure the DHCP server to assign IP addresses to technician laptops:

1. Enable the DHCP server:
config dhcp-server enable
2. Configure secondary bridge switch IP address 10.10.10.1/24:

config interface bridge switch ip address 10.10.10.1/24 secondary
Important: This step is important because an interface must exist on the same
subnet that the DHCP server will be servicing. If this interface does
not exist, the DHCP server will not start up.
3. Configure the DHCP server interface as bridge switch:
config dhcp-server interface bridge switch
4. Configure the DHCP server subnet as 10.10.10.0/24:

config dhcp-server subnet 10.10.10.0/24
5. Configure the DHCP server router as 10.10.10.1:

config dhcp-server subnet 10.10.10.0/24 router 10.10.10.1
11-4

Configuring Technician Laptop Access for Remote RMM-1400: Assigning IP Addresses to Technician
Laptops
6. Configure the DHCP server IP address range as 10.10.10.7 to 10.10.10.12:

config dhcp-server subnet 10.10.10.0/24 range 10.10.10.7
10.10.10.12
Note: When the DHCP server assigns IP addresses to network devices, it

automatically starts with the highest value IP address in the range.
7. Configure the default time that a network device can keep an IP address assigned
by the DHCP server as 4500 seconds:
config dhcp-server subnet 10.10.10.0/24 default-lease 4500
8. Configure the maximum time that a network device can keep an IP address
assigned by the DHCP server as 6000 seconds:
config dhcp-server subnet 10.10.10.0/24 max-lease 6000
9. (optional) Verify that the DHCP server has been configured properly:
show dhcp-server

(Dub)>show dhcp-server
Admin State:
enabled
Broadcast:
disabled
Authority:
disabled
Config file:
Note: User specified configuration files will override configured
DHCP server settings.
Interfaces:
bridge switch
Subnets:
10.10.10.0/24 range=10.10.10.7/10.10.10.12 router=10.10.10.1
default-lease=4500 max-lease=6000
DNS:
Hosts:
test MAC=00:00:00:00:00:00 IP=0.0.0.0
(Dub)>
11-5

Configuring Technician Laptop Access for Remote RMM-1400: Configuring IPTables for Network
Address Translation
Configuring IPTables for Network Address Translation

IPTables rules must be configured to enable network address translation for laptops
on the private network. Without NAT, devices with private addresses cannot send
packets to devices outside the LAN.
Note: For more information on IPTables, refer to an IPTables man page (version
1.2.7a).
Flush all Iptables
Configure a rule in the PREROUTING chain that accepts all packets from a
source subnet that go to a specified destination address
Set the default action for the PREROUTING chain to drop all packets
Configure a rule in the POSTROUTING chain that masquerades all TCP

packets from a specified source subnet.
To configure IPTables for address translation:

1. Flush all IPTables:
config iptables -t nat -F
config iptables -t filter -F
config iptables -t mangle -F
2. Configure a rule in the PREROUTING chain in the mangle table that accepts all
packets from source subnet 10.10.10.0/24 and to destination address
184.155.22.36:
config iptables -t mangle -A PREROUTING -s 10.10.10.0/24 -d
184.155.22.36 -j ACCEPT
3. Set the default action for the PREROUTING chain to drop all packets:
config iptables t mangle P PREROUTING DROP
CAUTION: If you are connected to Remote RMM-1400 via a Telnet connection

and you set the default action to drop all packets without first
configuring a rule to accept packets between your workstation and
Remote RMM-1400 (as in step 2), your connection to Remote RMM1400 will be lost.
11-6

Address Translation
4. Configure a rule in the POSTROUTING chain that masquerades all tcp packets from
source subnet 10.10.10.0/24:
config iptables -t nat -A POSTROUTING -s 10.10.10.0/24 -p tcp -j
MASQUERADE
5. (optional) Verify that the IPTables commands have been configured properly:
show iptables configuration

(Dub)>show iptables configuration
Table nat
------------------------------------------------------Chain PREROUTING (policy ACCEPT)
Chain POSTROUTING (policy ACCEPT)
-s 10.10.10.0/24 -p tcp -j MASQUERADE
Chain OUTPUT (policy ACCEPT)
Table filter
------------------------------------------------------Chain INPUT (policy ACCEPT)
-i lo -j ACCEPT
Chain FORWARD (policy ACCEPT)
-d 127.0.0.0/8 -j ACCEPT
Table mangle
------------------------------------------------------Chain PREROUTING (policy DROP)
-i lo -j ACCEPT
-s 10.10.10.0/24 -d 184.155.22.36 -j ACCEPT
Chain INPUT (policy ACCEPT)
-i lo -j ACCEPT
Chain FORWARD (policy ACCEPT)
-d 127.0.0.0/8 -j ACCEPT
Chain POSTROUTING (policy ACCEPT)
-d 127.0.0.0/8 -j ACCEPT
(Dub)>
11-7

Address Translation
11-8
12
Configuring Event Correlations
This chapter provides information about configuring event correlations.

Overview
Correlation Expression Components
Configuring an Event Correlation
12-1

Configuring Event Correlations: Overview
Overview
Event correlation is the ability to identify a unique condition by comparing the states of
multiple events and aggregating into a single event.
The goals of Remote RMM-1400 event correlation are to:
Report the correlated condition to a network management system
Include the correlated condition as an individual component in other event

correlations (if defined)
Perform an automatic response (if defined)
Event Correlation Components

Event correlation is represented by an event originator named correlation and the
following components:
12-2
A description of the event correlation
A boolean-like expression to define the event correlation
Properties controlling how the expression is evaluated. The evaluation of the

correlation expression results in a true or false state for the event correlation.

Configuring Event Correlations: Correlation Expression Components
Correlation Expression Components

The following illustrates a basic expression configuration:
Term
OriginatorType Instance State
Operator
and
Term
OriginatorType Instance State
Figure 12-1 Correlation Expression Example

A Term in a correlation expression is used to test the current state of an originator.
The Term consists collectively of the following elements:
OriginatorType, which is one of the Remote RMM-1400 event originator types.

The type can also be correlation, which refers to other event correlations.
Instance value, which is one of the valid instances for the specified type, for
example, 1/1, 2.
State, which is a valid state for the originator. In the case of a measurement, the
state may be a relational operator and a numeric value (for example, < 48 or
> 95).
Originator Types and States

Table 12-1 lists the types of originators that are valid for the correlation expressions,
the associated events that are valid as a state comparison and those originators that
can be used as multi-originators. Multi-originators must have either an any or an all
operator before the multiple instance token. See Operators on page 12-4 for details.
Table 12-1 Event Originator Types and States
Originator Type
Valid State Events
Multi Support
analog
high, in-band, inputsaturated, loss of signal, low
yes - point ranges
input
close, open
yes - point ranges
output
close, open
yes - point ranges
correlation
false, true
no
measurement
high, in-band, inputsaturated, loss of signal,

low, <, <=, =, >=, >, !=
yes - point ranges
12-3

Examples
Examples of these components combined are shown below:
analog 1/1 high
correlation examplecorr false
measurement ExtTemp1 > 90
Operators
The valid operators that can be used in a correlation expression are listed in the
following table, along with possible usages and example results for each.
Table 12-2 Operators and Usage
Operator
Usage
Example Result
and
expression analog 1/4

high and output 1/2
open
When both expressions are true, the

evaluation is true.
or
expression analog 1/4

high or measurement
extTemp > 110
When either expression is true, the

evaluation is true.
not
expression not analog

1/4 in-band
When negating a true expression, the

evaluation is false.
all
expression all output

1/1-4 close
When all expressions are true, the

evaluation is true.
any
expression any 3 input

1/1-4 close
When at least three (3) expressions are

true, the evaluation is true. If no number is
entered after any, the default value is 1.
Expression Evaluation
In an expression, the precedence order for evaluation is as follows:
1. Term
2. not
3. and
4. or
If a Term is a nested expression, it is fully evaluated as the evaluation of the Term, as
is typical with most programming languages. Nested expressions in parentheses are
supported, allowing complex expressions to be contained in a single correlation
expression. The use of parentheses can improve the readability of expressions which
mix and, not and or operators.
12-4

Example Expressions
The examples below show various forms of Terms in nested expressions.
all input
1/1 low )
not ( any
false )
all input
all input
1/1-4 open and ( analog 1/1 loss-of-signal or analog

3 analog 1/1-4 in-band and correlation myCorrelation
1/1,3,5,7 open and correlation myCorrelation true
1,2/1-4 open
Configuring a Time Period (Optional)

You can optionally configure a time period (duration) during which a correlation
expression must remain in a true or false state before the correlation itself changes
state to match the expression.
For example, you may want to configure a scenario where an alarm is generated
when a door is open for an extended period of time rather than a brief open/close
situation.
12-5

Configuring Event Correlations: Configuring an Event Correlation
Configuring an Event Correlation

Configure a correlation expression for two open door alarm events
Configure the time (duration) for which the expression must remain true or false
before the correlation matches the expressions state
Create two alarm table entries for the open door events.
To configure an event correlation for two open door alarm events:

1. At the main prompt, configure an event correlation named DoorAlarms with a
description of Correlation for open door alarms:
config correlation DoorAlarms description Correlation for open
door alarms
2. Configure the true duration time in the expression for 900 seconds, meaning an
alarm will be sent if the door is open for 15 minutes; set the false duration time to
0 seconds (immediate), meaning an alarm will be sent immediately upon closure:
config correlation DoorAlarms duration 900 0
3. Configure the correlation expression for the two doors as input 1/1 open and
input 1/2 open:
config correlation DoorAlarms expression input 1/1 open and input
1/2 open

show correlation DoorAlarms

(Dub)>show correlation DoorAlarms
Name
: DoorAlarms
Expression
: input 1/1 open and input 1/2 open
True Duration : 900
False Duration : 0
Evaluation
: false and false = false
Value
: false
Description
: Correlation for open door alarms
(Dub)>
12-6

To configure the alarm table entry for the open door correlation:
1. At the main prompt, configure the alarm entry name dooropen:
config alarm-entry dooropen
2. Configure the alarm entry dooropen with the following parameters:
event originator correlation DoorAlarms
event type true

event severity major
alarm message Door is open
config alarm-entry dooropen event correlation DoorAlarms true

major Door is open
event originator correlation DoorAlarms
event type false

event severity normal
alarm message Door is closed
config alarm-entry dooropen event correlation DoorAlarms false

normal Door is closed
Note: For an example of configuring an event correlation using a measurement, see

section Configuring an Event Correlation for a Measurement in Chapter 14:
Configuring Measurements and the Measurement Table.
12-7

12-8
13
Configuring Alarm Entries in the
Central Alarm Table
This chapter provides an overview of the central alarm table along with step-by-step scenarios
for configuring and using alarm entries in the central alarm table.

Overview
Alarm Protocol Formats
Configuring an Alarm Entry for a Temperature Sensor
Configuring an Alarm Entry for a Discrete Input
Configuring an Alarm Entry for a Serial Connection Failure
Configuring an Alarm Entry for a TCP Connection that Goes Down
Configuring an Alarm Entry for a Telnet Connection that Comes Up
Testing Alarm Table Configurations
13-1

Configuring Alarm Entries in the Central Alarm Table: Overview
Overview
The central alarm table collects and communicates the state of all alarms reported by
Remote RMM-1400. It is a table of alarm entries that contains information for each
attainable severity level and has the following features:
Event/alarm associationsThe central alarm table lets users associate events

with alarm responses in a single command. This is easier than configuring events
and alarm responses using the action subsystem, which requires three
commands for associating events with alarm responses.
Alarm NaggingAlarm nagging causes an alarm entry to send an alarm message

in all formats enabled for that entry at a specified time interval. For information
about configuring the alarm nagging interval, refer to section Configuring an
Alarm Entry for a Temperature Sensor on page 13-4.
Alarm reporting in a variety of formatsThe central alarm table can report alarm
statuses in raw format, or in SNMP format. For more information on these
formats, refer to section Alarm Protocol Formats on page 13-3.
For information about commands that configure central alarm table entries and data,
refer to the Remote RMM-1400 Command Reference Guide.
13-2

Configuring Alarm Entries in the Central Alarm Table: Alarm Protocol Formats
Alarm Protocol Formats

The central alarm table supports two alarm protocol formats:
Raw
SNMP
You can enable and disable each alarm protocol format independently of the other
(meaning that you can have both formats enabled).
Raw
The central alarm table supports raw alarm output that can be used for alarm formats
that are not directly supported by Remote RMM-1400. A script or application can take
the alarm information from the raw output and translate it into any type of alarm
message.
SNMP
The central alarm table supports SNMP through alarm traps in the aiMediationV2.mib.
Alarm traps are sent to all enabled SNMP management hosts. In order to receive
alarm traps, at least one SNMP management host must be configured.
13-3

Configuring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Temperature
Sensor
Configuring an Alarm Entry for a Temperature Sensor

Configure an alarm entry description
Configure a category name
Configure SNMP trap support
Configure the interval at which the alarm will send its state
Configure a network element name
Configure the alarm actions that signal when the detected temperature has
exceeded a maximum threshold, passed below a minimum threshold, or
entered into an acceptable range.
Important: This scenario does not show how to configure the analog input that is
associated with the alarm entry. For information on configuring analog
inputs, refer to command config discrete analog in the Remote
To configure the temperature sensor alarm entry:
1. At the main prompt, configure description Temperature sensor:
config alarm-entry tempSensor description Temperature sensor
2. Configure category name envAlms:

config alarm-entry tempSensor category envAlms
3. Enable SNMP trap support:

config alarm-entry tempSensor trap enable
4. Configure the SNMP trap priority level to high:

config alarm-entry tempSensor trap priority high
5. Configure the interval at which the alarm entry sends its state information to 5
seconds when the alarm state is critical:
config alarm-entry tempSensor nagging 5 critical
6. Configure network element name sensorUnit:

config alarm-entry tempSensor ne-name sensorUnit
13-4

Sensor
7. Configure an event for alarm entry tempSensor with the following settings:
Event originator analog 1/1
Event trigger high
Event severity level critical
Alarm event message Temperature above safe threshold - followed by

the actual high value for the alarm entry.
config alarm-entry tempSensor event analog 1/1 high critical

Temperature above safe threshold - $(value)
Note: Keyword $(value) is replaced with the current value of the analog input. If the
event associated with the analog input does not contain an event message
value, no substitution takes place.
8. Configure a second event for alarm entry tempSensor with the following settings:
Important: All events configured for an alarm entry must have the same event
originator.
Event trigger low
Event severity level minor
Alarm event message Temperature below low threshold - followed by

the actual low value for the alarm entry.
config alarm-entry tempSensor event analog 1/1 low minor

Temperature below low threshold - $(value)
9. Configure a third event for alarm entry tempSensor with the following settings:
Event trigger in-band
Event severity level normal
Alarm event message Temperature in normal range.
config alarm-entry tempSensor event analog 1/1 in-band normal

Temperature in normal range
13-5

Sensor
10. (optional) Verify that the alarm entry has been configured properly:
show alarm-entries name tempSensor

(Dub)>show alarm-entries name tempSensor
Name
- tempSensor
State
- normal
Current Message Description
- Temperature sensor
Nagging Interval - 5
Nagging Level
- critical
Trap
- enabled
Trap Priority
- high
Raw
- enabled
Category
- envAlms
NE Name
- TempSensor
Originator
- input 1/1
Alarm Actions:
Severity
Trigger
Message
-----------------------------------------------------------------critical
high
Temperature above safe thresho
minor
low
Temperature below low threshol
normal
in-band
Temperature in normal range
(Dub)>
Configuring Analog Input Values

The values reported by Remote analog inputs often show rapid fluctuations as
compared to the values read from a digital multi-meter. This is by design and does not
indicate a problem with the Remote. Digital multi-meters utilize sophisticated internal
circuitry to minimize these inherent fluctuations when displaying measurements to the
user. To compensate for these variations, Remote provides two analog input features:
analog averaging and analog adjustment.
13-6

Sensor
Analog Averaging
Users can specify the level at which Remote will average measurement values. The
goal is for a reasonable, steady-state value to measure consistently with both the
Remote and an external meter. Summarized in Table 13-1 are the valid averaging
values with typical examples of when they may be applied to a measurement.
Table 13-1 Analog Averaging Values
Measurement
Example
Value
Description
high
Provides the most averaging, but provides

slower response to rapid changes in the
measured value. This setting is typically
used with environmental or other sensors
which measure conditions that do not
change quickly.
Temperature/Humidity
medium
The typical value used when the unscaled

value fluctuates by +/- .01 V or mA. This
setting is recommended for measurements
which are not expected to change
instantaneously, but may change
significantly over a short period of time (for
example, 1 minute).
Fuel Level
low
Provides faster response to value fluctuation

while still providing a small level of
averaging. This setting is recommended for
measurements which may change very
rapidly during alarm conditions, but which
will still benefit from the smoothing feature
during steady-state operation.
Battery Voltage
none
No averaging will be applied and raw values

will be reported. This is the default value.
The following example shows how to configure discrete analog 1/1 with medium
level averaging:
config discrete analog 1/1 averaging medium
Analog Adjustment
A fixed adjustment can be applied to an analog input value to raise or lower the value
to match a reference value. By adjusting both the minimum and maximum sensor
readings by the same amount, the offset can be applied without changing the scaling
factor of the analog input. Note that these values affect only the current conditions.
13-7

Sensor
For example, to configure a voltage sensor for 0-10V scaling to 0-100 gallons of fuel,
an offset of +7 gallons can be applied by scaling the 0-10V to 7-107 gallons. This
scenario is configured as follows:
config discrete analog 1/1 minimum 0 7
config discrete analog 1/1 maximum 10 107
13-8

Configuring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Discrete Input
Configuring an Alarm Entry for a Discrete Input

Configure SNMP alarm protocol support
Configure an alarm action that occurs when a light turns off, which opens an
input
Configure an alarm action that occurs when a light turns on, which closes an
input.
Important: This scenario does not show how to configure the discrete input that is
associated with the alarm entry. For information on configuring
discrete inputs, refer to command config discrete input in the
Remote RMM-1400 Command Reference Guide.
To configure the open input alarm entry:
1. At the main prompt, configure description Light switch:
config alarm-entry input1_1 description Light Switch
2. Enable trap alarm protocol support:

config alarm-entry input1_1 trap enable
3. Configure an event for alarm entry input1_1 with the following settings:
Event originator input 1/1
Event trigger open
Event severity level major
Alarm event message Light off.
config alarm-entry input1_1 event input 1/1 open major Light off
4. Configure an event for alarm entry input1_1 with the following settings:
Event originator input 1/1
Event trigger close
Alarm event message Light on.
config alarm-entry input1_1 event input 1/1 close major Light on
13-9

Configuring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Discrete Input
show alarm-entries name input1_1

(Dub)>show alarm-entries name input1_1
Name
- input1_1
State
- normal
Nagging Level
- major
Trap
- enabled
Trap Priority
- disabled
Raw
- disabled
Category
NE Name
Originator
- input 1/1
Alarm Actions:
Severity
Trigger
Message
-----------------------------------------------------------------major
open
Light off
major
close
Light on
(Dub)>
13-10

Configuring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Serial Connection
Failure
Configuring an Alarm Entry for a Serial Connection Failure

Configure an alarm action that signals that a serial connection failure has
occurred.
Important: This scenario does not show how to configure the serial port that is
associated with the alarm entry. For information on configuring serial
ports, refer to command config controller serial in the Remote
To configure an alarm entry for a serial connection failure:
1. At the main prompt, configure description Serial connection failure:
config alarm-entry SerConnFail description Serial connection
failure
2. Enable SNMP trap alarm protocol support:

config alarm-entry SerConnFail trap enable
3. Configure an event for alarm entry SerConnFail with the following settings:
Event originator serial 3
Event trigger conn-failed
Alarm event message The serial connection has failed.
config alarm-entry SerConnFail event serial 3 conn-failed major

The serial connection has failed
13-11

Configuring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Serial Connection
Failure
show alarm-entries name SerConnFail

(Dub)>show alarm-entries name SerConnFail
Name
- SerConnFail
State
- normal
- Serial connection failure
Nagging Level
- major
Trap
- enabled
Trap Priority
- disabled
Raw
- disabled
Category
NE Name
Originator
- serial 3
Alarm Actions:
Severity
Trigger
Message
-----------------------------------------------------------------major
conn-failed
The serial connection has fail
(Dub)>
13-12

Configuring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a TCP Connection
that Goes Down
Configuring an Alarm Entry for a TCP Connection that

Goes Down
Configure an alarm action that signals that a TCP connection has gone down.
To configure an alarm entry for a TCP connection that goes down:

1. At the main prompt, configure description TCP connection down:
config alarm-entry TCPConnDown description TCP connection down

config alarm-entry TCPConnDown trap enable
3. Configure an event for alarm entry TCPConnDown with the following settings:
Event originator tcp 192.168.0.12:5001
Event trigger conn-down
Alarm event message TCP connection down.
config alarm-entry TCPConnDown event tcp 192.168.0.12:5001 conndown major TCP connection down
13-13

Configuring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a TCP Connection
that Goes Down
show alarm-entries name TCPConnDown

(Dub)>show alarm-entries name TCPConnDown
Name
- TCPConnDown
State
- normal
- TCP connection down
Nagging Level
- major
Trap
- enabled
Trap Priority
- disabled
Raw
- disabled
Category
NE Name
Originator
- tcp 192.168.0.12:5001
Alarm Actions:
Severity
Trigger
Message
-----------------------------------------------------------------major
conn-down
TCP connection down
(Dub)>
13-14

Configuring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Telnet Connection
that Comes Up
Configuring an Alarm Entry for a Telnet Connection that

Comes Up
Configure an alarm action that signals that a Telnet connection has come up.
To configure the Telnet connection up alarm entry:

1. At the main prompt, configure description Telnet connection up:
config alarm-entry TelnetConnUp description Telnet connection up

config alarm-entry TelnetConnUp trap enable
3. Configure an event for alarm entry TelnetConnUp with the following settings:
Event originator telnet 192.168.0.4:6001
Event trigger conn-up
Alarm event message Telnet connection now up.
config alarm-entry TelnetConnUp event telnet 192.168.0.4:6001

conn-up normal Telnet connection now up
Tip: This same scenario can be followed to configure a connection up alarm entry for
SSH. Simply substitute SSH for Telnet.
13-15

Configuring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Telnet Connection
that Comes Up
show alarm-entries name TelnetConnUp

(Dub)>show alarm-entries name TelnetConnUp
Name
- TelnetConnUp
State
- normal
- Telnet connection up
Nagging Level
- major
Trap
- enabled
Trap Priority
- disabled
Raw
- disabled
Category
NE Name
Originator
- telnet 192.168.0.4:6001
Alarm Actions:
Severity
Trigger
Message
-----------------------------------------------------------------normal
conn-up
Telnet connection now up
(Dub)>
13-16

Configuring Alarm Entries in the Central Alarm Table: Testing Alarm Table Configurations
Testing Alarm Table Configurations

After you configure alarm table entries, you can simulate test traps from the alarm
table to test your alarm table configurations before actual alarm traps are sent. Test
mode traps are sent to the management station.
Enable the alarm table test mode.
Simulate a test trap from Remote for a specific alarm entry.
To simulate a test trap from the Remote alarm table:

1. At the main prompt, enable the alarm table test mode using the default timeout
period (10 minutes):
diag test mode enable
2. Simulate a test trap for alarm entry GPS_Failure:

diag test alarm-entry GPS_Failure
3. (optional) Verify that the GPS_Failure alarm entry is being simulated:

show test alarm-entries
This command response displays the alarm entries that are currently being
simulated (in test mode).
(Dub)>show
(Dub) show>test
(Dub) show test> alarm-entries
Name
State
Current alarm message
---------------------------------------------------------------------Explosive_Gas
normal
Explosive Gas Not Detected
GPS_Failure
normal
GPS Normal
Generator_OilPressur normal
--NewTest
normal
--Toxic_Gas
normal
--(Dub) show test
13-17

Configuring Alarm Entries in the Central Alarm Table: Testing Alarm Table Configurations
13-18
14
Configuring Measurements and the
Measurement Table
This chapter provides an overview of Remote RMM-1400s measurement table along with stepby-step scenarios for configuring a measurement table entry, an alarm entry for a measurement
and an event correlation for a measurement.

Overview
Configuring a Measurement Table Entry for a Temperature Sensor
Configuring an Alarm Entry for a Measurement
Configuring an Event Correlation for a Measurement
14-1

Configuring Measurements and the Measurement Table: Overview
Overview
In addition to its central alarm table, Remote RMM-1400 provides a measurement
table that collects analog measurement values and reports these values to a central
management station, such as Optima. These measurement values can be sourced
from an analog input monitored by Remote RMM-1400, from a script running on
Remote RMM-1400 that monitors an attached network element, or via SNMP from a
network element that is monitored by SNMP proxy. The Remote RMM-1400
measurement table stores a 24-hour history of collected values.
Figure 14-1 Remote RMM-1400 Measurement Table

Each entry in the measurement table is identified by a name and contains an analog
value, units of measure (such as V, %, deg C, or deg F), the originator of the data
(such as analog 1/1 or script jobname_measurementname), the NE name, an
optional description and category and the maximum, minimum and average
measured values over the reporting interval.
14-2

Configuring Measurements and the Measurement Table: Overview
You can configure a measurement table entry such that the state of the measurement
will change based on the current value of the measurement. These states include:
Loss-of-signalThe value has passed below the minimum measurable threshold
LowThe value has passed below the minimum value that is considered normal
In-bandThe value falls between the minimum normal value and the maximum
normal value
HighThe value has passed above the maximum value that is considered normal
Input-saturatedThe value has passed above the maximum measurable

threshold
OfflineThe originator of the value has gone offline and is not reporting a value
Use with Alarm Table Entries

Measurement table entries can be used in connection with Remote RMM-1400s
alarm table. You can set up alarm entries with different events that are triggered in
response to fluctuations in the current state of a measurement.
See section Configuring an Alarm Entry for a Measurement for an example.
Use with Event Correlations

You can create event correlations to be used with measurement table entries. The
example in section Configuring an Event Correlation for a Measurement correlates a
temperature measurement exceeding a specified value with an input being open to
create an alarm for fire danger.
For more information on configuring correlations, see Chapter 12: Configuring Event
Correlations.
Use with Proxied SNMP NEs

See Chapter 18: Configuring the SNMP Proxy for information on how to use the
measurement table with proxied SNMP NEs. Relevant topics include Configuring a
Mediation SNMP Measurement Template and Configuring a Mediation SNMP
Network Element.
14-3

Configuring Measurements and the Measurement Table: Configuring a Measurement Table Entry for a
Temperature Sensor
Configuring a Measurement Table Entry for a Temperature

Sensor
Configure a measurement table entry with name and description
Configure a category name
Configure measurement units
Configure a network element name
Configure the normal (in-band), maximum and minimum values
Configure the originator for a measurement table entry
Enable the measurement table entry
To configure a measurement table entry for an external temperature sensor:

1. At the main prompt, configure measurement table entry ExtTemp1 with
description External temperature sensor:
config meas-table entry ExtTemp1 description External temperature
sensor

config meas-table entry ExtTemp1 category envAlms
3. Configure measurement units Degrees F:

config meas-table entry ExtTemp1 units Degrees F

config meas-table entry ExtTemp1 ne-name sensorUnit
5. Configure the normal range for measurement values:

config meas-table entry ExtTemp1 band 65 80
6. Configure the maximum measurable value:

config meas-table entry ExtTemp1 maximum 130
7. Configure the minimum measurable value:

config meas-table entry ExtTemp1 minimum -30
8. Configure the originator for this measurement:

config meas-table entry ExtTemp1 originator analog 1/4
9. Enable the measurement table entry:

config meas-table entry ExtTemp1 enable
14-4

Configuring Measurements and the Measurement Table: Configuring a Measurement Table Entry for a
Temperature Sensor
10. (optional) Verify that the measurement table entry has been configured properly:
show meas-table entries ExtTemp1

(Dub)>show meas-table entries ExtTemp1
Name
- ExtTemp1 (static)
State
- offline
Originator
- analog 1/4
Description
- External temperature sensor
NE Name
- sensorUnit
Category
- envAlms
Report Interval - 0
Low-Band
- 65.
High-Band
- 80.
Hysteresis
- 0.
Max-Limit
- 130.
Min-Limit
- -30.
Units
- Degrees F
Current Value
Interval Value
Interval Minimum
Interval Maximum
Interval Average
(Dub)>
76
76
76
76
76
Sample Configuration for SiteBus Temperature Sensor

The following is a sample configuration for a measurement table entry for the SiteBus
temperature sensor used with RMB-1 and RMB-2. Adjust the sensor name, NE name
and other values to fit your specific implementation.
config meas-table entry TempSensor1
config meas-table entry TempSensor1 category Temp Sensor
config meas-table entry TempSensor1 description One Wire Temp
Sensor
config meas-table entry TempSensor1 originator sitebus
Temp/temperatureF
config meas-table entry TempSensor1 report-interval 15
config meas-table entry TempSensor1 band 20 110
config meas-table entry TempSensor1 hysteresis 2
config meas-table entry TempSensor1 maximum 150
config meas-table entry TempSensor1 minimum -10
config meas-table entry TempSensor1 ne-name Test_RMM1400
config meas-table entry TempSensor1 units degrees Fahrenheit
14-5

Configuring Measurements and the Measurement Table: Configuring an Alarm Entry for a Measurement
Configuring an Alarm Entry for a Measurement

Configure an alarm entry description and category
Configure the network element name associated with this alarm entry
Configure SNMP trap alarm protocol support
Configure different alarm actions that occur when a measurement is normal,

low, high, falls below the measurable range, or rises above the measurable
range
To configure the measurement alarm entry:

1. At the main prompt, configure alarm entry ExtTemp with description External
temperature alarm:
config alarm-entry ExtTemp description External temperature alarm

config alarm-entry ExtTemp category envAlms

config alarm-entry ExtTemp ne-name sensorUnit
4. Enable SNMP trap alarm protocol support with priority normal:

config alarm-entry ExtTemp trap enable
config alarm-entry ExtTemp trap priority normal
5. Configure an event for alarm entry ExtTemp with the following settings:
Event originator measurement ExtTemp1
Event trigger high
Alarm event message $(value).
Note: Keyword $(value) is replaced with the current measurement value.

config alarm-entry ExtTemp event measurement ExtTemp1 high major
$(value)
14-6

Event trigger low
config alarm-entry ExtTemp event measurement ExtTemp1 low major

$(value)
Event trigger in-band
config alarm-entry ExtTemp event measurement ExtTemp1 in-band

normal $(value)
Event trigger input-saturated
Alarm event message Input saturated.
config alarm-entry ExtTemp event measurement ExtTemp1 inputsaturated critical Input saturated
Event trigger loss-of-signal
Alarm event message Signal loss.
config alarm-entry ExtTemp event measurement ExtTemp1 loss-ofsignal critical Signal loss
14-7

show alarm-entries name ExtTemp

(Dub)>show alarm-entries name ExtTemp
Name
- ExtTemp
State
- normal
- Exterior temperature alarm
Nagging Level
- major
Trap
- enabled
Trap Priority
- normal
Raw
- disabled
Category
- envAlms
NE Name
- sensorUnit
Originator
- measurement ExtTemp1
Alarm Actions:
Severity
Trigger
Message
-----------------------------------------------------------------major
high
$(value)
major
low
$(value)
normal
in-band
$(value)
critical
input-saturated
Input saturated
critical
loss-of-signal
Signal loss
(Dub)>
14-8

Configuring Measurements and the Measurement Table: Configuring an Event Correlation for a
Measurement
Configuring an Event Correlation for a Measurement

Configure a correlation expression for fire danger, when a measurement from a

temperature sensor exceeds a specified value while an alarm event from a
smoke detector (connected to input 1/3) exists
Configure the time (duration) for which the expression must remain true or false
before the correlation matches the expressions state
Create two alarm table entries for the correlation.
To configure an event correlation for fire danger:

1. At the main prompt, configure an event correlation named FireDanger with
description Correlation for temperature and smoke:
config correlation FireDanger description Correlation for
temperature and smoke
2. Configure the correlation expression for the value of measurement ExtTemp1 as

greater than or equal to 90 and the smoke detector (input 1/3) as open:
config correlation FireDanger expression measurement ExtTemp1 >=
90 and input 1/3 open
3. Configure the true duration time in the expression for 120 seconds, meaning an
alarm will be sent if these conditions persist for two minutes; set the false duration
time to 0 seconds (immediate), meaning an alarm will be sent immediately when
either condition no longer exists:
config correlation FireDanger duration 90 0

show correlations FireDanger

(Dub)>show correlations FireDanger
Name
: FireDanger
Expression
: measurement ExtTemp1 >= 90 and input 1/3 open
True Duration : 90
False Duration : 0
Evaluation
: false and false = false
Value
: false
Description
: Correlation for temperature and smoke
(Dub)>
14-9

Configuring Measurements and the Measurement Table: Configuring an Event Correlation for a
Measurement
To configure the alarm table entry for the fire danger correlation:
1. At the main prompt, configure the alarm entry name dooropen:
config alarm-entry fireDanger
event originator correlation FireDanger
event type true

event severity critical
alarm message Fire alarm exists
config alarm-entry fireDanger event correlation FireDanger true

critical Fire alarm exists
3. Configure the alarm entry doorclosed with the following parameters:
event originator correlation FireDanger
event type false

event severity normal
alarm message Fire alarm is cleared
config alarm-entry dooropen event correlation FireDanger false

normal Fire alarm is cleared
14-10
15
Configuring Mediation Connections
This chapter provides information about how to configure mediation connections, events,
responses and actions.

Overview
Secure Terminal Server Access
Configuring a TCP to Asynchronous Serial Connection
Configuring a Telnet to Asynchronous Serial Connection
Configuring a SSH to Asynchronous Serial Connection
Configuring an Asynchronous Serial to Asynchronous Serial Connection
Configuring an Asynchronous Serial to TCP Connection
15-1

Configuring Mediation Connections: Overview
Overview
Mediation connections allow you to connect different protocols. Examples of
mediation connections include:
Asynchronous to TCP connections and TCP to asynchronous connections
Asynchronous to asynchronous connections
A mediation connection can be configured to have multiple hops; however, the

connection must have a source endpoint and a destination endpoint at a minimum. In
addition, the connection can have data filters in the middle, for example, the Telnet
filter acts as a Telnet server proxy.
Mediation connections are established through the configuration of events, responses
and actions.
15-2

Configuring Mediation Connections: Secure Terminal Server Access
Secure Terminal Server Access

The secure terminal server access feature provides a layer of encryption and
authentication, creating a secure connection from a workstation to Remote RMM1400 to access a connected NE. The connection from Remote RMM-1400 to the NEs
is not secure.
The Secure Shell Protocol (SSH) is used to provide the secure connection and is
suitable for both an interactive user session via a client like PuTTY or through any
available SSH client library.
The Redirect application provides SSH as an option for a virtual serial ports protocol
in addition to TCP and Telnet protocols. Redirect also allows for user authentication
options to be configured.
Figure 15-1 shows the secure connection using SSH and a non-secure connection
using Telnet.
Figure 15-1 Secure and Non-Secure Connections
Terminal Server User Access

A built-in user profile called restricted is available for users, which allows terminal
server access but no CLI or FTP access. At the CLI, a user with the restricted
profile will only be able to log out; no files will be available for retrieval via FTP.
15-3

Configuring Mediation Connections: Configuring a TCP to Asynchronous Serial Connection
Configuring a TCP to Asynchronous Serial Connection

In this scenario, you will configure a mediation connection between a TCP port and
an asynchronous serial controller. You will set up an action, event and response
that cause the TCP port and controller to connect.
To configure a TCP connection to an asynchronous connection:
1. Configure event tcp40010 with originator tcp 10.40.57.5:40010 and event type
incoming-connection:
config event tcp40010 content tcp 10.40.57.5:40010 incomingconnection
Note: The TCP originator IP address is optional if it is the same as the Remote
RMM-1400 bridge switch interface IP address.
2. Configure response tcp40010ToSerial2 with responder tcp 10.40.57.5:40010
and response type dest serial 2:
config response tcp40010ToSerial2 content tcp 10.40.57.5:40010
connect dest serial 2
3. Configure action tcpToSerial2 with event tcp40010 and response

tcp40010ToSerial2:
config action tcpToSerial2 event tcp40010 response
tcp40010ToSerial2
4. (optional) Verify that the TCP to asynchronous connection has been configured
properly:
show actions tcpToSerial2

(Dub)>show actions tcpToSerial2
Action Name
: tcpToSerial2
Action Description
:
Event
Event
Event
Event
Name
Description
Originator
Type
Response
Response
Response
Response
Response
(Dub)>
15-4
Name
Description
Responder
Type
Parameters
: tcp40010
:
: tcp 10.40.57.5:40010
: incoming-connection
: tcp40010ToSerial2
:
: tcp 10.40.57.5:40010
: connect
:
dest=serial 2

Configuring Mediation Connections: Configuring a TCP to Asynchronous Serial Connection
5. Configure controller serial 2 to connect and disconnect as DCD goes active and
inactive:
config controller serial 2 connect mode dcd
config controller serial 2 disconnect mode dcd
6. Configure the application mode as destination:

config controller serial 2 application destination
7. (optional) Verify that a connection is established:

show connections

(Dub)>show connections
tcp 10.40.57.5:40010:4 -> serial 2
(Dub)>
Note: The 4 that comes after the TCP port number is an internal reference
number generated by Remote RMM-1400.
15-5

Configuring Mediation Connections: Configuring a Telnet to Asynchronous Serial Connection
Configuring a Telnet to Asynchronous Serial Connection

In this scenario, you will configure a mediation connection between a Telnet port
and an asynchronous serial controller. You will set up an action, event and
response that cause the Telnet port and controller to connect.
To configure a Telnet to asynchronous serial connection:
1. Configure event IncTelnetConn to signal that an incoming telnet connection
request has been received on port 60002 at IP address 10.40.57.5:
config event IncTelnetConn content telnet 10.40.57.5:60002
incoming-connection
2. Configure response telnet60002ToSerial3 to connect Telnet port 60002 at IP

address 10.40.57.5 to destination serial 3:
config response telnet60002ToSerial3 content telnet
10.40.57.5:60002 connect dest serial 3
3. Configure response telnet60002ToSerial3 to cause a Telnet connection from

port 60002 at IP address 10.40.57.5 to operate in binary mode:
config response telnet60002ToSerial3 content telnet
10.40.57.5:60002 connect options -b
4. Configure action telnetToSerial to associate event IncTelnetConn with

response telnet60002ToSerial3:
config action telnetToSerial event IncTelnetConn response
telnet60002ToSerial3
15-6

Configuring Mediation Connections: Configuring a Telnet to Asynchronous Serial Connection
5. (optional) Verify that the Telnet to asynchronous connection has been configured
properly:
show actions telnetToSerial

(Dub)>show actions telnetToSerial
Action Name
: telnetToSerial
Action Description
:
Event
Event
Event
Event
Name
Description
Originator
Type
Response
Response
Response
Response
Response
Name
Description
Responder
Type
Parameters
: IncTelnetConn
:
: telnet 10.40.57.5:60002
: telnet60002toSerial3
:
: telnet 10.40.57.5:60002
: connect
:
dest=serial 3
options=-b
(Dub)>
inactive:


show connections

telnet 10.40.57.5:60002:4 -> serial 3
(Dub)>
15-7

Configuring Mediation Connections: Configuring a SSH to Asynchronous Serial Connection
Configuring a SSH to Asynchronous Serial Connection

In this scenario, you will configure a mediation connection between an SSH port
and an asynchronous serial controller. You will set up an action, event and
response that cause the SSH port and controller to connect. In addition, you will
configure a user profile authorized for terminal server access
To configure an SSH to asynchronous serial connection:
1. Configure event IncSSHConn to signal that an incoming SSH connection request
has been received on port 20001 at IP address 10.40.57.5:
config event IncSSHConn content ssh 10.40.57.5:20001
incoming-connection
2. Configure response SSH20001ToSerial4 to connect SSH port 20001 at IP

address 10.40.57.5 to destination serial 4:
config response SSH20001ToSerial4 content ssh 10.40.57.5:20001
connect dest serial 4
3. Configure action SSHToSerial to associate event IncSSHConn with response

SSH20001ToSerial4:
config action SSHToSerial event IncSSHConn response
ssh20001ToSerial4
4. (optional) Verify that the SSH to asynchronous connection has been configured
properly:
show actions SSHToSerial

(Dub)>show actions SSHToSerial
Action Name
: SSHToSerial
Action Description
:
Event
Event
Event
Event
Name
Description
Originator
Type
Response
Response
Response
Response
Response
(Dub)>
15-8
Name
Description
Responder
Type
Parameters
: IncSSHConn
:
: ssh 10.40.57.5:20001
: SSH20001ToSerial4
:
: ssh 10.40.57.5:20001
: connect
:
dest=serial 4

Configuring Mediation Connections: Configuring a SSH to Asynchronous Serial Connection
inactive:


show connections

ssh 10.40.57.5:20001:4 -> serial 4
(Dub)>
15-9

Configuring Mediation Connections: Configuring an Asynchronous Serial to Asynchronous Serial
Connection
Configuring an Asynchronous Serial to Asynchronous

Serial Connection
In this scenario, you will configure a mediation connection between two
asynchronous serial controllers. You will set up an action, event and response that
cause the controllers to connect.
To configure an asynchronous serial to asynchronous serial connection:
1. Configure event serial2Up with originator serial 2 and event type up:
config event serial2Up content serial 2 up
2. Configure response serial2Connect with responder serial 2 and response

type connect with destination serial 1:
config response serial2Connect content serial 2 connect dest
serial 1
3. Configure action serial2ToSerial1 with event serial2Up and response

serial2Connect:
config action serial2ToSerial1 event serial2Up response
serial2Connect
4. (optional) Verify that the asynchronous to asynchronous connection has been

configured properly:
show actions serial2ToSerial1

(Dub)>show actions serial2ToSerial1
Action Name
: serial2ToSerial1
Action Description
:
Event
Event
Event
Event
Name
Description
Originator
Type
Response
Response
Response
Response
Response
(Dub)>
15-10
Name
Description
Responder
Type
Parameters
: serial2Up
:
: serial 2
: up
: serial2Connect
:
: serial 2
: connect
:
dest=serial 1

Connection
5. (optional) At the main prompt, configure controller serial 1 with application

mode destination:
Note: By default, asynchronous serial controllers are configured to act as both

sources and destinations for connections, which makes configuration of
this command optional.
6. (optional) Configure connection mode activity:
config controller serial 1 connect mode activity
7. Configure controller serial 2 application mode as source:

config controller serial 2 application source
8. Configure connection mode dcd:

15-11

Connection
9. (optional) Verify that the serial controllers have been configured properly:
show controllers serial 1

(Dub)>show controllers serial 1
serial 1 status=enabled link-state=down encapsulation= baud=9600 databits=8
stopbits=1 parity=none resource-state=unassigned
flow-control=none
linemode=rs232
dial-timer=1
init-string=
connect-mode= activity
rts-connect-mode=on
dtr-connect-mode=on
disconnect-mode=
rts-disconnect-mode=off
dtr-disconnect-mode=off
parity-errors=0
description=Asynchronous port
application=destination
(Dub)>
show controllers serial 2

(Dub)>show controllers serial 2
serial 2 status=enabled link-state=down encapsulation= baud=9600 databits=8
stopbits=1 parity=none resource-state=unassigned
flow-control=none
linemode=rs232
dial-timer=1
init-string=
connect-mode=dcd
rts-connect-mode=on
dtr-connect-mode=on
disconnect-mode=
rts-disconnect-mode=off
dtr-disconnect-mode=off
parity-errors=0
description=Asynchronous port
application=source
(Dub)>
10. (optional) Manually connect a device to controller serial 2 and send data.
show connections

serial 2 -> serial 1
(Dub)>

15-12

Configuring Mediation Connections: Configuring an Asynchronous Serial to TCP Connection
Configuring an Asynchronous Serial to TCP Connection

In this scenario, you will configure a mediation connection between an
asynchronous serial controller and a TCP port. You will set up an action, event and
response that cause the controller and TCP port to connect.
To configure an asynchronous to TCP connection:
1. Configure event serial3Up with originator serial 3 and event type up:
config event serial3Up content serial 3 up
2. Configure response serial3ConnectToNOC with responder serial 3 and

response type connect. The destination of the connect response is TCP port
5001 at IP address 10.40.57.5:
config response serial3ConnectToNOC content serial 3 connect dest
tcp 10.40.57.5:5001
3. Configure action serial3ToNOC with event serial3Up and response

serial3ConnectToNOC:
config action serial3ToNOC event serial3Up response
serial3ConnectToNOC
4. (optional) Verify that the asynchronous to TCP connection has been configured
properly:
show actions serial3ToNOC

(Dub)>show actions serial3ToNOC
Action Name
: serial3ToNOC
Action Description
:
Event
Event
Event
Event
Name
Description
Originator
Type
Response
Response
Response
Response
Response
Name
Description
Responder
Type
Parameters
: serial3Up
:
: serial 3
: up
: serial3ConnectToNOC
:
: serial 3
: connect
:
dest=tcp 10.40.57.5:5001
(Dub)>
5. Configure the application mode as source:

config controller serial 3 application source
15-13

Configuring Mediation Connections: Configuring an Asynchronous Serial to TCP Connection

show connections

serial 3 -> tcp 10.40.57.5:5001
(Dub)>
15-14
16
Configuring the DHCP Server
This chapter provides information on configuring the DHCP server with an associated host and
subnet.

DHCP Server Overview
Configuring a DHCP Server
Configuring a DHCP Server Subnet
Configuring a Host on a DHCP Server
Configuring BOOTP/DHCP Relay
Configuring DHCP Client Support
16-1

Configuring the DHCP Server: DHCP Server Overview
DHCP Server Overview

The DHCP server lets hosts connected to Remote RMM-1400's Ethernet interfaces or
bridge WAN interfaces request and obtain IP addresses from Remote RMM-1400. It
also lets hosts discover information about the network to which they are attached.
Available IP addresses are allocated by a network administrator who enters them into
a DHCP configuration file. The DHCP protocol then automatically assigns new IP
addresses to hosts from the pool of IP addresses.
At startup, the DHCP server reads the DHCP configuration file and stores a list of
available addresses on each subnet in memory. When a client requests an address,
the DHCP server allocates an address for it. Each client is assigned a lease that
expires after an amount of time chosen by the administrator. Clients to which leases
are assigned are expected to renew them in order to continue to use the addresses.
Once a lease has expired, the client to which that lease was assigned is no longer
permitted to use the leased IP address. For more information on the DHCP
client/server interaction, refer to Figure 16-1 on page 16-3.
16-2

Configuring the DHCP Server: DHCP Server Overview
The following example displays how the DHCP server distributes an IP address to a
requesting client:
Figure 16-1 DHCP Client/Server Interaction
16-3

Configuring the DHCP Server: Configuring a DHCP Server
Configuring a DHCP Server

Enable DHCP authority mode
Enable DHCP broadcast mode
Configure the DHCP server to use a configuration file
Configure the DHCP server to run on the bridge interface
Configure the DHCP server subnet with an IP address and subnet mask.
To configure the DHCP server settings:

1. At the main prompt, enable the DHCP authority mode:
config dhcp-server authority
2. Enable the DHCP broadcast mode:

config dhcp-server broadcast
3. Configure the DHCP server to run on interface bridge switch:

config dhcp-server interface bridge switch
4. Configure the DHCP server subnet with IP address 234.55.83.0 and subnet
mask 255.255.0.0:
config dhcp-server subnet 234.55.83.0 255.255.0.0
Note: Up to 25 subnets are configurable on the DHCP server. For information on

further DHCP server subnet configurations, refer to section Configuring a
DHCP Server Subnet on page 16-6.
16-4

Configuring the DHCP Server: Configuring a DHCP Server
show dhcp-server

Admin State:
disabled
Broadcast:
enabled
Authority:
enabled
Config file:
Interfaces:
bridge switch
Subnets:
234.55.0.0/16 range=0.0.0.0/0.0.0.0 router=0.0.0.0
DNS:
Hosts:
(Dub)>
Tip: Remote RMM-1400 lets you specify a DHCP server configuration file. This file
overrides any DHCP server settings configured in the Remote RMM-1400 CLI.
If you do not specify the correct DHCP server configuration file, Remote RMM1400 generates an error. The following command specifies file
dhcpconfig1.txt as the DHCP configuration file:
config dhcp-server config-file dhcpconfig1.txt
The DHCP server configuration file must exist in Remote RMM-1400 directory
/config/dhcp before you can specify it as the configuration file in the Remote
RMM-1400 CLI. For information about creating a DHCP server configuration
file, refer to the dhcpd.conf man page.
16-5

Configuring the DHCP Server: Configuring a DHCP Server Subnet
Configuring a DHCP Server Subnet

In this scenario, you will set up the following items for a DHCP server subnet:
Configure a maximum lease time
Configure a default lease time
Configure a domain name server address
Configure an IP address range
Configure a router address.
To configure settings for DHCP server subnet 234.55.83.0/16:

1. Configure maximum lease time 40000:
config dhcp-server subnet 234.55.83.0/16 max-lease 40000
2. Configure default lease time 36000:

config dhcp-server subnet 234.55.83.0/16 default-lease 36000
3. Configure domain name server 10.51.2.67:

config dhcp-server subnet 234.55.83.0/16 domain-name-server
10.51.2.67
4. Configure IP address range 234.55.83.2 to 234.55.83.30:

config dhcp-server subnet 234.55.83.0/16 range 234.55.83.2
234.55.83.30
5. Configure router 234.55.83.1:

config dhcp-server subnet 234.55.83.0/16 router 234.55.83.1
16-6

Configuring the DHCP Server: Configuring a DHCP Server Subnet
show dhcp-server

Admin State:
disabled
Broadcast:
enabled
Authority:
enabled
Config file:
Interfaces:
bridge switch
Subnets:
234.55.0.0/16 range=234.55.83.2/234.55.83.30 router=234.55.83.1
DNS:
10.51.2.67
Hosts:
(Dub)>
16-7

Configuring the DHCP Server: Configuring a Host on a DHCP Server
Configuring a Host on a DHCP Server

Configure a DHCP server host
Configure a host hardware address
Configure a host IP address.
To configure a host on a DHCP server:

1. Configure host firstHostConfig with hardware address 12:e3:a2:45:c5:b3:
config dhcp-server host firstHostConfig hardware-address
12:e3:a2:45:c5:b3
2. Configure host firstHostConfig with IP address 234.55.83.4:

config dhcp-server host firstHostConfig ip address 234.55.83.4
Note: The host IP address must be within one of the subnetworks being served
by the DHCP server. For more information, refer to section Configuring a
DHCP Server Subnet on page 16-6.
show dhcp-server

Admin State:
disabled
Broadcast:
enabled
Authority:
enabled
Config file:
Interfaces:
bridge switch
Subnets:
234.55.0.0/16 range=234.55.83.2/234.55.83.30 router=234.55.83.1
DNS:
10.51.2.67
Hosts:
firstHostConfig MAC=12:E3:A2:45:C5:B3 IP=234.55.83.4
(Dub)>
16-8

Configuring the DHCP Server: Configuring BOOTP/DHCP Relay
Configuring BOOTP/DHCP Relay

In this scenario, you will configure the BOOTP/DHCP server and enable
BOOTP/DHCP relay.
When BOOTP/DHCP relay is enabled, Remote RMM-1400 acts as a
BOOTP/DHCP relay agent; it passes BOOTP/DHCP configuration information
between BOOTP/DHCP clients and servers.
To configure and enable BOOTP/DHCP relay:
1. Configure the BOOTP/DHCP server IP address as 172.56.110.2:
config dhcp-relay server 172.56.110.2
2. Enable BOOTP/DHCP relay:

config dhcp-relay enable
3. (optional) Verify that the BOOTP/DHCP relay settings have been configured
properly:
show dhcp-relay

(Dub)>show dhcp-relay
bootp/DHCP relay is enabled
bootp/DHCP relay servers:
172.56.110.2
(Dub)>
16-9

Configuring the DHCP Server: Configuring DHCP Client Support
Configuring DHCP Client Support

In this scenario, you will enable DHCP client support and configure a ten-minute
interval for Remote RMM-1400 to retry contacting the DHCP server.
Note: DHCP client support cannot be enabled on the bridge group switch if a
static IP address has already been configured. You must remove the static
IP address before enabling DHCP client support.
To enable DHCP client support and configure the retry-timeout interval:
1. Enable DHCP client support:
config interface bridge switch ip dhcp enable
2. Configure the DHCP retry-timeout value as 10 minutes:

config interface bridge switch ip dhcp retry-timeout 10
3. (optional) Verify that the DHCP client settings have been configured properly:
show interface bridge switch
Note: The DHCP-related statements (shown below in boldface type) do not

appear unless DHCP client support is enabled.
(Dub)>show interface bridge switch
bridge switch system-name=br_switch
address=10.44.57.5/16
dhcp-status=enabled dhcp-state=bound
dhcp-retry-timeout=10
dhcp-address=10.44.7.8/16
dhcp-lease-acquired=Fri Sep 17 13:57:37 EST 2010
dhcp-lease-expires=Sun Sep 19 13:57:37 EST 2010
dhcp-routers=10.44.0.1 dhcp-server-id=10.25.2.102
Stats:
Bytes
Packets
Errors
Dropped
Overrun
Rx
2348892
12929
0
0
0
Tx
2050152
11687
0
0
0
ethernet 4
Stats:
Rx
Tx
Bytes
2587084
2618834
(Dub)>
16-10
Packets
12964
19175
Errors
0
0
Dropped
0
0
Overrun
0
0
Framing
0
0
Framing
0
0
17
Configuring the Peripheral
Management Subsystem
This chapter provides information on the expansion peripheral management subsystem and
gives examples of how to configure RMB peripheral units. This subsystem provides
communication, coordination, auto-discovery and state maintenance for Remote RMM-1400
peripheral management.

Peripheral Management Subsystem Overview
Expansion Peripheral Unit Discovery
Expansion Peripheral States
Configuring Remote RMM-1400 to Manage an Expansion Peripheral
Configuring Discrete I/O Points on an Expansion Peripheral
Configuring Alarms for an Expansion Peripheral
Configuring SNMP to Operate a Relay Output
Directly Controlling a Relay Output
Configuring SiteBus Devices for an Expansion Peripheral
Disconnecting a Managed Expansion Peripheral
17-1

Configuring the Peripheral Management Subsystem: Peripheral Management Subsystem Overview
Peripheral Management Subsystem Overview

The peripheral management subsystem lets Remote RMM-1400 manage one or
more peripheral units. The only peripheral units expressly supported by Remote
RMM-1400 are the RMB-1 Peripheral Unit and RMB-2 Peripheral Unit.

The RMB-1 peripheral unit (shown in Figure 17-1) contains the following inputs and
outputs:
Sixty-four digital bistate inputs
Four relay outputs
Four current inputs (4-20 mA)
Four voltage inputs (0-10V, positive only)
A four-terminal SiteBus
Four sets of auxiliary terminals, which are not electrically connected to other
RMB-1 I/O terminals
Built-in temperature and humidity sensors
17-2

Configuring the Peripheral Management Subsystem: Peripheral Management Subsystem Overview

The RMB-2 peripheral unit (shown in Figure 17-2) offers similar capabilities to RMB-1
in a chassis that is sized to be easily mounted in a standard 19-inch, 21-inch, or 23inch rack. RMB-2s digital bistate inputs support both wet and dry contacts, while
RMB-1s digital bistate inputs support dry contacts only.

For technical specifications on RMB-1 and RMB-2 and for details on physically
connecting to RMB terminals, see the Remote RMM-1400 Installation Guide.
RMB-1 and RMB-2 Identification

Each RMB peripheral unit has a name that is defined in the following format:
RMB1-XXXXXX
XXXXXX represents the low-order three bytes of the peripherals MAC address (for
example, RMB1-0E68F4). Note that the name begins with RMB1 regardless of whether
the peripheral unit is an RMB-1 or an RMB-2.
17-3

Configuring the Peripheral Management Subsystem: Expansion Peripheral Unit Discovery
Expansion Peripheral Unit Discovery

Expansion peripheral units announce themselves at all times to all locally-connected
Remote RMM-1400s. These announcements do not cross bridged or routed WAN
links, but they do traverse Ethernet bridges and hubs.
When Remote RMM-1400 discovers an expansion unit, it is made available for
association with a unit number by user command. You can then manually configure
the RMB in the Remote RMM-1400 CLI, which puts the unit under Remote RMM1400s management control. For more information on setting up unit number/
peripheral associations, refer to Configuring Remote RMM-1400 to Manage an
Expansion Peripheral on page 17-7.
17-4

Configuring the Peripheral Management Subsystem: Expansion Peripheral States
Expansion Peripheral States

Every discovered peripheral has an Admin state and Oper state field. The values
associated with these states appear in the output for command show peripherals.
The Administrative State is the configured state of the peripheral. Table 17-1 lists the
potential administrative states.
Table 17-1 Potential Expansion Peripheral Administrative States
Administrative
State
Description
Managed
Indicates that Remote RMM-1400 is ready to actively manage

the peripheral. This state goes into effect when the user issues
command config peripheral manage for the specified
peripheral.
Unmanaged
Indicates that Remote RMM-1400 has not been configured to

manage the peripheral.
The Operation State is the actual, operational state of a discovered peripheral. Table
17-2 lists the potential operation states.
Table 17-2 Potential Expansion Peripheral Operation States
Operation State
Description
Unmanaged
Specifies that the peripheral has been discovered, but

has not been configured for management.
Note: The Administrative State will also be

Unmanaged.
OtherManaged
Specifies that the peripheral is under the management of

another Remote device.
AdminManaged
Specifies that the peripheral has been configured under

the management of Remote RMM-1400, but has not
actively been managed.
Note: This state usually occurs when the expansion

peripheral is configured, but is not connected to
Remote RMM-1400.
Connecting
Specifies that Remote RMM-1400 is attempting to

establish a management connection to the peripheral.
17-5

Configuring the Peripheral Management Subsystem: Expansion Peripheral States
Table 17-2 Potential Expansion Peripheral Operation States (Continued)
17-6
Operation State
Description
Initializing
Specifies that Remote RMM-1400 has established a

management connection to the peripheral and is
exchanging initial setup messages with it.
IncompatibleManaged
Specifies that the following conditions exist:

Remote RMM-1400 has successfully set up and
initialized a management connection to the
peripheral.
The peripherals firmware is incompatible with
Remote RMM-1400s firmware.
Remote RMM-1400 is not currently downloading
compatible firmware to the peripheral (and perhaps
cannot, for some reason).
When a peripheral is in this state, only basic peripheral
management functions are available, such as updating
the image and reloading.
Downloading
Specifies that Remote RMM-1400 is downloading a new

firmware image to the peripheral.
Managed
Specifies that Remote RMM-1400 has successfully set

up and initialized a management connection to the
peripheral.
Online
Specifies that the peripheral is fully operational. Remote

RMM-1400 has established a management connection
to it and it is fully functioning as part of Remote RMM1400.

Configuring the Peripheral Management Subsystem: Configuring Remote RMM-1400 to Manage an
Expansion Peripheral
Configuring Remote RMM-1400 to Manage an Expansion

Peripheral
An expansion peripheral is managed by Remote RMM-1400 when it is:
Configured through the Remote RMM-1400
Connected to the Remote RMM-1400
Capable of operating as an extension of the Remote RMM-1400s discrete I/O

subsystem.
Management of a peripheral by Remote RMM-1400 requires peripheral type and

peripheral name configuration.
Configure a discrete peripheral unit
Configure a description for the discrete peripheral unit
Configure Remote RMM-1400 to manage the peripheral device.
To configure Remote RMM-1400 to manage an expansion peripheral:

1. Configure description Unit manages RMB1-0E68FD for peripheral unit 1:
config peripheral 1 description Unit manages RMB1-OE68FD
Note: The peripheral type is inferred from the peripheral name prefix (for
example, RMB1 = RMB-1 or RMB-2). If desired, you can explicitly configure
the peripheral type with command config peripheral type.
2. Configure Remote RMM-1400 peripheral unit 1 to manage peripheral device
RMB1-0E68FD:
config peripheral 1 manage RMB1-0E68FD
Notes: Configuring the peripheral name associated with a unit number causes
Remote RMM-1400 to attempt active management of the specified
device. If the device has been discovered, Remote RMM-1400 connects
to it and starts managing it immediately. If the device has not been
discovered, Remote RMM-1400 begins actively managing it as soon as it
is discovered.
All peripherals have a hard-coded, unique name. This unique name is

printed on a label affixed to the expansion module.
17-7

Configuring the Peripheral Management Subsystem: Configuring Remote RMM-1400 to Manage an
Expansion Peripheral
3. (optional) Verify that the expansion peripheral has been configured properly:
show peripherals unit 1
The output will look similar to the following:

(Dub) show>peripherals unit 1
Unit number: 1
Description: Unit manages RMB1-0E68FD
Type: rmb-1
Admin state: Managed
Name: RMB1-0E68FD
IP address: 0.0.0.0
Oper state: Online
Manager name: RMM
Manager IP address: 10.39.90.2
Type: rmb-1
Model: B684-00.A:0
Firmware version: 1.00
Firmware build date: Jan 11 2010 09:24:04
Firmware build ID: 071
Serial number: 0000000001
Manufacture date: 12/18/09
Stage2 bootloader version: 1.00
Stage2 bootloader build date: 11/05/09
MAC address: 00:40:72:0E:68:FD
Chassis serial number: 0000000001
Chassis slot number: 0
Chassis model: B684-0
Chassis manufacture date: 12/18/09
Chassis MAC address: 00:40:72:0E:68:FD
(Dub) show>
Note: The output above shows the expansion peripheral in online mode, which
indicates that the peripheral is fully operational. Remote RMM-1400 has
established a management connection to it and it is fully functioning as
part of Remote RMM-1400. For more information on management states,
refer to section Expansion Peripheral States on page 17-5.
17-8

Configuring the Peripheral Management Subsystem: Configuring Discrete I/O Points on an Expansion
Peripheral
Configuring Discrete I/O Points on an Expansion

Peripheral
Configure a default alarm entry for a discrete input point on a peripheral unit
Enable the discrete input point on the peripheral unit
Configure a description for a discrete output on the unit
Enable a discrete analog point on the unit.
To configure discrete I/O points for the discrete expansion peripheral:

1. Configure default alarm entries for discrete input 1/2:
config discrete input 1/2 alarm-default
2. Enable discrete input 1/2:

config discrete input 1/2 enable
3. Configure description Output 1 for discrete output 1/1:

config discrete output 1/1 description Output 1
4. Enable discrete analog 1/3

config discrete analog 1/3 enable
Note: For more information on discrete analog input settings, refer to section
Configuring an Alarm Entry for a Temperature Sensor on page 13-4.
17-9

Configuring the Peripheral Management Subsystem: Configuring Discrete I/O Points on an Expansion
Peripheral
5. (optional) Verify that the discrete I/O points have been configured properly:
show discrete inputs 1/2
The display will look similar to the following for the discrete input:
(Dub)>show discrete inputs 1/2
ID
- 1/2
Description
State
- enable
Resource State
- unassigned
Value
- offline
(Dub)>
show discrete outputs 1/1
The display will look similar to the following for the discrete output:
(Dub)>show discrete outputs 1/1
ID
- 1/1
Description
- Output 1
Resource State
- unassigned
Value
- offline
(Dub)>
show discrete analogs 1/3
The display will look similar to the following for the analog input:
(Dub)>show discrete analogs 1/3
ID
- 1/3
Description
State
- enable
Resource State
- unassigned
Low Band
- 0
High Band
- 0
Hysteresis
- 0
Interval
- 0
Max Loop Value
- 10
Min Loop Value
- 0
Max Sensor Reading - -100000
Min Sensor Reading - 0
Units
- U
Mode
- voltage
Averaging
- none
Value
- offline
(Dub)>
17-10

Configuring the Peripheral Management Subsystem: Configuring Alarms for an Expansion Peripheral
Configuring Alarms for an Expansion Peripheral

Configure an alarm entry that signals when a discrete input on RMB is closed
Configure an alarm entry that signals when the discrete input is open
To configure alarms for an expansion peripheral:

1. Configure alarm entry Input5_closed as a major alarm that signals when
discrete input 1/5 goes down:
config alarm-entry Input5_closed event input 1/5 close major Input
5 is closed
2. Configure alarm entry Input5_open as a normal alarm that signals when discrete
input 1/5 comes up:
config alarm-entry Input5_open event input 1/5 open normal Input 5
is open
17-11

Configuring the Peripheral Management Subsystem: Configuring Alarms for an Expansion Peripheral
3. (optional) Verify that the alarm entries have been configured properly:
show alarm-entries name Input5_closed
The display will look similar to the following for alarm entry Input5_closed:
(Dub)>show alarm-entries name Input5_closed
Name
- Input5_closed
State
- normal
Nagging Level
- major
Trap
- enabled
Trap Priority
- disabled
Raw
- disabled
Category
NE Name
Originator
- input 1/5
Alarm Actions:
Severity
Trigger
Message
-----------------------------------------------------------------major
close
Input 5 is closed
(Dub)>
show alarm-entries name Input5_open
The display will look similar to the following for alarm entry serConnUp:
(Dub)>show alarm-entries name Input5_open
Name
- Input5_open
State
- normal
Current Message - Input 5 is open
Description
Nagging Level
- major
Trap
- enabled
Trap Priority
- disabled
Raw
- disabled
Category
NE Name
Originator
- input 1/5
Alarm Actions:
Severity
Trigger
Message
-----------------------------------------------------------------normal
open
Input 5 is open
(Dub)>
17-12

Configuring the Peripheral Management Subsystem: Configuring SNMP to Operate a Relay Output
Configuring SNMP to Operate a Relay Output

Configure SNMP events to generate manager sets
Configure relay output close and open responses
Configure actions to associate the events with the responses.
To configure SNMP to manage a relay output:

1. Configure SNMP event snmpClose with manager set output4_close:
config event snmpClose content snmp manager-set output4_close
2. Configure SNMP event snmpOpen with manager set output4_open:

config event snmpOpen content snmp manager-set output4_open
3. Configure response switchClose to close output 1/4:

config response switchClose content output 1/4 close
4. Configure response switchOpen to open output 1/4:

config response switchOpen content output 1/4 open
5. Configure action snmpOutputClose to associate event snmpClose with response

switchClose:
config action snmpOutputClose event snmpClose response switchClose
6. Configure action snmpOutputOpen to associate event snmpOpen with response

switchOpen:
config action snmpOutputOpen event snmpOpen response switchOpen
17-13

Configuring the Peripheral Management Subsystem: Configuring SNMP to Operate a Relay Output
7. (optional) Verify that action snmpOutputClose has been configured properly:

show actions snmpOutputClose

(Dub)>show actions snmpOutputClose
Action Name
: snmpOutputClose
Action Description
:
Event
Event
Event
Event
Name
Description
Originator
Type
: snmpClose
:
: snmp
: manager-set output4_close
Response Name
: switchClose
Response Responder
: output 1/4
Response Type
: close
(Dub)>
8. (optional) Verify that action snmpOutputOpen has been configured properly:

show actions snmpOutputOpen

(Dub)>show actions snmpOutputOpen
Action Name
: snmpOutputOpen
Action Description
:
Event
Event
Event
Event
Name
Description
Originator
Type
: snmpOpen
:
: snmp
: manager-set output4_open
Response Name
: switchOpen
Response Responder
: output 1/4
Response Type
: open
(Dub)>

10. To cause the events to occur, issue an SNMP set on the aiMediation event object,
which is in the aiMediationV2 MIB. Use the same names that were used for the
manager sets in the SNMP events (output4_close and output4_open).
17-14

Configuring the Peripheral Management Subsystem: Directly Controlling a Relay Output
Directly Controlling a Relay Output

In this scenario, you will directly open and close a relay output.
To directly open and close a relay output:
1. Open output 1/4:
diag output 1/4 open
2. Close output 1/4 for 10 seconds:

diag output 1/4 close 10
3. (optional) Verify the status of output 1/4:

show discrete outputs 1/4

(Dub)>show discrete outputs 1/4
ID
- 1/4
Description
Resource State
- unassigned
Value
- open
(Dub)>
17-15

Configuring the Peripheral Management Subsystem: Configuring SiteBus Devices for an Expansion
Peripheral
Configuring SiteBus Devices for an Expansion Peripheral

The RMB-1 and RMB-2 expansion peripheral units include a four-terminal SiteBus,
where you can connect sensors that transmit data over a single wire. Each of these
one-wire SiteBus devices has a unique hexadecimal ID, which is discovered by
RMB. After you connect a SiteBus device and the device has been discovered, you
can configure the device for management by Remote RMM-1400.
Connect a device to a SiteBus terminal and discover its hexadecimal ID
Configure a SiteBus device for management by Remote RMM-1400
To configure a SiteBus device:

1. Power down the RMB peripheral by disconnecting its Ethernet connection to
Remote RMM-1400.
2. Use RMBs punchdown tool to physically connect the device to a SiteBus
terminal.
Note: For more information, see section Connecting Wires to RMB Punchdown
Terminals in the Remote RMM-1400 Installation Guide.
3. Power up the RMB peripheral by reconnecting its Ethernet connection to Remote
RMM-1400. RMB discovers the newly connected SiteBus device.
4. Obtain the hexadecimal ID for the newly connected SiteBus device:
show sitebus
In the following example, device 28004564AE05A5 has been discovered, but is not
yet managed by Remote RMM-1400.
(Dub)>show
(Dub) show>sitebus
ID
Periph:Bus
State
Managed Name
-----------------------------------------------------------------------------28004564AE05A5 1:1
Unmanaged
Name
ID
State
Type
Description
----------------------------------------------------------------------------(Dub) show>
17-16

Configuring the Peripheral Management Subsystem: Configuring SiteBus Devices for an Expansion
Peripheral
5. Configure the device with name temp1:

config sitebus temp1
Note: Each SiteBus device should be assigned a unique name in order to track
and store its reported values in the measurement table.
6. Configure device temp1 with hexadecimal ID 28004564AE05A5:
config sitebus temp1 id 28004564AE05A5
7. Assign device type sbTemp to device temp1:

config sitebus temp1 type sbTemp
Note: The device type determines how data from the device will be interpreted
and what points will be created for the device. The only device type
supported for Remote RMM-1400 version 4.0x is sbTemp, which includes
points for Celsius and Fahrenheit temperatures. The device in this
example would have two logical points: sitebus temp1/temperatureC
and sitebus temp1/temperatureF.
8. Add description Temperature Sensor 1 to device temp1:
config sitebus temp1 description Temperature Sensor 1
9. (optional) Verify that the SiteBus device has been configured properly:
show sitebus
The display will look similar to the following:

(Dub)>show
(Dub) show>sitebus
ID
Periph:Bus
State
Managed Name
-----------------------------------------------------------------------------28004564AE05A5 1:1
Managed
temp1
Name
ID
State
Type
Description
----------------------------------------------------------------------------temp1
28004564AE05A5 Online
sbTemp
Temperature Sensor 1
(Dub) show>
Note: For information on configuring a measurement-table entry for a SiteBus

device, see section Configuring a Measurement Table Entry for a
Temperature Sensor and its subsection Sample Configuration for SiteBus
Temperature Sensor.
17-17

Configuring the Peripheral Management Subsystem: Disconnecting a Managed Expansion Peripheral
Disconnecting a Managed Expansion Peripheral

When Remote RMM-1400 is disconnected from a managed peripheral, a trap is
generated. Remote RMM-1400 notices physical disconnections 20 to 30 seconds
after they occur.
In this scenario, you will disconnect the managed peripheral unit.
To disconnect a managed expansion peripheral, configure the unit 1 expansion
peripheral to become unmanaged:
config peripheral 1 no manage
When Remote RMM-1400 is reconnected to an expansion peripheral after a

temporarily disconnection:
17-18
Output state changes that occurred during the disconnection are applied to the
outputs points.
Events are generated that report on the current state of enabled expansion
peripheral inputs. This includes changes that occurred and persisted during the
disconnection.
18
Configuring the SNMP Proxy
This chapter provides information about how to configure the Remote RMM-1400 SNMP Proxy
feature.

SNMP Proxy Feature Overview
SNMP Proxy Configuration Information
Configuring a Mediation SNMP Event Template
Configuring a Mediation SNMP Point Template
Configuring a Mediation SNMP NE Template
Configuring a Mediation SNMP Measurement Template
Configuring a Mediation SNMP Network Element
Configuration Results
18-1

Configuring the SNMP Proxy: SNMP Proxy Feature Overview
SNMP Proxy Feature Overview

The Remote RMM-1400 SNMP Proxy feature allows for virtual network elements
(NEs) to represent devices which are subtended from Remote RMM-1400. Remote
RMM-1400 acts as the SNMP manager for the real NE. This means that an NE can
be hidden on the network, yet still monitored by Remote RMM-1400.
The various states of the NEs are represented in Remote RMM-1400s alarm table,
which provides a mechanism for management systems to query the state and receive
alarms.
One major benefit of this feature is a reduction in IP address requirements for sites,
where private addressing can be used between the SNMP device and Remote RMM1400.
Figure 18-1 shows the interaction of the mediation NEs (snmp ne1 and snmp ne2)
inside Remote RMM-1400 with the real SNMP NEs and the action and alarm table
mediation subsystems.
Figure 18-1 Remote SNMP Proxy Configuration
18-2

Configuring the SNMP Proxy: SNMP Proxy Configuration Information
SNMP Proxy Configuration Information

At a high level, the following information must be configured for the SNMP proxy
feature:
SNMP NE name and associated host information, points and events
The address of the SNMP Manager
SNMP Templates
The mapping of incoming SNMP traps to mediation events utilizes a template
mechanism which allows for a common mapping to be shared among multiple
mediation SNMP NEs or multiple instances within the same NE. The templates define
how the proxied devices SNMP MIB is used by the proxy SNMP NE.
There are two types of mappings: events and points, thus two types of templates that
are user-definable.
Point Template
The point template defines how a stateful item on the proxied device is managed by
Remote RMM-1400. For each state, the following information is configurable:
severity; message; varbind; offline state message and severity; and trap OID. The
varbind and trap OID are used to match incoming traps.
Event Template
Events are simple stateless mappings between an SNMP trap and a mediation event.
Events are not mapped to the Remote RMM-1400 alarm table. An event template
consists, at a minimum, of a trap-oid and a message parameter.
NE Template
The NE template contains device model definitions for a proxied SNMP network
element. This template can then be referenced by other NEs of that model. The
templates can be stored and applied as individual patch configurations for easy
distribution to multiple Remote RMM-1400 units.
Measurement Template
The measurement template describes parameters such as poll OID, trap OID and
varbind value used to obtain the value for a point on a proxied NE. This template can
then be applied to other proxied NEs.
Using Variables in Templates

Template events and points can contain variables in their OID and varbind values.
The values of the variables are defined when the template is referenced in the event
or point configuration of a mediation SNMP NE.
18-3

Configuring the SNMP Proxy: SNMP Proxy Configuration Information
The predefined variables that are available for use in these templates are described in
Table 18-1.
Table 18-1 Predefined Template Variables
Variable
Description
$(point)
Contains the name of the point configured on the

mediation SNMP NE
$(event)
Contains the name of the event configured on the

mediation SNMP NE
$(measurement)
Contains the name of the measurement configured

on the mediation SNMP NE
$(snmpne)
Contains the name of the mediation SNMP NE
SNMP NE
The mediation SNMP NE is a mediation event originator. The originator type is
snmpne and the originator instance is the name of the mediation NE. The snmpne
contains site-specific information and can be linked with a previously created event
template or a point template for part of its definition.
The name of the NE is used as the NE name value for mediation alarm table entries
and responses.
SNMP Manager
The configurable information for the SNMP manager is the port on which the SNMP
manager listens for incoming SNMP notifications. The default port is 162.
18-4

Configuring the SNMP Proxy: Configuring a Mediation SNMP Event Template
Configuring a Mediation SNMP Event Template

In this scenario, you will configure a mediation SNMP event template named
coldStartDef, which creates a reboot event for the proxied NE.
Note that not all possible parameters are used in this example. See the Remote
RMM-1400 Command Reference Guide for details on each parameter.
To configure a mediation SNMP event template:
1. Configure event template name coldStartDef:
config mediation snmp event-template coldStartDef
2. (optional) Configure an associated description Reboot event:

config mediation snmp event-template coldStartDef description
Reboot event
3. Configure the trap OID .1.3.6.1.6.3.1.1.5.1:

config mediation snmp event-template coldStartDef trap-oid
.1.3.6.1.6.3.1.1.5.1
4. Configure the message $(event) event on $(snmpne):

config mediation snmp event-template coldStartDef message $(event)
event on NE $(snmpne)
5. (optional) Verify that the event template has been configured properly:
show mediation snmp event-templates coldStartDef

(Dub)>show mediation snmp event-templates coldStartDef
Name: coldStartDef
Description: Reboot event
Message: $(event) event on NE $(snmpne)
Trap OID: .1.3.6.1.6.3.1.1.5.1
(Dub)>
18-5

Configuring the SNMP Proxy: Configuring a Mediation SNMP Point Template
Configuring a Mediation SNMP Point Template

In this scenario, you will configure a mediation SNMP point template named
ifEntryDef, which is a template for a row in the interface table on the proxied NE.
For each state (up and down) you will configure the:
poll value
dynamic poll table and trap map, or the poll OID
trap OID
varbind match
severity
message
poll default state
To configure a mediation SNMP point template:

1. Configure the point template name ifEntryDef:
config mediation snmp point-template ifEntryDef
2. (optional) Configure an associated description Entry in IfTable:

config mediation snmp point-template ifEntryDef description Entry
in IfTable
3. Configure the dynamic poll table with the following settings:
table oid .1.3.6.1.2.1.2.2.1
match column (number) 2
match value (for specified column) $(ifDescr)
state (table) column 8
config mediation snmp point-template ifEntryDef

poll-table .1.3.6.1.2.1.2.2.1 2 $(ifDescr) 8
Note: If you configure a dynamic poll table (Step 3), you will not configure a poll ID
(Step 4) and vice versa.
4. Configure the poll OID .1.3.6.1.2.1.2.2.1.8.$(ifIndex)for template
ifEntryDef:
config mediation snmp point-template ifEntryDef poll-oid
.1.3.6.1.2.1.2.2.1.8.$(ifIndex)
5. Configure the Up state:

config mediation snmp point-template ifEntryDef state up
18-6

6. Configure the poll value of 1 for the up state:

config mediation snmp event-template ifEntryDef state up pollvalue 1
7. Configure the trap oid .1.3.6.1.6.3.1.1.5.4 for the up state:

config mediation snmp point-template ifEntryDef state up trap-oid
.1.3.6.1.6.3.1.1.5.4
8. Configure the varbind match .1.3.6.1.2.1.2.2.1.1 $(ifIndex) for the up

state, that is, the OID equals the value of $(ifIndex):
config mediation snmp point-template ifEntryDef state up varbindmatch .1.3.6.1.2.1.2.2.1.1 $(ifIndex)
9. Configure the severity as normal for the up state:

config mediation snmp point-template ifEntryDef state up severity
normal
10. Configure the message as $(point) is up for the up state:

config mediation snmp point-template ifEntryDef state up message
$(point) is up
You will now configure similar parameters for the down state using the same point
template, ifEntryDef.
11. Configure the down state for point template ifEntryDef:
config mediation snmp point-template ifEntryDef state down
12. Configure the poll value of 2 for the down state:

config mediation snmp event-template ifEntryDef state down pollvalue 2
13. Configure the trap oid .1.3.6.1.6.3.1.1.5.3 the down state:

config mediation snmp point-template ifEntryDef state down trapoid .1.3.6.1.6.3.1.1.5.3
14. Configure the varbind match .1.3.6.1.2.1.2.2.1.1 $(ifIndex) for the down
state:
varbind-match .1.3.6.1.2.1.2.2.1.1 $(ifIndex)
15. Configure the severity as major for the down state:

severity major
16. Configure the message as $(point) is down:

config mediation snmp point-template ifEntryDef state down message
$(point) is down
18-7

17. Configure the default polling state for points in this template as up.
config mediation snmp point-template ifEntryDef poll-default-state
up
18. (optional) Verify that the point template has been configured properly:
show mediation snmp point-templates ifEntryDef

(Dub)>show mediation snmp point-templates ifEntryDef
Name: ifEntryDef
Description: Entry in IfTable
Poll OID: .1.3.6.1.2.1.2.2.1.8.$(ifIndex)
Poll Default State: up
Offline Severity: major
Offline Message: $(point) is offline
State: down
Message: $(point) is down
Poll Value: 2
Severity: major
Trap OID: .1.3.6.1.6.3.1.1.5.3
Varbind Match: .1.3.6.1.2.1.2.2.1.1 = $(ifIndex)
State: up
Message: $(point) is up
Poll Value: 1
Severity: normal
Trap OID: .1.3.6.1.6.3.1.1.5.4
Varbind Match: .1.3.6.1.2.1.2.2.1.1 = $(ifIndex)
(Dub)>
18-8

Configuring the SNMP Proxy: Configuring a Mediation SNMP NE Template
Configuring a Mediation SNMP NE Template

In this scenario, you will configure a mediation SNMP NE template, which is a
template containing device model definitions for a proxied SNMP network element.
For this template, you will configure the:
template name Template1
description
point, which refers to an existing point template and associated values
event, which refers to an the existing event template and associated values
NE template, which refers to the existing NE template and an associated value.
To configure a mediation SNMP NE template:

1. Configure the NE template name Template1:
config mediation snmp ne-template Template1
2. (optional) Configure a description for Template1 called Sample template:

config mediation snmp ne-template Template1 description Sample
template
3. Configure point modem with the following settings:
point template ifEntryDef
parameter ifDesc
value serial_modem
config mediation snmp ne-template Template1 point modem ifEntryDef

ifDesc serial_modem
4. Configure event runningConfigChange with the following settings:
event template (existing) configChangeDef
parameter file
value running-config
config mediation snmp ne-template Template1 event

runningConfigChange configChangeDef file running-config
18-9

Configuring the SNMP Proxy: Configuring a Mediation SNMP NE Template
5. Configure NE template alarm1 with the following settings:
NE template (existing) alarms
parameter num
value 1
config mediation snmp ne-template Template1 ne-template alarm1

alarms num 1
6. (optional) Verify that the NE template has been configured properly:

show mediation snmp ne-templates Template1

(Dub)>show mediation snmp
(Dub) show mediation snmp>ne-templates Template1
Name: Template1
Description: Sample template
Event: runningConfigChange
Template: configChangeDef
Parameter: file = running-config
Point: modem
Template: ifEntryDef
Parameter: ifDescr = serial_modem
Template Reference: alarm1
Template: alarms
Parameter: num = 1
(Dub) show mediation snmp>
18-10

Configuring the SNMP Proxy: Configuring a Mediation SNMP Measurement Template
Configuring a Mediation SNMP Measurement Template

In this scenario, you will configure a mediation SNMP measurement template,
which defines the way a mediation SNMP NE obtains the value for a point on a
proxied SNMP network element. We will look at two examples of measurement
templates: an example that configures an individual measurement and a second
example that configures a group of measurements.
For the first template, you will configure:
the template name alDef and description Single measurement
the poll OID
which numeric value to consider significant if the response is a string
the trap OID, varbind match and varbind value.
For the second template, you will configure:

the template name alTableDef and description Measurement group
the dynamic poll table
which numeric value to consider significant if the response is a string
the trap OID, varbind ID and varbind value.
To configure a mediation SNMP measurement template that configures an individual

measurement:
1. Configure the point template name alDef:
config mediation snmp measurement-template alDef
2. (optional) Configure an associated description Single measurement:

config mediation snmp measurement-template alDef description
Single measurement
3. Configure the poll OID .1.3.6.1.4.1.539.42.2.2.1.5.$(alIndex) for

template alDef:
config mediation snmp measurement-template alDef poll-oid
.1.3.6.1.4.1.539.42.2.2.1.5.$(alIndex)
4. Configure the template alDef to consider as significant the second numeric value
in a string response:
config mediation snmp measurement-template alDef value-match 2
5. Configure an SNMP trap named critical, with a trap OID

1.3.6.1.4.1.539.42.2.0.5 for the critical state:
config mediation snmp measurement-template alDef trap critical
trap-oid .1.3.6.1.4.1.539.42.2.0.5
18-11

6. Configure the varbind-match .1.3.6.1.4.1.539.42.2.2.1.1 for the critical

state; that is, the OID to use to retrieve the value of $alIndex:
varbind-match .1.3.6.1.4.1.539.42.2.2.1.1 $alIndex
7. Configure a varbind value of for .1.3.6.1.4.1.539.42.2.2.1.5 for the

critical state:
varbind-value .1.3.6.1.4.1.539.42.2.2.1.5
8. Configure the template alDef to consider as significant the second numeric value
in a string response for critical traps:
value-match 2
show mediation snmp measurement-templates alDef

(Dub)>show mediation snmp measurement-templates alDef
Name: alDef
Description: Single measurement
Poll OID: .1.3.6.1.4.1.539.42.2.2.1.5.$(alIndex)
Value Match Index: 2
Value Conversion Multiplier: 1
Trap: critical
Trap OID: .1.3.6.1.4.1.539.42.2.0.5
Varbind Value: .1.3.6.1.4.1.539.42.2.2.1.5
Varbind Match: .1.3.6.1.4.1.539.42.2.2.1.1 = $alIndex
(Dub)>

To configure a mediation SNMP measurement template that configures a group of
measurements:
1. Configure the point template name alTableDef:
config mediation snmp measurement-template alTableDef
2. (optional) Configure an associated description Measurement group:

config mediation snmp measurement-template alTableDef description
Measurement group
18-12

3. Configure the dynamic poll table with the following settings:
table OID .1.3.6.1.4.1.539.42.2.2
match column (number) 7
match value (for specified column) 5
config mediation snmp measurement-template alTableDef poll-table

.1.3.6.1.4.1.539.42.2.2 7 5
4. Configure the template alTableDef to consider as significant the second numeric

value in a string response:
config mediation snmp measurement-template alTableDef value-match
2
5. Configure an SNMP trap named critical, with a trap OID

1.3.6.1.4.1.539.42.2.0.5 for the critical state:
config mediation snmp measurement-template alTableDef trap
critical trap-oid .1.3.6.1.4.1.539.42.2.0.5
6. Configure the varbind OID .1.3.6.1.4.1.539.42.2.2.1.7 for the critical

state:
critical varbind-id .1.3.6.1.4.1.539.42.2.2.1.7
7. Configure a varbind value of for .1.3.6.1.4.1.539.42.2.2.1.5 for the

critical state:
critical varbind-value .1.3.6.1.4.1.539.42.2.2.1.5
8. Configure the template alTableDef to consider as significant the second numeric

value in a string response for critical traps:
critical value-match 2
18-13

show mediation snmp measurement-template alTableDef

(Dub)>show mediation snmp measurement-templates alTableDef
Name: a1TableDef
Description: Measurement group
Poll Table OID: .1.3.6.1.4.1.539.42.2.2
ID Column: 7
Value Column: 5
Value Conversion Multiplier: 1
Trap: critical
Trap OID:
Varbind Value: .1.3.6.1.4.1.539.42.2.2.1.5
Varbind ID:
Trap: critical
Trap OID: .1.3.6.1.4.1.539.42.2.0.5
Varbind Value:
Varbind ID: .1.3.6.1.4.1.539.42.2.2.1.7
(Dub)>
18-14

Configuring the SNMP Proxy: Configuring a Mediation SNMP Network Element
Configuring a Mediation SNMP Network Element

In this scenario, you will configure information specific to a mediation SNMP NE
including:
The host parameters
A link to the previously defined event template, coldStartDef, which defines
the associated event
A link to the previously defined point template, ifEntryDef, which defines the
associated event
A link to the previously defined measurement template, alTableDef, which
defines a means of obtaining a value for a point on a proxied NE.
To configure a mediation SNMP NE:
1. Configure the name, ProxyNE, for the mediation SNMP NE:
config mediation snmpne ProxyNE
2. Configure the network element name, ProxyNE:

config mediation snmpne ProxyNE ne-name ProxyNE
3. Configure the host with an IP address of 10.40.65.90, port number 161,

community name administrator and SNMP version number v1. These
parameters are used for polling the device.
config mediation snmpne ProxyNE host 10.40.65.90 161 administrator
v1
4. Configure the category as NECategory:

config mediation snmpne ProxyNE category NECategory
5. Configure status point ethernet1 with a link to the previously defined

ifEntryDef point template, a replaceable parameter name ifIndex and a value
for that parameter as 1:
config mediation snmpne ProxyNE point ethernet1 ifEntryDef ifIndex
1
6. Configure status point ethernet2 with a link to the previously defined

ifEntryDef point template, a replaceable parameter name ifIndex and a value
for that parameter as 2:
config mediation snmpne ProxyNE point ethernet2 ifEntryDef ifIndex
2
7. Configure an event named reboot, with a link to the previously defined

coldStartDef event template:
config mediation snmpne ProxyNE event reboot coldStartDef
18-15

Configuring the SNMP Proxy: Configuring a Mediation SNMP Network Element
8. Configure a measurement named analog, with a link to the previously defined

alTableDef measurement template:
config mediation snmpne ProxyNE measurement analog alTableDef
9. (optional) Verify that the ProxyNE SNMP NE has been configured properly:
show mediation snmpne ProxyNE

(Dub)>show mediation snmpne ProxyNE
Name: ProxyNE
Description:
Host: 10.40.65.90:161
SNMP Community: administrator
SNMP Version: v1
Category: NECategory
NE Name: ProxyNE
Measurement Poll Interval: 60
Point Poll Interval: 3600
Connectivity OID: .1.3.6.1.2.1.1.2.0
Connectivity State: offline
Last Connectivity Poll Reply: unknown
Event: reboot
Template: coldStartDef
Last Trap: unknown
Point: ethernet1
Current State: point offline
Last Trap: unknown
Last Poll Reply: unknown
Parameter: ifIndex = 1
Point: ethernet2
Current State: point offline
Last Trap: unknown
Parameter: ifIndex = 2
Measurement: analog
Template: a1TableDef
(Dub)>
18-16

Configuring the SNMP Proxy: Configuration Results
Configuration Results
The following is a partial example of a running-config, which shows the results of
the template points and events used to construct a mediation SNMP NE containing a
port with two states (up and down), Ethernet ports 1 and 2 and a reboot notification.
config mediation snmp
event-template coldStartDef
description Reboot event
message $(event) event on NE $(snmpne)
trap-oid .1.3.6.1.6.3.1.1.5.1
exit
measurement-template a1TableDef
description Measurement group
poll-table .1.3.6.1.4.1.539.42.2.2 7 5
value-match 2
trap critical
trap-oid .1.3.6.1.4.1.539.42.2.0.5
varbind-id .1.3.6.1.4.1.539.42.2.2.1.7
value-match 2
exit
trap critcal
varbind-value .1.3.6.1.4.1.539.42.2.2.1.5
exit
exit
point-template ifEntryDef
description Entry in IfTable
poll-oid .1.3.6.1.2.1.2.2.1.8.$(ifIndex)
state up
message $(point) is up
poll-value 1
trap-oid .1.3.6.1.6.3.1.1.5.4
exit
state down
message $(point) is down
poll-value 2
severity major
trap-oid .1.3.6.1.6.3.1.1.5.3
exit
poll-default-state up
exit
ne-template Template1
description Sample template
event runningConfigChange configChangeDef file running-config
point modem ifEntryDef ifDesc serial_modem
ne-template alarm1 alarms num 1
exit
config mediation snmpne ProxyNE
category NECategory
ne-name ProxyNE
host 10.40.65.90 161 administrator v1
event reboot coldStartDef
measurement analog a1TableDef
point ethernet1 ifEntryDef ifIndex 1
point ethernet2 ifEntryDef ifIndex 2
(Dub)>
18-17

Configuring the SNMP Proxy: Configuration Results
Note: Alarms, events, actions and responses for SNMP proxy will not display in
running-config as they are implicitly added to the configuration. Only if the
user makes a change to one of the entities will these four items display in
running-config. This applies only to new SNMP proxy configurations, not
those loaded from saved configurations.
The configuration will add the following alarm entries and actions automatically.
config alarm-entry ProxyNE_ethernet1_snmpne
event snmpne ProxyNE point ethernet1 trap up event $(message)
event snmpne ProxyNE point ethernet1 trap down event $(message)
ne-name MyNE
category some-category
config alarm-entry ProxyNE_ethernet2_snmpne
event snmpne ProxyNE point ethernet2 trap up event $(message)
event snmpne ProxyNE point ethernet2 trap down event $(message)
ne-name ProxyNE
config event ProxyNE_reboot_snmpne content snmpne ProxyNE trap reboot
config response ProxyNE_trap_snmpne content snmp trap
message $(message)
ne-name ProxyNE
config action ProxyNE_reboot_snmpne
event ProxyNE_reboot_snmpne
response ProxyNE_trap_snmpne
18-18
19
Configuring Jobs
This chapter includes scenarios that contain step-by-step procedures on how to configure jobs
for Remote RMM-1400.

Job Configuration Overview
Configuring Access to a Central FTP Package Server
Installing a Script Package
Configuring a Job with a Script Package and Script
Configuring a Job with a Job Property
Configuring a Job with a Job Task
Configuring Job Start Times
Configuring Dynamic Memory for a Job
19-1

Configuring Jobs: Job Configuration Overview
Job Configuration Overview

A job contains the specifications for running an instance of a script. It refers to a script
defined within a package and specifies the parameters for execution on Remote
RMM-1400. Scripts are defined in packages and specify the parameters for execution
when the associated jobs run.
Note: All job configuration examples in this document are set up in the CLI; however,
similar functions can also be performed from the Remote Web interface. See
Accessing the Web Interface on page 2-8 for details.
Script Package Components

Before you configure a job on Remote RMM-1400, you must first obtain a script
package from Kentrox. A script package (.pkg file) contains two basic components:
Python modules
A package manifest file
Python Modules
A script package can contain one or more Python modules (.py or .pyc files). Each
Python module can contain one or more scripts or it can be empty. A script is a Python
class that defines a run and stop method, which implements the scripting interface on
Remote RMM-1400. A script can define job properties, which pass runtime
parameters and/or settings (such as, connection information for a network element,
baud rates, TIDs, phone numbers, software version and user name and password
information) to Remote RMM-1400 when a job is executed. In addition, a script can
define job tasks and the properties required to request IP configuration for a device or
open a server socket connection to receive and transmit data.
In addition to Python modules, the script package can also contain Python packages.
A Python package is a way to store Python modules in a hierarchical directory
structure.
Package Manifest File

A Package Manifest file is an XML file that acts as a table of contents for the script
package. The package manifest lists which scripts the package contains, what tasks
must be configured to use the scripts and any supported properties for the script.
After you obtain a script package from Kentrox, you can use an FTP utility to transfer
the script package either directly to the pkgstage directory on Remote RMM-1400, or
to a directory on a central FTP package server that contains script packages. After
you transfer the script package, you can install it onto Remote RMM-1400.
19-2

Configuring Jobs: Job Configuration Overview
When a script package is installed on Remote RMM-1400, it is stored in a database

for executing jobs. A job must refer to a script package and a script in order for it to
execute properly. Basically, a job configured through the Remote RMM-1400 CLI runs
the function(s) within the script module. After configuring and executing a job, the
script package is retrieved from the package database and run by the script engine.
19-3

Configuring Jobs: Configuring Access to a Central FTP Package Server
Configuring Access to a Central FTP Package Server

Important: This procedure applies only if you plan to store script packages on a
central FTP package server and install the script packages from the
server to the pkgstage directory on Remote RMM-1400.
Configure the central FTP package server
Configure the script package directory location
Configure the server user name and password
Enable remote access to the central FTP package server
To configure the central FTP package server:

1. At the main prompt, configure Remote RMM-1400 to use an FTP server with IP
address 11.8.77.3 and the default port number:
config pkgs server address 11.8.77.3
2. Configure the directory that contains the script packages as /packages/test:

config pkgs server directory /packages/test
3. Configure the server user name as test and password as test:

config pkgs server user test test
Note: The user name and password must match the user name and password
configured on the central FTP package server.
4. Enable remote access to the central FTP package server:
config pkgs server enable
5. (optional) Verify that the central FTP package server has been configured
properly:
show pkgs server

(Dub)>show pkgs server
FTP server: enabled
Address: 11.8.77.3
Port: 21
User: test
Password: test
Directory: /packages/test
(Dub)>

19-4

Configuring Jobs: Installing a Script Package
Installing a Script Package

Important: This procedure assumes that you have obtained a script package from
Kentrox (in this example, exampleScript-1.0.0.pkg).
Use an FTP utility to transfer a script package to the Remote RMM-1400

staging area or to the configured central FTP package server
Tip: For more information on how to configure a central FTP package server,
refer to procedure Configuring Access to a Central FTP Package Server
on page 19-4.
Install the script package
To install a script package:

1. Using an FTP utility, do one of the following:
Transfer exampleScript-1.0.0.pkg from the local workstation to the

pkgstage directory on Remote RMM-1400. Continue to step 2.
Transfer exampleScript-1.0.0.pkg to the central FTP package server

default directory of /, which contains all script packages. Continue to step 3.
2. At the main CLI prompt, install script package exampleScript-1.0.0.pkg to

Remote RMM-1400:
config pkgs install name exampleScript
Continue to step 4.
3. At the main CLI prompt, install script package exampleScript-1.0.0.pkg to
Remote RMM-1400 from the central FTP package server:
config pkgs install name exampleScript-1.0.0 fromserver
Important: To install a script package from a central FTP package server, you
need to configure a static route. For more information, refer to
Configuring Static Routes on page 7-1.
19-5

Configuring Jobs: Installing a Script Package
4. (optional) Verify that the script package has been installed properly:
show pkgs summary

(Dub)>show pkgs summary
Package
examplescript
(Dub)>
Version
1.0.0
Tip: To display the contents and attributes of script package examplescript,

enter show pkgs name examplescript.
Note: Some jobs need to be restarted when the configuration changes, including:
19-6
Battery Monitor (including the Battery Learner)
Analog Monitor

Configuring Jobs: Configuring a Job with a Script Package and Script
Configuring a Job with a Script Package and Script

Kentrox (in this example, exampleScript-1.0.0.pkg) and the
procedure Installing a Script Package on page 19-5 has been completed.
In this scenario, you will configure a job with a script that prints a string of text to two
log files (stdout.log and stderr.log).
To configure a job with a script package and script:
1. At the main prompt, create job printlog:
config jobs name printlog
2. Configure job printlog to use script package examplescript and script

capture_example and define the minimum acceptable version level for an
installed package as 1.0.0:
config jobs name printlog script examplescript capture_example
1.0.0
3. (optional) Verify that the job has been configured with the proper script package
and script:
show jobs name printlog status

(Dub)>show jobs name printlog status
Job: printlog
Package: examplescript
Min version: 1.0.0
Script: capture_example
Cron start: disabled
Start at boot: disabled
Memory limit (Kb): 1024
Output capture: disabled
Max start attempts: 1
Run state: idle
(Dub)>
19-7

Configuring Jobs: Configuring a Job with a Job Property
Configuring a Job with a Job Property

procedure Configuring a Job with a Script Package and Script on page
19-7 has been completed.
In this scenario, you will configure a job that uses a script that prints a string of text
to two log files. During runtime, the two files will be created in the jobs data
directory when job capture is enabled.
To configure a job with a job property:
1. At the main prompt, enable output capture for job printlog:
config jobs name printlog capture
2. Configure job printlog with job property capture_text and assign it the
property value of Hello World:
config jobs name printlog property capture_text Hello World
Note: To include spaces or special characters, quotes must be included.

By entering job property value hello world, job printlog will run script
capture_example and pass runtime job property capture_text. This indicates
that value Hello World will be written to the stdout.log and stderr.log files located
in the jobs data directory on Remote RMM-1400.
3. (optional) Verify that the job has been configured with the proper job property:
show jobs name printlog properties

(Dub)>show jobs name printlog properties
Name
Value
capture_text
Hello World
(Dub)>

5. Run job printlog:
exec-job printlog run
A run ID is assigned.
19-8

Configuring Jobs: Configuring a Job with a Job Property
6. (optional) Verify that the job has been executed successfully:

show jobs name printlog history

(Dub) show jobs name printlog>history
Run ID
Start time
End time
1 2010/02/03 22:35:32 2010/02/03 22:35:33
(Dub) show jobs name printlog>
Exit state
normal
7. (optional) FTP to Remote RMM-1400 to verify that the output of the job has been
recorded to the stdout.log and stderr.log files located in the jobs data directory
(jobdata/printlog).
19-9

Configuring Jobs: Configuring a Job with a Job Task
Configuring a Job with a Job Task

procedure Installing a Script Package on page 19-5 has been completed.
In this scenario, you will configure a job with a job task. The job uses a script that
starts a server, which accepts an incoming socket connection. When a connection
is established, the script listens for data from the connection. When data is sent, the
script determines if it should modify the data based on the value yes entered for job
property upper_case and then writes back the changed data in uppercase.
To configure a job with a job task:
1. At the main prompt, create and configure job echodata to use script package
examplescript and script echo_example. Define the minimum acceptable
version level for an installed package as 1.0.0:
config jobs name echodata script examplescript echo_example 1.0.0
2. Create task new_ip and assign the task type as ifconfig:

config jobs name echodata task new_ip type ifconfig
3. Assign address property value 192.168.0.215 to task new_ip:

config jobs name echodata task new_ip property address
192.168.0.215
4. Assign controller property br_switch to task new_ip:

config jobs name echodata task new_ip property controller
br_switcheth0_1
5. (optional) Verify that the task new_ip has been configured properly:
show jobs name echodata task new_ip

(Dub)>show jobs name echodata task new_ip
Task: new_ip
Position: 1
Type: ifconfig
Properties:
Name
Value
address
192.168.0.215
controller
br_switch
(Dub)>
6. Create task server_sock and assign the task type as serversocket:

config jobs name echodata task server_sock type serversocket
19-10

Configuring Jobs: Configuring a Job with a Job Task
7. Assign the task property port as 50008, ifconfig as new_ip, type as STREAM
and listen as 5 to task server_sock:
config jobs name echodata task server_sock property port 50008
config jobs name echodata task server_sock property ifconfig
new_ip
config jobs name echodata task server_sock property type STREAM
config jobs name echodata task server_sock property listen 5
8. (optional) Verify that the task server_sock has been configured properly:
show jobs name echodata task server_sock

(Dub)>show jobs name echodata task server_sock
Task: server_sock
Position: 2
Type: serversocket
Properties:
Name
Value
address
10.40.57.50
ifconfig
new_ip
listen
5
port
50008
type
STREAM
(Dub)>
9. Enable capture output for job echodata:

config jobs name echodata capture
10. Configure job echodata with the job property upper_case and assign it with the
value of yes:
config jobs name echodata property upper_case yes
11. (optional) Verify that job echodata has been configured with the proper job
properly:
show jobs name echodata properties

(Dub)>show jobs name echodata properties
Name
Value
upper_case
yes
(Dub)>

13. Run job echodata:
exec-job echodata run
A run ID is assigned.
19-11

Configuring Jobs: Configuring Job Start Times
Configuring Job Start Times

In this scenario, you will configure a job to start on August 7 and to run through
September 30 at 12:30 p.m., 5:30 p.m. and 7:30 p.m. every Monday, Wednesday
and Friday.
To configure start times for a job:
1. At the main prompt, configure job printlog to start on August 7 and to run
through September 30 every Monday, Wednesday and Friday at 12:30 p.m., 5:30
p.m. and 7:30 p.m.:
config jobs name printlog start-at 8-9 7-30 12,17,19 30 1,3,5
A start-at index number of 1 is assigned.

2. (optional) Verify that job printlog has been configured with the proper starting
times:
show jobs name printlog starts *

(Dub)>show jobs name printlog starts *
Start at bootup: disabled
Start-at index: 1
Month: 8-9
Day: 7-30
Hour: 12,17,19
Minute: 30
Weekday: 1,3,5
No scheduled start time
(Dub)>
19-12

Configuring Jobs: Configuring Dynamic Memory for a Job
Configuring Dynamic Memory for a Job

In this scenario, you will configure the amount of dynamic memory that Remote
RMM-1400 can use while running job printlog.
To configure dynamic memory for a job:
1. At the main prompt, configure Remote RMM-1400 to use 2024 kilobytes of
dynamic memory while running job printlog:
config jobs name printlog memory 2024
2. (optional) Verify that the dynamic memory has been configured properly for job
printlog:
show jobs name printlog status

(Dub)>show jobs name printlog status
Job: printlog
Package:
Min version: any
Script:
Title:
Start at boot: disabled
Memory limit (Kb): 2024
Stack size (Kb): 1024
Output capture: enabled
Max start attempts: 1
Run state: idle
(Dub)>
19-13

Configuring Jobs: Configuring Dynamic Memory for a Job
19-14
20
Configuring Modules
This chapter includes scenarios that contain step-by-step procedures on how to configure
modules for Remote RMM-1400.

Module Configuration Overview
Installing Modules
Realizing and Configuring Network Elements
Configuring an NE Set
Initiating a Control Action
20-1

Configuring Modules: Module Configuration Overview
Module Configuration Overview

A module is a pre-packaged, turn-key solution built to address a specific area of site
management, such as Power Management or Environmental/HVAC Monitoring and
Control. Each module is composed of individual applications that provide a slice of
functionality and equipment (alarms, measurements, sensors, etc.) used to address a
specific purpose within a module.
The module applications define Network Elements (NEs) that represent physical
equipment at the site. Each NE defines the set of alarms and measurements essential
for effectively managing the operation of that physical piece of equipment. In addition
to NEs, the module and its applications can define parameters that are configuration
items used to customize the operation of the module. Controls are another feature of
modules that provide application-specific logic as well as an interface to allow users to
initiate an action, such as remotely starting a generator.
Once a module is installed, the user must realize or configure an instance of an NE for
each piece of physical equipment at the site. An NE is realized by selecting the NE
type from a list of options provided by the module and then customizing the NE
instance by configuring its associated parameters. The NE type is similar to selecting
the vendor and model of the physical piece of equipment. It is important to note that
many parameters may have a default value, but others may not have a default value.
The module may designate certain parameters to be required, in which case they
must have a value before the NE will transition to the online state and become
functional.
Using NE sets, users can customize the number of instances of NEs of a particular
type based on what actual physical equipment is at a site as compared to the fixed
number of instances that are defined in the module. Once an NE set has been
configured with new instances, the NE will need to be realized, just as the moduledefined NEs must be realized.
20-2

Configuring Modules: Installing Modules
Installing Modules
Use an FTP/SFTP utility to transfer the module to the Remote RMM-1400

staging area
Install the module
Show the installed modules
To install a module:
1. Using an FTP/SFTP utility, transfer the Environmental-1.0.0.tgz module file
from the local workstation to the modules directory on Remote RMM-1400.
2. At the main CLI prompt, install all module files in the staging area:
exec site install

(Dub)>exec site install
The modules Common and Environmental were installed successfully.
(Dub)>
Note: In this example, Environmental-1.0.0.tgz is a module bundle which

contains two individual modules packaged together.
3. (optional) Verify that the module has been installed properly:
show site modules

Module
Version
Description
Date
-----------------------------------------------------------------------------Common
1.0.0
Common Library
2011.09.30 10:31:28
Environmental
1.0.0
Environmental Management
2011.09.30 10:31:42
Tip: To display the applications and details of module Environmental, enter show
site modules Environmental
20-3

Configuring Modules: Realizing and Configuring Network Elements
Realizing and Configuring Network Elements

Realize the indoorTemperature Network Element (NE) and configure

several parameter values
Realize the fan NE and configure a parameter value
Show the NEs
To realize and configure NEs:

1. Select type RMBTemperature for Network Element indoorTemperature:
config site network-element indoorTemperature type RMBTemperature
2. In this example, the RMB at this site has already been configured as peripheral 2.
To customize the module with this data, set the value of parameter
peripheralNumber to 2:
config site network-element indoorTemperature param
peripheralNumber 2
3. Configure thresholds for the high temperature alarm and the low temperature
alarm by setting the values of the parameters highTemperature and
lowTemperature:
config site network-element indoorTemperature param
highTemperature 100
config site network-element indoorTemperature param lowTemperature
50
4. Select type Acme for Network Element fan:

config site network-element fan type Acme
5. In this example, the fan has been wired to the Remote RMM-1400 on discrete
output 2/4. To customize the module with this data, set the value of parameter
outputPoint to 4:
config site network-element fan param outputPoint output 2/4
20-4

Configuring Modules: Realizing and Configuring Network Elements
6. Verify that the network elements are in the online state:

show site network-elements

(Dub)>show site network-elements
Network Element
Category
Type
State
-----------------------------------------------------------------------------door
DoorSensor
offline
fan
VentilationFan
Acme
online
indoorHumidity
HumiditySensor
offline
indoorTemperature TemperatureSensor
RMBTemperature
online
outdoorHumidity
HumiditySensor
offline
outdoorTemperatur TemperatureSensor
offline
smokeDetector
SmokeDetector
offline
7. (optional) Display the details of the NE that includes the list of parameters:
show site network-elements indoorTemperature

(Dub)>show site network-elements indoorTemperature
Name
- indoorTemperature
Description
- Main indoor temperature sensor
Category
- TemperatureSensor
Type
- RMBTemperature
State
- online
InternalState
- Online
Parameters
-----------------------------------------------------------------------------Name
- REF_temperatureUnits
Value
- F
Type
- reference
Description
- Referenced from temperatureUnits. Per-NE configuration of units
is not supported.
Name
Value
Type
Description
highTemperature
100 (configured)
reference
High Temperature Alarming Point
Name
Value
Type
Description
lowTemperature
50
reference
Low Temperature Alarming Point
Name
Value
Type
Description
peripheralNumber
2 (configured)
integer (1 - 12)
Peripheral number for RMB
20-5

Configuring Modules: Configuring an NE Set
Configuring an NE Set
Configure two NEs (instances) in a network element set.
Configure a description for each NE (instance).
Configure a display name for each NE (instance).
Show information for the NE set and NEs (instances).
To configure an NE set:
1. At the main prompt, configure NE (instance) Tenant1Power in NE set
TenantPowerMeter:
config site network-element-set TenantPowerMeter instance
Tenant1Power
Note: NE (instance) names (for example, Tenant1Power) must be unique within

the site. In addition, a module may define a format to which the NE name
must conform. For example, the module may allow you to enter any
characters for the beginning of an NE name but require that the name end
with certain characters (for example, Power).
2. Configure description This is Tenant1Power. for NE (instance) Tenant1Power
in NE set TenantPowerMeter:
Tenant1Power description This is Tenant1Power.
3. Configure display name Tenant1PowerMeter for NE (instance) Tenant1Power in

NE set TenantPowerMeter:
Tenant1Power display-name Tenant1PowerMeter
Note: NE (instance) display names, which are used within the Optima
application, must be unique within the site.
4. Configure NE (instance) Tenant2Power in NE set TenantPowerMeter:
Tenant2Power
5. Configure description This is Tenant2Power. for NE (instance) Tenant2Power

in NE set TenantPowerMeter:
Tenant2Power description This is Tenant2Power.
20-6

Configuring Modules: Configuring an NE Set
6. Configure display name Tenant2PowerMeter for NE (instance) Tenant2Power in

NE set TenantPowerMeter:
Tenant2Power display-name Tenant2PowerMeter
7. (optional) Verify that the NE set has been configured properly:

show site network-elements-sets TenantPowerMeter

(Dub)>show site network-elements-sets TenantPowerMeter
Name
- TenantPowerMeter
Description
- NE Set for TenantPowerMeter
Category
- PowerMeterCategory
Max Elements
- 3
Name Restriction
- (.*Power)
Instances
-----------------------------------------------------------------------------Name
- Tenant1Power
Description
- This is Tenant1Power.
Display Name
- Tenant1PowerMeter
Activity State - Active
Name
Description
Display Name
Activity State
Tenant2Power
This is Tenant2Power.
Tenant2PowerMeter
Active
(Dub)>
8. Realize NE (instance) Tenant1Power and Tenant2Power using scenario

Realizing and Configuring Network Elements on page 20-4.
20-7

Configuring Modules: Initiating a Control Action
Initiating a Control Action

Initiate the control action to turn on the ventilation fan
Show the state of the controls
Note: In this example, the fan network element provides the fan-controller
control. Controls will automatically go to the online state once the host
network element is online and all the controls required parameters that do
not have default values have been configured.
To initiate a control action:
1. Select the run action for control fan-controller:
exec site control-action fan-controller run
2. (optional) Show the current state of all controls:

show site controls

(Dub)>show site controls
Control
Category
State
Admin
-----------------------------------------------------------------------------fan-controller
VentilationFan
Running
enabled
Tip: To display the details for control fan-controller, enter show site controls
fan-controller
20-8
21
Using Configuration Wizards
This chapter provides information on the three available configuration wizards.

Configuration Wizard Overview
Using the initsetup Wizard
Using the bistate-alarms Wizard
Using the serial-port Wizard
21-1

Using Configuration Wizards: Configuration Wizard Overview
Configuration Wizard Overview

A configuration wizard is a script or program accessed from the CLI that prompts you
for configuration information, then generates and applies the associated commands
in running the configuration.
When you execute the command config use-wizard from the CLI, you can set up
a configuration without entering individual CLI commands.
Three wizard scripts are provided to help simplify the configuration process for
Remote RMM-1400:
21-2
A setup wizard for initial connectivity configuration on an unconfigured Remote

RMM-1400
A wizard for common serial port setups
A wizard that configures alarm table entries for bistate points.

Using Configuration Wizards: Using the initsetup Wizard
Using the initsetup Wizard

In this scenario, you will configure the initial setup for Remote RMM-1400 using the
initsetup wizard. The wizard prompts you for all of the required and optional
information.
Note: The running-config file is automatically saved to a network-recovery

file when you run the initsetup wizard and apply the output to the
running-config file. If the running configuration is lost, you can copy file
network-recovery to file running-config to restore the initial system
configuration.
To configure the initial setup:
1. From the main prompt, access the initsetup wizard:
config use-wizard initsetup
The initsetup wizard screen appears:

(Dub)>config use-wizard initsetup
------------------------- initsetup ------------------------This wizard configures initial connectivity settings.
An asterisk (*) in a selection list denotes the default value.
Ctrl-c aborts the wizard.
NOTE:
This wizard provides only basic configuration. For additional
configuration options, consult the command reference guide.
Hostname of this device:
2. Enter the desired hostname.

3. Enter the desired IP address for the device when prompted.
4. Enter the desired subnet mask or mask length when prompted.
21-3

5. (optional) Select (y/N) to add login accounts.
If yes, select whether or not to require strong passwords.
Enter the desired login name and password. If strong passwords are required,
the password must be from 8 to 20 characters and contain at one upper-case,
lower-case and special punctuation character.
Select the desired user profile: 1) supervisor, 2) management, or 3) status.
Select (y/N) whether to add another user.
6. Enter the desired default route when prompted.

7. (optional) Select (y/N) to configure DHCP.
If yes, select the IP address for the DHCP router. Enter 1 to not use the device
IP address (default) or 2 to use the device IP address.
Enter the desired DHCP server settings when prompted. The following settings
are configurable:
DHCP router IP address
Subnet mask or mask length
The lowest address to serve
The number of addresses to serve.
8. (optional) Enter the desired clock settings when prompted. The following settings
are configurable:
The standard timezone
Daylight savings time
The current time and date.
9. (optional) Enter the desired NTP settings when prompted. The wizard asks you
for the primary and secondary server IP addresses.
10. (optional) Enter the desired SNMP v3 user settings when prompted. The following
settings are configurable:
21-4
User name
Authentication protocol
Authentication pass phrase
Privacy protocol
Privacy passphrase
Select (y/N) whether to add another user.

11. (optional) Enter the desired SNMP community settings when prompted. The
following settings are configurable:
The read-only community string
The read-write community string
The SNMP version.

If
SNMP v3 is selected, you will be prompted for the SNMP v3 user name.
You will then select the v3 desired authentication.
12. (optional) Enter the desired SNMP manager information when prompted. The
An IP address
A community string for traps
An SNMP version. If SNMP version 3 or SNMP version 3 inform requests

is selected, then you will be prompted for the type of v3 authentication.
Select (y/N) whether to add another SNMP manager.
13. (optional) Enter the application package server information when prompted. The
An IP address
A package directory on the server
An FTP username and password.
14. For the final step, select one of the following options when prompted:
(a) Apply the settings to running-config
(s) Save the commands to a patch configuration file
(v) View the commands
(c) Cancel
You are returned to the main CLI when complete.
21-5

Using Configuration Wizards: Using the bistate-alarms Wizard
Using the bistate-alarms Wizard

In this scenario, you will configure a bistate point on Remote RMM-1400 with the
bistate-alarms wizard. The wizard prompts you for all of the required and optional
configuration information
Note: This wizard also allows you to configure bistate points on expansion units.
To configure bistate points:
1. From the main prompt, access the bistate-alarms wizard:
config use-wizard bistate-alarms
The bistate alarm entry wizard screen appears:

(Dub)>config use-wizard bistate-alarms
------------------------------------------ bistate alarm entry wizard -----------------------------------------This wizard configures alarm entries for bistate (discrete input) points.
NOTE:
This wizard provides only basic configuration.
options, consult the command reference guide.
For additional configuration
Enter number of the unit containing point(s) to configure.

the base unit. Use 1-12 for a peripheral unit.
Enter unit number (leave blank for base unit):
Use 0 or blank for
2. Enter the desired unit number (0 is the base unit).

The wizard states which point is currently selected and prompts you for:
Choosing a different point (range 1 - 64)
Configuring the selected point
Ending the configuration.
3. (optional) Enter a description for the point when prompted.

4. Enter the desired alarm name when prompted.
5. Select the state of the point when it is alarmed (open/close) when prompted.
6. Select the desired severity level for the alarmed point from the list presented.
7. Enter a new alarm message or accept the default alarm message when
prompted.
21-6

Using Configuration Wizards: Using the bistate-alarms Wizard
8. Enter a new normal state message or accept the default normal state message
when prompted.
9. (optional) Enter the desired nagging interval when prompted.
10. (optional) Enter the desired network element name for the alarm entry when
prompted.
11. (optional) Enter an alarm category for the alarm entry when prompted.
The wizard takes you back to the initial bistate point prompt (configured in step 2).
12. If desired, follow this procedure again to configure another bistate point.
13. When you are finished configuring points, select one of the following options when
prompted:
(c) Cancel.
21-7

Using Configuration Wizards: Using the serial-port Wizard
Using the serial-port Wizard

In this scenario, you will configure an Remote RMM-1400 serial port with the serialport wizard.
To configure an Remote RMM-1400 serial port:
1. From the main prompt, access the serial-port wizard:
config use-wizard serial-port
The serial port wizard screen appears:

(Dub)>config use-wizard serial-port
---------------------------------------- serial port setup wizard ---------------------------------------This wizard configures serial ports.
An asterisk (*) in a selection list denotes the default value.
NOTE:
This wizard provides only basic configuration. For additional
configuration options, consult the command reference guide.
Enter number of the unit containing the port(s) to configure. Use 0 or blank
for the base unit. Use 1-12 for a peripheral unit.
Enter unit number (leave blank for base unit):
Port currently selected is 1
<port number> choose a different port (range 1-4)
(c)
configure this port
(d)
done
Choose option (leave blank to skip this port):
2. Enter the desired port number.

The wizard states which port is currently selected and lists options for:
Choosing a different port (1 - 4)
Configuring the selected port
Ending the configuration.
3. Select one of the options.

4. (optional) Enter a description for the port when prompted.
The wizard lists the default line settings and asks if you would like to accept those
settings.
21-8

5. (optional) Enter the desired line settings. The following settings are configurable:
The line mode
The baud rate
The parity
The number of databits
The number of stop bits.
The wizard asks you to select an application for the serial port. Application options
include terminal server, serial-to-IP, or none (basic async port).
6. Select an application for the serial port.
Note: The remaining prompts for the serial port configuration will vary based
upon the application you select.
7. Enter the desired values for the application as prompted.
8. If desired, follow this procedure again to configure another serial port.
9. When you are finished configuring the ports, select one of the following options
when prompted:
(c) Cancel.
21-9

21-10
A
Command Identifications
Command identifications are used when including and excluding commands for a
user-defined profile. The IDs are contained in the supervisor command tree. For
information on configuring user-defined profiles, see Creating a Custom Profile on
page 3-6.
The following are some of the valid command identifications for Remote RMM-1400:
Commands
Identifications
config
/config
config action
/config/action
config alarm-entry
/config/alarm-entry
config apply-patch
/config/apply-patch
config banner
/config/banner
config clock
/config/clock
config clock daylight-savings
/config/clock/daylight-savings
config clock local-time
/config/clock/local-time
config clock timezone
/config/clock/timezone
config controller
/config/controller
config controller bridge
/config/controller/bridge
config controller ethernet
/config/controller/eth
config controller ethernet assign
/config/controller/eth/assign
config controller ethernet bridge
/config/controller/eth/bridge
config controller ethernet description
/config/controller/eth/description
config controller ethernet disable
/config/controller/eth/disable
config controller ethernet enable
/config/controller/eth/enable
config controller ethernet

hardware-address
/config/controller/eth/hwaddr
A-1

Command Identifications:
A-2
Commands
Identifications (Continued)
config controller ethernet mac-security
/config/controller/eth/mac-security
config controller ethernet proxy-arp
/config/controller/eth/proxy-arp
config controller ethernet speed
/config/controller/eth/speed
config controller ethernet unassign
/config/controller/eth/unassign
config controller openvpn
/config/controller/openvpn/
config controller serial (wan)
/config/controller/wan
config correlation
/config/correlation
config dhcp-relay
/config/dhcp-relay
config dhcp-server
/config/dhcp-server
config discrete
/config/discrete
config event
/config/event
config hostname
/config/hostname
config interface
/config/interface
config interface bridge
/config/interface/bridge
config interface ethernet
/config/interface/eth
config interface ethernet description
/config/interface/eth/description
config interface ethernet disable
/config/interface/eth/disable
config interface ethernet enable
/config/interface/eth/enable
config interface ethernet ip
/config/interface/eth/ip
config interface openvpn
/config/interface/openvpn
config interface serial
/config/interface/wan
config ip
/config/ip
config ip arp
/config/ip/arp
config ip domain-name
/config/ip/domain-name
config ip name-server
/config/ip/name-server
config ip route
/config/ip/route

Commands
config route-v6
/config/ip/route-v6
config iptables
/config/iptables
config jobs
/config/jobs
config meas-table
/config/meas-table
config mediation
/config/mediation
config ntp
/config/ntp
config ntp disable
/config/ntp/disable
config ntp enable
/config/ntp/enable
config ntp poll-interval
/config/ntp/poll-interval
config ntp server
/config/ntp/server
config peripheral
/config/peripheral
config pkgs
/config/pkgs
config profile
/config/profile
config profile copy
/config/profile/copy
config profile exclude
/config/profile/exclude
config profile include
/config/profile/include
config profile priv-lvl
/config/profile/priv-lvl
config ras
/config/ras
config ras accounting
/config/ras/accounting
config ras authorization
/config/ras/authorization
config ras retry
/config/ras/retry
config ras server
/config/ras/server
config ras shell
/config/ras/shell
config ras timeout
/config/ras/timeout
config remote-access
/config/remote-access
config response
/config/response
A-3

A-4
Commands
config snmp
/config/snmp
config site control
/config/site/control
config site module
/config/site/module
config site network-element
/config/site/network-element
config site network-element-set
/config/site/network-element-set
config site network-elements

status-points
/config/site/network-element/statuspoints
config site param
/config/site/param
config snmp auth-trap
/config/snmp/auth-trap
config snmp community
/config/snmp/community
config snmp host
/config/snmp/host
config tbos
/config/tbos
config timeout
/config/timeout
config use-wizard
/config/use-wizard
config users
/config/users
config users add
/config/users/add
config users delete
/config/users/delete
config users password
/config/users/password
copy
/copy
debug
/debug
debug ethernet
/debug/ethernet
debug ethernet all
/debug/ethernet/all
debug ethernet controller
/debug/ethernet/controller
debug ethernet interface
/debug/ethernet/interface
debug level
/debug/level
debug mediation
/debug/mediation

Commands
debug serial
/debug/serial/
diag
/diag
diag break
/diag/break
diag clear
/diag/clear
diag controller
/diag/controller
diag fan
/diag/fan
diag ip route show
/diag/ip/route/show
diag ip route-v6 show
diag/ip/route-v6/show
diag line-monitor
/diag/line-monitor
diag line-status
/diag/line-status
diag mediation
/diag/mediation
diag mmdisplay
/diag/mmdisplay
diag output
/diag/output
diag peripheral
/diag/peripheral
diag ps
/diag/ps
diag snapshot
/diag/snapshot
diag tcpdump
/diag/tcpdump
diag test
/diag/test
diag top
/diag/top
diag who
/diag/who
diag whoami
/diag/whoami
erase
/erase
exec site control-action
/exec/site/control-action
exec site install
/exec/site/install
exec site uninstall
/exec/site/uninstall
exec-job
/exec-job
A-5

A-6
Commands
exit
/exit
halt
/halt
help
/help
password
/password
ping
/ping
reload
/reload
running-config
/running-config
show
/show
show actions
/show/actions
show alarm-entries
/show/alarm-entries
show audit
/show/audit
show banner
/show/banner
show bootp
/show/bootp
show clock
/show/clock
show compact-flash
/show/compact-flash
show config-file
/show/config-file
show connections
/show/connections
show controllers
/show/controllers
show correlations
/show/correlations
show debugging
/show/debugging
show dhcp-relay
/show/dhcp-relay
show dhcp-server
/show/dhcp-server
show discrete
/show/discrete
show events
/show/events
show expansion-images
/show/expansion-images
show interfaces
/show/interfaces

Commands
show inventory
/show/inventory
show ip
/show/ip
show iptables
/show/iptables
show jobs
/show/jobs
show listeners
/show/listeners
show log-file
/show/log-file
show meas-table
/show/meas-table
show mediation
/show/mediation
show ntp
/show/ntp
show peripherals
/show/peripherals
show pkgs
/show/pkgs
show product
/show/product
show profiles
/show/profiles
show pydoc
/show/pydoc
show ras
/show/ras
show remote-access
/show/remote-access
show resource-tracking
/show/resource-tracking
show responses
/show/responses
show running-config
/show/running-config
show site controls
/show/site/controls
show site modules
/show/site/modules
/show/site/network-elements
show site network-elements-sets
/show/site/network-elements-sets

status points
/show/site/network-elements/statuspoints
show site params
/show/site/params
A-7

A-8
Commands
show snmp
/show/snmp
show tbos
/show/tbos
show test
/show/test
show timeout
/show/timeout
show users
/show/users
show version
/show/version
ssh
/ssh
telnet
/telnet
trace-route
/trace-route
Glossary
Symbols
__init__.py
The __init__.py file is required in the script package for each module directory so that
Python will recognize and search the directory for Python code. Content is not
required in the file; however, it generally contains a Python document string. If Python
module subdirectories are not used, this file does not need to exist.
A
action
An action is a correlation between an event and response that controls system
alarming, logging and connection behavior on Remote RMM-1400.
AID
AID is an acronym for access-identifier. It identifies the NE system component to
which an alarm applies.
alarm affect
The alarm affect designates an alarm as service-affecting or non-service-affecting.
Glossary-1
Glossary
alarm class
An alarm class is a designation of an alarm as environmental or equipment-related.
Alarms designated as environmental signal the occurrence of events such as
temperature or pressure changes. Alarms designated as equipment-related signal the
occurrence of events such as device failures or malfunctions.
alarm code
The alarm code identifies the severity of an automatic alarm message based on a
condition. The alarm conditions are critical (CR), major (MJ), minor (MN) and
nonalarmed (NA).
alarm message
The alarm message is the text displayed for an alarm when a specified environmental
event occurs.
alarm type
The alarm type is the value for an environmental alarm response. For valid alarm type
values, refer to the Bellcore GR-833-CORE documentation.
analog reporting interval

The analog reporting interval is the rate at which events are generated for an analog
input.
analog input
Analog inputs monitor input current and support five different events that represent
input current transitions.
application mode
The application mode sets up a serial controller as a destination for internal
connections or gives the controller the ability to initiate internal connections when a
system event occurs.
Glossary-2
Glossary
asynchronous
Asynchronous transmission (or async) refers to a simple protocol where the
transmitting device does not need to be synchronized with the receiving device. The
transmitter can send data when data is ready to be sent. Each character of this data
contains start and stop bits, which indicate the beginning and end of each character.
B
band
The band sets the high and low threshold values for analog input event generation.
banner
The banner is the initial text that appears when the user logs into Remote RMM-1400.
baud rate
The baud rate is the speed of a connection in bits per second.
bit-level encoding
Bit-level encoding is the method by which binary codes represent characters of data.
T1 lines have available linecode options Binary 8 Zeros Substitution (B8ZS) and
Alternate Mark Inversion (AMI). E1 lines have available linecode options High Density
Bipolar Three (HDB3) and Alternate Mark Inversion (AMI).
boolean
An expression whose value can be either true or false.
Glossary-3
Glossary
bridge controller
A bridge controller groups controllers into an Ethernet bridge group. The controller is
named bridge switch because it is a bridge that (by default) includes all eight of the
Ethernet switch ports. Controller bridge switch can be configured to include or
exclude Ethernet, serial and WAN ports.
bridge group
A bridge group is a set of controllers assigned to a single bridge unit and network
interface. Each bridge group runs a separate Spanning Tree and is addressable using
a unique IP address.
bridge interface
The bridge interface routes packets to and from the bridge controller.
C
CDMA
Code Division Multiple Access (CDMA) is a digital technology that uses spread
spectrum techniques for transmitting voice or data over the air. Spread spectrum
technology separates users by assigning digital codes within the same broad
spectrum. The benefit of CDMA is that it provides higher user capacity and immunity
from interfering signals. CDMA is available in 800 megahertz or 1900 megahertz
frequencies.
central alarm table

The central alarm table is a table that maintains the state of all alarms on Remote
RMM-1400. It can be configured to communicate alarm state changes in a variety of
management protocols.
Glossary-4
Glossary
channel group
A channel group consists of one or more channels in a T1/E1 link grouped together as
a high-speed virtual path. A channel group treats all 24 channels of the T1 and all 32
channels of an E1 as a single data stream. A user can create one channel group for
each serial controller.
chat file
A chat file contains the connection initialization string for ports that are configured for
PPP encapsulation. It is stored in the /config/chat directory on Remote RMM-1400.
The user must FTP the chat file to the /config/chat directory on Remote RMM-1400
prior to configuring the file as the connection initialization string.
CLI
Command line interface. A user interface whereby the user types one line of
instructions at a time at a command prompt.
CLI session timeout

The command line interface (CLI) session timeout is the amount of time (in minutes)
that can elapse before an Remote RMM-1400 session expires due to inactivity.
clock source
The clock source determines how a serial controllers clock is set. The two options are
loop and internal. The loop option frames Remote RMM-1400 controller packets
based on the line timing from the incoming T1 link. The internal option frames Remote
RMM-1400 controller packets based on the Remote RMM-1400 generated clock.
community string
A community string is a password used with the SNMP protocol that is used for both
read-only and read-write privileges.
condition type
A condition type refers to an alarm type that is based on standards listed in the
Bellcore GR-833-CORE documentation.
Glossary-5
Glossary
configuration wizard
A configuration wizard is a user-friendly utility accessed from the CLI that prompts the
user for configuration information, then generates and applies the associated
commands in the running configuration.
connection mode
The connection mode specifies how an asynchronous serial controller determines
that it is up (for example, has an asynchronous connection).
connection string
The connection string is a string of characters sent to the attached device at
initialization by an Remote RMM-1400 asynchronous serial controller. Depending on
the connection settings, this string may or may not be sent to the attached device.
controller
A controller is a concept that is applied throughout the CLI. It is a software object on
Remote RMM-1400 that sends and receives a stream of bytes. A controller can be a
physical device, such as an Ethernet transceiver or a T1 framer, or it can be a virtual
entity, such as a T1 channel group.
cost
Cost is a metric used in spanning tree calculations to determine the best path for
reaching a destination. The higher a path's cost, the less desirable it is to use that
path and the more likely the spanning tree algorithm is to disable the port if a network
loop occurs.
cut-through
Cut-through support lets users connect directly to a serial port and issue commands
directly to network elements.
Glossary-6
Glossary
D
data bits
Data bits are the number of bits per character transmitted or received by an
asynchronous serial controller.
daylight savings
Daylight savings time is when clocks are set ahead one hour the first Sunday in April
and back one hour the last Sunday in October to provide an extra hour of daylight
during summer.
default lease time

The default lease time is the amount of time, in seconds, a device can use an IP
address assigned by the DHCP server. The default lease time is assigned to a device
when no other lease time is specified by the user.
default static route

The default static route is used to route a packet to a destination when there is no
other better route in the IP routing table.
delimiting character
The delimiting character defines the beginning and ending of the banner. Most
characters, such as (, @, #, ~, %, * and ), can be applied as the delimiting character.
destination address
In a static route, the destination address is the IP address of the network.
DHCP authority mode

The DHCP authority mode configures the DHCP server to respond to misconfigured
DHCP clients with DHCP negative acknowledgement (DHCPNAK) messages. If this
option is not configured, the client must wait until the old IP address lease has expired
before obtaining correct IP address information after moving to a new subnetwork.
Glossary-7
Glossary
DHCP broadcast mode

The DHCP broadcast mode configures the DHCP server to send DHCP request
responses as broadcast packets instead of unicast packets.
DHCP protocol
The DHCP protocol lets a host that is unknown to the network administrator
automatically access a new IP address for its network. The network administrator
allocates address pools in each subnet and enters them into the DHCP configuration
file.
DHCP server
The DHCP server provides automatic IP address and network configurations to
remote devices. For example, the DHCP server can provide dynamic IP address
information to a technicians laptop.
DHCP server host

The DHCP server host is a host that is served by the DHCP server. It can access and
obtain IP address and network configurations from the server.
digital input
Digital inputs generate two events that reflect the state of the input: open and close.
disconnect mode
The disconnect mode is a handshake from a device attached to Remote RMM-1400
that terminates or accepts termination of an asynchronous connection.
discrete alarm
Digital discrete alarms are basic open or closed circuits where no data communication
is involved. Monitored devices have either a set of dry or wet contact closure outputs.
The outputs from the monitored devices are relay switches that close or open upon a
given alarm condition. They are called dry when the monitored device (a network
element) does not apply voltage to the alarm connection. They are called wet when
the monitored device applies voltage to the alarm connection.
Glossary-8
Glossary
discrete expansion peripheral

A discrete expansion peripheral is a component that allows the user to add additional
discrete inputs, analog inputs and relay outputs to Remote RMM-1400s configuration.
These additional I/O points are managed through Remote RMM-1400.
discrete peripheral unit

The discrete peripheral unit is a space on Remote RMM-1400 that holds the I/O
configuration information for a discrete peripheral. Units are numbered 0 to 4, with 0
representing the on-board discrete I/O subsystem.
domain name
Domain names are used to represent IP addresses on a network and are formatted
as a series of alphanumeric characters separated by periods (for example,
www.domainname.com).
DNS server
A DNS server translates alphanumeric addresses into corresponding IP addresses.
DTR signal
DTR is a control signal on an Remote RMM-1400 asynchronous RS-232 serial port.
E
encapsulation
Communications encapsulation is a method for transmitting multiple protocols within
the same network. The frames of one type of protocol are carried within the frames of
another. The available communications encapsulation formats for Remote RMM-1400
are HDLC and PPP.
Glossary-9
Glossary
EvDO
EvDO (Evolution-Data Only) is an upgraded version of the cdma2000 system. The
1xEvDO system uses the bandwidth of one or more 1.23 MHz radio channels as the
existing cdma2000 system. It provides for multiple voice channels and medium rate
data services. The EvDO version changes the modulation technology to allow for a
maximum data transmission rate of approximately 2.4 Mbps on the forward channel.
The EvDO system uses the same reverse channel, which limits the uplink data
transmission rate to approximately 200 kbps. The EvDO system has an upgraded
packet data transmission control system that allows for bursty data transmission
rather than for more continuous voice data transmission. The industry standard for
EvDO is IS-856.
event
An event is an incident that is triggered by an external or internal event. An event can
be anything from a discrete input opening or closing, a serial controller going up or
down, a TCP connection request, or a power supply failure.
event correlation
Event correlation provides the ability to define a unique condition by comparing the
states of multiple events and aggregating them into a single event.
event originator
An event originator is the system component that generates an event.
event type
An event type identifies the cause of the generated event.
Glossary-10
Glossary
F
filter
A filter is an intermediate connection point that performs a processing operation on
data passing through a mediation connection. A telnet filter is a telnet session to a
device that does not support Telnet, such as a craft port on an NE, to function
smoothly.
flow control
Flow control allows a receiving device to tell a sending device to stop sending data
when the data comes in faster than the receiver can process it and to start sending it
when the receiver is ready.
framing
Framing is an error control procedure with multiplexed digital channels, such as T1,
where bits are inserted so that the receiver can identify the timeslots that are allocated
to each subchannel. Refer to the Remote RMM-1400 Command Reference Guide for
information on the framing formats Remote RMM-1400 utilizes.
FTP
FTP (File Transfer Protocol) is a communications protocol that governs the transfer of
files from one computer to another over a network.
G
gateway address
The gateway address is the IP address of the next node location in a route.
Glossary-11
Glossary
GPRS
GPRS (General Packet Radio Service) is a packet-switched mobile datacom service
that is widely expected to be the next major step forward in the evolution of GSM
technology. It enables high-speed mobile datacom and is most useful for data
applications such as mobile internet browsing, e-mail and push technologies. It has
demonstrated transmission rates as fast as 115Kbps.
H
hello time
The hello time is the interval between the generation of configuration bridge PDUs
when the bridge is either the root bridge or when it is trying to become the root bridge.
history runs
The history runs is the number of history entries kept for a job.
HSPA
High Speed Packet Access (HSPA) is a collection of mobile telephony protocols that
extend and improve the performance of existing UMTS (Universal Mobile
Telecommunications System) protocols.
HTTP
HTTP (Hypertext Transfer Protocol) provides a standard for Web browsers and
servers to communicate. It provides less security for sensitive information than
HTTPS.
HTTPS
HTTPS (Hyper Text Transfer Protocol Secure) provides the necessary security to
protect sensitive data. On Remote RMM-1400, HTTPS is implemented by
incorporating an SSL layer that encrypts the HTTP packets between the web server
and client/browser.
Glossary-12
Glossary
hysteresis
Hysteresis is a guard region around high and low thresholds on an analog input that
prevents rapid generation of events when input current oscillates rapidly across the
threshold.
I
inactivity timeout
The inactivity timeout sets the frequency (in minutes) that RX statistics will be
checked on a link in the event that a wireless service provider does not provide lcprequests (keep alives) in their network, or imposes time limitations on the network
connections.
interface
An interface is another concept that is applied throughout the CLI. It is an entity to
which you can route IP packets. An interface must be associated with a controller,
which may be an underlying physical port.
IP forwarding
IP forwarding allows IP packets received on an interface to be forwarded to other
interfaces.
IP routing table
The IP routing table is a database in a router that keeps track of paths to particular
networks and network destinations. More specifically, it associates network
addresses with gateway addresses.
Iptables
Iptables is the method by which IP packets are filtered or manipulated for Remote
RMM-1400. IP packets are filtered or manipulated using three iptables: filter, which
filters IP packets, mangle, which manipulates IP packets and NAT, which routes IP
packets.
Glossary-13
Glossary
J
job
A job contains the specifications for running an instance of a script. It refers to a script
defined within a package and specifies the parameters for execution on Remote
RMM-1400.
job property
A job property is a runtime parameter for a job on Remote RMM-1400. These
properties are used within a Python script.
job task
A job task is an optional initialization step for a job before it runs a script. Tasks are
used when a super user is required for job configuration, since scripts cannot be run
by a privileged user on Remote RMM-1400.
K
keep-alive disconnect time
The keep-alive disconnect time defines the number of seconds that a peer receives
no packets before it is considered to be disconnected. Valid values are 20 to 3600.
keep-alive inactivity time

The keep-alive inactivity time defines the number of seconds that a session must be
inactive before a ping packet is transmitted. Valid values are 5 to 60.
Glossary-14
Glossary
keep-alive packets
Keep-alive packets are sent from both the client and server when no user data is
being transmitted. When one side of the connection fails to receive packets, a
notification is sent to indicate a disconnected peer. These packets also maintain an
active firewall state.
L
LCP echo request
An LCP echo request is a packet sent from a client-side controller to a server-side
controller to signal if a PPP link is still available. PPPD stops if LCP echo requests are
not received by the server. LCP echo requests are sent only if LCP is enabled.
line buildout
Line buildout refers to the length of the cable (in feet) that is connecting the devices
on each end of a T1 line or the level of attenuation (in decibels) required for the
devices on each end of a T1 line to communicate. Buildout is usually specified by
cable length for shorter connections and by level of attenuation for longer
connections.
linemode
Linemode is the type of hardware connection of an asynchronous link. There are two
values for linemode: RS232 and RS422. RS232 is a set of standards that specify the
type of interfaces connected to an asynchronous controller. The three types of
interfaces are electrical, functional and mechanical, which are used for
communicating to computers, terminals and modems. RS422 is a standard that
defines a balanced interface that does not accompany a physical connector.
local identity
The local identity is supplied by the local site and sent to a remote device. The identity
is similar to a user name for CHAP and PAP authentication on a point-to-point
connection.
Glossary-15
Glossary
local method
The local method specifies the protocol Remote RMM-1400 uses to authenticate a
peer device on a serial controller PPP link. The two available methods are challenge
handshake authentication protocol (CHAP) and password authentication protocol
(PAP).
local secret
The local secret is supplied by the local site and sent to a remote device. The secret is
similar to a password for CHAP and PAP authentication on a point-to-point
connection.
M
MAC address
A MAC address is the address for a device as it is identified at the Media Access
Control layer in the network architecture.
MAC address capture

MAC address capture refers to the process of listening to traffic on an Ethernet
controller and then adding any MAC addresses learned to the controllers MAC
address table.
MAC address table

A MAC address table is a list containing the MAC addresses of all the devices that are
permitted access to Remote RMM-1400 through an Ethernet controller. A MAC
address table can contain a maximum of 32 MAC addresses.
management information base

A Management Information Base (MIB) is a repository of characteristics managed in a
network device. Each managed device knows how to respond to standard queries
issued by network management protocols (such as SNMP).
Glossary-16
Glossary
maximum current
The maximum current is the highest valid current allowed on a specified analog input
and the sensor value associated with that current.
maximum lease time

The maximum lease time is the maximum amount of time, in seconds, a device can
use an IP address assigned by the DHCP server.
mediation connection
Mediation connections are connections that allow the interconnection of different
protocols. The protocols on each side are terminated in the middle so that the
interconnection can occur.
minimum current
The minimum current is the lowest valid current that will be present on the specified
analog input and the sensor value associated with that current.
MRU
The MRU sets the maximum number of data bytes that can be received in a single
PPP frame on a WAN port.
MTU
The MTU sets the maximum number of data bytes that can be transmitted in a single
PPP frame on a WAN port.
Glossary-17
Glossary
N
nagging
Nagging is the process of repeatedly generating an alarm message at fixed intervals
even in the absence of an alarm state change. This is particularly useful for SNMP
traps which do not provide guaranteed delivery.
nagging interval
The nagging interval configures the number of seconds between instances of an
alarm sending its state to all enabled protocols.
nagging level
The nagging level defines the severity level at which an alarm will repeatedly send its
state to all enabled protocols.
Network Address Translation

Network Address Translation (NAT) is an iptables chain that allows multiple devices
on a private network to share a single, globally routable public address.
network element
A network element is a processor controlled entity on the telecommunications
network that provides switching and transport network functions and contains network
operations functions.
network element set

An NE set provides a way to customize the number of instances of NEs of a particular
type based on what actual physical equipment is at a site as compared to the fixed
number of instances that are defined in the module. Once an NE set has been
configured with new instances, the NE will need to be realized, just as the
module-defined NEs must be realized.
Glossary-18
Glossary
notification code
The notification code provides an indication of the severity of an alarm.
NTP polling interval

The minimum and maximum NTP polling intervals indicate the timeframe each host
on a network has to connect to the NTP server to retrieve and transmit data.
NTP server
An NTP server maintains a common clock time among hosts within a network.
O
OID
OID (Object Identifier) points to a specific parameter in the SNMP agent.
offset
When configuring the timezone for Remote RMM-1400, offset is the number of hours
and minutes difference between the desired time zone and the default time zone,
which is standard GMT +0.00.
OpenVPN
OpenVPN is a software package that establishes a VPN between an AI VPN server
and AI network element clients. SSL is used to manage the VPN connection and
encrypted UDP packets for data transmission. Both the management and data traffic
are passed as UDP packets on a single port. The customers external firewall needs
to open one UDP port for all connected client network elements.
Glossary-19
Glossary
originator
An originator is a physical and visible component within Remote RMM-1400 that
generates the event, such as an analog input or digital input, serial controller, or
Ethernet controller.
output signal
There are two types of output signals on Remote RMM-1400 asynchronous serial
ports: DTR and RTS. DTR and RTS may be used as part of the connect and
disconnect handshake. RTS may be used for hardware flow control.
P
package manifest
The package manifest is an XML file that serves as a table of contents for the
attributes of a script package.
packet framing
Packet framing refers to the method by which packets are sent over a serial line.
Framing options for T1 serial lines are D4 and ESF. Framing options for E1 serial lines
are CRC4, no-CRC4, multiframe-CRC4 and multiframe-no-CRC4.
parity
Bit parity is the process for detecting whether or not bits of data have been altered
during data transmission.
peripheral device
A peripheral device is a system component that expands Remote RMM-1400s
functionality. The only peripheral device currently available for Remote RMM-1400 is
the discrete expansion peripheral, which adds additional I/O points that are controlled
by Remote RMM-1400.
Glossary-20
Glossary
peripheral management subsystem

The peripheral management subsystem is the subsystem that lets Remote RMM1400 manage up to 12 discrete expansion peripherals at remote locations.
PID
A PID is a password.
position
A position indicates where in the list order a task should appear and when it should be
executed.
PPP
PPP (Point to Point Protocol) is a data link level protocol typically used to encapsulate
network level packets over an asynchronous serial line.
PPPoE
PPPoE (Point-to-Point Protocol over Ethernet) is a protocol for encapsulating PPP
frames in Ethernet frames. PPPoE is used to virtually dial to another Ethernet
machine, making a point to point connection. This connection can then be used to
transport IP packets, based upon the features of PPP.
preferred roaming list (PRL)

On a CDMA/EvDO cellular modem, the PRL (Preferred Roaming List) is used to
configure the radio channels and network carriers used by the modem. When carriers
change their networks, it is useful to update the PRL to pick up the changes.
priority level
The priority level determines which interface within a standby group will become the
master router. The higher the priority level, the more likely an interface will become
the master router. A priority level of 255 specifies that an interface will become the
master router.
Glossary-21
Glossary
profile
A profile gives a user designated permissions for operating commands in Remote
RMM-1400. User profiles can be status, management, supervisor, or restricted.
Python package
A Python package is a directory used to store Python modules. The package can
contain subpackages, resulting in a hierarchical directory structure. Each package
directory must include a file named __init__.py to indicate to Python that this is a
package. However, the file can be empty.
R
raw alarm output
Raw alarm output is an Remote RMM-1400 alarm format that contains all information
about the alarm and the event that caused it. It can be used for alarm formats that are
not directly supported by Remote RMM-1400. A script or application can take the
alarm information from the raw output and translate it into any type of alarm message.
relay output
Relay outputs can close or open an external circuit to cause connected devices to
respond.
remote access protocol

The remote access protocol defines the methods for establishing a CLI session and
transferring files.
remote identity
The remote identity is supplied by a remote device and sent to the local device.
Glossary-22
Glossary
remote method
The remote method specifies the protocol a peer device uses to authenticate Remote
RMM-1400 for a controller PPP link.
remote secret
The remote identity secret is supplied by a remote device and sent to the local device.
required task property

A required task property is a value dependent on the task type required for a job. Both
the ifconfig and serversocket task types have their own required properties defined
within the package manifest XML, which are needed to run a job.
responder
A responder is a visible component within Remote RMM-1400, such as a serial or
Ethernet controller, that implements responses.
response
A response is an executed result associated with a system event by configuration of
an action rule on Remote RMM-1400.
response type
A response type defines the activity that can be executed by the responder, such as
disable, enable, or close.
restart attempts
The number of times Remote RMM-1400 will attempt to restart a job if it stops
abnormally.
RTS signal
The RTS signal is a control signal that may be used as part of the connect and
disconnect handshake or for hardware flow control. The RTS signal is ignored if flow
control is enabled.
Glossary-23
Glossary
running configuration
The running configuration (current Remote RMM-1400 configuration) displays the
current user modifications to the configuration.
S
script
A script is a Python class that defines a run and stop method, which implements the
scripting interface on Remote RMM-1400. A script can define job properties, which
pass runtime parameters and/or settings (such as, connection information for a
network element, baud rates, TIDs, phone numbers, software version and user name
and password information) to Remote RMM-1400 when a job is executed. In addition,
a script can define job tasks and the properties required to request IP configuration for
a device or open a server socket connection to receive and transmit data.
script package
A script package is a compressed file that stores Python modules, Python packages
and the Package Manifest file. The modules included in the script package will be
referenced by jobs, which are configured to run on Remote RMM-1400.
secret
A secret is a shared encryption key that matches the encryption key configured on the
server to provide secure access.
secure sockets layer

The Secure Sockets Layer (SSL) is the dominant security protocol for Internet/Web
monetary transactions and communications. Information being transmitted is
encryptedonly the client and the server at the other end have the encryption key.
Glossary-24
Glossary
service effect
The service effect is the effect on customer telephone service of the condition
reported by an alarm.
SNMP
Simple Network Management Protocol (SNMP) is a standard specification for
exchanging information between Remote RMM-1400 and a monitoring system.
SNMP management station

Management stations are used to oversee network activity generated by SNMP
agents, which are hardware and/or software processes that report on each network
device. The trap table is a list of all available management stations.
SNMP management system

An SNMP management system is a system that can manage virtually any network
type. It is widely deployed in TCP/IP networks, but actual transport independence
means it is not limited to TCP/IP.
SNMP trap
SNMP traps are SNMP alarm messages.
SNMP trap queue

The SNMP trap queue saves SNMP traps when network connectivity is lost. When
the network comes back up, the SNMP traps are sent. This feature accommodates
wireless connections on Remote RMM-1400, which are less reliable than regular
connections. When trap queuing is enabled, pings are sent to SNMP hosts before
traps are sent. Traps are queued when the ping to the SNMP host fails.
Spanning Tree Protocol

The Spanning Tree Protocol deactivates links between networks so that information
packets are channeled along one path and do not search endlessly for a destination.
Glossary-25
Glossary
SSH
Secure Shell Protocol. An encrypting data transmission protocol used particularly for
encryption of terminal connections. SSH permits secure remote access over a
network from one computer to another.
staging area
The staging area is the pkgstage directory on Remote RMM-1400 that stores script
packages prior to their installation.
stop bits
A stop bit is a zero bit appended to a character transmitted on an asynchronous port.
T
TACACS+
TACACS+ is a protocol that provides remote user authentication.
task position
A task position is the order in which a task will be executed within Remote RMM-1400.
The position indicates where in the list a task should appear. Unless a user specifies a
new position for a task, Remote RMM-1400 adds new tasks to the end of the list.
task property
A task property is a required or optional parameter for a task. These parameters differ
depending on the task type (ifconfig or serversocket) configured for a task.
task type
There are two types that can be assigned to a task. The task type ifconfig creates a
subinterface for the job, which lasts for the lifetime of the job. The task type
serversocket binds a socket for the lifetime of the job.
Glossary-26
Glossary
text block
A text block is a field of an alarm response. The text block is a quoted text line in the
response block of an autonomous message. The exact format of a text block varies
based on the type of autonomous message being created. For more information
about the exact text block formats for different types of autonomous messages, refer
to the Bellcore GR-833-CORE documentation.
TID
The TID is the target identifier.
trap
A trap is an SNMP alarm message.
U
UID
The UID is the user name.
UMTS
UMTS (Universal Mobile Telecommunications System) is one of the third-generation
(3G) cell phone technologies, which is also being developed into a 4G technology.
units
Units is the unit name for measurements associated with analog inputs.
user datagram protocol

The user datagram protocol (UDP) is part of the TCP/IP protocol suite. It was created
to provide a way for applications to access the connectionless features of IP. UDP
provides for exchange of datagrams without acknowledgements or guaranteed
delivery. This protocol is normally bundled with IP-layer software.
Glossary-27
Glossary
V
Varbind
In an SNMP message, a varbind consists of a sequence of two fields: an Object ID
and the value for/from that Object ID.
VLAN
The term VLAN is specified by IEEE 802.1Q. It defines a method of differentiating
traffic on a LAN by tagging the Ethernet frames. By extension, VLAN is used to mean
the traffic separated by Ethernet frame tagging or similar mechanisms.
VPN client
The VPN client is the device that requests for a VPN session to be established on the
VPN network.
VPN server
The VPN server is a device that provides a VPN session to clients on the VPN
network.
W
WAN
Wide Area Network (WAN) is a computer network that covers a broad area (i.e., any
network whose communications links cross metropolitan, regional, or national
boundaries).
Glossary-28
Glossary
wireless backhaul
Wireless backhaul is the wireless connection from an individual base station (tower)
to the central network (backbone). The Kentrox wireless backhaul solution layers a
VPN on top of the wireless network. The VPN network is a logical extension of the
overall private management network.
Glossary-29
Glossary
Glossary-30
Index
A
accessing
CLI locally 2-2
help 2-2
web interface 2-8
accessing the CLI
using local connection 2-2
action
command example 10-5
components 10-5
configuring 10-6
description 10-2
alarm
nagging 13-2
reporting 13-2
simulation 13-17
alarm table
central 13-2
description 13-2
features 13-2
test mode 13-17
analog
adjustment 13-7
averaging 13-7
B
banner
configuring 2-4
bi-state points
configuring 21-6
BOOTP/DHCP relay
configuring 16-9
C
central alarm table
protocol formats 13-3
raw alarm support 13-3
SNMP support 13-3
CHAP 1-16
CLI
accessing with remote connection 2-7
commands
excluding 3-6
including 3-6
configuration
factory 4-4
file 4-3
fragment 4-3
running 4-2, 4-5
configuring
alarm entry 13-4, 13-9, 13-11
alarms for expansion peripheral 17-11

asynchronous serial to asynchronous
serial connection 15-10
asynchronous to TCP connection 1513
banner 2-4
BOOTP/DHCP relay 16-9
central FTP package server 19-4
CLI session timeout 2-5
custom profile 3-6
default route 2-5
DHCP server 11-4, 16-4, 16-6
domain name 5-2
event, response, action 10-6
expansion peripherals 17-7
GPRS 8-5
host name 2-5
host on DHCP server 16-8
I/O points for discrete expansion
peripheral 17-9
initial setup using wizard 21-3
IP address 2-5
IP settings 5-2
IPTables 11-6
IPv6 settings 5-4
jobs 19-1, 20-1
measurement table entry 14-4
network element sets 20-2, 20-6
NTP 5-5
OpenVPN 8-8
ppp encapsulation settings 8-6
remote access protocol 2-5
script package 19-5
serial port using wizard 21-8
session timeout 2-5
SiteBus devices 17-16
SNMP event template 18-5
SNMP measurement template 18-11
SNMP NE 18-15
SNMP point template 18-6, 18-9
SNMP to manage a relay output 17-13
SSH to asynchronous serial
connection 15-8
static routes 7-1
strong password 3-3
system clock parameters 5-5
TCP connection 15-4
Telnet 13-15, 15-6
VPN 8-8
wireless modem 8-5
wireless network 8-1
Connect SCS 8-2, 8-3
controller
bridge 6-2
definition 6-2
Ethernet 6-2
OpenVPN 6-2
serial 6-3
types 6-2
copy
network recovery file 4-5
correlation expression
configuring a time period 12-5
evaluation 12-4
operators 12-4
originator types and states 12-3
term 12-3
D
DHCP server
configuring 16-4
configuring a host 16-8
configuring subnet 16-6
example 16-3
Director SCD 8-2, 8-3
E
Ethernet 6-3
controllers 6-2
interfaces 6-3, 6-4
ports 1-4, 6-2, 6-3, 1-4
event
alarm associations 13-2
command example 10-3
components 10-3
configuring 10-6
correlation 12-2
description 10-2
event correlation
components 12-2
configuring 12-6
description 12-2
expression components 12-3
expression example 12-3
H
help
accessing 2-2
HTTP 2-7
HTTPS 2-7
I
interface
Index-1
Index
bridge 6-3
definition 6-3
description 6-3
Ethernet 6-3
modem 6-4
OpenVPN 6-4
serial 6-4
J
job
configuring dynamic memory 19-13
configuring start times 19-12
configuring with a job property 19-8
configuring with a job task 19-10
description 19-2
script package and script 19-7
K
Kentrox Kickstart 2-2
L
laptop
access for Remote 11-1
assigning IP addresses 11-4
M
measurement table
entries
configuration examples 14-4
states 14-3
use with alarm table 14-3
use with event correlations 14-3
overview 14-2
mediation connections
description 15-2
N
Network Address Translation
configuring IPTables 11-6
enabling for laptop 11-6
network element sets
configuring 20-2, 20-6
description of 20-2
instance 20-2, 20-6
NTP 5-5
P
Package Manifest file 19-2
PAP 1-16
password
changing 3-4
entering 2-3
strong 3-3
peripherals
administrative states 17-5
configuring alarms 17-11
Index-2
configuring discrete I/O points 17-9

configuring SiteBus devices 17-16
disconnecting a managed 17-18
expansion discovery 17-4
expansion states 17-5
management configuration 17-7
operation states 17-5
overview 17-2
RMB-1 1-5, 17-2
RMB-2 1-6, 17-3
profile
creating custom 3-6
protocols 15-2
Python modules 19-2
R
relay output
configuring SNMP 17-13
open and close 17-15
Remote RMM-1400
features 1-2
front panel connectors 1-4
responder 10-4
response
components 10-4
configuring 10-6
description 10-2
restore
network settings 4-5
RMB peripheral units
features 1-5
RMM Overview 1-4
running configuration 4-2
running-config 2-6
S
script
components 19-2
Package Manifest file 19-2
Python modules 19-2
script package
configuring a job 19-7
creating and installing 19-5
SiteBus devices 17-16
SNMP
event template 18-5
manager 18-4
measurement template 18-11
mediation event originator 18-4
NE template 18-9
network element 18-15
point template 18-6
SNMP proxy
configuration 18-2
configuration information 18-3
description 18-2
strong password 3-3
T
templates
NE 18-9
U
users
adding 3-2
deleting 3-5
V
verify user environment 2-6
VPN
configuring 8-8
server 8-2, 8-3, 8-4
W
WAN
interfaces 16-2
web interface
accessing 2-8
functions 2-8
Home page 2-9
job configuration 19-2
restore network settings 4-5
save running configuration 4-2
wireless network
configurations 8-3, 8-4
configuring for Remote 8-2
example 8-4
overview 8-2
required components 8-2
with Connect SCS 8-4
wizards
bistate-alarms 21-6
description 21-2
initsetup 21-3
serial-port 21-8
types 21-2
Copyrights and License

Statements
Copyright 1983-2013 by Kentrox, Inc.
The material discussed in this publication is the

proprietary property of Kentrox, Inc. Kentrox retains all
rights to reproduction and distribution of this publication.
You should have received a copy of the GNU General

Public License along with this program; if not, write to
the Free Software Foundation, Inc., 675 Mass Ave,
Cambridge, MA 02139, USA.
This product includes software copyrighted by the GNU

General Public License and/or the GNU Lesser General
Public License. The source for the GPL portions of the
software is available by sending an email request to
engineer@kentrox.com.
TRADEMARKS:
Kentrox, Applied Innovation, Applied Innovation Inc., the

AI logo, and other names are intellectual property of
Kentrox, Inc.
Linux is a registered trademark of Linus Torvalds.
All other trademarks or registered trademarks appearing
in this publication are property of their respective
companies.
THIRD PARTIES:
OpenVPN (TM) -- An Open Source VPN daemon

Copyright (C) 2002-2005 OpenVPN Solutions LLC
<info@openvpn.net> This distribution contains multiple
components, some of which fall under different licenses.
By using OpenVPN or any of the bundled components
enumerated below, you agree to be bound by the
conditions of the license for each respective component.
Copyright 2000-2002 by the netfilter coreteam
(coreteam@netfilter.org): Paul Rusty Russell
(rusty@rustcopr.com.au), Marc Boucher
(marc+nf@mbsi.ca), James Morris
(jmorris@intercode.com.au), Harald Welte
(laforge@gnumonks.org), Jozsef Kadlecsik
(kadlec@blackhole.kfki.hu).
This program is free software; you can redistribute it
and/or modify it under the terms of the GNU General
Public License as published by the Free Software
Foundation; either version 2 of the License, or (at your
Option) any later version.
This program is distributed in the hope that it will be
useful, but WITHOUT ANY WARRANTY; without even
the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
Copyrights-1
Copyrights and License Statements
Copyrights-2

Remote RMM 1400 Version 5 Configuration Guide

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Remote RMM 1400 Version 5 Configuration Guide

Загружено:

Авторское право:

Доступные форматы

Remote RMM-1400

Intelligent Remote Site Management Device

Part Number 65-000131

About this Document

Telecommunications networks, TCP/IP networking, including Telnet and FTP

Remote RMM-1400 Version 5.0xx Configuration Guide

Screen Text, Menu

This style indicates Kentrox configuration screen text,

Static Command Text

In a command statement, this style indicates text that

In a command statement, this style indicates

In a command statement, ellipses (...) signify that the

In a command statement, square brackets indicate an

In a command statement, two or more parameters in

Menus and Menu

This style indicates menu and menu commands. A right

Dialog Boxes, Tabs,

This style indicates dialog boxes, tabs, fields, check

Variable Field Text

This style indicates variable information you type in a

Uppercase body text indicates keys on a keyboard,

Remote RMM-1400 Version 5.0xx Configuration Guide

Table 1 Document Conventions (Continued)

This style designates physical components on Kentrox

Remote RMM-1400 Version 5.0xx Configuration Guide

Cautions and Warnings

You must remove and install cards in a static-free environment. Wear

Do not ship or store cards near strong electrostatic, electromagnetic,

Remote RMM-1400 Version 5.0xx Configuration Guide

The version of hardware and software you are currently running

How you tried to solve the problem

Kentrox Online Knowledge Base

Remote RMM-1400 Version 5.0xx Configuration Guide

Phone number: 800-733-5511, option 3

Chapter 2: Getting Started .....................................................................2-1

Chapter 3: Configuring Users in the CLI ................................................3-1

Chapter 4: Saving and Applying Configurations ....................................4-1

Chapter 5: Configuring Network Setup Parameters ...............................5-1

Configuring a Timezone Definition File .......................................................... 5-10

Chapter 6: Understanding Controllers and Interfaces ............................6-1

Chapter 7: Configuring Static Routes .....................................................7-1

Chapter 8: Configuring a Wireless Network with Remote RMM-1400 ...8-1

Chapter 9: Configuring a Site VPN Connection .....................................9-1

Chapter 10: Configuring Actions, Events and Responses ...................10-1

Overview .................................................................................................................... 10-2

Chapter 11: Configuring Technician Laptop Access for Remote RMM-1400

Chapter 12: Configuring Event Correlations ........................................12-1

Chapter 14: Configuring Measurements and the Measurement Table 14-1

Sample Configuration for SiteBus Temperature Sensor ................................ 14-5

Chapter 15: Configuring Mediation Connections .................................15-1

Chapter 16: Configuring the DHCP Server ..........................................16-1

Chapter 17: Configuring the Peripheral Management Subsystem .......17-1

Chapter 18: Configuring the SNMP Proxy ............................................18-1

Configuring a Mediation SNMP Event Template ........................................................ 18-5

Chapter 19: Configuring Jobs ..............................................................19-1

Chapter 20: Configuring Modules ........................................................20-1

Chapter 21: Using Configuration Wizards ............................................21-1

Appendix A: Command Identifications .................................................. A-1

Guide to this Chapter

Remote RMM-1400 Version 5.0x Configuration Guide

Remote Product Overview

Summary of Remote RMM-1400 Functions

Compatibility with Optima Management Portal or any standard SNMP-based

Intelligent connectivity to remote network elements