1675 LambdaUnite® MultiService Switch (MSS), Release ...

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

1675 LambdaUnite® MultiService Switch (MSS), Release.11.01.28

Software Release Description

Network Element (NE) Software Version 11.01.28

Craft Interface Terminal (CIT) Software Release.18.09.05, Build.5091

Issue 1.0

Nov. 2012

Alcatel-Lucent - Proprietary

See 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.

Trademarks

All trademarks and service marks specified herein are owned by their respective companies.

Notice

Every effort was made to ensure that this information product was complete and accurate at the

time of printing. However, information is subject to change.

Mandatory customer information

This information product does not contain any mandatory information.

Software copyright

Portions copyright by Atos Origin Integration under MARBEN™ Products

Legal Notices applicable to any software distributed alone or in connection with the

product to which this document pertains, are contained in files within the software itself located

at:

− the software distribution CD available with the product at /Licenses

− the WaveStar® CIT interface; selecting the Help About Licenses button from the Wave-

Star® CIT system view.

See the 1675 LambdaUnite MSS User Provisioning Guide for additional information about how

to access the WaveStar® CIT.

Support

Technical support

Please contact your Alcatel-Lucent Local Customer Support Team (LCS) for technical questions

about the information in this document.

C O N T E N T S

i i iAlcatel-Lucent - Proprietary


1675 LambdaUnite® MultiService Switch (MSS),

Release.11.01.28 Software Release DescriptionIssue 1.0, Nov. 2012

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

Contents

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

A About this Document

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

1 New Features

Overview 1 - 3

New Features of R11.01.28 1 - 4




New Features of R11.1 1 - 8


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

2 Fixed Problems

Introduction 2 - 3

Fixed Problems in Release 11.01.28 2 - 4



Fixed Problems in Release.11.01.25 2 - 9




Fixed Problems in Release.11.1 2 - 20


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

3 Known Problems

Introduction 3 - 2

Known Problems 3 - 3

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

4 New Installation and Upgrade Procedures

General 4 - 4

Upgrade path survey 4 - 5

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

C O N T E N T S

i vAlcatel-Lucent - Proprietary



Release.11.01.28 Software Release DescriptionIssue 1.0, Nov. 2012

New Installation and Software Upgrade 4 - 6

Overview 4 - 6

To perform an initial NE software download 4 - 7

NE Software Upgrade 4 - 12

To upgrade software to a new release 4 - 12

To perform an NE software download for upgrade purposes 4 - 20

To activate an NE software generic 4 - 26

To check for successful NE software upgrade 4 - 32

To solve NE software upgrade problems 4 - 33

To retrieve NE software generic information 4 - 42

Supporting information for “Retrieving NE software generic information” 4 - 43

Database backup 4 - 45

Overview 4 - 45

To limit the number of saved backups 4 - 45

Manually backup database to the WaveStar® CIT 4 - 47

To retrieve NE database information 4 - 51

Supporting information for Retrieving NE database information 4 - 52

To restore a database to a network element 4 - 54

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

5 Miscellaneous

Supported NE Releases with WaveStar®.CIT 5 - 2

Technical Support (TSC/TEC) 5 - 3

A - 1Alcatel-Lucent - Proprietary


1675 LambdaUnite® MultiService Switch (MSS), Release.11.01.28 Software Release DescriptionIssue 1.0, Nov. 2012

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

A About this Document

Purpose The 1675 LambdaUnite®.MultiService.Switch.(MSS) Release 11.01.28

Software Release Description (SRD) provides procedural information

required to install the 1675 LambdaUnite®.MultiService.Switch.(MSS)

Network Element (NE) software and WaveStar®.CIT (Craft Interface

Terminal) software. It also includes a listing of new features, known

problems, fixed problems, and other helpful information.

Reason for reissue This is the initial version of this document for 1675

LambdaUnite®.MultiService.Switch.(MSS) Release 11.01.28.

Intended audience This document is intended for those responsible for the installation,

acceptance, operations, and maintenance of Release 11.01.28.

How to Use This Document Each chapter of this document treats a specific aspect of the system and

can be regarded as an independent description. This ensures that readers

can inform themselves according to their special needs. This also means

that the document provides more information than needed by many of

the readers. Before you start reading the document, it is therefore

necessary to assess which aspects or chapters will cover the individual

area of interest.

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

About this Document

A - 2 Alcatel-Lucent - Proprietary


1675 LambdaUnite® MultiService Switch (MSS),Release.11.01.28 Software Release Description

Issue 1.0, Nov. 2012

The following briefly describes the type of information found in each

chapter.

Section 1 - New Features

This section provides a listing of 1675.LambdaUnite®.MSS features that

are new.

Section 2 - Fixed Problems

This section provides a listing of the problems from the previous

1675.LambdaUnite®.MSS Network Element (NE) software/hardware

and WaveStar®.CIT (Craft Interface Terminal) software releases that

have been fixed in 1675.LambdaUnite®.MSS Release 11.01.28.

Section 3 - Known Problems

This section provides descriptions and workarounds to existing problems

in 1675.LambdaUnite®.MSS Release 11.01.28 and WaveStar®.CIT

Release.18.09.05.

Section 4- Upgrade Procedure

This section provides the procedure to upgrade the WaveStar®.CIT

(Craft Interface Terminal) software on the PC or Laptop and the

1675.LambdaUnite®.MSS Network Element software of an existing

1675.LambdaUnite®.MSS system to 1675.LambdaUnite®.MSS Release

11.01.28.

Section 5- Miscellaneous

This section provides useful information to supplement the information

provided in the previous sections.

1 - 1Alcatel-Lucent - Proprietary



Release.11.01.28 Software Release Description


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

1 New Features

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

Contents 0

Overview 1 - 3

Purpose 1 - 3

Standards Compliance 1 - 3


CIT 1 - 4

Features blocked in R11.01.28 1 - 4


Software Features 1 - 5










Features blocked in R11.1 1 - 8

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

New Features

1 - 2 Alcatel-Lucent - Proprietary






Hardware 1 - 9


New Features

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






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

Overview 0

Purpose The following chapter briefly list the most important new features of

1675.LambdaUnite®.MSS Release 11.01.28. For the complete and

detailed feature content of 1675.LambdaUnite®.MSS Release 11.01.28

please refer to the 1675.LambdaUnite®.MSS Product Information and

Planning Guide and 1675.LambdaUnite®.MSS User Provisioning Guide

respectively.

Please note that in the case of upgrade, dependent on the release the

upgrade starts from, the new features of 1675.LambdaUnite®.MSS

Release 11.01.28 are a set of the new features of all intermediate

releases.

Standards Compliance Alcatel-Lucent SONET and SDH products comply with the relevant

European Telecommunication Standardization Institute (ETSI),

Telcordia™ Technologies, and International Telecommunications Union

- Telecommunication standardization sector (ITU-T) standards.

Important functions defined in SONET and SDH Standards such as the

Data Communications Channel (DCC), the associated 7-layer OSI

protocol stack, the SONET and SDH multiplexing structure and the

Operations, Administration, Maintenance, and Provisioning (OAM&P)

functions are implemented in Alcatel-Lucent product families.

Alcatel-Lucent intelligent control plane, implemented in

1675.LambdaUnite®.MSS as ONNS, is based on standards discussed in

the ITU-T Automatically Switched Optical Network (ASON), the

Internet Engineering Task Force (IETF) Generalized Multi Protocol

Label Switching (GMPLS) Forum and the Optical Internet Forum (OIF).

Alcatel-Lucent is heavily involved in various study groups with ITU-T,

Telcordia™ and ETSI work creating and maintaining the latest

worldwide SONET and SDH standards. 1675.LambdaUnite®.MSS

complies with all relevant and latest Telcordia™, ETSI and ITU-T

standards and supports both, SONET and SDH protocols in a single

hardware-software configuration.

Exceptions to this standard compliances and other minor defects of this

release are described in chapter 3 “Known Problems” of this document.

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

New Features






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

New Features of R11.01.28 0

CIT • Support of Windows® 7

Features blocked in

R11.01.28

• ONNS

• MS-SPRing TOP+EX

• 1:1 MSP

• this release is not intended for use in SDH networks

Due to the support of Windows 7 the JRE version had to be changed, so

WaveStar CIT no longer supports the NE’s BWM and TDM10G (please refer to

chapter "Known Problems", sub-chapter "CIT")

New Features

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






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


Software Features • LCAS on ES64U*

Features blocked in

R11.01.25

• ONNS


• 1:1 MSP


WaveStar CIT no longer supports Microsoft Windows 2000.

*: The ES64U does not support mixed LCAS/non-LCAS mode. Soenabling LCAS on a link involving ES64U must be done synchro-nized as much as possible on both ends of the link to minimize thetraffic hit.

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

New Features






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


Software Features • PM per flow on ES64U

• Adjustable Queue Weights

• Logging of CLI session Attempts

• Support of secure FTP*

• Alphanumeric CircuitId

• Support of FOSS (Free and Open Source Software)

Features blocked in

R11.01.20

• ONNS


• 1:1 MSP


*: In the configuration of the ssh daemon tcp port forwarding must beenabled on the EMS/NMS server

New Features

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






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


Software Features • ES64U: Enhanced number of CLI sessions: up to 6

• Enable-disable LACP also for an active LAG group

• Retrieval of flow information based on the VLAN tag

• LAG according to IEEE 802.3-2005 chapter 43

• Support of up to 6 unprotected ES64U cards

• Service Mirroring

• Oversubscription

• ES64U: Rolling Upgrade/Downgrade to minimize traffic impact

Released post DR4:

• PM per flow on ES64U

• Adjustable Queue Weights

Features blocked in

R11.1.11

• ONNS


• 1:1 MSP


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

New Features






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

New Features of R11.1 0

Software Features • 3 pairs of 1+1 equipment-protected ES64U packs per NE

• Preparation of rolling upgrade/downgrade of ES64U

• Rolling restore of ES64U

• Support of TL1 command log

Features blocked in R11.1 • ONNS


• 1:1 MSP


New Features

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






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

New Features of R11.0 0

Hardware • ES64U - Portless 20G Packet Switching Card

Software Features • ES64U HW Support

• ES64U Equipment Protection

• ES64U Maintenance

• ES64U mapping to STS1-kv

• ES64U VLAN switching

• EPL, EVPL and MEF 10 compliant E-Line and service

multiplexing on ES64U

• ES64U PM counter support

• ES64U CLI/SNMP provisioning and supervision

• Number of uni-directional VLAN cross-connections

• VLAN tag swapping

• ES64U 252 ports

• ES64U Ether Type provisioning per port

• ES64U Disable policing per flow

• ES64U Jumbo frame support on ports 1…30, 129..158

• ES64U QoS

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

New Features

1 - 1 0 Alcatel-Lucent - Proprietary








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

2 Fixed Problems

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

Contents 0

Introduction 2 - 3


Area Packet Management 2 - 4


Area Installation, Software Download, Backup & Restore, Upgrade 2 - 5

Area Performance Monitoring 2 - 5







Area Protection (BLSR/MS-SPRing, DRI/DNI, APS/MSP, UPSR/SNCP) 2 - 10


Area Configuration Management 2 - 12






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

Fixed Problems






Area CIT 2 - 19





Area Equipment Protection 2 - 24


Area Protection (BLSR/MS-SPRING, DRI/DNI, APS/MSP, UPSR/SNCP) 2 - 25

Area DCC/DCN Management 2 - 25


Area CIT 2 - 27

Fixed Problems

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




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

Introduction 0

This chapter provides a listing of the problems from the previous

1675.LambdaUnite®.MSS Network Element (NE) software/hardware

and WaveStar®.CIT (Craft Interface Terminal) software releases that

have been fixed in 1675.LambdaUnite®.MSS Release 11.01.28.

Please note that in the case of upgrade, dependant on the release the

upgrade starts from, the fixed problems of 1675.LambdaUnite®.MSS

Release 11.01.28 are a set of the fixed problems in all intermediate

releases.

Fixed Problems have been grouped into the following functional areas

• Area Installation, Software Download, Backup & Restore, Upgrade

• Area Configuration Management

• Area Synchronization Management

• Area ONNS

• Area Protection (BLSR/MS-SPRING, DRI/DNI, APS/MSP,

UPSR/SNCP)

• Area Equipment Protection

• Area Fault/Alarm Management

• Area Performance Monitoring

• Area DCN/DCC Management

• Area Security Management

• Area Packet Management

The syntax of the problem number (e.g. Fixed Problem 2.0 - nb12345) is

as follows:

• first part: the problem is known since this release

• second part: internal number

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

Fixed Problems





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

Fixed Problems in Release 11.01.28 0

Area Packet Management Problem 11.1.27 - nb95128

ES64U: Traffic Hits of up to several hundred msec in case of LAG

switch

When using LAG to group some links connected to ports of an ES64U a

failure of one leg causes the LAG state machine to not use this leg any

longer. As a side effect of some other code changes the time to recognize

the failure until the LAG state machine has switched away from the

failed leg has increased significantly from about 100msec to up to 800

msec.

Fixed Problems

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




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


Area Installation, Software

Download, Backup &

Restore, Upgrade

Problem 11.1.20 - nb95029

Rolling Upgrade of ES64U may get stuck in rare cases

It has been observed that in rare cases the rolling SW upgrade of

equipment-protected ES64U pairs may get stuck. The root cause is that

after starting up the standby ES64U with the new SW generic the

indication that this card has finished its restart and is operational is lost.

Only after a timeout of six hours the rolling upgrade will resolve this

stuck state by applying a reset to the standby ES64U. This stuck state

may occur only if more than one ES64U EQP group is existing.

Problem 11.1.20 - nb95005

ES64U: Failed ZBT RAM not detected by startup diagnostics

When the ZBT RAM of ES64U has a permament failure this may not be

detected by the diagnostics checks performed during startup. Such a

failure may lead to strange effects on traffic, e.g. a duplication of

Ethernet frames.

Area Performance

Monitoring

Problem 11.1.1 - nb92805

ES64U CLI/SNMP command pmperqeth shows wrong current pm

counters & becoming zero after crossing 15 minutes interval (on history

view)

In certain configurations (mainly in 10G traffic), the current pm counters

per queue of this port show giant wrong values and after crossing

15minutes interval , their value become zero.

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

Fixed Problems






ES64U: System Timers not working anymore after uptime of about

497 days

When an ES64U is up and running for more than 497 days, 2hours, 27

minutes and 53 seconds since the last reboot internal timers are not

working correctly anymore. This has severe impact on system

functionality.

E.g. for Link Aggregation Groups with LACP being enabled the periodic

transmission of LACP messages is stopped, so that the LACP peer will

declare these links as failed, thus dropping traffic.

