Troubleshooting

OneCommerce Int’l.
Corporation
My Sagittarius Place Bldg., 609 Calderon St., Addition Hills,
Mandaluyong City, Metro Manila, Philippines 1550
www.onecommerce.com.ph
Agenda
• Introduction/Type of faults • Loopbacks
• Radio link diagrams • Full Outdoor
• Full outdoor • Troubleshooting Diagrams
• Hybrid solutions (full outdoor + IDU for • Troubleshooting Procedure
TDM transport) • Hardware/RF Issues
• Fading
• Causes of Radio Link Failure • Interference
• Looping
• Faults and Alarms

• Performance Monitoring radio

• Troubleshooting a Link
• Performance Monitoring Ethernet • New Link
• examples
Services
• Working Link
• RMON • Examples
• Critical Alarms

2
Troubleshooting a Link
Following procedures describe the most common fault-situations.
• Important to find the root cause of the issue, for minimizing time for fault finding / downtime in a newly deployed or
existing link.

• Fault finding is based on: alarms, RSL, MSE and XPI values, event logs, performance monitoring and looping.

• Next procedures will provide guidance to isolate issues and some corrective actions to correct the failure, for most
scenarios, but not all.

• Fault-finding should be performed by skilled engineers, who truly understand the network and network elements.

• Before you start, you should have system-knowledge and familiarity with using GUI/EMS/CLI tools: looping,
alarms and PM logs.

• Some issues will be related to installation of RFU/PoE, antennas, Power/Data cables(Ethernet or AWG), connectors,
mediation devices & waveguides, water contamination, lightening, mechanical stress may give RFU or Data and
cable-problems.

• Sometimes it is difficult to find the reason for the problem since a faulty cable, connector, power supply and different
RFU-faults are giving exactly the same alarm-picture in GUI Manager.

• Normally when the link connection is lost, the alarm-information from the remote station is also lost.

• The next flow-charts will help you how to isolate the issue and perform the corrective actions.

3
Radio Link Diagrams

4
Full Outdoor Configuration
Ethernet Traffic RFU & Diplexer
1 1 1 0 0 0 1 1
Process the Digital Data from
customer, converts to
microwave and send the signal
to the antenna thru Mediation
device, Data are directly
modulated to RF (50Ω)
Diplexer defines the Frequency
sub-band and allowed channels
for the RFU
Mediation Device Mediation Device RFU & Diplexer Ethernet Traffic
1 1 0 0 0 1
Provide the coupling Provide the coupling Process Digital Data received from
between the RFU and between the Antenna and remote side, Process the RF signal,
Antenna, define the RFU, define the recovers the data sent thru
polarization of the polarization of the microwave and delivers the traffic
transmitted signal received signal to the customer.
Diplexer defines the frequency
sub-band and channels allowed to
work in.
Hybrid Configuration

Ethernet RFU & Mediation Mediation RFU & Ethernet

Diplexer Device Device Diplexer Traffic
1 1 1 0 0 0 1
Process the Digital Data Provide the coupling Provide the coupling Process the Digital Data 1 1 1 0 0 0 1 Ethernet &
Ethernet & from customer, converts between the RFU and between the RFU and from remote side, Process TDM Traffic
to microwave and send Antenna, define the Antenna, define the the microwave signal and
TDM Traffic
the signal to the antenna polarization of the polarization of the recovers the data send
thru Mediation device, transmitted signal transmitted signal thru microwave Deliver
Data are directly the traffic to the customer
modulated to RF (50Ω). Diplexer defines the Process the Digital Data from remote site,
Diplexer defines the frequency sub-band and In case of TDM Pseudowire traffic provide
Process the Digital Data from customer, Frequency sub-band and channels allowed to work. to the final customer native TDM traffic &
TDM native traffic is sent over the full allowed channels for the Ethernet traffic no RF connection is used
IP unit as Ethernet traffic while no RF RFU
connection is used
Causes of Radio Link Failure

7
Causes of Radio Link Failure
Antenna Misalignment

Antenna Assembly Antenna Loosened

or installation
Wrong Offset

Installation Quality Incorrect Assembly of Components

Cables Improper Grounding

Poor Waterproofing
Incorrect Radio
Wrong Assembly
Parameters
Wrong Equipment
Configuration Damaged Connectors
Wrong Traffic
Configuration Modulation, TX power
Causes of Radio
Link Failure External Interference
Interference

Inter-Channel interference
Propagation Issues Fading
Reflection Fading
Line Of Sight
Weather Fading

Multipath Fading
Hardware Failure
LOS not established
Equipment Failure
Power Supply
Near field obstructions
Issues
Fault and Alarms

9
General Unit Alarms & Indicators
• The IP-20C contains LEDs to indicate the status of the different
interfaces, and the unit itself as follows:
Electrical GbE RJ-45 OFF FULL BLINKING
GREEN LED E-GbE (RJ-45) DOWN UP UP + TRAFFIC
ORANGE LED E-GbE (RJ-45) 10Base-T 100 Base-T 1000Base-T

Optical GbE SFP OFF FULL BLINKING

GREEN LED O-GbE DOWN UP OPERATIONAL + TRAFFIC

Management FE Interface (RJ-45) LEDs OFF FULL BLINKING

GREEN LED FE RJ-45 DOWN UP UP+ TRAFFIC
ORANGE LED FE RJ-45 (if Protection) DOWN UP UP+ TRAFFIC

10
General Unit Alarms & Indicators cont.
Radio LEDs
• RSL Interface (BNC)
Status LED
• Intended for Alignment.
• Provides analog measurement of the Received Signal Level (RSL).
Radio LED
• Direct conversion between dB and VDC (i.e. 1.4 VDC= -40 dB).
Protection
• Source Sharing (TNC) LED
• IP-20C uses a TNC connector for source sharing (used in specific configuration as MIMO 4x4). This connector is
RSL (BNC)
marked EXT/REF.
OFF Green Yellow Red Source
RADIO LED Radio Off Power, Carriers UP Signal degradation Loss of Frame Sharing
(TNC)

OFF Green Yellow Red

STATUS LED No Power Power, No Alarms Minor Alarm Critical Alarm

OFF Green Yellow Red

PROTECTION LED Not Enabled Protection active Unit in Stand-by Alarm, No Cable

