remote rmc-700 configuration guide for site...

Remote RMC-700Configuration Guide

for Site Management

Version 5.2x

Part Number 030-101819
© 2014 by Westell, Inc. All rights reserved.

Copyright © 2014 by Westell, Inc. All Rights Reserved. Westell, Kentrox and Optima Management System are registered trademarks of Westell. All other names are trademarks of their respective owners.

Information is correct at time of publication and is subject to change without notice. Contact Westell in Dublin, Ohio to verify current product information. Westell, Inc. is an Equal Opportunity/Affirmative Action employer.

Westell, Inc.5800 Innovation Dr.

Dublin, Ohio 43016-3271 USAToll Free: (800) 247-9482

International: +1 (614) 798-2000Fax: +1 (614) 798-1770

Table of Contents

Preface.......................................................................................................... iAbout this Document...............................................................................................iDocument Conventions.......................................................................................... iiCautions and Warnings......................................................................................... ivCustomer Assistance .............................................................................................v

Chapter 1: Remote RMC-700 Product Overview ...................................... 1-1Remote Product Overview ................................................................................. 1-2

Summary of Remote Functions............................................................... 1-3Remote Features..................................................................................... 1-3

Remote RMC-700 Hardware Configuration ....................................................... 1-4Remote Product Specification Summary ........................................................... 1-5

Chapter 2: Getting Started ........................................................................ 2-1Accessing the CLI Using a Local Connection .................................................... 2-2

With Kentrox Kickstart ............................................................................. 2-2Without Kentrox Kickstart ........................................................................ 2-4

Setting Up the Initial Remote RMC-700 Configuration....................................... 2-6Accessing the CLI Using a Remote Connection ................................................ 2-9Accessing the Web Interface ........................................................................... 2-10

Chapter 3: Configuring Users in the CLI ................................................... 3-1Adding a New User ............................................................................................ 3-2Enabling the Strong Password Feature ............................................................. 3-3Changing a User Password ............................................................................... 3-4Deleting a User .................................................................................................. 3-5Creating a Custom Profile .................................................................................. 3-6

Chapter 4: Saving and Applying Configurations ....................................... 4-1Saving the Running Configuration ..................................................................... 4-2Applying Configuration Fragments to an Existing Configuration File ................. 4-3

TOC-1

Restoring Factory Defaults................................................................................. 4-4Restoring Basic Network Settings...................................................................... 4-5

Chapter 5: Configuring Network Setup Parameters.................................. 5-1Configuring the Domain Name, DNS Servers and IP Forwarding ..................... 5-2Configuring an IPv6 Address ............................................................................. 5-4Configuring NTP................................................................................................. 5-5Configuring System Clock Settings.................................................................... 5-7

Configuring Default Settings.................................................................... 5-7Configuring Custom System Clock Settings............................................ 5-8Configuring a Timezone Definition File ................................................. 5-10

Configuring RAS Settings ................................................................................ 5-11Configuring SNMP ........................................................................................... 5-13

Chapter 6: Understanding Controllers and Interfaces............................... 6-1Controller Descriptions....................................................................................... 6-2

Bridge Controllers.................................................................................... 6-2Ethernet Controllers ................................................................................ 6-2OpenVPN Controllers.............................................................................. 6-3Serial Controllers..................................................................................... 6-3

Interface Descriptions ........................................................................................ 6-4Bridge Interfaces ..................................................................................... 6-4Ethernet Interfaces .................................................................................. 6-4OpenVPN Interfaces ............................................................................... 6-4Serial Interfaces ...................................................................................... 6-5

Chapter 7: Configuring a Site VPN Connection ........................................ 7-1Getting Started ................................................................................................... 7-2

Configuration Requirements.................................................................... 7-2Optima..................................................................................................... 7-2Redirect ................................................................................................... 7-2

Configuration Example....................................................................................... 7-3Configuring the Site LAN.................................................................................... 7-5Configuring the Site VPN ................................................................................... 7-6Verifying the VPN Connection from the Client ................................................... 7-8

Chapter 8: Configuring Static Routes........................................................ 8-1Adding an IPv4 Static Route to the IP Routing Table ........................................ 8-2Adding a Default IPv4 Static Route to the IP Routing Table .............................. 8-3

TOC-2

Adding an IPv6 Static Route to the IP Routing Table ........................................ 8-4Adding a Default IPv6 Static Route to the IP Routing Table .............................. 8-5

Chapter 9: Configuring a Wireless Network with Remote RMC-700......... 9-1Getting Started ................................................................................................... 9-2

Wireless Network Overview .................................................................... 9-2Required Components ............................................................................ 9-2Initial Setup.............................................................................................. 9-3

Sample Configuration......................................................................................... 9-4Configuring the Wireless Modem....................................................................... 9-5Configuring the VPN .......................................................................................... 9-8

Chapter 10: Configuring Actions, Events and Responses ...................... 10-1Overview .......................................................................................................... 10-2Event Components........................................................................................... 10-4Response Components.................................................................................... 10-5Action Components.......................................................................................... 10-6Configuring an Event, Response and Action ................................................... 10-7

Chapter 11: Configuring Technician Laptop Access for Remote RMC-700...11-1

Configuration Overview.................................................................................... 11-2Assigning IP Addresses to Technician Laptops ............................................... 11-4Configuring IPTables for Network Address Translation ................................... 11-6

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

Event Correlation Components ............................................................. 12-2Correlation Expression Components ............................................................... 12-3

Originator Types and States.................................................................. 12-3Operators .............................................................................................. 12-4Expression Evaluation........................................................................... 12-4Configuring a Time Period (Optional).................................................... 12-5

Configuring an Event Correlation ..................................................................... 12-6

Chapter 13: Configuring Alarm Entries in the Central Alarm Table......... 13-1

TOC-3

Overview .......................................................................................................... 13-2Alarm Protocol Formats ................................................................................... 13-3

Raw ....................................................................................................... 13-3SNMP.................................................................................................... 13-3TL1 ........................................................................................................ 13-3

Configuring an Alarm Entry for a Temperature Sensor.................................... 13-4Configuring Analog Input Values........................................................... 13-6

Configuring an Alarm Entry for a Discrete Input............................................... 13-8Configuring an Alarm Entry for Ethernet Interface MAC Security Violations.. 13-10Configuring an Alarm Entry for a Serial Connection Failure .......................... 13-12Configuring an Alarm Entry for a Power Supply Failure................................. 13-14Configuring an Alarm Entry for a TCP Connection that Goes Down.............. 13-16Configuring an Alarm Entry for a Telnet Connection that Comes Up............. 13-18Testing Alarm Table Configurations............................................................... 13-20

Chapter 14: Configuring Measurements and the Measurement Table ... 14-1Overview .......................................................................................................... 14-2

Use for Measuring State Transitions and Durations.............................. 14-3Use with Alarm Table Entries ................................................................ 14-3Use with Event Correlations .................................................................. 14-3Use with Proxied SNMP NEs ................................................................ 14-4

Configuring a Measurement Table Entry for a Temperature Sensor ............... 14-5Sample Configuration for SiteBus Temperature Sensor ....................... 14-6

Configuring an Alarm Entry for a Measurement............................................... 14-7Configuring a Measurement Table Entry for State Transitions and Durations14-10Configuring an Event Correlation for a Measurement.................................... 14-12

Chapter 15: Configuring Mediation Connections .................................... 15-1Overview .......................................................................................................... 15-2Secure Terminal Server Access....................................................................... 15-3

Terminal Server User Access................................................................ 15-4TACACS+ Configuration ....................................................................... 15-4

Configuring a TCP to Asynchronous Serial Connection .................................. 15-5Configuring a Telnet to Asynchronous Serial Connection................................ 15-7Configuring a SSH to Asynchronous Serial Connection .................................. 15-9Configuring an Asynchronous Serial to Asynchronous Serial Connection..... 15-11Configuring an Asynchronous Serial to TCP Connection .............................. 15-14

Chapter 16: Configuring and Connecting TL1 Infrastructure .................. 16-1Overview .......................................................................................................... 16-2Configuring a TL1 Multiplexer .......................................................................... 16-3

TOC-4

Configuring a Virtual TL1 NE ........................................................................... 16-4Configuring the TCP Port for a TL1 Multiplexer ............................................... 16-5Configuring a Telnet Connection to a TL1 Multiplexer ..................................... 16-6Configuring a Telnet Connection to a Virtual TL1 NE ...................................... 16-7

Chapter 17: Configuring DHCP............................................................... 17-1DHCP Server Overview ................................................................................... 17-2

Configuring DHCP Client Support ......................................................... 17-2Configuring a DHCP Server ............................................................................. 17-4Configuring a DHCP Server Subnet................................................................. 17-6Configuring a Host on a DHCP Server............................................................. 17-8Configuring BOOTP/DHCP Relay.................................................................... 17-9Configuring DHCP Client Support.................................................................. 17-10

Chapter 18: Configuring Relay Outputs .................................................. 18-1Overview .......................................................................................................... 18-2Configuring the Mediation TL1 Command ....................................................... 18-3Configuring TL1 Commands to Control a Relay Output................................... 18-4Configuring SNMP to Operate a Relay Output ................................................ 18-6Directly Controlling a Relay Output .................................................................. 18-8

Chapter 19: Configuring the SNMP Proxy .............................................. 19-1SNMP Proxy Feature Overview ....................................................................... 19-2SNMP Proxy Configuration Information ........................................................... 19-3

SNMP Templates .................................................................................. 19-3SNMP NE.............................................................................................. 19-4SNMP Manager..................................................................................... 19-4

Configuring a Mediation SNMP Event Template.............................................. 19-5Configuring a Mediation SNMP Point Template............................................... 19-6Configuring a Mediation SNMP NE Template.................................................. 19-9Configuring a Mediation SNMP Measurement Template............................... 19-11Configuring a Mediation SNMP Network Element ......................................... 19-15Configuration Results..................................................................................... 19-17

Chapter 20: Configuring Jobs ................................................................. 20-1Job Configuration Overview............................................................................. 20-2

Script Package Components................................................................. 20-2Configuring Access to a Central FTP Package Server .................................... 20-4

TOC-5

Creating and Installing a Script Package ......................................................... 20-5Configuring a Job with a Script Package and Script ........................................ 20-7Configuring a Job with a Job Property ............................................................. 20-8Configuring a Job with a Job Task ................................................................. 20-10Configuring Job Start Times........................................................................... 20-12Configuring Dynamic Memory for a Job......................................................... 20-13

Chapter 21: Configuring Modules ........................................................... 21-1Module Configuration Overview....................................................................... 21-2Configuring Modules Using Command Line Interface...................................... 21-3

Installing Modules.................................................................................. 21-3Enabling an Optional Application .......................................................... 21-4Realizing and Configuring Network Elements ....................................... 21-5Configuring an NE Set........................................................................... 21-7Initiating a Control Action ...................................................................... 21-8

Configuring Modules Using Web Interface..................................................... 21-10Installing Modules................................................................................ 21-10Realizing and Configuring Network Elements ..................................... 21-14Configuring an NE Set......................................................................... 21-17

Chapter 22: Configuring SiteBus Devices............................................... 22-1Configuring SiteBus Devices............................................................................ 22-2

Chapter 23: Using Configuration Wizards............................................... 23-1Configuration Wizard Overview........................................................................ 23-2Using the initsetup Wizard ............................................................................... 23-3Using the bistate-alarms Wizard ...................................................................... 23-6Using the serial-port Wizard............................................................................. 23-8

Chapter 24: Remote RMC-700 TL1 Commands..................................... 24-1Overview .......................................................................................................... 24-2Default TL1 VNE Commands........................................................................... 24-3

ACT-USER............................................................................................ 24-3ALW-MSG-ALL...................................................................................... 24-4CANC-USER......................................................................................... 24-5RTRV-ALM-ALL .................................................................................... 24-5RTRV-ALM-DS3.................................................................................... 24-6RTRV-ALM-EC1.................................................................................... 24-7RTRV-ALM-ENV ................................................................................... 24-8

TOC-6

RTRV-ALM-EQPT................................................................................. 24-8RTRV-ALM-OC3 ................................................................................... 24-9RTRV-ALM-T1..................................................................................... 24-10RTRV-HDR.......................................................................................... 24-11

Unsupported TL1 Commands........................................................................ 24-12

Appendix A: Backing Up and Restoring the Remote RMC-700 ConfigurationA-1

Backing Up the Configuration ............................................................................A-2Restoring the Configuration ...............................................................................A-3

Appendix B: Command Identifications ....................................................B-1

Glossary........................................................................................Glossary-1

Index .................................................................................................. Index-1

Copyrights and License Statements ......................................... Copyrights-1

TOC-7

Preface

About this Document

This document explains how to configure and operate the Remote RMC-700 intelligent site management device.

Remote RMC-700 system administrators should have a working knowledge of:

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

FTP tools

Radius and/or TACACS+

SNMP or TL1

Remote RMC-700 script developers should also have a working knowledge of:

The Python script language

XML syntax

Additional information is presented in the Remote RMC-700 Command Reference Guide.

i

Remote RMC-700 version 5.2x Configuration GuidePreface: Document Conventions

Document ConventionsTable 1 describes the text conventions used in this document.

Table 1 Document Conventions

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 (+).

ii

Remote RMC-700 Version 5.2x Configuration GuidePreface: Document Conventions

Labels This style designates physical components on Kentrox products such as jumpers, switches, and cable connectors.

Note:

Note messages emphasize or supplement important points of the main text.

Important: Important messages provide information that is essential to the completion of a task.

Tip:Tip messages provide information that assists users in operating equipment more effectively.

Table 1 Document Conventions (Continued)

iii

Remote RMC-700 version 5.2x Configuration GuidePreface: 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 WarningThe Federal Communications Commission has set limits for emitted radio interference, and Remote RMC-700 is constructed with this electromagnetic interference (EMI) limitation in mind. Remote RMC-700 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

Remote RMC-700 Version 5.2x Configuration GuidePreface: Customer Assistance

Customer AssistanceAll 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 BaseThe 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 SupportEmail 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:

[email protected]

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 supportAvailable 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

http://kb.kentrox.com

mailto:[email protected]

Remote RMC-700 version 5.2x Configuration GuidePreface: 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 service-affecting outages that cannot wait until the next business day. To qualify for after-hours 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 DocumentationYou can also access and view the most current versions of Kentrox product documentation on our Web site at:

http://www.kentrox.com

vi

1

Remote RMC-700 Product Overview

This chapter provides a high level overview of the Remote product features and functionality. In addition, the hardware architecture and components of the Remote RMC-700, including expansion units and peripherals, are described.

Guide to this Chapter

Remote Product Overview

Remote RMC-700 Hardware Configuration

Remote Product Specification Summary

1-1

Remote RMC-700 Version 5.2x Configuration GuideRemote RMC-700 Product Overview: Remote Product Overview

Remote Product OverviewThe Kentrox®Remote suite of products includes Remote RMC-700, Remote RMM-1400, and Remote RMX-3200. The Remote suite of products includes several models that provide various features. 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 Management System®, the Remote products reside at the network’s remote locations and connect to each element via a wide variety of interface options. The Remote products perform protocol mediation and interface conversion, collect alarms and monitoring data and support bi-directional management control with the Optima Management Portal via Ethernet, T1/E1, 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 the Remote and Optima Management Portal functionality.

Figure 1-1 Remote and Optima Integration for Remote Site Management

1-2

Remote RMC-700 Version 5.2x Configuration GuideRemote RMC-700 Product Overview: Remote Product Overview

Summary of Remote FunctionsThe Remote product functions include:

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 FeaturesAll Remote products include the following features: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 RMC-700 Version 5.2x Configuration GuideRemote RMC-700 Product Overview: Remote RMC-700 Hardware Configuration

Remote RMC-700 Hardware ConfigurationFigure 1-2 shows the Remote RMC-700 base unit, which consists of the following connectors and counts:

2 Ethernet ports provide for connections into a network.

2 serial ports provide connectivity to any asynchronous device.12 discrete ports, 1 analog input, and 1 control output.

1 SiteBus One-Wire Interface allowing up to 12 One-Wire sensors

Figure 1-2 Remote RMC-700 Base Unit

SiteBus Connection2 Serial Ports 2 Ethernet Ports

12 Discrete PortsAnalog Input

Relay

Diversity SMA FemaleCellular/PCS Antenna

Tx/Rx SMAFemale Cellular/PCS Antenna

Battery InputDC Power Input

1-4

Remote RMC-700 Version 5.2x Configuration GuideRemote RMC-700 Product Overview: Remote Product Specification Summary

Remote Product Specification SummaryTable 1-1 summarizes the number and types of ports, outputs and inputs for the Remote RMC-700 and Expand modules.

Table 1-1 Product Specifications Summary

Product Async Ports

Console Ports

Ethernet Ports

Discrete Outputs

Control Outputs

Analog Inputs

Remote RMC-700

2 0 2 12 1 1

1-5

Remote RMC-700 Version 5.2x Configuration GuideRemote RMC-700 Product Overview: Remote Product Specification Summary

1-6

2

Getting Started

This chapter provides information on getting started with Remote RMC-700. Step-by-step scenarios describe 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 RMC-700 Configuration

Accessing the CLI Using a Remote Connection

Accessing the Web Interface

2-1

Remote RMC-700 Version 5.2x Configuration GuideGetting Started: Accessing the CLI Using a Local Connection

Accessing the CLI Using a Local Connection

To access the CLI using a local connection (using Kickstart):

1. If you haven’t 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 RMC-700.

3. Launch Kentrox Kickstart. Kickstart discovers the Remote RMC-700 device, as shown below (RMM-1400 shown - Remote RMC-700 is similar).

Note: If the Remote RMC-700 device is not discovered within one minute, select

Help > About in Kentrox Kickstart, then click the Network Troubleshooting Guide link for instructions.

4. Click SSH Terminal (or select Tools > Connect > SSH Terminal). An SSH window opens, displaying the Remote RMC-700 login prompt.

In this scenario, you will:

Connect and log into Remote RMC-700(optional) Access help information

Note: When a new Remote RMC-700 is booted for the first time, it does not have

a configured IP address. As a result, the initial configuration for Remote RMC-700 must be performed onsite using the console port. For information about configuring an IP address for remote logins, refer to Setting Up the Initial Remote RMC-700 Configuration on page 2-6.

2-2

Remote RMC-700 Version 5.2x Configuration GuideGetting Started: Accessing the CLI Using a Local Connection

5. At the login prompt, enter your user name:

admin

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 RMC-700 allows you to log in only five times using the default password. On your sixth login, Remote RMC-700 will prompt you to change the default password to a new password.

The main CLI prompt displays.

7. (optional) Access help information:

help

or

?

Note: For more information on using the CLI, refer to section “CLI Overview” in the

Remote RMC-700 Command Reference Guide.

loginas: admin

_ __ _____ _ _ _______ _____ ____ __ __| | / / | ___|| \ | ||___ ___|| _ \ / \ \ \ / /| |/ / | |___ | \ \| | | | | (_) || -- | \ \/ /| ( | ___|| |\ \ | | | | _ / | ( ) | ) (| |\ \ | |___ | | \ | | | | | \ \ | -- | / /\ \|_| \_\ |_____||_| \_| |_| |_| \_\ \____/ /_/ \_\

Remote RMC-700Using keyboard-interactive authentication.Password: You have 4 grace logins remaining using the default user password.You can create initial network connectivity settings and user accountsby running this command: config use-wizard initsetup(Kentrox)>

2-3

Remote RMC-700 Version 5.2x Configuration GuideGetting Started: Setting Up the Initial Remote RMC-700 Configuration

Setting Up the Initial Remote RMC-700 Configuration

To set up the initial Remote RMC-700 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 displays:

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-displays.


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)

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 the IP address.

