Fw4570 r4.2 Troubleshooting Manual

FTDG-H751-D830
FLASHWAVE 4570 RELEASE 4.2

TROUBLESHOOTING MANUAL (TSMN)
ISSUE 1, JANUARY 2011
FUJITSU LIMITED
Before You Begin
Proprietary Rights Notice
All product or service names mentioned in this document are trademarks or registered trademarks of their
respective companies.
This document and its contents are provided by FUJITSU Limited (FUJITSU) for guidance purposes only. This document is
provided as is with no warranties or representations whatsoever, either express or implied, including without limitation the
implied warranties of merchantability and fitness for purpose. FUJITSU does not warrant or represent that the contents of
this document are error free. Furthermore, the contents of this document are subject to update and change at any time
without notice by FUJITSU, since FUJITSU reserves the right, without notice, to make changes in equipment design or
components as progress in engineering methods may warrant. No part of the contents of this document may be copied,
modified, or otherwise reproduced without the express written consent of FUJITSU.
Unpublished work and only distributed under restriction.

Copyright FUJITSU LIMITED. All Rights Reserved.
FLASHWAVE 4570 Release 4.2 FTDG-H751-D830

FUJITSU and FUJITSU Customer Use Only
Troubleshooting Manual Issue 1, January 2011
Before You Begin
BEFORE YOU BEGIN

Read through this manual set carefully and familiarize yourself with the FLASHWAVE
4570 equipment before configuring, installing, turning up, performing operation and
maintenance of, and troubleshooting the equipment.
Keep the manual set at hand so that you can refer to it at any time.
Observe the notices and instructions provided in this manual set for your proper and
safety installation, use and maintenance of the equipment.
FTDG-H751-D830 FLASHWAVE 4570 Release 4.2

FUJITSU and FUJITSU Customer Use Only i
Issue 1, January 2011 Troubleshooting Manual
Before You Begin
! Important Notice on Product Safety
Elevated voltages are inevitably present at specific points in this electrical equipment.
Some of the parts may also have elevated operating temperatures. Systems with
forced ventilation have rotating items.
Non-observance of these conditions and the safety instructions can result in personal
injury or in property damage.
The system complies with the standard EN 60950-1 / IEC 60950-1. All equipment
connected has to comply with the applicable safety standards.
Mount the systems in areas with restricted access only. Only trained and qualified
personnel may install, operate, and maintain the systems.

ii FUJITSU and FUJITSU Customer Use Only
Contents
Contents
CHAPTER 1 Preface .......................................................................................................... 1-1

1.1 Intended Audience .................................................................................................. 1-2
1.2 Structure of This Document .................................................................................... 1-2
1.3 Symbols and Conventions ...................................................................................... 1-2
1.3.1 Symbols Used ........................................................................................................ 1-3
1.3.2 Conventions Used .................................................................................................. 1-3
1.4 History of Changes ................................................................................................. 1-4
CHAPTER 2 Alarm Lists ..................................................................................................... 2-1
2.1 Equipment Alarms .................................................................................................. 2-2
2.2 Communication Alarms ........................................................................................... 2-3
2.3 Environmental Alarms............................................................................................. 2-5
2.4 Quality of Service Alarms........................................................................................ 2-5
2.5 Security Alarms ...................................................................................................... 2-7
CHAPTER 3 Troubleshooting ............................................................................................. 3-1
3.1 Equipment Alarms .................................................................................................. 3-2
3.1.1 Communication_Fail ............................................................................................... 3-2
3.1.2 Equipment_Overheating ......................................................................................... 3-2
3.1.3 Fan_Failure ............................................................................................................ 3-3
3.1.4 Loss_of_Power_Input ............................................................................................. 3-3
3.1.5 Low_Board_Flash_Card_Capacity .......................................................................... 3-4
3.1.6 Low_Order_Capacity_Mismatch ............................................................................. 3-4
3.1.7 No_Free_Low_Order_Capacity............................................................................... 3-4
3.1.8 NO.XFan_Failure.................................................................................................... 3-5
3.1.9 OA-Power_Failure .................................................................................................. 3-5
3.1.10 OA-Pump_Bias_out_of_Range ............................................................................... 3-5
3.1.11 OA-Temperature_out_of_Range ............................................................................. 3-5
3.1.12 PLL_Unlock ............................................................................................................ 3-6
3.1.13 Power_Failure ........................................................................................................ 3-6
3.1.14 SC_CF_Module_Absent ......................................................................................... 3-6
3.1.15 SC_CF_Module_Failure ......................................................................................... 3-7
3.1.16 SC_SW_Version_Mismatch .................................................................................... 3-7
3.1.17 SFP_Absent ........................................................................................................... 3-7
3.1.18 SFP_Failure ........................................................................................................... 3-8
3.1.19 SFP_Mismatch ....................................................................................................... 3-8
3.1.20 SPI-Temperature_out_of_Range ............................................................................ 3-8
3.1.21 Unit_Failure ............................................................................................................ 3-9
3.1.22 Unit_Removal ......................................................................................................... 3-9
3.1.23 Unit_Type_Mismatch .............................................................................................. 3-9
3.1.24 VCXO_Failure ........................................................................................................ 3-9
3.2 Communication Alarms ......................................................................................... 3-10
3.2.1 AU_AIS ................................................................................................................ 3-10
3.2.2 AU_LOP ............................................................................................................... 3-10
3.2.3 Embedded_DCC_Channel (n)_Failure .................................................................. 3-10
3.2.4 HCOC27-DCC_Connection_Failure ...................................................................... 3-11
3.2.5 HCOC9-DCC_Connection_Failure ........................................................................ 3-11
3.2.6 HP-DEG ............................................................................................................... 3-11
3.2.7 HP-EXC................................................................................................................ 3-12
3.2.8 HP-GFP_Customer_Signal_Failure ...................................................................... 3-12

FUJITSU and FUJITSU Customer Use Only iii
Contents
3.2.9 HP-GFP_Loss_of_Frame_Delineation .................................................................. 3-12

3.2.10 HP-PLM................................................................................................................ 3-12
3.2.11 HP-RDI ................................................................................................................. 3-13
3.2.12 HP-TIM ................................................................................................................. 3-13
3.2.13 HP-UNEQ ............................................................................................................. 3-13
3.2.14 HP-Virtual_Concatenation_LOA............................................................................ 3-14
3.2.15 HP-Virtual_Concatenation_LOM ........................................................................... 3-14
3.2.16 HP-Virtual_Concatenation_PLCR ......................................................................... 3-14
3.2.17 HP-Virtual_Concatenation_PLCT .......................................................................... 3-15
3.2.18 HP-Virtual_Concatenation_TLCR.......................................................................... 3-15
3.2.19 Link_Failure .......................................................................................................... 3-16
3.2.20 Loss_of_Timing_Input........................................................................................... 3-16
3.2.21 Loss_of_Timing_Output ........................................................................................ 3-17
3.2.22 LP-DEG ................................................................................................................ 3-17
3.2.23 LP-EXC ................................................................................................................ 3-18
3.2.24 LP-GFP_Customer_Signal_Failure ....................................................................... 3-18
3.2.25 LP-GFP_Loss_of_Frame_Delineation ................................................................... 3-18
3.2.26 LP-PLM ................................................................................................................ 3-19
3.2.27 LP-RDI ................................................................................................................. 3-19
3.2.28 LP-RFI .................................................................................................................. 3-19
3.2.29 LP-TIM ................................................................................................................. 3-20
3.2.30 LP-UNEQ ............................................................................................................. 3-20
3.2.31 LP-Virtual_Concatenation_LOA ............................................................................ 3-21
3.2.32 LP-Virtual_Concatenation_LOM............................................................................ 3-21
3.2.33 LP-Virtual_Concatenation_TLCR .......................................................................... 3-21
3.2.34 MS_AIS ................................................................................................................ 3-22
3.2.35 MS-DCC_Connection_Failure ............................................................................... 3-22
3.2.36 MS_DEG .............................................................................................................. 3-23
3.2.37 MS_EXC .............................................................................................................. 3-23
3.2.38 MS-K1/K2_Mismatch ............................................................................................ 3-23
3.2.39 MS_RDI................................................................................................................ 3-24
3.2.40 OA-Gain_High ...................................................................................................... 3-24
3.2.41 OA-Input_LOS ...................................................................................................... 3-25
3.2.42 OA-Output_LOS ................................................................................................... 3-25
3.2.43 OA-Output_Power_High ....................................................................................... 3-26
3.2.44 ODU_AIS ............................................................................................................. 3-26
3.2.45 ODU_BDI ............................................................................................................. 3-26
3.2.46 ODU_DEG............................................................................................................ 3-27
3.2.47 ODU_LCK ............................................................................................................ 3-27
3.2.48 ODU_LOFLOM ..................................................................................................... 3-27
3.2.49 ODU_MSIM .......................................................................................................... 3-28
3.2.50 ODU_OCI ............................................................................................................. 3-28
3.2.51 ODU_PLM ............................................................................................................ 3-28
3.2.52 ODU_TIM ............................................................................................................. 3-29
3.2.53 OTU-BDI .............................................................................................................. 3-29
3.2.54 OTU-DEG ............................................................................................................. 3-29
3.2.55 OTU-LOF ............................................................................................................. 3-30
3.2.56 OTU-LOM............................................................................................................. 3-30
3.2.57 OTU-TIM .............................................................................................................. 3-30
3.2.58 PPI-AIS ................................................................................................................ 3-31
3.2.59 PPI-LOF ............................................................................................................... 3-31
3.2.60 PPI-LOM .............................................................................................................. 3-31
3.2.61 PPI-LOS ............................................................................................................... 3-32
3.2.62 PPI-RDI ................................................................................................................ 3-32
3.2.63 RPR-Exceed_Max_Stations.................................................................................. 3-33
3.2.64 RPR-Link_Failure_East ........................................................................................ 3-33
3.2.65 RPR-Link_Failure_West ....................................................................................... 3-33

iv FUJITSU and FUJITSU Customer Use Only
Contents
3.2.66 RPR-Miscabling_East ........................................................................................... 3-34

3.2.67 RPR-Miscabling_West .......................................................................................... 3-34
3.2.68 RPR-Protection_Misconfig .................................................................................... 3-34
3.2.69 RPR-Ringlet0_ReservedA0_Exceeding ................................................................ 3-35
3.2.70 RPR-Ringlet1_ReservedA0_Exceeding ................................................................ 3-35
3.2.71 RPR-Topology_Inconsistent ................................................................................. 3-35
3.2.72 RPR-Topology_Instability...................................................................................... 3-35
3.2.73 RS-DCC_Connection_Failure ............................................................................... 3-36
3.2.74 RS-DEG ............................................................................................................... 3-36
3.2.75 RS-EXC................................................................................................................ 3-37
3.2.76 RS-LOF ................................................................................................................ 3-37
3.2.77 RS-TIM ................................................................................................................. 3-38
3.2.78 Signal_Error_Fail .................................................................................................. 3-38
3.2.79 SPI-LOS ............................................................................................................... 3-38
3.2.80 Synchronization_Signal_Message_Mismatch........................................................ 3-39
3.2.81 System_Clock_Holdover_Longer .......................................................................... 3-39
3.2.82 System_Clock_Unlocked ...................................................................................... 3-40
3.2.83 Timing_Reference_Degrade ................................................................................. 3-40
3.2.84 Timing_Reference_Failure .................................................................................... 3-40
3.2.85 TU-AIS ................................................................................................................. 3-41
3.2.86 TU-LOM ............................................................................................................... 3-41
3.2.87 TU-LOP ................................................................................................................ 3-42
3.3 Environmental Alarms........................................................................................... 3-42
3.3.1 ENV_MDI<n> ....................................................................................................... 3-42
3.4 Quality of Service Alarms...................................................................................... 3-42
3.4.1 AU-PJCN_TCA_15m/24h ..................................................................................... 3-42
3.4.2 AU-PJCP_TCA_15m/24h...................................................................................... 3-43
3.4.3 Excessive_ Bad_Bytes_Received_TCA_1s (LAN or WAN) ................................... 3-43
3.4.4 Excessive_ Bad_Packets_Received_TCA_1s (LAN or WAN)................................ 3-44
3.4.5 E1-Negative_Bit-slip_TCA_15m/24h ..................................................................... 3-44
3.4.6 E1-Positive_Bit-slip_TCA_15m/24h ...................................................................... 3-44
3.4.7 HP-FE_BBE_TCA_15m/24h ................................................................................. 3-45
3.4.8 HP-FE_ES_TCA_15m/24h ................................................................................... 3-45
3.4.9 HP-FE_SES_TCA_15m/24h ................................................................................. 3-46
3.4.10 HP-FE_UAS_TCA_15m/24h ................................................................................. 3-46
3.4.11 HP-NE_BBE_TCA_15m/24h ................................................................................. 3-46
3.4.12 HP-NE_ES_TCA_15m/24h ................................................................................... 3-47
3.4.13 HP-NE_SES_TCA_15m/24h ................................................................................. 3-47
3.4.14 HP-NE_UAS_TCA_15m/24h................................................................................. 3-48
3.4.15 LP-FE_BBE_TCA_15m/24h.................................................................................. 3-48
3.4.16 LP-FE_SES_TCA_15m/24h.................................................................................. 3-48
3.4.17 LP-FE_UAS_TCA_15m/24h ................................................................................. 3-49
3.4.18 LP-NE_BBE_TCA_15m/24h ................................................................................. 3-49
3.4.19 LP-NE_ES_TCA_15m/24h.................................................................................... 3-50
3.4.20 LP-NE_SES_TCA_15m/24h ................................................................................. 3-50
3.4.21 LP-NE_UAS_TCA_15m/24h ................................................................................. 3-50
3.4.22 MS-FE_BBE_TCA_15m/24h ................................................................................. 3-51
3.4.23 MS-FE_ES_TCA_15m/24h ................................................................................... 3-51
3.4.24 MS-FE_SES_TCA_15m/24h ................................................................................. 3-51
3.4.25 MS-FE_UAS_TCA_15m/24h................................................................................. 3-52
3.4.26 MS-NE_BBE_TCA_15m/24h ................................................................................ 3-52
3.4.27 MS-NE_ES_TCA_15m/24h................................................................................... 3-53
3.4.28 MS-NE_SES_TCA_15m/24h ................................................................................ 3-53
3.4.29 MS-NE_UAS_TCA_15m/24h ................................................................................ 3-53
3.4.30 PPI-FE_BBE_TCA_15m/24h ................................................................................ 3-54
3.4.31 PPI-FE_ES_TCA_15m/24h................................................................................... 3-54
3.4.32 PPI-FE_SES_TCA_15m/24h ................................................................................ 3-54

FUJITSU and FUJITSU Customer Use Only v
Contents
3.4.33 PPI-FE_UAS_TCA_15m/24h ................................................................................ 3-55

3.4.34 PPI-NE_ES_TCA_15m/24h .................................................................................. 3-55
3.4.35 PPI-NE_SES_TCA_15m/24h ................................................................................ 3-55
3.4.36 PPI-NE_UAS_TCA_15m/24h ................................................................................ 3-56
3.4.37 RS-BBE_TCA_15m/24h ....................................................................................... 3-56
3.4.38 RS-ES_TCA_15m/24h .......................................................................................... 3-56
3.4.39 RS-SES_TCA_15m/24h ....................................................................................... 3-57
3.4.40 RS-UAS_TCA_15m/24h ....................................................................................... 3-57
3.5 Security Alarms .................................................................................................... 3-58
3.5.1 Account_Expired_Disabled ................................................................................... 3-58
3.5.2 Log_Is_Full ........................................................................................................... 3-58
3.5.3 Log_Occupancy_Threshold_Reached .................................................................. 3-58
3.5.4 Unauthorized_Access_Attempt ............................................................................. 3-59
3.5.5 Unsuccessful_Logins_Exceeded........................................................................... 3-59
CHAPTER 4 Common Incorrect Ethernet Configuration Cases ........................................... 4-1
4.1 Ethernet Traffic Frame Loss .................................................................................... 4-2
4.2 Ethernet Traffic Block.............................................................................................. 4-3
4.3 Prevention of Loobback on Data Card..................................................................... 4-4
4.4 Pause Frame for Layer 2 Card ................................................................................ 4-5
4.5 Default VLAN ID Warning for Layer 2 Card ............................................................. 4-5
4.6 VCG Bandwidth Configuration Reminder for Ethernet Cards ................................... 4-6
CHAPTER 5 Card Replacement ......................................................................................... 5-1
5.1 General Guideline for Card Replacement ................................................................ 5-2
5.2 Replacing SC Card ................................................................................................. 5-2
5.2.1 MIB Preparation before Replacement ..................................................................... 5-3
5.2.2 Switching SC before Replacement (for Redundant SC System) .............................. 5-4
5.2.3 SC Card Failure ...................................................................................................... 5-5
5.2.4 CF Card Failure ...................................................................................................... 5-6
5.2.5 Both SC and CF Cards Fail..................................................................................... 5-6
5.2.6 Downloading Boot Image ........................................................................................ 5-7
5.2.7 Downloading Software Load ................................................................................... 5-8
5.2.8 Downloading MIB.................................................................................................... 5-9
5.3 Troubleshooting SC 1+1 Common Problems......................................................... 5-11
5.3.1 Both ACT LEDs are Off......................................................................................... 5-11
5.3.2 Manual Switch Failure........................................................................................... 5-11
5.3.3 Automatic Switch Failure....................................................................................... 5-12
5.4 Replacing CC Card ............................................................................................... 5-13
5.5 Replacing Fan Unit ............................................................................................... 5-13
5.6 Replacing Filter Unit ............................................................................................. 5-14
CHAPTER 6 MIB Switching ................................................................................................ 6-1
6.1 Switching MIBs with Different Configuration ............................................................ 6-2
6.2 Switching MIBs with Same Configuration ................................................................ 6-3
6.3 Switching MIBs in Redundant SC System ............................................................... 6-3
6.4 MIB Restoration ...................................................................................................... 6-3
6.4.1 Restoring MIB Files ................................................................................................ 6-3
6.4.2 Problems Caused by Traffic Status ......................................................................... 6-4
CHAPTER 7 Abbreviations ................................................................................................. 7-1