11
Current Alarms
• Current Alarms: a list of most severe active alarms on the system
• Includes some help: Probable Causes & Corrective Actions
• Each Alarm has a unique Alarms ID
• The alarm will show severity configured by user or default severity.
• Color Codes: SEVERITY COLOUR
Indeterminate White
Critical Dark Red
Major Light Red
Minor Gold
Warning Yellow
Info Grey
• Example - possible alarm for eth cable disconnected (Major)
Event Log
• Logs and shows max. 5000 lines of events.
• When Event 5001 occurs, the first (in time) event is erased and 5001 is
logged as #1 (the latest)

13
Editing Alarm – Alarm configuration
• For Any Alarm in the system it possible to change
• Add. Text Descriptor
• Severity

• Select alarm, Edit & a window is opened where you can change the alarm details. NMS will take
alarm severity from here

14
Performance Monitoring - Radio

15
Counters Radio PMs & Statistics
Performance Monitoring Data and statistics available in the IP-20C
Radio > PM & Statistics > Counters.
• Defective Block Counters: displays the number of blocks in which errors
were detected, larger the amount, the poorer the radio link quality.
Radio > PM & Statistics > Signal Level.
• Displaying Signal Level PMs: Received Signal Level PMs for the
interface are displayed.
Diversity RSL PMs per radio: Go to Radio > PM & Statistics > Diversity.
Combined RSL PMs per radio: Go to Radio > PM & Statistics > Combined.
• Displaying PMs for the IF Combining Diversity Interface and IF
Combining Signal: Displays IF Combining (only space diversity ) RSL
levels for 2 signals combined into a single optimized signal. Displays RSL
PMs measured at the Diversity interface, as well as RSL PMs for the
combined signal.
Go to Radio > PM & Statistics > Aggregate.
• Displaying Modem BER (Aggregate) PMs: Displays modem BER (Bit
Error Rate) PMs per radio:

16
Counters Radio PMs & Statistics
Performance Monitoring Data and statistics available in the IP-20C
Radio > PM & Statistics > MSE.
• Displaying Modem MSE PMs: Displays modem MSE (Minimum Square
Error) PMs per radio:
Radio > PM & Statistics > XPI.
• Displaying XPI PMs: Displays XPI (Cross Polarization Interface) PMs per
radio:
Go to Radio > PM & Statistics > MRMC.
• Displaying MRMC PMs: Displays MRMC PMs, including ACM profile
fluctuations per interval per radio:
Radio > PM & Statistics > Traffic.
• Displaying Capacity and Throughput PMs: Displays capacity and
throughput for a radio, on:
• Layer 1 bandwidth (payload plus overheads) sent through the radio (Mbps).
• Effective Layer 2 traffic sent through the radio.
• Utilization of the link: displays % of link utilization through traffic
• Frame error rates: Displays the frame error rate (%)

17
Radio Parameters – Defective Blocks
• User can see the defective blocks under radio parameters

• Detailed view of the Defective Blocks in PM Statistics/Counters for Radio

IP-20C Counters
• Defective Block Counters
• The Counters page displays the number of blocks in which
errors were detected. The larger the amount, the poorer
the radio link quality.
•
To display the number of blocks in which errors were
detected per radio:
• Select Radio > PM & Statistics > Counters. The
Counters page opens.
Signal Level PMs
• Available per interface, 24 hours or 15 minutes intervals

• Configurable thresholds, shows time when radio was outside defined threshold (seconds).
• RSL (2 RSL thresholds)
• TSL (1 TSL threshold)

20
Aggregate PMs
The Aggregate page displays modem BER (Bit Error Ratio) counted as ES (errored seconds), SES (Severely
errored seconds), UAS (Unavailable seconds) and BBE (Background Block Errors) measurements.
• 15 in or 24 hrs. Interval
• Detailed view of the interval
MSE – Mean Square Error Report
• Interval of 24 hrs. or 15 minutes.
• Configurable Threshold exceeding (seconds)
Radio Parameters
• These example values are typical and subject to change in relation to the
frequency, bandwidth and RFU type.

Profile Mod MSE Down-Threshold MSE Up-Threshold

0 QPSK -18
1 8PSK -16 -19
2 16QAM -17 -23
3 32QAM -21 -26
4 64QAM -24 -29
5 128QAM -27 -32
6 256QAM -30 -34
7 512QAM -32 -37
8 1024 QAM SFEC -35 -38
9 1024 QAM WFEC -36 -41
10 2048QAM -39
XPI Level Report for XPIC
• Users can see the level of Cross Polarization Interference for CCDP systems.
• Threshold time also available
• 15 in or 24 hrs. Interval
• Detailed view of the interval
MRMC Statistics
Shows the MRMC PM including information related to the ACM profile fluctuations in the selected time period.
• 15 in or 24 hrs. Interval
• Detailed view of the interval includes Maximum and Minimum working profiles per radio carrier.
• Graphic view available
• To display Multi-Rate Multi-Constellation PMs, Select: Radio > PM & Statistics > MRMC.

25
MRMC actual status
• User can see the Actual
modulation and capacity
of the radio
• Detailed view of the
configuration and actual
capacity/modulation is
provided
Capacity PMs

• Available per carrier or per MC-ABC group, exampled below.

Capacity & Throughput PMs
• You can display PMs for capacity and throughput for a radio, based on Layer 1 bandwidth (payload plus overheads) sent through
the radio (Mbps) and total effective Layer 2 traffic sent through the radio.
• Possible to configure thresholds for capacity and throughput PMs. The number of seconds during which these thresholds are
exceeded are among the displayed PMs.
Utilization PMs
The Utilization PM report page displays radio capacity utilization PMs.
• 15 min or 24 hrs. Interval, Utilization Threshold configurable

• To display radio capacity utilization PMs: Radio > PM & Statistics > Traffic > Utilization. The Utilization PM Report page opens.

• Peak Utilization (%) Indicates the highest utilization of the radio capacity that occurred during the measured time interval.

• Average Utilization (%)Indicates the average utilization of the radio capacity during the measured time interval.

29
Frame error rate
• Framing errors are the number of packets received with an invalid frame checksum (FCS).
• Displays the Frame Error Rate in percentage during the measured time interval
Performance Monitoring – Ethernet Services
ETH PM – Remote Network Monitoring - RMON
• Remote Network MONitoring
• Industry Standard Monitoring tool
PM – RMON – Special Registers
RMON register / Counter Description

Undersize frames received Frames shorter than 64 bytes

Oversize frames received Frames longer than 2000 bytes

Total frames received with a length of more than 2000 bytes, but with an invalid
Jabber frames received
FCS
Total frames received with a length of less than 64
Fragments frames received
bytes, and an invalid FCS
Rx error frames received Total frames received with Phy-error
Total frames received with CRC error, not countered in
FCS frames received
"Fragments", "Jabber" or "Rx error" counters

