Sunteți pe pagina 1din 53

EMS Configuration CLI Reference Manual

Part Number 40-00016-02 Revision D, Version 1.0 May 21, 2004 Proprietary
All information disclosed by this document is the proprietary property of Navini Networks, Inc. and is protected by copyright, trademark, and/or trade secret laws. All rights therein are expressly reserved.

About This Document Purpose


This document is provided for personnel using the Element Management System (EMS) Configuration Command Line Interface (CLI) application to configure a Ripwave system. The document is a reference manual where you can look up the command syntax needed in the context of configuring, enabling, etc. It is recommended that the user of this document be familiar with the EMS Overview Manual, the EMS Software Installation Guide, and the Ripwave Configuration Guide, plus attend the appropriate product training classes.

Related Documents
EMS Overview Manual EMS Software Installation Guide EMS Administration Guide

EMS Diagnostic Tools Guide EMS Alarm Resolution Reference Manual EMS - OSS Integration Guide Ripwave Configuration Guide Ripwave Modem User Guide Ripwave Base Station Installation & Commissioning Guide Ripwave RFS Configuration Quick Guide Ripwave Modem Software Update (CCU) Tool - Quick Guide

Revision History
Date Revision/Version 1.21.03 A/1.0 Author

S. Redfoot Same Same Same Same

Contributors C. Sanders J. Price Same Same Same + M. Cox Same + M. Cox

Comments New Draft (from former CAM)

2.14.03 8.29.03 3.30.04 5.21.04

A/1.0 B/1.0 C/1.0 D/1.0

Standard Release 1.19 Commercial Release 1.20 Draft Release 2.3 Commercial Release 4.1

Contacts
Contact Navini Networks during normal business hours: Monday through Friday 8:30 a.m. to 5:30 p.m. Central Time. You can also submit questions or comments by emailing techsupport@navini.com. Corporate Headquarters: Web Address: Technical Support: (972) 852-4200 www.navini.com 1-866-RIPWAVE (1-866-747-9283)

Navini Networks, Inc. 2240 Campbell Creek Blvd., Suite 110, Richardson, Texas 75082 USA

Permissions, Trademarks & Distribution Copyright August 2004, Navini Networks, Inc. All information contained herein and disclosed by this document is confidential and the proprietary property of Navini Networks, Inc. and all rights therein are expressly reserved. Acceptance of this material signifies agreement by the recipient that the information contained in this document is confidential and that it will be used solely for the purposes set forth herein. Acceptance of this material signifies agreement by the recipient that it will not be used, reproduced in

whole or in part, disclosed, distributed, or conveyed to others in any manner or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems - without the express written permission of Navini Networks, Inc. Navini Networks, Internet at the Speed of Thought, zero-install, unwired by Navini, the Navini Networks logo, and Ripwave are trademarks of Navini Networks, Inc. Other product and company names mentioned herein may be trademarks and/or service marks of their respective owners. Nothing herein constitutes any representation, warranty, assurance, or guaranty of any kind. Because of continuing developments and improvements in design, manufacturing, and deployment, material in this document is subject to change without notification and does not represent any commitment or obligation on the part of Navini Networks, Inc. Navini Networks, Inc. shall have no liability for any error or damages resulting from the use of this document. Any unauthorized usage is strictly prohibited without the express written permission of Navini Networks, Inc.

2003 Navini Networks, Inc. All rights reserved. Navini Networks, Inc. 2240 Campbell Creek Blvd. Suite 110 Richardson, Texas 75082 USA TABLE OF CONTENTS Overview..............................................................................................................................6 EMS Configuration Applications........................................................................................6 Modes...................................................................................................................................7 Common Commands.........................................................................................................10

Valid Commands Per Mode...............................................................................................11 Command Syntax...............................................................................................................17 Navigation Examples.........................................................................................................18 CLI Scripts.........................................................................................................................19 Error Messages...................................................................................................................21 How to Use This Document...............................................................................................22 Add or Create Commands...........................................................................................24 ATM Descriptor.................................................................................................................24 ATM Interface...................................................................................................................24 BTS....................................................................................................................................25 CPE (Modem)....................................................................................................................26 CPE Descriptor..................................................................................................................27 CPE Ping Address..............................................................................................................28 DiffServ..............................................................................................................................29 Home BTS.........................................................................................................................29 IMA....................................................................................................................................29 Neighbor BTS....................................................................................................................30 PVC....................................................................................................................................31 T1 to IMA..........................................................................................................................31 Calibrate Commands......................................................................................................33 Change/Modify..................................................................................................................34 EMS Password...................................................................................................................34 Collect Performance Data..................................................................................................35

Configure Commands.....................................................................................................35 ACL Filter..........................................................................................................................35 ARP Proxy.........................................................................................................................36 ATM Interface...................................................................................................................37 BTS....................................................................................................................................38 CPE....................................................................................................................................51 CPE Descriptor..................................................................................................................52