Note: The Remote RMC-700 supports IPv4 and IPv6 and provides the ability to

configure both IP protocols at the same time. Refer to Chapter 5 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 RMC-700. This IP address is the primary Remote RMC-700 IP address.

9. Add a default route with gateway address 10.40.0.1:

config ip route default 10.40.0.1

Note: Refer to the remote access configuration commands in the Remote RMC-

700 Command Reference Guide for more information.

2-5


10. (optional) Verify that the user environment has been set up properly:

running-config

The command response displays similar to the following:

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.

11. Save the configuration. (Refer to Saving the Running Configuration on page 4-2.)

(Dub)>running-config# Product: Remote RMC# Version: 5.20# Created: 2014-04-25,12:25:00.0, 0000# User: janedoe# Stage2 Version: 1.00config banner #This is my banner.\d\t#config hostname Dubconfig ip route default 10.40.0.1config timeout 20config users add janedoe supervisor -e$6$cezdPzpb25A7nbK8$9ON8gQA9q7Ev4yi6CS2VjCmn6nA31PBA7wm/qkSVATxpGvbz3V85cW3NAkLo7fQ.xrp8zAzmZzSGmrQdvCVet/ -e$6$cezdPzpb25A7nbK8$9ON8gQA9q7Ev4yi6CS2VjCmn6nA31PBA7wm/qkSVATxpGvbz3V85cW3NAkLo7fQ.xrp8zAzmZzSGmrQdvCVet/config interface bridge switch ip address 10.40.57.90/16(Dub)>

2-6

Remote RMC-700 Version 5.2x Configuration GuideGetting Started: Accessing the CLI Using a Remote Connection

Accessing the CLI Using a Remote Connection

To access the CLI using a remote connection:

1. Use a PC or laptop with terminal emulation software to connect to Remote RMC-700. 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 an SSH connection.

Note: Individual procedures for making this connection will vary based on the type of

software you are using.

3. Enter the IP address of the Remote RMC-700 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 RMC-700 lets you log in only five times using the default password. On your sixth login, Remote RMC-700 will prompt you to change the default password to a new password.

In this scenario, you will connect and log into Remote RMC-700 remotely using an SSH connection.

2-7

Remote RMC-700 Version 5.2x Configuration GuideGetting Started: Accessing the Web Interface

Accessing the Web InterfaceFrom the Remote RMC-700 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

Manage and configure Modules and Applications

Before you can access the Remote RMC-700 Web interface you must:

Enable the remote access protocol (HTTPS).

Configure the IP address. For more information, refer to Setting Up the Initial Remote RMC-700 Configuration on page 2-6.

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.

To access the Remote RMC-700 Web interface:

1. At the main prompt, enable the remote access protocol as https:

config remote-access https enable

2. Open a Web browser.

3. In the URL address field, enter the Remote RMC-700 IP address:

https://10.40.57.233

The login window displays.

4. Enter your user name:

janedoe


Enable remote access (HTTPS).

Open a Web browser and access Remote RMC-700 using a specific IP address.

2-8


5. Enter your password:

mypassword

The Web interface opens to the Home page, refer to Figure 2-1.

6. 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 RMC-700 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

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Users in the CLI: Adding a New User

Adding 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 display as asterisks:

**********

3. When prompted to confirm, enter the same password. Again, the characters that you enter display 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 RMC-700 Command Reference Guide.

4. (optional) Verify that the new user has been added properly:

show users


5. Save the configuration.

In this scenario, you will add a new user.

(Dub)>show users Login Name Profile 1. janedoe supervisor 2. johndoe status 3. test supervisor(Dub)>

3-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Users in the CLI: Enabling the Strong Password Feature

Enabling the Strong Password FeatureThe 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. RAS users will use rules enforced by the Radius or TACACS+ server.

The strong password feature is disabled by default.

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


3. Change the existing password for user ebh. The following example shows the additional restrictions of the strong password feature.


Enable the strong password feature.

Change an existing user password.

(Dub)>show usersStrong Password Support: enabled

Login Name Profile 1. bob restricted 2. ebh restricted 3. jeff status 4. tech management 5. test supervisor(Dub)>

(Dub)>config users password ebhPlease 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 ebhPlease enter the new password. *********Please confirm the new password. *********(Dub)>

3-3

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Users in the CLI: Changing a User Password

Changing a User Password

To change a user password:

1. At the main prompt, change the password for user johndoe to oldguy:

config users password johndoe


Please enter the new password.

2. Enter the new password:

oldguy

Note: Passwords are case-sensitive and display as asterisks (*) on the screen

as you type them.


Please confirm the new password.

3. Re-enter the new password.

oldguy

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

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


In this scenario, you will change the password for an existing user.

3-4

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Users in the CLI: Deleting a User

Deleting 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


Note: If the user has been deleted, it will no longer display in the list of users.


In this scenario, you will delete a user.

(Dub)>show users Login Name Profile 1. janedoe supervisor 2. test supervisor(Dub)>

3-5

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Users in the CLI: Creating a Custom Profile

Creating a 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 B : 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


7. (Optional) Save the configuration.

In this scenario, you will: 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.

(Dub)>show profile techName: techBase Type: statusPrivilege Level: 5

Command ID Action/config/controller/eth include/config/interface/eth include/show/resource-tracking exclude(Dub)>

3-6

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

Remote RMC-700 Version 5.2x Configuration GuideSaving and Applying Configurations: Saving the Running Configuration

Saving the Running Configuration

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 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-10 for details.

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 RMC-700 without first saving the configuration, any unsaved changes will be lost.

4-2

Remote RMC-700 Version 5.2x Configuration GuideSaving and Applying Configurations: Applying Configuration Fragments to an Existing Configuration File

Applying Configuration Fragments to an Existing Configuration File

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 RMC-700.

To apply a configuration fragment to an existing configuration file:

1. Using an SFTP utility, transfer the patch file (patch1.pat) to Remote RMC-700 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:

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 RMC-700 (/config/patches) with an SFTP 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.

(Dub)>config apply-patch patch1 running-configconfig users add manager1 manage test testconfig no timeoutconfig ntp disableconfig clock daylight-savings DST(Dub)>

4-3

Remote RMC-700 Version 5.2x Configuration GuideSaving and Applying Configurations: Restoring Factory Defaults

Restoring Factory Defaults

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 RMC-700.

To restore the factory default settings, copy the factory configuration to the running configuration:

copy factory-config running-config

In this scenario, you will restore Remote RMC-700’s factory default settings.

4-4

Remote RMC-700 Version 5.2x Configuration GuideSaving and Applying Configurations: Restoring Basic Network Settings

Restoring Basic Network Settings

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-10 for details.

In this scenario, you will restore Remote RMC-700’s 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 23-3.

4-5

Remote RMC-700 Version 5.2x Configuration GuideSaving 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 RMC-700.


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

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Network Setup Parameters: Configuring the Domain Name, DNS Servers and IP Forwarding

Configuring the Domain Name, DNS Servers and 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:

config ip name-server 10.25.2.20

4. Enable IP forwarding:

config ip forward


Configure a domain name

Configure a primary and secondary DNS server

Enable IP forwarding

5-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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 similar to the following displays:ss

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.


(Dub)>running-config# Product: Remote RMC# Version: 5.20# Created: 2014-04-17,12:32:11.0,-0800# User: test# Bootloader Version 1.00config banner #This is my banner.\d\t#config hostname Dubconfig ip domain-name www.Kentrox.comconfig ip forwardconfig ip name-server 10.25.2.5config ip name-server 10.25.2.20config ip route default 10.40.0.1config timeout 20config users add janedoe supervisor -e$6$cezdPzpb25A7nbK8$9ON8gQA9q7Ev4yi6CS2VjCmn6nA31PBA7wm/qkSVATxpGvbz3V85cW3NAkLo7fQ.xrp8zAzmZzSGmrQdvCVet/ -e$6$cezdPzpb25A7nbK8$9ON8gQA9q7Ev4yi6CS2VjCmn6nA31PBA7wm/qkSVATxpGvbz3V85cW3NAkLo7fQ.xrp8zAzmZzSGmrQdvCVet/config interface bridge switch ip address 10.40.57.90/16(Dub)>

5-3

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Network Setup Parameters: Configuring an IPv6 Address

Configuring 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 RMC-700 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.

The command response similar to the following displays:


In this scenario, you will configure an IPv6 address.

(Dub)>show interfaces bridgebridge 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 valid=forever preferred=forever address=fe80::240:72ff:fe0e:678d/64 valid=forever preferred=forever(Dub)>

5-4

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Network Setup Parameters: Configuring NTP

Configuring NTP

To configure system clock parameters using the common clock time maintained by the Remote RMC-700 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 RMC-700:

config ntp enable


Configure a primary and secondary NTP server

Configure a minimum and maximum NTP polling interval

Enable NTP

5-5

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Network Setup Parameters: Configuring NTP

5. (optional) Verify that the clock parameters have been configured properly:

running-config


Tip: You can also use the show ntp command to verify the NTP configuration.


(Dub)>running-config# Product: Remote RMC# Version: 5.20# Created: 2014-04-17,12:32:11.0,-0800# User: test# Bootloader Version 1.00config banner #This is my banner.\d\t#config hostname Dubconfig ip domain-name www.Kentrox.comconfig ip forwardconfig ip name-server 10.25.2.5config ip name-server 10.25.2.20config ip route default 10.40.0.1config ntp enableconfig ntp poll-interval 7 12config ntp server 10.50.18.33 preferconfig ntp server 10.50.18.32config timeout 20config users add janedoe supervisor -e$6$cezdPzpb25A7nbK8$9ON8gQA9q7Ev4yi6CS2VjCmn6nA31PBA7wm/qkSVATxpGvbz3V85cW3NAkLo7fQ.xrp8zAzmZzSGmrQdvCVet/ -e$6$cezdPzpb25A7nbK8$9ON8gQA9q7Ev4yi6CS2VjCmn6nA31PBA7wm/qkSVATxpGvbz3V85cW3NAkLo7fQ.xrp8zAzmZzSGmrQdvCVet/config interface bridge switch ip address 10.40.57.90/16(Dub)>

5-6

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Network Setup Parameters: Configuring System Clock Settings

Configuring System Clock SettingsRemote RMC-700 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

Important: You must disable NTP before you can configure the Remote RMC-700 system clock locally.

To configure default system clock settings:

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 04/09/2010:

config clock local-time 11:22:30 04/09/2010


Configure the timezone in default mode

Enable daylight savings default parameters

Configure the local time and date

5-7



show clock


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 SettingsIf you configure the timezone in custom mode, you can use subcommands to customize the daylight savings parameters.

Important: You must disable NTP before you can configure the Remote RMC-700 system clock locally.

To configure custom system clock settings:

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

(Dub)>show clockFri Apr 9 11:22:30 EDT 2010Uptime 4 days, 0:17The 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)>


Configure the timezone in custom mode

Enable daylight savings in custom mode

Configure custom daylight savings time parameters

5-8


2. Set the following custom daylight savings time parameters:


show clock



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

(Dub)>show(Dub) show>clockFri Apr 9 14:18:24 EST 2010Uptime 9 days, 17:48The timezone is named EST and has an offset of -05:00 GMT.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 FileYou 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.

To configure a time zone definition file:

1. 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




Install the timezone definition file

Apply daylight savings rules from the timezone definition file

(Dub)>show(Dub) show>clockFri Apr 9 14:18:24 EST 2010Uptime 9 days, 17:48The timezone is named EST and has an offset of -05:00 GMT.Daylight savings time is currently active and is saving 01:00.These settings were loaded from the timezone definition file.(Dub) show>

5-10

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Network Setup Parameters: Configuring RAS Settings

Configuring RAS Settings

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.


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 RMC-700 attempts to connect to the RAS server

Configure the RAS timeout period for a remote authentication attempt

5-11

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Network Setup Parameters: Configuring RAS Settings

5. Configure Remote RMC-700 to make 5 connection attempts to the RAS server before failing:

config ras retry 5

6. Configure how long Remote RMC-700 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 rasShell RAS option: TACACS+ with Local FallbackRAS Accounting: enabledRAS Authorization: privilegeRAS Retry: 5RAS Timeout: 30

RAS ServersIP Port Secret Phases10.50.18.32 100 tserver1 authen author account

(Dub)>

5-12

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Network Setup Parameters: Configuring SNMP

Configuring SNMP

Note: The following management information bases (MIBs) are available for Remote

RMC-700:

aiMediationV2.mib

aiPeriphDiscrete.mib

aiPeripheral.mib

aiSysCfg.mib

aiSysCfgConfig.mib

aiSystem.mib

aiSystemInv.mib

aiRosetta.mib

To access the available MIBs for Remote RMC-700, 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

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


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

Notes: This scenario applies only when an SNMP management system, such as

AppliedView, is used to manage Remote RMC-700.

5-13

http://www3.kentrox.com/Support/Documentation-Library.aspx

http://www3.kentrox.com/Support/Documentation-Library.aspx


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



(Dub)>show snmp summaryAuthentication traps: enabledTrap queue: enabledCommunities: Name User Type Auth Mode administrator v1 noauth readwrite public v1 noauth readonlyV3 Users: Username Auth PrivHosts: IP Address Port Type Auth Community/User Queue 10.34.3.84 162 v1 noauth public sending fd10::39:0:0:200 162 v2-inform noauth public sendingPriority: Trap OID Priority .1.3.6.1.6.3.1.1.5.3 high(Dub)>

5-14


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



Configure an SNMP version 3 user

Configure an SNMP v3 community

Configure an SNMP v3 host

(Dub)>show snmp summaryAuthentication traps: enabledTrap queue: disabledCommunities: Name User Type Auth Mode administrator v1 noauth readwrite dublinusers eric v3 priv readwrite public v1 noauth readonly v3comm v3user v3 priv readwriteV3 Users: Username Auth Priv eric md5 des v3user md5 aes-128Hosts: IP Address Port Type Auth Community/User Queue 192.168.7.2 162 v1 noauth administrator sending 12.34.56.78 2 v3 auth eric sendingPriority: Trap OID Priority(Dub)>

5-15


5-16

6

Understanding Controllers and Interfaces

This chapter provides information about controllers and interfaces and how they operate on Remote RMC-700.


Controller Descriptions

Interface Descriptions

6-1

Remote RMC-700 Version 5.2x Configuration GuideUnderstanding Controllers and Interfaces: Controller Descriptions

Controller DescriptionsA controller is a software object on Remote RMC-700 that serves as a destination for a data bit stream. It can be a physical device, such as a serial transceiver, or the controller can be a virtual entity. There are four types of controllers that can be configured in the Remote RMC-700 CLI:

Bridge Controllers

Ethernet Controllers

OpenVPN Controllers

Serial Controllers

Bridge ControllersThere is only one bridge controller on Remote RMC-700. The controller is named bridge switch because it is a bridge that (by default) includes both of the Ethernet switch ports.

This and the next section imply that Ethernet controllers are always on the bridge.

Ethernet ControllersThere are two Ethernet controllers on every Remote RMC-700. They represent the two local switched Ethernet ports.Both are on the bridge by default, but can be configured to be excluded from the bridge controller.

OpenVPN ControllersOpenVPN controllers use the OpenVPN software package to manage VPN connections. The Remote RMC-700 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 RMC-700 client and the Connect SCS server. This VPN connection provides a secure link between remote sites and the protected customer management network.

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 RMC-700. This VPN connection provides a secure link for accessing network elements at a remote site from the technician's laptop.

Serial ControllersRemote RMC-700 has two asynchronous serial controllers.In addition, Remote RMC-700 contains a PCI mini card slot for a wireless modem with a USB interface to the processor. RMC-700 supports the Ericsson F3607 and F5321 GSM modems and the Sierra Wireless MC5727 and MC5728 CDMA modems. The modem is available as serial modem.

6-2

Remote RMC-700 Version 5.2x Configuration GuideUnderstanding Controllers and Interfaces: Interface Descriptions

Interface DescriptionsAn 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 RMC-700 CLI:

Bridge Interfaces

Ethernet Interfaces

OpenVPN Interfaces

Serial Interfaces

Bridge InterfacesThe bridge interface works in conjunction with the bridge controller switch. It is used to bridge Ethernet ports, and initially includes the two switched Ethernet ports. An IP address can be assigned to the bridge switch interface, providing a mechanism to route IP packets to the two switched Ethernet ports and any bridged port on Remote RMC-700. The IP address assigned to the bridge interface is Remote RMC-700’s primary IP address. Until this IP address is configured, Remote RMC-700 cannot be managed remotely via SSH or SNMP. For more information, refer to Setting Up the Initial Remote RMC-700 Configuration on page 2-6.

Ethernet InterfacesEthernet interfaces are individually configurable on Remote RMC-700, 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 RMC-700 Command Reference Guide for details on using this command.

OpenVPN InterfacesLike Ethernet interfaces, OpenVPN interfaces are individually configurable on Remote RMC-700. 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.

6-3

Remote RMC-700 Version 5.2x Configuration GuideUnderstanding Controllers and Interfaces: Interface Descriptions

Serial InterfacesInterfaces are not configurable for Remote RMC-700’s two asynchronomous 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 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 RMC-700.


Getting Started

Configuration Example

Configuring the Site LAN

Configuring the Site VPN

Verifying the VPN Connection from the Client

7-1

Remote RMC-700 Version 5.2x Configuration GuideConfiguring a Site VPN Connection: Getting Started

Getting StartedA major feature of the Remote RMC-700 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 RMC-700. The Remote RMC-700 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 RMC-700 to restrict the traffic to approved IP addresses and ports at the site.

Configuration RequirementsThe Remote RMC-700 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.

OptimaOptima 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 RMC-700 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.

RedirectThe Redirect software manages the site VPN connection to the Remote RMC-700 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.

7-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring a Site VPN Connection: Configuration Example

Configuration ExampleFigure 7-1 provides a detailed example of how the site VPN connection between Client 1 and Remote RMC-700 is configured.

In the following example, both Client 1 and Remote RMC-700 are connected to the Intranet. Redirect on Client 1 uses the IP address of the Remote RMC-700 on the Intranet to establish the site VPN connection to access Site NE 1 and Site NE 2.

Figure 7-1 Site VPN Connection between Client 1 and the Remote RMC-700

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. The IP address of Site NE 2 is 192.168.111.101/24.

The IP address of the site VPN interface on the Remote RMC-700 is 192.168.101.1/24.

After the site VPN connection is established between Client 1 and the Remote RMC-700, the client is assigned a point-to-point (site VPN) IP address 192.168.101.6/30.

7-3

Remote RMC-700 Version 5.2x Configuration GuideConfiguring a Site VPN Connection: Configuration Example

The peer’s IP address is 192.168.101.5/30 on the Remote RMC-700. 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 allow-access configurations on the Remote RMC-700 defined by the user.

The Remote RMC-700 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 RMC-700.

7-4

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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 1 interface is used.

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 1 from the bridge group:

config controller ethernet 1 no bridge

2. Configure IP address 192.168.111.1/24 for ethernet port 3:

config interface ethernet 1 ip address 192.168.111.1/24

3. Enable IP forwarding:

config ip forward


Remove the ethernet controller from the bridge group

Configure the IP address for the ethernet controller

Enable IP forwarding

7-5

Remote RMC-700 Version 5.2x Configuration GuideConfiguring a Site VPN Connection: Configuring the Site VPN

Configuring 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 2

Tip: Multiple routes can be added to reach different subnets at the same site by executing the command multiple times for each additional route.

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 RMC-700 blocks all traffic to the site LAN.

ICMP ping requests and replies are automatically allowed for each IP address specified.


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

