You are on page 1of 23

MW Troubleshooting Using LinkPilot v1.

0

MW Troubleshooting Using Link Pilot

Abstract: This document is tailored for use by the NOC staff. It keeps itself to how Sagem’s tool LinkPilot can be used to troubleshoot and help Field Engineer troubleshoot an issue with a Microwave link. Field engineers can benefit from this guide when running Link Pilot directly or remotely. The document also includes diagnosis of the problem on analysis made from results provided by the tool, and proposes possible remedies. Version: 1.0 Date: Nov 23, 2007 Compass Location: MOTOROLA INTERNAL USE ONLY This document and the information contained in it is MOTOROLA INTERNAL USE ONLY and shall not be used, or published, or disclosed, or disseminated outside of Motorola in whole or in part without Motorola’s consent. This document contains trade secrets of Motorola. Reverse engineering of any or all of the information in this document is prohibited. The copyright notice does not imply publication of this document.

Copyright © 2006 Motorola, Inc. All rights reserved. September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY .

Page 1/23

MW Troubleshooting Using LinkPilot v1.0

Approver List
Name Nadeem Khan Syed Irfan Ahmad Danial Mausoof Department
O&M Field Operations Field Operations

Revision History

Version 1.0

Date Nov 23, 2007

Author(s) Muhammad Waqar

Description MW Troubleshooting Using LinkPilot

Required Reviewers
Name Ali Saeed Rana Fahad Qamar Saud Sarwar Organization
SME Radio Access Network Field Operations Central MW Technical Community

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 2/23

MW Troubleshooting Using LinkPilot v1.0

Table of Contents

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 3/23

MW Troubleshooting Using LinkPilot v1.0

1. Checking Status
a. Logging in:

Launch Link Pilot Element Manager. Password: admin SNMP Community: public Save password to avoid having to enter every time for login. b. What do 5 LED’s Indicate:

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 4/23

MW Troubleshooting Using LinkPilot v1.0

c. What if RMT LED is Red: It indicates there is a problem with Local to Remote IDU communication. This is generally caused by a loose IF connector, or a loose MW Dish, and is normally accompanied by a drop in RSL, too. d. Displaying Current Alarms: Either click the Bell icon encircled below, or use Main Menu: Alarms -> Current Alarms.

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 5/23

MW Troubleshooting Using LinkPilot v1.0

Verifying Timestamps: Configure the current time in Main Menu -> File -> System -> Information, if alarms are not timestamped with correct timezone.

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 6/23

MW Troubleshooting Using LinkPilot v1.0

e. Getting RSL and Link Status: Click the IDU icon in icons bar, labelled with R or L depending on whether you want to find the Status for right or left ODU. The following window will appear:

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 7/23

MW Troubleshooting Using LinkPilot v1.0

Radio button will be showing “Local + Remote”, and Tx/Arrows against ODU will be green, only if the link is up. However, the link may be up, but RSL may have dropped down. This is being displayed against “Monitored Rx Level”. Normally, it should be within 4dB of what is proposed in the Link Budget. Fluctuating RSL can cause a fluctuating link. f. Finding Temperature of IDU and ODU

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 8/23

MW Troubleshooting Using LinkPilot v1.0

IDU Critical Temperature: 45C ODU Critical Temperature: 55C Operating the system for long periods above critical temperature can damage the hardware. Mostly IDU or ODU exceeds critical temperature because Aircon in Eltek cabinet is not working properly. Any such incidents should be escalated to save the equipment. For some IDU, the leftmost ‘I’ icon may need be clicking to display alarms. g. Displaying Version Information: Main Menu -> File -> System -> Version.

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 9/23

MW Troubleshooting Using LinkPilot v1.0

2. Verifying Configuration
a. ODU Configuration Main Menu -> Configuration -> ODU -> Right | Left -> ODU Configuration

Important here is to verify that Tx and Rx frequencies for both Local and Remote ODUs are as per link budget. If not, set them right and click ‘Apply’. b. In-Band Configuration

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 10/23

MW Troubleshooting Using LinkPilot v1.0

Main Menu -> Configuration -> Management System -> IP Configuration Make sure all three check boxes are checked. If not, IDU’s farther than this IDU will not be pingable. Network Element Type and Gateway Ring Subnet Address/Mask should be as per IP Plan.

c. MRMC Setting A link may fail if there is a mismatch between link speeds between the local and remote IDUs. Make sure they are same if the link is down. For a link to a Spur site, it would be 57Mbps,

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 11/23

MW Troubleshooting Using LinkPilot v1.0

For 100Mbps Link:

For 150Mbps Link:

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 12/23

MW Troubleshooting Using LinkPilot v1.0

