IDEN EBTS Subsystem Troubleshooting Guide

Technical Manual
iDEN
EBTS Subsystem
Troubleshooting Guide
6881012Y79-B
23-Feb-09
SR 16.0
RF SUBSYSTEM
Notice to Users
No part of this publication, or any software included with it, may be reproduced, stored in a retrieval system, or transmitted in any
form or by any means, including but not limited to, photocopying, electronic, mechanical, recording or otherwise, without the
express prior written permission of the copyright holder. Motorola, Inc. provides this document AS IS without warranty of any kind,
either expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular
purpose. Motorola reserves the rights to make changes or improvements in the equipment, software, or specifications described
in this document at any time without notice. These changes will be incorporated in new releases of this document.
Computer Software Copyrights
This document, Motorola products, and 3rd Party Software products described in this document may include or describe
copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws
in the United States and other countries preserve for Motorola, its licensors, and other 3rd Party supplied software certain exclusive
rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works
of the copyrighted material. Accordingly, any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied
material contained in the Motorola products described in this document may not be copied, reproduced, reverse engineered,
distributed, merged or modified 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 or other 3rd Party supplied software, except for the normal non-exclusive,
royalty free license to use that arises by operation of law in the sale of a product.
Use and Disclosure Restrictions
The software described in this document is the property of Motorola, Inc. It is furnished under a duly executed license agreement
and may be used and/or disclosed only in accordance with the terms of the said agreement.
The software and documentation contained in this publication are copyrighted materials. Making unauthorized copies is prohibited
by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language or computer language, in any form or by any means, without the express prior written permission of
Motorola, Inc.
Trademarks
MOTOROLA, the Stylized M Logo, iDEN, and Message Mail are trademarks or registered trademarks of Motorola, Inc. in the United
States and other countries.
All other product or services mentioned in this document are identified by the trademarks or service marks of their respective
companies or organizations, and Motorola, Inc. disclaims any responsibility for specifying their ownership. Any such marks are
used in an editorial manner, to the benefit of the owner, with no intention of infringement.
While reasonable efforts have been made to assure the accuracy of this document, this document may contain technical or
typographical errors or omissions. Motorola, Inc. and its subsidiaries and affiliates disclaim responsibility for any labor,
materials, or costs incurred by any person or party as a result of using this document. Motorola, Inc., any of its subsidiaries or
affiliates shall not be liable for any damages (including, but not limited to, consequential, indirect, incidental, or special damages
or loss of profits or data) even if they were foreseeable and Motorola has been informed of their potential occurrence, arising
out of or in connection with this document or its use. Motorola, Inc. reserves the right to make changes without notice to any
products or services described herein and reserves the right to make changes from time to time in content of this document
and substitute the new document therefor, with no obligation to notify any person or party of such changes or substitutions.
2009 - Motorola, Inc. All Rights Reserved
Contact Information
Motorola, Inc.
Networks business
1501 Shure Dr.
Arlington Heights, IL 60004
U.S.A
SPECIFICATIONS ARE SUBJECT TO CHANGE WITHOUT NOTICE.
REV 11/19/08
Table of Contents
List of Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -v
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -vii
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -ix
List of Changed Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xi
About this manual....

Purpose ........................................................................................... -xi
Audience Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xii

Customer Network Resolution Center (CNRC) . . . . . . . . . . . -xiii
Related Manuals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xiv
Manuals Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xvi
Reporting Manual Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . -xvii
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xviii
Software ....................................................................................... -xviii
Hardware...................................................................................... -xviii
Safety ........................................................................................... -xviii
General Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xix

Keep Away From Live Circuits ...................................................... -xix
Ground the Equipment ................................................................... -xx
Electro-Static Discharge................................................................. -xx
Do Not Operate In An Explosive Atmosphere ................................ -xx
Do Not Service Or Adjust Alone ..................................................... -xx
Use Caution When Exposing Or Handling a Cathode-Ray Tube... -xx
Do Not Substitute Parts Or Modify Equipment ............................... -xx
CMM Labeling and Disclosure Table . . . . . . . . . . . . . . . . . . . -xxi

Revision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xxiii
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xxiv
Chapter 1
Overview
EBTS Subsystem Troubleshooting Overview. . . . . . . . . . . . 1-2
Purpose and Focus ........................................................................ 1-2
Troubleshooting Method ................................................................ 1-2
Scenario Categories....................................................................... 1-3
Restricted Access .......................................................................... 1-3
Target Audience ............................................................................. 1-4
Recommended Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
Table of Contents
EBTS Subsystem Description . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Introduction .................................................................................... 1-6
EBTS Subsystem Components . . . . . . . . . . . . . . . . . . . . 1-7

Access Control Gateway ................................................................ 1-7
iDEN Monitor Unit/Environmental Alarm System ........................... 1-9
Base Radio..................................................................................... 1-9
Quad Base Radio ......................................................................... 1-10
Quad2 Base Radio ....................................................................... 1-11
RF Distribution System................................................................. 1-13
EBTS Subsystem Components Block Diagrams.......................... 1-14
Chapter 2
Troubleshooting Strategies
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
iDEN Open Problem List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
About MMI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Field Replaceable Units (FRU). . . . . . . . . . . . . . . . . . . . . 2-5
Site Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
General EBTS Troubleshooting Strategies . . . . . . . . . . . . . . 2-7
Data Collection ............................................................................... 2-7
EBTS Troubleshooting Resources. . . . . . . . . . . . . . . . . . . . 2-10

Operations and Maintenance Center . . . . . . . . . . . . . . 2-10
Events and Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
EBTS Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Integrated Site Controller (iSC) Indicators.................................... 2-13
Base Radio (BR) Indicators.......................................................... 2-17
Quad2 Base Radio - Front Panel LEDs and connectors.............. 2-22
iDEN Monitor Unit (iMU/EAS) Indicators ...................................... 2-24
R-2660 iDEN Test Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

Base Radio Tests ......................................................................... 2-27
Drive Test Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29

Site Performance Testing using Drive Test Application ............... 2-29
Alarm Traps to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

Alarm Severity .............................................................................. 2-30
Alarm Severity Filter .................................................................... 2-30
Alarm Traps Message Content ................................................ 2-31
ACG Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32

ACG Physical Links...................................................................... 2-32
ACG Reliable Logical Links.......................................................... 2-32
Communication Link Failures. . . . . . . . . . . . . . . . . . . . . . . . 2-33
EBTS Subsystem
ii
SR 16.0
6881012Y79-B
23-Feb-09
Table of Contents
Types of Links .............................................................................. 2-33
ACG Fault Recovery .................................................................... 2-33
Recovery from PCCH Base Radio Failures . . . . . . . . . . . . . 2-34

BR Supporting PCCH Fails .......................................................... 2-34
Recovery from ACG Failures . . . . . . . . . . . . . . . . . . . . . . . . 2-35

ACG Failure Recovery ................................................................. 2-35
Base Radio Controller States . . . . . . . . . . . . . . . . . . . . . . . 2-36

General State Definitions ............................................................. 2-36
Base Radio Controller (BRC) States . . . . . . . . . . . . . . . . . . 2-37

State Management within the ACG .............................................. 2-38
Troubleshooting RF-related Problems . . . . . . . . . . . . . . . . 2-40

EBTS Equipment-related Problems . . . . . . . . . . . . . . . . . . . 2-41
Chapter 3
EBTS Troubleshooting
Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Supplemental Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Resolving Hardware Issues . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
High Stability Oscillator (HSO) Failure . . . . . . . . . . . . . . 3-5
GPS Problem - 0 Tracked Satellites . . . . . . . . . . . . . . . 3-10
Multiple Momentary FREE RUN Events . . . . . . . . . . . . 3-19
Audio Problems Related to the Antenna . . . . . . . . . . . 3-22
Duplex Wattmeter VSWR Alarm Problem . . . . . . . . . . . 3-24
EBTS 5MHZ/iPPS Signal Integrity Test for EBRC
and Quad BR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Incorrectly Programmed ExBRCs FSB . . . . . . . . . . . . . 3-35
Resolving Visibility Issues to the OMC-R . . . . . . . . . . . . . . 3-37
Resolving Connectivity Issues to other Network
Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Resolving Download Issues . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Base Radio (BR) TX Initialization/Diagnostic Testing
Failures and Possible BR Application Code Download
Issue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Resolving Configuration Issues . . . . . . . . . . . . . . . . . . . . . . 3-43
Newly Installed BRs Do Not Come In Service Ethernet Loop Carrier Limit Exceeded . . . . . . . . . . . . . 3-43
Newly Installed BRs Not Keying Up After Site
Download - 5MHz/1PPS Loop Overload . . . . . . . . . . . . 3-46
Resolving Provisioning Issues. . . . . . . . . . . . . . . . . . . . . . . 3-49
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
iii
Table of Contents
Resolving Loss or Disruption of Service Issues . . . . . . . . 3-50
Resolving Database Issues. . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
Resolving Billing Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52
Resolving Statistics Issues. . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
Appendix A
EBTS GPS Troubleshooting Information
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Introduction ................................................................................... A-2
Scope ............................................................................................ A-2
GPS Hardware .............................................................................. A-2
GPS Failures that cause EBTS Reset . . . . . . . . . . . . . . . . . . A-3

No GPS Lock ................................................................................ A-3
Loss of GPS Lock ......................................................................... A-3
Critical GPS Fault.......................................................................... A-3
Traps and Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

[201] ACG Reset ........................................................................... A-4
[305] TFR/SRI Detected Alarm...................................................... A-4
[306] GPS Problem-0 Tracked Satellites....................................... A-4
[320] ACG Failed to Achieve GPS Sync ....................................... A-4
[313] ACG Freerun Timeout .......................................................... A-5
[314] HSO 1PPS Missing .............................................................. A-5
[316] HSO Phase Not Locked ....................................................... A-5
[317] Bad Original Position in GPSR............................................. A-5
[318] HSO Frequency Not Locked ................................................ A-6
[319] HSO Failed........................................................................... A-6
GPS SM transitions with reason [901]........................................... A-6
Immediate switchover (30 minutes or less) ................................... A-6
Index
EBTS Subsystem
iv
SR 16.0
6881012Y79-B
23-Feb-09
List of Procedures
TO
TO
TO
TO
TO
TO
TO
TO
TO
TO
Access the iDEN Technical Training Course Catalog ...................................................... 1-5

Resolve the iSC HSO Failure Issue at the EBTS Site ...................................................... 3-7
Resolve the [306] GPS Problem - 0 Tracked Satellites Issue at the EBTS Site .......... 3-13
Troubleshoot a Suspected Bad GPS Antenna Signal .................................................... 3-15
Troubleshoot a Suspected Bad iSC for a GPS Satellite Tracking Problem.................... 3-17
Resolve Antenna Issues at the EBTS Site ..................................................................... 3-22
Test the Terminators ...................................................................................................... 3-28
Test the Signal Integrity .................................................................................................. 3-30
Change the Affected Register on the ExBRC to its Correct Value ................................. 3-35
Resolve Single/QUAD Channel BR Diagnostic Failure Issue......................................... 3-41
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
List of Procedures
NOTES...
EBTS Subsystem
vi
SR 16.0
6881012Y79-B
23-Feb-09
List of Figures
Figure 1-1
Figure 1-2
Figure 1-3
Figure 1-4
Figure 1-5
Figure 1-6
Figure 2-1
Figure 2-2
Figure 2-3
Figure 2-4
Figure 2-5
Figure 2-6
Figure 2-7
Figure 2-8
Figure 2-9
Figure 2-10
Figure 2-11
Figure 3-1
Figure 3-2
Figure 3-3
Figure 3-4
Figure 3-5
Figure 3-6
iDEN System Diagram ...................................................................................... 1-6

Quad2 Base Radio .......................................................................................... 1-12
ACG/iSC and iMU/EAS Block Diagram........................................................... 1-15
BR Block Diagram ........................................................................................... 1-16
Duplexer RFDS Block Diagram....................................................................... 1-17
Antenna Diplexer Block Diagram .................................................................... 1-18
Alarm Display .................................................................................................. 2-12
iSC2 Front Panel ............................................................................................. 2-13
iSC3 Front Panel ............................................................................................. 2-15
Single Channel BR Controller Module Front Panel ......................................... 2-17
QUAD Channel BR Exciter/Controller Module Front Panel............................. 2-18
Quad2 Base Radio - Components .................................................................. 2-22
Power Amplifier LEDs ..................................................................................... 2-23
Transceiver LEDs and Connectors ................................................................. 2-23
iMU Front Panel .............................................................................................. 2-24
EAS Front Panel.............................................................................................. 2-25
EAS2 Front Panel............................................................................................ 2-25
HSO Failure Event messages for Standby ACG using the iSC2
(iSC3 would be similar) ..................................................................................... 3-5
Event messages for Active ACG Tracking 0 Satellites & Free Running
for More Than 4 Hours (shown for iSC2; iSC3 similar) ................................... 3-12
Event messages for Active ACG Experiencing Multiple Momentary
FREERUN Started & Ended (shown for iSC2; iSC3 similar)........................... 3-20
Site Reference - 25% and 75% Duty Cycle Pulse Mask ................................. 3-32
Signal Examples.............................................................................................. 3-33
BRC error log report for a single channel BR (other BRs would be similar).... 3-40
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
vii
List of Figures
NOTES...
EBTS Subsystem
viii
SR 16.0
6881012Y79-B
23-Feb-09
List of Tables
List of Tables
Table 1
Table 2
Table 3
Table 4
Table 2-1
Table 2-2
Table 2-3
Table 2-4
Table 2-5
Table 2-6
Table 2-7
Table 2-8
Table 2-9
Table 2-10
Table 2-11
Table 2-12
Table 2-13
Table 2-14
Table 3-1
Supplemental Publications ................................................................................. xiv

Disclosure Table................................................................................................ xxii
Manual Revision Details................................................................................... xxiii
Contributors...................................................................................................... xxiv
Network Status Indicators ............................................................................... 2-14
System Status Indicators................................................................................. 2-15
Reference Status Indicators ............................................................................ 2-15
iSC3 Front Panel Indicators ............................................................................ 2-16
Single Channel BRC Indicators....................................................................... 2-17
QUAD Channel Ex/BRC Indicators ................................................................. 2-19
iMU Indicators ................................................................................................. 2-24
EAS Indicators................................................................................................. 2-25
EAS2 Indicators............................................................................................... 2-26
Alarm Severity Levels...................................................................................... 2-30
Data Communication Signal Transport Links .................................................. 2-32
Data Links ....................................................................................................... 2-32
BRC Device State Management Details ......................................................... 2-36
BRC States...................................................................................................... 2-37
General Troubleshooting Symptom/Cause/Action Table ................................ 3-33
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
ix
List of Tables
NOTES...
EBTS Subsystem
x
SR 16.0
6881012Y79-B
23-Feb-09
List of Changed Pages
The table below lists new or changed information, of a technical nature, that has been added or changed
since the previous release of this document.
Chapter
Section
Type of Change
About this manual . . . .
Updated references to SR 16.0.
Chapter 1
Purpose and Focus
Chapter 2
General EBTS Troubleshooting Strategies

Deleted: J2300 Protocol Analyzer section.
Chapter 3
Resolving Hardware Issues
Inserted: Audio Problems Related to the

Antenna scenario.
Inserted: Duplex Wattmeter VSWR Alarm
Problem scenario.
Inserted: EBTS 5MHZ/iPPS Signal
Integrity Test for EBRC and Quad BR
scenario.
Inserted: Incorrectly Programmed
ExBRCs FSB scenario.
Deleted: Noted Increase of BRC 55001
Alarms scenario.
Deleted: Background Download may Fail
in AFR Mode scenario.
Deleted: Stats to not Upload on iSC2 in
AFR Mode scenario.
Resolving Statistics Issues
Deleted: EBTS Site Not Reporting ecell

Statistics to OMC-R scenario.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
xi
List of Changed Pages

NOTES...
EBTS Subsystem
xii
SR 16.0
6881012Y79-B
23-Feb-09
About this manual....

This chapter of the guide describes the guide in general terms. The major
topics of this chapter include:
Purpose
The intended content of the guide
How the guide is to be used
Who is to use the guide
Other reference material that supports information in this guide
Elements in the appearance of the guide and their meaning
General safety guidelines
The changes to the guide over time
Who helped produce and validate information in the guide
The purpose of this manual is to provide information to facilitate troubleshooting of the SR 16.0 Enhanced Base Transceiver System (EBTS) RF
subsystem with a focus on the following EBTS components:
Access Controller Gateway (ACG) using the integrated Site Controller

(iSC) platform; either Second Generation iSC (iSC2) or Third Generation
iSC (iSC3)
Base Radios (BRs)
RF Distribution System (RFDS)
This manual addresses problems in a single urban.

The EBTS Troubleshooting Guide assists users to:
Identify, verify, and isolate trouble in the EBTS
Obtain and use data relevant to troubleshooting
Employ strategies to diagnose and troubleshoot EBTS problems
Recognize frequent problems in the EBTS
Distinguish when a problem appearing to be an EBTS issue may be related

to another network element or transport component
Restore functionality/operation of the EBTS
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
xi
Audience Profile
Audience Profile
Tasks and procedures included should be performed by senior (second level)

support personnel who are actively involved in the day-to-day technical activities required to maintain system functionality.
EBTS Subsystem
xii
SR 16.0
6881012Y79-B
23-Feb-09
Customer Network Resolution Center (CNRC)
Customer Network Resolution Center (CNRC)
The Customer Network Resolution Center (CNRC) is a integral part of the

network support process.
Before performing any major changes or optimizations on the system, please
contact the CNRC. Notify the CNRC with the nature of and schedule for the
change. This will enable the CNRC to have the correct technical support
engineers on call in case they are needed.
Please refer to the Customer Guide to iDEN Customer Network Resolution
Center (CNRC) (WP2000-003) for more information regarding:
Procedures for calling the CNRC
Classification of trouble tickets
The escalation processes
This document is located on the iDEN extranet Web site at the following
URL:
http://mynetworksupport.motorola.com
The CNRC can be contacted at the following telephone numbers:
United States and Canada
1-800- 499-6477
International
1-847-704-9800
Note Toll-free international access codes are available for many locations.
Please refer to Appendix E of the Customer Guide to iDEN Customer
Network Resolution Center (WP2000-003) for a list of these access
codes and dialing instructions.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
xiii
Related Manuals
Related Manuals
The following publications may be required to supplement the information

contained in this guide.
Table 1
Supplemental Publications
Part Number
Title
68P81131E90
Guide to Motorola Acronyms and Terms
68P81098E05
iDEN Integrated Site Controller System Manual
68P80801E30
iDEN Gen 3 Site Controller System Manual
68P80801E35
iDEN Enhanced Base Transceiver System

(EBTS)
Volume 1 of 3 System Installation and
Testing
Volume 2 of 3 Base Radios
Volume 3 of 3 RF Distribution Systems
68P80801B75
iDEN Radio Frequency Interference
68P81001Y55
iDEN Ethernet Analyzer Detective Software

Users Manual
6871000P02
iDEN System Overview and Functional

Description
6880309F16
R-2660 iDEN Digital Communications System

Analyzer Operators Manual
Note
The Operators Manual is supplied with the R-2660 and is not

available online. A CD-ROM version, 6880309F17, can be ordered from
Motorola International Parts via 1-800-422-4210
asce16
Note
SR 16.0 Alarm & State Change Events

This Alarm & State Change Events documentation is in a ZIP file.
WP2003-014
IDEN EBTS Fan Maintenance Plan
WP2001-010
iDEN EBTS Total Site Maintenance
WP2003-011
RF Statistics and Solutions, RF Link Optimization
WP2003-008
Drive Test Data Collection and Analysis
WP05008
900 Quad EBTS Multi-Sector Rack Configuration
WP2002-021
Understanding iDEN System Fault Tolerance
WP07003
J2300D (Window Based) Set Up Procedure
EBTS Subsystem
xiv
SR 16.0
6881012Y79-B
23-Feb-09
Related Manuals
Table 1
Supplemental Publications (continued)
Part Number
Title
WP07004
Managing AFR QoS
WP06004
Installing and Using Ethereal to Capture EBTS

Traces
WP2002-025
EBTS Backhaul: Frame Relay DS0 Requirements
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
xv
Manuals Online
Manuals Online
This guide is available on the World Wide Web at My Network Support, the
iDEN customer site. This site was created to provide secure access to critical
iDEN infrastructure information. This Web site features a library of iDEN
infrastructure technical documentation such as bulletins, system release
documents, and product manuals.
The documents are located on the secured extranet Web site at the following
URL:
https://mynetworksupport.motorola.com
For information on obtaining an account on this site, go to the following URL:
https://membership.motorola.com/motorola
EBTS Subsystem
xvi
SR 16.0
6881012Y79-B
23-Feb-09
Reporting Manual Errors
Reporting Manual Errors
If you locate an error or identify a deficiency in this guide, please take the
time to contact us at the following email address:
tpid23@motorola.com
Be sure to include your name, fax or phone number, the complete guide title
and part number, the page number where the error is located, and any
comments you may have regarding what you have found.
Thank you for your time. We appreciate any comments from the users of our
manuals.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
xvii
Conventions
Conventions
Software
submenu commandsTable > Table Designer
new termsmobile subscriber
keystrokesCtrl+Alt+Delete, Return
mouse clicksclick, double-click
user inputType delete
screen outputDAP is starting....
Hardware
CD-ROM
Safety
This guide contains safety notices (alerts). Alerts are based on the standards
that apply to graphics on Motorola equipment. Specific procedural notices are
stated in the procedures as required and have specific visual representations.
The representations are:
DANGER
INDICATES AN IMMINENTLY HAZARDOUS SITUATION

WHICH, IF NOT AVOIDED, WILL RESULT IN DEATH OR
SERIOUS INJURY.
WARNING
Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.
CAUTION
Indicates a potentially hazardous situation which, if not

avoided, could result in minor or moderate injury.
CAUTION
Without the alert symbol indicates a potentially hazardous
situation which, if not avoided, may result in property damage.
Important
Indicates an item of the essence of a topic that is indispensable.

Note Indicates something of notable worth or consequence.
EBTS Subsystem
xviii
SR 16.0
6881012Y79-B
23-Feb-09
General Safety
General Safety
Important
Remember Safety depends on you!

General safety precautions must be observed during all phases of
operation, service, and repair of the equipment described in this
manual. Failure to comply with these precautions or with specific
warnings elsewhere in this manual violates safety standards of design,
manufacture, and intended use of the equipment.
You must heed the safety precautions and warnings listed in the product
manuals for your equipment. Any individual using or maintaining the
product(s), should follow these warnings and all other safety precautions
necessary for the safe operation of the equipment in your operating
environment. Motorola, Inc. assumes no liability for failure to comply with
these requirements.
Keep Away From

Live Circuits
DANGER
HAZARDOUS VOLTAGE, CURRENT, AND ENERGY LEVELS

ARE PRESENT IN THIS PRODUCT. POWER SWITCH
TERMINALS CAN HAVE HAZARDOUS VOLTAGES PRESENT
EVEN WHEN THE POWER SWITCH IS OFF. DO NOT OPERATE
THE SYSTEM WITH THE COVER REMOVED. ALWAYS
REPLACE THE COVER BEFORE TURNING ON THE SYSTEM.
Operating personnel must:
Not remove equipment covers. Only Factory Authorized Service Personnel

