omnibas troubleshooting 01 en

GD

C-0

03/1

1

INTRACOM TELECOM19.7 km Markopoulou Ave., Peania, Athens, GR 19002

T +30 210 667 1000, F +30 210 667 1001http://www.intracom-telecom.com

email (product support): [email protected]

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 containsare 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 purposewhatsoever 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 changewithout prior notice.

All trademarks and copyrights mentioned herein are the property of INTRACOM S.A. TELECOMSOLUTIONS and/or their respective owners.Any rights not expressly granted herein are reserved.

Printed in Greece.

OmniBAS-2W /-4WTroubleshooting Manual Edition 1.0

1

Table of Contents

Introduction.......................................................................................................... 3About this Document................................................................................... 3Declaration of Conformity............................................................................ 4Equipment Disposal .................................................................................... 5Safety Precautions...................................................................................... 6

1. Troubleshooting of Onsite Incidents.......................................................... 7Indoor Unit Not Powered Up ..................................................................... 12Management Connection Not Feasible ..................................................... 13System Synchronization Error................................................................... 20Control Card Not Operational.................................................................... 22Modem Card(s) Cannot be Recognized.................................................... 23Modem Card Not Operational ................................................................... 24Outdoor Radio (ODU) Not Operational...................................................... 25Radio Link Cannot Be Established............................................................ 30Radio Link Cannot Achieve Expected Performance.................................. 37Ethernet Physical Layer is Down............................................................... 45

2. Troubleshooting of uni|MS Alarms........................................................ 48General Alarms .......................................................................................... 54

Lost Communication with Element ............................................................ 54Equipment Extracted................................................................................. 59Part of Service has been Deactivated ....................................................... 60Part of Pending Service has been Activated ............................................. 61AEnd Down............................................................................................... 62ZEnd Down............................................................................................... 63Management Connection Closed.............................................................. 64License Violation....................................................................................... 65

Indoor Unit Alarms..................................................................................... 66Input Alarm 1 /2 /3 /4................................................................................. 66Fan Failure ............................................................................................... 68Fan Extracted ........................................................................................... 70PSU Failure .............................................................................................. 71Low Temperature...................................................................................... 72High Temperature..................................................................................... 73

Modem Card Alarms.................................................................................. 75Modem Failure.......................................................................................... 75Power Failure............................................................................................ 76Invalid Modem Inserted............................................................................. 78PHY Modulation Failure ............................................................................ 79Clock PLL Unlocked.................................................................................. 81Receiver PLL Unlocked ............................................................................ 82Transmitter PLL Unlocked......................................................................... 83Modem Chip Failure.................................................................................. 84Modem Chip Unlocked.............................................................................. 85

Radio Link Alarms ..................................................................................... 86Modem Link Failed.................................................................................... 86Remote Modem Link Failed ...................................................................... 87RAI Alarm (Modem Group 1-2 /1-3 /2-4) ................................................... 88RAI Blocked Alarm.................................................................................... 92ODU RSSI Alarm ...................................................................................... 95Rx Normalized MSE (SNR) Alarm............................................................. 98


2

Rx LDPC Decoders Stress Alarm ........................................................... 101East Port (Modem 2) of Ring Failure....................................................... 103West Port (Modem 1) of Ring Failure...................................................... 107

Outdoor Unit (ODU) Alarms .................................................................... 111ODU Communication Failure .................................................................. 111ODU Pout ALC Alarm ............................................................................. 113ODU Rx PLL LD Alarm ........................................................................... 115ODU Tx PLL LD Alarm............................................................................ 117ODU Tx Configured Frequency Out of Range Alarm............................... 119ODU RF PLL LD Alarm........................................................................... 122ODU MW PLL LD Alarm ......................................................................... 124ODU Loopback PLL LD Alarm ................................................................ 126Tx ODU Configured Power Out of Range Alarm ..................................... 128ODU High Temperature Alarm................................................................ 130ODU RSSI Rx User Alarm ...................................................................... 132ODU Min Pif Alarm.................................................................................. 135ODU Model Alarm................................................................................... 137ODU H/W Bandwidth Alarm.................................................................... 139ODU Cable Calibration Alarm ................................................................. 141ODU Max Pif Alarm................................................................................. 143ODU Low If Alarm................................................................................... 145ODU Low Temperature Alarm................................................................. 147

E1 Line Alarms......................................................................................... 149E1 Line LOS ........................................................................................... 149E1 Line LOF............................................................................................ 151E1 Line AIS............................................................................................. 153E1 Line RAI ............................................................................................ 155E1 Line Admin Down .............................................................................. 157E1 is Looped........................................................................................... 158E1 Local Loop......................................................................................... 160E1 Remote Loop..................................................................................... 162

Ethernet Line Alarms............................................................................... 164SFP Tx Fault........................................................................................... 164SFP Rx LOS ........................................................................................... 166Ethernet Link Down................................................................................. 168

3. Troubleshooting of Problems Reported by Customers ........................ 171Radio Link is Down ................................................................................. 172Ethernet Service Outage (or with Errors) ................................................ 176E1 Service Outage (or with Errors) ......................................................... 184E1 Synchronization Issues...................................................................... 189

Appendix: Procedures Relevant to Troubleshooting.................................... 193P1 Measuring the Input Voltage........................................................... 194P2 Replacing the Fan Tray (OmniBAS-4W) ......................................... 195P3 Getting the IP Addresses (Serial Connection)................................. 196P4 Replacing the E1 Interface Card (OmniBAS-4W)............................ 198P5 Realigning the Antennas................................................................. 199P6 Replacing a Modem Card ............................................................... 203P7 Replacing the Control Card............................................................. 205P8 Replacing the Radio Unit (ODU)..................................................... 208P9 Measuring Modems DC Voltage Out.............................................. 215


3

Introduction

About this Document

Scope This document aims at providing first-level troubleshootinginstructions for established Point-to-Point (PtP) links based onOmniBAS-2W and OmniBAS-4W systems.

Concernedproducts

Product Software VersionOmniBAS-2W Ethernet only 3.0_1210.1.4.1OmniBAS-2W 8E1 3.0_1200.4.1OmniBAS-2W 16E1 2.4_1220.1.0.0OmniBAS-2W RC (1) 3.0_1200_1210.1.5.1OmniBAS-4W 2GbE 3.0_1400.2.6.1OmniBAS-4W 2GbE / 2FE 3.0_1410.1.0.0

Classificationof incidents

In the following pages, troubleshooting instructions are given for avariety of incidents. The latter are classified in three majorcategories, according to how incidents are notified to the installer,the commissioner or the NOC operator:

OnsiteIncidents

Incidents that occur locally during the installation,commissioning or the maintenance of equipment.Onsite incidents are elaborated in chapter 1.

AlarmNotifications

uni|MS management notifications on alarmsituations associated with malfunctioningequipment or degradation of services.Alarms are elaborated in chapter 2.Chapter headings correspond to the alarmstext description, as provided by uni|MS.This facilitates readers in quickly accessingtroubleshooting information.

ProblemReports

Problems that are reported to the Call Center (bycustomers) and which they are associated withdegraded or interrupted services.Reported problems are elaborated in chapt. 3.

The Appendix contains all testing & hardware replacementprocedures to carry out during the equipment troubleshooting.

Continued on next page

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


4

About this Document, Continued

Targetaudience

The information given in this document is intended for techniciansauthorized to carry out troubleshooting tasks, inclusive of:

Task Required SkillsFault localizationand recovery.

Trained on OmniBAS systeminstallation /commissioning /operation.

Capability to carry out diagnostic andcorrective procedures using theuni|MS management software.

Basic networking skills. Experience in using generic

troubleshooting practices andmethodologies.

Onsite hardwarereplacement andmeasurements.

Experience in replacing hardware. Capability to carry out performance

tests and measurements.

Referencedocuments

