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

Lucent Technologies - ProprietaryThis document contains proprietary information of

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

Copyright © 2007 Lucent TechnologiesUnpublished and Not for Publication

All Rights Reserved

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

Network Element (NE) Software Version 08.00.20

Craft Interface Terminal (CIT) Software Release.16.02.00, Build.1445

Issue 1.1March 2007

Lucent Technologies - ProprietarySee Notice on first page

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

Support

Technical support

Please contact your Lucent Technologies Local Customer Support Team (LCS) for technical questions about the information in this document.

LambdaURelease.8DescriptiIssue 1.1

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

Contents

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

A About this Document

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

1 New Features

Overview 1 - 2

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

1a New Features of Release.8.0

Circuit Packs 1a - 2

Software Features 1a - 3

ONNS Feature Enhancements 1a - 4

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

1b New Features of Release.8.0.1

Circuit Packs 1b - 2

Software Features 1b - 2

ONNS Features Deferred to a Future Release 1b - 3

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

1c New Features of Release.8.0.20

Software Features 1c - 2

ONNS Features Deferred to a Future Release 1c - 2

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

2 Fixed Problems

Introduction 2 - 3

Fixed Problems in Release.8.0.20 2 - 4


Fixed Problems in Release.8.0 2 - 18

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

3 Known Problems

Introduction 3 - 2

Known Problems 3 - 3

C O N T E N T Si i i


nite® MultiService Switch (MSS), .0.20 Software Release

on, March 2007

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

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

4 New Installation and Upgrade Procedures

General 4 - 4

Upgrade path survey 4 - 6

New Installation and Software Upgrade 4 - 7

Overview 4 - 7

To perform an initial NE software download 4 - 8

NE Software Upgrade 4 - 13

To upgrade software to a new release 4 - 13

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

To activate an NE software generic 4 - 30

To check for successful NE software upgrade 4 - 34

To solve NE software upgrade problems 4 - 36

To retrieve NE software generic information 4 - 46

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

Database backup 4 - 49

Overview 4 - 49

To limit the number of saved backups 4 - 49

Manually backup database to the WaveStar® CIT 4 - 51

To retrieve NE database information 4 - 55

Supporting information for Retrieving NE database information 4 - 56

To restore a database to a network element 4 - 58

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

5 Miscellaneous

Supported NE Releases with WaveStar®.CIT 5 - 2

Technical Support 5 - 3

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

C O N T E N T Si v


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

Issue 1.1, March 2007

A About this Document

Purpose The LambdaUnite®.MultiService.Switch.(MSS) Release.8.0.20 Software Release Description (SRD) provides procedural information required to install the 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 LambdaUnite®.MultiService.Switch.(MSS) Release.8.0.20.

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

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.

A - 1Lucent Technologies - ProprietarySee Notice on first page

LambdaUnite® MultiService Switch (MSS), Release.8.0.20 Software Release DescriptionIssue 1.1, March 2007

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

About this Document

The following briefly describes the type of information found in each chapter.

Section 1 - New Features

This section provides a listing of LambdaUnite®.MSS features that are new in Release.8.0.20.

Section 2 - Fixed Problems

This section provides a listing of the problems from the previous LambdaUnite®.MSS Network Element (NE) software/hardware and WaveStar®.CIT (Craft Interface Terminal) software releases that have been fixed in LambdaUnite®.MSS Release.8.0.20.

Section 3 - Known Problems

This section provides descriptions and workarounds to existing problems in LambdaUnite®.MSS Release.8.0.20 and WaveStar®.CIT Release.16.02.00.

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 LambdaUnite®.MSS Network Element software of an existing LambdaUnite®.MSS system to LambdaUnite®.MSS Release.8.0.20.

Section 5- Miscellaneous

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

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

A - 2 Lucent Technologies - ProprietarySee Notice on first page



1 New Features

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

Contents 0

Overview 1 - 2

Purpose 1 - 2

Standards Compliance 1 - 2

1 - 1Lucent Technologies - ProprietarySee Notice on first page

LambdaUnite® MultiService Switch (MSS), Release.8.0.20 Software Release DescriptionIssue 1.1, February 2007

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

New FeaturesOverview

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

Overview 0

Purpose The following chapter briefly list the most important new features of LambdaUnite®.MSS Release.8.0.20. For the complete and detailed feature content of LambdaUnite®.MSS Release.8.0.20 please refer to the LambdaUnite®.MSS Applications and Planning Guide and LambdaUnite®.MSS User Operations Guide respectively.Please note that in the case of upgrade, dependant on the release the upgrade starts from, the new features of LambdaUnite®.MSS Release.8.0.20 are a set of the new features of all intermediate releases.

Standards Compliance Lucent Technologies 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 Lucent Technologies product families.

Lucent Technologies intelligent control plane, implemented in 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).

Lucent Technologies is heavily involved in various study groups with ITU-T, Telcordia™ and ETSI work creating and maintaining the latest worldwide SONET and SDH standards. 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.

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

1 - 2 Lucent Technologies - ProprietarySee Notice on first page


Issue 1.1, February 2007

1a New Features of Release.8.0

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

Contents 0

Circuit Packs 1a - 2

Purpose 1a - 2

Most Important New Circuit Packs 1a - 2

Software Features 1a - 3

Purpose 1a - 3

Most Important New Software Features 1a - 3

ONNS Feature Enhancements 1a - 4

Purpose 1a - 4

Most Important New ONNS Feature Enhancements 1a - 4

1 a - 1Lucent Technologies - ProprietarySee Notice on first page


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

New Features of Release.8.0Circuit Packs

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

Circuit Packs 0

Purpose The following section list the most important new types of prime plug-in units and optical interface modules of LambdaUnite®.MSS Release.8.0.

Most Important New CircuitPacks

• Private Line Card for one 10 GbE XFP or eight 1 GbE SFPs

• 10G XFPs (10 km/40 km) for Private Line card and XFP-based OP10 Parent cards

• 1 GbE SFPs for Private Line Card

• 2G5 CWDM SFPs (8 colors; 40 km and 80 km)

• New OP2G5 Single-Density Parent Board

• LOXC-pack with 40G lower-order switch capacity (two slot version)

• Tunable Xtreme-compatible circuit packs

• OP10/XTTC

• OP10/XTTL

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

1 a - 2 Lucent Technologies - ProprietarySee Notice on first page



New Features of Release.8.0Software Features

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

Software Features 0

Purpose The following section list the most important new software features of LambdaUnite®.MSS Release.8.0.

Most Important NewSoftware Features

• 1:N (N<=10) Broadcast Support

• Allow sub-structuring of unequipped VC-4

• Accept changed electronic SFP label info

• Coarse Wavelength Support

• Correlative Circuit Pack Alarming with Reporting Settings

• Fast Lock Non-Alarmed Report

• Explicit message for assigned TCA profile delete attempt

• Pre-emptible protection access on 2.5G/10G 2-fiber MS-SPRing/BLSR

• Combination of BLSR with LO UPSR

• LO BLSR without Type 2 squelching

• Rolling of lower-order cross-connections (for LOXC-pack with 40G lower-order switch capacity only)

• Support of remote test access for lower-order tributaries/cross-connections (for LOXC-pack with 40G lower-order switch capacity only)

• Support of topology conversion of lower-order cross-connections

• WaveStar®.CIT supports range commands for provisioning of cross-connection ranges

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

1 a - 3Lucent Technologies - ProprietarySee Notice on first page


New Features of Release.8.0ONNS Feature Enhancements

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

ONNS Feature Enhancements 0

Purpose The following section list the most important new ONNS feature enhancements of LambdaUnite®.MSS Release.8.0.

Most Important New ONNSFeature Enhancements

• Data Replication for ONNS

• ONNS Support of UNI Interface

• ONNS support for GE10/PL1 (for 1 GbE interfaces only, and for SONET applications <= 21 STS-1 support only - no STS-3c support)

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

1 a - 4 Lucent Technologies - ProprietarySee Notice on first page



1b New Features of Release.8.0.1

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

Contents 0

Circuit Packs 1b - 2

Purpose 1b - 2

Most Important New Circuit Packs 1b - 2

Software Features 1b - 2

Purpose 1b - 2

Most Important New Software Features 1b - 2

ONNS Features Deferred to a Future Release 1b - 3

Purpose 1b - 3

Most Important ONNS Features Deferred to a Future Release 1b - 3

1 b - 1Lucent Technologies - ProprietarySee Notice on first page


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

New Features of Release.8.0.1Circuit Packs

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

Circuit Packs 0

Purpose The following section list the most important new types of prime plug-in units and optical interface modules of LambdaUnite®.MSS Release.8.0.1.

Most Important New CircuitPacks

• 10G XFP (80 km) for Private Line card and XFP-based OP10 Parent cards

• New OP10 single-density and double-density parent board supporting XFPs

• OP10D/PAR2XFP

• OP10/PAR1XFP

• Three slot wide LOXC40 supporting XC320 as higher-order cross-connect (LOXC40G3S/1)

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

Software Features 0

Purpose The following section list the most important new software features of LambdaUnite®.MSS Release.8.0.1.


• For the STM-64 interfaces the system supports 4 fiber Multiplex Section Shared Protection Ring (MS-SPRing) Transoceanic Protocol protection scheme with re-establishment of extra traffic. Extra traffic is reestablished during protection switches on channels not needed to protect service traffic.

• The GE10PL1/1A8 Gigabit Ethernet unit supports the Link Capacity Adjustment Scheme (LCAS) acc. to the ITU-T Rec. G.7042/Y.1305

• Support of lower order loopback

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

1 b - 2 Lucent Technologies - ProprietarySee Notice on first page



New Features of Release.8.0.1ONNS Features Deferred to a Future Release

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

ONNS Features Deferred to a Future Release 0

Purpose The following section list the most important ONNS features that have been deferred from LambdaUnite®.MSS Release.8.0.1 to a future Release.

Most Important ONNSFeatures Deferred to a

Future Release

• Full Support of MPLS on SCN

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

1 b - 3Lucent Technologies - ProprietarySee Notice on first page


New Features of Release.8.0.1ONNS Features Deferred to a Future Release

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

1 b - 4 Lucent Technologies - ProprietarySee Notice on first page



1c New Features of Release.8.0.20

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

Contents 0

Software Features 1c - 2

Purpose 1c - 2

Most Important New Software Features 1c - 2

ONNS Features Deferred to a Future Release 1c - 2

Purpose 1c - 2

Most Important ONNS Features Deferred to a Future Release 1c - 2

1 c - 1Lucent Technologies - ProprietarySee Notice on first page


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

New Features of Release.8.0.20Software Features

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

Software Features 0

Purpose The following section list the most important new software features of LambdaUnite®.MSS Release.8.0.20.


• TOP-WO to TOP+EX conversion

• Path provisioning/de-provisioning during TOP+EX ring switch conditions

• Back-to-back TOP+EX to 1+1 MSP Cross-Connections

• Back-to-back TOP+EX to 1:1 MSP Cross-Connections

• Back-to-back TOP+EX to MS-SPRing Cross-Connections

• Back-to-back TOP+EX to TOP+EX Cross-Connections

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

ONNS Features Deferred to a Future Release 0

Purpose The following section list the most important ONNS features that have been deferred from LambdaUnite®.MSS Release.8.0.20 to a future Release.

Most Important ONNSFeatures Deferred to a

Future Release

• Full Support of MPLS on SCN

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

1 c - 2 Lucent Technologies - ProprietarySee Notice on first page



2 Fixed Problems

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

Contents 0

Introduction 2 - 3


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

Area Configuration Management 2 - 4

Area ONNS 2 - 5

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

Area Performance Monitoring 2 - 6



Area ONNS 2 - 8


Area Fault/Alarm Management 2 - 12


Area Gigabit EtherNET 2 - 14

Fixed Problems in Release.8.0 2 - 18



Area ONNS 2 - 22


Area Equipment Protection 2 - 28



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

Fixed Problems


Area Security Management 2 - 31

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




Fixed ProblemsIntroduction

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

Introduction 0

This chapter provides a listing of the problems from the previous LambdaUnite®.MSS Network Element (NE) software/hardware and WaveStar®.CIT (Craft Interface Terminal) software releases that have been fixed in LambdaUnite®.MSS Release.8.0.20. Please note that in the case of upgrade, dependant on the release the upgrade starts from, the fixed problems of LambdaUnite®.MSS Release.8.0.20 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 Gigabit EtherNET

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 ProblemsFixed Problems in Release.8.0.20

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

Fixed Problems in Release.8.0.20 0

The problem communicated via the following alert has been fixed in LambdaUnite®.MSS Release.8.0.20:

• 06-0836 LambdaUnite MSS: ONNS, meshed restoration, endless controller reboot if deprovisioning packs

• 06-0844 LambdaUnite MSS: ONNS, meshed restoration, rerouting problems after long term operation

Area Installation, SoftwareDownload, Backup &

Restore, Upgrade

Fixed Problem 8.0.1 - nb68101

Traffic outage of several minutes during downgrade from Release.8.0.20 to Release 7.0.3/Release.8.0.1

When downgrading from Release.8.0.20 to Release 7.0.3 or Release.8.0.1 by

• either replacing the flash card and restoring a database

• or via the Trial and Revert options of the APPLY command,

full resets of circuit packs may occur. Those full resets lead to traffic outages of several minutes.

Area ConfigurationManagement

Fixed Problem - nb74253

Traffic Loss after XC Switch

All traffic may be lost, if a XC gets active again after a full reset (e.g.: pack exchange).


CIT exchange circuit pack option does not work for OP2G5 packs

The operator will not be able to exchange an OP2G5 circuit pack via CIT GUI.

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





Area ONNS Fixed Problem 8.0.1 - nb69006

Restoration auto-revertive ONNS connections remain in state CON&OK&WTORV

Restoration auto-revertive connections which had a setup retry during restoration will remain in the state CON&OK&WTORV. This behavior has the following impacts:

• A repair of the original path of this restoration connection will trigger the notification “Original Path is Clear, Waiting To Revert” but no reversion will happen.

• The restored path persists and traffic continues to go via this path.

• The original path will stay forever without traffic.

• A failure of the restored path will trigger a restoration via a new path, which will also not revert back to the original path.


CTL reboot on ONNS connection setup from/to EDGE ports in MS-SPRing/BLSR groups with Automatic Squelch Map Calculation enabled

If automatic squelch map calculation (ASMC) is enabled for an MS-SPRing/BLSR node and an ONNS connection is set up to or from a ring port (= edge port) of this node, the CTL will perform a reboot. Nevertheless the ONNS connection setup is successful.

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




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

UPSR/SNCP)


Circuit provisioning and de-provisioning during active protection switches in MS-SPRing TOP+EX rings is not supported

For TOP+EX rings provisioning of new circuits and de-provisioning of circuits must only be performed when the ring is in an idle state. Never perform circuit provisioning or de-provisioning when protection switches are active in the ring, as this will result in

• the new circuit is not set-up successfully,

but existing traffic is not disturbed.

Area PerformanceMonitoring


SES PM counter increases during unavailable time

In the case of disturbed traffic, for instance during LOS conditions, Performance Monitoring (PM) Severely Errored Seconds (SES) are counted even in the case of a duration longer than 10 seconds, where unavailable time should be signalled and counted and SES counts should not be performed. These SES counts during unavailable time are wrong and should be ignored.

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





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

Fixed Problems in Release.8.0.1 0