7-6

Remote RMC-700 Version 5.2x Configuration GuideConfiguring a Site VPN Connection: Configuring the Site VPN

5. Verify the configuration:

show controllers openvpn site


6. Show the number of clients that are currently connected to the site VPN:

show controllers openvpn site client-count


(Dub)>show controllers openvpn siteopenvpn site system-name=ovpn_site status=enabled link-state=up mode=site-server protocol=udp port=1194 cipher=blowfish-128 keep-alive-inactive=30 keep-alive-disconnect=120 client-route=ethernet 2 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)>

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

7-7

Remote RMC-700 Version 5.2x Configuration GuideConfiguring a Site VPN Connection: Verifying the VPN Connection from the Client

Verifying the VPN Connection from the ClientThe VPN connection between the client and the Remote RMC-700 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.

Note: A connection from the client to the Remote RMC-700 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


To verify the number of clients that are connected:

show controllers openvpn site client-count


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.


Verify that a client is connected

Verify the number of clients that are connected

(Dub)>show controllers openvpn site clients>test addr10.39.7.9:1194 virtual-addr=192.168.101.6 connected=Mon Dec 10 13:27:30 EST 2012 rx-bytes=24617 tx-bytes=32053(Dub)>

(Dub)>show controllers openvpn site client-countNumber of known clients: 1Number of authenticated clients: 1(Dub)>

7-8

8

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



8-1

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Static Routes: Adding 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



In this scenario, you will add an IPv4 static route to the IP routing table.

(Dub)>show ip routeDestination Gateway Interface Flags10.40.0.0/16 0.0.0.0 bridge switch Up127.0.0.0/8 0.0.0.0 * Reject Up127.0.0.1/32 0.0.0.0 lo Host Up128.14.0.0/16 10.40.2.18 bridge switch Up(Dub)>

8-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Static Routes: Adding 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:

config ip route default 10.40.0.1

2. (optional) Verify the default static route has been added properly:

show ip route



In this scenario, you will add a default IPv4 static route to the IP routing table.

(Dub)>show ip routeDestination Gateway Interface Flags0.0.0.0/0 10.40.0.1 openvpn client Up10.40.0.0/16 0.0.0.0 bridge switch Up127.0.0.0/8 0.0.0.0 * Reject Up127.0.0.1/32 0.0.0.0 lo Up Host128.14.0.0/16 10.40.2.18 bridge switch Up(Dub)>

8-3

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Static Routes: Adding 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



In this scenario, you will add an IPv6 static route to the IP routing table.

(Dub)>show ip routeDestination Gateway Interface Flags0.0.0.0/0 10.39.0.1 bridge switch Up10.39.0.0/16 0.0.0.0 bridge switch Up127.0.0.0/8 0.0.0.0 * Up Reject127.0.0.1/32 0.0.0.0 lo Up Host169.254.0.0/16 0.0.0.0 bridge switch Up

fc10:0:0:39::/64 :: bridge switch Upfd10:0:0:39::/64 :: bridge switch Upfd11:0:0:40::/64 fd10::39:0:0:1:1 bridge switch Upfe80::/64 :: bridge switch Upff00::/8 :: bridge switch Upff02::fb/128 ff02::fb bridge switch Upff02::1:ffcb:4e8b/128 ff02::1:ffcb:4e8b bridge switch Up(Dub)>

8-4



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


Note: If an IPv6 router is advertising itself on the network and IPv6 is enabled on

the interface, the Remote RMC-700 route table may include a route which uses the router’s link-local IPV6 address as the default IPv6 static route.


In this scenario, you will add a default IPv6 static route to the IP routing table.

(Dub)>show ip routeDestination Gateway Interface Flags0.0.0.0/0 10.39.0.1 bridge switch Up10.39.0.0/16 0.0.0.0 bridge switch Up127.0.0.0/8 0.0.0.0 * Up Reject127.0.0.1/32 0.0.0.0 lo Up Host169.254.0.0/16 0.0.0.0 bridge switch Up192.168.101.0/32 0.0.0.0 openvpn site Up Host192.168.101.0/24 0.0.0.0 openvpn site Up192.168.101.1/32 127.0.0.1 lo Up Host

default fe80::e611:5bff:fecb:4e8b bridge switch Up::/0 fd10::39:0:0:1 bridge switch Upfc10:0:0:39::/64 :: bridge switch Upfd10::/64 :: bridge switch Upfe80::/64 :: bridge switch Upff00::/8 :: bridge switch Upff02::1/128 ff02::1 bridge switch Up(Dub)>

8-5


8-6

9

Configuring a Wireless Network with Remote RMC-700

This chapter provides information about configuring a wireless network with Remote RMC-700.


Getting Started

Sample Configuration

Configuring the Wireless Modem

Configuring the VPN

9-1

Remote RMC-700 Version 5.2x Configuration GuideConfiguring a Wireless Network with Remote RMC-700: Getting Started

Getting StartedThis section discusses the following topics:

Wireless Network Overview

Required Components

Initial Setup

Wireless Network OverviewRemote RMC-700 models can be equipped with EvDO or UMTS modules. These modules allow users to locate Remote RMC-700s in areas that do not have traditional WAN connectivity. A wireless Remote RMC-700 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 RMC-700 communicates with the service provider’s management network by delivering alarms to it. The management network tries to establish connections to Remote RMC-700 or to network elements connected to the Remote RMC-700.

Required ComponentsWhen operating in a wireless network, Remote RMC-700 works in conjunction with the following Kentrox products:

Connect SCSConnect SCS acts as the VPN server for Remote RMC-700. For more information about Connect SCS, refer to the Connect SCS Configuration Guide.

Director SCDDirector 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.

The Client OpenVPN controller on the Remote RMC-700 uses OpenVPN software to establish the VPN between Connect SCS and Remote RMC-700. 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 customer’s firewalls. The customers

9-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring a Wireless Network with Remote RMC-700: Getting Started

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 RMC-700 and Connect SCS to detect connection failures and to keep an active firewall state.

Initial SetupUsers must set up the following configurations for Remote RMC-700 to operate in a wireless network.

To set up the initial configurations:

1. Connect to Remote RMC-700, 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 RMC-700 as a new client

Create an association between Remote RMC-700 and the appropriate Connect SCS VPN server

Generate a new token for Remote RMC-700

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 RMC-700 to be installed

Generate a new token

Save the token as a file on the laptop

Use a local Ethernet connection to the Remote RMC-700 bridge to transfer the token via FTP/SFTP to file /config/openvpn/bundle/bundle.cfg on the Remote RMC-700.

5. Verify that Remote RMC-700 is connected to the management network.

9-3

Remote RMC-700 Version 5.2x Configuration GuideConfiguring a Wireless Network with Remote RMC-700: Sample Configuration

Sample ConfigurationFigure 9-1 displays Remote RMC-700 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 9-1 Wireless Network Example

Sections Configuring the Wireless Modem on page 9-5 and Configuring the VPN on page 9-8 provide procedures for making the above configurations on Remote RMC-700.

9-4

Remote RMC-700 Version 5.2x Configuration GuideConfiguring a Wireless Network with Remote RMC-700: Configuring the Wireless Modem

Configuring the Wireless ModemImportant: 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).

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 controller’s connection string as AT+CGDCONT=1, "IP", "valid_APN" AT ATD*99***1#:

config controller serial modem connect string AT+CGDCONT=1, "IP", "valid_APN" 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>


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.

9-5


4. Configure the following ppp encapsulation settings:

Remote method pap

Remote username [email protected] 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 RMC-700

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 [email protected] 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


6. Enable interface serial modem:

config interface serial modem enable

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

show interfaces serial modem

(Dub)>show controllers serial modemserial modem status=enabled link-state=up encapsulation=ppp init-string=AT+CGDCONT=1, "IP", "valid_APN" 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 modemppp defaultroute=truelocal-method=none local-identity= remote-method=pap [email protected] mru=1520 mtu=1520 lcp-requests=disabled(Dub)>

9-6



(Dub)>show interface serial modemserial 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 Overrun Framing Rx 31242388 182608 0 0 0 0 Tx 29748523 173100 0 0 0 0(Dub)>

9-7

Remote RMC-700 Version 5.2x Configuration GuideConfiguring a Wireless Network with Remote RMC-700: Configuring the VPN

Configuring the VPNImportant: 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 RMC-700. If you used one of these methods to configure the VPN, then you do not need to do this procedure.

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 RMC-700 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



Configure an OpenVPN controller

Configure an OpenVPN interface

(Dub)>show controllers openvpnopenvpn 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)>

9-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 openvpnopenvpn client system-name=ovpn_client status=enabled link-state=up address=192.168.100.80/24(Dub)>

9-9


9-10

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

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Actions, Events and Responses: Overview

OverviewActions are rules in Remote RMC-700 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:

Events—System occurrences related to changes in Remote RMC-700’s equipment or the environment.

Responses—Behaviors that are executed in response to system events.

Actions—Rules that create associations between responses and events.

During normal Remote RMC-700 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.

10-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Actions, Events and Responses: Overview

Figure 10-1 illustrates the sequence of events that occurs when action MyActions’s event (MyEvent) occurs.

Figure 10-1 Sequence of Events

Note: Several commands exist in the Remote RMC-700 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 RMC-700 Command Reference Guide.

10-3

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Actions, Events and Responses: Event Components

Event ComponentsFigure 10-2 illustrates a sample event configuration:

Figure 10-2 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 RMC-700 Command Reference Guide.

event name originator event type

config event MyEvent content input 0/1 close

10-4

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Actions, Events and Responses: Response Components

Response ComponentsFigure 10-3 illustrates a sample response configuration:

Figure 10-3 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 RMC-700 Command Reference Guide.

response name responder response type

config response MyResponse content output 0/1 close

10-5

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Actions, Events and Responses: Action Components

Action ComponentsFigure 10-4 illustrates a sample action configuration:

Figure 10-4 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 RMC-700

Command Reference Guide.

action name event name response name

config action MyAction event MyEvent response MyResponse

10-6

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Actions, Events and Responses: Configuring an Event, Response and Action

Configuring an Event, Response and Action

To configure the event, response and action:

1. At the main prompt, configure event one_close with event originator input0/1 and event type close:

config event one_close content input 0/1 close

Note: For information about specific event originators and event types, refer to

command config event content in the Remote RMC-700 Command Reference Guide.

2. Configure response Output0_1 with responder output 0/1 and response type open:

config response Output0_1 content output 0/1 open

Note: For information about specific responders and response types, refer to the

response configuration commands in the Remote RMC-700 Command Reference Guide.

3. Configure action One_Close with event one_close and response Output0_1:

config action One_Close event one_close response Output0_1


Configure an event that occurs when the discrete input 0/1 closes.

Configure a response that opens a relay output point

Configure an action that associates the event with the response.

10-7

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Actions, Events and Responses: Configuring an Event, Response and Action

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

show actions One_Close



(Dub)>show actions One_CloseAction Name : One_CloseAction Description :

Event Name : One_CloseEvent Description :Event Originator : input 0/1Event Type : close

Response Name : Output0_1Response Description :Response Responder : output 0/1Response Type : openResponse Parameters :No parameters configured for this response.(Dub)>

10-8

11

Configuring Technician Laptop Access for Remote RMC-700

This chapter provides information on configuring Remote RMC-700 network access to locally-connected technician laptops.


Configuration Overview

Assigning IP Addresses to Technician Laptops

Configuring IPTables for Network Address Translation

11-1

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Technician Laptop Access for Remote RMC-700: Configuration Overview

Configuration OverviewFigure 11-1 displays what happens when a technician’s laptop accesses the network by connecting to Remote RMC-700.

Figure 11-1 Technician Laptop Access via Remote RMC-700

IP Network

Server

Technician Laptop

IPTables

Remote RMC-700

64.152.3.27

DHCP Server

10.10.10.12 (Private Address)

The DHCP Serverassigns a private IPaddress to thetechnician laptop.

(184.155.22.36)

(Public Address)

IPTables rules allow laptopson the private network tosend packets to the WAN with Remote RMC-700’s public address.

11-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Technician Laptop Access for Remote RMC-700: Configuration Overview

When the technician’s laptop is connected to one of the Ethernet ports on Remote RMC-700, the DHCP server automatically assigns an IP address to the laptop. IP addresses that may be assigned to the technician’s laptop are configured using DHCP server configuration commands in the Remote RMC-700 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

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Technician Laptop Access for Remote RMC-700: Assigning IP Addresses to Technician Laptops

Assigning IP Addresses to Technician Laptops

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

Remote RMC-700 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 RMC-700 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.

11-4

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Technician Laptop Access for Remote RMC-700: 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-serverAdmin State: enabledBroadcast: disabledAuthority: disabledConfig 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

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Technician Laptop Access for Remote RMC-700: Configuring IPTables for Network Address Translation

Configuring IPTables for Network Address TranslationIPTables 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).

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 RMC-700 via anSSHconnection and you set the default action to drop all packets without first configuring a rule to accept packets between your workstation and Remote RMC-700 (as in step 2), your connection to Remote RMC-700 will be lost.


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.

11-6

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Technician Laptop Access for Remote RMC-700: Configuring IPTables for Network 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 configurationTable 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)

Chain OUTPUT (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)