or other qualified maintenance personnel may remove equipment covers for
internal subassembly, or component replacement, or any internal
adjustment.
Not replace components with power cable connected. Under certain

conditions, dangerous voltages may exist even with the power cable
removed.
Always disconnect power and discharge circuits before touching them.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
xix
General Safety
Ground the
Equipment
To minimize shock hazard, the equipment chassis and enclosure must be

connected to an electrical earth ground. The power cable must be either
plugged into an approved three-contact electrical outlet or used with a threecontact to two-contact adapter. The three-contact to two-contact adapter must
have the grounding wire (green) firmly connected to an electrical ground
(safety ground) at the power outlet. The power jack and mating plug of the
power cable must meet International Electrotechnical Commission (IEC)
safety standards.
Electro-Static
Discharge
Motorola strongly recommends that you use an anti-static wrist strap and a
conductive foam pad when installing or upgrading the system. Electronic
components, such as disk drives, computer boards, and memory modules, can
be extremely sensitive to Electro-Static Discharge (ESD). After removing the
component from the system or its protective wrapper, place the component
flat on a grounded, static-free surface, and in the case of a board, componentside up. Do not slide the component over any surface.
If an ESD station is not available, always wear an anti-static wrist strap that is
attached to an unpainted metal part of the system chassis. This will greatly
reduce the potential for ESD damage.
Do Not Operate In
An Explosive
Atmosphere
Do not operate the equipment in the presence of flammable gases or fumes.

Operation of any electrical equipment in such an environment constitutes a
definite safety hazard.
Do Not Service Or
Adjust Alone
Do not attempt internal service or adjustment, unless another person, capable

of rendering first aid and resuscitation, is present.
Use Caution When

Exposing Or
Handling a CathodeRay Tube
Breakage of the Cathode-Ray Tube (CRT) causes a high-velocity scattering of

glass fragments (implosion). To prevent CRT implosion, avoid rough
handling or jarring of the equipment. The CRT should be handled only by
qualified maintenance personnel, using approved safety mask and gloves.
Do Not Substitute
Parts Or Modify
Equipment
Because of the danger of introducing additional hazards, do not install

substitute parts or perform any unauthorized modification of equipment.
Contact Motorola Warranty and Repair for service and repair to ensure that
safety features are maintained.
EBTS Subsystem
xx
SR 16.0
6881012Y79-B
23-Feb-09
CMM Labeling and Disclosure Table
The Peoples Republic of China requires that Motorolas 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.
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 fieldreplaceable parts, such as battery modules, can have a different EFUP and are
marked separately.
The Disclosure Table (shown on the following page) is intended only to
communicate compliance with China requirements; it is not intended to
communicate compliance with EU RoHS or any other environmental requirements.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
xxi
Table 2
Disclosure Table
EBTS Subsystem
xxii
SR 16.0
6881012Y79-B
23-Feb-09
Revision History
Revision History
The following table lists revisions for this guide.

Table 3
Date
Manual Revision Details

Issue
Description of Changes
19-JUL-06 O
Original Release
30-Nov-07 A
Updated the manual to SR15.0.
23-Feb-09 B
Updated the manual to SR16.0.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
xxiii
Acknowledgements
Acknowledgements
We recognize and thank the following contributors to this guide:

Table 4
Contributors
Name
Carlos Carrillo
Michael Krol
Zave Domsky
Gil Scovill
Carolyn Frank
Mark Interrante
Elayne Tillman
Patti Rausch
Terry Lowe
EBTS Subsystem
xxiv
SR 16.0
6881012Y79-B
23-Feb-09
Chapter 1
Overview
In This Chapter
See Page
Topic
EBTS Subsystem Troubleshooting Overview. . . . . . . . . . . . 1-2

Purpose and Focus ........................................................................ 1-2
Troubleshooting Method ................................................................ 1-2
Scenario Categories....................................................................... 1-3
Restricted Access .......................................................................... 1-3
Target Audience ............................................................................. 1-4
Recommended Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

EBTS Subsystem Description . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Introduction .................................................................................... 1-6
EBTS Subsystem Components . . . . . . . . . . . . . . . . . . . . 1-7

Access Control Gateway ................................................................ 1-7
iDEN Monitor Unit/Environmental Alarm System ........................... 1-9
Base Radio..................................................................................... 1-9
Quad Base Radio ......................................................................... 1-10
Features..................................................................................... 1-10
Limitations ................................................................................ 1-10
Quad2 Base Radio ....................................................................... 1-11
RF Distribution System................................................................. 1-13
TX Combiner ............................................................................ 1-13
RX Signal Splitters/multicouplers ............................................ 1-13
Antenna Duplexer ..................................................................... 1-13
800/900 MHz Antenna Diplexer............................................... 1-14
EBTS Subsystem Components Block Diagrams.......................... 1-14
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
1-1
Overview
EBTS Subsystem Troubleshooting Overview

Purpose and Focus
Troubleshooting
Method
The purpose of this manual is to provide information to facilitate troubleshooting of the EBTS. Information will be current for SR 16.0. Components
of the EBTS for which troubleshooting will be provided are the: iSC2/iSC3
(site controller), BR (base radio), GPS (global positioning system), iMU/EAS
(iDEN monitor unit/environmental alarm system), and RFDS (Radio
Frequency Distribution System), and related interfaces. The EBTS Troubleshooting Guide will assist users to:
Identify, verify, and isolate trouble in the EBTS
Obtain and use data relevant to troubleshooting
Employ strategies to diagnose and troubleshoot EBTS problems
Recognize frequent problems in the EBTS
Distinguish when a problem appearing to be an EBTS issue may be related

to another network element or transport component
Restore functionality/operation of the EBTS
Troubleshooting is understood to be the set of activities performed on an

operational system to resolve problems that occur in normal operation.
Personnel responsible for troubleshooting are assumed to perform the
following tasks:
Clearly state the problem and symptoms
Verify and confirm the problem from a variety of data sources
Determine if the problem is known
Isolate the source of the problem
Plan how to resolve the problem considering access, impact, ability to

verify the resolution, etc.
Resolve the problem
Verify the resolution and subsequent proper operation
OR Escalate the problem
EBTS Subsystem
1-2
SR 16.0
6881012Y79-B
23-Feb-09
Overview
Scenario Categories
Troubleshooting procedures and scenarios presented in this manual are

recommendations to commonly encountered issues. Specific issues may be
encountered that vary from the conditions described. Therefore the resolutions cannot be guaranteed, but are intended to serve as a guide.
The following categories will be presented for scenarios describing
commonly used solutions:
Hardware issuesIssues related to the physical network element
Visibility issues to the OMC-RIssues related to communications

between the OMC-R (Operations and Maintenance Center-Radio) and the
network element
Connectivity issues to other network elementsIssues related to

communication between the network element and other elements in the
network
Download issuesIssues related to software and data distribution to

network elements from the OMC-R
Configuration issuesIssues related to changes to network elements

operating parameters
ProvisioningIssues related to adding or migrating subscribers in the

system
Loss or disruption of serviceIssues related to degradation or failure of

revenue-generating services
Database issuesIssues related to the integrity of network element

databases
Billing issuesIssues related to data and reporting for billing
Statistics issuesIssues related to data and reporting for performance

management
Note
Restricted Access
There may be instances where no solution has been identified. In those

cases, a notation will be made in that category. If or when information
becomes available, the category will be updated at a future date.
Some solutions that are presented in this manual may require access that is
restricted by Motorola. Contact the iDEN Customer Network Resolution
Center (CNRC) for assistance at:
US/Canada
+1-800-499-6477
All other International locations:
1-847-704-9800
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
1-3
Overview
Note
Target Audience
Toll-free international access codes are available for many locations.

Please refer to Appendix E of the Customer Guide to iDEN Customer
Network Resolution Center (WP2000-003) for a list of these access
codes and dialing instructions.
The information in this manual is designed to enhance the users ability to

troubleshoot the EBTS subsystem. Tasks and procedures included should be
performed by senior support personnel who are actively involved in the dayto-day technical activities required to maintain system functionality.
EBTS Subsystem
1-4
SR 16.0
6881012Y79-B
23-Feb-09
Overview
Recommended Training
Recommended Training
To maximize the effectiveness of this manual, it is strongly recommended that

the user complete the applicable Motorola-offered training courses prior to
performing the tasks presented.
For information related to your system release level, review the iDEN
Training Course Catalog which is available on the MyNetworkSupport web
site. To access it, follow the steps below.
TO
Access the iDEN Technical Training Course Catalog
Step
Action
Login to MyNetworkSupport at:

https://mynetworksupport.motorola.com/
The MyQuickLinks screen appears.
Scroll down to the section for iDEN technology.
On the right side of the page, click on iDEN Training Catalog.
Contact your local training coordinator for course enrollment information.

For questions on iDEN training, please call 847-576-2750.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
1-5
Overview
EBTS Subsystem Description

Introduction
The iDEN communications system encompasses a range of services that

deliver two-way radio communications, interconnect to wireline phone
service, mobile-to-mobile subscriber service and access to the Internet.
This troubleshooting guide focuses on the base station equipment that is
shared by Push-to-Talk two-way mobile service, interconnect service, and
packet data services. Figure 1-1 iDEN System Diagram on page 1-6 shows
the relationship of the EBTS subsystem to the rest of the iDEN system.
Figure 1-1
iDEN System Diagram
EBTS Subsystem
1-6
SR 16.0
6881012Y79-B
23-Feb-09
Overview
EBTS Subsystem Components
The EBTS subsystem provides the RF interface for the mobile subscribers
(MSs) as well as the T1/E1 serial data interface between the iDEN central
network that provides dispatch, interconnect, and packet data services.
All EBTS sites connect, via T1/E1 span lines, to the Digital Cross-connect
Switch (DCS) at the central network. The DCS routes control and MS call
traffic signals between the EBTS and the appropriate service subsystem.
In the iDEN system, the base station radios and associated control equipment
are contained in the EBTS or, more commonly, cell sites.
The EBTS site consists of the following components:
Access Control
Gateway
An Access Control Gateway (ACG), which uses the integrated Site

Controller (iSC) platform. Redundant ACGs/iSCs are usually equipped at
an EBTS site.
iDEN Monitor Unit/Environmental Alarm System (iMU/EAS)
One or more Base Radios (BRs)
An RF Distribution System (RFDS)
The Access Control Gateway (ACG) is the site controller and the communications gateway between an EBTS site and the central network. The ACG uses
either of two integrated Site Controller (iSC) platforms:
iSC3 - current platform
iSC2 - not available in new EBTS shipments, but still used in the field
The iSC discriminates between Dispatch, Interconnect and Packet Data calls
and routes the traffic accordingly. It also controls base radio timing and terminates transport facilities. Network infrastructure facilities (T1/E1s) are terminated at the iSC.
The iSC2 supports a maximum of 18 RF carriers in a site. Maximum capacity
is further derated if Split 3:1 and WiDEN features are enabled by an
additional three RF carriers for each feature.
The iSC3 can support a maximum of 36 carriers when configured for two
T1s or two E1s.
When the EBTS is configured as an omni site, the iSC3 supports up to 20

carriers. When the EBTS is configured as a 3-sector site, the iSC3 can
support up to 36 carriers, with a maximum of 20 carriers in any one sector.
Two ACGs/iSCs are recommended for redundant operation. These units are
software switchable (active-standby). Communication between the master
(active) and standby is initiated by the active controller. This redundancy
reduces maintenance and downtime in the event of an EBTS failure.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
1-7
Overview
The ACG/iSC allows an OMC-R operator to: perform tests to isolate faults
between the EBTS and the facilities (T1/E1), load new software, and remotely
switch over to the standby ACG.
(Refer to Figure 1-3 ACG/iSC and iMU/EAS Block Diagram on page 1-15.)
The ACG/iSC has the following interfaces:
Site Timing Reference - consisting of a Global Positioning System (GPS)

Receiver (GPSR) and High Stability Oscillator (HSO).
The HSO is frequency locked/synchronized to the GPS timing signals
output by the GPSR. The ACG/iSC derives a 5MHz/1PPS timing reference
signal from the HSO.
The 5MHz/1PPS output signal is distributed to all BRs at the EBTS site. All
BR RF local oscillators synchronize to the 5MHz/1PPS timing reference
signal.
Serial/parallel Data I/O interface - supports data communication between

the ACG/iSC and the iMU/EAS.
T1/E1 span line interface - provides PCM serial data channels/time slots
that carry control and call traffic between the EBTS and the central
network.
10Base2 (thinnet) Ethernet Local Area Network (LAN) interface - provides

data communication between ACG/iSC and the site BRs. This data
communication includes:
ACG/iSC sending BR control information and receiving BR alarm/

status information
ACG/iSC downloading code to the BRs
MS call traffic routing between ACG/iSC and the BRs
Note The ACG/iSC has an internal interface between the T1/E1 transport
and the Ethernet LAN that supports routing of MS traffic signals
between the central network and the BRs.
Refer to white paper EBTS Backhaul: Frame Relay DS0 Requirements

(WP2002-025), for information about configuring dual T1s and E1s. Refer
to white paper Managing AFR QoS (WP07004) for a list of the EBTS
statistics.
EBTS Subsystem
1-8
SR 16.0
6881012Y79-B
23-Feb-09
Overview
iDEN Monitor Unit/

Environmental
Alarm System
(Refer to Figure 1-3 ACG/iSC and iMU/EAS Block Diagram on page 1-15.)
Base Radio
(Refer to Figure 1-4 BR Block Diagram on page 1-16.)
The iDEN Monitor Unit/Environmental Alarm System (iMU/EAS) contains

the Environmental Alarm System (EAS). The iMU/EAS monitors the EBTS
site for alarms and reports them to the ACG which forwards them to the
OMC-R. Also the ACG/iSC and BR status/alarm information that is collected
by the ACG/iSC is applied to the iMU/EAS for reporting to the OMC-R.
The EBTS provides the Radio Frequency (RF) link between the land network
and the MSs. The Base Radios (BRs) perform the RF communications with
the MSs, sending both the control information and the compressed speech
over a radio channel. The radio channel consists of a 25 KHz TX and RX
carrier.
A Base Radio (BR) can be removed from the EBTS and replaced with a new
BR without taking the site off the air. The base radios and the radio link traffic
(voice and data) are controlled by the ACG/iSC over the Ethernet LAN.
BRs are either single channel units that provide a single 25 KHz RF carrier in
one physical unit or QUAD Channel BR that supports up to four 25 KHz RF
carriers in one physical unit. The QUAD BR can be software-configured from
the OMC-R for 1 to 4 carriers.
The single-channel BR provides reliable digital base radio capabilities in a
compact software-controlled design. Increased channel capacity is provided
through voice compression techniques and Time Division Multiplexing
(TDM). This mode, combined with voice compression techniques, provides
an increased channel capacity ratio of as much as 6 to 1. Both the receive and
transmit signals of the Base Radio are divided into 6 individual time slots.
Each receive slot has a corresponding transmit slot; this pair of slots
comprises a logical 25 KHz RF channel.
Each BR consists of the following components:
The Base Radio's DC Power Supply is capable of operating with input

voltages within the range of 41 V DC to 60V DC. The DC Power Supply
converts the 48V DC input to 28.6V DC, 14.2V DC, and 5.1V DC. These
voltages are distributed to the other Base Radio modules through the
backplane
Base Radio Controller (BRC) - controls the BR RF transmitter (TX) and

receiver (RX). The BRC has a 10Base2 Ethernet interface for
communication with the ACG/iSC
Exciter - provides low level TX RF output signal to drive the RF Power

Amplifier
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
1-9
Overview
Quad Base Radio
RF Power Amplifier (PA) - amplifies the low level TX RF signal from the
exciter. The RF PA provides the final TX RF power output to the RFDS and
TX antenna
Receiver - contains three receivers that provide RX antenna diversity
The Quad Base Radio provides efficient use of the frequency spectrum by
transmitting four 25 kHz channels over a 100 kHz wide band. Each Quad BR
can be remotely configured from the OMC-R for 1, 2, 3, or 4 RF carriers.
Since the Quad BR digitally combines four carriers internally, it eliminates
the need for high-loss external combiners. This results in a significant
reduction in transmit power losses.
The Quad BR can operate in either the 800 MHz or 900 MHz band.
Features
Four 25 kHz RF carriers in a single BR (must be contiguous channels)
Can be remotely configured for 1,2,3 or 4 carriers
Four 3x Receiver modules per Base Radio.
800 and 900 MHz Quad BRs can share the same antenna using a Diplexer.
The EBTS, using Quad BRs, can potentially be configured for 36 RF

carriers without any additional combining hardware. The iSC3 is required
to support 36 RF Carriers.
Limitations
PCCH Reassignment is only available if the PCCH BR and the redundant

BR are configured for the same number of RF carriers.
For example, if a Quad BR carrying the PCCH fails, the PCCH will be
reassigned only to another Quad BR configured with the same number of
carriers. If there is no other Quad BR with the same carrier configuration,
the cell will be out of service.
Quad BR must be configured for contiguous frequencies

The Quad BR requires RF carriers to be allocated with adjacent 25 kHz
channels. These adjacent channels must also be deployed in all co-channel
sites. It will require frequency reuse patterns to be re-drawn and system
wide retunes.
EBTS Subsystem
1-10
SR 16.0
6881012Y79-B
23-Feb-09
Overview
Adjacent channel interference

Adjacent channel interference results from interference between two or
more channels due to splatter effects. A strong uplink signal from a close in
subscriber can interfere with adjacent channels that are on the outer limits
of the cells coverage area. Subscriber software changes provide additional
power cutback.
Quad2 Base Radio
The dual band Quad2 BR provides the flexibility to change operating

frequency bands simply by changing the operating frequency in the site
configuration file without the need to replace the base radio. The dual band
Quad2 BR is functionally the same as the Quad BR with the exception that it
can be software configured for either 800 or 900 MHz band.
The dual band Quad2 BR hardware supports up to 6 iDEN carriers. However,
the call processing software limits the Quad2 BR to a maximum of 4 RF
carriers. The dual band Quad2 BR uses the same air interface and FNE
interface protocols as Quad BR. When configured to operate in the 900 MHz
band, the dual band Quad2 BR will support all the services that are currently
supported on the 900 MHz band, i.e. telephone interconnect, circuit data etc.
The dual band Quad2 BR defaults to the 800 MHz unless explicitly told
otherwise through the use of a new test application MMI command.
The ACG validates the BR type and band based upon cabinet and position.
For all configuration errors it will report an alarm to the OMC-R. The dual
band Quad2 BR interfaces with the ACG via the back panel 10Base2 Ethernet
link and follow the existing ACG -BRC procedures and message interfaces.
The dual band Quad2 BR provides a local console interface similar to Quad
BR.
Physically, the Quad2 BR is significantly different than the other iDEN BR
platforms. A transceiver module integrates the functionality of the base radio
controller, exciter, and receiver modules. The power supply and PA are also
significantly different. The Quad2 BR is smaller (3 rack units compared to 5
RUs for the legacy BRs) and lighter (approximately 45 pounds).
The Quad2 Base Radio is shown below:
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
1-11
Overview
Figure 1-2
Quad2 Base Radio
Refer to the EBTS Base Radios - Volume 2 - Enhanced Base Transceiver

System (EBTS) - Volume 2 of 3 (68P80801E35) for information related to the
operating characteristics of the BR, Quad, and Quad2.
EBTS Subsystem
1-12
SR 16.0
6881012Y79-B
23-Feb-09
Overview
RF Distribution
System
The EBTS site antennas provide the means for radiation and reception of the
RF energy that is the Radio Link.
The EBTS site antenna configurations will vary with each installation. Each
EBTS cell requires RF antennas for TX and RX signals. Site antenna configurations include three RX antennas for each omni or sector RF coverage area.
Sites may be configured with a separate TX antenna for each omni or sector
RF coverage area, but typically the site antennas are configured so that the TX
signals are applied to one or more of the RX antennas. Therefore a site may
have either four or three antennas for each omni or sector RF coverage area.
An RF Distribution System (RFDS) can include the following:
hybrid TX combiners
RX signal splitters/multicouplers
antenna duplexers
antenna diplexed filters for EBTS sites with 800 MHz and 900 MHz
BRs
(Refer to Figure 1-5 Duplexer RFDS Block Diagram on page 1-17).

TX Combiner
The EBTS is configured with hybrid TX combiners. The TX combiners
combine the high power TX RF carrier signals from more than one BR power
amplifier output into a single composite high power TX RF signal for application to the antenna.
RX Signal Splitters/multicouplers
The RX RF antenna signals, from the three antennas, are applied to the RX
signal splitters/multicouplers. The splitters/multicouplers split and amplify
the RX antenna input signals into multiple outputs for each RX antenna. An
RX signal output for each of the three RX antennas is routed from the
splitters/multicouplers to the corresponding RX input of each BR.
Antenna Duplexer
The RFDS may be equipped with antenna duplexers that allow the combined
TX signal and RX signal to share a common antenna.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
1-13
Overview
800/900 MHz Antenna Diplexer

At a dual band (800/900 MHz) EBTS site, the RFDS in one of the RF cabinets
contains three 800/900 MHz antenna diplexers. Each diplexer has a common
dual band (800/900 MHz) TX/RX antenna port, an 800 MHz TX/RX port,
and a 900 MHz TX/RX port.
The 800/900 MHz antenna diplexer allows the TX/RX signals of 800 MHz
BRs and the TX/RX signals of 900 MHz BRs to share a common antenna.
The 800/900 MHz antenna diplexer filtering is as follows:
Only 800 MHz band TX/RX signals pass between the antenna port and the
800 MHz TX/RX port.
Only 900 MHz band TX/RX signals pass between the antenna port and the
900 MHz TX/RX port.
800 MHz band TX/RX signals are isolated from the 900 MHz band RF
equipment
900 MHz band TX/RX signals are isolated from the 800 MHz band RF
equipment
(Refer to Figure 1-6 Antenna Diplexer Block Diagram on page 1-18.)
EBTS Subsystem
Components Block
Diagrams
The following figures show simplified block diagrams of the EBTS

subsystem components.:
Figure 1-3 ACG/iSC and iMU/EAS Block Diagram on page 1-15
Figure 1-4 BR Block Diagram on page 1-16
Figure 1-5 Duplexer RFDS Block Diagram on page 1-17
Figure 1-6 Antenna Diplexer Block Diagram on page 1-18
EBTS Subsystem
1-14
SR 16.0
6881012Y79-B
23-Feb-09
Overview
Figure 1-3
ACG/iSC and iMU/EAS Block Diagram

GPS
Ant A
1PPS
GPSR
DPLL & SIGNAL

COMBINER
5 MHz/1PPS
5MHz/1PPS
(To BRs)
HSO
T1/E1
SERIAL
LINE
INTERFACE
T1/E1
(To/From
DCS)
COMMUNICATIONS
PROCESSOR
AND
CONTROL &
STATUS/ALARM
PROCESSOR
PARALLEL
INTERFACE
ETHERNET
INTERFACE
10Base2
(To/From
BRs)
ACG/iSC
A
ALARM I/O
GPS
Ant B
1PPS
GPSR
DPLL & SIGNAL