Fixed Problem 8.0 - nb61660

Not possible to establish 600 user sessions through gateway NE

If IP access is used for management communication and the gateway NE is equipped with CTL/3S or CTL/3T, it is only possible to establish 318 user sessions through the gateway NE. The problem affects only gateway NEs equipped with CTL/3T or CTL/3S, which should allow to create 600 user sessions.


When creating crossconnection the XC number generator overwrites the XC number when filling the parameters for creating the cross connection

Customer could not assign his XC number if that is entered as the first step when creating a cross connection.

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




Area ONNS Fixed Problem 8.0 - nb60031

ONNS: Auto-revertive connections can behave like unprotected connections in case of interrupted restoration attempt

If traffic, which is protected in the ONNS network by an Auto-revertive connection, will be interrupted outside the ONNS domain it can happen that a restoration attempt is started and interrupted shortly after this. From that point in time the connection behaves like an unprotected connection.

The issue only occurs when the failure is fed from the destination node side to the ONNS connection. Such a failure can e.g. occur during following scenarious:

• Unprotected traffic will be interrupted.

• Double failure in e.g. SNCP, MSP, and MS-SPRing protected traffic.


Setup of unidirectional ONNS to UPSR/SNCP Constructs (OUCs) not possible in case of two unidirectional ONNS connections with opposite directionality using same tributaries

The setup of unidirectional ONNS to UPSR/SNCP Constructs (OUCs) - i.e. provisioning the unidirectional SNCP/UPSR part of an OUC - on top of unidirectional ONNS connections is not possible under the following circumstances:

1. Two unidirectional ONNS connections of opposite directionality exit on the same EDGE tributary and additionally connected to the same INNI tributary, and no OUC already exists on any of both ONNS connections. In this case the setup of an unidirectional OUC on top of any of both unidirectional ONNS connections will be denied. The setup of a bidirectional OUC is accepted, which then will cover both unidirectional ONNS connections together. In case any one of the underlying unidirectional ONNS connections being deleted then, an existing bidirectional OUC will be deleted as well.

2. One unidirectional ONNS connection with unidirectional OUC on top and a second unidirectional ONNS connection exist both on the same EDGE tributary and connected to the same INNI tributary (to get this configuration, the second ONNS connection in this case must have been setup after the OUC on the first ONNS connection). In this case the setup of any additional OUC on top of one or both ONNS connections will be denied.

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






Path restoration with OUC can lead to permanent traffic loss

Autoreroute connections in combination with OUC can lead to permanent traffic loss for restoration scenarios with more then 100 connections involved.

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





UPSR/SNCP)


Problematic node failure recovery in an MS-SPRing/BLSR with OP10/XTT ring interfaces

A node failure in an MS-SPRing / BLSR ring causes ring switches in the nodes adjacent to the failed one. Traffic routed across the failed node is restored whereas traffic added or dropped in the failed node is lost unless there is a DNI/DRI configuration. The behaviour w.r.t. the node failure is as expected. However, when the failed node recovers and OP10/XTT are used as MS-SPRing/BLSR ports in this node, the ring switches might be dropped too early, and excessive traffic hits up to several seconds for the protected traffic originally routed across the failed node might occur.


CTL reset when source/destination node (locz/loca) is entered on creation of a LO add/drop crossconnection to/from the protection bandwidth of an MS-SPRing/BLSR

The CTL will perform a reboot when the destination node (locz parameter) is present for the ENT-CRS TL1 command which tries to provision a Lower Order add crossconnection to the protection bandwidth of a 2 fibre MS-SPRing/BLSR. The same is true when the source node (loca parameter) is present for an attempt to provision a Lower Order drop crossconnection from the protection bandwidth of a 2 fibre MS-SPRing/BLSR. The problem occurs when automatic squelch map calculation is enabled. The correct behavior would be to deny the ENT-CRS command.


Inappropriate signal structure on protection port causes MS-SPRing TOP to fail

If the signal structure of the protection ports of an MS-SPRing with Transoceanic Protocol (TOP) is substructured into VC-4-yc (with y = 4, 16, 64) and a high order VC-3 circuit is provisioned for the x-th timeslot of the worker bandwidth in the ring (with x on VC-3/STS-1 granularity and x = 2, 3, 5, 6, 8, 9,...) the protection of this high order VC-3 in case of a ring switch might fail and the traffic might get lost for the duration of the switch.

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

2 - 1 0 Lucent Technologies - ProprietarySee Notice on first page




Fixed Problem 5.0.1 - nb35304/nb43714

Problematic node failure recovery in an MS-SPRing/BLSR

A node failure in an MS-SPRing / BLSR ring causes ring switches in the nodes adjacent to the failed one. Traffic routed across the failed node is restored whereas traffic added or dropped in the failed node is lost unless there is a DNI/DRI configuration. The behaviour w.r.t. the node failure is as expected. However, when the failed node recovers, the ring switches are dropped too early, and excessive traffic hits up to 2 seconds for the protected traffic originally routed across the failed node have been observed. The traffic hits can be even longer in mixed LambdaUnite MSS/WaveStar BandWidth Manager rings.

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

2 - 1 1Lucent Technologies - ProprietarySee Notice on first page



Area Fault/AlarmManagement


Wrong transient CPFAIL alarm is raised for OP10/XTT in case transmission is enabled

A transient wrong Circuit Pack Failure (CPFAIL) alarm is raised for an OP10/XTT pack (L or C band) when the transmission is enabled (by entering the Txenable command) after setting the optical frequency (Wavelength). This CPFAIL alarm needs to be ignored and the alarm will clear autonomously after some clear validation time.

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





Area PerformanceMonitoring


BBE count is wrong for Lower order VC on LOXC 40G

In the case that for Lower order VCs cross connected via the LOXC 40G the counting of BBE (Background Block Errors) is not correct. Effectively approximately the number of counted block errors is only around the half of the incoming block errors. Due to this fact the TCA will also be raised after approximately double of incoming (real) block errors than the value configured for that TCA.

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




Area Gigabit EtherNET Fixed Problem 8.0 - nb64283

GE10PL1: LCAS not supported, provisioning of LCAS has no effect

At the Virtual Concatenation Groups (VCGs) of GE10PL1 packs Link Capacity Adjustment Scheme (LCAS) is currently not supported. This means that hitless bandwidth adjustment and autonomous removal of members in case of failure is currently not supported. At the management interface it is still possible to enable or disable LCAS or to modify LCAS-related parameters like partial loss of capacity transmitter threshold. However, this has almost no effect:

If LCAS is set to enabled

• the reporting of VCG tributary membership status is reported as Not Applicable (NA) always

• some non-LCAS alarms are suppressed - e.g. Sequence Number Mismatch (SQM) or Loss of Alignment (LOA) - or not reported as required in non-LCAS mode; VCG Server Signal Fail (VCGSSF) alarm would be raised only if all tributaries are failed.

Therefore it is recommended to disable LCAS manually when initially provisioning a VCG, i.e. to change the parameter lcasmode to DISABLE (the default value after provisioning a GE10PL1 pack is ENABLE).


Ethernet traffic loss on GE1 in case of traffic interruptions or degradation on WAN-link

An Ethernet traffic loss has been observed on the WAN-link connected to GE1-packs running in repeater mode when there is a traffic interruption of the WAN-link, e.g. due to ONNS-restoration. In such a case the Ethernet frames are still received at the WAN-port but are dropped inside the GE1-pack and not forwarded as expected to the LAN-port.

The probability that this problem occurs is rather low because it could be only reproduced with traffic interruptions of around 200 ms. That means, e.g. during MS-SPRing/BLSR protection switching the problem will normally not occur, because the switching time is less than 60 ms.

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






GFP-FCS must be disabled when interworking with GE10PL1

LambdaUnite does not support to transport GFP-frames with Frame Check Sequence (FCS) being enabled (FCS is optional acc. to G.7041). It always sends out GFP-frames without FCS because the transported payload is already protected by the Ethernet-FCS.

When receiving GFP-frames with FCS the FCS is appended to the Ethernet frame and passed on to the LAN-port. Such frames will be dropped as invalid by the next NE when checking the Ethernet-FCS.

Therefore when using a GE1-pack or a GE10PL1-pack of LambdaUnite for interworking with other equipment, which supports GFP-FCS it is mandatory to disable GFP-FCS in the other equipment.


Laser might switch off when Far-Side-Facility loopback is enabled

When enabling the Far-Side-Facility (FSF) loopback at an 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 might trigger a consequent action (e.g. disable the laser at the LAN-port) at this remote NE and disrupt the looped traffic.Note, that this only applies for the 10G LAN-port of the GE10PL1.

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





GE10PL1: Default settings for CSF-alarm and CSF-related consequent action may lead to silent switch-off of laser without alarm

The default values for link-pass-through-related alarms and consequent actions are as follows:

• The default severity of the CSF (Client Signal Fail) alarm is “Not Reported”

• The consequent action when receiving a CSF-indication to switch off the laser at the related 10GbE or 1GbE LAN-port is enabled by default (parameter rcf_linkdown of a VCG of GE10PL1)

If those default settings are not changed the following happens in case of a LANLOS or LANNOSYNC at a LAN-port of a GE10PL1:

• This GE10PL1 will transport the CSF-indication over the WAN-link related to this failed LAN-port.

• The VCG at the remote end will detect the incoming CSF-indication and switch off the laser of the related LAN-port as consequent action.

• However, no CSF alarm is raised by the receiving VCG because it is set to “Not Reported”.


Change of interface standard of VCG-ports of GE1 is possible only for all ports via de-provisioning and newly provisioning the pack

When the interface standard of a VCG-port shall be changed via ED-VCG the NE rejects this request. This means that the interface standard of the VCG-ports can only be controlled while pre- or auto-provisioning the pack. It is not possible to selectively change the interface standard of a single VCG-port.

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






Traffic loss of 10GbE link after disruption and repair of the WAN-link

In a configuration with two GE10PL1-packs working in 10GbE-mode and connected via a WAN-link it might happen that traffic is restored only unidirectional when disrupting and repairing the WAN-link, e.g. due to a Full Reset of one of the packs or a fibre break and repair of the WAN-link leading to reception of AIS on all VCG tributaries.

In such a case the GE10PL1 pack detecting the broken WAN-link raises a LFD alarm as expected and clears it when the WAN-link is restored, but drops all frames received via the WAN-link. This is visible via the EDFC-counter of the WAN-port.

To restore bidirectional traffic again a Full Reset of this pack is needed.


GE10PL1: Unexpected LOM alarm raised for VCG-Tributary when working in contiguous concatenation mode

When provisioning a 10GbE port of a GE10PL1 to work in contiguous concatenation mode (i.e. vcat=DISABLE to transport the Ethernet stream via a VC4-64c or STS-192c signal) an unexpected LOM (Loss Of Multiframe) alarm is raised to the VCG-tributary of this port. The alarm remains raised as long as contiguous concatenation mode is active.

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



Fixed ProblemsFixed Problems in Release.8.0

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

Fixed Problems in Release.8.0 0

The problem communicated via the following alert has been fixed in LambdaUnite®.MSS Release.8.0:

• 06-0443 LambdaUnite MSS: Traffic Impact on OP2G5/PAR4 (KFA621) Boards

Area Installation, SoftwareDownload, Backup &

Restore, Upgrade


NE falls back from Duplex Control to Simplex Control in Downgrade/Upgrade scenario

If a Downgrade had to be performed and subsequently the NE is upgraded again, Duplex Control might be autonomously changed to Simplex without notifying the operator.Even the operator gets indicated that Duplex Control is fully operational. However, autonomous CTL equipment protection switches will not succeed. Also manual switches will not lead to an activation of the other CTL.


Specific assignments of HO tributary ASAPs get lost after NE reboot or Upgrade

If the ASAP pointer (ASAP assignment) is changed for Higher Order (HO) tributary in the system (Non-intrusive Monitor - NIM or path termination functions) from the DEFAULT profile to a specific one, and for the system an INIT-SYS or Power OFF/ON is executed, these ASAP assignment might have changed back to DEFAULT after system recovery. The same occurs during Upgrade for ASAPs assigned to HO tributaries. The alarming picture visible after the system recovery might have changed therefore.


CIT aborts session after software download when finishing the trial phase

The CIT aborts its session, which is unnecessary, when the user finish the trial phase with option COMMIT.

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







Not possible to create 1:N broadcast with N>2 using CIT XC Application 1-way Point-to-Point

If more than two 1WAY cross-connections should be created with the same source, the source can not be selected a third time, because the available status is NO.


Only two SNCPs/UPSRs with same input tributaries can be created via CIT GUI individually

It should be possible to create up to ten SNCPs/UPSRs with same input tributaries (WKG/PROTN) individually via CIT GUI, but it is only possible to create two SNCPs/UPSRs with same input tributaries (WKG/PROTN) individually. For the third SNCP/UPSR the CIT wrongly refuses the selection of the tributaries, which are used for the other two SNCPs/UPSRs.

Fixed Problem 7.0.2 - nb56966/nb57179

TID value disappears from last 1:N broadcast leg when using CIT

If some tributaries for an 1:N broadcast are selected in the tributary selection dialog of CIT, and the tributaries are in a BLSR/MS-SPRing, the last TID of the tributary list is not added to the destination list of the create cross-connection dialog. The preselected item has to be selected explicitly with the ENTER-button (or a mouse-click) or another entity in the dialog must be selected before the OK-button is applied.


Selection made by the Delete Cross-Connection CIT screen

The selection list of the CIT Configuration → Cross Connection → Delete screen does not only list all those crossconnection legs, which are starting or ending on the selected port / tributary, but all those crossconnection legs, which have the same XC number as any crossconnection starting or ending on the selected port / tributary.

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





The CIT Cross Connection screen does not display all legs of broadcast connections

When the selected port or tributary is the source of an 1-Way broadcast application, only some of the crossconnection legs are displayed in the CIT Cross Connection screens (e.g. Configuration → Cross Connection → Convert Path Protected XC).


The graphics of broadcast cross connections are not proper shown after extending via CIT Cross Connection Bridge Menu

Only graphics of broadcast cross connections created via the CIT menu Configuration → Cross Connection → Create are displayed proper. When cross connections are extended via the CIT menu Configuration → Cross Connection → Bridge a XC, such cross connection extensions are created as 1-way point-to-point cross connections. Then the graphics of the cross connection extensions are shown as 1-way point-to-point applications instead of a cumulative broadcast cross connection.


Risk of CTL Bootloop when changing interface standard of GE1 VCG from SONET to SDH

Changing the interface standard of GE1 VCGs from SONET to SDH might result in an endless bootloop of the CTL after the next reboot of the CTL, if PM was enabled on one of VCGtribs 2, 3, 5, 6, 8, 9, 11, 12, 14, 15, 17, 18, 20, 21 before changing the interface standard.


Sporadic CTL/DCF reboot in case of massive TL1 commands

It has been observed that the CTL/DCF reboots, thus dropping all managementconnections, when sending provisioning commands from a script file without waiting for the NE reaction (COMPLD or DENY) between the single TL1-commands. (CIT usually waits for the response from the NE).

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






Not possible to provision Lower Order-tributaries with NE Release 6.1.1 via CIT