Problem 11.01.25 - nb95027

ES64U: Transmission of LACP messages for non-Attached LAG links

stops without obvious trigger

When using Link Aggregation groups with LACP being enabled where

not all members are in state Attached (e.g. in combination with Multi-

Chassis LAG of 7750 only the active leg is Attached, the standby leg is

shown to be in state "Reserved") the periodic transmission of LACP

messages for such a non-Attached LAG leg may suddenly stop without

any obvious trigger. The LACP peer will declare this LAG leg as Failed,

effectively losing protection of the active leg.

The root cause is a wrong handling of a FIFO buffer inside the ES64U

used for LACP message transport. If the buffer ran full once then only

corrupted LACP messages will be passed through this FIFO, being

dropped further down in the transmission path on ES64U.

Fixed Problems

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




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



GE10PL1: First Controller Reset in 10GbE mode not hitless after

reducing VCG size

When operating a GE10PL1 pack in 10GbE mode the first Controller

Reset after reducing the size of the VCG by disabling one or more

members is not hitless as expected. Instead a traffic hit of a few seconds

can be observed. Subsequent Controller Resets are hitless as expected.

Problem 10.5.52 - nb94572

GE10PL1: Controller Reset not always hitless for 10GbE/STS1-

192v

When using GE10PL1 in 10GbE mode with an STS1-192v VCG having

all 192 members enabled and all VCGTribs are set to monitored a

Controller Reset of the pack is not hitless when LPT is enabled. Due to

some race conditions while the pack is starting up the laser is switched

off for about one to three seconds. This effect cannot be observed when

VCGTrib monitoring is disabled or when the VCG size is VC4-64v. It is

assumed that also in STS1-kv case for smaller VCG sizes this effect

cannot be observed.

Problem 11.1.25 - nb94638

ES64U: Loss of a single Ethernet frame when adding another flow to a

port which is used as output port of other flows

When adding flows having an output port which is already used as

output port of other flows then a single frame belonging to the

previously existing flows is lost.

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

Fixed Problems





Problem 11.1.11 - nb94697

ES64U: Reboot of active and standby ES64U when using SNMP

community string intended for GET requests also for SNMP SET

requests.

When sending an SNMP SET request but using the SNMP community

string intended for GET requests and ES64U is used in a an equipment

protection group, then the local data controllers (LDC) of active and

standby ES64U perform a reboot more or less in parallel. Consequently

traffic is lost until the active ES64U has finished its reboot.

This reboot only happens in equipment-protected mode of operation.

Fixed Problems

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




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

Fixed Problems in Release.11.01.25 0

Area Packet Management Problem 11.1.11 - nb94474 / nb94275

Alarm for QDR parity errors missing

On rare occasions defective hw inside the ES64U can cause “Quad Data

Rate (QDR) Parity Errors”. By this the ES64 will erroneously discard

packets.

While this problem is infrequent, ALU has added additional alarming

and automatic switch protection to release R11.01.25 (1675 LU). I.e.

these QDR parity errors will be alarmed as HWFAIL followed by an

automatic protection switch if detected.

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

Fixed Problems





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


Area Protection (BLSR/MS-

SPRing, DRI/DNI, APS/MSP,

UPSR/SNCP)

Problem 11.1 - nb89969

Parameters of a path protection group with output in an ACG port

on DS-3 side of a TMUX2G5/1 cannot be edited

If a path protected cross connection has its output tributary in an ACG

port of the asynchronous side of the TransMUX unit TMUX2G5/1 then

the parameters of this protection group cannot be changed afterwards.

The related TL1 command ED_PROTN-GRP is denied with "Input,

Entity Not Exists". This denial affects attempts to change the following

parameters: associated alarm severity profile, hold-off timer, mode of

operation, SNCP type, wait to restore timer.

Problem 10.5.41 - nb93543

Toggling HO-SNCP/UPSR switches may cause CTL reboots and

other side effects due to overload

When the input signals of HO-SNCP/UPSR selectors are permanently

toggling this causes permanent state changes or even permanent

protection switches. Those state changes and protection switches have to

be processed by the system to update the internal database and to report

those changes at the TL1 interface. Due to this massive processing the

system enters an overload condition where it is more or less

unmanagable via TL1. Additionally this may cause also various side

effects:

- periodic CTL reboot about every eight hours due to running out of

memory

- CTL/DCF reboot leading to drop of management connections

- XC reboots (usually no impact in non-ONNS systems)

- CTL hang-up due to failing system shutdown (observed once)

- A traffic outage was observed once which occured due to a parallel Full

Reset of XC and a reboot of the CTL.

Fixed Problems

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

2 - 1 1Alcatel-Lucent - Proprietary



Problem 8.0.1 - nb66277 (nb68110)

Wrong Traffic Squelched Alarm during MS-SPRing/BLSR node deletion

When a node is deleted from an MS-SPRing/BLSR ring by using the

recommended procedure, a Traffic Squelched alarm might be raised by

the nodes adjacent to the deleted one. When following this procedure,

the node to be deleted is not allowed to have other connections than

higher order (HO) through connections carrying circuits originally

routed via the deleted node. For these HO through connections no

squelching must occur in this scenario and has also not been encountered

during tests. The wrong Traffic Squelched alarm clears together with the

Ring Protection Switch Suspended alarm.

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

Fixed Problems





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


Area Configuration

Management


Autonomous ES64U reboots

When using any prolonged CLI scripting to access ES64U units with

R11.1.0 or R11.1.1, these commands consume memory improperly over

time resulting in resource congestion of the ES64U’s memory.

The following has been observed:

• ES64U boards may autonomously reboot (typically STDBY only and

non-traffic effecting)

• Sometimes ES64U reboot switches lead to customer login "lockouts"

that require further intervention to clear (also not traffic effecting if

resolved properly)

• Less frequently an active and standby ES64U reboot can occur

simultaneously leading to a temporary outage, based on number of flows

provisioned.

Fixed Problems

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




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



Download, Backup &

Restore, Upgrade

Problem 11.1 - nb89775 (90044)

ES64U: Sometimes CPFail after pack reboot

After a reboot of ES64U, e.g. due to EQP creation or EQP switches,

sometimes a CPFail is raised for this pack. Applying another Controller

Reset or Full Reset to the pack usually clears the CPFail, in rare cases

another reset is required. If such a pack is part of an equipment

protection group it cannot become active. If it is unprotected traffic is

lost. The probability of this effect is about 20%.


Rolling DB Restoration or Rolling SW Upgrade in a ES64U

configuration where the standby ES64U is pulled takes several

hours until new configuration/new SW generic is activated,

potentially causing traffic interruption for several hours.

When performing a DB Restoration/SW Upgrade to a system where

equipment-protected ES64U packs are provisioned a rolling DB

restore/SW upgrade is initiated to minimize traffic impact. However, if

the standby pack is pulled when initiating the rolling restore/SW upgrade

the system waits for a period of 6 hours until the (pulled) standby ES64U

indicates that it has finished its initialization. Only after this timeout of

six hours this process is interrupted and the active ES64U pack is reset to

restart and reconfigure it with the new database/SW generic.

This means that in case of a DB restore where

- the active ES64U is still operational with the old database the new

database will not be active before the six hours timeout plus the time

until it has restarted and applied the new configuration. During the six

hour timeout the active ES64U will continue to forward traffic according

to the old configuration.

- the active ES64U is not operational traffic is interrupted for thetimeout

period of six hours plus the time the ES64U needs to complete

initialization according to the new configuration.

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

Fixed Problems





In case of a SW Upgrade the first case above applies, i.e. active ES64U

continues to run the old SW generic during the timeout period.Traffic is

interrupted after the timeout until the new generic has completed starting

up and has applied the configuration to HW.

Area Configuration

Management


ES64U: CPCOMF alarms during extensive provisioning activities or

DB restore

When performing extensive provisioning activities, e.g. when enabling

the input and output membership of an ES64U VCG provisioned for

10GbE capacity (i.e. STS1?192v) by sending a sequence of TL1

commands one after the other or during a DB restore temporary

CPCOMF alarms may be raised due to ES64U being in an overload

condition. Such activities usually take very long (enabling of all 192

members of a 10G VCG may take 4 to 5 minutes).

In case of bulk configurations of multiple VCGs also an overload

condition on standby XC has been observed, leading to a temporary

CPCOMF alarm of the standby XC pack as well.

In the case of enabling 192 members of a 10G VCG also toggling

GFPLFD and GFPCSF alarms may occur if the cross?connections

related to the involved VCG are already created and the remote end of

the VCG link is already provisioned and working.

Problem 9.0.4 - nb89704

Explicit or implicit sub structure change of 1st TUG-3 from 21 *

TU-12 into TU-3 disturbs all TU-12s in the 2nd and 3rd TUG-3

Explicit or implicit sub structure change of 1st TUG-3 from 21 * TU-12

into TU-3 disturbs all TU-12s in the 2nd and 3rd TUG-3 Customer

Impact: When in a system with LOXC40 the first TUG-3 of an egressing

VC-4 is currently sub-structured into 21 * TU-12 and then the sub-

structure of this first TUG-3 is changed into TU-3 then any VC-12 in the

second and third TUG-3 of the VC-4 will get a short traffic hit (about 70

ms). The root cause is that the multiframe indication of the egressing

VC-4 gets transiently lost. The substructure change in the first TUG-3

can be caused by an explicit sub structure change or by switching a VC-

3 cross connection.

Fixed Problems

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





SPRing, DRI/DNI, APS/MSP,

UPSR/SNCP)


Enabling of DCC protection not denied when transparent DCC

present

The ED-PROTN-GRP command is not denied, when DCC protection is

enabled (dcclmsprotmd=ENABLE or dccsrsprotmd=ENABLE) for a

MS protection group while transparent DCC cross connections are

present at the protection port.

This results in an illegal configuration with the transparent DCC not

working properly. According to the test results, the protected DCC at the

worker port is OK.

Problem 10.5.2 - nb89992 (nb89716)

Auto-recovery might be not complete after an input power interrupt

or an INIT-SYS command

During a restart due to a power interrupt or an INIT-SYS TL1 command

it can occur that the lasers of ports in BLSR or MS SPRING protection

groups are not switched on again or that the lasers are switched on, but

the K-byte protocol is not correctly re-started. Consequently the ports in

the neighbor nodes continue to indicate LOS alarms for the links sourced

from the affected ports or the neighbor nodes will raise DefaultKbytes

(DKB) alarms for these links. The problem is caused by race conditions

during system recovery and has been observed for systems equipped

with CTL/-.

Problem 8.0.24 - nb90738

A path might transmit AIS caused by incomplete removal of

previous MS-SPRING / BLSR squelching actions

A path might transmit path AIS if for one of its path segments the

following history is true:

1. The path segment has been part of a BLSR or MS SPRING

2. Traffic has been squelched on this segment (i.e. path AIS has been

inserted into the path segment in accordance with the situation in the

MSSPRING / BLSR)

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

Fixed Problems





3. Protection switching has been suspended while squelching was still

active. One potential root cause for suspension of protection switching is

that a node has been added to or removed from the ring.

4. The reason for the squelching has cleared while protection switching

was still suspended. One reason for that is that the cross connections of

the path segment have been deleted. Another could be that the ring

topology has been changed again.

In this case the AIS which has been inserted due to the squelching action

is not physically removed. Consequently the AIS insertion will remain

and will have impact on the current path (if there is still any) or on any

new path which is set up later and which is routed across the timeslots of

the affected bandwidth.

Area Performance

Monitoring


ES64U: PM Data retrieved via CLI/SNMP might show wrong

information on discarded frames

In case of congestion the PM data available via CLI/SNMP might show

wrong information w.r.t. dropped frames. In a scenario with two flows,

one with 1G CIR, the other with 1G EIR, both having the same output

port with just 1G output capacity the following can be observed:

- Frame forwarding works as expected, i.e. all CIR frames are

forwarded, only EIR frames are dropped

- However, PM data retrieval indicates that also green (CIR) frames are

dropped, which is not correct.

The NP of ES64U seems to count yellow frames being dropped

erroneously as green.

Beside the wrong counting no further bad side effect is known. The

observed behavior seems to occur only under heavy load conditions of

the NP.

Fixed Problems

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





ES64U do not count Dropped frames in pm counter.

Frames, which exceed the defined size (2026 bytes) of the egress port,

are correctly dropped but not counted in the related pm counter. The

retrieve of the related PM counter e.g. via CLI shows zero dropped

frames.

Area Packet Management Problem 11.1 - nb89979

When switching a FSF-loop on a 10GbE port of GE10PL1 a

LANPHYNOSYNC alarm is raised and Client-signal-fail is

indicated via the WAN-link towards the remote NE.

When enabling the far-side-facility loopback at a 10GbE LAN port of

the GE10PL1 the system detects an unexpected NOSYNC condition and

raises the LANPHYNOSYNC alarm. This leads to sending a Client-

Signal-Fail indication via the WAN-link towards the remote end. This

triggers a consequent action (e.g. disable the laser at the LAN-port) at

this remote NE, if enabled, and disrupts the looped traffic.

This applies for 10GbE ports, only. 1GbE ports are not affected.


Setting outmbs on ES64U for VCG tribs to disable does not

influence CSF

When you set a unidirectional cross-connections from the ES64U

towards GE10PL1, CSF is always transmitted upstream. The parameter

OUTMBS (output membership) in TL1 command ED-VCGTRIB has no

impact to the CSF control.

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

Fixed Problems





Problem 10.5.2 - nb89604

In rare cases a CPCommFail alarm may be raised for GE10PL1

during normal operation

It has been observed in rare cases that during normal operation, either

while processing autonomous events caused by WAN failures or while

processing provisioning requests, a CPCommFail alarm is raised for

GE10PL1 packs permanently. The reason for this CPCommFail alarm is

that the pack does no longer send periodic fault status information to

CTL. Consequently fault reporting for the pack in this state no longer

works.


GE10PL1: Traffic might not come up after fast disabling and

re-enabling of VCG members

When disabling VCG members with a delay of less than two seconds

and interleaved at both ends of a VCG trail (i.e. disabling member #1 at

near end, then disabling member #1 at far end, then #2 at near end, #2 at

far end, and so on) bandwidth is reduced as expected and after disabling

the last member traffic is interrupted as expected.

When enabling some or all of these members again (regardless of order,

quantity or delay between the commands) traffic might not be

established as expected. Instead some of the members use wrong

sequence numbers so that the LCAS sink cannot re-assemble the

Ethernet frames from the GFP stream.

This effect was not observed, when disabling the members first at one

side, then at the other, or when waiting for two seconds between the

commands to disable the members.

Fixed Problems

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




