Alcatel-Lucent 1643 AMS Operation Manual
Alcatel-Lucent 1643 AMS Operation Manual

Alcatel-Lucent 1643 AMS Operation Manual

Access multiplexer and access multiplexer small (formerly metropolis am and metropolis ams. release 1.0 through 7.2. alarm messages and trouble clearing guide
Hide thumbs Also See for 1643 AMS:
Table of Contents

Advertisement

1643 Access Multiplexer and 1643
Access Multiplexer Small (Formerly
®
®
Metropolis
AM and Metropolis
AMS)
Release 1.0 through 7.2
Alarm Messages and Trouble Clearing Guide
365-312-803R7.2
CC109635763
Issue 4
May 2007
Alcatel-Lucent - Proprietary
This document contains proprietary information of Alcatel-Lucent and
is not to be disclosed or used except in accordance with applicable agreements.
Copyright © 2007 Alcatel-Lucent
Unpublished and Not for Publication
All Rights Reserved

Advertisement

Table of Contents
loading

Summary of Contents for Alcatel-Lucent 1643 AMS

  • Page 1 CC109635763 Issue 4 May 2007 Alcatel-Lucent - Proprietary This document contains proprietary information of Alcatel-Lucent and is not to be disclosed or used except in accordance with applicable agreements. Copyright © 2007 Alcatel-Lucent Unpublished and Not for Publication All Rights Reserved...
  • Page 2 See notice on first age Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
  • Page 3: Table Of Contents

    2 Mbit/s Alarm indication signal received 1-23 1-23 ........................2 Mbit/s Excessive FAW bit error rate 1-24 1-24 ......................... 2 Mbit/s Excessive FAW bit error rate egress 1-25 1-25 ....................................................................365-312-803R7.2 Alcatel-Lucent - Proprietary Issue 4, May 2007 See notice on first page...
  • Page 4 ....................Encapsulated-MAC loss of frame alignment 1-52 1-52 ......................Ethernet interface Auto Negotiation Mismatch 1-53 1-53 ......................Ethernet interface Loss of input signal 1-54 1-54 ......................................................................Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 5 Maximum number of VLAN instances exceeded in MIB 1-83 1-83 ..................Maximum round trip delay threshold crossing 15min 1-84 1-84 ................... Maximum round trip delay threshold crossing 24hrs 1-85 1-85 ................................................................365-312-803R7.2 Alcatel-Lucent - Proprietary Issue 4, May 2007 See notice on first page...
  • Page 6 P12S Network side remote degraded condition 1-112 1-112 ...................... P12S Network side remote loss of frame condition 1-113 1-113 ..................... Pluggable Module failure 1-114 1-114 ............................................................................ Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 7 SHDSL Near-end unavailable seconds threshold crossing 24-hrs 1-141 1-141 ..............SHDSL Network Termination Unit authentication error 1-142 1-142 ..................SHDSL Network Termination Unit configuration command incomplete 1-143 1-143 ........................................................365-312-803R7.2 Alcatel-Lucent - Proprietary Issue 4, May 2007 See notice on first page...
  • Page 8 STM-1 MS Alarm indication signal received 1-171 1-171 ......................STM-1 MS Moderate block error rate 1-172 1-172 ........................STM-1 MS Near-end background block errors threshold crossing 15-min 1-173 1-173 ........................................................viii Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 9 1-199 ......................STM-4 Not expected input signal 1-200 1-200 ..........................STM-4 RS trace identifier mismatch 1-201 1-201 .......................... System timing in backup state 1-202 1-202 .......................................................................... 365-312-803R7.2 Alcatel-Lucent - Proprietary Issue 4, May 2007 See notice on first page...
  • Page 10 VC-12 Near-end errored seconds threshold crossing 15-min 1-229 1-229 ................VC-12 Near-end errored seconds threshold crossing 24-hrs 1-230 1-230 ................VC-12 Near-end severely ES threshold crossing 15-min 1-231 1-231 ..............................................................Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 11 VC-3 Near-end background block errors threshold crossing 24-hrs 1-258 1-258 .............. VC-3 Near-end errored seconds threshold crossing 15-min 1-259 1-259 ................VC-3 Near-end errored seconds threshold crossing 24-hrs 1-260 1-260 ..............................................................365-312-803R7.2 Alcatel-Lucent - Proprietary Issue 4, May 2007 See notice on first page...
  • Page 12 VC-4 Near-end background block errors threshold crossing 24-hrs 1-287 1-287 .............. VC-4 Near-end errored seconds threshold crossing 15-min 1-288 1-288 ................VC-4 Near-end errored seconds threshold crossing 24-hrs 1-289 1-289 ..............................................................Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 13 1-315 ..............................Wrong Pluggable Module present 1-316 1-316 ..........................Wrong SDSL unit present 1-317 1-317 ..............................Wrong STM-1 interface extension board present 1-318 1-318 ..................................................................365-312-803R7.2 Alcatel-Lucent - Proprietary xiii Issue 4, May 2007 See notice on first page...
  • Page 14 X21 interface loss of input signal 1-323 1-323 ..........................X21 interface interface not expected input signal 1-324 1-324 ....................X21 output timing mode change 1-325 1-325 ..........................Glossary Index ..............................................Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 15: About This Information Product

    Reason for reissue This is the fourth issue of this guide for 1643 AM and 1643 AMS, Releases 1.0 through 7.2. A new version of this document was needed to address all features supported by 1643 AM and 1643 AMS, Releases 1.0 through 7.2.
  • Page 16 Spanning tree protocol Garnet 3.1 May 2003 • Rapid spanning tree protocol Garnet 3.2 July 2003 • introduction of 1643 AMS • introduction of Network Termination Unit (NTU) • Optional additional twelve SHDSL interfaces Venus 4.0 September • X8PL option card 2003 •...
  • Page 17: Intended Audience

    J0 support on STM-n lines • E1 non-intrusive monitoring • E1 PDH AIS • 1643 AMS with integrated AC power supply • Increased SFP support (STM-1e, single fiber) • New SHDSL option card with R6.1 Features, e.g. SW Download to NTUs.
  • Page 18: How To Use This Information Product

    • Alarm Messages: This chapter holds an alphabetic list of all alarms for the related network element. • Glossary: In this chapter all the special terms and all the abbreviations and acronyms, used in this manual, are listed..............................................xviii Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 19: Related Documentation

    Related documentation These documents are included in the 1643 AM and 1643 AMS documentation set. • The 1643 AM and 1643 AMS Installation Guide is a step-by-step guide to system installation and setup. It also includes information needed for pre-installation site planning and post-installation acceptance testing.
  • Page 20: Related Training

    Related training For detailed information about the training courses that are related to 1643 AM and 1643 AMS please refer to the 1643 AM and 1643 AMS Applications and Planning Guide, chapter 8 Product support - Training courses. Approval mark The following CE approval mark applies to this product.
  • Page 21: Alarm Messages

    • Subsequently the alarm messages that can be reported by 1643 AM and 1643 AMS systems are described in alphabetical order. Alarm descriptions Each alarm message is described using a tabular overview. The alarm descriptions are alphabetically ordered according to the alarm text.
  • Page 22 The “Alarm category” entry in the alarm overview table indicates the functional area to which the alarm belongs. The alarms that can be reported by 1643 AM and 1643 AMS systems can be divided into these alarm categories: • Environment Environment alarms are caused by defects detected in external devices which can be monitored.
  • Page 23 The “Reporting state (default setting)” entry in the alarm overview table indicates the factory settings of the corresponding alarm’s reporting state, i.e. whether an alarm is reported towards the management systems or not..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary Issue 4, May 2007 See notice on first page...
  • Page 24 2 Mbit/s Frame slip/skip count threshold crossing 15-min 1-29 2 Mbit/s Frame slip/skip count threshold crossing 24-hrs 1-30 2 Mbit/s Loss of frame alignment 1-31 2 Mbit/s Loss of input signal 1-32 ..............................................Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 25 LAN Loaded Sec for incoming traffic with class 3 green traffic Thr 1-65 24-hrs LAN Loaded Sec for Inc Tr with class 3 or 2 green traffic Thr 15min 1-66 ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary Issue 4, May 2007 See notice on first page...
  • Page 26 P12s Near-end background block errors thresh cross 24-hrs egress 1-97 P12s Near- end errored seconds threshold crossing 15-min 1-98 P12s Near- end errored seconds threshold crossing 24-hrs 1-99 ..............................................Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 27 SDSL Not expected input signal 1-130 SDSL unit failure 1-131 SDSL unit failure - protected 1-132 SDSL unit not present 1-133 SHDSL Near-end background block errors threshold crossing 15-min 1-134 ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary Issue 4, May 2007 See notice on first page...
  • Page 28 STM-1 interface extension board failure - protected 1-167 STM-1 interface extension board removed 1-168 STM-1 Loss of frame alignment 1-169 STM-1 Loss of input signal 1-170 ..............................................Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 29 STM-4 RS trace identifier mismatch 1-201 System timing in backup state 1-202 Timing link failed 1-203 Timing link unequipped 1-204 Total Power Fail of Remote Power Supply 1-205 ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary Issue 4, May 2007 See notice on first page...
  • Page 30 VC-12 Path trace identifier mismatch 1-236 VC-12 Payload mismatch 1-237 VC-12 Remote defect indicator 1-238 VC-12 Unequipped 1-239 VC-12 Virtual concatenated failure of protocol received 1-240 ..............................................1-10 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 31 VC3-VCG total loss of capacity(transmission) 1-272 VC3-VCG partial loss of capacity(transmission) 1-273 VC-3 Virtual concatenated failure of protocol received 1-274 VC-3 Virtual concatenated failure of protocol transmitted 1-275 ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-11 Issue 4, May 2007 See notice on first page...
  • Page 32 WAN Loaded Sec for inc Tr with class 3 or class 2 green traffic Thr 1-305 24-hrs WAN Severly Loaded Sec for inc Tr with class 3 green traffic Thr 1-306 15min ..............................................1-12 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 33 X21 interface extension board removed 1-322 X21 interface loss of input signal 1-323 X21 interface interface not expected input signal 1-324 X21 output timing mode change 1-325 ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-13 Issue 4, May 2007 See notice on first page...
  • Page 34: Operation Modes

    ..............................................Slot modes The slots of a 1643 AM and 1643 AMS system can be occupied by a “unit”. A unit is either a main unit or a tributary unit. Usually, a unit occupies a single slot. However, some tributary units (i.e. legacy option boards, mounted on an adapter card) occupy two slots.
  • Page 35 The monitoring mode of a P11s or P12s trail termination point (TTP) can be set for each TTP individually to: • “Monitored” (MON), or • “Not monitored” (NMON)..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-15 Issue 4, May 2007 See notice on first page...
  • Page 36 The monitoring mode of a VC connection termination point (CTP) for non intrusive monitoring of a VC path can be set for each CTP individually to: • “Monitored” (MON), or • “Not monitored” (NMON)..............................................1-16 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 37 As there is no equipment protection of the 1.5 Mbit/s extension board, E11XcEQF, and E11XcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-17 Issue 4, May 2007 See notice on first page...
  • Page 38 As there is no equipment protection of the 1.5 Mbit/s extension board, E11XcEQF and E11XcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................1-18 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 39 Although the respective slot is provisioned to be equipped with a 1.5 Mbit/s extension board, no 1.5 Mbit/s extension board is present. Actions Install a 1.5 Mbit/s extension board, or change the provisioning (i.e. unassign the slot)..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-19 Issue 4, May 2007 See notice on first page...
  • Page 40 • Check intermediate cabling. Note(s) Depending on the provisioning: A Tributary Timing Reference Switch Request is generated to switch over to another timing source..............................................1-20 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 41 2. although an input signal is applied, the port is mistakenly provisioned “Not Monitored”. Actions Change the port monitoring mode to “Monitored”, or check the cabling (and re-arrange if necessary)..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-21 Issue 4, May 2007 See notice on first page...
  • Page 42 Note(s) The consequent action of this alarm is user provisionable (including but not limited to switching from the re-timed to the self-timed mode)..............................................1-22 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 43 0 is terminated, then AIS is inserted in the downstream direction. If the port is operated in ISDN mode, then RDI is inserted in the upstream direction..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-23 Issue 4, May 2007 See notice on first page...
  • Page 44 (default setting) Local indications – Cause Fault(s) in upstream external cabling or equipment. Actions Check upstream external cabling and equipment. Note(s) Threshold is not provisionable..............................................1-24 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 45 Alarm severity Prompt (default setting) Reporting state Reported (default setting) Cause Fault(s) in upstream external cabling or equipment. Actions Check upstream external cabling and equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-25 Issue 4, May 2007 See notice on first page...
  • Page 46 Actions Replace the 2 Mbit/s extension board. Note(s) As 1643 AM and 1643 AMS systems do not support hardware protection, E12XcEQF, and E12XcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................1-26 Alcatel-Lucent - Proprietary 365-312-803R7.2...
  • Page 47 Actions Replace the 2 Mbit/s extension board. Note(s) As 1643 AM and 1643 AMS systems do not support hardware protection, E12XcEQF, and E12XcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................365-312-803R7.2...
  • Page 48 Local indications The red “Fault” LED is lit. Cause Although the 1643 AM/1643 AMS is provisioned to be equipped with a 2 Mbit/s extension board, no 2 Mbit/s extension board is present. Actions Install a 2 Mbit/s extension board, or change the provisioning.
  • Page 49 E1 (2 Mbit/s) signal, usually a voice switch or 64- kbit/s level cross-connect. Actions Check the synchronisation trails to both the 1643 AM and 1643 AMS and the network element that generated the E1 (2 Mbit/s) signal. These two network elements should have their respective clocks traced back to the same synchronization source when the 1643 AM and 1643 AMS system is operated in the re-timed mode.
  • Page 50 E1 (2 Mbit/s) signal, usually a voice switch or 64- kbit/s level cross-connect. Actions Check the synchronisation trails to both the 1643 AM and 1643 AMS and the network element that generated the E1 (2 Mbit/s) signal. These two network elements should have their respective clocks traced back to the same synchronization source when the 1643 AM and 1643 AMS system is operated in the re-timed mode.
  • Page 51 0 is terminated, then AIS is inserted in the downstream direction. If the port is operated in ISDN mode, then RDI is inserted in the upstream direction..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-31 Issue 4, May 2007 See notice on first page...
  • Page 52 0 is terminated, then AIS is inserted in the downstream direction. If the port is operated in ISDN mode, then RDI is inserted in the upstream direction..............................................1-32 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 53 2. although an input signal is applied, the port is mistakenly provisioned “Not Monitored”. Actions Change the port monitoring mode to “Monitored”, or check the cabling (and re-arrange if necessary)..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-33 Issue 4, May 2007 See notice on first page...
  • Page 54 Note(s) The consequent action of this alarm is user provisionable (including but not limited to switching from the re-timed to the self-timed mode)..............................................1-34 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 55 Check upstream equipment (not part of the transmission system). Check the tributary transmitter port of the indicated tributary unit by looping the data at the DDF. Check upstream cabling or upstream equipment interface..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-35 Issue 4, May 2007 See notice on first page...
  • Page 56 As there is no equipment protection of the 34 Mbit/s extension board, E31XcEQF and E31XcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................1-36 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 57 As there is no equipment protection of the 34 Mbit/s extension board, E31XcEQF, and E31XcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-37 Issue 4, May 2007 See notice on first page...
  • Page 58 Local indications The red fault LED on the unit is lit. Cause Although the 1643 AM and 1643 AMS is provisioned to be equipped with a 34 Mbit/s extension board, no 34 Mbit/s extension board is present. Actions Install a 34 Mbit/s extension board, or change the provisioning (i.e. unassign the slot).
  • Page 59 Check the tributary receiver port of the indicated unit by looping the data at the DDF. • Check the transmitting equipment, including the configuration of the output power level. • Check intermediate cabling..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-39 Issue 4, May 2007 See notice on first page...
  • Page 60 2. although an input signal is applied, the port is mistakenly provisioned “Not Monitored”. Actions Change the port monitoring mode to “Monitored”, or check the cabling (and re-arrange if necessary)..............................................1-40 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 61 As there is no equipment protection of the 45 Mbit/s extension board, E32XcEQF, and E32XcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-41 Issue 4, May 2007 See notice on first page...
  • Page 62 As there is no equipment protection of the 45 Mbit/s extension board, E32XcEQF, and E32XcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................1-42 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 63 Although the respective slot is provisioned to be equipped with a 45 Mbit/s extension board, no 45 Mbit/s extension board is present. Actions Install a 45 Mbit/s extension board, or change the provisioning (i.e. unassign the slot)..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-43 Issue 4, May 2007 See notice on first page...
  • Page 64 Check the tributary receiver port of the indicated unit by looping the data at the DDF. • Check the transmitting equipment, including the configuration of the output power level. • Check intermediate cabling..............................................1-44 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 65 2. although an input signal is applied, the port is mistakenly provisioned “Not Monitored”. Actions Change the port monitoring mode to “Monitored”, or check the cabling (and re-arrange if necessary)..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-45 Issue 4, May 2007 See notice on first page...
  • Page 66 AIS has been inserted in the downstream direction. Actions Locally no actions need to be taken. Analyze the alarm state of the upstream equipment and take appropriate measures..............................................1-46 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 67 Failure in line unit in the remote network element or local unit failure in the station that reported the alarm. Actions Check remote line unit. Check local unit. Note(s) AU-AIS is inserted in the downstream direction..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-47 Issue 4, May 2007 See notice on first page...
  • Page 68 The value for the average round trip delay exceeded the provisioned threshold value. Actions Check the topology of the network and the load of ethernet traffic over the links..............................................1-48 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 69 The value for the average round trip delay exceeded the provisioned threshold value. Actions Check the topology of the network and the load of ethernet traffic over the links..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-49 Issue 4, May 2007 See notice on first page...
  • Page 70 Make sure that both ends of the DCC link are 1. enabled, and 2. configured for the same operation mode of the LAPD protocol (AITS or UITS)..............................................1-50 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 71 Ethernet interface of one NE to the Ethernet interface of another NE using the DCN as the transport medium. As the DCN is using OSI the IP PDUs will be embedded in OSI PDUs..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-51 Issue 4, May 2007 See notice on first page...
  • Page 72 The alarm is raised when the GFP (or LAP-S, or EoS, depending on the provisioning) frame synchronization is lost. Actions Check whether the VC cross-connection and/or mapping method are correct..............................................1-52 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 73 The common technology also depends on the type of Ethernet interface. On optical Ethernet interfaces for example, always Gigabit Ethernet in full duplex mode (1000Base-X full duplex) is assumed..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-53 Issue 4, May 2007 See notice on first page...
  • Page 74 Check connections between the indicated unit, the connecting panel, and the Digital Distribution Frame (DDF). Check upstream equipment (not part of the transmission system). Check intermediate cabling..............................................1-54 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 75: Ethernet Interface Not Expected Input Signal

    2. although an input signal is applied, the port is mistakenly provisioned “Not Monitored”. Actions Change the port monitoring mode to “Monitored”, or check the cabling (and re-arrange if necessary)..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-55 Issue 4, May 2007 See notice on first page...
  • Page 76: Failed Segment In Shdsl Span

    NTU and possibly with an SRU. Example This example illustrates the fault localization in case of a failed segment in an SHDSL span: ..............................................1-56 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 77 (located in the upstream direction between the LTU and the SRU where the LOSW condition is detected) then the “segd” bit is transparently passed through this SRU..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-57 Issue 4, May 2007 See notice on first page...
  • Page 78: Far End Client Signal Failure

    Fault in the LAN input signal at the remote end resulting in loss of signal or loss of character synchronization. Actions Repair the upstream signal interface..............................................1-58 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 79: Isdn-Pra Loopback Inband Activated From Far-End Exchange Termination

    Loopback has been enabled via SC-manager or Sa-bits for the ISDN interface. Actions Disconnect the loopback local or disconnect the loopback remote from far end..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-59 Issue 4, May 2007 See notice on first page...
  • Page 80: Is-Is Configuration Error

    (default setting) Local indications The red fault LED is lit. Cause IS-IS is not set on this network element. Actions Provision the correct IS-IS parameters..............................................1-60 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 81: Is-Is Level-2 Area Repair, Transmission/Configuration Error

    IS-IS Level-2 Area is not supported due to transmission or configuration errors. Actions Check the transmission and configuration data. If wrong, provision the correct IS-IS parameters..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-61 Issue 4, May 2007 See notice on first page...
  • Page 82: Lan Dropped Packets Threshold Crossing 15-Min

    Check upstream external cabling or equipment. Note(s) The counter only includes packets dropped due to errors. It does not include packets dropped due to congestion..............................................1-62 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 83: Lan Dropped Packets Threshold Crossing 24-Hrs

    Check upstream external cabling or equipment. Note(s) The counter only includes packets dropped due to errors. It does not include packets dropped due to congestion..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-63 Issue 4, May 2007 See notice on first page...
  • Page 84: Lan Loaded Sec For Incoming Traffic With Class 3 Green Traffic Thr 15Min

    3 frames. Note(s) A loaded second indicates the traffic overload in the network and therefore, is a monitoring parameter for planning the network traffic..............................................1-64 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 85: Lan Loaded Sec For Incoming Traffic With Class 3 Green Traffic Thr 24-Hrs

    3 frames. Note(s) A loaded second indicates the traffic overload in the network and therefore, is a monitoring parameter for planning the network traffic..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-65 Issue 4, May 2007 See notice on first page...
  • Page 86: Lan Loaded Sec For Inc Tr With Class 3 Or 2 Green Traffic Thr 15Min

    (green frames) is detected at the egress port of the upstream equipment. An equal number of severely loaded seconds and loaded seconds indicate that the rate control has not been provisioned correctly..............................................1-66 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 87: Lan Loaded Sec For Inc Tr With Class 3 Or 2 Green Traffic Thr 24-Hrs

    (green frames) is detected at the egress port of the upstream equipment. An equal number of severely loaded seconds and loaded seconds indicate that the rate control has not been provisioned correctly..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-67 Issue 4, May 2007 See notice on first page...
  • Page 88: Lan Severly Loaded Sec For Inc Tr With Class 3 Green Traffic Thr 15Min

    An equal number of severely loaded seconds and loaded seconds indicate that the rate control has not been provisioned correctly..............................................1-68 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 89: Lan Severly Loaded Sec For Inc Tr With Class 3 Green Traffic Thr 24-Hrs

    An equal number of severely loaded seconds and loaded seconds indicate that the rate control has not been provisioned correctly..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-69 Issue 4, May 2007 See notice on first page...
  • Page 90: Lan Severly Loaded Sec For Inc Tr With Cl 3 Or 2 Green Traffic Thr 15Min

    (green frames) is detected at the egress port of the upstream equipment. An equal number of severely loaded seconds and loaded seconds indicate that the rate control has not been provisioned correctly..............................................1-70 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 91: Lan Severly Loaded Sec For Inc Tr With Cl 3 Or 2 Green Traffic Thr 24-Hrs

    (green frames) is detected at the egress port of the upstream equipment. An equal number of severely loaded seconds and loaded seconds indicate that the rate control has not been provisioned correctly..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-71 Issue 4, May 2007 See notice on first page...
  • Page 92: Lan Unit Failure

    As there is no equipment protection of the TransLAN option board, IPcEQF, and IPcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................1-72 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 93: Lan Unit Failure - Protected

    As there is no equipment protection of the TransLAN option board., IPcEQF and IPcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-73 Issue 4, May 2007 See notice on first page...
  • Page 94: Lan Unit Removed

    Although the respective slot is provisioned to be equipped with a TransLAN ® option board, no TransLAN option board is present. ® Actions Install a TransLAN option board, or change the provisioning (i.e. unassign the slot)..............................................1-74 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 95: Loss Of Q2-Communications

    DCN settings: Management → Overlay Comms Network → DCN → Edit → OK. • It is also possible that the SEEPROM is defective, or the contents is corrupt..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-75 Issue 4, May 2007 See notice on first page...
  • Page 96 Loss of Q2-communications Note(s) In general this alarm will only be reported on the ITM-CIT since the ITM-SC will have lost association with the network element..............................................1-76 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 97: Loss Of Signal On Ntu Customer Port

    Loss of signal on the end-user interface of the external NTU modem. Actions Clear the loss of signal condition by e.g. checking physical connections, cabling, and the related receiver and transmitter..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-77 Issue 4, May 2007 See notice on first page...
  • Page 98: Loss Of Voltage Power Feed A

    Power Distribution Panel (PDP), or the corresponding circuit breaker is opened, or the corresponding fuse is blown. Actions Check the power supply cabling, circuit breakers and fuses..............................................1-78 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 99: Loss Of Voltage Power Feed B

    Power Distribution Panel (PDP), or the corresponding circuit breaker is opened, or the corresponding fuse is blown. Actions Check the power supply cabling, circuit breakers and fuses..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-79 Issue 4, May 2007 See notice on first page...
  • Page 100: Mac Address Mismatch For Lan/Wan Port

    MAC address list. Actions Adapt the static MAC address list if the received MAC address pertains to an addresse relevant to the list..............................................1-80 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 101: Mandatory Is-Is Parameters Missing

    Local indications The red fault LED is lit. Cause Not all IS-IS parameters are correctly set for this mode. Actions Provision the IS-IS parameters correctly..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-81 Issue 4, May 2007 See notice on first page...
  • Page 102: Maximum Number Of Vlan Instances Exceeded

    VLAN instances is limited by the number of TransLAN units installed in combination with the maximum number of VLAN instances that can be stored in the management information base (MIB)..............................................1-82 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 103: Maximum Number Of Vlan Instances Exceeded In Mib

    VLAN instances. Note(s) A maximum number of 1024 VLAN instances per network element is supported. A maximum number of 2000 VLAN/port associations is supported..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-83 Issue 4, May 2007 See notice on first page...
  • Page 104: Maximum Round Trip Delay Threshold Crossing 15Min

    The value for the maximum round trip delay exceeded the provisioned threshold value. Actions Check the topology of the network and the load of ethernet traffic over the links..............................................1-84 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 105: Maximum Round Trip Delay Threshold Crossing 24Hrs

    The value for the maximum round trip delay exceeded the provisioned threshold value. Actions Check the topology of the network and the load of ethernet traffic over the links..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-85 Issue 4, May 2007 See notice on first page...
  • Page 106 MDIs can thus be used to trigger the reporting of application-specific environmental alarms. Each MDI can be assigned a descriptive text identifying the type of environmental alarm condition in more detail..............................................1-86 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 107 MDIs can thus be used to trigger the reporting of application-specific environmental alarms. Each MDI can be assigned a descriptive text identifying the type of environmental alarm condition in more detail..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-87 Issue 4, May 2007 See notice on first page...
  • Page 108 MDIs can thus be used to trigger the reporting of application-specific environmental alarms. Each MDI can be assigned a descriptive text identifying the type of environmental alarm condition in more detail..............................................1-88 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 109 MDIs can thus be used to trigger the reporting of application-specific environmental alarms. Each MDI can be assigned a descriptive text identifying the type of environmental alarm condition in more detail..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-89 Issue 4, May 2007 See notice on first page...
  • Page 110 The connection for the round trip delay measurement test was timed-out. Actions Check the topology of the network and the load of ethernet traffic over the links..............................................1-90 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 111 The connection for the round trip delay measurement test was timed-out. Actions Check the topology of the network and the load of ethernet traffic over the links..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-91 Issue 4, May 2007 See notice on first page...
  • Page 112 Local indications – Cause Fault(s) in upstream external cabling or equipment. Actions Check upstream external cabling and equipment. Note(s) The fault detection monitors on ts0 ..............................................1-92 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 113 Alarm severity Deferred (default setting) Reporting state Reported (default setting) Cause Fault(s) in upstream external cabling or equipment. Actions Check upstream external cabling and equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-93 Issue 4, May 2007 See notice on first page...
  • Page 114 (default setting) Reporting state Not Reported (default setting) Local indications – Cause Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-94 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 115 (default setting) Reporting state Not Reported (default setting) Local indications – Cause Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-95 Issue 4, May 2007 See notice on first page...
  • Page 116 Alarm severity Information (default setting) Reporting state Not Reported (default setting) Cause Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-96 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 117 Alarm severity Information (default setting) Reporting state Not Reported (default setting) Cause Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-97 Issue 4, May 2007 See notice on first page...
  • Page 118 (default setting) Reporting state Not Reported (default setting) Local indications – Cause Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-98 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 119 (default setting) Reporting state Not Reported (default setting) Local indications – Cause Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-99 Issue 4, May 2007 See notice on first page...
  • Page 120 Alarm severity Information (default setting) Reporting state Not Reported (default setting) Cause Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-100 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 121 Alarm severity Information (default setting) Reporting state Not Reported (default setting) Cause Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-101 Issue 4, May 2007 See notice on first page...
  • Page 122 (default setting) Reporting state Not Reported (default setting) Local indications – Cause Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-102 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 123 (default setting) Reporting state Not Reported (default setting) Local indications – Cause Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-103 Issue 4, May 2007 See notice on first page...
  • Page 124 Alarm severity Information (default setting) Reporting state Not Reported (default setting) Cause Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-104 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 125 Alarm severity Information (default setting) Reporting state Not Reported (default setting) Cause Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-105 Issue 4, May 2007 See notice on first page...
  • Page 126 – Cause The alarm was generated because of a fiber cut or equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-106 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 127 – Cause The alarm was generated because of a fiber cut or equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-107 Issue 4, May 2007 See notice on first page...
  • Page 128 (default setting) Cause The alarm was generated because of a fiber cut or equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-108 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 129 (default setting) Cause The alarm was generated because of a fiber cut or equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-109 Issue 4, May 2007 See notice on first page...
  • Page 130 One or more VC-12 or MS faults in this or upstream network elements. Actions This message is always raised as a consequence of one or more equipment and/or transmission faults. Clear these alarms first..............................................1-110 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 131 One or more VC-12 or MS faults in this or upstream network elements. Actions This message is always raised as a consequence of one or more equipment and/or transmission faults. Clear these alarms first..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-111 Issue 4, May 2007 See notice on first page...
  • Page 132 Degraded signal condition on the end-user interface of the external NTU modem. Actions Clear the degraded signal condition by e.g. checking physical connections, cabling, and the related receiver and transmitter..............................................1-112 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 133 Loss of frame on the end-user interface of the external NTU modem. Actions Clear the loss of frame condition by e.g. checking physical connections, cabling, and the related receiver and transmitter..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-113 Issue 4, May 2007 See notice on first page...
  • Page 134 As no equipment protection exists for pluggable modules, PMcEQF, and PMcUPF are always reported simultaneously as a reminder that a pluggable module failure is service affecting..............................................1-114 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 135: Pluggable Module Failure - Protected

    As no equipment protection exists for pluggable modules, PMcEQF, and PMcUPF are always reported simultaneously as a reminder that a pluggable module failure is service affecting..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-115 Issue 4, May 2007 See notice on first page...
  • Page 136: Pluggable Module Removed

    The red fault LED associated to the failed pluggable module is lit. Cause Pluggable module not present. Actions Either re-insert or unassign the pluggable module..............................................1-116 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 137: Q-Lan Termination Loopback Failed

    SC-unit (which contains the Q-LAN device). In general this alarm will only be reported on the ITM-CIT since the ITM-SC will have lost association with the network element..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-117 Issue 4, May 2007 See notice on first page...
  • Page 138: Remote Power Supply Asymetrical Leakage Detected

    (default setting) Reporting state Reported (default setting) Local indications – Cause The remote power supply box is defective. Actions Identify and repair the power box..............................................1-118 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 139: Remote Power Supply Internal Overvoltage Detected And Shut Down

    The remote power supply box is subjected to a voltage higher than its operable capacity. Actions Operate the remote power supply box at a lower voltage..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-119 Issue 4, May 2007 See notice on first page...
  • Page 140: Rpsip 1:

    MDIs can thus be used to trigger the reporting of application-specific environmental alarms. Each MDI can be assigned a descriptive text identifying the type of environmental alarm condition in more detail..............................................1-120 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 141: Rpsip 2:

    MDIs can thus be used to trigger the reporting of application-specific environmental alarms. Each MDI can be assigned a descriptive text identifying the type of environmental alarm condition in more detail..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-121 Issue 4, May 2007 See notice on first page...
  • Page 142: Rpsip 3:

    MDIs can thus be used to trigger the reporting of application-specific environmental alarms. Each MDI can be assigned a descriptive text identifying the type of environmental alarm condition in more detail..............................................1-122 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 143: Remote Power Supply Is Autonomously Shut Down

    – Cause The remote power supply box has been manually switched off. Actions Switch on the power box and provision the restart command through ITM-CIT..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-123 Issue 4, May 2007 See notice on first page...
  • Page 144: Remote Power Supply Open Circuit

    This can be caused by a blown fuse, faulty wiring, or missing components in the remote power supply box or even by manually disconnecting the power box. Actions Identify and repair the defective component in the power box..............................................1-124 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 145: Remote Power Supply Overload Detected

    Actions Incorporate suitable overload protection devices to prevent damage. Fuses and circuit breakers are commonly used for this purpose..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-125 Issue 4, May 2007 See notice on first page...
  • Page 146: Sdsl Excessive Bit Error Rate

    More than 37 CRC errors per second lead to an SDSLcDEG alarm. • More than 163 CRC errors per second lead to an SDSLcEXC alarm..............................................1-126 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 147: Sdsl Loss Of Frame Alignment

    LTU where the LOSW condition has been detected) functions properly. • Verify that the transmitter at the remote end of the SHDSL segment (i.e. at the next attached SHDSL device) functions properly..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-127 Issue 4, May 2007 See notice on first page...
  • Page 148: Sdsl Loss Of Input Signal

    A Tributary Timing Reference Switch Request is generated to switch over to another timing source. The remote alarm indication (Remote Defect Indicator) is activated towards the upstream equipment..............................................1-128 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 149: Sdsl Moderate Block Error Rate

    More than 37 CRC errors per second lead to an SDSLcDEG alarm. • More than 163 CRC errors per second lead to an SDSLcEXC alarm..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-129 Issue 4, May 2007 See notice on first page...
  • Page 150: Sdsl Not Expected Input Signal

    2. although an input signal is applied, the port is mistakenly provisioned “Not Monitored”. Actions Put the port in “Monitored”- state or check intermediate cabling..............................................1-130 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 151: Sdsl Unit Failure

    A hardware failure of the SHDSL extension board has been detected. Actions Replace the SHDSL extension board. Note(s) As 1643 AM and 1643 AMS systems do not support hardware protection, SDSLcEQF, and SDSLcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................
  • Page 152: Sdsl Unit Failure - Protected

    Equipment failure of the SHDSL extension board. Actions Replace the SHDSL extension board. Note(s) As 1643 AM and 1643 AMS systems do not support hardware protection, SDSLcEQF, and SDSLcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................
  • Page 153: Sdsl Unit Not Present

    Local indications The red “Fault” LED is lit Cause Although the 1643 AM/ 1643 AMS is provisioned to be equipped with an SHDSL option board, no SHDSL option board is present. Actions Install an SHDSL option board, or change the provisioning.
  • Page 154: Shdsl Near-End Background Block Errors Threshold Crossing 15-Min

    Check SHDSL connection on attenuation and crosstalk. Note(s) The default values of the raise and clear thresholds are fix preset. They cannot be changed by user provisioning..............................................1-134 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 155: Shdsl Near-End Background Block Errors Threshold Crossing 24-Hrs

    Check SHDSL connection on attenuation and crosstalk. Note(s) The default values of the raise and clear thresholds are fix preset. They cannot be changed by user provisioning..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-135 Issue 4, May 2007 See notice on first page...
  • Page 156: Shdsl Near-End Errored Seconds Threshold Crossing 15-Min

    Check SHDSL connection on attenuation and crosstalk. Note(s) The default values of the raise and clear thresholds are fix preset. They cannot be changed by user provisioning..............................................1-136 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 157: Shdsl Near-End Errored Seconds Threshold Crossing 24-Hrs

    Check SHDSL connection on attenuation and crosstalk. Note(s) The default values of the raise and clear thresholds are fix preset. They cannot be changed by user provisioning..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-137 Issue 4, May 2007 See notice on first page...
  • Page 158: Shdsl Near-End Severely Es Threshold Crossing 15-Min

    Check SHDSL connection on attenuation and crosstalk. Note(s) The default values of the raise and clear thresholds are fix preset. They cannot be changed by user provisioning..............................................1-138 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 159: Shdsl Near-End Severely Es Threshold Crossing 24-Hrs

    Check SHDSL connection on attenuation and crosstalk. Note(s) The default values of the raise and clear thresholds are fix preset. They cannot be changed by user provisioning..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-139 Issue 4, May 2007 See notice on first page...
  • Page 160: Shdsl Near-End Unavailable Seconds Threshold Crossing 15-Min

    Check SHDSL connection on attenuation and crosstalk. Note(s) The default values of the raise and clear thresholds are fix preset. They cannot be changed by user provisioning..............................................1-140 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 161: Shdsl Near-End Unavailable Seconds Threshold Crossing 24-Hrs

    Check SHDSL connection on attenuation and crosstalk. Note(s) The default values of the raise and clear thresholds are fix preset. They cannot be changed by user provisioning..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-141 Issue 4, May 2007 See notice on first page...
  • Page 162: Shdsl Network Termination Unit Authentication Error

    – wiring error type III), then the NTU returns an error code (0xB1) to the LTU. If, after 3 retries, the authentication still remains unsuccessful, SHDSL Network Termination Unit authentication error alarm then an is reported..............................................1-142 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 163: Shdsl Network Termination Unit Configuration Command Incomplete

    (MIB) on the LTU and the actual configuration of the connected SHDSL device might differ. An invalid response leads to a “Configuration command incomplete” (CNC) alarm..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-143 Issue 4, May 2007 See notice on first page...
  • Page 164: Shdsl Network Termination Unit Embedded Operations Channel Failure

    (MIB) on the LTU and the actual configuration of the connected SHDSL device might differ. An invalid response leads to a “Configuration command incomplete” (CNC) alarm..............................................1-144 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 165: Shdsl Network Termination Unit Equipment Failure

    Alarm messages SHDSL Network Termination Unit equipment failure ..............................................This alarm message is not supported in 1643 AM and 1643 AMS releases prior to release 6.1! Alarm identifier NTUcEQF Information Failure in the external NTU modem. Alarm category Equipment ASAP...
  • Page 166: Shdsl Network Termination Unit Minor Internal Failure

    Alarm messages SHDSL Network Termination Unit minor internal failure ..............................................This alarm message is not supported in 1643 AM and 1643 AMS releases prior to release 6.1! Alarm identifier NTUcINTB Information Failure in the external NTU modem (not service-affecting). Alarm category...
  • Page 167: Shdsl Network Termination Unit New Device Detected

    Actions Perform a configuration download to the new NTU in order to download the existing configuration data, stored in the management information base (MIB) of the 1643 AM/ 1643 AMS network element (LTU), to the new NTU..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary...
  • Page 168: Shdsl Network Termination Unit Power Failure

    Alarm messages SHDSL Network Termination Unit power failure ..............................................This alarm message is not supported in 1643 AM and 1643 AMS releases prior to release 6.1! Alarm identifier NTUcPS Information NTU power failure Alarm category Equipment ASAP sdsl Alarm severity...
  • Page 169: Shdsl Network Termination Unit Software Download Complete

    “Software download complete” (SWDC) notification is generated as a reminder that a reset is required to activate the new software image. Actions Reset the NTU in order to activate the new software image..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-149 Issue 4, May 2007 See notice on first page...
  • Page 170: Shdsl Network Termination Unit Software Download Failure

    The autonomous software download to an NTU modem has failed, after a number of retries. Actions Check for other SHDSL alarms. Check the physical connection..............................................1-150 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 171: Shdsl Network Termination Unit Unmanageable Device Type

    Make sure to use an SHDSL device for which interworking is supported, and which is configured to operate in SDH mode (TU-12 mapping mode). Please refer to the 1643 AM and 1643 AMS Applications and Planning Guide for an overview of supported SHDSL devices.
  • Page 172: Shdsl Network Termination Unit Unprotected Failure

    Alarm messages SHDSL Network Termination Unit unprotected failure ..............................................This alarm message is not supported in 1643 AM and 1643 AMS releases prior to release 6.1! Alarm identifier NTUcUPF Information Failure in the external NTU modem. Alarm category Equipment ASAP...
  • Page 173: Shdsl Regenerator Unit Configuration Command Incomplete

    (MIB) on the LTU and the actual configuration of the connected SHDSL device might differ. An invalid response leads to a “Configuration command incomplete” (CNC) alarm..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-153 Issue 4, May 2007 See notice on first page...
  • Page 174: Shdsl Regenerator Unit Embedded Operations Channel Failure

    (MIB) on the LTU and the actual configuration of the connected SHDSL device might differ. An invalid response leads to a “Configuration command incomplete” (CNC) alarm..............................................1-154 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 175: Shdsl Regenerator Unit Equipment Failure

    Alarm severity Deferred (default setting) Reporting state Reported (default setting) Local indications – Cause Equipment failure of the SRU. Actions See the documentation of the SRU..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-155 Issue 4, May 2007 See notice on first page...
  • Page 176: Shdsl Regenerator Unit Minor Internal Failure

    (default setting) Reporting state Reported (default setting) Local indications – Cause Equipment failure of the SRU (not service-affecting). Actions See the documentation of the SRU..............................................1-156 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 177: Shdsl Regenerator Unit New Device Detected

    Actions Perform a configuration download to the new SRU in order to download the existing configuration data, stored in the management information base (MIB) of the 1643 AM/ 1643 AMS network element (LTU), to the new SRU..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary...
  • Page 178: Shdsl Regenerator Unit Software Download Complete

    “Software download complete” (SWDC) notification is generated as a reminder that a reset is required to activate the new software image. Actions Reset the SRU in order to activate the new software image..............................................1-158 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 179: Shdsl Regenerator Unit Software Download Failure

    The autonomous software download to an SRU has failed, after a number of retries. Actions Check for other SHDSL alarms. Check the physical connection. Check software version numbers..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-159 Issue 4, May 2007 See notice on first page...
  • Page 180: Shdsl Regenerator Unit Unmanageable Device Type

    Make sure that only SHDSL devices are used for which interworking is supported, and that at most two SRUs are added to an SHDSL link. Please refer to the 1643 AM and 1643 AMS Applications and Planning Guide for an overview of supported SHDSL devices.
  • Page 181: Shdsl Regenerator Unit Unprotected Failure

    Alarm severity Prompt (default setting) Reporting state Reported (default setting) Local indications – Cause Equipment failure of the SRU. Actions See the documentation of the SRU..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-161 Issue 4, May 2007 See notice on first page...
  • Page 182: Shdsl Span Discovery Procedure Takes Too Much Time

    This message is to be understood as an information rather than as an alarm. There are no further consequent actions. The discovery will continue to repeat until it completes..............................................1-162 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 183: Shdsl Wiring Error

    ..............................................Alarm identifier SDSLcSWE Information Between the SHDSL ports on the LTU (1643 AM/ 1643 AMS) and the SHDSL ports on the NTU modem, an incorrect wiring of cables has been detected. SHDSL Wiring Error Note that the alarm is applicable to NTU modems of type SDSL-NT10ETH only.
  • Page 184 SHDSL Wiring Error (NTUcNAE) and an alarm will be reported. The authentication error will be reported by the second LTU, because its authentication will not be accepted..............................................1-164 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 185: Station Clock Output Squelched

    Local indications – Cause The timing input reference signal is not available or the quality is too low. Actions Restore the timing input reference signal..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-165 Issue 4, May 2007 See notice on first page...
  • Page 186: Stm-1 Interface Extension Board Failure

    Remove the STM-1 interface extension board and replace it with another one. Note(s) As 1643 AM and 1643 AMS systems do not support hardware protection, STM1XcEQF, and STM1XcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting.
  • Page 187: Stm-1 Interface Extension Board Failure - Protected

    A hardware failure of the STM-1 interface extension board has been detected. Actions Replace the STM-1 interface extension board. Note(s) As 1643 AM and 1643 AMS systems do not support hardware protection, STM1XcEQF, and STM1XcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................
  • Page 188: Stm-1 Interface Extension Board Removed

    (default setting) Local indications The red “Fault” LED is lit. Cause Although the 1643 AM/ 1643 AMS is provisioned to be equipped with an STM-1 interface extension board, no STM-1 interface extension board is present. Actions Install an STM-1 interface extension board, or change the provisioning.
  • Page 189: Stm-1 Loss Of Frame Alignment

    Check upstream external cabling and equipment. Note(s) In the downstream direction, AIS is inserted. In the upstream direction, “Multiplex Section - Remote Defect Indicator” (MS-RDI) is inserted..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-169 Issue 4, May 2007 See notice on first page...
  • Page 190: Stm-1 Loss Of Input Signal

    The power level of the STM-1 receive signal (optical or electrical) is below a defined level and LOF is detected. In previous releases of the 1643 AMS (releases prior to release 5.0), this alarm may also indicate that an optical SFP module is not plugged.
  • Page 191: Stm-1 Ms Alarm Indication Signal Received

    Locally no actions need to be taken. Analyze the alarm state of the upstream equipment and take appropriate measures. Note(s) In the upstream direction, “Multiplex Section - Remote Defect Indicator” (MS-RDI) is inserted..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-171 Issue 4, May 2007 See notice on first page...
  • Page 192: Stm-1 Ms Moderate Block Error Rate

    Fault(s) in upstream external cabling or equipment. Actions Check optical connectors and/or the external cabling and equipment. Note(s) The signal degrade threshold can be provisioned by using the management system..............................................1-172 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 193: Ms Near-End Background Block Errors Threshold Crossing 15-Min

    Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-173 Issue 4, May 2007 See notice on first page...
  • Page 194 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-174 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 195 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-175 Issue 4, May 2007 See notice on first page...
  • Page 196 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-176 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 197 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-177 Issue 4, May 2007 See notice on first page...
  • Page 198 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-178 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 199 Cause Possible causes are: • Dirty optical connector(s). • Fiber cut. • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-179 Issue 4, May 2007 See notice on first page...
  • Page 200 Cause Possible causes are: • Dirty optical connector(s). • Fiber cut. • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-180 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 201 Check that the MSP group is correctly created at both ends of the line (both ends provisioned with the same MSP configuration). Check that interworking between the two MSP groups is possible..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-181 Issue 4, May 2007 See notice on first page...
  • Page 202 STM-1 LOF (Loss of frame). This is reported to the transmitting equipment via the Remote Defect Indication (RDI) which is used to draw local attention to the remote failure..............................................1-182 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 203 Check for the failed section and repair it. Note(s) In the downstream direction, AIS is inserted. In the upstream direction, “Multiplex Section - Remote Defect Indicator” (MS-RDI) is inserted on STM-1 level..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-183 Issue 4, May 2007 See notice on first page...
  • Page 204 2. although an input signal is applied, the port is mistakenly provisioned “Not Monitored”. Actions Change the port monitoring mode to “Monitored”, or check the cabling (and re-arrange if necessary)..............................................1-184 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 205 Check the correctness of the cross-connections. Determine in which node(s) the line cables are wrongly connected by interpreting the received STM-1 RS trace identifiers..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-185 Issue 4, May 2007 See notice on first page...
  • Page 206 Check upstream external cabling and equipment. Note(s) In the downstream direction, AIS is inserted. In the upstream direction, “Multiplex Section - Remote Defect Indicator” (MS-RDI) is inserted..............................................1-186 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 207 Check operation of the transmitter in the far-end station. Check for cable breaks or dirty connectors. Note(s) In the upstream direction, “MS - Remote Defect Indicator” is activated..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-187 Issue 4, May 2007 See notice on first page...
  • Page 208 Locally no actions need to be taken. Analyze the alarm state of the upstream equipment and take appropriate measures. Note(s) There are no actions needed concerning the indicated network element; alarm indication signal is only reported for information..............................................1-188 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 209 (default setting) Reporting state Reported (default setting) Local indications – Cause Fault(s) in upstream external cabling or equipment. Actions Check upstream external cabling and equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-189 Issue 4, May 2007 See notice on first page...
  • Page 210 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-190 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 211 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-191 Issue 4, May 2007 See notice on first page...
  • Page 212 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-192 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 213 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-193 Issue 4, May 2007 See notice on first page...
  • Page 214 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-194 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 215 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-195 Issue 4, May 2007 See notice on first page...
  • Page 216 Cause Possible causes are: • Dirty optical connector(s). • Fiber cut. • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-196 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 217 Cause Possible causes are: • Dirty optical connector(s). • Fiber cut. • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-197 Issue 4, May 2007 See notice on first page...
  • Page 218 STM-4 LOF (Loss Of Frame). This is reported to the transmitting equipment via the Remote Defect Indication (RDI) which is used to draw local attention to the remote failure..............................................1-198 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 219 One of more STM-4 or MS faults in this or upstream network elements, the effect of which could not be circumvented via protection. Actions Check for the failed section and repair it..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-199 Issue 4, May 2007 See notice on first page...
  • Page 220 2. although an input signal is applied, the port is mistakenly provisioned “Not Monitored”. Actions Change the port monitoring mode to “Monitored”, or check the cabling (and re-arrange if necessary)..............................................1-200 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 221 Check the correctness of the cross-connections. Determine in which node(s) the line cables are wrongly connected by interpreting the received STM-4 RS trace identifiers..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-201 Issue 4, May 2007 See notice on first page...
  • Page 222 Local indications – Cause No timing sources with sufficient quality and/or priority are present. Actions Restore original timing source or reconfigure the most reliable timing source..............................................1-202 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 223 Check upstream cabling. Note(s) 1643 AM and 1643 AMS systems only support the monitoring of one timing reference at a time. This means that for standby references, no timing link failure (due to frequency deviations for example) can be reported.
  • Page 224 No timing source assigned to a timing port in monitored state. Actions Define or change the timing link output reference signal at the far end upstream station..............................................1-204 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 225 Local indications – Cause The on board self-test circuitry indicates that an essential function of the unit has failed. Actions Replace the remote power supply box..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-205 Issue 4, May 2007 See notice on first page...
  • Page 226 Locally no actions need to be taken. Analyze the alarm state of the upstream equipment and take appropriate measures. Note(s) In the upstream direction, “VC-12 Remote Defect Indicator” is activated..............................................1-206 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 227 TU-12 Loss of pointer contains the faulty unit. Note(s) In the downstream direction, AIS is inserted In the upstream direction, “VC-12 Remote Defect Indicator” is activated..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-207 Issue 4, May 2007 See notice on first page...
  • Page 228 Locally no actions need to be taken. Analyze the alarm state of the upstream equipment and take appropriate measures. Note(s) In the upstream direction, “VC-3 Remote Defect Indicator” is activated..............................................1-208 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 229 In this condition, the node reporting TU-3 Loss of pointer contains the faulty unit. Note(s) In the upstream direction, “VC-3 Remote Defect Indicator” is activated..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-209 Issue 4, May 2007 See notice on first page...
  • Page 230 A unit is installed but it has not (yet) been provisioned. Actions Have the unit provisioned, or remove it from the indicated slot. Note(s) An empty slot, not configured, will not generate an alarm message..............................................1-210 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 231 (default setting) Reporting state Reported (default setting) Local indications – Cause Fault(s) in upstream external cabling or equipment. Actions Check upstream external cabling and equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-211 Issue 4, May 2007 See notice on first page...
  • Page 232 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-212 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 233 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-213 Issue 4, May 2007 See notice on first page...
  • Page 234 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-214 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 235 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-215 Issue 4, May 2007 See notice on first page...
  • Page 236 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-216 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 237 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-217 Issue 4, May 2007 See notice on first page...
  • Page 238 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-218 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 239 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-219 Issue 4, May 2007 See notice on first page...
  • Page 240 When the VC-11 is unprotected, then select an alternative VC-4 as server for the lower order VC. When the VC-11 is protected, then check for external switch commands locking the protection switch to a failed link connection..............................................1-220 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 241 Actions Check cross-connections. Check upstream external cabling and equipment. Check trace identifier provisioning in VC-11 source and sink functions..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-221 Issue 4, May 2007 See notice on first page...
  • Page 242 In the reporting Network Element: • In the upstream direction VC-11 Remote Defect Indicator (RDI) is inserted. • In the downstream direction the alarm indication signal is inserted..............................................1-222 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 243 Actions No alarms in the reporting node. React on the far-end alarms. Follow the clearing actions for those alarm(s)..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-223 Issue 4, May 2007 See notice on first page...
  • Page 244 When defining or changing cross-connections this alarm will almost inevitably come up as it is practically impossible to issue the changes at both sides exactly at the same time..............................................1-224 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 245 (default setting) Local indications – Cause Fault(s) in upstream external cabling or equipment. Actions Check upstream external cabling and equipment. Note(s) Threshold is not provisionable..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-225 Issue 4, May 2007 See notice on first page...
  • Page 246 (default setting) Reporting state Reported (default setting) Local indications – Cause Fault(s) in upstream external cabling or equipment. Actions Check upstream external cabling and equipment..............................................1-226 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 247 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-227 Issue 4, May 2007 See notice on first page...
  • Page 248 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-228 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 249 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-229 Issue 4, May 2007 See notice on first page...
  • Page 250 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-230 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 251 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-231 Issue 4, May 2007 See notice on first page...
  • Page 252 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-232 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 253 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-233 Issue 4, May 2007 See notice on first page...
  • Page 254 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-234 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 255 VC. When there is a protected lower order VC, check for external switch commands locking the protection switch to a failed link connection..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-235 Issue 4, May 2007 See notice on first page...
  • Page 256 Actions Check cross-connections. Check upstream external cabling and equipment..............................................1-236 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 257 If the received V5 signal label (V5 [5-7]) has a value other than “000” or “001”, then check if the mapping mode of the local and far-end nodes is the same..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-237 Issue 4, May 2007 See notice on first page...
  • Page 258 Path signal label mismatch, or tributary unit alarm indication signal received. Actions No alarms in the reporting network element. React on the far-end alarms. Follow the clearing actions for those alarm(s)..............................................1-238 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 259 When defining or changing a cross-connection this alarm will almost inevitably come up as it is practically impossible to issue the changes simultaneously at both sides..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-239 Issue 4, May 2007 See notice on first page...
  • Page 260 Inconsistent sequence numbers or CRC errors in control packets. Actions Check the provisioning of the source side. Make sure that LCAS is enabled at both sides, and that the used equipment can interwork..............................................1-240 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 261 (default setting) Local indications – Cause Inconsistent member status received. Actions Check the provisioning of the source side. Make sure that the used equipment can interwork..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-241 Issue 4, May 2007 See notice on first page...
  • Page 262 Actions Re-route the VC-12 paths in order to adjust the propagation delays of the individual VC-12 paths..............................................1-242 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 263 VC-12-4v VCGs are used to transport Ethernet traffic of up to approximately 8 Mbit/s capacity between the LTU and NTU modems of type SDSL-NT10ETH over multiple SHDSL links in parallel..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-243 Issue 4, May 2007 See notice on first page...
  • Page 264 The delay difference between the VC-12s in the Virtual Concatenation Group (VCG) exceeds the range that can be compensated by buffering. Actions Check the cross connect structure. Note(s) Re-plan the path of each VC-12 channel..............................................1-244 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 265 In this condition, the node VC-12 Virtual concatenated Loss of multiframe reporting contains the faulty unit. Note(s) AIS is inserted in the downstream direction..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-245 Issue 4, May 2007 See notice on first page...
  • Page 266 Identify the affected VC-12s by means of the alarms that are reported for these individual VC-12s (VC12cEXC, VC12cDEG, VC12cTIM or VC12cUNEQ for example), and clear these alarms..............................................1-246 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 267 Note(s) Generally it is recommended to have LCAS enabled, and apply “diverse routing” i.e. to route the members of the VCG via physically diverse routes..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-247 Issue 4, May 2007 See notice on first page...
  • Page 268 One or more received VC-12-Xv group members have equal sequence numbers. Actions Verify that the connections in the preceding network element(s) have been provisioned correctly..............................................1-248 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 269 (default setting) Reporting state Reported (default setting) Local indications – Cause Fault(s) in upstream external cabling or equipment. Actions Check upstream external cabling and equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-249 Issue 4, May 2007 See notice on first page...
  • Page 270 Clear the alarms that are reported for the members of the VC-12-Xv group, or for the VC-12-Xv group itself. Please refer to the corresponding alarm descriptions..............................................1-250 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 271 The payload composition of the VC-12-Xv is not as expected. Actions Check whether all source (far end) and sink payload composition labels of all VC-12-Xv group members are equal..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-251 Issue 4, May 2007 See notice on first page...
  • Page 272 LCAS is always enabled for an SHDSL NTU and therefore, it is recommended to apply “diverse routing” i.e. to route the members of the VCG via physically diverse routes..............................................1-252 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 273 (default setting) Local indications – Cause One or more VC-12s of the VCG have failed. Actions Identify and clear the alarms for the affected VC-12s..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-253 Issue 4, May 2007 See notice on first page...
  • Page 274 LCAS is always enabled for an SHDSL NTU and therefore, it is recommended to apply “diverse routing” i.e. to route the members of the VCG via physically diverse routes..............................................1-254 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 275 (default setting) Local indications – Cause One or more VC-12s of the VCG have failed. Actions Identify and clear the alarms for the affected VC-12s..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-255 Issue 4, May 2007 See notice on first page...
  • Page 276 (default setting) Reporting state Reported (default setting) Local indications – Cause Fault(s) in upstream external cabling or equipment. Actions Check upstream external cabling and equipment..............................................1-256 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 277 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-257 Issue 4, May 2007 See notice on first page...
  • Page 278 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-258 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 279 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-259 Issue 4, May 2007 See notice on first page...
  • Page 280 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-260 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 281 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-261 Issue 4, May 2007 See notice on first page...
  • Page 282 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-262 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 283 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-263 Issue 4, May 2007 See notice on first page...
  • Page 284 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-264 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 285 VC. When there is a protected lower order VC, check for external switch commands locking the protection switch to a failed link connection..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-265 Issue 4, May 2007 See notice on first page...
  • Page 286 A provisioned trace string inserted in a VC- 3 path was received corrupted or not at all, due to wrong configuration, hardware failures or transmission failures. Actions Check cross-connections. Check tributary cables and tributary interfaces of the unit..............................................1-266 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 287 VC-3 at its far-end station. Actions If the received payload is >=1, check if the mapping mode of the local and far-end network elements is the same..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-267 Issue 4, May 2007 See notice on first page...
  • Page 288 Actions No alarms in the reporting network element. React on the far-end alarms. Follow the clearing actions for those alarm(s)..............................................1-268 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 289 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..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-269 Issue 4, May 2007 See notice on first page...
  • Page 290 LCAS is always enabled for an SHDSL NTU and therefore, it is recommended to apply “diverse routing” i.e. to route the members of the VCG via physically diverse routes..............................................1-270 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 291 (default setting) Local indications – Cause One or more VC-3s of the VCG have failed. Actions Identify and clear the alarms for the affected VC-3s..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-271 Issue 4, May 2007 See notice on first page...
  • Page 292 LCAS is always enabled for an SHDSL NTU and therefore, it is recommended to apply “diverse routing” i.e. to route the members of the VCG via physically diverse routes..............................................1-272 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 293 (default setting) Local indications – Cause One or more VC-3s of the VCG have failed. Actions Identify and clear the alarms for the affected VC-3s..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-273 Issue 4, May 2007 See notice on first page...
  • Page 294 Inconsistent sequence numbers or CRC errors in control packets. Actions Check the provisioning of the source side. Make sure that LCAS is enabled at both sides, and that the used equipment can interwork..............................................1-274 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 295 (default setting) Local indications – Cause Inconsistent member status received. Actions Check the provisioning of the source side. Make sure that the used equipment can interwork..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-275 Issue 4, May 2007 See notice on first page...
  • Page 296 Actions Reroute the VC-3 paths in order to adjust the propagation delays of the individual VC-3 paths..............................................1-276 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 297 The delay difference between the VC-3s in the Virtual Concatenation Group (VCG) exceeds the range that can be compensated by buffering. Actions Check the cross connect structure. Note(s) Re-plan the path of each VC-3 channel..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-277 Issue 4, May 2007 See notice on first page...
  • Page 298 Otherwise (i.e. when no unit failure is reported), loop the STM-1 signal at the transmitting node and at the receiving node. In this condition, the node reporting VC-3 Loss of multiframe contains the faulty unit..............................................1-278 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 299 Identify the affected VC-3s by means of the alarms that are reported for these individual VC-3s (VC3cDEG, VC3cTIM or VC3cUNEQ for example), and clear these alarms..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-279 Issue 4, May 2007 See notice on first page...
  • Page 300 Note(s) Generally it is recommended to have LCAS enabled, and apply “diverse routing”, i.e. to route the members of the VCG via physically diverse routes..............................................1-280 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 301 VC-3 Virtual concatenated Sequence mismatch signal fail condition, then alarms are raised against all paths of the VCG, not only against the paths which actually have a sequence mismatch..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-281 Issue 4, May 2007 See notice on first page...
  • Page 302 (default setting) Reporting state Reported (default setting) Local indications – Cause Fault(s) in upstream external cabling or equipment. Actions Check upstream external cabling and equipment..............................................1-282 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 303 Clear the alarms that are reported for the members of the VC-3-Xv group, or for the VC-3-Xv group itself. Please refer to the corresponding alarm descriptions..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-283 Issue 4, May 2007 See notice on first page...
  • Page 304 If the unit failure is not reported, loop the STM-1 signal at the transmitting network element and at the receiving network element. In this condition, the network element reporting VC-4 Loss of multiframe contains the faulty unit..............................................1-284 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 305 (default setting) Reporting state Reported (default setting) Local indications – Cause Fault(s) in upstream external cabling or equipment. Actions Check upstream external cabling and equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-285 Issue 4, May 2007 See notice on first page...
  • Page 306 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-286 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 307 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-287 Issue 4, May 2007 See notice on first page...
  • Page 308 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-288 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 309 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-289 Issue 4, May 2007 See notice on first page...
  • Page 310 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................1-290 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 311 Local indications – Cause Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-291 Issue 4, May 2007 See notice on first page...
  • Page 312 Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. • VC-4 is not reported. Actions Check upstream external cabling or equipment..............................................1-292 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 313 Possible causes are: • Dirty optical connector(s). • Equipment fault(s) in the upstream station. • VC4 is not reported. Actions Check upstream external cabling or equipment..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-293 Issue 4, May 2007 See notice on first page...
  • Page 314 This alarm message is always raised as a consequence of one or more equipment and/or transmission faults. Refer to the description of the corresponding alarm messages..............................................1-294 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 315 Determine in which network element(s) the line cables are wrongly connected by interpreting the received VC-4 path trace identifiers. Check correctness of expected path trace identifier..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-295 Issue 4, May 2007 See notice on first page...
  • Page 316 VC-4 at its far-end station. Actions If the received payload label is >=1, check if the mapping mode of the local and far-end network elements is the same..............................................1-296 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 317 AU-4 Alarm indication signal received. Actions No alarms in the reporting network element. React on the far-end alarms. Follow the clearing actions for those alarm(s)..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-297 Issue 4, May 2007 See notice on first page...
  • Page 318 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..............................................1-298 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 319 It is not permitted to provision a VLAN which is currently in use in another virtual switch on the same data unit. Note(s) The required service cannot operate successfully..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-299 Issue 4, May 2007 See notice on first page...
  • Page 320 Check upstream external cabling or equipment. Note(s) The counter only includes packets dropped due to errors. It does not include packets dropped due to congestion..............................................1-300 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 321 Check upstream external cabling or equipment. Note(s) The counter only includes packets dropped due to errors. It does not include packets dropped due to congestion..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-301 Issue 4, May 2007 See notice on first page...
  • Page 322 3 frames. Note(s) A loaded second indicates the traffic overload in the network and therefore, is a monitoring parameter for planning the network traffic..............................................1-302 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 323 3 frames. Note(s) A loaded second indicates the traffic overload in the network and therefore, is a monitoring parameter for planning the network traffic..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-303 Issue 4, May 2007 See notice on first page...
  • Page 324 (green frames) is detected at the egress port of the upstream equipment. An equal number of severely loaded seconds and loaded seconds indicate that the rate control has not been provisioned correctly..............................................1-304 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 325 (green frames) is detected at the egress port of the upstream equipment. An equal number of severely loaded seconds and loaded seconds indicate that the rate control has not been provisioned correctly..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-305 Issue 4, May 2007 See notice on first page...
  • Page 326 An equal number of severely loaded seconds and loaded seconds indicate that the rate control has not been provisioned correctly..............................................1-306 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 327 An equal number of severely loaded seconds and loaded seconds indicate that the rate control has not been provisioned correctly..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-307 Issue 4, May 2007 See notice on first page...
  • Page 328 (green frames) is detected at the egress port of the upstream equipment. An equal number of severely loaded seconds and loaded seconds indicate that the rate control has not been provisioned correctly..............................................1-308 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 329 (green frames) is detected at the egress port of the upstream equipment. An equal number of severely loaded seconds and loaded seconds indicate that the rate control has not been provisioned correctly..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-309 Issue 4, May 2007 See notice on first page...
  • Page 330 The on board self-test circuitry indicates that an essential function of the 1643 AM/ 1643 AMS system has failed. In previous releases of the 1643 AMS (releases prior to release 5.0), this alarm may also indicate a failure of an SFP module.
  • Page 331 Wrong extension board inserted, or the inserted extension board is defective. Actions Replace the extension board , and insert an extension board of the provisioned type..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-311 Issue 4, May 2007 See notice on first page...
  • Page 332 Wrong extension board inserted, or the inserted extension board is defective. Actions Replace the extension board , and insert an extension board of the provisioned type..............................................1-312 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 333 The red fault LED on the unit is lit. Cause Wrong extension board inserted, or the inserted extension board is defective. Actions Insert a 34 Mbit/s extension board, or change the provisioning..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-313 Issue 4, May 2007 See notice on first page...
  • Page 334 The red fault LED on the unit is lit. Cause Wrong extension board inserted, or the inserted extension board is defective. Actions Insert a 45 Mbit/s extension board, or change the provisioning..............................................1-314 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 335 ® If a TransLAN card is actually present when the alarm is reported, then the ® TransLAN card is defective and has to be replaced..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-315 Issue 4, May 2007 See notice on first page...
  • Page 336 If a pluggable module of the correct type is already present in the respective socket when the alarm is reported, then the pluggable module is defective and has to be replaced..............................................1-316 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 337 The red “Fault” LED is lit. Cause Wrong extension board inserted, or the inserted extension board is defective. Actions Insert an SHDSL extension board, or change the provisioning..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-317 Issue 4, May 2007 See notice on first page...
  • Page 338 The red “Fault” LED is lit. Cause Wrong extension board inserted, or the inserted extension board is defective. Actions Insert an STM-1 interface extension board, or change the provisioning..............................................1-318 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 339 The red “Fault” LED is lit. Cause Wrong extension board inserted, or the inserted extension board is defective. Actions Insert an X.21 interface extension board, or change the provisioning..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-319 Issue 4, May 2007 See notice on first page...
  • Page 340 A hardware failure has been detected on the X.21 interface extension board. Actions Replace the X.21 interface extension board. Note(s) As 1643 AM and 1643 AMS systems do not support hardware protection, X21XcEQF, and X21XcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................
  • Page 341 A hardware failure has been detected on the X.21 interface extension board. Actions Replace the X.21 interface extension board. Note(s) As 1643 AM and 1643 AMS systems do not support hardware protection, X21XcEQF, and X21XcUPF are always reported simultaneously as a reminder that a hardware failure is service affecting..............................................
  • Page 342 Local indications The red “Fault” LED is lit. Cause Although the 1643 AM/ 1643 AMS is provisioned to be equipped with an X.21 interface extension board, no X.21 interface extension board is present. Actions Install an X.21 interface extension board, or change the provisioning.
  • Page 343 Local indications The red “Fault” LED is lit. Cause Possible causes may be a cable break or wrong physical connections for example. Actions Check the cabling..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-323 Issue 4, May 2007 See notice on first page...
  • Page 344 2. although an input signal is applied, the port is mistakenly provisioned “Not Monitored”. Actions Put the X.21 interface port “Monitored”, or check the cabling (and re-arrange if necessary)..............................................1-324 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 345 Actions Restore the original timing source, or reconfigure the most reliable timing source to improve the quality of the system clock..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary 1-325 Issue 4, May 2007 See notice on first page...
  • Page 347 Alarm Collection Unit. Radio Relay circuit pack that collects of equipment alarms, analogue measurements from internal monitoring points and calculation data. Add-Drop Multiplexer Administrative Unit (AU) Carrier for TUs ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-1 Issue 4, May 2007 See notice on first page...
  • Page 348 Anomaly A difference between the actual and the desired operation of a function. ANSI American National Standards Institute Automatic Protection Switching Alarm Suppression assembly ..............................................GL-2 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 349 A message transmitted from the controlled network element to the ITM-SC that was not a response to a command that originated in the ITM-SC..............................................B3ZS Bipolar 3-Zero Substitution B8ZS Bipolar 8-Zero Substitution BBTR Backplane Bus TRansceiver ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-3 Issue 4, May 2007 See notice on first page...
  • Page 350 Voice, data, and/or video communication at greater than 2 Mbit/s rates. Broadband Service Transport STM-1 concatenation transport over the SLM for ATM applications. BUSTR BUS Transmitter and Receiver ..............................................Channel Associated Signaling CATastrophic Cross-Connection, Cross-connect ..............................................GL-4 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 351 Configuration Management (CM) Subsystem of the ITM-SC that, among other things, configures the network and processes messages from the network..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-5 Issue 4, May 2007 See notice on first page...
  • Page 352 Data Terminating Equipment (DTE) Originates data for transmission and accepts transmitted data. Database Administrator A user who administers the database of the ITM-SC application. See also User Privilege..............................................GL-6 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 353 (node names) to addresses (node Id). There can be one DSNE per (sub)network. Disassembly Splitting up of a signal into its constituents as payload data and overhead (an indication of the direction of a signal)..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-7 Issue 4, May 2007 See notice on first page...
  • Page 354 Dual-Tone Multi-Frequency Dual Homing An STM-1/STM-4 ring with 1643 AM/ 1643 AMS equipment can be dual homed on a ring consisting of Metropolis® ADM (Universal shelf), Metropolis® ADM (Compact shelf), or WaveStar® ADM 16/1. Also STM-16 rings can be dual homed with the Metropolis®...
  • Page 355 The calculated average bit error rate over a data stream. Errored Second (ES) A performance monitoring parameter. End System ElectroStatic Discharge ESPG Elastic Store & Pointer Generator ETSI European Telecommunication Standardisation Institute ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-9 Issue 4, May 2007 See notice on first page...
  • Page 356 ..............................................GARP Generic Attribute Registration Protocol Gateway Network Element (GNE) Passes information between other network elements and management systems via a Data Communications Network..............................................GL-10 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 357 Overhead, and assembling/disassembling the complete higher order Virtual Container. Higher order Path Connection (HPC) Function that provides for flexible assignment of higher order Virtual Containers within an STM-N signal..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-11 Issue 4, May 2007 See notice on first page...
  • Page 358 Intermediate Frequency InterFace Terminal Integrated Transport Management Craft Interface Terminal (ITM-CIT) Local manager for SDH network elements in a subnetwork. Also called as Craft Interface Terminal..............................................GL-12 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 359 ITM-SC Administrator See ITM-SC System Administrator. ITM-SC System Administrator A user of the ITM-SC application with System Administrator privileges. See also User Privilege. International Telecommunications Union ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-13 Issue 4, May 2007 See notice on first page...
  • Page 360 LCAS → “Link Capacity Adjustment Scheme” (p. GL-15) Local Communications Network Linear Drop/Insert (Add-Drop) Light Emitting Diode Local Exchange Node Low Frequency ..............................................GL-14 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 361 A timing mode in which the terminal derives its transmit timing from the received line signal. Loss of pointer Loss of signal LOSW Loss of sync word ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-15 Issue 4, May 2007 See notice on first page...
  • Page 362 Under normal circumstances the MIB and MIB image of one Network Element are synchronized. Manager Is capable of issuing network management operations and receiving events ..............................................GL-16 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 363 A copy of each MIB is available in the EMS and is called the MIB image. Under normal circumstances, the MIB and MIB image of one node are synchronized. MIB image See Management Information Base..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-17 Issue 4, May 2007 See notice on first page...
  • Page 364 Provides capability of switching a signal from a working to a protection section. Multiplexer Section Shared Protection Ring (MS-SPRING) A protection method used in multiplex line systems..............................................GL-18 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 365 An end system address of the System Controller according to ISO 8348 AD2. The format is ISO_DCC_LUCENT, which has the following structure: Network Termination Unit (NTU) The system that contains the STU-R function. Network Maintenance Center ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-19 Issue 4, May 2007 See notice on first page...
  • Page 366 ITM-SC and are not currently protected by another ITM-SC. If the ITM-SC fails, the network elements in this domain are not managed by any ITM-SC. See also Geographic Redundancy. Null Pointer Indication ..............................................GL-20 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 367 Optical Carrier, Level n Optical Distribution Frame Optical Demultiplexer Unit Out of Frame Second Optical Interface Optical Multiplexer Unit Operations Network Out Of Frame Out Of Service ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-21 Issue 4, May 2007 See notice on first page...
  • Page 368 ..............................................GL-22 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 369 A proprietary physical link interface that supports the transport of 21 * 2 Mbit/s signals. Physical Interface, Plesiochronous Interface Peak Information Rate Pointer Justification Event ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-23 Issue 4, May 2007 See notice on first page...
  • Page 370 Protecting Domain The protecting domain for an ITM-SC contains all the network elements for which this manager is the secondary ITM-SC. See also Geographic Redundancy..............................................GL-24 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 371 Possible levels are: - PRC (Primary Reference Clock) - SSU_T (Synchronization Supply Unit - Transit) - SSU_L (Synchronization ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-25 Issue 4, May 2007 See notice on first page...
  • Page 372 Radio Relay circuit pack whose main function is to perform protection switching when the Alignment Switch in the demodulator unit is unable to perform protection switching. Remote Defect Indication (RDI) (formerly → FERF) ..............................................GL-26 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 373 Remote Switching Module RSOH Regenerator-Section OverHead; part of the SOH. RSTTP Regenerator Section Trail Termination Point Return to Zero ..............................................Service Affecting Synchronous Adapter Station Alarm Interface ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-27 Issue 4, May 2007 See notice on first page...
  • Page 374 SOH can be subdivided into MSOH (multiplex section overhead) and RSOH (regenerator section overhead). Support Entity Function (in NE) Self-healing A network’s ability to automatically recover from the failure of one or more of its components..............................................GL-28 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 375 DCC messaging channels that are located in the STM-N section overhead. Service Management Level SDH Management Network SDH Management Subnetwork SNC/I SubNetwork Connection (protection) / Inherent monitoring ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-29 Issue 4, May 2007 See notice on first page...
  • Page 376 An external clock may be connected to a Station Clock Input. Station Clock Output (SCO) A clock signal that can be used for other systems..............................................GL-30 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 377 SLM circuit pack that provides the cross-connect in the transmit direction between high speed line time slots and low speed tributaries. Switching Module (SM) An access module from the 5ESS switch..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-31 Issue 4, May 2007 See notice on first page...
  • Page 378 ..............................................Tunnel auto provisioning protocol Threshold Crossing Alert TCP/IP Transmission Control Protocol/Internet Protocol TDEV Timing Deviation Time Division Multiplexing ..............................................GL-32 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 379 A combined coding and modulation scheme for improving the reliability of a digital transmission system without increasing the transmitted power or the required bandwidth. TRansFer unit ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-33 Issue 4, May 2007 See notice on first page...
  • Page 380 Allows connected computer equipment to gracefully shutdown and therefore prevents damage in the case of a power failure. Also absorbs dips in the power supply..............................................GL-34 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 381 Long term variations of amplitude frequency components (below 10 Hz) of a digital signal from their ideal position in time. Wander can result in buffer problems at a receiver..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary GL-35 Issue 4, May 2007 See notice on first page...
  • Page 382 Radio Relay circuit pack that performs connections for protection switching and transmission of low priority traffic on the protection channel. XPIC Cross Polarization Interference Cancellation XMTR Switch Unit ..............................................GL-36 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 383 1-59 Monitoring modes, 1-14 ............. E12cNES, 1-33 MS1cAIS, 1-171 E12XcEQF, 1-27 LANcANM, 1-53 MS1cDEG, 1-172 E12XcUNI, 1-28 LANcLOS, 1-54 MS1cFOP, 1-181 E12XcUPF, 1-26 LANcNES, 1-55 ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary IN-1 Issue 4, May 2007 See notice on first page...
  • Page 384 SDSLNSEScTHR15, 1-138 NTUcSWDF, 1-150 PMcUPF, 1-114 SDSLNSEScTHR24, 1-139 NTUcUMD, 1-151 PMcWUP, 1-316 SDSLNUAScTHR15, 1-140 NTUcUPF, 1-152 POWAcFLR, 1-78 SDSLNUAScTHR24, 1-141 POWBcFLR, 1-79 Slot modes, 1-14 ..............................................IN-2 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...
  • Page 385 URTDMcTHR24, 1-91 VC12VcMND, 1-242 VC3VcTLCR, 1-270 ............. VC12VcPLCR, 1-253 VC3VcTLCT, 1-272 VC11cDEG, 1-211 VC12VcPLCT, 1-255 VC4cDEG, 1-285 VC11cPLM, 1-222 VC12VcPLM, 1-251 VC4cLOM, 1-284 VC11cRDI, 1-223 ..............................................365-312-803R7.2 Alcatel-Lucent - Proprietary IN-3 Issue 4, May 2007 See notice on first page...
  • Page 386 WANI3GEILScTHR24, 1-303 WANI3GEISLScTHR15, 1-306 WANI3GEISLScTHR24, 1-307 ............. X21cLOS, 1-323 X21cNES, 1-324 X21OTMcSW, 1-325 X21XcEQF, 1-321 X21XcUNI, 1-322 X21XcUPF, 1-320 X21XcWUP, 1-319 XRTDcTHR15, 1-84 XRTDcTHR24, 1-85 ..............................................IN-4 Alcatel-Lucent - Proprietary 365-312-803R7.2 See notice on first page Issue 4, May 2007...

This manual is also suitable for:

1643 am

Table of Contents