The CIT offers to provision parameters of Lower Order-tributaries since Release 6.1.0. For backwards compatibility this should work with the current CIT for Release 6.1.x and Release 7.0.x.For NE Release 7.0.x provisioning of Lower Order-tributaries is possible but not for Release 6.1.1. The user cannot provision Lower Order-tributaries because the Apply-buttons never gets active to commit the modified parameters.The screen for Lower Order-tributary also wrongly shows an entity for provisioning Threshold Crossing Alert profiles with Release 6.1.1. This feature is not supported for Release 6.1.1

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




Area ONNS Fixed Problem 7.0 - nb50043

Creation of an OUC may be positively acknowledged, although the OUC has correctly not been established

Under the following circumstances the creation of an ONNS to UPSR/SPCP Construct (OUC) will be positively acknowledged, although the OUC has not been established based on a correct validation: The OUC has bandwidth STS3 or larger (VC4 or larger) and a part of the requested bandwidth on the protecting EDGE port (but not the first STS1) is already allocated by a cross connection (e.g. another OUC) of smaller bandwidth. Note: Such an improper tributary selection is not blocked by CIT.

Fixed Problem 7.0 - nb52200/nb57517

ONNS does not become operational after fast double XC switch

When performing a XC switch followed by another XC switch within two minutes back to the previous active XC the ONNS functionality does not become operational and may be blocked for about 2 hours. ONNS-related commands are rejected with error response 'ONNS not yet initialized'. ONNS path setups or restorations involving this NE are not executed.It is also possible that the ONNS blocking state occurs immediately after enabling the ONNS functionality. The reason would then be that in the node two consecutive XC protection switches have occurred before.

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






Do not execute two (or more) Link Defragmentation actions on one and the same NE simultaneously

Simultaneous execution of two or more Link Defragmentation actions on one and the same NE on links towards different neighbor NEs may lead to undesired behaviour, if ONNS paths between links involved in the Link Defragmentation actions exist. This undesired behaviour may consists of one or more of the following effects:

• Wrong and inconsistent reporting about success or failure of the Link Defragmentation actions. E.g. one action reported as successfully finished, the other one as partially complete due to a local cross connect release failure, although both actions are in fact incomplete.

• Link Defragmentation actions remaining incomplete, i.e. a number of moves are not performed.

• Single cases of multiple cross connections assigned to one path ID left over from the Link Defragmentation activity.

• Defragmentation analysis applied to involved links afterwards reporting nonsense.

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





UPSR/SNCP)


Incorrect alarm severity and service state for the MSP/APS protection line after a CTL reboot

If after a CTL reboot (e.g. caused by leaving the maintenance condition) there is a signal fail of the protection line of an 1+1 MSP/APS group e.g. due to LOS while the worker line is the active one, the LOS alarm is incorrectly reported as critical (CA) and service affecting (SA) instead of minor (MN) and non-service affecting (NSA). The problem disappears as soon as there has been a Signal Fail of the worker line, i.e. then all subsequent Signal Fails of the protection line are handled correctly.


Incorrect alarm severity and service state for Circuit Pack not Present alarming of inactive port of a BLSR

In the case that a port unit that is configured in a BLSR configuration is removed, the related Circuit Pack not Present is alarmed with service affecting (SA) service state while it is inactive due to a protection switch. As inactive unit however it should have the service state not service affecting (NSA) as the traffic is protected and not affected.

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






LambdaUnite´s automatic squelch map calculation function is not compatible with DMX´s and FT-2000´s ring circuit audit function

When LambdaUnite´s automatic squelch map calculation is enabled it does not re-distribute the source and destination node information for its local crossconnections across the ring as determinated by the automatic squelch map calculation function. The following consequences will result from this:

• The RTRV-CKT and RTRV-TMSLT commands as supported by DMX to retrieve the view of the node on a BLSR circuit or timeslot will not return loca and locz values for crossconnections in remote LambdaUnite nodes. This is not deemed critical as the operator can check for PIF indications to detect whether a circuit is not complete.

• When DMX´s ring circuit audit function is enabled while its automatic squelch map calculation function is disabled, squelch map inconsistency alarms will be raised as DMX checks the consistency of the loca / locz values as communicated by a node against the result of its ring circuit validation. Therefore it is recommended not to combine LambdaUnite nodes with enabled automatic squelch map calculation function with DMX nodes in the before mentioned combination of modes. There are no squelch map inconsistency alarms when the automatic squelch map calculation function is disabled for LambdaUnite nodes as in this case the user provisioned loca/locz values are sent around the ring.

• It is strictly recommended not to enable LambdaUnite´s automatic squelch map calculation function when FT-2000 nodes are in the ring. FT´s ring circuit audit function is per crossconnection and cannot be disabled in service. That means there would be standing alarms in existing rings. Further incompatibilities might occur, but have not been investigated in detail. Note that FT-2000 does not support automatic squelch map calculation, so the way of provisioning crossconnections is the same for LambdaUnite and FT-2000.


Ring Discovery incomplete after deleting a node in a mixed DMX-LambdaUnite 2F-BLSR ring

It has been observed that after a deletion of a DMX-node in a 2F-BLSR ring consisting of DMX and LambdaUnite the ring discovery failed and Ring Incomplete, Ring Protection Switch Suspended and Node ID Mismatch alarms were present.

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





Automatic selection of destination of LO-trib does not work for BLSR/MS-SPRing 2-way Thru application

CIT offers with the crossconnect application “BLSR/MS-SPRing 2-way Thru” an automatism to select the destination trib for the user. When the user creates some cross-connection BLSR/MS-SPRing 2-way Thru with a special order he gets a wrong warning message and can not create the cross-connection. For instance, the user creates a cross-connections with source LOVC3-tribs in following order: ...-100-100, ...-110-100,...120-100, he gets a warning message that the corresponding destination LO-trib of source trib ...-140-100 is in use.


Tributaries from DS3 ports can not be used as input for path protection

If an attempt is made, to create a path protected cross connection with tributaries (STS1 path terminations) from DS3 ports as input tributaries, then the command is denied with SROF - Status, Requested Operation Failed.The correct behaviour would be to allow and complete the command.


CTL reboot when attempting to create LO cross connections to MS-SPRing/BLSR protection tributaries

If an attempt is made, to create a low order (LO) cross connection to a tributary belonging to the protection port or bandwidth of an MS-SPRing/BLSR protection group, then the CTL will reboot. The correct behaviour would be to deny the attempt.

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






For MSP 1:1 the Lockout request does not deny extra traffic from protection section

For MSP 1:1 when Lockout of Protection is applied, the working channels are correctly locked to the working sections. The extra traffic may be disrupted by maintenance actions on the protection section, instead of being replaced by AIS all the time the lockout state lasts (extra traffic is not dropped for Lockout of Protection state, no AIS is inserted). Only applicable if extra traffic is really used in the application.

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




Area Equipment Protection Fixed Problem 7.0 - nb51524

Manual path protection switch configurations get lost after an autonomous LOXC equipment protection switch

The operator gets notified that the status of a path protection group has been changed autonomously from a manual switch request to a normal operation (cleared switch request). Manual LOXC equipment protection switch do not trigger such an unexpected state transition.


Wrong port mode after re-insertion of a protected EP51 pack

If the active EP51 circuit pack of an EP51 Equipment Protection (EQP) group has been plugged-out and re-inserted, then all disconnected ports who had the port monitoring mode set to AUTO recover with the monitoring mode set to MONITORED. This causes all disconnected ports to report an LOS alarm.

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





Area Fault/AlarmManagement


HO Cross Connections generated via Setup of LO Cross Connections do not contribute to the Enhanced Mode of SA/NSA Alarm Classification Functionality

With the one step approach for low order (LO) cross connections, high order (HO) cross connections are generated implicitly. However, these HO cross connections do not contribute to the enhanced mode of SA/NSA alarm classification functionality. Therefore it can happen that if enhanced mode of SA/NSA alarm classification is set to Enable and a port has only HO cross connections generated implicitly via LO cross connections, that the port related alarms are reported as NSA (non-service affecting) because formally no explicit HO cross connection does exist for this port. This effect can also be seen in combination with explicitly created HO cross connections for this port bandwidth. For these the enhanced mode of SA/NSA alarm classification functionality applies, however the HO cross connection generated via setup of LO cross connections will never contribute to the SA/NSA calculation.


Creation of a pipe cross connection not rejected despite pre-existing cross connection loops

In adaptive tributary mode the provisioning of a pipe cross connection should be denied if there is a cross connection on at least one tributary in the bandwidth of the pipe cross connection. However the denial only occurs if there is a cross connection loop for the first tributary. Existing cross connection loops on other tributaries will cause the following effects:

• the transmission of a constituent signal of the pipe cross connection with a cross connection loop in its bandwidth will fail

• the loop cannot be deleted via CIT GUI as long as the pipe cross connection exists

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





Not all probable causes are set to Not Reported by creating NonReporting ASAPs via CIT

The CIT shall support the operator to create ASAPs, which have all Probable causes set to “Not Reported”. This is not the case for some profiles. Following NonReporting ASAPs are not created correct:

• Ethernet

• Equipment with Protection State Dependence

• SDH/SONET ports

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





Area Security Management Fixed Problem 2.1 - hz03125

Logout of all NE users does not terminate all user sessions

If a superuser logs out all NE Users (TL1 command CANC-USER-SECU without specifying an User ID), not all USER sessions are terminated.In some cases no user session is terminated at all.The expected behavior is, that all sessions of all users are terminated which are not superusers or MEMADMIN users.

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




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




3 Known Problems

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

Contents 0

Introduction 3 - 2




Area Synchronization Management 3 - 11

Area ONNS 3 - 12


Area Equipment Protection 3 - 35



Area Security Management 3 - 45

Area Gigabit EtherNET 3 - 46



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

Known ProblemsIntroduction

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

Introduction 0

This chapter provides descriptions of significant customer-affecting problems known to exist in LambdaUnite®.MSS Release.8.0.20 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 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 Gigabit EtherNET

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 LambdaUnite®.MSS release

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




Known ProblemsKnown Problems

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

Known Problems 0

Please note, that the following alert which has been published for LambdaUnite®.MSS Release.7.0 is still relevant for Release.8.0.20.

• 06-0670 LambdaUnite MSS: WS-CIT ONNS GUI not working after WS-CIT upgrade from previous version

0Area Installation, SoftwareDownload, Backup &

Restore, Upgrade

Problem 8.0.2 - nb69117

ONNS GUI of CIT is not updated when a CIT software upgrade from Release.7.0.2/Release.7.0.3 to Release.8.0.20 is performed

Typically the CIT software can be upgraded from one release to a new one without uninstalling the previous one. This is not the case for the ONNS GUI of the CIT. The following upgrades are affected:

• upgrading from Release 7.0.2 (CIT Release 15.03.00 Build 1304) to Release.8.0.20 (CIT Release.16.02.00 Build.1445) or

• upgrading from Release 7.0.3 (CIT Release 15.03.01 Build 1421) to Release.8.0.20 (CIT Release.16.02.00 Build.1445)

The traditional part of CIT (Network Element View) is not affected by this upgrade issue.

Workaround:

If the ONNS GUI of the CIT is used, the previous CIT must be uninstalled before installing a new release of the CIT. To keep the settings of your old installation use the option Remove Installed WaveStar CIT Components Only (retain user information) within the WaveStar CIT - UninstallShield Wizard.


Traffic outage of several minutes during downgrade from Release.8.0.20 to Release 7.0.2

When downgrading from Release.8.0.20 to Release 7.0.2 by

• either replacing the flash card and restoring a database

• or via the Trial and Revert options of the APPLY command,

full resets of circuit packs may occur. Those full resets lead to traffic outages of several minutes.

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




Problem 8.0.1 - nb67404

GE1 hang-up and CPCOMF alarm when Downgrading from Release.8.0.20 to Release.7.0.2/Release.7.0.3/Release.8.0.1

When

• upgrading a LambdaUnite node equipped with GE1 packs from Release.7.0.2/Release.7.0.3/Release.8.0.1 to Release.8.0.20 using the trial mechanism and falling back to Release.7.0.2/Release.7.0.3/Release.8.0.1 or

• when downgrading to Release.7.0.2/Release.7.0.3/Release.8.0.1 via the emergency downgrade procedure after an upgrade trial

the GE1 packs hang up in recovery. A Circuit Pack Comm Failure (CPCOMF) alarm is 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.

Workaround:

To bring the GE1 packs 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.

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





Problem 8.0.1 - nb65799

Problems with parallel database backups through one gateway NE

If IP access is used, then only one database backup through the gateway Network Element (GNE) is possible at the same time without problems. If it is tried to perform additional database backups in parallel through the GNE, then the attempts will either be denied (immediately or after some time), or the backups become very slow. In the case that the backup is denied, all running database backups through the GNE will be terminated. This problem affects mainly large networks, where database backups for the whole network are performed regularly. The total time needed to perform a backup for the whole network will increase significantly.

Workaround:

Schedule database backups in a way, that only one database backup is performed at a time through a gateway NE.

Problem 5.0 - nb31029

CPCOMF alarm on GbE pack sometimes raised after upgrade

When upgrading NEs to a new SW load or downgrading to the previous SW load again a CP_Commfail alarm is raised in about 25% of the cases for GE1 packs. The root cause is that the GE1 pack does not take over system date and time correctly. Traffic is not affected.

Workaround:

Setting date and time re-distributes date and time within the system. As a result the CP_Commfail disappears. Usually the network management systems autonomously set date and time when logging in again after the CTL-reboot due to the release upgrade is completed.

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




0Area ConfigurationManagement

Problem 8.0.1 - nb67921/nb69015

Traffic not established when reconfiguring GE10PL1 from 10G to 1G mode or vice versa

When reconfiguring a GE10PL1 pack from a 10G mode to an 1G mode or vice versa by removing all cross-connections, de-provisioning the XFP (SFPs), provisioning some SFPs (XFP), creating cross-connections and enabling tributaries, then all members should change their state to ACTIVE and traffic should run over the active tributaries. However, membership status does not change as expected and traffic is not established. After applying a Full reset to the pack traffic is established as expected.

Workaround:

When switching from 10G-mode to 1G-mode or vice versa always perform the following steps:

• 1st step remove old XFP (SFP’s)

• 2nd step deprovision old XFP (SFP’s)

• 3rd step apply full reset to GE10PL1

• 4th step insert SFP’s (XFP)

Problem 8.0.1 - nb68747

Auto-provision of the signal structure of a tributary does not happen before sending the create cross-connection command by CIT

Cross connection creation via CIT GUI sometimes may fail without manual adaptation of the substructure of the involved ports.

Workaround:

If creation of cross connection is denied with IDNC /* Input, Data Not Consistent, Specified Tributary does not support the indicated rate */, check the substructure of the involved ports and adapt it manually. Afterwards repeat the creation of the cross connection.

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






Port Mode Timer does not expire under certain Equipment Protection Scenarios

If for an EP155 or EP51 pack an 1+1 Equipment Protection (EQP) is set up, the Port Mode Timer, which determines the delay for the transition of the port monitoring mode from AUTO to MONITORED, will never expire under the following conditions: If on the currently active pack the Port Mode Timer is currently running (expiring) because of an appropriate LOS transition and during this period an Equipment Protection switch happens to the inactive pack, the newly active pack will stick at the AUTO Port Mode because uninformed about the running Port Mode Timer on the formerly active pack. The newly active pack gets actually an LOS clears transition in the moment of the Equipment Protection switch, however this “early” transition cannot be used to start the Port Mode Timer because of suppression methods to overcome undesired Port Mode changes during Equipment Protection switches without an Port Mode Timer active. The Port Mode Timer will be started on the next LOS clears transition for this pack. This however is not directly correlated in time to the original one on the formerly active pack, meaning the transition can be anywhere in the future.