vi FUJITSU and FUJITSU Customer Use Only
List of Figures
List of Illustrations
Figure 4-1 Topology of Traffic Frame Loss Scenario ........................................................... 4-2
Figure 4-2 Topology of Traffic Block Scenario ..................................................................... 4-3
Figure 4-3 Loop on WAN Port ............................................................................................. 4-5
Figure 5-1 SC 1+1 Working Status .................................................................................... 5-11

FUJITSU and FUJITSU Customer Use Only vii
List of Tables
List of Tables
Table 1-1 List of Used Conventions..................................................................................... 1-3
Table 1-2 History of Changes.............................................................................................. 1-4
Table 2-1 Equipment Alarms ............................................................................................... 2-2
Table 2-2 Communication Alarms ....................................................................................... 2-5
Table 2-3 Environmental Alarms ......................................................................................... 2-5
Table 2-4 Quality of Service Alarms .................................................................................... 2-7
Table 2-5 Security Alarms ................................................................................................... 2-7
Table 4-1 Incorrect Configuration of Traffic Block Scenario.................................................. 4-3
Table 5-1 Switch Priority of SC 1+1................................................................................... 5-12

viii FUJITSU and FUJITSU Customer Use Only
CHAPTER 1
Preface
CHAPTER 1
Preface

FUJITSU and FUJITSU Customer Use Only 1-1
CHAPTER 1
Preface
This Troubleshooting Manual describes fault-clearing procedures to be performed in reaction

to alarm events that may occur in the FLASHWAVE 4570 system.
1.1 Intended Audience
This document is intended for anyone tasked with clearing fault conditions to restore normal
system operation. Personnel performing these procedures must have general experience
with Synchronous Digital Hierarchy (SDH) transport networks as well as specific experience
with Fujitsu FLASHWAVE 4570 hardware components and network management software.
Personnel must also comply with all relevant safety practices whenever working with
FLASHWAVE 4570 equipment.
1.2 Structure of This Document
Alarm lists
When a fault condition occurs, the relevant alarm notification will be generated and displayed
on craft terminal screens. All FLASHWAVE 4570 alarms are listed in the Alarm lists in
Chapter 2. The alarm lists are divided into separate tables that match the fault categories as
presented on craft terminal screens. These categories are as follows:
Equipment alarms
Communication alarms
Environment alarms
Quality of Service (QoS) alarms
Security alarms
Troubleshooting
For each entry in the Alarm lists, specific fault-clearing procedures are contained in Chapter
3, Troubleshooting.
Described Features
Some features described in this document may not be available. To identify the features
i released for your project, please refer to the Release Note delivered together with the
product.
1.3 Symbols and Conventions
The following symbols and conventions are used in this document:

1-2 FUJITSU and FUJITSU Customer Use Only
CHAPTER 1
Preface
1.3.1 Symbols Used
Danger This symbol identifies notes which, if ignored, can result in bodily harm.
!
Warning This symbol identifies notes which, if ignored, can result in damage to the equipment.
!
Caution This symbol identifies notes which, if ignored, can result in service interruption.
!
i This symbol stands for an important note to be paid extra attention to, or additional
information which extends beyond the immediate context.
This symbol stands for a cross reference to other chapters in this manual or reference to
other manuals.
Help This symbol stands for a reference to the online help system of the FLEXR L local craft
terminal or FLEXR C subnetwork management system software.
1.3.2 Conventions Used
Representation Meaning
Inverted commas Window or wizard titles are represented in inverted commas.
Example: Open the Help and Support Center window. The New
Connection wizard is displayed.
Bold Any field or text in the GUI is represented in bold type. Example:
Click Shutdown and then click OK to turn off the computer.
Italic Variables and file extensions are represented in italic.
Example: Enter 192.168.0.1 in the IP address field. Click OK to
produce a .pdf rendition.
Courier Commands, screen output, file names and paths are represented
in courier.
Example: # ping -t 192.168.0.1
<Angle brackets> Used for keyboard actions or place holders for concrete names or
values are represented in <angle brackets>. If used for a filename
the courier font must be used also.
Example: The naming convention for the log files is
<NEname>.txt, where <NEName> is the name of the NE sending
the messages. Press <CTRL>+<ALT><DEL> to open the task
manager.
Table 1-1 List of Used Conventions

CHAPTER 1
Preface
1.4 History of Changes
Issue Issue date

1 January 2011 Initial version
Table 1-2 History of Changes

CHAPTER 2
Alarm Lists
CHAPTER 2
Alarm Lists

CHAPTER 2
Alarm Lists
FLASHWAVE 4570 alarms are divided into the following categories:

Equipment alarms: originate from specific hardware elements (e.g., traffic card, controller
card, shelf, etc.)
Communication alarms: originate from termination points which represent a particular
function of the network
Environmental alarms: originate from telemetry sensors that monitor conditions/ events
external to the NE
Quality of Service alarms: originate from termination points where performance
measurement and threshold supervision is enabled
Security alarms: alarms relevant to the system authentication and authorization
2.1 Equipment Alarms
Table 2-1 lists FLASHWAVE 4570 equipment alarms.
Alarm Name Alarm Message Text

Communication_Fail Communication failure
Equipment_OverHeating Equipment overheating
Fan_Failure Fan failure
Loss_of_Power_Input Loss of power input
Low_Board_Flash_Card_Capacity Low board flash card capacity
Low_Order_Capacity_Mismatch Low order capacity mismatch
No_Free_Low_Order_Capacity No free low order capacity
NO.XFan_Failure No. x fan failure
OA-Power_Failure Optical Amplifier (OA) power failure
OA-Pump_Bias_out_of_Range OA pump bias out of range
OA-Temperature_out_of_Range OA temperature out of range
PLL_Unlock Phase Lock Loop (PLL) unlock
Power_Failure Power failure
SC_CF_Module_Absent SC Compact Flash (CF) card absent
SC_CF_Module_Failure SC CF module failure
SC_SW_Version_Mismatch SC software version mismatch
SFP_Absent SFP absent
SFP_Failure SFP failure
SFP_Mismatch SFP mismatch
SPI-Temperature_out_of_Range Synchronous Physical Interface (SPI) laser
temperature out of range
Unit_Failure Unit failure
Unit_Removal Unit removal
Unit_Type_Mismatch Unit type mismatch
VCXO_Failure VCXO Failure
Table 2-1 Equipment Alarms

CHAPTER 2
Alarm Lists
2.2 Communication Alarms
Table 2-2 lists FLASHWAVE 4570 communication alarms..

AU_AIS Administrative Unit (AU) Alarm Indication
Signal (AIS)
AU_LOP AU Loss Of Pointer (LOP)
Embedded DCC channel (n) failure Embedded DCC Channel 1 or 2 failure
HCOC27-DCC_Connection_Failure High Capacity Overhead Channel (HCOC) 27
Data Communication Channel (DCC)
connection failure
HCOC9-DCC_Connection_Failure HCOC 9 DCC connection failure
HP-DEG High order Path (HP) signal DEGraded (DEG)
HP-EXC HP EXCessive (EXC) error
HP-GFP_Customer_Signal_Failure HP Generic Framing Procedure (GFP)
customer signal failure
HP-GFP_Loss_of_Frame_Delineation HP GFP loss of frame delineation
HP-PLM HP PayLoad Mismatch (PLM)
HP-RDI HP Remote Defect Indication (RDI)
HP-TIM HP Trace Identifier Mismatch (TIM)
HP-UNEQ HP UNEQuipped (UNEQ)
HP-Virtual_Concatenation_LOA HP virtual concatenation Loss Of Alignment
(LOA)
HP-Virtual_Concatenation_LOM HP virtual concatenation Loss Of Multiframe
(LOM)
HP-Virtual_Concatenation_PLCR HP virtual concatenation Partial Loss of
Capacity of Reception (PLCR)
HP-Virtual_Concatenation_PLCT HP virtual concatenation Partial Loss of
Capacity of Transmission (PLCT)
HP-Virtual_Concatenation_TLCR HP virtual concatenation Total Loss of
Capacity Reception (TLCR)
Link_Failure Link failure
Loss_of_Optical_Input Loss of optical inpu
Loss_of_Timing_Input Loss of timing input
Loss_of_Timing_Output Loss of timing output
LP-DEG Low order Path (LP) signal DEG
LP-EXC LP EXC error
LP-GFP_Customer_Signal_Failure LP GFP customer signal failure
LP-GFP_Loss_of_Frame_Delineation LP GFP loss of frame delineation
LP-PLM LP PLM
LP-RDI LP RDI
LP-RFI LP Remote Failure Indication (RFI)

CHAPTER 2
Alarm Lists

LP-TIM LP TIM
LP-UNEQ LP UNEQ
LP-Virtual_Concatenation_LOA LP virtual concatenation LOA
LP-Virtual_Concatenation_LOM LP virtual concatenation LOM
LP-Virtual_Concatenation_TLCR LP virtual concatenation TLCR
MS_AIS Multiplex Section (MS) AIS
MS-DCC_Connection_Failure MS DCC connection failure
MS_DEG MS signal DEG
MS_EXC MS EXC
MS-K1/K2_Mismatch K1/K2 mismatch
MS_RDI MS RDI
OA-Gain_High OA gain high
OA-Input_LOS OA input Loss Of Signal (LOS)
OA-Output_LOS OA output LOS
OA-Output_Power_High OA output power high
ODU_AIS ODU alarm indication signal (AIS)
ODU_BDI ODU backward defect identifier (BDI)
ODU_DEG ODU degrade signal
ODU_LOFLOM ODU LOF and LOM signal
ODU_LCK ODU locked
ODU_MSIM ODU multiplex structure identifier mismatch
(MSIM)
ODU_OCI ODU open connection indication (OCI)
ODU_PLM ODU payload mismatch (PLM)
ODU_TIM ODU section trail trace identifier mismatch
OTU-BDI OTU section backward defect indication (BDI)
OTU-DEG OTU section degrade signal
OTU-LOF OTU section loss of frame (LOF)
OTU-LOM OTU section loss of multi-frame (LOM)
OTU-TIM OTU section trail trace identifier mismatch
(TIM)
PPI-AIS Plesiochronous Digital Hierarchy (PDH)
Physical Interface (PPI) AIS
PPI-LOF PPI LOF
PPI-LOM PPI LOM
PPI-LOS PPI LOS
PPI-RDI PPI RDI
RPR-Exceed_Max_Stations Resilient Packet Ring (RPR) exceed
maximum stations
RPR-Link_Failure_East RPR link failure east

CHAPTER 2
Alarm Lists

RPR-Link_Failure_West RPR link failure west
RPR-Miscabling_East RPR miscabling east
RPR-Miscabling_West RPR miscabling west
RPR-Protection_Misconfig RPR protection misconfiguration
RPR-Ringlet0_ReservedA0_Exceeding RPR ringlet 0 reserved A0 exceeding
RPR-Ringlet1_ReservedA0_Exceeding RPR ringlet 1 reserved A0 exceeding
RPR-Topology_Inconsistent RPR topology inconsistent
RPR-Topology_Instability RPR topology instability
RS-DCC_Connection_Failure Regeneration Section (RS) DCC connection
failure
RS_DEG RS signal DEG
RS_EXC RS EXC
RS_LOF RS Loss Of Frame (LOF)
RS_TIM RS TIM
Signal_Error_Fail Signal error failure
SPI_LOS SPI LOS
Synchronization_Signal_Message_Mis Synchronization Signal Message (SSM)
match mismatch
System_Clock_Holdover_Longer System clock holdover longer
System_Clock_Unlocked System clock unlocked
Timing_Reference_Degrade Timing reference degraded
Timing_Reference_Failure Timing reference failure
TU-AIS Tributary Unit (TU) AIS
TU-LOM TU LOM
TU-LOP TU LOP
Table 2-2 Communication Alarms
2.3 Environmental Alarms
Table 2-3 lists FLASHWAVE 4570 environmental alarms.

ENV_MDI<n> ENVironment (ENV) Miscellaneous Discrete
Input (MDI) 1 ~ 8
Table 2-3 Environmental Alarms
2.4 Quality of Service Alarms
Table 2-4 lists FLASHWAVE 4570 QoS alarms.

CHAPTER 2
Alarm Lists

AU-PJCN_TCA_15m/24h AU Pointer Justification Count Negative
(PJCN) Threshold Crossed Alarm (TCA)
15-minute or 24-hour
AU-PJCP_TCA_15m/24h AU Pointer Justification Count Positive
(PJCP) Threshold Crossed Alarm (TCA)
Excessive_Bad_Bytes_Received_TCA_1 Excessive bad bytes received TCA 1 second
s (LAN or WAN) (LAN or WAN)
Excessive_Bad_Packet_Received_TCA_ Excessive bad packet received TCA 1
1s (LAN or WAN) second (LAN or WAN)
E1-Negative_Bit-slip_TCA_15m/24h E1 negative bit-slip Threshold Crossed Alarm
(TCA) 15-minute or 24-hour
E1-Positive_Bit-slip_TCA_15m/24h E1 positive bit-slip TCA 24 15-minute or 24-
hour
HP-FE_BBE_TCA_15m/24h HP Far-End (FE) Background Block Error
(BBE) TCA 15-minute or 24-hour
HP-FE_ES_TCA_15m/24h HP FE Errored Second (ES) TCA 15-minute
or 24-hour
HP-FE_SES_TCA_15m/24h HP FE Severely Errored Second (SES) TCA
HP-FE_UAS_TCA_15m/24h HP FE Unavailable Second (UAS) TCA 15-
minute or 24-hour
HP-NE_BBE_TCA_15m/24h HP NE BBE TCA 15-minute or 24-hour
HP-NE_ES_TCA_15m/24h HP NE ES TCA 15-minute or 24-hour
HP-NE_SES_TCA_15m/24h HP NE SES TCA 15-minute or 24-hour
HP-NE_UAS_TCA_15m/24h HP NE UAS TCA 15-minute or 24-hour
LP-FE_BBE_TCA_15m/24h LP FE BBE TCA 15-minute or 24-hour
LP-FE_SES_TCA_15m/24h LP FE SES TCA 15-minute or 24-hour
LP-FE_UAS_TCA_15m/24h LP FE UAS TCA 15-minute or 24-hour
LP-NE_BBE_TCA_15m/24h LP NE BBE TCA 15-minute or 24-hour
LP-NE_ES_TCA_15m/24h LP NE ES TCA 15-minute or 24-hour
LP-NE_SES_TCA_15m/24h LP NE SES TCA 15-minute or 24-hour
LP-NE_UAS_TCA_15m/24h LP NE UAS TCA 15-minute or 24-hour
MS-FE_BBE_TCA_15m/24h MS FE BBE TCA 15-minute or 24-hour
MS-FE_ES_TCA_15m/24h MS FE ES TCA 15-minute or 24-hour
MS-FE_SES_TCA_15m/24h MS FE SES TCA 15-minute or 24-hour
MS-FE_UAS_TCA_15m/24h MS FE UAS TCA 15-minute or 24-hour
MS-NE_BBE_TCA_15m/24h MS NE BBE TCA 15-minute or 24-hour
MS-NE_ES_TCA_15m/24h MS NE ES TCA 15-minute or 24-hour
MS-NE_SES_TCA_15m/24h MS NE SES TCA 15-minute or 24-hour
MS-NE_UAS_TCA_15m/24h MS NE UAS TCA 15-minute or 24-hour
PPI-FE_BBE_TCA_15m/24h PPI FE BBE TCA 15-minute or 24-hour

