Alcatel-Lucent 1643 AMS · • Alcatel-Lucent 1643 AMS Release 7.2.11, SCA404L, 109782573. •...

Alcatel-Lucent - ProprietaryThis document contains proprietary information of

Alcatel-Lucent and is not to be disclosed or used except inaccordance with applicable agreements

Copyright © 2012 Alcatel-LucentUnpublished and Not for Publication

All Rights Reserved

Alcatel-Lucent 1643 AMSSoftware Release Description

Release 7.2.11

Issue 1August 2012

Alcatel-Lucent - ProprietarySee Notice on first page

This material is protected by the copyright and trade secret laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Alcatel-Lucent), except in accordance with applicable agreements, contracts, or licensing, without the express written consent of Alcatel-Lucent and the business management owner of the material.

For permission to reproduce or distribute, please contact your Account Executive.

Notice

The information in this document is subject to change without notice. Although every effort has been made to make this document as accurate, complete, and clear as possible, Alcatel-Lucent and its predecessors assume no responsibility for any errors that may appear in this document.

Federal Communications Commission (FCC) Notification and Repair Information

This equipment is designed to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions manual, may cause interference to radio communications. Operation of this equipment in a residence is likely to cause harmful interference, in which case, the user will be required to correct the interference at his own expense.

Security

In rare instances, unauthorized individuals make connections to the telecommunications network. In such an event, applicable tariffs require that the customer pay all network charges for traffic. Alcatel-Lucent and its predecessors cannot be responsible for such charges and will not make any allowance or give any credit for charges that result from unauthorized access.

Trademarks

Windows is a registered trademark of Microsoft Corporation.

Ordering Information

For information on how to order Alcatel-Lucent information products, see the “About this information product” section (Preface) of this document.

Support

Information Product Support Number

Alcatel-Lucent provides a referral telephone number for support. Use this number to report errors or to ask questions about the information in this product. This is a non-technical number. The referral number is 1 800 645 6759 or 1 317 322 6848.

Technical support

Technical assistance can be obtained by calling the International Customer Management Center (ICMC) at 00800 00 lucent (toll free inside EMEA) or +353 1 6924579 (toll) for in-hours and emergency out-of-hours support.

This document was developed by Alcatel-Lucent.

C O N T E N T Si

Alcatel-Lucent - ProprietarySee Notice on first page

Issue 1, August 2012

...........................................................................................................................................................................................................................................................

Contents

............................................................................................................................................................................................................................................................

1 Software Licenses and Features

Software Licences 1-2

New features introduced in R7.2.11 1-5











............................................................................................................................................................................................................................................................

2 Problems Fixed

Problems Fixed in Network Element Software Release 7.2.11 2-3










...........................................................................................................................................................................................................................................................

C O N T E N T Si i

Alcatel-Lucent - ProprietarySee Notice on first page Issue 1, August 2012


Problems Fixed in Network Element Software Release 7.2 2-16


Fixed Problems for ITM-CIT R18.10.00 2-22

............................................................................................................................................................................................................................................................

3 Known Problems

General Remarks 3-2

Known Problems in Network Element software Release 7.2.11 3-4

Known Problems for ITM-CIT R18.10.00 3-19

............................................................................................................................................................................................................................................................

4 New Installation

General Remarks 4-2

............................................................................................................................................................................................................................................................

5 Upgrade Procedures

ITM-CIT Upgrade 5-2

NE Software Upgrade General 5-3

NE Maintenance Upgrade With the ITM-CIT 5-5

NE Maintenance Upgrade with Lucent® OMS 5-7

Switch to TransLAN standard-compliant IEEE tagging modes 5-12

............................................................................................................................................................................................................................................................

6 Miscellaneous

Technical Support Services (TSS) 6-2

iAlcatel-Lucent - ProprietarySee Notice on first page


............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

About this information product

Purpose This document provides important information about known problems and problems fixed in the Alcatel-Lucent 1643 AMS Release 7.2.11 Network Element (NE) software and ITM-CIT (Craft Interface Terminal) software.

This document also provides procedures about how to install and/or upgrade the Alcatel-Lucent 1643 AMS NE and ITM-CIT software.

Reason for reissue This is the first issue.

Intended Audience This document is intended for those responsible for the installation, acceptance, operations and maintenance of Release 7.2.11.

How to Use This Document Section 1 - Software Licenses and Features

This section contains an explanation of the Software Licenses and new features introduced in this release.

Section 2 - Problems Fixed

This section provides descriptions of the problems that have been fixed in Alcatel-Lucent 1643 AMS Release 7.2.11 or before.

This section also provides a listing of problems that have been fixed in the ITM-CIT Release R18.10.00.

...........................................................................................................................................................................................................................................................

i i Alcatel-Lucent - ProprietarySee Notice on first page Issue 1, August 2012

Section 3 - Known Problems

This section provides descriptions and workarounds to existing problems in Alcatel-Lucent 1643 AMS Release 7.2.11 and ITM-CIT Release R18.10.00.

Section 4 - New Installation

This section provides a reference to the procedure to install the Alcatel-Lucent 1643 AMS Network Element (NE) software onto a new Alcatel-Lucent 1643 AMS system and a reference to the procedure to install the ITM-CIT (Craft Interface Terminal) software onto a Windows-based PC. Additionally it contains information that will contribute to a proper installation of the Alcatel-Lucent 1643 AMS.

Section 5- Upgrade Procedures

This section provides the procedure for a maintenance upgrade of the Alcatel-Lucent 1643 AMS Network Element (NE) software to Alcatel-Lucent 1643 AMS Release 7.2.11 if applicable.

The maintenance upgrade can be performed with the ITM-CIT (Craft Interface Terminal) or with the Lucent® OMS, and both procedures are given.

Section 6 - Miscellaneous

This section provides useful information to supplement the information provided in the previous sections.

