Harmony Hub 800, R2-6, Troubleshooting, Issue 1

Harmony Hub 800, R2.
6
Troubleshooting
Issue 1, updated in November, 2013
Notice
This document contains DragonWave proprietary information. Use, disclosure,

copying or distribution of any part of the information contained herein, beyond that
for which it was originally furnished, requires the written permission of
DragonWave Inc.
The information in this document is subject to change without notice and relates
only to the product defined in the introduction of this document. DragonWave
intends that information contained herein is, to the best of its knowledge, correct
and accurate. However, any/all liabilities associated with the use or accuracy of
the information contained herein must be defined in a separate agreement
between DragonWave and the customer/user.
Copyright © DragonWave Inc. 2013. All rights reserved.

Contents
1 Preface .................................................................................................... 3
1.1 History of changes ........................................................................................................... 3
1.2 Scope of the document .................................................................................................... 3
1.3 Intended audience ............................................................................................................ 3
1.4 Document structure .......................................................................................................... 3
1.5 Symbols and conventions ................................................................................................ 4
1.6 Documentation set ........................................................................................................... 4
2 Overview ................................................................................................. 7
2.1 Troubleshooting tool ......................................................................................................... 7
3 Alarm-triggered troubleshooting .......................................................... 9
3.1 NE alarms ...................................................................................................................... 11
3.2 P+E alarms .................................................................................................................... 14
3.3 PW alarms ...................................................................................................................... 14
3.4 Sync alarms ................................................................................................................... 15
3.5 STM alarms .................................................................................................................... 15
3.5.1 Regenerator section alarms ................................................................................................ 16
3.5.2 Multiplex section alarms ...................................................................................................... 16
3.5.3 High order path alarms ........................................................................................................ 18
3.5.4 Low order path alarms ........................................................................................................ 20

3.6 E1 alarms ........................................................................................................................22
3.7 FlexBus alarms ...............................................................................................................22
3.8 Ethernet alarms ..............................................................................................................23
4 Non-alarm-triggered troubleshooting ................................................ 25
4.1 LED indication .................................................................................................................25
4.2 Cleaning dirty fiber optic ports and connectors ...............................................................26

List of Tables
TABLE. 1 History of changes ..................................................................................................................... 3
TABLE. 2 Document structure .................................................................................................................... 3
TABLE. 3 Symbols and conventions .......................................................................................................... 4
TABLE. 4 Documentation set of product .................................................................................................... 4
TABLE. 5 NE alarms ................................................................................................................................ 11
TABLE. 6 P+E alarms .............................................................................................................................. 14
TABLE. 7 PW alarms ................................................................................................................................ 14
TABLE. 8 Sync alarms ............................................................................................................................. 15
TABLE. 9 Regenerator section alarms ..................................................................................................... 16
TABLE. 10 Multiplex section alarms ......................................................................................................... 16
TABLE. 11 High order path alarms ........................................................................................................... 18
TABLE. 12 Low order path alarms ........................................................................................................... 20
TABLE. 13 E1 alarms ............................................................................................................................... 22
TABLE. 14 FlexBus alarms ...................................................................................................................... 22
TABLE. 15 Ethernet alarms ...................................................................................................................... 23
TABLE. 16 LED indication ........................................................................................................................ 25

Preface
1 Preface
1.1 History of changes

The history of changes is shown in the following table:
TABLE 1-1. History of changes
Issue Updates Update date

1 - November 2013
1.2 Scope of the document

This document provides the warning descriptions and information to troubleshoot the Hub 800 sys-
tem.
INFO
This document only concerns Hub 800 system release 2.6 (Hub 800 R2.6 in short) without
specific statements in the context.
1.3 Intended audience

This document is prepared for the use of radio network planners and technicians who are responsi-
ble for the system management.
WARNING!
PERSONS HANDLING THIS EQUIPMENT MAY BE EXPOSED TO HAZARDS WHICH

COULD RESULT IN PHYSICAL INJURY! IT IS THEREFORE MANDATORY TO CARE-
FULLY READ AND UNDERSTAND THIS DOCUMENT.
1.4 Document structure

The document is comprised of the following chapters.
TABLE 1-2. Document structure
Chapter Title Subject

Chapter 1 Preface Provides an introduction on who and how to use this document.
Chapter 2 Overview Provides an overview of troubleshooting knowledge.
Chapter 3 Alarm-triggered trouble- Provides information about how to locate problems related to
shooting alarms.
Chapter 4 Non-alarm-triggered trou- Provides procedures to troubleshoot non-alarm-triggered faults.
bleshooting
Hub 800, R2.6, Troubleshooting, Issue 1 3

Preface
1.5 Symbols and conventions