Pause frames received Number of flow-control pause frames received

Troubleshooting with RMON: Oversized frames

• When ingress frames exceed the maximum frame size, RMON counter “Oversized
frames received” is updated accordingly

Site A Site B

T T T A

Tagged Frames with frame

size > 1522 bytes
Troubleshooting with RMON: Discarding Example

• Discarding Examples:
• Ingress rate > Rate Limiter
• Ingress frames do not qualify to Policer rules

Site A Site B

T T T A

Ingress traffic does not

comply to Policer rules
Troubleshooting with RMON: Monitoring traffic types
• Video streams are generally transmitted over UDP with multicast addresses
• To monitor traffic, check out the Multicast Frames Received register
• To limit MC traffic, assign a Policer with a MC CIR rules

Site A Site B

Rate Limiter
T T

Monitor
Egress CoS Statistics
• Available Per Port and bundle ID
• Detailed view per port
Ethernet Port Tx and RX PM Report
• User needs to Enable the PM Port Reporting per each interface
• Available for Tx and Rx
• 15 min or 24 hrs
• Detailed view per port
Loopbacks
Loopback in general
• The loopback is an on-demand testing mechanism.
• Used to verify connectivity from a specific point to certain Maintenance Point.
• IP 20 supports Radio and Ethernet loopbacks, physical and logical loopbacks.
• Feed-back received depends on type of loopback and platform
• Very useful tool for first-hand Troubleshooting.
Full Outdoor Platform

41
Radio Loopback Outdoor
• RF loopback can be set for up to
1440 minutes = 24 hrs

IP-20C IP-20C
• RF loopback will raise an alarm

Loopback from this IP-20C, over

under Current Alarms
the Radio Interface and Back:
Tx to Rx

Do you hear me?

Do I hear me?
Radio loopback configuration IP-20C
• Radio>Diagnostics>Loopback
• Loopback activation will generate one
alarm
• Loopback can be found also in the
Event Log
• Radio LED is Green when loopback
alarm is on.
• You can see results under the Radio
Parameters.
Radio loopback results
• You can see results under the Radio Parameters.
• If RSL and MSE are looking good, this transducer and
the whole way to it, are operational.
• Radio LED is Green when loopback alarm is on.

• Loopback will be found in the Event Log

44
What to expect in Radio Loopback results
• RF loopback acts as if the Rx would be on the same Frequency as your Tx, for the
activation period
• RSL value: RSL value is dependent on the Tx Power and any changes performed
in Tx Power should be observed in received signal level (ie, increasing 5dB Tx
should also increase RSL with 5dB)
• RSL value read on loopback can varies between RFUs, but expect to receive
RSL=Tx Power - 70dB (with a margin of +-10dB)
• No Defective Blocks should observed (make sure counters are clear before starting
loopback, if needed reset counters.)
• MSE values should be within the range of the used modulation (Slide 22).

• If RSL and MSE are looking good, this transducer and the whole way to it, are
operational.

45
Ethernet Loopback IP-20C
• Eth loopbacks can be performed on any
logical interface, apart from management.

IP-20C • Eth loopbacks all frames ingressing.

IP-20C

• Eth loopbacks can be configured on

Loopback from Test
Equipment to IP-20C multiple interfaces simultaneously.
Ethernet Interface
• Up to 15 minutes, 900 Seconds
Do you hear me?
• The interface can be configured to swap
Do I hear me?
DA and SA MAC addresses during the
loopback (if MSTP or LLDP enabled).
Ethernet loopback configuration
• Under Ethernet >Logical
Interfaces
• Eth. Loopback does not trigger an
alarm
• With in-band management, Eth
loopback on remote side causes
loss of management to remote.
• The duration period of the
loopback should take this into
account
Troubleshooting Diagrams

48
Troubleshooting procedure Co-Channel or adjacent channel
interference
Analyze RSL & MSE PM
compared with current values
Long delay caused by terrain reflection
START RSL higher than Receiver yes
sensitivity Interference
No
yes Long delay caused by terrain reflection
Yes RSL higher than Designed
Is there a wrong value?
Reconfigure Radio Link
configuration? No Misalignment
No yes
RSL always lower than
designed value Wrong antenna offset
Yes
HW alarms are No
Refer to HW Diagram
present? Passive components like OMT, Splitter,
No couplers or flex WG faulty
Did it rain when the fault
yes
occurred Water leak inside antenna Feeder or
RF Alarms are Yes No waveguide
present? yes
TX or remote ODU or local RX might be
No The fault appears repeatedly
faulty (Perform RF loops)
No
Troubleshoot the link by Rain fading (weather fading)
Troubleshoot the
replacing suspected faulty parts
Issue as a non Multipath Fading
Radio Link Fault No

No Is the fault Resolved? Terrain reflections

Yes
END

49
Troubleshooting Hardware Diagram/RF Issues
Hardware Are there RFU active
No Low RSL/MSE or low TX
Diagram Alarms? power? Start
Yes Yes

No No
Is -48 VDC in Fuse Check Power
Is Traffic OK?
Panel? Supply
Yes Yes

IS -48 VDC present on

No Replace connector(s) and
RFU? or power Cable Go to End

Yes
No
Is traffic OK?
Perform a Yes
Loopback test

Go to End
Loopback results Yes Continue Troubleshooting
Go to End
are OK? In remote station
No

Replace RFU END

50
Fault Finding: Rx Level
START

No No
Are RF input warning on both stations (local/remote)? Is there RF input warning on one side of the Link?
Yes yes
No
Is antenna proper aligned? Check that Tx power and RX level warnings settings are
equal on both terminals
Yes

Fading or damage or water leak in antenna, adapter or flex Adjust Antenna alignment
waveguide on either side of the link

Is RF-LOS alarm on local and remote stations? usually No Is RF-LOS alarm on one side of the Link? usually followed No
followed by HBER, LBER, EW alarms by HBER, LBER, EW alarms
Yes Yes
Go to End

Perform corrective maintenance following Hardware diagram

Probably equipment fault, Perform a Loop test/ go to loop
explanation for test
No
Is Rx level OK?
Yes
No Probably equipment fault, go to Loop diagram/loop
Is Traffic OK?
explanation for test
Yes

END
Fault Finding: Nominal Rx Level
START

Traffic interruption

No
Are Rx levels OK?
Use Rx Level Diagram Go to End
Yes

Verify the event log to locate which terminal is presenting the