How to Comment To comment on this information product, go to the Online Comment Form (http://www.alcatel-lucent-info.com/comments) or email your comments to the Comments Hotline ([email protected]).

Ordering Information The following is a list of described and referred Network Element (NE) and Craft Interface Terminal (CIT) software that can be ordered:

• Alcatel-Lucent 1643 AMS Release 7.2.11, SCA404L, 109782573.

• ITM-CIT, R18.10.00, SAA619K, 109796904.

The following is a list of related documents:

• Applications and Planning Guide, Release 1.0 through 7.2, 365-312-801R7.2, 109635771.

• Installation Guide, Release 1.0 through 7.2, 365-312-802R7.2, 109635797.

...........................................................................................................................................................................................................................................................

i i iAlcatel-Lucent - ProprietarySee Notice on first page


• User Operations Guide, Release 1.0 through 7.2, 365-312-807R7.2, 109635813.

• Alarm Messages and Trouble Clearing Guide, Release 1.0 through 7.2, 365-312-803R7.2, 109635763.

• Lucent® OMS Provisioning Guide for 1643 AM/AMS Release 7.2, 365-312-877R7.2, 109635805.

How to Order To order Alcatel-Lucent documents and courses, use the following websites, or the e-mail, phone, and fax contacts linked from “Contact Us” on the following sites:Documentation:http://support.alcatel-lucent.comTraining:http://support.alcatel-lucent.com

1 - 1Alcatel-Lucent - ProprietarySee Notice on first page


............................................................................................................................................................................................................................................................

1 Software Licenses and Features

............................................................................................................................................................................................................................................................

Overview

Purpose This section contains an explanation of the software licenses and new features introduced in this release.

Reason for revision This is the first issue.

Software Licenses and Features

...........................................................................................................................................................................................................................................................



Contents This section contains the following:

Software Licenses 1-2












...........................................................................................................................................................................................................................................................

Software Licenses and FeaturesSoftware Licences

1 - 3 Alcatel-Lucent - ProprietarySee Notice on first page Issue 1, August 2012

............................................................................................................................................................................................................................................................

Software Licences

The following open source software packages are used in the Alcatel-Lucent 1643 AMS R7.2.11 software:

Linux Kernel 2.4.20, licensed under the GNU General Public License, Version 2, see LINUX GPL below

MontaVista Linux 3.1,licensed under the GNU General Public License, Version 2, see LINUX GPL below

The following open source software was used during the Alcatel-Lucent 1643 AMS R7.2.11 software development process:

MontaVista Linux 3.1,licensed under the GNU General Public License, Version 2, see LINUX GPL below

GCC 3.2GCC 3.3.1,licensed under the GNU General Public License, Version 2 or later, see GPL V2 below

GDB 6.3GDB 6.0licensed under the GNU General Public License, Version 2 or later, see GPL V2 below

Binutils 2.12.1Binutils 2.13licensed under the GNU General Public License, Version 2 or later, see GPL V2 below

Net-SNMP 5.0.9,Licensed under serveral BSD/BSD-like license, see Net-SNMP license below

MySQL Ver 11.18 Distrib 3.23.58,Licensed under the GNU General Public License Version 2 and GNU Lesser General Public License 2.1, see GPL V2 and LGPL 2.1 below

Software Licenses and FeaturesSoftware Licences

...........................................................................................................................................................................................................................................................



CVS 1.11.18,Licensed under the GNU General Public License, Version 2 or later, see GPL V2 below

Bugzilla 2.16.5,Licensed under the MOZILLA Public License, Version 1.1 or later see MPL 1.1 below

If you want to receive the sources for the mentioned packages please contact your Alcatel-Lucent.

For further details about handling/usage and licensing of the contained/used open source software please check Alcatel-Lucent 1643 AMS R7.2.11 open source declaration file which is available on Alcatel-Lucent 1643 AMS Network Element (NE) Software Release R7.2.11 delivered on a CD-ROM (Comcode 109782573).

...........................................................................................................................................................................................................................................................

Software Licenses and FeaturesNew features introduced in R7.2.11


............................................................................................................................................................................................................................................................

New features introduced in R7.2.11

Existing features are not described in this document because this information is provided in the Applications, Planning and Ordering Guide, which is included in the Alcatel-Lucent 1643 AM/AMS documentation set.

The release R7.2.11 is a maintenance release which replaces the R7.2.10 software. Release R7.2.11 has the following new feature.

Support of SHDLSv3 Option Board (item code: CMC417C, comcode: 109782565). This Option Board is only supported on Alcatel-Lucent 1643 AMS, not on Alcatel-Lucent 1643 AM.

SHDSLv3 Option Board is supported since ITM-CIT R18.09.02. There is further enhancement in ITM-CIT R18.10.00 for SHDSLv3 option board.


...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................



The release R7.2.10 is a maintenance release which replaces the R7.2.9 software. Release R7.2.10 has no new features.

...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................




...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................



The release R7.2.7 is a maintenance release which replaces the R7.2.6 software. Release R7.2.7 has the following additional features:

Support of SFP Digital Diagnostic Monitoring on 1643AM/AMS, the DDM information can be viewed in ITM-CIT.


...........................................................................................................................................................................................................................................................

1 - 1 0Alcatel-Lucent - ProprietarySee Notice on first page


............................................................................................................................................................................................................................................................




...........................................................................................................................................................................................................................................................


1 - 1 1 Alcatel-Lucent - ProprietarySee Notice on first page Issue 1, August 2012

............................................................................................................................................................................................................................................................





...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................




Support of X2E3-V3 and X2DS3-V3 Option Boards.

This release supports the following two option boards:X2E3-V3 (item code: CMC407B, comcode: 109673004)X2DS3-V3 (item code: CMC408B, comcode: 109672998)

Support of X5IP-V2 Option Board.

This release supports the following option board:

X5IP-V2 (item code: CMC419B, comcode: 109667931)

...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................





...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................




SHDSL: Trib-to-Trib cross-connections.

When the LTU is set in LTU/TU12 mode, it supports the creation of cross-connections of VC12s between any two SHDSL ports. The management system enables the tasks related to the bi-directional VC-12 connection when the following two conditions are fulfilled:- An SHDSL option card is assigned to TP2. - The system is in LTU/TU12 mode.The management system interface lets you perform the following tasks:1. Create a bi-directional VC-12 connection.2. Delete the bi-directional VC-12 connection.3. View the status of a VC-12 Connection Point as Source.

MIB gets cleared after 5 boot rejections.

In case a MIB gets corrupt and/or the NE is getting an incorrect or corrupt MIB downloaded from the Management System, the NE may not be able to boot correctly. As a consequence, the NE remains in an infinite boot: the NE is no longer reachable by (Element) Management System or Craft Terminal (ITM-CIT). In this release, the “infinite reboot” is restricted to 5 retries. After 5 retries the NE will boot with an empty MIB, allowing the operator to download a correct MIB and/or commission with Craft Terminal.

...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................



Release R7.2.1 has the following additional features:

Extended MIB Upload/Download functionality.

The MIB Upload/Download tool (MUD), as introduced with Release R7.1, has an extended function set per release R7.2.1:- ITM-CIT password protection is implemented- Option to set MIB state to not-confirmed after download- MIB conversion between different AM/AMS mother boards (flexible item code).

X5IP: Enhanced Flow Classification.

The traffic of end users can be classified into flows on the edge ports of a TransLAN domain. For this purpose, ports can provisioned to be "Edge" or "Interior". Edge ports are either Customer Role ports (UNI) or "virtual ports" on a Trunk port (E-NNI). A virtual port is the traffic over a trunk port belonging to a single end-user, i.e. it is characterized by an S-VID tag. On edge ports up to 7 freely provisionable flows can be defined based on a combination of: - flow = port- flow = C-Tag(C-VID, C-UP) formerly: VID, UP- flow = IP-TOS field (DSCP)- flow = Destination Address Mask (for broadcast/multicast and for customer control traffic)In addition there is always a default flow for each user present.When ports are designated as "Interior", the flow classification will be based solely on the S-UPT bits. There is no rate control and the S-UPT bits are transparently transported through the device. Virtual ports on a trunk port can be provisioned to behave as "Interior" ports, i.e. to use the S-UPT bits for classification instead of the freely provisionable flow. By provisioning a (virtual) port an "Interior", the flow definition is fixed. Note: release R7.1 introduced this feature for X4IP-v2.


...........................................................................................................................................................................................................................................................



X5IP: Latency measurement (Round Trip Delay).

The Metropolis® AM/AMS supports end-to-end CPU in-band Round Trip Delay measurement using a retrieval function for the MAC-DA of the VS. Users can enable a repeated latency measurement to another network element in the TransLAN network using the MAC-DA, TC, the color (dropping precedence), and the V-LAN tag to identify the VS. The measured path follows the currently valid STP-topology. The RTD measurement accuracy is 4 ms.Note: release R7.1 introduced this feature for X4IP-v2.

X5IP: Manual MAC Address provisioning.

* It is possible to add static MAC entries in the FDB (not submitted to the ageing time process) and reversely possibility to delete some MAC entries from the FDB.* It is possible to enable/disable the MAC learning process per port.* It is possible to set a maximum number of MAC adddress entries learnded per VLAN.* It is possible to flush the whole dynamic FDB.* For automatic learning of MAC address, the aging pass timer can be provisioned for whole FDB from 10s to 630s in steps of 10s.* System supports to query the whole static MAC entries and the dynamic MAC address entry (MAC address + VLAN).* It's possible to set a port in locked mode. All new frames into this locked port will be dropped. This SA address will not be learned. Alarming would be reported against new frames in locked port mode.Note: release R7.1 introduced this feature for X4IP-v2.

X5IP: Enhanced Performance Monitoring.

It is possible to monitor packet related performance parameters on any external Ethernet port and any WAN port. Examples are counters fro multicast, unicast and broadcast frames, as well as crc errored and pause frames. Furthermore it is possible to monitor the performance parameters in byte per Traffic Class, service fow and congestion. Note: release R7.1 introduced this feature for X4IP-v2.

X5IP: Provisionable CBS.

Two extended parameters can be provisioned to QoS profiles for both IEEE802.1Q and IEEE802.1ad: CBS (Committed Burst Size), PBS (Peak Burst Size). Note: release R7.1 introduced this feature for X4IP-v2.

...........................................................................................................................................................................................................................................................



TransLAN: Outloops on Ethernet ports in repeater mode.

The user can set outgoing loopbacks on Ethernet and fast Ethernet outputs ports of X8PL, X4IP-v2 and X5IP, in case that port is part of a repeater switch. I.e. the outgoing signal is looped back to the corresponding input directly before leaving the system. These loopbacks can be setup per output E/FE port. On X5IP loopbacks in GbE can also be set.

Alarm Severity Assignment Profile Support (ASAP).

This release supports Alarm Severity Assignment Profiles to control the alarm reporting with flexibility. Each reported fault cause of the NE is contained by one profile type. Each alarm profile contains the follwoing information(1) alarm profile name(2) alarm profile type(3) fault list (fault causes, fault severity and reported flag)

SHDSL: Remote CSF alarm supported on modems.

This release supports the alarm Remote CSF (RCSF) for the modems (CSF = GFP Client Signal Fail signalling). Note that this kind of alarm is already supported by the X5IP and other Alcatel-Lucent products supporting Link Pass Through (LPT) functionality.



............................................................................................................................................................................................................................................................

2 Problems Fixed

............................................................................................................................................................................................................................................................

Overview

Introduction This section provides descriptions of the problems that have been fixed in Alcatel-Lucent 1643 AMS Release 7.2.11 or before.


Contents This chapter contains the following:












...........................................................................................................................................................................................................................................................

Problems Fixed




Fixed Problems for ITM-CIT R18.10.00 2-22

Problems FixedProblems Fixed in Network Element Software Release 7.2.11

...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................

Problems Fixed in Network Element Software Release 7.2.11

7.2_AR1-3477291 AMS:15 minutes Performance Monitoring counter still counts even after traffic is stopped.

After setting up the traffic between a NT10ETH SHDSL modem and the SHDSL card, the 15 minutes performance monitoring counter is still counting even fter the traffic is stopped.

7.2_AR1-3851070 AMS:Default Oversubscription mode (enabled/disabled) is different for the first created Virtual Switch and all the following created Virtual Switches on X5IP.

The first created Virtual Switch has the oversubscription enabled while all the following created Virtual Switches have the oversubscription disabled.

3.0_CPDnb01974 AMS:SHDSL Trib available for station clock timing.

It is possible to select the SHDSL trib port as input for the station clock (select TRIB_2 when an SHDSL board is present in TS2). However the SHDSL port can not serve as a timing reference.

...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................


7.2_CPDnb42766/AR1-2084071/AR1-3143510

OMS/AMS:Alarm problems after VCG modify requested capacity.

After the modification of the Requested Capacity of a VCG with VC12 servers (from 4 to 2 and then from 2 to 4) on the 3rd VC12-server, VC12cUNEQ was displayed on OMS, but this alarm did not appear in the CIT. After the synchronization (all information) from OMS to the AMS the alarm still exists. Only after deactivation and activation of the OMS communication to the AMS, the alarm VC12cUNEQ disappeared.


...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................


7.2_CPDnb45301/AR1-2753360

AMS Software Update from R7.2.6 (SCA404G) to R7.2.8 (SCA404I) leads to X8PL ports go down.

After AMS Software is upgraded from R7.2.6 to R7.2.8, traffic of Ethernet on X8PL is down. The Port switched from Full Duplex to Half Duplex due to the Autonegotiation problem. Only activating/deactivating of the Autonegotiation Function solves the issue.

7.2_CPDnb45305/AR1-2755190

X8PL Autonegotiation Problem in R7.2.8 (SCA404I).

After the customer Equipment is power off or the LAN connection is interrupted, the Port Settings of X8PL need to change the config to "Autoneg" again to get the correct config back.

...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................


7.2_CPDnb40301/AR1-2210013

VC3 SNCP is not behaving as it is expected.

After LOS on SNCP worker section of a TU12/TU3/TU3 structured VC4, TU3cLOP gets reported and after clearance of the LOS situation, TU3cLOP will not clear even reconnect fiber. Therefore when remove fiber from the protection SNCP, traffic can not switch because the worker SNCP is still defective.

This situation does prevent SNCP to switching back to worker when a problem occurs on the protection section.

7.2_CPDnb40313/AR1-2173673

OMS Management System reports wrong PDE Performance Monitoring values.

The 1643 AM/AMS does not compress the PDE (Packets Dropped due Error), resulting in random PDE values on OMS Performance Monitoring screens.

7.2_CPDnb40672/AR1-2156983

DCC interworking problem with DACS 4/4/1.

In a setup where 1643 AM/AMS interworks via DCC with DACS 4/4/1, the DCC connection status may not be correctly populated in DCC neighbors and AREA information screens.

7.2_CPDnb41586/AR1-1934035

X8PL lock up after customer equipment reboot.

After a customer equipment (Cisco 2590) reboot, the link with the X8PL PHY may not be established correctly, resulting in, for example, one-way traffic only. A power down of the X8PL (and thus the whole 1643 AM/AMS) is necessary to resolve this issue.

7.2_CPDnb41754/AR1-2423869

Performance monitoring problems on AMS release SCA404H.

When migration from SCA404F to SCA404H, 15 min PM block after a few hours. The “elapsed time” stays to “00:00:00”. After reboots of the AMS, PMs restart but will re-block after a few hours.


...........................................................................................................................................................................................................................................................



7.2_CPDnb42051/AR1-1989681

X5IP: Fault LED not lit when PMc-UNI alarm raised.

When remove the acceptable SFP with Fiber looped, PMc-UNI alarm raises, but the Falut LED does NOT lit.

7.2_CPDnb42052/AR1-2419701

X5IP: rSTP incorrect when unidirectional transmission problem.

When no traffic received on the WAN, the STP does NOT change the port status: the ports stay in forwarding while the link is only working in one direction.

...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................


7.2_CPDnb37942/AR1-1971777

X5IP: no VS reference in VCG Information Window.

After creating Virtual Switch on X5IP with WAN port assigned, the VS identifier is not displayed in VCG overview window.

7.2_CPDnb38146/AR1-1918363

RTD feature malfunction on X5IP.

In some cases, the Round Trip Delay measurement feature (RTD) on the X5IP card will not work (the initiation of RTD measurement leads to a time out) even though network connection is working.


...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................


7.2_CPDnb37496/AR1-1896669

SDSL alarm shown on OMS not synchronized.

In diagnostic mode, SDSLcLOF might be raised at SRU2.xyz.NP1/CP1 as consequence of a Line-Interruption between the SRU and the connected Device in direction of Customer-Equipment (Customer Side). Under some circumstances, after restoring the line connection, this alarm will not be cleared from OMS alarm list.

7.2_CPDnb37873/AR1-1856926

STP switch on X5IP malfunction after long time running.

If STP or GVRP is enabled on X5IP, the STP protocol may fail after running for a long time (around 50 days). In this situation any network change will be traffic affecting.

...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................


7.2_CPDnb36881/AR1-1867449

LCAS doesn’t work on X8PL VCGs when running software release R7.2.4.

If one NE is running software release R7.2.4 or is being upgraded to R7.2.4 from previous releases, in case LCAS is being enabled on X8PL VCG, the NE might reboot continuously and management connection between the NE and ITM-CIT or Navis OMS will be lost and can not be regained.


...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................


5.0_CPDnb10941 Power cycle needed when Fast Download Tool is used.

In case the NE software has been downloaded using the Fast Download Tool (FDT) the NE might not start up as expected. Therefore the NE shall be power cycled every time the NE software is downloaded with use of the FDT.

6.1_CPDnb33111/AR1-1650835

AM/AMS may switch up 21 x TU12 AIS when interworking with 5ESS.

The AM/AMS internal architecture can support both SDH and SONET mode. In the SDH mode there is just one column of path Overhead (OH) for a VC4, where in SONET mode there are 3 columns of OH, each representing an STS1. For the AM/AMS in SDH mode the consequent actions for the Trail Signal Label (TSL) in the not used columns of the SONET (STS1) OH is, incorrectly, not disabled. This, in combination with the fact that the 5ESS is generating random stuff bytes in the VC4 path overhead (i.e. within ITU/ETSI requirements), may cause the AM/AMS to react on a persistent not expected STS1 TSL, by switching up 21 x TU12 AIS. This is observed on trunked voice traffic which is, within the AM/AMS going through the low order cross-connect.

7.2_CPDnb35162/AR1-1734937

Pluggable Module Failure raised on 1643 AM.

1643 AM units, having fixed lasers/receivers (contrary to1643 with Small Form Pluggable Optics), reports AM1cEQF, PMcEQF and PMcUPF in case of a defective laser and/or tranceiver. The "Pluggable Module Failure" Alarms should not be raised on units without Pluggable Modules (i.e on 1643 AM).

7.2_CPDnb35838/AR1-1776585

Outloop provisioning on customer side of SRU SDSL port not working.

From the management system a user can try to set an outloop on the customer side (SRU2xxx.CP) of an SRU (SHDSL Regenerator Unit). However, the AM/AMS is not forwarding the correct command to the remote device, and therefore the action is not implemented.

...........................................................................................................................................................................................................................................................



7.2_CPDnb36568/AR1-1749955/AR1-3921765

X5IP: Latency of TC3 flow too big when TC0 is bursty.

Changing TC0 from constant flooding to bursty loading could introduce 15ms additional delay in TC3.


...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................


7.2_CPDnb33000 X4IP-v2: Manual MAC entry should not be made for Multicast Address.

In case a Multicast Address in entered in the Manual MAC Address Table, with according VLAN, eventhough the particular VLAN is not (yet) provisioned as a Virtual Switch VLAN Member, traffic will still be forwarded to those ports. This does not apply to Unicast and Broadcast addresses.

7.2_CPDnb33214/AR1-1657986

X5IP: Latency VC3-xv for TC3 flow too high for small frames.

With RFC2544 latency test, carried out over a TC3 flow, and the path of the TC3 flow being congested by TC0 traffic (WAN is flooded by an FE port with 64 or 1600 byte frames), the RFC tests results show that the delay is too big for small frames.

7.2_CPDnb33214/AR1-1657986

Gateway address lost after reboot or power cycle.

The gateway address set on the Datacom Interface is lost after a reboot or power cycle of the Network Element. As a result, the Network Element may no longer be reachable by hosts outside the IP domain of the Network Element.

...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................


7.2_CPDnb29805 X5IP: ePCR PM counter does not increase when receiving CRC errored frames > 1518 bytes.

The ePCR counter (Ethernet Incoming Number of Frame with CRC Error) should increase for frames up to the supported length of 9216 bytes. CRC errored frames with length above 1518 are not counted.

7.2_CPDnb32049 X4IP-v2: inaccurate HQ and LQ frame counters.

On X4IP-v2, inaccurate values can be observed on the following High Quality (HQ) and Low Quality (LQ) counters:HQ: c3EIN, c2EIN, g2EINF, y2EINF, g3EINF, y3EINF, i3gEILS, i32gEILS, i3gEISLS, i32gEISLSLQ: g0EINF, y0EINF, g1EINF, y1EINFThe problem applies to the frame counters only, i.e. the HQ and LQ byte counters do not contain inaccuracy, and is especially likely to be seen after long term counting.

7.2_CPDnb33282/AR1-1587237

Infinite management loss of AM/AMS nodes with SHDSL spans.

After certain time of operation, AM/AMS with SHDSL option card can loose management with EMS/NMS. It is observed that the Fault LED is continuously lit and local craft terminal (ITM-CIT) is not able to login into the system.


...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................


7.1_CPDnb26875/AR1-1592002

SHDSL: Not possible to set CBS to value 0.

With the Lucent® OMS, the CBS (Commited Burst Size) on ports of NT10ETH modems can be configured between 0 and100. With the ITM-CIT, value "0" is rejected (values can be set here from 1 to 100).

7.2_CPDnb31613/AR1-1603312

In case an Etherloop is set the NE state stays Normal in stead of Abnormal.

Release 7.2 introduced Ethernet loops on repeater mode applications. When such a loop is enabled the NE state stays Normal while Abnormal state is expected.

7.x_CPDnb30321/AR1-1586682

Avarage latency exceeds 100ms in case WAN becomes congested.

In a configuration with multiple flows of different priorities, the traffic flow with the highest priority undergoes a too long latency in the event of a WAN congestion.

...........................................................................................................................................................................................................................................................

Problems FixedProblems Fixed in Network Element Software Release 7.2


............................................................................................................................................................................................................................................................

Problems Fixed in Network Element Software Release 7.2

7.1_CPDnb22536/AR1-1373213

Incorrect Performance Monitoring displayed for disconnected SHDSL modem.

The Performance Report List (Report Type: VC12, VCG, LAN, SHDSL) shows values (0 errors) for SHDSL-NTs (modems) although the managment link to the NT is down.

7.1_CPDnb27248 X5IP can report Wrong Pluggable Module after SFP replacement.

When a 2K EEPROM based GbE SFP is changed with a 1 K EEPROM based SFP, the inserted SFP is rejected by the software.

7.1_CPDnb27303 Traffic control has no effect for X4IP-v2 Virtual Switch in M-LAN mode.

When CIR is set to xMb/s and the amount of traffic offered to that LAN port is more then xMb/s, Frames should be marked both green (x Mb/s) as Yellow (>> xMb/s). However, all the traffic of xMb/s is marked Green.

7.1_CPDnb27395 Continuous RoundTrip Delay Measurement (RTD): First bin data incorrect.

When RoundTrip Delay Measurement is provisioned in the Continuous Measurement Mode the first bin (both 15min and 24h) contain incorrect data. For example the aRTD counter (average) can have a lower value then the mRTD counter (minimum). Also the sRTDM counter for 15min does not equal the sRTDM for 24h (which should contain idemtical values).

7.1_CPDnb27427 X5IP Link LED indicates a valid link although link is down.

With X5IP port parameters set to 10Mb/FullDuplex (Auto-Negotiation disabled) the link LED is lit when this port is connected to a link partner with port parameters 100Mb/FullDuplex (Auto-Negotiation disabled).

Note: According to datasheet, this is correct behavior. Therefore this report has mistakenly be taken into the Known Problems section of release R7.1.


...........................................................................................................................................................................................................................................................



7.1_CPDnb27533 X5IP LAN2.1 Link LED not lit in case of 10Mb/FD.

With X5IP LAN2.1 port parameters set to 10Mb/FullDuplex (Auto-Negotiation disabled) the link LED will not lit eventhough this port is connected to a link partner with same, correct, port parameters 10Mb/FullDuplex (Auto-Negotiation disabled). This problem does not apply to other LAN ports on the X5IP.

7.1_CPDnb27693 RoundTrip Delay Measurement MAC address not displayed on ITM-CIT.

When using ITM-CIT to list all virtual switches on a pack, the RoundTrip Delay Measurement (RTD) MAC address is not displayed correctly until the "Virtual Switch Details" window is opened for that virtual switch.

7.1_CPDnb27907/AR1-1546773

X5IP can not generate Pause Frames.

Eventhough enabled, the X5IP can not generate Pause Frames to indicate towards link partner.

7.1_CPDnb28167/AR1-1547014

X5IP VCG capacity increment/reduction with LCAS enabled not hitless.

On a span between two X5IP VCG’s a hit is seen on incrementation/reduction of the VCG capacity, eventhough LCAS is enabled on both sides of the span.

7.1_CPDnb28623 Upgrade of 1643 AMS to R7.1 fails.

Some 5 minutes after switching the software stores to SCA403 (R7.1) the lasers of a 1643 AMS are shut off. Apart from traffic being lost, a DCC managed NE can therefore not be downloaded anymore with an (upgraded) MIB. Note: this does not apply to 1643 AM systems.

7.1_CPDnb28028/AR1-1549700

NTUcNDD alarm raised on span with SRU.

During a modem the New Device Detected alarm (NTUcNDD) is not expected to be raised. For a connection with a Repeater Unit (SRU) though the alarm is raised.

7.1_CPDnb28027/AR1-1545376

GbE port down after deleting a repeater with LPT enabled.

The link of a GbE port with LPT enabled goes down in case the switch is deleted.

...........................................................................................................................................................................................................................................................



7.1_CPDnb28418/AR1-1557746

No WAN side event filter implemented for LPT on X5IP.

A Hold-Off time af about 1 second should be implemented to allow SDH/VCAT layer to restore the VCG, such that short VCG interuptions do no trigger LPT.

7.1_CPDnb29161/AR1-1553461

Pause Frames not counted in Multicast counters.

Pause frames should be counted in eMPR and eMPS counters (Ethernet Incoming/outgoing Number of Good Multicast Frames), but are not.

7.1_CPDnb29689/AR1-1547936

Changing the TUG structure of TP2.1 reset the NE.

On X5IP the VC4 (TP2.1) has been structured VC12/VC12/VC12 per default. Changing the third TU tu TU3 structure makes the NE to reset. The NE comes back with the former TUG structure.


...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................

Problems Fixed in Network Element Software Release 7.1

Important! The Network Element Software Release R7.2 is based on a different Info Model as Release R7.1. An upgrade from R7.1 to R7.2 is therefore not possible with preservation of the MIB (i.e. switch - retain MIB). For more information on upgrades refer to section 4: Upgrade Procedures).