CHAPTER 2
Alarm Lists

PPI-FE_ES_TCA_15m/24h PPI FE ES TCA 15-minute or 24-hour
PPI-FE_SES_TCA_15m/24h PPI FE SES TCA 15-minute or 24-hour
PPI-FE_UAS_TCA_15m/24h PPI FE UAS TCA 15-minute or 24-hour
PPI-NE_ES_TCA_15m/24h PPI NE ES TCA 15-minute or 24-hour
PPI-NE_SES_TCA_15m/24h PPI NE SES TCA 15-minute or 24-hour
PPI-NE_UAS_TCA_15m/24h PPI NE UAS TCA 15-minute or 24-hour
RS-BBE_TCA_15m/24h RS BBE TCA 15-minute or 24-hour
RS-ES_TCA_15m/24h RS ES TCA 15-minute or 24-hour
RS-SES_TCA_15m/24h RS SES TCA 15-minute or 24-hour
RS-UAS_TCA_15m/24h RS UAS TCA 15-minute or 24-hour
Table 2-4 Quality of Service Alarms
2.5 Security Alarms
Table 2-5 lists the FLASHWAVE 4570 security alarms.

Account_Expired_Disabled Account expired or disabled
Log_Is_Full Log is full
Log_Occupancy_Threshold_Reached Log occupancy threshold reached
Unauthorized_Access_Attempt Unauthorized access attempt
Unsuccessful_Logins_Exceeded Unsuccessful logins exceeded
Table 2-5 Security Alarms

CHAPTER 3
Troubleshooting
CHAPTER 3
Troubleshooting

CHAPTER 3
Troubleshooting
This chapter describes the general troubleshooting instructions for each alarm.
3.1 Equipment Alarms
The equipment alarms are listed in the following sub-chapters.
3.1.1 Communication_Fail
Alarm name Communication_Failure

Default severity Major
Alarm object System Controller (SC), High Order Cross Connect
(HOCC), and Low Order Cross Connect (LOCC)
cards
General information and causes The communication between a traffic card and the
SC, HOCC, or LOCC card fails. This also includes
communication between the SC, HOCC, and LOCC
cards.
Troubleshooting instructions
1 Reboot or replace the traffic card.
2 Reboot or replace the SC card.
3 If the alarm persists, contact the next higher level of technical support.
i If the communication failure happens between two SC cards in the 1+1 rendundant
SC system, follow the procedure below to solve the problem.
Troubleshooting instruction for communication failure between two SC cards

1 Cold or warm reboot the standby SC card.
2 If it does not work, remove the standby SC card.
3 Cold or warm reboot the active SC card.
4 After the active SC card completes rebooting, insert the standby SC card.
5 If it does not work, execute a Manual Save of the Management Information Base (MIB)
of the active SC card (by selecting Configuration > NE > MIB Management in the
FLEXR L) and then go to the next step.
6 Remove and insert both SC cards.
7 If the alarm still exists, contact the next higher level of technical support.
i When replacing an SC card, remember to take out the CF card from the original SC
card and insert it into the new SC card.
3.1.2 Equipment_Overheating
Alarm name Equipment_Overheating


CHAPTER 3
Troubleshooting
Alarm object SC, HOCC, LOCC, and all service cards (not
including IO cards)
General information and causes The temperature of the equipment is not in the
normal working range which is specified in the card
properties configuration.
1 Verify that the fan unit is working normally.
2 Verify that the filter unit is clean.
3 Verify that the air-conditioning (if any) is working correctly.
4 Verify that the equipment is working normally.
5 Verify that the card temperature threshold is configured properly.
3.1.3 Fan_Failure
Alarm name Fan_Failure

Alarm object Fan unit
General information and causes The fan unit is defective.
1 Verify the fans in the fan unit are working normally.
2 Replace the fan unit. Changing the upper faulty fan unit must be finished within 2
minutes.
3.1.4 Loss_of_Power_Input
Alarm name Loss_of_Power_Input

Alarm object Power module
General information and causes The -48 V power input is absent.
The input power is lower than -40 V.
The input power is higher than -72 V.
1 Verify that the power cables to the power module are connected correctly.

CHAPTER 3
Troubleshooting
3.1.5 Low_Board_Flash_Card_Capacity
Alarm name Low_Board_Flash_Card_Capacity

Alarm object Flash card
General information and causes After write operation, the system will check the
usage of the Board Flash card. If it exceeds the
threshold, this alarm will be reported
1 Delete some information in the CF card.
3.1.6 Low_Order_Capacity_Mismatch
Alarm name Low_Order_Capacity_Mismatch

Alarm object NE
General information and causes Alarm triggered when the MIB configuration files in a
newly inserted SC card do not match the actual
configuration of the LOCC card in the NE.
1 Download a backup MIB from the PC into the CF card of the newly inserted SC card.
For more information on MIB download, please refer to CHAPTER 6.
Caution If there is no backup MIB, the system will have to be reconfigured.
3.1.7 No_Free_Low_Order_Capacity
Alarm name No_Free_Low_Order_Capacity

Alarm object PDH cards
General information and causes Although a new PDH card is inserted in the shelf,
there is not enough low order capacity in the LOCC
card.
1 Upgrade the LOCC capacity.
2 Delete some existing low order mapping.

CHAPTER 3
Troubleshooting
3.1.8 NO.XFan_Failure
Alarm name NO.XFan_Failure

Alarm object Fan unit
General information and causes The fan unit is defective.
1 Replace the failed fan unit. Replacement of the faulty fan unit must be finished within 2
minutes. To ensure this, prepare the new fan unit before starting the exchange process
(e.g. unpack the unit, check the part numbers, visual inspection of the unit).
3.1.9 OA-Power_Failure
Alarm name OA_Power_Failure

Default severity Critical
Alarm object OA card
General information and causes The power for the OA card fails.
1 Replace the OA card.
3.1.10 OA-Pump_Bias_out_of_Range
Alarm name OA-Pump_Bias_out_of_Range

General information and causes The OA pump bias exceeds the threshold which is
specified in the OA port properties configuration.
1 Verify that the OA pump bias threshold is configured properly.
2 Verify that the OA input power is normal.
3 Verify that the OA card is not aging.
3.1.11 OA-Temperature_out_of_Range
Alarm name OA-Temperature_out_of_Range


CHAPTER 3
Troubleshooting

General information and causes The OA cards temperature exceeds the threshold
which is specified in the OA port properties
configuration.
1 Verify that the fan unit is working correctly.
2 Verify that the OA temperature threshold is configured properly.
3.1.12 PLL_Unlock
Alarm name PLL_Unlock

Alarm object Cards (All cards except HOCC, SC, power module,
and fan unit)
General information and causes The PLL is in the unlock state.
1 If fault occurs during the card boot or synchronization, wait till the initialization process of
the card is complete.
2 If the alarm continues after the initialization is complete, replace the card.
3.1.13 Power_Failure
Alarm name Power_Failure

Alarm object Power module
General information and causes The power module is not working normally.
1 Change the power module.
3.1.14 SC_CF_Module_Absent
Alarm name SC_CF_Module_Absent

Alarm object SC card
General information and causes The CF card is absent.

CHAPTER 3
Troubleshooting
1 Insert the CF card.
For more detailed instruction, refer to The FLASHWAVE 4570 Installation and Test
Manual (ITMN).
3.1.15 SC_CF_Module_Failure
Alarm name SC_CF_Module_Failure

General information and causes The CF card cannot be accessed.
1 Replace the CF card.
For more detailed instruction, refer to The FLASHWAVE 4570 Installation and Test
Manual (ITMN).
3.1.16 SC_SW_Version_Mismatch
Alarm name SC_ SW_Version_Mismatch

General information and causes The software version is different between the active
and standby SC cards.
1 Find which SC card contains the wrong version of the software and replace the wrong
card with a new SC with correct version of the software, or upgrade or downgrade the
software of the wrong one to the correct version.
i Make sure that there is a CF card within the SC card. If the software version is
unknown, contact technical support for help.
3.1.17 SFP_Absent
Alarm name SFP_Absent

Alarm object Optical port
General information and causes The SFP module is absent.

CHAPTER 3
Troubleshooting
1 Insert the proper SFP module.
3.1.18 SFP_Failure
Alarm name SFP_Failure

Alarm object SFP module
General information and causes The SFP module is not working normally.
1 Replace the SFP module.
3.1.19 SFP_Mismatch
Alarm name SFP_Mismatch

Alarm object SFP module
General information and causes The bit rate of the SFP is lower than the port
requirement.
1 Replace the SFP module with a suitable one.
3.1.20 SPI-Temperature_out_of_Range
Alarm name SPI-Temperature_out_of_Range

Alarm object STM-64 port
General information and causes The temperature of the laser exceeds the normal
range.
1 Verify the refrigeration part and the bias current part of the laser are working normally.
2 Replace the 10 Gigabit Small Form Factor Pluggable (XFP) module.

CHAPTER 3
Troubleshooting
3.1.21 Unit_Failure
Alarm name Unit_Failure

Alarm object Cards
General information and causes The card is defective.
1 Replace the card.
3.1.22 Unit_Removal
Alarm name Unit_Removal

Alarm object Cards
General information and causes The card is absent.
1 Insert the card.
3.1.23 Unit_Type_Mismatch
Alarm name UnitType_Mismatch

Alarm object Cards
General information and causes The inserted card type is not consistent with the
preconfigured card type.
1 Replace the card with the correct one.
2 Verify that the card type set in SEEPROM is correct through the mini USB port on the
card.
3.1.24 VCXO_Failure
Alarm name VCXO_Failure

Alarm object HOCC card

CHAPTER 3
Troubleshooting
General information and causes The VCXO component on the HOCC card has
failed.
1 Replace the HOCC card.
3.2 Communication Alarms
The communication alarms are listed in the following sub-chapters.
3.2.1 AU_AIS
Alarm name AU_AIS

Default severity Minor
Alarm object SDH AU
General information and causes The upstream signal is defective.
1 Troubleshoot the SPI, RS, MS, or AU-LOP alarms in the upstream node.
3.2.2 AU_LOP
Alarm name AU_LOP

Alarm object SDH AU
General information and causes No valid AU-4 pointer is found in the received signal
due to:
Line unit failure in the remote node.
Tributary unit failure in the local node.
1 Verify that the upstream external fiber connections are correct.
3.2.3 Embedded_DCC_Channel (n)_Failure
Alarm name Embedded DCC channel 1 failure, or

Embedded DCC channel 2 failure
Alarm object NE
General information and causes DCC communication channel has failed.

CHAPTER 3
Troubleshooting
1 Check the routing configuration for any error.
3.2.4 HCOC27-DCC_Connection_Failure
Alarm name HCOC27-DCC_Connection_Failure

Alarm object SDH HCOC
General information and causes The HCOC27-DCC is disabled at one side of
the DCC link.
DCC link is down.
1 Verify that the HCOC27-DCC is enabled and working normally at both ends of the DCC
link.
3.2.5 HCOC9-DCC_Connection_Failure
Alarm name HCOC9-DCC_Connection_Failure

Alarm object SDH HCOC
General information and causes The HCOC9-DCC is disabled at one side of the
DCC link.
DCC link is down.
1 Verify the HCOC9-DCC is enabled and working normally at both ends of the DCC link.
3.2.6 HP-DEG
Alarm name HP-DEG

Alarm object SDH HP
General information and causes The equivalent Bit Error Rate (BER) exceeded a
preset threshold for the HP-DEG alarm generation,
-x
i.e. ,10 , x = 5, 6, 7, 8, 9.
1 Verify that the upstream external cabling and equipment are normal.

CHAPTER 3
Troubleshooting
2 Verify that the threshold is set correctly.

3.2.7 HP-EXC
Alarm name HP-EXC

Alarm object SDH HP
General information and causes The equivalent BER exceeded a preset threshold for
-x
the HP-EXC alarm generation, i.e., 10 , x = 4, 5.
1 Verify that the upstream external cabling and equipment are normal.
3.2.8 HP-GFP_Customer_Signal_Failure
Alarm name HP-GFP_Customer_Signal_Failure

Alarm object Ethernet WAN ports
General information and causes The upstream LAN port connectivity is down.
1 Check the upstream external cabling and equipment for any error.
3.2.9 HP-GFP_Loss_of_Frame_Delineation
Alarm name HP-GFP_Loss_of_Frame_Delineation

General information and causes The upstream Ethernet signal fails because of GFP
synchronization failure.
1 Verify that the upstream connection and equipment are normal.
3.2.10 HP-PLM
Alarm name HP-PLM

CHAPTER 3
Troubleshooting

Alarm object SDH HP
General information and causes The mapping modes of the local side and the
remote side are not the same.
The expected payload value set via
management system at the local node is not
the same as the actual payload value from the
remote node.
1 Change the mapping mode of the local node to the same mode as that of the remote
node.
2 Change the expected payload value of the local node to the same one as the actual
payload value of the remote node.
3.2.11 HP-RDI
Alarm name HP-RDI

Alarm object SDH HP
General information and causes The downstream NE receives the malfunctioning
signal.
1 React to the far-end alarms.
3.2.12 HP-TIM
Alarm name HP-TIM

Alarm object SDH HP
General information and causes The received path trace identifier does not match
the expected value.
1 Verify that the expected path trace identifier is correct.
3.2.13 HP-UNEQ
Alarm name HP-UNEQ

CHAPTER 3
Troubleshooting

Alarm object SDH HP
General information and causes The VC-4, VC-4-Xc (X = 4, 16, 64) in the STM-N
signal is not in use.
1 Verify that the cross connection are the same at the both end.
3.2.14 HP-Virtual_Concatenation_LOA
Alarm name HP-Virtual_Concatenation_LOA

Alarm object HP VCG
General information and causes The time between the first and last member of a
Virtual Concatenation Group (VCG) to reach the
local node exceeded the differential delay period.
1 Check the SDH path for each VCG member to see which member passes through the
most nodes or is taking the longest time, and configure the shorter route.
3.2.15 HP-Virtual_Concatenation_LOM
Alarm name HP-Virtual_Concatenation_LOM

Alarm object HP VCG member
General information and causes One VCG member failed or was received at the
local node with errors.
1 Check the VCG member of the relevant terminal point for alarms.
2 Check the performance monitoring of the relevant VCG member terminal point for errors.
3.2.16 HP-Virtual_Concatenation_PLCR
Alarm name HP-Virtual_Concatenation_PLCR


CHAPTER 3
Troubleshooting
General information and causes Partial loss of the capacity, receive

If both ends of the NE connections are in the
LCAS mode and the sink status of some TPs
has failed, as well as alarms are reported from
TP in the VCG, this alarm will be activated.
Alternatively, even when the sink status of the
TPs is normal with no alarms reported from
VCG, if the TPs are less than the configured
threshold, this alarm will be activated too.
1 Check upstream external cabling and equipment for any error.
3.2.17 HP-Virtual_Concatenation_PLCT
Alarm name HP-Virtual_Concatenation_PLCT

General information and causes Partial loss of the capacity, transmit.
If both ends of the NE connections are in the
LCAS mode and the source status of some TPs
is Do Not Use (DNU), this alarm will be
activated.
Alternatively, even when the source status of
the TPs is normal with no DNU, if the TPs are
less than the configured threshold, this alarm
will be activated too.
3.2.18 HP-Virtual_Concatenation_TLCR
Alarm name HP-Virtual_Concatenation_TLCR

Alarm object HP VCG

CHAPTER 3
Troubleshooting
General information and causes Total loss of capacity at the receiver

If both ends are in LCAS mode, all TPs have
failed
The TP in the VCG has alarms;
The sink TP receives the IDLE signal sent
from the remote source TP.
If both ends are in non-LCAS mode, any TP has
the following alarms:
AU/TU-AIS
AU/TU -LOP
HP/LP-PLM
HP/LP -TIM
HP/LP -UNEQ
HP-Virtual_Concatenation_LOM
If the following VCG alarms occur:
HP-Virtual_Concatenation_LOA
HP-GFP_Loss_of_Frame_Delineation
3.2.19 Link_Failure
Alarm name Link_Failure

