Accuracy 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. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability, function, or design, 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 document, Motorola products, and 3rd Party Software products described in this document may include or describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in the Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed, merged or modified in any manner without the express written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied software, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a product. Restrictions 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. License Agreements 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. High Risk Materials Components, units, or 3rd Party products used in the product described herein are NOT fault-tolerant and are NOT designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments requiring fail-safe 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.
The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center (CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
What is covered in this manual? This manual provides general information and procedures for optimization, calibration, and acceptance testing of the BTS. Also, covered is general information on test equipment set–up, calibration, and cable calibration.
68P09309A80-2 OCT 2010
1
FOA
Revision history
Revision history ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The following sections show the revision status of this document.
Version information The following table describes the changes made to this document: Version
Date of issue
Description
1
SEP 2010
Initial Draft.
2
OCT 2010
FOA Version
Release information This section describes the changes in this document between release 2.23.x.x and 2.24.x.x. •
Added content in support of the Dual Technology components, test equipment configuration, and operational testing.
•
Updated the Optimization/ATP test equipment configuration diagrams.
Resolution of Service Requests The following Service Requests are resolved in this document: Description
Service Request NA
NA
2
68P09309A80-2
FOA
OCT 2010
General information
General information ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Purpose Motorola documents provide the information to operate, install, and maintain Motorola equipment. It is recommended that all personnel engaged in such activities be properly trained by Motorola. Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or reduction in system performance arising directly or indirectly out of the failure of the customer, or anyone acting on the customer's behalf, to abide by the instructions, system parameters, or recommendations made in this document. These documents are not intended to replace the system and equipment training offered by Motorola. They can be used to supplement and enhance the knowledge gained through such training.
NOTE If this document was obtained when attending a Motorola training course, it is not 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 Motorola automatically supplies corrections and posts on the Motorola customer website.
Cross references References made to external publications are shown in italics. Other cross references, emphasized in blue text in electronic versions, are active links to the references. This document is divided into numbered chapters that are divided into sections. Sections are not numbered, but are individually named at the top of each page, and are listed in the table of contents.
Document banner definitions A banner indicates that some information contained in the document is not yet approved for general customer use. A banner is oversized text on the bottom of the page, for example, PRELIMINARY — UNDER DEVELOPMENT
68P09309A80-2 OCT 2010
3
FOA
Text conventions
Text conventions The following conventions are used in Motorola documents to represent keyboard input text, screen output text, and special key sequences.
Input Characters typed in at the keyboard are shown like this sentence. Items of interest within a command appear like this sentence.
Output Messages, prompts, file listings, directories, utilities, and environmental variables that appear on the screen are shown like this sentence. Items of interest within a screen display appear like this sentence.
Special key sequences Special key sequences are represented as follows: CTRL-c or CTRL+C
Press the Ctrl and C keys at the same time.
CTRL-SHIFT-c or CTRL+SHIFT+C
Press the Ctrl, Shift, and C keys at the same time.
ALT-f or ALT+F
Press the Alt and F keys at the same time.
ALT+SHIFT+F11
Press the Alt, Shift and F11 keys at the same time.
¦
Press the pipe symbol key.
RETURN or ENTER
Press the Return or Enter key.
4
68P09309A80-2
FOA
OCT 2010
Contacting Motorola
Contacting Motorola ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Motorola appreciates feedback from the users of our documents.
24–hour support If you have problems regarding the operation of your equipment, 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. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
Ordering documents and CD-ROMs With internet access available, to view, download, or order documents (original or revised), visit the Motorola customer web page at https://mynetworksupport.motorola.com, or contact your Motorola account representative. Without internet access available, order hard-copy documents or CD-ROMs from your Motorola Local Office or Representative. 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.
Questions and comments Send questions and comments regarding user documentation to the email address: [email protected].
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 document title, part number, and revision character
•
The page number with the error
•
A detailed description of the error and if possible the proposed solution
68P09309A80-2 OCT 2010
5
FOA
Errors
6
68P09309A80-2
FOA
OCT 2010
Chapter
1 Introduction ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
68P09309A80-2 OCT 2010
1-1
FOA
Scope, Assumptions, and Audience
Chapter 1: Introduction
Scope, Assumptions, and Audience ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
CAUTION Procedures in this manual require the use of Local Maintenance Facility (LMF) for Windows (WinLMF) application software version 2.24.0.0.26 or later.
Scope This publication provides information and procedures pertaining to the optimization and acceptance tests of the SC™7224 Base Transceiver Subsystem (1X SC7224 BTS) and the SC7224 Dual Technology (SC7224 DT) Base Transceiver Subsystem. The following models are covered in this manual: •
Single Band Configuration: 800 MHz or 2.1GHz
•
Dual Band Configuration: 800 MHz and 2.1 GHz
•
Dual Technology (800MHz only) Single Band Configuration Dual Band Configuration
NOTE The equipment shown in many of the figures is typical. The actual equipment appearance may vary slightly."
Packet BTS Support Information in this publication supports optimization of the 1X packet BTS operating with Motorola Software Release 2.24x.x. The CDMA2000 1X) packet BTS has a packet backhaul network interface provided through BTS routers operating with a Third-generation Group Line Interface (GLI3) card. This BTS equipment is configured with all 1X devices. This configuration is compliant with all applicable 1X specifications. It provides the forward link and reverse link RF functions to support Third Generation (3G) 1X features; that is, high capacity voice and high bit–rate data.
1-2
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Dual Technology Support
Dual Technology Support The Dual Technology BTS combines a Long Term Evolution (LTE) Baseband Control Unit (BCU) with the standard 800 MHz CDMA2000 1X BTS in the same frame. This combination allows both CDMA2000 1X and LTE carriers to operate simultaneously using the BTS CDMA2000 1X transceiver and RF power amplification equipment. The result is the ability to deploy LTE advanced wireless technology with significantly lower initial and operating costs to the customer. Throughout the manual, SC7224 BTS will be referred to as BTS or SCBTS in places where material applies to both BTS versions. Where information, components, operational details, and procedures differ between the two configurations, the content will be identified with the specific BTS version to which it applies as follows: •
Content applying only to the CDMA2000 1X BTS will be identified as SC7224
•
Content applying only to the Dual Technology BTS will be identified as SC7224DT, or DT (Dual Technology).
Assumptions This document assumes that the BTS frames and cabling have been installed according to the following manuals: •
Standards and Guidelines for Communication Sites; 68P81089E50, which covers the physical installation of all communication equipment frames
•
1X SC7224 BTS Hardware Modifications; 68P09283A26, which covers modifications from single band to dual band configurations.
•
1X SC7224 BTS Hardware Installation, which covers installation and cabling configurations for the SC7224 BTS.
•
For the Dual Technology BTS, SC7224 BTS Dual Technology Conversion, which covers converting the CDMA2000 1X–only version to the Dual Technology version
NOTE The SC7224 Dual Technology BTS version can not be ordered from Motorola. It must be created by retrofitting a previously installed standard 800 MHz CDMA2000 1X SC7224 BTS with the Dual Technology modification items.
Audience Motorola has attempted to incorporate into this document the many customer suggestions and comments received since the introduction of the Super Cell 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.
68P09309A80-2
1-3
FOA
OCT 2010
Intended Reader Profile
Chapter 1: Introduction
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 Microsoft® Windows® 2000,Windows XP™, Windows Vista®, or Windows 7.
1-4
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Content Summary
Content Summary ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Publication Composition This publication covers the following areas. •
Introduction: preliminary background information (such as component and subassembly locations and BTS layouts) to be considered by the Cellular Field Engineer (CFE) before optimization or tests are performed.
•
Preliminary Operations: BTS sub-assemblies, pre-power up tests, and initial power application and power-up tests for the BTS after installation.
•
Optimization: code syncing all BTS processor boards, test equipment set–up and calibration, XMI verification, radio frequency (RF) path verification, Bay Level Offset (BLO), and Cellular Remote Monitoring System (CRMS) functions.
•
Field Verification: At the site the BTS is assembled per the installation manual and tested using TX Audit and RSSI procedures.
•
Acceptance Test Procedures (ATP): automated ATP scripts executed by the WinLMF and used to verify all major transmit (TX) and receive (RX) performance characteristics on all BTS equipment. Includes generating an ATP report. Using the full ATP is optional.
•
Configuring Packet BTS Transport: Determining and changing GLI3 card code load and backhaul mode, and configuring GLI3 cards for the required packet transport mode: Integrated BTS Router (IBR), External BTS Router (EBR), or Open Transport Interface (OTI)
•
LTE Performance Verification and Acceptance. Draft version contains potential information categories normally associated with wireless communication system initial operation and normal performance evaluation.
•
Prepare to Leave the Site: site turnover process after ATP is completed.
•
Basic Troubleshooting: procedures to perform when an ATP fails, as well as when incorrect results are obtained during logon, test equipment operation, audit, Global Positioning System (GPS) operation, and backhaul set–up. These tests are typically used to isolate faults down to the module level. Also provided is additional information necessary to better understand equipment operation.
•
Appendices containing data sheets to be filled out manually by the CFE at the site, optimization/ATP matrix, output power data tables; CDMA operating frequency programming information; manual test set–up information; configuring External BTS Routers (EBR) for operation with a Motorola network; procedures for verifying that the Voltage Standing Wave Ratio (VSWR) of all antennas and associated feed lines falls within acceptable limits; and procedures to support configuring GLI3 cards for OTI.
68P09309A80-2
1-5
FOA
OCT 2010
Purpose of Optimization
Chapter 1: Introduction
Purpose of Optimization ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Why Optimize? Proper optimization ensures that: •
Accurate downlink RF power levels are transmitted from the site.
•
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 do not accumulate and cause improper site operation.
NOTE Calibration is not required when the SC7224 passes the TX Audit/Optimization tests. Calibration is included for cases where RF components have been changed and path loss/gain measurements are needed.
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 definitions 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 Appendix G Optimization and Calibration Procedures.
XMI calibration XMI modules will be calibrated at the factory to a pre-determined output level.
1-6
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
What Happens During Calibration?
Using RF path gain/loss values BTS equipment factors in the derived calibration values internally to adjust transceiver power levels, leaving only site-specific antenna feed line loss and antenna gain characteristics to be factored in by the CFE when determining required site Effective Radiated Power (ERP) output power levels.
68P09309A80-2
1-7
FOA
OCT 2010
When to Perform BTS RF Calibration and Acceptance Testing
Chapter 1: Introduction
When to Perform BTS RF Calibration and Acceptance Testing ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
This section summarizes Motorola-recommended 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 troubleshooting and for use after the following listed installation/upgrade activities: •
New BTS installation
•
Carrier additions
•
Multi-Channel CDMA (MCC) card additions
•
Site repairs
New Installations Objectives 1.
Verify forward (transmit) RF paths
2.
Verify reverse (receive) RF path performance
3.
Verify MCC operation for a new BTS installation
Recommended Actions Perform the following actions after initial power-up, code syncing, and verifying GPS operation: 1.
TX Audit of all transmit RF paths to verify BTS calibration is within tolerance.
2.
Perform RSSI on all receive RF paths
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.
1-8
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Repaired Sites
Recommended Actions Use any or all of the following tests during a troubleshooting visit to determine the nature of a BTS problem: •
TX calibration and audit on the affected carrier(s)
•
Code domain power for the affected carrier(s)
•
TX mask for the affected carrier(s)
•
Pilot time offset for the affected carrier(s)
•
Rho (TX Waveform) for the affected carrier(s)
•
FER for the affected carrier(s)
•
OBW for the affected carrier(s)
•
Continuous Waveform for the affected carrier
Repaired Sites Refer to Appendix B FRU Optimization/ATP Test Matrixfor 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.
68P09309A80-2
1-9
FOA
OCT 2010
General Test Equipment Selection, Calibration, and Operation Requirements
Chapter 1: Introduction
General Test Equipment Selection, Calibration, and Operation Requirements ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
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 WinLMF.
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 on-hand and operating properly.
Test Equipment Calibration Optimal 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 On-site 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.
1-10
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Equipment Warm-up
In-shop cable characterization Another method to account for cable loss is by entering it into the WinLMF 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 WinLMF before performing BTS calibration.
Equipment Warm-up 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. •
Communications Test Set
•
Power Meter
68P09309A80-2
1-11
FOA
OCT 2010
Required Test Equipment and Software
Chapter 1: Introduction
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.
WinLMF Computer and Software WinLMF Hardware Requirements An WinLMF computer platform that meets the following minimum requirements (or better) is recommended: •
Notebook computer
•
1GHz processor
•
Windows 2000, Windows XP (with Service Pack 3), Windows Vista or Windows 7 operating system
•
100MB of free disk space
•
Color display with 1024 x 768 resolution
•
Memory requirements: 512 MB for Windows 2000, Windows XP (with Service Pack 3) 1GB for Windows Vista or Windows 7
•
CD/DVD drive
•
Serial port (COM 1) when using GPIB
•
Serial port COM 2 for SC™6XX and serial versions of SC™3XX
Ethernet switch when using Ethernet test equipment
1-12
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Test Equipment and Associated Items
WinLMF Software The WinLMF 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: •
Installation
•
Maintenance
•
Calibration
Test Equipment and Associated Items Communications System Analyzer CDMA/analog Table 1-1
CDMA WinLMF Test Equipment Support Table Item
Description
Test Capability
Test Sets Agilent 8935 series E6380A (formerly HP 8935) with option 200 or R2K
Communications test set
CDMA 2000 testing
Agilent E4406A (with E4438C)
Communications Analyzer with Agilent E4438C CDMA Signal Generator
CDMA 2000 testing
Advantest R3267 Analyzer (with R3562)
Communications Analyzer with Advantest R3562 Generator
CDMA 2000 testing
Agilent E7495A or E7495B
Communications test set
CDMA 2000 testing
Antrisu™ MT8212B
Multi–function base station test set
CDMA 2000 testing
Power Meters Agilent E4418
Power Meter
Gigatronix 8541C
Power meter
A combination of test equipment supported by the WinLMF 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: •
Frequency counter
•
RF power meter (average)
•
RF signal generator (capable of CDMA modulation)
•
Spectrum analyzer
•
CDMA code domain analyzer
68P09309A80-2
1-13
FOA
OCT 2010
Test Equipment and Associated Items
Chapter 1: Introduction
RS-232 to GPIB Interface •
National Instruments GPIB-232CT–A is used to interface the WinLMF to the test equipment.
•
Standard RS–232 cable can be used with the following modifications (see Figure 1-1): This solution passes only the 3 minimum electrical connections between the WinLMF and the General Purpose Information Bus (GPIB) interface. The control signals are jumpered as enabled on both ends of the RS–232 cable (9–pin 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
9-PIN D-FEMALE GND RX TX RTS CTS RSD/DCD DTR DSR
5 3 2 7 8 1 4 6
9-PIN D-FEMALE
ON BOTH CONNECTORS SHORT PINS 7, 8; SHORT PINS 1, 4, AND 6
5 2 3 7 8 1 4 6
GND TX RX RTS CTS RSD/DCD DTR DSR FW00362
ti-cdma-00088.eps
Ethernet LAN Transceiver Most lap top computers built in 2004 and beyond have one Ethernet NIC port built into system. If a Ethernet NIC is needed the below list is a suggestion of devices that will work. •
PCMCIA Ethernet Adpater + Ethernet UTP Adapter: 3COM Model - Etherlink III 3C589B
•
Linksys EC2T
•
Other similar models
10BaseT/10Base2 Converter A SC7224 DMC has a 10Base2 Lan with access at the top of the DMC chassis. A 10BaseT/10Base2 Converter is needed to allow the WinLMF to communication with the SC7224 GLI in the DMC chassis. •
Transition Engineering Model E-CX-TBT-03 10BaseT/10Base2 Converter
•
Other compatible models
NOTE Xircom Model PE3-10B2 or equivalent can also be used to interface the WinLMF Ethernet connection to the frame.
1-14
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Test Equipment and Associated Items
3C-PC-COMBO CBL •
Connects to the 3COM PCMCIA card and eliminates the need for a 10BaseT/10base2 Converter.
MMI Interface Motorola cable part number CGDSMMICABLE219112 or a cable locally fabricated as described in Appendix F MMI Cable Fabrication is used to connect the WinLMF to the BTS.
GPIB Cables Hewlett Packard 10833A or equivalent; 1 to 2 meters (3 to 6 feet) long used to interconnect test equipment and WinLMF terminal.
Timing Reference Cables 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 Fluke Model 8062A with Y8134 test lead kit or equivalent; used for precision dc and ac measurements, requiring 4-1/2 digits.
Directional Coupler •
Narda Model 3042B-30, 200 W, .92-2.2 GHz, N-connectors, 30 dB or
•
Narda Model 3661B (Motorola P/N 58D09732W01)
RF Terminations/Loads At least three 200-Watt (or larger) non-radiating RF terminations/loads.
Miscellaneous RF Adapters, Loads, etc 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 N-Type Female-to-Female Adapters.
LAN Cable BNC–to–BNC 50 ohm coaxial cable [.91 m (3 ft) maximum] with an F-to-F adapter, used to connect the 10BaseT-to-coaxial adapter to the BTS LAN connector.
68P09309A80-2
1-15
FOA
OCT 2010
Optional Equipment
Chapter 1: Introduction
High-impedance Conductive Wrist Strap Motorola Model 42-80385A59; 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: •
NOTE Not all optional equipment specified here will be supported by the WinLMF 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.
Frequency Counter Stanford Research Systems SR620 or equivalent. If direct measurement of the 3 MHz or 19.6608 MHz references is required.
Spectrum Analyzer Spectrum Analyzer (HP8594E with CDMA personality card) or equivalent; required for manual tests.
Local Area Network (LAN) Tester Model NETcat 800 LAN troubleshooter (or equivalent); used to supplement LAN tests using the ohmmeter.
Span Line (T1) Verification Equipment As required for local application.
1-16
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Optional Equipment
Oscilloscope Tektronics Model 2445 or equivalent; for waveform viewing, timing, and measurements or during general troubleshooting procedure.
2-way Splitter Mini-Circuits Model ZFSC-2-2500 or equivalent; provides the diversity receive input to the BTS.
High Stability 10 MHz Rubidium Standard Stanford Research Systems SR625 or equivalent - required for CSM and High Stability Oscillator/Medium Stability Oscillator (HSO/MSO) frequency verification.
Itasca Alarms Test Box Itasca CGDSCMIS00014 - This test box may be used as a tool to assist in the testing of customer alarms.
68P09309A80-2
1-17
FOA
OCT 2010
Required Documents and Related Publications
Chapter 1: Introduction
Required Documents and Related Publications ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Required Documents The following documents are required to perform optimization of the cell site equipment: •
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
Site-specific NEC files •
Demarcation Document (Scope of Work Agreement)
•
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 sub–section may be needed 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 supported is assigned. Visit https://mynetworksupport.motorola.com for complete lists and part numbers of Motorola BTS and operating publications by software release.
1-18
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Related publications
Related publications Additional, detailed information about the installation, operation, and maintenance of the 1X SC™7224 BTS and its components is included in the following publications: •
WinLMF Help function on–line documentation
•
1X SC7224 BTS Hardware Installation
•
1X SC7224 BTS Hardware Modifications
•
1X SC7224 BTS Field Replaceable Units
•
CDMA2000 1X BTS Open Transport Interface Implementation/Conversion
•
CRMS P110 Installation Guide
•
CRMS P110 ICT User Manual
•
CRMS P110 User Guide
•
WinLMF CDMA CLI Reference
•
MWR 1941-DC Wireless Mobile Edge Router Software Configuration Guide; part number 78-13983
•
MWR1941-DC Mobile Wireless Edge Router Hardware Installation Guide; part number 78-15827
68P09309A80-2
1-19
FOA
OCT 2010
Acronyms and Abbreviations
Chapter 1: Introduction
Acronyms and Abbreviations ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Standard and Non–standard Acronyms and Abbreviations Standard terms and abbreviations used in this manual are defined in Glossary of Cellular Acronyms and Terms - CDMA On-line Documentation, 68P09266A86. Any non-standard terms or abbreviations included in this manual are listed in Table 1-2.
Table 1-2
Acronyms and Abbreviations Acronym
Definition
1X
One of two bandwidths currently defined in the IS-2000 CDMA specification, which extends the capability of the IS-95A and B specifications. 1X bandwidth provides wireless packet voice and data transmission capability at up to 144 Mbps.
AR
As Required
ATP
Acceptance Test Procedure
BCU 3
Baseband Control Unit, third generation
BSI
Baseband Switch Interface
BLO
Bay Level Offset
BPR
BTS Packet Router. Markings on GLI3 Fast Ethernet connectors and Fast Ethernet interface housing.
BSS
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).
BTSRTR
BTS RouTeR (see BTS router)
BTSRTRGRP
BTS RouTeR GRouP (see BTS router group)
BTS router
One of the routers in a BTS router group.
BTS router group
The single non-redundant router or redundant router pair required for network interface when a BTS is operating on packet backhaul.
cage
Used interchangeably with “shelf" in BTSes, as in Combined CDMA Channel Processor shelf.
canned configuration
See minimum standard configuration.
CCD
Clock Combining and Distribution. DMC shelf module which accepts timing signals from the active source and distributes them to other DMC shelf modules.
CEPT
Conference of European Postal and Telecommunications Administrators Continued
1-20
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Table 1-2
Standard and Non–standard Acronyms and Abbreviations
Acronyms and Abbreviations (Continued)
Acronym
Definition
CF
Compact Flash. Type of flash memory card used in the BTS router to store the Internetwork Operating System and configuration files.
CRMS
Cellular Remote Monitoring System
DDRF
Dual Duplexer Receive Filter
DMC
Digital Modem Cage
duplex router
See redundant router
ESM
Ethernet Surge Module
external BTS router
MWR 1941 BTS routers mounted outside the DMC cage of a packet BTS.
FE
Fast Ethernet. 100base-T mode of 10/100base-T Ethernet used for transmitting packetized control and bearer traffic between the BTS router group and GLI3 cards in the BTS.
GLI3
Third generation Group Line Interface card. This card 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.17x.x software or higher.
GPS
Global Positioning System (GPS)
high availability BTS router
See redundant router.
HSO
High Stability Oscillator
HSO2
Second-generation HSO card
IBR
Integrated BTS Router; see integrated BTS router
Integrated BTS Router
A GLI3 card loaded with bootROM code which allows the card's 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 non-redundant or redundant BTS routers, but their employment limits BTS span capacity to one span as opposed to four spans for external BTS routers.
IDRF
Integrated Duplexer Receive Filter
IOS
Internetwork Operating System. Operating system software used by the external BTS routers.
LIF
Load Information File
MCC-1X
Multichannel CDMA Card supporting 48 or 64 CDMA2000 1X (with Software Release 2.17.x.x and higher) channels. Continued
68P09309A80-2
1-21
FOA
OCT 2010
Standard and Non–standard Acronyms and Abbreviations
Table 1-2
Chapter 1: Introduction
Acronyms and Abbreviations (Continued)
Acronym
Definition
minimum standard configuration
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 OMC-R/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 OMC-IP and the full, site-specific 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.
mixed backhaul
See split backhaul.
MSO
Medium Stability Oscillator (also Motorola Standard Oscillator)
NECB
Network Element Configuration Baseline. WinLMF will only read NECB files.
NECF
Network Element Configuration File. Term which includes both the NECB and NECJ files (see NECB and NECJ).
NECJ
Network Element Configuration Journal. NECJ only used by WinLMF for code syncing to the GLI.
non-redundant router
A BTS router group consisting of a single router without redundancy used as a cost-reduced network interface for a BTS operating on packet backhaul.
OLF
Object List File. File containing a list of the ROM and RAM code versions which should be operating on every device installed in a BTS. The file is resident on the Central Base Station Controller (CBSC) Mobility Manager (MM) and is passed to the GLI after a DLM job is invoked. The GLI uses the OLF to determine which devices require code download to meet the OLF-specified version.
OTI
Open Transport Interface
PDU
Power Distribution Unit
packet backhaul
IP-based backhaul between the BTS and the the network. Packet backhaul capability is implemented in Software Release 2.17.x.x and requires equipping a BTS with BTS routers and GLI3 cards.
packet BTS
A BTS operating on packet backhaul
pBTS
Packet BTS
redundant router
A BTS router group consisting of two MWR 1941 routers with Hot Standby Router Protocol (HSRP) to provide redundancy.
ROMmon
Low-level operating system used in MWR 1941 routers along with the IOS
RGD
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). Continued
1-22
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Table 1-2
Standard and Non–standard Acronyms and Abbreviations
Acronyms and Abbreviations (Continued)
Acronym
Definition
RSSI
Receive Signal Strength Indicator
simplex router
See non-redundant router.
SNMP
Simple Network Management Protocol
Var.
Variable
VWIC
Voice-WAN Interface Card
WIC
WAN Interface Card (also VWIC)
68P09309A80-2
1-23
FOA
OCT 2010
BTS Equipment Identification
Chapter 1: Introduction
BTS Equipment Identification ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
SC7224 Overview The SC7224 BTS has some significant differences from SC4840 BTSs. The MPC, BBX, and PA modules no longer exist. They have been replaced by the XMI. The Serializer is a new module which is an interface between the MCCs and the XMIs. The SC7224 BTS continues to use GLI3s, MCC–1Xs, AMRs, and CSMs. These modules are all housed in the Digital Modem Cage (DMC). The DMC can be viewed as a merger of 2 CCP12 shelves from an SC4840 without BBXs and the power distribution shelf. There are no RF interfaces to the DMC except for GPS. The SC7224 BTS does not require calibration. The XMI modules are calibrated in the factory and the variation from combining XMIs, cables, and filters is small enough that a power out variation of ±2 dB can be achieved without calibration. The Serializer and MCCs are digital modules which do not require any calibration. The basic ATP for the SC7224 at the site will consist of TX Power Audit and RSSI. The other ATP items will be tested in the factory. A self–check by the SC7224 will be able to verify the some of the cabling to the Serializers and the XMIs. Since the SC7224 operates in Packet mode, downloading from the WinLMF will not be done. If a connection to the OMC–R is available, the OMC–R will be used to ensure the proper software is in place on the BTS. In those cases where an OMC–R connection is not available, WinLMF downloading is replaced with a Syncing Procedure. The Syncing Procedure should only be used when necessary, since it is possible to accidentally put the GLI in a non–operable state.
SC7224 Frame Overview The SC7224 frame contains three major sections: 1.
The upper portion of the rack contains the PDU Circuit Breaker Panel TX Combiner, IDRF or DDRF and XMI Shelf,
2.
The middle portion of the rack contains the RF Splitter and External BTS Routers (EBR) or the Baseband Switch Interface (BSI) and Baseband Control Unit 3 (BCU3).
3.
The lower portion of the rack contains the DMC (consisting of cards, modules, and fans). The top interconnect panel of the DMC provides both inter fame and external frame connections.
NOTE I/O panel detail is provided for one BTS in Figure 1-6.DMC cage details are provided in Figure 1-7 The equipment shown in many of the figures is typical. The actual equipment appearance may vary slightly.
1-24
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Figure 1-2
SC7224 Frame Overview
SC7224 Single Band Frame
LABEL POWER INPUT
FOR TX/RX ANTENNAS IDRF (Integerated Duplexer and Rx Filter)
EXPANSION RX OUTPUT PDU CIRCUIT BREAKERS
IDRF BRACKET
COMBINER
PDU
CELLULAR REMOTE MONITORING SYSTEM (CRMS)
RIGHT CHANNEL OF RACK
XMI 1
RIGHT CHANNEL COVER (Left channel cover not shown)
XMI 2 XMI 3 SLOT
XMI SHELF XMI 4 SLOT
EBR 1 EBR 2
SPLITTER
CABLE TROUGH
SPAN A SPAN B
DMC RACK
Note: 2.1 GHzequi pm en t is shown. ti-cdma-00027.eps
68P09309A80-2
1-25
FOA
OCT 2010
SC7224 Frame Overview
Figure 1-3
Chapter 1: Introduction
SC7224 Dual Band Frame
LABEL POWER INPUT
FOR TX/RX ANTENNAS IDRF (Integerated Duplexer and Rx Filter) IDRF BRACKET
EXPANSION RX OUTPUT PDU CIRCUIT BREAKERS COMBINER
PDU
CELLULAR REMOTE MONITORING SYSTEM (CRMS)
RIGHT CHANNEL OF RACK
XMI 1
RIGHT CHANNEL COVER (Left channel cover not shown)
XMI 2 XMI 3
XMI SHELF
XMI 4
EBR 1 EBR 2 SPLITTER
CABLE TROUGH
SPAN A SPAN B
DMC RACK
ti-cdma-01624.eps
1-26
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Figure 1-4
SC7224 Frame Overview
SC7224 Dual Technology Single Band (800MHz) Frame
DDRF (Integrated Duplexer And Rx Filter)
Power Input
Filter Bracket
PDU Circuit Breakers
PDU Right Channel Of Frame Cellular Remote Monitoring System (CRMS)
Right Channel Cover (Left channel cover not shown)
XMI 1 XMI 2
BCU 3 BSI XMI Shelf
Splitter
Cable Tray Alarm B Feed Through Filter
DMC
Rack
A8_single_band_SC7224after.eps
68P09309A80-2
1-27
FOA
OCT 2010
SC7224 Frame Overview
Figure 1-5
Chapter 1: Introduction
SC7224 Dual Technology Dual Band Frame IDRF (Integrated Duplexer And Rx Filter) DDRF (Integrated Duplexer And Rx Filter)
Power Input Filter Bracket
PDU Circuit Breakers
PDU Cellular Remote Monitoring System (CRMS)
Right Channel Of Rack Right Channel Cover (Left channel cover not shown)
XMI 1 XMI 2 XMI 3 XMI 4
BCU 3 BSI XMI Shelf
Splitter Cable Tray Alarm B Feed Through Filter
Rack DMC
A8_dual_band_SC7224after.eps
1-28
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Digital Modem Cage (DMC) I/O Panel
Digital Modem Cage (DMC) I/O Panel Most of the cabling to and from the BTS equipment is accomplished at the DMC I/O panel (see Figure 1-6). Connections at the I/O panel include: •
Alarm connections
•
Fast Ethernet interface
•
LAN connections
•
Power input
•
RF GPS input or Remote Global Positioning System (RGPS) on the Site I/O
•
HSO/MSO connection
•
XMI conections
•
Span A and B I/O
•
Site I/O
Figure 1-6 presents the nomenclature for the Digital Modem Cage I/O Panel.
68P09309A80-2
1-29
FOA
OCT 2010
Digital Modem Cage (DMC) I/O Panel
Figure 1-6
Chapter 1: Introduction
Digital Modem Cage I/O Panel
Power Supply Card Circuit Breakers 1 DMC DC Input Power (+27V from PDU)
2
HSO/MSO (9-pin D-Sub)
LAN 2 (B) (BNC) IN
OUT
For Customer Alarm Equipment (68-pin Dual Row Headers) ALARM B ALARM A
Ethernet 2 Ethernet 3 Span I/O A (RJ-45) 1 & 2 for EBRs
50-pin Connector for Spans A, C, E Used with IBR
XMI 1-4 HSL 1 & 2 (to XMIs, 9-pin D-Subs)
50-pin Connector for Spans B, D, F Used with IBR
Ethernet 1 Ethernet 2 Ethernet 3 Span I/O B (RJ-45) 1 & 2 for EBRs ti-cdma-00039.eps
1-30
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
DMC Shelves
DMC Shelves The DMC Cage houses the circuit cards/modules, cooling fans, and 100BaseT ethernet connections (see Figure 1-7). The DMC shelves include: •
DMC backplane and cage
•
DMC power supplies
•
Clock Synchronization Manager (CSM)
•
High Stability Oscillator (HSO) or Medium Stability Oscillator (MSO) card
•
Alarm Monitoring and Reporting (AMR) cards
•
GLI cards
•
Serializer modules
•
MCC cards
•
Clock Combining and Distribution (CCD1 & 2) cards
Serializer The Serializer (SER) card is used in the SC7224 architecture to provide the interface between the digital processing subsystem and RF distribution system. SER cards are required to be configured in redundant pairs with one card active (primary SER) and the other SER in hot-standby. If the primary SER fails, the standby SER will take over the Serializer function. Up to four SER cards can be installed in the DMC with two cards per shelf. Therefore, the SC7224 supports either two (2) or (4) SER cards. A pair of SER cards is required to support a single Modem Group and provide redundancy for the minimum sector-carrier configuration. Each SER can support up to 12 sector-carriers per Modem Group.2 The upper DMC shelf must always be configured first with a pair SER cards. The SER pair associated with the first Modem Group provides the interface to the XMIs. The XMIs are configured to use the primary SER feed if it is available. If the primary SER fails, the XMIs can switch to the standby SER feed. The number of SER cards required for the SC7224 is as follows: •
Two (2) SER cards or any configuration with a single GLI3 pair (supports up to 12 sector-carriers)
•
Four (4) SER cards for any configuration with two GLI3 pairs (up to 24 sector-carriers)
Each MCC-1X card has six sector–carrier connections to each SER card. Since the SER cards provide redundancy for all sector-carriers, the same six sector-carriers must be routed to each SER. Since each MCC-1X card has 12 connections, then six connections are routed to each SER card. All XMIs are physically connected to both SERs in the first Modem Group (that is, SER-1 and SER-2). The interface between XMI and SER is based on the Common Public Radio Interface Specification, and the base band signaling is processed by both SERs and is available to each XMI continuously.
DMC Shelf Card/Module Device ID Numbers All cards/modules/boards in the BTS at a single site, assigned to a single BTS number, are also identified with unique Device ID numbers dependent upon the BTS ID number in which they are located. Refer to Table 1-3 and Table 1-4 for specific DMC Shelf Device ID numbers.
68P09309A80-2
1-31
FOA
OCT 2010
DMC Shelves
Chapter 1: Introduction
Table 1-3
DMC Shelf/Cage Card/Module Device ID Numbers (Top Shelf) Card/Module ID Number (Left to Right)
Frame #
PS-1
AMR
GLI
GLI
1
-
1
1
2
Table 1-4
MCC 1
2
SER
3
4
1
MCC 5
2
7
6
8
CSM
HSO/MSO
1
1
DMC Shelf/Cage Card/Module Device ID Numbers (Bottom Shelf) Card/Module ID Number (Left to Right)
Frame #
PS-2
AMR
GLI
GLI
1
-
2
3
4
MCC 21
22
SER 23
1-32
24
3
4
MCC 25
26 27
28
CSM
CCD1/2
2
1/2
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Figure 1-7
DMC Shelves
DMC Shelves (Single Band) DMC
NOTE: 1. Cards are shipped installed in the DMC cage 2. CCD slot cover panel is shown removed. 3. Cables are not shown. 4. mcc, GLI, and SER cards are not present in the lower shelf.
PWR/ALM
PWR/ALM
PWR/ALM
PWR/ALM
PWR/ALM
PWR/ALM
PWR/ALM
PWR/ALM
BPR A
SYNC MONITOR
BPR B
PWR/ALM
XMI3 XMI4
XMI3 XMI4
PWR/ALM
XMI1 XMI2
XMI1 XMI2
GLI
PWR/ALM
AUX
PWR/ALM
FREQ MONITOR
RESET MMI
ACTIVE
ACTIVE
ACTIVE
ACTIVE
STA
ACT
STA
ACT
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACT
MMI STA
RESET MMI
SPAN
ALARM
RESET
PWR/ALM
21
22
23
24
25 26
27
28
CCD 1 SYNC MONITOR PWR/ALM
PWR/ALM
PWR/ALM
FREQ MONITOR
CCD 2
ti-cdma-00066.eps
68P09309A80-2
1-33
FOA
OCT 2010
DMC Shelves
Chapter 1: Introduction
Figure 1-8
Span B
EtherNet 3 EtherNet 2 EtherNet 1
Span A
EtherNet 3 EtherNet 2 EtherNet 1
DMC Shelves (Dual Band) Grd Stud
Top panel cover
EN 1
EN 2 SPAN A
EN 3
EN 1
EN 2 SPAN A
EN 3
FE Ports (RJ45) for GLI Cabling (shown behind top panel cover) PWR/ALM
PWR/ALM
PWR/ALM
PWR/ALM
PWR/ALM
PWR/ALM
SYNC MONITOR
BPR B
PWR/ALM
XMI3 XMI4
XMI3 XMI4
PWR/ALM
XMI1 XMI2
XMI1 XMI2
GLI
PWR/ALM
AUX
PWR/ALM
FREQ MONITOR
RESET MMI
ACTIVE
ACTIVE
ACTIVE
ACTIVE
STA
ACT
ACT
STA
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACT
MMI STA
RESET MMI
SPAN
ALARM
RESET
1. GLI 1 and GLI 2 operate as MGLI devices. 2. Quantity of MCC cards varies and is system dependent. 3. CCD slot cover panel is shown removed. 4. Cables are not shown.
PWR/ALM
PWR/ALM
BPR A
NOTES:
PWR/ALM
22
21
24
25 26
27
28
SYNC MONITOR
BPR B
PWR/ALM FREQ MONITOR ACTIVE
STA
ACT
ACTIVE
RESET MMI
ACTIVE
XMI3 XMI4 ACTIVE
XMI1 XMI2
STA
ACT
ACTIVE
RESET MMI
ACTIVE
ACTIVE
ACTIVE
ACT
MMI STA
XMI3 XMI4
SPAN
ALARM
RESET
XMI1 XMI2
GLI
PWR/ALM
AUX
PWR/ALM
ESD (Electro-Static Discharge) Jack for Plug-in Wrist Strap
CCD 1 (Note 4)
PWR/ALM
PWR/ALM
PWR/ALM
PWR/ALM
PWR/ALM
PWR/ALM
PWR/ALM
PWR/ALM
BPR A
Modem Group 1 Consists of GLI 1, GLI 2, MCC 1 - MCC 8, SER 1, SER 2 (NOTES 1, 2, 3)
23
CCD 2 (Note 4)
Modem Group 2 Consists of GLI 1, GLI 2, MCC 1 - MCC 8, SER 1, SER 2 (NOTES 1, 2, 3) Fan Modules ti-cdma-01625.eps
1-34
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
XMI Module
XMI Module
XMI Overview The XMI module is a combination of PA module and the RF and base-band signal processing portions of the BBX as well as the low noise amplifiers of an MPC. The SC7224 utilizes an Integrated Transceiver / Power Amplifier Module (XMI) that provides both the base-band transceiver and linear power amplifier functionality for the BTS. This functionality is integrated within a single module. The SC7224 frame can support up to four XMI's mounted in a vertical orientation. Each XMI can support one to three sectors with up to four carriers receive and up to eight carriers transmit. Each XMI supports up to four carriers (or 5 MHz) of the 15 MHz total bandwidth supported by the SC7224 in the reverse (receive) direction or up to eight carriers of the 15 MHz total bandwidth in the forward (transmit) direction. After the first carrier is assigned to an XMI, additional carriers assigned to that XMI must be within the 5 MHz. When carriers are mapped to the XMI, they may be either adjacent or non-adjacent within the 5 MHz bandwidth constraint of the target XMI. Carriers that fall outside the 5 MHz bandwidth are required to be associated with a different XMI. When four XMI's are provisioned, the SC7224 is capable of supporting the entire 15 MHz bandwidth allocation. For the reverse link, the XMI is always configured in a fully redundant, N+1 configuration, where N=1 to 3. Therefore, the base configuration for the SC7224 must always have at least two XMI's. In the forward link the XMI supports soft–fail redundancy. When an XMI becomes disabled, a power drop will occur but all carriers will remain active. In the reverse link, the XMI is configured such that a single XMI only provides the Low Noise Amplifier (LNA) for either Main or Diversity antennas. Therefore, loss of a single XMI (LNA) results in the loss of receive diversity, but all carriers are maintained (provided there is still a functional Main or Diversity receive path.) The XMI supports trunking and two or more XMI's can be combined to increase the total available transmit power. The maximum RF output power per XMI is 120W, up to 30W per single sector-carrier or 160W total per antenna port. The total available RF output power from all XMIs configured in the SC7224 is shared across all sector-carriers. The SC7224 continuously monitors the RF output power demand of the BTS and can adjust for required power through On-Demand Power Amplification (ODPA). For example, the SC7224 can reduce the required DC input power when the operating RF power allows. Each XMI monitors the required RF output power and applies an internal algorithm to disable sections of their internal power amplifier to reduce the DC input power required by the XMI. The XMI includes provisions to prevent rapid cycling of the power amplifiers. With R17, the 2.1GHz XMI has hardware capable of providing interference cancellation. However, software functionality to enable interference cancellation on the XMI will be enabled on a future release. The XMI utilizes a wide-band receiver that supports up to four carriers per XMI. The interference cancellation utilizes digital processing (FFT/IFFT) capable of removing multiple narrow band interference signals within the CDMA carriers up to –50 dBm. In a future release, interference canceling can be enabled/disabled on a per carrier basis, and interference statistics will be viewable at the OMC–R. Figure 1-9 presents the nomenclature for the XMI.
68P09309A80-2
1-35
FOA
OCT 2010
TX Combiner
Chapter 1: Introduction
Figure 1-9
XMI Module XMI CARD
Mounting Tab
TXD (ganged MCX-type) To/From TX Combiner
TOP
(+) (-)
+27V DC Input Power From PDU
HSL2
(HSSDC2 Type) To DMC
HSL1 TX-3 (Sector 3)
CONTROL to Combiner (9-pin D-type) LMT (RJ45) Status/Alarm LED
TX RF Outputs (QN-type coaxial) To TX Combiner Inputs
MMI (RJ45)
TX-2 (Sector 2)
RX EXP OUT RX Expansion Ports to Splitter (ganged mini-coaxial) RX EXP IN
TX-1 (Sector 1) RX 3 D; from Sector 3 IDRF RX DIV (QMA-Type Coaxial) Only used on XMI 1
RX 2 D; from Sector 2 IDRF RX 1 D; from Sector 1 IDRF
Mounting Tab
RX 3 M; from Sector 3 IDRF
RX 2 M; from Sector 2 IDRF
RX MAIN (QMA-Type Coaxial) Only used on XMI 2
RX 1 M; from Sector 1 IDRF
BOTTOM
ti-cdma-00037.eps
TX Combiner Figure 1-10 presents the nomenclature for the TX Combiner.
NOTES: 1. All TX RF I/O connectors are QN-type coaxial. 2. All XMI TXD connectors are ganged MCX-type. 3. All XMI CONTROL connectors are 9-pin D-type. 4. S1=Sector 1, S2=Sector 2 and S3=Sector 3. 5. Signal flow direction for all TX RF Inputs is from XMI. Signal flow direction for all TX RF Outputs is to IDRFs.
Rear Panel
ti-cdma-00031.eps
68P09309A80-2
1-37
FOA
OCT 2010
TX Combiner
Chapter 1: Introduction
Figure 1-11
TX Combiner (800 MHz) TX RF Inputs from XMIs
XMI 1 TX-1 (S1)
TX-2 (S2)
XMI 2 TX-3 (S3)
TX-1 (S1)
TX-2 (S2)
XMI 4
XMI 3 TX-1 (S1)
TX-3 (S3)
TX-2 (S2)
TX-3 (S3)
TX-1 (S1)
TX-2 (S2)
TX-3 (S3)
800 MHz COMBINER Front Panel
Not Used TXD Mounting Tab
CONTROL
TXD
XMI 1
CONTROL
TXD
CONTROL XMI 3
XMI 2
TXD
CONTROL XMI 4
Mounting Tab
NOTES: 1. All TX RF I/O connectors are QN-type coaxial. 2. All XMI TXD connectors are ganged MCX-type. 3. All XMI CONTROL connectors are 9-pin D-type. 4. S1=Sector 1, S2=Sector 2 and S3=Sector 3. 5. Signal flow direction for all TX RF Inputs is from XMI. Signal flow direction for all TX RF Outputs is to IDRFs.
Combined Sector TX RF Outputs to IDRFs
TX-3 (S3)
TX-2 (S2)
TX-1 (S1)
Rear Panel
ti-cdma-01706.eps
1-38
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Figure 1-12
RF Splitter
Dual Band Combiner TX RF Inputs from XMIs
TX RF Inputs from XMIs XMI 1 TX-1 (S1)
TX-2 (S2)
XMI 2 TX-3 (S3)
TX-1 (S1)
TX-2 (S2)
XMI 4
XMI 3 TX-1 (S1)
TX-3 (S3)
TX-2 (S2)
TX-3 (S3)
TX-1 (S1)
TX-2 (S2)
TX-3 (S3)
DUAL BAND COMBINER Front Panel
Not Used TXD Mounting Tab
CONTROL
2.1 GHz XMI1
CONTROL
TXD
CONTROL
TXD
2.1 GHz XMI2
800 MHz XMI 3
TXD
CONTROL
800 MHz XMI 4
Mounting Tab
NOTES: 1. All TX RF I/O connectors are QN-type coaxial. 2. All XMI TXD connectors are ganged MCX-type. 3. All XMI CONTROL connectors are 9-pin D-type. 4. S1=Sector 1, S2=Sector 2 and S3=Sector 3. 5. Signal flow direction for all TX RF Inputs is from XMI. Signal flow direction for all TX RF Outputs is to IDRFs. Combined Sector TX RF Outputs to 800 MHz IDRFs TX-3 (S3)
RF Splitter Figure 1-13 presents the nomenclature for the RF Splitter.
68P09309A80-2
1-39
FOA
OCT 2010
External BTS Router
Chapter 1: Introduction
Figure 1-13
RF Splitter (Wide Band)
Mounting Tab
NOTES: 1. All RX splitter connectors are ganged mini-coaxial. 2. RX EXP IN signal flow direction is from XMI. RX EXP OUT signal flow direction is to XMI. 3. Used in both 2.1 GHz and 800 MHz applications.
XMI 1 EXP OUT (RX MAIN)
EXP IN (RX DIV )
XMI 3 EXP OUT (RX MAIN & DIV)
Mounting Tab
XMI 4 EXP OUT (RX MAIN & DIV)
WIDE BAND SPLITTER
EXPANSION/ 3RD PARTY (Signal source via splitter: RX MAIN is XMI 1 and RX DIV is XMI 2.)
EXP OUT (RX DIV )
EXP IN (RX MAIN)
XMI 2 ti-cdma-01727.eps
Figure 1-14
RF Splitter (Dual Band) NOTES: 1. All RX splitter connectors are ganged mini-coaxial. 2. RX EXP IN signal flow direction is from XMI. RX EXP OUT signal flow direction is to XMI.
Mounting Tab
EXP OUT (RX MAIN)
Mounting Tab
XMI 3
XMI 1
EXP OUT (RX MAIN)
EXP IN (RX DIV )
EXP IN (RX DIV )
DUAL BAND SPLITTER EXPANSION/ 3RD PARTY (Signal source via splitter: RX MAIN is XMI 1 and RX DIV is XMI 2.)
EXP OUT (RX DIV )
EXP IN (RX MAIN)
XMI 2
EXP OUT (RX DIV )
EXP IN (RX MAIN)
XMI 4 ti-cdma-00034.eps
External BTS Router Figure 1-15 presents nomenclature for the External BTS Router (EBR).
NOTES: 1. VWIC slot 0 is always used. 2. VWIC slot 1 is for optional expansion VWIC when more T1 capacity is required. 3. VWIC in slot 1 has same port and LED labeling/layout as shown for VWIC in slot 0.
CTRLR T1 0 To SPAN (RJ-48C) PWR Chassis STAT LEDs ACT
Rack Mount Bracket (both sides) FE 1 Port LEDs: ACT SPEED LINK
FE 1 FE 0 Fast Ethernet Ports To DMC (10/100 BaseT; RJ-45)
CF Slot ACT LED
AUXILIARY CONSOLE Port (RJ-45) Port (RJ-45)
Compact Flash Card Slot FE 0 Port LEDs: ACT SPEED LINK
Rear Panel
DC Input Power Connector To PDU
Grounding Nut/Screw
Cooling Fan (rear exhaust) 1-of-4
Rack Mount Bracket (both sides, at front)
ti-cdma-00038.eps
Optional Baseband Switch Interface (BSI) Equipment Identification The Baseband Switch Interface (BSI) is required in the optional Dual Technology frame. The BSI provides an interface between the DMI, BCU3 (Dual Technology component) and XMI modules. The BSI permits the forward baseband data from all the DMIs and the BCU3 in a BTS to be connected to the XMIs that are providing the small signal processing. It also provides the mechanism to connect the reverse baseband data from the XMI to the correct DMI and BCU3. Figure 1-16 shows the I/O connectors on the front panel of the BSI and their respective termination points.
68P09309A80-2
1-41
FOA
OCT 2010
Optional Baseband Control Unit 3 (BCU3)
Figure 1-16
Chapter 1: Introduction
BSI Front Panel Detail +27 V DC Input Power To/From
XMI 1
Mounting Tab
DMI 1
DMI 2
XMI 2
XMI 1
BCU 3
Status, Instance and Alarm LEDs
XMI 2 BCU 3
BCU 3
Mounting Tab
/
FRONT VIEW
A9-DT_BSI_Front_2.eps
Optional Baseband Control Unit 3 (BCU3) In the optional Dual Technology frame the BCU3 provides the LTE network interface between the Access Terminals (ATs) and the LTE network. The BCU3 combines both Station Control Module and Modem Cards of the BCU2 into a 1U rack mounted module. The BCU3 interfaces with the BSI module to send/receive baseband LTE data to/from the UBS XMI module. Figure 1-17 shows the front panel of the Baseband Control Unit 3.
1-42
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Figure 1-17
Integrated Duplexer and RF Filter
BCU3 Front Panel
POWER CONNECTOR
B BACKHAUL
B BACKHAUL
A-REF-B STATUS
EXP TEST
SYNC
SYNC R RU SYNC R RU SYNC R RU
1
ESD
2
3
4
5
6
RFGS
SYNC R RU SYNC R RU SYNC R RU
RFGS
SYNC
ESD
AISG
A
A
STATUS A- REF-B
CUST ENET
CUSTOMER I/O
EXP
CUST EN ET
LMT
TEST
LMT
AISG
CUST OMER I/O
ON/OFF
6 BSI
5 4
3 BSI 2 1 BSI GROUND
Enter_illustration_filename_here.eps
Integrated Duplexer and RF Filter The 2.1 GHz IDRF is shown in Figure 1-18. The two styles of 800 MHz IDRF are shown in Figure 1-19 and Figure 1-20 .
68P09309A80-2
1-43
FOA
OCT 2010
Integrated Duplexer and RF Filter
Figure 1-18
Chapter 1: Introduction
2.1 GHz IDRF
TOP VIEW
IDRF
BOTTOM VIEW
Mounting Tab
Antenna Coupled Ports to CRMS (SMA-Type Coaxial)
TX to Combiner (Combined Sector TX RF) (QN-Type Coaxial)
RX DIV FWD RX DIV RFL
RX DIV to Antenna (N-Type Coaxial) TX/RX MAIN FWD
Antenna Coupled Ports to CRMS (SMA-Type Coaxial)
RX MAIN to XMI 1 (QMA-Type Coaxial)
TX/RX MAIN RFL
TX/RX MAIN to Antenna (N-Type Coaxial) RX DIV to XMI 2 (QMA-Type Coaxial) Mounting Tab
ti-cdma-05680.eps
Figure 1-19
800 MHz IDRF (Style A) TOP VIEW
IDRF
BOTTOM VIEW
Mounting Tab
Antenna Coupled Ports to CRMS (SMA-Type Coaxial)
TX to Combiner (Combined Sector TX RF) (QN-Type Coaxial)
RX DIV FWD RX DIV RFL
RX DIV to Antenna (N-Type Coaxial)
Antenna Coupled Ports to CRMS (SMA-Type Coaxial)
TX/RX MAIN FWD
RX MAIN to XMI 1 (QMA-Type Coaxial)
TX/RX MAIN RFL
TX/RX MAIN to Antenna (N-Type Coaxial) RX DIV to XMI 2 (QMA-Type Coaxial) Mounting Tab ti-cdma-01626.eps
1-44
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Figure 1-20
IDRF I/O and PDU I/O
800 MHz (Style B)
TOP VIEW
IDRF
BOTTOM VIEW
Mounting Tab
Antenna Coupled Ports to CRMS (SMA-Type Coaxial)
TX to Combiner (Combined Sector TX RF) (QN-Type Coaxial)
RX DIV FWD RX DIV RFL
RX DIV to Antenna (N-Type Coaxial) Antenna Coupled Ports to CRMS (SMA-Type Coaxial)
TX/RX MAIN FWD TX/RX MAIN RFL
TX/RX MAIN to Antenna (N-Type Coaxial) RX MAIN to XMI 1 (QMA-Type Coaxial)
RX DIV to XMI 2 (QMA-Type Coaxial) Mounting Tab
ti-cdma-05681.eps
IDRF I/O and PDU I/O Figure 1-21 presents the nomenclature for the IDRF I/O and PDU I/O.
68P09309A80-2
1-45
FOA
OCT 2010
IDRF I/O and PDU I/O
Figure 1-21
DC Input Power (Secondary)
Chapter 1: Introduction
Integrated Duplexer and RF Filter (IDRF) I/O and PDU I/O. +27V DC Output Power (3-pin Connectors)
+27V DC Output Power (2-pin Connector) To CRMS
PDU I/O Panel (Rack/PDU Top View)
To EBR 1
To EBR 2
FRONT RX Expansion Ports DC Input Power RX Out 1 - RX Out 6 (Primary) (N-Type Coaxial)
DC Input Power Connectors
RX Expansion Ports RX In 1 - RX In 6 (N-Type Coaxial)
Circuit Breakers on Circuit Breaker Panel
DMC (90A)
XMI 1 (90A)
XMI 2 (90A)
To DMC
To XMI 1
CRMS EBR 1 EBR 2 (10A) (10A) (10A)
XMI 3 (90A)
XMI 4 (90A)
PDU Circuit Breaker Panel
To XMI 2
To XMI 3
To XMI 4
+27V DC Output Power (3-pin Connectors located behind TX Combiner not shown) ti-cdma-00035.eps
1-46
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Optional Dual Duplexer RX Filter (DDRF)
Optional Dual Duplexer RX Filter (DDRF) The Dual Duplexer Receive Filter (DDRF) replaces the IDRF in the optional Dual Technology Compact Macro UBS at the 800MHz band. The DDRF is an all passive network. It is configured with a dual duplex filter block (2 Tx, 2 Rx) and a coaxial transfer relay switch on the input Transmit ports. There are dual directional couplers on the antenna ports. The transmit and receive filters also provide the final stage of transmit filtering and the first stage of receive filtering in the Universal BTS architecture. The primary application of this device is to diplex both a main and diversity transmit path with their corresponding receive paths. The primary function of coaxial transfer relay switch on the transmit input ports is to allow the swapping of Ant1 & Ant2 if requested by control signals from the XMI. Each of the two transmitter inputs can deliver a total maximum average power of 65 watts. The DDRF also has an integrated Diagnostics board that can provide Forward and Reverse Power readings with the aid of an RMS power detector. This information is provided to the XMI via a CAN bus interface. Power Detector level shall be referenced to the antenna port.
Figure 1-22
DDRF Front View
CRMS Figure 1-23presents the nomenclature of the CRMS.
Fast LAN Ethernet to DMC (10 Base2, BNC-type coaxial)
Mounting Tab
LAN A LAN B
BOTTOM ti-cdma-01728.eps
1-48
68P09309A80-2
FOA
OCT 2010
Chapter
2 Preliminary Operations ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
68P09309A80-2 OCT 2010
2-1
FOA
Overview
Chapter 2: Preliminary Operations
Overview ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction This section first verifies proper frame equipage. This includes verifying module placement, jumper, and dual in-line 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 3-Sector with a maximum of 8 carriers. For more information on the differences in site types, please refer to the 1X SC 7224 BTS Hardware Installation 68P09275A22 manual.
NEC The Network Element Configuration (NEC) files contains site type and equipage data information and passes it directly to the LMF during optimization. The number of modem frames, DMC shelves, MCC–1X boards (per cage), and XMI 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 OMC-R. Failure to use the correct NEC files can cause system errors. Failure to use the correct NEC files log into a site can cause incorrect calibration information to be generated.
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.
CAUTION Always wear a conductive, high impedance wrist strap while handling any circuit card/module to prevent damage by ESD. After removal, the card/module should be placed on a conductive surface or back into the anti-static shipping container.
2-2
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Initial Installation of Boards/Modules
Initial Installation of Boards/Modules Follow the procedure in Procedure 2-1 to verify the initial installation of boards/modules.
Procedure 2-1 1
Initial Installation of Boards/Modules
Refer to the site documentation and install all boards and modules into the appropriate shelves as required. Verify they are NOT SEATED at this time.
2
NOTE The DMC Shelf is shown in 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.
68P09309A80-2
2-3
FOA
OCT 2010
Initial Installation of Boards/Modules
Figure 2-1
Chapter 2: Preliminary Operations
DMC Shelves
24
2 SER 4
5
6
7 MCC
8
25
26
27
28
1 CSM 2
HSO or MSO
CSM
MCC MCC MCC MCC
SER
SER 3
HSOMSO CCD
CCD2
CCD1
23
1 ESD
CSM
22
4
MCC MCC MCC MCC
21
2 3 MCC
SER
1
SER
GLI MCC MCC MCC MCC 2 GLI 4
GLI MCC MCC MCC MCC
GLI
AMR
1 1 AMR GLI 2 3
GLI
Power Supply
1 POWER 2
AMR
Power Supply
EN 1 EN 2 EN 3 EN 1 EN 2 EN 3 SPAN A SPAN B
FAN 1
FAN 2
Fully Populated DMC ti-cdma-00099.eps
2-4
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
DMC Backplane Configuration Switch
DMC Backplane Configuration Switch Each DMC Backplane has an associated network address that is defined by the DIP switch settings on its backside within the DMC. Verification of the DIP switch settings for a single BTS is not required since it is preset by the factory. For reference see Figure 2-2.
Objective 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 pre-power-up tests: •
Digital Multimeter (DMM)
CAUTION Always wear a conductive high impedance wrist strap while handling 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: •
Receive RF cabling - up to 6 RX cables (12 for dual band)
•
Transmit RF cabling - up to 3 TX cables (6 for dual band)
•
GPS
NOTE There are initially 3 TX/RX and 3 RX DIV cables connected. Antennas and GPS do not have to be connected before power up.
DC Power Pre-test (BTS Frame) Before applying any power to the BTS frame, follow the procedure in Procedure 2-2 while referring to Figure 2-3 to verify there are no shorts in the BTS frame DC distribution system.
2-6
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 2-2 1
DC Power Pre-test (BTS Frame)
DC Power Pre-test (BTS Frame)
Physically verify that all DC power sources supplying power to the frame are OFF or disabled.
2
3
On each frame: •
Unseat all circuit boards (except CCD cards) in the DMC shelves, but leave them in their associated slots.
•
Set DMC shelf circuit breaker to the OFF position by pulling out DMC circuit breaker located on the power distribution unit panel.
•
Set XMI breakers to the OFF position by pulling out the XMI breakers (4 breakers, labeled XMI 1 through XMI 4) located on the power distribution panel.
•
Set CRMS, EBR1 and EBR2 circuit breakers to the OFF position by pulling out their respective circuit breaker located on the power distribution panel.
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). •
4
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).
Set the DMC breaker to the ON position by pushing it IN.
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. 5
Insert and lock the DC/DC converter modules for the DMC shelves and into their associated slots one at a time. Repeat step 3. A typical response is that the ohmmeter steadily climbs in resistance as capacitors charge, finally indicating approximately 500 Ω.
6
CAUTION Verify the correct power/converter modules by observing the locking/retracting tabs. Insert and lock all remaining circuit boards and modules into their associated slots in the DMC shelf. Repeat step 3 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 Ω.. Continued
68P09309A80-2
2-7
FOA
OCT 2010
DC Power Pre-test (BTS Frame)
Procedure 2-2 7
Chapter 2: Preliminary Operations
DC Power Pre-test (BTS Frame) (Continued)
Set the XMI breakers ON by pushing them in. Repeat step 3 after turning on each breaker. •
A typical response is that the ohmmeter will steadily climb in resistance as capacitors charge, stopping at approximately 500 Ω.
WARNING Once powered up, note whether the HOT sticker is fully visible. If so, do not touch the metal surfaces of the XMI with unprotected hands. The HOT sticker will become fully visible when the XMI metal case temperature reaches 50°C. However, the sticker may be partially visible at lower case temperatures.
Figure 2-3
Circuit Breakers on PDU Circuit Breakers on Circuit Breaker Panel
DC Input Power Connectors
DMC (90A)
XMI 1 (90A)
XMI 2 (90A)
To DMC
To XMI 1
CRMS EBR 1 EBR 2 (10A) (10A) (10A)
XMI 3 (90A)
XMI 4 (90A)
PDU Circuit Breaker Panel
To XMI 2
To XMI 3
To XMI 4
+27V DC Output Power (3-pin Connectors located behind TX Combiner not shown) ti-cdma-000101-ALT.eps
2-8
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Initial Power Up Tests and Procedures
Initial Power Up Tests and Procedures ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Power-up Procedures
WARNING Potentially lethal voltage and current levels are routed to the BTS equipment. This test must be performed with a seocnd 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): •
The positive power cable is red.
•
The negative power cable 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-1.
Table 2-1
DC Input Power Cable Guidelines Wire Size
Maximum Cable Length 30.38 m (100 ft)
107 mm2 (AWG #4/0)
54.864 m (180 ft)
185 mm2 (350 kcmil)
Greater that 54.864 m (180 ft)
Not recommended
WARNING 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. Loose power cables may cause a fire.
68P09309A80-2
2-9
FOA
OCT 2010
Common Power Supply Verification
Chapter 2: Preliminary Operations
Common Power Supply Verification The procedure in Procedure 2-3 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 removal and installation of any card/module should be placed on a conductive surface or back into the anti-static bag in which it was shipped.
Procedure 2-3
Common Power Supply Verification
1
Physically verify that all DC power sources supplying the frame are OFF or disabled.
2
On each frame: •
Unseat all circuit boards (except CCD cards) in the DMC shelf and XMI, but leave them in their associated slots.
•
Set breakers to the OFF position by pulling out DMC and XMI breakers (see Figure 2-3 for breaker panel layout if required).
•
DMC Cage breaker is labeled DMC.
•
Power Supply Card breakers on the DMC I/O labeled POWER 1 and 2.
•
XMI breakers are labeled XMI 1 through XMI 4.
3
Inspect input cables, verify correct input power polarity via decal on top of frame.
4
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.
5
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 +27 V BTS: +27 Vdc nominal
Initial Power-up (BTS) The procedure must be performed on each frame after input power from the common power supply has been verified. Follow the steps in Procedure 2-4 to apply initial power to the cards/modules within the frame itself, verifying that each is operating within specification.
2-10
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 2-4
Initial Power-up (BTS)
Initial Power-up (BTS)
1
At the BTS, set the DMC (POWER) power distribution breaker (see Figure 2-3) to the ON position by pushing in the breaker. Ensure that POWER 1 and 2 breakers on DMC I/O are engaged.
2
Insert the DMC fan modules. Observe that the fan modules come on line.
3
CAUTION Verify the correct DMC power supplies by observing the locking/retracting tabs.Insert and lock the 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 power supply is indicated and should be replaced before proceeding.
4
Seat and lock all remaining circuit cards and modules in the DMC shelf into their associated slots.
5
Set the XMI breakers to the ON position (per configuration) by pushing them IN. See Figure 2-3 for breaker panel layout. •
Confirm LEDs on XMI LEDs light.
WARNING Avoid touching the metal surfaces of the XMI with unprotected hands when the HOT sticker is clearly visible. The HOT sticker will become fully visible when the XMI metal case temperature reaches 50°C. However, the sticker may be partially visible at lower case temperatures. 6
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 +27 V BTS: +27 Vdc nominal
68P09309A80-2 OCT 2010
2-11
FOA
Initial Power-up (BTS)
Chapter 2: Preliminary Operations
2-12
68P09309A80-2
FOA
OCT 2010
Chapter
3 Acceptance Test Procedures ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
68P09309A80-2 OCT 2010
3-1
FOA
Reduced Acceptance Test Procedures — Introduction
Chapter 3: Acceptance Test Procedures
Reduced Acceptance Test Procedures — Introduction ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction General The Reduced Acceptance Test Procedures (ATP) allow Cellular Field Engineers (CFEs) to run a brief acceptance tests to verify all BTS subsystem devices equipped in the NEC using the WinLMF and the test equipment it supports.
WinLMF User Interface This chapter provides procedures for performing the acceptance testing from the WinLMF GUI environment, the recommended method. The GUI provides the advantages of simplifying the WinLMF user interface, reducing the potential for mis-keying commmands and associated parameters, and speeding up the execution of complex operations involving multiple command strings. If it is believed the WinLMF command line interface (CLI) will provide additional insight into ATP operation or unexpected test results, refer to WinLMF 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 WinLMF through the GPIB, only the test equipment models supported by the WinLMF can be used.
CAUTION 1.
Before using the WinLMF, read the Developer Release Notes for WinLMF section in the WinLMF Help function on-line documentation 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 BTSes.
3.
DO NOT substitute test equipment with other models not supported by the WinLMF.
Test Equipment Set Calibration Refer to Appendix G Optimization and Calibration Procedures for detailed interconnection information needed for calibrating equipment, cables, and other test equipment set components.
3-2
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Reduced ATP
XMI Cable Check After the WinLMF is connected to the BTS, perform the XMI cable check procedure to verify that they are properly installed.
Reduced ATP The CFE must perform these procedures (minimal recommendation): 1.
CDMA 1X TX Audit Test
2.
CDMA 1X RX RSSI Test
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 B-3) in Appendix B FRU Optimization/ATP Test Matrix 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. These tests are discussed in Appendix H Optional Full Acceptance Test Procedures.
68P09309A80-2
3-3
FOA
OCT 2010
Preparing the WinLMF
Chapter 3: Acceptance Test Procedures
Preparing the WinLMF ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview Before optimization can be performed, the WinLMF application software must be installed and configured on a computer platform meeting Motorola-specified requirements (see Recommended Test Equipment and Software in Chapter 1 Introduction). Software and files for installation and updating of the WinLMF are provided on CD ROM disks. The following installation items must be available: •
WinLMF Program on CD ROM
•
NEC files for each supported BTS (on diskette or available from the CBSC)
The following section provides information and instructions for installing and updating the WinLMF software and files.
Overview of Packet BTS Files There are two NEC files. These are: •
NEC Base (NECB) file
•
NEC Journal (NECJ) file
The NECB contains the baseline configuration information and is analogous to the circuit CDF, while the NECJ contains all the changes made to the configuration since the last time the NECB was re-generated. Once the NECJ reaches 80% of its maximum size, the NECB is re-generated by the OMC-R, and all updates from the NECJ file are rolled into it. The NEC files play much more extensive role than the previously-used CDF files.
3-4
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
WinLMF File Structure Overview
Additional important, WinLMF-related facts about the the NEC files are: •
Both files (NECB and NECJ) are in eXtensible Markup Language (XML) format.
•
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.
•
Both files can be viewed in any XML viewer (e.g., Internet Explorer V5.0 and higher) or text/word processing program (e.g., Wordpad).
•
These files will be created by OMC-R from MIB and reflect the BTS provisioning.
•
These files will be regenerated for each software release upgrade on the system for each BTS.
•
The NEC files will reside on GLI3s operating in packet mode. The NEC files in the GLI3s will be synchronized periodically with the OMC-R MIB file.
•
Both the NECB and NECJ files contain a SoftwareVersion field in their header section indicating the system release version of these files.
•
The packet WinLMF uses NECB--bts#.xml and NECJ--bts#.xml files, which are copies of the NEC files.
•
A GLI3 operating in packet mode will need the NECB and NECJ files for site initialization.
•
The scope of the NEC files has grown much broader than that of the CDF and has much more BTS-centric 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, site-unique information for the BTS must be included in the NEC file for the site to operate properly.
WinLMF File Structure Overview The WinLMF uses a :\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 WinLMF. Except for the bts-# folders, these folders are created as part of the the WinLMF installation. Refer to the WinLMF On-Line Help for a complete description of the folder structure.
68P09309A80-2
3-5
FOA
OCT 2010
WinLMF Home Directory
Chapter 3: Acceptance Test Procedures
Figure 3-1
WinLMF Folder Structure
(x:\) x:\ folder cdma folder bts-# folders (A separate folder is required for each BTS where bts-# is the unique BTS number; for example, bts-163.) 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 ti-cdma-00102.eps
NOTE The loads folder and all the folders below it are no longer contained on the WinLMF CD as of WinLMF 2.16.4.1. When installing WinLMF software on a system that has never contained WinLMF software before, the user will need to create these folders manually. When installing a new version of WinLMF onto a PC already containing WinLMF software, any existing folders will be unaffected.
WinLMF Home Directory The CDMA WinLMF 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 WinLMF home directory will be referred to with the generic convention of: :\ Where: = the WinLMF computer drive letter where the CDMA WinLMF home directory is located. = the directory path or name where the CDMA WinLMF is installed.
3-6
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Filename Conventions and Directory Location
Filename Conventions and Directory Location NEC Files The naming conventions for the NECB and NECJ files are: NECB - - bts#.xml NECJ - - bts#.xml Where: = This field can contain any text characters, but generally corresponds to software tape number information # = BTS ID number from the OMC. For example: BTS 12 running on system tape 2.22.0.99.17 might have NECB/NECJ filenames NECB–2.22.0.99.17–BTS12.xml and NECJ–2.22.0.99.17–BTS12.xml, respectively While the system provides both the NECB and NECJ files, the WinLMF is only capable of reading the NECB file. It is therefore necessary to ensure that any changes that appear in the NECJ file are rolled into the NECB prior to using that NECB in the WinLMF. 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 \cdma\bts-# directory for the BTS to which they apply. NEC files are available on the OMC–R in the bts-# directory located in /screl/active/loadable/ Where: # = the actual integer number assigned to the BTS in the RAN to which it is assigned.
Load Information File (LIF) The LIF 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 pre–Packet. The naming convention for the LIF is: NE_LIF.xml The LIF must reside in the \cdma\loads\ directory Where: = the home directory in which the WinLMF is installed, usually C:\wlmf\cdma\loads\ = the exact number of the system software release load with which the BTS is to operate (for example, 2.22.0.99.17). The LIF files are available on the OMC–R in the /screl//loadable/bts/ directory, where tape# is the exact number of the software release load with which the BTS is to operate; for example, SC–2.22.0.99.17.
68P09309A80-2
3-7
FOA
OCT 2010
WinLMF Application Installation
Chapter 3: Acceptance Test Procedures
WinLMF Application Installation This section provides information and instructions for installing and updating the WinLMF application software and files.
NOTE Any time U/WIN is re-installed, the WinLMF application software must also be re-installed. This is because the WinLMF application installation modifies some of the files that are installed during the U/Win installation. These modifications are necessary for proper WinLMF CLI operation. If required, a separate CD ROM of BTS Binaries may be obtained for binary updates. Follow the procedure in Procedure 3-1 to install the WinLMF application program using the WinLMF CD ROM.
Procedure 3-1 1
WinLMF Application Program Installation
Insert the WinLMF Program CD ROM into the WinLMF 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 2.
2
Click on the Start button.
3
Select Run.
4
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 BTS NEC Files to the WinLMF Computer Before logging on to a BTS with the WinLMF computer to execute optimization/ATP procedures, the correct NECB--bts#.xml and NECJ--bts#.xml files must be obtained from the OMC–R and put in a bts–# folder in the WinLMF computer. This requires creating versions of the BTS NEC files on a DOS–formatted floppy diskette and using the diskette to install the NEC files on the WinLMF computer. 3-8
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Copy BTS NEC Files to the WinLMF Computer
NOTE If the WinLMF has FTP capability, the FTP method can be used to copy the NEC files from the OMC–R
NOTE When copying NEC files, comply with the following to prevent BTS login problems with the WinLMF: The numbers used in the NECB--bts#.xml and NECJ––bts#.xml filenames must correspond to the locally assigned numbers for each BTS. The procedure in Procedure 3-2 lists the steps required to transfer the NEC files from the OMC–R to the WinLMF computer. For further information, refer to the WinLMF On-Line Help documentation.
Procedure 3-2
Copying OMC–R NEC Files to the WinLMF
At the OMC–R: 1
Login to the OMC–R workstation.
2
Insert a DOS formatted diskette in the workstation drive.
3
Type eject -q and press the Enter key.
4
Type mount and press the Enter key.
NOTE
5
•
Look for the “floppy/no_name" message on the last line displayed.
•
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.
Change to the directory containing the file by typing cd (for example, cd bts–248) and pressing Enter.
NOTE NEC files are normally available in the bts–# directory located in /screl/active/loadable/ Where: # = the actual integer number assigned to the BTS in the RAN to which it is assigned. 6
Type ls and press Enter to display the list of files in the directory. Continued
68P09309A80-2
3-9
FOA
OCT 2010
Creating a Named HyperTerminal Connection for MMI Sessions
Procedure 3-2 7
Chapter 3: Acceptance Test Procedures
Copying OMC–R NEC Files to the WinLMF (Continued)
With Solaris versions of Unix, create DOS-formatted versions of the NECB––bts#.xml and NECJ––bts#.xml files on the diskette by entering the following command: unix2dos /floppy/no_name/ For example, NECB-2.22.0.99.17-bts248.xml /floppy/no_name/NECB-2.22.0.99.17-bts248.xml
NOTE •
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 WinLMF computer is, therefore, not recommended.
•
Using cp, multiple files can be copied in one operation by separating each filename to be copied 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 NECB–2.22.0.99.17–bts248.xml /floppy/no_name).
8
Repeat step 5 through step 7 for each bts–# that must be supported by the WinLMF.
9
When all required files have been copied to the diskette, type eject and press the key.
10
Remove the diskette from the OMC–R.
On the WinLMF computer: 11
Start the Windows operating system.
12
Insert the diskette into the WinLMF computer.
13
Using Windows Explorer (or equivalent program), create a corresponding bts–# folder in the \cdma directory for each NECB–-bts#.xml and NECJ–-bts#.xml file pair copied from the OMC–R.
14
Use Windows Explorer (or equivalent program) to transfer the NECB*bts#.xml and NECJ*bts#.xml files from the diskette to the corresponding \cdma\bts–# folders created in step 13.
Creating a Named HyperTerminal Connection for MMI Sessions Confirming or changing the configuration data of certain BTS Field Replaceable Units (FRUs) requires establishing an MMI communication session between the WinLMF and the FRU. Using features of the Windows operating system, the connection properties for an MMI session can be saved on the WinLMF computer as a named Windows HyperTerminal connection. This eliminates the need for setting up connection parameters each time an MMI session is required to support optimization. Once the named connection is saved, a shortcut for it can be created on the Windows desktop. Double clicking the shortcut icon will start the connection without the need to negotiate multiple menu levels. Follow the procedure in Procedure 3-3 to establish a named HyperTerminal connection and create a Windows desktop shortcut for it.
3-10
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 3-3
Creating a Named HyperTerminal Connection for MMI Sessions
Creating a Named HyperTerminal Connection for MMI Sessions
1
From the Windows Start menu, select: Programs>Accessories.
2
Select Communications, double click the Hyperterminal folder, and then double click on the Hyperterm.exe icon in the window that opens.
NOTE
3
•
If a Location Information Window appears, enter the required information, then click Close. (This is required the first time, even if a modem is not to be used.)
•
If a You need to install a modem..... message appears, click NO.
When the Connection Description box opens: •
Type a name for the connection being defined (for example, MMI Session) in the Name: window.
•
Highlight any icon preferred for the named connection in the Icon: chooser window.
•
Click OK.
4
NOTE For WinLMF configurations where COM1 is used by anotheer interface such as test equipment and a physical port is available for COM2, select COM2 to prevent conflicts. From the Connect using: pick list in the Connect To box displayed, select the RS-232 port to be used for the connection (e.g., COM1 or COM2 (Win 2000 or Win XP) - or Direct to Com 1 or Direct to Com 2 (Win 98 SE), and click OK. 5
In the Port Settings tab of the COM# Properties window displayed, configure the RS-232 port settings as follows: •
Bits per second: 9600
•
Data bits: 8
•
Parity: None
•
Stop bits: 1
•
Flow control: None
6
Click OK.
7
Save the defined connection by selecting: File>Save.
8
Close the HyperTerminal window by selecting: File>Exit. Continued
68P09309A80-2
3-11
FOA
OCT 2010
Creating a Named HyperTerminal Connection for MMI Sessions
Procedure 3-3 (Continued) 9 10
Creating a Named HyperTerminal Connection for MMI Sessions
Click Yes to disconnect when prompted. Perform the following: •
11
Chapter 3: Acceptance Test Procedures
From the Windows Start menu, select Programs > Accessories
Perform one of the following: •
For Win 2000 or WinXP, select Hyperterminal and release any pressed mouse buttons.
•
For Win98 SE, select Communications and double click the Hyperterminal folder.
12
Highlight the newly created connection icon by moving the cursor over it (WinXP or Win 2000) or clicking on it (Win 98SE)
13
Right click and drag the highlighted connection icon to the Windows desktop and release the right mouse button.
14
From the pop-up menu displayed, select Create Shortcut(s) Here.
15
If desired, reposition the shortcut icon for the new connection by dragging it to another location on the Windows desktop.
3-12
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
WinLMF to BTS Connection
WinLMF to BTS Connection ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Connect the WinLMF to the BTS The WinLMF is connected to the LAN A or B connector located on the top and towards the rear of the DMC (see Figure 3-2).
Procedure 3-4
WinLMF to BTS Connection
1
Disconnect the LAN terminations from both LAN A and B connectors.
2
Connect the WinLMF to the LAN A BNC connector through a 10BASE-T/10BASE-2 Converter.
NOTE •
Xircom Model PE3-10B2 or equivalent can also be used to interface the WinLMF Ethernet connection to the 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.
68P09309A80-2
3-13
FOA
OCT 2010
Connect the WinLMF to the BTS
Figure 3-2
Chapter 3: Acceptance Test Procedures
WinLMF Connection Detail LAN B (BNC) IN OUT
LAN A (BNC) IN OUT
10BASE-T/10BASE-2 CONVERTER CONNECTS DIRECTLY TO BNC T
Basic WinLMF Operation WinLMF Coverage in This Publication There are WinLMF application programs to support maintenance of the CDMA BTSes. All references to the WinLMF in this publication are for the CDMA application program.
Operating Environments The WinLMF application program allows the user to work in the two following operating environments which are accessed using the specified desktop icons: •
Graphical User Interface (GUI) using the WinLMF icon
•
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 WinLMF in either environment includes performing the following: •
Selecting and deselecting BTS devices
•
Enabling devices
•
Disabling devices
•
Resetting devices
•
Obtaining device status
The following additional basic operation can be performed in a GUI environment: Sorting a status report window For detailed information on performing these and other WinLMF operations, refer to the WinLMF On-Line Help .
NOTE Unless otherwise noted, WinLMF procedures in this manual are performed using the GUI environment.
68P09309A80-2
3-15
FOA
OCT 2010
The WinLMF Display and the BTS
Chapter 3: Acceptance Test Procedures
The WinLMF Display and the BTS BTS Display When the WinLMF 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, BTS-812-1 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 WinLMF to recognize the devices installed in the BTS, the BTS NEC files which include equipage information for all the devices in the BTS must be located in the applicable :\\cdma\bts-# folder.
CRMS Probe Display WinLMF does not support CRMS Probe functions.
NOTE The RFDS display is used for the CRMS Probe. CRMS Probe is NOT shown or called out in the WinLMF screens.
Graphical User Interface Overview The WinLMF uses a Graphical User Interface (GUI), which supports the following functions: •
Selecting a device or devices.
•
Selecting an action to apply to selected device(s).
•
Status report window displaying progress of actions taking place and related information.
•
Notification when an action is complete and related information such as indication of success or failure
•
An OK button to close the status report window.
3-16
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Understanding GUI Operation
Understanding GUI Operation The following descriptions are provided to help understand how the GUI operates: •
On the WinLMF login screen, If there is a packet configuration file (NEC) for the BTS, a (P) is added as a suffix to the BTS number. The Self-Managed Network Elements (NE) state of a packet-mode BTS has an X displayed on the front of each card that is under Self-Managed NE control by the GLI3 card. Normally the GLI3 has Self-Managed NE control of all cards as identified with an X. In that state, the WinLMF may only status a card. In order to download code or test a card, the WinLMF must request Self-Managed NE control of the card by using the drop-down menu. The WinLMF 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 WinLMF 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. When the card/module is under WinLMF control the letter X is missing from the front of the device. For detailed information on performing these and other WinLMF operations, refer to the WinLMF On-Lin Help documentation.
Command Line Interface Overview The WinLMF 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. Only one handler can be running at one time. Due to architectural limitations, the GUI must be started before the CLI if it is desired that the GUI and CLI to use the same handler. When the CLI is launched after the GUI, the CLI automatically finds and uses an in-progress 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 running when the user starts the GUI, or if another copy of the GUI is already running when the user starts the GUI), a dialog window displays the following warning message: The CLI handler is already running. This may cause conflicts with the WinLMF. 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.
68P09309A80-2
3-17
FOA
OCT 2010
Logging into a BTS
Chapter 3: Acceptance Test Procedures
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 mcc-- rssi channel=3 sector=5 Refer to the WinLMF CDMA CLI Reference manual for a complete explanation of the CLI commands and their use.
Logging into a BTS Logging into a BTS establishes a communications link between the BTS and the WinLMF. A WinLMF session can be logged into only one BTS at a time.
Prerequisites Before attempting to login to a BTS, ensure the following have been completed: •
The WinLMF is properly connected to the BTS (see Figure 3-2).
•
The WinLMF application program is correctly installed and prepared.
•
A bts-# folder with the correct NEC files exists.
•
Preparing the WinLMF for Connectivity and Configuring the GLI of SC7224 procedures are completed
•
The WinLMF computer was connected to the BTS before starting the Windows operating system and WinLMF software. If necessary, restart the computer after connecting it to the BTS in accordance with Procedure 3-4 and Figure 3-2.
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 OMC-R. Failure to use the correct NEC files can result in invalid optimization. Failure to use
3-18
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Logging into a BTS
the correct NEC files to log into a site can cause incorrect calibration information to be generated.
BTS Login from the GUI Environment Follow the procedure in Procedure 3-5 to log into a BTS when using the GUI environment.
Procedure 3-5 1
BTS GUI Login Procedure
Start the CDMA WinLMF GUI environment by double clicking on the WinLMF desktop icon (if the WinLMF is not running).
NOTE If a warning similar to the following is displayed, select No, shut down other WinLMF sessions which may be running, and start the CDMA WinLMF GUI environment again: The CLI handler is already running. This may cause conflicts with the WinLMF Are you sure you want to start the application? Yes No 2
Click on the Login tab (if not displayed).
3
If no base stations are displayed in the Available Base Stations pick list, double click on the CDMA icon.
4
Click on the desired BTS number.
5
Click on the Network Login tab (if not already in the forefront).
6
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 MGLI-1 in field BTS units. 128.0.0.1 is the default IP address for MGLI-2. 7
Type in the correct IP Port number (normally 9216) if not correctly displayed in the IP Port box. Continued
68P09309A80-2
3-19
FOA
OCT 2010
Logging into a BTS
Chapter 3: Acceptance Test Procedures
Procedure 3-5 8
BTS GUI Login Procedure (Continued)
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 If the MGLI fails to respond, reset and perform the ping process again. If the MGLI still fails to respond, typical problems are shorted BNC to inter-frame cabling, open cables, crossed A and B link cables, missing 50-Ohm terminators, or the MGLI itself. 9
Click on Login. A BTS tab with a graphical representation of the BTS DMC cage is displayed.
NOTE •
If login is attempted to a BTS that is already logged on, all devices will be gray. Otherwise, only devices not in the configuration file will be gray.
•
There may be instances where the BTS initiates a log out due to a system error (that is, a device failure).
•
The MGLI is always OOS_RAM (yellow), after a while it enables iself and checks the software versions of other installed devices.
BTS Login from the CLI Environment Follow the procedure in Procedure 3-6 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 Procedure 3-5 to start the GUI environment and log into a BTS.
Procedure 3-6 1
BTS CLI Login Procedure
Double click the WinLMF CLI desktop icon (if the WinLMF CLI environment is not already running)
NOTE .If a BTS was logged into under a GUI session when the CLI environment was started, the CLI session will be logged into the same BTS, and step 2 is not required. Continued
3-20
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 3-6 2
Logging Out
BTS CLI Login Procedure (Continued)
At the /wlmf CLI prompt, enter the following command: login bts- host= port= where: host = MGLI 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
Logging Out 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 Procedure 3-7 to logout of a BTS when using the GUI environment.
Procedure 3-7
BTS GUI Logout Procedure
1
Click on BTS on the BTS tab menu bar.
2
Click the Logout item in the pull-down menu (a Confirm Logout pop-up message appears).
3
Click on Yes or press the Enter key to confirm logout. The screen display returns to the Login tab.
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 pop-up message appears stating the Continued
68P09309A80-2
3-21
FOA
OCT 2010
Logging Out
Chapter 3: Acceptance Test Procedures
Procedure 3-7
BTS GUI Logout Procedure (Continued)
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
5
If a Logout Error pop-up 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 pop-up.
•
Click Yes in the Logout Error pop-up which appears again.
If further work is to be done in the GUI, restart it.
NOTE •
The Logout item on the BTS menu bar will only log the WinLMF out of the displayed BTS.
•
Logging out of all BTS sessions and exiting the WinLMF can be done by clicking on the File selection in the menu bar and selecting Exit from the File menu list. A Confirm Logout pop-up message will appear.
Logging Out of a BTS from the CLI Environment Follow the procedure in Procedure 3-8 to logout of a BTS when using the CLI environment.
Procedure 3-8
BTS CLI Logout Procedure
1
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- A response similar to the following is displayed: LMF> 12:22:58.028 Command Received and Accepted Command=logout bts-33 12:22:58.028 Command Received and Accepted 12:22:58.028 Command Successfully Completed REASON_CODE="No Reason" Continued
3-22
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 3-8 2
Logging Out
BTS CLI Logout Procedure (Continued)
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....
68P09309A80-2
3-23
FOA
OCT 2010
Establishing an MMI Communication Session
Chapter 3: Acceptance Test Procedures
Establishing an MMI Communication Session ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
For those procedures that require MMI communications between the WinLMF and BTS FRUs, perform the following to initiate the communication session.
Procedure 3-9
Establishing MMI Communication
1
Connect the WinLMF computer to the equipment as detailed in the applicable procedure that requires the MMI communication session and Figure 3-3.
2
If the WinLMF computer has only one serial port (COM1) and the WinLMF is running, disconnect the WinLMF from COM1 by performing the following: •
Click on Tools in the WinLMF window menu bar, and select Options from the pull-down menu list.
WinLMF Options dialog box will appear.
3
•
In the Test Equipment tab of the dialog box, select COM1 in the Comm Port pull-down on the Serial Connection tab.
•
Click the Disconnect Port button on the Serial Connection tab.
Start the named HyperTerminal connection for MMI sessions by double clicking on its Windows 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>
HyperTerminal Connection (e.g.,MMI Session) 4
Once the connection window opens, establish MMI communication with the BTS FRU by pressing the WinLMF computer Enter key until the prompt identified in the applicable procedure is obtained.
3-24
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Establishing an MMI Communication Session
Figure 3-3 CDMA WinLMF Computer Common MMI Connections - Cable CGDSMMICABLE219112 or Fabricated MMI Cable To FRU MMI Connector 8-PIN
LMF COMPUTER
COM1 OR COM2
CABLE PART NUMBEr CGDSMMICABLE219112 OR FABRICATED MMI CABLE (SEE APPENDIX )
DB-9 CONNECTOR
ti-cdma-00104.eps
68P09309A80-2
3-25
FOA
OCT 2010
WinLMF On-Line Help
Chapter 3: Acceptance Test Procedures
WinLMF On-Line Help ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Task oriented online help is available in the WinLMF by clicking on Help in the window menu bar, and selecting LMF Help from the pull-down menu.
3-26
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
WinLMF Connectivity Flowchart
WinLMF Connectivity Flowchart ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
WinLMF Connectivity Flowchart Use the flowchart as an aid in determining connectivity to the WinLMF for an OOS or INS BTS.
68P09309A80-2
3-27
FOA
OCT 2010
WinLMF Connectivity Flowchart
Figure 3-4
Chapter 3: Acceptance Test Procedures
WinLMF Connectivity Flowchart
Start LMF Connection
Y Connected to Backhaul? Unconnected BTS Interrupted LMF oeration Return to LMF testing
BTS In Service
N
Y
Unconnected BTS Operational code load Typical site install
N
Previous LMF connection?
Connected BTS Correct code load Troubleshooting or repair verification
N
Y 2.17.0.50.6 or later SW?
Unconnected BTS Unknown code load Site recovery
N
1. Prepare LMF for Connectivity 2. Establish LMF Connectivity to SC7224 with BTS OOS
1. Prepare LMF for Connectivity 2. Configuring the GLI of SC7224 3. Establish LMF Connectivity to SC7224 with BTS OOS
1. Prepare LMF for Connectivity 2. Configuring and recovering the GLI of SC7224 3. Establish LMF Connectivity to SC7224 with BTS OOS
LMF Based Testing
1. Prepare LMF 2. Establish LMF Connectivity with SC7224 with BTS INS
Return to Default Settings
LMF Connection Terminated
ti-cdma-00105.eps
3-28
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Flow Chart Table
Flow Chart Table ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Flow Chart Table The following table describes how to answer the questions (diamond shapes) in the flow chart Figure 3-4. Only the GLI in slot 1 should be inserted into the BTS. All other GLIs are to be disconnected from the backplane. All of the commands and responses listed in the table are executed/read from the GLI using hyper-terminal and GLI MMI connection as defined by Procedure 3-9. Question
Description
Connected to Backhaul?
A system is connected to the backhaul will have OMC-R connectivity. If it does not have connectivity to an OMC-R, it is not connected to the backhaul even if the span line cables are connected. To determine the existence of a backhaul connection use the GLI MMI to get the synch status as indicated below. If the two bolded conditions do not show the indicated responses, the SC7224 is not connected to the backhaul. GLI3> synch status 07.11.2005 18:33:14 MGLI-426-1 CC PRESENT BTS-CDMA GLI: Active Golden Mode SYNCH Status: IDLE Substate: None Current\Last Management Audit Job Params ====================== Init type: OMCR Committed Software Load: 2.17.0.50.6 NECF Baseline Version: 0x6857 NECF Journal Version: 0x970 LIF Location IP: 10.100.32.5 LIF Filepath: /screl/sc-2.17.0.50.6/loadable/bts/NE_LIF NECB Location IP: 10.100.32.5 NECB Filepath /screl/active/loadable/bts-426/NECB-2.17.0.50.6-BTS26.xml ======================
Question
Description Any other response in the bolded areas.
BTS In-Service?
Answer
Answer NO
There are two requirements for the BTS to be In-Service:.
1.
None of the devices that would cause a Sector Carrier not to be INS_ACT can be locked. This has to be checked via the OMC-R using the Display BTS Status command. Locked devices will prevent the WinLMF from keying up the carriers as needed for testing..
2.
The SC7224 must have a connection with the MM. Use the GLI MMI to execute the lum display state as shown below to check that the BTSRALINK States are ENA_ACT. Continued
68P09309A80-2
3-29
FOA
OCT 2010
Flow Chart Table
Chapter 3: Acceptance Test Procedures
Question
Description GLI3> lum display state 06.09.2005 12:39:18 GLI-006-3 CC PRESENT BTS-CDMA 16.4.0.0 BTSRALINK STATES BTSRALINK 0 is in has NO DEP and is in state ENA_ACT
Answer YES
CARRIER STATES CARRIER 0 is in has NO DEP and is in state OOS_NRML CARRIER DO STATES GLI3> lum display state 06.09.2005 12:39:18 GLI-006-3 CC PRESENT BTS-CDMA 16.4.0.0 BTSRALINK STATES BTSRALINK 0 is in has NO DEP and is in state OOS_PROXY CARRIER STATES CARRIER 0 is in has NO DEP and is in state OOS_NRML CARRIER DO STATES Question
Description
Previous WinLMF Connection?
An SC7224 that had been connected to the WinLMF and had not had its GLI returned to the default state can skip some of the procedural steps to reconnect to the WinLMF. Use the GLI MMI to execute config btsrtr current command as shown below to determine if the BTS Router Override parameter is set or not set. If the SC7224 was previously connected to an WinLMF and not returned to its default state if the BTS Router Override is set.
2.17.0.50.6 or later software
NO
Answer
GLI3> config btsrtr current BTS Router Override set OMCR IP address: 128.0.0.48 Login/password: anonymous/hotspur
YES
GLI3> config btsrtr current BTS Router Override Not set OMCR IP address: Login/password: iluser/foolbar
NO
Software version 2.17.0.50.6 or later will allow the WinLMF to automatically upgrade the SC7224 software version if the software version of the WinLMF is more recent than is current running on the GLI. Otherwise, the software loaded on the GLI must be recovered to software version 2.17.0.50.6 or later to allow connection to the WinLMF. To determine the current software version on the SC7224, use the GLI MMI to execute the sync status commands as shown below. The Committed Software Load must be 2.17.0.50.6 or later to answer YES to this question. GLI3> synch status 01.06.1980 00:06:02 MGLI-041-1 CC PRESENT BTS-CDMA 2.17.0.50.6 GLI: Active Golden Mode SYNCH Status: IDLE Substate: NONE Current\Last Management Audit Job Params ====================== Init type: OMCR Committed Software Load: 2.17.0.50.6 NECF Baseline Version:
YES
Continued
3-30
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Question
Flow Chart Table
Description
Answer
0x4df9 NECF Journal Version: 0x4df9 LIF Location IP: 128.0.0.48 LIF Filepath : cdma/loads/2.17.0.50.6/NE_LIF.xml NECB Location IP: 128.0.0.48 NECB Filepath cdma/bts-41/NECB-2.17.0.50.6-BTS41.xml ====================== This is an example of a system that hasn't been able to synch up with the OMC too many times. This system has defaulted to a circuit load. In the circuit load the synch status command is not supported. The output will be as follows: GLI3> synch status CP: Invalid command 01.06.1980 00:01:05 MGLI-000-1 OOS_ACT BTS-CDMA 16.41.20.20
68P09309A80-2
NO
3-31
FOA
OCT 2010
Preparing WinLMF Connectivity to SC7224
Chapter 3: Acceptance Test Procedures
Preparing WinLMF Connectivity to SC7224 ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction The following procedure is required to connect an WinLMF to an SC7224 that does not have a connection to the transport network. The SC7224 delivered from the factory is configured to search for an OMC-R via the transport network. If that connection cannot be established, the steps of this procedure are required to enable the WinLMF to connect. An SC7224 that is connected to the transport network, is provisioned, and has synchronized with the OMC-R will need to follow the procedures in Procedure 3-10, Preparing the WinLMF for Connectivity and Procedure 3-11, step 1 and step 2 of the procedure for Configuring the SC7224 GLI. After that is completed, the procedure in Procedure 3-13 Establish WinLMF to SC7224 Connection are used to achieve the WinLMF connection. This procedure will result in the GLI taking a new code load from the WinLMF if the version of system code contained on the WinLMF is not equal to that contained on the GLI. In general, the WinLMF should contain the same code load as is shipped on the SC7224 from the factory. Doing so will minimize the time it takes to verify the installation of the SC7224 . Once connected to the backhaul network, the SC7224 will easily code load to the current system configuration from the OMC-R.
Preparing the WinLMF for Connectivity The procedure described in Procedure 3-10 assumes the WinLMF IP address is 128.0.0.48. If the IP address of the WinLMF being used is not that address, substitute the IP address of the WinLMF being used for 128.0.0.48. Following completion of the procedure the WinLMF terminal will be properly configured for use with a particular SC7224. The WinLMF must have the correct NECB--bts-#.xml and NECJ--bts-#.xml files for the specific SC7224 stored in the WinLMF file directory. The NECB and NECJ files are typically obtained from the OMC-R using the procedure in Procedure 3-2 The proper directory structure for storage of the files for a particular BTS is shown in Figure 3-5.
Procedure 3-10
Procedure for WinLMF Connectivity Continued
3-32
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 3-10 1
Preparing the WinLMF for Connectivity
Procedure for WinLMF Connectivity (Continued)
[WinLMF] NECB file preparation: Open the NECB file for the specific bts-# with a suitable editor (Microsoft WordPad) and carefully make modifications to the NECB parameters.
NOTE The NECB is a very large file that requires caution be used to ensure that the correct attributes are modified.
•
Set neManagerLocation and all server parameters in NECB to IP address of WinLMF PC:
•
Set GLI router configuration
•
Set router parameters to IP address of GLI1: ... ... ... ... ... ...
NOTE The “. . ." indicates there may be one or more lines in the NECB between the desired ID and the attribute to be changed. Continued
68P09309A80-2
3-33
FOA
OCT 2010
Preparing the WinLMF for Connectivity
Procedure 3-10
• 2
Chapter 3: Acceptance Test Procedures
Procedure for WinLMF Connectivity (Continued)
Save the modified NECB file back to the bts-# directory
[WinLMF] Code/data preparation: The code files that are installed on the WinLMF with these steps will be those that are loaded onto the SC7224 if their versions are different from those already loaded on the BTS. If the desire is to not code load from the WinLMF, then the code version stored on the WinLMF must be identical to that already installed on the SC7224. •
Obtain the code files which are going to be downloaded to the GLI and put them in WLMF_HOME>/cdma/loads//code directory. The code files are obtained from the desired system release file and have the following names for each of the SC7224 components. All files components must be included in the /code directory. GLI code file: gli_ram.bin.0108 MCC code files: pmcp_ram.bin.0c04 mcp_rom.bin.0c04 CSM code files: csm_ram.bin.0801 csm_rom.bin.0801 SER code files: ser_ram.bin.1000 XMI code files: xmi_ram.bin.1040
•
Obtain the data files from the desired system release file and put them in /cdma/loads//data directory
•
Obtain the NE_LIF.xml file from the desired system release file and put it in /cdma/loads/ directory
•
Perform Update LIF operation from WinLMF with this code (Tools->Update LIF menu item)
NOTE Release software code and data files are stored at /cdma/loads//code and /cdma/loads/ / data directories, respectively.Binary files (*.bin*) have to be put in code subdirectory, and data files (*.dds*) in data subdirectory.The NE_LIF.xml file describes binary files versions and should be placed in /cdma/loads/ directory.(See example in NE_LIF.xml example file section of this document.) If the binary file versions in the NE_LIF.xml file do not match the binary file versions contained on the GLI, a code load will occur as a result of following the steps of this procedure. If a code load is not desired, the versions identified in the NE_LIF.xml file must match the versions of the code contained on the GLI. Directory example: When system tape version has a value 2.17.0.50.0 there should be /cdma/loads/ directory. All binary files should be put in /cdma/loads//code directory. Continued
3-34
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 3-10
Preparing the WinLMF for Connectivity
Procedure for WinLMF Connectivity (Continued)
All data files should be put in /cdma/loads//data directory. NE_LIF.xml file should be put in /cdma/loads// directory See Figure 3-5. Please refer Help -> LMF Help File and Directory Structure section for more detailed description of naming convention in WinLMF 3
[WinLMF] Set NextLoad to the new code version (Tools->Update NextLoad menu item)
Figure 3-5
Example of Directory Structure
wlmf
cdma bts-221
bts-245
bts-248 bts-303
bts-485 loads
2.17.0.50.0
code
data
ti-cdma-00106.eps
68P09309A80-2
3-35
FOA
OCT 2010
Configuring and Recovering the GLI of SC7224
Chapter 3: Acceptance Test Procedures
Configuring and Recovering the GLI of SC7224 ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Configuring and Recovering the GLI Follow the procedure in Procedure 3-11 to configure and recover the SC7224 GLI for use by the WinLMF. This procedure is required when the GLI software release is earlier than 2.17.0.50.6. All GLI interfaces are via the MMI interface on the GLI located in slot 1. Use the hyper-terminal and GLI MM connection procedure of Procedure 3-9 to connect to the GLI in slot 1.
Procedure 3-11 1
2
3
Procedure to Configure and Recover the GLI
[BTS] Initial setup. •
Only the GLI in slot 1 should be inserted in the frame. All other GLIs are to be disconnected from the back plane.
•
Remove all LAN B connections and connect LAN A to the WinLMF using a suitable 10Base2 to 10BaseT adapter.
[GLI] Clear all GLI configuration files and boot settings. •
From the GLI> prompt, reset the GLI using CTRL+x.
•
Enter [VXWorks Boot] after GLI reset by pressing the ENTER key during the displayed countdown.
•
List all the files in the GLI configuration directory by entering ls /nvram00/config/ at the [VXWorks Boot] prompt.
•
Remove each listed file from the GLI configuration directory by entering: rm /nvram00/config/ at the [VXWorks Boot] prompt for each file. For example: rm /nvram00/config/hlp_param.txt to remove the hlp_param.txt file.
•
Clear all boot configuration settings by entering 'C' at the [VXWorks Boot] prompt, and then choose all default settings with '5' and progressing backwards to 1. The default setting by entering a '.' for each default attribute.
•
Set the router to duplex by entering rtrmode_set duplex at the [VXWorks Boot] prompt.
[WinLMF] Start FTP server on the WinLMF •
Use Tools->FTP Server->Start to initialize the LMF FTP server Continued
3-36
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 3-11 4
Configuring and Recovering the GLI
Procedure to Configure and Recover the GLI (Continued)
[GLI] Set GLI to use WinLMF as default code server •
Enter 'C' at the [VxWorks Boot] prompt to change the GLI boot configuration settings
•
Choose '3' to change the boot configuration setting for the 10base-2 interface (LAN-A)
•
Select 'N' to not use the standard boot configuration settings
•
Enter the BOOTSERVER IP address as that of the WinLMF, 128.0.0.48
•
Use '.' to accept the default settings for BOOTGW, IPADDRESS and NETMASK
•
For FILENAME enter the full WinLMF path to the GLI code file 'cdma/loads//code/'
•
Set the RETRY count to 9.
•
Enter '@' at the [VxWorks Boot] prompt to boot up the GLI using the new settings. The GLI will proceed to boot up using the code image on the WinLMF and will FTP that image to its volatile memory.
– example output on GLI after @ – [VxWorks Boot]: @ boot device : motscc unit number : 0 processor number : 0 file name : /cdma/loads//code/gli_ram.bin.0108 inet on ethernet (e) : 128.0.0.2:ffffff80 host inet (h) : 128.0.0.48 gateway inet (g) : 128.0.0.126 user (u) : anonymous ftp password (pw) : user flags (f) : 0x0 Loading... FTP'ing to /ram00/loads/gli_ram.bin.0108... Validating checksums...Image checksum valid 5317072 Upgrade present... Version match! No upgrade necessary...Done. Starting at 0x10000... Continued
68P09309A80-2
3-37
FOA
OCT 2010
Configuring and Recovering the GLI
Procedure 3-11 5
Chapter 3: Acceptance Test Procedures
Procedure to Configure and Recover the GLI (Continued)
[GLI] Set the GLI boottype to FILESYSTEM and the GLI3 volatile memory location •
At the [VxWorks Boot] prompt use CTRL+x to reboot the GLI
•
Enter [VxWorks Boot] after GLI reset by pressing the ENTER key during the displayed countdown.
•
Enter C at the [VxWorks Boot] prompt to change the GLI boot configuration settings
•
Choose '2' to change the boot configuration setting for the FILESYSTEM boot type
•
Enter the BOOTSERVER IP address as that of the WinLMF, 128.0.0.48
•
Use '.' to accept the default settings for BOOTGW, IPADDRESS, and NETMASK
•
For FILENAME enter the GLI volatile memory file path and file name '/ram00/loads/gli_ram.bin.0108'
•
Set the RETRY count to 9.
•
Enter '@' at the [VxWorks Boot] prompt to boot up the GLI using the new settings. The GLI will proceed to boot up using the code image in its volatile memory. Once it successfully boots from that code image, it will transfer that image to a non-volatile memory location.
– example output on GLI after @ – +————————————– |The following is a list of the current |Configuration Parameters from the file |/nvram00/config/bootcfg.txt: +————————————– BOOTTYPE=FILESYSTEM BOOTSERVER=128.0.0.48 BOOTGW=128.0.0.126 FILENAME=/ram00/loads/gli_ram.bin.0108 RETRY=2 [VxWorks Boot]: @ boot device : tffs=0,0 unit number : 0 processor number : 0 file name : /ram00/loads/gli_ram.bin.0108 inet on ethernet (e) : 128.0.0.2:ffffff80 host inet (h) : 128.0.0.48 user (u) : anonymous ftp password (pw) : user flags (f) : 0x0 Attaching to TFFS... Loading /ram00/loads/gli_ram.bin.0108... Validating checksums...Image checksum valid 5414992 Continued
3-38
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 3-11
Configuring and Recovering the GLI
Procedure to Configure and Recover the GLI (Continued)
Upgrade present... Versions match! No upgrade necessary...Done. Starting at 0x10000... 6
[GLI] Ensure that file motfcc1_bootcfg.txt exists in configuration directory on GLI •
Use the display file /nvram00/config/motfcc1_bootcfg.txt command at the GLI3> prompt to check if that file exists.
•
Proceed to step 7 if file exists. Otherwise, GLI will display the following message:
Do the following to create and upload this file to GLI3: Using a text editor on local PC, create a new text file with the following two lines of content: IPADDRESS=192.168.146.32 NETMASK=0xffffff00
Save the text file to any desired location on the local PC with the filename motfcc1_bootcfg.txt
Use local PC FTP client to transfer the new text file motfcc1_bootcfg.txt to the GLI3 card directory /nvram00/config/ directory with the following commands/entries: ftp 128.0.0.2 user: anonymous password: hotspur cd /nvram00/config put motfcc1_bootcfg.txt 7
[GLI] GLI has valid SC7224 code image, finish setup to connect to the WinLMF. •
Use the config btsrtr override command at the GLI3> prompt to set the IP address of the WinLMF PC as the address of the code server. The user login ID is anonymous and the password is hotspur. The MMI interface will occur as follows:
GLI3> config btsrtr override COMMAND SYNTAX: config btsrtr override omcr_ip_addr boot_server_login boot_server_password Next available options: STRING - omcr_ip_addr : OMCR IP address (ddd.ddd.ddd.ddd), or enter [.] to use current setting. > 128.0.0.48 Continued
68P09309A80-2
3-39
FOA
OCT 2010
Configuring and Recovering the GLI
Procedure 3-11
Chapter 3: Acceptance Test Procedures
Procedure to Configure and Recover the GLI (Continued)
COMMAND SYNTAX: config btsrtr override omcr_ip_addr boot_server_login boot_server_password Next available options: STRING - boot_server_login : Boot Server FTP login, or enter [.] to use current setting. > anonymous COMMAND SYNTAX: config btsrtr override omcr_ip_addr boot_server_login boot_server_password Next available options: STRING - boot_server_password : Boot Server FTP password, or enter [.] to use current setting. > hotspur 01.06.1980 00:00:34 MGLI-000-1 CC PRESENT BTS-CDMA 17.00.202.73 NOTICE: This MMI should only be used in a test environment. It will set parameters that are used to work around getting real DHCP parameters onto the GLI. If you have a router on your BTS, you should use it to supply these parameters. OMCR IP address: 128.0.0.48 Boot Server login/password: anonymous/hotspur YOU NEED TO BOOT YOUR BOARD TO SET INTO THESE PARAMETERS.
•
Reset GLI by using CTRL+X at the MMI interface
•
Enter the synch reset off command at the GLI3> prompt. This command prevents the GLI from resetting when it is unable to synchronize with an OMC-R.
synch reset off 01.06.1980 00:00:13 MGLI-000-1 CC PRESENT BTS-CDMA 17.00.202.73 Synch resets for timers have been disabled. This is NOT saved across boots and should only be used in test environments.
3-40
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Configuring the GLI of SC7224
Configuring the GLI of SC7224 ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Configuring the GLI Follow the procedure in Procedure 3-12 to configure the SC7224 GLI for use by the WinLMF. All GLI interfaces are via the MMI interface on the GLI located in slot 1. Use the hyper-terminal and GLI MMI connection procedure of Procedure 3-9 to connect to the GLI in slot 1.
Procedure 3-12 1
Procedure to Configure the GLI
[BTS] Initial Setup. •
Only the GLI in slot 1 should be inserted in the frame.
•
Remove all LAN B connections and connect LAN A to the WinLMF using a suitable 10Base2 to 10Base T adapter.
2
Use Tools->FTP Server->Start to initialize the WinLMF FTP server.
3
[GLI] GLI has valid SC7224 code image, finish setup to connect to the WinLMF. •
Use the config btsrtr override command at the GLI3> prompt to set the IP address of the WinLMF PC as the address of the code server. The user login ID is anonymous and the password is hotspur. The MMI interface will occur as follows:
GLI3> config btsrtr override COMMAND SYNTAX: config btsrtr override omcr_ip_addr boot_server_login boot_server_password Next available options: STRING - omcr_ip_addr: OMCR IP Address (ddd.ddd.ddd.ddd), or enter [.] to use current setting. >128.0.0.4˘ 8 COMMAND SYNTAX: config btsrtr override omcr_ip_addr boot_server_login boot_server_password Next available options: STRING - boot_server_login: Boot Server FTP login, or enter [.] to use current setting. >anonymous COMMAND SYNTAX: config btsrtr override omcr_ip_addr boot_server_login boot_server_password Next available options: STRING - boot_server_password: Boot Server FTP password, or enter [.] to use current setting. >hotspur 01.06.1980 00:00:34 MGLI-000-1 CC PRESENT BTS-CDMA 17.00.202.73 NOTICE: This MMI should only be used in a test environment. It will set parameters that are used to work around getting real DHCP parameters onto the GLI. The router on the BTS should be used to supply these parameters. OMCR IP Address: 128.0.0.48 Boot Server Login/password: anonymous/hotspur Continued
68P09309A80-2
3-41
FOA
OCT 2010
Configuring the GLI
Chapter 3: Acceptance Test Procedures
Procedure 3-12
Procedure to Configure the GLI (Continued)
THE GLI NEEDS TO BE BOOTED TO SET THESE PARAMETERS.
•
Reset GLI by using CTRL+X at the MMI interface.
•
After the GLI boots up, enter the synch reset off command at the GLI3> prompt. This command prevents the GLI from resetting when it is unable to synchronize with an OMC-R.
synch reset off 01.06.1980 00:00:13 MGLI-000-1 CC PRESET BTS-CDMA 17.00.202.73 Synch resets for timers have been disabled. This is NOT saved across boots and should only be used in test environments.
3-42
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Establish WinLMF to SC7224 Connection with BTS OOS
Establish WinLMF to SC7224 Connection with BTS OOS ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Establish WinLMF to SC7224 BTS Connection with BTS OOS Follow the procedure in Procedure 3-13 to establish the connection between the WinLMF and the SC7224.
Procedure 3-13
Procedure to Establish WinLMF to SC7224 Connection with BTS OOS
1
[WinLMF] Ping BTS. The standard Ping command from the WinLMF to the SC7224 can be used to verify that the WinLMF is connected to the BTS.
2
[WinLMF] Start the FTP server from the WinLMF: Tools->FTP Sever->Start
3
[GLI] Prepare GLI
4
•
At the GLI3> prompt enter the synch reset off command to prevent the GLI from rebooting when it is unable to synchronize with an OMC-R.
•
Wait for the GLI to achieve 'SYNCH state: GET_PERF_MGMT_AUDIT' The SYNCH state of the GLI is checked by entering the synch status command at the GLI3> prompt. Repetitive entries of the synch status command will be required.
[WinLMF] Update NECB on GLI •
Login to the BTS from the WinLMF. The 'Packet GLI is OOS' information message will appear as indicated in the Figure 3-6. Click on OK for that message.
•
Perform Upload Config Files (by BTS->Upload Config Files menu item) to load the NECB and NECJ from the WinLMF to the GLI.
•
GLI will load the NECB, NECJ, and the rest of the BTS code files. Once the code files are loaded and transferred to non-volatile memory in the GLI, the GLI will transition to the INS ACTIVE state.In this case, it is necessary to repeat step 4. The entire process may take up to 20 minutes.
•
The status of this GLI can be determined using the synch status command at the GLI3> prompt. The response to this command for a GLI in the INS_ACTIVE state is shown in the following example. The WinLMF display for a properly connected WinLMF is shown in Figure 3-7.
GLI3> synch status 01.06.1980 00:02:38 MGLI-000-1 CC PRESENT BTS-CDMA 17.00.202.75 GLI: Active Golden Node SYNCH state: IDLE Substate: NONE Continued
68P09309A80-2
3-43
FOA
OCT 2010
Establish WinLMF to SC7224 BTS Connection with BTS OOS
Procedure 3-13 OOS (Continued)
Chapter 3: Acceptance Test Procedures
Procedure to Establish WinLMF to SC7224 Connection with BTS
[GLI] Enable GLI to operate without connection to MM. •
At the GLI> prompt, enter lum override on. There is no response to this command.
6
[BTS] GLI is in INS ACTIVE state.
7
[GLI] Set the BTS ID. The BTS ID is determined by the following NECB parameters: With their values inserted into the following formula: system=80h + ((OMCRNumber - 1) * 10h) + CBSCNumber Example: If OMCRNumber=1, CBSCNumber=5, and networkElementID=BTS0073 then, system = 0x085, networkElementID = 0x0049 (hex for 73), btsId = 850049 At the GLI> prompt, enter rte btsid Using the result from the above example type rte btsid 0x085 0x0049 Continued
3-44
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 3-13 OOS (Continued) 8
Establish WinLMF to SC7224 BTS Connection with BTS OOS
Procedure to Establish WinLMF to SC7224 Connection with BTS
WinLMF connectivity to the SC7224 is now established. All necessary WinLMF operations can be undertaken.
Figure 3-6
Packet GLI OOS_Message
68P09309A80-2
3-45
FOA
OCT 2010
Establish WinLMF to SC7224 BTS Connection with BTS OOS
Figure 3-7
Chapter 3: Acceptance Test Procedures
WinLMF Display After Successful Connection to the SC7224
3-46
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Establish WinLMF to SC7224 Connection with BTS INS
Establish WinLMF to SC7224 Connection with BTS INS ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Establish WinLMF to SC7224 Connection with BTS INS Follow the procedure in Procedure 3-14 to establish the connection between the WinLMF and the SC7224 when the BTS has an active connection to the OMC-R and MM.
Procedure 3-14
Procedure to Establish WinLMF to SC7224 Connection with BTS INS
1
[WinLMF] Ping BTS. The standard ping command from the WinLMF to the SC7224 can be used to verify that the WinLMF is connected to the BTS.
2
Login to BTS from the WinLMF.
3
[BTS] GLI is in INS ACTIVE state.
4
WinLMF connectivity to the SC7224 is now established. All necessary WinLMF operations can be undertaken.
68P09309A80-2
3-47
FOA
OCT 2010
Return GLI to Default Settings
Chapter 3: Acceptance Test Procedures
Return GLI to Default Settings ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Return GLI to Default Settings after WinLMF Work is Complete After WinLMF has completed its operation with the SC7224 GLI, follow the procedure in Procedure 3-15to return the GLI to its default settings.
Procedure 3-15 1
Procedure to Return GLI to Default Settings
[GLI] After working with the WinLMF connected to the BTS without a backhaul connection it is necessary to reconfigure the GLI to restore the ability of the GLI to find and connect to the OMC-R when the backhaul connection is made. Enter the 'config btsrtr default' command at the GLI3> prompt to restore default router settings. Enter the 'lum override off' command at the GLI3> prompt Use CTRL+x at the GLI3> prompt to reset the GLI and then use the ENTER key during the countdown to get to the [VXWorks Boot]. Enter 'C' at the [VXWorks Boot] prompt, select '3' and then enter 'Y' when asked if default configuration is to be used. Enter 'C' at the [VXWorks Boot] prompt, select '1' and then enter '.' in response to BOOTSERVER, BOOTGW, IPADDRESS, NETMASK, FILENAME, and RETRY prompts. Enter '@' at the [VXWorks Boot] prompt to boot up the GLI using the new settings. The SC7224 is now in a state that will allow it to connect to the OMC-R once network connectivity is established.
3-48
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Example NE_LIF.xml File
Example NE_LIF.xml File ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
NE_LIF.xml File The following is an example of the NE_LIF.xml file contents showing code paths. 82902423 22 MCC C04 ROM 17.00.201.42 234264 2DFF452F 10.16.0.1 /cdma/loads/2.17.0.50.0/code/mcp_rom.bin.0c04 CSM 801 RAM 17.00.00.05 30812 87235781 10.16.0.1 /cdma/loads/2.17.0.50.0/code/csm_ram.bin.0801 MCC C04 RAM 17.00.202.35 31E6B0 CC8B0247 10.16.0.1 /cdma/loads/2.17.0.50.0/code/pmcp_ram.bin.0c04 GLI 108 RAM 17.00.202.35 6B85D2 875878A7 10.16.0.1 /cdma/loads/2.17.0.50.0/code/gli_ram.bin.0108 SER 1000 RAM 17.00.200.35 3741c7 42578aa6 10.16.0.1 /cdma/loads/2.17.0.50.0/code/ser_ram.bin.1000 XMI 1040 RAM 17.00.00.23 3B525A b43861e6 10.16.0.1 /cdma/loads/2.17.0.50.0/code/xmi_ram.bin.1040 •
68P09309A80-2
3-49
FOA
OCT 2010
Pinging the Processor
Chapter 3: Acceptance Test Procedures
Pinging the Processor ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Pinging the Processor For proper operation, the integrity of the Ethernet LAN A and B links must be verified. Figure 3-8 represents a typical BTS Ethernet configuration. The drawing depicts one (of two identical) links, LAN 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-8
BTS LAN Diagram
LAN B LAN A
LAN B
LAN A
CRMS
50-Ohm Loads
DMC I/O
ti-cdma-00109.eps
Follow the procedure in Procedure 3-16 and refer to Figure 3-8, as required, to ping each processor (on both LAN A and LAN B) and verify LAN redundancy is operating correctly.
3-50
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Pinging the Processor
CAUTION Always wear an approved anti-static wrist strap while handling any circuit card/module to prevent damage by ESD.
NOTE The Ethernet LAN A and B cables must be installed on each frame/enclosure before performing this test. All other processor board LAN connections are made via the backplanes.
Procedure 3-16
Pinging the Processors
1
If it has not already been done, connect the WinLMF to the BTS (see Procedure 3-4.
2
From the Windows desktop, click the Start button and select Run.
3
In the Open box, type ping and the (for example, ping 128.0.0.2).
NOTE 128.0.0.2 is the default IP address for MGLI-1 in field BTS units. 128.0.0.1 is the default IP address for MGLI-2. 4
Click on the OK button.
5
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 If the MGLI fails to respond, reset and perform the ping process again. If the MGLI still fails to respond, typical problems are shorted BNC-to-inter-frame cabling, open cables, crossed A and B link cables, missing 50-Ohm terminators, or the MGLI itself.
68P09309A80-2
3-51
FOA
OCT 2010
XMI Cable Check
Chapter 3: Acceptance Test Procedures
XMI Cable Check ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
XMI Cable Check Perform the procedure in Procedure 3-17to verify correct XMI cabling.
Procedure 3-17
Procedure for XMI Cable Check
1
On the WinLMF, select (highlight) the XMI(s).
2
From the drop down menu, select Device > XMI > Cable Check.
3
A Results Window opens. If cable checking produces a failure, double click on the Results row.
4
A Details Window opens with information about the cabling problem.
3-52
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
TX Audit Test, CDMA1X and DT SC-BTS
TX Audit Test, CDMA1X and DT SC-BTS ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
TX Audit Test The TX audit test is used to determine if the TX power output at the antenna connector (TX port) of the BTS is within a specified range. The BLO calibration audit procedure confirms the successful hardware installation. The calibration audit procedure measures the path gain or loss of every sector-carrier transmit path at the site. In this test, actual system tolerances are used to determine the success or failure of a test. The same external test equipment set up is used. The Tests menu item, TX Audit, performs the TX BLO Audit test for a sector-carrier(s). All measurements are made through the appropriate TX output connector using the calibrated TX cable setup.
NOTE RF path verification and CAL file upload to GLI must have been successfully completed prior to performing the calibration audit. A generic CAL file is used place of a site specific one.
WARNING Before connecting any test equipment directly to any TX OUT connector, you must: •
verify there are no CDMA XMI channels keyed Have the OMC-R place all sector under test OOS.
•
In a SC7224DT frameverify there are no LTE XMI channels keyed
Have the WBM operator place all eNB cells under test OOS Failure to do so can result in serious personal injury and/or equipment damage.
68P09309A80-2
3-53
FOA
OCT 2010
TX Audit Test
Chapter 3: Acceptance Test Procedures
Prerequisites Before running this test, ensure that the following have been done:
NOTE All XMIs must be INS_ACT during any TX testing. •
CSM-1, MCCs, and GLIs have the correct code load and data load.
•
Primary CSM and MGLI are INS.
•
All XMIs are INS.
NOTE At least one MCC assigned to Pilot Generation for sector-carrier being calibrated is INS.
•
Test equipment and test cables are calibrated and connected for TX Audit.
•
WinLMF is logged into the BTS.
Test Procedure Follow the procedure in Procedure 3-18 to perform the TX Audit.
Procedure 3-18
Procedure for TX Audit
1
Establish an MMI connection per Procedure 3-3. At the GLI> prompt, enter lum override on.
2
Re-Establish WinLMF connection.
3
If it has not already been done, configure test equipment for TX path audit by following the applicable illustration in:
4
•
CDMA2000 1X TX (with IDRF): Test Equipment Setup for CDMA2000 1X Optimization/ATP on page G-34.
•
DT BTS with DDRF: Test Equipment Setup for CDMA2000 1X Optimization/ATP on page G-34
Configure MCC Data Select all MCCs. Take control over the MCCs using Device->Packet Mode Options->LMF Control Request menu. Select all MCCs again and deactivate, then using Device->Disable/Deactivate menu. Continued
3-54
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 3-18
TX Audit Test
Procedure for TX Audit (Continued)
Select all MCCs and download configuration data using Device->Download->Data menu. Select all MCCs and activate them using Device->Enable/Activate menu. 5
Select Sector-carrier to be audited. See Figure 3-9.
6
Perform TX Audit by doing the following:
• •
Select the MCC mapped to the sector-carrier. Select Test To Perform is TX Audit.
•
Enter the selected carrier's gain in dBm (Default).
•
In the Test Pattern box, select Standard.
•
The WinLMF will automatically key the designated sector-carrier.
68P09309A80-2
3-55
FOA
OCT 2010
TX Audit Test
Chapter 3: Acceptance Test Procedures
Figure 3-9
Sector-Carrier Location on WinLMF
3-56
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
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, that path losses are within tolerances required for correct receiver operation, and correct installation of the RX path. Testing is performed using the calibrated external test equipment as the signal source. The test equipment is controlled by the WinLMF 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 WinLMF sets the pilot channel power level of the sector-carrier for the selected sector to +25.2 dBm (measured at the TX port of the frame) and enables the sector-carrier on pilot channel only to enable the RX circuitry. The WinLMF 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 XMI. The WinLMF corrects the measured power of the signal using the RX BLO 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: •
2100 MHz: –80 dB (–86 dBm or greater)
•
800 MHz: –80 dBm (–86 dBm or greater)
NOTE The WinLMF provides a –80 dBm signal (default) input to the BTS. The RSSI must be ±6 dB
RSSI Acceptance Test Follow the steps in Procedure 3-19 to verify RSSI of the RX antenna paths for the required sector-carriers.
68P09309A80-2
3-57
FOA
OCT 2010
RSSI Acceptance Test
Chapter 3: Acceptance Test Procedures
Procedure 3-19 1
Test RSSI
Set up the test equipment for RX acceptance tests (refer to the applicable illustration in Test Equipment Setup for CDMA2000 1X Optimization/ATP on page G-34 of Appendix G Optimization and Calibration Procedures).
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
Select the sector-carrier for the carrier to be tested.
3
In the WinLMF window menu bar, click on Tests > RX > RSSI.
4
Select the sector-carriers to be tested in the Channels/Carriers pick list which is displayed.
5
Select the RX Branch to be tested from the choices in the drop down list provided (Both, Main, or Diversity).
6
Enter the appropriate power level into the Generator amplitude box (default: -80 dBm)
7
Click OK. A status bar will be displayed followed by a Directions pop-up window..
8
Follow cable connection directions as they are displayed, and click the Continue button to begin testing. Progress will be indicated in the status bar.
9
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.
3-58
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
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 all test results saved with the Save Results button. Test results are overwritten by results for the same TEST, XCVR, SECTOR, CARRIER, and CHANNEL. When an ATP report for a BTS is generated, all test results will be included in the report.
ATP Report Each time an ATP test is run, a separate report is created for each BTS and includes the following for each test: •
Test name
•
Channel number
•
Carrier number
•
Sector number
•
Test result
•
PASS or FAIL
•
Description information (if applicable)
•
Time stamp
•
Details/Warning information (if applicable)
The report can be printed if the WinLMF computer is connected to a printer. Follow the procedure in the Procedure 3-20 to view and/or print the ATP report for a BTS.
68P09309A80-2
3-59
FOA
OCT 2010
ATP Report
Chapter 3: Acceptance Test Procedures
Procedure 3-20
Generating an ATP Report
1
Click on the Login tab (if not in the forefront.
2
Select the desired BTS from the available Base Station pick list.
3
Click on the Report button.
4
Click on the column heading to sort the report.
5
If not a printable file copy is not needed, click on the Dismiss button. If requiring a printable file copy, select the desired file tpe in the picklist and click on the Save button.
3-60
68P09309A80-2
FOA
OCT 2010
Chapter
4 Configuring Packet BTS Transport ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
68P09309A80-2 OCT 2010
4-1
FOA
Introduction to Packet BTS CDMA2000 1X Transport Configuration
Chapter 4: Configuring Packet BTS Transport
Introduction to Packet BTS CDMA2000 1X Transport Configuration ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
There are several backhaul configurations used for traffic and control signalling transport between a packet BTS and the OMC-R. For the SC7224 BTS, all of these depend on correctly setting the GLI3 card operating mode to interface with the required backhaul configuration. The backhaul configurations are: •
Integrated BTS Router (IBR)
•
External BTS Router (EBR)
•
Open Transport Interface (OTI)
NOTE In a SC7224DT (Dual Technology) frame the CDMA 1X and LTE use separate backhauls. This chapter only applies to the CDMA 1X side of a SC7224DT frame.
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: •
Determine GLI3 card: Installed software version Operating mode Backhaul mode
•
Loading GLI3 cards with code for the required software release
•
Convert GLI3 card to IBR operation
•
Convert GLI3 card to EBR operation
•
Convert GLI3 card to OTI operation
•
Enable File Transfer Protocol (FTP) or Secure File Transfer Protocol (SFTP)
4-2
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Applicability
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 apply to GLI3 cards in a newly installed BTS.
When to Use BTS Conversion Procedures from Another Publication If the BTS hardware configuration is being converted from one transport technique to another (for example, from IBR to EBR), the procedures in the BTS hardware modifications or OTI implementation/conversion manual must be used instead of the procedures in this chapter. Table 4-1, below, lists the various Motorola–supported packet BTS transport conversions along with the applicable conversion or upgrade manual title needed to perform the conversion. For more information on the BTS hardware modifications or OTI implementation/conversion manuals and how to obtain them, refer to Required Documents and Related Publications on page 1-18.
Table 4-1
Packet BTS Transport Conversions
Conversion Type
Use Procedures in
IBR to EBR
SC7224 BTS Hardware Modifications
EBR to IBR
SC7224 BTS Hardware Modifications
IBR to OTI
CDMA2000 1X BTS Open Transport Interface Implementation/Conversion
EBR to OTI
CDMA2000 1X BTS Open Transport Interface Implementation/Conversion
68P09309A80-2
4-3
FOA
OCT 2010
GLI3 Required Software Release, Operating Mode, and Loading Code
Chapter 4: Configuring Packet BTS Transport
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 4-2 lists GLI3 backhaul modes along with the earliest Motorola software release which supports each.
Table 4-2
GLI3 Packet Backhaul Mode and Software Release Required Description
Packet Backhaul Mode
Required Software Release
DUPLEX
EBR (redundant BTS routers)
2.19.0.x and later
INTERNAL
IBR
2.19.0.x and later
IWF-OTI
OTI
2.20.0.x and later
The software release of the code loaded in a GLI3 card can be determined by performing Procedure 4-1.
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 4-3 lists the code loading methods available in each operating mode.
4-4
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Table 4-3
GLI3 initialization
GLI3 Code Loading Methods Based on Operating Mode
Operating Mode
Available Code Loading Methods
Circuit 1.
Download from OMC–R.
2.
Cross-load from INS_ACT GLI card in a BTS.
3.
Download using WinLMF application.
1.
Download from OMC–R.
2.
Cross-load from INS_ACT GLI card in a BTS.
3.
Download using WinLMF application (beginning with R22.0).
Packet
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 4-4.
The operating mode and backhaul mode of a GLI3 card can be determined by performing Procedure 4-1.
Loading code into GLI3 cards 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 4-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.
68P09309A80-2
4-5
FOA
OCT 2010
Loading code into GLI3 cards
Chapter 4: Configuring Packet BTS Transport
The Motorola-recommended method to load GLI3 cards on-site 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 pre-loading GLI3 cards with the correct software release code and then transporting them to the base station site. Pre-loaded cards can be exchanged for the GLI3 cards installed in the BTS. The cards removed can be pre-loaded for the next new base station installation or for use as spares.
Loading GLI3 cards with the WinLMF (Motorola-recommended) To load code to packet GLI3 cards with the WinLMF, refer to Loading Packet GLI Devices on page G-10.
Pre-loading GLI3 cards (Motorola-recommended) To pre-load GLI3 cards, refer to Procedure 4-3.
4-6
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
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: •
Code loaded for a different software release
•
Change of backhaul mode
Determining GLI3 backhaul mode This procedure is used to identify the software release of the code loaded in a GLI3 card and the backhaul mode into which the card will initialize. Both of these must be known to determine if the code load requires upgrading to support the type of backhaul required at the site.
Prerequisites The following are required before performing this procedure: •
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 MMI prompt
•
A working copy has been made of the GLI3 Software Release and Backhaul Mode Worksheet on page 4-49
Procedure Determine GLI3 card installed software version and backhaul mode by performing the following procedure.
Procedure 4-1
Determine GLI3 Card Software Version and Backhaul Mode
1
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.
2
If it has not been done, start a GLI3 MMI communication session on the LMF computer with the powered GLI3 card as described in Establishing an MMI Communication Session on page 3-24. Continued
68P09309A80-2
4-7
FOA
OCT 2010
Determining GLI3 backhaul mode
Procedure 4-1 (Continued) 3
Chapter 4: Configuring Packet BTS Transport
Determine GLI3 Card Software Version and Backhaul Mode
If GLI3 cards were pre-loaded with code for the software release installed on the Radio Access Network (RAN), do the following:. 1.
Enter the pre–loaded software release number in the Software Version column of line 1 of Table 4-7 in the worksheet.
2.
Skip to step 9.
4
Determine the software version loaded in the GLI3 card installed in GLI slot 1 by entering the following at the GLI3 prompt: display version
5
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 MGLI-002-2
OOS-SBY
BTS-CDMA 16.41.200.14
RAM version: 16.41.200.14 ROM version: 16.41.200.14 Built: Tue Oct 21 09:52:28 2003 il27-2112
Bootrom version: 16.41.200.12 Bootrom Built: Thu Oct 2 03:11:34 2003 IL27-0775 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> 6
Record the release number for the RAM version in the Software Version column of line 2 of Table 4-7 in the worksheet, 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. Continued
4-8
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 4-1 (Continued) 7
Determining GLI3 backhaul mode
Determine GLI3 Card Software Version and Backhaul Mode
A GLI3 operating in packet mode will generate a response similar to the following: GLI3>
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
Record the COMMITTED VERSION number in the Software Version column of line 2 of Table 4-7 in the worksheet.
9
Determine the backhaul mode of the GLI3 cards by entering the following at the GLI3 prompt: display bkhaul_mode
10
A response similar to the following will be displayed: GLI3> display bkhaul_mode 06.08.2007 08:53:33 MGLI-1550-2
CC PRESENT BTS-CDMA 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: •
DUPLEX = EBR with redundant BTS routers
•
INTERNAL = IBR Continued
68P09309A80-2
4-9
FOA
OCT 2010
Determine if GLI3 Card Configuration Changes Are Required
Procedure 4-1 (Continued)
Chapter 4: Configuring Packet BTS Transport
Determine GLI3 Card Software Version and Backhaul Mode
•
IWF-OTI = OTI
•
SIMPLEX = EBR with a non-redundant BTS router
•
UNKNOWN = circuit mode
11
Record the response in the Backhaul Mode column of line 2 of Table 4-7 in the worksheet.
12
If the software version requires updating for operation with the required backhaul type, proceed to the GLI3 Operating Mode and Loading Code section, and select the method to update software based on the card operating mode (Table 4-3) and backhaul mode (Table 4-4).
13
If there are no additional MMI communication session requirements, disconnect the MMI cable from the GLI3 MMI receptacle.
Determine if GLI3 Card Configuration Changes Are Required Perform the following with the information recorded in Table 4-7.
Procedure 4-2
Does GLI3 Card Need Configuration Change?
1
Compare the entries in line 2 of Table 4-7 in the worksheet with the line 1 entries in the same column.
2
If there are differences in the software release, refer to Table 4-2 to determine if the code loaded in the card will support the required backhaul mode for the BTS.
3
If the code will not support the required backhaul mode for the BTS, load the required software release into the card (review GLI3 Required Software Release, Operating Mode, and Loading Code on page 4-4 to determine how to proceed with loading the required software into the card).
4
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: •
Configure GLI3 cards for IBR packet operation, Procedure 4-4, Procedure 4-5, and Procedure 4-6
•
Configure GLI3 cards for operation with EBR, Procedure 4-8 and Procedure 4-9
•
Configure GLI3 cards for operation with OTI backhaul, Procedure 4-10, Procedure 4-11, and Procedure 4-12
4-10
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Loading Packet GLI Devices
Loading Packet GLI Devices ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Beginning with R22.0, the WinLMF has the capability to download code to GLI3 cards operating in packet mode. Refer to Loading Packet GLI Devices on page G-10 for the procedure to load code into a packet GLI3 device.
68P09309A80-2
4-11
FOA
OCT 2010
Pre-loading GLI3 Cards in Packet Mode
Chapter 4: Configuring Packet BTS Transport
Pre-loading GLI3 Cards in Packet Mode ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
This procedure is for pre-loading GLI3 cards with the required software release code and data when they are operating in packet mode. It can also be used to pre-load cards for which the operating mode is unknown.
Required items The following are needed to perform this procedure:
•
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
•
Approved anti–static wrist strap
•
GLI3 cards to be pre–loaded and their transport packaging
•
Tagging materials
Pre–load procedure Perform the following to pre–load GLI3 cards for a new base station site or for use as spares.
Procedure 4-3
Pre-load GLI3 Cards
1
Identify the INS_SBY GLI3 card (ACT LED not lighted, STA LED slow flashing green) in the BTS card cage.
2
Remove the card from the BTS card cage following the procedure in the Field Replaceable Unit (FRU) manual (refer to Required Documents and Related Publications on page 1-18).
3
CAUTION Wear an approved anti-static wrist strap when performing the following. Failure to do so could result in Electro-Static Discharge (ESD) damage to the circuit cards. Remove the GLI3 card to be pre–loaded from its protective packaging. 4
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 step 2, above.
5
Allow the GLI3 card to boot and reach OOS_SBY status (ACT LED not lighted, STA LED steady green).
6
Contact the OMC-R operator to request the OOS_SBY GLI3 be enabled, and ask the operator to provide notification when the action is complete. Continued
4-12
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 4-3
Pre–load procedure
Pre-load GLI3 Cards (Continued)
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. 7
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).
8
Remove the pre-loaded INS_SBY GLI3 card from the BTS card cage following the procedure in the base station FRU manual.
9
Place the pre-loaded GLI3 card in the original protective packaging for transport to the new BTS site.
10
Tag the packaging for the pre–loaded card to identify the pre-loaded software release code and data.
11
If other GLI3 cards must be pre–loaded, repeat steps step 3 through step 10 for each additional card.
12
When all cards have been pre–loaded, re-install the GLI3 card originally removed from the BTS card cage in step 2, above.
68P09309A80-2
4-13
FOA
OCT 2010
Configure GLI3 Cards for IBR Operation
Chapter 4: Configuring Packet BTS Transport
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 OMC–R communication with the INS_SBY GLI during normal redundant BTS operation:
Table 4-5 Group
Item Required for BTS Redundant GLI Cabling – Integrated BTS Router
Item Double Crossover Accessory Cable Assembly
Item Number SGKN4408
Qty
Description
1
Consists of GLI-to-GLI FE cable 3088643C28. Category 5E Ethernet transceiver cable, double cross-over, 26-24 AWG, unshielded twisted pair, 0.3 m (12 in.), two 8-contact modular plugs
Prerequisites The following must be accomplished before traveling to the BTS site for IBR implementation: •
The BTS has been installed as described in the BTS hardware installation manual (refer to Required Documents and Related Publications on page 1-18)
•
GLI3 cards for the site have been verified as having IBR-capable software installed
•
GLI3 card(s) are installed in the BTS
•
The BTS has power applied
•
The file transfer protocol setting required for operating the BTS (either FTP or Secure FTP (SFTP)) on the network has been verified with the OMC-R provisioning and network operator's policy
•
Number and types of spans required at the site have been determined and installed
•
If a fractional span is to be used, the starting and ending DS0 numbers provisioned on the OMC–R have been obtained
•
Required publications to support transport configuration activities are on hand for transportation to the BTS site (refer to Required Documents and Related Publications on page 1-18)
4-14
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
IBR Implementation Overview
IBR Implementation Overview Addition of fractional span support for IBR-equipped packet BTS in R18.0 has made IBR implementation at the BTS a two-part process. The parts are: 1.
Preparation actions
2.
Configure GLI3 cards for IBR operation for either of the following span configurations: Full span Fractional span
IBR Conversion Preparation Perform the following to prepare the site for configuring the GLI3 card(s) for IBR operation.
Procedure 4-4
IBR Configuration Preparation
1
Contact the OMC–R and notify the operator that GLI3 transport configuration for IBR preparation is starting.
2
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.
3
Make sure the GLI–to–GLI double cross-over Fast Ethernet (FE) cable (Table 4-5) is installed between in the GLI connectors of the GLI3 cards as follows: •
FOR IBR IN MODEM GROUP 1: cable connected between GLI receptacles of the card in GLI slot 1 and the card in GLI slot 2.
•
FOR IBR IN MODEM GROUP 2: cable connected between GLI receptacles of the card in GLI slot 3 and the card in GLI slot 4.
4
If it was not previously done, follow the procedure in Procedure 4-1 to verify the software version in the GLI3 card(s)
5
If the GLI3 software requires upgrading for IBR capability, review GLI3 Required Software Release, Operating Mode, and Loading Code on page 4-4 to determine how to proceed with loading IBR-capable software into the card.
NOTE Only one card in a BTS with redundant GLI3s is required to have IBR-capable 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 cross-load the correct software to the INS_SBY GLI3. 6
Refer to the site documentation for IBR spans and inspect the BTS span cabling connections to be sure they match the requirements. Continued
68P09309A80-2
4-15
FOA
OCT 2010
Convert GLI3 Cards to IBR Operation
Procedure 4-4
Chapter 4: Configuring Packet BTS Transport
IBR Configuration Preparation (Continued)
7
Correct any cabling discrepancies between the BTS span cabling and site documentation, referring to the BTS hardware installation or hardware modifications manual as needed (refer to Required Documents and Related Publications on page 1-18).
8
If it has not already been done, follow the procedure in Establishing an MMI Communication Session on page 3-24 to establish an MMI communication session with the INS_ACT GLI3 card.
9
Configure the file transfer protocol settings for each GLI3 card to match what is required for network operation by performing the procedures in Configuring BTS File Transfer Protocol – New BTS Installation or Non–redundant GLI3 Replacement on page 4-46.
10
To complete the IBR conversion, perform one of the following, depending on what span configuration has been provisioned for the BTS at the OMC–R: •
If the BTS is provisioned with one, two, three, or four full spans (24 DS0 for T1, 31 DS0 for E1), perform the procedure in Procedure 4-5.
•
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 Procedure 4-6.
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: •
For a BTS provisioned with full span(s), use Procedure 4-5
•
For a BTS provisioned with a fractional span, use Procedure 4-6
Full Span(s) IBR Conversion To convert GLI3 cards in a BTS provisioned with full span(s) to IBR, perform the following.
Procedure 4-5 1
IBR Conversion - BTS Provisioned with Full Span(s)
If it has not already been done, follow the procedure in Establishing an MMI Communication Session on page 3-24 to establish an MMI communication session with the INS_SBY GLI3 card, depending on the frame redundancy: Continued
4-16
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 4-5 2
Convert GLI3 Cards to IBR Operation
IBR Conversion - BTS Provisioned with Full Span(s) (Continued)
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
>
NOTE For J1_1 or J1_2 span types use menu selection T1_2. 3
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. Continued
68P09309A80-2
4-17
FOA
OCT 2010
Convert GLI3 Cards to IBR Operation
Procedure 4-5 4
Chapter 4: Configuring Packet BTS Transport
IBR Conversion - BTS Provisioned with Full Span(s) (Continued)
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, 0-131 feet (default for T1) T1_2 : T1 Short Haul mode, 132-262 feet T1_3 : T1 Short Haul mode, 263-393 T1_4 : T1 Short Haul mode, 394-524 T1_5 : T1 Short Haul mode, 525-655 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
>
CAUTION When selecting span equalization settings, comply with the following or the BTS may operate erratically or unpredictably: •
For four-digit BTS models supported with Channel Service Units (CSU), do not select any of the following settings: 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.0 dB
5
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 Continued
4-18
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 4-5 6
Convert GLI3 Cards to IBR Operation
IBR Conversion - BTS Provisioned with Full Span(s) (Continued)
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 pBTS-IBR mode(R18.0+)
1 - 31
> 7
For a BTS provisioned with full spans, accept the default setting full_span by pressing the Enter key.
8
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 MGLI-004-1
CC PRESENT BTS-CDMA 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 Continued
68P09309A80-2
4-19
FOA
OCT 2010
Convert GLI3 Cards to IBR Operation
Procedure 4-5
Chapter 4: Configuring Packet BTS Transport
IBR Conversion - BTS Provisioned with Full Span(s) (Continued)
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:
Establish MMI communication by pressing the Enter key to display the GLI3 > prompt.
10
Repeat step 2 through step 8 of this table for the INS_ACT GLI card, and then proceed to step step 11, below.
11
Re-connect the MMI cable to the INS_SBY GLI3 and press the Enter key to display the GLI3 > prompt. Continued
4-20
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 4-5
Convert GLI3 Cards to IBR Operation
IBR Conversion - BTS Provisioned with Full Span(s) (Continued)
12
NOTE 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, step 1 through step 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.
Disconnect the MMI cable from the INS_SBY GLI3.
2.
Connect the MMI cable to the INS_ACT GLI3.
3.
Press the Enter key to display the GLI3 > prompt.
4.
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 step 1 through step 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 (non-redundant cards), they will automatically reset to their previous backhaul mode (configuration fallback). The BTS must be placed under OMC–R 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 OMC–R can take control of the BTS, do the following for each installed GLI3 card: 1.
Perform the convert_ibr operation from step 1 through step 8 for the INS_SBY card.
2.
Perform the exception procedure in Procedure 4-7 for the INS_SBY card.
3.
Start an MMI session with the INS_ACT card and perform step 1 through step 8.
4.
Perform the exception procedure in Procedure 4-7 for the INS_ACT card.
5.
Resume this procedure at step 12, and follow the procedure to completion. Continued
68P09309A80-2
4-21
FOA
OCT 2010
Convert GLI3 Cards to IBR Operation
Procedure 4-5 15
Chapter 4: Configuring Packet BTS Transport
IBR Conversion - BTS Provisioned with Full Span(s) (Continued)
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 one-time 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 17-minute upgrade process will not be repeated, even if the card is later downgraded to pre–R18.0 software. 16
17
Contact the OMC–R and advise the operator: •
The convert_ibr command has been executed on the GLI3 card(s)
•
The site is ready for IBR backhaul operational verification
•
Provide notification when the OMC–R has communication with the BTS
When advised that the OMC–R has communication with the BTS, proceed to Prepare to Leave the Site on page 5-2.
Fractional Span IBR Conversion To convert GLI3 cards in a BTS provisioned with a fractional span to IBR, perform the following.
Procedure 4-6
IBR Conversion - BTS Provisioned with Fractional Span
1
If it has not already been done, follow the procedure in Establishing an MMI Communication Session on page 3-24 to establish an MMI communication session with the INS_SBY GLI3 card.
2
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) Continued
4-22
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 4-6
Convert GLI3 Cards to IBR Operation
IBR Conversion - BTS Provisioned with Fractional Span (Continued)
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 >
NOTE For J1_1 or J1_2 span types use menu selection T1_2. 3
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. 4
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, 0-131 feet (default for T1) T1_2 : T1 Short Haul mode, 132-262 feet T1_3 : T1 Short Haul mode, 263-393 T1_4 : T1 Short Haul mode, 394-524 T1_5 : T1 Short Haul mode, 525-655 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
>
Continued
68P09309A80-2
4-23
FOA
OCT 2010
Convert GLI3 Cards to IBR Operation
Procedure 4-6
Chapter 4: Configuring Packet BTS Transport
IBR Conversion - BTS Provisioned with Fractional Span (Continued)
CAUTION When selecting span equalization settings, comply with the following or the BTS may operate erratically or unpredictably: •
For four-digit BTS models supported with Channel Service Units (CSU), do not select any of the following settings: 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.0 dB
5
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 pBTS-IBR mode(R18.0+)
1 - 31
> Continued
4-24
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 4-6 7
Convert GLI3 Cards to IBR Operation
IBR Conversion - BTS Provisioned with Fractional Span (Continued)
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 pBTS-IBR mode(R18.0+)
1 - 31
> 8
Enter the ending DS0 number for the span from the specified range of values as shown in the following example:
> 12 9
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 MGLI-004-1
CC PRESENT BTS-CDMA 18.00.00.75
WARNING!!! This MMI is changing the GLI configuration.
IBR Conversion - BTS Provisioned with Fractional Span (Continued)
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: > full_span 01.06.1980 00:13:05 MGLI-004-1
Establish MMI communication by pressing the Enter key to display the GLI3 > prompt.
11
Repeat step 2 through step 9 for the INS_ACT GLI card, and then proceed to step 12, below.
12
Re–connect the MMI cable to the INS_SBY GLI3 and press the Enter key to display the GLI3 > prompt. Continued
4-26
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 4-6
Convert GLI3 Cards to IBR Operation
IBR Conversion - BTS Provisioned with Fractional Span (Continued)
13
NOTE 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, step 1 through step 9 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. 14
Perform the following within 45 seconds of resetting the INS_SBY GLI3: 1.
Disconnect the MMI cable from the INS_SBY GLI3.
2.
Connect the MMI cable to the INS_ACT GLI3.
3.
Press the Enter key to display the GLI3 > prompt.
4.
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 step 1 through step 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. 15
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 (non-redundant cards), they will automatically reset to their previous backhaul mode (configuration fallback). The BTS must be placed under OMC-R 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 OMC–R can take control of the BTS, do the following for each installed GLI3 card: 1.
Perform the convert_ibr operation from step 1 through step 9 for the INS_SBY card.
2.
Perform the exception procedure in Procedure 4-7 for the INS_SBY card.
3.
Start an MMI session with the INS_ACT card and perform step 1 through step 9.
4.
Perform the exception procedure in Procedure 4-7 for the INS_ACT card.
5.
Resume this procedure at step 13 of this table, and follow the procedure to completion. Continued
68P09309A80-2
4-27
FOA
OCT 2010
Exception Procedure for Use When Configuration Fallback Can Not Be Overcome 4: Configuring Packet BTS Transport
Procedure 4-6 16
Chapter
IBR Conversion - BTS Provisioned with Fractional Span (Continued)
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 one-time 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 17-minute upgrade process will not be repeated, even if the card is later downgraded to pre-R18.0 software. 17
18
Contact the OMC–R and advise the operator: •
The convert_ibr command has been executed on the GLI3 card(s)
•
The site is ready for IBR backhaul operational verification
•
Provide notification when the OMC–R has communication with the BTS
When advised that the OMC–R has communication with the BTS, proceed to Prepare to Leave the Site on page 5-2.
Exception Procedure for Use When Configuration Fallback Can Not Be Overcome Perform the following procedure only when directed to it by step 14 in Procedure 4-5 or step step 15 in Procedure 4-6. This procedure is intended for use when the OMC–R is continually unable to take control of the BTS before the GLI3 cards reboot to their last-known-good configuration.
NOTE 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.
Procedure 4-7
Prevent GLI3 Configuration Fallback
1
If it has not been done, establish an MMI communication session with a GLI3 card by following the procedure in Establishing an MMI Communication Session on page 3-24.
2
Prevent the card from automatically rebooting to the last known-good configuration (fallback) by entering the following commands at the GLI3> prompt in the sequence shown and pressing the ENTER key after each: rmfile /nvram00/history/boothistory0.txt rmfile /nvram00/history/boothistory1.txt rmfile /nvram00/history/boothistory2.txt Continued
4-28
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 4-7
Exception Procedure for Use When Configuration Fallback Can Not Be Overcome
Prevent GLI3 Configuration Fallback (Continued)
rmfile /nvram00/history/boothistory3.txt rmfile /nvram00/history/boothistory4.txt rmfile /nvram00/history/boothistory5.txt The terminal will display a response similar to the following:
Return to the table which directed using this procedure, and refer to the applicable table step of the following to resume the conversion: •
For Procedure 4-5, see step 14
•
For Procedure 4-6, see step 15
68P09309A80-2
4-29
FOA
OCT 2010
Configure GLI3 Cards for Operation with External BTS Routers
Chapter 4: Configuring Packet BTS Transport
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: •
New packet BTS initialization
•
Replacement of a non-redundant 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: •
The BTS has been installed as described in the BTS hardware installation manual (refer to Required Documents and Related Publications on page 1-18)
•
GLI3 card(s) for the site have been verified as having IBR/EBR-capable software installed
•
GLI3 card(s) for the site are installed in the BTS
•
The BTS has power applied
•
The file transfer protocol setting required for operating the BTS (either FTP or Secure FTP (SFTP)) on the network has been verified with the OMC-R provisioning and network operator's policy
•
EBR span configuration required at the site has been determined from site documentation
•
The required EBR span cabling has been installed as specified in the hardware installation or hardware modifications manual (refer to Required Documents and Related Publications on page 1-18)
•
Required publications to support transport configuration activities are on hand for transportation to the BTS site (refer to Required Documents and Related Publications on page 1-18)
EBR conversion preparation Do the following to prepare a new BTS for converting the GLI3 card(s) to EBR operation.
4-30
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 4-8 1
Convert GLI3 Cards to EBR Operation
EBR Conversion Preparation
Contact the OMC–R, and:. •
Notify the operator that GLI3 transport configuration for EBR preparation is starting.
•
Request the operator provide notification when the OMC–R is ready to initialize the BTS.
2
If it was not previously done, verify the software version in the GLI3 card(s) following the procedure in GLI3 Card Software Version and Backhaul Mode on page 4-7.
3
If the GLI3 software requires upgrading for EBR capability, review GLI3 Required Software Release, Operating Mode, and Loading Code on page 4-4to determine how to proceed with loading IBR/EBR–capable software into the card.
NOTE Only one card in a BTS with redundant GLI3s is required to have IBR-capable 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 cross-load the correct software to the INS_SBY GLI3. 4
5
Inspect the BTS router span Y–cable connections to be sure they are connected as specified in the following: •
Site documentation for EBR spans
•
BTS hardware installation or hardware modifications manual (Required Documents and Related Publications on page 1-18) for connection details
Verify the following and correct any discrepancies as needed: •
External BTS routers EBR 1 and EBR 2 are installed
•
External BTS router power cable, Ethernet cables, and the GLI–GLI double–crossover cable(s), are connected as specified.
•
Compact Flash (CF) memory cards are installed in each external BTS router
6
If it has not been done, apply power to the external BTS routers by setting PDU circuit breakers EBR 1 and EBR 2 to ON (pushed in) (Figure 2-3).
7
Configure the GLI3 card file transfer protocol settings to match what is required for network operation by performing the procedure in Configuring BTS File Transfer Protocol – New BTS Installation or Non–redundant GLI3 Replacement on page 4-46.
8
Proceed to Convert GLI3 Cards to EBR Operation on page 4-31.
Convert GLI3 Cards to EBR Operation When notified that the OMC–R is prepared for BTS initialization, perform the following procedure.
68P09309A80-2
4-31
FOA
OCT 2010
Convert GLI3 Cards to EBR Operation
Procedure 4-9
Chapter 4: Configuring Packet BTS Transport
Convert GLI3 Cards to EBR Operation
1
Following the procedure in Establishing an MMI Communication Session on page 3-24, establish an MMI communication session with the INS_SBY GLI3 card.
2
Enter the following command to configure the GLI3 card to EBR operation: convert_ebr
The system will display responses similar to the following: GLI3> convert_ebr 11.24.2003 23:14:57 MGLI-004-2
CC PRESENT BTS-CDMA 16.40.00.09
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 To complete the conversion to EBR, this GLI must be reset! 3
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.
4
Repeat step 2, above, for the INS_ACT GLI3 card, and then proceed to step 5, below.
5
For redundant frames, re–connect the MMI cable to the INS_SBY GLI3 card and press the Enter key to display the GLI3 > prompt. Continued
4-32
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 4-9
Convert GLI3 Cards to EBR Operation
Convert GLI3 Cards to EBR Operation (Continued)
6
NOTE 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 IBR or OTI. If one GLI3 completes initialization before the other is reset, step 1 and step 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. 7
Perform the following within 45 seconds of resetting the INS_SBY GLI3 card: 1.
Disconnect the MMI cable from the INS_SBY GLI3 card.
2.
Connect the MMI cable to the INS_ACT GLI3 card.
3.
Press the Enter key to display the GLI3 > prompt.
4.
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 step 1 through step 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 (non-redundant card) to prevent the GLI3 cards from automatically rebooting to their last known good operating mode. If cards self-initiate configuration fall back before the OMC–R takes control, the convert_ebr procedure in step 1 through step 8 must be performed again. 9
10
Contact the OMC–R and advise the operator: •
The convert_ebr command has been executed on the GLI3 card(s)
•
All EBR cabling is complete
•
The site is ready for EBR backhaul operational verification
•
Provide notification when the OMC–R has communication with the BTS
When advised that the OMC–R has communication with the BTS, proceed to Prepare to Leave the Site on page 5-2
68P09309A80-2
4-33
FOA
OCT 2010
Configure GLI3 Cards for OTI
Chapter 4: Configuring Packet BTS Transport
Configure GLI3 Cards for OTI ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
This section contains procedures necessary to configure the GLI3 cards for CDMA2000 1X OTI backhaul.
NOTE This procedure requires a site visit. There can be no contact between the BTS and the OMC–R 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 •
The OTI edge device (Figure J-1) has been installed and configured by the customer
•
The cables to connect the OTI edge device to the base station are available at the site
•
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 BTS–to–edge device connection after power-up can result in inability to establish communication between the BTS and the OMC–R.
BTS •
The BTS was installed as a packet BTS with OTI in accordance with the applicable BTS hardware installation manual
•
The BTS has had power applied
•
The edge device HAS NOT BEEN CONNECTED TO THE BTS 10/100BaseTX Fast Ethernet (FE) Local Area Network (LAN)
•
Site documentation specifies:
4-34
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Equipment required
The required number of Ethernet connections between the BTS and edge device The BTS demarcation connection point(s) and corresponding edge device connection point(s) for each
OMC–R •
Provisioning of the OTI BTS has started, and the following are done: BTS ID number is assigned (example: BTS–201) 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 Preparing the WinLMF on page 3-4.
MMI Interface •
One of the following Motorola cable part number CGDSMMICABLE219112 Fabricated DB–9 receptacle-to-8-contact MMI connector cable (see MMI Cable Fabrication on page F-2 for fabrication instructions and Establishing an MMI Communication Session on page 3-24 for connection)
GLI3 OTI implementation This subsection covers the actions needed to implement OTI transport for the installation of a new packet 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.
68P09309A80-2
4-35
FOA
OCT 2010
GLI3 OTI implementation
Chapter 4: Configuring Packet BTS Transport
Prerequisites The following must be accomplished before traveling to the BTS site for OTI implementation: •
The BTS has been installed as described in the BTS hardware installation manual for the BTS type (refer to Required Documents and Related Publications on page 1-18)
•
GLI3 cards for the site have been verified as having IBR–capable software installed
•
GLI3 card(s) are installed in the BTS
•
The file transfer protocol setting required for operating the BTS (either FTP or Secure FTP (SFTP)) on the network has been verified with the OMC–R provisioning and network operator's policy
•
Required publications to support OTI implementation activities are on hand for transportation to the BTS site (refer to Required Documents and Related Publications on page 1-18)
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.
Procedure 4-10
Preparation for BTS OTI Implementation
1
Locate the OTI configuration settings worksheet on page 4-50 (OTI worksheet) and Network Interface Card (NIC) configuration worksheet on page 4-51.
2
Make a copy of the worksheets for each BTS to be initialized.
3
Contact the network administrator to obtain the values for the following items in Table 4-8 in the OTI worksheet for each BTS to be initialized: •
BTS ID
•
OTIClientID
•
OTI_BTSRTRGRP_IP_addr
•
OTI_Network_Mask
•
MLS_OTI_CON_HSRP_Logical_Addr for CDMA2000 1X
4
Use the information obtained to fill in the applicable IP addressing information blanks in the Internet Protocol (TCP/IP) Properties dialog box General tab on page 4-52 on the Network Interface Card (NIC) configuration worksheet on page 4-51.
5
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 on page 4-35 and GLI3 OTI implementation on page 4-35, above.
4-36
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
GLI3 OTI implementation
On–site preparations – Perform the following after arriving at the BTS site.
Procedure 4-11
Site Arrival and Initial Preparation
1
Upon arrival at the site, contact the OMC–R and notify the operator that GLI3 transport configuration for OTI preparation is starting.
2
If it has not been done, open the BTS enclosure door and BTS DMC door to gain access to the BTS modules.
3
Make sure frame FE cabling is connected to the GLI3 card(s) as shown in Figure 4-1 and the following for cable 3088643C39:
4
5
6
•
FOR SINGLE–BAND FRAME: cable connected between GLI receptacles of the card in GLI slot 1 and the card in GLI slot 2.
•
FOR DUAL–BAND FRAME: cable connected between GLI receptacles of the card in GLI slot 3 and the card in GLI slot 4.
With the BTS fully powered up, the GLI3 cards should have been seated in the correct slots. Perform one of the following : •
If cards are not seated, seat only one card, and allow it to complete initialization to OOS_SBY.
•
If all cards are seated, unseat all but one card from the cage backplane connector. Do not disconnect the FE cables from the card BPR A and GLI connectors.
If it was not previously done, follow Procedure 4-1 for the powered GLI3 card to determine: •
The installed software version (any version of software release 2.20.x.x or later is required)
•
The backhaul mode
•
The operating mode (circuit or packet — determined from backhaul mode; see Table 4-4)
If the GLI3 software requires upgrading for OTI capability, review the GLI3 Required Software Release, Operating Mode, and Loading Code on page 4-4 to determine how to proceed with loading OTI–capable software into the card.
NOTE Only one card in a BTS with redundant GLI3s is required to have OTI–capable 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 OMC–R after OTI implementation. The INS_ACT GLI3 will cross-load the correct software to the INS_SBY GLI3 after communication with the OMC–R is established. 7
Perform the CDMA2000 1X OTI link confidence check procedure in OTI Link Confidence Check on page J-9. Continued
68P09309A80-2
4-37
FOA
OCT 2010
Convert GLI3 cards to OTI operation
Procedure 4-11
Chapter 4: Configuring Packet BTS Transport
Site Arrival and Initial Preparation (Continued)
8
If it has not already been done, follow the procedure in Establishing an MMI Communication Session on page 3-24 to establish an MMI communication session with the powered GLI3 card.
9
Configure the powered GLI3 card file transfer protocol settings to match what is required for network operation by performing the procedures in Configuring BTS File Transfer Protocol – New BTS Installation or Non–redundant GLI3 Replacement on page 4-46.
10
Proceed to Procedure 4-12.
Convert GLI3 cards to OTI operation Perform the following to implement OTI operation beginning with the powered GLI3 card.
Procedure 4-12
Convert GLI3 Card to OTI Operation
1
If it has not already been provided, contact the OMC–R and request the operator provide the BTS OTIClientID (Table 4-8, second row, in the OTI worksheet).
2
Enter the 4–byte hexadecimal value provided into Table 4-8 in the OTI worksheet for the BTS being initialized.
3
Refer to the site documentation, and connect the Ethernet cables from the BTS edge device to the BTS span I/O ENET connectors as specified.
4
Verify that the BTS edge device connector link light is lighted for the Ethernet cable connected to the powered GLI3 card.
5
Get the assigned BTS OTIClientID from Table 4-8 in the OTI worksheet completed for the BTS.
6
In the MMI communication session with the powered GLI3 card, enter the following at the GLI3> prompt: convert_oti Where is the 4–byte 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:
WARNING!!! This MMI is changing the GLI configuration.
The OTIClientID has been set to: 13-f8-be-20 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> 7
Reset the card using the MMI reset command and monitor the terminal session for conversion results.
NOTE When the card completes re–booting 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, re–boot, and begin the DHCP discovery process over again. DHCP time–out and card–initiated re–boot create terminal responses similar to the following: Press any key to stop auto-boot... 3 2 1 0 auto-booting...
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 OMC–R will generate a terminal response similar to the following: Continued
68P09309A80-2
4-39
FOA
OCT 2010
Convert GLI3 cards to OTI operation
Procedure 4-12
Chapter 4: Configuring Packet BTS Transport
Convert GLI3 Card to OTI Operation (Continued)
Press any key to stop auto-boot... 3 2 1 0 auto-booting...
Getting boot parameters via network interface motscc. CC went active, stopping motscc attempt and restarting over motfcc1... Getting boot parameters via network interface motfcc.
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 OMC–R. The terminal will display a response similar to the following:
SYSTEM INIT COMPLETE
CheckpointManager NOT Active informAllCheckpointableObjectListeners attribute id 75 sshd2: SSH2 Secure Shell MOT-SSH IPTG_REL_1.2.04 on BTS->GLI3
4-40
Continued
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 4-12
Convert GLI3 cards to OTI operation
Convert GLI3 Card to OTI Operation (Continued)
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/bts-1902/NECB-2.20.0.2.8-BTS1902.xml
0:0:46.150000 put NECB here /nvram00/screl/2.20.0.2.8/NECB-2.20.0.2.8-BTS1902.xml
0:0:49.160000 get NECJ from /screl/active/loadable/bts-1902/NECJ-2.20.0.2.8-BTS1902.xml
0:0:49.160000 put NECJ here /nvram00/screl/2.20.0.2.8/NECJ-2.20.0.2.8-BTS1902.xml
0:0:49.160000 put NECJ temporarily here /ram00/config/journal/ NECJ-2.20.0.2.8-BTS1902.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/bts-1902/bts-1902.cal
0:1:0.810000 put CAL file: /nvram00/config/temp_bts-1902.cal 9
When the card completes its initialization, the terminal will display the GLI3> prompt. When the GLI3> prompt appears, seat the redundant GLI3 card, if installed, and allow it to initialize. Continued
68P09309A80-2
4-41
FOA
OCT 2010
Convert GLI3 cards to OTI operation
Procedure 4-12 10
Chapter 4: Configuring Packet BTS Transport
Convert GLI3 Card to OTI Operation (Continued)
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
08.08.2007 15:30:00 MGLI-1902-2
CC NOT PRESENT BTS-CDMA 20.00.30.42
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 MGLI-1902-2
CC NOT PRESENT BTS-CDMA 20.00.30.42
The current BTS Router Backhaul Mode is IWF-OTI After the next reset, the BTS Router Backhaul Mode will be IWF-OTI GLI3> 11
Verify that the BTS edge device connector link light is lighted for the Ethernet cable connected to the INS_SBY GLI3 card.
12
Repeat step 9 through step 11 for each additional GLI3 card in the frame.
13
When advised that the OMC–R has communication with the BTS, proceed to Prepare to Leave the Site on page 5-2
4-42
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Convert GLI3 cards to OTI operation
Figure 4-1 OTI Interconnection for SC7224 (Dual–band frame shown; see NOTES for single–band frame)
ENET1
ENET1
ENET2
ENET2
ENET3
ENET3
PART OF SC7224 FRAME INTERNAL SPAN I/O CABLES SPAN I/O B
SPAN I/O A
EN1
EN2 EN3 SPAN A
EN1
EN2 EN3 SPAN B
CABLE 3088643C33 OR 3088643C40
BTS# MDM GROUP 1
GLI–1 BPR A
CABLE 3088643C33 OR 3088643C40
GLI–2 BPR A
GLI–1 GLI
GLI–2 GLI CABLE 3088643C22
CABLE 3088643C22
GLI #1
GLI #2
CABLE 3088643C39
BTS# MDM GROUP 2
CABLE 3088643C39
WHERE: BTS# = Number of the BTS in the BSS (1 to 1000)
GLI–3 BPR A
GLI–4 BPR A
GLI–3 GLI
GLI–4 GLI
GLI #3
GLI #4
NOTES: 1. SINGLE–BAND FRAME USES ONLY CONNECTIONS TO GLI 1 AND GLI 2 2. BTS EDGE DEVICE CONNECTS TO ANY SPAN I/O CARD ENET 1 AND ENET 2 CONNECTORS WHICH ARE CONNECTED TO GLI3 CARDS.
A1-7224_oti_2mo dem _groups.eps
68P09309A80-2
4-43
FOA
OCT 2010
Configuring BTS File Transfer Protocol – Introduction
Chapter 4: Configuring Packet BTS Transport
Configuring BTS File Transfer Protocol – Introduction ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Motorola BTS models have used File Transfer Protocol (FTP) to transfer data to and from the OMC–R 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 OMC–R. This utility is only used at the cell site before communication is established with the OMC–R to select the transfer protocol for a newly installed BTS (greenfield) or after replacement of a non–redundant 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.
4-44
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
File transfer protocol selection item summary
File transfer protocol selection item summary The following summarizes the selection items included in the Secure FTP Settings dialog box, their function, and the conditions under which they can be selected by the user.
Table 4-6
LMF File Transfer Protocol Selections
Selection
Location in Dialog Box
Description
Conditions when Selection Can Be Chosen
FTP
Protocol group
Protocol to be used for transferring files in unencrypted form to and from NE
BTS is operating with SFTP
SFTP
Protocol group
Protocol to be used for transferring files in encrypted form to and from NE
BTS is operating with FTP
Change protocol type with current settings
Action group
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
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)
NOTE This selection can be used: 1.
During conversion from FTP to SFTP
2.
While BTS is operating with SFTP without changing the protocol
68P09309A80-2
...or... Condition 2: BTS is operating with SFTP
4-45
FOA
OCT 2010
Configuring BTS File Transfer Protocol – New BTS Installation or Non–redundant GLI3 Replacement 4: Configuring Packet BTS Transport
Chapter
Configuring BTS File Transfer Protocol – New BTS Installation or Non–redundant GLI3 Replacement ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The procedures in this section specifically cover configuring the file transfer protocol of a new BTS or a replacement non–redundant GLI3 card.
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 OMC–R and delays in placing the site in service.
Prerequisites The following conditions must be met before performing the procedures: •
The required transfer protocol for the BTS has been specified by the network operator and provisioned at the OMC–R
•
The BTS has power applied, and is operating without traffic or communication with the OMC–R
•
LMF computer must be connected to the BTS
•
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.
Procedure 4-13
1
Determine operating file transfer protocol using the LMF
On the BTS tab menu bar select Util > Secure FTP Settings. Result: The Secure FTP Settings dialog box will open. Continued
4-46
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Changing the operating file transfer protocol
Procedure 4-13
Determine operating file transfer protocol using the LMF (Continued)
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
4
Do one of the following depending on the protocol setting provisioned for this BTS at the OMC–R: •
If the button for the required protocol is not darkened, the protocol must be changed. Proceed to Procedure 4-14 to change the protocol.
•
If the button for the required protocol is darkened, continue to step 4.
If the required operating protocol is SFTP, click in the radio button for Reset username and password in theAction 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 card to IBR, EBR, or OTI operation as specified in the applicable BTS Hardware Modifications manual or the OTI Implementation/Conversion manual, as required.
Changing the operating file transfer protocol Change the file transfer protocol by performing the following.
Procedure 4-14
1
Change operating file transfer protocol using the LMF
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
3
Do one of the following depending on the protocol setting required for operating this BTS on the network: •
If FTP is required, click the FTP radio button in the Protocol group, and skip to step 4.
•
If SFTP is required, click the SFTP radio button, and continue to step 3.
Click in the radio button for Reset username and password in theAction group. Result: The radio button for the selected choice will darken.
4
Click OK. Result: Selected settings are applied, and the dialog box closes. Continued
68P09309A80-2
4-47
FOA
OCT 2010
Changing the operating file transfer protocol
Procedure 4-14 5
Chapter 4: Configuring Packet BTS Transport
Change operating file transfer protocol using the LMF (Continued)
Proceed with converting the GLI3 card to IBR, EBR, or OTI operation as specified in the applicable BTS Packet Backhaul Upgrade manual or the OTI Implementation/Conversion manual, as required.
4-48
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
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 4-7 by performing the following: 1.
Enter the BTS number assigned to the base station where the GLI3 cards are installed (for example, BTS-180)
2.
Enter the software version and backhaul mode required for the BTS in the respective columns on the first line of Table 4-7.
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 step 4 of Procedure 4-1.
4.
Enter the backhaul mode of the GLI3 card installed in BTS card cage slot GLI 1 when determined by performing step step 9 of Procedure 4-1.
Software Version and Backhaul Mode BTS#: _________________
Table 4-7
Software Release and Backhaul Mode Record Software Release
Backhaul Mode
1.Required for BTS 2.GLI 1
68P09309A80-2
4-49
FOA
OCT 2010
OTI configuration settings worksheet
Chapter 4: Configuring Packet BTS Transport
OTI configuration settings worksheet ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Obtain these OTI backhaul configuration settings from the network administrator The identification and IP information to be entered in the Value column of Table 4-8, 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 4-8
OTI Configuration Settings and Values
Configuration Setting
Value
Description
BTS ID (example: BTS-201) for BTS or UBS to be tested
Unique number assigned to each BTS or UBS in network
OTIClientID (example: 1a–2b–3c–4d)
Unique 4–byte hexadecimal value generated for each BTS by the OMC–R
OTI_BTSRTRGRP_IP_addr (example: 10.20.22.4)
4-octet (dotted decimal) IP address unique to the BTS to be tested
OTI_Network_Mask (example: 255.255.255.0)
4-octet (dotted decimal) IP subnet mask for the MLS OTI CON to the BTS to be tested
Record of original NIC configuration Advanced tab of NIC hardware Properties dialog box Table 4-9
Advanced Tab Property List Box Connection Settings - Original
Operating System
Property:
Windows XP
Speed & Duplex
Windows 2000
Connection Type
Original Value:
Internet Protocol (TCP/IP) Properties dialog box General tab ____ Obtain an IP address automatically ____ Use the following IP address: IP address: _______________________________ Subnet mask: _______________________________
OTI verification NIC configuration Advanced tab of NIC hardware Properties dialog box Table 4-10
Advanced Tab Property List Box Connection Settings – for OTI
Operating System
Property:
OTI Test Value:
Windows XP
Speed & Duplex
100 Mb Full
Windows 2000
Connection Type
100 Mbps Full_Duplex
Default Gateway: _______________________________ (See reverse side for Internet Protocol (TCP/IP) Properties Dialog Box General Tab record.)
68P09309A80-2
4-51
FOA
OCT 2010
OTI verification NIC configuration
Chapter 4: Configuring Packet BTS Transport
Internet Protocol (TCP/IP) Properties dialog box General tab CDMA2000 1X OTI test settings: ____ Obtain an IP address automatically X Use the following IP address: IP address: _______________________________ (use value for OTI_BTSRTRGRP_IP_addr from OTI configuration settings worksheet on page 4-50) Subnet mask: _______________________________ (use value for OTI_Network_Mask from OTI configuration settings worksheet on page 4-50) Default Gateway: _______________________________ (use value for MLS_OTI_CON_HSRP_Logical_Addr from OTI configuration settings worksheet on page 4-50)
4-52
68P09309A80-2
FOA
OCT 2010
Chapter
5 Leave the Site ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
68P09309A80-2 OCT 2010
5-1
FOA
Prepare to Leave the Site
Chapter 5: Leave the Site
Prepare to Leave the Site ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
External Test Equipment Removal Perform the procedure in Procedure 5-1 to disconnect the test equipment and configure the BTS for active service.
Procedure 5-1
External Test Equipment Removal
1
Disconnect all external test equipment from all TX and RX connectors on the top of the frame and DMC.
2
Reconnect and visually inspect all TX and RX antenna feed lines at the top of the frame.
CAUTION Verify that all sector antenna feed lines are connected to the correct ports on the frame. Crossed antenna cables will cause system degradation of call processing.
LMF Removal
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 Procedure 5-2 to terminate the LMF session and remove the terminal.
Procedure 5-2 1
LMF Termination and Removal
From the CDMA window select File>Exit.
NOTE The File > Exit command will prompt you to confirm the logout procedure. The File > Logout and Exit command will not prompt you and continues to shut down LMF. 2
From the Windows Task Bar click Start>Shutdown. Click Yes when the Shut Down Windows message appears.
3
Disconnect the LMF terminal Ethernet connector from the BTS cabinet.
4
Disconnect the LMF serial port, the RS-232 to GPIB interface box, and the GPIB cables as required for equipment transport.
5-2
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Re-Activate BTS JT1 Spans
Re-Activate BTS JT1 Spans Before leaving the site, connect any JT1 span TELCO connectors that were removed to allow the LMF to control the BTS. Refer to Procedure 5-3.
Procedure 5-3 1
JT1 Span Connections
For EBR, have OMC-R operator re-activate span lines.
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 Procedure 5-4 to reset all devices and initialize site remotely.
Procedure 5-4
Reset BTS Devices and Remote Site Initialization
1
Terminate the LMF session by following the procedures in Procedure 5-2.
2
Verify that the operator has re-activated the spans.
3
Packet BTS procedure: From the BTS site, have the OMC-R operator PREACTIVATE the BTS to the required software version for the BSS. There are two types of PREACTIVATE load processes: •
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.
4
Account for all tools used and parts used/removed on the BTS during the operations, being that none are left on or inside the BTS.
5
Visually inspect the BTS for any other foreign objects left inside, and remove any that are discovered.
6
Visually inspect all cable connections, ensuring they are connected as required for normal BTS operation.
7
Be sure all internal BTS cables are routed and secured to prevent damage to them.
8
Verify no alarm conditions are being reported to the OMC-R.
9
After all activities at the site have been completed, contact the OMC-R and confirm that the BTS is under OMC-R control.
68P09309A80-2 OCT 2010
5-3
FOA
Reset All Devices and Initialize Site Remotely
Chapter 5: Leave the Site
5-4
68P09309A80-2
FOA
OCT 2010
Chapter
6 Basic Troubleshooting ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
68P09309A80-2 OCT 2010
6-1
FOA
Troubleshooting Overview
Chapter 6: Basic Troubleshooting
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.
6-2
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Troubleshooting: Test Equipment Installation
Troubleshooting: Test Equipment Installation ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Cannot Log into Cell-Site Follow the procedure in Procedure 6-1 to troubleshoot a login failure.
Procedure 6-1
Login Failure Troubleshooting Procedures
1
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 DMC.
2
Verify that T1 is disconnected. If T1 is still connected, verify the OMC-R has disabled the BTS.
3
Try pinging the MGLI (see Pinging the Processor on page 3-50).
4
Verify the LMF is connected to the Primary LMF port (LAN A). See Procedure 3-4.
5
Verify the LMF was configured properly (see Preparing the LMF section).
6
Verify the BTS-LMF cable is RG-58 [flexible black cable of less than 76 cm (2.5 feet) length].
7
Verify the Ethernet ports are terminated properly (see Figure 3-8).
8
Re-boot the LMF and retry.
9
Re-seat the MGLI and retry.
10
Verify IP addresses are configured properly.
Cannot Communicate to Power Meter Follow the procedure in Procedure 6-2 to troubleshoot a power meter communication failure.
Procedure 6-2
Troubleshooting a Power Meter Communication Failure
1
Verify the Power Meter is connected to the LMF with a GPIB adapter.
2
Verify the cable setup as specified in Chapter 3 Acceptance Test Procedures.
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 procedures in GPIB Interface Test Equipment Manual Selection and Autodetection on page G-47 and the applicable GPIB Addresses section of Appendix D Test Equipment Preparationfor details.
4
Verify the GPIB adapter DIP switch settings are correct. Refer to Verifying and Setting GPIB Addresses: RS232 GPIB Interface Box on page D-20for details. Continued
68P09309A80-2
6-3
FOA
OCT 2010
Cannot Communicate to GPIB Based Communications Analyzer
Procedure 6-2
Chapter 6: Basic Troubleshooting
Troubleshooting a Power Meter Communication Failure (Continued)
5
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.
6
Verify the LMF computer COM1 port is not used by another application; for example, if a HyperTerminal window is open for MMI, close it.
7
Reset all test equipment by clicking Util in the BTS menu bar and selecting Test Equipment>Reset from the pull-down lists.
Cannot Communicate to GPIB Based Communications Analyzer Follow the procedure in Procedure 6-3 to troubleshoot a communications analyzer communication failure.
Procedure 6-3
Troubleshooting a Communications Analyzer Communication Failure
1
Verify the analyzer is connected to the LMF with GPIB adapter.
2
Verify the cable setup.
3
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 GPIB Interface Test Equipment Manual Selection and Autodetection on page G-47 and the applicable GPIB address section of Appendix D Test Equipment Preparation for details.
4
Verify the GPIB adapter DIP switch settings are correct. Refer to Verifying and Setting GPIB Addresses: RS232 GPIB Interface Box on page D-20 for details.
5
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.
6
Verify the LMF computer COM1 port is not used by another application; for example, if a HyperTerminal window is open for MMI, close it.
7
Reset all test equipment by clicking Util in the BTS menu bar and selecting Test Equipment>Reset from the pull-down lists.
6-4
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Troubleshooting: Enable
Troubleshooting: Enable ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
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: •
Enabled (green, INS)
•
Disabled (yellow, OOS_RAM)
•
Reset (blue, OOS_ROM)
Follow the procedure in Procedure 6-4 to troubleshoot a device enable failure.
Procedure 6-4
Troubleshooting Device Enable (INS) Failure
1
Re-seat the card and repeat the code and data load procedure.
2
If the CSM cannot be enabled, verify the NEC file has correct latitude and longitude data for cell site location and GPS sync.
3
Ensure the primary CSM is in INS_ACT state.
NOTE MCCs will not go INS without the CSM being INS. 4
Verify the 19.6608 MHz CSM clock; MCCs will not go INS otherwise.
5
If MCCs give “invalid or no system time", verify the CSM is operable.
Miscellaneous Errors Perform the procedure in Procedure 6-5 to troubleshoot miscellaneous failures.
Procedure 6-5
Miscellaneous Failures
1
If XMIs continue to give alarms, even after cycling power at the circuit breakers, then connect an MMI cable to the XMI and set up a Hyperterminal connection (see Procedure 3-3.
2
Enter ALARMS in the Hyperterminal window. The resulting LMF display may provide an indication of the problem. (Call Field Support for further assistance.)
68P09309A80-2
6-5
FOA
OCT 2010
Troubleshooting: Calibration
Chapter 6: Basic Troubleshooting
Troubleshooting: Calibration ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Calibration Audit Failure Follow the procedure in Procedure 6-6 to troubleshoot a calibration audit failure.
NOTE Only one carrier can be tested at a time. All XMIs must be INS during testing.
Procedure 6-6
Troubleshooting Calibration Audit Failure
1
Verify the Power Meter is configured correctly (refer to the test equipment setup section of Chapter 3 Acceptance Test Procedures.)
2
Re-calibrate the Power Meter and verify it is calibrated correctly with cal factors from the sensor head.
3
Verify that XMIs are INS.
4
Reset the XMIs by taking control of the Serializers, then releasing them. The Serializers will default, then go INS. The XMIs will soon follow.
5
Verify that no sensor head is functioning improperly by checking it with the 1 mW (0 dBm) Power Ref signal.
6
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.
7
Re-try the audit.
6-6
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Troubleshooting: Transmit ATP
Troubleshooting: Transmit ATP ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
BTS passed Reduced ATP tests but has forward link problem during normal operation Follow the procedure in Procedure 6-7 to troubleshoot a Forward Link problem during normal operation.
Procedure 6-7 1
Troubleshooting Forward Link Failure (BTS Passed Reduced ATP)
Perform these additional TX tests to troubleshoot a forward link problem: (See Appendix H Optional Full Acceptance Test Procedures) •
TX mask
•
TX rho
•
TX code domain
Cannot Perform TX Mask Measurement Follow the procedure in Procedure 6-8 to troubleshoot a TX mask measurement failure.
NOTE Only one carrier can be tested at a time. All XMIs must be INS during testing.
Procedure 6-8
Troubleshooting TX Mask Measurement Failure
1
Verify that TX audit passes for the XMI(s).
2
If performing manual measurement, verify analyzer setup.
3
Verify that XMIs are INS.
4
Reset the XMIs by taking control of the Serializers, then releasing them. The Serializers will default, then go INS. The XMIs will soon follow.
5
Try to Re-audit
68P09309A80-2
6-7
FOA
OCT 2010
Cannot Perform Rho or Pilot Time Offset Measurement
Chapter 6: Basic Troubleshooting
Cannot Perform Rho or Pilot Time Offset Measurement Follow the procedure in Procedure 6-9 to troubleshoot a rho or pilot time offset measurement failure.
Procedure 6-9
Troubleshooting Rho and Pilot Time Offset Measurement Failure
1
Verify presence of RF signal by switching to spectrum analyzer screen.
2
Verify PN offset displayed on the analyzer is the same as the PN offset in the NEC file.
3
Replace suspected XMI with a known good one and repeat the test.
4
If performing manual measurement, verify spectrum analyzer setup.
5
Verify that no XMI is in alarm state (flashing red LED).
6
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 Shift-avg 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.
Cannot Perform Code Domain Power and Noise Floor Measurement Perform the procedure in Procedure 6-10 to troubleshoot a code domain and noise floor measurement failure.
Procedure 6-10 Failure
Troubleshooting Code Domain Power and Noise Floor Measurement
1
Verify presence of RF signal by switching to spectrum analyzer screen.
2
Verify PN offset displayed on analyzer is same as PN offset being used in the NEC file.
3
Disable and re-enable MCC (one or more MCCs based on extent of failure).
6-8
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Troubleshooting: Receive ATP
Troubleshooting: Receive ATP ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Multi-FER Test Failure Perform the procedure in Procedure 6-11 to troubleshoot a Multi-FER failure.
Procedure 6-11
Troubleshooting Multi-FER Failure
1
Verify that the sector-carrier (MCC) under test is enabled.
2
Verify the test equipment set up is correct for an FER test.
3
Verify the test equipment is locked to 19.6608 MHz and even second clocks.
4
Verify the MCCs have been loaded with data and are INS-ACT.
5
Disable and re-enable the MCC (one or more based on extent of failure).
6
Verify the antenna connections to BTS are correct based on the directions messages.
68P09309A80-2
6-9
FOA
OCT 2010
Troubleshooting: CSM Checklist
Chapter 6: Basic Troubleshooting
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.
RF-GPS (Local GPS) - CSM kit SGLN1145GE or later (with GPS), should be installed in slot 1 and Kit SGLN4132GE (without GPS) is installed in slot 2.. CSM Kit SGLN4132GE or later, 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 Sub-system 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 % blockage in visibility. Any decrease in visibility greater than 50 % will likely result in increased numbers of GPS reference source failure alarms.
6-10
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
CSM Reference Source Configuration Error
CSM Reference Source Configuration Error This problem is caused by incorrect reference source configuration performed in the field by software download. CSM kits SGLN1145GE and SGLN4132GE must have proper reference sources configured (as shown below) to function correctly. CSM Kit No.
Hardware Configuration
CSM Slot No.
Reference Source Configuration
NEC Value
SGLN1145GE
With GPS Receiver
1
Primary = Local GPS Backup = HSO
0 2 or 18
SGLN4132GE
Without GPS Receiver
2
Primary = Mate GPS Backup = HSO
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 and HSO/MSO verification section in Chapter 3 Acceptance Test Procedures. 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 10 dB signal loss at a 1.575 GHz 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.0 dB. 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 NEC file is accurate. The , and should be within +/-200 m in the estimated mode and +/-30 m in the surveyed mode. The surveyed mode should only be used when absolutely necessary.
68P09309A80-2
6-11
FOA
OCT 2010
Troubleshooting: XMI Module
Chapter 6: Basic Troubleshooting
Troubleshooting: XMI Module ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
No DC Voltage (+27 Volts) to a Specific XMI Perform the procedure in Procedure 6-12 to troubleshoot a DC input voltage to GLI or XMI failure.
Procedure 6-12 1
No DC Input Voltage to XMI Module
Verify DC power is applied to the BTS frame.
2
WARNING Before touching an XMI Module, note whether the HOT sticker is fully visible. If so, do not touch the metal surfaces of the XMI with unprotected hands. The HOT sticker will become fully visible when the XMI metal case temperature reaches 50°C. However, the sticker may be partially visible at lower case temperatures. Verify that XMIs are properly seated. Re-seat as required. 3
Unseat suspect XMI module and inspect the connector for damage.
4
Replace suspect XMI module with known good XMI module. Repeat test.
6-12
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Troubleshooting: DMC Backplane
Troubleshooting: DMC Backplane ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction The DMC backplane is a multi-layer board that interconnects all the DMC 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: •
Determine which connector(s) is associated with a specific problem type.
•
Isolate problems to a specific cable or connector.
Span Line Connector The 50-pin span line connector provides a primary and secondary (if used) span line interface to each GLI in the DMC shelf. The span line is used for MM/EMX switch control of the Master GLI and also all the XMI traffic.
Power Input (Return A, B, and C connectors) For +27 V configuration - Provides input for regulated +27 Volts.
Power Supply Interface Each DMC power supply has a series of three different connectors to provide the needed inputs/outputs to the DMC backplane. These include a VCC/Ground input connector, a Harting style multiple pin interface, and a +15 V/Analog Ground output connector. The DMC Power Supplies convert +27 Volts to a regulated +15, +6.5, and +5.0 Volts to be used by the DMC shelf cards.
GLI Connector This connector consists of a Harting 4SU digital connector and a 6-conductor coaxial connector for RDM distribution. The connectors provide inputs/outputs for the GLIs in the DMC backplane.
GLI 10Base-2 Ethernet “A" and “B" Connections These BNC connectors are located on the DMC 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.
68P09309A80-2
6-13
FOA
OCT 2010
DMC Backplane Troubleshooting Procedure
Chapter 6: Basic Troubleshooting
DMC Backplane Troubleshooting Procedure Procedure 6-13 through Procedure 6-20 provide procedures for troubleshooting problems that appear to be related to a defective DMC 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: Procedure 6-13 through Procedure 6-20 must be completed before replacing ANY DMC backplane.
Digital Control Problems No GLI Control via LMF (all GLIs) Follow the procedure in Procedure 6-13 to troubleshoot a GLI control via LMF failure.
Procedure 6-13
No GLI Control via LMF (all GLIs)
CAUTION Ensure that an ESD device is worn before handling any circuit card or module. 1
Check the 10Base-2 ethernet connector for proper connection, damage, shorts, or opens.
2
Visually check the master GLI connector (both board and backplane) for damage.
3
Replace the master GLI with a known good GLI.
No GLI Control through Span Line Connection (All GLIs) Follow the procedures in Procedure 6-14 to troubleshoot GLI control failures.
Procedure 6-14
MGLI Control Good - No Control over Co-Located GLI
CAUTION Ensure that an ESD device is worn before handling any circuit card or module. 1
Verify that the BTS and GLIs are correctly configured in the OMC-R CBSC data base.
2
Check the 10Base-2 ethernet connector for proper connection, damage, shorts, or opens. Continued
6-14
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 6-14
Digital Control Problems
MGLI Control Good - No Control over Co-Located GLI (Continued)
3
Visually check all GLI connectors (both board and backplane) for damage.
4
Replace the remaining GLI with a known good GLI.
No AMR Control (MGLI good) Perform the procedure in Procedure 6-15 to troubleshoot an AMR control failure when the MGLI control is good.
Procedure 6-15
MGLI Control Good — No Control over AMR
CAUTION Ensure that an ESD device is worn before handling any circuit card or module. 1
Visually check the master GLI connector (both board and backplane) for damage.
2
Replace the master GLI with a known good GLI.
3
Replace the AMR with a known good AMR.
No XMI Control in the Shelf - (No Control over Co-located GLIs) Perform the procedure in Procedure 6-16 to troubleshoot a XMI control in the shelf failure.
Procedure 6-16
No XMI Control in the Shelf — No Control over Co-located GLIs
CAUTION Ensure that an ESD device is worn before handling any circuit card or module. 1
Visually check all GLI connectors (both board and backplane) for damage.
2
Replace the remaining GLI with a known good GLI.
3
Visually check XMI connectors for damage.
4
Replace the XMI with a known good XMI.
68P09309A80-2
6-15
FOA
OCT 2010
DC Power Problems
Chapter 6: Basic Troubleshooting
No (or Missing) MCC Channel Elements Perform the procedure in Procedure 6-17 to troubleshoot a channel elements failure.
Procedure 6-17
No MCC Channel Elements
CAUTION Ensure that an ESD device is worn before handling any circuit card or module. 1
Verify CEs on a co-located MCC-1X.
2
If the problem seems to be limited to one MCC, replace the MCC with a known good MCC. •
3
If no CEs on any MCC: •
4
Check connectors (both board and backplane) for damage.
Verify clock reference.
Check the NEC for MCC-1X.
DC Power Problems
WARNING Potentially lethal voltage and current levels are routed to the BTS equipment. his 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 Perform the procedure in Procedure 6-18 to troubleshoot a DC input voltage to power supply module failure.
Procedure 6-18
No DC Input Voltage to Power Supply Module
1
Verify DC power is applied to the BTS frame.
2
Verify there are no breakers tripped.
NOTE 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. Continued
6-16
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure 6-18 •
TX and RX Signal Routing Problems
No DC Input Voltage to Power Supply Module (Continued)
If the breaker does not trip, there is probably a defective module or sub-assembly within the shelf.
3
Verify that the DMC shelf breakers are functional.
4
Use a voltmeter to determine if the input voltage is being routed to the DMC backplane by measuring the DC voltage level on the PWR_IN cable.
5
•
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.
If steps step 1 through step 4 fail to indicate a problem, a DMC backplane failure (possibly an open trace) has occurred.
No DC Voltage (+5, +6.5, +15 Volts) to a Specific GLI Perform the procedure in Procedure 6-19 to troubleshoot a DC input voltage to GLI failure.
Procedure 6-19
No DC Input Voltage to any DMC Shelf
1
Verify the steps in Procedure 6-18 have been performed.
2
Inspect the defective board/module (both board and backplane) connector for damage.
3
Replace suspect board/module with known good board/module.
TX and RX Signal Routing Problems Perform the procedure in Procedure 6-20 to troubleshoot TX and RX signal routing problems.
Procedure 6-20
TX and RX Signal Routing Problems
1
Inspect all Harting Cable connectors and back-plane connectors for damage in all the affected board slots.
2
Perform steps in the RF path troubleshooting flowchart in this manual.
68P09309A80-2
6-17
FOA
OCT 2010
Troubleshooting: GLI3 card continually reboots after converting to satellite backhaul
Chapter 6: Basic Troubleshooting
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 timeout Reset due Backhaul timeout DHCP attempt timed out Reset due Backhaul 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 OMC–R but will be generating communication alarms such as “Packet Backhaul Down.” The BTS and OMC–R will be unable to communicate. Because of this, a site visit is needed to correct this condition. This procedure can also be used to pre–configure a GLI3 card for satellite backhaul before commissioning or converting a BTS.
Prerequisites The following are required to perform the corrective procedure: •
Laptop computer with at least one serial port or laptop computer meeting the LMF computer platform requirements specified in the BTS optimization/ATP manual
•
One of the following: Motorola cable part number CGDSMMICABLE219112 (see Figure 3-3 for connection) Fabricated DB–9 receptacle–to–8–contact MMI connector cable (see MMI Cable Fabrication on page F-2 for fabrication instructions and Figure 3-3 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
•
(For use with SLN2006A only) Straight–through RS–232 cable, DB–9 to DB–9, and DB–9 to DB–25 connector adapter
•
A terminal emulation application such as HyperTerminal or PuTTY
6-18
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Performing the correction
Performing the correction Perform the following to convert the GLI3 card to satellite backhaul and establish communication with the OMC–R.
Procedure 6-21 Intervals
Setting GLI3 Backhaul Type to Satellite and Correct Timeout
1
Upon arrival at the site, contact the OMC–R and notify the operator that site operations are starting.
2
Locate the INS_ACT GLI3 card.
NOTE The INS_ACT card LEDs will show the following indications: •
STA: Slow flashing green
•
ACT: green
3
Start an MMI communication session with the INS_ACT GLI3 card by following the instructions and illustrations in Establishing an MMI Communication Session on page 3-24.
4
In a BTS with redundant GLI3 cards, locate the INS_SBY card.
NOTE The INS_SBY card LEDs will show the following indications: •
STA: Slow flashing green
•
ACT: OFF
5
Disable the INS_SBY GLI3 card by unseating it from the backplane.
6
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
Oscillator speed: 66000000
+---------------------------------------+ | GLI3 BootROM Version
22.00.70.37 | Continued
68P09309A80-2
6-19
FOA
OCT 2010
Performing the correction
Chapter 6: Basic Troubleshooting
Procedure 6-21 Setting GLI3 Backhaul Type to Satellite and Correct Timeout Intervals (Continued) +---------------------------------------+ | 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 |
The GLI3 boot process must be stopped within 3 seconds after the Press any key to stop auto-boot... line appears (see highlighted output line in the following):
VxWorks System Boot
Copyright 1984-1998
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 auto-boot...
6-20
Continued
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Performing the correction
Procedure 6-21 Setting GLI3 Backhaul Type to Satellite and Correct Timeout Intervals (Continued)
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
When the Press any key to stop auto-boot... line appears, press the Enter key.
9
The system will display a response similar to the following:
Press any key to stop auto-boot... 3 2 [VxWorks Boot]: 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. 11
Verify that the backhaul type has been changed to satellite by entering the following at the [VxWorks Boot]: prompt: bkhaul_type_get The system will display a response similar to the following:
[VxWorks Boot]: bkhaul_type_get The current backhaul type is SATELLITE. Continued
68P09309A80-2
6-21
FOA
OCT 2010
Performing the correction
Chapter 6: Basic Troubleshooting
Procedure 6-21 Setting GLI3 Backhaul Type to Satellite and Correct Timeout Intervals (Continued) 12
Verify the current satellite backhaul Link Control Protocol (LCP) values by entering the following at the [VxWorks Boot]: prompt: sat_bkhaul_get The system will display a response similar to the following:
VxWorks Boot]: sat_bkhaul_get Satellite Backhaul LCP Neg-Retry 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 The system will display a response similar to the following:
[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 The system will display a response similar to the following:
[VxWorks Boot]: sat_bkhaul_set neg_retry_int 3 Set neg_retry_int successfully.
Continued
6-22
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Performing the correction
Procedure 6-21 Setting GLI3 Backhaul Type to Satellite and Correct Timeout Intervals (Continued) 15
Verify that the LCP parameter values have been set correctly by entering the following at the [VxWorks Boot]: prompt: sat_bkhaul_get The system will display a response similar to the following:
VxWorks Boot]: sat_bkhaul_get Satellite Backhaul LCP Neg-Retry 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]: @
boot device
: tffs=0,0
unit number
: 0
processor number
: 0
file name code/gli3_pkt1.elf
: /ram00/projects/cdmaazlabs/frame/RF-7224_14/
inet on ethernet (e) : 128.0.0.2:ffffff80 host inet (h)
: 192.168.1.8
user (u)
: anonymous
ftp password (pw)
: user
flags (f)
: 0x0
<<< remaining output omitted >>>
Continued
68P09309A80-2
6-23
FOA
OCT 2010
Performing the correction
Chapter 6: Basic Troubleshooting
Procedure 6-21 Setting GLI3 Backhaul Type to Satellite and Correct Timeout Intervals (Continued) 17
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
When the GLI3 reaches INS_ACT, reseat the redundant GLI3 in its backplane slot (if the BTS is so equipped).
19
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).
20
When the GLI3 card(s) are INS, contact the OMC–R operator and:
21
•
Advise the operator that the BTS is operational with the correct backhaul settings
•
Request notification when communication between the OMC–R and the BTS is confirmed
When notified that the OMC–R and BTS can communicate, advise the operator that site operations are complete, and perform the procedures in the Prepare to leave the site section.
6-24
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
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 PWR/ALM LED The following list describes the states of the module status indicator. •
Solid GREEN - module operating in a normal (fault free) condition.
•
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.
PWR/ALM LED The following list describes the states of the bi-color LED. •
Solid GREEN - module operating in a normal (fault free) condition.
•
Solid RED - module is operating in a fault (alarm) condition due to electrical hardware problem.
68P09309A80-2
6-25
FOA
OCT 2010
CSM Indicator and Connectors
Chapter 6: Basic Troubleshooting
CSM Indicator and Connectors
Figure 6-1
CSM Front Panel Indicator and Monitor Connectors
SYNC MONITOR
SYNC MONITOR PWR/ALM
PWR/ALM Indicator
FREQ
MONITOR
FREQ MONITOR
FW00303 ti-cdma-00111.eps
PWR/ALM LED The CSM includes on-board alarm detection. Hardware and software/firmware state and alarm conditions are displayed by the front panel LED indicator (Figure 6-1). For detailed descriptions of displayed state/alarm indications refer to Table G-1 and Front Panel LED and Status Displays in the CSM System Time - GPS and HSO/MSO Verification section of Chapter 3 Acceptance Test Procedures.
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.
6-26
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
GLI LED Status Combinations
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 Only accessible behind front panel. The RS-232 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 GLI The GLI module has indicators, controls and connectors as described below and shown in Table 6-1(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.
ALARM •
Solid RED - GLI is in a fault condition or in reset.
•
While in reset transition, STATUS LED is OFF while GLI is performing ROM boot (about 12 seconds for normal boot).
•
While in reset transition, STATUS LED is ON while GLI is performing RAM boot (about 4 seconds for normal boot).
•
Off - No Alarm.
•
Flashing GREEN- GLI is in service (INS), in a stable operating condition.
•
On - GLI is in OOS RAM state operating downloaded code.
•
Off - GLI is in OOS ROM state operating boot code.
STATUS
68P09309A80-2
6-27
FOA
OCT 2010
GLI Controls, Indicators, and Connectors
Chapter 6: Basic Troubleshooting
SPANS •
Solid GREEN - Span line is connected and operating.
•
Solid RED - Span line is disconnected or a fault condition exists.
GLI Controls, Indicators, and Connectors Table 6-1shows the front panel of the GLI3 card and includes the descriptions, locations, and/or indications for each control, indicator, and connector.
Table 6-1 Item
GLI3 Front Panel Function/Indications
BPR A
Connects to either a BPR or expansion cage and is wired as an Ethernet client.
BPR B
Connects to either a BPR or expansion cage and is wired as an Ethernet client.
AUX
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.
GLI
Supports the cross-coupled Ethernet circuits to the mate GLI using a double crossover cable.
RESET
Pressing and releasing the switch resets all functions on the GLI3.
ALARM
OFF – operating normally ON – briefly during power-up when the Alarm LED turns OFF SLOW GREEN – when the GLI3 is INS (in-service)
SPAN
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
MMI
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.
STATUS
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 first–time 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.)
ACTIVE
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
6-28
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Figure 6-2
XMI Module Status /Alarm LED Combination
GLI3 Card Front Panel Controls, Indicators, and Connectors
BPR A BPR B
100BASE-T to BTS Packet Router or Expansion cage
AUX
100BASE-T Auxiliary Monitor Port
GLI
Dual 100BASE-T in a single RJ45 to Redundant (Mate) GLI3 SPAN
ALARM RESET
Reset Switch Span (LED)
MMI
Alarm (LED) MMI Port ACT
STA
Active (LED) Status (LED)
ti-cdma-00699.eps
XMI Module Status /Alarm LED Combination XMI Module Status/Alarm LED Each XMI module contains a bi-color LED between the MMI and LMT connectors on the front panel of the module. Interpret this LED as follows: •
GREEN - XMI module is active and is reporting no alarms (Normal condition).
•
Flashing GREEN/RED - XMI module is active but is reporting an low input power condition. If no XMI is keyed, this is normal and does not constitute a failure.
•
Solid RED Red - initializing or power-up alarm
•
Slowly Flashing GREEN - OOS_ROM no alarm
68P09309A80-2
6-29
FOA
OCT 2010
XMI Module Status /Alarm LED Combination
Chapter 6: Basic Troubleshooting
•
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
6-30
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Figure 6-3
XMI Module Status /Alarm LED Combination
XMI Module
XMI CARD TOP
Status/Alarm LED
BOTTOM ti-cdma-00037-A.eps
68P09309A80-2
6-31
FOA
OCT 2010
MCC LED Status Combinations
Chapter 6: Basic Troubleshooting
MCC LED Status Combinations The MCC module has LED indicators and connectors as described below (see Figure 6-4). Note that the figure does not show the connectors as they are concealed by the removable lens.
MMI Connectors •
The RS-232 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.
Figure 6-4
PWR/ALM
PWR/ALM LED
MCC Front Panel
LENS (REMOVABLE)
ACTIVE
ACTIVE LED
ti-cdma-00113.eps
The RJ-11 ethernet port connector (eight-pin) is intended to be used primarily in the development environment but may be used in the field for high data rate debugging purposes.
6-32
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Table 6-2
Serializer
MCC Front Panel
LED
COLOR
OPERATING STATUS
PWR/ALM
RED
OFF - operating normally ON - briefly during power-up and during failure conditions
ACTIVE
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)
RED
ON - fault condition SLOW FLASHING (alternating with green) - CHI bus inactive on power-up
Serializer The SER card contains the following front panel LEDs: •
ACT (Active/Standby) - red/green. This LED indicates the operating status of the redundant cards. The redundant card toggles automatically if the active card is removed or fails
•
STA (Power/Alarm) - red/green/amber
•
XMI Serial Data Port LED 1 - red
•
XMI Serial Data Port LED 2 - green
Table 6-3 shows the possible states for the SER front panel ACT and STA LEDs and the corresponding device states.
Table 6-3
Serializer Front Panel ACT & STATUS LEDs and Device States
ACT LED State
STA LED State
Device Status
OFF
OFF
No DC operating power to card
RED
RED
Card is booting up and running test mode diagnostics. This occurs upon power-up and reset. Card failed to initialize.
OFF
RED
Card has detected an alarm condition and is OOS (out-of-service).
GREEN
Slow Flashing Green
Card is INS (in-service) and Active; normal in service no fault operation.
OFF
Slow Flashing Green
Card is INS (in-service) and Standby; normal in service no fault operation.
Table 6-4 shows the possible states for the SER front panel XMI serial data port LEDs and the corresponding device states. These LEDs indicate the port link status.
68P09309A80-2
6-33
FOA
OCT 2010
Serializer
Table 6-4
Chapter 6: Basic Troubleshooting
Serializer Front Panel XMI Serial Data Port ACT & STATUS LEDs and Device States
ACT LED State
STA LED State
Device Status
OFF
OFF
No DC operating power to card. Card is not initialized.
OFF
GREEN
SER card is Active and serial data link with XMI is established and operational.
RED
GREEN
SER card is Active, but serial data link/port is down or serial data cable/connector is unplugged.
RED
OFF
SER card is Standby.
Figure 6-5
Serializer Module Detail
XMI Data Port Detail (Shown for XMI 1 & 2, XMI 3 & 4 is similar.) XMI 2 - LED 1
XMI 1 - LED 1
Card Ejector/Latch
XMI 2
XMI 1
XMI 2 - LED 2
XMI3 XMI4
XMI 3 Serial Data Port (NOTE 1)
XMI 4 Serial Data Port (NOTE 1) XMI1 XMI2
XMI 1 Serial Data Port (NOTE 1)
XMI 2 Serial Data Port (NOTE 1) RESET
Reset Switch
MMI
MMI (RS-232) Port
XMI 1 - LED 2
NOTE: 1. XMI 1 - 4 serial data ports are 20-pin SFP (Small Form Factor Pluggable) connectors. Each SFP connector has two status LEDs. See XMI Data Port Detail in diagram inset.
ACT
STA
Active LED
Status (Pwr/Alm) LED Card Ejector/Latch
ti-cdma-00114.eps
6-34
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Card or Module Reset Restrictions
Card or Module Reset Restrictions ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview If a device is rest 4 tines in succession within a 60–minute period, the device will not be recovered and be placed OOS. After the fourth reset, it will be 60 minutes before another recovery attempt can be made locally to place the device INS.
Reset Actions that Cause Device to go OOS Performing four of the following actions (in any combination) within a 60–minute period will cause the device to be placed OOS.
•
Reset by toggling the module switch (ON/OFF)
•
Reset by removing the card or module
•
Reset the card or module by depressing the front panel RESET button
•
Reset the card or module through a computer using the MMI command
Recovery To enable the device during the 60–minute waiting period, the OMC–R must lock and unlock it.
Service Impact The device will be unavailable until either the 60–minute waiting period expires or the device is locked and unlocked by the OMC–R. There is no direct impact on service resulting from the lock/unlock operation.
Affected Devices The following devices are affected by the reset restrictions. Not all the devices may be in use in a particular BTS.
68P09309A80-2
6-35
FOA
OCT 2010
Affected Devices
Chapter 6: Basic Troubleshooting
•
BBX
•
CRMS
•
CSM
•
LPAC
•
MACH (AMR)
•
MCC*
•
TGLI
•
SER
•
XMI
* For the MCC, resets caused by code loads are not counted in the reset restriction.
6-36
68P09309A80-2
FOA
OCT 2010
Appendix
A
Data Sheets
68P09309A80-2 OCT 2010
A-1
FOA
Optimization (Pre-ATP) Data Sheets for Multi-Carrier
Appendix A: Data Sheets
Optimization (Pre-ATP) Data Sheets for Multi-Carrier ■
Site Temperature Dress Covers/Brackets Comments:________________________________________________________ ____________________________________________________________________ ____________________________________________________________________ ____________________________________________________________________
DDRF Part of the SC7224DT Dual Technology frames. DDRF1: _________________________________ DDRF2: _________________________________ DDRF3: _________________________________
Cellular Remote Monitoring System (CRMS) CRMS:_________________________________
BSI Part of the SC7224DT Dual Technology frames. BSI: _________________________________
BCU3 Part of the SC7224DT Dual Technology frames. BCU3: _________________________________
68P09309A80-2 OCT 2010
A-11
FOA
A-12
68P09309A80-2
FOA
OCT 2010
Appendix
B
FRU Optimization/ATP Test Matrix
68P09309A80-2 OCT 2010
B-1
FOA
FRU Optimization/ATP Test Matrix
Appendix B: FRU Optimization/ATP Test Matrix
FRU Optimization/ATP Test Matrix ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Usage & Background Re-optimization of specific portions of the site may be required. An outline of some basic guidelines is included in the following tables.
NOTE Re-optimization 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 B-1
When RF Optimization is Required on the BTS Item Replaced
Optimize
DMC Shelf
All sector TX and RX paths to all DMC shelves.
XMI Module
All sector-carrier TX/RX paths.
IDRF or DDRF
The affected sector TX path.
Inter-frame Cabling Optimization must be performed after the replacement of any RF cabling between BTS frames.
Table B-2
When to Optimize Inter-frame Cabling Optimize
Item Replaced Ancillary frame to BTS frame (RX) cables
The affected sector/antenna RX paths.
BTS frame to ancillary frame (TX) cables
The affected sector/antenna TX paths.
Detailed Reduced ATP Test Matrix Table B-3 outlines the reduced ATP tests that required to be run at the site to ensure proper operation of new or replaced components. It is also assumed that all modules are placed OOS-ROM via the LMF until full redundancy of all applicable modules is implemented.
B-2
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Detailed Optional Full ATP Test Matrix
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 re-running the TX Audit and RSSI tests.
Table B-3
Reduced ATP Test Matrix Procedure
TEST
Reference
IDRF
Procedure 3-18 Procedure 3-19
TX Audit RSSI Test
DDRF
Procedure 3-18 Procedure 3-19
TX Audit RSSI Test
XMI
Procedure 3-16 Procedure 3-18 Procedure 3-19
Ping the Processor TX Audit RSSI Test
MCC
Procedure 3-16 Procedure 3-18 Procedure 3-19
Ping the Processor TX Audit RSSI Test
RX Cables
Procedure 3-19
RSSI Test
TX Cables
Procedure 3-18 Procedure 3-19
TX Audit RSSI Test
HSO/MSO
1
Serializer Module
Procedure 3-18
TX Audit
3
DMC Backplane
Procedure 3-16 Procedure 3-18
Ping the Processors TX Audit
1
GLI
Procedure 3-16 Procedure 3-18
Ping the Processors TX Audit
2
CSM
Procedure 3-16 Procedure 3-18
Ping the Processors TX Audit
3
OPTIMIZATION AND TEST LEGEND 1 — Perform on all carrier and sector RX paths to the DMC cage. 2 — Perform on all affected carrier and sector RX paths. 3 — Verify performance by performing on one sector of one carrier only.
Detailed Optional Full ATP Test Matrix Table B-4 outlines the optional ATP tests that would need to be performed if the user wants to fully test the BTS components or if the reduced ATP fails. It is also assumed that all modules are placed OOS-ROM via the LMF until full redundancy of all applicable modules is implemented. For more information refer to Appendix HAppendix H Optional Full Acceptance Test Procedures. The following guidelines should also be noted when using this table.
68P09309A80-2 OCT 2010
B-3
FOA
Detailed Optional Full ATP Test Matrix
Appendix B: FRU Optimization/ATP Test Matrix
NOTE Not every procedure required to bring the site back on line is indicated in Table B-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, 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 DMC BACKPLANE is replaced, it is assumed that only power to the DMC shelf being replaced is turned off via the breaker supplying that shelf.
Ping the Processors Enable CSMs Enable MCCs GPS Initialization/Verification HSO/MSO Initialization/Verification TX Audit RSSI Test TX Mask ATP Waveform Quality ATP Pilot Time Offset ATP Code Domain Power/Noise Floor FER Test
Ping the Processors Enable CSMs GPS Initialization/Verification HSO/MSO Initialization/Verification RSSI Test Waveform Quality ATP Pilot Time Offset ATP Code Domain Power/Noise Floor FER Test
— 6 * * 6 6
OPTIMIZATION AND TEST LEGEND
68P09309A80-2 OCT 2010
B-5
FOA
Detailed Optional Full ATP Test Matrix
Table B-4 Test
Appendix B: FRU Optimization/ATP Test Matrix
Full ATP Test Matrix (Continued)
Procedure
Description
Reference
* Perform if necessary for additional fault isolation, repair assurance, or site certification 1 Perform on all carrier and sector TX paths to the DMC cage. 2 Perform on all carrier and sector RX paths to the DMC cage. 3 Perform on all primary and redundant TX paths of the affected carrier. 4 Perform on the affected carrier and sector TX paths. 5 Perform on the affected carrier and sector RX paths. 6 Verify performance by performing on one sector of on carrier only.
B-6
68P09309A80-2
FOA
OCT 2010
Appendix
C
CDMA Operating Frequency
68P09309A80-2 OCT 2010
C-1
FOA
CDMA Operating Frequency Programming Information
Appendix C: CDMA Operating Frequency
CDMA Operating Frequency Programming Information ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction Programming of each of the BTS XMIs 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 XMI.
2100 MHz Channels Figure C-1 shows the total channels for the 2100 MHz frequency spectrum and the channels allocated to CDMA. There are 10 CDMA channels used in a CDMA system. The channels used are unique to each customer system.
C-2
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Figure C-1
Calculating 2100 MHz Channel Center Frequencies
2100 MHz Frequency Spectrum (CDMA Allocation) FREQ (MHz) RX TX
CHANNEL 1
125
1926.25
2116.25
1978.75
2168.75
C D M A
1175 1199
CDMA2100MHZ-1 ti-cdma-00115.eps
Calculating 2100 MHz Channel Center Frequencies Table C-1 shows the valid 2100 MHz CDMA channels, listed in both decimal and hexadecimal, and the corresponding transmit and receive frequencies for each. Center frequencies (in MHz) for channels not shown in the table may be calculated as follows: •
Actual frequencies used depend on customer CDMA system frequency plan.
68P09309A80-2 OCT 2010
C-3
FOA
Calculating 2100 MHz Channel Center Frequencies
Appendix C: CDMA Operating Frequency
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 C-1
2100 MHz TX and RX Channel Center Frequencies Channel Number
Transmit Center Frequency (MHz)
Receive Center Frequency (MHz)
Decimal
Hex
125
007D
2116.25
1926.25
150
0096
2117.50
1927.50
175
00AF
2118.75
1928.75
200
00C8
2120.00
1930.00
225
00E1
2121.25
1931.25
250
00FA
2122.50
1932.50
275
0113
2123.75
1933.75
300
012C
2125.00
1935.00
325
0145
2126.25
1936.25
350
015E
2127.50
1937.50
375
0177
2128.75
1938.75
400
0190
2130.00
1940.00
425
01A9
2131.25
1941.25
450
01C2
2132.50
1942.50
475
01DB
2133.75
1943.75
500
01F4
2135.00
1945.00
525
020D
2136.25
1946.25
550
0226
2137.50
1947.50
575
023F
2138.75
1948.75
600
0258
2140.00
1950.00
625
0271
2141.25
1951.25
650
028A
2142.50
1952.50
675
02A3
2143.75
1953.75
700
02BC
2145.00
1955.00
725
02D5
2146.25
1956.25
750
02EE
2147.50
1957.50
775
0307
2148.75
1958.75
800
0320
2150.00
1960.00
C-4
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Table C-1
Calculating 2100 MHz Channel Center Frequencies
2100 MHz TX and RX Channel Center Frequencies (Continued) Channel Number
Receive Center Frequency (MHz)
Decimal
Hex
825
0339
2151.25
1961.25
850
0352
2152.50
1962.50
875
036B
2153.75
1963.75
900
0384
2155.00
1965.00
925
039D
2156.25
1966.25
950
03B6
2157.50
1967.50
975
03CF
2158.75
1968.75
1000
03E8
2160.00
1970.00
1025
0401
2161.25
1971.25
1050
041A
2162.50
1972.50
1075
0433
2163.75
1973.75
1100
044C
2165.00
1975.00
1125
0465
2166.25
1976.25
1150
047E
2167.50
1977.50
1175
0497
2168.75
1978.75
68P09309A80-2 OCT 2010
Transmit Center Frequency (MHz)
C-5
FOA
C-6
68P09309A80-2
FOA
OCT 2010
Appendix
D
Test Equipment Preparation
68P09309A80-2 OCT 2010
D-1
FOA
Test Equipment Preparation
Appendix D: Test Equipment Preparation
Test Equipment Preparation ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Purpose Test equipment preparation information includes verification and setting GPIB addresses, inter–unit cabling, and equipment calibration for items which are not calibrated with the LMF Calibrate Test Equipment function. This portion of the publication is organized according to the following for the listed CDMA test equipment supported by the LMF.
Test equipment set-up •
Agilent E7495A/B test equipment set-up
Verify and set GPIB address •
Advantest R3267 spectrum 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
Test equipment interconnection •
Advantest R3267 spectrum analyzer and Advantest R3562 signal generator
•
Agilent 8935 analyzer (formerly HP 8935) and Agilent E4438C signal generator
•
Agilent E4406A transmitter test set and Agilent E4438C signal generator
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 and E7495B with the LMF The Agilent E7495 does not require the use of the 19 MHz 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 –80 dB. In order to achieve accurate FER testing, be sure the RX set–up includes at least 40 dB 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 the following procedure.
Procedure D-1
Set IP Address on Agilent E7495 test set
1
Use the System Button > Controls > IPAdmin to set the IP address on the E7495A/B as 128.0.0.11, and Netmask as 255.255.255.128.
2
If the IP address was changed, reboot the E7495.
3
For compatibility, change the LMF computer Network Interface Card (NIC) IP address to 128.0.0.48, subnetmask 255.255.255.128.
Connection Connect the E7495 test set as described in the Test Equpment Connection to the LMF section of Chapter Appendix G Optimization and Calibration Procedures.
Power Sensor Calibration Perform the following procedure to perform E7495 power sensor calibration.
Procedure D-2
E7495 Power Sensor Calibration
1
Display the power meter screen.
2
Make sure equipment is connected as shown in Figure D-1.
D-4
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure D-2 3
Power Sensor Calibration
E7495 Power Sensor Calibration (Continued)
Zero the power meter by doing the following:
4
1.
Press the Zero softkey.
2.
Press the Continue softkey.
Calibrate the power meter by doing the following:
Figure D-1
1.
Press Ref CF.
2.
Enter the reference cal factor, reading it off the label on the power sensor head.
3.
Press Calibrate.
4.
Connect the power sensor (see Figure D-2).
5.
Press Continue.
6.
Press Cal Factor.
7.
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.
Agilent E7495 Power Sensor Calibration connection POWER SENSOR CONNECTED GPIO
Port 2 RF In
Power REF 50 MHz
Ext Ref In
Even Second Sync In
Serial 1 Sensor
Serial 2
Use only Agilent supplied power adapter
Port 1 RF Out / SWR
GPS Antenna
A1-E7495_Power_Sen se_Cal-2.eps
68P09309A80-2 OCT 2010
D-5
FOA
Cable Calibration
Appendix D: Test Equipment Preparation
Cable Calibration Follow the directions in the LMF application program to calibrate cables.
Additional cable calibration details – Calibrate the short cable (see Figure G-15) and two 10 dB attenuators to establish a baseline and then calibrate the TX and RX set-ups. Because at least 40 dB of attenuation is needed when testing the FER, the set-up for RX is the same as for TX.
D-6
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Verifying and Setting GPIB Addresses: Advantest R3267 Spectrum Analyzer
Verifying and Setting GPIB Addresses: Advantest R3267 Spectrum Analyzer ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Figure D-3
Setting Advantest R3267 GPIB Address SOFTKEY LABLE DISPLAY AREA
SOFTKEY BUTTONS
on
REMOTE LED LCL KEY
CONFIG KEY
KEYPAD
BS KEY
ENTR KEY A1-R3267_GPIB.eps
Refer to Figure D-3 when performing the following.
Procedure D-3 1
Verify and Set/Change Advantest R3267 GPIB Address
If the REMOTE LED is lighted, press the LCL key. Result: The LED extinguishes.
2
Press the CONFIG key. Result: •
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.
68P09309A80-2 OCT 2010
D-7
FOA
Verifying and Setting GPIB Addresses: Advantest R3267 Spectrum Analyzer
Procedure D-3 3
Appendix D: Test Equipment Preparation
Verify and Set/Change Advantest R3267 GPIB Address (Continued)
If the current GPIB address is not set to 18, perform the following to change it: 1.
Press the GPIB Address softkey.
Result: 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.
NOTE To correct an entry, press the BS (backspace) key at the lower right of the keypad to delete one character at a time. Result: Characters typed on the keypad will replace the address displayed in the GPIB Address entry window. 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.
D-8
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Verifying and Setting GPIB Addresses: Advantest R3562 Signal Generator
Verifying and Setting GPIB Addresses: Advantest R3562 Signal Generator ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Set the GP–IB ADDRESS switch on the rear of the Advantest R3562 signal generator to address 1 as shown in Figure D-4.
Figure D-4
Advantest R3562 GPIB Address Switch Setting
GPIB Address set to “1”
GP–IP ADDRESS 5 4 3 2 1 1
2
3
4
5
6
7
8
1 0
A1-R3562_GPIB.eps
68P09309A80-2 OCT 2010
D-9
FOA
Verifying and Setting GPIB Addresses: Agilent 8935 Series E6380 Test Set
Appendix D: Test Equipment Preparation
Verifying and Setting GPIB Addresses: Agilent 8935 Series E6380 Test Set ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Figure D-5
Agilent 8935 Series E6380 Test Set Verify and Set/Change GPIB Address
Preset
Local
Inst Config
Shift
Cursor Control
A1-8935_GPIB.eps
NOTE This procedure assumes that the test equipment is set up and ready for testing. Refer to Figure D-5 when performing the following.
Procedure D-4 Address
Verify and Set/Change Agilent 8935 Series E6380 Test Set GPIB
1
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 manufacturer's documentation for additional information as required.) To verify that the GPIB addresses are set correctly, press Shift and LOCAL on the 8935. Result: The current HP-IB address is displayed at the top of the screen.
D-10
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Verifying and Setting GPIB Addresses: Agilent 8935 Series E6380 Test Set
Procedure D-4 Verify and Set/Change Agilent 8935 Series E6380 Test Set GPIB Address (Continued)
NOTE HP-IB is the same as GPIB. 2
3
If the current GPIB address is not set to 18, perform the following to change it: 1.
Press Shift and Inst Config.
2.
Turn the Cursor Control knob to move the cursor to the HP-IB Adrs field.
3.
Press the Cursor Control knob to select the field.
4.
Turn the Cursor Control knob as required to change the address to 18.
5.
Press the Cursor Control knob to set the address.
Press Preset to return to normal operation.
68P09309A80-2 OCT 2010
D-11
FOA
Verifying and Setting GPIB Addresses: Agilent E4406A Transmitter Tester
Appendix D: Test Equipment Preparation
Verifying and Setting GPIB Addresses: Agilent E4406A Transmitter Tester ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Figure D-6
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
A1-E4406A_GPIB.eps
Refer to Figure D-6 when performing the following.
Procedure D-5 Address 1
Verify and Set/Change Agilent E4406A Transmitter Tester GPIB
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.
D-12
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Verifying and Setting GPIB Addresses: Agilent E4406A Transmitter Tester
If the current GPIB address is not set to 18, perform the following to change it: 1.
Press the GPIB Address softkey button.
Result: In the on-screen 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.
NOTE To correct an entry, press the Bk Sp key at the upper right of the keypad to delete one character at a time. Result: The GPIB Address label will change to Enter. Digits entered with the keypad will replace the current GPIB address in the display. 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.
68P09309A80-2 OCT 2010
D-13
FOA
Verifying and Setting GPIB Addresses - Agilent E4418 Power Meter
Appendix D: Test Equipment Preparation
Verifying and Setting GPIB Addresses - Agilent E4418 Power Meter ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Figure D-7
Agilent E4418B Power Meter Verify and Set/Change GPIB Address ARROW KEYS
PRESET/ LOCAL
STATUS REPORTING LINE
SYSTEM/ INPUTS
Procedure D-6
SOFTKEY LABEL AREA
SOFTKEY MENU TITLE
LEFT
DOWN
UP
SOFTKEY MENU PAGE NUMBER
RIGHT
A1-E4418_GPIB.eps
Verify and Set/Change Agilent E4418 Power Meter GPIB Address
Refer to Figure D-7 when performing the following. 1
If RMT (remote operation) is displayed on the left end of the instrument screen status reporting line, press the Preset/Local front panel button. Result: The status line entry will change to LCL (local or front panel operation).
2
On the instrument front panel, press the System/Inputs key. Result: The softkey labels displayed on the right side of the instrument screen will change.
3
Press the Remote Interface > Configure Interface > GPIB softkeys to the right of the instrument screen. Result: 1.
The softkey labels will change.
2.
The current instrument GPIB address will be displayed below the GP-IB Addr softkey label.
D-14
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure D-6 (Continued)
Verifying and Setting GPIB Addresses - Agilent E4418 Power Meter
Verify and Set/Change Agilent E4418 Power Meter GPIB Address
4
If the current GPIB address is set to 13, skip to step 8
5
If the current GPIB address is not set to 13, press the GP-IB Addr softkey. Result: A pop-up window will appear and display the current GPIB address.
6
Modify the GPIB address in the pop-up as necessary using the following front panel keys to perform the indicated functions: Result: 1.
Up and down arrow keys to change the digit on which the cursor is currently located
2.
Left and right arrow keys to move the cursor to other digits
7
When the GPIB address is correct, press the Enter softkey.
8
Return the instrument to the required setup configuration for testing.
68P09309A80-2 OCT 2010
D-15
FOA
Verifying and Setting GPIB Addresses: Agilent E4438C Signal Generator
Appendix D: Test Equipment Preparation
Verifying and Setting GPIB Addresses: Agilent E4438C Signal Generator ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Figure D-8
Agilent E4438C Verify and Set/Change GPIB Address
Active Entry Area
Softkey Label Display Area
Return Key
Utility Key
Softkey Buttons
Numeric Keypad
Backspace Key
A1-E4438C_GPIB.eps
Refer to Figure F-9 when performing the following.
Procedure D-7
1
Verify and Change Agilent E4438C Signal Generator GPIB Address
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.
2
Press the GPIB/RS232 LAN softkey button to the right of the instrument screen. Result:
3
•
The softkey labels will change.
•
The current instrument GPIB address will be displayed below the GPIB Address softkey label.
If the current GPIB address is set to 1, skip to step 7.
D-16
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure D-7 (Continued) 4
Verifying and Setting GPIB Addresses: Agilent E4438C Signal Generator
Verify and Change Agilent E4438C Signal Generator GPIB Address
If the current GPIB address is not set to 1, press the GPIB Address softkey button. Result:
5
•
The GPIB Address label and current GPIB address will change to boldface.
•
In the on-screen Active Entry Area, Address: will be displayed followed by the current GPIB address.
On the front panel Numeric keypad, enter the signal generator GPIB address of 1. Result: •
The GPIB Address label will change to Enter.
•
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
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.
7
Exit from the Utility menus by pressing the Return key several times.
68P09309A80-2 OCT 2010
D-17
FOA
Verifying and Setting GPIB Addresses: Gigatronics 8541C Power Meter
Appendix D: Test Equipment Preparation
Verifying and Setting GPIB Addresses: Gigatronics 8541C Power Meter ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Figure D-9
Gigatronics 8541C Power Meter 1
MENU
ENTER
ARROW KEYS
A1-G8541_GPIB.eps
Refer to Figure D-9 when performing the following.
NOTE This procedure assumes that the test equipment is set up and ready for testing.
Procedure D-8
Verify and Set/Change Gigatronics 8541C Power Meter GPIB Address
1
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
Use the “down” arrow key to select CONFIG MENU and press ENTER.
3
Use the “down” arrow key to select GPIB and press ENTER.The current Mode and GPIB Address are displayed.
D-18
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure D-8 (Continued) 4
5
6
Verifying and Setting GPIB Addresses: Gigatronics 8541C Power Meter
Verify and Set/Change Gigatronics 8541C Power Meter GPIB Address
If the Mode is not set to 8541C, perform the following to change it: 1.
Use the “left” and “right” arrow keys as required to select MODE.
2.
Use the “down” and “up” arrow keys as required to set MODE to 8541C.
If the GPIB address is not set to 13, perform the following to change it: 1.
Use the “right” arrow key to select ADDRESS.
2.
Use the “down” and “up” arrow keys as required to set the GPIB address to 13.
Press ENTER to return to normal operation.
68P09309A80-2 OCT 2010
D-19
FOA
Verifying and Setting GPIB Addresses: RS232 GPIB Interface Box
Appendix D: Test Equipment Preparation
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 D-10.
Figure D-10
Verify and Set/Change RS232 GPIB Interface Box GPIB Address
DIP SWITCH SETTINGS
S MODE DATA FORMAT
BAUD RATE
ON
GPIB ADRS
G MODE
RS232–GPIB INTERFACE BOX A1-GPIB_GPIB.eps
D-20
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
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 D-11.
68P09309A80-2 OCT 2010
D-21
FOA
Serial I/O
Appendix D: Test Equipment Preparation
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 D-11.
Figure D-11
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
D-22
R3562 SERIAL I/O
A1-R3267-R3562_Interconnect.eps
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Test Equipment Interconnection: Agilent 8935 Series E6380 and E4438C
Test Equipment Interconnection: Agilent 8935 Series E6380 and E4438C ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
To perform FER testing on a 1X BTS with the Agilent 8935, a 1X-capable 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 D-12
Even second pulse reference Refer to Figure D-12, 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.
68P09309A80-2 OCT 2010
D-23
FOA
Even second pulse reference
Figure D-12
Appendix D: Test Equipment Preparation
Agilent 8935/E4438C 10MHz Reference and Even Second Tick Connections E4438C PATT TRIG IN
E4438C 10 MHz IN
TO GPIB
8935 10 MHz REF OUT
TO CSM BOARD SYNCH MONITOR (EVEN SEC TICK)
8935 EVEN SECOND SYNC IN WITH BNC “T”
OR UBS SSI TREF OUT A1-8935-4438_Interconnect.eps
D-24
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
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 D-13.
Figure D-13
Agilent 10 MHz Reference Connections
E4438C 10 MHz IN TO GPIB BOX
E4406A 10 MHz OUT (SWITCHED)
A1-E4406-E4438_Interconnect.eps
68P09309A80-2 OCT 2010
D-25
FOA
Test Equipment Calibration: Agilent E4406A Self-alignment
Appendix D: Test Equipment Preparation
Test Equipment Calibration: Agilent E4406A Self-alignment ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Refer to Figure D-14 when performing the following.
Figure D-14
Agilent E4406A Softkey Label Display Area
System Key
Softkey Buttons
Procedure D-9 1
A1-E4406_Cal.eps
Agilent E4406A Self-alignment (Calibration)
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.
D-26
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Test Equipment Calibration: Gigatronics 8541C Power Meter
Test Equipment Calibration: Gigatronics 8541C Power Meter ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Precise transmit output power calibration measurements are made using a bolometer-type broadband power meter with a sensitive power sensor. Follow the steps in to enter information unique to the power sensor. Refer to Figure D-15 as necessary.
Procedure D-10
Calibrate Gigatronics 8541C Power Meter
1
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
Connect the power sensor cable to the SENSOR input.
3
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
Connect the power sensor to the CALIBRATOR output connector.
5
Press ZERO, and wait for the process to complete.
NOTE Sensor factory calibration data is read to power meter during this process. 6
When the zeroing process is complete, disconnect the power sensor from the CALIBRATOR output.
68P09309A80-2 OCT 2010
D-27
FOA
Test Equipment Calibration: Gigatronics 8541C Power Meter
Figure D-15 CONNECT POWER SENSOR TO CALIBRATOR POWER REFERENCE WHEN CALIBRATING/ZEROING UNIT
Appendix D: Test Equipment Preparation
Gigatronics 8541C Power Meter CONNECT POWER SENSOR WITH POWER METER TURNED OFF
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, site-specific, operational configuration can be downloaded to the router over the network. This appendix includes sections on: •
Setting up communications with a router using a Microsoft® Windows®-based computer
•
Downloading BTS router canned configuration files from the OMC-R
•
Transferring the canned configuration files from the Windows-based computer to the BTS router
•
Verifying and, if necessary, replacing/upgrading the IOS version loaded on the CF memory card
•
Verifying and, if necessary, replacing/upgrading the ROM monitor low-level operating system version loaded in the BTS router
•
Recovery from BTS router initialization with the ROM monitor low-level operating system and troubleshooting to locate and correct the cause
•
Changing the router FE interface IP addresses if necessary to support FE verification
•
Sample listings of the BTS router canned configuration files
Application Unless otherwise noted, the procedures and information in this appendix apply to MWR 1941-DC model of the external BTS router.
E-2
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Terminal Set-up
Terminal Set-up ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Creating a Terminal Session General - This section provides the procedures to configure and save a terminal session for communicating with the MWR 1941-DC BTS router. Terminal settings are the same as those used for BTS card and module Man-Machine Interface (MMI) communication sessions. The procedures are for a Pentium® processor-based computer operating with either Windows 2000 or Windows XP. or Windows 98 Second Edition (SE). Using the LMF computer - LMF computer platforms can be used for communicating with the routers, and the MMI terminal connection created for BTS card/module optimization actions will operate with the BTS routers. See the “Establishing a BTS Router Communication Session" section of this appendix for additional interface hardware required for BTS router communication.
Terminal Settings Follow the procedure in Procedure E-1 to create a named HyperTerminal connection for BTS router interface and generate a Windows desktop shortcut for it.
NOTE There are differences between Windows 98 SE and Windows XP or 2000 in the menus and screens used for creating a HyperTerminal connection. In the following procedure, items applicable to: •
Windows 98 SE will be identified with Win98
•
Windows XP and 2000will be identified with WinXP or Win2K
Procedure E-1 1
Establish HyperTerminal Connection
From the Windows Start menu, select: Programs > Accessories.
68P09309A80-2 OCT 2010
E-3
FOA
Terminal Settings
Appendix E: BTS Router Initial Configuration
Procedure E-1 2
Establish HyperTerminal Connection (Continued)
Perform one of the following: •
For Win2K or WinXP, select Hyperterminal and then click on HyperTerminal
•
For Win98, select Communications, double click the Hyperterminal folder, and then double click on the Hypertrm.exe icon in the window which opens
NOTE
3
•
If a Location Information Window appears, enter the required information, then click on the Close button. (This is required the first time a HyperTerminal connection is configured, even if a modem is not to be used.)
•
If a You need to install a modem. . . . . message appears, click on NO.
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.
4
From the Connect using: pick list in the Connect To box displayed, select the RS-232 port to be used for the connection (e.g., COM1 or COM2 - Win2000 or WinXP or Direct to Com 1 or Direct to Com 2- Win98), and click OK.
5
In the Port Settings tab of the COM# Properties window displayed, configure the RS-232 port settings as follows: •
Bits per second: 9600
•
Data bits: 8
•
Parity: None
•
Stop bits: 1
•
Flow control: None
6
Click OK.
7
With the HyperTerminal window still open and the connection running, select: File > Properties.
8
Click the Settings tab, click the arrow in the Emulation window, and select VT100 from the drop down list.
9
Click the ASCII Setup button, uncheck all boxes in the ASCII Setup window which appears, and click OK.
10
Highlight the newly-created connection icon by moving the cursor over it (Win2000) or (WinXP).
E-4
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure E-1
Terminal Settings
Establish HyperTerminal Connection (Continued)
11
Right click and drag the highlighted connection icon to the Windows desktop and release the right mouse button.
12
From the popup menu displayed, select Create Shortcut(s) Here.
13
Click OK for the connection Properties box.
14
Save the defined connection by selecting: File > Save.
15
Close the HyperTerminal window by selecting: File > Exit.
16
Click the Yes button to disconnect when prompted.
17
Perform one of the following:
18
•
For Win2000 or WinXP, select Hyperterminal and release any pressed mouse buttons.
•
For Win98, select Communications, and double click the Hyperterminal folder.
If desired, reposition the shortcut icon for the new connection by dragging it to another location on the Windows desktop.
NOTE The shortcut icon can now be double-clicked to open a BTS router or BTS card/module MMI HyperTerminal session without the need to negotiate multiple menu levels.
68P09309A80-2 OCT 2010
E-5
FOA
Establishing a BTS Router Communication Session
Appendix E: BTS Router Initial Configuration
Establishing a BTS Router Communication Session ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
BTS Router Serial Communication For those procedures which require serial communication with BTS routers, follow the procedures in Procedure E-2 to initiate the communication session. This procedure calls out the LMF computer platform, but any VT100-equivalent 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: •
LMF computer platform or equivalent
•
Eight-conductor (four-pair, unshielded twisted pair is acceptable) rollover cable, two 8-contact modular plugs (see Figure E-1 for cable wiring requirements)
•
Adapter, DB-9 plug-to-8-contact modular plug, Global Computer Supplies C4717 or equivalent (see Figure E-2 for adapter wiring requirements)
Figure E-1
Wiring Diagram, BTS Router Communication Rollover Cable
If it has not been done, start the computer and allow it to complete boot-up.
2
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 Procedure E-1 in the “Terminal Set-up" section of this appendix.
3
Connect the computer to the BTS router as shown in Figure E-3.
4
Start the named HyperTerminal connection for BTS router communication sessions by double clicking on its Windows desktop shortcut.
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> 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.
68P09309A80-2 OCT 2010
E-7
FOA
BTS Router Serial Communication
Figure E-3
Appendix E: BTS Router Initial Configuration
LMF Computer Connections to BTS Router
ROLLOVER CABLE
TO BTS ROUTER CONSOLE RECEPTACLE
DB9-TO-RJ48C ADAPTER
LMF COMPUTER OR EQUIVALENT
COM1 OR COM2
ti-cdma-00131.eps
E-8
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Obtain BTS Router Minimum (Canned) Configuration File from the OMC-R
Obtain BTS Router Minimum (Canned) Configuration File from the OMC-R ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Obtaining BTS Router Minimum (Canned) Configuration Files After they are generated on the OMC-R, 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 OMC-R 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 OMC-R, 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 Procedure E-3 must be used rather than those in the NEC file transfer procedure.
2.
If a Windows-based server connection is available in the operator's network and it can provide an FTP or telnet connection to the OMC-R, files may be transferred by either the FTP or telnet methods.
3.
If a dial-up connection is available for accessing the OMC-R, 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-based server in the operator's 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 Procedure E-3: •
User ID and password to log onto the OMC-R
•
Name of the sub-directory where the specific BTS router group canned configuration files to be downloaded were created
FTP File Transfer from the OMC-R This procedure uses the Windows-based LMF computer platform to download BTS router canned configuration files from the OMC-R. Follow the procedure in Procedure E-3.
Procedure E-3
BTS Router Canned Configuration File FTP Transfer from the OMC-R
68P09309A80-2 OCT 2010
E-9
FOA
FTP File Transfer from the OMC-R
Procedure E-3 (Continued)
Appendix E: BTS Router Initial Configuration
BTS Router Canned Configuration File FTP Transfer from the OMC-R
1
If it has not been done, create a directory on the LMF computer where the BTS router canned configuration files will be stored.
2
If it has not been done, obtain the OMC-R logon user ID and password from the local network administrator.
3
Connect the LMF computer to the local network and log on.
4
NOTE This procedure uses the command line FTP client supplied with Windows 2000 and Windows XP; however, any commercially available FTP client application can be used. Follow the manufacturer's instructions for operation of an alternative application. Open a command line (MS-DOS) window by clicking on Start>Programs>Command Prompt. 5
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>
6
Check the contents of the directory by entering the following: dir A response similar to the following will be displayed: C:\Can_Cfg>dir Volume in drive C is MAIN Volume Serial Number is F2AA-1721 Directory of C:\Can_Cfg> 08/22/2002 08/22/2002 08/22/2002 08/22/2002
If either or both of the following files are found in the directory, delete them or move them to another directory: •
btsrtr_canned.blue
•
btsrtr_canned.red
E-10
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure E-3 (Continued) 8
FTP File Transfer from the OMC-R
BTS Router Canned Configuration File FTP Transfer from the OMC-R
Begin the FTP session by entering the following: ftp hostname Where hostname = the OMC-R hostname or IP address A response similar to the following will be displayed: C:\Can_Cfg> ftp OMCR-1 C:\Can_Cfg> Connected to OMCR-1. 220 OMCR-1 FTP server (SunOS 5.6) ready. User (OMCR-1:(none)):
9
Enter the User ID and password when prompted, pressing the Enter key after each. A response similar to the following will be displayed: User (OMCR-1:(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 sub-directories 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 A response similar to the following will be displayed: 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 A response similar to the following will be displayed: 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.02 Seconds 1.50 Kbytes/sec. ftp>
68P09309A80-2 OCT 2010
E-11
FOA
FTP File Transfer from the OMC-R
Procedure E-3 (Continued)
Appendix E: BTS Router Initial Configuration
BTS Router Canned Configuration File FTP Transfer from the OMC-R
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 OMC-R. 12
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 A response similar to the following will be displayed: 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 A response similar to the following will be displayed: ftp> bin 200 Type set to I. ftp> hash Hash mark printing On ftp>
14
ftp: (2048 bytes/hash mark) .
Download the BTS router canned configuration files to the LMF computer by performing the following:
•
Enter the following to download the first canned configuration file:
get btsrtr_canned.blue A response similar to the following will be displayed: 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.59 Seconds 3.76 Kbytes/sec.
E-12
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure E-3 (Continued)
FTP File Transfer from the OMC-R
BTS Router Canned Configuration File FTP Transfer from the OMC-R
ftp> •
Enter the following to download the second BTS router canned configuration file:
get btsrtr_canned.red A response similar to the following will be displayed: 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.59 Seconds 3.76 Kbytes/sec. ftp> 15
Before terminating the FTP session, open Windows Explorer 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: •
Click Start > Programs > Windows Explorer.
•
In the left-hand pane of Windows Explorer, perform one of the following depending on the LMF computer operating system:
Win2K or WinXP: 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.
16
•
Expand any sub-directories as required to display the directory folder where the canned configuration files are to be stored.
•
In the right-hand pane, verify that the files btsrtr_canned.blue and btsrtr_canned.red appear.
•
Click on the directory folder icon where the canned configuration files are to be stored.
•
If the files appear, proceed to step 16.
•
If the files do not appear, repeat step 14 and step 15 .
Close Windows Explorer, and in the command line window, enter the following to terminate the FTP session: bye A response similar to the following will be displayed: ftp> bye
221 Goodbye.
C:\Can_Cfg>
68P09309A80-2 OCT 2010
E-13
FOA
FTP File Transfer from the OMC-R
Procedure E-3 (Continued)
Appendix E: BTS Router Initial Configuration
BTS Router Canned Configuration File FTP Transfer from the OMC-R
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.
E-14
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
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 set-up 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 1900-27 or MWR 1941-DC router will first search the startup-config 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 1941-DC 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 startup-config file contains a boot system line which specifies a missing or incorrect IOS pathname/filename.
68P09309A80-2 OCT 2010
E-15
FOA
Using a TFTP Server to Copy Files to CF Memory Card
Appendix E: BTS Router Initial Configuration
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 canned-config. Canned configuration file location and filename requirements are a result of Mobile Wireless Center (MWC) actions during BTS re-parenting to another OMC-R. In this process, the MWC will query the BTS routers' slot0: directory for a file named canned-config. A missing or mis-named file will cause problems with execution of the mode-switching process.
Installation Method - The startup-config 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 boot-up, the file must be copied into the startup-config file in NVRAM. This requires copying the canned configuration file from the Windows-based LMF computer to the CF memory card installed in a router, and then copying it to the startup-config file in the router's NVRAM. The only Motorola-supported 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: •
Formatting a BTS router CF memory card
•
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.
Using a TFTP Server to Copy Files to CF Memory Card Required Equipment and Software The following items are required to perform this procedure:
E-16
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Using a TFTP Server to Copy Files to CF Memory Card
•
A Windows-based computer which meets the requirements of the LMF computer platform
•
One of the following operating systems for the Windows-based computer:
Windows 2000 or Windows XP Windows 98 Second Edition (SE) using FAT32 file system
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.
•
One of the following for the Windows-based computer: Internal 10/100baseT Network Interface Card (NIC) PCMCIA 10/100baseT NIC
•
Cable, rollover, as described in the Establishing a BTS Router Communication Session section of this Appendix
•
DB-9 plug-to-8-contact modular plug adapter as described in the Establishing a BTS Router Communication Session section of this Appendix
•
Cable, Ethernet crossover, Category 5E or better, unshielded twisted pair, two 8-contact 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)
• •
A +27 Vdc power supply to power the BTS router during configuration file operations 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 •
A copy of the MWR 1941-DC 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)
68P09309A80-2 OCT 2010
E-17
FOA
Using a TFTP Server to Copy Files to CF Memory Card
Appendix E: BTS Router Initial Configuration
Required Materials The following material is required to perform this method: •
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: •
The optimization/ATP manual for the BTS type
•
Cellular System Administration - CDMA OnLine Documentation
•
MWR 1941-DC Wireless Mobile Edge Router Software Configuration Guide; part number 78-13983
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 power-up and initial configuration for Ethernet communication
The following procedures are used to accomplish all of these preparatory actions.
Set LMF computer NIC TCP/IP address and create the default TFTP directory Follow the procedure in Procedure E-4 to set the NIC IP address. •
E-18
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Using a TFTP Server to Copy Files to CF Memory Card
NOTE If the IP address for the LAN connection on an LMF computer is being changed to support tftp downloads to a BTS router, the BTS 10base–2 LAN IP address and subnetmask for the NIC must be restored before the LMF can log into a BTS to perform an optimization or ATP.
Procedure E-4 Determine LMF Computer NIC Speed, Set NIC IP Address, and Create a Default TFTP Directory 1
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 Procedure E-4.
2
Start the computer.
3
Login and allow the computer to boot to the desktop.
4
Depending on the installed operating system, from the Windows Start menu, select one of the following:
5
6
•
Win2000 or WinXP: Settings > Network and Dial-up Connections
•
Win98: Settings > Control Panel and double click Network.
Perform one of the following as applicable for the installed operating system: •
For Win2000 or WinXP, in the list of displayed connections, locate the Local Area Network connection for the NIC to be used for BTS router Ethernet communication.
•
For Win98, in the Configuration tab of the Network dialog box, locate the TCP/IP connection forthe installed NIC.
•
If TCP/IP does not appear in the displayed list of installed network components, refer to the operating system documentation and install TCP/IP.
Perform one of the following as applicable for the installed operating system: •
For Win2000 or WinXP, highlight the connection for the NIC and right click the highlighted connection, and select Properties from the pop-up menu.
•
For Win98:
•
Highlight the TCP/IP NIC connection in the displayed list of installed network components.
•
Click the Properties button.
•
Skip to step 9.
7
For Win2000 or WinXP, 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: listbox, refer to the operating system documentation and install TCP/IP.
8
For Win2000 or WinXP, if the checkbox next to the Internet Protocol (TCP/IP) entry is not checked, click in the box to check it.
68P09309A80-2 OCT 2010
E-19
FOA
Using a TFTP Server to Copy Files to CF Memory Card
Appendix E: BTS Router Initial Configuration
Procedure E-4 Determine LMF Computer NIC Speed, Set NIC IP Address, and Create a Default TFTP Directory (Continued) 9
Perform one of the following: •
Win2000or WinXP: Highlight the Internet Protocol (TCP/IP) entry, and click on the Properties button below the Components checked are used by this connection: listbox.
• 10
Win98: From the tabs displayed in the TCP/IP Properties dialog box which opens, select the IP Address tab if it is not at the front.
In the Internet Protocol (TCP/IP) Properties dialog box which appears (Win2000) or WinXP, perform the following: •
If a black dot is not showing in the radio button circle next to Use the following IP address: (Win2000) or WinXP or Specifiy an IP Address (Win98), click on the radio button.
•
If using an LMF computer, record the IP address and subnet mask used for LMF-BTS communication so they can be re-entered when tftp transfer activities for the BTS router are completed.
•
Enter 100.100.100.1 in the IP address: box.
•
Enter 255.255.255.252 in the Subnet mask: box.
11
Click the OK button for the Internet Protocol (TCP/IP) Properties dialog box (Win2000) or WinXP or the TCP/IP Properties box (Win98).
12
Click the OK button for the Local Area Connection Properties box (Win2000) or WinXP or the Network box (Win98).
13
In Win98, click File > Close to close the Control Panel window.
14
Click Start > Programs > Windows Explorer to open Windows Explorer.
15
If the default tftp directory will be the same directory in which the files downloaded from the OMC-R are stored, proceed to step 23.
16
In the left-hand pane of Windows Explorer, locate the icon for the drive where the default tftp directory is to be created.
17
Highlight the drive icon and click Files > New > Folder.
18
While observing the new folder icon in the right-hand pane, type the name for the folder (for example, tftp_files), and press the Enter key.
19
In Windows Explorer, locate the directory where the canned configuration files downloaded from the OMC-R are stored.
20
In the left-hand pane, highlight the directory where the files are stored.
21
Scroll the left-hand pane until the newly-created default tftp directory is visible.
22
In the right-hand pane, highlight the canned configuration files and drag them to the default tftp directory.
E-20
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Using a TFTP Server to Copy Files to CF Memory Card
Procedure E-4 Determine LMF Computer NIC Speed, Set NIC IP Address, and Create a Default TFTP Directory (Continued) 23
In the left-hand pane, click on the default tftp directory, and verify that the canned configuration files appear in the right-hand pane.
24
Load a copy of the required BTS router IOS version into the default tftp directory using FTP, internet download, or media such as a Zip disk (file size is over 7 MB).
25
Click Files > Close to close Windows 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 manufacturer's instructions.
NOTE 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 Procedure E-4, step 15, or created in Procedure E-4, step 18, above. Connect the LMF computer to the BTS router — Connect the LMF computer to the BTS router by following the procedure in Procedure E-5 and referring to Figure E-4.
68P09309A80-2 OCT 2010
E-21
FOA
Using a TFTP Server to Copy Files to CF Memory Card
Figure E-4
Appendix E: BTS Router Initial Configuration
LMF Computer TFTP Connections to BTS Router FAST ETHERNET PORT FE 0 (SOFTWARE DESIGNATION FA0/0)
Connecting the LMF Computer to the BTS Router for TFTP File Transfer
1
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.
2
Connect the LMF computer to the BTS router as shown in Figure E-4, referring to the list of required equipment in this section as required.
3
If the LMF computer has not been started, turn it on, login, and allow it to boot to the desktop.
E-22
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Using a TFTP Server to Copy Files to CF Memory Card
Procedure E-5 Connecting the LMF Computer to the BTS Router for TFTP File Transfer (Continued) 4
Refer to the procedure in Procedure E-2 of this appendix, and start a HyperTerminal communication session for the BTS router.
5
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 manufacturer's instructions).
BTS router power–up and initial configuration for Ethernet communication – Follow the procedure below to apply power to the router and set an initial configuration for Ethernet communication. •
The required version of the IOS is loaded on the CF memory card
•
The CF memory card is installed in the BTS router
Procedure E-6
BTS Router Power-up and Initial Ethernet Configuration
NOTE 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 MWR1941–DC Wireless Mobile Edge Router Software Configuration Guide; part number 78–13983. 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 BTS FRU manual for instructions to access the CF memory card slot).
2
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 boot-up. 3
If a message similar to the following, is displayed, press the Enter key and proceed to step 5: Press RETURN to get started!
68P09309A80-2 OCT 2010
E-23
FOA
Using a TFTP Server to Copy Files to CF Memory Card
Procedure E-6 4
Appendix E: BTS Router Initial Configuration
BTS Router Power-up and Initial Ethernet Configuration (Continued)
If a message similar to the following, is displayed type no and press the Enter key: Basic management connectivity for system, extended interface on the
setup configures only enough management of the setup will ask you to configure each system
Would you like to enter basic management setup? [yes/no]: A response similar to the following will be displayed:
Would you like to enter basic management setup? [yes/no]: no Cisco Internetwork Operating System Software IOS (tm) 1900 Software (MWR1900-I-M), Version 12.2(20020127:101239 Copyright (c) 1986-2002 by cisco Systems, Inc. Compiled Sun 27-Jan-02 06:08 by walrobin Router> 5
At the Router> user EXEC mode prompt, enter the following to access the privileged EXEC mode: enable A response similar to the following will be displayed: Router>enable Router#
6
At the Router# privileged EXEC mode prompt, enter the following to access the configure submode: configure terminal A response similar to the following will be displayed: 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.
7
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 exec-timeout 0 0 no login line vty 0 4 no login
E-24
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure E-6
Using a TFTP Server to Copy Files to CF Memory Card
BTS Router Power-up and Initial Ethernet Configuration (Continued)
Responses similar to the following will be displayed: Router(config)#hostname BTSRTR1 BTSRTR1(config)#interface fa0/0 BTSRTR1(config-if)#ip address 100.100.100.2 255.255.255.252 BTSRTR1(config-if)#speed 100 BTSRTR1(config-if)#duplex full BTSRTR1(config-if)#no shutdown BTSRTR1(config-if)#line con 0 BTSRTR1(config-line)#exec-timeout 0 0 BTSRTR1(config-line)#no login BTSRTR1(config-line)#line vty 0 4 BTSRTR1(config-line)#no login BTSRTR1(config-line)# 8
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(config-line)# ^z 01:11:27: %SYS-5-CONFIG_I: Configured from console by console BTSRTR1#
NOTE Entering exit twice, pressing Enter key after each entry, will also complete the configuration process and return the router to the privileged EXEC mode. 9
Verify port FE 0 (fa0/0) is configured with the correct IP address by entering the following: show ip interface brief A response similar to the following will be displayed: BTSRTR1#sh ip int br Interface IP Address OK? Method Status Protocol FastEthernet0/0 100.100.100.2 YES manual up up Serial0:0 unassigned YES unset administratively down down FastEthernet0/1 unassigned YES unset administratively down down Serial1:0 unassigned YES unset administratively down down BTSRTR1#
10
The router is now configured for Ethernet communication on FE 0, and the canned configuration file can be transferred by tftp. Proceed to Procedure E-7.
68P09309A80-2 OCT 2010
E-25
FOA
Using a TFTP Server to Copy Files to CF Memory Card
Appendix E: BTS Router Initial Configuration
Verifying IOS Version and Canned Configuration File TFTP Transfer to the BTS Router Prerequisites — The following is required prior to performing this procedure: •
A copy of the required MWR 1900-27 or MWR 1941-DC router IOS version file is installed in the default tftp directory (transfer the file to the LMF computer using FTP, internet download, or media such as a Zip disk; file size is approximately 7-8 MB)
NOTE MWR 1941–DC routers must be loaded with IOS version mwr1900–i–mz.122–8.MC2d.bin or later. This router model will not function properly with earlier IOS versions.
IOS verification and canned configuration file transfer IOS verification and canned configuration file transfer – Follow the procedure in Procedure E-7 to verify the loaded IOS version and transfer the canned configuration files from the LMF computer to the BTS router CF memory card.
NOTE This procedure does not cover all aspects of BTS routeroperation and programming. Before performing thisprocedure, review BTS router initialization, operation, and programming information and procedures in MWR1941–DC Wireless Mobile Edge Router Software Configuration Guide; part number 78–13983. Have this publication available for reference while performing this procedure.
Procedure E-7 Server
Transfer Canned Configuration Files to the BTS Router Using a TFTP
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 manufacturer's directions (refer to the Setting Up the TFTP Server - Procedure in the Cellular System Administration - CDMA OnLine Documentation).
2
If a HyperTerminal communication session with the BTS router is not running, start one following the procedure in Procedure E-2.
E-26
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Using a TFTP Server to Copy Files to CF Memory Card
Procedure E-7 Transfer Canned Configuration Files to the BTS Router Using a TFTP Server (Continued) 3
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#
4
Be sure the Ethernet crossover cable is connected between the LMF computer NIC port and the BTS router FE 0 port (Figure E-4).
5
Begin verification that the CF memory card contains the correct version of the Cisco IOS by entering the following: dir slot0: A response similar to the following will be displayed: BTSRTR1#dir slot0: Directory of slot0:/ 1 -rw- 7051976 Mar 01 1993 00:11:34 31932416 bytes total (24879104 bytes free) BTSRTR1#
mwr1900-i-mz.122-8.MC2a.bin
NOTE
6
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 thedefault setting.
2.
If slot0: is included in the command, be sure to include the colon (:) after slot0 when typing thecommand.
3.
The IOS filename will be similar to the following: mwr1900–i-mz.122–8.MC2a.bin
Direct the router to show the version information by entering the following: show version
A response similar to the following will be displayed: BTSRTR1#sh ver Cisco Internetwork Operating System Software IOS (tm) 1900 Software (MWR1900-I-M), Version 12.2(8)MC2a, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) TAC Support: http://www.cisco.com/tac Copyright (c) 1986-2002 by cisco Systems, Inc. Compiled Mon 05-Aug-02 11:07 by nmasa Image text-base: 0x60008940, data-base: 0x60B54000 ROM: System Bootstrap, Version 12.2(20020113:235343) [sbose-wilma 109], DEVELOPMENT SOFTWARE ROM: 1900 Software (MWR1900-I-M), Version 12.2(8)MC2a, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) Router uptime is 1 minute System returned to ROM by power-on System image file is "slot0:mwr1900-i-mz.122-8.MC2a.bin" cisco mwr1900 (R7000) 68P09309A80-2 OCT 2010
E-27
FOA
Using a TFTP Server to Copy Files to CF Memory Card
Appendix E: BTS Router Initial Configuration
Procedure E-7 Transfer Canned Configuration Files to the BTS Router Using a TFTP Server (Continued) 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 non-volatile configuration memory. 31360K bytes of ATA Slot0 CompactFlash (Read/Write) Configuration register is 0x101 BTSRTR1# 7
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.
NOTE MWR 1941-DC routers must be loaded with IOS version mwr1900-i-mz.122-8.MC2d.bin or later. This router model will not function properly with earlier IOS versions. 8
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 Procedure E-8 to load the required version, and then return to step 9, below.
9
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: •
Backup all files on the CF memory card to the LMF computer default tftp directory by performing step 3 through step 10 of Procedure E-8.
•
Perform steps step 25 through step 29 of Procedure E-8, as applicable.
E-28
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Using a TFTP Server to Copy Files to CF Memory Card
Procedure E-7 Transfer Canned Configuration Files to the BTS Router Using a TFTP Server (Continued)
•
Type the following to delete a possible boot system line in the startup-config file, pressing the Enter key after the command and at each prompt to confirm the filename and deletion operation:
del nvram:startup-config A response similar to the following will be displayed: BTSRTR1#del nvram:startup-config Delete filename [startup-config]? Delete nvram:startup-config? [confirm] [OK] BTSRTR1#
NOTE Be sure to include the colon (:) after nvram when typing the command.
•
Verify the startup-config file size has been reduced to a minimum by entering the following:
dir nvram: A response similar to the following will be displayed: Router#dir nvram: Directory of nvram:/ 53 -rw5 54 ---5 57336 bytes total (57274 bytes free) BTSRTR1# 10
startup-config private-config
At the privileged EXEC mode prompt, enter the following: copy tftp:btsrtr_canned.color slot0:canned-config Where color = blue or red, as applicable. A response similar to the following will be displayed: BTSRTR1#copy tftp:btsrtr_canned.blue slot0:canned-config 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 A response similar to the following will be displayed: BTSRTR1#copy tftp:btsrtr_canned.blue slot0:canned-config Address or name of remote host []? 100.100.100.1 Destination filename [canned-config]?
68P09309A80-2 OCT 2010
E-29
FOA
Using a TFTP Server to Copy Files to CF Memory Card
Appendix E: BTS Router Initial Configuration
Procedure E-7 Transfer Canned Configuration Files to the BTS Router Using a TFTP Server (Continued) 12
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:canned-config Address or name of remote host []? 100.100.100.1 Destination filename [canned-config]? 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 A response similar to the following will be displayed: Directory of slot0:/ 1 -rw- 7051976 Mar 01 1993 00:11:34 mwr1900-i-mz.122-8.MC2a.bin 2 -rw2457 Mar 01 1993 00:14:48 canned-config 31932416 bytes total (24877983 bytes free) BTSRTR1#
14
To allow the BTS router to boot using the canned configuration, enter the following: copy canned-config start up-config A response similar to the following will be displayed: BTSRTR1#copy canned-config start Destination filename [startup-config]?
15
When prompted for the destination file name, press the Enter key. A response similar to the following will be displayed: BTSRTR1#copy canned-config start Destination filename [startup-config]? 2457 bytes copied in 3.52 secs BTSRTR1#
16
Display and note the file size of startup-config by entering the following: dir nvram: A response similar to the following will be displayed: Directory of nvram:/ 26 -rw2457 27 ---5
startup-config private-config
29688 bytes total (24774 bytes free) BTSRTR1# 17
Scroll the HyperTerminal window back to the slot0: directory display obtained in step 13, above.
18
Compare the file size of startup-config to the canned configuration file to verify the copy operation. File sizes should be the same.
E-30
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Using a TFTP Server to Copy Files to CF Memory Card
Procedure E-7 Transfer Canned Configuration Files to the BTS Router Using a TFTP Server (Continued) 19
If desired, the contents of the startup-config 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 startup-config
NOTE Pressing the space bar at the MORE prompt will scroll another screen–full 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 startup-config files by entering the following: reload A response similar to the following will be displayed: BTSRTR1#reload System configuration has been modified. Save? [yes/no]: n Proceed with reload? [confirm]
68P09309A80-2 OCT 2010
E-31
FOA
Using a TFTP Server to Copy Files to CF Memory Card
Appendix E: BTS Router Initial Configuration
Procedure E-7 Transfer Canned Configuration Files to the BTS Router Using a TFTP Server (Continued) 21
If prompted to save a modified configuration, enter n for no, and press the Enter key.
22
When prompted to proceed with reload, press the Enter key to continue the reload operation.
23
NOTE Reloading the router with the revised startup-config 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 RouterBoot to rommon section of this appendix. 24
Using the tagging materials, tag the router to clearly identify the installed configuration (blue (BTSRTR1) or red (BTSRTR2)).
25
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 BTS FRU manual, 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 BTS FRU manual.
26
If an additional router must have the canned configuration installed, perform the following: •
Disconnect the cabling from the BTS router.
•
Remove power from the router and disconnect it from the power supply.
•
Repeat the procedures in Procedure E-5, Procedure E-6, and this table (Procedure E-7) using the additional router.
27
If no additional routers must be configured, perform step 26.
28
On the LMF computer, shut down the tftp server application and exit the HyperTerminal session.
29
If no additional tftp transfer activities will be performed, change the NIC IP address and subnet mask back to those for LMF-BTS communication recorded in Procedure E-4, step 10.
CAUTION If the BTS 10base–2 LAN IP address and subnet mask for the LMF computer’s NIC are not restored, the LMF cannot log into a BTS when attempting to perform a BTS optimization or ATP.
E-32
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Change or Upgrade BTS Router IOS Version
Change or Upgrade BTS Router IOS Version ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Background BTS routers are supplied with CF memory cards pre-loaded 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: •
A Windows-based computer which meets the requirements of the LMF computer platform
•
One of the following operating systems for the Windows-based computer:
Windows 2000 or Windows XP Windows 98 Second Edition (SE) and FAT32 file system.
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 operateproperly, resulting in a complete site outage.
•
Cable, rollover, as described in the Establishing a BTS Router Communication Session section of this Appendix
•
DB-9 plug-to-8-contact modular plug adapter as described in the Establishing a BTS Router Communication Session section of this Appendix
•
Cable, Ethernet crossover, Category 5E or better, unshielded twisted pair, two 8-contact 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)
68P09309A80-2 OCT 2010
E-33
FOA
Required Publications
• •
Appendix E: BTS Router Initial Configuration
A +27 Vdc power supply to power the BTS router during configuration file operations 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 •
A copy of the MWR 1900-27 or MWR 1941-DC 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.
NOTE MWR 1941–DC routers must be loaded with IOS version mwr1900–i–mz.122–8.MC2d.bin or later. This router model will not function properly with earlier IOS versions.
Required Publications The following publication is required to perform procedures in this section: •
MWR 1941-DC Wireless Mobile Edge Router Software Configuration Guide; part number 78-13983
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
E-34
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Upgrade/Replace Installed IOS Version and Verify File Sequence Position
Prerequisites - The following are required prior to performing this procedure: •
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 Procedure E-4, Procedure E-5, Procedure E-6, and steps step 1 through step 8 of Procedure E-7
•
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 Procedure E-8 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.
Procedure E-8 Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position
NOTE 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 MWR1941–DC Wireless Mobile Edge Router Software Configuration Guide; part number 78–13983. 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 Procedure E-4, Procedure E-5, Procedure E-6, and steps step 1 through step 8 of Procedure E-7. If necessary, perform these procedures now.
2
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 A response similar to the following will be displayed: BTSRTR1#dir Directory of slot0:/ 1 –rw– 7051844
Sep 23 2002 07:15:08
68P09309A80-2 OCT 2010
mwr1900–i–mz.07022002.bin
E-35
FOA
Upgrade/Replace Installed IOS Version and Verify File Sequence Position
Appendix E: BTS Router Initial Configuration
Procedure E-8 Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position (Continued) 2
–rw–
2212
Mar 01 1993 00:11:00
canned–config
31932416 bytes total (24878360 bytes free) BTSRTR1# 3
Begin to backup the currently installed version of the router's IOS to the LMF computer's 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 mwr1900-i-mz.07022002.bin tftp: Address or name of remote host []?
4
At the remote host prompt, enter the following: 100.100.100.1 A response similar to the following will be displayed: Address or name of remote host []? 100.100.100.1 Destination filename [mwr1900-i-mz.07022002.bin]?
5
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 [mwr1900-i-mz.07022002.bin]? !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
E-36
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Upgrade/Replace Installed IOS Version and Verify File Sequence Position
Procedure E-8 Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position (Continued) !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 7051844 bytes copied in 109.92 secs (64697 bytes/sec) BTSRTR1# 6
If additional files are stored on the CF memory card, begin backing them up to the LMF computer's 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 canned-config tftp: Address or name of remote host [100.100.100.1]?
7
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 [canned-config]?
8
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: Source filename [canned-config]? Destination filename [canned-config]?
9
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 [canned-config]? ! [OK - 2212/4096 bytes] 2212 bytes copied in 0.152 secs BTSRTR1#
10
If more files are stored on the CF memory card, repeat step 6 through step 9 until all files have been backed up to the LMF computer.
11
Delete all files from the CF memory card by entering the following command: format slot0: A response similar to the following will be displayed: BTSRTR1#format slot0: Format operation may take a while. Continue? [confirm]
68P09309A80-2 OCT 2010
E-37
FOA
Upgrade/Replace Installed IOS Version and Verify File Sequence Position
Appendix E: BTS Router Initial Configuration
Procedure E-8 Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position (Continued) 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
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 BTSRTR1#
14
Verify all files have been deleted from the CF memory card by entering the following: dir A response similar to the following will be displayed: 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:mwr1900-i-mz.122-8.MC2a.bin slot0: Address or name of remote host [100.100.100.1]?
16
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 [mwr1900-i-mz.122-8.MC2a.bin]?
E-38
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Upgrade/Replace Installed IOS Version and Verify File Sequence Position
Procedure E-8 Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position (Continued) 17
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: Source filename [mwr1900-i-mz.122-8.MC2a.bin]? Destination filename [mwr1900-i-mz.122-8.MC2a.bin]?
18
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-i-mz.122-8.MC2a.bin]? Accessing tftp://100.100.100.1/mwr1900-i-mz.122-8.MC2a.bin... Loading mwr1900-i-mz.122-8.MC2a.bin from 100.100.100.1 (via FastEthernet0/0): !!!! Loading mwr1900-i-mz.122-8.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#
68P09309A80-2 OCT 2010
E-39
FOA
Upgrade/Replace Installed IOS Version and Verify File Sequence Position
Appendix E: BTS Router Initial Configuration
Procedure E-8 Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position (Continued) 19
Display the CF memory card directory to verify that the new IOS file is there by entering the following: dir A response similar to the following will be displayed: BTSRTR1#dir Directory of slot0:/ 1 -rw7051976 Sep 23 2002 07:25:36 mwr1900-i-mz.122-8.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:canned-config 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 Enterkey 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 [canned-config]?
22
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: Destination filename [canned-config]? Accessing tftp://100.100.100.1/canned-config... Loading basic_config from 100.100.100.1 (via FastEthernet0/0): ! [OK - 2212/4096 bytes] 2212 bytes copied in 0.152 secs BTSRTR1#
23
After the additional file is copied to the CF memory card, display the CF memory card directory by entering the following: dir A response similar to the following will be displayed: BTSRTR1#dir Directory of slot0:/ 1 -rw7051976 2 -rw2212
Sep 23 2002 07:24:18 Mar 01 1993 00:09:06
E-40
mwr1900-i-mz.122-8.MC2a.bin canned-config
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Upgrade/Replace Installed IOS Version and Verify File Sequence Position
Procedure E-8 Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position (Continued) 24
The IOS file must be the first file listed for the BTS router to boot properly. If it is, proceed to step step 29.
25
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 step 11 through step 13 and display the directory of the CF memory card as described in step 23 to be sure the file is deleted. 26
Copy the file from the LMF computer to the CF memory card again by performing steps step 20 through step 23.
27
If the file is again listed before the IOS file in the CF memory card directory display, format the CF memory card by performing through step 11 through step 14 of this table.
28
Copy the IOS file and any other required file to the formatted CF memory card by performing steps step 15 through step 24.
29
If additional files are to be transferred to the CF memory card, perform step 20 through step 24 for each one.
30
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 A response similar to the following will be displayed: BTSRTR1#reload System configuration has been modified. Save? [yes/no]: n Proceed with reload? [confirm]
31
If prompted to save a modified configuration, enter n for no, and press the Enter key.
32
When prompted to proceed with reload, press the Enter key to continue the reload operation.
33
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 (MWR1900-I-M), Version 12.2(8)MC2a, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) . . . BTSRTR1#
68P09309A80-2 OCT 2010
E-41
FOA
Upgrade/Replace Installed IOS Version and Verify File Sequence Position
Appendix E: BTS Router Initial Configuration
Procedure E-8 Using a TFTP Server Application for Upgrading/Replacing Loaded IOS Version and Verifying File Sequence Position (Continued) 34
Verify the version number displayed in the second line of the version information is the correct IOS version.
35
If this procedure was entered from step 8 of Procedure E-7, return to Procedure E-7, step 9.
36
If no other BTS router file operations or configuration actions are required, perform the following:
37
•
Remove power from the router and disconnect it from the power supply.
•
Disconnect all other cabling from the BTS router.
•
On the LMF computer, exit the HyperTerminal communications session.
If no additional tftp transfer activities will be performed, change the NIC IP address and subnet mask back to those for LMF-BTS communication recorded in Procedure E-4, step 10.
CAUTION If the BTS 10base–2 LAN IP address and subnet mask for the LMF computer’s NIC are not restored, the LMF can not log into a BTS when attempting to perform a BTS optimization or ATP.
E-42
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Verify and Upgrade ROMmon Version
Verify and Upgrade ROMmon Version ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction BTS routers are supplied pre-loaded with a version of the ROM monitor (ROMmon) low-level 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 router's CF memory card.
Required Equipment and Software The following items are required to perform ROMmon version verification and upgrade for both verification/upgrade methods: •
A Windows-based computer which meets the requirements of the LMF computer platform
•
One of the following operating systems for the Windows-based computer:
Windows 2000 or WinXP
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 operateproperly, resulting in a complete site outage.
•
Cable, rollover, as described in the Establishing a BTS Router Communication Session section of this Appendix
•
DB-9 plug-to-8-contact modular plug adapter as described in the Establishing a BTS Router Communication Session section of this Appendix
•
Cable, Ethernet crossover, Category 5E or better, unshielded twisted pair, two 8-contact 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)
68P09309A80-2 OCT 2010
E-43
FOA
Required Publications
• •
Appendix E: BTS Router Initial Configuration
A +27 Vdc power supply to power the BTS router during configuration file operations 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 •
A copy of the MWR 1941-DC router ROMmon 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 ROMmon version.
Required Publications The following publication is required to perform procedures in this section: •
MWR 1941-DC Wireless Mobile Edge Router Software Configuration Guide; part number 78-13983
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: •
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 Procedure E-4, Procedure E-5, Procedure E-6, and step 1 through step 8 of Procedure E-7
•
A copy of the required ROMmon version is loaded into the tftp default directory of the LMF computer
E-44
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Verification and Upgrade/Replacement of Installed ROMmon Version
Verifying and Upgrading/replacing installed ROMmon version - Follow the procedure in Procedure E-9 to verify and, if necessary, replace or upgrade the installed ROMmon version using the tftp server application.
Procedure E-9 Server
Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP
NOTE 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 1941–DC Wireless Mobile Edge Router Software Configuration Guide; part number 78–13983. 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 Procedure E-4, Procedure E-5, Procedure E-6, and step 1 through step 8 of Procedure E-7. If necessary, perform these procedures now.
2
Determine the currently installed ROMmon version by entering the following at the router privileged EXEC mode prompt: show version A response similar to the following will be displayed: BTSRTR1#sh ver Cisco Internetwork Operating System Software IOS (tm) 1900 Software (MWR1900-I-M), Version 12.2(8)MC2b, EARLY DEPLOYMENT RELEASE SOFTWARE (fc3) TAC Support: http://www.cisco.com/tac Copyright (c) 1986-2002 by cisco Systems, Inc. Compiled Mon 05-Aug-02 11:07 by nmasa Image text-base: 0x60008940, data-base: 0x60B54000 ROM: System Bootstrap, Version 12.2(20020113:235343) [sbose-wilma 109], DEVELOPMENT SOFTWARE ROM: 1900 Software (MWR1900-I-M), Version 12.2(8)MC2b, EARLY DEPLOYMENT RELEASE SOFTWARE (fc3) Router uptime is 1 minute System returned to ROM by power-on System image file is "slot0:mwr1900-i-mz.122-8.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)
68P09309A80-2 OCT 2010
E-45
FOA
Verification and Upgrade/Replacement of Installed ROMmon Version
Appendix E: BTS Router Initial Configuration
Procedure E-9 Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server (Continued) DRAM configuration is 64 bits wide with parity disabled. 55K bytes of non-volatile configuration memory. 31360K bytes of ATA Slot0 CompactFlash (Read/Write) Configuration register is 0x101 BTSRTR1# 3
To determine the currently installed ROMmon version, examine the ROM: System Bootstrap line in the response.
4
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.122–8r.MC3.bin
2.
The ROMmon filename reflects the version number of the software (122–8r.MC3)
5
If the installed version is the one required for the network skip to step 26.
6
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:start up-config tftp A response similar to the following will be displayed: 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 A response similar to the following will be displayed: BTSRTR1#copy copy nvram:start tftp Address or name of remote host []? 100.100.100.1 Source filename [startup-config]?
8
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: Source filename [startup-config]? Destination filename [startup-config]?
E-46
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Verification and Upgrade/Replacement of Installed ROMmon Version
Procedure E-9 Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server (Continued) 9
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 [startup-config]? ! [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 A response similar to the following will be displayed: BTSRTR#dir Directory of slot0:/ 1 —rw- 7051976 Sep 23 2002 07:24:18 mwr1900–i-mz.122–8.MC2b.bin 2 —rw- 2212 Mar 01 1993 00:14:48 canned-config 31932416 bytes total (24885606 bytes free) Router# 11
Be sure there is at least 1 MB (1048580) of free memory.
NOTE A ROMmon version file requires approximately 0.7 MB. 12
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.122-8r.MC3.bin slot0: Address or name of remote host [100.100.100.1]?
68P09309A80-2 OCT 2010
E-47
FOA
Verification and Upgrade/Replacement of Installed ROMmon Version
Appendix E: BTS Router Initial Configuration
Procedure E-9 Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server (Continued) 13
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 [MWR1900_RM2.srec.122-8r.MC3.bin]
14
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: Source filename [MWR1900_RM2.srec.122-8r.MC3.bin] Destination filename [MWR1900_RM2.srec.122-8r.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.122-8r.MC3.bin]? Accessing tftp://100.100.100.1/MWR1900_RM2.srec.122-8r.MC3.bin... Loading MWR1900_RM2.srec.122-8r.MC3.bin from 100.100.100.1 (via FastEthernet0/0): !!!! Loading MWR1900_RM2.srec.122-8r.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#
16
Display the CF memory card directory to verify that the new ROMmon version file is there by entering the following: dir A response similar to the following will be displayed: BTSRTR1#dir Directory of slot0:/ 1 -rw7051976 Sep 23 2002 07:25:36 mwr1900-i-mz.122-8.MC2b.bin 2 -rw2212 Mar 01 1993 00:09:06 canned-config 3 -rw614306 Dec 13 2002 14:59:36 MWR1900_RM2.srec.122-8r.MC3.bin 31932416 bytes total (24263922 bytes free) BTSRTR1#
E-48
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Verification and Upgrade/Replacement of Installed ROMmon Version
Procedure E-9 Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server (Continued) 17
Replace the existing ROMmon version with the new one copied to the CF memory card by entering the following: upgrade rom-monitor file slot0:MWR1900_RM2.srec.122-8r.MC3 A response similar to the following will be displayed: 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 eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee 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 A response similar to the following will be displayed: BTSRTR1>enable BTSRTR1#
20
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 (MWR1900-I-M), Version 12.2(8)MC2b, EARLY DEPLOYMENT RELEASE SOFTWARE (fc3) TAC Support: http://www.cisco.com/tac Copyright (c) 1986-2002 by cisco Systems, Inc. Compiled Mon 05-Aug-02 11:07 by nmasa Image text-base: 0x60008940, data-base: 0x60B54000 ROM: System Bootstrap, Version 12.2(8r)MC3 RELEASE SOFTWARE (fc1)
21
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.
68P09309A80-2 OCT 2010
E-49
FOA
Verification and Upgrade/Replacement of Installed ROMmon Version
Appendix E: BTS Router Initial Configuration
Procedure E-9 Verify and Upgrade/Replace Installed ROMmon Version Using a TFTP Server (Continued) 22
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 step 12 through step 15, above. A response similar to the following will be displayed:
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: Delete filename [MWR1900_RM2.srec.122-8r.MC3.bin]? Delete slot0:MWR1900_RM2.srec.122-8r.MC3.bin? [confirm]
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.122-8r.MC3.bin]? Delete slot0:MWR1900_RM2.srec.122-8r.MC3.bin? [confirm] BTSRTR1#
25
CAUTION In this step, do not delete the IOS and canned-config files from the CF memory card. The BTS router must have these files on the card to properly boot in packet mode. If additional unnecessary files, such as a backup of the startup-config file, are also on the CF memory card, delete them by repeating step 22 through step 24 for each file. 26
27
If no other BTS router file operations or configuration actions are required, perform the following: •
Remove power from the router and disconnect it from the power supply.
•
Disconnect all cabling from the BTS router.
•
On the LMF computer, exit the HyperTerminal communications session.
If no additional tftp transfer activities will be performed, change the NIC IP address and subnet mask back to those for LMF-BTS communication recorded in Procedure E-4, step 10.
CAUTION If the BTS 10base-2 LAN IP address and subnet mask for the LMF computer's NIC are not restored, the LMF can not log into a BTS when attempting to perform a BTS optimization or ATP
E-50
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
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: •
The hexadecimal value in the router's configuration register has been changed from the factory default (can change the location from where the router attempts to load code for boot-up).
•
IOS file is missing from the CF memory card
•
IOS file is not the first file on the CF memory card
•
Startup-config file contains an outdated boot system line specifying an IOS file which has been replaced with an updated version
•
Startup-config file contains boot system line with typographical error(s) in the IOS filename
•
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 low-level 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 router's CF memory card.
68P09309A80-2 OCT 2010
E-51
FOA
Simple Recovery from Boot to ROMmon
Appendix E: BTS Router Initial Configuration
Recovery - Follow the procedure in Procedure E-10 to attempt a simple recovery from a BTS router ROMmon initialization.
Procedure E-10
Simple Recovery from BTS Router ROMmon Boot
NOTE 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 1941–DC Wireless Mobile Edge Router Software Configuration Guide; part number 78–13983. 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 Procedure E-2 to establish a HyperTerminal communication session.
2
With the rommon 1 > prompt displayed in the HyperTerminal window, enter the following to determine if the router's configuration register is set to the factory default value: confreg A response similar to the following will be displayed: 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: cisco2-mwr1900 do you wish to change the configuration? y/n [n]:
NOTE
3
•
The configuration register setting is shown in the (Virtual Configuration Register: 0x____) line
•
0x in the Virtual Configuration Register line indicates the numbers following are hexadecimal
If the value shown for the configuration register is 2102, skip to step 6.
E-52
68P09309A80-2
FOA
OCT 2010
1X SC™7224 BTS Optimization/ATP
Procedure E-10 4
Simple Recovery from Boot to ROMmon
Simple Recovery from BTS Router ROMmon Boot (Continued)
If the value shown for the configuration register is not 2102, perform the following: Press the Return key to accept the default of n (for no). Enter the following at the rommon prompt: confreg 0x2102 A response similar to the following will be displayed: rommon 3 > confreg 0x2102 You must reset or power cycle for new config to take effect rommon 4 > 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) [sbose-wilma 109], DEVELOPMENT SOFTWARE Copyright (c) 1994-2002 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 . ...