5.0_CPDnb09953 LANcNES alarms raised during TransLAN+ card (X4IP-v2) assignment state.

In case the LANcNES alarm is set to reported (Default is not reported) and the TransLAN+ changes from unassigned to assigned the LANcNES alarm is reported for all 4 lan ports, during the period from assignment till unit operation. LANcNES alarms are cleared once the unit is operational.

5.0_CPDnb11045 GVRP can be enabled even when the VS contains > 64 VLANs.

In case the dynamic VLAN registration protocol is enabled (GVRP) no more then 64 VLAN’s are supported. Current implementation does not prevent user the provision more then 64 VLANs with GVRP enabled.

5.0_CPDnb11060/6.1_CPDnb13740

NE does not support large amount of VLANs.

NE does not recover if power cycled when large number of VLANs are provisioned. In other test cases the NE was found to reset during creation of large number or VLANs.Note: This problem has been solved already by 1643 AM/AMS R6.1H, but has not been included on the SRD Fixed List of that release.

...........................................................................................................................................................................................................................................................



6.1_CPDnb16623 No progress indicator when downloading modem software.

When downloading software to a modem via the Lucent LTU, there is no progress indicator like it is during downloading software to the 1643 AM/AMS itself.

6.1_CPDnb16889 Alarm Instance Setting not available for SHDSL alarms.