COMBINER
5 MHz/1PPS
HSO
T1/E1
SERIAL
LINE
INTERFACE
COMMUNICATIONS
PROCESSOR
AND
CONTROL &
STATUS/ALARM
PROCESSOR
PARALLEL
INTERFACE
ETHERNET
INTERFACE
10BASE2
ACG/iSC
B
ALARM I/O
Alarm I/O (From/To

Site, Cabinet, User
Devices)
iMU/EAS
PARALLEL
INTERFACE
ALARM
I/O
LOGIC
ALARM I/O B
PARALLEL
INTERFACE
LEGEND:
Control &
Status/Alarm Bus
Data Bus
ALARM I/O A
T-connection
NOTE:
1. DC operating power is intentionally not shown in this diagram.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
1-15
Overview
Figure 1-4
BR Block Diagram
Diversity Receivers
(Note 2)
PRE-AMP
& FILTER
RX 1
RX1 DATA & CLK
MIXER
I-F AMPS &

FILTERS
DET
MIXER
I-F AMPS &

FILTERS
DET
MIXER
I-F AMPS &

FILTERS
DET
LO INJ
RX Antenna
Signals
(From RFDS)
PRE-AMP
& FILTER
RX 2
RX1 DATA & CLK
LO INJ
PRE-AMP
& FILTER
RX 3
VCO/
SYNTH
10Base2
(To/From BRs)
RX3 DATA & CLK
LO INJ
Base Radio
Controller
(BRC)
2.4 MHz
10BASE2
ETHERNET
INTERFACE
10Base2
(To/From
ACG/iSC)
COMMUNICATIONS
PROCESSOR
AND
CONTROL &
STATUS/ALARM
PROCESSOR
RX DSP
&
ADC
1PPS &
SLOT TIMING
16.8 MHz
TX DSP
TX DATA & CLK
5MHz/1PPS
(To BRs)
5 MHz/1PPS
5MHz/1PPS
(From
ACG/iSC)
16.8 MHz
PLL & VCO
1PPS REF
2.4 MHz
1PPS &
SLOT TIMING
Power Amplifier
Exciter
VCO/
SYNTH
(Note 3)
TX
To Antenna
(Via RFDS)
COMBINER
FINAL
RF AMPS
PHASE
SPLITTER
LINEAR
RF AMP
MODULATOR
DAC &
FILTER/AMP
RF FEEDBACK
NOTES:
1. DC operating power is intentionally not shown in this diagram.
2. A single channel Base Radio (BR) has one set of diversity receivers. A QUAD
channel BR has four sets of diversity receivers; one set per RF channel.
3. A single channel Base Radio (BR) has a separate exciter module as shown in
this diagram. A QUAD channel BR has the exciter together with the BRC in
one module. The QUAD channel BR exciter contains four sets of exciter
circuits; one set per RF channel.
EBTS Subsystem
1-16
AMP &
FILTER
LEGEND:
Control &
Status/Alarm Bus
Data Bus
T-connection
SR 16.0
6881012Y79-B
23-Feb-09
Overview
Figure 1-5
Duplexer RFDS Block Diagram
ANT 1
ANT 2
ANT 3
ANT
ANT
ANT
Duplexer
Duplexer
Duplexer
TX
TX
TX
RFDS
TX 1
TX 2
RX
RX
TX 3
RX
RX 1
RF Combiners
RX 2
RX 3
RF Splitters/Multicouplers
RX 1
TX
Base
Radio
RX 2
RX 3
RX 1
TX
Base
Radio
RX 2
RX 3
RX 1
TX
Base
Radio
RX 2
RX 3
RX 1
TX
Base
Radio
RX 2
RX 3
RX 1
TX
Base
Radio
RX 2
RX 3
NOTES:
1. This diagram is for an omni antenna configuration or one sector of a sector antenna configuration.
Other sectors would be similar, but with separate BRs, RFDS and antennas for each sector.
2. Each omni/sector antenna configuration has three antennas for receiver antenna diversity. TX signal
combining and routing determines how the TX signals are distributed among the three antennas.
3. Antenna configurations are site dependent and may vary from one site to another.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
1-17
Overview
Figure 1-6
Antenna Diplexer Block Diagram
ANT 1
ANT 2
ANT 3
ANT
Diplexer
900
ANT
800
Diplexer
900
ANT
800
Diplexer
900
800
ANT
ANT
ANT
Duplexer
Duplexer
Duplexer
TX
TX
TX
RX
TX 1
TX 2
TX 3
RF Combiners
RX
RX 1
RX
RX 2
RX 3
RX 1
TX Output Signals
(From 800 MHz BRs)
800 MHz
RFDS
RX 2
ANT
ANT
ANT
Duplexer
Duplexer
Duplexer
TX
TX
TX
RX
TX 1
TX 3
RF Combiners
RX 3
RX Antenna Signals
(To 800 MHz BRs)
RX 1
TX Output Signals
(From 900 MHz BRs)
RX
RX 2
RX 3
RX 1
EBTS Subsystem
1-18
TX 2
RX
900 MHz
RFDS
RX 2
RX 3
RX Antenna Signals
(To 900 MHz BRs)
SR 16.0
6881012Y79-B
23-Feb-09
Chapter 2
In This Chapter
See Page
Topic
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
iDEN Open Problem List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
About MMI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Field Replaceable Units (FRU) 5
Site Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
General EBTS Troubleshooting Strategies . . . . . . . . . . . . . . 2-7
Data Collection ...............................................................................
OMC Events & Alarms ......................................................
Console Logs ....................................................................
T1 Tester ...........................................................................
Ethernet Capture ...............................................................
Drive Test Application .......................................................
2-7
2-7
2-7
2-8
2-8
2-8
EBTS Troubleshooting Resources. . . . . . . . . . . . . . . . . . . . 2-10

Operations and Maintenance Center 10
Events and Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
EBTS Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Integrated Site Controller (iSC) Indicators.................................... 2-13
iSC2 Front Panel Indicators ............................................ 2-13
iSC3 Front Panel Indicators ............................................ 2-15
Base Radio (BR) Indicators..........................................................
Single Channel BRC .......................................................
QUAD Channel Ex/BRC..................................................
Transceiver......................................................................
Power Amplifier ...............................................................
Power Supply ..................................................................
Fan Assembly..................................................................
SR 16.0
23-Feb-09
2-17
2-17
2-18
2-21
2-21
2-21
2-21
EBTS Subsystem
6881012Y79-B
2-1
Quad2 Base Radio - Front Panel LEDs and connectors.............. 2-22

Power Amplifier LEDs ..................................................... 2-22
Transceiver LEDs and connectors .................................. 2-23
iDEN Monitor Unit (iMU/EAS) Indicators ......................................
iMU Front Panel Indicators..............................................
EAS Front Panel Indicators .............................................
EAS2 Front Panel Indicators ...........................................
2-24
2-24
2-25
2-25
R-2660 iDEN Test Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

Base Radio Tests ......................................................................... 2-27
Base Radio BER Floor and Sensitivity Verification ......... 2-27
Drive Test Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29

Site Performance Testing using Drive Test Application ............... 2-29
Alarm Traps to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

Alarm Severity .............................................................................. 2-30
Alarm Severity Filter .................................................................... 2-30
Alarm Traps Message Content ................................................ 2-31
ACG Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32

ACG Physical Links...................................................................... 2-32
ACG Reliable Logical Links.......................................................... 2-32
Communication Link Failures. . . . . . . . . . . . . . . . . . . . . . . . 2-33

Types of Links .............................................................................. 2-33
Physical Links.................................................................. 2-33
ACG Reliable Logical Links............................................. 2-33
ACG Fault Recovery .................................................................... 2-33
Base Radio Failure.......................................................... 2-33
Recovery from PCCH Base Radio Failures . . . . . . . . . . . . . 2-34

BR Supporting PCCH Fails .......................................................... 2-34
Recovery from ACG Failures . . . . . . . . . . . . . . . . . . . . . . . . 2-35

ACG Failure Recovery ................................................................. 2-35
Base Radio Controller States . . . . . . . . . . . . . . . . . . . . . . . 2-36

General State Definitions ............................................................. 2-36
Base Radio Controller (BRC) States . . . . . . . . . . . . . . . . . . 2-37

State Management within the ACG .............................................. 2-38
Troubleshooting RF-related Problems . . . . . . . . . . . . . . . . 2-40

EBTS Equipment-related Problems . . . . . . . . . . . . . . . . . . . 2-41
EBTS Subsystem
2-2
SR 16.0
6881012Y79-B
23-Feb-09
Introduction
Introduction
This chapter provides overall strategies for troubleshooting the Enhanced

Base Transceiver System.
The information present here presumes that the reader has attended the iDEN
System School and EBTS Operations and Maintenance training classes and is
knowledgeable of the troubleshooting methodologies taught in those classes.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-3
iDEN Open Problem List
iDEN Open Problem List
The iDEN Open Problem List (OPL) is a living document (Excel spreadsheet)
that is updated monthly. It lists the current, known software issues that are
related to bugs identified in System Releases (SRs) and/or patches along with
their workaround(s), if applicable. If the issue has been closed, i.e., resolved
with a deployed patch or new SR, the issue is noted as CLOSED.
It is recommended that you review this list on a monthly basis to obtain
workarounds to current issues you might encounter.
The iDEN Open Problem List is available on My Network Support. To locate
it, use the Advanced Search function on My Network Support by typing
*opl* in the Part Number text box.
EBTS Subsystem
2-4
SR 16.0
6881012Y79-B
23-Feb-09
About MMI Commands
About MMI Commands
Service technicians can communicate with the EBTS through the use of Man
Machine Interface (MMI) commands and a service computer. MMI
commands provide testing capabilities with access to alarm log files and
various diagnostic tests. MMI commands also provide a means to configure
the Site Control and RF Cabinets for various system tests.
Commonly used MMI commands pertaining to Base Radios are located in
Chapter 6 of the EBTS Volume 1 of 3 System Installation and Testing manual
(68P80801E35). All valid commands are described, along with the syntax,
definitions, and examples.
For a complete description of all MMI commands pertaining to the iSC, refer
to the following applicable iSC manual:
For iSC2, iDEN Integrated Site Controller System Manual (68P81098E05)
For iSC3, iDEN Gen 3 Site Controller System Manual (68P80801E30)
Field Replaceable Units (FRU)
For a guide to isolating failures to a Field Replaceable Unit (FRU), refer to

Chapter 7 in the EBTS Volume 1 of 3 System Installation and Testing manual
(68P80801E35).
EBTS Volume 2 of 3 Base Radios manual (68P80801E35) contains instructions for isolating Base Radio failures to the FRU level.
EBTS Volume 3 of 3 RF Distribution Systems manual (68P80801E35)
contains information that will aid in replacing RFDS FRUs.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-5
Site Maintenance
Site Maintenance
EBTS sites are built to specific mechanical and electrical standards that
support proper and reliable operation of EBTS equipment. EBTS site design
considerations include desired radio coverage, potential RF interference,
future site expansion, connectivity and power, site environment, local climate,
accessibility, and security. These sites initially serve the application well, but
may degrade over time due to a number of factors such as excessive
equipment population, excessive electrical loads, inadequate HVAC (Heating
Ventilation Air Conditioning) capacity, insufficient floor loading strength,
degraded grounding systems, unreliable T1 circuits, defective or compromised antenna systems, and perhaps encroachment by others. While there is
considerable customer involvement with initial site development, oftentimes a
long-term maintenance and inspection program is overlooked.
To establish a program of preventative maintenance a review of the Motorola
White Paper, iDEN EBTS Total Site Maintenance (WP2001-010), is recommended.
This document is intended to point out commonplace areas of failure in aging
EBTS sites and to recommend solutions. The service technician and site
manager must both remain proactive in inspecting EBTS sites and investigating even the smallest problem that can become a service-affecting catastrophe if left uncorrected. Even if the EBTS site itself remains unchanged
over time, the operating environment around the site may have changed
enough to seriously degrade site performance.
EBTS Subsystem
2-6
SR 16.0
6881012Y79-B
23-Feb-09
When troubleshooting the EBTS it is important to isolate the root cause using
a systematic approach.
Determine which services are affected: Interconnect, Dispatch, Packet

Data, or all three.
Determine which sites may be serving the unit(s) with the problem.
Determine if other units in the area are also experiencing the problem.
Determine if the issue is a hardware problem or software problem.
Data Collection
Download the test bed with the datafill parameters for the faulty site. If
the test bed experiences the same symptoms, check the datafill
parameters for incorrect values.
Drive test the affected area and collect site data.
Data collection is needed whenever a problem is to be escalated to Motorola.

The supporting data listed below can be very helpful in determining the cause
of the problem. Although more data collection may be required in some cases
with special debug mode on the EBTS to provide a better understanding of the
issue. The following are the recommended data collection methods:
OMC Events & Alarms
OMC event logs are the first recommended data to be investigated/
collected. By cross-referencing the EBTS, ACG, and BR events and alarms
with the ASCE (Alarm & State Change Events) documentation for the
applicable Software Release (SR), the site engineers can determine the
status and history of the site equipment. Also information regarding GPS
and other hardware, referenced in this troubleshooting guide, makes use of
OMC event logs.
Note Refer to SR16.0 Alarm & State Change Events documentation,
ASCE16.
The OMC operator can provide Event and Alarm information about the site.
equipment
Console Logs
The ACGs/iSCs and BRCs are equipped with a console port MMI (Man
Machine Interface) that can be connected to a service computer (i.e., PC).
A non-intrusive set of MMI commands are available on the BRC that will
help the service technician to isolate faults within the EBTS while the
EBTS is processing calls. There is also a set of iSC MMI commands
available, but not while the EBTS is processing calls.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-7
Although console log information is not documented and supported by

Motorola, it may provide some insight as to the internal status of the ACG
software and error messages when the problem/issue happens.
To capture ACG console logs, a service computer must be directly
connected to the console port on the Active ACG/iSC when the problem/
issue happens.
The service computer must be configured as follows:
Procomm or terminal emulation software that supports serial com

connection.
VT100 emulation
COM1 for com port
19200 Baud Rate
None for Parity Bit
8 for data bits
1 for stop bit

Once the connection is established, messages will be displayed on the
service computer. Start the screen capture and save to a file.
T1 Tester
The T1 tester is used to verify the quality of the T1 circuit and identify
errors on the T1 lines.
Ethernet Capture
Ethernet communication between the ACG/iSC and the BRs can provide
information including voice and control messages. Refer to Installing and
Using Ethereal to Capture EBTS Traces (WP06004A).
Drive Test Application
The drive test application software runs on a PC laptop. The PC I/O
interface is cabled to an iDEN Test Mobile radio. The drive test
application software in conjunction with the Test Mobile radio collects
and displays iDEN RF interface data. This data can be used to optimize the
network, resolve coverage issues, and monitor handover performance.
The drive test application trace can be a good information source for to
understand what the subscriber unit receives from the EBTS site radio
interface. Refer to the drive test application software documentation for
operation and configuration of the drive test application trace. For more
information about using a drive test application, refer to the Drive Test Data
Collection and Analysis (WP2003-008).
EBTS Site Indicators and Equipment Manuals

The LEDs in the Control and RF cabinets can be invaluable to the service
technician in isolating the faults within the EBTS. Refer to the
troubleshooting sections of the equipment manuals for assistance in
EBTS Subsystem
2-8
SR 16.0
6881012Y79-B
23-Feb-09
isolating the failure whenever any front panel indicators are illuminated.
See Table 1 Supplemental Publications on page -xiv for a list of manual
titles and part numbers.
R-2660 iDEN Test Set

The Motorola R-2660 iDEN Digital Communications System Analyzer is
programmed with special software to test the unique requirements of iDEN
equipment.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-9
EBTS Troubleshooting Resources
EBTS Troubleshooting Resources
Following are the resources available for troubleshooting the EBTS.
Operations and Maintenance Center
The Operations and Maintenance Center (OMC) provides the capability to

remotely monitor and maintain the iDEN network elements. The OMC
receives events and alarms from the various network elements and provides
the network operator a means of Loading, Configuring, and Isolating faults
within the iDEN network. The main network elements that the OMC has
control of are:
EBTS
DAP
BSC
APDs
MDGs
ISGs
IDACs
HA-iHLRs
The OMC supports the following functional areas:
Configuration Management
Event and Alarm Management
Fault Management
Performance Management
Security Management
Load Management
EBTS Subsystem
2-10
SR 16.0
6881012Y79-B
23-Feb-09
Events and Alarms
Events and Alarms
Event/Alarm management provides a mechanism at the OMC for managing

network element generated events/alarms routed to the OMC. Alarms appear
on an operator's terminal or a central alarm display. All operator actions
associated with alarms (seeing, handling, and clearing) will be recorded and
time stamped.
Having been informed of a fault by Event/Alarm management, the fault
management features enable an operator to pin-point the location of the fault
by running diagnostics and remote MMI commands.
For example, the operator can:
Put devices into service or out of service
Place a device into a state suitable for testing and verify if it is functioning
correctly by running diagnostic routine from the OMC
Issue control calls for maintenance purposes
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-11
Events and Alarms
Figure 2-1
Alarm Display
S ite S ta tu s D is p la y
EBTS Subsystem
2-12
SR 16.0
6881012Y79-B
23-Feb-09
EBTS Indicators
EBTS Indicators
The front panel indicators on various EBTS components provide a means for
monitoring operation of the EBTS equipment.
Integrated Site
Controller (iSC)
Indicators
The iSC front panel indicators provide a means of monitoring operation of the
iSC. These LEDs provide information on the status of the iSC controller, the
network, the T1/E1 interface, and Site Reference ISA circuits.
iSC2 Front Panel Indicators
The iSC2 front panel indicators provide a means for monitoring the operation
of the controller.
Figure 2-2 iSC2 Front Panel on page 2-13 shows the location of LED
indicators on the iSC2 front panel.
Figure 2-2
iSC2 Front Panel
Power
Network Status
Reference Status
C
PU
Re
se
t
E)
C
(D
Ye
llo
w
Re Ala
d
rm
AI Ala
S rm
BP
V
CR
C
LO Err
S or
Ne
tw
Lo ork
ca Lo
l L op
oo
p
O
nli
n
Ke e
ep
M Ali
O ve
B
Fr IS
am
XC e R
D ela
Bo R P y
ot ac
ke
W
t
at
c
Po hdo
we g
rO
n
O
nli
ne
Fr
eq
Lo
ck
G
PS
Tr
Ala ack
rm ing
Lo
op
Fr
om
Ne
M
on t
Ne
tt
Eq
o
Eq
uip
uip
Eq In
uip
O
u
t
M
on
E
To quip
Ne
to
t
Ne
t
Network Access
M
on
INTEGRATED SITE CONTROLLER
Service Access
iSC045
090696JNM
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-13
EBTS Indicators
For a description of iSC2 front panel indicators, refer to the following:
Table 2-1 Network Status Indicators on page 2-14 for the Network Status
indicators; driven by the Subrated T1 PCI (STP) card and Subrated E1 PCI
(SEP) card.
Table 2-2 System Status Indicators on page 2-15 for the System Status
indicators
Table 2-3 Reference Status Indicators on page 2-15 for the Reference Status
indicators; driven by the Site Reference ISA (SRI) card.
Table 2-1
Network Status Indicators
Indicator
Color
Yellow Alarm
yellow
Indicates the STP/SEP is receiving an alarm

signal from the far end.
Red Alarm
red
Indicates the STP/SEP is in an out-of-frame

condition.
AIS
yellow
Indicates the STP/SEP is receiving an Alarm

Indication Signal (Keep Alive).
BPV
red
Indicates the STP/SEP has received a Bipolar

Violation from the network.
CRC Error
red
Indicates the STP/SEP has received a Cyclic

Redundancy Check (CRC) error from the
network.
LOS
red
Indicates the STP/SEP is not detecting a T1/E1

carrier on the input.
Network Loop
yellow
Indicates the STP/SEP has received an in-band

or out-of-band loopback code and is in loopback
mode.
Local Loop
red
Indicates the STP/SEP is in loopback mode via

software or the front panel switch.
On-Line
green
Indicates the STP/SEP is on-line and connected

to the network.
Keep Alive
red
Indicates the STP/SEP is in a boot-up condition

and transmitting a framed all ones pattern to the
network.
MOBIS
green
Flashes each time the STP/SEP receives a

Mobis or SNMP packet.
Frame Relay
green
Flashes each time the STP/SEP receives a frame

relay packet.
XCDR Packet
green
Flashes each time the STP/SEP receives

interconnect voice packets from the transcoder.
EBTS Subsystem
2-14
Description when lit
SR 16.0
6881012Y79-B
23-Feb-09
EBTS Indicators
Table 2-2
System Status Indicators
Indicator
Color
Boot
green
Indicates the iSC is booting up and running

software stored in the motherboard ROM.
Watchdog
red
Indicates the iSC watchdog timer has expired.
Power On
green
Indicates the iSC is powered up.
Table 2-3
Reference Status Indicators
Indicator
Color
On-line
green
Indicates the SRI card is on-line and providing

5 MHz and 1 PPS to the Base Radios.
Freq Lock
green
Indicates the 5 MHz oscillator is frequency

locked to the GPS system.
GPS Tracking
green
Indicates the GPS receiver is tracking GPS

satellites.
Alarm
red
Indicates a hardware failure condition is present

on the SRI card or improper GPS antenna
connection.

The iSC3 front panel indicators provide a means for monitoring the operation
of the controller.
Figure 2-3 iSC3 Front Panel on page 2-15 shows the location of LED
indicators on the iSC3 front panel.
Figure 2-3
iSC3 Front Panel
Po
w
er
Ac
tiv
e
G
PS
SITE CONTROLLER
DCE
Lo
ca
Mon
Net
Eqp
Net
Eqp
Net Mon Eqp
Net Mon Eqp
Net Mon Eqp
Net Mon Eqp
Power
et
N
PD
V/
BP
C
R
/C
Abort/
Reset
FE
Sel/
Loop
S
AI
w
llo
Ye
S/
LO F
O
O
Service Access
iSC401
042202JNM
Refer to Table 2-4 iSC3 Front Panel Indicators on page 2-16 for a description
of iSC3 front panel indicators.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-15
EBTS Indicators
Table 2-4
Indicator
Color
Function
Top Row
Power
Green
ON: Power Supplies are operating and CPU is not in reset mode.
OFF: Power supplies are not within tolerance, or the CPU is in reset mode.
Active
Green
ON: T1 / E1 and Site Reference relays are energized.

OFF: T1 / E1 and Site Reference relays are open.
GPS
Green
ON: Satellites tracked; high stability oscillator locked to GPS; no alarms

detected.
FLASHING: Free running, or tracking satellites but not ready to key BRs.
OFF: Alarm condition detected.
Green
Reserved for future use. Span 4 selected. (Bottom row of LEDs refers to
Span 4.)
Green
Span 3.)
Green
Span 2.)
Green
Span 1 selected. (Bottom row of LEDs refers to Span 1.)
Bottom Row
LOS / OOF
Red
ON: Detected T1 / E1 Loss Of Signal or Out -Of-Frame condition.