LIST OF FIGURES

LIST OF TABLES

Overview
EMS Configuration Applications
The EMS Configuration Command Line Interface (CLI) application may be used to configure, enable, disable, etc., Ripwave system parameters and elements. A separate EMS application, EMS Admin CLI, also uses the CLI format to enable Operators to perform backups of their EMS database, restore data, and perform other administrative tasks. The two applications together handle the same functionality as the EMS Configuration & Alarm Manager (CAM) Graphical User Interface (GUI) application (Figure 1). Figure 1: EMS Applications

While most users prefer the CAM application because it utilizes user-friendly windows, menus, click-on buttons, etc., CLI provides a common computer interface language used by networking professionals for data entry across different platforms (Figure 2 and Table 1). For example, a feature of the Configuration CLI is the ability to perform bulk configuration using CLI scripts. The scripts are created and tailored by the user for quicker and easier data entry. Every system executes unique CLI commands coded just for that system. This document explains those commands for the Ripwave system. Figure 2: CLI vs. CAM User Interface

Table 1: Comparison of CAM & CLI Table 1: Comparison of CLI & CAM

Modes

A mode is an environment in which a group of related commands is valid. All commands are mode-specific, i.e., you must navigate to a mode to execute a command contained in that mode (indicated by the command line prompt). There are three modes of operation in the Ripwave system (Figure 3): User Mode (view only) Admin Mode (view and modify all system elements) Configuration Modes (view and modify certain elements in the system)

The User Mode allows the user to log in and view all elements of the system, but not modify any of the data. The Admin Mode (Figure 4) allows the user to move into the configure mode, and to export data or show data. The Configuration Mode (Figure 5) allows the user to make configuration changes to the system overall, and to add, enable, configure, modify, etc., any of the system elements or attributes. There is more than one Configuration Command Mode. When initiating a session, the CLI is always set to the User Mode (view only) by default. This mode allows the user to log in to the system. In order to make any changes to the system, the Admin Mode or Configuration Mode must be entered. Within any mode, the exit command brings the user up one level in the mode hierarchy. For example, when in the Config BTS Mode, the exit command will take you to the Global Configuration Mode. From the User Mode, the exit command terminates the EMS Config CLI application. Typing end causes the CLI to immediately exit any configuration mode and return to the Admin Mode. Figure 3: CLI Modes

Figure 4: User Mode When you open the Config CLI application and type ? it lists the available commands in User Mode:

Figure 5: Admin Mode When you type enable <user name> <password> then ? it lists the available commands in Admin Mode:

Figure 6: Config Mode

From the Admin Mode, when you type configure then ? it lists the available commands in Config Mode:

Common Commands
As a general rule of thumb, if an element or condition of the system already exists in software, if you are planning to modify it you start by typing in the name of the element or attribute. If the element or attribute does not yet exist, you generally start with add or create or configure. Table 2 provides a list of common commands that can be executed from the different CLI modes.

Table 2: Common CLI Commands Command add configure delete disable enable end exit show script export ? Description Add an element to the network (i.e., BTS, PVC, ) Enter the Global Configuration Mode Delete an element from the network (i.e., BTS, PVC, ) Disable an element in the network (i.e., BTS, PVC, ) Enable an element in the network (i.e., BTS, PVC, ) Exit any Configuration Mode and return to the Admin Mode Exit the CLI application (if in User Mode), or exit current mode Display configuration data for a given network element Run a CLI script Export configuration data for a given network element to a text file Displays all the commands available for the current mode

Valid Commands Per Mode


Table 3 provides a list of valid commands for each of the CLI modes. Within the Configuration Mode, each sub-level Configuration Command Mode can set all attributes related to that mode. For example, from the Layer 1 Configuration Mode, the syncLevel attribute can be set. For a complete command listing of a specific mode, navigate to the mode within the CLI and type ?. Table 3: Valid Commands In Each Mode Mode User Admin Global Configuration - aclFilter - add - alarmAutoACK - arpProxy - autoProvision - bts Valid Commands enable, exit, language configure, exit, export, show downlinkBroadcast, dynamicAcl, end, exit add element to the network enable system to automatically acknowledge alarms egressProxy, ingressProxy, end, exit end, exit add, alarmHighTemp, alarmLowTemp, bridgeAgingTimer, broadcastSoftwareToCPE, btsContact, btsName, calInterval, calibrate, city, configsrc, cpeAutoUpgrade, cpePingAddress, defaultGateway, delete, diagnostics, disable, downloadBtsSoftware, downloadCpeSoftware, emsIpAddress, enable, enablePvcLoopback, end, exit, gps, ima, interfaceType, ipAddress, layer1, layer2, mgmtPvc, neighbor, performance, phoneNumber, provisioned, pvcLoopbackTest, radius, reset, shutdownHighTemp, shutdownLowTemp, state, street,

