Tier2 Symettry 3.5 WLL

ABS4000 Tier II Troubleshooting
Course
033-100725-001, Issue 1
The information in this manual is subject to change without notice. All statements, information
and recommendations in this manual are believed to be accurate, but are presented without
warranty of any kind, expressed or implied. Users must take full responsibility for their use of
any products.
No part of this publication may be reproduced or transmitted in any form or by any means,
electronic or mechanical, including photocopying and recording, or by any information storage
or retrieval system, without prior written consent from SR Telecom Inc.
SR TELECOM, AIRSTAR, ANGEL, INSIGHT NMS, METROFLEX, METROPOL, SR500,

SR500IP, SWING, SYMMETRY and WL500 are trademarks of SR Telecom Inc. All rights
reserved 2006. All other trademarks are property of their owners. Information subject to change
without notice.
© 2006, SR Telecom Inc.

All rights reserved. 6/19/06
Printed in Canada
Head Office:
SR Telecom Inc. Tel.: +1 514 335 1210
8150 Trans-Canada Hwy. Fax: +1 514 334 7783
Montreal, Quebec 1 888 SRTELECOM (778-3532) (U.S. and Canada)
Canada H4S 1M5 www.srtelecom.com
ii ABS4000 Tier II Troubleshooting Course

Table of Contents
Course Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Module 1: Troubleshooting the Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Lesson 1: CP Software Reboot and Downloads . . . . . . . . . . . . . . . . . . . . . . . . 23
Lesson 2: CP Re-Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Lesson 3: SMP IP Address Modification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Lesson 4: V5.2 Interface Verification (With Alarms) . . . . . . . . . . . . . . . . . . . . . 43
Lesson 5: V5.2 Interface Verification (Without Alarms). . . . . . . . . . . . . . . . . . . 51
Lesson 6: BRU Alarm Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Lesson 7: BRU Verification (No Alarms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Module 2: Troubleshooting the CPEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Lesson 1: CPE Startup Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Lesson 2: CPE Installation Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Module 3: Troubleshooting RF Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Lesson 1: Uplink RF Interference Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Lesson 2: Downlink RF Interference Detection. . . . . . . . . . . . . . . . . . . . . . . . . 89
Module 4: Troubleshooting Telephony Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Lesson 1: Voice Communication Interruptions . . . . . . . . . . . . . . . . . . . . . . . . . 97
Lesson 2: Voice Line Noise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Lesson 3: E1 Link Synchronization Slips . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Module 5: Troubleshooting Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Lesson 1: Duplex Mode Verification Between the Base Station
and the Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
and the Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
and the CPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Lesson 4: Ethernet Cable Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Lesson 5: Ethernet Connectivity Verification. . . . . . . . . . . . . . . . . . . . . . . . . . 161
Lesson 6: CPE IP Address Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
ABS4000 Tier II Troubleshooting Course iii

iv ABS4000 Tier II Troubleshooting Course
ABS4000 Tier II Troubleshooting Course
Course Introduction Troubleshooting the Troubleshooting
CPEs Data Services
Troubleshooting the CPE Startup Verification Duplex Mode Verification

Base Station Between the Base Station
CPE Installation and the Gateway
Verification
CP Software Reboot and Duplex Mode Verification
Downloads Between the Base Station
CP Re-Activation Troubleshooting RF and the Hub
Interference Duplex Mode Verification
SMP IP Address
Modification Between the Base Station
Uplink RF Interference and the CPE
V5.2 Interface Verification Detection
(With Alarms) Ethernet Cable Verification
Downlink RF Interference
V5.2 Interface Verification Ethernet Connectivity
Detection
(Without Alarms) Verification
BRU Alarm Verification CPE IP Address

Troubleshooting Verification
BRU Verification (No Telephony Services
Alarms)
Voice Communication
Interruptions
Voice Line Noise
E1 Link Synchronization
Slips
1
2 ABS4000 Tier II Troubleshooting Course
Course Introduction
Overview
The introduction provides an overview of the tier I and II courses, as well as
describes the SYMMETRY ABS4000 Tier II Troubleshooting course objectives,
course prerequisites, and course outline.
ABS4000 Tier II Troubleshooting Course 3

Course Introduction
SR Telecom Headquarters Location
SR Telecom™ headquarters in Montreal, Canada
• Over 500 employees

• The plant is over 11 000 m2
• ISO-9001 registered

Course Introduction
Tier Knowledge System Architecture
Tier II
Tier I
Jv04011701
• Tier I courses provide the essential knowledge and skills that are required to
start working with an SR Telecom system
• Tier II courses, such as operations and troubleshooting, provide specialized
skills and in-depth knowledge of an SR Telecom system

Course Introduction
Course Objectives
The SYMMETRY ABS4000 Tier II Troubleshooting course objectives provide
students with the ability to:
• Identify and isolate faults at the base station and CPEs

• Resolve voice problems
• Resolve data Problems
• Resolve Network Management System (NMS) Problems
• Run application (app) calls to locate and correct errors in a
SYMMETRY ABS4000 system

Course Introduction
Course Prerequisites
The SYMMETRY ABS4000 Tier II Troubleshooting course assumes that students
possess a basic knowledge of the following:
• SYMMETRY NMS tools, including the Local Craft Interface Device (LCID) and
the Gabriel Element Management System (EMS)
• Broadband data and telephony provisioning
• Radio frequency (RF) engineering principles
• Networking

Course Introduction
Participant Introductions
• Name
• Company
• Title and function
• Job responsibility
• Technical background
• Networking or radio experience
• Course expectations

Course Introduction
Course Materials
• Name tag
• Student manual
— Slides
— Hands-on exercises
— glossary
• Supplementary CD
• Course evaluation

Course Introduction
Facilities
Class Hours Phones
Meals Pager/Cell
Rest Rooms Smoking

RB03101403

Course Introduction
SYMMETRY ABS4000 Tier II Troubleshooting

Overview
The SYMMETRY ABS4000 Tier II Troubleshooting course provides a list of
symptoms that may affect your network. Locate the symptom that most resembles
your network problem and review the probable causes, then follow the
recommended procedures to resolve the problem.
SYMMETRY ABS4000 Tier II Troubleshooting Overview
Symptom Probable Cause Procedure
• CP is not operational • CP is not loaded with a • Section “Verify the CP LED

• CP is not communicating valid software version Status Indicators” on page 24
with the base station • CP is not loaded with • Section “Verify CP Status” on
any software page 25
• Section “Reboot the CP” on
page 26
• Section “Download Valid
Software to the CP” on
page 29
CP is operational, but not CP has locked itself out of • Section “Verify CP Status” on
communicating with the service page 34
base station, continuously • Section “Re-Activate CP
failing to boot Software Load” on page 35
SMP CP is not able to boot SMP may be configured • Section “Connect to the SMP
with invalid IP Ethernet Port” on page 40
configuration parameters • Section “Reprogram the SMP
IP Address” on page 41

Course Introduction
V5.2 network interface is • Transmission path • Section “Verify V5.2 Interface

down and alarms are may be compromised Status” on page 44
present on the E1 link between the base • Section “Verify the Alarms at
station and the LE the LE” on page 46
• E1 cable connection • Section “Perform a Loopback
may be loose or Test to the LE” on page 47
disconnected at the
• Section “Verify the Physical
base station or LE
E1 Connection” on page 48
• Synchronization
• Section “Verify the
source designation
Synchronization Source
may not be valid
Designation” on page 49
V5.2 network interface is V5.2 network interface • Section “Verify the V5.2
down and no alarms are parameters do not match Interface Configuration
present on the E1 link the configuration at the Parameters” on page 52
V5.2 voice switch • Section “Verify E1 link Status”
on page 53
BRU encounters an alarm • BRU is faulty • Section “Verify BRU Alarm
condition • Frequency provisioned Status” on page 56
does not match the • Section “Scenario 1: BRU is
BRU’s operating in Alarm” on page 57
frequency • Section “Scenario 2: BRU is
• BRU is not calibrated in Alarm” on page 58

Course Introduction
BRU suspected of having a • Weak or no RSSI for Section “Verify the RSSI Level”
problem; however, there are an associated BRU in on page 60
no alarms a sector that supports
RF path diversity
• Significant branch
imbalance, an RSSI
level difference of
more than 25,
between two BRUs
configured in a single
sector
CPE continuously reboots • CPE product code is • Section “Verify the CPE
or does not start up invalid Product Code” on page 66
• CPE is not loaded with • Section “Reboot the CPE” on
a valid software page 67
version • Section “Download Valid
• CPE is not loaded with Software to the CPE” on
any software page 70

Course Introduction
CPE installation has failed • CPE is not correctly • Section “Verify the CPE Site
installed or Survey Criteria” on page 76
provisioned • Section “Verify the CPE
• CPE installation Installation and Provisioning
parameters are not Criteria” on page 77
correctly entered in the • Section “Verify the CPE LED
work order and do not Status Indicators” on page 79
match the
• Section “Verify the SQI
configuration
Installation Criteria” on
information at the base
page 81
station
• FTR degradation • Base station RF • Section “Verify the SNR
• SNR below the required configuration does not Measurements” on page 86
threshold match the associated • Section “Verify the Base
network plan Station Configuration” on
• CPE of an adjacent page 87
base station may be • Section “Determine the
the cause of the Source of the Uplink
interference Interference” on page 88
• Higher BLER • RU is not installed in a Section “Verify the Downlink
• Use of lower order location that optimizes Interference Levels” on page 90
modulations and the RF signal between
excessive call hand over the base station and
CPE
• Base station antenna
is significantly higher
or lower than RU
antenna

Course Introduction
• Dropped calls • Low RSSI, airlink • Section “Run a Ping Test

• No dial tone communication Over the NAC Airlink” on
between the CPE and page 99
• No voice path the base station is • Section “Verify Airlink Status”
compromised on page 101
• CPE is not • Section “Run a BLER
communicating with Loopback Test” on page 102
the base station over
• Section “Run a Ping Test
the NAC or HSD
Over the HSD Airlink” on
airlink
page 105
• V5.2 network interface
• Section “Verify E1 Voice Span
is not operating
Status” on page 107
properly
• Section “Verify V5.2 Network
• E1 connection
Interface Status” on page 108
between the base
station and LE is not • Section “Verify Base Station
secured or the E1 link Alarm Status” on page 109
has encountered an • Section “Verify CP Status
alarm condition Logs” on page 110
• Section “Print the Number of
DSP Crashes” on page 111

Course Introduction
CPE encounters noise on • Airlink communication • Section “Verify Airlink Status”

the voice line between the CPE and on page 115
the base station is • Section “Run a BLER
compromised Loopback Test” on page 116
• BOB cable wiring • Section “Verify Voice Channel
incorrectly connected Conditions” on page 118
to the BOB unit or
• Section “Capture the
telephone handset is
Hardware Resources” on
faulty
page 119
• Section “Test the Voice Line”
on page 121
• Section “Verify the BOB
Connections” on page 123
• Section “Verify the SSU4000
BOB Cable Connections” on
page 124
• Section “Verify the SSU4400
BOB Cable Connections” on
page 125

Course Introduction
Fax or modem performance Synchronization slips over • Section “Verify ESI Status” on
problems, such as dropped the E1 links that are page 130
calls or reduced configured for voice, fax, • Section “Verify ESI LED
transmission rates or modem communication Status Indicators” on
page 131
• Section “Verify the E1 Link
Performance Metrics” on
page 132
• HSD service is Mismatched duplex • “Verify CPE Downlink and
operational; but there are setting between the base Uplink Data Rates” on
a lot of dropped packets station and the gateway page 138
• CPE data rates are lower • “Verify Ethernet Link Status”
than expected in the on page 141
uplink and downlink • “Verify the Base Station
• Ethernet link errors are Duplex Mode Setting” on
reported by the router or page 144
base station • “Verify the Gateway Duplex
Mode Setting” on page 145

Course Introduction
• HSD service is The base station is • “Verify CPE Downlink and

operational; however, connected to the DSN Uplink Data Rates” on
data rates are lower than over a hub that does not page 138
expected for all CPEs support full-duplex mode • “Verify Ethernet Link Status”
communicating with a on page 141
specific base station
• “Verify the Hub Duplex Mode
• Ethernet link errors are Setting” on page 148
reported by the customer
supplied hub or base
station
• HSD performance is CPEs (R4) supporting a • “Verify CPE Downlink and
lower than expected for a 10Base-T Ethernet Uplink Data Rates” on
specific CPE, despite interface may be page 138
good airlink configured to operate only • “Verify Ethernet Link Status”
communication and no in half-duplex mode on page 141
congestion
• “Verify CPE RF Link Status”
• Subscriber PC or CPE is on page 152
reporting link errors
• “Verify the PC Ethernet Link
• Subscriber PC is Settings” on page 153
configured for full-duplex
• “Verify the CPE Ethernet Link
Settings” on page 155

Course Introduction
• All CPEs serving a • Wrong cable is used • “Verify CPE Downlink and
single base station • Ethernet cable is not Uplink Data Rates” on
cannot receive or secured page 138
transmit data • “Verify Ethernet Link Status”
• BOB unit is not wired
• A specific CPE cannot correctly on page 141
receive or transmit data • “Verify CPE RF Link Status”
on page 152
• “Verify the Ethernet Cable
Connections” on page 158
• “Verify the BOB Connections”
on page 123
• Base station cannot • Destination IP address • “Verify Ethernet Backhaul
reach the next hop uplink is not on the same Connectivity” on page 162
destination IP address subnet as the base • “Verify the Next Hop Uplink
• CPE cannot reach the station (host) Destination” on page 163
next hop downlink • Destination IP address • “Verify the Next Hop Downlink
destination IP address is not mapped in the Destination” on page 164
ARP table
• “Display Active PPPoE
Sessions” on page 165
• CPE connected to PC DSN network IP address • “Verify the DSN Network
reports a duplicate settings specified at the Configuration” on page 168
IP address on the LAN base station are • “Verify the DSN IP Network
• Multiple CPEs or overlapping the CPE IP Settings” on page 169
subscribers for a single address range
base station report
duplicate IP addresses
on the LAN

Module 1: Troubleshooting the Base Station
Module 1: Troubleshooting the Base Station
Overview
The lessons covered in this module are:
CP Software Reboot and Downloads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
CP Re-Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
SMP IP Address Modification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
V5.2 Interface Verification (With Alarms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
V5.2 Interface Verification (Without Alarms). . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
BRU Alarm Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
BRU Verification (No Alarms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Lesson 1: CP Software Reboot and Downloads Module 1: Troubleshooting the Base Station
Lesson 1: CP Software Reboot and Downloads
Symptom
Circuit pack (CP) is not operational or is not communicating with the
ABS4000 Base Station.
Probable Cause
• CP is not loaded with the valid software version
• CP is not loaded with any software
Procedures
“Verify the CP LED Status Indicators” on page 24
“Verify CP Status” on page 25
“Reboot the CP” on page 26
“Download Valid Software to the CP” on page 29

Module 1: Troubleshooting the Base Station Lesson 1: CP Software Reboot and Downloads
Verify the CP LED Status Indicators
Circuit
Pack LED Primary CP Standby CP CP Status
Green (Solid) Green (Solid) Powered
Power Power
Red (Solid) Red (Solid) Not Powered
or Off or Off Not Operational
Alarm Off Off No Alarms
Alarm
Red (Solid or Red (Solid or
Status Blinking) Blinking) In Alarm
Status Red (Solid) Red (Solid) Not Operational

Orange
Green (Solid) Operational
(Blinking)
Dk06040401
Verify the Light Emitting Diodes (LEDs) to determine if the CP is working properly.
• Power LED must be solid green

• Alarm LED must be off (not solid or blinking red)
• Status LED must be solid green for an active CP (primary) or blinking orange
for a CP in standby mode
— If the Status or Power LED is red, the CP is either not operational or not
powered

Verify CP Status
“Y” indicates that CP is present, operational,

and communicating. CPs present in the
system (Y) display status information
“N” indicates that the CP is not present. CPs not

present in the system (N) do not display any
additional status information
DK06032701
From the Local Craft Interface Device (LCID), click the
CP Status>CP Monitor>Digital tabs to identify any major CP problems.
• “Y” in the Present, Oper, and Comm columns indicates that the CP is present,
operational, and communicating
— Communication status is provided for the Master (M) and Slave (S) CPs
• “N” in the Present column indicates that the CP is not present and no
additional status information is provided

Reboot the CP
Reset Button
for Most CPs
A
Reset Button for

Specific BCP2
Revisions
B
Dk06032801
• Connect an RS-232 flat serial cable to the CP’s 10-pin header and to a PC
running terminal emulation software, such as HyperTerminal or Kermit
• Press the CP’s reset button:
— Most CPs are reset using the upper reset button (A), including the SBC
and BCP2 that provide two, 10-pin headers
— Certain BCP2 versions may be reset using the lower reset button (B)
• Quickly press the ESC key three times when the command line displays:
Hit ESC 3 times to abort start of application (2s timeout)...

Reboot the CP
• Select command option 3:
Choose the commands:
1) Run HwTest Program (Hardware Debug)
2) Run Probe Program (Software Debug)
3) SWCI and EEPROM DE commands
ESC) Continue to load the application
• Select command option 1 to verify the current software release loaded in the
software configuration items (SWCI) #0 and #1:
0) Active SWCI #1 (default: SWCI #0)
1) Query SWCIs
2) Audit SWCIs
3) Dump All EEPROM DE
4) Reset EEPROM Header
ESC) Up to last command page
• The software version loaded for the CP is displayed as follows:
SWCI #0: R241SB1S00C0603
SWCI #1: R241SB1S00A0512
Boot Ver: R163SBMB0000204
• Verify that the correct software release is loaded
— The software release in SWCI #0 and #1 should correspond to the release
indicated in the SYMMETRY software release notes
– First four characters (R241...) denote the software load release =
release 2.41
– The remaining characters denote the CP or CPE type =
Sub-band Controller (SBC)

