OmniBAS Troubleshooting 01 en

GDC-003/11
The information contained in this document is subject to change without prior notice.
INTRACOM S.A. TELECOM SOLUTIONS, 2013. All rights reserved. All copyright, intellectual and industrial rights in this document and in the technical knowledge it contains are owned by INTRACOM S.A. TELECOM SOLUTIONS and/or their respective owners. This document is made available to the end users only for their internal use. No part of this document nor any data herein may be published, disclosed, copied, reproduced, redistributed by any form or means, electronically or mechanically, or used for any other purpose whatsoever without the prior written approval of INTRACOM S.A. TELECOM SOLUTIONS. Information as well as drawings and specifications contained in this document are subject to change without prior notice. All trademarks and copyrights mentioned herein are the property of INTRACOM S.A. TELECOM SOLUTIONS and/or their respective owners. Any rights not expressly granted herein are reserved. Printed in Greece.
INTRACOM TELECOM 19.7 km Markopoulou Ave., Peania, Athens, GR 19002 T +30 210 667 1000, F +30 210 667 1001 http://www.intracom-telecom.com email (product support): omnibas_support@intracom.com
OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0
Table of Contents
Introduction.......................................................................................................... 3 About this Document................................................................................... 3 Declaration of Conformity............................................................................ 4 Equipment Disposal .................................................................................... 5 Safety Precautions...................................................................................... 6 1. Troubleshooting of Onsite Incidents.......................................................... 7 Indoor Unit Not Powered Up ..................................................................... 12 Management Connection Not Feasible ..................................................... 13 System Synchronization Error................................................................... 20 Control Card Not Operational.................................................................... 22 Modem Card(s) Cannot be Recognized .................................................... 23 Modem Card Not Operational ................................................................... 24 Outdoor Radio (ODU) Not Operational...................................................... 25 Radio Link Cannot Be Established............................................................ 30 Radio Link Cannot Achieve Expected Performance .................................. 37 Ethernet Physical Layer is Down............................................................... 45 2. Troubleshooting of uni|MS Alarms........................................................ 48 General Alarms .......................................................................................... 54 Lost Communication with Element ............................................................ 54 Equipment Extracted................................................................................. 59 Part of Service has been Deactivated ....................................................... 60 Part of Pending Service has been Activated ............................................. 61 AEnd Down............................................................................................... 62 ZEnd Down............................................................................................... 63 Management Connection Closed .............................................................. 64 License Violation....................................................................................... 65 Indoor Unit Alarms..................................................................................... 66 Input Alarm 1 /2 /3 /4................................................................................. 66 Fan Failure ............................................................................................... 68 Fan Extracted ........................................................................................... 70 PSU Failure .............................................................................................. 71 Low Temperature...................................................................................... 72 High Temperature..................................................................................... 73 Modem Card Alarms .................................................................................. 75 Modem Failure.......................................................................................... 75 Power Failure............................................................................................ 76 Invalid Modem Inserted............................................................................. 78 PHY Modulation Failure ............................................................................ 79 Clock PLL Unlocked.................................................................................. 81 Receiver PLL Unlocked ............................................................................ 82 Transmitter PLL Unlocked......................................................................... 83 Modem Chip Failure.................................................................................. 84 Modem Chip Unlocked.............................................................................. 85 Radio Link Alarms ..................................................................................... 86 Modem Link Failed.................................................................................... 86 Remote Modem Link Failed ...................................................................... 87 RAI Alarm (Modem Group 1-2 /1-3 /2-4) ................................................... 88 RAI Blocked Alarm.................................................................................... 92 ODU RSSI Alarm ...................................................................................... 95 Rx Normalized MSE (SNR) Alarm............................................................. 98 1
Rx LDPC Decoders Stress Alarm ........................................................... 101 East Port (Modem 2) of Ring Failure....................................................... 103 West Port (Modem 1) of Ring Failure...................................................... 107 Outdoor Unit (ODU) Alarms .................................................................... 111 ODU Communication Failure .................................................................. 111 ODU Pout ALC Alarm ............................................................................. 113 ODU Rx PLL LD Alarm ........................................................................... 115 ODU Tx PLL LD Alarm............................................................................ 117 ODU Tx Configured Frequency Out of Range Alarm............................... 119 ODU RF PLL LD Alarm........................................................................... 122 ODU MW PLL LD Alarm ......................................................................... 124 ODU Loopback PLL LD Alarm ................................................................ 126 Tx ODU Configured Power Out of Range Alarm ..................................... 128 ODU High Temperature Alarm................................................................ 130 ODU RSSI Rx User Alarm ...................................................................... 132 ODU Min Pif Alarm.................................................................................. 135 ODU Model Alarm................................................................................... 137 ODU H/W Bandwidth Alarm .................................................................... 139 ODU Cable Calibration Alarm ................................................................. 141 ODU Max Pif Alarm................................................................................. 143 ODU Low If Alarm................................................................................... 145 ODU Low Temperature Alarm................................................................. 147 E1 Line Alarms......................................................................................... 149 E1 Line LOS ........................................................................................... 149 E1 Line LOF............................................................................................ 151 E1 Line AIS............................................................................................. 153 E1 Line RAI ............................................................................................ 155 E1 Line Admin Down .............................................................................. 157 E1 is Looped........................................................................................... 158 E1 Local Loop......................................................................................... 160 E1 Remote Loop..................................................................................... 162 Ethernet Line Alarms............................................................................... 164 SFP Tx Fault........................................................................................... 164 SFP Rx LOS ........................................................................................... 166 Ethernet Link Down................................................................................. 168 3. Troubleshooting of Problems Reported by Customers ........................ 171 Radio Link is Down ................................................................................. 172 Ethernet Service Outage (or with Errors) ................................................ 176 E1 Service Outage (or with Errors) ......................................................... 184 E1 Synchronization Issues...................................................................... 189 Appendix: Procedures Relevant to Troubleshooting.................................... 193 P1 Measuring the Input Voltage ........................................................... 194 P2 Replacing the Fan Tray (OmniBAS-4W) ......................................... 195 P3 Getting the IP Addresses (Serial Connection)................................. 196 P4 Replacing the E1 Interface Card (OmniBAS-4W)............................ 198 P5 Realigning the Antennas................................................................. 199 P6 Replacing a Modem Card ............................................................... 203 P7 Replacing the Control Card............................................................. 205 P8 Replacing the Radio Unit (ODU)..................................................... 208 P9 Measuring Modems DC Voltage Out.............................................. 215
Introduction About this Document

Scope
This document aims at providing first-level troubleshooting instructions for established Point-to-Point (PtP) links based on OmniBAS-2W and OmniBAS-4W systems.
Concerned products
Product OmniBAS-2W Ethernet only OmniBAS-2W 8E1 OmniBAS-2W 16E1 OmniBAS-2W RC (1) OmniBAS-4W 2GbE OmniBAS-4W 2GbE / 2FE
Software Version 3.0_1210.1.4.1 3.0_1200.4.1 2.4_1220.1.0.0 3.0_1200_1210.1.5.1 3.0_1400.2.6.1 3.0_1410.1.0.0
Classification of incidents
In the following pages, troubleshooting instructions are given for a variety of incidents. The latter are classified in three major categories, according to how incidents are notified to the installer, the commissioner or the NOC operator: Onsite Incidents Incidents that occur locally during the installation, commissioning or the maintenance of equipment. Onsite incidents are elaborated in chapter 1. uni|MS management notifications on alarm situations associated with malfunctioning equipment or degradation of services. Alarms are elaborated in chapter 2. Chapter headings correspond to the alarms text description, as provided by uni|MS. This facilitates readers in quickly accessing troubleshooting information. Problems that are reported to the Call Center (by customers) and which they are associated with degraded or interrupted services. Reported problems are elaborated in chapt. 3.
Alarm Notifications
Problem Reports
The Appendix contains all testing & hardware replacement procedures to carry out during the equipment troubleshooting.
Continued on next page
(1)
Support of PTP-R modem card (28 GHz).
About this Document, Continued

Target audience
The information given in this document is intended for technicians authorized to carry out troubleshooting tasks, inclusive of: Task Fault localization and recovery. Onsite hardware replacement and measurements. Required Skills Trained on OmniBAS system installation /commissioning /operation. Capability to carry out diagnostic and corrective procedures using the uni|MS management software. Basic networking skills. Experience in using generic troubleshooting practices and methodologies. Experience in replacing hardware. Capability to carry out performance tests and measurements.
Reference documents
The following documents, which are available by Intracom Telecom, may be needed during troubleshooting: # Reference Document 1 uni|MS technology driver for OmniBAS. 2 OmniBAS installation manual (indoor). 3 OmniBAS installation manual (outdoor). 4 OmniBAS startup & commissioning manual. 5 OmniBAS product catalog (indoor). 6 OmniBAS product catalog (outdoor). 7 PtP operating frequencies reference manual. 8 uni|MS Firewall setup administrator manual. Intracom S.A. Telecom Solutions 19.7 km Markopoulou Ave., Peania, Athens, GR-19002 Tel. (+30) 210 667 1000, Fax: (+30) 210 667 1001 email (support): omnibas_support@intracom-telecom.com
Contact information
Declaration of Conformity
Hereby, Intracom S.A. Telecom Solutions declares that the OmniBAS systems are in compliance with the essential requirements of the R&TTE Directive 1999/5/EC. For further information about the relevant Declaration of Conformity, please visit our website at http://emc.intracom.gr
Equipment Disposal
Disposal of old electrical and electronic equipment (applicable through the European Union and other European countries with separate waste collection systems). This symbol, found on this product and any of its parts or on its operating instructions or on its packaging, indicates that electrical and electronic equipment may not be disposed of as unsorted municipal waste. Instead, this product should be handed over to applicable collection points for the recycling of electrical and electronic equipment. By ensuring the correct disposal of this product, you will help prevent potential negative consequences to the environment and human health, which could otherwise be caused by inappropriate disposal of this product. By recycling, reusing and other forms of recovery of old electrical and electronic equipment you are making an important contribution to the conservation of natural resources and to the protection of the environment. For more information about the recycling of this product, please contact your local municipal authorities, municipal waste disposal service or the store where you purchased this product.
( ). , , , , . . , , . , . , , . , .. (www.electrocycle.gr).
Safety Precautions
WORKING ON THE BUILDINGS ROOF
During stormy weather, do not perform any mechanical assembling or antenna beaming (alignment) works on the buildings roof. The metal structure of towers/ masts is prone to lightning.
ESD PROTECTION
Always use proper antistatic protection when handling ESD sensitive parts. Protection is provided by means of a grounding bracelet, antistatic bags, etc.
EXTERNAL OVER-VOLTAGE PROTECTION

Ensure the existence of external over-voltage protection (of rating that exceeds 1.5 kV) at the input and the output of the indoor unit, prior to its connection to the network. Lack of external protection could cause damage to the equipment.
1.
Introduction
Troubleshooting of Onsite Incidents