d. Autoneg Setting For an IDU connecting directly to BCU (as would be the case with all Spur sites), port Speeds for BCU and IDM must match. (The universal rule is that no two ports connecting directly to each other can have a speed mismatch). DAP is 100Mbps, so should be IDM. Double click the 2x FE port on IDM, ( or Main Menu -> Configuration -> Interfaces -> Right -> Fast Ethernet)

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 13/23

MW Troubleshooting Using LinkPilot v1.0

e. IP Configuration Click the encircled upper serial port on IDC. ( or Main Menu -> Configuration -> Management System -> IP Configuration) Verify “Ethernet IP Mask” and “Default Router IP Address”. For a Network Element, Defautl Router IP Address should be 0.0.0.0, and as per IP Plan for a Gateway Network Element (GNE). Configuring it non-zero for an NE may introduce management issues to the network (ie some IDU’s may no more remain pingable).

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 14/23

MW Troubleshooting Using LinkPilot v1.0

f. Protection In case of a 1+1 link, Left IDM is generally active and Right standby. System automatically switches to the standby IDM if BER on the active one exceeds a threshold. Standby IDM can be identified by an amber Drawer LED. We normally keep Protection disabled if Link is 1+0. Internal Protection is configured for 1+1 links.

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 15/23

MW Troubleshooting Using LinkPilot v1.0

Above: 1+0 Link (Protection Disabled) , Below: 1+1 Link (Internal Protection)

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 16/23

MW Troubleshooting Using LinkPilot v1.0

3. Monitoring Performance
a. RSL History IDM stores RSL for the last 24 Hours, and displays it averaged over intervals of 15min.

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 17/23

MW Troubleshooting Using LinkPilot v1.0

Both graph and table are self-explanatory. Integrity means probable validity of the RSL data, e.g., during event of an IDM or ODU reset, the RSL data is unreliable. b. Aggregate Performance Main Menu -> Performance -> Radio -> Right -> Aggregate Displayed if the communication between local and remote ODUs has been erratic in the last 24 hours, again in intervals of 15min. UAS: UnAvailable Seconds, ES: Error Seconds SES: Severe Error Seconds

c. Checking Bit Error Rate Shows if ODU is receiving too many bit errors from remote ODU. BER should be less than 1e-6 (one error in 1 million bits). A good link would have it around 1e-11 to 1e-9. If it is too high (eg 1e-3), cross check the frequency of both local and remote ODUs. It may also be due to external interference to the frequency band allocated. If there is

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 18/23

MW Troubleshooting Using LinkPilot v1.0

another frequency channel allocated in the same frequency band, shifting both sides of the link to it may help. Click the encircled IF connector on IDM or use Main Menu.

d. Alarms Log IDU keeps a faily long record for history of alarms. Click encircled Bell icon or use Main Menu.

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 19/23

MW Troubleshooting Using LinkPilot v1.0

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 20/23

MW Troubleshooting Using LinkPilot v1.0

4. Usual Maintenance
a. Resetting an IDM IDM Can only be Hard reset.

b. Resetting an IDC or ODU Soft as well as Hard reset can be applied to IDC and ODU.

c. Using Loopback Loopback is used to verify if the connection from IDM to the IDU is ok. Furthermore, loopback can be applied at two levels: IDU and ODU, thus identifying whether the problem belongs to within the IDM or between the IDM and the ODU.

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 21/23

MW Troubleshooting Using LinkPilot v1.0

Sometimes, the ODU icon may not appear in the above window. This means IDM is unable to communicate to ODU. IF cable, either of its connectors or IDM may be faulty, hindering the connectivity. Click the loopback icon on IDU or ODU depending on which loopback you want to apply. Then click ‘Apply’. Loopback LED should turn red. All other four LED’s should stay green. If they don’t there may be a problem with IDM. Check RSL at ODU configuration, and note the status of LED’s at IDM on main window of Link Pilot. For a healthy link upto the ODU, RSL during loopback should be higher than -60dBm (normally around -57dBm). Important: Make sure you lift the loopback after you have done your experiment. This because Loopback puts the IDM out of service.

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 22/23

MW Troubleshooting Using LinkPilot v1.0

Important: Never ever apply a loopback remotely on a Remote-end IDM. For Near-end IDM you can. This because when you have applied Loopback to a Remote-end IDM, you will lose access to it since it has stopped transmitting and receiving and is out of service during Loopback. Thus, you will not be able to lift Loopback, and IDM will continue to be out of service unless FE visits and connects to it directly. d. Opening Remote Session Most of the time, we need to verify parameters at both ends of the link. Having opened one end, here’s how open the other.

September 21, 2013 DOCPROPERTY projectdocumentclassification \* MERGEFORMAT MOTOROLA INTERNAL USE ONLY . Page 23/23