Workaround:

If the port mode does not change as expected in the described scenario, set the port mode to MONITORED manually.

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





Setup or Roll of LO-cross-connections on LOXC40 might fail when issued in too fast sequence, e.g. via TL1-script

When setting up or rolling a lot of LO-cross-connections being switched on the LOXC40 it must be avoided to issue the ENT-CRS or ENT-ROLL commands in a too fast sequence. If the command sequence is sent to the NE too fast (e.g via an TL1 script) some LO-cross-connection might not be setup correctly even though all commands are correctly acknowledged by the COMPLD indication.

A reboot by applying a Controller Reset to the CTL or to the LOXC40 cleans up configuration and ensures to have all cross-connections set up correctly in HW. Waiting for the COMPLD is not sufficient.

When using the ranging support of CIT to setup LO-cross-connections the issue does not occur because at most 63 LO-cross-connections can be set up with a single request which does not lead to an overload condition on LOXC40.

Workaround:

When issuing a lot of ENT-CRS commands to setup LO-cross-connections or ENT-ROLL commands to roll LO-cross-connections (e.g. via TL1-script) add a delay of 500ms in case of VC12 and VT1.5 connections, 800ms in case of LO-VC3 connections between the ENT-CRS commands.

If there is a suspicion that not all LO-cross-connections have been setup as expected apply a CTL reset or a Controller Reset to the LOXC40 pack.


Port mode set to AUTO if CTL recovers during running Port Mode Timer for this port

If a port has a Port Mode Timer running because of a recognized “LOS clears” event (and the signal does not change on this port) and during this time period the CTL recovers, the port mode will be set to AUTO after the CTL recovery. The port will stay in AUTO mode until the next “LOS clears” event. The port will behave as NMON till this event.

Workaround:

If observed, set the port manually to MONITORED or generate artificially an “LOS clears” event for this port.

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






Not possible to release a crossconnect loopback with non-default rate in adaptive mode

When the user has established a crossconnect loopback with a rate (e.g. sts48) which is not the default rate (e.g. sts1) he can not release this crossconnect loopback. The CIT offers only default rates with the release crossconnect loopback screen, although the port is in adaptive mode and the tributary rates are different to the default rates. Selects the user a tributary with default rate (e.g. sts1) in the selection screen the CIT hangs-up.

Workaround:

In this case use Cut Through to release the crossconnect loopback.


LOXC configuration hang-up in rare cases with late indication about communication problems

High-frequent configurations (so far only observed with TL1 scripts) may lead to a configuration hang-up of LOXC hardware although all TL1 commands are replied by a successful completion. This hang-up of the LOXC hardware will be indicated by a Circuit Pack Comm Failure (CPCOMF) alarm, but it can take up to 30 minutes (worst case) until the alarm is raised. Transmission alarms in other NEs may pop-up or do not clear unexpectedly, although the applied configuration should have avoided this, since transmission setups within UNITE has not really been applied (due to the LOXC hang-up). The whole scenario is not traffic affecting for existing configurations.

Workaround:

Do not use scripts for LOXC configuration. If this scenario has been entered then perform a controller reset to the failed LOXC pack. Note that the reset request will only be performed after 5 minutes since a graceful shutdown is hindered by the configuration hang-up (after 5 minutes, the controller reset is re-applied in a different way which is still not traffic affecting).

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




Problem 5.0.1 - nb35767

OP40/1.3IOR1 might fail to recover successfully on plug-in or after NE power-fail

When plugging in an OP40 intra-office pack it has been observed that the pack does not recover successfully. Exact figures for probability are not available, the effect is related to pack temperature. The probability to occur is higher when inserting a pack which was already in operation shortly before than when inserting a cold pack. Also after a short NE power fail (less than 5 seconds) with a probability of 50% the OP40 pack may not recover successfully.

Workaround:

Apply a Full Reset to the OP40 intra-office pack which does not start up in time for the scenarios mentioned above.

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





0Area SynchronizationManagement

Problem 8.0.1 - nb67042

Temporary CPFail alarm for standby XC after frequency jump at active timing reference followed by XC protection switch

When a frequency jump at the active timing reference has occurred, a consecutive XC equipment protection switch causes some unexpected alarms to be raised and cleared:

• For the newly standby XC a Circuit Pack Failure (CPFail) alarm is raised and cleared again after 10 to 12 seconds

• Two Fast Lock mode entered (NEFASTLOCK) alarms are raised and cleared again after 2 minutes at latest (this alarms are only raised in SONET mode and when the alarm is set to Reported in the alarm severity assignment profile).

Those unexpected alarms may occur not only when the XC equipment protection switch happens rather shortly after the frequency jump but also later, i.e. after all frequencies and oscillators should have stabilized already. The effect has been observed with a frequency offset of 4 ppm, followed by a forced XC equipment protection switch five minutes later.

Workaround:

Ignore the temporary CPFail alarm.

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




0Area ONNS Problem 8.0.2 - nb71267

AUTONR connections may show connection state "NOCON" after upgrade to Release.8.0.20

After the upgrade to Release.8.0.20 it may happen, that some ONNS connections of protection type AUTONR will show the state NOCON, although the traffic over these connections is ok. Additionally affected connections, that showed the state NOCON after upgrade, will behave as unprotected.

Workaround:

1. Apply a manual reroute for all affected connections (for all connections with state NOCON).

After the manual reroute the connection state will be the correct one again, but the connections will still behave as unprotected. For that reason it is necessary to

2. apply an XC switch/reset to all nodes in the ONNS network. After this XC switch/reset the affected connections will behave as AUTONR again.

Problem 8.0.1 - nb66954

Same UNI-node and SCN-node IP address can be provisioned

Malfunctions or instabilities can not be excluded in case of the same IP address is provisioned for an UNI-node and an SCN-node.

Workaround:

The operator has to attend to provision different IP addresses for UNI-node and SCN-node.

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





Problem 8.0.1 - nb66557

UNI data inconsistency when XC and CTL reboots

An XC reboot or protection switch and a following succeeding CTL reboot or protection switch can lead to data inconsistencies of UNI connections.

Workaround:

In such reboot scenario all ONNS switched connections with the parameter ConnCtrl=SC have to be checked for consistency by searching for an appropriate UNI client connection. This can be done via TL1:

• By using the commands RTRV-PATH (ONNS connection) and RTRV-PATH-UNI (UNI connection) on the rebooted NE. For every ONNS connection in the RTRV-PATH output with a parameter value “SC” for the parameter ConnCtrl an UNI connection in the RTRV-PATH-UNI under the same ConnID should be available.

Or can be done via CIT:

• By selecting the view path screen. Select every ONNS connection with the parameter ConnCtrl=SC and select the button “UNI Client” to get the appropriate UNI connection. For every selected ONNS connection an appropriate UNI connection should be available.

ONNS connections with the parameter ConnCtrl=SC but no appropriate UNI client connection need to be deleted.

Problem 8.0.1 - nb65629

ONNS connection setup to a Z-EDGE port in a 2f-BLSR/MS-SPRing group fails, if this port is in a failed state

An ONNS connection setup fails with “E022: Status, Path setup Failure, caused by signal transmission failure at egress node” under the following condition:

• The Z-node EDGE port is in a 2f-BLSR/MS-SPRing group and

• a ring switch is active, i.e. the Z-node EDGE port is in a failed state.

Workaround:

Before the ONNS connection setup repair the ring failure.

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





Sync Data of Local DB audit is needed before Sync Data of Path Neighbor DB Audit in case of incomplete Cross Connections

The synchronization of the path data will fail with a syntax error “Data not consistent” if a ONNS path neighbor audit shows in addition to a missing path ID incomplete Cross Connections.

Workaround:

A synchronization of the local data has to be done before the synchronization of the path data works correctly.


Status of 1+1 protected ONNS paths can be wrong

The following two scenarios with wrong status during setup of 1+1 protected ONNS connections are known:

1. a transmission failure during the setup of the second path of an 1+1 protected ONNS connection has no impact on the connection except the status of the second path (CON&FAILED).

2. a signaling failure during the setup of the second path of an 1+1 protected ONNS connection leads to an unprotected connection without any indication about the missing 1+1 protection.

Workaround:

Check the status of both paths of the 1+1 connection after successful setup.


Unidirectional M:N groups not supported

In release 8.0 unidirectional paths for M:N protection groups are not supported anymore. This has the following consequences:

• Before Upgrade to R8.0 all unidirectional connections of a M:N protection groups have to be removed and then setup as bidirectional connections of a M:N group.

• After Upgrade to R8.0 the setup of new unidirectional connections of a M:N groups is not possible anymore.

Workaround:

Create only bidirectional paths for M:N protection groups

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






Database Restore not possible for ONNS data

With the introduction of the new “Data Replication” functionality it is not possible to restore “old” ONNS relevant data like ONNS connection data and cross connections at iNNI, EDGE, and UNI ports. The system keeps the current ONNS data and ignores the changes triggered by the Database Restore function.

Workaround:

Reboot both XCs (Controller Reset) and enter immediately afterwards the maintenance mode (necessary for database restore).

To make this procedure much quicker you can execute the following TL1 script

INIT-EQPT:TID:1-1-#-#-xcw:ctag:::resettype=contr;

INIT-EQPT:TID:1-1-#-#-xcp:ctag:::resettype=contr;

ED-STATE_EQPT:TID:system:ctag:::mcond=Y;

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





Removal of orphan OUCs and associated orphan cross connections requires special proceeding

If it should happen that OUCs and possibly associated cross connections are left over as orphans due to misbehavior in the ONNS domain, the following must be taken into consideration: (an orphan OUC in this respects means an OUC with the corresponding underlying NN connection not existing any more)

• While an orphan OUC is existing, probably associated still existing orphan cross connections cannot be removed in the usual way by setting their class to TRADITIONAL and removing them afterwards by traditional cross connection deletion. The command to change class to TRADITIONAL in this case will be rejected with error code “Status, Not in valid State, resources in use by Swiss”.

• Standard deletion of an orphan OUC (i.e. an OUC without existing associated NN connection) is not possible via CIT GUI.

Workaround:

In such a case first the OUC should be deleted using TL1 command DLT-OUC via TL1 cut-through. If after the OUC has been deleted this way there are still corresponding orphan cross connections left, these can be removed in the usual way by setting their class to TRADITIONAL and applying traditional cross connection deletion afterwards.

Problem 6.0 - nb42439 (nb42006)

Outdated ONNS connection state information after CTL or XC recovery or upgrade may be confusing and even result in deferred restoration

For a certain short time period following a CTL reboot, an XC reboot or a release upgrade in an ONNS NE, outdated connection state information may be reported for the existing ONNS connections the affected node is A-node of. This is due to the fact, that during this time period the actual state information for the ONNS connections is not known yet and outdated state information is assumed and reported as valid. This may lead to deferred restoration, if e.g. NO-IN state is wrongly assumed and reported as valid during this time for an ONNS connection and an internal failure affecting this connection occurs. In such a case restoration would start only after the actual valid state is determined.

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





Problem 6.0 - nb67241 (nb42503) (nb41141)

A CTL or XC reset or protection switch in an NE of an ONNS network while restorations are being performed may lead to side effects

The following effects may be observed if a CTL or XC reset or protection switch occurs in an NE, which is currently performing ONNS connection restorations (revertive or non-revertive) for connections this NE is A-node of. Such effects may especially occur, if restoration for many connections is running.

• Traffic of the ONNS connection is ok but remains in unexpected states and node lists show still the original (now failed) path.

• Restoration will be retried and remains in state CON&FAILED&WTORSTR with “Status, Edge port Used up” (for revertive restoration) or “Insufficient Network resources” (for non-revertive restoration).

• A following repair of the original path changes the state of a revertive restoration connection to CON&OK&WTORV without reverting the connection.

Workaround:

After such a situation has occurred, the following must be done:

• Check all ONNS connections the affected NE is A-node of. Affected ONNS connections (connection in status CON&OK&WTORV) have to be deleted. This will delete the original (failed) path.

• The restoration paths (but not shown in the ONNS data) has to be deleted cross connection by cross connection. First the cross connection class of every cross connection of these paths have to be changed from ONNS to traditional. Afterwards these cross connections have to be deleted.

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





Setup command for an M:N protected ONNS connection group with a large number of working connections may be answered with a denial, although setup in reality succeeds

In rare cases the following effect may be observed when setting up an M:N protected ONNS connection group with a large number of working connection (i.e. a number near to 64, which is the limit for Release 6.0 and Release 6.1 anyway):

• The setup command is denied with reason “E013 SSCF - Signalling Communication link Failure (or abort) caused path operation failure”

• However, the setup in reality succeeds, which is also indicated by corresponding REPT PTCHCHG notifications sent afterwards.

Workaround:

Check for REPT PTHCHG notifications or view paths to determine if the M:N group has been setup, when receiving denial with E013.

Problem 5.0 - nb32269/nb34115

No automatic removal of VCG tributaries from member list of VCGs, when deleting ONNS connections of a connection group

When ONNS connections of a connection group starting and/or ending in a VCG are deleted, the affected VCG tributaries are not automatically removed from the input and/or output member lists of the VCGs involved. This results in packet loss when removing VCG tributaries.It can also result in the following alarms popping up:

• THPUNEQ (unequipped) on affected VCG tributaries, where monitoring is enabled

• VCGLOPC or VCGLOTC (loss of partial capacity or loss of total capacity) on affected VCGs, if monitoring is enabled and LCAS is active and depending on whether only a part or all of the connections of a group are deleted

• VCGSSF (server signal fail) on affected VCGs, if monitoring is enabled and LCAS is not active.

Workaround:

Remove affected VCG tributaries manually from member lists (input and/or output member list) of VCGs via corresponding management system functions. First set input membership to disabled, then disable output membership before deleting the ONNS connection.Any alarms that have popped up as described above will clear after that.

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





Problem 4.1 - nb42687 (nb42641)

ONNS connection inconsistencies with traffic loss possible for restored connections after DB restore

If in a node of an ONNS network the database had to be restored, e.g. after its database had got lost, depending on the age of the database backup the following inconsistency might occur:ONNS connections, the node with restored database is A-, Z- or intermediate node of and that have been rerouted in the time interval between backup of the database and loss of the database, might after database restoration have lost traffic and be in “strange” connection states. Orphan cross connections might have been left over in affected nodes.Moreover, some of such connections may still be in state CON&OK, but may also have lost traffic. In such a case no restoration will be triggered autonomously either.

Workaround:

In order to avoid such situations, database backups should be performed in an ONNS network, whenever restoration actions have been recognized, as they should also be performed, when configuration actions as e.g. connection setups have been performed.

In case the situation described should have occurred, the following steps can be done:

1. Apply a reset to the XC pack of the node with restored database.

2. Identify all ONNS connections in the network being in connection states, that cannot be explained and having lost traffic, and delete these ONNS connections. These connections have to be remembered for step 5.

3. Identify all ONNS connections the node with restored database is A-node of and that are disturbed. This identification can be achieved by a TL1 retrieve with “detailed route” qualifier (RTRV-PATH:TID:snn:CTAG:::CONNECTIONID:detailroute=on;). All connections delivering incomplete detailed route information, i.e. delivering “NO REPLY” instead of detailed cross connection information are these connections wanted. Delete these ONNS connections. Again, these connections have to be remembered for step 5.