Mode

Valid Commands subnetMask, suppressAlarms, suppressCpeReg, SwapAndReset, syncAlarms, syncAllBtsData, syncAtmDescriptor, syncCpeDescriptor, SyncDiffServ, syncEmsVersion, syncMipProxy, syncNetworkId, t1, uploadPerfData, verifyBtsData, webAddress, zip enableAutoBcast, end, ethernetCpeSwVer, exit, cpeAutoUpgrade lcdCpeSw, pmcmiaCpeSw, usbCpeSwVer cpePingAddress displayString, end, exit, pingAddress diagnostics btsConsoleTimeout, diagPassword, diagUserName, enableBtsConsole, enableConstDisp, enableFreqSpecDisp, end, exit, maxBeamDisps gps end, exit, gmtOffset, height, latitude, longitude, updateFromBts ima add, addT1ToIma, alpha, atmInterface, beta, delete, disable, enable, end, exit, gamma, minRxLinks, minTxLinks, remoteT1FromIma, symmetry, txClkMode, txFrameLength, txImaId layer1 accScale, antenna, antennaPower, calBackplanLoss, calCableLoss, calcoefficient, calcoeffstatus, calibration, end, exit, gpsOffset, maxScale, rfs, rxSensitivity, rxSynGain, scSynGain, synLevel, syncScale, tccScale, txSynGain, w0 layer2 bandwidth, bccFlag, btsWanCC, carrierAccMask, centerFreq, cpeUplinkCC, end, exit, maxSubCarriers, repeatUplinkPkts, symmetricRatio neighbor end, exit, isCoLocate performance collectInterval, end, exit, ftpDirectory, ftpPassword, ftpServerIp, ftpUserName, uploadInterval t1 add, atmInterface, channelization, circuitId, delete, disable, enable, end, exit, fdl, lineCoding, lineLength, lineStatusTrap, lineType, loopback, sendCode, signalMode, txClockSrc antenna disable, enable, end, exit, rfCableLoss, rfRxGain, rfTxGain, splitterX, splitterY atmInterface add, delete, maxActiveVciBits, maxActiveVpiBits, maxVccs, maxVpcs, pvc bandwidth avgBurstTime, avgLlcQLenFactor, bwAdjustTime, deniedReqNum, dlFtpAckPriority, downlinkAccPower, end, exit, expAvgPower, expForAverage, extendedDistance, inactiveTime, initSetupPower, llcReserved (1-4), macReserved (1-4), maxBtsPwrPerUser, maxDLBufferDelay, maxSimulSessions, minActiveTime, minBtsPwrCntrlMargin, minBwDownlink, minBwHoldTime, minBwUplink, minIdleTime,

Mode

btsWanCC calibration cpeUplinkCC w0 - cpe layer3

- cpeDescriptor

trafficCtrl

- cpeFtpDirectory - cpeFtpPassword - cpeFtpUserName - delete - dhcpRelay

- diffServ - emsId - ftpRootDir - maxAcksPerHour - mobileIP - networkId - output - password - probeCpe - script - updateEmsVersion

Valid Commands minReassignStep, minUplinkStrength, negativeThreshold, nrtBwHoldTime, nrtPacketTTL, nrtPreReleaseBw, overloadThreshold, positiveThreshold, powerCtrlRange, priority1Bw (1-8), qamMask, quietTime, reservedBw, reservedSessions, rtBwHoldTime, rtMinBw, totalPriority, underloadThreshold end, exit, highThreshold, lowThreshold, maxThresProb, maxThreshold, voiceThreshold, weight end, exit, rxCalWeightX, rxCalWeightY, txCalWeightX, txCalWeightY end, exit, highThreshold, lowThreshold, maxThresProb, maxThreshold, voiceThreshold, weight end, exit, weightX, weightY add, collectPM, delete, descrIndex, disable, enable, end, exit, layer3, nomadic, reset, trusted, unicastSoftwareToCpe verifyCPEData ClientAddress, end, exit, highDropPolicy, ingressAcl, ingressBroadcast, maxAddressNumber descrName, downlinkMaxBW, downlinkMinBW, end, exit, priority, trafficCtrl, uplinkMaxBW, uplinkMinBW end, exit, HighThreshold, lowThreshold, maxThresProb, maxThreshold, voiceThreshold, weight end, exit end, exit end, exit end, exit disable, enable, end, exit, highAgentThreshold, lowAgentThreshold, maxDhcpSize, optionCircuitId, optionDOCSISDevice, optionRemoteId, optionStatus, optionVPNId end, exit, diffServType end, exit end, exit end, exit end, exit end, exit end, exit end, exit end, exit

Figure 7 on the following 3 pages provides a quick-reference Command Tree, which visually represents the command layers using EMS Config CLI. Figure 7 (1 of 3): Command Tree

Figure 7 (2 of 3): Command Tree

Figure 7 (3 of 3): Command Tree