Area CIT Problem 10.5.1 - nb91618

WS-CIT sometimes faces difficulties to maintain connection to

LambdaUnite via TCP/IP

In rare cases the connection from CIT to LambdaUnite via TCP/IP gets

interrupted

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

Fixed Problems





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

Fixed Problems in Release.11.1 0

Area Performance

Monitoring


Wrong DS1 PM counters on TMUX2G5 in case of DS1-LOF

When a TMUX2G5 detects a DS1-LOF condition the PM counters do

not correctly reflect this. The counter ES-P, SES-P, SAS-P and

consequently UAS-P are not incremented further as long as the LOF

condition is persistently present.


During Loss of signal condition wrong Received bytes may be

counted by PM counters

In the case of a loss of signal condition at a optical interface module of

the 10GPL1 (LANLOS or NOSYNCH condition) a possible optical

noise may mimic valid bytes which are counted in the EONB and EINB

PM counts and give the wrong impression of a valid signal. During such

period no valid frames are counted.


Download, Backup &

Restore, Upgrade


ES64U: No provisioning possible for some time during a DB backup

While executing a DB backup from the system there is a time window

where no provisioning actions can be executed on ES64U via

CLI/SNMP. This time window is related to the timeframe where the

ES64U database is copied to CTL for further processing together with

the database part s stored on CTL. Provisioning requests via CLI/SNMP

are denied during this timeframe.


ES64U: Wrong LED indication when opening the upper latch while

pack is still starting up

When opening the upper latch of ES64U a graceful shutdown should be

initiated allowing to complete pending operations on CF-disk of ES64U

to avoid file system corruptions.

Fixed Problems

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




However, when opening the upper latch while the pack is not yet

operational the LEDs of ES64U indicate immediately that the pack can

be safely pulled (i.e. green LED off, red LED on) even though the

shutdwon actions are not yet completed (if started at all). When pulling

the pack immediately there is a risk of corrupting the file system and

losing the database.


ES64U databases not restored on NE with empty database

The ES64U databases contained in a downloaded DB generic are not

restored to the ES64U, if the NE in in maintenence mode after restert

with empty database. This problem is relevant for fall back after upgrade

failures and recovery after CTL failures. In both scenarios, the NE is

restarted with an empty database, what leads to maintenance mode. Then

the last backup is downloaded and applied. This should restore the NE

datbase and all ES64U datbases. But because af the problem, only the

NE database is restored.

Workaround:

Download the database generic again an apply it. But this leads to a

traffic outage for the traffic through the ES64U.


ES64U: Green LED not flashing when opening upper latch

In order to properly shutdown an ES64U pack a special procedure

described in UPG is required to safely shut down the pack. According to

this procedure the upper latch must be opened at first, then it must be

waited until green LED stopped flashing and red LED goes on, before

opening the lower latch as well.

After opening the upper latch the green LED should start flashing to

indicate to the operator that shutdown tasks are going on. However, the

green LED remains in its previous state, i.e. either permanently on or off,

until the shutdown tasks are completed. It is then switched off as

expected.

So the difference to the expected behavior is that it is not flashing during

execution of the shutdown tasks

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

Fixed Problems






GE10PL1: After Controller Reset some VCG members may end in

state FAILED, thus WAN bandwidth is reduced

When applying a Controller Reset to a GE10PL1 at one end of a VCG

trail it may happen that some VCG members enter the state FAILED,

even though the path is error free. Consequently the WAN bandwidth is

reduced.

This has been observed in different configurations:

• with LCAS htmr=0 at the end being reset and htmr=1sec at the

other end

• with symmetric setting of htmr=0 at both ends

When setting the hold-off symmetrically to 300ms at both ends the effect

was not observed.

When using the 10GbE interface with htmr=0 at the one end and 1sec at

the other end the issue was never observed in 230 runs.

Problem 8.0 - nb67830 (nb59928)

Traffic Hits on Controller Resets of GE10PL1

When applying a Controller Reset to the GE10PL1, e.g. by the TL1

command INIT-EQPT or during a software-upgrade, the resulting reboot

of the GE10PL1 is not hitless. Instead a traffic loss is observed:

• When using the 1GbE ports a traffic hit in the range of 1.2 to 2.2

seconds has been observed.

• When using the 10GbE port, a traffic hit in the range of 5 to 6

seconds has been observed.

At the remote side of the WAN-link a Total Loss of Capacity alarm will

be raised temporary caused by the traffic interruption.

If LCAS is enabled and the Wait-to-restore timer is set to a value higher

than zero (which is the default value) then this WTR-time adds to the

traffic interruption time.

Fixed Problems

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




Problem 11.0 - ch00306

GE10PL1: LCAS WTR Timer also applied during Reset of

GE10PL1

When applying a reset to GE10PL1 while LCAS is enabled the LCAS

wait-to-restore (WTR) timer is also applied for VCG members becoming

good again.

In case of a Controller Reset traffic is affected due to another known

issue (nb67830). Once the VCG members become good again after the

initialization the currently provisioned WTR time is applied, extending

the outage time caused by the Controller Reset.

In case of a Full Reset traffic is interrupted anyhow. However, the time

until traffic is restored is extended by the currently provisioned LCAS

WTR (the default of this paramater is 0 min). This is not considered an

issue, because also after a full traffic loss, e.g. due to a fiber cut, the

WTR timer is applied for the first member to become good again, thus

extending the overall outage time by the WTR time.

Problem 10.0.1 - nb88600

GE10PL1: Switching and Releasing of FSF loop on 10GbE port not

reliable

When switching or releasing a Far-side facility (FSF) loop at the 10GbE

port of a GE10PL1 pack this operation is not reliable to take effect.

When switching the loop it might in fact not be switched even though the

system reports it to be active. When releasing a loop it might not be

released properly even though the system reports it to be released.

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

Fixed Problems





Area Equipment Protection Problem 11.0 - nb87590

ES64U: CPFail Alarm raised for several minutes when creating

ES64U EQP group

When creating an ES64U equipment protection group a CPFail alarm is

raised for the standby ES64U pack. The alarm is cleared after several

minutes during the process of initialization and synchronization of the

standby pack.

Fixed Problems

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




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

Fixed Problems in Release.11.0 0

The problem communicated via the following alert has been fixed in

1675.LambdaUnite®.MSS Release.11.0:

• 08-0392 1675 LambdaUnite MSS - Loss of Management

Association


SPRING, DRI/DNI,

APS/MSP, UPSR/SNCP)


Roll crossconnect command of the TU3-side of a AU3 to TU3

conversion connection fails if the source of the AU3 is sourced by a

DS3 located on a EP51

In the case a roll command for the TU3 side of a AU3 to TU3 conversion

connection (roll the LO TU3 to a new HO VC of a STM-N port) with the

AU3 being sourced by a DS3 from an EP51 is entered , this is rejected.

The error code of this invalid rejection is "Input, Data Not Consistent,

LO tributary not supported by that pack (e.g. OPT2G5, EP51, GE1)".

Area DCC/DCN

Management

Fixed Problem - nb86129/86194/86516 (Alert 08-0392)

Management systems may lose association to the 1675 LambdaUnite

and login is impossible

Management systems may lose association to the 1675 LambdaUnite

and login is impossible. It has also been observed that communication

between management systems and the 1675 LambdaUnite is very slow.

This is caused by memory leaks. Memory leaks occur with certain TL1

commands (primarily ENT-USER-SECU, ED-PID, ED-USER, ED-

USER-SECU, ENT-BANNER, ACT-USER, CANC-USER, CANC-

USER-SECU, and DLT-USER-SECU), Failed User login/logouts,

Enable/Disable DCC channels commands (ENT-FECOM), and Large

Memory Retrieval (LMR) commands where huge amounts of data are

requested.

Due to these leaks insufficient free memory is available on the CTL to

fulfill requests from the management system. Depending on the usage of

the NE and the controller type, the time until this effect becomes visible

may vary greatly.

On CTL/3T, the incidence of the problem is reduced due to the higher

amount of RAM Memory available. Also when the system is equipped

with this controller, an automatic reboot of the TL1 controller function

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

Fixed Problems





takes place when the consumed memory allocated to TL1 processing

exceeds a predefined threshold. This action may result in an autonomous

recovery from the problem. With CTL/- a loss of association will occur

when this threshold is met.


GE10PL1: Traffic may not be established when sequence numbers

of VCG members are unsorted in non-LCAS mode

According to standards in non-LCAS mode the sequence numbers of

VCG members have to be sequential, i.e. the member i uses sequence

number (i-1). In LCAS-mode arbitrarily ordered sequence numbers are

allowed.

However, a VCG source of GE10PL1 does not behave according to

standard and may use unordered sequence numbers depending on the

order of provisioning:

• E.g. when enabling trib #1 and #3 followed by #2 the used sequence

numbers are 0, 2, 1 instead of 0, 1, 2

• When disabling LCAS the order of sequence numbers remains

unchanged. So when the sequence numbers were unordered before

switching off LCAS they remain unordered.

A VCG sink of GE10PL1 accepts arbitrarily ordered sequence numbers

and resorts the members accordingly. So connecting GE10PL1 to

GE10PL1 is not an issue. However, when interworking with equipment

which does not accept arbitrarily ordered sequence numbers no traffic is

possible over such a link.


GE10PL1: Long traffic interruptions in case of SDH/SONET

protection switches

When the pathes ending at a GE10PL1 are double-protected by LCAS

and SDH/SONET protection schemes, e.g. SNCP/UPSR, the traffic hit

on an Ethernet link in case of a SDH protection switch is longer than

without LCAS.

For a VC4-7v link the following traffic interruption times have been

measured with SNCP (LPT disabled, 2000 runs):

With LCAS disabled all times were below 80ms, 86% of the runs

showed even less than 60 msec (the interruption time usually allowed in

SDH protection schemes consisting of 10ms detection time plus 50ms

swicthing time)

Fixed Problems

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




On the other side, with LCAS enabled, resulted in times of up to 200

msec, in rare cases even higher.

If LPT is enabled (default) this might cause another interuption if the

corresponding hold-off timer is set to 0ms.

Area CIT Problem 11.0 - nb87272

CIT fails to send APPLY command after a successful DB Download

The user would assume the activation of the database, but CIT would not

have activated.

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

Fixed Problems








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

3 Known Problems

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

Contents 0

Introduction 3 - 2





Area Equipment Protection 3 - 7

Area Fault/Alarm Management 3 - 7



Area CIT 3 - 14

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

Known ProblemsIntroduction





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

Introduction 0

This chapter provides descriptions of significant customer-affecting

problems known to exist in 1675.LambdaUnite®.MSS Release 11.01.28

Network Element software/hardware and WaveStar®.CIT software.

Workarounds are provided where they apply.

Known Problems have been grouped into the following functional areas

• Area Installation, Software Download, Backup & Restore, Upgrade

• Area Configuration Management

• Area Synchronization Management

• Area Protection (BLSR/MS-SPRing, DRI/DNI, APS/MSP,

UPSR/SNCP)

• Area Equipment Protection

• Area Fault/Alarm Management

• Area Performance Monitoring

• Area DCN/DCC Management

• Area Security Management

• Area Packet Management

• Area CIT

The syntax of the problem number, e.g. “Problem 2.0 - nb12345” is as

follows:

• first part: the problem is known since this release

• second part: internal number

• in some cases a second internal number in brackets means that the

internal number of the problem has changed; the number in

brackets denotes the old number used in the Software Release

description of a former 1675.LambdaUnite®.MSS release

Known ProblemsKnown Problems

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




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

Known Problems 0

0Area Installation, Software

Download, Backup &

Restore, Upgrade


Permanent Loss of management connection when connecting a QT600 test

set

It has been observed at customer sites that when connecting a JDSU

QT600 Ethernet test set to LAN port 2 of 1675 LambdaUnite a

CTL/DCF boot loop may occur, thus losing management connectivity to

this NE. The tester seems to have send an improper login request

followed by an abort request which is not correctly handled by DCF and

causes the reboot.

Workarounds:

There are two alternative workarounds.

The first one being to disconnect the QT600 from LAN2. The CTL will

autonomously clear the fault by a reboot.

If it is not desired to remove the JDSU QT-600 from the network, a

second option to clear this condition is to follow the steps below and

change the JDSU TAM Interface from Master to Passive. Once these

steps have been completed, this condition will autonomously clear from

the 1675 LU MSS with one completed reboot cycle of the CTL circuit

pack.

These steps have been provided by JDSU Technical Support as a high

level of the required steps. If additional assistance with these steps is

required, please contact your JDSU Technical Support organization for

further assistance.

Change the JDSU QT-600 Tam interface from Master to Passive on each

installed JDSU QT-600 in this location.

1. login in as craft

2. press 1 and then enter to continue into craft mode

3. press 3 and then enter for tam configuration

4. press 1 and then enter to select tam mode

5. press 1 and enter to select passive

6. press 0 and enter to return to previous menu

7. press 9 and enter to save

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






8. verify you see the tam mode is passive - tam mode passive should

appear on the top of the session.

9. press 0 and then enter to return to main menu

10. press 0 and then enter to exit and logout as craft

Once either of the above options has been performed, logins should be

allowed. In some instances it is possible that the 1675 LU MSS User ID

that was provisioned for the JDSU QT-600 has become invalid. If login

attempts using the JDSU QT-600 User ID are denied, delete this login

from the 1675 LU MSS and provision this User ID again exactly as it

was previously set. This will allow the JDSU QT-600 to establish login

session again.

0Area Configuration

Management

Problem 10.5.4 - nb94363

Sending two consecutive CTL Reset Requests within a few seconds may

cause CTL bootloop (simplex case) or an unusable CTL (duplex case)

When sending a command to request a CTL reboot and, within a few

seconds, sending the same request again, then this second request may

result in marking the CTL unusable. In a simplex configuration the CTL

will not be able to start up anylonger (boot loop). In a duplex

configuration this CTL will not become operational anymore. The same

may happen when sending a request to reset another pack as the second

command. The root cause is that the second request is started to be

processed, especially the check of SW generics on CF-disk is started a

second time, but this second check fails due to the shutdown actions

caused by the first reset request. This failed check marks the CF-disk as

unusable, such that this CTL cannot start up anymore. The commands

leading to a reset of the active CTL are

- INIT-EQPT with a CTL AID

- INIT-SYS

- Leave mcond (ED-STATE-EQPT with mcond=N)

- APPLY

in the course of a SW Upgrade

The commands triggering a check of the SW generics on CF-disk (i.e.

those which should be avoided to be sent as the second one) are

- INIT-EQPT to any pack


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




- INIT-SYS

- leave mcond (ED-STATE-EQPT with mcond=N).

Workaround:

Avoid to send multiple commands leading to a CTL reset within a few

seconds.

0Area Protection

(BLSR/MS-SPRing,

DRI/DNI, APS/MSP,

UPSR/SNCP)

Problem 10.5.2 - nb93224

Short Failure at MS-SPRING/BLSR port may cause Protection Switching

and Squelching due to invalid K-Bytes

In case of a short failure at an MS-SPRING/BLSR port, e.g. caused by a

protection switch on optical layer in a DWDM system, it may happen

that invalid, but acceptable K-bytes are injected into the MS-

SPRING/BLSR ring. These invalid K-bytes may start rotating through

the ring, if they contain an unknown Node ID.

Due to the mechanism to declare a SF condition if too many K-Byte

changes are detected in a certain period of time, further propagation of

the invalid K-bytes is stopped. However, the SF condition now triggers

MS-SPRING/BSLR protection switches and traffic squelching actions

(the SF may be declared by more than one node). After three seconds the

SF condition is cleared and the situation normalizes again.

Workaround:

Provision Extra Traffic in at least one of the ring nodes. This will prevent

to forward the invalid K-bytes.


Inconsistent state information for MS SPRING / BLSR ring entry/exit

points

Cross connections of MS SPRING / BLSR service traffic circuits have

attached state information for the ring entry point (loca) and the ring exit

point (locz). These states are called "locastate" and "loczstate". A cross

connection of an MS SPRING / BLSR ring circuit is considered

bidirectional if there are cross connections of the same rate for both

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






directions which have consistent loca and locz information. However,

the consistency of the locastate and loczstate information is not checked

for this purpose. For the case that ring entry and exit information is

manually provisioned (ED-PROTN-GRP parameter "asmc" = disabled),

the locastate and loczstate should always have the value "MANUAL-

VALID" if the entered TID is part of the ring map.

Nevertheless, cases of incorrect state values "MANUAL-INVALID"

have occurred. If this problem affects only one direction of a

bidirectional MS SPRING / BLSR cross connection then the result of

cross connection retrieval operations (RTRV-CRS) will become

inconsistent. Dependent on from which end the cross connection is

retrieved, the incorrect value of "MANUAL-INVALID" will become

visible or not.

Workaround:

Once occurred the problem of incorrect locastate or loczstate values can

be repaired by enabling automatic squelch map calculation in the

affected node and ring and disabling it later again (parameter "asmc").

Another option is to change the related TID value (loca or locz) forth and

back via the ED-CRS command. This will also cause to re-calculate the

locastate and loczstate.

Problem 10.5.5 - nb93083

SYSCOMF alarm may be an indicator for toggling LO-UPSR protections

if interface standard of NE is SONET.

If the input signals to LO-UPSR selectors are not stable and cause a lot

of LO-UPSR switches this may cause the system to enter an overload

state where it throttles the generation of LO-UPSR switch notifications.

If this state persists for some time and the system's interface standard

is set to SONET then a SYSCOMF alarm is raised as an indicator for this

state.

Therefore the operator should check whether the system is in an

overload state due to massive LO-UPSR switching. The output of the

TL1 command RTRV-OVLD may give further hints on LO tributaries

causing the notification load.

Workaround:

When a SYSCOMF alarm is raised and the interface standard is SONET

then first follow the trouble clearing procedure for the alarm

PROCROVLD before following that of SYSCOMF.


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




0Area Equipment

Protection

Problem 9.0.3 - nb87425

CTL reports CPFail due to slow synchronisation in very rare cases

It has been observed in very rare cases that after a reset of the standby

CTL, e.g. due to a Duplex CTL switch or a reset applied to the standby

CTL, the initial synchronisation of the CF-disk content takes place very

slow and does not complete with in 45 minutes. After this timeout a

CPFail alarm is reported for the standby CTL.

Workaround:

If a CPFail alarm is raised about 45 minutes after a duplex switch or after

resetting the standby CTL apply a Full Reset to the standby CTL. If the

CPFail alarm does not clear permanently the CPFail has a different root

cause and the CTL should be replaced.

0Area Fault/Alarm

Management

Problem 10.0.1 - nb90684

STM1 Port on OPLB with STM1/OC3 interface modules always uses the

default ASAP

In the case of an OPLB equipped and configured for STM1/OC3 ports

an assigned non default port ASAP will not be used. Instead always the

default ASAP is taken for severity calculation.

Workaround:

The only workaround possible is to modify the default ASAP for the

fault causes where a modification is required. If the defaults are required

for other ports a copy of this can be made for these ports and this copied

ASAP could be taken e.g. private ASAP Def1 for the other ports

requiring the original defaults.

Problem 10.0.1 - nb90703

OPLB used for STM1/OC3 Port capacity always uses the default ASAP for

path instances

In the case of an OPLB equipped and configured for STM1/OC3 port

capacity an assigned non default ASAP as e.g. PATH ASAP assigned to

a tributary of a port will not be used. Instead always the default ASAP is

taken for severity calculation.

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






Workaround:

The only workaround possible is to modify the default ASAP for the

fault-causes where a modification is required. If the defaults are required

for any other instances in the system a copy of this can be made for these

instances as e.g. path entities, and this copied ASAP could be taken

instead of the modified default. So e.g. create a private ASAP e.g. DEF1

as copy of the default , assign this for the instances in the system

requiring the original default, and modify the default ASAP to the

desired values.

0Area Performance

Monitoring


ES64U historical PM bins are lost after reboot of ES64U

After a reboot (also an upgrade to the next release) of the ES64U the

historical bin data for 15min and 24h data are lost.

Workaround:

Retrieve the historical data on a regular base if information is needed.


Failure Counters for DS3 and STS1 on TMUX2G5 count wrong

The Failure Counts FC-P and FC-PFE related to the DS3 termination

and STS1 termination at the asynchronous side of TMUX2G5 do not

count failure events as expected. Instead they count the seconds where a

failure is present.

E.g. when a LOS is detected and cleared after five seconds, FC-P is

expected to be incremented by 1. However, it actually is incremented by

five.

Workaround:

None.


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





TMUX2G5: DS1 PM counter FC-P never incremented

The DS1 PM counter FC-P related to DS1 NIMs on TMUX2G5 is

always reported with a value of zero and is never incremented. The

reason is that it is currently not fully supported by the system.

Workaround:

None.

Problem 10.5 - nb89559 (nb86495)

Wrong DS1 PM counters on TMUX2G5 in case of DS1-LOF

When a TMUX2G5 detects a DS1-LOF condition the PM counters do

not correctly reflect this. The counter ES-P, SES-P, SAS-P and conse-

quently UAS-P are not incremented further as long as the LOF condition

is persistently present.

Workaround:

None.

0Area Packet Management Problem 11.01.27 - nb95084

ES64U: Inconsistent MAXMTU settings may lead to CARD_FAIL alarm

When the MAXMTU size for ports on ES64U is not configured

consistently this may result in an unexpected CPFAIL/CARD_FAIL

alarm being raised for the ES64U card.

This may happen under the following circumstances:

+ The MAXMTU of the ingress port is larger than the MAXMTU of the

egress port,

+ All traffic arriving at this ingress port has a frame length larger than

the MAXMTU if the egress port, such that the frames pass the MTU size

check of the ingress port but are dropped at the egress port.

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






+ Beside the ingress or egress port there is no other port existing on the

same GAUSS device, which carries traffic.

Workaround:

Ensure to consistently provision MAXMTU of ports being used as

ingress and egress ports of flows.

Problem 11.01.25 - nb94411 / nb94519

ES64U: UPSR switching times high when LCAS is enabled and LCAS-

HTMR=0

When the tribs of a VCG located on ES64U with LCAS being enabled

are protected by UPSR and a UPSR switch occurs it is expected that the

resulting traffic interruption time is less than 50 msec. However, if the

LCAS hold-off timer is set to 0 the observable traffic hits are below 50

msec with a probability of about 75%, about 20% have a duration of 3

seconds and the rest is somewhere in between.

When using an LCAS hold-off timer of 100msec then the traffic hit is

below 50 msec with a probability of about 95% with outliers of up to

about 3 seconds.

Workaround:

If VCG tribs are UPSR-protected set LCAS holdoff timer to 100msec or

higher.


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




Problem 11.01.25 - nb94390 / nb94518

ES64U: EQP blocked on Reset of active ES64U when Forced Switch is

active

When applying a Forced Switch to the active ES64U and now resetting

the active ES64U card the ES64U will reboot as expected and become

operational again. However, the Equipment Protection Group will be

blocked, after clearing the forced switch further switch requests are

rejected, also autonomous switching is disabled.

This state is notified at the management interface with a Switch Request

State of EF for the equipment protection group and an Equipment Status

of EF for both ES64U packs.

Workaround:

To re-enable the equipment protection group again the standby ES64U

must be reset twice. After the first reset request the standby ES64U will

not become operational due to a failed synchronisation with the active

ES64U. Therefore another Reset is required, about 15 minutes after the

first one. Now the standby ES64U succeeds to synchronise and become

operational, the Switch request State and the Equipment Status changes

to NR.

Problem 11.01.25 - nb94442 / nb94449

ES64U: Clearing an LCAS WTR Timer not supported

When a member of a VCG located on ES64U with LCAS being enabled

is in a wait-to-restore state, i.e. a failure has cleared again, but the

member has not been activated again because the WTR timer is still

running, the operator should be able to terminate the WTR period using

the TL1 command OPR-VCGTRIB-STS. However, this command is

always rejected by the system with error code

SNVS /* Status, Not in Valid State, Tributary is not in state wait-to-

restore */

when applied to a VCGTrib on ES64U.

Workaround:

Disable and re-enable output membership of the VCGTrib to terminate

WTR period.

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






Problem 11.01.25 - nb94333

ES64U: No MND alarm if VCG member is removed because of too high

differential delay

When a VCG member of ES64U is removed by LCAS from the group

because its differential delay is too high related to the other VCG

members then, beside the PLCR alarm, a MND (Member Not

Deskewable) alarm is expected. However, due to the generic decision to

not support tributary related alarms on ES64U no MND is raised.

Workaround:

When a PLCR (Partial Loss of Capacity) alarm is raised for a VCG of

ES64U and membership provisioning is consistent at both ends of the

VCG then check for trib alarms on the related I/O pack to which the

VCG tributaries are cross-connected.

If the membership provisioning is consistent and there are no trib alarms

on the I/O packs then the root cause of the PLCR alarm is most likely a

differential delay that is too large for the failed ES64U VCG members.

Problem 11.01.25 - nb94345

ES64U: Disabling of VCG members in LCAS mode only hitless if waiting

long enough between the provisioning steps

When reducing the size of a VCG having LCAS enabled this is expected

to be hitless if following the correct order (disable source side (inmbs),

before sink side (outmbs)). However, for a VCG on ES64U it is also

required to wait for at least one second between the single provisioning

steps. E.g. when removing one trib bidirectionally from a VCG between

a GE10PL1 and an ES64U then

- disable inmbs at GE10PL1 and wait one second

- then disable inmbs at ES64U and wait one second

- then disable outmbs at GE10PL1 and wait one second

- then disable outmbs at ES64U.


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




When following these steps the trib removal is hitless.

Workaround:

Wait at least one second between the provisioning steps.


ES64U is not able to push vlan when the inflowclassifier has same vlan

The attempt to push for an ETS the same VLAN ID via CLI is denied, if

the inflowclassifier has this VLAN ID already.

Workaround:

Need to define different vlan tag on classifier or on push table - for the

same port

Problem 10.0 - nb83944 (nb83632)

Disabling of LCAS causes traffic hit which is longer than expected

When an Ethernet connection is set up and LCAS is disabled at one end

a traffic hit occurs which is longer than expected.

When disabling LCAS at the remote end of the VCG-trail while

GE10PL1 at the local end of the trail still has LCAS enabled traffic is

lost for a rather long period of time. Instead of a potential short hit

caused by the need to resort the members the following hit times

havebeen observed:

+ 1GbE connection

- VC4-7v/STS3c-7v: about 0.6 seconds

- STS1-21v: 0.7 to 1.1 seconds

+ 10GbE connection

- VC4-64v/STS3c-64v: 5.6 to 6 seconds

- STS1-192v: 45 to 49 seconds

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






When disabling LCAS at the remote end while LCAS is already disabled

locally at GE10PL1 only the potential expected short hit may occur

(proven only with GE10PL1 at both ends).

Workaround:

None.

Problem 8.0.1 - nb95033

GE10PL1: VCG member not declared failed on degraded

condition

When for a VCG member of GE10PL1 a degraded condition is detected

due to a high bit error rate, this is alarmed by a THPDEG alarm.

However, in case LCAS is enabled for this VCG, the degraded condition

does not lead to declaring the VCG member as failed, thus the member is

not removed from the VCG.

Under a degraded condition, however, the VCG member may be

removed due to other failures, e.g. if the LCAS and VCAT protocol

information transported in the H4 byte of the overhead has errors.

Workaround:

Remove a member manually when a THPDEG alarm is present.

0Area CIT Problem 11.01.28 - nb95142

No further support of BWM orTDM10G

Due to incompatibility of the Java versions it is not possible that BWM

or TDM10G will be supported by the CIT of R11.01.28.; So this support

is removed.




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

4 New Installation and Upgrade

Procedures

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

Contents 0

General 4 - 4


updated PC requirements 4 - 4

Upgrade from Release 11.01.27, Release 11.01.26 or Release.11.1.11 to Release 11.01.28 4 - 4

Upgrade path survey 4 - 5

New Installation and Software Upgrade 4 - 6

Overview 4 - 6

To perform an initial NE software download 4 - 7

Purpose 4 - 7

Safety precautions 4 - 7

Before you begin 4 - 7

Instructions 4 - 8

NE Software Upgrade 4 - 12

To upgrade software to a new release 4 - 12

When to use 4 - 12


Prepare CompactFlash® card for fall back solution 4 - 13

Upgrade-preconditions for the Network Element 4 - 13

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

New Installation and Upgrade Procedures





Upgrade-preconditions for the whole network 4 - 14

Instructions 4 - 15

To perform an NE software download for upgrade purposes 4 - 20

When to use 4 - 20

Download limitations 4 - 20

Related information 4 - 20


Instructions 4 - 21

To activate an NE software generic 4 - 26

When to use 4 - 26


Instructions 4 - 27

To check for successful NE software upgrade 4 - 32

When to use 4 - 32


Instructions 4 - 32

To solve NE software upgrade problems 4 - 33

When to use 4 - 33

Instructions 4 - 33

Trouble shooting procedure A 4 - 34

Trouble shooting procedure B 4 - 35

Trouble shooting procedure C 4 - 36

Trouble shooting procedure D 4 - 37