Alarm object Ethernet ports
General information and causes The interconnecting fiber contacts fail.
The receiver fails in the relevant card.
The transmitter fails in the upstream equipment.
Discontinuity of the intermediate cabling occurs.
The erroneous routing of intermediate cabling
occurs.
The fiber type is incorrect.
1 Verify that the connections of the physical layer are correct.
2 Verify that the fiber cable connectors are clean.
3 Verify that the fiber type is correct.
3.2.20 Loss_of_Timing_Input
Alarm name Loss_of_Timing_Input


CHAPTER 3
Troubleshooting
General information and causes No incoming signal on the 2048 KHz/Kbps station
clock port. This is detected by the absence of
pulses in the signal.
Fault in the equipment producing the station
clock.
Discontinuity in the cabling between the station
clock equipment and the node or erroneous
routing
2 Verify that the fiber cables are not damaged and the connectors are not dirty.
3.2.21 Loss_of_Timing_Output
Alarm name Loss_of_Timing_Output

General information and causes There is no station clock output available. The
HOCC card is defective and unable to generate the
timing output.
1 Verify that the synchronization configuration is correct.
2 Verify that the external timing input is normal.
3 Replace the HOCC card.
3.2.22 LP-DEG
Alarm name LP-DEG

Alarm object SDH LP
General information and causes The BER in the LP has exceeded the
provisioned LP-DEG alarm threshold. The
quality of the transmission signal is degraded.
This error is caused by fault(s) in upstream
external cabling or equipment.
1 Check the upstream external cabling and equipment for error.
2 Verify that the threshold configuration is correct.

CHAPTER 3
Troubleshooting
3.2.23 LP-EXC
Alarm name LP-EXC

Alarm object SDH LP
General information and causes The BER in the LP has exceeded the
provisioned LP-EXC alarm threshold. The
quality of the transmission signal is degraded.
This error is caused by fault(s) in upstream
external cabling or equipment.
2 Verify that the threshold configuration is correct.
3.2.24 LP-GFP_Customer_Signal_Failure
Alarm name LP-GFP_Customer_Signal_Failure

General information and causes There is a customer signal failure at lower order
path.
The upstream LAN port connectivity is down or
there is a fault(s) in upstream external cabling or
equipment
3.2.25 LP-GFP_Loss_of_Frame_Delineation
Alarm name LP-GFP_Loss_of_Frame_Delineation

General information and causes There is loss of frame delineation in the lower order
path. The upstream Ethernet signal fails because of
GFP synchronization failure or there is a fault(s) in
upstream external cabling and equipment.
1 Check the upstream connection and equipment for error.

CHAPTER 3
Troubleshooting
3.2.26 LP-PLM
Alarm name LP-PLM

Alarm object SDH LP
General information and causes The received payload value, used to indicate the
composition of the VC-12 payload, does not match
the expected value.
Mapping mode of local and far-end NEs is not
same.
Expected payload value set for the local node
via the TP Configuration window of the FLEXR
L is not the same as the actual payload value in
the remote node.
1 Verify that the traffic bandwidth structure of the local node is the same as that of the
remote node.
2 Change the expected traffic type of the local node using the TP Configuration menu of
the FLEXR L to match the actual payload value in remote node.
3.2.27 LP-RDI
Alarm name LP-RDI

Alarm object SDH LP
General information and causes A remote defect indicator has been received. The
downstream node has detected an error on the
receiving side:
TU-AIS
LP-TIM (PDH cards)
i LP-TIM (enable TIM) will cause LP-RDI.
1 No error in the reporting node. Troubleshoot the failure that caused the LP-RDI
generation at the far-end node.
3.2.28 LP-RFI
Alarm name LP-RFI


CHAPTER 3
Troubleshooting
Alarm object SDH LP

General information and causes There is a remote failure indication at the lower order
path.
The downstream node that reported the alarm
detects a failure at its receiving side:
VC-11 byte synchronous path remote failure.
1 No error in the reporting node. Troubleshoot the failure that caused the LP-RFI
generation at the far-end node.
3.2.29 LP-TIM
Alarm name LP-TIM

Alarm object SDH LP
General information and causes Mismatch between received trace ID and expected
trace ID.
The received path trace identifier in the J1 byte
(VC-3) or J2 byte of the VC-n does not match the
provisioned value.
A provisioned trace string inserted in a received
VC-12 was corrupted or was not received at all,
due to wrong configuration, hardware failures, or
transmission failures.
1 Check the cross-connections for any error.
2 Check the tributary cables and tributary units for any error.
3 Verify that the provisioned expected trace ID is correct
3.2.30 LP-UNEQ
Alarm name LP-UNEQ

Alarm object SDH LP
General information and causes Lower order path in STM-N signal is unequipped or
is not in use.
1 Confirm or create the cross connection settings at the remote side to be consistent with
the local side.

CHAPTER 3
Troubleshooting
i When defining or changing a cross-connection this alarm will almost inevitably come
up as it is practically impossible to validate the changes at both sides at the same
moment.
Warning The LP-UNEQ cannot be reported from 126 E1 (W/P) cards monitored ports if
there is no cross-connection card equipped in NE.
!
3.2.31 LP-Virtual_Concatenation_LOA
Alarm name LP-Virtual_Concatenation_LOA

Alarm object LP VCG
General information and causes There is LOA at the lower order path virtual
concatenation.
The time between the first and last member of a
VCG group to reach the local node exceeds the
differential delay period.
1 Check the SDH path for each VCG member to see which member passes through the
most nodes or is taking the longest time, and configure the shorter route.
3.2.32 LP-Virtual_Concatenation_LOM
Alarm name LP-Virtual_Concatenation_LOM

Alarm object LP VCG member
General information and causes There is LOM at the lower order path virtual
concatenation.
One VCG member has failed or has been
erroneously received at the local node.
1 Check the VCG member of the relevant terminal point for alarms..
2 Check the performance monitoring of the relevant VCG member terminal point for errors.
3.2.33 LP-Virtual_Concatenation_TLCR
Alarm name LP-Virtual_Concatenation_TLCR


CHAPTER 3
Troubleshooting
Alarm object LP VCG

General information and causes Total loss of capacity, receive
If both ends are in LCAS mode, all TPs failed:
The TPs in the VCG have alarms;
The sink TP receives the IDLE signal sent
from the remote source TP.
If both ends are in non-LCAS mode, any TP has
the following alarms:
AU/TU-AIS
AU/TU-LOP
HP/LP-PLM
HP/LP-TIM
HP/LP-UNEQ
HP/LP-Virtual_Concatenation_LOM
If the following VCG alarms occur:
HP/LP-Virtual_Concatenation_LOA
HP/LP-GFP_Loss_of_Frame_Delineation
3.2.34 MS_AIS
Alarm name MS_AIS

Alarm object SDH MS
General information and causes The received signal contains MS-AIS. MS-AIS is an
indication that loss of signal or loss of frame has
been detected in the upstream NE or equipment.
3.2.35 MS-DCC_Connection_Failure
Alarm name MS-DCC_Connection_Failure

Alarm object SDH MS
General information and causes No connection could be established on an
enabled MS DCC link.
MS-DCC is disabled at one side of the MS DCC
link.

CHAPTER 3
Troubleshooting
1 Verify that the MS-DCC is enabled and working normally at both ends of the MS DCC
link.
3.2.36 MS_DEG
Alarm name MS_DEG

Alarm object SDH MS
General information and causes The BER in the MS has exceeded the provisioned
MS-DEG alarm threshold. The quality of the
transmission signal has degraded.
The equivalent BER exceeds a preset threshold
of 10-x, x = 5, 6, 7, 8, 9.
There is a fault(s) in the upstream external
cabling or equipment.
2 Verify that the threshold is configured correctly.
3.2.37 MS_EXC
Alarm name MS_EXC

Alarm object SDH MS
General information and causes The BER in the MS has exceeded the provisioned
MS-EXC alarm threshold. The quality of the
transmission signal has degraded.
The equivalent BER exceeds a preset threshold
of 10-x, x = 3, 4, 5.
There are faults in upstream external cabling or
equipment.
3.2.38 MS-K1/K2_Mismatch
Alarm name MS-K1/K2_Mismatch

CHAPTER 3
Troubleshooting

Alarm object SDH MS
General information and causes Invalid K1/K2 bytes have been received in the
MS section.
The protection switching is not successful.
1 Verify that the conditions of protection switching are normal.
3.2.39 MS_RDI
Alarm name MS_RDI

Alarm object SDH MS
General information and causes The far-end node of the multiplex section has
detected an error in the incoming signal, and, as a
consequence, has inserted Remote Defect
Indication (RDI) (110 in bits 6, 7, and 8 of the K2
byte) into the outgoing signal at the upstream
direction.
The downstream NE receives the failed signal:
MS-AIS
RS-LOF
RS-TIM
SPI-LOS
The following situations occur in the far-end station:
No signal received
AIS signal received
Excessive error rate
i RS-TIM (enable TIM and enable TIM AIS) will cause MS-RDI.
RS-TIM (enable TIM and disable TIM AIS) will not cause MS-RDI.
2 Verity that the local transmitting equipment is working normally.
3 Troubleshoot the faults reported in the far-end node.
3.2.40 OA-Gain_High
Alarm name OA-Gain_High

Alarm object OA port

CHAPTER 3
Troubleshooting
General information and causes Gain of OA is too high and has exceeded the
following threshold:
20 dB POA: > 21 dB
13 dBm BOA: > 19 dB
15 dBm BOA: > 21 dB
18 dBm BOA: > 24 dB
1 Verify that the output power of the OA is set properly.
2 Verity that the input power of the OA is normal.
3.2.41 OA-Input_LOS
Alarm name OA-Input_LOS

General information and causes There is a loss of signal at OA input for the
following reason:
The fiber is broken.
The optical connector is dirty.
The input optical power is lower than the pre-
defined threshold.
2 Verity that the transmitter in the far-end is working normally.
3 Verify that the fibers and connectors are not damaged.
4 Measure the input power and verify that the pre-defined input power threshold is correct.
5 Clean the optical connector if it is dirty.
3.2.42 OA-Output_LOS
Alarm name OA-Output_LOS

General information and causes There is loss of signal at OA output for the following
reason:
The local transmitting module fails.
The output optical power is lower than the pre-
defined threshold.
1 Verify that the local transmitting module is working normally.

CHAPTER 3
Troubleshooting
2 Verify that the pre-defined output power threshold is correct.

3.2.43 OA-Output_Power_High
Alarm name OA-Output_Power_High

General information and causes OA output power is too high and has exceeded the
following threshold:
20 dB POA: Output power > -9 dBm
13 dBm BOA: Output power > 14 dBm
1 Verify that the gain of the OA is configured properly.
2 Verify the input power of the OA is proper.
3.2.44 ODU_AIS
Alarm name ODU_AIS

Alarm object 2 x OTU-2
General information and causes ODU_AIS is an alarm indication signal that the
upstream station frame changes its frame position.
1 Verify that the transmitter in the far-end is working normally.
3.2.45 ODU_BDI
Alarm name ODU_BDI

General information and causes ODU section backward defect indicator.
In the upstream station, one of the following
conditions is detected:
ODU_AIS
ODU_LCK
ODU_OCI

CHAPTER 3
Troubleshooting
2 Verify that the local transmitter is working normally.
3 Troubleshoot the reported receivers fault in the far-end.
3.2.46 ODU_DEG
Alarm name ODU_DEG

Alarm object Optical channel data unit
General information and causes DEGM consecutive bad intervals (which is 1 second
period used for performance monitoring) are
detected.
A degraded signal defect (dDEG) is detected
2 Verify that the degraded monitor (DEGM) interval and threshold are configured correctly.
3.2.47 ODU_LCK
Alarm name ODU_LCK

General information and causes The connection in upstream is locked, and no signal
is passed through.
3.2.48 ODU_LOFLOM
Alarm name ODU_LOFLOM

General information and causes There is loss of frame and loss of multi-frame in
ODUK.

CHAPTER 3
Troubleshooting
3.2.49 ODU_MSIM
Alarm name ODU_MSIM

General information and causes Mapping mode of local side and far-end sides are not
the same
1 Reconfigure the mapping mode of the local side to the same as that of the remote node.
3.2.50 ODU_OCI
Alarm name ODU_OCI

General information and causes The upstream station matrix connection is open as a
result of a management command.
1 Verify that the ODU connection of the far-end node is correct.
3.2.51 ODU_PLM
Alarm name ODU_PLM

General information and causes Mapping modes of the local side and the remote
side are not the same.
The expected payload value set via management
system in the local side is not the same as the
actual payload value from the remote side
1 Verify that the mapping mode of the local node is the same as that of the remote node.
2 Reconfigure the expected payload value of the local node to match the actual payload
value in the remote node.

CHAPTER 3
Troubleshooting
3.2.52 ODU_TIM
Alarm name ODU_TIM

General information and causes The received ODU trace identifier, used to verify the
connectivity to the intended transmitter, does not
match the provisioned value.
There is wrong routing somewhere in the network
due to:
Wrong fiber cabling
Wong expected trace identifier configuration
1 Verify that the fiber cable connection is correct.
2 Verify that the expected trace identifier is configured correctly.
3.2.53 OTU-BDI
Alarm name OTU-BDI

General information and causes OTU section backward defect indicator. In the
upstream station, one of the following conditions is
detected:
SPI_LOS (Loss of signal);
OTU_LOF (Loss of frame);
OTU_LOM (Loss of multiframe);
OTU_TIM (Section trace identifier mismatch).
1 Check the upstream external fibers and equipment for any error.
2 Verify that the local node is working normally.
3 Troubleshoot the indicated receive side faults in the far-end node..
3.2.54 OTU-DEG
Alarm name OTU-DEG


CHAPTER 3
Troubleshooting
General information and causes DEGM consecutive bad intervals (which is 1 second
period used for performance monitoring) are
detected.
A degraded signal defect (dDEG) is detected
2 Verify that the degraded monitor (DEGM) interval and threshold are configured correctly.
3.2.55 OTU-LOF
Alarm name OTU-LOF

General information and causes OTU section loss of frame alignment. Alarm occurs
when an OOF state persists for a defined period of
time.
3.2.56 OTU-LOM
Alarm name OTU-LOM

General information and causes OTU section loss of multi-frame alignment. Alarm
occurs when the received multi-frame alignment
signal does not match the expected multiframe
number in defined consecutive OTUK frames.
3.2.57 OTU-TIM
Alarm name OTU-TIM


CHAPTER 3
Troubleshooting
General information and causes The received OTU trace identifier does not match the
provisioned value.
Fiber cable connection is not correct.
Configuration of the expected trace identifier is
not correct
1 Verify that the fiber cable connection is correct.
2 Verify that the expected trace identifier is configured correctly.
3.2.58 PPI-AIS
Alarm name PPI-AIS

Alarm object PDH port
General information and causes There is alarm indication signal in the E1, E3, or
DS3 frame on the PDH ports. In one of the
upstream nodes a defect is detected and leads to
the insertion of the alarm indication signal.
3.2.59 PPI-LOF
Alarm name PPI-LOF

General information and causes There is loss of frame in E1, E3, or DS3 on the
PDH ports. It is not possible to align the frame
structure of the E1/E3/DS3 signal received.
3.2.60 PPI-LOM
Alarm name PPI-LOM


CHAPTER 3
Troubleshooting
General information and causes There is loss of multi-frame in E1. It is not possible
to align the multi-frame structure of the E1 signal
received to the Cyclic Redundancy Check (CRC)
multiframe.
3.2.61 PPI-LOS
Alarm name PPI-LOS

General information and causes There is no incoming signal on the PDH tributary
port. The LOS state is considered to have occurred
when the amplitude of the relevant signal has
dropped below the preset limits for a prescribed
period because of the following reasons:
Interconnecting cabling contacts have a
problem.
Receiver of the relevant tributary unit is faulty.
Transmitter in the upstream equipment (not the
transmission system) is faulty.
There is discontinuity in the intermediate
cabling.
There is erroneous routing of intermediate
cabling.
1 Check the connections of the physical layer for error.
2 Verify there is no cable breaks or dirty connectors (measure it with power meter and
clear it).
3.2.62 PPI-RDI
Alarm name PPI-RDI

Alarm object PDH Port
General information and causes There is remote alarm indication in the E1, E3, or
DS3 frame. When a PDH Physical Interface
alarm from the local node is transmitted to the
remote (far-end) node, the far-end node will send
this alarm back.

CHAPTER 3
Troubleshooting
1 Verify that the transmitter in the local node is working normally.
3.2.63 RPR-Exceed_Max_Stations
Alarm name RPR-Exceed_Max_Stations