The user can not set associated severities of SHDSL related alarms on a per-instance (e.g. port, TTP) base.

6.1_CPDnb16907 Sequence numbers should be ignored on Ethernet modems.

The accepted sequence numbers are not correctly displayed on the management systems. It is in all cases "0".

6.1_CPDnb17765 Manual Trigger Discovery needed to get management link up.

It is observed that with full NTU usage configurations (twelve connections with either NT10ETH and/or NT2M modems), not all management links with the modems will recover after an NE reset or power-cycle. Traffic over those links is not affected.Note: This problem has been solved already by 1643 AM/AMS R6.1H, but has not been included on the SRD Fixed List of that release.

6.1_CPDnb17847/AR1-1287067

X4IP-v2 option card tolerates inadequate QoS profiles.

From the different allowed CIR/PIR combinations the user might get the wrong impression a dual rate controller has been implemented instead of a single one. Depending on its provisioning the system will behave as follows:CIR=PIR --> Oversubscription= off.In case the CIR value is not 0, the PIR value will be treated as PIR=MAX and oversubscription is enabled.in case CIR is 0 and PIR is not 0 the rate controller will behave as a PIR limiter.

5.0_CPDnb21317/AR1-1368360

Node reset with purge LSP’s without area address.

Under certain conditions purge LSP's may lead to a DPS reset. Purge LSP's are not common in stable networks, hence this problem will usually not be noticed.


...........................................................................................................................................................................................................................................................



6.1_CPDnb22546/AR1-1373213

Incorrect performance display for SHDSL.

The Performance Report List (Report Type: VC12, VCG, LAN, SHDSL) shows values (0 errors) for SHDSL-NTUs although the managment link to that specific NTU is down.

6.1_CPDnb23883/AR1-1434886

NTUcLOSD alarm not forwarded to IMT-SC.

Correct SDSL Loss Of Signal alarming behavior:1. E12cLOS shall be reported for E1 port in TU12 mode. 2. LANcLOS shall be reported for ethernet port in TU12 mode.

...........................................................................................................................................................................................................................................................

Problems FixedFixed Problems for ITM-CIT R18.10.00


............................................................................................................................................................................................................................................................

Fixed Problems for ITM-CIT R18.10.00

None.



............................................................................................................................................................................................................................................................

3 Known Problems

............................................................................................................................................................................................................................................................

Overview

Introduction This chapter describes significant customer-affecting problems known to exist in Alcatel-Lucent 1643 AMS Release 7.2.11 Network Element software and ITM-CIT Release R18.10.00. Workarounds are provided where they apply.



General Remarks 3-2

Known Problems in Network Element software Release 7.2.11 3-4

Known Problems for ITM-CIT R18.10.00 3-19

...........................................................................................................................................................................................................................................................

Known ProblemsGeneral Remarks


............................................................................................................................................................................................................................................................

General Remarks

Interworking between X8PL/X5IP and X4IP-v2.

For X8PL/X5IP the Transmitted Virtual Concatenation Sequence numbers are filled in dynamically. Always the lowest TP number gets the lowest SQ nr, and so on. Additionally, the TP members in an X8PL/X5IP VCG group don't have to be consecutive. On the X4IP-v2 TransLAN card, the assignment is fixed according to the table below.

To prevent VC-x Virtual Concatenation sequence mismatch alarms, one should always Cross Connect the lowest X8PL/X5IP TP number to the X4IP-v2 TP with the lowest transmitted sequence number. If not, no traffic is possible towards the X4IP-v2 as it will not be able to reconstruct the virtually concatenated signal. This will be alarmed with a Sequence Number Mismatch alarm.

Small Form Factor Plugable (SFP) validity checking.

Since Release 5.0 the SFP checking is active and will raise alarms in case an unsupported SFP is inserted.

The Alarm Supervision feature has not fully been certified.

When using the Alarm Supervision feature unusual behaviour can not be fully excluded.

SHDSL: Change of configuration.

A change from a running modem configuration to another modem configuration should always be preceded by execution of ‘Drop Remote Configuration’ command.

Wan Port 1 Wan Port 2 Wan Port 3 Wan Port 4 Tr SQ nr

TP2.1311 TP2.1361 TP2.1342 TP2.1323 0

TP2.1321 TP2.1371 TP2.1352 TP2.1333 1

TP2.1331 TP2.1312 TP2.1362 TP2.1343 2

TP2.1341 TP2.1322 TP2.1372 TP2.1353 3

TP2.1351 TP2.1332 TP2.1313 TP2.1363 4

Known ProblemsGeneral Remarks

...........................................................................................................................................................................................................................................................



TransLAN: Maximum amount of VLANs.

For this release the operator should limit the amount of provisioned VLANs/CIDs on 1643 AM/AMS X4IP-V2 and X5IP TransLAN card to a maximum of 64, independent of GVRP being enabled or disabled.

As result of a warm reboot, PM counters may record UAS (UnAvailable Seconds).

This due the sequence in software component startup: the component handling PM may become active, while other software component might not yet be. These UAS counters may be counted even though traffic was not affected by the warm reboot.

Not Close Fast Download Tool Window in time may cause NE Recovery.

When Fast Download Tool (FDT) is used, if the new software image is not activated in time, and the FDT window is still open after the software download is successfully finished, the NE will recover after 5 to 10 minutes. It is recommended to activate the new software image within 5 minutes after the software download is finished.

Gracefully Assign/Unassign Option Card and Change/Change Back port mode

Do not run these toggling operations (assign/unassign option card, change/change back port mode) too quickly.

...........................................................................................................................................................................................................................................................

Known ProblemsKnown Problems in Network Element software Release 7.2.11


............................................................................................................................................................................................................................................................

Known Problems in Network Element software Release 7.2.11

PDH/SDH Related Problems See the following.

4.0_CPDnb04356 DS3 outloop is transparent.

Although the DS3 traffic can be looped in this release by provisioning an outloop, the set outloop acts transparent: it’s both looped back, as well as transmitted on the DS3 port.

Workaround:None.

4.0_CPDnb04920 No frequency monitoring on DS1 when having more references.

The DS1 frequency monitoring doesn't work when having more than one timing reference. The System Timing stays in locked mode on the DS1 ref, even when the selected reference is above +/- 20 ppm. When having only a DS1 reference it works fine. The behaviour is the same for mainboard (AMS DS1) and DS1 option board.

Workaround:None. When using a DS1 timing source, it is recommended to restrict to a single source only.

5.0_CPDnb06816 P2P Adjacency also in case of DataLinkBlockSize mismatch.

When a difference of ‘MaxLspBufSize’ existing on neighboring NE’s a P2P IS Adjacency should not come up after enabling DCC channels. The current behaviour however is that a P2P Adjacency does come up. The effect of this situation will be an unstable management network.

Preventive action:The maximum LSP size is an area wide parameter which should be consistent within the DCN. Inconsistent usage of the LSP size can result in a complete or partial DCN failure. If it is required to operate different areas with different LSP sizes, then an external router must be used which converts the different LSP sizes.

5.0_CPDnb06878 MaxLspBufSize mismatch not recognizable on QLAN.

When a node, which is the Designated Router for the broadcast subnetwork (QLAN), has ‘MaxLspBufSize’ fixed to 1492, this will lead to management instability of nodes within that subnetwork which have a MaxLspBufSize setting of 512 bytes.


...........................................................................................................................................................................................................................................................



Preventive action:Refer to Preventive action of 5.0_CPDnb06816.

5.0_CPDnb07023 PMcWUP does not shut down the laser.

When a Small Form Factor Plugable (SFP) unit is inserted, there is a check if the SFP contains a supported type (so if it is an STM1 SFP) if this is not the case (like for instance it is a GbE SFP) the PMcWUP alarm will be raised and the Laser should be shut off. That laser shutdown does not occur in this release.

Workaround:None.

...........................................................................................................................................................................................................................................................



SHDSL-Related Problems See the following:

6.1_CPDnb17481 Diagnostic mode not working for span of two SRU’s.

Selecting the “Diagnostic Mode”, which makes any SHDSL Regenerator Unit behave as an NTU, does not work when two SRU’s are part of the span.

Workaround:None.

Note:This problem only exists on the previous version SHDSL card, it does not exist on SHDSLv3 card.

7.2_AR1-1776576/AR1-4047433

Wrongly reported NDD alarm on the second SRU when enabling/disabling Diagnostic Mode.

When two SRU are used between customer equipment and SHDSL card, sometimes enabling and disabling diagnostic mode will caused a NDD alarm at the second SRU which is supposed to be not reported.

Workaround:The alarm will be cleared after the second SRU is synchonized again.


...........................................................................................................................................................................................................................................................



6.1_CPDnb20474/AR1-1339232

NDE and SWE alarms are incorrectly raised on a miswired span.

A wrong connection of the 1st. span ("Master-Span") of the NT10ETH generates an NDD alarm on the AM management system. In this case sometimes the indicated SWE alarms are not correct.

Workaround:If, after the spans are miswired, an NDD alarm appears, do not press the synchronise button. Instead reconnect the 1st. Span (Port one of the Modem) with the correct AM SHDSL port. The NDD alarm will disappear. Then check if there are still SWE alarms and reconnect the spans in the right order.Note: Due to the long specified polling cycles the alarms NDD and SWE can take about 2 minutes before they are raised/cleared.

Note:This problem only exists on the previous version SHDSL card, it does not exist on SHDSLv3 card.

6.1_CPDnb21641/CPDnb21331/AR1-1378770

MIB download or NE reset causes small traffic interruption on NT10ETH traffic.

After a MIB download or reset of the 1643 AM/AMS, the Ethernet traffic running over an NT10ETH modem is affected. From tests it is seen that this interruption affects only a couple of frames.

Workaround:None.

9.0_CPDnb37278 FSC counter showed in SHDSL-V2 card P12 PM history bin.

Although FSC count is not supported by P12 performance monitoring, the counter will be showed in SHDSL-V2 P12 PM history bin with all zero.

Workaround:None.

7.2_CPDnb52170/CPDnb52378/CPDnb52379/CPDnb52380/

CPDnb54909/CPDnb54910

Some Weaknesses on SHDSL Performance Monitoring

- NTU LAN ppDE counter value is 32 times of the actual data.

- eINFO counter wrongly counts when Jabber frame comes.

- NTU WAN pcbR wrongly counts when Flow Control takes effect, or when LAN eFDFO counts.

...........................................................................................................................................................................................................................................................



- Sometimes the 24h history pcbR/pcbS counter values are not accurate, they are less than expected values.

- If NE time changes during 24h PM period, the LAN port eINFO/eINFU will count 0 in history bin, and pcbR/pcbS count wrong values.