Trouble shooting procedure E 4 - 40

To retrieve NE software generic information 4 - 42

When to use 4 - 42

NE active software 4 - 42

Instructions 4 - 42

Supporting information for “Retrieving NE software generic information” 4 - 43

NE software display window 4 - 43

Elements of the NE software display window 4 - 43

Database backup 4 - 45

Overview 4 - 45

Purpose 4 - 45

To limit the number of saved backups 4 - 45


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




Purpose 4 - 45


Instructions 4 - 45

Manually backup database to the WaveStar® CIT 4 - 47

When to use 4 - 47


Related information 4 - 47


Instructions 4 - 48

To retrieve NE database information 4 - 51

When to use 4 - 51

Instructions 4 - 51

Supporting information for Retrieving NE database information 4 - 52

Elements of the Database Info window 4 - 52

To restore a database to a network element 4 - 54

Purpose 4 - 54



Instructions 4 - 55

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






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

General 0

Known Problems When detecting problems check chapter 3 “Known Problems” of this

document for workarounds.

updated PC requirements The minimum PC configuration that supports the WaveStar-CIT

application:

• Pentium® 4 1.3 GHz or higher recommended.

• Minimum 1GB of RAM .

• 2 GB of free hard-disk drive space

• CD-ROM drive (16X recommended)

• CompactFlash® card device

• SVGA monitor set to minimum 1024x768 resolution, 16

million colors

• 100BaseT LAN interface, installed and working

Upgrade from

Release 11.01.27, Release

11.01.26 or Release.11.1.11

to Release 11.01.28

The Upgrade Software for upgrading an existing

1675.LambdaUnite®.MSS system with Release 11.01.27, Release

11.01.26 or Release.11.1.11 to Release 11.01.28, consists of two parts:

• 1675.LambdaUnite®.MSS Network Element (NE) Software

Version 11.01.28

• WaveStar®.CIT (Craft Interface Terminal) Software

Release.18.09.05 Build.5091

delivered on a CD-ROM (Comcode 109792648 or 109792671

downloadable version).

The WaveStar®.CIT only CD-ROM (Comcode 109799296 or

109799304 downloadable version) does not contain the

1675.LambdaUnite®.MSS Network Element (NE) Software Version

11.01.28, but only the WaveStar®.CIT (Craft Interface Terminal)

Software Release.18.09.05 Build.5091.

The software for the 1675.LambdaUnite®.MSS NE is loaded into the

CTL/memory pack of the shelf via the CompactFlash® card. The

software for the WaveStar®.CIT is installed onto a (Microsoft®

Windows XP® based) PC configured with an Ethernet LAN card. The

procedure for loading both packages is provided below.

Additionally a survey of upgrade paths is embodied in this chapter.


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




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

Upgrade path survey 0

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






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

New Installation and Software Upgrade 0

Overview

This chapter describes both

• the procedures which have to be carried out for the first installation

and

• the procedures for the software upgrade of the

1675.LambdaUnite®.MSS.


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




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

To perform an initial NE software download 0

Purpose Use this procedure to install a software generic in the NE for the first

time.

The software is initially delivered to the customer on a CD-ROM

(Comcode 109792630 or 109792663 downloadable version). The

software generic has to be copied from the CD-ROM to the

WaveStar®.CIT PC and then to the empty CompactFlash® card via

WaveStar®.CIT. Afterwards, the CompactFlash® card is inserted into the

NE.

Safety precautions

Electronic components can be destroyed by electrostatic discharge.

Circuit packs must therefore always be kept in antistatic covers. Use the

original antistatic packaging if possible. Always observe the ESD

instructions.

CAUTION

Improper removal of a CompactFlash® card can result in damaged files

and the generation of information messages such as “lost clusters”

and/or “missing/damaged sectors”.

Be very cautious and follow the specific instructions when handling

CompactFlash® cards.

To assure both personal safety and the proper functioning of the

1675.LambdaUnite®.MSS product, it is imperative to observe the

preceding precautions.

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

1. Acquire the CD-ROM that contains the new generic/version of the

NE software (Comcode 109792630).

Required equipment

The following equipment is required to perform this task:

• Empty CompactFlash® card (the required storage capacity depends

on the used Controller)

• CD-ROM that contains the new generic/version of the NE software

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






• WaveStar®.CIT PC with CompactFlash or PCMCIA slot. For the

second case an adapter is required.

Instructions To initially download the NE software (delivered on a CD-ROM)

proceed as follows:

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

1. Power up the WaveStar®.CIT PC and log into Windows XP® as

administrator. If you are already logged in, close any open window.

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

2. Install the NE software on your PC. To do this, use one of the

following two methods (automatic or manual installation).

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

3.

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

4. Insert the LambdaUnite® CD-ROM with the new NE software.

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

5.

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

6. Click Continue.

IF THEN

You use the automatic

installation method

proceed with the next step.

You use the manual

installation method

proceed with Step 11

IF THEN

the Welcome Screen

appears,

proceed to Step 6

the Welcome Screen does

not appear,perform the following:

1. Go to the Start button.

2. Click Start with the right mouse

button and select Explore.

3. Select the drive that corresponds to

your CD-ROM.

4. Double click the setup.exe file in

the root directory of your CD-

ROM drive.

5. Proceed to Step 6.


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




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

7. Choose the NE Software entry.

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

8. Click the NE Software button on the right.

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

9. Wait for the software transfer to complete.

NOTE: You will notice that the “Copying files, please wait ...”

message and also the InstallShield Wizard disappears when this

operation has completed.

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

10. Click Exit.

Continue with Step 19.

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

11. Manual Installation: Insert the 1675.LambdaUnite®.MSS CD-ROM

with the new NE software. If the welcoming screen appears, select

Cancel to exit from the automatic installation procedure.

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

12. Open the Windows Explorer on your desktop.

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

13. Select the hard disk drive where WaveStar®.CIT is installed (in

most cases C:) and click through to Program Files --> Alcatel-

Lucent --> WaveStar CIT --> generics or Program Files -->

Lucent Technologies --> WaveStar CIT --> generics.

Please note that, if the subdirectory generics does not exist, you

must create it!

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

14. In the generics directory, create a new folder, preferably stating the

new software version in its name.

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

15. In the Windows XP® Explorer, right-click the CD-ROM drive of

your computer and select Explore. Go to the generics directory.

This directory contains two subdirectories: p and up.

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

16. Select the complete up and p directories and copy it to the folder

you created in Step 14.

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






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

17. To install Acrobat Reader on your system, go to the Acrobat Reader

subdirectory on your CD-ROM drive and double-click the

AcrobatReader40.exe file.

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

18. The Software Release Description (SRD) is located in the

Documentation subdirectory of the CD. You can read it by double-

clicking the .pdf file in this subdirectory.

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

19. Insert the empty CompactFlash® card into the CompactFlash® slot

(or PCMCIA slot with adapter) of the WaveStar®.CIT PC.

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

20. Start WaveStar®.CIT.

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

21. In the WaveStar®.CIT Main Window, choose the option

Administration --> Prepare PCMCIA Disks

Result: The Prepare PCMCIA Disk window appears.

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

22. In the left list, under Available Generics, click the version of

network element software you are installing.

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

23. In the right list, click on the drive letter that represents the

CompactFlash® card.

Result: A WaveStar®.CIT error message is displayed.

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

24. Click on OK.

Important! If the error message window is not closed

automatically after clicking OK then click on the close button (x) in

the upper right corner of the window.

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

25. Click on Copy Generic.

Result: The file copy function starts and you see a Copying files

message.

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


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




26. The “Copying files...” message will disappear when the file transfer

is complete. Click the Close button to exit the Prepare PCMCIA

Disk window.

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

27. If the CompactFlash® card driver software you are using requires

you to stop the CompactFlash® card before ejecting it, stop the card

now. If the software you are using does not allow for this

procedure, make sure that the used slot is not being accessed (the

LED is not blinking) before continuing.

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

28. Eject the CompactFlash® card from the CompactFlash® slot (or

PCMCIA slot with adapter) of the WaveStar®.CIT PC.

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

29. Insert the CompactFlash® card with the new software version into

the CTL circuit pack. Please observe the ESD instruction.

To do this

• insert the CompactFlash® card (red arrow on card down and

facing left)

• close and fix the protecting bar.

Result: The CTL circuit pack is now prepared for insertion

into the system.

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

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






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

NE Software Upgrade 0

To upgrade software to a new release

When to use Use this procedure to upgrade to a new release of the NE software.

This procedure describes a non-traffic-affecting field upgrade of the

1675.LambdaUnite®.MSS software from a former release to Release

11.01.28.

After a software generic has successfully been loaded onto the NE and is

activated with the option TRIAL, it is possible to revert back to the

previous generic together with the restoration of the last matching

database. Upgrading with option TRIAL (and downgrading with

REVERT) is only supported for non-ONNS (traditional) NEs. This

functionality is called Software Downgrade.

Important! A SW upgrade should be performed by trained person-

nel only.


1. Have a valid login on both the WaveStar®.CIT and all subject

NE(s).


NE software.

3. Connect the WaveStar®.CIT locally to the subject NE.

4. Make sure that there is no configuration (write) access to the NE

from other WaveStar®.CITs or management systems during the

software download. During the upgrade procedure, starting with the

database backup until the complete error free start up of the new

release, the following must be avoided:

• provisioning, including provisioning in other parts of the net-

work (e.g. BLSR rings)

• changing cables,

• changing HW,

• replacing defect HW.

5. Make sure that there are no fault situations in DNI/DRI

configurations to avoid unintended protection switches.


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




Prepare CompactFlash®

card for fall back solution

Prepare a CompactFlash® card for a “fall back” solution (in case the NE

software is not successful) with the currently used NE software. Please

refer to the 1675.LambdaUnite®.MSS Installation Guide.

Depending on the application a CompactFlash® card of the following

size has to be used:

• 1-GByte (for applications with CTL/3T or CTL/3S), Comcodes

109558544 or for the new version 109763557.

Important! In case of duplex control, it is also possible to plug out the

standby CTL and use the CompactFlash® card of the standby CTL for

the “fall back” solution. The upgrade will be performed in the simplex

control mode in this case. After successful completion of the upgrade the

second CTL can be inserted again in order to establish the duplex control

mode.

Upgrade-preconditions for

the Network Element

The following preconditions have to be fulfilled by the NE to be

upgraded:

• Prior to an upgrade any alarm OMUNSUP, OMMISMA, OMFAIL

present for ports on GE10PL1 needs to be cleared to avoid potential

permanent traffic loss after the upgrade.

• All alarms on the NE (e.g. alarm list, UPL) are cleared. If it is not

possible to clear all alarms the cause for the remaining alarms must

be fully understood and clear.

• All protection switches (SNCP; MS-SPRING; MSP) should work

in idle/no switch state.

• The ring maps (DCCEI) for all configured MSSPRING/ BLSR

rings are available.

• Protection switches (e.g. equipment protection, traffic protection)

should be avoided during the upgrade.

• Activation of a new SW generic or a newly downloaded DB is only

possible if the NVM of standby the CTL is reliably accessible:

When the NVM (i.e. the CF-disk) of the standby CTL is not reliably

accessible from the active CTL while trying to activate a SW

generic or a database previously downloaded this activation request

is rejected. This behavior is implemented to ensure that such a

standby CTL having a somewhat indefined NVM state cannot take

over in the course of the reset being applied to the active CTL on

SW/DB activation.

If this precondition is not given, then:

- First it should be tried to bring back the standby CTL into a better

state by applying a Full Reset to the standby CTL and waiting

whether it succeeds to start synchronisation.

- If after five minutes the SW/DB activation request is still rejected

then on-site action is necessary.

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






- The standby CTL must be pulled from the system and the SW/DB

activation can be done in simplex mode. Alternatively it can be

tried to bring the standby CTL into a proper state again by replacing

either CF-disk or the complete CTL including the CF-disk.

Upgrade-preconditions for

the whole network

The following preconditions have to be fulfilled by the other

1675.LambdaUnite®.MSS NEs, which are included in the same network:

• A checklist of all NSAP addresses of the 1675.LambdaUnite®.MSS

NEs, to be updated in the network, must exist

• During the upgrade all 1675.LambdaUnite®.MSS NEs in this

network must run the same old NE software version or already the

new NE software.

• It is strongly recommended not to use the new features and

extended features of the new release, until the complete upgrade of

the whole network is achieved.

Possible traffic loss in a Spanning Tree network when rebooting two

GE1 port units in parallel

When resetting in parallel (or shortly after each other) two bridges,

which belong to the same spanning tree, the traffic which is routed

through these two bridges and an adjacent one is likely to be dropped on

the reset of the second bridge until this one is operational again.

However, such a scenario of resetting two bridges in parallel is unlikely

to occur:

• If the bridges are located in different NEs the main reason to reset

both in parallel is a software upgrade within the network. It is

expected that such a software upgrade is done NE by NE, i.e.

upgrading and rebooting one NE before starting with the next one.

• If the bridges are located in the same NE then during a software

upgrade it is very likely that both are reset in parallel. However, the

traffic would only be dropped if it would be routed through both

bridges, i.e. in scenarios where several bridges are cascaded to build

a bigger switch having more LAN and/or WAN ports.


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




Required equipment

The following equipment is required for upgrading the

1675.LambdaUnite®.MSS software from a former release to Release

11.01.28:

• Software for 1675.LambdaUnite®.MSS, Release 11.01.28.

• Software for 1675.LambdaUnite®.MSS, former release (used for

“Fall Back” solution). That means, in accordance with the allowed

upgrade path, exactly the release that comes before the release, to

which the NE should be upgraded.

• An empty CompactFlash® card (the required storage capacity

depends on the used Controller)

Depending on the application:

– a spare 1 GB CompactFlash® card, Comcodes 109558544 or

for the new version 109763557 (for applications with CTL/3T

or CTL/3S)

– and the opposite CompactFlash® adapter.

• a WaveStar®.CIT PC with CompactFlash or PCMCIA slot. For the

second case an adapter is required.

To avoid interworking problems during the upgrade, which starts

with the old release and ends with the new release, the

WaveStar®.CIT shall support both versions.

• 10 Mbit Hub (recommended).

Important! In configuration with 100Mbit LAN cards, sometimes

the transmission link can not be established. For that cases, insert a

10Mbit Hub in the physical link between the PC (with installed

WaveStar®.CIT software) and one of the supported Ethernet LAN

ports of the 1675.LambdaUnite®.MSS (i.e. LAN1 on the User panel

or LAN2 or LAN3 on the CICTL).

The following Hubs are tested with 1675.LambdaUnite®.MSS

– Hewlett Packard J3128A/ Advanced Stack Hub-8E