The following symbols and mark-up conventions are used in this document:
TABLE 1-3. Symbols and conventions
Representati
on Meaning
WARNING! Indicates a hazardous situation which, if not avoided, will/could/may result in death or seri-
ous (irreversible) personal injury.
NOTICE A property damage message indicates a hazard that may result in equipment damage,
data loss, traffic interruption, or similar situations.
INFO • A note provides important information related to the topic, for example, excep-
tions to a rule or side effects that may not be obvious.
• A tip provides additional information related to the topic which is not essential
in the context, but given for convenience.
Bold All names of graphical user interface (GUI) objects, such as windows, field names, but-
tons, etc., for example:
Select the Full Screen check box and press OK.
Italic • Files, folders, and file system paths, for example:
/usr/etc/sbin/ftpd.exe
• Input to be typed in a command line or a GUI field, for example:
Enter World in the Domain field.
• Output from a command, error messages, content of a status line, etc.
• File content, such as program sources, scripts, logs and settings.
<angle brack- Placeholders, e.g., part of a file name or field value, for example:
ets> <picture name>.png.
[square A key to be pressed on a PC keyboard, for example [F11].
brackets] Keys to be pressed simultaneously are concatenated with a “+” sign, e.g.,
[Ctrl]+[Alt]+[Del].
Keys to be pressed one by one are concatenated with spaces, e.g., [Esc] [Space] [M].
> Used to concatenate a series of GUI items in order to depict a GUI path. This is an
abridged presentation of a procedure to be carried out in order to perform an action or dis-
play a window or dialog box, for example:
SURPASS TransNet window > Tools menu > 3R-Matrix Report command > 3R-Matrix
Report dialog box
x For convenience, items that are named in ascending order are sometimes listed with a
lower case x variable, in order to concisely present multiple items, for example:
I01T40G-x (is to be interpreted as I01T40G-1, I01T40G-2,...)
Screenshots of Graphical User Interfaces (GUI) are examples only to illustrate principles. This espe-
cially applies to a software version number visible in a screenshot.
1.6 Documentation set

Documents in this documentation set for this product release are listed below.
TABLE 1-4. Documentation set of product
Name No.
Harmony Hub 800, R2.6, Product Description, Issue 1 DC-PM0-HH800-CGA-EN-0001-01
Harmony Hub 800, R2.6, Accessories Product Description, Issue 1 DC-PM0-HH800-CGA-EN-0002-01
4 Hub 800, R2.6, Troubleshooting, Issue 1

Preface
TABLE 1-4. Documentation set of product
Name No.
Harmony Hub 800, R2.6, Hardware Installation Guide, Issue 1 DC-PM0-HH800-CGA-EN-0003-01
Harmony Hub 800, R2.6, Order Codes Reference, Issue 1 DC-PM0-HH800-CGA-EN-0004-01
Harmony Hub 800, R2.6, Operation and Maintenance Guide, Issue 1 DC-PM0-HH800-CGA-EN-0005-01
Harmony Hub 800, R2.6, Troubleshooting, Issue 1 DC-PM0-HH800-CGA-EN-0006-01

Preface

Overview
2 Overview
If a single alarm has been generated, go to Chapter 3, where for each alarm, a description and the
steps needed to take to turn off the alarm are provided.
To troubleshoot a case where there is no alarm go to Chapter 4 and locate the fault description that
matches the case. Instructions for further investigating the problem and the steps needed to solve
the problem are provided.
2.1 Troubleshooting tool

Loopback is used to test the network connection and diagnose the network problems. For Hub 800,
all the physical interfaces, i.e., E1, SFP, GE ports as well as the pseudowire circuits can be tested by
loopback.

Overview

Alarm-triggered troubleshooting
3 Alarm-triggered troubleshooting
The troubleshooting is performed by WebLCT with the information given in the alarm window, which
can be seen in the following steps.
1. Start WebLCT and establish a local connection. A list of alarms is shown in the bottom of
the window.
FIGURE 3-1. WebLCT main window
2. Show or hide the alarms by clicking the different color of bell symbols.

FIGURE 3-2. Alarm display
3. The detailed information of each alarm item is also shown in the right corner in Figure 3-2
after clicking the alarm entry.