Chain OUTPUT (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

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Technician Laptop Access for Remote RMC-700: Configuring IPTables for Network 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

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Event Correlations: Overview

OverviewEvent 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 RMC-700 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 ComponentsEvent correlation is represented by an event originator named correlation and the following components:

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.

12-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Event Correlations: Correlation Expression Components

Correlation Expression ComponentsThe following illustrates a basic expression configuration:

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:

Originator Type, which is one of the Remote RMC-700 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, 0/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 StatesTable 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

Term Operator Term

OriginatorType Instance State and OriginatorType Instance State

Originator Type Valid State Events Multi Support

analog high, in-band, input-saturated, 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, input-saturated, loss of signal, low, <, <=, =, >=, >, !=

yes - point ranges

12-3


ExamplesExamples of these components combined are shown below:

analog 0/1 high

correlation examplecorr false

measurement ExtTemp1 > 90

OperatorsThe 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

Expression EvaluationIn 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.

Operator Usage Example Result

and expression analog 0/1 high and output 0/1 open

When both expressions are true, the evaluation is true.

or expression analog 0/1 high or measurement extTemp > 110

When either expression is true, the evaluation is true.

not expression not analog 0/1 in-band

When negating a true expression, the evaluation is false.

all expression all input 0/1-12 close

When all expressions are true, the evaluation is true.

any expression any 3 input 0/1-5 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.

12-4


Example ExpressionsThe examples below show various forms of Terms in nested expressions.

all input 0/1-4 open and ( analog 0/1 loss-of-signal or analog 0/1 low )

not ( any 3 analog 0/1-4 in-band and correlation myCorrelation false )

all input 1/1,3,5,7 open and correlation myCorrelation true all input 0,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

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Event Correlations: Configuring an Event Correlation

Configuring an Event Correlation

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 0/1 open and input 0/2 open:

config correlation DoorAlarms expression input 0/1 open and input 0/2 open


show correlation DoorAlarms

The command response appears similar to the following:


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 expression’s state

Create two alarm table entries for the open door events.

(Dub)>show correlation DoorAlarmsName : DoorAlarmsExpression : input 0/1 open and input 0/2 openTrue Duration : 900False Duration : 0Evaluation : false and false = false Value : falseDescription : 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 a Measurement Table Entry for State Transitions and Durations 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 Power Supply 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

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Alarm Entries in the Central Alarm Table: Overview

OverviewThe central alarm table collects and communicates the state of all alarms reported by Remote RMC-700. It is a table of alarm entries that contains information for each attainable severity level and has the following features:

Event/alarm associations—The 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 Nagging—Alarm 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 formats—The central alarm table can report alarm statuses in raw, SNMP, or TL1 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 RMC-700 Command Reference Guide.

13-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Alarm Entries in the Central Alarm Table: Alarm Protocol Formats

Alarm Protocol FormatsThe central alarm table supports multiple alarm protocol formats, including:

Raw

SNMP

TL1

You can enable and disable each alarm protocol format independently of the others (meaning that you can have more than one format enabled at a time).

RawThe central alarm table supports raw alarm output that can be used for alarm formats that are not directly supported by Remote RMC-700. A script or application can take the alarm information from the raw output and translate it into any type of alarm message.

SNMPThe 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.

TL1The central alarm table supports TL1 reporting through virtual TL1 NEs. You must configure and enable the desired virtual TL1 NEs to use them with the central alarm table.

13-3

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Temperature Sensor

Configuring an Alarm Entry for a Temperature Sensor

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


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 RMC-700 Command Reference Guide.

13-4

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Temperature

Sensor

7. Configure an event for alarm entry tempSensor with the following settings:

Event originator analog 0/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 0/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 0/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 0/1 in-band normal Temperature in normal range

13-5

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Temperature Sensor

10. (optional) Verify that the alarm entry has been configured properly:

show alarm-entries name tempSensor



Configuring Analog Input ValuesThe values reported by Remote analog inputs oftentimes 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.

Analog AveragingUsers 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.

(Dub)>show alarm-entries name tempSensorName - tempSensorState - normalCurrent Message -Description - Temperature sensorNagging Interval - 5Nagging Level - criticalTrap - enabledTrap Priority - highRaw - enabledTL1 - disabledTL1 AID -TL1 Class - envTL1 Affect - nsaTL1 Type -TL1NE - 1Category - envAlmsNE Name - TempSensorAlarm Actions: Severity Originator Trigger Message------------------------------------------------------------------ critical analog 0/1 high Temperature above sa minor analog 0/1 low Temperature below lo normal analog 0/1 in-band Temperature in norma(Dub)>

13-6

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Temperature

Sensor

.

The following example shows how to configure discrete analog 0/1 with medium level averaging:

config discrete analog 0/1 averaging medium

Analog AdjustmentA 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.

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 0/1 minimum 0 7

config discrete analog 0/1 maximum 10 107

Table 13-1 Analog Averaging Values

Value Description Measurement Example

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.

13-7

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Discrete Input

Configuring an Alarm Entry for a Discrete Input

To configure the open input alarm entry:

1. At the main prompt, configure description Light switch:

config alarm-entry input0_1 description Light Switch

2. Enable tl1 alarm protocol support and set the TL1 alarm class to eqpt (equipment) and the TL1 service state to sa (service-affecting):

config alarm-entry input0_1 tl1 enable

config alarm-entry input0_1 tl1 eqpt

config alarm-entry input0_1 tl1 sa

Note: For information on configuring the TL1 NE and TL1 MUX that monitor the

alarm, refer to Chapter 16: Configuring and Connecting TL1 Infrastructure.

3. Configure an event for alarm entry input0_1 with the following settings:

Event originator input 0/1

Event trigger open

Event severity level major

Alarm event message Light off.

config alarm-entry input0_1 event input 0/1 open major Light off



Configure TL1 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 RMC-700 Command Reference Guide.

13-8

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Discrete Input

4. Configure an event for alarm entry input0_1 with the following settings:

Event originator input 0/1

Event trigger close


Alarm event message Light on.

config alarm-entry input0_1 event input 0/1 close major Light on


show alarm-entries name input0_1



(Dub)>show alarm-entries name input0_1Name - input0_1State - normalCurrent Message -Description - Light SwitchNagging Interval - 0Nagging Level - majorTrap - enabledRaw - disabledTL1 - enabledTL1 AID -TL1 Class - eqptTL1 Affect - saTL1 Type -TL1NE - 1Category -NE Name -Alarm Actions: Severity Originator Trigger Message------------------------------------------------------------------ major input 0/1 open Light off major input 0/1 close Light on(Dub)>

13-9

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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

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 1

Event trigger conn-failed


Alarm event message The serial connection has failed.

config alarm-entry SerConnFail event serial 1 conn-failed major The serial connection has failed



Configure SNMP alarm protocol support

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 RMC-700 Command Reference Guide.

13-10

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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 SerConnFailName - SerConnFailState - normalCurrent Message -Description - Serial connection failureNagging Interval - 0Nagging Level - majorTrap - enabledRaw - disabledTL1 - disabledTL1 AID -TL1 Class - envTL1 Affect - nsaTL1 Type -TL1NE - 1Category -NE Name -Alarm Actions: Severity Originator Trigger Message------------------------------------------------------------------ major serial 1 conn-faile The serial connectio(Dub)>

13-11

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Power Supply Failure

Configuring an Alarm Entry for a Power Supply Failure

To configure an alarm entry for a power supply failure:

1. At the main prompt, configure description 24 volt power supply failure:

config alarm-entry powerFail24 description 24 volt power supply failure

2. Enable tl1 alarm protocol support and set the TL1 alarm class to eqpt (equipment) and the TL1 service state to sa (service-affecting):

config alarm-entry powerFail24 tl1 enable

config alarm-entry powerFail24 tl1 eqpt

config alarm-entry powerFail24 tl1 sa

Note: For information on configuring the TL1 NE and TL1 MUX that monitor the

alarm, refer to Chapter 16: Configuring and Connecting TL1 Infrastructure.

3. Configure an event for alarm entry powerFail5 with the following settings:

Event originator system

Event trigger power-fail-24


Alarm event message 24 volt power supply failure.

config alarm-entry powerFail24 event system power-fail-24 critical 24 volt power supply failure



Configure TL1 alarm protocol support

Configure an alarm action that signals that a power supply failure has occurred.

13-12

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Alarm Entries in the Central Alarm Table: Configuring an Alarm Entry for a Power Supply

Failure


show alarm-entries name powerFail24



(Dub)>show alarm-entries name powerFail24Name - powerFail24State - normalCurrent Message -Description - 24 volt power supply failureNagging Interval - 0Nagging Level - majorTrap - enabledRaw - disabledTL1 - enabledTL1 AID -TL1 Class - eqptTL1 Affect - saTL1 Type -TL1NE - 1Category -NE Name -Alarm Actions: Severity Originator Trigger Message------------------------------------------------------------------ critical system power-fail 24 volt power supply(Dub)>

13-13

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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

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 conn-down major TCP connection down




Configure an alarm action that signals that a TCP connection has gone down.

13-14

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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 TCPConnDownName - TCPConnDownState - normalCurrent Message -Description - TCP connection downNagging Interval - 0Nagging Level - majorTrap - enabledRaw - disabledTL1 - disabledTL1 AID -TL1 Class - envTL1 Affect - nsaTL1 Type -TL1NE - 1Category -NE Name -Alarm Actions: Severity Originator Trigger Message------------------------------------------------------------------ major tcp 192.168.0.12 conn-down TCP connection down(Dub)>

13-15

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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

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.




Configure an alarm action that signals that a Telnet connection has come up.

13-16

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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 TelnetConnUpName - TelnetConnUpState - normalCurrent Message -Description - Telnet connection upNagging Interval - 0Nagging Level - majorTrap - enabledRaw - disabledTL1 - disabledTL1 AID -TL1 Class - envTL1 Affect - nsaTL1 Type -TL1NE - 1Category -NE Name -Alarm Actions: Severity Originator Trigger Message------------------------------------------------------------------ normal telnet 192.168.0 conn-up Telnet connection no(Dub)>

13-17

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Alarm Entries in the Central Alarm Table: Testing Alarm Table Configurations

Testing Alarm Table ConfigurationsAfter 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.

To simulate a test trap from the Remote alarm table:

1. Simulate a test trap with a normal state for 5 minutes for alarm entry GPS_Failure:

diag test alarm-entry GPS_Failure mode normal 5

2. (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).

In this scenario, you will simulate a test trap from Remote for a specific alarm entry.

(Dub)>show(Dub) show>test(Dub) show test> alarm-entriesName State Current alarm message----------------------------------------------------------------------Explosive_Gas normal Explosive Gas Not DetectedGPS_Failure normal GPS NormalGenerator_OilPressur normal ---NewTest normal ---Toxic_Gas normal ---(Dub) show test

13-18

14

Configuring Measurements and the Measurement Table

This chapter provides an overview of the Remote RMC-700’s measurement table and step-by-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 a Measurement Table Entry for State Transitions and Durations

14-1

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Measurements and the Measurement Table: Overview

OverviewIn addition to its central alarm table, the Remote RMC-700 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 the Remote RMC-700’s analog input, from a script running on the Remote RMC-700 that monitors an attached network element, or via SNMP from a network element that is monitored by SNMP proxy. The Remote RMC-700 measurement table stores a 7-day history of collected values.

Figure 14-1 Remote RMC-700 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 0/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.

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-signal—The value has passed below the minimum measurable threshold

Low—The value has passed below the minimum value that is considered normal

14-2


In-band—The value falls between the minimum normal value and the maximum normal value

High—The value has passed above the maximum value that is considered normal

Input-saturated—The value has passed above the maximum measurable threshold

Offline—The originator of the value has gone offline and is not reporting a value

Use for Measuring State Transitions and DurationsTransition and duration information for state changes on alarm entries and status points can also be obtained. The measurement table entry provides a new originator which contains a function that references an alarm entry or status point and calculates the measurement value.

@state-transition counts the number of times an originator (alarm entry or status point) transitions to a particular state within a measurement interval. The transition count is reported as a whole number and resets to zero at the start of each measurement period.

@state-duration counts the number of seconds an originator (alarm entry or status point) is in a particular state within a measurement interval. The duration count is reported as a sum for the current measurement interval and is rounded to the nearest whole second. The duration count will reset to zero at the start of each measurement interval.

See Configuring a Measurement Table Entry for State Transitions and Durations on page 14-10 for an example.

Use with Alarm Table EntriesMeasurement table entries can be used in connection with Remote RMC-700’s 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 CorrelationsYou can create event correlations to be used with measurement table entries. The example in section Configuring a Measurement Table Entry for State Transitions and Durations 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.

14-3


Use with Proxied SNMP NEsSee Chapter 19: 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-4

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Measurements and the Measurement Table: Configuring a Measurement Table Entry for a

Temperature Sensor

Configuring a Measurement Table Entry for a Temperature Sensor

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


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 0/1

9. Enable the measurement table entry:

config meas-table entry ExtTemp1 enable


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

14-5

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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



Sample Configuration for SiteBus Temperature SensorThe following is a sample configuration for a measurement table entry for the SiteBus temperature sensor. 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_RMX3200

config meas-table entry TempSensor1 units degrees Fahrenheit

(Dub)>show meas-table entries ExtTemp1Name - ExtTemp1 (static)State - in-bandOriginator - analog 0/1Description - External temperature sensorNE Name - sensorUnitCategory - envAlmsReport Interval - 0Low-Band - 65.High-Band - 80.Hysteresis - 0.Max-Limit - 130.Min-Limit - -30.Units - Degrees F

Current Value - 72Interval Value - ?Interval Minimum - ?Interval Maximum - ?Interval Average - ?(Dub)>

14-6

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Measurements and the Measurement Table: Configuring an Alarm Entry for a Measurement

Configuring an Alarm Entry for a Measurement

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)


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

14-7




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 input-saturated critical Input saturated



Event trigger loss-of-signal


Alarm event message Signal loss.

config alarm-entry ExtTemp event measurement ExtTemp1 loss-of-signal critical Signal loss

14-8



show alarm-entries name ExtTemp



(Dub)>show alarm-entries name ExtTempName - ExtTempState - normalCurrent Message -Description - Exterior temperature alarmNagging Interval - 0Nagging Level - majorTrap - enabledTrap Priority - normalRaw - disabledTL1 - disabledTL1 AID -TL1 Class - envTL1 Affect - nsaTL1 Type -TL1NE - 1Category - envAlmsNE Name - sensorUnitOriginator - measurement ExtTemp1Alarm 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-9

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Measurements and the Measurement Table: Configuring a Measurement Table Entry for State Transitions and Durations

Configuring a Measurement Table Entry for State Transitions and Durations

To configure a measurement table entry that tracks the number of times the alarm table entry ExtTemp1 transitions to the major state:

1. At the main prompt, configure measurement table entry ExtTemp1_Transitions with description Number of External temperature high alarms:

config meas-table entry ExtTemp1_Transitions description Number of External temperature high alarms

2. Configure the originator for this measurement with the following settings:

Measurement function @state-transitions

Originator alarm-entry ExtTemp1

Active state major

config meas-table entry ExtTemp1_Transitions originator @state-transitions (alarm-entry ExtTemp1, major)

Note: The measurement function @state-duration can be used to measure

the number of seconds an alarm is in the specified active state.

3. (optional) Verify that the measurement table entry has been configured properly:

show meas-table entries ExtTemp1_Transitions


Configure a measurement table entry with name and description

Configure the originator to use the @state-transitions function to measure the number of state transitions

14-10

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Measurements and the Measurement Table: Configuring a Measurement Table Entry for

State Transitions and Durations


(Dub)>show meas-table entries ExtTemp1_TransitionsName – ExtTemp1_Transitions (static)State – in-bandOriginator - @state-transitions ( alarm-entry ExtTemp1 , major )Description – Number of External temperature high alarmsNE Name - Category - Report Interval - 0Low-Band - 0High-Band - 0Hysteresis - 0Max-Limit - 0Min-Limit - 0Units - Current Value - 3Interval Value - 0Interval Minimum - 0Interval Maximum - 0Interval Average - 0(Dub)>

14-11

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Measurements and the Measurement Table: Configuring an Event Correlation for a Measurement

Configuring an Event Correlation for a Measurement

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 0/3) as open:

config correlation FireDanger expression measurement ExtTemp1 >= 90 and input 0/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 correlation FireDanger



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 0/3) exists

Configure the time (duration) for which the expression must remain true or false before the correlation matches the expression’s state

Create two alarm table entries for the correlation.

(Dub)>show correlation FireDangerName : FireDangerExpression : measurement ExtTemp1 >= 90 and input 0/3 openTrue Duration : 90False Duration : 0Evaluation : false and false = false Value : falseDescription : Correlation for temperature and smoke(Dub)>

14-12

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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-13

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Measurements and the Measurement Table: Configuring an Event Correlation for a Measurement

14-14

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

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Mediation Connections: Overview

OverviewMediation 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

TCP to TL1 multiplexer connections and TL1 multiplexer to network element (NE) 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.

Except for mediation connections between an NE and a TL1 multiplexer, mediation connections are established through the configuration of events, responses and actions.

Note: For more information on how to configure mediation connections between an

NE and a TL1 multiplexer, refer to Chapter 16: Configuring and Connecting TL1 Infrastructure.

15-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Mediation Connections: Secure Terminal Server Access

Secure Terminal Server AccessThe secure terminal server access feature provides a layer of encryption and authentication, creating a secure connection from a workstation to Remote RMC-700 to access a connected NE. The connection from Remote RMC-700 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 port’s 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

15-3

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Mediation Connections: Secure Terminal Server Access

Terminal Server User AccessA 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 logout; no files will be available for retrieval via SFTP.

TACACS+ ConfigurationIf your Remote RMC-700 is configured for TACACS+, authorization and accounting of the secure terminal server login is performed according to your Remote RMC-700’s configuration. The authorization uses a TACACS+ service, aimediation, which is different from the one used for CLI logins. The aimediation service must be added to the TACACS+ server and associated with the appropriate users and groups.

See the config mediation tacacs-service command in the Remote RMC-700 Command Reference Guide for more information.

15-4

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Mediation Connections: Configuring a TCP to Asynchronous Serial Connection

Configuring a TCP to Asynchronous Serial Connection

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 incoming-connection

Note: The TCP originator IP address is optional if it is the same as the Remote

RMC-700 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


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.

(Dub)>show actions tcpToSerial2Action Name : tcpToSerial2Action Description :

Event Name : tcp40010Event Description :Event Originator : tcp 10.40.57.5:40010Event Type : incoming-connection

Response Name : tcp40010ToSerial2Response Description :Response Responder : tcp 10.40.57.5:40010Response Type : connectResponse Parameters : dest=serial 2(Dub)>

15-5

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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


Note: The 4 that comes after the TCP port number is an internal reference

number generated by Remote RMC-700.


(Dub)>show connectionstcp 10.40.57.5:40010:4 -> serial 2(Dub)>

15-6

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Mediation Connections: Configuring a Telnet to Asynchronous Serial Connection

Configuring a Telnet to Asynchronous Serial Connection

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 telnet60002ToSerial1 to connect Telnet port 60002 at IP address 10.40.57.5 to destination serial 1:

config response telnet60002ToSerial1 content telnet 10.40.57.5:60002 connect dest serial 1

3. Configure response telnet60002ToSerial1 to cause a Telnet connection from port 60002 at IP address 10.40.57.5 to operate in binary mode:

config response telnet60002ToSerial1 content telnet 10.40.57.5:60002 connect options -b

4. Configure action telnetToSerial to associate event IncTelnetConn with response telnet60002ToSerial1:

config action telnetToSerial event IncTelnetConn response telnet60002ToSerial1

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.

15-7

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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








show connections





(Dub)>show actions telnetToSerialAction Name : telnetToSerialAction Description :

Event Name : IncTelnetConnEvent Description :Event Originator : telnet 10.40.57.5:60002Event Type : incoming-connection

Response Name : telnet60002ToSerial1Response Description :Response Responder : telnet 10.40.57.5:60002Response Type : connectResponse Parameters : dest=serial 1 options=-b(Dub)>

(Dub)>show connectionstelnet 10.40.57.5:40010:4 -> serial 1(Dub)>

15-8

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Mediation Connections: Configuring a SSH to Asynchronous Serial Connection

Configuring a SSH to Asynchronous Serial Connection

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 SSH20001ToSerial2 to connect SSH port 20001 at IP address 10.40.57.5 to destination serial 2:

config response SSH20001ToSerial2 content ssh 10.40.57.5:20001 connect dest serial 2

3. Configure action SSHToSerial to associate event IncSSHConn with response SSH20001ToSerial2:

config action SSHToSerial event IncSSHConn response ssh20001ToSerial2

4. (optional) Verify that the SSH to asynchronous connection has been configured properly:

show actions SSHToSerial


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

A service that is passed to the TACACS+ server when authenticating users for mediation

(Dub)>show actions SSHToSerialAction Name : SSHToSerialAction Description :

Event Name : IncSSHConnEvent Description :Event Originator : ssh 10.40.57.5:20001Event Type : incoming-connection

Response Name : ssh20001ToSerial2Response Description :Response Responder : ssh 10.40.57.5:20001Response Type : connectResponse Parameters : dest=serial 2(Dub)>

15-9

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Mediation Connections: Configuring a SSH to Asynchronous Serial Connection







show connections




8. (Optional) Create a new user named ebh, password jimbo, with the restricted profile, authorizing this user for terminal server access:

config users add ebh restricted jimbo jimbo

9. (Optional) Configure the aimediation service (the default) on the TACACS+ server, which will be used when authenticating users for mediation:

config mediation default tacacs-service

Note: You will need to add priv_lvl=0 to the aimediation service on the

TACACS+ server.


(Dub)>show connectionsssh 10.40.57.5:20001:4 -> serial 2(Dub)>

15-10

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Mediation Connections: Configuring an Asynchronous Serial to Asynchronous Serial

Connection

Configuring an Asynchronous Serial to Asynchronous Serial Connection

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


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.

(Dub)>show actions serial2ToSerial1Action Name : serial2ToSerial1Action Description :

Event Name : serial2UpEvent Description :Event Originator : serial 2Event Type : up

Response Name : serial2ConnectResponse Description :Response Responder : serial 2Response Type : connectResponse Parameters : dest=serial 1(Dub)>

15-11

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Mediation Connections: Configuring an Asynchronous Serial to Asynchronous Serial 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-12

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Mediation Connections: Configuring an Asynchronous Serial to Asynchronous Serial

Connection

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

show controllers serial 1


show controllers serial 2


10. (optional) Manually connect a device to controller serial 2 and send data.


show connections



(Dub)>show controllers serial 1serial 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)>

(Dub)>show controllers serial 2serial 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)>

(Dub)>show connectionsserial 2 -> serial 1(Dub)>

15-13

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Mediation Connections: Configuring an Asynchronous Serial to TCP Connection

Configuring an Asynchronous Serial to TCP Connection

To configure an asynchronous to TCP connection:

1. Configure event serial1Up with originator serial 1 and event type up:

config event serial1Up content serial 1 up

2. Configure response serial1ConnectToNOC with responder serial 1 and response type connect. The destination of the connect response is TCP port 5001 at IP address 10.40.57.5:

config response serial1ConnectToNOC content serial 1 connect dest tcp 10.40.57.5:5001

3. Configure action serial1ToNOC with event serial1Up and response serial1ConnectToNOC:

config action serial1ToNOC event serial1Up response serial1ConnectToNOC

4. (optional) Verify that the asynchronous to TCP connection has been configured properly:

show actions serial1ToNOC


5. Configure the application mode as source:

config controller serial 1 application source

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.

(Dub)>show actions serial1ToNOCAction Name : serial1ToNOCAction Description :

Event Name : serial1UpEvent Description :Event Originator : serial 1Event Type : up

Response Name : serial1ConnectToNOCResponse Description :Response Responder : serial 1Response Type : connectResponse Parameters : dest=tcp 10.40.57.5:5001(Dub)>

15-14



show connections



(Dub)>show connectionsserial 1 -> tcp 10.40.57.5:5001(Dub)>

15-15


15-16

16

Configuring and Connecting TL1 Infrastructure

This chapter provides information about how to configure a TL1 multiplexer and a virtual TL1 NE. This chapter also provides step-by-step scenarios on how to configure a meditation connection from a TL1 multiplexer to an NE with a TCP or asynchronous connection and how to configure a virtual TL1 NE to establish a meditation connection to a TL1 multiplexer.


Overview

Configuring a TL1 Multiplexer

Configuring a Virtual TL1 NE

Configuring the TCP Port for a TL1 Multiplexer

Configuring a Telnet Connection to a TL1 Multiplexer

Configuring a Telnet Connection to a Virtual TL1 NE

16-1

Remote RMC-700 Version 5.2x Configuration GuideConfiguring and Connecting TL1 Infrastructure: Overview

OverviewIn order to configure TL1 alarms and mediation connections on Remote RMC-700, you must configure the infrastructure for TL1 reporting. TL1 is an ASCII-based language for management of network elements. The TL1 infrastructure on Remote RMC-700 consists of TL1 multiplexers and virtual TL1 NEs (VNEs).

A TL1 multiplexer is a software component that uses TIDs to multiplex several TL1 data streams onto a single TCP connection. It can be configured to connect to varbinds, real TL1 NEs and scripts that generate TL1. A TL1 multiplexer acts like a TL1 GNE, which provides a single point of contact to multiple subtending NEs.

A virtual TL1 NE is a simulation of a TL1 NE environment for generating TL1 alarms and responding to TL1 commands. A VNE typically might be used for generating alarms based upon digital and analog inputs and controlling relay outputs.

Note: TL1 multiplexers and TL1 NEs must be configured for use on the Remote

RMC-700. Refer to the Remote RMC-700 Command Reference Guide.

Notes:

16-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring and Connecting TL1 Infrastructure: Configuring a TL1 Multiplexer

Configuring a TL1 Multiplexer

To configure a TL1 multiplexer:

1. At the main prompt, configure a mediation connection from tl1mux 2 to tl1ne 2:

config mediation tl1mux 2 conn tl1ne2

2. Configure a mediation connection from tl1mux 2 to a real NE with IP address 192.172.3.4, TCP port 5003 and whose TID is TCPTID:

config mediation tl1mux 2 conn 192.172.3.4:5003-TCPTID

3. Configure a mediation connection from tl1mux 2 to a real NE connected to asynchronous port async2 and whose TID is ASYNCTID:

config mediation tl1mux 2 conn async2-ASYNCTID

4. Enable tl1mux 2:

config mediation tl1mux 2 enable

5. (optional) Verify that tl1mux 2 has been configured properly:

show mediation tl1muxes 2




Configure a mediation connection from the TL1 multiplexer to a Varbind (VNE)

Configure a TCP mediation connection from the TL1 multiplexer to a real NE

Configure an asynchronous mediation connection from the TL1 multiplexer to a real NE.

The traffic from these NE’s will be multiplexed onto a single TCP connection through a TL1 multiplexer.

(Dub)>show mediation tl1muxes 2Mux-ID - 2State - enabledConnection Strings: tl1ne2 192.172.3.4:5003-TCPTID async2-ASYNCTID(Dub)>

16-3

Remote RMC-700 Version 5.2x Configuration GuideConfiguring and Connecting TL1 Infrastructure: Configuring a Virtual TL1 NE

Configuring a Virtual TL1 NE

To configure a virtual TL1 NE:

1. At the main prompt, configure a user with login name JohnDoe and password Password for tl1ne 2:

config mediation tl1ne 2 user JohnDoe Password

2. Configure tl1ne 2 and its TID as mytid:

config mediation tl1ne 2 tid mytid

3. Enable tl1ne 2:

config mediation tl1ne 2 enable

4. Configure tl1ne 2 to send autonomous messages without a login:

config mediation tl1ne 2 automsgs nologon

5. Configure tl1ne 2 to send header messages without a login:

config mediation tl1ne 2 rtrvhdr nologon

6. (optional) Verify that tl1ne 2 has been configured properly:

show mediation tl1nes 2



In this scenario, you will configure the login information, TID and message settings for a virtual TL1 NE.

Note: A virtual NE listens for a connection from a TL1 multiplexer above it in the

TL1 infrastructure. Once a multiplexer has made a connection to the VNE, a user or OSS can log in using the ACT-USER command. Currently, each VNE supports a single user session.

(Dub)>show mediation tl1nes 2NE-ID - 2State - enabledAutoMsgs - nologonRtrvHdr - nologonTID - mytidDescription:Users: UID PID ---------- ---------- JohnDoe Password(Dub)>

16-4

Remote RMC-700 Version 5.2x Configuration GuideConfiguring and Connecting TL1 Infrastructure: Configuring the TCP Port for a TL1 Multiplexer

Configuring the TCP Port for a TL1 Multiplexer

To configure an incoming TCP connection to connect to a TL1 multiplexer using events, responses and actions:

1. At the main prompt, configure event ossConnection with originator as tcp 40002 and event type as incoming-connection:

config event ossConnection content tcp 40002 incoming-connection

2. Configure response connectToMux2 with the responder as tcp 40002 and with the response type as connect. The destination is tl1mux 2:

config response connectToMux2 content tcp 40002 connect dest tl1mux 2

3. Configure action ossToMux with event ossConnection and response connectToMux2:

config action ossToMux event ossConnection response connectToMux2

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

show actions ossToMux



In this scenario, you will: Configure an event that matches an incoming TCP connection on TCP port

40002 Configure a response that connects the incoming TCP connection to a TL1

multiplexer Configure an action that associates the event with the response. When Remote

RMC-700 receives the incoming TCP connection, the action connects it to the TL1 multiplexer.

(Dub)>show actions ossToMuxAction Name : ossToMuxAction Description :

Event Name : ossConnectionEvent Description :Event Originator : tcp 40002Event Type : incoming-connection

Response Name : connectToMux2Response Description :Response Responder : tcp 40002Response Type : connectResponse Parameters : dest=tl1mux 2(Dub)>

16-5

Remote RMC-700 Version 5.2x Configuration GuideConfiguring and Connecting TL1 Infrastructure: Configuring a Telnet Connection to a TL1 Multiplexer

Configuring a Telnet Connection to a TL1 Multiplexer

To configure a Telnet connection to a TL1 multiplexer:

1. At the main prompt, configure event telnetConn to signal that an incoming telnet connection request has been received on port 40004:

config event telnetConn content telnet 40004 incoming-connection

2. Configure response telnet40004ToMux3 to connect Telnet port 40004 to destination tl1mux 3:

config response telnet40004ToMux3 content telnet 40004 connect dest tl1mux 3

3. Configure action telnetToMux to associate event telnetConn with response telnet40004ToMux3:

config action telnetToMux event telnetConn response telnet40004ToMux3

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

show actions telnetToMux




Configure an event to signal that an incoming Telnet connection request has been received on a port

Configure a response to connect a Telnet port to a TL1 multiplexer destination

Configure an action to associate the event with the response.

(Dub)>show actions telnetToMuxAction Name : telnetToMuxAction Description :

Event Name : telnetConnEvent Description :Event Originator : telnet 40004Event Type : incoming-connection

Response Name : telnet40004ToMux3Response Description :Response Responder : telnet 40004Response Type : connectResponse Parameters : dest=tl1mux 3(Dub)>

16-6

Remote RMC-700 Version 5.2x Configuration GuideConfiguring and Connecting TL1 Infrastructure: Configuring a Telnet Connection to a Virtual TL1 NE

Configuring a Telnet Connection to a Virtual TL1 NE

To configure a Telnet connection to a VNE:

1. At the main prompt, configure event telnetConn to signal that an incoming telnet connection request has been received on port 40004:

config event telnetConn content telnet 40004 incoming-connection

2. Configure response telnet40004ToVne3 to connect Telnet port 40004 to destination tl1ne 3:

config response telnet40004ToVne3 content telnet 40004 connect dest tl1ne 3

3. Configure action telnetToVne to associate event telnetConn with response telnet40004ToVne3:

config action telnetToVne event telnetConn response telnet40004ToVne3

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

show actions telnetToVne




Configure an event to signal that an incoming Telnet connection request has been received on a port

Configure a response to connect a Telnet port to a VNE destination

Configure an action to associate the event with the response.

(Dub)>show actions telnetToVneAction Name : telnetToVneAction Description :

Event Name : telnetConnEvent Description :Event Originator : telnet 40004Event Type : incoming-connection

Response Name : telnet40004ToVne3Response Description :Response Responder : telnet 40004Response Type : connectResponse Parameters : dest=tl1ne 3(Dub)>

16-7

Remote RMC-700 Version 5.2x Configuration GuideConfiguring and Connecting TL1 Infrastructure: Configuring a Telnet Connection to a Virtual TL1 NE

16-8

17

Configuring DHCP

This chapter provides information on configuring the DHCP server with an associated host and subnet and configuring DHCP client support.


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

17-1

Remote RMC-700 Version 5.2x Configuration GuideConfiguring DHCP: DHCP Server Overview

DHCP Server OverviewThe DHCP server lets hosts connected to Remote RMC-700's Ethernet interfaces or bridge WAN interfaces request and obtain IP addresses from Remote RMC-700. 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.

DHCP Client SupportProviding DHCP client support on Remote RMC-700 will allow the Remote RMC-700 device to dynamically configure its network information from a DHCP server. This reduces the amount of configuration required from the user to gain network access to a Remote RMC-700 and centralizes the control of IP address to a single DHCP server. With the DHCP client enabled on an interface, Remote RMC-700 has the ability to dynamically configure an interface's IP address, DNS server information, domain name information and NTP server information.

Note: For more information on DHCP, refer to the dhcpd linux man page.

17-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring DHCP: Configuring a DHCP Server

Configuring a DHCP Server

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 17-6.


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.

17-3

Remote RMC-700 Version 5.2x Configuration GuideConfiguring DHCP: Configuring a DHCP Server


show dhcp-server



Tip: Remote RMC-700 lets you specify a DHCP server configuration file. This file overrides any DHCP server settings configured in the Remote RMC-700 CLI. If you do not specify the correct DHCP server configuration file, Remote RMC-700 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 RMC-700 directory /config/dhcp before you can specify it as the configuration file in the Remote RMC-700 CLI. For information about creating a DHCP server configuration file, refer to the dhcpd.conf man page.

(Dub)>show dhcp-serverAdmin State: disabledBroadcast: enabledAuthority: enabledConfig file: Note: User specified configuration files will override configured DHCP server settings.Interfaces: bridge switch

Subnets: 234.55.0.0/16 range=0.0.0.0/0.0.0.0 router=0.0.0.0 default-lease=3600 max-lease=28800 DNS:

Hosts:(Dub)>

17-4

Remote RMC-700 Version 5.2x Configuration GuideConfiguring DHCP: Configuring a DHCP Server Subnet

Configuring a DHCP Server Subnet

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

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.

17-5

Remote RMC-700 Version 5.2x Configuration GuideConfiguring DHCP: Configuring a DHCP Server Subnet


show dhcp-server




Subnets: 234.55.0.0/16 range=234.55.83.2/234.55.83.30 router=234.55.83.1 default-lease=36000 max-lease=40000 DNS: 10.51.2.67

Hosts:(Dub)>

17-6

Remote RMC-700 Version 5.2x Configuration GuideConfiguring DHCP: Configuring a Host on a DHCP Server

Configuring a Host on a DHCP Server

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 17-6.


show dhcp-server




Configure a DHCP server host

Configure a host hardware address

Configure a host IP address.


Subnets: 234.55.0.0/16 range=234.55.83.2/234.55.83.30 router=234.55.83.1 default-lease=36000 max-lease=40000 DNS: 10.51.2.67

Hosts: firstHostConfig MAC=12:E3:A2:45:C5:B3 IP=234.55.83.4(Dub)>

17-7

Remote RMC-700 Version 5.2x Configuration GuideConfiguring DHCP: Configuring BOOTP/DHCP Relay

Configuring BOOTP/DHCP Relay

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



In this scenario, you will configure the BOOTP/DHCP server and enable BOOTP/DHCP relay.

When BOOTP/DHCP relay is enabled, Remote RMC-700 acts as a BOOTP/DHCP relay agent; it passes BOOTP/DHCP configuration information between BOOTP/DHCP clients and servers.

(Dub)>show dhcp-relaybootp/DHCP relay is enabledbootp/DHCP relay servers:172.56.110.2(Dub)>

17-8

Remote RMC-700 Version 5.2x Configuration GuideConfiguring DHCP: Configuring DHCP Client Support

Configuring 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.


In this scenario, you will enable DHCP client support and configure a ten-minute interval for Remote RMC-700 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.

(Dub)>show interface bridge switchbridge switch system-name=br_switch status=enabled link-state=up 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 Apr 16 13:57:37 EST 2010 dhcp-lease-expires=Sun Apr 18 13:57:37 EST 2010 dhcp-routers=10.44.0.1 dhcp-server-id=10.25.2.102 Stats: Bytes Packets Errors Dropped Overrun Framing Rx 2348892 12929 0 0 0 0 Tx 2050152 11687 0 0 0 0

ethernet 1 Stats: Bytes Packets Errors Dropped Overrun Framing Rx 2587084 12964 0 0 0 0 Tx 2618834 19175 0 0 0 0

ethernet 2 Stats: Bytes Packets Errors Dropped Overrun Framing Rx 0 0 0 0 0 0 Tx 0 0 0 0 0 0

--More--

17-9

Remote RMC-700 Version 5.2x Configuration GuideConfiguring DHCP: Configuring DHCP Client Support

17-10

18

Configuring Relay Outputs

This chapter provides information about how to configure relay outputs.


Overview

Configuring the Mediation TL1 Command

Configuring TL1 Commands to Control a Relay Output

Configuring SNMP to Operate a Relay Output

Directly Controlling a Relay Output

18-1

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Relay Outputs: Overview

OverviewIn this chapter, you will complete a scenario that activates a relay output using a TL1 command. You will configure a virtual NE (VNE) to generate an event when it receives a specific TL1 command. Relay outputs have two states: open and close.

You will configure a VNE to generate an event when a matching TL1 command is received. The TL1 VNE will compare the incoming command code, TID and AID against a configured command. If there is a match, the TL1 VNE will generate the event, which triggers the response to turn on the device (a fan).

Note: For more information on how to configure a TL1 multiplexer and a TL1 VNE,

refer to Configuring a TL1 Multiplexer on page 16-3 and Configuring a Virtual TL1 NE on page 16-4.

18-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Relay Outputs: Configuring the Mediation TL1 Command

Configuring the Mediation TL1 Command

Note: For information about valid default Remote RMC-700 TL1 commands, refer to

Chapter 24: Remote RMC-700 TL1 Commands. All available TL1 commands are documented in the Telcordia GR 833-CORE documentation.

To configure TL1 command patterns for a fan application:

1. Configure TL1 command pattern identifier fanOn with TL1 command OPR-EXT-CONT, TID mytid and AID 1-fan:

config mediation tl1command fanOn OPR-EXT-CONT mytid 1-fan

2. Configure TL1 command pattern identifier fanOff with TL1 command RLS-EXT-CONT, TID mytid and AID 1-fan:

config mediation tl1command fanOff RLS-EXT-CONT mytid 1-fan

3. (optional) Verify that TL1 command pattern fanOn has been configured properly:

show mediation tl1commands fanOn


4. (optional) Verify that TL1 command pattern fanOff has been configured properly:

show mediation tl1commands fanOff


Remote RMC-700 TL1 VNEs can generate events in response to TL1 commands. VNEs match up incoming command codes, TIDs and AIDs against preconfigured command, TID and AID tuplets. If the VNE finds a match, it generates a corresponding event. This event can trigger any response in the system and is used to create a command for relay output activation.In this scenario, you will configure a fan control application that supports configured TL1 commands OPR-EXT-CONT and RLS-EXT-CONT.

(Dub)>show mediation tl1commands fanOnName - fanOnCommand Pattern - OPR-EXT-CONTTID - mytidAID - 1-fan(Dub)>

(Dub)>show mediation tl1commands fanOffName - fanOffCommand Pattern - RLS-EXT-CONTTID - mytidAID - 1-fan(Dub)>

18-3

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Relay Outputs: Configuring TL1 Commands to Control a Relay Output

Configuring TL1 Commands to Control a Relay Output

To configureTL1 commands to control relay outputs:

1. At the main prompt, configure event fanOnCmd with originator tl1ne 2 and event type tl1cmd-rcvd with command fanOn:

config event fanOnCmd content tl1ne 2 tl1cmd-rcvd fanOn

2. At the main prompt, configure event fanOffCmd with originator tl1ne 2 and event type tl1cmd-rcvd with command fanOff:

config event fanOffCmd content tl1ne 2 tl1cmd-rcvd fanOff

3. (optional) At the main prompt, add description Fan control to discrete output 0/1:

config discrete output 0/1 description Fan control

4. Configure response fanOnReponse with responder output 0/1 and response type close:

config response fanOnResponse content output 0/1 close

5. Configure response fanOffReponse with responder output 0/1 and response type open:

config response fanOffResponse content output 0/1 open

6. Configure action fanOnAction with the event fanOnCmd and response fanOnResponse:

config action fanOnAction event fanOnCmd response fanOnResponse

7. Configure action fanOffAction with the event fanOffCmd and response fanOffResponse:

config action fanOffAction event fanOffCmd response fanOffResponse


Configure events that occur when specific TL1 commands are received on a virtual TL1 NE

Configure responses that open and close a relay output

Configure actions that associate the events with the responses.

18-4

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Relay Outputs: Configuring TL1 Commands to Control a Relay Output

8. (optional) Verify that action fanOnAction has been configured properly:

show actions fanOnAction


9. (optional) Verify that action fanOffAction has been configured properly:

show actions fanOffAction



(Dub)>show actions fanOnActionAction Name : fanOnActionAction Description :

Event Name : fanOnCmdEvent Description :Event Originator : tl1ne 2Event Type : tl1cmd-rcvd fanOn

Response Name : fanOnResponseResponse Description :Response Responder : output 0/1Response Type : closeResponse Parameters :No parameters configured for this response.(Dub)>

(Dub)>show actions fanOffActionAction Name : fanOffActionAction Description :

Event Name : fanOffCmdEvent Description :Event Originator : tl1ne 2Event Type : tl1cmd-rcvd fanOff

Response Name : fanOffResponseResponse Description :Response Responder : output 0/1Response Type : openResponse Parameters :No parameters configured for this response.(Dub)>

18-5

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Relay Outputs: Configuring SNMP to Operate a Relay Output

Configuring SNMP to Operate a Relay Output

To configure SNMP to manage a relay output:

1. Configure SNMP event snmpClose with manager set output1_close:

config event snmpClose content snmp manager-set output1_close

2. Configure SNMP event snmpOpen with manager set output1_open:

config event snmpOpen content snmp manager-set output1_open

3. Configure response switchClose to close output 0/1:

config response switchClose content output 0/1 close

4. Configure response switchOpen to open output 0/1:

config response switchOpen content output 0/1 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


Configure SNMP events to generate manager sets

Configure relay output close and open responses

Configure actions to associate the events with the responses.

18-6

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Relay Outputs: Configuring SNMP to Operate a Relay Output

7. (optional) Verify that action snmpOutputClose has been configured properly:

show actions snmpOutputClose


8. (optional) Verify that action snmpOutputOpen has been configured properly:

show actions snmpOutputOpen



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 (output1_close and output1_open).

(Dub)>show actions snmpOutputCloseAction Name : snmpOutputCloseAction Description :

Event Name : snmpCloseEvent Description :Event Originator : snmpEvent Type : manager-set output1_close

Response Name : switchCloseResponse Description :Response Responder : output 0/1Response Type : closeResponse Parameters :No parameters configured for this response.(Dub)>

(Dub)>show actions snmpOutputOpenAction Name : snmpOutputOpenAction Description :

Event Name : snmpOpenEvent Description :Event Originator : snmpEvent Type : manager-set output1_open

Response Name : switchOpenResponse Description :Response Responder : output 0/1Response Type : openResponse Parameters :No parameters configured for this response.(Dub)>

18-7

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Relay Outputs: Directly Controlling a Relay Output

Directly Controlling a Relay Output

To directly open and close a relay output:

1. Open output 0/1:

diag output 0/1 open

2. Close output 0/1 for 10 seconds:

diag output 0/1 close 10

3. (optional) Verify the status of output 0/1:

show discrete outputs 0/1


Note: For details on the operation of the output relays for Remote RMC-700, see the

Remote RMC-700 Installation Guide.

Note: For additional related information, see the Remote RMC-700 Command

Reference Guide sections config discrete analog, config discrete output, and show discrete.

In this scenario, you will directly open and close a relay output.

(Dub)>show discrete outputs 0/1ID - 0/1Description -Resource State - unassignedValue - open(Dub)>

18-8

19

Configuring the SNMP Proxy

This chapter provides information about how to configure the Remote RMC-700 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

19-1

Remote RMC-700 Version 5.2x Configuration GuideConfiguring the SNMP Proxy: SNMP Proxy Feature Overview

SNMP Proxy Feature OverviewThe Remote RMC-700 SNMP Proxy feature allows for virtual network elements (NEs) to represent devices which are subtended from Remote RMC-700. Remote RMC-700 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 RMC-700.

The various states of the NEs are represented in Remote RMC-700’s 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 RMC-700.

Figure 19-1 shows the interaction of the mediation NEs (snmp ne1 and snmp ne2) inside Remote RMC-700 with the “real” SNMP NEs and the action and alarm table mediation subsystems.

Figure 19-1 Remote SNMP Proxy Configuration