4. Remove remaining inconsistencies throughout the network by applying the following actions: Create a working list of nodes to be worked on by first including the node with restored database into the list.Then the following sequence must be applied until the list is empty:

• a. Take first node out of the list. In the following this node will be referred to as node under test.

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




• b. Identify all neighboring nodes to this node under test, referred to in the following as neighboring nodes.

• c. Apply neighbor DB audit actions to the node under test w.r.t. the neighboring nodes and to all neighboring nodes w.r.t. the node under test.

• d. Remove all inconsistent cross connections reported under c. by setting first the cross connection class to TRADITIONAL and deleting the cross connection by the standard traditional deletion mechanism.

• e. Append all neighboring nodes to the end of the working list that fulfill the following criteria:- Inconsistencies w.r.t. the node under test have been reported and removed by deleting cross connections in the neighboring node itself- The neighboring node is not yet in the working list

• f. Remove node under test from the working list and continue with a. until working list is empty.

5. Switch all ONNS connections anew that have been removed under steps 2 and 3.

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





Problem 3.0.1 - nb68955 (nb28509)

No alarm when SCN connectivity to an ONNS NE is lost

There is no alarm raised, when SCN (Signalling Communications Network) connectivity to another ONNS NE is lost. The SCN is critical to transport topology information and signalling messages for the setup, tear down and restoration of ONNS connections, defragmentation and neighbor audit and synchronization functions. ONNS functionality may be impaired due to an SCN failure without an obvious root cause (since no alarm is raised).

Workaround: • The operator shall engineer the SCN in a way that it is assured that

there are at least two SCN routes between any two ONNS nodes. Those routes shall be as diverse as possible to avoid single point of failure scenarios.

• For two ONNS neighbor nodes, which are connected by one or multiple iNNI ports, it is recommended, that the SCN is enabled for one iNNI port-pair (ensure that the port-pairs are configured consistently).

If the customer observes an abnormal ONNS behaviour,

• The TL1 error code might be evaluated and Operations System Engineering Guide looked up to check, whether it provides a hint about an SCN problem,

• the TL1 log of the ONNS GUI might be inspected to check for REPT NNEVT entries with message text “SIG Session Communications Loss” or “SIG Communications Session Re-established”.

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




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

UPSR/SNCP)

Problem 8.0.2 - nb71509

Combination of 4 fibre MS-SPRing TOP+EX with asymmetric ring feature is not yet supported

The combination of 4 fibre MS-SPRing TOP+EX with the asymmetric ring feature is not yet supported and must not be used. However, the system will not deny attempts to provision asymmetric spans or to transform a symmetric 4 fibre MS-SPRing TOP+EX ring into an asymmetric one.

Problem 8.0.2 - nb71508

Procedure for node addition and deletion not yet released for MS-SPRing TOP+EX

The common procedure for in-service node addition and deletion is not yet released for 4 fibre MS-SPRing TOP+EX rings. If such an in-service modification of an TOP+EX ring with LambdaUnite Release.8.0.20 software becomes necessary the LambdaUnite Technical Support should be consulted first.

Workaround:

Conversion to TOP-WO (requires de-provisioning of extra traffic), in-service node addition / deletion with TOP-WO, and conversion back to TOP+EX might be an option for applications where either extra traffic is not used yet or is allowed to be dropped during the ring size modification.

Problem 8.0.2 - nb69436

Drop and Continue crossconnections are not supported for 4 fibre MS-SPRing TOP+EX

Drop and continue crossconnections must not be used between the ports of an 4 fibre MS-SPRing TOP+EX group and also a TOP-WO group must not be converted into a TOP+EX group when such crossconnections are currently used.

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





Problem 8.0.2 - nb70391

LO crossconnections involving MS-SPRing TOP+EX ports might be problematic

The provisioning of lower order (LO) crossconnections to, from, and between the ports of an 4 fibre MS-SPRing TOP+EX group is not fully supported and might result in problems. For instance a CTL reboot has been observed when an LO crossconnection has been deleted using an LOXC/1 pack and involving a TOP+EX port. So it is currently not recommended to use LO crossconnections with ports of an 4 fibre MS-SPRing TOP+EX group. However, the system does not deny the attempt to provision such LO crossconnections.

Workaround:

• grooming of LO traffic in other nodes

• LO grooming in the same node, but usage of additional ports with fiber loops to be able to feed higher order (HO) traffic to the TOP+EX ports

Problem 8.0.2 - nb70333

Alarming for extra traffic tributaries might be incorrect during TOP+EX protection switches

When a protection switch is active for a service traffic tributary of an 4 fibre MS-SPRing with TOP+EX protocol and tributary monitoring is enabled for an extra traffic tributary with the same timeslot number as the service traffic tributary the alarming might be incorrect. When the related extra traffic circuit could not be reestablished e.g. due to competition with an service traffic circuit the alarming for the extra traffic tributary should indicate that an all-ones is being detected due to preemption (=squelching) of the extra traffic. This is currently not correctly supported and alarming for the extra traffic tributary might refer to the signal quality of the competing service traffic which is currently using the protection bandwidth. This is not in accordance with the functional for MS-SPRing as given by ITU-T G.841.

Workaround:

Do not rely on alarm information for extra traffic tributaries when a TOP+EX protection switch is active and the associated protection bandwidth is used by service traffic.

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




Problem 8.0.2 - nb70203

HO crossconnection loopbacks are not fully protected for MS-SPRing/BLSR

Higher order (HO) crossconnection loopbacks on worker tributaries of an MS-SPRing/BLSR protection group are not fully protected by MS-SPRing/BLSR. Dependent on whether automatic squelch map calculation is enabled or disabled and forced or non-forced HO crossconnection loopbacks are used the behavior will vary. The reason is that the ring entry and ring exit node information for these loopbacks is not fully supported. Either

• this information is not available at all (automatic squelch map calculation is disabled and non-forced loop)

or

• the related information of the underlying crossconnection is used instead.

Consequently especially for scenarios with multiple ring switches the squelching behavior might not be as expected. One effect is that the original circuit might be still protected if the node with the loop gets isolated, however no misconnections with other non-related circuits can occur.

Workaround:

Do not use HO loopbacks on worker tributaries of an MS-SPRing/BLSR protection group during MS-SPRing/BLSR switches of this group. If a loop is necessary for such protection scenarios an HO crossconnection with the same input and output tributary could be used instead.

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





Problem 8.0.2 - nb71545

Do not use fast script based crossconnection provisioning with 4 fibre MS-SPRing TOP+EX

For 4 fibre MS-SPRing TOP+EX it is essential that the view on the ring circuits is aligned among all ring nodes. For this purpose the crossconnection information is forwarded in the ring from node to node. To avoid effects caused by an overload of the related communication mechanisms it is recommended not to use script based ring circuit provisioning and also not crossconnection range commands which setup a large number of crossconnections at a single blow. In case that script based provisioning shall be used anyway a waiting time (5 seconds is proposed) should be inserted between each setup or deletion of a ring circuit. Provisioning of a bundle of crossconnections per node at a single blow would require longer waiting times between each crossconnection creation/deletion TL1 command. Normal operator driven setup or tear down of ring circuits via OMS will not cause a problem.

Workaround:

The alignment for a service traffic circuit can be checked as follows: The RTRV-CKT TL1 command is used with the tributary number of the circuit in all nodes of the circuit.

• The circuit is aligned if the parameter service restoration (srvcrest) indicates RINGSPAN for all involved nodes.

• If alignment for a service traffic circuit was not achieved the following procedure can be used to achieve alignment again: Toggle the parameter automatic squelch map calculation (asmc) in one of the nodes from ENABLE to DISABLE and back to ENABLE to initiate a re-distribution of the ring circuit information.

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




Problem 8.0.2 - nb71560

For 4 fibre MS-SPRing TOP+EX circuit provisioning during DCN unreachability of nodes is restricted

When one or several nodes of an 4 fibre MS-SPRing TOP+EX ring are not reachable from a DCN perspective, crossconnection information cannot be exchanged among the ring nodes. Therefore crossconnection provisioning operations have limited added value in this state as the information cannot become aligned among all nodes and thus there is no immediate protection for any new circuit setup in this state. Nevertheless new circuits can be setup which are not affected by the failures in the ring and so they will also be able to transport traffic. However, what must not be done in this state is that crossconnections are deleted as this can cause problems with ring circuit alignment later.

Workaround:

Do not perform crossconnection deletion operations when DCN communication to one node or to a segment of the ring is lost. The DCN communication has to be re-installed first if major reprovisioning operations including the deletion of existing crossconnections are necessary. For subsea applications this does not require the repair of the subsea cable, but to establish an additional DCN link (e.g. via LAN) with the unreachable landing station(s) is sufficient.

Problem 8.0.2 - nb71801

Do not use MS-SPRing/BLSR service to extra traffic crossconnections

Crossconnections between service traffic of an 4 fibre MS-SPRing TOP+EX ring and extra traffic of a 2 fibre MS-SPRing/BLSR ring are not supported. However, the system does not deny attempts to create such ring interconnections between service traffic and extra traffic. It has not been tested whether such interconnections work correctly, thus they must not be used.

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





Problem 8.0.2 - nb71843

Back-to-back combination of 4 fibre MS-SPRing TOP+EX with HO-SNCP/UPSR is not supported

Attempts to provision a back-to-back combination of 4 fibre MS-SPRing TOP+EX with HO (higher order) SNCP/UPSR are currently denied with SNVS, multiple added XCs for TOP. However, this combination of protection schemes is not a multiply added circuit and should be supported.

Workaround:

Use MS-SPRing TOP-WO instead of MS-SPRing TOP+EX when a back-to-back combination with HO-SNCP/UPSR is needed.

Problem 8.0.2 - nb71618

Deletion of an unidirectional LO MS-SPRing crossconnection might cause the CTL to reboot

The deletion of an unidirectional lower order (LO) crossconnection which is the last one for the associated higher order (HO) tributary in a port of an 4 fibre MS-SPRing TOP-WO group causes the CTL to reboot. After the reboot the crossconnection is still present. The problem is seen in a system with LOXC/1 pack if automatic squelch map calculation had been enabled when the crossconnection was initially created.

Workaround:

When this problem occurs the following can be done: • Change the ring entry/exit node information of the unidirectional

LO crossconnection just before deleting it

or

• convert the unidirectional LO crossconnection into a bidirectional one and delete the bidirectional one

or

• alternatively automatic squelch map calculation could be disabled when unidirectional LO crossconnections shall be used.

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




Problem 8.0.2 - nb71798

Result of TL1 command RTRV-SPANSW is not correct for circuits terminated on isolated nodes of 4 fibre MS-SPRing TOP+EX rings

When for an 4 fibre MS-SPRing TOP+EX ring a service traffic circuit is terminated on an isolated node (e.g. isolated by ring switches on both adjacent spans) and thus is not restorable, the result as given by the TL1 command RTRV-SPANSW is incorrect. Instead of indicating the circuit as affected by the switch request, but not switched or bridged, i.e. parameter Protection Signal Level = AFFNOSW (affected not switched) or AFFNOBR (affected not bridged), a value of NOTAFF (not affected) is returned. This is misleading as it indicates that the traffic is not affected by the ring requests, but indeed the traffic is lost.

Workaround:

Do not rely on the result of RTRV-SPANSW when a node is isolated.

Problem 8.0.1 - nb68994

Automatic squelch map calculation of LambdaUnite does not work in mixed MS SPRING with Metropolis ADM Universal nodes if service traffic circuits of rates VC4-4c or VC4-16c are used

In a mixed 2 fiber MS SPRING with nodes of MADM and LambdaUnite the automatic squelch map calculation feature does not work for circuits of rate VC4-4c or VC-4-16c. Consequently either automatic squelch map calculation has to be disabled in such rings with service traffic circuits of those rates or loca/locz provisioning in USER_OVERRIDE mode has to be used for service traffic cross connections of these rates. Not observing this rule can result in traffic outage when more than one ring switch request is active, e.g. during node addition or deletion.

Workaround:

See above. The safer variant is to disable automatic squelch map calculation when VC4-4c or VC4-16c service traffic circuits are used and to do manual ring entry / ring exit node (loca / locz) provisioning.

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





Problem 8.0.1 - nb68767

MS-SPRing/BLSR circuits with inhomogeneous provisioned cross connection rate are not handled as expected

When automatic squelch map calculation is enabled it should be supported for MS SPRING/BLSR (except: TOP+EX) that cross connections of different rates may sum up to the connected bandwidth of a circuit. This means e.g. that a STS-3 cross connection in one node is considered equivalent to 3 STS-1 cross connections for the equivalent tributaries in another node. This is currently not the case.

As a consequence of this non-support PIF alarms are raised, loca and locz are not available, and locastate/loczstate are indicated as AUTO-INVALID when a node detects during automatic squelch map calculation that in its neighbor node a cross connection of a different rate is provisioned.

For TOP+EX this behavior is as expected. For this application same rate cross connections in the neighbor nodes are a must i.e. in this case the behavior and the associated alarms are justified.

Problem 8.0.1 - nb66277

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.

Workaround:

Ignore transient Traffic Squelched alarms during node deletion if the deleted node has no other than HO through connections and while the Ring Protection Switch Suspended alarm is still active.

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




Problem 8.0.1 - nb67923

Forced LO loopback not handled correctly for an LO SNCP/UPSR on LOXC40

When in a system with LOXC40 a forced lower order (LO) loopback is applied to an input tributary of an LO path protected crossconnection (LO SNCP / LO UPSR), the behavior of the LO path protected crossconnection might be incorrect, i.e. an expected switch to the other input tributary might not occur. The correct behavior would be that the input tributary with the loop is considered in a Signal Fail fault status and that a switch to the other input tributary would occur unless the selector is forced to the side with the loop or the other input tributary has also a Signal Fail Fault Status. However, the behavior with respect to the looped signal is correct.

Workaround:

If it is necessary that the protected traffic survives when a forced LO loopback is applied to one of the inputs, a forced switch to the second input tributary has to be applied before the forced LO loopback for the first input tributary is initiated.

Problem 8.0.1 - nb67899

Forced LO loopback not recovered correctly for an LO SNCP/UPSR on LOXC40 after a full reset

When in a system with LOXC40 a forced lower order (LO) loopback is applied to an input tributary of an LO path protected crossconnection (LO SNCP / LO UPSR), the behavior of the LO path protected crossconnection might be incorrect, i.e. an expected switch to the other input tributary might not occur. Even if currently correct, the behavior might change after a recovery from a full reset and the selector output might show an Unequipped signal.

Workaround:

If it is necessary that the protected traffic survives when a forced LO loopback is applied to one of the inputs, a forced switch to the second input tributary has to be applied before the forced LO loopback for the first input tributary is initiated. This state will also be recovered again after a full reset of the LOXC40.

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






In-service change of HO SNCP type has unexpected effects on the switching criteria

When for a High Order (HO) Sub-Network Connection Protection (SNCP) the SNCP type is changed without deleting the protection group, the system does not use the expected set of switching criteria. The SNCP type provided via ED-PROTN-GRP is rather inverted from SNC/I into SNC/N and vice versa. Example: An HO path protection group which had been created as HO SNC/I shall be modified into an HO SNC/N group (by using the ED-PROTN-GRP TL1 command). The modified group should now start to react on Signal Degrade due to B3 errors, but it does not. It rather still uses the SNC/I switching criteria. However, when it is now tried to change it back to HO-SNC/I it will start to use the switching criteria for HO-SNC/N.