3.1 NE alarms
TABLE 3-1. NE alarms
Most probable
Alarm name Severity Description cause Action
Cross First Warning Notification of first Account log is filled to Clear the account log
Threshold threshold crossing the first threshold. or disable the account
alert. Accessing NE by log feature.
WebLCT or Net-
Viewer may cause the
account log full.
Cross Second Major Notification of second Account log is filled to Clear the account log
Threshold threshold crossing the second threshold. or disable the account
alert. Accessing NE by log feature.
WebLCT or Net-
Viewer may cause the
account log full.
Function Card Critical Function card in Slot Failure during initial- Repair or replace the
Failed #n failed. ization or system peri- function card.
odic self check mainly
caused by hardware.
Failure causes
include: FPGA down-
load failure, Register
Access Failure, Hard-
ware Selfcheck Fail-
ure.
Function Card Critical Function card in Slot Function card is Check whether the
Absent #n is absent. absent. function card is pres-
ent.
Function Card Critical Function card in Slot Inserted function card Replace the mis-
Mismatch #n is mismatched. type is not consistent matching function
with the preconfigured card with a suitable
type. function card. Or reas-
sign function card as
actual card displayed
in slot status of NE
management.
Fan Fail Major Fan failure. One of the fans in Fan Replace the fan.
card fault.
Scheduled Major The failure of a sched- The scheduler did not Check the standby
Action Failure uled action to change invoke actions at load to see if it is a
Operational Status appropriate time. Or valid load.
and SchedLastOpRe- the standby load is
sult. damaged.
SNTP Server Minor Time server unavail- The link to the time Check the time server,
Unavailable able. server is not working. it will be cleared when
Or the time server time server answers.
hangs up.
SFP Absent Critical SFP #n is absent. SFP transceiver is Check whether the
absent or is not work- SFP transceiver is
ing. present. Or replace
the unworkable mod-
ule.
SFP Mismatch Critical SFP #n is mismatch- Inserted SFP trans- Replace the mis-
ing. ceiver type is not con- matched SFP module
sistent with the with a suitable SFP
preconfigured type. module.

Most probable
SFP Tempera- Major SFP temperature is Check whether tem- Make sure the tem-
ture Abnormal abnormal. perature is out of the perature is in valid
valid range in SFP range. Or replace a
module, or SFP is new SFP transceiver.
broken.
SFP Bias Cur- Major The SFP bias current The SFP is broken. Check the SFP status.
rent Abnormal is abnormal.
SFP Tx Power Major The transmitted The SFP is broken. Check the SFP status.
Abnormal power is abnormal.
SFP Rx Power Major The received power is The peer SFP is bro- Check the peer SFP
Abnormal abnormal. ken or the attenuation status.
is too large.
Service Down Major The service opera- The ports of the ser- Check the link state
tional status is down. vice may link down or for the service, or
the service abnormal. delete and recreate
the service.
Power Supply Major The status of power Short/open circuit in Check the ODU cable
to ODU Failed supply to ODU. ODU cable; wrong and ODU.
cable manufacturing;
ODU failure.
NE Overheat- Major The board tempera- Temperature of equip- Check whether the
ing ture is higher than the ment is not in normal fan is working cor-
threshold. working range. rectly.
Check whether the
temperature of equip-
ment is really out of
working range.
Check if temperature
threshold is config-
ured properly.
IDU Not in Major The IDU is not in The shroud is not con- Check the connection
Shroud shroud (only reported nected with dual-IDU. between the shroud
in idle mode). and the dual-IDU.
Communica- Major The peer IDU is not Peer IDU is not exist- Check the peer IDU.
tion Failure responding. ing; not powered up;
with Peer IDU in initial status; in
standby status; or in
idle status.
Peer IDU Fail Major The peer IDU is fail. 3 continuous I-CCM Check peer IDU sta-
message missing, will tus.
notice dual-IDU state
machine that peer
IDU is failed; or FPGA
heartbeat loss.
Not in Dual Major The IDU is not work- The IDU is working in If IDU is planned to
Mode ing in dual-IDU mode. single IDU mode, but work in single mode,
IDU is in shroud. plug out the IDU from
shroud.
If IDU is planned to
work in dual-IDU
mode, update dual-
IDU license on both
IDUs, then set work-
ing mode to dual-IDU
mode.

Most probable
Load Mis- Major SW load mismatch. Dual-IDU with differ- Check the SW loads
match ent SW loaded at on dual-IDU, make
IDUs. them consistent.
License Mis- Major The license between Dual-IDU with differ- Check the licenses on
match two IDUs does not ent license. IDUs, make them con-
match. sistent.
UNI Port Shut- Critical UNI port is shutdown There is error in Check the link status
down because there is error related NNI port. and their OAM status
in related NNI port. on related NNI port.
Wrong Load Minor SW switch is not Any component A new SW needs to
allowed. standby FW version is be downloaded.
not compatible with
the HW version, the
switch command can
not be executed.
Manual Opera- Test This alarm applies to Loopback is imple- Wait for timeout or
tion On E1/T1, STM-1/4 and mented at E1/T1 port, stop loopback manu-
Ethernet interfaces. STM-1 port or GE ally.
This alarm is used in port.
debugging in manual
operation in NE, i.e.,
loopback.
Station Alarm Intermediate The station alarm is Configuration is Check the configura-
1/2 (default) (default) configurable by dry wrong in NE or input tion or solve the prob-
contact. Both alarm polarity is same as lem from external
name and severity is configured one. equipment.
configurable to the
user. Dry contact is an
RJ45 port on main-
board and generally
connect to sensor or
other equipment, i.e.,
station overheat,
humidity, open-door
indications.