Workaround:None.

7.2_CPDnb54524 NE Warm Restart is not always hitless for NT2M modem.

When having NT2M as NTU, warm restart NE may cause traffic hit. The probability is about 20%.

Workaround:None.

7.2_CPDnb54525/CPDnb54552

SWE Alarm is not cleared when wrong connection is corrected.

The wrong connection between LTU and NTU will cause SWE alarm. Sometimes when the wrong connection is corrected, the SWE alarm is not cleared.

Workaround:Restart NE.

7.2_CPDnb54527 Modem Power Supply alarm will be automatically cleared after 12 seconds.

The alarm will be automatically cleared in 12 seconds regardless the power supply is recovered or not.

Workaround:None.

7.2_CPDnb54548 Wrong Alarms from Modem is reported there is LOS or no Cross Connection on Line port.

The correct alarm in this case should be LANcLOS, but LANcNES is reported instead.

Workaround:None.


...........................................................................................................................................................................................................................................................



7.2_CPDnb54550 SRUcUMD alarm is not reported when 3rd SRU is added.

No SRUcUMD alarm is reported when 3rd SRU is added. Instead, the span is taken into service as if there were just 2 SRUs, and the 3rd SRU is invisible. Traffic is still running properly.

Workaround:Not adding the 3rd SRU, as only 2 SRU are guaranteed.

7.2_CPDnb54556 Authentication Error is not reported when one of 4 wires is from another NTU.

Workaround:None.

...........................................................................................................................................................................................................................................................



Ethernet-Related Problems See the following:

3.2_CPDnb01012 TransLAN interruption after maintenance upgrade fall back to original release.

There are reasons why a (maintenance) upgrade to this Release 5.0C (as to any other release) can fail. Amongst these reasons are e.g. instable DCN network or planned interruption by the operator. In the case of an upgrade failure the system will fall back to the previous release after time-out or after forced switch. Please note that in case of upgrades from Pearl releases before R2.2.G (SCA92G) there is a risk that the fall back results in permanently interrupted LAN data traffic. The SDH traffic will not be affected.

Workaround:None. The TransLAN card has to undergo a hard reset after falling back, for proper operation in the previous release.

Preventive action:It is strongly recommended not to start a network upgrade in case of instable DCN network. It is strongly recommended once an upgrade is started not to interrupt this upgrade by the operator.

2.0_CPDnb01951 Actual parameters shown during auto-negotiation configuration.

When auto-negotiation mode is enabled and auto-negotiation status is “configuring”, the actual parameter values the Network Element raises to managers should be “not available”. However the Network Element raises the last values it had auto-negotiated or values when auto-negotiation mode was disabled.

Workaround: The actual values can be disregarded by the user during auto-negotiation configuration.

2.2_CPDnb01953 X4IP-v2: CIR not restricting traffic 60-msec per minute.

When the CIR is provisioned on the X4IP-v2 option card, for 60 Milli seconds per minute (0.1% of the time) all traffic (all flows) is passed instead of being restricted according to the provisioned CIR. The effect of this is at largest when the LAN input traffic is much higher than the provisioned CIR values.

This problem is only applicable for X4IP-v2 option cards equipped with an Ethernet switch device version B1. The B2 version does not suffer from this issue although known problem 3.2_CPDnb04424


...........................................................................................................................................................................................................................................................



applies. All units produced after October 2002 (S/N start with 02R211) will have the B2 version.Remark: At that time the B1 and B2 was considered as two equivalent components and therefore an IM change was not required.

Workaround: None.

4.0_CPDnb03421 X8PL: Traffic loss if LCAS in not enabled on both ends.

If on an existing path LCAS is enabled, the traffic will be lost until LCAS is enabled on the terminating TP as well.

Workaround:None.

7.2_CPDnb55339 X8PL: Traffic hit is more than 50ms during SNCP protection switch.

The traffic hit is about 160ms during SNCP protection switch.

Workaround:None.

3.2_CPDnb04424 X4IP-v2: Very Small percentage of packet loss on Fast Ethernet.

In this release, where QoS is always enabled independent of Tagging Mode, a small percentage of packet loss (1E-5 or less) at the Performance Monitoring Counters or Ethernet Analyzer can be observed. The root cause is basically the same as for 2.2_CPDnb01953 but for the B2 version of the Ethernet switch all packets are dropped instead of being passed. From the data application perspective, it has no impact on customer networks since there is higher layer error correction mechanism built in TCP/IP protocol suite to handle such kind of packet loss. This behaviour is always present when the provisioned CIR value is smaller then the maximum rate allowed (CIR<MAX).In case the CIR value is set to its maximum (CIR=MAX) the packets will not be dropped immediately but marked as "yellow". This means that only when the network is congested these packets will have higher probability to be dropped than rest of the packets.

Workaround:None.

...........................................................................................................................................................................................................................................................



5.0_CPDnb10690 X4IP-v2: LAN Link LED is on but there is no link established.

When TransLAN+ LAN port is provisioned with auto negotiation: disabled, Speed: 10 Mbit/s, Duplex: Half Duplex and Pause Mode: disabled while the remote LAN port is provisioned with auto negotiation: Disabled, Speed: 100 Mbit/s, Duplex: Full Duplex and Pause Mode: disable the link TransLAN+ LAN LED is on while as expected no traffic will get through. This problem is only applicable for X4IP-v2 option card with IM=S1:4 or lower.

Workaround: Match both port settings.

5.0_CPDnb15887,CPDnb15608,CPDnb15640

X8PL: Unusual behaviour when Private Line Option Card with IM S1:3 or lower is used.

In case an X8PL option card is installed with interchangeability marker S1:3 or lower the following unusual behaviour exist compared to Systems equipped with X8PL option card with IM S1:4 or higher:

1) Raise and clear times of LANcANM, LANcLOS and LANcNES alarms are respectively 42 and 50 seconds instead of 1 and 10 seconds.

2) No update on LANcANM, LANcLOS and LANcNES alarms status when on the same node a NE software download is in progress.

3) Not able to download NE software to remote NE when using ITM-CIT and local NE has an X8PL card installed.

4) NE SW download could fail in case the NE that is used as a hop contains an X8PL card and provisioning is executed on this X8PL card.

Workaround:None.

6.1_CPDnb17846 X4IP-v2: Frame loss with QoS enabled and high utilization.

In case a WAN capacity of 2xVC3 has been provisioned and the total utilization exceeds 95%, the throughput will be reduced to 87%~92% due to limitations on buffer capacity and an internal flow control protocol trying to avoid buffer overrun situations. This is especially noticeable using large and random frame sizes. In case both high and low priority flows have been defined both flows will be affected.In this release the throughput reduction does not apply to repeater and non-QoS mode applications (CPDnb22002). Note that less then 10 Exp-5 is to be expected as a result of the problem described under 3.2_CPDnb04424.


...........................................................................................................................................................................................................................................................



Workaround:It is recommended to keep high priority flows below 70% of the provisioned WAN capacity to prevent this package drop.

6.1_CPDnb20958 X8PL: LAN pDe indicates dropped value for frames >> 1518/1522 Bytes.

Eventhough 1650 byte size frames are supported on X8PL, the pDe counter of LAN/WAN Performance Monitoring counts frames larger then 1518 (non VLAN frames) or 1522 (VLAN frames) Bytes. Traffic goes through unharmed, and CbS and CbR counters show correct values. This phenomena is a result of the definition of Oversize Packets, of an implemented IC (Integrated Circuit), and can thus not be changed by software.

Workaround:None.

6.1_CPDnb21071 X4IP-v2: High Packet loss on high priority traffic when low priority traffic contains small packets.

On a VC3-2v WAN link with a total utilization of over 80% and a high priority flow existing out of mixed frame sizes while a low priority flow contains mostly small frame sizes, a packet loss up to 3% can be noticed on the high priority flow. Especially small packets are being dropped.

Workaround:None.


X5IP: Limitatons on egress weight.

For X5IP, the Egress Queue Scheduler provisioned in Weighted Bandwidth mode (WRR, Weighted Round Robin), the weight value cannot exceed 16.

Workaround:None, scale the provisioned number and use value range 1..15 instead.

7.1_CPDnb23015 X5IP: Limitation in Rate Controller for X5IP TransLAN card (Green/Yellow information not encoded in the p0 bit).

When a flow is provisioned as 0<CIR<PIR<MAX, the yellow/green color information can only be used in same node for dropping priority. The p0 bit will be fixed (marked as green) so in the next node it will consider all frame that comes from this flow as green frame.

...........................................................................................................................................................................................................................................................



Workaround:If the application requires further limits on the same flow, it can be done on one of the downstream side nodes by applying rate control on network ports.

7.1_CPDnb24628 X4IP-v2: Queue Scheduler acting inappropriate under heavy traffic.

When LAN port CIR >> VCG capacity (e.g. CIR for X4IP-v2 = MAX = 100000, but VCG = 5xVC12) internal FIFO mechanism can cause small percentages of low priority traffic to get through eventhough high priority traffic was expected to get all available VCG bandwidth.

Workaround:Follow design rules and do not provision CIR a greater value then available bandwidth.

7.1_CPDnb25003 NE Time should be set prior to doing RoundTrip Delay Measurement (RTD).

Prior to running RoundTrip Delay Measurements (Single Shot mode) the NE time should be set (not per default done for an ITM-CIT managed NE). In case not done, the ITM-CIT GUI will hold-up in the Trigger Window, untill the ITM-CIT session times out.

Workaround:Synchronize the NE with ITM-CIT time or provision a manual time.

7.1_CPDnb26168 X5IP: Modifying FIT table will affect existing FIT Table entries.

When modifying an existing FIT table (Adding/Removing/Updating entries), due architecture the software may need to re-locate the existing flow entries. This may affect the traffic. The hit time is related with traffic speed and numbers of FIT entries. From test results, the traffic hit can be up to 30ms. This problem does apply to X5IP only.

Workaround:None.

7.1_CPDnb26216 X5IP: pCbR (PM) counts both good and bad bytes.

The pCbR counter (Ethernet Incoming Number of Good Bytes) for X5IP does count good bytes as well as ‘bad’ bytes (CRC errored frames, length violation frames, etc.).

Workaround:Make use of the INF counter (Ethernet Incoming Good Frames), which does not count ‘bad’ frames.


...........................................................................................................................................................................................................................................................



7.1_CPDnb27143/CPDnb23271/CPDnb23559/CPDnb23155/CPDnb08611

X8PL: Frame Size and Performance Monitoring behavior.

1. For X8PL the maximum supported frame size equals 1650 bytes. Oversize frame is counted according to 1518/1522 bytes. Frames between 1518/1522 bytes and 1650 bytes, will not be dropped but are counted both in pCbR and ppDE counters. If the received frame length is larger than 1650 bytes, the frames will be dropped and ppDE and pCbR will continue to increase, but only 1650 bytes will be counted (e.g. for a frame with 2048 bytes, only 1650 bytes will be counted in ppDE and pCbR counters). 2. Ethernet frames received which are shorter than the Ethernet standard of 64 bytes are counted as Undersize or Fragments, but will still pass through as long as the FCS is correct. In this case ppDE counter will not increase but other supported counters (Unicast, Multicast, Broadcast) will be increased.3. For X8PL, received frames with CRC error are counted in the pCbR and pUPR PM counters (pCbR = Ethernet Incoming Number of Good Bytes, pUPR = Ethernet Incoming Number of Good Unicast Frames).4. For X8PL, received Broadcast or Multicast frame with framelength above the Oversize length (1518/1522) are not counted in the Broadcast respectively Multicast counters. At sending side, pMPS and pBPS, the Oversized Frames are counted