issues and use Diagram loop or Loop explanation for test

Are configuration and SW versions correct?, use GUI for No Correct the configuration and load correct SW version if is
review the SW version and configuration needed (reefer to release notes for compatibility)
Yes

Check the alarms in GUI/RFU (LED status)

Yes
Is Traffic OK? Go to End
No
Verify port status and if needed
replace Faulty Hardware
No
yesOK?
Is Traffic
Yes
END
Configuration issue when you have different profiles and one unit try to switch to higher profile
Fault Finding Interference or Fading procedure
Link down or bad Yes
Does it rain, Is storm Wait till weather
performance
in the area? improve
No

Link frequency is above Yes Yes

Atmospheric fading Is traffic ok?
11GHz?
No No
END
Perform interference
Path fading test Yes
Is traffic ok?
No
Yes
Are there water Resurvey the path.
reflections, sand, glass? Planning issue With remote TX Yes Troubleshoot the issue as
No muted, local RSL is a non radio link fault
less -90 dBm?
Yes No Co-channel interference
Does link has space
diversity?
No Yes Adjacent channel
Link affected by interference
interference

Multi-path issue Intersymbol interference

Signal Fading approach
Types and causes
• Fading in a radio link can drastically affect the RF performance. Often caused by multipath conditions, fading is much
difficult to be located and to deal with it than the hardware failure.

Fading types Phenomena description Fading cause

· Multi-path fading
Down The RSL is lower than the nominal RSL when fading. The difference
· Duct-type fading
Fading effects on fading can be tens of dBs.
· Rain fading
RSL
Up The RSL is higher than the calculated or nominal RSL in the free · Interference
fading space. The difference can be more than 10 decibels. · Long delay caused by terrain reflection

The fading lasts from several milliseconds to tens of seconds.

Generally, fast fading is caused by multipath fading. It occurs · Multi-path fading
Fast
periodically. Usually, fast fading occurs in the time of the day were · Duct-type fading
fading
weather conditions changes (period from 06:00 to 09:00 or 18:00 · Long delay caused by terrain reflection
to 21:00 of a day) or in a certain season of a year.
Fading Duration
· Generally, slow up fading is caused by interference.
· Slow down fading is caused by rain, and therefore is also
Slow
The fading lasts from tens of seconds to several hours. called rain fading.
fading
Rain fading Mainly occurs on links working at a frequency of
10GHz and up or in areas where heavy rain occurs.

54
Fading solutions
• Fading: If RSL varies in amplitude quickly (more than 10 dB to dozens of dBs over seconds), or fluctuates periodically (i.e, always at midnight), the fault may be caused by
terrain reflection. Are there rivers or large bodies of waters, lakes on the propagation path?
• ACTION: If excessive reflection exists, adjust the antenna height to change the path angle to reduce the impact of the reflection, or replan the propagation path (Temporary
solution can be to tilt up the remote antenna until change the nominal RSL around 4 dB).

• Multipath Fading: If a radio link fault occurred in bad weather conditions (such as rainy, snowy, or foggy) and was recovered after the conditions disappeared, the fault
cause was weather fading. For a fault caused by weather fading, check whether the link fading margin is insufficient.
Before re-planning a radio link, check whether the rain zone parameters, the refractivity gradient, and the planning algorithm are incorrect. The practicable measure could be
as follows:
 Increase the transmit power or replace the original antenna with a new one having a larger diameter to increase the system gain and the fading margin
 Use a frequency band on which rain fading has smaller impacts (Frequencies lower than 11 GHz).
If the RSL varies greatly and fast (by more than 10 dB or several 10 dB within several seconds or several 10 seconds), fast fading occurs.
Fast fading may occur due to:
 Multi-path fading: Faults occur periodically, for example, at the day-and-night alternating time period (Between 06:00 to 09:00 and 18:00 to 21:00 hrs.).
 Duct-type fading: random fast fading, Usually levels during commissioning are better than the calculated RSL level.
To handle fast fading, proceed as follows:
 Increase the path angle: that is, adjust the antenna mount heights at both ends to increase the height differences between the antennas at both ends.
 Reduce surface reflection. For apparent strong reflection surfaces, for example, large areas of water, flat lands, and bold mountain tops, adjust antennas to move reflection
points out of the strong reflection areas (Tilt up remote antenna until decrease the RSL around 4 dB) or mask the reflection by using landforms.
 Reduce the path clearance. With LOS conditions guaranteed, lower antenna mount at higher heights as much as possible.
Multipath
• When Min & Max RSL signals rise and fall together, Both signal create an “envelope” of X dB
• These symptoms are a clear evidence of Multipath
• Space Diversity should be considered to eliminate the multipath impact on RSL
Interference
• If the RSL varies within a range of less than 10 dB, mute the opposite ODU and check the RSL at the local
side. After the remote ODU is muted, if the RSL value is greater than -90 dBm, there may be external
fading in 1+0 links or also co-channel interference in 2+0 links that affects long-term availability and error-
second performance of the link.
In order to identify external interferences (foreign), use a frequency spectrum analyzer to locate the
possible interfering frequencies. If interference is caused due to improper frequency settings, modify the
frequency plan to minimize the interference impacts.
If the RSL varies in amplitude and quickly (from more than ten dBs to dozens of dBs over seconds), or
fluctuates periodically (for example, always at midnight), the fault may be caused by terrain reflection.
Check whether there are rivers or lakes on the propagation path.

• If excessive reflection exists, adjust the antenna height to change the path angle to reduce the impact of
the reflection, or replan the propagation path.

56
Fault Finding by Looping Outdoor Config.
START

No Use RX block diagrams

Traffic issues?
Yes
No
Do you have alarms In the local site? Check remote Terminal Go to End
Yes
Yes
No
Make a near end Eth loopback Use other block diagram Is Traffic OK?

No Verify connections No
IS traffic OK? Is Traffic OK? Verify Ethernet Cable
and LED status
Yes
Yes
Go to End
Make a RFU Loopback

No Yes Verify looping and

Is Traffic OK? Check/replace RFU Is Traffic OK? use same procedure
No on remote station
Yes

END
Possible fault in RFU
go to HW diagram
Troubleshooting a New Link

58
Troubleshooting a New Link
• Fault Finding: When dealing with many type of alarms and performance events on a Link, first analyze the radio related alarms, RSL, MSE, XPI and
PMs continue with the errors generated by the line processing unit in the same service, continue with the alarms generated by physical
connections/Location (Power or UTP cables).

• Isolate the Problem