3.2 P+E alarms

TABLE 3-2. P+E alarms
Most probable
Short Circuit Major Overcurrent/undercur- Short/open circuit in Check ODU cable and
rent condition has ODU cable; wrong ODU.
been detected at the cable manufacturing;
ODU Ethernet inter- ODU failure.
face. Each ODU-
enabled GE interface
has its own Overcur-
rent/Undercurrent
alarm.
3.3 PW alarms
TABLE 3-3. PW alarms
Most probable
PW Down Major PW# Operation sta- Ethernet service car- Check Ethernet con-
tus: lower layer down rying this CESoP ser- nection, CESoP con-
or mismatch in two vice is down. MAC figuration and/or
ends. address is not network connection.
learned. UDP port
mismatches. C-VLAN
mismatches. Packet
loss.
Remote Minor PW# Remote packet “PW Down” alarm Check the CESoP
Packet Loss loss indication. reports in peer NE servcie according to
and it sets R bit to “action of PW Down”
local NE, “Remote in peer NE.
Packet Loss” alarm
reports in local NE.
CEP-LOPS Critical STM-1 #n CEP loss of Some packets from Check the connection
packet synchroniza- Ethernet port are lost. in the network, i.e.,
tion whether congestion
happens in the net-
work, radio signal
degrade, delay is too
long.
CEP-AIS Minor STM-1 #n CEP alarm LOS, LOF or MS-AIS Clean alarms at STM-
indication signal is received from STM- 1 port.
1 port in peer NE. L bit
set to STM-1 CESoP
packet when received
alarms from STM-1
port.
CEP-RDI Minor STM-1 #n CEP PW down happens in Check the configura-
remote defect indica- peer NE and CEP- tion in peer NE or
tion RDI report in local NE. CESoP packets to
peer NE.

3.4 Sync alarms

TABLE 3-4. Sync alarms
Most probable
Clock Source Major The source of transmit The clock source is Check the link status
Deteriorate clock is deteriorated. not good enough, of this clock source,
maybe big jitter, big and synchronization
wander, or unlocked status of this source’s
to its source. source.
Timing Quality Minor Sync# Timing quality The quality level Check received qual-
Level level degraded. received from ity level from
Degraded upstream synchroni- upstream synchroni-
zation network is zation network.
lower than “setting of
SSM system clock
threshold”
Timing SSM Major Sync# Timing SSM SSM message can- Check whether the
Missing missing. not be received at this switch of SSM is
timing source. opened in local and
upstream NEs. Check
the connection
between two NEs.
Timing Config- Major The master slave The master slave Make sure the master
uration Error state of the GE port is state of PHY is master slave state of PHY is
not slave when the when the GE port is slave when the GE
port configures as tim- configured as a tim- port is configured as
ing source. ing source. timing source.
Timing Inter- Minor Sync# Timing inter- A LinkState = Down Check the interface.
face Down face down. has been detected in
an Ethernet interface
selected as synchro-
nization interface;
A LOS has been
detected in the E1
interface selected as
synchronization inter-
face;
LOF and AIS also
cause this alarm.
Timing Unlock Major Sync# Timing unlock All timing sources are Check the failure
failed. cause of all timing
sources.
3.5 STM alarms

3.5.1 Regenerator section alarms
TABLE 3-5. Regenerator section alarms
Most probable
LOF Critical STM 1 #n loss of When an OOF state Check the operation
frame. persists for a defined of transmitter in both
period of time. near-end and far-end
stations.
LOS Critical STM 1 #n loss of sig- Fiber cut. Check fiber connec-
nal. Optical power is too tion.
large. If optical power is too
Attenuation is too large, add an attenua-
large. tor.
Transmitter fault in Change SFP trans-

peer NE. ceiver.
RS-TIM Critical STM 1 #n RS trace Wrong routing some- Determine in which

