Documente Academic
Documente Profesional
Documente Cultură
DIMETRATM
System Documentation
Dimetra IP
June 2008
When printed by Motorola
6866600D04-G
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs. Laws in the United States and other countries
preserve for Motorola certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted Motorola computer programs contained in
the Motorola products described in this document may not be copied or reproduced in any manner without the express written permission of Motorola.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the
copyrights, patents or patent applications of Motorola, except for the normal nonexclusive, royalty-free license to use that arises by operation of law in the sale
of a product.
Disclaimer
Please note that certain features, facilities and capabilities described in this document may not be applicable to or licensed for use on a particular system, or
may be dependent upon the characteristics of a particular mobile subscriber unit or configuration of certain parameters. Please refer to your Motorola contact
for further information.
Trademarks
MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their
respective owners.
Copyrights
© 2006 - 2008 Motorola, Inc. All rights reserved.
No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated into any language or computer language, in any form or by
any means, without the prior written permission of Motorola, Inc.
European Union (EU) Waste of Electrical and Electronic Equipment (WEEE) directive
The European Union’s WEEE directive requires that products sold into EU countries must have the crossed out trashbin label on the product (or the package
in some cases).
As defined by the WEEE directive, this cross-out trashbin label means that customers and end-users in EU countries should not dispose of electronic and
electrical equipment or accessories in household waste.
Customers or end-users in EU countries should contact their local equipment supplier representative or service centre for information about the waste collection
system in their country.
CMM labeling and disclosure table
The People’s Republic of China requires that Motorola’s products comply with
China Management Methods (CMM) environmental regulations. (China
Management Methods refers to the regulation Management Methods for
Controlling Pollution by Electronic Information Products.) Two items are used to
demonstrate compliance; the label and the disclosure table.
The label is placed in a customer visible position on the product.
• Logo 1 means that the product contains no substances in excess of the
maximum concentration value for materials identified in the China
Management Methods regulation.
• Logo 2 means that the product may contain substances in excess of the
maximum concentration value for materials identified in the China
Management Methods regulation, and has an Environmental Friendly
Use Period (EFUP) in years, fifty years in the example shown.
Logo 1 Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during
which the Toxic and Hazardous Substances (T&HS) contained in the Electronic
Information Product (EIP) will not leak or mutate causing environmental pollution
or bodily injury from the use of the EIP. The EFUP indicated by the Logo 2 label
applies to a product and all its parts. Certain field-replaceable parts, such as
battery modules, can have a different EFUP and are marked separately.
The Disclosure Table is intended only to communicate compliance with China
requirements; it is not intended to communicate compliance with EU RoHS or any
other environmental requirements.
The EMEA Systems Support Centre provides a Technical Consulting service. This service is accessed via the Call
Management Centre.
The European System Component Centre provides a repair service for infrastructure equipment, including the
MBTS. Customers requiring repair service should contact the Call Management Centre to obtain a Return
Authorisation number. The equipment should then be shipped to the following address unless advised otherwise.
Request for help in identification of non-referenced spare parts should be directed to the Customer Care
Organization of Motorola’s local area representation. Orders for replacement parts, kits and assemblies should be
placed directly on Motorola’s local distribution organization or via the Extranet site Motorola Online at
https://emeaonline.motorola.com.
Information related to support and service of Motorola Test Equipment is available by calling the Motorola Test
Equipment Service Group in Germany at +49 (0) 6128 702179, Telefax +49 (0) 6128 951046, through the
Customer Care Organization of Motorola’s local area representation, or via the Internet at
http://www.gd-decisionsystems.com/cte/.
Your Input
...is much appreciated. If you have any comments, corrections, suggestions or ideas for this publication or any
other requirements regarding Motorola publications, please send an e-mail to doc.emea@motorola.com.
Document History
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Contents
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Chapter 1: Introduction
MMI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Access Levels and Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
platform_number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
revision_number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
reference_source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
real_time_clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
rx_fru_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56
time_reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
temp_sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
watchdog_settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
unmount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
vols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
position_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
fv -oplatform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
freq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Base Radio Application Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
AIEA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
AIR_TRACER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
AIR_TRACER_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
CHANSTAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
CLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
DEKEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
EXIT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
GET ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
GET CABINET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
GET CONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
GET EX_AD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
GET EXT_REF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
GET FWD_PWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
GET MAX_VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
GET NVM_PARAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
GET PA_AD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
GET PA_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
GET POSITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
GET REF_PWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
GET RPTR_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
GET RX_FREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
GET TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
GET VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
KEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
KVL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
lstalm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
lstalmtr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
VER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
SET LAPD_TRACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
SET LOG_ROUTING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
SET MAX_VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
SET NVM_PARAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
SET SM_TRACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
List of Tables
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Related Information
In addition to the information in the table below, see the Related Information Guide.
Related Information Purpose
Standards and Guidelines for Provides standards and guidelines that should be followed
Communication Sites (68P81089E50) when setting up a Motorola communications site. Also
known as R56 manual.
Dimetra System Overview (6866600D10) Provides the overall description and theory of operation for
the system. It consists of two sections, a general view of the
system that is suitable for non-technical personnel, and a
technical view that can provide maintenance personnel with
a detailed description of the system and its components. It
also includes the Dimetra IP 2007 system diagrams and a
glossary, as well as customer documentation descriptions and
a port configurations reference for Dimetra IP 2007 systems.
Icon Conventions
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The document set is designed to give the reader more visual clues. The following graphic icons are used
throughout the documentation set. These icons and their associated meanings are described below.
The signal word DANGER with the associated safety icon implies information
that, if disregarded, will result in death or serious injury.
The signal word WARNING with the associated safety icon implies information that,
if disregarded, could result in death or serious injury, or serious product damage.
The signal word CAUTION with the associated safety icon implies information that,
if disregarded, may result in minor or moderate injury, or serious product damage.
The signal word CAUTION may be used without the safety icon to state
potential damage or injury that is not related to the product.
IMPORTANT statements contain information that is crucial to the discussion at hand, but is not
CAUTION or WARNING. There is no warning level associated with the IMPORTANT statement.
NOTE contains information more important than the surrounding text, such as exceptions or
preconditions. They also refer the reader elsewhere for additional information, remind the reader
how to complete an action (when it is not part of the current procedure, for instance), or tell the
reader where something is located on the screen. There is no warning level associated with a note.
SUGGESTION
SUGGESTION implies a recommendation or tip from Motorola, that does not require to be
followed, but might be helpful. There is no warning level associated with SUGGESTION.
1
Introduction
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
MMI Commands
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
MMI commands are the input from a service computer to the system RS-232 serial port (19200 bps, 8 data
bits, 1 stop bit, no parity). Depending on the task, the RS-232 port is accessed from the Site Controller,
or from the front of each Base Radio Controller (BRC) in the Equipment Cabinet.
The service technician enters the MMI commands to communicate with the Site Controller at the
system level. The system response is returned to the service computer via RS-232.
Various test procedures use these commands to test and configure the system. The test procedures
for the Site Controller are described in “MTS 2 and MTS 4 Configuration, Installation and
Basic Service Manual”, in chapter “Configuration and Testing”.
The Site Controller and BR commands are available through the use of the password. This password allows
the service technician access to a subset of the MMI command set for field service operations.
There is a default password that is programmed during manufacturing. The pass-
word should be changed via the MMI.
Site Controller can be accessed in the following modes:
• BOOT1: used for loading the actual Site Controller Application or loading the Test Application
• Test Application: provides facilities for setup, diagnostic and testing
• Site Controller Application
Base Radio has similar modes, where MMI commands can be used:
• BOOT1: used for loading the actual Base Radio Application or loading the Test Application
• Test Application: provides facilities for setup, diagnostic and testing
• Base Radio Application
Conventions
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The syntax for the Site Controller and BR commands is case sensitive. Each example is
shown in the format that should be entered by the operator.
Some commands require the use of parameters. If input parameters are not entered, a response
is returned identifying the proper syntax for the command.
A definition describes in detail each command’s purpose and function. Where helpful, the definition is
followed by an example of the commands response. Typical values have been used whenever possible.
Some commands return varying responses (such as available, not available, unknown, o.k., and
alarm). Only one of the possible responses is listed in each example.
2
Test Application Commands
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Test Application is a powerful mode, inappropriate use of Test Application MMI
can lead to a permanent hardware failure. Please proceed with extreme caution.
HELP
Syntax:
help –c<command>
Description:
The help command displays a short synopsis of the command, comprising an option list and a brief description.
canbus
Syntax:
Commands for manipulating power supplies, auto-tune cavity combiners and digital power meters
– devices that communicate via the CAN bus – all share a common syntax:
can | canbus –o<object> -c<command> <various parameters depending on command>
The following table provides a quick overview of all commands related to the CAN bus.
Table 2-1 CAN Bus Related Commands
Purpose Add a CAN bus unit to the CAN bus unit mapping list.
Syntax can –oplatform –cadd –t<trackID> -u<unit name>
Table 2-2 Managing the CAN Bus Unit mapping List (Continued)
Commands for adding, deleting and changing CAN bus units
Example > can -oplatform -cadd -tOWK0640099 -upsu2
>
Comment trackID must be in the form AAA99BBBBB, where A denotes a letter, 9 denotes
a digit and B is either a digit or one of the letters B, C, D, F, G, H, J, K, L, M,
N, P, R, S, T, V, W, X, Y, Z. Unit name is one of psuX, dpmX, atccX, where X
denotes a digit between 0 and 3
Purpose Delete a CAN bus unit from the CAN bus unit mapping list.
Syntax can –oplatform –cdel -t<trackID>
Example > can -oplatform -cdel -tCOM0632855
>
Comment trackID must be in the form AAA99BBBBB, where A denotes a letter, 9 denotes
a digit and B is either a digit or one of the letters B, C, D, F, G, H, J, K, L, M,
N, P, R, S, T, V, W, X, Y, Z.
Purpose Change the name (i.e. the position) of a CAN bus unit mapping list.
Syntax can –oplatform –cchg -t<trackID> -u<new unit name>
Example > can -oplatform -cchg -tOWK0640099 -upsu2
>
Comment trackID must be in the form AAA99BBBBB, where A denotes a letter, 9 denotes
a digit and B is either a digit or one of the letters B, C, D, F, G, H, J, K, L, M, N,
P, R, S, T, V, W, X, Y, Z. new unit name is one of psuX, dpmX, atccX, where X
denotes a digit between 0 and 3
The following table lists the names of the variables that can be read from the different
CAN bus units together with examples of their use.
Table 2-3 Variables Readable from the CAN bus Units
Digital Auto-Tune
Power
Power Cavity Example
Supply
Meter Combiner
Device ID Device ID Device ID > can -opsu0 -cread -vdevice
psu0: device id = vendor: 30,
hw_revision: 80, sw_revision: 45
Kit Number Kit Number Kit Number > can -odpm1 -cread –vkit
dpm1: kit number = 0000000000
Vendor Serial Vendor Serial Vendor Serial > can -odpm0 -cread -vserial
Number Number Number dpm0: serial number = FC1061000588
Table 2-3 Variables Readable from the CAN bus Units (Continued)
Digital Auto-Tune
Power
Power Cavity Example
Supply
Meter Combiner
Alarm > can -odpm0 -cread -valarm
dpm0: alarm = (0x0):
Software: Ok
VSWR: Ok
Forward > can -odpm1 -cread -vfwd_pwr
Power dpm1: forward power = 0.00 Watt
Table 2-3 Variables Readable from the CAN bus Units (Continued)
Digital Auto-Tune
Power
Power Cavity Example
Supply
Meter Combiner
PSU > can -opsu0 -cread -vpsu_temp
Temperature psu0: psu temperature = 50.00 Degree
Celcius
Ambient > can -opsu1 -cread -vamb_temp
Temperature psu1: ambient temperature = 30.00 Degree
Celcius
Battery > can -opsu0 -cread -vbat_volt
Voltage psu0: battery voltage = 2.70 Volt
Digital Auto-Tune
Power
Power Cavity Example
Supply
Meter Combiner
Cavity Tune > can -oatcc0 -cwrite -vtune_to -d100
Timeout
VSWR Alarm > can -oatcc0 -cwrite -vvswr_alarm_th
Threshold -d2.0
>
VSWR Alarm > can -odpm1 -cwrite -vvswr_alarm_th
Threshold -d2.0
Comment atcc object is one of atcc0, atcc1, atcc2 and atcc3 cavity number must be between 1 and 4
Reset type cc cannot be sent to the platform object (i.e. cannot be broadcast).
Low-level commands for sending and receiving frames on the CAN bus
Purpose Enable display of received CAN bus frames on the MMI console
Syntax can –oplatform -copen
Example > can -oplatform -copen
CAN-Bus receive channel opened
>
Comment
Purpose Disable display of received CAN bus frames on the MMI console
Syntax can –oplatform -cclose
Example > can -oplatform -cclose
CAN-Bus receive channel closed
>
Comment
Description:
The Site Controller board communicates with power supplies (psu), digital power meters (dpm) and
auto-tune cavity combiners (atcc) via a CAN bus. Power supplies, digital power meters and auto-tune
cavity combiners are units on the CAN bus. In order for the Site Controller to know which units are
mounted in the base station, the user must enter the mounted units in a CAN bus unit mapping list.
The Site Controller uses this list to check that all mounted units register their presence on the CAN
bus at power up. The can command can be used to maintain this mapping list.
The various CAN units have a number of variables (e.g. psu voltage level or dpm power measurements)
which can be read or written. The can command can be used to read and write value in these variables.
For diagnostic purposes thecan command can also be used to send reset frames to units,
send raw data frames to units, display raw data frame received from units and display various
statistics characterizing the performance of the CAN bus.
This command can be used for:
• Displaying the contents of the mapping list
• Adding and deleting CAN bus units (power supplies, digital power meters and
auto-tune cavity combiners) to/from the mapping list
• Changing the position of CAN bus units in the mapping list
• Deleting the entire mapping list
• Reading and writing the values of CAN bus units
• Parking a cavity in an atcc
• Sending reset frames to units
• Sending raw data frames to CAN bus units.
• Displaying raw data frames received from CAN bus units.
Received CAN-Bus frames are not displayed on the console before the user enters a <carriage
return>. One received frame will be displayed for each <carriage return> pressed.
alarm_log
Alarm logging has to be enabled before logging of alarms are possible. To enable alarm
logging, please refer to Test Application Command alarm_log_enable.
Syntax:
al | alarm_log –l<log_type>
Description:
Displays the alarm log contents, this is will include the following: fault (HW), exception (SW), and errors (SW).
Options:
<log_type> A character string representing the alarm category to be displayed. Valid settings:
• fault
• error
• exception
• all
Output:
Exception type:
alarm type=EXCEPTION
time stamp<prd><time_stamp>
record num<prd><record__num>
exception id<prd><excep_id>
severity<prd><excep_severity>
detail 1<prd><detail>
detail 2<prd><detail>
detail 3<prd><detail>
detail 4<prd><detail>
detail 5<prd><detail>
detail 6<prd><detail>
detail 7<prd><detail>
detail 8<prd><detail>
Error type:
alarm type=ERROR
time stamp<prd><time_stamp>
record num<prd><record_num>
error id<prd><error>
description<prd><desc>
Fault type:
alarm type=FAULT
time stamp<prd><time_stamp>
record num<prd><record_num>
fault id<prd><fault_id>
object id<prd><core_object>
severity<prd><fault_severity>
action taken<prd><action_taken>
action recom<prd><action_recomm>
size<prd><user_data_size>
<possible_user_data>
Example:
> al –lfault
alarm type=FAULT
time stamp=0000000565
record num=6
fault id=INDETERMINATE_FAILURE
object id=PLATFORM
severity=CLEARED
action taken=PA_POWER_CUTBACK_CLEAR
action recom=0000000000
size=0x00000001
level2 diagnosis=INDETERMINATE_FAILURE
contributing alarms:
fault id[0]=TX_FWD_PWR_HIGH
object id[0]=CORE_PA1
severity[0]=CLEARED
action taken[0]=PA_POWER_CUTBACK_CLEAR
action recom[0]=0000000000
user data[0]=
>
alarms
Syntax:
Read operations:
alarms –ofault_hndlr
Description:
Displays the current active hardware alarms.
Options:
Output:
> alarms –ofault_hndlr
>
Example:
ACTIVE_FAULT 1<prd><fault_id>
.
.
ACTIVE_FAULT n<prd><fault_id>
alarm_log_clear
Syntax:
Write operations:
alc | alarm_log_clear
Description:
Clears the alarm log contents.
Options:
None
Output:
None
Example:
> alc
>
alarm_log_enable
Syntax:
Read operations:
ale | alarm_log_enable
Write operations:
ale | alarm_log_enable –s<state>
Description:
Controls the alarm logging enable state. If enabled, all unmasked alarm events are logged.
Options:
<state> A character string representing the state of the alarm log feature. Valid settings:
• on
• off
Output:
State<prd><state>
Example:
> ale
State=off
>
> ale –son
>
> ale
State=on
calibration_factor
Syntax:
Read operations:
cf | calibration_factor -o<object>
Write operations:
cf | calibration_factor -o<object> -c<cal_factor_name> -f<cal_factor>
Description:
Sets and reads calibration factor of the Site Controller’s OCXO.
Options:
<object> A character string representing the object assigned to control the calibra-
tion factor. Valid settings: platform
<cal_factor_name> A character string representing the calibration factor identifier. Valid settings: ocxo1
<cal_factor> An interger value representing the calibration factor setting.
Output:
<cal_factor_id 1><prd><cal_factor>
<cal_factor_id 1> A string which identifies the calibration factor. Valid settings: ocxo1
Example:
factory> cf -oplatform
ocxo1=0x64
factory>
factory> cf -oplatform -cocxo1 -f100
factory>
comm_port_parms
Syntax:
Read operations:
cpp | comm_port_parms -o<object> (for serial and lan)
cpp | comm_port_parms -o<object> -c<port> (for switch ports)
Write operations:
cpp | comm_port_parms –o<object> -b<baud> -p<oper_mode> -l<line_mode> (for serial)
cpp | comm_port_parms –o<object> -m<mac_address> -i<ip_address>
-p<oper_mode> -l<line_mode> (for lans)
cpp | comm_port_parms –o<object> -c<port> -p<oper_mode> -l<line_mode> (for switch ports)
Description:
Controls serial communication ports, Ethernet communication ports and Ethernet switch ports settings.
This MMI sets and reads the baud rate and other settings of the Site Controller’s serial communication
ports. It also sets and reads the MAC address, the IP address, duplex mode (line mode), the communication
speed and the loopback mode of the Site Controller CPU Ethernet communication ports. Finally, it sets
and reads duplex mode and communication speed of the Site Controller’s Ethernet switch ports. When
loopback mode is set, “fsd – fru_self_diagnostic” mmi can be used to perform loopback tests.
• For FRUs with only one switch, use front panel switch definitions.
• If cpp mmi used to set loopback test configuration path for lan1 and lan3 objects, it is
required to provide both line_mode=100_base_full_duplex and oper_mode=ext_loopback
parameters on switch1-port0 object. Loopback test will not function correctly
unless full duplex bit is set on switch1-port0.
• If normal mode of operation was not restored on switch1-port0 object, after warm
reboot SC will keep previously set values. In this case fsd mmi command on lan1
and lan3 will report incorrectly current mode as external loopback mode while the
platform software will be configured for internal loopback. Normal functionality
can be restored by setting switch1-port0 to normal mode.
• Platform does not support internal (on MCU level) loopback settings for LAN1 and
LAN3 objects. Cpp mmi for lan1 and lan3 does not provide possibility to set any
other oper_mode except “normal”. Because of this limitation, lan1 and lan3 objects
can not be tested with internal loopback mode on MCU level.
• Line mode settings are not supported for switches and LANs without integrated EPHY. The
command will report error “Invalid argument” while trying to set line mode on lan1, lan3, on
ports 9, 11 of local and remote switches and on ports 20, 22 of local switch1 – back panel.
• IP addresses and MAC addresses written for LANs 1 to 3 are stored in non-volatile
memory. I.e. they will survive a power-down/power-up cycle.
Options:
<object> A character string representing the object assigned to control the communication port. Valid settings:
• lan1,2,3
• serial1,2,4
• switch1(local FP and BP unit as a whole )
• switch2...6 (remote switches)
<baud_rate> A integer value representing the serial port baud rate setting. Valid settings:
9600, 19200 (other values are not supported on SummitSC)
<mac_address> A hexadecimal value representing the station lan port mac address. Valid
settings: any valid MAC address in the form 112233445566
<oper_mode> A character string representing the operational mode setting. Valid settings:
• Normal (normal mode of object operations)
• int_loopback ( not valid for switch ports and LAN1, LAN3)
• ext_loopback (not valid for LAN1 and LAN3)
<line_mode> A character string representing line mode of the operation. Valid settings
(lan and switch objects with integrated ephy):
• 10_base_half_duplex
• 10_base_full_duplex
• 100_base_half_duplex
• 100_base_full_duplex
• 1000_base_half_duplex
• 1000_base_full_duplex
• auto_negotiate
<port> A character string representing the switch port. Valid settings: p0…10 (front panel
switch1 and remote switches), p11…21 (back panel switch1)
For FRUs with only one switch, use front panel switch definitions.
Output:
Lan :
line mode<prd>< mode>
MAC address<prd><mac_address>
IP address<prd><ip_address>
oper mode<prd> <oper_mode>
Serial:
baud<prd><baud_rate>
line mode<prd>< mode>
data bits<prd><data_bits>
stop bits<prd><stop_bits>
parity<prd><parity>
echo mode<prd><echo_mode>
flow control<prd><flow_cntrl>
delimiters<prd><delimiter>
Switch Ports:
port<prd><port>
line mode<prd>< mode>
< mode> A character string representing the line mode of the operation. Valid settings:
• Serial — a character string representing serial line mode of the operation:
half_duplex; full_duplex; Undefined
• Lan and switches — a character string representing ethernet’s mode of the operation:
10_base_half_duplex; 10_base_full_duplex; 100_base_half_duplex; 100_base_full_duplex;
1000_base_half_duplex; 1000_base_full_duplex; auto_negotiate
<mac_address> A character string representing the MAC address of the the station lan port.
Valid settings: any valid MAC address in the form 112233445566
<ip_address> character string representing the ip address of the station lan port. Valid
settings: any valid IP address in the form 111.222.333.444
<data_bits> A integer value representing the number of data bits in the serial transfer. Valid settings: 8
<stop_bits> A integer value representing the number of stop bits in the serial transfer. Valid settings: 1
<parity> A character string representing the parity. Valid settings: none
<echo_mode> A character string representing the echo mode used in the serial transfer. Valid settings: on
<flow_cntrl> A character string representing the flow control used in the serial transfer. Valid settings: none
<delimiter> A integer value representing the number of delimiters used in the serial transfer. Valid settings: 0
Example:
Mapping of objects between TestApp and Platform:
lan1...3 - LAN1…3
Serial1, 2,4 - TTY1, TTY2, TTY4
switch1 - LAN_SWITCH1 (SC front and back panel switches as a whole)
switch2 - LAN_SWITCH2 (remote xhub2)
switch3 - LAN_SWITCH3 (remote xhub3)
switch4 - LAN_SWITCH4 (remote xhub4)
switch5 - LAN_SWITCH5 (remote xhub5)
switch6 - LAN_SWITCH6 (remote xhub6)
Mapping of between TestApp switch ports and Platform ports:
Local front panel switch1 and remote xhub ports
P0 - SWITCH_PORT_1
P1 - SWITCH_PORT_2
P2 - SWITCH_PORT_3
P3 - SWITCH_PORT_4
P4 - SWITCH_PORT_5
P5 - SWITCH_PORT_6
P6 - SWITCH_PORT_7
P7 - SWITCH_PORT_8
P8 - SWITCH_PORT_9 (mii1 no EPHY)
P9 - SWITCH_PORT_10 (Gb1)
P10 - SWITCH_PORT_11 (gmii1 no EPHY)
Local back panel switch ports
P11 - SWITCH_PORT_12
P12 - SWITCH_PORT_13
P13 - SWITCH_PORT_14
P14 - SWITCH_PORT_15
P15 - SWITCH_PORT_16
P16 - SWITCH_PORT_17
P17 - SWITCH_PORT_18
P18 - SWITCH_PORT_19
P19 - SWITCH_PORT_20 (mii1 no EPHY)
P20 - SWITCH_PORT_21 (Gb1)
P21 - SWITCH_PORT_22 (gmii1 no EPHY)
factory> comm_port_parms –olan1
MAC Address=112233445500
IP Address=0.0.0.0
oper mode=normal
factory>
factory> comm_port_parms –oserial1
baud=9600
line mode=full_duplex
data bits=8
stop bits=1
parity=none
echo mode=off
flow control=none
delimiter=0
factory>
factory> comm_port_parms –oswitch1 –cp1
port=1 line mode=10_base_half_duplex
factory>factory> cpp –olan1 –m112233445566 –i111.222.233.244
factory>
factory> cpp –olan2 –l10_base_half_duplex
factory>
factory> cpp –oserial1 –b9600
factory>
To set internal loopback mode on PHY level for lan1 and lan3 loopback tests run:
> cpp –oswitch1 –cp0 –l100_base_full_duplex –pext_loopback
chipset_reg
Syntax:
Read operations:
Command format 1: cr | chipset_reg –o<object> -c<chip_id> [-r<register_id>]
Command format 2: cr | chipset_reg –o<object> -c<chip_id> -p<page> -f<offset> -s<size>
Write operations:
Command format 1: cr | chipset_reg –o<object> -c<chip_id> -r<register_id> -v<value>
Command format 2: cr | chipset_reg –o<object> -c<chip_id> -p<page> -f<offset> [-s<size>] –v<value>
Description:
Provides access to the registers of several devices on the Site Controller card. It sets and reads registers of
the alarm card, the real time clock, the Ethernet switch and the standalone Ethernet PHY.
Options:
<object> A character string representing the object assigned to control the chipset register. Valid settings:
• controller
• switch1 (local)
• switch2..6 (remote)
• ps
• ps1..6
• ac1
<chip_id> An integer value representing the hardware integrated circuit containing the register. Valid settings:
• ac_reg (alarm card registry)
• rtc_reg (real time clock registry)
• fp (front panel switch)
• bp (back panel switch)
• phy1
• ps_dac1
• ps_dac2
• ocxo_dac
no validation is done to the size entered therefore the user should be careful with the
usage of this parameter as he could overwrite important data.
<value> A hexadecimal value to be written.
Output:
Format 1 read operation output (cr –o<object> -c<chip_id> [-r<register_id>])
<chip_id> Register <reg_id 1><prd><value>
.
.
<chip_id> Register <reg_id n><prd><value>
: If the register ID it is not specified, the content of all registers of the selected chip_id will
be displayed. Otherwise, only the selected register’s value will be shown.
Format 2 read operation output (cr –o<object> -c<chip_id> -p<page> -f<offset> -s<size>)
Object<prd><object>
Chip_id<prd><chip_id>
Page<prd><page>
Offset<prd><offset>
Size<prd><size>
Value<prd><value>
The displayed <size>, refers to the actual read size, not to the requested one.
Example:
> cr –ocontroller –crtc_reg
rtc_reg Register 0x00=0x00000023
rtc_reg Register 0x01=0x00000024
rtc_reg Register 0x02=0x000000a2
rtc_reg Register 0x03=0x00000001
rtc_reg Register 0x04=0x00000003
rtc_reg Register 0x05=0x00000001
rtc_reg Register 0x06=0x00000071
rtc_reg Register 0x07=0x000000b7
rtc_reg Register 0x08=0x000000da
rtc_reg Register 0x09=0x000000fc
rtc_reg Register 0x0a=0x000000aa
rtc_reg Register 0x0b=0x000000bf
rtc_reg Register 0x0c=0x00000000
rtc_reg Register 0x0d=0x000000f3
rtc_reg Register 0x0e=0x00000006
rtc_reg Register 0x0f=0x000000ef
rtc_reg Register 0x10=0x00000010
rtc_reg Register 0x11=0x000000fa
rtc_reg Register 0x12=0x00000008
rtc_reg Register 0x13=0x000000ff
rtc_reg Register 0x14=0x00000001
rtc_reg Register 0x15=0x000000fe
rtc_reg Register 0x16=0x00000000
rtc_reg Register 0x17=0x000000ef
rtc_reg Register 0x18=0x00000000
rtc_reg Register 0x19=0x0000005f
rtc_reg Register 0x1a=0x00000000
rtc_reg Register 0x1b=0x0000005f
rtc_reg Register 0x1c=0x00000000
rtc_reg Register 0x1d=0x0000005f
rtc_reg Register 0x1e=0x00000000
rtc_reg Register 0x1f=0x000000bf
rtc_reg Register 0x20=0x00000080
rtc_reg Register 0x21=0x000000f7
rtc_reg Register 0x22=0x0000000e
rtc_reg Register 0x23=0x000000bf
rtc_reg Register 0x24=0x00000000
rtc_reg Register 0x25=0x000000ba
rtc_reg Register 0x26=0x00000080
rtc_reg Register 0x27=0x000000fe
rtc_reg Register 0x28=0x00000000
rtc_reg Register 0x29=0x00000073
rtc_reg Register 0x2a=0x000000c0
rtc_reg Register 0x2b=0x000000ef
rtc_reg Register 0x2c=0x00000000
rtc_reg Register 0x2d=0x0000003b
rtc_reg Register 0x2e=0x00000000
rtc_reg Register 0x2f=0x000000ff
rtc_reg Register 0x30=0x00000000
rtc_reg Register 0x31=0x000000ba
rtc_reg Register 0x32=0x00000001
rtc_reg Register 0x33=0x000000fe
rtc_reg Register 0x34=0x00000000
rtc_reg Register 0x35=0x000000fb
rtc_reg Register 0x36=0x00000040
digital_analog_converter
Syntax:
Write operations: dac | digital_analog_converter –o<object> -c<chip_id> -r<reg_id> -v<value>
Description:
Writes the power supply digital to analog converters.
Options:
<object> An character string representing the object assigned to the DAC. Valid settings: ps_loc
<chip_id> An character string representing the chip_id inside the object. Valid settings: ps_dac1; ps_dac2
<reg_id> An integer value representing the reg_id inside the chip. Valid settings: 0..7
<value> A integer value representing the value to write in the DAC.
Output:
N/A
Example:
> dac -ops_loc -cps_dac1 -r0 -v128
>
> dac -ops_loc -cps_dac2 -r7 -v128
>
e1_external_loopback
Syntax:
Write operations:
e1el | e1_external_loopback –o<object> -d<deviceidd> -c<command>
e1el | e1_external_loopback –o<object> -d<deviceidd> -c<command> -n<no. of
packets> (command = senddata)
Description:
Opens and closes E1 links and sends and receives HDLC packets over those links.
Options:
<object> A character string representing the object owning the E1 interface. Valid settings: platform
<deviceid> A character string representing E1 interface. Valid settings: e1a; e1b
senddata (unsuccessful):
The <deviceid> HDLC pkt transmission/reception FAILED
Number of pkt sent=<no of packets sent>
Number of pkt recv=<no of packets received>
fru_configuration_parameter
Syntax:
Read operations:
fcp | fru_configuration_parameter –o<object> -p<parameterid>
Write operations:
fcp | fru_configuration_parameter –o<object> -p<parameterid> -v<value>
Description:
Provides access to configuration parameters which are stored on the non-volatile memory of Site
Controller’s EEPROM, local power supply,remote power supplies and XHUBs.
Options:
<object> A character string representing the object assigned to the fault management
monitoring control. Valid settings:
• control
• ps
• ps1..6
• xhub2..6
• encryption
• plat_eeprom
Example:
> fcp –ocontrol –pmanuf_loc
manuf_loc=IL02
> > fcp –ocontrol –pmanuf_loc –vIL03
>
> fcp –oencryption –pone_wire_device_info
Family Code = 0x23
HW Identifier = 0xa5f22e000000
CRC = 0x5f
> fcp –oencryption –pone_wire_device_info –v0
Platform Failed
>
fault_management_enable
Syntax:
Read operations:
fme | fault_management_enable –o<object>
Write operations:
fme | fault_management_enable –o<object> -s<state>
Description:
Controls the hardware fault management enabled state.
Options:
<object> A character string representing the object assigned to the fault management
monitoring control. Valid settings: fault_hndlr
<state> A character string representing the state of the fault management feature. Valid settings: on; off
Output:
Mode<prd><state>
Example:
> fme –ofault_hndlr –son
>
> fme –ofault_hndlr
Mode=on
>
fault_management_interval
Syntax:
Read operations:
fmi | fault_management_interval –o<object>
Write operations:
fmi | fault_management_interval –o<object> -s<scaling_factor>
Description:
Controls the hardware fault management periodic monitoring interval.
Options:
<object> A character string representing the object assigned to the fault management
monitoring control. Valid settings: fault_hndlr
<scaling_factor> A float value representing the periodic monitoring interval scaling
factor. Valid settings: 0.2 Up to 10
Output:
Scaling factor<prd><scaling_factor>
Example:
> fmi –ofault_hndlr –s3
>
> fmi –ofault_hndlr
Scaling factor=3
>
e1_frm_config
Syntax:
Read operations:
frm | e1_frm_config –o<object> -d<deviceidd> -c<command>
Write operations:
frm | e1_frm_config –o<object> -d<deviceidd> -c<command>
Description:
Reads and writes the registers in the E1 framer chip.
Options:
<object> A character string representing the object owning the E1 interface. Valid settings: platform
<deviceid> A character string representing E1 interface or framer chip. Valid settings: e1a; e1b; frm
<command> A character string representing the command to be executed. Valid settings – read commands:
• status deviceid = frm, reports the state of the framer chip (ALIVE or DEAD)
• lb_status deviceid = e1a or e1b, reports the loopback state
• version deviceid = frm, reports the version of the framer chip firmware
Valid settings – write commands:
• reset deviceid = frm, resets the framer chip
• int_enable deviceid = e1a or e1b
• int_disable deviceid = e1a or e1b
• activate_line deviceid = e1a or e1b
• deactivate_line deviceid = e1a or e1b
• rst_all_lb deviceid = e1a or e1b
• idle deviceid = e1a or e1b
• rst_idle deviceid = e1a or e1b
• local deviceid = e1a or e1b
• rst_local deviceid = e1a or e1b
Example:
> frm -oplatform -dfrm -cstatus
The Framer is ALIVE
> > frm -oplatform -de1a -clb_status
All loopbacks are DISABLED on e1a
>
> frm -oplatform -dfrm -cversion
Framer SW Version=5
>
> frm -oplatform -de1a -clocal
> frm -oplatform -de1a -clb_status
Loopback is ENABLED on e1a
fru_self_diagnostic
Syntax:
Read operations:
fsd | fru_self_diagnostic -o<object> -t<test>
Description:Initiates a different, including loopback, tests on the passed object. It returns result string
” pass” or “fail”. The loopback test consist of verifying data integrity for a given transmit-receive loop.
The type of loopback on specified object (internal or external) depends on specific objects configurations.
This can be done with cpp MMI command. The user can also use cr mmi to provide test specific switch
configuration. For external loopback the test requires external dungle. Correct loopback functionality for
lan1…3 objects should be provided with unmanaged switch mode as explained below.
Options:
<object> A character string representing the object under the test. Valid settings:
• lan1...3
• serial1,2,4
• uhso1
• ac1…ac12 (ac1, ac3, ac5, ac7, ac9, ac11 – integrated alarm cards; ac2, ac4,
ac6, ac8, ac10, ac12 – external alarm cards)
<test> loopback
Output:
test<prd><test_status>
Example:
Mapping of objects between TestApp and Platform
lan1...3 - LAN1…3
serial1, 2,4 - TTY1, TTY2, TTY4
uhso1 - CORE_UHSO (Rubidium)
ac1 - ALARM_CARD1 (integrated SC alarm card)
ac2 - ALARM_CARD2 (external SC alarm card)
ac3 - ALARM_CARD3 (xhub 2 integrated alarm card)
ac4 - ALARM_CARD4 (xhub 2 external alarm card)
ac5 - ALARM_CARD5 (xhub 3 integrated alarm card)
ac6 - ALARM_CARD6 (xhub 3 external alarm card)
ac7 - ALARM_CARD7 (xhub 4 integrated alarm card)
ac8 - ALARM_CARD8 (xhub 4 external alarm card)
ac9 - ALARM_CARD9 (xhub 5 integrated alarm card)
ac10 - ALARM_CARD10 (xhub 5 external alarm card)
ac11 - ALARM_CARD11 (xhub 6 integrated alarm card)
ac12 - ALARM_CARD12 (xhub 6 external alarm card)
SC board reset and configuration of unmanaged mode for front and back panel switches:
reset -oswitch1
cr -oswitch1 -cfp -p00 -f1E -s1 -vFB
cr -oswitch1 -cfp -p00 -f00 -s1 -v00
cr -oswitch1 -cfp -p00 -f01 -s1 -v00
cr -oswitch1 -cfp -p00 -f02 -s1 -v00
cr -oswitch1 -cfp -p00 -f03 -s1 -v00
cr -oswitch1 -cfp -p00 -f04 -s1 -v00
cr -oswitch1 -cfp -p00 -f05 -s1 -v00
cr -oswitch1 -cfp -p00 -f06 -s1 -v00
cr -oswitch1 -cfp -p00 -f07 -s1 -v00
cr -oswitch1 -cfp -p00 -f08 -s1 -v00
cr -oswitch1 -cfp -p00 -f0B -s1 -v06
cr -oswitch1 -cfp -p00 -f1C -s1 -v00
cr -oswitch1 -cfp -p00 -f1D -s1 -v00
cr -oswitch1 -cbp -p00 -f00 -s1 -v00
cr -oswitch1 -cbp -p00 -f01 -s1 -v00
cr -oswitch1 -cbp -p00 -f02 -s1 -v00
cr -oswitch1 -cbp -p00 -f03 -s1 -v00
cr -oswitch1 -cbp -p00 -f04 -s1 -v00
cr -oswitch1 -cbp -p00 -f05 -s1 -v00
cr -oswitch1 -cbp -p00 -f06 -s1 -v00
cr -oswitch1 -cbp -p00 -f07 -s1 -v00
cr -oswitch1 -cbp -p00 -f08 -s1 -v00
cr -oswitch1 -cbp -p00 -f0B -s1 -v06
cr -oswitch1 -cbp -p00 -f1C -s1 -v00
cr -oswitch1 -cbp -p00 -f1D -s1 -v00
Default external loopback on serial4 object with external test path set to EAC:
> fsd -oserial4 -tloopback
You must place a dungle on the port to test now.
-----Press the SPACE bar to continue-----
Starting test...
test=pass
>
Default external loopback on ac2 object with serial 4 used as a loopback packets source and
external test path set to EAC (equivalent to previous step):
> fsd –oac2 -tloopback
You must place a dungle on the port to test now.
-----Press the SPACE bar to continue-----
Starting test...
test=pass
>
Internal loopback on lan1 object with lan1 used as a loopback packets source and external
loopback test path set on switch1-port0 ephy:
> cpp –oswitch1 –cp0 –l100_base_full_duplex –pext_loopback
> fsd -olan1 -tloopback
INTERNAL LOOPBACK MODE; NO DUNGLE ON THE PORT
-----Press the SPACE bar to continue-----
Starting test...
test=pass
>
Internal loopback on lan3 object with lan3 used as a loopback packets source and external
loopback test path set on switch1-port0 ephy during previous step:
> fsd -olan3 -tloopback
INTERNAL LOOPBACK MODE; NO DUNGLE ON THE PORT
-----Press the SPACE bar to continue-----
Starting test...
test=pass
>
External loopback on lan1 object with lan1 used as a loopback packets source and external
loopback test path provided by external dungle:
> cpp –oswitch1 –cp0 –pnormal
> fsd -olan1 -tloopback
You must place a dungle on the port to test now.
-----Press the SPACE bar to continue-----
Starting test...
test=pass
>
External loopback on lan3 object with lan3 used as a loopback packets source and external
loopback test path provided by external dungle:
> cpp –olan3 –pnormal
> fsd –olan3 -tloopback
You must place a dungle on the port to test now.
-----Press the SPACE bar to continue-----
Starting test...
test=pass
>
External loopback on lan2 object with lan2 used as a loopback packets source and external
loopback test path provided by external dungle:
> cpp –olan2 –pnormal
> fsd –olan2 -tloopback
You must place a dungle on the port to test now.
-----Press the SPACE bar to continue-----
Starting test...
test=pass
>
Internal loopback on lan2 object with lan2 used as a loopback packets source and internal
loopback test path set on lan2 MCU level:
> cpp –olan2 –pint_loopback
> fsd –olan2 -tloopback
INTERNAL LOOPBACK MODE; NO DUNGLE ON THE PORT
-----Press the SPACE bar to continue-----
Starting test...
test=pass
>
Internal loopback on lan2 object with lan2 used as a loopback packets source and external
loopback test path set on the lan2 ephy:
> cpp –olan2 –pext_loopback
> fsd –olan2 -tloopback
INTERNAL LOOPBACK MODE; NO DUNGLE ON THE PORT
-----Press the SPACE bar to continue-----
Starting test...
test=pass
>
firmware_version
Syntax:
Read operations:
fv | firmware_version –o<object>
Description:
Displays the run-time firmware versions.
Options:
<object> A character string representing the object assigned to the firmware version
query control. Valid settings: platform
Output:
Multiple:
Test Application Version<prd><testapp_version>
OS Version<prd><os_version>
Core Software Ver<prd><core_version>
BootFlashEntry[0]<prd>ID: <entry_id>, Ver: <version>, Status: <status>
.
.
BootFlashEntry[n=valid entries]<prd>ID: <entry_id>, Ver:
<version>, Status: <status>
Boot Sequencer Version<prd><boot_seq_version>
FPGA Version<prd><fpga_version>
gps
Syntax:
Read operations:
gps –o<object> -c<command>
gps –o<object> -c<command> -s<time_type> (command = time)
Write operations:
gps –o<object> -c<command> -a<altitude> -g<longitude> -l<latitude> (command = location)
gps –o<object> -c<command> -s<time type> -d<day> -m<month> -y<year> -t<time> (command = time)
gps –o<object> -c<command> -k<angle> (command = mask)
Description:
Configures the GPS receiver and displays its status and current location information.
Options:
<object> A character string representing the object to the GPS. Valid settings: platform
<command> A character string representing the command to be executed. Valid settings:
• status (read-only)
• location
• time
• mask
<time_type> Select either the GPS time or the UTC time calculated by the GPS. Valid
settings: GPS (Default value), UTC
<altitude> New altitude provided to the GPS as initial setting, expressed in meters with a
resolution of 0.01. Valid settings: -1000.00..18288.00.
<longitude> New longitude provided to the GPS as initial setting, expressed in degrees
with a decimal part. Valid settings: -180.000..180.000
<latitude> New latitude provided to the GPS as initial setting, expressed in degrees
with a decimal part. Valid settings: -90.000..90.000
<day> The day to provide to the GPS. Valid settings: 1..31
<month> The month to provide to the GPS. Valid settings: 1..12
<year> The 4 digits year to provide to the GPS Valid settings: 2000..9999
<time> The current time to provide to provide to the GPS in the hh:mm:ss format.
Valid settings: 00:00:00..23:59:59
<angle> Satellite mask angle in degrees. Valid settings: 0..89 (Zero indicate no mask)
Output:
Status:
Model Number<prd><model_number>
Lock State<prd><lock_state>
Tracking State<prd><tracking state>
Longitude<prd><gpsr_longitude>
Latitude<prd><gpsr_latitude>
Altitude<prd><gpsr_altitude>
DOP<prd><dilution_of_precision>
Number of visible satellites<prd><gpsr_visible_sat>
Number of tracked satellites<prd><gpsr_tracked_sat>
Channel1 SVID<prd><Satellite ID>
Mode<prd><tracking mode>
Strength<prd><signal strength>
.
.
.
Channel12
SVID<prd><Satellite ID>
Mode<prd><tracking mode>
Strength<prd><signal strength>
location:
Latitude<prd><value>
Longitude<prd><value>
Altitude<prd><value>
time:
gps <time_ type><prd><month>/<day>/<year> <time>
mask:
gps mask angle<prd><mask angle>
<model_number> GPS model number provided by the device. Valid settings: GPS module specific string
<lock_state> Indicate if the timing reference of the GPS is locked and usable. Valid settings: locked not locked.
<tracking state> Current tracking state of the GPS receiver. Valid settings:
• No FIX
• Site Survey
• Position Hold
• 2D FIX
• 3D FIX
<gpsr_longitude> Current longitude as determined by the GPS receiver or the value used to
preset the longitude. Valid settings: -180.000..180.000
<gpsr_latitude> Current latitude as determined by the GPS receiver or the value used to
preset the latitude. Valid settings: -90.000..90.000
<gpsr_altitude> Current altitude as determined by the GPS receiver or the value used to preset the
altitude in meter (2 digits after the dot) Valid settings: -1000.00..18288.00
<dilution_of_precision> Value of the dilution of precision. Valid settings: 0.0..99.9
<gpsr_visible_sat> Number of satellites visible to the GPS unit. Valid settings: 0..12
<gpsr_tracked_sat> Number of tracked satellites by the GPS unit. Valid settings: 0..12
<Satellite ID> SVID of the satellite tracked on this channel. Valid settings: GPS module specific string
<tracking mode> Current tracking mode of this channel Valid settings:
• code search
• code acquire
• AGC set
• preq acquire
• bit sync detect
• message sync detect
• satellite time available
• ephemeris acquire
• Available for position
<signal strength> Signal strength received by this channel. Valid settings: GPS module specific string.
<mask angle> Specifies the desired satellite mask angle in degrees. Valid settings: 0..89
Example:
> gps –oplatform –cstatus
Model Number=P273T12T11
Lock State=not locked
Tracking State=GPSR is not tracking any satellites
Longitude=-180.00 degrees
Latitude=-90.00 degrees Altitude=8672.00 m
igps
Syntax:
Read operations:
gps –o<object> -c<command>
gps –o<object> -c<command> -s<time_type> (command = time)
Write operations:
gps –o<object> -c<command> -a<altitude> -g<longitude> -l<latitude> (command = location)
gps –o<object> -c<command> -s<time type> -d<day> -m<month> -y<year> -t<time> (command = time)
gps –o<object> -c<command> -k<angle> (command = mask)
Description:
Configures the internal GPS receiver and displays its status and current location information.
The first request to get the time will return the value 0/0/0 0:00:00. Subsequent
requests will return the correct time.
Options:
<object> A character string representing the object to the GPS. Valid settings: platform
<command> A character string representing the command to be executed. Valid settings:
• status (read-only)
• location
• time
• mask
<time_type> Select either the GPS time or the UTC time calculated by the GPS. Valid
settings: GPS (Default value); UTC
<altitude> New altitude provided to the GPS as initial setting, expressed in meters with a
resolution of 0.01. Valid settings: -1000.00..18288.00
<longitude> New longitude provided to the GPS as initial setting, expressed in degrees
with a decimal part. Valid settings: -180.000..180.000
<latitude> New latitude provided to the GPS as initial setting, expressed in degrees
with a decimal part. Valid settings: -90.000..90.000
<day> The day to provide to the GPS. Valid settings: 1..31
Location:
Latitude<prd><value>
Longitude<prd><value>
Altitude<prd><value>
time:
gps <time_ type><prd><month>/<day>/<year> <time>
mask:
gps mask angle<prd><mask angle>
<model_number> GPS model number provided by the device. Valid settings: GPS module specific string
<lock_state> Indicate if the timing reference of the GPS is locked and usable. Valid settings: locked; not locked
<tracking state> Current tracking state of the GPS receiver Valid settings:
• No FIX
• Site Survey
• Position Hold
• 2D FIX
• 3D FIX
<gpsr_longitude> Current longitude as determined by the GPS receiver or the value used to
preset the longitude. Valid settings: -180.000..180.000
<gpsr_latitude> Current latitude as determined by the GPS receiver or the value used to
preset the latitude. Valid settings: -90.000..90.000
<gpsr_altitude> Current altitude as determined by the GPS receiver or the value used to preset the
altitude in meter (2 digits after the dot). Valid settings: -1000.00..18288.00
<dilution_of_precision> Value of the dilution of precision. Valid settings: 0.0..99.9
<gpsr_visible_sat> Number of satellites visible to the GPS unit. Valid settings: 0..12
<gpsr_tracked_sat> Number of tracked satellites by the GPS unit. Valid settings: 0..12
<Satellite ID> SVID of the satellite tracked on this channel. Valid settings: GPS module specific string.
<tracking mode> Current tracking mode of this channel. Valid settings:
• code search
• code acquire
• AGC set
• preq acquire
• bit sync detect
• message sync detect
• satellite time available
• ephemeris acquire
• Available for position
<signal strength> Signal strength received by this channel. Valid settings: GPS module specific string.
<mask angle> Specifies the desired satellite mask angle in degrees. Valid settings: 0..89
Example:
> igps -oplatform -cstatus
Lock State=not locked
Tracking State= Longitude= 0.00 degrees
Latitude= 0.00 degrees
Altitude= 0.00 m
DOP=0.0
Number of visible satellites= 3
Number of tracked satellites= 2
Channel 1
SVID= 14
mode=code search
strength=47.60 dB Hz
Channel 2
SVID= 17
mode=preq acquire
strength=50.10 dB Hz
Channel 3
SVID= 24
mode=code search
strength=49.50 dB Hz
Channel 4 SVID= 3
mode=preq acquire
strength=47.00 dB Hz
Channel 5
SVID= 5
mode=code search
strength=27.20 dB Hz
Channel 6
SVID= 1
mode=code search
strength= 0.00 dB Hz
Channel 7
SVID= 1
mode=code search
strength= 0.00 dB Hz
Channel 8
SVID= 1
mode=code search
strength= 0.00 dB Hz
Channel 9
SVID= 1
mode=code search
strength= 0.00 dB Hz
Channel 10
SVID= 1
mode=code search
strength= 0.00 dB Hz
Channel 11
SVID= 1
mode=code search
strength= 0.00 dB Hz
Channel 12
SVID= 1
mode=code search
strength= 0.00 dB Hz
>
> gps –oplatform –cmask
gps mask angle=89
>
> gps –oplatform –cmask –k89
>
> gps –oplatform –ctime –sUTC
gps UTC=2/1/2004 14:01:05
>
> gps –oplatform –clocation –a18288.00 –g180.00 –l90.00
>
> gps –oplatform –ctime –sUTC –d1 –m2 –y2004 –t14:01:01
>
kit_number
Syntax:
Read operations:
kn | kit_number –o<object>
Write operations:
kn | kit_number -o<object> -s<kit_number>
Description:
Controls the FRU kit number setting.
Options:
<object> A character string representing the object assigned to control the FRU kit number. Valid settings:
• control
• ps
• ps1..6
• xhub2..6
Example:
> kn –ocontrol –s25
> kn –ocontrol
kit_number=25
led_config
Syntax:
Read operations:
lc| led_config –o<object> -l<led_id>
Write operations:
lc | led_config -o<object> -l<led_id> -s<state> -r<rate> -d<duty> -c<color>
Description:
Controls the platform LED configuration. This command offers enhanced capability over the led command.
Table 2-10 lc MMI Objects, led_id and LED Color State Mapping
lc MMI can’t set the remote fan leds when the fan is off.
Options:
<object> A character string representing the object assigned to control the led’s. Valid settings:
• ps, ps2...6
• fan,fan2...6
• xhub2…6
• controller
Example:
>lc -ops -lfan_fail -sblink -d25 -rvslow -ccolor1
> lc -ops -lfan_fail
fan_fail
state<prd>blink
rate<prd>vslow
duty<prd>25
color<prd>color1
>
led
Syntax:
Read operations:
led -o<object>
Write operations:
led -o<object> -l<led_pattern>
Description:
Controls the front-panel LEDs. This MMI turns off a specified front-panel LED or turns it on to a specified color.
Options:
<object> A character string representing the object assigned to control the led’s. Valid settings: platform.
<led_pattern> A left justified hexadecimal value representing the front panel led pattern setting. Valid led_ids:
• cntrl_01, cntrl_02, cntrl_03, cntrl_04, cntrl_05, cntrl_06.
• The LED pattern is represented as an unsigned int. Each LED gets two bits.
The bit val¬ues are defined as follows: 00: LED is off; 01: LED is colour
1; 10: LED is colour 2; 11: LED is colour 3;
• The pattern should be right justified with the least significant bits corresponding to the
lowest or rightmost (physical location of front panel) LED and the most significant bits
representing the top or leftmost (physical location on front panel) LED.
Output:
Led_pattern<prd><led_pattern>
Example:
> led -oplatform
led_pattern=0000
>
>led -oplatform -l3cc
>
load
Syntax:
Write Operations:
load –m<method> -h<host_ip> -p<path/filename> -t<target>
Description:
Downloads a hex-file (also known as an srec-file) from a TFTP server and programs it into the flash memory.
The TFTP server must be connected via a LAN to the redundant Site Controller Ethernet Port.
Options:
<method> A character string representing the file download protocol. Valid settings: tftp
<host_ip> A character string representing the standard IP formatted address of the host to download
from. Valid settings: any valid IP address in the form 111.222.333.444
<path/filename> A character string representing the path and filename of the file to be downloaded.
Valid settings: any valid path and S-Record filename.
<target> A character string representing the location where the file will be downloaded. Valid settings: flash
Output:
Downloading hex file from TFTP server...
<num_received_pkts> 512-byte packets (<num_received_bytes>) received
Processing S records...
<num_records> records processed
Programming block 1 of 1 (offset = <address>, size(bytes) = <size>)
Please wait! This may take up to <programming_duration>
<num_received_pkts> A decimal integer value representing the number of TFTP packets received.
<num_received_bytes> A decimal integer value representing the number of bytes received.
<num_records> A decimal integer value representing the number of S-Records processed.
<address> A hexadecimal integer value representing the address in the flash memory where
the programming starts. The value is relative to the start of the flash memory chip, which
in this version of the Test Application is 0xFE000000.
<size> A decimal integer value representing the number of bytes programmed.
<programming_duration> Decimal integer values representing time it will take to program
the flash memory expressed in minutes and seconds.
In case hex file is larger than 16 Mbytes (16777216 bytes):
> load -mtftp -h169.254.24.57 -pTSC_RLJ_TESTAPP_20_APR_06_just_over_16MB.hex
-tflash
Downloading hex file from TFTP server...
32769 512-byte packets (16777218 bytes) received - downloading failed.
TFTP file exceeds maximum size of 16777216 bytes
>
Example:
> load -mtftp -h169.254.24.57 -pTSC_RLJ_TESTAPP_20_APR_06_b_B.tmp -tflash
Downloading hex file from TFTP server...
17444 512-byte packets (8931090 bytes) received
Processing S records...
159495 records processed
Programming block 1 of 1 (offset = 0x1740000, size(bytes) = 3189584)
Please wait! This may take up to 9 minutes and 39 seconds
>
login
Syntax:
Write operations:
login –u<user_id>
Description:
Allows the user to login as one of valid users (developer, factory or field). Each user type is giving
access to specific set of MMIs commands and their access rights (read and/or write).
Options:
user_id> A character string representing the user id to be logged in as. Valid settings:
• field
• factory
• dev
Output:
password:
Example:
login –ufactory
factory>
logout
Syntax:
Operations:
logout
Description:
Allows the user to log out of the current MMI command access level.
Options:
N/A
Output:
N/A
Example:
factory> logout
>
lrr - last_reset_reason
Syntax:
Read operations:
lrr | last_reset_reason -o<object>
Description:
Gives the reason for which a reset last occurred on the Site Controller card.
Options:
<object> A character string representing the object to access for the last reason. Valid settings: platform.
Output:
Last reset reason<prd><last_reset>
< last_reset > A string which identifies the reason that caused the last reset. Valid settings:
• GS_RESET_BUTTONS -> Push-button
• GS_RESET_SOFTWARE -> Software Request
• GS_RESET_POWERUP -> Power-On
• GS_RESET_HOST -> Host Request
• HOST_SOFT_RESET
• GS_RESET_WDG -> watchdog reset
Example:
> lrr -oplatform
last reset reason:=GS_RESET_POWERUP -> Power-On
>
memory
Syntax:
Read operations:
memory -o<object> -f<offset> -l<length> -w<width>
Write operations:
memory -o<object> -f<offset> -l<length> -v<value>
Description:
Provides the user a means to read and write in volatile and non-volatile memory space contents.
Operations can be performed in various word sizes and length.
• User should always write to the reserved user section for objects spd_eeprom and
boot_eeprom, the valid offset range of spd_eeprom is from 0x80 to 0x100 and
boot_eeprom offset range is from 0x1f00 to 0x1fff.
• Request to display the first 8 bytes of RTC RAM is provided by CR MMI.
Options:
<object> A character string representing the memory object. Valid settings:
• mass_store1
• flash0
• address (for peek and poke operations)
• rtc_ram
• plat_eeprom (for 1-wire memory in the backplane)
• encryption (for 1-wire protection memory in the board)
• boot_eeprom
• spd_eeprom
<offset> A hexadecimal value representing the starting address of the memory block.
Offset is a virtual offset from the start of a memory region/device. It may/ may
not map directly to a physical memory address.
<length> A hexadecimal value representing the length of the memory block.
: length will be restricted to device/region specific limitations such as device size, block
size, etc.. For Read operations, <length> indicates the number of bytes to be read as per the
following formula: (length*width)/8 is equal to the nb of bytes read. For Write operations,
<length> is optional with a default value of 1, as in one of<value>. Thus, the number of
bytes to write is determined by Test Application using the following formula: bytes =
<length> *sizeof (<value>). This also implies that if <length> is greater than 1, the<value>
is repeated successively in memory <length> times in the write data buffer.
<width> An integer value representing the block size of the data. For Read Operations,
this parameter is optional with the default being 32. For Write Operations, It’s not
applicable (not supported). Valid Settings: 8, 16, 32, 64
memory_parameters
Syntax:
Read operations:
mp | memory_parameters -o<object>
Write operations:
mp | memory_parameters -o<object> -c<write_blocking_cycles> -d<write_block-
ing_duration> -e<erase_blocking_state>
Description:
Controls the memory access operational parameter setting.
Options:
<object> A character string representing the object assigned to control the memory
parameters. Valid settings: compact_flash; flash.
<write_blocking_cycles> An integer value representing the number of write cycles between blocking
states during all write operations. Valid settings: any positive integer.
A value of 0 results in blocking only if there are other tasks of the same priority ready to
run. Busy looping will be used if no other same priority tasks are ready.
<erase_blocking_state> A character string representing the state of erase blocking. Valid settings: on; off
>
> mp -oflash -c1 -d2 –eon
>
> mp -oflash
Write Cycles Between Blocking=1
Write Blocking Duration=2
Erase Blocking State=on
>
ping
Syntax:
Read operations:
ping -h<host_ip>
Description:
Executes the IP network ping feature.
Options:
<host_ip> A character string representing the host IP address to ping. Valid settings:
any valid IP address in the form 111.222.333.444
Output:
32 bytes received from <ip_address>:icmp_seq = 1
.
.
32 bytes received from <ip_address>:icmp_seq = 4
Packets Transmitted<prd><tx_packets>
Packets Received<prd><rx_packets>
Packet Loss %<prd><loss>
Example:
Success in finding the machine on the lan:
> cpp –olan2 –i192.168.2.58
> ping -h192.168.2.153
32 bytes received from 192.168.2.153:icmp_seq = 0
32 bytes received from 192.168.2.153:icmp_seq = 1
32 bytes received from 192.168.2.153:icmp_seq = 2
32 bytes received from 192.168.2.153:icmp_seq = 3
Packets Transmitted=4
Packets Received=4
Packet Loss %=0.000000
>
platform_number
Syntax:
Read operations:
pn | platform_number -o<object>
Description:
Displays the platform number setting.
Options:
<object> A character string representing the object assigned to control the platform
number query. Valid settings: platform.
Output:
Controller platform id<prd><Control data>
<Control data> A character string representing the platform number setting of the controller
board. This includes both numeric and character descriptions. Undefined controller in
the case of an invalid or unrecognized configuration.
Example:
> pn –oplatform
Controller platform id=8 Summit Site Controller MPC8560 based
>
reset
Syntax:
Write operations:
reset -o<object>
Description:
Forces the hard or soft reset of Site Controller board.
Options:
<object> A character string representing the object assigned to control the reset feature. Valid settings:
• platform (hard reset of the Site Controller board)
• control (soft reset of the Site Controller board)
• xhub2..6
• switch1
• peer1..36
Output:
N/A
Example:
> reset -oxhub2
>
> reset -oplatform
revision_number
Syntax:
Read operations:
rn | revision_number -o<object>
Write operations:
rn | revision_number -o<object> -s<string>
Description:
Controls the FRU revision number setting.
Options:
<object> A character string representing the object assigned to control the revi-
sion number setting. Valid settings:
• control
• ps
• ps1..6
• xhub2...6
reference_source
Syntax:
Read operations:
rs | reference_source -o<object>
Write operations:
rs | reference_source -o<object> -s<source>
Description:
Selects the frequency reference source or gets the current selection.
Options:
<object> A character string representing the object to access for the frequency ref-
erence. Valid settings: platform.
<source> A character string representing the source of the frequency reference. Valid settings:
• ext_ref
• rubidium
• redundant_sc
• fp_cal_port
• int_ref (read only, cannot be set)
Output:
Reference Source<prd><source>
Example:
> rs -oplatform
Reference Source=int_ref
>
> reference_source -oplatform -sext_ref
>
real_time_clock
Syntax:
Read operations:
rtc | real_time_clock -o<object>
Write operations:
rtc | real_time_clock -o<object> -t<time>
Description:
Sets and gets time of the real time clock. Time is given in number of seconds since 1st January 1970.
Options:
<object> A character string representing the object assigned to control the real time
clock setting. Valid settings: rt_clock.
<time> An integer value representing the time in seconds (UNIX epoch time: sec-
onds since midnight 1970 Jan 1st).
Output:
Time<prd><time>
Example:
> rtc -ort_clock
Time=31786949
3 Jan 1971 21:42:29 GMT
>
> rtc -ort_clock -t2678400
>
rx_fru_config
Syntax:
Read operations:
fcp -orxch1 -prx_fru_config
Write operations:
fcp -orxch1 -prx_fru_config -v{1 | 2 | 4 | 3 | 5 | 6 | 7}
Description:
Controls the receiver branches to be present in a Base Radio.
Options:
Valid settings:
• 1 - Receiver branch 1 enabled
• 2 - Receiver branch 2 enabled
• 4 - Receiver branch 3 enabled
• 3 - Receiver branches 1, 2 enabled
• 5 - Receiver branches 1, 3 enabled
• 6 - Receiver branches 2, 3 enabled
• 7 - Receiver branches 1, 2, 3 enabled
status
Syntax:
Read operations:
status -o<object>
Description:
Displays the platform and FRUs status information.
• status –ops1..n will only display presence detection. The rest of the infor-
mation will be provided with the bs MMI.
• Only lan2 is supported. lan1 and lan3 are not supported because they don’t have a PHY.
Options:
<object> A character string representing the object assigned to control the status query. Valid settings:
• compact_flash
• flash0
• platform
• switch{1..6}
• lan2
• xhub{2..6}
• ps
• ps(1..6)
ps=ps1 ps1 is local and ps(2->6) are remote. xhub1 does not exist since
an xhub is a remote component.
Output:
Compact Flash:
CompactFlash Bank Serial Number<prd><serial_num>
CompactFlash Bank Firmware Version<prd><fw_version>
CompactFlash Bank Model<prd><model>
CompactFlash Bank Start Address<prd><physical address>
CompactFlash Bank Internal Buffer size<prd><int_buff_size>
CompactFlash Bank Size<prd><size>
CompactFlash Bank Sector size <prd><sector_size>
CompactFlash Bank Number of sectors<prd><num_sectors>
Flash Memory:
Flash Bank(n) Start Address<prd><physical address>
Flash Bank(n) Size<prd><size>
Flash Bank(n) Sector(1)<prd><sector_offset(1)>,<sector_ad-
dress(1)>,<sector_size(1)>
...
Flash Bank(n) Sector(n)<prd><sector_offset(n)>,<sector_ad-
dress(n)>,<sector_size(n)>
Platform:
Redundant SC presence detect<prd><pres_detect>
Power Supply presence detect<prd><pres_detect>
Power Supply functional state<prd><func_state>
Fan Module presence detect<prd><pres_detect>
Fan Module functional state<prd><func_state>
Rubidium clock active<prd><active_state>
Rubidium clock state<prd><lock_state>
CP2 Input Clock presence detect<prd><pres_detect>
OCXO Oven ready state<prd><ready_state>
Backplane ID<prd><bck_id>
Slot ID<prd><slot_id>
SC Online state<prd><online_state>
Fan power switch functional state<prd><pres_detect>
Power Supply:
Power Supply <prd><pres_detect>
Xhub:
Power Supply presence detect<prd><pres_detect>
Power Supply functional state<prd><func_state>
Fan Module presence detect<prd><pres_detect>
Fan Module functional state<prd><func_state>
Switch:
Ethernet port (0)<prd><link_status>, <line mode>
Ethernet port (1)<prd><link_status>, <line mode>
...
Only ports with Ephy will have their status reports, so ports from 0 to 7, port9,
ports from 11 to 18 and port 20 will be reported.
<active_state> A character string representing the active state of the device. Valid settings: active not active.
<app size> An integer value representing the number of bytes available to the Application in a memory.
<bck_id> An integer value representing the SC backplane ID.
<func_state> A character string representing the functional state of the device.
Valid settings: functional, failure.
<int_buf_size> An integer value representing the internal buffer size of the mass storage device.
<line_mode> A character string representing the line mode of an Ethernet port. Valid settings:
• unknown
• 10 base half duplex
• 10 base full duplex
• 100 base half duplex
• 100 base full duplex
• 1000 base half duplex
• 1000 base full duplex
<link_status> A character string representing the link status of an ethernet port. Valid settings: up, down.
<lock_state> A character string representing the lock state of the device. Valid settings: locked unlocked.
<model> A character string representing the manucfacturer model of the mass storage device.
<num_sectors> An integer value representing the number of sectors in the mass storage device.
<online_state> An character string representing the SC online_state. Valid settings: online offline.
<physical address> A hexadecimal value representing the physical start address corresponding
to the Platform zero offset in the memory bank.
<pres_detect> A character string representing the detected presence of the device.
Valid settings: present, not present
<ready_state> A character string representing the ready state of the device. Valid settings: ready, not ready.
<sector_address> A hexadecimal value representing the physical address of the memory sector.
<sector_offset> A hexadecimal value representing the offset of the memory sector.
<sector_size> An integer value representing the number of bytes in a memory sector.
<serial_num> An character string representing the the serial number of the compact flash device.
<size> An integer value representing the number of bytes starting from the Plat-
form zero offset in a memory bank.
<slot_id> An integer value representing the SC slot ID.
Example:
factory> status -oplatform
Redundant SC presence detect=not present
Power Supply presence detect=not present
Power Supply functional state=functional
Fan Module presence detect=not present
Fan Module functional state=functional
Rubidium clock active=not active
Rubidium clock state=unknown
CP2 Input Clock presence detect=not present
Fan power switch functional state=functional
OCXO Oven ready state=ready
Backplane ID=0
Slot ID=0
SC Online state=online
factory>
time_reference
Syntax:
Read operations:
tr | time_reference -o<object>
Write operations:
tr | time_reference -o<object> -v<value>
Description:
Selects the time reference source or gets the current selection.
Options:
<object> A character string representing the object to access for the time reference. Valid settings: platform.
<value> A character string representing the time reference. Valid settings:
• ext_1pps
• gps
• redundant_sc
• cp2_link
Output:
TimeRef<prd><value>
Example:
> tr -oplatform
TimeRef=gps
>
> time_reference -oplatform -vext_1pps
>
temp_sensor
Syntax:
Read operations:
ts | temp_sensor -o<object>
Description:
Displays the Site Controller’s board temperature.
Options:
<object> A character string representing the temperature sensor. Valid settings: platform.
Output:
Temp<prd><value><C>
Example:
> ts -oplatform
> Temp=-15C
watchdog_settings
Syntax:
Read operations:
ws -o<object>
Write operations:
ws -o<object> -s<status> -v<value>
Description:
Provides access to the Site Controller’s card watchdog timer. Permits to enable the
watchdog, set and read its time-out period.
Options:
<object> A character string representing the object for the watchdog timer. Valid settings: watchdog.
<status> A character string representing the status. Valid settings: enable, disable
<value> A positive integer representing the timeout value. Valid settings: <Device specific value>
Output:
Watchdog<prd><status> timeout<prd><timeout value> msec
The value returned will be the actual watchdog value that the Platform was able to
achieve. The value may be different from the value used in the set command due
to hardware limitations. For example: for the specified value of 120000 in the set
operation, a value of 161464 is returned by the Platform.
Example:
> ws -owatchdog
Watchdog=enable=timeout=161464 msec
>
> ws -owatchdog -senable -v120000
>
3
BOOT1 Commands
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BOOT1: used for loading the actual SC Application or loading the Test Application.
BOOT1 Commands
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
ATTRIB
Syntax:
Syntax1: attrib [-bare] [-n | -a | -aClear] [<file1> [<file2> ...]]
Syntax2: attrib [-bare] [-v <verStr>] [-d <dateStr>] [<comp1> [<comp2> ...]]
Syntax3: attrib [-bare] [-update] [-dump] [<comp1> [<comp2> ...]]
Description:
The attrib command displays or edits information associated with hardware and file
components within the Site Controller.
Options:
Table 3-1 Common Options:
Option Description
-bare Suppress display of heading, paging & results.
-n Sets file(s) to be used as next after reset. Valid file must exist
-a Set file archive flag.
-aClear Clear file archive flag.
-v <verStr> Set version label of component (no spaces!).
-d <dd/mm/yyyy> <hh:mm:ss> Set component upgraded date & time.
Example:
attrib Displays all attributes
boot
Syntax:
boot [<flashimage>|<filepath>]
Description:
boot according to argument or configuration
build_info
Syntax:
build_info
Description:
print build info of the image
bview
Syntax:
bview
Description:
view the boot configuration
cd
Syntax:
cd [<dirname>]
Description:
change the working directory
chmod
Syntax:
chmod <mode> <path> ...
Description:
change access mode of files
cp
Syntax:
cp <source> ... <destination>
Description:
The cp command copies one or more files to a destination directory or copies one file to a new name.
ethstat
Syntax:
ethstat <interface name>
Description:
Display Ethernet statistics
exit
Syntax:
exit
Description:
exit shell session
finstall
Syntax:
finstall [-b] <name> <filepath> [<base>]
Description:
install image in flash (at address)
format
Syntax:
format [-f] <volume> [<params>]
Description:
format a volume
fusage
Syntax:
fusage
Description:
display flash usage
go
Syntax:
go [<addr>]
Description:
go to specified address or last load entrypoint
help
Syntax:
help [<command> ...]
Description:
Without parameter, prints syntax and description of all available commands.
Provide a command as a parameter to get the description of a given command.
ifattach
Syntax:
ifattach -h
Description:
attach or detach an interface
ifconfig
Syntax:
ifconfig -a | interface [options
Description:
configure network interface
ifstat
Syntax:
ifstat <interface name>
Description:
Display interface statistics
inetcfg
Syntax:
inetcfg -h
Description:
Get/set INET configuration
ipaddr
Syntax:
ipaddr [<new ipaddr> [<new netmask>]]
Description:
Display or change IP address and netmask
load
Syntax:
load <filepath> [<base>].
Description:
The load command loads the image at a given location.
login
Syntax:
login [-d <device>] [<username>]
Description:
Log the user in.
ls
Syntax:
ls [-acil] [<dirname> ...]
Description:
The ls command lists the specified files or the files and subdirectories in that direc-
tory where the command is executed.
mkdir
Syntax:
mkdir <directory> ...
Description:
create directories
mload
Syntax:
mload <filepath> <base>
Description:
load memory from (raw) file
mount
Syntax:
mount <volume> <fmtmgr> <device> [<params>]
Description:
mount a volume
mv
Syntax:
mv <source> ... <destination>
Description:
rename/move files
netstat
Syntax:
netstat
Description:
Display network statistics
ping
Syntax:
ping [options] host
Description:
send ICMP ECHO_REQUEST packets to host.
pwd
Syntax:
pwd
Description:
print the working directory
reset
Syntax:
reset
Description:
Reset the system.
rm
Syntax:
rm [-f] <filename> ...
Description:
remove files
rmdir
Syntax:
rmdir [-f] <directory> ...
Description:
remove (empty) directories
route
Syntax:
route <add | delete | print>
Description:
[dest mask gateway] add/delete/list routes
shell
Syntax:
shell [<cmd> ...] / [-f <file>]
Description:
invoke shell [to execute command]
shutdown
Syntax:
shutdown [-r]
Description:
shutdown system [ and reset]
sleep
Syntax:
sleep <seconds>
Description:
sleep for a number of secondse
stat
Syntax:
stat <pathname> ...
Description:
report information about file/directory
sync
Syntax:
sync <volume>
Description:
synchronize volume with disk
testapp
Syntax:
testapp
Description:
executes test application
tftp
Syntax:
tftp [-a] <host> <get|put> <source> [destination]
Description:
The tftp command allows files to be uploaded to or downloaded from a remote computer. The remote
host whose IP address is specified by host must be running TFTP server software.
Options:
-a Indicates that the transfer shall be in ascii mode, as opposed to binary (default).
Example:
tftp 10.128.116.186 put brc12log.csv where 10.128.116.186 is the IP address of the machine
to which the file will be copied in the directory specified by the TFTP server software.
traceroute
Syntax:
traceroute [options] destination
Description:
print hop-by-hop path to destination.
unmount
Syntax:
unmount [-f] <volume>
Description:
unmount a volume
vols
Syntax:
vols [<volume> ...]
Description:
report volume statistics
4
Site Controller Commands
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
ARP
Syntax:
arp [-V <routetab>] [-i <ifname>] -a
arp [-V <routetab>] [-i <ifname>] -A
arp [-V <routetab>] -d <hostaddress>
arp [-V <routetab>] [-i <ifname>] [-p] [-t] -s <hostaddress> <ether_addr>
Description:
The arp command displays the current ARP (Address Resolution Protocol) lookup table maintained
internally by the IP protocol stack in the Site Controller. This table shows the Site Controller's
mapping of MAC addresses to IP addresses of the devices connected to it.
Options:
-i [ifname] Specify interface. First one if not specified.
-t Temporary ARP entry.
-p Public ARP entry (i.e. proxy ARP entry).
-V [routetab] Specify route table. 0 if not specified.
Commands:
-a Display the currently existing ARP entries.
-A Erase all the ARP entries.
ATTRIB
Syntax:
Syntax1: attrib [-bare] [-n | -a | -aClear] [<file1> [<file2> ...]]
Syntax2: attrib [-bare] [-v <verStr>] [-d <dateStr>] [<comp1> [<comp2> ...]]
Syntax3: attrib [-bare] [-update] [-dump] [<comp1> [<comp2> ...]]
Description:
The attrib command displays or edits information associated with hardware and file
components within the Site Controller.
Options:
Table 4-1 Attribute Bit Values:
Option Description
-c Sets file(s) to be used as current now
-n Sets file(s) to be used as next after reset. Valid file must exist
-cn Sets file(s) to be used as current and next. Valid file must exist
Option Description
-install Sets a file as valid
-remove Sets a file as invalid. Clears the date and version string
-update Update date and readable flag data from hardware and filing system
Table 4-4 Options available at any time and with any syntax:
Option Description
-all Display current versions as well
-bare Does not page information or display the header text
-verboseOff Turn display of SWDL errors/information off
-verboseErrors Turn display of SWDL errors only on
-verboseAll Turn display of SWDL errors and information on
Option Description
verStr Version label for the component
dateStr The upgraded date string (hh:mm:ss) for the component
component Specifies the component to set/display
Example:
attrib Displays all attributes
attrib -c tsc.code.1 brc.code.1 Sets the brc.code.1 and tsc.code.1 to be used now
BRLOCK
Syntax:
brlock
brlock -status br_number
brlock -clear br_number
brlock -clearall
Description:
Following a VSWR alarm all BRs are locked. The brlock command allows the service personnel to ascertain
the lock status of BRs and unlock individual BRs. brlock -clear br_number clears the lock from an individual br;
brlock -clearall clears the lock from all brs; brlock -status br_number returns the lock status for an individual br.
BTS_TYPE
Syntax:
bts_type
Description:
The bts_type command displays the kind of Base Station. This information is also
available via status sc command.
Example:
SC: bts_type -?
bts_type [-mts4 | -mts2 | -?] Display or set the BTS type
-mts4 = Set BTS type to MTS4 (requires reset to take effect!)
-mts2 = Set BTS type to MTS2 (requires reset to take effect!)
-? = Display help for this command
SC: bts_type
BTS type: MTS2
CLS
Syntax:
cls
Description:
The cls command attempts to clear the screen by sending the ANSI codes ^[[0;0H^[[J to the standard output..
DISPLAY CONFIG
Syntax:
display config [-quick | -ip]
Description:
The display config command display the current configuration data of the Site Controller. By default, this
command displays all of the configurable parameters set in the configuration data file downloaded from the
BTS Service Software. Options are provided to allow useful subsets of this information to be displayed.
Options:
-ip Display all IP addresses and port settings.
-quick Display site and zone ID, adjacencies, LST enabled flag, GPS status, and all address ranges.
EAS_OUT
Syntax:
eas_out
Description:
Command for controlling the user control outputs. The user control outputs are two
user definable output signals on the MTS.
.EGOP
Syntax:
.egop [-e <min_gc_id> <max_gc_id> | -d | -?]
Description:
Modifies/displays the values for the 'Extended GC on PDCH' subfeature'
The “-?” option displays the help for this command
No arguments displays the current value stored in the MIB
The “-d” option disables the feature
The “-e <min_gc_id> <max_gc_id>“ option enables the feature using the range [min_gc_id, max_gc_id] (inc)
EXIT
Syntax:
exit
Description:
This command is used to log out the user and terminate the MMI. If the user was logged
in via telnet, the connection is dropped.
HELP
Syntax:
help
Description:
The help command displays a list of all available commands and a short synopsis of their
use, comprising an option list and a brief description.
All commands support a ‘-?’ option which displays a description of that command and
its usage, including a brief description of each parameter.
KVL
Syntax:
kvl
Description:
The kvl command entered via the front serial port of the Site Controller configures the front port for
communication with the Key Variable Loader device. If no valid KVL communication is received within 60
seconds, then the port returns to normal operation. Since the front serial port is normally used by the MMI, no
MMI commands may be entered via this port until the communication with the Key Variable Loader device has
been terminated. The success of this operation is indicated at the Key Variable Loader device only. Following
termination of communication by the KVL, the front serial port automatically returns to normal MMI mode.
LOCK
Syntax:
lock
Description:
The lock command places the BTS into the locked state. While in the locked state, the BRs are prevented
from keying. The MMI waits while the Site Controller performs the operation before returning to the user.
The call processing operation will be shut down gracefully when a lock command is issued.
LOG
Syntax:
log [-inform | -minor | -major | -fatal] <string>
Description:
The log command saves the specified string into one of the SC’s log files. The string may be up to
approximately 80 characters in length, and will be converted to lower case before being saved. If
no option is specified, the minor (Fault/Event) log will be used by default.
The # character is the MMI comment character. If this character is used in the
string, then any text following it will be discarded.
Options:
-inform Saves string to the information (Volatile) log
-minor Saves string to the minor (Fault/Event) log
-major Saves string to the major (Major Event) log
-fatal Saves string to the fatal (Major Event) log
LOGOUT
Syntax:
logout
Description:
The logout command logs out a user, it is the same command as "EXIT".
LS
Syntax:
ls [-acil] [<dirname> ...]
Description:
The ls command lists the specified files or the files and subdirectories in that direc-
tory where the command is executed.
MIRROR
Syntax:
mirror [portID <in|out|both|port_true|off> | -?]
Description:
Modifies/displays ethernet switch mirroring state..
Options:
\n (No arguments) = Display mirroring state for all ports
\n portID = Display mirroring state of port no. portID (portID=0,...,10)
\n portID in = Enable mirroring all received frames on port no. portID
\n portID out = Enable mirroring all transmitted frames on port no. portID
\n portID both = Enable mirroring all frames on port no. portID
\n portID port_true = Set port no. portID as a mirror capture port
\n portID off = Disable mirroring on port no. portID
\n -? = Display help for this command
Port IDs:
Table 4-6 Roles of Switch Ports
NETSTAT
Syntax:
netstat [-a]
Description:
The netstat command displays all connections and listening ports information.
PASSWORD
Syntax:
password
Description:
This command impacts on current access level only.
Upon entry of the password command, the user will be prompted to enter the existing password. A correct
entry will result in a request for the new password, and the presentation of the restriction to which it must
conform. If the entry is valid, the user will be prompted to re-enter the new password.
A message will then be displayed informing the user whether a change has been made. The command
will change the appropriate password according to the newly entered password.
PING
Syntax:
ping [ip_address]
Description:
The ping command enables the user to send an ICMP ping message to be sent to the specified IP address over a
connected IP network. This command is not available on System Releases that do not support the redundant SC.
If the IP address is not specified, the help text will be displayed.
PORT
Syntax:
port [id] [on | off]
Description:
Command for site controller switch port enabling and disabling..
RESET
Syntax:
reset
Description:
The reset command causes the Site Controller to perform a hardware reset, which is roughly
equivalent to pressing the front panel RESET button.
RGPS_DELAY
Syntax:
rgps_delay [-set <delay> | -invalidate]
Description:
The rgps_delay command sets the transmission time delay for the cable connecting the RGPS (Remote GPS)
receiver to the Site Controller. The time delay is only to be set when an independently powered RGPS receiver is
being used. By setting a time delay the Site Controller assumes that a independently powered RGPS is present.
Options:
-set Set the transmission time delay to the entered value. Must be entered in nanoseconds.
-invalidate This command invalidates the transmission time delay value.
This command is not available on System Releases that do not support the
use of a remote GPS antenna.
SITE_LOCATION
Syntax:
site_location
site_location {-reset | -valid}
site_location -co_ordinates [N | S] deg: min: sec [W | E] deg: min: sec H metres
Description:
This command allows resetting, setting and checking of the site location. The system needs to
determine its location in order to synchronize its timing with other sites.
When a remote GPS is used, the position information is relevant to the re-
mote GPS and not to the BTS.
Options:
-reset Clears any site location information from permanent memory. The Site Controller
will perform GPS site survey when it is next restarted.
-valid Determine if a valid site location has been stored in permanent memory.
-co_ordinates Sets the lattitude, longitude and height co-ordinates for the site location.
If the SC is moved, the site_location -reset command must be entered immediately after
first power up to allow the system to calculate its new location.
Example:
site_location Determine location of site
site_location -reset Clear any stored site location
site_location -valid Determine if site location valid
site_location N54:12:45.789 W1:6:12.345 H174 Set the site location
The system must be restarted for these commands to have any effect.
STATUS BR
Syntax:
status br [cabinet | position]
Description:
The status br command returns information relating to a single BR or all BRs. If entered without cabinet
and position parameters, the command causes the information for all BRs to be displayed in a table.
If no response is received from a BR, then the entries in the table are made with a series of dashes.
Options:
cabinet The cabinet in which the BR is physically located.
position The position of the specified BR within the cabinet.
The cabinet and position parameters must be entered directly next to each
other without any separating spaces, so a BR in cabinet 1 position 1 would be
checked with the command “status br 11”.
STATUS BSL
Syntax:
status bsl [-r]
Description:
The status bsl command will display the current status of the base site link, includ-
ing the results of any tests performed.
Options:
-r Resets the statistics for the base site link.
STATUS BSLQ
Syntax:
status bslq [-r]
Description:
The status bslq command displays the statistics for the transmission queues associated with the X.21 interface.
Options:
-r Resets the statistics for the X.21 transmission queues.
STATUS BTS
Syntax:
status bts [-l]
Description:
The status bts command displays state information for various BTS subsystems.
Options:
-l Long output format. In addition to the state, the associated probable cause and time of
last state change trap are displayed on each subsystem.
STATUS CRTP
Syntax:
status crtp [-r]
Description:
The status crtp command displays the current CRTP (Compressed Real Time Protocol) statistics.
Options:
-r Resets these CRTP statistics
STATUS EAS
Syntax:
status eas [ -p9] [-all | -m ]
Description:
The status eas command displays the status of all the alarm contacts of the EAS.
Status results are displayed in a table.
The table contains input/output number, a textual description, and a status (o.k./alarm for inputs and
active/inactive for outputs). The inputs and outputs are displayed in separate sections in the table.
Options:
-p9 This option gets the status of the plug number entered (-p9 parameter is required in MTS,
but it matches rear plug 9 in the EBTS EAS hardware.
-all This option shows all inputs (including disabled inputs).
-m This option starts continuous status monitoring.
STATUS FR
Syntax:
status fr [-r]
Description:
The status fr command displays the current statistics associated with the frame relay protocol layer.
Options:
-r Resets these frame relay statistics
STATUS FRF
Syntax:
status frf [-r]
Description:
The status frf command displays the current statistics associated with frame re-
lay fragmentations and reassembly.
Options:
-r Resets the frame relay fragmentation statistics
STATUS KEYS
Syntax:
status keys
Description:
The status keys command displays the security key status information.
STATUS LMI
Syntax:
status lmi [-r]
Description:
The status lmi command displays the current LMI (Local Management Interface) statistics. The LMI protocol
monitors the PVCs (Permanent Virtual Circuit) that link the Site Controller to the Core Routers.
Options:
-r Resets these LMI statistics
STATUS NTP
Syntax:
status ntp
Description:
The status ntp command displays the current network time protocol status information
STATUS PEER
Syntax:
status peer
Description:
The status peer command displays information on the other site controller's current functional status
and its identity position. A valid id will only be displayed if the peer SC is responding and correctly
configured. The command is only applicable for an BTS with a dual site controller configuration. This
command is not available on System Releases that do not support the redundant SC.
STATUS RIGMP
Syntax:
status rigmp [-r]
Description:
The status rigmp command displays the current statistics associated with robust IGMP
(Internet Group Membership Protocol).
Options:
-r resets these robust IGMP statistics
STATUS SC
Syntax:
status sc [-all]
Description:
The status sc command displays preliminary diagnostics information on the SC. This includes the health
of the SC, the trunking state, the internal state, BTS runtime statistics and the site link status.
Options:
-all Displays the internal state of the cell and BRs.
STATUS SEC
Syntax:
status sec
Description:
The status sec command displays security parameters used by the Site Controller.
STATUS SRI
Syntax:
status sri [-gps | -sr | -t -stat_reset | -p]
Description:
The status sri command provides general information on the health of the Site Reference system. This
includes the Site Reference and GPS operational status, UTC, GPS and local times and 1PPS signal status.
Options:
-gps Displays detailed status of the GPS receiver including a satellite tracking report.
-sr Provides details of the site reference internal state status sri [-all | -t | -p | -stat_show | -stat_reset]
-t Displays GPS receiver identifier.
When a remote GPS is used, the position information is relevant to the re-
mote GPS and not to the BTS
TFTP
Syntax:
tftp [-a] <host> <get|put> <source> [destination]
Description:
The tftp command allows files to be uploaded to or downloaded from a remote computer. The remote
host whose IP address is specified by host must be running TFTP server software.
Options:
-a Indicates that the transfer shall be in ascii mode, as opposed to binary (default).
Example:
tftp 10.128.116.186 put brc12log.csv where 10.128.116.186 is the IP address of the machine
to which the file will be copied in the directory specified by the TFTP server software.
TIMEZONE
Syntax:
timezone [ [+|-]{0..14}:{00|30} ]
Description:
Command for configuring the MTS timezone..
Options:
[ [+|-]{0..14}:{00|30} ] — Set the Site Controller time zone relative to GMT.
Example:
SC> timezone +1:00
Sets the time zone to GMT +1.
UNLOCK
Syntax:
unlock
Description:
The unlock command places the Site Controller into the unlocked state from the current state.
VER
Syntax:
ver [-h]
Description:
The ver command displays version information for Site Controller software and, optionally, the Site Controller
hardware. If entered without options, the firmware and application version numbers are displayed.
Options:
-h Displays both hardware and software information.
WHO
Syntax:
who
Description:
This command displays a list of users logged in or connected to the SC. The information
displayed includes the user name, port, and access mode. If the user name field is blank, then
a telnet connection exists but no user is logged in over it.
If a user is logged into a Base Radio, then the user name is displayed as “Unknown”.
Example:
SC>atc 1 get device_id
Device ID 000.080.123
atc # cav_park
Syntax:
atc # cav_park <cav>
Description:
The atc # cav_park command instructs the Autotuner to park the specified cavity. The ATCC will respond with
one of the following cavity status indicators: cavity parked, park conflict (signal present), invalid cavity number.
Example:
SC>atc 1 cav_park 1
Command executed OK
Example:
SC>dpm 1 get device_id
Device ID 000.080.123
This command should be used only when the transmitter is keyed to obtain accurate results.
Example:
SC>dpm 1 get fwd_power
Input Power 37.68 Watt
DPM Status 20 – DPM OK
Description:
The psu # get vendor_serial returns the Vendor serial number
Example:
SC>psu 1 get vendor_serial
Vendor serial number 12D145521145A421105
Example:
SC>psu 1 get alarm
Alarm 0x20 - DC in fail
Example:
SC>psu 1 get dc_operation
PSU is configured to DC Operation
Status 0E – All ok
Description:
The psu # get psu_temperature returns the internal temperature of the PSU in Celsius
Example:
SC>psu 1 get psu_temperature
PSU Temperature 38°C
Status 0E – All ok
Example:
SC>psu 1 get fan_speed
FAN Speed 4
Status 0E – All ok
psu # start_fan
Syntax:
psu # start_fan
Description:
In the case were a technician replaces a FAN kit and the FAN’s does not start automatically the
command psu # start_fan can be used. It forces the fan voltages to 24V and check the Alarm/Status
to ensure the fan is running and then return to current state.
Example:
SC>psu 1 start_fan
Command executed OK
can reboot
Syntax:
can reboot <type> #
Description:
The can reboot forces the CAN-unit to reboot.
Example:
SC>can reboot dpm 1
Command send
can reset
Syntax:
can reset <type> #
Description:
The can reset forces the CAN-unit to reset.
Example:
SC>can reset dpm 1
Command send
can view_mapping_list
Syntax:
can view_mapping_list
Description:
The can view_mapping_list command prints the mapping list.
Example:
SC>can view_mapping_list
Mapping list:
Device Track ID
DPM 1 JTH0500100
PSU 1 JTH0500200
can add_mapping
Syntax:
can add_mapping <device> <Track ID>
Description:
The can view_add_mapping command adds a mapping to the list. If device already
exist in the list it will overwrite the old mapping.
Example:
SC>can add_mapping dpm 1 JTH0500100
dpm 1 mapped to JTH0500100
can remove_mapping
Syntax:
can remove_mapping <device>
Description:
The can remove_mapping command removes a mapping from the list.
Example:
SC>can remove_mapping dpm 1
dpm 1 removed from mapping
can change_mapping
Syntax:
can change_mapping <From Track ID> <To Track ID>
Description:
The can change_mapping command changes a mapping.
Example:
SC>can change_mapping JTH0500100 JTH0500101
dpm 1 mapping changed to JTH0500101
can check_mapping
Syntax:
can check_mapping
Description:
The can check_mapping command checks and print the status of the mapping.
Example:
SC>can check_mapping
Units are present:
Device Track ID
DPM 1 JTH0500101
PSU 1 JTH0500200
Units are not present:
DPM 2 JTH0500105
Track ID not mapped
JTH0500102
5
Base Radio Commands
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Test Application is a powerful mode, inappropriate use of Test Application MMI
can lead to a permanent hardware failure. Please proceed with extreme caution.
cabinet_id
Syntax:
cabinet_id -o<object> –c<cabinet>
Description:
This command is used to display/change the cabinet id settings of the Base Radio Station. This
is one of the values sent back to the ACG in a BR registration msg.
Options:
-o(object)=platform
-c(cabinet id)=1,8,1,No Units
Example:
> cabinet_id -oplatform -c1
> cabinet_id -oplatform
Cabinet ID=1
position_id
Syntax:
position_id -o<object> –p<cposition>
Description:
This command is used to display/change the position id settings of the Base Radio Station. This
is one of the values sent back to the ACG in a BR registration message.
Options:
-o(object)=platform
-p(position id)=1,8,1,No Units
Example:
> cabinet_id -oplatform -c1
> position_id -oplatform -p1
> cabinet_id -oplatform
Cabinet ID=1
> position_id -oplatform
Position=1
fv -oplatform
Syntax:
fv -oplatform
Description:
Checks the current version of all system components.
power
Syntax:
power -otxch1 -a<value>
power -otxch1
Description:
Gets or sets the current output power level.
Example:
> power -otxch1 -a35
set the maximum power.
freq
Syntax:
freq -otx_all -f<frequency>
freq -orx_all -f<frequency>
freq -otx_all
freq -orx_all
Description:
Controls the transmit/receive channel frequency.
Options:
freq -otx_all -f<frequency> — sets the transmitter frequency
freq -orx_all -f<frequency> — sets the receiver frequency
freq -otx_all — gets the transmitter frequency
freq -orx_all — gets the receiver frequency
AIEA
Syntax:
aiea
Description:
This aiea command returns the Air interface Encryption and Authentication configuration.
AIR_TRACER
Syntax:
air_tracer [get | off | on default | on <ip> encrypt | clear | both]
Description:
Enable or disable air_tracer or get its status.
Examples:
a) CSS: air_tracer
Use one of:
• air_tracer get
• air_tracer off
• air_tracer on default
• air_tracer on <ip> encrypt | clear | both
AIR_TRACER_MODE
Syntax:
air_tracer_mode [x x x x]
Description:
The air_tracer_mode command sets the Mode of the TMV output to clear, encrypted or both.
Example:
CSS: air_tracer_mode E C B C
CHANSTAT
Syntax:
chanstat
Description:
Displays current channel usage on BR.
CLS
Syntax:
cls
Description:
The cls command causes a VT100 clear screen escape sequence followed by a cursor location
(top left) command to be sent to the console screen.
DEKEY
Syntax:
dekey
Description:
The dekey command stops all RF transmission.
After the command is entered, an indication of a successful transmission stop is returned.
EXIT
Syntax:
exit
Description:
This command is used to log out the user and terminate the MMI. If the user was logged
in via telnet, the connection is dropped.
GET ALARMS
Syntax:
get alarms
Description:
Displays list of application and core alarms.
GET CABINET
Syntax:
get cabinet
Description:
This command returns the cabinet position of the current Base Radio.
GET CONFIG
Syntax:
get config
Description:
Displays the current configuration of the BR.
GET EX_AD
Syntax:
get ex_ad [port]
Description:
The get ex_ad command returns the current hexadecimal value of all A/D ports (0 to 11)
on the Exciter module with their interpreted voltages.
If the variable for the port number is not entered, the current value of all ports are returned.
GET EXT_REF
Syntax:
get ext_ref
Description:
Show the external reference status.
GET FWD_PWR
Syntax:
get fwd_pwr
Description:
The get fwd_pwr command returns the current value of forward power. This reading is taken from the built-in
power meter of the RF Power Amplifier module. The results are returned in Watts and dBm.
This command should be used only when the transmitter is keyed to obtain accurate results.
GET MAX_VSWR
Syntax:
get max_vswr
Description:
The get max_vswr command returns the maximum VSWR before an alarm is triggered, as measured
by the built-in power meters of the RF Power Amplifier module.
GET NVM_PARAM
Syntax:
get nvm_param [-object] [-param] [-crc]
Arguments:
object: object id (cntrl | ex | pa | rx1)
param: parameter id or all for complete list of parameters for given fru.
crc: use to calculate and display CRC-32 checkusm (optional)
GET PA_AD
Syntax:
get pa_ad [port]
Description:
The get pa_ad command returns the current hexadecimal value of all A/D ports ( 0 to 11) on
the Power Amplifier module with their interpreted voltages.
If the variable for the port number is not entered, the current value of all ports are returned.
GET PA_STATUS
Syntax:
get pa_status
Description:
Displays all configuration information and current status relating to the PA.
GET POSITION
Syntax:
get position
Description:
The get position command returns the position number of where the current BR is mounted within
a selected cabinet. This does not represent the cabinet in which the BR resides.
GET REF_PWR
Syntax:
get ref_pwr
Description:
The get ref_pwr command returns the current value of reflected power. This reading is taken from the built-in
power meter of the RF Power Amplifier module. The results are returned in Watts and dBm.
This command should only be used when the transmitter is keyed to obtain accurate results.
GET RPTR_STATUS
Syntax:
get rptr_status
Description:
The get rptr_status command returns the overall status of the base radio.
GET RX_FREQ
Syntax:
get rx_freq
Description:
The get rx_freq command returns the programmed receiver frequency for the current BR.
GET TIME
Syntax:
get time
Description:
Display the current system time (GMT).
GET VSWR
Syntax:
get vswr
Description:
The get vswr command calculates the current VSWR, as measured by the built-in power meters of the RF Power
Amplifier module. This command should only be used when the transmitter is keyed to obtain accurate results.
HELP
Syntax:
help
Description:
The help command displays a list of all available commands and a short synopsis of their
use, comprising an option list and a brief description.
All commands support a ‘-?’ option which displays a description of that command and
its usage, including a brief description of each parameter.
KEY
Syntax:
key
Description:
The key command starts the RF transmission of the BR at default TX power.
After the command is entered, an indication is printed that the key-up process has started. As soon as the trans-
mission has started and the default TX power has been reached the command returns the current output power.
KVL
Syntax:
kvl
Description:
The kvl command entered via the front serial port of the Site Controller configures the front port for
communication with the Key Variable Loader device. If no valid KVL communication is received within 60
seconds, then the port returns to normal operation. Since the front serial port is normally used by the MMI, no
MMI commands may be entered via this port until the communication with the Key Variable Loader device has
been terminated.The success of this operation is indicated at the Key Variable Loader device only. Following
termination of communication by the KVL, the front serial port will automatically return to normal MMI mode.
lstalm
Syntax:
lstalm
Description:
Displays list of application and core alarms.
lstalmtr
Syntax:
lstalmtr
Description:
Displays list of transient alarms.
RESET
Syntax:
reset
Description:
The reset command causes the Base Radio to perform a hardware reset, which is roughly
equivalent to pressing the front panel RESET button.
VER
Syntax:
ver [-h]
Description:
The ver command displays version information for Base Radio software and, optionally, the Site Controller
hardware. If entered without options, the firmware and application version numbers are displayed.
Options:
-h Displays both hardware and software information.
SET LAPD_TRACE
Syntax:
set lapd_trace [on | off]
Description:
Command for controlling LAPD tracing to MMI.
SET LOG_ROUTING
Syntax:
set log_routing [nvlog | vlog | both | none]
Description:
Command for controlling routing of logging information.
Use "nvlog", "vlog" or "both" to show detailed logs on the MMI or "none" to disable
showing detailed logs. There's no need to specify any extra parameter with file name since
only default volatile/non volatile logs will be used.
SET MAX_VSWR
Syntax:
set max_vswr {1.1..4.0}
Description:
The set max_vswr command sets the maximum VSWR for the internal BR power monitor.
The power is rolled back if this value is reached. (The Base Radio may shut down if the
excessive VSWR condition still exists after power roll-back).
SET NVM_PARAM
Syntax:
set nvm_param [-object] [-param] [-crc]
Arguments:
object: object id (cntrl | ex | pa | rx1)
param: parameter id
value: parameter value
crc: use to force checking of CRC-32 checkusm (optional)
SET SM_TRACE
Syntax:
set sm_trace
Description:
Command for controlling state transition tracing to MMI.
TETRA/Dimetra Acronyms
The table explains the acronyms used throughout this manual and in the Dimetra System and is not system
release specific. Therefore not all terms may be relevant for a specific system or release.
Item Description
A-ISSI Assigned ISSI
A/V Anti-Virus
AAA Authentication, Authorization, and Accounting
ABO Automatic Busy Override
ACC Adjacent Control Channel
ACCH Associated Control Channel
ACELP Algebraic Code Excited Linear Prediction
AD Active Directory
ADM Alias Database Manager (part of CENTRACOM Gold Server)
AEB Ambassador Electronics Bank
AEI Audio Expansion Interface
AGC Automatic Gain Control
AI 1. Air Interface
2. Additional Identity
AIE Air Interface Encryption
AIMI Ambassador Interface Multiplex Interface
AIS 1. Alias Integrated Solution
2. Archiving Interface Server
ALOM Advanced Lights Out Management
AMB Ambassador Board
AMS Alert Management System
API Application Programming Interface
APN Access Point Name
ARP Address Resolution Protocol
AS Alias Server
ASC Automatic Synchronization Configuration
ASIC Application Specific Integrated Circuit
ASSI Alias Short Subscriber Identity
ATCC Auto Tune Cavity Combiner
Index
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
B
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
C
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Commands
MMI Commands. . . . . . . . . . . . . . . 1-1
I
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction . . . . . . . . . . . . . . . . . . 1-1
M
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
S
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
T
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■