1) If RSL has low level, verify the antenna alignment (value should be according to the Link Budget). If the RSL is good proceed with MSE, XPIs and PMs.

2) MSE should show a value according to the MRMC profile (see chart in slide 22), if value is -99.99 dB and good RSL, modulation mismatch is present.

3) If you fail to locate the fault by analyzing the alarms and performance events, perform loopback operations segment by segment.

4) If is a system with XPIC, verify the XPI values in both polarizations values should don’t have more that 2 dB of difference and should have a value no
less than 25 dB (This value varies according to the installed antenna).

5) Determine the XPI, by either of the following two methods:

1.- Measure the RSL of the second carrier (the “RSLunwanted”). To calculate the XPI, subtract RSLunwanted from the RSLwanted.
2.- Read the XPI from the Modem XPI field of the Radio Parameters page in the Web EMS.

6) The XPI should be at least 22 dB. If it is not, you should adjust the OMT assembly on the back of the antenna or feeder (Remote mount configuration)
at one side of the link until you achieve the highest XPI, which should be no less than 22 dB (depending of the antenna performance). Adjust the OMT
or feeder very slowly in a right-left direction. OMT or feeder adjustment requires very fine movements and it may take several minutes to achieve the
best possible XPI. It is recommended to achieve XPI levels at least 22 dB in both polarizations.

• Reminder: XPI values in both polarizations should not have a difference more than 2 dB

59
 Troubleshooting a Link – Checklist no.1
What to Check? Possible Reason and Corrective Action Mark

Antenna misalignment One or both antennas are incorrectly aligned. Make sure that the ATPC is disabled during alignment process.
√
Frequency mismatch Tx Frequency must exactly match the Rx frequency on the remote side
√
RFUs Frequency Tx high frequency set on High band RFU and Tx low frequency set on the Low band RFU?
mismatch For N+0 links => make sure you use in site A all RFU’s within the same Sub-band, Low or High.
√
Low + High on same site should NOT be used, unless Radio Planning teams create an exception.
Modulation Mismatch RSL is good, but the MSE is -99,99 dB?
Check MRMC scripts, do they match completely? Same number & operational mode profile.
√
RSL not good? Change MRMC profile to a lower modulation to (4 – 16 QAM) on both sides of the link and
observe the results. Check link for interference.
When commissioning a radio link, MSE should be smaller than -34dB(-35 to -43). High values than -18dB will
result in loss of signal.
High RSL?(-30,-29) Too strong Tx power could lead to high RSL (> -30dBm) and low MSE values due to link saturation: Reduce the
output TX power.
√
Mismatching antenna Given a typical polarization discrimination of 22 dB, for most links a mismatched polarization setting means it
polarization would not be possible to capture a signal to begin the antenna alignment process
√
Faulty equipment Either RFU or any other passive component (cable, waveguides, mediation devices, antenna), along the
transmission path might be faulty. If the RSL is still not good after the proper alignment was done and the MSE
√
is bad, either the local RX or remote TX are faulty. Start the Troubleshooting Guide
Do Loopback test; Perform a RF loopback. Clear RF counters. Check the defective blocks. If the RSL is too low
or the number of defective blocks increases, the RFU is faulty and needs replacement.

For Values of the RSL, please refer to the section “What to expect in Radio loopback results” 60
 Troubleshooting a Link – Checklist no.2
What to Check? Possible Reason and Corrective Action Mark

Interferences. Frequency In N+0 links check for frequency separation and channel bandwidth in order to avoid inter-channel
separation (N+0 ACCP): interferences. Mute one link or all except the one that is under tests; turn off the Tx in either ends of the link.
√
Check the RSL and the MSE. No interferences means good and stable
MSE values. In 2 x IP-20C Multicore, 2+0 (2 XPIC groups) swap the central frequency from the 1st channel
(XPIC group) to the 2nd channel (2nd XPIC group). If the fault stays stick with the frequency, there is an
external interference source.
Incorrect path If the RSLs are too low or too high, antenna alignment is correct, and Tx power settings are correct, check the
calculations path calculations used to determine the link performance. A good calculation match is +/- 2 dB. Differences in
√
excess of 3 dB should be investigated.
Reflections Reflection (path cancellation) problems may not have been picked up at the path planning stage, particularly if
the survey was a simple line-of-sight. If suspected, resurvey the path
√
Loopbacks Check if RF loopback is set on one of the RFUs; if RF loopbacks are present, remove them and verify the RSL.
If all the above actions cannot resolve the fault, replace the RFU at both ends. Then, check if services are
√
functional. If the fault persists, re-plan the radio link by changing the operating frequency, using antennas with a
larger diameter, changing the antenna heights, or changing the routes.
Interoperability with other Ensure that the radio system is functional from interoperability point of view. Check the Release Notes to find
products out if the radio units are interoperable across the link (for Ceragon radios)
√
Wrong port state Radio ports should be enabled on both sides of the link.
√

For Values of the RSL, please refer to the section “What to expect in Radio loopback results”
61
Troubleshooting a New Link, examples

62
Troubleshooting a New Link – Case Study 1
• Potential problems can also be caused by: Wrong port state or wrong settings, so the same Radio/Ethernet ports should be enabled on
both sides of the link.
• Ceragon IP20S installation: “Hi, for the last 3 days we have been installing 4 IP20S links in a system in the West part of our country. The
links are replacing AVIAT WTM3200 units, which were working before the Ceragon replacement. The system provides data connectivity
to SCADA equipment along the length of the microwave link equipment (see diagram) and especially provides connection from a
TETRA sever/switch located at the customer premises and 3 remotely located base stations along the length of the system.”

63
Troubleshooting a New Link – CS1 Resolution
• After installation of the links and confirmation of end to end connectivity across them we proceeded testing the TETRA radio system along the network. Network
uses VLAN 10 to provide connectivity between the TETRA Server & 3 remote base stations. Since installing the IP20S units we have lost connectivity between all
the devices. It appears that IP20S is not passing the VLAN through. We tried different configurations but so far have not been successful in fixing the issue.

• Below shows the current configuration of the first link in the system. Can you please look over our configuration and help us setup to pass all traffic?

Issue:
Mismatch in Eth services

• In a remote session we found that Ethernet service points on the unit connecting TETRA BS, should have been configured for eth Port 2, but the service was
created with Service Point on Ethernet port 1. Re-creating the pipe service between them, using eth Port 2 instead fixed the issue.

Solution:
Reconfigure the Eth services