identifier mismatch. where in the network node(s) the line
due to: cables are wrongly
Wrong connected line connected by inter-
cables; Wrong preting the received
expected trace identi- STM-N RS trace iden-
fier filled in via the tifiers. Check the cor-
management system. rectness of expected
RS trace identifier.
3.5.2 Multiplex section alarms
TABLE 3-6. Multiplex section alarms
Most probable
MS-RDI Minor STM 1 #n Remote In the upstream sta- Check upstream
Defect Indication is tion (that reporting the external cabling and
used to return an indi- failure which detects a equipment.
cation to the transmit malfunction at the Check local transmit-
end that the received receiving side), one of ting equipment.
end has detected an the following condi-
incoming section tions is detected: Locally no actions can
defect or is receiving be taken.
MS-AIS, SPI-LOS or
MS-AIS. MS-RDI is RS-LOF, or RS-TIM. In the far-end node,
generated by inserting clear the indicated
a “110” code in posi- The far end station of receiving side fault(s).
tions 6, 7 and 8 of the the node: no signal
K2 byte before scram- received, alarm indi-
bling. cation signal received,
or excessive error
rate.
MS-AIS Minor STM 1 #n Multiplex Upstream NE has Clear upstream
Section alarm indica- inserted AIS signal. inserted AIS.
tion signal.
The MS-AIS is speci-
fied as all “1”s in the
entries STM-N,
excluding the STM-N
MSOH.

TABLE 3-6. Multiplex section alarms
Most probable
MS-EXC Major STM 1 #n Multiplex An excessive error Check the upstream
Section Excessive defect (dEXC) shall external cabling and
error. be detected if the equipment.
equivalent BER Check the threshold in
exceeds a preset the management sys-
threshold of 10-x, tem.
x=3,4,5.
MS-DEG Minor STM 1 #n Multiplex A degraded signal Check upstream
Section Degrade Sig- defect (dDEG) shall external cabling and
nal be detected if the equipment.
x=5,6,7,8,9.

3.5.3 High order path alarms
TABLE 3-7. High order path alarms
Most probable
AU-LOP Critical STM 1 #n Administra- Wrong configuration. Check the configura-
tive Unit Loss Of Received error is too tion.
Pointer large. Change the SFP
Fault in peer NE. transceiver.
Check synchroniza-
tion state.
Check configuration in
peer NE.
AU-AIS Minor STM 1 #n Administra- In one of the Check and clear
tive Unit Alarm Indica- upstream nodes a upstream NE’s SPI,
tion Signal. AU-AIS is defect is detected and RS, MS or AU-LOP
specified as all “1”s in led to the insertion of alarms.
the entire AU-4, the alarm indication Check configurations.
including the AU-4 signal.
pointer. The VC-4 Release high order
Wrong configurations. alarms in local NE.
payload signal is
replaced by the alarm LOS, LOF, MS-AIS in
indication signal. local NE.
HP-RDI Minor STM 1 #n Higher A fault exists in Check the fault in

Order Path Remote received direction of peer NE.
Defect Indication. peer NE, it sends HP-
RDI to local NE.
HP-UNEQ Critical STM 1 #n Higher VC-4 in STM-N signal Define or change the
Order Path is not in use. cross-connection at
Unequipped. the other side to be
consistent with local
side.
HP-PLM Critical STM-1 #n Higher Mapping mode of Change the mapping
Order Path Payload local and far-end mode of local node to
Mismatch. The nodes is not the be the same as far-
received payload same. Expected pay- end node.
value, used to indica- load value set via Change the expected
tion the composition management system payload value in local
of VC-4 payload, does in local node is not the node to be the same
not match the provi- same as the actual as the actual payload
sioned value. This payload value in far- value in far-end node.
alarm does not rely on end node.
port alarm monitored
mode.
HP-DEG Minor STM 1 #n Higher A degraded signal Check the upstream
Order Path Degraded defect (dDEG) shall external cabling and
Signal be detected if the equipment.
x=5,6,7,8,9.

TABLE 3-7. High order path alarms
Most probable
HP-EXC Major STM 1 #n Higher An excessive error Check the upstream
Order Path Excessive defect (dEXC) shall external cabling and
error be detected if the equipment.
equivalent BER
exceeds a preset
threshold of 10-x,
x=4,5.
HP-TIM Critical STM 1 #n J1 Trace Wrong routing some- Determine in which
Identifier Mismatch, where in the network node(s) the line
the received is not the due to: cables are wrongly
expected. Wrong connected line connected by inter-
cables; preting the received
STM-N J1 trace iden-
Wrong expected trace tifier. Check the cor-
identifier filled in via rectness of expected
the management sys- J1 trace identifier.
tem.