19-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring the SNMP Proxy: SNMP Proxy Configuration Information

SNMP Proxy Configuration InformationAt 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 TemplatesThe 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 device’s 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 TemplateThe point template defines how a stateful item on the proxied device is managed by Remote RMC-700. 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 TemplateEvents are simple stateless mappings between an SNMP trap and a mediation event. Events are not mapped to the Remote RMC-700 alarm table. An event template consists, at a minimum, of a trap-oid and a message parameter.

NE TemplateThe 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 RMC-700s.

Measurement TemplateThe 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 TemplatesTemplate 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.

19-3

Remote RMC-700 Version 5.2x Configuration GuideConfiguring the SNMP Proxy: SNMP Proxy Configuration Information

The predefined variables that are available for use in these templates are described in Table 19-1.

SNMP NEThe 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 ManagerThe configurable information for the SNMP manager is the port on which the SNMP manager listens for incoming SNMP notifications. The default port is 162.

Table 19-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

19-4

Remote RMC-700 Version 5.2x Configuration GuideConfiguring the SNMP Proxy: Configuring a Mediation SNMP Event Template

Configuring a Mediation SNMP Event Template

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-template coldStartDef



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 RMC-700 Command Reference Guide for details on each parameter.

(Dub)>show mediation snmp event-template coldStartDefName: coldStartDefDescription: Reboot eventMessage: $(event) event on NE $(snmpne)Trap OID: .1.3.6.1.6.3.1.1.5.1(Dub)>

19-5

Remote RMC-700 Version 5.2x Configuration GuideConfiguring the SNMP Proxy: Configuring a Mediation SNMP Point Template

Configuring a Mediation SNMP Point Template

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

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

19-6


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

config mediation snmp event-template ifEntryDef state up poll-value 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 varbind-match .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 poll-value 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 trap-oid .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:

config mediation snmp point-template ifEntryDef state down varbind-match .1.3.6.1.2.1.2.2.1.1 $(ifIndex)

15. Configure the severity as major for the down state:

config mediation snmp point-template ifEntryDef state down severity major

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

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

19-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-template ifEntryDef



(Dub)>show mediation snmp point-template ifEntryDefName: ifEntryDefDescription: Entry in IfTablePoll OID: .1.3.6.1.2.1.2.2.1.8.$(ifIndex)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)>

19-8

Remote RMC-700 Version 5.2x Configuration GuideConfiguring the SNMP Proxy: Configuring a Mediation SNMP NE Template

Configuring a Mediation SNMP NE Template

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

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.

19-9

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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-template Template1



(Dub)>show mediation snmp(Dub) show mediation snmp>ne-templates Template1Name: Template1Description: Sample templateEvent: runningConfigChange Template: configChangeDef Parameter: file = running-configPoint: modem Template: ifEntryDef Parameter: ifDescr = serial_modemTemplate Reference: alarm1 Template: alarms Parameter: num = 1(Dub) show mediation snmp>

19-10

Remote RMC-700 Version 5.2x Configuration GuideConfiguring the SNMP Proxy: Configuring a Mediation SNMP Measurement Template

Configuring a Mediation SNMP Measurement Template

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

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

poll OID

which numeric value to consider significant if the response is a string

trap OID, varbind match and varbind value.

For the second template, you will configure the: template name alTableDef and description Measurement group

dynamic poll table

which numeric value to consider significant if the response is a string

trap OID, varbind ID and varbind value.

19-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:

config mediation snmp measurement-template alDef trap critical 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:

config mediation snmp measurement-template alDef trap critical 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:

config mediation snmp measurement-template alDef trap critical value-match 2


show mediation snmp measurement-template alDef



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

(Dub)>show mediation snmp measurement-templates alDefName: alDefDescription: Single measurementPoll OID: .1.3.6.1.4.1.539.42.2.2.1.5.$(alIndex)Value Match Index: 2Value Conversion Multiplier: 1Trap: 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 Value Match Index: 2 Varbind Match: .1.3.6.1.4.1.539.42.2.2.1.1 = $alIndex(Dub)>

19-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:

config mediation snmp measurement-template alTableDef trap 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:

config mediation snmp measurement-template alTableDef trap 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:

config mediation snmp measurement-template alTableDef trap critical value-match 2

19-13



show mediation snmp measurement-template alTableDef



(Dub)>show mediation snmp measurement-templates alTableDefName: alTableDefDescription: Measurement groupPoll Table OID: .1.3.6.1.4.1.539.42.2.2ID Column: 7Value Column: 5Value Match Index: 2Value Conversion Multiplier: 1Trap: 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 Value Match Index: 2 Varbind ID: .1.3.6.1.4.1.539.42.2.2.1.7(Dub)>

19-14

Remote RMC-700 Version 5.2x Configuration GuideConfiguring the SNMP Proxy: Configuring a Mediation SNMP Network Element

Configuring a Mediation SNMP Network Element

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

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.

19-15

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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 ProxyNEName: ProxyNEDescription:Host: 10.40.65.90:161SNMP Community: administratorSNMP Version: v1Category: NECategoryNE Name: ProxyNEMeasurement Poll Interval: 60Point Poll Interval: 3600Connectivity OID: .1.3.6.1.2.1.1.2.0Connectivity State: offlineLast Connectivity Poll Reply: unknownEvent: reboot Template: coldStartDef Last Trap: UnknownPoint: ethernet1 Template: ifEntryDef Current State: down Last Trap: Unknown Last Poll Reply: Unknown Parameter: ifIndex = 1Point: ethernet2 Template: ifEntryDef Current State: down Last Trap: Unknown Last Poll Reply: Unknown Parameter: ifIndex = 2Measurement: analog Template: alTableDef Last Poll Reply: unknown(Dub)>

19-16

Remote RMC-700 Version 5.2x Configuration GuideConfiguring the SNMP Proxy: Configuration Results

Configuration ResultsThe 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 exitconfig mediation snmp 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 exitconfig mediation snmp 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 varbind-match .1.3.6.1.2.1.2.2.1.1 $(ifIndex) exit 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) exit poll-default-state up exitconfig mediation snmp ne-template Template1 description Sample template event runningConfigChange configChangeDef file running-config point modem ifEntryDef ifDesc serial_modem ne-template alarm1 alarms num 1 exitconfig 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)>

19-17

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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-categoryconfig 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 category some-categoryconfig event ProxyNE_reboot_snmpne content snmpne ProxyNE trap rebootconfig response ProxyNE_trap_snmpne content snmp trap message $(message) ne-name ProxyNE category some-categoryconfig action ProxyNE_reboot_snmpne event ProxyNE_reboot_snmpne response ProxyNE_trap_snmpne

19-18

20

Configuring Jobs

This chapter includes scenarios that contain step-by-step procedures on how to configure jobs for Remote RMC-700.


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

20-1

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Jobs: Job Configuration Overview

Job Configuration OverviewA 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 RMC-700. Scripts are defined in packages and specify the parameters for execution when the associated jobs run. Figure 20-1 on page 20-3 illustrates how scripting operates in Remote RMC-700.

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-10 for details.

Script Package ComponentsBefore you configure a job on Remote RMC-700, you must first create a script package. A script package (.pkg file) contains two basic components:

Python modules

A package manifest file

Python ModulesA 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 RMC-700. A script can define job properties, which pass runtime parameters and/or settings (such as, connection information for a network element, baud rates, TID’s, phone numbers, software version and user name and password information) to Remote RMC-700 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. For example, a Python package named PkgA will be created when you create a directory named PkgA. This directory will store additional modules or subpackages. In order for Python to recognize the directory as a Python package, the directory needs to include a file named __init__.py. However, the file can be empty.

Package Manifest FileA 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.

20-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Jobs: Job Configuration Overview

Once a script package is created on a local workstation, you can use an FTP utility to transfer the script package either directly to the pkgstage directory on Remote RMC-700, 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 RMC-700.

When a script package is installed on Remote RMC-700, 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 RMC-700 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.

20-3

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Jobs: Configuring Access to a Central FTP Package Server

Configuring Access to a Central FTP Package ServerImportant: This procedure only applies 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 RMC-700.

To configure the central FTP package server:

1. At the main prompt, configure Remote RMC-700 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




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

(Dub)>show pkgs serverFTP server: enabledAddress: 11.8.77.3Port: 21User: testPassword: testDirectory: /packages/test(Dub)>

20-4

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Jobs: Installing a Script Package

Installing a Script PackageImportant: This procedure assumes that you have obtained a script package from

Westell (in this example, exampleScript-1.0.0.pkg).

To install a script package:

1. Using an SFTP utility, do one of the following:

Transfer exampleScript-1.0.0.pkg from the local workstation to the pkgstage directory on Remote RMC-700. Continue to step 7.

Transfer exampleScript-1.0.0.pkg to the central FTP package server default directory of /, which contains all script packages. Continue to step 8.

2. At the main CLI prompt, install script package exampleScript-1.0.0.pkg to Remote RMC-700:

config pkgs install name exampleScript

Continue to step 9.

3. At the main CLI prompt, install script package exampleScript-1.0.0.pkg to Remote RMC-700 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 8-1.

4. (optional) Verify that the script package has been installed properly:

show pkgs summary



Use an SFTP utility to transfer a script package to the Remote RMC-700 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 20-4.

Install the script package

(Dub)>show pkgs summaryPackage Versionexamplescript 1.0.0(Dub)>

20-5

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Jobs: Installing a Script Package

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:

Battery Monitor (including the Battery Learner)

Analog Monitor

20-6

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Jobs: Configuring a Job with a Script Package and Script

Configuring a Job with a Script Package and ScriptImportant: This procedure assumes that theuser has obtained a script package

from Westell (in this example, exampleScript-1.0.0.pkg) and the procedure Installing a Script Package on page 20-5 has been completed.

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



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).

(Dub)>show jobs name printlog statusJob: printlogPackage: examplescriptMin version: 1.0.0Script: capture_exampleCron start: disabledStart at boot: disabledMemory limit (Kb): 1024Output capture: disabledMax start attempts: 1Run state: idle(Dub)>

20-7

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Jobs: Configuring a Job with a Job Property

Configuring a Job with a Job PropertyImportant: This procedure assumes that theuser has obtained a script package

from Westell (in this example, exampleScript-1.0.0.pkg) and the procedure, Configuring a Job with a Script Package and Script on page 20-7 has been completed.

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 job’s data directory on Remote RMC-700.

3. (optional) Verify that the job has been configured with the proper job property:

show jobs name printlog properties



5. Run job printlog:

exec-job printlog run

A run ID is assigned.

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 job’s data directory when job capture is enabled.

(Dub)>show jobs name printlog propertiesName Valuecapture_text Hello World(Dub)>

20-8

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Jobs: Configuring a Job with a Job Property

6. (optional) Verify that the job has been executed successfully:

show jobs name printlog history


7. (optional) SFTP to Remote RMC-700 to verify that the output of the job has been recorded to the stdout.log and stderr.log files located in the job’s data directory (jobdata/printlog).

(Dub) show jobs name printlog>historyRun ID Start time End time Exit state 1 2010/02/03 22:35:32 2010/02/03 22:35:33 normal(Dub) show jobs name printlog>

20-9

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Jobs: Configuring a Job with a Job Task

Configuring a Job with a Job TaskImportant: This procedure assumes that the user has obtained a script package

from Westell (in this example, exampleScript-1.0.0.pkg) and the procedure, Installing a Script Package on page 20-5 has been completed.

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


6. Create task server_sock and assign the task type as serversocket:

config jobs name echodata task server_sock type serversocket

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.

(Dub)>show jobs name echodata task new_ipTask: new_ip Position: 1 Type: ifconfig Properties: Name Value address 192.168.0.215 controller br_switch(Dub)>

20-10

Remote RMC-700 Version 5.2x Configuration GuideConfiguring 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


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



13. Run job echodata:

exec-job echodata run

A run ID is assigned.

(Dub)>show jobs name echodata task server_sockTask: server_sock Position: 2 Type: serversocket Properties: Name Value address 10.40.57.50 ifconfig new_ip listen 5 port 50008 type STREAM(Dub)>

(Dub)>show jobs name echodata propertiesName Valueupper_case yes(Dub)>

20-11

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Jobs: Configuring Job Start Times

Configuring Job Start Times

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 *



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.

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

20-12

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Jobs: Configuring Dynamic Memory for a Job

Configuring Dynamic Memory for a Job

To configure dynamic memory for a job:

1. At the main prompt, configure Remote RMC-700 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



In this scenario, you will configure the amount of dynamic memory that Remote RMC-700 can use while running job printlog.

(Dub)>show jobs name printlog statusJob: printlogPackage:Min version: anyScript:Title:Cron start: disabledStart at boot: disabledMemory limit (Kb): 2024Stack size (Kb): 1024Output capture: enabledMax start attempts: 1Run state: idle(Dub)>

20-13

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Jobs: Configuring Dynamic Memory for a Job

20-14

21

Configuring Modules

This chapter includes scenarios that contain step-by-step procedures on how to configure modules for Remote RMC-700.


Module Configuration Overview

Configuring Modules Using Command Line Interface

Configuring Modules Using Web Interface

21-1

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Modules: Module Configuration Overview

Module Configuration OverviewA 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 module-defined NEs must be realized.

The web interface for module configuration provides an alternative to the command line interface. The web interface is used for initial site installation and small, individual site changes once the site is managed in Optima. Refer to Configuring Modules Using Command Line Interface on page 21-3 and Configuring Modules Using Web Interface on page 21-10.

21-2

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Modules: Configuring Modules Using Command Line Interface

Configuring Modules Using Command Line Interface

Installing Modules

To install a module:

1. Using an FTP/SFTP utility, transfer the SYSTEM-1.6.7.mod and TOWER-1.6.7.tgz module files from the local workstation to the modules directory on Remote RMC-700.

2. At the main CLI prompt, install all module files in the staging area:

exec site install


Note: In this example, TOWER-1.6.7.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


Tip: To display module applications and details, enter show site modules { modulename }


Use an FTP/SFTP utility to transfer the module to the Remote RMC-700 staging area

Install the module

Show the installed modules

(Dub)>exec site installThe modules System and Tower were installed successfully.(Dub)>

(Dub)>show site modulesModule Version Description Date------------------------------------------------------------------------------System 1.6.7 System 2013.07.11 18:54:03Tower 1.6.7 Tower Management Applicat 2013.07.11 18:55:28TowerTenants 1.6.7 Tower Management Live Vie 2013.07.11 18:55:28

21-3


Enabling an Optional Application

1. Display the applications and details from the module Tower:

show site modules Tower


2. Enable the Environmental Monitoring application from the Tower module:

config site module Tower application EnvironmentalMonitoring enable

3. Confirm that the Environmental Monitoring application has been enabled:

show site modules Tower


Display applications available in an installed module. Enable an application in the Tower module.

>show site modules TowerName - TowerDisplay Name -Description - Tower Management Applications, Reports, and Live ViewProduct Version - 1.6.7Compatibility Version - 1.0.7Build ID - 007Build Date - 2013.07.11 18:55:28.830 -0400

Application Type State Description------------------------------------------------------------------------------ACPowerMonitoring optional disabled An application for monitoring AC PoAccessManagement optional disabled An application for site access manaAssetTampering optional disabled An application that monitors assetBatteryMonitoring optional disabled An application for monitoring batteCabinetMonitoring optional disabled Application for monitoring the cabiDASMonitoring optional disabled An application for monitoring distrDCPowerMonitoring optional disabled An application for monitoring DC PoEnvironmentalMonitor optional disabled Application for monitoring the enviFuelMonitoring optional disabled An application for monitoring fuelGeneratorManagement optional disabled An application for monitoring generHVACControl optional disabled Application that allows for HVAC coHVACEnergyMonitoring optional disabled Application that monitors HVAC enerHVACMonitoring optional disabled Application that allows for HVAC moRectifierMonitoring optional disabled An application for monitoring the rSurveillance optional disabled An application for surveillanceTenantDCMetering optional disabled An application for tenant meteringTenantMetering optional disabled An application for monitoring energTowerLightMonitoring optional disabled An application for monitoring towerUPSMonitoring optional disabled An application for monitoring UPSs

21-4


The command line response “State” column shall display that Environmental Monitoring has been enabled.

4. Applications can be disabled by using the above command with “disable” instead of “enable.”

Realizing and Configuring Network Elements

To realize and configure NEs:

1. Select type SiteBusTemperature for Network Element indoorTemperature:

config site network-element indoorTemperature type SiteBusTemperature

2. In this example, a SiteBusTemperature sensor has already been installed.. To customize the module with this data, set the value of parameter ID to 28004565AE05A5:

config site network-element indoorTemperature param ID 28004565AE05A5

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


Realize the indoorTemperature Network Element (NE) and configure several parameter valuesShow the NEs

21-5


4. Verify that the network elements are in the ‘online’ state:

show site network-elements


5. (optional) Display the details of the NE that includes the list of parameters:

show site network-elements indoorTemperature


(Dub)>show site network-elementsNetwork Element Category Type State------------------------------------------------------------------------------backhaulSender BackhaulSender offlineindoorhumidityzzzz HumiditySensor offlineindoorTemperature TemperatureSensor SiteBusTemperaturezzzzzz onlinemonitor ModuleMonitor offlineoutdoorHumidity HumiditySensor offlineoutdoorTemperatur TemperatureSensor offlinesmokeDetector SmokeDetector offline

(Dub)>show site network-elements indoorTemperatureName - indoorTemperatureDescription - Main indoor temperature sensorCategory - TemperatureSensorType - RMBTemperatureState - onlineInternalState - Online

Parameters------------------------------------------------------------------------------Name - REF_temperatureUnitsValue - FType - referenceDescription - Referenced from temperatureUnits. Per-NE configuration of unitsis not supported.

Name - highTemperatureValue - 100 (configured)Type - referenceDescription - High Temperature Alarming Point

Name - lowTemperatureValue - 50Type - referenceDescription - Low Temperature Alarming Point

Name - peripheralNumberValue - 2 (configured)Type - integer (1 - 12)Description - Peripheral number for RMB

21-6


Configuring an NE Set

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). To view the name format, execute the command show site network-elements-sets <NE Set>. The “Name Restriction” field shows the format.

2. Configure description This is Tenant1Power. for NE (instance) Tenant1Power in NE set TenantPowerMeter:

config site network-element-set TenantPowerMeter instance Tenant1Power description This is Tenant1Power.

3. Configure display name Tenant1PowerMeter for NE (instance) Tenant1Power in NE set TenantPowerMeter:

config site network-element-set TenantPowerMeter instance 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:

config site network-element-set TenantPowerMeter instance Tenant2Power

5. Configure description This is Tenant2Power. for NE (instance) Tenant2Power in NE set TenantPowerMeter:


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).

21-7


config site network-element-set TenantPowerMeter instance Tenant2Power description This is Tenant2Power.

6. Configure display name Tenant2PowerMeter for NE (instance) Tenant2Power in NE set TenantPowerMeter:

config site network-element-set TenantPowerMeter instance Tenant2Power display-name Tenant2PowerMeter

7. (optional) Verify that the NE set has been configured properly:

show site network-elements-sets TenantPowerMeter


8. Realize NE (instance) Tenant1Power and Tenant2Power using scenario Realizing and Configuring Network Elements on page 21-14.


Initiating a Control Action

Note: In this example, the fan network element provides the fan-controller

control. Controls will automatically go to the “online” state once the host

(Dub)>show site network-elements-sets TenantPowerMeterName - TenantPowerMeterDescription - NE Set for TenantPowerMeterCategory - PowerMeterCategoryMax Elements - 3Name Restriction - (.*Power)