The following documents, which are available by IntracomTelecom, may be needed during troubleshooting:

# Reference Document1 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.

Contactinformation

Intracom S.A. Telecom Solutions19.7 km Markopoulou Ave., Peania, Athens, GR-19002Tel. (+30) 210 667 1000, Fax: (+30) 210 667 1001email (support): [email protected]

Declaration of Conformity

Hereby, Intracom S.A. Telecom Solutions declares that theOmniBAS systems are in compliance with the essentialrequirements 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


5

Equipment Disposal

Disposal of old electrical and electronic equipment (applicable throughthe European Union and other European countries with separate wastecollection systems).

This symbol, found on this product and any of its parts or on its operatinginstructions or on its packaging, indicates that electrical and electronicequipment may not be disposed of as unsorted municipal waste. Instead,this product should be handed over to applicable collection points for therecycling of electrical and electronic equipment.By ensuring the correct disposal of this product, you will help preventpotential 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 andelectronic equipment you are making an important contribution to theconservation of natural resources and to the protection of the environment.For more information about the recycling of this product, please contact yourlocal municipal authorities, municipal waste disposal service or the storewhere you purchased this product.

( ).

, , , , . . , , . , . , , . , .. (www.electrocycle.gr).


6

Safety Precautions

WORKING ON THE BUILDINGS ROOFDuring stormy weather, do not perform any mechanical assembling orantenna beaming (alignment) works on the buildings roof.The metal structure of towers/ masts is prone to lightning.

ESD PROTECTIONAlways use proper antistatic protection when handling ESD sensitive parts.Protection is provided by means of a grounding bracelet, antistatic bags, etc.

EXTERNAL OVER-VOLTAGE PROTECTIONEnsure the existence of external over-voltage protection (of rating thatexceeds 1.5 kV) at the input and the output of the indoor unit, prior to itsconnection to the network.Lack of external protection could cause damage to the equipment.


7

1. Troubleshooting of Onsite Incidents

Introduction This chapter deals with onsite incidents that might occur duringthe onsite installation, commissioning or maintenance of theequipment. A problem is usually notified visually:

either through the activation of an alarm indicator (on thefront panel of the indoor unit), or

through the unexpected behavior of the equipment (duringits power up process for instance).

Basic trouble-shooting byhardwareswapping