3.5.4 Low order path alarms
TABLE 3-8. Low order path alarms
Most probable
TU-LOP Critical STM 1 #n LP #m trib- No valid tributary unit Check the configura-
utary Unit Loss Of pointer interpretation tion.
Pointer obtained in received
signal.
TU-AIS Minor STM 1 #n LP #m trib- Wrong configuration; Check the configura-
utary Unit Alarm Indi- High order alarm tion;
cation Signal. exists. Turn off high order
alarms.
TU-LOM Critical STM 1 #n LP #m trib- Alignment to the multi Check upstream
utary unit loss of multi- frame structure of the external cabling and
frame. received VC-4 signal equipment;
is not possible. There- Check on the man-
fore VC-12 overhead agement system if
and payload data can- unit failure is reported
not be extracted. for the unit generat-
ing the multi-frame
alignment signal. In
that node, remove the
unit and replace it with
a new one.
LP-RDI Minor STM 1 #n Higher A fault exists in Check the fault in
Order Path Remote received direction of peer NE.
Defect Indication. peer NE, it sends HP-
RDI to local NE.
LP-UNEQ Major STM 1 #n Lower Lower order path in Define or change the
Order Path STM-N signal is not in cross-connection at
Unequipped. This use. the other side to be
alarm relies on the consistent with local
monitoring switch: LP side.
E1 enabled.
LP-PLM Major STM-1 #n Lower Mapping mode of Change the mapping
Order Path Payload local and far-end mode of local node to
Mismatch. The nodes is not the be the same as far-
received payload same. Expected pay- end node.
value, used to indicate load value set via Change the expected
the composition of management system payload value in local
lower order path pay- in local node is not the node to be the same
load, does not match same as the actual as the actual payload
the provisioned value. payload value in far- value in far-end node.
end node.
LP-DEG Minor STM 1 #n Lower A degraded signal Check the upstream
Order Path Degraded defect (dDEG) shall external cabling and
Signal. This alarm be detected if the equipment.
relies on the monitor- equivalent BER Check the threshold in
ing switch: LP E1 exceeds a preset the management sys-
enable. threshold of 10-x, tem.
x=5,6,7,8,9.

TABLE 3-8. Low order path alarms
Most probable
LP-EXC Major STM 1 #n Lower An excessive error Check the upstream
Order Path Excessive defect (dEXC) shall external cabling and
error. This alarm be detected if the equipment.
relies on the monitor- equivalent BER
ing switch: LP E1 exceeds a preset
enable. threshold of 10-x,
x=3,4,5.
LP-TIM Critical STM 1 #n LP #m Mismatch between Check the cross-con-
lower order trace received trace ID and nections;
identifier mismatch. expected trace ID. Check the tributary
This alarm relies on cables and tributary
the monitoring switch: units;
LP E1 enabled.
Check the expected
trace in the manage-
ment system.

3.6 E1 alarms
TABLE 3-9. E1 alarms
Most probable
AIS (Far) Warning E1/T1 #n receive all Wrong configuration Check the configura-
‘1’ signal. in local NE or in far tions in local NE or in
end NE; far end NE;
Fault in far end NE. Solve the fault in far
end NE.
AIS (Near) Warning E1/T1 #n transmit all Wrong configuration Check the configura-
‘1’ signal. in local NE. tions in local NE.
RDI (Far) Minor E1/T1 #n receive far The fault exists in Check alarms in peer
end alarm failure. peer NE, and it sends NE, e.g., LOS, LOF
RDI to local NE. and AIS.
RDI (Near) Minor E1/T1 #n transmit The fault exists in Check alarms in peer
near end alarm fail- peer NE, and it sends NE, e.g., LOS, LOF
ure. RDI to local NE. and AIS.
LOF Critical E1/T1 #n receive far Frame type between Check the configura-
end loss of frame. two E1/T1 interfaces tions between con-
is mismatching; nected E1/T1
Or 3 consecutive OOF interfaces;
is detected. Or check the synchro-
nization state.
LOS Critical E1/T1 #n near end Cable rupture; Check the connec-
Loss of Signal. The Equipment fault(s) in tions of the physical
LOS state is consid- the upstream far end layer;
ered to have occurred station of the node Check for cable
when the amplitude of that reported the breaks or dirty con-
the relevant signal alarm. nectors (measure it
has dropped below with power meter and
prescribed limits for a clear it).
prescribed period.
Looped Test The incoming E1 or E1 or T1 interface is Wait for timeout or
T1 signal is looped to looped from local stop loopback manu-
egress port and cop- manually. ally.
ied to the remote site.
3.7 FlexBus alarms

TABLE 3-10. FlexBus alarms
Most probable
FB Port # Loss Major FB port receives far FB card cannot de-lin- Check cable connec-
Of Frame end loss of frame. ear the FB frames for tion or cable length.
(LOF) a certain time.
FB Port # Loss Critical FB port near end loss Cable ruptures. Check the connec-
Of Signal of signal. tions of the physical
(LOS) layer.

3.8 Ethernet alarms