Reboot the CP
• Press the ESC key two times to continue loading the application:
— The default memory bank loads during the startup process; in this
example, it is SWCI #0
— The startup process is successful when the following is displayed at the
end of the boot up process:
BSM: All tasks inited. Log the BSM_ALL_TASKS_INITED event.
f If no valid software is loaded in the CP, then the message displayed is

“Header CRC Check Error”. To load valid software in a CP, see Section
“Download Valid Software to the CP” on page 29.
• Select command option 0 to swap the default memory bank:

— The default memory bank is swapped; in this example, it switches from
SWCI #0 to SWCI #1
1) Query SWCIs
2) Audit SWCIs
• Press the ESC key until the following commands are displayed, then press the
the ESC key again to start the startup process for the newly selected default
memory bank (SWCI #1):

Download Valid Software to the CP

The ANGEL/SYMMETRY Download Utility program is used to download a valid
software release to a CP’s SWCI memory banks in cases where no valid software
is loaded on the CP.
Before loading the software in a base station CP:
• Verify that the Download Utility program is installed on your PC

• Verify that the base station files (.bin) from \\CD1swan\swan\loads are copied
to the Download Utility directory in \\utility\sw_dl_utility\wan\SWANx_xxx
• Verify that the name of the SWANx_xxx folder in the Download Utility directory
corresponds to the software release
— The SWAN folder is renamed to match the valid software release; for
example, SWAN2_41C
• Verify that the DownloadUtility.ini file in the Download Utility directory is
updated to correspond to the software release

Download Valid Software in the CP
Dk06041101
• Double-click the DownloadUtility. exe file to run the application

Dk06041101
• Select the appropriate software revision to load
• Select the memory bank in which to load the software (SWCI0 or SWCI1)
• Click the Base PCA card option
— PCA means printed circuit assembly
• Select the appropriate CP for which the software load is intended
— CPs that can be selected include the WP, GNIC, SMP, and SBC
• Remove the CP from the base station chassis
• Connect an RS-232 flat serial cable to the PC’s serial port and to the CP’s
10-pin header
• Click the Start Programming to begin the software load process

Dk06041204
• Re-insert the CP in the base station chassis when the CP being programmed
is identified in the command window; for example, “Programming NIC”
• When the software download is completed, the command window displays the
following:
Download sequence completed!
Press any key to continue . . .

Lesson 2: CP Re-Activation Module 1: Troubleshooting the Base Station
Lesson 2: CP Re-Activation
Symptom
Circuit pack (CP) is operational, but not communicating with the ABS4000 Base
Station. It continuously fails to boot.
Probable Cause
CP has locked itself out of service.
d If there is only one Baseband Control Processor 2 (BCP2) CP installed in the

base station chassis, the Waveform Processor (WP) or Sub-band Controller
(SBC) CP may lock itself out of service if the BCP2 is removed while the
system is powered. The BCP2 provides critical clock synchronization to the
system; therefore, never power a SYMMETRY ABS4000 system without
having at least one BCP2 CP installed in the base station chassis.
Procedures
“Verify CP Status” on page 34
“Re-Activate CP Software Load” on page 35

Module 1: Troubleshooting the Base Station Lesson 2: CP Re-Activation
Verify CP Status
CP is communicating, but not operational
Dk06032805
From LCID, click the CP Status>CP Monitor>Digital tabs to determine if a CP
has locked itself out of service.
• A CP that is communicating, but does not seem to be operational, may have

locked itself out of service:
— Comm M and Comm S = “Y”
— Oper = “N”

Re-Activate CP Software Load
Select CP
Click the Activate Button

Dk06040701
From LCID, click the Configuration>Software Loads tabs to re-activate the

current software load.
• Select the CP from the CPID column

• Click the Activate button

Module 1: Troubleshooting the Base Station Lesson 2: CP Re-Activation
Blue = Active
Red = Inactive
Click the Activate

Button
Dk06040702
• Verify that the CP’s existing software load corresponds to the version indicated
in the SYMMETRY release notes
• Click the Activate button

Select CP
Click to Reset the CP

Click to Reset the
Base Station
Confirms the Sucessful

Re-activation of Active
Software Load (SWCI 0)
for the Selected CP
Dk06040703
• Select the CP, then click either the Reset button to reset the CP or the Base
Reset button to reset the base station to activate the software load
— Voice and data service will be down for approximately 10 minutes during a
base station reset; the base station is reset when absolutely necessary or
during scheduled maintenance periods
• If the CP continues to lock itself out of service it may be defective

Lesson 3: SMP IP Address Modification Module 1: Troubleshooting the Base Station
Lesson 3: SMP IP Address Modification
Symptom
Sub-band Management Processor (SMP) circuit pack (CP) is not able to boot.
Probable Cause
SMP may be configured with invalid IP configuration parameters.
Procedure
“Connect to the SMP Ethernet Port” on page 40
“Reprogram the SMP IP Address” on page 41

Module 1: Troubleshooting the Base Station Lesson 3: SMP IP Address Modification
Connect to the SMP Ethernet Port
Dk06041001
RS-232 Serial Cable

(RJ-45 to DB-9 Connector)
• Connect the RS-232 Serial Cable’s RJ-45 connector to the Base Connection
Interface (BCI) SMP RS-232 port and the DB-9 connector to the serial port of
a PC running terminal emulation software, such as HyperTerminal or Kermit
— Ensure that the cable does not exceed a total length of 15 m (50 ft.)
• Open the terminal emulation software and configure the PC’s local serial port:
— Data bits: 8
— Parity: None
— Stop bits: 1
— Flow control: off and echo on
— Port speed (baud rate): 19200 with auto-detect enabled

Lesson 3: SMP IP Address Modification Module 1: Troubleshooting the Base Station
Reprogram the SMP IP Address

• Press ESC key to change the original settings when the SMP CP restarts from
a reset
• Follow the prompts to select the configuration
• Restart the SMP CP when prompted for any new settings to take effect
— If the SMP fails to boot, the following message is displayed:
pROBE+ Initialization Failed, Error Code 0x00001F05
f An SMP may not be able to boot if invalid IP address parameters are

configured; for example, the programming of a default gateway that is outside
the configured subnet.
• Press the SMP’s reset button

• Quickly press the ESC key three times to get to the boot menu when the
command line displays:
• Select option 2 to program a valid IP address for the SMP:

Lesson 4: V5.2 Interface Verification (With Alarms) Module 1: Troubleshooting the Base Station
Lesson 4: V5.2 Interface Verification (With

Alarms)
Symptom
V5.2 network interface is down and alarms are present on the E1 link.
Probable Cause
• Transmission path may be compromised between the base station and the
Local Exchange (LE)
• E1 cable connection may be loose or disconnected at the base station or LE
• Synchronization source designation may not be valid
Procedures
“Verify V5.2 Interface Status” on page 44
“Verify the Alarms at the LE” on page 46
“Perform a Loopback Test to the LE” on page 47
“Verify the Physical E1 Connection” on page 48
“Verify the Synchronization Source Designation” on page 49

Module 1: Troubleshooting the Base Station Lesson 4: V5.2 Interface Verification (With Alarms)
Verify V5.2 Interface Status
Dk06032902
From LCID, click the System Status> Network Status>Trunk Status tabs to
verify the V5.2 network interface’s operational status.
• C-Path status must be “Up” for the V5.2 protocol control channels
• V5 Interface status must be “Up”
• Voice Trunks status must be “In Service” for voice connections; at least one E1
trunk carrying a C-path channel must be “Up” for voice to be processed
• Data Trunks, as well as Multi-Link Point-to-Point Protocol (MPPP), status must
be “In Service” for data connectivity

Verify the V5.2 Interface Status

If the Voice Trunks status displays “Not in Service”:
• Verify the connection to the V5.2 switch

• Verify that the V5.2 switch is working properly
If the Data Trunks status, as well as the MPPP or BCP 100Base-T status, displays
“Not in Service”:
• Verify the connection to the router

• Verify that the router is working properly

Verify the Alarms at the LE
Dk06033001
Terms
AIS: Alarm Indication Signal
RAI: Remote Alarm Indications
Select Interval Sample LOS: Loss of Signals
LOF: Loss of Frames
RMESS:RX Mechanism Elastic
Store Slips
TMESS: TX Mechanism Elastic
Store Slips
LOTC: Loss of TX Clocks
VC: Violation Counts (VC)
Specify Number of Samples CRC4: Cyclic Redundancy
Check 4 counts
Specify E1 Link FEBE: Far End Block Errors
FAE: Frame Alignment Errors
Click “Get” RDF: Remotely Detected Failures
LDF: Locally Detected Failures
From LCID, click the System Status> Network Status>E1 Performance

Monitor tabs to verify the alarms at the LE.
• Select the 15-minute, 1-hour, or 24-hour interval sample to specify the duration
for collecting the E1 link performance metrics
• Specify the E1 link and the number of samples to be collected
• Click the Get button to retrieve the E1 link performance metrics
• Verify if the selected E1 link indicates any errors, slips, or other problems

Perform a Loopback Test to the LE
Dk06040501
Specify E1 Link
Specify Time Duration
Start or Stop
Loopback Test
evaluate the transmission path between the ABS4000 Base Station and the LE.
• Specify the E1 link to be tested

• Specify the time duration in minutes for the loopback test
• Click the Start Loopback button to run a loopback test for a specified E1 link
• Click the Stop Loopback button to end a loopback test for a specified E1 link

Verify the Physical E1 Connection
Dk06040403
10Base-T Interface
(Local Access to the GNIC)
Power LED
Alarm LED
Status LED Status LED
Solid Red: CP is not operational
Blinking Orange: CP is in standby mode
Solid Green: CP is active (Primary)
If the V5.2 interface is down, verify the following:
• Is the E1 cable securely fastened at the base station and the V5.2 switch
• Is the GNIC operational
— If the Status LEDs is solid red, the GNIC is not operational

Verify the Synchronization Source Designation
Do not mix voice

and data E1 links,
there must be a
contiguous list
of E1s for voice
and data
. E1 voice starts
from #1
. E1 data starts
from #16.
Dk06040502
From LCID, click the Configuration>Base Configuration> Network
Configuration tabs to verify master versus slave clock source designation for the
voice and high-speed data (HSD) services.
• In this scenario, voice should be set up as “Slave” and data should be set up
as “Master”
— SYMMETRY supports various synchronization options, such as Global
Position System (GPS), E1/T1, or external clock method; however, SR
Telecom recommends using GPS clocking on all SYMMETRY systems

Lesson 5: V5.2 Interface Verification (Without Alarms) Module 1: Troubleshooting the Base Station
Lesson 5: V5.2 Interface Verification (Without

Alarms)
Symptom
V5.2 network interface is down and no alarms are present on the E1 link.
Probable Cause
V5.2 network interface parameters do not match the configuration at the
V5.2 voice switch.
Procedure
“Verify the V5.2 Interface Configuration Parameters” on page 52
“Verify E1 link Status” on page 53

Module 1: Troubleshooting the Base Station Lesson 5: V5.2 Interface Verification (Without Alarms)
Verify the V5.2 Interface Configuration Parameters
Dk06033003
From LCID, click the Configuration>Base Configuration>V5.2/XML config to
verify the V5.2 configuration parameters between the base station and the switch.
• Verify that the values for the Variant Number, LE Interface Id, Interface Type,
and Interface Edition match to values configured at the voice switch
• Verify that the correct V5.2/XML configuration file is selected
— V5.2/XML configuration files contain national specific PSTN configuration
data and must be set correctly to allow interoperability between the base
station and the V5.2 switch

Lesson 5: V5.2 Interface Verification (Without Alarms) Module 1: Troubleshooting the Base Station
Verify E1 link Status
Dk06040503
From LCID, click the System Status>Network Status>Trunk Status tabs to
verify the E1 link status assigned to V5.2 network interface.
• C-Path status must be “Up” for the V5.2 protocol control channels
• V5 Interface status must be “Up”
• Voice Trunks status must be “In Service” for voice traffic
• Data Trunks status must be “In Service” for data connectivity

Lesson 6: BRU Alarm Verification Module 1: Troubleshooting the Base Station
Lesson 6: BRU Alarm Verification
Symptom
Base Radio Unit (BRU) encounters an alarm condition.
Probable Cause
• BRU is faulty
• Set frequency does not match the BRU’s operating frequency
• BRU is not calibrated
Procedure
“Verify BRU Alarm Status” on page 56
“Scenario 1: BRU is in Alarm” on page 57
“Scenario 2: BRU is in Alarm” on page 58

Module 1: Troubleshooting the Base Station Lesson 6: BRU Alarm Verification
Verify BRU Alarm Status
Click CP Option to
Select an Individual
CP from the List
Dk06040601
From LCID, click the Monitor>Alarms tabs to verify if any alarms are reported by
the BRU. The BRU can report fault conditions, which include the following:
• Power or overtemperature alarm: BRU may not be working properly

• Local oscillator (LO) alarm: BRU programmed frequency may not match the
BRU’s operating frequency
• Calibration error: BRU may not be calibrated or the programmed frequency
may not match the BRU’s operating frequency

Lesson 6: BRU Alarm Verification Module 1: Troubleshooting the Base Station
Scenario 1: BRU is in Alarm
Reset Command
Dk06040602
From LCID, click the CP Status>CP Monitor>EIS tabs if the BRU encounters any
type of alarm condition.
• EIS (expansion interfaces) tab displays WiMAX Transceiver Interface (WTIF)

or the Digital Shelf Interface (DSI) status for a corresponding BRU or XCVR
• Verify if the WTIF is in alarm then click in the “Action” column to access the
“Reset” command for the corresponding BRU
• Reset the BRU; if the WTIF is still in alarm after the reset, replace the BRU

Module 1: Troubleshooting the Base Station Lesson 6: BRU Alarm Verification
Scenario 2: BRU is in Alarm
Verify Selected
Frequency with
BRU Operating
Frequency
Dk06040603
From LCID, click the Configuration>Base Configuration>RF Configuration
tabs if the BRU encounters an “LO not lock” alarm condition or calibration error.
• Locate the BRU’s part number to verify its operating frequency

• Verify that the BRU is calibrated
• Verify the that the BRU’s operating frequency is correctly set
— If the BRU’s operating frequency is correctly set, then the transceiver may
have a problem

Lesson 7: BRU Verification (No Alarms) Module 1: Troubleshooting the Base Station
Lesson 7: BRU Verification (No Alarms)
Symptom
BRU suspected of having a problem; however, there are no alarms.
Probable Cause
• Weak or no Receive Signal Strength Indication (RSSI) for an associated BRU
in a sector that supports RF path diversity (two BRUs)
• Significant branch imbalance, an RSSI level difference of more than 25,
between two BRUs configured in a single sector
Procedure
“Verify the RSSI Level” on page 60

Module 1: Troubleshooting the Base Station Lesson 7: BRU Verification (No Alarms)
Verify the RSSI Level
<25 Between BRU A and B

BRU A BRU B
Very Little or Strong Signal

No Received Signal Strength Level
Dk06040604
From LCID, click the Airlink PM>CPE Sync tabs in the event that a problem is
suspected with the BRU; however, no alarms are present.
• Verify that the RSSI levels for both branch values (BRU A and BRU B) are
within the ranges specified in Section “Verify the RSSI Level” on page 61
— The RSSI represents the BRU received signal strength as seen at the CPE
• Verify that the difference between the two branch values is not greater than 25
— If there is an RSSI difference more 25 between the two branch values,
replace the associated BRU

Lesson 7: BRU Verification (No Alarms) Module 1: Troubleshooting the Base Station
Verify the RSSI Level

Depending on the modulation scheme supported by a particular BRU and its
corresponding CPEs, the RSSI level can vary. Typical receiver sensitivity
thresholds are listed, the values assume the following:
• Block Error Rate (BLER) of 1% in Line-of-Sight (LOS) conditions

• RF path diversity (typical diversity gain is 5 dB in LOS conditions)
Modulation Receiver Sensitivity1 Thresholds at Receiver Sensitivity Thresholds1

Schemes the Base Station (Typical) at the CPEs (Typical)
Voice High-Speed Data Voice

(HSD)
64 QAM -110.0 dBm/Tone -108.1 dBm/Tone -109 dBm/Tone

QPSK -122.6 dBm/Tone -121.1 dBm/Tone -123 dBm/Tone
1. The receiver sensitivity thresholds are per tone, 25 dB should be added to calculate the per channel receiver sensitivity.

Module 1: Troubleshooting the Base Station Lesson 7: BRU Verification (No Alarms)
Review – Q & A
• ABS4000 CP software reboots and downloads
• ABS4000 CP re-activation
• SMP IP Address modification
• V5.2 interface verification
• BRU verification

Module 2: Troubleshooting the CPEs
Overview
CPE Startup Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
CPE Installation Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Lesson 1: CPE Startup Verification
Symptom
CPE (SSU4000 or SSU4400) continuously reboots or does not start up.
Probable Cause
• CPE product code is invalid
• CPE is not loaded with a valid software version
• CPE is not loaded with any software
Procedures
“Verify the CPE Product Code” on page 66
“Reboot the CPE” on page 67
“Download Valid Software to the CPE” on page 70

Module 2: Troubleshooting the CPEs Lesson 1: CPE Startup Verification
Verify the CPE Product Code

Part Site Serial
Number Code Number YYMMDD Revision
Product
Code
Dk06050803
Base Station and CCA Description Product Code of
CPE Circuit Card Supported CCA
Assembly (CCA)
SSU4x00 SSU4x00 CPE with Data and Voice Support CLRU4XXNXX or

CLRU4XXNVD
SSU4000(data only) SSU4000 CPE with Data Support (No Voice) CLRU4XXX0D
SSU4000 (voice only) SSU4x00 CPE with Voice Support (No Data) CLRU4XXXV0
• Verify the CPE product codes to ensure that the latest updates are included
— CPE product codes are located on the SSU4000 or SSU44000 labels, as
well as can be read through the Gabriel or LCID NMS
• CPE product codes must match the values listed in the SYMMETRY release
notes
— Mismatched product codes can cause CPEs to continuously reboot

Lesson 1: CPE Startup Verification Module 2: Troubleshooting the CPEs
Reboot the CPE

• Power down the SSU4000 or SSU4400 Break-out Box (BOB) unit
• Connect an RS-232 serial cable to the BOB unit’s maintenance port and to a
PC running terminal emulation software, such as HyperTerminal or Kermit
• Power up the BOB, then quickly press the ESC key three times when the
command line displays:
• Select command option 3:
• Select command option 1 to verify the current software release loaded in the
software configuration items (SWCI) #0 and #1:
1) Query SWCIs
2) Audit SWCIs