Command Syntax
When entering data in the command line, do not enter any spaces in the command parameters (i.e., show btsDownLink). If a parameter requires a space, enter it in double quotes (i.e. Ems1> btsContact Joe Smith). The commands are not case sensitive. The capital letters in the commands are used only for ease in reading the string. Figure 8 is an example with explanation. Table 4 lists the syntax symbols and their meanings. Figure 8: Example of a Command Syntax

Table 4: Command Syntax Syntax <> [] < | > or [ | ] bold Use Mandatory parameter Optional parameter Designates that only one of the parameters is used in the command Key word

Navigation Examples
Following are examples of changing Modes and executing command sequences. 1. Enter the BTS Mode from the User Mode: General example Ems> enable <userID> <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Specific example Ems> enable navini emsAdmin Ems1# configure Ems1(config)# bts 2 2. Enter the CPE Mode from the User Mode: General example Ems> enable <userID> <your password> Ems1# configure Ems1(config)# cpe <desired specific CPE> Specific example Ems> enable navini emsAdmin Ems1# configure Ems1(config)# cpe 0x37 3. Enter the CPE Descriptor Mode from the User Mode: General example

Ems> enable <userID> <your password> Ems1# configure Ems1(config)# cpedescriptor <desired specific CPE Descriptor> Specific example Ems> enable navini emsAdmin Ems1# configure Ems1(config)# cpedescriptor 1 4. Enter the DiffServ Mode from the User Mode: General example Ems> enable <userID> <your password> Ems1# configure Ems1(config)# diffserv <diffServ code point> Specific example Ems> enable navini emsAdmin Ems1# configure Ems1(config)# diffserv 10

CLI Scripts
A CLI script consists of a string of commands that helps expedite the configuration process. Administrators familiar with CLI scripting will find that using scripts to execute Ripwave configurations can save valuable time. A script must be accessible from the machine that is running the CLI program. To run a script, type the following: script [-<s (silence) | c (continue on error) | sc (both c and s)>] <fileName> silence No output is displayed to the screen when a script is run.

continue on error

The script continues to execute the next command even if one of the commands fail. If the -c option is not used, the entire script terminates if one command fails. The name of the CLI script file to be executed. Either an absolute path to the CLI script can be given or a relative path from the <EMS install directory>.

filename

By using the output command, the EMS outputs all commands entered in the CLI to the specified CLI script file. This command is used to create CLI scripts: output [-<a (includes error message to output)>] <fileName | 'close' (close output)> -a Includes all error messages to the output file. Includes any error message to the output CLI script file. This option is useful to record any activity performed on the CLI and the success/failure status on each command executed. Output file name for the CLI script. Closes the CLI script output file. Use this option after all output commands are entered into the output file.

filename Close

The following exhibit is an example of a script that might be used to modify existing Modems Home BTSs. Exhibit: Sample CLI Script
#EmsId 1 CPE 0xFFFF276C add homeBts 1000 delete homeBts 1002 enable exit CPE 0xFFFF2860 add homeBts 1000 delete homeBts 1002

enable exit CPE 0xFFFF28F9 add homeBts 1000 delete homeBts 1002 enable exit CPE 0xFFFF2906 add homeBts 1000 delete homeBts 1002 enable exit

Error Messages
Table 5 contains a few of the error messages encountered when a command is not entered correctly. Common mistakes include use of or lack of spacing, entering commands from an incorrect Mode, and forgetting to specify a particular identification number or value. Table 5: CLI Error Messages

Example
Ems1(config)# t1 % Incomplete command: T1 Enter T1 command mode: t1 <ifIndex> Ems1(config-t1)# linelength temp % Invalid input detected with value temp

Meaning
Incomplete command error message: You did not enter all of the keywords or values required by this command. This example requires an interface index.

Invalid input error message: This example is expecting an integer instead of a string.

Change dsx1LineLength value: Linelength <value> Ems1(config)# gizbot % Unrecognized command: gizbot Type ? for help. Backspace over the previous text and enter a question mark to see all the commands for that mode. This example uses a command that is not available within that mode.

How to Use This Document


This is a look up, or reference, document. This document assumes the user is familiar with the Ripwave Configuration Guide and other documents that are descriptive and procedural. The structure of this document is based on key actions/commands: Add or Create Calibrate Change EMS Password Collect Performance Data Configure Delete Disable or Remove Enable Export Reset Show Swap & Reset Synchronize

Probe or Test Upgrade Software Verify

These are arranged alphabetically for quick look-up of information. Within each section, i.e., within Add or Create, the types of commands are also arranged by entity and/or alphabetically. As you are using the CLI interface, if you arent sure which command or syntax to use, go to the section in this document covering that action - i.e., Add, Configure, Show, etc. - whatever it is you are attempting to do. Also, in the back of this document is a Key Word Index to help you locate information related to a key term, i.e., BTS, CPE, or action throughout the document. Therefore, you can find a command based on the action you are performing or based on a key term. This manual may be found on the Ripwave Documentation CD, as well as on the EMS software itself (online) under the pull-down Help menu in CAM.