This chapter deals with onsite incidents that might occur during the onsite installation, commissioning or maintenance of the equipment. A problem is usually notified visually: either through the activation of an alarm indicator (on the front panel of the indoor unit), or through the unexpected behavior of the equipment (during its power up process for instance).
Basic troubleshooting by hardware swapping
The following procedure is carried out when the field technician is not familiar with the OmniBASs software alarms and troubleshooting methodology, and there is lack of spare equipment (i.e. cards). By swapping equipment in a specific order, the field technician will be able to localize the fault, provided that other collocated links are readily available and that downtime is allowed. `The field technician must be able to correctly and accordingly configure the following: Modem operation (protected / standalone). Modem parameters. ODU
NOTE
When swapping equipment, the field technician should be able to recognize what configuration changes are needed to be done in order to successfully re-establish the links. To avoid problems, technician should first carry out backup of the initial configuration (prior to proceeding) and restore it as soon as he/she finishes with hardware swapping troubleshooting.
In the following two examples, we assume that Link A is up and Link B is down.
Troubleshooting of Onsite Incidents, Continued

Basic troubleshooting by hardware swapping, continued
A. Installation without Waveguide (between ODU & Antenna): Without OMT:
With OMT:
Action
Step 1: Swap coaxial cables A & B (modem side).
Connections
Results
Both paths have problem. Only Modem B path has problem.
Suspected Issue
Configuration settings have errors. Modem B.
Modem A Coaxial B ODU B OMT Port B Antenna B (Antenna) Modem B Coaxial A ODU A OMT Port A Antenna A (Antenna)
Problem shifted to Modem A path.
Coaxial B or ODU B or OMT /Antenna B (Antenna) (refer to step 2).
Only Modem A path has problem. Problem shifted to Modem A path.
Coaxial B. OMT /Antenna B (Antenna). Continued on next page

A. Installation without Waveguide (between ODU & Antenna), continued: Action Connections Results
Both paths have problem. Modem A Coaxial B ODU A OMT Port A Antenna A (Antenna) Modem B Coaxial A ODU B OMT Port B Antenna B (Antenna) Only Modem A path has problem.
Suspected Issue
Configuration settings have errors. Coaxial B.
Step 2: Swap coaxial cables A & B (ODU side).
Problem shifted to Modem B path.
ODU B or OMT /Antenna B (Antenna) (refer to step 3).
Step 3: Swap ODU A & B.
Modem A Coaxial B ODU A OMT Port B Antenna B (Antenna) Modem B Coaxial A ODU B OMT Port A Antenna A (Antenna)
Problem persists for Modem B path. Problem shifted to Modem A path.
ODU B.
OMT /Antenna B (Antenna).

B. Installation with Waveguide W/G (between ODU & Antenna):
NOTE
In order to carry out the steps 3 & 4 below, both modem paths (A & B) need to operate in the same frequency band. If not, then spare parts (ODU, W/G and Antenna) are required.
Action Step 1: Swap coaxial cables A &B (modem side).
Connections Modem A Coaxial B ODU B W/G B Antenna B Modem B Coaxial A ODU A W/G A Antenna A Modem A Coaxial B ODU A W/G A Antenna A Modem B Coaxial A ODU B W/G B Antenna B
Results Both paths have problem.
Suspected Issue Configuration settings have errors.
Only Modem B Modem B. path has problem. Problem shifted to Modem A path. Both paths have problem. Coaxial B or ODU B or W/G B or Antenna B (refer to step 2). Configuration settings have errors.
Step 2: Swap coaxial cables A & B (ODU side).
Only Modem A Coaxial B. path has problem. Problem shifted to Modem B path. ODU B or W/G B or Antenna B (refer to step 3).
10

B. Installation with Waveguide W/G (between ODU & Antenna), continued: Action Connections Modem A ODU A Coupler A W/G B Antenna B Modem B ODU B W/G A Antenna A Modem A ODU A W/G B Antenna A Modem B ODU B W/G A Antenna B Results Problem persists for Modem B path. Problem shifted to Modem A path. Problem persists for Modem A path. Problem shifted to Modem B path. Suspected Issue
Step 3: Swap W/G A & B (ODU side).
ODU B.
W/G B or Antenna B (refer to step 4).
Step 4: Swap W/G A&B (Antenna side).
W/G B.
Antenna B.
11
Indoor Unit Not Powered Up

Explanation
The OmniBAS-2W /-4W indoor unit is not powered up after it is switched on for the first time.
Indication
After the indoor unit is switched on, all front-panel leds remain off.
Causes & actions
# 1
Probable Causes Power cable is impaired or its connector is incorrectly inserted. Inappropriate input voltage.
Implications Potential short-circuit condition.
Suggested Recovery Procedure Check for connector / terminal displacement at both ends of the cable. Investigate for visual deterioration along the entire run of the cable. Measure the input voltage applied to the indoor unit (P1 procedure). If voltage is found out of the equipment manufacturers range, use a different power supply source. Ensure that you have activated the correct breaker(s). Ensure that breaker(s) are rated at the amperage specified by the equipment manufacturer.
Wrong circuit breaker(s) activated or breaker(s) are under-rated.
Indoor unit cannot operate.
Only for OmniBAS-4W: PSU card not correctly inserted. Only for OmniBAS-2W: Controller card not correctly inserted.
Gently push the card fully inwards to ensure proper contact with the pins at the backplane. Then, secure card in place by fully tightening its side screws.
12
Management Connection Not Feasible

Explanation
Communication with the OmniBAS-2W /-4W indoor unit, using one of its front-accessible ports (see table below), is unfeasible:
Designation on Port
Port Type
Port is Used for Carrying Payload traffic Inband Mngt. x Outband Mngt. x x x
ETH 100/1000, GbE GbE ETH 10/100 NMS 10/100
RJ-45 (electrical) SFP RJ-45 (electrical) RJ-45 (electrical)
Indication
a. Status of leds on Ethernet ports (while waiting for ping response from the OmniBAS indoor unit): Ethernet ports led (link): remains constantly on, meaning that the port is administratively up. Ethernet ports led (activity): does not blink, meaning that OmniBAS does not respond to ping command.
b. On-screen notification (while waiting to connect through the uni|MS Node Manager): Example: if you are trying to access the IP address 172.28.77.16, then the following message appears:
13
Management Connection Not Feasible, Continued

Causes & actions (1/2)
A. Outband management connection: # 1 Probable Causes The Ethernet cable, connecting the laptop to the OmniBAS indoor unit, is impaired. Wrong IP address. (1) Implications The OmniBAS system cannot be managed through the outband management port. Suggested Recovery Procedure Replace cable with a new one and re-try.
a. Connect the laptop to the AUX port and get the IP address of the system (P3 procedure). b. Change the IP address of the laptop or the indoor unit so that they both belong to the same subnet.
The default IP address for the outband management is 192.168.1.100, which can be changed. In such a case, management communication over the outband channel will be feasible only through the new IP address.
(1)
14

B. Inband management connection local unit (gateway): (We assume that engineer is trying to access the local unit, serving as gateway to other OmniBAS units, using a laptop and untagged traffic). # 1 Probable Causes The Ethernet cable, connected on the local unit and carrying inband management, is impaired. Ethernet port is physically down. Wrong IP address. (1) Cannot manage local as well as any other OmniBAS units managed through the local OmniBAS unit. Implication s Suggested Recovery Procedure Replace cable with a new one and re-try.
Carry out troubleshooting as instructed for case: Ethernet Physical Layer is Down If the correct IP address cannot be found then: a. Connect the laptop to an outband management port (NMS 10/100). b. From the management application, click OmniBAS NE and select Configuration > Management tab to type the inband managements IP address.
NOTE
Both laptop and OmniBAS units outband management port must belong to the same subnet.
(1)
When not configured, inband managements IP address is 10.10.10.100.
15

B. Inband management connection local unit (gateway), continued: # 4 Probable Causes Inband / outband conflict. Implications Cannot manage the OmniBAS unit. Suggested Recovery Procedure a. Connect the laptop to an outband management port (NMS 10/100). b. From the management application, click OmniBAS NE and select Configuration > Management tab. c. Set the inband and outband IP addresses to belong to a different subnetwork. Set inband management ports default VLAN to the same value shown next to VLAN ID field in the Inband Management Parameters group box (right click OmniBAS NE and select Configuration tab > Inband / Outband / RTC tab).
The VLAN of the Ethernet port (to be used for inband management) is not configured correctly.
Cannot manage the OmniBAS unit (through the inband management port).
16

B. Inband management connection local unit (gateway), continued: # 6 Probable Causes Congestion exists on the network and QoS has not been set. Implications Problematic or no inband management of both local (gateway) unit and other OmniBAS units managed through the local unit. Suggested Recovery Procedure Enable QoS and make sure that management traffic has the highest priority queue with respect to the one for all other types of traffic.
Bridge loops exist in the network without proper Problematic or no configuration. inband management and payload traffic in the network. Control card has failed.
a. Connect the laptop to an outband management port (NMS 10/100). b. Remove the logical loop(s). Replace the control card with a spare one (P7 procedure).
C. Inband management connection remote unit(s) managed through the local (gateway) unit: (We assume that engineer is trying to access remote unit(s) using a laptop and untagged traffic). # 1 Probable Causes Local (gateway) OmniBAS unit has problem. Implications Cannot manage remote OmniBAS unit(s) participating in the same link. Suggested Recovery Procedure For troubleshooting, refer to the previous inband management case (B).
17

C. Inband management connection remote unit(s) managed through the local (gateway) unit, continued: # 2 Probable Causes Wrong IP address. (1) Implications Cannot manage the remote OmniBAS unit. Cannot manage the remote OmniBAS unit. Suggested Recovery Procedure Connect to the local OmniBAS unit and from within the modem status screen, find the IP address of the remote OmniBAS unit. a. Visit remote site. b. Connect the laptop to an outband management port (NMS 10/100). c. From the management application, click OmniBAS NE and select Configuration > Management tab. d. Set the inband and outband IP addresses to belong to a different subnetwork. Create the appropriate associations of the inband management VLAN id with the required Ethernet ports (right click OmniBAS NE > Configuration tab > L2 Properties tab > VLAN/VLAN Port tab).
Inband / outband conflict.
OmniBAS is not configured to pass inband management for the rest of the elements in the network.(2)
Remote management cannot pass through the specific OmniBAS unit.
(1) (2)
When not configured, inband managements IP address is 10.10.10.100. Assuming that the links in the network are established and working properly.
18

# 5
Probable Causes Link outage or with problematic behavior.
Implications Remote management cannot pass through the specific OmniBAS unit. Problematic or no inband management of both local (gateway) and the remote OmniBAS units within the same link.
Suggested Recovery Procedure Carry out troubleshooting of the problematic link(s). Refer to cases: Radio Link Cannot Be Established Radio Link Cannot Achieve Expected Performance Enable QoS and make sure that management traffic has the highest priority queue with respect to the one for all other types of traffic.
Congestion exists on the network and QoS has not been set.
Bridge loops exist in the network Problematic without proper or no inband configuration. management and payload traffic in the network. Control card has failed.
a. Connect the laptop to an outband management port (NMS 10/100). b. Remove the logical loop(s). Replace the control card with a spare one (P7 procedure).
19
System Synchronization Error

Explanation
The OmniBAS system has a synchronization error, which may have impact on the delivered services.
Indication
OmniBAS-2W: The led STAT2 (STATUS2) on the control card: blinks amber, meaning that the system is running in holdover mode, or is off, meaning that the system is out of synchronization.
OmniBAS-4W:
Causes & actions
# 1
Probable Causes Clock source is not correctly configured.
Implications Problematic E1 service due to slips.
Suggested Recovery Procedure From the management application, click the OmniBAS system and select Configuration > Synchronization tab. Select and configure an appropriate clock source, as instructed in the Driver for OmniBAS reference manual. Click the OmniBAS system and select Configuration > Synchronization tab. Check if clock sources Operation Status = Locked. If not, check clock source itself (cable, clock accuracy, etc.). If an alternative clock source is available, try using this source.
The predefined clock source is absent or has problem.
System operates in holdover mode. Problematic E1 service due to slips.
20
System Synchronization Error, Continued

Causes & actions (continued)
# 3
Probable Causes Control cards synchronization circuitry has failed.
Implications Problematic E1 service due to slips.
Suggested Recovery Procedure a. From the management application, perform a system reset.
Resetting the system will result in interruption of all OmniBAS node services. b. If problem persists, replace the control card (P7 procedure).
21
Control Card Not Operational

Explanation
The control card (fitted in the OmniBAS-2W /-4W indoor unit) malfunctions, or it has failed.
Indication
OmniBAS-2W: The led STAT1 (STATUS1) on the control card is: off, meaning that the control card is not powered, or red, meaning that the control card has failed.
OmniBAS-4W:
Causes & actions
# 1
Probable Causes All leds on all cards are off: Generic power supply problem. Leds on other cards light up: Internal control card failure. Internal control card failure (STATUS 1/ STAT1 led = red).
Implications
Suggested Recovery Procedure Refer to case: Indoor Unit Not Powered Up a. From the management application, perform a system reset. b. If problem is not fixed, try performing a hard reset by switching off and on the power supply breaker(s). c. If problem persists, replace the control card with a spare one (P7 procedure).
All served links are out of operation.
22
Modem Card(s) Cannot be Recognized

Explanation
The control card cannot communicate with one (or more) modem cards fitted in the OmniBAS-2W /-4W indoor unit.
Indication
OmniBAS-2W: The led MDM (MODEM) on the concerned modem card is off, red (or blinks red), meaning that the card is not correctly installed (or it has failed).
OmniBAS-4W:
Causes & actions
# 1
Probable Causes Modem card is not correctly installed into the indoor unit.
Implications
Suggested Recovery Procedure a. Carefully extract the modem from its slot. b. Inspect the condition of cards backplane pins. If pins are found impaired, proceed to step 2b. c. Fully reinsert card back in slot and secure in place. a. From the management application, perform a modem card reset. b. If nothing changes, replace the modem card (P6 procedure). c. If problem still persists and other modems also have problem, then perform a system reset. d. If problem is not fixed, perform a hard reset by switching off and on the power supply breaker(s).
Modem card failure.
Unprotected operation: Link out of operation. Protected operation: Link protection no longer available.
23
Modem Card Not Operational

Explanation
A specific modem card (fitted in the OmniBAS-2W /-4W indoor unit) has failed.
Indication
OmniBAS-2W: The led PWR on the modem card is off or red, meaning that the modem card has failed. OmniBAS-4W:
Causes & actions
# 1
Probable Causes
Implications
Suggested Recovery Procedure Replace the modem card (P6 procedure).
Modem card Unprotected operation: failure. Link out of operation. Protected operation: Link protection no longer available.
24
Outdoor Radio (ODU) Not Operational

Explanation
Incident that is observed locally and which is associated with a problem somewhere in the hardware chain: modem card coaxial cable outdoor unit (ODU).
Indication
a.
Change in Status of Front-panel Leds (Modem Card): The led ODU on the modem card: is off, meaning that the ODU is disabled (i.e. not powered from the interconnected modem card), lights up green, meaning that the ODU is present and not muted, blinks green, meaning that the ODU is present and muted, lights up amber, meaning that the ODU is present and not muted but has an alarm, blinks amber, meaning that the ODU is present and muted but has an alarm, lights up red, meaning that the ODU is not present or it has a power failure at its input, blinks red, meaning that the ODU is present but the modem ODU communication has errors.
OmniBAS-2W:
OmniBAS-4W:
b.
Listing of Relevant uni|MS Alarms:
Refer to section Outdoor Unit (ODU) Alarms, on page 111, where all the relevant alarms are explained.
25
Outdoor Radio (ODU) Not Operational, Continued

Causes & actions
# 1
Probable Causes ODU is disabled.
Implications
Suggested Recovery Procedure From the uni|MS management application, try re-activating ODU. (i.e. set DC Power = ON)
The coaxial cable, interconnecting the modem card with the ODU, is impaired. The coaxial cable, interconnecting the modem card with the outdoor radio box, is too long. ODU has failed. Modem card has failed.
Inspect coaxial cables terminations at both ends. Then, inspect the cable itself.
Investigate a different route that shortens the coaxial cables total length or replace the existing cable with another, better quality one.
Replace the ODU with a spare one (P8 procedure). Replace the modem card with a spare one (P6 procedure).
26

Recovery procedure
Execute one of the following three troubleshooting flowcharts to resolve the onsite problem, based on the observed status of the modem card ODU communication:
A. Modems ODU led is blinking red:
START
No
Coaxial No cable and its terminations ok?
Yes
Repair cable or terminals ODU led on modem flashing red?
No
Yes
Replace modem (P6 procedure)
No
ODU led on modem still flashing red?
Yes
END
Replace ODU (P8 procedure)
27

Recovery procedure, continued
B. Modems ODU led is off:
28

Recovery procedure, continued
C. Modems ODU led lights up red:
29
Radio Link Cannot Be Established

Explanation
Incident that might be observed locally after the commissioning of an OmniBAS link. In particular, the latter cannot be established. This procedure must be carried out for the one NOTE OmniBAS node or for both OmniBAS nodes participating in the problematic link.
Indication
a. Status of Front-panel Leds (Modem Card): OmniBAS-2W: The led MDM / MODEM on the modem card lights up amber, meaning that the link is not established. OmniBAS-4W:
30
Radio Link Cannot Be Established, Continued

Causes & actions
# 1
Probable Causes Wrong configuration settings.
Implications
Suggested Recovery Procedure Check the following and correct if found wrong: Modems configured channel size. Modems configured profile (links mode). ODUs configured transmit (Tx) frequency. ODUs configured transmit (Tx) power. (1) If ODU is disabled or muted. If ODU is looped.
Unprotected operation: Link out of operation. Protected operation: Link protection no longer available. 2 Interference
Check if other frequencies of other collocated links conflict with the links current Tx frequency.
(1)
If modulation is set to manual, ODU should support this Tx power value.
31

# 3
Probable Causes Faulty or wronglyinstalled hardware (1/4).
Implications Unprotected operation: Link out of operation. Protected operation: Link protection no longer available.
Suggested Recovery Procedure Step 1: Try to isolate the site with fault local or remote by setting a software ODU loopback (see below). If ODU does not support loopback, proceed to step 2:
a. Dispatch a technician to the remote site. b. Activate an ODU loopback at the local site and mute ODU at the remote site. Check if local site locks. c. Deactivate the ODU loopback at the local site and unmute ODU at the remote site. d. Activate an ODU loopback at the remote site and mute ODU at the local site. Check if remote site locks. e. Deactivate the ODU loopback at the remote site and unmute ODU at the local site.
32

Suggested Recovery Procedure If both local and remote sites lock, technicians at both sites should inspect the entire postODU paths (inclusive of wave-guide, coupler and antenna) and act accordingly. g. If, after setting the loopbacks, one or both sites are unable to lock, proceed to Step 2 in order to troubleshoot the specific (or both) sites accordingly. Step 2: Try to identify and replace the hardware that has failed (modem / ODU / cable / antenna). If loopback has revealed one problematic site, follow the instructions below for this specific site. Otherwise, follow instructions for both sites (the same holds true when ODU loopback is not supported). f.
The following actions imply services outage. For troubleshooters convenience, the IF coaxial cables should be marked at both ends with labels. If extra links (1+1 or N+0, N>1) are available onsite: a. Swap IF connectors at modem card side.
33

Suggested Recovery Procedure b. If the two modems operate in different frequencies (N+0), swap frequencies. Otherwise, skip this step. c. If problem persists for the same modem, then problem resides in modem itself. Replace with spare modem (P6 procedure). d. If problem passes to the other modem, then problem resides in ODU, IF cable or the post-ODU path. e. Inspect connectors at both sides of the IF cable and fix if necessary. f. Swap IF connectors at ODU side. g. If the two modems operate in different frequencies (N+0 configuration), swap frequencies. Otherwise, skip this step. h. If problem passes to the other modem, replace the IF cable. i. If problem persists for the same modem, then problem resides in ODU itself. Replace with spare ODU (P8 procedure). j. If problem persists, inspect the entire postODU path (inclusive of waveguide, coupler and antenna) and act accordingly.
34

# Probable Causes Faulty or wronglyinstalled hardware (4/4).
Suggested Recovery Procedure k. After resolving the hardware problem, restore the original cable configuration as well as the correct transmit frequencies (provided that they have been swapped in previous step). If no extra links are available onsite (1+0 case): a. Inspect connectors at both sides of the IF cable and fix if necessary. b. First, replace modem card (P6 procedure). If problem persists, replace ODU with a spare one of the same type (P8 procedure). c. If problem persists, inspect the entire post-ODU path (inclusive of waveguide, coupler and antenna) and act accordingly. d. If problem persists and modem still does not lock, replace the IF cable.
NOTE
Troubleshooting in 1+0 case should use trialand-error, since no action can secure the specific part that has failed (modem, ODU, antenna etc). Engineer may decide to follow this procedure for 1+1 or N+0 cases.
35

# 4
Probable Causes Radio transmission issues.
Suggested Recovery Procedure Check whether: The antenna is in good condition and properly installed. The antenna is installed at the correct height. The position of the antenna allows appropriate adjustments in azimuth and elevation planes, regarding the pointing toward the remote site. The antenna points to the right direction (i.e. toward the remote site). If antenna misaligned, carry out re-alignment, as described in P5 procedure. New obstacles appeared in the line-of-sight path, not present during the radio planning.
36
Radio Link Cannot Achieve Expected Performance

Explanation
Incident that might be observed locally after the commissioning of an OmniBAS link. In particular, the latter cannot achieve the expected radio performance. This procedure must be carried out for both NOTE OmniBAS nodes participating in the problematic link.
Indication
There are several indications that might reveal a degraded or poor radio performance, inclusive of: Lower RSSI. Lower SNR (Signal to Noise Ratio), resulted mostly from interference. Uncorrected FEC blocks, resulted from stressed operation of the LDPC (Low-Density Parity-Check) decoders.
Causes & actions
# 1
Implications
Suggested Recovery Procedure Check the following and correct if found wrong: Modems configured profile (i.e. links mode). ODUs configured transmit (Tx) frequency. ODUs configured transmit (Tx) power.
(1)
If ODU is looped.
Interference.
Check if other frequencies of other collocated links conflict with the links current Tx frequency.
(1)
37
Radio Link Cannot Achieve Expected Performance,

Continued
# 2
Implications Unprotected operation: Service degradation with errors or drops. Protected operation: Possible service degradation with errors or frequent switchovers.
Suggested Recovery Procedure Step 1: Try to isolate the site with fault local or remote by setting a software ODU loopback (see below). If ODU does not support loopback, proceed to step 2:
a. Dispatch a technician to the remote site. b. Activate an ODU loopback at the local site and mute ODU at the remote site. c. Start traffic test on one E1 port (using BER tester). Check if traffic errors are encountered at the local site. d. Deactivate the ODU loopback at the local site and unmute ODU at the remote site.
38

Continued
Suggested Recovery Procedure e. Activate an ODU loopback at the remote site and mute ODU at the local site. Check if remote site locks. f. Start traffic test on one E1 port (using BER tester). Check if traffic errors are encountered at the remote site. g. Deactivate the ODU loopback at the remote site and unmute ODU at the local site. h. If both local and remote sites measure well, technicians at both sites should inspect the entire postODU paths (inclusive of wave-guide, coupler and antenna) and act accordingly. i. If, after setting the loopbacks, one or both sites encounter traffic errors, proceed to Step 2 in order to troubleshoot the specific (or both) sites accordingly.
39

Continued
Suggested Recovery Procedure Step 2: Try to identify and replace the hardware that has failed (modem / ODU / cable / antenna). If loopback has revealed one problematic site, follow the instructions below for this specific site. Otherwise, follow instructions for both sites (the same holds true when ODU loopback is not supported).
The following actions imply services outage. For troubleshooters convenience, the IF coaxial cables should be marked at both ends with labels. If extra links (1+1 or N+0) are available onsite, then: a. Swap the IF cable connectors at modem card side. b. If the two modems operate in different frequencies (N+0), swap frequencies. Otherwise, skip this step. c. If problem persists for the same modem, then problem resides in modem itself. Replace with spare modem (P6 procedure).
40

Continued
Suggested Recovery Procedure d. If problem passes to the other modem, then problem resides in ODU, IF cable or the post-ODU path. e. Inspect connectors at both sides of the IF cable and fix if necessary. f. Swap the IF cable connectors at ODU side. g. If the two modems operate in different frequencies (N+0 configuration), swap frequencies. Otherwise, skip this step. h. If problem passes to the other modem, replace the IF cable. i. If problem persists for the same modem, then problem resides in ODU itself. Replace with spare ODU (P8 procedure). j. If problem persists, inspect the entire postODU path (inclusive of waveguide, coupler and antenna) and act accordingly. k. After resolving the hardware problem, restore the original cable configuration as well as the correct transmit frequencies (provided that they have been swapped in previous step).
41

Continued
Suggested Recovery Procedure If no extra links (1+1 or N+0) are available onsite, then: a. Inspect connectors at both sides of the IF cable and fix if necessary. b. First, replace modem card (P6 procedure). If problem persists, replace ODU with a spare one of the same type (P8 procedure). c. If problem persists, inspect the entire postODU path (inclusive of waveguide, coupler and antenna) and act accordingly. d. If problem persists (traffic has errors), replace the IF cable.
42

Continued
# 3
Probable Causes Radio transmission issues.
Suggested Recovery Procedure Check whether: The antenna is in good condition and properly installed. The antenna is installed at the correct height. The position of the antenna allows appropriate adjustments in azimuth and elevation planes, regarding the pointing toward the remote site. The antenna points to the right direction (i.e. toward the remote site). If antenna misaligned, carry out re-alignment, as described in P5 procedure. New obstacles appeared in the line-of-sight path, not present during the radio planning.
43

Continued
# 4
Probable Causes
Implications
Suggested Recovery Procedure Using appropriate isolators (the T devices in schematic below) and a spectrum analyzer featuring DC block capability, proceed as follows: a. Mute remote ODU. (1) b. Carry out an IF test (1). If the analyzer detects a signal, either interference is present, or the ODU malfunctions. c. If possible, carry out an RF test (2). If the analyzer detects a signal, then RF interference is present. If not, replace the ODU (P8 procedure) and repeat previous tests. If problem persists, there is likely IF interference, which needs further investigation.
Unprotected Radio interference. operation: Service degradation with errors or drops. Protected operation: Possible service degradation with errors or frequent switchovers.
(1)
If no spectrum analyzer is available, check whether RSSI is higher than -90 dBm. If it is (e.g. -85 dBm), RF interference is present and requires further investigation.
44
Ethernet Physical Layer is Down

Explanation
Incident that concerns the inability of an Ethernet line (associated with an OmniBAS-2W /-4W indoor unit) to pass Ethernet traffic.
Indication
a. Status of Front-panel Leds: (Indication for all problem causes except when Ethernet port negotiation on both sides of the Ethernet line is incorrectly configured). OmniBAS-2W Control Card
(shown: all versions)
Both leds on the corresponding Ethernet port are off.
OmniBAS-4W Control Card

(shown: electr. & opt. GbE versions)
45
Ethernet Physical Layer is Down, Continued

Causes & actions
# 1
Probable Causes Ethernet port (on OmniBAS indoor unit) is disabled.
Implications
Suggested Recovery Procedure From within uni|MS, click the respective Ethernet port, select Configuration tab and change Admin State value to up:
Incompatible negotiation mode (between the devices communicating over the Ethernet line). Interruption of associated services.
Ensure that both OmniBAS and the device at the other end of the Ethernet line have been configured for the same negotiation mode (Auto or Forced). If not, change the negotiation mode in one of the devices (e.g. the OmniBAS unit). Try Auto negotiation first, then Forced negotiation with identical settings for both sides of the Ethernet line. Refer to chapter 2 cases: Modem Link Failed Remote Modem Link Failed Alternatively, you can:

Link Loss Forwarding (LLF) is enabled and the respective Modem Link Failed alarm is present.
disable LLF (if not necessary), or change LLF settings if found to be incorrectly configured (e.g. LLF not enabled for both working and standby modem cards, or for all modem cards of the RLA group).
46
Ethernet Physical Layer is Down, Continued

# 4
Probable Causes The OmniBAS indoor unit is daisy-chained with another one and both units are synchronized from a Gigabit interface.
Implications
Suggested Recovery Procedure Change the synchronization source in one of the two cascaded OmniBAS units. From within uni|MS, click the OmniBAS NE, select Configuration tab and change the Configured Clock Source value to any available source, other than the Gb Ethernet one:
Impaired or deteriorated Ethernet cable.
Interruption of associated services.
Check cables entire run and terminations at both sides. Replace cable if necessary.
47
2.
Introduction
Troubleshooting of uni|MS Alarms

This chapter deals with those alarm situations that are notified to the users of uni|MS management software. Such notifications constitute the basis for remotely localizing the actual cause(s) of any incident. For troubleshooting guidelines on a specific alarm, search for the corresponding header (on the next pages) providing the alarms uni|MS description. For instance, to get troubleshooting information on the uni|MS alarm described as Fan Failure, refer to section Fan Failure on page 68.
In the next pages, reference lists are provided concerning the various uni|MS alarm groups: Reference List of Indoor Unit (NE) alarms. Modem Card alarms. Radio Link alarms. Outdoor Unit (ODU) alarms. E1 Line alarms. Ethernet Line alarms. Page 50 50 51 52 53 53
NOTE
The abbreviations used in table headers (on the following pages) mean the following: OB-2W ETH OmniBAS-2W Ethernet PTP modems. OB-2W 8E1 OmniBAS-2W 8E1. OB-2W 16E1 OmniBAS-2W 16E1. OB-2W RC OmniBAS-2W Ethernet PTP-R modems. OB-4W 2GbE OmniBAS-4W 2GbE. OB-4W 2GbE/2FE OmniBAS-4W 2GbE/2FE.
48
Troubleshooting of uni|MS Alarms, Continued

General alarms Severity (Default) Critical Major Critical
(1) (2)
Alarm Description Lost Communication with Element Equipment Extracted Part of Service has been Deactivated (1) (2) Part of Pending Service has been Activated AEnd Down (1) (2) ZEnd Down (1) (2) Management Connection Closed License Violation (1)
Alarm id (all OB models) 3 4 8 9 15 16 21 30 Continued on next page
minor
Critical Critical Major Warning
(1) (2)
Not supported in the uniMS Node Manager. Supported in the uni|MS Service Manager.
49

Reference list of alarms for Indoor Unit (NE) Alarm id
OB-2W ETH OB-2W 8E1 OB-2W RC OB-2W 16E1 OB-4W 2GbE OB-4W 2GbE/2FE
Alarm Description Input Alarm 1 Input Alarm 2 Input Alarm 3 Input Alarm 4 Fan Failure Fan Extracted PSU Failure Low Temperature High Temperature
Severity (Default) Warning Warning Warning Warning Critical Major Major Critical Critical
14002 14003 14004 14005 14044 14020 14021
24002 24003 24004 24005 24044 24020 24021
6002 6003 6006 6007 6011 6020 6021
Reference list of alarms for Modem Card Alarm id

Alarm Description Modem Failure Power Failure Invalid Modem Inserted PHY Modulation Failure Clock PLL Unlocked Receiver PLL Unlocked Transmitter PLL Unlocked Modem Chip Failure Modem Chip Unlocked
Severity (Default) Major Major Major Major Major Major Major Major Major
14040 14043 -
14046 14043 16044 16045 16046 16047 16048 16049
24046 24043 16044 16045 16046 16047 16048 16049
6040 6102 6043 -
16044 16045 16046 16047 16048 16049
50

Reference list of alarms for Radio Link Alarm id
Alarm Description Modem Link Failed Remote Modem Link Failed RAI Alarm
Modem Group 1-2
Severity (Default) Major Major Major Major Major Major Major Major
14041 14042 14024 16040 14051 -
24041 24042 24024
6041 6042 6026 6027
RAI Alarm
Modem Group 1-3
RAI Alarm
Modem Group 2-4
RAI Blocked Alarm ODU RSSI Alarm Rx Normalized MSE (SNR) Alarm Rx LDPC Decoders Stress Alarm East Port (Modem 2) of Ring Failure West Port (Modem 1) of Ring Failure
16040 24051 16041
16040 6051
Major
16042
Warning
16030
16030
Warning
16031
16031
51

Reference list of alarms for Outdoor Unit (ODU) Alarm id
Alarm Description ODU Communication Failure ODU Pout ALC Alarm ODU Rx PLL LD Alarm ODU Tx PLL LD Alarm ODU Tx Configured Frequency Out of Range Alarm ODU RF PLL LD Alarm ODU MW PLL LD Alarm ODU Loopback PLL LD Alarm Tx ODU Configured Power Out of Range Alarm ODU High Temperature Alarm ODU RSSI Rx User Alarm ODU Min Pif Alarm ODU Model Alarm ODU H/W Bandwidth Alarm ODU cable Calibration Alarm ODU Max Pif Alarm ODU Low If Alarm ODU Low Temperature Alarm
Severity (Default) Critical Critical Critical Critical Warning Critical Critical
14050 14052 14053 14054 14055 14056 14057 14058 14059 -
24050 24052 24053 24054 24055 24056 24057 24058
6050 6052 6053 6054 6055
6056 6057 6058
minor
Warning
Critical Major Warning Major Warning Critical Warning Critical Warning
14062 14066 14067 14090 14091 14092 14093 14094 14100 -
24062 24066 24067 24090 24091 24092 24093 24094 24100
6062 6066 6067 6090 6091 6092 6093 6094 6100 Continued on next page
52

Reference list of alarms for E1 Line Alarm id
Alarm Description E1 Line LOS E1 Line LOF E1 Line AIS E1 Line RAI E1 Line Admin Down E1 is Looped E1 Local Loop E1 Remote Loop
Severity (Default) Major Major Major Major Major Warning Warning Warning
14070 14071 14072 14073 14074 16043 -
24070 24071 24072 24073 24074 16105 16106
6070 6071 6072 6073 6074 16043 -
Reference list of alarms for Ethernet Line Alarm id

Alarm Description SFP Tx Fault SFP Rx LOS Ethernet Link Down
Severity (Default) Major Major Major
14080 14081 14082
24080 24081 24082
6080 6081 6082
53
General Alarms Lost Communication with Element

Explanation
Cannot remotely communicate with the OmniBAS-2W /-4W system through the inband or the outband management path.
Indication
Issuance of an alarm denoting the loss of management communication with the OmniBAS system.
54
Lost Communication with Element, Continued

Causes & actions
Probable Causes (see below) Site power failure. Impaired Ethernet cabling.
Implications
Suggested Recovery Procedure
1 2
Traffic loss. OmniBAS cannot be managed. Also, possible traffic loss. Traffic loss. OmniBAS cannot be managed. Also, possible traffic loss. Using the respective management system(s), check DCN end-to-end to isolate the impacted segment and resolve any connectivity problem. Change the Firewall settings accordingly. Refer to the uni|MS Firewall Setup Administrator Manual for those management ports to be excluded from Firewall.
System reboot in progress. Hardware has failed.
If problem is not restored in the next few minutes (since the instance of alarm issuance), dispatch a technician locally to carry out the local troubleshooting procedure as described on the next pages.
Broken DCN connection. OmniBAS system cannot be managed.
Wrong Firewall setup.
55

Local troubleshooting procedure
To carry out local OmniBAS troubleshooting, proceed as follows: Step 1 Action Check for site power issues: Check whether OmniBAS is powered up and runs properly. If yes, proceed to next step. If not, inspect the local DC power supply source. Check for impaired Ethernet cables: Visually check for activity on the OmniBAS Ethernet port used for carrying management traffic. In case of no activity, inspect Ethernet cabling and replace if found impaired. Otherwise, proceed to next step. Check for impact on traffic: Make a local survey to check if services are affected. If yes (despite the fact that Ethernet cabling is not the cause of the problem), replace the OmniBAS control card (P7 procedure), or replace the whole OmniBAS unit with a spare one (if available). Check for broken DCN connectivity: Use a laptop with appropriate Ethernet and IP settings to locally connect to an external switch and ping the uni|MS Server / Host. If necessary, change the settings of the switch or make corrective actions to the DCN equipment. In case of no ping response, resolve the DCN connectivity problem using the respective DCN management system(s).
56

Local troubleshooting procedure (continued)
Step 5
Action Checking local communication with OmniBAS: Outband management connection: a. Disconnect the outband management cable from the OmniBAS Ethernet port. b. Connect a laptop with appropriate IP settings to the same OmniBAS Ethernet port. c. Ping the OmniBAS unit. Inband management connection: a. Connect a laptop with appropriate IP settings to a free outband management port on the OmniBAS unit. b. Check whether inband management VLAN ID: is associated with the correct Ethernet port used for inband management. has the highest priority over the air. c. Setup a Gigabit (GbE) or Fast Ethernet (FE) port to be used for inband management and configure for untagged traffic. Set as ports default VLAN the value shown next to VLAN ID field in the Inband Management Parameters group box: (Right click OmniBAS NE > Configuration tab > Inband / Outband / RTC tab).
d. Connect the laptop to the configured inband management port. e. Ping the OmniBAS node.
57

Local troubleshooting procedure (continued)
Step 6
Action In case of no ping response (or in case the IP settings are unknown), connect the laptop to the AUX port on the OmniBAS control card and find the IP address of the OmniBAS node (P3 procedure). Then, re-try to connect using this IP address. If no remedies work, reset the OmniBAS node. WARNING: Resetting OmniBAS will interrupt all node services.
If problem still persists, replace the control card (P7 procedure).
End of procedure.
58
Equipment Extracted
Explanation
Card extracted from a specific OmniBAS-2W /-4W chassis slot for unknown reason.
Indication
Issuance of an alarm denoting the card extraction.
Causes & actions
# 1
Probable Causes Card extracted intentionally (e.g. for maintenance purposes).
Implications
Suggested Recovery Procedure Manually cease the alarm. From the uni|MS management, perform the Remove Extracted Equipment action on that card. Dispatch a technician locally to correctly reinsert and/or replace the card. In the latter case, refer to the corresponding troubleshooting procedure (P2/P4/P6/P7).
Card selfextracted or has failed.
Service interruption (in case of unprotected card operation).
59
Part of Service has been Deactivated

Explanation
The corresponding OmniBAS-2W /-4W service is partially activated, as one or more service fragments are non-functional or not existing any more. This alarm is associated with the uni|MS Service Manager for OmniBAS.
Indication
Issuance of an alarm denoting that the OmniBAS service is partially (and not fully) activated.
Causes & actions
# 1
Probable Causes Service fragment has been deactivated or deleted from the respective OmniBAS system.
Implication
Suggested Recovery Procedure Manually activate service: a. Perform an Activate Service action to fully activate service. b. Perform a Validate Service action to verify the new service state.
Communication with the associated OmniBAS system cannot be established.
End-to-end service is interrupted, as one or more service fragments are not working.
For detailed instructions, refer to case: Lost Communication with Element
60
Part of Pending Service has been Activated

Explanation
The corresponding service fragment being in pending state (for several reasons) and which it is part of an OmniBAS-2W /-4W service has been activated. (1) This alarm is associated with the uni|MS Service Manager for OmniBAS.
Indication
Issuance of a notification denoting that the specific service fragment has been activated.
Causes & actions
Probable Causes
Implications
Service fragment was in pending state due to the fact that uni|MS was unable to connect to the respective OmniBAS system. Service fragment was in pending state due to the fact that the respective OmniBAS system has failed. Service fragment was in pending state due to resources unavailability. None. None.
(1)
If the specific service fragment is the last pending one (within the same service path), then service will also be activated.
61
AEnd Down
Explanation
The OmniBAS-2W /-4W end-to-end service has been reported as being down from the starting (AEnd) side. The traffic flow between the two ends of the service path has been interrupted. This alarm is associated with the uni|MS Service Manager for OmniBAS.
Indication
Issuance of an alarm denoting that the starting (AEnd) point of the end-to-end service has problem.
Causes & actions
# 1
Probable Causes The respective OmniBAS system has failed.
Implications Service interrupted.
Suggested Recovery Procedure Check for active alarms associated with the specific OmniBAS system and act as instructed in the corresponding sections of this document (Chapter 2).
62
ZEnd Down
Explanation
The OmniBAS-2W /-4W end-to-end service has been reported as being down from the ending (ZEnd) side. The traffic flow between the two ends of the service path has been interrupted. This alarm is associated with the uni|MS Service Manager for OmniBAS.
Indication
Issuance of an alarm denoting that the ending (ZEnd) point of the end-to-end service has problem.
Causes & actions
# 1
Probable Causes The respective OmniBAS system has failed.
Implications Service interrupted.
Suggested Recovery Procedure Check for active alarms associated with the specific OmniBAS system and act as instructed in the corresponding sections of this document (Chapter 2).
63
Management Connection Closed

Explanation
The controller of the associated OmniBAS-2W /-4W system cannot internally communicate with a specific supervised card. The communication between uni|MS and the OmniBAS system is not affected by this alarm.
Indication
Alarm issued by the OmniBAS control card to denote an internal communication problem with a specific card (e.g. Modem Card 1).
Causes & actions
# 1
Probable Causes The concerned card is currently rebooting, is not correctly inserted, or it has just failed.
Implications Interruption of associated services.
Suggested Recovery Procedure a. Wait to see if alarm ceases (as a result of card reboot and re-activation). b. Dispatch a technician locally to inspect the card and act as instructed in the relevant cases of Chapter 2.
64
License Violation
Explanation
Violation of the number of ODUs that can be managed by uni|MS.
Indication
Issuance of an alarm denoting that the number of ODUs has exceeded the license limit.
Causes & actions
# 1
Probable Causes Number of ODUs to be managed by uni|MS is greater than the number of license keys.
Implications uni|MS will continue to warn for 30 days before server is disabled.
Suggested Recovery Procedure Obtain extra license keys to be able to manage the additional ODUs.
65
Indoor Unit Alarms Input Alarm 1 /2 /3 /4

Explanation
The corresponding device (sensor, door switch, etc.), wired onto the AUX receptacle of the control card of the OmniBAS-2W /-4W indoor unit, has been activated or disconnected. (1)
Indication
a. Listing of Relevant Alarms:

Alarm Description Input Alarm 1 Input Alarm 2 Input Alarm 3 Input Alarm 4 Severity (Default) Warning Warning Warning Warning Alarm id OB-2W ETH 14002 14003 14004 14005 OB-2W 8E1 14002 14003 14004 14005 OB-2W 16E1 24002 24003 24004 24005 OB-2W RC 14002 14003 14004 14005 OB-4W 2GbE 6002 6003 OB-4W 2GbE/2FE 6002 6003 -
Example list (OmniBAS-4W):
b. Change in Elements Monitoring Status: (Configuration > External Alarms tab) The corresponding Input led lights up red (2):
OmniBAS-4W:
OmniBAS-2W:

(1) (2)
This alarm concerns only the occupied AUX inputs.
NOTE: Regarding the unoccupied AUX inputs, the corresponding led also lights up red to indicate the absence of a connected device which is normal and not an alarm.
66
Input Alarm 1 /2 /3 /4, Continued

Causes & actions
# 1
Probable Causes Maintenance of equipment. Activation of the connected device.
Implications None.
Suggested Recovery Procedure None. Confirm the onsite intervention (i.e. whether it is scheduled or urgent). Investigate the reason causing the alarm (open door, premises trespass, etc.). Call for dispatching a technician locally to inspect.
Unknown.
Device Inability to disconnection. further monitor the corresponding external alarm.
67
Fan Failure
Explanation
For OmniBAS-2W Systems: The fan subsystem of the specific modem card is malfunctioning or it has failed. For OmniBAS-4W Systems: The fan tray is malfunctioning or it has failed.
Indication

Alarm Description Fan Failure Severity (Default) Critical Alarm id OB-2W ETH 14044 OB-2W 8E1 14044 OB-2W 16E1 24044 OB-2W RC 14044 OB-4W 2GbE 6006 OB-4W 2GbE/2FE 6006
Also, the respective alarm (see table below) might also be listed, denoting an excessive (i.e. unsafe) temperature as a result from the prolonged time the fan tray was out of operation:
Alarm Description High Temperature Severity (Default) Critical Alarm id
OB-2W ETH OB-2W 8E1 OB-2W 16E1 OB-2W RC OB-4W 2GbE OB-4W 2GbE/2FE
14021
14021
24021
14021
6021
6021
b. Change in Elements Monitoring Status: (Click on NE > Status > Equipment tab) For OmniBAS-2W Systems: The displayed status next to: Fan Tray 1 (for left modem slot) = Failure, or Fan Tray 2 (for right modem slot) = Failure,
depending on the concerned modem card (see example below).
For OmniBAS-4W Systems: The displayed status next to Fan Tray = Failure.
68
Fan Failure, Continued

Causes & actions
# 1
Probable Causes Air exhaust slots are clogged. Fan tray not correctly inserted in the chassis slot. (1) Fan is not powered. (2)
Implications
Suggested Recovery Procedure Remove all objects impeding the air flow. Remove the fan tray from the chassis and re-install it correctly to check whether it operates or not. Check whether the fans power cable is correctly plugged into the corresponding receptacle on the modems pcb. Carefully extract the modem (OmniBAS-2W) or the fan tray (OmniBAS-4W) and check for obstacles impeding the rotation of the fan. OmniBAS-2W: Replace the modem card with a spare one of the same type (P6 procedure). OmniBAS-4W: Replace the fan tray with a spare one (P2 procedure).
Obstacle impedes rotation of internal fins. Fan has failed.
On-site visit is needed. Link may temporarily be interrupted.
Precautions
This specific problem should be fixed the sooner possible, as overheat could harm the housed electronics with possible impact on services.
(1) (2)
Concerns OmniBAS-4W systems only. Concerns OmniBAS-2W systems only.
69
Fan Extracted
Explanation
The fan tray of the OmniBAS-4W indoor unit has been extracted.
Indication

Alarm Description Fan Extracted Severity (Default) Major Alarm id OB-2W ETH OB-2W 8E1 OB-2W 16E1 OB-2W RC OB-4W 2GbE 6007 OB-4W 2GbE/2FE 6007
b. Change in Elements Monitoring Status: (Click on NE > Status > Equipment tab) The displayed status next to Fan Tray = Fan Extracted.
Causes & actions
# 1
Probable Causes Maintenance of equipment.
Implications None.
Suggested Recovery Procedure Confirm onsite intervention (i.e. whether visit is scheduled or urgent).
70
PSU Failure
Explanation
One of the two power supply cards fitted in the OmniBAS-4W unit is malfunctioning or has failed.
Indication

Alarm Description PSU Failure Severity (Default) Major Alarm id OB-2W ETH OB-2W 8E1 OB-2W 16E1 OB-2W RC OB-4W 2GbE 6011 OB-4W 2GbE/2FE 6011
Causes & actions
# 1
Probable Causes Power supply card not correctly installed. Power supply card has failed.
Implications
Suggested Recovery Procedure Extract and re-insert card correctly into the chassis slot.
Power supply redundancy no longer available. Onsite visit should be scheduled.
a. Remove power cable. b. Extract the power supply card and install a spare one. c. Secure the new card in place. d. Re-install the power supply cable.
71
Low Temperature
Explanation
The configured threshold (see below), regarding the lowestallowable operating temperature for the OmniBAS-2W /-4W indoor unit, has been exceeded.
Indication

Alarm Description Low Temperature Severity (Default) Critical Alarm id OB-2W ETH 14020 OB-2W 8E1 14020 OB-2W 16E1 24020 OB-2W RC 14020 OB-4W 2GbE 6020 OB-4W 2GbE/2FE 6020
b. Change in Elements Monitoring Status: (Click on NE > Configuration tab > Threshold tab)
Causes & actions
# 1
Probable Causes Wrong setting regarding the low temperature threshold.
Implications
Suggested Recovery Procedure a. Check the low temperature threshold value. b. If threshold is high, re-adjust it to -5 oC. Call for dispatching a technician to inspect equipment premises.
System performance may be affected.
xtra-low room temperature.
Control cards temperature monitoring subsystem has failed.
Inability to further monitor the system temperature.
Replace the control card with a spare one (P7 procedure).
72
High Temperature
Explanation
The configured threshold (see below), regarding the highestallowable operating temperature of the OmniBAS-2W /-4W indoor unit, has been exceeded.
Indication

Alarm Description High Temperature Severity (Default) Critical Alarm id OB-2W ETH 14021 OB-2W 8E1 14021 OB-2W 16E1 24021 OB-2W RC 14021 OB-4W 2GbE 6021 OB-4W 2GbE/2FE 6021
b. Change in Elements Monitoring Status: (Click on NE > Configuration tab > Threshold tab)
c. Listing of Temperature Values (per Card): Click on NE > Status tab > Equipment tab (below: example for OmniBAS-4W)
73
High Temperature, Continued

Causes & actions
# 1
Probable Causes High room temperature.
Implications Possible equipment damage due to overheat. Degraded system performance and/or possible equipment damage due to overheat.
Suggested Recovery Procedure Call for dispatching a technician to inspect equipment premises. a. Check the temperatures of all cards to detect the root cause of overheat. b. Check for other alarms that might be associated with overheat (such as a fan alarm). c. Call for dispatching a technician onsite to inspect equipment. Check the high temperature threshold value and increase if possible. The new value should be within the operating range specified by the manufacturer. Replace the control card with a spare one (P7 procedure).
Hot-spot inside the indoor unit.
Wrong setting regarding the high temperature threshold.
System performance may be affected.
Control cards temperature monitoring subsystem has failed.
Inability to further monitor the system temperature.
74
Modem Card Alarms Modem Failure

Explanation
The modem card fitted in the OmniBAS-2W / 4W chassis is malfunctioning or it has failed.

Indication
Alarm Description Modem Failure Severity (Default) Major Alarm id OB-2W ETH 14040 OB-2W 8E1 14040 OB-2W 16E1 OB-2W RC OB-4W 2GbE 6040 OB-4W 2GbE/2FE -
b. Change in Elements Monitoring Status: (Click on Modem > Status tab, Alarms group box) Modem Failure alarm = True:
Causes & actions
# 1
Probable Causes
Implications
Suggested Recovery Procedure a. From the management application, click on modem, right click and select Reboot to reset modem. b. If problem persists, replace the modem (P6 procedure).
Modem card Unprotected operation: has failed. Link out of operation. Protected operation: Link protection no longer available.
75
Power Failure
Explanation
There is a problem with one (or more) operating DC voltages internally the specific modem card of the OmniBAS-2W /-4W indoor unit. These DC voltages include: 3.3 V (modems input voltage). 48 V (modems output / ODUs input voltage). 1.2 V / 1.8 V / 2.5 V / 10 V / 5.1 V (other voltages).
Indication

Alarm Description Power Failure Severity (Default) Major Alarm id OB-2W ETH OB-2W 8E1 OB-2W 16E1 24046 OB-2W RC 14046 OB-4W 2GbE 6102 OB-4W 2GbE/2FE 6102
b. Visual Indication (on the Connected Modems Front Panel): OmniBAS-2W: The led PWR on the concerned modem card lights up red meaning that there is problem with cards power. OmniBAS-4W: The led PWR on the concerned modem card lights up amber meaning that there is problem with cards power.
76
Power Failure, Continued

Causes & actions
# 1
Probable Causes
Implications
77
Invalid Modem Inserted

Explanation
A specific modem card fitted in the OmniBAS-2W /-4W chassis is either of invalid type or it has failed.
Indication

Alarm id OB-2W ETH 14043 OB-2W 8E1 14043 OB-2W 16E1 24043 OB-2W RC 14043 OB-4W 2GbE 6043 OB-4W 2GbE/2FE 6043
Alarm Description Invalid Modem Inserted
Severity (Default) Major
Causes & actions
# 1
Probable Causes
Implications
Suggested Recovery Procedure Extract the modem card and replace with another one of the correct type. Replace the modem card with a spare one of same type (P6 procedure).
Invalid OmniBAS link modem card cannot be type. established. Modem card has failed.
78
PHY Modulation Failure

Explanation
The modem card, fitted in the OmniBAS-2W / 4W chassis, is malfunctioning or the ODU does not support the links configured physical modulation (e.g. 256-QAM).

Indication
Alarm Description PHY Modulation Failure Severity (Default) Major Alarm id OB-2W ETH OB-2W 8E1 OB-2W 16E1 16044 OB-2W RC 16044 OB-4W 2GbE OB-4W 2GbE/2FE 16044
b. Change in Elements Monitoring Status: (Click on Modem > Status tab, Alarms group box) PHY Modulation Failure = True:
Causes & actions
# 1
Probable Causes Wrong ODU model installed. Wrong modulation selected for the specific ODU.
Implications
Suggested Recovery Procedure Replace ODU with another of the correct type (P8 procedure). Select an appropriate modulation that is supported by the ODU.
Links modulation is not supported by the ODU.
79
PHY Modulation Failure, Continued

# 3
Probable Causes
Implications
Suggested Recovery Procedure a. From the management application, click on modem, right click and select Reboot to reset modem. b. If problem persists, check whether the modem is securely installed in its slot. c. If it is installed properly, replace the modem card with a spare one (P6 procedure).
80
Clock PLL Unlocked

Explanation
Indication

Alarm id OB-2W ETH OB-2W 8E1 OB-2W 16E1 16045 OB-2W RC 16045 OB-4W 2GbE OB-4W 2GbE/2FE 16045
Alarm Description Clock PLL Unlocked
b. Change in Elements Monitoring Status: (Click on Modem > Status tab, Alarms group box) Clock PLL Unlocked = True:
Causes & actions
# 1
Probable Causes
Implications
Modem card Link with has failed. possible errors or out of operation.
81
Receiver PLL Unlocked

Explanation

Indication
Alarm Description Receiver PLL Unlocked Severity (Default) Major Alarm id OB-2W ETH OB-2W 8E1 OB-2W 16E1 16046 OB-2W RC 16046 OB-4W 2GbE OB-4W 2GbE/2FE 16046
b. Change in Elements Monitoring Status: (Click on Modem > Status tab, Alarms group box) Receiver PLL Unlocked = True:
Causes & actions
# 1
Probable Causes
Implications
82
Transmitter PLL Unlocked

Explanation
Indication

Alarm Description Transmitter PLL Unlocked
b. Change in Elements Monitoring Status: (Click on Modem > Status tab, Alarms group box) Transmitter PLL Unlocked = True:
Causes & actions
# 1
Probable Causes
Implications
83
Modem Chip Failure

Explanation
Indication

Alarm Description Modem Chip Failure
b. Change in Elements Monitoring Status: (Click on Modem > Status tab, Alarms group box) Modem Chip Failure = True:
Causes & actions
# 1
Probable Causes
Implications
84
Modem Chip Unlocked

Explanation
Indication

Alarm Description Modem Chip Unlocked
b. Change in Elements Monitoring Status: (Click on Modem > Status tab, Alarms group box) Modem Chip Unlocked = True:
Causes & actions
# 1
Probable Causes
Implications
85
Radio Link Alarms Modem Link Failed

Explanation
There is a radio communication error in the direction from the remote station to the local one (to which the uni|MS management application is connected):
Indication

Alarm Description Modem Link Failed Severity (Default) Major Alarm id OB-2W ETH 14041 OB-2W 8E1 14041 OB-2W 16E1 24041 OB-2W RC 14041 OB-4W 2GbE 6041 OB-4W 2GbE/2FE 6041
b. Change in Elements Monitoring Status: (Select local NE > Status tab > Link Summary tab > Modem x) Link Status (local / remote) = Wait Lock or Failed (status denoted for local modem on the left, see below).
Causes & actions
Refer to causes & actions of the following case: Radio Link is Down
86
Remote Modem Link Failed

Explanation
There is a radio communication error in the direction from the local station to the remote one. For reference, the uni|MS management application is connected to the local station.
Indication

Alarm Description Remote Modem Link Failed
b. Change in Elements Monitoring Status: (Select remote NE > Status tab > Link Summary tab > Modem x) Link Status (local / remote) = Locked / Unknown or Unlocked (status denoted for remote modem on the right, see below).
Causes & actions
Refer to causes & actions of the following case: Radio Link is Down
87
RAI Alarm (Modem Group 1-2 /1-3 /2-4)

RAI mechanism illustrated
The following schematics illustrate the mechanism behind the issuance of a Remote Alarm Indication (RAI) alarm, with regard to an OmniBAS-2W /-4W link operating in protected 1+1 Hot Standby (HSB) mode: a. Normally, each working (W) ODU transmits to both ODUs at the other side of the link. The standby (S) ODUs just receive and do not transmit.
b. In case one of the ODUs (e.g. ODU A1) stops transmitting, the two ODUs at the other side of the link stop listening and the working ODU (ODU B1) dispatches a RAI alarm. Switchover to Modem A2 is about to occur after the RAI timeout. c. If the link is reestablished within the predefined RAI timer value, the RAI alarm ceases. Otherwise, and upon RAI timer elapse, the OmniBAS at site A issues a RAI blocked alarm for Modem A1. In such a case, local inspection at the site A is required.
88
RAI Alarm (Modem Group 1-2 /1-3 /2-4), Continued

Explanation
A specific x-y pair of OmniBAS-2W /-4W modems (see below), which operate in protected 1+1 HSB mode, have received a RAI from the remote link partner. With the RAI alarm, the remote link partner declares its inability to receive a radio signal from the currently-working modem of the concerned x-y pair.
OmniBAS-2W
OmniBAS-4W
89

Indication

Severity (Default) Major Major Major Alarm id OB-2W ETH 14024 OB-2W 8E1 14024 OB-2W 16E1 24024 OB-2W RC OB-4W 2GbE 6026 6027 OB-4W 2GbE/2FE 6026 6027
Alarm Description RAI Alarm Modem Group 1-2 RAI Alarm Modem Group 1-3 RAI Alarm Modem Group 2-4
Upon RAI timer elapse, an alarm with id = 16040 might also be listed to denote that switchover to the standby modem card could not be executed.
b. Change in Elements Monitoring Status: (Click on NE > Configuration > Modem > Hot Standby tab) The corresponding led lights up red to indicate RAI (see example below for OmniBAS-4W, Pair 1-3):
90

Causes & actions
(The troubleshooting below will be carried out only upon existence of a RAI blocked alarm associated with the specific modem). # 1 Probable Causes Modem malfunctioned. Implications Suggested Recovery Procedure a. From the management application, click on modem, right click and select Reboot to reset modem. b. Check whether both the RAI alarm and the RAI blocked alarm have ceased. Link protection is no longer available. First inspect cables terminations at both ends. Then, inspect the cable itself.
The coaxial cable, interconnecting the modem with the outdoor radio, is impaired. Modem failed.
Replace the modem card with a spare one (P6 procedure). (1) Replace the outdoor radio box with a spare one having exactly the same specifications (P8 procedure). (1)
The outdoor radio (connected with the modem) has internal problem.
(1)
First, check for other modem or ODU alarms.
91
RAI Blocked Alarm

Explanation
Following the dispatch of a RAI alarm from the remote link partner, the local (working) modem issues a RAI Blocked alarm to notify the management that a switchover to the standby modem could not be executed.
For the description of the RAI mechanism, please refer to the preceding section: RAI Alarm (Modem Group 1-2 /1-3 /2-4).
92
RAI Blocked Alarm, Continued

Indication

Alarm Description RAI Blocked Alarm Severity (Default) Major Alarm id OB-2W ETH 16040 OB-2W 8E1 16040 OB-2W 16E1 16040 OB-2W RC OB-4W 2GbE 16040 OB-4W 2GbE/2FE 16040
Alarm Description RAI Alarm Modem Group 1-2 RAI Alarm Modem Group 1-3 RAI Alarm Modem Group 2-4
Severity (Default) Major Major Major
Alarm id OB-2W ETH 14024 OB-2W 8E1 14024 OB-2W 16E1 24024 OB-2W RC OB-4W 2GbE 6026 6027 OB-4W 2GbE/2FE 6026 6027
b. Change in Elements Monitoring Status: (Click on Modem card > Status tab) The RAI Blocked status is True to indicate that the specific modem has issued a RAI Blocked alarm:
93
RAI Blocked Alarm, Continued

Causes & actions
(To identify the modems mentioned below, please refer to the illustrative schematic on page 92). # 1 Probable Causes Working modem (A1) malfunctioned. Implications Suggested Recovery Procedure Note: Before proceeding, ensure that modem (A2) has been tested and found to be fully operational. a. From the management application, click on modem (A1), right click and select Reboot to reset. b. If RAI Blocked alarm still persists, replace modem (A1)(P6 procedure). First inspect cables terminations at both ends. Then, inspect the cable itself.
Possible unavailability of link protection. 2 The coaxial cable, interconnecting the modem with the outdoor radio, is impaired. The outdoor radio (connected with the modem) has problem.
Replace the outdoor radio box with a spare one having exactly the same specifications (P8 procedure).
94
ODU RSSI Alarm

Explanation
The factory-predefined RSSI threshold for the specific ODU has been exceeded. The ODU cannot operate reliably due to extremely-weak signal reception, or due to a hardware failure.
Indication

Alarm id
Alarm Description ODU RSSI Alarm
14051
14051
14051
24051
6051
6051
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The RSSI (factory) indicator turns to red (see below) to denote that the factory-preset RSSI threshold has been exceeded. The current received signal strength is shown next to the RSSI (dBm) field:
95
ODU RSSI Alarm, Continued

NOTE
Whether check of ODU alignment or LOS will be needed first is up to the technician and the installation conditions (antenna size and distance). For short distances, LOS will be checked first. For large antennas (over 3 m in diameter), alignment will be carried out last, etc.
Causes & actions
# 1
Implications
Suggested Recovery Procedure Check the following and correct if found wrong: ODUs configured transmit (Tx) frequency. ODUs configured transmit (Tx) power
(1)
If ODU is disabled or muted.
2 3
Misalignment of antenna(s). Local receiver has failed. Remote site problem. Problematic installation (antenna ODU fixing, etc.). New obstacles are blocking the Line of Sight (LOS).
Poor radio performance and/or services unavailability.
Re-align antennas at both sites (P5 procedure). Replace local outdoor radio box with a spare one (P8 procedure). Carry out troubleshooting at remote site. Visually inspect locally for hardware deterioration / connector displacement and act accordingly. Possibly radio re-planning will be needed.
4 5
(1)
96
ODU RSSI Alarm, Continued

Recovery procedure
Execute the following troubleshooting flowchart to resolve the low RSSI problem: (A persistent link problem is assumed, not caused by faulty or wrongly-installed hardware, and not being an isolated temporary incident that might be caused by extreme weather conditions).
NOTE
If new obstacles are blocking the Line of Sight (LOS), then radio re-planning should be carried out.
97
Rx Normalized MSE (SNR) Alarm

Explanation
The predefined threshold for received signals normalized MeanSquared Error (MSE), or else Signal to Noise Ratio (SNR), has been exceeded. The high noise and interference in the inbound signal hampers modems demodulation task and degrades links performance.
Indication

Alarm Description Rx Normalized MSE (SNR) Alarm
b. Change in Elements Monitoring Status: (Click on Modem > Status tab, Alarms group box) Rx Normalized MSE (SNR) Failure = True. (The predefined threshold for Rx Normalized MSE is shown next to the SNR (dB) field).
98
Rx Normalized MSE (SNR) Alarm, Continued

NOTE
Before proceeding to troubleshooting, check for existence of active ODU RSSI alarm. If so, first troubleshoot it as instructed in the respective section.
Causes & actions
# 1
Probable Causes Link cannot operate in the selected fixed modulation. Presence of multipath interference (despite the fact that reception is strong).
Implications
Suggested Recovery Procedure Change links operation to adaptive and check if alarm ceases. a. Only for links with Space Diversity (without coupler): carry out a modem switchover and check if alarm ceases. b. Provided that the fade margin of the link always exceeds the requirement for proper annual operation, then: 1. Try reducing the transmit power at the remote site. If alarm ceases, go to step 2d, otherwise proceed. 2. Try misaligning the antenna. If alarm ceases, go to step 2d. c. Carry out radio replanning. d. End of procedure.
Link degradation and/or interruption of services.
99
Rx Normalized MSE (SNR) Alarm, Continued

# 3
Probable Causes Interference.
Implications
Suggested Recovery Procedure Refer to case: Radio Link Cannot Achieve Expected Performance, probable cause #3.
Radio transmission issues.
Link degradation and/or interruption of services.
Refer to case: Radio Link Cannot Be Established, probable cause #4. Refer to case: Modem Link Failed, probable cause #2.
Hardware problem.
100
Rx LDPC Decoders Stress Alarm

Explanation
The predefined error correction threshold has been exceeded. The inbound radio signal has so many errors that the modems LDPC forward error correction mechanism is pushed beyond its capabilities and becomes practically ineffective.
Indication

Alarm Description Rx LDPC Decoders Stress Alarm
b. Change in Elements Monitoring Status: (Click on Modem > Status tab, Alarms group box) Rx LDPC Decoders Stress Failure = True. (The predefined threshold for LDPC Decoders Stress is shown next to the LDPC Decoders Stress field).
101
Rx LDPC Decoders Stress Alarm, Continued

Causes & actions
# 1
Probable Causes Predefined LDPC threshold has been set too high.
Implications None. Relevant alarm will be issued more frequently denoting false stress of the LDPC decoders.
Suggested Recovery Procedure a. Click on NE. b. Select Configuration tab > Thresholds tab. c. In the PTP Modem group box > LDPC Decoders Stress header, double-click the threshold value of the concerned modem (see below). d. In this field, type a lower ratio between
10-6 (1E-06) and 100 (1E00).(1)
Reception has lots of errors.
Poor link performance and/or interruption of services.
Refer to cases: Modem Link Failed Radio Link Cannot Achieve Expected Performance
(1)
Default setting.
102
East Port (Modem 2) of Ring Failure

Explanation
The OmniBAS-2W /-4W node, which participates in an Ethernet Ring Protection (ERP) ring, has stopped receiving control messages from its east-side ring partner (see below).
103
East Port (Modem 2) of Ring Failure, Continued

Indication

Alarm id OB-2W ETH 16030 OB-2W 8E1 16030 OB-2W 16E1 16030 OB-2W RC OB-4W 2GbE 16030 OB-4W 2GbE/2FE 16030
Alarm Description East Port (Modem 2) of Ring Failure
Severity (Default) Warning
In case the link (between the two OmniBAS peers in the ring) is down, the following alarms will be listed:
b. Change in Elements Monitoring Status: (Click on NE > Configuration tab > Modem tab > Ring tab) The Signal Fail East status is Active to indicate that no control messages are received from the east side of the OmniBAS ring.
104

Causes & actions
# 1
Probable Causes ERP not yet configured for the links peer.
Implications
Suggested Recovery Procedure Most probably, there is no issuance of Modem Link Failed and Remote Modem Link Failed alarms. From the uni|MS application, click the OmniBAS NE. Then, select Configuration > Modem > Ring tab and configure the ERP settings for the respective modem card. Refer to cases: Modem Link Failed Remote Modem Link Failed
The corresponding link (participating in the OmniBAS ring) is down. All remaining links remain up.
ERP no longer available. Services remain unaffected but ERP must be restored the sooner possible.
105

# 3
Probable Causes Link peers control card malfunctions.
Implications In case of ring failure, ERP cannot be activated.
Suggested Recovery Procedure NOTE: The remedy actions below impose the interruption of all add/drop services provided by the OmniBAS node: a. From the management application, click on local ODU (East), right click and select Reset to reset ODU. b. If problem persists, click on the NE, right click and select Reset to reset the OmniBAS node. c. If previous steps fail, replace the control card (P7 procedure). d. If no remedy applies, call Intracom Telecom.
106
West Port (Modem 1) of Ring Failure

Explanation
The OmniBAS-2W /-4W node, which participates in an Ethernet Ring Protection (ERP) ring, has stopped receiving control messages from its west-side ring peer (see below).
107
West Port (Modem 1) of Ring Failure, Continued

Indication

Alarm Description West Port (Modem 1) of Ring Failure
In case the link (between the two OmniBAS peers in the ring) is down, the following alarms will be listed:
b. Change in Elements Monitoring Status: (Click on NE > Configuration tab > Modem tab > Ring tab) The Signal Fail West status is Active to indicate that no control messages are received from the west side of the OmniBAS ring.
108

Causes & actions
# 1
Probable Causes ERP not yet configured for the links peer.
Implications
Suggested Recovery Procedure Most probably, there is no issuance of Modem Link Failed and Remote Modem Link Failed alarms. From the uni|MS application, click the OmniBAS NE. Then, select Configuration > Modem > Ring tab and configure the ERP settings for the respective modem card. Refer to cases: Modem Link Failed Remote Modem Link Failed
The corresponding link (participating in the OmniBAS ring) is down. All remaining links remain up.
ERP no longer available. Services remain unaffected but ERP must be restored the sooner possible.
109

# 3
Probable Causes Link peers control card malfunctions.
Implications In case of ring failure, ERP cannot be activated.
Suggested Recovery Procedure NOTE: The remedy actions below impose the interruption of all add/drop services provided by the OmniBAS node: a. From the management application, click on local ODU (West), right click and select Reset to reset ODU. b. If problem persists, click on the NE, right click and select Reset to reset the OmniBAS node. c. If previous steps fail, replace the control card (P7 procedure). d. If no remedy applies, call Intracom Telecom.
110
Outdoor Unit (ODU) Alarms ODU Communication Failure

Explanation
The concerned modem card cannot communicate with its physically-connected ODU through the service channel.
Indication

Alarm Description ODU Communication Failure
Severity (Default) Critical
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) Communication Status = Not Connected.
c. Visual Indication (on the Connected Modems Front Panel): OmniBAS-2W: The led ODU on the concerned modem card blinks red to denote a communication problem with the ODU.
OmniBAS-4W:
111
ODU Communication Failure, Continued

Causes & actions
# 1
Probable Causes The coaxial cable, interconnecting the modem card with the outdoor radio box, is impaired. The external power supply is underrated and it has been overloaded.
Implications
Suggested Recovery Procedure First inspect the connectors at both ends. Then inspect the cable itself.
Unprotected operation: Link out of operation. Protected operation: Link protection is no longer available.
Use another external power supply of appropriate rating. Refer to OmniBAS specifications to get systems maximum power consumption values. Replace the modem card with a spare one (P6 procedure). Replace the outdoor radio box with a spare one (P8 procedure).
The modem card has failed.
The outdoor radio box has failed.
112
ODU Pout ALC Alarm

Explanation
The actual transmit Tx power exceeds 3 dB from the ODUs configured value.
Indication

Alarm Description ODU Pout ALC Alarm Severity (Default) Critical Alarm id OB-2W ETH 14052 OB-2W 8E1 14052 OB-2W 16E1 24052 OB-2W RC 14052 OB-4W 2GbE 6052 OB-4W 2GbE/2FE 6052
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The actual transmit Tx power exceeds 3 dB from the ODUs configured value (see fields below). The Pout ALC indicator turns to red (see below) to denote that ODUs Tx Power is exceedingly low.
c. Visual Indication (on the Connected Modems Front Panel): OmniBAS-2W: The led ODU on the concerned modem card lights up amber, meaning that the connected ODU has an active alarm.
OmniBAS-4W:
113
ODU Pout ALC Alarm, Continued

Causes & actions
# 1
Probable Causes The modem card has failed. The ODU has failed.
Implications Degraded radio performance and/or unavailability
Suggested Recovery Procedure Replace the modem card with a spare one (P6 procedure). Replace the ODU with a spare one (P8 procedure).
114
ODU Rx PLL LD Alarm

Explanation
The PLL stage (internally the specific ODU), which is used for IF signal reception, is malfunctioning.
Indication

Alarm Description ODU Rx PLL LD Alarm Severity (Default) Critical Alarm id OB-2W ETH 14053 OB-2W 8E1 14053 OB-2W 16E1 24053 OB-2W RC 14053 OB-4W 2GbE 6053 OB-4W 2GbE/2FE 6053
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The Rx PLL LD indicator turns to red (see below) to denote that ODUs Rx PLL is malfunctioning.
OmniBAS-4W:
115
ODU Rx PLL LD Alarm, Continued

Causes & actions
# 1
Probable Causes Temporary ODU malfunction.
Implications Unprotected operation: Link out of operation. Protected operation: Link protection is no longer
Suggested Recovery Procedure From the management application, click on modems ODU port, right click and select Reboot to reset ODU. Replace the ODU with a spare one (P8 procedure).
The ODU has failed.
116
ODU Tx PLL LD Alarm

Explanation
The PLL stage (internally the specific ODU) that is used for Tx signal transmission, is malfunctioning.
Indication

Alarm Description ODU Tx PLL LD Alarm Severity (Default) Critical Alarm id OB-2W ETH 14054 OB-2W 8E1 14054 OB-2W 16E1 24054 OB-2W RC OB-4W 2GbE 6054 OB-4W 2GbE/2FE 6054
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The Tx PLL LD indicator turns to red (see below) to denote that ODUs Tx PLL is malfunctioning.
c. Visual Indication (on the Connected Modems Front Panel): OmniBAS-2W: The led ODU on the concerned modem card lights up amber, meaning that the connected ODU has OmniBAS-4W: an active alarm.
117
ODU Tx PLL LD Alarm, Continued

Causes & actions
# 1
Probable Causes Temporary ODU malfunction. The ODU has failed.
Implicati ons Unprotected operation: Link out of operation. Protected operation: Link protection is no longer available.
Suggested Recovery Procedure From the Node Manager, click on modems ODU port, right click and select Reboot to reset ODU. Replace the ODU with a spare one (P8 procedure).
118
ODU Tx Configured Frequency Out of Range Alarm

Explanation
The transmit (Tx) frequency that has been set through the management application is not supported by the specific ODU.
Indication

Alarm Description ODU Tx Configured Frequency Out of Range Alarm Severity (Default) Warning Alarm id OB-2W ETH 14055 OB-2W 8E1 14055 OB-2W 16E1 24055 OB-2W RC 14055 OB-4W 2GbE 6055 OB-4W 2GbE/2FE 6055
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The Tx Configured Frequency Out of Range indicator turns to red to denote that the configured transmit frequency (see upper left ellipse below) is out of the supported range.
119
ODU Tx Configured Frequency Out of Range Alarm,

Continued
Indication, continued
OmniBAS-4W:
120
ODU Tx Configured Frequency Out of Range Alarm,

Continued
Causes & actions
# 1
Probable Causes Unsupported Tx frequency.
Implication Link may not be established.
Suggested Recovery Procedure a. Click on the modems ODU port. b. Select Configuration tab. c. Click the ... button next to the Tx Frequency (KHz) field (see below). d. From the list that appears, select a valid transmit frequency value (in thousands of Hz).
Wrong ODU model installed.
Link cannot be established.
Replace the ODU with a spare one of the correct type (P8 procedure).
121
ODU RF PLL LD Alarm

Explanation
The internal RF signal PLL stage is malfunctioning.
Indication

Alarm id OB-2W ETH OB-2W 8E1 OB-2W 16E1 OB-2W RC 14059 OB-4W 2GbE OB-4W 2GbE/2FE -
Alarm Description ODU RF PLL LD Alarm
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The RF PLL LD indicator turns to red (see below) to denote that ODUs RF PLL is malfunctioning.
c. Visual Indication (on the Connected Modems Front Panel): The led ODU on the concerned modem card lights up amber, meaning that the connected ODU has an active alarm.
122
ODU RF PLL LD Alarm, Continued

Causes & actions
# 1
Probable Causes Temporary ODU malfunctioning.
Implications Unprotected operation: Link out of operation. Protected operation: Link protection is no longer available.
The ODU has failed.
123
ODU MW PLL LD Alarm

Explanation
The RF signal PLL stage (internally the specific ODU) is malfunctioning.
Indication

Alarm Description ODU MW PLL LD Alarm Severity (Default) Critical Alarm id OB-2W ETH 14056 OB-2W 8E1 14056 OB-2W 16E1 24056 OB-2W RC OB-4W 2GbE 6056 OB-4W 2GbE/2FE 6056
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The MW PLL LD indicator turns to red (see below) to denote that ODUs MW PLL is malfunctioning.
OmniBAS-4W:
124
ODU MW PLL LD Alarm, Continued

Causes & actions
# 1
The ODU has failed.
125
ODU Loopback PLL LD Alarm

Explanation
Following a request by the management, the specific ODU cannot activate an internal software loopback.
Indication

Alarm Description ODU Loopback PLL LD Alarm Severity (Default) minor Alarm id OB-2W ETH 14057 OB-2W 8E1 14057 OB-2W 16E1 24057 OB-2W RC OB-4W 2GbE 6057 OB-4W 2GbE/2FE 6057
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The Loopback PLL LD indicator turns to red (see below) to denote that ODU cannot activate the internal loopback.
OmniBAS-4W:
126
ODU Loopback PLL LD Alarm,

Causes & actions
Continued
# 1
Suggested Recovery Procedure From the management application, click on modems ODU port, right click and select Reboot to reset ODU.
Minor ODU malfunction.
Cannot troubleshoot ODU loopback. Link services are not impacted.
Although not critical for links operation, it is advisable to replace the ODU with a spare one (P8 procedure). Choose a convenient time for this task.
127
Tx ODU Configured Power Out of Range Alarm

Explanation
The transmit (Tx) power level that has been set manually through the management application is not supported by the specific ODU. The instructions provided hereinafter are valid when the respective modem is configured for Adaptive Mode = Manual or Auto / Manual Power.
Indication

Alarm Description Tx ODU Configured Power Out of Range Alarm
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The Pwr Out of Range Errors indicator turns to red to denote that the configured transmit power (see upper left ellipse below) is out of the supported range (see lower left eclipse below).
128
Tx ODU Configured Power Out of Range Alarm,

Continued
Causes & actions
# 1
Probable Causes Incorrect Tx power setting.
Implications Link may not be established.
Suggested Recovery Procedure a. Click on modems ODU port. b. Select Configuration tab (see below). c. In the Tx Power (dBm) field, type a valid value for the transmit power. For the supported values, refer to the OmniBAS system description.
129
ODU High Temperature Alarm

Explanation
The predefined upper threshold for ODUs operating temperature has been exceeded and ODU is overheated.
Indication

Alarm Description ODU High Temperature Alarm
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The High Temperature indicator turns to red (see below) to denote ODUs overheat.
130
ODU High Temperature Alarm,

Causes & actions
Continued
# 1
Probable Causes Upper temperature threshold has been set too low.
Implications None. Relevant alarms will be issued more frequently, especially during hot seasons.
Suggested Recovery Procedure a. Click on NE. b. Select Configuration tab > Thresholds tab. c. In the ODU group box > High Temperature (oC) header, doubleclick on threshold value (see below). d. In this field, type a higher threshold value that will still be within the ODUs operating temperature range (refer to OmniBAS system description).
Extreme high temperatures locally. The ODUs temperature monitoring subsystem
Radio performance may be degraded. Inability to further monitor ODU temperature.
Contact Intracom Telecom for details on the order and installation of a protective sun shield. Replace ODU with a spare one (P8 procedure).
131
ODU RSSI Rx User Alarm

Explanation
The specific ODU has exceeded the predefined threshold regarding the received signal strength.
Indication

Alarm Description ODU RSSI Rx User Alarm
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The RSSI indicator turns to red (see below) to denote that the predefined RSSI threshold has been exceeded.
132
ODU RSSI Rx User Alarm, Continued

Causes & actions
# 1
Probable Causes Extreme weather conditions.
Implications Degradation of link performance.
Suggested Recovery Procedure Consider increasing the transmit power or using a lower modulation (by setting operation to auto optimum). Radio re-planning should also be carried out if needed. a. Click on NE. b. Select Configuration tab > Thresholds tab. c. In the ODU group box > RSSI (dBm) header, double-click on threshold value (see below). d. In this field, type a lower threshold value that will still be within the ODUs reception capabilities (refer to OmniBAS system description).
RSSI threshold has been set too high with respect to planned value.
None. Relevant alarm will be issued more frequently, especially during highfading conditions.
133
ODU RSSI Rx User Alarm, Continued

# 3
Probable Causes Incompatible, faulty or wronglyinstalled hardware. Radio transmission issues
Refer to case: Radio Link is Down
134
ODU Min Pif Alarm

Explanation
The IF signal at the input of the specific ODU has crossed the acceptable minimum level (-16.5 dBm), which is marginal for the normal operation of the ODU. The ODU still has the capability to compensate this power loss through its inherent cable calibration mechanism. Hereinafter, we assume an alarm incident that happens during the normal operation of the system and not during its commissioning (where it would definitely denote an installation problem).
Indication

Alarm Description ODU Min Pif Alarm
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The Min Pif indicator turns to red (see below) to denote that the IF signal at ODUs input has exceeded the low limit.
135
ODU Min Pif Alarm, Continued

Causes & actions
# 1
Probable Causes The coaxial cable, interconnecting the modem card with the outdoor radio box, is impaired. The modem card has failed. The ODU has failed.
Implications Unprotected operation: None for the time. Nevertheless, onsite visit will be needed to avoid link downtime and services interruption. Protected operation: None for the time. Nevertheless, onsite visit will be needed to retain links protection.
Replace the modem card with a spare one (P6 procedure). Replace the ODU with a spare one (P8 procedure).
136
ODU Model Alarm

Explanation
The modem card cannot recognize the connected ODU.
Indication

Alarm Description ODU Model Alarm Severity (Default) Major Alarm id OB-2W ETH 14090 OB-2W 8E1 14090 OB-2W 16E1 24090 OB-2W RC OB-4W 2GbE 6090 OB-4W 2GbE/2FE 6090
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The Invalid Model indicator turns to red (see below) to denote that the model of ODU is not recognized.
OmniBAS-4W:
137
ODU Model Alarm, Continued

Causes & actions
# 1
Probable Causes Wrong ODU model installed. (1)
Implications Link cannot be established.
Suggested Recovery Procedure Replace ODU with a spare one of the correct model (P8 procedure).
(1)
Assuming that modem card is of the correct type.
138
ODU H/W Bandwidth Alarm

Explanation
The configured channel size (e.g. 56 MHz) is not supported by the specific ODU.
Indication

Alarm Description ODU H/W Bandwidth Alarm Severity (Default) Warning Alarm id OB-2W ETH 14091 OB-2W 8E1 14091 OB-2W 16E1 24091 OB-2W RC OB-4W 2GbE 6091 OB-4W 2GbE/2FE 6091
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The H/W Bandwidth indicator turns to red (see below) to denote that the configured channel size is not supported by the ODU.
OmniBAS-4W:
139
ODU H/W Bandwidth Alarm, Continued

Causes & actions
# 1
Probable Causes Incorrect channel size setting.
Implications
Suggested Recovery Procedure a. Click on the respective modem. b. Select Configuration tab. c. Expand the list next to Bandwidth (MHz) field and select the correct channel size.
Link cannot be established.
Wrong ODU model installed.
Replace ODU with a spare one of the correct model (P8 procedure).
140
ODU Cable Calibration Alarm

Explanation
Excessive IF signal power loss (at the input of the specific ODU), which cannot be compensated through the ODUs cable calibration mechanism. Hereinafter, we assume an alarm incident that occurs during the normal operation of the system and not during its commissioning (where it would definitely denote an installation problem).
Indication

Alarm Description ODU cable Calibration Alarm
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The Cable Calibration indicator turns to red (see below) to denote that ODUs cable calibration mechanism is currently ineffective due to excessive power loss.
141
ODU Cable Calibration Alarm, Continued

Causes & actions
# 1
Probable Causes The coaxial cable, interconnecting the modem card with the outdoor radio box, is impaired. The coaxial cable, interconnecting the modem card with the outdoor radio box, is too long. The modem card has failed. The ODU has failed.
Implications
Suggested Recovery Procedure First inspect cables connectors at both ends and re-terminate if needed. Then, inspect cable itself and replace if found worn or damaged. Investigate a different route that shortens the coaxial cables total length or replace the existing cable with another, better quality one. Replace the modem card with a spare one (P6 procedure). Replace the ODU with a spare one (P8 procedure).
Degraded radio performance and/or unavailability of services.
142
ODU Max Pif Alarm

Explanation
Either the specific ODU is overdriven by the IF signal applied to its input or the ODU overloads the interconnected modem card.
Indication

Alarm Description ODU Max Pif Alarm
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The Max Pif indicator turns to red (see below) to denote either an ODUs overdrive or a modems input overload.
143
ODU Max Pif Alarm, Continued

Causes & actions
# 1
Probable Causes The modem card has failed. The ODU has failed.
Implications Unprotected operation: None for the time. Nevertheless, onsite visit will be needed to avoid link downtime and services interruption. Protected operation: None for the time. Nevertheless, onsite visit will be needed to retain links protection.
Suggested Recovery Procedure Replace the modem card with a spare one (P6 procedure). Replace the ODU with a spare one (P8 procedure).
144
ODU Low If Alarm

Explanation
Either the IF signal level at the input of the specific ODU is too weak (typically -35 dBm) that the ODU has stopped operating, or the ODU has just failed. In the first case, power loss cannot be compensated through the ODUs cable calibration mechanism. Hereinafter, we assume an alarm incident that happens during the normal operation of the system and not during its commissioning (where it would definitely denote an installation problem).
Indication

Alarm Description ODU Low If Alarm
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The Low If indicator turns to red (see below) to denote that input IF signal is too weak. The Cable Calibration indicator turns to red (see below) to denote ODUs inability to compensate the power loss.
145
ODU Low If Alarm, Continued

Causes & actions
# 1
Probable Causes The coaxial cable, interconnecting the modem card with the outdoor radio box, is impaired. The coaxial cable, interconnecting the modem card with the outdoor radio box, is too long. The modem card has failed. The ODU has failed.
Implications
Unprotected operation: Link out of operation. Protected operation: Link protection is not available.
Investigate a different route that shortens the coaxial cables total length or replace the existing cable with another, better quality one. Replace the modem card with a spare one (P6 procedure). Replace the ODU with a spare one (P8 procedure).
146
ODU Low Temperature Alarm

Explanation
Extra-low temperature at local premises or the specific ODU has exceeded the (predefined) low temperature threshold.
Indication

Alarm Description ODU Low Temperature Alarm
b. Change in Elements Monitoring Status: (Click on Modems ODU port > Status tab) The Low Temperature indicator turns to red (see below) to denote that ODUs low temperature threshold has been crossed.
147
ODU Low Temperature Alarm,

Causes & actions
Continued
# 1
Probable Causes Extra-low temperature.
Implications System performance may be affected. None.
Suggested Recovery Procedure None. Just confirming the actual local environmental conditions. a. Click on NE. b. Select Configuration tab > Thresholds tab. c. In the ODU group box > Low Temperature (oC) header, double-click on threshold value (see below). d. In this field, type a lower threshold value that will still be within the ODUs operating temperature range (refer to OmniBAS system description).
Low temperature threshold has been set too high.
The ODUs temperature monitoring subsystem has failed.
Inability to further monitor ODU temperature.
Replace ODU with a spare one (P8 procedure).
148
E1 Line Alarms E1 Line LOS

Explanation
The OmniBAS-2W/ -4W indoor unit (A) cannot receive data from peer B (at the other end of the E1 line). For structured (framed) mode only: A sends a Remote Alarm Indication (RAI) to B to denote the reception problem.
NOTE
The LOS alarm is applicable to both structured (framed) and unstructured (unframed) modes.
Indication

Alarm id OB-2W ETH OB-2W 8E1 14070 OB-2W 16E1 24070 OB-2W RC OB-4W 2GbE 6070 OB-4W 2GbE/2FE 6070
Alarm Description E1 Line LOS
b. Change in Elements Monitoring Status: (Click on Interface Cards respective E1 port > Status tab) The LOS indicator turns to red (see below) to denote an active LOS alarm on the E1 line.
149
E1 Line LOS, Continued

Causes & actions
# 1
Probable Causes External equipment is out of service, or not operating or it has failed. Impaired E1 cable. The OmniBAS indoor unit has failed.
Implications
Suggested Recovery Procedure Cooperate with the external equipment technical support to resolve the problem. Replace cable (at the problematic direction only, if possible). OmniBAS-2W: Replace the control card (P7 procedure). OmniBAS-4W: Replace the E1 interface card (P4 procedure).
150
E1 Line LOF
Explanation
The OmniBAS-2W/ -4W indoor unit (A) receives unsynchronized data from the external equipment B, at the other end of the E1 line.
NOTE
The LOF alarm is applicable to structured (framed) mode only.
Indication

Alarm Description E1 Line LOF
b. Change in Elements Monitoring Status: (Click on Interface Cards respective E1 port > Status tab) The LOF indicator turns to red (see below) to denote an active LOF alarm on the E1 line.
151
E1 Line LOF, Continued

Causes & actions
# 1
Probable Causes E1 configuration mismatch (between peers). The line transmitter of the external equipment has problem. Deteriorated cabling.
Implications
Suggested Recovery Procedure Set E1 structured for both peers. Check CRC (CRC-4 vs. CRC-16).
Cooperate with external equipment technical support to resolve problem. Replace cable (at the problematic direction only, if possible).
152
E1 Line AIS
Explanation
The external equipment (B), at the other end of the E1 line, sends an Alarm Indication Signal (AIS) to the OmniBAS-2W/ -4W indoor unit (A) to denote its inability to receive data from the preceding section (see below).
NOTE
The AIS alarm is applicable to structured (framed) mode.
Indication

Alarm Description E1 Line AIS
b. Change in Elements Monitoring Status: (Click on Interface Cards respective E1 port > Status tab) The AIS indicator turns to red (see below) to denote an active AIS alarm on the E1 line.
153
E1 Line AIS, Continued

Causes & actions
# 1
Probable Causes The line receiver of the external equipment has problem. Impaired cabling.
Implications
2 3
Cooperate with external equipment technical support to resolve problem.
Interruption of The OmniBAS associated indoor unit services. has failed.
OmniBAS-2W: Replace the control card (P7 procedure). OmniBAS-4W: Replace the E1 interface card (P4 procedure).
154
E1 Line RAI
Explanation
The external equipment (B), at the other end of the E1 line, sends a RAI alarm to denote its inability to receive data from the OmniBAS-2W/ -4W indoor unit (A).
NOTE
The RAI alarm is applicable to structured (framed) mode only.
Indication

Alarm Description E1 Line RAI
b. Change in Elements Monitoring Status: (Click on Interface Cards respective E1 port > Status tab) The RAI indicator turns to red (see below) to denote an active RAI alarm on the E1 line.
155
E1 Line RAI, Continued

Causes & actions
# 1
Probable Causes E1 configuration mismatch (between peers). Impaired E1 cabling. External equipment has reception problem (verified through an external loop). Indoor unit has transmission problem (verified through an external loop).
Implications
Suggested Recovery Procedure Check / correct the E1 framing and synchronization at both peers. Replace cable (at the problematic direction only, if possible). Cooperate with external equipment technical support.
OmniBAS-2W: Replace the control card (P7 procedure). OmniBAS-4W: Replace the E1 interface card (P4 procedure).
156
E1 Line Admin Down

Explanation
The corresponding E1 port on the control card (E1 interface card) of the OmniBAS-2W (OmniBAS-4W) indoor unit is currently disabled and data cannot be transmitted nor received over the E1 line.
Indication

Alarm Description E1 Line Admin Down
b. Change in Elements Monitoring Status: (Click on Interface Cards respective E1 port > Status tab) The Admin Down indicator turns to red (see below) to denote that the specific E1 port is disabled.
Causes & actions
# 1
Probable Causes E1 port manually disabled.
Suggested Recovery Procedure Re-enable the E1 port: (Click on E1 port > Configuration tab > Admin State = Up > click Apply)
157
E1 is Looped
Explanation
A software loopback one of the three shown in the schematic below has been activated on the E1 port of the OmniBAS-2W / OmniBAS-4W indoor unit. Services provided through the E1 port are interrupted for as long the loopback remains active.
Remote Framer
Local Framer Local LIU E1 line Remote OmniBAS system uni|MS management
E1 line Local OmniBAS system
Loopbacks
Indication

Alarm Description E1 is Looped Severity (Default) Warning Alarm id OB-2W ETH OB-2W 8E1 16043 OB-2W 16E1 OB-2W RC OB-4W 2GbE 16043 OB-4W 2GbE/2FE 16043
b. Change in Elements Monitoring Status: (Click on Interface Cards respective E1 port > Status tab) The activated loopback is denoted next to the Local Loopback State or next to the Remote Loopback State field (see example below).
158
E1 is Looped, Continued
Causes & actions
# 1
Probable Causes Manual setting of loopback for E1 line troubleshooting purposes.
Implications Temporary unavailability of associated services.
Suggested Recovery Procedure When E1 line measurements complete and loopback is removed, expect for cessation of the E1 is Looped alarm.
159
E1 Local Loop
Explanation
A software loopback has been activated on the E1 port of the local OmniBAS-2W (16E1) indoor unit, either at the Line Interface Unit (LIU) or at the Framer section, as shown below. Services provided through the E1 port are interrupted for as long the loopback remains active. This alarm reminds users to remove the loopback so that services are restored.
Local OmniBAS system Local Framer Local LIU E1 line Loopbacks
Remote OmniBAS system
E1 line
E1 tester uni|MS management
Indication

Alarm Description E1 Local Loop Severity (Default) Warning Alarm id OB-2W ETH OB-2W 8E1 OB-2W 16E1 16105 OB-2W RC OB-4W 2GbE OB-4W 2GbE/2FE -
b. Change in Elements Monitoring Status: (Click on Interface Cards respective E1 port > Status tab) The activated loopback is denoted next to the Local Loopback State field (see the example below).
160
E1 Local Loop, Continued

Causes & actions
# 1
Suggested Recovery Procedure When E1 line measurements complete and loopback is removed, expect for cessation of the E1 Local Loop alarm.
161
E1 Remote Loop
Explanation
A software loopback has been activated on the E1 port at the framer section of the local OmniBAS-2W (16E1) indoor unit, as shown below. Services provided through the E1 port are interrupted for as long the loopback remains active. This alarm reminds users to remove the loopback so that services are restored.
Local OmniBAS system Remote Framer E1 line
Remote OmniBAS system
Loopback
E1 line
E1 tester uni|MS management
Indication

Alarm Description E1 Remote Loop Severity (Default) Warning Alarm id OB-2W ETH OB-2W 8E1 OB-2W 16E1 16106 OB-2W RC OB-4W 2GbE OB-4W 2GbE/2FE -
b. Change in Elements Monitoring Status: (Click on Interface Cards respective E1 port > Status tab) The activated loopback (Remote Framer) is denoted next to the Remote Loopback State field:
162
E1 Remote Loop, Continued

Causes & actions
# 1
Suggested Recovery Procedure When E1 line measurements complete and loopback is removed, expect for cessation of the E1 Remote Loop alarm.
163
Ethernet Line Alarms SFP Tx Fault

Explanation
The specific Gigabit Ethernet SFP, accommodated by the control card of the OmniBAS-2W /-4W indoor unit, has failed.
Indication

Alarm Description SFP Tx Fault Severity (Default) Major Alarm id OB-2W ETH 14080 OB-2W 8E1 14080 OB-2W 16E1 24080 OB-2W RC 14080 OB-4W 2GbE 6080 OB-4W 2GbE/2FE 6080
b. Change in Elements Monitoring Status: (Click on Control Cards respective Gigabit Ethernet port > Status tab) The SFP Tx Fault indicator is True (see below) to denote the SFP failure:
164
SFP Tx Fault, Continued

Causes & actions
# Probable Causes 1 SFP has failed.
Implications Unprotected operation: Outage of SFP link services. Protected operation (RSTP, LAG): No SFP link protection.
Suggested Recovery Procedure a. Unplug optical fibers. b. Remove and replace SFP with a spare, compatible one. c. Re-install the optical fibers.
165
SFP Rx LOS
Explanation
The specific Gigabit Ethernet SFP, accommodated by the control card of the OmniBAS-2W /-4W indoor unit (A), cannot receive any data from peer B (at the other end of the optical GbE line).
Indication

Alarm Description SFP Rx LOS
b. Change in Elements Monitoring Status: (Click on Control Cards respective Gigabit Ethernet port > Status tab) The SFP Rx Loss of Signal indicator is True (see below) to denote the LOS alarm:
166
SFP Rx LOS, Continued

Causes & actions
Probable Causes
Suggested Recovery Procedure Cooperate with the farend equipment technical support to resolve the problem. Replace cable (only at the reception direction, if possible).
1 External equipment currently is out of service or not operating. 2 Impaired optical cable. 3 SFP has failed.
Unprotected operation: Outage of SFP link services. Protected operation (RSTP, LAG): No SFP link protection.
a. Unplug optical fibers. b. Remove and replace SFP with a spare, compatible one. c. Re-install the optical fibers.
4 Control card has failed.
Outage of SFP link services.
Replace the control card with a spare one (P7 procedure).
167
Ethernet Link Down

Explanation
The specific Gigabit Ethernet (GbE) or Fast Ethernet (FE) port is either disabled or the wireline connection associated with this port is broken.
Indication

Alarm Description Ethernet Link Down
b. Change in Elements Monitoring Status: (Click on Control Cards respective Ethernet port > Status tab) The Link Status indicator is Down (see below) to denote that Ethernet connection is either disabled or broken:
168
Ethernet Link Down, Continued

Causes & actions
# 1
Probable Causes Ethernet port (on OmniBAS indoor unit) is disabled.
Implications
Suggested Recovery Procedure From within uni|MS, click the respective Ethernet port, select Configuration tab and change Admin State value to up:
Incompatible negotiation mode (between the devices communicating over the Ethernet line). Interruption of associated services.
Ensure that both OmniBAS and the device at the other end of the Ethernet line have been configured for the same negotiation mode (Auto or Forced). If not, change the negotiation mode in one of the devices (e.g. the OmniBAS unit). Try Auto negotiation first, then Forced negotiation with identical settings for both sides of the Ethernet line. Refer to cases: Modem Link Failed Remote Modem Link Failed Alternatively, you can:

Link Loss Forwarding (LLF) is enabled and the respective Modem Link Failed alarm is present.
disable LLF (if not necessary), or change LLF settings if found to be incorrectly configured (e.g. LLF not enabled for both working and standby modem cards or for all modem cards of the RLA group).
169
Ethernet Link Down, Continued

# 4
Probable Causes The OmniBAS indoor unit is daisy-chained with another one and both units are synchronized from a Gigabit interface.
Implications
Suggested Recovery Procedure Change the synchronization source in one of the two cascaded OmniBAS units. From within uni|MS, click the OmniBAS NE, select Configuration tab and change the Configured Clock Source value to any available source, other than the Gb Ethernet one:
Impaired or deteriorated Ethernet cable.
Check cables entire run and terminations at both sides. Replace cable if necessary.
170
3.
Troubleshooting of Problems Reported by Customers

This chapter deals with those incidents that might be reported to the Call Center by customers using the OmniBAS network services. The goal is to filter the reported information in order to isolate the root cause and rectify the problem from the centralized location (NOC), while trying to avoid unnecessary on-site visits.
Introduction
171
Radio Link is Down

Explanation
A broken OmniBAS radio link has been reported to the call center. Troubleshooting will be carried out from the NOC and by using the uni|MS Node Manager / Domain Manager application.
Assuring the normal operation of an OmniBAS radio link is a vital prerequisite in order to troubleshoot any other incident associated with the services provided by this specific OmniBAS link.
NOTE
If the remote OmniBAS system is accessible, then the steps on the next pages should be followed for both sides of the link from the NOC. If the remote OmniBAS system is not accessible, then the steps on the next pages should be followed for the local OmniBAS from the NOC. For the remote OmniBAS, local visit will be needed. Steps will be followed in sequence, i.e.: step 1 first, then step 2, step 3, etc., until the reported problem is rectified.
172
Radio Link is Down, Continued

Recovery procedure
# 1
Step Check whether the local and remote OmniBAS nodes are accessible from the uni|MS Domain Manager.
Details If one or both OmniBAS nodes are not accessible, then a Lost Communication with Element alarm will be issued. If management is not restored within the next 5 minutes, then: In case the local OmniBAS NOTE units are accessible, proceed to step 2 immediately. 1. Contact the 1st level support team to visit site(s) with which communication has been lost. 2. Consult the power supply management systems (if available) to check whether local power is up. Then, accordingly inform the 1st level support team. Troubleshooting instructions for the 1st level support team: 1. Check power supply as instructed for case: Indoor Unit Not Powered Up). 2. In case that no local power problem exists, inspect for the reason of management loss by following the instructions for cases: Management Connection Not Feasible Lost Communication with Element 3. Check with NOC either for receiving specific orders (for onsite actions) or for proceeding with onsite troubleshooting, by following the instructions for cases: Radio Link Cannot Be Established Radio Link Cannot Achieve Expected Performance
173

Recovery procedure (continued)
# 2
Step Check whether the ODU is connected.
Details If ODU status = Not connected, then reboot the respective modem (or even the OmniBAS unit). If alarms persist, then contact 1st level support team to visit site and follow the instructions for case: ODU Communication Failure If one of the following alarms is active, reboot the respective card (or even the OmniBAS unit). If alarms persist, then contact 1st level support team to visit site and follow the instructions for corresponding case(s): Modem Failure Modem Chip Failure Invalid Modem Inserted ODU Pout ALC Alarm ODU Rx PLL LD Alarm ODU RF PLL LD Alarm ODU MW PLL LD Alarm ODU Tx PLL LD Alarm ODU Model Alarm ODU Max Pif Alarm ODU Min Pif Alarm Contact 1st level support team to visit site and follow the instructions for case: ODU Cable Calibration Alarm
Check for issuance of: a. Equipment extracted alarm. b. Hardwareassociated alarms.
Check for active cable-relevant alarms.
174

# 5
Step Check for active ODU configuration alarms.
Details Depending on the alarm that is active, accordingly refer to the corresponding case: ODU Tx Configured Frequency Out of Range Alarm Tx ODU Configured Power Out of Range Alarm ODU H/W Bandwidth Alarm Depending on the alarm that is active, accordingly refer to the corresponding case: Modem Link Failed Remote Modem Link Failed
RAI Alarm (Modem Group 1-2 /1-3 /2-4)
Check for active link alarms.
ODU RSSI Alarm Rx Normalized MSE (SNR) Alarm Rx LDPC Decoders Stress Alarm 7 Carry out onsite troubleshooting. If none of the aforementioned corrective actions helps, dispatch engineers to both sides of the link in order to perform onsite troubleshooting, as instructed in cases: Radio Link Cannot Be Established (when link is unlocked). Radio Link Cannot Achieve Expected Performance (when link is unstable).
HINT
Consult link status and in-service / out-of-service seconds to check which one is happening.
End of procedure.
175
Ethernet Service Outage (or with Errors)

Explanation
Ethernet service degradation or interruption has been reported to the call center. This incident concerns a specific site served by an OmniBAS link through Ethernet interfaces (see below). Troubleshooting will be carried out from the NOC and by using the uni|MS Node Manager / Domain Manager application.
NOTE
The procedure that follows must be carried out for both OmniBAS nodes participating in the problematic link. Steps will be followed in sequence, i.e.: step 1 first, then step 2, step 3, etc., until the reported problem is rectified.
176
Ethernet Service Outage (or with Errors), Continued

Recovery procedure
# 1
Step Check if radio link is up and running. Check radio performance.
Details If link is down, follow the instructions provided for case: Radio Link is Down a. On the photorealistic view, click the modem card associated with the problematic link, select Performance tab > PTP Modem (Rx) tab:
b. Check for: - Total link downtime (Total time out of Service). - Frames not corrected by the OmniBAS FEC mechanism (Uncorrected Blocks). c. In case of link downtime or uncorrected frames, refer to case: Radio Link Cannot Achieve Expected Performance.
177

Step
Details a. Click the Ethernet port (GbE or FE) associated with the service problem and select Configuration tab:
3 Check Ethernet port configuration.
b. If Admin State = down, then change to Up. c. Check if LLF Operation = Enabled. If yes, and Modem Link Failed alarm is present, then refer to cases: Modem Link Failed Remote Modem Link Failed Alternatively, you can disable LLF (if not necessary), or change the LLF settings if found to be incorrectly configured (e.g. LLF enabled for both working and standby modem cards or for all modems of the RLA group). d. Select the Status tab (see below) and verify that settings are as follows: Speed = 1000 Mbps (for GbE port) or 100 Mbps (for FE port). Duplex Mode = Full Duplex. Negotiation Mode = Auto.
178

Step Check Ethernet port configuration (continued).
Details e. Ensure that settings (in step d) are also valid for the device at the other end of the Ethernet line. If not, change the negotiation mode in one of the devices (e.g. the OmniBAS unit). Try Auto first, then Forced negotiation with identical settings for both sides of the Ethernet line. a. In the photorealistic view of the OmniBAS node (closest to the served site for which the service problem has been reported), click the OmniBAS NE and select the Performance tab.
(Screenshot below depicts part of Performance tab).
4 Check service performance bridge level (1/2).
b. For the PtP Modem and GbEthernet (FastEth) ports associated with the reported service problem, check the Rx Valid Packets counter. If counter is not increasing, then: either the external equipment does not send data and needs further investigation, or VLAN association is not configured correctly.
179

Step Check service performance bridge level (1/2), continued.
Details c. Check the Discarded Ingress counter. If it increases: either the Acceptable Frame Type is not configured correctly for the required traffic type (tagged and/or untagged), or - the external equipment is not configured correctly and sends traffic of wrong type. Make the necessary changes for both equipments so that they have the same traffic type (tagged / untagged) across the network. d. Check the Discarded VLAN counter. If it increases, one or more inbound VLANs have not the correct association. Based on VLAN network design, either setup the OmniBAS VLAN association or setup the VLANs in external network equipment. e. Check the Tx Queue Drop Packets counter. If it increases rapidly, the inbound Ethernet traffic is highly bursty (minor increase in counters is considered normal). Activate traffic shaping in external equipment. f. Check the Discarded Bridge counter. If it increases, and policer has been configured to discard packets, ignore counter reading. Otherwise, disable policer. -
g. Check the Deny MAC SA and Deny MAC DA counters. If they increase rapidly, frames are discarded due to the anti-spoofing mechanism. Check the network for malicious users or duplicated MAC address.
180

# 5
Step Check service performance port level (2/2).
Details a. Click the Ethernet port of the OmniBAS node associated with the reported problem, and select Performance tab > RMON tab:
b. Check the Oversize Frames counters. If they increase, check if the external equipments MTU size configuration is in accordance with the OmniBASs capabilities. c. Click the modem card associated with the reported problem, and select Performance tab:
d. In the contained tabs, ensure that only the following counters increase.
Rx Packets Rx Vlan Tags Detected Rx Bytes Rx Rate (Mbps) Tx Rate (Mbps) Tx Packets Tx Vlan Tags Tx Multicasts Tx Broadcasts Tx Wire Bytes Tx Bytes
If one (or more) of the remaining of the counters increase, contact Intracom Telecom for further troubleshooting.
181

# 6
Step Check service configuration.
Details a. Click the OmniBAS NE (associated with the reported problem) and select: Configuration tab > L2 Properties tab > L2 Port tab:
b. In the L2 port, VLAN/VLAN Port, pbit to Queues Mapping and Bridge Info tabs, ensure that the following parameters are correctly configured:
cVLAN / sVLAN mode VLAN type Ingress check Acceptable frame type Default VLANs VLAN association p-bits DSCP Queue mapping
NOTE
For configuring all the aforementioned parameters correctly requires deep knowledge of: Network theory. OmniBAS capabilities. Network implementation details.
182

# 7
Step Check for synchronization errors (valid for a pair of daisychained OmniBAS units).
Details Check whether both OmniBAS units are synchronized from different sources. If both units are synchronized from a Gigabit interface, then: a. Click the OmniBAS NE (corresponding to one of the two OmniBAS nodes participating in the link) and select Configuration tab (see below). b. Change the synchronization source (Configured Clock Source) to a different one, other than the Gb Ethernet option:
End of procedure.
183
E1 Service Outage (or with Errors)

Explanation
E1 service degradation or interruption has been reported to the call center. This incident concerns a specific site served by an OmniBAS system. Troubleshooting will be carried out from the NOC and by using the uni|MS Node Manager / Domain Manager application.
NOTE
184
E1 Service Outage (or with Errors), Continued

Recovery procedure
# 1
Step Check whether the radio link is up and running. Check radio performance.
Details If link is down, troubleshoot and rectify the problem as instructed in case: Radio Link is Down a. On the photorealistic view, click the modem card associated with the problematic link, select Performance tab > PTP Modem (Rx) tab:
b. Check for: - Total link downtime (Total time out of Service). - Frames not corrected by the OmniBAS FEC mechanism (Uncorrected Blocks). c. In case of link downtime or uncorrected frames, refer to case: Radio Link Cannot Achieve Expected Performance. 3 Check the status of the E1 port / E1 line. a. In case the corresponding E1 port is disabled (Admin State = Down), re-enable it. b. If active alarms exist, refer to the respective case(s): E1 Line Alarms E1 Line LOF E1 Line AIS E1 Line RAI
185

# 4
Step Check Pseudowire (PW) TDM configuration.
Details a. Click the OmniBAS NE and select Configuration tab > TDM tab, in order to list all PW connections together with their settings:
b. For the specific PW connection associated with the TDM service, note down the following values: - Ingress ID - Egress ID - TS Usage - VLAN ID - PBit c. Ensure that the aforementioned values are the same for both local and remote OmniBAS nodes. d. Ensure that for each OmniBAS node, the Dest MAC Address of its link partner is shown. e. Ensure that TS Usage (regarding the allocation of E1 timeslots) is configured correctly for both OmniBAS nodes of the link: TS Usage = all (full E1 service). Number of timeslots, next to TS Usage, is the same for both OmniBAS nodes (fractional E1 service).
186

# 5
Step Check Pseudowire (PW) VLAN configuration.
Details For all the involved OmniBAS units, along the E1 service path, create the required VLAN associations for the respective Ethernet ports (right click OmniBAS NE > Configuration tab > L2 Properties tab > VLAN/VLAN Port tab). a. Click the OmniBAS NE and select Configuration tab > L2 Properties tab > pbit to Queues Mapping tab:
Ensure that the PW TDM connection has been assigned to high priority queue.
b. By consulting the pbit-to-queue mapping screen (see above), and by considering the PBit value shown in the example of step 4a (PBit = 0 or q0), ensure that the PW TDM service, associated with a specific L2 Port, has been assigned second-highest priority (=6). Only inband management should have higher priority (=7).
187

# 7
Step Check TDM service performance.
Details a. Click the OmniBAS NE and select Configuration tab > TDM tab:
b. Ensure that the performance counters Received Valid Packets and Transmitted Packets continuously increase. This verifies the existence of service flows in the upstream and downstream paths. c. Ensure that the Jitter Buffer Underruns / Overruns counters remain unchanged. If these counters increase: - Carry out end-to-end inspection toward the packet network (PSN) to spot segment(s) generating packet loss. - Check for synchronization errors that could generate slips in the externally-connected TDM equipment. The two OmniBAS nodes (of the link associated with the TDM service) should be synchronized by the same source.
End of procedure.
188
E1 Synchronization Issues
Explanation
Unsynchronized E1 service or loss of E1 synchronization in the externally-connected equipment (e.g. BTS / NodeB) has been reported to the call center. The externally-connected equipment cannot be synchronized to OmniBAS system or it is generating slips. Troubleshooting will be carried out from the NOC and by using the uni|MS Node Manager / Domain Manager application.
NOTE
Recovery procedure
# 1
Step Check OmniBAS synchronization status & configuration.
Details Check whether the OmniBAS synchronization circuit: is in holdover mode. If yes, rectify the synchronization source. is locked to an incorrect synchronization source. If yes, change the synchronization source.
In case that E1 service passes through multiple OmniBAS units, verify that the synchronization signal is transported correctly across the links.
189
E1 Synchronization Issues, Continued

# 2
Step Check radio performance.
Details a. On the photorealistic view, click the modem card associated with the problematic link, select Performance tab > PTP Modem (Rx) tab:
b. Check for: - Total link downtime (Total time out of Service). - Frames not corrected by the OmniBAS FEC mechanism (Uncorrected Blocks). c. In case of link downtime or uncorrected frames, refer to case: Radio Link Cannot Achieve Expected Performance.
190

# 3
Step Check TDM service performance.
Details a. Click the OmniBAS NE and select Configuration tab > TDM tab:
b. Ensure that the counters Received Valid Packets and Transmitted Packets continuously increase. This verifies the existence of service flows in the upstream and downstream paths. c. Ensure that the Jitter Buffer Underruns / Overruns counters remain unchanged. If these counters increase: Carry out end-to-end inspection toward the packet network (PSN) to spot segment(s) generating packet loss. Check for synchronization errors that could generate slips in the externally-connected TDM equipment. The two OmniBAS nodes (of the link associated with the TDM service) should be synchronized by the same source.
191

# 4
Step Ensure that the PW TDM connection has been assigned the highest priority.
Details a. Click the OmniBAS NE and select Configuration tab > L2 Properties tab > pbit to Queues Mapping tab:
b. By consulting the pbit-to-queue mapping screen (see above), and by considering the PBit value shown in the example of step 3a (PBit = 0 or q0), ensure that the PW TDM service, associated with a specific L2 Port, has been assigned the highest priority (=7).
End of procedure.
192
Appendix: Procedures Relevant to Troubleshooting

Introduction
This appendix provides all the procedures associated with the aforementioned troubleshooting cases: Procedure P1 P2 P3 P4 P5 P6 P7 P8 P9 Description Measuring the Input Voltage. Replacing the Fan Tray (OmniBAS-4W). Getting IP Addresses (Serial Connection). Replacing the E1 Interface Card (OmniBAS-4W). Re-aligning the Antennas. Replacing the Modem Card. Replacing the Control Card. Replacing the Radio Unit (ODU). Measuring Modems DC Voltage Out Page 194 195 196 198 199 203 205 208 215
193
P1 Measuring the Input Voltage

Procedure
To measure the input DC voltage of an OmniBAS system, proceed as follows: Step 1 Action Unplug the power supply connector from the indoor unit, as shown below for the OmniBAS-4W indoor unit: (The same also applies for the OmniBAS-2W unit).
1 2
2 3 4
Ensure that the breaker on the DC distribution board is set to ON position. Carefully position the two leads of the multimeter on the cable connectors exposed power pins. Measure the DC voltage across the two power pins. DC voltage must be found within the upper / lower limits, as specified by the equipment manufacturer (Intracom Telecom). Re-plug the connector back to the indoor unit. Repeat the previous steps for the other power connector (if available).
End of procedure.
194
P2 Replacing the Fan Tray (OmniBAS-4W)

Introduction
The fan tray is located at the far left of the OmniBAS-4W indoor unit and is secured in place with two screws (see photo below).
NOTE
This component is critical for the proper operation of the OmniBAS-4W indoor unit. In case of failure, the fan tray must be replaced the sooner possible, in order to avoid equipment overheat and/or damage to housed electronics. Fan tray replacement can be carried out lively, without the need to power down the indoor unit. In the case that an over-temperature alarm is notified by the management and no spare fan tray is available, then the OmniBAS-4W indoor unit should be powered off to avoid damage. This implies the interruption of all OmniBAS-4W node services.
NOTE
Procedure
To replace the fan unit, proceed as follows: Step 1 Action Loosen and remove the two screws securing the fan tray module in place (see below).
Carefully pull out the fan tray from its front handle to disengage it from the chassis backplane. Completely pull out the fan tray by its handle only. Insert the new fan tray and firmly push it to correctly engage with the connectors at the backplane. Then, the embedded fans will start operating. Re-install and tighten the two screws (previously removed) to secure the fan tray in place.
End of procedure.
195
P3 Getting the IP Addresses (Serial Connection)

Requirements
In order to connect to the OmniBAS indoor unit and find its management IP address(es), you need the following hardware: Laptop equipped with a serial port and running Windows. Serial console I/O alarms cable (supplied with the packaging of the OmniBAS control card).
Procedure
To retrieve the OmniBAS indoor units management IP address(es), proceed as follows: Step 1 Action Connect the end of the serial console I/O alarms cable to the AUX receptacle on the control card: OmniBAS-4W:
OmniBAS-2W:
2 3
Connect the other end of the cable to the serial port of the laptop. Run a CLI client (e.g. Hyper Terminal, CRT, etc.), after selecting and configuring the laptops COM serial port as follows: Baud rate = 115200 Data bits = 8 Parity = None Stop bits = 1 No flow control
196
P3 Getting the IP Addresses (Serial Connection),

Continued
Procedure (continued)
Step 4
Action Login to the OmniBAS unit using the following credentials: Username: admin Password: admin Next to the CLI prompt, type: get system mng and press
Enter
When system responds (see below), check for the IP addresses of the OmniBAS units management ports:
Type exit to end telnet session and disconnect laptop from the OmniBAS unit.
End of procedure.
197
P4 Replacing the E1 Interface Card (OmniBAS-4W)

Procedure
To replace the E1 interface card of the OmniBAS-4W indoor unit, proceed as follows: Step 1 2 Action Remove the E1 cable connector from the front panel of the E1 interface card. Remove the two side screws securing the module in place (see below).
Carefully pull out the module by its handles to disengage it from the chassis backplane (see below). Completely pull out the module by its handles only.
Insert the new module. Using its handles, firmly push the module to engage it with the connectors at the backplane. Re-install and tighten the two screws (previously removed) to secure the module in place. Re-install the E1 cable connector.
5 6
End of procedure.
198
P5 Realigning the Antennas

Introduction
This procedure concerns the re-alignment of the antennas in order to improve the signal reception at both sides of the OmniBAS link.
Precautions
Prerequisites
Prior to the alignment of the antennas: Have at hand the sites planned Rx power values. Ensure that links both OmniBAS systems are powered up. Ensure the availability of voice communication between the two sides of the link.
199
P5 Realigning the Antennas, Continued

Procedure
To realign the antennas of an OmniBAS link, proceed as follows: Step 1 Action Locate the RSSI receptacle at the side of the ODU. Remove its protective cap by turning it 90o counter clockwise.
Connect the BNC connector of the supplied RSSI cable (see below) to the mating receptacle on the ODU:
Connect cables black and red (labeled RSSI field) banana plugs to the respective voltage terminal positions on a digital multimeter and adjust for DC voltage measurement in the 2 V range.
200

Step 4
Action In cooperation with the commissioner at the remote site, mechanically adjust the azimuth / tilting position of the antenna system toward a voltage readout maximum on the multimeter.
NOTE
The antenna at the one site must be stable, while the antenna at the other site must be moved along the entire azimuth axis. If scanning fails, you could interfere with a side lobe. Try moving the other antenna. Indicative correspondence of the planned received power level to voltage readouts (for 28 MHz channel) is provided in the following table (a tolerance of +/-5db must be taken into account):
NOTE
201

Step 5
Action Secure both antennas in their final positions. In case of Space Diversity (SD) link mode, you need to also carry out the alignment of the other antenna pair.
6 7
Remove the RSSI cable from ODU. Re-place the RSSI protective cap.
End of procedure.
202
P6 Replacing a Modem Card

Procedure
To replace an OmniBAS-4W / OmniBAS-2W modem card, proceed as follows: Step 1 Action Using a U-ring spanner 11 mm, remove the angle adapter of the coaxial cable connector from the front of the modem module (a). OmniBAS-4W:
OmniBAS-2W:
OmniBAS-4W: Remove the two side screws securing the card on the chassis (b). OmniBAS-2W: Fully loosen (by hand) the cards two side screws (d).
OmniBAS-4W: Carefully pull out the modem card by its handle (c) to disengage it from the chassis backplane. OmniBAS-2W: Carefully pull out the modem card by its two side screws (d) to disengage it from the chassis backplane.
Insert the new card. Firmly push the card to correctly engage it with the connectors at the backplane.
203
P6 Replacing a Modem Card, Continued

Step 5 6
Action Fully tighten the two screws to secure the card in place. Re-install the angle connector of the coaxial cable connector. First, tighten the connector by hand, then by using the U-ring spanner 11 mm. Apply a maximum 1.7 Nm tightening torque; this practically corresponds to 90o rotation of the connector after it is hand-tightened.
End of procedure.
204
P7 Replacing the Control Card

Carrying out this procedure will interrupt all OmniBAS-2W /-4W node services.
Procedure
To replace an OmniBAS-4W / OmniBAS-2W control card, proceed as follows: Step 1 Action Using the uni|MS management software: Save system configuration. Carry out a system configuration backup in order to save the current configuration of the OmniBAS node. Refer to the Technology Driver for OmniBAS manual, chapter Maintenance Procedures, section Backing up Configuration. In the uni|MS management software, click the NE, then select the Inventory tab and note down the current system firmware version (see example below).
3 4
From the DC distribution board, switch off the circuit breaker(s) in order to power down the OmniBAS node. Remove all cables from the front panel of the control card. If necessary, place temporary stickers with marking on each cable. Remove the two side screws securing the module in place.
205
P7 Replacing the Control Card, Continued

Step 5
Action OmniBAS-4W: Pull both handles of the control card outward (a) so that the card is disengaged from the backplane connectors. Then, extract card completely (b).
OmniBAS-2W: By hand, fully loosen the two side screws of the control card. Then, carefully pull out card by its screws to disengage from the backplane connectors and extract. 6 OmniBAS-4W: Insert a new control card of the same type. Push its handles inwards to engage card with the connectors at the backplane. Re-install and tighten the two screws (previously removed) to secure the card in place.
OmniBAS-2W: Carefully insert a new control card of the same type. By hand, fully tighten the two side screws of the card to engage the card with the connectors at the backplane and secure it in place.
206
P7 Replacing the Control Card, Continued

Step 7 8 9
Action Re-install all cables previously removed. From the DC distribution board, switch on the circuit breaker(s) to power up the OmniBAS node. In the uni|MS management software, click the NE, then select the Inventory tab and check the system firmware version (see example below): a. If firmware is the same or a newer version (with respect to the one tracked in step 2), proceed to step 10. b. If not, carry out an OmniBAS indoor unit upgrade, as instructed in the Technology Driver manual for OmniBAS, chapter Maintenance Procedures, section Upgrading NE Software.
10
Using the uni|MS management software, carry out a system configuration restore in order to restore the latest configuration of the OmniBAS node. Refer to the Technology Driver for OmniBAS manual, chapter Maintenance Procedures, section Restoring Configuration. After the restore process is completed, check and verify all the configuration settings of the OmniBAS node.
11
End of procedure.
207
P8 Replacing the Radio Unit (ODU)

Introduction
This procedure concerns the replacement of an OmniBAS radio unit (ODU) for the following cases: ODU directly attached to an antenna or coupler system. ODU attached to its own support and interfacing with the (external) antenna through a flexible waveguide.
NOTE
Always use an appropriate spare ODU of the same frequency characteristics.
Procedure: ODU directly attached to an antenna / coupler
To replace an ODU attached directly to an antenna or a coupler system, proceed as follows: Step 1 2 Action Identify the modem card (fitted in the OmniBAS indoor unit) that is connected with the ODU to be replaced. If ODU is standalone (i.e. unprotected link): From the management application, click the ODU and select Configuration tab. Power down ODU (DC Power = Off) and then remove the coaxial IF cable and angle adapter from the modem card. First extract the modem card. Then, remove the coaxial IF cable and its angle adapter from the modem card.
If ODU is protected (hot-standby):
On the tower (or on the buildings roof), confirm that the ODU to be replaced is the correct one. Hint #1: Connecting the RSSI cable onto an ODU and reading the voltage on a multimeter can verify if ODU operates or not. No reading means that the ODU is not operating. Hint #2: if no clear marking is available on the coaxial cable, and provided that the outdoor weather conditions allow, try touching the ODU case. The ODU to replace is the cooler one among other neighboring ODUs, as it is not yet powered by the indoor unit.
208
P8 Replacing the Radio Unit (ODU), Continued

Procedure: ODU directly attached to an antenna / coupler (continued)
Step 4
Action From the ODU, uninstall the following: Grounding cables terminal (a). Coaxial cables connector (b), after removing the connectors black insulation. Use a U-ring spanner 11 mm. (Photo shows an ODU attached directly to an antenna).
Carefully unlock the four clamps securing the ODU at the back of the antenna / coupler. Unlock clamps in diagonal fashion to avoid accidental drop of the ODU:
Carefully install an appropriate spare ODU of the same frequency characteristics.

NOTE
Beware of the correct orientation of the new ODU during installation. Secure the ODU at the back of the antenna / coupler by carefully locking its four clamps.
209

Procedure: ODU directly attached to an antenna / coupler (continued)
Step 7 8
Action Re-install the grounding cables terminal. Re-install the coaxial IF cable on the corresponding receptacle of the new ODU.
NOTE
Re-insulate the coaxial connector termination on the new ODU, as instructed in the Installation & Cabling Manual (OmniBAS radio equipment).
Re-install the angle adapter of the coaxial cable to the modem card. Apply a maximum 1.7 Nm tightening torque; this practically corresponds to 90o rotation of the connector after it is hand-tightened. Using the uni|MS management software, click the new ODU, then select the Status tab and check the value shown next to the Software Update field (see below): a. If Software Update = Updated, the new ODU has the correct firmware version. Go to step 11. b. If Software Update = Needs Update, the new ODU needs a firmware update. Carry out an ODU upgrade, as instructed in the Technology Driver for OmniBAS manual, chapter Maintenance Procedures, section Upgrading ODU Software.
NOTE
10
The upgrading process takes approx. 12 min. to complete. When finished, re-check the Software Update status of the new ODU to verify its successful upgrade.
11
End of procedure.
210

Procedure: ODU attached to own support
To replace an ODU that is attached to its own support system, proceed as follows: Step 1 2 Action Identify the modem card fitted in the OmniBAS indoor unit that corresponds to the ODU to be replaced. If ODU is standalone (i.e. unprotected link): From the management application, click the ODU and select Configuration tab. Power down ODU (DC Power = Off) and then remove the angle adapter of the coaxial IF cable from the modem card. First extract the modem card. Then, remove the angle adapter of the coaxial IF cable from the modem card.
If ODU is protected (hot-standby):
On the tower (or on the buildings roof), confirm that the ODU to be replaced is the correct one. Hint #1: Connecting the RSSI cable onto an ODU and reading the voltage on a multimeter can verify if ODU operates or not. No reading means that the ODU is not operating. Hint #2: if no clear marking is available on the coaxial cable, and provided that the outdoor weather conditions allow, try touching the ODU case. The ODU to replace is the cooler one among other neighboring ODUs, as it is not yet powered by the indoor unit.
From the ODU, uninstall the following: Grounding cables terminal. Coaxial cables connector, after removing the connectors black insulation. Use a U-ring spanner 11 mm.
211

Procedure: ODU attached to own support (continued)
Step 5
Action With an appropriate hexagonal key, carefully remove the four screws securing the waveguide on the antenna feeder at the back of the ODU.
NOTE
Beware not to remove the o-ring from the waveguide. Do not bend the waveguide after its removal from the back of the ODU. Keep it hung close to the intended fixing position.
Carefully unlock the four clamps securing the ODU on the support system. Unlock clamps in diagonal fashion to avoid accidental drop of the ODU. Carefully install a new ODU of the same model and frequency characteristics.
NOTE
Beware of the correct orientation of the new ODU during installation. Secure the ODU by carefully locking its four clamps.
Re-install the grounding cables terminal.

212

Step 9
Action Re-install the coaxial IF cable on the corresponding receptacle of the new ODU.
NOTE
Re-insulate the coaxial connector termination on the new ODU, as instructed in the Installation & Cabling Manual (OmniBAS radio equipment).
10
With the same hexagonal key and using the four screws previously removed, carefully re-install the waveguide flange on the antenna feeder at the back of the ODU.
NOTE
Apply a maximum 4.5 Nm torque when tightening the four screws.
11
Re-install the angle adapter of the coaxial cable to the modem card. Apply a maximum 1.7 Nm tightening torque; this practically corresponds to 90o rotation of the connector after it is hand-tightened.
213

Step 12
Action Using the uni|MS management software, click the new ODU, then select the Status tab and check the value shown next to the Software Update field (see below): a. If Software Update = Updated, the new ODU has the correct firmware version. Go to step 13. b. If Software Update = Needs Update, the new ODU needs a firmware update. Carry out an ODU upgrade, as instructed in the Technology Driver manual for OmniBAS, chapter Maintenance Procedures, section Upgrading ODU Software.
NOTE
The upgrading process takes approx. 12 min. to complete. When finished, re-check the Software Update status of the new ODU to verify its successful upgrade.
13
End of procedure.
214
P9 Measuring Modems DC Voltage Out

Overview
This procedure is carried out to check whether an installed modem card is capable to output the required DC voltage (typically -48 V) toward the ODU. This voltage is equal to the OmniBAS systems input DC voltage, which may be within the specified range (refer to OmniBAS system description).
Procedure
To measure the modems DC voltage out, proceed as follows: Step 1 2 3 Action Carefully remove the angle adapter of the coaxial cable from the ODU receptacle of the respective modem card. Adjust a multimeter for DC voltage measurement. a. On the exposed part of the red lead (+) of the multimeter (see detail in the schematic below), apply two turns of electrical tape to isolate the exposed metallic part, except the tip. b. Connect the black lead (-) of the multimeter to the outer conductor of the ODU receptacle. c. Carefully insert the tip of the red lead (+) into the center conductor of the ODU receptacle.
Measure the DC voltage. If found to be equal to system voltage, re-install both the angle adapter and the coaxial cable. If not, replace the modem card (P6 procedure).
End of procedure.
215

OmniBAS Troubleshooting 01 en

Uploaded by

Copyright:

Available Formats

OmniBAS Troubleshooting 01 en

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

OmniBAS Troubleshooting 01 en

Uploaded by

Copyright:

Available Formats

What is the document about?

What is the document about?

What steps are involved in measuring a modem's DC voltage output?

What steps are involved in measuring a modem's DC voltage output?

GDC-003/11

OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0

OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0

OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0

Introduction About this Document

Software Version 3.0_1210.1.4.1 3.0_1200.4.1 2.4_1220.1.0.0 3.0_1200_1210.1.5.1 3.0_1400.2.6.1 3.0_1410.1.0.0

Support of PTP-R modem card (28 GHz).

OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0

About this Document, Continued

OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0

OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0

EXTERNAL OVER-VOLTAGE PROTECTION

OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0

Troubleshooting of Onsite Incidents

Basic troubleshooting by hardware swapping

OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0

Troubleshooting of Onsite Incidents, Continued

A. Installation without Waveguide (between ODU & Antenna): Without OMT:

Problem shifted to Modem A path.

Coaxial B or ODU B or OMT /Antenna B (Antenna) (refer to step 2).

Only Modem A path has problem. Problem shifted to Modem A path.

Coaxial B. OMT /Antenna B (Antenna). Continued on next page

OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0

Troubleshooting of Onsite Incidents, Continued

Step 2: Swap coaxial cables A & B (ODU side).

Problem shifted to Modem B path.

ODU B or OMT /Antenna B (Antenna) (refer to step 3).

Step 3: Swap ODU A & B.

Problem persists for Modem B path. Problem shifted to Modem A path.

OMT /Antenna B (Antenna).

Continued on next page

OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0

Troubleshooting of Onsite Incidents, Continued

B. Installation with Waveguide W/G (between ODU & Antenna):

Action Step 1: Swap coaxial cables A &B (modem side).

Results Both paths have problem.

Suspected Issue Configuration settings have errors.

Step 2: Swap coaxial cables A & B (ODU side).

OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0

Troubleshooting of Onsite Incidents, Continued

Step 3: Swap W/G A & B (ODU side).

W/G B or Antenna B (refer to step 4).

Step 4: Swap W/G A&B (Antenna side).

OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0

Indoor Unit Not Powered Up

Causes & actions

Implications Potential short-circuit condition.

Wrong circuit breaker(s) activated or breaker(s) are under-rated.

Indoor unit cannot operate.

OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0

Management Connection Not Feasible

ETH 100/1000, GbE GbE ETH 10/100 NMS 10/100

RJ-45 (electrical) SFP RJ-45 (electrical) RJ-45 (electrical)

Continued on next page

OmniBAS-2W /-4W Troubleshooting Manual Edition 1.0