OFF: Normal operation.
Yellow
Yellow
ON: Detected T1 / E1 yellow alarm.

AIS
Yellow
ON: Detected Alarm Indication Signal.

FE / CRC
Red
ON: Detected Framing Error or CRC error.

BPV / PD
Red
ON: Detected Bipolar Violation or Pulse Density violation.

Net
Red
ON: T1 / E1 Network loopback.

Local
Yellow
ON: T1 / E1 Local loopback.

EBTS Subsystem
2-16
SR 16.0
6881012Y79-B
23-Feb-09
EBTS Indicators
Base Radio (BR)

Indicators
The Base Radio Controller (BRC) monitors the functions of all the modules in
the Base Radio (BR). The LEDs on the front panel indicate the status of the
modules monitored by the BRC. A solid red LED indicates hard failures.
Minor failures are indicated by a flashing red LED.
Single Channel BRC
The BRC front panel indicators provide a means for monitoring the operation
of the single channel Base Radio Controller.
Figure 2-4 Single Channel BR Controller Module Front Panel on page 2-17
shows the location of LED indicators on the BRC front panel.
Figure 2-4
Single Channel BR Controller Module Front Panel
SERVICE ACCESS
B R P S E X P A C T L R 1 R 2 R 3 RESET
ENHANCED CONTROL
EBTS316g
06701SJW
Refer to Table 2-5 Single Channel BRC Indicators on page 2-17 for a
description of the single channel BRC front panel indicators.
Table 2-5
Single Channel BRC Indicators

LED
BR
PS
EX
Color
Green
Red
Red
Module
Monitored
Condition
BR
Solid (on)
Station is keyed
Flashing (on)
Station is not keyed
Off
Station is out of service or power is

removed
Solid (on)
FRU failure indication - Power Supply has

a major alarm and is out of service
Flashing (on)
Power Supply has a minor alarm and may

be operating at reduced performance
Off
Power Supply under normal operation (no

alarms)
Solid (on)
FRU failure indication - Exciter has a

major alarm and is out of service
Flashing (on)
Exciter has a minor alarm and may be

operating at reduced performance
Off
Exciter under normal operation

(no alarms)
Power
Supply
Exciter
SR 16.0
23-Feb-09
Indications
EBTS Subsystem
6881012Y79-B
2-17
EBTS Indicators
Table 2-5
Single Channel BRC Indicators (continued)

LED
Color
PA
Red
CTL
Red
Module
Monitored
Condition
Power
Amplifier
Solid (on)
FRU failure indication - PA has a major

alarm and is out of service
Flashing (on)
PA has a minor alarm and may be

Off
PA under normal operation (no alarms)
Solid (on)
FRU failure indication - BRC has a major

alarm and is out of service.
Controller
Indications
NOTE:
R1
Red
R2
Receiver #1,
#2, or #3
Flashing (on)
BRC has a minor alarm and may be