Add or Create Commands


When the system is turned over to the Operator/Service Provider, it usually has the minimum configuration required in the EMS database to test its operational status. This section provides the commands associated with adding system elements, such as BTSs, CPEs/Modems, global parameters, etc., and additional indexes or values to the system database using the EMS CLI interface.

ATM Descriptor
To add an ATM Descriptor to the system: Ems> enable < userID > <your password> Ems1# configure Ems1# add atmDescriptor <index descriptorType<2=ATMNOCLPNOSCR| 5=ATMNOCLPSCR | 6=ATMCLPNOTAGGINGSCR | 7=ATMCLPTAGGINGSCR| 8=ATMCLPNOTAGGINGMCR | 9=ATMCLPTRANSPARENTNOSCR | 10=ATMCLPTRANSPARENTSCR |11=ATMNOCLPTAGGINGNOSCR | 12=ATMNOCLPNOSCRCDVT | 13=ATMNOCLPSCRCDVT | 14=ATMCLPNOTAGGINGSCRCDVT | 15=ATMCLPTAGGINGSCRCDVT>param1 param2 param3 param4 param5 serviceCategory<2=CBR | 3=RTVBR | 4=NRTVBR | 5=ABR | 6=UBR> frameDiscard <1=TRUE | 2=FALSE>> Index type Param 1-5 service category frame discard Index of the ATM descriptor. Type of ATM. Dependant on ATM Category. Category of ATM. Enable ability to discard ATM frames.

ATM Interface
To add an ATM interface for an IMA group: Ems> enable < userID > <your password>

Ems1# configure Ems1(config)# bts <desired specific BTS > Ems1(config-bts)# ima <imaGroupIndex> Ems1(config-ima)# add atmInterface < atmInterfaceMaxVpcs atmInterfaceMaxVccs atmInterfaceMaxActiveVpiBits atmInterfaceMaxActiveVciBits > OR Ems> enable < userID > <your password> Ems1# configure Ems1(config)# bts <desired specific BTS > Ems1(config-bts)# T1 <ifIndex> Note: The syntax t1 is used whether the facility is a T1 or an E1. Ems1(config-T1)# add atmInterface < atmInterfaceMaxVpcs atmInterfaceMaxVccs atmInterfaceMaxActiveVpiBits atmInterfaceMaxActiveVciBits > atmInterfaceMaxVpcs interface. atmInterfaceMaxVccs atmInterfaceMaxActiveVpiBits atmInterfaceMaxActiveVciBits Maximum number of VPCs for this Maximum number of VCCs for this interface. Maximum number of bits for a PVCs VPI. Maximum number of bits for a PVCs VCI.

Note: An IMA group must exist before you can add an ATM Interface.

BTS
To add a BTS to the system:

Ems> enable <userID > <your password>

Ems1# configure Ems1# add bts : <name IPAddress btsId profileType <1=UNLICENCE_BAND | 2=MMDS_BAND | 3=WCS_AB_BAND | 4=WCS_CD_BAND | 5=MMDS_BAND_NO_FILTERS | 6=TWO_POINT_THREE_EIGHT_BAND | 7=TTA_UNLICENCE_BAND | 8=TTA_WLL_BAND | 9=TTA_WLL_BAND_NO_FILTERS | 10=ONE_POINT_EIGHT_BAND_NO_FILTERS | 11=TTA_MMDS_BAND | 12=TTA_MMDS_BAND_NO_FILTERS | 13=TWO_POINT_ZERO_ONE_BAND_NO_FILTERS> interfaceType<1=ETHERNET | 2=ATM | 3=ATM_E1> defaultGateway subnetMask centerfrequency(KHz) maxSupportedSubCarriers <0=SUB_10CARRIERS | 1=SUB_8CARRIERS | 2=SUB_6CARRIERS>> name IPAddress btsId profileType Interface Type Default gateway Subnet mask centerFrequency Unique name given to the BTS. Unique IP address given to the BTS. Unique numeric ID number given to the BTS. The type of BTS based on frequency range (2.4, 2.6, etc.) The type of backhaul interface, either ATM or Ethernet. The Default Gateway used to route IP packets for a BTS. The Subnet Mask used to route IP packets for a BTS. The center frequency of the BTS transmit signal. The maximum number of sub-carriers supported.

MaxSupportedSubCarriers

CPE (Modem)
To add a CPE/Modem to the system: Ems> enable < userID > <your password> Ems1# configure Ems1# add cpe <cpeEid [- toCpeEid] parmDescrIndex nomadicType<1=ENABLED | 2=DISABLED | 3=ENABLED_WITH_HOME_BTS> collectPm<1=TRUE | 2=FALSE> trusted <1=TRUE | 2=FALSE> ingressAcl <1=ENABLED | 2=DISABLED> ingressBroadcast <1=ENABLED | 2=DISABLED> highDropPolicy <1=DROP_LEASE_RECENTLY_LEASED |

