User's Manual
Table Of Contents
- Chapter 4: Acceptance Test Procedures
- Automated Acceptance Test Procedure
- Acceptance Tests - Test Set-up
- Abbreviated (All-inclusive) Acceptance Tests
- Individual Acceptance Tests
- TX Spectral Purity Transmit Mask Acceptance Test
- TX Waveform Quality (Rho) Acceptance Test
- TX Pilot Time Offset Acceptance Test
- TX Code Domain Power/Noise Floor Acceptance Test
- RX FER Acceptance Test
- Generating an ATP Report
- Updating Calibration Data Files
- Chapter 5: Prepare to Leave the Site
- Chapter 6: Troubleshooting
- Basic Troubleshooting: Overview
- Troubleshooting: Installation
- Cannot Log into Cell-Site
- Force LAN A Active (LMF Connection at I/O Panel LAN Connector)
- Force LAN A Active (LMF Connection at Service Shelf LAN Connector)
- Set the GLI IP Address
- Cannot Communicate with Power Meter
- Cannot Communicate with Communications System Analyzer
- Cannot Communicate with Signal Generator
- Troubleshooting: Download
- Troubleshooting: Calibration
- Basic Troubleshooting: RF Path Fault Isolation
- Troubleshooting: Transmit ATP
- Troubleshooting: Receive ATP
- Troubleshooting: CSM Checklist
- Troubleshooting: SCCP Backplane
- Troubleshooting: RFDS
- Module Front Panel LED Indicators and Connectors
- Troubleshooting: Span Control Link
- Appendix A: Data Sheets
- Appendix B: PN Offset/I & Q Offset Register Programming Information
- Appendix C: FRU Optimization / ATP Test Matrix
- Appendix D: BBX Gain Set Point vs. BTS Output
- Appendix E: CDMA Operating Frequency Programming Information
- Appendix F: Test Equipment Preparation
- Test Equipment Preparation
- Verifying and Setting GPIB Addresses
- Agilent E4406A Transmitter Tester GPIB Address
- Agilent E4432B Signal Generator GPIB Address
- Advantest R3267 Spectrum Analyzer GPIB Address
- Advantest R3562 Signal Generator GPIB Address
- Agilent 8935 Series E6380 (formerly HP 8935) Test Set GPIB Address
- Hewlett Packard HP 8921A and HP83236A/B GPIB Address
- Advantest R3465 Communications Test Set GPIB Address
- Motorola CyberTest GPIB Address
- HP 437 Power Meter GPIB Address
- Gigatronics 8541C Power Meter GPIB Address
- RS232 GPIB Interface Adapter
- Test Equipment Inter-Unit Connection, Testing, and Control
- Inter-Unit Connection, Testing, and Control Settings
- HP 8921A with PCS Interface Test Equipment Connections
- HP 8921A with PCS Interface System Connectivity Test
- Pretest Set-up for HP 8921A
- Pretest Set-up for Agilent 8935
- Advantest R3465 Connection
- R3465 GPIB Clock Set-up
- Pretest Set-up for Advantest R3465
- Agilent 8932/E4432B Test Equipment Interconnection
- Agilent E4406A/E4432B Test Equipment Interconnection
- Advantest R3267/R3562 Test Equipment Interconnection
- Equipment Calibration
- Manual Cable Calibration
- Appendix G: Downloading ROM Code
- Appendix H: In-Service Calibration
- Appendix I: Packet Backhaul Configuration
- BTS Router Initial Configuration
- Terminal Setup
- Downloading Minimum Canned BTS Router Configuration Files
- Verifying IOS Canned Version of the CF Memory Card
- Replacing Installed BTS Router CF Memory Card IOS Version
- Background
- Equipment and Software Required for Verification Methods
- Required Publications
- Method 1: Replacement of Installed Router CF Card IOS Data
- Method 2: Using a CF Memory Card Reader for Replacement of Installed IOS Version and Changing File Sequence ...
- Change CF Memory Card File Sequence to Place IOS File First on the Card
- Verify and Upgrade ROMMON Version
- Recovery from BTS Router Boot to ROMMON
- Entering or Changing Router FE Interface IP Address
- Preparation for Site Turn-over
- Index
Verifying IOS Canned Version of the CF Memory Card
I-14 1X SC 4812T Lite BTS Optimization/ATP FEB 2005
PRELIMINARY
Overview
This section covers the procedures and commands required to verify that
the IOS Version loaded on BTS Router CF Memory Cards and copy
standard Canned Configuration Files to the BTS 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
BTS 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 the loaded IOS Version are provided in the Change
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 1941 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 BTS Router will default to attempting to boot from the first file in its
Flash Memory.
Flash Memory for the MWR 1941 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 BTS 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 that specifies a
missing or incorrect IOS Pathname/Filename..
I