TABLE 3-11. Ethernet alarms
Most probable
Autonegotia- Critical Eth #n autonegotiat- Two Ethernet ports Check the duplex/
tion Mismatch ing mismatch. failed to negotiate the speed configuration of
master and the slave the two ports.
status.
OAM CCM Major IDU does not receive Connection problem, Check the connection,
Loss MCC loss threshold CPU did not process or whether there is
consecutive CCMs in the CCM message in many messages to
the relevant MEP; an time. process.
alarm is raised and
RDI is sent back.
Mep Radio Minor Eth #n OAM MEP The radio link of the Check the ODU con-
Link Down radio link down. ODU is down. figuration, role (active
or standby).
1731 AIS Minor Indicates MEP is in AIS condition occurs Check all link status
AIS condition. when it receives an between these two
AIS frame. MEPs.
SFP LOS Major Optical SFP # LOS The ifOperStatus = Check the optical SFP
down, and the notifi- ports.
cation sent to the
EMS is linkDown
(linkUp).
OAM Discov- Major Local NE cannot In active mode, NE Check the links
ery Fail detect the presence of doesn’t receive between two NEs and
an OAM sublayer at OAMPDU after three make sure that at
the remote NE. intervals after admin least one of them is
enabling or negotia- configured to active
tion failed after receiv- mode.
ing information
OAMPDU. Or two NE
configure to passive
mode.
OAM Loop- Warning OAM loopback is A loopback is imple- Cancel the loopback
back Enabled enabled by peer OAM menting by peer NE. in peer NE.
NE.
W/P_configu- Critical APS PDU is received There is APS PDU There is no APS PDU
ration_mis- on working path received on working received on working
match path. path.
Protec- Critical Transmitted Transmitted Reception of the first
tion_switch_in- “Requested Signal” “Requested Signal” APS frame which indi-
complete and received “Bridge and received “Bridged cates the same
Signal” do not match Signal” do not match “Bridged Signal” value
for a period of 50 ms for a period of 50 ms with the transmitted
or longer or longer. “Requested Signal”
value.
G.8031 Protec- Critical Two G.8031 Protec- Two G.8031 Protec- At least one link of
tion Group tion Group link failed tion Group link failed. G.8031 Protection
failed Group working.
B_bit_mis- Critical Transmitted and Transmitted and Once transmitted and
match received B bit do not received B bit do not received B bit match,
match match the alarm shall be
cleared.

TABLE 3-11. Ethernet alarms
Most probable
A_bit_mis- Critical Transmitted and Transmitted and Once transmitted and
match received A bit do not received A bit do not received A bit match,
match match. the alarm shall be
cleared.
D_bit_mis- Critical Transmitted and Transmitted and Once transmitted and
match received D bit do not received D bit do not received D bit match,
cleared.
R_bit_mis- Critical Transmitted and Transmitted and Once transmitted and
match received R bit do not received R bit do not received R bit match,
cleared.

Non-alarm-triggered troubleshooting
4 Non-alarm-triggered troubleshooting
This section provides procedures to troubleshoot non-alarm-triggered fault causes involving the Hub
800.
4.1 LED indication

Hub 800 has four types of LEDs on the front panel to indicate the operational status of the system
during operation.
TABLE 4-1. LED indication
Type Name Color State Function

PWR Green On Power on (either PWR A or PWR B or PWR A &
PWR B)
Mode Blue/ On Blue indicates the hybrid mode;
Green Green indicates the Packet mode.
Blink (1 The test condition is active (e.g., loopback, pro-
GHz 50%) tection forcing)
Base System
ALM Red/ On Red indicates the alarm severity is Critical or
Yellow Major
Yellow indicates Minor or Warning.
ODU Red On ODU failure in at least one of the connected
ODUs, including both on mainboard and plug-in
cards.
Link (left) Green On Connection established.
Ethernet elec-
trical interface Active Green Blink Activity indication (on Rx or Tx).
(right)
Link Green On Connection established.
SFP interface
Active (left) Green Blink Activity indication (on Rx or Tx).
STM-1 inter- Active Green On Activity indication (on Rx or Tx) and no LOS.
face (right)
LOS/LOF Red On Loss of signal or loss of frame.
FlexBus inter-
Connection Green On Connection established;
face
No alarm.
The LEDs display differently during the cold reboot and warm reboot:
• During the cold reboot, the Microprocessor will be rebooted, FPGA image will be downloaded, all
of the ASICs on the mainboard and plug-in cards will be reset, and all of the LEDs except for the
PWR will be set off;
After the reboot, all of the LEDs including the system LEDs and LEDs for each interface will flash
together at a time which lasts for 1 second. Stop flashing is regarded as the symbol of the end of
the reboot. And this can be used for LED test as well.
• During the warm reboot, the Microprocessor will be rebooted but the traffic will not be interrupted,
the system LEDs except for the PWR will be set off;
After the reboot, the system LEDs except for the PWR will flash together at a time which lasts for
1 second. Stop flashing is regarded as the end of the reboot.

Non-alarm-triggered troubleshooting
4.2 Cleaning dirty fiber optic ports and connectors