– Allied Telesyn MR820TR

– Allied Telesyn 3024SL

– Allied Telesyn MR815T

– Allied Telesyn MR415T

• Ethernet LAN cables

Important! Two straight cables are required when using a hub. A

crossover cable is required when connecting directly from

WaveStar®.CIT to the NE.

Instructions Complete the following steps to update the NE with a new software

release.

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






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

1. Upgrade the WaveStar®.CIT software.

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



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

3. Download the software for the new release. Refer to “To perform

an NE software download for upgrade purposes”

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

4. Perform a database backup. Refer to “Manually backup database to

the WaveStar® CIT”

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

5. Activate the SW for the new release. Refer to “To activate an NE

software generic”

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

6. Check if new software generic has been activated. Refer to “To

retrieve NE software generic information”

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

7. Check if the upgrade was successful.

Check the following:

• Remote management access is possible, as before the upgrade.

• No unexpected changes in the alarm states occurred.

Changes in the alarm states may be caused by newly introduced

system functions. Therefore any change in the alarm states need to

be checked thoroughly.

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

8.

IF THEN

the upgrade was successful, The upgrade is complete and the

system works with the new release

SW.

End of Steps

the upgrade was not

successful and the system is

running with the old

software,

End of Steps


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




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

9. The following steps are to be used to perform a fallback to the old

release after an unsuccessful SW upgrade.

In case of duplex control the standby CTL has to be removed before

the active CTL is plugged out.

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

10. Plug out the active CTL and remove the CompactFlash® card.

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

11. Insert the CompactFlash® card (either a new one or the one

removed from LambdaUnite® CTL) into the CompactFlash® slot

(or PCMCIA slot with adapter) of the WaveStar®.CIT PC.

Additional info: If you are using a used CompactFlash® card at

first you have to empty it by using the Windows® Explorer. Do not

format the CompactFlash® card.

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

12. Start WaveStar®.CIT.

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

13. Copy the old release SW stored on the WaveStar®.CIT onto the

CompactFlash® card. In the WaveStar®.CIT Main Window, choose

the option Administration --> Prepare PCMCIA Disks.

Result: The Prepare PCMCIA Disk window appears.

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

14. In the left list, under Available Generics, click the version

(previous SW generic) of network element software you are

installing.

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

15. In the right list, click on the drive letter that represents the

CompactFlash® card.

Result: A WaveStar®.CIT error message is displayed mentioning

that “The device you have selected is not blank”.

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

the upgrade was not

successful and the system is

inoperable (e.g. cyclic

reboot),

perform a fall back to the old release,

proceed with Step 9

IF THEN

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






16. Click on OK.

Important! If the error message window is not closed automati-

cally after clicking OK then click on the close button (x) in the

upper right corner of the window.

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

17. Click on Copy Generic.

Result: The file copy function starts and you see a Copying files

message.

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

18. The “Copying files...” message will disappear when the file transfer

is complete. Click the Close button to exit the Prepare PCMCIA

Disk window.

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

19. If the CompactFlash® card driver software you are using requires

you to stop the CompactFlash® card before ejecting it, stop the card

now. If the software you are using does not allow for this

procedure, make sure that the used slot is not being accessed (the

LED is not blinking) before continuing.

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

20. Eject the CompactFlash® card from the CompactFlash® slot (or

PCMCIA slot with adapter) of the WaveStar®.CIT PC.

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

21. Insert the CompactFlash® card with the old SW and the empty

database into the plugged out CTL.

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

22. Make sure that the CompactFlash® card is firmly seated in the CTL.

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

23. Insert the CTL.

Result: The system starts to activate the old SW generic and comes

up in the maintenance mode.

Note that the CompactFlash® card has to remain in the CTL circuit

pack during normal operation (normal operation comprises the

maintenance mode).

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


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




24. Restore the database backup which was made before the upgrade

via local WaveStar®.CIT (connected via LAN1 of the NE). Refer to

“To restore a database to a network element”.

Result: Fall-Back complete. System up again with old release SW.

Important! The GE1 packs might hang up in recovery and a

Circuit Pack Comm Failure (CPCOMF) alarm might be raised for

those packs.

To bring them back to operation up to two Controller Resets of the

GE1 packs might be necessary.

In Repeater mode traffic is not affected. In switched modes traffic is

affected until the GE1 pack is operational again as protocols like

Spanning Tree Protocol (STP) and Generic Attribute Registration

Protocol VLAN Registration Protocol (GVRP) are not working.

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

25.

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

26. When the system is up again with the old release, delete the content

on the CompactFlash® card of the standby CTL by using the

Windows® Explorer. Do not format the CompactFlash® card.

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

27. Insert the standby CTL, after the first CTL has completely

recovered.

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

IF THEN

a standby CTL (duplex

control) is used,continue with the next steps.

no standby CTL is used, Stop! You have completed this

procedure.

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






To perform an NE software download for upgrade purposes

When to use Use this procedure to download a new version of the NE software

generic. A prerequisite for this is that a software generic (the predecessor

release) is already available in the NE. If this is not the case, please refer

to the task “To perform an initial NE software download”.

Important! This procedure has to be performed for all NEs within

the network.

Download limitations The number of parallel SW downloads from one WaveStar®.CIT is

limited to 5 parallel downloads.

A SWDL will not be possible if the NE in the trial phase (PRESERVED

state)

If a user tries to invoke a SW download from a WaveStar®.CIT while

there are already 5 SW downloads in progress from the same

WaveStar®.CIT, then the CPY-MEM command is denied with the error

code SROF - Status, Requested Operation Failed.

Related information Important! Do not remove or reset the standby (inactive) CTL

while a software download or database restoration is in progress.

Otherwise, the software download or database restoration will be

aborted.

Important! It is not possible to download the R11 SW image, if the

route of the SW download through the DCN involves RS-DCCs.

The SW download will fail with SROF error message. Try to con-

figure the DCN, that only MS-DCCs are used, or perform the SW

download locally via CIT at LAN port.



NE(s).


NE software.

3. Connect the WaveStar®.CIT to the local area network (LAN) of the

subject NE.

Required privilege code

You must have at least a privilege code of S4.


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




Required equipment


• WaveStar®.CIT

Please make sure that you always use the WaveStar®.CIT version

corresponding to the NE release you are upgrading to. If not yet

done, install WaveStar®.CIT on your PC (cf. WaveStar®.CIT

Tutorial).

• For SW download from the WaveStar®.CIT to the system via LAN

connections using a hub the following hubs are recommended:

– Hewlett Packard:

J3128A / Advanced Stack Hub-8E

– Allied Telesyn:

MR820TR

3024SL

MR815T

MR415T

Instructions Complete the following steps to download a new version of the NE

software generic.

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



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

2. Install the NE software on your PC. To do this, use one of the

following two methods (automatic or manual installation).

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

3.

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

4. Insert the LambdaUnite® CD-ROM with the new NE software.

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

IF THEN

You use the automatic

installation methodproceed with the next step.

You use the manual

installation

proceed with Step 11

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






5.

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

6. Click Continue.

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

7. Choose the NE Software entry.

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

8. Click the NE Software button on the right.

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

9. Wait for the software transfer to complete.

NOTE: You will notice that the “Copying files, please wait ...”

message and also the InstallShield Wizard disappears when this

operation has completed.

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

10. Click Exit.

END OF AUTOMATIC INSTALLATION PROCEDURE

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

11. Manual Installation: Insert the 1675.LambdaUnite®.MSS CD-ROM

with the new NE software. If the welcoming screen appears, select

Cancel to exit from the automatic installation procedure.

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

IF THEN

the Welcome Screen

appears,proceed to Step 6.

the Welcome Screen does

not appear,perform the following:

1. Go to the Start button.

2. Click Start with the right mouse

button and select Explore.

3. Select the drive that corresponds to

your CD-ROM.

4. Double click the setup.exe file in

the root directory of your CD-ROM

drive.

5. Proceed to Step 6.


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




12. Open the Windows XP® Explorer on your desktop.

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

13. Select the hard disk drive where WaveStar®.CIT is installed (in

most cases C:) and click through to Program Files --> Alcatel-

Lucent --> WaveStar CIT --> generics.

Please note that if the subdirectory generics does not exist, you

must create it!

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

14. In the generics directory, create a new folder, preferably stating the

new software version in its name.

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

15. In the Windows XP® Explorer, right-click the CD-ROM drive of

your computer and select Explore. Go to the generics directory.

This directory contains two subdirectories: p and up.

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

16. Select the complete up and p directories and copy it to the folder

you created in Step 14.

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

17. To install Acrobat Reader on your system, go to the Acrobat Reader

subdirectory on your CD-ROM drive and double-click the

AcrobatReader.exe file.

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

18. The Software Release Description (SRD) is located in the

Documentation subdirectory of the CD. You can read it by double

clicking the .pdf file in this subdirectory.

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

19. Log into the WaveStar®.CIT.

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

20. At the WaveStar®.CIT, connect to the network element.

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

21. From the WaveStar®.CIT System View, select the Configuration

--> Software --> Download Software menu option.

Result: The Download Generic window appears.

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

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






22. According on how the NE is connected to the WaveStar®.CIT

select the responding option in the Download From/Via drop

down list box

23. Click the Download push-button.

Result: The software download is started.

In case of successful starting, a progress indicator window appears.

The NE will be provisionable during this generic download is in

process.

IF THEN

the WaveStar®.CIT is

connected to the NE via

DCC or OSI LAN

in the Download From/Via drop

down list box select CIT

A file selection screen appears

showing that the software will

downloaded from Program Files -->

Alcatel-Lucent --> WaveStar CIT --

> generics or Program Files -->

Lucent Technologies --> WaveStar

CIT --> generics. The directory of

the file selection screen is

automatically pre-populated.

In the file selection window, double

click the version of network element

software you are upgrading to (i.e. if

manual installation has been done, the

name of the folder you created in Step

14), double click the p directory.

the WaveStar®.CIT is

connected to the NE via

TCP/IP

in the Download From/Via drop

down list box select FTTD.

Enter the required parameters.

Specify the Source directory path as

follows:

generics/Wavestar_UNITE/<version

of network element software>/p.

the download of the software

generic shall be performed

using FTAM,

n the Download From/Via drop

down list box select FTAM.

Enter the required parameters.

Specify the Source directory path.


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




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

24. Important! TCP/IP connections are aborted automatically after 60

minutes of inactivity (an “inactive TCP/IP connection” is a TCP/IP

connection over which no TL1 messages are transmitted in either

direction).

To avoid the behavior described before during the current software

download, if the WaveStar®.CIT is connected to the NE via a

TCP/IP, perform an action like clicking on the Update Alarms but-

ton in the system view. This causes TL1 messages (RTRV-ALM-

ALL, RTRV-ALM-ENV) to be sent to the NE.

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

25. To check whether the download was successful, select View -->

Software Generic --> All Info from the NE System View menu

bar.

Result Two loads are displayed: Previous and Current.

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

26.

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

IF THEN

the download was

successful,Nothing to do.

Result: The new software generic is

now available in the “PREVIOUS”

area of the NE’s non-volatile memory

(NVM). It is not yet activated.

Reference: For activating the new

software, please refer to the task “To

activate an NE software generic”.

the download was

interrupted,Wait for about 10 minutes.

After 10 minutes the NE has

recovered from the last action and a

new download can be executed

Reference: Continue with Step 20.

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






To activate an NE software generic

When to use Use this procedure to activate a downloaded new version of an NE

software generic.

Important! Observe the following important details:

Duplex control Activation of a new SW generic or a

newly downloaded DB is only possible if

the NVM of the standby CTL is reliably

accessible: When the NVM (i.e. the CF-

disk) of the standby CTL is not reliably

accessible from the active CTL while

trying to activate a SW generic or a

database previously downloaded this

activation request is rejected. This

behavior is implemented to ensure that

such a standby CTL having a somewhat

indefined NVM state cannot take over in

the course of the reset being applied to the

active CTL on SW/DB activation.

If this precondition is not given, then:

- First it should be tried to bring back the

standby CTL into a better state by applying

a Full Reset to the standby CTL and

waiting whether it succeeds to start

synchronisation.

- If after five minutes the SW/DB

activation request is still rejected then on-

site action is necessary.

- The standby CTL must be pulled from

the system and the SW/DB activation can

be done in simplex mode. Alternatively it

can be tried to bring the standby CTL into

a proper state again by replacing either CF-

disk or the complete CTL including the

CF-disk.


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






NE(s) within the ring.


subject NE/ring.

3. Have performed a software download to the non-volatile memory

of the NE before.



Required equipment


• WaveStar®.CIT

Instructions Complete the following steps to activate/install a new/other version of

the NE software generic.

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


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

Software downgrade Only supported for non ONNS NEs and

PRESERVED state.

After a software generic has successfully

been loaded onto the NE it is possible to

revert back to the previous generic

together with the restoration of the last

matching database. This functionality is

called Software Downgrade. Therefore,

the system provides in addition an

alternative function to activate the new

generic with the option that an operator

may revert back to the previous generic

together with the restoration of the last

matching database.

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






2. At the WaveStar®.CIT, connect to the network element where you

want to activate the software currently located in the “PREVIOUS”

area of the non-volatile memory (NVM). The previous software