64
Troubleshooting a New Link – Case Study 2
• Customer has IP-20C links, but they were not able to setup properly and we can't seem to work out why. Plan is to decommission the links and
do further testing in their office. Long links, on towers, so a costly task to remove and re-install. Ceragon offered assistance & analysis before
they decommission. The customer is naturally keen to see a resolution ASAP, they are paying for the channel license.

• Link Budget Details: Link length 17.9km; Expected RSL: -45.07 dB, with Ceragon IP-20C @ 7.5GHz with a 2ft Dish (site A) and a 3ft Dish
(Site B). Initially 1+0 (single core) at 500Mbps on Horizontal Polarization, future upgradeable to 2+0 at 1Gbps.

• Problem description: link is unable to achieve the desired RSL reading on site, despite several panning attempts. Summary of the customer
explanations follows:
1. Technicians team bench-tested the link beforehand using lots of attenuation between the dishes and saw around -70dBm RSL
2. After install they couldn't even see a glimpse of RSL either side (~-90dBm floor, is this the lower threshold?)
3. Own 1st level Engineers logged in remotely, made some changes to the config and recommended trying to re-pan.
4. Technicians went back to site to re-pan with no success.
5. Own 1st level Engineers remotely performed an RF loopback test to confirm there is a received signal into the receiver, positive results on
each end.
6. Customer compiled their own assembly manual so they could check correct installation of all components correctly: OMT, interface adaptor,
cables, etc.
7. Technicians team went back to site to check assembly and re-pan with no success
Last resort: bring 1 link back to the office and use spare radios to eliminate the possibility of any faulty equipment. Location & length of the link
makes this a costly task to go back to site each time.
Can Ceragon Support help us remotely and check the settings and logs ?
Troubleshooting a New Link, Examples
Remote troubleshooting and Workaround
Ceragon observed and corrected 2 configuration issues, first hand:
1. the frequencies pair was set incorrectly: the low Tx freq was set on the high Tx ODU and the high Tx freq was set on
the low Tx ODU. We changed frequencies in between them, but this doesn't match with regulations (Site A has the low
Tx and Site B has high Tx).
2. There was a MRMC profile mismatch (corrected). Even so, the link was still unable to be established. With RF loops,
the radio units acts normal, as not being faulty.
Analyzing the part numbers Ceragon observed that the set frequencies, are slightly (7MHz) outside the freq range of the
diplexor, for both units:
• 22-0543-0 - TX: 7671.5-7786.5 RX: 7426.5-7541.5
• 22-0544-0 - TX: 7426.5-7541.5 RX: 7671.5-7786.5
With a new pair of frequencies from these ranges, for test purposes, the link comes up with no issues, so either:
1. This is caused by heavy interference from other links running in the same area, within the same band.
2. Or there was something wrong on the frequencies from the regulator.
Customer’s response: Thank you VERY much for your prompt response and detailed report - I've managed to speak to
the engineering team and they're able to cancel the engineers’ visit and tests for Monday and assign other tasks, nothing
lost. Great news about the hardware. We can confirm by looking at the e-mails and the application form that regulator
gave us slightly different channels than requested. Good lesson learned for next time.
Troubleshooting an Installed Link

67
Troubleshooting an Installed Link
Following procedures describe the most common fault-situations.
• Important to find the root cause of the issue, for minimizing time for fault finding / downtime in a newly deployed or
existing link.

• Fault finding is based on: alarms, RSL, MSE and XPI values, event logs, performance monitoring and looping.

• Next procedures will provide guidance to isolate issues and some corrective actions to correct the failure, for most
scenarios, but not all.

• Fault-finding should be performed by skilled engineers, who truly understand the network and network elements.

• Before you start, you should have system-knowledge and familiarity with using GUI/EMS/CLI tools: looping, alarms
and PM logs.

• Some issues will be related to installation of RFU/PoE, antennas, Power/Data cables(Ethernet or AWG), connectors,
mediation devices & waveguides, water contamination, lightening, mechanical stress may give RFU or Data and cable-
problems.

• Sometimes it is difficult to find the reason for the problem since a faulty cable, connector, power supply and different RFU-
faults are giving exactly the same alarm-picture in GUI Manager.

• Normally when the link connection is lost, the alarm-information from the remote station is also lost.

• The next flow-charts will help you how to isolate the issue and perform the corrective actions.

68
Troubleshooting an Installed Link
Continuation
Define the symptom: this step is generally performed by the customer's field technician or supervisor. Example symptoms include “ODU alarm is
red”, “complete loss of service”, “excessive errors” and “RSL values”.

• Symptoms may be constant or intermittent. Constant symptoms require immediate troubleshooting attention. Intermittent symptoms may require
circuit monitoring or robust test procedures prior to troubleshooting.

Investigate & Isolate the Problem

• After you have a clear definition of the symptom, the malfunction can be isolated using diagnostics, loopback testing, fault isolation tables/flow
charts, test equipment, and manual procedures.
• This step will identify the specific piece of equipment that is producing the failure; Although it may be difficult at times to immediately determine
which part of a radio link is causing the fault, the initial suspicion should be focused on one of the following near-end or far-end issues:
• Power supplies.
• Fading (due to heavy rain, new obstacle in path, antenna misalignment)
• External equipment (CISCO/JUNIPER, Ethernet connection, etc.)
• PoE
• Radio Frequency Unit (RFU)
• Ethernet fiber/cable between the RFU and Router or external device
• Exposure of equipment to severe conditions (high temperature, etc.)
• System configuration
• Understand the Problem & Apply suggested workaround actions
Once the fault has been isolated, you will need to understand why the fault occurred and what is required to correct it. Use the tables and flow
charts provided in the following sections and the GUI EMS Manager to understand the problem and for suggestions of possible solutions.

69
Troubleshooting an Installed Link, examples

70
Troubleshooting an Installed Link
Examples
• If RSL has is low, verify antenna alignment (value according to the Link Budget). If the RSL is good proceed with MSE and XPIs.
• Monitor fading activity with RF statistic to decide if it is marginal design or equipment failure.

• MSE should show a value according to the MRMC profile, if value is -99.99 dB and good RSL, check for modulation mismatch.

• If you fail to locate the fault by analyzing the alarms and performance events, perform loopback operations segment by segment.

• If is a system with XPIC, verify the XPI values in both polarizations values should don’t have more that 2 dB of difference and should
have a value no less than 22 dB (This value varies according to the installed antenna).

• Determine the XPI, by either of the following two methods:

1. Measure the RSL of the second carrier (the “RSLunwanted”). To calculate the XPI, subtract RSLunwanted from the RSLwanted.
2. Read the XPI from the Modem XPI field of the Radio Parameters page in the Web EMS.