Reboot the CPE

• The software version loaded for the CPE is displayed as follows:
SWCI #0: R241RU4S00B0602
SWCI #1: R241RU4S00B0602
Boot Ver: R169RU4B0000306
• Verify that the correct software release is loaded
— The software release in SWCI #0 and #1 should correspond to the release
indicated in the SYMMETRY software release notes
– First four characters (R241...) denote the software load release =
release 2.41
– The remaining characters denote the CP or CPE type =
Radio Unit (RU4...)
• Press the ESC key two times to continue loading the application:
— The default memory bank loads during the startup process; in this
example, it is SWCI #0
— The startup process is successful when the following is displayed at the
end of the boot up process:
BSM: All tasks inited. Log the BSM_ALL_TASKS_INITED event.
f If no valid software is loaded in the CPE, then the message displayed is

“Header CRC Check Error”. To load valid software in a CPE, see Section
“Download Valid Software to the CPE” on page 70.

Reboot the CPE

• Select command option 0 to swap the default memory bank:
— The default memory bank is swapped; in this example, it switches from
SWCI #0 to SWCI #1
1) Query SWCIs
2) Audit SWCIs
• Press the ESC key until the following commands are displayed, then press the
the ESC key again to start the startup process for the newly selected default
memory bank (SWCI #1):

Download Valid Software to the CPE

The ANGEL/SYMMETRY Download Utility program is used to download a valid
software release to a CPE’s SWCI memory banks in cases where there is no valid
software loaded into the CPE.
Before loading the software in an SSU4000 or SSU4400:
• Verify that the Download Utility program is installed on your PC

• Verify that the CPE files (.cmp) from \\CD1swan\swan\loads are copied to the
Download Utility directory in \\sw_dl_utility\wan\SWANx_xxx, as well as in the
appropriate R3 or R4 folder
• Verify that the name of the SWANx_xxx folder in the Download Utility directory
corresponds to the software release
— The SWAN folder is renamed to match the valid software release; for
example, SWAN2_41C
• Verify that the DownloadUtility.ini file in the Download Utility directory is
updated to correspond to the software release

Dk06041101
• Double-click the DownloadUtility. exe file to run the application

Dk06041301
• Select the appropriate software revision to load
• Select the memory bank in which to load the software (SWCI0 or SWCI1)
• Click the CPE Unit option
• Select the appropriate CPE for which the software load is intended
• Connect an RS-232 straight-through serial cable to the PC’s serial port and to
the SSU4000 or SSU4400 BOB unit’s maintenance port
• Power down the SSU4000 or SSU4400 BOB unit
• Click the Start Programming to begin the software load process

Dk06041302
• Power up the BOB unit
• Press the ESC key when the message “Agent Software” is displayed in the
command window to start the application download

Dk06041303
• Press the ESC key when the message “Flash Done” is displayed in the
command window to start the application download to SWCI #0
• Press the ESC key again when the message “Flash Done” is displayed in the
command window to start the application download to SWCI #1

Lesson 2: CPE Installation Verification Module 2: Troubleshooting the CPEs
Lesson 2: CPE Installation Verification
Symptom
CPE (SSU4000 or SSU4400) installation has failed.
Probable Cause
• CPE is not correctly installed or provisioned at the subscriber premises
• CPE installation parameters are not correctly entered in the work order and do
not match the configuration information at the base station
Procedures
“Verify the CPE Site Survey Criteria” on page 76
“Verify the CPE Installation and Provisioning Criteria” on page 77
“Verify the CPE LED Status Indicators” on page 79
“Verify the SQI Installation Criteria” on page 81

Module 2: Troubleshooting the CPEs Lesson 2: CPE Installation Verification
Verify the CPE Site Survey Criteria

Prepare the Work Orders Create the Data Files Synchronize the MIT PDA
for Synchronizaton
Perform the MIT Survey with a CPE

and Battery Backpack
Set Up the Site Survey Equipment
Start the MIT Application
Select a Work Order
Determines the
Location of the
Install and Connect the Radio Units (RU)
SSU4000 or SSU4400
Provision the SSU4000 or SSU4400

using the MIT PDA
Verify Voice and Data Services
CPE Installation and Verification Completed DK06041304
• Verify that the latest work orders are loaded on the MIT PDA
• Verify that the CPE in the best possible location to optimize the
RF propagation path
• Verify that the CPE is synchronized and communicating with the base station
• Verify that the CPE is installed at least 3 m (10 ft.) above street level
• Verify that the CPE is loaded with a valid software release

Verify the CPE Installation and Provisioning

Criteria
• Create the CPE records using MICHAEL Order Management (MOM)
— CPE records are classified as “pending CPE” in both the Gabriel NMS and
the base station
— Provision the voice switch and Data Service Node (DSN)
• Generate the work order files using MOM
• Synchronize the MIT Palm file with work order file
• Install the CPEs at the subscriber sites
— CPEs send installation message to the base station
— Base station sends the message “CPE installation successful”
• Verify that the CPE is synchronized and can communicate with the base
station
— Gabriel Viewer receives a message to change CPE status from pending to
installed in the system database after the CPE is installed and
communicating with the base station
• Provision the voice and data services
• Test the voice and data connections

Verify the CPE Installation and Provisioning

Criteria
Michael Order Manager Web Browser
Add Subscriber, Create CPE Installation Order and Submit It

No Hardware Serial Number (HSN) yet
MIT Work Order Check Gabriel Viewer for the Pending CPE Record (Optional)
Synchronization LOC code xxxx
(Field) Services created? —
(NOC)
CPE In Pending Mode
CPE Field MIT Installation
(Field)
CPE In Installed Mode
Close the Work
Pick Phone Lines. Check Dial Tone. Make Call. Check Data.
Order for this Go to a Web Site and Check Data Connection.
Particular (Field)
Installation and
Synchronization
(Field)
Check Gabriel Viewer and/or Base Status & Control
Services Automatically Created
HSN Automatically Updated
Check thee Sector that the CPE was installed.
(NOC)
Dk06041305
CPE Installation and Verification Completed

Verify the CPE LED Status Indicators
05
12
04
06
Dk
Power Status
RF Link Status
SQI Status
• The SSU4000 and SSU4400 integrated Radio Units (RUs) support three LED
status indicators: Power (PWR) Status, RF Link Status, and the Signal Quality
Index (SQI) Status
• An operational CPE indicates a solid green LED for the power and RF Link
status, as well as a flashing green LED for the SQI status.

Verify the CPE LED Status Indicators

LEDs State Interpretation
PWR Off No power or CPE application software did not startup

Status
Green (Solid) CPE is powered and the CPE application software is operational
RF Link Off LED is not lit during the CPE boot sequence; if the LED does
Status not light after a minute, the boot sequence has failed
Red (Flashing) No RF synchronization:
• CPE is not synchronized with the base station
Orange RF synchronization, but no Network Access Channel (NAC)
(Flashing) synchronization:
• CPE has achieved downlink synchronization with the base
station
• CPE is receiving broadcast messages from the base station
Green NAC synchronization, but no high-speed data (HSD)
(Flashing) synchronization:
• CPE has established basic communication with the base
station in both uplink and downlink and is waiting for
configuration information from the base station
Green (Solid) CPE is fully operational
SQI Off LED remains off until the CPE has achieved downlink
Status synchronization with the base station
Red (Flashing) SQI is < 50
Green SQI is >50
(Flashing)

Verify the SQI Installation Criteria

The CPE installation is based on a single criterion of SQI (Signal Quality Index).
The SQI is an indication of the quality of the downlink RF signal as seen by the
CPE. The SQI value is primarily used during CPE installations to optimize the
location of the CPEs, ensuring that the best possible signal is received from the
base station.
• The SQI value has a range of 0 to 100

• The greater the SQI, the better the downlink channel quality
• An SQI value ≥50 indicates a downlink signal of sufficient quality for a
successful CPE installation
• An SQI value <50 indicates a weak downlink signal that indicates that the
installation location for the CPE is not acceptable

Review – Q & A
• CPE product codes
• CPE reboot process
• CPE software download
• CPE site survey criteria
• CPE installation and provisioning criteria
• CPE LED status indicators
• SQI installation criteria

Module 3: Troubleshooting RF Interference
Overview
Uplink RF Interference Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Downlink RF Interference Detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Lesson 1: Uplink RF Interference Detection Module 3: Troubleshooting RF Interference
Lesson 1: Uplink RF Interference Detection
Symptom
• Frequency-time resource (FTR) degradation
• Signal-to-Noise Ratio (SNR) below the required threshold
Probable Cause
• Base station RF configuration does not match the associated network plan
• CPE of an adjacent base station may be the cause of the interference
Procedures
“Verify the SNR Measurements” on page 86
“Verify the Base Station Configuration” on page 87
“Determine the Source of the Uplink Interference” on page 88

Module 3: Troubleshooting RF Interference Lesson 1: Uplink RF Interference Detection
Verify the SNR Measurements
Selected Sector
Time
Frequency
Voice Partition
Click to
Display
Actual SNR
Measurements
Dk06042101
From LCID, click the System Status> Call tabs to verify the uplink interference.
• Cells are highlighted in the voice partition if there is signal interference

• Click Display SNR Data to monitor the received SNR in real time for a sector
— Verify if the interference moves in frequency over time, as well as
determine the number of FTRs that are affected by the interference
– FTRs not used by a call are typically greater than 25 dBm; if all values
are less than 15 dBm, the base station may be experiencing some type
of RF equipment failure or external interference

Lesson 1: Uplink RF Interference Detection Module 3: Troubleshooting RF Interference
Verify the Base Station Configuration
Frequency Assignment
Base Station Offset Code (BSOC)

Embeds a Value from 0-31 in the Signal
to Uniquely Identify the Base Station
Dk06041702
From LCID, click the Configuration> Base Configuration>RF Configuration
tabs to verify that the base station configuration matches the RF network plan.
• Verify that the base station frequency, as well as BSOC, is correctly assigned
— If a CPE from an adjacent base station is suspected as being the source of
the interference, temporarily disable (power down) the CPE to verify if the
received interference at the base station still persists
— If the CPE is the source of the interference, re-orient or relocate the RU

Module 3: Troubleshooting RF Interference Lesson 1: Uplink RF Interference Detection
Determine the Source of the Uplink Interference

If the source of the interference is not believed to be from an adjacent CPE,
perform the following:
• Check the coverage map to verify if the service providers is using any other
wireless equipment in the same operating frequency band
• If the source of the interference cannot be identified, visit the base station site
with a spectrum analyzer and a directional antenna to locate the source of
interference
— At the highest point, as near as possible to the antenna, pan the directional
antenna to determine the direction of the interfering signal
— Measurements can be taken at multiple sites to pinpoint the exact location
of the interference
– If the interfering source is an unauthorized transmitter, then it maybe
necessary to contact the local regulatory authorities
f A Low Noise Amplifier (LNA) may also be required to detect very low signals.

Lesson 2: Downlink RF Interference Detection Module 3: Troubleshooting RF Interference
Lesson 2: Downlink RF Interference Detection
Symptom
• Higher Block Error Rate (BLER)
• Use of lower order modulations and excessive call hand over
Probable Cause
• RU is not installed in a location that optimizes the RF signal between the base
station and CPE
• Base station antenna is significantly higher or lower than RU antenna
Procedures
“Verify the Downlink Interference Levels” on page 90

Module 3: Troubleshooting RF Interference Lesson 2: Downlink RF Interference Detection
Verify the Downlink Interference Levels
Displays the Interference “<” Indicates Interference

Detected from Each is Below or at Noise Level
Base Station in dBm
Displays the Carrier-to-Interference in dB

(≥18 dB is Required to Pass the Downlink Test)
Specifies Time Duration for

Collecting the Metrics in Seconds
Selects the CPE
Dk06041801
From LCID, click the Airlink PM> Base Interference tabs to verify the
interference levels measured in the downlink direction.
• Select multiple CPEs to test for downlink interference since the level of
downlink interference will likely vary based on the RU location and orientation
• Correlate the level of interference on a map with the CPE locations to
determine the direction of the interference signal


• Since downlink interference will likely first manifests itself in higher BLERs, as
well as the use of lower order modulations and excessive call hand over, it is
important to monitor the symptoms regularly using one of the following:
— Gabriel for real time metrics
— Raphael for generating reports

Module 3: Troubleshooting RF Interference Lesson 2: Downlink RF Interference Detection

f2 f1 BSOC 0
BSOC 2 f3 A
Interference-1
D f2
B
C
BSOC 1
f4
f2 f2
Interference-2
No interference since the
frequency used for BSOC 0 (f1)
BSOC 3 is not the same as the frequency
used for BSOC 1, 2, and 3 (f2)
Interference exists since the
frequency used for BSOC 2 and 3
(f2) is the same as the frequency
Dk06042801
used for BSOC 1 (f2) CPE
• C/I ratio is expressed in dB and is a measure of the amount of interference that

the CPE can potentially observe from other ABS4000 Base Stations
— For C/I calculations, the signal is measured on the time-keyed RSPs
– C/I ratio is not displayed if interference is generated by other sources
transmitting on frequencies that do not correspond to the RSP locations
– C/I ratio is not displayed if there is interference from a base station with
same BSOC as the parent base station
— The higher C/I ratio, the better the signal quality
— The C/I threshold is 18 dB

Review – Q & A
• Uplink RF interference
• Downlink RF interference

Module 4: Troubleshooting Telephony Services
Overview
Voice Communication Interruptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Voice Line Noise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
E1 Link Synchronization Slips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Module 4: Troubleshooting Telephony Services
Lesson 1: Voice Communication Interruptions
Symptom
The network is experiencing problems establishing and maintaining voice
connections at the subscriber site, problems encountered include:
• Dropped calls
• No dial tone
• No voice path
Probable Cause
• Low RSSI, airlink communication between the CPE and the base station is
compromised
• CPE is not communicating with the base station over the Network Access
Channel (NAC) or High-speed Data (HSD) airlink
• V5.2 network interface is not operating properly
• Physical E1 connection between the base station and Local Exchange is not
secured or the E1 link has encountered an alarm condition

Module 4: Troubleshooting Telephony Services Lesson 1: Voice Communication Interruptions
Procedures
“Run a Ping Test Over the NAC Airlink” on page 99
“Verify Airlink Status” on page 101
“Run a BLER Loopback Test” on page 102
“Run a Ping Test Over the HSD Airlink” on page 105
“Verify E1 Voice Span Status” on page 107
“Verify V5.2 Network Interface Status” on page 108
“Verify Base Station Alarm Status” on page 109
“Verify CP Status Logs” on page 110
“Print the Number of DSP Crashes” on page 111

Lesson 1: Voice Communication Interruptions Module 4: Troubleshooting Telephony Services
Run a Ping Test Over the NAC Airlink
Click NAC Option
Select Sector and CPE
Click Ping Button
Dk06041901
From LCID, click the System Status>CPE Status>Ping tabs to verify if a
selected CPE communicates with the base station over the NAC airlink.
• Select the specific CPE in the designated sector

• Click the CPE over NAC Airlink option
• Click the Ping button to run the test

Run a Ping Test Over the NAC Airlink
The Selected CPE

Passed Ping Test
Dk06041902
• Click the OK button when the message confirms that the Ping test for the
selected CPE was successful
• If the Ping test fails, run a Ping test for all CPEs in the sector to determine if all
the CPEs are encountering the same problem or if this is an isolated incident
— If all the CPEs cannot communicate over the NAC, see Section Module 3:
“Troubleshooting RF Interference” on page 83 to identify the source of
interference
— If this is an isolated incident, re-orient or relocate the RU at the CPE site

Verify Airlink Status
BRU A BRU B
Dk06041802
From LCID, click the Airlink PM>CPE Sync tabs to verify airlink status.
• Verify that the RSSI levels for both branch values (BRU A and B) are within the
receiver sensitivity threshold ranges listed in Section “Verify the RSSI Level”
on page 61 for the selected CPE
• If the difference is greater than 25 between the two branch values or if the
RSSI levels are not within the acceptable ranges, see Section Module 3:
“Troubleshooting RF Interference” on page 83

Run a BLER Loopback Test
Selected Sector
and CPE
Click the
Start Button
Specify BLER Specify Time Intervals for to Run the
Test Duration Periodic Updates of Test
Airlink Quality
Dk06041904
From LCID, click the System Status>CPE Status>BLER tabs to determine the
transmission levels at both the base station and the CPE.

• Specify the BLER test duration, as well as the intervals for periodic updates
• Click the Start button to run the BLER test

Resets to Zero at
Approximately 65,000
-6
BLER <1% (10000 x 10 )
BLER % = Uncorrectable Blocks × 100

Good + Corrected + Uncorrectable Blocks
Dk06041903
• Verify the number of total, good, corrected, and uncorrected Reed-Solomon
(RS) Blocks in the uplink and downlink
• BLER is the ratio of uncorrectable to the total number of received RS Blocks
— BLER should always be less than 1% for the voice air interface
• Statistically valid samples require a collection of more than 65,536 units worth
of data

Dk06042001
• If the BLER test fails to start, an error message is displayed indicating an error
failure code
— BLER test failure can indicate that the HSD airlink is probably down
• Click the OK button, then run a Ping test over the HSD airlink to determine if all
the CPEs in the sector are unable to communicate with the base station over
the HSD channel or if this is an isolated incident

Run a Ping Test Over the HSD Airlink
Select
Sector
and CPE . Data Link Up: Cells Shaded White Click HSD Option
. Data Link Down: Cells Shaded Gray
Click Ping Button
Total CPE
Data Link
Count
Dk06042003
From LCID, click the System Status>CPE Status>Ping tabs to verify if a
selected CPE communicates with the base station over the HSD airlink.

• Click the CPE over HSD Airlink option
• Click the Ping button to run the test

Run a Ping Test Over the HSD Airlink
Dk06042002
• Click the OK button when the message confirms that the Ping test for the
selected CPE was successful
• If the Ping test fails, run a Ping test for all CPEs in the sector to determine if all
the CPEs are encountering the same problem or if this is an isolated incident
— If all the CPEs cannot communicate over the HSD channel, see Section
Module 3: “Troubleshooting RF Interference” on page 83 to identify the
source of interference
— If this is an isolated incident, re-orient or relocate the RU at the CPE site

Verify E1 Voice Span Status
Select the Time Interval
Specify the E1 Link Specify the Number

of Samples
Dk06042005
Monitor tabs to verify if there are errors, slips, or other problems with the physical
layer E1 links assigned for voice service.
• Click the appropriate time interval samples tab for collecting the E1 data
• Click the Get button to retrieve the samples

Verify V5.2 Network Interface Status
Voice E1 Status
V5.2 Protocol
Control Channels
V5.2 Interface Status
Dk06042004
verify if the V5.2 network interface is “Up” and stable.
• If the V5.2 interface is down, verify that the physical E1 connection between
the base station and the switch is good
• If the voice trunks are “Out of Service”, voice connections cannot be
processed
— At least one E1 trunk carrying a C-path channel must be “Up” for voice
connections

Verify Base Station Alarm Status
Click CP Option to
Select an Individual
CP from the List
Dk06040601
From LCID, click the Monitor>Alarms tabs to verify if any alarms are reported at
the base station.
• A summary of all active CP alarms are displayed

— Click the CP option to select a specific CP from the list

Verify CP Status Logs
Dk06042006
From LCID, click the CP Status>CP Logs tabs to verify if any CP resets have
occurred.
• Logs track CP activity, including resets, stopped communication, or other

major events
• Each log entry displays the CP ID, date and time stamp, as well as the status
of the node
f A default time stamp of 1/07/1999 is displayed when the base station does
not have accurate timing information; generally, the default time stamp is
displayed after a base station or CP reset.

Print the Number of DSP Crashes
Select function
Select CP
bs_print_dsp_de
Click Call Button
Dk06042007
From LCID, click the Development>App Call tabs to print the number of Digital
Signal Processor (DSP) crashes for the selected WP and SBC CPs.
• Select each WP and SBC slave CP from the list; for example, BCP1S or WP1S
• Select the “bsm_print_dsp_de” app call from the list
• Set in the cell for Param1: “0x01”
• Click the Call button to run the “bsm_print_dsp_de” app call
— If the number of DSP crashes is increasing or appears excessive, contact
you SR Telecom representative

Lesson 2: Voice Line Noise Module 4: Troubleshooting Telephony Services
Lesson 2: Voice Line Noise
Symptom
CPE encounters noise on the voice line.
Probable Cause
• Airlink communication between the CPE and the base station is compromised
• BOB cable wiring is incorrectly connected to the BOB or the telephone
handset is faulty

Module 4: Troubleshooting Telephony Services Lesson 2: Voice Line Noise
Procedures
“Verify Airlink Status” on page 115
“Run a BLER Loopback Test” on page 116
“Verify Voice Channel Conditions” on page 118
“Capture the Hardware Resources” on page 119
“Test the Voice Line” on page 121
“Verify the BOB Connections” on page 123
“Verify the SSU4000 BOB Cable Connections” on page 124
“Verify the SSU4400 BOB Cable Connections” on page 125
“Verify the SSU4000 Surge Arrestor Connections” on page 127
“Verify the SSU4400 Surge Arrestor Connections” on page 128

Verify Airlink Status
BRU A BRU B
Dk06041802
From LCID, click the Airlink PM>CPE Sync tabs to verify airlink status.
• Verify that the RSSI levels for both branch values (BRU A and B) are within the
receiver sensitivity threshold ranges listed in Section “Verify the RSSI Level”
on page 61 for the selected CPE
• If the difference is greater than 25 between the two branch values or if the
RSSI levels are not within the acceptable ranges, see Section Module 3:
“Troubleshooting RF Interference” on page 83

Selected Sector
and CPE
Click the
Start Button
Specify BLER Specify Time Intervals for to Run the
Test Duration Periodic Updates of Test
Airlink Quality
Dk06041904
From LCID, click the System Status>CPE Status>BLER tabs to determine the
transmission levels at both the base station and the CPE.

• Specify the BLER test duration, as well as the intervals for periodic updates
• Click the Start button to run the BLER test

Resets to Zero at
Approximately 65,000
-6
BLER <1% (10000 x 10 )
BLER % = Uncorrectable Blocks × 100

Good + Corrected + Uncorrectable Blocks
Dk06041903
• Verify the number of total, good, corrected, and uncorrected RS Blocks in the
uplink and downlink
• More than 65,536 units worth of data is required to collect a statistically valid
sample
• BLER should always be less than 1%
— When the test starts, the Total RS Blocks counter will start to increment

Verify Voice Channel Conditions
Selected Sector Line ID

Time
CPE ID Modulation
Frequency
Voice Partition
Voice FTRs Usage

. 64-QAM = 2 FTRs
Active Calls (Yellow) . 18-QAM = 3 FTRs
. 8-QAM = 4 FTRs
. QPSK = 6 FTRs
Call
Count
Per
Dk06041701
Sector
Place a call; then from LCID, click the System Status> Call tabs to verify if there
is a shift from 64-QAM to lower order modulations (hand over) for the active calls.
• Cells shaded in yellow represent the active calls

• If there is hand over for most of the active calls, see Section Module 3:
“Troubleshooting RF Interference” on page 83 to stabilize the airlink
— Shifts can occur to lower order modulations if prevailing channel conditions
degrade due to interference or fading

Capture the Hardware Resources
Select BCP
Select Function
rm_read_sbc-details
Click Call Button
Dk06042504
If there is no hand over to lower order modulations for the active voice calls, the
problem can be due to bad hardware resources.
From LCID, click the Development>App Call tabs to capture the resources used
for this call.
• Select the BCP2 CP from the list; for example, BCP1M

• Select the “rm_read_sbc_details” app call
• Click the Call button to run the “rm_read_sbc_details” app call at the BCP2 to
verify if a problem exists with the hardware resources used for this call

Capture the Hardware Resources

• Place another call
— If the same problem persists, run the same app call (rm_read_sbc_details)
at the BCP to capture the hardware resources used for this call
• If the problem occurs on same hardware resource, replace WP
• If the problem occurs on different hardware resource, contact your SR Telecom
Representative

Test the Voice Line
Select Sector
Select Line
and CPE
Click the “Start”

Button to Run the
Ring Test
Dk06042501
From LCID, click the System Status>CPE Status>Line Status tabs to diagnose
voice line problems for the CPEs.

• Select the specific CPE voice line
• Click the Start button to preform a ring test on the selected voice line

Test the Voice Line
Click the “Refresh”

Button to Update
Line Statistics
Dk06042502
• CPD HSD Info notification confirms that the ring test started successfully
— Hook Status and Offhook Count can be useful in diagnosing problems with
inside wiring and telephone equipment at the subscriber premises
• Click the Refresh button to update the line statistics when the message “ring
test complete” is displayed

Verify the BOB Connections

SSU4400 Line 1 SSU4000
Fax
RU Line 2 RU
Telephone
BOB Cable BOB Cable
(15-Pin) (26-Pin) Telephone
BOB Unit BOB Unit Line 1
Line 3
Telephone Line 2
Dk06042503
Line 4 Fax
Telephone
• Verify that an RJ-11 cable is connected securely to the BOB unit’s telephony
interface and the subscriber’s telephone, fax, or modem
• Replace the telephone handset to ensure that the handset is not a faulty
• If a faulty handset is not the problem, verify the BOB cable connection between
the RU and the BOB unit
— BOB cable provides a D-Sub termination to connect to the RU and
IDC termination to connect to the BOB unit
– SSU4000 uses a 15-pin conductor BOB cable (DB-15 connector) to
support up to two telephony interfaces (RJ-11)
– SSU4400 uses a 26-pin conductor BOB cable (DB-26 connector) to
support up to four telephony interfaces (RJ-11)

Verify the SSU4000 BOB Cable Connections

SSU4000 BOB Unit Wire Colour Signal Description DB-15 Connector
Pin Assignment Pin Assignment
1 Brown Ethernet RX Positive (+) 2

2 Brown/White Ethernet RX Negative (-) 10
3 Orange Ethernet TX Positive (+) 3
4 Orange/White Ethernet TX Negative (-) 11
5 Yellow Phone Line 2 Ring 5
6 Yellow/White Phone Line 2 Tip 6
7 Green Phone Line 1 Ring 7
8 Green/White Phone Line 1 Tip 8
9 Blue RS-232 TX 1
10 Blue/White RS-232 RX 9
11 Grey (Drain Wire) Ground 4
12 None No Connection -
13 Black DC Power Negative (-) 12
15 Red DC Power Positive (+) 14
16 Red DC Power Positive (+). 15

Verify the SSU4400 BOB Cable Connections

1 Brown Ethernet RX Positive (+) 2

2 Brown/White Ethernet RX Negative (-) 11
3 Orange Ethernet TX Positive (+) 3
4 Orange/White Ethernet TX Negative (-) 12
9 Blue RS-232 TX 1
10 Blue/White RS-232 RX 19
11/12 Grey (Drain Wire) Ground 10
17 Green/White Phone Line 1 Tip 7
18 Green Phone Line 1 Ring 6
19 Yellow/White Phone Line 2 Tip 5
20 Yellow Phone Line 2 Ring 4


21 Light Blue/White Phone Line 3 Tip 21

22 Light Blue Phone Line 3 Ring 20
23 Purple/White Phone Line 4 Tip 24
24 Purple Phone Line 4 Ring 23

Verify the SSU4000 Surge Arrestor Connections
P/N 7205-07-26N15 N
Brown Brown
Brown/White Brown/White
Orange Orange
Orange/White Orange/White
Yellow Yellow
Yellow/White Yellow/White
Green Green
Green/White Green/White
TO
TO
OUTDOOR B.O.B
Light Blue
UNIT Light Blue/White
Gray (Shielded
Blue Drain Wire)
Blue/White
Black
Gray (Shielded Black
Drain Wire) Red
Black Red
Black
Red Earth Ground
Red Connection
Dk06060802
!

Verify the SSU4400 Surge Arrestor Connections
P/N 7205-08-26N15
Brown Brown
Brown/White Brown/White
Orange Orange
Orange/White Orange/White
Yellow Yellow
Yellow/White Yellow/White
Green Green
Green/White Green/White
TO
TO
OUTDOOR B.O.B
Light Blue
UNIT Light Blue/White
Purple
Light Blue Purple/White
Light Blue/White Black
Purple
Purple/White Red
Black Blue
Blue/White
Red
Blue Drain Wire &
Blue/White Earth Ground
Dk06060801
Connection
!

Lesson 3: E1 Link Synchronization Slips Module 4: Troubleshooting Telephony Services
Lesson 3: E1 Link Synchronization Slips
Symptom
Fax or modem performance problems, such as dropped calls or reduced
transmission rates.
Probable Cause
Synchronization slips over the E1 links that are configured for voice, fax, or
modem communication.
Procedures
“Verify ESI Status” on page 130
“Verify ESI LED Status Indicators” on page 131
“Verify the E1 Link Performance Metrics” on page 132

Module 4: Troubleshooting Telephony Services Lesson 3: E1 Link Synchronization Slips
Verify ESI Status
Dk06042601
From LCID, click the CP Status>CP Monitor>EIS tabs to identify any problem.
• EIS tab displays the status of the External Synchronization Interface (ESI)
• “Y” in the Present, Oper, and Comm columns indicates that the ESI is present,
operational, and communicating
• “N” in the Present column indicates that the ESI is not present and no
additional status information is provided

Verify ESI LED Status Indicators
Dk06042602
LED Primary CP CP Status
Green (Solid) Powered

Power
Red (Solid) Not Powered
or Off
Off No Alarms
ESI
Alarm Red (Solid or In Alarm: POWER
Blinking) . GPS Antenna is Not Power
ALARM
Alarm
Connected to Cable STATUS
Status
. Shorted Circuit
. GPS Antenna is Not
Locked to Satellite EXT. CLOC
K
Status Red (Solid) . Not Operational GPS ANT.

. Cannot be Used
for Synchronization
Green (Solid) Operational
Orange
Standby Mode
(Blinking)
Network synchronization ensures optimal transmission quality. Without accurate

synchronization, timing slips can occur, degrading overall system performance.
• Verify that the ESI is not in alarm

• Verify the number of GPS satellites detected (minimum three)
• Verify GPS timing reference source

Verify the E1 Link Performance Metrics
Select Interval Sample
Specify E1 Link Specify Number of Samples
Dk06042603
Click “Get”

Monitor tabs to verify that E1 link is operating without any errors or alarms.
• Select the 15-minute, 1-hour, or 24-hour interval sample to specify the duration
for collecting the E1 link performance metrics
• Click the Get button to retrieve the E1 link performance metrics

Verify the E1 Link Performance Metrics
RX Mechanism Far End

Elastic Store Slips Block Errors
TX Mechanism
Elastic Store Slips
Dk06042604
• Verify if the selected E1 link indicates any errors, slips, or other problems to
determine if E1 link synchronization problems can be affecting fax or modem
performance
— It may not always be possible to detect E1 synchronization slips during
voice calls, since only a small amount of noise or clicking sounds may be
audible; however, fax or modem connections can be severely impacted

Review – Q & A
• Voice communication interruptions
• Noise on voice line
• E1 synchronization slips

Module 5: Troubleshooting Data Services
Objectives
Duplex Mode Verification Between the Base Station and the Gateway . . . . . . 137
Duplex Mode Verification Between the Base Station and the Hub. . . . . . . . . . 147
Duplex Mode Verification Between the Base Station and the CPE . . . . . . . . . 151
Ethernet Cable Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Ethernet Connectivity Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
CPE IP Address Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Lesson 1: Duplex Mode Verification Between the Base Station and the Gateway Module 5: Troubleshooting
Lesson 1: Duplex Mode Verification Between the

Base Station and the Gateway
Symptom
• HSD service is operational; however, there are a lot of dropped packets
• Data rates are lower than expected in the uplink and downlink for all CPEs
communicating with a specific base station
• Ethernet link errors are reported by the customer supplied router or base
station
Probable Cause
Mismatched duplex setting between the base station and the gateway.
Procedures
“Verify CPE Downlink and Uplink Data Rates” on page 138
“Verify Ethernet Link Status” on page 141
“Verify the Base Station Duplex Mode Setting” on page 144
“Verify the Gateway Duplex Mode Setting” on page 145

Module 5: Troubleshooting Data Services Lesson 1: Duplex Mode Verification Between the Base Station and the
Verify CPE Downlink and Uplink Data Rates
Dk06050401
Select the CPE
or Sector Option
Click Add to Test
CPE or Sector
Specify Time
Interval for Data
Traffic Updates
From LCID, click the System Status>HSD TL (High-speed Data Transport Layer)
tabs to verify downlink and uplink data rates of selected CPEs or sectors.
• Click the CPE or Sector option, then scroll to select a specific CPE or sector
— CPE option displays the metrics for the selected CPEs
— Sector option displays the metrics for the selected sectors
• Click the Add button to include each selected CPE or sector for a specific base
station in the CPE ID/Sector ID list

Dk06050402
Select the CPE
or Sector ID
Click Start
• Select the CPE ID or Sector ID, and then click the Start button to collect the
data for a specific base station
— More than one CPE or sector can be added into the CPE ID/Sector ID list
— Select the CPE ID or Sector ID from the list to collect the data for the
specified CPEs or sectors

Dk06050403
Select the Uplink and Downlink
Data Rates for the CPE or Sector
• Click the Downlink Scale tab, then scroll to select the downlink data rate
• Click the Uplink Scale tab, then scroll to select the uplink data rate
• Open a File Transfer Protocol (FTP) session to verify if the achievable CPE
data rates are below the expected uplink and downlink rates for a specific base
station
• Click the Stop button to end the data collection
• Click the Reset button to reset the interface to the default settings

Verify Ethernet Link Status
Dk06050404
Select
BCP1S
Select function
fcc_eth_drv_info Click Call Button
From LCID, click the Development>App Call tabs to verify if any Ethernet link
errors are reported by the customer supplied gateway or base station.
• Select each BCP2 slave CP; for example, BCP1S

• Select the “fcc_eth_drv_info” app call from the list
• Click the Call button to run the “fcc_eth_drv_info” app call
— Ethernet link status can be verified by displaying the BCP2 100Base-T
Ethernet interface statistics


Transmitted Frames Received Frames
Dk06050405
HSD performance can be affected by factors, including incorrectly configured

Ethernet parameters or defective cables, switches, and router interface modules.
• Percentage of frames transmitted with errors can be determined by checking

the difference between the “attempts” and the “error_free_transmissions”
— Standard Ethernet transmit error counts are listed, including “carrier_lost”
and “retries_exceeded”
• Percentage of frames received with errors can be determined by checking the
difference between “received_frames” and “error_free_frames_received”
— Standard Ethernet received error counts are listed, including “crc_error”
and “short_frame”

Dk06050406
Click Call Button
• Set in the cell for Param1: “0x03” to clear the statistics for the BCP2 Ethernet
link

Verify the Base Station Duplex Mode Setting
Enable or Disable
10 or 100Base-T
Half or Full Duplex
Dk06050201
From LCID, click the Configuration>Base Configuration>Network
Configuration tabs to verify the BCP2 Ethernet link settings at the base station.
• Verify if the Auto Negotiation is enabled over the BCP2 Ethernet link
— Auto Negotiation allows the base station and the gateway (switch or router)
to agree on the duplex mode settings configured at the both ends of the
Ethernet link to ensure interoperability
— Duplex mode is not a selectable option when Auto Negotiation is enabled

Verify the Gateway Duplex Mode Setting

• Verify that the gateway (switch or router) is powered
• Connect the gateway to a PC running HyperTerminal emulation software
• Verify that the gateway’s Ethernet link settings are identical to the setting
configured at the base station
— Auto Negotiation works only if enabled at both sides of the Ethernet link
– Mismatched Ethernet link settings can result in packet loss and severely
decreased performance; for example, if one side uses full-duplex mode
and the other uses Auto Negotiation

Lesson 2: Duplex Mode Verification Between the Base Station and the Hub Module 5: Troubleshooting

Base Station and the Hub
Symptom
• HSD service is operational; however, data rates are lower than expected for all
CPEs communicating with a specific base station
• Ethernet link errors are reported by the customer supplied hub or base station
Probable Cause
Base station is connected to the DSN over a hub that does not support full-duplex
mode.
Procedures
“Verify the Hub Duplex Mode Setting” on page 148

Verify the Hub Duplex Mode Setting

Data In Hub
Dk06050801
Data Out
A B C D
• Verify the Ethernet link settings between the base station and DSN, since
older networks may still connect the base station to the DSN over a hub
— Hubs provide centralized connection points for network access, connecting
multiple PCs together to make a single segment that shares the Ethernet
LAN resources
– A hub receiving a packet from a PC, transmits the packet to all other
PCs on the network; for example, a packet sent from computer A to
computer B, is sent to all other PCs on the network
• Hubs typically operate in half-duplex mode; therefore, data cannot be
transmitted and received simultaneously; only one PC can successfully
transmit at a time
— PCs are also not able to detect other traffic while transmitting, if two or
more PCs on the network try to transmit simultaneously collisions occur

Lesson 2: Duplex Mode Verification Between the Base Station and the Hub Module 5: Troubleshooting
Verify the Hub Duplex Mode Setting

Data In Hub
Dk06050802
Singal 1
Singal 2
A B C D
Signal 1 Collision Signal 2
• Since all incoming and outgoing data traffic is routed through the hub,
collisions can occur when two or more PCs try to send data simultaneously,
• Hubs use Collision Sense Multiple Access/Collision Detection (CSMA/CD) so
that when a collision occurs, each PC has to wait a random length of time
before resending its data
— As a network get busier, more collisions can occur resulting in rapid
Ethernet degradation as the number of PCs increase on the network
• Since hubs use CSMA/CD and operate in half-duplex mode, full-duplex
Ethernet traffic cannot be routed through a hub; as a result, hubs are not
recommended for base station Ethernet backhaul traffic

Lesson 3: Duplex Mode Verification Between the Base Station and the CPE Module 5: Troubleshooting

Base Station and the CPE
Symptom
• HSD performance is lower than expected for a specific CPE, despite good
airlink communication and no congestion (no excessive traffic in the sector)
• Subscriber PC or CPE is reporting link errors
• Subscriber PC is configured for full-duplex mode
Probable Cause
CPEs (R4) supporting a 10Base-T Ethernet interface may be configured to
operate only in half-duplex mode.
Procedures
“Verify CPE RF Link Status” on page 152
“Verify the PC Ethernet Link Settings” on page 153
“Verify the CPE Ethernet Link Settings” on page 155

Verify CPE RF Link Status
01
09
05
06
RF Link Status
Dk
• Operational CPEs indicate solid green for the power and RF link LEDs, as well
as a flashing green for the SQI LED
• Verify the CPE’s RF Link Status LED:
— If flashing red, the CPE is not synchronized with the base station
— If flashing orange the CPE has achieved downlink synchronization with the
base station and is receiving broadcast messages from the base station
— If flashing green CPE has established basic communication with the base
station in the uplink and downlink, and is awaiting configuration information
from the base station

Verify the PC Ethernet Link Settings
Dk06050902
To access the LAN connection settings configured for the subscriber PC:
• Click Start>Settings> Network and Dial-up Connections

• Right-click on Local Area Connection, then select the Properties

Verify the PC Ethernet Link Settings
Dk06050903
• Click the Configure button, then the Advanced tab

• From the Property list, select Media Type to verify the configured PC Ethernet
settings

Verify the CPE Ethernet Link Settings

YYMMDD Revision
Dk06050904
• Locate the date on the label to determine if the CPE is configured for
half-duplex or full-duplex
— CPE releases from April 2005 or later operate in half-duplex mode
— CPE releases from June 2006 or later operate in either half-duplex or
full-duplex mode
• Verify that the Ethernet settings between the PC and CPE match

Lesson 4: Ethernet Cable Verification Module 5: Troubleshooting Data Services
Lesson 4: Ethernet Cable Verification
Symptom
• All CPEs serving a single base station cannot receive or transmit data
• A specific CPE cannot receive or transmit data
Probable Cause
• Wrong Ethernet cable is used or Ethernet cable connection is not secured
• BOB unit is not wired correctly
Procedures
“Verify CPE RF Link Status” on page 152
“Verify the Ethernet Cable Connections” on page 158
“Verify the BOB Connections” on page 123

Module 5: Troubleshooting Data Services Lesson 4: Ethernet Cable Verification
Verify the Ethernet Cable Connections

• Verify that the correct Ethernet cable types are used to connect the
SYMMETRY ABS4000 equipment to the data networking equipment for the
efficient transport data traffic
— ABS4000 Base Station uses the following Ethernet cables:
– Straight-through Ethernet cables (RJ-45) to connect to switches or hubs
– Crossover Ethernet cables (RJ-45) to connect to routers
— SYMMETRY ABS4000 CPEs, such as the SSU4000 and SSU4400, use
the following Ethernet cables
– Straight-through Ethernet cable (RJ-45) to connect to PCs or switches
• TIA/EIA 586-B standard defines the pin assignment using Unshielded Twisted
Pair (UTP) cable and RJ-45 connectors for Ethernet connectivity
f TIA/EIA-568-A standard, which was approved in 1995, was replaced by the

TIA 568-B standard in 2002

Lesson 4: Ethernet Cable Verification Module 5: Troubleshooting Data Services

Straight-Through Ethernet Cable
Base Station (RJ-45) Switch or Hub (RJ-45)
1 (TX+) 1 (RX+)
2 (TX-) 2 (RX-)
3 (RX+) 3 (TX+)
4 (Not Used) 4 (Not Used)

6 (RX-) 6 (TX-)
• Straight-through cables are identical at both ends

• Straight-through cables are used as patch cords in Ethernet connections
• Odd numbered pins are striped and even numbered pins are a solid colour
• Ethernet cables should not be bent, stretched, or stapled
• Ethernet cables should not run parallel with power cables or near noise
inducing components

Module 5: Troubleshooting Data Services Lesson 4: Ethernet Cable Verification

Crossover Ethernet Cable
Base Station (RJ-45) Router (RJ-45)
1 (TX+) 1 (TX+)
2 (TX-) 2 (TX-)
3 (RX+) 3 (RX+)

6 (RX-) 6 (RX-)
• Crossover Ethernet cables are different at each end

• Crossover Ethernet cables are used to connect two Ethernet devices without a
hub
• Crossover Ethernet cables’ TX (transmitter) pins connect to the corresponding
RX (receiver) pins, positive to positive and negative to negative
• Odd numbered pins are striped and even numbered pins are a solid colour
• Ethernet cables should not be bent, stretched, or stapled
• Ethernet cables should not run parallel with power cables or near noise
inducing components

Lesson 5: Ethernet Connectivity Verification Module 5: Troubleshooting Data Services
Lesson 5: Ethernet Connectivity Verification
Symptom
• Base station cannot reach the next hop uplink destination IP address
• CPE cannot reach the next hop downlink destination IP address
Probable Cause
• Destination IP address is not on the same LAN (subnet) specified for the base
station (host)
• Destination IP address is not mapped in the Address Resolution Protocol
(ARP) table
Procedures
“Verify Ethernet Backhaul Connectivity” on page 162
“Verify the Next Hop Uplink Destination” on page 163
“Verify the Next Hop Downlink Destination” on page 164
“Display Active PPPoE Sessions” on page 165

Module 5: Troubleshooting Data Services Lesson 5: Ethernet Connectivity Verification
Verify Ethernet Backhaul Connectivity

IP Network Configuration on Two Different Ethernet Segments
A C
Network 192.168.1.X
Network 192.168.0.X
192.168.0.A 192.168.1.C
192.168.0.R
IP Router
192.168.1.R
B D
Dk06051701
192.168.0.B 192.168.1.D
• Base stations use the ARP to find the CPE Ethernet addresses when sending
a packet to a CPE for the first time or trying to reach a CPE on different LAN
— ARP keeps a table of Ethernet addresses and corresponding IP addresses
— Base stations only know the CPE IP addresses; therefore, if an Ethernet
address is not in the ARP table, an ARP request is broadcasted over the
network to obtain the physical hardware address corresponding to CPE’s
IP address, the CPE then responds with its Ethernet address

Verify the Next Hop Uplink Destination
Select function Select BCP

ethb_arp_app_call
Click Call Button
Dk06051702
From LCID, click the Development>App Call tabs to resolve the next hop uplink
destination using an ARP table for non-PPPoE traffic.
• Select the BCP2 CP from the list; for example, BCP1S

• Select the “ethb_arp_app_call” from the list
• Set in the cell for Param1: “0x01”, then click the Call button to run the
“ethb_arp_app_call” to view the BCP2 100Base-T interface ARP table
— Base stations use ARP tables to resolve the next hop uplink destination
– If ARP is resolved, IP and corresponding MAC addresses are displayed
– If ARP cannot be resolved, instead of a valid MAC address
“NOT RESOLVED” is displayed

Verify the Next Hop Downlink Destination
Select function Select CPE

adt_net_arp_cache
_show
Click Call Button
Dk06051703
From LCID, click the Development>App Call tabs to resolve the next hop
downlink destination using an ARP table for non-PPPoE traffic.
• Select the specific CPE from the list; for example, SSU4000 or SSU4400
• Select the “adt_net_arp_cache_show” app call from the list
• Click the Call button to run the “adt_net_arp_cache_show” app call
— CPEs use ARP tables to resolve the next hop downlink destination
– If ARP is resolved, IP addresses and resolved MAC addresses are
displayed
– If ARP cannot be resolved, a MAC address of 0:0:0:0:0:0 is displayed

Display Active PPPoE Sessions
Select BCP
Select function
ethb_pppoe_app_
call Click Call Button
Dk06051705
From LCID, click the Development>App Call tabs to display lists of active PPPoE
sessions using the BCP2 app call.
• Select the BCP2 from the list; for example, BCP1S

• Select the “ethb_pppoe_app_call” from the list
• Click the Call button to run the “ethb_pppoe_app_call”
— All active PPPoE access concentrators (AC) are listed

Display Active PPPoE Sessions

Change Setting for “Param1” from “0x02” to “0x03
Click Call Button
1704
• List all active PPPoE sessions:
— From the BCP2 app call “ethb_pppoe_app_call”, change the setting in the
cell for “Param1” from “0x02” to “0x03”
— Click the Call button to run the “ethb_pppoe_app_call”
– All active PPPoE sessions for the access concentrator index specified by
Param1: “0x02” are listed

Lesson 6: CPE IP Address Verification Module 5: Troubleshooting Data Services
Lesson 6: CPE IP Address Verification
Symptom
• CPE connected to a PC reports a duplicate IP address on the LAN (subnet)
• Multiple CPEs or subscribers for a single base station report duplicate IP
addresses on the LAN
Probable Cause
DSN network IP address settings specified at the base station are overlapping the
CPE IP address range.
Procedures
“Verify the DSN Network Configuration” on page 168
“Verify the DSN IP Network Settings” on page 169

Module 5: Troubleshooting Data Services Lesson 6: CPE IP Address Verification
Verify the DSN Network Configuration
Enables Dynamic
Public IP Functions
Starting IP Address
DHCP Server IP DSN IP Address
for Assigning Private DSN Subnet Mask
IP Addresses
DHCP Server IP
for Assigning Public
IP Addresses
Dk06060701
From LCID, click the Configuration>Base Configuration>IP Configuration tabs
to verify the public IP settings for the DSN in the base station configuration.
• Address block 10.255.252.0/22 (10.255.252.0-10.255.255.255) is reserved for

DSN private network addressing
• Subscriber LANs use private addresses
• Use of the same private address space for the SYMMETRY control network
and the DSN management network is not recommended
— CPE private address spaces can be replicated in each Local Service Area;
however, the management networks require unique addresses

Lesson 6: CPE IP Address Verification Module 5: Troubleshooting Data Services
Verify the DSN IP Network Settings

10.240.0.3 10.240.0.5
255.240.0.0 255.240.0.0
10.255.252.3 GW 10.255.252.3 GW
Attached:
10.240.0.0/29
10.240.0.1
Dk06060702
10.240.0.0/29
CPE
Proxy-ARP for:
10.255.252.0/24
10.240.0.2 10.240.0.4 10.240.0.6

255.240.0.0 255.240.0.0 255.240.0.0
10.255.252.3 GW 10.255.252.3 GW 10.255.252.3 GW
• Each CPE is allocated a DHCP configured subnet with six useable private
addresses: one for the CPE Ethernet interface and five for the subscriber PC
and IP networking equipment
— DHCP server subnet mask assigned to the PC is designed to include the
DSN address space
• Subscriber-to-subscriber communication is transported through the DSN and
public network (CPE automatically blocks subscriber-to-subscriber
communication through the private network)
— CPEs provide a proxy ARP response for any address in the DSN address
space

Module 5: Troubleshooting Data Services Lesson 6: CPE IP Address Verification
Review – Q & A
• Duplex mode verification
• Ethernet cable connection verification
• Ethernet connectivity verification
• CPE IP Address Verification

Tier2 Symettry 3.5 WLL

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tier2 Symettry 3.5 WLL

Uploaded by

Copyright:

Available Formats

ABS4000 Tier II Troubleshooting

SR TELECOM, AIRSTAR, ANGEL, INSIGHT NMS, METROFLEX, METROPOL, SR500,

© 2006, SR Telecom Inc.

ii ABS4000 Tier II Troubleshooting Course

Module 1: Troubleshooting the Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Module 2: Troubleshooting the CPEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Module 3: Troubleshooting RF Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Module 4: Troubleshooting Telephony Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Module 5: Troubleshooting Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

ABS4000 Tier II Troubleshooting Course iii

Troubleshooting the CPE Startup Verification Duplex Mode Verification

BRU Alarm Verification CPE IP Address

ABS4000 Tier II Troubleshooting Course 3

SR Telecom Headquarters Location

SR Telecom™ headquarters in Montreal, Canada

• Over 500 employees

4 ABS4000 Tier II Troubleshooting Course

Tier Knowledge System Architecture

ABS4000 Tier II Troubleshooting Course 5

• Identify and isolate faults at the base station and CPEs

6 ABS4000 Tier II Troubleshooting Course

ABS4000 Tier II Troubleshooting Course 7

8 ABS4000 Tier II Troubleshooting Course

ABS4000 Tier II Troubleshooting Course 9

Class Hours Phones

Rest Rooms Smoking

10 ABS4000 Tier II Troubleshooting Course

SYMMETRY ABS4000 Tier II Troubleshooting

SYMMETRY ABS4000 Tier II Troubleshooting Overview

Symptom Probable Cause Procedure

• CP is not operational • CP is not loaded with a • Section “Verify the CP LED

ABS4000 Tier II Troubleshooting Course 11

SYMMETRY ABS4000 Tier II Troubleshooting Overview

Symptom Probable Cause Procedure

V5.2 network interface is • Transmission path • Section “Verify V5.2 Interface

12 ABS4000 Tier II Troubleshooting Course

SYMMETRY ABS4000 Tier II Troubleshooting Overview

Symptom Probable Cause Procedure

ABS4000 Tier II Troubleshooting Course 13

SYMMETRY ABS4000 Tier II Troubleshooting Overview

Symptom Probable Cause Procedure

14 ABS4000 Tier II Troubleshooting Course

SYMMETRY ABS4000 Tier II Troubleshooting Overview

Symptom Probable Cause Procedure

• Dropped calls • Low RSSI, airlink • Section “Run a Ping Test

ABS4000 Tier II Troubleshooting Course 15

SYMMETRY ABS4000 Tier II Troubleshooting Overview

Symptom Probable Cause Procedure

CPE encounters noise on • Airlink communication • Section “Verify Airlink Status”

16 ABS4000 Tier II Troubleshooting Course

SYMMETRY ABS4000 Tier II Troubleshooting Overview

Symptom Probable Cause Procedure

ABS4000 Tier II Troubleshooting Course 17

SYMMETRY ABS4000 Tier II Troubleshooting Overview

Symptom Probable Cause Procedure

• HSD service is The base station is • “Verify CPE Downlink and

18 ABS4000 Tier II Troubleshooting Course

SYMMETRY ABS4000 Tier II Troubleshooting Overview

Symptom Probable Cause Procedure

ABS4000 Tier II Troubleshooting Course 19

Module 1: Troubleshooting the Base Station

CP Software Reboot and Downloads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

SMP IP Address Modification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39