Instances------------------------------------------------------------------------------Name - Tenant1PowerDescription - This is Tenant1Power.Display Name - Tenant1PowerMeterActivity State - Active

Name - Tenant2PowerDescription - This is Tenant2Power.Display Name - Tenant2PowerMeterActivity State - Active

(Dub)>


Initiate the control action to turn on the ventilation fan

Show the state of the controls

21-8


network element is “online” and all the control’s 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


Tip: To display the details for control fan-controller, enter show site controls fan-controller

(Dub)>show site controls

Control Category State Admin------------------------------------------------------------------------------fan-controller VentilationFan Running enabled

21-9

Remote RMC-700 Version 5.2x Configuration GuideConfiguring Modules: Configuring Modules Using Web Interface

Configuring Modules Using Web Interface

Installing Modules

To install a module:

1. Using an SFTP utility, transfer the TOWER-x.x.x.tgz module file from the local workstation to the modules directory on Remote RMC-700.

Note: Users might have different modules than the ones in this example

Note: The file name TOWER_x.x.x.tgz generically denotes the version; the actual

file version will be numbered

2. Using a browser, access the web interface and enter a valid usename and password on the login page. From the main menu or from the navigation menu on the left side of the screen, select the Modules link. The module home page will be displayed See Figure 21-1.

In this scenario, you will: Use an SFTP utility to transfer the module to the Remote RMC-700 staging

area

Log into the web interface and navigate to the modules home page

Install the module

View the list of installed modules

Enable an optional application

21-10


Figure 21-1 The screen displays RMC-700 Web Interface Modules Home page

3. From Modules Home page, click the Modules icon. The Modules page will be displayed. See Figure 21-2.

Figure 21-2 The screen displays available modules, here in a magnified view

21-11


4. The available modules list will show the SYSTEM and TOWER-1.6.7.tgz modules that were transferred to the staging area. Click on Install All Modules.

5. A list of installed modules will appear in the upper panel as shown in Figure 21-3.

Figure 21-3 The screen displays installed modules

6. Use the breadcrumbs trail to return to the Modules Home page.

7. Select the Applications icon. The Applications page will be displayed as shown in Figure 21-4.

21-12


Figure 21-4 The Applications page shows all applications and their state.

8. Click the checkmark box for EnvironmentalMonitoring in the “Enabled” column and click “Save” to enable the application. The checkmark will remain and the state will change to Enabled as shown in Figure 21-5.

21-13


Figure 21-5 The Applications page shows EnvironmentalMonitoring enabled.

Realizing and Configuring Network Elements

1. Use the breadcrumbs trail to return to the Modules Home page.

2. Select the Network Elements icon and expand the Temperature Sensor category (see Figure 21-6).

Important: Network Elements such as Temperature Sensor and Humidity Sensor will not appear by default. Follow Steps 6, 7 and 8 in the Installing Modules instructions and use the Applications page shown in Figure 21-4 to enable Network Elements. The Temperature Sensor and Humidity Sensor NEs are part of the EnvironmentalMonitoring application.

In this scenario, you will: Realize the indoorTemperature Network Element (NE) and configure

several parameter values

Realize the indoorHumidity NE and configure a parameter value

View the list of NEs

21-14


Figure 21-6 Screen display of Network Elements with the Temperature Sensor category expanded to show its component NEs.

3. Move the cursor into the Display column, highlight “indoorTemperature” and click on it. The screen will display details of this NE. See Figure 21-7.

Figure 21-7 Initial screen display of the indoorTemperature NE

21-15


4. Select RMB Temperature from the Type pull-down menu and click the Save button at lower right. The parameters of this NE will display as shown in Figure 21-8.

Figure 21-8 The display of parameters of indoorTemperature type RMB Temperature

5. Click on peripheralNumber to highlight that line, and then click on the value column in that line to open the value edit window. Set the value at 2, click outside the edit window (See Note on Page 21-16), and click Save. After the user saves this change, the screen should appear as shown in Figure 21-9.

Note: On this and other screens in this web interface, small red triangles appear in

affected cells to mark pending settings changes which the user has made. A triangle appears each time the user changes a setting and then clicks the cursor outside that cell. The Save button will save these changes. The Discard button will discard changes. A popup window prompts the user to confirm a Discard.

21-16


Figure 21-9 The screen display of parameters from Indoor Temperature Sensor type RMB Temperature after the peripheralNumber value was changed to 2 in Step 5.

6. Using the same methods described in step 5, click on highTemperature, set the value at 100, and click Save.

7. Using the same methods described in step 5, click on lowTemperature, set the value at 60, and click Save.

8. Use the breadcrumbs trail to return to the Network Elements page.

9. Expand HumiditySensor, highlight indoorHumidity in the display column, and click on it to display details of this NE.

10. Using the same methods described in step 5, select RMBHumidity, set the peripheralNumber value at 2, and Save.

Configuring an NE Set

1. On the Modules Home page, click the Network Element Sets icon. The list of Network Element Sets will appear.


Configure two NEs (instances) in a network element set.

Configure a display name and description for each NE (instance).

21-17


2. Expand TenantPowerMeter and click the Add button below the display column. The box “Add NE” will appear.Type Tenant1Power in the Name box. See Figure 21-10.

Figure 21-10 The Add NE window prompts the user for a name, display, and description of the NE being added.

Note: The name must conform to the pattern specified below the name box.

When this is shown as *Power, the name must end with the word “Power.” See Figure 21-10.

3. Type “Tenant 1 Power Meter” in the Display box and “This is Tenant 1 Power” in the Description box. See Figure 21-10. Click Ok.

4. Click Add. The Add NE box will appear.

5. Type “Tenant2Power” in the name box, “Tenant 2 Power Meter” in the Display box, and “This is Tenant 2 Power” in the Description box. Click Ok.

6. Click Save.

7. Realize the added NEs using the steps specified in Realizing and Configuring Network Elements on page 21-14.

21-18

22-1

22

Configuring SiteBus Devices

This chapter provides information on configuringSiteBus devices for Remote RMC-700.


Configuring SiteBus Devices

Remote RMC-700 Version 5.2x Configuration GuideConfiguring SiteBus Devices: Configuring SiteBus Devices

Configuring SiteBus DevicesRemote RMC-700 includes a SiteBus, port that will accommodate up to 12 one-wire devices. Each of these one-wire SiteBus devices has a unique hexadecimal ID. Oncea SiteBus device has been connected and the device has been discovered, you can configure the device for management by Remote RMC-700.

To configure a SiteBus device:

1. Connect one or more DS18B20 1-wire digital thermometer(s) to Remote RMC-700’s SiteBus port using an RJ45 ethernet cable.

Note:

2. Remote RMC-700 discovers the newly connected SiteBus device(s).

3. Obtain the hexadecimal ID for the newly connected SiteBus device:

show sitebus

In the following example, device 004564AE05A528 has been discovered, but is not yet managed by Remote RMC-700.

4. 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.

5. Configure device temp1 with hexadecimal ID 28004564AE05A5:

config sitebus temp1 id 28004564AE05A5


Connect a device to a SiteBus terminal and discover its hexadecimal ID

Configure a SiteBus device for management by Remote RMC-700

(Dub)>show(Dub) show>sitebus

ID Periph:Bus State Managed Name------------------------------------------------------------------------------004564AE05A528 0:1 Unmanaged

Name ID State Type Description-----------------------------------------------------------------------------(Dub) show>

22-2


6. 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 SiteBus device type supported for Remote RMC-700 version 5.2x 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.

7. Add description Temperature Sensor 1 to device temp1:

config sitebus temp1 description Temperature Sensor 1

8. (optional) Verify that the SiteBus device has been configured properly:

show sitebus

The display will look similar to the following:


For information on configuring a measurement-table entry for a SiteBus device, see section Configuring a Measurement Table Entry for a Temperature Sensor and subsection Sample Configuration for SiteBus Temperature Sensor.