• The XPI should be at least 22 dB, otherwise adjust OMT assembly on the back of the antenna or feeder (Remote mount configuration)
on 1 side of the link until you achieve the highest XPI, which should be no less than 25 dB (depending of the antenna performance).

• Adjust the OMT or feeder very slowly in a right-left direction. OMT or feeder adjustment requires very fine movements and it may take
several minutes to achieve the best possible XPI. It is recommended to achieve XPI levels at least 22 dB in both polarizations.

Reminder: XPI values in both polarizations should not differ with more than 2 dB!

71
Troubleshooting an Installed Link
Unstable RSL
• Check current RSL & check changes in RSL during last 24hours (5dB change during the day is
normal)
• Identify rain fading, multi-path,
• Check if RSL reached sensitivity threshold
• In case you are using ATPC, check Transmit Signal Level
• If your link is installed in a construction area – look for a tower crane or obstructions:
• Construction Cranes have a free rotation in order to reduce the risk of damage due to wind.

• Intermittent drops in RSL values may reflect line of site interferences caused by the rotating crane

• You can configure RSL Threshold counters to get a better resolution of the problem!

72
Troubleshooting an Installed Link
Multipath
• When Min & Max RSL signals rise and fall together
• Both signal create an “envelope” of X dB
• These symptoms are a clear evidence of Multipath
• Space Diversity should be considered to eliminate the MP impact on RSL

• You can configure RSL Threshold counters to get a better resolution of the problem!
Troubleshooting an Installed Link
RF Interference Received at Antenna
• Interference from other radio links in the same frequency or Tx High / Tx Low on same site
(Includes XPIC configurations).
Actions:
• Mute transmitter at remote end and check RSL (should be less than -90dBm) in order to
identify interference for XPIC system, both Tx should be muted;
• Perform RF loop and verify that no errors are registered.

74
 Troubleshooting an Installed Link
Fading due to weather conditions
• Please see below records from our IP-20E link which is used as main traffic connection of our office, site called “Natura – Ceragon” with
connectivity site “Natura – Silo”

• Storm started around 9:45 AM local time. During the storm was min bit rate 42Mbps, AC power lost in the office around 9:55AM but both
sites are protected by UPC with different power capacity. At ~10:23AM, our office site “Natura – Ceragon” was turned off due to loss of
power from UPC.
Signal Level PM report “Natura - Ceragon” Signal Level PM report “Natura - Silo”

• Why do PM reports not contain the data of the know lost power?
• The skipped values when the radio was without power cannot be considered by the radio for the PM, concept of PM are
measurements with working conditions (Power up radios).
• Why the integrity in one site is checked and in the opposite site is with a “x”?
Integrity Indicates whether the values received at time and date of the measured interval are reliable. An x in the column indicates that the values are not reliable due to a possible power
surge or power failure that occurred at that time.
75
Troubleshooting an Installed Link
Fading due to weather conditions
• Continuing with the revision of the data and checking the Aggregate PM reports we found the follow:
• In the Ceragon Side, only were recorded 1 Errored Second in 2 different intervals.
• In the site “Natura – Silo” are recorded several periods with Unavailable Seconds and Errored seconds.
WHY?
• The skipped values when the radio was without power cannot be considered by the radio for the PM, concept of PM are measurements
with working conditions (Powered-up radios).
• Aggregate page displays modem BER (Bit Error Ratio) ==> the reason that we have ES (errored seconds) SES (Severely errored
seconds) and UAS (Unavailable seconds) measurements.
Aggregate PM report from Site “Natura - Ceragon” Aggregate PM report from Site “Natura - Silo”
Site “Natura – Ceragon suffer a power outage and no records are available for the periods Site “Natura – Silo was still under the power, because recorded are “unavailable seconds” during whole time.
during the outage

76
Troubleshooting an Installed Link
MRMC PM & ACM
• Analyzing the MRMC PM report we can find that the ACM was working and capacity was reduced during the reported period
of time, anyway the register for the outage are not available

MRMC PM report “Natura - Ceragon” MRMC PM report “Natura - Silo”

After storm and power

supply recover, link
continue working in
normal way

77
 Critical Alarms
How to analyze event log/alarms?
Alarm ID Name Type Description Severity Probable Cause Corrective Actions
1. Check link performance.
1. Fade in the link.
2. Replace RFU.
603 radio-lof Alarm Radio loss of frame Critical 2. Fault in RFU.
3. Make sure same script is loaded at both ends of the
3. Different radio scripts at both ends of the link.
link.
The current configuration does not match the activation-
key-enabled feature set. 1. Get the list of features' configurations that are violated
48 hours after a "activation key violation" alarm is raised, via the "activation key information report".
907 license-violation-alarm Alarm Activation key violation Critical
sanction mode is activated in which all alarms except the 2. Install a new activation key that allows the use of all
activation key violation alarm are cleared and no new required features.
alarms are raised.
5100 mkey-mismatch Alarm Master key mismatch cross over the link Critical Master Key was not set correctly. Verify the Master Key.
1. Validate the MSE on both sides of the link.
1. Radio LOF on Tx/Rx direction.
general-encryption 2. Validate the session key on both sides of the link.
5102 Alarm Payload Encryption failure Critical 2. The session key does not match across the link.
failure 1. Validate the AES admin setting on both sides of the
1. The AES admin setting does not match across the link.
link.
5108 post-fail-alarm Alarm Power On Self-Test Failed Critical System failure Reboot the unit.
1. Faulty coaxial cable between master and slave RFUs. 1. Try re-initiation of MIMO. If still fails:
Clock-source-sharing
30007 Event Clock source sharing failure Critical 2. Hardware failure in Master RFU. 2. Replace faulty coaxial cable and reset Master RFU.
failure-event
3. Hardware failure in Slave RFU. 3. Replace faulty RFU.
1. Unsuitable hardware for MIMO operation requirements.
Unsuitable-hardware 2. Dual carrier RFUs (MIMO 2x2 and 4x4). Make sure both RFUs are compatible for MIMO
31003 Alarm Unsuitable hardware for MIMO Critical
for-MIMO-alarm 3. RFUs with MIMO bus interface (MIMO 4x4). operation.
4. Clock source sharing capability (MIMO 4x4).
1. Not all MIMO carriers are set to same radio script or 1. Load same MIMO compatible radio script to all MIMO
Unsuitable-software script is not compatible for MIMO. carriers.
Unsuitable software configuration for
31004 configuration-for-MIMO Alarm Critical 2. Radio TX and RX frequency is not identical on all MIMO 2. Set same TX and RX frequency on all MIMO carriers.
MIMO
alarm carriers. 3. Disable XPIC, Multi radio and ATPC on all MIMO
3. XPIC or Multi radio or ATPC features are enabled. carriers.
Clock-source-sharing 2. Faulty coaxial cable between master and slave RFUs 2. Replace faulty coaxial cable and reset Master RFU.
31005 Alarm Clock source sharing cable unplugged Critical
failure-alarm 3. Mate does not exist 3. Replace faulty RFU.