Alarm object RPR card
General information and causes Number of stations in the RPR ring exceeds the
maximum limit of 32.
1 Reduce the station number of the ring to 32.
3.2.64 RPR-Link_Failure_East
Alarm name RPR-Link_Failure_East

General information and causes A time-out happened to the east RPR links which
function as active detection.
1 Verify that the optical fiber or the SDH cross-connection used for the east RPR path has
no problem.
3.2.65 RPR-Link_Failure_West
Alarm name RPR-Link_Failure_West

General information and causes A time-out happened to the west RPR links which
function as active detection.
1 Verify that the optical fiber or the SDH cross-connection used for the west RPR path has
no problem.

CHAPTER 3
Troubleshooting
3.2.66 RPR-Miscabling_East
Alarm name RPR-Miscabling_East

General information and causes The east link of one RPR station is wrongly
connected to the same side (east link) of another
RPR station.
1 Re-configure the RPR link direction of one of the links, either local or far end, to make
sure the west (east) link connects to the east (west) link. Ensure this change is
consistent with the rest of the topology structure.
3.2.67 RPR-Miscabling_West
Alarm name RPR-Miscabling_West

General information and causes The west link of one RPR station is wrongly
connected to the same side (west link) of another
RPR station.
1 Re-configure the RPR link direction of one of the links, either local or far end, to make
sure the west (east) link connects to the east (west) link. Ensure this change is
consistent with the rest of the topology structure.
3.2.68 RPR-Protection_Misconfig
Alarm name RPR-Protection_Misconfig

General information and causes At least one stations protection mode is different
from other stations.
1 Verify that the protection mode in all of the RPR stations of the ring is the same.

CHAPTER 3
Troubleshooting
3.2.69 RPR-Ringlet0_ReservedA0_Exceeding
Alarm name RPR-Ringlet0_ReservedA0_Exceeding

General information and causes A0 bandwidth reserved on RPR ringlet0 exceeds
the link rate.
1 Re-configure the A0 bandwidth reserved on RPR ringlet0 and make sure that it does not
exceed the available link rate.
3.2.70 RPR-Ringlet1_ReservedA0_Exceeding
Alarm name RPR-Ringlet1_ReservedA0_Exceeding

General information and causes A0 bandwidth reserved on RPR ringlet1 exceeds
the link rate.
1 Re-configure the A0 bandwidth reserved on RPR ringlet1 and make sure it does not
exceed the available link rate.
3.2.71 RPR-Topology_Inconsistent
Alarm name RPR-Topology_Inconsistent

General information and causes Inconsistent topology of the RPR ring is usually
caused by the duplicate MAC addresses.
1 Re-configure the duplicated RPR stations MAC address.
3.2.72 RPR-Topology_Instability
Alarm name RPR-Topology_Instability


CHAPTER 3
Troubleshooting
General information and causes Topology instability is caused by the topology not
being discovered correctly, because of reasons
such as the incorrect configuration of RPR links
and stations.
1 Reconfigure the RPR networks topology (such as the cross connection (CC), the WAN
port trigger, the optical link, etc.) and make sure the configuration is correct.
3.2.73 RS-DCC_Connection_Failure
Alarm name RS-DCC_Connection_Failure

Alarm object SDH RS
General information and causes There is DCC connection failure in the
regenerator section.
RS-DCC is disabled at one side of the RS DCC
link.
1 Verify the RS-DCC is enabled and working normally at both ends of the RS DCC link.
3.2.74 RS-DEG
Alarm name RS-DEG

Alarm object SDH RS
General information and causes The quality of the transmission signal is degraded,
and the BER in the RS has exceeded the
provisioned RS-DEG alarm threshold.
An RS-DEG is declared d when the equivalent
BER exceeds a preset threshold of 10-x, x = 6, 7,
8, 9.
Fault(s) in upstream external cabling or
equipment.
1 Check the upstream external cabling and equipment for any possible errors.

CHAPTER 3
Troubleshooting
3.2.75 RS-EXC
Alarm name RS-EXC

Alarm object SDH RS
General information and causes The quality of the transmission signal is degraded,
and the BER in the RS has exceeded the
provisioned RS-EXC alarm threshold.
An RS-EXC is declared when the equivalent
BER exceeds a preset threshold of 10-5.
Fault(s) in upstream external cabling or
equipment.
3.2.76 RS-LOF
Alarm name RS_LOF

Alarm object SDH RS
General information and causes The position of the frame alignment bytes (A1/A2
bytes) cannot be detected correctly in the received
signal for the following reasons:
The received signal does not match the port rate
(for example, this could be caused by a
misconnected fiber, such as an STM-1 signal
received at an STM-4 port).
The Section Overhead (SOH) of the received
SDH signal is not correctly structured (due to a
failure of the transmitting card at the far-end).
The receiver in the card reporting the alarm is
defective.
The port input level (dBm) is too high or too low.
The fiber type is wrong.
1 Verify that the intermediate fiber is normal.
2 Verify that the connectors are clean.
3 Loop the signal from the transmitter to the receiver. Verify that no LOF fault is reported.
If there is LOF, replace the card.
4 Verify that the incoming signal rate is correct.
5 Verify that the transmitter in the far-end is normal.

CHAPTER 3
Troubleshooting
i This alarm can be enabled or disabled in the Alarm Rule Switch Configuration
window of the FLEXR L by selecting Fault > Alarm Rule Switch Configuration.
3.2.77 RS-TIM
Alarm name RS-TIM

Alarm object SDH RS
General information and causes The received RS trace identifier used to verify the
continued connection to the intended transmitter
does not match the provisioned value.
Fiber cable connection is not correct.
Configuration of the expected trace identifier is
not correct.
1 Verify that the fiber cables are connected correctly by interpreting the received STM-N
RS trace identifiers.
2 Verify that the expected RS trace identifier is correct.
3.2.78 Signal_Error_Fail
Alarm name Signal_Error_Fail

Alarm object SDH, PDH, and all interface cards (including SI
card)
General information and causes This alarm can be triggered when there is no signal
on the port or the signal is not correct, in case of
interface card absence, card mismatch, and card
failure.
1 Verify the connections of the physical layer are correct..
4 Check whether there is fiber breaks or dirty connector.
5 Verify that the card state is normal.
3.2.79 SPI-LOS
Alarm name SPI-LOS

CHAPTER 3
Troubleshooting

Alarm object SDH SPI
General information and causes The optical input power at the corresponding port is
too low. Frame alignment and synchronization to
the received signal is not possible.
When the optical input power is being gradually
decreased below the receiver sensitivity limit, loss
of frame will be reported. If it reaches to a low
enough level, a loss of signal will be reported. The
possible causes are as follows:
The fiber is broken.
The optical connectors are dirty.
The upstream far-end station fails.
2 Verify that the transmitter in the far-end is working normal.
4 Check whether there is fiber breaks or dirty connector.
3.2.80 Synchronization_Signal_Message_Mismatch
Alarm name Synchronization_Signal_Message_Mismatch

General information and causes The SSM byte is invalid.
1 Verify that the SSM byte value is valid.
3.2.81 System_Clock_Holdover_Longer
Alarm name System_Clock_Holdover_Longer

Default severity Warning
General information and causes The system clock has been running in the holdover
mode for more than 24 hours.
1 Repair the failed timing reference.
2 Re-lock the system clock to a valid timing reference.

CHAPTER 3
Troubleshooting
3.2.82 System_Clock_Unlocked
Alarm name System_Clock_Unlocked

General information and causes The system clock is not locked for the following
possible causes:
All selected timing references are lost or have
failed.
The system clock mode has been changed from
the locked mode to the holdover or free-running
mode manually.
1 Verify the selected timing reference works normally.
2 Re-select a valid timing reference.
3 Set the system clock working mode as locked
3.2.83 Timing_Reference_Degrade
Alarm name Timing_Reference_Degrade

Alarm object Input clock reference
General information and causes The frequency offset of the timing source is out
of range.
The phase change of the timing source is
abnormal.
1 Verify that the upstream equipment is working normally.
2 Verify that the local timing input equipment is working normally.
3.2.84 Timing_Reference_Failure
Alarm name Timing_Reference_Failure

Alarm object Input clock reference
General information and causes The timing reference signal is not acceptable as
timing source.
The timing reference clock fails.

CHAPTER 3
Troubleshooting
2 Verify that the local timing input equipment is working normally.
3.2.85 TU-AIS
Alarm name TU-AIS

Alarm object SDH TU
General information and causes The VC-3 or VC-12 payload signal is replaced by
the alarm indication signal. This is detected by
checking the TU-3 or TU-12 pointer bytes for all 1
second patterns.
In one of the upstream nodes a defect is detected
which leads to the insertion of the alarm
indication signal.
3.2.86 TU-LOM
Alarm name TU-LOM

Alarm object SDH TU
General information and causes It is not possible to align to the multiframe structure of
the VC-4 signal received. Therefore VC-12 overhead
and payload data cannot be extracted.
2 Using the management system, check if the card generating the multi-frame alignment
signal has a unit failure. If so, replace it with a new one.
3 If there is no unit failure found, loop the STM-1 signal at the transmitting NE and at the
receiving NE. In this condition, the NE reporting VC-4 loss of multiframe contains the
faulty unit.

CHAPTER 3
Troubleshooting
3.2.87 TU-LOP
Alarm name TU-LOP

Alarm object SDH TU
General information and causes There is loss of pointer in tributary unit. No valid
tributary unit pointer interpretation is obtained in the
received signal.
2 Verify that the TP multiplexer structure of the both ends of the path is the same.
3.3 Environmental Alarms
The environmental alarm is listed in the following sub-chapter.
3.3.1 ENV_MDI<n>
Alarm name ENV_MDI<n>

Default severity Warning
Alarm object MDI associated condition
General information and causes The states of the MDI items has changed.
1 Revert the MDI associated condition to the original state.
2 Verify that the MDI associated condition is provisioned properly.
3.4 Quality of Service Alarms
The quality of service alarms are listed in the following sub-chapters.
3.4.1 AU-PJCN_TCA_15m/24h
Alarm name AU-PJCN_TCA_15m, or AU-PJCN_TCA_24h

Alarm object Monitored performance parameter

CHAPTER 3
Troubleshooting
General information and causes The AU performance monitor counter PJCN

exceeded the provisioned threshold during a 15-
minute or 24-hour period. When the input data rate
is higher than the output data rate, a negative
pointer justification will occur.
1 Set the all the relevant NEs to synchronize with each other.
3.4.2 AU-PJCP_TCA_15m/24h
Alarm name AU-PJCP_TCA_15m, or AU-PJCP_TCA_24h

General information and causes The AU performance monitor counter PJCN
minute or 24-hour period. When the input data rate
is lower than the output data rate, a positive pointer
justification will occur.
1 Set the all the relevant NEs to synchronize with each other.
3.4.3 Excessive_ Bad_Bytes_Received_TCA_1s (LAN or WAN)
Alarm name Excessive_ Bad_Bytes_Received_TCA_1s (LAN or

WAN)
General information and causes The number of the bad bytes received exceeded
the provisioned threshold value for one of the
following possible reasons.
Erroneous routing of intermediate cabling.
Equipment fault(s) in the upstream station.
Wrong LAN/GFP group port configuration.
1 Check the upstream external cabling and equipment for errors.
2 Check whether the upstream NE sent out excessive bad bytes intentionally.

CHAPTER 3
Troubleshooting
3.4.4 Excessive_ Bad_Packets_Received_TCA_1s (LAN or WAN)
Alarm name Excessive_ Bad_Packets_Received_TCA_1s (LAN

or WAN)
General information and causes The number of the bad packets received at
LAN/WAN interface exceeded the provisioned
threshold value for one of the following possible
reasons.
Erroneous routing of intermediate cabling.
Equipment fault(s) in the upstream station.
Wrong LAN/GFP group port configuration.
1 Check the upstream external cabling and equipment for errors.
2 Check whether the upstream NE sent out excessive bad bytes intentionally.
3.4.5 E1-Negative_Bit-slip_TCA_15m/24h
Alarm name E1-Negative_Bit-slip_TCA_15m, E1-Negative_Bit-

slip_TCA_24h
Alarm object PDH E1
General information and causes The number of negative bit-slip during a 15-minute
or 24-hour period is greater than or equal to the
threshold. The alarm only applies to E1 retiming
ports.
The clock frequency of the E1 service is faster than
the frequency of the system clock.
1 Verify the clock frequency of E1 ports is correct.
2 Verify that the system clock is in locked status.
3.4.6 E1-Positive_Bit-slip_TCA_15m/24h
Alarm name E1-Positive_Bit-slip_TCA_15m, or E1-Positive_Bit-

slip_TCA_24h
Alarm object PDH E1

CHAPTER 3
Troubleshooting
General information and causes The number of positive bit-slip during a 15-minute
or 24-hour period is greater than or equal to the
threshold. The alarm only applies to E1 retiming
ports.
The clock frequency of the E1 service is faster than
the frequency of the system clock.
1 Verify the clock frequency of E1 ports is correct.
2 Verify that the system clock is in locked status.
3.4.7 HP-FE_BBE_TCA_15m/24h
Alarm name HP-FE_BBE_TCA_15m, or HP-FE_BBE_TCA_24h

General information and causes The HP far-end performance monitor counter BBE
minute or 24-hour period.
An indication returned to the upstream node to
notify that the errored blocks have been detected at
the downstream node. The HP BBE value of the
downstream node exceeded the provisioned
threshold.
1 Check the downstream external cabling for error.
3.4.8 HP-FE_ES_TCA_15m/24h
Alarm name HP-FE_ES_TCA_15m, or HP-FE_ES_TCA_24h

General information and causes The HP far-end performance monitor counter ES
the downstream node. The HP ES value of the
threshold.

CHAPTER 3
Troubleshooting
3.4.9 HP-FE_SES_TCA_15m/24h
Alarm name HP-FE_SES_TCA_15m, or HP-FE_SES_TCA_24h

General information and causes The HP far-end performance monitor counter SES
the downstream node. The HP SES value of the
threshold.
3.4.10 HP-FE_UAS_TCA_15m/24h
Alarm name HP-FE_UAS_TCA_15m, or HP-FE_UAS_TCA_24h

General information and causes The HP far-end performance monitor counter UAS
the downstream node. The HP UAS value of the
threshold.
3.4.11 HP-NE_BBE_TCA_15m/24h
Alarm name HP-NE_BBE_TCA_15m, or HP-NE_BBE_TCA_24h


CHAPTER 3
Troubleshooting

General information and causes The HP near-end performance monitor counter
BBE exceeded the provisioned threshold during a
15- minute or 24-hour period.
The possible reasons are as follows:
High order path BBE causes low order path
BBE.
The operating temperature of the NE has
exceeded the maximum permitted value.
Equipment fault(s) in the upstream nodes.
3.4.12 HP-NE_ES_TCA_15m/24h
Alarm name HP-NE_ES_TCA_15m, or HP-NE_ES_TCA_24h

General information and causes The HP near-end performance monitor counter ES
3.4.13 HP-NE_SES_TCA_15m/24h
Alarm name HP-NE_SES_TCA_15m, or HP-NE_SES_TCA_24h

SES exceeded the provisioned threshold during a

CHAPTER 3
Troubleshooting
3.4.14 HP-NE_UAS_TCA_15m/24h
Alarm name HP-NE_UAS_TCA_15m, or

HP-NE_UAS_TCA_24h
UAS exceeded the provisioned threshold during a
3.4.15 LP-FE_BBE_TCA_15m/24h
Alarm name LP-FE_BBE_TCA_15m, or LP-FE_BBE_TCA_24h

General information and causes The LP far-end performance monitor counter BBE
the downstream node. The LP BBE value of the
threshold.
3.4.16 LP-FE_SES_TCA_15m/24h
Alarm name LP-FE_SES_TCA_15m, or LP-FE_SES_TCA_24h


CHAPTER 3
Troubleshooting
General information and causes The LP far-end performance monitor counter SES
the downstream node. The LP SES value of the
threshold.
3.4.17 LP-FE_UAS_TCA_15m/24h
Alarm name LP-FE_UAS_TCA_15m, or LP-FE_UAS_TCA_24h

General information and causes The LP far-end performance monitor counter UAS
the downstream node. The LP UAS value of the
threshold.
3.4.18 LP-NE_BBE_TCA_15m/24h
Alarm name LP-NE_BBE_TCA_15m, or LP-NE_BBE_TCA_24h

General information and causes The LP near-end performance monitor counter BBE
High order path BBE causes low order path
BBE.
The operating temperature of the NE has
exceeded the maximum permitted value.