2=DROP_MOST_RECENTLY_LEASED> maxAddressNumber <value> homeBTSIds... (up to 8 btsIds) > cpeEid ToCpeEid parmDescrIndex NormaticType collectPm Modem. Trusted IngressAcl Represents the EID for a Modem. Represents the last EID if a contiguous range is given. Index for the CPE descriptor. Value that enables/disables nomadism for the Modem. Value that enables/disables collection of performance data on this Value that turns on or off the trusted capability. Determines whether a MAC address that cannot be found in the current CPE Authenticated IP List is discarded.

IngressBroadcast Determines whether an incoming MAC broadcast message is discarded. HighDropPolicy Determines what type of leased IP addresses are dropped.

MaxAddressNumber Maximum number of devices a single Modem can serve. homeBTSIds ID of the home BTS(s) for this Modem.

CPE Descriptor
To add a CPE Descriptor to the system: Ems> enable < userID > <your password> Ems1# configure Ems1# add CPEDescriptor <CPEParamDescrIndex CPEDescriptorName priority uplinkMaxBandwidth uplinkMinBandwidth downlinkMaxBandwidth downlinkMinBandwidth weight lowPriorityMinThreshold highPriorityMinThreshold voicePriorityMinThreshold maxThreshold maxThresProb> CPEParamDescrIndex This object is used to identify the row of this table. When creating a new row in the table the value of this index may be obtained by retrieving the value of descrParamIndexNext.

CPEDescriptorName priority

The name of the CPE Descriptor. This is used to indicate the overall service priority, 0 represents the highest level service, 4 is the lowest level. Indicates the maximum UL bandwidth guaranteed for this Indicates the minimum UL bandwidth guaranteed for this Indicates the maximum DL bandwidth guaranteed for this Indicates the minimum DL bandwidth guaranteed for this Indicates the queue weight. Indicates the minimum threshold for low priority. Indicates the minimum threshold for high priority. Indicates the minimum threshold for voice priority. Indicates the maximum threshold for all priority. Indicates the maximum threshold probability.

uplinkMaxBandwidth Modem. uplinkMinBandwidth Modem. downlinkMaxBandwidth Modem. downlinkMinBandwidth Modem. weight lowPriorityMinThreshold highPriorityMinThreshold voicePriorityMinThreshold maxThreshold maxThresholdProb

CPE Ping Address


To add a CPE Ping Address: Ems> enable < userID > <your password> Ems1# configure Ems1(config)# bts <desired specific BTS > Ems1(config-bts)# add cpePingAddress <sequence number> <IP Address> <Display String> sequence number ip address Order in which the elements are pinged. IP address of the element.

display string

User-assigned designation (name/string) of the element

DiffServ
To add a Differentiated Service: Ems> enable < userID > <your password> Ems1# configure Ems1(config)# add diffServ <diffservcodepoint> <diffservtype 1=LOW | 2=HIGH | 3=VOICE> diffServCodePoint diffServType Unique index mappings to a defined differentiated service. Value indicating diffServ type.

Home BTS
To add a BTS ID to the Home BTS List for a Modem: add <homeBts> <btsId | btsName> entity type (homeBts) Entity of item to add. btsId btsName Unique numeric ID number given to the BTS. Unique name given to the BTS.

IMA
To add an IMA group to the system: Ems> enable < userID > <your password> Ems1# configure Ems1(config)# bts <desired specific BTS > Ems1(config-bts)# add ima <imaGroupIndex imaGroupSymmetry <1=Symmetric_Operation | 2=Asymmetric Operation | 3= Asymmetric Configuration> imaGroupMinNumTxLinks imaGroupMinNumRxLinks btsImaGroupFarendEquipment <0=Standard Compliant | 1=Alcatel> imaGroupNeTxClkMode <1=CTC | 2=ITC>

imaGroupTxImaId imaGroupTxFrameLength imaGroupAlphaValue imaGroupBetaValue imaGroupGammaValue> imaGroupIndex imaGroupSymmetry imaGroupMinNumTxLinks A unique integer value for the IMA Group. Symmetry of the IMA group. Minimum number of Transmit links required to be active for the IMA group to be in the operational state. Minimum number of Receive links required to be active for the IMA group to be in the operational state.

imaGroupMinNumRxLinks