7.1_CPDnb27238 Maximum 64 HQ/LQ/Flow PM counters.

From the 150 supported PM counters on 1643 AM/AMS, a restricted number of 64 can be used for Ethernet counters.

Workaround:None, take system limits into account.


X5IP: Inaccurate WRR ratio.

If a X5IP is provisioned to use WRR mode in its egress QoS setting, and two(or more) traffic flow go to two(or more) egress queue on same WAN port, sometimes the WRR raito may be inaccurate and even lead to traffic loss on the low-bandwidth queue. This inaccuracy increases when:* traffic marked as Yellow* traffic with small-frame-size* WAN bandwidth is small

...........................................................................................................................................................................................................................................................



Workaround:Use SP mode instead.

7.2_CPDnb28798 X5IP: CBS/PBS provisioning not accurate.

On X5IP the CBS/PBS can be provisioned via the (ITM-CIT) GUI in steps of 1K, while the hardware only supports 4K, 8K, 16K, 32K, ..., 16M. So the actual value may be bigger than the provisioned value.

Workaround:None.

7.2_CPDnb28938 X5IP: CBS/PBS limitation.

Due to hardware limitation, the actural CBS/PBS on X5IP may not exceed 275kByte, any value provisioned from GUI that exceeds the limitation will not be met.

Workaround:None.

7.2_CPDnb29109 X5IP: Ratio not accurate for egress queue in WRR mode.

For X5IP, if two egress queues are set to Weighted Round Robin (WRR) mode and the ratio is big (e.g. 1:16 or 1:32), and the traffic is mainly small frames, the actual ratio may vary from the setting, due to buffer overflow of one queue when the egress scheduler is serving another queue.

Workaround:None. Avoid using high ratio when using WRR mode.

7.2_CPDnb29158 X5IP: CBS/PBS less than calculated value.

On X5IP, the number of packets that can be hold in the egress queue is limitted (at most 250 per queue). So the actual Committed Burst Size / Peak Burst Size (CBS/PBS) might be less than calculated value incase the ingress rate is higher than the egress rate, and the majority of packets are small ones (in this case the egress queue have reached limitation of packets number and additional packets will be dropped, eventhough the byte count has not reached CBS/PBS value.)

Workaround:None.


...........................................................................................................................................................................................................................................................



7.2_CPDnb29452 X5IP: Inaccuracy for several PM counters.

High Quality PM Wan Ports cannot display counter values for frame sizes between 64 and 84 bytes. This impacts the accuracy for C3EIN, C2EIN, i3gEILS, i32gEILS, i3gEISLS and i32gEISLS counters.

Workaround:None.

7.1_CPDnb29462 X5IP: TC PM counter increases when receiving CRC errored frames.

The PM counters for Traffic Classes (TC), such as g0EINB/ g1EINB/ y0EINB/y1EINB, should not increase when the frames have CRC errors or incorrect Vlans.

Workaround:None.

7.2_CPDnb33330 X5IP: Manual MAC entry should not be made for Multicast Address.

In case a Multicast Address in entered in the Manual MAC Address Table, traffic will be forwarded to all ports within a Virtual Switch, inlcuding those which were not set as valid output port of the Manual MAC address. This does not apply to Unicast and Broadcast addresses.

Workaround:None.

8.0_CPDnb34459 X5IP: Traffic totally lost if one VC member's differential delay is out of range.

For X5IP, if one member of an LCAS-enabled VCG experiences excessive differential delay (>> 64 msec), the whole VCG will be declared failed. Contrary to expected, VCxVcTLCR will be reported rather then VCxVcPLCR, and all traffic will be lost, rather then reduced.

Workaround:None.

8.0_CPDnb35186 X5IP: LCAS protocol interferes with lower layer protection schemes.

Due a lack of hold-off timer on the LCAS-enabled VCGs of X5IP TransLAN card, LCAS protocol will be activated eventhough lower layer protection schemes (SNC- or MSP-protection) do take care of service restoration. As a result, a complete Ethernet circuit may be down after an SNC or MSP switch, for a total time T, according to

...........................................................................................................................................................................................................................................................



LCAS Wait To Restore (WTR) timer. Note: in this release the LCAS WTR timer for X5IP TransLAN card is set to default value of 5 minutes.

Workaround:The WTR timer may be set from the default 5 minutes to 0 minutes.

7.2_CPDnb36558 ASAP set EthPS can not be assigned to X5IP optical GE port through ITM-CIT.

When ASAP set EthPS is being assigned to X5IP optical GE port, error message “port does not exist” will raise. The same problem exist when assigning ASAP set EthPD to X5IP electrical GE port.

Workaround:Assign ASAP set EthPS through OMS.

7.2_CPDnb38080/AR 1-1989681

Fault LED lit on X5IP.

Neither there is SFP ever been inserted, nor any active alarm raised for the slot TS2, the fault LED of X5IP is on.

Workaround:None.

7.2_CPDnb39157 VC-n-Xc group members’ status is wrong while differential delay exceeds threshold.

While differential delay in one VC-n-Xv group exceeds threshold, allmembers of that VCG show failed status but not only the member in which the differential delay is introduced. The threshold value is different for every data cards as below:

X8PL - 32ms for VC-12-Xv, 48ms for VC-3-Xv

X5IP - 64ms for VC-n-Xv, n = 3, 12

X10IP - 128ms for VC-n-Xv, n = 4, 3, 12

X4GPL - 128ms for VC-n-Xv, n = 4, 3, 12

Workaround:None.


...........................................................................................................................................................................................................................................................



7.2_CPDnb41495 DDM information error after X5IP cold start.

After a cold reset of the X5IP option card with an SFP plugged in, DDM (SFP Digital Diagnostic Monitoring) may not behave as prior the cold restart, and for example may show Laser Bias Current and Tx PWR display errors.

Workaround:None.

7.2_CPDnb43295 On Card CMC410 the vlan id range 4001 to 4093 can't be used as "Default VLAN ID" (dafault vlan id toggle Button).

Provisioning of a "Switched Ethernet Service" with VLAN ID between 4001 and 4093 in combination with the activation of the "Default VLANID" (default vlan id toggle Button), the implementation will fail.

Workaround:None.

...........................................................................................................................................................................................................................................................

Known ProblemsKnown Problems for ITM-CIT R18.10.00


............................................................................................................................................................................................................................................................

Known Problems for ITM-CIT R18.10.00

None.



............................................................................................................................................................................................................................................................

4 New Installation

............................................................................................................................................................................................................................................................

Overview

Introduction This section provides a reference to the procedure to install the Alcatel-Lucent 1643 AMS Network Element (NE) software onto a new Alcatel-Lucent 1643 AMS system and a reference to the procedure to install the ITM-CIT (Craft Interface Terminal) software onto a Windows-based PC. Additionally it contains information that will contribute to a proper installation of the Alcatel-Lucent 1643 AMS.



General Remarks 4-2

...........................................................................................................................................................................................................................................................

New InstallationGeneral Remarks


............................................................................................................................................................................................................................................................

General Remarks

Software availability Software for Alcatel-Lucent 1643 AMS Release 7.2.11 consists of two packages:

• Alcatel-Lucent 1643 AMS Network Element (NE) Software Release 7.2.11 delivered on a CD-ROM (Comcode 109782573). The CD-ROM contains besides NE software also the Fast Download Tool, as well this SRD.

• ITM-CIT (Craft Interface Terminal) Software Release R18.10.00 delivered on a CD-ROM (Comcode 109796904).

For new installations refer to the Alcatel-Lucent 1643 AMS Installation Guide, Release 1.0 through 7.2 (365-312-802R7.2, Comcode 109635797).



............................................................................................................................................................................................................................................................


............................................................................................................................................................................................................................................................

Overview

Purpose This chapter contains information regarding upgrade procedures.



ITM-CIT Upgrade 5-2





...........................................................................................................................................................................................................................................................

Upgrade ProceduresITM-CIT Upgrade


............................................................................................................................................................................................................................................................

ITM-CIT Upgrade

De-installation of PreviousITM-CIT Release

To upgrade an existing ITM-CIT to R18.10.00, an installed ITM-CIT version older than release R18.10.00 needs to be un-installed via the MS-Windows application “Add/Remove Programs”. User-created data (saved views, data communication, provisioning, CIT security administration, NE generic file transfers) needs to be preserved before installing the new R18.10.00 ITM-CIT version.

Installation of ITM-CITR18.10.00

For installation of the ITM-CIT refer to the Alcatel-Lucent 1643 AMS Installation Guide, Release 1.0 through 7.2 (365-312-802R7.2, Comcode 109635797).

Upgrade ProceduresNE Software Upgrade General

...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................

NE Software Upgrade General

UpgradingFrom Releases older thanRelease R7.2.x to Release

7.2.11

To upgrade an Alcatel-Lucent 1643 AMS Network Element from a release older than Release 7.2.x a MIB conversion is needed. MIB conversion takes place outside the NE by means of Lucent® OMS. As this may impact your entire network this procedure falls outside the scope of this document. For more details on this procedure please contact your local Alcatel-Lucent support group. In any case take the notes below into account.

Important! The upgrade from Release 7.1 to R7.2 is NOT a maintenance release upgrade. Conversion of the MIB using Lucent® OMS is mandatory!

Traffic impact whenupgrading from R7.2.10 toR7.2.11 and from R7.2.9 to

R7.2.11.

Data

If the Alcatel-Lucent 1643 AMS is equipped with a TransLAN Ethernet option card like switched ethernet card X5IP the following, maximum, traffic interruptions can be expected:X5IP: no more then 17 seconds in STP mode

Be aware that the given values can only be met when the network itself is stable and when in a Virtual Switch Network within its spanning tree diameter (all Virtual Switches that share the same root bridge) only one node at a time is upgraded.

SDH/PDH

The remaining SDH/PDH traffic is never affected for more then 50 millisecond.

