Nokia Solutions and Networks T5BR1 CDMA Cellular Base Station User Manual IHET5BR1 Part 3 of 3

Nokia Solutions and Networks CDMA Cellular Base Station IHET5BR1 Part 3 of 3

IHET5BR1 User Manual Part 3 of 3

Download: Nokia Solutions and Networks T5BR1 CDMA Cellular Base Station User Manual IHET5BR1  Part 3 of 3
Mirror Download [FCC.gov]Nokia Solutions and Networks T5BR1 CDMA Cellular Base Station User Manual IHET5BR1  Part 3 of 3
Document ID170604
Application IDE7OqQiupt0xohX2WphFsyQ==
Document DescriptionIHET5BR1 User Manual Part 3 of 3
Short Term ConfidentialNo
Permanent ConfidentialNo
SupercedeNo
Document TypeUser Manual
Display FormatAdobe Acrobat PDF - pdf
Filesize67.94kB (849283 bits)
Date Submitted2001-09-20 00:00:00
Date Available2001-09-20 00:00:00
Creation Date2001-09-20 17:17:41
Producing SoftwareAcrobat Distiller 4.0 for Windows
Document Lastmod2001-09-20 17:18:30
Document TitleIHET5BR1 User Manual Part 3 of 3

Prepare to Leave the Site – continued
Table 5-6: Remove LMF
Step
Action
Disconnect the CDMA LMF terminal Ethernet port from the BTS frame.
Disconnect the CDMA LMF terminal serial port, the RS–232–to–GPIB interface box, and the
GPIB cables as required for equipment transport.
Connecting BTS T1/E1 Spans
Before leaving the site, connect any T1 or E1 span connectors removed
previously to allow the LMF to control the BTS. Refer to Table 5-7 and
Figure 3-7.
Table 5-7: Connect T1 or E1 Spans
Step
Action
Re–connect any disconnected span connectors to the Span I/O A and B boards.
If equipped, ensure the CSU is powered on.
Verify span status, ensuring the OMC–R/CBSC can communicate with the BTS.
Before Leaving the site
Be sure all requirements listed in Table 5-8 are completed before leaving
the site.
Table 5-8: Check Before Leaving the Site
Step
Action
All battery circuit breakers (for occupied shelves) are ON (pushed in).
Both heat exchanger circuit breakers on the DC PDA are set to ON (pushed in), and the heat
exchanger blowers are running.
The External Blower Assembly (EBA) power cable is connected, and the EBA is running.
The MAP power switch is set to ON, and the POWER (green) LED is lighted.
The BATT TEST switch on the MAP is set to OFF, and the BATT. TEST (amber) LED is not lighted.
No alarm conditions are being reported to the CBSC with all frame doors closed.
08/01/2001
1X SCt4812ET Lite BTS Optimization/ATP
PRELIMINARY
5-5
Prepare to Leave the Site
– continued
Notes
5-6
1X SCt4812ET Lite BTS Optimization/ATP
08/01/2001
PRELIMINARY
Chapter 6: Basic Troubleshooting
Table of Contents
08/01/2001
Basic Troubleshooting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-1
6-1
Troubleshooting: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cannot Log into Cell-Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cannot Communicate with Power Meter . . . . . . . . . . . . . . . . . . . . . . .
Cannot Communicate with Communications Analyzer . . . . . . . . . . . .
6-2
6-2
6-5
6-6
Troubleshooting: Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cannot Download DATA to Any Device (Card) . . . . . . . . . . . . . . . . . .
Cannot ENABLE Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LPA Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-7
6-7
6-8
6-9
Troubleshooting: Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bay Level Offset Calibration Failure . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calibration Audit Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-10
6-10
6-11
Basic Troubleshooting – RF Path Fault Isolation . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
If Every Test Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verify BLO Checkbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
If Faults Are Isolated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault Isolation Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flowchart Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TX Power Output Fault Isolation Flowchart . . . . . . . . . . . . . . . . . . . . .
6-12
6-12
6-12
6-13
6-13
6-13
6-13
6-14
Troubleshooting: Transmit ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cannot Perform Txmask Measurement . . . . . . . . . . . . . . . . . . . . . . . . .
Cannot Perform Rho or Pilot Time Offset Measurement . . . . . . . . . . .
Cannot Perform Code Domain Power and Noise Floor Measurement .
Cannot Perform Carrier Measurement . . . . . . . . . . . . . . . . . . . . . . . . . .
6-15
6-15
6-15
6-16
6-16
Troubleshooting: Receive ATP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi–FER Test Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-17
6-17
Troubleshooting: CSM Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problem Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Intermittent 19.6608 MHz Reference Clock / GPS Receiver Operation
No GPS Reference Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checksum Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GPS Bad RX Message Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CSM Reference Source Configuration Error . . . . . . . . . . . . . . . . . . . . .
6-18
6-18
6-18
6-18
6-18
6-18
6-19
1X SCt4812ET Lite BTS Optimization/ATP
PRELIMINARY
Table of Contents
– continued
Takes Too Long for CSM to Come INS . . . . . . . . . . . . . . . . . . . . . . . .
6-19
SCCP Backplane Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connector Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCCP Backplane Troubleshooting Procedure . . . . . . . . . . . . . . . . . . . .
Digital Control Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DC Power Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TX and RX Signal Routing Problems . . . . . . . . . . . . . . . . . . . . . . . . . .
6-20
6-20
6-20
6-21
6-21
6-24
6-25
RFDS – Fault Isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All tests fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All RX and TX paths fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All tests fail on a single antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-26
6-26
6-26
6-26
6-26
Module Front Panel LED Indicators and Connectors . . . . . . . . . . . . . . . . . . . . .
Module Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LED Status Combinations for All Modules
(except GLI2, CSM, BBX2, MCC24, MCC8E) . . . . . . . . . . . . . . . . . .
DC/DC Converter LED Status Combinations . . . . . . . . . . . . . . . . . . . .
CSM LED Status Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GLI2 LED Status Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GLI2 Pushbuttons and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BBX2 LED Status Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MCC24 LED Status Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LPA Shelf LED Status Combinations . . . . . . . . . . . . . . . . . . . . . . . . . .
6-28
6-28
6-28
6-28
6-29
6-31
6-32
6-33
6-33
6-34
Basic Troubleshooting – Span Control Link . . . . . . . . . . . . . . . . . . . . . . . . . . .
Span Problems (No Control Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set BTS Site Span Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-35
6-35
6-36
1X SCt4812ET Lite BTS Optimization/ATP
08/01/2001
PRELIMINARY
Basic Troubleshooting Overview
Overview
The information in this chapter addresses some of the scenarios likely to
be encountered by Customer Field Engineering (CFE) team members.
This troubleshooting guide was created as an interim reference document
for use in the field. It provides “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 from experience in Motorola labs and
classrooms.
08/01/2001
1X SCt4812ET Lite BTS Optimization/ATP
PRELIMINARY
6-1
Troubleshooting: Installation
Cannot Log into Cell-Site
Table 6-1: Login Failure Troubleshooting Procedures
n Step
Action
If MGLI2 LED is solid RED, it implies a hardware failure. Reset MGLI2 by
re-seating it. If this persists, install RGLI2 card in MGLI2 slot and retry. A Red
LED may also indicate no termination on an external LAN connector (power entry
compartment at rear of frame).
Verify that the span line is disconnected at the Span I/O card. If the span is still
connected, verify the CBSC has disabled the BTS.
Try ‘ping’ing the MGLI2.
Verify the LMF is connected to the primary LAN (LAN A) at the LAN shelf
below the SCCP cage. If LAN A is not the active LAN, force a LAN switch to
LAN A by following the procedure in Table 6-2.
Verify the LMF was configured properly.
If a Xircom parallel BNC LAN interface is being used, verify the BTS-LMF cable
is RG-58 (flexible black cable of less than 2.5 feet length).
Verify the external LAN connectors are properly terminated (power entry
compartment at rear of frame).
Verify a T-adapter is not used on LMF computer side connector when connected
to the primary LAN at the LAN shelf.
Try connecting to the Ethernet Out port in the power entry compartment (rear of
frame). Use a TRB–to–BNC (triax–to–coax) adapter at the LAN connector for this
connection.
10
Re-boot the CDMA LMF and retry.
11
Re-seat the MGLI2 and retry.
12
Verify GLI2 IP addresses are configured properly by following the procedure in
Table 6-3.
Table 6-2: Force Ethernet LAN A to Active State as Primary LAN
n Step
Action
If LAN A is not the active LAN, make certain all external LAN connectors are
terminated with 50Ω loads or cabled to another frame.
If it has not already been done, connect the LMF computer to the stand–alone or
starter frame, as applicable (Table 3-6).
If it has not already been done, start a GUI LMF session and log into the BTS on
the active LAN (Table 3-7).
. . . continued on next page
6-2
08/01/2001
PRELIMINARY
1X SCt4812ET Lite BTS Optimization/ATP
Troubleshooting: Installation – continued
Table 6-2: Force Ethernet LAN A to Active State as Primary LAN
n Step
Remove the 50Ω termination from the LAN B IN connector in the power entry
compartment at the rear of the stand–alone or starter frame. The CDMA LMF
session will become inactive.
Disconnect the LMF computer from the LAN shelf LAN B connector and connect
it to the LAN A connector.
If the LAN was successfully forced to an active state (the cards in any cage can be
selected and statused), proceed to step 13.
With the 50Ω termination still removed from the LAN B IN connector, remove
the 50Ω termination from LAN B OUT connector. If more than one frame is
connected to the LAN, remove the termination from the last frame in the chain.
If the LAN was successfully forced to an active state (the cards in any cage can be
selected and statused), proceed to step 13.
With the 50Ω terminations still removed from LAN B, unseat each GLI card in
each frame connected to the LAN, until all are disconnected from the shelf
backplanes.
10
Reseat each GLI card until all are reconnected.
11
Allow the GLIs to power up, and attempt to select and status cards in the CCP
shelves. If LAN A is active, proceed to step 13.
12
If LAN A is still not active, troubleshoot or continue troubleshooting following
the procedures in Table 6-1.
13
08/01/2001
Action
Replace the 50Ω terminations removed from the LAN B IN and OUT connectors.
PRELIMINARY
1X SCt4812ET Lite BTS Optimization/ATP
6-3
Troubleshooting: Installation – continued
Table 6-3: GLI IP Address Setting
n Step
Action
If it has not previously been done, establish an MMI communication session with
the GLI card as described in Table 3-11.
Enter the following command to display the IP address and subnet mask settings
for the card:
config lg0 current
A response similar to the following will be displayed:
GLI2>config lg0 current
lg0: IP address is set to
DEFAULT (configured based on card location)
lg0: netmask is set to
DEFAULT (255.255.255.128)
If the IP address setting response shows an IP address rather than “Default
(configured based on card location),” enter the following:
config lg0 ip default
A response similar to the following will be displayed:
GLI2>config lg0 ip default
_param_config_lg0_ip(): param_delete(): 0x00050001
lg0: ip address set to DEFAULT
If the GLI subnet mask setting does not display as “DEFAULT
(255.255.255.128),” set it to default by entering the following command:
config lg0 netmask default
A response similar to the following will be displayed:
GLI2>config lg0 netmask default
_param_config_lg0_netmask(): param_delete(): 0x00050001
lg0: netmask set to DEFAULT
. . . continued on next page
6-4
08/01/2001
PRELIMINARY
1X SCt4812ET Lite BTS Optimization/ATP
Troubleshooting: Installation – continued
Table 6-3: GLI IP Address Setting
n Step
Action
Set the GLI route default to default by entering the following command:
config route default default
A response similar to the following will be displayed:
GLI2>config route default default
_esh_config_route_default(): param_delete(): 0x00050001
route: default gateway set to DEFAULT
NOTE
Changes to the settings will not take effect unless the GLI is reset.
When changes are completed, close the MMI session, and reset the GLI card.
Once the GLI is reset, re–establish MMI communication with it and issue the
following command to confirm its IP address and subnet mask settings:
config lg0 current
A response similar to the following will be displayed:
GLI2>config lg0 current
lg0: IP address is set to
DEFAULT (configured based on card location)
lg0: netmask is set to
DEFAULT (255.255.255.128)
Repeat steps 1 through 7 for all remaining GLI2s, including those in any
additional, inter–connected frames.
Cannot Communicate with
Power Meter
Table 6-4: Troubleshooting a Power Meter Communication Failure
n Step
08/01/2001
Action
Verify Power Meter is connected to LMF with GPIB adapter.
Verify cable setup as specified in Chapter 3.
Verify the GPIB address of the Power Meter is set to 13. Refer to Test Equipment
setup section of Chapter 3 for details.
. . . continued on next page
PRELIMINARY
1X SCt4812ET Lite BTS Optimization/ATP
6-5
Troubleshooting: Installation – continued
Table 6-4: Troubleshooting a Power Meter Communication Failure
n Step
Action
Verify that Com1 port is not used by another application.
Verify that the communications analyzer is in Talk&Listen mode, not Control
mode.
Cannot Communicate with
Communications Analyzer
Table 6-5: Troubleshooting a Communications Analyzer Communication Failure
n Step
6-6
Action
Verify analyzer is connected to LMF with GPIB adapter.
Verify cable setup.
Verify the GPIB address is set to 18.
Verify the GPIB adapter DIP switch settings are correct. Refer to Test Equipment
setup section for details.
Verify the GPIB adapter is not locked up. Under normal conditions, only 2 green
LEDs must be ‘ON’ (Power and Ready). If any other LED is continuously ‘ON’,
then power-cycle the GPIB Box and retry.
If a Hyperterm window is open for MMI, close it.
Verify the LMF GPIB address is set to 18.
Verify the analyzer is in Talk&Listen mode, not Control mode.
08/01/2001
PRELIMINARY
1X SCt4812ET Lite BTS Optimization/ATP
Troubleshooting: Download
Table 6-6: Troubleshooting Code Download Failure
n Step
Action
Verify T1 or E1 span is disconnected from the BTS at CSU.
Verify LMF can communicate with the BTS device using the Status function.
Communication to MGLI2 must first be established before trying to talk to any
other BTS device. MGLI2 must be INS_ACT state (green).
Verify the card is physically present in the cage and powered-up.
If card LED is solid RED, it implies hardware failure. Reset card by re-seating it.
If this persists, replace card from another slot & retry.
NOTE
The card can only be replaced by a card of the same type.
Re-seat card and try again.
If BBX2 reports a failure message and is OOS_RAM, the code load was OK.
Status it to verify the load.
If the download portion completes and the reset portion fails, reset the device by
clicking on the device and selecting DEVICE > RESET.
Cannot Download DATA to Any
Device (Card)
Table 6-7: Troubleshooting Data Download Failure
n Step
08/01/2001
Action
Re-seat card and repeat code and data load procedure.
Verify the ROM and RAM code loads are of the same release by statusing the
card. Refer to Chapter 3, “Download the BTS” for more information.
PRELIMINARY
1X SCt4812ET Lite BTS Optimization/ATP
6-7
Troubleshooting: Download – continued
Cannot ENABLE Device
Before a device can be enabled (placed in-service), it must be in the
OOS_RAM state (yellow on the LMF) with data downloaded to the
device. The color of the device on the LMF changes to green, once it is
enabled.
The three states that devices can be displayed:
S Enabled (green, INS)
S Disabled (yellow, OOS_RAM)
S Reset (blue, OOS_ROM)
Table 6-8: Troubleshooting Device Enable (INS) Failure
n Step
Action
Re-seat card and repeat code and data load procedure.
If CSM cannot be enabled, verify the CDF file has correct latitude and longitude
data for cell site location and GPS sync.
Ensure primary CSM is in INS_ACT state.
NOTE
MCCs will not go INS without the CSM being INS.
6-8
Verify 19.6608 MHz CSM clock is present; MCCs will not go INS without it.
BBXs should not be enabled for ATP tests.
If MCCs give “invalid or no system time,” verify the CSM is enabled.
08/01/2001
PRELIMINARY
1X SCt4812ET Lite BTS Optimization/ATP
Troubleshooting: Download – continued
LPA Errors
Table 6-9: LPA Errors
n Step
Action
If LPAs continue to give alarms, even after cycling power at the circuit breakers,
then connect an MMI cable to the LPA and set up a HyperTerminal connection.
Enter ALARMS in the Hyperterminal window. The resulting hyperTerminal
display may provide an indication of the problem. (Call Field Support for further
assistance.)
08/01/2001
PRELIMINARY
1X SCt4812ET Lite BTS Optimization/ATP
6-9
Troubleshooting: Calibration
Bay Level Offset Calibration
Failure
Table 6-10: Troubleshooting BLO Calibration Failure
n Step
Verify the Power Meter is configured correctly (see the test equipment setup
section) and connection is made to the proper TX port.
Verify the parameters in the bts–#.cdf file are set correctly for the following
bands:
For 1900 MHz:
Bandclass=1; Freq_Band=16
For 800 MHz:
Bandclass=0; Freq_Band=8
Verify that no LPA in the sector is in alarm state (flashing red LED). Reset the
LPA by pulling the circuit breaker, and, after 5 seconds, pushing back in.
Re-calibrate the Power Meter and verify it is calibrated correctly with cal factors
from the power sensor.
Verify GPIB adapter is not locked up. Under normal conditions, only 2 green
LEDs must be ‘ON’ (Power and Ready). If any other LED is continuously ‘ON’,
power-cycle (turn power off and on) the GPIB Box and retry.
Verify the power sensor is functioning properly by checking it with the 1–mW (0
dBm) Power Ref signal.
If communication between the LMF and Power Meter is working, the Meter
display will show “RES :’’
Verify the combiner frequency is the same as the test freq/chan.
6-10
Action
08/01/2001
PRELIMINARY
1X SCt4812ET Lite BTS Optimization/ATP
Troubleshooting: Calibration – continued
Calibration Audit Failure
Table 6-11: Troubleshooting Calibration Audit Failure
n Step
Action
Verify Power Meter is configured correctly (refer to the test equipment setup
section).
Re-calibrate the Power Meter and verify it is calibrated correctly with cal factors
from the power sensor.
Verify that no LPA is in alarm state (rapidly flashing red LED). Reset the LPA by
pulling the circuit breaker, and, after 5 seconds, pushing back in.
Verify the power sensor is functioning properly by checking it with the 1 mW (0
dBm) Power Ref signal.
After calibration, the BLO data must be re-loaded to the BBXs before auditing.
Click on the BBX(s) and select Download Code > Download Data>Enable.
Re-try the audit.
Verify GPIB adapter is not locked up. Under normal conditions, only 2 green
LEDs must be ‘ON’ (Power and Ready). If any other LED is continuously ‘ON’,
power-cycle (turn power off and on) the GPIB Box and retry.
08/01/2001
PRELIMINARY 6-11
1X SCt4812ET Lite BTS Optimization/ATP
Basic Troubleshooting – RF Path Fault Isolation
Overview
The optimization (RF path characterization or calibration) and
post-calibration (audit) procedures measure and limit-check the BTS
reported transmit and receive levels of the path from each BBX2 to the
back of the frame. When a fault is detected, it is specific to a receive or
transmit path. The troubleshooting process in this section determines the
most probable cause of the fault.
As the calibration and audit tests are performed, results are displayed in
the LMF test status report window. When faults are encountered, the test
procedure in progress continues running and displaying any further
faults. If it appears that there are major faults, the test can be aborted.
The test results can be saved to a bts–<#>.rpt file in the
wlmf\cdma\bts–<#> folder. To do this, close the test status report
window using the Save Results button.
IMPORTANT
Closing the test status report window with the Dismiss
button will delete the test results without saving them.
If a test is re–run or a new calibration, audit, or test is run and the results
are saved, the previous test results in the bts–<#>.rpt file are
overwritten. To prevent losing previous test results in the bts–<#>.rpt
file, refer to the procedure in Table 4-10 before performing further
testing with the LMF.
If there are major faults, recheck the test equipment attachments for
errors. If none are found, close the test status report window using the
Save Results button, and save the contents of the resulting
bts–<#>.rpt file as described in Table 4-10. Also, note other specifics
about the failure, and proceed with the fault isolation procedure.
If Every Test Fails
Check the calibration equipment for proper operation by manually
setting the signal generator output attenuator to the lowest output power
setting. Connect the output port to the spectrum analyzer RF input port.
Set the signal generator output attenuator to –90 dBm, and switch on the
RF output. Verify that the spectrum analyzer can receive the signal,
indicate the correct signal strength (accounting for the cable insertion
loss), and indicate the approximate frequency.
6-12
1X SCt4812ET Lite BTS Optimization/ATP
08/01/2001
PRELIMINARY
Basic Troubleshooting – RF Path Fault Isolation – continued
Verify BLO Checkbox
When performing a calibration with the TX Calibration... or All
Cal/Audit... functions, the Verify BLO checkbox should normally be
checked. When a calibration fails, determine if any items such as
directional couplers or combiners have been added to the TX path. If
additional items have been installed in the path, try re–running the
calibration with Verify BLO unchecked. If calibration still does not
pass, refer to the following paragraphs and use the TX output fault
isolation flowchart to identify the most probable cause of the failure.
If Faults Are Isolated
If the fault reports are isolated between successful path checks, the root
cause of the faults most likely lies with one or more of the Field
Replaceable Unit (FRU) modules. If more than one failure was reported,
look for a common denominator in the data. For example, if any TX test
fails on one sector only, the BBX2 assigned to that sector (Table 1-5) is a
likely cause. Also, look at the severity of the failure. If the path loss is
just marginally out of the relaxed specification limit during the
post-calibration TX audit, suspect excessive cable loss. If limits are
missed by a wide margin, suspect mis–wired cables or total device
failure. Use the TX output fault isolation flowchart in Figure 6-1 to
identify the strongest possible cause for a failed TX test.
Fault Isolation Flowchart
The flowchart covers the transmit path. Transmit paths usually fail the
lower test limit, indicating excessive loss in some component in the BTS
site or mis–wiring. A failure of an upper limit usually indicates a
problem with the test setup or external equipment. Before replacing a
suspected FRU, always repeat and verify the test results to rule out a
transient condition. If a BBX2 fails an upper limit in the post–calibration
audit procedure, re–calibrate and verify the out–of–tolerance condition
for that BBX2 and/or sector before replacement.
Flowchart Prerequisites
Before entering the fault isolation sequence outlined in the flowchart, be
sure the following have been completed:
S GLIs, MCCs, and BBXs have been downloaded with the correct ROM
code, RAM code, and data (Table 3-13, Table 3-14, and Table 3-15).
S MGLI, CSMs, and MCCs are enabled (Table 3-14, Table 3-17, and
Table 3-18, respectively)
S Be sure the LED on the correct CCD card is solid green.
S Be sure no alarms are being reported by opening an LMF alarm
window as outlined in Table 3-47.
08/01/2001
1X SCt4812ET Lite BTS Optimization/ATP
PRELIMINARY
6-13
Basic Troubleshooting – RF Path Fault Isolation – continued
TX Power Output Fault
Isolation Flowchart
Figure 6-1: TX Output Fault Isolation Flowchart
Start
TX Power
Out of Limits
Did TX Output
fail the High or
Low limit?
High limit
failure.
Does
redundant BBX
have the same
problem on the
same sector?
No
Likely Cause:
Yes
Low limit
failure.
Does any other
sector have the
same problem?
Yes
Likely Cause:
External Power Measurement
Equipment and/or Set–up.
Also check:
Switch card
External Attenuators & Pads,
Check Site Documentation.
Likely Cause:
CIO card
Carrier trunking module
Also check:
CIO–trunking module cabling
TX filter/combiner cabling
TX DRDC/TRDC cabling
Likely Cause:
BBX card
Loose connections on
CIO–trunking module cabling,
TX filter/combiner cabling, or
TX DRDC/TRDC cabling
Also check:
CIO card
Carrier trunking module
Likely Cause:
Crossed TX cabling to include:
– CIO–trunking module,
– Trunking module–filter/combiner,
– Filter/combiner–DRDC/TRDC
Carrier LPAs
Also check:
Carrier trunking module
CIO card.
Likely Cause:
CIO card not fully seated
External Power Measurement
Equipment and/or Set–up
Crossed TX cabling to include:
– CIO–trunking module,
– Trunking module–filter/combiner,
– Filter/combiner–DRDC/TRDC
No
If equipped, does a
BBX on the same
carrier but for a
different sector
pass?
Yes, it passes.
No, next BBX on same carrier
fails on different sector.
If equipped, does a
BBX on a different
carrier but for the
same sector
pass?
Yes, it passes.
No, everything fails
6-14
BBX card
Attempt re–calibration
before replacement.
1X SCt4812ET Lite BTS Optimization/ATP
08/01/2001
PRELIMINARY
Troubleshooting: Transmit ATP
Cannot Perform Txmask
Measurement
Table 6-12: Troubleshooting TX Mask Measurement Failure
n Step
Action
Verify that TX audit passes for the BBX2(s).
If performing manual measurement, verify analyzer setup.
Verify that no LPA in the sector is in alarm state (flashing red LED). Re-set the
LPA by pulling the circuit breaker, and, after 5 seconds, pushing it back in.
Cannot Perform Rho or Pilot
Time Offset Measurement
Table 6-13: Troubleshooting Rho and Pilot Time Offset Measurement Failure
n Step
08/01/2001
Action
Verify presence of RF signal by switching to spectrum analyzer screen.
Verify PN offsets displayed on the analyzer is the same as the PN offset in the
CDF file.
Re–load MGLI2 data and repeat the test.
If performing manual measurement, verify analyzer setup.
Verify that no LPA in the sector is in alarm state (flashing red LED). Reset the
LPA by pulling the circuit breaker, and, after 5 seconds, pushing back in.
If Rho value is unstable and varies considerably (e.g. .95,.92,.93), this may
indicate that the GPS is still phasing (i.e. trying to reach and maintain 0 freq.
error). Go to the freq. bar in the upper right corner of the Rho meter and select Hz.
Press  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.
PRELIMINARY 6-15
1X SCt4812ET Lite BTS Optimization/ATP
Troubleshooting: Transmit ATP – continued
Cannot Perform Code Domain
Power and Noise Floor
Measurement
Table 6-14: Troubleshooting Code Domain Power and Noise Floor Measurement Failure
n Step
Action
Verify presence of RF signal by switching to spectrum analyzer screen.
Verify PN offset displayed on analyzer is same as PN offset being used in the
CDF file.
Disable and re-enable MCC (one or more MCCs based on extent of failure).
Cannot Perform Carrier
Measurement
Table 6-15: Troubleshooting Carrier Measurement Failure
n Step
Action
Perform the test manually, using the spread CDMA signal. Verify High Stability
10 MHz Rubidium Standard is warmed up (60 minutes) and properly connected to
test set-up.
6-16
08/01/2001
PRELIMINARY
1X SCt4812ET Lite BTS Optimization/ATP
Troubleshooting: Receive ATP
Multi–FER Test Failure
Table 6-16: Troubleshooting Multi-FER Failure
n Step
Action
Verify test equipment set up is correct for a FER test.
Verify test equipment is locked to 19.6608 and even second clocks. The yellow
LED (REF UNLOCK) must be OFF.
Verify MCCs have been loaded with data and are INS–ACT.
Disable and re-enable the MCC (1 or more based on extent of failure).
Disable, re-load code and data, and re-enable MCC (one or more MCCs based on
extent of failure).
Verify antenna connections to frame are correct based on the directions messages.
08/01/2001
PRELIMINARY6-17
1X SCt4812ET Lite BTS Optimization/ATP
Troubleshooting: CSM Checklist
Problem Description
Many Clock Synchronization Manager (CSM) board problems may be
resolved in the field before sending the boards 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 boards.
Intermittent 19.6608 MHz
Reference Clock / GPS
Receiver Operation
If having any problems with CSM board kit numbers, SGLN1145 or
SGLN4132, check the suffix with the kit number. If the kit has version
“AB,” then replace with version ‘‘BC’’ or higher, and return model AB
to the repair center.
No GPS Reference Source
Check the CSM boards for proper hardware configuration.
RF–GPS (Local GPS) – CSM kit SGLN1145, which should be installed
in Slot l, has an on-board GPS receiver; while kit SGLN4132, in Slot 2,
does not have a GPS receiver.
Remote GPS (R–GPS) – Kit SGLN4132, which should be installed in
both Slot 1 and Slot 2, does not have a GPS receiver.
Any incorrectly configured board must be returned to the repair center.
Do not attempt to change hardware configuration in the field. Also,
verify the GPS antenna is not damaged and is installed per recommended
guidelines.
Checksum Failure
The CSM could have corrupted data in its firmware resulting in a
non-executable code. The problem is usually caused by either electrical
disturbance, or interruption of data during a download. Attempt another
download with no interruptions in the data transfer. Return CSM board
back to repair center if the attempt to reload fails.
GPS Bad RX Message Type
This is believed to be caused by a later version of CSM software (3.5 or
higher) being downloaded, via LMF, followed by an earlier version of
CSM software (3.4 or lower), being downloaded from the CBSC.
Download again with CSM software code 3.5 or higher. Return CSM
board back to repair center if attempt to reload fails.
6-18
1X SCt4812ET Lite BTS Optimization/ATP
08/01/2001
PRELIMINARY
Troubleshooting: CSM Checklist – continued
CSM Reference Source
Configuration Error
This is caused by incorrect reference source configuration performed in
the field by software download. CSM kit SGLN1145 and SGLN4132
must have proper reference sources configured (as shown below) to
function correctly.
CSM Kit No.
SGLN1145
SGLN4132
Hardware Configuration
With GPS Receiver
Without GPS Receiver
CSM Slot No.
Reference Source Configuration
Primary = Local GPS
Backup = Either LFR or HSO
Primary = Remote GPS
Backup = Either LFR or HSO
Primary = Remote GPS
Backup = Either LFR or HSO
Primary = Mate GPS
Backup = Either LFR or HSO
Takes Too Long for CSM to
Come INS
This 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 LFR/HSO verification section in Chapter 3. At least 1 satellite
should be visible and tracked for the “surveyed” mode and 4 satellites
should be visible and tracked for the “estimated” mode. Also, verify
correct base site position data used in “surveyed” mode.
08/01/2001
1X SCt4812ET Lite BTS Optimization/ATP
PRELIMINARY
6-19
SCCP Backplane Troubleshooting
Introduction
The SCCP backplane is a multi–layer board that interconnects all the
SCCP 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 will
allow the Cellular Field Engineer (CFE) to:
S Determine which connector(s) is associated with a specific problem
type.
S Allow the isolation of problems to a specific cable or connector.
Span Line Connector
The span line input is an 8 pin RJ–45 connector that provides a primary
and secondary (if used) span line interface to each GLI2 in the SCCP
shelf. The span line is used for MM/EMX switch control of the Master
GLI2 and also all the BBX2 traffic.
Power Input (Return A and B connectors)
Provides a 27 volt input for use by the power supply modules.
Power Supply Module Interface
Each power supply module has a series of three different connectors to
provide the needed inputs/outputs to the SCCP backplane. These include
a VCC/Ground input connector, a Harting style multiple pin interface,
and a +15V/Analog Ground output connector. The Transceiver Power
Module converts 27/48 Volts to a regulated +15, +6.5, +5.0 volts to be
used by the SCCP shelf cards.
GLI2 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 GLI2s in the SCCP backplane.
GLI2 Ethernet “A” and “B” Connections
These SMB connectors are located on the SCCP backplane and connect
to the GLI2 board. This interface provides all the control and data
communications over the Ethernet LAN between the master GLI2, the
other GLI2, and the LMF.
BBX2 Connector
Each BBX2 connector consists of a Harting 2SU/1SU digital connector
and two 6–conductor coaxial connectors. These connectors provide DC,
digital, and RF inputs/outputs for the BBX2s in the SCCP backplane.
6-20
1X SCt4812ET Lite BTS Optimization/ATP
08/01/2001
PRELIMINARY
SCCP Backplane Troubleshooting – continued
CIO Connectors
S RX RF antenna path signal inputs are routed through RX paths of the
DRDCs or TRDCs at the RF interface panel (rear of frame), and
through coaxial cables to the two MPC modules. The three “A” (main)
signals go to one MPC; the three “B” (diversity) to the other. The
MPC outputs the low–noise–amplified signals via the SCCP
backplane to the CIO where the signals are split and sent to the
appropriate BBX2.
S A digital bus then routes the baseband signal through the BBX2, to
the backplane, and then on to the MCC24/MCC8E slots.
S Digital TX antenna path signals originate at the MCC24/MCC8Es.
Each output is routed from the MCC24/MCC8E slot through the
backplane to the appropriate BBX2.
S TX RF path signal originates from the BBX2, travels through the
backplane to the CIO, through the CIO, and then through
multi-conductor coaxial cabling to the trunking module and LPAs in
the LPA shelf.
SCCP Backplane
Troubleshooting Procedure
The following tables provide standard procedures for troubleshooting
problems that appear to be related to a defective SCCP backplane. The
tables are broken down into possible problems and steps which should
be taken in an attempt to find the root cause.
IMPORTANT
It is important to note that all steps be followed before
replacing ANY SCCP backplane.
Digital Control Problems
No GLI2 Control via LMF (all GLI2s)
Table 6-17: No GLI2 Control via LMF (all GLI2s)
Step
08/01/2001
Action
Check the Ethernet LAN for proper connection, damage,
shorts, or opens.
Be sure the LAN IN and OUT connectors in the power entry
compartment are properly terminated.
Be sure the proper IP address is entered in the Network Login
tab of the LMF login screen.
Verify SCCP backplane Shelf ID DIP switch is set correctly.
1X SCt4812ET Lite BTS Optimization/ATP
PRELIMINARY
6-21
SCCP Backplane Troubleshooting – continued
Table 6-17: No GLI2 Control via LMF (all GLI2s)
Step
Action
Visually check the master GLI2 connectors (both module and
backplane) for damage.
Replace the master GLI2 with a known good GLI2.
No GLI2 Control through Span Line Connection (All GLI2s)
Table 6-18: No GLI2 Control through Span Line Connection (Both
GLI2s)
Step
Action
Verify SCCP backplane Shelf ID DIP switch is set correctly.
Verify that the BTS and GLI2s are correctly configured in the
OMCR/CBSC data base.
Verify the span configurations set in the GLI2s match those in
the OMC–R/CBSC database (refer to Table 6-29).
Visually check the master GLI2 connectors (both module and
backplane) for damage.
Replace the master GLI2 with a known good GLI2.
Check the span line inputs from the top of the frame to the
master GLI2 for proper connection and damage.
Table 6-19: MGLI2 Control Good – No Control over Co–located
GLI2
Step
Action
Verify that the BTS and GLI2s are correctly configured in the
OMCR CBSC data base.
Check the ethernet for proper connection, damage, shorts, or
opens.
Visually check all GLI2 connectors (both module and
backplane) for damage.
Replace the remaining GLI2 with a known good GLI2.
No AMR Control (MGLI2 good)
Table 6-20: MGLI2 Control Good – No Control over AMR
6-22
Step
Action
Visually check the master GLI2 connectors (both module and
backplane) for damage.
Replace the master GLI2 with a known good GLI2.
Replace the AMR with a known good AMR.
1X SCt4812ET Lite BTS Optimization/ATP
08/01/2001
PRELIMINARY
SCCP Backplane Troubleshooting – continued
No BBX2 Control in the Shelf
Table 6-21: MGLI2 Control Good – No Control over Co–located
BBX2s
Step
Action
Visually check all GLI2 connectors (both module and
backplane) for damage.
Replace the remaining GLI2 with a known good GLI2.
Visually check BBX2 connectors (both module and
backplane) for damage.
Replace the BBX2 with a known good BBX2.
No (or Missing) Span Line Traffic
Table 6-22: BBX2 Control Good – No (or Missing) Span Line Traffic
Step
Action
Visually check all GLI2 connectors (both module and
backplane) for damage.
Replace the remaining GLI2 with a known good GLI2.
Visually check all span line distribution (both connectors and
cables) for damage.
If the problem seems to be limited to one BBX2, replace the
BBX2 with a known good BBX2.
No (or Missing) MCC24/MCC8E Channel Elements
Table 6-23: No MCC24/MCC8E Channel Elements
Step
08/01/2001
Action
Verify CEs on a co–located MCC24/MCC8E (MccType=2)
If the problem seems to be limited to 1 MCC24/MCC8E,
replace the MCC24/MCC8E with a known good
MCC24/MCC8E.
– Check connectors (both module and backplane) for
damage.
If no CEs on any MCC24/MCC8E:
– Verify clock reference to CIO.
1X SCt4812ET Lite BTS Optimization/ATP
PRELIMINARY
6-23
SCCP Backplane Troubleshooting – continued
DC Power Problems
WARNING
Potentially lethal voltage and current levels are routed to
the BTS equipment. This test must be carried out with a
second person present, acting in a safety role. Remove all
rings, jewelry, and wrist watches prior to beginning this
test.
No DC Input Voltage to SCCP Shelf Power Supply Modules
Table 6-24: No DC Input Voltage to Power Supply Module
Step
Action
Verify DC power is applied to the frame. Determine if any
circuit breakers are tripped.
* IMPORTANT
If a breaker has tripped, remove all modules from the SCCP
shelf and attempt to reset it.
– If breaker trips again, there is probably a cable or breaker
problem within the frame or DC PDA.
– If breaker does not trip, there is probably a defective
module or sub–assembly within the shelf. Perform the
tests in Table 2-3 to attempt to isolate the module.
Verify that the PS1 and PS2 circuit breakers on the DC PDA
are functional.
Remove the frame rear access panel (Figure 2-1), and use a
voltmeter to determine if the input voltage is being routed to
the SCCP backplane. Measure the DC voltage level between:
S The PWR_IN_A and PWR_RTN_A contacts on the
extreme right side at the rear of the backplane
S The PWR_IN_B and PWR_RTN_B contacts on the
extreme right side at the rear of the backplane
– If the voltage is not present, there is probably a cable or
circuit breaker problem within the frame or DC PDA.
6-24
If everything appears to be correct, visually inspect the PS1
and PS2 power supply module connectors.
Replace the power supply modules with a known good
module.
If steps 1 through 4 fail to indicate a problem, an SCCP
backplane failure has occurred (possibly an open trace).
1X SCt4812ET Lite BTS Optimization/ATP
08/01/2001
PRELIMINARY
SCCP Backplane Troubleshooting – continued
No DC Voltage (+5, +6.5, or +15 Volts) to a Specific GLI2,
BBX2, or Switchmodule
Table 6-25: No DC Input Voltage to any SCCP Shelf Module
Step
Action
Verify steps outlined in Table 6-24 have been performed.
Inspect the defective module connectors (both module and
backplane) for damage.
Replace suspect module with known good module.
TX and RX Signal Routing
Problems
Table 6-26: TX and RX Signal Routing Problems
Step
Action
Inspect all Harting Cable connectors and backplane
connectors for damage in all the affected board slots.
Perform steps outlined in the RF path troubleshooting
flowchart in Figure 6-1.
08/01/2001
1X SCt4812ET Lite BTS Optimization/ATP
PRELIMINARY
6-25
RFDS – Fault Isolation
Introduction
The RFDS is used to perform Pre–Calibration Verification and
Post-Calibration Audits which limit-check the RFDS-generate and
reported receive levels of every path from the RFDS through the
directional coupler coupled paths. In the event of test failure, refer to the
following tables.
All tests fail
Table 6-27: RFDS Fault Isolation – All tests fail
Step
Action
Check the calibration equipment for proper operation by manually setting the signal generator output
attenuator to the lowest output power setting and connecting the output port to the spectrum analyzer
rf input port.
Set the signal generator output attenuator to –90 dBm, and switch on the rf output. Verify that the
spectrum analyzer can receive the signal, indicate the correct signal strength, (accounting for the cable
insertion loss), and the approximate frequency.
Visually inspect RF cabling. Make sure each directional coupler forward and reflected port connects to
the RFDS antenna select unit on the RFDS.
Check the wiring against the site documentation wiring diagram or the BTS Site Installation manual.
Verify RGLI and TSU have been downloaded.
Check to see that all RFDS boards show green on the front panel indicators. Visually check for
external damage.
If any boards that do not show green replace the RFDS with a known–good unit. Re–test after
replacement.
All RX and TX paths fail
If every receive or transmit path fails, the problem most likely lies with
the rf converter board or the transceiver board. Replace the RFDS with a
known–good unit and retest.
All tests fail on a single
antenna
If all path failures are on one antenna port, forward and/or reflected,
make the following checks.
Table 6-28: RFDS Fault Isolation – All tests fail on single antenna path
Step
Action
Visually inspect the site interface cabinet internal cabling to the suspect directional coupler antenna
port.
Verify the forward and reflected ports connect to the correct RFDS antenna select unit positions on the
RFDS backplane. Refer to the installation manual for details.
. . . continued on next page
6-26
1X SCt4812ET Lite BTS Optimization/ATP
08/01/2001
PRELIMINARY
RFDS – Fault Isolation – continued
Table 6-28: RFDS Fault Isolation – All tests fail on single antenna path
Step
Action
Replace the RFDS with a known–good unit.
Replace the RF cables between the affected directional coupler and RFDS.
NOTE
Externally route the cable to bypass suspect segment.
08/01/2001
1X SCt4812ET Lite BTS Optimization/ATP
PRELIMINARY
6-27
Module Front Panel LED Indicators and Connectors
Module Status Indicators
Each of the non-passive plug-in modules has a bi-color (green & red)
LED status indicator located on the module front panel. The indicator is
labeled PWR/ALM. If both colors are turned on, the indicator is yellow.
Each plug-in module, except for the fan module, has its own alarm
(fault) detection circuitry that controls the state of the PWR/ALM LED.
The fan TACH signal of each fan module is monitored by the AMR.
Based on the status of this signal the AMR controls the state of the
PWR/ALM LED on the fan module.
LED Status Combinations for
All Modules (except GLI2, CSM,
BBX2, MCC24, MCC8E)
PWR/ALM LED
The following list describes the states of the module status indicator.
S Solid GREEN – module operating in a normal (fault free) condition.
S Solid RED – module is operating in a fault (alarm) condition due to
electrical hardware failure.
Note that a fault (alarm) indication may or may not be due to a complete
module failure and normal service may or may not be reduced or
interrupted.
DC/DC Converter LED Status
Combinations
The PWR CNVTR has its own 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.
S Solid GREEN – module operating in a normal (fault free) condition.
S Solid RED – module is operating in a fault (alarm) condition due to
electrical hardware problem.
6-28
1X SCt4812ET Lite BTS Optimization/ATP
08/01/2001
PRELIMINARY
Module Front Panel LED Indicators and Connectors – continued
CSM LED Status Combinations
PWR/ALM LED
The CSMs include on-board alarm detection. Hardware and
software/firmware alarms are indicated via the front panel indicators.
After the memory tests, the CSM loads OOS–RAM code from the Flash
EPROM, if available. If not available, the OOS–ROM code is loaded
from the Flash EPROM.
S Solid GREEN – module is INS_ACT or INS_STBY no alarm.
S Solid RED – Initial power up or module is operating in a fault (alarm)
condition.
S Slowly Flashing GREEN – OOS_ROM no alarm.
S Long RED/Short GREEN – OOS_ROM alarm.
S Rapidly Flashing GREEN – OOS_RAM no alarm or
INS_ACT in DUMB mode.
Short RED/Short GREEN – OOS_RAM alarm.
Long GREEN/Short RED – INS_ACT or INS_STBY alarm.
Off – no DC power or on-board fuse is open.
Solid YELLOW – After a reset, the CSMs begin to boot. During
SRAM test and Flash EPROM code check, the LED is yellow. (If
SRAM or Flash EPROM fail, the LED changes to a solid RED and
the CSM attempts to reboot.)
Figure 6-2: CSM Front Panel Indicators & Monitor Ports
SYNC
MONITOR
PWR/ALM
Indicator
FREQ
MONITOR
FW00303
. . . continued on next page
08/01/2001
1X SCt4812ET Lite BTS Optimization/ATP
PRELIMINARY
6-29
Module Front Panel LED Indicators and Connectors – continued
FREQ Monitor Connector
A test port provided at the CSM front panel via a BNC receptacle allows
monitoring of the 19.6608 MHz clock generated by the CSM. When
both CSM 1 and CSM 2 are in an in-service (INS) condition, the CSM 2
clock signal frequency is the same as that output by CSM 1.
The clock is a sine wave signal with a minimum amplitude of +2 dBm
(800 mVpp) into a 50 Ω load connected to this port.
SYNC Monitor Connector
A test port provided at the CSM front panel via a BNC receptacle allows
monitoring of the “Even Second Tick” reference signal generated by the
CSMs.
At this port, the reference signal is a TTL active high signal with a pulse
width of 153 nanoseconds.
MMI Connector – 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.
6-30
1X SCt4812ET Lite BTS Optimization/ATP
08/01/2001
PRELIMINARY
Module Front Panel LED Indicators and Connectors – continued
GLI2 LED Status Combinations
The GLI2 module has indicators, controls and connectors as described
below and shown in Figure 6-3.
The indicators and controls consist of:
S Four LEDs
S One pushbutton
ACTIVE LED
Solid GREEN – GLI2 is active. This means that the GLI2 has shelf
control and is providing control of the digital interfaces.
Off – GLI2 is not active (i.e., Standby). The mate GLI2 should be
active.
MASTER LED
S Solid GREEN – GLI2 is Master (sometimes referred to as MGLI2).
S Off – GLI2 is non-master (i.e., Slave).
ALARM LED
S Solid RED – GLI2 is in a fault condition or in reset.
S While in reset transition, STATUS LED is OFF while GLI2 is
performing ROM boot (about 12 seconds for normal boot).
S While in reset transition, STATUS LED is ON while GLI2 is
performing RAM boot (about 4 seconds for normal boot).
S Off – No Alarm.
STATUS LED
S Flashing GREEN– GLI2 is in service (INS), in a stable operating
condition.
S On – GLI2 is in OOS RAM state operating downloaded code.
S Off – GLI2 is in OOS ROM state operating boot code.
SPANS LED
S Solid GREEN – Span line is connected and operating.
S Solid RED – Span line is disconnected or a fault condition exists.
08/01/2001
1X SCt4812ET Lite BTS Optimization/ATP
PRELIMINARY
6-31
Module Front Panel LED Indicators and Connectors – continued
GLI2 Pushbuttons and
Connectors
RESET Pushbutton – Depressing the RESET pushbutton causes a
partial reset of the CPU and a reset of all board devices. GLI2 will be
placed in the OOS_ROM state
MMI Connector – The RS–232MMI 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.
Figure 6-3: GLI2 Front Panel Operating Indicators
LED
ALARM LED
ALARM
SPANS LED
SPANS
RESET
RESET
PUSHBUTTON
STATUS
STATUS LED
ACTIVE
ACTIVE LED
STATUS
OFF - operating normally
ON - briefly during powerĆup when the Alarm LED turns OFF.
SLOW GREEN - when the GLI2 is INS (inĆservice)
RESET
All functions on the GLI2 are reset when pressing and releasing
the switch.
ALARM
OFF - operating normally
ON - briefly during powerĆup when the Alarm LED turns OFF.
SLOW GREEN - when the GLI2 is INS (inĆservice)
SPANS
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
MASTER
The pair of GLI2 cards include a redundant status. The card in the
top shelf is designated by hardware as the active card; the card in
the bottom shelf is in the standby mode.
ON - operating normally in active card
OFF - operating normally in standby card
MMI PORT
CONNECTOR
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.
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
MMI
MMI PORT
CONNECTOR
MASTER
MASTER LED
OPERATING STATUS
FW00225
6-32
1X SCt4812ET Lite BTS Optimization/ATP
08/01/2001
PRELIMINARY
Module Front Panel LED Indicators and Connectors – continued
BBX2 LED Status
Combinations
PWR/ALM LED
The BBX module has its own alarm (fault) detection circuitry that
controls the state of the PWR/ALM LED.
The following list describes the states of the bi-color LED:
Solid GREEN – INS_ACT no alarm
Solid RED Red – initializing or power-up alarm
Slowly Flashing GREEN – OOS_ROM no alarm
Long RED/Short GREEN – OOS_ROM alarm
Rapidly Flashing GREEN – OOS_RAM no alarm
Short RED/Short GREEN – OOS_RAM alarm
Long GREEN/Short RED – INS_ACT alarm
MCC24 LED Status
Combinations
The MCC24 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.
The LED indicators and their states are as follows:
PWR/ALM LED
S RED – fault on module
ACTIVE LED
Off – module is inactive, off-line, or not processing traffic.
Slowly Flashing GREEN – OOS_ROM no alarm.
Rapidly Flashing Green – OOS_RAM no alarm.
Solid GREEN – module is INS_ACT, on-line, processing traffic.
PWR/ALM and ACTIVE LEDs
S Solid RED – module is powered but is in reset or the BCP is inactive.
MMI Connectors
S 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.
S 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.
. . . continued on next page
08/01/2001
1X SCt4812ET Lite BTS Optimization/ATP
PRELIMINARY
6-33
Module Front Panel LED Indicators and Connectors – continued
Figure 6-4: MCC24 Front Panel LEDs and LED Indicators
PWR/ALM
PWR/ALM LED
LED
COLOR
OFF - operating normally
ON - briefly during powerĆup and during failure
ąconditions
An alarm is generated in the event of a failure
PWR/ALM
LENS
(REMOVABLE)
ACTIVE
RED
GREEN
RED
ACTIVE
ACTIVE LED
OPERATING STATUS
RAPIDLY BLINKING - Card is codeĆloaded but
ąnot enabled
SLOW BLINKING - Card is not codeĆloaded
ON - card is codeĆloaded and enabled
ą(INS_ACTIVE)
ON - fault condition
SLOW FLASHING (alternating with green) - CHI
ąbus inactive on powerĆup
FW00224
LPA Shelf LED Status
Combinations
LPA Module LED
Each LPA module is provided with a bi–color LED on the ETIB module
next to the MMI connector. Interpret this LED as follows:
S GREEN — LPA module is active and is reporting no alarms (Normal
condition).
S Flashing GREEN/RED — LPA module is active but is reporting an
low input power condition. If no BBX is keyed, this is normal and
does not constitute a failure.
S Flashing RED — LPA is in alarm.
6-34
1X SCt4812ET Lite BTS Optimization/ATP
08/01/2001
PRELIMINARY
Basic Troubleshooting – Span Control Link
Span Problems (No Control
Link)
Table 6-29: Troubleshoot Control Link Failure
n Step
Action
Connect the CDMA LMF computer to the MMI port on the applicable MGLI2/GLI2 as shown in
Figure 6-5.
Start an MMI communication session with the applicable MGLI2/GLI2 by using the Windows
desktop shortcut icon (refer to Table 3-11).
Once the connection window opens, press the CDMA LMF computer Enter key until the GLI2>
prompt is obtained.
At the GLI2> prompt, enter:
config ni current  (equivalent of span view command)
The system will respond with a display similar to the following:
The frame format in flash
Equalization:
Span A – Default (0–131
Span B – Default (0–131
Span C – Default (0–131
Span D – Default (0–131
Span E – Default (0–131
Span F – Default (0–131
is set to use T1_2.
feet
feet
feet
feet
feet
feet
for
for
for
for
for
for
T1/J1,
T1/J1,
T1/J1,
T1/J1,
T1/J1,
T1/J1,
120
120
120
120
120
120
Ohm
Ohm
Ohm
Ohm
Ohm
Ohm
for
for
for
for
for
for
E1)
E1)
E1)
E1)
E1)
E1)
Linkspeed: Default (56K for T1 D4 AMI, 64K otherwise)
Currently, the link is running at the default rate
The actual rate is 0
NOTE
Defaults for span equalization are 0–131 feet for T1/J1 spans and 120 Ohm for E1.
Default linkspeed is 56K for T1 D4 AMI spans and 64K for all other types.
There is no need to change from defaults unless the OMC–R/CBSC span configuration requires it.
The span configurations loaded in the GLI must match those in the OMCR/CBSC database for the
BTS. If they do not, proceed to Table 6-30.
Repeat steps 1 through 5 for all remaining GLIs.
If the span settings are correct, verify the edlc parameters using the show command.
Any alarm conditions indicate that the span is not operating correctly.
S Try looping back the span line from the DSX panel back to the MM, and verify that the looped
signal is good.
S Listen for control tone on the appropriate timeslot from the Base Site and MM.
Exit the GLI MMI session and HyperTerminal connection by selecting File from the connection
window menu bar, and then Exit from the dropdown menu.
If no TCHs in groomed MCCs (or in whole SCCP shelf) can process calls, verify that the ISB
cabling is correct and that ISB A and ISB B cables are not swapped.
08/01/2001
1X SCt4812ET Lite BTS Optimization/ATP
PRELIMINARY
6-35
Basic Troubleshooting – Span Control Link – continued
Figure 6-5: MGLI/GLI Board MMI Connection Detail
STATUS LED
STATUS
RESET ALARM SPANS MASTER MMI ACTIVE
To MMI port
RESET
Pushbutton
ALARM LED
SPANS LED
MASTER LED
MMI Port
Connector
ACTIVE LED
8–PIN
NULL MODEM
BOARD
(TRN9666A)
8–PIN TO 10–PIN
RS–232 CABLE (P/N
30–09786R01)
CDMA LMF
COMPUTER
RS–232 CABLE
COM1
OR
COM2
DB9–TO–DB25
ADAPTER
Set BTS Site Span
Configuration
IMPORTANT
6-36
Perform the following procedure ONLY if span
configurations loaded in the MGLI2/GLI2s do not match
those in the OMCR/CBSC data base, AND ONLY when the
exact configuration data is available. Loading incorrect
span configuration data will render the site inoperable.
1X SCt4812ET Lite BTS Optimization/ATP
08/01/2001
PRELIMINARY
Basic Troubleshooting – Span Control Link – continued
Table 6-30: Set BTS Span Parameter Configuration
n Step
Action
If not previously done, connect the CDMA LMF computer to the MMI port on the applicable
MGLI2/GLI2 as shown in Figure 6-5.
If there is no MMI communication session in progress with the applicable MGLI2/GLI2, initiate
one by using the Windows desktop shortcut icon (refer to Table 3-11).
At the GLI2> prompt, enter:
config ni format

Source Exif Data:
File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.3
Linearized                      : No
Modify Date                     : 2001:09:20 17:18:30-04:00
Create Date                     : 2001:09:20 17:17:41-04:00
Producer                        : Acrobat Distiller 4.0 for Windows
Page Count                      : 162
EXIF Metadata provided by EXIF.tools
FCC ID Filing: IHET5BR1

Navigation menu