CHAPTER 3
Troubleshooting
3.4.19 LP-NE_ES_TCA_15m/24h
Alarm name LP-NE_ES_TCA_15m, or LP-NE_ES_TCA_24h

General information and causes The LP near-end performance monitor counter ES
3.4.20 LP-NE_SES_TCA_15m/24h
Alarm name LP-NE_SES_TCA_15m, or LP-NE_SES_TCA_24h

General information and causes The LP near-end performance monitor counter SES
3.4.21 LP-NE_UAS_TCA_15m/24h
Alarm name LP-NE_UAS_TCA_15m, or LP-NE_UAS_TCA_24h

General information and causes The LP near-end performance monitor counter

CHAPTER 3
Troubleshooting
3.4.22 MS-FE_BBE_TCA_15m/24h
Alarm name MS-FE_BBE_TCA_15m, or MS-FE_BBE_TCA_24h

General information and causes The MS far-end performance monitor counter BBE
the downstream node. The MS BBE value of the
threshold.
3.4.23 MS-FE_ES_TCA_15m/24h
Alarm name MS-FE_ES_TCA_15m, or MS-FE_ES_TCA_24h

General information and causes The MS far-end performance monitor counter ES
the downstream node. The MS ES value of the
threshold.
3.4.24 MS-FE_SES_TCA_15m/24h
Alarm name MS-FE_SES_TCA_15m, or MS-FE_SES_TCA_24h


CHAPTER 3
Troubleshooting

General information and causes The MS far-end performance monitor counter SES
the downstream node. The MS SES value of the
threshold.
3.4.25 MS-FE_UAS_TCA_15m/24h
Alarm name MS-FE_UAS_TCA_15m, or

MS-FE_UAS_TCA_24h
General information and causes The MS far-end performance monitor counter UAS
the downstream node. The MS UAS value of the
threshold.
3.4.26 MS-NE_BBE_TCA_15m/24h
Alarm name MS-NE_BBE_TCA_15m, or

MS-NE_BBE_TCA_24h
General information and causes The MS near-end performance monitor counter
Dirty optical connector(s).

CHAPTER 3
Troubleshooting
3.4.27 MS-NE_ES_TCA_15m/24h
Alarm name MS-NE_ES_TCA_15m, or MS-NE_ES_TCA_24h

General information and causes The MS near-end performance monitor counter ES
3.4.28 MS-NE_SES_TCA_15m/24h
Alarm name MS-NE_SES_TCA_15m, or

MS-NE_SES_TCA_24h
3.4.29 MS-NE_UAS_TCA_15m/24h
Alarm name MS-NE_UAS_TCA_15m, or

MS-NE_UAS_TCA_24h

CHAPTER 3
Troubleshooting

3.4.30 PPI-FE_BBE_TCA_15m/24h
Alarm name PPI-FE_BBE_TCA_15m, or

PPI-FE_BBE_TCA_24h
General information and causes The PDF far-end performance monitor counter BBE
3.4.31 PPI-FE_ES_TCA_15m/24h
Alarm name PPI-FE_ES_TCA_15m, or PPI-FE_ES_TCA_24h

General information and causes The PDF far-end performance monitor counter ES
3.4.32 PPI-FE_SES_TCA_15m/24h
Alarm name PPI-FE_SES_TCA_15m, or

PPI-FE_SES_TCA_24h

CHAPTER 3
Troubleshooting
General information and causes The PDF far-end performance monitor counter SES
3.4.33 PPI-FE_UAS_TCA_15m/24h
Alarm name PPI-FE_UAS_TCA_15m, or

PPI-FE_UAS_TCA_24h
General information and causes The PDF far-end performance monitor counter UAS
3.4.34 PPI-NE_ES_TCA_15m/24h
Alarm name PPI-NE_ES_TCA_15m, or PPI-NE_ES_TCA_24h

General information and causes The PDF near-end performance monitor counter
ES exceeded the provisioned threshold during a
3.4.35 PPI-NE_SES_TCA_15m/24h
Alarm name PPI-NE_SES_TCA_15m, or

PPI-NE_SES_TCA_24h

CHAPTER 3
Troubleshooting
3.4.36 PPI-NE_UAS_TCA_15m/24h
Alarm name PPI-NE_UAS_TCA_15m, or

PPI-NE_ UAS_TCA_24h
3.4.37 RS-BBE_TCA_15m/24h
Alarm name RS-BBE_TCA_15m, or RS-BBE_TCA_24h

General information and causes The RS near-end performance monitor counter
3.4.38 RS-ES_TCA_15m/24h
Alarm name RS-ES_TCA_15m, or RS-ES_TCA_24h


CHAPTER 3
Troubleshooting
General information and causes The RS near-end performance monitor counter ES

3.4.39 RS-SES_TCA_15m/24h
Alarm name RS-SES_TCA_15m, or RS-SES_TCA_24h

3.4.40 RS-UAS_TCA_15m/24h
Alarm name RS-UAS_TCA_15m, or RS- UAS_TCA_24h


CHAPTER 3
Troubleshooting
3.5 Security Alarms
The security alarms are listed in the following sub-chapters.
3.5.1 Account_Expired_Disabled
Alarm name Account_Expired_Disabled

Alarm object NE
General information and causes This alarm is generated because:
A specific account has reached its configured
expiration date
Account has been disabled due to SNMPv3
error detection
1 If the account has expired - enable the account using the FLEXR L and set a new
expiration date.
2 If the account was automatically disabled by SNMPv3 - verify the security log for reason
of account suspension and if desired re-enable the user.
3.5.2 Log_Is_Full
Alarm name Log_Is_Full

Alarm object NE
General information and causes Security log for tracking security and configuration
related events has reached its maximum number
of entries. All entries past this point will either be
dropped or replace earliest entries.
1 Upload the log file to a PC or storage device to empty space for more log files.
2 Increase the size of security file log using the FLEXR L.
3.5.3 Log_Occupancy_Threshold_Reached
Alarm name Log_Occupancy_Threshold_Reached

Alarm object NE

CHAPTER 3
Troubleshooting
General information and causes Security log for tracking security and configuration
related events has reached the user defined
threshold (default 80%).
1 Upload the log file to a PC or storage device to empty space for more log files.
2 Increase the size of security file log using the FLEXR L.
3.5.4 Unauthorized_Access_Attempt
Alarm name Unauthorized_Access_Attempt

Alarm object NE
General information and causes The SNMP engine detects unauthorized access to
the system.
1 Track down the source of the attempt.
2 In the FLEXR L, go to the User Administration window by selecting NE Security > NE
User Management. Clear the alarm manually by right-clicking the desired user and
selecting Reset Unauthorized Access Counter from the context menu.
3.5.5 Unsuccessful_Logins_Exceeded
Alarm name Unsuccessful_Logins_Exceeded

Alarm object NE
General information and causes Five or more unsuccessful login attempts for the
same user account.
1 In the FLEXR L, go to the User Administration window by selecting NE Security > NE
User Management. Check the desired user or user who exceeded the maximum
numbers of login attempt (which is 5 by default). Re-enable the user by right-clicking the
user and selecting Enable from the context menu or click Modify and deselecting the
check box for Account is disabled in the Modify User window.

CHAPTER 4
Common Incorrect Ethernet Configuration Cases
CHAPTER 4

CHAPTER 4
This chapter provides some common incorrect Ethernet configuration cases, which the
customer should avoid when setting up the product in the network. Ethernet data cards
include the 8 x GE/T, 1 x 10 GE/T, 6 x GE + 4 x FEGE/A, and 1 x 10 GE + 10 x GE/L2 cards.
4.1 Ethernet Traffic Frame Loss
The incorrect configuration described in this chapter is only applicable to 6 x

i GE + 4 x FEGE/A, and 1 x 10 GE + 10 x GE/L2 cards, but not to the other
Ethernet cards (i.e., 8 x GE/T and 1 x 10 GE/T).
Ethernet is based on blocks of frames (also called packets) to transmit the traffic (a series of
data flow). The loss of frame can pose a negative impact on the data (e.g. video or audio)
being communicated. Incorrect configuration of the 6 x GE + 4 x FEGE/A, and 1 x 10 GE +
10 x GE/L2 cards will cause frame loss for Ethernet traffic.
Figure 4-1 shows the topology in which this case may occur..
Description for the incorrect configuration:
There is a 1000 Mbps bandwidth connection between port B and port C.
Port A receives 100 Mbps of untagged frame traffic from the egress of the counterpart
equipment.
Port B is configured as Tag mode.
If port A receives 1000 Mbps untagged frames traffic from the egress of the counterpart
equipment, an additional Port VLAN Identifier (PVID) (with a length of four bytes) will be
added into the traffic. It will cause congestion in the egress direction of port B. Frame
loss will occur on port B if flow control is not enabled on port A.
At Port A At Port B
1) Flow control: disabled 1) Tag mode: Tag
2) Untagged frame received
A B C D
1000 Mbps Traffic 1000 Mbps Traffic 1000 Mbps Traffic

1 x 10GE + 10 x GE/L2 1 x 10GE + 10 x GE/L2
Card X Card Y
Frame Loss
Figure 4-1 Topology of Traffic Frame Loss Scenario
There are two methods to solve the frame loss problem in this situation:
Change tag mode from Tag to Untag on port B, or
Enable flow control on port A.
For more information on configuring tag mode and flow control, refer to the
Configuring LAN port properties and Configuring WAN port properties sections
of the FLASHWAVE 4570 Operating Manual.

CHAPTER 4
4.2 Ethernet Traffic Block
The incorrect configuration described in this chapter is only applicable to 6 x

i GE + 4 x FEGE/A, and 1 x 10 GE + 10 x GE/L2 cards, but not to the other
Ethernet cards of 8 x GE/T and 1 x 10 GE/T.
Traffic block or traffic congestion occurs when incoming data exceeds the specified capacity
of the transmission channel.
The following incorrect configuration will cause traffic to be blocked if the 6 x GE + 4 x
FEGE/A, or 1 x 10 GE + 10 x GE/L2 card has been used for Ethernet traffic.
Figure 4-2 shows the incorrect configuration topology.
Description for the incorrect configuration:
There is a 1000 Mbps bandwidth connection between port B and port C.
Port A and port D receive 1000 Mbps of untagged frame traffic from downstream.
The flow control and tag mode are configured as shown in table below
At Port A At Port A At Port C At Port D

1) Flow control: disabled 1) Flow control: enabled 1) Flow control: enabled 1) Flow control: disabled
2) Tag mode: Tag 2) Tag mode: Untag 2) Tag mode: Untag 2) Tag mode: Tag
A B C D
Pause Frame
1000 Mbps Traffic 1 x 10GE + 10xGE/L2 1000 Mbps Traffic 1000 Mbps Traffic
1 x 10GE + 10xGE/L2
Card X Card Y
Pause Frame
Figure 4-2 Topology of Traffic Block Scenario
Port Flow Control Tag Mode

Port A Disabled Tag
Port B Enabled Untag
Port C Enabled Untag
Port D Disabled Tag
Table 4-1 Incorrect Configuration of Traffic Block Scenario
If this configuration has been used to set up the product in the network, and the traffic rate
reaches close to 1000 Mbps, pause frames (a frame used by flow control to tell the opposite
port to stop transmitting traffic) will be sent between port B and C bidirectionally.
Consequently, all bidirectional traffic between port B and port C will be blocked except pause
frames themselves. This can cause bidirectional traffic block triggered by the pause frame.
There are several methods to recover the traffic from such a situation:

CHAPTER 4
It is highly recommended to configure the same tag mode (all tagged or all untagged) on
all ports, and then remove and insert the Ethernet/optical cables for both port A and port
D to reset and activate this change. Alternatively, the user can also reset and activate
this change from the FLEXR L software:
1. Right-click the corresponding LAN port from the FLASHWAVE 4570 Chassis View.
Select LAN Port Property Configuration from the context menu.
2. In the LAN Port Property Configuration window, select Disable from the Admin
mode drop-down list. Click Apply. Click Yes and then click OK in the
Confirmation window to confirm the settings.
3. Select Enable from the Admin mode drop-down list. Click Yes and click OK in the
Confirmation window to confirm the settings.
4. The user needs to repeat the above mentioned steps for each port (i.e., port A and
D).
Disable the flow control on port B and port C and then remove and insert the Ethernet
cables for both port A and port D to reset and activate this change. Alternatively, the user
can also reset and activate this change from the FLEXR L software. Refer to procedures
in method one as described above.
This method can cause traffic frame loss. Refer to Chapter 4.1 for details.
Enable the flow control on the port A and port D, and make sure that flow control is also
enabled on the downstream systems connected, and then remove and insert the
Ethernet cables for both port A and port D to reset and activate this change. Alternatively,
the user can also reset and activate this change from the FLEXR L software. Refer to
procedures of method one as described above.
4.3 Prevention of Loobback on Data Card
Loopbacks are created when the incoming path and outgoing path which are supposed to be
independent on each other are arbitrarily connected for testing purpose or by accident.
Loopback can happen on all Ethernet cards (8 x GE/T, 1 x 10 GE/T, 6 x GE +

i 4 x FEGE/A, and 1 x 10 GE + 10 x GE/L2).
Users should establish a loopback free topology of layer 2 card transmission because,
otherwise, a loopback may cause flooding and massive congestion in the network.
For layer 2 cards, a loopback (e.g., on the same WAN port via CC) on any LAN or WAN port
will cause failure to the layer 2 functionality. For example, it may cause broadcast storm,
traffic blockage, or frame duplication. To restore the layer 2 functionality, the user should
avoid the following three actions that lead to loopback.
A loopback between the transmitter and receiver on the same LAN port via cable or fiber.
This will cause a loopback in which, in an enclosed circle, the transmitter will
continuously send message to a receiver.
A loopback created by a cross-connection between source and sink on the same VC.
This will create a loopback on the WAN port.
Enabling the loopback function on any SDH port, which contains cross-connection(s) to
any layer 2 card WAN port(s).

CHAPTER 4
Figure 4-3 shows a loopback on the WAN port by creating a cross-connection between
source and sink in the same Virtual Container (VC) to WAN port 1.
Enabling Multiple Spanning Tree Protocol (MSTP), which is supposed to

i create a loopback free network, eliminates the loopback on 1 x 10GE + 10 x
GE/L2 card, but not the others.
WAN Port CC Card
VC Source
VC Sink
Figure 4-3 Loop on WAN Port
For more information about the management of loopback, refer to the Testing
loopback and Managing synchronization section of the FLASHWAVE 4570
Operating Manual (OMN).
4.4 Pause Frame for Layer 2 Card
The function of the pause frame is to request the network element which is sending frames
to stop transmitting frame for a period of time.
The pause frame will influence transmission of all frames, including protocol frames (such as
protocol frames in GARP VLAN Registration Protocol (GVRP), Link Aggregation Control
Protocol (LACP), and MSTP). If there are lots of pause frames repeatedly received in a short
time, the egress traffic may be blocked completely (a situation as described in Subchapter
4.2). In this case, protocol frames will also be blocked, which may lead to protocol interaction
failure. To restore the protocol interaction in this case, the congestion condition should be
eliminated (e.g., by reducing the amount of traffic flow or enlarging the bandwidth) or, as an
alternative, the flow control should be disabled.
The impact of pause frame on different protocol varies because some

i protocols are more tolerant to protocol frame than others.
For more information on configuring flow control, refer to the Configuring a

Layer 2 LAN port section of the FLASHWAVE 4570 Operating Manual (OMN).
4.5 Default VLAN ID Warning for Layer 2 Card
VLAN ID 1 is the default VLAN ID for all ports. GVRP cannot automatically register ports to
VLAN ID 1 for management and security reasons. As a result, the network administrator
should manually configure ports in VLAN ID 1, even though the GVRP function is enabled.

CHAPTER 4
For more information on managing GVRP, refer to the Managing GARP

VLAN registration protocol section of the FLASHWAVE 4570 Operating
Manual.
For more information about manual configuration of VLAN, refer to the

Managing VLAN section of FLASHWAVE 4570 Operating Manual.
4.6 VCG Bandwidth Configuration Reminder for Ethernet Cards
The following description is applicable to LCAS mode and is not applicable to