Software availability CIT and NE Software are available on CD-ROM (see table below:

SoftwareComcode for the CD-

ROM

NE Software Release 7.2.11 (SCA404L)

109782573

CIT Software Version R18.10.00 (SAA619K)

109796904

...........................................................................................................................................................................................................................................................



Customers that have a password and privileges can download the NE software as a self-extracting WinZip package from the following website:

http://support.alcatel-lucent.com

Alcatel-Lucent engineers can also use the TSS ONG Product Support website on the Alcatel-Lucent intranet (for training, test and demonstration purposes):

http://ong.nl.lucent.com/tss/

Upgrade ProceduresNE Maintenance Upgrade with the ITM-CIT

...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................

NE Maintenance Upgrade with the ITM-CIT

Purpose This procedure describes a field upgrade of the NE Software to Release 7.2.11 via the ITM-CIT.

Important! This section is applicable for upgrades from Release 7.1.x to Release 7.2.11. To upgrade a Alcatel-Lucent 1643 AMS Network Element from a release older than Release 7.1.x please contact your local Alcatel-Lucent support group.

Before you begin Prior to performing this task, you must:

1. Read the ‘NE Software Upgrade General’ section

2. Always use the ITM-CIT version corresponding to the NE release you are upgrading to.

3. Connect the ITM-CIT to the CIT interface of the subjected NE/ring.

4. The NE should be Alarm free prior to beginning with the upgrade.

Task This procedure consists of the following parts, each described separately:

• Download the NE software

• Activate the NE software

• Final check

Alcatel-Lucent 1643 AMS NE Software Upgrade With ITM-CIT

This procedure describes how to download a new NE software release to a NE from the ITM-CIT. The software download is not traffic affecting. The NE will not be provisionable during the generic download.

A step-by-step instruction is given below:

................................................................................................................................................................................................................................................................

1 Place the CD-ROM into the CD-ROM drive.

................................................................................................................................................................................................................................................................

2 Start up the ITM-CIT and log in.

...........................................................................................................................................................................................................................................................



................................................................................................................................................................................................................................................................

3 Go to the menu Provisioning, Equipment, NE Software Configuration. Check store ID equals 1 (Network Element), then press Edit

Result: A new window will appear.

................................................................................................................................................................................................................................................................

4 Choose Download. Go to the ISD directory and select the file to download and then press Open. This may take up to 1 hour.

Result: The new NE software will be presented as being available (but inactive) in the backup store.

................................................................................................................................................................................................................................................................

5 Press Edit again. Under Switch Store, click on the box Retain MIB. Then press on the Switch button.

Result: After a short while, the ITM-CIT will disconnect.

................................................................................................................................................................................................................................................................

6 After approximately 5 minutes, you can log in again with the ITM-CIT.

................................................................................................................................................................................................................................................................

7 Go to the menu Provisioning, Equipment, NE Software Configuration and press Edit. Then press Commit.

Important! If the software switch is not committed within 2 hours, the software will switch back to the previous release.

................................................................................................................................................................................................................................................................

8 Check that the system works normally and error-free.

........................................................................................................................................................E N D O F S T E P S

Upgrade ProceduresNE Maintenance Upgrade with Lucent® OMS

...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................

NE Maintenance Upgrade with Lucent® OMS

Purpose This document describes a field upgrade of the Alcatel-Lucent 1643 AMS NE Software to Release 7.2.11 via the Lucent® OMS.

Before you begin The Alcatel-Lucent 1643 AMS network is running in a release not lower than Release 7.2.x

During the network upgrade the following actions must be avoided:

• NE provisioning

• Insertion of new equipment

• Replacement of NE hardware

Before upgrading the NE you should:

1. Read NE Software Upgrade General: page 5-3.

2. Check that the NE is alarm free prior to beginning with the upgrade.


1. Install the NE software on the OMS.

2. Download the NE software to the NE.

3. Activate the NE software.

4. Final check.

...........................................................................................................................................................................................................................................................



1. Install the NE SoftwareFrom CD-ROM With Use of

the OMS

This procedure describes how to copy the NE software from the CD-ROM to the Lucent® OMS.

To install the NE software, the following action must be performed


................................................................................................................................................................................................................................................................

1 Put the CD-ROM with the NE sw in the CD/DVD.

................................................................................................................................................................................................................................................................

2 Login onto the Lucent® OMS as a user with software management privileges.

................................................................................................................................................................................................................................................................

3 Open the network element/software screen.

................................................................................................................................................................................................................................................................

4 Select the New (action) button in the right top corner of the screen. A new window will open which allows you to import the software.

................................................................................................................................................................................................................................................................

5 In the NE Type pull-down menu, select Alcatel-Lucent 1643 AM and the NE Generic.

................................................................................................................................................................................................................................................................

6 After selecting Submit the software will be copied to the server.

................................................................................................................................................................................................................................................................

7 Wait until you get the message “A new NE generic for Alcatel-Lucent 1643 AM has been successfully transferred to the management system”.

........................................................................................................................................................E N D O F S T E P S

Action Result Time

Copy NE software to OMS server

Software will be copied to the /var/opt/lucent/ftp/pub/SW/AM1PLUS directory

10 min.


...........................................................................................................................................................................................................................................................



2. Download the NE Softwareto the NE

This procedure describes how to download a new NE software release to an NE from the Lucent® OMS and will take approximately 25 minutes.

The software download is not traffic-affecting.


................................................................................................................................................................................................................................................................

1 Return to the Network Elements Software Menu and select NE generic and NE.

................................................................................................................................................................................................................................................................

2 At NE type and NE name, select Alcatel-Lucent 1643 AM and the name of the NE you want to download the software to, Then press Search.

................................................................................................................................................................................................................................................................

3 You will get information about the active and inactive store of the NE. From the bottom of the screen, select “Transfer NE generic from management system to NE” and press GO.

................................................................................................................................................................................................................................................................

4 Wait until you get the message that the software has been successfully downloaded to the NE.

........................................................................................................................................................E N D O F S T E P S

...........................................................................................................................................................................................................................................................



3. Activate the NE Software This procedure describes how to activate a new NE software release and will take approximately 25 minutes.

Important! As a result of this action, a system reset will be initiated and the communication to the NE will be lost for approximately 20 minutes. After this time has elapsed, the NE can once again be managed via the Lucent® OMS.

Activate SW From OMS To activate the software via the Lucent® OMS follow the step-by-step instruction given below:

................................................................................................................................................................................................................................................................

1 Return to the Network Elements Software menu and select NE generic and NE.

................................................................................................................................................................................................................................................................

2 At NE type and NE name, select Alcatel-Lucent 1643 AM and the name of the NE you want to upgrade; then press Search.

................................................................................................................................................................................................................................................................

3 You will get information about the active and inactive store of the NE. Verify that the inactive store shows the correct Item Code.

................................................................................................................................................................................................................................................................

4 From the bottom of the screen, select “Activate: No Mib clear” and press Go.

................................................................................................................................................................................................................................................................

5 Wait until you get the message that the operation was successful.

........................................................................................................................................................E N D O F S T E P S


...........................................................................................................................................................................................................................................................



4. Final Check This procedure describes how to verify whether the upgrade was performed successfully or not.

Make sure of the following:

1. The traffic is working properly;

2. The NE is running in the correct NE load. This can be seen in the window “Network Elements Software Menu, NE generic, NE name, search.”

3. Other nodes in the ring show no unexpected/new alarms.

4. There are no new unexpected alarms on the shelf.

...........................................................................................................................................................................................................................................................

Upgrade ProceduresSwitch to TransLAN standard-compliant IEEE tagging modes


............................................................................................................................................................................................................................................................

Switch to TransLAN standard-compliant IEEE tagging modes

Introduction The preferred TransLAN® operational modes from Earth Network Release on are the two standard-compliant IEEE tagging modes, i.e. the IEEE 802.1Q VLAN tagging mode and the IEEE 802.1ad VLAN tagging mode (provider bridge mode). The proprietary VPN tagging modes will be superseded in the long term by the new tagging modes and valuable concepts like enhanced flow classification and flexible QoS assignment as well as comprehensive PM/OAM functionality have been or will be implemented in the IEEE802.1Q and IEEE802.1ad tagging modes mode only. The AMS supports two Ethernet switch option cards. The X4IP-v2 option card support both the proprietary VPN tagging modes and the standard-compliant IEEE tagging modes. Although its feature set has been frozen to the Earth network release, it still might be required to switch to the standard -compliant IEEE tagging mode to insure proper interworking. Switching modes does not apply to the X5IP option card as it only operate in the standard-compliant IEEE tagging modes supporting the latest features.

Mode change basics To make your current network keep pace with future evolution it is highly recommended to start with or to migrate to the new mode.

- A mode change is applied for an entire TransLAN card.- A switched network needs all virtual switches running in the same mode.- There is no mode change needed for the IEEE802.1Q mode.- The repeater mode is a special case. The repeater mode is existing under the pre-standard mode and under the standard IEEE mode and interwork with each other.

High–Level Operationalprocedures

As this paragraph will only provide an high level operational procedure it does not cover the network and service interruption impact. For more details on this procedure please contact your local Alcatel-Lucent support group.

The high level procedure for a mode change from legacy transparent to IEEE802.1ad mode shall be processed as follows.


...........................................................................................................................................................................................................................................................



On ITM-SC/ITM-CIT managed networks:

- Identify and record the switch parameters for the Virtual Switches (VS)- Delete all the VS.- Execute the tagging mode change- Recreate the VS with Ethertype not equal to ‘8100’ selecting the necessary WAN and LAN ports.- Provision VLANs, PVIDs, and QOS settings.

On OMS managed networks

- Identify and record the switch parameters for the service- Delete the service - Recreate the service in IEEE tagging with switch parameters as required- Add the new IEEE service.

Important! OMS supports discovery, fault/performance management and service deletion for all Transparent tagging mode services but no modifying.



............................................................................................................................................................................................................................................................


............................................................................................................................................................................................................................................................

Overview

Purpose This chapter contains information regarding upgrade procedures.



ITM-CIT Upgrade 5-2





...........................................................................................................................................................................................................................................................

Upgrade ProceduresITM-CIT Upgrade


............................................................................................................................................................................................................................................................

ITM-CIT Upgrade

De-installation of PreviousITM-CIT Release

To upgrade an existing ITM-CIT to R18.10.00, an installed ITM-CIT version older than release R18.10.00 needs to be un-installed via the MS-Windows application “Add/Remove Programs”. User-created data (saved views, data communication, provisioning, CIT security administration, NE generic file transfers) needs to be preserved before installing the new R18.10.00 ITM-CIT version.

Installation of ITM-CITR18.10.00

For installation of the ITM-CIT refer to the Alcatel-Lucent 1643 AMS Installation Guide, Release 1.0 through 7.2 (365-312-802R7.2, Comcode 109635797).


...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................

NE Software Upgrade General

UpgradingFrom Releases older thanRelease R7.2.x to Release

7.2.11

To upgrade an Alcatel-Lucent 1643 AMS Network Element from a release older than Release 7.2.x a MIB conversion is needed. MIB conversion takes place outside the NE by means of Lucent® OMS. As this may impact your entire network this procedure falls outside the scope of this document. For more details on this procedure please contact your local Alcatel-Lucent support group. In any case take the notes below into account.

Important! The upgrade from Release 7.1 to R7.2 is NOT a maintenance release upgrade. Conversion of the MIB using Lucent® OMS is mandatory!

Traffic impact whenupgrading from R7.2.10 toR7.2.11 and from R7.2.9 to

R7.2.11.

Data

If the Alcatel-Lucent 1643 AMS is equipped with a TransLAN Ethernet option card like switched ethernet card X5IP the following, maximum, traffic interruptions can be expected:X5IP: no more then 17 seconds in STP mode

Be aware that the given values can only be met when the network itself is stable and when in a Virtual Switch Network within its spanning tree diameter (all Virtual Switches that share the same root bridge) only one node at a time is upgraded.

SDH/PDH

The remaining SDH/PDH traffic is never affected for more then 50 millisecond.

Software availability CIT and NE Software are available on CD-ROM (see table below:

SoftwareComcode for the CD-

ROM

NE Software Release 7.2.11 (SCA404L)

109782573

CIT Software Version R18.10.00 (SAA619K)

109796904

...........................................................................................................................................................................................................................................................



Customers that have a password and privileges can download the NE software as a self-extracting WinZip package from the following website:

http://support.alcatel-lucent.com

Alcatel-Lucent engineers can also use the TSS ONG Product Support website on the Alcatel-Lucent intranet (for training, test and demonstration purposes):

http://ong.nl.lucent.com/tss/


...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................

NE Maintenance Upgrade with the ITM-CIT

Purpose This procedure describes a field upgrade of the NE Software to Release 7.2.11 via the ITM-CIT.

Important! This section is applicable for upgrades from Release 7.1.x to Release 7.2.11. To upgrade a Alcatel-Lucent 1643 AMS Network Element from a release older than Release 7.1.x please contact your local Alcatel-Lucent support group.

Before you begin Prior to performing this task, you must:

1. Read the ‘NE Software Upgrade General’ section

2. Always use the ITM-CIT version corresponding to the NE release you are upgrading to.

3. Connect the ITM-CIT to the CIT interface of the subjected NE/ring.

4. The NE should be Alarm free prior to beginning with the upgrade.


• Download the NE software

• Activate the NE software

• Final check

Alcatel-Lucent 1643 AMS NE Software Upgrade With ITM-CIT

This procedure describes how to download a new NE software release to a NE from the ITM-CIT. The software download is not traffic affecting. The NE will not be provisionable during the generic download.


................................................................................................................................................................................................................................................................

1 Place the CD-ROM into the CD-ROM drive.

................................................................................................................................................................................................................................................................

2 Start up the ITM-CIT and log in.

...........................................................................................................................................................................................................................................................



................................................................................................................................................................................................................................................................

3 Go to the menu Provisioning, Equipment, NE Software Configuration. Check store ID equals 1 (Network Element), then press Edit

Result: A new window will appear.

................................................................................................................................................................................................................................................................

4 Choose Download. Go to the ISD directory and select the file to download and then press Open. This may take up to 1 hour.

Result: The new NE software will be presented as being available (but inactive) in the backup store.

................................................................................................................................................................................................................................................................

5 Press Edit again. Under Switch Store, click on the box Retain MIB. Then press on the Switch button.

Result: After a short while, the ITM-CIT will disconnect.

................................................................................................................................................................................................................................................................

6 After approximately 5 minutes, you can log in again with the ITM-CIT.

................................................................................................................................................................................................................................................................

7 Go to the menu Provisioning, Equipment, NE Software Configuration and press Edit. Then press Commit.

Important! If the software switch is not committed within 2 hours, the software will switch back to the previous release.

................................................................................................................................................................................................................................................................

8 Check that the system works normally and error-free.

........................................................................................................................................................E N D O F S T E P S


...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................

NE Maintenance Upgrade with Lucent® OMS

Purpose This document describes a field upgrade of the Alcatel-Lucent 1643 AMS NE Software to Release 7.2.11 via the Lucent® OMS.

Before you begin The Alcatel-Lucent 1643 AMS network is running in a release not lower than Release 7.2.x

During the network upgrade the following actions must be avoided:

• NE provisioning

• Insertion of new equipment

• Replacement of NE hardware

Before upgrading the NE you should:

1. Read NE Software Upgrade General: page 5-3.

2. Check that the NE is alarm free prior to beginning with the upgrade.


1. Install the NE software on the OMS.

2. Download the NE software to the NE.

3. Activate the NE software.

4. Final check.

...........................................................................................................................................................................................................................................................



1. Install the NE SoftwareFrom CD-ROM With Use of

the OMS

This procedure describes how to copy the NE software from the CD-ROM to the Lucent® OMS.

To install the NE software, the following action must be performed


................................................................................................................................................................................................................................................................

1 Put the CD-ROM with the NE sw in the CD/DVD.

................................................................................................................................................................................................................................................................

2 Login onto the Lucent® OMS as a user with software management privileges.

................................................................................................................................................................................................................................................................

3 Open the network element/software screen.

................................................................................................................................................................................................................................................................

4 Select the New (action) button in the right top corner of the screen. A new window will open which allows you to import the software.

................................................................................................................................................................................................................................................................

5 In the NE Type pull-down menu, select Alcatel-Lucent 1643 AM and the NE Generic.

................................................................................................................................................................................................................................................................

6 After selecting Submit the software will be copied to the server.

................................................................................................................................................................................................................................................................

7 Wait until you get the message “A new NE generic for Alcatel-Lucent 1643 AM has been successfully transferred to the management system”.

........................................................................................................................................................E N D O F S T E P S

Action Result Time

Copy NE software to OMS server

Software will be copied to the /var/opt/lucent/ftp/pub/SW/AM1PLUS directory

10 min.


...........................................................................................................................................................................................................................................................



2. Download the NE Softwareto the NE

This procedure describes how to download a new NE software release to an NE from the Lucent® OMS and will take approximately 25 minutes.

The software download is not traffic-affecting.


................................................................................................................................................................................................................................................................

1 Return to the Network Elements Software Menu and select NE generic and NE.

................................................................................................................................................................................................................................................................

2 At NE type and NE name, select Alcatel-Lucent 1643 AM and the name of the NE you want to download the software to, Then press Search.

................................................................................................................................................................................................................................................................

3 You will get information about the active and inactive store of the NE. From the bottom of the screen, select “Transfer NE generic from management system to NE” and press GO.

................................................................................................................................................................................................................................................................

4 Wait until you get the message that the software has been successfully downloaded to the NE.

........................................................................................................................................................E N D O F S T E P S

...........................................................................................................................................................................................................................................................



3. Activate the NE Software This procedure describes how to activate a new NE software release and will take approximately 25 minutes.

Important! As a result of this action, a system reset will be initiated and the communication to the NE will be lost for approximately 20 minutes. After this time has elapsed, the NE can once again be managed via the Lucent® OMS.

Activate SW From OMS To activate the software via the Lucent® OMS follow the step-by-step instruction given below:

................................................................................................................................................................................................................................................................

1 Return to the Network Elements Software menu and select NE generic and NE.

................................................................................................................................................................................................................................................................

2 At NE type and NE name, select Alcatel-Lucent 1643 AM and the name of the NE you want to upgrade; then press Search.

................................................................................................................................................................................................................................................................

3 You will get information about the active and inactive store of the NE. Verify that the inactive store shows the correct Item Code.

................................................................................................................................................................................................................................................................

4 From the bottom of the screen, select “Activate: No Mib clear” and press Go.

................................................................................................................................................................................................................................................................

5 Wait until you get the message that the operation was successful.

........................................................................................................................................................E N D O F S T E P S


...........................................................................................................................................................................................................................................................



4. Final Check This procedure describes how to verify whether the upgrade was performed successfully or not.

Make sure of the following:

1. The traffic is working properly;

2. The NE is running in the correct NE load. This can be seen in the window “Network Elements Software Menu, NE generic, NE name, search.”

3. Other nodes in the ring show no unexpected/new alarms.

4. There are no new unexpected alarms on the shelf.

...........................................................................................................................................................................................................................................................



............................................................................................................................................................................................................................................................

Switch to TransLAN standard-compliant IEEE tagging modes

Introduction The preferred TransLAN® operational modes from Earth Network Release on are the two standard-compliant IEEE tagging modes, i.e. the IEEE 802.1Q VLAN tagging mode and the IEEE 802.1ad VLAN tagging mode (provider bridge mode). The proprietary VPN tagging modes will be superseded in the long term by the new tagging modes and valuable concepts like enhanced flow classification and flexible QoS assignment as well as comprehensive PM/OAM functionality have been or will be implemented in the IEEE802.1Q and IEEE802.1ad tagging modes mode only. The AMS supports two Ethernet switch option cards. The X4IP-v2 option card support both the proprietary VPN tagging modes and the standard-compliant IEEE tagging modes. Although its feature set has been frozen to the Earth network release, it still might be required to switch to the standard -compliant IEEE tagging mode to insure proper interworking. Switching modes does not apply to the X5IP option card as it only operate in the standard-compliant IEEE tagging modes supporting the latest features.

Mode change basics To make your current network keep pace with future evolution it is highly recommended to start with or to migrate to the new mode.

- A mode change is applied for an entire TransLAN card.- A switched network needs all virtual switches running in the same mode.- There is no mode change needed for the IEEE802.1Q mode.- The repeater mode is a special case. The repeater mode is existing under the pre-standard mode and under the standard IEEE mode and interwork with each other.

High–Level Operationalprocedures

As this paragraph will only provide an high level operational procedure it does not cover the network and service interruption impact. For more details on this procedure please contact your local Alcatel-Lucent support group.

The high level procedure for a mode change from legacy transparent to IEEE802.1ad mode shall be processed as follows.


...........................................................................................................................................................................................................................................................



On ITM-SC/ITM-CIT managed networks:

- Identify and record the switch parameters for the Virtual Switches (VS)- Delete all the VS.- Execute the tagging mode change- Recreate the VS with Ethertype not equal to ‘8100’ selecting the necessary WAN and LAN ports.- Provision VLANs, PVIDs, and QOS settings.

On OMS managed networks

- Identify and record the switch parameters for the service- Delete the service - Recreate the service in IEEE tagging with switch parameters as required- Add the new IEEE service.

Important! OMS supports discovery, fault/performance management and service deletion for all Transparent tagging mode services but no modifying.



............................................................................................................................................................................................................................................................

6 Miscellaneous

............................................................................................................................................................................................................................................................

Overview

Purpose This section describes the technical support available for Alcatel-Lucent 1643 AMS.



Technical Support Services (TSS) 6-2

...........................................................................................................................................................................................................................................................

MiscellaneousTechnical Support Services (TSS)


............................................................................................................................................................................................................................................................

Technical Support Services (TSS)

Technical Support Groups Technical support is available through:

• Local/Regional TSS.

• TEC Global Product Support.

Contacting YourLocal/Regional TSS

Local/Regional Technical Support Services (TSS) personnel troubleshoot field problems 24 hours a day over the phone and on site (if necessary) based on Alcatel-Lucent Service Contracts.For Technical assistance, call your Local/Regional TSS team or the International Customer Management Center (ICMC) at 00800 00 lucent (toll free inside EMEA) or +353 1 6924579 (toll) for in-hours and emergency out-of-hours support. If the request cannot be solved by Local Regional TSS, it will be escalated to the TEC Global Product Support team.

Product Support Alcatel-Lucent TEC Global Product Support organization is committed to providing customers with quality product support services. Each segment of the TSS organization regards the customer as its highest priority and understands your obligations to maintain quality services for your customers.

The TEC team maintains direct contact with Alcatel-Lucent manufacturing, Research & Development, and other organizations to assure fast resolution of all assistance requests.

Services Alcatel-Lucent 1643 AMS is complemented by a full range of services available to support planning, maintaining, and operating your system. Applications testing, network integration, and upgrade/conversion support is also available.

A technical support Platform A global online trouble tracking system is used by all support teams to track customer assistance requests. The system communicates details about product bulletins, troubleshooting procedures, and other critical information to customers. All details of a request are entered into this database until closure. For online access to your trouble tickets via the web please contact your local support team.

Reference For additional information about technical support, please contact your Alcatel-Lucent Local/Regional Technical Support Services or visit http://support.alcatel-lucent.com.

Alcatel-Lucent 1643 AMS · • Alcatel-Lucent 1643 AMS Release 7.2.11, SCA404L, 109782573. •...

Documents

Transcript of Alcatel-Lucent 1643 AMS · • Alcatel-Lucent 1643 AMS Release 7.2.11, SCA404L, 109782573. •...