Fiber optic transceivers are sensitive optical devices and should always be handled carefully. If dirt
collects on a fiber optic lens, light may not be able to penetrate the lens, which may cause a reduc-
tion in port performance.
Warning!
The fiber optic lasers used in the device meet the regulatory requirement for casual exposure
to the eye.
As with any source of bright light, however, we recommends not to look into the laser light
source.
Steps to clean the fiber optic lens:

1. Remove any accumulated dust or debris from the port or connector by blowing across all
surfaces with a canned air duster. A compressed gas, such as Chemtronics’ Ultrajet or the
Triangle Tool Group’s Liguid-Tool Dust-A-Way, is recommended. DO NOT use commercial
compressed air or “house air” because of the risk of oil contamination.
2. Reconnect the cable to the port to check whether dusting has corrected the problem.
3. Gently wipe the ports with a lint-free, nonabrasive, nonadhesive swab. Micro swabs by Tex
wipe are recommended.
4. Gently wipe the connectors with a lint-free, nonabrasive wipe or pad. Tex wipe pads are
recommended. Avoid touching any connector surface after cleaning the connectors.

Harmony Hub 800, R2-6, Troubleshooting, Issue 1

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Harmony Hub 800, R2-6, Troubleshooting, Issue 1

Hochgeladen von

Copyright:

Verfügbare Formate

Harmony Hub 800, R2.

This document contains DragonWave proprietary information. Use, disclosure,

Copyright © DragonWave Inc. 2013. All rights reserved.

1.1 History of changes ........................................................................................................... 3

1.2 Scope of the document .................................................................................................... 3

1.3 Intended audience ............................................................................................................ 3

1.4 Document structure .......................................................................................................... 3

1.5 Symbols and conventions ................................................................................................ 4

1.6 Documentation set ........................................................................................................... 4

2.1 Troubleshooting tool ......................................................................................................... 7

3 Alarm-triggered troubleshooting .......................................................... 9

3.1 NE alarms ...................................................................................................................... 11

3.2 P+E alarms .................................................................................................................... 14

3.3 PW alarms ...................................................................................................................... 14

3.4 Sync alarms ................................................................................................................... 15

3.5 STM alarms .................................................................................................................... 15

3.5.1 Regenerator section alarms ................................................................................................ 16

3.5.2 Multiplex section alarms ...................................................................................................... 16

3.5.3 High order path alarms ........................................................................................................ 18

3.5.4 Low order path alarms ........................................................................................................ 20

3.7 FlexBus alarms ...............................................................................................................22

3.8 Ethernet alarms ..............................................................................................................23

4 Non-alarm-triggered troubleshooting ................................................ 25

4.1 LED indication .................................................................................................................25

4.2 Cleaning dirty fiber optic ports and connectors ...............................................................26

TABLE. 1 History of changes ..................................................................................................................... 3

TABLE. 2 Document structure .................................................................................................................... 3

TABLE. 3 Symbols and conventions .......................................................................................................... 4

TABLE. 4 Documentation set of product .................................................................................................... 4

TABLE. 5 NE alarms ................................................................................................................................ 11

TABLE. 6 P+E alarms .............................................................................................................................. 14

TABLE. 7 PW alarms ................................................................................................................................ 14

TABLE. 8 Sync alarms ............................................................................................................................. 15

TABLE. 9 Regenerator section alarms ..................................................................................................... 16

TABLE. 10 Multiplex section alarms ......................................................................................................... 16

TABLE. 11 High order path alarms ........................................................................................................... 18

TABLE. 12 Low order path alarms ........................................................................................................... 20

TABLE. 13 E1 alarms ............................................................................................................................... 22

TABLE. 14 FlexBus alarms ...................................................................................................................... 22

TABLE. 15 Ethernet alarms ...................................................................................................................... 23

TABLE. 16 LED indication ........................................................................................................................ 25

1.1 History of changes

TABLE 1-1. History of changes

Issue Updates Update date

1.2 Scope of the document

1.3 Intended audience

PERSONS HANDLING THIS EQUIPMENT MAY BE EXPOSED TO HAZARDS WHICH

1.4 Document structure

TABLE 1-2. Document structure

Chapter Title Subject

Hub 800, R2.6, Troubleshooting, Issue 1 3

1.5 Symbols and conventions

TABLE 1-3. Symbols and conventions

1.6 Documentation set

TABLE 1-4. Documentation set of product

4 Hub 800, R2.6, Troubleshooting, Issue 1

TABLE 1-4. Documentation set of product

Hub 800, R2.6, Troubleshooting, Issue 1 5

6 Hub 800, R2.6, Troubleshooting, Issue 1

2.1 Troubleshooting tool

Hub 800, R2.6, Troubleshooting, Issue 1 7

8 Hub 800, R2.6, Troubleshooting, Issue 1

FIGURE 3-1. WebLCT main window

Hub 800, R2.6, Troubleshooting, Issue 1 9