i NON-LCAS mode (i.e. when LCAS is disabled).
On the Ethernet cards, VCGs can be used to configure the bandwidth of a port. The user can
configure the bandwidth by establishing a symmetrical VCG arrangement between sink and
source (in other words, the bandwidth configured is always equal between source and sink
of one VCG) to create a port that has the same transmitting and receiving capacity. This
symmetrical VCG arrangement is done in the bidirection mode, which is the default mode.
In the bidirection mode, the bandwidth configured for either one of the sink and
i source will be applied to the other as well automatically.
The user can also create a port that has different transmitting and receiving capacity by
establishing an asymmetrical VCG arrangement between sink and source (in other words,
the bandwidth configured can be different between source and sink of one VCG). This
asymmetrical VCG arrangement is done in the unidirection mode.
This flexibility of symmetrical and asymmetrical VCG arrangement makes asymmetrical
bandwidth configuration possible for one VCG.
For more information on setting the bidirection and unidirection and how to
manage VCG, refer to the Managing virtual concatenation groups section of
FLASHWAVE 4570 Operating Manual.
Caution
In unidirection mode, user should not leave either source or sink configuration
! unassigned with any VC. If there is no bandwidth assigned for either source or
sink of one VCG, the traffic will be blocked.

CHAPTER 5
CHAPTER 5
Card Replacement

CHAPTER 5
This section contains instructions for removing a faulty card and replacing it with a spare of
the same type
5.1 General Guideline for Card Replacement
The general instructions are as follows:

When replacing cards, all the operations must comply with the FLASHWAVE 4570
Safety Instructions.
When replacing the optical interface cards, it is essential to check and record the optical
transmitting power, using an optical power meter, before the cards are returned to
service.
Cards can be removed from or inserted in the slots while they are alive. The lever on the
card must be opened before the card is removed and be closed after the card is inserted.
Before replacing a card which is suspected of being faulty, try to reactivate the system
by means of a hardware reset (e.g. removing and re-inserting the card). Never do this
when the red FAULT Light Emitting Diode (LED) on the card is illuminated.
The card setup procedure can only start once the card has been mated properly with its
backplane connector. Make sure that the two levers of the card secure the card in the
shelf properly.
After a card has been replaced, the card status must be confirmed on the FLEXR L.
Running the system without the Cross Connection (CC) card is prohibited. Make sure
that the CC cards have been mounted properly before the system is powered on. If the
user has removed the CC card (on either working or protection CC cards), a cold reboot
is mandatory after re-installing it.
i All optical fibers, transmitters, and ports are classified as hazard level 1 as
defined by EN 60825-1/ IEC 60825-1. Nevertheless, in view of possible
malfunction, laser transmission systems which contain optical amplifier modules
are classified as hazard level 1M. To avoid damage to health, the user must
observe the regulations regarding protection against radiation from laser devices
(EN 60825-1/IEC60825-1).
i The user has to wait about 10 to 30 minutes for the NE to complete rebooting
For the detailed procedures on how to execute many of the instructions described
in this chapter, refer to the FLASHWAVE 4570 Installation and Test Manual
(ITMN), Commissioning Manual (COMN), and Operating Manual (OMN)
5.2 Replacing SC Card
Replacement of the SC card requires special care since it contains a field-replaceable CF

card used for persistent storage of the MIB and system software.

CHAPTER 5
Caution
The SC card replacement instructions described in the following subchapters
! presume all the SC cards is loaded with the same version of NE software
(Release 4.2).
Caution
When an SC card is removed from the single SC system, the management
! system will lose connectivity to the NE. During this time, the management
interface is not functional.
Before the replacement, the MIB file should be prepared in a PC. Follow the procedures
given in Chapter 5.2.1.
Also if the failure is present in the active SC card, and/or the active CF card (in the active SC
card) of the 1+1 redundant SC system, additional procedure is required to switch the SC
card to the standby side before the replacement procedure. Refer to Chapter 5.2.2.
The SC card and/or CF card replacement procedures vary depending on the failure scenario
as follows.
SC card failure: see Chapter 5.2.3
CF card failure: see Chapter 5.2.4
Both the SC and CF cards fail: see Chapter 5.2.5.
i Unless the CF card is damaged, when replacing the old SC card with a new SC
card, it is recommended to remove the original CF card in the old SC card and
put it into the new SC card to ensure the data information for the new card is
consistent with the peer SC card.
The following instructions include the FLEXR L operation. For the detailed
instructions on how to use the FLEXR L for the specific operation, refer to
FLASHWAVE 4570 Operating Manual (OMN).
5.2.1 MIB Preparation before Replacement
Before the SC card replacement, the following preparation should be done:

1 Connect a PC to the new SC card via the console port and connect the PC to the
System Interface with Engineering Order Wire (SI-E) or System Interface (SI) card via
the MGMT port.
2 The Hyper Terminal should be installed and properly set on the PC
Refer to The FLASHWAVE 4570 Commissioning Manual (COMN).
3 A File Transport Protocol (FTP) server program should be installed and properly set on
the PC. For convenience, it is suggested to use the built-in FTP server on Windows XP.
To activate this server, follow the procedures below:
Insert Windows XP Service Pack 2 (SP2) installation CD into CD/DVD drive.
To install the FTP server, select Start > Control Panel > Add/Remove Programs >
Add/Remove Windows Components.
Select the Internet Information Service (IIS) check box. Click Details to
open the Internet Information Service (IIS) window.

CHAPTER 5
Select the Common Files and File Transfer Protocol (FTP) Service check
boxes and click OK.
To configure the FTP server, select Start > Control Panel > Administrative Tools >
Internet Information Service > XXXX (local computer) > FTP Sites > Default FTP Site.
Right-click the Default FTP Site item and select FTP properties to open the
Default FTP Site Properties window. It is suggested to select the Allow
Anonymous Connections check box.
Ensure FTP Site Directory is where the MIB and software load files are
located. By default, the location is at C:Inetpubfproot.
After the above procedures are completed, the operator should verify the FTP server by
clicking Start > Run.
Enter ftp 127.0.0.1 to open the command prompt.
Enter anonymous as the user name and any words as passwords.
Enter dir to check the software load file and MIB file in the folder.
4 The unzip software like winzip or winrar should be installed on the PC.
5 The boot image file (e.g., <SC.bin>) and software load file (e.g.,
<PBm1r42bxxx.bld>) should be saved in the FTP server user directory.
For the boot image file and software load file, please contact Fujitsu Technical Support.
6 The MIB file saved by the FLEXR L with the extension .mib should be changed into
a .zip file and unzipped to the local working directory on the PC.
The unzipped MIB file package on the PC includes the following files:
%Local_working_drive%<ghead.txt>
%Local_working_drive%<headfile.txt>
%Local_working_drive%ne*.*
%Local_working_drive%gmpls*.*
%Local_working_drive% specifies the drive letter of the hard disk drive containing
the local working directory on the PC.
5.2.2 Switching SC before Replacement (for Redundant SC System)
The procedure in this subchapter is only applied when the failure is present in the active SC
card or the active CF card (in the active SC card) of the 1+1 redundant SC system.
When the FLASHWAVE 4570 is equipped with two SC cards for SC 1 + 1 protection, in the
event of the active card failure, the automatic switching is executed from the active to the
standby to offer system protection and system stability. With this feature, the user has time
to isolate and troubleshoot faults of an SC card encountering problems without losing control
of the system.
Two switch modes exist when the system is equipped with two SC cards: one is the
automatic switch, the other is the manual switch. Automatic switch is triggered by faults in
the active SC card, while the manual switch is triggered by the operators command from the
FLEXR L and usually used to conduct the system upgrading or testing.

CHAPTER 5
i Not all faults will trigger SC 1 + 1 switch and they include cases such as
mechanical breakdown, software version upgrading, malfunction of individual
integrated circuit, etc.
i If the ACT LEDs on both SC cards are off, refer to Chapter 5.3.
The following procedures only apply to the replacement of the active SC card, CF card (in
the active SC card), and both the active SC card and its CF card.
1. Using the FLEXR L, perform a switch request for the active SC cards.
2. If Step 1 does not work, using the FLEXR L warm reboot the active SC card.
3. If both Step 1 and Step 2 do not work, or if the FLASHWAVE 4570 cannot be managed
by the FLEXR L, remove the active SC card to activate the switching to the standby SC
card eventually.
5.2.3 SC Card Failure
To replace the SC card, complete the following steps:

1 Remove the faulty SC card from the slot.
2 Remove the CF card from the faulty SC card.
Refer to The FLASHWAVE 4570 Installation and Test Manual (ITMN).
3 Insert the original CF card into a new SC card.

4 Insert the new SC card in the slot. The system will automatically start rebooting.
5 During the system reboot, press to stop the boot process when the Hyper Terminal
shows the countdown 5 4 3 2 1 ... .
Caution If the boot process is not stopped in time and the system comes into the
normal startup process, the NE configuration may be lost and the traffic may
! be interrupted. If this happens, remove the SC card immediately and
execute Steps 2 and 3 above again.
The Boot Mode window is opened in the Hyper Terminal.
6 Press <f> to enter the Flash Commands window.
7 Press <1> to format the board flash in the SC card.
8 After the formatting finishes, press <x> to return to the Boot Mode window.
9 Press <0> to enter System Maintain window
10 Press to check the current boot image version and ensure the version is 2.2.2.2.
11 If it is not version 2.2.2.2, download the boot image according to Chapter 5.2.6.
12 Press <r> to reboot the system and press <y> to confirm.
13 After the system reboot finishes, verify the software version is correct through the
FLEXR L.

CHAPTER 5
Refer to The FLASHWAVE 4570 Operating Manual (OMN).
PROCEDURE COMPLETE!
5.2.4 CF Card Failure
To replace the CF card, complete the following steps:

1 Remove the SC card.
2 Remove the faulty CF card from the SC card.
3 Insert a new CF card into the SC card.

4 Insert the SC card with the new CF card. The system will automatically start rebooting.
7 Press <2> to format the CF in the SC card.
9 Press <0> to enter the System Maintain Window.
11 If it is not version 2.2.2.2, download boot image according to Chapter 5.2.6.
12 Press <r> to reboot the system and press <y> to confirm.
13 After the system reboot finishes, verify the software version is correct through the
FLEXR L.
PROCEDURE COMPLETE!
5.2.5 Both SC and CF Cards Fail
To replace the SC and CF card, complete the following steps. In case the user is not sure
whether the failure is caused by the SC card or CF card, follow this procedure.
1 Remove the faulty SC card.

CHAPTER 5
2 Insert a new SC card with a new CF card.

The system will automatically reboot.
5 Press <1> to format the board flash in the SC card.
6 Press <2> to format the CF in the SC card.
8 Press <r> to reboot the system, and press <y> to confirm the operation.
! be interrupted. If this happens, remove the SC card immediately and insert
it. Then again start with Step 9 above again.
10 Press <0> to enter the System Maintain window.
12 If it is not version 2.2.2.2, download boot image according to Chapter 5.2.6.
13 Download the MIB according to Chapter 5.2.8.
14 Press <c> to enter Command Mode window.
15 Download the software load from the PC to the SC card by setting the FTP configuration.
Refer to Chapter 5.2.7.
16 In the boot area, input @ and press <Enter> to reboot the system.
17 Because there is only one SC card is in use, upload the MIB from the PC to the SC card
by executing the following steps.
18 In the boot area, input @ and press <Enter> to reboot the system.
14 After the system reboot finishes, verify the software version is correct through the LCT.
PROCEDURE COMPLETE!
5.2.6 Downloading Boot Image
To download the boot image from the PC to the SC card, complete the following steps:
1 Launch the Boot Mode window in the Hyper Terminal by pressing during the
system reboot when the Hyper Terminal shows the countdown 5 4 3 2 1 ...

CHAPTER 5
2 Press to enter the IP Configuration window.

3 Press <1> and set the boot device as mottsec.
4 Press <2> and enter the NE Ethernet Internet Protocol (IP) address.
i Ensure the IP address is unique and not in conflict with any other IP address and
sub-network in the DCN environment.
5 Press <3> and enter the NE Ethernet IP mask address.

6 Press <4> and enter the PC IP address. In order to communicate with the NE, the PC IP
address needs to be in the same sub-network as the NE Ethernet IP address.
7 Press <7> and enter the FTP user account name which is used for the NE to login into
the FTP server on the PC.
The PC acts as an FTP server. Refer to Step 3 in Chapter 5.2.1 for the FTP
server setup
8 Press <8> and enter the FTP password which is used for the NE to login into the FTP
server.
9 Press <9> and type up to enable the uplink port.
10 Press <x> to return to the Boot Mode window.
11 Press <0> to enter the System Maintain window.
12 Press <f> to enter the Boot image window.
13 Enter the corresponding boot image file name (e.g., <sc.bin>) and press <Enter>.
The File Size prompt is displayed.
14 When all items show OK, the boot image file is downloaded to the SC card.
Press <Enter> to return to the System Maintain window.
15 Press <x> to return to the Boot Mode window.
16 Press to enter the IP Configuration window.
17 Press <1> to modify the boot device as auto.
18 Press <9> and type down to disable the uplink port.
19 Press <x> to return to the Boot window.
PROCEDURE COMPLETE!
5.2.7 Downloading Software Load
To download the boot image from the PC to the SC card, complete the following steps:
1. Launch the Boot Mode window in the Hyper Terminal by pressing during the
2. Press to enter the IP Configuration window.
3. Press <1> and set the boot device as mottsec.
4. Press <2> and enter the NE Ethernet Internet Protocol (IP) address.
5. Press <3> and enter the NE Ethernet IP mask address.

CHAPTER 5
6. Press <4> and enter the PC IP address. In order to communicate with the NE, the PC
IP address needs to be in the same sub-network as the NE Ethernet IP address.
7. Press <7> and enter the FTP user account name which is used for the NE to login into
the FTP server on the PC.
The PC is an FTP server. Refer to Step 3 in Chapter 5.2.1 for the FTP server setup.
8. Press <8> and enter the FTP password which is used for the NE to login into the FTP
server.
9. Press <9> and type up to enable the uplink port.
10. In the IP Configuration window, press <6> and enter the corresponding software load
file name (e.g., <PBm1r40bxxx.bld>).
11. Press <x> to return to the Boot Mode window.
12. Press <c> to enter the Command Mode window and type @ to download the load.
PROCEDURE COMPLETE!
5.2.8 Downloading MIB
To download the MIB from the PC to the SC card, complete the following steps:
1. Launch the Boot Mode window in the Hyper Terminal by pressing during the
2. Press to enter the IP Configuration window.
3. Press <2> and enter the NE Ethernet Internet Protocol (IP) address.
4. Press <3> and enter the NE Ethernet IP mask address.

5. Press <4> and enter the PC IP address. In order to communicate with the NE, the PC
IP address needs to be in the same sub-network as the NE Ethernet IP address.
6. Press <9> and type up to enable the uplink port.
7. Press <x> to return to the Boot Mode window.
8. On the PC, select Start > All Programs > Accessories > Command Prompt menu
item.
The Command Prompt window is opened.
9. Use the following commands:
cd To enter the local working directory. The default location for use with the
FLEXR L FTP server is <c:inetpubftproot>.
ftp To login the NE FTP server using the NE Ethernet IP address by typing
ftp followed by the IP address of the NE Ethernet FTP address.
The NE act as FTP server.
10. Enter the FTP user account name and password for the PC to login to the FTP server
on the NE.
The NE acts as an FTP server.
The default user name is root.

CHAPTER 5
The default password is <Enter>.