BtsimaGroupFarendEquipment The type of far-end equipment used. imaGroupNeTxClkMode imaGroupTxImaId function. imaGroupTxFrameLength Transmit clocking mode used by the near-end IMA group. The IMA ID currently in use by the near-end IMA The frame length to be used by the IMA group in the transmit direction. Can only be set when the IMA group is startup. Indicates the 'alpha' value used to specify the number of consecutive invalid ICP cells to be detected before moving to the IMA Hunt state from the IMA Sync state. Indicates the 'beta' value used to specify the number of consecutive errored ICP cells to be detected before moving to the IMA Hunt state from the IMA Sync state. Indicates the 'gamma' value used to specify the number of consecutive valid ICP cells to be detected before moving to the IMA Sync state from the IMA PreSync state.

imaGroupAlphaValue

imaGroupBetaValue

imaGroupGammaValue

Neighbor BTS
To add a Neighbor BTS to a specific BTS: Ems> enable < userID > <your password> Ems1# configure

Ems1(config)# bts <desired specific BTS > Ems1(config-bts)# add neighbor <centerFrequency> <in kHz> <isCoLocate> <1=TRUE | 2=FALSE>> centerFrequency isCoLocate Numeric value of the centerFrequency Co-location status represented by TRUE or FALSE

PVC
To add a PVC to an ATM interface: . Ems> enable < userID > <your password> Ems1# configure Ems1(config)# bts <desired specific BTS > Ems1(config-bts)# ima <imaGroupIndex> Ems1(config-ima)# atmInterface Ems1(config- atmInterface)# add pvc <index [-toIndex] atmVclReceiveTrafficDescrIndex atmVclTransmitTrafficDescrIndex atmVccAal5EncapsType <7=LLC_ENCAPSULATION | 2=VC_MULTIPLEXBRIDGEDPROTOCOL8023 | 1=VC_MULTIPLEXROUTEDPROTOCOL >> index atmVclReceiveTrafficDescrIndex data atmVclTransmitTrafficDescrIndex data atmVccAal5EncapsType Interface index for this PVC. Index of the ATM traffic descriptor used to receive Index of the ATM traffic descriptor used to transmit Type of encapsulation to be used for this PVC.

T1 to IMA
To add a T1 or E1 to an IMA group:

addt1toima <(T1s) index> T1s index T1 index specifying which T1/E1 to add to the IMA group.

Calibrate Commands
You can select one of three types of Base Station calibration: 1 2 3 OR OR OR fullcalibration online onlinewohistory Power and Gain Tuning Online calibration Clear the history and perform calibration

To perform a Full Calibration, use the following CLI commands: Ems> enable < userID > <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Ems1(config-bts)# calibrate fullcalibration OR Ems1(config-bts)# calibrate 1

To perform an Online Calibration, use the following CLI commands: Ems> enable < userID > <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Ems1(config-bts)# online

OR

Ems1(config-bts)# calibrate 2

To perform an Online Calibration Without History, use the following CLI commands: Ems> enable < userID > <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Ems1(config-bts)# calibrate onlinewohistory

OR Ems1(config-bts)# calibrate 3

To monitor calibration status, use the following CLI commands:

Ems> enable < userID > <your password> Ems1# show antenna <BTS ID|BTS name> [antennaIndex] [detail | stats] This will display the gain setting of each antenna to determine if the calibration is successful. If any antenna has a gain value of zero, calibration failed for that antenna.

Change/Modify
EMS Password
When you first receive the Ripwave system, the EMS user ID and password are set to defaults. For security reasons, you should change the password for each user account. Both are case sensitive. Default User ID: Default Password: emsAdmin emsAdmin

Ems> enable < userID > <your password> Ems1# configure Ems1(config)# password <old password> <new password> old password new password Old EMS password for the user currently logged into the CLI. New EMS password for the user currently logged into the CLI.

Collect Performance Data


To upload Modem and Base Station performance logs, use the following commands: Ems> enable < userID > <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Emsl(config-bts)# uploadPerfData Check the performance log server and the log storage directory for uploaded BTS and CPE performance logs.

Configure Commands
ACL Filter
To enable the Access Channel Filter for downlink Broadcasts (Figure 9): Ems> enable <userID> <your password> Ems1# configure Ems1(config)# aclFilter Ems1(config-aclFilter)# downlinkBroadcast <1 = Enabled | 2 = Disabled> To enable dynamic Access Channel Filter: Ems> enable <userID> <your password> Ems1# configure Ems1(config)# aclFilter Ems1(config-aclFilter)# dynamicAcl <1 = True | 2 = False> Figure 9: ACL Filter Commands

ARP Proxy
To enable ARP Proxy for egress filtering (Figure 10): Ems> enable <userID> <your password> Ems1# configure Ems1(config)# arpProxy Ems1(config-aclFilter)# egressProxy <1 = True | 2 = False> To enable ARP Proxy for ingress filtering: Ems> enable <userID> <your password> Ems1# configure Ems1(config)# arpProxy Ems1(config-aclFilter)# ingressProxy <1 = True | 2 = False> Figure 10: ARP Proxy Commands

