Beruflich Dokumente
Kultur Dokumente
FUJITSU LIMITED
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.
FTDG-H750-D830
Issue 1, August 2008
FTDG-H750-D830
Issue 1, August 2008
ii
FTDG-H750-D830
Issue 1, August 2008
Contents
Contents
BEFORE YOU BEGIN.....................................................................................................................i
Important Notice on Product Safety ........................................................................................... 1-2
CHAPTER 1 Preface ............................................................................................................... 1-1
1.1
1.2
1.3
1.3.1
1.3.2
1.4
FTDG-H750-D830
Issue 1, August 2008
Contents
3.2.10
3.2.11
3.2.12
3.2.13
3.2.14
3.2.15
3.2.16
3.2.17
3.2.18
3.2.19
3.2.20
3.2.21
3.2.22
3.2.23
3.2.24
3.2.25
3.2.26
3.2.27
3.2.28
3.2.29
3.2.30
3.2.31
3.2.32
3.2.33
3.2.34
3.2.35
3.2.36
3.2.37
3.2.38
3.2.39
3.2.40
3.2.41
3.2.42
3.2.43
3.2.44
3.2.45
3.2.46
3.2.47
3.2.48
3.2.49
3.2.50
3.2.51
3.2.52
3.2.53
3.2.54
3.2.55
3.2.56
3.2.57
3.2.58
3.2.59
3.2.60
3.2.61
3.2.62
3.2.63
3.2.64
3.2.65
3.2.66
iv
HP-PLM..................................................................................................................... 3-12
HP-RDI...................................................................................................................... 3-12
HP-TIM...................................................................................................................... 3-13
HP-UNEQ.................................................................................................................. 3-13
HP-Virtual_Concatenation_LOA ............................................................................... 3-13
HP-Virtual_Concatenation_LOM............................................................................... 3-14
HP-Virtual_Concatenation_TLCT ............................................................................. 3-14
Link_Failure............................................................................................................... 3-15
Loss_of_Timing_Input............................................................................................... 3-15
Loss_of_Timing_Output............................................................................................ 3-16
LP-DEG..................................................................................................................... 3-16
LP-EXC ..................................................................................................................... 3-16
LP-GFP_Customer_Signal_Failure .......................................................................... 3-17
LP-GFP_Loss_of_Frame_Delineation ...................................................................... 3-17
LP-PLM ..................................................................................................................... 3-17
LP-RDI ...................................................................................................................... 3-18
LP-RFI....................................................................................................................... 3-18
LP-TIM ...................................................................................................................... 3-18
LP-UNEQ .................................................................................................................. 3-19
LP-Virtual_Concatenation_LOA................................................................................ 3-19
LP-Virtual_Concatenation_LOM ............................................................................... 3-19
LP-Virtual_Concatenation_TLCT .............................................................................. 3-20
MS_AIS ..................................................................................................................... 3-21
MS-DCC_Connection_Failure .................................................................................. 3-21
MS_DEG ................................................................................................................... 3-21
MS_EXC ................................................................................................................... 3-22
MS-K1/K2_Mismatch ................................................................................................ 3-22
MS_RDI..................................................................................................................... 3-22
OA_Gain_High .......................................................................................................... 3-23
OA_Input_LOS.......................................................................................................... 3-23
OA_Output_LOS ....................................................................................................... 3-24
OA_Output_Power_High .......................................................................................... 3-24
PPI-AIS ..................................................................................................................... 3-24
PPI-LOF .................................................................................................................... 3-25
PPI-LOM ................................................................................................................... 3-25
PPI-LOS .................................................................................................................... 3-25
PPI-RDI ..................................................................................................................... 3-26
RPR-Exceed_Max_Stations ..................................................................................... 3-26
RPR-Link_Failure_East............................................................................................. 3-26
RPR-Link_Failure_West............................................................................................ 3-27
RPR-Miscabling_East ............................................................................................... 3-27
RPR-Miscabling_West .............................................................................................. 3-27
RPR-Protection_Misconfig........................................................................................ 3-28
RPR-Ringlet0_ReservedA0_Exceeding ................................................................... 3-28
RPR-Ringlet1_ReservedA0_Exceeding ................................................................... 3-28
RPR-Topology_Inconsistent ..................................................................................... 3-29
RPR-Topology_Instability ......................................................................................... 3-29
RS-DCC_Connection_Failure................................................................................... 3-29
RS_DEG ................................................................................................................... 3-30
RS_EXC.................................................................................................................... 3-30
RS_LOF .................................................................................................................... 3-30
RS_TIM ..................................................................................................................... 3-31
SPI_LOS ................................................................................................................... 3-31
Synchronization_Signal_Message_Mismatch .......................................................... 3-32
System_Clock_Holdover_Longer ............................................................................. 3-32
System_Clock_Unlocked .......................................................................................... 3-32
Timing_Reference_Degrade..................................................................................... 3-33
FTDG-H750-D830
Issue 1, August 2008
Contents
3.2.67
3.2.68
3.2.69
3.2.70
3.3
3.3.1
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.4.6
3.4.7
3.5
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
FTDG-H750-D830
Issue 1, August 2008
Contents
List of Tables
Table 1-1
Table 1-2
Table 2-1
Table 2-2
Table 2-3
Table 2-4
Table 2-5
vi
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 1
Preface
CHAPTER 1
Preface
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 1
Preface
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
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. Click the desired alarm name in the Alarm list to jump directly to the
instructions for that alarm.
Described Features
i
1.3
Some features described in this document may not be available. To identify the features
released for your project, please refer to the Release Note delivered together with the
product.
1-2
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 1
Preface
1.3.1
Symbols Used
Danger
This symbol identifies notes which, if ignored, can result in bodily harm.
Warning
!
Caution
This symbol identifies notes which, if ignored, can result in damage to the equipment.
This symbol identifies notes which, if ignored, can result in service interruption.
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
1.3.2
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.
Conventions Used
Representation
Inverted commas
Bold
Italic
Courier
<Angle brackets>
>
Table 1-1
FTDG-H750-D830
Issue 1, August 2008
Meaning
CHAPTER 1
Preface
1.4
History of Changes
Issue
Issue date
August 2008
Table 1-2
1-4
Initial version
History of Changes
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 2
Alarm Lists
CHAPTER 2
Alarm Lists
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 2
Alarm Lists
2.1
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 Network Element (NE)
Quality of Service alarms: originate from termination points where performance
measurement and threshold supervision is enabled
Security alarms: originate from termination points which detect the system authentication
and authorization
Equipment Alarms
Table 2-1 lists FLASHWAVE 4570 equipment alarms. Click the alarm name in the table to
jump directly to the troubleshooting procedure for that alarm.
Alarm name
Communication_Failure
Communication failure
Equipment_OverHeating
Equipment overheating
Fan_Failure
Fan failure
Loss_of_Power_Input
Low_Order_Capacity_Mismatch
No_Free_Low_Order_Capacity
OA-Power_Failure
OA-Pump_Bias_out_of_Range
OA-Temperature_out_of_Range
PLL_Unlock
Power_Failure
Power failure
SC_CF_Module_Absent
SC_CF_Module_Failure
CF card failure
SFP_Absent
SFP_Failure
SFP failure
SFP_Mismatch
SFP mismatch
SPI-Temperature_out_of_Range
Unit_Failure
Unit failure
Unit_Removal
Unit removal
UnitType_Mismatch
VCXO_Failure
Table 2-1
2-2
Equipment Alarms
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 2
Alarm Lists
2.2
Communication Alarms
Table 2-2 lists FLASHWAVE 4570 communication alarms. Click the alarm name in the table
to jump directly to the troubleshooting procedure for that alarm.
Alarm Name
AU_AIS
AU_LOP
HCOC27-DCC_Connection_Failure
HCOC9-DCC_Connection_Failure
HP-DEG
HP-EXC
HP-GFP_Customer_Signal_Failure
HP-GFP_Loss_of_Frame_Delineation
HP-PLM
HP-RDI
HP-TIM
HP-UNEQ
HP UNEQuipped (UNEQ)
HP-Virtual_Concatenation_LOA
HP-Virtual_Concatenation_LOM
HP-Virtual_Concatenation_TLCT
Link_Failure
Link failure
Loss_of_Timing_Input
Loss_of_Timing_Output
LP-DEG
LP-EXC
LP EXC error
LP-GFP_Customer_Signal_Failure
LP-GFP_Loss_of_Frame_Delineation
LP-PLM
LP PLM
LP-RDI
LP RDI
LP-RFI
LP-TIM
LP TIM
Table 2-2
FTDG-H750-D830
Issue 1, August 2008
Communication Alarms
CHAPTER 2
Alarm Lists
Alarm Name
LP-UNEQ
LP UNEQ
LP-Virtual_Concatenation_LOA
LP-Virtual_Concatenation_LOM
LP-Virtual_Concatenation_TLCT
MS_AIS
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_Output_LOS
OA output LOS
OA_Output_Power_High
PPI-AIS
PPI-LOF
PPI LOF
PPI-LOM
PPI LOM
PPI-LOS
PPI LOS
PPI-RDI
PPI RDI
RPR-Exceed_Max_Stations
RPR-Link_Failure_East
RPR-Link_Failure_West
RPR-Miscabling_East
RPR-Miscabling_West
RPR-Protection_Misconfig
RPR-Ringlet0_ReservedA0_Exceeding
RPR-Ringlet1_ReservedA0_Exceeding
RPR-Topology_Inconsistent
RPR-Topology_Instability
RS-DCC_Connection_Failure
RS_DEG
RS signal DEG
RS_EXC
RS EXC
RS_LOF
RS_TIM
RS TIM
SPI_LOS
SPI LOS
Table 2-2
2-4
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 2
Alarm Lists
Alarm Name
Synchronization_Signal_Message_Mis
match
System_Clock_Holdover_Longer
System_Clock_Unlocked
Timing_Reference_Degrade
Timing_Reference_Failure
TU-AIS
TU-LOM
TU LOM
TU-LOP
TU LOP
Table 2-2
2.3
Environmental Alarms
Table 2-3 lists FLASHWAVE 4570 environmental alarms. Click the alarm name in the table
to jump directly to the troubleshooting procedure for that alarm.
Alarm name
ENV_MDI<n>
Table 2-3
2.4
Environmental Alarms
E1-Negative_Bit-slip_TCA_24h
E1-Positive_Bit-slip_TCA_15m
E1-Positive_Bit-slip_TCA_24h
Ethernet TCA
Ethernet TCA
PDH TCA
PDH TCA
SDH TCA
SDH TCA
Table 2-4
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 2
Alarm Lists
2.5
Security Alarms
Table 2-5 lists S hiT 7080 security alarms. Click the alarm name in the table to jump directly
to the troubleshooting procedure for that alarm.
Alarm name
accountExpiredOrDisabled
logIsFull
Log is full
logOccupancyThresholdReached
Unauthorized_Access_Attempt
Unsuccessful_Logins_Exceeded
Table 2-5
2-6
Security Alarms
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
CHAPTER 3
Troubleshooting
FTDG-H750-D830
Issue 1, August 2008
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_Failure
Alarm name
Communication_Failure
Default severity
Major
Alarm object
Troubleshooting instructions
3.1.2
If the alarm persists, contact the next higher level of technical support.
Equipment_OverHeating
Alarm name
Equipment_OverHeating
Default severity
Major
Alarm object
Troubleshooting instructions
3-2
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.1.3
Fan_Failure
Alarm name
Fan_Failure
Default severity
Major
Alarm object
Fan unit
Troubleshooting instructions
3.1.4
If the alarm persists, contact the next higher level of technical support.
Loss_of_Power_Input
Alarm name
Loss_of_Power_Input
Default severity
Major
Alarm object
Power module
Troubleshooting instructions
3.1.5
Verify the power cables to the power module are connected correctly.
If the alarm persists, contact the next higher level of technical support.
Low_Order_Capacity_Mismatch
Alarm name
Low_Order_Capacity_Mismatch
Default severity
Major
Alarm object
NE
Troubleshooting instructions
1
Download a backup MIB from the Personal Computer (PC) into the CF card of the newly
inserted SC card. For more information on MIB download, please refer to Chapter 4.1.6.
If the alarm persists, contact the next higher level of technical support.
Caution
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.1.6
No_Free_Low_Order_Capacity
Alarm name
No_Free_Low_Order_Capacity
Default severity
Major
Alarm object
PDH cards
Troubleshooting instructions
3.1.7
Delete some existing low order mapping on unused PDH cards and remove them from
the system to reallocate low order capacity.
If the alarm persists, contact the next higher level of technical support.
OA-Power_Failure
Alarm name
OA_Power_Failure
Default severity
Critical
Alarm object
OA card
Troubleshooting instructions
3.1.8
If the alarm persists, contact the next higher level of technical support.
OA-Pump_Bias_out_of_Range
Alarm name
OA-Pump_Bias_out_of_Range
Default severity
Major
Alarm object
OA card
Troubleshooting instructions
3-4
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.1.9
OA-Temperature_out_of_Range
Alarm name
OA-Temperature_out_of_Range
Default severity
Major
Alarm object
OA card
Troubleshooting instructions
3.1.10
If the alarm persists, contact the next higher level of technical support.
PLL_Unlock
Alarm name
PLL_Unlock
Default severity
Major
Alarm object
Troubleshooting instructions
3.1.11
If fault occurs during card boot or synchronization, please wait till the initialization
process of the card is complete.
If the alarm persists, contact the next higher level of technical support.
Power_Failure
Alarm name
Power_Failure
Default severity
Major
Alarm object
Power module
Troubleshooting instructions
1
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.1.12
SC_CF_Module_Absent
Alarm name
SC_CF_Module_Absent
Default severity
Major
Alarm object
SC card
Troubleshooting instructions
1
3.1.13
If the alarm persists, contact the next higher level of technical support.
SC_CF_Module_Failure
Alarm name
SC_CF_Module_Failure
Default severity
Major
Alarm object
SC card
Troubleshooting instructions
1 Change the CF card.
For more information, please refer to the FLASHWAVE 4570 Installation and Test
Manual (ITMN).
2
3.1.14
If the alarm persists, contact the next higher level of technical support.
SFP_Absent
Alarm name
SFP_Absent
Default severity
Major
Alarm object
Optical port
Troubleshooting instructions
3-6
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.1.15
SFP_Failure
Alarm name
SFP_Failure
Default severity
Major
Alarm object
SFP module
Troubleshooting instructions
3.1.16
If the alarm persists, contact the next higher level of technical support.
SFP_Mismatch
Alarm name
SFP_Mismatch
Default severity
Major
Alarm object
SFP module
Troubleshooting instructions
3.1.17
If the alarm persists, contact the next higher level of technical support.
SPI-Temperature_out_of_Range
Alarm name
SPI-Temperature_out_of_Range
Default severity
Major
Alarm object
STM-64 port
Troubleshooting instructions
1
Verify the refrigeration part and the bias current part of the laser are working correctly.
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.1.18
Unit_Failure
Alarm name
Unit_Failure
Default severity
Major
Alarm object
Cards
Troubleshooting instructions
3.1.19
If the alarm persists, contact the next higher level of technical support.
Unit_Removal
Alarm name
Unit_Removal
Default severity
Major
Alarm object
Cards
Troubleshooting instructions
3.1.20
If the alarm persists, contact the next higher level of technical support.
UnitType_Mismatch
Alarm name
UnitType_Mismatch
Default severity
Major
Alarm object
Cards
Troubleshooting instructions
3-8
Verify the card type in SEEPROM is set correctly through the cards mini USB.
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.1.21
VCXO_Failure
Alarm name
VCXO_Failure
Default severity
Major
Alarm object
HOCC card
Troubleshooting instructions
3.2
If the alarm persists, contact the next higher level of technical support.
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
Troubleshooting instructions
3.2.2
Troubleshoot the SPI, RS, MS, or AU-LOP alarms in the upstream node.
If the alarm persists, contact the next higher level of technical support.
AU_LOP
Alarm name
AU_LOP
Default severity
Critical
Alarm object
SDH AU
Troubleshooting instructions
1
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.3
Default severity
Major
Alarm object
NE
Troubleshooting instructions
3.2.4
If the alarm persists, contact the next higher level of technical support.
HCOC27-DCC_Connection_Failure
Alarm name
HCOC27-DCC_Connection_Failure
Default severity
Major
Alarm object
SDH HCOC
Troubleshooting instructions
3.2.5
Verify the HCOC27-DCC is enabled and working normally at both ends of the DCC link.
If the alarm persists, contact the next higher level of technical support.
HCOC9-DCC_Connection_Failure
Alarm name
HCOC9-DCC_Connection_Failure
Default severity
Major
Alarm object
SDH HCOC
Troubleshooting instructions
3-10
Verify the HCOC9-DCC is enabled and working normally at both ends of the DCC link.
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.6
HP-DEG
Alarm name
HP-DEG
Default severity
Minor
Alarm object
SDH HP
Troubleshooting instructions
3.2.7
If the alarm persists, contact the next higher level of technical support.
HP-EXC
Alarm name
HP-EXC
Default severity
Major
Alarm object
SDH HP
Troubleshooting instructions
3.2.8
If the alarm persists, contact the next higher level of technical support.
HP-GFP_Customer_Signal_Failure
Alarm name
HP-GFP_Customer_Signal_Failure
Default severity
Critical
Alarm object
Troubleshooting instructions
1
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.9
HP-GFP_Loss_of_Frame_Delineation
Alarm name
HP-GFP_Loss_of_Frame_Delineation
Default severity
Critical
Alarm object
Troubleshooting instructions
3.2.10
If the alarm persists, contact the next higher level of technical support.
HP-PLM
Alarm name
HP-PLM
Default severity
Critical
Alarm object
SDH HP
Troubleshooting instructions
3.2.11
Change the mapping mode of the local node to the same as the remote node.
Change the expected payload value of the local node to the same as the actual payload
value of the remote node.
If the alarm persists, contact the next higher level of technical support.
HP-RDI
Alarm name
HP-RDI
Default severity
Minor
Alarm object
SDH HP
Troubleshooting instructions
3-12
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.12
HP-TIM
Alarm name
HP-TIM
Default severity
Critical
Alarm object
SDH HP
Troubleshooting instructions
3.2.13
If the alarm persists, contact the next higher level of technical support.
HP-UNEQ
Alarm name
HP-UNEQ
Default severity
Critical
Alarm object
SDH HP
Troubleshooting instructions
3.2.14
Confirm or create the cross connection at the other side to be consistent with the local
side.
If the alarm persists, contact the next higher level of technical support.
HP-Virtual_Concatenation_LOA
Alarm name
HP-Virtual_Concatenation_LOA
Default severity
Critical
Alarm object
HP VCG
Troubleshooting instructions
1
Check the SDH path for each VCG member to see which member passes through the
most equipment or is taking the most time, and investigate an alternative connection
route.
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.15
HP-Virtual_Concatenation_LOM
Alarm name
HP-Virtual_Concatenation_LOM
Default severity
Critical
Alarm object
HP VCG member
Troubleshooting instructions
3.2.16
Check VCG member for relevant terminal point alarms and correct them. Verify if HPVirtual_Concatenation_LOM alarm still exists.
Check performance monitoring for relevant VCG member terminal point for errors and
correct them. Verify if HP-Virtual_Concatenation_LOM alarm still exists.
If the alarm persists, contact the next higher level of technical support.
HP-Virtual_Concatenation_TLCT
Alarm name
HP-Virtual_Concatenation_TLCT
Default severity
Critical
Alarm object
HP VCG
Troubleshooting instructions
3-14
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.17
Link_Failure
Alarm name
Link_Failure
Default severity
Critical
Alarm object
Ethernet ports
Troubleshooting instructions
3.2.18
If the alarm persists, contact the next higher level of technical support.
Loss_of_Timing_Input
Alarm name
Loss_of_Timing_Input
Default severity
Critical
Alarm object
HOCC card
Troubleshooting instructions
1
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.19
Loss_of_Timing_Output
Alarm name
Loss_of_Timing_Output
Default severity
Critical
Alarm object
HOCC card
Troubleshooting instructions
3.2.20
If the alarm persists, contact the next higher level of technical support.
LP-DEG
Alarm name
Default severity
Alarm object
General information and causes
LP-DEG
Minor
SDH LP
The bit error ratio in the LP has exceeded the
provisioned LP Degrade Threshold. The quality
of the transmission signal is degraded.
This error is caused by fault(s) in upstream
external cabling or equipment.
Troubleshooting instructions
3.2.21
If the alarm persists, contact the next higher level of technical support.
LP-EXC
Alarm name
LP-EXC
Default severity
Major
Alarm object
SDH LP
Troubleshooting instructions
3-16
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.22
LP-GFP_Customer_Signal_Failure
Alarm name
LP-GFP_Customer_Signal_Failure
Default severity
Critical
Alarm object
Troubleshooting instructions
3.2.23
If the alarm persists, contact the next higher level of technical support.
LP-GFP_Loss_of_Frame_Delineation
Alarm name
LP-GFP_Loss_of_Frame_Delineation
Default severity
Critical
Alarm object
Troubleshooting instructions
3.2.24
If the alarm persists, contact the next higher level of technical support.
LP-PLM
Alarm name
LP-PLM
Default severity
Major
Alarm object
SDH LP
Troubleshooting instructions
1
Verify the traffic structure of the local node is the same as the far-end node.
Change the expected traffic type in the TP Configuration window of the local node LCT
to match the actual payload value in far-end node.
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.25
LP-RDI
Alarm name
LP-RDI
Default severity
Minor
Alarm object
SDH LP
Troubleshooting instructions
3.2.26
No alarms in the reporting node. React on the far-end alarms. Follow the clearing
actions for those alarm(s).
If the alarm persists, contact the next higher level of technical support.
LP-RFI
Alarm name
LP-RFI
Default severity
Minor
Alarm object
SDH LP
Troubleshooting instructions
3.2.27
No alarms in the reporting node. React on the far-end alarms. Follow the clearing
actions for those alarm(s).
If the alarm persists, contact the next higher level of technical support.
LP-TIM
Alarm name
LP-TIM
Default severity
Critical
Alarm object
SDH LP
Troubleshooting instructions
3-18
Verify cross-connections.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.28
If the alarm persists, contact the next higher level of technical support.
LP-UNEQ
Alarm name
LP-UNEQ
Default severity
Critical
Alarm object
SDH LP
Troubleshooting instructions
1
Confirm or create the cross connection settings at the remote side to be consistent with
the local side.
If the alarm persists, contact the next higher level of technical support.
i
Warning
!
3.2.29
When defining or changing a cross-connection this alarm will almost inevitably come up
as it is practically impossible to issue the changes at both sides at the same moment.
The LP-UNEQ can not be reported from 126 E1 (W/P) cards monitored ports if there is no
cross connect card equipped in NE.
LP-Virtual_Concatenation_LOA
Alarm name
LP-Virtual_Concatenation_LOA
Default severity
Critical
Alarm object
LP VCG
Troubleshooting instructions
3.2.30
Check the SDH path for each VCG member to see which member passes through the
most equipment or is taking the most time, and investigate an alternative connection
route.
If the alarm persists, contact the next higher level of technical support.
LP-Virtual_Concatenation_LOM
FTDG-H750-D830
Issue 1, August 2008
Alarm name
LP-Virtual_Concatenation_LOM
Default severity
Critical
Alarm object
LP VCG member
CHAPTER 3
Troubleshooting
Troubleshooting instructions
3.2.31
Check VCG member for relevant terminal point alarms and correct them. Verify if LPVirtual_Concatenation_LOM alarm still exists.
Check performance monitoring for relevant VCG member terminal point for errors and
correct them. Verify if LP-Virtual_Concatenation_LOM alarm still exists.
3 If the alarm persists, contact the next higher level of technical support.
LP-Virtual_Concatenation_TLCT
Alarm name
LP-Virtual_Concatenation_TLCT
Default severity
Critical
Alarm object
LP VCG
Troubleshooting instructions
3-20
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.32
MS_AIS
Alarm name
MS_AIS
Default severity
Minor
Alarm object
SDH MS
Troubleshooting instructions
3.2.33
If the alarm persists, contact the next higher level of technical support.
MS-DCC_Connection_Failure
Alarm name
MS-DCC_Connection_Failure
Default severity
Major
Alarm object
SDH MS
Troubleshooting instructions
3.2.34
Verify the MS-DCC is enabled and working normally at both ends of the MS DCC link.
If the alarm persists, contact the next higher level of technical support.
MS_DEG
Alarm name
MS_DEG
Default severity
Minor
Alarm object
SDH MS
Troubleshooting instructions
1
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.35
MS_EXC
Alarm name
MS_EXC
Default severity
Major
Alarm object
SDH MS
Troubleshooting instructions
3.2.36
If the alarm persists, contact the next higher level of technical support.
MS-K1/K2_Mismatch
Alarm name
MS-K1/K2_Mismatch
Default severity
Major
Alarm object
SDH MS
Troubleshooting instructions
3.2.37
If the alarm persists, contact the next higher level of technical support.
MS_RDI
Alarm name
MS_RDI
Default severity
Minor
Alarm object
SDH MS
Troubleshooting instructions
1
3-22
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.38
If the alarm persists, contact the next higher level of technical support.
OA_Gain_High
Alarm name
OA_Gain_High
Default severity
Major
Alarm object
OA ports
Troubleshooting instructions
3.2.39
If the alarm persists, contact the next higher level of technical support.
OA_Input_LOS
Alarm name
OA_Input_LOS
Default severity
Critical
Alarm object
OA ports
Troubleshooting instructions
1
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.40
OA_Output_LOS
Alarm name
OA_Output_LOS
Default severity
Critical
Alarm object
OA ports
Troubleshooting instructions
3.2.41
If the alarm persists, contact the next higher level of technical support.
OA_Output_Power_High
Alarm name
OA_Output_Power_High
Default severity
Major
Alarm object
OA ports
Troubleshooting instructions
3.2.42
If the alarm persists, contact the next higher level of technical support.
PPI-AIS
Alarm name
PPI-AIS
Default severity
Minor
Alarm object
Port
Troubleshooting instructions
3-24
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.43
PPI-LOF
Alarm name
PPI-LOF
Default severity
Critical
Alarm object
PDH Port
Troubleshooting instructions
3.2.44
If the alarm persists, contact the next higher level of technical support.
PPI-LOM
Alarm name
PPI-LOM
Default severity
Critical
Alarm object
PDH Port
Troubleshooting instructions
3.2.45
If the alarm persists, contact the next higher level of technical support.
PPI-LOS
Alarm name
PPI-LOS
Default severity
Critical
Alarm object
PDH Port
Troubleshooting instructions
1
Verify for cable breaks or dirty connectors (measure it with power meter and clear it).
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.46
PPI-RDI
Alarm name
PPI-RDI
Default severity
Minor
Alarm object
PDH Port
Troubleshooting instructions
3.2.47
If the alarm persists, contact the next higher level of technical support.
RPR-Exceed_Max_Stations
Alarm name
RPR-Exceed_Max_Stations
Default severity
Critical
Alarm object
RPR Card
Troubleshooting instructions
3.2.48
If the alarm persists, contact the next higher level of technical support.
RPR-Link_Failure_East
Alarm name
RPR-Link_Failure_East
Default severity
Critical
Alarm object
RPR Card
Troubleshooting instructions
3-26
Verify that the optical fiber or the SDH cross-connection used for the east RPR path is
normal.
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.49
RPR-Link_Failure_West
Alarm name
RPR-Link_Failure_West
Default severity
Critical
Alarm object
RPR Card
Troubleshooting instructions
3.2.50
Verify that the optical fiber or the SDH cross-connection used for the west RPR path is
normal.
If the alarm persists, contact the next higher level of technical support.
RPR-Miscabling_East
Alarm name
RPR-Miscabling_East
Default severity
Critical
Alarm object
RPR Card
Troubleshooting instructions
3.2.51
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.
If the alarm persists, contact the next higher level of technical support.
RPR-Miscabling_West
Alarm name
RPR-Miscabling_West
Default severity
Critical
Alarm object
RPR Card
Troubleshooting instructions
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.
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.52
RPR-Protection_Misconfig
Alarm name
RPR-Protection_Misconfig
Default severity
Critical
Alarm object
RPR Card
Troubleshooting instructions
3.2.53
Verify the protection mode in all of the RPR stations of the ring is the same. If not, reconfigure the protection mode to be the same.
If the alarm persists, contact the next higher level of technical support.
RPR-Ringlet0_ReservedA0_Exceeding
Alarm name
RPR-Ringlet0_ReservedA0_Exceeding
Default severity
Major
Alarm object
RPR Card
Troubleshooting instructions
3.2.54
Re-configure the A0 bandwidth reserved on RPR ringlet0 and make sure not to exceed
the available link rate.
If the alarm persists, contact the next higher level of technical support.
RPR-Ringlet1_ReservedA0_Exceeding
Alarm name
RPR-Ringlet1_ReservedA0_Exceeding
Default severity
Major
Alarm object
RPR Card
Troubleshooting instructions
3-28
Re-configure the A0 bandwidth reserved on RPR ringlet1 and make sure not to exceed
the available link rate.
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.55
RPR-Topology_Inconsistent
Alarm name
RPR-Topology_Inconsistent
Default severity
Critical
Alarm object
RPR Card
Troubleshooting instructions
3.2.56
If the alarm persists, contact the next higher level of technical support.
RPR-Topology_Instability
Alarm name
RPR-Topology_Instability
Default severity
Critical
Alarm object
RPR Card
Troubleshooting instructions
3.2.57
Re-configure 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.
If the alarm persists, contact the next higher level of technical support.
RS-DCC_Connection_Failure
Alarm name
RS-DCC_Connection_Failure
Default severity
Major
Alarm object
SDH RS
Troubleshooting instructions
1
Verify the RS-DCC is enabled and working normally at both ends of the RS DCC link.
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.58
RS_DEG
Alarm name
RS-DEG
Default severity
Minor
Alarm object
SDH RS
Troubleshooting instructions
3.2.59
If the alarm persists, contact the next higher level of technical support.
RS_EXC
Alarm name
RS_EXC
Default severity
Major
Alarm object
SDH RS
Troubleshooting instructions
3.2.60
If the alarm persists, contact the next higher level of technical support.
RS_LOF
Alarm name
RS_LOF
Default severity
Critical
Alarm object
SDH RS
Troubleshooting instructions
3-30
Loop the signal from the transmitter to the receiver. Verify no LOF fault is reported.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.61
If the alarm persists, contact the next higher level of technical support.
RS_TIM
Alarm name
RS_TIM
Default severity
Critical
Alarm object
SDH RS
Troubleshooting instructions
3.2.62
Verify the line cables are connected correctly by interpreting the received STM-N RS
trace identifiers.
If the alarm persists, contact the next higher level of technical support.
SPI_LOS
Alarm name
SPI_LOS
Default severity
Critical
Alarm object
SDH SPI
Troubleshooting instructions
1
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.63
Synchronization_Signal_Message_Mismatch
Alarm name
Synchronization_Signal_Message_Mismatch
Default severity
Major
Alarm object
HOCC card
Troubleshooting instructions
3.2.64
If the alarm persists, contact the next higher level of technical support.
System_Clock_Holdover_Longer
Alarm name
System_Clock_Holdover_Longer
Default severity
Warning
Alarm object
HOCC card
Troubleshooting instructions
3.2.65
If the alarm persists, contact the next higher level of technical support.
System_Clock_Unlocked
Alarm name
System_Clock_Unlocked
Default severity
Major
Alarm object
HOCC card
Troubleshooting instructions
3-32
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.66
Timing_Reference_Degrade
Alarm name
Timing_Reference_Degrade
Default severity
Minor
Alarm object
Troubleshooting instructions
3.2.67
If the alarm persists, contact the next higher level of technical support.
Timing_Reference_Failure
Alarm name
Timing_Reference_Failure
Default severity
Major
Alarm object
Troubleshooting instructions
3.2.68
If the alarm persists, contact the next higher level of technical support.
TU-AIS
Alarm name
TU-AIS
Default severity
Minor
Alarm object
SDH TU
Troubleshooting instructions
1
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.2.69
TU-LOM
Alarm name
TU-LOM
Default severity
Critical
Alarm object
SDH TU
Troubleshooting instructions
3.2.70
Using the management system, check if unit failure is reported for the unit generating
the multi-frame alignment signal. In that NE, remove the unit and replace it with a new
one.
If a unit failure is not reported, loop the STM-1 signal at the transmitting NE and at the
receiving NE. In this condition, the network element reporting VC-4 Loss of multiframe
contains the faulty unit.
If the alarm persists, contact the next higher level of technical support.
TU-LOP
Alarm name
TU-LOP
Default severity
Critical
Alarm object
SDH TU
Troubleshooting instructions
3.3
Verify whether the TP Multiplexer structure of the both ends of the stream is the same.
If the alarm persists, contact the next higher level of technical support.
Environmental Alarms
The environmental alarm is listed in the following sub-chapter.
3-34
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.3.1
ENV_MDI<n>
Alarm name
EVN_MDI<n>
Default severity
Warning
Alarm object
MDI module
Troubleshooting instructions
3.4
Keep the states of the MDI items same with what is pre-defined.
If the alarm persists, contact the next higher level of technical support.
3.4.1
E1-Negative_Bit-slip_TCA_15m
Alarm name
E1-Negative_Bit-slip_TCA_15m
Default severity
Minor
Alarm object
PDH E1
Troubleshooting instructions
3.4.2
If the alarm persists, contact the next higher level of technical support.
E1-Negative_Bit-slip_TCA_24h
Alarm name
E1-Negative_Bit-slip_TCA_24h
Default severity
Minor
Alarm object
PDH E1
Troubleshooting instructions
1
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.4.3
E1-Positive_Bit-slip_TCA_15m
Alarm name
E1-Positive_Bit-slip_TCA_15m
Default severity
Minor
Alarm object
PDH E1
Troubleshooting instructions
3.4.4
If the alarm persists, contact the next higher level of technical support.
E1-Positive_Bit-slip_TCA_24h
Alarm name
E1-Positive_Bit-slip_TCA_24h
Default severity
Minor
Alarm object
PDH E1
Troubleshooting instructions
3.4.5
If the alarm persists, contact the next higher level of technical support.
Ethernet TCA
Alarm name
Ethernet TCA
Default severity
Minor
Alarm object
Troubleshooting instructions
1
3-36
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.4.6
Verify the upstream NE sends the excessive bad bytes or packets on purpose.
If the alarm persists, contact the next higher level of technical support.
PDH TCA
Alarm name
PDH TCA
Default severity
Minor
Alarm object
Troubleshooting instructions
1
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.4.7
SDH TCA
Alarm name
SDH TCA
Default severity
Minor
Alarm object
Troubleshooting instructions
3-38
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.5
Security Alarms
The security alarms are listed in the following sub-chapters.
3.5.1
AccountExpiredOrDisabled
Alarm name
accountExpiredOrDisabled
Default severity
Minor
Alarm object
NE
Troubleshooting instructions
3.5.2
If the account has expired - enable the account using the LCT and set a new expiration
date.
If the account was automatically disabled by SNMPv3 - verify the security log for reason
of account suspension and if desired re-enable the user.
If the alarm persists, contact the next higher level of technical support.
LogIsFull
Alarm name
logIsFull
Default severity
Major
Alarm object
NE
Troubleshooting instructions
1
Upload log file and select option to delete log after upload.
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 3
Troubleshooting
3.5.3
LogOccupancyThresholdReached
Alarm name
logOccupancyThresholdReached
Default severity
Minor
Alarm object
NE
Troubleshooting instructions
3.5.4
Upload log file and select option to delete log after upload.
If the alarm persists, contact the next higher level of technical support.
Unauthorized_Access_Attempt
Alarm name
Unauthorized_Access_Attempt
Default severity
Minor
Alarm object
NE
Troubleshooting instructions
3.5.5
In the LCT, go the User Administration window (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.
If the alarm persists, contact the next higher level of technical support.
Unsuccessful_Logins_Exceeded
Alarm name
Unsuccessful_Logins_Exceeded
Default severity
Major
Alarm object
NE
Troubleshooting instructions
3-40
In the LCT, go the User Administration window (NE Security > NE User
Management). Check the desired user or user with high number of invalid logins. Reenable the user by right-clicking the user and selecting Enable from the context menu or
click Modify User and deselect the Account is disabled check box in the Modify User
window.
If the alarm persists, contact the next higher level of technical support.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 4
Card Replacement
CHAPTER 4
Card Replacement
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 4
Card Replacement
This section contains instructions for removing a faulty card and replacing it with a spare of
the same type.
The general instructions are as follows:
When replacing cards, all the operations must comply with the FLASHWAVE 4570
Safety Instructions.
When replacing 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 or inserted the slots while they are live. 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. Please make sure that the two levers of the card secure the card
pair in the shelf properly.
After a card has been replaced, the card status must be confirmed on the LCT.
Running the system without the Cross Connection (CC) card is prohibited. Please 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.
For instructions on how to execute many of the instructions described in this chapter, please
refer to the FLASHWAVE 4570 Installation and Test Manual (ITMN), Commissioning Manual
(COMN), and Operating Manual (OMN).
4.1
Replacing SC Card
Each NE includes an SC card, which functions as the central management controller for the
NE. Replacement of the SC card requires special care since it contains a fieldreplaceable
CF card used for persistent storage of the MIB and system software. Card replacement
procedures vary, depending on the failure scenario.
These different scenarios are as follows:
SC card failure
CF card failure
Caution
When an SC card is removed from the shelf, the management system will lose connectivity
to the NE.
During this time, the management interface is not functional.
Before the SC card replacement, the following preparation should be done:
1
One PC connects to the new SC card via the console port and connects to the System
Interface with Engineering Order Wire (SI-E) or System Interface (SI) card via the
MGMT port.
4-2
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.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 4
Card Replacement
To activate this server please refer to the FLEXR L manual in the section containing
information on 3rd party software installation.
4
The unzip software like winzip or winrar should be installed on the PC.
The boot image file (e.g., 7080.bin) and software load file (e.g., PBm1r40bxxx.bld)
should be saved in the FTP server user directory.
For the boot image file and software load file, please contact Fujitsu Technical Support.
The MIB file saved by the LCT 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.
4.1.1
SC Card Failure
To replace the SC card, complete the following steps:
1
5
Caution
During the system reboot, press <b> to stop the boot process when the Hyper Terminal
shows the countdown 5 4 3 2 1 ... .
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.
In this case, the operator must remove the SC card immediately and execute the step 4 and
5 again.
The Boot Mode window is opened in the Hyper Terminal.
6
After the formatting finishes, press <x> to return to the Boot Mode window.
CHAPTER 4
Card Replacement
14 After the system reboot finishes, verify the software version is correct through the LCT.
See ........... The FLASHWAVE 4570 Operating Manual (OMN).
PROCEDURE COMPLETE!
4.1.2
CF Card Failure
To replace the CF card, complete the following steps:
1
During the system reboot, press <b> to stop the boot process when the Hyper Terminal
shows the countdown 5 4 3 2 1 ... .
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.
In this case, the operator must remove the SC card immediately and execute the step 4 and
5 again.
The Boot Mode window is opened in the Hyper Terminal.
6
After the formatting finishes, press <x> to return to the Boot Mode window.
4.1.3
4-4
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 4
Card Replacement
3
Caution
During the system reboot, press <b> to stop the boot process when the Hyper Terminal
shows the countdown 5 4 3 2 1 ... .
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.
In this case, the operator must remove the SC card immediately and execute the step 4 and
5 again.
The Boot Mode window is opened in the Hyper Terminal.
4
4.1.4
Launch the Boot Mode window in the Hyper Terminal by pressing <b> during the
system reboot when the Hyper Terminal shows the countdown 5 4 3 2 1 ...
Press <2> and enter the NE Ethernet Internet Protocol (IP) address.
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.
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.
The default user name is pm.
FTDG-H750-D830
Issue 1, August 2008
Press <8> and enter the FTP password which is used for the NE to login into the FTP
server.
CHAPTER 4
Card Replacement
4.1.5
In the IP Configuration window, press <6> and enter the corresponding software load
file name (e.g., PBm1r40bxxx.bld).
After the system has finished rebooting, veriify the software version is correct through
the NE LCT system using the FLEXR L or FLEXR C R3.
PROCEDURE COMPLETE!
4.1.6
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 <b> during the
system reboot when the Hyper Terminal shows the countdown 5 4 3 2 1 ...
Press <2> and enter the NE Ethernet Internet Protocol (IP) address.
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.
On the PC, select Start > Programs > Accessories > Command Prompt menu item.
The Command Prompt window is opened.
4-6
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 4
Card Replacement
ftp
Enter the FTP user account name and password for the PC to login to the FTP server
on the NE.
The NE is an FTP server.
The default user name is root.
The default password is <Enter>.
mkdir mib
cd mib
mkdir active
cd active
bin
prom
put ghead.txt
put headfile.txt
mkdir ne
cd ne
lcd ne
mput *.*
cd ..
mkdir gmpls
cd gmpls
lcd ..
lcd gmpls
mput *.*
FTDG-H750-D830
Issue 1, August 2008
dir
pwd
bye
CHAPTER 4
Card Replacement
/cfg/mib/active/ghead.txt
/cfg/mib/active/headfile.txt
/cfg/mib/active/ne/*.*
/cfg/mib/active/gmpls/*.*
PROCEDURE COMPLETE!
4.2
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 traffic has been transfered to the CC card
which is NOT being replaced via the LCT.
When the working CC card fails, the traffic will switch to the protection card
automatically.
See ........... The FLASHWAVE 4570 Operating Manual (OMN).
If the CC card is switched manually in Step 1, clear the switch request command set in
Step 1 via the LCT.
See ........... The FLASHWAVE 4570 Operating Manual (OMN).
PROCEDURE COMPLETE!
i
4.3
There must be three minutes between two consecutive CC card switches to ensure no
traffic hit.
The system can still work normally for 16 hours when only one fan unit fails and the
failed unit is still inserted in the NE.
The system can not work when a fan unit is absent for more than two minutes. The
action of exchanging the faulty fan unit must be finished within two minutes.
Detailed instructions for replacing the fan unit can be found in the FLASHWAVE 4570
Installation and Test Manual (ITMN).
4-8
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 4
Card Replacement
4.4
Detailed instructions for replacing the filter unit can be found in the FLASHWAVE 4570
Installation and Test Manual (ITMN).
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 5
MIB Switching
CHAPTER 5
MIB Switching
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 5
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 data configuration is different between the old and new MIB.
The data configuration is the same between the old and new MIB.
For instructions on how to execute the instructions described in this chapter, please refer to
the FLASHWAVE 4570 Operating Manual (OMN).
5.1
Upload the MIB of the old configuration from the NE to the local PC to backup the old
configuration.
See ........... The FLASHWAVE 4570 Operating Manual (OMN).
Download the MIB of the new configuration from the local PC to the NE.
See ........... The FLASHWAVE 4570 Operating Manual (OMN).
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
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.
!
See ........... The FLASHWAVE 4570 Operating Manual (OMN).
PROCEDURE COMPLETE!
5-2
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 5
MIB Switching
5.2
Upload the MIB of the old configuration from the NE to the local PC to backup the old
configuration.
See ........... The FLASHWAVE 4570 Operating Manual (OMN).
Download the MIB of the new configuration from the local PC to the NE.
See ........... The FLASHWAVE 4570 Operating Manual (OMN).
PROCEDURE COMPLETE!
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 6
Optical Connector and Fiber Handling
CHAPTER 6
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 6
Optical Connector and Fiber Handling
Danger
Never handle exposed fiber with your bare hands or touch it to your body. Fiber fragments
can enter the skin and are difficult to detect and remove.
Warning Optical connectors are precision-made components and must be handled accordingly. To
ensure faultless functioning, the following points must be observed.
!
6-2
Always fit optical fiber connectors with protective caps to guard them against mechanical
damage and contamination. The protective dust caps should only be removed
immediately prior to installation.
Once the protective dust caps have been removed, you must check the surfaces of the
optical fiber connectors to ensure that they are clean, and clean them if necessary.
Use only lint-free swabs, or ribbon cleaner specially designed for cleaning optical
connectors. Lint-free swabs should be stored in a clean container to avoid contamination
of the tip. Never use ordinary cotton swabs or tissues. Lint from these items will
contaminate the connector. Also never use alcohol. Only dry clean connectors.
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 7
Abbreviations
CHAPTER 7
Abbreviations
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 7
Abbreviations
7-2
AIS
AU
Administrative Unit
BBE
BER
BF
Board Flash
BOA
CC
Cross-Connection
CF
Compact Flash
COMN
Commissioning Manual
CRC
DCC
DEG
DEGraded
ENV
ENVironment
ES
Errored Second
EXC
EXCessive
FC
Fiber Channel
FTP
GFP
GUI
HCOC
HOCC
HP
IP
Internet Protocol
LAN
LCAS
LCT
LED
LOA
Loss Of Alignment
LOF
Loss Of Frame
LOM
Loss Of Multiframe
LOP
Loss Of Pointer
LOS
Loss Of Signal
LP
ITMN
MAC
MDI
MIB
MS
Multiplex Section
FTDG-H750-D830
Issue 1, August 2008
CHAPTER 7
Abbreviations
NE
Network Element
OA
Optical Amplifier
OMN
Operating Manual
PC
Personal Computer
PDH
PLM
PayLoad Mismatch
POA
Pre-Optical Amplifier
PLL
PPI
QoS
Quality of Service
RDI
RFI
RPR
RS
Regeneration Section
SC
System Controller
SDH
SES
SFP
SI-E
SNMP
SPI
SSM
TCA
TIM
TLCT
TP
Terminal Point
TU
Tributary Unit
UAS
UnAvailable Second
UNEQ
UNEQuipped
VCG
VCXO
WAN
XFP
FTDG-H750-D830
Issue 1, August 2008