(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>

22-3


22-4

23

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

23-1

Remote RMC-700 Version 5.2x Configuration GuideUsing Configuration Wizards: Configuration Wizard Overview

Configuration Wizard OverviewA 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 RMC-700:

A setup wizard for initial connectivity configuration on an unconfigured Remote RMC-700

A wizard for common serial port setups

A wizard that configures alarm table entries for bi-state points.

23-2

Remote RMC-700 Version 5.2x Configuration GuideUsing Configuration Wizards: Using the initsetup Wizard

Using the initsetup Wizard

To configure the initial setup:

1. From the main prompt, access the initsetup wizard:

config use-wizard initsetup

The initsetup wizard screen displays:

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.

In this scenario, you will configure the initial setup for Remote RMC-700 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.

(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 additionalconfiguration options, consult the command reference guide.

Hostname of this device:

23-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. If a wireless modem is installed, you will be prompted whether to configure the WAN connection. The following settings are configurable and are for wireless modem cards only:

Wireless service provider

Access point name

PPP authentication method

Remote server if used as default route

7. Enter the desired default route when prompted.

8. (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

9. (optional) Enter the desired clock settings when prompted. The following settings are configurable:

The standard timezone

Daylight savings time

The current time and date

10. (optional) Enter the desired NTP settings when prompted. The wizard asks you for the primary and secondary server IP addresses.

23-4


11. (optional) Enter the desired SNMP v3 user settings when prompted. The following settings are configurable:

User name

Authentication protocol

Authentication pass phrase

Privacy protocol

Privacy passphrase

Select (y/N) whether to add another user

12. (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.

13. (optional) Enter the desired SNMP manager information when prompted. The following settings are configurable:

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

14. (optional) Enter the application package server information when prompted. The following settings are configurable:

An IP address

A package directory on the server

An FTP username and password

15. 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.

23-5

Remote RMC-700 Version 5.2x Configuration GuideUsing Configuration Wizards: Using the bistate-alarms Wizard

Using the bistate-alarms Wizard

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 displays:

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 - 12)

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.

In this scenario, you will configure a bistate point on Remote RMC-700 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.

(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. For additional configurationoptions, consult the command reference guide.

Enter number of the unit containing point(s) to configure. Use 0 or blank forthe base unit. Use 1-12 for a peripheral unit.Enter unit number (leave blank for base unit):

23-6

Remote RMC-700 Version 5.2x Configuration GuideUsing 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 bi-state 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


23-7

Remote RMC-700 Version 5.2x Configuration GuideUsing Configuration Wizards: Using the serial-port Wizard

Using the serial-port Wizard

To configure a Remote RMC-700 serial port:

1. From the main prompt, access the serial-port wizard:

config use-wizard serial-port

The serial port wizard screen displays:

2. Enter the desired port number.

The wizard states which port is currently selected and lists options for:

Choosing a different port (1 - 2)

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.

In this scenario, you will configure an Remote RMC-700 serial port with the serial-port wizard.

(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 additionalconfiguration options, consult the command reference guide.

Enter number of the unit containing the port(s) to configure. Use 0 or blankfor 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-2) (c) configure this port (d) doneChoose option (leave blank to skip this port):

23-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, TBOS, 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.


23-9


23-10

24

Remote RMC-700 TL1 Commands

This chapter lists the default TL1 commands that are supported by Remote RMC-700’s Virtual Network Elements (VNEs).


Overview

Default TL1 VNE Commands

Unsupported TL1 Commands

24-1

Remote RMC-700 Version 5.2x Configuration GuideRemote RMC-700 TL1 Commands: Overview

OverviewThis chapter discusses the following topics:

The default Remote RMC-700 TL1 command set

Recognizing the failure messages associated with TL1 commands that aren’t supported by Remote RMC-700.

You should be familiar with Remote RMC-700 actions and TL1 on Remote RMC-700 before reading this chapter. For more information on these topics, refer to Chapter 10: Configuring Actions, Events and Responses and Chapter 16: Configuring and Connecting TL1 Infrastructure.

24-2

Remote RMC-700 Version 5.2x Configuration GuideRemote RMC-700 TL1 Commands: Default TL1 VNE Commands

Default TL1 VNE CommandsThe default TL1 commands supported by Remote RMC-700 are a small subset of all available TL1 commands. The following default commands are supported:

ACT-USER

ALW-MSG-ALL

CANC-USER

RTRV-ALM-ALL

RTRV-ALM-DS3

RTRV-ALM-EC1

RTRV-ALM-ENV

RTRV-ALM-EQPT

RTRV-ALM-OC3

RTRV-ALM-T1

RTRV-HDR

ACT-USER

DescriptionThis command lets a remote user log into the VNE on Remote RMC-700.

FormatACT-USER:tid:user:ctag::password;

Parameters

tid Defines the target identifier for a VNE on Remote RMC-700.

user Defines the user name for a VNE on Remote RMC-700.

ctag Defines the correlation tag used to correlate responses to commands. Each command has a unique correlation tag. A response includes the identical correlation tag to the one used for the corresponding command.

password Defines the user password for a VNE on Remote RMC-700.

24-3


ExamplesThis example displays a normal response when command ACT-USER:Remote:ai:1::ai; is entered.

ALW-MSG-ALL

DescriptionThis command causes Remote RMC-700 to resume transmission of automatic messages after being in the inhibit message mode.

Note: Remote RMC-700 does not currently support the inhibit message TL1

command. Because of this, Remote RMC-700 is always in ALW-MSG-ALL mode.

FormatALW-MSG-ALL:tid:[ aid ]:ctag;

Parameters

ExamplesThis example displays a normal response when command ALW-MSG-ALL:Remote:AID:1; is entered.

Remote RMC 09-01-24 16:58:44M 1 COMPLD /* 1 User(s) Logged On */;


aid Defines the user name for a VNE on Remote RMC-700.

ctag

Defines the correlation tag used to correlate responses to commands. Each command has a unique correlation tag. A response includes the identical correlation tag to the one used for the corresponding command.

Remote RMC 09-01-24 17:47:44M 1 COMPLD /* ALW-MSG-ALL:Remote:AID:1 */;

24-4


CANC-USER

DescriptionThis command lets the connected user log out of the VNE on Remote RMC-700.

FormatCANC-USER:tid:aid:ctag;

Parameters

ExamplesThis example displays a normal response when command CANC-USER:Remote:ai:1; is entered.

RTRV-ALM-ALL

DescriptionThis command causes Remote RMC-700 to return all alarms.

FormatRTRV-ALM-ALL:tid:[ aid ]:ctag::;




Remote RMC 09-01-25 10:07:18M 1 COMPLD /* CANC-USER:Remote:ai:1 */ /* Your session has been disconnected. */;

24-5


Parameters

ExamplesThis example displays a normal response when command RTRV-ALM-ALL:Remote::1::; is entered.

RTRV-ALM-DS3

DescriptionThis command causes Remote RMC-700 to return all alarms designated with the DS3 modifier during Remote RMC-700 configuration. Points associated with class DS3, which transmits digital signals at 44.736 Mbps over a T-3 facility, are generally programmed with this modifier.

FormatRTRV-ALM-DS3:tid:[ aid ]:ctag::;

Parameters



ctag Defines the correlation tag used to correlate responses to input commands. Each input command has a unique correlation tag. A response includes the identical correlation tag to the one used for the corresponding input command.

Remote RMC 09-01-27 14:00:02M 1 COMPLD /* RTRV-ALM-ALL:Remote::1:: */ "INPUT0_19,ENV:CR,MISC,NSA,09-27,09-48-45,,,:\"INPUT 0/19 CLOSE\",:,";




24-6


ExamplesThis example displays a normal response when command RTRV-ALM-DS3:Remote::1::; is entered.

RTRV-ALM-EC1

DescriptionThis command causes Remote RMC-700 to return all alarms designated with the EC1 modifier during Remote RMC-700 configuration. Points associated with class EC1, which is a facility with electrical levels at 51.84 Mbps, are generally programmed with this modifier.

FormatRTRV-ALM-EC1:tid:[ aid ]:ctag::;

Parameters

ExamplesThis example displays a normal response when command RTRV-ALM-EC1:Remote::1::; is entered.

Remote RMC 09-01-18 12:46:19M 1 COMPLD /* RTRV-ALM-DS3:Remote::1:: */ "INPUT0_1,DS3:CR,MISC,NSA,09-18,12-36-34,,,:\"INPUT 0/1 CLOSE\",:,";




Remote RMC 09-01-18 13:08:18M 1 COMPLD /* RTRV-ALM-EC1:Remote::1:: */ "INPUT0_2,EC1:CR,MISC,NSA,09-18,13-07-17,,,:\"INPUT 0/2 CLOSE\",:,";

24-7


RTRV-ALM-ENV

DescriptionThis command causes Remote RMC-700 to return all alarms for points designated with environment modifiers during Remote RMC-700 configuration. Points associated with environmental alarms, such as high temperature, are generally programmed with this modifier.

FormatRTRV-ALM-ENV:tid:[ aid ]::ctag;

Parameters

ExamplesThis example displays a normal response when command RTRV-ALM-ENV:Remote::1; is entered.

RTRV-ALM-EQPT

DescriptionThis command causes Remote RMC-700 to return all alarms for points designated with equipment modifiers during Remote RMC-700 configuration. Points associated with equipment alarms, such as link down, are generally programmed with this modifier.

FormatRTRV-ALM-EQPT:tid:[ aid ]::ctag;




Remote RMC 09-01-25 12:19:02M 1 COMPLD /* RTRV-ALM-ENV:Remote::1 */ "INPUT0_19:CR,MISC,09-27,09-48-45,\"INPUT 0/19 CLOSE\"";

24-8


Parameters

ExamplesThis example displays a normal response when command RTRV-ALM-EQPT:Remote::1; is entered.

RTRV-ALM-OC3

DescriptionThis command causes Remote RMC-700 to return all alarms designated with the OC3 modifier during Remote RMC-700 configuration. Points associated with class OC3, which is an optical fiber line that carries 155mbps, are generally programmed with this modifier.

FormatRTRV-ALM-OC3:tid:[ aid ]::ctag;

Parameters




Remote RMC 09-01-18 13:27:36M 1 COMPLD /* RTRV-ALM-EQPT:Remote::1:: */ "INPUT0_4,EQPT:CR,MISC,NSA,09-18,13-27-06,,,:\"INPUT 0/4 CLOSE\",:,";




24-9


ExamplesThis example displays a normal response when command RTRV-ALM-OC3:Remote::1; is entered.

RTRV-ALM-T1

DescriptionThis command causes Remote RMC-700 to return all alarms designated with the T1 modifier during Remote RMC-700 configuration. Points associated with class T1, which is a digital transmission link with a capacity of 1.544 Mbps, are generally programmed with this modifier.

FormatRTRV-ALM-T1:tid:[ aid ]::ctag;

Parameters

ExamplesThis example displays a normal response when command RTRV-ALM-T1:Remote::1; is entered.

Remote RMC 09-01-18 13:16:00M 1 COMPLD /* RTRV-ALM-OC3:Remote::1:: */ "INPUT0_3,OC3:CR,MISC,NSA,09-18,13-15-29,,,:\"INPUT 0/3 CLOSE\",:,";




Remote RMC 09-01-18 13:30:34M 1 COMPLD /* RTRV-ALM-T1:Remote::1:: */ "INPUT0_5,T1:CR,MISC,NSA,09-18,13-30-14,,,:\"INPUT 0/5 CLOSE\",:,";

24-10


RTRV-HDR

DescriptionThis command causes Remote RMC-700 to send its TL1 System Identifier (SID) header to the OSS. The SID is used primarily to check the status of the communications link.

FormatRTRV-HDR:tid::ctag;

Parameters

ExamplesThis example displays a normal response when command RTRV-HDR:Remote::1; is entered.



IP 1<

Remote RMC 09-01-25 15:18:17M 1 COMPLD /* RTRV-HDR:Remote::1 */;

24-11

Remote RMC-700 Version 5.2x Configuration GuideRemote RMC-700 TL1 Commands: Unsupported TL1 Commands

Unsupported TL1 CommandsRemote RMC-700 TL1 VNE’s only take action when default or configured TL1 commands are entered. A failure message occurs when an invalid command is entered, which causes Remote RMC-700 to give a deny response. Responses include a ctag that is identical to the invalid command.

ExampleThis example displays the failure message that occurs when unsupported command REPT-ALM-ENV:Remote:ALL:1; is entered.

Remote RMC 09-01-26 12:01:37M 1 DENY ICNV /* Input, Command Not Valid */ /* The command code entered is not a valid command code. */;

24-12

A

Backing Up and Restoring the Remote RMC-700 Configuration

This appendix provides step-by-step scenarios on how to back up and restore the Remote RMC-700 configuration.

Guide to this Appendix

Backing Up the Configuration

Restoring the Configuration

A-1

Remote RMC-700 Version 5.2x Configuration GuideBacking Up and Restoring the Remote RMC-700 Configuration: Backing Up the Configuration

Backing Up the Configuration

Important: There are two configuration files. The startup configuration file (primary.cnf) is the configuration used to start Remote RMC-700. The running configuration file (running-config) includes configuration changes that have been made since startup.

To back up the configuration:

1. Using an SFTP utility, connect to and log into Remote RMC-700.

2. Change the current directory to the config directory on Remote RMC-700.

3. Locate the Remote RMC-700 configuration file (primary.cnf or running-config) in the config directory.

4. Using ASCII mode, get the configuration file from the config directory on Remote RMC-700. The configuration file is copied to the working directory on your workstation.

Note: The running-config file is an ASCII file—it should only be transferred with

an ASCII mode SFTP.

5. Close the SFTP connection to Remote RMC-700 and exit the SFTP utility.

In this scenario, you will back up the Remote RMC-700 configuration file.

A-2

Remote RMC-700 Version 5.2x Configuration GuideBacking Up and Restoring the Remote RMC-700 Configuration: Restoring the Configuration

Restoring the Configuration

Important: There are two configuration files. The startup configuration file (primary.cnf) is the configuration used to start Remote RMC-700. The running configuration file (running-config) includes configuration changes that have been made since startup.

To restore the configuration:

1. Using an SFTP utility, connect to and log into Remote RMC-700.

2. Change the local current directory to the working directory on your workstation.

3. Locate the Remote RMC-700 configuration file (primary.cnf or running-config) file in the working directory.

4. Change from the current directory to the config directory on Remote RMC-700.

5. Using ASCII mode, put the configuration file in the config directory.

Note: The running-config file is an ASCII file—it should only be transferred with

an ASCII mode SFTP.

6. Close the SFTP connection to Remote RMC-700 and exit the SFTP utility.

Note: Changes to the startup configuration file (primary.cnf) will not take effect

until Remote RMC-700 is rebooted or command copy startup-config running-config is entered.

In this scenario, you will restore the Remote RMC-700 configuration file.

Note: You must have supervisor permissions to completely restore the Remote

RMC-700 configuration. Users with management permission can restore the configuration; however, user information will not be modified.

A-3

Remote RMC-700 Version 5.2x Configuration GuideBacking Up and Restoring the Remote RMC-700 Configuration: Restoring the Configuration

A-4

B

Command IdentificationsCommand 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 table contains some of the valid command identifications for the Remote RMC-700:

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

B-1

Remote RMC-700 Version 5.2x Configuration GuideCommand Identifications:

config controller ethernethardware-address

/config/controller/eth/hwaddr

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 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 Identifications (Continued)

B-2


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 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

config snmp /config/snmp


B-3


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/status-points

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 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

debug serial /debug/serial/

diag /diag


B-4


diag break /diag/break

diag clear /diag/clear

diag controller /diag/controller

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 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

exit /exit

halt /halt

help /help

password /password


B-5


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

show inventory /show/inventory

show ip /show/ip

show iptables /show/iptables

show jobs /show/jobs


B-6


show licenses /show/licenses

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

show site network-elements-sets /show/site/network-elements-sets

show site network-elementsstatus points

/show/site/network-elements/status-points

show site params /show/site/params

show snmp /show/snmp

show test /show/test

show timeout /show/timeout


B-7


show users /show/users

show version /show/version

ssh /ssh

trace-route /trace-route


B-8

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 RMC-700.

AID

AID is an acronym for access-identifier. It identifies the NE system component to which the TL1 alarm applies.

alarm affect

The alarm affect designates a TL1 alarm as service-affecting or non-service-affecting.

Glossary-1

Glossary

alarm class

An alarm class is a designation of a TL1 alarm as environmental or equipment-related. TL1 alarms designated as environmental signal the occurrence of events such as temperature or pressure changes. TL1 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 a TL1 alarm when a specified environmental event occurs.

alarm type

The alarm type is the value for TL1 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 RMC-700.

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 both of the Ethernet switch ports. Controller bridge switch can be configured to include or exclude Ethernet 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 RMC-700. It can be configured to communicate alarm state changes in a variety of management protocols.

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 RMC-700. The

Glossary-4

Glossary

user must SFTP the chat file to the /config/chat directory on Remote RMC-700 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 RMC-700 session expires due to inactivity.

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 a TL1 alarm type that is based on standards listed in the Bellcore GR-833-CORE documentation.

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 RMC-700 asynchronous serial controller. Depending on the connection settings, this string may or may not be sent to the attached device.

Glossary-5

Glossary

controller

A controller is a concept that is applied throughout the CLI. It is a software object on Remote RMC-700 that sends and receives a stream of bytes. A controller can be a physical device, such as an Ethernet transceiver, or it can be a virtual entity such as OpenVPN client.

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.

D

data bits

Data bits are the number of bits per character transmitted or received by an asynchronous serial controller.

daylight savings

Daylight saving time is when clocks are set ahead one hour to provide an extra hour of daylight during summer. In the U.S., daylight saving time presently starts on the second Sunday in March and ends on the first Sunday in November. Daylight saving time start and end dates vary in some other countries, and some countries do not use daylight saving time.

default lease time

Glossary-6

Glossary

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.

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

Glossary-7

Glossary

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 technician’s 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 RMC-700 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.

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 RMC-700’s configuration. These additional I/O points are managed through Remote RMC-700.

discrete peripheral unit

The discrete peripheral unit is a space on Remote RMC-700 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

Glossary-8

Glossary

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 RMC-700 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 RMC-700 are HDLC and PPP.

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.

Glossary-9

Glossary

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.

forward delay

Forward delay defines the amount of time a controller participating in a bridge group that is running the spanning tree protocol (STP) spends in the listening state before entering the learning state, the amount of time a controller spends in the learning state before entering the forwarding state, and the aging time for dynamic entries in the filtering database during a network topology change.

framing

Framing is an error control procedure with multiplexed digital channels, where bits are inserted so that the receiver can identify the timeslots that are allocated to each subchannel. Refer to the Remote RMC-700 Command Reference Guide for information on the framing formats Remote RMC-700 utilizes.

FTP

FTP (File Transfer Protocol) is a communications protocol that governs the transfer of files from one computer to another over a network.

Glossary-11

Glossary

G

gateway address

The gateway address is the IP address of the next node location in a route.

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.

Glossary-12

/wiki/Mobile_telephony

/wiki/Mobile_telephony

/wiki/UMTS

/wiki/UMTS

Glossary

HTTPS

HTTPS (Hyper Text Transfer Protocol Secure) provides the necessary security to protect sensitive data. On Remote RMC-700, HTTPS is implemented by incorporating an SSL layer that encrypts the HTTP packets between the web server and client/browser.

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 lcp-requests (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.

Glossary-13

Glossary

Iptables

Iptables is the method by which IP packets are filtered or manipulated for Remote RMC-700. 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.

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 RMC-700.

job property

A job property is a runtime parameter for a job on Remote RMC-700. 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 RMC-700.

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.

Glossary-14

Glossary

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.

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.

Glossary-15

Glossary

local fallback

Local fallback indicates local user authentication will be used when attempts to contact the primary and secondary RAS servers fail.

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.

local method

The local method specifies the protocol Remote RMC-700 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 controller’s MAC address table.

Glossary-16

Glossary

MAC address table

A MAC address table is a list containing the MAC addresses of all the devices that are permitted access to Remote RMC-700 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).

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.

Glossary-17

Glossary

MTU

The MTU sets the maximum number of data bytes that can be transmitted in a single PPP frame on a WAN port.

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.

Glossary-18

Glossary

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.

notification code

The notification code provides an indication of the severity of a TL1 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 RMC-700, 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.

Glossary-19

Glossary

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 customer’s external firewall needs to open one UDP port for all connected client network elements.

originator

An originator is a physical and visible component within Remote RMC-700 that generates the event, such as an analog input or digital input, serial controller, TL1 multiplexer, or an Ethernet controller.

output signal

There are two types of output signals on Remote RMC-700 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.

Glossary-20

Glossary

peripheral device

A peripheral device is a system component that expands Remote RMC-700’s functionality. The only peripheral device currently available for Remote RMC-700 is the discrete expansion peripheral, which adds additional I/O points that are controlled by Remote RMC-700.

peripheral management subsystem

The peripheral management subsystem is the subsystem that lets Remote RMC-700 manage up to 12 discrete expansion peripherals at remote locations.

PID

A PID is the TL1 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.

Glossary-21

Glossary

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.

privilege level

The privilege level is configured for a user-defined profile when RAS mode authorization is set to priv-lvl. The RAS server returns a privilege level to Remote RMC-700 and matches it up with the correct profile.

profile

A profile gives a user designated permissions for operating commands in Remote RMC-700. 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

RADIUS

RADIUS authenticates a user and authorizes a profile from a remote location.

RAS accounting

RAS accounting is the method for tracking user logins and command entry when Remote RMC-700 is configured for TACACS+ remote authentication. An accounting start packet or stop packet is issued each time a user logs into or out of Remote RMC-700. An accounting start packet is also issued for each command that is entered.

Glossary-22

Glossary

RAS authorization

RAS authorization is the method by which Remote RMC-700 grants command access when TACACS+ remote authentication is configured. Access can be granted based on command level or privilege level. Command level authorization requires Remote RMC-700 to contact the TACACS+ server for each command the user runs. Individual commands are then allowed or denied. Privilege level authorization configures the TACACS+ authorization method based on the privilege returned from the TACACS+ server.

RAS server

A RAS server is a device that provides user authentication and provisioning for access into the network using RADIUS software or the TACACS+ protocol.

RAS timeout

The RAS timeout is the amount of time that the device waits for a response from the RAS servers before falling back on local authentication.

raw alarm output

Raw alarm output is an Remote RMC-700 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 RMC-700. 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.

Glossary-23

Glossary

remote authentication

Remote authentication is the method by which users are granted access to Remote RMC-700 through a remote server. Available remote authentication methods are RADIUS and TACACS+.

remote identity

The remote identity is supplied by a remote device and sent to the local device.

remote method

The remote method specifies the protocol a peer device uses to authenticate Remote RMC-700 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 RMC-700, 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 RMC-700.

response type

A response type defines the activity that can be executed by the responder, such as disable, enable, or close.

Glossary-24

Glossary

restart attempts

The number of times Remote RMC-700 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.

running configuration

The running configuration (current Remote RMC-700 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 RMC-700. A script can define job properties, which pass runtime parameters and/or settings (such as, connection information for a network element, baud rates, TID’s, phone numbers, software version, and user name and password information) to Remote RMC-700 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 RMC-700.

Glossary-25

Glossary

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 encrypted—only the client and the server at the other end have the encryption key.

server type

Server type is the type of remote user authentication used to provide security on a RAS server. The two supported options are TACACS+ and RADIUS.

service effect

The service effect is the effect on customer telephone service of the condition reported by a TL1 alarm.

SNMP

Simple Network Management Protocol (SNMP) is a standard specification for exchanging information between Remote RMC-700 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.

Glossary-26

Glossary

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 RMC-700, 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.

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 RMC-700 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.

STP maximum age

The STP maximum age specifies the maximum amount of time allowed before protocol information for the spanning tree protocol (STP) is discarded.

Glossary-27

Glossary

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 RMC-700. The position indicates where in the list a task should appear. Unless a user specifies a new position for a task, Remote RMC-700 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.

text block

A text block is a field of a TL1 alarm response. The TL1 text block is a quoted text line in the response block of a TL1 autonomous message. The exact format of a TL1 text block varies based on the type of autonomous message being created. For more information about the exact TL1 text block formats for different types of TL1 autonomous messages, refer to the Bellcore GR-833-CORE documentation.

TID

The TID is the TL1 target identifier.

TL1 command

A TL1 command pattern can generate a system event. TL1 commands are delivered through a communication path to a virtual NE.

Glossary-28

Glossary

TL1 multiplexer

A TL1 multiplexer is a device that multiplexes more than one TL1 data stream onto a single TCP connection.

trap

A trap is an SNMP alarm message.

U

UID

The UID is the TL1 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-29

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.

virtual TL1 NE

A virtual TL1 NE is a simulation of a TL1 NE environment that provides the ability to generate TL1 alarms on behalf of a digital and analog inputs state changes, and other system events. It also can be used to generate system responses, such as closing and opening relay outputs upon receipt of TL1 commands.

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

Glossary-30

Glossary

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).

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-31

Glossary

Glossary-32

. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Index

Aaccessing

CLI locally 2-2help 2-2web interface 2-10

accessing the CLIusing local connection 2-2

actioncommand example 10-6components 10-6configuring 10-7description 10-2

alarmnagging 13-2reporting 13-2simulation 13-20

alarm tablecentral 13-2description 13-2features 13-2test mode 13-20

analogadjustment 13-7averaging 13-6

architecture 20-3

Bbanner

configuring 2-6bi-state points

configuring 23-6BOOTP/DHCP relay

configuring 17-9

Ccentral alarm table

protocol formats 13-3raw alarm support 13-3SNMP support 13-3TL1 reporting support 13-3

CLIaccessing with remote connection 2-9

commandsexcluding 3-6identifications B-1including 3-6, B-1

configurationbacking up A-2

factory 4-4file 4-3fragment 4-3restoring A-3running 4-2, 4-5

configuration file A-3configuring

alarm entry 13-4, 13-8, 13-12, 13-14asynchronous serial to asynchronous

serial connection 15-11asynchronous to TCP connection 15-

14banner 2-6BOOTP/DHCP relay 17-9central FTP package server 20-4CLI session timeout 2-7custom profile 3-6default route 2-7DHCP client 17-10DHCP server 11-4, 17-4, 17-6domain name 5-2event, response, action 10-7GPRS 9-5host name 2-7host on DHCP server 17-8initial setup using wizard 23-3IP address 2-7IP settings 5-2IPTables 11-6IPv6 settings 5-4jobs 20-1MAC security 13-10measurement table entry 14-5mediation TL1 command 18-3modules 21-1network element sets 21-2NTP 5-5OpenVPN 9-8ppp encapsulation settings 9-6remote access protocol 2-7script package 20-5serial port using wizard 23-8session timeout 2-7SiteBus devices 22-2SNMP event template 19-5SNMP measurement template 19-11SNMP NE 19-15SNMP point template 19-6, 19-9SNMP to manage a relay output 18-6SSH to asynchronous serial

connection 15-9

static routes 8-1strong password 3-3system clock parameters 5-5TCP connection 15-5Telnet 13-18, 15-7, 16-6, 16-7TL1 multiplexer 16-3VPN 9-8wireless modem 9-5wireless network 9-1

Configuring Modules Using Command Line Interface 21-3

Configuring Modules Using Web Interface 21-10

Connect SCS 9-2, 9-3controller

bridge 6-2definition 6-2Ethernet 6-2OpenVPN 6-3serial 6-3types 6-2

copynetwork recovery file 4-5

correlation expressionconfiguring a time period 12-5evaluation 12-4operators 12-4originator types and states 12-3term 12-3

DDHCP client 17-10DHCP server

configuring 17-4configuring a host 17-8configuring subnet 17-6example 17-3

Director SCD 9-2, 9-3

EEthernet 6-4

controllers 6-2interfaces 6-4ports 1-4, 1-5, 6-2, 6-4

eventalarm associations 13-2command example 10-4components 10-4

Index-1

Index

configuring 10-7correlation 12-2description 10-2

event correlationcomponents 12-2configuring 12-6description 12-2expression components 12-3expression example 12-3

Hhelp

accessing 2-2HTTP 2-9HTTPS 2-9

Iinterface

asynchronous serial 6-5bridge 6-4definition 6-4description 6-4Ethernet 6-4modem 6-5OpenVPN 6-4serial 6-5

Jjob

configuring dynamic memory 20-13configuring start times 20-12configuring with a job property 20-8configuring with a job task 20-10description 20-2script package and script 20-7

KKentrox Kickstart 2-2

Llaptop

access for Remote 11-1assigning IP addresses 11-4

Mmeasurement table

entriesconfiguration examples 14-5states 14-2use with alarm table 14-3use with event correlations 14-3

overview 14-2mediation connections

description 15-2

NNetwork Address Translation

configuring IPTables 11-6enabling for laptop 11-6

network element setsconfiguring 21-2description of 21-2instance 21-2

NTP 5-5

PPackage Manifest file 20-2password

changing 3-4entering 2-3, 2-4strong 3-3

peripheralsconfiguring SiteBus devices 22-2

profileconfiguring B-1creating custom 3-6

protocols 15-2Python modules 20-2

Rrelay output

configuring SNMP 18-6configuring TL1 commands 18-4description 18-2open and close 18-8

Remotefeatures 1-2front panel connectors 1-4RMX 1-5

responder 10-5response

components 10-5configuring 10-7description 10-2

restorenetwork settings 4-5

RMX3200overview 1-5

running configuration 4-2running-config 2-8

Sscript 20-3

components 20-2Package Manifest file 20-2Python modules 20-2

script packageconfiguring a job 20-7creating and installing 20-5

SiteBus devices 22-2SNMP

event template 19-5manager 19-4

measurement template 19-11mediation event originator 19-4NE template 19-9network element 19-15point template 19-6

SNMP proxyconfiguration 19-2configuration information 19-3description 19-2

strong password 3-3

Ttemplates

NE 19-9terminal emulation software 2-4TL1 default commands 24-2

Uusers

adding 3-2deleting 3-5

Vverify user environment 2-8Virtual NE 16-4, 16-7Virtual Network Elements 24-1VNE 16-7VPN

configuring 9-8server 9-2, 9-3, 9-4

WWAN

interfaces 17-2web interface

accessing 2-10functions 2-10Home page 2-11job configuration 20-2restore network settings 4-5save running configuration 4-2

wireless networkconfigurations 9-3, 9-4configuring for Remote 9-2example 9-4overview 9-2required components 9-2with Connect SCS 9-4

wizardsbistate-alarms 23-6description 23-2initsetup 23-3serial-port 23-8types 23-2

Index-2

Copyrights and License Statements

Copyright © 1983-2014 by Kentrox® and/or Westell Technologies®

The material discussed in this publication is the proprietary property of Westell. Westell retains all rights to reproduction and distribution of this publication.

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 at www.westell.com/support.

TRADEMARKS:Kentrox, the Kentrox logo, and other names are intellectual property of WestellTechnologies.Linux is a registered trademark of Linus Torvalds.

All other trademarks or registered trademarks appearing in this publication are property of their respective companies.

To view entire license files and copyright statements for all open source code used in this product, use the show licenses command. Refer to the show licenses instructions in Remote RMC-700 Version 5.2x Command Reference Guide.

1-1

http://www.westell.com/support

Remote RMC-700 Version 5.2x Configuration Guide:

1-2

remote rmc-700 configuration guide for site...

Documents