78
IP-20C Alarm analysis example
NSA SA
NSA SA Grand
IP's Element
Minor Warning Total Critical Major Total Total Reported Issue Corrective Action
Unreachable
Grand Total 804 415 1219 7976 1 58 8035 9254
2405:200:137:800:3:2:553:24b 679 679 946 1 53 1000 1679 RSL High/MSE Low Perform a Radio loopback/Interference Test
RSL Cross the threshold if was isolated issue and disappear after
RSL Degrade/Defective block the time, Check weather conditions during the reported issue.
2405:200:13d:500:3:2:552:33a 51 51 256 256 307
observed on port 1 If is a permanent issue, please verify the follow:
Antenna alignment, test interference and perform RF loopback
RSL Cross the threshold if was isolated issue and disappear after
the time, Check weather conditions during the reported issue.
2405:200:13d:500:3:2:553:22b 37 3 40 247 5 252 292 RSL Degrade/Defective block
If is a permanent issue, please verify the follow:
Antenna alignment, test interference and perform RF loopback
RSL Cross the threshold if was isolated issue and disappear after
RSL Degrade/Defective block the time, Check weather conditions during the reported issue.
2405:200:10f:100:3:2:552:4d2 19 19 1547 1547 1566
observed on port 2 If is a permanent issue, please verify the follow:
Antenna alignment, test interference and perform RF loopback
RSL Degrade/Defective block RSL Cross the threshold ,weather/need to be verify the
2405:200:13d:d00:3:2:553:d3 9 9 1706 1706 1715
observed on port 2 alignment/local loopback/interference

2405:200:137:800:3:2:553:24a 6 2 8 1191 1191 1199 RSL Low/MSE Low Verify the antenna alignment/Radio loopback/Interference

Combination of Alarms in a working Network

.Radio port #1 : Radio loss of frame | Radio port #1 : RFU RX level out of range | Radio port #1 : RFU RX level out of range Link Down/Power Issues
Radio port #2 : Radio loss of frame | Radio port #2 : RFU RX level out of range | Radio port #2 : Remote communication failure Link Down/Power Issues
Multi Carrier ABC LOF | Carrier 1: Remote communication failure | Carrier 1: RFU RX level out of range | Carrier 2: Remote communication failure | Carrier 2: RFU RX level out of range Link Down/Power Issues
Carrier 1: Radio excessive BER | Carrier 1: Radio loss of frame | Carrier 1: Remote communication failure Link Fading
Carrier 2: Radio excessive BER | Carrier 2: Radio loss of frame | Carrier 2: Remote communication failure Link Fading
Radio port #1 : Radio excessive BER | Radio port #1 : Radio loss of frame | Radio port #1 : Radio signal degrade Link Fading
Radio port #2 : Radio excessive BER | Radio port #2 : Radio loss of frame | Radio port #2 : Radio signal degrade Link Fading

79
Troubleshooting an Installed Link
ABS-CBN (Antipolo-Silang Link)

Link Assessment (CMS)

 01 July 2017
 Errors both sides of the link, more frequent at Silang side
 MSE value is -31 to -29 at Silang. This is relatively high at normal operation.
Typical value is -38 to -34.
 Loss of frame (LOF) and Signal Degraded on Radio alarm, more frequent at Silang
 -99dBm Signal level for sometimes on main receiver at Silang
 Cable Short alarm (intermittent) at Silang
Troubleshooting Plan
 July 2, 2017 at 1am (sign off)
 Check Flexible waveguide, main RF receive path (Silang)
 Check if cable (both site)
 Change RFU at Antipolo
 Align SD antenna at Silang
Actual Troubleshooting
Silang Site
 Arrived at site; Silang (0045H), Saved configurations, screenshots
 RSL= -99 dBm
 Noticed that frequencies of both sites are not match. Put back the original
frequency (Silang Rx)
 Link are up but still intermittent
 Checked IF connector physically (indoor)
 No abnormality
 Checked FlexWG for possible dent, open one end to check water ingress (OCB side)
 No dent and no trace of water ingress
 Put back connection
 Checked IF connector (OCB side)
 Corrosion bet the inner and outer conductor found
 Cleaned/removed corrosion
 Put back connections
 Monitor Performance
 MSE improved from -31 to -36
 No errors for more than an hour
 No defective blocks for an hour
 Leaved the site
Antipolo Site
 Arrived at Antipolo Site (0030H)
 Saved configurations, screenshots
 Checked physical hardware
 Evaluate configurations
Photos and Screenshots (CMS)

 RSLMAIN= -99 dBm  Drawer-RFU communication failure

 Signal degraded
 Loss of Frame
Photos and Screenshots (Silang Site)

 At Silang before start of

troubleshooting at site
 Frequencies not matched
 RSL= -99 dBm
 After putting back the the
correct frequency
 Link is up
 But link still intermittent
 Loopback test fail at Silang

Silang Antipolo
 Checked flexible waveguide
 No water inside
 No trace of water ingress
either
 Gasket is intact
 Checked IF cable dry
 Sealing is dry
 Crimped/assembly is intact
 Corrosion bet inner and outer
conductor
 Removed/cleaned corrosion
 After cleaning the connector
 MSE improved to -36.5
 No error on loopback test
 No error on normal operation
for more than 1 hr after
activity at site
 No alarm since the troubleshooting end
 Very minimal error since the
troubleshooting end
What was discussed
 Introduction/Type of faults  Full Outdoor

 Radio link diagrams  Troubleshooting Diagrams

 Full outdoor  Troubleshooting Procedure
 Hybrid solutions (full outdoor + IDU for  Hardware/RF Issues
 Fading
TDM transport)
 Interference
 Causes of Radio Link Failure  Looping

 Faults and Alarms

 Troubleshooting a Link
 Performance Monitoring radio
 New Link
 examples
 Performance Monitoring Ethernet
 Working Link
Services  Examples
 Critical Alarms
 RMON

 Loopbacks
94
95