ATM Interface
There are two paths available to reach the ATM Interface Mode (Figure 11): through the IMA mode or through the T1 mode. Note: Before you can enter the ATM Interface Mode, you must first add an ATM Interface. For instructions on how to add an ATM Interface, refer to the section entitled, Add or Create Commands. If you do an add an ATM Interface before attempting these commands, you will get a message that reads, Object does not exist To enter the ATM Interface Mode through the IMA Mode: Ems> enable <userID> <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Ems1(config-bts)# ima <ima group index> Ems1(config-ima)# atminterface To enter the ATM Interface Mode through the T1 Mode: Ems> enable <userID> <your password> Ems1# configure Ems1(config)# bts <desired specific BTS>

Ems1(config-bts)# t1 <ifIndex, i.e. 1, 2, 3, 4, 5, 6, 7, or 8> Note: The syntax t1 is used whether the facility is a T1 or an E1. Ems1(config-t1)# atminterface Figure 11: ATM Interface Commands

BTS
To configure a BTS that has been added to the system (Figure 12): Ems> enable <userID> <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Figure 12: Configure BTS Commands (next 2 pages)

Figure 12 (1 of 3): Configure BTS Commands

Figure 12 (2 of 3): Configure BTS Commands

Figure 12 (3 of 3): Configure BTS Commands

CPE AutoUpgrade
To enable or disable the CPE AutoUpgrade feature (Figure 13):

Ems> enable <userID> <your password> Ems1# configure Ems1(config)# BTS <desired specific BTS> Ems1(config-bts)# cpeAutoUpgrade Figure 13: CPE AutoUpgrade Commands

GPS
To configure a Global Positioning System for a specific BTS (Figure 14): Ems> enable <userID> <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Ems1(config-bts)# gps

Figure 14: GPS Commands

Layer 1 Commands
To configure Layer 1 for a specific BTS (Figure 15): Ems> enable <userID> <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Ems1(config-bts)# layer1 Figure 15: Layer 1 Commands

Antenna To configure the antenna table for a specific BTS (Figure 16): Ems> enable <userID> <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Ems1(config-bts)# layer1 Ems1(config-layer1)# antenna <antennaIndex> Figure 16: Antenna Commands

Calibration To configure the calibration values for a specific BTS (Figure 17):

CAUTION: Calibration values are set automatically by the BTS. Under normal circumstances you should not change these values. They are populated when a Full Calibration, Online Calibration, or Online Calibration Without History is invoked or runs automatically. Ems> enable <userID> <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Ems1(config-bts)# layer1 Ems1(config-layer1)# calibration <carrierId/antennaIndex> Figure 17: Calibration Commands

w0 Table Commands To configure the w0 Table for a specific BTS (Figure 18): Ems> enable <userID> <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Ems1(config-bts)# layer1 Ems1(config-layer1)# w0 <carrierId/antennaIndex> Figure 18: w0 Commands

Layer 2 Commands
To configure Layer 2 for a specific BTS (Figure 19): Ems> enable <userID> <your password>

Ems1# configure Ems1(config)# bts <desired specific BTS> Ems1(config-bts)# layer2

Figure 19: Layer 2 Commands

Bandwidth To configure the bandwidth for a specific BTS: Ems> enable <userID> <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Ems1(config-bts)# layer2 Ems1 (config-layer2) bandwidth Figure 20 (pages 1 of 3, 2 of 3, and 3 of 3) show all parameters associated with L2 bandwidth.

Figure 20 (1 of 3): L2 Bandwidth Commands

Figure 20 (2 of 3): L2 Bandwidth Commands

Figure 20 (3 of 3): L2 Bandwidth Commands

Congestion Control To configure (modify) the bandwidth thresholds on the downlink side, use the following command sequence (Figure 21). It will bring up the configurable parameters. Ems> enable <userID> <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Ems1(config-bts)# layer2 Ems1 (config-layer2) btsWanCC

To configure (modify) the bandwidth thresholds on the uplink side, use the following command sequence (Figure 22). It will bring up the configurable parameters. Ems> enable <userID> <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Ems1(config-bts)# layer2 Ems1 (config-layer2) cpeUplinkCC Figure 21: Downlink Congestion Control Commands

Figure 22: Uplink Congestion Control Commands

Temperature

To configure (modify) the BTS temperature shutdown low and high use the following commands: Ems> enable <userID> <your password> Ems1# configure Ems1(config)# bts <desired specific BTS> Ems1(config-bts)# alarmHighTemp <value> alarmLowTemp <value> shutdownHighTemp <value> shutdownLowTemp <value>

CPE
To configure a CPE/Modem (Figure 23): Ems> enable <userID> <your password> Ems1# configure Ems1(config)# cpe <desired specific CPE> Figure 23: CPE Commands

CPE Descriptor
To configure a CPE Descriptor (Figure 24): Ems> enable <userID> <your password> Ems1# configure Ems1(config)# cpedescriptor <desired specific CPE descriptor> Figure 24: CPE Descriptor Commands