Workaround:

Delete the protection group of the old SNCP type and create a new protection group of the new SNCP type. If this has to be done in-service, the SNCP can be converted into an unprotected cross-connection and than converted back into an SNCP with the desired SNCP type (CNVT-CCT TL1 command) to avoid traffic loss.

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





1+1 APS in bidirectional operation does not fall back to unidirectional operation

When in bidirectional operation of linear 1+1 APS the protocol indicates via K2[6..8] that the other end is provisioned for unidirectional operation, the bidirectional end should fall back to unidirectional operation. This is currently not the case. Instead the protocol will not complete as K-byte requests are not acknowledged by the unidirectional end. Consequently the system might return wrong information for the selector position, might not set the abnormal condition (e.g. in case of a Forced switch). However, the misprovisioning is indicated by a PAMOPER alarm and can be corrected.

Workaround:

Make always sure that both ends of an MSP/ APS protected link are provisioned for the same operation mode (unidirectional or bidirectional). If a PAMOPER alarm occurs check the protection group at both ends for correct configuration.

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






TID changes might not correctly be recognized in a mixed DMX/LambdaUnite 2 fibre BLSR

If two or more TIDs are changed in a mixed BLSR ring of LambdaUnite and DMX nodes, where “Automatic Squelch Map Calculation” is NOT enabled, it might occur that LambdaUnite nodes fall back to the previous TID string for the ring entry node / ring exit node (=loca/locz) parameters.

If the loca/locz information is incorrect anywhere in the ring, wrong squelching could occur during ring switches.

Workaround:

If wrong TIDs are in the ring this can be checked as follows:

• For DMX nodes a “Squelch Map Inconsistent” (SMI) alarm will raised

• For LambdaUnite nodes by using RTRV-CRS commands

If outdated TIDs are found during the proposed checks then the following procedure can be used in the node showing the wrong TID(s):

1. Disable “Automatic Ring Discovery”.

2. Enable “Automatic Ring Discovery” again.

3. Enable additional “Automatic Squelch Map Calculation”.

4. Wait for some minutes to make sure that the information has been communicated in the ring

5. Disable “Automatic Squelch Map Calculation” again.

6. Re-check the TIDs by using RTRV-CRS as described above or make sure that DMX´s SMI alarms have been cleared.

However, it is very unlikely to disable “Automatic Squelch Map Calculation”, if this function is available for all NEs in the ring.


Deletion of MSP not denied while test access session exists

If an MSP protection group is deleted, while test access sessions exist at tributaries on ports involved in the MSP, then the command is not denied.

Workaround:

First disable the “Test Access Session” before deleting an MSP protection group.

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





4-fibre MS-SPRing/BLSR: traffic hit on worker fibre repair

A ring switching node of an 4-fibre MS-SPRing/BLSR with a failed protection line should not drop a ring switch for the same span as due to the missing short path signalling it cannot decide whether the ring switch is still requested by its neighbor node. This principle is not followed. As a consequence a LambdaUnite node with an Signal Fail-Ring (SF-R) due to a failed worker and protection line will start to transiently signal Lockout of Protection-Span (LP-S) also on the long path when the worker line failure of the affected span clears and the protection line is still failed. This behaviour will cause a short traffic hit (about 10 ms) when for a bidirectional fiber cut of both worker and protection fibres, the worker fibre in one of the two directions is repaired first as the ring switch is transiently dropped and then re-established. A transient traffic hit will also occur when external Force to Protection-Ring (FS-R) switch commands are used for the two adjacent nodes of a span and the FS-R command is cleared for one of the nodes with the incoming short path protection line being failed for this node.

Workaround:

When repairing a bidirectional SF-R in an 4-fibre MS-SPRing/BLSR the protection fibres should be repaired before the worker fibres. An alternative is to fix the ring switch by applying an FS-R switch for the affected span before beginning to repair the fibres and to clear the FS-R switch again when the repair actions are completed.An external ring switch command should not be cleared when the short path protection line for this node is failed and a ring switch is still also requested by the other end of the span (e.g. due to a second external ring switch command).

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





0Area EquipmentProtection

Problem 8.0.1 - nb68003

XC640 Equipment protection switch when changing signal structure of 10G-port of GE10PL10

When changing the signal structure of the 10GbE VCG-port of a GE10PL1 from STS1-based virtual concatenation mode to STS-3c-based mode or vice versa an unexpected XC equipment protection switch may occur in NEs equipped with XC640. The probability of this switch to occur is about 1%.


LOXC40 Equipment Protection Group not operational for 30 seconds after creation

When creating an LOXC40 Equipment Protection Group the state of this group immediately goes to No Request (NR) after having processed the TL1-command to create the group. However, the protection LOXC40-pack needs additional 30 seconds to process the configuration data until it is fully operational. If during these 30 seconds any equipment protection switch would happen (either manual or forced by the operator or autonomous) LO-traffic would be completely lost for this period of time. Traffic is restored as soon as the protection LOXC40 has processed its configuration data.

Workaround:

Wait at least 30 seconds after creating an LOXC40 equipment protection group before applying a manual or forced switch to the protection pack.

Problem 7.0.3 - nb70721

Incorrect message displayed when CIT protection switch window opened from the Fault-->Protection Switch

The operator finds unnecessary message dialogs being popped-up when Fault-->Protectection Switch option is chosen.Workaround:

The Protection Switch info can be viewed by right clicking the pack and choosing the protection switch option.

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




0Area Fault/AlarmManagement


A wrong degraded Alarm raised at the LOXC40G unit in the case of LOS at the corresponding SDH port

In the case that a LOS condition is present at a SDH port the corresponding higher order path termination function on the Lower Order Cross-connect 40G (LOXC40G) will raise a wrong degraded alarm. This alarm of the termination in the case of a LOS condition is wrong and should be ignored.

The correct alarm condition is retrievable from the NIM.

Workaround:

Set the degraded alarming of the path-termination function to “Not Reported” and enable degraded alarm from the HO NIM.


A generic AIS condition of the OTN layer of the OP10XTT generates an AIS-P alarm instead of LOF

In the case that a signal Fail condition on the OTN layer of the OP10XTT due to a LOS-P or some other trail signal fail condition is present, Generic AIS is inserted downstream. This should trigger LOF alarm on the SDH/SONET client port. Instead of them only an AIS-P alarm will raised.

Problem 7.0.2 - nb57036

On a DS3 port an Application Mismatch is not alarmed in case that a C-Bit Parity structure is applied to a port where M23 is configured

If a DS3 port is configured for M23 application and a frame format for C-bit Parity will be applied/received, no alarm will be raised. An Application Identification Mismatch alarm would be expected. Remark: LOF would be raised correctly in the case an unframed signal is applied at the port.

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






Incorrect and incomplete handling of lower order alarms during VC-4 TIM

If for a substructured VC-4 a higher order trace identifier mismatch (TIM) is detected and the consequent action of all-ones insertion is enabled there should be no additional lower order path alarms reported for the associated TUG-3s.However, this is only true for the first TUG-3 while for the 2nd and 3rd TUG-3 lower order alarms such as e.g. Unequipped may occur. Nevertheless not only the first TUG-3, but also the contents of the 2nd and 3rd TUG-3 are correctly overwritten with all-ones. On the other hand if the all-ones insertion for higher order TIM is disabled, additionally lower order path alarms should be raised if there are any. This is currently not the case for the first TUG-3, but only for the 2nd and 3rd TUG-3.

Workaround:

Ignore lower order path alarms from the 2nd and 3rd TUG-3 of a substructured VC-4 if a higher order defect as TIM causes all-ones insertion. Be aware that lower order path alarms will not be raised for the 1st TUG-3 when a higher order TIM with disabled all-ones insertion occurs.

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





Configuration for TIM detection for HO path termination as well as LO non-intrusive monitoring have strange effects (only for LOXC/1)

The following does only apply for LOXC/1 usage:

1. HO Trace Identifier Mismatch (TIM) detection/monitoring: The TIM detection/monitoring settings for a high order path termination function (HO PTF) which is substructured to low order (LO) traffic being involved as input of a LO path protection may get ignored if the TIM detection/monitoring of the other involved HO PTF has been set later and to a different value.

2. LO TIM detection/monitoring: Changing the TIM detection/monitoring settings for a low order non-intrusive monitor (LO NIM) being involved as input of an LO path protection has no effect if this NIM belongs to the protection leg. Only worker leg configurations take effect.

Issue 1) is applicable to all types of LO SNCP/UPSR if consequent action handling upon TIM detection has been enabled (this is the default).

Issue 2) takes only effect for LO SNC/N.

If HO PTF as well as LO NIM TIM detection/monitoring settings are different for the various legs of LO path protections, then there is a high chance of an unexpected path protection switch during the upgrade to Release.8.0.20.

Workaround:

Set all LO cross-connection related HO PTF and LO NIM settings for TIM detection/monitoring to the same value before upgrading the system to Release.8.0.20 (to avoid unexpected path protection switches). With Release.8.0.20 adapt all newly created HO PTF and LO NIM entities to the same value. Do not change these values until an upgrade has been offered to a version which fully implements the problem resolution.


Switch to Protection EP51 or EP155 Unit leads to Port Alarms raised as NSA if the Enhanced Mode of SA/NSA Alarm Classification Functionality is enabled

If service affecting port alarms are present on a protected EP51 circuit pack or a protected EP155 circuit pack and the enhanced mode of SA/NSA alarm classification functionality is enabled, a switch to the protection unit will lead to the effect that the service state of these alarms will change to non-service affecting.

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





Problem 4.0 - nb58711/nb58712 (nb23154)

The non standard SRM alarm is not raised for pipe mode for certain port units / other alarms are raised instead

Signal Rate Mismatch (SRM) alarming for incoming rate mismatch is supported only on the following port units:

• OP10G KFA6, KFA7, KFA14

• OP10GPar1XFP, Par2XFP

• OP10/XTT (extreme with tunable laser)

• OP2G5 KFA12

• OP2G5Par8

SRM alarm is not raised for incoming rate mismatch, and also no other alarms are raised instead of SRM on the following port units:

• OP10GDD (slide in modules)

• OP10GOLS/PWDM

• OP10GXT (old extreme)

• OP2G5 1.3LR4, 1.5LR4

• OP2G5MOD

• OP2G5Par4

• all OP40

• all packs with lower bandwidth than STM16:

• OPLB/OP622/155

• EP155

• EP51

• OPT2G5

For all kind of port units the alarms “Excessive Bit Error Ratio” and “Degraded Signal” are raised instead of SRM against the incoming stream for the port operating in pipe mode only in the following case:The cut out bandwidth of such overlapping pipe is outgoing on a port and entering an LambdaUnite system.

Workaround: When using adaptive mode make sure the configured and received signal rates match to each other.

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




Problem 3.0.1 - nb11321

SRM defect not supported

The SRM (Signal Rate Mismatch) defect is a non-standard defect defined on path level in context of adaptive pointer processing. This defect is not supported for the following port units in pipe mode:

• OP10GDD (slide in modules)

• OP10GOLS/PWDM

• OP10GXT (old extreme)

• OP2G5 1.3LR4, 1.5LR4

• OP2G5MOD

• OP2G5Par4

• all OP40

• all packs with lower bandwidth than STM16:

• OPLB/OP622/155

• EP155

• EP51

• OPT2G5

Workaround: • In pipe mode ignore SRM failure if reported for a port unit listed

above.

• In non-pipe-mode ignore SRM and also additional alarms like Trace identifier Mismatch (TIM) alarm if the path is not under trace identifier supervision.

• Operate the path under full trace identifier supervision.AIS-inserted-on-TIM is to be enabled AND correct trail identifier has to be inserted.

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





0Area PerformanceMonitoring

Problem 8.0.2 - nb71845

Performance Monitoring Data of an LOXC PTF can not be retrieved via CIT

The CIT shall support the retrieval of Performance Monitoring Counters of a Path Termination Function (PTF) belonging to a LOXC connection. This is not possible in this release.

Workaround:

Use Cut Through to get the information.


Maximum values of TCA profiles are not possible

For the following Threshold Crossing Alert (TCA) profiles the maximum value is not 4294967295 (as described in the Operations System Engineering Guide) but only 2147483648:

• Day threshold for PDE bin for GE (daypdege)

• Day reset threshold for PDE bin for GE (daytrpdege)

• Day threshold for PDE bin for VCG (daypdevcg)

• Day reset threshold for PDE bin for VCG (dayrtrpdevcg)

• Day threshold for MS_N_BBE and MS_F_BBE for STM-1 bin (daymsbbestm1)

• Day reset threshold for MS_N_BBE and MS_F_BBE for STM-1 bin (dayrtrmsbbestm1)









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




• 15-min threshold for MS_N_BBE and MS_F_BBE for STM-64 bin (qhmsbbestm64)

• 15-min reset threshold for MS_N_BBE and MS_F_BBE for STM-64 bin (qhrtrmsbbestm64)

• 15-min threshold for MS_N_BBE and MS_F_BBE for STM-256 bin (qhmsbbestm256)

• 15-min reset threshold for MS_N_BBE and MS_F_BBE for STM-256 bin (qhrtrmsbbestm256)

• Day threshold for MS-N-FECC bin for STM-64 (daymsnfeccstm64)

• Day reset threshold for MS-N-FECC bin for STM-64 (dayrtrmsnfeccstm64)

• Day threshold for MS-N-FECC bin for STM-256 (daymsnfeccstm256)

• Day reset threshold for MS-N-FECC bin for STM-256 (dayrtrmsnfeccstm256)

• 15-minute threshold for MS-N-FECC bin for STM-64 (qhmsnfeccstm64)

• 15-minute reset threshold for MS-N-FECC bin for STM-64 (qhrtrmsnfeccstm64)

• 15-minute threshold for MS-N-FECC bin for STM-256 (qhmsnfeccstm256)

• 15-minute reset threshold for MS-N-FECC bin for STM-256 (qhrtrmsnfeccstm256)

• Day threshold for CV-S bin of OC-3 (daycvsoc3)

• Day threshold for CV-S bin for OC-12 (daycvsoc12)




• Day threshold for CV-L bin and CV-LFE for OC-3 (daycvloc3)

• Day threshold for CV-L bin and CV-LFE for OC-12 (daycvloc12)

• Day threshold for CV-L and CV-LFE bin for OC-48 (daycvloc48)



• 15-minute threshold for CV-L and CV-LFE bin for OC-192 (qhcvloc192)

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





• 15-minute threshold for CV-L and CV-LFE bin for OC-768 (qhcvloc768)

• Day threshold for FECC-L bin for OC-192 (dayfeccloc192)

• Day threshold for FECC-L bin for OC-768 (dayfeccloc768)

• 15-minute threshold for FECC-L bin for OC-192 (qhfeccloc192)

• 15-minute threshold for FECC-L bin for OC-768 (qhfeccloc768)

Problem 7.0.2 - nb56255

DS3 Path Level egress Performance Monitoring counters do not work for M23 and C-bit Parity Mode

DS3 path level egress performance monitoring counters do not work for both relevant applications: M23 and C-bit parity mode. For the “clear channel” mode this issue does not apply since no path level monitoring functions are present.