The following procedure is carried out when the field technician isnot familiar with the OmniBASs software alarms andtroubleshooting methodology, and there is lack of spareequipment (i.e. cards).By swapping equipment in a specific order, the field technician willbe able to localize the fault, provided that other collocated linksare readily available and that downtime is allowed.`The field technician must be able to correctly and accordinglyconfigure the following:

Modem operation (protected / standalone). Modem parameters. ODU

NOTE When swapping equipment, the field technicianshould be able to recognize what configurationchanges are needed to be done in order tosuccessfully re-establish the links.To avoid problems, technician should first carry outbackup of the initial configuration (prior toproceeding) and restore it as soon as he/she finisheswith hardware swapping troubleshooting.

In the following two examples, we assume that Link A is up andLink B is down.



8

Troubleshooting of Onsite Incidents, Continued

Basic trouble-shooting byhardwareswapping,continued

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

Without OMT:

With OMT:

Action Connections Results Suspected IssueBoth paths haveproblem.

Configurationsettings have errors.

Only Modem Bpath hasproblem.

Modem B.

Problem shiftedto Modem A path.

Coaxial B or ODU Bor OMT /Antenna B(Antenna) (refer tostep 2).

Only Modem Apath hasproblem.

Coaxial B.

Step 1:Swapcoaxialcables A &B (modemside).

Modem A CoaxialB ODU B OMTPort B Antenna B(Antenna)

Modem B CoaxialA ODU A OMTPort A Antenna A(Antenna)


OMT /Antenna B(Antenna).



9



A. Installation without Waveguide (between ODU & Antenna),continued:

Action Connections Results SuspectedIssue

Both paths haveproblem.

Configurationsettings haveerrors.

Only Modem Apath hasproblem.

Coaxial B.

Step 2:Swapcoaxialcables A &B (ODUside).

Modem A Coaxial BODU A OMT Port AAntenna A (Antenna)

Modem B Coaxial AODU B OMT Port BAntenna B (Antenna) Problem shifted

to Modem B path.

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

Problem persistsfor Modem Bpath.

ODU B.Step 3:Swap ODUA & B.

Modem A Coaxial BODU A OMT Port BAntenna B (Antenna)

Modem B Coaxial AODU B OMT Port AAntenna A (Antenna)


OMT /Antenna B(Antenna).



10



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 Connections Results Suspected Issue



Only Modem Bpath has problem. Modem B.

Step 1:Swapcoaxialcables A& B(modemside).

Modem ACoaxial BODU B W/G B Antenna B

Modem BCoaxial AODU A W/G A Antenna A


Coaxial B or ODUB or W/G B orAntenna B (refer tostep 2).



Only Modem Apath has problem. Coaxial B.

Step 2:Swapcoaxialcables A& B (ODUside).

Modem ACoaxial BODU A W/G A Antenna A

Modem BCoaxial AODU B W/G B Antenna B

Problem shiftedto Modem B path.

ODU B or W/G B orAntenna B(refer to step 3).



11



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

Action Connections Results Suspected Issue

Problem persistsfor Modem Bpath.

ODU B.Step 3:Swap W/GA & B (ODUside).

Modem AODU ACoupler A W/GB Antenna B

Modem BODU B W/G A Antenna A


W/G B orAntenna B (referto step 4).

Problem persistsfor Modem Apath.

W/G B.Step 4:Swap W/GA & B(Antennaside).

Modem AODU A W/G B Antenna A

Modem BODU B W/G A Antenna B

Problem shiftedto Modem B path. Antenna B.


12

Indoor Unit Not Powered Up

Explanation The OmniBAS-2W /-4W indoor unit is not powered up after it isswitched on for the first time.

Indication After the indoor unit is switched on, all front-panel leds remain off.

Causes &actions

# ProbableCauses

Implications Suggested RecoveryProcedure

1 Power cable isimpaired or itsconnector isincorrectlyinserted.

Potentialshort-circuitcondition.

Check for connector /terminal displacement atboth ends of the cable.Investigate for visualdeterioration along theentire run of the cable.

2 Inappropriateinput voltage.

Measure the input voltageapplied to the indoor unit(P1 procedure). If voltageis found out of theequipment manufacturersrange, use a differentpower supply source.

3 Wrong circuitbreaker(s)activated orbreaker(s) areunder-rated.

Ensure that you haveactivated the correctbreaker(s).Ensure that breaker(s) arerated at the amperagespecified by the equipmentmanufacturer.

4 Only forOmniBAS-4W:PSU card notcorrectlyinserted.

5 Only forOmniBAS-2W:Controller cardnot correctlyinserted.

Indoor unitcannotoperate.

Gently push the card fullyinwards to ensure propercontact with the pins at thebackplane.Then, secure card in placeby fully tightening its sidescrews.


13

Management Connection Not Feasible

Explanation Communication with the OmniBAS-2W /-4W indoor unit, usingone of its front-accessible ports (see table below), is unfeasible:

Port is Used forCarrying

Designation onPort

Port Type

Payloadtraffic

InbandMngt.

OutbandMngt.

ETH 100/1000,GbE

RJ-45(electrical) x

GbE SFP x

ETH 10/100 RJ-45(electrical) x

NMS 10/100 RJ-45(electrical) x x

Indication a. Status of leds on Ethernet ports (while waiting for pingresponse 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 pingcommand.

b. On-screen notification (while waiting to connectthrough the uni|MS Node Manager):

Example: if you are trying to access the IP address172.28.77.16, then the following message appears:



14

Management Connection Not Feasible, Continued

Causes &actions (1/2)

A. Outband management connection:

# ProbableCauses


1 The Ethernetcable,connectingthe laptop tothe OmniBASindoor unit, isimpaired.

Replace cable with a newone and re-try.

2 Wrong IPaddress. (1)

TheOmniBASsystemcannot bemanagedthrough theoutbandmanagementport. a. Connect the laptopto the AUX port and

get the IP address ofthe system (P3procedure).

b. Change the IPaddress of the laptopor the indoor unit sothat they both belongto the same subnet.


(1) The default IP address for the outband management is 192.168.1.100, which can bechanged. In such a case, management communication over the outband channel will befeasible only through the new IP address.


15



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 anduntagged traffic).

# ProbableCauses

Implications

Suggested RecoveryProcedure

1 The Ethernetcable,connected onthe local unitand carryinginbandmanagement,is impaired.

Replace cable with a newone and re-try.

2 Ethernet portis physicallydown.

Carry out troubleshooting asinstructed for case:

Ethernet Physical Layeris Down


Cannotmanagelocal as wellas any otherOmniBASunitsmanagedthrough thelocalOmniBASunit.

If the correct IP addresscannot be found then:

a. Connect the laptop toan outbandmanagement port(NMS 10/100).

b. From themanagementapplication, clickOmniBAS NE andselect Configuration> Management tabto type the inbandmanagements IPaddress.

NOTE Both laptop andOmniBAS unitsoutbandmanagement portmust belong tothe same subnet.


(1) When not configured, inband managements IP address is 10.10.10.100.


16



B. Inband management connection local unit (gateway),continued:

# ProbableCauses


4 Inband /outbandconflict.

Cannot managethe OmniBASunit.

a. Connect the laptopto an outbandmanagement port(NMS 10/100).

b. From themanagementapplication, clickOmniBAS NE andselectConfiguration >Management tab.

c. Set the inband andoutband IPaddresses to belongto a differentsubnetwork.

5 The VLAN ofthe Ethernetport (to beused forinbandmanagement)is notconfiguredcorrectly.

Cannot managethe OmniBASunit (through theinbandmanagementport).

Set inband managementports default VLAN tothe same value shownnext to VLAN ID field inthe InbandManagementParameters group box(right click OmniBAS NEand selectConfiguration tab >Inband / Outband / RTCtab).



17



B. Inband management connection local unit (gateway),continued:

# ProbableCauses


6 Congestionexists on thenetwork andQoS has notbeen set.

Problematic or noinbandmanagement ofboth local(gateway) unitand otherOmniBAS unitsmanaged throughthe local unit.

Enable QoS and makesure that managementtraffic has the highestpriority queue withrespect to the one forall other types of traffic.

7 Bridge loopsexist in thenetworkwithout properconfiguration.

a. Connect the laptopto an outbandmanagement port(NMS 10/100).

b. Remove the logicalloop(s).

8 Control cardhas failed.

Problematic or noinbandmanagement andpayload traffic inthe network.

Replace the controlcard 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) usinga laptop and untagged traffic).

# ProbableCauses


1 Local(gateway)OmniBAS unithas problem.

Cannot manageremote OmniBASunit(s)participating inthe same link.

For troubleshooting,refer to the previousinband managementcase (B).



18



C. Inband management connection remote unit(s) managedthrough the local (gateway) unit, continued:

# ProbableCauses



Cannotmanage theremoteOmniBASunit.

Connect to the localOmniBAS unit and fromwithin the modem statusscreen, find the IP addressof the remote OmniBASunit.

3 Inband /outbandconflict.

Cannotmanage theremoteOmniBASunit.

a. Visit remote site.b. Connect the laptop

to an outbandmanagement port(NMS 10/100).

c. From themanagementapplication, clickOmniBAS NE andselectConfiguration >Management tab.

d. Set the inband andoutband IPaddresses tobelong to a differentsubnetwork.

4 OmniBAS isnot configuredto passinbandmanagementfor the rest ofthe elementsin thenetwork.(2)

Remotemanagementcannot passthrough thespecificOmniBASunit.

Create the appropriateassociations of the inbandmanagement VLAN id withthe required Ethernet ports(right click OmniBAS NE >Configuration tab >L2 Properties tab >VLAN/VLAN Port tab).


(1) When not configured, inband managements IP address is 10.10.10.100.

(2) Assuming that the links in the network are established and working properly.


19


Causes &actions (6/6) # Probable

CausesImplications Suggested Recovery

Procedure5 Link outage or

withproblematicbehavior.

Remotemanagementcannot passthrough thespecificOmniBASunit.

Carry out troubleshootingof the problematic link(s).Refer to cases:

Radio Link Cannot BeEstablishedRadio Link CannotAchieve ExpectedPerformance

6 Congestionexists on thenetwork andQoS has notbeen set.

Problematicor no inbandmanagementof both local(gateway) andthe remoteOmniBASunits withinthe same link.

Enable QoS and makesure that managementtraffic has the highestpriority queue with respectto the one for all othertypes of traffic.

7 Bridge loopsexist in thenetworkwithout properconfiguration.

a. Connect the laptop toan outbandmanagement port(NMS 10/100).

b. Remove the logicalloop(s).

8 Control cardhas failed.

Problematicor no inbandmanagementand payloadtraffic in thenetwork. Replace the control card

with a spare one (P7procedure).


20

System Synchronization Error

Explanation The OmniBAS system has a synchronization error, which mayhave impact on the delivered services.

Indication OmniBAS-2W:

OmniBAS-4W:

The led STAT2 (STATUS2)on the control card:

blinks amber,meaning that thesystem is running inholdover mode, or

is off, meaning thatthe system is out ofsynchronization.

Causes &actions

# ProbableCauses


1 Clocksource isnot correctlyconfigured.

ProblematicE1 servicedue to slips.

From the managementapplication, click the OmniBASsystem and selectConfiguration >Synchronization tab.Select and configure anappropriate clock source, asinstructed in the Driver forOmniBAS reference manual.

2 Thepredefinedclocksource isabsent orhasproblem.

Systemoperates inholdovermode.ProblematicE1 servicedue to slips.

Click the OmniBAS systemand select Configuration >Synchronization tab.Check if clock sourcesOperation Status = Locked.If not, check clock source itself(cable, clock accuracy, etc.). Ifan alternative clock source isavailable, try using this source.



21

System Synchronization Error, Continued

Causes &actions(continued) # ProbableCauses


3 Controlcardssynchro-nizationcircuitry hasfailed.

Problematic E1service due toslips.

a. From themanagementapplication, perform asystem reset.

Resetting thesystem will resultin interruption ofall OmniBAS nodeservices.

b. If problem persists,replace the controlcard (P7 procedure).


22

Control Card Not Operational

Explanation The control card (fitted in the OmniBAS-2W /-4W indoor unit)malfunctions, or it has failed.


OmniBAS-4W:

The led STAT1(STATUS1) on the controlcard is:

off, meaning thatthe control card isnot powered, or

red, meaning thatthe control cardhas failed.

Causes &actions

# ProbableCauses


1 All leds on allcards are off:Generic powersupply problem.

Refer to case:Indoor Unit NotPowered Up

2 Leds on othercards light up:Internal controlcard failure.

2 Internal controlcard failure(STATUS 1/STAT1 led =red).

All servedlinks are outof operation.

a. From themanagementapplication, performa system reset.

b. If problem is notfixed, try performinga hard reset byswitching off and onthe power supplybreaker(s).

c. If problem persists,replace the controlcard with a spareone (P7 procedure).


23

Modem Card(s) Cannot be Recognized

Explanation The control card cannot communicate with one (or more) modemcards fitted in the OmniBAS-2W /-4W indoor unit.


OmniBAS-4W:

The led MDM (MODEM) onthe concerned modem cardis off, red (or blinks red),meaning that the card is notcorrectly installed (or it hasfailed).

Causes &actions

# ProbableCauses


1 Modemcard is notcorrectlyinstalledinto theindoorunit.

a. Carefully extract themodem from its slot.

b. Inspect the condition ofcards backplane pins. Ifpins are found impaired,proceed to step 2b.

c. Fully reinsert card backin slot and secure inplace.

2 Modemcardfailure.

Unprotectedoperation:Link out ofoperation.

Protectedoperation:Linkprotection nolongeravailable.

a. From the managementapplication, perform amodem card reset.

b. If nothing changes,replace the modem card(P6 procedure).

c. If problem still persistsand other modems alsohave problem, thenperform a system reset.

d. If problem is not fixed,perform a hard reset byswitching off and on thepower supply breaker(s).


24

Modem Card Not Operational

Explanation A specific modem card (fitted in the OmniBAS-2W /-4W indoorunit) has failed.


OmniBAS-4W:

The led PWR on themodem card is off or red,meaning that the modemcard has failed.

Causes &actions

# ProbableCauses


1 Modem cardfailure.

Unprotectedoperation:Link out of operation.

Protectedoperation:Link protection nolonger available.

Replace the modemcard (P6 procedure).


25

Outdoor Radio (ODU) Not Operational

Explanation Incident that is observed locally and which is associated with aproblem somewhere in the hardware chain: modem card coaxialcable outdoor unit (ODU).

Indication a. Change in Status of Front-panel Leds (Modem Card):

OmniBAS-2W:

OmniBAS-4W:

The led ODU on the modem card:

is off, meaning that theODU is disabled (i.e. notpowered from theinterconnected modemcard),

lights up green, meaningthat the ODU is presentand not muted,

blinks green, meaning thatthe ODU is present andmuted,

lights up amber, meaningthat the ODU is presentand not muted but has analarm,

blinks amber, meaningthat the ODU is presentand muted but has analarm,

lights up red, meaning thatthe ODU is not present orit has a power failure at itsinput,

blinks red, meaning thatthe ODU is present but themodem ODUcommunication has errors.

b. Listing of Relevant uni|MS Alarms:Refer to section Outdoor Unit (ODU) Alarms, on page 111, whereall the relevant alarms are explained.



26

Outdoor Radio (ODU) Not Operational, Continued

Causes &actions

# ProbableCauses


1 ODU isdisabled.

From the uni|MSmanagement application,try re-activating ODU.

(i.e. set DC Power = ON)

2 The coaxialcable,interconnectingthe modemcard with theODU, isimpaired.

Inspect coaxial cablesterminations at both ends.Then, inspect the cableitself.

3 The coaxialcable,interconnectingthe modemcard with theoutdoor radiobox, is too long.

Investigate a differentroute that shortens thecoaxial cables total lengthor replace the existingcable with another, betterquality one.

4 ODU hasfailed.

Replace the ODU with aspare one (P8 procedure).

5 Modem cardhas failed.

Unprotectedoperation:

Link out ofoperation.

Protectedoperation:

Link protectionno longeravailable.

Replace the modem cardwith a spare one (P6procedure).



27


Recoveryprocedure

Execute one of the following three troubleshooting flowcharts toresolve the onsite problem, based on the observed status of themodem card ODU communication:

A. Modems ODU led is blinking red:

START

NoYes

Coaxialcable and itsterminations

ok?

ODU ledon modem flashing

red?

END

Replace modem(P6 procedure)

No

YesNo

ODU ledon modem stillflashing red?

YesNo

Replace ODU(P8 procedure)

Repair cable orterminals



28


Recoveryprocedure,continued

B. Modems ODU led is off:



29


Recoveryprocedure,continued

C. Modems ODU led lights up red:


30

Radio Link Cannot Be Established

Explanation Incident that might be observed locally after the commissioning ofan OmniBAS link. In particular, the latter cannot be established.

NOTE This procedure must be carried out for the oneOmniBAS node or for both OmniBAS nodesparticipating in the problematic link.

Indication a. Status of Front-panel Leds (Modem Card):OmniBAS-2W:

OmniBAS-4W:

The led MDM / MODEM onthe modem card lights upamber, meaning that the linkis not established.



31

Radio Link Cannot Be Established, Continued

Causes &actions

# ProbableCauses


1 Wrongconfigu-rationsettings.

Check the following and correctif found wrong:

Modems configuredchannel size.

Modems configuredprofile (links mode).

ODUs configuredtransmit (Tx)frequency.

ODUs configuredtransmit (Tx) power. (1)

If ODU is disabled ormuted.

If ODU is looped.

2 Inter-ference



Check if other frequencies ofother collocated links conflictwith the links current Txfrequency.


(1) If modulation is set to manual, ODU should support this Tx power value.


32




3 Faulty orwrongly-installedhardware(1/4).



Step 1:Try to isolate the site with fault local or remote by setting asoftware ODU loopback (seebelow). If ODU does notsupport loopback, proceed tostep 2:

a. Dispatch a technicianto the remote site.

b. Activate an ODUloopback at the localsite and mute ODU atthe remote site. Checkif local site locks.

c. Deactivate the ODUloopback at the localsite and unmute ODUat the remote site.

d. Activate an ODUloopback at the remotesite and mute ODU atthe local site. Check ifremote site locks.

e. Deactivate the ODUloopback at the remotesite and unmute ODUat the local site.



33




Faulty orwrongly-installedhardware(2/4).



f. If both local and remotesites lock, techniciansat both sites shouldinspect the entire post-ODU paths (inclusiveof wave-guide, couplerand antenna) and actaccordingly.

g. If, after setting theloopbacks, one or bothsites are unable tolock, proceed to Step 2in order to troubleshootthe specific (or both)sites accordingly.

Step 2:Try to identify and replace thehardware that has failed(modem / ODU / cable /antenna). If loopback hasrevealed one problematic site,follow the instructions belowfor this specific site.Otherwise, follow instructionsfor both sites (the same holdstrue when ODU loopback isnot supported).

The following actions implyservices outage.For troubleshootersconvenience, the IF coaxialcables should be marked atboth ends with labels.

If extra links (1+1 or N+0,N>1) are available onsite:a. Swap IF connectors

at modem card side.



34







b. If the two modemsoperate in differentfrequencies (N+0), swapfrequencies. Otherwise,skip this step.

c. If problem persists for thesame modem, thenproblem resides inmodem itself. Replacewith spare modem(P6 procedure).

d. If problem passes to theother modem, thenproblem resides in ODU,IF cable or the post-ODUpath.

e. Inspect connectors at bothsides of the IF cable andfix if necessary.

f. Swap IF connectors atODU side.

g. If the two modemsoperate in differentfrequencies (N+0configuration), swapfrequencies. Otherwise,skip this step.

h. If problem passes to theother modem, replace theIF cable.

i. If problem persists for thesame modem, thenproblem resides in ODUitself. Replace with spareODU (P8 procedure).

j. If problem persists,inspect the entire post-ODU path (inclusive ofwaveguide, coupler andantenna) and actaccordingly.



35







k. After resolving the hardwareproblem, restore the originalcable configuration as wellas the correct transmitfrequencies (provided thatthey have been swapped inprevious step).

If no extra links are availableonsite (1+0 case):a. Inspect connectors at both

sides of the IF cable and fixif necessary.

b. First, replace modem card(P6 procedure). If problempersists, replace ODU witha spare one of the sametype (P8 procedure).

c. If problem persists, inspectthe entire post-ODU path(inclusive of waveguide,coupler and antenna) andact accordingly.

d. If problem persists andmodem still does not lock,replace the IF cable.

NOTE Troubleshooting in 1+0case should use trial-and-error, since noaction can secure thespecific part that hasfailed (modem, ODU,antenna etc). Engineermay decide to followthis procedure for 1+1or N+0 cases.



36




4 Radiotransmissionissues.



Check whether: The antenna is in

good condition andproperly installed.

The antenna isinstalled at thecorrect height.

The position of theantenna allowsappropriateadjustments inazimuth andelevation planes,regarding thepointing toward theremote site.

The antenna pointsto the right direction(i.e. toward theremote site). Ifantennamisaligned, carryout re-alignment,as described in P5procedure.

New obstaclesappeared in theline-of-sight path,not present duringthe radio planning.


37

Radio Link Cannot Achieve Expected Performance

Explanation Incident that might be observed locally after the commissioning ofan OmniBAS link. In particular, the latter cannot achieve theexpected radio performance.

NOTE This procedure must be carried out for bothOmniBAS nodes participating in the problematic link.

Indication There are several indications that might reveal a degraded or poorradio 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

# ProbableCauses


1 Wrongconfigurationsettings.

Check the following andcorrect if found wrong:

Modems configuredprofile (i.e. linksmode).

ODUs configuredtransmit (Tx)frequency.

ODUs configuredtransmit (Tx) power.(1)

If ODU is looped.

2 Inter-ference.


Protectedoperation:Linkprotection nolongeravailable. Check if other frequencies of

other collocated links conflictwith the links current Txfrequency.


(1) If modulation is set to manual, ODU should support this Tx power value.


38

Radio Link Cannot Achieve Expected Performance,Continued



2 Faulty orwrongly-installedhardware(1/5).

Unprotectedoperation:Servicedegradationwith errors ordrops.

Protectedoperation:Possibleservicedegradationwith errors orfrequentswitchovers.

Step 1:Try to isolate the site with fault local or remote by setting asoftware ODU loopback (seebelow). If ODU does notsupport loopback, proceed tostep 2:

a. Dispatch a technicianto the remote site.

b. Activate an ODUloopback at the localsite and mute ODU atthe remote site.

c. Start traffic test on oneE1 port (using BERtester). Check if trafficerrors areencountered at thelocal site.

d. Deactivate the ODUloopback at the localsite and unmute ODUat the remote site.



39







e. Activate an ODUloopback at theremote site and muteODU at the local site.Check if remote sitelocks.

f. Start traffic test on oneE1 port (using BERtester). Check if trafficerrors areencountered at theremote site.

g. Deactivate the ODUloopback at theremote site andunmute ODU at thelocal site.

h. If both local andremote sites measurewell, technicians atboth sites shouldinspect the entire post-ODU paths (inclusiveof wave-guide, couplerand antenna) and actaccordingly.

i. If, after setting theloopbacks, one or bothsites encounter trafficerrors, proceed toStep 2 in order totroubleshoot thespecific (or both) sitesaccordingly.



40







Step 2:Try to identify and replace thehardware that has failed(modem / ODU / cable /antenna). If loopback hasrevealed one problematic site,follow the instructions belowfor this specific site.Otherwise, follow instructionsfor both sites (the same holdstrue when ODU loopback isnot supported).

The following actions implyservices outage.For troubleshootersconvenience, the IF coaxialcables should be marked atboth ends with labels.

If extra links (1+1 or N+0) areavailable onsite, then:a. Swap the IF cable

connectors at modemcard side.

b. If the two modemsoperate in differentfrequencies (N+0), swapfrequencies. Otherwise,skip this step.

c. If problem persists for thesame modem, thenproblem resides inmodem itself. Replacewith spare modem(P6 procedure).



41







d. If problem passes to theother modem, thenproblem resides in ODU,IF cable or the post-ODUpath.

e. Inspect connectors at bothsides of the IF cable andfix if necessary.

f. Swap the IF cableconnectors at ODU side.

g. If the two modemsoperate in differentfrequencies (N+0configuration), swapfrequencies. Otherwise,skip this step.

h. If problem passes to theother modem, replace theIF cable.

i. If problem persists for thesame modem, thenproblem resides in ODUitself. Replace with spareODU (P8 procedure).

j. If problem persists,inspect the entire post-ODU path (inclusive ofwaveguide, coupler andantenna) and actaccordingly.

k. After resolving thehardware problem, restorethe original cableconfiguration as well asthe correct transmitfrequencies (provided thatthey have been swappedin previous step).



42







If no extra links (1+1 or N+0)are available onsite, then:a. Inspect connectors at both

sides of the IF cable andfix if necessary.

b. First, replace modem card(P6 procedure). If problempersists, replace ODUwith a spare one of thesame type (P8procedure).

c. If problem persists,inspect the entire post-ODU path (inclusive ofwaveguide, coupler andantenna) and actaccordingly.

d. If problem persists (traffichas errors), replace the IFcable.



43




3 Radiotransmissionissues.



Check whether: The antenna is in

good condition andproperly installed.

The antenna isinstalled at thecorrect height.

The position of theantenna allowsappropriateadjustments inazimuth andelevation planes,regarding thepointing toward theremote site.

The antenna pointsto the right direction(i.e. toward theremote site). Ifantennamisaligned, carryout re-alignment,as described in P5procedure.

New obstaclesappeared in theline-of-sight path,not present duringthe radio planning.



44


Causes &actions(continued)

# ProbableCauses


4 Radiointerference.



Using appropriate isolators(the T devices in schematicbelow) and a spectrumanalyzer featuring DC blockcapability, proceed as follows:

a. Mute remote ODU. (1)

b. Carry out an IF test (1).If the analyzer detectsa signal, either inter-ference is present, orthe ODU malfunctions.

c. If possible, carry out anRF test (2). If theanalyzer detects asignal, then RFinterference is present.If not, replace the ODU(P8 procedure) andrepeat previous tests. Ifproblem persists, thereis likely IF interference,which needs furtherinvestigation.

(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.


45

Ethernet Physical Layer is Down

Explanation Incident that concerns the inability of an Ethernet line (associatedwith 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 portnegotiation on both sides of the Ethernet line is incorrectlyconfigured).

OmniBAS-2W Control Card(shown: all versions)

OmniBAS-4W Control Card(shown: electr. & opt. GbE versions)

Both leds on thecorrespondingEthernet port are off.



46

Ethernet Physical Layer is Down, Continued

Causes &actions

# ProbableCauses


1 Ethernet port(on OmniBASindoor unit) isdisabled.

From within uni|MS, click therespective Ethernet port,select Configuration taband change Admin Statevalue to up:

2 Incompatiblenegotiationmode(between thedevices com-municatingover theEthernet line).

Ensure that both OmniBASand the device at the otherend of the Ethernet line havebeen configured for thesame negotiation mode(Auto or Forced).If not, change the negotiationmode in one of the devices(e.g. the OmniBAS unit).Try Auto negotiation first,then Forced negotiation withidentical settings for bothsides of the Ethernet line.

3 Link LossForwarding(LLF) isenabled andthe respectiveModem LinkFailed alarmis present.

Interruption ofassociatedservices.

Refer to chapter 2 cases:

Modem Link FailedRemote Modem LinkFailed

Alternatively, you can:

disable LLF (if notnecessary), or

change LLF settingsif found to beincorrectly configured(e.g. LLF not enabledfor both working andstandby modemcards, or for allmodem cards of theRLA group).



47

Ethernet Physical Layer is Down, Continued



4 TheOmniBASindoor unit isdaisy-chainedwith anotherone and bothunits aresynchronizedfrom a Gigabitinterface.

Change the synchronizationsource in one of the twocascaded OmniBAS units.From within uni|MS, click theOmniBAS NE, selectConfiguration tab andchange the ConfiguredClock Source value to anyavailable source, other thanthe Gb Ethernet one:

5 Impaired ordeterioratedEthernetcable.


Check cables entire run andterminations at both sides.Replace cable if necessary.


48

2. Troubleshooting of uni|MS Alarms

Introduction This chapter deals with those alarm situations that are notified tothe users of uni|MS management software. Such notificationsconstitute the basis for remotely localizing the actual cause(s) ofany incident.

For troubleshooting guidelines on a specific alarm,search for the corresponding header (on the nextpages) providing the alarms uni|MS description.For instance, to get troubleshooting information onthe uni|MS alarm described as Fan Failure, referto section Fan Failure on page 68.

In the next pages, reference lists are provided concerning thevarious uni|MS alarm groups:

Reference List of Page

Indoor Unit (NE) alarms. 50

Modem Card alarms. 50

Radio Link alarms. 51

Outdoor Unit (ODU) alarms. 52

E1 Line alarms. 53

Ethernet Line alarms. 53

NOTE The abbreviations used in table headers (on thefollowing pages) mean the following:

OB-2W ETHOmniBAS-2W Ethernet PTP modems.

OB-2W 8E1 OmniBAS-2W 8E1.OB-2W 16E1 OmniBAS-2W 16E1.OB-2W RCOmniBAS-2W Ethernet PTP-R modems.OB-4W 2GbE OmniBAS-4W 2GbE.OB-4W 2GbE/2FE OmniBAS-4W 2GbE/2FE.



49

Troubleshooting of uni|MS Alarms, Continued

General alarms

Alarm Description Severity(Default)Alarm id

(all OB models)

Lost Communication with Element Critical 3

Equipment Extracted Major 4

Part of Service has been Deactivated (1) (2) Critical 8

Part of Pending Service has been Activated (1) (2) minor 9

AEnd Down (1) (2) Critical 15

ZEnd Down (1) (2) Critical 16

Management Connection Closed Major 21

License Violation (1) Warning 30


(1) Not supported in the uniMS Node Manager.

(2) Supported in the uni|MS Service Manager.


50


Reference list of alarms for Indoor Unit (NE)

Alarm idAlarmDescription

Severity(Default) OB-2W

ETHOB-2W

8E1OB-2W

RCOB-2W16E1

OB-4W2GbE

OB-4W2GbE/2FE

Input Alarm 1 Warning 14002 24002 6002Input Alarm 2 Warning 14003 24003 6003Input Alarm 3 Warning 14004 24004 -Input Alarm 4 Warning 14005 24005 -Fan Failure Critical 14044 24044 6006Fan Extracted Major - - 6007PSU Failure Major - - 6011LowTemperature Critical 14020 24020 6020

HighTemperature Critical 14021 24021 6021

Reference list of alarms for Modem Card



ETHOB-2W

8E1OB-2W

RCOB-2W16E1

OB-4W2GbE

OB-4W2GbE/2FE

Modem Failure Major 14040 - - 6040 -Power Failure Major - 14046 24046 6102Invalid ModemInserted Major 14043 14043 24043 6043

PHYModulationFailure

Major - 16044 16044 - 16044

Clock PLLUnlocked Major - 16045 16045 - 16045

Receiver PLLUnlocked Major - 16046 16046 - 16046

TransmitterPLL Unlocked Major - 16047 16047 - 16047

Modem ChipFailure Major - 16048 16048 - 16048

Modem ChipUnlocked Major - 16049 16049 - 16049



51


Reference list of alarms for Radio Link



ETHOB-2W

8E1OB-2W

RCOB-2W16E1

OB-4W2GbE

OB-4W2GbE/2FE

Modem LinkFailed Major 14041 24041 6041

Remote ModemLink Failed Major 14042 24042 6042

RAI AlarmModem Group 1-2 Major 14024 - 24024 -

RAI AlarmModem Group 1-3 Major - 6026

RAI AlarmModem Group 2-4 Major - 6027

RAI BlockedAlarm Major 16040 - 16040 16040

ODU RSSI Alarm Major 14051 24051 6051

Rx NormalizedMSE (SNR)Alarm

Major 16041

Rx LDPCDecoders StressAlarm

Major 16042

East Port(Modem 2) ofRing Failure

Warning 16030 - 16030

West Port(Modem 1) ofRing Failure

Warning 16031 - 16031



52


Reference list of alarms for Outdoor Unit (ODU)



ETHOB-2W

8E1OB-2W

RCOB-2W16E1

OB-4W2GbE

OB-4W2GbE/2FE

ODUCommunicationFailure

Critical 14050 24050 6050

ODU Pout ALCAlarm Critical 14052 24052 6052

ODU Rx PLL LDAlarm Critical 14053 24053 6053

ODU Tx PLL LDAlarm Critical 14054 - 24054 6054

ODU TxConfiguredFrequency Out ofRange Alarm

Warning 14055 24055 6055

ODU RF PLL LDAlarm Critical - 14059 -

ODU MW PLL LDAlarm Critical 14056 - 24056 6056

ODU LoopbackPLL LD Alarm minor 14057 - 24057 6057Tx ODUConfiguredPower Out ofRange Alarm

Warning 14058 24058 6058

ODU HighTemperatureAlarm

Critical 14062 24062 6062

ODU RSSI RxUser Alarm Major 14066 24066 6066

ODU Min PifAlarm Warning 14067 - 24067 6067

ODU ModelAlarm Major 14090 - 24090 6090

ODU H/WBandwidth Alarm Warning 14091 - 24091 6091

ODU cableCalibration Alarm Critical 14092 - 24092 6092

ODU Max PifAlarm Warning 14093 - 24093 6093

ODU Low IfAlarm Critical 14094 - 24094 6094

ODU LowTemperatureAlarm

Warning 14100 24100 6100



53


Reference list of alarms for E1 Line



ETHOB-2W

8E1OB-2W

RCOB-2W16E1

OB-4W2GbE

OB-4W2GbE/2FE

E1 Line LOS Major - 14070 - 24070 6070E1 Line LOF Major - 14071 - 24071 6071E1 Line AIS Major - 14072 - 24072 6072E1 Line RAI Major - 14073 - 24073 6073E1 Line AdminDown Major - 14074 - 24074 6074

E1 is Looped Warning - 16043 - - 16043E1 Local Loop Warning - 16105 -E1 RemoteLoop Warning - 16106 -

Reference list of alarms for Ethernet Line



ETHOB-2W

8E1OB-2W

RCOB-2W16E1

OB-4W2GbE

OB-4W2GbE/2FE

SFP Tx Fault Major 14080 24080 6080SFP Rx LOS Major 14081 24081 6081Ethernet LinkDown Major 14082 24082 6082


54

General Alarms

Lost Communication with Element

Explanation Cannot remotely communicate with the OmniBAS-2W /-4Wsystem through the inband or the outband management path.

Indication Issuance of an alarm denoting the loss of managementcommunication with the OmniBAS system.



55

Lost Communication with Element, Continued

Causes &actions

# ProbableCauses

(see below)


1 Site powerfailure. Traffic loss.

2 ImpairedEthernetcabling.

OmniBAScannot bemanaged.Also, possibletraffic loss.

3 Systemreboot inprogress.

Traffic loss.

4 Hardwarehas failed.

OmniBAScannot bemanaged.Also, possibletraffic loss.

If problem is not restored in thenext few minutes (since theinstance of alarm issuance),dispatch a technician locally tocarry out the localtroubleshooting procedure asdescribed on the next pages.

5 BrokenDCNconnection.

Using the respectivemanagement system(s), checkDCN end-to-end to isolate theimpacted segment and resolveany connectivity problem.

6 WrongFirewallsetup.

OmniBASsystemcannot bemanaged.

Change the Firewall settingsaccordingly. Refer to theuni|MS Firewall SetupAdministrator Manual for thosemanagement ports to beexcluded from Firewall.



56


Local trouble-shootingprocedure

To carry out local OmniBAS troubleshooting, proceed as follows:

Step Action

1 Check for site power issues:Check whether OmniBAS is powered up and runsproperly. If yes, proceed to next step.If not, inspect the local DC power supply source.

2 Check for impaired Ethernet cables:Visually check for activity on the OmniBAS Ethernet portused for carrying management traffic.In case of no activity, inspect Ethernet cabling andreplace if found impaired. Otherwise, proceed to nextstep.

3 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 thecause of the problem), replace the OmniBAS controlcard (P7 procedure), or replace the whole OmniBASunit with a spare one (if available).

4 Check for broken DCN connectivity:Use a laptop with appropriate Ethernet and IP settingsto locally connect to an external switch and ping theuni|MS Server / Host.If necessary, change the settings of the switch or makecorrective actions to the DCN equipment.In case of no ping response, resolve the DCNconnectivity problem using the respective DCNmanagement system(s).



57


Local trouble-shootingprocedure(continued)

Step Action

5 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 theOmniBAS 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) portto be used for inband management andconfigure for untagged traffic. Set as portsdefault VLAN the value shown next to VLAN IDfield in the Inband Management Parametersgroup box:

(Right click OmniBAS NE > Configuration tab >Inband / Outband / RTC tab).

d. Connect the laptop to the configured inbandmanagement port.

e. Ping the OmniBAS node.



58


Local trouble-shootingprocedure(continued)

Step Action

6 In case of no ping response (or in case the IP settingsare unknown), connect the laptop to the AUX port onthe OmniBAS control card and find the IP address of theOmniBAS node (P3 procedure).Then, re-try to connect using this IP address.

7 If no remedies work, reset the OmniBAS node.

WARNING: Resetting OmniBAS willinterrupt all node services.

8 If problem still persists, replace the control card (P7procedure).

End of procedure.


59

Equipment Extracted

Explanation Card extracted from a specific OmniBAS-2W /-4W chassis slot forunknown reason.

Indication Issuance of an alarm denoting the card extraction.

Causes &actions

# Probable Causes Implications Suggested RecoveryProcedure

1 Card extractedintentionally (e.g.for maintenancepurposes).

Manually cease thealarm.

From the uni|MSmanagement, performthe RemoveExtracted Equipmentaction on that card.

2 Card self-extracted or hasfailed.

Serviceinterruption(in case ofunprotectedcardoperation).

Dispatch a technicianlocally to correctly re-insert and/or replacethe card. In the lattercase, refer to thecorrespondingtroubleshootingprocedure(P2/P4/P6/P7).


60

Part of Service has been Deactivated

Explanation The corresponding OmniBAS-2W /-4W service is partiallyactivated, as one or more service fragments are non-functional ornot existing any more.

This alarm is associated with the uni|MS Service Manager forOmniBAS.

Indication Issuance of an alarm denoting that the OmniBAS service ispartially (and not fully) activated.

Causes &actions

# Probable Causes Implication Suggested RecoveryProcedure

1 Service fragmenthas beendeactivated ordeleted from therespectiveOmniBAS system.

Manually activateservice:

a. Perform anActivate Serviceaction to fullyactivate service.

b. Perform a ValidateService action toverify the newservice state.

2 Communicationwith the associatedOmniBAS systemcannot beestablished.

End-to-endservice isinterrupted,as one ormoreservicefragmentsare notworking. For detailed

instructions, refer tocase:

LostCommunicationwith Element


61

Part of Pending Service has been Activated

Explanation The corresponding service fragment being in pending state (forseveral reasons) and which it is part of an OmniBAS-2W /-4Wservice has been activated. (1)

This alarm is associated with the uni|MS Service Manager forOmniBAS.

Indication Issuance of a notification denoting that the specific servicefragment has been activated.

Causes &actions

# Probable Causes Implications SuggestedRecoveryProcedure

1 Service fragment was inpending state due to thefact that uni|MS wasunable to connect to therespective OmniBASsystem.

2 Service fragment was inpending state due to thefact that the respectiveOmniBAS system hasfailed.

3 Service fragment was inpending state due toresources unavailability.

None. None.

(1) If the specific service fragment is the last pending one (within the same service path), thenservice will also be activated.


62

AEnd Down

Explanation The OmniBAS-2W /-4W end-to-end service has been reported asbeing down from the starting (AEnd) side. The traffic flow betweenthe two ends of the service path has been interrupted.This alarm is associated with the uni|MS Service Manager forOmniBAS.

Indication Issuance of an alarm denoting that the starting (AEnd) point of theend-to-end service has problem.

Causes &actions

# ProbableCauses


1 TherespectiveOmniBASsystem hasfailed.

Serviceinterrupted.

Check for active alarmsassociated with thespecific OmniBAS systemand act as instructed in thecorresponding sections ofthis document (Chapter 2).


63

ZEnd Down

Explanation The OmniBAS-2W /-4W end-to-end service has been reported asbeing down from the ending (ZEnd) side. The traffic flow betweenthe two ends of the service path has been interrupted.This alarm is associated with the uni|MS Service Manager forOmniBAS.

Indication Issuance of an alarm denoting that the ending (ZEnd) point of theend-to-end service has problem.

Causes &actions

# ProbableCauses


1 TherespectiveOmniBASsystem hasfailed.

Serviceinterrupted.

Check for active alarmsassociated with thespecific OmniBASsystem and act asinstructed in thecorresponding sectionsof this document(Chapter 2).


64

Management Connection Closed

Explanation The controller of the associated OmniBAS-2W /-4W systemcannot internally communicate with a specific supervised card.The communication between uni|MS and the OmniBAS system isnot affected by this alarm.

Indication Alarm issued by the OmniBAS control card to denote an internalcommunication problem with a specific card (e.g. Modem Card 1).

Causes &actions

# ProbableCauses


1 The concernedcard is currentlyrebooting, is notcorrectlyinserted, or ithas just failed.


a. Wait to see if alarmceases (as a resultof card reboot andre-activation).

b. Dispatch atechnician locally toinspect the cardand act asinstructed in therelevant cases ofChapter 2.


65

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 hasexceeded the license limit.

Causes &actions

# ProbableCauses


1 Number of ODUsto be managed byuni|MS is greaterthan the numberof license keys.

uni|MS willcontinue towarn for 30days beforeserver isdisabled.

Obtain extra licensekeys to be able tomanage the additionalODUs.


66

Indoor Unit Alarms

Input Alarm 1 /2 /3 /4

Explanation The corresponding device (sensor, door switch, etc.), wired ontothe AUX receptacle of the control card of the OmniBAS-2W /-4Windoor unit, has been activated or disconnected. (1)

Indication a. Listing of Relevant Alarms:Alarm id

AlarmDescription


ETHOB-2W

8E1OB-2W16E1

OB-2WRC

OB-4W2GbE

OB-4W2GbE/2FE

Input Alarm 1 Warning 14002 14002 24002 14002 6002 6002

Input Alarm 2 Warning 14003 14003 24003 14003 6003 6003

Input Alarm 3 Warning 14004 14004 24004 14004 - -Input Alarm 4 Warning 14005 14005 24005 14005 - -

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) This alarm concerns only the occupied AUX inputs.

(2) NOTE: Regarding the unoccupied AUX inputs, the corresponding led also lights up red toindicate the absence of a connected device which is normal and not an alarm.


67

Input Alarm 1 /2 /3 /4, Continued

Causes &actions

# ProbableCauses


1 Maintenanceof equipment.

None. None. Confirm the onsiteintervention (i.e. whetherit is scheduled or urgent).

2 Activation ofthe connecteddevice.

Unknown. Investigate the reasoncausing the alarm (opendoor, premises trespass,etc.).

3 Devicedisconnection.

Inability tofurther monitorthecorrespondingexternal alarm.

Call for dispatching atechnician locally toinspect.


68

Fan Failure

Explanation For OmniBAS-2W Systems:The fan subsystem of the specific modem card ismalfunctioning or it has failed.

For OmniBAS-4W Systems:The fan tray is malfunctioning or it has failed.


AlarmDescription


ETHOB-2W

8E1OB-2W16E1

OB-2WRC

OB-4W2GbE

OB-4W2GbE/2FE

Fan Failure Critical 14044 14044 24044 14044 6006 6006

Also, the respective alarm (see table below) might also be listed,denoting an excessive (i.e. unsafe) temperature as a result fromthe prolonged time the fan tray was out of operation:



ETHOB-2W

8E1OB-2W16E1

OB-2WRC

OB-4W2GbE

OB-4W2GbE/2FE

HighTemperature Critical 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 examplebelow).

For OmniBAS-4W Systems: The displayed status next to Fan Tray = Failure.



69

Fan Failure, Continued

Causes &actions

# ProbableCauses


1 Air exhaustslots areclogged.

Remove all objects impedingthe air flow.

2 Fan tray notcorrectlyinserted inthe chassisslot. (1)

Remove the fan tray fromthe chassis and re-install itcorrectly to check whether itoperates or not.

3 Fan is notpowered. (2)

Check whether the fanspower cable is correctlyplugged into thecorresponding receptacle onthe modems pcb.

4 Obstacleimpedesrotation ofinternal fins.

Carefully extract the modem(OmniBAS-2W) or the fantray (OmniBAS-4W) andcheck for obstacles impedingthe rotation of the fan.

5 Fan hasfailed.

On-site visit isneeded. Linkmaytemporarily beinterrupted.

OmniBAS-2W:Replace the modem cardwith a spare one of the sametype (P6 procedure).

OmniBAS-4W:Replace the fan tray with aspare one (P2 procedure).

Precautions This specific problem should be fixed the soonerpossible, as overheat could harm the housedelectronics with possible impact on services.

(1) Concerns OmniBAS-4W systems only.

(2) Concerns OmniBAS-2W systems only.


70

Fan Extracted

Explanation The fan tray of the OmniBAS-4W indoor unit has been extracted.


AlarmDescription


ETHOB-2W

8E1OB-2W16E1

OB-2WRC

OB-4W2GbE

OB-4W2GbE/2FE

Fan Extracted Major - - - - 6007 6007

b. Change in Elements Monitoring Status:(Click on NE > Status > Equipment tab)

The displayed status next to Fan Tray = Fan Extracted.

Causes &actions

# ProbableCauses


1 Maintenanceof equipment.

None. Confirm onsite intervention(i.e. whether visit isscheduled or urgent).


71

PSU Failure

Explanation One of the two power supply cards fitted in the OmniBAS-4Wunit is malfunctioning or has failed.


AlarmDescription


ETHOB-2W

8E1OB-2W16E1

OB-2WRC

OB-4W2GbE

OB-4W2GbE/2FE

PSU Failure Major - - - - 6011 6011

Causes &actions

# ProbableCauses


1 Powersupply cardnot correctlyinstalled.

Extract and re-insert cardcorrectly into the chassisslot.

2 Powersupply cardhas failed.

Power supplyredundancy nolongeravailable.Onsite visitshould bescheduled.

a. Remove powercable.

b. Extract the powersupply card andinstall a spare one.

c. Secure the newcard in place.

d. Re-install thepower supplycable.


72

Low Temperature

Explanation The configured threshold (see below), regarding the lowest-allowable operating temperature for the OmniBAS-2W /-4Windoor unit, has been exceeded.


AlarmDescription


ETHOB-2W

8E1OB-2W16E1

OB-2WRC

OB-4W2GbE

OB-4W2GbE/2FE

LowTemperature Critical 14020 14020 24020 14020 6020 6020

b. Change in Elements Monitoring Status:(Click on NE > Configuration tab > Threshold tab)

Causes &actions

# ProbableCauses


1 Wrong settingregarding thelow temperaturethreshold.

a. Check the lowtemperaturethreshold value.

b. If threshold ishigh, re-adjust itto -5 oC.

2 xtra-low roomtemperature.

Systemperformancemay beaffected.

Call for dispatchinga technician toinspect equipmentpremises.

3 Control cardstemperaturemonitoringsubsystem hasfailed.

Inability tofurthermonitor thesystemtemperature.

Replace the control cardwith a spare one (P7procedure).


73

High Temperature

Explanation The configured threshold (see below), regarding the highest-allowable operating temperature of the OmniBAS-2W /-4W indoorunit, has been exceeded.


AlarmDescription


ETHOB-2W

8E1OB-2W16E1

OB-2WRC

OB-4W2GbE

OB-4W2GbE/2FE

HighTemperature Critical 14021 14021 24021 14021 6021 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)



74

High Temperature, Continued

Causes &actions

# ProbableCauses


1 High roomtemperature.

Possibleequipmentdamage due tooverheat.

Call for dispatching atechnician to inspectequipment premises.

2 Hot-spot insidethe indoor unit.

Degradedsystemperformanceand/or possibleequipmentdamage due tooverheat.

a. Check thetemperatures of allcards to detect theroot cause ofoverheat.

b. Check for otheralarms that mightbe associated withoverheat (such asa fan alarm).

c. Call for dispatchinga technician onsiteto inspectequipment.

3 Wrong settingregarding thehightemperaturethreshold.

Systemperformancemay beaffected.

Check the hightemperature thresholdvalue and increase ifpossible. The newvalue should be withinthe operating rangespecified by themanufacturer.

4 Control cardstemperaturemonitoringsubsystem hasfailed.

Inability tofurther monitorthe systemtemperature.

Replace the controlcard with a spare one(P7 procedure).


75

Modem Card Alarms

Modem Failure

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

Indicationa. Listing of Relevant Alarms:

Alarm idAlarm Description Severity(Default) OB-2W

ETHOB-2W

8E1OB-2W16E1

OB-2WRC

OB-4W2GbE

OB-4W2GbE/2FE

Modem Failure Major 14040 14040 - - 6040 -

b. Change in Elements Monitoring Status:(Click on Modem > Status tab, Alarms group box)

Modem Failure alarm = True:

Causes &actions

# ProbableCauses




Protectedoperation:Link protectionno longeravailable.

a. From themanagementapplication, click onmodem, right clickand select Rebootto reset modem.

b. If problem persists,replace the modem(P6 procedure).


76

Power Failure

Explanation There is a problem with one (or more) operating DC voltagesinternally the specific modem card of the OmniBAS-2W /-4Windoor 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).


Alarm Description Severity(Default) OB-2WETH

OB-2W8E1

OB-2W16E1

OB-2WRC

OB-4W2GbE

OB-4W2GbE/2FE

Power Failure Major - - 24046 14046 6102 6102

b. Visual Indication (on the Connected Modems FrontPanel):

OmniBAS-2W:The led PWR on the concernedmodem card lights up redmeaning that there is problemwith cards power.

OmniBAS-4W:The led PWR on the concernedmodem card lights up ambermeaning that there is problemwith cards power.



77

Power Failure, Continued

Causes &actions

# ProbableCauses




Protectedoperation:Link protectionno longeravailable.

a. From themanagementapplication, click onmodem, right clickand select Rebootto reset modem.

b. If problem persists,replace the modem(P6 procedure).


78

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 a. Listing of Relevant Alarms:


ETHOB-2W

8E1OB-2W16E1

OB-2WRC

OB-4W2GbE

OB-4W2GbE/2FE

Invalid ModemInserted Major 14043 14043 24043 14043 6043 6043

Causes &actions

# ProbableCauses


1 Invalidmodem cardtype.

Extract the modem cardand replace with anotherone of the correct type.


OmniBAS linkcannot beestablished.

Replace the modem cardwith a spare one of sametype (P6 procedure).


79

PHY Modulation Failure

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

Indicationa. Listing of Relevant Alarms:


ETHOB-2W

8E1OB-2W16E1

OB-2WRC

OB-4W2GbE

OB-4W2GbE

omnibas troubleshooting 01 en

Documents

property of intracom

intracom telecom19

telecom solutions andor

radio link

respective owners

changewithout prior

industrial rights

outdoor radio odu