Off
BRC under normal operation (no alarms)
Solid (on)
FRU failure indication - Receiver (#1, #2,

or #3) has a major alarm and is out of
service
Flashing (on)
Receiver (#1, #2, or #3) has a minor alarm

and may be operating at reduced
performance
Off
Receiver (#1, #2, or #3) under normal

operation (no alarms)
R3
QUAD Channel Ex/BRC

The Ex/BRC front panel indicators provide a means for monitoring the
operation of the Base Radio Exciter/Controller.
Figure 2-5 QUAD Channel BR Exciter/Controller Module Front Panel on
page 2-18 shows the location of LED indicators on the Ex/BRC front panel.
Figure 2-5
QUAD Channel BR Exciter/Controller Module Front Panel
TX
TX
TX
TX
PA C N
/
RESET
STATUS
TL
QUAD CHANNEL EX/CNTL
EBTS316Q
013001JNM
Refer to Figure 2-6 Quad2 Base Radio - Components on page 2-22 for a
description of the QUAD channel Base Radio Exciter/Controller front panel
indicators
EBTS Subsystem
2-18
SR 16.0
6881012Y79-B
23-Feb-09
EBTS Indicators
Table 2-6
QUAD Channel Ex/BRC Indicators

LED
PS
EXBRC
PA
REF
Color
Red
Red
Red
Red
Module
Monitored
Power
Supply
Controller/
Exciter
Power
Amplifier
Controller
Station
Reference
Condition
Indications
Solid (on)
FRU failure indication - Power

Supply has a major alarm, and is
out of service
Flashing
(on)
Power Supply has a minor alarm,

and may be operating at reduced
performance
Off
Power Supply is operating

normally (no alarms)
Solid (on)
FRU failure indication Controller/Exciter has a major

alarm, and is out of service (Note:
Upon power-up of the BR, this
LED indicates a failed mode until
BR software achieves a known
state of operation.)
Flashing
(on)
Controller/Exciter has a minor

alarm, and may be operating at
reduced performance
Off
Controller/Exciter is operating
normally (no alarms)
Solid (on)
FRU failure indication - PA has a

major alarm, and is out of service
Flashing
(on)
PA has a minor alarm, and may

be operating at reduced
performance
Off
PA is operating normally (no

alarms)
Solid (on)
FRU failure indication - Controller

Station Reference has a major
alarm, and is out of service
Flashing
(on)
BRC has a minor alarm, and may

be operating in a marginal region
Off
BRC is operating normally (no

alarms)
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-19
EBTS Indicators
LED
RX1
Color
Red
Module
Monitored
Receiver
#1, #2, #3,
or #4
RX2
RX3
RX4
TX1
TX2
TX3
TX4
Quad2 Base Radio

Components/
Indicators
Green
Green
Green
Green
BR
BR
BR
BR
Condition
Indications
Solid (on)
FRU failure indication - Receiver

(#1, #2, #3 or #4) has a major
alarm, and is out of service
Flashing
(on)
Receiver (#1, #2, #3 or #4) has a

minor alarm, and may be
operating at reduced
performance
Off
Receiver (#1, #2, #3 or #4) is

operating normally (no alarms)
Solid (on)
Station Transmit Carrier #1 is

keyed
Flashing
(on)
Station Transmit Carrier #1 is not

keyed
Off
Station is out of service, or power

is removed
Solid (on)

keyed
Flashing
(on)

keyed
Off

is removed
Solid (on)

keyed
Flashing
(on)

keyed
Off

is removed
Solid (on)

keyed
Flashing
(on)

keyed
Off

is removed
The Quad2 BR contains four field replaceable units (FRUs):

1. Power Supply
EBTS Subsystem
2-20
SR 16.0
6881012Y79-B
23-Feb-09
EBTS Indicators
2. Power Amplifier
3. Transceiver
4. Fan Assembly
Transceiver
The Transceiver module provides the functionality of the controller, exciter,
and receiver modules in the legacy BRs.
Power Amplifier
The Power Supply provides the DC operating voltages for the Quad2 BR. It
accepts input voltage sources from 43 Vdc to 60 Vdc, positively or negatively
grounded. The Power Supply also supports an alternate AC power source
from 90 to 264 VAC, 60 Hz.
Power Supply
The Power Amplifier accepts a low-level modulated RF signal from the transceiver module, and amplifies it for transmission via the site transmit antenna
The Power Amplifier provides the same maximum power settings as the Quad
BR.
Fan Assembly
The Fan Module provides the cooling for the Transceiver and Power
Amplifier. On the left hand side of the fan is an access door that when opened,
provides access to the service port and the component LEDs.
On the lower right hand side of the fan is the Fan Alarm LED. If there is a
failure with one or both cooling fans, the LED will illuminate red.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-21
EBTS Indicators
Figure 2-6
Quad2 Base Radio - Components

Power Amplifier
Transceiver
Power Supply
Quad2 Base Radio Front Panel LEDs

and connectors
The Status and Alarm LEDs on the Power Amplifier and Transceiver LEDs
have the same function on their respective modules. They work in conjunction
with each other to identify the condition of the Power Amplifier or Transceiver.
If both LEDs are off, there is no power going to the Power Amplifier. If the
Status LED is green, and the Alarm LED is red, a Lamp Test is occurring.
If there is a failure, the Status LED is off and the Alarm LED is red. An
impaired module's Status LED is green while the Alarm LED will be blinking
red.
While the module is booting up, the Status LED is blinking green and the
Alarm LED is off. And finally, when the module is online and working
properly, the Status LED is green and the Alarm LED is off.
Power Amplifier LEDs
The XMIT LED illuminates solid Green to indicate that the Power Amplifier
is operating at full power output. An Amber LED indicates that the Power
Amplifier is operating at reduced power output.
EBTS Subsystem
2-22
SR 16.0
6881012Y79-B
23-Feb-09
EBTS Indicators
Transceiver LEDs and connectors

LEDs one through six indicate the status of each individual carrier - green
indicates the RF carrier is configured and transmitting; flashing green means
the RF carrier is configured but not transmitting; off means the carrier is not
configured.
LED number seven indicates the current Quad2 Band State - green indicates
the Quad2 BR is configured for 800 MHz band and amber is for 900 MHz.
The Reset switch resets the Transceiver control module.
The Serial Service Port connects to the service PC using an EIA-232
connection and is used for configuring the base radio.
The 10/100 Base T port is currently not used.
Figure 2-7
Power Amplifier LEDs
Figure 2-8
Transceiver LEDs and Connectors
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-23
EBTS Indicators
iDEN Monitor Unit

(iMU/EAS) Indicators
Front panel LED indicators are provided to monitor the status of the iMU/
EAS. Two LEDs, Input Active and Output Active, are used to indicate the
status of the Environmental Alarm System (EAS) input alarms and relay
outputs, respectively. Also, one LED to indicate that the iMU/EAS is powered
on.
iMU Front Panel Indicators
The iMU front panel indicators provide a means for monitoring the operation
of the iMU.
Figure 2-9 iMU Front Panel on page 2-24 shows the location of LED
indicators on the iMU front panel.
Figure 2-9
iMU Front Panel
Power
ad
Lo
Download
In
p
Ac ut
tiv
O e
ut
p
A c ut
tiv
Po e
w
O er
n
iDEN MONITOR UNIT
Status
Handset
iSC042
060796JNM
Refer to Table 2-7 iMU Indicators on page 2-24 for a description of iMU front
panel indicators.
Table 2-7
LED
iMU Indicators
Color
Download
Load
yellow
Indicates software is being loaded to the

subscriber unit.
Status
Input Active
red
Indicates an active input.
Output Active
yellow
Indicates an active output.
Power On
green
Indicates the unit is on.
EBTS Subsystem
2-24
SR 16.0
6881012Y79-B
23-Feb-09
EBTS Indicators
EAS Front Panel Indicators

The EAS front panel indicators provide a means for monitoring the operation
of the EAS.
Figure 2-10 EAS Front Panel on page 2-25 shows the location of LED
indicators on the EAS front panel.
Po
w
O er
n
In
p
A ut
ct
iv
e
POWER
O
u
A tpu
ct t
iv
e
Figure 2-10 EAS Front Panel
ENVIRONMENTAL ALARM SYSTEM
iSC402
102600JNM
Refer to Table 2-8 EAS Indicators on page 2-25 for a description of EAS front
panel indicators.
Table 2-8
EAS Indicators
Indicator
Input Active
Color
Function
red
Output Active
yellow
Power On
green
Indicates the unit is on and powered-up.
EAS2 Front Panel Indicators

The EAS2 front panel indicators provide a means for monitoring the
operation of the EAS2.
Figure 2-11 EAS2 Front Panel on page 2-25 shows the location of LED
indicators on the EAS2 front panel.
Figure 2-11 EAS2 Front Panel
O
pe
r
In ate
p
A ut
ct
i
O ve
ut
A pu
ct t
iv
e
Po
w
er
ENVIRONMENTAL ALARM SYSTEM
POWER
iSC402_2
010802JNM
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-25
EBTS Indicators
Refer to Table 2-9 EAS2 Indicators on page 2-26 for a description of EAS2
front panel indicators.
Table 2-9
Indicator
Input Active
EAS2 Indicators
Color
red
Output Active
yellow
Power On
green
Indicates the unit is on and powered-up.
Operate
green
Indicates I/O board is operational.
EBTS Subsystem
2-26
Function
SR 16.0
6881012Y79-B
23-Feb-09
The R-2660 iDEN Digital Communications System Analyzer is programmed

with an application that is designed to specifically test the unique requirements of Motorolas iDEN network equipment. For further information, refer
to the R-2660 iDEN Digital Communications System Analyzer Operators
Manual, part number 6880309F16, supplied with the R-2660.
Note The R-2660 Operators Manual, part number 6880309F16, is not
available online. A CD-ROM version, part number 6880309F17, can
be ordered from Motorola International Parts via 1-800-422-4210.
The R-2660 operates in one of four top-level modes:
Base Radio Tests
iDEN BER test base stations receiver sensitivity by generating

predefined data patterns in one of three types of interleave patterns: 1/6, 6/
6, or 4/4.
iDEN Base provides capability to monitor signals transmitted by an

operational iDEN base radio. Outbound SQE, average power level, and
frequency error can be measured when monitoring a BR in this mode.
iDEN Mobile supports testing of iDEN mobile radios. The analyzer can
be configured to simulate iDEN fixed end equipment providing the
capability to exercise registration, interconnect, and dispatch call
operations of the mobile radio under test.
Standard Mode supports all the standard test capabilities of the service
monitor. Many of the features of this mode are not unique to iDEN, and,
therefore, are not capable of displaying accurate measurements of iDEN
signals.
Possible interference problems can be isolated by viewing the transmit

spectrum on the R-2660 iDEN communication analyzer. If interference is
suspected, a directional Yagi antenna can be used to locate the source of interference.
Base Radio BER Floor and Sensitivity Verification
BER Floor test verifies the receivers ability to achieve a specified

minimum BER at a high signal level. The BER floor percent value is valid
only if the RSSI signal strength is within the limits of 81.0 dBm to -79.0
dBm. The R2660 signal output level needs to be adjusted to get the
appropriate RSSI dBm level.
BER Sensitivity test verifies the receivers performance by verifying

the receivers ability to achieve low BER with a low-level signal (-113.5
dBm) applied to the top of the rack.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-27
See Chapter 6, System Testing in the Enhanced Base Transceiver System

(EBTS) Volume 1 of 3 System Installation and Testing manual (68P80801E35)
for more information regarding the aforementioned BER tests.
EBTS Subsystem
2-28
SR 16.0
6881012Y79-B
23-Feb-09
The drive test application software is a third party Windows based software
product that runs on a PC laptop. The PC I/O interface is cabled to an iDEN
radio equipped with Test Mobile software. The drive test application
software converts collected Test Mobile data into more usable records
which are then formatted into an ASCII log file.
The drive test application software is designed to work with a GPS receiver
that is cabled to the PC I/O interface. This GPS receiver provides the
geographic location information to identify specific drive test areas and to
help analyze the data collected by the drive test application software.
When the drive test application software is running, it controls the Test
Mobile radio. This duo is capable of collecting and outputting information
about the current serving cell and its neighbors. The Test Mobile radio
provides information such as:
Site Performance
Testing using Drive
Test Application
RSSI and SQE of the serving cell and its neighbors
Frequency and Color Codes of serving cell and its neighbors
Test radios transmit levels
Control channel information
Layer 3 messages
Assignment of Control Channels and Traffic channels
Drive testing is performed to obtain a quantitative indication of the quality

level of delivered RF in a given coverage area. The coverage area of a site
is considered to be balanced when at least 90% area reliability has been
achieved at the chosen C/I+N (SQE) level, typically 22db.
Drive testing can also aid in the verification of the performance of a site or
a group of sites.
Drive testing can be used to monitor specific message types or specific

channel types.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-29
Alarm Traps to the OMC

Alarm Severity
The alarm's severity is defined as one of the severity levels listed below.
Table 2-10
Alarm Severity Levels
Alarm Severity Level
Alarm Severity Filter
Description
INDETERMINATE
Indicates that the system can not determine the

severity level.
WARNING
Indicates the detection of a potential or

impending fault before any significant effects
have been felt. Action should be taken as soon
as possible to further diagnose (if necessary)
and correct the problem in order to prevent it
from becoming a severe, service affecting fault.
MINOR
Indicates the existence of a fault which does not

have a serious effect on service, or
malfunctioning or failure of a resource noncritical to system operation. Corrective action
should be taken as soon as possible.
MAJOR
Indicates that a fault has developed resulting in

a severe degradation in the capability of the
managed object. Urgent corrective action is
necessary to recover its full capabilities.
CRITICAL
Indicates that a severe service affecting

condition has occurred resulting in the managed
object being totally out of service. Hence
immediate corrective action is necessary to
recover its full capability.
The alarm's Severity Filter is defined as one of the following:
do not filter: The Alarm Manager Task will not filter the alarm (i.e., the
reporting of the Alarm Trap to the OMC is enabled).
filter: The Alarm Manager Task will filter the alarm (i.e., the reporting of
the Alarm Trap to the OMC is disabled).
EBTS Subsystem
2-30
SR 16.0
6881012Y79-B
23-Feb-09
Alarm Traps
Message Content
The defined BRC hardware alarms are signaled using Equipment Failure
Alarm Traps as described below. These Traps are always sent to the iSC
regardless of the current state of the BRC.
All Traps contain:
Managed Object Identifier (MOI)

The MOI identifies the Field Replaceable Unit (FRU) that is associated to
the fault condition.
Valid FRUs for the single channel BR are Receiver 1, Receiver 2,
Receiver 3, Exciter, Power Supply, Power Amplifier, BR Controller
Board, and General BR. The General BR FRU is used when a fault
cannot be isolated to a specific FRU.
Valid FRUs for the QUAD channel BR are Receiver 1, Receiver 2,
Receiver 3, Power Supply, Power Amplifier, Exciter/BR Controller
Board, and General BR. The General BR FRU is used when a fault
cannot be isolated to a specific FRU.
Problem Text Field

The problem text field is not filled in for any of the traps. A code is sent
to the OMC and it is decoded there.
The OMC ignores this field in the trap and provides its own problem
text. There is no need for the BRC to send this text; thus, the BRC does
not waste code space to store an unused text string. A suggested OMC
problem text message is included to help OMC implementation.
Severity Level Message

Indicates the severity level of the fault.
These failures have direct impact on the current Operational and Usage states
of the BRC. In addition to sending a Trap to the iSC, the State Manager is
informed of all failures. It determines how the states are affected.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-31
ACG Links
ACG Links
ACG Physical Links

Table 2-11
Data Communication Signal Transport Links
Physical Link
Description
T1 Span
The number of CRC error, Rx and Tx frames, Rx and Tx aborted

frames, and long frame size will be reported to the OMC every half
hour.
Ethernet
An Ethernet failure is indicated when transmission errors increase, all

BRC LAPD Links drop, and Standby iSC disappears. These
indications trigger a series of Ethernet diagnostic tests to determine the
health of the EBTS Ethernet or the iSC's Ethernet chip-set.
ACG Reliable
Logical Links
Table 2-12
Ethernet failure alarm traps to the OMC are currently not supported.
An ACG has one reliable data link connection to a BSC, DAP and each BRC
in a site. For each data link connection, there is a server and a client. For all
data links the client initiates the connection and is responsible for re-establishing a failed connection.
Data Links
Reliable Logical Links
Description
DAP ACG
For a DAP-ACG link, the DAP is the client and establishes or reestablishes the data link connection. If the link is released, all services
involved with the DAP cease. Changes to the DAP-ACG link are
reported via DAP link state change traps, not as alarm reports and
clears.
ACG MOBIS (BSC)
For an ACG-Mobis link, the ACG is the client and establishes or reestablishes the data link connection.
BRC ACG
For a BRC-ACG link, a BRC establishes or re-establishes the data link

connection. Once the link is first established, the BRC is brought into
service only when there exists both a DAP and Mobis link.
LAPD Supporting SNMP
If this link fails, no SNMP traps can be sent to the OMC. The states of
cells and Active ACG are unaffected.
All reliable links mentioned above, except for the BRC-ACG link, will drop if
the T1 fails. These alarms are called sympathetic alarms since they occur as a
result of an overriding fault condition.
EBTS Subsystem
2-32
SR 16.0
6881012Y79-B
23-Feb-09
Communication Link Failures
Communication Link Failures

Types of Links
Physical Links
T1 Link
Ethernet
ACG Reliable Logical Links
ACG Fault Recovery
ACG-DAP Link
ACG-Mobis (BSC) Link
ACG-BRC Link
ACG-OMC (SNMP) Link
Base Radio Failure
Recovery from Disabled BRs
A BR supports a carrier needed to make a cell operate at full capacity. The

ACG acts to recover from any BR that becomes Disabled (short notation for
Unlocked, Disabled, Idle). When a BR becomes Disabled, it must go off the
air. The ACG takes steps to bring a Disabled BR back or to bring up another
BR in its place if the Disabled BR was the PCCH BR.
Note The ACG treats a failed BRC LAPD link the same as a Disabled BR.
When the link drops, the ACG takes the actions as described below.
Additionally, the ACG treats a BRC reset, indicated by receipt of BRC
I Am Here messages, in the same way. Either event means the BR
is off the air. The link drop and the I Am Here messages are both
by-products of a BRC reset. The ACG must handle both events.
BR Not Supporting PCCH Fails

Failure of this BR reduces the Cell's level of service, but it does not take the
cell out of service.
Following Failure, BR Appears

Non-Redundant BR: After a failure, a BR may come alive and send I Am
Here messages; the BR may have reset on its own or as part of a
technician's repair effort. This BR is required to make the cell fully
functional.
The ACG loads it with code and the configuration of the missing carrier.
Then the ACG unlocks the BR to bring it into service and bring the cell to
a better functional state.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-33
Recovery from PCCH Base Radio Failures
Recovery from PCCH Base Radio Failures

BR Supporting
PCCH Fails
Failure of this BR is the most serious since it takes the cell out-of-service.
Handling of this fault differs based on whether there is a redundant BR
available in the cell.
Any BR can carry any frequency. The ACG can rearrange frequencies as
needed to address faults. When the PCCH BR fails, the ACG uses another BR
in the cell to replace it. Two cases are possible:
Redundant BR available: A redundant BR is tied to a particular cell; if three

cells at a site require redundancy, then three redundant BRs are required.
Only one Redundant BR is allowed per cell. The redundant BR is the first
choice carrier to be used to backup the PCCH BR.
Redundant BR Not Available: When no Redundant BR is available, the

ACG selects one of the active BRs to become the new PCCH Carrier and
locks that BR. Next, the ACG reconfigures the BR by modifying, via a
series of SNMP set messages, those parameters include frequency and color
code. After the BR has been reconfigured, it is unlocked and brought back
into service. The steps involved in reconfiguring this BR are similar to
those for a redundant BR.
ACG call processing has no indication of the physical BR change. To Call

Processing, the recovered failure looks like the PCCH carrier went down and
came back. The same BRC ID is used for this carrier regardless of the
physical BR supporting it. NM keeps call processing hidden from these
details by providing a BRC ID to Host Name translation for the Control
Router and Voice Router. Only these routers need be concerned with how to
get messages to the correct BR. Updates to this translation table are made
while the BRs are locked.
EBTS Subsystem
2-34
SR 16.0
6881012Y79-B
23-Feb-09
Recovery from ACG Failures
Recovery from ACG Failures

ACG Failure
Recovery
Active ACG (Side A) Disappears

To recover from an ACG failure, a switch from the Active to the Standby
side may be required. There are many inputs into the decision to make the
switch. These inputs are discussed below.
A common, initial scenario is used to make the following discussions easier
to follow. The Active ACG from which the site is switching is Side A; it
will become the newly Standby ACG. The Standby ACG, which will
become Active, is Side B.
The Standby ACG can determine the Active ACG disappears when the
heartbeat messages stop. For redundancy, both conditions are treated the
same.
Side B Point Of View

The ACG Redundancy Communications system has indicated that Side A
is no longer responding. After Side B verifies that the Ethernet is
terminated, Side B takes over the T1 by initializing the NIC, thereby
becoming Active.
Then, it waits for BRCs to appear. After the BRC has found this ACG (see
HOG messages), it is required to send its state information. The ACG uses
the state information to indicate the BRC is alive and to prevent using failed
BRCs.
Following switch, Side A Appears

After Side B has become active, Side A may come back alive (for instance,
after a technician has replaced failed cards). When Side A returns, Side B
reloads it with the current code and configuration objects. Side A is
reloaded at a slow enough rate to prevent interference with calls in progress.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-35
Base Radio Controller States
Base Radio Controller States

General State
Definitions
Table 2-13
The BRC states are valid combinations of the following administrative, operational and usage states of the BRC:
BRC Device State Management Details
State
Administrative
Description
Locked: The Base Radio is not allowed to operate (it may be functional or
not)
Unlocked: The Base Radio is allowed to operate (it may be functional or not)
Operational
Disabled: Base Radio is not functional

Enabled: Base Radio is functional
Usage
Active: Base Radio is operating

Idle: Base Radio is not operating
Transitions Caused by
Fault Conditions
For many critical failures, the BRC will dekey.

The BRC state becomes Disabled, and this BRC is taken out of service.
Certain failures may cause the BRC to go through a self-lock procedure in

order to recover.
The ACG may bring the BRC back-into service after the BRC reports that its
state is Locked, Enabled, Idle.
If a critical failure has forced the BRC state to Disabled, the ACG can not
bring this BRC back into service until the BRC again reports that its state is
Locked, Enabled, Idle.
Administrative State
Changes
The ACG may lock BRCs in response to certain failures.

When the failure clears the affected BRCs are unlocked.
For example, complete DAP Communications or Mobis link failures will
cause the ACG to lock all BRCs at a site until the failure clears (see Definition
of ACG States).
Specific BRC failures within a cell may trigger the ACG to lock the BRCs in
that cell in order to perform Cell Recovery (see Definition of Cell States).
EBTS Subsystem
2-36
SR 16.0
6881012Y79-B
23-Feb-09
Base Radio Controller (BRC) States
Table 2-14 BRC States on page 2-37 shows all valid BRC states. All other
potential combinations of Administrative, Operational and usage states are
not valid (for example, unlock-disabled-active is not valid).
Table 2-14
BRC States
State
Description
State 1
Initial, Initial, Initial This state indicates that the BRC has just reset.
State 2
Locked, Disabled, Idle This state indicates the BRC has been
downloaded with code and generic configuration data and the BRC has
enabled local BRC MMI.
- OR Alternatively, this state indicates that the BRC is not functional (has failed)
and has been taken out of service.
State 3
Locked, Enabled, Idle This state indicates that:
the BRC has been loaded with carrier-specific configuration via SNMP
Set commands
the ACG-BRC LAPD link has been established
the BRC has established GPS time and date synchronization
the BRC has detected no initialization faults, but the BRC has not been
brought into service by the ACG via an Unlock command.
- OR -
Alternatively, this state could indicate that the BRC had been in service but
has been taken out of service by the ACG via a Lock command. Note that
some failure modes can only be detected during run-mode; these may exist
but cannot be detected until the BRC is Unlocked.
State 4
Unlocked, Enabled, Idle This state indicates that the BRC has been
Unlocked by the ACG and is beginning to key-up. During this state the BRC
will attempt to transmit.
State 5
Unlocked, Enabled, Active This state indicates that the BRC has
keyed-up, is fully functional, and able to process calls.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-37
State Management
within the ACG
The ACG maintains state information for all of the BRs, the condition of each
cell, the DAP links, and MDG links. A failure in any of the monitored
elements, causes events and alarms to be reported to the OMC. Depending on
the type of failure, the color of the site icon might change from green to
yellow, red, or blue. EBTS site status is interpreted as follows:
Green Operational Condition; all devices/connections operational for

this site
Yellow Impaired Condition; the link, to one or more of the site's

subdevices (e.g., Cell, DL, BR, etc.) has failed, but the site is still partially
connected. As long as at least one cell at a site is operational, the site will
remain in `yellow status and not go to red status.
Red without an X Failed Temporary Condition; a soft reset has occurred

for the site. A soft reset is initiated by any of:
a download to the site

a manual reset via NE Management
a background download operation
a redundancy switch operation.
Red with an X Failed Condition; all sub-devices (Cells, BRs, etc.) for the
site have failed, and the site is considered non-connected to the OMC.
Blue Indeterminate Condition; the X.25 link from the OMC to the site is
down, preventing all communications between the OMC and the site. This
status does not necessarily indicate that the site is down.
Circle around icon Site is in Isolated Site Operation Mode; the site has
lost all links to the DAP(s) and is considered to be in Isolated Site Operation
(ISO).
Note
The ISO mode is an optional iDEN feature.
Status information is reported on various objects within the EBTS.

The BRC reports status information on the BRC object.
The Cell State represents the status of an individual cell within the
EBTS site.
The DAP Link (DL) State represents the status of an individual ACGDAP link.
The DAP Communications Composite (DCC) State represents the
composite status of multiple ACG-DAP links at the site.
The ACG reports status information on the Cell objects, DAP Link
objects, DAP Communication Composite object, and the ACG object.
The ACG State represents the status of the entire EBTS site.
EBTS Subsystem
2-38
SR 16.0
6881012Y79-B
23-Feb-09
The states of its Cells (sectors), the DCC state, and the state of the Mobis link
affect the state of the ACG.
In a sectored site, if one sector is Disabled or Impaired while the other

sectors are Active, the ACG is Impaired.
If all sectors are Disabled, then the ACG is Disabled.
Only if all sectors are Active and the DCC state is Active will the ACG state
be Active.
ACG state transitions are trapped and sent to the OMC. These are referred
to as ACG State Change Traps.
Note
Because the Cell and DCC states directly affect the ACG be configured
with the correct number of Cells and DAPs as are expected to report.
If less DAPs report than are entered in the site configuration, the ACG state
(which is the composite state of the EBTS) will not transition beyond
Impaired.
If less BRs report than are entered in the site configuration, the
corresponding Cell will be Disabled/Impaired and therefore the ACG will
only be Impaired at best.
The following information is contained in the ACG State Change Traps sent
to the OMC:
States of each:
BRC
Cell
DL Individual DAP links
DCC DAP Communication Composite
MCC MDG Communication Composite link
ACG
Faults at each:
Base Radio
ACG
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-39
Troubleshooting RF-related Problems
Troubleshooting RF-related Problems
There are many different symptoms that can be attributed to RF related

problems. For example:
Insufficient coverage
Co-channel interference
Adjacent channel interference
Excessive site noise
Subscriber unit interference
Broadband Interference
BR imbalance uplink / downlink imbalance; imbalanced link budget
Note
Refer to iDEN Radio Frequency Interference manual (68P80801B75).
Symptoms include:
Low SQE (<20 dB) with low RSSI (<-90 dBm) on uplink and/or downlink
on one or more frequencies (Insufficient coverage)
Low SQE (<20 dB) with medium to high RSSI (>-90 dBm); co-channel or
adjacent channel interference
Sporadic outages
Dropped calls
High rate of connection failures (Please try again or System Busy)
High rate of handover failures and handover dropped calls
Garble audio
Resolutions:
Increase and / or decrease antenna gain
Increase and / or decrease outbound transmit power
Add new site to fill coverage holes
Add new BRs to increase capacity
Downtilt antennas of co-channel cells
Lower antenna height
Increase / Decrease PCC and Desired_Pri parameters in the EBTS datafill
Retune frequency(ies) of interfering and/or victim site(s)
EBTS Subsystem
2-40
SR 16.0
6881012Y79-B
23-Feb-09
EBTS Equipment-related Problems
Unscheduled hardware outage relates to any failure of the BR Field

Replaceable Units (FRUs) and ACG FRUs (e.g. exciter, power supply, SRI
card, etc.).
The hardware alarms are very straightforward, and it will usually be very
obvious to the person troubleshooting this type of failure.
Some failures that cause the degradation of signal without generating

alarms are more difficult to troubleshoot.
It is recommended that the technician use a logical troubleshooting procedure

to isolate a problem to the faulty component(s).
Symptom Recognition
Identify the symptoms using available resources: OMC alarms, events, and
statistics; Customer trouble tickets; Subscriber Unit error messages; etc.
Symptom Elaboration
Use available test equipment and troubleshooting resources to gather
further information on the failure.
Drive test the site if suspecting RF related problems.
Review the OMC statistics for high levels of blocking, dropped calls,
etc.
Check the front panel indicators at the EBTS site for abnormal
conditions (check for red or yellow alarms and verify that the green Led
are in proper operating condition).
Use the troubleshooting charts and test procedures in the EBTS and iSC
manuals to isolate the problem.
Fault Isolation
Use the service computer, test equipment, troubleshooting charts, and
system test procedures in the EBTS and iSC manuals to isolate the problem.
Connect the laptop computer to the front panel of the suspected Base
Radio(s), login, and type get alarms. Verify that no alarm conditions
are detected. Also type set alarm_reports on verify that all test
components are operating normally.
Connect the laptop to the front panel of the iSC controller and monitor
alarm reports and status messages reported by the iSC.
If the problem is still not found, use electronic test equipment to further
isolate the problem (T1 tester to verify T1 is error-free, R-2660 to test
transmit and receive operation, and external analog wattmeter to test
transmit power out of the duplexer).
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
2-41
NOTES...
EBTS Subsystem
2-42
SR 16.0
6881012Y79-B
23-Feb-09
Chapter 3
In This Chapter
See Page
Topic
Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Supplemental Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Resolving Hardware Issues . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
High Stability Oscillator (HSO) Failure . . . . . . . . . . . . . . 3-5
GPS Problem - 0 Tracked Satellites . . . . . . . . . . . . . . . 3-10
Multiple Momentary FREE RUN Events . . . . . . . . . . . . 3-19
Audio Problems Related to the Antenna . . . . . . . . . . . 3-22
Duplex Wattmeter VSWR Alarm Problem . . . . . . . . . . . 3-24
EBTS 5MHZ/iPPS Signal Integrity Test for EBRC
and Quad BR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Incorrectly Programmed ExBRCs FSB . . . . . . . . . . . . . 3-35
Resolving Visibility Issues to the OMC-R . . . . . . . . . . . . . . 3-37
Resolving Connectivity Issues to other Network Elements 3-38
Resolving Download Issues . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Issue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Resolving Configuration Issues . . . . . . . . . . . . . . . . . . . . . . 3-43
Newly Installed BRs Do Not Come In Service Ethernet Loop Carrier Limit Exceeded . . . . . . . . . . . . . 3-43
Newly Installed BRs Not Keying Up After Site
Download - 5MHz/1PPS Loop Overload . . . . . . . . . . . . 3-46
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-1
Resolving Provisioning Issues. . . . . . . . . . . . . . . . . . . . . . . 3-49

Resolving Loss or Disruption of Service Issues . . . . . . . . 3-50
Resolving Database Issues. . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
Resolving Billing Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52
Resolving Statistics Issues. . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
EBTS Subsystem
3-2
SR 16.0
6881012Y79-B
23-Feb-09
Purpose
Purpose
This chapter describes troubleshooting scenarios for the Enhanced Base

Transceiver System (EBTS) RF subsytem. Descriptions of the symptoms you
may be experiencing, how to isolate the problem, the recommended action(s)
you should take, and verification procedures to ensure that the action(s) you
took was successful are provided.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-3
Supplemental Information
Supplemental Information
Most of the troubleshooting scenarios in this chapter use or reference OMC

alarm and state change event messages for the EBTS, ACG and BR. For
additional information regarding these OMC messages, refer to the Alarm &
State Change Events (ASCE) documentation.
The ASCE documentation is updated with each System Release (SR). This
documentation is located on the iDEN extranet Web site at the following
URL:
http://mynetworksupport.motorola.com
EBTS Subsystem
3-4
SR 16.0
6881012Y79-B
23-Feb-09
High Stability Oscillator (HSO) Failure
Scenario
Alarm [319] HSO Failed - Critical - causes the system to place the failing
Access Controller Gateway (ACG) Out-Of-Service (OOS). If the EBTS is
equipped with redundant ACGs and the failing ACG was Active, then
automatic switch over to the Standby ACG would occur. If the EBTS is not
equipped with redundant ACGs (i.e., non-redundant ACG), then a site outage
would occur.
Note This scenario is for an ACG using the iSC2 platform. The iSC3
platform would have a similar scenario.
Symptoms
OMC console Site Status Display (SSD) for the affected site shows that the
failing ACG is OOS.
For redundant ACGs with a failing Active ACG, redundancy switch over
would have occurred and the SSD would also show the following:
Switch Recommendation is NO.
Active Side B.
For a non-redundant ACG, the SSD would also show the following:
Cell_#s are OOS.
BR_#s are OOS.
OMC console Event Display shows that the Standby ACG experienced an
equipment Failure Event due to alarm [319] HSO Failed - Critical and was
subsequently disabled.
For an example of HSO failure event messages, refer to Figure 3-1 HSO
Failure Event messages for Standby ACG using the iSC2 (iSC3 would be
similar) on page 3-5.
Figure 3-1
HSO Failure Event messages for Standby ACG using the iSC2 (iSC3 would be similar)
#0 - NOT APPL - *NONE*.

equipmentFailureEvent - TFR/SRI - NIL3697R_IIWheaton, Cab 2, Pos 2, standby
ACG, TFR/SRI 0 - Aug 12, 2004 13:17:28.
[319] HSO Failed - Critical.
150725536,-317279611,19546
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-5
esmrStateChangeEvent - ACG - NIL3697R_IIWheaton, ACG 1, standby ACG - Aug 12,
2004 13:37:02.
From: (Unlocked, Disabled, Idle)
To : ( Unlocked, Disabled, Idle) - [807] STANDBY ACG COMMUNICATION DOWN.

esmrStateChangeEvent - SRI/TFR - NIL3697R_IIWheaton, SRI/TFR 1, standby ACG Aug 12, 2004 13:37:03.
From : ( Unlocked, Disabled, Idle)
To : ( Unlocked, Enabled, Idle) - [955] STANDBY GPS SENT TO IDLE.

equipmentFailureEvent - TFR/SRI - NIL3697R_IIWheaton, Cab 2, Pos 2, standby
ACG, TFR/SRI 0 - Aug 12, 2004 13:44:40.
[308] GPSR 1PPS Missing - Clear.

esmrStateChangeEvent - SRI/TFR - NIL3697R_IIWheaton, SRI/TFR 1, standby ACG Aug 12, 2004 13:47:30.
From : ( Unlocked, Enabled, Idle)
To : ( Unlocked, Disabled, Idle) - [951] STANDBY GPS CRITICAL FAULT.

esmrStateChangeEvent - ACG - NIL3697R_IIWheaton, ACG 1, standby ACG - Aug 12,
2004 13:47:30.
From : ( Unlocked, Enabled, Idle)
To : ( Unlocked, Disabled, Idle) - [801] STANDBY GPS DISABLED.
EBTS Subsystem
3-6
SR 16.0
6881012Y79-B
23-Feb-09
Service Impact
Service impact for redundant ACGs is as follows:

With a failing Active ACG, call processing and EBTS operation is
temporarily interrupted until redundancy switch over completes.
With a failing Standby ACG, call processing and EBTS operation is not
affected.
ACG redundancy is no longer available.
For a non-redundant ACG, call processing and EBTS operation is interrupted
until the ACG failure is resolved.
Problem Isolation
From the OMC console, the OMC-R operator tries to recover the failed ACG
by performing a Reset on the OOS ACG. After several minutes, the reset
completes, but the ACG remains OOS.
The recent OMC console Event Display shows that the failed ACG experienced an immediate equipment Failure Event due to alarm [319] HSO Failed Critical and was subsequently disabled.
The problem is at the site. Because alarm [319] occurs immediately, there is a
malfunction of the GPSR (GPS Receiver) and/or HSO within the failed iSC.
Note For iSC2, the GPSR and HSO are part of the field replaceable SRI
(Site Reference ISA) card plugged into the main board of the iSC2.
Note For iSC3, the GPSR and HSO are integral parts of the iSC3 assembly.
A malfunctioning GPSR or HSO in the iSC3 requires replacement of
the entire iSC3 assembly.
Recommended
Action
Send technician to the site to fix the problem. The following actions are
performed by the technician at the site.
TO
Resolve the iSC HSO Failure Issue at the

EBTS Site
Step
Action
Cycle the failed iSC operating power Off-On. This action will reset
the failed iSC.
Observe the LED indicators on the front panel of the failed iSC.
After iSC reset completes, verify the following LED indications.

For iSC2, Ref. Status
ALARM LED - On (red); hardware failure on SRI card.
For iSC3,
GPS LED - Off; internal GPSR/HSO alarm condition and
failure.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-7
TO
Resolve the iSC HSO Failure Issue at the

EBTS Site (continued)
Step
4
Action
Replace the appropriate Field Replaceable Unit (FRU); SRI card or
iSC3 assembly.
For the failing iSC2, replace the SRI card. Refer iSC SRI Card
Removal/Installation section in the FRU Replacement Procedures
chapter of the iDEN Integrated Site Controller System Manual
(68P81098E05).
For the failing iSC3, replace the iSC3 assembly. Refer to the Site
Controller Replacement section in the FRU Replacement
Procedures chapter of the iDEN Gen 3 Site Controller System
Manual (68P80801E30).
Verify the following LED indications.

For iSC2,
ALARM LED - Off; no hardware failure on SRI card.
GPS TRACKING - Off; GPSR trying to track/acquire
satellites. Turns on solid green after successful satellite
tracking/acquisition.
FREQ LOCK - Off; HSO free run while GPSR trying to track
and acquire satellites. Turns on solid green after HSO is
locked to GPS.
Note It may take up to two hours for the GPSR to successfully
track and acquire satellites. Also before the HSO can free run or
lock to GPS, the HSO requires approximately 20 minutes for
frequency stabilization after a cold startup.
For iSC3,
GPS LED - Flashing green; HSO free run and GPSR trying
to track/acquire satellites. Turns on solid green after
successful satellite tracking/acquisition and HSO is locked to
GPS.
Note It may take up to two hours for the GPSR to successfully
track and acquire satellites. Also before the HSO can free run or
lock to GPS, the HSO requires approximately 20 minutes for
frequency stabilization after a cold startup.
Contact the OMC-R operator and have them verify that there are no
new alarms.
EBTS Subsystem
3-8
SR 16.0
6881012Y79-B
23-Feb-09
Verification
The OMC-R operator uses the OMC console SSD to monitor the affected site
to verify that the previously failed ACG status is now Operational.
Note The affected ACG will not be Operational until the GPSR
successfully tracks and acquires satellites. This may take up to two
hours. Also before the HSO can free run or lock to GPS, the HSO
requires approximately 20 minutes for frequency stabilization after a
cold startup.
If the site is equipped with a non-redundant ACG, then verify that the Active
ACG is Operational
If the site is equipped with redundant ACGs, then:
Verify that both the Active and Standby ACGs are Operational.
Verify that the Switch Recommendation is YES.
Verify redundancy switching by clicking the Redundancy Switch button
and observe that the Active Side changes.
Leave AGC redundancy with Active Side A.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-9
GPS Problem - 0 Tracked Satellites

Scenario
The Access Controller Gateway (ACG) stops tracking GPS satellites.

Alarm [306] GPS Problem - 0 Tracked Satellites - Major - causes the system
to place the affected ACG in the impaired state. The High Stability Oscillator
(HSO) of the affected ACG starts to free run because the HSO frequency is no
longer locked to GPS timing. In addition, the system starts a 4-hour Free-Run
timer if the affected ACG is currently Active.
The affected ACG will continue to try and track satellites.
If tracking resumes, then alarm [306] will clear and the affected ACG will
recover and its HSO will lock to GPS timing in a short time. The affected
ACG and EBTS site status changes from impaired to operational.
If tracking does not resume within approximately 4 hours for an affected

ACG that is currently Active, then the 4-hour Free-Run timer times out and
alarm [313] will be generated. When this timer times out, redundant ACG
switch over occurs.
Note
Note
Note
Occasional detection/reporting of [306] GPS Problem - 0 Tracked

Satellites and associated events soon followed by a clearing of the
alarm and ACG recovery is part of normal ACG operation. Frequent
occurrences of short term [306] alarm/clear should be investigated and
resolved while infrequent occurrences of short term [306] alarm/clear
are normal and can be ignored. Refer to the performance statistics for
the affected EBTS site to determine occurrence frequency of short
term [306] alarm/clear.
This scenario is described for an ACG using the iSC2 platform. The
iSC3 platform would have a similar scenario.
If no redundant ACG is present at the site all the BRs will dekey and
there will be a loss of call processing after the 4 hour timer expires.
EBTS Subsystem
3-10
SR 16.0
6881012Y79-B
23-Feb-09
Symptoms
OMC console Site Status Display (SSD) for the affected site shows that the
affected ACG is Impaired.
For redundant ACGs with the Active ACG tracking 0 satellites, the SSD
shows the following status:
EBTS Status: Impaired
Switch Recommendation: Maybe
Active ACG Status: Impaired
Active SRI/TFR Status: Impaired
For redundant ACGs with the Standby ACG tracking 0 satellites, the SSD
shows the following status:
EBTS Status: Impaired
Standby ACG Status: Impaired
Standby SRI/TFR Status: Impaired
OMC console Event Display shows that the affected ACG experienced an
equipment Failure Event due to alarm [306] GPS Problem - 0 Tracked Satellites - Major and was subsequently marked as impaired.
Refer to Figure 3-2 Event messages for Active ACG Tracking 0 Satellites &
Free Running for More Than 4 Hours (shown for iSC2; iSC3 similar) on
page 3-12 for an example of event messages for an affected Active ACG that
has been tracking 0 satellites and free running for more than 4 hours. An
affected Standby ACG would have similar event messages except there would
be no [313] ACG Free Run Timeout - Critical message after 4-hours of free
run.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-11
Figure 3-2
Event messages for Active ACG Tracking 0 Satellites & Free Running for More
Than 4 Hours (shown for iSC2; iSC3 similar)

esmrStateChangeEvent - ACTIVE SRI/TFR - CNRC_EBTS_42, ACTIVE SRI/TFR 1, active
A CG - May 4, 2006 10:51:42.
From : ( Unlocked, Enabled, Active)
To : ( Unlocked, Enabled, Impaired) - [902] ACTIVE GPS FREERUN STARTED.

esmrStateChangeEvent - ACG - CNRC_EBTS_42, ACG 1, active ACG - May 4, 2006
10:51:42.
To : ( Unlocked, Enabled, Impaired) - [223] ACTIVE GPS IMPAIRED.

esmrStateChangeEvent - EBTS - CNRC_EBTS_42, EBTS 1, active ACG - May 4, 2006
10:51:42.
To : ( Unlocked, Enabled, Impaired) - [701] ACTIVE ACG IMPAIRED.
- NOT APPL - *NONE*.

equipmentFailureEvent - TFR/SRI - CNRC_EBTS_42, Cab 2, Pos 2, active ACG, TFR/
SRI 0 - May 4, 2006 10:51:42.
[306] GPS Problem - 0 Tracked Satellites - Major.
- NOT APPL - *NONE*.

equipmentFailureEvent - TFR/SRI - CNRC_EBTS_42, Cab 2, Pos 2, active ACG, TFR/
SRI 0 - May 4, 2006 14:51:51.
[313] ACG Free Run Timeout - Critical.
EBTS Subsystem
3-12
SR 16.0
6881012Y79-B
23-Feb-09
Service Impact
Increased dropped calls and handover failures due to site not being synchronized with neighboring sites.
When in free run (0 satellites tracked), the Active ACG processes calls
normally, but Base Radios (BRs) cannot sync back up during the brief free run
period if they are reset.
Free run (0 satellites tracked) on the Standby ACG has no impact on call
service at all.
Note If no redundant ACG is present at the site all the BRs will dekey and
there will be a loss of call processing after the 4 hour timer expires.
Problem Isolation
A [306] GPS Problem - 0 Tracked Satellites alarm indicates an equipment

problem at the EBTS site. There may be a malfunction of either the GPS
antenna system or the GPSR (GPS Receiver) within the affected iSC.
Note For iSC2, the GPSR is part of the field replaceable SRI (Site Reference
ISA) card plugged into the main board of the iSC2. There are other
circuits on the iSC2 main board that support GPSR functions. Input/
output interfaces between the GPSR support circuits and the SRI card
are routed via the main board. If the problem is isolated to the iSC2,
first the SRI card would be replaced. If that does not correct the
problem, then the entire iSC2 assembly with SRI card would be
replaced.
Note For iSC3, the GPSR and support circuits/functions are an integral part
of the iSC3 assembly. If the problem is isolated to the iSC3, the entire
iSC3 assembly would be replaced.
Recommended
Actions
If the affected ACG has been in free run (0 satellites tracked) for over 30
minutes, send a technician to the EBTS site to fix the problem. The following
actions are performed by the technician at the EBTS site.
TO
Resolve the [306] GPS Problem - 0 Tracked Satellites Issue

at the EBTS Site
Step
1
Action
Observe the LED indicators on the front panel of the affected iSC.
For iSC2,
GPS TRACKING - Off; GPSR not tracking satellites.
FREQ LOCK - Off; HSO is not locked to GPS timing.
For iSC3,
GPS LED - Off; GPSR not tracking satellites and HSO is not
locked to GPS timing.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-13
TO
Resolve the [306] GPS Problem - 0 Tracked Satellites Issue

at the EBTS Site (continued)
Step
2
Action
Observe the LED indicator on the front panel of the redundant mate
iSC.
For iSC2,
GPS TRACKING - On; GPSR is tracking satellites.
FREQ LOCK - On; HSO is locked to GPS timing.
For iSC3,
GPS LED - On; GPSR is tracking satellites and HSO is
locked to GPS timing.
Connect a service computer (i.e., PC) to the RS232 serial port

Service Access connector on the front panel of the affected iSC.
Observe the service computer display and verify that the iSC is not
tracking satellites.
Go to the rear of the iSCs and switch GPS antenna cables A & B
between the two redundant iSCs.
Go to the front of the iSCs.

a) Check front panel LEDs and service computer display to see if
the affected iSC is now tracking satellites.
Note It may take a few minutes for tracking to start.
b) Check front panel LEDs on the redundant mate iSC to see if it is

still tracking satellites.
If the affected iSC is now tracking satellites and the redundant mate
iSC is not tracking satellites, then the GPS antenna signal
connected to the iSC that is currently not tracking satellites is bad.
Perform the steps in the following table:TO Troubleshoot a
Suspected Bad GPS Antenna Signal on page 3-15.
If the affected iSC is still not tracking satellites and the redundant
mate iSC is tracking satellites, then the both GPS antenna signals
are good. The affected iSC is suspect.
Perform the steps in the following table:TO Troubleshoot a
Suspected Bad iSC for a GPS Satellite Tracking Problem on

page 3-17.
EBTS Subsystem
3-14
SR 16.0
6881012Y79-B
23-Feb-09
Previous actions of switching GPS antenna signals between redundant iSCs

indicate that the GPS antenna signal to the iSC is either too weak or there is
no signal. Perform the following actions to troubleshoot the GPS antenna
signal.
TO
Troubleshoot a Suspected Bad GPS Antenna Signal
Step
Action
Use a portable hand-held GPS receiver (GPSR), Garmin model

GPS V or equivalent, for GPS antenna signal tracing.
Note An assortment of coaxial connector adapters will be need
to allow direct connection of antenna path components to the
portable GPSR.
Disconnect the suspect GPS antenna signal cable from the rear of
the iSC and connect this cable to the antenna connector on the
portable GPSR.
Observe the portable GPSR display. Confirm that this GPS

antenna signal is weak/missing as indicated by the earlier GPS
antenna signal switch.
Signal trace the GPS antenna path from the iSC toward the GPS
antenna. Determine the point in the antenna path where the GPS
antenna signal is strong/present and then changes to weak/
missing.
Troubleshoot the portion of the antenna path with weak/missing

GPS signal.
For GPS antenna path information, refer to the following applicable
iSC manual:
For the iSC2, the iDEN Integrated Site Controller System
Manual (68P81098E05).
For iSC3, the FRU Replacement Procedures chapter of the
iDEN Gen 3 Site Controller System Manual (68P80801E30).
a) Check the condition of the following applicable GPS antenna
path components:
Coaxial cables and connections
In-line RF amplifier
RF signal splitter
Surge/Lightning arrestor
b) Repair/replace the faulty GPS antenna path components as
necessary.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-15
TO
Troubleshoot a Suspected Bad GPS Antenna Signal
Step
6
Action
If signal tracing indicates that the GPS antenna is bad, then
troubleshoot the GPS antenna. Correct the antenna problem as
necessary.
For GPS antenna information, refer to the following applicable iSC
manual:
For the iSC2, the iDEN Integrated Site Controller System
Manual (68P81098E05).
For iSC3, the FRU Replacement Procedures chapter of the
iDEN Gen 3 Site Controller System Manual (68P80801E30).
Use the portable GPSR to confirm that the GPS antenna signal
path/antenna fix is successful. The minimum requires 4 satellites
for accurate position and elevation information.
Reconnect all cable connections that were disconnected during

signal tracing.
Use the portable GPSR to confirm that the iSC GPS antenna cable
has a good GPS antenna signal.
10
Reconnect the GPS antenna signal cable to the rear of the iSC.
11
Verify that the iSC is now tracking satellites.

Further verify that both iSCs are tracking satellites.
12
The GPS antenna problem is fixed.

Go to the rear of the iSCs and switch the GPS antenna cables back
to the original connections so that:
upper iSC is connected to GPS antenna cable A
lower iSC is connected to GPS antenna cable B.
EBTS Subsystem
3-16
SR 16.0
6881012Y79-B
23-Feb-09
Previous actions of switching GPS antenna signals between redundant iSCs

indicate that the suspect iSC has a known good GPS antenna signal input, but
it is not tracking satellites.
Perform the following actions to troubleshoot the suspect iSC.
Important
The following procedure will cause all calls to be dropped. This should
be performed during the maintenance window.
.
TO
Troubleshoot a Suspected Bad iSC for a GPS Satellite

Tracking Problem
Step
Action
On the front of the suspect iSC, set the POWER switch to Off. This
action causes the redundant iSC to switch over to Active if it is not
already Active.
After the redundant iSC is Active, set the POWER switch on the
front of the suspect iSC to On. This action causes the suspect iSC
to hard-reset. The hard-reset completes in about two minutes and
then the suspect iSC becomes Standby.
After the suspect iSC completes the hard reset, check to see if it is
now tracking GPS satellites.
Note It may take up to 30 minutes for the GPSR to successfully
track and acquire satellites.
If the suspect iSC is tracking GPS satellites, then the problem is
fixed. Go to step 7.
If the suspect iSC is an iSC2 and it is not tracking GPS satellites,
then go to step 4.
If the suspect iSC is an iSC3 and it is not tracking GPS satellites,
then go to step 6.
For an iSC2, replace the SRI card.

Refer to the iDEN Integrated Site Controller System Manual
(68P81098E05) for SRI card replacement information.
If the suspect iSC is still not tracking GPS satellites, then go to step
5.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-17
TO
Troubleshoot a Suspected Bad iSC for a GPS Satellite

Tracking Problem (continued)
Step
5
Action
Replace the iSC2 assembly.
Refer the iDEN Integrated Site Controller System Manual
(68P81098E05) for iSC2 assembly replacement information.
For an iSC3, replace the iSC3 assembly.

Refer to the iDEN Gen 3 Site Controller System Manual
(68P80801E30) for iSC3 assembly replacement information.
Verification
Go to the rear of the iSCs and switch the GPS antenna cables back
to the original connections so that:
upper iSC is connected to GPS antenna cable A
lower iSC is connected to GPS antenna cable B.
The OMC-R operator uses the OMC console SSD to monitor the affected site
to verify the following:
Status for the EBTS, affected ACG and affected SRI/TFR is now
Operational instead of Impaired
Event Display shows alarm [306] GPS Problem - 0 Tracked Satellites Clear for the affected ACG.
Note The Operational status and alarm [306] clear do not appear until the
affected ACG GPSR successfully tracks and acquires satellites. This
may take up to 30 minutes if the SRI or iSC assembly was replaced.
EBTS Subsystem
3-18
SR 16.0
6881012Y79-B
23-Feb-09
Multiple Momentary FREE RUN Events

Scenario
Typically when the EBTS Access Controller Gateway (ACG) is powered-up

for the very first time, it can take up to 30 minutes for the ACG GPS Receiver
(GPSR) to acquire and track the appropriate quantity of GPS satellites and
then to synchronize/lock the ACG High Stability Oscillator (HSO) to GPS
timing. For all subsequent resets of the ACG, GPSR satellite acquisition/
tracking and HSO synchronization/locking typically takes significantly less
than 30 minutes.
Occasionally after an ACG power-up or reset, the ACG GPSR may acquire
and track the appropriate quantity of GPS satellites long enough to achieve
HSO synchronization/lock and then lose satellites and go out-of-lock and free
run. Then in a very short period of time, the ACG GPSR again acquires and
tracks the appropriate quantity of satellites and achieves lock ending free run.
This momentary locking and unlocking/free run behavior is repeated over and
over, but eventually stabilizes to longer/normal lock durations within 24 hours
after the reset.
Symptoms
The OMC-R receives frequent momentary FREERUN event messages from

the ACG that is experiencing momentary locking and unlocking/free run
behavior after the ACG reset.
The momentary event message sequence is as follows:
FREERUN STARTED event message is reported and then immediately

followed by a FREERUN ENDED event message.
This sequence is likely to be repeated in rapid succession (two sequences

within three seconds).
For an example of the momentary event message sequence, refer to
Figure 3-3 Event messages for Active ACG Experiencing Multiple
Momentary FREERUN Started & Ended (shown for iSC2; iSC3 similar) on
page 3-20.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-19
Figure 3-3
Event messages for Active ACG Experiencing Multiple Momentary FREERUN

Started & Ended (shown for iSC2; iSC3 similar)

A CG - May 4, 2006 11:51:42.

A CG - May 4, 2006 11:51:44.
From : ( Unlocked, Enabled, Impaired)
To : ( Unlocked, Enabled, Active) - [903] ACTIVE GPS FREERUN ENDED.

A CG - May 4, 2006 11:51:45.

A CG - May 4, 2006 11:51:47.
From : ( Unlocked, Enabled, Impaired)
To : ( Unlocked, Enabled, Active) - [903] ACTIVE GPS FREERUN ENDED.
Service Impact
There is no service impact.

This multiple momentary locking and unlocking/free run behavior is not
uncommon GPSR operation. The ACG is not out-of-lock and free running
long enough to cause service interruptions.
EBTS Subsystem
3-20
SR 16.0
6881012Y79-B
23-Feb-09
Problem Isolation
There is actually no problem, just unusual intermittent ACG GPSR operation

at the affected EBTS site.
Recommended
Actions
No immediate action is necessary. These multiple momentary FREERUN

Started & Ended event messages can be disregarded.
At the OMC-R, continue to monitor the EBTS for multiple momentary
FREERUN Started & Ended event messages. They should cease within 24
hours after the ACG reset.
If this problem persists longer than 24 hours, check the site for proper GPS
coverage. Check the site statistics and site GPS satellite tracking statistics. If
satellite statistics indicate zero satellites tracked for extended periods of time,
troubleshoot the GPS system.
Verification
At the OMC-R, verify that the EBTS stops reporting multiple momentary
FREERUN Started & Ended event messages within 24 hours after the ACG
reset.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-21
Audio Problems Related to the Antenna
Scenario
Garbled, intermittent, or no audio during call setup.
Symptom
The customer reports garbled, intermittent, or no audio during call setup.
Service Impact
These issues are typically linked to one site and usually occur on interconnect
calls, but can also happen on dispatch calls. No alarms would be seen at the
OMC on issues like this; they are usually found by customer complaints.
These issues may be related to bad antennas.
Problem Isolation
Does not apply.
Recommended
Action
This scenario assumes that the issue is related to an antenna.

Send the technician to the site to fix the problem. The following actions are
performed by the technician at the site.
WARNING
To protect equipment and personnel from RF transmissions,

dekey the BR before disconnecting and reconnecting the
antenna cables.
TO
Resolve Antenna Issues at the EBTS Site
Step
Action
While drive testing, the technician determines what sector (if not
Omni) or BRs might be having the issue.
Connect the PC to the suspect BR(s) and login to the BR. Then type
get rx1rabid
The RABID counter should be zero on all three branches. If the
counter indicates branch imbalance on any of the receive paths,
troubleshoot the antenna path.
Take the available information and perform antenna sweeps to

determine the issues.
Check the feed line and connectors.
EBTS Subsystem
3-22
SR 16.0
6881012Y79-B
23-Feb-09
TO
Resolve Antenna Issues at the EBTS Site
Step
Verification
Action
Swap the antenna with the other RFDS (RF Distribution System)
cabinet to see where the problem is.
Replace the bad antenna.
Perform drive testing to verify that garbled audio is no longer present.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-23
Duplex Wattmeter VSWR Alarm Problem

Scenario
On an EBTS configured for low power operation, there is a chance of false

VSWR (voltage standing wave ratio) alarms which may cause BRs to de-key.
The issue being addressed in this scenario applies to both T1 and E1 systems.
Symptom
The VSWR alarm is a result of limited wattmeter accuracy under low power
operation. The false VSWR alarm triggers fault management software to dekey the BR, taking it out of service. Calls will potentially be dropped when
the BR is dekeyed and capacity of the cell will be reduced. Reduced cell
capacity can increase the number of blocked calls in the cell.
The wattmeter employs directional couplers, signal detectors, filters, opamps, and analog to digital converters to provide a measurement of the
antenna port power. The accuracy of the power monitor is limited by all of the
circuitry involved. The primary contributing factors to the finite accuracy of
the power monitor include the directivity of the coupler, detection threshold of
the signal detector, offset voltages associated with op-amp circuits, and
quantization error of the analog to digital converter. To complete the
processing of the wattmeter, EBTS software is utilized. Current EBTS
software monitors the output of the wattmeter and fault management procedures set a VSWR alarm if the detected VSWR is 4:1 or greater. Further, fault
management will de-key the BR if VSWR alarm is detected.
The wattmeter has been designed to provide acceptable accuracy over a
nominal range of operation from 100+ Watts down to approximately 10 Watts.
As cell sizes are reduced, the transmit power at the antenna port is reduced. At
low power operation the wattmeter accuracy is strained. With antenna port
power of 6 Watts and below, the wattmeters ability to accurately determine a
VSWR of 4:1 is diminished.
The accuracy of the wattmeter can provide a false reading of reflected power
of one to two watts. If the forward power is six Watts or less, then the 4:1
VSWR alarm may be triggered. The VSWR alarm will be triggered when the
reflected power reading is one-third the forward power reading. The VSWR
alarm will de-key the BR.
Service Impact
The finite accuracy of the wattmeter reading can trigger a VSWR alarm. Upon
detection of the VSWR alarm, the EBTS fault management software will dekey the associated transmitter. This BR is then taken out of service until the
alarm is cleared.
EBTS Subsystem
SR 16.0
3-24
6881012Y79-B
23-Feb-09
Worst Case Scenario

The BR will register a wattmeter VSWR alarm, the BR will also be de-keyed
and be taken out of service. If calls are in place when the BR is dekeyed, the
calls will be dropped. With the BR dekeyed, the affected cell has a reduction
in capacity. The reduced cell capacity can increase the number of blocked
calls for the cell.
Problem Isolation
The wattmeter accuracy is degraded at low antenna port transmit power. If the
total transmit power at the antenna for all carriers combined is less than or
equal to six watts, a false VSWR alarm is possible.
Recommended
Action
If an EBTS has an antenna transmit power of six watts or less and a VSWR
alarm of 4:1, the power monitor should be disconnected from the BR. To
disconnect the power monitor, the db-25 ALARM connection on the back
of the BR should be disconnected. After the ALARM connection has been
disconnected, the BR needs to be reset to re-initialize the software. The
VSWR alarm will be disabled after the BR comes out of reset.
Equipment Required
Laptop with Radio communication software and EIA232 communication
cable.
Test Procedure
On the BRs, use the get wattmeter MMI command to display the power
measured at the wattmeter.
Risk Assessment
The VSWR alarm can falsely be triggered and BR will de-key. The OMC-R
will still be able to read power at the BR but not the wattmeter.
Solution
The wattmeter should be disconnected on low power EBTS configurations.
Verification
None
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-25
EBTS 5MHZ/iPPS Signal Integrity Test for EBRC and Quad BR

Scenario
This scenario explains how to test the signal integrity of the 5MHz_1PPS
signal at the input to the Base Radio (BR).
The issue being addressed in this scenario applies to both E1 and T1 systems.
Symptom
The 5MHz/1PPS failure messages such as 1PPS out of window alarm or

External reference failure are reported by one or more Base Radio(s) within
an EBTS site resulting in subsequent resetting of the BRs configured with
EBRC or ExBRC modules or in a locked condition for BRs configured with
Legacy BRC modules.
The most probable cause of this failure is with degradation of the
5MHz_1PPS site reference signal at the Base Radios 5MHz/1PPS input port.
This problem may occur due to conditions including, but not limited to faulty
or improper cables and connectors, poor termination impedance, and electromagnetic interference. A faulty BR may also drag down the 5MHz/1PPS
signal resulting in degraded signal to all other BRs.
For Base Radios with Legacy BRCs:
Degraded 5MHz/1PPS signals produce External reference failure alarm and
No 1pps FREE running mode messages, but do NOT produce the 1PPS
out of window message. This causes the Base Radio to go into a LOCKED
condition. All active calls on the BR are dropped.
For QUAD Base Radios and Single Carrier Base Radios with
Enhanced BRCs (Gen2 BRs):
Degraded 5MHz/1PPS signals produce the 1pps out of window alarm
messages and External reference failure alarms. This will cause the Base
Radio to RESET. All active calls on the BR are dropped.
The examples below illustrate an OMC event for each type of BRC.
EBRC
processingFailureEvent - CntlrBrd - NC1963_Sophia, BR 21, Cab 2,
Pos
1, CntlrBrd 0 - Nov 27, 2002 05:05:48.
[32007] BR DSP Alarm - Clear. R09.08.13 1PPS out of window error
EBTS Subsystem
3-26
SR 16.0
6881012Y79-B
23-Feb-09
received from RX DSP1.(EBRC).
QUAD BRC
processingFailureEvent - CntlrBrd - D5_01860_WarenOutDr, BR 43,
Cab
4, Pos
3, CntlrBrd 0 - Nov 21, 2002 23:46:00. [32007] BR DSP Alarm Clear. R09.06.08 DSP Alarm A0.
Service Impact
Base Radios configured with EBRC or ExBRC modules may reset repeatedly.
These conditions will persist until a stable 5MHz/1PPs reference signal is
provided to the affected BR. Any resetting BRs will result in the dropping of
all current active calls on that BR. Any BRs in a lock condition will not
support any subscriber traffic and may eventually RESET.
Problem Isolation
Does not apply.
Recommended
Action
Equipment Required
Oscilloscope: e.g. Tektronix TDS 644B.
Oscilloscope used must have at least the following features/functions:
100 MHz bandwidth.
10 ns/div or less to 500 ms or more for horizontal sweep.
10mv/div or less to 5V/div or more vertical range.
Positive and negative edge trigger capability, auto/normal/single sweep

capability.
1Meg/50 ohm minimum input impedance (50 ohm is optional).
DC/AC coupling.
Dual channel (minimum requirement).
Persistence capability (Optional but highly desirable, enables captures of

infrequent occurrences).
Portable media storage capability to transfer and store waveform captures.
Note
Ensure that the oscilloscope has been calibrated within the period
recommended by the manufacturer or as use demands it.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-27
Oscilloscope Probes:
High impedance FET probes (1 M ohm or more)
<2 pF capacitance
Short probe length (0.5 inch)
Short ground clip (0.5 inch)
Note
Ensure that the Multimeter has been calibrated within the period
recommended by the manufacturer or as use demands it.
Multimeter
0 to 200 Ohm resistance scale with 1% precision.
Test Procedure
Note
In order to have minimal impact on service, these tests should be

completed during the maintenance window. Testing can be performed
on a live site by an experienced technician, but it will be harder to
determine the result and some loss of service may occur.
Whenever working on EBTS hardware, the ESD wrist strap should
always be worn and properly connected to the cabinet. The wrist strap
should be tight around the wrist with the metallic portion in contact
with dry skin. Please use the strap provided with the EBTS equipment.
Note
Terminator Impedance Test

Note
TO
Any repair or replacement of components must comply with the

equipment specified in Chapter 4 of Installation portion of the Gen 3
Site Controller System Manual (The most current version of
68P80801E30).
Test the Terminators
Step
Action
Remove the 5MHz/1PPS 50-Ohm terminator (PN0909906D01)

from the end of the site reference cabling. This terminator is
typically located at the top of the last EBTS RF rack in the system.
There may be multiple terminators at sites where multiple 5MHz/
1PPS reference lines are utilized. Repeat the following test for all
5MHz/1PPS terminators used at the site.
Note This same test can also be applied to the Ethernet 50 Ohm
terminators.
Visually inspect the cable, connectors and the terminator for

physical damage, corrosion or dirt and replace if necessary.
EBTS Subsystem
3-28
SR 16.0
6881012Y79-B
23-Feb-09
TO
Test the Terminators
Step
3
Action
Use a Multimeter to verify that the termination is between 48.45 and
53.55 ohms. Replace any terminator found to be outside of this
range.
Faulty or improper cables and connectors

Visually check for the following faults and correct any defective condition.
Only one 5MHz/1PPS 50-ohm terminator located at the end of any 5MHz/
1PPS chain.
Loose, dirty, or broken connectors.
Crushed, kinked, broken, frayed, or deformed cables.
Important
There is sensitive electronic circuitry directly connected to the BNC

5MHz/1PPS connector on the back of the BR and it is through this
connector that most ESD damage occurs. Since this area is very
sensitive to ESD, it is recommended that service technicians not probe
this port directly unless absolutely necessary as described above and
with the proper ESD protection in place.
Important
All testing methods detailed above result in some loss of service, as it is

not possible to turn off random BRs without affecting caller traffic or
software. However, if done correctly, allowing BRs that have been
removed from service to key up and return to service before taking the
next BR out of service, user impact will be minimal. For optimal time
considerations, the site should be taken off line, so that all BRs can be
tested and checked randomly.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-29
Oscilloscope Test
The integrity of the 5MHz_1PPS signal in the system can be checked with the
procedures shown below. These procedures should help identify signal
problems if they exist. A scope with screen capture capability is required (see
Equipment Required on page 27) so that the captures can be documented and,
if needed, communicated to Motorola (via email/fax, etc.). High impedance
and short leaded probes must be used so that the probe does not disturb the
signal. (see Oscilloscope Probes: on page 28).
TO
Test the Signal Integrity
Step
1
Action
At the Failing Base Radios 5MHz_1PPS BNC port:
a) Setup an Oscilloscope for 1V per division, and 100ns per

division.
b) Set the scope for DC input.
c) Set your trigger level at 1.0Vdc.
d) Select high impedance input (1M ohm) on the scope channel.
e) At the failing BR, disconnect the BNC T from the BR
without breaking the cable between the ACG and the 50 ohm
Termination at the end of the cable.
f) Add another T to the T from above.
g) Connect a high impedance probe (e.g. FET probe, <2 pF)
from the scope to the exposed center conductor of the
installed BNC T. Connect the ground of the probe to the
ground of the BNC T.
Note The probe and its ground connections used for tapping the
5MHz must be less than 1 inch in length.
h) Cause a single sweep to occur on the oscilloscope and

capture one each of a (25% hi / 75% low) signal and (75% hi
/ 25% low) signal. This can be accomplished by a few trials.
i)
j)
k)
l)
Save the screen captures to encapsulated postscript or other

electronically displayable format that can be easily sent
electronically.
If the 5MHz/1PPS errors are intermittent or occur
infrequently, free run the trigger (auto trigger mode) on the
scope and monitor the resulting scope traces over an
extended time period. This scope configuration only allows
for signal observation and not capture.
If problem is suspected to be infrequent, use the persistence
to attempt to capture the anomaly.
Connect the BNC port of the recently add T to the BR.
Repeat substeps h, i, and j.
EBTS Subsystem
3-30
SR 16.0
6881012Y79-B
23-Feb-09
TO
Test the Signal Integrity
Step
Action
Repeat the steps outlined in step 1 (above) at all other Base Radio
5MHz/1PPS ports at the site.
Note Since the 5MHz/1PPS cable is a transmission line, it is
recommended that all BR ports be verified to have good signal
integrity even if the Base Radios connected to those ports are not
experiencing a problem. Another reason to validate the 5MHz/1PPS
signal at all BR ports is that it is possible to have multiple defective
conditions on the line. In such cases you may find that replacement/
repair of a defective condition will serve to translate the signal
degradation to another point within the 5MHz/1PPS line.
Scope capture of 5MHz_1PPS 50-ohm termination point at the end

of the cable.
a) Repeat substeps a, b, and c of step 1.

b) Add a BNC T between the end of the cable and the
termination.
c) Repeat substeps g through j in step 1.
4
Repeat test procedure 1 for a scope setting 1Vdc/division and

50ns/division as well. This will give a close look at the signal.
Compare your resulting wave forms with the wave form examples
shown in Figure 3-4 to evaluate your results.
Figure 3-4 below is obtained from Chapter 6 (System Testing) of the Gen3
Site Controller Manual (68P80801E30) contained on the EBTS System
Manual CD ROM (98P80800A21). This figure shows the 5MHz/1PPS signal
mask. The upper picture shows the 25/75 percent duty cycle mask and the
lower picture shows the 75/25 percent duty cycle mask. These signal values
must be maintained to guarantee proper operation of the Base Radio
equipment.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-31
Figure 3-4
Site Reference - 25% and 75% Duty Cycle Pulse Mask
The examples in Figure 3-5 illustrate two good 5MHZ signals. The first is a
25%/75% duty cycle portion of the signal and the second is the inverted or
75%/25% duty cycle portion of the signal.
EBTS Subsystem
3-32
SR 16.0
6881012Y79-B
23-Feb-09
Figure 3-5
Signal Examples
Table 3-1
General Troubleshooting Symptom/Cause/Action Table
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-33
Verification
If any Base Radio within a site is reporting a 5MHz or 1PPS fault, that site
should be examined to ensure that all 5MHz/1PPS cables and connections are
in good condition and properly operating. A visual examination should be
conducted and all faulty hardware must be replaced or repaired. Where visual
examinations fail to correct the failure condition, then oscilloscope tests
identified within this scenario must be conducted to locate the fault and repair
it.
EBTS Subsystem
3-34
SR 16.0
6881012Y79-B
23-Feb-09
Incorrectly Programmed ExBRCs FSB

Scenario
Some CLF1560L exciter/base radio controllers (ExBRCs) left the factory

with an incorrect register value. Modules with this issue are likely to contain
serial numbers that fall in the range of CAF061N7SM to CAF082FB3C.
Investigation to date has identified that the modules are built correctly and are
not defective. The factory test process has been updated to prevent further
escapes of improperly programmed units.
Symptom
A false Exciter LO Feedthrough Alarm is generated. There is the possibility

of an increased drop call rate.
Service Impact
This defect could result in an increased drop call rate. If the recommendations
outlined below are not followed, the alarm will persist. If the alarm is ignored,
it is possible that a true exciter feedthrough occurrence might occur, resulting
in degraded Tx EVM (Error Vector Magnitude) and impacting BER on the
subscriber unit.
Problem Isolation
No workaround exists for this issue.
Recommended
Action
Look for an LO feedthrough alarm to verify that a misprogrammed

calibration factor is the likely source of the issue, which should be checked
per the procedure listed. Call the Motorola CNRC. The CNRC will assist with
the procedure to change the affected register on the ExBRC to its correct
value.
Note The customer will need a computer with a serial port, a terminal
emulator program, and a serial cable to communicate with the ExBRC.
Alternatively, the product can be returned to the repair depot.
TO
Change the Affected Register on the ExBRC to its Correct

Value
Step
1
Action
At the cell site, connect a cable to the MMI port on the front of the
ExBRC.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-35
TO
Change the Affected Register on the ExBRC to its Correct

Value
Step
2
Action
Start a terminal emulator program such as Hyperterm (Hyperterm
is shipped with Microsoft Windows and can be found in
Programs->Accessories->Communications).
The serial connection should be set with the following parameters:
Verification
Baud: 19200 baud
Parity: none
Data bit: 8
Stop bit: 1
Flow control: none
Com port: typically 1
Press the Reset switch on the front of the ExBRC after the serial
connection is established.
When Press any key to enter test mode appears, press the space
bar.
When the > prompt appears, enter login -udev
A seven or eight digit number should appear followed by a :.

Note The customer will need to be on the telephone with a CNRC
representative to complete the log in.
Ask the CNRC representative for the corresponding password.
Enter that number into the terminal emulator.
If the dev> prompt is not returned, then repeat steps 7 to 8 until

successful. In some cases multiple attempts may be required.
10
Enter the cf -otx_all command
11
Note the value of calibration factor number 25. If it is above 75, then
the TX calibration factor programming was OK.
12
If calibration factor 25 is not above 75, then enter cf -otx_all -c25 f90.
13
Enter reset -ocontrol for the change to take effect.
14
Remove the cable. The ExBRC should now be fully functional.
When the change takes effect, the alarm should no longer be reported.
EBTS Subsystem
3-36
SR 16.0
6881012Y79-B
23-Feb-09
Resolving Visibility Issues to the OMC-R
Resolving Visibility Issues to the OMC-R
There are no commonly occurring issues for this topic at this time.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-37
Resolving Connectivity Issues to other Network Elements
Resolving Connectivity Issues to other Network

Elements
EBTS Subsystem
3-38
SR 16.0
6881012Y79-B
23-Feb-09
Resolving Download Issues
Base Radio (BR) TX Initialization/Diagnostic Testing Failures and

Possible BR Application Code Download Issue
Scenario
A BR is being added to an EBTS site.

A technician is at the EBTS site performing configuration/setup and testing/
verification for the added BR.
Note BR configuration/setup and testing/verification is performed
according to the following manual: iDEN Enhanced Base Transceiver
System (EBTS) Volume 1of 3 System Installation and Testing
(68P80801E35).
For a single channel or QUAD channel BR, the technician verifies that the BR
has completed the application code download from the iSC.
A service computer (i.e., PC) is cabled to the BRC (BR Controller) RS232
serial port STATUS connector on the BR control module front panel.
The BR goes through an initialization process, including diagnostic testing,
when the power to the BR is turned on (power on reset).
After the BR is powered on, pressing the BRC RESET button on the BR
exciter/control module front panel followed by pressing any key on the
service computer keyboard launches the test application.
The test application allows any initialization/diagnostic errors or BR alarm
conditions to be output to the service computer via the STATUS port
connector.
Symptoms
The BR fails to successfully initialize and reports diagnostic errors to the

service computer. BRC reports CORE_SOFTWARE_ERROR. For an
example of the report, refer to Figure 3-6 BRC error log report for a single
channel BR (other BRs would be similar) on page 3-40.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-39
Figure 3-6
BRC error log report for a single channel BR (other BRs would be similar)
log_error:
Software Version: R09.08.13
Platform: EBRC
Date: 3/10/2003
Time: 18:15.08 (GMT)
File: TX_CONFIGURE_EXTERNAL
Task: CORE
Function: CORE
Line: 286
Comments: CORE_SOFTWARE_ERROR
Detail 1: CE_CHECK_VALUE
Detail 2: TX_CONFIGURE_EXTERNA
Detail 3: 0x0000011e
Detail 4: 0x00000000
Detail 5: 0x00000000
Detail 6: 0x00000000
Detail 7: 0x00000000
Detail 8: 0x00000000
log_error:
Software Version: R09.08.13
Platform: EBRC
Date: 3/10/2003
Time: 18:15.08 (GMT)
File: TX_INIT
Task: CORE
Function: CORE
Line: 352
Comments: CORE_SOFTWARE_ERROR
Detail 1: CE_CHECK_VALUE
EBTS Subsystem
3-40
SR 16.0
6881012Y79-B
23-Feb-09
Detail 2: TX_INIT
Detail 3: 0x00000160
Detail 4: 0x00000003
Detail 5: 0x00000000
Detail 6: 0x00000000
Detail 7: 0x00000000
Detail 8: 0x00000000
Service Impact
Unable to use potential resources of the additional BR.
Problem Isolation
BR receiver operation verification/testing is successful, but BR transmitter

(TX) will not key up.
Closer examination of the BRC error log report shows that detail 3 under line
286 and line 352 in the example (Figure 3-6 BRC error log report for a single
channel BR (other BRs would be similar) on page 3-40) are not all zeros
going across. This is an indication that the BR is failing transmitter initialization due to exciter Q offset not being programmed to non-zero values.
Exciter I and Q Offset must be programmed to all zeros. Programming either
the Exciter I or Q Offsets with non-zero values causes BR TX initialization
failure.
For a single channel or QUAD channel BR:
The application code downloaded from the iSC may be corrupt causing
improper BR exciter module programming
The BR exciter module cannot be properly programmed due to a
hardware malfunction
Recommended
Actions
The technician at the EBTS site performs the following procedure for the
single channel or QUAD channel BR being added
TO
Resolve Single/QUAD Channel BR Diagnostic Failure Issue
Step
Action
Power off the faulty BR.
Connect the service computer to the active ACG and launch the
communication software (Procomm Plus or equivalent).
Reset the active ACG and press a key when prompted to press a
key to enter configuration mode.
Type rm br2.code to delete the BRs application code.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-41
TO
Resolve Single/QUAD Channel BR Diagnostic Failure Issue
Step
Action
Type exit to place the iSC back into service and wait for the iSC
to download the br2.code file from the OMC.
Power on the BR and verify that the BR has completed the

application code download from the iSC.
Further verify that initialization was successful and that no BRC

errors are reported.
If BR initialization is not successful and BRC errors are reported to

the service computer, replace the BR exciter module Field
Replaceable Unit (FRU).
Refer the corresponding applicable single channel BR FRU
Replacement Procedures section in the Troubleshooting chapter of
the iDEN Enhanced Base Transceiver System (EBTS) Volume 2 of
3 Base Radios (68P80801E35).
Verification
Complete configuration/setup and testing/verification for the added

BR.
Problem resolution verifications are performed as part of the aforementioned

Recommended Actions.
EBTS Subsystem
3-42
SR 16.0
6881012Y79-B
23-Feb-09
Resolving Configuration Issues
Newly Installed BRs Do Not Come In Service - Ethernet Loop Carrier

Limit Exceeded
Scenario
Newly installed Base Radios (BRs) cannot communicate with ACG/iSC and
therefore the BRs never come in service.
The EBTS site ACG/iSC communicates with the site BRs via a 10Base2
Ethernet LAN interface. This Ethernet LAN consists of a 50-Ohm coaxial
cable bus with one end that terminates at a 10Base2 Ethernet port on the rear
of the ACG/iSC. This cable bus is routed into an RF cabinet where it connects
via a T-connector to the 10Base2 Ethernet port on the rear of each BR. The Tconnectors and coaxial cabling form a chain that loops through the cabinet
starting with the bottom BR and then onto the next BR moving toward the top
of the RF cabinet and out to the next RF cabinet and its BRs. The end of the
chain terminates in a 50-Ohm load connected on the output of the last RF
cabinet in the chain.
Each 10Base2 Ethernet port on the ACG/iSC can support up to 24 carriers
maximum per Ethernet chain/loop. The number of carriers correlates to
number of BRs as follows:
For all single channel BRs, a maximum of 24 BRs.
For all QUAD channel BRs using all four channels, a maximum of 6 BRs.
The iSC2 has one 10Base2 Ethernet port and can support one Ethernet chain/
loop with up to 24 carriers maximum.
The iSC3 has three 10Base2 Ethernet ports and can support three Ethernet
chains/loops for a possible 72 carriers maximum. However 36 carriers is the
maximum supported by EBTS software.
When the number of carriers/BRs exceeds the maximum per Ethernet chain/
loop, those violator BRs at the end of the chain cannot communicate with the
ACG/iSC and are not configured and remain out-of-service.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-43
Symptoms
The ACG/iSC detects that the 24 carriers maximum limit on an Ethernet

chain/loop is being exceeded. The ACG/iSC prevents the violating BRs from
registering. The ACG/iSC reports the following equipment alarm to the
OMC-R: [913] More than 24 carriers on the local Ethernet loop - Major.
The OMC console Event Display shows an equipment Failure Event alarm
[913] - Major for each violating BR rejected by the ACG/iSC at the affected
EBTS site. This alarm message indicates the following:
Ethernet Loop ID (1, 2, or 3) for the affected Ethernet loop
Cabinet ID (1-8) where the violating BR is located
BR cabinet position ID (1-6) for violating BR
The violating BRs fail to successfully come into service because the BR
Controller (BRC) cannot communicate with the ACG/iSC via the Ethernet
LAN. The BRC front panel LEDs on the violating BRs indicate that the BR is
out-of-service.
Service Impact
Unable to use potential resources of the newly installed BRs.
Problem Isolation
This issue is due to human error when installing BRs at the EBTS site without
considering the local Ethernet loop configuration.
EBTS Subsystem
3-44
SR 16.0
6881012Y79-B
23-Feb-09
Recommended
Actions
For an EBTS site with ACG using the iSC3 platform, take the following
actions:
1. Reduce the number of BRs connected to the indicated local Ethernet loop
so as not to exceed the 24 carriers maximum limit. Disconnect the
violating BRs from this Ethernet loop.
2. Reconnect the violating BRs to another local Ethernet loop having enough
BR/carrier capacity.
Evenly distribute the BRs on the loop so as to minimize BR outage due to
a single Ethernet loop failure. For details on Ethernet loop and BR
distribution, refer to the following manuals:
For iSC2: iDEN Integrated Site Controller System Manual

(68P81098E05)
For iSC3: iDEN Gen 3 Site Controller System Manual (68P80801E30)
iDEN Enhanced Base Transceiver System (EBTS) Volumes 1, 2 and 3;

(68P80801E35)
Note The 10Base2 Ethernet ports 2 and 3 on the iSC3 must be used if the
EBTS site is configured for more than 24 carriers.
For an EBTS site with ACG using the iSC2 platform and requiring more than
24 carriers, take the following action:
1. If the affected EBTS site must be equipped with more than 24 carriers,
upgrade ACGs to the iSC3 platform.
For an EBTS site with ACG using the iSC2 platform and upgrading ACGs to
the iSC3 platform is not an option, take the following actions:
1. Reduce the number of BRs connected to the indicated local Ethernet loop
so as not to exceed the 24 carriers maximum limit. Disconnect the
violating BRs from this Ethernet loop.
2. Remove the violating BRs and use them at another EBTS site with local
Ethernet loop having enough BR/carrier capacity.
Verification
Verify that the OMC console Event Display shows an equipment Failure
Event alarm [913] - Clear for each previous violating BR at the affected EBTS
site.
Verify that the previous violating BRs successfully come in service.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-45
Newly Installed BRs Not Keying Up After Site Download - 5MHz/1PPS

Loop Overload
Scenario
Newly installed Base Radios (BRs) receive site download from ACG/iSC via
local Ethernet loop, but cannot key up.
The EBTS site ACG/iSC distributes a 5MHz/1PPS signal to all BRs at the
site. This signal distribution is via a 50-Ohm coaxial cable bus with one end
that terminates at a 5MHz/1PPS output port on the rear of the ACG/iSC. This
cable bus is routed into an RF cabinet where it connects via a T-connector to
the 5MHz/1PPS input port on the rear of each BR. The T-connectors and
coaxial cabling form a chain that loops through the cabinet starting with the
bottom BR and then onto the next BR moving toward the top of the RF
cabinet and out to the next RF cabinet and its BRs. The end of the chain terminates in a 50-Ohm load connected on the output of the last RF cabinet in the
chain.
If a BR connected to a 5MHz/1PPS chain/loop detects a degraded 5MHz/
1PPS signal, the BR transmitter is not allowed to key up.
Items that can cause degradation of the 5MHz/1PPS signal and affect the
operation of BRs connected to the chain/loop are as follows:
improper 5MHz/1PPS signal from the ACG/iSC
cabling or connectors with improper impedance and/or too much signal loss
improper coaxial cable bus termination impedance; BR with defective

5MHz/1PPS port interface, improper end of the chain/loop termination or
too many BRs connected to the chain/loop.
This scenario assumes that all of the aforementioned items are proper except
for too many BRs are connected to a 5MHz/1PPS chain/loop.
A 5MHz/1PPS output port on the ACG/iSC can typically support 13 to 15
BRs per 5MHz/1PPS chain/loop.
Note Some 5MHz/1PPS chains/loops may support slightly less than 15 BRs,
but 5MHz/1PPS chains/loops should never be configured with more
than 15 BRs.
The iSC2 has two 5MHz/1PPS output ports (labeled OUT 1 and OUT 2) and
can support two 5MHz/1PPS chains/loops per EBTS site.
The iSC3 has three 5MHz/1PPS output ports (labeled SITE REF OUT 1,
SITE REF OUT 2, SITE REF OUT 3) and can support three 5MHz/1PPS
chains/loops per EBTS site.
EBTS Subsystem
3-46
SR 16.0
6881012Y79-B
23-Feb-09
When too many BRs are connected to a 5MHz/1PPS chain/loop, an overload

condition on the 5MHz/1PPS chain/loop exists which degrades the 5MHz/
1PPS signal. The following events occur:
BRs in the chain/loop detect the overload condition and generate alarms.
These BRs may also fail due to the effects of the degraded 5MHz/1PPS
signal.
The exact quantity of BRs affected by the overload condition depends on
the severity of the overload and degradation of the 5MHz/1PPS signal;
more severe, more degraded, more BRs affected
less severe, less degraded, fewer BRs affected
Symptoms
The added violator BRs at the end of the chain detect the overload condition
and generate alarms. These BRs fail due to the effects of the degraded
5MHz/1PPS signal.
The local oscillators in all failing BRs cannot synchronize to the ACG/iSC
5MHz/1PPS. Therefore the BR Controller (BRC) does not allow the BR
transmitter to key.
The BRCs of affected BRs detect an overload condition on the 5MHz/1PPS

chain/loop. The BRC prevents BR transmitter keying. The BRC sends an
alarm report to the ACG/iSC which reports the following BR equipment
alarm to the OMC-R: [35033] Overload condition on 5MHz/1PPS line Major.
The OMC console Event Display shows a BR Equipment Failure alarm
[35033] - Major for each affected BR including each violating BR at the
affected EBTS site. This alarm message indicates the following:
5MHz/1PPS Line (1, 2, or 3) for the affected 5MHz/1PPS chain/loop
Cabinet ID (1-8) where the alarming BR is located
BR cabinet position ID (1-6) for alarming BR
The affected BRs cannot synchronize to the ACG/iSC 5MHz/1PPS. Therefore

the BR Controller (BRC) does not allow the BR to be in service and the transmitter cannot key. The BRC front panel LEDs on the affected BRs indicate
that the BR is out-of-service and not able to key its transmitter.
Service Impacts
Affected BRs are out-of-service reducing call processing capacity.

Unable to use potential resources of the newly installed BRs.
Problem Isolation
This issue is due to human error when installing BRs at the EBTS site without
considering the 5MHz/1PPS chain/loop configuration.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-47
Recommended
Actions
For an EBTS site with ACG using either the iSC2 or iSC3 platform, take the
following actions:
1. Reduce the number of BRs connected to the indicated 5MHz/1PPS line so
as not to overload the line. Disconnect the violating BRs from this 5MHz/
1PPS chain/loop.
2. Reconnect the violating BRs to another 5MHz/1PPS chain/loop having
enough BR capacity.
Evenly distribute the BRs on the chain/loop so as to minimize BR outage
due to a single 5MHz/1PPS chain/loop failure. For details on 5MHz/1PPS
chain/loop and BR distribution and cabling, refer to the following
manuals:
For iSC2: iDEN Integrated Site Controller System Manual

(68P81098E05)
For iSC3: iDEN Gen 3 Site Controller System Manual (68P80801E30)
iDEN Enhanced Base Transceiver System (EBTS) Volumes 1, 2 and 3;

(68P80801E35)
3. Ensure that all coaxial cabling and terminations for the applicable 5MHz/
1PPS chain/loop are installed as described in the aforementioned manuals.
Verification
Verify that the OMC console Event Display shows a BR Equipment Failure
alarm [35033] - Clear for each previous alarming BR at the affected EBTS
site.
Verify that all BRs on the applicable 5MHz/1PPS chain/loop are in service
and that the transmitters key.
EBTS Subsystem
3-48
SR 16.0
6881012Y79-B
23-Feb-09
Resolving Provisioning Issues
Resolving Provisioning Issues
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-49
Resolving Loss or Disruption of Service Issues
Resolving Loss or Disruption of Service Issues
EBTS Subsystem
3-50
SR 16.0
6881012Y79-B
23-Feb-09
Resolving Database Issues
Resolving Database Issues
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-51
Resolving Billing Issues
Resolving Billing Issues
EBTS Subsystem
3-52
SR 16.0
6881012Y79-B
23-Feb-09
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
3-53
NOTES...
EBTS Subsystem
3-54
SR 16.0
6881012Y79-B
23-Feb-09
Appendix A
EBTS GPS Troubleshooting
Information
In This Chapter
See Page
Topic
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Introduction ................................................................................... A-2
Scope ............................................................................................ A-2
GPS Hardware .............................................................................. A-2
GPS Failures that cause EBTS Reset . . . . . . . . . . . . . . . . . . A-3

No GPS Lock ................................................................................ A-3
Loss of GPS Lock ......................................................................... A-3
Critical GPS Fault.......................................................................... A-3
Traps and Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

[201] ACG Reset ........................................................................... A-4
[305] TFR/SRI Detected Alarm...................................................... A-4
[306] GPS Problem-0 Tracked Satellites....................................... A-4
[320] ACG Failed to Achieve GPS Sync ....................................... A-4
[313] ACG Freerun Timeout .......................................................... A-5
[314] HSO 1PPS Missing .............................................................. A-5
[316] HSO Phase Not Locked ....................................................... A-5
[317] Bad Original Position in GPSR............................................. A-5
[318] HSO Frequency Not Locked ................................................ A-6
[319] HSO Failed........................................................................... A-6
GPS SM transitions with reason [901]........................................... A-6
Immediate switchover (30 minutes or less) ................................... A-6
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
A-1

Overview
Overview
Introduction
This chapter describes the various methods by which EBTS automatic resets
due to GPS related problems can be diagnosed.
The EBTS sends a variety of alarms and traps to the OMC-R which can
indicate the presence of a GPS problem. Depending on the exact alarms sent,
the problem could be with either of the following:
the EBTS not being able to see the required minimum number of satellites
or an issue with the EBTS GPS hardware
Knowing why the EBTS sends the alarms should aid in diagnosis of faulty
hardware and hopefully prevent misdiagnosis of faulty hardware when the
site configuration is to blame.
Scope
The scope of this chapter is to describe how several EBTS alarms and traps
relate to the operation of the EBTS GPS subsystem. It is not intended to
provide a formal set of troubleshooting steps, but is meant to provide
background information for those who may do troubleshooting of EBTS GPS
related problems.
GPS Hardware
The Site Reference ISA (SRI) resides in the ACG itself. It contains the GPS
receiver on a replaceable daughter board. In addition, the SRI contains a High
Speed Stability (HSO), which is tuned to the same phase and frequency as the
1 pulse-per-second (1PPS) signal from the GPS satellites. This is used to
provide a more stable 1PPS to the Base Radios (BRs) at the EBTS site. The
SRI communicates with the ACG via a serial connection. In addition, there is
a connection from the SRI to the external GPS antenna. Finally, a dedicated
connection from the SRI to the BRs provides the 1PPS signal and other time
synchronization information. Note that the standby ACG is also present on the
same 1PPS line as the active ACG, however, only one ACG is ever driving
this 1PPS line at a time. The two ACGs have entirely separate hardware, GPS
antennas, and cabling.
EBTS Subsystem
SR 16.0
A-2
6881012Y79-B
23-Feb-09

GPS Failures that cause EBTS Reset
GPS Failures that cause EBTS Reset
The GPS subsystem is critical to the successful operation of the EBTS. If the
GPS fails, it can lead to an automatic EBTS reset, either in an attempt to allow
the redundant ACG to take control, or to reinitialize the GPS hardware on the
active ACG. There are three different ways in which the GPS can fail and
cause an automatic EBTS reset. These are as follows:
No GPS Lock
Loss of GPS Lock
Critical GPS Fault
No GPS Lock
Before the EBTS can process calls, it must first get a time and location lock
from the GPS subsystem. Also, the standby ACG will not take over operation
unless it already has a GPS lock. If the standby ACG GPS locks prior to the
active ACG GPS locking, a ten minute timer is started. If this timer goes off
before the active ACG GPS locks, then the EBTS will reset and the standby
ACG will take over as active. Also, if the active ACG GPS does not lock
within 30 minutes of the EBTS initialization, the EBTS will reset so that the
GPS hardware is reinitialized.
Loss of GPS Lock
If some time after the active ACG GPS locks and then the GPS lock is lost, a
four-hour timer is started. The EBTS will continue to process calls during this
time period. However, if the active ACG GPS lock does not return within four
hours, the EBTS will automatically reset. The most likely cause of this issue
is satellite tracking, possibly due to a faulty antenna or connection from the
antenna to the ACG.
Critical GPS Fault
There are several critical faults which may occur within the GPS subsystem.
If any of these critical faults occur within the first 30 minutes after EBTS
initialization, the EBTS will automatically reset when either the standby ACG
GPS locks or the 30 minute site initialization timer expires, whichever occurs
first. If the critical fault occurs more than 30 minutes after EBTS initialization, the EBTS will automatically reset immediately.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
A-3

Traps and Alarms
Traps and Alarms
The EBTS has several traps and alarms that may get sent to the OMC-R in the
case of a GPS fault. These traps and alarms can be used to begin troubleshooting the cause of the GPS fault.
[201] ACG Reset
This alarm is reported every time the ACG-OMC link is reestablished after an
EBTS reset. The additional text found in this alarm offers some indication of
whether or not the reset is due to GPS issues. For releases SR13.4 and earlier,
the EBTS will report one of the following additional text in the case of a GPS
fault:
ACG Initiated Redundancy Switch: old Active is new Active
ACG Initiated Redundancy Switch: old Stby is new Active
In SR13.4 and earlier, this additional text is also reported when the EBTS is
unable to bring up an external links for 1 hour as well. So, in cases where the
EBTS has been up for more than 1 hour prior to resetting, other alarms must
also be examined in determining whether or not this is a GPS fault.
In SR14.0 and later, the additional text looks like this:
ACG Initiated Switch: old Active is new Active 123456789 <x>
ACG Initiated Switch: old Stby is new Active 123456789 <x>
In this text, the number 123456789 will be replaced by the serial number of
the ACG reporting the alarm. The <x> will be replaced by a numeric code,
indicating the internal reset reason. If this number is 42 or 44, then the reset
was due to a GPS fault.
[305] TFR/SRI
Detected Alarm
This alarm indicates that a fault has been detected with the GPS hardware
located on the ACG. Repeated resets with this alarm are a strong indicator that
the GPS hardware on that ACG is damaged.
[306] GPS Problem-0

Tracked Satellites
This alarm causes the system to place the affected ACG in the impaired state.
The High Stability Oscillator (HSO) of the affected ACG starts to free run
because the HSO frequency is no longer locked to GPS timing. In addition,
the system starts a 4-hour Free-Run timer if the affected ACG is currently
Active
[320] ACG Failed to

Achieve GPS Sync
This alarm is reported just prior to the EBTS reset. It indicates that the No
GPS Lock condition, described earlier, occurred where no GPS lock was
ever achieved.
EBTS Subsystem
A-4
SR 16.0
6881012Y79-B
23-Feb-09

Traps and Alarms
If the EBTS switches operation to the standby ACG after resetting, this alarm
indicates that only one of the two ACGs was unable to get a GPS lock. In that
case, troubleshooting efforts should focus on the GPS antenna and cabling
going to the ACG which is unable to get GPS lock first, and to the GPS
hardware in the ACG second.
If EBTS operation remains on the active ACG after resetting, this alarm
indicates that neither of the ACGs was able to get a GPS lock. If this is a
repetitive occurrence on the site, the placement of the GPS antennas and the
site itself should be investigated to ensure that the site is not being shadowed.
Such shadowing of the GPS antennas prevents proper site operation. In rare
cases, this can also be indicative of antenna, cabling or hardware issues on
both of the ACGs, although not if both the active and standby ACG were
operating properly and lost GPS lock at the same time.
[313] ACG Freerun

Timeout
This alarm is reported just prior to the EBTS reset. It indicates that the Loss
of GPS Lock condition described earlier, occurred where GPS lock was lost
for four consecutive hours. Troubleshooting is similar to the [320] alarm. In
fact, in many cases the EBTS may begin reporting resets and [320] alarms
after this first reset. Again, if the standby takes over operation after the reset,
it is indicative of antenna or cabling problems on one of the ACGs. If the
active takes over operation after the reset, it may be indicative of shadowing
issues.
[314] HSO 1PPS

Missing
This alarm indicates that the GPS hardware has reported that the 1PPS signal
from the HSO has disappeared. Repeated resets with this alarm are a strong
indicator that the GPS hardware on that ACG is damaged.
[316] HSO Phase Not

Locked
This alarm is reported when the 1PPS signal being generated by the GPS
hardware on the ACG is more that 30ms out of phase with the 1PPS signal
coming from the satellites. This can be caused by either a problem with
satellite visibility or with a problem with the GPS hardware on the ACG.
However, if it is a problem with the GPS hardware on the ACG, this alarm
should only be reported when one of the two ACGs at the site is running as
active.
[317] Bad Original

Position in GPSR
This alarm is reported when the original position data in the GPS hardware is
inconsistent with the data coming from the satellites. This may occur when a
previously deployed ACG is redeployed at a new site. However, if this occurs
frequently, it may indicate a problem with the GPS hardware.
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
A-5

Traps and Alarms
[318] HSO
Frequency Not
Locked
This alarm indicates that the frequency of the 1PPS signal being generated by
the GPS hardware does not match the frequency of the 1PPS signal coming
from the satellites. This can be caused be either a problem with satellite
visibility or with a problem with the GPS hardware on the ACG. However, if
it is a problem with the GPS hardware on the ACG, this alarm should only be
reported when one of the two ACGs at the site is running as active.
[319] HSO Failed
This alarm indicates that the HSO hardware that generates the proper 1PPS
signal has failed. The hardware must be replaced.
GPS SM transitions
with reason [901]
The GPS SM (State Machine) has a reason code of [901] that corresponds to a
critical GPS fault. If a critical fault occurs in addition to any alarms listed
above, the SM will transition to the - Locked, Enabled, Idle - state with a
reason of [901]. Unfortunately, if this state change is recorded, but none of the
traps listed above are seen, nothing can be determined other than there is a
GPS problem without further investigation at the site.
Immediate
switchover (30
minutes or less)
In some cases, the GPS critical fault may occur before the ACG-OMC link
has a chance to come up. However, the site will not reset until either the
standby ACG GPS has locked or 30 minutes have passed, whichever comes
first. The [201] ACG Reset alarm, described earlier, will be reported with the
applicable additional text. This fault will be due to GPS issues. Unfortunately,
no further determination can be made without visiting the site and examining
the ACG, via the console, for GPS errors.
EBTS Subsystem
A-6
SR 16.0
6881012Y79-B
23-Feb-09
Index
Numerics
5MHz/1PPS
Newly Installed BRs Not Keying Up After Site Download 5MHz/1PPS Loop Overload 3-34
part of Site Timing Reference 1-8
5MHz/1PPS Timing Reference Signal, See 5MHz/1PPS
800/900 MHz Antenna Diplexer
Description 1-14
A
Access Control Gateway, See ACG
ACG
201- ACG Reset A-4
305- TFR/SRI Detected Alarm A-5
313- ACG Freerun Timeout A-5
314- HSO 1PPS Missing A-5
316- HSO Phase Not Locked A-5
317- Bad Original Position in GPSR A-5
318- HSO Frequency Not Locked A-6
320- ACG Failed to Achieve GPS Sync A-4
Description 1-7
EBTS Site Not Reporting ecell Statistics To OMC-R 3-41
GPS Hardware A-2
GPS Problem - 0 Tracked Satellites 3-9
High Stability Oscillator (HSO) Failure 3-4
Immediate switchover (30 minutes or less) A-6
Interfaces 1-8
Links 2-32
Multiple Momentary FREE RUN Events 3-18
Newly Installed BRs Do Not Come In Service - Ethernet
Loop Carrier Limit Exceeded 3-31
Physical Links 2-32
Recovery from ACG Failures 2-35
Reliable Logical Links 2-32
State Management within the ACG 2-38
ACG Links 2-32
Alarm Description
201- ACG Reset A-4
305- TFR/SRI Detected Alarm A-5
313- ACG Freerun Timeout A-5
319- HSO Failed A-6
GPS SM transitions with reason -901 A-6
Alarm Traps to the OMC 2-30
Alert
Caution with symbol definition xviii
Caution without symbol definition xviii
Danger definition xviii
definitions xviii
Important definition xviii
Note definition xviii
Warning definition xviii
Antenna Duplexer
Description 1-13
B
Base Radio
Description 1-9
Base Radio Tests 2-27
Base Radio, also See BR
BR
Issue 3-27
Base Radio Controller (BRC) States 2-37
Base Radio Controller States 2-36
Components 1-9
Description of Single Channel BRC Indicators 2-17
function 1-9
QUAD Channel Ex/BRC Indicators 2-18
Recovery from PCCH Base Radio Failures 2-34
Single Channel BRC Indicators 2-17
types 1-9
C
Capacity
EBTS Base Radios 1-9
iSC3 T1 lines 1-7
Quantity of RF channels per BR type 1-9
Caution with symbol
General Safety definition xviii
Caution without symbol
Combiner
EBTS RF 1-13
Communication Link Failures 2-33
D
Danger
DAP
CD-ROM/tape stuck in the tape drive 3-21
CPU hardware failure 3-23
Data Collection
Console Logs 2-7
Drive Test Application 2-9
Ethernet Capture 2-8
J2300 Protocol Analyzer 2-8
OMC Events & Alarms 2-7
T1 Tester 2-8
Diagrams
ACG/iSC and iMU/EAS Block Diagram 1-15
Antenna Diplexer Block Diagram 1-18
BR Block Diagram 1-16
Duplexer RFDS Block Diagram 1-17
EAS Front Panel Detail 2-25
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
Index
EAS2 Front Panel Detail 2-25
iDEN System Diagram 1-6
iMU Front Panel Detail 2-24
iSC2 Front Panel Detail 2-13
iSC3 Front Panel Detail 2-15
OMC Alarm Display & Site Status Display Detail 2-12
QUAD Channel BR Exciter/Controller Module Front Panel
Detail 2-18
Single Channel BR Controller Module Front Panel Detail
2-17
Digital Cross-connect Switch (DCS) 1-7
Diplexer 1-14
Document Conventions
General Safety xviii
keystrokes xviii
mouse clicks xviii
new terms xviii
screen output xviii
sub-menu commands xviii
user input xviii
Description 2-29
Usage 2-29
Duplexer 1-13
E
EBTS
Control Hardware 1-7
EBTS Equipment-related Problems 2-41
Front Panel Indicators 2-13
GPS Failures that cause EBTS Reset A-3
Subsystem Components 1-7
Subsystem Description 1-6
Subsystem Troubleshooting Overview 1-2
Traps and Alarms A-4
EBTS Indicators
EAS Front Panel Indicators 2-25
EAS2 Front Panel Indicators 2-25
iMU Front Panel Indicators 2-24
iSC2 Front Panel Indicators 2-13
QUAD Channel Ex/BRC 2-18
Single Channel BRC 2-17
Enhanced Base Transceiver System, See EBTS
Ethernet LAN
Communication Interface between BRC and ACG/iSC 1-9
Data path between ACG/iSC and BRs 1-8
Ethernet Capture 2-8
Ethernet, physical link 2-32
iDEN Ethernet Analyzer Detective Software Users
Manual -xiv
Physical Link 2-33
Radio Link between ACG/iSC and BRs 1-9
Ethernet Local Area Network (LAN), See Ethernet LAN
F
Field Replaceable Units (FRU)
reference for EBTS FRU failure isolation guide and
replacement procedures 2-5
G
General Safety
Caution with symbol definition xviii
Caution without symbol definition xviii
Danger definition xviii
document conventions xviii
Important definition xviii
Note definition xviii
Warning definition xviii
Global Positioning System Receiver, See GPSR
Global Positioning System, See GPS
GPS
GPS Failures that cause EBTS Reset A-3
GPS Hardware A-2
GPS SM transitions with reason -901 A-6
GPSR
GPS Hardware A-2
H
High Stability Oscillator, See HSO
HSO
319- HSO Failed A-6
I
iDEN Monitor Unit/Environmental Alarm System, See iMU/
EAS
iDEN Open Problem List, description & location 2-4
Important
iMU/EAS
Description 1-9
Description of EAS Indicators 2-25
Description of EAS2 Indicators 2-26
Description of iMU Indicators 2-24
EAS Front Panel Indicators 2-25
EAS2 Front Panel Indicators 2-25
iMU Front Panel Indicators 2-24
integrated Site Controller, See iSC
iSC
Description 1-7
Description of iSC2 Network Status Indicators 2-14
Description of iSC2 Reference Status Indicators 2-15
Description of iSC2 System Status Indicators 2-15
Description of iSC3 Front Panel Indicators 2-16
EBTS Subsystem
ii
SR 16.0
6881012Y79-B
23-Feb-09
Index
Platforms 1-7
GPS Hardware A-2

Span Line, See T1
Sub-Menu Commands
Subrated T1 PCI card
network status controls and indicators 2-14- 2-15
Keystrokes
T1
MMI Commands
Reference information for iSC and BR console port
commands 2-5
Mouse clicks
Multicouplers 1-13
N
New Terms
Note
O
OMC
Alarm & State Change Events (ASCE) Documentation 3-3
Alarm Display and Site Status Display (SSD) 2-12
Alarm Traps 2-30
Base Radio 1-9
Description 2-10
EBTS Traps and Alarms A-4
Events and Alarms 2-11
Interpreting EBTS Site Status Display 2-38
R
R-2660
Description 2-27
Operating modes 2-27
R-2660 iDEN Digital Communications System Analyzer, also
See R-2660
RF
800/900 MHz Antenna Diplexer 1-14
Antenna Duplexer 1-13
Base Radio 1-9
EBTS Combiner 1-13
RX Signal Splitters/multicouplers 1-13
Troubleshooting RF-related Problems 2-40
TX Combiner 1-13
RF Distribution System, also See RFDS
RFDS
800/900 MHz Antenna Diplexer 1-14
Antenna Duplexer 1-13
Description 1-13
RX Signal Splitters/multicouplers 1-13
TX Combiner 1-13
RX Signal Splitters/multicouplers
Description 1-13
ACG control of T1 2-35

Data path between EBTS and Digital Cross-connect Switch
(DCS) 1-7
Data path between EBTS/ACG/iSC and iDEN network 1-8
Data path between EBTS/ACG/iSC and OMC 1-8
iSC interface 2-13
J2300 Protocol Analyzer 2-8
Link impact due to T1 failure 2-32
Physical Link 2-33
Subrated T1 PCI (STP) card 2-14
T1 Span, physical link 2-32
T1 Tester 2-8
Troubleshooting RF-related Problems 2-40
Troubleshooting Scenarios
Issue 3-27
TX Combiner
Description 1-13
U
User Input
W
Warning
S
Screen Output
Site Maintenance 2-6
Site Timing Reference 1-8
SR 16.0
23-Feb-09
EBTS Subsystem
6881012Y79-B
iii
Index
EBTS Subsystem
iv
SR 16.0
6881012Y79-B
23-Feb-09
MOTOROLA and the Stylized M logo are registered in the U.S. Patent and
Trademark Office. All other product or service names are the property of
their respective owners.
Motorola, Inc. 2009
6881012Y79-B

IDEN EBTS Subsystem Troubleshooting Guide

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

IDEN EBTS Subsystem Troubleshooting Guide

Hochgeladen von

Copyright:

Verfügbare Formate

Technical Manual

2009 - Motorola, Inc. All Rights Reserved

SPECIFICATIONS ARE SUBJECT TO CHANGE WITHOUT NOTICE.

About this manual....

Audience Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xii

General Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xix

CMM Labeling and Disclosure Table . . . . . . . . . . . . . . . . . . . -xxi

Recommended Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

EBTS Subsystem Components . . . . . . . . . . . . . . . . . . . . 1-7

EBTS Troubleshooting Resources. . . . . . . . . . . . . . . . . . . . 2-10

R-2660 iDEN Test Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

Drive Test Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29

Alarm Traps to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

ACG Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32

Communication Link Failures. . . . . . . . . . . . . . . . . . . . . . . . 2-33

Recovery from PCCH Base Radio Failures . . . . . . . . . . . . . 2-34

Recovery from ACG Failures . . . . . . . . . . . . . . . . . . . . . . . . 2-35

Base Radio Controller States . . . . . . . . . . . . . . . . . . . . . . . 2-36

Base Radio Controller (BRC) States . . . . . . . . . . . . . . . . . . 2-37

Troubleshooting RF-related Problems . . . . . . . . . . . . . . . . 2-40

GPS Failures that cause EBTS Reset . . . . . . . . . . . . . . . . . . A-3

Traps and Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

Access the iDEN Technical Training Course Catalog ...................................................... 1-5

iDEN System Diagram ...................................................................................... 1-6

Supplemental Publications ................................................................................. xiv

List of Changed Pages

About this manual . . . .

Updated references to SR 16.0.

Purpose and Focus

Updated references to SR 16.0.

General EBTS Troubleshooting Strategies

Updated references to SR 16.0.

Resolving Hardware Issues

Inserted: Audio Problems Related to the

Resolving Statistics Issues

Deleted: EBTS Site Not Reporting ecell

List of Changed Pages

About this manual....

The intended content of the guide

How the guide is to be used

Who is to use the guide

Other reference material that supports information in this guide

Elements in the appearance of the guide and their meaning

General safety guidelines

The changes to the guide over time

Who helped produce and validate information in the guide

Access Controller Gateway (ACG) using the integrated Site Controller

Base Radios (BRs)

RF Distribution System (RFDS)

This manual addresses problems in a single urban.

Identify, verify, and isolate trouble in the EBTS

Obtain and use data relevant to troubleshooting

Employ strategies to diagnose and troubleshoot EBTS problems

Recognize frequent problems in the EBTS

Distinguish when a problem appearing to be an EBTS issue may be related

Restore functionality/operation of the EBTS

Tasks and procedures included should be performed by senior (second level)

Customer Network Resolution Center (CNRC)

Customer Network Resolution Center (CNRC)

The Customer Network Resolution Center (CNRC) is a integral part of the

Procedures for calling the CNRC

Classification of trouble tickets

The escalation processes

The following publications may be required to supplement the information