Workaround: Due to the missing egress performance monitoring functionality on path level, only the server layer STS-1 per DS3 signal can be supervised. If this one does not report any errors, the assumption that also the relevant DS3 client signal is still intact might be valid. Alternatively also the far end monitoring capabilities could be used which is critical because the information received comes then from outside of the providers network. Meaning the applicability is not ensured in all cases.

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





Reset of performance monitoring (PM) current bins is not supported

The system does not allow to reset the counter values of a current bin.

Workaround: Either

• wait for the begin of a new measurement period as this will reset the counters

or

• note down the current values prior to performing a measurement and calculate the difference of the counters after the measurement manually

or

• disable and then enable the package(s) for which the register init is wanted.

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





0Area SecurityManagement


Established sessions of users, which are deleted, are not terminated

If an user is deleted from the system (TL1 command DLT-USER-SECU), the established sessions for the deleted user are not terminated. This can lead to a security gap, because Security Administrators may expect that deleted users can not work with the system any more.

Workaround: After deletion of an user, check if there are user sessions established for this user and terminate the sessions manually (TL1 commandCANC-USER-SECU).

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




0Area Gigabit EtherNET Problem 8.0.2 - nb71527

Unexpected THPUNEQ alarm when reconfiguring GE10PL1 from 1GbE mode to 10GbE mode

When reconfiguring a GE10PL1 pack from 1GbE mode to 10GbE mode by removing all cross-connections, de-provisioning the SFPs, and provisioning the XFP and then setting up a VC4-64c cross-connection from/to the 10GbE WAN-port traffic is established as expected. However, a THPUNEQ alarm is raised and when retrieving the path trail state AIS is reported. After applying a Controller Reset to the pack the THPUNEQ alarm is cleared and the path trail state is reported correctly.

Workaround:

When switching from 10G-mode to 1G-mode or vice versa apply a Full Reset to the GE10PL1 pack after deleting the configuration, i.e. after de-provisioning the XFP/SFPs.

Problem 8.0.1 - nb68750

Periodic Reboot of GE1 in unidirectional applications if flow control is disabled in unused direction

When a GE1 is used for unidirectional applications, e.g. video broadcast, and flow control is disabled at the LAN port of the GE1 which receives traffic from the WAN-port and transmits it over the LAN-port, then spontaneous reboots may happen. Those reboots are caused by Ethernet frames received at this LAN-port, which cannot be forwarded further as this direction is unused.

Workaround:

Always enable flow control at the LAN port of the transmitting GE1 or make sure that this port never receives Ethernet frames.

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





Problem 8.0.1 - nb68394

Small packet loss when enabling LCAS on a link between GE1 and GE10PL1

On an Ethernet link between a GE1 and a GE10PL1 with LCAS being disabled on both sides a small packet loss is observed when enabling LCAS on GE1 first. When enabling LCAS on GE10PL1 first no packet loss is observed. The packet loss happens only in direction from GE10PL1 to GE1, the other direction shows no packet loss. On a connection with full WAN-bandwidth (7 VC4) and a bandwidth usage of 95% with a framesize of 1000 byte, 21 frames were lost in the direction from GE10PL1 to GE1 when enabling LCAS on GE1.

Workaround:

When LCAS shall be enabled on a non-LCAS link between GE10PL1 and GE1, then enable LCAS at the GE10PL1 first before enabling it at GE1.

Problem 8.0.1 - nb68090

Unexpected PLCT Alarm when enabling LCAS on a working 10GbE link

When a 10GbE WAN-link is running with LCAS disabled and then LCAS is enabled on both sides, an unexpected Partial Loss of Capacity Transmitter (VCGPLCT) alarm may occur at both ends of the link. The alarms are never cleared again. This issue does not always occur. Further circumstances leading to this unexpected alarm are unknown.

Workaround:

• Hide VCGPLCT alarm via the Alarm Severity Assignment Profile (ASAP) settings and rely on Partial Loss of Capacity Receiver (VCGPLCR) for detecting partial loss of capacity

or

• apply a full reset to the GE10PL1 packs (which is traffic affecting).

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




Problem 8.0.1 - nb68232

Unexpected Alarming in case of failed multiframe alignment on a VCG Tributary of GE10PL1

When a VCG tributary of a GE10PL1 is in a state where it cannot align the multiframe structure based on the information contained in the received H4-bytes, the VCG tributary is removed from the VCG and a Partial Loss of Capacity (PLCR) alarm is raised as expected. However, to identify the failed VCG tributary the membership status must be evaluated. For the VCG tributary itself neither a Loss of Multiframe (LOM) nor a Server Signal Fail (SSF) alarm is raised. In addition an unexpected VCG Failure of Protocol - Receiver (VCGFOPR) alarm is raised.

Workaround:

Ignore the VCGFOPR alarm; check the output membership status of the VCG to identify the failed member.

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 3 to 8 seconds has been observed.

• When using the 10GbE port, a traffic hit with a duration below 1 second 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.

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






GE10PL1: Frames with bad FCS received at the WAN port are forwarded to the LAN port instead of being discarded

When Ethernet frames are received at the WAN port of a GE10PL1 which have a bad Frame Check Sequence (FCS), e.g. due to a degraded server signal, such frames should be discarded and counted as errored frames via the Performance Monitoring counter for EDFE of the LAN port. However, such frames are not discarded and not counted. Instead they are forwarded unchanged to the LAN port and transmitted on the fiber. The next receiving station will then detect the FCS-error and discard the frames.

Workaround:

As a consequence it is necessary to take a look at the SDH/SONET Performance Monitoring counters of the WAN-link in order to find out whether the WAN-segment or the LAN-segment of a link is disturbed.


GE10PL1: VCG member status only reflects provisioning status

When retrieving the VCG membership status from VCG tributaries on GE10PL1 while LCAS is disabled either ACTIVE for enabled members or NA for disabled members is returned regardless of their current state. This matches the required behavior at the source side of the GFP trail. However, at the sink side the required behavior would be to also report a state FAILED if the respective tributary has a pending Loss of Pointer (LOP), Unequipped (UNEQ), Loss of Multiframe (LOM) or Payload Mismatch (PLM) condition. This behavior exceeds the requirements from the standards but provides a more accurate picture of the current status of a VCG.

Workaround:

The operator has to determine whether a VCG member is in a good state or is in failed state from the alarms related to the VCG tributaries.

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




Problem 7.0.2 - nb57095

No Ethernet Traffic if LCAS is enabled in uni-directional configurations

When Ethernet traffic shall be transported uni-directional, i.e. there is no connection from the receiving Virtual Concatenation Group (VCG) termination side to the sending side, and Link Capacity Adjustment Scheme (LCAS) is enabled at the sending side then traffic is completely blocked.

This may occur

• when setting up such a unidirectional configuration initially

• or after having set up such a configuration with LCAS being disabled and then enabling LCAS by accident or intentionally at the sending side.

The expected behavior is that the LCAS sender continues normally and sends traffic and LCAS information. The fact that this VCG does not receive any feedback in the reverse direction should not break traffic.

Workaround:

Disable membership of all members at the source side, then disable LCAS and enable membership again. Alternative disable LCAS at the sending side and apply a Controller Reset to the GE1 pack acting as sender.


GE1 pack: LOA and LOF alarm do not work properly when the differential delay exceeds 32ms / framing of GFP frames is incorrect

In case the differential delay for components of a Virtual Concatenation Group (VCG) is more than 32 msec, the traffic is lost (as expected), but no Loss of Alignment (LOA) alarm is shown to indicate this.No Generic Framing Procedure (GFP) Loss of Frame (LOF) alarm is raised when the framing of the GFP frames is incorrect. In this case ethernet traffic is disabled, but no alarm is raised.Note: Raising of LOA and LOF only works as expected when operating on SONET mode and using all 21 STS1 within a VCG.

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




4 New Installation and Upgrade Procedures

4 - 1Lucent Technologies - ProprietaryLambdaUnite® MultiService Switch (MSS),

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

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

Contents 0

General 4 - 4


Software upgrade concepts 4 - 4

Database backup concepts 4 - 4

Upgrade from Release.7.0.2/Release.7.0.3 to Release.8.0.20 4 - 4

Upgrade from Release.8.0.1 to Release.8.0.20 4 - 4

Upgrade path survey 4 - 6

New Installation and Software Upgrade 4 - 7

Overview 4 - 7

To perform an initial NE software download 4 - 8

Purpose 4 - 8

Safety precautions 4 - 8

Before you begin 4 - 8

Instructions 4 - 9

NE Software Upgrade 4 - 13

To upgrade software to a new release 4 - 13

When to use 4 - 13


Precondition for Upgrade 4 - 14

Further Upgrade related issues/procedures 4 - 15

See Notice on first pageRelease.8.0.20 Software Release DescriptionIssue 1.1, March 2007

New Installation and Upgrade Procedures

Prepare CompactFlash® card for fall back solution 4 - 16

Upgrade-preconditions for the Network Element 4 - 17

Upgrade-preconditions for the whole network 4 - 17

Instructions 4 - 20

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

When to use 4 - 24

Download limitations 4 - 24

Related information 4 - 24


Instructions 4 - 25

To activate an NE software generic 4 - 30

When to use 4 - 30


Instructions 4 - 31

To check for successful NE software upgrade 4 - 34

When to use 4 - 34


Instructions 4 - 34

To solve NE software upgrade problems 4 - 36

When to use 4 - 36

Instructions 4 - 36

Trouble shooting procedure A 4 - 38

Trouble shooting procedure B 4 - 39

Trouble shooting procedure C 4 - 40

Trouble shooting procedure D 4 - 42

Trouble shooting procedure E 4 - 44

To retrieve NE software generic information 4 - 46

When to use 4 - 46

NE active software 4 - 46

Instructions 4 - 46

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

NE software display window 4 - 47

Elements of the NE software display window 4 - 47

Database backup 4 - 49

Overview 4 - 49

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




New Installation and Upgrade Procedures

Purpose 4 - 49

To limit the number of saved backups 4 - 49

Purpose 4 - 49


Instructions 4 - 50

Manually backup database to the WaveStar® CIT 4 - 51

When to use 4 - 51


Related information 4 - 51


Instructions 4 - 52

To retrieve NE database information 4 - 55

When to use 4 - 55

Instructions 4 - 55

Supporting information for Retrieving NE database information 4 - 56

Elements of the Database Info window 4 - 56

To restore a database to a network element 4 - 58

Purpose 4 - 58



Instructions 4 - 59

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



New Installation and Upgrade ProceduresGeneral

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

General 0

Known Problems When detecting problems check chapter 3 “Known Problems” of this document for workarounds.

Software upgrade concepts The “Software upgrade concepts” for further information are described in the LambdaUnite®.MultiService.Switch.(MSS) User Operations Guide.

The WaveStar®.CIT only CD-ROM (109649442) does not contain the LambdaUnite®.MSS Network Element (NE) Software Version 08.00.20, but only the WaveStar®.CIT (Craft Interface Terminal) Software Release.16.02.00 Build.1445.

Database backup concepts The “database backup concepts” for further information are described in the LambdaUnite®.MultiService.Switch.(MSS) User Operations Guide.

Upgrade fromRelease.7.0.2/Release.7.0.3

to Release.8.0.20

Upgrade Software for upgrading an existing LambdaUnite®.MSS Release.7.0.2/Release.7.0.3 system to LambdaUnite®.MSS Release.8.0.20, consists of two parts:

• LambdaUnite®.MSS Network Element (NE) Software Version 08.00.20

• WaveStar®.CIT (Craft Interface Terminal) Software Release.16.02.00 Build.1445

delivered on a CD-ROM (Comcode 109649228).

The software for the 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 Pentium-III Microsoft® Windows® 2000 or 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 from Release.8.0.1to Release.8.0.20

Upgrade Software for upgrading an existing LambdaUnite®.MSS Release.8.0.1 system to LambdaUnite®.MSS Release.8.0.20, consists of two parts:

• LambdaUnite®.MSS Network Element (NE) Software Version 08.00.20

• WaveStar®.CIT (Craft Interface Terminal) Software Release.16.02.00 Build.1445

delivered on a CD-ROM (Comcode 109649228).

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




New Installation and Upgrade ProceduresGeneral

The software for the 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 Pentium-III Microsoft® Windows® 2000 or 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.

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



New Installation and Upgrade ProceduresUpgrade path survey

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

Upgrade path survey 0

R6.0.0109494666

Upgrade: R5.0.2->R6.0SW: 109494658License: 109494641

R7.0 LA109572396

Upgrade: R6.1.x->R7.0SW: 109572404License: 109572412

R6.1.1109568949

Upgrade: R6.0x->R6.1.xSW: 109537753License: 109537761

Upgrade: R5.0.x->R6.1.1SW: 109556001License: 109555995

Legend:Standard upgrade pathAlternative upgrade paths

From5.0.3

From5.0.2

From5.0.x

R6.0.1109597856

Upgrade: R7.0->R7.0.2SW: 109598912

Upgrade: R6.0.0->R6.0.1SW: 109597872

R7.0.2109598896.

Upgrade: R7.x->R7.0.4SW: 109645663

R8.0.20109649178

Upgrade: to R8.0.20SW: 109649228License: 109649236Upgrade: R6.1.1->R7.0.2

SW: 109598904License: 109572412 R7.0.4

109645655

R8.0.1109618082

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




New Installation and Upgrade ProceduresNew Installation and Software Upgrade

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

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 LambdaUnite®.MSS.

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



New Installation and Upgrade ProceduresTo perform an initial NE software download

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

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 109649178). 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 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 109649178).

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® 2000 / 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.

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

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.

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




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.

Continue with Step 19.

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

11. Manual Installation: Insert the 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 --> 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® 2000 / 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

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




New Installation and Upgrade ProceduresNE Software Upgrade

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

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 LambdaUnite®.MSS software from a former release to Release.8.0.20.

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

2. Acquire the CD-ROM that contains the new generic/version of the 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.

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




Precondition for Upgrade Preconditions for the Network Element

Additional precondition for the NE, which will be upgraded from Release.7.0.2/Release.7.0.3/Release.8.0.1 to Release.8.0.20:

Important: The following actions have to be taken prior to per-forming the upgrade from Release.7.0.2/Release.7.0.3/Release.8.0.1 to Release.8.0.20.

• The following applies to LO cross-connections, which are involved in an LO SNCP/UPSR: Before starting the upgrade, set all LO cross-connection related HO PTF and LO NIM settings for TIM detection/monitoring to the same value before upgrading the system to Release.8.0.20. This is necessary to avoid unexpected path protection switches during upgrade. For details see Problem 7.0 - nb49879 of chapter 3 “Known Problems” of this document.

Additional precondition for the NE, which will be upgraded from Release.7.0.2/Release.7.0.3 to Release.8.0.20:

Important: The following actions have to be taken prior to per-forming the upgrade from Release.7.0.2/Release.7.0.3 to Release.8.0.20.

• Before the upgrade of an ONNS domain to Release.8.0.20 is performed, it shall be checked, whether in this domain there is a group of unidirectional ONNS connections of protection type MBYN configured. For each such group identified the following procedure is recommended during the network upgrade:

• Delete the unidirectional MBYN group before the upgrade is started and set it up again as bidirectional MBYN group.

Background: In case such an unidirectional MBYN group has been upgraded, protection of this group is not working afterwards, unless the group has been deleted and setup a new as bidirectional MBYN group.This action is necessary in order to avoid database inconsistencies in Release.8.0.20, as with Release.8.0.20 unidirectional MBYN groups are not supported any more.

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





