1X SC4812T CLPA BTS Optimization Manual

SPECIFICATIONS SUBJECT TO CHANGE WITHOUT NOTICE Notice
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. The information in this document has been carefully checked and is believed to be entirely reliable. However, no responsibility is assumed for inaccuracies or omissions. Motorola, Inc. reserves the right to make changes to any products described herein and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license under its patent rights or the rights of others. It is possible that this publication may contain references to, or information about Motorola products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Motorola intends to announce such Motorola products, programming, or services in your country.
Copyrights
This instruction manual, and the Motorola products described in this instruction manual may be, include or describe copyrighted Motorola material, such as computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola and its licensors 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 and its licensors contained herein or in the Motorola products described in this instruction manual may not be copied, reproduced, 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, as arises by operation of law in the sale of a product.
Computer Software Copyrights

The Motorola and 3rd Party supplied Software (SW) products described in this instruction manual may include 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 and other 3rd Party supplied SW certain exclusive rights for copyrighted computer programs, including the exclusive right to copy or reproduce in any form the copyrighted computer program. Accordingly, any copyrighted Motorola or other 3rd Party supplied SW computer programs contained in the Motorola products described in this instruction manual may not be copied (reverse engineered) or reproduced in any manner without the express written permission of Motorola or the 3rd Party SW supplier. 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 SW, except for the normal nonexclusive, royalty free license to use that arises by operation of law in the sale of a product. VENDOR Apache Software Foundation Artesyn CMU * Freeware Tools / Utilities * Performance Technologies Telelogic QNX * * Freeware COPYRIGHT Copyright 20022003 Copyright 20022003 Copyright 20022003 Copyright 20022003 Copyright 20022003 Copyright 20022003 Copyright 20022003
All Rights Reserved All Rights Reserved All Rights Reserved All Rights Reserved All Rights Reserved All Rights Reserved All Rights Reserved
Usage and Disclosure Restrictions

License Agreement
The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express license agreement only and may be used only in accordance with the terms of such an agreement.
Copyrighted Materials
Software and documentation 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 prior written permission of Motorola, Inc.
High Risk Activities
Components, units, or thirdparty products used in the product described herein are NOT faulttolerant and are NOT designed, manufactured, or intended for use as online control equipment in the following hazardous environments requiring failsafe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s) specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.
Trademarks
MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. Copyright 2009 Motorola, Inc. Javat Technology and/or J2MEt: Java and all other Javabased marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. UNIXR: UNIX is a registered trademark of The Open Group in the United States and other countries. 3ComR and OfficeConnectR: 3Com and OfficeConnect are registered trademarks of the 3Com Corporation. MicrosoftR, WindowsR. and Windows MeR: Microsoft, Windows, and Windows Me are registered trademarks of Microsoft Corporation; Windows XPt is a trademark of Microsoft Corporation. CiscoR, Cisco IOSR, and IOSR: Cisco, Cisco IOS, and IOS are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries. PC Cardt: PC Card is a trademark of the Personal Computer Memory Card International Association (PCMCIA) Anritsut is a trademeark of the Anritsu Company. REV052604
Table of Contents 1X SC4812T CLPA BTS Optimization/ATP

Software Release 2.22.0.X
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contacting Motorola . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Advice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings, cautions, and notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Caring for the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CMM labeling and disclosure table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola document set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Third Party computer software and trademarks . . . . . . . . . . . . . . . . . . . . . . . . .
FCC Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi x xvii xviii xix xviii xx xxi xxii xxii xxii xxii xxiii xxiv xxv xxvi xxvi xxvii xxvii
xxviii
Chapter 1: Introduction
Scope, Assumptions, and Audience ................................. 1-1 1-3 1-4 1-5 1-8 1-9 1-15
i
Content Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . When to Perform BTS RF Calibration and Acceptance Testing . . . . . . . . . . . . General Test Equipment Selection, Calibration, and Operation Requirememnts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Test Equipment and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Documents and Related Publications . . . . . . . . . . . . . . . . . . . . . . . . .
SEP 2009 1X SC4812T CLPA BTS Optimization/ATP
Table of Contents continued

Terms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Equipment Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sector Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17 1-21 1-31
Chapter 2: Preliminary Operation

Preliminary Operations: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Equipage Verification and Card/Module Installation . . . . . . . . . . . . . . . . . Frame Identification Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PrePowerup Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial Powerup Tests and Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 2-2 2-4 2-5 2-9
Chapter 3: Optimization/Calibration
Introduction to Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare the LMF Computer for MMI Communication . . . . . . . . . . . . . . . . . . . LMF to BTS Connection Service Shelf Connection . . . . . . . . . . . . . . . . . . . . LMF to BTS Connection I/O Panel Connection . . . . . . . . . . . . . . . . . . . . . . . Using the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Establishing an MMI Communication Session . . . . . . . . . . . . . . . . . . . . . . . . . LMF Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pinging the Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Take Control of Packet BTS Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download the BTS General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download BTS Loading Packet GLI Devices . . . . . . . . . . . . . . . . . . . . . . . . . Download BTS Loading NonGLI Devices . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Other Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSM System Time GPS, LFR, and HSO/MSO Verification . . . . . . . . . . . . . Test Equipment Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Connection to the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Set Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting and Editing Generator Calibration Data . . . . . . . . . . . . . . . . . . . . . . . . . Cable Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay Level Offset Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX BLO Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download BLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Calibration Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create CAL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii 1X SC4812T CLPA BTS Optimization/ATP
3-1 3-4 3-11 3-14 3-16 3-18 3-31 3-33 3-34 3-36 3-38 3-40 3-43 3-46 3-50 3-63 3-82 3-85 3-92 3-98 3-100 3-112 3-120 3-123 3-124 3-125
SEP 2009

Cellular Remote Monitoring System (CRMS) Probe Setup and Calibration . . BTS Redundancy/Alarm Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarms Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-126 3-127 3-136
Chapter 4: Automated Acceptance Test Procedure

Acceptance Test Procedures Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automated Acceptance Test Procedures TX & RX . . . . . . . . . . . . . . . . . . . . . Individual Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Spectral Purity Transmit Mask Acceptance Test . . . . . . . . . . . . . . . . . . . . . TX Waveform Quality (rho) Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . . TX Pilot Time Offset Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Code Domain Power/Noise Floor Acceptance Test . . . . . . . . . . . . . . . . . . . RX Frame Error Rate (FER) Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . . Receive Signal Strength Indication (RSSI) Acceptance Test . . . . . . . . . . . . . . . Generate an ATP Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 4-3 4-8 4-10 4-12 4-13 4-14 4-16 4-17 4-19
Chapter 5: Configuring Packet BTS Transport

Introduction to Packet BTS Transport Configuration . . . . . . . . . . . . . . . . . . . . . GLI3 Required Software Release, Operating Mode, and Loading Code . . . . . . GLI3 Card Software Version and Backhaul Mode . . . . . . . . . . . . . . . . . . . . . . . Preloading GLI3 Cards in Packet Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure GLI3 Cards for IBR Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure GLI3 Cards for Operation with External BTS Routers . . . . . . . . . . . Configure GLI3 Cards for OTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring BTS File Transfer Protocol Introduction . . . . . . . . . . . . . . . . . . Configuring BTS File Transfer Protocol New BTS Installation . . . . . . . . . . . GLI3 Software Release and Backhaul Mode Worksheet . . . . . . . . . . . . . . . . . . OTI configuration settings worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Interface Card (NIC) configuration worksheet . . . . . . . . . . . . . . . . . . 5-1 5-3 5-5 5-10 5-12 5-27 5-33 5-44 5-46 5-48 5-49 5-51
Chapter 6: Prepare to Leave the Site

Updating Calibration Data Files Packet BTS . . . . . . . . . . . . . . . . . . . . . . . . . Prepare to Leave the Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 6-5
Chapter 7: Basic Troubleshooting

Basic Troubleshooting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-1 7-2 7-5 7-8

iii

Troubleshooting: Transmit ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: Receive ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: CSM Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: CCCP Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: Span Control Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: GLI3 card continually reboots after converting to satellite backhaul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Module Front Panel LED Indicators and Connectors . . . . . . . . . . . . . . . . . . . . . 7-10 7-14 7-15 7-17 7-24 7-33 7-40
Appendix A: Data Sheets

Optimization (PreATP) Data Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Serial Number Check List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 A-17
Appendix B: PN Offset/I & Q Offset Register Programming Information

PN Offset Programming Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Appendix C: FRU Optimization/ATP Test Matrix

FRU Optimization/ATP Test Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Appendix D: BBX Gain Set Point vs BTS Output

BBX Gain Set Point vs. BTS Output Considerations . . . . . . . . . . . . . . . . . . . . D-1
Appendix E: CDMA Operating Frequency

CDMA Operating Frequency Programming Information . . . . . . . . . . . . . . . . . 1900 MHz PCS Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800 MHz CDMA Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1 E-2 E-5
Appendix F: Test Equipment Preparation

Test Equipment Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Setup: Agilent E7495 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying and Setting GPIB Addresses: Advantest R3267 Spectrum Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying and Setting GPIB Addresses: Advantest R3465 Communications Test Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying and Setting GPIB Addresses: Advantest R3562 Signal Generator . . Verifying and Setting GPIB Addresses: Agilent 8935 Series E6380 Test Set . . Verifying and Setting GPIB Addresses: Agilent E4406A Transmitter Tester . . Verifying and Setting GPIB Addresses: Agilent E4418 Power Meter . . . . . . . . Verifying and Setting GPIB Addresses: Agilent E4438C Signal Generator . . . Verifying and Setting GPIB Addresses: Gigatronics 8541C Power Meter . . . . Verifying and Setting GPIB Addresses: RS232 GPIB Interface Box . . . . . . . .
iv 1X SC4812T CLPA BTS Optimization/ATP
F-1 F-2 F-5 F-7 F-8 F-9 F-11 F-13 F-15 F-17 F-18
SEP 2009

Test Equipment Interconnection: Advantest R3267 and R3562 . . . . . . . . . . . . . Test Equipment Interconnection: Agilent 8935 Series E6380 and E4438C . . . Test Equipment Interconnection: Agilent E4406A and E4438C . . . . . . . . . . . . Test Equipment Calibration: Agilent E4406A Selfalignment . . . . . . . . . . . . . Test Equipment Calibration: Gigatronics 8542 Power Meter . . . . . . . . . . . . . . . Cable Calibration with R3465 Test Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-19 F-20 F-21 F-22 F-23 F-24
Appendix G: VSWR
Transmit & Receive Antenna VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1
Appendix H: Download ROM Code

Download ROM Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-1
Appendix I: InService Calibration

In Service Calibration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Delta Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . InService Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1 I-2 I-10
Appendix J: Packet Backhaul Configuration

BTS Router Configuration Operations Introduction . . . . . . . . . . . . . . . . . . . . Terminal Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Establishing a BTS Router Communication Session . . . . . . . . . . . . . . . . . . . . . Obtain BTS Router Minimum (Canned) Configuration Files from the OMCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Router IOS Version Verification and Canned Configuration File Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change or Upgrade BTS Router IOS Version . . . . . . . . . . . . . . . . . . . . . . . . . . Verify and Upgrade ROMmon Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovery from BTS Router Boot to ROMmon . . . . . . . . . . . . . . . . . . . . . . . . . Entering or Changing BTS Router FE Interface IP Addresses . . . . . . . . . . . . . . Example BTS Router Canned Configuration Files . . . . . . . . . . . . . . . . . . . . . . Network Interface Card (NIC) Configuration Worksheet . . . . . . . . . . . . . . . . . . External BTS Router Compact Flash (CF) Memory Card Installation and Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-1 J-2 J-5 J-8 J-15 J-35 J-47 J-57 J-72 J-77 J-84 J-85
Appendix K: MMI Cable Fabrication

MMI Cable Fabrication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . K-1
Appendix L: OTI Configuration Support Operations

OTI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Computer Network Interface Card (NIC) for OTI Verification . . . . . OTI Link Confidence Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L-1 L-2 L-5
Index
SEP 2009 1X SC4812T CLPA BTS Optimization/ATP v
List of Figures 1X SC4812T CLPA BTS Optimization/ATP

Figure 1-1: Null Modem Cable Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 1-2: Starter Frame (48 V configuration) . . . . . . . . . . . . . . . . . . . . . . . . Figure 1-3: Starter Frame (+27 V configuration) . . . . . . . . . . . . . . . . . . . . . . . . Figure 1-4: Starter Frame I/O (Interconnect) Panel . . . . . . . . . . . . . . . . . . . . . . Figure 1-5: Expansion Frame I/O (Interconnect) Panel . . . . . . . . . . . . . . . . . . . Figure 1-6: CCCP Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 1-7: Power Amplifier (PA) Configurations . . . . . . . . . . . . . . . . . . . . . . . Figure 2-1: SC4812Tseries BTS Switch Card DIP Switch Settings . . . . . . . . Figure 2-2: SC4812Tseries BTS Backplane DIP Switch Settings for BTS or Logical BTS Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-3: Breaker Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-1: LMF Folder Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-2: Service Shelf LAN Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-3: I/O Panel LAN Connection (SC4812TMC BTS shown; typical for other indoor BTS models) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-4: BTS Login screen identifying circuit and packet BTS files . . . . . Figure 3-5: SelfManaged Network Elements (NEs) state of a packet mode BTS (SC4812T shown) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-6: Available packet mode commands . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-7: Packet mode BTS with MCC2 and BBX2 under LMF control . Figure 3-8: CDMA LMF Computer Common MMI Connections Cable CGDSMMICABLE219112 or Fabricated MMI Cable . . . . . . . . . . . . . . Figure 3-9: CDMA LMF Computer Common MMI Connections Motorola MMI Interface Kit, SLN2006A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-10: BTS LAN Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-11: CSM Front Panel PWR/ALM LED Indicator . . . . . . . . . . . . . . . . Figure 3-12: CSM MMI Terminal Connection . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-13: TX Calibration Test Setup Agilent 8935 (IS95A/B & CDMA2000 1X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-14: TX Calibration Test Setup Agilent E4406A and Advantest R3567 (IS95A/B and CDMA2000 1X) . . . . . . . . . . . . . . . . . . . . . . Figure 3-15: TX Calibration Test Setup Agilent E7495A (IS95A/B & CDMA2000 1X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi 1X SC4812T CLPA BTS Optimization/ATP
1-10 1-23 1-24 1-26 1-27 1-28 1-30 2-3 2-4 2-8 3-5 3-14 3-16 3-20 3-21 3-22 3-23 3-32 3-32 3-34 3-51 3-55 3-70 3-71 3-72
SEP 2009
List of Figures continued

Figure 3-16: TX Calibration Test Setup Anritsu MT8212B (IS95A/B and CDMA2000 1X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-17: ATP Test Setup IS95A/B (Agilent 8935) . . . . . . . . . . . . . . . . . Figure 3-18: ATP Test Setup IS95A/B and CDMA2000 1X (Agilent E4438C/8935 and Agilent E4438C/E4406A) . . . . . . . . . . . . . . . . . . . Figure 3-19: ATP Test Setup IS95A/B and CDMA2000 1X (Advantest R3267/3562) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-20: ATP Test Setup IS95A/B and CDMA2000 1X (Agilent E7495A or E7495B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-21: ATP Test Setup IS95A/B and CDMA2000 1X (Anritsu MT8212B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-22: Alternate ATP Test Setups (Except Agilent E7495A/B and Anritsu MT8121B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-23: Alternate ATP Test Setups (Agilent E7495A or E7495B) . . . . . . . Figure 3-24: Alternate ATP Test Setups (Anritsu MT8212B) . . . . . . . . . . . . . . Figure 3-25: IS95A/B Cable Calibration Test Setup Agilent 8935 . . . . . . . . Figure 3-26: IS95A/B and CDMA 2000 1X Cable Calibration Test Setup Agilent E4406A/E4432B and Advantest R3267/R3562 . . . . . . . . . . . . . . . . . . Figure 3-27: CDMA2000 1X Cable Calibration Test Setup Agilent E7495A or E7495B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-28: IS95A/B and CDMA 2000 1X Cable Calibration Test Setup Anritsu MT8212B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-29: Calibrating Test Equipment Setup for TX BLO and TX ATP Tests (using Signal Generator and Spectrum Analyzer) . . . . . . . . . . . . . . . . . . . Figure 3-30: Calibrating Test Equipment Setup for RX ATP Test (using Signal Generator and Spectrum Analyzer) . . . . . . . . . . . . . . . . . . . . . . . Figure 3-31: CCCP Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-32: Fan Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-33: Alarm Connector Location and Connector Pin Numbering . . . . . Figure 3-34: AMR Connector Pin Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-1: TX Mask Verification Spectrum Analyzer Display . . . . . . . . . . . . . Figure 4-2: Code Domain Power and Noise Floor Levels . . . . . . . . . . . . . . . . . Figure 5-1: OTI Interconnection for SC4812Tseries Starter Frame . . . . . . . . . Figure 5-2: OTI Interconnection for SC4812Tseries Starter Frame with One Expansion Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6-1: Automated Calibration File Transfer Process User and LMF Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6-2: Automated Calibration File Transfer Process GLI3 and LMF Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6-3: GLI3 Card MMI Connection Detail . . . . . . . . . . . . . . . . . . . . . . . . Figure 6-4: GLI3 Card MMI Connection Detail Fabricated MMI Cable . . . . Figure 6-5: Indoor BTS Site and Span I/O Boards Span and Modem Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-73 3-74 3-75 3-76 3-77 3-78 3-79 3-80 3-81 3-103 3-104 3-105 3-106 3-108 3-109 3-129 3-131 3-137 3-138 4-11 4-15 5-42 5-43 6-2 6-3 6-7 6-8 6-11
vii

Figure 7-1: GLI3 Card MMI Connection Detail . . . . . . . . . . . . . . . . . . . . . . . . Figure 7-2: CSM Front Panel Indicator and Monitor Connectors . . . . . . . . . . . Figure 7-3: MCC Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure E-1: North America PCS Frequency Spectrum (CDMA Allocation) . . . Figure E-2: North American Cellular Telephone System Frequency Spectrum (CDMA Allocation). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-1: Agilent E7495 PrePower Sensor Calibration connection . . . . . . . Figure F-2: Agilent E7495 Power Sensor Calibration connection . . . . . . . . . . . Figure F-3: Setting Advantest R3267 GPIB Address . . . . . . . . . . . . . . . . . . . . . Figure F-4: R3465 Communications Test Set . . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-5: Advantest R3562 GPIB Address Switch Setting . . . . . . . . . . . . . . Figure F-6: Agilent 8935 Series E6380 Test Set Verify and Set/Change GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-7: Agilent E4406A Transmitter Tester Verify and Set/Change GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-8: Agilent E4418B Power Meter Verify and Set/Change GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-9: Agilent E4438C Verify and Set/Change GPIB Address . . . . . . . . . Figure F-10: Gigatronics 8541C Power Meter Detail . . . . . . . . . . . . . . . . . . . . Figure F-11: Verify and Set/Change RS232 GPIB Interface Box GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-12: Advantest 10 MHz Reference and Serial I/O Connections . . . . . . Figure F-13: Agilent 8935/E4438C 10MHz Reference and Even Second Tick Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-14: Agilent 10 MHz Reference Connections . . . . . . . . . . . . . . . . . . . . Figure F-15: Agilent E4406A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-16: Gigatronics 8541C Power Meter . . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-17: Cable Calibration using Advantest R3465 . . . . . . . . . . . . . . . . . . Figure G-1: Manual VSWR Test Setup Using Advantest R3465 . . . . . . . . . . . Figure I-1: Delta Calibration Setup R3561L to HP437B . . . . . . . . . . . . . . . . Figure I-2: Delta Calibration Setup R3561L to R3465 . . . . . . . . . . . . . . . . . . Figure I-3: Delta Calibration Setup HP8935 to HP437B . . . . . . . . . . . . . . . . Figure I-4: Delta Calibration Setup HP8935 to HP8935 . . . . . . . . . . . . . . . . . Figure I-5: Delta Calibration Setup Agilent E4432B to HP437 . . . . . . . . . . . Figure I-6: Delta Calibration Setup Agilent E4432B to Agilent E4406A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure I-7: Optimization/ATP Test Setup Using RFDS . . . . . . . . . . . . . . . . . . . Figure I-8: IS95 A/B/C Optimization/ATP Test Setup Using RFDS . . . . . . . . Figure J-1: Wiring Diagram, BTS Router Communication Rollover Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii 1X SC4812T CLPA BTS Optimization/ATP
7-26 7-41 7-46 E-2 E-5 F-3 F-4 F-5 F-7 F-8 F-9 F-11 F-13 F-15 F-17 F-18 F-19 F-20 F-21 F-22 F-23 F-27 G-3 I-4 I-4 I-6 I-6 I-9 I-9 I-11 I-12 J-5
SEP 2009

Figure J-2: Wiring Diagram, DB9 Plugto8contact Modular Plug Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure J-3: LMF Computer Connections to BTS Router . . . . . . . . . . . . . . . . . Figure J-4: LMF Computer TFTP Connections to BTS Router . . . . . . . . . . . . . Figure J-5: Router CF Memory Card Removal . . . . . . . . . . . . . . . . . . . . . . . . . Figure K-1: Fabricated MMI Cable Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure L-1: OTI Base Station Functional Block Diagram . . . . . . . . . . . . . . . . .
J-6 J-7 J-22 J-85 K-1 L-1
SEP 2009
1X SC4812T CLPA BTS Optimization/ATP
ix
List of Tables 1X SC4812T CLPA BTS Optimization/ATP

FCC Part 68 Registered Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 1-1: CDMA LMF Test Equipment Support Table . . . . . . . . . . . . . . . . . . Table 1-2: Abbreviations and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 1-3: CCCP Shelf/Cage Card/Module Device ID Numbers (Top Shelf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 1-4: CCCP Shelf/Cage Card/Module Device ID Numbers (Bottom Shelf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 1-5: BTS Sector Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 1-6: Power Amplifier and Trunking Backplane Compatibility . . . . . . . . Table 1-7: Sector Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-1: Initial Installation of Cards/Modules . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-2: DC Power Pretest (BTS Frame) . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-3: DC Input Power Cable Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-4: Common Power Supply Verification . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-5: Initial Powerup (BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-1: LMF Application Program Installation . . . . . . . . . . . . . . . . . . . . . . . Table 3-2: Copying NEC Files to the LMF Computer . . . . . . . . . . . . . . . . . . . . Table 3-3: Establish HyperTerminal Connection . . . . . . . . . . . . . . . . . . . . . . . . Table 3-4: Connecting the LMF to the BTS, Service Shelf Connection . . . . . . Table 3-5: Connecting the LMF to the BTS, I/O Panel LAN Connection . . . . . Table 3-6: BTS GUI Login Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-7: BTS CLI Login Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-8: BTS GUI Logout Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-9: BTS CLI Logout Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-10: Establishing MMI Communication . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-11: Pinging the Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-12: Take Control of Packet BTS Resources with the LMF . . . . . . . . . . Table 3-13: Loading Code into Packet GLI3 Card with the LMF . . . . . . . . . . . Table 3-14: Download RAM Code and Data or Data Only to NonGLI Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x 1X SC4812T CLPA BTS Optimization/ATP
xxix 1-11 1-17 1-22 1-22 1-31 1-31 1-32 2-2 2-6 2-9 2-10 2-11 3-8 3-9 3-12 3-14 3-17 3-26 3-28 3-29 3-30 3-31 3-35 3-37 3-40 3-44
SEP 2009
List of Tables continued

Table 3-15: Select CSM Clock Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-16: Enable CSMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-17: Enable MCCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-18: CSM PWR/ALM LED Indications . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-19: Test Equipment Setup for GPS and LFR/HSO/MSO/QHSO Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-20: GPS and HSO/MSO/QHSO Initialization/Verification . . . . . . . . . . Table 3-21: Loran Initialization/Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-22: IS95A/Bonly Test Equipment Interconnection . . . . . . . . . . . . . . Table 3-23: CDMA2000 1X/IS95A/B Test Equipment Interconnection . . . . . Table 3-24: Additional CDMA2000 1X/IS95A/B Test Equipment Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-25: Selecting a COM Port for GPIB or Serial Test Equipment Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-26: Disconnect and Reconnect the LMF and the Active COM Port . . . Table 3-27: Manually Selecting Test Equipment GPIB Interface . . . . . . . . . . Table 3-28: Autodetecting Test Equipment GPIB Interface . . . . . . . . . . . . . . Table 3-29: Manually Selecting Test Equipment Serial Interface . . . . . . . . . . Table 3-30: Autodetecting Test Equipment Serial Interface . . . . . . . . . . . . . . Table 3-31: Manually Selecting Test Equipment Network Interface . . . . . . . . Table 3-32: Autodetecting Test Equipment Network Interface . . . . . . . . . . . . Table 3-33: Calibrate Test Equipment Power Measurement Zeroing . . . . . . . Table 3-34: Anritsu MT8212B Multifunction Test Set Zero Out Power Meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-35: Anritsu MT8212B Multifunction Test Set TX Analyzer Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-36: Anritsu MT8212B Multifunction Test Set CW Generator Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-37: Set or Edit Generator Calibration Data . . . . . . . . . . . . . . . . . . . . . . Table 3-38: Cable Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-39: Calibrating TX and Duplexed RX Cables Using Signal Generator and Spectrum Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-40: Calibrating RX Cables Using a Signal Generator and Spectrum Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-41: Setting Cable Loss Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-42: Setting Coupler Loss Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-43: BLO BTS.cal File Array Assignments . . . . . . . . . . . . . . . . . . . . . . Table 3-44: BTS.cal File Array (Per Sector) . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-45: Test Equipment Setup (RF Path Calibration) . . . . . . . . . . . . . . . . . Table 3-46: All Cal/Audit and TX Calibration Procedure . . . . . . . . . . . . . . . . .
3-46 3-47 3-49 3-52 3-54 3-56 3-61 3-66 3-67 3-68 3-82 3-83 3-86 3-87 3-88 3-89 3-90 3-90 3-94 3-95 3-96 3-97 3-98 3-101 3-107 3-108 3-110 3-111 3-115 3-115 3-117 3-121
xi
List of Tables
continued
Table 3-47: Download BLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-48: Create CAL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-49: Test Equipment Setup for Redundancy/Alarm Tests . . . . . . . . . . . . Table 3-50: Power Supply/Converter Redundancy (BTS Frame) . . . . . . . . . . . Table 3-51: Miscellaneous Alarm Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-52: BBX Redundancy Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-53: CSM, GPS, & HSO, Redundancy/Alarm Tests . . . . . . . . . . . . . . . Table 3-54: Power Amplifier Redundancy Test . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-55: GLI Redundancy Test (with MM Connection Established) . . . . . . Table 3-56: CDI Alarm Input Verification Using the Alarms Test Box . . . . . . . Table 3-57: CDI Alarm Input Verification Without the Alarms Test Box . . . . . Table 4-1: ATP Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4-2: Reload Affected MCC(s) with Data After Redundant BBX TX Testing with Standard Test Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4-3: Test RSSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4-4: Generating an ATP Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-1: Packet BTS Transport Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-2: GLI3 Packet Backhaul Mode and Software Release Required . . . . . Table 5-3: GLI3 Code Loading Methods Based on Operating Mode . . . . . . . . Table 5-4: GLI3 Backhaul Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-5: Determine GLI3 Card Software Version and Backhaul Mode . . . . . Table 5-6: Does GLI3 Card Need Configuration Change? . . . . . . . . . . . . . . . . . Table 5-7: Preload GLI3 Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-8: Item Required for BTS Redundant GLI Cabling Integrated BTS Router Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-9: IBR Configuration Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-10: IBR Conversion BTS Provisioned with Full Span(s) . . . . . . . . . Table 5-11: IBR Conversion BTS Provisioned with Fractional Span . . . . . . . Table 5-12: Prevent GLI3 Configuration Fallback . . . . . . . . . . . . . . . . . . . . . . . Table 5-13: Items Required for FE Cabling External BTS Router Group . . . Table 5-14: EBR Conversion Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-15: Convert GLI3 Cards to EBR Operation . . . . . . . . . . . . . . . . . . . . . Table 5-16: Preparation for BTS OTI Implementation . . . . . . . . . . . . . . . . . . . . Table 5-17: Site Arrival and Initial Preparation . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-18: Convert GLI3 Card to OTI Operation . . . . . . . . . . . . . . . . . . . . . . . Table 5-19: LMF File Transfer Protocol Selections . . . . . . . . . . . . . . . . . . . . . . Table 5-20: Determine Operating File Transfer Protocol Using the LMF . . . . .
xii 1X SC4812T CLPA BTS Optimization/ATP
3-123 3-125 3-128 3-128 3-130 3-131 3-132 3-134 3-135 3-139 3-141 4-6 4-7 4-18 4-19 5-2 5-3 5-3 5-4 5-5 5-8 5-10 5-12 5-13 5-15 5-20 5-26 5-27 5-28 5-30 5-35 5-36 5-37 5-44 5-46
SEP 2009

Table 5-21: Change Operating File Transfer Protocol Using the LMF . . . . . . . Table 5-22: Software Release and Backhaul Mode Record . . . . . . . . . . . . . . . . Table 5-23: OTI Configuration Settings and Values . . . . . . . . . . . . . . . . . . . . . . Table 5-24: Advanced Tab Property List Box Connection Settings Original . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-25: Advanced Tab Property List Box Connection Settings for OTI . Table 6-1: Uploading Calibration File to a Packet BTS . . . . . . . . . . . . . . . . . . . Table 6-2: External Test Equipment Removal . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-3: IBR Span Parameter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-4: Bring Modules into Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-5: LMF Termination and Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-6: BTS Span and Modem Connections . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-7: Reset BTS Devices and Remote Site Initialization . . . . . . . . . . . . . . Table 7-1: Login Failure Troubleshooting Procedures . . . . . . . . . . . . . . . . . . . . Table 7-2: Turn Off Video Card Acceleration . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-3: Troubleshooting a Power Meter Communication Failure . . . . . . . . . Table 7-4: Troubleshooting a Communications Analyzer Communication Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-5: Troubleshooting Code Download Failure . . . . . . . . . . . . . . . . . . . . . Table 7-6: Troubleshooting Data Download Failure . . . . . . . . . . . . . . . . . . . . . Table 7-7: Troubleshooting Device Enable (INS) Failure . . . . . . . . . . . . . . . . . Table 7-8: Miscellaneous Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-9: Troubleshooting BLO Calibration Failure . . . . . . . . . . . . . . . . . . . . Table 7-10: Troubleshooting Calibration Audit Failure . . . . . . . . . . . . . . . . . . . Table 7-11: Correcting E7495A/B Test Set Communication Failure . . . . . . . . . Table 7-12: Troubleshooting Forward Link Failure (BTS Passed Reduced ATP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-13: Troubleshooting TX Mask Measurement Failure . . . . . . . . . . . . . . Table 7-14: Troubleshooting Rho and Pilot Time Offset Measurement Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-15: Troubleshooting Code Domain Power and Noise Floor Measurement Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-16: Troubleshooting Carrier Measurement Failure . . . . . . . . . . . . . . . . Table 7-17: CD Power/Noise Floor Test Failure Workaround for Agilent E7495A/B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-18: Troubleshooting Multi-FER Failure . . . . . . . . . . . . . . . . . . . . . . . . Table 7-19: No GLI Control via LMF (all GLIs) . . . . . . . . . . . . . . . . . . . . . . . . Table 7-20: No GLI Control through Span Line Connection (Both GLIs) . . . . Table 7-21: MGLI Control Good No Control over Colocated GLI . . . . . . .
5-47 5-48 5-49 5-51 5-51 6-4 6-5 6-5 6-9 6-10 6-10 6-11 7-2 7-2 7-3 7-4 7-5 7-6 7-6 7-7 7-8 7-9 7-10 7-10 7-11 7-11 7-12 7-12 7-13 7-14 7-19 7-20 7-20
xiii
List of Tables
continued
Table 7-22: MGLI Control Good No Control over AMR . . . . . . . . . . . . . . . . Table 7-23: No BBX Control in the Shelf No Control over Colocated GLIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-24: MGLI Control Good No (or Missing) Span Line Traffic . . . . . . . Table 7-25: No MCC Channel Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-26: No DC Input Voltage to Power Supply Module . . . . . . . . . . . . . . . Table 7-27: No DC Input Voltage to any CCCP Shelf Module . . . . . . . . . . . . Table 7-28: TX and RX Signal Routing Problems . . . . . . . . . . . . . . . . . . . . . . . Table 7-29: Troubleshoot Control Link Failure . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-30: Set BTS Span Parameter Configuration . . . . . . . . . . . . . . . . . . . . . Table 7-31: Setting GLI3 Backhaul Type to Satellite and Correct Timeout Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-32: GLI3 Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table A-1: Verification of Test Equipment Used . . . . . . . . . . . . . . . . . . . . . . . . Table A-2: Site Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table A-3: Preliminary Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table A-4: Prepower Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table A-5: Prepower Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table A-6: GPS Receiver Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table A-7: LPA IM Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table A-8: LPA Convergence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-20 7-21 7-21 7-21 7-22 7-23 7-23 7-24 7-27 7-34 7-44 A-1 A-2 A-2 A-3 A-4 A-5 A-6 A-7
Table A-9: TX BLO Calibration (3Sector: 1; 2; and 4Carrier Nonadjacent Channels) A-8 Table A-10: TX Bay Level Offset Calibration (3Sector: 2Carrier Adjacent Channels) . A-10 Table A-11: TX Bay Level Offset Calibration (3Sector: 3 or 4Carrier Adjacent Channels) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table A-12: TX BLO Calibration (6Sector: 1Carrier, 2Carrier Nonadjacent Channels) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table A-13: BTS Redundancy/Alarm Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table A-14: TX Antenna VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table A-15: RX Antenna VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table A-16: AMR CDI Alarm Input Verification . . . . . . . . . . . . . . . . . . . . . . . . Table B-1: PnMask I and PnMask Q Values for PilotPn . . . . . . . . . . . . . . . . . . Table C-1: When RF Optimization Is required on the BTS . . . . . . . . . . . . . . . . Table C-2: When to Optimize Interframe Cabling . . . . . . . . . . . . . . . . . . . . . . Table C-3: SC 4812T CLPA BTS Optimization and ATP Test Matrix . . . . . . . Table D-1: BBX Gain Set Point vs. Actual BTS Output (in dBm) . . . . . . . . . . Table E-1: 1900 MHz TX and RX Frequency vs. Channel . . . . . . . . . . . . . . . .
xiv 1X SC4812T CLPA BTS Optimization/ATP
A-11 A-13 A-15 A-15 A-16 A-16 B-2 C-1 C-2 C-4 D-1 E-3
SEP 2009

Table E-2: 800 MHz TX and RX Frequency vs. Channel . . . . . . . . . . . . . . . . . Table F-1: Set IP Address on Agilent E7495 test set . . . . . . . . . . . . . . . . . . . . . Table F-2: E7495 Power Sensor Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . Table F-3: Verify and Set/Change Advantest R3267 GPIB Address . . . . . . . . . E-6 F-2 F-3 F-5
Table F-4: Verify and Set/Change Advantest R3465 Communications Test Set GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-7 Table F-5: Verify and Set/Change Agilent 8935 Series E6380 Test Set GPIB Address . . F-9 Table F-6: Verify and Set/Change Agilent E4406A Transmitter Tester GPIB Address . . . F-11 Table F-7: Verify and Set/Change Agilent E4418 Power Meter GPIB Address Table F-8: Verify and Change Agilent E4438C Signal Generator GPIB Address Table F-9: Verify and Set/Change Gigatronics 8541C Power Meter GPIB Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table F-10: Agilent E4406A Selfalignment (Calibration) . . . . . . . . . . . . . . . . Table F-11: Calibrate Gigatronics 8542 Power Meter . . . . . . . . . . . . . . . . . . . . Table F-12: Procedure for Calibrating Test Cable Setup Using Advantest R3465 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table G-1: VSWR Measurement Procedure Advantest R3465 Test Set . . . . . Table H-1: Download ROM Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table I-1: Advantest Power Delta Calibration Procedure . . . . . . . . . . . . . . . . . . Table I-2: HP8935 Power Delta Calibration Procedure . . . . . . . . . . . . . . . . . . . Table I-3: Agilent E4406A Power Delta Calibration Procedure . . . . . . . . . . . . Table I-4: InService Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table J-1: Establish HyperTerminal Connection . . . . . . . . . . . . . . . . . . . . . . . . Table J-2: Establishing BTS Router Serial Communication . . . . . . . . . . . . . . . Table J-3: BTS Router Canned Configuration File FTP Transfer from the OMCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table J-4: Configure Computer NIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table J-5: Create a Default TFTP Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table J-6: Connecting the LMF Computer to the BTS Router for TFTP File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table J-7: BTS Router Powerup and Initial Ethernet Configuration . . . . . . . . Table J-8: Transfer Canned Configuration Files to the BTS Router Using a TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table J-9: Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position . . . . . . . . . . . . . . . . Table J-10: Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table J-11: Simple Recovery from BTS Router ROMmon Boot . . . . . . . . . . . . Table J-12: Extended Recovery from BTS Router ROMmon Boot . . . . . . . . . .
F-13 F-15 F-17 F-22 F-23 F-24 G-2 H-1 I-2 I-5 I-7 I-13 J-3 J-6 J-9 J-19 J-21 J-23 J-23 J-27 J-37 J-49 J-58 J-67
xv
List of Tables
continued
Table J-13: Entering or Changing BTS Router FE Interface IP Addresses and Operating Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table J-14: Advanced Tab Property List Box Connection Settings Original . Table J-15: Advanced Tab Property List Box Connection Settings for BTS Router Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table J-16: External BTS Router Flash Memory Card Removal . . . . . . . . . . . . Table J-17: External BTS Router Flash Memory Card Installation . . . . . . . . . . Table K-1: Parts Required to Fabricate MMI Cable . . . . . . . . . . . . . . . . . . . . . . Table K-2: Fabricated MMI Cable Wire Run List . . . . . . . . . . . . . . . . . . . . . . . Table L-1: Configure Computer NIC for OTI Verification . . . . . . . . . . . . . . . . Table L-2: OTI Link Confidence Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
J-72 J-84 J-84 J-86 J-87 K-1 K-2 L-2 L-5
xvi
SEP 2009
Revision History
Version Information The following table lists the manual version, date of version, and remarks on the version. Issue A Manual Number The following Service Requests are resolved in this document. Service Request NA CMBP Number NA Initial release Remarks Date of Issue SEP 2009 Remarks Release for General Availability (GA).
Cellular Manual Revision Information The following Change Notices (CN) are incorporated in this document. CN Date NA CN NA NA Title
SEP 2009
xvii
General information
Scope of manual This manual is intended for use by cellular telephone system craftspersons in the day-to-day operation of Motorola cellular system equipment and ancillary devices. This manual is not intended to replace the system and equipment training offered by Motorola, although it can be used to supplement or enhance the knowledge gained through such training. NOTE If this document was obtained when attending a Motorola training course, it will not be updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied under normal operational circumstances, to support a major software release, then corrections are supplied automatically by Motorola and posted on the Motorola customer website.
Cross references
The following special paragraphs are used in this manual to point out information that must be read. This information may be set-off from the surrounding text, but is always preceded by a bold title in capital letters. The four categories of these special paragraphs are:
xviii
SEP 2009
General Information continued

Text conventions
The following conventions are used in the Motorola cellular infrastructure documents to represent keyboard input text, screen output text and special key sequences. Input CMMD required required [optional] [optional] Output CMMD required required [optional] [optional] Special key sequences CRTLc or CTRL+C CTRLSHIFTc or CTRL+SHIFT+C ALTf or ALT+F ALT+SHIFT+F11 | RETURN or ENTER Press the Ctrl and C keys at the same time. Press the Ctrl, Shift, and C keys at the same time. Press the Alt and F keys at the same time. Press the Alt, Shift, and F11 keys at the same time. Press the pipe symbol key. Press the Return or Enter key.
SEP 2009
xix
Contacting Motorola
Motorola appreciates feedback from the users of our information. 24-hour support service If you have problems regarding the operation of your equipment, please contact the Customer Network Resolution Center (CNRC) for immediate assistance. The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center contact information, from the menu located to the left of the Login box. For additional CNRC contact information, contact your Motorola account representative. Contact us Send questions and comments regarding user documentation to the email address below: cdma.documentation@motorola.com Reporting manual errors To report a documentation error, call the CNRC (Customer Network Resolution Center) and provide the following information to enable CNRC to open an SR (Service Request): the document type the manual title, part number, and revision character the page number(s) with the error a detailed description of the error and if possible the proposed solution Motorola appreciates feedback from the users of our manuals.
xx
SEP 2009
Security Advice
Motorola systems and equipment provide configurable security parameters to be set by the operator based on their particular operating environment. Motorola recommends setting and using these parameters following industry recognized security practices. Security aspects to be considered are protecting the confidentiality, integrity, and availability of information and assets. Assets include the ability to communicate, information about the nature of the communications, and information about the parties involved. In certain instances Motorola makes specific recommendations regarding security practices, however the implementation of these recommendations and final responsibility for the security of the system lies with the operator of the system. Please contact the Customer Network Resolution Center (CNRC) for assistance. The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com/. Select Customer Network Resolution Center contact information, from the menu located to the left of the Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
SEP 2009
xxi
Warnings, cautions, and notes
The following describes how warnings and cautions are used in this document and in all documents of this Motorola document set.
Warnings
Warnings precede instructions that contain potentially hazardous situations. Warnings are used to alert the reader to possible hazards that could cause loss of life or physical injury. A warning has the following format: WARNING Warning text and consequence for not following the instructions in the warning.
Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems, software, or individual items of equipment within a system. However, this damage presents no danger to personnel. A caution has the following format: CAUTION Caution text and consequence for not following the instructions in the caution.
Notes
A note means that there is a possibility of an undesirable situation or provides additional information to help the reader understand a topic or concept. A note has the following format: NOTE Note text.
xxii
SEP 2009
Safety
Remember! . . . Safety depends on you!! The following 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. Motorola, Inc. assumes no liability for the customers failure to comply with these requirements. The safety precautions listed below represent warnings of certain dangers of which we are aware. You, as the user of this product, should follow these warnings and all other safety precautions necessary for the safe operation of the equipment in your operating environment.
S 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. NOTE Refer to Grounding Guideline for Cellular Radio Installations 68P81150E62.
S not replace components with power cable connected. Under certain
conditions, dangerous voltages may exist even with the power cable removed.
S always disconnect power and discharge circuits before touching them. S Portions of Motorola equipment may be damaged from exposure to
electrostatic discharge. Use precautions to prevent damage Use caution when exposing or handling the CRT Breakage of the CathodeRay 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.
S ANSI IEEE C95.11991, IEEE Standard for Safety Levels with S Council recommendation of 12 July 1999 on the limitation of
Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz. exposure of the general public to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective national regulations. of 29 April 2004 on the minimum health and safety requirements regarding the exposure of workers to the risks arising from physical agents (electromagnetic fields) (18th individual Directive within the meaning of Article 16(1) of Directive 89/391/EEC).
S Directive 2004/40/EC of the European Parliament and of the Council
SEP 2009
xxiii
Caring for the Environment
Please do not dispose of Motorola Networks equipment in landfill sites. Please contact the Customer Network Resolution Center (CNRC) for assistance. The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com/. Select Customer Network Resolution Center contact information, from the menu located to the left of the Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
Disposal of Motorola Networks equipment in EU countries
In the EU, Motorola Networks in conjunction with a recycling partner will ensure that equipment is collected and recycled according to the requirements of EU environmental law.
Disposal of Motorola equipment European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE) Do not dispose of Motorola equipment in landfill sites. In the EU, Motorola in conjunction with a recycling partner ensures that equipment is collected and recycled according to the requirements of EU environmental law. Disposal of surplus packaging European Parliament and Council Directive 94/62/EC Packaging and Packaging Waste Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipients responsibility to ensure that packaging materials are collected and recycled according to the requirements of EU environmental law.
Disposal of Motorola Networks equipment in nonEU countries
In nonEU countries, dispose of Motorola Networks equipment in accordance with national and regional regulations.
xxiv
SEP 2009
CMM labeling and disclosure table
The Peoples Republic of China require that our 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.
S Logo 1 means the product contains no substances in excess of the
maximum concentration value for materials identified in the China Management Methods regulation. 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.
S Logo 2 means that the product may contain substances in excess of the
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 is intended only to communicate compliance with China requirements. It is not intended to communicate compliance with EU RoHS or any other environmental requirements.
SEP 2009
xxv
Motorola document set
The Motorola document sets provide the information needed to operate, install and maintain the Motorola equipment. Obtaining manuals To view, download, or order manuals (original or revised), visit the Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, or contact your Motorola account representative. If Motorola changes the content of a manual after the original printing date, Motorola publishes a new version with the same part number but a different revision character. If Motorola changes the content of a document after the original printing date, Motorola publishes a new version with the same part number but a different revision character. Manual banner definitions A banner (oversized text on the bottom of the page, for example, PRELIMINARY) indicates that some information contained in the manual is not yet approved for general customer use.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the network is encrypted. In order to comply with the export and import requirements of particular countries, this encryption occurs at different levels as individually standardized, or may not be present at all in some parts of the network in which it is normally implemented. The document set, of which this document is a part, covers encryption as if fully implemented. Because the rules differ in individual countries, limitations on the encryption included in the particular software being delivered, are covered in the Release Notes that accompany the individual software release.
xxvi
SEP 2009
Third Party computer software and trademarks
Computer Software
The Motorola and 3rd Party supplied Software (SW) products described in this instruction manual may include 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 and other 3rd Party supplied SW certain exclusive rights for copyrighted computer programs, including the exclusive right to copy or reproduce in any form the copyrighted computer program. Accordingly, any copyrighted Motorola or other 3rd Party supplied SW computer programs contained in the Motorola products described in this instruction manual may not be copied (reverse engineered) or reproduced in any manner without the express written permission of Motorola or the 3rd Party SW supplier. 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 SW, except for the normal nonexclusive, royalty free license to use that arises by operation of law in the sale of a product.
Vendor Wind River Systems, Inc. Apache Software Foundation * * Publicly Available Software
Copyright Copyright 19842007 All rights reserved. Copyright 19992007 All rights reserved.
Trademarks
Javat Technology and/or J2MEt: Java and all other Javabased marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. UNIXR: UNIX is a registered trademark of The Open Group in the United States and other countries. 3ComR and OfficeConnectR: 3Com and OfficeConnect are registered trademarks of the 3Com Corporation. MicrosoftR, WindowsR. and Windows MeR: Microsoft, Windows, and Windows Me are registered trademarks of Microsoft Corporation; Windows XPt is a trademark of Microsoft Corporation. CiscoR, Cisco IOSR, and IOSR: Cisco, Cisco IOS, and IOS are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries. PC Cardt: PC Card is a trademark of the Personal Computer Memory Card International Association (PCMCIA) Anritsut is a trademeark of the Anritsu Company.
SEP 2009
xxvii
FCC Requirements
Content
This section presents Federal Communications Commission (FCC) Rules Parts 15 and 68 requirements and compliance information for the SCt4812 series Radio Frequency Base Transceiver Subsystems (BTS).
FCC Part 15 Requirements
Part 15.19a(3) INFORMATION TO USER NOTE This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Part 15.21 INFORMATION TO USER Changes or modifications that change the FCC type approved configuration of the equipment could void the users authority to operate the equipment.
xxviii
SEP 2009
FCC Requirements continued

15.105(b) INFORMATION TO USER NOTE This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment OFF and ON, the user is encouraged to try to correct the interference by one or more of the following measures: Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help.
FCC Part 68 Requirements
This equipment complies with Part 68 of the FCC rules and the requirements adopted by the Administrative Council for Terminal Attachments (ACTA). The product identifier in the format US: AAAAEQ##TXXXX is located on a label. If requested, this number must be provided to the telephone company. The label that contains the product identifier is visible when the GLI and MCCDO boards are removed from the cage. FCC Part 68 Registered Devices Item Group Line Interface (GLI2) *See Note Group Line Interface (GLI3) *See Note Cisco Model 190027 Router ADC KENTROX Model 537 Description US: IHEUSA32769XDE US: IHEXDNANGLI31X US: 5B1DDNDN0006 US: F81USA31217DEN table continued on next page
SEP 2009 1X SC4812T CLPA BTS Optimization/ATP xxix

FCC Part 68 Registered Devices Item MultiChannel CDMA Data Only (MCCDO) *See Note Description US: 83YXDNANMCCDO
NOTE
The BTS equipment may be equipped with either the GLI2, <US: IHEUSA32769XDE>, or the GLI3, < US: IHEXDNANGLI31X>, and the MCCDO, <US: 83YXDNANMCCDO>, and may be used in conjunction with one or both of the listed registered CSU devices, or another registered CSU device not listed above.
A plug and jack used to connect this equipment to the premises wiring and telephone network must comply with the applicable FCC Part 68 rules and requirements adopted by the ACTA. A compliant telephone cord and modular plug is provided with this product. It is designed to be connected to a compatible modular jack that is also compliant. See installation instructions for details. The Ringer Equivalence Number (REN) is used to determine the number of devices that may be connected to a telephone line. Excessive RENs on a telephone line may result in the devices not ringing in response to an incoming call. In most but not all areas, the sum of RENs should not exceed five (5.0). To be certain of the number of devices that may be connected to a line, as determined by the total RENs, contact the local telephone company. For products approved after July 23, 2001, the REN for this product is part of the product identifier that has the format US:AAAEQ##TXXXX. The digits represented by ## are the REN without a decimal point (for example, 03 is a REN of 0.3). For earlier products, the REN is separately shown on the label.
xxx
SEP 2009

The telephone company may make changes in its facilities, equipment, operations, or procedures that could affect the operation of the users T1. If this happens, the telephone company will provide advance notice to users so that they can modify their equipment as required to maintain uninterrupted service. If this equipment causes harm to the telephone network, the telephone company will notify users in advance that temporary discontinuance of service may be required. If advance notice is not practical, the telephone company will notify users as soon as possible. Also, users will be advised of their right to file a complaint with the FCC if the users believe it is necessary. If trouble is experienced operating this equipment with the T1, please contact the Customer Network Resolution Center (CNRC) for repair and/or warranty information. The 24hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center contact information. If the trouble is causing harm to the telephone network, the telephone company may request users to disconnect the equipment from the network until the problem is solved. Users should not attempt to repair this equipment themselves. This equipment contains no customer or userserviceable parts. Changes or modifications not expressly approved by Motorola could void the users authority to operate this equipment.
SEP 2009
xxxi
Notes
xxxii
SEP 2009
Chapter 1: Introduction
Table of Contents
Scope, Assumptions, and Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit and Packet BTS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Reader Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Content Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Publication Composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Why Optimize? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What Is Calibration? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What Happens During Calibration? . . . . . . . . . . . . . . . . . . . . . . . . . . . . When to Perform BTS RF Calibration and Acceptance Testing . . . . . . . . . . . . New Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . After Adding MCC Card(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Periodic Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Repaired Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Test Equipment Selection, Calibration, and Operation Requirememnts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Cable Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment Warmup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Test Equipment and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMF Computer and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communications System Analyzer CDMA/analog . . . . . . . . . . . . . . . . Optional Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Documents and Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . Required Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard and Nonstandard Terms and Abbreviations . . . . . . . . . . . . .
1-1 1-1 1-1 1-1 1-2 1-2 1-3 1-3 1-4 1-4 1-4 1-4 1-5 1-5 1-6 1-6 1-7 1-7 1-7 1-8 1-8 1-8 1-8 1-8 1-9 1-9 1-9 1-11 1-13 1-15 1-15 1-16 1-17 1-17
Table of Contents
continued
BTS Equipment Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Frame Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Top I/O (Interconnect) Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCCP Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBX1X and BBX2 Interchangeability . . . . . . . . . . . . . . . . . . . . . . . . PA Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sector Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring a BTS Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-21 1-21 1-21 1-25 1-25 1-27 1-28 1-29 1-31 1-31
SEP 2009
Scope, Assumptions, and Audience Scope, Assumptions, and Audience

CAUTION Procedures in this manual require the use of Local Maintenance Facility for the Windowsr operating system (WinLMF) application software version 2.22.0.0.32 or later.
Scope
This publication provides information pertaining to the optimization and acceptance tests of the SC4812T C Linear Power Amplifier (CLPA) Base Transceiver Subsystem (1X SC4812T CLPA BTS) (1800 mm frame). The following models equipped with trunked Power Amplifiers (PA) and their associated internal and external interfaces are covered:
S 800 MHz models:

+27 Vdc ST1401/ST1402 48 Vdc ST1248/ST1249
S 1.9 GHz models:

+27 Vdc ST1138/ST1139
Circuit and Packet BTS Support
Information in this publication supports optimization and calibration of cdma2000 1X packet BTS sites operating with Motorola Software Release 2.22.0.x and later. The cdma2000 1X (1X) packet BTS has a packet backhaul network interface provided through BTS routers operating with a Thirdgeneration Group Line Interface (GLI3) card that can support voice (IS-95A/B, 1X) and data (IS-95B, 1X). This BTS equipment is configured with all 1X cards (BBX1X and MCC1X). This configuration is compliant with all applicable 1X specifications. It provides the forward link and reverse link RF functions to support Second Generation (2G) features and Third Generation (3G) 1X features; that is, high capacity voice and high bitrate data.
Assumptions
This document assumes that the BTS frames and cabling have been installed according to the following manuals:
S SC Product Family Frame Mounting Guide; 68P09226A18, which S 1X SC4812T CLPA BTS Hardware Installation, which covers
covers the physical bolt down of all SCseries equipment frames BTSspecific cabling configurations for packet backhaul and the addition of carriers to the BTS
1-1
Scope, Assumptions, and Audience

Audience
continued
Motorola has attempted to incorporate into this document the many customer suggestions and comments received since the introduction of the SC product line. Additionally, the attempt has been made to ensure that the scope of the document supports both the novice and expert site technician and engineer with the information required to successfully perform the task at hand. If, in some areas, the manual seems to cover a subject with too much or not enough detail, please keep this in mind.
Intended Reader Profile
The information in this manual set is intended for use by cellular communications personnel in the initial installation and configuration, as well as the day-to-day operation and maintenance of a BTS. The user of this information must have a general understanding of telephony, as used in the operation of the Public Switched Telephone Network (PSTN), and must be familiar with these concepts as they are applied in the cellular and mobile/portable radiotelephone maintenance environment. The user also must have a working knowledge of Microsoftr Windowsr 2000 or Windows XP.
1-2
SEP 2009
Content Summary Content Summary

Publication Composition
This publication covers the following areas.
S Introduction: preliminary background information (such as component

and subassembly locations and frame layouts) to be considered by the Cellular Field Engineer (CFE) before optimization or tests are performed. prepower up tests, and initial power application and powerup tests for the BTS equipment frame after installation.
S Preliminary Operations: jumper configuration of BTS subassemblies, S Optimization/Calibration: downloading all BTS processor boards, test
equipment setup and calibration, PA verification, radio frequency (RF) path verification, Bay Level Offset (BLO) calibration, Cellular Radio Monitoring System (CRMS), and Radio Frequency Diagnostic System (RFDS) functions and calibration. by the LMF and used to verify all major transmit (TX) and receive (RX) performance characteristics on all BTS equipment. Includes generating an ATP report. GLI3 card to interface with the various available transport technologies/techniques and implementing available file transport protocols. completed.
S Acceptance Test Procedures (ATP): automated ATP scripts executed
S Packet BTS Transport Configuration Procedures: configuring the BTS
S Prepare to Leave the Site: site turnover process after ATP is S Basic Troubleshooting: procedures to perform when an ATP fails, as
well as when incorrect results are obtained during logon, test equipment operation, calibration, and Global Positioning System (GPS) operation. These tests are typically used to isolate faults down to the module level. Also provided is additional information necessary to better understand equipment operation. CFE at the site; Pseudorandom Noise (PN) Offset information; an optimization/ATP matrix; output power data tables; CDMA operating frequency programming information; manual test setup information; procedures for verifying that the Voltage Standing Wave Ratio (VSWR) of all antennas and associated feed lines falls within acceptable limits; procedures for downloading ROM and RAM code; detailed information on configuring external BTS routers for initial operation and recovery from incorrect router initialization; and instructions for fabrication of an MMI communication cable; and an overview of and procedures to use during implementation of Open Transport Interface (OTI).
S Appendices containing data sheets to be filled out manually by the
SEP 2009
1-3
Purpose of Optimization Purpose of Optimization

Why Optimize?
Proper optimization, also known as calibration, ensures that:
S Accurate downlink RF power levels are transmitted from the site. S Accurate uplink signal strength determinations are made by the site.
What Is Calibration?
Calibration compensates for the site-specific cabling and normal equipment variations. Site calibration guarantees that the combined losses of the cables and the gain/loss characteristics and built-in tolerances of each BTS frame do not accumulate and cause improper site operation.
What Happens During Calibration?
Overview During calibration, the accumulated path loss or gain is first determined for each RF transmit path in the BTS. These transmit path loss or gain values are then stored in a database along with RF receive path default values. RF path defintions For definitions of the BTS transmit (TX) and receive (RX) paths, see What is Bay Level Offset Calibration? in the Bay Level Offset Calibration section of Chapter 3. NOTE In this publication, all models of the Broad Band Transceiver (BBX) board usable in this BTS, are generically identified as BBX, unless otherwise specified. Also, all models of the MultiChannel CDMA (MCC) cards usable in this BTS, are generically identified as MCC, unless otherwise specified.
RF paths and transceiver calibration Twelve of the BBX boards in each CombinedCDMA Channel Processor (CCCP) shelf are optimized to specific RX and TX antenna connectors. The last BBX board provides redundancy for BBX boards 1 through 12, and is optimized to all antenna connectors. A single calibration value is generated for each complete path. This eliminates the accumulation of error that would occur from individually measuring and summing the gain and loss of each element in the path. Using RF path gain/loss values BTS equipment factors in the derived calibration values internally to adjust transceiver power levels, leaving only sitespecific antenna feedline loss and antenna gain characteristics to be factored in by the CFE when determining required site Effective Radiated Power (ERP) output power levels.
1-4 1X SC4812T CLPA BTS Optimization/ATP SEP 2009
When to Perform BTS RF Calibration and Acceptance Testing When to Perform BTS RF Calibration and Acceptance Testing
This section summarizes Motorolarecommended BTS transmit RF path calibration, forward and reverse RF path integrity and operation verification, and other acceptance testing. Specific calibration and testing recommendations are included for periodic maintenance, troubleshooting and for use after the following listed installation/upgrade activities:
S New BTS and expansion frame installation S BTS conversion from 3 to 6sector operation S Carrier additions S MultiChannel CDMA (MCC) card additions S Site repairs
New Installations
Objectives 1. Calibrate and verify forward (transmit) RF paths 2. Verify reverse (receive) RF path performance 3. Verify MCC operation for a new BTS installation, expansion frame installation, or conversion from 3 to 6sector operation Recommended Actions Perform the following actions after initial powerup, downloading operating code, and verifying GPS operation: 1. Calibrate all transmit RF paths and download derived calibration data. 2. Audit TX calibration of all transmit RF paths to verify BTS calibration is within tolerance. 3. After testing alarm reporting and redundancy performance, perform the code domain power test on all equipped sector carriers, making sure that each equipped MCC is exercised at least once. 4. Perform Frame Error Rate (FER) test, or, for 1xEVDOequipped frames, Packet Erase Rate (PER) test on both the main and diversity RX paths for all sector carriers using at least one MCC. NOTE It is not necessary to test all equipped MCCs during FER/PER testing. 5. Perform any other acceptance tests required to demonstrate compliance with applicable regulatory requirements.
SEP 2009 1X SC4812T CLPA BTS Optimization/ATP 1-5
When to Perform BTS RF Calibration and Acceptance Testing

Site Expansion
continued
Objectives 1. Calibrate and verify forward RF paths 2. Verify reverse RF path performance for the newly added sector carriers. Recommended Actions Perform the following actions after expansion of a site with additional carriers (carrier add): NOTE If carriers are added in conjunction with adding MCCs, testing of both should be combined. It is not necessary to perform separate MCC testing in addition to testing newly added sector carriers. 1. Perform TX calibration and audit on each new sector carrier. 2. Perform the code domain power test for all new sector carriers, making sure that each applicable MCC is exercised at least once. 3. Perform FER/PER test on both the main and diversity RX paths for each new sector carrier using at least one MCC. NOTE It is not necessary to test all equipped MCCs during FER/PER testing. 4. Perform any other acceptance tests required to demonstrate compliance with applicable regulatory requirements.
After Adding MCC Card(s)
Objective Verify operation of new MCC cards. Recommended Actions Perform the following after adding one or more MCC cards to a BTS: NOTE If carriers are added in conjunction with adding MCC cards, testing of both should be combined. It is not necessary to perform separate MCC testing in addition to testing newly added sector carriers.
When to Perform BTS RF Calibration and Acceptance Testing
continued
1. Perform the code domain power test for at least one sector carrier, making sure that each new MCC is exercised at least once. 2. Perform FER/PER test for at least one sector carrier on either the main or diversity RX path using each new MCC. 3. Perform any other acceptance tests required to demonstrate compliance with applicable regulatory requirements.
Periodic Maintenance
Objectives 1. Verify transmit RF path calibration, and recalibrate as required to compensate for equipment performance changes. 2. Validate reverse path performance. NOTE Reverse path validation is not always necessary, but may be desired as a result of observed site operational performance changes. Recommended Actions Perform the following tests on a yearly basis to revalidate the TX and RX paths of the BTS: 1. Perform TX calibration and audit on each sector carrier. 2. Perform FER/PER test for each sector carrier. 3. Perform any other acceptance tests required to demonstrate compliance with applicable regulatory requirements.
Troubleshooting
Objective Support fault isolation or identifying source of degraded performance. Recommended Actions Use any or all of the following tests during a troubleshooting visit to determine the nature of a BTS problem: S TX calibration and audit on the affected sector carrier(s) S Code domain power for the affected sector carrier(s) S TX mask for the affected sector carrier(s) S Pilot time offset for the affected sector carrier(s) S Rho for the affected sector carrier(s) S FER/PER for the affected sector carrier(s)
Repaired Sites
Refer to Appendix C for a detailed FRU Optimization/ATP Test Matrix outlining the minimum tests that must be performed any time a BTS RF subassembly or cable associated with an RF path is replaced.
General Test Equipment Selection, Calibration, and Operation Requirememnts General Test Equipment Selection, Calibration, and Operation Requirememnts
Policy
General Requirements To ensure consistent, reliable, and repeatable BTS calibration results, test equipment and software meeting the following technical criteria should be used for BTS calibration. Test equipment substitution Test equipment can be substituted with other test equipment models, but substitute items must meet the same technical specifications. All test equipment models selected for use in BTS calibration and acceptance testing must be supported by the LMF. Measurement variances and test equipment substitution It is the responsibility of the customer to account for any measurement variances and/or additional losses/inaccuracies which can be introduced as a result of test equipment item substitutions. Before beginning BTS calibration or troubleshooting, make sure that the test equipment needed is onhand and operating properly.
Test Equipment Calibration
Optimum system performance and capacity depend on regular support equipment service and calibration prior to its use for BTS calibration. Follow the original equipment manufacturer (OEM) recommended maintenance and calibration schedules closely.
Test Cable Calibration
Onsite cable calibration Test cables can make critical differences in calibration accuracy. Motorola recommends that cable calibration be run at every BTS with the complete test equipment set. This method compensates for test cable insertion loss within the test equipment set itself. No other allowance for test cable insertion loss needs to be made during the performance of BTS calibration or acceptance tests. Inshop cable characterization Another method to account for cable loss is by entering it into the LMF prior to the calibration procedure. This method requires accurate test cable characterization using shop test equipment. Characterized cables should be tagged with the characterization information, and the measured losses entered into the LMF before performing BTS calibration.
Equipment Warmup
After arriving at the a site, the test equipment should be plugged in and turned on to allow warm up and stabilization for as long as possible. The following test equipment items must be warmed up for a minimum of 60 minutes prior to use for BTS calibration. S Communications Test Set
S Power Meter
Required Test Equipment and Software Required Test Equipment and Software
Overview
Test equipment and software described in this section is required for the calibration and acceptance testing procedures. Common tools such as screwdrivers and frame keys are also needed. Read the operators manual for all test equipment items to understand their individual operation before using them for calibration or acceptance testing.
LMF Computer and Software
LMF Hardware Requirements An LMF computer platform that meets the following requirements (or better) is recommended: S Laptop computer S Windows 2000 or Windows XP operating system S 533 MHz processor (1 GHz or higher recommended) S 4 GB internal hard disk drive S Color display with 1024 x 768 resolution S Memory requirements: Minimum required RAM: 256 MB Recommended RAM: 512 MB S CD/DVD drive S 3 1/2 inch floppy drive (may not be required if equipped with CD/DVD writer drive) S Serial port (COM 1) S Serial port (COM 2) for SC 6XX BTS and serial versions of SC 3XX BTS S Builtin Ethernet Network Interface Card (NIC) (recommended) or PCMCIA Ethernet interface card (not recommended) LMF Computer to BTS Interface Device One or both of the following may be requred to connect the LMF computer platform to the BTS 10Base2 LAN: Ethernet LAN hub or switch Ethernet Hub or Switch (recommended with 10Base2 port, for example 3ComR OfficeConnectR Ethernet Hub 4C) 10Base2/10BaseT converter 10Base2/10BaseT Converter (only needed if hub/switch does not have 10Base2 port, for example Unicom ETP20038T) NOTE Xircom Model PE310B2 or equivalent can also be used to interface the LMF Ethernet connection to the frame.
Required Test Equipment and Software

LMF Software
continued
The Local Maintenance Facility (LMF) application program is a graphical user interface (GUI)based software tool. This product is specifically designed to provide cellular communications field personnel with the capability to support the following CDMA BTS operations:
S Installation S Maintenance S Calibration

3CPCCOMBO CBL
S Connects to the 3COM PCMCIA card and eliminates the need for a
10BaseT/10base2 Converter. RS232 to GPIB Interface
S National Instruments GPIB232CT with Motorola CGDSEDN04X

RS232 serial null modem cable or equivalent; used to interface the LMF to the test equipment.
S Standard RS232 cable can be used with the following modifications
(see Figure 1-1): This solution passes only the 3 minimum electrical connections between the LMF and the General Purpose Information Bus (GPIB) interface. The control signals are jumpered as enabled on both ends of the RS232 cable (9pin D). TX and RX signals are crossed as Null Modem effect. Pin 5 is the ground reference. Short pins 7 and 8 together, and short pins 1, 4, and 6 together on each connector.
Figure 1-1: Null Modem Cable Detail

9PIN DFEMALE GND RX TX RTS CTS RSD/DCD DTR DSR 5 3 2 7 8 1 4 6 9PIN DFEMALE 5 2 3 7 8 1 4 6 GND TX RX RTS CTS RSD/DCD DTR DSR
ON BOTH CONNECTORS SHORT PINS 7, 8; SHORT PINS 1, 4, AND 6
MMI Interface Motorola cable part number CGDSMMICABLE219112 or a cable locally fabricated as described in Appendix K is used to connect the LMF to the BTS.
1-10
SEP 2009

Communications System Analyzer CDMA/analog
continued
Table 1-1: CDMA LMF Test Equipment Support Table Item Test Sets Advantest R3465 (with 3561L) Agilent E4406A (with E4438C) Advantest R3267 Analyzer (with R3562) Agilent 8935 series E6380A (formerly HP 8935) with option 200 or R2K Agilent E7495A or E7495B Anritsut MT8212B Power Meters Agilent E4418B Gigatronix 8541C Power meter Power meter Communications analyzer (with 3561 CDMA option) Communications Analyzer with Agilent E4438C CDMA Signal Generator Communications Analyzer with Advantest R3562 Generator Communications test set IS95A/B only IS95A/B and CDMA 2000 testing IS95A/B and CDMA 2000 testing IS95A/B and CDMA 2000 testing IS95A/B and CDMA 2000 testing IS95A/B and CDMA 2000 testing Description Test Capability
Communications test set Multifunction base station test set
SEP 2009
1-11
continued
A combination of test equipment supported by the LMF may also be used during calibration and testing of the RF communications portion of BTS equipment when the communications system analyzer does not perform all of the following functions:
S S S S S S S S S S
Frequency counter Deviation meter RF power meter (average and code domain) RF signal generator (capable of DSAT/CDMA modulation) Audio signal generator AC voltmeter (with 600ohm balanced audio input and high impedance input mode) Noise measurement meter CMessage filter Spectrum analyzer CDMA code domain analyzer
GPIB Cables
S Hewlett Packard 10833A or equivalent; 1 to 2 meters (3 to 6 feet) long

used to interconnect test equipment and LMF terminal. Timing Reference Cables
S Two BNC-male to BNC-male RG316 cables; 3.05 m (10 ft.) long.

Used to connect the communications analyzer to the front timing reference of the CSM cards in the BTS frame.
Digital Multimeter
S Fluke Model 8062A with Y8134 test lead kit or equivalent; used for
precision dc and ac measurements, requiring 41/2 digits. Directional Coupler
S Narda Model 30445 30 dB (Motorola Part No. 58D09643T01 )
800 MHz coupler terminated with two Narda Model 375BNM loads, or equivalent.
RF Terminations/Loads
S At least three 100Watt (or larger) nonradiating RF

terminations/loads.
1-12
SEP 2009
continued
Miscellaneous RF Adapters, Loads, etc
S As required to interface test cables and BTS equipment and for
various test set ups. Should include at least two 50 Ohm loads (type N) for calibration and one RF short, two NType FemaletoFemale Adapters.
LAN Cables and Adapters
S For connection to the 10Base2 LAN below the CCCP cage: BNCto
BNC 50 Ohm coaxial cable [.91 m (3 ft) maximum] with an FtoF adapter, used to connect the 10BaseTtocoaxial adapter to the BTS LAN connector.
S For connection to BTS I/O panel 10Base2 LAN connectors: 50 Ohm
coaxial cable with two BNC plugs and sufficient length to reach the operating location for the LMF computer and/or 10BaseTto10Base2 Ethernet converter or hub equivalent, for connecting the LMF computer to the BTS I/O panel LAN connectors on indoor BTS models
S BNC T connector, jackplugjack configuration, AMP 2215432 or
Highimpedance Conductive Wrist Strap
S Motorola Model 4280385A59; used to prevent damage from
Electrostatic Discharge (ESD) when handling or working with modules.
Test Set Calibration Support Items The Anritsu MT8212B requires the following additional items to perform the indicated calibrations:
S For standard OpenShortLoad (OSL) calibration:

Anritsu 22N50 Open/Short, DC to 18 GHz, N(m) connector, 50 ohm Anritsu SM/PL precision load, DCto4 GHz, 42 dB, N(m) connector, 50 ohm
S For standard InstaCalt calibration:

Anritsu ICN50 InstaCalt calibration module, 2 MHz to 4 GHz, N(m) connector, 50 ohm
Optional Equipment
NOTE Not all optional equipment specified here will be supported by the LMF in automated tests or when executing various measure type command line interface (CLI) commands. It is meant to serve as a list of additional equipment that might be required during maintenance and troubleshooting operations.
continued
Frequency Counter
S Stanford Research Systems SR620 or equivalent. If direct

Spectrum Analyzer
measurement of the 3 MHz or 19.6608 MHz references is required.
S Spectrum Analyzer (HP8594E with CDMA personality card) or

equivalent; required for manual tests. Local Area Network (LAN) Tester
S Model NETcat 800 LAN troubleshooter (or equivalent); used to

supplement LAN tests using the ohmmeter. Span Line (T1/E1) Verification Equipment
S As required for local application

Oscilloscope
S Tektronics Model 2445 or equivalent; for waveform viewing, timing,

and measurements or during general troubleshooting procedure. 2way Splitter
S MiniCircuits Model ZFSC22500 or equivalent; provides the

diversity receive input to the BTS High Stability 10 MHz Rubidium Standard
S Stanford Research Systems SR625 or equivalent required for CSM

and Low Frequency Receiver/High Stability Oscillator (LFR/HSO) frequency verification.
Itasca Alarms Test Box
S Itasca CGDSCMIS00014 This test box may be used as a tool to

assist in the testing of customer alarms.
1-14
SEP 2009
Required Documents and Related Publications Required Documents and Related Publications
Required Documents
The following documents are required to perform optimization of the cell site equipment: S Site Document (generated by Motorola Systems Engineering), which includes: General Site Information Floor Plan RF Power Levels Frequency Plan (includes Site PN and Operating Frequencies) Channel Allocation (Paging, Traffic, etc.) Board Placement Site Wiring List CDF files (bts#.cdf and cbsc#.cdf) S Demarcation Document (Scope of Work Agreement) S Equipment Manuals for non-Motorola test equipment Motorola Publications General In addition to this publication, BTS, operating, conversion, and other related publications listed in the following subsections are required to support operations with the cell site equipment. Required publication issue Use the issue of the publication for the software release installed on the Radio Access Network (RAN) to which the BTS being modified is assigned. Visit https://mynetworksupport.motorola.com for complete lists of Motorola BTS and operating publications by software release. SC4812TMC and Other Publications The following publications are required to support various operations on the cell site equipment: S LMF Help function online documentation (part of the Local Maintenance Facility (LMF) software application) S 1X SC4812T CLPA BTS Hardware Installation S 1X SC4812T CLPA BTS Field Replaceable Units S LMF CDMA CLI Reference CDMA Remote Montoring System (CRMS) Publicaitons S CRMS Probe Installation Guide; 68P02969A20 S CRMS Probe Users Guide; 68P02969A25 Additional NonMotorola Publications S MWR 1941DC Wireless Mobile Edge Router Software Configuration Guide; part number 7813983
Required Documents and Related Publications
continued
S MWR1941DC Mobile Wireless Edge Router Hardware Installation

Guide; part number 7815827
Related Publications
Additional, detailed information about the installation, operation, and maintenance of the 1X SCt4812TCLPA BTS and its components is included in the following publications:
S S S S
SC Product Family Frame Mounting Guide; 68P09226A18 Cellular System Administration CDMA OnLine Documentation 1X SC4812 Series Packet BTS Troubleshooting Guide); 68P09266A07 Glossary of Cellular Acronyms and Terms CDMA Online Documentation, 68P09266A86
1-16
SEP 2009
Terms and Abbreviations Terms and Abbreviations

Standard and Nonstandard Terms and Abbreviations
Standard terms and abbreviations used in this manual are defined in Glossary of Cellular Acronyms and Terms CDMA Online Documentation, 68P09266A86. Any nonstandard terms or abbreviations included in this manual are listed in Table 1-2. Table 1-2: Abbreviations and Acronyms Acronym 1X Definition One of two bandwidths currently defined in the IS2000 CDMA specification, which extends the capability of the IS95A and B specifications. 1X bandwidth provides wireless packet voice and data transmission capability at up to 144 Mbps. As Required Broadband Transceiver, 3rd Generation supports IS95A/B and cdma2000 1X Redundant BBX for a CCP shelf or cage. BTS Packet Router. Markings on GLI3 Fast Ethernet connectors and SC4812T Fast Ethernet interface housing. Base Station Subsystem (BSS). The BSS consists of a Radio Access Network (RAN), at least one Access Node (AN), and a pair of core routers. It may also include a Digital Access Crossconnect System (DACS) to support split backhaul and, under Software Release 2.16.1.x and higher, a Selector Distribution Unit (SDU). BTS RouTeR (see BTS router) BTS RouTeR GRouP (see BTS router group) One of the routers in a BTS router group. The single nonredundant router or redundant router pair required for network interface when a BTS is operating on packet backhaul. Used interchangeably with shelf in SC4812T/ET/ET Lite BTSs, as in Combined CDMA Channel Processor shelf. See minimum standard configuration. Combined CDMA Channel Processor Clock Combining and Distribution. CCP shelf module which accepts timing signals from the active source and distributes them to other CCP shelf modules. Conference of European Postal and Telecommunications Administrators Compact Flash. Type of flash memory card used in the BTS router to store the Internetwork Operating System and configuration files. Cellular Radio Monitoring System table continued on next page
AR BBX1X BBXR BPR BSS
BTSRTR BTSRTRGRP BTS router BTS router group cage canned configuration CCCP CCD CEPT CF CRMS
Terms and Abbreviations
continued
Table 1-2: Abbreviations and Acronyms Acronym duplex router EMPC ESM ETM external BTS router FE See redundant router Expansion Multicoupler Preselector Card Ethernet Surge Module Enhanced Trunking Module MWR 1900 or MWR 1941 BTS routers mounted outside the CCCP or SCCP cage of a packet BTS. Fast Ethernet. 100baseT mode of 10/100baseT Ethernet used for transmitting packetized control and bearer traffic between the BTS router group and GLI3 cards in the BTS. File Transfer Protocol Fixed Wireless Terminal Interface Card Third generation Group Line Interface card. Replaces GLI2 cards in a BTS when upgrading to packet backhaul capability under Software Release 2.16.1.x or higher. Provides all the functionality of GLI2 cards plus additional capabilities needed for packet backhaul. GLI3 cards may only be installed in BSSs operating with Software Release 2.16.1.x or higher software. See redundant router. High Stability Oscillator Secondgeneration HSO card High Stability Oscillator eXpansion. Module installed in a BTS expansion frame which interfaces with the starter frame HSO or MSO for distribution of starter frame timing signals to the expansion frame CSM cards. Integrated BTS Router; see integrated BTS router A GLI3 card loaded with bootROM code which allows the cards controller for Concentration Interface Highway (CHI) bus 2 to function as a router for packet traffic for the BTS. Employing IBRs permits converting a BTS to packet backhaul operation without using an external BTS router group. IBRs can operate as nonredundant or redundant BTS routers, but their employment limits BTS span capacity to one span as opposed to four spans for external BTS routers. Internetwork Operating System. Operating system software used by the external BTS routers. Load Information File LOng RAnge Navigational Multichannel CDMA Card supporting 8 IS95A/B channels. table continued on next page Definition
FTP FWTIC GLI3
high availability BTS router HSO HSO2 HSOX
IBR Integrated BTS Router
IOSR LIF LORAN MCC8E
1-18
SEP 2009
continued
Table 1-2: Abbreviations and Acronyms Acronym MCC24E MCC1X MCIO MCM minimum standard configuration Definition Multichannel CDMA Card supporting 24 IS95A/B channels. Multichannel CDMA Card supporting 16 or 48 CDMA2000 1X or (with Software Release 2.16.0.84.3 and higher) IS95A/B channels. Multicarrier Combiner Input/Output MultiCarrier Module The initial minimum configuration data which must be loaded into a BTS router to enable it to communicate on the network. This standard canned configuration is generated by a script included in the R16.1 software load for the OMCR/CBSC. Separate configuration files for the primary BTS router on each FE LAN at a site is created by the script and can be copied to the Compact Flash (CF) memory card containing the IOS for BTS routers. Once the CF card with the IOS and minimum standard configuration is installed, the BTS router can communicate with the OMCIP and the full, sitespecific router configuration file can be downloaded from the Mobile Wireless Center to the router. Different configuration files are required for circuit and packet backhaul operation. Multicoupler Preselector Card Motorola Standard Oscillator Network Element Configuration Baseline Network Element Configuration File. Term which includes both the NECB and NECJ files (see NECB and NECJ). Network Element Configuration Journal Network Inteface Card. The Ethernet card used to connect to an Ethernet network. A BTS router group consisting of a single router without redundancy used as a costreduced network interface for a BTS operating on packet backhaul. Open Transport Interface Power Distribution Assembly Parallel Linear amplifier Combiner IPbased backhaul between the BTS and the the network. Packet backhaul capability is implemented in Software Release 2.16.1.x and requires equipping a BTS with BTS routers and GLI3 cards. With the packet backhaul upgrade, a BTS can be configured for circuit operation with the capability to switch to packet backhaul or for packetonly operation. A BTS operating on packet backhaul Packet BTS Quartz High Stability Oscillator table continued on next page
MPC MSO NECB NECF NECJ NIC nonredundant router OTI PDA PLC packet backhaul
packet BTS pBTS QHSO
SEP 2009
1-19
continued
Table 1-2: Abbreviations and Acronyms Acronym redundant router ROMmon RGD Definition A BTS router group consisting of two MWR 1900 or MWR 1941 routers with Hot Standby Router Protocol (HSRP) to provide redundancy. Lowlevel operating system used in MWR 1900 or MWR 1941 routers along with the IOS Remote Global Positioning System (GPS) Distribution. Module which allows distribution of digital timing information from a single Remote GPS receiver to up to four BTS RF modem frames (RFMFs). Remote Global Positioning System. GPS receiver which provides digital timing information for BTS RFMFs at a cell site. Single Bandpass Filter Secure File Transfer Protocol See nonredundant router. Simple Network Management Protocol Subscriber Unit Assembly trivial file transfer protocol Universal Time Coordinates Variable VoiceWAN Interface Card WAN Interface Card (also VWIC)
RGPS SBPF SFTP simplex router SNMP SUA tftp UTC Var. VWIC WIC
1-20
SEP 2009
BTS Equipment Identification BTS Equipment Identification

Equipment Overview
The BTS can consist of the following equipment frames: S At least one BTS starter frame 48 V configuration shown in Figure 1-2 +27 V configuration shown in Figure 1-3 S Ancillary equipment frame (or wall mounted equipment) S One or more Expansion frames. Expansion frames are essentially the same as starter frames, but which incorporate unique components on the I/O (Interconnect) panel. NOTE I/O panel detail is provided for Starter Frame in Figure 1-4 and Expansion Frame in Figure 1-5 CCCP cage details are provided in Figure 1-6
Logical BTS
The BTS software implements the logical BTS capability. Previously, all BTS frames colocated at a single site had to be identified in the network with separate and distinct BTS ID numbers. In the Logical BTS feature, all frames located at a single BTS site are identified with unique Frame ID numbers (Frame ID Numbers 1, 101, 201, 301) under a single (site) BTS ID number. A logical BTS can consist of up to four frames.When the LMF is connected to frame 1 of a logical BTS, you can access all devices in all of the frames that make up the logical BTS. A logical BTS requires a CDF file that includes equipage information for all of the logical BTS frames and their devices and a CBSC file that includes channel data for all of the logical BTS fames. Logical BTS Numbering The first frame of a logical BTS has a 1 suffix (e.g., BTS8121 ). Other frames of the logical BTS are numbered with suffixes, 101, 201, and 301 (e. g. BTS812201 ). When you log into a BTS, a FRAME tab is displayed for each frame. If there is only one frame for the BTS, there is only one tab (e.g., FRAME2821) for BTS282. If a logical BTS has more than one frame, there is a separate FRAME tab for each frame (e.g. FRAME4381, FRAME438101, and FRAME438201 for a BTS438 that has three frames). Actions (e.g., ATP tests) can be initiated for selected devices in one or more frames of a logical BTS. Refer to the Select devices help screen for information on how to select devices. CCCP Shelf Card/Module Device ID Numbers All cards/modules/boards in the frames at a single site, assigned to a single BTS number, are also identified with unique Device ID numbers dependent upon the Frame ID number in which they are located. Refer to Table 1-3 and Table 1-4 for specific CCCP Shelf Device ID numbers.
BTS Equipment Identification
continued
Table 1-3: CCCP Shelf/Cage Card/Module Device ID Numbers (Top Shelf)

Frame # Card/Module ID Number (Left to Right) Power Power Power AMR GLI (PS1) (PS2) (PS3) 1 1 1 101 201 301 1 101 201 301 1 101 201 301 2 102 202 302 3 103 203 303 MCC BBX BBX R 4 104 204 304 5 105 205 305 6 106 206 306 R1 R101 R201 R301 MPC/ EMPC 1
1 101 201 301
4 104 204 304
5 105 205 305
6 106 206 306
1 101 201 301
2 102 202 302
3 103 203 303
Table 1-4: CCCP Shelf/Cage Card/Module Device ID Numbers (Bottom Shelf)

Frame # Card/Module ID Number (Left to Right) HSO CSM CSM CCD CCD 1 2 A B 1 101 201 301 2 102 202 302 AMR GLI2 2 2 102 202 302 2 102 202 302 7 8 MCC BBX SW MPC/ EMPC 2
1 101 201 301
10
11
12
10
11
12
107 108 109 110 207 208 209 210 307 308 309 310
111 112 107 108 211 311 212 207 208 312 307 308
109 110
111 112 212 312
209 210 211 309 310 311
1-22
SEP 2009

Figure 1-2: Starter Frame (48 V configuration)
continued
Fan Module
I/O Interconnect Plate (See Figure 1-4 and Figure 1-5)
CCCP Cage
Combiner Section
Power Supply Modules
48 Vdc Power Supply Breakers
Power Amplifier Cage Power Alarms Card
For clarity, doors are not shown.
ti-CDMA-WP-00195-v01-ildoc-ftw REF
SEP 2009
1-23

Figure 1-3: Starter Frame (+27 V configuration)
continued
Fan Module
I/O Interconnect Plate (See Figure 1-4 and Figure 1-5)
CCCP Cage
Combiner Section
CCCP Cage and Power Amplifier Breakers
Power Amplifier Cage
For clarity, doors are not shown.
ti-CDMA-WP-00187-v01-ildoc-ftw REF.
1-24
SEP 2009

BTS Frame Description
continued
The BTS is the interface between the span lines to/from the Centralized Base Station Controller (CBSC) and the site antennas. This frame is described in three sections:
S The top interconnect plate where all connections are made. S The upper portion of the frame which houses circuit breakers, cooling
fans, and the CCCP shelf.
S The lower portion of the frame which houses the power amplifiers and
PA fans, and TX filter/combiners.
Top I/O (Interconnect) Panel
All cabling to and from the BTS equipment frames is accomplished at the I/O panel on top of each frame (see Figure 1-4 and Figure 1-5). Connections made here include:
S S S S S S S S S S S S S
Alarm connections Ethernet Surge Module (ESM) Expansion frame connection Fast Ethernet interface Ground connections HSO/LFR connections (supports LFR, HSO, MSO, QHSO, or HSOX) LAN connections Power input RF GPS input or Remote Global Positioning System (RGPS) on the Site I/O Board RGPS Distribution (RGD) card RX antennas Span lines TX antenna
SEP 2009
1-25

Figure 1-4: Starter Frame I/O (Interconnect) Panel
REMOTE GPS DISTRIBUTION (RGD) MODULE USED ONLY IF EXPANSION FRAME(S) INSTALLED AND RGPS IS USED. SITE I/O ALARM CONNECTORS SPAN I/O
continued
SPAN I/O RGPS

SPAN I/O B
REAR
SITE I/O SITE I/O SPAN I/O A
RECEIVE LAN ANTENNA CONNECTORS CONNECTIONS LAN GROUND STUD (NOT PRESENT ON FRAMES PRODUCED AFTER JANUARY 2005) RF GPS IN
2A 5A
ALARM B ALARM A
RX
1A 4A
GND
SPAN I/O A
SPAN I/O B
DC FILTER 2
HSO/LFR FILLER PLATE
3A 1B
6A 4B
2B
5B
DC FILTER 1
INPUT CONNECTOR/ DC FILTER POWER INPUT LABEL WILL BE VOLTAGE SPECIFIC 3 TO 6 TRANSMIT ANTENNA CONNECTORS (DEPENDING ON CONFIGURATION) 2 TO 3 TRANSMIT ANTENNA FILLER PLATES (DEPENDING ON CONFIGURATION)
3B
6B
RX
FRONT
ESM FAST ETHERNET INTERFACE HOUSING (IF USED; OTHERWISE, FILLER PLATE USED ON ETHERNET ROUTER OPENING) EXP IN FILLER PLATE
RF EXPANSION PORT TO ANOTHER BTS (USED ONLY IF EXPANSION FRAME INSTALLED; OTHERWISE, FILLER PLATE INSTALLED)
ti-CDMA-WP-00033-v03-ildoc-ftw
1-26
SEP 2009
continued
Figure 1-5: Expansion Frame I/O (Interconnect) Panel

SPAN I/O RECEIVE ANTENNA COVERS
SITE I/O ALARM CONNECTORS SPAN I/O

SITE I/O SPAN I/O A
REAR
SPAN I/O B
LAN CONNECTIONS LAN GROUND STUD (NOT PRESENT ON FRAMES PRODUCED AFTER JANUARY 2005) GPS IN HSO/LFR
DC FILTER 2
ALARM B ALARM A
RX
1A 4A
GND
2A SPAN I/O A SITE I/O SPAN I/O B 3A 1B
5A
6A 4B
FILLER PLATE
DC FILTER 1
2B
5B
INPUT CONNECTOR/ DC FILTER
3B
6B
RX
TX ANTENNA CONNECTORS
FRONT
ESM FAST ETHERNET INTERFACE HOUSING (IF USED; OTHERWISE, FILLER PLATE USED ON ETHERNET ROUTER OPENING) EXP OUT FILLER PLATE
2 TX ANTENNA FILLER PLATES RF EXPANSION PORT FROM STARTER BTS

CCCP Shelf
The upper portion of the frame houses circuit breakers, cooling fans, and the CombinedCDMA Channel Processor (CCCP) shelf (see Figure 1-6). The CCCP shelf includes:
S S S S S
CCCP backplane and cage CCCP Power supplies CDMA clock distribution (CCD) cards Clock Synchronization Manager (CSM) card Low Frequency Receiver (LFR), High Stability Oscillator (HSO), Motorola Standard Oscillator (MSO), or Quartz High Stability Oscillator (QHSO) card
S Alarm Monitoring and Reporting (AMR) cards S GLI cards S Multicoulper Preselector Card (MPC)/Expansion MPC (EMPC)
(expansion frame) card

S S S S
Figure 1-6: CCCP Shelf
continued
Switch card MCC cards BBX cards CIO cards
19 mm Filler Panel
CIO
MPC/EMPC1
MCC1
MCC2
MCC3
MCC4
MCC5
MCC6
AMR1
BBXR
BBX1
BBX2
BBX3
BBX4
BBX5
BBX6
GLI1
PS1
PS2
PS3
CCD1
38 mm Filler Panel
HSO/LFR
CCD2
MPC/EMPC2
NOTE: MCCs may be MCC24Es, MCC8Es, or MCC1Xs. BBXs may be BBX2s or BBX1Xs. GLIs may be GLI2s or GLI3s.
MCC10
MCC12
MCC11
BBX10
BBX11
BBX12
CSM1
CSM2
AMR2
MCC7
MCC8
MCC9
BBX7
BBX8
BBX9
Switch
GLI2
BBX1X and BBX2 Interchangeability
In a BSS operating with R16.0 or later software, BBX1X cards can be used as direct replacements for BBX2 cards; however, different types of BBXs should not be mixed on the same carrier. Therefore, if a BBX2 card is replaced with a BBX1X, all remaining BBX2 cards for the carrier supported by the replaced card must also be replaced with BBX1X cards.
1-28
SEP 2009

PA Shelf
continued
The lower portion of the frame houses the power amplifier shelves which include power amplifiers modules, the PA fans, trunking backplanes, and TX filter/combiners. These components are configured in different ways depending upon a number of factors. Sector Configuration includes diagrams (Figure 1-7) which illlustrate the available configurations. NOTE The configurations in Figure 1-7 show BTS carriers with four Trunked LPAs per carrier. BTS carriers with CLPAs will have only three CLPAs per carrier (D slot not used).
SEP 2009
1-29

Figure 1-7: Power Amplifier (PA) Configurations
SC4812T
Sector Numbering
continued
4 to 1 Combiner
3 Sector
Sector Numbering
Sector Numbering 3 Sector (6 Sector)

1 2
SC4812T 2 to 1 Combiner
3 Sector or 6 Sector
3
Sector Numbering 3 Sector (6 Sector)
3 4 5 6
PA 1A
PA 2A PA 2B
PA 1A
PA 2A PA 2B
C1, S13
PA 1B PA 1C PA 1D PA 3A
C2, S13
PA 2C
C1, S13 (C1, S13)
PA 1B PA 1C PA 1D
PA 2C PA 2D
C2, S13 (C2, S13)
PA 2D PA 4A PA 4B
PA 3A C3, S13 (C1, S46) PA 3B PA 3C PA 3D PA 4D PA 4B
PA 4A C4, S13 (C2, S46)
C3, S13
PA 3B PA 3C PA 3D
PA 4C PA 4D
C4, S13
PA 4C
Sector Numbering
SC4812T Dual Bandpass Filter
6 Sector 3 Sector 2 Adj. 6 Sector 1 Carrier Only or (Carriers Only) (3 Sector)

1 2 3
Sector Numbering 3 Sector

1 4
SC4812T DBPF or 2 to 1 Combiner

3 Sector Only 2 Carrier Maximum
2 5 3 6
Sector Numbering 3 Sector
PA 1A C1, S13 (C1, S13) PA 1B PA 1C PA 1D PA 3A C1, S46 (C2, S13) PA 3B PA 3C PA 3D PA 1B
PA 1A PA 2B PA 1C PA 1D PA 2D
PA 2A
C1, S13
PA 2C
C2, S13
1-30
SEP 2009
Sector Configuration Sector Configuration

Configuring a BTS Frame
There are a number of ways to configure the BTS frame. Table 1-5 outlines the basic requirements. When carrier capacity is greater than two, a 2:1 or 4:1 cavity combiner must be used. For one or two carriers, bandpass filters or cavity combiners may be used, depending on sectorization and channel sequencing. Table 1-5: BTS Sector Configuration Number of carriers 1 2 2 2 2 3,4 3,4 Number of sectors 3 or 6 6 6 3 3 3 3 Channel spacing N/A Nonadjacent Adjacent Nonadjacent Adjacent Nonadjacent Adjacent Filter requirements Bandpass Filter, Cavity Combiner (2:1 or 4:1) Cavity Combiner (2:1 Only) Not supported in single frame Cavity Combiner (2:1 or 4:1) Bandpass Filter Cavity Combiner (2:1 or 4:1) Cavity Combiner (2:1 Only)
Trunked sets are numbered 1 through 4. Refer to Table 1-6 for Power Amplifier and Trunking Backplane compatibility and PA numbering. Figure 1-7 illustrates PA mapping. Table 1-6: Power Amplifier and Trunking Backplane Compatibility Power Amplifier Type LPA CLPA Kit Number STTF1004 STLF1098 Qty per Trunked Set 4 3 Trunking Backplane Type 4x4 3x3 Kit Number STTF4013 STLF4067 Labeling PA Slot A,B,C,D A,B,C Carrier 1,2,3,4 1,2,3,4
SEP 2009
1-31
Sector Configuration
continued
Table 1-7: Sector Configurations Config Ref. No. Description

3Sector/2ADJACENT Carriers The configuration below maps TX with optional 2:1 cavity combiners for 3 sectors/2 carriers for adjacent channels. Note that 2:1 cavity combiners are used (6 total). TX1
BBX1 N/A
TX2
BBX2 N/A
TX3
BBX3 N/A
TX4
N/A BBX7
TX5
N/A BBX8
TX6
N/A BBX9
Carrier#
1 2
6Sector/2NONADJACENT Carriers The configuration below maps TX with 2:1 cavity combiners for 6 sectors/2 carriers for nonadjacent channels.
TX1
BBX1 BBX7
TX2
BBX2 BBX8
TX3
BBX3 BBX9
TX4
BBX4 BBX10
TX5
BBX5 BBX11
TX6
BBX6 BBX12
Carrier#
1 2
3Sector/2NONADJACENT Carriers The configuration below maps TX with 2:1 cavity combiners for 3 sectors/2 carriers for nonadjacent channels.
TX1
BBX1 BBX7
TX2
BBX2 BBX8
TX3
BBX3 BBX9
TX4
N/A N/A
TX5
N/A N/A
TX6
N/A N/A
Carrier#
1 2
3Sector/4ADJACENT Carriers The configuration below maps TX with 2:1 cavity combiners for 3 sector/4 carriers for adjacent channels. TX1 TX2
BBX2 N/A BBX5 N/A
TX3
BBX3 N/A BBX6 N/A
TX4
N/A BBX7 N/A BBX10
TX5
N/A BBX8 N/A BBX11
TX6
N/A BBX9 N/A BBX12
Carrier#
1 2 3 4
BBX1 N/A BBX4 N/A
3Sector / 2ADJACENT Carriers The configuration below maps TX with bandpass filters for 3 sectors/2 carriers for adjacent channels.
TX1
BBX1 N/A
TX2
BBX2 N/A
TX3
BBX3 N/A
TX4
N/A BBX7
TX5
N/A BBX8
TX6
N/A BBX9
Carrier#
1 2
3Sector/3 or 4NONADJACENT Carriers The configuration below maps TX with 4:1 cavity combiners for 3 sectors/3 or 4 carriers for nonadjacent channels. TX1 TX2
BBX2 BBX8 BBX5 BBX11
TX3
TX4
N/A N/A N/A N/A
TX5
N/A N/A N/A N/A
TX6
N/A N/A N/A N/A
Carrier#
1 2 3 4
6Sector/1Carrier The configuration below maps TX with either bandpass filters or 2:1 cavity combiners for 6 sector/1 carrier. TX1
BBX1
TX2
BBX2
TX3
BBX3
TX4
BBX4
TX5
BBX5
TX6
BBX6
Carrier#
1
NOTE: BBXs may be BBX2s or BBX1Xs.
1-32
SEP 2009
Chapter 2: Preliminary Operation

Table of Contents
Preliminary Operations: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Site Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Equipage Verification and Card/Module Installation . . . . . . . . . . . . . . . . . Site Equipage Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial Installation of Cards/Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . Frame Identification Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Frame Identification (ID) with CCCP Cage Backplane DIP Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PrePowerup Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabling Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DC Power Pre-test (BTS Frame) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial Powerup Tests and Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power-up Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Common Power Supply Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial Power-up (BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1 2-1 2-1 2-1 2-2 2-2 2-2 2-4 2-4 2-5 2-5 2-5 2-5 2-6 2-9 2-9 2-10 2-11
SEP 2009
Table of Contents
continued
Notes
SEP 2009
Preliminary Operations: Overview Preliminary Operations: Overview

Introduction
2
This section first verifies proper frame equipage. This includes verifying module placement, jumper, and Dual Inline Package (DIP) switch settings against the site-specific documentation supplied for each BTS application. Next, pre-power up and initial power-up procedures are presented.
Cell Site Types
Sites are configured as Omni with a maximum of 4 carriers, 3sectored with a maximum of 4 carriers, and 6sectored with a maximum of 2 carriers. Each type has unique characteristics and must be calibrated accordingly. For more information on the differences in site types, please refer to the 1X SC4812T CLPA BTS Hardware Installation.
NEC
The Network Element Configuration (NEC) files (packet BTS) contain site type and equipage data information and passes it directly to the LMF during optimization. The number of modem frames, CCCP shelves, BBX boards, MCC boards (per cage), and power amplifier assignments are some of the equipage data included in the NEC files. CAUTION Be sure that the correct NECB*bts#.xml and NECJ*bts#.xml files are used for the BTS. These should be the NEC files that are provided for the BTS by the OMCR. Failure to use the correct NEC files can cause system errors. Failure to use the correct NEC files to log into a live (traffic carrying) site can shut down the site.
SEP 2009
2-1
Site Equipage Verification and Card/Module Installation Site Equipage Verification and Card/Module Installation
2
Site Equipage Verification
Review the site documentation. Match the site engineering equipage data to the actual boards and modules shipped to the site. Physically inspect and verify the equipment provided for the BTS or modem frame and ancillary equipment frame. CAUTION Always wear an approved antistatic wrist strap while handling any circuit card/module to prevent damage from ESD. After removal, the card/module should be placed on a conductive surface or back into the antistatic shipping container.
Initial Installation of Cards/Modules
Follow the procedure in Table 2-1 to verify the initial installation of cards/modules. Table 2-1: Initial Installation of Cards/Modules Step 1 2 Action Refer to the site documentation and install all cards and modules into the appropriate shelves as required. Verify they are NOT SEATED at this time.
NOTE
The Switch card has a configuration DIP switch that must be set to match the site configuration (see Figure 2-1). As the actual site hardware is installed, record the serial number of each module on a Serial Number Checklist in the site logbook. NOTE Figure 2-1 shows DIP switch configuration settings for SC4812Tseries BTS models in both 3sector and 6sector configurations. Switches 1 and 4 control configuration. For Multicarrier BTS models, switch 1 should be down.
2-2
SEP 2009
Site Equipage Verification and Card/Module Installation

Figure 2-1: SC4812Tseries BTS Switch Card DIP Switch Settings
continued
SHIELDS
CONFIGURATION DIP SWITCH
CCCP CAGE
BTS AND SECTOR CONFIGURATION SWITCH SETTINGS SC4812T, SC4812T CLPA, and SC4812TMC SC4812ET
3SECTOR SITE
1 2 3 4 BTS ON MF
3SECTOR SITE
1 2 3 4
3 Sector 6 Sector
BTS MF
ON
3 Sector 6 Sector
6SECTOR SITE
6SECTOR SITE
1 2 3 4
SWITCH CARD
1 2 3 4 BTS ON MF
3 Sector 6 Sector
BTS MF
ON
3 Sector 6 Sector
SEP 2009
2-3
Frame Identification Switch Settings Frame Identification Switch Settings

2
Setting Frame Identification (ID) with CCCP Cage Backplane DIP Switch
IMPORTANT
Inspect and set the BTS frame ID with the CCCP cage backplane Dual Inline Package (DIP) switch before power is applied to the frame.
Inspect the CCCP cage backplane switch in a BTS or in each frame of a logical BTS and set as required for the BTS frame number as shown in Figure 2-2. Figure 2-2: SC4812Tseries BTS Backplane DIP Switch Settings for BTS or Logical BTS Operation
ON OFF
MODEM_FRAME_ID_1 MODEM_FRAME_ID_0 BOTTOM / TOP RIGHT / LEFT
FRAME 1 SETTING (STANDALONE STARTER FRAME AND LOGICAL BTS PRIMARY FRAME)
FARRIGHT FAN MODULE REMOVED
FAN MODULE REAR FRONT PWR/ALM REAR FRONT
FAN MODULE
PWR/ALM
Power Supply
Power Supply
Power Supply
AMR / MACH GLI2 MCC241 MCC242 MCC243 MCC244 MCC245 MCC246 BBX21 BBX22 BBX23 BBX24 BBX25 BBX26 BBX2R AMR / MACH GLI2 MCC247 MCC248 MCC249 MCC2410 MCC2411 MCC2412 BBX27 BBX28 BBX29 BBX210 BBX211 BBX212 Switch CIO
MODEM_FRAME_ID_1
MODEM_FRAME_ID_0
BOTTOM / TOP
RIGHT / LEFT
39 mm Filter Panel
CSM
CSM
CCD
ON OFF
MODEM_FRAME_ID_1 MODEM_FRAME_ID_0 BOTTOM / TOP RIGHT / LEFT
FRAME 201 SETTING (EXPANSION FRAME 2)
SC4812T SERIES BTS CCCP CAGE

SC4812T_01010
2-4
CCD
MPC
HSO
MPC
ON OFF
19 mm Filter Panel
FRAME 101 SETTING (EXPANSION FRAME 1)
SEP 2009
PrePowerup Tests PrePowerup Tests

Objective
2
This procedure checks for any electrical short circuits and verifies the operation and tolerances of the cellsite and BTS power supply units prior to applying power for the first time.
Test Equipment
The following test equipment is required to complete the prepowerup tests:
S Digital Multimeter (DMM)

CAUTION Always wear a conductive, high impedance wrist strap while handling the any circuit card/module to prevent damage by ESD.
Cabling Inspection
Using the site-specific documentation generated by Motorola Systems Engineering, verify that the following cable systems are properly connected:
S Receive RF cabling up to 12 RX cables S Transmit RF cabling up to six TX cables S GPS

NOTE
S The negative power cable is red or blue. S The positive power cable (ground) is black.
SEP 2009
2-5
PrePowerup Tests
DC Power Pre-test (BTS Frame)
continued
Before applying any power to the BTS frame, follow the procedure in Table 2-2 while referring to Figure 2-3 to verify there are no shorts in the BTS frame DC distribution system.
Table 2-2: DC Power Pretest (BTS Frame) Step 1 2 On each frame: Action Physically verify that all DC power sources supplying power to the frame are OFF or disabled.
S Unseat all circuit boards (except CCD and CIO cards) in the CCCP shelf and LPA shelves, but
leave them in their associated slots.
S Set CCCP shelf breakers to the OFF position by pulling out power distribution breakers (labeled
CCCP 1, 2, 3) located on the power distribution panel. through 4C4D) located on the power distribution panel. Continue with Step 3 for 48 V or Step 4 for +27 V. 3
S Set LPA breakers to the OFF position by pulling out the LPA breakers (8 breakers, labeled 1A1B
For 48 V configurations ONLY: Verify the resistance on the 48 V bus: Remove the Power Supply Modules (PSMs). Verify that the resistance from the power () feed terminal with respect to the ground terminal on the top of the frame measures > 500 (see Figure 2-3). Verify the resistance on the +27 V bus: Remove PSM#1 or the filler panel.
! CAUTION
Do not put probes inside Elcon connectors. Place the Digital Multimeter probes on the mounting screws on the Elcon connector (bottom two Elcon connectors). If reading is < 500 , a short may exist somewhere in the DC distribution path supplied by the breaker. Isolate the problem before proceeding. A reading > 3 M could indicate an open (or missing) bleeder resistor (installed across the filter capacitors behind the breaker panel). 4 For +27 V configurations ONLY: Verify that the resistance from the power (+ or ) feed terminals with respect to the ground terminal on the top of the frame measures > 500 (see Figure 2-3). If reading is < 500 , a short may exist somewhere in the DC distribution path supplied by the breaker. Isolate the problem before proceeding. A reading > 3 M could indicate an open (or missing) bleeder resistor (installed across the filter capacitors behind the breaker panel). table continued on next page
2-6
SEP 2009
PrePowerup Tests
continued
Table 2-2: DC Power Pretest (BTS Frame) Step 5 Action Set the CCCP breakers to the ON position by pushing them IN one at a time. Repeat Step 3 (for 48 V) or Step 4 (for +27 V) after turning on each breaker.
NOTE
If the multimeter stays at 0 after inserting any board/module, a short probably exists in that board/module. Replace the suspect board/module and repeat the test. If test still fails, isolate the problem before proceeding. 6 Insert and lock the DC/DC converter modules for the CCCP shelf and into their associated slots one at a time. Repeat Step 3 (for 48 V) or Step 4 (for +27 V) after inserting each module. A typical response is that the ohmmeter steadily climbs in resistance as capacitors charge, finally indicating approximately 500 . Verify the correct power/converter modules are installed by observing the locking/retracting tabs appear as follows:
STPN4009B PWR CCCP 4812 +27V
! CAUTION
Insert and lock all remaining circuit boards and modules into their associated slots in the CCCP shelf. Repeat Step 3 (for 48 V) or Step 4 (for +27 V) after inserting and locking each board or module. A typical response is that the ohmmeter steadily climbs in resistance as capacitors charge, stopping at approximately 500 .. Set the LPA breakers ON by pushing them in. Repeat Step 3 (for 48 V) or Step 4 (for +27 V) after turning on each breaker. A typical response is that the ohmmeter will steadily climb in resistance as capacitors charge, stopping at approximately 500 ..
NOTE
Engage circuit breakers only for LPAs that are equipped. 9 10 In the 48V BTS, insert PSMs one at a time in their associated slots, verifying that LED is green. Repeat Step 3 after inserting each module. Seat all LPA and associated LPA fan modules into their associated slots in the shelves one at a time. Repeat Step 3 (for 48 V) or Step 4 (for +27 V) after seating each LPA and associated LPA fan module.
S A typical response is that the ohmmeter will steadily climb in resistance as capacitors charge,
stopping at approximately 500 ..
SEP 2009
2-7
PrePowerup Tests
Figure 2-3: Breaker Panel
continued
2
A LAN A OUT B LAN IN B
TOP OF FRAME
TX OUT
HSO/LFR
6 GND
INPUT CONNECTOR/ DC FILTER
FILLER PLATE GROUND LUG
1A 1C 2A 2C 3A 3C 4A 4C 1 2 3
50 50 50 50
1B 1D 2B 2D 3B 3D 4B
L P A
50 50
50
50
50
4D
C C C P
2-8
50
50
SEP 2009
Initial Powerup Tests and Procedures Initial Powerup Tests and Procedures
Power-up Procedures
2
WARNING Potentially lethal voltage and current levels are routed to the BTS equipment. This test must be performed with a second person present, acting in a safety role. Remove all rings, jewelry, and wrist watches prior to beginning this test. DC Input Power In the tests to follow, power will first be verified at the input to each BTS frame. After power is verified, cards and modules within the frame itself will be powered up and verified one at a time. Before applying any power, verify the correct power feed and return cables are connected between the power supply breakers and the power connectors at the top of each BTS frame. Verify correct cable position referring to Figure 2-3. NOTE For positive power applications (+27 V): S The positive power cable is red. For negative power applications (48 V): S The negative power cable is red or blue.
S The negative power cable is black.
S The positive power cable (ground) is black.

Motorola recommends that the DC input power cable used to connect the frame to the main DC power source conforms to the guidelines outlined in Table 2-3. Table 2-3: DC Input Power Cable Guidelines Maximum Cable Length 30.38 m (100 ft) 54.864 m (180 ft) Greater that 54.864 m (180 ft) NOTE Make sure the connector adapters are securely attached to each of the BTS power feeds and returns. Also, make sure the cables have been properly installed into each connector.
Wire Size 107 mm2 (AWG #4/0) 185 mm2 (350 kcmil) Not recommended
Initial Powerup Tests and Procedures

Common Power Supply Verification
continued
The procedure in Table 2-4 must be performed on any BTS frame connected to a common power supply at the site after the common power supply has been installed and verified per the power supply OEM suggested procedures. Perform the following steps to verify the power input is within specification before powering up the individual cards/modules with the frames themselves. CAUTION While handling any circuit card/module, always wear a conductive, high impedance wrist strap to prevent damage by ESD. Extreme care should be taken during the removal and installation of any card/module. After removal, the card/module should be placed on a conductive surface or back into the antistatic bag in which it was shipped.
Table 2-4: Common Power Supply Verification Step 1 2 On each frame: Action Physically verify that all DC power sources supplying the frame are OFF or disabled.
S Unseat all circuit boards (except CCD and CIO cards) in the CCCP shelf and LPA shelves, but
leave them in their associated slots.
S Set breakers to the OFF position by pulling out CCCP and LPA breakers (see Figure 2-3 for
breaker panel layout if required). CCCP shelf breakers are labeled CCCP1, 2, 3. LPA breakers are labeled 1A1B through 4C4D.
3 4 5 6
On 48 V BTS: Remove the 48 V to +27 V Power Supply Modules. Inspect input cables, verify correct input power polarity via decal on top of frame. Apply power to BTS frames, one at a time, by setting the appropriate breaker in the power supply that supplies the frame to the ON position. After power is applied to each frame, use a digital voltmeter to verify power supply output voltages at the top of each BTS frame are within specifications: On 48 V BTS: 48 Vdc nominal On +27 V BTS: +27 Vdc nominal
On 48 V BTS: Plug in PSMs one at a time and verify Green LEDs on PSMs light.
2-10
SEP 2009

Initial Power-up (BTS)
continued
The procedure must be performed on each frame after input power from the common power supply has been verified. Follow the steps in Table 2-5 to apply initial power to the cards/modules within the frame itself, verifying that each is operating within specification. Table 2-5: Initial Powerup (BTS) Step 1 2 3 Action At the BTS, set the CCCP (POWER) power distribution breakers (see Figure 2-3) to the ON position by pushing in the breakers. Insert the CCCP fan modules. Observe that the fan modules come on line. Verify the correct CCCP power/converter modules by observing the locking/retracting tabs appear as follows: STPN 4009B
PWR CCCP 4812 +27V
! CAUTION
Insert and lock the converter/power supplies into their associated slots one at a time. If no boards have been inserted, all three PWR/ALM LEDs would indicate RED to notify the user that there is no load on the power supplies. If the LED is RED, do not be alarmed. After Step 4 is performed, the LEDs should turn GREEN; if not, then a faulty converter/power supply module is indicated and should be replaced before proceeding. 4 5 6 7 Seat and lock all remaining circuit cards and modules in the CCCP shelf into their associated slots. Seat the first equipped LPA module pair into the assigned slot in the upper LPA shelf including LPA fan. Repeat step 5 for all remaining LPAs.
! CAUTION
On frames that have LPAs, engage the circuit breakers one at a time. On frames that have CLPAs, engage the circuit breakers in pairs as marked on the breaker panel.
NOTE
Engage circuit breakers only for LPAs that are equipped. Set the LPA breakers to the ON position (per configuration ) by pushing them IN. See Figure 2-3 for breaker panel layout. Engage (push) LPA circuit breakers.
S Confirm LEDs on LPAs light.

. . . continued on next page
SEP 2009
2-11
continued
Table 2-5: Initial Powerup (BTS)
Step 8
Action After all cards/modules have been seated and verified, use a digital voltmeter to verify power supply output voltages at the top of the frame remain within specifications: On 48 V BTS: 48 Vdc nominal On +27 V BTS: +27 Vdc nominal
Repeat Steps 1 through 8 for additional colocated frames (if equipped).
2-12
SEP 2009
Chapter 3: Optimization/Calibration
Table of Contents
3
Introduction to Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibration Process Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Site Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Software Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Equipage Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Packet BTS files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMF File Structure Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMF Home Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filename Conventions and Directory Location . . . . . . . . . . . . . . . . . . . LMF Application Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copy NEC Files to the LMF Computer . . . . . . . . . . . . . . . . . . . . . . . . Prepare the LMF Computer for MMI Communication . . . . . . . . . . . . . . . . . . . Named HyperTerminal Connection for MMI Sessions . . . . . . . . . . . . . Terminal Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMF to BTS Connection Service Shelf Connection . . . . . . . . . . . . . . . . . . . . Connect the LMF to the BTS at the Service Shelf . . . . . . . . . . . . . . . . LMF to BTS Connection I/O Panel Connection . . . . . . . . . . . . . . . . . . . . . . . Connect the LMF to the BTS at the I/O Panel . . . . . . . . . . . . . . . . . . . Using the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic LMF Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The LMF Display and the BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Graphical User Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding GUI Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Line Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging into a BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Establishing an MMI Communication Session . . . . . . . . . . . . . . . . . . . . . . . . . Establishing an MMI Communication Session . . . . . . . . . . . . . . . . . . . LMF Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pinging the Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pinging the Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-1 3-1 3-1 3-2 3-2 3-3 3-3 3-4 3-4 3-4 3-5 3-6 3-6 3-7 3-8 3-11 3-11 3-11 3-14 3-14 3-16 3-16 3-18 3-18 3-19 3-19 3-19 3-24 3-25 3-29 3-31 3-31 3-33 3-33 3-34 3-34
Table of Contents
continued
Take Control of Packet BTS Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet BTS Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Taking Control of Packet BTS Resources . . . . . . . . . . . . . . . . . . . . . . . Download the BTS General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download ROM Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RAM Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download BTS Loading Packet GLI Devices . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading code to packet GLI3 card . . . . . . . . . . . . . . . . . . . . . . . . Download BTS Loading NonGLI Devices . . . . . . . . . . . . . . . . . . . . . . . . . . Download Code and Data to NonGLI Devices . . . . . . . . . . . . . . . . . . Enabling Other Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting the CSM Clock Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable CSMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable MCCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSM System Time GPS, LFR, and HSO/MSO Verification . . . . . . . . . . . . . Clock Synchronization Manager (CSM) Subsystem Description . . . . Front Panel LED and Status Displays . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Timing Reference Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSM Frequency Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Setup for GPS and LFR/HSO/MSO/QHSO Verification . . . . . . . . . . . . . . . . . . . GPS and HSO/MSO/QHSO Initialization/Verification . . . . . . . . . . . . . Loran Initialization/Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting Test Equipment to the BTS . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment GPIB Address Settings . . . . . . . . . . . . . . . . . . . . . . . . Supported Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Connection Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment Warm-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic Cable Calibration Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual Cable Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set-up for TX Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup for Optimization/ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Connection to the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Addressing Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual and Autodetect Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selection Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Set Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Set Calibration Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibration Procedures Included . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrate Test Equipment Function (Except Agilent E4406A and Anritsu MT8212B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating the Anritsu MT8212B . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-36 3-36 3-36 3-38 3-38 3-38 3-38 3-40 3-40 3-40 3-43 3-43 3-46 3-46 3-47 3-49 3-50 3-50 3-51 3-52 3-54 3-54 3-55 3-61 3-63 3-63 3-63 3-64 3-65 3-65 3-68 3-69 3-69 3-70 3-74 3-82 3-82 3-84 3-85 3-85 3-85 3-85 3-85 3-92 3-92 3-93 3-93 3-94
SEP 2009
Table of Contents
continued
Setting and Editing Generator Calibration Data . . . . . . . . . . . . . . . . . . . . . . . . . Generator Calibration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cable Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating Cables Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cable Calibration Setup Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrate Test Cabling Using Communications System Analyzer . . . . Calibrate Test Cabling Using Signal Generator & Spectrum Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Cable Loss Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Coupler Loss Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay Level Offset Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of Bay Level Offset Calibration . . . . . . . . . . . . . . . . . . . . . . . . What is BLO Calibration? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transceiver Slots Tested for Different Antenna Configurations . . . . . . When to Calibrate BLOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Path Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BLO Calibration Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Set-up for RF Path Calibration . . . . . . . . . . . . . . . . . . Transmit (TX) Path Calibration Description . . . . . . . . . . . . . . . . . . . . . TX Calibration and the LMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX BLO Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . All Cal/Audit and TX Calibration Procedure . . . . . . . . . . . . . . . . . . . . Download BLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Calibration Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Audit Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create CAL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cellular Remote Monitoring System (CRMS) Probe Setup and Calibration . . CRMS Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Redundancy/Alarm Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundancy/Alarm Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Supply Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Miscellaneous Alarm/Redundancy Tests . . . . . . . . . . . . . . . . . . . . . . . . BBX Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSM, GPS, &HSO Redundancy/Alarm Tests . . . . . . . . . . . . . . . . . . . . Power Amplifier (PA) Redundancy Test . . . . . . . . . . . . . . . . . . . . . . . . GLI Redundancy Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarms Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm Reporting Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDI Alarm Input Verification with Alarms Test Box . . . . . . . . . . . . . . CDI Alarm Input Verification without Alarms Test Box . . . . . . . . . . . Pin and Signal Information for Alarm Connectors . . . . . . . . . . . . . . . .
3-98 3-98 3-100 3-100 3-101 3-101 3-107 3-110 3-111 3-112 3-112 3-112 3-112 3-113 3-113 3-114 3-117 3-117 3-118 3-120 3-120 3-120 3-123 3-124 3-124 3-124 3-125 3-126 3-126 3-127 3-127 3-127 3-127 3-128 3-128 3-130 3-131 3-132 3-133 3-135 3-136 3-136 3-136 3-137 3-138 3-139 3-141 3-143
Table of Contents
continued
Notes
SEP 2009
Introduction to Calibration Introduction to Calibration

Overview
This chapter describes procedures for isolating the BTS from the span lines, preparing and using the LMF, downloading BTS software, CSM reference verification/optimization, set up and calibration of the supported test equipment, transmit/receive path verification, and verifying the customer defined alarms and relay contacts are functioning properly. NOTE Before using the LMF, use an editor to view the CAVEATS section in the readme.txt file in the c:\wlmf folder for any applicable information.
Calibration Process Summary
After a BTS is physically installed and the preliminary operations, such as power up, have been completed, the LMF is used to calibrate the BTS. The basic calibration process consists of the following: 1. Download GLI 1 with code and data and then enable GLI 1. NOTE GLIs must be GLI3 cards. 2. Use the status function and verify that all of the installed devices of the following types respond with status information: CSM, BBX, GLI, and MCC. If a device is installed and powered up but is not responding and is colored gray in the BTS display, the device is not listed in the NEC files. The NEC files must be corrected before the device can be accessed by the LMF. 3. Download code and data to all devices of the following types: CSM BBX (multicarrier uses BBX1X) GLI3 (other than GLI 1) MCC1X 4. Verify the operation of the GPS and QHSO, HSO, or MSO signals. 5. Enable the following devices (in the order listed): Secondary CSM Primary CSM All MCCs 6. Connect the required test equipment for a full optimization. 7. Select the test equipment.
Introduction to Calibration
continued
8. Calibrate the TX and RX test cables if they have not previously been calibrated using the CDMA LMF that will be used for the optimization/calibration. The cable calibration values can also be entered manually. 9. If the TX calibration fails, repeat the optimization for any failed paths. 10. If the TX calibration fails again, correct the problem that caused the failure and repeat the optimization for the failed path. 11. If the TX calibration and audit portion of the optimization passes for a path but some of the TX or RX tests fail, correct the problem that caused the failure and run the individual tests as required until all TX and RX tests have passed for all paths.
Cell Site Types
Sites are configured as Omni/Omni or Sector/Sector (TX/RX). Each type has unique characteristics and must be optimized accordingly. NOTE For more information on the differences in site types, refer to the applicable BTS Hardware Installation manual.
Configuration Files
The Network Element Configuration (NEC) files contain information that defines the BTS and data used to download files to the devices. The NEC Base (NECB NECB*bts#.xml) and NEC Journaling (NECJ NECJ*bts#.xml) files are used by packet BTSs. NEC files must be placed in the applicable BTS folder before the LMF can be used to log into that BTS. NEC files can be obtained from the OMCR using a floppy disk. A file transfer protocol (ftp) method can be used if the LMF computer has that capability. The NEC files include the following information:
S Download instructions and protocol S Site specific equipage information S CCCP shelf allocation plan
BBX equipage (based on cellsite type) including redundancy CSM equipage including redundancy MCC (MCC24E, MCC8E, or MCC1X) channel element allocation plan. This plan indicates how the CCCP shelf is configured, and how the paging, synchronization, traffic, and access channel elements (and associated gain values) are assigned among the (up to 12) MCCs in the shelf.
S CSM equipage including redundancy S HSO equipage whenever either an HSO, QHSO, or MSO backup
timing reference source card is installed in the BTS.
Introduction to Calibration
continued
S Effective Rated Power (ERP) table for all TX channels to antennas
respectively. Motorola System Engineering specifies the ERP of a transmit antenna based on site geography, antenna placement, and government regulations. Working from this ERP requirement, the antenna gain, (dependent on the units of measurement specified) and antenna feed line loss can be combined to determine the required power at the top of the BTS frame. The corresponding BBX output level required to achieve that power level on any channel/sector can also be determined. NOTE Refer to the LMF Help function online documentation (part of the LMF software application) for additional information on the layout of the LMF directory structure (including NEC file location and format).
BTS Software Download
BTS software must be successfully downloaded to the BTS processor boards before calibration can be performed. BTS operating code is loaded from the LMF computer. CAUTION Before using the LMF for calibration or acceptance testing, the correct NECB*bts#.xml and NECJ*bts#.xml files for the BTS must be obtained from the OMCR and put in a bts# folder in the LMF. Failure to use the correct NEC files can cause improper or unpredictable BTS operation. Failure to use the correct NEC files to log into a live (traffic carrying) site can shut down the site. The NEC files are normally obtained from the OMCR on a DOS formatted diskette, or through a file transfer protocol (ftp) if the LMF computer has ftp capability. Refer to the LMF Help function online documentation (part of the LMF software application) for the procedure.
Site Equipage Verification
If it has not already done, use an editor to view the NEC files, and review the site documentation. Verify the site engineering equipage data in the NEC files matches the actual site hardware using a NEC file conversion table. CAUTION Use extreme care not to make any changes to the NEC file content while viewing the file. Changes to the NEC file can cause the site to operate unreliably or render it incapable of operation.
Preparing the LMF Preparing the LMF

Overview
Before optimization can be performed, the LMF application software must be installed and configured on a computer platform meeting Motorolaspecified requirements (see Recommended Test Equipment and Software in Chapter 1).
Software and files for installation and updating of the LMF are provided on CD ROM disks. The following installation items must be available: S LMF Program on CD ROM S NEC files for each supported BTS (on diskette or available from the OMCR) The following section provides information and instructions for installing and updating the LMF software and files.
Overview of Packet BTS files
R16.0 and earlier software releases used the CDF configuration file for each BTS and CBSC supported by the LMF. In a packet BTS operating with Software Release 16.1 or later, the CDF is replaced by the NEC files. There are two NEC files. These are: S NEC Base (NECB) file S NEC Journal (NECJ) file The NECB contains the baseline configuration information and is analogous to the CDF, while the NECJ contains all the changes made to the configuration since the last time the NECB was regenerated. Once the NECJ reaches 80% of its maximum size, the NECB is regenerated by the OMCR, and all updates from the NECJ file are rolled into it. The NEC files play much more extensive role than the previouslyused CDF files. Additional important, LMFrelated facts about the the NEC files are: S Both files (NECB and NECJ) are in eXtensible Markup Language (XML) format. S NECB contains all the up-to-date static configuration information and NECJ contains all the recent changes (including operations) which are not updated in the NECB. S Both files can be viewed in any XML viewer (most easily available is Internet Explorer V5.0 and higher). They can be also viewed by any other word or text processor, but the XML tags will also be seen when using these types of applications. S These files will be created by OMCR from MIB and reflect the BTS provisioning. S These files will be regenerated for each software release upgrade on the system for each BTS. S Unlike the CDF file, the NEC files will reside on both OMCR and GLI3s operating in packet mode. The NEC files will be synchronized periodically between the OMCR and GLI3s in each BTS.
Preparing the LMF
continued
S Both the NECB and NECJ files contain a SoftwareVersion field in

their header section indicating the system release version of these files.
S Instead of the bts#.cdf file, the packet LMF uses

NEC files.
NECB*bts#.xml and NECJ*bts#.xml files, which are copies of the
S A GLI3 operating in packet mode will need the NECB and NECJ files
for site initialization.
S The scope of the NEC files has grown much broader than that of the
CDF and has much more BTScentric information. This is principally because the role of the GLI card has expanded significantly with the introduction of the GLI3 card and packet backhaul. CAUTION Never use a generic NEC file. The specific, siteunique information for the BTS must be included in the NEC file for the site to operate properly.
LMF File Structure Overview
The LMF uses a <x>:\lmf home directory> folder that contains all of the essential data for installing and maintaining the BTS. The following list outlines the folder structure for LMF. Except for the bts# folders, these folders are created as part of the the LMF installation. Refer to the CDMA LMF Operators Guide for a complete description of the folder structure. Figure 3-1: LMF Folder Structure
(C:) x:\<lmf home directory> folder cdma folder bts# folders (A separate folder is required for each BTS where bts# is the unique BTS number; for example, bts163.) loads folder version folder (A separate folder is required for each different version; for example, a folder name 2.8.1.1.1.5.) code folder data folder
SEP 2009
3-5
Preparing the LMF
continued
NOTE The loads folder and all the folders below it are not available from the LMF for Software Release 2.16.4.1. These folders may be present as as a legacy from previous software versions or downloaded from the OMCR. Users will need to manually add the directories to a newly installed LMF when they add the code loads to be downloaded.
LMF Home Directory
The CDMA LMF installation program creates the default home directory, c:\wlmf, and installs the application files and subdirectories (folders) in it. Because this can be changed at installation, the CDMA LMF home directory will be referred to with the generic convention of: <x>:\<lmf home directory> Where: <x> = the LMF computer drive letter where the CDMA LMF home directory is located. <lmf home directory> = the directory path or name where the CDMA LMF is installed.
Filename Conventions and Directory Location
NEC Files The naming conventions for the NECB and NECJ files are: NECB*bts#.xml NECJ*bts#.xmlNECJ*bts#.xml Where: * = any characters can be substituted # = the actual integer BTS number; for example, NECB2.16.4.1.40bts 480.xml The NECB and its corresponding NECJ must have the exact same name, except for the B and J after the initial NEC characters. The NECB and the NECJ must reside in the <LMF_HOME>\cdma\bts# directory for the BTS to which they apply. Load Information File (LIF) The LIF is used for packet BTS. It contains all the devices binaries available for the specified System Software Release. It is the functional equivalent of the Object List File (OLF) file that was used prePacket.
Preparing the LMF
continued
The naming convention for the LIF is: NE_LIF.xml The LIF must be placed in the <x>:\lmf home directory>\cdma\loads\<software_release#> directory; for example, c:\wlmf\cdma\loads\2.17.0.10. The LIF can be obtained from the OMCR directory /screl/<software_release#>/loadable/bts Cal File The Cal File still resides in the <LMF_HOME>\cdma\bts# directory and is named bts#.cal, where # is the actual integer number of the BTS.
LMF Application Installation
This section provides information and instructions for installing and updating the LMF software and files. NOTE First Time Installation Sequence: 1. Install Java Runtime Environment (JRE) 2. Install U/WIN Kshell emulator 3. Install LMF application programs 4. Install/create BTS folders
NOTE Any time U/WIN is installed, the LMF application software must also be installed. This is because the LMF application installation modifies some of the files that are installed during the U/Win installation. These modifications are necessary for proper LMF operation. Installing U/Win overwrites these modifications. There are multiple binary image packages for installation on the CDROM. When prompted, choose the load that corresponds to the software release currently installed in the network. Perform the Device Images installation after the LMF installation. If applicable, a separate CD ROM of BTS Binaries may be available for binary updates.
Follow the procedure in Table 3-1 to install the LMF application program using the LMF CD ROM.
Preparing the LMF
continued
Table 3-1: LMF Application Program Installation n Step 1 2 3 4 5 6 Action Insert the LMF Program CD ROM into the LMF CD ROM drive. If the Setup screen appears, follow the instructions displayed on the screen. If the Setup screen is not displayed, proceed to Step 4. Click on the Start button. Select Run. Enter d:\autorun In the Open box and click OK.
NOTE
If applicable, replace the letter d with the correct CD ROM drive letter.
Copy NEC Files to the LMF Computer
Before logging on to a BTS with the LMF computer to execute optimization/ATP procedures, the correct NECB*bts#.xml and NECJ*bts#.xml files must be obtained from the OMCR and put in a bts-# folder in the LMF computer. This requires downloading the files using File Transfer Protocol (FTP) or creating versions of the OMCR NEC files on a DOSformatted floppy diskette and using the diskette to install the NEC files on the LMF computer. NOTE
S If a network connection is available, the ftp method can

be used to copy the NEC files from the OMCR.
S On Sun OS workstations, the unix2dos command can
be used in place of the cp command (for example, unix2dos NECB2.21.0.0.9bts248.xml NECB2.21.0.0.9bts248.xml). This should be done using a copy of the OMCR NEC files so the original OMCR NEC files are not changed to DOS format.
NOTE When copying NEC files, be sure the numbers used in the NECB*bts#.xml and NECJ*bts#.xml filenames correspond to the locally assigned numbers for each BTS and its controlling OMCR. This will prevent BTS login problems with the LMF.
Preparing the LMF
continued
The procedure in Table 3-2 lists the steps required to transfer the NEC files from the OMCR to the LMF computer using a floppy diskette. For further information, refer to the LMF Help function on line documentation. Table 3-2: Copying NEC Files to the LMF Computer n Step
AT THE OMCR:
Action
1 2 3 4
Start a Command Line Interface (CLI) session and log in. Insert a DOS formatted diskette in the workstation drive. Type eject q and press the <Enter> key. Type mount and press the <Enter> key.
NOTE S Look for the floppy/no_name message on the last line displayed. S If the eject command was previously entered, floppy/no_name will be appended with a
number. Use the explicit floppy/no_name reference displayed when performing step 7. 5 6 7 Change to the directory containing the file by typing cd <directory name> (ex. cd bts248 ) and pressing <Enter>. Type ls <Enter> to display the list of files in the directory. With Solaris versions of Unix, create DOSformatted versions of the NECB*bts#.xml and NECJ*bts#.xml files on the diskette by entering the following command: unix2dos <source filename> /floppy/no_name/ <target filename> For example, unix2dos NECB2.12.4.41bts248.xml /floppy/no_name/ NECB2.12.4.41bts248.xml .
NOTE S Other versions of Unix do not support the unix2dos and dos2unix commands. In these cases,
use the Unix cp (copy) command. The copied files will be difficult to read with a DOS or Windows text editor because Unix files do not contain line feed characters. Editing copied NEC files on the LMF computer is, therefore, not recommended. with a space and ensuring the destination directory (floppy/no_name) is listed at the end of the command string following a space (for example, cp NECB2.21.4.41bts248.xml NECJ2.21.4.41bts248.xml /floppy/no_name).
S Using cp, multiple files can be copied in one operation by separating each filename to be copied
8 9 10
Repeat steps 5 through 7 for each bts# that must be supported by the LMF. When all required files have been copied to the diskette, type eject and press the <Enter> key. Remove the diskette from the workstation drive. table continued on next page
SEP 2009
3-9
Preparing the LMF
continued
Table 3-2: Copying NEC Files to the LMF Computer n Step

ON THE LMF COMPUTER:
Action Start the Windows operating system. Insert the diskette into the LMF. Using Windows Explorer (or equivalent program), create a corresponding bts# folder in the <lmf home directory>\cdma directory for each NECB*bts#.xml and NECJ*bts#.xml file pair copied from the OMCR. Use Windows Explorer (or equivalent program) to transfer the NECB*bts#.xml and NECJ*bts#.xml files from the diskette to the corresponding <lmf home directory>\cdma\bts# folders created in step 13.
11 12 13
14
3-10
SEP 2009
Prepare the LMF Computer for MMI Communication Prepare the LMF Computer for MMI Communication
Named HyperTerminal Connection for MMI Sessions
General Confirming or changing the configuration data of External BTS Routers (EBR) and certain BTS Field Replaceable Units (FRU) requires establishing a ManMachine Interface (MMI) communication session between the LMF and the FRU or EBR. Using features of the Windows operating system, the connection properties for an MMI session can be saved on the LMF computer as a named HyperTerminal connection. This eliminates the need for setting up connection parameters each time an MMI session is required to support operations. Desktop Shortcut Once the named connection is saved, a shortcut for it can be created on the Windows operating system desktop. Double clicking the shortcut icon will start the connection without the need to negotiate multiple menu levels.
Terminal Settings
Perform the following to create a named HyperTerminal connection for FRU or EBR MMI interface and generate a Windows operating system desktop shortcut for it. NOTE There are differences between Windows 2000 and Windows XP operating systems in the menus and screens used for creating a HyperTerminal connection. In the following procedure, items applicable only to the: S Windows 2000 operating system will be identified with Win2000)
S Windows XP operating system will be identified with

WinXP
SEP 2009
3-11
Prepare the LMF Computer for MMI Communication
continued
Table 3-3: Establish HyperTerminal Connection Step 1 2 Action From the Windows operating system Start menu, select: Programs > Accessories Perform one of the following:
S For Win2000, select Hyperterminal and then click on HyperTerminal S For WinXP, select Communications and then click on the HyperTerminal icon. NOTE S If a Location Information Window appears, enter the required information, then click on the S If a You need to install a modem..... message appears, click on NO.
3 When the Connection Description box opens: Type a name for the connection being defined (for example, BTSRTR Session, MMI) in the Name: window, Highlight any icon preferred for the named connection in the Icon: chooser window, and Click OK. From the Connect using: pick list in the Connect To box displayed, select the RS232 port to be used for the connection (e.g., COM1 or COM2), and click OK. In the Port Settings tab of the COM# Properties window displayed, configure the RS232 port settings as follows:
Close button. (This is required the first time a HyperTerminal connection is configured, even if a modem is not to be used.)
4 5
S S S S S
6 7 8 9 10 11
Bits per second: 9600 Data bits: 8 Parity: None Stop bits: 1 Flow control: None
Click OK. With the HyperTerminal window still open and the connection running, select: File > Properties Click the Settings tab, click the arrow in the Emulation window, and select VT100 from the dropdown list. Click the ASCII Setup button, uncheck all boxes in the ASCII Setup window which appears, and click OK. Click OK for the connection Properties box. Save the defined connection by selecting: File > Save table continued on next page
3-12
SEP 2009
Prepare the LMF Computer for MMI Communication
continued
Table 3-3: Establish HyperTerminal Connection Step 12 13 14 15 Close the HyperTerminal window by selecting: File > Exit Click the Yes button to disconnect when prompted. From the Windows operating system Start menu, select Programs > Accessories Perform one of the following: Action
S For Win2000, select Hyperterminal and release any pressed mouse buttons. S For WinXP, select Communications and double click the Hyperterminal folder.
16 17 18 Move the cursor over the newlycreated connection icon. Right click and drag the connection icon to the Windows operating system desktop and release the right mouse button. From the popup menu displayed, select one of the following depending on the operating system used:
S Win2000: Create Shortcut(s) Here S WinXP: Copy Here

19 If desired, reposition the shortcut icon for the new connection by dragging it to another location on the Windows operating system desktop.
NOTE
The shortcut icon can now be doubleclicked to open a BTS router or BTS card/module MMI HyperTerminal session without the need to negotiate multiple menu levels. 20 In WinXP, select File > Close to close the HyperTerminal window.
SEP 2009
3-13
LMF to BTS Connection Service Shelf Connection LMF to BTS Connection Service Shelf Connection
Connect the LMF to the BTS at the Service Shelf
The LMF computer may be connected to the LAN A or B connector located behind the frame lower air intake grill below the CCCP cage. Figure 3-2, below, shows the general location of these connectors. LAN A is considered the primary LAN. Figure 3-2: Service Shelf LAN Connection
NOTE: OPEN LAN CABLE ACCESS DOOR. PULL APART HOOKANDLOOP FABRIC AND GAIN ACCESS TO THE LAN A OR LAN B LMF BNC CONNECTOR. LMF BNC T CONNECTIONS ON LEFT SIDE OF FRAME (ETHERNET A SHOWN; ETHERNET B COVERED WITH HOOKANDLOOP FABRIC)
10BASETTO10BASE2 CONVERTER OR HUB CONNECTS DIRECTLY TO LAN BNC T
LMF COMPUTER TERMINAL WITH MOUSE
PCMCIA 10BASET ETHERNET NETWORK INTERFACE CARD (NIC)
UNSHIELDED TWISTED PAIR (UTP) CABLE (RJ45 CONNECTORS)
115 VAC POWER CONNECTION (IF REQUIRED)
Table 3-4: Connecting the LMF to the BTS, Service Shelf Connection Step 1 2 Action Open the LAN cable access door. (see Figure 3-2). Pull apart the fabric covering one of the BNC T connectors.
! CAUTION
The outer conductor in the 10base2 LAN cabling is isolated from chassis ground. This conductor is connected to the BNC connector shell. Do not allow the BTC T connectors to touch the chassis during calibration. table continued on next page
LMF to BTS Connection Service Shelf Connection
continued
Table 3-4: Connecting the LMF to the BTS, Service Shelf Connection Step 3 4 Slide out the service shelf, if desired. Connect the LMF computer to the BNC connector through an Ethernet Network Interface Card (NIC) (internal or PCMCIA) and 10BaseTto10Base2 converter or hub. Action
NOTE
Xircom Model PE310B2 or equivalent can also be used to interface the LMF Ethernet connection to the BTS frame connected to the PC parallel port, powered by an external AC/DC transformer. In this case, the BNC cable must not exceed 91 cm (3 ft) in length.
SEP 2009
3-15
LMF to BTS Connection I/O Panel Connection LMF to BTS Connection I/O Panel Connection
Connect the LMF to the BTS at the I/O Panel
The LMF may be connected to the BTS 10Base2 LAN at the LAN A or B OUT connectors on the frame I/O panel. Figure 3-3 shows the locations and marking for the I/O panel LAN connectors. This procedure may also be used to connect the LMF to earlier production frames. NOTE BTS frames produced after January 2005 do not have a service shelf below the CCCP cage. As a result, the UTP Ethernet cable and/or coaxial cable used to connect the LMF computer with the I/O panel LAN connector must be long enough to permit placing the LMF computer in another location during optimization or acceptance testing.
Figure 3-3: I/O Panel LAN Connection (SC4812TMC BTS shown; typical for other indoor BTS models)
LAN A OUT CONNECTOR LAN B OUT CONNECTOR (WITH 50 TERMINATOR) COAXIAL CABLE WITH TWO BNC PLUGS
GROUND STUD NOT PRESENT ON FRAMES MANUFACTURED AFTER JANUARY 2005 BNC T (JACKPLUGJACK) 50 TERMINATOR REMOVED FROM I/O PANEL LAN OUT CONNECTOR
10BASET/10BASE2 CONVERTER OR HUB CONNECTS DIRECTLY TO BNC T
LMF COMPUTER PLATFORM WITH MOUSE PCMCIA OR BUILTIN ETHERNET NETWORK INTERFACE CARD (NIC) (10BASET)
115 VAC POWER CONNECTION (IF REQUIRED)
SC 4812TSERIES
LMF_IO_CONNECT_00022
3-16
SEP 2009
LMF to BTS Connection I/O Panel Connection
continued
Table 3-5: Connecting the LMF to the BTS, I/O Panel LAN Connection Step 1 2 3 4 Action Connect the LMF computer platform Network Interface Card (NIC) to the 10base2/10baseT converter or hub. Connect a jackplugjack configuration BNC T connector to the 10base2/10baseT converter or hub (Figure 3-3). Connect one BNC plug of the coaxial cable to one jack of the BNC T connector.
NOTE
1. In this step, do not disconnect the 50 terminator from either LAN IN connector on the I/O panel (these terminators may be grounded with a jumper wire which is fastened to the I/O panel). 2. When this step is performed, the active 10base2 LAN will swap to the one with the terminated LAN OUT connector (LAN B in Figure 3-3). At the top of the frame, remove the 50 terminator from one LAN OUT connector on the I/O panel, and connect the remaining BNC plug on the coaxial cable to this LAN OUT connector.
5 6 7
Connect the 50 terminator removed in step 4, above, to the other jack of the BNC T connector on the converter or hub. At the I/O panel, remove the 50 terminator from the other LAN OUT connector, and wait 30 seconds for the active LAN to swap to the one connected to the BNC T. Replace the 50 terminator on the LAN OUT connector from where it was removed in step 4, above.
SEP 2009
3-17
Using the LMF Using the LMF

Basic LMF Operation
LMF Coverage in This Publication There are LMF application programs to support maintenance of both CDMA and SAS BTSs. All references to the LMF in this publication are for the CDMA application program.
Operating Environments The LMF application program allows the user to work in the two following operating environments which are accessed using the specified desktop icons: S Graphical User Interface (GUI) using the WinLMF icon S Command Line Interface (CLI) using the WinLMF CLI icon The GUI is the primary optimization and acceptance testing operating environment. The CLI environment provides additional capability to the user to perform manually controlled acceptance tests and audit the results of optimization and calibration actions. Basic Operation Basic operation of the LMF in either environment includes performing the following: S Selecting and deselecting BTS devices S Enabling devices S Disabling devices S Resetting devices S Obtaining device status The following additional basic operation can be performed in a GUI environment: S Sorting a status report window For detailed information on performing these and other LMF operations, refer to the LMF Help function online documentation (part of the Local Maintenance Facility (LMF) software application). NOTE Unless otherwise noted, LMF procedures in this manual are performed using the GUI environment. Online Help Task oriented online help is available in the LMF by clicking on Help from the menu bar. NOTE When using the R17 and earlier LMF versions which use JRE 1.4.1, a bug in this JRE version can cause the LMF to become unresponsive when operating with some video cards. See the Troubleshooting: Installation section of Chapter 7 if this problem occurs.
Using the LMF
continued
The LMF Display and the BTS
BTS Display When the LMF is logged into a BTS, a frame tab is displayed for each BTS frames. The frame tab will be labeled with CDMA and the BTS number, a dash, and the frame number (for example, BTS8121 for BTS 812, RFMF 1). If there is only one frame for the BTS, there will only be one tab. NEC file Requirements For the LMF to recognize the devices installed in the BTS, BTS NEC files which include equipage information for all the devices in the BTS must be located in the applicable <x>:\<lmf home directory>\cdma\bts# folder. RFDS or CRMS Probe Display If an RFDS or CRMS Probe is included in the NEC files, a tab labeled with RFDS, a dash, and the BTS numberframe number combination (for example, RFDS8121) will be displayed. NOTE The RFDS display is used for the CRMS models. CRMS models are NOT shown or called out in the LMF screens.
Graphical User Interface Overview
The LMF uses a Graphical User Interface (GUI), which supports the following functions:
S Selecting a device or devices. S Selecting an action to apply to selected device(s). S Status report window displaying progress of actions taking place and
related information.
S Notification when an action is complete and related information such

as indication of success or failure
S An OK button to close the status report window.

Understanding GUI Operation
The following screen captures are provided to help understand how the GUI operates: Figure 3-4 shows the differences between packet and circuit BTS representations on the LMF login screen. If there is a packet configuration file (NEC) for the BTS, the (P) is added as a suffix to the BTS number. Figure 3-5 shows the Self-Managed Network Elements (NE) state of a packetmode BTS (SC4812T shown). An X is displayed on the front of each card that is under SelfManaged NE control by the GLI3 card.
Using the LMF
continued
Figure 3-6 shows three of the available packet mode commands. Normally the GLI3 has Self-Managed NE control of all cards as shown inFigure 3-6 identified with an X. In that state, the LMF may only status a card. In order to download code or test a card, the LMF must request Self-Managed NE control of the card by using the dropdown menu shown. The LMF also uses this menu to release control of the card back to the GLI3. The GLI3 will also assume control of the cards after the LMF logs out of the BTS. The packet mode GLI3 normally is loaded with a tape release and NECB and NECJ files which point to a tape release stored on the GLI3. When the GLI3 has control of a card it will maintain that card with the code on that tape release. Figure 3-7 depicts a packetmode BTS that has the MCC1 and the BBX1 cards under LMF control. Notice that the X is missing from the front of these two cards. Figure 3-4: BTS Login screen identifying circuit and packet BTS files
For detailed information on performing these and other LMF operations, refer to the LMF Help function online documentation (part of the Local Maintenance Facility (LMF) software application).
Using the LMF
continued
Figure 3-5: SelfManaged Network Elements (NEs) state of a packet mode BTS (SC4812T shown)
SEP 2009
3-21
Using the LMF
continued
Figure 3-6: Available packet mode commands
3-22
SEP 2009
Using the LMF
continued
Figure 3-7: Packet mode BTS with MCC2 and BBX2 under LMF control
SEP 2009
3-23
Using the LMF
continued
Command Line Interface Overview
The LMF also provides Command Line Interface (CLI) capability. Activate the CLI by clicking on a shortcut icon on the desktop. The CLI cannot be launched from the GUI, only from the desktop icon. Both the GUI and the CLI use a program known as the handler. The LMF architectural design is such that only one handler can be running at one time. Because of this in R19.0 and later, the GUI must be started before the CLI if the GUI and CLI are to be used at the same time. When the CLI is launched after the GUI, the CLI automatically finds and uses an inprogress login session with a BTS initiated under the GUI. This allows the use of the GUI and the CLI in the same BTS login session. If a CLI handler is already running when the GUI is launched (this happens if the CLI window is already open when the user starts the GUI) or if the GUI is already running when the user starts a second GUI instance, a dialog window displays the following warning message:
The CLI handler is already running. This may cause conflicts with the LMF. Are you sure that you want to start the application? Yes No
Selecting the yes button starts the application. Selecting the no button terminates the application. CLI Format Conventions The CLI command can be broken down in the following way: verb device including device identifier parameters switch option parameters consisting of: keywords equals signs (=) between the keywords and the parameter values parameter values Spaces are required between the verb, device, switch, and option parameters. A hyphen is required between the device and its identifiers. Following is an example of a CLI command. measure bbx<bts_id><bbx_id> rssi channel=6 sector=5 Refer to the LMF CDMA CLI Reference manual for a complete explanation of the CLI commands and their use.
S S S S
3-24
SEP 2009
Using the LMF

Logging into a BTS
continued
Logging into a BTS establishes a communications link between the BTS and the LMF. An LMF session can be logged into only one BTS at a time. Prerequisites Before attempting to log into the BTS, Before attempting to login to a BTS, ensure the following have been completed:
S The LMF is properly connected to the BTS (see Figure 3-2 or

Figure 3-3).
S The LMF application program is correctly installed and prepared. S A bts-# folder with the correct NEC files exists. S The LMF computer was connected to the BTS before starting the
Windows operating system and LMF software. If necessary, restart the computer after connecting it to the BTS in accordance with Table 3-4 or Table 3-5.
NOTE Be sure that the correct NECB*bts#.xml and NECJ*bts#.xml files are used for the BTS. These should be the NEC files that are provided for the BTS by the OMCR. Failure to use the correct NEC files can result in invalid optimization. Failure to use the correct NEC files to log into a live (traffic carrying) site can shut down the site.
SEP 2009
3-25
Using the LMF
continued
BTS Login from the GUI Environment Follow the procedure in Table 3-6 to log into a BTS when using the GUI environment. Table 3-6: BTS GUI Login Procedure n Step Action Start the LMF GUI environment by double clicking on the LMF desktop icon (if the LMF is not running). 1
NOTE
If a warning similar to the following is displayed, select No, shut down other LMF sessions which may be running, and start the LMF GUI environment again:
The CLI handler is already running. This may cause conflicts with the LMF Are you sure you want to start the application? Yes No
2 3 4 5 6
Click on the Login tab (if not displayed). If no base stations are displayed in the Available Base Stations pick list, double click on the CDMA icon. Click on the desired BTS number. Click on the Network Login tab (if not already in the forefront). Enter the correct IP address (normally 128.0.0.2 for a field BTS) if not correctly displayed in the IP Address box.
NOTE
128.0.0.2 is the default IP address for the card in cage slot GLI 1 in field BTS units. 128.0.0.1 is the default IP address for the card in cage slot GLI 2. 7 8 Type in the correct IP Port number (normally 9216 ) if not correctly displayed in the IP Port box. Click on Ping. If the connection is successful, the Ping Display window shows text similar to the following:
Reply from 128 128.0.0.2: bytes=32 time=3ms TTL=255
If there is no response the following is displayed:

128.0.0.2:9216:Timed out
NOTE
If the GLI fails to respond, reset and perform the ping process again. If the GLI still fails to respond, typical problems are shorted BNC to interframe cabling, open cables, crossed A and B link cables, missing 50Ohm terminators, or the GLI itself. table continued on next page
3-26
SEP 2009
Using the LMF
continued
Table 3-6: BTS GUI Login Procedure n Step 9 Action Change the Multi-Channel Preselector (from the Multi-Channel Preselector pick list) selection, normally MPC, to correspond to the BTS configuration, if required.
NOTE
When performing RX tests on expansion frames, do not choose EMPC if the test equipment is connected to the starter frame.
NOTE
Use a Tower Top Amplifier is not applicable to the SC4812T, SC4812ET, SC4812ET Lite, SC4812TMC, or SC4812T Lite BTS models. 10 Click on Login. A BTS tab with a graphical representation of the BTS CCP cage is displayed.
NOTE S If login is attempted to a BTS that is already logged on, all devices will be gray. S For Software Release 2.16.4.0 and earlier, a Mode Selection box asking if the BTS is Trunked
or Multicarrier will pop up. Multicarrier must be selected for the SC4812TMC BTS. failure).
S There may be instances where the BTS initiates a log out due to a system error (than is, a device S If the GLI is OOS_ROM (blue), it will have to be downloaded with code before other devices
can be seen.
S If the GLI is OOS_RAM (yellow), it must be enabled before other installed devices can be seen.
SEP 2009
3-27
Using the LMF
continued
BTS Login from the CLI Environment Follow the procedure in Table 3-7 to log into a BTS when using the CLI environment. NOTE If the CLI and GUI environments are to be used at the same time, the GUI must be started first and BTS login must be performed from the GUI. Refer to Table 3-6 to start the GUI environment and log into a BTS.
Table 3-7: BTS CLI Login Procedure n Step 1 Action Double click the LMF CLI desktop icon (if the LMF CLI environment is not already running).
NOTE
If a warning similar to the following is displayed, select No, shut down other LMF sessions which may be running, and start the LMF CLI environment again:
The CLI handler is already running. This may cause conflicts with the LMF Are you sure you want to start the application? Yes No
At the /wlmf prompt, enter the following command: login bts<bts#> host=<host> port=<port> where: host = GLI card IP address (defaults to address last logged into for this BTS or 128.0.0.2 if this is first login to this BTS). port = IP port of the BTS (defaults to port last logged into for this BTS or 9216 if this is first login to this BTS). A response similar to the following will be displayed:
LMF> 13:08:18.882 Command Received and Accepted COMMAND=login bts33 13:08:18.882 Command In Progress 13:08:21.275 Command Successfully Completed REASON_CODE=No Reason
3-28
SEP 2009
Using the LMF

Logging Out
continued
Logging out of a BTS is accomplished differently for the GUI and the CLI operating environments. NOTE The GUI and CLI environments use the same connection to a BTS. If a GUI and the CLI session are running for the same BTS at the same time, logging out of the BTS in either environment will log out of it for both. When either a login or logout is performed in the CLI window, there is no GUI indication that logout has occurred.
Logging Out of a BTS from the GUI Environment Follow the procedure in Table 3-8 to logout of a BTS when using the GUI environment. Table 3-8: BTS GUI Logout Procedure n Step 1 2 3 Click on BTS on the BTS tab menu bar. Click the Logout item in the pulldown menu (a Confirm Logout popup message appears). Click on Yes or press the <Enter> key to confirm logout. The screen display returns to the Login tab. Action
NOTE
If a logout was previously performed on the BTS from a CLI window running at the same time as the GUI, a Logout Error popup message appears stating the system should not log out of the BTS. When this occurs, the GUI must be exited and restarted before it can be used for further operations. 4 If a Logout Error popup message appears stating that the system could not log out of the Base Station because the given BTS is not logged in, perform the following actions: Click OK. Select File>Exit in the window menu bar. Click Yes in the Confirm Logout popup. Click Yes in the Logout Error popup which appears again. If further work is to be done in the GUI, restart it.
NOTE S The Logout item on the BTS menu bar will only log the LMF out of the displayed BTS. S Logging out of all BTS sessions and exiting the LMF can be done by clicking on the File
selection in the menu bar and selecting Exit from the File menu list. A Confirm Logout popup message will appear.
SEP 2009
3-29
Using the LMF
continued
Logging Out of a BTS from the CLI Environment Follow the procedure in Table 3-9 to logout of a BTS when using the CLI environment. Table 3-9: BTS CLI Logout Procedure n Step 1 Action
NOTE
If the BTS is also logged into from a GUI running at the same time and further work must be done with it in the GUI, proceed to step 2. Logout of a BTS by entering the following command: logout bts<bts#> A response similar to the following is displayed:
LMF> 12:22:58.028 Command Received and Accepted Command=logout bts33 12:22:58.028 Command Received and Accepted 12:22:58.028 Command Successfully Completed REASON_CODE=No Reason
If desired, close the CLI interface by entering the following command: exit A response similar to the following is displayed before the window closes:
Killing background processes....
3-30
SEP 2009
Establishing an MMI Communication Session Establishing an MMI Communication Session

Establishing an MMI Communication Session
For those procedures that require MMI communications between the LMF and BTS FRUs, follow the procedure in Table 3-10 to initiate the communication session. Table 3-10: Establishing MMI Communication Step 1 2 Action Connect the LMF computer to the equipment as detailed in the applicable procedure that requires the MMI communication session and Figure 3-8 or Figure 3-9. If the LMF computer has only one serial port (COM1) and the LMF is running, disconnect the LMF from COM1 by performing the following: 1. Click on Tools in the LMF window menu bar, and select Options from the pulldown menu list. Result: An LMF Options dialog box will appear. 2. In the Test Equipment tab of the dialog box, select COM1 in the Comm Port pulldown on the Serial Connection tab. 3. Click the Disconnect Port button on the Serial Connection tab. Start the named HyperTerminal connection for MMI sessions by double clicking on its Windows operating system desktop shortcut.
NOTE
If a Windows desktop shortcut was not created for the MMI connection, access the connection from the Windows Start menu by selecting: Programs > Accessories > Hyperterminal > HyperTerminal > <Named HyperTerminal Connection (e.g., MMI Session)> 4 Once the connection window opens, establish MMI communication with the BTS FRU by pressing the LMF computer Enter key until the prompt identified in the applicable procedure is obtained.
SEP 2009
3-31
Establishing an MMI Communication Session
continued
Figure 3-8: CDMA LMF Computer Common MMI Connections Cable CGDSMMICABLE219112 or Fabricated MMI Cable
TO FRU MMI CONNECTOR 8PIN
3
LMF COMPUTER
CABLE PART NUMBEr CGDSMMICABLE219112 OR COM1 OR COM2 FABRICATED MMI CABLE (SEE APPENDIX K)
DB9 CONNECTOR
Figure 3-9: CDMA LMF Computer Common MMI Connections Motorola MMI Interface Kit, SLN2006A
TO FRU MMI PORT
8PIN
NULL MODEM BOARD (TRN9666A)
8PIN TO 10PIN RS232 CABLE (P/N 3009786R01)
CDMA LMF COMPUTER

RS232 CABLE COM1 OR COM2 DB9TODB25 ADAPTER FW00687
3-32
SEP 2009
LMF Online Help LMF Online Help

Online Help
Task oriented online help is available in the LMF by clicking on Help in the LMF window menu bar, and selecting LMF Help from the pulldown menu.
SEP 2009
3-33
Pinging the Processor Pinging the Processor

Pinging the Processor
For proper operation, the integrity of the Ethernet LAN A and B links must be be verified. Figure 3-10 represents a typical BTS Ethernet configuration. The drawing depicts one (of two identical) links, A and B.
Ping is a program that routes request packets to the LAN network modules to obtain a response from the specified targeted BTS.
Figure 3-10: BTS LAN Diagram

UNUSED LAN OUT CONNECTORS MUST HAVE NONGROUNDED 50 OHM TERMINATORS INSTALLED. OR BE CONNECTED TO EXPANSION FRAMES WITH COAX CABLES
ON STARTER FRAMES PRODUCED BEFORE JANUARY 2005, LAN IN CONNECTORS MUST HAVE GROUNDED 50 OHM TERMINATORS AT ALL TIMES. ON LOGICAL BTS EXPANSION FRAMES AND STARTER FRAMES PRODUCED AFTER JANUARY 2005, TERMINATORS ON LAN IN CONNECTORS ARE NOT GROUNDED AND GROUND STUD IS NOT PRESENT ON THE BTS I/O PANEL.
IN 50
OUT
IN
OUT
50
CCCP CAGE
A IN
CCCP CAGE A
A IN
A OUT B
OUT
LMF CONNECTORS
BTS (STARTER)
BTS (EXPANSION)
FW00141
Follow the procedure in Table 3-11 and refer to Figure 3-10, as required, to ping each processor (on both LAN A and LAN B) and verify LAN redundancy is operating correctly.
Pinging the Processor
continued
CAUTION Always wear an approved antistatic wrist strap while handling any circuit card/module to prevent damage from ESD.
NOTE Ethernet cables or terminators must be installed on all LAN A and B connectors on each BTS frame I/O panel before performing this test.
Table 3-11: Pinging the Processors Step 1 2 3 Action If it has not already been done, connect the LMF to the BTS (see Figure 3-2 or Figure 3-3). From the Windows desktop, click the Start button and select Run. In the Open box, type ping and the <GLI IP address> (for example, ping 128.0.0.2).
NOTE
128.0.0.2 is the default IP address for the card in cage slot GLI 1 in field BTS units. 128.0.0.1 is the default IP address for the card in cage slot GLI 2. 4 5 Click on the OK button. If the connection is successful, text similar to the following is displayed: Reply from 128 128.0.0.2: bytes=32 time=3ms TTL=255
If there is no response the following is displayed:
Request timed out
NOTE
If the GLI fails to respond, reset and perform the ping process again. If the GLI still fails to respond, typical problems are shorted BNCtointer-frame cabling, open cables, crossed A and B link cables, missing 50Ohm terminators, or the GLI itself.
SEP 2009
3-35
Take Control of Packet BTS Resources Take Control of Packet BTS Resources
Packet BTS Control
In a packet BTS, the GLI3 card controls all BTS resources, such as the MCC, BBX, and CSM cards, which were previously managed by the Central Base Station Controller (CBSC) Mobility Manager (MM) for circuit BTSs. As a result, the LMF can not perform any of the normal code/data download, optimization, or test functions with packet BTS cards until the GLI3 gives up control of these items. NOTE The GLI3 cards in a packet BTS can never be placed under LMF control. GLI3 cards are selfmanaged Network Elements (NE) in a packet Base Station System (BSS). The GLI3 cards are not designed to give up control of the packet BTS and, in packet mode, will not transfer control of themselves to the LMF. An LMF control request for a GLI3 in a packet BTS will fail immediately with a status message of GLI Object Not Supported For LMF Control. In a packet BTS, the GLI3 cards will always show the X in the LMF display indicating they are not under LMF control.
Taking Control of Packet BTS Resources
After logging into a packet BTS for optimization or acceptance testing, the first action which must be performed is transferring control of the BTS cards from the GLI3 to the LMF. Prerequisites LMF must be logged into the BTS.
3-36
SEP 2009
Take Control of Packet BTS Resources

Taking Control
continued
Perform the following to have the LMF assume control of the BTS resources. Table 3-12: Take Control of Packet BTS Resources with the LMF Step 1 Action With the BTS frame card cage displayed in the LMF, click on all MCC and BBX cards or use selections under the BTS tab Select menu item to select them. Result: Cards will change to a darker color in the display when selected. In the BTS tab menu select Device > Packet Mode Options > LMF Control Request Result: An LMF Control progress window will be displayed followed by a status report window when the activity is completed.
NOTE
The X indicating GLI3 control (Figure 3-5) will not be displayed on any cards for which control has been transferred to the LMF. 3 If the attempt to obtain control of some cards fails, repeat steps 1 and 2 for each failed card one card at a time.
SEP 2009
3-37
Download the BTS General Information Download the BTS General Information
Overview
Before a BTS can operate, each equipped device must contain device initialization (ROM) code. ROM code is loaded in all devices during manufacture or factory repair. Device application (RAM) code and data must be downloaded to each equipped device by the user before the BTS can be made fully functional for the site where it is installed.
Download ROM Code
Downloading ROM code to BTS devices from the LMF is NOT routine maintenance nor a normal part of the optimization process. It is only done in unusual situations where the resident ROM code in the device does not match the release level of the software on the RAN AND the OMCR cannot communicate with the BTS to perform the download. If ROM code must be downloaded, refer to Appendix H. Before ROM code can be downloaded from the LMF, the correct ROM code file for each device to be loaded must exist on the LMF computer. ROM code must be manually selected for download. NOTE The ROM code file is not available for GLI3 cards. GLI3s are ROM code loaded at the factory.
RAM Code
NOTE GLI3 cards in packet mode can not be downloaded with RAM code and data using the LMF. Onsite RAM code download to packet GLI3 cards when communication with the OMCR is not possible require expert procedures. Contact the local Morotola account team for assistance if this operation is required. Before RAM code can be downloaded from the CDMA LMF, the correct RAM code file for each device must exist on the LMF computer. RAM code can be automatically or manually selected depending on the Device menu item chosen and where the RAM code file for the device is stored in the CDMA LMF file structure. The RAM code file is selected automatically if the file is in the \lmf\cdma\loads\n.n.n.n\code folder (where n.n.n.n is the version number of the download code). The RAM code file in the code folder must have the correct hardware bin number. RAM code can be downloaded from the LMF to a device that is in any state. After the download is started, the device being downloaded changes to Out Of Service_ReadOnly Memory (OOS_ROM) (blue). When the download is completed successfully, the device changes to Out Of Service_Random Access Memory (OOS_RAM) (yellow).
Download the BTS General Information
continued
For nonGLI devices, data must be downloaded after RAM code is downloaded. To download data, the device state must be OOS_RAM (yellow). Prior to downloading to a device, a code file must be located on the LMF computer. The code file is selected automatically if the code file is in the /lmf/cdma/n.n.n.n/code folder (where n.n.n.n is the version number of the download code that matches the NextLoad parameter in the NEC files). The code file in the code folder must have the correct hardware bin number. Code can be automatically or manually selected. The devices to be loaded with RAM code and data are:
S Clock Synchronization Module (CSM) S Multi Channel Card (MCC24E, MCC8E or MCC1X) S Broadband Transceiver (BBX)
NOTE
S One GLI3 card must be loaded with code and data, and
operating as INS_ACT before the LMF can download any other device. GLI3 cards are normally downloaded from the OMCR or crossloaded from an INS_ACT GLI3 card by being installed in another BTS. If the GLI3 cards in the BTS require a different code load from that installed and communication between the BTS and OMCR is not possible, contact the local Motorola account team for assistance in performing an onsite GLI3 code load. LMF in any order.
S Other devices in the BTS can be downloaded by the
SEP 2009
3-39
Download BTS Loading Packet GLI Devices Download BTS Loading Packet GLI Devices
Beginning with R22.0, the LMF has the capability to download code to GLI3 cards operating in packet mode. This section contains the intructions needed to do this.
Prerequisites
The following must be done before performing this procedure:
S The BTS has power applied and has reached normal operating
temperature
S The GLI3 code and data files required for the software release
installed in the RAN where the BTS is assigned have been loaded in the LMF computer in the correct directory (refer to the Preparing the LMF section in this chapter). connected, and unused LAN connectors are properly terminated (refer to Figure 3-10). necessary, LAN A has been forced to be the active LAN (refer to the procedure in Table 3-5)
S For a logical BTS, the interframe 10Base2 LAN cables are correctly S The LMF computer is connected to the BTS 10Base2 LAN A and, if S The LMF is operating S The LMF is NOT logged into the BTS
Downloading code to packet GLI3 card
Perform the following to load code into the GLI3 cards. Table 3-13: Loading Code into Packet GLI3 Card with the LMF Step 1 Action With the BTS fully powered up, the GLI3 cards should have been connected (seated) in the correct cage slots. Perform one of the following:
S If cards are not seated, seat only the card in Frame 1 cage slot 1, and allow it to complete
initialization to OOS_SBY. connector.
S If all cards are seated, disconnect (unseat) the card in Frame 1 cage slot 2 from the cage backplane NOTE
Do not disconnect any installed Fast Ethernet (FE) cables from card BPR and GLI connectors. 2 In logical BTS expansion frames, unseat all GLI3 cards from their backplane connectors.
NOTE
Do not disconnect any installed FE cables from card BPR and GLI connectors. table continued on next page
Download BTS Loading Packet GLI Devices
continued
Table 3-13: Loading Code into Packet GLI3 Card with the LMF Step 3 Action If desired or required by the network operators procedures, back up the powered GLI3 card configuration files by selecting Tools > GLI3 Code Operations > GLI3 Configuration Files Backup from the LMF window menu bar. Result: A status window will open displaying a progress bar. When the operation is complete, the status window will display a pass/fail indication. If files were backed up, click OK to close the GLI3 Configuration Files Backup status window Verify availability of the GLI3 card in cage slot 1 by selecting Tools > GLI3 Code Operations > Verify GLI3 Availability from the LMF window menu bar. Result: A message box will open, and, if the GLI3 is available, it will display a message that the GLI3 card is detected at IP address 128.0.0.2, port 9216 (128.0.0.2:9216). Click OK to close the message box. Begin the download GLI3 code process for the card by selecting Tools > GLI3 Code Operations > GLI3 Code Download from the LMF window menu bar. Result: A GLI3 Code Download window will open, and download parameter options will be displayed. Using the dropdown pick list for Code file to put on GLI3, select the required code image for the GLI3 card based on the required software release and GLI3 operation mode.
4 5
6 7
NOTE
1. The dropdown picklist will display the GLI3 code images available on the LMF computer by their software release numbers. 2. Listed GLI3 code images will have a suffix of (P) for packet operation or (C) for circuit operation. 9 Select Reset after code download to GLI3 by clicking in the checkbox.
NOTE
This option will cause the GLI3 to reset and initialize with the code image downloaded with this procedure. 10 To prevent a packet GLI3 from continually resetting because the timeout for synchronizing with the OMCR expires, click in the checkbox Leave synchronization resets turned OFF on GLI3 (P).
NOTE
1. This option is only available when packet code is selected for download and Reset after code download to GLI3 is selected. 2. This option is very useful when there will be an extended time before communication between the BTS and the OMCR can be established. Examples are optimization of a new (greenfield) BTS and reconfiguring the BTS backhaul mode. 11 Click OK to download code to the GLI3 card. Result: A GLI3 Code Download status window will open displaying a progress bar and each action taken during the GLI3 code download. A pass/fail indication and description are also provided for each action taken. table continued on next page
SEP 2009
3-41
Download BTS Loading Packet GLI Devices
continued
Table 3-13: Loading Code into Packet GLI3 Card with the LMF Step 12 13 Action When download and reset are successfully completed, be sure the GLI3 initializes as INS_ACT (shows light green in the LMF; LED states: ACT LED steady green, STA LED slow flashing green) If no further actions are needed which requre the other GLI3 card(s) in the BTS to remain unpowered (such as completing conversion to OTI backhaul), seat the other GLI3 cards in the cage backplane. Result: The other GLI3 cards will initialize and the INS_ACT GLI3 will crossload them with the downloaded code.
3-42
SEP 2009
Download BTS Loading NonGLI Devices Download BTS Loading NonGLI Devices
Download Code and Data to NonGLI Devices
Prerequisite In a packet BTS, control of the nonGLI devices has been transferred to the LMF (Table 3-12). Downloading NonGLI Devices NonGLI devices can be downloaded individually or all equipped devices can be downloaded with one action. Follow the procedure in Table 3-14 to download code and data to the nonGLI devices. NOTE
S CSM devices are RAM codeloaded at the factory.
RAM code is downloaded to CSMs only if updating to a newer software version. may fail for some of the devices (a time out occurs). These devices can be downloaded separately after completing the multiple download.
S When downloading multiple devices, the download
SEP 2009
3-43
Download BTS Loading NonGLI Devices
continued
Table 3-14: Download RAM Code and Data or Data Only to NonGLI Devices n Step 1 Action
NOTE
In a packet BTS, be sure to perform the procedure in Table 3-12 to give the LMF control of the nonGLI devices before continuing.
Select the target CSM, MCC, and/or BBX device(s) by clicking on them. 2 Do one of the following, as required:
S To download code and data, click Device in the BTS menu bar, and select Download >
Code/Data in the pulldown menus. pulldown menus.
S To download only data, click Device in the BTS menu bar, and select Download > Data in the
Result: A status report is displayed that shows the results of the download for each selected device. 3 Click OK to close the status report window when downloading is completed.
NOTE S After the download has started, the device being downloaded changes to blue. If the download
is completed successfully, the device changes to yellow (OOSRAM with code loaded). the OOS_RAM state (yellow), the status LED should be rapidly flashing GREEN. the Device > Download > Data command.
S After a BBX, CSM, or MCC device is successfully loaded with RAM code and has changed to S Data can be downloaded without doing a code download any time a device is OOSRAM using
NOTE When downloading code and data to MCC1X cards, the LMF may report that the cards are not responding or have timed out. Newly installed MCC1X cards can take up to 5 minutes to establish the link with the GLI and complete the download. If the LMF reports that newly installed MCC1X cards are not responding, allow a minimum of 5 minutes for the cards to complete the download process and then restatus the cards. Until the 5minute minimum wait time is over, do not: S Attempt to restart the download process to the cards
S Remove the cards from the BTS

Download BTS Loading NonGLI Devices
continued
BBX Cards Remain OOS_ROM If BBX cards remain OOS_ROM (blue) after powerup or following code load, refer to Table 7-5, Steps 9 and 10.
SEP 2009
3-45
Enabling Other Devices Enabling Other Devices

Selecting the CSM Clock Source
CSMs must be enabled prior to enabling the MCCs. Procedures in the following two subsections cover the actions to accomplish this. For additional information on the CSM subsystem, see Clock Synchronization Manager (CSM) Subsystem Description in the CSM System Time GPS, LFR, and HSO/MSO Verification section of this chapter. Select CSM Clock Source A CSM can monitor up to three reference sources at the same time. Typically, however, only two sources are used. The Select CSM Source function can be used to select the clock source for each of the three reference source inputs. This function is only used if the clock source for a CSM needs to be updated to match the currently installed hardware. The Clock Source function provides the following clock source options: S Local GPS
S S S S S S
Mate GPS Remote GPS HSO/MSO/QHSO (only used as source 2 or 3) HSO Extender (only used as source 2 or 3) LFR (only used as source 2 or 3) NONE (only used as source 2 or 3)
Prerequisites S GLI is INS_ACT (light green in the LMF) S CSM is OOS_RAM (yellow in the LMF) or INS_ACT (light green in the LMF) Table 3-15: Select CSM Clock Source Step 1 2 3 4 Action Display the CSM cage view in the LMF by clicking on the CSM area of the CCCP shelf in the picture of the BTS frame. When the CSM cage view replaces the GLI/MCC/BBX view, click on the CSM(s) for which the clock source is to be selected. In a packet BTS, gain control of the selected card(s) by performing the procedure in Table 3-12. Click on Device in the BTS menu bar, and select CSM/MAWI > Select Clock Source... in the pulldown menu list. Result: A CSM clock reference source selection window will appear. 5 Select the applicable clock source in the Clock Reference Source pick lists. Uncheck the related check boxes for Clock Reference Sources 2 and 3 if the displayed pick list item is NOT to be used. table continued on next page
Enabling Other Devices
continued
Table 3-15: Select CSM Clock Source Step 6 Click on the OK button. Result: A status report is displayed showing the results of the operation. 7 Click on the OK button to close the status report window. Action
3
NOTE For RFGPS, verify the CSM configured with the GPS receiver daughter board is installed in slot CSM 1 before continuing.
Enable CSMs Perform the following to enable the CSMs. Table 3-16: Enable CSMs Step 1 Action
NOTE
If the BTS is equipped with two CSMs, enable the card in slot CSM 2 first. Click on the target CSM.
Click on Device in the BTS menu bar, and select Enable/Activate in the pulldown menu list. Result: A status report is displayed showing the results of the enable operation.
Click OK to close the status report window.
NOTE S The card in slot CSM 1 interfaces with the GPS receiver (either onboard or remote). The enable
sequence for this card can require up to one hour to complete (see below).
S FAIL may be shown in the status report table for a slot CSM 1 enable action. If Waiting For
change to the Enabled state after phase lock is achieved.
Phase Lock is shown in the Description field, do not cancel the enable process. The CSM will
table continued on next page
SEP 2009
3-47
continued
Table 3-16: Enable CSMs Step 4 Allow the card to come into service. Action
NOTE 3
The GPS satellite system satellites are not in a geosynchronous orbit and are maintained and operated by the United States Department of Defense (DOD). The DOD periodically alters satellite orbits; therefore, satellite trajectories are subject to change. A GPS receiver that is INS contains an ephemeris (satellite position table) that is updated periodically to take these changes into account. If a GPS receiver has not been updated for a number of weeks, it may take up to an hour for the GPS receiver ephemeris to be updated. Once updated, the GPS receiver must track at least four satellites and obtain (hold) a 3D position fix for a minimum of 45 seconds before the CSM will come in service. (In some cases, the GPS receiver needs to track only one satellite, depending on accuracy mode set during the data load.) 5
NOTE S If two CSM cards are installed and the CSM in slot CSM 1 is in the INS_ACT state, the LMF cage
view should show CSM 1 as light green. If the CSM in slot CSM 2 is the INS_SBY state, the LMF cage view should display CSM 2 colored dark green. Time GPS & LFR/HSO Verification section of this chapter (see Table 3-19, Figure 3-12, and Table 3-20) to determine the cause.
S If more than an hour has passed without the board in slot CSM 1 enabling, refer to the CSM System
After CSMs have been successfully enabled, be sure the PWR/ALM LEDs are steady green (alternating green/red indicates the card is in an alarm state).
3-48
SEP 2009

Enable MCCs
continued
Prerequisites One GLI and the primary CSM must be downloaded and enabled (INS_ACTIVE green) before downloading and enabling MCCs. Enabling MCCs Perform the following to enable the MCCs. Table 3-17: Enable MCCs Step 1 2 Action Verify the MCC(s) have been downloaded with code (yellow, OOS_RAM) and data. Select the MCCs to be enabled from the Select pulldown menu by choosing MCCs or by clicking on them in the graphic display. In a packet BTS, gain control of the selected card(s) by performing the procedure in Table 3-12. From the Device menu, select Enable/Activate. Result: A status report confirms change in the device(s) status. 5 Click on OK to close the status report window.
3 4
SEP 2009
3-49
CSM System Time GPS, LFR, and HSO/MSO Verification CSM System Time GPS, LFR, and HSO/MSO Verification
Clock Synchronization Manager (CSM) Subsystem Description
Overview
Each BTS CSM subsystem features two CSM cards per RFMF. The primary function of the CSM cards is to maintain CDMA system time. GPS is used as the primary timing reference and synchronizes the entire cellular system. In typical operation, the primary CSM locks its Digital Phase Locked Loop (DPLL) circuits to GPS signals. These signals are provided by either an onboard GPS receiver module (RFGPS) or a remote GPS receiver (RGPS). RGPS uses a GPS receiver in the antenna head that has a digital output. The second generation CSM card (CSMII) is required when using the RGPS. A CSMII card can also be equipped with a local (RFGPS) GPS receiver daughter card to support an RFGPS signal. CCCP Shelf CSM Card Slot Assignments The card in CCCP or SCCP shelf slot CSM 1 (CSM 1 card) is the primary timing source, while the card in CSM slot 2 (CSM 2 card) provides redundancy. For RFGPS, the GPS receiver is installed on the CSM 1 card. In a BTS equipped with Remote GPS neither CSM card has a GPS receiver installed. The redundant CSM card is never equipped with a GPS receiver. CSMII Card Type Description Each CSMII card provides a 19.6608 MHz clock, Even Second Tick pulse, and 3 MHz reference that is referenced to one or more of the following available clock sources: S GPS: local/remote RFGPS or RGPS S High Stability Oscillator (HSO) S Motorola Standard Oscillator (MSO) S Quartz High Stability Oscillator (QHSO) S High Stability Oscillator eXpansion (HSOX) S Low Frequency Receiver (LFR) CDMA Clock Distribution Card (CCD) Description CCD cards buffer and distribute evensecond reference and 19.6608 MHz clock signals from the CSM cards. CCD 1 is married to the CSM 1 card, and CCD 2 is married to the CSM 2 card. CSM Card Redundancy The BTS switches between the primary and redundant units (cards CSM 1 and CSM 2, respectively) upon a card failure or command. A failure in CSM 1 or CCD 1 will cause the system to switch to the CSM 2CCD 2 redundant card pair. GPS timing synchronization is continually maintained between the primary and redundant CSMCCD pairs.
CSM System Time GPS, LFR, and HSO/MSO Verification continued

Secondary Timing References The BTS should be equipped with a backup time reference source to maintain synchronization if the GPS reference becomes unavailable. The BTS supports the following backup reference sources: HSO, MSO, HSOX, or LFR. The CSM continuously monitors all available reference sources and selects the most appropriate source for the current operational conditions. Timing Source Fault Management CSM fault management has the ability to switch between the GPS and any available backup reference source in the event of a GPS reference failure. During normal operation, the CSM 1 card will select a GPS reference source (Table 3-20). The source selection can also be overridden through the LMF or system commands.
Front Panel LED and Status Displays
The CSM cards include on-board alarm detection. Hardware and software/firmware state and alarm conditions are displayed by the front panel LED indicator (Figure 3-11). Table 3-18 provides explanations of card front panel LED indications for CSM card state/status. Figure 3-11: CSM Front Panel PWR/ALM LED Indicator
PWR/ALM Indicator
FW00303
After running onboard memory tests, the CSM loads OOS_RAM code from the Flash EPROM, if available. If not available, the OOS_ROM code is loaded from the Flash EPROM.
Table 3-18: CSM PWR/ALM LED Indications LED Display Steady GREEN Steady RED CSM Card State CSM is in INS_ACT or INS_SBY state with no detected faults. Initial power up or module is operating in a fault (alarm) condition. OOS_ROM (no alarm) OOS_ROM with detected fault (alarm) OOS_RAM state with no detected faults OOS_RAM with detected fault (alarm) or CSM in GPS satellite acquisition/synchronization process INS_ACT or INS_SBY with detected fault (alarm) No DC power or on-board fuse is open. After a reset, the CSMs begin to boot. During SRAM test and Flash EPROM code check, the LED is yellow. (If SRAM or Flash EPROM fail, the LED changes to a solid RED and the CSM attempts to reboot.)
Slowly Flashing GREEN Alternating Long RED / Short GREEN Rapidly Flashing GREEN Alternating Short RED / Short GREEN Alternating Long GREEN / Short RED Off Steady YELLOW
Backup Timing Reference Sources
CSM and LFR, HSO, MSO, or QHSO Backup The CSM performs the overall configuration and status monitoring functions for the LFR, HSO, MSO, or QHSO backup reference. During times when a GPS timing reference is unavailable, the CSM can use the LFR, HSO, or MSO to maintain the synchronization initially established by the GPS reference. LFR The LFR requires an external antenna to receive longrange navigation (loran) RF signals. Timing pulses are obtained from this signal, which is synchronized to Universal Time Coordinates (UTC) and GPS time. After initial GPS lock, the LFR can maintain system synchronization indefinitely.

HSO An HSO card provides a highly stable clock source for installed CSM cards. The HSO is capable of maintaining CSM synchronization for a minimum of 24 hours following 24 hours of calibration by a GPS reference. MSO An MSO card provides a highly stable clock source for installed CSM cards. The MSO is capable of maintaining CSM synchronization for a minimum of 8 hours following 8 hours of calibration by a GPS reference. QHSO A QHSO card provides the same highly stable clock source for installed CSM cards. Like the HSO, the QHSO is capable of maintaining CSM synchronization for a minimum of 24 hours following 24 hours of calibration by a GPS reference. HSOX An HSOX card is used to receive an HSO or MSO clock reference from a starter frame in a multiframe BTS. CSM cards using an HSOX backup reference will maintain synchronization from the HSO or MSO in the starter frame during the absence of a GPS reference source. NOTE Allow the base site and test equipment to warm up for 60 minutes after any interruption in oscillator power. CSM card warm-up allows the oscillator oven temperature and oscillator frequency to stabilize prior to test. Test equipment warm-up allows the Rubidium standard timebase to stabilize in frequency before any measurements are made.
SEP 2009
3-53

CSM Frequency Verification
The objective of this procedure is the initial verification of the Clock Synchronization Module (CSM) cards and timing sources before performing the RF path verification tests.
Test Equipment Setup for GPS and LFR/HSO/MSO/QHSO Verification
Follow the steps outlined in Table 3-19 to set up test equipment. Table 3-19: Test Equipment Setup for GPS and LFR/HSO/MSO/QHSO Verification Step 1 Action Perform one of the following as required by installed equipment: 1. For local GPS (RFGPS): Verify a CSM card with a GPS receiver is installed in the primary CSM slot, CSM 1, and that the card is INS_ACT (light green in LMF display).
NOTE
Verify by checking the card ejectors for kit number SGLN1145 on the CSM 1 card. 2. For Remote GPS (RGPS): Verify a CSMII card, kit number SGLN4132ED or subsequent, is installed in both the primary (CSM 1) and secondary (CSM 2) card slots, and that the cards are INS_ACT (steady green LED on card front panels and light and dark green color, respectively, in LMF display). 2 3 4 5 Remove the CSM 2 card (if installed), and connect an MMI communication cable from the LMF computer COM 1 port to the MMI port on the CSM 1 card (see Figure 3-12). Reinstall the CSM 2 card. Start an MMI communication session with the CSM 1 card by using the Windows desktop shortcut icon (see Table 3-3) . When the terminal screen appears press the Enter key until the CSM> prompt appears.
CAUTION 1. In the power entry compartment, connect the GPS antenna to the RF GPS connector ONLY. Damage to the GPS antenna and/or receiver can result if the GPS antenna is inadvertently connected to any other RF connector. 2. The following procedure requires handling of staticsensitive devices. Always wear an approved antistatic wrist strap while handling any circuit card/module to prevent damage by ESD. Extreme care should be taken during the removal and installation of any card/module. After removal, the card/module should be placed on a conductive surface or back into the antistatic container in which it was shipped.
3-54 SEP 2009

Figure 3-12: CSM MMI Terminal Connection
CSM CARD SHOWN REMOVED FROM FRAME
MMI SERIAL PORT REFERENCE OSCILLATOR
EVEN SECOND TICK TEST POINT REFERENCE GPS RECEIVER ANTENNA INPUT LED (SEE NOTE) ANTENNA COAX CABLE GPS RECEIVER 9PIN TO 9PIN RS232 CABLE 19.6 MHZ TEST POINT REFERENCE NULL MODEM BOARD (TRN9666A)
FW00372
LMF COMPUTER PLATFORM
DB9TODB25 ADAPTER
COM1
RS232 SERIAL MODEM CABLE
NOTE 1. For card state LED indications, see Table 3-18 and Figure 3-11 in this section. 2. MMI connection can also be made using locally fabricated MMI cable. See Appendix K.
GPS and HSO/MSO/QHSO Initialization/Verification
Prerequisites Ensure the following prerequisites have been met before proceeding:
S The LMF is not logged into the BTS. S The primary CSM and HSO, MSO, or QHSO (if equipped) has been
warmed up for at least 15 minutes. S The LMF computer serial port (COM1) is connected to the MMI port of the primary CSM as shown in Figure 3-12.

S An MMI communication session has been started, and the CSM>
prompt is present in the HyperTerminal window (Table 3-19). Follow the steps outlined in Table 3-20 to initialize and verify proper GPS receiver functioning. Table 3-20: GPS and HSO/MSO/QHSO Initialization/Verification Step Action To verify that Clock alarms (0000), Dpll is locked and has a reference source, and GPS self test passed messages are displayed within the report, issue the following MMI command bstatus The system will display a response similar to the following:
Clock Alarms (0000): DPLL is locked and has a reference source. GPS receiver self test result: passed Time since reset 0:33:11, time since power on: 0:33:11
Verify the following GPS information (underlined text above): GPS information is usually the 0 reference source. At least one Primary source must indicate Status = good and Valid = yes to bring site up. table continued on next page
3-56
SEP 2009
Table 3-20: GPS and HSO/MSO/QHSO Initialization/Verification Step 3 gstatus The CSM will provide a response similar to the following:
0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 (GPS) 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 0:25:54 GPS Receiver Control Task State: tracking satellites. Frame type (0): master. Recent Change Data: GPS time offset 0 ns. Initial position: lat 151681457 msec, lon 316796711 msec, height 20647 cm Initial position accuracy (0): estimated. GPS Receiver Status: Position hold: lat 123204234 msec, lon 280481015 msec, hgt 1584 cm Current position: lat 123204233 msec, lon 280481014 msec, hgt 1584 cm (GPS) 8 satellites tracked, receiving 8 satellites, 11 satellites visible. Current Dilution of Precision (PDOP or HDOP): 0. Date & Time: 2005:01:31:20:50:18 LS:13 Cached LS:13 GPS Receiver Status Byte:0x08 Chan:0, SVID: 2, Mode: 8, RSSI: 49, Status: 0xa2 Chan:1, SVID: 10, Mode: 8, RSSI: 47, Status: 0xa2 Chan:2, SVID: 17, Mode: 8, RSSI: 47, Status: 0xa2 Chan:3, SVID: 4, Mode: 8, RSSI: 43, Status: 0xa2 Chan:4, SVID: 5, Mode: 8, RSSI: 45, Status: 0xa2 Chan:5, SVID: 24, Mode: 8, RSSI: 44, Status: 0xa2 Chan:6, SVID: 30, Mode: 8, RSSI: 43, Status: 0xa2 Chan:7, SVID: 7, Mode: 8, RSSI: 40, Status: 0xa2 GPS Receiver Identification: COPYRIGHT 20002003 NAVMAN LTD. SFTW P/N # 0000 SOFTWARE VER # 93 SOFTWARE REV # 07 SOFTWARE DATE 09/04/2003 MODEL # R01 HDWR P/N # TU60D125 SERIAL # 1103108952 MANUFACTUR DATE 111//02030 OPTIONS LIST 5843 The receiver has 8 channels and is equipped with TRAIM.
Action Enter the following command at the CSM> prompt to verify that the GPS receiver is in tracking mode.
Verify the following GPS information (shown above in underlined text): At least 4 satellites are tracked, and 4 satellites are visible. GPS Receiver Control Task State is tracking satellites. Do not continue until this occurs! Record the following: Current position latitude and longitude in the displayed milliseconds format Current position height in the displayed cm units table continued on next page
SEP 2009
3-57
Table 3-20: GPS and HSO/MSO/QHSO Initialization/Verification Step 5 If steps 1 through 4 pass, the GPS is good. Action
NOTE 3
If any of the above mentioned areas fail, verify that: If Initial position accuracy is estimated (typical), at least 4 satellites must be tracked and visible (1 satellite must be tracked and visible if actual lat, log, and height data for this site has been entered into NEC file). If Initial position accuracy is surveyed, position data currently in the NEC file is assumed to be accurate. GPS will not automatically survey and update its position. The GPS antenna is not obstructed or misaligned. GPS antenna connector center conductor measures approximately +5 Vdc with respect to the shield. There is no more than 10dB signal loss (@ 1.575GHz) between the GPS antenna and BTS RF modem frame I/O connection. The total GPS antenna system noise figure (including all preamplifiers, cable losses, splitters) is less than 4.0dB. Any lightning protection installed between GPS antenna and BTS frame is installed correctly. table continued on next page
3-58
SEP 2009
Table 3-20: GPS and HSO/MSO/QHSO Initialization/Verification Step 6 Action Enter the following command at the CSM> prompt to display the current status of the GPS receiver and, depending on how the BTS is equipped, the LFR (loran receiver), the HSO, or the MSO backup timing source: sources When equipped with LFR, the system will generate a response similar to the following:
N Source Name Type TO Good Status Last Phase Target Phase Valid 0 LocalGPS Primary 4 YES Good 0 0 Yes 1 LFR CHA Secondary 4 YES Good 2013177 2013177 Yes 2 Not Used Current reference source number: 0
When equipped with HSO or MSO, the system will generate a response similar to the following:
Num Source Name Type TO Good Status Last Phase Target Phase Valid 0 Local GPS Primary 4 Yes Good 3 0 Yes 1 HSO Backup 4 No N/A timedout* Timedout* No
NOTE
HSO will be displayed in the CSM MMI responses when either and HSO or an MSO is installed. Timedout should only be displayed while the HSO or MSO is warming up. If an HSO or MSO is installed and HSO does not appear as one of the sources, configure the HSO or MSO as a backup source by entering the following command at the CSM> prompt:
ss 1 12
After a maximum of 15 minutes, the HSO or MSO should reach operational temperature. This will be indicated by the HSO or MSO front panel LED changing to green. After the HSO or MSO front panel LED has changed to green, enter sources <cr> at the CSM> prompt. Verify that the HSO or MSO is now receiving valid clock pulses as indicated by a numeric value (not timedout) in the Last Phase column as shown below. A valid HSO or MSO is indicated by Yes in the Valid column of the sources response below.
Num Source Name Type TO Good Status Last Phase Target Phase Valid 0 Local GPS Primary 4 Yes Good 3 0 Yes 1 HSO Backup 4 Yes N/A xxxxxxxxxx xxxxxxxxxx Yes
NOTE
The time required for an MSO to become a valid reference source can range from 8 hours for a newly installed module to less than 1 hour for modules that have been in operation for several days. table continued on next page
SEP 2009
3-59
Table 3-20: GPS and HSO/MSO/QHSO Initialization/Verification Step 7 Action HSO, MSO, or QHSO information (underlined text in step 6, above, read from left to right) is usually the #1 reference source. If this is not the case, have the OMCR determine the correct BTS timing source has been identified in the database by entering the display bts csmgen command and correct as required using the edit csm csmgen refsrc command.
NOTE
If any of the above areas fail, verify: If LED is RED, verify that HSO/MSO/QHSO had been powered up for at least 5 minutes. After oscillator temperature is stable, LED should change to GREEN Wait for this to occur before continuing ! If timed out is displayed in the Last Phase column, suspect the HSO/MSO/QHSO output buffer or oscillator is defective Verify the HSO/MSO/QHSO is FULLY SEATED and card extractor levers are LOCKED to prevent possible card warpage 8 Enter the following commands at the CSM> prompt to verify that the CSM is warmed up and that GPS acquisition has taken place. debug dpllp Observe the following typical response if the CSM is not warmed up (15 minutes from application of power) (If warmedup proceed to step 9)
CSM>DPLL Task Wait. 884 seconds left. DPLL Task Wait. 882 seconds left. DPLL Task Wait. 880 seconds left. ...........etc.
NOTE
The warm command can be issued at the MMI port used to force the CSM into warmup, but the reference oscillator will be unstable. 9 Observe the following typical response if the CSM is warmed up.
c:17486 c:17486 c:17470 c:17486 c:17470 c:17470 off: off: off: off: off: off: 11, 11, 11, 11, 11, 11, 3, 3, 1, 3, 1, 1, 6 6 6 6 6 6 TK TK TK TK TK TK SRC:0 SRC:0 SRC:0 SRC:0 SRC:0 SRC:0 S0: S0: S0: S0: S0: S0: 3 3 1 3 1 1 S1:2013175,2013175 S1:2013175,2013175 S1:2013175,2013175 S1:2013175,2013175 S1:2013175,2013175 S1:2013175,2013175
10
Verify the following GPS information (underlined text above, from left to right): Lower limit offset from tracked source variable is not less than 60 (equates to 3s limit). Upper limit offset from tracked source variable is not more than +60 (equates to 3s limit). TK SRC: 0 is selected, where SRC 0 = GPS. Enter the following commands at the CSM> prompt to exit the debug mode display. debug dpllp
11
3-60
SEP 2009

Loran Initialization/Verification
Table 3-21: Loran Initialization/Verification Step 1 Action At the CSM> prompt, enter lstatus <cr> to verify that the LFR is in tracking mode. A typical response is:
CSM> lstatus <cr> LFR Station Status: Stat s Clock coherence: 512 5930M 51/60 dB 0 S/N 5930X 52/64 dn 1 S/N 5990 47/55 dB 6 S/N 7980M 62/66 dB 10 S/N 7980W 65/69 dB 14 S/N 7980X 48/54 dB 4 S/N 7980Y 46/58 dB 8 S/N 7980Z 60/67 dB 8 S/N 8290M 50/65 dB 0 S/N 8290W 73/79 dB 20 S/N 8290W 58/61 dB 6 S/N 8970M 89/95 dB 29 S/N 8970W 62/66 dB 10 S/N 8970X 73/79 dB 22 S/N 8970Y 73/79 dB 19 S/N 8970Z 62/65 dB 10 S/N 9610M 62/65 dB 10 S/N 9610V 58/61 dB 8 S/N 9610W 47/49 dB 4 S/N 9610X 46/57 dB 5 S/N 9610Y 48/54 dB 5 S/N 9610Z 65/69 dB 12 S/N 9940M 50/53 / dB 1 S/N / 9940W 49/56 dB 4 S/N 9940Y 46/50 dB10 S/N 9960M 73/79 dB 22 S/N 9960W 51/60 dB 0 S/N 9960X 51/63 dB 1 S/N 9960Y 59/67 dB 8 S/N 9960Z 89/96 dB 29 S/N
Note
Flag: Flag: Flag: Flag: Flag: . PLL Station . Flag: Flag:E Flag: Flag: Flag: Flag: Flag: Flag: Flag: Flag: Flag: Flag: Flag: Flag:E Flag:E Flag:E Flag: g Flag:S Flag:E Flag:E Flag: Flag: Flag: Flag: Flag:
> This must be greater
than 100 before LFR becomes a valid source.
> This shows the LFR is
locked to the selected PLL station.
LFR Task State: lfr locked to station 7980W LFR Recent Change Data: Search List: 5930 5990 7980 8290 8970 9940 9610 9960 PLL GRI: 7980W LFR Master, reset not needed, not the reference source. CSM>
This search list and PLL data must match the > configuration for the geographical location of the cell site.
SEP 2009
3-61
Table 3-21: Loran Initialization/Verification Step 2 Action Note Verify the following LFR information (highlighted above in boldface type): Locate the dot that indicates the current phase locked station assignment (assigned by MM). Verify that the station call letters are as specified in site documentation as well as M X Y Z assignment. Verify the S/N ratio of the phase locked station is greater than 8. At the CSM> prompt, enter sources <cr> to display the current status of the the loran receiver. Observe the following typical response.
Num Source Name Type TO Good Status Last Phase Target Phase Valid 0 Local GPS Primary 4 Yes Good 3 0 Yes 1 LFR ch A Secondary 4 Yes Good 2013177 2013177 Yes 2 Not used Current reference source number: 1
3
3
NOTE
Timedout should only be displayed while the LFR is warming up. NotPresent or Faulty should not be displayed. If the LFR does not appear as one of the sources, then configure the LFR as a backup source by entering the following command at the CSM> prompt:
ss 1 2
Loran LFR information (highlighted above in boldface type) is usually the #1 reference source (verified from left to right).
NOTE
1. If any of the above mentioned areas fail, verify: The LFR antenna is not obstructed or misaligned. The antenna preamplifier power and calibration twisted pair connections are intact and < 91.4 m (300 ft) in length. A dependable connection to suitable Earth Ground is in place. The search list and PLL station for cellsite location are correctly configured . 2. LFR functionality should be verified using the source command (as shown in Step 3). Use the underlined responses on the LFR row to validate correct LFR operation. 5 Close the hyperterminal window.
3-62
SEP 2009
Test Equipment Set Up Test Equipment Set Up

Connecting Test Equipment to the BTS
The following equipment is required to perform optimization:
S S S S S S S
LMF Communications system analyzer model supported by the LMF Nonradiating transmit line termination load Directional coupler and inline attenuator RF cables and connectors Null modem cable (see Figure 1-1) GPIB interface box
Refer to Table 3-22, Table 3-23 and Table 3-24 for an overview of connections for test equipment currently supported by the LMF. In addition, see the following figures:
S Figure 3-13, Figure 3-14, Figure 3-15, and Figure 3-16 show the test
set connections for TX calibration. optimization/ATP testing.
S Figure 3-17 shows the test set connections for IS95A/B S Figure 3-18, Figure 3-19, Figure 3-20, and Figure 3-21 show test set S Figure 3-22, Figure 3-23, and Figure 3-24 show alternate test set
setups for externally mounted directional couplers.
Test Equipment GPIB Address Settings
connections for IS95 A/B and CDMA 2000 optimization/ATP tests.
All test equipment except the Agilent E7495A and Anritsu MT8212B is controlled by the LMF through an IEEE488/GPIB bus. To communicate on the bus, each piece of test equipment must have a GPIB address set which the LMF will recognize. The standard address settings used by the LMF for the various types of test equipment items are as follows:
S Signal generator address: 1 S Power meter address: 13 S Communications system analyzer: 18

Using the procedures included in the Setting GPIB Addresses section of Appendix F, verify and, if necessary, change the GPIB address of each piece of test equipment used to match the above
.
SEP 2009
3-63
Test Equipment Set Up

Supported Test Equipment
continued
CAUTION To prevent damage to the test equipment, all TX test connections must be through the directional coupler and in-line attenuator as shown in the test setup illustrations.
IS95 A/B Testing Optimization and ATP testing for IS95A/B may be performed using one of the following test sets:
S Agilent 8935 series E6380A communications test set (formerly HP

8935) with option 200 or R2K
S Advantest R3465 and Gigatronics Power Meter

The equipment as listed above cannot be used for CDMA 2000 testing. CDMA 2000 Testing NOTE IS95 C is the same as CDMA 2000. Optimization and ATP testing for IS95A/B and CDMA2000 1X sites or carriers may be performed using the following test equipment:
S Advantest R3267 Analyzer with Advantest R3562 Signal Generator S Agilent E4406A with E4438C Signal Generator S Agilent 8935 series E6380A communications test set (formerly HP S Agilent E7495A and Agilent E7495B communications test sets S Anritsu MT8212B communications test set
8935) with option 200 or R2K and with E4438C signal generator for 1X FER
The E4406A/E4438C pair, or the R3267/R3562 pair, should be connected together using a GPIB cable. In addition, the R3562 and R3267 should be connected with a serial cable from the Serial I/O to the Serial I/O. This test equipment is capable of performing tests in both IS95 A/B mode and CDMA 2000 mode if the required options are installed. Optional test equipment
S Spectrum Analyzer (HP8594E) can be used to perform cable

calibration.
3-64
SEP 2009

Test Equipment Preparation
continued
See Appendix F for specific steps to prepare each type of test set and power meter to perform calibration and ATP. The Agilent E7495A communications test set requires additional setup and preparation. This is described in detail in Appendix F. NOTE Calibration of the communications test set (or equivalent test equipment) must be performed at the site before calibrating the overall test equipment set. Calibrate the test equipment after it has been allowed to warm up and stabilize for a minimum of 60 minutes.
CAUTION If any piece of the the test equipment set (for example, test cable, RF adapter) has been replaced, the test equipment set must be recalibrated. Failure to do so could introduce measurement errors, resulting in incorrect measurement and degredation of system performance.
Test Equipment Connection Charts
To use the following charts to identify necessary test equipment connections, locate the communications system analyzer being used in the COMMUNICATIONS SYSTEM ANALYZER columns, and read down the column. Where a dot appears in the column, connect one end of the test cable to that connector. Follow the horizontal line to locate the end connection(s), reading up the column to identify the appropriate equipment and/or BTS connector. IS95A/Bonly Test Equipment Connections Table 3-22 depicts the interconnection requirements for currently available test equipment supporting IS95A/B only which meets Motorola standards and is supported by the LMF.
SEP 2009
3-65
continued
Table 3-22: IS95A/Bonly Test Equipment Interconnection

COMMUNICATIONS SYSTEM ANALYZER ADDITIONAL TEST EQUIPMENT Attenuator & Directional Coupler
SIGNAL
Advantest R3465
Power Meter
GPIB Interface
LMF
BTS
SYNC MON-ITOR
EVEN SECOND SYNCH
EVEN SEC SYNC IN
19.6608 MHZ CLOCK
CDMA TIME BASE IN
FREQ MONITOR
CONTROL IEEE 488 BUS
GPIB
TX TEST CABLES
INPUT 50W
20 DB BTS ATTEN. PORT
TX16
RX TEST CABLES
RF OUT 50W
RX16
NOTE TX Test cables are set up as follows: TX 13 for 3-sector BTS and TX 16 for 6-sector. RX Test Cables are set up as follows: RX 16 for 3-sector and RX 112 for 6-sector.
3-66
SEP 2009
continued
CDMA2000 1X/IS95A/Bcapable Test Equipment Connections Table 3-23 depicts the interconnection requirements for currently available test equipment supporting both CDMA 2000 1X and IS95A/B which meets Motorola standards and is supported by the LMF. Table 3-23: CDMA2000 1X/IS95A/B Test Equipment Interconnection
COMMUNICATIONS SYSTEM ANALYZER ADDITIONAL TEST EQUIPMENT
SIGNAL
EVEN SECOND SYNCH
Agilent 8935 (Option 200 or R2K)

EXT TRIG IN
Agilent E7495A and E7495B

EVEN SECOND SYNC IN
Advan test R3267

EXT TRIG
Agilent E4406A
TRIGGER IN
Agilent E4438C Signal Generator

PATTERN TRIG IN
Advantest R3562 Signal Generator

EVEN SECOND SYNC IN
Power Meter
GPIB Interface
LMF
30 dB Directional Coupler & 20 dB Pad*
BTS
SYNC MONITOR
19.6608 MHZ CLOCK
MOD TIME BASE IN
EXT REF IN
EXT REF IN
FREQ MONITOR
IEEE 488
GPIB
HPIB
GPIB
HPIB
HPIB
GPIB
SERIAL PORT
10 MHZ
10 MHZ IN
10 MHZ OUT
10 MHZ OUT (SWITCHED)
10 MHZ IN
SYNTHE REF IN
SIGNAL SOURCE CONTROLLED SERIAL I/O TX TEST CABLES RF IN/OUT PORT 2 RF IN
SERIAL I/O
SERIAL I/O
RF IN
RF INPUT 50 OHM
RF OUTPUT 50 OHM
RF IN/OUT
30 DB COUPLER AND 20 DB PAD
TX16
RX TEST CABLES
DUPLEX OUT *
PORT 1 RF OUT
RF OUT 50OHM
RF OUT ONLY
RF OUTPUT 50OHM
RF OUT 50 OHM
RX16
* WHEN USED ALONE, THE AGILENT 8935 WITH OPTION 200 OR R2K SUPPORTS IS95A/B RX TESTING BUT NOT CDMA2000 1X RX TESTING.
SEP 2009
3-67
continued
Table 3-24: Additional CDMA2000 1X/IS95A/B Test Equipment Interconnection

COMMUNICATIONS SYSTEM ANALYZER ADDITIONAL TEST EQUIPMENT 30 dB Directional Coupler & Inline Attenuator
SIGNAL
EVEN SECOND SYNCH
Anritsu MT8212B
EXTERNAL FREQ REF / EXT TRIGGER
Power Meter
GPIB Interface
LMF
BTS
SYNC MONITOR
19.6608 MHZ CLOCK
CDMA TIMING INPUT
FREQ MONITOR
CONTROL SERIAL BUS
SERIAL INTERFACE
SERIAL PORT
10 MHZ
SIGNAL SOURCE CONTROLLED SERIAL I/O
TX TEST CABLES
RF IN 50 W
30 DB COUPLER AND MINIMUM OF 10 DB PAD
TX16
RX TEST CABLES
RF OUT 50 W
30 DB COUPLER AND MINIMUM OF 35 DB PAD
RX16
Equipment Warm-up
Warm-up BTS equipment for a minimum of 60 minutes before performing the BTS optimization procedure. This assures BTS site stability and contributes to optimization accuracy.
continued
NOTE Time spent running initial power-up, hardware/firmware audit, and BTS download counts as test equipment warm-up time.
WARNING Before installing any test equipment directly to any BTS TX OUT connector, verify there are NO CDMA BBX channels keyed. At active sites, have the OMC-R place the antenna (sector) assigned to the PA under test OOS. Failure to do so can result in serious personal injury and/or equipment damage.
Automatic Cable Calibration Setup
Refer to Table 3-38 in the Calibrate Test Cabling Using Communications System Analyzer section of this chapter for automatic cable calibration procedures using a communications test set.
Manual Cable Calibration
If manual cable calibration is required, refer to Table 3-39 and Table 3-40 in the Calibrate Test Cabling Using Signal Generator and Spectrum Analyzer section of this chapter for procedures to use a spectrum analyzer and signal generator. An additional manual cable calibration procedure is available using the using the Advantest R3465 communications system analyzer. Refer to the Cable Calibration with R3465 Test Set section of Appendix F.
SEP 2009
3-69

Set-up for TX Calibration
continued
Figure 3-13, Figure 3-14, Figure 3-15, and Figure 3-16 show the test set connections for TX calibration.
Figure 3-13: TX Calibration Test Setup Agilent 8935 (IS95A/B & CDMA2000 1X)
TEST SETS
AGILENT 8935 SERIES E6380A (FORMERLY HP 8935)
HPIB TO GPIB BOX
TRANSMIT (TX) SET UP

100WATT (MIN) NONRADIATING RF LOAD POWER SENSOR TX TEST CABLE OUT TEST SET INPUT/ OUTPUT PORTS OR 10 DB MINIMUM INLINE ATTENUATOR TX TEST IN CABLE COMMUNICATION SYSTEM ANALYZER POWER METER (OPTIONAL)*

RF IN/OUT
50 TERM.
30 DB DIRECTIONAL COUPLER
CONTROL IEEE 488 GPIB BUS
* A POWER METER CAN BE USED IN PLACE OF THE COMMUNICATIONS TEST SET FOR TX CALIBRATION/AUDIT
TX TEST CABLE
GPIB CABLE
TX ANTENNA PORT OR CRMS PROBE OR RFDS TX DIRECTIONAL COUPLER ANTENNA PORT
DIP SWITCH SETTINGS
S MODE DATA FORMAT BAUD RATE
ON
ADVANTEST MODEL R3465
BTS
GPIB ADRS LAN B RS232GPIB INTERFACE BOX RS232 NULL MODEM CABLE G MODE LAN A
10BASET/ 10BASE2 CONVERTER GPIB CONNECTS TO BACK OF UNIT INPUT 50OHM
CDMA LMF
INTERNAL OR PCMCIA ETHERNET NETWORK INTERFACE CARD (NIC)
3-70
SEP 2009
continued
Figure 3-14: TX Calibration Test Setup Agilent E4406A and Advantest R3567 (IS95A/B and CDMA2000 1X)
TEST SETS
AGILENT E4406A
100WATT (MIN) NONRADIATING RF LOAD

POWER SENSOR TX TEST CABLE OUT 30 DB DIRECTIONAL COUPLER 50 TERM. OR 1O DB MINIMUM INLINE ATTENUATOR TX TEST CABLE TX TEST CABLE IN TEST SET INPUT/ OUTPUT PORTS COMMUNICATION SYSTEM ANALYZER POWER METER (OPTIONAL)*
CONTROL IEEE 488 GPIB BUS
RF INPUT 50 ADVANTEST MODEL R3267
* A POWER METER CAN BE USED IN PLACE OF THE COMMUNICATIONS TEST SET FOR TX CALIBRATION/AUDIT
GPIB CABLE
RF IN
DIP SWITCH SETTINGS
ON
BTS
GPIB ADRS LAN B LAN A RS232GPIB INTERFACE BOX RS232 NULL MODEM CABLE G MODE
10BASET/ 10BASE2 CONVERTER
CDMA LMF
SEP 2009
3-71
continued
Figure 3-15: TX Calibration Test Setup Agilent E7495A (IS95A/B & CDMA2000 1X)
TEST SETS
AGILENT E7495A

POWER SENSOR TX TEST CABLE POWER METER
PORT 1 RF OUT COMMUNICATIONS SYSTEM ANALYZER
100WATT (MIN.) NONRADIATING RF LOAD
OR TX TEST CABLE
PORT 2 RF IN
INTERNAL ETHERNET CARD
50 TERM.
1O DB MINIMUM INLINE ATTENUATOR

GPIO Power REF 50 MHz Ext Ref In Use only Agilent supplied power adapter
TX TEST CABLE
Port 2 RF In
Serial 1 Sensor
Even Second Sync In
Port 1 RF Out / SWR
Serial 2
GPS Antenna
RX ANTENNA PORT OR CRMS PROBE OR RFDS TX DIRECTIONAL COUPLER ANTENNA PORT
ETHERNET HUB
PORT 2 RF IN
SYNC MONITOR EVEN SEC TICK PULSE REFERENCE FROM CSM BOARD
BTS
SYNC MONITOR
NOTES: 1. WHEN USING THE E7495A, TX TESTS REQUIRE A MINIMUM OF 30 DB ATTENUATION PLUS THE CABLE LOSSES. 2. IF BTS IS EQUIPPED WITH DRDCS (DUPLEXED RX/TX SIGNALS), CONNECT THE TX TEST CABLE TO THE DRDC ANTENNA CONNECTOR.
LAN A
CSM
LAN B
CDMA LMF
INTERNAL OR PCMCIA ETHERNET NETWORK INTERFACE CARD (NIC) ticdma05736.eps
3-72
SEP 2009
continued
Figure 3-16: TX Calibration Test Setup Anritsu MT8212B (IS95A/B and CDMA2000 1X)
TEST SETS
ANRITSU MT8212B
RF OUT 50 COMMUNICATIONS SYSTEM ANALYZER 100WATT (MIN.) NONRADIATING RF LOAD SERIAL INTERFACE CONNECTOR RF IN 50 TX AND RX TEST CABLE RF IN 50 SERIAL INTERFACE
50 TERM.
1O DB MINIMUM INLINE ATTENUATOR TX AND RX TEST CABLE RX ANTENNA PORT OR CRMS PROBE OR RFDS TX DIRECTIONAL COUPLER ANTENNA PORT TX ANTENNA PORT OR CRMS PROBE OR RFDS TX DIRECTIONAL COUPLER ANTENNA PORT RS232 SERIAL INTERFACE CABLE
BTS
FREQ MONITOR
SYNC MONITOR CSM
LAN A
LAN B
10BASET/ 10BASE2 CONVERTER UNSHIELDED TWISTED PAIR (UTP) CABLE (RJ45 CONNECTORS)
CDMA LMF
SEP 2009
3-73

Setup for Optimization/ATP
continued
Figure 3-17 shows test set connections for IS95 A/B optimization/ATP tests. Figure 3-18, Figure 3-19, Figure 3-20, and Figure 3-21 show test set connections for IS95 A/B and CDMA 2000 optimization/ATP tests. Figure 3-17: ATP Test Setup IS95A/B (Agilent 8935)
TEST SETS
AGILENT 8935 SERIES E6380A (FORMERLY HP 8935)
SYNC MONITOR EVEN SEC TICK PULSE REFERENCE FROM CSM BOARD FREQ MONITOR 19.6608 MHZ CLOCK REFERENCE FROM CSM BOARD
OPTIMIZATION/ATP SET UP
HPIB TO GPIB BOX RX TEST CABLE
OUT
COMMUNICATIONS SYSTEM ANALYZER EVEN SECOND/SYNC IN
CDMA TEST SET TIMEBASE INPUT/ IN OUTPUT PORTS IN
IEEE 488 GPIB BUS 50 TERM.
DUPLEX OUT
RF IN/OUT 30 DB DIRECTIONAL COUPLER
Motorola CyberTest
10 DB MINIMUM INLINE ATTENUATOR

Advantest Model R3465
SYNC MONITOR EVEN SEC TICK PULSE REFERENCE FROM CSM BOARD BNC T
TX TEST CABLE
RF IN/OUT
RF OUT
RX ANTENNA PORT TX ANTENNA PORT OR CRMS PROBE OR CRMS PROBE OR RFDS TX OR RFDS TX DIRECTIONAL DIRECTIONAL COUPLER COUPLER ANTENNA PORT ANTENNA PORT
NOTE: The Directional Coupler is not used with the Cybertest Test Set. The TX cable is connected directly to the Cybertest Test set.
BTS
FREQ MONITOR SYNC MONITOR LAN B LAN A CSM
DIP SWITCH SETTINGS
ON
FREQ MONITOR 19.6608 MHZ CLOCK REFERENCE FROM CSM BOARD
GPIB ADRS RS232GPIB INTERFACE BOX
G MODE
RF OUT 50
RS232 NULL MODEM CABLE
GPIB CONNECTS TO BACK OF UNIT INPUT 50 TO EXT TRIGGER CONNECTOR ON REAR OF TEST SET UNSHIELDED TWISTED PAIR (UTP) CABLE (RJ45 CONNECTORS)
CDMA LMF
3-74
SEP 2009
continued
Figure 3-18: ATP Test Setup IS95A/B and CDMA2000 1X (Agilent E4438C/8935 and Agilent E4438C/E4406A)
TEST SETS
AGILENT E4438C (TOP) AND 8935 SERIES E6380A (BOTTOM)
RX TEST CABLE
RF OUTPUT 50
SIGNAL GENERATOR PATTERN TRIG IN
RF OUTPUT 50
10 MHZ IN GPIB 10 MHZ REF OUT OR 10 MHZ OUT HPIB OR GPIB

RF IN/OUT BNC T SYNC MONITOR EVEN SEC TICK PULSE REFERENCE FROM CSM BOARD FREQ MONITOR 19.6608 MHZ CLOCK REFERENCE FROM CSM BOARD 50 TERM. NOTES: 10 MHZ IN ON REAR OF SIGNAL GENERATOR IS CONNECTED TO 10 MHZ REF OUT ON SIDE OF CDMA BASE STATION TEST SET PATTERN TRIG IN ON REAR OF SIGNAL GENERATOR IS CONNECTED TO EVEN SECOND SYNC IN ON SIDE OF CDMA BASE STATION TEST SET.
RF IN/OUT OR RF INPUT 50 100WATT (MIN.) NONRADIATING RF LOAD TX TEST CABLE
COMMUNICATIONS SYSTEM ANALYZER EXT REF IN TRIGGER IN OR EVEN SEC SYNCH IN
BNC T 1O DB MINIMUM INLINE ATTENUATOR
TX TEST CABLE
AGILENT E4438C (TOP) AND E4406A (BOTTOM)
RF OUTPUT 50
GPIB CABLE
* BLACK RECTANGLES REPRESENT THE RAISED PART OF SWITCHES RF INPUT 50
BTS
FREQ MONITOR SYNC MONITOR CSM
DIP SWITCH SETTINGS * S MODE DATA FORMAT BAUD RATE ON
TO PATTERN TRIG IN ON REAR OF SIGNAL GENERATOR BNC T
TO TRIGGER IN ON REAR OF TRANSMITTER TESTER
TO EXT REF IN ON REAR OF TRANSMITTER TESTER
G MODE
LAN B LAN A FREQ MONITOR 19.6608 MHZ CLOCK REFERENCE FROM CSM BOARD
NOTE:
CDM ALMF
10 MHZ IN ON REAR OF SIGNAL GENERATOR IS CONNECTED TO 10 MHZ OUT (SWITCHED) ON REAR OF TRANSMITTER TESTER
INTERNAL PCMCIA ETHERNET NETWORK INTERFACE CARD (NIC)
SEP 2009
3-75
continued
Figure 3-19: ATP Test Setup IS95A/B and CDMA2000 1X (Advantest R3267/3562)
TEST SETS
Advantest R3267 (Top) and R3562 (Bottom)
RX TEST CABLE TO EXT TRIG ON REAR OF SPECTRUM ANALYZER RF OUT 50 SIGNAL GENERATOR MOD TIME BASE IN EXT TRIG IN SYNTHE REF IN GPIB SPECTRUM ANALYZER 100WATT (MIN.) NONRADIATING RF LOAD BNC T
3
INPUT 50 INPUT 50 TX TEST CABLE
10 MHZ OUT
EXT TRIG GPIB
RF OUT 50
50 TERM. 30 DB DIRECTIONAL COUPLER BNC T 1O DB MINIMUM INLINE ATTENUATOR
TX TEST CABLE
NOTE: SYNTHE REF IN ON REAR OF SIGNAL GENERATOR IS CONNECTED TO 10 MHZ REF OUT ON REAR OF SPECTRUM ANALYZER
GPIB CABLE
* BLACK RECTANGLES REPRESENT THE RAISED PART OF SWITCHES
BTS
FREQ MONITOR SYNC MONITOR CSM
DIP SWITCH SETTINGS
ON
G MODE
LAN B LAN A
CDMA LMF
3-76
SEP 2009
continued
Figure 3-20: ATP Test Setup IS95A/B and CDMA2000 1X (Agilent E7495A or E7495B)
TEST SET
AGILENT E7495A or E7495B
ATP TEST SET UP

POWER METER (SEE NOTE FOR RX TEST ATTENUATION SELECTION) RX TEST
PORT 1 RF OUT COMMUNICATIONS SYSTEM ANALYZER PORT 2 RF IN INTERNAL ETHERNET CARD
RF INPUT 50 OR INPUT 50 TX TEST
50 TERM.
NOTE: USE THE SAME CABLE SET FOR TX AND RX ATP. SWITCH THE CABLES DURING ALL ATP TESTS AS SHOWN.
TX TEST: 1O DB MINIMUM INLINE ATTENUATOR

Use only Agilent supplied power adapter
RX TEST
GPIO
Power REF 50 MHz
Ext Ref In
TEST CABLES
Port 2 RF In
Serial 1 Sensor
Even Second Sync In
Port 1 RF Out / SWR
TX TEST
Serial 2
GPS Antenna
PORT 2 RF IN
PORT 1 RF OUT
ETHERNET HUB
NOTE: FOR RX TESTING, TOTAL RF PATH ATTENUATION (CABLES+COUPLERS+ATTENUATORS) MUST BE WITHIN THE FOLLOWING VALUES SPECIFIED FOR EACH TYPE OF TEST SET: E7495A: 25 TO 32 dB E7495B: 10 TO 100 dB 2. WHEN USING THE E7495A, TX TESTS REQUIRE A MINIMUM OF 30 DB ATTENUATION PLUS THE CABLE LOSSES. 3. USE THE SAME CABLE SET FOR TX AND RX ATP. SWITCH THE CABLES DURING ALL ATP TESTS AS SHOWN. 4. IF BTS IS EQUIPPED WITH DUPLEXED RX/TX SIGNALS, CONNECT THE TX TEST CABLE TO THE DUPLEXED ANTENNA CONNECTOR.
LAN A
BTS
SYNC MONITOR CSM LAN B
CDMA LMF
INTERNAL PCMCIA ETHERNET NETWORK INTERFACE CARD (NIC) ticdma05737.eps
SEP 2009
3-77
continued
Figure 3-21: ATP Test Setup IS95A/B and CDMA2000 1X (Anritsu MT8212B)
TEST SET
ANRITSU MT8212B
RX TEST
RF OUT 50 COMMUNICATIONS SYSTEM ANALYZER
RF IN 50
SERIAL INTERFACE
TX TEST
SERIAL INTERFACE CONNECTOR
RF IN 50
RF OUT 50
50 TERM.
TX TEST: 1O DB MINIMUM INLINE ATTENUATOR RX TEST TX TEST RX ANTENNA PORT OR CRMS PROBE OR RFDS TX DIRECTIONAL COUPLER ANTENNA PORT TX ANTENNA PORT OR CRMS PROBE OR RFDS TX DIRECTIONAL COUPLER ANTENNA PORT RX TEST (RSSI): 35 DB MINIMUM INLINE ATTENUATOR
RS232 SERIAL INTERFACE CABLE
BTS
FREQ MONITOR
NOTES: 1. USE THE SAME CABLE SET FOR TX AND RX ATP. SWITCH THE CABLES DURING ATP TESTS AS SHOWN. 2. FOR RX TESTING (RSSI), TOTAL RF PATH ATTENUATION (CABLES+COUPLERS+ATTENUATORS) MUST BE 65 dB OR GREATER.
LAN A SYNC MONITOR CSM
LAN B
10BASET/ 10BASE2 CONVERTER UNSHIELDED TWISTED PAIR (UTP) CABLE (RJ45 CONNECTORS)
CDMA LMF
3-78
SEP 2009
continued
Figure 3-22: Alternate ATP Test Setups (Except Agilent E7495A/B and Anritsu MT8121B)
RX TEST CABLE OUT ANTENNA CABLE REMOVED FOR TESTING 100WATT (MIN.) NONRADIATING RF LOAD TX TEST CABLE TX TEST CABLE 50 TERM. 50 TERM. 50 TERM. 50 TERM. 50 TERM. 1O DB MINIMUM INLINE ATTENUATOR TX TESTING OR TX & RX TESTING DUPLEXED TX/RX ANTENNA CONNECTOR TX TEST CABLE DIRECTIONAL COUPLER (30 DB)
SIGNAL GENERATOR
COMMUNICATIONS SYSTEM ANALYZER
IN
RX TESTING
TX TESTING
REF IN
EVEN SEC IN
OPTIONAL EXTERNAL DIRECTIONAL COUPLERS
RX ANTENNA CONNECTOR
TX ANTENNA CONNECTOR
GPIB CABLE
INTERNAL RX CABLE TO MPC
INTERNALTX CABLE TO PA TRUNKING MODULE
* BLACK RECTANGLES REPRESENT THE RAISED PART OF SWITCHES DIP SWITCH SETTINGS S MODE DATA FORMAT BAUD RATE
ON FREQ MONITOR SYNC MONITOR CSM FREQ MONITOR SYNC MONITOR CSM GPIB ADRS RS232GPIB INTERFACE BOX RS232 NULL MODEM CABLE G MODE
LAN B LAN A LAN A
LAN B
CDMA LMF
BTS WITHOUT DUPLEXED RX &TX PORTS
BTS WITH DUPLEXED RX &TX PORTS
SEP 2009
3-79
continued
Figure 3-23: Alternate ATP Test Setups (Agilent E7495A or E7495B)

POWER METER
(SEE NOTE FOR RX TEST ATTENUATION SELECTION) ANTENNA CABLE REMOVED FOR TESTING 100WATT (MIN.) NONRADIATING RF LOAD TX TEST CABLE IN DIRECTIONAL COUPLER (30 DB)
PORT 1 RF OUT OUT PORT 2 RF IN COMMUNICATIONS SYSTEM ANALYZER INTERNAL ETHERNET NIC
3
RX TESTING TX TESTING
TX TEST CABLE OR 50 TERM.
50 TERM.
50 TERM. 50 TERM. 50 TERM.
TX TEST: 1O DB MINIMUM INLINE ATTENUATOR
OR
TX & RX TESTING DUPLEXED TX/RX ANTENNA CONNECTOR
NOTE: 1. FOR RX TESTING, TOTAL RF PATH ATTENUATION (CABLES+COUPLERS+ATTENUATORS) MUST BE WITHIN THE FOLLOWING VALUES SPECIFIED FOR EACH TYPE OF TEST SET: E7495A: 25 TO 32 dB E7495B: 10 TO 100 dB 2. WHEN USING THE E7495A, TX TESTS REQUIRE A MINIMUM OF 30 DB ATTENUATION PLUS THE CABLE LOSSES.
ETHERNET HUB
LAN B LAN A LAN A
LAN B
CDMA LMF
BTS WITHOUT DUPLEXED RX & TX PORTS
BTS WITH DUPLEXED RX & TX PORTS
3-80
SEP 2009
continued
Figure 3-24: Alternate ATP Test Setups (Anritsu MT8212B)

NOTES: 1. USE THE SAME CABLE SET FOR TX AND RX ATP. SWITCH CABLES DURING ALL ATP TESTS AS SHOWN. 2.FOR RX TESTING (RSSI) TOTAL RF PATH ATTENUATION (CABLES + COUPLERS + ATTENUATORS) MUST BE 65 DB OR GREATER. 100WATT (MIN.) NONRADIATING RF LOAD
ANTENNA CABLE REMOVED FOR TESTING
RF OUT 50 RX TEST OUT RF IN 50 COMMUNICATIONS SYSTEM ANALYZER SERIAL INTERFACE
TX AND RX TEST CABLE OR RX TESTING TX TESTING 50 TERM. DIRECTIONAL COUPLER (30 DB)
IN
TX TEST
50 TERM.
50 TERM. 50 TERM. 50 TERM.
TX TEST: 1O DB MINIMUM INLINE ATTENUATOR RX TEST (RSSI): 35 DB MINIMUM INLINE ATTENUATOR
OR
TX & RX TESTING DUPLEXED TX/RX ANTENNA CONNECTOR
RS232 SERIAL INTERFACE CABLE
LAN B LAN A LAN A
LAN B
CDMA LMF
BTS WITHOUT DUPLEXED RX & TX PORTS
BTS WITH DUPLEXED RX & TX PORTS
SEP 2009
3-81
Test Equipment Connection to the LMF Test Equipment Connection to the LMF
Test Equipment Connection
The LMF computer platform provides two types of hardware interfaces which support three different test equipment communication methods.
S The COM hardware interface (RS232) supports connection with both

the General Purpose Interface Bus (GPIB) and direct serial communication methods. communication method.
S The Ethernet interface supports the network test equipment

Additional information on each interface type is provided in the following subsections. COM Port Interface The LMF computer RS232 serial bus interfaces are designated as COM connections or ports in software. These interfaces support communication with test equipment connected to the LMF computer directly with a serial cable or through a GPIB interface device (GPIB box). The LMF normally uses COM1 for the interface. COM2 is not used unless the LMF computer has two RS232 connectors. The COM port selected in the LMF can not be used for any other purpose when the LMF is using it. Selecting the COM port Perform the following to select a COM port for use with test equipment needing a GPIB or direct serial connection: Table 3-25: Selecting a COM Port for GPIB or Serial Test Equipment Connection Step 1 2 3 4 5 6 Action From the LMF window menu bar select Tools > Options. Result: The LMF Options window opens. If the Test Equipment tab is not in the forefront, click the tab to bring it forward. Click in the COM radio button in the GPIB/COM settings area. Result: A black dot appears in the circle. Select the COM port to use (normally COM1) from the dropdown in the Port: box of the GPIB/COM settings area. Click the Save button to save the selection configuration for future LMF sessions. Click the Close button to close the LMF Options window.
3-82
SEP 2009
Test Equipment Connection to the LMF
continued
Disconnecting and Reconnecting the LMF and the COM port The LMF can be disconnected from the active COM port by using the Disconnect Port button in the GPIB/COM settings area of the Test Equipment tab. Disconnecting the LMF may be needed, for example, to use a HyperTerminal connection for a hardware Man Machine Interface (MMI) communication session. Perform the following to disconnect or reconnect the LMF and the selected COM port. Table 3-26: Disconnect and Reconnect the LMF and the Active COM Port Step 1 2 3 4 5 Action From the LMF window menu bar select Tools > Options. Result: The LMF Options window opens. If the Test Equipment tab is not in the forefront, click the tab to bring it forward. Disconnect the LMF from the active COM port: click the Disconnect Port button in the GPIB/COM settings area. Reconnect the LMF to the active COM port: click the Detect button in the GPIB Test equipment or Serial Test Equipment area. If no other operations are required in the LMF Options window click Close to close the window.
Ethernet Interface The LMF computer Ethernet interface supports communication with test equipment which uses the network connection method. This interface uses Internet Protocol (IP) addressing to differentiate each node on the network. Motorola recommends that Ethernet connection of the test equipment and the LMF computer be done though an Ethernet hub which includes both 10/100BaseT and coaxial 10Base2 connections. The hub connects to the LMF computer, the test equipment and the BTS. Connection details are as follows: Test equipment to hub This is an Unshielded Twisted Pair (UTP) Ethernet cable with two 10/100BaseT 8contact modular connectors. LMF to Hub Use one of the following cables to connect the LMF to the Hub: S Ethernet cable. Be sure the LMF computer Network Interface Card (NIC) is set for either AUTO or to use the 8contact modular connector only. S Coaxial cable between NIC and Hub. Use a 10Base2 (BNC) tee connector on the hub. If the hub does not have BNC connectors, use a BNCtoUTP adapter with the tee connector. Connect a coaxial cable between the LAN card and one end of the BNC tee crossbar. Hub to BTS With a BNC tee connector on the hub, connect a coaxial cable between the open end of the T crossbar and the BTS LAN connection.
Test Equipment Connection to the LMF

Addressing Methods
continued
Different addressing methods are used for test equipment depending on the type of interface connection it has. The different addressing methods are described in the following subsections. GPIB Addresses
GPIB addresses can range from 1 through 30. The LMF will accept any address in that range, but the numbers entered in the LMF Options window GPIB address box must match the addresses set in the test equipment. Motorola recommends using 1 for a CDMA signal generator, 13 for a power meter, and 18 for a communications system analyzer. To verify and, if necessary, change the GPIB addresses of the test equipment, refer to the Setting GPIB Addresses sections of Appendix F. Serial Connection This connection type uses a direct serial connection between the test equipment and the LMF computer platform. The Anritsu MT8212B communications test set is an example of test equipment using this type of connection. There are no specific addressing requirements for this type of interface. IP Addresses Test equipment using the Network connection type use IP addresses to identify them on the Ethernet Local Area Network (LAN). The E7495A and E7495B communications test sets are examples of Network connection test equipment. Setting the IP address in the test equipment is covered in the specific test equipment (for example, Agilent E7495) setup section of Appendix F.
3-84
SEP 2009
Test Equipment Selection Test Equipment Selection

Test Equipment Selection
Test equipment selection is performed in the LMF Options window, accessed through Tools > Options in the LMF window menu bar. The window has four tabs covering different categories of options. Test equipment operations, including selection, are performed on the Test Equipment tab. For software release 2.20.0.x (R20), the test equipment list displayed on this tab is context sensitive based on the Connection type selected. S When GPIB is selected, only test equipment with a GPIB interface is displayed.
S When Serial is selected, only test equipment needing a direct serial

connection is displayed. connection is displayed.
S When Network is selected, only test equipment needing an Ethernet

Manual and Autodetect Selection
Test equipment can be manually specified before or after the test equipment is connected. The LMF does not try to determine if the test equipment is actually connected for manual selection. The LMF can be commanded to automatically detect test equipment connected to it. This autodetection feature is operated by a Detect button located in the test equipment list area for each connection type (GPIB, Serial, or Network).
Selecting Test Equipment
There is a different set of test equipment selection procedures for each test equipment connection type. These are:
S GPIB connection S Serial connection S Network (Ethernet) connection

Selection Procedures
Test equipment selection procedures are contained in the following subsections. Each subsection is for a different connection type. Each subsection includes a procedure for manually specifying test equipment items and a procedure to have the LMF automatically detect the connected test equipment. GPIB Interface Test Equipment Manual Selection and Autodetection Prerequisites The following must be done before performing these procedures:
S LMF computer and test equipment are both correctly connected to the
GPIB box
continued
S Test equipment is turned on S GPIB addresses set in the test equipment have been verified as correct
using the applicable procedures in Appendix F.
Manual selection Test equipment may be selected manually even if it is not connected to the LMF.
3
Step 1 2 3 4 5 6 7
Table 3-27: Manually Selecting Test Equipment GPIB Interface Action In the LMF menu bar, select Tools > Options. Result: The LMF Options window appears. Click on the Test Equipment tab (if not in the forefront). Click the GPIB radio button in the Connection Type area. Result: A black dot appears in the circle. Click the COM radio button in the GPIB/COM settings area. Result: A black dot appears in the circle. Select the correct LMF computer serial port from the Port: pick list (normally COM1) (Refer to the Test Equipment Connection to the LMF section of this chapter). In the GPIB Test equipment area click the checkbox(es) of the test equipment being used. Result: Checkmarks appear in the boxes clicked on. If one is not already displayed, type the GPIB address for each checked piece of test equipment in the corresponding box labeled GPIB. Recommended Addresses 1 = CDMA Signal generator 13 = Power Meter 18 = CDMA Analyzer
NOTE
When the test equipment items are manually selected, the CDMA analyzer is used only if a power meter is not selected. 8 9 Click the Apply button. The button will darken until the selection is committed. Click the Detect on startup checkbox in the Autodetection settings area to allow the LMF to detect the test equipment automatically on application startup. Result: A checkmark appears in the box. Click the Save button to save the selection configuration for future LMF sessions. Click the Close button to close the LMF Options window.
10 11
NOTE
When two devices of the same type have been selected, a window will appear warning that more than one signal generator/power meter/ analyzer has been chosen. Click the Continue button to close this window. The checkbox can be clicked to prevent the window from being displayed again, if desired.
3-86
SEP 2009
continued
Automatically Selecting Test Equipment (Autodetection) When using the autodetection feature to select test equipment, the LMF determines which test equipment items are actually communicating with the LMF. Table 3-28: Autodetecting Test Equipment GPIB Interface Step 1 2 3 4 5 6 In the LMF menu bar, select Tools > Options. Result: The LMF Options window appears. Click on the Test Equipment tab (if not in the forefront). Click the GPIB radio button in the Connection Type area. Result: A black dot appears in the circle. Click the COM radio button in the GPIB/COM settings area. Result: A black dot appears in the circle. Select the correct LMF computer serial port from the Port: pick list (normally COM1) (Refer to the Test Equipment Connection to the LMF section of this chapter). If they are not already displayed, enter the GPIB address for each piece of required test equipment, separated by commas, in the GPIB Addresses: box in the GPIB Test equipment area. Recommended Addresses 1 = CDMA Signal generator 13 = Power Meter 18 = CDMA Analyzer In autodetection when both a power meter and a CDMA analyzer are selected, the LMF uses the first item that is capable of performing RF power measurement listed in the GPIB Addresses: box. The address for a CDMA signal generator is normally 1, the address for a power meter is normally 13, and the address for a CDMA analyzer is normally 18. If 1,13,18 is listed in the GPIB Addresses: box, the power meter (13) is used for RF power measurements. When the test equipment items are manually selected, the CDMA analyzer is used only if a power meter is not selected. 7 Click the Detect button. The button will darken until the selection is committed. Result: For each detected equipment item, a check will appear in its checkbox and its GPIB address will appear in its GPIB box. Click the Detect on startup checkbox in the Autodetection settings area to allow the LMF to detect the test equipment automatically on application startup. Result: A checkmark appears in the box. Click the Save button to save the selection configuration for future LMF sessions. Click the Close button to close the LMF Options window. Action
NOTE
9 10
NOTE
When two devices of the same type have been selected, a window will appear warning that more than one signal generator/power meter/ analyzer has been chosen. Click the Continue button to close this window. The checkbox can be clicked to prevent the window from being displayed again, if desired.
SEP 2009
3-87
continued
Serial Interface Test Equipment Manual Selection and Autodetection Prerequisites The following must be done before performing these procedures:
S Test equipment is correctly connected to the LMF computer RS232

connector with a serial cable
S Test equipment is turned on

Manual selection Test equipment may be selected manually even if it is not connected to the LMF. Table 3-29: Manually Selecting Test Equipment Serial Interface Step 1 2 3 4 5 6 7 8 In the LMF menu bar, select Tools > Options. Result: The LMF Options window appears. Click on the Test Equipment tab (if not in the forefront). Click the Serial radio button in the Connection Type area. Result: A black dot appears in the circle. Click the COM radio button in the GPIB/COM settings area. Result: A black dot appears in the circle. Select the correct LMF computer serial port from the Port: pick list (normally COM1) (Refer to the Test Equipment Connection to the LMF section of this chapter). In the Serial Test equipment area click the checkbox(es) of the test equipment being used. Result: Checkmarks appear in the box(es) clicked on. Click the Apply button. The button will darken until the selection is committed. Click the Detect on startup checkbox in the Autodetection settings area to allow the LMF to detect the test equipment automatically on application startup. Result: A checkmark appears in the box. Click the Save button to save the selection configuration for future LMF sessions. Click the Close button to close the LMF Options window. Action
9 10
Automatically Selecting Test Equipment (Autodetection) When using the autodetection feature to select test equipment, the LMF
3-88
SEP 2009
continued
determines which test equipment items are actually communicating with the LMF. Table 3-30: Autodetecting Test Equipment Serial Interface Step 1 2 3 4 5 6 7 8 In the LMF menu bar, select Tools > Options. Result: The LMF Options window appears. Click on the Test Equipment tab (if not in the forefront). Click the Serial radio button in the Connection Type area. Result: A black dot appears in the circle. Click the COM radio button in the GPIB/COM settings area. Result: A black dot appears in the circle. Select the correct LMF computer serial port from the Port: pick list (normally COM1) (Refer to the Test Equipment Connection to the LMF section of this chapter). Choose the test equipment on the Serial Test Equipment list by clicking the corresponding checkbox. Result: A checkmark appears in the box. Click the Detect button. The button will darken until the selection is committed. Result: For each detected equipment item, a check will appear in its checkbox. Click the Detect on startup checkbox in the Autodetection settings area to allow the LMF to detect the test equipment automatically on application startup. Result: A checkmark appears in the box. Click the Save button to save the selection configuration for future LMF sessions. Click the Close button to close the LMF Options window. Action
9 10
Network Interface Test Equipment Manual Selection and Autodetection Prerequisites The following must be done before performing these procedures:
S Be sure that no other equipment is connected to the LMF. S Test equipment is correctly connected to the LMF computer through
the Ethernet LAN
S The IP address is set in the test equipment as specified in the test S Test equipment is turned on
equipment model (for example, Agilent E7495) setup section of Appendix F.
S TURN OFF any firewall software installed on the LMF computer

platform
continued
Manual selection Test equipment may be selected manually even if it is not connected to the LMF. Table 3-31: Manually Selecting Test Equipment Network Interface Step 1 In the LMF menu bar, select Tools > Options. Result: The LMF Options window appears. Click on the Test Equipment tab (if not in the forefront). Click the Network radio button in the Connection Type area. Result: A black dot appears in the circle. In the Ethernet Test equipment area click the checkbox(es) of the test equipment being used. Result: Checkmarks appear in the box(es) clicked on. If it is not already displayed, enter the IP address for the required piece test equipment in the IP box in the Ethernet Test equipment area. Click the Apply button. The button will darken until the selection is committed. Click the Detect on startup checkbox in the Autodetection settings area to allow the LMF to detect the test equipment automatically on application startup. Result: A checkmark appears in the box. Click the Save button to save the selection configuration for future LMF sessions. Click the Close button to close the LMF Options window. Action
2 3 4 5 6 7
8 9
Automatically Selecting Test Equipment (Autodetection) When using the autodetection feature to select test equipment, the LMF determines which test equipment items are actually communicating with the LMF. Table 3-32: Autodetecting Test Equipment Network Interface Step 1 2 3 4 5 In the LMF menu bar, select Tools > Options. Result: The LMF Options window appears. Click on the Test Equipment tab (if not in the forefront). Click the Network radio button in the Connection Type area. Result: A black dot appears in the circle. If it is not already displayed, enter the IP address for the required piece test equipment in the IP box in the Ethernet Test equipment area. Click the Detect button. The button will darken until the selection is committed. Result: For each detected equipment item, a check will appear in its checkbox. table continued on next page
Action
continued
Table 3-32: Autodetecting Test Equipment Network Interface Step 6 Action Click the Detect on startup checkbox in the Autodetection settings area to allow the LMF to detect the test equipment automatically on application startup. Result: A checkmark appears in the box. Click the Save button to save the selection configuration for future LMF sessions. Click the Close button to close the LMF Options window.
7 8
SEP 2009
3-91
Test Set Calibration Test Set Calibration

Test Set Calibration Background
Proper test equipment calibration ensures that the test equipment and associated test cables do not introduce measurement errors, and that measurements are correct. NOTE If the test set being used to interface with the BTS has been calibrated and maintained as a set, this procedure does not need to be performed. (Test Set includes LMF terminal, communications test set, additional test equipment, associated test cables, and adapters.) This procedure must be performed before beginning the optimization. Verify all test equipment (including all associated test cables and adapters actually used to interface all test equipment and the BTS) has been calibrated and maintained as a set. CAUTION If any piece of test equipment, test cable, or RF adapter, that makes up the calibrated test equipment set, has been replaced, re-calibration must be performed. Failure to do so can introduce measurement errors, resulting in incorrect measurements and degradation to system performance.
NOTE Calibration of the communications test set (or equivalent test equipment) must be performed at the site before calibrating the overall test equipment set. Calibrate the test equipment after it has been allowed to warm up and stabilize for a minimum of 60 minutes.
3-92
SEP 2009
Test Set Calibration

Calibration Procedures Included
continued
Automatic Procedures included in this section use the LMF automated calibration routines to determine path losses of the supported communications analyzer, power meter, associated test cables, adapters, and (if used) antenna switch that make up the overall calibrated test equipment set. After calibration, the gain/loss offset values are stored in a test measurement offset file on the LMF computer. Manual Agilent E4406A Transmitter Tester The E4406A does not support the power level zeroing calibration performed by the LMF. If this instrument is to be used for Bay Level Offset calibration and calibration is attempted with the LMF Calibrate Test Equipment function, the LMF will return a status window failure message stating that zeroing power is not supported by the E4406A. Refer to the Test Equipment Calibration Agilent E4406A Selfalignment section of Appendix F for instructions on using the instruments selfalignment (calibration) function prior to performing Bay Level Offset calibration. Power Meter Manual power meter calibration procedures to be performed prior to automated calibration are included in the Test Equipment Calibration Gigatronics 8542 Power Meter section of Appendix F. Prerequisites Ensure the following prerequisites have been met before proceeding:
S Test equipment is correctly connected and turned on. S Test equipment addressing is set as required for the connection type
being used (GPIB, Serial, Network)
Calibrate Test Equipment Function (Except Agilent E4406A and Anritsu MT8212B)
The Calibrate Test Equipment function zeros the power measurement level of the test equipment item to be used for TX calibration and audit. If both a power meter and an analyzer are connected, only the power meter is zeroed.
SEP 2009
3-93
continued
NOTE 1. The Agilent E4406A transmitter tester does not support power measurement level zeroing. Refer to the Test Equipment Calibration section of Appendix F for E4406A calibration. 2. Power measurement zeroing and other required calibration procedures for the Anritsu MT8212B are included in the Calibrating the Anritsu MT8212B subsection below.
Prerequisites
S Test equipment to be zeroed has been connected correctly for tests to

be run.
S Test equipment has been selected in the LMF (Table 3-27, Table 3-28,
Table 3-29, Table 3-30, Table 3-31, or Table 3-32) and detected. Procedure Follow the procedure in Table 3-33 to calibrate the test equipment. Table 3-33: Calibrate Test Equipment Power Measurement Zeroing Step 1 2 3 4 Action From the Util menu, select Calibrate Test Equipment from the pulldown menu. A Directions window is displayed. Follow the directions provided. Click on Continue to close the Directions window and start the calibration process. A status report window is displayed. Click on OK to close the status report window.
Calibrating the Anritsu MT8212B
Three types of calibration are required for the MT812B. These are:
S Zero out power meter S Calibrate TX Analyzer S Calibrate CW Generator

Procedures for each type of calibration is covered in the following subsections. Zero Out Power Meter Before using the MT8212B test set to perform RF power measurement, the test set internal power meter function must be zeroed.
continued
Prerequisites The following must be done before the zeroing out the power meter:
S The test set is connected to the LMF computer serial port with the
Anritsu 800441 RS232 serial interface cable minutes.
S Test equipment is turned on and has warmed up for at least 60 S Test equipment has been selected/detected in the LMF (Table 3-29 or
Table 3-30)
Zero out power meter Perform the following to zero out the power meter function before performing RF power measurements. Table 3-34: Anritsu MT8212B Multifunction Test Set Zero Out Power Meter Step 1 2 Action In the LMF menu bar select Util > Calibrate Test Equipment. Calibrate Anritsu MT8212B window appears Click in the Option for zero out power meter on Anritsu MT8212B radio button in the Zero Out Power Meter area. A black dot appears in the circle. Click on OK. A Directions window is displayed. Follow the directions provided. A status report window will open. Click on OK to close the status report window.
3 4 5
Calibrate TX Analyzer TX Analyzer calibration should be accomplished before performing any ATP operations with the MT8212B. Prerequisites The following must be done before the CW generator calibration:
S The test set is connected to the LMF computer serial port with the
Anritsu 800441 RS232 serial interface cable Table 3-30)
S Test equipment has been selected/detected in the LMF (Table 3-29 or

method chosen as indicated in the following: 1. Standard OpenShortLoad Components calibration: Anritsu 22N50 Open/Short, DC to 18 GHz, N(m) connector, 50 ohm Anritsu SM/PL precision load, DCto4 GHz, 42 dB, N(m) connector, 50 ohm
S Additional items must be available for the TX Analyzer calibration
3-95
continued
2. Standard InstaCalt calibration: Anritsu ICN50 InstaCal calibration module, 2 MHz to 4 GHz, N(m) connector, 50 ohm TX analyzer calibration Perform the following to calibrate the MT8212B TX analyzer function.. Table 3-35: Anritsu MT8212B Multifunction Test Set TX Analyzer Calibration
Step 1 2 3
Action In the LMF menu bar select Util > Calibrate Test Equipment. Result: Calibrate Anritsu MT8212B window appears Click in the radio button in the Calibrate TX Analyzer area. Result: A black dot appears in the circle. Select the required frequency band from the dropdown list in the Frequency Band: box.
NOTE
The dropdown list in the Frequency Band: box is automatically populated with selections for the BTS the LMF is logged into. 4 5 6 7 8 Enter the channel number to be calibrated in the Channel box. Select the desired calibration method from the dropdown list in the Calibration Method box. Click OK. Result: A Directions window is displayed. Follow the directions provided. When actions required by directions have been completed, click on Continue to close the Directions window and start the generator calibration process. Result: A status report window is displayed. Click on OK to close the status report window.
Calibrate CW Generator Before using the MT8212B test set to perform BTS RSSI testing, the test set internal Continuous Wave (CW) generator must be calibrated. Prerequisites The following must be done before the CW generator calibration: S The test set is connected to the LMF computer serial port with the Anritsu 800441 RS232 serial interface cable S Test equipment is turned on and has warmed up for at least 60 minutes. S Test equipment has been selected/detected in the LMF (Table 3-29 or Table 3-30) S RX cable(s) used in the calibration process must be calibrated for the channel for which the CW generator is to be calibrated (refer to Figure 3-28 and Table 3-38)
continued
CW generator calibration Perform the following to calibrate the MT8212B internal CW generator before performing RSSI testing with this test set. Table 3-36: Anritsu MT8212B Multifunction Test Set CW Generator Calibration Step 1 2 3 Action In the LMF menu bar select Util > Calibrate Test Equipment. Result: Calibrate Anritsu MT8212B window appears Click in the radio button in the Calibrate CW Generator area. Result: A black dot appears in the circle. Select the required frequency band from the dropdown list in the Frequency Band: box.
NOTE
The dropdown list in the Frequency Band: box is automatically populated with selections for the BTS the LMF is logged into. 4 Enter the channel or channels to be calibrated in the Channel(s) box (separate multiple channels with a comma and no space).
NOTE
When two or more channels numbers are entered, the generator will be calibrated for each channel. Interpolation will be accomplished for other channels as required for TX calibration. Channels must be within the range of the selected frequency band. 5 6 7 Click OK. Result: A Directions window is displayed. Follow the directions provided. When actions required by directions have been completed, click on Continue to close the Directions window and start the generator calibration process. Result: A status report window is displayed. Click on OK to close the status report window.
SEP 2009
3-97
Setting and Editing Generator Calibration Data Setting and Editing Generator Calibration Data
Generator Calibration Data
Generator calibration data is automatically stored in a generator calibration data file by the LMF when the generator function of a test equipment item is calibrated using the LMF Util > Calibrate Test Equipment functions. Stored data values can be edited with this procedure, or new data can be entered manually for a test equipment item generator function which was calibrated without using the LMF. CAUTION This procedure MUST be used to enter calibration data values for any MT8212B which was calibrated without using the LMF. Failure to do this will generate incorrect results for any RSSI testing performed.
Prerequisites The LMF is logged into a BTS. Set or Edit Generator Calibration Data Perform the following to enter new calibration data or edit existing data. Table 3-37: Set or Edit Generator Calibration Data Step 1 Action In the LMF menu bar select Util > Edit > Generator Calibration Data. Generator Calibration Data window appears with tabs for each type of generator test equipment calibrated using the LMF (for example, the Anritsu MT8212B) Click on the tab for the generator with data to be edited or entered. The tab moves to the forefront. To edit existing values, click in the data field to be edited and make required changes. To add a new channel and its data: 1. Click the Add Row button. 2. Click in the field where data is to be entered; for example, Frequency Band, Channel #, or Power (dB). 3. Enter the desired value.
2 3 4
NOTE
For Frequency Band fields, select the required frequency band from the dropdown provided. Selections are made available for the BTS which the LMF is logged into. table continued on next page
Setting and Editing Generator Calibration Data
continued
Table 3-37: Set or Edit Generator Calibration Data Step 5 6 Action To delete a row, click in the row, and then click the Delete Row button. For each tab with changes, click the Save button to save the displayed values.
NOTE S Values entered after the Save button was used will not be saved. S If generator calibration values exist for two different channels assigned to one frequency band, the
LMF will interpolate for all other channels on this frequency band. log back into the LMF for changes to take effect.
S Entered values will be used by the LMF as soon as they are saved. It is not necessary to log out and
SEP 2009
3-99
Cable Calibration Cable Calibration

Automatic Procedures included in this section use the LMF automated calibration routines to determine path losses of the supported communications analyzer, power meter, associated test cables, adapters, and (if used) antenna switch that make up the overall calibrated test equipment set. After calibration, the gain/loss offset values are stored in a test measurement offset file on the LMF computer. Manual Also included in this section are manual cable and directional coupler calibration procedures using a signal generator and spectrum analyzer to determine the path losses of cables which will be used in a test equipment set. When these procedures are used, the cable loss values established in the calibration process must be manually entered into the LMF. The manual entry procedures are also included in this section under Setting Cable Loss Values. In addition, manual cable calibration procedures using the Advantest R3465 communications system analyzer are provided in the Manual Cable Calibration section of Appendix F, if needed.
Calibrating Cables Overview
The cable calibration function measures the loss (in dB) for the TX and RX cables that are to be used for testing. A CDMA analyzer is used to measure the loss of each cable configuration (TX cable configuration and RX cable configuration). The cable calibration consists of the following:
S Measuring the loss of a short cable This is required to compensate

for any measurement error of the analyzer. The short cable (used only for the calibration process) is used in series with both the TX and RX cable configuration when measuring. The measured loss of the short cable is deducted from the measured loss of the TX and RX cable configuration to determine the actual loss of the TX and RX cable configurations. The result is then adjusted out of both the TX and RX measurements to compensate for the measured loss.
S Measuring the short cable plus the RX cable configuration loss
The RX cable configuration normally consists only of a coax cable with type-N connectors that is long enough to reach from the BTS RX port of the test equipment. Refer to Figure 3-25, Figure 3-26, Figure 3-27, or Figure 3-28 for specific cable and connection requirements for each type of communications system analyzer.
S Measuring the short cable plus the TX cable configuration loss
The TX cable configuration normally consists of two coax cables with type-N connectors and a directional coupler, a load, and an additional attenuator (if required by the specified BTS). The total loss of the path loss of the TX cable configuration must be as required for the BTS (normally 30 or 50 dB). Refer to Figure 3-25, Figure 3-26,
SEP 2009
3-100
Cable Calibration
continued
Figure 3-27, or Figure 3-28 for specific cable and connection requirements for each type of communications system analyzer.
Cable Calibration Setup Diagrams
Figure 3-25, Figure 3-26, Figure 3-27, and Figure 3-28 show the cable calibration setup for various supported test sets. The left side of the diagram depicts the location of the input and output ports of each test set, and the right side details the set up for each test.
Calibrate Test Cabling Using Communications System Analyzer
Cable Calibration is used to calibrate both TX and RX test cables. Appendix F covers the procedures for manual cable calibration. Prerequisites Ensure the following prerequisites have been met before proceeding:
S One of the following:

LMF computer serial port and test equipment are connected to the GPIB box For MT8212B, the test equipment is connected to the LMF computer serial port For E7495A/B, the LMF computer network card and the E7495 are connected to the Ethernet hub ( Test Equipment Connection section) and any firewall software on the LMF computer platform is TURNED OFF S Test equipment is turned on and has warmed up for at least 60 minutes. S Test equipment has been selected/detected in the LMF (Refer to the Selection Procedures subsection of the Test Equipment Selection section) Calibrating cables Refer to Figure 3-25, Figure 3-26, Figure 3-27, or Figure 3-28 and follow the procedure in Table 3-38 to calibrate the test cable configurations. Table 3-38: Cable Calibration n Step 1 2 Action From the Util menu, select Cable Calibration. A Cable Calibration window is displayed. Enter the channel number(s) in the Channels box.
NOTE
Multiple channel numbers must be separated with a comma and no space (for example; 200,800). When two or more channel numbers are entered, the cables are calibrated for each channel. Interpolation is accomplished for other channels as required for TX calibration.
Cable Calibration
continued
Table 3-38: Cable Calibration n Step 3 Action In the Cable Calibration pick list select one of the following: TX and RX Cable Cal TX Cable Cal RX Cable Cal Click OK and follow the direction displayed for each step. A status report window displays the results of the cable calibration.
3-102
SEP 2009
Cable Calibration
continued
Figure 3-25: IS95A/B Cable Calibration Test Setup Agilent 8935
SUPPORTED TEST SETS HEWLETTPACKARD MODEL HP 8935
CALIBRATION SET UP A. SHORT CABLE CAL
SHORT CABLE
TEST SET
ANT IN
DUPLEX OUT
B. RX TEST SETUP
NN FEMALE ADAPTER
RX CABLE
SHORT CABLE
TEST SET
C. TX TEST SETUP
50 TERM. DIRECTIONAL COUPLER (30 DB)
TX CABLE
SHORT CABLE
NN FEMALE ADAPTER
RX CABLE
TEST SET
SEP 2009
3-103
Cable Calibration
continued
Figure 3-26: IS95A/B and CDMA 2000 1X Cable Calibration Test Setup Agilent E4406A/E4432B and Advantest R3267/R3562
SUPPORTED TEST SETS
ADVANTEST R3267 (TOP) AND R3562 (BOTTOM)
3
RF IN
SHORT CABLE
TEST SET
EXT TRIG IN MOD TIME BASE IN (EXT REF IN) RF OUT
B. RX TEST SETUP
NN FEMALE ADAPTER
RX CABLE
AGILENT E4432B (TOP) AND E4406A (BOTTOM)
SHORT CABLE
TEST SET
RF OUTPUT 50 OHM
RF INPUT 50 OHM
C. TX TEST SETUP
AGILENT E4432B (TOP) AND 8935 SERIES E6380A (BOTTOM)

ANT IN
RF OUTPUT 50
TX CABLE
SHORT CABLE
NN FEMALE ADAPTER
RX CABLE
TEST SET
NOTE: 10 MHZ IN on rear of signal generator is connected to 10 MHZ REF OUT on side of CDMA Base Station Test Set
REF FW00089
3-104
SEP 2009
Cable Calibration
continued
Figure 3-27: CDMA2000 1X Cable Calibration Test Setup Agilent E7495A or E7495B
AGILENT E7495A OR E7495B
10 DB PAD SHORT CABLE 10 DB PAD
SUPPORTED TEST SETS
TEST SET
B. RX and TX TEST SETUP


10 DB MIMIMUM INLINE ATTENUATOR TX CABLE
10 DB PAD
Port 2 RF In Serial 1 Sensor Even Second Sync In Port 1 RF Out / SWR
Serial 2
GPS Antenna
SHORT CABLE RX CABLE
NN FEMALE ADAPTER
10 DB PAD PORT 2 RF IN PORT 1 RF OUT
TEST SET
NOTES: 1. FOR RX TESTING, TOTAL RF PATH ATTENUATION (CABLES+COUPLERS+ATTENUATORS) MUST BE WITHIN THE VALUES SPECIFIED BELOW FOR EACH TYPE OF TEST SET: E7495A: 25 TO 32 dB E7495B: 10 TO 100 dB 2. WHEN USING THE E7495A, TX TESTS REQUIRE A MINIMUM OF 30 DB ATTENUATION PLUS THE CABLE LOSSES.
SEP 2009
3-105
Cable Calibration
continued
Figure 3-28: IS95A/B and CDMA 2000 1X Cable Calibration Test Setup Anritsu MT8212B
SUPPORTED TEST SETS
ANRITSU MT8212B
SHORT CABLE
TEST SET
3
RF IN 50 RF OUT 50
C. RX and TX TEST SETUP

TX TESTS: 10 DB MINIMUM INLINE ATTENUATOR RX TEST: 35 DB MINIMUM INLINE ATTENUATOR TX AND RX CABLE SHORT CABLE NN FEMALE ADAPTER
NOTE: FOR RX TESTING (RSSI), TOTAL RF PATH ATTENUATION (CABLES+COUPLERS+ATTENUATORS) MUST BE 65 dB OR GREATER.
TX AND RX CABLE
TEST SET
3-106
SEP 2009
Cable Calibration
continued
Calibrate Test Cabling Using Signal Generator & Spectrum Analyzer
Follow the procedure in Table 3-39 to calibrate the TX/Duplexed RX cables using a signal generator and spectrum analyzer. Refer to Figure 3-29, if required. Follow the procedure in Table 3-40 to calibrate the NonDuplexed RX cables using the signal generator and spectrum analyzer. Refer to Figure 3-30, if required. TX and Duplexed RX Cable Calibration Table 3-39: Calibrating TX and Duplexed RX Cables Using Signal Generator and Spectrum Analyzer n Step 1 2 3 4 5 Action Connect a short test cable between the spectrum analyzer and the signal generator. Set signal generator to 0 dBm at the customer frequency. Use a spectrum analyzer to measure signal generator output (see Figure 3-29, A) and record the value. Connect the spectrum analyzers short cable to point B, (as shown in the lower right portion of the diagram) to measure cable output at customer frequency. Record the value at point B. Calibration factor = A B. Example: Cal = 1 dBm (53.5 dBm) = 52.5 dB
The short cable is used for calibration only. It is not part of the final test setup. After calibration is completed, do not re-arrange any cables. Use the equipment setup, as is, to ensure test procedures use the correct calibration factor.
NOTE
SEP 2009
3-107
Cable Calibration
continued
Figure 3-29: Calibrating Test Equipment Setup for TX BLO and TX ATP Tests (using Signal Generator and Spectrum Analyzer)
SIGNAL GENERATOR SPECTRUM ANALYZER
SHORT TEST CABLE
40W NONRADIATING RF LOAD
A
50 OHM TERMINATION SPECTRUM ANALYZER ONE 20DB 20 W IN LINE ATTENUATOR SHORT TEST CABLE
THIS WILL BE THE CONNECTION TO THE TX PORTS DURING TX BAY LEVEL OFFSET TEST AND TX ATP TESTS.
SIGNAL GENERATOR
THIS WILL BE THE CONNECTION TO THE HP8481A POWER SENSOR DURING TX BAY LEVEL OFFSET TEST AND TO THE PCS INTERFACE BOX INPUT PORT DURING TX ATP TESTS.
CABLE FROM 20 DB @ 20W ATTENUATOR TO THE PCS INTERFACE OR THE HP8481A POWER SENSOR. FW00293
Non-Duplexed RX Cable Calibration Table 3-40: Calibrating RX Cables Using a Signal Generator and Spectrum Analyzer n Step 1 2 3 4 5 Action Connect a short test cable to the spectrum analyzer and connect the other end to the Signal Generator. Set signal generator to 10 dBm at the customers RX frequency. Use spectrum analyzer to measure signal generator output (see Figure 3-30, A) and record the value for A. Connect the test setup, as shown in the lower portion of the diagram to measure the output at the customers RX frequency. Record the value at point B. Calibration factor = A B. Example: Cal = 12 dBm (14 dBm) = 2 dBm
The short cable is used for calibration only. It is not part of the final test setup. After calibration is completed, do not re-arrange any cables. Use the equipment setup, as is, to ensure test procedures use the correct calibration factor.
NOTE
Cable Calibration
continued
Figure 3-30: Calibrating Test Equipment Setup for RX ATP Test (using Signal Generator and Spectrum Analyzer)
SIGNAL GENERATOR SPECTRUM ANALYZER SIGNAL GENERATOR
SHORT TEST CABLE
CONNECTION TO THE HP PCS INTERFACE OUTPUT PORT DURING RX MEASUREMENTS.
SPECTRUM ANALYZER
SHORT TEST CABLE
B
LONG CABLE 2
BULLET CONNECTOR
CONNECTION TO THE RX PORTS DURING RX MEASUREMENTS.
FW00294
SEP 2009
3-109
Cable Calibration
continued
Setting Cable Loss Values
Cable loss values for the TX and RX test cable configurations are normally set by accomplishing cable calibration using the applicable test equipment. The resulting values are stored in the cable loss files. The cable loss values can also be set/changed manually. Follow the procedure in Table 3-41 to set cable loss values. CAUTION
If cable calibration was performed without using the LMF, cable loss values must be manually entered in the LMF database. Failure to do this will result in inaccurate BTS calibration and reduced site performance.
Prerequisites
S Logged into the BTS

Table 3-41: Setting Cable Loss Values n Step 1 2 3 4 5 6 7 8 Click on the Util menu. Select Edit > Cable Loss. In the data entry popup window, select TX Cable Loss or RX Cable Loss. To add a new channel number, click on the Add Row button, then click in the Channel # and Loss (dBm) columns and enter the desired values. To edit existing values, click in the data box to be changed and change the value. To delete a row, click on the row and then click on the Delete Row button. To save displayed values, click on the Save button. To exit the window, click on the Dismiss button. Values entered/changed after the Save button was used are not saved. Action
NOTE S If cable loss values exist for two different channels, the LMF will interpolate for all other
channels.
S Entered values are used by the LMF as soon as they are saved. Logging out and logging in
again is not necessary.
3-110
SEP 2009
Cable Calibration
continued
Setting Coupler Loss Values
If an inservice coupler is installed, the coupler loss (e.g., 30 dB) must be manually entered so it will be included in the LMF TX calibration and audit calculations and RX FER Test. Follow the procedure in Table 3-42 to set coupler loss values. Prerequisites
S Logged into the BTS.

Table 3-42: Setting Coupler Loss Value n Step 1 2 3 Click on the Util menu. Select Edit > Coupler Loss. In the data entry popup window, select one of the following: TX Coupler Loss RX Coupler Loss. Click in the Loss (dBm) column for each carrier that has a coupler and enter the appropriate value. To edit existing values click in the data box to be changed and change the value. Click on the Save button to save displayed values. Click on the Dismiss button to exit the window. Values entered/changed after the Save button was used are not saved. Action
4 5 6 7
NOTE S The InService Calibration check box in the
Tools > Options > BTS Options tab must checked before entered coupler loss values are used by the TX calibration and audit functions or RX FER test. again is not necessary.
S Entered values are used by the LMF as soon as they are saved. Logging out and logging in
SEP 2009
3-111
Bay Level Offset Calibration Bay Level Offset Calibration

Purpose of Bay Level Offset Calibration
3
What is BLO Calibration?
Bay Level Offset (BLO) calibration is the central activity of the optimization process. BLO calibration compensates for normal equipment variations within the BTS RF paths and assures the correct transmit power is available at the BTS antenna connectors to meet site performance requirements.
Description BLO calibration is the complete title of what is normally referred to as calibration. Calibration identifies the accumulated gain in every transmit path at the BTS site. The transmit path BLO values determined during calibration are stored in the LMF calibration data file, and are subsequently downloaded to each BBX. When transmit path calibration is performed, the LMF automatically sets receive path BLO values to a default value in the LMF calibration file. Receive BLO values are downloaded to each BBX along with the transmit BLO values. BTS RF Path Descriptions Transmit (TX) path A TX path starts at a CCCP shelf BBX backplane slot, travels through the Power Amplifier (PA), and is routed to the frametop TX antenna connector. If the BTS is equipped with a CDMA Remote Monitoring System (CRMS) Probe, the TX path continues from the frametop TX antenna through the TX directional coupler supporting the CRMS Probe, and ends at the directional coupler TX antenna port. Receive (RX) path An RX path starts at the CRMS Probe RX directional coupler antenna port, if equipped, and travels through the directional coupler to the frametop RX antenna port, the MPC, the CIO or MCIO card, and terminates at a backplane BBX slot in the CCCP shelf. For a BTS not equipped with a CRMS Probe, the RX path begins at the frametop RX antenna port and follows the remainder of the route described above. Receive (RX) path, expansion frame For expansion frames each receive path starts at the BTS RX port of the cell site starter frame, travels through the frame-to-frame expansion cable, and terminates at a backplane BBX slot of the expansion frame.
Transceiver Slots Tested for Different Antenna Configurations
At omni sites, BBX slots 1 and 13 (redundant) are tested. At sector sites, BBX slots 1 through 12, and 13 (redundant) are tested. Only those slots (sectors) actually equipped in the current NEC files are tested, regardless of physical BBX board installation in the slot.
Bay Level Offset Calibration

When to Calibrate BLOs
continued
Calibration of BLOs is required:
S After initial BTS installation S Once each year S After replacing any of the following components or associated
interconnecting RF cabling: BBX board CCCP shelf CIO card CIO to Power Amplifier backplane RF cable PA backplane PA TX filter / TX filter combiner TX thru-port cable to the top of frame
TX Path Calibration
The TX Path Calibration assures correct site installation, cabling, and the first order functionality of all installed equipment. The proper function of each RF path is verified during calibration. The external test equipment is used to validate/calibrate the TX paths of the BTS. WARNING Before installing any test equipment directly to any TX OUT connector you must first verify that there are no CDMA channels keyed. Have the OMCR place the sector assigned to the BBXs under test OOS. Failure to do so can result in serious personal injury and/or equipment damage.
CAUTION Always wear an approved antistatic wrist strap while handling any circuit card/module. If this is not done, there is a high probability that the card/module could be damaged by ESD.
SEP 2009
3-113
continued
NOTE At new site installations, to facilitate the complete test of each CCP shelf (if the shelf is not already fully populated with BBX boards), move BBX boards from shelves currently not under test and install them into the empty BBX slots of the shelf currently being tested to insure that all BBX TX paths are tested.
This procedure can be bypassed on operational sites that are due for periodic optimization. Prior to testing, view the NEC file to verify the correct BBX slots are equipped. Edit the file as required to include BBX slots not currently equipped (per Systems Engineering documentation).
BLO Calibration Data File
During the calibration process, the LMF creates a bts#.cal calibration (BLO) offset data file (CAL file) in the bts# folder. After calibration has been completed, this offset data must be downloaded to the BBXs using the LMF Download BLO function. An explanation of the file is shown below. NOTE Due to the size of the file, Motorola recommends printing a hard copy of a CAL file and refer to it for the following descriptions. The CAL file is subdivided into sections organized on a per slot basis (a slot Block). Slot 1 contains the calibration data for the 12 BBX slots. Slot 20 contains the calibration data for the redundant BBX. Each BBX slot header block contains:
S A creation Date and Time broken down into separate parameters of

createMonth, createDay, createYear, createHour, and createMin.
S The number of calibration entries fixed at 720 entries corresponding

to 360 calibration points of the CAL file including the slot header and actual calibration data.
3-114
SEP 2009
continued
S The calibration data for a BBX is organized as a large flat array. The
array is organized by branch, sector, and calibration point. The first breakdown of the array indicates which branch the contained calibration points are for. The array covers transmit, main receive and diversity receive offsets as follows: Table 3-43: BLO BTS.cal File Array Assignments Range C[1]C[240] C[241]C[480] C[481]C[720] NOTE Slot 385 is the BLO for the RFDS. The second breakdown of the array is per sector. Configurations supported are Omni, 3sector or 6sector. Assignment Transmit Main Receive Diversity Receive
Table 3-44: BTS.cal File Array (Per Sector) BBX 1 (Omni) 2 3 4 5 6 7 8 9 10 11 12 1 (Omni) 2 3 4 5 6
SEP 2009
Sectorization 3Sector, 1st C i Carrier 3Sector, 3rd C i Carrier 3Sector, 2nd C i Carrier 3Sector, 4th C i Carrier
TX Slot[1] (Primary BBXs 1 through 12) C[1]C[20] C[21]C[40] C[41]C[60] C[61]C[80] C[81]C[100] C[101]C[120] C[121]C[140] C[141]C[160] C[161]C[180] C[181]C[200] C[201]C[220] C[221]C[240] C[1]C[20] C[21]C[40] C[41]C[60] C[61]C[80] C[81]C[100] C[101]C[120]
RX C[241]C[260] C[261]C[280] C[281]C[300] C[301]C[320] C[321]C[340] C[341]C[360] C[361]C[380] C[381]C[400] C[401]C[420] C[421]C[440] C[441]C[460] C[461]C[480] C[241]C[260] C[261]C[280] C[281]C[300] C[301]C[320] C[321]C[340] C[341]C[360]
RX Diversity C[481]C[500] C[501]C[520] C[521]C[540] C[541]C[560] C[561]C[580] C[581]C[600] C[601]C[620] C[621]C[640] C[641]C[660] C[661]C[680] C[681]C[700] C[701]C[720] C[481]C[500] C[501]C[520] C[521]C[540] C[541]C[560] C[561]C[580] C[581]C[600] table continued next page
3-115
6 Sector, 1st Carrier
6 Sector, 2nd Carrier
Slot[20] (Redundant BBX13) 3Sector, 1st C i Carrier 3Sector, 3rd C i Carrier
6 Sector, 1st Carrier
continued
Table 3-44: BTS.cal File Array (Per Sector) BBX 7 8 9 10 6 Sector, 2nd Carrier Sectorization 3Sector, 2nd C i Carrier 3Sector, 4th C i Carrier TX C[121]C[140] C[141]C[160] C[161]C[180] C[181]C[200] C[201]C[220] C[221]C[240] RX C[361]C[380] C[381]C[400] C[401]C[420] C[421]C[440] C[441]C[460] C[461]C[480] RX Diversity C[601]C[620] C[621]C[640] C[641]C[660] C[661]C[680] C[681]C[700] C[701]C[720]
11 12
S Ten calibration points per sector are supported for each branch. Two
entries are required for each calibration point: 1. The first value (all odd entries) identifies the CDMA channel (frequency) where the BLO is measured. 2. The second value (all even entries) is the power set level (PwrLvlAdj). The valid range for PwrLvlAdj is from 2500 to 27500 (2500 corresponds to 125 dBm and 27500 corresponds to +125 dBm). stored in order of increasing frequency. If less than 10 points (frequencies) are calibrated, data for the highest frequency calibrated is repeated to fill out the remainder of the 10 points. odd cal entry
S The 20 calibration entries for each sector/branch combination must be
Example: C[1]=384,
= 1 calibration point C[2]=19102, even cal entry C[3]=777, C[4]=19086, . . C[19]=777, C[20]=19086, (Since only two frequencies were calibrated, data for this one, the highest, is repeated for the last eight calibration points of the sector/branch)
S When the BBX is loaded with data, the CAL file data for the BBX is
downloaded to the device in the order it is stored in the CAL file. TxCal data is sent first, C[1] C[240]. Sector 1s ten calibration points are sent (C[1] C[20]) followed by sector 2s ten calibration points (C[21] C[40]), etc. The RxCal data is sent next (C[241] C[480]), followed by the RxDCal data (C[481] C[720]). set.
S Temperature compensation data is also stored in the cal file for each
3-116
SEP 2009

Test Equipment Set-up for RF Path Calibration
continued
Follow the procedure in Table 3-45 to set up test equipment. Table 3-45: Test Equipment Setup (RF Path Calibration) n Step 1 Action Verify the GPIB controller is properly connected and turned on (does not apply to the Agilent E7495A/B or Anritsu MT8212B).
! CAUTION
To prevent damage to the test equipment, all transmit (TX) test connections must be via the 30 dB directional coupler. 2 If it has not already been done, connect the LMF computer to the BTS LAN A connector on the BTS. Refer to the procedure in Table 32.
S If required, calibrate the test equipment using the procedure in Table 3-33. S Connect the test equipment as shown in Figure 3-13 through Figure 3-15.
Transmit (TX) Path Calibration Description
The assigned channel frequency and power level (as measured at the top of the frame) for transmit calibration are derived from the site NEC files. For each BBX, the power is specified in the SIFPilotPwr NEC file parameter for the sector associated with the BBX. NOTE If both the NECB*bts#.xml and NECJ*bts#.xml files are current, all information will be correct on the LMF. If not, the carrier and channel will have to be set for each test. The calibration procedure attempts to adjust the power to within "0.5 dB of the desired power. The calibration will pass if the error is less than "1.5 dB. Transmit (TX) Bay Level Offset (BLO) Specifications SC4812T TX BLO specifications for different BTS configurations are as follows:
S At sites WITHOUT the directional coupler option, BLO is

approximately 42.0 dB +3.0 dB. Example BLO Calculation: TX BLO = Frame Power Output minus BBX output level. TX output power measured at BTS (36.0 dBm) minus the BBX TX output level (approximately 6.0 dBm) would equate to 42 dB BLO.
S At sites WITH the directional coupler option, BLO is approximately

41.4 dB 3.0 dB.
continued
Example BLO Calculation: TX BLO = Frame Power Output minus BBX output level. TX output power measured at BTS (39.4 dBm) minus the BBX TX output level (approximately 2.0 dBm) and directional coupler/cable (approximately 0.6 dBm) would equate to 41.4 dB BLO. To set the expected values see Table 3-46.
TX Calibration and the LMF
The LMF Tests > TX > TX Calibration... and Tests > All Cal/Audit... selections perform TX BLO calibration testing for installed BBX(s). The All Cal/Audit... selection initiates a series of actions to perform TX calibration, and, if calibration is successful, download BLO and perform TX audit. The TX Calibration... selection performs only TX calibration. When TX Calibration... is used, BLO download and TX audit must be performed as separate activities. The CDMA Test Parameters window which opens when TX Calibration... or All Cal/Audit... is selected contains several userselectable features which are described in the following subsections. Rate Set Dropdown Pick List The Rate Set dropdown box is enabled if at least one MCC card is selected for the test. The available options for TX tests are 1 = 9600, and 3 = 9600 1X. Option 3 is only available if 1X cards are selected for the test. The available transfer rate options for RX tests are 1 = 9600 and 2 = 14400. Option 2 is only available if no 1X cards are selected. Verify BLO In both the TX Calibration and All Cal/Audit dialog boxes, a Verify BLO checkbox is provided and checked by default. After the actual TX calibration is completed during either the TX Calibration or All Cal/Audit process, the BLO derived from the calibration is compared to a standard, acceptable BLO tolerance for the BTS. In some installations, additional items may be installed in the transmit path. The additional change in gain from these items could cause BLO verification failure and, therefore, failure of the entire calibration. In these cases, either the Verify BLO checkbox should be unchecked or the additional path losses should be added into each applicable sector using the Util > Edit > TX Coupler Loss... function. Singlesided BLO Checkbox Another option that appears in the pulldown menu is Singlesided BLO. Normally valid BLO values are some value plusorminus some offset. The ranges currently used for calibration are wider than necessary to accommodate the redundant BBX. The lower half of the allowable range is where nonredundant BBXs should function. Singlesided BLO spec is > 16dB. Doublesided BLO spec is 11 +/5dB. To get the more stringent conditions, the operator checks Singlesided BLO when calibrating non-redundant transceivers. Singlesided BLO carries the likelihood of more failures. This option should only be used by experienced CFEs.
continued
The Tests > TX > TX Calibration... menu window has a Test Pattern pulldown menu. This menu has the following choices:
S Pilot (default) performs tests using a pilot signal only. This pattern S Standard performs the tests using pilot, synch, paging and six
should be used when running inservice tests. It only requires a BBX to do the test.
traffic channels. This pattern should be used on all noninservice tests. Standard requires a BBX and an MCC. Standard uses gain values specified by the IS97 standard. is specified in the CDF file. Advanced users may use CDFPilot to generate a Pilot pattern using the value specified by the PilotGain parameter in the CDF file instead of a predetermined value.
S CDFPilot performs the tests using the pilot signal, however, the gain
S CDF performs the tests using pilot, synch, paging and six traffic
channels, however, the gain for the channel elements is specified in the CDF file. Advanced users may use CDF to generate a standard pattern. Instead of using the values specified by IS97, the settings for the following CDF parameters are used: PilotGain PchGain SchGain NomGain1Way
SEP 2009
3-119
TX BLO Calibration TX BLO Calibration

TX Calibration
WARNING Before installing any test equipment directly to any TX OUT connector, first verify there are no CDMA BBX channels keyed. Failure to do so can result in serious personal injury and/or equipment damage.
CAUTION Always wear an approved antistatic wrist strap while handling any circuit card or module. If this is not done, there is a high probability that the card or module could be damaged by ESD.
All Cal/Audit and TX Calibration Procedure
The LMF All Cal/Audit and TX calibration procedures are essentially identical, except for the step that selects the type of procedure desired (Refer to Step 3 in Table 3-46). Prerequisites Before running this procedure, be sure that the following have been done:
S The card in slot CSM 1, GLIs, MCCs, and BBXs have correct code
and data loads.
S Primary CSM and MGLI are INS_ACT (bright green). S All BBXs are OOS_RAM (yellow). S If running calibration or audit using a test pattern other than Pilot,
MCCs are INS_ACT (bright green). calibration.
S Test equipment and test cables are calibrated and connected for TX S LMF is logged into the BTS in the GUI environment.
NOTE Verify all BBX boards removed and repositioned have been returned to their assigned shelves/slots. Any BBX boards moved since they were downloaded will have to be downloaded again.
TX BLO Calibration
continued
All Cal Audit/TX Path Calibration procedure Follow the procedure in Table 3-46 to perform the All Cal/Audit and TX path calibration test. Table 3-46: All Cal/Audit and TX Calibration Procedure n Step 1 2 3 Action If it has not already been done, configure test equipment for TX calibration by following the procedure in Table 3-45. Click on the BBX(s) to be calibrated and the BBXR. For All Cal Audit... Click Tests in the BTS menu bar, and select All Cal/Audit... from the pulldown menus. A CDMA Test Parameters window will appear. For TX Calibration Click Tests in the BTS menu bar, and select TX > TX Calibration from the pulldown menus. A CDMA Test Parameters window will appear. Select the appropriate carrier(s) and sector(s) (carrier-bts#-sector#-carrier#) from those displayed in the Channels/Carrier pick list.
NOTE
To select multiple items, hold down the Shift or Ctrl key while clicking on pick list items to select multiple carrier(s)sector(s). 5 Verify that the correct channel number for the selected carrier is shown in the Carrier # Channels box. If it is not, obtain the latest bts#.necf files from the OMCR.
NOTE
If necessary, the correct channel number may be manually entered into the Carrier # Channels box. 6 7 If Verify BLO is to be used during the calibration, leave the checkbox checked (default). If SingleSided BLO is to be used during the calibration, click on the checkbox.
NOTE
SingleSided BLO should only be used for primary BBXs. Do not check the box when calibrating the redundant BBX. 8 In the Test Pattern box, select the test pattern to use for the calibration from the dropdown list. Result: The LMF will automatically key the designated BBX and ask the operator to move the test equipment cable to appropriate TX path.
NOTE
If the Test Pattern to be used is Standard , CDFPilot, or CDF, select at least one MCC (refer to Test Pattern Dropdown Pick List under TX Calibration and the LMF in this section). 9 If at least one MCC was selected in Step 8, select the appropriate transfer rate (1 = 9600, 3 = 9600 1X) from the dropdown list in the Rate Set box.
NOTE
The rate selection of 3 is only available if 1X cards are selected for the test. table continued on next page
TX BLO Calibration
continued
Table 3-46: All Cal/Audit and TX Calibration Procedure n Step 10 11 Action Click OK to display the status report window followed by a Directions pop-up window. Follow cable connection directions as they are displayed. Result: When the calibration process is completed, results will be displayed in the status report window. Click on the Save Results or Dismiss button, as desired, to close the status report window.
12
Exception Handling In the event of a failure, the calibration procedure displays a FAIL message in the status report window and provides information in the Description field. Recheck the test setup and connection and rerun the test. If the tests fail again, note specifics about the failure, and refer to Chapter 7, Troubleshooting.
3-122
SEP 2009
Download BLO Download BLO

After a successful TX path calibration, download the BLO calibration file data to the BBXs. NOTE If a successful All Cal/Audit was completed, this procedure does not need to be performed, as BLO is downloaded as part of the All Cal/Audit.
Prerequisites Ensure the following prerequisites have been met before proceeding:
S BBXs being downloaded are OOSRAM (yellow). S TX calibration is successfully completed.

Test Procedure Follow the procedure in Table 3-47 to download the BLO data to the BBXs. Table 3-47: Download BLO n Step 1 2 Select the BBX(s) to be downloaded. Click Device in the BTS menu bar, and select Download > BLO from the pulldown menus. A status report window displays the result of the download. Action
NOTE
Selected device(s) do not change color when BLO is downloaded. 3 Click on OK to close the status report window.
SEP 2009
3-123
TX Calibration Audit TX Calibration Audit

Introduction
NOTE RF path verification, BLO calibration, and BLO data download to BBXs must have been successfully completed prior to performing the calibration audit.
3
The BLO calibration audit procedure confirms the successful generation and storage of the BLO calibration offsets. The calibration audit procedure measures the path gain or loss of every BBX transmit path at the site. In this test, actual system tolerances are used to determine the success or failure of a test. The external test equipment set up used is same as that for TX calibration.
TX Audit Test
The Tests menu item, TX Audit, performs the TX BLO Audit test for a BBX(s). All measurements are made through the appropriate TX output connector using the calibrated TX cable setup. Prerequisites WARNING Before installing any test equipment directly to any TX OUT connector, first verify there are no CDMA BBX channels keyed. Failure to do so can result in serious personal injury and/or equipment damage. Before running this test, ensure that the following have been done: NOTE All PAs must be INS during any TX testing.
S S S S
CSM1, GLIs, and BBXs have correct code load and data load. Primary CSM and MGLI are INS. All BBXs are OOS_RAM.
Test equipment and test cables are calibrated and connected for TX BLO calibration. S LMF is logged into the BTS. Test Procedure Connect the test equipment as shown in Figure 3-13 through Figure 3-16. Follow the procedure in Table 3-46 using the If performing TX Audit alternative in Step 3 to perform the BTS TX Path Audit test.
Create CAL File Create CAL File

After downloading BLO data to the BBXs, the BLO data must also be saved to a CAL file in the BTS folder on the LMF computer platform. The CAL file must be created or updated so it can be transferred to the OMCR. If no CAL file is stored in the BTS folder (such as after the firsttime calibration of a new BTS), the Create Cal File function gets the BLO data from the BBXs, creates the CAL file, and stores the BLO data in it. If the CAL file already exists in the BTS folder, this function will update it with the new BLO data. NOTE Create Cal File function only applies to selected (highlighted) BBXs.
CAUTION Motorola does not encourage the user to edit the CAL file as this action can cause interface problems between the BTS and the LMF. To manually edit the CAL file, the LMF must first be logged out of the BTS. If the CAL file is manually edited and then the Create Cal File function is run, the edited information is lost.
Prerequisites Before performing this procedure, the following should be done:
S LMF is logged into the BTS. S BBXs are OOS_RAM with BLO downloaded.
Creating a CAL File Table 3-48: Create CAL File n Step 1 Action Select the applicable BBXs.
NOTE
The CAL file is only updated for the selected BBXs. 2 3 4 Click on the Device menu. Click on the Create Cal File menu item. A status report window displays the results of the action. Click OK to close the status report window.
SEP 2009
3-125
Cellular Remote Monitoring System (CRMS) Probe Setup and Calibration Cellular Remote Monitoring System (CRMS) Probe Setup and Calibration
CRMS Probe
If the BTS is equipped with a CRMS Probe, refer to CRMS Probe Users Guide; 68P02969A25 for CRMS Probe setup, calibration, acceptance testing, and required calibration and test application software.
3-126
SEP 2009
BTS Redundancy/Alarm Testing BTS Redundancy/Alarm Testing

Objective
This section tests the redundancy options that could be included in the cell site. These tests verify, under a fault condition, that all modules equipped with redundancy switch operations to their redundant partner and resume operation. An example would be to pull the currently active CSM and verify the standby CSM takes over distribution of the CDMA reference signal. Redundancy covers many BTS modules. Confirm the redundant options included in the BTS, and proceed as required. If the BTS has only basic power supply redundancy, the tests and procedures detailed in the following tables should be bypassed.
S S S S S
Table 3-51. Miscellaneous Alarm Tests (BTS Frame) Table 3-52. BBX Redundancy Tests (BTS Frame) Table 3-53. CSM, GPS, and HSO Redundancy Alarm Tests Table 3-54. PA Redundancy Test Table 3-55. GLI Redundancy Test
During redundancy verification of the test, alarms reported by the GLI (displayed via the alarm monitor) will also be verified/noted.
Test Equipment
The following pieces of test equipment are required to perform this test:
S LMF S Communications Test Set

Redundancy/Alarm Test
Perform each of the following tests to verify BTS redundancy and to confirm all alarms are received and reported by the BTS equipment. The procedures should be performed on the following modules/boards:
S S S S S
Power supply/converter modules in all frames Distribution shelf modules in the BTS frame CCCP shelf modules in the BTS frame (except MCCs) PA modules in the BTS frame AMR Customer defined input/output tests
SEP 2009
3-127
BTS Redundancy/Alarm Testing

Test Equipment Setup
continued
Follow the procedure in Table 3-49 to set up test equipment: NOTE All alarm tests are performed using TX antenna 1
3
Step 1 2 3
Table 3-49: Test Equipment Setup for Redundancy/Alarm Tests Action Interface the LMF computer to the BTS LAN A connector on the BTS frame (refer to Table 3-4, page 3-14). Login to the BTS. Set up test equipment for TX Calibration at TXOUT1 (see Figure 3-13 through Figure 3-16, as applicable).
NOTE
If site is not equipped for redundancy, remove all GLI and BBX boards installed in any redundant slot positions at this time. 4 5 Display the alarm monitor by selecting Util>Alarm Monitor. Unequip all customer defined AMR alarms reported via the AMR Alarm connector (A & B) by clicking on GLI, then selecting Device>Set Alarm Relays>Unequipped.
NOTE
During configuration of GLI alarm reporting, spurious alarms may report. Allow the BTS to stabilize for 10 seconds. If any alarms are actively being reported after the BTS has stabilized, determine the cause before proceeding further.
Power Supply Redundancy
Follow the steps in Table 3-50 to verify redundancy of the power supply modules. Alarms reported by the GLI (displayed via the alarm monitor) are also verified. Table 3-50: Power Supply/Converter Redundancy (BTS Frame) Step 1 Action Select the GLI (highlight) and from the pulldown menu select: Device>BBX/MAWI>Set Redundant Sector>Carrier#11 Device>BBX/MAWI>Set Pilot Only>Carrier#1-1 Device>BBX/MAWI>Set Pilot Gain>Carrier#-1-1 and Pilot Gain = 262 Select (highlight) BBX1 and from the pulldown menu select Device>BBX/MAWI>Key. Set XCVR gain to 40 and enter the correct XCVR channel number. table continued on next page
2 3
continued
Table 3-50: Power Supply/Converter Redundancy (BTS Frame) Step 4 Action Remove PS1 from the power distribution shelf (see Figure 3-31). Observe that an alarm message is reported via the GLI as displayed on the alarm monitor. Verify no other modules went OOS. Re-install PS1. Observe the alarm clears on the alarm monitor. Repeat steps 4 and 5 for PS2 and PS3. Verify that all PWR/ALM LEDs are GREEN. Select BBX-1 and Device>BBX/MAWI>Dekey
5 6 7 8
Figure 3-31: CCCP Shelf
19 mm Filler Panel
CIO
MPC/EMPC1
MCC1
MCC2
MCC3
MCC4
MCC5
MCC6
AMR1
BBXR
BBX1
BBX2
BBX3
BBX4
BBX5
BBX6
GLI1
PS1
PS2
PS3
CCD1
38 mm Filler Panel
HSO/LFR
CCD2
MPC/EMPC2
NOTE: MCCs may be MCC24Es, MCC8Es, or MCC1Xs. BBXs may be BBX2s or BBX1Xs. GLIs may be GLI2s or GLI3s.
MCC10
MCC12
MCC11
BBX10
BBX11
BBX12
CSM1
CSM2
AMR2
MCC7
MCC8
MCC9
BBX7
BBX8
BBX9
Switch
GLI2
SEP 2009
3-129

Miscellaneous Alarm/Redundancy Tests
continued
Follow steps in Table 3-51 to verify that alarms reported by the GLI are displayed via the alarm monitor if a BTS frame module failure occurs. Table 3-51: Miscellaneous Alarm Tests Step Action Select Util>Alarm Monitor to display the alarm monitor window. Perform the following to verify fan module alarms: 1 2
Unseat a fan module (see Figure 3-32). Observe an alarm message was reported via the GLI (as displayed on the alarm monitor). Replace fan module and verify the alarm monitor reports that the alarm clears. Repeat for all other fan modules in the BTS frame. NOTE
Follow Step 3 for Starter Frames and Step 4 for Expansion Frames. 3 Starter Frames Only: Perform the following to verify MPC module alarms. Unseat MPC modules (see Figure 3-31) one at a time.
Observe that an alarm message was reported via the GLI as displayed on the alarm monitor. Replace the MPC modules and verify the alarm monitor reports the alarm clears.
4 Expansion Frames Only: Perform the following to verify EMPC module alarms.
Unseat EMPC modules (see Figure 3-31) one at a time Observe that an alarm message was reported via the GLI as displayed on the alarm monitor. Replace the EMPC modules and verify the alarm monitor reports that the alarm clears.
5 If equipped with AMR redundancy, perform the following to verify AMR module redundancy/alarms. Unseat AMR 2 (see Figure 3-31).
Observe that an alarm message is reported via the GLI (as displayed on the alarm monitor). Repeat Steps 1, 2 and 3 (starter frame) or Steps 1, 2 and 4 (expansion frame). Replace the AMR module and verify the alarm monitor reports that the alarm clears. Unseat AMR 1; observe alarm message was reported via GLI (as displayed on the alarm monitor). Replace the AMR module and verify the LMF reports the alarm has cleared. NOTE
All PWR/ALM LEDs should be GREEN at the completion of this test.
3-130
SEP 2009

Figure 3-32: Fan Modules
LATCHES
continued
FAN MODULES
BBX Redundancy
Follow the steps in Table 3-52 to verify redundancy of the BBXs in the CCCP shelf. Alarms reported by the GLI (displayed via the alarm monitor) are also verified. This test can be repeated for additional sectors at the customers discretion. Table 3-52: BBX Redundancy Alarms Step Action
n WARNING
Any BBXs enabled will immediately key-up. Before enabling any BBX, always verify that the TX output assigned to the BBX is terminated into a 50 W non-radiating RF load! Failure to do so could result in serious personal injury and/or damage to the equipment. 1 2 3 4 5 6 7 8 9 10 11 12 Enable the primary, then the redundant BBX assigned to ANT 1 by selecting the BBX and Device>BBX/MAWI>Key. Observe that primary BBXs key up, and a carrier is present at each respective frequency. Remove the primary BBX. Observe a carrier is still present. The Redundant BBX is now the active BBX for Antenna 1. Replace the primary BBX and reload the BBX with code and data. Re-enable the primary BBX assigned to ANT 1 and observe that a carrier is present at each respective frequency. Remove the redundant BBX and observe a carrier is still present. The Primary BBX is now the active BBX for ANT 1. Replace the redundant BBX and reload the BBX with code and data. Re-enable the redundant BBX assigned to ANT 1 and observe that a carrier is present at each respective frequency: De-key the Xcvr by selecting Device>BBX/MAWI>Dekey. Repeat Steps 1 through 11 for additional BBXs/antennas, if equipped.
1X SC4812T CLPA BTS Optimization/ATP 3-131
SEP 2009

CSM, GPS, &HSO Redundancy/Alarm Tests
continued
Follow the procedure in Table 3-53 to verify the manual redundancy of the CSM, GPS, and HSO boards. Verification of alarms reported is also covered. NOTE
DO NOT perform the procedure in Table 3-53, unless the site is configured with an HSO timebase as a backup for the GPS.
Table 3-53: CSM, GPS, & HSO, Redundancy/Alarm Tests Step Action
n WARNING
Any BBXs enabled will immediately key-up. Before enabling any BBX, always verify that the TX output assigned to the BBX is terminated into a 50 W non-radiating RF load! Failure to do so could result in serious personal injury and/or damage to the equipment. 1 2 3 4 Enable the primary, then the redundant BBXs assigned to ANT 1 by selecting the BBX and Device>BBX/MAWI>Key. Disconnect the GPS antenna cable, located on top of the BTS frame. This forces the HSO board timebase to become the CDMA timing source. Observe a CDMA timing reference alarm and source change is reported by the alarm monitor. Allow the HSO to become the active timing source.
S Verify the BBXs remain keyed and INS. S Verify no other modules went OOS due to the transfer to HSO reference. S Observe the PWR/ALM LEDs on the CSM 1 front panel are steady GREEN.
5 6 Reconnect the GPS antenna cable. Allow the GPS to become the active timing source.
S Verify the BBXs remain keyed and INS. S Verify no other modules went OOS due to the transfer back to the GPS reference. S Observe the PWR/ALM LEDs on CSM 1 are steady GREEN.
7 Disable CSM 1 and enable CSM 2.
S Various CSM source and clock alarms are now reported and the site comes down. S Alarms clear when the site comes back up.
3-132
SEP 2009
continued
Table 3-53: CSM, GPS, & HSO, Redundancy/Alarm Tests Step 8 Allow the CSM 2 board to go INS_ACT. Action
S Verify the BBXs are dekeyed and OOS, and the MCCs are OOS_RAM. S Verify no other modules went OOS due to the transfer to CSM 2 reference. S Observe the PWR/ALM LEDs on CSM 2 front panels are steady GREEN. NOTE
It can take up to 20 minutes for the CSM to re-establish the GPS link and go INS. MCCs go OOS_RAM. 9 10 11 Key BBXs 1 and R and observe a carrier is present. Repeat Steps 2 through 6 to verify CSM source redundancy with CSM 2.
NOTE
DO NOT ENABLE the redundant CSM. Disable CSM 2 and enable CSM 1.
S Various CSM Source and Clock alarms are reported and the site comes down. S Alarms clear when the site comes back up.
12 13 De-key the Xcvr by selecting Device>BBX/MAWI>Dekey. Allow the CSM 1 board to go INS_ACT.
S Verify the BBXs are de-keyed and OOS. S Verify no other modules went OOS due to the transfer to CSM 1 reference. S Observe PWR/ALM LEDs on the CSM 1 front panels are steady GREEN.
14 Disable the primary and redundant BBXs.
Power Amplifier (PA) Redundancy Test
Follow the procedure in Table 3-54 to verify redundancy of the Power Amplifiers (PA). WARNING First verify there are no BBX channels keyed BEFORE moving the antenna connection. Failure to do so can result in serious personal injury and/or equipment damage.
SEP 2009
3-133
continued
Table 3-54: Power Amplifier Redundancy Test Step 1 Action From the pulldown menu select: Device>BBX/MAWI>Set Redundant Sector>Carrier#11 Device>BBX/MAWI>Set Pilot Only>Carrier#1-1 Device>BBX/MAWI>Set Pilot Gain> Carrier#-1-1 and Pilot Gain = 262 Key-up the BBX assigned to the PAs associated with the sector under test (gain = 40). Adjust the communications test set spectrum analyzer, as required, to observe the overall carrier amplitude and IM Shelf and note for reference. These figures will be required later.
2 3
NOTE
See Figure 3-13 through Figure 3-16, as applicable, for test equipment setup, if required. 4 Push-in and release the breaker supplying the first PA of the pair.
NOTE
After power is removed, IM suppression takes a few seconds to settle out while compensating for the removal of the first PA. The overall gain decreases by approximately 6 dB. The process must be complete before proceeding. 5 Verify: The other PA module did not go OOS due to the loss of the PA.
The overall carrier amplitude is reduced by approximately 6 dB and IM suppression on the analyzer
display remains basically unchanged.
PA fault message is reported via the GLI and displayed on the alarm monitor.
6 Re-apply power to the PA module and observe the alarm has cleared on the alarm monitor.
NOTE
All PWR/ALM LEDs should be GREEN at completion of test. 7 8 9 Repeat Steps 4 through 6 to verify the second PA of the pair. De-key the BBX.
n WARNING
First verify there are no BBX channels keyed when moving the antenna connection. Failure to do so can result in serious personal injury and/or equipment damage. Repeat Steps 1 through 8 to verify PAs assigned to sectors 2 and 3 (if equipped). Move the test cable on top of the BTS to TX OUT 2 and TX OUT 3 antenna connectors as required.
3-134
SEP 2009

GLI Redundancy Test
continued
CAUTION This test can only be performed when the MM path is established by the MM (not just with LAPD link connected). Attempting to force the GLIs to hot swap under alarm monitor control, when isolated from the MM, causes GLIs to hang up.
Table 3-55: GLI Redundancy Test (with MM Connection Established) Step 1 Action
NOTE S This test assumes the alarm monitor is NOT connected to the BTS and the T1/E1 span is connected
and communication is established with the MM.
S BOTH GLIs must be INS before continuing.

Verify the BBXs are enabled and a CDMA carrier is present. 2 3 4 5 6 7 8 Identify the primary and redundant GLI pairs. Pull the GLI that is currently INSACT and has cage control. Observe the BBX remains GREEN, and the redundant GLI is now active. Verify no other modules go OOS due to the transfer of control to the redundant module. Verify that the BBXs are enabled and a CDMA carrier is present. Reinstall the GLI and have the OMCR/CBSC place it back in-service. Repeat Steps 1 through 7 to verify the other GLI board.
SEP 2009
3-135
Alarms Testing Alarms Testing

Alarm Verification
ALARM connectors provide Customer Defined Alarm Inputs and Outputs. The customer can connect BTS site alarm input sensors and output devices to the BTS, thus providing alarm reporting of active sensors as well controlling output devices. The SC 4812T is capable of concurrently monitoring 35 input signals. These inputs are divided between 2 Alarm connectors marked ALARM A and ALARM B located at the top of the frame (see Figure 3-33). The ALARM A connector is always functional; ALARM B is functional when an AMR module is equipped in the AMR 2 slot in the distribution shelf. ALARM A port monitors input numbers 1 through 18, while ALARM B port monitors input numbers 19, 20, and 22 through 36 (see Figure 3-34). Alarm 21 is reserved for system use. State transitions on these input lines are reported to the LMF and OMCR as GLI Input Relay alarms. ALARM A and ALARM B connectors each provide 18 inputs and 8 outputs. If both A and B are functional, 36 inputs and 16 outputs are available. They may be configured as redundant. The configuration is set by the CBSC.
Alarm Reporting Display
The Alarm Monitor window can be displayed to list alarms that occur after the window is displayed. To access the Alarm Monitor window, select Util>Alarm Monitor. The following buttons are included:
S The Options button allows for a severity level (Warning, Minor, and
Major) selection. The default is all levels. To change the level of alarms reported click on the Options button and highlight the desired alarm level(s). To select multiple levels press the <Ctrl> key (for individual selections) or <Shift> key (for a range of selections) while clicking on the desired levels. button is clicked the name of the button changes to Continue. When the Continue button is clicked, the display of alarms continues. Alarms that occur between the time the Pause button is clicked and the Continue button is clicked are not displayed.
S The Pause button pauses/stops the display of alarms. When the Pause
S The Clear button clears the Alarm Monitor display. New alarms that
occur after the Clear button is clicked are displayed.
S The Dismiss button dismisses/closes the Alarm Monitor display.

Alarms Testing
continued
Figure 3-33: Alarm Connector Location and Connector Pin Numbering
1 1 2 59 59 60 60
Purpose
The following procedures verify the customer defined alarms and relay contacts are functioning properly. These tests are performed on all AMR alarms/relays in a sequential manner until all have been verified. Perform these procedures periodically to ensure the external alarms are reported properly. Following these procedures ensures continued peak system performance. Study the site engineering documents and perform the following tests only after first verifying that the AMR cabling configuration required to interconnect the BTS frame with external alarm sensors and/or relays meet requirements called out in the SC 4812T BTS Installation Manual. NOTE Motorola highly recommends that you read and understand this procedure in its entirety before starting this procedure.
SEP 2009
3-137
Alarms Testing
Test Equipment
continued
The following test equipment is required to perform these tests:
S LMF S Alarms Test Box (CGDSCMIS00014) optional

NOTE
Abbreviations used in the following figures and tables are defined as: S NC = normally closed S NO = normally open S COM or C = common S CDO = Customer Defined (Relay) Output S CDI = Customer Defined (Alarm) Input
Figure 3-34: AMR Connector Pin Numbering

A CDI 18 ... A CDI 1
Returns
2 60 26 2
60
26
59
25
59
25
Returns
ALARM A (AMR 1) B CDI 36 ...
ALARM B (AMR 2) B CDI 19

FW00302
NOTE The preferred method to verify alarms is to follow the Alarms Test Box Procedure in Table 3-56. If not using an Alarm Test Box, follow the procedure in Table 3-57.
3-138
SEP 2009
Alarms Testing
continued
CDI Alarm Input Verification with Alarms Test Box
Table 3-56 describes how to test the CDI alarm input verification using the Alarm Test Box. Follow the steps as instructed and compare results with the LMF display. NOTE It may take a few seconds for alarms to be reported. The default delay is 5 seconds. Leave the alarms test box switches in the new position until the alarms have been reported. Table 3-56: CDI Alarm Input Verification Using the Alarms Test Box Step 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Select the GLI. Click on the Device menu. Click on the Set Alarm Relays menu item. Click on Normally Open. A status report window displays the results of the action. Click on the OK button to close the status report window. Set all switches on the alarms test box to the Open position. Connect the alarms test box to the ALARM A connector (see Figure 3-33). Set all of the switches on the alarms test box to the Closed position. An alarm should be reported for each switch setting. Set all of the switches on the alarms test box to the Open position. A clear alarm should be reported for each switch setting. Disconnect the alarms test box from the ALARM A connector. Connect the alarms test box to the ALARM B connector. Set all switches on the alarms test box to the Closed position. An alarm should be reported for each switch setting Set all switches on the alarms test box to the Open position. A clear alarm should be reported for each switch setting. Disconnect the alarms test box from the ALARM B connector. Select the GLI. Click on the Device menu. Click on the Set Alarm Relays menu item. table continued on next page
Action Connect the LMF to the BTS and log into the BTS.
Alarms Testing
continued
Table 3-56: CDI Alarm Input Verification Using the Alarms Test Box Step 19 20 21 22 23 24 25 26 Action Click on Normally Closed. A status report window displays the results of the action. Click OK to close the status report window. Alarms should be reported for alarm inputs 1 through 36. Set all switches on the alarms test box to the Closed position. Connect the alarms test box to the ALARM A connector. Alarms should be reported for alarm inputs 1 through 18. Set all switches on the alarms test box to the Open position. An alarm should be reported for each switch setting. Set all switches on the alarms test box to the Closed position. A clear alarm should be reported for each switch setting. Disconnect the alarms test box from the ALARM A connector.
NOTE
Input 21 (pins 29 and 30) on the Alarm B connector is reserved for the Power Supply Modules alarm. Connect the alarms test box to the ALARM B connector. A clear alarm should be reported for alarm inputs 19 through 36.
27 28 29 30 31 32 33 34 35 36 37 38
Set all switches on the alarms test box to the Open position. An alarm should be reported for each switch setting. Set all switches on the alarms test box to the Closed position. A clear alarm should be reported for each switch setting. Disconnect the alarms test box from the ALARM B connector. Select the GLI. Click on the Device menu. Click on the Set Alarm Relays menu item. Click on Unequipped . A status report window displays the results of the action. Click on the OK button to close the status report window. Connect the alarms test box to the ALARM A connector. Set all switches on the alarms test box to both the Open and the Closed position. No alarm should be reported for any switch settings. Disconnect the alarms test box from the ALARM A connector. Connect the alarms test box to the ALARM B connector. table continued on next page
3-140
SEP 2009
Alarms Testing
continued
Table 3-56: CDI Alarm Input Verification Using the Alarms Test Box Step 39 40 41 Action Set all switches on the alarms test box to both the Open and the Closed position. No alarm should be reported for any switch settings. Disconnect the alarms test box from the ALARM B connector. Load data to the GLI to reset the alarm relay conditions according to the CDF file.
CDI Alarm Input Verification without Alarms Test Box
Table 3-57 describes how to test the CDI alarm input verification without the use of the Alarms Test Box. Follow the steps as instructed and compare results with the LMF display. NOTE It may take a few seconds for alarms to be reported. The default delay is 5 seconds. When shorting alarm pins wait for the alarm report before removing the short.
Table 3-57: CDI Alarm Input Verification Without the Alarms Test Box Step 1 2 3 4 5 6 7 Select the GLI. Click on the Device menu. Click on the Set Alarm Relays menu item. Click on Normally Open. A status report window displays the results of the action. Click on OK to close the status report window. Refer to Figure 3-34 and sequentially short the ALARM A connector CDI 1 through CDI 18 pins (2526 through 5960) together. An alarm should be reported for each pair of pins that are shorted. A clear alarm should be reported for each pair of pins when the short is removed. table continued on next page Action Connect the LMF to the BTS and log into the BTS.
SEP 2009
3-141
Alarms Testing
continued
Table 3-57: CDI Alarm Input Verification Without the Alarms Test Box Step 8 Action
NOTE
Input 21 (pins 29 and 30) on the Alarm B connector is reserved for the Power Supply Modules alarm. Refer to Figure 3-34 and sequentially short the ALARM B connector CDI 19 through CDI 36 pins (2526 through 5960) together. An alarm should be reported for each pair of pins that are shorted. A clear alarm should be reported for each pair of pins when the short is removed.
3
9 10 11 12 13 14
Select the GLI. Click on the Device menu. Click on the Set Alarm Relays menu item. Click on Normally Closed. A status report window displays the results of the action. Click on OK to close the status report window. Alarms should be reported for alarm inputs 1 through 36. Refer to Figure 3-34 and sequentially short the ALARM A connector CDI 1 through CDI 18 pins (2526 through 5960) together. A clear alarm should be reported for each pair of pins that are shorted. An alarm should be reported for each pair of pins when the short is removed.
15
NOTE
Input 21 (pins 29 and 30) on the Alarm B connector is reserved for the Power Supply Modules alarm. Refer to Figure 3-34 and sequentially short the ALARM B connector CDI 19 through CDI 36 pins (2526 through 5960) together. A clear alarm should be reported for each pair of pins that are shorted. An alarm should be reported for each pair of pins when the short is removed.
16 17 18 19 20 21
Select the GLI. Click on the Device menu. Click on the Set Alarm Relays menu item. Click on Unequipped . A status report window displays the results of the action. Click on OK to close the status report window. Refer to Figure 3-34 and sequentially short the ALARM A connector CDI 1 through CDI 18 pins (2526 through 5960) together. No alarms should be displayed. table continued on next page
3-142
SEP 2009
Alarms Testing
continued
Table 3-57: CDI Alarm Input Verification Without the Alarms Test Box Step 22 Action
NOTE
Input 21 (pins 29 and 30) on the Alarm B connector is reserved for the Power Supply Modules alarm. Refer to Figure 3-34 and sequentially short the ALARM B connector CDI 19 through CDI 36 pins (2526 through 5960) together. No alarms should be displayed.
23
Load data to the GLI to reset the alarm relay conditions according to the CDF file.
Pin and Signal Information for Alarm Connectors
Table 3-58 lists the pins and signal names for Alarms A and B. Table 3-58: Pin and Signal Information for Alarm Connectors Signal Name Pin 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Alarm A
A CDO1 NC A CDO1 Com A CDO1 NO A CDO2 NC A CDO2 Com A CDO2 NO A CDO3 NC A CDO3 Com A CDO3 NO A CDO4 NC A CDO4 Com A CDO4 NO A CDO5 NC A CDO5 Com A CDO5 NO A CDO6 NC A CDO6 Com A CDO6 NO A CDO7 NC B CDO9 NC B CDO9 Com B CDO9 NO B CDO10 NC B CDO10 Com B CDO10 NO B CDO11 NC B CDO11 Com B CDO11 NO B CDO12 NC B CDO12 Com B CDO12 NO B CDO13 NC B CDO13 Com B CDO13 NO B CDO14 NC B CDO14 Com B CDO14 NO B CDO15 NC
Alarm B

Alarms Testing
continued
Table 3-58: Pin and Signal Information for Alarm Connectors Signal Name Pin 20 21 22 Alarm A
A CDO7 Com A CDO7 NO A CDO8 NC A CDO8 Com A CDO8 NO Cust Retn 1 A CDI 1 Cust Retn 2 A CDI 2 Cust Retn 3 A CDI 3 Cust Retn 4 A CDI 4 Cust Retn 5 A CDI 5 Cust Retn 6 A CDI 6 Cust Retn 7 A CDI 7 Cust Retn 8 A CDI 8 Cust Retn 9 A CDI 9 Cust Retn 10 A CDI 10 Cust Retn 11 A CDI 11 Cust Retn 12 A CDI 12 Cust Retn 13 A CDI 13 B CDO15 Com B CDO15 NO B CDO16 NC B CDO16 Com B CDO16 NO B CDI 19 Cust Retn 19 B CDI 20 Cust Retn 20
Alarm B
23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
Power Supply Modules alarm Power Supply Modules alarm Retn

B CDI 22 Cust Retn 22 B CDI 23 Cust Retn 23 B CDI 24 Cust Retn 24 B CDI 25 Cust Retn 25 B CDI 26 Cust Retn 26 B CDI 27 Cust Retn 27 B CDI 28 Cust Retn 28 B CDI 29 Cust Retn 29 B CDI 30 Cust Retn 30 B CDI 31 Cust Retn 31

Alarms Testing
continued
Table 3-58: Pin and Signal Information for Alarm Connectors Signal Name Pin 51 52 53 54 55 56 57 58 59 60 Alarm A
Cust Retn 14 A CDI 14 Cust Retn 15 A CDI 15 Cust Retn 16 A CDI 16 Cust Retn 17 A CDI 17 Cust Retn 18 A CDI 18 B CDI 32 Cust Retn 32 B CDI 33 Cust Retn 33 B CDI 34 Cust Retn 34 B CDI 35 Cust Retn 35 B CDI 36 Cust Retn 36
Alarm B
NOTE
CDO = Customer Defined Output; CDI = Customer Defined Input
SEP 2009
3-145
Alarms Testing
Notes
continued
3-146
SEP 2009
Chapter 4: Automated Acceptance Test Procedure

Table of Contents
Acceptance Test Procedures Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reduced ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automated Acceptance Test Procedures TX & RX . . . . . . . . . . . . . . . . . . . . . Automated ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automated ATP Test Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATP Test Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antenna Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATP Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reload MCC Following TX Testing of Redundant BBX Card Using Standard Test Pattern, Software Release 2.18.0.x . . . . . . . . . . . . . . . . . Individual Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX and RX Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Individual Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Spectral Purity Transmit Mask Acceptance Test . . . . . . . . . . . . . . . . . . . . . Tx Mask Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Waveform Quality (rho) Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . . Rho Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Pilot Time Offset Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pilot Offset Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Code Domain Power/Noise Floor Acceptance Test . . . . . . . . . . . . . . . . . . . Code Domain Power Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CD Power/Noise FloorTest Failures with Agilent E7495A/B Test Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RX Frame Error Rate (FER) Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . . FER Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receive Signal Strength Indication (RSSI) Acceptance Test . . . . . . . . . . . . . . . Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSSI Acceptance Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generate an ATP Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATP Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1 4-1 4-2 4-3 4-3 4-3 4-3 4-4 4-5 4-6 4-7 4-8 4-8 4-8 4-10 4-10 4-12 4-12 4-13 4-13 4-14 4-14 4-14 4-16 4-16 4-17 4-17 4-18 4-19 4-19 4-19
Table of Contents
continued
Notes
SEP 2009
Acceptance Test Procedures Introduction Acceptance Test Procedures Introduction

Introduction
General The Acceptance Test Procedures (ATP) allow Cellular Field Engineers (CFEs) to run automated acceptance tests on all BTS subsystem devices equipped in the CDF using the LMF and the test equipment it supports. LMF User Interface This chapter provides procedures for performing acceptance testing from the LMF GUI environment, the recommended method. The GUI provides the advantages of simplifying the LMF user interface, reducing the potential for miskeying commmands and associated parameters, and speeding up the execution of complex operations involving multiple command strings. If it is believed the LMF command line interface (CLI) will provide additional insight into ATP operation or unexpected test results, refer to LMF CLI Reference. Test Reports The CFE can choose to save the results of ATP tests to a report file from which ATP reports are generated for later printing. See the Generating an ATP Report section in this chapter. Test Equipment Selection Because test equipment functions during acceptance testing are controlled by the LMF through the GPIB, only the test equipment models supported by the LMF can be used. CAUTION 1. Before using the LMF, read the Developer Release Notes for WinLMF section in the LMF Help function online documentation (part of the Local Maintenance Facility (LMF) software application) for any applicable information. Pay particular attention to the Caveats/Known Issues part of this section. 2. The ATP test is to be performed on out-of-service sectors only. 3. DO NOT substitute test equipment with other models not supported by the LMF.
Test Equipment Set Calibration Refer to Chapter 3 for detailed interconnection information needed for calibrating equipment, cables, and other test equipment set components.
Acceptance Test Procedures Introduction

Reduced ATP
continued
NOTE Equipment has been factorytested for FCC compliance. If licensegoverning bodies require documentation supporting BTS site compliance with regulations, a full ATP may be necessary. Perform the Reduced ATP only if reports for the specific BTS site are NOT required. After downloading the proper operational software to the BTS, the CFE must perform these procedures (minimal recommendation): 1. Verify the TX/RX paths by performing TX Calibration, TX Audit, and the Code Domain Power and FER tests. 2. Be sure calibration data for all equipped carrier sectors is obtained and loaded on the OMCR (packet) or CBSC (circuit) for normal site operation. Failures During Testing Should failures occur while performing the specified tests, refer to the Basic Troubleshooting section of this manual for help in determining the failure point. Once the point of failure has been identified and corrected, refer to the FRU Optimization and ATP Test Matrix (Table C-3) in Appendix C to determine the applicable test that must be performed. In the unlikely event that the BTS passes these tests but has a forward link problem during normal operation, the CFE should then perform the additional TX tests for troubleshooting: TX spectral mask, TX rho, and TX code domain.
4-2
SEP 2009
Automated Acceptance Test Procedures TX & RX Automated Acceptance Test Procedures TX & RX
Automated ATP
This section covers the general requirements and procedures for conducting both automated ATP testing and performing individual ATP tests.
Automated ATP Test Options
Acceptance tests can be run individually or as one of the following automated groups:
S All TX: TX tests verify the performance of the BTS transmit line up.
These include the GLI, MCC, BBX, and MCIO cards, the PAs and passive components including ETMs, (S)PLCs, TX filters, and RF cables.
S All RX: RX tests verify the performance of the BTS receiver line up.
These include the MPC (for starter frames), EMPC (for expansion frames), MCIO, BBX, MCC, and GLI cards and the passive components including RX filters (starter frame only), and RF cables.
S All TX/RX: Executes all the TX and RX tests. S Full Optimization: Executes the TX calibration, downloads the BLO,
and executes the TX audit before running all of the TX and RX tests. NOTE The Full Optimization test can be run if TX path calibration is needed before the TX and RX acceptance tests are run. If manual testing has been performed with the HP analyzer, remove the manual control/system memory card from the card slot and set the I/O Config to the Talk & Lstn mode before starting the automated testing. The STOP button can be used to stop the testing process.
Required Test Equipment
The following test equipment is required:
S LMF S Power meter (used with HP8921A/600 and Advantest R3465) S Communications system analyzer S Signal generator for FER testing (required for all communications
system analyzers except the Agilent E7495A/B for 1X FER for 1X FER)
4-3
Automated Acceptance Test Procedures TX & RX

WARNING
continued
S Before installing any test equipment directly to any

BTS TX OUT connector, verify that there are no CDMA channels keyed.
S At active sites, have the OMCR operator place the
carrier assigned to the PAs under test OOS. Failure to do so can result in serious personal injury and/or equipment damage.
NOTE Test equipment must be recalibrated before using it to perform acceptance tests.
4
ATP Test Prerequisites
NOTE For the SC4812TMC BTS, all CLPA modules in a 3sector frame must be INS during any TX testing. In a 6sector frame, all CLPA modules sharing a trunked group must be INS during any TX testing. There are two trunked groups in a 6 sector frame. Group one includes MCM1, CLPA modules in slots 1 and 2 and sectors 13 of the frame, Group two includes MCM2, CLPA modules in slots 3 and 4 and sectors 46 of the frame. Before attempting to run any ATP tests, ensure the following have been completed:
S BTS has been optimized (BBXs calibrated and BLOs downloaded)

(Chapter 3)
S The carrier(s) and/or sector(s) to be tested have been taken out of

service at the OMCR
S S S S S S S S
LMF is logged into the BTS. CSMs, GLIs, BBXs, and MCCs have correct code and data loads Primary CSM and GLI are INS_ACT (light green in LMF) MCCs are INS_ACT (light green in LMF) BBXs are OOS_RAM (yellow in LMF) No BBXs are keyed (not transmitting) Test cables are calibrated Test equipment is connected for ATP tests (refer to ATP Test Setup illustrations in the Test Equipment Set Up section of Chapter 3). and calibrated.
S Test equipment has been selected in the LMF, warmed up 60 minutes,

continued
S GPIB is on (not required for Agilent E7495A) S All required Ethernet test equipment connections are made S BTS transmit connectors are properly terminated for the test(s) to be
performed WARNING 1. All transmit connectors must be properly terminated for all ATP tests. 2. Before a FER test is run, be sure that one of the following is done: All transmitter connectors are properly terminated OR All LPAs are turned OFF (circuit breakers pulled) Failure to observe these warnings may result in bodily injury or equipment damage.
Antenna Connectors
All acceptance testing requires test equipment connections to the BTS antenna TX or RX connectors. Refer to the ATP Test Setup illustrations in the Test Equipment Set Up section of Chapter 3 for specific connection requirements
SEP 2009
4-5

ATP Test Procedure
continued
Follow the procedure in Table 4-1 to perform any ATP test. Table 4-1: ATP Test Procedure n Step 1 2 Be sure all prerequisites have been met. Select the BTS device(s) to be tested. Action
* IMPORTANT
All PAs must be enabled during TX testing.
NOTE
If the LMF has been logged into the BTS with a different MultiChannel Preselector setting than the one to be used for this test, the LMF must be logged out of the BTS and logged in again with the new MultiChannel Preselector setting. Using the wrong MPC setting can cause a false test failure. 3 4 From the Tests menu, select the test to be run. Select the appropriate carrier (carrier-bts#-sector#-carrier#) displayed in the Channels/Carrier pick list.
NOTE
To select multiple items, hold down the <Shift> or <Ctrl> key while making the selections. 5 Enter the appropriate channel number in the Carrier n Channels box. The default channel number displayed is determined by the CdmaChans[n] number in the cbscn.cdf file for the BTS. If applicable, select Verify BLO (default) or Singlesided BLO.
NOTE
Singlesided BLO is only used when checking nonredundant transceivers. 7 If applicable, select a test pattern from the Test Pattern pick list.
NOTE S Selecting Pilot (default) performs tests using only a pilot signal. S Selecting Standard performs tests using pilot, synch, paging, and 6 traffic channels. This
requires an MCC to be selected.
S Selecting CDFPilot performs tests using only a pilot signal, however, the gain for the channel
elements is specified in the CDF file.
S Selecting CDF performs tests using pilot, synch, paging, and 6 traffic channels, however, the
gain for the channel elements is specified in the CDF file. table continued on next page
continued
Table 4-1: ATP Test Procedure n Step 8 9 10 Action Click on the OK button. The status report window and a Directions pop-up are displayed. Follow the cable connection directions as they are displayed. The test results are displayed in the status report window. Click on Save Results or Dismiss.
NOTE
If Dismiss is used, the test results will not be saved in the test report file.
4
Reload MCC Following TX Testing of Redundant BBX Card Using Standard Test Pattern, Software Release 2.18.0.x
For software release 2.18.0.x, any MCCs supporting BBXR card transmit tests using the Standard test pattern must be reloaded with data before performing CD power/noise floor testing on a primary BBX card. CAUTION In software release 2.18.0.x, failure to reload data into MCC cards which supported BBXR TX testing using the Standard test pattern will result in CD power/noise floor test failures for subsequently tested primary BBX cards. Reload affected MCCs with data as specified in the following procedure. Table 4-2: Reload Affected MCC(s) with Data After Redundant BBX TX Testing with Standard Test Pattern Step 1 2 3 4 Select the applicable MCCs. From the BTS tab menu bar, select Device > Disable/Deactivate. Download data to the applicable MCC(s) by following the code load procedure in Table 3-14. After data download is complete, select Device > Enable/Activate from the BTS tab menu bar. Action
SEP 2009
4-7
Individual Tests Individual Tests

TX and RX Testing
The following individual ATP tests can be used to evaluate specific aspects of BTS operation against individual performance requirements. All testing is performed using the LMF GUI environment. TX Testing TX tests verify transmit antenna paths and output power control. All tests are performed using the external, calibrated test equipment. All measurements are made at the appropriate BTS TX OUT connector(s). TX tests verify TX operation of the entire CDMA forward link using selected BBXs assigned to respective sector antennas. Each BBX is keyed up to generate a CDMA carrier (using both bbxlevel and BLO) at the CDF or NEC filespecified carrier output power level. RX Testing RX testing verifies receive antenna paths for BBXs selected for the test. All tests are performed using the external, calibrated test equipment to inject a CDMA RF carrier with all zero longcode at the specified RX frequency at the appropriate BTS RX IN connector(s). RX tests verify RX operation of the entire CDMA reverse link.
Individual Tests
Spectral Purity TX Mask (Primary & Redundant BBX) This test verifies that the transmitted CDMA carrier waveform generated on each sector meets the transmit spectral mask specification with respect to the assigned CDF or NEC file values. Waveform Quality (Rho) This test verifies that the transmitted Pilot channel element digital waveform quality (rho) exceeds the minimum specified value in IS97. Rho represents the correlation between the actual and perfect CDMA modulation spectrums. 1.0000 represents 100% (or perfect correlation). Pilot Time Offset The Pilot Time Offset is the difference between the CDMA analyzer measurement interval (based on the BTS system time reference) and the incoming block of transmitted data from the BTS (Pilot only, Pilot Gain = 262, PN Offset = 0). Code Domain Power/Noise Floor This test verifies the code domain power levels, which have been set for all ODD numbered Walsh channels, using the OCNS command. This is done by verifying that the ratio of PILOT divided by OCNS is equal to 10.2 + 2 dB, and, that the noise floor of all EVEN numbered OFF Walsh channels measures < 27 dB for IS95A/B and CDMA2000 1X with respect to total CDMA channel power.
Individual Tests
continued
Frame Error Rate (FER) The Frame Error Rate (FER) test verifies RX operation of the entire CDMA Reverse Link using all equipped MCCs assigned to all respective sectors/antennas. This test verifies the BTS sensitivity on all traffic channel elements currently configured on all equipped MCCs at an RF input level of 119 dBm (or 116 dBm if using TMPC). NOTE There are no pass/fail criteria associated with FER readings taken at levels below 119 dBm, other than to verify that the FER measurement reflects changes in the RX input signal level.
Receive Signal Strength Indication (RSSI) This test verifies the gain for BTS reverse (RX) paths for each carriersector selected is within requirements for correct BBX receiver operation for the operating band of the BTS as follows:
S 800 MHz: +15 dB (65 dBm or greater) S 1900 and 2100 MHz: +9 dB (71 dBm or greater)
SEP 2009
4-9
TX Spectral Purity Transmit Mask Acceptance Test TX Spectral Purity Transmit Mask Acceptance Test
Tx Mask Test
This test verifies the spectral purity of each BBX carrier keyed up at a specific frequency, per the current NEC file assignment. All tests are performed using the external calibrated test set, controlled by the same command. All measurements are via the appropriate TX OUT connector. The Pilot Gain is set to 541 for each antenna, and all channel elements from the MCCs are forward-link disabled. The BBX is keyed up, using both bbxlvl and bay level offsets, to generate a CDMA carrier (with pilot channel element only). BBX power output is set to obtain +40 dBm as measured at the TX OUT connector (on the BTS directional coupler).
NOTE TX output power is set to +40 dBm by setting BTS power level to +33.5 dBm to compensate for 6.5 dB increase from pilot gain set to 541. The calibrated communications test set measures and returns the attenuation level of all spurious and IM products in a 30 kHz resolution bandwidth. With respect to the mean power of the CDMA channel measured in a 1.23 MHz bandwidth in dB, verify that results meet system tolerances at the following test points: at least 45 dB @ + 750 kHz from center frequency at least 45 dB @ 750 kHz from center frequency at least 60 dB @ 1980 kHz from center frequency at least 60 dB @ 1980 kHz from center frequency The BBX then de-keys, and, if selected, the MCC is re-configured to assign the applicable redundant BBX to the current TX antenna path under test. The test is then repeated. See Table 4-1 to perform this test.
4-10
SEP 2009
TX Spectral Purity Transmit Mask Acceptance Test

Figure 4-1: TX Mask Verification Spectrum Analyzer Display
continued
.5 MHz Span/Div Ampl 10 dB/Div
Mean CDMA Bandwidth Power Reference Center Frequency Reference
4
Attenuation level of all spurious and IM products with respect to the mean power of the CDMA channel
1980 kHz kHz 1980 900 kHz 750 900 kHz kHz 750 kHz
+ 1980 kHz + kHz 1980 kHz + 900 +750 + 900kHz kHz +750 kHz
FW00282
SEP 2009
4-11
TX Waveform Quality (rho) Acceptance Test TX Waveform Quality (rho) Acceptance Test
Rho Test
This test verifies the transmitted Pilot channel element digital waveform quality of each BBX carrier keyed up at a specific frequency per the current CDF file assignment. All tests are performed using the external calibrated test set controlled by the same command. All measurements are via the appropriate TX OUT connector. The Pilot Gain is set to 262 for each antenna, and all channel elements from the MCCs are forward link disabled. The BBX is keyed up using both bbxlvl and bay level offsets, to generate a CDMA carrier (with pilot channel element only, Walsh code 0). BBX power output is set to 40 dBm as measured at the TX OUT connector (on the BTS directional coupler). The calibrated communications test set measures and returns the Pilot channel element digital waveform quality (rho) in dB, verifying that the result meets system tolerances:
S Waveform quality (rho) should be w 0.912 (0.4 dB).

The BBX then de-keys and, if selected, the MCC is re-configured to assign the applicable redundant BBX to the current TX antenna path under test. The test is then be repeated. See Table 4-1 to perform this test.
4-12
SEP 2009
TX Pilot Time Offset Acceptance Test TX Pilot Time Offset Acceptance Test
Pilot Offset Test
This test verifies the transmitted Pilot channel element Pilot Time Offset of each BBX carrier keyed up at a specific frequency per the current CDF file assignment. All tests are performed using the external calibrated test set controlled by the same command. All measurements are via the appropriate TX OUT connector. The Pilot Gain is set to 262 for each antenna, and all TCH elements from the MCCs are forward link disabled. The BBX is keyed up, using both bbxlvl and bay level offsets, to generate a CDMA carrier (with pilot channel element only, Walsh code 0). BBX power output is set to 40 dBm as measured at the TX OUT connector (on either the BTS or RFDS directional coupler). The calibrated communications test set measures and returns the Pilot Time Offset in s, verifying results meet system tolerances:
S Pilot Time Offset should be within + 3 s of the target PT

Offset (0 s). The BBX then de-keys, and if selected, the MCC is re-configured to assign the applicable redundant BBX to the current TX antenna path under test. The test is then repeated. See Table 4-1 to perform this test.
SEP 2009
4-13
TX Code Domain Power/Noise Floor Acceptance Test TX Code Domain Power/Noise Floor Acceptance Test
Code Domain Power Test
This test verifies the Code Domain (CD) power/noise floor of each BBX carrier transmitting at a specific frequency as listed in the current CDF file assignment. All tests are performed using the external calibrated test set controlled by the same command. All measurements are via the appropriate TX OUT connector. For each sector/antenna under test, the Pilot Gain is set to 262. All MCC channel elements under test are configured to generate Orthogonal Channel Noise Source (OCNS) on different odd Walsh codes and to be assigned a fullrate gain of 81. The maximum number of MCC Channel Elements (CE) to be tested at any one time is 32 (32 odd Walsh codes). If more than 32 CEs exist, then multiple sets of measurements are made to verify all CEs on all sectors. BBX power output is set to 40 dBm as measured at the TX OUT connector. Verify the code domain power levels, which have been set for all ODD numbered Walsh channels, using the OCNS command. This is done by verifying that Pilot Power (dBm) minus OCNS Power (dBm) is equal to 10.2 + 2 dB and that the noise floor of all OFF Walsh channels measures < 27 dB (with respect to total CDMA channel power). NOTE When performing this test using the LMF and the MCC is an MCC8E or MCC24E, the redundant BBX may fail or show marginal performance. This is due to a timing mismatch that the LMF does not address. Performing this test from the CBSC will not have this timing problem. After all channels are tested, the BBX(s) under test are de-keyed, and the redundant BBX (BBXR), if selected, is assigned to the current TX antenna path under test. The test is then repeated. Upon completion of the test, OCNS is disabled on the specified MCC CE. NOTE If using Advantest test equipment, Code Domain Test MUST be configured in RC1 mode. See Table 4-1 to perform this test.
CD Power/Noise FloorTest Failures with Agilent E7495A/B Test Set
If this test fails when using an Agilent E7495A/B test set, refer to Table 7-17 in the Troubleshooting: Transmit ATP section of Chapter 7.
TX Code Domain Power/Noise Floor Acceptance Test

Figure 4-2: Code Domain Power and Noise Floor Levels
PILOT CHANNEL
MAX OCNS CHANNEL 8.2 dB
continued
PILOT LEVEL 12.2 dB MAX OCNS SPEC. MIN OCNS SPEC.
ACTIVE CHANNELS
MIN OCNS CHANNEL MAX NOISE FLOOR
MAXIMUM NOISE FLOOR: < 27 dB SPEC.
INACTIVE CHANNELS
Walsh 0 1 2 3 4 5 6 7
...
64
SHOWING ALL OCNS PASSING
PILOT CHANNEL
FAILURE EXCEEDS MAX OCNS SPEC. 8.2 dB
PILOT LEVEL 12.2 dB MAX OCNS SPEC. MIN OCNS SPEC.
ACTIVE CHANNELS
FAILURE DOES NOT MEET MIN OCNS SPEC.
FAILURE EXCEEDS MAX NOISE FLOOR SPEC. MAXIMUM NOISE FLOOR: < 27 dB
INACTIVE CHANNELS
Walsh 0 1 2 3 4 5 6 7
...
64
INDICATING FAILURES
FW00283
SEP 2009
4-15
RX Frame Error Rate (FER) Acceptance Test RX Frame Error Rate (FER) Acceptance Test
FER Test
This test verifies the BTS FER on all traffic channel elements currently configured on all equipped MCCs (full rate at 1% FER) at an RF input level of 119 dBm [or 116 dBm if using Tower Top Amplifier (TMPC)]. All tests are performed using the external calibrated test set as the signal source controlled by the same command. All measurements are through the LMF. The Pilot Gain is set to 262 for each TX antenna, and all channel elements from the MCCs are forward-link disabled. The BBX is keyed up, using only bbxlvl level offsets, to generate a CDMA carrier (with pilot channel element only). BBX power output is set to 20 dBm as measured at the TX OUT connector. The BBX must be keyed to enable the RX receive circuitry. The LMF prompts the MCC/CE under test to measure all zero longcode and provide the FER report on the selected active MCC on the reverse link for both the main and diversity RX antenna paths, verifying that results meet the following specification:
S FER returned less than 1% and total frames measured is 1500

All MCC/CEs selected are tested on the specified RX antenna path. The BBX then de-keys and, if selected, the MCC is re-configured to assign the applicable redundant BBX to the current RX antenna paths under test. The test is then repeated. See Table 4-1 to perform this test.
4-16
SEP 2009
Receive Signal Strength Indication (RSSI) Acceptance Test Receive Signal Strength Indication (RSSI) Acceptance Test
Background
Overview This test verifies Receive Signal Strength Indication (RSSI) for the selected sectors to ensure integrity of the reverse (RX) path and that path losses are within tolerances required for correct receiver operation. Testing is performed using the calibrated external test equipment as the signal source. The test equipment is controlled by the LMF during the test. The receive signal generated by the test equipment is injected into the sector RX path to be tested at the applicable BTS main and/or diversity receive ports. Equipment operation during testing The LMF sets the pilot channel power level of the BBX for the selected sector to 150 dBm (measured at the TX port of the frame) and keys the BBX on pilot channel only to enable the RX circuitry. The LMF then commands the test equipment to generate the receive signal on the selected carrier at 80 dBm as measured at the BTS RX port. Test measurements The power level of the received signal is measured by the BBX. The LMF corrects the measured power of the signal using the RX BLO from the BBX database and determines if the corrected signal gain is equal to or greater than the following specified criteria for the band in which the BTS operates:
S 800 MHz: +15 dB (65 dBm or greater) S 1900 and 2100 MHz: +9 dB (71 dBm or greater)
Redundant BBX testing When the redundant BBX is selected for RSSI testing, the test is run on those carriersectors specified in the Channels/Carriers pick list and the receive path(s) selected in the RX Branch dropdown list (refer to Table 4-3).
SEP 2009
4-17
Receive Signal Strength Indication (RSSI) Acceptance Test

RSSI Acceptance Test
continued
Follow the steps in Table 4-3 to verify RSSI of the RX antenna paths for the required sectorcarriers. Table 4-3: Test RSSI Step 1 Action Set up the test equipment for RX acceptance tests (refer to Figure 3-17 through Figure 3-23 in the Test Equipment Setup section of Chapter 3).
n WARNING
Be sure all TX antenna ports on the BTS are properly terminated with antenna connections or RF loads. Failure to properly terminate transmit paths can result in personnel injury and/or equipment damage. 2 If the LMF has been logged into the BTS with a different MultiChannel Preselector setting than the one to be used for this test, the LMF must be logged out of the BTS and logged in again with the new MultiChannel Preselector setting. Using the wrong MPC setting can cause a false test failure. Select the BBXs for the carriersectors to be tested. In the LMF window menu bar, click on Tests > RX > RSSI. Select the sectors and carriers to be tested in the Channels/Carriers pick list which is displayed.
3 4 5
NOTE
To select multiple carrier(s)sectors(s), hold down the Shift or Ctrl while clicking on the required items. 6 7 8 9 10 Select the RX Branch to be tested from the choices in the dropdown list provided (Both, Main, or Diversity). Enter the appropriate power level into the Generator amplitude box (default: 80 dBm) Click OK. A status bar will be displayed followed by a Directions popup window.. Follow cable connection directions as they are displayed, and click the Continue button to begin testing. Progress will be indicated in the status bar. When the test is completed, click the Save Results or Dismiss button, as required, in the Status Report window.
NOTE
If the Dismiss button is clicked, test results will not be saved in the test report file.
4-18
SEP 2009
Generate an ATP Report Generate an ATP Report

Background
Each time an ATP test is run, an ATP report is updated to include the results of the most recent ATP tests if the Save Results button is used to close the status report window. The ATP report is not updated if the status reports window is closed using the Dismiss button. NOTE The ATP report for a BTS will contain test results saved with the Save Results button. Results will be saved for the last test performed on the same: S BBX
When an ATP report for a BTS is generated, all saved test results will be included in the report.
ATP Report
S Sector S Carrier S Channel
Each time an ATP test is run, a report may be created for the BTS being tested. If a previous report exists for the BTS, it is updated with the new test results as noted above. The report includes the following for each test: S Test name S Channel number S Carrier number S Sector number S Test result S PASS or FAIL S Description information (if applicable) S Time stamp S Details/Warning information (if applicable) The report can be printed if the LMF computer is connected to a printer. Follow the procedure in the Table 4-4 to view and/or print the ATP report for a BTS. Table 4-4: Generating an ATP Report Step 1 2 Action Click on the Login tab (if not in the forefront). Select the desired BTS from the available Base Station pick list. table continued on next page
Generate an ATP Report
continued
Table 4-4: Generating an ATP Report Step 3 4 5 Action Click on the Report button. Click on a column heading to sort the report. Do one of the following:
S If a printable file copy is not desired, click on the Dismiss

button.
S If a printable file copy is required, select the desired file

type in the picklist and click on the Save button.
4-20
SEP 2009
Chapter 5: Configuring Packet BTS Transport

Table of Contents
Introduction to Packet BTS Transport Configuration . . . . . . . . . . . . . . . . . . . . . Content Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GLI3 Required Software Release, Operating Mode, and Loading Code . . . . . . Software release affect on backhaul mode . . . . . . . . . . . . . . . . . . . . . . . GLI3 operating mode affect on loading code . . . . . . . . . . . . . . . . . . . . GLI3 initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading code into GLI3 cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GLI3 Card Software Version and Backhaul Mode . . . . . . . . . . . . . . . . . . . . . . . Determine if GLI3 Card Configuration Changes Are Required . . . . . . Preloading GLI3 Cards in Packet Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure GLI3 Cards for IBR Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Items Required for BTS with Redundant GLI3 Cards . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IBR Implementation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IBR Conversion Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Convert GLI3 Cards to IBR Operation . . . . . . . . . . . . . . . . . . . . . . . . . Exception Procedure for Use When Configuration Fallback Can Not Be Overcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure GLI3 Cards for Operation with External BTS Routers . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional items for new packet BTS EBR conversion preparation . . . EBR conversion preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Convert GLI3 Cards to EBR Operation . . . . . . . . . . . . . . . . . . . . . . . . Configure GLI3 Cards for OTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assumptions and prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GLI3 OTI implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Convert GLI3 cards to OTI operation . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring BTS File Transfer Protocol Introduction . . . . . . . . . . . . . . . . . . LMF file transfer protocol setting utility . . . . . . . . . . . . . . . . . . . . . . . . Configuring BTS File Transfer Protocol New BTS Installation . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the operating file transfer protocol . . . . . . . . . . . . . . . . . . Changing the operating file transfer protocol . . . . . . . . . . . . . . . . . . . .
5-1 5-1 5-1 5-3 5-3 5-3 5-4 5-4 5-5 5-8 5-10 5-12 5-12 5-12 5-13 5-13 5-14 5-25 5-27 5-27 5-27 5-28 5-30 5-33 5-33 5-34 5-34 5-37 5-44 5-44 5-46 5-46 5-46 5-47
Table of Contents
continued
GLI3 Software Release and Backhaul Mode Worksheet . . . . . . . . . . . . . . . . . . OTI configuration settings worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtain these OTI backhaul configuration settings from the network administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Interface Card (NIC) configuration worksheet . . . . . . . . . . . . . . . . . . Record of original NIC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . OTI verification NIC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-48 5-49 5-49 5-51 5-51 5-51
SEP 2009
Introduction to Packet BTS Transport Configuration Introduction to Packet BTS Transport Configuration
There are several backhaul configurations used for traffic and control signalling transport between a packet BTS and the OMCR. For SC4812series and SC48x BTS models all of these depend on correctly setting the GLI3 card operating mode to interface with the required backhaul configuration. The backhaul configurations are: S Integrated BTS Router (IBR) S External BTS Router (EBR) S Open Transport Interface (OTI)
Content Summary
This chapter contains information and procedures necessary to configure GLI3 cards for the backhaul configuration required for a packet BTS. When additional procedures required for this are contained in other sections of this publication or in other publications, the procedures in this chapter will specify them at the point in the configuration process where they are necessary. This chapter contains procedures to accomplish the following: S Determine GLI3 card: Installed software version Operating mode Backhaul mode S Loading GLI3 cards with code for the required software release S Convert GLI3 card to IBR operation S Convert GLI3 card to EBR operation S Convert GLI3 card to OTI operation S Enable File Transfer Protocol (FTP) or Secure File Transfer Protocol (SFTP)
Applicability
When to Use GLI3 Conversion Procedures in this Chapter Procedures in this chapter are only for use in configuring GLI3 cards to interface with the transport technique for which the BTS hardware has already been configured. These include GLI3 cards in a newly installed BTS and replacement GLI3 cards in an existing nonredundant BTS. When to Use BTS Conversion Procedures from Another Publication If the BTS hardware configuration is being converted from one transport techinque to another (for example, from IBR to EBR), the procedures in the applicable BTS model conversion or upgrade manual must be used instead of the procedures in this chapter. Table 5-1, below, lists the various Motorolasupported packet BTS transport conversions along with the applicable conversion or upgrade manual title needed to perform the conversion. For more information on the applicable conversion or upgrade manuals and how to obtain them, refer to the Required Documents and Related Publications section of Chapter 1.
Introduction to Packet BTS Transport Configuration
continued
Table 5-1: Packet BTS Transport Conversions Conversion Type IBR to EBR EBR to IBR IBR to OTI EBR to OTI Use Procedures in (BTS model) BTS Packet Backhaul Upgrade (BTS model) BTS Packet Backhaul Upgrade CDMA2000 1X BTS Open Transport Interface Implementation/Conversion CDMA2000 1X BTS Open Transport Interface Implementation/Conversion
5-2
SEP 2009
GLI3 Required Software Release, Operating Mode, and Loading Code GLI3 Required Software Release, Operating Mode, and Loading Code
If a GLI3 card is not loaded with code which supports the required BTS backhaul configuration, it is necessary to load code into the card for the correct software release.
Software release affect on backhaul mode
The software release of the code loaded in a GLI card determines which packet backhaul modes the card will support. Table 5-2 lists GLI3 backhaul modes along with the earliest Motorola software release which supports each. Table 5-2: GLI3 Packet Backhaul Mode and Software Release Required Packet Backhaul Mode DUPLEX INTERNAL IWFOTI SIMPLEX IBR OTI EBR (nonredundant BTS routers) Description Required Software Release 2.16.1.x and later 2.16.4.1 and later 2.20.0.x and later 2.16.1.1 and later
EBR (redundant BTS routers)
The software release of the code loaded in a GLI3 card can be determined by following the procedure in Table 5-5.
GLI3 operating mode affect on loading code
GLI3 card operating mode determines the methods which can be used to load code into the GLI cards. Table 5-3 lists the code loading methods available in each operating mode. Table 5-3: GLI3 Code Loading Methods Based on Operating Mode Operating Mode Circuit Available Code Loading Methods 1. Download from OMCR 2. Crossload from INS_ACT GLI card in a BTS 3. Download using WinLMF application 1. Download from OMCR 2. Crossload from INS_ACT GLI card 3. Download using WinLMF application (beginning with R22.0)
5-3
Packet
SEP 2009
GLI3 Required Software Release, Operating Mode, and Loading Code

continued
GLI3 initialization
A GLI3 card will initialize in the last operating and backhaul modes in which it was functioning. This can be either of the two operating modes and any of their corresponding backhaul modes listed in Table 5-4. Table 5-4: GLI3 Backhaul Modes Operating Mode Circuit Packet MMI display bkhaul_mode Mode Designation UNKNOWN INTERNAL DUPLEX SIMPLEX IWFOTI Description
Circuit backhaul Integrated BTS Router (IBR) External BTS Router (EBR) Redundant EBR Nonredundant Open Transport Interface (OTI)
5
Loading code into GLI3 cards
The operating mode and backhaul mode of a GLI3 card can be determined by following the procedure in Table 5-5.
Unless the customer knows the operating history and the exact software release installed in them, GLI3 cards will initialize to an unknown operating mode with a software release which may not support the required backhaul mode. The code loading methods for packet mode cards listed in Table 5-3 have been changed with softare release 2.22.0.x (R22.0). Beginning with R22.0, the WinLMF has the capability to load code into a packet GLI3. The Motorolarecommended method to load GLI3 cards onsite is to use the WinLMF. To do this, the BTS must have active spans which allow the GLI3 cards to communicate with the network for DHCP purposes. The second choice is preloading GLI3 cards with the correct software release code and then transporting them to the base station site. Preloaded cards can be exchanged for the GLI3 cards installed in the BTS. The cards removed can be preloaded for the next new base station installation or for use as spares. Loading GLI3 cards with the WinLMF (Motorolarecommended) To load code to packet GLI3 cards with the WinLMF, refer to the procedure in Table 3-13. Preloading GLI3 cards (Motorolarecommended) To preload GLI3 cards with OTIcapable code, refer to the procedure in Table 5-7.
GLI3 Card Software Version and Backhaul Mode GLI3 Card Software Version and Backhaul Mode
This procedure is used to obtain the information needed to determine if the GLI3 cards installed in the BTS need:
S Code loaded for a different software release S Change of backhaul mode

Prerequisites The following are required before performing this procedure:
S S S S S
A minimum of one GLI3 card is installed in the BTS card cage The installed GLI3 card is in BTS card cage slot GLI 1 The BTS has power applied The installed GLI3 card has booted to the GLI3 prompt A working copy has been made of the Software Release and Backhaul Mode worksheet at the end of this chapter
Procedure Determine GLI3 card installed software version and backhaul mode by performing the following procedure. Table 5-5: Determine GLI3 Card Software Version and Backhaul Mode Step 1 2 3 Action If GLI3 cards are installed in more than one slot in the BTS card cage, unseat all GLI3 cards except the card in slot GLI 1. If it has not been done, start a GLI3 MMI communication session on the LMF computer with the powered GLI3 card as described in the GLI3 Card MMI Communication Session section of Chapter 1. If GLI3 cards were preloaded with code for the software release installed on the Radio Access Network (RAN), do the following: 1. Enter the preloaded software release number in the Software Version column of line 1 of Table 5-22, Software Release and Backhaul Mode Record. 2. Skip to step 9. Determine the software version loaded in the GLI3 card installed in GLI slot 1 by entering the following at the GLI3 prompt:
display version
SEP 2009
5-5
GLI3 Card Software Version and Backhaul Mode
continued
Table 5-5: Determine GLI3 Card Software Version and Backhaul Mode Step 5 Action If a response similar to the following is displayed, the GLI3 card is operating in circuit mode:
GLI3> display version 01.09.1980 20:01:59 MGLI0022 OOSSBY BTSCDMA 16.41.200.14
RAM version: 16.41.200.14 ROM version: 16.41.200.14 Built: Tue Oct 21 09:52:28 2003 il272112 Bootrom version: 16.41.200.12 Bootrom Built: Thu Oct 2 03:11:34 2003 IL270775 Bootblock version: 16.1.59.00 Bootblock Built: Wed Apr 10 07:08:06 2002 RIPCORD004 This GLI board is in RAM Booted from /nvram00/loads/gli3_ckt_rom_upgrade.elf Next boot from /nvram00/loads/gli3_ckt_rom_upgrade.elf GLI3>
5
6
Record the release number for the RAM version in the Software Version column of line 2 of Table 5-22, and skip to step 9.
NOTE
In the above example, the software release is 2.16.4.1. Later software releases use notation which is more easily understood.
5-6
SEP 2009
continued
Table 5-5: Determine GLI3 Card Software Version and Backhaul Mode Step 7 Action A GLI3 operating in packet mode will generate a response similar to the following:
GLI3> display version CC PRESENT BTSCDMA 20.00.30.42
08.08.2007 13:27:28 MGLI19021
INTERNAL RAM VERSION: 20.0.30.42 RAM Built: Tue Aug 7 10:00:00 2007 W0010711 BOOTROM VERSION: 20.00.130.26 BOOTROM Built: Wed Dec 20 11:05:06 2006 IL273595 BOOTBLOCK VERSION: 16.41.60.31 BOOTBLOCK Built: Fri Aug 27 16:50:14 2004 IL271322
SYSTEM VERSION: 2.20.0.30.42 COMMITTED VERSION: 2.20.0.30.42 NEXT VERSION: 2.20.0.30.42 BACK UP VERSION 2.20.0.30.42 CURRENT RELEASE PATH: /nvram00/screl/2.20.0.30.42/ CURRENT LIF: /nvram00/screl/2.20.0.30.42/NE_LIF.xml CURRENT IMAGE: /nvram00/screl/2.20.0.30.42/gli_ram.bin.0108 CODE SERVER: 128.0.0.1 SW UPGRADE STATE: READY GLI3>
8 9
Record the COMMITTED VERSION number in the Software Version column of line 2 of Table 5-22. Determine the backhaul mode of the GLI3 cards by entering the following at the GLI3 prompt:
display bkhaul_mode
SEP 2009
5-7
continued
Table 5-5: Determine GLI3 Card Software Version and Backhaul Mode Step 10 Action A response similar to the following will be displayed:
GLI3> display bkhaul_mode 06.08.2007 08:53:33 MGLI15502 CC PRESENT BTSCDMA 20.00.20.37
The current BTS Router Backhaul Mode is DUPLEX After the next reset, the BTS Router Backhaul Mode will be DUPLEX GLI3>
NOTE
The possible modes and their meanings are:
5
11 12
S S S S S
DUPLEX = EBR with redundant BTS routers INTERNAL = IBR IWFOTI = OTI SIMPLEX = EBR with a nonredundant BTS router UNKNOWN = circuit mode
Record the response in the Backhaul Mode column of line 2 of Table 5-22. If the software version requires updating for OTI operation, proceed to the GLI3 Operating Mode and Loading Code section, and select the method to update software based on the card operating mode (Table 5-3) and backhaul mode (Table 5-4). If there are no additional MMI communication session requirements, disconnect the MMI cable from the GLI3 MMI receptacle.
13
Determine if GLI3 Card Configuration Changes Are Required
Perform the following with the information recorded in Table 5-22. Table 5-6: Does GLI3 Card Need Configuration Change? Step 1 2 Action Compare the entries in line 2 of Table 5-22 with the line 1 entries in the same column. If there are differences in the software release, refer to Table 5-2 to determine if the code loaded in the card will support the required backhaul mode for the BTS. table continued on next page
continued
Table 5-6: Does GLI3 Card Need Configuration Change? Step 3 Action If the code will not support the required backhaul mode for the BTS, load the required software release into the card (review the GLI3 Required Software Release, Operating Mode, and Loading Code section of this chapter to determine how to proceed with loading the required software into the card). If there are differences in the backhaul mode, perform the applicable GLI3 conversion procedure on the card when the installed code will support it. GLI3 conversion procedures are:
S Configure GLI3 cards for IBR packet operation, Table 5-9, Table 5-10, and Table 5-11 S Configure GLI3 cards for operation with EBR, Table 5-14 and Table 5-15 S Configure GLI3 cards for operation with OTI backhaul, Table 5-16, Table 5-17, and Table 5-18
SEP 2009
5-9
Preloading GLI3 Cards in Packet Mode Preloading GLI3 Cards in Packet Mode
This procedure is for preloading GLI3 cards with the required software release code and data when they are operating in packet mode. It can also be used to preload cards for which the operating mode is unknown. Required items
S A test laboratory packet BTS (toy cell) or an operational packet

BTS in which the INS_ACT GLI3 card is loaded with the correct software release code
S Approved antistatic wrist strap S GLI3 cards to be preloaded and their transport packaging S Tagging materials
Preload procedure Perform the following to preload GLI3 cards for a new base station site or for use as spares.
Table 5-7: Preload GLI3 Cards Step 1 2 Action Identify the INS_SBY GLI3 card (ACT LED not lighted, STA LED slow flashing green) in the BTS card cage. Remove the card from the BTS card cage following the procedure in the Field Replaceable Unit (FRU) manual for the base station model (Refer to the Required Documents and Related Publications section of Chapter 1).
! CAUTION
Wear an approved antistatic wrist strap when performing the following. Failure to do so could result in ElectroStatic Discharge (ESD) damage to the circuit cards. Remove the GLI3 card to be preloaded from its protective packaging.
4 5 6
Follow the procedure in the base station FRU manual to install the GLI3 card in the BTS card cage slot where the INS_SBY GLI3 card was removed in step 2, above. Allow the GLI3 card to boot and reach OOS_SBY status (ACT LED not lighted, STA LED steady green). Contact the OMCR operator to request the OOS_SBY GLI3 be enabled, and ask the operator to provide notification when the action is complete.
NOTE
Enabling the card will cause code to download to the card if the current loads in the card do not match those required for the BTS. Wait at least 17 minutes for the card to complete this operation and/or the STA indicator to change to slow flashing green before proceeding beyond the next step. table continued on next page
Preloading GLI3 Cards in Packet Mode
continued
Table 5-7: Preload GLI3 Cards Step 7 8 9 10 11 12 Action When notified that the GLI3 is enabled, visually verify when the GLI3 card has changed to INS_SBY (ACT LED not lighted, STA LED slow flashing green). Remove the preloaded INS_SBY GLI3 card from the BTS card cage following the procedure in the base station FRU manual. Place the preloaded GLI3 card in the original protective packaging for transport to the new BTS site. Tag the packaging for the preloaded card to identify the preloaded software release code and data. If other GLI3 cards must be preloaded, repeat steps 3 through 10 for each additional card. When all cards have been preloaded, reinstall the GLI3 card originally removed from the BTS card cage in step 2, above.
SEP 2009
5-11
Configure GLI3 Cards for IBR Operation Configure GLI3 Cards for IBR Operation
This section covers the actions needed to configure GLI3 cards for IBR packet operation. Procedures unique to this process are contained in this section. When procedures required for this process are contained in other parts of this publication or in other publications, specifically direction to them will be provided at the appropriate places in this section.
Items Required for BTS with Redundant GLI3 Cards
If it is not already installed in the BTS, the following item is required to support OMCR communication with the INS_SBY GLI during normal redundant BTS operation: Table 5-8: Item Required for BTS Redundant GLI Cabling Integrated BTS Router Group Item Double Crossover Accessory Cable Assembly Item Number SGKN4408 Qty 1 Description Consists of GLItoGLI FE cable 3088643C28. Category 5E Ethernet transceiver cable, double crossover, 2624 AWG, unshielded twisted pair, 0.3 m (12 in.), two 8contact modular plugs
Prerequisites
The following must be accomplished before traveling to the BTS site for IBR implementation:
S The BTS has been installed as described in the BTS hardware
installation manual for the BTS type (refer to the Required Documents and Related Publications section of Chapter 1) software installed
S GLI3 cards for the site have been verified as having IBRcapable S GLI3 card(s) are installed in the BTS S The BTS has power applied S The file transfer protocol setting required for operating the BTS (either
FTP or Secure FTP (SFTP)) on the network has been verified with the OMCR provisioning and network operators policy and installed
S Number and types of spans required at the site have been determined S If a fractional span is to be used, the starting and ending DS0 numbers
provisioned on the OMCR have been obtained
S Required publications to support IBR implementation activities are on

hand for transportation to the BTS site (refer to the Required Documents and Related Publications section of Chapter 1)
5-12
SEP 2009
Configure GLI3 Cards for IBR Operation

IBR Implementation Overview
continued
Addition of fractional span support for IBRequipped packet BTS in R18.0 has made IBR implementation at the BTS a twopart process. The parts are: 1. Preparation actions 2. Configure GLI3 cards for IBR operation in either: Full span or Fractional span configuration
IBR Conversion Preparation
Follow the procedure in Table 5-9 to prepare the site for configuring the GLI3 card(s) for IBR operation. Table 5-9: IBR Configuration Preparation Step 1 2 3 4 5 Action Contact the OMCR and notify the operator that GLI3 transport configuration operations are starting. With the BTS fully powered up, the GLI3 card(s) should have been seated in the correct slots. If not, seat the card(s) at this time and allow each to complete its initialization. Make sure the GLItoGLI double crossover Fast Ethernet (FE) cable (Table 5-8) is installed between in the GLI connectors of the GLI3 cards If it was not previously done, follow the procedure in Table 5-5 to verify the software version in the GLI3 card(s) If the GLI3 software requires upgrading for IBR capability, review the GLI3 Required Software Release, Operating Mode, and Loading Code section of this chapter to determine how to proceed with loading IBRcapable software into the card.
NOTE
Only one card in a BTS with redundant GLI3s is required to have IBRcapable software. This card must be the INS_ACT card (shows light green in the LMF) in the BTS. The INS_ACT GLI will be the first card in the BTS which is downloaded with code and data from the LMF. The INS_ACT GLI3 will crossload the correct software to the INS_SBY GLI3. 6 7 Refer to the site documentation for IBR spans and inspect the BTS span cabling connections to be sure they match the requirements. Correct any cabling discrepancies between the BTS span cabling and site documentation, referring to the BTS hardware installation or packet backhaul upgrade manual as needed (Required Documents and Related Publications section of Chapter 1). If it has not already been done, follow the procedure in Table 3-10 to establish an MMI communication session with the INS_ACT GLI3 card. table continued on next page
continued
Table 5-9: IBR Configuration Preparation Step 9 Action Configure the file transfer protocol settings for each GLI3 card to match what is required for network operation by performing the Configuring BTS File Transfer Protocol New BTS Installation procedure in thchapter. To complete the IBR conversion, perform one of the following, depending on what span configuration has been provisioned for the BTS at the OMCR:
10
S If the BTS is provisioned with one or two full spans (24 DS0 for T1, 31 DS0 for E1), perform the
procedure in Table 5-10.
S If the BTS is provisioned with a fractional span (less than 24 DS0 for T1, less than 31 DS0 for E1),
perform the procedure in Table 5-11.
Convert GLI3 Cards to IBR Operation
The procedure used to convert GLI3 cards to IBR operation depends on the required span configuration (span_config) for the BTS:
S For a BTS provisioned with full span(s), use the procedure in

Table 5-10 Table 5-11
S For a BTS provisioned with a fractional span, use the procedure in
5-14
SEP 2009
continued
Full Span(s) IBR Conversion To convert GLI3 cards in a BTS provisioned with full span(s) to IBR, follow the procedure in Table 5-10. Table 5-10: IBR Conversion BTS Provisioned with Full Span(s) Step 1 2 Action If it has not already been done, follow the procedure in Table 3-10 to establish an MMI communication session with the INS_SBY GLI3 card, depending on the frame redundancy: Enter the following at the GLI3 prompt to convert the GLI3 cards to IBR operation with full span(s):
convert_ibr
The system will display responses similar to the following:

GLI3> convert_ibr
PARTIAL SYNTAX: convert_ibr span_type span_eq Next available options: LIST spanType : span Type E1_1 : E1_1 E1 HDB3, CRC4 Framing 31TS (default for E1) E1_2 : E1_2 E1 HDB3, Double Framing 31TS T1_2 : T1_2 T1 ESF Framing, B8ZS (default for T1) T1_3 : T1_3 T1 SF Framing, AMI, SW JBZS current : Use current spanType >
To set or change the span type, enter the correct option from the list at the entry prompt (>), as shown in the following example:
> T1_2
NOTE
If the span type should not change from what is currently set, enter current. table continued on next page
SEP 2009
5-15
continued
Table 5-10: IBR Conversion BTS Provisioned with Full Span(s) Step 4 Action The terminal will display a response similar to the following:
> T1_2 PARTIAL SYNTAX: convert_ibr T1_2 Next available options: LIST spanEq : Span Equalization T1_1 : T1 Short Haul mode, 0131 feet (default for T1) T1_2 : T1 Short Haul mode, 132262 feet T1_3 : T1 Short Haul mode, 263393 T1_4 : T1 Short Haul mode, 394524 T1_5 : T1 Short Haul mode, 525655 E1_120 : E1 Short Haul mode, 120 ohm (default for E1) T1_0DB : T1 Long Haul mode, LBO = 0 dB T1_7_5DB : T1 Long Haul mode, LBO = 7.5 dB T1_15DB : T1 Long Haul mode, LBO = 15 dB current : Use current spanEq >
Select the required equalization for the span type selected from the list and enter it at the prompt as shown in the following example:
> T1_1
NOTE
If the span equalization should not change from what is currently set, enter current. 6 After selecting the required equalization for the span, the terminal will display a response similar to the following:
> T1_1 PARTIAL SYNTAX: convert_ibr T1_2 T1_1 Next available options: LIST span_config : Span A full configuration full_span : Full span configuration will be used on reset to IBR mode. RANGE startDS0 : SPAN A startDS0 value*Value set is ignored except in Fractional Span pBTSIBR mode(R18.0+) 1 31 >
For a BTS provisioned with full spans, accept the default setting full_span by pressing the Enter key. table continued on next page
5-16
SEP 2009
continued
Table 5-10: IBR Conversion BTS Provisioned with Full Span(s) Step 8 Action After entering the span_config, a warning and a series of actions will be displayed similar to the following example:
> full_span 01.06.1980 00:13:05 MGLI0041 CC PRESENT BTSCDMA 18.00.00.75
WARNING!!! This MMI is changing the GLI configuration. Removing file: /nvram00/config/bootcfg.txt Successfully removed file: /nvram00/config/bootcfg.txt Removing file: /nvram00/config/hlp_param.txt Successfully removed file: /nvram00/config/hlp_param.txt Removing file: /nvram00/config/ospf_cfg.txt Successfully removed file: /nvram00/config/ospf_cfg.txt Removing file: /nvram00/config/ran_fail_cfg.txt Successfully removed file: /nvram00/config/ran_fail_cfg.txt Setting backhaul mode to IBR Successfully set backhaul mode to: IBR Setting spanType to: T1_2 Successfully set spanType to: T1_2 Setting spanEq to: T1_1 Successfully set spanEq to: T1_1 Setting SPAN A to FULL span configuration. Successfully set SPAN A to FULL span configuration. To complete the conversion to IBR, this GLI must be reset!
NOTE
Parameters which were entered in error will be identified after the final parameter is entered. Errors will be reported by responses similar to the following:
ERROR: Unsupported Span Type: J1_1. Unsupported span types for IBR: E1_3, E1_4, J1_1, J1_2 & T1_1 Supported IBR Span Types: E1_1, E1_2, T1_2 & T1_3 Conversion to IBR failed!
Perform the following: 1. Disconnect the MMI cable from the INS_SBY card 2. Connect it to the INS_ACT GLI3 card 3. Establish MMI communication by pressing the Enter key to display the GLI3 > prompt table continued on next page
SEP 2009
5-17
continued
Table 5-10: IBR Conversion BTS Provisioned with Full Span(s) Step 10 11 12 Action Repeat steps 1 through 8 of this table for the INS_ACT GLI card, and then proceed to step 11, below. Reconnect the MMI cable to the INS_SBY GLI3 and press the Enter key to display the GLI3 > prompt.
NOTE
For redundant BTS frames, the INS_SBY GLI3 must be reset first. The INS_ACT GLI3 card must then be reset (step 13) within approximately 45 seconds of the INS_SBY GLI3 (step 12) to make sure neither card reboots with configuration files for operation with external BTS routers or circuit mode. If one GLI3 completes initialization before the other is reset, steps 1 through 8 must be repeated for both cards and both must be reset again. Use the MMI reset command to reset the GLI3 card where the MMI cable is connected.
13
Perform the following within 45 seconds of resetting the INS_SBY GLI3: 1. 2. 3. 4. Disconnect the MMI cable from the INS_SBY GLI3 Connect the MMI cable to the INS_ACT GLI3 Press the Enter key to display the GLI3 > prompt Reset the card using the MMI reset command
NOTE
In a redundant frame, if the INS_ACT GLI3 cannot be reset before the INS_SBY GLI3 completes its reboot, perform steps 1 through 8 again for each card, reset the INS_SBY GLI3, and then reset the INS_ACT GLI3 using the hardware RESET button on the front of each card. 14
NOTE
Upon rebooting after the convert_ibr operation, the GLI3 cards will begin sending Dynamic Host Control Protocol (DHCP) requests over their backplane span connections. If they do not receive a response within 50 minutes (redundant cards) or 25 minutes (nonredundant cards), they will automatically reset to their previous backhaul mode (configuration fallback). The BTS must be placed under OMCR control and initialized in packet mode within these times or the convert_ibr operation must be performed again. If continual problems are experienced with GLI3 configuration fallback before the OMCR can take control of the BTS, do the following for each installed GLI3 card: 1. Perform the convert_ibr operation from steps 1 through 8 for the INS_SBY card. 2. Perform the exception procedure in Table 5-12 for the INS_SBY card. 3. Start an MMI session with the INS_ACT card and perform steps 1 through 8. 4. Perform the exception procedure in Table 5-12 for the INS_ACT card. 5. Resume this procedure at step 12, and follow the procedure to completion. table continued on next page
5-18
SEP 2009
continued
Table 5-10: IBR Conversion BTS Provisioned with Full Span(s) Step 15 Action Wait at least 17 minutes for the cards to complete the rebooting operation and/or the STA indicator to change to slow flashing green before attempting to proceed with the next step.
NOTE
Upon its first initialization with R18.0 or later RAM code, a packet GLI3 card will reallocate flash memory space for a duplicate copy of the bootROM code. It will then write a redundant copy of the code image to the new memory area. Visual indication of this process is provided by the STA LED flashing orange at 0.5 second intervals. This onetime process can cause the card to require up to 17 minutes to complete initialization to an INS state. Once the redundant image is created on the card, the extended 17minute upgrade process will not be repeated, even if the card is later downgraded to preR18.0 software. 16 When all preparations for BTS operation are completed, contact the OMCR, notify the operator that the BTS is ready for operation, and request notification when the operator no longer requires support onsite. When advised that there is no further requirement for onsite support of BTS and IBR initialization, proceed to Chapter 6 and follow the procedures to prepare to leave the site.
17
SEP 2009
5-19
continued
Fractional Span IBR Conversion To convert GLI3 cards in a BTS provisioned with a fractional span to IBR, follow the procedure in Table 5-11. Table 5-11: IBR Conversion BTS Provisioned with Fractional Span Step 1 2 Action If it has not already been done, follow the procedure in Table 3-10 to establish an MMI communication session with the INS_SBY GLI3 card. Enter the following at the GLI3 prompt to convert the GLI3 card(s) to IBR operation with a fractional span:
convert_ibr

GLI3> convert_ibr
PARTIAL SYNTAX: convert_ibr span_type span_eq Next available options: LIST spanType : span Type E1_1 : E1_1 E1 HDB3, CRC4 Framing 31TS (default for E1) E1_2 : E1_2 E1 HDB3, Double Framing 31TS T1_2 : T1_2 T1 ESF Framing, B8ZS (default for T1) T1_3 : T1_3 T1 SF Framing, AMI, SW JBZS current : Use current spanType >
To set or change the span type, enter the correct option from the list at the entry prompt (>), as shown in the following example:
> T1_2
NOTE
If the span type should not change from what is currently set, enter current. table continued on next page
5-20
SEP 2009
continued
Table 5-11: IBR Conversion BTS Provisioned with Fractional Span Step 4 Action The terminal will display a response similar to the following:
> T1_2 PARTIAL SYNTAX: convert_ibr T1_2 Next available options: LIST spanEq : Span Equalization T1_1 : T1 Short Haul mode, 0131 feet (default for T1) T1_2 : T1 Short Haul mode, 132262 feet T1_3 : T1 Short Haul mode, 263393 T1_4 : T1 Short Haul mode, 394524 T1_5 : T1 Short Haul mode, 525655 E1_120 : E1 Short Haul mode, 120 ohm (default for E1) T1_0DB : T1 Long Haul mode, LBO = 0 dB T1_7_5DB : T1 Long Haul mode, LBO = 7.5 dB T1_15DB : T1 Long Haul mode, LBO = 15 dB current : Use current spanEq >
Select the required equalization for the span type selected from the list and enter it at the prompt as shown in the following example:
> T1_1
NOTE
If the span equalization should not change from what is currently set, enter current. 6 After selecting the required equalization for the span, the terminal will display a response similar to the following:
> T1_1 PARTIAL SYNTAX: convert_ibr T1_2 T1_1 Next available options: LIST span_config : Span A full configuration full_span : Full span configuration will be used on reset to IBR mode. RANGE startDS0 : SPAN A startDS0 value*Value set is ignored except in Fractional Span pBTSIBR mode(R18.0+) 1 31 >
SEP 2009
5-21
continued
Table 5-11: IBR Conversion BTS Provisioned with Fractional Span Step 7 Action For a BTS provisioned with a fractional span, enter the starting DS0 number for the span from the specified range of values as shown in the following example:
> 1
The terminal will display a response similar to the following:

> 1 COMMAND SYNTAX: convert_ibr T1_2 T1_1 startDS0 endDS0 Next available options: RANGE endDS0 : SPAN A endDS0 value*Value set is ignored except in Fractional Span pBTSIBR mode(R18.0+) 1 31 >
Enter the ending DS0 number for the span from the specified range of values as shown in the following example:
> 12
5-22
SEP 2009
continued
Table 5-11: IBR Conversion BTS Provisioned with Fractional Span Step 9 Action After entering the endDS0 value, a warning and a series of actions will be displayed similar to the following example:
> 12 01.06.1980 00:13:05 MGLI0041 CC PRESENT BTSCDMA 18.00.00.75
WARNING!!! This MMI is changing the GLI configuration. Removing file: /nvram00/config/bootcfg.txt Successfully removed file: /nvram00/config/bootcfg.txt Removing file: /nvram00/config/hlp_param.txt Successfully removed file: /nvram00/config/hlp_param.txt Removing file: /nvram00/config/ospf_cfg.txt Successfully removed file: /nvram00/config/ospf_cfg.txt Removing file: /nvram00/config/ran_fail_cfg.txt Successfully removed file: /nvram00/config/ran_fail_cfg.txt Setting backhaul mode to IBR Successfully set backhaul mode to: IBR Setting spanType to: T1_2 Successfully set spanType to: T1_2 Setting spanEq to: T1_1 Successfully set spanEq to: T1_1 Setting SPAN A startDS0 to: 1 Successfully set SPAN A startDS0 to: 1 Setting SPAN A endDS0 to: 12 Successfully set SPAN A endDS0 to: 12 To complete the conversion to IBR, this GLI must be reset!
NOTE
Parameters which were entered in error will be identified after the final parameter is entered. Errors will be reported by responses similar to the following:
ERROR: Unsupported Span Type: J1_1. Unsupported span types for IBR: E1_3, E1_4, J1_1, J1_2 & T1_1 Supported IBR Span Types: E1_1, E1_2, T1_2 & T1_3 Conversion to IBR failed!
SEP 2009
5-23
continued
Table 5-11: IBR Conversion BTS Provisioned with Fractional Span Step 10 Action Perform the following: 1. Disconnect the MMI cable from the INS_SBY card 2. Connect it to the INS_ACT GLI3 card 3. Establish MMI communication by pressing the Enter key to display the GLI3 > prompt Repeat steps 1 through 9 for the INS_ACT GLI card, and then proceed to step 12, below. For redundant frames, reconnect the MMI cable to the INS_SBY GLI3 and press the Enter key to display the GLI3 > prompt.
11 12 13
NOTE
In a redundant BTS frame, the INS_SBY GLI3 must be reset first. The INS_ACT GLI3 card must then be reset (step 14) within approximately 45 seconds of the INS_SBY GLI3 (step 13) to make sure neither card reboots with configuration files for operation with external BTS routers or circuit mode. If one GLI3 completes initialization before the other is reset, steps 1 through 9 must be repeated for both cards and both must be reset again.
5
14
Use the MMI reset command to reset the GLI3 card where the MMI cable is connected. Perform the following within 45 seconds of resetting the INS_SBY GLI3: 1. 2. 3. 4. Disconnect the MMI cable from the INS_SBY GLI3 Connect the MMI cable to the INS_ACT GLI3 Press the Enter key to display the GLI3 > prompt Reset the card using the MMI reset command
NOTE
If the INS_ACT GLI3 cannot be reset before the INS_SBY GLI3 completes its reboot, perform steps 1 through 9 again for each card, reset the INS_SBY GLI3, and then reset the INS_ACT GLI3 using the hardware RESET button on the front of each card. table continued on next page
5-24
SEP 2009
continued
Table 5-11: IBR Conversion BTS Provisioned with Fractional Span Step 15 Action
NOTE
Upon rebooting after the convert_ibr operation, the GLI3 cards will begin sending DHCP requests over their backplane span connections. If they do not receive a response within 50 minutes (redundant cards) or 25 minutes (nonredundant cards), they will automatically reset to their previous backhaul mode (configuration fallback). The BTS must be placed under OMCR control and initialized in packet mode within these times or the convert_ibr operation must be performed again. If continual problems are experienced with GLI3 configuration fallback before the OMCR can take control of the BTS, do the following for each installed GLI3 card: 1. Perform the convert_ibr operation from steps 1 through 9 for the INS_SBY card. 2. Perform the exception procedure in Table 5-12 for the INS_SBY card. 3. Start an MMI session with the INS_ACT card and perform steps 1 through 9. 4. Perform the exception procedure in Table 5-12 for the INS_ACT card. 5. Resume this procedure at step 13 of this table, and follow the procedure to completion.
16
Wait at least 17 minutes for the cards to complete the rebooting operation and/or the STA indicator to change to slow flashing green before attempting to proceed with the next step.
NOTE
Upon its first initialization with R18.0 or later RAM code, a packet GLI3 card will reallocate flash memory space for a duplicate copy of the bootROM code. It will then write a redundant copy of the code image to the new memory area. Visual indication of this process is provided by the STA LED flashing orange at 0.5 second intervals. This onetime process can cause the card to require up to 17 minutes to complete initialization to an INS state. Once the redundant image is created on the card, the extended 17minute upgrade process will not be repeated, even if the card is later downgraded to preR18.0 software. 17 When all preparations for BTS operation are completed, contact the OMCR and notify the operator that the BTS is ready for operation and request notification when the operator no longer requires support onsite. When advised that there is no further requirement for onsite support of BTS and IBR initialization, proceed to Chapter 6 and follow the procedures to prepare to leave the site.
18
Exception Procedure for Use When Configuration Fallback Can Not Be Overcome
Perform the following procedure only when directed to it by the NOTE after step 14 in Table 5-10 or step 14 in Table 5-11. This procedure is intended for use when the OMCR is continually unable to take control of the BTS before the GLI3 cards reboot to their lastknowngood configuration.
continued
IMPORTANT
This procedure should never be used unless absolutely required because it will prevent backing the BTS out of the IBR conversion if that is needed.
Table 5-12: Prevent GLI3 Configuration Fallback Step 1 2 Action If it has not been done, establish an MMI communication session with a GLI3 card by following the procedure in Table 3-10. Prevent the card from automatically rebooting to the last knowngood configuration (fallback) by entering the following commands at the GLI3> prompt in the sequence shown and pressing the ENTER key after each:
rmfile rmfile rmfile rmfile rmfile rmfile /nvram00/history/boothistory0.txt /nvram00/history/boothistory1.txt /nvram00/history/boothistory2.txt /nvram00/history/boothistory3.txt /nvram00/history/boothistory4.txt /nvram00/history/boothistory5.txt

GLI3> rmfile /nvram00/history/boothistory0.txt 09.16.2004 20:07:33 MGLI0031 CC NOT PRESENT BTSCDMA 17.00.201.22 GLI3> rmfile /nvram00/history/boothistory1.txt 09.16.2004 20:08:05 MGLI0031 CC NOT PRESENT BTSCDMA 17.00.201.22 GLI3> rmfile /nvram00/history/boothistory2.txt 09.16.2004 20:08:49 MGLI0031 CC NOT PRESENT BTSCDMA 17.00.201.22 GLI3> rmfile /nvram00/history/boothistory3.txt 09.16.2004 20:09:17 MGLI0031 CC NOT PRESENT BTSCDMA 17.00.201.22 GLI3> rmfile /nvram00/history/boothistory4.txt 09.16.2004 20:09:50 MGLI0031 CC NOT PRESENT BTSCDMA 17.00.201.22 GLI3> rmfile /nvram00/history/boothistory5.txt 09.16.2004 20:10:28 MGLI0031 CC NOT PRESENT BTSCDMA 17.00.201.22 GLI3>
Return to the table which directed using this procedure, and refer to the applicable table step of the following to resume the conversion:
S For Table 5-10, see step 14 15 NOTE S For Table 5-11, see step 15 NOTE
5-26
SEP 2009
Configure GLI3 Cards for Operation with External BTS Routers Configure GLI3 Cards for Operation with External BTS Routers
This section covers the actions needed to configure GLI3 cards for operation with External BTS Routers (EBR). Procedures in this section apply to:
S New packet BTS initialization S Replacement of a nonredundant GLI3 card

Procedures unique to this process are contained in this section. When procedures required for this process are contained in other parts of this publication or in other publications, the user will be specifically directed to them at the appropriate places in this section.
Prerequisites
The following must be done before performing this procedure:
S The BTS has been installed as described in the BTS hardware S GLI3 card(s) for the site have been verified as having
IBR/EBRcapable software installed
installation manual for the BTS type (refer to the Required Documents and Related Publications section of Chapter 1)
S GLI3 card(s) for the site are installed in the BTS S The BTS has power applied S The file transfer protocol setting required for operating the BTS (either
FTP or Secure FTP (SFTP)) on the network has been verified with the OMCR provisioning and network operators policy site documentation
S EBR span configuration required at the site has been determined from S Required publications to support conversion activities are on hand
(refer to the Required Documents and Related Publications section of Chapter 1)
Additional items for new packet BTS EBR conversion preparation
The following items are required to prepare a new BTS EBR group for the conversion: Table 5-13: Items Required for FE Cabling External BTS Router Group Item External BTS router FE connector interconnect cables
SEP 2009
Part Number Motorola 3088643C14 or equivalent
Qty 2
Description Category 5E Ethernet transceiver cable, crossover, 24 AWG, shielded twisted pair, 0.6 m (23.6 in), two 8contact modular plugs
5-27
Configure GLI3 Cards for Operation with External BTS Routers

EBR conversion preparation
continued
Do the following to prepare a new BTS for converting the GLI3 card(s) to EBR operation. Table 5-14: EBR Conversion Preparation Step 1 Action Contact the OMCR, and: 1. Notify the operator that EBR conversion preparation is starting 2. Request the operator provide notification when the OMCR is ready to initialize the BTS. If it was not previously done, verify the software version in the GLI3 card(s) as described in Chapter 4 of the packet backhaul upgrade manual for the BTS type (refer to the Required Documents and Related Publications section of Chapter 1). If it was not previously done, follow the procedure in Table 5-5 to verify the software version in the GLI3 card(s) If the GLI3 software requires upgrading for EBR capability,, review the GLI3 Required Software Release, Operating Mode, and Loading Code section of this chapter to determine how to proceed with loading IBR/EBRcapable software into the card.
3 4
NOTE
Only one card in a BTS with redundant GLI3s is required to have IBRcapable software. This card must be the INS_ACT card (shows light green in the LMF) in the BTS. The INS_ACT GLI will be the first card in the BTS which is downloaded with code and data from the LMF. The INS_ACT GLI3 will crossload the correct software to the INS_SBY GLI3. 5 6 Refer to the site documentation for EBR spans and inspect the BTS span cabling connections to be sure they match the requirements.
! CAUTION
Do not crossconnect external BTS router span cables to active spans in the termination equipment when performing the procedures in this step. Correct any cabling discrepancies between the BTS span cabling and site documentation, referring to the BTS hardware installation or packet backhaul upgrade manual as needed (Required Documents and Related Publications section of Chapter 1)..
Inspect the BTS and BTStoEBR 10/100BaseT Fast Ethernet (FE) cabling and be sure it matches the required configuration for the EBR group type installed (redundant or nonredundant) according to the hardware installation or packet backhaul upgrade manual. If the FE cabling has not yet been functionally verified, verify it as described in the Fast Ethernet Verification chapter of the packet backhaul upgrade manual for the BTS type. table continued on next page
5-28
SEP 2009
continued
Table 5-14: EBR Conversion Preparation Step 9 Action
NOTE
If it has not been done, be sure to mark the EBR end of BTStoEBR FE cables for proper reconnection before performing this step. Disconnect BTStoEBR FE cables from the EBR FE interface connectors, and use FE crossover cables (Table 5-13) to connect the EBR FE interface connectors as follows:
S FE0 of BTSRTR 1 to connector FE0 of BTSRTR2 S FE1 of BTSRTR 1 to connector FE1 of BTSRTR2
10 11 If it has not been done, apply power to the external BTS router(s) by setting the facility circuit breaker for each router to ON. Configure the GLI3 card file transfer protocol settings to match what is required for network operation by performing the Configuring BTS File Transfer Protocol New BTS Installation procedure in this chapter. Proceed to the Convert GLI3 cards to EBR operation portion of this section.
12
SEP 2009
5-29

Convert GLI3 Cards to EBR Operation
continued
When notified that the OMCR is prepared for BTS initialization, perform the following procedure. Table 5-15: Convert GLI3 Cards to EBR Operation Step 1 2 Action Following the procedure in Table 3-10, establish an MMI communication session with the INS_SBY GLI3 card. Enter the following command to configure the GLI3 card to EBR operation:
convert_ebr

GLI3> convert_ebr 11.24.2003 23:14:57 MGLI0041
CC PRESENT BTSCDMA 16.40.00.09
5
WARNING!!! This MMI is changing the GLI configuration. Removing file: /nvram00/config/bootcfg.txt Successfully removed file: /nvram00/config/bootcfg.txt Removing file: /nvram00/config/hlp_param.txt Successfully removed file: /nvram00/config/hlp_param.txt Removing file: /nvram00/config/ospf_cfg.txt Successfully removed file: /nvram00/config/ospf_cfg.txt Setting backhaul mode to EBR Successfully set backhaul mode to: EBR To complete the conversion to EBR, this GLI must be reset!
For redundant frames, perform the following: 1. Disconnect the MMI cable from the INS_SBY GLI3 card 2. Connect it to the INS_ACT GLI3 card 3. Establish MMI communication by pressing the Enter key to display the GLI3 > prompt Repeat step 2, above, for the INS_ACT GLI3 card, and then proceed to step 5, below. For redundant frames, reconnect the MMI cable to the INS_SBY GLI3 card and press the Enter key to display the GLI3 > prompt. table continued on next page
4 5
5-30
SEP 2009
continued
Table 5-15: Convert GLI3 Cards to EBR Operation Step 6 Action
NOTE
In redundant frames, the INS_SBY GLI3 card must be reset first. Then the INS_ACT GLI3 card must be reset (step 7) within approximately 45 seconds of the INS_SBY GLI3 (step 6) to make sure neither card reboots with configuration files for operation with external BTS routers. If one GLI3 completes initialization before the other is reset, steps 1 and 2 must be repeated for each card and the cards reset again. Use the MMI reset command to reset the GLI3 card where the MMI cable is connected.
Perform the following within 45 seconds of resetting the INS_SBY GLI3 card: 1. 2. 3. 4. Disconnect the MMI cable from the INS_SBY GLI3 card Connect the MMI cable to the INS_ACT GLI3 card Press the Enter key to display the GLI3 > prompt Reset the card using the MMI reset command
NOTE
If the INS_ACT GLI3 card cannot be reset before the INS_SBY GLI3 card completes its reboot, perform steps 1 through 5 again for each card, reset the INS_SBY GLI3, and then reset the INS_ACT GLI3 card using the hardware RESET button on the front of each card. 8 When both cards complete their initialization after being reset, terminate the MMI communication session and disconnect the LMF computer from the GLI3 card.
NOTE
The remaining steps in this procedure must be performed within 50 minutes (redundant cards) or 25 minutes (nonredundant card) to prevent the GLI3 cards from automatically rebooting to their last known good operating mode. If cards selfinitiate configuration fall back before the OMCR takes control, the convert_ebr procedure in steps 1 through 8 must be performed again. 9 10 Disconnect the FE crossover cables interconnecting the external BTS router FE connectors (Table 5-9, step 9) and remove the cables from the routers. Connect the FE cabling between the external BTS router FE connectors and the BTS FE interface housing or ESM EXTERNAL connectors according to the cable markings and the applicable procedure in the packet backhaul upgrade manual for the BTS type. Crossconnect each external BTS router span cable or span Ycable to the specified site span in the termination equipment (refer to the span connection section of the packet backhaul upgrade manual for the BTS type). Connect the ground lug for each router span cable or span Ycable to the ground stud at the termination equipment. table continued on next page
11
12
SEP 2009
5-31

Table 5-15: Convert GLI3 Cards to EBR Operation Step 13 14 Action
continued
Verify BTS router span cable connections with site documentation and the span connection section of the packet backhaul upgrade manual for the BTS type, as applicable. Contact the OMCR and advise the operator that:
S The convert_ebr command has been executed on the GLI3 card(s) S All EBR cabling is complete S The site is ready for operational verification
15 When advised that there is no further requirement for onsite support of EBR initialization, proceed to Chapter 6, and follow the procedures to prepare to leave the site.
5-32
SEP 2009
Configure GLI3 Cards for OTI Configure GLI3 Cards for OTI
This section contains procedures necessary to configure the GLI3 cards in an SC4812Tseries packet BTS for OTI backhaul. NOTE This procedure requires a site visit. There can be no contact between the BTS and the OMCR until the BTS is operating in OTI backhaul mode. A site visit is required to convert the GLI3 cards in a new BTS to OTI operation or ensure OTI operation prior to connection to the network.
Assumptions and prerequisites
Procedures in this section assume or require the following are done before performing BTS initialization with OTI: OTI edge device
S The OTI edge device (Figure L-1) has been installed and configured
by the customer
S The cables to connect the OTI edge device to the base station are
available at the site
S The edge device HAS NOT BEEN CONNECTED TO THE BTS

10/100BaseTX Fast Ethernet (FE) Local Area Network (LAN) NOTE It is essential that the edge device is NOT connected to the BTS 10/100BaseTX Ethernet LAN before it is required in this initialization procedure. Under certain conditions, removal of a BTStoedge device connection after powerup can result in inability to establish communication between the BTS and the OMCR.
BTS
S The BTS was installed as a packet BTS with OTI in accordance with
the applicable BTS hardware installation manual (Required Documents and Related Publications section of Chapter 1)
S The BTS is equipped with redundant GLI3 cards S The BTS has had power applied S The edge device HAS NOT BEEN CONNECTED TO THE BTS
10/100BaseTX Fast Ethernet (FE) Local Area Network (LAN)
S Site documentation specifies:

The required number of Ethernet connections between the BTS and edge device
Configure GLI3 Cards for OTI
continued
The BTS ESM EXTERNAL connection points and corresponding edge device connection points for each OMCR Provisioning of the OTI BTS has started, and the following are done: BTS ID number is assigned (example: BTS201) OTI_BTSRTRGRP_IP_addr is assigned OTI_Network_Mask is identified BTS OTIClientID is provisioned MLS_OTI_CON is enabled
Equipment required
The following hardware items are required to perform OTI implementation: LMF computer
The LMF computer which has been prepared as required in Chapter 3. MMI Interface
S One of the following

Motorola cable part number CGDSMMICABLE219112 Fabricated DB9 receptacleto8contact MMI connector cable (see the MMI Cable Fabrication Section of Appendix K for fabrication instructions and Table 3-10 for connection) SLN2006A MMI Interface Kit (this kit is no longer available to order), consisting of the following: Motorola Model TRN9666A null modem board Motorola 3009786R01 MMI cable or equivalent
S (For use with SLN2006A only) Straightthrough RS232 cable,

DB9 to DB9, and DB9 to DB25 connector adapter (see Figure 3-9)
GLI3 OTI implementation
This subsection covers the actions needed to implement OTI transport for a packet BTS or following GLI3 FRU replacement in a nonredundant BTS. Procedures unique to this process are contained in this subsection. When procedures required for this process are contained in other parts of this publication or in other publications, the user will be specifically directed to them at the appropriate places in this subsection. Prerequisites The following must be accomplished before traveling to the BTS site for OTI implementation:
S GLI3 card(s) for the site have been verified as having OTIcapable
software installed
continued
S GLI3 card(s) are installed in the BTS S The file transfer protocol setting required for operating the BTS (either
FTP or Secure FTP (SFTP)) on the network has been verified with the OMCR provisioning and network operators policy hand for transportation to the BTS site (refer to Required Documents and Related Publications section of Chapter 1)
S Required publications to support OTI implementation activities are on
OTI implementation preparation Perform the following to prepare the site for OTI implementation. Preparation before traveling to the BTS site The following must be performed before traveling to the BTS site. Table 5-16: Preparation for BTS OTI Implementation Step 1 2 3 Action Locate the OTI configuration settings worksheet and Network Interface Card (NIC) configuration worksheet at the end of this chapter. Make a copy of the worksheets for each BTS to be initialized. Contact the network administrator to obtain the values for the following Test Setting Items in Table 5-23 for each BTS to be initialized:
S OTI configuration settings:

BTS ID OTIClientID
S OTI IP address settings:

OTI_BTSRTRGRP_IP_addr OTI_Network_Mask MLS_OTI_CON_HSRP_Logical_Addr 4 5 Enter the OTI configuration settings into the Value column for the applicable settings in Table 5-23 of the OTI configuration settings worksheet. Use the IP information obtained to fill in the applicable IP addressing information blanks in the Internet Protocol (TCP/IP) Properties dialog box General tab portion of the Network Interface Card (NIC) configuration worksheet. Inventory the items to be transported to the BTS sites, and be sure they include the completed worksheets and the items identified in the Equipment required and GLI3 OTI implementation Prerequisites subsections, above.
Onsite preparations Perform the following after arriving at the BTS site.
continued
Table 5-17: Site Arrival and Initial Preparation Step 1 2 3 4 Action Upon arrival at the site, contact the OMCR and notify the operator that OTI backhaul configuration operations are starting. If it has not been done, open the BTS enclosure door and BTS cabinet doors to gain access to the BTS modules. Make sure frame FE cabling is connected to the cards as shown in Figure 5-1 or Figure 5-2 and the doublecrossover GLItoGLI cable 3088643C28 is connected. Verify frame FE cabling between the ESM and frame FE interface housing is connected according to Figure 5-1 or Figure 5-2.
! CAUTION
Be sure cables are dressed and/or secured so they ARE NOT PLACED IN COOLING FAN AIRFLOW. This will interfere with frame cooling and reduce equipment reliability. 5 With the BTS fully powered up, the GLI3 cards should have been seated in the correct slots. Perform one of the following:
5
6
S If cards are not seated, seat only one card, and allow it to complete initialization to OOS_SBY. S If both cards are seated, unseat one card from the CCCP cage backplane connector. Do not
disconnect the FE cables from the card BPR A and GLI connectors. If it was not previously done, follow the procedure in Table 5-5 for the powered GLI3 card to determine:
S The installed software version (any version of software release 2.20.x.x.x or later is required) S The backhaul mode S The operating mode (circuit or packet determined from backhaul mode; see Table 5-4)
7 If the GLI3 software requires upgrading for OTI capability, review the GLI3 Required Software Release, Operating Mode, and Loading Code section of this chapter to determine how to proceed with loading OTIcapable software into the card.
NOTE
Only one card in a BTS with redundant GLI3s is required to have OTIcapable software. This card must be the INS_ACT card (shows light green in the LMF; LED states: ACT LED steady green, STA LED slow flashing green ) in the BTS. The INS_ACT GLI will be the powered card in the BTS which is downloaded with code and data from the OMCR after OTI implementation. The INS_ACT GLI3 will crossload the correct software to the INS_SBY GLI3 after communication with the OMCR is established. 8 9 10 In any logical BTS expansion frames, unseat both GLI3 cards from their backplane connectors. Do not disconnect the FE cables from the card BPR A and GLI connectors. For a logical BTS, verify that the interframe 10Base2 LAN cables are correctly connected, and that the unused LAN connectors are properly terminated (refer to Figure 3-10). If it has not already been done, follow the procedure in Table 3-10 to establish an MMI communication session with the powered GLI3 card. table continued on next page
continued
Table 5-17: Site Arrival and Initial Preparation Step 11 12 Action Perform the OTI link confidence check procedure in Table L-2 of Appendix L. Configure the powered GLI3 card file transfer protocol settings to match what is required for network operation by performing the Configuring BTS File Transfer Protocol New BTS Installation procedure in this chapter. Proceed to Table 5-18 in the Convert GLI3 card to OTI operation subsection
13
Convert GLI3 cards to OTI operation
Perform the following to implement OTI operation beginning with the powered GLI3 card. Table 5-18: Convert GLI3 Card to OTI Operation Step 1 2 3 4 5 Action If it has not already been provided, contact the OMCR and request the operator provide the BTS OTIClientID (Table 5-23, second row). Enter the 4byte hexadecimal value provided into Table 5-23 of the worksheet for the BTS being initialized. Refer to the site documentation, and connect the Ethernet cables from the BTS edge device to the BTS ESM EXTERNAL connectors as specified. Verify that the BTS edge device connector link light is lighted for the Ethernet cable connected to the powered GLI3 card. Get the assigned BTS OTIClientID from Table 5-23 in the OTI configuration settings worksheet completed for the BTS. table continued on next page
SEP 2009
5-37
continued
Table 5-18: Convert GLI3 Card to OTI Operation Step 6 Action In the MMI communication session with the powered GLI3 card, enter the following at the GLI3> prompt: convert_oti <OTIClientID> Where <OTIClientID> is the 4byte hexadecimal OTIClientID from the Network Interface Card (NIC) Configuration Worksheet
NOTE
Include the dashes between the byte values when entering the OTIClientID. The system will display responses similar to the following:
GLI3> convert_oti 13f8be20 08.08.2007 13:50:17 MGLI19021
CC PRESENT BTSCDMA 20.00.30.42
WARNING!!! This MMI is changing the GLI configuration. The OTIClientID has been set to: 13f8be20 Removing file: /nvram00/config/bootcfg.txt Successfully removed file: /nvram00/config/bootcfg.txt Removing file: /nvram00/config/hlp_param.txt Successfully removed file: /nvram00/config/hlp_param.txt Removing file: /nvram00/config/ospf_cfg.txt Successfully removed file: /nvram00/config/ospf_cfg.txt Setting backhaul mode to OTI Successfully set backhaul mode to OTI To complete the conversion to OTI, this GLI must be reset! GLI3>
5-38
SEP 2009
continued
Reset the card using the MMI reset command and monitor the terminal session for conversion results.
NOTE
When the card completes rebooting after the reset, it will begin broadcasting DHCPDISCOVER messages through the OTI interface. If it does not receive a DHCPOFFER message from the RAN DHCP server within approximately 5 minutes, the card will reset itself, reboot, and begin the DHCP discovery process over again. DHCP timeout and cardinitiated reboot create terminal responses similar to the following:
Press any key to stop autoboot... 3 2 1 0 autobooting... Getting boot parameters via network interface motscc. CC went active, stopping motscc attempt and restarting over motfcc1... Getting boot parameters via network interface motfcc. DHCP attempt over motfcc1 has timed out. Decremented RAN DHCP retries.
A successful DHCP discovery/offer/request/acknowledgement and subsequent code download from the OMCR will generate a terminal response similar to the following:
Press any key to stop autoboot... 3 2 1 0 autobooting... Getting boot parameters via network interface motscc. CC went active, stopping motscc attempt and restarting over motfcc1... Getting boot parameters via network interface motfcc. DHCP Server:192.168.2.3 Boot file: /screl/active/boot/bts1902.boot Boot host: 10.78.0.37 Boot device Addr (motfcc1): 192.168.2.8 Subnet mask: 0xffffff00 Gateway: 192.168.2.1 Routers address: 192.168.2.1 Logical MGLI IP Addr: 10.78.128.144 Loading... FTPing to /ram00/loads/bts1902.boot... Bytes Transferred: 0 1024 103424 205824 308224 615424 717824 820224 922624 1025024 1127424 1229824 1537024 1639424 1741824 1844224 1946624 2049024 2151424 2458624 2561024 2663424 2765824 2868224 2970624 3073024 3380224 3482624 3585024 3687424 3789824 3892224 3994624 4301824 4404224 4506624 4609024 4711424 4813824 4916224 5223424 5325824 5428224 5530624 5633024 5735424 5837824 6145024 6247424 6349824 6452224 6554624 6657024 6759424 7066624 7169024 7271424 7373824 7476224 7578624 7681024 7988224 8090624 8193024 8295424 8308838 Transfer Complete.
410624 1332224 2253824 3175424 4097024 5018624 5940224 6861824 7783424
513024 1434624 2356224 3277824 4199424 5121024 6042624 6964224 7885824
SEP 2009
5-39
continued
Table 5-18: Convert GLI3 Card to OTI Operation Step 8 Action Following various process boot actions, and a SYSTEM INIT COMPLETE message, the card will verify its operating image with the List Information File (LIF) and download NEC and, if available, BTS RF calibration (CAL) files from the OMCR. The terminal will display a response similar to the following:
SYSTEM INIT COMPLETE CheckpointManager NOT Active informAllCheckpointableObjectListeners attribute id 75 sshd2: SSH2 Secure Shell MOTSSH IPTG_REL_1.2.04 on BTS>GLI3 0:0:26.560000 VERIFYING CURRENT GLI IMAGE WITH LIF 0:0:26.780000 COPYING GLI IMAGE Copy OK: 8308838 bytes copied 0:0:46.150000 get NECB from /screl/active/loadable/bts1902/NECB2.20.0.2.8BTS1902.xml 0:0:46.150000 put NECB here /nvram00/screl/2.20.0.2.8/NECB2.20.0.2.8BTS1902.xml 0:0:49.160000 get NECJ from /screl/active/loadable/bts1902/NECJ2.20.0.2.8BTS1902.xml 0:0:49.160000 put NECJ here /nvram00/screl/2.20.0.2.8/NECJ2.20.0.2.8BTS1902.xml 0:0:49.160000 put NECJ temporarily here /ram00/config/journal/ NECJ2.20.0.2.8BTS1902.xml Copy OK: 194 bytes copied Copy OK: 194 bytes copied Copy OK: 194 bytes copied 0:1:0.810000 get CAL file: /screl/active/loadable/bts1902/bts1902.cal 0:1:0.810000 put CAL file: /nvram00/config/temp_bts1902.cal
When the card completes its initialization, the terminal will display the GLI3> prompt. When the GLI3> prompt appears, seat the redundant GLI3 card and allow it to initialize. table continued on next page
5-40
SEP 2009
continued
Table 5-18: Convert GLI3 Card to OTI Operation Step 10 Action When the redundant GLI3 completes initialization and reaches INS_SBY (LED states: ACT LED not lighted, STA LED slow flashing green), move the MMI cable to the redundant card and verify its state by entering the following at the GLI3> prompt in the order listed: display status display bkhaul_mode The system will display responses similar to the following:
GLI3> display status CC NOT PRESENT BTSCDMA 20.00.30.42
08.08.2007 15:30:00 MGLI19022
status: Status for PACKET GLI B in the TOP / LEFT shelf of frame 0: status: This is a MASTER GLI shelf. status: Cage Control is NOT PRESENT status: Local CC Request ASSERTED status: Partner CC Request ASSERTED status: The current active LAN is B. status: SCAP Address: 81 076E 80 30 FF status: DNC number: 2 status: Logical number: 1 status: Cage type = SLIM (DCCP) status: EID Kit Number = SGLN6266BA status: EID Serial Number = 750X4X015Q GLI3> display bkhaul_mode 08.08.2007 15:31:39 MGLI19022 CC NOT PRESENT BTSCDMA 20.00.30.42
The current BTS Router Backhaul Mode is IWFOTI After the next reset, the BTS Router Backhaul Mode will be IWFOTI GLI3>
11 12 13 14
Verify that the BTS edge device connector link light is lighted for the Ethernet cable connected to the INS_SBY GLI3 card. For a logical BTS, repeat steps 9 through 11 for each GLI3 card in the expansion frame. At this point OTI implementation is complete for the BTS. If RF optimization and acceptance test of the BTS is required, it may be performed at this time. When activities are complete, proceed to Chapter 6 and follow the procedures to prepare to leave the site.
SEP 2009
5-41
continued
Figure 5-1: OTI Interconnection for SC4812Tseries Starter Frame

FRAME 1 ESM
EXTERNAL
ENET1 ENET3 ENET2 ENET4 ENET2 ENET4
BTS
ENET1 ENET3 ENET5
BTS# FRAME 1
GLI1 BPR A CABLE 3088643C23 OR 3088643C26
GLI #1
GLI1 GLI
CABLE 3088643C28
GLI #2
GLI2 GLI
NOTES: 1. BTS EDGE DEVICE CONNECTS TO ANY ESM EXTERNAL ENET 1 AND ENET 3 CONNECTORS WHICH ARE CONNECTED TO GLI3 CARDS. 2. BE SURE CABLES DO NOT BLOCK AIRFLOW FROM FRAME COOLING FANS.
SC4812OTI0012A
WHERE: BTS# = Number of the BTS in the BSS (1 to 1000)
5-42
SEP 2009
continued
Figure 5-2: OTI Interconnection for SC4812Tseries Starter Frame with One Expansion Frame
FRAME 1 ESM FRAME 101 ESM
EXTERNAL
ENET1 ENET3 ENET2 ENET4 ENET5 ENET2 ENET4
BTS
ENET1 ENET3 ENET5
EXTERNAL
ENET1 ENET3 ENET2 ENET4 ENET5 ENET2 ENET4
BTS
ENET1 ENET3 ENET5
BTS# FRAME 1
BTS# FRAME 101 (BTS EXP.)
GLI #1
GLI1 GLI
GLI #101
CABLE 3088643C28
GLI101 GLI
5
CABLE 3088643C28
GLI #2
GLI2 GLI
GLI #102
GLI102 GLI
WHERE: BTS# = Number of the BTS in the BSS (1 to 1000)
NOTES: 1. BTS EDGE DEVICE CONNECTS TO ANY ESM EXTERNAL ENET 1 AND ENET 3 CONNECTORS WHICH ARE CONNECTED TO GLI3 CARDS. 2. NO INTERFRAME FE CONNECTIONS ARE USED FOR OTI IN A LOGICAL BTS. 3. BE SURE CABLES DO NOT BLOCK AIRFLOW FROM FRAME COOLING FANS. SC4812OTI0012A
SEP 2009
5-43
Configuring BTS File Transfer Protocol Introduction Configuring BTS File Transfer Protocol Introduction
Motorola BTS models have used File Transfer Protocol (FTP) to transfer data to and from the OMCR since the introduction of packet data transport. Evolution of the traditional closed transport system to an Open Transport Interface (OTI) has emphasized the need to provide customers with increased security for data transfers. Motorola has incorporated Secure FTP (SFTP) into the CDMA Network Elements (NE) to address the problem of data security over open, unsecured networks. SFTP is supported on all Motorola NE and Operations Support Subsystems (OSS) beginning with CDMA software release 2.21.0. The LMF is equipped with a utility which is used to select either FTP or SFTP for information transfer between the BTS and the OMCR. This utility is only used at the cell site before communication is established with the OMCR to select the transfer protocol for a newly installed BTS (greenfield) or after replacement of a nonredundant GLI3 card.
LMF file transfer protocol setting utility
When the LMF is logged into a BTS, the file transfer protocol utility is available as the Secure FTP Settings selection under Util on the BTS tab menu bar . The Secure FTP Settings dialog box for the utility contains a number of selection items which are available depending on the protocol with which the BTS is operating. NOTE The protocol being used by the BTS is marked with a black dot in its radio button when the dialog box first opens.
Table 5-19: LMF File Transfer Protocol Selections Selection Location in Dialog Box Protocol group Protocol group Description Conditions when Selection Can Be Chosen BTS is operating with SFTP BTS is operating with FTP table continued next page
FTP
Protocol to be used for transferring files in unencrypted form to and from NE Protocol to be used for transferring files in encrypted form to and from NE
SFTP
5-44
SEP 2009
Configuring BTS File Transfer Protocol Introduction
continued
Table 5-19: LMF File Transfer Protocol Selections Selection Location in Dialog Box Action group Description Conditions when Selection Can Be Chosen 1. BTS is operating with FTP, and... 2. SFTP is selected (radio button is black) Condition 1: 1. BTS is operating with FTP, and... 2. SFTP is selected (radio button is black) ...or... Condition 2: BTS is operating with SFTP
Change protocol type with current settings
Change file transfer protocol from type currently used without making any changes to username, password, or key
Reset username and password
Action group
Resets current username and password to CDMA RAN default settings
NOTE
This selection can be used: 1. During conversion from FTP to SFTP 2. While BTS is operating with SFTP without changing the protocol
SEP 2009
5-45
Configuring BTS File Transfer Protocol New BTS Installation Configuring BTS File Transfer Protocol New BTS Installation
The procedures in this section specifically cover configuring the file transfer protocol of a new BTS. CAUTION This procedure must be performed before converting the GLI3 cards for operation with Integrated BTS Router (IBR), External BTS Routers (EBR), or Open Transport Interface (OTI) backhaul. Failure to perform this procedure first can result in the BTS failing to synchronize with the OMCR and delays in placing the site in service.
Prerequisites
The following conditions must be met before performing the procedures: S The required transfer protocol for the BTS has been specified by the network operator and provisioned at the OMCR S The BTS has power applied, and is operating without traffic or communication with the OMCR S The procedures in this section specifically cover configuring the file transfer protocol of a new BTS S LMF application must be operating and logged into the BTS
Determining the operating file transfer protocol
To configure the BTS or replacement GLI3 card file transfer protocol, it is necessary to first determine if the current protocol on which the BTS is operating is the one required. Determine the operating protocol by performing the following. Table 5-20: Determine Operating File Transfer Protocol Using the LMF Step 1 Action On the BTS tab menu bar select Util > Secure FTP Settings. Result: The Secure FTP Settings dialog box will open. 2 Examine the Protocol group to determine the protocol with the darkened radio button (FTP or SFTP).
NOTE
The protocol with the darkened radio button is the one with which the BTS is operating. 3 Do one of the following depending on the protocol setting provisioned for this BTS at the OMCR:
S If the button for the required protocol is not darkened, the protocol must be changed. Proceed to
Table 5-21 to change the protocol.
S If the button for the required protocol is darkened, continue to step 4.

Configuring BTS File Transfer Protocol New BTS Installation
continued
Table 5-20: Determine Operating File Transfer Protocol Using the LMF Step 4 Action If the required operating protocol is SFTP, click in the radio button for Reset username and password in the Action group. Result: The radio button for the selected choice will darken. 5 Click OK. Result: Selected settings are applied, and the dialog box closes. 6 Proceed with converting the GLI3 cards to IBR, EBR, or OTI operation as specified in those sections of this manual, as applicable.
Changing the operating file transfer protocol
Change the file transfer protocol by performing the following. Table 5-21: Change Operating File Transfer Protocol Using the LMF Step 1 Action If the Secure FTP Settings dialog box is not already open, open it by selecting Util > Secure FTP Settings from the BTS tab menu bar. Result: The Secure FTP Settings dialog box will open. 2 Do one of the following depending on the protocol setting required for operating this BTS on the network:
S If FTP is required, click the FTP radio button in the Protocol group, and skip to step 4. S If SFTP is required, click the SFTP radio button, and continue to step 3.
3 Click in the radio button for Reset username and password in the Action group. Result: The radio button for the selected choice will darken. 4 Click OK. Result: Selected settings are applied, and the dialog box closes. 5 Proceed with converting the GLI3 cards to IBR, EBR, or OTI operation as specified in those sections of this manual, as applicable.
SEP 2009
5-47
GLI3 Software Release and Backhaul Mode Worksheet GLI3 Software Release and Backhaul Mode Worksheet
NOTE Copy this page and use it as a form to record the information for a BTS. Enter the information into Table 5-22 by performing the following: 1. Enter the BTS number assigned to the base station where the GLI3 cards are installed (for example, BTS180) 2. Enter the software version and backhaul mode required for the BTS in the respective columns on the first line of Table 5-22. 3. Enter the software version of the code loaded in the GLI3 card installed in BTS card cage slot GLI 1 when determined by performing step 4 of Table 5-5. 4. Enter the backhaul mode of the GLI3 card installed in BTS card cage slot GLI 1 when determined by performing step 9 of Table 5-5.
Software Version and Backhaul Mode BTS# : _________________ Table 5-22: Software Release and Backhaul Mode Record Software Release 1. 2. Required for BTS GLI 1

Backhaul Mode
5-48
SEP 2009
OTI configuration settings worksheet OTI configuration settings worksheet

Obtain these OTI backhaul configuration settings from the network administrator
Information to be entered in the Value column of Table 5-23, below, must be obtained from the network administrator. This information is for use in configuring BTS OTI backhaul and OTI link confidence checks. The information should be obtained before leaving for the BTS site. Table 5-23: OTI Configuration Settings and Values Configuration Setting BTS ID (example: BTS201) for BTS or UBS to be tested OTIClientID (example: 1a2b3c4d) OTI_BTSRTRGRP_IP_addr (example: 10.20.22.4) OTI_Network_Mask (example: 255.255.255.0) MLS_OTI_CON_HSRP_Log ical_Addr (example: 10.20.22.1) OTIRawBkhlBW (UBS BTS models only) Value Description Unique number assigned to each BTS or UBS in network Unique 4byte hexadecimal value generated for each BTS by the OMCR 4octet (dotted decimal) IP address unique to the BTS 4octet (dotted decimal) IP subnet mask for the MLS OTI CON to the BTS 4octet (dotted decimal) IP address for default router (gateway) Raw backhaul bandwidth provisioned for a UBS in bits/second
SEP 2009
5-49
OTI configuration settings worksheet
continued
Notes
5-50
SEP 2009
Network Interface Card (NIC) configuration worksheet Network Interface Card (NIC) configuration worksheet
Record of original NIC configuration
Advanced tab of NIC hardware Properties dialog box Table 5-24: Advanced Tab Property List Box Connection Settings Original Operating System Windows XP Windows 2000 Property: Speed & Duplex Connection Type Internet Protocol (TCP/IP) Properties dialog box General tab ____ Obtain an IP address automatically ____ Use the following IP address: IP address: _______________________________ Subnet mask: _______________________________ Default Gateway: _______________________________
OTI verification NIC configuration
Original Value:
Advanced tab of NIC hardware Properties dialog box Table 5-25: Advanced Tab Property List Box Connection Settings for OTI Operating System Windows XP Windows 2000 Property: Speed & Duplex Connection Type OTI Test Value: 100 Mb Full 100 Mbps Full_Duplex
Internet Protocol (TCP/IP) Properties dialog box General tab ____ Obtain an IP address automatically X Use the following IP address: IP address: _______________________________ (use value for OTI_BTSRTRGRP_IP_addr from Table 5-23) Subnet mask: _______________________________ (use value for OTI_Network_Mask from Table 5-23) Default Gateway: _______________________________ (use value for MLS_OTI_CON_HSRP_Logical_Addr from Table 5-23)
SEP 2009
5-51
Network Interface Card (NIC) configuration worksheet
continued
Notes
5-52
SEP 2009
Chapter 6: Prepare to Leave the Site

Table of Contents
Updating Calibration Data Files Packet BTS . . . . . . . . . . . . . . . . . . . . . . . . . Automated Calibration File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . Process Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uploading Calibration File to the Master GLI3 in a Packet BTS . . . . . Prepare to Leave the Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External Test Equipment Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . IBR Span Configuration Verification . . . . . . . . . . . . . . . . . . . . . . . . . . Bringing Modules into Service with the LMF . . . . . . . . . . . . . . . . . . . LMF Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reconnect BTS Span and Modem Cables . . . . . . . . . . . . . . . . . . . . . . Reset All Devices and Initialize Site Remotely . . . . . . . . . . . . . . . . . . .
6-1 6-1 6-1 6-4 6-5 6-5 6-5 6-9 6-10 6-10 6-11
SEP 2009
Table of Contents
continued
Notes
SEP 2009
Updating Calibration Data Files Packet BTS Updating Calibration Data Files Packet BTS
Automated Calibration File Transfer
Beginning with Software Release 2.17.0, the user can load the calibration (CAL) file from the LMF directly to the MGLI. The MGLI will then: 1. Crossload the CAL file to the other GLI cards in the BTS 2. Crossload the BBX cards with their applicable TX calibration parameters and reset the BBX cards 3. FTP the new CAL file to the OMCR during synchronization This process eliminates the need for the user to transfer the CAL file to the OMCR, either through FTP from the LMF computer or by using the diskette transfer method.
Process Description
Figure 6-1 and Figure 6-2 provide a summary of the automated CAL file transfer process showing the general steps required, decision points, and messages provided to the user when applicable.
SEP 2009
6-1
Updating Calibration Data Files Packet BTS
continued
Figure 6-1: Automated Calibration File Transfer Process User and LMF Actions
START
Was CAL file updated or created with current TX BLO?
Perform procedure to update/establish TX BLO.
Y
User commands LMF to upload CAL file.
LMF opens window showing upload progress
LMF begins verification sequence Does CAL file exist in BTS folder on LMF computer? LMF displays an error message that CAL file does not exist and will not be uploaded
Y
Is LMF FTP server operating?
N
LMF displays a warning that LMF has problem connecting to GLI FTP server Does user choose to continue?
Can LMF Connect to MGLI?
Y N
LMF displays a warning that this operation will result in synchronization between GLI and OMCR
Does CAL file exist on MGLI?
Y
LMF displays warning that this operation will: 1. Overwrite the existing CAL file on the GLI, and... 2. Result in synchronization between GLI and OMCR
Does user choose to continue?
N
LMF opens window showing result of CAL file upload process
Y
LMF sends CAL file upload request to MGLI
LMF terminates CAL file upload process Go to Figure 6-2
END 6-2 1X SC4812T CLPA BTS Optimization/ATP SEP 2009
continued
Figure 6-2: Automated Calibration File Transfer Process GLI3 and LMF Actions
From Figure 6-1
MGLI receives CAL file upload request from LMF
Is GLI synchronizing with OMCR?
Does MGLI accept CAL file upload from LMF
Y
MGLI refuses upload from LMF
Y
Does CAL file upload to MGLI succeed?
Y
Do other GLIs in BTS accept MGLI distribution request for new CAL file?
Y
Does CAL file crossload to other GLIs succeed?
N
LMF records failure of CAL file to crossload to other GLIs and continues process
Y
Does OMCR accept MGLI request for synchronization to upload new CAL file?
Y
Does CAL file upload to OMCR succeed?
N
LMF records failure of CAL file to upload to OMCR and continues process
LMF opens window showing result of CAL file upload process
LMF terminates CAL file upload process NOTE: The MGLI will refuse OMCR synchronization requests while: 1. MGLI is in process of loading new CAL file from LMF or 2. Crossloading new LMF CAL file to other GLIs in the BTS.
END
SEP 2009
6-3

Uploading Calibration File to the Master GLI3 in a Packet BTS
continued
This procedure allows the user to upload a calibration (CAL) file from the LMF computer to the MGLI in a packet BTS. It also causes the MGLI to synchronize with the OMCR and transfer the uploaded CAL file to the OMCR during the synchronization process. Prerequisites The following are required before performing this procedure:
S The LMF computer is connected to the BTS 10Base2 LAN S The LMF application is logged into the BTS S The BTS CAL file has been created and saved in the applicable BTS
folder on the LMF computer
S The BTS CAL file contains the current BLO calibration data
Procedure Follow the procedure in Table 6-1 to upload a new CAL file from the LMF computer to the MGLI and update the BTS CAL file on the OMCR. Table 6-1: Uploading Calibration File to a Packet BTS
Step 1
Action In the LMF BTS tab menu bar, select BTS > Upload CAL file. Result: A window will open showing progress of the upload CAL file process.
2 3
If issues are encountered during the upload process, error or warning messages will be displayed. When the upload process ends, a window will open showing success or failure in the upload:
S If all the operations in the upload process are successful, the display will show complete success. S If upload of the CAL file to the MGLI fails, the display will show complete failure without details. S If CAL file crossload to other GLI cards fails, the display will show that operation failed but other
operations may be completed successfully. operations may be completed successfully.
S If CAL file upload to the OMCR fails, the display will show that operation failed but other NOTE
If the BTS is not enabled on the network or unable to communicate with the OMCR when the upload process is performed, the CAL file upload to the OMCR will fail. The new CAL file will be uploaded to the OMCR during the synchronization which will occur when communication is established between the MGLI and the OMCR. 4 Click Save Results to save the information displayed or Dismiss to close the window.
6-4
SEP 2009
Prepare to Leave the Site Prepare to Leave the Site

External Test Equipment Removal
Perform the procedure in Table 6-2 to disconnect the test equipment and prepare the BTS for active service. Table 6-2: External Test Equipment Removal Step 1 2 Action Disconnect all external test equipment from all BTS TX and RX antenna cable connectors. Visually inspect all TX and RX antennas cables and connect them to the BTS TX and RX antenna cable connectors.
CAUTION Verify that all sector antenna cables are connected to the correct ports on the frame. Crossed antenna cables will cause system degradation of call processing.
IBR Span Configuration Verification
6
The procedure in Table 6-3 is required only for a packet BTS configured to operate with Integrated BTS Router (IBR). Perform the procedure to verify the current span parameter settings. ALL GLI3 cards in all CCCP shelves that terminate a T1/E1 span should be verified. Table 6-3: IBR Span Parameter Configuration
Step 1 2 3
Action Connect the CDMA LMF computer to the MMI port on the applicable GLI as shown in Figure 6-3 or Figure 6-4. Start an MMI communication session with the applicable GLI by using the Windows desktop shortcut icon (see Table 3-3). Once the connection window opens, press the LMF computer Enter key until the GLI prompt is obtained. table continued on next page
SEP 2009
6-5
Prepare to Leave the Site
continued
Table 6-3: IBR Span Parameter Configuration Step 4 Action Verify the span parameter settings for frame format and equalization for the span to be used by entering the following at the GLI3> prompt:
config ni current
(equivalent of span view command)
The system will respond with a display similar to the following:

The frame format in flash Equalization: Span A Default (0131 Span B Default (0131 Span C Default (0131 Span D Default (0131 Span E Default (0131 Span F Default (0131 is set to use T1_2. feet feet feet feet feet feet for for for for for for T1/J1, T1/J1, T1/J1, T1/J1, T1/J1, T1/J1, 120 120 120 120 120 120 Ohm Ohm Ohm Ohm Ohm Ohm for for for for for for E1) E1) E1) E1) E1) E1)
Linkspeed: Default (56K for T1 D4 AMI, 64K otherwise) Currently, the link is running at the default rate The actual rate is 0 Loopback: OFF
NOTE 6
Defaults for span equalization are 0131 feet for T1/J1 spans and 120 Ohm for E1. There is no need to change from defaults unless the span configuration provisioned in the OMCR requires it. Linkspeed is set automatically by the GLI3 for the span type selected. 5 The span configurations loaded in the GLI must match those in the OMCR database for the BTS. If they do not, follow the Table 5-10 or Table 5-11 procedure, as applicable, to correct span settings for IBR. Repeat steps 1 through 5 for all remaining GLIs. If no other MMI actions are required with the GLI cards, terminate the GLI MMI session and HyperTerminal connection by selecting File from the connection window menu bar, and then Exit from the dropdown menu.
6 7
6-6
SEP 2009
continued
Figure 6-3: GLI3 Card MMI Connection Detail
To MMI Connector
MMI Connector
8PIN
LMF COMPUTER OR EQUIVALENT
6
RS232 CABLE COM1 OR COM2 DB9TODB25 ADAPTER
SEP 2009
6-7
continued
Figure 6-4: GLI3 Card MMI Connection Detail Fabricated MMI Cable
RESET Button
To MMI Connector
MMI Connector
8PIN

CABLE PART NUMBEr CGDSMMICABLE219112 OR COM1 OR COM2 FABRICATED MMI CABLE (SEE MMI CABLE FABRICATION SECTION)
6
DB9 CONNECTOR
6-8
SEP 2009

Bringing Modules into Service with the LMF
continued
NOTE Whenever possible, have the OMCR bring up the site and enable all devices at the BTS. If there is a reason code and/or data should or could not be loaded remotely from the OMCR, follow the steps outlined in Table 6-4 as required to bring BTS processor modules from OOS to INS state. Table 6-4: Bring Modules into Service Step 1 Action In the LMF GUI environment, select the device(s) to be enabled by clicking on each one.
NOTE S The GLI and CSM must be INS_ACT (bright green) before an MCC can be enabled. S Processors which must be enabled and the order of enabling are as follows:
1. GLI 2. CSMs 3. MCCs 2 Click on Device in the BTS menu bar, and select Enable from the pulldown list. Result: A status report window is displayed.
NOTE
If a BBX is selected, a transceiver parameters window is displayed to collect keying information. Do not enable the BBX. 3 4 Click Cancel to close the transceiver parameters window, if applicable. Click OK to close the status report window. Result: The color of devices which successfully change to INS will change to light green.
SEP 2009
6-9

LMF Removal
continued
NOTE DO NOT power down the LMF without performing the procedure below. Corrupted/lost data files may result, and in some cases, the LMF may lock up.
Follow the procedure in Table 6-5 to terminate the LMF session and remove the terminal. Table 6-5: LMF Termination and Removal Step 1 From the CDMA window select File > Exit. Action
NOTE
The File > Exit command will prompt to confirm the logout request. The File > Logout and Exit command will not prompt to confirm logout and will shut down the LMF. 2 3 4 5 From the Windows Task Bar click Start > Shutdown. Click Yes when the Shut Down Windows message appears. Disconnect the LMF terminal Ethernet connector from the BTS cabinet. Disconnect the LMF serial port, the RS-232toGPIB interface box, and the GPIB cables as required for equipment transport.
Reconnect BTS Span and Modem Cables
Before leaving the site, be sure any span TELCO and modem connectors that were removed from the BTS are reconnected. Refer to Table 6-6 and Figure 6-5 as required. Table 6-6: BTS Span and Modem Connections Step 1 2 3
6-10
Action If it was removed, connect the 50pin TELCO cables to the BTS span I/O card 50pin TELCO connectors. If used, connect the dialup modem RS232 serial cable to the Site I/O board RS232 9pin sub D connector. Verify the span status.
1X SC4812T CLPA BTS Optimization/ATP SEP 2009
continued
Figure 6-5: Indoor BTS Site and Span I/O Boards Span and Modem Connections
50PIN TELCO CONNECTORS REMOVED
SPAN A CONNECTOR (TELCO) INTERFACE TO SPAN LINES
RS232 9PIN SUB D CONNECTOR SERIAL PORT FOR EXTERNAL DIAL UP MODEM CONNECTION (IF USED)
SPAN B CONNECTOR (TELCO) INTERFACE TO SPAN LINES
TOP OF FRAME (SITE I/O AND SPAN I/O BOARDS)

FW00299
Reset All Devices and Initialize Site Remotely
Devices in the BTS should not be left with data and code loaded from the LMF. The configuration data and code loads used for normal operation could be different from those stored in the LMF files. Perform the procedure in Table 6-7 to reset all devices and initialize site remotely. NOTE Each module or device can be in any state prior to downloading. Each module or device will be in an OOS_RAM state after downloading has completed.
Table 6-7: Reset BTS Devices and Remote Site Initialization Step 1 2 Action Terminate the LMF session by following the procedures in Table 6-5. If applicable, be sure BTS spans are connected by following the procedure in Table 6-6. table continued on next page
SEP 2009
6-11
continued
Table 6-7: Reset BTS Devices and Remote Site Initialization Step 3 Action From the BTS site, contact the OMCR and request the operator to PREACTIVATE the BTS to the required software version for the BSS. There are two types of PREACTIVATE load processes: Rolling Upgrade: This load process is only available when the BTS cards are populated for full redundancy as applicable. Quick Reboot: This process is used when there is not full redundancy for the BTS cards. The GLI3 will disable and reboot to the new load. This will cause all the other cards to go out of service. Once it is rebooted, the GLI3 determines which cards require a new load and then downloads the cards in the order which they establish communication with the GLI3 following their reboot. The GLI3 can reload up to 16 devices simultaneously.
NOTE
Upon its first initialization with R18.0 or later RAM code, a packet GLI3 card will reallocate flash memory space for a duplicate copy of the bootROM code. It will then write a redundant copy of the code image to the new memory area. Visual indication of this process is provided by the STA LED flashing orange at 0.5 second intervals. This onetime process can cause the card to require up to 17 minutes to complete initialization to an INS state. Once the redundant image is created on the card, the extended 17minute upgrade process will not be repeated, even if the card is later downgraded to preR18.0 software. Wait at least 17 minutes for the card to complete this operation and/or the STA indicator to change to slow flashing green before attempting to proceed with the next step. 4 Account for all tools used and parts removed from the frame during the operations, being sure none were left inside the frame. Visually inspect the frame for any foreign objects left inside, and remove any discovered. Visually inspect all cable connections, ensuring they are connected as required for normal BTS operation. Be sure all internal frame cables are routed and secured to prevent damage to them when the frame doors are closed. Close and secure the cabinet doors. Verify no alarm conditions are being reported to the OMCR with the frame doors closed. After all activities at the site have been completed, contact the OMCR and confirm that the BTS is under OMCR control.
5 6 7 8 9 10
6-12
SEP 2009
Chapter 7: Basic Troubleshooting

Table of Contents
Basic Troubleshooting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cannot Log into Cell-Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unresponsive LMF operation with LMF R17 or earlier software . . . . . Cannot Communicate to Power Meter . . . . . . . . . . . . . . . . . . . . . . . . . Cannot Communicate to Communications Analyzer . . . . . . . . . . . . . . Troubleshooting: Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Can not perform any operation when using the Agilent E7595A/B . . . Cannot Download CODE to Any Device (card) . . . . . . . . . . . . . . . . . . Cannot Download DATA to Any Device (Card) . . . . . . . . . . . . . . . . . . Cannot ENABLE Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Miscellaneous Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Can not perform any operation when using the Agilent E7595A/B . . . Bay Level Offset Calibration Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . Cannot Load BLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibration Audit Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: Transmit ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Can not perform any test when using the Agilent E7595A/B . . . . . . . . BTS passed Reduced ATP tests but has forward link problem during normal operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cannot Perform TX Mask Measurement . . . . . . . . . . . . . . . . . . . . . . . . Cannot Perform Rho or Pilot Time Offset Measurement . . . . . . . . . . . Cannot Perform Code Domain Power and Noise Floor Measurement . Primary BBX Fails CD Power/Noise Floor Test After Redundant BBX TX Tests, Software Release 2.18.0.x . . . . . . . . . . . . . . . . . . . . . . . . . . . CD Power/Noise FloorTest Failures with Agilent E7495A/B Test Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: Receive ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Can not perform any test when using the Agilent E7595A/B . . . . . . . . MultiFER Test Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: CSM Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Problem Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No GPS Reference Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSM Reference Source Configuration Error . . . . . . . . . . . . . . . . . . . . . Takes Too Long for CSM to Come INS . . . . . . . . . . . . . . . . . . . . . . . .
7-1 7-1 7-2 7-2 7-2 7-3 7-4 7-5 7-5 7-5 7-6 7-6 7-6 7-8 7-8 7-8 7-8 7-9 7-10 7-10 7-10 7-11 7-11 7-12 7-12 7-12 7-14 7-14 7-14 7-15 7-15 7-15 7-16 7-16
Table of Contents
continued
Troubleshooting: CCCP Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connector Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCCP Backplane Troubleshooting Procedure . . . . . . . . . . . . . . . . . . . Digital Control Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DC Power Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX and RX Signal Routing Problems . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: Span Control Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Span Problems (No Control Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set BTS Site Span Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting: GLI3 card continually reboots after converting to satellite backhaul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing the correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Module Front Panel LED Indicators and Connectors . . . . . . . . . . . . . . . . . . . . . Module Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LED Status Combinations for All Modules (except GLI, CSM, BBX, MCC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DC/DC Converter LED Status Combinations . . . . . . . . . . . . . . . . . . . . CSM Indicator and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GLI LED Status Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GLI Pushbuttons and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBX LED Status Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PA Shelf LED Status Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . MCC LED Status Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-17 7-17 7-17 7-19 7-19 7-22 7-23 7-24 7-24 7-27 7-33 7-33 7-33 7-40 7-40 7-40 7-40 7-41 7-42 7-43 7-45 7-45 7-45
SEP 2009
Basic Troubleshooting Overview Basic Troubleshooting Overview

Overview
The information in this section addresses some of the scenarios likely to be encountered by Cellular Field Engineering (CFE) team members. This troubleshooting guide was created as an interim reference document for use in the field. It provides basic what to do if basic troubleshooting suggestions when the BTS equipment does not perform per the procedure documented in the manual. Comments are consolidated from inputs provided by CFEs in the field and information gained form experience in Motorola labs and classrooms.
SEP 2009
7-1
Troubleshooting: Installation Troubleshooting: Installation

Cannot Log into Cell-Site
Follow the procedure in Table 7-1 to troubleshoot a login failure. Table 7-1: Login Failure Troubleshooting Procedures n Step 1 Action If MGLI LED is solid RED, it implies a hardware failure. Reset MGLI by re-seating it. If this persists, install a known good MGLI card in MGLI slot and retry. A Red LED may also indicate no Ethernet termination at top of frame. Determine if the OMCR still has control of the BTS. Try pinging the MGLI (see Table 3-11). Verify the LMF is connected to the Primary LMF port (LAN A) in the front of the BTS (see Table 3-4). Verify the LMF was configured properly (see Preparing the LMF section of Chapter 3). Verify the BTS-LMF cable is RG-58 [flexible black cable of less than 76 cm (2.5 feet) length]. Verify the Ethernet ports are terminated properly (see Figure 3-10). Verify a T-adapter is not used on the LMF side port if connected to the BTS front LMF primary port. Try connecting to the I/O panel (top of frame). Use BNC T-adapters at the LMF port for this connection. Re-boot the LMF and retry. Re-seat the MGLI and retry. Verify IP addresses are configured properly.
2 3 4 5 6 7 8 9 10 11 12
7
Unresponsive LMF operation with LMF R17 or earlier software
When using R17 and earlier LMF versions needing Java Runtime Environment (JRE) 1.4.1, a bug in this JRE version can cause the LMF to become unresponsive when operating with some video cards. If this problem occurs, turn off video card acceleration by doing the following. Table 7-2: Turn Off Video Card Acceleration n Step 1 2 Select Properties from the popup menu. table continued on next page
Action Rightclick on the Windows operating system desktop.
Troubleshooting: Installation
continued
Table 7-2: Turn Off Video Card Acceleration n Step 3 4 5 6 7 8 9 Action Click the Settings tab in the Display Properties dialog box if it is not in the front. Click the Advanced button on the Settings tab. In the new dialog box, click on the Troubleshooting* tab to bring it to the front. Set Hardware acceleration to None. Click the OK button on the dialog box. Click the OK button on the Display Properties dialog. Restart the computer if directed to do so.
* The tab on which the hardware acceleration control is located may have any of several names. On some comupters it is named Performance. In all cases, the tab is found by pressing the Advanced button on the Settings tab in the Display Properties dialog box.
Cannot Communicate to Power Meter
Follow the procedure in Table 7-3 to troubleshoot a power meter communication failure. Table 7-3: Troubleshooting a Power Meter Communication Failure n Step 1 2 3 Action Verify the Power Meter is connected to the LMF with a GPIB adapter. Verify the cable setup as specified in Chapter 3. Verify the GPIB address of the power meter is set to the same value displayed in the applicable GPIB address box of the LMF Options window Test Equipment tab. Refer to Table 3-27 or Table 3-28 and the GPIB Addresses section of Appendix F for details. Verify the GPIB adapter DIP switch settings are correct. Refer to the Test Equipment setup section for details. Verify the GPIB adapter is not locked up. Under normal conditions, only two green LEDs must be ON (Power and Ready). If any other LED is continuously ON, then power-cycle the GPIB Box and retry. Verify the LMF computer COM1 port is not used by another application; for example, if a HyperTerminal window is open for MMI, close it. Reset all test equipment by clicking Util in the BTS menu bar and selecting Test Equipment>Reset from the pulldown lists.
4 5
6 7
SEP 2009
7-3
Troubleshooting: Installation
Cannot Communicate to Communications Analyzer
continued
Follow the procedure in Table 7-4 to troubleshoot a communications analyzer communication failure. Table 7-4: Troubleshooting a Communications Analyzer Communication Failure n Step 1 2 3 4 Action If using the Agilent E7495A/B or other network connection (IPbased connection) analyzer, TURN OFF any firewall or intrusion protection software installed on the LMF computer platform. Verify the analyzer is connected to the LMF with GPIB adapter. Verify the cable setup. Verify the signal generator GPIB address is set to the same value displayed in the applicable GPIB address box of the LMF Options window Test Equipment tab. Refer to Table 3-27 or Table 3-28 and the GPIB Address section of Appendix F for details. Verify the GPIB adapter DIP switch settings are correct. Refer to the CDMA 2000 Test Equipment Preparation section of Appendix F for details. Verify the GPIB adapter is not locked up. Under normal conditions, only two green LEDs must be ON (Power and Ready). If any other LED is continuously ON, then cycle the GPIB box power and retry. Verify the LMF computer COM1 port is not used by another application; for example, if a HyperTerminal window is open for MMI, close it. Reset all test equipment by clicking Util in the BTS menu bar and selecting Test Equipment>Reset from the pulldown lists.
5 6
7 8
7-4
SEP 2009
Troubleshooting: Download Troubleshooting: Download

Can not perform any operation when using the Agilent E7595A/B
Perform the procedure in Table 7-11 of the Troubleshooting: Transmit ATP section when attempting to perform any operation using the Agilent E7495A or B communication test set and the following message is received: Unable to receive desired data packet, too many errors
Cannot Download CODE to Any Device (card)
Follow the procedure in Table 7-5 to troubleshoot a code download failure. Table 7-5: Troubleshooting Code Download Failure n Step 1 2 3 Action Be sure the OMCR does not have control of the BTS. Verify the LMF can communicate with the BTS device using the Status function. Communication to the MGLI2 must first be established before trying to talk to any other BTS device. The MGLI2 must be INS_ACT state (green). Verify the card is physically present in the cage and powered-up. If the card LED is solid RED, it implies hardware failure. Reset the card by re-seating it. If the LED remains solid red, replace with a card from another slot & retry.
4 5
NOTE
The card can only be replaced by a card of the same type. 6 7 8 9 10 Re-seat the card and try again. If BBX reports a failure message and is OOS_RAM, the code load was OK. If the download portion completes and the reset portion fails, reset the device by selecting the device and Reset. If a BBX or an MCC remains OOS_ROM (blue) after code download, use the LMF Device > Status function to verify that the code load was accepted. If the code load was accepted, use LMF Device > Download > Flash to load RAM code into flash memory.
SEP 2009
7-5
Troubleshooting: Download
Cannot Download DATA to Any Device (Card)
continued
Perform the procedure in Table 7-6 to troubleshoot a data download failure. Table 7-6: Troubleshooting Data Download Failure n Step 1 Action Re-seat the card and repeat code and data load procedure.
Cannot ENABLE Device
Before a device can be enabled (placed in-service), it must be in the OOS_RAM state (yellow) with data downloaded to the device. The color of the device changes to green once it is enabled. The three states that devices can be changed to are as follows:
S Enabled (green, INS) S Disabled (yellow, OOS_RAM) S Reset (blue, OOS_ROM)

Follow the procedure in Table 7-7 to troubleshoot a device enable failure. Table 7-7: Troubleshooting Device Enable (INS) Failure n Step 1 Action Re-seat the card and repeat the code and data load procedure. If the CSM cannot be enabled, verify the CDF file has correct latitude and longitude data for cell site location and GPS sync. Ensure the primary CSM is in INS_ACT state.
2 3
NOTE
MCCs will not go INS without the CSM being INS. 4 5 6 Verify the 19.6608 MHz CSM clock; MCCs will not go INS otherwise. The BBX should not be enabled for ATP tests. If MCCs give invalid or no system time, verify the CSM is operable.
Miscellaneous Errors
Perform the procedure in Table 7-8 to troubleshoot miscellaneous failures.

Troubleshooting: Download
continued
Table 7-8: Miscellaneous Failures n Step 1 2 Action If PAs continue to give alarms, even after cycling power at the circuit breakers, then connect an MMI cable to the PA and set up a Hyperterminal connection (see Table 3-3). Enter ALARMS in the Hyperterminal window. The resulting LMF display may provide an indication of the problem. (Call Field Support for further assistance.)
SEP 2009
7-7
Troubleshooting: Calibration Troubleshooting: Calibration

Can not perform any operation when using the Agilent E7595A/B
Bay Level Offset Calibration Failure
Perform the procedure in Table 7-9 to troubleshoot a BLO calibration failure. Table 7-9: Troubleshooting BLO Calibration Failure n Step 1 2 3 4 Action Verify the Power Meter is configured correctly (see the test equipment setup section in Chapter 3) and connection is made to the proper TX port. Verify the parameters in the bts#.cdf file are set correctly for 800MHz: Bandclass=0; Freq_Band=8; SSType=8 Verify that no PA is in alarm state (flashing red LED). Reset the PA by pulling the circuit breaker and, after 5 seconds, pushing back in. Re-calibrate the Power Meter and verify it is calibrated correctly with cal factors from the sensor head. Verify the GPIB adapter is not locked up. Under normal conditions, only two green LEDs must be ON (Power and Ready). If any other LED is continuously ON, power-cycle (turn power off and on) the GPIB Box and retry. Verify the sensor head is functioning properly by checking it with the 1 mW (0 dBm) Power Ref signal. If communication between the LMF and Power Meter is operatonal, the Meter display will show RES.
6 7
Cannot Load BLO
For Load BLO failures see Table 7-8.
7-8
SEP 2009
Troubleshooting: Calibration
Calibration Audit Failure
continued
Follow the procedure in Table 7-10 to troubleshoot a calibration audit failure. Table 7-10: Troubleshooting Calibration Audit Failure n Step 1 2 3 4 5 Action Verify the Power Meter is configured correctly (refer to the test equipment setup section of Chapter 3). Re-calibrate the Power Meter and verify it is calibrated correctly with cal factors from the sensor head. Verify that no PA is in alarm state (rapidly flashing red LED). Reset the PA by pulling the circuit breaker and, after 5 seconds, pushing back in. Verify that no sensor head is functioning properly by checking it with the 1 mW (0 dBm) Power Ref signal. After calibration, the BLO data must be re-loaded to the BBXs before auditing. Click on the BBX(s) and select Device>Download BLO. Re-try the audit. Verify the GPIB adapter is not locked up. Under normal conditions, only two green LEDs must be ON (Power and Ready). If any other LED is continuously ON, power-cycle (turn power off and on) the GPIB Box and retry.
SEP 2009
7-9
Troubleshooting: Transmit ATP Troubleshooting: Transmit ATP

Can not perform any test when using the Agilent E7595A/B
Perform the following procedure when attempting to perform any test using the Agilent E7495A or B communication test set and the following message is received: Unable to receive desired data packet, too many errors Table 7-11: Correcting E7495A/B Test Set Communication Failure n Step 1 Action Determine the manufacturer of the Network Interface Card (NIC) installed in the LMF computer by accessing the Windows operating system Device Manager function.
! CAUTION
A user must have Adminisrtrator priveliges on the computer to make changes using Device Manager. If unfamiliar with this function, get help from a person experienced in configuring the Windows operating system. Incorrectly changing settings with Device Manager can cause the computer to become unuseable. 2 3 4 5 6 Download and install the latest driver(s) for the NIC from the manufacturers web site. If the problem continues, locate the latest drivers for all NICs installed on the LMF computer. Download and store the drivers in a new folder on the LMF computer. Uninstall all of the NICs using the Windows operating system Device Manager. Reinstall all of the NICs using the new drivers downloaded in step 4, above.
7
BTS passed Reduced ATP tests but has forward link problem during normal operation
Follow the procedure in Table 7-12 to troubleshoot a Forward Link problem during normal operation. Table 7-12: Troubleshooting Forward Link Failure (BTS Passed Reduced ATP) n Step 1 Action Perform these additional TX tests to troubleshoot a forward link problem: TX mask TX rho TX code domain
7-10
SEP 2009
Troubleshooting: Transmit ATP

Cannot Perform TX Mask Measurement
continued
Follow the procedure in Table 7-13 to troubleshoot a TX mask measurement failure. Table 7-13: Troubleshooting TX Mask Measurement Failure n Step 1 2 3 Verify that TX audit passes for the BBX(s). If performing manual measurement, verify analyzer setup. Verify that no PA in the sector is in alarm state (flashing red LED). Re-set the PA by pulling the circuit breaker and, after 5 seconds, pushing it back in. Action
Cannot Perform Rho or Pilot Time Offset Measurement
Follow the procedure in Table 7-14 to troubleshoot a rho or pilot time offset measurement failure. Table 7-14: Troubleshooting Rho and Pilot Time Offset Measurement Failure n Step 1 2 3 4 5 6 Action Verify presence of RF signal by switching to spectrum analyzer screen. Verify PN offsets displayed on the analyzer is the same as the PN offset in the CDF file. Reload BBX data and repeat the test. If performing manual measurement, verify analyzer setup. Verify that no PA in the sector is in alarm state (flashing red LED). Reset the PA by pulling the circuit breaker and, after 5 seconds, pushing back in. If Rho value is unstable and varies considerably (e.g. .95,.92,.93), this may indicate that the GPS is still phasing (i.e., trying to reach and maintain 0 freq. error). Go to the freq. bar in the upper right corner of the Rho meter and select Hz. Press <Shiftavg> and enter 10, to obtain an average Rho value. This is an indication the GPS has not stabilized before going INS and may need to be re-initialized.
SEP 2009
7-11

Cannot Perform Code Domain Power and Noise Floor Measurement
continued
Perform the procedure in Table 7-15 to troubleshoot a code domain and noise floor measurement failure. Table 7-15: Troubleshooting Code Domain Power and Noise Floor Measurement Failure n Step 1 2 3 Action Verify presence of RF signal by switching to spectrum analyzer screen. Verify PN offset displayed on analyzer is same as PN offset being used in the CDF file. Disable and re-enable MCC (one or more MCCs based on extent of failure).
Primary BBX Fails CD Power/Noise Floor Test After Redundant BBX TX Tests, Software Release 2.18.0.x
For software release 2.18.0.x, the CD power/noise floor test on a primary BBX can fail if the test is performed after any TX testing of the redundant BBX (BBXR) which used the Standard test pattern. Perform the following to retest primary BBXs which failed. Table 7-16: Troubleshooting Carrier Measurement Failure Step 1 2 Action Reload MCCs used in BBXR testing by performing the procedure in Table 4-2. Repeat CD/noise floor test for primary BBX(s) which failed.
CD Power/Noise FloorTest Failures with Agilent E7495A/B Test Set
Using an Agilent E7495 test set equipped with version A.06.00 firmware or earlier, this test can fail when a number of successive channels are keyed with the same spread factor and similar power (usually less than 1dB difference). An E7495 test set with the above firmware versions may erroneously detect the multiple channels as a single channel with a higher spread factor and power. E7495A/B Test Failure Workaround CD power/noise foor tests which fail under these conditions should be performed again following the procedure in Table 7-17.
continued
Table 7-17: CD Power/Noise Floor Test Failure Workaround for Agilent E7495A/B Step 1 Action Change the Measurement Time setting on the E7495A/B test set as follows: 1. Press the ESC/Lcl button on the E7495 front panel. 2. Press the Mode button on the E7495 front panel. 3. Press the TX Analyzer menu softkey selection (next to the test set display screen). 4. Press the CDMA Analyzer menu softkey selection which appears in the TX Analyzer menu. 5. Press the Setup menu softkey selection which appears in the CDMA Analyzer menu. 6. Press the Measurement Time softkey selection appearing in the Setup menu, repeating until Slow appears.
NOTE
Changing the Measurement Time setting on the E7495 will reduce but not completely eliminate the chance of the CD power/noise floor test failing. 2 3 From the LMF Login tab, open the LMF Options window by selecting Tools > Options. Be sure the Agilent E7495: 1. Is selected in the Test Equipment tab under Non Gpib Test Equipment, and... 2. Test set IP address is correctly entered in the Non Gpib Test Equipment IP address window Press the Apply button to close the LMF Options window. Log into the BTS. Use the LMF to perform the CD power/noise floor test as described in the Test Equipment Setup and Automated ATP sections of this publication.
4 5 6
SEP 2009
7-13
Troubleshooting: Receive ATP Troubleshooting: Receive ATP

Can not perform any test when using the Agilent E7595A/B
MultiFER Test Failure
Perform the procedure in Table 7-18 to troubleshoot a MultiFER failure. Table 7-18: Troubleshooting Multi-FER Failure n Step 1 2 3 4 5 6 Action Verify the test equipment set up is correct for an FER test. Verify the test equipment is locked to 19.6608 and even second clocks. On the HP8921A test set, the yellow LED (REF UNLOCK) must be OFF. Verify the MCCs have been loaded with data and are INSACT. Disable and re-enable the MCC (one or more based on extent of failure). Disable, re-load code and data, and re-enable the MCC (one or more MCCs based on extent of failure). Verify the antenna connections to frame are correct based on the directions messages.
7-14
SEP 2009
Troubleshooting: CSM Checklist Troubleshooting: CSM Checklist

Problem Description
Many of the Clock Synchronization Manager (CSM) card failures may be resolved in the field before sending the cards to the factory for repair. This section describes known CSM problems identified in field returns, some of which are field-repairable. Check these problems before returning suspect CSM cards.
No GPS Reference Source
Correct Hardware Check the CSM cards for proper hardware configuration for the type of GPS in use and the cage slot where they are installed. RFGPS (Local GPS) CSM kit SGLN1145, which should be installed in card slot l, has an oncard GPS receiver; while kit SGLN4132, in card slot 2, does not have a GPS receiver. Remote GPS (RGPS) Kit SGLN4132ED or later, which should be installed in both card slot 1 and card slot 2, does not have a GPS receiver. Any incorrectly configured card must be returned to the repair center. Do not attempt to change hardware configuration in the field. GPS Subsystem Installation Perform the following: 1. Inspect the GPS antenna and cabling for damage, water leaks, or loose connections. 2. Verify that the GPS antenna and lightning arrestor have not been damaged by lightning strikes. 3. Verify that the GPS antenna has a clear view to the sky. The GPS antenna should ideally have a clear view in all directions for elevations above 20 degrees from the horizon. Suitable GPS operation can be realized with as much as a 50 percent blockage in visibility. Any decrease in visibility greater than 50 percent will likely result in increased numbers of GPS reference source failure alarms.
SEP 2009
7-15
Troubleshooting: CSM Checklist

CSM Reference Source Configuration Error
continued
This problem is caused by incorrect reference source configuration performed in the field by software download. CSM kits SGLN1145 and SGLN4132 must have proper reference sources configured (as shown below) to function correctly. CSM Kit No. SGLN1145 SGLN4132 Hardware Configuration With GPS Receiver Without GPS Receiver CSM Slot No. 1 2 Reference Source Configuration Primary = Local GPS Backup = HSO Primary = Remote GPS Backup = HSO CDF Value 0 2 or 18 1 2 or 18
Takes Too Long for CSM to Come INS
Investigate the following to identify the source of delays in CSM cards reaching the INS state: GPS acquisition delay This problem may be caused by a delay in GPS acquisition. Check the accuracy flag status and/or current position. Refer to the CSM System time GPS, LFR and HSO/MSO verification section in Chapter 3. At least one satellite should be visible and tracked for the surveyed mode and four satellites should be visible and tracked for the estimated mode. Also, verify correct base site position data used in surveyed mode. GPS satellite reception problems Delays in bringing CSM cards INS are usually due to GPS satellite reception problems. Verify that the GPS antenna is provided with a clear view to the sky. The GPS antenna should ideally have a clear view in all directions for elevations above 20 degrees to the horizon. Suitable GPS operation can be realized with as much as a 50% blockage in visibility. Any decrease in visibility beyond 50% will likely result in increased CSM initialization times. Antenna system path losses Verify that no more than a 10dB signal loss at a 1.575GHz frequency is present between the GPS antenna and RF modem frame GPS antenna input. The total GPS antenna system noise figure (including all preamplifiers, cabling and splitter losses) must be less than 4.0dB. Higher GPS antenna system noise figures will result in degraded GPS receiver performance. Antenna location coordinates Verify that the GPS antenna coordinate information contained in the BTS CDF or NEC file is accurate. The <BtsLatGps>, <BtsLongGps> and <BtsHeightGps> should be within +/200m in the estimated mode and +/30m in the surveyed mode. The surveyed mode should only be used when absolutely necessary.
Troubleshooting: CCCP Backplane Troubleshooting: CCCP Backplane

Introduction
The CCCP backplane is a multilayer board that interconnects all the CCCP modules. The complexity of this board lends itself to possible improper diagnoses when problems occur.
Connector Functionality
The following connector overview describes the major types of backplane connectors along with the functionality of each. This information allows the CFE to:
S Determine which connector(s) is associated with a specific problem

type.
S Isolate problems to a specific cable or connector.

Primary A and Redundant B Inter Shelf Bus Connectors The 40 pin Inter Shelf Bus (ISB) connectors provide an interface bus from the master GLI to all other GLIs in the modem frame. Their basic function is to provide clock synchronization from the master GLI to all other GLIs in the frame. The ISB also provides the following functions:
S Span line grooming when a single span is used for multiple cages. S MMI connection to/from the master GLI to cell site modem. S Interface between GLIs and the AMR (for reporting BTS alarms).
Span Line Connector The 50pin span line connector provides a primary and secondary (if used) span line interface to each GLI in the CCCP shelf. The span line is used for MM/EMX switch control of the Master GLI and also all the BBX traffic. Primary A and Redundant B Reference Distribution Module Input/Output The Reference Distribution Module (RDM) connectors route the 3 MHz reference signals from the CSMs to the GLIs and all BBXs in the backplane. The signals are used to phase lock loop all clock circuits on the GLIs and BBX boards to produce precise clock and signal frequencies. Power Input (Return A, B, and C connectors) For 48 V configuration Provides a 48 volt input for use by the power supply modules. For +27 V configuration Provides input for regulated +27 Volts.
Troubleshooting: CCCP Backplane
continued
Power Supply Interface Each CCCP power supply has a series of three different connectors to provide the needed inputs/outputs to the CCCP backplane. These include a VCC/Ground input connector, a Harting style multiple pin interface, and a +15 V/Analog Ground output connector. The CCCP Power Supplies convert +27 Volts to a regulated +15, +6.5, and +5.0 Volts to be used by the CCCP shelf cards. For 48V BTS only, the power supply modules convert 48 Volts to a regulated +27 Volts. GLI Connector This connector consists of a Harting 4SU digital connector and a 6conductor coaxial connector for RDM distribution. The connectors provide inputs/outputs for the GLIs in the CCCP backplane. GLI 10Base2 Ethernet A and B Connections These BNC connectors are located on the CCCP backplane and routed to the GLI board. This interface provides all the control and data communications between the master GLI and the other GLI, between gateways, and for the LMF on the LAN. BBX Connector Each BBX connector consists of a Harting 2SU/1SU digital connector and two 6conductor coaxial connectors. These connectors provide DC, digital, and RF inputs/outputs for the BBXs in the CCCP backplane. MCIO Connectors
S RX RF antenna path signal inputs are routed through RX TriFilters 7
(on the I/O plate), and via coaxial cables to the two MPC modules the six A (main) signals go to one MPC; the six B (diversity) to the other. The MPC outputs the lownoiseamplified signals via the CCCP backplane to the MCIO where the signals are split and sent to the appropriate BBX. backplane, then on to the MCC slots.
S A digital bus then routes the baseband signal through the BBX, to the S Digital TX antenna path signals originate at the MCCs. Each output
is routed from the MCC slot via the backplane appropriate BBX. the MCIO, through the MCIO, and via multi-conductor coaxial cabling to the PAs in the PA shelf.
S TX RF path signal originates from the BBX, through the backplane to
7-18
SEP 2009

CCCP Backplane Troubleshooting Procedure
continued
Table 7-19 through Table 7-28 provide procedures for troubleshooting problems that appear to be related to a defective CCCP backplane. The tables are broken down into possible problems and steps that should be taken in an attempt to find the root cause. NOTE
IMPORTANT: Table 7-19 through Table 7-28 must be
completed before replacing ANY CCCP backplane.
Digital Control Problems
No GLI Control via LMF (all GLIs) Follow the procedure in Table 7-19 to troubleshoot a GLI control via LMF failure. Table 7-19: No GLI Control via LMF (all GLIs) n Step 1 2 3 4 Action Check the 10Base2 ethernet connector for proper connection, damage, shorts, or opens. Verify the CCCP backplane Shelf ID DIP switch is set correctly. Visually check the master GLI connector (both board and backplane) for damage. Replace the master GLI with a known good GLI.
SEP 2009
7-19
continued
No GLI Control through Span Line Connection (All GLIs) Follow the procedures in Table 7-20 and Table 7-21 to troubleshoot GLI control failures. Table 7-20: No GLI Control through Span Line Connection (Both GLIs) Step 1 2 3 4 5 6 Action Verify the CCCP backplane Shelf ID DIP switch is set correctly. Verify that the BTS and GLIs are correctly configured in the OMCR/CBSC data base. Visually check the master GLI connector (both board and backplane) for damage. Replace the master GLI with a known good GLI. Check the span line inputs from the top of the frame to the master GLI for proper connection and damage. Check the span line configuration on the MGLI (see Table 6-3).
Table 7-21: MGLI Control Good No Control over Colocated GLI Step 1 2 3 4 Action Verify that the BTS and GLIs are correctly configured in the OMCR CBSC data base. Check the 10Base2 ethernet connector for proper connection, damage, shorts, or opens. Visually check all GLI connectors (both board and backplane) for damage. Replace the remaining GLI with a known good GLI.
No AMR Control (MGLI good) Perform the procedure in Table 7-22 to troubleshoot an AMR control failure when the MGLI control is good. Table 7-22: MGLI Control Good No Control over AMR Step 1 2 3 Action Visually check the master GLI connector (both board and backplane) for damage. Replace the master GLI with a known good GLI. Replace the AMR with a known good AMR.
No BBX Control in the Shelf (No Control over Colocated GLIs) Perform the procedure in Table 7-23 to troubleshoot a BBX control in the shelf failure.
continued
Table 7-23: No BBX Control in the Shelf No Control over Colocated GLIs Step 1 2 3 4 Action Visually check all GLI connectors (both board and backplane) for damage. Replace the remaining GLI with a known good GLI. Visually check BBX connectors (both board and backplane) for damage. Replace the BBX with a known good BBX.
No (or Missing) Span Line Traffic Perform the procedure in Table 7-24 to troubleshoot a span line traffic failure. Table 7-24: MGLI Control Good No (or Missing) Span Line Traffic Step 1 2 3 4 5 6 Action Visually check all GLI connectors (both board and backplane) for damage. Replace the remaining GLI with a known good GLI. Visually check all span line distribution (both connectors and cables) for damage. If the problem seems to be limited to one BBX, replace the MGLI with a known good MGLI. Perform the BTS Span Parameter Configuration ( see Table 6-3). Ensure that ISB cabling is correct.
No (or Missing) MCC Channel Elements Perform the procedure in Table 7-25 to troubleshoot a channel elements failure. Table 7-25: No MCC Channel Elements Step 1 2 3 4 Action Verify CEs on a colocated MCC (MCC24 TYPE=2). If the problem seems to be limited to one MCC, replace the MCC with a known good MCC. Check connectors (both board and backplane) for damage. If no CEs on any MCC: Verify clock reference to MCIO. Check the CDF for MCCTYPE=2 (MCC24E); MCCTYPE=0 (MCC8E) or MCCTYPE=3 (MCC1X)
SEP 2009
7-21

DC Power Problems
continued
Perform the procedure in Table 7-26 to troubleshoot a DC input voltage to power supply module failure. WARNING Potentially lethal voltage and current levels are routed to the BTS equipment. This test must be carried out with a second person present, acting in a safety role. Remove all rings, jewelry, and wrist watches prior to beginning this test.
No DC Input Voltage to Power Supply Module Table 7-26: No DC Input Voltage to Power Supply Module Step 1 2 Verify DC power is applied to the BTS frame. Verify there are no breakers tripped. If a breaker has tripped, remove all modules from the applicable shelf supplied by the breaker and attempt to reset it. If the breaker trips again, there is probably a cable or breaker problem within the frame. If the breaker does not trip, there is probably a defective module or subassembly within the shelf. 3 4 Verify that the CCCP shelf breaker on the BTS frame breaker panel is functional. Use a voltmeter to determine if the input voltage is being routed to the CCCP backplane by measuring the DC voltage level on the PWR_IN cable. If the voltage is not present, there is probably a cable or breaker problem within the frame. If the voltage is present at the connector, reconnect and measure the level at the VCC power feed clip on the distribution backplane. If the voltage is correct at the power clip, inspect the clip for damage. 48 V configuration only If everything appears to be correct, visually inspect the power supply module and verify LEDs are green. 48 V configuration only If LED is red, then replace the power suppy module with a known good module and verify LEDs are green. If steps 1 through 5 fail to indicate a problem, a CCCP backplane failure (possibly an open trace) has occurred. Action
* IMPORTANT
7
5 6 7
7-22
SEP 2009
continued
No DC Voltage (+5, +6.5, or +15 Volts) to a Specific GLI, BBX, or Switchboard Perform the procedure in Table 7-27 to troubleshoot a DC input voltage to GLI, BBX, or Switchboard failure. Table 7-27: No DC Input Voltage to any CCCP Shelf Module Step 1 2 3 Action Verify the steps in Table 7-26 have been performed. Inspect the defective board/module (both board and backplane) connector for damage. Replace suspect board/module with known good board/module.
TX and RX Signal Routing Problems
Perform the procedure in Table 7-28 to troubleshoot TX and RX signal routing problems. Table 7-28: TX and RX Signal Routing Problems Step 1 2 Action Inspect all Harting Cable connectors and backplane connectors for damage in all the affected board slots. Perform steps in the RF path troubleshooting flowchart in this manual.
SEP 2009
7-23
Troubleshooting: Span Control Link Troubleshooting: Span Control Link

Span Problems (No Control Link)
Perform the procedure in Table 7-29 to troubleshoot a control link failure. Table 7-29: Troubleshoot Control Link Failure n Step 1 2 3 4 Action Connect the CDMA LMF computer to the MMI port on the applicable GLI as shown in Figure 7-1. Start an MMI communication session with the applicable GLI by using the Windows desktop shortcut icon. Once the connection window opens, press the LMF computer Enter key until the GLI prompt is obtained. Verify the span parameter settings for frame format, equalization, and linkspeed for the span to be used by entering the following at the GLI3> prompt:
config ni current
(equivalent of span view command)
The system will respond with a display similar to the following:

The frame format in flash Equalization: Span A Default (0131 Span B Default (0131 Span C Default (0131 Span D Default (0131 Span E Default (0131 Span F Default (0131 is set to use T1_2. feet feet feet feet feet feet for for for for for for T1/J1, T1/J1, T1/J1, T1/J1, T1/J1, T1/J1, 120 120 120 120 120 120 Ohm Ohm Ohm Ohm Ohm Ohm for for for for for for E1) E1) E1) E1) E1) E1)
Linkspeed: Default (56K for T1 D4 AMI, 64K otherwise) Currently, the link is running at the default rate The actual rate is 0 Loopback: OFF
NOTE
Defaults for span equalization are 0131 feet for T1/J1 spans and 120 Ohm for E1. Default linkspeed is 56 kbps for T1 D4 AMI spans and 64 kbps for all other types. There is no need to change from defaults unless the span configuration provisioned in the OMCR requires it. 5 6 The span configurations loaded in the GLI must match those in the OMCR database for the BTS. If they do not, follow the procedure in Table 7-30. Repeat steps 1 through 5 for all remaining GLIs. table continued on next page
Troubleshooting: Span Control Link
continued
Table 7-29: Troubleshoot Control Link Failure n Step 7 Action If the span settings are correct, verify the edlc parameters using the show command. Any alarm conditions indicate that the span is not operating correctly.
S Try looping back the span line from the DSX panel back to the MM, and verify that the looped
signal is good.
S Listen for control tone on the appropriate timeslot from the Base Site and MM.
8 9 Terminate the GLI MMI session and HyperTerminal connection by selecting File from the connection window menu bar, and then Exit from the dropdown menu. If no TCHs in groomed MCCs (or in whole SCCP shelf) can process calls, verify that the ISB cabling is correct and that ISB A and ISB B cables are not swapped.
SEP 2009
7-25

Figure 7-1: GLI3 Card MMI Connection Detail
continued
BPR A BPR B AUX GLI ALARM RESET
100BASET TO BTS PACKET ROUTER OR EXPANSION CAGE 100BASET AUXILIARY MONITOR PORT DUAL 100BASET IN A SINGLE RJ45 TO REDUNDANT (MATE) GLI3 RESET SWITCH
SPAN
GLI3
TO MMI PORT
SPAN (LED) ALARM (LED) MMI PORT ACTIVE (LED) STATUS (LED)
MMI STA ACT
8PIN
7
CDMA LMF COMPUTER
RS232 CABLE COM1 OR COM2 NOTE: MMI connection can also be made using locally fabricated MMI cable. See Appendix K. DB9TODB25 ADAPTER
REF ti-CDMA-WP-00064-v01-ildoc-ftw
7-26
SEP 2009

Set BTS Site Span Configuration
continued
Perform the procedure in Table 7-30 to set the span parameter configuration. NOTE 1. Perform the following procedure ONLY if span configurations loaded in the GLI cards do not match those in the OMCR data base, AND ONLY when the exact configuration data is available. Loading incorrect span configuration data will render the site inoperable. 2. In R18.0 and later software releases, span rate (linkspeed) is no longer set using a config ni command. Linkspeed is determined and automatically set by the span type selected.
Table 7-30: Set BTS Span Parameter Configuration n Step 1 2 Action If not previously done, connect the CDMA LMF computer to the MMI port on the applicable GLI as shown in Figure 7-1. If there is no MMI communication session in progress with the applicable GLI, initiate one by using the Windows desktop shortcut icon. table continued on next page
SEP 2009
7-27
continued
Table 7-30: Set BTS Span Parameter Configuration n Step 3 At the GLI prompt, enter: config ni format <option> Action

COMMAND SYNTAX: config ni format option_gli3 Next available options: LIST option_gli3: Span Option E1_1 : E1_1 E1 HDB3 CRC4 no TS16 E1_2 : E1_2 E1 HDB3 no CRC4 no TS16 E1_3 : E1_3 E1 HDB3 CRC4 TS16 E1_4 : E1_4 E1 HDB3 no CRC4 TS16 T1_1 : T1_1 D4, AMI, No ZCS T1_2 : T1_2 ESF, B8ZS J1_1 : J1_1 ESF, B8ZS (Japan) J1_2 : J1_2 ESF, B8ZS T1_3 : T1_3 D4, AMI, ZCS >
NOTE
1. With this command, all active (inuse) spans will be set to the same format. 2. E1_1 and E1_2 are PCM31 formats which provide 31 time slots for bearer traffic. 3. E1_3 and E1_4 are PCM30 formats which provide 30 time slots for bearer traffic. TS16 in these formats is reserved and not used for payload transport. 4 To set or change the span type, enter the correct option from the list at the entry prompt (>), as shown in the following example:
> T1_2
NOTE
The entry is casesensitive and must be typed exactly as it appears in the list. If the entry is typed incorrectly, a response similar to the following will be displayed:
CP: Invalid command 01.05.1980 00:11:59 MGLI0041 INSACT BTSCDMA 19.00.201.68 GLI3>
7-28
SEP 2009
continued
Table 7-30: Set BTS Span Parameter Configuration n Step 5 Action An acknowledgement similar to the following will be displayed:
The value has been programmed. It will take effect after the next reset. GLI3>
NOTE
In R18.0 and later software releases, span linkspeed is no longer set using a config ni command. Linkspeed is determined and automatically set by the span type selected. 6 If the span equalization must be changed, enter the following MMI command:
config ni equal

COMMAND SYNTAX: config ni equal span_gli3 equal Next available options: LIST span_gli3 : Span a : Span A b : Span B c : Span C d : Span D e : Span E f : Span F >
SEP 2009
7-29
continued
Table 7-30: Set BTS Span Parameter Configuration n Step 7 Action At the entry prompt (>), enter the designator from the list for the span to be changed as shown in the following example:
> a
A response similar to the following will be displayed:

COMMAND SYNTAX: config ni equal a equal Next available options: LIST equal : Span Equalization default : Default (0131 feet for T1/J1, 120 ohm for E1) T1_1 : T1 Short Haul mode. 0131 feet T1_2 : T1 Short Haul mode. 132262 feet T1_3 : T1 Short Haul mode. 263393 feet T1_4 : T1 Short Haul mode. 394524 feet T1_5 : T1 Short Haul mode. 525655 feet E1_120 : E1 Short Haul mode. 120 OHM T1_0DB : T1 Short Haul mode. LBO = 0 dB T1_7_5DB : T1 Short Haul mode. LBO = 7.5 dB T1_15DB : T1 Short Haul mode. LBO = 15.0 dB >
! CAUTION
For fourdigit BTSs supported with Channel Service Units (CSU), do not select any of the following additional settings:
S T1_0DB T1 Long Haul mode. LBO = 0 dB S T1_7_5DB T1 Long Haul mode. LBO = 7.5 dB S 10T1_15DB T1 Long Haul mode. LBO = 15.0 dB
8 At the entry prompt (>), enter the code for the required equalization from the list as shown in the following example:
> T1_1

> T1_1 The value has been programmed. It will take effect after the next reset. GLI3>
Repeat steps 6 through 8 for each inuse span. table continued on next page
7-30
SEP 2009
continued
Table 7-30: Set BTS Span Parameter Configuration n Step 10 Action
NOTE
This step must be performed for GLI3 cards operating on a packet image to ensure the span parameter changes will replace the previous settings. For a GLI3 card in packet mode, enter the following:
rmfile /nvram00/config/hlp_param.txt
A response similar to the following will be displayed :

GLI3> rmfile /nvram00/config/hlp_param.txt 01.06.1980 00:12:57 MGLI0041 CC PRESENT BTSCDMA 19.00.201.68 GLI3>
11
NOTE S After executing the config ni format and/or config ni equal commands, the affected GLI
card MUST be reset and reloaded for changes to take effect.
S Although defaults are shown in the software, always consult sitespecific documentation for
span type, equalization, and linkspeed used at the site where the cards are to be installed. Reset the card using the MMI reset command. 12 Once the card has completed resetting, execute the following command to verify span settings are as required:
config ni current

The frame format in flash is set to use T1_2. Equalization: Span A T1 Short Haul mode. 0131 feet Span B T1 Short Haul mode. 0131 feet Span C Default (0131 feet for T1/J1, 120 Span D Default (0131 feet for T1/J1, 120 Span E Default (0131 feet for T1/J1, 120 Span F Default (0131 feet for T1/J1, 120 Linkspeed: 64K Currently, the link is running at 64K The actual rate is 0 Loopback: OFF
Ohm Ohm Ohm Ohm
for for for for
E1) E1) E1) E1)
SEP 2009
7-31
continued
Table 7-30: Set BTS Span Parameter Configuration n Step 13 14 Action If the span configuration is not correct, perform the applicable step from this table to change it and repeat steps 10 through 12 to verify required changes have been programmed. Return to step 6 of Table 7-29.
7-32
SEP 2009
Troubleshooting: GLI3 card continually reboots after converting to satellite backhaul Troubleshooting: GLI3 card continually reboots after converting to satellite backhaul
At times, a GLI3 card which should have been converted to satellite backhaul will continuously reboot and display MMI messages similar to the following:
Reset due Backhaul Reset due Backhaul DHCP attempt timed Reset due Backhaul timeout timeout out timeout
This condition can occur when the GLI3 card(s) backhaul type has not actually changed to satellite with associated longer timeout periods. In this situation, the BTS can appear INS_ACTIVE at the OMCR but will be generating communication alarms such as Packet Backhaul Down. The BTS and OMCR will be unable to communicate. Because of this, a site visit is needed to correct this condition. This procedure can also be used to preconfigure a GLI3 card for satellite backhaul before commissioning or converting a BTS.
Prerequisites
The following are required to perform the corrective procedure:
S Laptop computer with at least one serial port or laptop computer S One of the following:
Motorola cable part number CGDSMMICABLE219112 (see Figure 3-8 for connection)
meeting the LMF computer platform requirements specified in the BTS optimization/ATP manual
Fabricated DB9 receptacleto8 contact MMI connector cable (see the MMI Cable Fabrication Section of Appendix K for fabrication instructions and Figure 3-8 for connection) SLN2006A MMI Interface Kit (see Figure 3-9) (this kit is no longer available to order), consisting of the following: Motorola Model TRN9666A null modem board Motorola 3009786R01 MMI cable or equivalent
S (For use with SLN2006A only) Straightthrough RS232 cable,

DB9 to DB9, and DB9 to DB25 connector adapter (see Figure 3-9)
S A terminal emulation application such as HyperTerminal or PuTTY

Performing the correction
Perform the following to convert the GLI3 card to satellite backhaul and establish communication with the OMCR.
Troubleshooting: GLI3 card continually reboots after converting to satellite backhaul continued
Table 7-31: Setting GLI3 Backhaul Type to Satellite and Correct Timeout Intervals Step 1 2 Locate the INS_ACT GLI3 card. Action Upon arrival at the site, contact the OMC R and notify the operator that site operations are starting.
NOTE
The INS_ACT card LEDs will show the following indications:
S STA: Slow flashing green S ACT: green

3 4 Start an MMI communication session with the INS_ACT GLI3 card by following the instructions and illustrations in the Establishing an MMI Communication Session section of Chapter 3. In a BTS with redundant GLI3 cards, locate the INS_SBY card.
NOTE
The INS_SBY card LEDs will show the following indications:
S STA: Slow flashing green S ACT: OFF

5 Disable the INS_SBY GLI3 card by unseating it from the backplane. table continued on next page
7-34
SEP 2009
Table 7-31: Setting GLI3 Backhaul Type to Satellite and Correct Timeout Intervals Step 6 Action At the GLI3> prompt, reset the INS_ACT card by entering the following command:
reset
The system will display a response similar to the following partial example:
GLI3> reset
++ | GLI3 BootROM Version 22.00.70.37 | ++ | Redundant BootROM from:0xC0800000 | | TFFS location:0xC0980000 | | Checking FLASH formatting | | TFFS device created | | Checking TFFS device | /nvram00/ Volume is OK ++ | Reset Status Register : 0x00000002 | | Other Reset Data : 0x00800000 | | Reset Reason : Soft Reset Command | | Exception Type : NONE | | Cage Control Status : STANDBY (0x00) | | File Transfer Mode : FTP | ++ | Network Interface Initialization |
7
<<< remaining output omitted >>>
SEP 2009
7-35
Table 7-31: Setting GLI3 Backhaul Type to Satellite and Correct Timeout Intervals Step 7 Action The GLI3 boot process must be stopped within 3 seconds after the Press any key to stop autoboot... line appears (see bold output line in the following):
VxWorks System Boot Copyright 19841998 Wind River Systems, Inc.
CPU: EST Corp. est8260 MPC8260 PowerQUICC II SBC Version: 5.4.2 BSP version: 1.2/0 Creation date: Oct 22 2008, 10:58:02
Press any key to stop autoboot...
NOTE
If any key is not pressed within 3 seconds after the line appears, the card must be allowed to complete the boot process and then reset again to force it to reboot. 8 9 When the Press any key to stop autoboot... line appears, press the Enter key. The system will display a response similar to the following:
Press any key to stop autoboot... Copyright 19841998 3 2 VxWorks Boot]: Wind River Systems, Inc.
7
10
Change the backhaul type to satellite by entering the following at the [VxWorks Boot]: prompt:
bkhaul_type_set satellite
The system will display a response similar to the following:

[VxWorks Boot]: bkhaul_type_set satellite New backhaul type has been set successfully.
7-36
SEP 2009
Table 7-31: Setting GLI3 Backhaul Type to Satellite and Correct Timeout Intervals Step 11 Action Verify that the backhaul type has been changed to satellite by entering the following at the [VxWorks Boot]: prompt:
bkhaul_type_get

[VxWorks Boot]: bkhaul_type_get The current backhaul type is SATELLITE.
12
Verify the current satellite backhaul Link Control Protocol (LCP) values by entering the following at the [VxWorks Boot]: prompt:
sat_bkhaul_get

VxWorks Boot]: sat_bkhaul_get Satellite Backhaul LCP NegRetry Interval is 1000 ms. Satellite Backhaul LCP Keepalive Interval is 0 ms.
13
If the LCP parameter values are not set to 3000, set the satellite backhaul keepalive interval by entering the following at the [VxWorks Boot]: prompt:
sat_bkhaul_set keepalive_int 3

[VxWorks Boot]: sat_bkhaul_set keepalive_int 3 Set keepalive_int successfully.
NOTE
This sets the timeout interval to 3000 ms as required for satellite backhaul. 14 Set the satellite backhaul negotiation retry interval by entering the following at the [VxWorks Boot]: prompt:
sat_bkhaul_set neg_retry_int 3

[VxWorks Boot]: sat_bkhaul_set neg_retry_int 3 Set neg_retry_int successfully.
SEP 2009
7-37
Table 7-31: Setting GLI3 Backhaul Type to Satellite and Correct Timeout Intervals Step 15 Action Verify that the LCP parameter values have been set correctly by entering the following at the [VxWorks Boot]: prompt:
sat_bkhaul_get

VxWorks Boot]: sat_bkhaul_get Satellite Backhaul LCP NegRetry Interval is 3000 ms. Satellite Backhaul LCP Keepalive Interval is 3000 ms.
16
Force the card to reboot with the new settings by entering the following at the [VxWorks Boot]: prompt:
@
The system will display a response similar to the following partial example:
[VxWorks Boot]: @ [VxWorks Boot]: @ unit number processor number file name code/gli3_pkt1.elf inet on ethernet (e) host inet (h) user (u) ftp password (pw) flags (f) : 0 : 0 : /ram00/projects/cdmaazlabs/frame/RF7224_14/ : : : : : 128.0.0.2:ffffff80 192.168.1.8 anonymous user 0x0
7
17
<<< remaining output omitted >>>
Allow the card to complete rebooting to the GLI3 > prompt and reach INS_ACT state (STA LED: slow flashing green; ACT LED: green).
NOTE
This process can take as long as 17 minutes to complete. Do not attempt to reboot or unseat the GLI3 card unless the LED indications do not change to INS_ACT after the 17 minute period has passed. 18 19 When the GLI3 reaches INS_ACT, reseat the redundant GLI3 in its backplane slot (if the BTS is so equipped). Allow the redundant GLI3 to boot, be crossloaded by the INS_ACT card with the new settings, and reach INS_SBY (STA LED: slow flashing green; ACT LED: OFF). table continued on next page
Table 7-31: Setting GLI3 Backhaul Type to Satellite and Correct Timeout Intervals Step 20 Action When the GLI3 card(s) are INS, contact the OMCR operator and:
S Advise the operator that the BTS is operational with the correct backhaul settings S Request notification when communication between the OMCR and the
BTS is confirmed 21 When notified that the OMCR and BTS can communicate, advise the operator that site operations are complete, and perform the procedures in the Prepare to leave the site section in Chapter 6.
SEP 2009
7-39
Module Front Panel LED Indicators and Connectors Module Front Panel LED Indicators and Connectors
Module Status Indicators
Each of the non-passive plug-in modules has a bi-color (green & red) LED status indicator located on the module front panel. The indicator is labeled PWR/ALM. If both colors are turned on, the indicator is yellow. Each plug-in module, except for the fan module, has its own alarm (fault) detection circuitry that controls the state of the PWR/ALM LED. The fan TACH signal of each fan module is monitored by the AMR. Based on the status of this signal, the AMR controls the state of the PWR/ALM LED on the fan module.
LED Status Combinations for All Modules (except GLI, CSM, BBX, MCC)
PWR/ALM LED The following list describes the states of the module status indicator.
S Solid GREEN module operating in a normal (fault free) condition. S Solid RED module is operating in a fault (alarm) condition due to
electrical hardware failure. Note that a fault (alarm) indication may or may not be due to a complete module failure and normal service may or may not be reduced or interrupted.
DC/DC Converter LED Status Combinations
The PWR CNVTR has alarm (fault) detection circuitry that controls the state of the PWR/ALM LED. This is true for both the CCCP and PA power converters. PWR/ALM LED The following list describes the states of the bi-color LED.
S Solid GREEN module operating in a normal (fault free) condition. S Solid RED module is operating in a fault (alarm) condition due to
electrical hardware problem.
7-40
SEP 2009
Module Front Panel LED Indicators and Connectors

CSM Indicator and Connectors
continued
Figure 7-2: CSM Front Panel Indicator and Monitor Connectors
SYNC MONITOR PWR/ALM INDICATOR
FREQ MONITOR
FW00303
PWR/ALM LED The CSM includes on-board alarm detection. Hardware and software/firmware state and alarm conditons are displayed by the front panel LED indicator (Figure 7-2). For detailed descriptions of displayed state/alarm indications refer to Figure 3-11 and Front Panel LED and Status Displays in the CSM System Time GPS, LFR, and HSO/MSO Verification section of Chapter 3. FREQ Monitor Connector A test port provided at the CSM front panel via a BNC receptacle allows monitoring of the 19.6608 MHz clock generated by the CSM. When both CSM 1 and CSM 2 are in an in-service (INS) condition, the CSM 2 clock signal frequency is the same as that output by CSM 1. The clock is a sine wave signal with a minimum amplitude of +2 dBm (800 mVpp) into a 50 load connected to this port. SYNC Monitor Connector A test port provided at the CSM front panel via a BNC receptacle allows monitoring of the Even Second Tick reference signal generated by the CSMs. At this port, the reference signal is a TTL active high signal with a pulse width of 153 nanoseconds.

MMI Connector
continued
Only accessible behind front panel. The RS232 MMI port connector is intended to be used primarily in the development or factory environment, but may be used in the field for debug/maintenance purposes.
GLI LED Status Combinations
NOTE GLIs must be GLI3 to support packet operation.
GLI The GLI module has indicators, controls and connectors as described below and shown in Table 7-32 (GLI3). The operating states of the LEDs are: ACTIVE Solid GREEN GLI is active. This means that the GLI has shelf control and is providing control of the digital interfaces. Off GLI is not active (i.e., Standby). The mate GLI should be active.
7-42
SEP 2009

ALARM
continued
S Solid RED GLI is in a fault condition or in reset. S While in reset transition, STATUS LED is OFF while GLI is
performing ROM boot (about 12 seconds for normal boot). performing RAM boot (about 4 seconds for normal boot).
S While in reset transition, STATUS LED is ON while GLI is S Off No Alarm.

STATUS
S Flashing GREEN GLI is in service (INS), in a stable operating

condition.
S On GLI is in OOS RAM state operating downloaded code. S Off GLI is in OOS ROM state operating boot code.
SPANS
S Solid GREEN Span line is connected and operating. S Solid RED Span line is disconnected or a fault condition exists.
GLI Pushbuttons and Connectors
RESET Pushbutton Depressing the RESET pushbutton causes a partial reset of the CPU and a reset of all board devices. The GLI is placed in the OOS_ROM state MMI Connector The RS232MMI port connector is intended to be used primarily in the development or factory environment but may be used in the field for debug/maintenance purposes. 10/100BaseT Ethernet Connectors Four 8contact modular receptacles are located on the front panel of a GLI3 card. The BPR A and BPR B connectors provide interfaces with for external BTS routers for packet traffic transport. The GLI connector provides two Ethernet connections in the same connector. The two connections provide a passthrough for each BTS internal 10/100BaseT subnet to support packet transport redundancy. The AUX connector provides an Ethernet interface for external devices which may be used with the BTS in the future. Table 7-32 shows the front panel of the GLI3 card and includes a description of the components.
SEP 2009
7-43

Table 7-32: GLI3 Front Panel LED
BPR A BPR B AUX
continued
Operating Status
Connects to either a BPR or expansion cage and is wired as an ethernet client. Connects to either a BPR or expansion cage and is wired as an ethernet client. Wired as an ethernet client for direct connection to a personal computer with a standard ethernet cable. It allows connection of ethernet sniffer when the ethernet switch is properly configured for port monitoring. Supports the crosscoupled ethernet circuits to the mate GLI using a double crossover cable. Pressing and releasing the switch resets all functions on the GLI3. OFF operating normally ON briefly during power-up when the Alarm LED turns OFF SLOW GREEN when the GLI3 is INS (in-service) OFF card is powered down, in initialization, or in standby GREEN operating normally YELLOW one or more of the equipped initialized spans is receiving a remote alarm indication signal from the far end RED one or more of the equipped initialized spans is in an alarm state An RS-232, serial, asynchronous communications link for use as an MMI port. This port supports 300 baud, up to a maximum of 115,200 baud communications. OFF operating normally ON briefly during power-up when the Alarm LED turns OFF SLOW GREEN when the GLI3 is INS (in-service) RAPID ORANGE (0.5 second intervals) Software upgrade in progress (for a firsttime upgrade to R18.0 or later release, can require up to 17 minutes) VERY RAPID ORANGE (0.1 second intervals) FTP in progress while card is operating on bootROM code. (No FTP indications in normal operation.) Shows the operating status of the redundant cards. The redundant card toggles automatically if the active card is removed or fails ON active card operating normally OFF standby card operating normally
BPR A
Diagram
GLI RESET ALARM
100BASE T to BTS Packet 100BASET Router or Expansion cage 100BASET Auxiliary Monitor Port
BPR RB AUX
SPAN
Dual 100BASET in a single RJ45 to Redundant (Mate) GLI3 Reset Switch

SPAN
GLI ALARM M RESET
Span (LED) Alarm (LED) Ala MMI Port Active (LED) Status (LED)
MMI
MMI STA ACT
STATUS
ACTIVE
7-44
SEP 2009

BBX LED Status Combinations
continued
PWR/ALM LED The BBX module has its own alarm (fault) detection circuitry that controls the state of the PWR/ALM LED. The following list describes the states of the bi-color LED:
S S S S S S S
PA Shelf LED Status Combinations
Solid GREEN INS_ACT no alarm Solid RED Red initializing or power-up alarm Slowly Flashing GREEN OOS_ROM no alarm Long RED/Short GREEN OOS_ROM alarm Rapidly Flashing GREEN OOS_RAM no alarm Short RED/Short GREEN OOS_RAM alarm Long GREEN/Short RED INS_ACT alarm
PA Module LED Each PA module contains a bicolor LED just above the MMI connector on the front panel of the module. Interpret this LED as follows:
S GREEN PA module is active and is reporting no alarms (Normal

condition).
S Flashing GREEN/RED PA module is active but is reporting an low

input power condition. If no BBX is keyed, this is normal and does not constitute a failure.
MCC LED Status Combinations
The MCC module has LED indicators and connectors as described below (see Figure 7-3). Note that the figure does not show the connectors as they are concealed by the removable lens. The LED indicators and their states are as follows: PWR/ALM LED
S RED fault on module

ACTIVE LED Off module is inactive, off-line, or not processing traffic. Slowly Flashing GREEN OOS_ROM no alarm. Rapidly Flashing Green OOS_RAM no alarm. Solid GREEN module is INS_ACT, on-line, processing traffic.
S S S S
PWR/ALM and ACTIVE LEDs
S Solid RED module is powered but is in reset or the BCP is inactive.


MMI Connectors
continued
S The RS232 MMI port connector (four-pin) is intended to be used
primarily in the development or factory environment but may be used in the field for debugging purposes. primarily in the development environment but may be used in the field for high data rate debugging purposes.
S The RJ11 ethernet port connector (eight-pin) is intended to be used

Figure 7-3: MCC Front Panel
LED PWR/ALM
PWR/ALM
COLOR RED
OPERATING STATUS
PWR/ALM LED
OFF operating normally ON briefly during power-up and during failure conditions An alarm is generated in the event of a failure GREEN RAPIDLY BLINKING Card is code-loaded but not enabled SLOW BLINKING Card is not code-loaded ON card is code-loaded and enabled (INS_ACTIVE) ON fault condition SLOW FLASHING (alternating with green) CHI bus inactive on power-up
ACTIVE
LENS (REMOVABLE)
RED
ACTIVE
ACTIVE LED
7-46
SEP 2009
Appendix A: Data Sheets

Appendix Content
Optimization (PreATP) Data Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verification of Test Equipment Used . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preliminary Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PrePower and Initial Power Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Optimization Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPS Receiver Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LPA IM Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LPA Convergence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Bay Level Offset/Power Output Verification for 3Sector Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Bay Level Offset/Power Output Verification for 6Sector Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Redundancy/Alarm Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Antenna VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RX Antenna VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMR Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Serial Number Check List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCCP Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LPAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-1 A-1 A-2 A-2 A-3 A-4 A-5 A-6 A-7 A-8 A-13 A-15 A-15 A-16 A-16 A-17 A-17 A-18
SEP 2009
Table of Contents
continued
Notes
SEP 2009
Optimization (PreATP) Data Sheets Optimization (PreATP) Data Sheets

Verification of Test Equipment Used
Table A-1: Verification of Test Equipment Used Manufacturer Model Serial Number
Comments:________________________________________________________
SEP 2009 1X SC4812T CLPA BTS Optimization/ATP A-1
Optimization (PreATP) Data Sheets
continued
__________________________________________________________________
Site Checklist
Table A-2: Site Checklist OK Deliveries Floor Plan Inter Frame Cables: Ethernet Frame Ground Power Factory Data: BBX Test Panel Site Temperature Dress Covers/Brackets Parameter Specification Per established procedures Verified Per procedure Per procedure Per procedure Per procedure Per procedure Comments
Preliminary Operations
Table A-3: Preliminary Operations OK Parameter Shelf ID Dip Switches BBX Jumpers Ethernet LAN verification Specification Per site equipage Verified per procedure Verified per procedure Comments
Comments:_________________________________________________________
A-2
SEP 2009

PrePower and Initial Power Tests
continued
Table A-4: Prepower Checklist OK Parameter Prepowerup tests Specification Verify power supply output voltage at the top of each BTS frame is within specifications verified verified verified verified verified isolated isolated installed installed Verify power supply output voltage at the top of each BTS frame is within specifications: Comments
Internal Cables: ISB (all cages) CSM (all cages) Power (all cages) Ethernet Connectors LAN A ohms LAN B ohms LAN A shield LAN B shield Ethernet Boots Air Impedance Cage (single cage) Initial powerup tests
Comments:_________________________________________________________
SEP 2009
A-3

General Optimization Checklist
continued
Table A-5: Prepower Checklist OK LEDs Frame fans LMF to BTS Connection Preparing the LMF Log into the LMF PC Create site specific BTS directory Create masterbtscdma directory Download device loads Moving/Linking files Ping LAN A Ping LAN B Download/Enable MGLIs Download/Enable GLIs Set Site Span Configuration Download CSMs Download Enable CSMs Download/Enable MCCs Download BBXs Test Set Calibration Parameter Specification illuminated operational per procedure per procedure per procedure per procedure per procedure per procedure per procedure per procedure per procedure per procedure per procedure per procedure per procedure per procedure per procedure per procedure per procedure Comments
Comments:_________________________________________________________
A-4
SEP 2009

GPS Receiver Operation
continued
Table A-6: GPS Receiver Operation OK Parameter GPS Receiver Control Task State: tracking satellites Initial Position Accuracy: Current Position: lat lon height Current Position: satellites tracked Estimated: (>4) satellites tracked,(>4) satellites visible Surveyed: (>1) satellite tracked,(>4) satellites visible Current reference source: Number: 0; Status: Good; Valid: Yes Specification Verify parameter Verify Estimated or Surveyed RECORD in ms and cm also convert to deg min sec Verify parameter as appropriate: Comments
Verify parameter
Comments:_________________________________________________________
SEP 2009
A-5

LPA IM Reduction
continued
Table A-7: LPA IM Reduction

Parameter OK LPA # CARRIER 4:1 & 2:1 3Sector 2:1 6Sector Dual BP 3Sector Dual BP 6Sector Specification Comments
1A 1B 1C 1D 2A 2B 2C 2D 3A 3B 3C 3D 4A 4B 4C 4D
C1 C1 C1 C1 C2 C2 C2 C2 C3 C3 C3 C3 C4 C4 C4 C4
C1 C1 C1 C1 C2 C2 C2 C2 C1 C1 C1 C1 C2 C2 C2 C2
C1 C1 C1 C1 C2 C2 C2 C2
C1 C1 C1 C1
No Alarms No Alarms No Alarms No Alarms No Alarms No Alarms No Alarms No Alarms
C1 C1 C1 C1
No Alarms No Alarms No Alarms No Alarms No Alarms No Alarms No Alarms No Alarms
Comments:_________________________________________________________
A-6
SEP 2009

LPA Convergence
continued
Table A-8: LPA Convergence OK Parameter LPA # Converged 1A 1B 1C 1D 2A 2B 2C 2D 3A 3B 3C 3D 4A 4B 4C 4D Verify per procedure & upload convergence data Verify per procedure & upload convergence data Verify per procedure & upload convergence data Specification Verify per procedure & upload convergence data Data
SEP 2009
A-7

TX Bay Level Offset/Power Output Verification for 3Sector Configurations
continued
1Carrier 2Carrier Nonadjacent Channels 4Carrier Nonadjacent Channels
Table A-9: TX BLO Calibration (3Sector: 1; 2; and 4Carrier Nonadjacent Channels) OK Calibrate carrier 4 TX Bay Level Offset = 42 dB (+4 dB) prior to calibration Calibrate carrier 3 TX Bay Level Offset = 42 dB (+4 dB) prior to calibration Calibrate carrier 2 TX Bay Level Offset = 42 dB (+4 dB) prior to calibration Calibrate carrier 1 TX Bay Level Offset = 42 dB (+4 dB) prior to calibration Parameter Specification Comments BBX1, ANT1 = BBXr, ANT1 = BBX2, ANT2 = BBXr, ANT2 = BBX3, ANT3 = BBXr, ANT3 = BBX7, ANT1 = BBXr, ANT1 = BBX8, ANT2 = BBXr, ANT2 = BBX9, ANT3 = BBXr, ANT3 = BBX4, ANT1 = BBXr, ANT1 = BBX5, ANT2 = BBXr, ANT2 = BBX6, ANT3 = BBXr, ANT3 = BBX10, ANT1 = BBXr, ANT1 = BBX11, ANT2 = BBXr, ANT2 = BBX12, ANT3 = BBXr, ANT3 = dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB
A-8
SEP 2009
continued
Table A-9: TX BLO Calibration (3Sector: 1; 2; and 4Carrier Nonadjacent Channels) OK Calibration Audit carrier 4 0 dB (+0.5 dB) for gain set resolution post calibration Calibration Audit carrier 3 0 dB (+0.5 dB) for gain set resolution post calibration Calibration Audit carrier 2 0 dB (+0.5 dB) for gain set resolution post calibration Calibration Audit carrier 1 0 dB (+0.5 dB) for gain set resolution post calibration Parameter Specification Comments BBX1, ANT1 = BBXr, ANT1 = BBX2, ANT2 = BBXr, ANT2 = BBX3, ANT3 = BBXr, ANT3 = BBX7, ANT1 = BBXr, ANT1 = BBX8, ANT2 = BBXr, ANT2 = BBX9, ANT3 = BBXr, ANT3 = BBX4, ANT1 = BBXr, ANT1 = BBX5, ANT2 = BBXr, ANT2 = BBX6, ANT3 = BBXr, ANT3 = BBX10, ANT1 = BBXr, ANT1 = BBX11, ANT2 = BBXr, ANT2 = BBX12, ANT3 = BBXr, ANT3 = dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB
Comments:________________________________________________________ __________________________________________________________________
SEP 2009
A-9
continued
2Carrier Adjacent Channel Table A-10: TX Bay Level Offset Calibration (3Sector: 2Carrier Adjacent Channels) OK Calibration Audit carrier 2 0 dB (+0.5 dB) for gain set resolution post calibration Calibration Audit carrier 1 0 dB (+0.5 dB) for gain set resolution post calibration Calibrate carrier 2 TX Bay Level Offset = 42 dB (typical), 38 dB (minimum) prior to calibration Calibrate carrier 1 TX Bay Level Offset = 42 dB (typical), 38 dB (minimum) prior to calibration Parameter Specification Comments BBX1, ANT1 = BBXr, ANT1 = BBX2, ANT2 = BBXr, ANT2 = BBX3, ANT3 = BBXr, ANT3 = BBX7, ANT4 = BBXr, ANT4 = BBX8, ANT5 = BBXr, ANT5 = BBX9, ANT6 = BBXr, ANT6 = BBX1, ANT1 = BBXr, ANT1 = BBX2, ANT2 = BBXr, ANT2 = BBX3, ANT3 = BBXr, ANT3 = BBX7, ANT4 = BBXr, ANT4 = BBX8, ANT5 = BBXr, ANT5 = BBX9, ANT6 = BBXr, ANT6 = dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB
Comments:________________________________________________________ __________________________________________________________________
A-10
SEP 2009
continued
3Carrier Adjacent Channels 4Carrier Adjacent Channels Table A-11: TX Bay Level Offset Calibration (3Sector: 3 or 4Carrier Adjacent Channels) OK Calibration Audit carrier 1 0 dB (+0.5 dB) for gain set resolution post calibration Calibrate carrier 4 TX Bay Level Offset = 42 dB (+4 dB) prior to calibration Calibrate carrier 3 TX Bay Level Offset = 42 dB (+4 dB) prior to calibration Calibrate carrier 2 TX Bay Level Offset = 42 dB (+4 dB) prior to calibration Calibrate carrier 1 TX Bay Level Offset = 42 dB (+4 dB) prior to calibration Parameter Specification Comments BBX1, ANT1 = BBXr, ANT1 = BBX2, ANT2 = BBXr, ANT2 = BBX3, ANT3 = BBXr, ANT3 = BBX7, ANT1 = BBXr, ANT1 = BBX8, ANT2 = BBXr, ANT2 = BBX9, ANT3 = BBXr, ANT3 = BBX4, ANT4 = BBXr, ANT4 = BBX5, ANT5 = BBXr, ANT5 = BBX6, ANT6 = BBXr, ANT6 = BBX10, ANT4 = BBX3, ANT4 = BBX11, ANT5 = BBXr, ANT5 = BBX12, ANT6 = BBXr, ANT6 = BBX1, ANT1 = BBXr, ANT1 = BBX2, ANT2 = BBXr, ANT2 = BBX3, ANT3 = BBXr, ANT3 = dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB
SEP 2009
A-11
continued
Table A-11: TX Bay Level Offset Calibration (3Sector: 3 or 4Carrier Adjacent Channels) OK Calibration Audit carrier 4 0 dB (+0.5 dB) for gain set resolution post calibration Calibration Audit carrier 3 0 dB (+0.5 dB) for gain set resolution post calibration Calibration Audit carrier 2 0 dB (+0.5 dB) for gain set resolution post calibration Parameter Specification Comments BBX7, ANT1 = BBXr, ANT1 = BBX8, ANT2 = BBXr, ANT2 = BBX9, ANT3 = BBXr, ANT3 = BBX4, ANT4 = BBXr, ANT4 = BBX5, ANT5 = BBXr, ANT5 = BBX6, ANT6 = BBXr, ANT6 = BBX10, ANT4 = BBXr, ANT4 = BBX11, ANT5 = BBXr, ANT5 = BBX12, ANT6 = BBXr, ANT6 = dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB
Comments:________________________________________________________ __________________________________________________________________
A-12
SEP 2009

TX Bay Level Offset/Power Output Verification for 6Sector Configurations
continued
1Carrier 2Carrier Nonadjacent Channels
Table A-12: TX BLO Calibration (6Sector: 1Carrier, 2Carrier Nonadjacent Channels) OK Parameter Specification Comments BBX1, ANT1 = BBXr, ANT1 = BBX2, ANT2 = BBXr, ANT2 = Calibrate carrier 1 TX Bay y Level Offset = 42 dB (typical), ( yp ), 38 dB (minimum) prior to calibration BBX3, ANT3 = BBXr, ANT3 = BBX4, ANT4 = BBXr, ANT4 = BBX5, ANT5 = BBXr, ANT5 = BBX6, ANT6 = BBXr, ANT6 = BBX7, ANT1 = BBXr, ANT1 = BBX8, ANT2 = BBXr, ANT2 = Calibrate carrier 2 TX Bay y Level Offset = 42 dB (typical), ( yp ), 38 dB (minimum) prior to calibration BBX9, ANT3 = BBXr, ANT3 = BBX10, ANT4 = BBX3, ANT4 = BBX11, ANT5 = BBXr, ANT5 = BBX12, ANT6 = BBXr, ANT5 = dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB
SEP 2009
A-13
continued
Table A-12: TX BLO Calibration (6Sector: 1Carrier, 2Carrier Nonadjacent Channels) OK Calibration Audit carrier 2 Calibration Audit carrier 1 Parameter Specification Comments BBX1, ANT1 = BBXr, ANT1 = BBX2, ANT2 = BBXr, ANT2 = 0 dB (+0.5 ( dB) ) for gain g set resolution post calibration BBX3, ANT3 = BBXr, ANT3 = BBX4, ANT4 = BBXr, ANT4 = BBX5, ANT5 = BBXr, ANT5 = BBX6, ANT6 = BBXr, ANT6 = BBX7, ANT1 = BBXr, ANT1 = BBX8, ANT2 = BBXr, ANT2 = 0 dB (+0.5 ( dB) ) for gain g set resolution post calibration BBX9, ANT3 = BBXr, ANT3 = BBX10, ANT4 = BBXr, ANT4 = BBX11, ANT5 = BBXr, ANT5 = BBX12, ANT6 = BBXr, ANT6 = dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB dB
Comments:________________________________________________________ __________________________________________________________________
A-14
SEP 2009

BTS Redundancy/Alarm Tests
continued
Table A-13: BTS Redundancy/Alarm Tests OK Parameter SIF: Misc. alarm tests GLI redundancy test Power supply/converter redundancy Misc. alarm tests CSM and GPS redundancy/alarm tests LPA redundancy test Specification Verify per procedure Verify per procedure Verify per procedure Verify per procedure Verify per procedure Verify per procedure Data
Comments:________________________________________________________ __________________________________________________________________
TX Antenna VSWR
Table A-14: TX Antenna VSWR OK Parameter VSWR Antenna 1 VSWR Antenna 2 VSWR Antenna 3 VSWR Antenna 4 VSWR Antenna 5 VSWR Antenna 6 Specification < (1.5 : 1) < (1.5 : 1) < (1.5 : 1) < (1.5 : 1) < (1.5 : 1) < (1.5 : 1) Data
Comments:________________________________________________________ __________________________________________________________________

RX Antenna VSWR
continued
Table A-15: RX Antenna VSWR OK Parameter VSWR Antenna 1 VSWR Antenna 2 VSWR Antenna 3 VSWR Antenna 4 VSWR Antenna 5 VSWR Antenna 6 Specification < (1.5 : 1) < (1.5 : 1) < (1.5 : 1) < (1.5 : 1) < (1.5 : 1) < (1.5 : 1) Data
Comments:_________________________________________________________
AMR Verification
Table A-16: AMR CDI Alarm Input Verification OK Parameter Verify CDI alarm input operation (ALARM A (numbers 1 18) Verify CDI alarm input operation (ALARM B (numbers 19 36) Specification BTS Relay #XX Contact Alarm Sets/Clears BTS Relay #XX Contact Alarm Sets/Clears Data
Comments:_________________________________________________________
A-16
SEP 2009
Site Serial Number Check List Site Serial Number Check List
Date
CCCP Shelf
Site
Site I/O A & B CCCP Shelf CSM1 CSM2 HSO/MSO/HSOX CCD1 CCD2 AMR1 AMR2 MPC1 MPC2 Fans 13 GLI1 GLI2 BBX1 BBX2 BBX3 BBX4 BBX5 BBX6 BBX7 BBX8 BBX9 BBX10 BBX11 BBX12 BBXr MCC1 MCC2 MCC3 MCC4 MCC5 MCC6 MCC7 MCC8 MCC9 . . . continued on next page
Site Serial Number Check List

MCC10 MCC11 MCC12 CIO SWITCH PAC CCCP PS1 CCCP PS2 CCCP PS3 PSM #1 (48 V only) PSM #2 (48 V only) PSM #3 (48 V only) PSM #4 (48 V only) PSM #5 (48 V only)
LPAs
LPA 1A LPA 1B LPA 1C LPA 1D LPA 2A LPA 2B LPA 2C LPA 2D LPA 3A LPA 3B LPA 3C LPA 3D LPA 4A LPA 4B LPA 4C LPA 4D
continued
A-18
SEP 2009
Appendix B: PN Offset/I & Q Offset Register Programming Information

Appendix Content
PN Offset Programming Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PN Offset Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PN Offset Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B-1 B-1 B-1
SEP 2009
Table of Contents
continued
Notes
SEP 2009
PN Offset Programming Information PN Offset Programming Information

PN Offset Background
B
All channel elements transmitted from a BTS in a particular 1.25 MHz CDMA channel are orthonogonally spread by 1 of 128 possible Walsh code functions; additionally, they are also spread by a quadrature pair of PN sequences unique to each sector. Overall, the mobile uses this to differentiate multiple signals transmitted from the same BTS (and surrounding BTS) sectors, and to synchronize to the next strongest sector. The PN offset per sector is stored on the BBXs, where the corresponding I & Q registers reside. The PN offset values are determined on a per BTS/per sector(antenna) basis as determined by the appropriate cdf file content. A breakdown of this information is found in Table B-1.
PN Offset Usage
Only the 14chip delay is currently in use. It is important to determine the RF chip delay to be able to test the BTS functionality. This can be done by ascertaining if the CDF file FineTxAdj value was set to on when the MCC was downloaded with image data. The FineTxAdj value is used to compensate for the processing delay (approximately 20 mS) in the BTS using any type of mobile meeting IS97 specifications. If the FineTxAdj value in the cdf file is 213 (D5 HEX), FineTxAdj has been set for the 14 chip table. NOTE CDF file I and Q values can be represented in DECIMAL or HEX. If using HEX, add 0x before the HEX value. If necessary, convert HEX values in Table B-1 to decimal before comparing them to cdf file I & Q value assignments.
SEP 2009
B-1
PN Offset Programming Information
continued
Table B-1: PnMask I and PnMask Q Values for PilotPn
Pilot PN
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
I
17523 32292 4700 14406 14899 17025 14745 2783 5832 12407 31295 7581 18523 29920 25184 26282 30623 15540 23026 20019 4050 1557 30262 18000 20056 12143 17437 17438 5102 9302 17154 5198 4606 24804 17180 10507 10157 23850 31425 4075 10030 16984 14225 26519 27775 30100 7922 14199 17637 23081 5099
(Dec.)
14Chip Delay Q
23459 32589 17398 26333 4011 2256 18651 1094 21202 13841 31767 18890 30999 22420 20168 12354 11187 11834 10395 28035 27399 22087 2077 13758 11778 3543 7184 2362 25840 12177 10402 1917 17708 10630 6812 14350 10999 25003 2652 19898 2010 25936 28531 11952 31947 25589 11345 28198 13947 8462 9595
I
4473 7E24 125C 3846 3A33 4281 3999 0ADF 16C8 3077 7A3F 1D9D 485B 74E0 6260 66AA 779F 3CB4 59F2 4E33 0FD2 0615 7636 4650 4E58 2F6F 441D 441E 13EE 2456 4302 144E 1FE 60E4 431C 290B 27AD 5D2A 7AC1 0FEB 272E 4258 3791 6797 6C7F 7594 1EF2 3777 44E5 5A29 13EB
(Hex.)
Q
5BA3 7F4D 43F6 66DD 0FAB 08D0 48DB 0446 52D2 3611 7C17 49CA 7917 5794 4EC8 3042 2BB3 2E3A 289B 6D83 6B07 5647 081D 35BE 2E02 0DD7 1C10 093A 64F0 2F91 28A2 077D 452C 2986 1A9C 380E 2AF7 61AB 0A5C 4DBA 07DA 6550 6F73 2EB0 7CCB 63F5 2C51 6E26 367B 210E 257B
B-2
SEP 2009
continued

Pilot PN
51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
I
32743 7114 7699 19339 28212 29587 19715 14901 20160 22249 26582 7153 15127 15274 23149 16340 27052 13519 10620 15978 27966 12479 1536 3199 4549 17888 13117 7506 27626 31109 29755 26711 20397 18608 7391 23168 23466 15932 25798 28134 28024 6335 21508 26338 17186 22462 3908 25390 27891 9620
(Dec.)
14Chip Delay Q
4670 14672 29415 20610 6479 10957 18426 22726 5247 29953 5796 16829 4528 5415 10294 17046 7846 10762 13814 16854 795 9774 24291 3172 2229 21283 16905 7062 7532 25575 14244 28053 30408 5094 16222 7159 174 25530 2320 23113 23985 2604 1826 30853 15699 2589 25000 18163 12555 8670
I
7FE7 1BCA 1E13 4B8B 6E34 7393 4D03 3A35 4EC0 56E9 67D6 1BF1 3B17 3BAA 5A6D 3FD4 69AC 34CF 297C 3E6A 6D3E 30BF 0600 0C7F 11C5 45E0 333D 1D52 6BEA 7985 743B 6857 4FAD 48B0 1CDF 5A80 5BAA 3E3C 64C6 6DE6 6D78 18BF 5404 66E2 4322 57BE 0F44 632E 6CF3 2594
(Hex.)
Q
123E 3950 72E7 5082 194F 2ACD 47FA 58C6 147F 7501 16A4 41BD 11B0 1527 2836 4296 1EA6 2A0A 35F6 41D6 031B 262E 5EE3 0C64 08B5 5323 4209 1B96 1D6C 63E7 37A4 6D95 76C8 13E6 3F5E 1BF7 00AE 63BA 0910 5A49 5DB1 0A2C 0722 7885 3D53 0A1D 61A8 46F3 310B 21DE
SEP 2009
B-3
continued
Pilot PN
101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150
I
6491 16876 17034 32405 27417 8382 5624 1424 13034 15682 27101 8521 30232 6429 27116 4238 5128 14846 13024 10625 31724 13811 24915 1213 2290 31551 12088 7722 27312 23130 594 25804 31013 32585 3077 17231 31554 8764 15375 13428 17658 13475 22095 24805 4307 23292 1377 28654 6350 16770
(Dec.)
14Chip Delay Q
1290 4407 1163 12215 7253 8978 25547 3130 31406 6222 20340 25094 23380 10926 22821 31634 4403 689 27045 27557 16307 22338 27550 22096 23136 12199 1213 936 6272 32446 13555 8789 24821 21068 31891 5321 551 12115 4902 1991 14404 17982 19566 2970 23055 15158 29094 653 19155 23588
I
195B 41EC 428A 7E95 6B19 20BE 15F8 0590 32EA 3D42 69DD 2149 7618 191D 69EC 108E 1408 39FE 32E0 2981 7BEC 35F3 6153 04BD 08F2 7B3F 2F38 1E2A 6AB0 5A5A 0252 64CC 7925 7F49 0C05 434F 7B42 223C 3C0F 3474 44FA 34A3 564F 60E5 10D3 5AFC 0561 6FEE 18CE 4182
(Hex.)
Q
050A 1137 048B 2FB7 1C55 2312 63CB 0C3A 7AAE 184E 4F74 6206 5B54 2AAE 5925 7B92 1133 02B1 69A5 6BA5 3FB3 5742 6B9E 5650 5A60 2FA7 04BD 03A8 1880 7EBE 34F3 2255 60F5 524C 7C93 14C9 0227 2F53 1326 07C7 3844 463E 4C6E 0B9A 5A0F 3B36 71A6 028D 4AD3 5C24
B-4
SEP 2009
continued

Pilot PN
151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200
I
14726 25685 21356 12149 28966 22898 1713 30010 2365 27179 29740 5665 23671 1680 25861 25712 19245 26887 30897 11496 1278 31555 29171 20472 5816 30270 22188 6182 32333 14046 15873 19843 29367 13352 22977 31691 10637 25454 18610 6368 7887 7730 23476 889 21141 20520 21669 15967 21639 31120
(Dec.)
14Chip Delay Q
10878 31060 30875 11496 24545 9586 20984 30389 7298 18934 23137 24597 23301 7764 14518 21634 11546 26454 15938 9050 3103 758 16528 20375 10208 17698 8405 28634 1951 20344 26696 3355 11975 31942 9737 9638 30643 13230 22185 2055 8767 15852 16125 6074 31245 15880 20371 8666 816 22309
I
3986 6455 536C 2F75 7126 5972 06B1 753A 093D 6A2B 742C 1621 5C77 0690 6505 6470 4B2D 6907 78B1 2CE8 04FE 7B43 71F3 4FF8 16B8 763E 56AC 1826 7E4D 36DE 3E01 4D83 72B7 3428 59C1 7BCB 298D 636E 48B2 18E0 1ECF 1E32 5BB4 0379 5295 5028 54A5 3E5F 5487 7990
(Hex.)
Q
2A7E 7954 789B 2CE8 5FE1 2572 51F8 76B5 1C82 49F6 5A61 6015 5B05 1E54 38B6 5482 2D1A 6756 3E42 235A 0C1F 02F6 4090 4F97 27E0 4522 20D5 6FDA 079F 4F78 6848 0D1B 2EC7 7CC6 2609 25A6 77B3 33AE 56A9 0807 223F 3DEC 3EFD 17BA 7A0D 3E08 4F93 21DA 0330 5725
SEP 2009
B-5
continued
Pilot PN
201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250
I
3698 16322 17429 21730 17808 30068 12737 28241 20371 13829 13366 25732 19864 5187 23219 28242 6243 445 21346 13256 18472 25945 31051 1093 5829 31546 29833 18146 24813 47 3202 21571 7469 25297 8175 28519 4991 7907 17728 14415 30976 26376 19063 19160 3800 8307 12918 19642 24873 22071
(Dec.)
14Chip Delay Q
29563 13078 10460 17590 20277 19988 6781 32501 6024 20520 31951 26063 27203 6614 10970 5511 17119 16064 31614 4660 13881 16819 6371 24673 6055 10009 5957 11597 22155 15050 16450 27899 2016 17153 15849 30581 3600 4097 671 20774 24471 27341 19388 25278 9505 26143 13359 2154 13747 27646
I
0E72 3FC2 4415 54E2 4590 7574 31C1 6E51 4F93 3605 3436 6484 4D98 1443 5AB3 6E52 1863 01BD 5362 33C8 4828 6559 794B 0445 16C5 7B3A 7489 46E2 60ED 002F 0C82 5443 1D2D 62D1 1FEF 6F67 137F 1EE3 4540 384F 7900 6708 4A77 4AD8 0ED8 2073 3276 4CBA 6129 5637
(Hex.)
Q
737B 3316 28DC 44B6 4F35 4E14 1A7D 7EF5 1788 5028 7CCF 65CF 6A43 19D6 2ADA 1587 42DF 3EC0 7B7E 1234 3639 41B3 18E3 6061 17A7 2719 1745 2D4D 568B 3ACA 4042 6CFB 07E0 4301 3DE9 7775 0E10 1001 029F 5126 5F97 6ACD 4BBC 62BE 2521 661F 342F 086A 35B3 6BFE
B-6
SEP 2009
continued

Pilot PN
251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300
I
13904 27198 3685 16820 22479 6850 15434 19332 8518 14698 21476 30475 23984 1912 26735 15705 3881 20434 16779 31413 16860 8322 28530 26934 18806 20216 9245 8271 18684 8220 6837 9613 31632 27448 12417 30901 9366 12225 21458 6466 8999 26718 3230 27961 28465 6791 17338 11832 11407 15553
(Dec.)
14Chip Delay Q
1056 1413 3311 4951 749 6307 961 2358 28350 31198 11467 8862 6327 7443 28574 25093 6139 22047 32545 7112 28535 10378 15065 5125 12528 23215 20959 3568 26453 29421 24555 10779 25260 16084 26028 29852 14978 12182 25143 15838 5336 21885 20561 30097 21877 23589 26060 9964 25959 3294
I
3650 6A3E 0E65 41B4 57CF 1AC2 3C4A 4B84 2146 396A 53E4 770B 5DB0 0778 686F 3D59 0F29 4FD2 418B 7AB5 41DC 2082 6F72 6936 4976 4EF8 241D 204F 48FC 201C 1AB5 258D 7B90 6B38 3081 78B5 2496 2FC1 53D2 1942 2327 685E 0C9E 6D39 6F31 1A87 43BA 2E38 2C8F 3CC1
(Hex.)
Q
0420 0585 0CEF 1357 02ED 18A3 03C1 0936 6EBE 79DE 2CCB 229E 18B7 1D13 6F9E 6205 17FB 561F 7F21 1BC8 6F77 288A 3AD9 1405 30F0 5AAF 51DF 0DF0 6755 72ED 5FEB 2A1B 62AC 3ED4 65AC 749C 3A82 2F96 6237 3DDE 14D8 557D 5051 7591 5575 5C25 65CC 26EC 6567 0CDE
SEP 2009
B-7
continued
Pilot PN
301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350
I
17418 14952 52 27254 15064 10942 377 14303 24427 26629 20011 16086 24374 9969 29364 25560 28281 7327 32449 26334 14760 15128 29912 4244 8499 9362 10175 30957 12755 19350 1153 29304 6041 21668 28048 10096 23388 15542 24013 2684 19018 25501 4489 31011 29448 25461 11846 30331 10588 32154
(Dec.)
14Chip Delay Q
30173 15515 5371 10242 28052 14714 19550 8866 15297 10898 31315 19475 1278 11431 31392 4381 14898 23959 16091 9037 24162 6383 27183 16872 9072 12966 28886 25118 20424 6729 20983 12372 13948 27547 8152 17354 17835 14378 7453 26317 5955 10346 13200 30402 7311 3082 21398 31104 24272 27123
I
440A 3A68 0034 6A76 3AD8 2ABE 0179 37DF 5F6B 6805 4E2B 3ED6 5F36 26F1 72B4 63D8 6E79 1C9F 7EC1 66DE 39A8 3B18 74D8 1094 2133 2492 27BF 78ED 31D3 4B96 0481 7278 1799 54A4 6D90 2770 5B5C 3CB6 5DCD 0A7C 4A4A 639D 1189 7923 7308 6375 2E46 767B 295C 7D9A
(Hex.)
Q
75DD 3C9B 14FB 2802 6D94 397A 4C5E 22A2 3BC1 2A92 7A53 4C13 04FE 2CA7 7AA0 111D 3A32 5D97 3EDB 234D 5E62 18EF 6A2F 41E8 2370 32A6 70D6 621E 4FC8 1A49 51F7 3054 367C 6B9B 1FD8 43CA 45AB 382A 1D1D 66CD 1743 286A 3390 76C2 1C8F 0C0A 5396 7980 5ED0 69F3
B-8
SEP 2009
continued

Pilot PN
351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400
I
29572 13173 10735 224 12083 22822 2934 27692 10205 7011 22098 2640 4408 102 27632 19646 26967 32008 7873 655 25274 16210 11631 8535 19293 12110 21538 10579 13032 14717 11666 25809 5008 32418 22175 11742 22546 21413 133 4915 8736 1397 18024 15532 26870 5904 24341 13041 23478 1862
(Dec.)
14Chip Delay Q
5578 25731 10662 11084 31098 16408 6362 2719 14732 22744 1476 8445 21118 22198 22030 10363 25802 2496 31288 24248 14327 23154 13394 1806 17179 10856 25755 15674 7083 29096 3038 16277 25525 20465 28855 32732 20373 9469 26155 6957 12214 21479 31914 32311 11276 20626 423 2679 15537 10818
I
7384 3375 29EF 00E0 2F33 5926 0B76 6C2C 27DD 1B63 5652 0A50 1138 0066 6BF0 4CBE 6957 7D08 1EC1 028F 62BA 3F52 2D6F 2157 4B5D 2F4E 5422 2953 32E8 397D 2D92 64D1 1390 7EA2 569F 2DDE 5812 53A5 0085 1333 2220 0575 4668 3CAC 68F6 1710 5F15 32F1 5BB6 0746
(Hex.)
Q
15CA 6483 29A6 2B4C 797A 4018 18DA 0A9F 398C 58D8 05C4 20FD 527E 56B6 560E 287B 64CA 09C0 7A38 5EB8 37F7 5A72 3452 070E 431B 2A68 649B 3D3A 1BAB 71A8 0BDE 3F95 63B5 4FF1 70B7 7FDC 4F95 24FD 662B 1B2D 2FB6 53E7 7CAA 7E37 2C0C 5092 01A7 0A77 3CB1 2A42
SEP 2009
B-9
continued
Pilot PN
401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450
I
5850 5552 12589 23008 27636 17600 17000 21913 30320 28240 7260 17906 5882 22080 12183 23082 17435 18527 31902 18783 20027 7982 20587 10004 13459 13383 28930 4860 13108 24161 20067 2667 13372 28743 24489 249 19960 29682 31101 27148 26706 5148 4216 5762 245 21882 3763 206 28798 32402
(Dec.)
14Chip Delay Q
23074 20250 14629 29175 13943 11072 29492 5719 7347 12156 25623 27725 28870 31478 28530 24834 9075 32265 3175 17434 12178 25613 31692 25384 18908 25816 4661 31115 7691 1311 16471 15771 16112 21062 29690 10141 19014 22141 11852 26404 30663 32524 28644 10228 23536 18045 25441 27066 13740 13815
I
16DA 15B0 312D 59E0 6BF4 44C0 4268 5599 7670 6E50 1C5C 45F2 16FA 5640 2F97 5A2A 441B 485F 7C9E 495F 4E3B 1F2E 506B 2714 3493 3447 7102 12FC 3334 5E61 4E63 0A6B 343C 7047 5FA9 00F9 4DF8 73F2 797D 6A0C 6852 141C 1078 1682 00F5 557A 0EB3 00CE 707E 7E92
(Hex.)
Q
5A22 4F1A 3925 71F7 3677 2B40 7334 1657 1CB3 2F7C 6417 6C4D 70C6 7AF6 6F72 6102 2373 7E09 0C67 441A 2F92 640D 7BCC 6328 49DC 64D8 1235 798B 1E0B 051F 4057 3D9B 3EF0 5246 73FA 279D 4A46 567D 2E4C 6724 77C7 7F0C 6FE4 27F4 5BF0 467D 6361 69BA 35AC 35F7
B-10
SEP 2009
continued

Pilot PN
451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500
I
13463 15417 23101 14957 23429 12990 12421 28875 4009 1872 15203 30109 24001 4862 14091 6702 3067 28643 21379 20276 25337 19683 10147 16791 17359 13248 22740 13095 10345 30342 27866 9559 8808 12744 11618 27162 17899 29745 31892 23964 23562 2964 18208 15028 21901 24566 18994 13608 27492 11706
(Dec.)
14Chip Delay Q
3684 23715 15314 32469 9816 4444 5664 7358 27264 28128 30168 29971 3409 16910 20739 10191 12819 19295 10072 15191 27748 720 29799 27640 263 24734 16615 20378 25116 19669 14656 27151 28728 25092 22601 2471 25309 15358 17739 12643 32730 19122 16870 10787 18400 20295 1937 17963 7438 12938
I
3497 3C39 5A3D 3A6D 5B85 32BE 3085 70CB 0FA9 0750 3B63 759D 5DC1 12FE 370B 1A2E 0BFB 6FE3 5383 4F34 62F9 4CE3 27A3 4197 43CF 33C0 58D4 3327 2869 7686 6CDA 2557 2268 31C8 2D62 6A1A 45EB 7431 7C94 5D9C 5C0A 0B94 4720 3AB4 558D 5FF6 4A32 3528 6B64 2DBA
(Hex.)
Q
0E64 5CA3 3BD2 7ED5 2658 115C 1620 1CBE 6A80 6DE0 75D8 7513 0D51 420E 5103 27CF 3213 4B5F 2758 3B57 6C64 02D0 7467 6BF8 0107 609E 40E7 4F9A 621C 4CD5 3940 6A0F 7038 6204 5849 09A7 62DD 3BFE 454B 3163 7FDA 4AB2 41E6 2A23 47E0 4F47 0791 462B 1D0E 328A
SEP 2009
B-11
continued
Pilot PN
501 502 503 504 505 506 507 508 509 510 511
I
14301 23380 11338 2995 23390 14473 6530 20452 12226 1058 12026
(Dec.)
14Chip Delay Q
19272 29989 8526 18139 3247 28919 7292 20740 27994 2224 6827
I
37DD 5B54 2C4A 0BB3 5B5E 3889 1982 4FE4 2FC2 0422 2EFA
(Hex.)
Q
4B48 7525 214E 46DB 0CAF 70F7 1C7C 5104 6D5A 08B0 1AAB
B-12
SEP 2009
Appendix C: FRU Optimization/ATP Test Matrix

Appendix Content
C
FRU Optimization/ATP Test Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Usage & Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detailed Optimization/ATP Test Matrix . . . . . . . . . . . . . . . . . . . . . . . . C-1 C-1 C-2
SEP 2009
Table of Contents
continued
Notes
SEP 2009
FRU Optimization/ATP Test Matrix FRU Optimization/ATP Test Matrix

Usage & Background
Periodic maintenance of a site may also may mandate reoptimization of specific portions of the site. An outline of some basic guidelines is included in the following tables. NOTE Reoptimization steps listed for any assembly detailed in the tables below must be performed anytime an RF cable associated with it is replaced.
BTS Frame Table C-1: When RF Optimization Is required on the BTS Item Replaced CCCP Shelf Optimize All sector TX and RX paths to all Combined CDMA Channel Processor (CCCP) shelves. The three or six affected sector RX paths for the CCCP shelf in the BTS frames. RX and TX paths of the affected CCCP shelf / BBX board. All RX and TX paths of the affected CDMA carrier. The affected sector TX path. The affected sector TX path. The affected sector TX path.
Multicoupler/ Preselector Card BBX board CIO Card Any LPA Module LPA Backplane LPA Filter Ancillary Frame Item Replaced Directional Coupler Site filter
Optimize All affected sector RX and TX paths to all BTS frame shelves. All affected RX sector paths in all shelves in all BTS frames.
SEP 2009
C-1
FRU Optimization/ATP Test Matrix
continued
Inter-frame Cabling Optimization must be performed after the replacement of any RF cabling between BTS frames. Table C-2: When to Optimize Interframe Cabling Item Replaced Optimize The affected sector/antenna RX paths. The affected sector/antenna TX paths. Ancillary frame to BTS frame (RX) cables BTS frame to ancillary frame (TX) cables
Detailed Optimization/ATP Test Matrix
Table C-3 outlines in more detail the tests that would need to be performed if one of the BTS components were to fail and be replaced. It is also assumed that all modules are placed OOSROM via the LMF until full redundancy of all applicable modules is implemented. The following guidelines should also be noted when using this table. IMPORTANT
Not every procedure required to bring the site back on line is indicated in Table C-3. It is meant to be used as a guideline ONLY. The table assumes that the user is familiar enough with the BTS Optimization/ATP procedure to understand which test equipment set ups, calibrations, and BTS site preparation will be required before performing the Table # procedures referenced.
Various passive BTS components (such as the TX and RX directional couplers, Preselector IO, CIO; etc.) only call for a TX or RX calibration audit to be performed in lieu of a full path calibration. If the RX or TX path calibration audit fails, the entire RF path calibration will need to be repeated. If the RF path calibration fails, further troubleshooting is warranted. Whenever any CCCP BACKPLANE is replaced, it is assumed that only power to the CCCP shelf being replaced is turned off via the breaker supplying that shelf. Whenever any DISTRIBUTION BACKPLANE is replaced it is assumed that the power to the entire RFM frame is removed and the Preselector I/O is replaced. The modem frame should be brought up as if it were a new installation.
C-2 1X SC4812T CLPA BTS Optimization/ATP SEP 2009
continued
NOTE If any significant change in signal level results from any component being replaced in the RX or TX signal flow paths, it would be identified by rerunning the RX and TX calibration audit command. When the CIO is replaced, the CCCP shelf remains powered up. The BBX boards may need to be removed, then reinstalled into their original slots, and redownloaded (code and BLO data). RX and TX calibration audits should then be performed.
SEP 2009
C-3
continued
Table C-3: SC 4812T CLPA BTS Optimization and ATP Test Matrix
Trunking Module/Backplane
Directional Coupler (RX)
Directional Coupler (TX)
LFR/HSO/MSO/HSOX
CCCP Backplane
Power Amplifier
RX Cables
RX Filter
BBX
Doc Tbl #
TX Cables
MPC/EMPC
MCC
CSM
GPS
Description
Table 3-11 Ping the Processors Table 3-14 Download CSMs Table 3-14 Download MCCs Table 3-14 Download BBXs Table 3-16 Enable CSMs Table 3-17 Enable MCCs Table 3-20 GPS Initialization/Verification Table 3-20 HSO/MSO/HSOX Initialization/Verification Table 3-21 LFR Initialization/Verification Table 3-46 TX Path Calibration Audit Table 3-47 Download Offsets to BBX Table 4-1 Spectral Purity TX Mask ATP Table 4-1 Waveform Quality (rho) ATP Table 4-1 Pilot Time Offset ATP Table 4-1 Code Domain Power / Noise Floor Table 4-1 FER Test Table 4-3 RSSI Test 4 4 4 4 4 4 4 4 4 4 4 4 5 5 5 5 5 5 4
CIO
D D D D D D D D D D D D D 1 1 4 1 4 1 4 * 1 4 * 1 4 * * D D D D D D D D D D D D
* 3 6 3 3 3 * * * * * * * * * * * * * * * * * 6 6 * * * * * * * * *
1 4 7 7 7 7 2 2 2 5 7 7 7 7 2 2 2 5 7 7 7 7
C-4
Switch Card
GLI
SEP 2009
LPA Combiner/Filter 2:1
continued
Table C-3: SC 4812T CLPA BTS Optimization and ATP Test Matrix
Trunking Module/Backplane
Directional Coupler (RX)
Directional Coupler (TX)
LFR/HSO/MSO/HSOX
CCCP Backplane
Power Amplifier
RX Cables
TX Cables
MPC/EMPC
Switch Card
BBX
Doc Tbl #
RX Filter
MCC
CSM
GPS
Description
OPTIMIZATION AND TEST LEGEND:

D *
1 2 3 4 5 6 7
Required Perform if necessary for additional fault isolation, repair assurance, or site certification. Perform on all carrier and sector TX paths to the CCCP cage. Perform on all carrier and sector RX paths to the CCCP cage. Perform on all primary and redundant TX paths of the affected carrier. Perform on the affected carrier and sector TX paths. (BBXR replacement affects all carrier and sector TX paths.) Perform on the affected carrier and sector RX paths. (BBXR replacement affects all carrier and sector RX paths.) Perform with redundant BBX for all sectors on all carriers. Verify performance by performing on one sector of one carrier only.
SEP 2009
CIO
GLI
C-5

Notes
continued
C-6
SEP 2009
Appendix D: BBX Gain Set Point vs BTS Output

Appendix Content
BBX Gain Set Point vs. BTS Output Considerations . . . . . . . . . . . . . . . . . . . . Usage & Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D-1 D-1
SEP 2009
Table of Contents
continued
Notes
SEP 2009
BBX Gain Set Point vs. BTS Output Considerations BBX Gain Set Point vs. BTS Output Considerations
Usage & Background
Table 3-22 outlines the relationship between the total of all code domain channel element gain settings (digital root sum of the squares) and the BBX Gain Set Point between 33.0 dBm and 44.0 dBm. The resultant RF output (as measured at the top of the BTS in dBm) is shown in the table. The table assumes that the BBX Bay Level Offset (BLO) values have been calculated. As an illustration, consider a BBX keyed up to produce a CDMA carrier with only the Pilot channel (no MCCs forward link enabled). Pilot gain is set to 262. In this case, the BBX Gain Set Point is shown to correlate exactly to the actual RF output anywhere in the 33 to 44 dBm output range. (This is the level used to calibrate the BTS). Table D-1: BBX Gain Set Point vs. Actual BTS Output (in dBm)
dBm Gainb
44
43
42
41
40 44 43.8 43.6
39 43.9 43.8 43.6 43.4 43.3 43.1 43 42.8 42.6
38 44 43.9 43.8 43.6 43.5 43.4 43.2 43.1 42.9 42.8 42.6 42.4 42.3 42.1 42 41.8 41.6
37 43.3 43.2 43 42.9 42.8 42.6 42.5 42.4 42.2 42.1 41.9 41.8 41.6 41.4 41.3 41.1 41 40.8 40.6
36 42.3 42.2 42 41.9 41.8 41.6 41.5 41.4 41.2 41.1 40.9 40.8 40.6 40.4 40.3 40.1 40 39.8 39.6
35 41.3 41.2 41 40.9 40.8 40.6 40.5 40.4 40.2 40.1 39.9 39.8 39.6 39.4 39.3 39.1 39 38.8 38.6
34 40.3 40.2 40 39.9 39.8 39.6 39.5 39.4 39.2 39.1 38.9 38.8 38.6 38.4 38.3 38.1 38 37.8 37.6
33 39.3 39.2 39 38.9 38.8 38.6 38.5 38.4 38.2 38.1 37.9 37.8 37.6 37.4 37.3 37.1 37 36.8 36.6
541 533 525 517 509 501 493 485 477 469 461 453 445 437 429 421 413 405 397

SEP 2009 1X SC4812T CLPA BTS Optimization/ATP D-1
BBX Gain Set Point vs. BTS Output Considerations

Table D-1: BBX Gain Set Point vs. Actual BTS Output (in dBm)
dBm Gainb
continued
44 44 43.7 43.4 43.2 42.9 42.6 42.2
43 44 43.8 43.5 43.3 43 42.7 42.4 42.2 41.9 41.6 41.2
42 43.9 43.7 43.5 43.2 43 42.8 42.5 42.3 42 41.7 41.4 41.2 40.9 40.6 40.2
41 43.9 43.7 43.5 43.3 43.1 42.9 42.7 42.5 42.2 42 41.8 41.5 41.3 41 40.7 40.4 40.2 39.9 39.6 39.2
40 43.4 43.3 43.1 42.9 42.7 42.5 42.3 42.1 41.9 41.7 41.5 41.2 41 40.8 40.5 40.3 40 39.7 39.4 39.2 38.9 38.6 38.2
39 42.4 42.3 42.1 41.9 41.7 41.5 41.3 41.1 40.9 40.7 40.5 40.2 40 39.8 39.5 39.3 39 38.7 38.4 38.2 37.9 37.6 37.2
38 41.4 41.3 41.1 40.9 40.7 40.5 40.3 40.1 39.9 39.7 39.5 39.2 39 38.8 38.5 38.3 38 37.7 37.4 37.2 36.9 36.6 36.2
37 40.4 40.3 40.1 39.9 39.7 39.5 39.3 39.1 38.9 38.7 38.5 38.2 38 37.8 37.5 37.3 37 36.7 36.4 36.2 35.9 35.6 35.2
36 39.4 39.3 39.1 38.9 38.7 38.5 38.3 38.1 37.9 37.7 37.5 37.2 37 36.8 36.5 36.3 36 35.7 35.4 35.2 34.9 34.6 34.2
35 38.4 38.3 38.1 37.9 37.7 37.5 37.3 37.1 36.9 36.7 36.5 36.2 36 35.8 35.5 35.3 35 34.7 34.4 34.2 33.9 33.6 33.2
34 37.4 37.3 37.1 36.9 36.7 36.5 36.3 36.1 35.9 35.7 35.5 35.2 35 34.8 34.5 34.3 34 33.7 33.4 33.2
33 36.4 36.3 36.1 35.9 35.7 35.5 35.3 35.1 34.9 34.7 34.5 34.2 34 33.8 33.5 33.3 33
389 381 374 366 358 350 342 334 326 318 310 302 294 286 278 270 262 254 246 238 230 222 214
D-2
SEP 2009
Appendix E: CDMA Operating Frequency

Appendix Content
CDMA Operating Frequency Programming Information . . . . . . . . . . . . . . . . . 1900 MHz PCS Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating 1900 MHz Center Frequencies . . . . . . . . . . . . . . . . . . . . . . 800 MHz CDMA Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating 800 MHz Center Frequencies . . . . . . . . . . . . . . . . . . . . . . .
E-1 E-2 E-3 E-5 E-5
SEP 2009
Table of Contents
continued
Notes
SEP 2009
CDMA Operating Frequency Programming Information CDMA Operating Frequency Programming Information
Programming of each of the BTS BBX synthesizers is performed by the BTS GLI cards over the Concentration Highway Interface (CHI) bus. This programming data determines the transmit and receive operating frequencies (channels) for each BBX.
SEP 2009
E-1
1900 MHz PCS Channels 1900 MHz PCS Channels

Figure E-1 shows the valid channels for the North American PCS 1900 MHz frequency spectrum. There are 10 CDMA wireline or nonwireline band channels used in a CDMA system (unique per customer operating system). Figure E-1: North America PCS Frequency Spectrum (CDMA Allocation)
CHANNEL 25
FREQ (MHz) RX TX 1851.25 1931.25
275
425

D B
1863.75
1943.75
1871.25
1951.25
675
925

E F C
1883.75
1963.75
1896.25
1976.25
1175
1908.75
1988.75
FW004
E-2
SEP 2009
1900 MHz PCS Channels

Calculating 1900 MHz Center Frequencies
continued
Table E-1 shows selected 1900 MHz CDMA candidate operating channels, listed in both decimal and hexadecimal, and the corresponding transmit, and receive frequencies. Center frequencies (in MHz) for channels not shown in the table may be calculated as follows:
S TX = 1930 + 0.05 * Channel# S RX = TX 80
Example: Channel 262 TX = 1930 + 0.05 * 262 = 1943.10 MHz Example: Channel 262 RX = 1943.10 50 = 1863.10 MHz
Actual frequencies used depend on customer CDMA system frequency plan. Each CDMA channel requires a 1.77 MHz frequency segment. The actual CDMA carrier is 1.23 MHz wide, with a 0.27 MHz guard band on both sides of the carrier. Minimum frequency separation required between any CDMA carrier and the nearest NAMPS/AMPS carrier is 900 kHz (center-to-center). Table E-1: 1900 MHz TX and RX Frequency vs. Channel
Channel Number Decimal Hex 25 0019 50 0032 75 004B 100 0064 125 007D 150 0096 175 00AF 200 00C8 225 00E1 250 00FA 275 0113 300 012C 325 0145 350 015E 375 0177 400 0190 425 01A9 450 01C2 475 01DB 500 01F4 525 020D 550 0226 SEP 2009 Transmit Frequency (MHz) Center Frequency 1931.25 1932.50 1933.75 1935.00 1936.25 1937.50 1938.75 1940.00 1941.25 1942.50 1943.75 1945.00 1946.25 1947.50 1948.75 1950.00 1951.25 1952.50 1953.75 1955.00 1956.25 1957.50 Receive Frequency (MHz) Center Frequency 1851.25 1852.50 1853.75 1855.00 1856.25 1857.50 1858.75 1860.00 1861.25 1862.50 1863.75 1865.00 1866.25 1867.50 1868.75 1870.00 1871.25 1872.50 1873.75 1875.00 1876.25 1877.50
table continued next page

1X SC4812T CLPA BTS Optimization/ATP E-3
1900 MHz PCS Channels
continued
Table E-1: 1900 MHz TX and RX Frequency vs. Channel

Channel Number Decimal Hex 575 023F 600 0258 625 0271 650 028A 675 02A3 700 02BC 725 02D5 750 02EE 775 0307 800 0320 825 0339 850 0352 875 036B 900 0384 925 039D 950 03B6 975 03CF 1000 03E8 1025 0401 1050 041A 1075 0433 1100 044C 1125 0465 1150 047E 1175 0497 Transmit Frequency (MHz) Center Frequency 1958.75 1960.00 1961.25 1962.50 1963.75 1965.00 1966.25 1967.50 1968.75 1970.00 1971.25 1972.50 1973.75 1975.00 1976.25 1977.50 1978.75 1980.00 1981.25 1982.50 1983.75 1985.00 1986.25 1987.50 1988.75 Receive Frequency (MHz) Center Frequency 1878.75 1880.00 1881.25 1882.50 1883.75 1885.00 1886.25 1887.50 1888.75 1890.00 1891.25 1892.50 1893.75 1895.00 1896.25 1897.50 1898.75 1900.00 1901.25 1902.50 1903.75 1905.00 1906.25 1807.50 1908.75
E-4
SEP 2009
800 MHz CDMA Channels 800 MHz CDMA Channels

Figure E-2 shows the valid channels for the North American cellular telephone frequency spectrum. There are 10 CDMA wireline or nonwireline band channels used in a CDMA system (unique per customer operating system).
Figure E-2: North American Cellular Telephone System Frequency Spectrum (CDMA Allocation).
869.040
870.000 870.030
879.990 880.020
889.980 890.010
891.480 891.510
TX FREQ (MHz)
824.040
825.000 825.030
834.990 835.020
844.980 845.010
846.480 846.510
RX FREQ (MHz)
1013
1023 1
CHANNEL

311 333 334 356 644 666 667 689 694 OVERALL NONWIRELINE (A) BANDS OVERALL WIRELINE (B) BANDS
991
716 717
739
777
CDMA NONWIRELINE (A) BAND
CDMA WIRELINE (B) BAND FW00402
Calculating 800 MHz Center Frequencies
Table E-2 shows selected 800 MHz CDMA candidate operating channels, listed in both decimal and hexadecimal, and the corresponding transmit, and receive frequencies. Center frequencies (in MHz) for channels not shown in the table may be calculated as follows:
S Channels 1777
TX = 870 + 0.03 * Channel# Example: Channel 262 TX = 870 + 0.03*262 = 877.86 MHz TX = 870 + 0.03 * (Channel# 1023) Example: Channel 1015 TX = 870 +0.03 *(1015 1023) = 869.76 MHz Example: Channel 262 RX = 877.86 45 = 832.86 MHz
E-5
S Channels 10131023
S RX = TX 45 MHz
SEP 2009
799
848.970
893.970
800 MHz CDMA Channels
continued
Table E-2: 800 MHz TX and RX Frequency vs. Channel Channel Number Decimal 1 25 50 75 100 125 150 175 200 225 250 275 300 325 350 375 400 425 450 475 500 525 550 575 600 625 650 675 700 725 750 775 Hex 0001 0019 0032 004B 0064 007D 0096 00AF 00C8 00E1 00FA 0113 012C 0145 015E 0177 0190 01A9 01C2 01DB 01F4 020D 0226 023F 0258 0271 028A 02A3 02BC 02D5 02EE 0307 Transmit Frequency (MHz) Center Frequency 870.0300 870.7500 871.5000 872.2500 873.0000 873.7500 874.5000 875.2500 876.0000 876.7500 877.5000 878.2500 879.0000 879.7500 880.5000 881.2500 882.0000 882.7500 883.5000 884.2500 885.0000 885.7500 886.5000 887.2500 888.0000 888.7500 889.5000 890.2500 891.0000 891.7500 892.5000 893.2500 Receive Frequency (MHz) Center Frequency 825.0300 825.7500 826.5000 827.2500 828.0000 828.7500 829.5000 830.2500 831.0000 831.7500 832.5000 833.2500 834.0000 834.7500 835.5000 836.2500 837.0000 837.7500 838.5000 839.2500 840.0000 840.7500 841.5000 842.2500 843.0000 843.7500 844.5000 845.2500 846.0000 846.7500 847.5000 848.2500 table continued next page
E-6
SEP 2009
continued
Table E-2: 800 MHz TX and RX Frequency vs. Channel Channel Number Decimal Hex Transmit Frequency (MHz) Center Frequency Receive Frequency (MHz) Center Frequency
NOTE
Channel numbers 778 through 1012 are not used. 1013 03F5 869.7000 1023 03FF 870.0000 824.7000 825.0000
SEP 2009
E-7
continued
Notes
E-8
SEP 2009
Appendix F: Test Equipment Preparation

Appendix Content
Test Equipment Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify and set GPIB address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating test sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cable calibration set-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Setup: Agilent E7495 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Agilent E7495A/B with the LMF . . . . . . . . . . . . . . . . . . . . . Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Sensor Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cable Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying and Setting GPIB Addresses: Advantest R3267 Spectrum Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying and Setting GPIB Addresses: Advantest R3465 Communications Test Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying and Setting GPIB Addresses: Advantest R3562 Signal Generator . . Verifying and Setting GPIB Addresses: Agilent 8935 Series E6380 Test Set . . Verifying and Setting GPIB Addresses: Agilent E4406A Transmitter Tester . . Verifying and Setting GPIB Addresses: Agilent E4418 Power Meter . . . . . . . . Verifying and Setting GPIB Addresses: Agilent E4438C Signal Generator . . . Verifying and Setting GPIB Addresses: Gigatronics 8541C Power Meter . . . . Verifying and Setting GPIB Addresses: RS232 GPIB Interface Box . . . . . . . . Test Equipment Interconnection: Advantest R3267 and R3562 . . . . . . . . . . . . . 10 MHz reference signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serial I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Equipment Interconnection: Agilent 8935 Series E6380 and E4438C . . . Agilent 8932/E4438C Test Equipment Interconnection . . . . . . . . . . . . Test Equipment Interconnection: Agilent E4406A and E4438C . . . . . . . . . . . . Test Equipment Calibration: Agilent E4406A Selfalignment . . . . . . . . . . . . . Test Equipment Calibration: Gigatronics 8542 Power Meter . . . . . . . . . . . . . . .
F-1 F-1 F-1 F-1 F-1 F-1 F-1 F-2 F-2 F-2 F-2 F-3 F-4 F-5 F-7 F-8 F-9 F-11 F-13 F-15 F-17 F-18 F-19 F-19 F-19 F-20 F-20 F-21 F-22 F-23
Table of Contents
continued
Cable Calibration with R3465 Test Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-24 F-24
SEP 2009
Test Equipment Preparation Test Equipment Preparation

Purpose
Test equipment preparation information includes verification and setting GPIB addresses, interunit cabling, and equipment calibration for items which are not calibrated with the LMF Calibrate Test Equipment function. Manual cable calibration procedures using the Advantest R3465 test set are also provided. This portion of the publication is organized according to the following for the listed CDMA test equipment supported by the LMF.
Test equipment setup
S Agilent E7495A/B test equipment setup

Verify and set GPIB address
S S S S S S S S S
Test equipment interconnection
Advantest R3267 spectrum analyzer Advantest R3465 analyzer Advantest R3562 signal generator Agilent 8935 series E6380 analyzer (formerly HP 8935) Agilent E4406A transmitter test set Agilent E4418 power meter Agilent E4438C signal generator Gigatronics 8541C power meter GPIB adapter
S Advantest R3267 spectrum analyzer and Advantest R3562 signal

generator generator generator
S Agilent 8935 analyzer (formerly HP 8935) and Agilent E4438C signal S Agilent E4406A transmitter test set and Agilent E4438C signal
Calibrating test sets
S Agilent E4406A Transmitter Tester Self-alignment (Calibration) S Gigatronics 8542 power meter (Calibration)
Cable calibration set-up
S Calibrating Test Cable Setup using Advantest R3465
SEP 2009
F-1
Test Equipment Setup: Agilent E7495 Test Equipment Setup: Agilent E7495
Initial Requirement
This test equipment requires a warm-up period of at least 30 minutes before BTS testing or calibration begins.
Using the Agilent E7495A/B with the LMF
The Agilent E7495 does not require the use of the 19MHz frequency reference; if connected, it will be ignored. The Even Sec SYNC connection is required. The Agilent E7495 signal generator is only calibrated down to 80dB. In order to achieve accurate FER testing, be sure the RX setup includes at least 40dB of attenuation. This will ensure the signal generator will output sufficient power to operate in the calibrated range. Set the IP Address in the test set as described in Table F-1. Table F-1: Set IP Address on Agilent E7495 test set n Step 1 Action Use the System Button > Controls > IPAdmin to set an IP address on the E7495A/B as 128.0.0.11, and Netmask to 255.255.255.128 . If the IP addressed was changed, reboot the E7495 For compatibility, change the LMF computer Network Interface Card (NIC) IP address to 128.0.0.48, subnetmask 255.255.255.128.
2 3
Connection
Connect the E7495 test set as described in the Test Equpment Connection to the LMF section of Chapter 3.
F-2
SEP 2009
Test Equipment Setup: Agilent E7495

Power Sensor Calibration
continued
Table F-2 describes the E7495 Power Sensor Calibration. Table F-2: E7495 Power Sensor Calibration n Step 1 2 Action Display the power meter screen. Zero the power meter. Make sure equipment is connected as shown in Figure F-1. Press the Zero softkey. Press the Continue softkey. Calibrate the power meter: Press Ref CF. Enter the reference cal factor, reading it off the label on the power sensor head. Press Calibrate. Connect the power sensor (see Figure F-2). Press Continue. Press Cal Factor. Enter the cal factor from the label on the power sensor head. Select a cal factor that is within the operating frequency of the BTS being calibrated.
F
Figure F-1: Agilent E7495 PrePower Sensor Calibration connection
Port 2 RF In
Serial 1 Sensor
Even Second Sync In
Port 1 RF Out / SWR
Serial 2
GPS Antenna
POWER SENSOR NOT CONNECTED
SEP 2009
F-3
Test Equipment Setup: Agilent E7495
continued
Figure F-2: Agilent E7495 Power Sensor Calibration connection

POWER SENSOR CONNECTED
Port 2 RF In
Serial 1 Sensor
Even Second Sync In
Port 1 RF Out / SWR
Serial 2
GPS Antenna
Cable Calibration
Follow the directions in the LMF application program to calibrate cables. Additional cable calibration details Calibrate the short cable (see Figure 3-27) and two 10 dB attenuators to establish a baseline and then calibrate the TX and RX setups. Because at least 40 dB of attenuation is needed when testing the FER, the setup for RX is the same as for TX.
F-4
SEP 2009
Verifying and Setting GPIB Addresses: Advantest R3267 Spectrum Analyzer Verifying and Setting GPIB Addresses: Advantest R3267 Spectrum Analyzer
Figure F-3: Setting Advantest R3267 GPIB Address
SOFTKEY LABLE DISPLAY AREA SOFTKEY BUTTONS
on
REMOTE LED LCL KEY
CONFIG KEY
KEYPAD
BS KEY
ENTR KEY
Refer to Figure F-3 when performing the following. Table F-3: Verify and Set/Change Advantest R3267 GPIB Address Step 1 2 Action If the REMOTE LED is lighted, press the LCL key. The LED extinguishes. Press the CONFIG key. The CONFIG softkey labels will appear in the softkey label display area of the instrument display. The current GPIB address will be displayed below the GPIB Address softkey label. table continued on next page
SEP 2009
F-5
Verifying and Setting GPIB Addresses: Advantest R3267 Spectrum Analyzer continued
Table F-3: Verify and Set/Change Advantest R3267 GPIB Address Step 3 Action If the current GPIB address is not set to 18, perform the following to change it: 1. Press the GPIB Address softkey. A GPIB Address entry window will open in the instrument display showing the current GPIB address. 2. Enter 18 on the keypad in the ENTRY section of the instrument front panel. Characters typed on the keypad will replace the address displayed in the GPIB Address entry window.
NOTE
To correct an entry, press the BS (backspace) key at the lower right of the keypad to delete one character at a time. 3. Press the ENTR key to the lower right of the keypad to enter the address. Result: The GPIB Address entry window closes. The new address is displayed in the bottom portion of the GPIB Address softkey label.
F-6
SEP 2009
Verifying and Setting GPIB Addresses: Advantest R3465 Communications Test Set Verifying and Setting GPIB Addresses: Advantest R3465 Communications Test Set
Figure F-4: R3465 Communications Test Set
REF UNLOCK
EVEN SEC/SYNC IN
CDMA TIME BASE IN
GPIB and others
Preset Shift LCL
BNC T
POWER OFF ON
Vernier Knob
REF FW00337
NOTE This procedure assumes that the test equipment is set up and ready for testing. Refer to Figure F-4 when performing the following. Table F-4: Verify and Set/Change Advantest R3465 Communications Test Set GPIB Address Step 1 Action To verify that the GPIB address is set correctly, perform the following procedure: Press SHIFT then PRESET. Press LCL. Press the GPIB and Others CRT menu key to view the current address. If the current GPIB address is not set to 18, perform the following to change it: Turn the vernier knob as required to select 18. Press the vernier knob to set the address. To return to normal operation, press Shift and Preset.
SEP 2009
F-7
Verifying and Setting GPIB Addresses: Advantest R3562 Signal Generator Verifying and Setting GPIB Addresses: Advantest R3562 Signal Generator
Set the GPIB ADDRESS switch on the rear of the Advantest R3562 signal generator to address 1 as shown in Figure F-5. Figure F-5: Advantest R3562 GPIB Address Switch Setting
GPIB Address set to 1
GPIP ADDRESS
5 4 3 2 1
1 2 3 4 5 6 7 8
1 0
F-8
SEP 2009
Verifying and Setting GPIB Addresses: Agilent 8935 Series E6380 Test Set Verifying and Setting GPIB Addresses: Agilent 8935 Series E6380 Test Set
Figure F-6: Agilent 8935 Series E6380 Test Set Verify and Set/Change GPIB Address
Preset
Local
Inst Config
Shift
Cursor Control
FW00885
NOTE This procedure assumes that the test equipment is set up and ready for testing. Follow Refer to Figure F-6 when performing the following. Table F-5: Verify and Set/Change Agilent 8935 Series E6380 Test Set GPIB Address Step 1 Action
NOTE
The HP I/O configuration MUST be set to Talk & Listen, or NO device on the GPIB bus will be accessible. (Consult test equipment manufacturers documentation for additional information as required.) To verify that the GPIB addresses are set correctly, press Shift and LOCAL on the 8935. The current HPIB address is displayed at the top of the screen.
NOTE
HPIB is the same as GPIB. table continued on next page
SEP 2009
F-9
Verifying and Setting GPIB Addresses: Agilent 8935 Series E6380 Test Set continued
Table F-5: Verify and Set/Change Agilent 8935 Series E6380 Test Set GPIB Address Step 2 Action If the current GPIB address is not set to 18, perform the following to change it: Press Shift and Inst Config. Turn the Cursor Control knob to move the cursor to the HPIB Adrs field. Press the Cursor Control knob to select the field. Turn the Cursor Control knob as required to change the address to 18. Press the Cursor Control knob to set the address. Press Preset to return to normal operation.
F-10
SEP 2009
Verifying and Setting GPIB Addresses: Agilent E4406A Transmitter Tester Verifying and Setting GPIB Addresses: Agilent E4406A Transmitter Tester
Figure F-7: Agilent E4406A Transmitter Tester Verify and Set/Change GPIB Address
Active Function Area Softkey Label Display Area System Key
Bk Sp Key
Enter Key Softkey Buttons Data Entry Keypad
Refer to Figure F-7 when performing the following. Table F-6: Verify and Set/Change Agilent E4406A Transmitter Tester GPIB Address Step 1 Action In the SYSTEM section of the instrument front panel, press the System key. Result: The softkey labels displayed on the right side of the instrument screen will change. 2 Press the Config I/O softkey button to the right of the instrument screen. Result: The softkey labels will change. The current instrument GPIB address will be displayed below the GPIB Address softkey label. table continued on next page
SEP 2009
F-11
Verifying and Setting GPIB Addresses: Agilent E4406A Transmitter Tester continued
Table F-6: Verify and Set/Change Agilent E4406A Transmitter Tester GPIB Address Step 3 Action If the current GPIB address is not set to 18, perform the following to change it: 1. Press the GPIB Address softkey button. In the onscreen Active Function Area, GPIB Address will be displayed followed by the current GPIB address. 2. On the front panel Data Entry keypad, enter the communications system analyzer GPIB address of 18. Result: The GPIB Address label will change to Enter. Digits entered with the keypad will replace the current GPIB address in the display.
NOTE
To correct an entry, press the Bk Sp key at the upper right of the keypad to delete one character at a time. 3. Press the Enter softkey button or the keypad Enter key to set the new GPIB address. Result: The Config I/O softkey labels will reappear. The new GPIB address will be displayed under the GPIB Address softkey label.
F-12
SEP 2009
Verifying and Setting GPIB Addresses: Agilent E4418 Power Meter Verifying and Setting GPIB Addresses: Agilent E4418 Power Meter
Figure F-8: Agilent E4418B Power Meter Verify and Set/Change GPIB Address
PRESET/ LOCAL STATUS REPORTING LINE SOFTKEY LABEL AREA SOFTKEY MENU TITLE ARROW KEYS LEFT DOWN UP RIGHT
SYSTEM/ INPUTS
SOFTKEY MENU PAGE NUMBER
ticdma05962.eps
Refer to Figure F-8 when performing the following. Table F-7: Verify and Set/Change Agilent E4418 Power Meter GPIB Address Step 4 Action If RMT (remote operation) is displayed on the left end of the instrument screen status reporting line, press the Preset/Local front panel button. The status line entry will change to LCL (local or front panel operation). On the instrument front panel, press the System/Inputs key. The softkey labels displayed on the right side of the instrument screen will change. Press the Remote Interface > Configure Interface > GPIB softkeys to the right of the instrument screen. The softkey labels will change. The current instrument GPIB address will be displayed below the GPIB Addr softkey label. If the current GPIB address is set to 13, skip to step 11. If the current GPIB address is not set to 13, press the GPIB Addr softkey. A popup window will appear and display the current GPIB address. Modify the GPIB address in the popup as necessary using the following front panel keys to perform the indicated functions:
5 6
7 8 9
S Up and down arrow keys to change the digit on which the cursor is currently located S Left and right arrow keys to move the cursor to other digits
SEP 2009 1X SC4812T CLPA BTS Optimization/ATP F-13
Verifying and Setting GPIB Addresses: Agilent E4418 Power Meter

continued Table F-7: Verify and Set/Change Agilent E4418 Power Meter GPIB Address Step 10 11 Action When the GPIB address is correct, press the Enter softkey. Return the instrument to the required setup configuration for testing.
F-14
SEP 2009
Verifying and Setting GPIB Addresses: Agilent E4438C Signal Generator Verifying and Setting GPIB Addresses: Agilent E4438C Signal Generator
Figure F-9: Agilent E4438C Verify and Set/Change GPIB Address
Active Entry Area Softkey Label Display Area Utility Key
Return Key
Softkey Buttons
Numeric Keypad
Backspace Key
ticdma06850.eps
F
Refer to Figure F-9 when performing the following. Table F-8: Verify and Change Agilent E4438C Signal Generator GPIB Address Step 1 2 Action In the MENUS section of the instrument front panel, press the Utility key. Result: The softkey labels displayed on the right side of the instrument screen will change. Press the GPIB/RS232/LAN softkey button to the right of the instrument screen. Result:
S The softkey labels will change. S The current instrument GPIB address will be displayed below the GPIB Address softkey label.
3 4 If the current GPIB address is set to 1, skip to step 7. If the current GPIB address is not set to 1, press the GPIB Address softkey button. Result:
S The GPIB Address label and current GPIB address will change to boldface. S In the onscreen Active Entry Area, Address: will be displayed followed by the current GPIB
address. table continued on next page
SEP 2009 1X SC4812T CLPA BTS Optimization/ATP F-15
Verifying and Setting GPIB Addresses: Agilent E4438C Signal Generator continued
Table F-8: Verify and Change Agilent E4438C Signal Generator GPIB Address Step 5 Action On the front panel Numeric keypad, enter the signal generator GPIB address of 1. Result:
S The GPIB Address label will change to Enter. S Digits entered with the keypad will replace the current GPIB address in the Active Entry display. NOTE
To correct an entry, press the backspace key at the lower right of the keypad to delete one character at a time. 6 7 Press the Enter softkey button to set the new GPIB address. Result: The new GPIB address will be displayed under the GPIB Address softkey label. Exit from the Utility menus by pressing the Return key several times.
F-16
SEP 2009
Verifying and Setting GPIB Addresses: Gigatronics 8541C Power Meter Verifying and Setting GPIB Addresses: Gigatronics 8541C Power Meter
Figure F-10: Gigatronics 8541C Power Meter Detail
MENU
ENTER
ARROW KEYS
REF FW00564
Refer to Figure F-10 when performing the following. NOTE This procedure assumes that the test equipment is set up and ready for testing.
Table F-9: Verify and Set/Change Gigatronics 8541C Power Meter GPIB Address Step 1 Action
! CAUTION
Do not connect/disconnect the power meter sensor cable with AC power applied to the meter. Disconnection could result in destruction of the sensing element or miscalibration. Press MENU.
2 3 4
Use the b arrow key to select CONFIG MENU and press ENTER. Use the b arrow key to select GPIB and press ENTER. The current Mode and GPIB Address are displayed. If the Mode is not set to 8541C, perform the following to change it: Use the a arrow keys as required to select MODE. Use the by arrow keys as required to set MODE to 8541C. If the GPIB address is not set to 13, perform the following to change it: Use the arrow key to select ADDRESS. Use the by arrow keys as required to set the GPIB address to 13. Press ENTER to return to normal operation.
SEP 2009
F-17
Verifying and Setting GPIB Addresses: RS232 GPIB Interface Box Verifying and Setting GPIB Addresses: RS232 GPIB Interface Box
Be sure that the RS232 GPIB interface box DIP switches are set as shown in Figure F-11. Figure F-11: Verify and Set/Change RS232 GPIB Interface Box GPIB Address
DIP SWITCH SETTINGS
S MODE DATA FORMAT
BAUD RATE
ON
GPIB ADRS
G MODE
RS232GPIB INTERFACE BOX

F-18
SEP 2009
Test Equipment Interconnection: Advantest R3267 and R3562 Test Equipment Interconnection: Advantest R3267 and R3562
To provide proper operation during testing when both units are required, the R3257 spectrum analyzer must be interconnected with the R3562 signal generator as follows:
10 MHz reference signal
Connect a BNC (M)BNC (M) cable between the R3562 SYNTHE REF IN connector and the R3267 10 MHz OUT connector as shown in Figure F-12.
Serial I/O
Using the Advantest cable provided, connect the R3267 SERIAL I/O connector to the R3562 SERIAL I/O connector as shown in Figure F-12. Figure F-12: Advantest 10 MHz Reference and Serial I/O Connections
R3267 10 MHZ OUT R3267 SERIAL I/O
TO GPIB BOX
R3562 SYNTHE REF IN
TO GPIB BOX
R3562 SERIAL I/O
TDME00101
SEP 2009
F-19
Test Equipment Interconnection: Agilent 8935 Series E6380 and
E4438C E4438C
Test Equipment Interconnection: Agilent 8935 Series E6380 and

Agilent 8932/E4438C Test Equipment Interconnection
To perform FER testing on a 1X BTS with the Agilent 8935, a 1Xcapable signal generator, such as the Agilent E4438C, must be used in conjunction with the CDMA base station test set. For proper operation, the test equipment items must be interconnected as follows: 10 MHz reference signal Connect a BNC (M)BNC (M) cable from the 8935 10 MHz REF OUT connector to the E4438C 10MHz IN connector as shown in Figure F-13 Even second pulse reference Refer to Figure F-13, and connect a BNC T connector to the 8935 EVEN SEC SYNC IN connector. Connect a BNC (M)BNC (M) cable from one side of the BNC T to the E4438C PATT TRIG IN connector. Connect the other side of the BNC T to the CSM board SYNC MONITOR connector using a BNC (M)BNC (M) cable. Figure F-13: Agilent 8935/E4438C 10MHz Reference and Even Second Tick Connections
E4438C PATT TRIG IN
E4438C 10 MHz IN

8935 EVEN SECOND SYNC IN WITH BNC T
TO GPIB
8935 10 MHz REF OUT
TO CSM BOARD SYNCH MONITOR (EVEN SEC TICK) OR UBS SSI TREF OUT
TDME00201
F-20
SEP 2009
Test Equipment Interconnection: Agilent E4406A and E4438C Test Equipment Interconnection: Agilent E4406A and E4438C
To provide proper operation during testing when both units are required, the 10 MHz reference signal from the E4406A transmitter test set must be provided to the E4438C signal generator. Connect a BNC (M)BNC (M) cable from the E4406A 10 MHz OUT (SWITCHED) connector to the E4438C 10MHz IN connector as shown in Figure F-14. Figure F-14: Agilent 10 MHz Reference Connections
E4438C 10 MHz IN TO GPIB BOX E4406A 10 MHz OUT (SWITCHED)
TDME00091
SEP 2009
F-21
Test Equipment Calibration: Agilent E4406A Selfalignment Test Equipment Calibration: Agilent E4406A Selfalignment
Refer to Figure F-15 when performing the following. Figure F-15: Agilent E4406A
Softkey Label Display Area System Key
Softkey Buttons
Table F-10: Agilent E4406A Selfalignment (Calibration) Step 1 Action In the SYSTEM section of the instrument front panel, press the System key. Result: The softkey labels displayed on the right side of the instrument screen will change. 2 Press the Alignments softkey button to the right of the instrument screen. Result: The softkey labels will change. 3 Press the Align All Now softkey button. Result: All other instrument functions will be suspended during the alignment. The display will change to show progress and results of the alignments performed. The alignment will take less than one minute.
F-22
SEP 2009
Test Equipment Calibration: Gigatronics 8542 Power Meter Test Equipment Calibration: Gigatronics 8542 Power Meter
Precise transmit output power calibration measurements are made using a bolometertype broadband power meter with a sensitive power sensor. Follow the steps in Table F-11 to enter information unique to the power sensor. Refer to Figure F-16 as necessary. Table F-11: Calibrate Gigatronics 8542 Power Meter Step 1 Action
! CAUTION
Do not connect/disconnect the power meter sensor cable with AC power applied to the meter. Disconnection could result in destruction of the sensing element or miscalibration. Make sure the power meter POWER pushbutton is OFF.
2 3
Connect the power sensor cable to the SENSOR input. Set the POWER pushbutton to ON.
NOTE
Allow the power meter and sensor to warm up and stabilize for a minimum of 60 minutes before performing the calibration procedure. 4 5 Connect the power sensor to the CALIBRATOR output connector. Press ZERO. Wait for the process to complete. Sensor factory calibration data is read to power meter during this process. When the zeroing process is complete, disconnect the power sensor from the CALIBRATOR output.
Figure F-16: Gigatronics 8541C Power Meter

CONNECT POWER SENSOR TO CALIBRATOR POWER REFERENCE WHEN CALIBRATING/ZEROING UNIT CONNECT POWER SENSOR WITH POWER METER TURNED OFF
AC POWER
GPIB CONNECTION
FRONT VIEW
REAR VIEW
FW00564
SEP 2009
F-23
Cable Calibration with R3465 Test Set Cable Calibration with R3465 Test Set
NOTE Warm-up BTS equipment for a minimum of 60 minutes prior to performing the BTS optimization procedure. This assures BTS site stability and contributes to optimization accuracy. (Time spent running initial power-up, hardware/firmware audit, and BTS download counts as warm-up time.) CAUTION If any piece of test equipment (i.e., test cable, RF adapter) has been replaced, re-calibration must be performed. Failure to do so could introduce measurement errors, resulting in incorrect measurements and degradation to system performance.. NOTE Calibration of the communications test set (or equivalent test equipment) must be performed at the site before calibrating the overall test set. Calibrate the test equipment after it has been allowed to warm-up and stabilize for a minimum of 60 minutes.
Prerequisites
Prior to performing this procedure, all actions for preparing the LMF, updating LMF files, and any other pre-calibration procedures identified in Chapter 3 must be completed. NOTE Be sure the GPIB Interface box is OFF for this procedure. Perform the following to calibrate the test cable setup using the Advantest R3465. Advantest R3465 manual test setup and calibration must be performed at both the TX and RX frequencies. Table F-12: Procedure for Calibrating Test Cable Setup Using Advantest R3465 Step Action
NOTE
This procedure can only be performed after test equipment has been allowed to warmup and stabilize for a minimum of 60 minutes. 1 Press the SHIFT and the PRESET keys located below the display. table continued on next page
F-24 1X SC4812T CLPA BTS Optimization/ATP SEP 2009
Cable Calibration with R3465 Test Set
continued
Table F-12: Procedure for Calibrating Test Cable Setup Using Advantest R3465 Step 2 3 4 5 Select the CDMA Sig CRT menu key. Select the Setup CRT menu key. Using the vernier knob and the cursor keys set the following parameters: Action Press the ADVANCE key in the MEASUREMENT area of the control panel.
NOTE
Fields not listed remain at default. Generator Mode: SIGNAL Link: FORWARD Level Unit: dBm CalCorrection: ON Level Offset: OFF 6 7 8 9 10 11 12 13 14 15 16 Select the return CRT menu key. Press FREQ key in the ENTRY area. Set the frequency to the desired value using the keypad entry keys. Verify that the Mod CRT menu key is highlighting OFF; if not, press the Mod key to toggle it OFF. Verify that the Output CRT menu key is highlighting OFF; if not, press the Output key to toggle it OFF. Press the LEVEL key in the ENTRY area. Set the LEVEL to 0 dBm using the key pad entry keys. Zero power meter. Next connect the power sensor directly to the RF OUT port on the R3561L CDMA Test Source Unit. Press the Output CRT menu key to toggle Output to ON. Record the power meter reading ________________________ Disconnect the power meter sensor from the R3561L RF OUT jack.
NOTE
The Power Meter sensor lower limit is 30 dBm. Thus, only components having losses < 30 dB should be measured using this method. For best accuracy, always rezero the power meter before connecting the power sensor to the component being calibrated. Then, after connecting the power sensor to the component, record the calibrated loss immediately. table continued on next page
SEP 2009
F-25
continued
Table F-12: Procedure for Calibrating Test Cable Setup Using Advantest R3465 Step 17 Action Disconnect all components in the the test setup and calibrate each one separately. Connect each component oneatatime between the RF OUT port and the power sensor (see Figure F-17, Setups A, B, and C). Record the calibrated loss value displayed on the power meter for each connection. Example: (A) 1st Test Cable = 0.5 dB (B) 2nd Test Cable = 1.4 dB (C) 20 dB Attenuator = 20.1 dB (D) 30 dB Directional Coupler = 29.8 dB Press the Output CRT menu key to toggle Output OFF. Calculate the total test setup loss by adding up all the individual losses: Example: Total test setup loss = 0.5 + 1.4 + 20.1 + 29.8 = 51.8 dB This calculated value will be used in the next series of tests. Press the FREQ key in the ENTRY area. Using the keypad entry keys, set the test frequency to the RX frequency. Repeat steps 9 through 19 for the RX frequency. Refer to Table 3-41 for assistance in manually setting the cable loss values into the LMF.
18 19
20 21 22 23
F-26
SEP 2009

Figure F-17: Cable Calibration using Advantest R3465
RF OUT
continued
POWER SENSOR
(A) & (B)
POWER SENSOR
F
(C)
20 DB / 2 WATT ATTENUATOR
POWER SENSOR
(C)
POWER SENSOR
(D)
100 W NONRADIATING RF LOAD 30 DB DIRECTIONAL COUPLER
FW00320
SEP 2009
F-27

Notes
continued
F-28
SEP 2009
Appendix G: VSWR
Appendix Content
Transmit & Receive Antenna VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment Setup and Measurement Procedure Advantest R3465 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
G-1 G-1 G-1 G-1
SEP 2009
Table of Contents
continued
Notes
SEP 2009
Transmit & Receive Antenna VSWR Transmit & Receive Antenna VSWR
Purpose
The following procedures will verify that the Voltage Standing Wave Ratio (VSWR) of all antennas and associated feed lines fall within acceptable limits. The tests will be performed on all antennas in a sequential manner (i.e., ANT 1, then ANT 2) until all antennas/feedlines have been verified. These procedures should be performed periodically by measuring each respective antennas VSWR (reflected power) to verify that the antenna system is within acceptable limits. This will ensure continued peak system performance. The antenna VSWR will be calculated at the CDMA carrier frequency assigned to each antenna. Record and verify that they meet the test specification of less than or equal to 1.5:1. NOTE Motorola recommends that the installer be familiar with the following procedure in its entirety before beginning the actual procedure. Ensure that the entire site is currently not in service. This test is used to test RX antennas by substituting RX frequencies for TX frequencies. Study the site engineering documents and perform the following tests only after first verifying that the RF cabling configuration required to interconnect the BTS frames and antennas meet requirements called out in the BTS Installation Manual.
Test equipment
The following pieces of test equipment will be required to perform this test: S LMF S Directional coupler S Communications test set WARNING Prior to performing antenna tests, insure that no CDMA BBX channels are keyed. Failure to do so could result in personal injury or serious equipment damage.
Equipment Setup and Measurement Procedure Advantest R3465
Follow the procedure in Table G-1 to set up test equipment required to measure and calculate the VSWR for each antenna.
SEP 2009 1X SC4812T CLPA BTS Optimization/ATP G-1
Transmit & Receive Antenna VSWR
continued
Table G-1: VSWR Measurement Procedure Advantest R3465 Test Set Step 1 2 Action ADVANTEST If you have not already done so, refer to the procedure in Table 3-4 to set up test equipment and interface the LMF computer to the BTS. For manual VSWR testing using external directional coupler, refer to Figure G-1 and perform the following on the first sector to be measured: 1. Connect the communications test set RF OUT port to the input port of the directional coupler. 2. Connect the INPUT port of the communication test set to the forward port on the directional coupler. Terminate the forward port with a 50 Ohm load. 3. Connect the RF short to the directional coupler output port. Perform the following to instruct the calibrated test set to generate a CDMA RF carrier (RVL call) with allzero longcode at the assigned RX frequency at 10 dBm: 1. Push the ADVANCE Measurement key. 2. Push the CDMA Sig CRT menu key. 3. Push the FREQ Entry key, and then perform one of the following depending on the frequency band of the BTS being tested: 1900 MHz systems: Set RF Gen Freq to center frequency of actual CDMA carrier between 19301990 MHz for TX and 18501910 MHz for RX. 800 MHz systems: Set RF Gen Freq to center frequency of actual CDMA carrier between 869894 MHz for TX and 824849 MHz for RX. 1700 MHz systems: Set RF Gen Freq to center frequency of actual CDMA carrier between 18401870 MHz for TX and 17501780 MHz for RX. 4. Push the LEVEL Entry key; set to 0 dBm (by entering 0 and pushing the dBm key). 5. Verify that ON is active in the Output CRT menu key. 6. Verify that OFF is active in the Mod CRT menu key. 7. Push the CW Measurement key. 8. Push the Transient Measurement key, and then perform the following: Push the more 1/2 CRT menu key. Set Preselect CRT menu key to 3.0G. 9. Push the Transient Measurement key, and then perform the following: Push the Tx Power CRT menu key. Push the LEVEL entry key (set to 7 dBm by entering 7 and pushing the the dBm key). Set Avg Times CRT menu key to ON. Set to 20 (by entering 20 and pushing the Hz ENTER key). 10.Push the REPEAT Start key to take the measurement. Record the Burst Power displayed on the communications analyzer and identify as PS for reference. Install the antenna feedline to the output port of the directional coupler. Perform the following to take the measurement for the antenna feedline:
4 5 6
S Push the Auto Level Set CRT menu key. S Push the REPEAT Start key to take the measurement.
G-2 1X SC4812T CLPA BTS Optimization/ATP SEP 2009
continued
Table G-1: VSWR Measurement Procedure Advantest R3465 Test Set Step 7 8 9 Action ADVANTEST Record the Burst Power displayed on the communications analyzer and identify as PA level for reference. Calculate and record the difference in dB between the measurements recorded in steps 4 and 7, above, and identify as RL(dB) level for reference. Calculate the VSWR per the equation shown to the right. Where: RL(dB) = PA(dBm) PS(dBm) PA = Power reflected from antenna PS = Power reflected from short A calculated value of 13.98 dB equates to VSWR of better than 1.5:1. Repeat steps 2 through 9 for all remaining TX sectors/antennas. Repeat steps 2 through 9 for all remaining RX sectors/antennas.
1 ) 10 VSWR + 1 * 10
RL 20 RL 20
10 11
Figure G-1: Manual VSWR Test Setup Using Advantest R3465

RF OUT
FEED LINE TO ANTENNA UNDER TEST
RF IN
RF SHORT
G
RVS (REFLECTED) PORT 30 DB DIRECTIONAL COUPLER INPUT PORT
OUTPUT PORT
FWD (INCIDENT) PORT 50OHM TERMINATED LOAD
FW00332
SEP 2009
G-3

Notes
continued
G-4
SEP 2009
Appendix H: Download ROM Code

Appendix Content
Download ROM Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download ROM Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H-1 H-1
SEP 2009
Table of Contents
continued
Notes
SEP 2009
Download ROM Code Download ROM Code

Download ROM Code
ROM code can be downloaded to a device that is in any state. After the download is started, the device being downloaded changes to OOS_ROM (blue) and remains OOS_ROM (blue). The same Rlevel RAM code must then be downloaded to the device. This procedure includes steps for both the ROM code download and the RAM code download. ROM code files cannot be selected automatically. The ROM code file must be selected manually. Follow the procedure in Table H-1 to download ROM code. Prerequisite
S ROM and RAM code files exist for the device to be downloaded.
CAUTION The Rlevel of the ROM code to be downloaded must be the same as the Rlevel of the ROM code for other devices in the BTS. Code must not be mixed in a BTS. This procedure should only be used to upgrade replacement devices for a BTS and it should not be used to upgrade all devices in a BTS. If a BTS is to be upgraded from one Rlevel to another, the optimization and ATP procedures must first be performed with the BTS in the original configuration. The upgrade should then be done by the OMCR.
Table H-1: Download ROM Code Step 1 Click on the device to be downloaded. Action
NOTE
More than one device of the same type can be selected for download by either clicking on each one to be downloaded or from the BTS menu bar Select pulldown menu, select the device item that applies. Where: device = the type of device to be loaded (BBX, CSM, GLI, MCC) 2 3 Click on the Device menu. Click on the Status menu item. A status report window appears. table continued on next page
SEP 2009 1X SC4812T CLPA BTS Optimization/ATP H-1
Download ROM Code
continued
Table H-1: Download ROM Code Step 4 Action Make a note of the number in the HW Bin Type column.
NOTE
HW Bin Type is the Hardware Binary Type for the device. This code is used as the last four digits in the filename of a devices binary ROM code file. Using this part of the filename, the ROM code file can be matched to the device in which it is to be loaded. 5 6 Click on the OK button to dismiss the status report window.
NOTE
ROM code is automatically selected for download from the <x>:\<lmf home directory>\version folder>\<code folder> specified by the NextLoad property. To check the value of the NextLoad property, click on Util>Examine>Display Nextload. A popup message will show the value of the NextLoad. Click on the Download Code Manual menu item. Result: A file selection window appears.
7 8 9
Doubleclick on the version folder that contains the desired ROM code file. Doubleclick on the Code folder. Result: A list of ROM and RAM code files is displayed.
! CAUTION
A ROM code file having the correct hardware binary type (HW Bin Type) needs to be chosen. The hardware binary type (last four digits in the file name) was determined in step 4. Unpredictable results can happen and the device may be damaged (may have to be replaced) if a ROM code file with wrong binary type is downloaded. Choose a ROM code file having the correct hardware binary type (HW Bin Type). The hardware binary type (last four digits in the file name) was determined in step 4.
10
Click on the ROM code file that matches the device type and HW Bin Type (e.g., bbx_rom.bin.0604 for a BBX having a HW Bin Type of 0604). Result: The file should be highlighted. Click on the Load button. A status report window displays the result of the download.
11
NOTE
If the ROM load failed for some devices, load them individually by clicking on one device, perform steps 6 through 11 for it, and repeat the process for each remaining device. 12 13 14 15 Click on the Ok button to close the status report window. Click on the Util menu. Select the Tools menu item. Click on the Update NextLoad>CDMA menu item. table continued on next page
H-2 1X SC4812T CLPA BTS Optimization/ATP SEP 2009
Download ROM Code
continued
Table H-1: Download ROM Code Step 16 17 18 19 20 21 Action Select the version number of the folder that was used for the ROM code download. Click on the Save button. Result: A popup message indicates that the NextLoad property has been updated. Click on the OK button to dismiss the popup message. Click on the device that was downloaded with ROM code. Click on the Device menu. Click on the Download Code menu item to download RAM code. Result: A status report window displays the result of the download.
NOTE
Data is automatically downloaded to GLI devices when the RAM code is downloaded. Use the Download Data procedure to download data to other device types after they have been upgraded. 22 Click on the Ok button to close the status report window. The downloaded device should be OOS_RAM (yellow) unless it is a GLI in which case it should be INS (green). Click on the device that was downloaded. Click on the Device menu. Click on the Status menu item. Result: A status report window displays the result of the query for each selected device. Verify that the status report window displays the correct ROM and RAM version numbers. Click on the Ok button to close the status report window.
23 24 25 26 27
SEP 2009
H-3
Download ROM Code
continued
Notes
H-4
SEP 2009
Appendix I: InService Calibration

Appendix Content
In Service Calibration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment Warm up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Delta Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Delta Calibration Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . Advantest R3465 Power Delta Calibration . . . . . . . . . . . . . . . . . . . . . . HP8935 Power Delta Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Agilent E4406A Power Delta Calibration . . . . . . . . . . . . . . . . . . . . . . . InService Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I-1 I-1 I-1 I-2 I-2 I-2 I-5 I-7 I-10 I-10
SEP 2009
Table of Contents
continued
Notes
SEP 2009
In Service Calibration Overview In Service Calibration Overview

Purpose
This procedure is a guide to expanding your system with multiple carriers while the system remains in service. This procedure also allows you to perform on site maintenance (replace defective boards and recalibrate) while the remainder of the site stays in service. Motorola recommends that you perform this procedure during a maintenance window. This procedure cannot be performed on BTSs with 4to1 combiners. The procedure can only be performed on one side of the BTS at one time. That is, LPAs 1, 2 ,3, 7, 8, 9 (feed antennas 1, 2, 3) can be calibrated while LPAs 6, 7, 8, 10, 11, 12 (feed antennas 4, 5, 6) remain in service and vice versa.
Equipment Warm up
CAUTION If any piece of test equipment (i.e., test cable, RF adapter) has been replaced, re-calibration must be performed. Failure to do so could introduce measurement errors, causing incorrect measurements and degradation to system performance.
NOTE Calibration of the communications test set (or equivalent test equipment) must be performed at the site before calibrating the overall test set. Calibrate the test equipment after it has been allowed to warm-up and stabilize for a minimum of 60 minutes.
SEP 2009
I-1
Power Delta Calibration Power Delta Calibration

Power Delta Calibration Introduction
The Inservice calibration procedure has several differences from a normal calibration procedure. One of these is the use of a spectrum analyzer instead of a power meter to measure power. Power meters are broadband measurement devices and cannot be used to measure power during Inservice Calibration since other carriers are operating. A spectrum analyzer can be used because it measures power at a given frequency. However, measuring power using a spectrum analyzer is less accurate than using a power meter. Therefore, you must compensate for the difference (delta) between the power meter and the spectrum analyzer.
Advantest R3465 Power Delta Calibration
Follow the procedure in Table I-1 to perform the Advantest R3465 Power Delta Calibration procedure. Table I-1: Advantest Power Delta Calibration Procedure Step Action
NOTE
Perform this procedure after test equipment has been allowed to warmup and stabilize for a minimum of 60 minutes. On the Advantest R3465: 1 2 3 4 5 6 7 8 9 Press the SHIFT and the PRESET keys located below the CRT display. Press the ADVANCE key in the Measurement area of the control panel. Press the CDMA Sig CRT menu key. Press the FREQ key in the Entry area of the control panel. Set the frequency to the desired value using the keypad entry keys. Press the LEVEL key in the Entry area of the control panel. Set the LEVEL to 0 dBm using the keypad entry keys. Verify the Mod CRT menu key is highlighting OFF, if not press the Mod key to toggle it OFF. Verify the Output CRT menu key is highlighting OFF. If not, press the Output key to toggle it OFF. Zero the Power Meter prior to connecting the power sensor to the RF cable from the signal generator.
On the HP 437 Power Meter:
10
NOTE
For best accuracy, always rezero the power meter before connecting the power sensor to the component being calibrated. table continued on next page
I-2 1X SC4812T CLPA BTS Optimization/ATP SEP 2009
Power Delta Calibration
continued
Table I-1: Advantest Power Delta Calibration Procedure Step 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 Action Connect the RF cable from the R3561L CDMA Test Source Unit RF OUT port to the power sensor (see Figure I-1). Press the Output CRT menu key to toggle the Output to ON. Record the Power Meter reading as result A ________________________. Press the Output CRT menu key to toggle the Output to OFF. Connect the RF cable from the R3561L CDMA Test Source Unit RF OUT port to the Spectrum Analyzer INPUT Port (see Figure I-2). Press the Output CRT menu key to change the Output to ON. Press the CW key in the Measurement area of the control panel. Press the LEVEL key in the Entry area of the control panel. Set the REF LEVEL to 10 dBm using the keypad entry keys. Press the dB/div CRT menu key. Press the 10 dB/div CRT menu key. Press the FREQ key in Entry area of the control panel. Set the frequency to the desired value using the keypad entry keys. Press the more 1/2 CRT menu key. Press the Preselector CRT menu key to highlight 3.0G. Press the FORMAT key in the Display Control area of the control panel. Press the TRACE CRT menu key. Press the AVG A CRT menu key. Set AVG to 20 using keypad entry keys. Press the return CRT menu key. Press the SPAN key in the Entry area of the control panel. Press the Zero Span CRT menu key. Press the BW key in the Entry area of the control panel. Press the RBW CRT menu key to highlight MNL. Set RBW to 30 kHz using keypad entry keys. Press the VBW CRT menu key to highlight MNL. Set VBW to 1 MHz using keypad entry keys. Press the Marker ON key in the Display Control area of the control panel. table continued on next page
SEP 2009 1X SC4812T CLPA BTS Optimization/ATP I-3
continued
Table I-1: Advantest Power Delta Calibration Procedure Step 39 40 Action Record the Marker Level reading as result B ________________________. Calculate the Power Calibration Delta value. The delta value is the power meter measurement minus the Advantest measurement. Delta = A B Example: Delta = 0.70 dBm (1.25 dBm) = 0.55 dBm Example: Delta = 0.26 dBm 0.55 dBm = 0.29 dBm These examples are included to show the mathematics and do not represent actual readings.
NOTE
Add this delta value to the TX Cable Loss value during InService Calibration (see Step 4 in Table I-4).
Figure I-1: Delta Calibration Setup R3561L to HP437B

ADVANTEST R3561L
RF OUT POWER SENSOR SHORT RF CABLE SENSOR
HP437B
FW00803
Figure I-2: Delta Calibration Setup R3561L to R3465

RF OUT
R3561L
SHORT RF CABLE
R3465
INPUT
FW00804
I-4
SEP 2009

HP8935 Power Delta Calibration
continued
Follow the procedure in Table I-2 to perform the HP8935 Power Delta Calibration procedure. Table I-2: HP8935 Power Delta Calibration Procedure Step Action
NOTE
Perform this procedure after test equipment has been allowed to warmup and stabilize for a minimum of 60 minutes. 1 2 Connect a short RF cable between the HP8935 Duplex Out port and the HP437B power sensor (see Figure I-3). Set the HP8935 signal source as follows: Measure mode to CDMA Gen Frequency to the CDMA Calibration target frequency CW RF Path to IQ Output Port to Dupl Data Source to Random Amplitude to 0 dBm Measure and record the power value reading on the HP437B Power Meter. Record the Power Meter reading as result A ________________________. Turn off the source HP8935 signal output, and disconnect the HP437B.
3 4 5
NOTE
Leave the settings on the source HP8935 for convenience in the following steps. 6 7 8 Connect the short RF cable between the source HP8935 Duplex Out port and the RFIN/OUT port (see Figure I-4). Ensure that the source HP8935 settings are the same as in Step 2. Set the measuring HP8935 as follows: Measure mode to CDMA Anl Frequency to the CDMA calibration target frequency Input Attenuation to 0 dB Input port to RFIN Gain to Auto Anl Dir to Fwd Turn on the source HP8935 signal output. Set the Chn Pwr Cal to Calibrate and select to calibrate. Measure and record the channel power reading on the measuring HP8935 as result B ________________________. table continued on next page
9 10 11
continued
Table I-2: HP8935 Power Delta Calibration Procedure Step 12 13 Action Turn off the source HP8935 signal output and disconnect the equipment. Calculate the Power Calibration Delta value. The delta value is the power meter measurement minus the Advantest measurement. Delta = A B Example: Delta = 0.70 dBm (1.25 dBm) = 0.55 dBm Example: Delta = 0.26 dBm 0.55 dBm = 0.29 dBm These examples are included to show the mathematics and do not represent actual readings.
NOTE
Add this delta value to the TX Cable Loss value during InService Calibration (see Step 4 in Table I-4).
Figure I-3: Delta Calibration Setup HP8935 to HP437B

HEWLETTPACKARD MODEL HP 8935
HP437B
SENSOR
DUPLEX OUT
POWER SENSOR SHORT RF CABLE FW00805
Figure I-4: Delta Calibration Setup HP8935 to HP8935

DUPLEX OUT
RF IN/OUT SHORT RF CABLE
FW00806
I-6
SEP 2009

Agilent E4406A Power Delta Calibration
continued
The Agilent E4406A transmitter tester and E4432B signal generator test equipment combination can be used for ISC of IS2000 CDMA 1X as well as IS95A/B operation modes. The power delta calibration is performed on the E4406A, but the E4432B is required to generate the reference signal used to calculate the power delta offset. After the offset value has been calculated, add it to the TX cable loss value in the LMF. Follow the procedure in Table I-3 to perform the Agilent E4406A Power Delta Calibration procedure. Table I-3: Agilent E4406A Power Delta Calibration Procedure Step Action
NOTE
Perform this procedure after test equipment has been allowed to warmup and stabilize for a minimum of 60 minutes. After it is warmed up and stabilized, calibrate the test equipment as described in the Test Set Calibration section of the Optimization/Calibration chapter in the SC 4812T Optimization/ATP manual. 1 Zero the Power Meter prior to connecting the power sensor to the RF cable from the signal generator.
NOTE
For best accuracy, always rezero the power meter before connecting the power sensor to the component being calibrated. 2 3 Connect a short RF cable from the E4432B RF OUTPUT connector the HP437 power meter power sensor (see Figure I-5). Set the E4432B signal generator as follows: Press Preset to exit any modes for which the signal generator is configured. Press Frequency and enter the frequency of the channel to be calibrated using the numeric keypad. Using the soft keys to the right of the screen, select the frequency range to be measured (for example, MHz). Press Amplitude and, using the numeric keypad, set signal amplitude to 0 (zero). Using the soft keys, set the measurement type to dBm. On the E4432B, press RF On/Off to toggle the RF output to RF ON. Note that the RF On/Off status in the screen display changes. Measure and record the value reading on the HP437 power meter as result A____________________. On the E4432B, press RF On/Off to toggle the RF output to RF OFF. Note that the RF On/Off status in the screen display changes. Disconnect the short RF cable from the HP437 power meter power sensor, and connect it to the RF INPUT connector on the E4406A transmitter tester (see Figure I-6). table continued on next page
4 5 6 7
continued
Table I-3: Agilent E4406A Power Delta Calibration Procedure Step 8 Action
NOTE
Do not change the frequency and amplitude settings on the E4432B when performing the following steps. Set the E4406A as follows: Press Preset to exit any modes for which the transmitter tester is configured. Press MODE and, using the soft keys to the right of the screen, select cdmaOne. Press MEASURE and, using the soft keys, select spectrum. Press Frequency and, using the soft keys, select Center Frequency. Using the numeric keypad. enter the frequency of the channel to be calibrated. Using the soft keys, select the frequency range to be measured (for example, MHz). Press Input/Output and, using the soft keys, select Input Atten. Using the numeric keypad, set Input Atten to 0 (zero) and, using the soft keys, select dB. Using the soft keys, select External Atten and then select Mobile. Using the numeric keypad, set Mobile to 0 (zero) and, using the soft keys, select dB. Using the soft keys, select Base. Using the numeric keypad, set Base to 0 (zero) and, using the soft keys, select dB. Press MEASURE and, using the soft keys, select Channel Power.
9 10 11 12
On the E4432B signal generator, press RF On/Off to toggle the RF output to RF ON. Note that the RF On/Off status in the screen display changes. Read the measured Channel Power from the E4406A screen display and record it as result B____________________ . On the E4432B, press RF On/Off to toggle the RF output to RF OFF. Note that the RF On/Off status in the screen display changes. Calculate the Power Calibration Delta value. The delta value is the power meter measurement minus the Agilent measurement. Delta = A B Example: Delta = 0.70 dBm (1.25 dBm) = 0.55 dBm Example: Delta = 0.26 dBm 0.55 dBm = 0.29 dBm These examples are included to show the mathematics and do not represent actual readings.
NOTE
Add this delta value to the TX Cable Loss value during InService Calibration (see step 4 in Table I-4).
I-8
SEP 2009
continued
Figure I-5: Delta Calibration Setup Agilent E4432B to HP437

AGILENT E4432B AND E4406A HP437B
RF OUTPUT
SENSOR
POWER SENSOR SHORT RF CABLE
FW00858
Figure I-6: Delta Calibration Setup Agilent E4432B to Agilent E4406A

AGILENT E4432B AND E4406A
RF OUTPUT
SHORT RF CABLE
RF INPUT
FW00859
SEP 2009
I-9
InService Calibration InService Calibration

Overview
CAUTION This feature does NOT have fault tolerance at this time. The system has no safeguards to stop you from doing something that will take the BTS out of service. If possible, perform this procedure during a maintenance window. Follow the procedures in this section precisely, otherwise the entire BTS will most likely go OUT OF SERVICE. At the CBSC, only perform operations on expansion hardware when it is in the OOS_MANUAL state. The operator must be trained in the LMF operation prior to performing this procedure. Prerequisites S Expansion hardware has been added in the CBSC database, and the CDF file has been generated. S The expansion devices have been inserted into the CCCP cage and are in the OOS_MANUAL state at the CBSC. S The site specific cdf (with the expansion hardware) and cal files have been loaded onto the LMF. S The LMF has the same code and dds files as the CBSC to download. CAUTION Do not download code or data to any cards other than those you are working on. Downloading code or data to other cards will take the site OUT OF SERVICE. The code file version numbers must match the version numbers on the other cards in the frame. If the numbers do not match, the site may go OUT OF SERVICE. The BTS#.cdf, CBSC#.cdf, and CAL files for this BTS must have come from the CBSC.
S Test equipment has been configured per Figure I-7 and Figure I-8. S An RFDS (or at a minimum a directional coupler), whose loss is
already known, must be in line to perform the inservice calibration. S Test equipment has been calibrated after 1 hour warm up. S A short RF cable and two BNCN adapters are available to perform Cable Calibration.
I-10 1X SC4812T CLPA BTS Optimization/ATP SEP 2009
InService Calibration
continued
S The Power Delta Calibration has been performed (see Table I-1 or
Table I-2).
Figure I-7: Optimization/ATP Test Setup Using RFDS

TEST SETS
NOTE: IF BTS RX/TX SIGNALS ARE DUPLEXED: BOTH THE TX AND RX TEST CABLES CONNECT TO THE DUPLEXED ANTENNA GROUP. 20 DB PAD (FOR 1.7/1.9 GHZ) 10 DB PAD RX (FOR 800 MHZ) TEST OUT CABLE
HPIB TO GPIB BOX
COMMUNICATIONS TEST SET EXT REF IN EVEN SECOND/ SYNC IN

DUPLEX OUT RF IN/OUT
ANTENNA
TX TEST CABLE
TEST SET INPUT/ OUTPUT PORTS IN
20 DB PAD (FOR 1.7/1.9 GHZ) 10 DB PAD (FOR 800 MHZ) RFDS DUPLEXER DIRECTIONAL COUPLER FWD COUPLED PORT
IEEE 488 GPIB BUS
RX TEST CABLE
TX TEST CABLE
GPIB CABLE
RX ANTENNA PORT
TX ANTENNA PORT
BTS
FREQ MONITOR SYNC MONITOR CSM LAN B LAN A
DIP SWITCH SETTINGS
ON
G MODE
CDMA LMF
UNIVERSAL TWISTED PAIR (UTP) CABLE (RJ45 CONNECTORS)
INTERNAL PCMCIA ETHERNET CARD REF FW00759
SEP 2009
I-11
continued
Figure I-8: IS95 A/B/C Optimization/ATP Test Setup Using RFDS

TEST SETS
ADVANTEST R3267 (TOP) AND R3562 (BOTTOM)
TO EXT TRIG ON REAR OF SPECTRUM ANALYZER NOTE: IF BTS RX/TX SIGNALS ARE DUPLEXED: BOTH THE TX AND RX TEST CABLES CONNECT TO THE DUPLEXED ANTENNA GROUP. RX TEST CABLE
OUT
RF IN
ANTENNA
TX TEST CABLE
TEST SET INPUT/ OUTPUT PORTS IN
COMMUNICATIONS TEST SET EXT EVEN REF SECOND/ IN SYNC IN
EXT TRIG IN MOD TIME BASE IN (EXT REF IN) RF OUT
BNC T
20 DB PAD (FOR 1.7/1.9 GHZ) 10 DB PAD (FOR 800 MHZ) RFDS DUPLEXER DIRECTIONAL COUPLER FWD COUPLED PORT
IEEE 488 GPIB BUS
SIGNAL GENERATOR
NOTE:
BNC T GPIB CABLE
SYNTHE REF IN ON REAR OF SIGNAL GENERATOR IS CONNECTED TO 10 MHZ OUT ON REAR OF SPECTRUM ANALYZER
RX CABLE
TX CABLE
AGILENT E4432B (TOP) AND E4406A (BOTTOM)

RX ANTENNA PORT RF OUTPUT TX ANTENNA PORT
BTS
FREQ MONITOR RF INPUT SYNC MONITOR CSM TO TRIGGER IN ON REAR OF TRANSMITTER TESTER TO 10 MHZ IN (EXT REF IN) ON REAR OF TRANSMITTER TESTER LAN B LAN A
DIP SWITCH SETTINGS 19.6608 MHZ CLOCK
ON
G MODE
TO PATTERN TRIG IN ON REAR OF SIGNAL GENERATOR
CDMA LMF
BNC T
UNIVERSAL TWISTED PAIR (UTP) CABLE (RJ45 CONNECTORS)
INTERNAL PCMCIA ETHERNET CARD REF FW00759
I-12
SEP 2009
continued
Follow the procedure in Table I-4 to perform the InService Calibration. Table I-4: InService Calibration Step Action
NOTE
Perform this procedure after test equipment has been allowed to warmup and stabilize for a minimum of 60 minutes. 1 Set up the LMF for InService Calibration: Start the LMF by doubleclicking the LMF icon on the Windows desktop. Click Tools>Options from the menu bar at the login screen. Check the applicable spectrum analyzer check box and the signal generator check box on the Test Equipment tab. Ensure that the GPIB address is 18 for the CDMA analyzer and 1 for the signal generator. Uncheck any other other equipment that is selected. Click the Apply button. Select the BTS Options tab in the LMF Option window. Check the InService Calibration check box. Click the Apply button. Click the Dismiss button to close the LMF Option window. Login to the target BTS: Select the target BTS icon. Click the Login button at the login screen. Measure the Cable Loss using the Cable Calibration function: Click Util>Cable Calibration from the menu bar at the main window. Set the desired channel(s) and select TX and RX CABLE CAL at the cable calibration pop up window. Click the OK button to perform cable calibration. Follow the onscreen instructions to complete the cable loss measurement.
NOTE
The measured value is input automatically to the cable loss file. To view the cable loss file, click Util>Examine>Cable Loss>TX or RX. table continued on next page
SEP 2009
I-13
continued
Table I-4: InService Calibration Step 4 Action Add the spectrum analyzer power delta to the Cable Loss. To view the cable loss file, click Util>Examine>Cable Loss>TX or RX. Add the value computed in Table I-1 or Table I-2 to the TX Cable Loss.
NOTE
Be sure to include the sign of the value. The following examples are included to show the mathematics and do not represent actual readings: Example: 5.65 dBm + 0.55 dBm = 6.20 dBm Example: 5.65 dBm + (0.29 dBm) = 5.36 dBm Example: 5.65 dBm + 0.55 dBm = 5.10 dBm Example: 5.65 dBm + (0.29 dBm) = 5.94 dBm 5 Input the Coupler Loss for the TX and RX tests: Click Util>Edit>Coupler Loss>TX or RX from the menu bar at the main window. Input the appropriate coupler loss for the target carrier(s) by referring to the information taken at the time of BTS installation. Click the Save button. Click the Dismiss button to close the window. To view the coupler loss file, click Util>Examine>Coupler Loss>TX or RX. Have the CBSC operator put the redundant BBX OOS_MANUAL.
6 7
! CAUTION
Be sure to download OOS devices only. Loading inservice devices takes them OUT OF SERVICE and can result in dropped calls. The code file version numbers must match the version numbers on the other cards in the frame. If the numbers do not match, the site may go OUT OF SERVICE.
NOTE
Be sure to include the redundant BBX in steps 7, 8, and 9. Download code and data to the target devices: Click Tools>Update NextLoad>CDMA to set the code version that will be downloaded. Select the BTS(s) you need, check the appropriate code version in the pop up window, and click the Save button to close. Select the target BBX(s) on the CCCP cage picture. Click Device>Download>Code/Data to start downloading code. Select the target BBX(s) on the CCCP cage picture. Click Device>Download>Data to start downloading data. table continued on next page
I-14
SEP 2009
continued
Table I-4: InService Calibration Step 8 Action
! CAUTION
Perform the Inservice Calibration procedure on OOS devices only. Select the desired test: Select the target BBX(s) on the CCCP cage picture. Click Tests>[desired test] from the menu bar at the main window. Select the target carrier and confirm the channel number in the pop up window. Leave the Verify BLO check box checked. From the Test Pattern pick list, select a test pattern. Click the OK button to start calibration. Follow the onscreen instructions, except, do not connect to the BTS antenna port, connect to the directional coupler (fwd) port associated with the on screen prompt antenna port.
NOTE S Selecting Pilot (default) performs tests using a pilot signal only. S Selecting Standard performs tests using pilot, synch, paging and six traffic channels. This requires
an MCC to be selected.
S Selecting CDFPilot performs tests using a pilot signal, however, the gain for the channel elements
is specified in the CDF file.
S Selecting CDF performs tests using pilot, synch, paging and six traffic channels, however, the gain
for the channel elements is specified in the CDF file. 9 Save the result and download the BLO data to the target BBX(s): Click the Save Result button on the result screen. The window closes automatically. Logout from the BTS and close the LMF session: Click BTS>Logout to close the BTS connection. Close the LMF window. Restore the new bts*.cal file to the CBSC. Enable the target device(s) from the CBSC.
10
11 12
SEP 2009
I-15
Notes
continued
I-16
SEP 2009
Appendix J: Packet Backhaul Configuration

Appendix Content
BTS Router Configuration Operations Introduction . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminal Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminal Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Establishing a BTS Router Communication Session . . . . . . . . . . . . . . . . . . . . . BTS Router Serial Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtain BTS Router Minimum (Canned) Configuration Files from the OMCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining BTS Router Minimum (Canned) Configuration Files . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FTP File Transfer from the OMCR . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Router IOS Version Verification and Canned Configuration File Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using a TFTP Server to Copy Files to CF Memory Card . . . . . . . . . . . Change or Upgrade BTS Router IOS Version . . . . . . . . . . . . . . . . . . . . . . . . . . Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment and Software Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade/Replace Installed IOS Version and Verify File Sequence Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify and Upgrade ROMmon Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Equipment and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verification and Upgrade/Replacement of Installed ROMmon Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovery from BTS Router Boot to ROMmon . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simple Recovery from Boot to ROMmon . . . . . . . . . . . . . . . . . . . . . . . Extended Recovery from Boot to ROMmon . . . . . . . . . . . . . . . . . . . . . Entering or Changing BTS Router FE Interface IP Addresses . . . . . . . . . . . . . . FE Interface IP Addresses and Operating Parameters . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entering or Changing FE Interface IP Addresses . . . . . . . . . . . . . . . . .
J-1 J-1 J-1 J-2 J-2 J-2 J-5 J-5 J-8 J-8 J-8 J-9 J-15 J-15 J-17 J-35 J-35 J-35 J-36 J-36 J-47 J-47 J-47 J-48 J-48 J-57 J-57 J-57 J-67 J-72 J-72 J-72 J-72
Table of Contents
continued
Example BTS Router Canned Configuration Files . . . . . . . . . . . . . . . . . . . . . . BTS Router Canned Configuration File . . . . . . . . . . . . . . . . . . . . . . . . Obtaining the Latest Configuration File Content . . . . . . . . . . . . . . . . . Configuration File Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blue BTS Router Canned Configuration . . . . . . . . . . . . . . . . . . . . . . Red BTS Router Canned Configuration . . . . . . . . . . . . . . . . . . . . . . Network Interface Card (NIC) Configuration Worksheet . . . . . . . . . . . . . . . . . . Record of original NIC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . BTS router communication NIC configuration . . . . . . . . . . . . . . . . . . . External BTS Router Compact Flash (CF) Memory Card Installation and Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CF Memory Card Installation/Removal Operations . . . . . . . . . . . . . . . Tools Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Router CF Memory Card Removal and Installation . . . . . . . . . . .
J-77 J-77 J-77 J-77 J-78 J-81 J-84 J-84 J-84 J-85 J-85 J-85 J-86
J
BTS Router Configuration Operations Introduction BTS Router Configuration Operations Introduction
Overview
This appendix contains information and operations related to loading an external BTS router with the minimum standard (canned) configuration necessary for network communications. Once the router is communicating on the network, the full, sitespecific, operational configuration can be downloaded to the router over the network. This appendix includes sections on:
S Setting up communications with a router using a Microsoftr

Windowsrbased computer
S Downloading BTS router canned configuration files from the OMCR S Transferring the canned configuration files from the Windowsbased
computer to the BTS router
S Verifying and, if necessary, replacing/upgrading the IOS version

loaded on the CF memory card
S Verifying and, if necessary, replacing/upgrading the ROM monitor

lowlevel operating system version loaded in the BTS router
S Recovery from BTS router initialization with the ROM monitor
lowlevel operating system and troubleshooting to locate and correct the cause FE verification
S Changing the router FE interface IP addresses if necessary to support S Sample listings of the BTS router canned configuration files
Application
Unless otherwise noted, the procedures and information in this appendix apply to both the MWR 190027 and MWR 1941DC models of the external BTS router.
J
SEP 2009 1X SC4812T CLPA BTS Optimization/ATP J-1
Terminal Setup Terminal Setup

Creating a Terminal Session
General Confirming or changing the configuration data of External BTS Routers (EBR) an certian BTS Field Replaceable Units (FRU) requires establishing a ManMachine Interface (MMI) communication session between a laptop computer and the FRU or EBR. Using features of the Windows operating system, the connection properties for an MMI session can be saved on the laptop computer as a named HyperTerminal connection. This elminiates the need for setting up connection parameters each time an MMI session is required to support operations. Desktop Shortcut Once the named connection is saved, a shortcut for it can be created on the Windows operating system desktop. Double clicking the shortcut icon will start the connection without the need to negotiate multiple menu levels.
Terminal Settings
Perform the following to create a named HyperTerminal connection for FRU or EBR MMI interface and generate a Windows operating system desktop shortcut for it. NOTE There are differences between the Windows 2000 and Windows XT operating systems in the menus and screens used for creating a HyperTerminal connection. In the following procedure, items applicable only to: S Windows 2000 operating system will be identified with Win2000)
S Windows XT operating system will be identified with

WinXT
J
J-2 1X SC4812T CLPA BTS Optimization/ATP SEP 2009
Terminal Setup
continued
Table J-1: Establish HyperTerminal Connection Step 1 2 Action From the Windows operating system Start menu, select: Programs > Accessories Perform one of the following:
S For Win2000, select Hyperterminal and then click on HyperTerminal S For WinXT, select Communications and then click on the HyperTerminal icon. NOTE S If a Location Information Window appears, enter the required information, then click on the S If a You need to install a modem..... message appears, click on NO.
3 When the Connection Description box opens: Type a name for the connection being defined (for example, BTSRTR Session, MMI) in the Name: window, Highlight any icon preferred for the named connection in the Icon: chooser window, and Click OK. From the Connect using: pick list in the Connect To box displayed, select the RS232 port to be used for the connection (e.g., COM1 or COM2), and click OK. In the Port Settings tab of the COM# Properties window displayed, configure the RS232 port settings as follows:
Close button. (This is required the first time a HyperTerminal connection is configured, even if a modem is not to be used.)
4 5
S S S S S
6 7 8 9 10 11
Bits per second: 9600 Data bits: 8 Parity: None Stop bits: 1 Flow control: None
Click OK. With the HyperTerminal window still open and the connection running, select: File > Properties Click the Settings tab, click the arrow in the Emulation window, and select VT100 from the dropdown list. Click the ASCII Setup button, uncheck all boxes in the ASCII Setup window which appears, and click OK. Click OK for the connection Properties box. Save the defined connection by selecting: File > Save table continued on next page
J
Terminal Setup
continued
Table J-1: Establish HyperTerminal Connection Step 12 13 14 15 Close the HyperTerminal window by selecting: File > Exit Click the Yes button to disconnect when prompted. From the Windows operating system Start menu, select Programs > Accessories Perform one of the following: Action
S For Win2000, select Hyperterminal and release any pressed mouse buttons. S For WinXT, select Communications and double click the Hyperterminal folder.
16 17 18 Move the cursor over the newlycreated connection icon. Right click and drag the connection icon to the Windows operating system desktop and release the right mouse button. From the popup menu displayed, select one of the following depending on the operating system used:
S Win2000: Create Shortcut(s) Here S Winxp: Copy Here

19 If desired, reposition the shortcut icon for the new connection by dragging it to another location on the Windows operating system desktop.
NOTE
The shortcut icon can now be doubleclicked to open a BTS router or BTS card/module MMI HyperTerminal session without the need to negotiate multiple menu levels. 20 In WinXT, select File > Close to close the HyperTerminal window.
J
Establishing a BTS Router Communication Session Establishing a BTS Router Communication Session
BTS Router Serial Communication
For those procedures which require serial communication with BTS routers, follow the procedures in Table J-2 to initiate the communication session. This procedure calls out the LMF computer platform, but any VT100equivalent terminal or computer equipped with terminal emulation software and a hardware serial connector may be used. Required Items The following items are required to perform the verification:
S LMF computer platform or equivalent S Eightconductor (fourpair, unshielded twisted pair is acceptable)
rollover cable, two 8contact modular plugs (see Figure J-1 for cable wiring requirements)
S Adapter, DB9 plugto8contact modular plug, Global Computer

Supplies C4717 or equivalent (see Figure J-2 for adapter wiring requirements) Figure J-1: Wiring Diagram, BTS Router Communication Rollover Cable
8contact Modular Plug
8contact Plug Contact Numbering (Insertion End) 8 76543 21
8contact Modular Plug 8 7 6 5 4 3 2 1
1 2 3 4 5
Locking Clip
6 7 8
J
Establishing a BTS Router Communication Session

Figure J-2: Wiring Diagram, DB9 Plugto8contact Modular Plug Adapter
DB9 Receptacle
Adapter DB9 Receptacle Socket Numbering (Mating Side) 5 4 3 2 1
continued
8contact Modular Receptacle NC 6 3 2 5 4 7 1 8 NC

Adapter 8contact Receptacle Contact Numbering (Mating Side) 12 34567 8
1 2 3 4 5
8 7 6
6 7 8 9
Table J-2: Establishing BTS Router Serial Communication Step 1 2 Action If it has not been done, start the computer and allow it to complete bootup. If a named HyperTerminal connection for BTS router serial communication or BTS card/module MMI communication has not been created on the LMF computer, create one as described in Table J-1 in the Terminal Setup section of this appendix. Connect the computer to the BTS router as shown in Figure J-3. Start the named HyperTerminal connection for BTS router communication sessions by double clicking on its Windows desktop shortcut.
3 4
NOTE
If a Windows desktop shortcut was not created for the communication session, access the connection from the Windows Start menu by selecting: Programs > Accessories > Hyperterminal > HyperTerminal > <Named HyperTerminal Connection (for example, BTSRTR )> 5 Once the connection window opens, establish communication with the BTS router by pressing the computer Enter key until the prompt identified in the applicable procedure is obtained.
J
Establishing a BTS Router Communication Session

Figure J-3: LMF Computer Connections to BTS Router
continued
ROLLOVER CABLE
TO BTS ROUTER CONSOLE RECEPTACLE
DB9TORJ48C ADAPTER
COM1 OR COM2
OPTOATP00010
J
Obtain BTS Router Minimum (Canned) Configuration Files from the OMCR Obtain BTS Router Minimum (Canned) Configuration Files from the OMCR
Obtaining BTS Router Minimum (Canned) Configuration Files
After they are generated on the OMCR, the BTS router canned configuration files must be transferred to another computer platform from which they can be installed into the BTS routers. A number of procedures may be used to move the canned configuration files from the OMCR to a platform from which they can be loaded into the routers. Some alternatives are: 1. If a floppy diskette drive is available at the OMCR, such as the one for UNO workstations, the configuration files can be transferred to an LMF computer or similar machine using the NEC file transfer procedure in the Preparing the LMF section of the optimization/ATP manual. Directories identified in Table J-3 must be used rather than those in the NEC file transfer procedure. 2. If a Windows operating systembased server connection is available in the operators network and it can provide an FTP or telnet connection to the OMCR, files may be transferred by either the FTP or telnet methods. 3. If a dialup connection is available for accessing the OMCR, an FTP or telnet session may be possible to transfer files to the computer used to load the CF memory cards. The procedure provided in this section covers FTP transfer using a Windows operating systembased server in the operators network. Coordinate with the local network administrator to determine the method and procedure to use on a specific network.
Prerequisites
The following must be obtained from the local network administrator before performing the canned configuration file FTP procedure in Table J-3:
S User ID and password to log onto the OMCR S Name of the subdirectory where the specific BTS router group
canned configuration files to be downloaded were created
J
Obtain BTS Router Minimum (Canned) Configuration Files from the OMCR
continued
FTP File Transfer from the OMCR
This procedure uses the Windows operating systembased LMF computer platform to download BTS router canned configuration files from the OMCR. Follow the procedure in Table J-3. Table J-3: BTS Router Canned Configuration File FTP Transfer from the OMCR Step 1 2 3 4 Action If it has not been done, create a directory on the LMF computer where the BTS router canned configuration files will be stored. If it has not been done, obtain the OMCR logon user ID and password from the local network administrator. Connect the LMF computer to the local network and log on.
NOTE
This procedure uses the command line FTP client supplied with the Windows XP and Windows 2000 operating systems; however, any commercially available FTP client application can be used. Follow the manufacturers instructions for operation of an alternative application. Open a command line (MS DOS) window by clicking on Start > Programs > Command Prompt.
When the command line window opens, change to the directory where the canned configuration files will be stored on the LMF computer by entering:
cd pathname
Where pathname = the path to the required directory A response similar to the following will be displayed:
C:\> cd Can_Cfg C:\Can_Cfg>
J
continued Table J-3: BTS Router Canned Configuration File FTP Transfer from the OMCR Step 6 Action Check the contents of the directory by entering the following:
dir

C:\Can_Cfg>dir Volume in drive C is MAIN Volume Serial Number is F2AA1721 Directory of C:\Can_Cfg> 08/22/2002 08/22/2002 08/22/2002 08/22/2002 03:46p <DIR> . 03:46p <DIR> .. 03:46p 2,223 btsrtr_canned.blue 03:47p 2,223 btsrtr_canned.red 2 File(s) 4,644 bytes 2 Dir(s) 2,556,045,312 bytes free
C:\Can_Cfg>
If either or both of the following files are found in the directory, delete them or move them to another directory:
S btsrtr_canned.blue S btsrtr_canned.red
8 Begin the FTP session by entering the following:
ftp hostname
Where hostname = the OMCR hostname or IP address A response similar to the following will be displayed:
C:\Can_Cfg> ftp OMCR1 C:\Can_Cfg> Connected to OMCR1. 220 OMCR1 FTP server (SunOS 5.6) ready. User (OMCR1:(none)):
J
continued Table J-3: BTS Router Canned Configuration File FTP Transfer from the OMCR Step 9 Action Enter the User ID and password when prompted, pressing the Enter key after each. A response similar to the following will be displayed:
User (OMCR1:(none)): scadm 331 Password required for scadm. Password: 230 User scadm logged in. ftp>
10
Change to the directory where the BTS router canned configuration file subdirectories are created and verify the present working directory by entering the following, pressing the Enter key after each:
cd /home/scadm/btsrtr_canned_configs pwd

ftp> cd /home/scadm/btsrtr_canned_configs 240 CWD command successful. ftp> pwd 245 /home/scadm/btsrtr_canned_configs is current directory.
11
Enter the following to list the contents of the directory and be sure the specific canned configuration directory name provided by the administrator exists:
ls

ftp> ls 200 PORT command successful. 150 ASCII data connection for /bin/ls (10.182.29.117,80) (0 bytes). Mon_Jul_2_01:55:07_CDT_2002 Wed_Jul_24_09:35:41_CDT_2002 Tue_Aug_04_10:35:22_CDT_2002 226 ASCII Transfer complete. ftp: 30 bytes received in 0.02Seconds 1.50Kbytes/sec. ftp>
NOTE
Directory names where canned configuration files are located will consist of the weekday_month_day_time_year when the canned configuration files were created on the OMCR. table continued on next page
J
continued Table J-3: BTS Router Canned Configuration File FTP Transfer from the OMCR Step 12 Action Change to the directory specified for the BTS router group to be configured and list the directory contents by entering the following, pressing the Enter key after each command:
cd weekday_month_day_time_year ls

ftp> cd Wed_Jul_24_09:35:41_CDT_2002 250 CWD command successful. ftp> ls 200 PORT command successful. 150 ASCII data connection for /bin/ls (10.182.29.117,80) (0 bytes). btsrtr_canned.blue btsrtr_canned.red 226 ASCII Transfer complete. ftp: 39 bytes received in 0.05Seconds 0.78Kbytes/sec. ftp>
13
Change to the binary transfer mode and, if desired, turn on hash mark printing for transfer progress by entering the following, pressing the Enter key after each command:
bin hash

ftp> bin 200 Type set to I. ftp> hash Hash mark printing On ftp>
ftp: (2048 bytes/hash mark) .
J
continued Table J-3: BTS Router Canned Configuration File FTP Transfer from the OMCR Step 14 Action Download the BTS router canned configuration files to the LMF computer by performing the following: 1. Enter the following to download the first canned configuration file:
get btsrtr_canned.blue

ftp> get btsrtr_canned.blue 200 PORT command successful. 150 Binary data connection for btsrtr_canned.blue (10.182.29.117,80) (2223 bytes). # 226 Binary Transfer complete. ftp: 2223 bytes received in 0.59Seconds 3.76Kbytes/sec. ftp>
2. Enter the following to download the second BTS router canned configuration file:
get btsrtr_canned.red

ftp> get btsrtr_canned.red 200 PORT command successful. 150 Binary data connection for btsrtr_canned.red (10.182.29.117,80) (2223 bytes). # 226 Binary Transfer complete. ftp: 2223 bytes received in 0.59Seconds 3.76Kbytes/sec. ftp>
15
Before terminating the FTP session, open the Windows operating system Explorer (Explorer) application and view the contents of the directory where the canned configuration files are to be stored to be sure the files are present. Perform the following: 1. Click Start > Programs > Windows Explorer 2. In the lefthand pane of Explorer, expand the user profile and directory display for the drive where the canned configuration file storage directory is located by clicking on the + next to each icon, respectively. 3. Expand any subdirectories as required to display the directory folder where the canned configuration files are to be stored. 4. Click on the directory folder icon where the canned configuration files are to be stored. 5. In the righthand pane, verify that the files btsrtr_canned.blue and btsrtr_canned.red appear. 6. If the files appear, proceed to step 16. 7. If the files do not appear, repeat step 14, its substeps, step 15 and its substeps. table continued on next page
J
continued Table J-3: BTS Router Canned Configuration File FTP Transfer from the OMCR Step 16 Action Close Explorer, and, in the command line window, enter the following to terminate the FTP session:
bye

ftp> bye 221 Goodbye. C:\Can_Cfg>
17
Close the command line window by entering the following:

exit
18
BTS router canned configuration files are now ready for transfer to a BTS router.
J
BTS Router IOS Version Verification and Canned Configuration File Installation BTS Router IOS Version Verification and Canned Configuration File Installation
Introduction
Overview This section covers the procedures and commands required to verify the IOS version loaded on BTS router CF memory cards and copy standard canned configuration files to the routers. Because of the setup required and the length of some of the procedures, Motorola recommends performing the actions covered in this section at a central location to prepare the BTS routers for installation prior to the site visit. IOS Version Verification and File Sequence Position Version verification The IOS version loaded on the BTS router CF memory card should be verified as the version required for operation on the network where the routers will be installed. If the loaded IOS version is not correct, it can be replaced with a different version. There are several methods available to accomplish version verification. These depend on the equipment and software applications the user selects to use in installing the canned configuration files in the BTS routers. Appropriate verification procedures are included in each of the two canned configuration installation methods covered in this section. Methods to change or upgrade the loaded IOS version are provided in the Change or Upgrade BTS Router IOS Version section of this appendix and are referenced at the appropriate places in the canned configuration installation methods. File sequence position During initialization, the MWR 190027 or MWR 1941DC router will first search the startupconfig file for a boot system command line telling it in what directory and file to find the boot loader. If this line is not found, the router will default to attempting to boot from the first file in its flash memory. Flash memory for the MWR 190027 or MWR 1941DC is the CF memory card (software identifier slot0:). The canned configuration files used for BTS router installation do not contain a boot system command line because of the need to maintain flexibility for IOS version changes. Because of this, it is critical that the IOS file is the first file listed on the CF memory card. The canned configuration installation procedures contain steps to assure that this is the case, and, if it is not, provide guidance to correct the condition. It is important to remember that, if the router boots and displays a rommon 1 > prompt, the IOS file is missing, out of sequence, has a corrupted flash memory image or the startupconfig file contains a boot system line which specifies a missing or incorrect IOS pathname/filename.
BTS Router IOS Version Verification and Canned Configuration File Installation continued
Canned Configuration File Installation Filename and installation location requirements The canned configuration files for the BTS routers must be copied to the CF memory card. The filename of the file on the CF memory card must be cannedconfig. Canned configuration file location and filename requirements are a result of Mobile Wireless Center (MWC) actions during the process of switching a BTS from packet to circuit mode or during BTS reparenting to another OMCR. In this process, the MWC will query the BTS routers slot0: directory for a file named cannedconfig. A missing or misnamed file will cause problems with execution of the modeswitching process. Installation Method The startupconfig configuration file used by the BTS router during initialization is stored in NVRAM. This is a memory device internal to the router and is separate from the CF memory card. To install the canned configuration file so the router will use it during bootup, the file must be copied into the startupconfig file in NVRAM. This requires copying the canned configuration file from the Windows operating systembased LMF computer to the CF memory card installed in a router, and then copying it to the startupconfig file in the routers NVRAM. The only Motorolasupported method to copy files to the BTS router CF memory card is through tftp file transfer. CAUTION Motorola does not support using a CF memory card reader to copy files to the BTS router CF memory card. Do not use a CF memory card reader for either of the following actions: S Formatting a BTS router CF memory card
S Copying files to a BTS router CF memory card
CAUTION Do not format BTS router CF memory cards using a CF memory card reader. Only format CF memory cards in a BTS router. Using a card reader to format the CF memory card will result in improper BTS router initialization which requires special recovery procedures.
J
Using a TFTP Server to Copy Files to CF Memory Card
Required Equipment and Software The following items are required to perform this procedure:
S A Windows operating systembased computer which meets the

requirements of the LMF computer platform systembased computer: Windows 2000 Windows XP CAUTION BTS router CF memory cards loaded using computers equipped with Windows 98 versions earlier than Windows 98 SE and using the FAT16 file system will not operate properly, resulting in a complete site outage.
S One of the following operating systems for the Windows operating
S One of the following for the Windows operating systembased

computer: Internal 10/100baseT Network Interface Card (NIC) PCMCIA 10/100baseT NIC Communication Session section of this Appendix
S Cable, rollover, as described in the Establishing a BTS Router S DB9 plugto8contact modular plug adapter as described in the
Establishing a BTS Router Communication Session section of this Appendix pair, two 8contact modular plugs, in one of the following lengths, as determined necessary: 0.3 m (11.8 in) (Motorola pn 3088643C07) 0.6 m (23.6 in)(Motorola pn 3088643C13) 1.0 m (39.4 in) (Motorola pn 3088643C15) 2.1 m (84 in) (Motorola pn 3088643C08) 3.0 m (120 in) (Motorola pn 3088643C09)
S Cable, Ethernet crossover, Category 5E or better, unshielded twisted
S A +27 Vdc power supply to power the BTS router during

configuration file operations
S A tftp server software application (refer to the Setting Up the TFTP

Server Procedure in Cellular System Administration CDMA OnLine Documentation) such as: Cisco tftp server PumpKIN tftp server Any other equivalent tftp server application
J
J-17
SEP 2009
S A copy of the MWR 190027 or MWR 1941DC router IOS version
required for the network where the routers are to be installed (contact the network administrator or the Motorola account team for information on obtaining the required external BTS router IOS version)
Required Materials The following material is required to perform this method: S Marking material to identify the BTS router and CF memory card with the installed configuration (blue or red) Required Publications The following publications are required to perform procedures in this section: S The optimization/ATP manual for the BTS type S Cellular System Administration CDMA OnLine Documentation
S MWR 1941DC Wireless Mobile Edge Router Software Configuration

Preparation for Canned Configuration File TFTP Transfer to CF Memory Card
Preparation for a canned configuration file tftp transfer consists of the following activities: 1. Determining the speed of the LMF computer NIC (10 or 100 MHz) 2. Setting the LMF computer NIC IP address 3. Creating a directory (folder) on the LMF computer to be used for all tftp file transfers 4. Installing the tftp server application on the LMF computer, and setting the tftp server application root directory to the directory created in 2, above 5. Connecting the LMF computer to the BTS router for both HyperTerminal (serial) and Ethernet communication 6. BTS router powerup and initial configuration for Ethernet communication The following procedures are used to accomplish all of these preparatory actions. Set LMF computer NIC to communicate with BTS routers Follow the procedure in Table J-4 to set the NIC IP address. NOTE If the IP address for the LAN connection on an LMF computer is being changed using this procedure, the BTS 10base2 LAN IP address and subnet mask for the NIC must be restored before the LMF can log into a BTS to perform an optimization or ATP.
J
NOTE There are differences between the various operating systems supported on the LMF computer in the menus and screens used for setting or changing a NIC connection. In the following procedure, items unique to: S Windows XP operating system will be identified with WinXP
S Windows 2000 operating system will be identified with

Win2000
Table J-4: Configure Computer NIC Step 1 2 3 Action If it is not known, determine and record the speed of the LMF computer NIC (10 or 100 MHz) for use in step 7 of Table J-7. Start the computer. Depending on the installed operating system, from the Windows operating system Start menu, select one of the following:
S WinXP: Settings > Network Connections S Win2000: Settings > Network and Dialup Connections
4 5 In the list of displayed connections, locate the Local Area Network connection for the NIC to be used. Perform the following: 1. Highlight the connection for the NIC 2. Right click the highlighted connection 3. Select Properties from the popup menu. In the Local Area Connection Properties dialog box which appears, if Internet Protocol (TCP/IP) is not showing in the Components checked are used by this connection: (Win2000) or The connection uses the following items: (WinXP) listbox, refer to the operating system documentation and install TCP/IP. If the checkbox next to the Internet Protocol (TCP/IP) entry is not checked, click in the box to check it. Click the Configure button under the Connect using: list box at the top of the General tab. In the Properties dialog box for the NIC hardware, click the Advanced tab to bring it to the front. table continued on next page
7 8 9
J
Table J-4: Configure Computer NIC Step 10 Action
NOTE
If the installed NIC does not support speeds of 100 Mbps, note the maximum speed available (such as 10 Mbps) in the worksheet and use it when initially configuring the BTS router in later procedures. Perform one of the following as applicable for the installed operating system:
S For Win2000:
In the Property: listbox, highlight Connection Type. Note the setting in the Value: list box, and record it in Table 5-24 of the Network Interface Card (NIC) Configuration Worksheet at the end of this appendix. From the Value: listbox dropdown menu, select 100 Mbps Full_Duplex. Click OK.
S For WinXP:
In the Property: listbox, highlight Speed & Duplex. Note the setting in the Value: list box, and record it in Table 5-24 of the Network Interface Card (NIC) Configuration Worksheet at the end of this appendix. From the Value: listbox dropdown menu, select 100 Mb Full. Click OK. 11 Perform one of the following:
S Win2000:
Highlight the Internet Protocol (TCP/IP) entry. Cick on the Properties button below the Components checked are used by this connection:.
S WinXP:
Highlight the Internet Protocol (TCP/IP) entry. Cick on the Properties button below the The connection uses the following items: listbox. 12 In the Internet Protocol (TCP/IP) Properties dialog box which appears, perform the following: 1. Note all settings on the General tab, and record them in the Record of original NIC configuration subsection of the Network Interface Card (NIC) Configuration Worksheet at the end of this appendix. 2. If a black dot is not showing in the the radio button circle next to Use the following IP address:, click on the radio button. Result: A black dot will appear in the circle. 3. Refer to the Network Interface Card (NIC) Configuration Worksheet, and enter the BTS router communication setting values as indicated for the following under Use the following IP address: : IP address: Subnet mask: table continued on next page
J
Table J-4: Configure Computer NIC Step 13 14 Action Click OK for the Internet Protocol (TCP/IP) Properties dialog box. Click the OK button for the Local Area Connection Properties box.
Create default TFTP directory Perform the following to create a default tftp directory on the laptop computer. Table J-5: Create a Default TFTP Directory Step 1 2 3 4 5 6 7 8 9 10 11 12 Action Click Start > Programs > Windows Explorer to open the Windows operating system Explorer (Explorer) application. If the default tftp directory will be the same directory in which the files downloaded from the OMCR are stored, proceed to step 10. In the lefthand pane of Explorer, locate the icon for the drive where the default tftp directory is to be created. Highlight the drive icon and click Files > New > Folder. While observing the new folder icon in the righthand pane, type the name for the folder (for example, tftp_files ), and press the Enter key. In Explorer, locate the directory where the canned configuration files downloaded from the OMCR are stored. In the lefthand pane, highlight the directory where the files are stored. Scroll the lefthand pane until the newlycreated default tftp directory is visible. In the righthand pane, highlight the canned configuration files and drag them to the default tftp directory. In the lefthand pane, click on the default tftp directory, and verify that the canned configuration files appear in the righthand pane. Load a copy of the required BTS router IOS version into the default tftp directory using FTP, internet download, or media such as a flash drive (file size is over 7 MB). Click Files > Close to close Explorer.
Install and configure tftp server application To obtain, install, and configure the Cisco or PumpKIN tftp software applications, refer to the Setting Up the TFTP Server Procedure in Cellular System Administration CDMA OnLine Documentation For other tftp server applications, install and configure the application according to the manufacturers instructions.
IMPORTANT
When entering the name of the tftp server root directory while configuring the tftp server application, be sure to use the name of the directory identified in Table J-4, step 2, or created in Table J-5, step 2, above.
Connect the LMF computer to the BTS router Connect the LMF computer to the BTS router by following the procedure in Table J-6 and referring to Figure J-4. Figure J-4: LMF Computer TFTP Connections to BTS Router
FAST ETHERNET PORT FE 0 (SOFTWARE DESIGNATION FA0/0) CONSOLE PORT
ETHERNET CROSSOVER CABLE
ROLLOVER CABLE TO BTS ROUTER CONSOLE RECEPTACLE DB9TORJ48C ADAPTER
COM1 OR COM2
10/100BASE T NIC PORT

BTSRTR0025
J
Table J-6: Connecting the LMF Computer to the BTS Router for TFTP File Transfer Step 1 2 3 4 5 Action If the BTS router has not been connected to a power source, be sure the +27 Vdc power source is not on, and connect it to the router. Connect the LMF computer to the BTS router as shown in Figure J-4, referring to the list of required equipment in this section as required. If the LMF computer has not been started, turn it on, login, and allow it to boot to the desktop. Refer to the procedure in Table J-2 of this appendix, and start a HyperTerminal communication session for the BTS router. Start the tftp server application as specified for the software (refer to the Setting Up the TFTP Server Procedure in Cellular System Administration CDMA OnLine Documentation or the manufacturers instructions).
BTS router powerup and initial configuration for Ethernet communication Follow the procedure in Table J-7 to apply power to the router and set an initial configuration for Ethernet communication.
S The required version of the IOS is loaded on the CF memory card S The CF memory card is installed in the BTS router
Table J-7: BTS Router Powerup and Initial Ethernet Configuration Step Action
* IMPORTANT
This procedure does not cover all aspects of BTS router operation and programming. Before performing this procedure, review BTS router initialization, operation, and programming information and procedures in MWR 1941DC Wireless Mobile Edge Router Software Configuration Guide; part number 7813983. Have this publication available for reference while performing this procedure. 1 Be sure a CF memory card loaded with the Cisco IOS is installed in the BTS router (refer to the Replacing a Compact Flash (CF) Memory Card section of the BTS Router chapter in the 1X SC4812TMF BTS Field Replaceable Units for instructions to access the CF memory card slot).
NOTE
In this step do not touch the computer keyboard until the router completes the boot process. The router will buffer any keystrokes made during the boot process and interpret them as commands to be executed immediately following boot completion. Apply power to the router and allow it to complete bootup.
If a message similar to the following, is displayed, press the Enter key and proceed to step 5:
Press RETURN to get started!

Table J-7: BTS Router Powerup and Initial Ethernet Configuration Step 4 Action If a message similar to the following, is displayed type no and press the Enter key:
Basic management setup configures only enough connectivity for management of the system, extended setup will ask you to configure each interface on the system Would you like to enter basic management setup? [yes/no]:

Would you like to enter basic management setup? [yes/no]: no Cisco Internetwork Operating System Software IOS (tm) 1900 Software (MWR1900IM), Version 12.2(20020127:101239 Copyright (c) 19862002 by cisco Systems, Inc. Compiled Sun 27Jan02 06:08 by walrobin Router>
At the Router> user EXEC mode prompt, enter the following to access the privileged EXEC mode:
enable

Router>enable Router#
At the Router# privileged EXEC mode prompt, enter the following to access the configure submode:
configure terminal

Router#conf t Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
The router is now in the global configuration mode and ready to accept configuration changes entered from the keyboard. table continued on next page
J
Table J-7: BTS Router Powerup and Initial Ethernet Configuration Step 7 Action At the global configuration mode prompt, type each of the following commands, pressing the Enter key after each command:
hostname btsrtr1 interface fa0/0 ip address 100.100.100.2 255.255.255.252 speed 100 or 10 depending on the speed of the LMF computer NIC duplex full no shutdown line con 0 exectimeout 0 0 no login line vty 0 4 no login
Responses similar to the following will be displayed:

Router(config)#hostname BTSRTR1 BTSRTR1(config)#interface fa0/0 BTSRTR1(configif)#ip address 100.100.100.2 255.255.255.252 BTSRTR1(configif)#speed 100 BTSRTR1(configif)#duplex full BTSRTR1(configif)#no shutdown BTSRTR1(configif)#line con 0 BTSRTR1(configline)#exectimeout 0 0 BTSRTR1(configline)#no login BTSRTR1(configline)#line vty 0 4 BTSRTR1(configline)#no login BTSRTR1(configline)#
Once the correct parameters have been set, return to the privileged EXEC mode prompt by holding down the Ctrl key and pressing z (Ctrl+z). A response similar to the following will be displayed:
BTSRTR1(configline)# ^z 01:11:27: %SYS5CONFIG_I: Configured from console by console BTSRTR1#
NOTE
Entering exit twice, pressing the Enter key after each entry, will also complete the configuration process and return the router to the privileged EXEC mode. table continued on next page
J
Table J-7: BTS Router Powerup and Initial Ethernet Configuration Step 9 Action Verify port FE 0 (fa0/0) is configured with the correct IP address by entering the following:
show ip interface brief

BTSRTR1#sh ip int br Interface IP Address FastEthernet0/0 100.100.100.2 Serial0:0 unassigned FastEthernet0/1 unassigned Serial1:0 unassigned BTSRTR1# OK? YES YES YES YES Method manual unset unset unset Status Protocol up up administratively down down administratively down down administratively down down
10
The router is now configured for Ethernet communication on FE 0, and the canned configuration file can be transferred by tftp. Proceed to Table J-8.
Verifying IOS Version and Canned Configuration File TFTP Transfer to the BTS Router
Prerequisites A copy of the required MWR 190027 or MWR 1941DC router IOS version file must be installed in the default tftp directory (transfer the file to the LMF computer using FTP, internet download, or media such as a flash drive; file size is approximately 78 MB) IMPORTANT
MWR 1941DC routers must be loaded with IOS version mwr1900imz.1228.MC2d.bin or later. This router model will not function properly with earlier IOS versions.
IOS verification and canned configuration file transfer Follow the procedure in Table J-8 to verify the loaded IOS version and transfer the canned configuration files from the LMF computer to the BTS router CF memory card.
J
IMPORTANT
This procedure does not cover all aspects of BTS router operation and programming. Before performing this procedure, review BTS router initialization, operation, and programming information and procedures in MWR 1941DC Wireless Mobile Edge Router Software Configuration Guide; part number 7813983. Have this publication available for reference while performing this procedure.
Table J-8: Transfer Canned Configuration Files to the BTS Router Using a TFTP Server Step Action
! CAUTION
If personal firewall and/or intrusion detection software such as Black ICE is running on the LMF computer, shut it down before performing this procedure. If this is not done, the tftp transfer process will not operate. 1 On the LMF computer, if it has not been done, start the tftp server according to the manufacturers directions (refer to the Setting Up the TFTP Server Procedure in the Cellular System Administration CDMA OnLine Documentation). If a HyperTerminal communication session with the BTS router is not running, start one following the procedure in Table J-2. In the HyperTerminal window, the router must be in the privileged EXEC mode, as indicated by a number sign at the end of the prompt:
BTSRTR1#
2 3
Be sure the Ethernet crossover cable is connected between the LMF computer NIC port and the BTS router FE 0 port (Figure J-4). table continued on next page
J
Table J-8: Transfer Canned Configuration Files to the BTS Router Using a TFTP Server Step 5 Action Begin verification that the CF memory card contains the correct version of the Cisco IOS by entering the following:
dir slot0:

BTSRTR1#dir slot0: Directory of slot0:/ 1 rw 7051976 Mar 01 1993 00:11:34 mwr1900imz.1228.MC2a.bin
31932416 bytes total (24879104 bytes free) BTSRTR1#
NOTE
1. The IOS defaults to the CF memory card (slot0:) directory unless the present working directory has been changed using the cd command. Determine the present working directory by entering pwd . If the present working directory has been changed, enter the command cd slot0: to return to the default setting. 2. If slot0: is included in the command, be sure to include the colon (:) after slot0 when typing the command. 3. The IOS filename will be similar to the following: mwr1900imz.1228.MC2a.bin table continued on next page
J
Table J-8: Transfer Canned Configuration Files to the BTS Router Using a TFTP Server Step 6 Action Direct the router to show the version information by entering the following:
show version

BTSRTR1#sh ver Cisco Internetwork Operating System Software IOS (tm) 1900 Software (MWR1900IM), Version 12.2(8)MC2a, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) TAC Support: http://www.cisco.com/tac Copyright (c) 19862002 by cisco Systems, Inc. Compiled Mon 05Aug02 11:07 by nmasa Image textbase: 0x60008940, database: 0x60B54000 ROM: System Bootstrap, Version 12.2(20020113:235343) [sbosewilma 109], DEVELOPMENT SOFTWARE ROM: 1900 Software (MWR1900IM), Version 12.2(8)MC2a, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) Router uptime is 1 minute System returned to ROM by poweron System image file is slot0:mwr1900imz.1228.MC2a.bin cisco mwr1900 (R7000) processor (revision 0.1) with 121856K/18432K bytes of memory. Processor board ID JMX0611K5TS R7000 CPU at 240Mhz, Implementation 39, Rev 3.3, 256KB L2 Cache Bridging software. X.25 software, Version 3.0.0. Primary Rate ISDN software, Version 1.1. Toaster processor tmc is running. 2 FastEthernet/IEEE 802.3 interface(s) 2 Serial network interface(s) 2 Channelized T1/PRI port(s) DRAM configuration is 64 bits wide with parity disabled. 55K bytes of nonvolatile configuration memory. 31360K bytes of ATA Slot0 CompactFlash (Read/Write) Configuration register is 0x101 BTSRTR1#
Compare the IOS filename returned in step 5 and the second line of the version information in step 6. Note the correspondence between the filename and IOS version information.
* IMPORTANT
MWR 1941DC routers must be loaded with IOS version mwr1900imz.1228.MC2d.bin or later. This router model will not function properly with earlier IOS versions. table continued on next page
Table J-8: Transfer Canned Configuration Files to the BTS Router Using a TFTP Server Step 8 Action If the IOS filename from the CF memory card returned in step 5 is different than the filename of the required IOS version loaded in the LMF computer default tftp directory, perform the procedure in Table J-9 to load the required version, and then return to step 9, below.
! CAUTION
The file sequence on the CF memory card can not be verified with application programs which place the listed file names in alphabetical order (for example, certain Unix telnet applications, Unix directory listing commands, and Windows file managers such as Windows Explorer). This portion of the procedure is intended for use only with applications, such as HyperTerminal, which do not list directory contents alphabetically. If the IOS version is correct and there is more than one file loaded on the CF memory card, be sure the IOS file is the first file listed in the directory content display. If it is not, perform the following: 1. Backup all files on the CF memory card to the LMF computer default tftp directory by performing steps 3 through 10 of Table J-9. 2. Perform steps 25 through 29 of Table J-9, as applicable. 3. Type the following to delete a possible boot system line in the startupconfig file, pressing the Enter key after the command and at each prompt to confirm the filename and deletion operation:
del nvram:startupconfig

BTSRTR1#del nvram:startupconfig Delete filename [startupconfig]? Delete nvram:startupconfig? [confirm] [OK] BTSRTR1#
NOTE
Be sure to include the colon (:) after nvram when typing the command. table continued on next page
J
Table J-8: Transfer Canned Configuration Files to the BTS Router Using a TFTP Server Step Action 4. Verify the startupconfig file size has been reduced to a minimum by entering the following:
dir nvram:

Router#dir nvram: Directory of nvram:/ 53 54 rw 5 5 <no date> <no date> startupconfig privateconfig
10
At the privileged EXEC mode prompt, enter the following:

copy tftp:btsrtr_canned.color slot0:cannedconfig
Where color = blue or red, as applicable. A response similar to the following will be displayed:
BTSRTR1#copy tftp:btsrtr_canned.blue slot0:cannedconfig Address or name of remote host []?
11
At the prompt for the remote host address or name, enter the IP address of the LMF computer NIC:
100.100.100.1

BTSRTR1#copy tftp:btsrtr_canned.blue slot0:cannedconfig Address or name of remote host []? 100.100.100.1 Destination filename [cannedconfig]?
J
Table J-8: Transfer Canned Configuration Files to the BTS Router Using a TFTP Server Step 12 Action At the prompt for the destination filename, press the Enter key. A response similar to the following will be displayed:
BTSRTR1#copy tftp:btsrtr_canned.blue slot0:cannedconfig Address or name of remote host []? 100.100.100.1 Destination filename [cannedconfig]? Loading btsrtr_canned.blue from 100.100.100.1 (via Ethernet0/0): ! [OK 2457/4096 bytes] 2457 bytes copied in 84.724 secs (29 bytes/sec) BTSRTR1#
13
Verify that the canned configuration file is saved on the CF memory card by entering the following:
dir

Directory of slot0:/ 1 2 rw rw 7051976 2457 Mar 01 1993 00:11:34 Mar 01 1993 00:14:48 mwr1900imz.1228.MC2a.bin cannedconfig
14
To allow the BTS router to boot using the canned configuration, enter the following:
copy cannedconfig startupconfig

BTSRTR1#copy cannedconfig start Destination filename [startupconfig]?
15
When prompted for the destination file name, press the Enter key. A response similar to the following will be displayed:
BTSRTR1#copy cannedconfig start Destination filename [startupconfig]? 2457 bytes copied in 3.52 secs BTSRTR1#
J
Table J-8: Transfer Canned Configuration Files to the BTS Router Using a TFTP Server Step 16 Action Display and note the file size of startupconfig by entering the following:
dir nvram:

Directory of nvram:/ 26 27 rw 2457 5 <no date> <no date> startupconfig privateconfig
17 18 19
Scroll the HyperTerminal window back to the slot0: directory display obtained in step 13, above. Compare the file size of startupconfig to the canned configuration file to verify the copy operation. File sizes should be the same. If desired, the contents of the startupconfig file may be verified against the file listings at the end of this appendix for the blue or red canned configuration, as applicable, by entering the following:
show startupconfig
NOTE
Pressing the space bar at the MORE prompt will scroll another screenfull of data. Pressing the Enter key will scroll the screen one line at a time. 20 Verify the router will boot properly on the IOS and revised startupconfig files by entering the following:
reload

BTSRTR1#reload System configuration has been modified. Save? [yes/no]: n Proceed with reload? [confirm]
21 22
If prompted to save a modified configuration, enter n for no, and press the Enter key. When prompted to proceed with reload, press the Enter key to continue the reload operation. table continued on next page
J
Table J-8: Transfer Canned Configuration Files to the BTS Router Using a TFTP Server Step 23 Action
NOTE
Reloading the router with the revised startupconfig file will change router FE port speed to 100. If the router FE port speed was changed to 10 to communicate with the LMF computer NIC, the computer may indicate that the FE LAN connection has been lost at this point. Verify the router reboots without displaying the rommon 1 > prompt or error messages related to port configurations. If the router boots to the rommon prompt, proceed to the Recovery from BTS Router Boot to rommon section of this appendix.
24 25
Using the tagging materials, tag the router to clearly identify the installed configuration (blue (BTSRTR1) or red (BTSRTR2)). Remove the CF memory from the router following the procedure in the Replacing a Compact Flash (CF) Memory Card section of the BTS Router chapter in the 1X SC4812TMF BTS Field Replaceable Units, mark the installed configuration (blue or red) on the card label, and install the card in the router following the CF memory card replacement procedure in the 1X SC4812TMF BTS Field Replaceable Units. If an additional router must have the canned configuration installed, perform the following: 1. Disconnect the cabling from the BTS router. 2. Remove power from the router and disconnect it from the power supply. 3. Repeat the procedures in Table J-6, Table J-7, and this table (Table J-8) using the additional router.
26
27 28 29
If no additional routers must be configured, perform the first two substeps of step 26. On the LMF computer, shut down the tftp server application and exit the HyperTerminal session. If no additional tftp transfer activities will be performed, change the NIC IP address and subnet mask back to those for LMFBTS communication recorded in Table J-4, step 10.
! CAUTION
If the BTS 10base2 LAN IP address and subnet mask for the LMF computers NIC are not restored, the LMF can not log into a BTS when attempting to perform a BTS optimization or ATP.
J
Change or Upgrade BTS Router IOS Version Change or Upgrade BTS Router IOS Version
Background
BTS routers are supplied with CF memory cards preloaded with a version of the IOS. Prior to installing the routers in a BTS, the loaded IOS version should be verified as being the one required for the network. It is critical to also verify that the IOS file is the first file on the CF memory card. If another file precedes the IOS file, the BTS router will not boot properly and will not function in the network.
Equipment and Software Required
The following items are required to perform this procedure:

requirements of the LMF computer platform systembased computer: Windows 2000 Windows XP CAUTION BTS router CF memory cards loaded using computers equipped with Windows 98 versions earlier than Windows 98 SE and using the FAT16 file system will not operate properly, resulting in a complete site outage.
S Cable, rollover, as described in the Establishing a BTS Router

Communication Session section of this Appendix
S DB9 plugto8contact modular plug adapter as described in the


Server Procedure in Cellular System Administration CDMA OnLine Documentation) such as:
J
J-35
SEP 2009
Change or Upgrade BTS Router IOS Version
continued
Cisco tftp server PumpKIN tftp server Any other equivalent tftp server application S A copy of the MWR 190027 or MWR 1941DC router IOS version required for the network where the routers are to be installed NOTE Contact the network administrator or the Motorola Account Team for assistance in determining and obtaining a copy of the required IOS version. IMPORTANT
*
Required Publications
MWR 1941DC routers must be loaded with IOS version mwr1900imz.1228.MC2d.bin or later. This router model will not function properly with earlier IOS versions.
The following publication is required to perform procedures in this section: S MWR 1941DC Wireless Mobile Edge Router Software Configuration Guide; part number 7813983
Upgrade/Replace Installed IOS Version and Verify File Sequence Position
Description This procedure covers using an LMF computer equipped with a tftp server application to perform the following activities: 1. Verify the IOS version loaded on a CF memory card and running on a BTS router 2. Upgrade or replace the IOS version installed in a BTS router 3. Ensure the IOS file is the first file on the CF memory card Prerequisites The following are required prior to performing this procedure: S The LMF computer and BTS router have been prepared for tftp file transfer and are operating as they would be after performing the procedures in Table J-4, Table J-6, Table J-7, and steps 1 through 8 of Table J-8 S A copy of the required IOS version is loaded into the tftp default directory of the LMF computer Upgrading/replacing installed IOS version and verifying file sequence position Follow the procedure in Table J-9 to replace or upgrade the installed IOS version using the tftp server application, and ensure the IOS file is first in the stored file sequence on the CF memory card.
continued
Table J-9: Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position Step Action
* IMPORTANT
This procedure does not cover all aspects of BTS router operation and programming. Before performing this procedure, review BTS router initialization, operation, and programming information and procedures in MWR 1941DC Wireless Mobile Edge Router Software Configuration Guide; part number 7813983. Have this publication available for reference while performing this procedure. 1 This procedure assumes the LMF computer and BTS router are configured, connected, and operating as they would be after performing the procedures in Table J-4, Table J-6, Table J-7, and steps 1 through 8 of Table J-8. If necessary, perform these procedures now.
NOTE
The IOS present working directory defaults to the CF memory card (slot0:) directory unless the present working directory has been changed using the cd command. Determine the present working directory by entering pwd . If the present working directory has been changed, enter the command cd slot0: to return to the default setting. Identify the filename of the currently loaded IOS which must be replaced by entering the following:
dir

BTSRTR1#dir Directory of slot0:/ 1 2 rw rw 7051844 2212 Sep 23 2002 07:15:08 Mar 01 1993 00:11:00 mwr1900imz.07022002.bin cannedconfig
Begin to backup the currently installed version of the routers IOS to the LMF computers default tftp directory by entering the following:
copy old_IOS_filename tftp:
Where old_IOS_filename = the filename of the IOS currently loaded on the BTS router CF memory card. A response similar to the following will be displayed:
BTSRTR1#copy mwr1900imz.07022002.bin tftp: Address or name of remote host []?
J
continued
Table J-9: Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position Step 4 At the remote host prompt, enter the following:
100.100.100.1
Action

Address or name of remote host []? 100.100.100.1 Destination filename [mwr1900imz.07022002.bin]?
If the default filename displayed in the prompt is correct, press the Enter key to accept it. If it is missing or not correct, enter the correct filename. A response similar to the following will be displayed if the default filename is selected:
Address or name of remote host []? 100.100.100.1 Destination filename [mwr1900imz.07022002.bin]? !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 7051844 bytes copied in 109.92 secs (64697 bytes/sec) BTSRTR1#
J
continued
Table J-9: Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position Step 6 Action If additional files are stored on the CF memory card, begin backing them up to the LMF computers default tftp directory by entering the following:
copy additional_filename tftp:
Where additional_filename = the filename of an additional file loaded on the BTS router CF memory card. A response similar to the following will be displayed:
BTSRTR1#copy cannedconfig tftp: Address or name of remote host [100.100.100.1]?
If the default IP address displayed in the prompt is correct, press the Enter key to accept it. If it is missing or not correct, enter the correct IP address for the LMF computer. A response similar to the following will be displayed if the default filename is selected:
Address or name of remote host [100.100.100.1]? Source filename [cannedconfig]?
Source filename [cannedconfig]? Destination filename [cannedconfig]?
If the default filename displayed in the prompt is correct, press the Enter key to accept it. If it is missing or not correct, enter the correct filename. A response similar to the following will be displayed:
Destination filename [cannedconfig]? ! [OK 2212/4096 bytes] 2212 bytes copied in 0.152 secs BTSRTR1#
10
If more files are stored on the CF memory card, repeat steps 6 through 9 until all files have been backed up to the LMF computer. table continued on next page
J
continued
Table J-9: Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position Step 11 Action Delete all files from the CF memory card by entering the following command:
format slot0:

BTSRTR1#format slot0: Format operation may take a while. Continue? [confirm]
12
Press the Enter key to continue the format operation. A response similar to the following will be displayed:
Format operation may take a while. Continue? [confirm] Format operation will destroy all data in slot0:. Continue? [confirm]
13
Format operation will destroy all data in slot0:. Continue? [confirm] Format: Drive communication & 1st Sector Write OK... Writing Monlib sectors.................................................................... ................ Monlib write complete . Format: All system sectors written. OK... Format: Total sectors in formatted partition: 62560 Format: Total bytes in formatted partition: 32030720 Format: Operation completed successfully. Format of slot0 complete BTSRTR1#
J
continued
Table J-9: Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position Step 14 Action Verify all files have been deleted from the CF memory card by entering the following:
dir

Directory of slot0:/ No files in directory 31932416 bytes total (31932416 bytes free) BTSRTR1#
15
Begin to copy the required version of the IOS from the LMF computer to the BTS router by entering the following:
copy tftp:new_IOS_filename slot0:
Where new_IOS_filename = the filename of the required IOS for the BTS router. A response similar to the following will be displayed:
BTSRTR1#copy tftp:mwr1900imz.1228.MC2a.bin slot0: Address or name of remote host [100.100.100.1]?
16
Address or name of remote host [100.100.100.1]? Source filename [mwr1900imz.1228.MC2a.bin]?
17
Source filename [mwr1900imz.1228.MC2a.bin]? Destination filename [mwr1900imz.1228.MC2a.bin]?
J
continued
Table J-9: Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position Step 18 Action If the default filename displayed in the prompt is correct, press the Enter key to accept it. If it is not correct, enter the correct filename. A response similar to the following will be displayed if the default filename is selected:
Destination filename [mwr1900imz.1228.MC2a.bin]? Accessing tftp://100.100.100.1/mwr1900imz.1228.MC2a.bin... Loading mwr1900imz.1228.MC2a.bin from 100.100.100.1 (via FastEthernet0/0): !!!! Loading mwr1900imz.1228.MC2a.bin from 100.100.100.1 (via FastEthernet0/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK 7051976/14103552 bytes] 7051976 bytes copied in 145.108 secs (48634 bytes/sec) BTSRTR1#
J
continued
Table J-9: Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position Step 19 Action Display the CF memory card directory to verify that the new IOS file is there by entering the following:
dir

BTSRTR1#dir Directory of slot0:/ 1 rw 7051976 Sep 23 2002 07:25:36 mwr1900imz.1228.MC2a.bin 31932416 bytes total (24880440 bytes free) BTSRTR1#
20
If any additional files previously stored on the CF memory card are to be copied to the card, perform the following: copy tftp:filename slot0: Where filename = the filename of the file to be copied to the CF memory card A response similar to the following will be displayed:
BTSRTR1#copy tftp:cannedconfig slot0: Address or name of remote host [100.100.100.1]?
21
If the default IP address displayed in the prompt is correct, press the Enter key to accept it. If it is missing or not correct, enter the correct IP address for the LMF computer. A response similar to the following will be displayed if the default IP address is selected:
Address or name of remote host [100.100.100.1]? Destination filename [cannedconfig]?
22
Destination filename [cannedconfig]? Accessing tftp://100.100.100.1/cannedconfig... Loading basic_config from 100.100.100.1 (via FastEthernet0/0): ! [OK 2212/4096 bytes] 2212 bytes copied in 0.152 secs BTSRTR1#
J
continued
Table J-9: Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position Step 23 Action After the additional file is copied to the CF memory card, display the CF memory card directory by entering the following:
dir

BTSRTR1#dir Directory of slot0:/ 1 rw 7051976 Sep 23 2002 07:24:18 mwr1900imz.1228.MC2a.bin 2 rw 2212 Mar 01 1993 00:09:06
cannedconfig
24 25
The IOS file must be the first file listed for the BTS router to boot properly. If it is, proceed to step 29.
! CAUTION
The file sequence on the CF memory card can not be verified with application programs which place the listed file names in alphabetical order (for example, certain Unix telnet applications, Unix directory listing commands, and Windows file managers such as Windows Explorer). This portion of the procedure is intended for use only with applications, such as HyperTerminal, which do not list directory contents alphabetically. If another file is listed before the IOS file, delete the file by performing steps 11 through 13 and display the directory of the CF memory card as described in step 23 to be sure the file is deleted.
26 27 28 29
Copy the file from the LMF computer to the CF memory card again by performing steps 20 through 23. If the file is again listed before the IOS file in the CF memory card directory display, format the CF memory card by performing steps 11 through 14 of this table. Copy the IOS file and any other required file to the formatted CF memory card by performing steps 15 through 24. If additional files are to be transferred to the CF memory card, perform steps 20 through 24 for each one. table continued on next page
J
continued
Table J-9: Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position Step 30 Action After making sure the IOS file is the first file on the CF memory card, restart the BTS router with the new IOS version by entering the following:
reload

31 32 33
If prompted to save a modified configuration, enter n for no, and press the Enter key. When prompted to proceed with reload, press the Enter key to continue the reload operation. Once the router has completed rebooting, change to the privileged EXEC mode and confirm the booted IOS version is correct by entering the following:
show version
A response similar to the following partial example will be displayed:

BTSRTR1#sh ver Cisco Internetwork Operating System Software IOS (tm) 1900 Software (MWR1900IM), Version 12.2(8)MC2a, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) . . . BTSRTR1#
34 35
Verify the version number displayed in the second line of the version information is the correct IOS version. If this procedure was entered from step 8 of Table J-8, return to Table J-8, step 9. table continued on next page
J
continued
Table J-9: Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position Step 36 Action If no other BTS router file operations or configuration actions are required, perform the following: 1. Remove power from the router and disconnect it from the power supply. 2. Disconnect all other cabling from the BTS router. 3. On the LMF computer, exit the HyperTerminal communications session. 37 If no additional tftp transfer activities will be performed, change the NIC IP address and subnet mask back to those for LMFBTS communication recorded in Table J-4, step 10.
! CAUTION
J
Verify and Upgrade ROMmon Version Verify and Upgrade ROMmon Version
Introduction
BTS routers are supplied preloaded with a version of the ROM monitor (ROMmon) lowlevel operating system. Along with the IOS version, the loaded ROMmon version should be verified as being the one required for the network. Procedures in this section are used to verify the loaded ROMmon version, and, if necessary, upgrade or change it to the required version. A tftp server application is needed to transfer the required ROMmon version to a BTS routers CF memory card.
Required Equipment and Software
The following items are required to perform ROMmon version verification and upgrade for both verification/upgrade methods:

requirements of the LMF computer platform systembased computer: Windows 2000 Windows XP CAUTION BTS router CF memory cards loaded using computers equipped with Windows 98 operating system versions earlier than Windows 98 SE and using the FAT16 file system will not operate properly, resulting in a complete site outage.
S Cable, rollover, as described in the Establishing a BTS Router

Communication Session section of this Appendix
S DB9 plugto8contact modular plug adapter as described in the

J
J-47
SEP 2009
Verify and Upgrade ROMmon Version
continued

Server Procedure in Cellular System Administration CDMA OnLine Documentation) such as: Cisco tftp server PumpKIN tftp server Any other equivalent tftp server application
S A copy of the MWR 190027 or MWR 1941DC router ROMmon

NOTE
version required for the network where the routers are to be installed
Contact the network administrator or the Motorola Account Team for assistance in determining and obtaining a copy of the required ROMmon version.
Required Publications
The following publication is required to perform procedures in this section:
S MWR 1941DC Wireless Mobile Edge Router Software Configuration

Verification and Upgrade/Replacement of Installed ROMmon Version
Description This procedure covers using an LMF computer equipped with a tftp server application to perform the following activities: 1. Verify the ROMmon version loaded and running on a BTS router 2. Upgrade or replace the ROMmon version installed in a BTS router Prerequisites The following are required prior to performing this procedure:
S The LMF computer and BTS router have been prepared for tftp file
transfer and are operating as they would be after performing the procedures in Table J-4, Table J-6, Table J-7, and steps 1 through 8 of Table J-8 default directory of the LMF computer
S A copy of the required ROMmon version is loaded into the tftp
J
continued
Verifying and Upgrading/replacing installed ROMmon version Follow the procedure in Table J-10 to verify and, if necessary, replace or upgrade the installed ROMmon version using the tftp server application. Table J-10: Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server Step Action
* IMPORTANT
This procedure does not cover all aspects of BTS router operation and programming. Before performing this procedure, review BTS router initialization, operation, and programming information and procedures in MWR 1941DC Wireless Mobile Edge Router Software Configuration Guide; part number 7813983. Have this publication available for reference while performing this procedure. 1 This procedure assumes the LMF computer and BTS router are configured, connected, and operating as they would be after performing the procedures in Table J-4, Table J-6, Table J-7, and steps 1 through 4 of Table J-8. If necessary, perform these procedures now. table continued on next page
J
continued
Table J-10: Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server Step 2 Action Determine the currently installed ROMmon version by entering the following at the router privileged EXEC mode prompt:
show version

BTSRTR1#sh ver Cisco Internetwork Operating System Software IOS (tm) 1900 Software (MWR1900IM), Version 12.2(8)MC2b, EARLY DEPLOYMENT RELEASE SOFTWARE (fc3) TAC Support: http://www.cisco.com/tac Copyright (c) 19862002 by cisco Systems, Inc. Compiled Mon 05Aug02 11:07 by nmasa Image textbase: 0x60008940, database: 0x60B54000 ROM: System Bootstrap, Version 12.2(20020113:235343) [sbosewilma 109], DEVELOPMENT SOFTWARE ROM: 1900 Software (MWR1900IM), Version 12.2(8)MC2b, EARLY DEPLOYMENT RELEASE SOFTWARE (fc3) Router uptime is 1 minute System returned to ROM by poweron System image file is slot0:mwr1900imz.1228.MC2b.bin cisco mwr1900 (R7000) processor (revision 0.1) with 121856K/18432K bytes of memory. Processor board ID JMX0611K5TS R7000 CPU at 240Mhz, Implementation 39, Rev 3.3, 256KB L2 Cache Bridging software. X.25 software, Version 3.0.0. Primary Rate ISDN software, Version 1.1. Toaster processor tmc is running. 2 FastEthernet/IEEE 802.3 interface(s) 2 Serial network interface(s) 2 Channelized T1/PRI port(s) DRAM configuration is 64 bits wide with parity disabled. 55K bytes of nonvolatile configuration memory. 31360K bytes of ATA Slot0 CompactFlash (Read/Write) Configuration register is 0x101 BTSRTR1#
To determine the currently installed ROMmon version, examine the ROM: System Bootstrap line in the response. table continued on next page
J
continued
Table J-10: Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server Step 4 Action Compare the installed ROMmon version information with the filename of the ROMmon version required for the network.
NOTE
1. Rommon filename format is similar to the following: MWR1900_RM2.srec.1228r.MC3.bin 2. The ROMmon filename reflects the version number of the software (1228r.MC3). 5 6 If the installed version is the one required for the network skip to step 26. If the installed ROMmon version is not the one required for the network, backup the current BTS router configuration to the LMF computer by entering the following:
copy nvram:startupconfig tftp

BTSRTR1#copy nvram:start tftp Address or name of remote host []?
NOTE
Be sure to include the colon (:) after nvram when typing the command. 7 At the prompt for the remote host address or name, enter the IP address of the LMF computer NIC:
100.100.100.1

BTSRTR1#copy copy nvram:start tftp Address or name of remote host []? 100.100.100.1 Source filename [startupconfig]?
Source filename [startupconfig]? Destination filename [startupconfig]?
J
continued
Table J-10: Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server Step 9 Action If the default filename displayed in the prompt is correct, press the Enter key to accept it. If it is missing or not correct, enter the correct filename. A response similar to the following will be displayed:
Destination filename [startupconfig]? ! [OK 2212/4096 bytes] 2212 bytes copied in 0.152 secs BTSRTR1#
10
NOTE
The IOS defaults to the CF memory card (slot0:) directory unless the present working directory has been changed using the cd command. Determine the present working directory by entering pwd . If the present working directory has been changed, enter the command cd slot0: to return to the default setting. Determine the amount of memory available (bytes free) on the CF memory card by entering the following:
dir

BTSRTR1#dir Directory of slot0:/ 1 rw 7051976 Sep 23 2002 07:24:18 mwr1900imz.1228.MC2b.bin 2 rw 2212 Mar 01 1993 00:14:48 31932416 bytes total (24885606 bytes free) Router#
cannedconfig
11
Be sure there is at least 1 MB (1048580) of free memory.
NOTE
A ROMmon version file requires approximately 0.7 MB. table continued on next page
J
continued
Table J-10: Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server Step 12 Action Begin to copy the required version of the ROMmon file from the LMF computer to the BTS router by entering the following:
copy tftp:new_rommon_filename slot0:
Where new_rommon_filename = the filename of the required ROMmon version for the BTS router. A response similar to the following will be displayed:
BTSRTR1#copy tftp:MWR1900_RM2.srec.1228r.MC3.bin slot0: Address or name of remote host [100.100.100.1]?
13
Address or name of remote host [100.100.100.1]? Source filename [MWR1900_RM2.srec.1228r.MC3.bin]?
14
Source filename [MWR1900_RM2.srec.1228r.MC3.bin]? Destination filename [MWR1900_RM2.srec.1228r.MC3.bin]?
15
If the default filename displayed in the prompt is correct, press the Enter key to accept it. If it is not correct, enter the correct filename. A response similar to the following will be displayed if the default filename is selected:
Destination filename [MWR1900_RM2.srec.1228r.MC3.bin]? Accessing tftp://100.100.100.1/MWR1900_RM2.srec.1228r.MC3.bin... Loading MWR1900_RM2.srec.1228r.MC3.bin from 100.100.100.1 (via FastEthernet0/0): !!!! Loading MWR1900_RM2.srec.1228r.MC3.bin from 100.100.100.1 (via FastEthernet0/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK 614306/14103552 bytes] 614306 bytes copied in 13.059 secs (48634 bytes/sec) BTSRTR1#
J
continued
Table J-10: Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server Step 16 Action Display the CF memory card directory to verify that the new ROMmon version file is there by entering the following:
dir

BTSRTR1#dir Directory of slot0:/ 1 rw 7051976 Sep 23 2002 07:25:36 2 rw 2212 Mar 01 1993 00:09:06 3 rw 614306 Dec 13 2002 14:59:36 MWR1900_RM2.srec.1228r.MC3.bin 31932416 bytes total (24263922 bytes free) BTSRTR1# mwr1900imz.1228.MC2b.bin cannedconfig
17
Replace the existing ROMmon version with the new one copied to the CF memory card by entering the following:
upgrade rommonitor file slot0:MWR1900_RM2.srec.1228r.MC3

BTSRTR1#This command will reload the router. Continue?[yes/no]
18
When prompted to continue, enter yes and press the Enter key. A response similar to the following will be displayed:
BTSRTR1#This command will reload the router. Continue?[yes/no] yes ROMMON image upgrade in progress Erasing boot flash eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee Programming boot flash pppp Now reloading
19
When the router has completed initialization, change to the router privileged EXEC mode by entering the following:
enable

BTSRTR1>enable BTSRTR1#
J
continued
Table J-10: Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server Step 20 Action Verify the router has initialized with the new ROMmon version by entering the following:
show version
A response similar to the following partial response will be displayed:

BTSRTR1#sh ver Cisco Internetwork Operating System Software IOS (tm) 1900 Software (MWR1900IM), Version 12.2(8)MC2b, EARLY DEPLOYMENT RELEASE SOFTWARE (fc3) TAC Support: http://www.cisco.com/tac Copyright (c) 19862002 by cisco Systems, Inc. Compiled Mon 05Aug02 11:07 by nmasa Image textbase: 0x60008940, database: 0x60B54000 ROM: System Bootstrap, Version 12.2(8r)MC3 RELEASE SOFTWARE (fc1)
21 22
Compare the version displayed in the response ROM: System Bootstrap line to the filename of the new ROMmon version file copied to the CF memory card. If the router successfully rebooted with the new ROMmon version, the ROMmon file can be deleted from the CF memory card by entering the following:
delete slot0:new_rommon_filename
Where new_rommon_filename = the filename of the required ROMmon version copied to the CF memory card in steps 12 through 15, above. A response similar to the following will be displayed:
BTSRTR1#del slot0:MWR1900_RM2.srec.1228r.MC3.bin Delete filename [MWR1900_RM2.srec.1228r.MC3.bin]?
23
Delete filename [MWR1900_RM2.srec.1228r.MC3.bin]? Delete slot0:MWR1900_RM2.srec.1228r.MC3.bin? [confirm]
J
continued
Table J-10: Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server Step 24 Press the Enter key to confirm the deletion. A response similar to the following will be displayed if the default filename is selected:
Delete filename [MWR1900_RM2.srec.1228r.MC3.bin]? Delete slot0:MWR1900_RM2.srec.1228r.MC3.bin? [confirm] BTSRTR1#
Action
25
! CAUTION
In this step, do not delete the IOS and cannedconfig files from the CF memory card. The BTS router must have these files on the card to properly boot or switch between packet and circuit mode. If additional unnecessary files, such as a backup of the startupconfig file, are also on the CF memory card, delete them by repeating steps 22 through 24 for each file.
26
If no other BTS router file operations or configuration actions are required, perform the following: 1. Remove power from the router and disconnect it from the power supply. 2. Disconnect all cabling from the BTS router. 3. On the LMF computer, exit the HyperTerminal communications session.
27
If no additional tftp transfer activities will be performed, change the NIC IP address and subnet mask back to those for LMFBTS communication recorded in Table J-4, step 10.
! CAUTION
J
Recovery from BTS Router Boot to ROMmon Recovery from BTS Router Boot to ROMmon
Introduction
ROM monitor boot conditions Under certain circumstances the BTS router will initialize with the ROM monitor (ROMmon) operating system rather than the IOS. These circumstances include:
S The hexadecimal value in the routers configuration register has been S IOS file is missing from the CF memory card S IOS file is not the first file on the CF memory card S Startupconfig file contains an outdated boot system line specifying
an IOS file which has been replaced with an updated version error(s) in the IOS filename
changed from the factory default (can change the location from where the router attempts to load code for bootup).
S Startupconfig file contains boot system line with typographical S IOS file image on the CF memory card is corrupted
Description Router operation on ROMmon is signalled by the display of the rommon # > prompt, where # is a number which increments each time a command is issued. ROMmon is a lowlevel operating system which provides limited capabilities for router testing and troubleshooting operations, including viewing directory contents and booting from a specified file. Recovery methods Two recovery methods are included in this section. The first is the simplest and requires that a valid, uncorrupted IOS version is installed on the CF memory card. The second method requires additional equipment and must be used in instances when an IOS file is not installed on the CF memory card or the installed IOS image is corrupted.
Simple Recovery from Boot to ROMmon
Requirements Unless it is certain that the IOS image on the CF memory card is corrupted, this method should always be the first tried for router recovery from ROMmon initialization. This method does not require any additional equipment beyond the items necessary to load canned configuration files into the BTS router. To be effective, this method does require that a valid, uncorrupted IOS image file is installed on the routers CF memory card.
J
Recovery from BTS Router Boot to ROMmon
continued
Recovery Follow the procedure in Table J-11 to attempt a simple recovery from a BTS router ROMmon initialization. Table J-11: Simple Recovery from BTS Router ROMmon Boot Step Action
* IMPORTANT
This procedure does not cover all aspects of BTS router operation and programming. Before performing this procedure, review BTS router initialization, operation, and programming information and procedures in MWR 1941DC Wireless Mobile Edge Router Software Configuration Guide; part number 7813983. Have this publication available for reference while performing this procedure. 1 This procedure assumes the LMF computer is set up and connected to the BTS router with an active HyperTerminal communication session. If it is not, follow the procedure in Table J-2 to establish a HyperTerminal communication session. With the rommon 1 > prompt displayed in the HyperTerminal window, enter the following to determine if the routers configuration register is set to the factory default value:
confreg

rommon 4 > confreg
Configuration Summary (Virtual Configuration Register: 0x100) enabled are: load rom after netboot fails console baud: 9600 boot: image specified by the boot system commands or default to: cisco2mwr1900 do you wish to change the configuration? y/n [n]:
NOTE S The configuration register setting is shown in the (Virtual Configuration Register: 0x____) line S 0x in the Virtual Configuration Register line indicates the numbers following are hexadecimal
3 If the value shown for the configuration register is 2102, skip to step 6. table continued on next page
J
continued
Table J-11: Simple Recovery from BTS Router ROMmon Boot Step 4 Action If the value shown for the configuration register is not 2102, perform the following: 1. Press the Return key to accept the default of n (for no). 2. Enter the following at the rommon prompt:
confreg 0x2102

rommon 3 > confreg 0x2102
You must reset or power cycle for new config to take effect rommon 4 >
3. Enter the following at the rommon prompt:

reset
A response which begins and ends similar to the following will be displayed:
rommon 4 > reset System Bootstrap, Version 12.2(20020113:235343) [sbosewilma 109], DEVELOPMENT SOFTWARE Copyright (c) 19942002 by cisco Systems, Inc. mwr1900 processor with 131072 Kbytes of main memory Main memory is configured to 64 bit mode with parity disabled
Readonly ROMMON initialized . ...<output omitted>... . Press RETURN to get started!
If the router reboots with the IOS, skip to step 21. table continued on next page
J
continued
Table J-11: Simple Recovery from BTS Router ROMmon Boot Step 6 Action If the configuration register is set properly and/or the router does not reboot with the IOS, enter the following at the rommon # > prompt to identify the IOS file on the CF memory card:
dir slot0:

rommon 1 > dir slot0: program load complete, entry point: 0x80008000, size: 0xb2a0 Directory of slot0: 2 3 4 2212 7051976 614306 rw rw rw cannedconfig mwr1900imz.1228.MC2b.bin MWR1900_RM2.srec.1228r.MC3.bin
rommon 2 >
NOTE
The IOS filename will be similar to the following: mwr1900imz.1228.MC2b.bin 7 If there is no IOS file on the CF memory card, proceed to Table J-12 and perform the extended recovery procedure. table continued on next page
J
continued
Table J-11: Simple Recovery from BTS Router ROMmon Boot Step 8 Action If an IOS file is found, note the IOS filename, and enter the following to begin recovery to an IOS boot:
boot slot0:IOS_filename
Where IOS_filename = the filename of the IOS noted in step 6, above. A successful IOS reboot operation will result in display of a response which begins and ends similar to the following:
rommon 2 > boot slot0:mwr1900imz.1228.MC2b.bin program load complete, entry point: 0x80008000, size: 0xb2a0 program load complete, entry point: 0x80008000, size: 0x6b99ac Self decompressing the image : ################################################################### [OK] Smart Init is enabled smart init is sizing iomem ID 00031A MEMORY_REQ TYPE
0X005F3C00 MWR1900 Mainboard 0X000F3BB0 public buffer pools 0X00211000 public particle pools
TOTAL: 0X008F87B0 . ...<output omitted>... . Press RETURN to get started!
9 10
If the router successfully reboots with the IOS, skip to step 12. If the router does not reboot with the IOS, perform the following: 1. Scroll the HyperTerminal display down until the directory display from step 6, above, is visible. 2. Compare the IOS filename from the directory display with the filename entered when performing step 8, above. 3. If the filename was typed incorrectly, repeat step 8, using care to type the filename correctly. table continued on next page
J
continued
Table J-11: Simple Recovery from BTS Router ROMmon Boot Step 11 12 Action If the router still does not reboot with the IOS after typing the filename correctly, proceed to Table J-12 and perform the extended recovery procedure.
! CAUTION
The file sequence on the CF memory card can not be verified with application programs which place the listed file names in alphabetical order (for example, certain Unix telnet applications, Unix directory listing commands, and Windows file managers such as Windows Explorer). This portion of the procedure is intended for use only with applications, such as HyperTerminal, which do not list directory contents alphabetically. After a successful reboot with IOS, perform the following to correct the cause of the boot to ROMmon: 1. At the BTSRTR1> user EXEC mode prompt, enter the following to access the privileged EXEC mode:
enable

BTSRTR1>enable BTSRTR1#
2. Enter the dir slot0: command to display the CF memory card directory, and, if the IOS file is not the first file listed, perform the procedure in Table J-9, steps 25 through 32, to correct the situation table continued on next page
J
continued
Table J-11: Simple Recovery from BTS Router ROMmon Boot Step Action 3. If the IOS file is the first file, enter the following command to display the contents of the startupconfig file:
show startupconfig
A response which begins similar to the following will be displayed:

BTSRTR1#sh start Using 1589 out of 57336 bytes ! version 12.2 service timestamps debug uptime service timestamps log uptime no service passwordencryption ! hostname BTSRTR1 ! boot system slot0:mwr1900imz.07132002.bin no logging console ! username cisco password 0 cisco ! redundancy mode ycable standalone !
13
Review the startupconfig file listing for a boot system line and perform the following: 1. If the startupconfig file does not contain a boot system line, skip to step 14. 2. If the file listing contains a boot system line, examine it for the correct IOS filename. 3. If the boot system slot0: filename is incorrect, enter the following, using care to type the filename correctly:
boot system slot0:IOS_filename
Where IOS_filename = the filename of the IOS noted in step 6, above. 4. Replace the boot system line in the startupconfig file with the line entered in substep 3, above, by entering the following:
copy runingconfig startupconfig
J
continued
Table J-11: Simple Recovery from BTS Router ROMmon Boot Step Action 5. Verify the correct IOS filename is now included in the listing by entering the following:
show startupconfig
A response which begins similar to the following will be displayed:

BTSRTR1#sh start Using 1589 out of 57336 bytes ! version 12.2 service timestamps debug uptime service timestamps log uptime no service passwordencryption ! hostname BTSRTR1 ! boot system slot0:mwr1900imz.1228.MC2b.bin no logging console ! username cisco password 0 cisco ! redundancy mode ycable standalone !
J
continued
Table J-11: Simple Recovery from BTS Router ROMmon Boot Step 14 Action Reverify the routers configuration register setting by entering the following:
show version

BTSRTR1#sh ver Cisco Internetwork Operating System Software IOS (tm) 1900 Software (MWR1900IM), Version 12.2(8)MC2b, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) TAC Support: http://www.cisco.com/tac Copyright (c) 19862002 by cisco Systems, Inc. Compiled Mon 05Aug02 11:07 by nmasa Image textbase: 0x60008940, database: 0x60B54000 ROM: System Bootstrap, Version 12.2(20020113:235343) [sbosewilma 109], DEVELOPMENT SOFTWARE ROM: 1900 Software (MWR1900IM), Version 12.2(8)MC2b, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) Router uptime is 1 minute System returned to ROM by poweron System image file is slot0:mwr1900imz.1228.MC2b.bin cisco mwr1900 (R7000) processor (revision 0.1) with 121856K/18432K bytes of memory. Processor board ID JMX0611K5TS R7000 CPU at 240Mhz, Implementation 39, Rev 3.3, 256KB L2 Cache Bridging software. X.25 software, Version 3.0.0. Primary Rate ISDN software, Version 1.1. Toaster processor tmc is running. 2 FastEthernet/IEEE 802.3 interface(s) 2 Serial network interface(s) 2 Channelized T1/PRI port(s) DRAM configuration is 64 bits wide with parity disabled. 55K bytes of nonvolatile configuration memory. 31360K bytes of ATA Slot0 CompactFlash (Read/Write) Configuration register is 0x101 BTSRTR1#
NOTE
The configuration register value is shown in the last line of the show version response. 15 If the value shown for the configuration register is 0x2102, skip to step 18. table continued on next page
J
continued
Table J-11: Simple Recovery from BTS Router ROMmon Boot Step 16 Action If the value shown for the configuration register is not 0x2102, enter the following command in the order shown to change it:
configure terminal configregister 0x2102

BTSRTR1#conf t Enter configuration commands, one per line. BTSRTR1(config)#configregister 0x2102 BTSRTR1(config)# End with CNTL/Z.
17
Verify the change was entered properly by entering the following commands in the order shown:
exit show version
A response which begins and ends similar to the following will be displayed:
BTSRTR1(config)#exit BTSRTR1#sh ver Cisco Internetwork Operating System Software IOS (tm) 1900 Software (MWR1900IM), Version 12.2(8)MC2b, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) TAC Support: http://www.cisco.com/tac Copyright (c) 19862002 by cisco Systems, Inc. . ...<output omitted>... . Configuration register is 0x101 (will be 0x2102 at next reload) BTSRTR1#
18
If the filename is correctly written in the boot system line (substep 5 of step 13) and the configuration register is properly set to the factory default of 0x2102, enter the following to determine if the router will reboot to IOS:
reload

J
continued
Table J-11: Simple Recovery from BTS Router ROMmon Boot Step 19 20 21 22 Action If prompted to save a modified configuration, enter n for no, and press the Enter key. When prompted to proceed with reload, press the Enter key to continue the reload operation. After a successful reboot with IOS, proceed with other BTS router activities or remove power from the router and disconnect it If the router still will not successfully boot with IOS, proceed to Table J-12 and perform the extended recovery procedure.
Extended Recovery from Boot to ROMmon
Requirements If ROMmon boot recovery attempts fail using the simple recovery method, this method must be used to reboot a BTS router which has initialized with ROMmon. This method requires additional equipment beyond the items necessary to load canned configuration files into the BTS router. Extended recovery requires formatting the CF memory card from the ROMmoninitialized router and reloading the reformatted CF memory card with the required IOS version. Additional equipment required An additional, formatted, 32 MB CF memory card with the required version of the IOS installed is required in addition to the equipment and software required for BTS router canned configuration installation. This card may be:
S A spare CF memory card which is loaded with the required IOS

version
S A CF memory card from an additional BTS router which is loaded

with the required IOS version Recovery Follow the procedure in Table J-12 to perform an extended recovery from a BTS router ROMmon initialization. Table J-12: Extended Recovery from BTS Router ROMmon Boot Step 1 Action This procedure assumes the BTS router is powered and operating on ROMmon with the LMF computer set up and connected to the router with an active HyperTerminal communication session. If it is not, follow the procedure in Table J-2 to establish a HyperTerminal communication session. Remove the CF memory card from the BTS router following the procedure in Table J-16. Install the additional CF memory card in the router following the procedure inTable J-17. table continued on next page
2 3
continued
Table J-12: Extended Recovery from BTS Router ROMmon Boot Step 4 Action Enter the following to obtain the filename of the IOS version loaded on the CF memory card:
dir slot0:

rommon 1 > dir slot0: program load complete, entry point: 0x80008000, size: 0xb2a0 Directory of slot0: 1 7051976 rw mwr1900imz.1228.MC2b.bin
rommon 2 >
Note the exact filename displayed for the IOS version. table continued on next page
J
continued
Table J-12: Extended Recovery from BTS Router ROMmon Boot Step 6 Action Enter the following to initialize the router with the IOS on the additional CF memory card:
boot slot0:IOS_filename
Where IOS_filename = the filename of the IOS noted in step 5, above. A successful IOS reboot operation will result in display of a response which begins and ends similar to the following:
rommon 2 > boot slot0:mwr1900imz.1228.MC2b.bin program load complete, entry point: 0x80008000, size: 0xb2a0 program load complete, entry point: 0x80008000, size: 0x6b99ac Self decompressing the image : ################################################################### [OK] Smart Init is enabled smart init is sizing iomem ID 00031A MEMORY_REQ TYPE
0X005F3C00 MWR1900 Mainboard 0X000F3BB0 public buffer pools 0X00211000 public particle pools
TOTAL: . . .
0X008F87B0
System Configuration Dialog Would you like to enter the initial configuration dialog? [yes/no]: n
7 8
If the router prompts with a question to enter the initial dialog as shown in step 6, above, type no and press the Enter key to obtain the user EXEC mode prompt. If the router prompts with Press RETURN to get started!, press the Enter key to obtain the user EXEC mode prompt. table continued on next page
J
continued
Table J-12: Extended Recovery from BTS Router ROMmon Boot Step 9 Action At the user EXEC mode prompt, enter the following to access the privileged EXEC mode:
enable

Router> enable Router#
10 11 12
Remove the additional CF memory card from the BTS router following the procedure in Table J-16. Install the original CF memory card in the router following the procedure inTable J-17. Format the original CF memory card by entering the following:
format slot0:

Router#format slot0: Format operation may take a while. Continue? [confirm]
13
Format operation may take a while. Continue? [confirm] Format operation will destroy all data in slot0:. Continue? [confirm]
J
continued
Table J-12: Extended Recovery from BTS Router ROMmon Boot Step 14 Action Press the Enter key to continue the format operation. A response similar to the following will be displayed:
Format operation will destroy all data in slot0:. Continue? [confirm] Format: Drive communication & 1st Sector Write OK... Writing Monlib sectors.................................................................... ................ Monlib write complete . Format: All system sectors written. OK... Format: Total sectors in formatted partition: 62560 Format: Total bytes in formatted partition: 32030720 Format: Operation completed successfully. Format of slot0 complete Router#
15 16
Copy the required IOS version to the formatted original CF memory card using the LMF computer and a tftp server following the procedure in Table J-9. If applicable, perform IOS initialization troubleshooting as described in Table J-11, steps 12 through 21.
J
Entering or Changing BTS Router FE Interface IP Addresses Entering or Changing BTS Router FE Interface IP Addresses
FE Interface IP Addresses and Operating Parameters
It may be necessary to enter or change the IP addresses and/or operating parameters for BTS router FE interfaces FE 0 and FE1 without making other changes in the router configuration files. Procedures in this section cover these operations.
Prerequisites
The following must be accomplished before entering or changing BTS router FE port IP addresses and/or operating parameters:
S The user has read and understands the content of MWR 1941DC
Wireless Mobile Edge Router Software Configuration Guide; part number 7813983 installed CF memory card
S BTS routers must have the required version of the IOS saved on their S BTS routers must have power applied, be operating without alarms
other than span alarms, and have completed bootup to the user EXEC mode prompt (BTSRTRbts#11>) from the network administrator
S The BTS router privileged EXEC mode password has been obtained
Entering or Changing FE Interface IP Addresses
To enter or change FE interface IP addresses, follow the procedure in Table J-13. Table J-13: Entering or Changing BTS Router FE Interface IP Addresses and Operating Parameters Step Action
* IMPORTANT
This procedure does not cover all aspects of BTS router operation and programming. Before performing this procedure, review BTS router initialization, operation, and programming information and procedures in MWR 1941DC Wireless Mobile Edge Router Software Configuration Guide; part number 7813983. Have this publication available for reference while performing this procedure. 1 2 3 Obtain the correct IP addresses and subnet masks for the BTS router FE interfaces from the network administrator. If a HyperTerminal connection for BTS card/module MMI or BTS router (BTSRTR) communication has not been created, create one as described in Table J-1 of this appendix. Connect the LMF computer to the BTS router, and start a communication session as described in Table J-2 in this appendix. table continued on next page
Entering or Changing BTS Router FE Interface IP Addresses
continued
Table J-13: Entering or Changing BTS Router FE Interface IP Addresses and Operating Parameters Step 4 Action
NOTE
Examples in this procedure show prompts for BTSRTRbts#11 and BTSRTRbts#12, but the procedure can be used for any router in any BTS router group or a router running the canned configuration file (BTSRTR1 or BTSRTR2). At the BTSRTRbts#11> user EXEC mode prompt, enter the following to access the privileged EXEC mode:
enable

BTSRTRbts#11> enable Password:
Enter the privileged EXEC mode password. A response similar to the following will be displayed:
BTSRTRbts#11> enable Password: BTSRTRbts#11#
At the BTSRTRbts#11# privileged EXEC mode prompt, display the FE interface IP addresses by typing:
show ip interface brief

BTSRTRbts#11# Interface FastEthernet0/0 Serial0:0 FastEthernet0/1 Serial1:0 BTSRTRbts#11# show ip interface IP Address OK? 192.168.146.1 YES unassigned YES unassigned YES unassigned YES brief Method NVRAM unset unset unset Status Protocol up up administratively down down administratively down down administratively down down
J
continued
Table J-13: Entering or Changing BTS Router FE Interface IP Addresses and Operating Parameters Step 7 Action For a FastEthernet0/0 (fa0/0) or FastEthernet0/1(fa0/1) interface which does not have a correct or an assigned IP address, enter the following at the router prompt to access the global configuration mode:
configure terminal

BTSRTRbts#11# conf t Enter configuration commands, one per line. End with CNTL/Z. BTSRTRbts#11(config)#
At the global configure mode prompt, enter the following to access the configure interface submode for the interface requiring IP address assignment/change:
interface fastethernetinterface#
Where interface# = 0/0 or 0/1, as applicable. A response similar to the following will be displayed:
BTSRTRbts#11(config)# int fa0/1
BTSRTRbts#11(configif)#
At the configure interface submode prompt, assign or change the interface IP address by entering:
ip address IP_addr subnet_mask
Where: IP_addr = the required IP address for the interface; for example, 192.168.147.1 subnet_mask = the required subnet mask for the interface; for example, 255.255.255.0 A response similar to the following will be displayed:
BTSRTRbts#11(configif)# BTSRTRbts#11(configif)# ip address 192.168.147.1 255.255.255.0
10
To complete configuration of the interface, enter the following parameter settings, one at a time, pressing Enter after each:
duplex full speed 100 keepalive 1 no shutdown
J
J-74 1X SC4812T CLPA BTS Optimization/ATP

SEP 2009
continued
Table J-13: Entering or Changing BTS Router FE Interface IP Addresses and Operating Parameters Step 11 Action Return to the global configuration mode by entering the following:
exit

BTSRTRbts#11(configif)# BTSRTRbts#11(config)# exit
12 13
If the IP address and/or parameters for the other FE interface on the router must be assigned or changed at this time, repeat steps 8 through 11 for the other FE interface. Once the correct parameters have been set for all FE interfaces, return to the privileged EXEC mode prompt by holding down the Ctrl key and pressing z (Ctrl +z). A response similar to the following will be displayed:
BTSRTRbts#11(configif)# ^z 01:11:27: %SYS5CONFIG_I: Configured from console by console BTSRTRbts#11#
NOTE
Entering exit twice, pressing the Enter key after each entry, will also complete the interface configuration and return the router to the privileged EXEC mode. 14 Save the interface configuration changes to the startup configuration file on the CF memory card by entering the following:
copy runningconfig startupconfig

BTSRTRbts#11# BTSRTRbts#11# copy run start Destination filename [startupconfig]?
15
Press Enter A response similar to the following will be displayed:

BTSRTRbts#11# copy run start BTSRTRbts#11# Destination filename [startupconfig]? Building configuration... !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!![OK] BTSRTRbts#11#
J
continued
Table J-13: Entering or Changing BTS Router FE Interface IP Addresses and Operating Parameters Step 16 Action If all FE IP address entries/changes for the router are complete, enter the following to return the router to user EXEC mode:
disable

BTSRTRbts#11# BTSRTRbts#11> disable
17 18 19 20
If no other router requires the FE interfaces to be assigned/changed, proceed to step 20. If FE interfaces on another router must be assigned/changed, disconnect the 8contact modular plug from the current router CONSOLE port and connect it to the CONSOLE port of the other router. Press the Enter key, and when the router user EXEC mode prompt appears repeat steps 3 through 16 for the other router. When the router is in user EXEC mode, close the HyperTerminal session and disconnect the LMF computer and additional components from the BTS router.
J
Example BTS Router Canned Configuration Files Example BTS Router Canned Configuration Files
BTS Router Canned Configuration File
This section presents listings of the blue and red router canned configuration file contents for the MWR 190027 and MWR 1941DC BTS routers. The blue router is the primary router on the BTS LAN subnet 192.168.146.0, and the red router is the primary on BTS LAN subnet 192.168.147.0. The canned configuration files allow communication with the BTS routers for both onsite FE cabling connectivity verification and for downloading the routers from the network with the full, sitespecific operational configuration.
Obtaining the Latest Configuration File Content
The files included here are for example only. The correct canned configuration file content for each BTS router should be generated at the OMCR using the /screl/active/bin/gen_btsrtr_canned_config.ksh script.
Configuration File Examples
Examples of both configuration files are provided in the following subsections.
J
Example BTS Router Canned Configuration Files

Blue BTS Router Canned Configuration
! Canned Config file for BTSRTR1 version 12.2 service timestamps debug uptime service timestamps log uptime no service passwordencryption ! hostname BTSRTR1 ! no logging console ! ! ip subnetzero ip classless ip pim bidirenable ! disableeadi memorysize iomem 25 ! redundancy mode ycable standby useinterface Loopback101 health standby useinterface Loopback102 revertive standby useinterface Multilink1 backhaul interface loopback 101 description BTSRTR health loopback no ip address interface loopback 102 description BTSRTR revertive loopback no ip address ! ! configure 1 DS0 for BTSRTRLINK ! controller T1 0/0 description 1st span on BTSRTR framing esf linecode b8zs cablelength short 133 clock source line channelgroup 0 timeslots 124 speed 64
continued
! MLPPP bundle with BTSRTRLINK. ! This performs IPCP with RPM when BTSRTR is rebooted interface Multilink 1 ip address negotiated no ip routecache no cdp enable ppp multilink
J
continued
multilinkgroup 1 no shutdown ! ! Setup Serial Interface for PPP and IPCP, no MLPPP at this time ! interface Serial0/0:0 no ip address encapsulation ppp keepalive 1 ppp multilink multilinkgroup 1 no shutdown ! ! Setup Ethernet Interfaces and HSRP between them ! interface FastEthernet0/0 ip address 192.168.146.1 255.255.255.0 keepalive 1 speed 100 fullduplex standby 1 timers 1 3 standby 1 preempt standby 1 priority 100 standby 1 ip 192.168.146.3 standby 1 name one standby 1 track Fa0/1 10 standby 1 track Multilink1 10 ! Track the router health interface standby 1 track Loopback101 10 ! Track the router revertive (compensation) interface standby 1 track Loopback102 5 no shutdown ! interface FastEthernet0/1 ip address 192.168.147.1 255.255.255.0 keepalive 1 speed 100 fullduplex standby 2 timers 1 3 standby 2 preempt standby 2 priority 100 standby 2 ip 192.168.147.3 standby 2 name two standby 2 track Fa0/0 10 standby 2 track Multilink1 10 ! Track the router health interface standby 2 track Loopback101 10 ! Track the router revertive (compensation) interface standby 2 track Loopback102 5 no shutdown ! ! Set a default route to RPM thru BTSRTRLINK ! SEP 2009 1X SC4812T CLPA BTS Optimization/ATP J-79

ip route 0.0.0.0 0.0.0.0 Multilink 1 ! line con 0 exectimeout 15 0 password cisco line aux 0 login password cisco line vty 0 4 login password cisco end
continued
J

Red BTS Router Canned Configuration
! Canned Config file for BTSRTR2 version 12.2 service timestamps debug uptime service timestamps log uptime no service passwordencryption ! hostname BTSRTR2 ! no logging console ! ! ip subnetzero ip classless ip pim bidirenable ! disableeadi memorysize iomem 25 ! redundancy mode ycable standby useinterface Loopback101 health standby useinterface Loopback102 revertive standby useinterface Multilink1 backhaul interface loopback 101 description BTSRTR health loopback no ip address interface loopback 102 description BTSRTR revertive loopback no ip address ! ! configure 1 DS0 for BTSRTRLINK ! controller T1 0/0 description 1st span on BTSRTR framing esf linecode b8zs cablelength short 133 clock source line channelgroup 0 timeslots 124 speed 64
continued
! MLPPP bundle with BTSRTRLINK. ! This performs IPCP with RPM when BTSRTR is rebooted interface Multilink 1 ip address negotiated no ip routecache no cdp enable
J
continued
ppp multilink multilinkgroup 1 no shutdown ! ! Setup Serial Interface for PPP and IPCP, no MLPPP at this time ! interface Serial0/0:0 no ip address encapsulation ppp keepalive 1 ppp multilink multilinkgroup 1 no shutdown ! ! Setup Ethernet Interfaces and HSRP between them ! interface FastEthernet0/0 ip address 192.168.146.2 255.255.255.0 keepalive 1 speed 100 fullduplex standby 1 timers 1 3 standby 1 preempt standby 1 priority 100 standby 1 ip 192.168.146.3 standby 1 name one standby 1 track Fa0/1 10 standby 1 track Multilink1 10 ! Track the router health interface standby 1 track Loopback101 10 ! Track the router revertive (compensation) interface standby 1 track Loopback102 5 no shutdown ! interface FastEthernet0/1 ip address 192.168.147.2 255.255.255.0 keepalive 1 speed 100 fullduplex standby 2 timers 1 3 standby 2 preempt standby 2 priority 100 standby 2 ip 192.168.147.3 standby 2 name two standby 2 track Fa0/0 10 standby 2 track Multilink1 10 ! Track the router health interface standby 2 track Loopback101 10 ! Track the router revertive (compensation) interface standby 2 track Loopback102 5 no shutdown ! ! Set a default route to RPM thru BTSRTRLINK J-82 1X SC4812T CLPA BTS Optimization/ATP SEP 2009

! ip route 0.0.0.0 0.0.0.0 Multilink 1 ! line con 0 exectimeout 15 0 password cisco line aux 0 login password cisco line vty 0 4 login password cisco end
continued
J
Network Interface Card (NIC) Configuration Worksheet Network Interface Card (NIC) Configuration Worksheet
Record of original NIC configuration
Advanced tab of NIC hardware Properties dialog box Table J-14: Advanced Tab Property List Box Connection Settings Original Operating System Windows XP Windows 2000 Property: Speed & Duplex Connection Type Internet Protocol (TCP/IP) Properties dialog box General tab ____ Obtain an IP address automatically ____ Use the following IP address: IP address: _______________________________ Subnet mask: _______________________________ Default Gateway: _______________________________
BTS router communication NIC configuration
Original Value:
Advanced tab of NIC hardware Properties dialog box Table J-15: Advanced Tab Property List Box Connection Settings for BTS Router Communication Operating System Windows XP Windows 2000 Property: Speed & Duplex Connection Type OTI Test Value: 100 Mb Full 100 Mbps Full_Duplex
Internet Protocol (TCP/IP) Properties dialog box General tab ____ Obtain an IP address automatically X Use the following IP address: 100.100.100.1 IP address: Subnet mask: 255.255.255.252
J
External BTS Router Compact Flash (CF) Memory Card Installation and Removal External BTS Router Compact Flash (CF) Memory Card Installation and Removal
CF Memory Card Installation/Removal Operations
Procedures in this section apply to the removal or installation of the external BTS router CF memory card
Tools Required
The following tools are required to perform procedures included in this section:
S Number 2 crossrecess screwdriver S Approved antistatic wrist strap or equivalent personal grounding
device Figure J-5: Router CF Memory Card Removal
CF Memory Card Cover
Card Ejector Lever
ACT LED
PUSH IN CF Memory Card
ROTATE OUT
Captive Screws
SC4812T0012
J
External BTS Router Compact Flash (CF) Memory Card Installation and Removal continued
BTS Router CF Memory Card Removal and Installation
The following procedures cover removal and installation of the CF memory card used to store the IOS and configuration data for the external BTS router. Removing a CF memory card Refer to Figure J-5 and follow the procedures in Table J-16 to remove the CF memory card from the external BTS router models. NOTE The CF memory card may be removed and installed while power is applied to the router.
Table J-16: External BTS Router Flash Memory Card Removal Step 1 Action Refer to MWR1941DC Mobile Wireless Edge Router Hardware Installation Guide; part number 7815827 for the latest information, cautions, and notes on BTS router CF memory card removal and installation prior to proceeding with the following steps.
! CAUTION
Do not remove the CF memory card while there are read or write operations occurring on the card. Removing the card during these operations will cause the router to shut down and damage the file system. If power is applied to the router, be sure there are no read or write operations in progress for the card by verifying the ACT indicator LED is not lighted or lighting intermittently.
3 4
Using a crossrecess screwdriver, fully loosen the captive screws securing the flash memory card slot cover to the router, and remove the cover. Remove the CF memory card by performing the following: 1. Rotate the end of the card ejector lever until it is pointing out 90_ to the router front panel (see Figure J-5). 2. Push the card ejector lever straight into the router to unseat the CF memory card. 3. Carefully pull the card out of the slot. Place the CF memory card on an antistatic surface or in an antistatic container.
J
Installing a Flash Memory Card Refer to Figure J-5 and follow the procedures in Table J-17 to install the CF memory card in an external BTS router Table J-17: External BTS Router Flash Memory Card Installation Step 1 Action Refer to MWR1941DC Mobile Wireless Edge Router Hardware Installation Guide; part number 7815827 for the latest information, cautions, and notes on BTS router CF memory card removal and installation prior to proceeding with the following steps. If the flash memory slot cover is installed, use a crossrecess screwdriver to fully loosen the captive screws securing the cover to the router, and remove the cover (see Figure J-5). Install the CF memory card by performing the following: 1. Hold the CF memory card with the label facing up and the connector end pointing toward the router. 2. Carefully insert the connector end into the flash memory card slot. 3. Push the CF memory card into the slot to seat it in the slot connector. The card ejector lever will extend out of the router as the card is seated. 4. Pull on the card ejector lever to fully extend it from the router, and rotate it to the left to its stowed position to latch the card in the slot (see Figure J-5).
2 3
J
Notes
J
Appendix K: MMI Cable Fabrication

Appendix Content
MMI Cable Fabrication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cable Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wire Run List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K-1 K-1 K-1 K-1 K-2
SEP 2009
Table of Contents
continued
Notes
SEP 2009
MMI Cable Fabrication MMI Cable Fabrication

Purpose
When the Motorola SLN2006A MMI Interface Kit is not available, a cable can be fabricated by the user to interface a ninepin serial connector on an LMF computer platform with an MMI connector on GLI cards and other Motorola BTS assemblies. This section provides information necessary for fabricating this cable.
Required Parts
Table K-1: Parts Required to Fabricate MMI Cable Item A B Part Number Motorola 3009786R01 AMP 7498141, Belkin A4B202BGC, or equivalent Qty 1 1 Description Ribbon cable assembly, 1.524 M, one 8contact MMI connector, one 10contact connector Receptacle kit, unassembled, 9position, socket contacts, unshielded, metal or plastic shell, solder or crimptype contacts
Cable Details
Figure K-1 illustrates the details of the fabricated MMI cable.
Figure K-1: Fabricated MMI Cable Details
8Contact MMI Plug Socket Numbering (Mating Side) 1 3 5 7
Item B
DB9 Plug Socket Numbering (Mating Side) 5 4 3 2 1
2 4 6 8 9 Item A: Cable assembly 3009786R01 (with 10contact plug removed) 8 7 6
FABRICATION NOTES: 1. Remove 10contact connector from ribbon cable of cable assembly 3009786R01 2. Separate wires at unterminated end of ribbon cable as required to connect to DB9 connector contacts 3. Dark wire on ribbon cable of cable assembly 3009786R01 connects to pin 1 of the 8contact plug 4. Strip three ribbon cable wires with connections specified in Table K-2 and connect to DB9 plug contacts as specified in Table K-2 5. Shorten unconnected ribbon cable wires enough to prevent contacting DB9 contacts, leaving enough wire to egage any strain relief in the DB9 connector shell
MMIFAB0010
SEP 2009
K-1
MMI Cable Fabrication

Wire Run List
continued
Table K-2 provides the wire run/pinout information for the fabricated MMI cable. Table K-2: Fabricated MMI Cable Wire Run List 8CONTACT MMI PLUG CONTACT 1 2 3 4 5 6 7 8 5 2 3 No Connection (NC) NC NC NC NC DB9 PLUG CONTACT
K-2
SEP 2009
Appendix L: OTI Configuration Support Operations

Appendix Content
OTI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS edge device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Computer Network Interface Card (NIC) for OTI Verification . . . . . OTI Link Confidence Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing the check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
L-1 L-1 L-2 L-5 L-5
SEP 2009
Table of Contents
continued
Notes
SEP 2009
OTI Overview OTI Overview

OTI employs the packet BTS Ethernet transport interface to provide customers an alternative to spantype transport. Customers can select the most costeffective highspeed IP Wide Area Network (WAN) available to them for use as backhaul between base stations and base station controllers. A Radio Access Network (RAN) can employ a mix of base stations equipped with span backhaul and OTIequipped base stations at the same time. Figure L-1: OTI Base Station Functional Block Diagram
ETHERNET CABLING
(CUSTOMERSUPPLIED; BTS EXTERNAL INTERFACE TO EDGE DEVICE)
(CONNECTS TO CUSTOMER WAN DEMARCATION)
OTI WAN
BTS
(WITH GLI3 CARDS)
BTS EDGE DEVICE

(CUSTOMERSUPPLIED; PROVIDES ETHERNET CONNECTIONS TO BTS)
BTS EXTERNAL ETHERNET INTERFACE

(ESM)
BTS edge device
At the base station site, the enabler for OTI is the edge device. This is a customerprovided device which serves as the interface between the base station 10/100BaseTX Fast Ethernet (FE) LAN and the customerselected IP transport technology (Figure L-1).
SEP 2009
L-1
Configure Computer Network Interface Card (NIC) for OTI Verification Configure Computer Network Interface Card (NIC) for OTI Verification
L
Perform the following procedure to configure the computer NIC to support TCP/IP operations in the OTI verification process. NOTE If the IP address for the LAN connection on a WinLMF computer is being changed using this procedure, the BTS 10base2 LAN IP address and subnet mask for the NIC must be restored before the WinLMF can log into a BTS to perform an optimization or ATP. NOTE There are differences between the various operating systems supported on the WinLMF computer in the menus and screens used for setting or changing a NIC connection. In the following procedure, items unique to: S Windows XP operating system will be identified with WinXP
S Windows 2000 operating system will be identified with

Win2000
Table L-1: Configure Computer NIC for OTI Verification Step 1 2 3 Start the computer. Login and allow the computer to boot to the desktop. Depending on the installed operating system, from the Windows operating system Start menu, select one of the following: Action
S WinXP: Settings > Network Connections S Win2000: Settings > Network and Dialup Connections
4 5 In the list of displayed connections, locate the Local Area Network connection for the NIC to be used. Perform the following: 1. Highlight the connection for the NIC 2. Right click the highlighted connection 3. Select Properties from the popup menu. In the Local Area Connection Properties dialog box which appears, if Internet Protocol (TCP/IP) is not showing in the Components checked are used by this connection: (Win2000) or The connection uses the following items: (WinXP) listbox, refer to the operating system documentation and install TCP/IP. If the checkbox next to the Internet Protocol (TCP/IP) entry is not checked, click in the box to check it. table continued on next page
L-2 1X SC4812T CLPA BTS Optimization/ATP SEP 2009
Configure Computer Network Interface Card (NIC) for OTI Verification

continued Table L-1: Configure Computer NIC for OTI Verification Step 8 9 10 Action Click the Configure button under the Connect using: list box at the top of the General tab. In the Properties dialog box for the NIC hardware, click the Advanced tab to bring it to the front. Perform one of the following as applicable for the installed operating system:
S For Win2000:
In the Property: listbox, highlight Connection Type. Note the setting in the Value: list box, and record it in Table 5-24 of the Network Interface Card (NIC) Configuration Worksheet (see the end of Chapter 5). From the Value: listbox dropdown menu, select 100 Mbps Full_Duplex. Click OK.
S For WinXP:
In the Property: listbox, highlight Speed & Duplex. Note the setting in the Value: list box, and record it in Table 5-24 of the Network Interface Card (NIC) Configuration Worksheet (see the end of Chapter 5). From the Value: listbox dropdown menu, select 100 Mb Full. Click OK. 11 Perform one of the following:
S Win2000:
Highlight the Internet Protocol (TCP/IP) entry. Cick on the Properties button below the Components checked are used by this connection:.
S WinXP:
Highlight the Internet Protocol (TCP/IP) entry. Cick on the Properties button below the The connection uses the following items: listbox. 12 In the Internet Protocol (TCP/IP) Properties dialog box which appears, perform the following: 1. Note all settings on the General tab, and record them in the Record of original NIC configuration subsection of the Network Interface Card (NIC) Configuration Worksheet (see the end of Chapter 5). 2. If a black dot is not showing in the the radio button circle next to Use the following IP address:, click on the radio button. A black dot will appear in the circle. 3. Refer to Table 5-23 of the Network Interface Card (NIC) Configuration Worksheet, and enter the OTI test setting values as indicated for the following under Use the following IP address: : IP address: box: <OTI_BTSRTRGRP_IP_addr> Subnet mask: box: <OTI_Network_Mask> Default Gateway: box: <MLS_OTI_CON_HSRP_Logical_Addr > table continued on next page
SEP 2009
L-3
Configure Computer Network Interface Card (NIC) for OTI Verification

continued Table L-1: Configure Computer NIC for OTI Verification
Step 13 14
Action Click OK for the Internet Protocol (TCP/IP) Properties dialog box. Click the OK button for the Local Area Connection Properties box.
L-4
SEP 2009
OTI Link Confidence Check OTI Link Confidence Check

Acquisition, installation, certification, and maintenance of the BTS edge device and the associated WAN for control and bearer traffic transport is the responsibility of the customer. Before connecting the BTS edge device to the BTS external Ethernet interface, however, a check of the edge device, interconnecting cabling for the BTS, and connectivity with the RAN core router should be performed to provide confidence that the BTS will be able to communicate with the RAN.
Performing the check
Perform the following to accomplish an operational confidence check of the network operatorprovided OTI link. This procedure also verifies the BTS edge device cable connections. Table L-2: OTI Link Confidence Check Step 1 2 3 4 Action Be sure the WinLMF computer is booted to the desktop. If it has not been done, configure the WinLMF computer for TCP/IP operations in support of OTI testing by following the procedure in Table L-1 of this appendix. Open a command line interface (CLI) window on the computer (Start > Programs > Accessories > Command Prompt). Enter the following command at the command prompt:
ipconfig /all
5 6
Locate the completed Network Interface Card (NIC) configuration worksheet for the site. Verify that the settings for the following match those in the OTI verification NIC configuration subsection of the worksheet: IP Address Subnet Mask Default Gateway Leave the command line window open and proceed to step 8. Locate the Ethernet cables provided for connecting the BTS edge device with the BTS external Ethernet interface. If one end of each required cable is already connected to the BTS edge device: 1. Refer to site documentation, and verify that each cable is connected to the correct edge device connector 2. Skip to step 11. Refer to the site documentation, and connect one end of each required cable to each of the BTS edge device Ethernet connectors specified for BTS connection. table continued on next page
7 8 9
10
SEP 2009
L-5
OTI Link Confidence Check
continued
Table L-2: OTI Link Confidence Check
Step 11 12 13
Action Connect the other end of one cable to the computer NIC Ethernet connector. Verify Ethernet connectivity between the computer and BTS edge device by observing that the link lights for both the WinLMF computer NIC and the BTS edge device are lighted. In the command line window, ping the Default Gateway IP address using the following command (refer to the completed OTI configuration settings worksheet for the IP address):
ping <MLS_OTI_CON_HSRP_Logical_Addr>
14 15 16 17
Verify communication between the computer and the BTS edge device by observing that the activity light on the BTS edge device flickers at each ping attempt from the computer. Disconnect the BTS edge device cable from the WinLMF computer NIC. Repeat steps 11 through15 for each remaining Ethernet cable on the BTS edge device which will be connected to the BTS external Ethernet interface. When all BTS edge device cables and connectors required by the site documentation have been checked, disconnect the WinLMF computer from the BTS edge device.
NOTE
All Ethernet cables should remain connected to the BTS edge device connectors. 18 After successfully pinging the Default Gateway router on each edge device port to be used, reconfigure the WinLMF computer NIC with the original NIC settings recorded when filling out the Network Interface Card (NIC) configuration worksheet.
! CAUTION
If the BTS 10base2 LAN IP address and subnet mask for the WinLMF computers NIC are not restored, the WinLMF can not log into a BTS when attempting to perform a BTS optimization or ATP.
L-6
SEP 2009
Index
Numbers
100BaseT connectors, GLI, 7-43 10BaseT/10Base2 Converter, 1-9 2way Splitter, 1-14 3CPCCOMBO CBL, 1-10
Alarm Reporting Display, 3-136 Alarm tests, redundancy, 3-127 Alarm/Redundancy Tests, Distribution Shelf, 3-130 All Cal/Audit procedure, 3-120 All RX, 4-3 All TX, 4-3 All TX/RX, 4-3 AMR, No control, 7-20 AMR CDI Alarm Input Verification, test data sheets, A-16 Ancillary frame, when to optimize, C-1 Anritsu MT8212B ATP alternate test setup, 3-81 TX and RX test setup, 3-78 Calibrating CW generator, 3-96 power meter zeroing, 3-94 TX analyzer, 3-95 test equipment interconnection, 3-68 TX calibration, test setup, 3-73 Antenna connections, 4-5 ATP Code Domain Power, 4-14 , 4-15 Frame Error Rate (FER), 4-16 generate report, 4-19 Pilot Time Offset, 4-13 Report, 4-19 test matrix/detailed optimization, C-2 Test Prerequisites, 4-4 Test Procedure, 4-6 test setup, Advantest R3267/R3562, DRDCs, 3-76 automated calibration file transfer, 6-1 process description, 6-1 GLI3 and LMF actions flowchart, 6-3
Index-1
A
ACTIVE LED GLI, 7-42 MCC, 7-45 Advantest R3267, GPIB Address, F-5 Advantest R3465, 3-64 Calibrating Test Cable, F-1 , F-24 Advantest R3465 Communications Test Set GPIB Address, F-7 Advantest R3562, GPIB Address, F-8 Agilent 8935 Series E6380 (formerly HP 8935) Test Set GPIB Address, F-9 Agilent E4406A calibration, F-1 , F-22 GPIB Address, F-11 Agilent E4418 power meter, GPIB address, setting, F-13 Agilent E4438C Signal Generator, GPIB Address, F-15 Agilent E7495 calibration, power sensor, F-3 IP address, setting, F-2 Alarm Connector Location/Pin, 3-137 ALARM LED, GLI, 7-43 Alarm Monitor window, 3-136 alarm redundancy tests, BBX, 3-131
SEP 2009
Index
continued
user and LMF actions flowchart, 6-2 upload procedure, 6-4
BTSRTR, 1-17 BTSRTRGRP, 1-17
B
backhaul, packet OTI, 5-33 satellite, 7-33 Bay Level Offset calibration failure, 7-8 BBX alarm redundancy tests, 3-131 Connector, 7-18 gain set point vs BTS output considerations, D-1 No control in the shelf, 7-20 BLO Calibration, 3-112 defined, 3-113 Calibration Audit, 3-124 calibration data file, 3-114 Calibration Failure, 7-8 Download, 3-123 BPR, 1-17 Breaker Panel, 2-8 BSS, 1-17 BTS Ethernet LAN interconnect diagram, 3-34 system software download, 3-3 test data sheets, redundancy/alarm tests, A-15 when to optimize, C-1 BTS frame, initial powerup, 2-11 BTS Packet Router, BPR, 1-17 BTS Router change or upgrade IOS version, J-35 communication session, J-5 download configuration files, minimum canned, J-8 IOS verification, canned config installation, J-15 IOS version verification file sequence position, J-36 required equipment and software, J-35 TFTP server, CF memory card load, J-17 BTS router communication session, establishing, J-6 BTS router connections FE verification, J-7 programming, J-7 Create CAL File, 3-125
Index-2
C
CCCP Backplane, Troubleshooting, 7-17 , 7-19 CCCP Shelf, 1-27 Site Serial Number Check List, A-17 Cable GPIB, 1-12 LAN Cable, 1-13 Calibrating, 3-100 Setting Loss Values, 3-110 Timimg Reference, 1-12 Cable Calibration, Manual, 3-69 , 3-107 cable calibration, automatic, test setup, Agilent E4406A/E4432B, 3-104 Cable Calibration Setup, Automatic, 3-69 , 3-101 Cable calibration setup, diagrams, 3-101 cabling, Fast Ethernet, required cables, BTSRTRtoframe, 5-27 CAL File, create, 3-125 Calibrate Test Cabling, Communications System Analyzer, 3-101 Calibrating Cables, 3-100 Test Equipment, 3-93 Anritsu MT8212B, 3-94 manual, 3-93 Calibrating Test Cable, Advantest R3465, F-1 , F-24 Calibrating Test Cabling, Signal Generator & Spectrum Analyzer, 3-107 Calibration BLO, 3-113 Cable, 1-8 data file, BLO, 3-114 InService, I-13 Process, 3-1 RF Path, Test Equipment Setup, 3-117 Test Equipment, 1-8 TX Path, 3-113 , 3-117 Test Cable Calibration, 1-8 Test Equipment Calibration, 1-8 calibration, Gigatronics 8542B, F-1 , F-23 Calibration Audit Failure, Troubleshooting, 7-9
Index
continued
Calibration data, Generator, 3-98 edit, 3-98 set, 3-98 Calibration Procedures Included, Automatic, 3-93 Cannot communicate to Communications Analyzer, 7-4 Cannot communicate to Power Meter, 7-3 Cannot download CODE to any device card, 7-5 Cannot Download DATA to any device card, 7-6 Cannot ENABLE device, 7-6 Cannot load BLO, 7-8 Cannot Log into cellsite, 7-2 Cannot perform Code Domain Noise Power measurement, 7-12 Cannot perform Rho or pilot time offset measurement, 7-11 Cannot perform Txmask measurement, 7-11 CDI Alarm with Alarms Test Box, 3-139 without Alarms Test Box, 3-141 CDMA, allocation diagram for the North American, cellular telephone frequency spectrum, E-5 CDMA LMF, Product Description, 1-9 Cell Site equipage verification, 2-2 preliminary operations, 2-1 types, 3-2 CEPT, 1-17 CF, 1-17 CF Memory Card, load using a TFTP server, J-17 CF memory card, installation and removal, J-85 Channel elements, No or missing, 7-21 CLI, 3-24 Command Line Interface, 3-18 Format Conventions, 3-24 Logging Out, 3-30 CLPA, 1-29 , 1-31 , 2-11 Code Domain Power, ATP, 4-14 , 4-15 Code Domain Power and Noise Floor Measurement Failure, Troubleshooting, 7-12 Code Domain Power Test, 4-14
SEP 2009
Code Download Failure, Troubleshooting, 7-5 Command Line Interface, 3-24 command terminal, settings, 3-11 , J-2 Common power supply verification, 2-10 Communication Session, BTS Router, J-5 Communications Analyzer Communication Failure, Troubleshooting, 7-4 Communications System Analyzer, 1-11 Communications test set. See Test equipment communications test set, TX acceptance tests, 4-3 Configuration, 1-19 BTS Router, IOS verification, J-15 OMCR FTP file transfer, J-9 operations overview, BTS Router, J-1 Connector Functionality, Backplane, Troubleshooting, 7-17 Copy NEC Files from OMCR, 3-8 CSM Clock Source, 3-46 clock source, select, 3-46 Enable, 3-47 LEDs, 3-51 MMI terminal connection, illustration, 3-55 redundancy/alarm tests, 3-132 Reference Source Configuration Error, 7-16 system description, 3-50 Troubleshooting, 7-15 , 7-16 CSM clock source, select, 3-46 CSM frequency verification, 3-54
D
Data Download Failure, Troubleshooting, 7-6 DC Power Pretest, BTS Frame, 2-6 DC Power Problems, 7-22 DC/DC Converter, LED Status Combinations, 7-40 Device Enable (INS) Failure, Troubleshooting, 7-6 Digital Control Problems, CCCP Backplane Troubleshooting, 7-19 Digital Multimeter, 1-12 Directional Coupler, 1-12 Distribution shelf, alarm/redundancy tests, 3-130 Download BLO, 3-123
Index-3
Index
continued
BTS system software, 3-3 NonGLI2 Devices, 3-43 ROM Code, H-1 Duplex Router, 1-18
General optimization checklist, test data sheets, A-4 Gigatronics 8542 power meter, calibration, F-1 , F-23 Gigatronics 8542B power meter, illustration, F-17 Gigatronics Power Meter, 3-64 GLI LED Status, 7-42 No Control through span line connection, 7-20 No Control via LMF, 7-19 redundancy test RFM frame, 3-135 WinLMF code load, packet mode, 3-40 GLI2 Connector, 7-18 Ethernet Connections, 7-18 GLI3 backhaul mode, satellite, 7-33 backhaul mode change required, 5-8 configure for EBR, 5-27 configure for IBR, 5-12 IBR full span, 5-15 configure for OTI, 5-33 determining, 5-5 IBR fractional span, 5-20 backhaul modes, 5-4 code loading operating mode effect, 5-3 preload procedure, 5-10 recommended procedure, 5-4 code version change required, 5-8 determining, 5-5 GPIB, power meter, Gigatronics 8542B, F-17 GPIB Cable, 1-12 GPIB Address Advantest R3267, F-5 Advantest R3465, F-7 Advantest R3562, F-8 Agilent (formerly HP) 8935, F-9 Agilent E4406A, F-11 Agilent E4438C, F-15 GPS receiver operation, test data sheets, A-5 redundancy alarm tests, 3-132 Test Equipment Setup, 3-54 GPS Initialization/Verification estimated position accuracy, 3-55
E
E4406A, calibration, F-1 , F-22 EBR, configure GLI3, 5-27 edge device, BTS, L-1 Enable CSMs, 3-47 MCCs, 3-49 establish MMI communication, 3-31 Ethernet LAN hub, 1-9 interconnect diagram, 3-34 switch, 1-9 External BTS Router CF memory card installation, J-85 removal, J-85 memory card installation, J-85 removal, J-85 External Test Equipment Removal, 6-5
F
Fast Ethernet (FE) connectors, GLI, 7-43 FE, 1-18 FE Verification, preliminary actions, 5-35 FER test, 4-16 file transfer protocol, configuring for, 5-46 Folder Structure Overview, 3-5 Frame Error Rate, 4-8 , 4-9 ATP, 4-16 FREQ Monitor Connector, CSM, 7-41 Frequency counter, optional test equipment, 1-14 Full Optimization, 4-3
G
Gain set point, BBX, D-1
Index-4
Index
continued
surveyed position accuracy, 3-55 GPS satellite system, 3-48 Graphical User Interface, 3-19 GUI, 3-19 Graphical User Interface, 3-18 Logging Out, 3-29
CSM, 3-51 , 7-41 DC/DC Converter, 7-40 GLI, 7-42 MCC, 7-45 PA, 7-45 LFR/HSO, Test Equipment Setup, 3-54 LIF, Load Information File, 3-6 LMF, 3-4 1X FER acceptance test, 4-3 Installation and Update Procedures, 3-7 loading code, packet GLI3, 3-40 Termination and Removal, 6-10 TX acceptance tests, 4-3 LMF BTS displays, 3-19 LMF Home Directory, 3-6 LMF Operation, 3-18 LMF Removal, 6-10 Load Information File, 3-6 Logging In to a BTS, 3-25 Logging Out, 3-29 CLI, 3-30 GUI, 3-29 Logical BTS, 1-21 Numbering, 1-21 Login CLI, 3-28 GUI, 3-26 Login Failure, Troubleshooting, 7-2 LORANC Initialization/Verification, 3-61 LPA, 1-31 redundancy test, 3-133 test data sheets convergence, A-7 IM Reduction, A-6 LPA Configurations, 32 W, 1-30 LPAs, Site Serial Number Check List, A-18
H
LMF Hardware Requirements, 1-9 High Availability BTS Router, 1-18 High Stability 10 MHz Rubidium Standard, 1-14 Highimpedance Conductive Wrist Strap, 1-13 HP 8935, 3-64 HSO, redundancy/alarm tests, 3-132 HyperTerminal Connection, Creating, 3-11
I
I and Q values, B-1 IBR, configure GLI3, 5-12 IBR Span Configuration Verification, 6-5 InService Calibration, I-13 Initial Installation of Boards/Modules, preliminary operations, 2-2 Initial power tests, test data sheets, A-3 Initial powerup, BTS frame, 2-11 Intended reader profile, 1-2 Interframe cabling, when to optimize, C-2 IOS Version, change or upgrade, BTS Router, J-35 IP Addresses, Agilent E7495A, 3-84 IS97 specification, B-1 ISB connectors, 7-17 Itasca Alarms Test Box, 1-14
L
LAN BTS frame interconnect, illustration, 3-34 Tester, 1-14 LED Status, 7-40 BBX, 7-45
SEP 2009
M
MCC, Enable, 3-49 MCIO, Connectors, 7-18 Miscellaneous errors, Troubleshooting, 7-6 MMI Connection, 3-31 fabricated MMI cable, 3-32
1X SC4812T CLPA BTS Optimization/ATP Index-5
Index
continued
MMI Connector CSM, 7-42 GLI, 7-43 MCC, 7-46 MMI equipment setup cable CGDSMMICABLE219112, 3-32 Kit SLN2006A, 3-32 Module status indicators, 7-40 MultiFER test Failure, Troubleshooting, 7-14 MWR 1900 BTS Router, configuration overview, J-1
OTI configure GLI3, 5-33 edge device, L-1 link confidence check, L-5 OTI link, confidence check, L-5
P
PA Module LED, 7-45 PA Shelf, 1-29 Packet Backhaul, defined, 1-19 Periodic optimization, 1-7 Pilot Gain, 4-12 , 4-13 , 4-14 , 4-16 Pilot Offset Acceptance test, 4-13 Pilot Time Offset, 4-8 , 4-13 Pin/Signal Information for ARM A Cable, 3-143 Ping, 3-34 PN Offset programming information, B-1 usage, B-1 PnMask, I and PnMask Q Values, B-2 Power Delta Calibration Advantest, I-2 HP8935, I-5 Power Input, 7-17 Power meter GPIB, Gigatronics 8542B, F-17 illustration, Gigatronics 8542B, F-17 TX acceptance tests, 4-3 Power Meter Communication Failure, Troubleshooting, 7-3 Power supply, converter redundancy, 3-128 Power Supply Interface, 7-18 power supply/converter redundancy, 3-128 Prepower tests, test data sheets, A-3 Preliminary operations cell Site types, 2-1 test data sheets, A-2 Prepare to Leave the Site External Test Equipment Removal, 6-5 IBR Span Configuration Verification, 6-5 LMF Removal, 6-10 Reconnect BTS Span Cables and Integrated Frame Modem, 6-10
SEP 2009
N
NEC site equipage verification, 3-3 site type and equipage data information, 2-1 NECF, 3-2 network, transport configuration, 5-1 determine code version, 5-5 determine GLI3 backhaul mode, 5-5 FTP, 5-44 security, 5-44 SFTP, 5-44 software release requirements, 5-3 Network Element Configuration file, 2-1 New installations, 1-5 NIC configuration, OTI verification, L-2 No DC input voltage to Power Supply Module, 7-22 No DC voltage +5 +65 or +15 Volts to a specific GLI, BBX, or Switch board, 7-23 No GPS Reference Source, 7-15 NonGLI, Download, 3-43 North American, cellular telephone system frequency spectrum, CDMA allocation, E-5
O
OMCR, FTP file transfer procedure, J-9 Online Help, 3-18 , 3-33 Optimization/ATP Setup, 3-74 Optional Test Equipment, frequency counter, 1-14 Oscilloscope, 1-14
Index-6
Index
continued
Reset All Devices and Initialize Site Remotely, 6-11 publications, required for upgrade, 1-15 Pushbuttons and Connectors, GLI, 7-43 PWR/ALM LED BBX, 7-45 CSM, 3-51 DC/DC Converter, 7-40 generic, 7-40 MCC, 7-45
antenna VSWR, test data sheets, A-16 RX Acceptance Tests Frame Error Rate, 4-8 , 4-9 RSSI, 4-9 RX path. See receive path
S
secure file transport protocol, configuring for, 5-46 Setting Cable Loss Values, 3-110 Setting TX Coupler Loss Value, 3-111 Setup for Optimization/ATP, 3-74 Signal Generator, 3-108 signal generator, 1X FER acceptance test, 4-3 Simplex Router, defined, 1-20 Site, equipage verification, 3-3 Site checklist, data sheets, A-2 Site equipage, NECF, 3-2 Site expansion, 1-6 Site I/O board, modem cable connection, 6-11 span I/O card, span connection, 6-11 Span Line connector , 7-17 T1/E1 Verification Equipment, 1-14 Span line, troubleshooting, 7-24 Span line configuration, troubleshooting, 7-27 Span line traffic, No or missing, 7-21 SPANS LED, GLI, 7-43 Spectral Purity TX Mask, 4-8 Spectrum Analyzer, 1-14 , 3-108 Spectrum Analyzer , HP8594E, 3-64 STATUS LED, GLI, 7-43 SYNC Monitor Connector, CSM, 7-41
R
RDM, 7-17 Reconnect BTS Spans, 6-10 Reconnect Integrated Frame Modem, 6-10 receive path calibration, 3-112 definition, 3-112 Receive Signal Strength Indication, 4-9 procedure, 4-17 testing, 4-18 Reduced ATP, 4-2 , 7-10 redundancy/alarm tests, 3-127 Reference Distribution Module, 7-17 Required documents, 1-15 Required test equipment, communications system analyzer, 1-11 Reset All Devices and Initialize Site Remotely, 6-11 RESET Pushbutton, GLI, 7-43 RF Adapters, 1-13 Load, 1-12 RF Path Calibration, 3-117 rho test, 4-12 ROM Code, Download, H-1 rommon, 1-20 RS232 to GPIB Interface, 1-10 RS232 GPIB Interface Box, F-18 RSSI, 4-9 RX acceptance tests, RSSI, 4-17
SEP 2009
T
terminal communication settings, 3-11 , J-2 Terminal Session, setup, BTS Router, J-2 Test data sheets AMR CDI Alarm Input Verification, A-16 BTS redundancy/alarm tests, A-15 general optimization checklist, A-4
1X SC4812T CLPA BTS Optimization/ATP Index-7
Index
continued
GPS receiver operation, A-5 initial power tests, A-3 LPA convergence, A-7 IM Reduction, A-6 prepower tests, A-3 preliminary operations, A-2 RX antenna VSWR, A-16 site checklist, A-2 TX antenna VSWR, A-15 TX BLO Offset/Power Output Verification, A-8 Power Output Verification, A-13 Test Equipment Automatically Selecting, 3-87 , 3-88 , 3-90 Calibrating Anritsu MT8212B, 3-94 automated, 3-93 manual, 3-93 Connecting test equipment to the BTS, 3-63 Connection Chart, 3-65 Selecting, 3-85 verification data sheets, A-1 VSWR, G-1 Test equipment See also Optional test equipment; Required test equipment system analyzer, 1-11 TX acceptance tests, 4-3 test equipment connection Ethernet, 3-83 GPIB addresses, 3-84 COM port, 3-82 Serial addresses, 3-84 COM port, 3-82 test equipment selection Ethernet automatic selection, 3-90 manual selection, 3-90 prequisites, 3-89 GPIB automatic selection, 3-87 manual selection, 3-86 prerequisites, 3-85 network automatic selection, 3-90 manual selection, 3-90
Index-8
prerequisites, 3-89 serial automatic selection, 3-88 manual selection, 3-88 prerequisites, 3-88 Test Equipment Setup GPS & LFR/HSO, 3-54 RF path calibration, 3-117 Test Matrix, C-4 ATP optimization, C-2 Test Set Calibration , Background, 3-92 TFTP, loading a CF memory card procedure, J-17 Timing Reference Cables, 1-12 timing reference sources, 3-52 Top Interconnect Plate, 1-25 transmit path calibration, 3-112 definition, 3-112 transport configuration, introduction, 5-1 Troubleshooting BBX Control Good No (or Missing) Span Line Traffic, 7-21 BLO Calibration Failure, 7-8 CCCP Backplane, 7-17 , 7-19 Calibration Audit Failure, 7-9 Code Domain Power and Noise Floor Measurement Failure, 7-12 Code Download Failure, 7-5 Communications Analyzer Communication Failure, 7-4 Data Download Failure, 7-6 DC Power Problems, 7-22 Device Enable (INS) Failure, 7-6 Login Failure, 7-2 MGLI Control Good No Control over AMR, 7-20 MGLI Control Good No Control over Colocated GLI2, 7-20 Miscellaneous Failures, 7-7 MultiFER Failure, 7-14 No BBX Control in the Shelf No Control over Colocated GLIs, 7-21 No DC Input Voltage to any CCCP Shelf Module, 7-23 No DC Input Voltage to Power Supply Module, 7-22 No GLI Control through Span Line Connection, 7-20
SEP 2009
Index
continued
No GLI Control via LMF, 7-19 No MCC Channel Elements, 7-21 Power Meter Communication Failure, 7-3 Rho and Pilot Time Offset Measurement Failure, 7-11 Set span configuration, 7-27 span problems, 7-24 TX and RX Signal Routing, 7-23 TX Mask Measurement Failure, 7-11 troubleshooting, backhaul, satellite, 7-33 TX acceptance tests, equipment setup, 4-3 antenna VSWR, test data sheets, A-15 TX and RX Frequency vs Channel , E-3 TX and RX Signal Routing, CCCP Backplane Troubleshooting, 7-23 TX Audit Test, 3-124 TX BLO, test data sheets Offset/Power Output Verification, A-8 Power Output Verification, A-13 TX calibration, 3-120 All Cal/Audit, 3-120 TX Mask test, 4-10 TX Mask Verification, spectrum analyzer display, illustration, 4-11 TX Output Acceptance Tests Code domain power, 4-14 Pilot Time Offset, 4-8 , 4-13 Spectral purity TX mask, 4-8 Waveform quality (rho), 4-8 , 4-12 TX Path, calibration, 3-113 TX path See also transmit path
audit, 3-124 calibration, 3-117 TX path calibration, 3-120
U
updating calibration data files, automated, 6-1
V
Verification of Test Equipment, data sheets, A-1 Voltage Standing Wave Ratio. See VSWR VSWR Advantest Test Set, G-1 Calculation, G-3 Equation, G-3 manual test setup detail, Advantest illustration, G-3 required test equipment, G-1 transmit and receive antenna, G-1
W
Walsh channels, 4-14 Warmup, 1-8 Warmup Equipment, 3-68 Waveform Quality (rho), 4-8 When to optimize Ancillary table, C-1 BTS, C-1 interframe cabling, C-2 WIC, 1-20 worksheet, software release and backhaul mode, 5-48
SEP 2009
Index-9
Index
continued
Notes
Index-10
SEP 2009
*68P09293A66A*
68P09293A66A
Technical Information
1X SC4812T CLPA BTS OPTIMIZATION/ATP
SOFTWARE RELEASE 2.22.0.X 800 AND 1900 MHZ CDMA2000 1X
ENGLISH SEP 2009 68P09293A66A
SOFTWARE RELEASE 2.22.0.X 800 AND 1900 MHZ CDMA2000 1X
68P09293A66A
1X SC4812T CLPA BTS OPTIMIZATION/ATP
SEP 2009
ENGLISH
Cellular Networks Customer Documentation
STANDARD MANUAL PRINTING INSTRUCTIONS

Part Number: 68P09293A66A Volume 1 of 1 Filename: 68P09293A66A.pdf APC: 379 Title: 1X SC4812T CLPA BTS Optimization/ATP
STANDARD SPECIFICATIONS FOR REFERENCEDO NOT MODIFY

PAPER: 1st. LEVEL TABS: 2nd. LEVEL TABS: Single Sided 5 Cuts Clear Mylar Pantone 2706C Black Ink Single Sided 7 Cuts Clear Mylar White Black Ink FINISHING: Body: 70 lb. Inside Cover: 65 lb. Cougar Tabs: 110 lb. Index Binder Cover: Standard TED cover 10 pt. Carolina 3Ring Binder SlantD 3Hole Punched (5/16in. dia.) Shrink Wrap Body Black ink for body, inside cover, and binder cover.
Print Vendor: eDOC
Date SEP 2009
TAB and SHEET SIZE/QUANTITY

11x17 2nd Level Tabs
7X9
8.5x11 304 1st Level Tabs
Sheets = (Total Pages) / 2
NONSTANDARD SPECIFICATIONS
Tape Bound Corner Stitch
Other: Meet with manager to determine the deliverable.
SPECIAL INSTRUCTIONS

1X SC4812T CLPA BTS Optimization Manual

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

1X SC4812T CLPA BTS Optimization Manual

Caricato da

Copyright:

Formati disponibili

SPECIFICATIONS SUBJECT TO CHANGE WITHOUT NOTICE Notice

Computer Software Copyrights

Usage and Disclosure Restrictions

High Risk Activities

Table of Contents 1X SC4812T CLPA BTS Optimization/ATP

Table of Contents continued

Chapter 2: Preliminary Operation

Table of Contents continued

Chapter 4: Automated Acceptance Test Procedure

Chapter 5: Configuring Packet BTS Transport

Chapter 6: Prepare to Leave the Site

Chapter 7: Basic Troubleshooting

7-1 7-2 7-5 7-8

Table of Contents continued

Appendix A: Data Sheets

Appendix B: PN Offset/I & Q Offset Register Programming Information

Appendix C: FRU Optimization/ATP Test Matrix

Appendix D: BBX Gain Set Point vs BTS Output

Appendix E: CDMA Operating Frequency

Appendix F: Test Equipment Preparation

Table of Contents continued

Appendix H: Download ROM Code

Appendix I: InService Calibration

Appendix J: Packet Backhaul Configuration

Appendix K: MMI Cable Fabrication

Appendix L: OTI Configuration Support Operations

List of Figures 1X SC4812T CLPA BTS Optimization/ATP

List of Figures continued

List of Figures continued

List of Figures continued

J-6 J-7 J-22 J-85 K-1 L-1

1X SC4812T CLPA BTS Optimization/ATP

List of Tables 1X SC4812T CLPA BTS Optimization/ATP

List of Tables continued

List of Tables continued

List of Tables continued

J-72 J-84 J-84 J-86 J-87 K-1 K-2 L-2 L-5

1X SC4812T CLPA BTS Optimization/ATP

1X SC4812T CLPA BTS Optimization/ATP

1X SC4812T CLPA BTS Optimization/ATP

General Information continued

1X SC4812T CLPA BTS Optimization/ATP

1X SC4812T CLPA BTS Optimization/ATP

1X SC4812T CLPA BTS Optimization/ATP

Warnings, cautions, and notes

1X SC4812T CLPA BTS Optimization/ATP

S not remove equipment covers. Only Factory Authorized Service

S not replace components with power cable connected. Under certain

S Directive 2004/40/EC of the European Parliament and of the Council

1X SC4812T CLPA BTS Optimization/ATP

Caring for the Environment

1X SC4812T CLPA BTS Optimization/ATP

CMM labeling and disclosure table

S Logo 1 means the product contains no substances in excess of the

1X SC4812T CLPA BTS Optimization/ATP

Motorola document set

1X SC4812T CLPA BTS Optimization/ATP

Third Party computer software and trademarks

1X SC4812T CLPA BTS Optimization/ATP

1X SC4812T CLPA BTS Optimization/ATP

FCC Requirements continued

FCC Part 68 Requirements

FCC Requirements continued