store should have the state DOWNLOADED (refer to “To retrieve

NE software generic information”.

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

3. If STM-1 electrical interfaces in combination with 1+1 protecting

paddle boards are present in the NE execute a forced switch to the

active STM-1e pack to avoid a short traffic interruption

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

4. In the WaveStar®.CIT System View, select the menu option

Configuration --> Software --> Activate Software.

Result: The Software Generic Install window appears. The win-

dow shows the currently inactive software generic in the “PREVI-

OUS” area of the non-volatile memory. Select the generic in the

list.

The group box Available Generics show the data of the PREVI-

OUS Generics.

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

5. Using the group box Switch type you can select which type of SW

switch to perform

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

6. Click OK.

Result: A confirmation window appears.

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

7. If you are sure you want to activate the software, confirm by

clicking Yes.

Result: Several non traffic affecting system resets will be initiated

and communication to the NE will be lost during that time. During

the NE software upgrade, also a secondary boot upgrade take place.

IF YOU WANT TO THEN SELECT

install a downloaded SW

generic, Install

cause the downloaded

software to be installed in a

trial phase,

Trial

Only supported for non ONNS NEs.

During the trial phase, it is possible to

switch back to the previously

installed software and database. Prior

to installation, the software state must

be equal to DOWNLOADED.


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




This process might need about 1 hour.

Important! The resulting reboot of the GE10PL1 is not hitless

under all circumstances. Instead a traffic loss in the range of sec-

onds is observed. For details see the upg, Procedure 4-28 part "Pro-

visioning a VCG port for private line applications".

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

8.

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

9. In the WaveStar®.CIT System View, select the menu option

Configuration --> Software --> Activate Software.

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

10. Using the group box Switch type you can select which type of SW

switch to perform

IF YOU THEN

installed software in normal

mode (SW switch type:

Install).

the procedure is ended!

installed software in trial

mode, and don’t want to

terminate the trial phase,

the procedure is ended!

installed software in trial

mode, and want to terminate

the trial phase,

continue with the next step.

IF YOU WANT TO THEN SELECT

terminate the trial phase of a

newly installed software.

Commit


When the trial phase is terminated, a

switch back to the previously

installed software and database is no

longer possible. The termination of

the trial phase is allowed with the

PRESERVED state of the previous

SW generic and the previous

database.

force the system to switch

back to the previously

installed software and

database, during trial phase,

Revert


Revert is only allowed if the NE is in

the PRESERVED state.

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






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

11. Click OK.

Result: A confirmation window appears.

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


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




12. If you are sure you want to activate the software, confirm by

clicking Yes.

Result: Several non traffic affecting system resets will be initiated

and communication to the NE will be lost during that time. During

the NE software upgrade, also a secondary boot upgrade take place.

This process might need about 1 hour.

Important! The resulting reboot of the GE10PL1 is not hitless

under all circumstances. Instead a traffic loss in the range of sec-

onds is observed. For details see the UPG, chapter 4.

Important! When upgrading a LambdaUnite node equipped with

GE1 packs using the trial mechanism and falling back to the old

release, the GE1 packs might hang up in recovery and a Circuit

Pack Comm Failure (CPCOMF) alarm might be raised for those

packs.







For details see the MTCG, chapter 3.

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

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






To check for successful NE software upgrade

When to use Use this procedure to check if NE software upgrade to new release was

successful.



NE(s) within the ring.


subject NE/ring.

Required equipment


• WaveStar®.CIT

Instructions Complete the following steps to check the software upgrade to new

release was successful.

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


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

2. Check if traffic is working properly.

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

3. Check if the system is working in normal mode.

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

4. Check if the NE is running in Release 11.01.28 (The current version

is mentioned in the title bar of the System View window).

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

5. Check if there are no new unexpected alarms on the shelf.

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

6. Check if synchronization is locked to the correct timing source.

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

7. Check if no protection switches took place.

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

8. Verify the LED status on the front of the packs (CTL(s), XCs, OPs,

EPs).

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

9. Verify the date and time of the NE and correct it if necessary..


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




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

10. If STM-1 electrical interfaces in combination with 1+1 protecting

paddle boards are present in the NE, clear the forced switch to the

active STM-1e pack (the forced switch to the active STM-1e pack

has been executed during execution of the “To activate an NE

software generic”).

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

11. It is recommended to perform a first database backup of all

successfully upgraded NE(s) now, since all former backups can not

be restored in Release 11.01.28.

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

E N D O F S T E P S

To solve NE software upgrade problems

When to use Use this procedure to solve NE software upgrade problems.

Instructions ..................................................................................................................

1. If a Circuit Pack Comm Failure (CPCOMF) alarm is raised for a

circuit pack after software activation, then please refer to the

1675.LambdaUnite®.MSS Alarm Messages and Trouble Clearing

Guide for the respective trouble clearing procedure. Traffic is not

affected.

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

2. If the NE shows strange behavior after software activation (for

example: login to NE not possible), then proceed as follows,

depending on the shown NE behavior after software activation:

Current NE behavior Trouble

shooting

Resulting NE behavior

A NE in simplex control:

• Login to NE not

possible

• No traffic lost

• Green activity LED on

the CTL is still flashing

1 hour after software

activation.

Please refer to

“Trouble

shooting

procedure A”.

Login to NE is possible

again (in case of no

success, refer to

“Trouble shooting

procedure E”).

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






Trouble shooting

procedure A


B NE in duplex control:

• Login to NE possible

• No traffic lost

• Green activity LED on

one CTL is still

flashing 1 hour after

software activation.

Operational status is

disabled and Circuit

Pack Failure alarm

raised for one CTL.

Please refer to

“Trouble

shooting

procedure B”.

Duplex control is

established properly

(green LED on one CTL

is lit, and LEDs on

second CTL are off, 1

hour after software

activation at the latest).

C NE in duplex control:

• Login to NE not

possible

• No traffic lost

• Green activity LEDs on

both CTLs are still

flashing 1 hour after


Please refer to

“Trouble

shooting

procedure C”

(. 10-31).

Duplex control is


(green LED on one

CTL is lit, and LEDs

on second CTL are off,



D NE in duplex control:

• No traffic lost

• Red fault LED on one

CTL is lit 1 hour after


Please refer to

“Trouble

shooting

procedure D”.

Duplex control is


(green LED on one CTL

is lit, and LEDs on

second CTL are off,



E NE in simplex or duplex

control:

• Login to NE not

possible

• Traffic lost

Please refer to

“Trouble

shooting

procedure E”.

NE software will be

restored to the previous

NE software version.

Current NE behavior Trouble

shooting

Resulting NE behavior


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




Hold circuit packs only at the edges or on the insertion and removal

facilities. Always observe the ESD instructions.

Proceed as follows:

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

1. Open the latches of the CTL.

Important! Do not immediately remove the CTL from its slot at

that time.

The green activity LED on the faceplate of the CTL starts flashing.

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

2. Wait until the green activity LED has stopped flashing (about five

seconds).

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

3. Remove the CTL from its slot.

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

4. Reinsert the CTL in the CTL worker slot (slot 11) and wait until the

green activity LED is permanently lit.

Removing and reinserting the CTL is equivalent to a full reset of

the CTL.

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

5. Try to login again.

Result: Login should now be possible again. Otherwise, please

refer to “Trouble shooting procedure E”.

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

6. Check the status of the 1675.LambdaUnite®.MSS system, as

described in “To check for successful NE software upgrade”.

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

Trouble shooting

procedure B

Proceed as follows:

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

1. Login to the 1675.LambdaUnite®.MSS NE, using the

WaveStar®.CIT.

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

2. Perform a controller reset to the standby CTL.

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

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






3. Wait until the Operational Status of the standby CTL is Enabled

and the green activity LED stops flashing (is switched off).

The Operational Status can be retrieved via:

• the WaveStar®.CIT System View main menu: View --> View

Equipment Details (select the standby CTL) --> Status tab,

or

• the context menu (right-click popup menu) of the standby

CTL: View Circuit Pack Details --> Status tab.

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



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

Trouble shooting

procedure C




Proceed as follows:

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

1. Open the latches of the CTL in the protection slot (slot 31).


that time.

The green activity LED on the faceplate of the CTL starts flashing.

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


seconds).

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


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

4. Repeat Step 1 to Step 3 for the CTL in the worker slot (slot 11).

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

5. Reinsert the CTL in the CTL worker slot (slot 11) and wait until the

green activity LED is permanently lit.


the CTL.


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




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

6. Try to login again.

Result: Login should now be possible again. Otherwise, please

refer to “Trouble shooting procedure E”.

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

7. Reinsert the CTL in the CTL protection slot (slot 31) and wait until

the green activity LED is permanently lit.


the CTL.

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

8. Wait until the Operational Status of the CTL in the CTL

protection slot is Enabled, and the green activity LED stops

flashing (is switched off).



Equipment Details (select the CTL in the protection slot) -->

Status tab, or

• the context menu (right-click popup menu) of the CTL in the

protection slot: View Circuit Pack Details --> Status tab.

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



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

Trouble shooting

procedure D




Proceed as follows:

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

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






1.

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

2. Perform a controller reset of the standby CTL.

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

3. Wait until the Operational Status of the standby CTL is Enabled,





Status tab, or



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

4. Perform a full reset of the standby CTL.

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

IF THEN

login to the NE is possible, login to the

1675.LambdaUnite®.MSS NE, using

the WaveStar®.CIT, and then


login to the NE is not

possible

continue with Step 6.

IF THEN

the Operational Status of

the standby CTL is

Enabled, and the green

activity LED is switched off

after 1 hour at the latest,



the standby CTL is still is

Disabled after 1 hour,



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




5. Wait until the Operational Status of the standby CTL is Enabled,





Status tab, or



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

6. Remove the CTL, where the red LED is lit, from its slot.

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

7. Reinsert the CTL.

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

8. Wait until the Operational Status of the just reinserted CTL is

Enabled, and the green activity LED stops flashing (is switched

off).



Equipment Details (select the just reinserted CTL) --> Status tab,

or

• the context menu (right-click popup menu) of the just reinserted

CTL: View Circuit Pack Details --> Status tab.

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



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

IF THEN


the standby CTL is

Enabled, and the green

activity LED is switched off

after 1 hour at the latest,



the standby CTL is still is

Disabled after 1 hour,


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






Trouble shooting

procedure E




Proceed as follows to restore the NE software to the previous NE

software version:

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

1. Open the latches of the CTL in the worker slot (slot 11).


that time. The green activity LED on the faceplate of the CTL starts

flashing.

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


seconds).

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


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

4. If necessary, repeat Step 1 to Step 3 for the CTL in the protection

slot (slot 31).

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

5. Insert the prepared CompactFlash® card (with the “old” NE

software and empty database) in the working CTL, and reinsert the

CTL in the CTL worker slot (slot 11).

Reference: “Prepare CompactFlash® card for fall back solution”.

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


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




6. After the system boot has finished, login into the system with the

following default settings:

• NE-Name: UNITE-NE.

• User-Login: LUC01 (or LUC02)

• Password-Login: UNITE+01 (or UNITE+02)

Result: A password change is requested.

Important! The system is coming up in the maintenance mode. Do

not leave the maintenance mode at this state. Otherwise, all

traffic will be lost!

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

7. Using the WaveStar®.CIT, start the database restore process of the

NE.

Make sure to select the correct directory of the database to be

restored (the location of the backup folder was recorded during the

preparation of the upgrade (cf. “To upgrade software to a new

release”, Step 3: database backup).

Reference: Please also refer to:

• “Manually backup database to the WaveStar®.CIT”

• “To restore a database to a network element”

Result: In case of successful starting, a progress indicator window

appears. After finishing of database restore to the NE, an automatic

reset of the NE takes place. As a consequence, the connection to the

NE will be lost for some minutes.

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

8. Wait until the system reboot has finished.

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

9. Login to the NE again using the login parameters (NE-Name, User-

Login, Password-Login), that were used before the upgrade was

started.

Important! The GE1 packs might hang up in recovery and a Cir-

cuit Pack Comm Failure (CPCOMF) alarm might be raised for

those packs.







For details see the MTCG, chapter 3.

If applicable, and if no second upgrade trial is planned, delete all

files of the CompactFlash® card of the protection CTL and reinsert

the CTL in the CTL protection slot again. Wait until the operational

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






status of the CTL in the CTL protection slot is enabled (see System

View main menu, select View --> View Equipment Details, or

context menu of the protection CTL (right mouse button), select

View Circuit Pack Details) and the green activity LED stops flash-

ing (is switched off).

Important! If a second upgrade trial is planned, then leave out the

protecting CTL to avoid unnecessary CTL synchronization time.

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



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

E N D O F S T E P S

To retrieve NE software generic information

When to use Using the WaveStar®.CIT you can retrieve the current software version

ID. Software updates, or patches, are identified and included in the

current version, if appropriate.

NE active software The About NE window which displays the currently active NE software

version in the form explained above, is invoked by selecting Help -->

About This Network Element from the NE System View menu bar.

Instructions To invoke the CIT/NE Software display window proceed as follows.

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

1. Select View --> Software Generic from the NE System View menu

bar.

Result: A file selection window is displayed.

Additional info With this invocation of the file selection screen,

only NE software type files stored on the CIT or on the NE are

selectable.

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

2. Select a file or files or directory.

Reference: The displayed parameters are described in “Supporting

information for “Retrieving NE software generic information””.

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

E N D O F S T E P S


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




Supporting information for “Retrieving NE software generic information”

NE software display

window

WaveStar®.CIT allows the user to view the current status of the various

copies and releases of the NE software as they reside on the NE non-

volatile memory (NVM). The display includes the currently active

release and may include either the previous release or a newly

downloaded release which is not yet be applied.

Elements of the NE

software display window

Important! On the CompactFlash® card, there is room for two

databases, the current and the previous one. If a CompactFlash®

card never contained a second database, the content of the previous

partition is reported wrongly: the allocated size parameter for the

previous database is missing (“size=0”) and a serial number for that

non-existing database is reported.

The following information is displayed in the window for each file

selected by the user:

.

______________________________________________________________OBJECT DESCRIPTION/BEHAVIOR

Current generic the software release which is currently active for

the WaveStar®.CIT or network element.

NVM Selected file. If resident on the NE, the file

description indicates whether the file is

• Current,

• Previous, or

• Secondary

Otherwise it gives the directory tree and name of

the specific file.

NE Type Product type of alphanumeric characters

Release Software release, for example: 07.00.00.

Supplier Name of the supplier, currently Lucent.

Delivered Date and end time the software release was

downloaded onto the NE, if this is an NE file, or the

date and time the file was last modified if the file is

not on the NE.

Installed Date and start time the software release was

installed (activated) onto the NE. If this release has

not yet been applied, this field is empty.

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






Size Size of the software in bytes.

Possible values are integers from 0...999,999,999,

inclusive.

Source Source of the original download. Examples at this

time include CIT, EMS and FTTD along with a

file path and file name. If the source system is

either CIT, EMS or FTTD and if the file is on the

NE, the field additionally includes the psel, ssel,

tsel, and NSAP values for those systems:

• CIT,psel,ssel,tsel,nsap,filename

• EMS,psel,ssel,tsel,nsap,filename

• PRE-LOADED

The fields psel, ssel, tsel, nsap specify the GNE,

ranges are

• psel (path selector): 0-4 bytes represented as

0-8 hex characters,

• ssel (session selector): 0-4 bytes represented

as 0-8 hex characters,

• tsel (transport selector): 0-16 bytes

represented as 0-32 hex characters,

• nsap: 20 bytes represented as 40 hex

characters.

State State of this software release. It may take the

values:

• Corrupt

• Downloaded

• In Progress

• Failed

• Previous

• Running

• Initial.

• Preserved (for SW Downgrade during trial

phase)

Free NVM Space n/a (not applicable)

Unavailable NVM

Space

n/a (not applicable)



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




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

Database backup 0

Overview

Purpose This chapter describes the procedure which has to be carried out for a

NE database backup of the 1675.LambdaUnite®.MSS. Furthermore, the

procedure for retrieving information on the current NE database is

provided.

To limit the number of saved backups

Purpose Use this procedure to specify the maximum number of backup

directories to be saved.

Before you begin Before you begin this task:

• Obtain the work instructions for this task.

• Verify that a WaveStar®.CIT is connected and logged into the

1675.LambdaUnite®.MSS system.

Required equipment

The following equipment is required to perform this task.

• WaveStar® Customer Interface Terminal (WaveStar®.CIT)

Instructions Complete the following steps to manually backup the network element

database (current program and data) to the WaveStar®.CIT.

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

1. At the WaveStar®.CIT, select Configuration --> Software -->

Remote Backup.

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

2. In the Backup Database window select Setup.

Result: The Provision Backup Number screen appears.

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

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






3. In the Provision Backup Number screen specify the maximum

number of backups to CIT per system.

Additional info: The parameter can be set to a number from 1 to

10, or it can be set to infinite by clicking the radio button Infinite.

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

4. Click on OK.

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

E N D O F S T E P S


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




Manually backup database to the WaveStar® CIT

When to use Use this procedure to manually backup the network element database

(current program and data) to the WaveStar® Customer Interface

Terminal (WaveStar®.CIT):

• after initial software installations/upgrades/changes

• after major provisioning data changes

• periodically according to local policy

• before software upgrades/changes

• before major provisioning data changes

Safety precautions To assure both personal safety and the proper functioning of the

1675.LambdaUnite®.MSS system, it is imperative to review and

understand these warnings and precautions prior to performing this task.

Related information For related information, see:

• 1675.LambdaUnite®.MSS User Operations Guide, “Database

backup concepts”

• 1675.LambdaUnite®.MSS Alarm Messages and Trouble Clearing

Guide, “Manually Restore Database from the WaveStar®.CIT to an

NE”


• Obtain the work instructions for this task.

• Verify that a WaveStar®.CIT is connected and logged into the

1675.LambdaUnite®.MSS system.

• Ensure that no other user is remotely logged in (to the NE) and do

not perform any provisioning activities on the NE while the

database backup is running. Also ensure that no auto-/de-

provisioning activities (plug in/plug out of packs) are performed on

the NE while the database backup is running.

Required equipment



• For connecting the WaveStar®.CIT to the system via LAN




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






– Allied Telesyn:

MR820TR

3024SL

MR815T

MR415T

Instructions Complete the following steps to manually backup the network element

database (current program and data) to the WaveStar®.CIT.

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

1. At the WaveStar®.CIT, select Configuration --> Software -->

Remote Backup.

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

2.

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

3. In the FTAM tab specify the TID, PSEL, SSEL, TSEL and NSAP

for the FTAM information.

Reference: Continue with step Step 6.

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

______________________________________________________________IF THEN

you want to backup the

database via FTAM,

in the Backup To/Via drop down list

box select FTAM.


the connection to the NE is

through a TCP/IP

Gateway,


box select FTTD.


you want to backup the

database directly to the

CIT,


box select CIT.

Result: A file selection screen appears

showing that the database will back up

to a specified folder under C:\Program

Files\Alcatel-Lucent\Wavestar

CIT\....or C:\Program Files\Lucent

Technologies\Wavestar CIT\.... The

directory of the file selection screen is




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




4. In the FTTD tab specify the TID, PSEL, SSEL, TSEL and NSAP

for the FTTD information.

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

5. In the FTP tab specify the Server, IP or Name, Port (optional), User

Name (optional) and User Password (optional) for FTP information

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

6. Specify the Destination directory path.

Additional info: If you backup with FTP or FTTD feature you can

write backups into any directory you want.

When making a backup the directory structure must be compliant

with the directory structure which is used when making a backup

via CIT.

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

7. Record the path/destination of the backup folder/files and click on

Backup.

Result: The NE Data Progress Indicator Screen appears.

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

8. Important! TCP/IP connections are aborted automatically after 60

minutes of inactivity (an “inactive TCP connection” is a TCP

connection over which no TL1 messages are transmitted in either

direction).

To avoid this behavior during the current action, perform an action

like clicking on the Update Alarms button in the system view

which causes TL1 messages (RTRV-ALM-ALL, RTRV-ALM-

ENV) to be sent to the NE.

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

9. If the backup went wrong for any reason the following screen is

displayed stating:

The backup went wrong.

Do you want to delete the backup directory:

<path of the backup directory>

You have decide either to delete or not to delete the backup direc-

tory, and either to click Yes or No.

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

10. Important! If the current action has been interrupted. Wait for

about 10 minutes. After 10 Minutes the NE has recovered from the

last action and a new download/restore/backup can be executed.

When the NE Data Backup in Progress screen disappears and the

backup is complete, select View --> NE Data...

Result: The File Selection Screen appears.

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






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

11. Select CIT in the Look in: field and double click on C:, Program

Files, Alcatel-Lucent or Lucent Technologies, WaveStar®.CIT, and

Backups. Then click on the backup folder number and on OK.

Result: The Database Info Screen appears.

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

12. Verify the Last Backup Time and Last Backup Destination

parameters and click on Close.

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

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


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




To retrieve NE database information

When to use Via the WaveStar®.CIT you can retrieve the NE Backup status as

reported by the NE as well as showing the release number of NE Data

backup files resident on the CIT.

Instructions To invoke the Database Info window proceed as follows.

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

1. Select View --> NE Data from the System View menu bar.

Result: A file selection window is displayed.

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

2. Select a file or files or directory.

Reference: The displayed parameters are described in “Supporting

information for Retrieving NE database information”.

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

E N D O F S T E P S

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






Supporting information for Retrieving NE database information

Elements of the Database

Info window

The Database Info window consists of two tabs, Remote and Local.

These two tabs show the following information for the file(s) selected by

the user:

.


Current generic the software release which is currently active for

the WaveStar®.CIT or network element.

NVM Selected file. If resident on the NE, the file

description indicates whether the file is

• Current,

• Previous, or

• Secondary

Otherwise it gives the directory tree and name of

the specific file.

TID TID of the NE from which the configuration data

was stored on this NVM.

Serial Number Serial number

Software Release Software release corresponding to the data.

Size Size of the file in bytes.

Possible values:

• integers ranging from 0 to 999,999,999

inclusive.

State State of this data. It may take the values:

• Backup

• Corrupt

• Downloaded

• Failed

• Initial

• In Progress

• Previous

• Running.

• Preserved (for SW Downgrade during trial

phase)


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




Last/Previous

Backup Time

Date and time when the data was backed up from

the NE. If there has been no backup, this field is

blank.

Last/Previous

Backup Location

Destination of the most recent backup. Examples

at this time include FTTD, EMS, and CIT and a

file name/path. If there has been no backup, this

field is blank.

Last/Previous

Backup Time

Date and time when the data was restored to the

NE. If there has been no restoral, this field is blank.

This field only applies to files on the NE.

Last/Previous

Backup Source

Source of the most recent restore. Examples at this

time include EMS, WaveStar®.CIT and FTTD

plus a file name/path. If there has been no restoral,

this field is blank.


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






To restore a database to a network element

Purpose Use this procedure to restore a previously saved database to a network

element.

Important! A restore of a database will not be possible if the NE is

in the trial phase (PRESERVED state).

Safety precautions To assure both personal safety and the proper functioning of the

1675.LambdaUnite®.MSS system, it is imperative to review and

understand these warnings and precautions prior to performing this task.

Important! If provisioning changes were made after the last

backup files were created, use the appropriate WaveStar®.CIT com-

mands to manually apply the recent provisioning changes to the

just-restored database.

Do not remove or reset the standby (inactive) CTL while a software

download or database restoration is in progress. Otherwise, the soft-

ware download or database restoration will be aborted.


• Obtain the work instructions for this task and note the database to

be restored and the location of the most recent backup files.

• Verify that a WaveStar®.CIT is connected and logged in to the

1675.LambdaUnite®.MSS network element (NE) where the

database is to be restored.

• You have to log in as one of the two predefined super user logins.



Required equipment



• For connecting the WaveStar®.CIT to the system via LAN




– Allied Telesyn:

MR820TR

3024SL

MR815T

MR415T


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




Instructions Complete the following steps to manually restore a database to a

network element:

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

1. From the System View main menu, enter the maintenance

condition via Fault --> Enter/Exit Maintenance Condition... -->

Enter Maintenance Condition...

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

2. Confirm the resulting system message by clicking OK.

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

3. Select Configuration --> Software --> Remote Restore... from

the System View main menu.

Result: The Restore Database window will be opened.

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

4. Proceed as follows:

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

5. Select “CIT” in the Look in field and double click successively on

C:, Program Files, Alcatel-Lucent or Lucent Technologies,

Wavestar CIT, and backups.

Proceed Step 8.

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

______________________________________________________________IF THEN

you want to restore the

database directly from the

PC where the

WaveStar®.CIT is

installed,

select CIT in the Restore From/Via

drop down list box.

Result: A file selection screen appears

showing that the database will back up

to a specified folder under C:\Program

Files\Alcatel-Lucent\Wavestar CIT\....

or C:\Program Files\Lucent

Technologies\Wavestar CIT\.... The

directory of the file selection screen is


Reference: Proceed with Step 5.

the connection to the NE is

through a TCP/IP gateway,

select FTTD in the Restore

From/Via drop down list box.

Reference: Proceed with Step 6.

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






6. Select the FTTD tab and specify the TID, presentation selector

(Psel), session selector (Ssel), transport selector (Tsel) and the

NSAP Address for the FTTD information.

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

7. Select the FTP tab and specify the Server (IP address or server

name), port information (optional), User name (optional) and

password (optional) for the FTP information.

Proceed with Step 8.

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

8. Important! Be careful to select the correct backup files to restore

to the NE. Specify the path to the folder where the backup files

reside.

Important! The NE does not restore a backup file properly if the

release number of the backup file is not the same as the release

number of the running SW.

Restoring a backup file with a different release number

Restoring a backup file with a different release number is quite

dangerous for the consistency of the database and the configuration

of the system and should therefore only be performed in emergency

cases by trained personal.

To restore a backup file with a different release number as the run-

ning software you have to perform the following:

• open the file named db (in the WaveStar®.CIT) in the directory

where the backuped information (list of files) are stored, using

a text editor

• in this file change the release number of the backup file to the

release number of the running SW.

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

9. Verify your settings and correct if necessary. Then click Restore.

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


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




10. Confirm the resulting system message by clicking YES.

Important! TCP/IP connections are aborted automatically after 60

minutes of inactivity (an “inactive TCP connection” is a TCP con-

nection over which no TL1 messages are transmitted in either direc-

tion).

To avoid this behavior during the current action, perform an action

like clicking on the Update Alarms button in the system view

which causes TL1 messages (RTRV-ALM-ALL, RTRV-ALM-

ENV) to be sent to the NE.

Result: The NE Data Restore in Progress window appears. When

the database restore is complete, the system will perform a reset. As

a consequence, the management association between the Wave-

Star®.CIT and the NE will be lost. After the system reset has fin-

ished, you can re-establish the management association by again

connecting the WaveStar®.CIT to the NE.

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

11. If the current action has been interrupted. Wait for about 10

minutes. After 10 minutes the NE has recovered from the last action

and a new download/restore/backup can be executed.

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

12. Connect to the NE again.

Result: The NE comes up in maintenance mode if during startup a

data base with a not matching serial number is detected. However,

if the original data base (with matching serial number) is restored,

the NE does not come up in maintenance mode.

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

13.

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

14. From the System View main menu, select Fault --> Enter/Exit

Maintenance Condition... --> Exit Maintenance Condition...

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

15. Confirm the resulting system message by clicking OK.

Additional info: The 1675.LambdaUnite®.MSS NE will now per-

form a system reset. As a consequence, the management association

between the WaveStar®.CIT and the NE will be lost. After the sys-

______________________________________________________________IF THEN

the NE comes up in

maintenance mode,


the NE does not come up in

maintenance mode,

the procedure is ended.

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






tem reset has finished, you can re-establish the management associ-

ation by again connecting the WaveStar®.CIT to the NE.

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

E N D O F S T E P S




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

5 Miscellaneous

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

Contents 0

Supported NE Releases with WaveStar®.CIT 5 - 2

1675.LambdaUnite®.MSS 5 - 2

Other NE Types 5 - 2

Technical Support (TSC/TEC) 5 - 3

Technical Support Groups 5 - 3

Contacting Your Local/Regional TSC 5 - 3

Product Support 5 - 3

Services 5 - 3

Technical Support Platform 5 - 3

Reference 5 - 4

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

Miscellaneous





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

Supported NE Releases with WaveStar®.CIT 0

1675.LambdaUnite®

.MSS The traditional part of WaveStar®.CIT Software Release.18.09.05

Build.50xy supports 1675.LambdaUnite®.MSS

• Release.11.1.11

• Release 11.01.26

• Release 11.01.27

• Release 11.01.28

.

Other NE Types Please refer to file ’release.txt’ in the folder ’cit’ of the CD for

information on the support of other network elements and their releases

by WaveStar®.CIT Software Release.18.09.05 Build.50xy.

Miscellaneous

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




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

Technical Support (TSC/TEC) 0

Technical Support Groups Technical support is available through:

• Local/Regional TSC

• OND Support TEC (Technical Excellence Center Nuremberg)

Contacting Your

Local/Regional TSC

Local/Regional Technical Support Centers (TSC) 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 Customer Support

Team. If the request cannot be solved by Local/Regional TSC, it will be

escalated to the TEC team who maintain direct contact with Alcatel-

lucent manufacturing, Research & Development, and other organizations

to assure fast resolution of all assistance requests.

Product Support The Alcatel-Lucent OND TEC (Nuremberg, Germany) organization is

committed to providing customers with quality product support

sercvices. Each segment of the Technical Support organization regards

the customer as its highest priority and understands your obligations to

maintain quality sercvices for your customers.

Services Alcatel Lucent 1675 LambdaUnite MSS is complemented by a full range

of services available to support planning, maintaining, and operating

your system. Application testing, network integration, and

upgrade/conversion support is also available.

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

for north and south

America (NAR and

CALA)

Customer Technical Assistance Management (CTAM):

• +1 866 Lucent8 (prompt#1)

• +1 630 224 4672 (from outside the United States)

for Europe, Africa, Asia

and the pacific region

(EMEA and APAC)

International Customer Management Centre (ICMC):

• +353 1 692 4579 (toll number)

• 00 800 00Lucent (toll free number in most EMEA

countries)

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

Miscellaneous





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 Center or visit

http://www.alcatel-lucent.com/wps/portal/support.

1675 LambdaUnite® MultiService Switch (MSS), Release ...

Documents

Transcript of 1675 LambdaUnite® MultiService Switch (MSS), Release ...