• Before the upgrade of an ONNS domain to Release.8.0.20 is performed, it shall be checked, whether in any of the affected nodes the following scenario is given:

• An bidirectional ONNS to UPSR/SNCP Construct (OUC) is configured, with two separate unidirectional ONNS connec-tions underlying this OUC instead of one bidirectional ONNS connection.

For each such scenario identified the following action shall be per-formed, before performing the network upgrade:

• Delete this bidirectional OUC and add two new independent OUCs on the corresponding EDGE tributaries, one unidirec-tional add OUC and one unidirectional drop OUC, i.e. a sepa-rate OUC for each underlying unidirectional ONNS connection.

• If such an action has been forgotten to be done before the upgrade, it is still possible to do it after the upgrade is finished, but the recommendation is to do it before.

Background: This action is necessary in order to avoid database inconsistencies in Release.8.0.20, as starting with this release bidirectional OUCs on top of unidirectional ONNS connections are not supported any more.

Further Upgrade relatedissues/procedures

Network Element

Important: Additional issues/procedures specific for the upgrade from Release.7.0.2/Release.7.0.3/Release.8.0.1 to Release.8.0.20:

• The following effect can be seen after an upgrade of an ONNS NE:For a certain short time period outdated connection state information may be reported for the existing ONNS connections the affected node is A-node of.For details see Problem 6.0 - nb42439 (nb42006) of chapter 3 “Known Problems” of this document.

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




Prepare CompactFlash®

card for fall back solutionPrepare 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 LambdaUnite®.MSS Installation Guide.

Depending on the application a CompactFlash® card of the following size has to be used:

• 256-MByte (for traditional applications with CTL/- or CTL/4T).

• 512-MByte (for traditional and ONNS applications with CTL/2 or CTL/4S).

• 1-GByte (for traditional applications with CTL/3T, or traditional and ONNS applications with CTL/3S).

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 forthe Network Element

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

• The upgrade from Release.8.0.1 to Release.8.0.20 is not supported for Network Elements equipped with CTL/- and/or CTL/4T.

• Do not upgrade a Network Element equipped with CTL/2 with Series Number S2:4 to Release.8.0.20 unless the primary boot version is modified. For this primary boot version modification a Product Change Notification and an Alcatel-Lucent Alert will be released soon.An upgrade to Release.8.0.20 would lead to a endless reboot when the primary boot version is not modified!

• The LambdaUnite®.MSS NE is running a software prior to the current release.

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

• For NEs with ONNS functionality enabled ensure that all EDGE and iNNI ports are in error free condition.

• For NEs with ONNS functionality enabled ensure that for all paths the Connection Status must be CON&OK or CON&NOIN.

Upgrade-preconditions forthe whole network

The following preconditions have to be fulfilled by the other LambdaUnite®.MSS NEs, which are included in the same network:

• A checklist of all NSAP addresses of the LambdaUnite®.MSS NEs, to be updated in the network, must exist

• During the upgrade all 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.

• To ensure proper operation of the ONNS functionality the complete ONNS network must be upgraded to the new release.

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




• The ONNS functionality is fully available only after all NEs of the ONNS network have been successfully upgraded to the new release and the new ONNS functionality is enabled for all NEs of the whole ONNS network.

• For an upgrade with ONNS functionality enabled the following has to be ensured: During the upgrade procedure, starting with the database backup of the first NE in the ONNS network until the complete error free start up of the new release of the last NE in the ONNS network and until the new ONNS functionality is enabled for all NEs of the whole ONNS network, no

– ONNS relevant provisioning (such as port parameters provi-sioning, path setup, teardown and modifications)

– link defragmentation

shall be performed in any part of the ONNS network.

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 LambdaUnite®.MSS software from a former release to Release.8.0.20:

• Software for LambdaUnite®.MSS, Release.8.0.20.

• Software for LambdaUnite®.MSS, former release (used for “Fall Back” solution).

• An empty CompactFlash® card (the required storage capacity depends on the used Controller)

Depending on the application:

– a spare 1 GB CompactFlash® card, Comcode 109558544 (for traditional and ONNS applications with CTL/3S) or

– a spare 1 GB CompactFlash® card, Comcode 109558544 (for traditional and ONNS applications with CTL/3T) or

– a spare 512 MB CompactFlash® card, Comcode 109449710 (for traditional and ONNS applications with CTL/2) or

– a spare 256 MB CompactFlash® card, Comcode 109197137 (for traditional applications with CTL/-)

– and the apposite 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 the Ethernet LAN port of the LambdaUnite®.MSS NE.

The following Hubs are tested with LambdaUnite®.MSS

– Hewlett Packard J3128A/ Advanced Stack Hub-8E

– Allied Telesyn MR820TR

– Allied Telesyn 3024SL

– Allied Telesyn MR815T

– Allied Telesyn MR415T

• Ethernet LAN cablesImportant! 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 releases software.

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

1. Upgrade the WaveStar®.CIT software.

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


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

3. Perform a database backup.

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

4. Download the SW for the new release. Refer to “To perform an NE software download for upgrade purposes”

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

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.

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

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

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

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,

Go back to Step 4 and try it one time again. If you run the second time in this situation contact the TIER 3 support.

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

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




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

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

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 hang up in recovery and a Circuit Pack Comm Failure (CPCOMF) alarm is 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. For details see Problem 8.0.1 - nb67404 of chapter 3 “Known Prob-lems” of this document..

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

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 a similar 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.


1. Have a valid login on both the WaveStar®.CIT and all subject NE(s).

2. Acquire the CD-ROM that contains the new generic/version of the 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:MR820TR3024SLMR815TMR415T

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 method

proceed 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 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® 2000 / 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 --> 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® 2000 / 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 C:\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 A new software generic can only be activated if the duplex control state is error free.

This means:

• The Holder Status of the mate CTL must be Valid.

• The Operational Status of the mate CTL must be Enabled.

• No alarm must be present for the mate CTL.

• No equipment fail condition must be present for the mate CTL (Fault Status = NONE).

This implies that a new software generic can only be activated if:

• the NVMs of both CTLs are fully synchronized, and

• all subsequent changes can be applied to both CTLs in parallel.

Software downgrade 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.

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






1. Have a valid login on both the WaveStar®.CIT and all subject NE(s) within the ring.

2. Connect the WaveStar®.CIT to the local area network (LAN) of the 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.

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


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

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.

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

8.

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

9. In the WaveStar®.CIT System View, select the menu option Configuration --> Software --> Activate Software.

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

IF YOU WANT TO THEN SELECT

install a downloaded SW generic,

Install

cause the downloaded software to be installed in a trial phase,

Trial

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.

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.

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





10. Using the group box Switch type you can select which type of SW switch to perform

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

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.

Important! When upgrading a LambdaUnite node equipped with GE1 packs from Release.7.0.2/Release.7.0.3/Release.8.0.1 to Release.8.0.20 using the trial mechanism and falling back to Release.7.0.2/Release.7.0.3/Release.8.0.1, the GE1 packs hang up in recovery and a Circuit Pack Comm Failure (CPCOMF) alarm is 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. For details see Problem 8.0.1 - nb67404 of chapter 3 “Known Prob-lems” of this document..

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

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.

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




To check for successful NE software upgrade

When to use Use this procedure to check if NE software upgrade to new release was successful.


1. Have a valid login on both the WaveStar®.CIT and all subject NE(s) within the ring.

2. Connect the WaveStar®.CIT to the local area network (LAN) of the subject NE/ring.

Required equipment


• WaveStar®.CIT

Instructions Complete the following steps to 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.8.0.20 (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. After upgrade of an NE with ONNS functionality enabled is finished and once again after upgrade of the whole ONNS network is finished verify that for all paths the Connection Status is the same as before the upgrade was started and check the paths details.

Note: With WaveStar®.CIT ONNS View only login to already upgraded NEs is possible, since management of ONNS is supported by WaveStar®.CIT Software for LambdaUnite®.MSS Release.8.0.20 only. This implies that the start node of Wave-Star®.CIT ONNS View must already be upgraded to Release.8.0.20, and only the Connection Status and paths details of paths, where an already upgraded NE is A-node of, can be verified.

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

11. After upgrade of the whole ONNS network is finished, the new ONNS functionality must be enabled for all NEs of the whole ONNS network.

Select Administration --> ONNS Parameters from the menu bar of the WaveStar®.CIT ONNS View.

Check Enable for New ONNS Functionality and apply the OK button for all ONNS nodes.

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

12. After upgrade of the whole ONNS network is finished, check the topology data.

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

13. After upgrade of the whole ONNS network is finished, perform NN Database Audit and Synchronization.

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

14. 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”).

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

15. 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.8.0.20.

...........................................................................................................................................................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 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”).

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:


• No traffic lost

• Green activity LEDs on both CTLs are still flashing 1 hour after software activation.

Please refer to “Trouble shooting procedure C”(. 10-31).

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

D NE in duplex control:

• No traffic lost

• Red fault LED on one CTL is lit 1 hour after software activation.

Please refer to “Trouble shooting procedure D”.

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

E NE in simplex or duplex control:


• 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

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




Trouble shooting procedureA


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 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 procedureB

Proceed as follows:

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

1. Login to the 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 procedureC



Proceed as follows:

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

1. Open the latches of the CTL in the protection slot (slot 31).

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.

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


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


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

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.


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

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.


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

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





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


• the WaveStar®.CIT System View main menu: View --> View 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 procedureD



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, and the green activity LED stops flashing (is switched off).




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

IF THEN

login to the NE is possible, login to the LambdaUnite®.MSS NE, using the WaveStar®.CIT, and then continue with the next step.

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 Operational Status of the standby CTL is still is Disabled after 1 hour,


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





4. Perform a full reset of the standby CTL.

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

5. Wait until the Operational Status of the standby CTL is Enabled, and the green activity LED stops flashing (is switched off).




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

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


• the WaveStar®.CIT System View main menu: View --> View 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 Operational Status of the standby CTL is Enabled, and the green activity LED is switched off after 1 hour at the latest,


the Operational Status of the standby CTL is still is Disabled after 1 hour,


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




Trouble shooting procedureE



Important! For NEs with ONNS functionality enabled, it is recom-mended to perform this fall-back procedure for all NEs in the ONNS network with a previously taken consistent database backup. An isolated fall-back of a single NE may impair the consistency of ONNS data, which needs to be repaired by means of NN Database Audit and Synchronization features

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

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.

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


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


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

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: LUCENT-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 hang up in recovery and a Circuit Pack Comm Failure (CPCOMF) alarm is 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. For details see Problem 8.0.1 - nb67404 of chapter 3 “Known Problems” of this document..

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

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




10. 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 flashing (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 displaywindow

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 NEsoftware 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

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




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

• LUCENT

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)


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




New Installation and Upgrade ProceduresDatabase backup

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

Database backup 0

Overview

Purpose This chapter describes the procedure which has to be carried out for a NE database backup of the 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 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 .

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 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:

• LambdaUnite®.MSS User Operations Guide, “Database backup concepts”

• 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 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 connections using a hub the following hubs are recommended:


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





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,

in the Backup To/Via drop down list box select FTTD.


you want to backup the database directly to the CIT,

in the Backup To/Via drop down list box select CIT.

Result: A file selection screen appears showing that the database will back up to a specified folder under C:\Program Files\Lucent Technologies\Wavestar CIT\.... The directory of the file selection screen is automatically pre-populated.


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





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, 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 DatabaseInfo 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

• 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 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 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 connections using a hub the following hubs are recommended:



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





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. 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, Lucent Technologies, Wavestar CIT, and backups.Proceed Step 8.

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

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.

_______________________IF THEN

you want to restore the 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\Lucent Technologies\Wavestar CIT\.... The directory of the file selection screen is automatically pre-populated.

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.

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




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

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 dan-gerous 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 LambdaUnite®.MSS NE will now perform a system reset. As a consequence, the management association between the WaveStar®.CIT and the NE will be lost. After the sys-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

_______________________IF THEN

the NE comes up in maintenance mode,


the NE does not come up in maintenance mode,

the procedure is ended.

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




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




5 Miscellaneous

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

Contents 0

Supported NE Releases with WaveStar®.CIT 5 - 2

LambdaUnite®.MSS 5 - 2

Other NE Types 5 - 2

Technical Support 5 - 3

Overview 5 - 3

Services 5 - 3

Technical Support Groups 5 - 3

Contacting your LCS/RCS 5 - 3

Technical Support Service 5 - 3

Technical Support Platform 5 - 4

Reference 5 - 4

Product Support Levels 5 - 4



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

MiscellaneousSupported NE Releases with WaveStar®.CIT

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

Supported NE Releases with WaveStar®.CIT 0

LambdaUnite®.MSS The traditional part of WaveStar®.CIT Software Release.16.02.00 Build.1445 supports LambdaUnite®.MSS

• Release.7.0.2/Release.7.0.3

• Release.8.0.1/Release.8.0.20

Management of ONNS is supported by WaveStar®.CIT Software Release.16.02.00 Build.1445 for LambdaUnite®.MSS

• Release.8.0.20

Note: The upgrade of an ONNS network to Release.8.0.20 is supported by the traditional part of WaveStar®.CIT.

Other NE Types The following Network Element (NE) Releases of NE types other than LambdaUnite®.MSS are supported by WaveStar®.CIT Software Release.16.02.00 Build.1445:

NE Supported Release

WaveStar ® BandWidth Manager 01.03.00 - 04.01.99

WaveStar ® TDM 2.5G/10G (OC-48 2F/OC-192 2F) 01.00.00 - 07.01.99

WaveStar ® TDM 10G (STM-64) 01.00.00 - 05.00.99

Metropolis ® DMX 05.00.00 - 06.00.03

Metropolis ® DMXpress 01.00.00 - 02.00.01

Metropolis ® DMXplore 01.00.00 - 02.01.01

Metropolis ® DMXtend 03.00.00 - 04.00.03

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




MiscellaneousTechnical Support

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

Technical Support 0

Overview This section describes the technical support available for LambdaUnite®.MSS.

Services LambdaUnite®.MSS is complemented by a full range of services available to support planning, maintaining, and operating your system.Applications testing, network integration, and upgrade/conversion support is also available.

Technical Support Groups Technical support is available through

• Local/Regional Customer Support (LCS/RCS)

• Technical Support Service (TSS).

Contacting your LCS/RCS LCS/RCS personnel troubleshoot field problems 24 hours a day over the phone and on site (if necessary) based on Lucent Technologies Service Contracts:

For technical assistance, call your Local/Regional Customer Support Team. If the request cannot be solved by LCS/RCS, it will be escalated to the central Technical Support Service (TSS) teams in Westford, MA USA or Nuremberg, Germany.

Technical Support Service Lucent Technologies Technical Support Service (TSS) organization is committed to providing customers with quality product support services. Each segment of the TSS organization regards the customer as its highest priority and understands your obligations to maintain quality services for your customers.

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)

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



MiscellaneousTechnical Support

The TSS team maintains direct contact with Lucent Technologies manufacturing, Bell Laboratories development, and other organizations to assure fast resolution of all assistance requests.

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

Reference For additional information about technical support, please contact your Lucent Technologies Customer Team.

Product Support Levels The following figure shows the levels of product support for Lucent Technologies products.

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




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

Documents

Transcript of LambdaUnite® MultiService Switch.(MSS), Release.8.0.20