11. Use the following commands:
cd /cfg/ To enter the default MIB directory, named cfg.
mkdir mib To create the sub-directory of cfg, named mib.
cd mib To enter the directory, /cfg/mib.
mkdir active To create the sub-directory named active in folder mib,.
cd active To enter the directory, /cfg/mib/active.
bin To set the binary file transport mode.
prom To turn off the interactive mode.
put ghead.txt To upload the file, ghead.txt, from the local working root
directory to the directory, /cfg/mib/active.
put headfile.txt To upload the file, headfile.txt, from the local working root
directory to the directory, /cfg/mib/active.
mkdir ne To create the sub-directory named ne in the folder active,.
cd ne To enter the directory, /cfg/mib/active/ne.
lcd ne To enter the local working
directory, %Local_working_drive%\ne.
mput *.* To upload all the files from the local working
directory, %Local_working_drive%\ne, to the directory,
/cfg/mib/active/ne.
dir To verify all the files have been uploaded successfully.
cd .. To return to the directory, /cfg/mib/active.
mkdir gmpls To create the sub-directory named gmpls in the folder active,.
cd gmpls To enter the directory, /cfg/mib/active/gmpls.
lcd .. To return to the local working root directory.
lcd gmpls To enter the local working
directory, %Local_working_drive%\gmpls.
mput *.* To upload all the files from the local working
directory, %Local_working_drive%\gmpls, to the directory,
/cfg/mib/active/gmpls.
dir To verify all the files have been uploaded successfully.
pwd To check the path.
bye To logout the FTP server on the NE.
The MIB file package on the NE includes the following files:
/cfg/mib/active/<ghead.txt>
/cfg/mib/active/<headfile.txt>
/cfg/mib/active/ne/*.*
/cfg/mib/active/gmpls/*.*
PROCEDURE COMPLETE!

CHAPTER 5
5.3 Troubleshooting SC 1+1 Common Problems
This section describes the most commonly encountered problems of the SC 1 + 1

mechanism. SC card switching failure may fall into two categories: one is the manual switch
failure and the other is automatic switch failure. This section also describes what the user
should do to troubleshoot when both ACT LEDs are off on both SC cards.
5.3.1 Both ACT LEDs are Off
If the ACT LEDs of the both SC cards are off, please check whether the FLEXR L is still
online or not.
If the FLEXR L is online, perform a switch request for the active SC card. To determine if
an SC card is active or not, the user needs to open the SC 1+1 Protection window by
selecting Configuration > SC 1+1 Protection and checking at the Active SC area to
see if any SC card is available. If there is no SC card being displayed in the Active SC
area, the user should perform a warm reboot. If this switch command still does not work,
perform a warm reboot to both the active and standby SC cards.
If the FLEXR L is offline, remove and insert both SC cards so that the FLEXR L can
automatically log in again.
i The time needed for the FLEXR L to go online may be as long as 15 minutes
depending on the system configuration.
5.3.2 Manual Switch Failure
If the manual switch between the active and standby SC fails, check the SC status area of
the SC 1+1 Protection window. Make sure the settings and parameters are set as
illustrated in the figure below.
Figure 5-1 SC 1+1 Working Status

CHAPTER 5
There are several parameters that the user should pay attention to and double check in the
SC 1+1 Protection window.
Active SC: It can be SC1 or SC2 depending on which card is active at the moment.
Last switch reason: The user should ensure it is in No Request state before manual
switch.
Switch request: It indicates whether the user or system has issued a command to
switch between SC cards. The user will not be able to perform a manual switch if this
area shows any other parameter than No Request.
In the SC status area, the user should check:
Slot: The slot where each SC card is located.
Role: Shows which card is in Active state and which card is in Standby state.
Present: Tells the user either of the slots contains a SC1 card or SC2 card and shows
the card is in place and works properly.
Latch: There are two states, Close or Open.
Close: The latch of the card is closed. The user should ensure the latch of the
card is closed for normal operation.
Open: The latch of the card is open. When the latch is opened, control system
will switch to another SC card.
The failure to perform a manual switch can result from switch priority rules. If there are
multiple switches performed at the same time, the switch type with higher priority will take
precedence over the switch type with lower priority. In other words, if manual switch and
automatic switch are executed at the same time, manual switch will not be available for
users to perform because automatic switch takes the priority. Table 5-1 lists the priority of
each of the available switch types.
Switch Type Scenario Priority

Automatic switch SC card failure 1
Latch switch SC card latch is opened 2
Manual switch Performing switch command from 3
FLEXR L
Table 5-1 Switch Priority of SC 1+1
If the above settings in the SC 1+1 Protection window are correct, but automatic switch still
fails, follow the procedure described in Chapter 5.3.3.
5.3.3 Automatic Switch Failure
Caution Switch failure in the SC 1 + 1 mechanism can cause interruption in system

control operation and monitoring and also it can disable the FLEXR L
! operation.
If the automatic switch between the active and standby SC fails and if the FLEXR L is still
online, execute the following procedure:
1. Repeat checking the parameters in the SC 1+1 Protection window and ensure that
both Active and Standby cards are allocated and they are present. Check that the

CHAPTER 5
Latch is also in a Close state and the Switch request shows No request. Make sure
the settings are configured as listed in Table 5-1.
2. If the automatic switch still does not work, check system alarms and troubleshoot them
based on the instructions listed in CHAPTER 3. SC related alarms include:
SC_SW_Version_Mismatch
Communication_Fail
3. If the automatic switch still does not work, cold reboot both SC cards.
i SC card failure may cause the FLEXR L to go offline.
4. Contact Technical support for further assistance if the corrective procedure above fails.
5.4 Replacing CC Card
Each NE has CC cards, which function as the cross-connection and timing management
controller. Replacement of the CC card requires special care since it deals with all traffic of
the NE.
To replace the CC card, complete the following steps:
1. Before replacing the CC card, verify that the CC card to be replaced is not active via the
FLEXR L.
i When the working CC card fails, the traffic will switch to the protection card
automatically.
2. Remove the faulty CC card.

3. Insert a new CC card.
4. If the CC card is switched manually in Step 1, clear the switch request command set in
Step 1 via the FLEXR L.
i Take at least three-minute interval between the first CC card switch in Step 1 and
the second CC card switch in Step 4 to ensure no traffic hit.
PROCEDURE COMPLETE!
5.5 Replacing Fan Unit
FLASHWAVE 4570 shelf is equipped with two fan units to cool the system. Replacement of
the fan unit requires special care.
Observe the following rules:
The whole fan unit must be replaced even if only one of the fans in the unit fails.
The system cannot work with no fan units.

CHAPTER 5
The system can still work normally for 16 hours when only one fan unit fails and that the
failed unit is still inserted in the NE.
The system cannot work when either one of fan units is absent for more than two
minutes. Complete exchanging the faulty fan unit within two minutes.
Detailed instructions for replacing the fan unit can be found in the FLASHWAVE
4570 Installation and Test Manual (ITMN).
5.6 Replacing Filter Unit
FLASHWAVE 4570 shelf is equipped with one filter unit to protect the system from the
environmental dust or other airborne contaminants. Replacement of the fan unit requires
special care.
Observe the following rules:
The filter unit replacement must be treated as a periodic maintenance procedure to
ensure that the fans are able to sustain optimum shelf operating temperature.
It is recommended to clean the filter unit every two months, otherwise the efficiency of
the fan unit may be reduced.
The filter unit can be cleaned by water, but must be dry when placed back.
The filter unit must be placed back within 24 hours, otherwise the system may be
polluted by the dust.
Detailed instructions for replacing the fan unit can be found in the FLASHWAVE
4570 Installation and Test Manual (ITMN).

CHAPTER 6
MIB Switching
CHAPTER 6
MIB Switching

CHAPTER 6
MIB Switching
This section contains instructions for switching between the active MIB and the backup MIB.
Normally the MIB is saved in the active Board Flash (BF) in the SC card. There are three
additional copies for backup purposes, including:
Active CF
Backup CF
The MIB collects:
Data managed by the external interfaces
Data used in the cards settings
Data used by the SC card for internal activities
MIB switching procedures vary, depending on the following different scenarios:
The data configuration is different between the old and new MIB.
The data configuration is the same between the old and new MIB.
6.1 Switching MIBs with Different Configuration
To switch between the two MIBs whose data is different from each other, complete the
following steps using the FLEXR L:
1. Upload the MIB of the old configuration from the NE to the local PC to backup the old
configuration.
2. Download the MIB of the new configuration from the local PC to the NE.
3. Switch the new MIB into the active MIB.
4. Activate the new configuration in the MIB in the following two methods:
Method 1
Cold reboot the NE to activate all the new configuration in the MIB.
Caution All traffic will be dropped while the NE is cold rebooting.
!
Method 2
1. Warm reboot the NE to activate the configuration in the MIB except the new
data configuration.
Caution The Ethernet traffic related to the new data configuration will not be normal
! after the NE warm reboots.
2. Cold reboot all the Ethernet cards related to the new data configuration to
activate the new data configuration.
Caution
The Ethernet traffic will be dropped while the card is cold rebooting.
!
PROCEDURE COMPLETE!

CHAPTER 6
MIB Switching
6.2 Switching MIBs with Same Configuration
To switch between the two MIBs which contain the same data, complete the following steps:
configuration.
2. Download the MIB of the new configuration from the local PC to the NE.
3. Switch the new MIB into the active MIB.
4. Warm reboot the NE to activate the new configuration in the MIB.
PROCEDURE COMPLETE!
6.3 Switching MIBs in Redundant SC System
To switch the two MIBs on the 1 + 1 redundant SC system, complete the following steps via
FLEXR L:
configuration.
It is recommended that the user should empty the MIB before performing
i downloading.
2. In the Download tab (Configuration > NE > MIB Management), configure all the
settings in the Download page to download the MIB of the new configuration from the
local PC to the NE.
3. Configure all the settings in the Synchronize page to copy the new MIB from the Active
SC card to the Standby SC card.
4. Configure all the settings in the Switch MIB on standby SC page to switch the new
MIB into the active MIB for the Standby SC.
5. Configure all the settings in the Switch MIB on active SC page to switch the new MIB
into the active MIB for the Active SC.
6. Configure all the settings in the Reboot NE page to activate the new MIB configuration
for both Active SC and Standby SC.
PROCEDURE COMPLETE!
6.4 MIB Restoration
To reduce complexity of applying MIB restoration with GMPLS feature, it is strongly

recommended that user should backup MIB periodically, especially when there has been any
changes to the call switch status, or network topology, or system configuration.
6.4.1 Restoring MIB Files
There are two ways to restore MIB files:

Upload MIB files through FTP connections.

CHAPTER 6
MIB Switching
When using FTP server to upload MIB files, most of the problems occurred during
replacing SC and CF card, which only one SC card available on the node. The operator
can upload the MIB file onto the node through the FTP server.
For the detailed operation procedure, refer to Chapter 5.2.
Upload MIB files through Element Management.

The most of problem is that the node needs to be restored from one new MIB files.
For the detailed operation procedure, refer to the FLASHWAVE 4570 Operating
Manual (OMN).
6.4.2 Problems Caused by Traffic Status
There are two kind of problems caused by traffics status:

Upload MIB files through FTP connections.
The operator does not need to do anything after the node reboot procedure competed.
The uploaded MIB files are different from file running on the node.
The difference may come from different call information, call status, or call routes, etc.
After uploading MIB file, the operational status of some calls will be switched to disable.
Then the traffic works in the down status. However this result can be avoid.
Please follow the steps below:
1. Open Call Management window in FLEXR L.
2. Query calls with the Operational status of Disable.
3. Delete these calls.
4. Open the LSP Management window.
5. Query the LSPs:
with the Operational status of Disable;
with the LSP status of Error or Failure; or
with the Notify counter is an odd number.
6. Right-click one of these LSPs and select Call in the context menu. The Call
Management window is opened.
7. Delete this LSP related call.
8. Repeat Steps 6 and 7 until all the queried calls are deleted.
9. Warm reboot NE.
10. Wait for 45 minutes to make sure the other NEs have released the resources which
used for those disabled calls.
11. Re-create or re-enable calls needed after MIB restoration.
PROCEDURE COMPLET

CHAPTER 7
Abbreviations
CHAPTER 7
Abbreviations

CHAPTER 7
Abbreviations
AIS Alarm Indication Signal

AU Administrative Unit
BBE Background Block Error
BER Bit Error Rate
BF Board Flash
BOA Booster Optical Amplifier
CC Cross-Connection
CF Compact Flash
COMN Commissioning Manual
CRC Cyclic Redundancy Check
DCC Data Communication Channel
DEG DEGraded
ENV ENVironment
ES Errored Second
EXC EXCessive
FC Fiber Channel
FTP File Transport Protocol
GFP Generic Framing Procedure
GUI Graphical User Interface
HCOC High Capacity Overhead Channel
HOCC High Order Cross Connection
HP High order Path
IP Internet Protocol
LAN Local Area network
LCAS Link Capacity Adjustment Scheme
LCT Local Craft Terminal
LED Light Emitting Diode
LOA Loss Of Alignment
LOF Loss Of Frame
LOM Loss Of Multiframe
LOP Loss Of Pointer
LOS Loss Of Signal
LP Low order Path
ITMN Installation and Test Manual
MAC Media Access Control
MDI Miscellaneous Discrete Input
MIB Management Information Base
MS Multiplex Section

CHAPTER 7
Abbreviations
NE Network Element
OA Optical Amplifier
OMN Operating Manual
PC Personal Computer
PDH Plesiochronous Digital Hierarchy
PLM PayLoad Mismatch
POA Pre-Optical Amplifier
PLL Phase Lock Loop
PPI PDH Physical Interface
QoS Quality of Service
RDI Remote Defect Indication
RFI Remote Failure Indication
RPR Resilient Packet Ring
RS Regeneration Section
SC System Controller
SDH Synchronous Digital Hierarchy
SES Severely Errored Second
SFP Small Factor Pluggable
SI-E System Interface with Engineering Order Wire
SNMP Simple Network Management Protocol
SPI Synchronous Physical Interface
SSM Synchronization Signal Message
TCA Threshold Crossed Alarm
TIM Trace Identifier Mismatch
TLCT Total Loss of Capacity Transmit
TP Terminal Point
TU Tributary Unit
UAS UnAvailable Second
UNEQ UNEQuipped
VCG Virtual Concatenation Group
VCXO Voltage Control Crystal Oscillator
WAN Wide Area Network
XFP 10 Gigabit Small Form Factor Pluggabl

Fw4570 r4.2 Troubleshooting Manual

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Fw4570 r4.2 Troubleshooting Manual

Загружено:

Авторское право:

Доступные форматы

FTDG-H751-D830

FLASHWAVE 4570 RELEASE 4.2

ISSUE 1, JANUARY 2011

Proprietary Rights Notice

Unpublished work and only distributed under restriction.

FLASHWAVE 4570 Release 4.2 FTDG-H751-D830

BEFORE YOU BEGIN

FTDG-H751-D830 FLASHWAVE 4570 Release 4.2

! Important Notice on Product Safety

FLASHWAVE 4570 Release 4.2 FTDG-H751-D830

CHAPTER 1 Preface .......................................................................................................... 1-1

FTDG-H751-D830 FLASHWAVE 4570 Release 4.2

3.2.9 HP-GFP_Loss_of_Frame_Delineation .................................................................. 3-12

FLASHWAVE 4570 Release 4.2 FTDG-H751-D830

3.2.66 RPR-Miscabling_East ........................................................................................... 3-34

FTDG-H751-D830 FLASHWAVE 4570 Release 4.2

3.4.33 PPI-FE_UAS_TCA_15m/24h ................................................................................ 3-55

FLASHWAVE 4570 Release 4.2 FTDG-H751-D830

FTDG-H751-D830 FLASHWAVE 4570 Release 4.2

FLASHWAVE 4570 Release 4.2 FTDG-H751-D830

FTDG-H751-D830 FLASHWAVE 4570 Release 4.2

This Troubleshooting Manual describes fault-clearing procedures to be performed in reaction

1.1 Intended Audience

1.2 Structure of This Document

1.3 Symbols and Conventions

The following symbols and conventions are used in this document:

FLASHWAVE 4570 Release 4.2 FTDG-H751-D830

1.3.1 Symbols Used

1.3.2 Conventions Used

Table 1-1 List of Used Conventions

FTDG-H751-D830 FLASHWAVE 4570 Release 4.2

1.4 History of Changes

Issue Issue date

Table 1-2 History of Changes

FLASHWAVE 4570 Release 4.2 FTDG-H751-D830

FTDG-H751-D830 FLASHWAVE 4570 Release 4.2

FLASHWAVE 4570 alarms are divided into the following categories:

2.1 Equipment Alarms

Table 2-1 lists FLASHWAVE 4570 equipment alarms.

Alarm Name Alarm Message Text

Table 2-1 Equipment Alarms

FLASHWAVE 4570 Release 4.2 FTDG-H751-D830

2.2 Communication Alarms

Table 2-2 lists FLASHWAVE 4570 communication alarms..

Alarm Name Alarm Message Text

FTDG-H751-D830 FLASHWAVE 4570 Release 4.2

Alarm Name Alarm Message Text

FLASHWAVE 4570 Release 4.2 FTDG-H751-D830

Alarm Name Alarm Message Text

Table 2-2 Communication Alarms

2.3 Environmental Alarms

Table 2-3 lists FLASHWAVE 4570 environmental alarms.

Alarm Name Alarm Message Text

Table 2-3 Environmental Alarms

2.4 Quality of Service Alarms

Table 2-4 lists FLASHWAVE 4570 QoS alarms.

FTDG-H751-D830 FLASHWAVE 4570 Release 4.2

Alarm Name Alarm Message Text

FLASHWAVE 4570 Release 4.2 FTDG-H751-D830

Alarm Name Alarm Message Text

Table 2-4 Quality of Service Alarms

2.5 Security Alarms

Table 2-5 lists the FLASHWAVE 4570 security alarms.

Alarm Name Alarm Message Text