AM1 Software Release Description R5 0B PDF

Metropolis AM/AMS
Software Release Description
Network Element Software

Release 5.0B
Issue 2.0
August 2004
/XFHQW7HFKQRORJLHV3URSULHWDU\
7KLVGRFXPHQWFRQWDLQVSURSULHWDU\LQIRUPDWLRQ
RI/XFHQW7HFKQRORJLHVDQGLVQRWWREHGLVFORVHGRUXVHG
H[FHSWLQDFFRUGDQFHZLWKDSSOLFDEOHDJUHHPHQWV
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 the Customer Training and Information Products organization and the business
management owner of the material.
Lucent Technologies Network Systems
Larenseweg 50
1200 BD Hilversum
The Netherlands
Telephone +31 35 6873111
Internet www.lucent.com
Notice
Every effort was made to ensure that the information in this document was complete and accurate at the time
of printing. However, information is subject to change.
Trademarks
Pentium is a registered trademark of Intel Corporation
WaveStar, Metropolis and Navis are a trademarks of Lucent Technologies Inc.
Windows, Windows NT and Microsoft are registered trademarks of Microsoft Corporation.
Support
Please contact your Lucent Technologies Local Techical Support and services Team (TSS) for technical
questions about the information in this document.
Metropolis AM/AMS, Release 5.0B
Contents
0 About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Intended Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
How to Use This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
1 Problems Fixed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Fixed problems in Network Element software Release 5.0B . . . 1-2
Fixed Problems for ITM-CIT R13.03.01 . . . . . . . . . . . . . . . . . . . . . . 1-4
2 Known Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
General remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Known Problems in Network Element software Release 5.0B . 2-3
Known Problems for ITM-CIT R13.03.01 . . . . . . . . . . . . . . . . . . . . 2-11
3 New Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
4 Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

ITM-CIT Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
NE Software Upgrade General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
NE Maintenance Upgrade with WaveStar ITM-SC . . . . . . . . . . 4-4
8VHSXUVXDQWWR&RPSDQ\LQVWUXFWLRQV
Issue 2.0 August 2004 i

Metropolis AM/AMS, Release 5.0B
Contents
NE Maintenance Upgrade with the ITM-CIT . . . . . . . . . . . . . . . . . 4-12

NE Maintenance Upgrade with Navis OMS. . . . . . . . . . . . . . . . . . 4-14
5 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
ii Issue 2.0 August 2004

About This Document 0
Purpose
This document provides important information about known problems and

problems fixed in the Metropolis AM/AMS Release 5.0B Network Element (NE)
software and ITM-CIT (Craft Interface Terminal) software.
This document also provides procedures about how to install and/or upgrade the
Metropolis AM/AMS NE and ITM-CIT software.
Features are not described in this document because this information is provided
in the Applications, Planning and Ordering Guide, which is included in the
Metropolis AM/AMS documentation set.
Intended Audience
This document is intended for those responsible for the installation, acceptance,
operations and maintenance of Release 5.0B.
Issue 2.0 August 2004 i

About This Document Metropolis AM/AMS, Release 5.0B
How to Use This Document
Section 1- This section provides a description of the problems from the previous Metropolis
Problems Fixed AM/AMS Network Element that have been fixed in Metropolis AM/AMS Release
5.0B.
This section also provides a listing of problems that have been fixed in the ITM-
CIT Release R13.03.01.
Section 2- Known This section provides descriptions and workarounds to existing problems in
Problems Metropolis AM/AMS Release 5.0B and ITM-CIT Release R13.03.01.
Section 3- New This section provides a reference to the procedure to install the Metropolis AM/
Installation AMS Network Element (NE) software onto a new Metropolis AM/AMS system
and a reference to the procedure to install the ITM-CIT (Craft Interface Terminal)
software onto a Windows-based PC.
Section 4- This section provides the procedure for a maintenance upgrade of the
Upgrade Metropolis AM/AMS Network Element (NE) software to Metropolis AM/AMS
Procedures Release 5.0B if applicable
The maintenance upgrade can be performed with the ITM-CIT (Craft Interface
Terminal), with the WaveStar ITM-SC or with the Navis OMS, and all three the
procedures are given.
Section 5- This section provides useful information to supplement the information provided in
Miscellaneous the previous sections.
ii Issue 2.0 August 2004

Problems Fixed 1
1
Introduction
This section provides a description of the problems from previous Metropolis

AM/AMS Network Element releases that have been fixed in Metropolis AM/AMS
Release 5.0B.
This section also provides a listing of problems that have been fixed in the ITM-
CIT Release R13.03.01.
Issue 2.0 August 2004 1-1

Problems Fixed Metropolis AM/AMS, Release 5.0B
Fixed problems in Network Element

software Release 5.0B
4.0_nb03344 Virtual concatenation sequence numbers are not available.

On the AM NE, equipped with an X8PL option board, requesting the VC12/
VC3 termination point details will always display the transmitted/accepted
sequence number value 0.
4.0_nb03904 LCAS Hold-off and Wait to Restore timer values have no effect.
Hold-off and Wait to Restore on LCAS scheme are not supported features
for the Metropolis AM/AMS. Although these Hold-off and WTR fields are
available on the element managers, and the operator can fill out these
fields, applying these values will have no effect.
BQE LAN and WAN PM counters cannot be measured for X4IP card using
ITM-SC.
Using ITM-SC, when clicking on PM Current Measurements in order to
lookup enabled LAN and WAN PM points, the LAN and WAN ports are not
listed. Therefore PM current counters cannot be viewed using ITM-SC.
Same is applicable with Reset Digital counters and Create Report
windows.
4.0_nb04759 Retrieval of TP2 through Cross Connection List results in NE reset.

When using a DS1 option board and having TS2 cross-connects present,
the request of details in "TP list" of the "cross connect list" menu will result
in a NE reset.
4.0_nb05398 First frame of burst traffic might not get through X8PL.
When using the X8PL (CMC418), having traffic patterns consisting of short
bursts of frames, loss of the first frame (per burst) might occur.
5.0_nb06739 Software Download using ITM-CIT Fails.

The software download fails after completing 100% with error message:
"No response from the NE after 3 attempts" after which the CIT session is
terminated. Logging back in and retrieving the NE software configuration,
information displays "error" for the back-up store.
5.0_nb07557 Changing a Virtual Switch in repeater mode results in an unexpected

error message.
Any change on a Virtual Switch in transparent Repeater mode, for example
a label, will result in a message "Error ID 190: Invalid Acceptable Frame
type for virtual switch mode"
1-2 Issue 2.0 August 2004

5.0_nb07564 Sequence numbering for VC3-2v and VC12-xv always shows 0.

In case a virtual concatenation group exist out of more then 1 member, the
sequence numbers of each member should have a unique number in
sequential order.
5.0_nb07654 Slight packet loss on X8PL.

While running Ethernet traffic of random size, udp background, 80%
utilization for 20 min, some frames are lost. VC4 performance monitoring
does not indicate problems on SDH level.
5.0_nb08056 Preferred WAN link does not get active

When on an existing Ethernet path some provisioning settings (e.g. cross
connects) are deleted and afterwards corrected, the traffic does not
restore.

Fixed Problems for ITM-CIT R13.03.01
5.0_nb07556 Error message displayed when editing the SDH channel/VCG

information.
Edit SDH channel / VCG information window results in an unexpected error
message: 'Error ID 4: Value not in valid range'.
5.0_nb07566 CIT presents Acceptable Frame Type parameter in IEEE 802.1ad.

Acceptable Frame Type parameter should not be present when the
Ethernet switch is set in the IEEE 802.1ad mode.
5.0_nb07593 Selecting the SFP Unassign button results in meaningless error

message.
When the SFP unasign button is selected, an error message pops up with
a meaningless description: "Error ID: -1, Description: "
5.0_nb07633 STP and GVRP are still selectable in case the WAN port is set in
Customer role.
A Customer role WAN port should not support the STP and GVRP
protocol. However, both protocols are still selectable.
5.0_nb07708 Unexpected behaviour on confirmation warning when editing an

existing Virtual Switch.
After a virtual switch has been created and some additional changes are
applied, the manager response with "Do You Want To Apply Changes"
Regardless the response of the user (yes or no) the changes are made
effective.
5.0_nb00395 Default flow user priority modification not taking in account.

Changing the user priority does not always become effective.
5.0_nb03993 Available TP list in VCG information window also shows used TPs.
When editing the VCG to add or remove VCG members also the already
used TPs are shown.
5.0_nb08432 Unexpected error message when editing CC1 VC4 TP parameters.

When editing the VC4 TP of the CC, the CIT pops up with an error
message "Value is not in Valid Range" when any of the port parameters are
changed. Also the changes are not reflected.
5.0_nb08407 Several windows displays a '-'for the TP mode i.s.o. monitored / not
monitored.
When retrieving the termination point details the respective window does
not display the actual value but instead a "-".
5.0_nb07616 Editing Virtual Switch Details can give error message.

Editing parameters of an existing Virtual switch will result in a unexpected

error message although the provisioning change will become active.
2.2_1012367/ Backup & restore with ITM-CIT not supported.

nb08571 Backup & restore is no longer a feature for Metropolis AM/AMS, although
the menu option Get NE Configuration and Send NE configuration is still
selectable from within the ITM-CIT.
5.0_nb06600/ Essential details of the SFPs is not presented.

nb07591 When retrieving the SFP content some important information fields like
Lucent comcode and Serial number are not displayed.


Known Problems 2
2
Introduction
This chapter describes significant customer-affecting problems known to exist in

Metropolis AM/AMS Release 5.0B Network Element software and ITM-CIT
Release R13.03.01. Workarounds are provided where they apply.

Known Problems Metropolis AM/AMS, Release 5.0B
General remarks
Interworking between X8PL and TransLAN (X4IP-v2)

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

TP2.1311 TP2.1361 TP2.1342 TP2.1323 0
TP2.1321 TP2.1371 TP2.1352 TP2.1333 1
TP2.1331 TP2.1312 TP2.1362 TP2.1343 2
TP2.1341 TP2.1322 TP2.1372 TP2.1353 3
TP2.1351 TP2.1332 TP2.1313 TP2.1363 4
To prevent VC-x Virtual Concatenation sequence mismatch alarms, one

should always Cross Connect the lowest X8PL TP number to the X4IP-v2
TP with the lowest transmitted sequence number. If not, no traffic is
possible towards the X4IP as it will not be able to reconstruct the virtually
concatenated signal. This will be alarmed with a Sequence Number
Mismatch alarm.
Release 5.0B E1 non intrusive monitoring (NIM) feature deferred to

R6.x.
The NE software for Earth Release 5.0B does not contain the E1-NIM
feature although the CIT manager is already prepared.
As a consequence the current behaviour is as follow:
When the 2Mbit/s Port is operating in Transparent TS0 Termination mode,
the TS0 Monitoring is always disabled and the parameters PDH Layer
Monitoring and Degraded Signal Threshold can not be provisioned. This
is applicable to both PDH to SDH and SDH to PDH sub sections.
When switching to Double Terminated ISDN mode all parameters are
available to the user.
Also release R5.0 Customer Documentation has the E1 NIM feature
wrongfully described.
Small Form Factor Plugable (SFP) validity checking

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

Known Problems in Network Element

software Release 5.0B
3.2_nb00634 UAS always unavailable.

Inserting bit errors for more then 10 seconds does not increment the SES
counter on VC12 TTP of the Lucent NTU. Instead it displays unavailable.
Workaround:
None.
3.2_nb01012 TransLAN interruption after maintenance upgrade fall back to original

release.
There are reasons why a (maintenance) upgrade to this Release 5.0B (as
to any other release) can fail. Amongst these reasons are e.g. instable
DCN network or planned interruption by the operator. In the case of an
upgrade failure the system will fall back to the previous release after time-
out or after forced switch. Please note that in case of upgrades from Pearl
releases before R2.2.G (SCA92G) there is a risk that the fall back results in
permanently interrupted LAN data traffic. The SDH traffic will not be
affected.
Work around:
None. The TransLAN card has to undergo a hardreset after falling back, for
proper operation in the previous release.
Preventive action:
It is strongly recommended not to start a network upgrade in case of
instable DCN network. It is strongly recommended once an upgrade is
started not to interrupt this upgrade by the operator.
3.1_nb01184 UAT log retrieval fails for E1 termination on the SDSL board.
When the PM counters are retrieved with the CIT, the error code "value not
in valid range" is reported.
Work Around:
None.
2.0_nb01951 Actual parameters shown during auto-negotiation configuration.

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

Work around:
The actual values can be disregarded by the user during auto-negotiation
configuration.
2.2_nb01953 CIR not restricting traffic 60msec per minute (TransLAN).

When the CIR is provisioned, for 60 Millie seconds per minute (0.1% of the
time) all traffic (all flows) is passed instead of being restricted according to
the provisioned CIR. The effect of this is at largest when the LAN input
traffic is much higher than the provisioned CIR values.
Work around:
None.
2.0_nb01962 Lining up not working correctly.

After de-activating lining up, existing alarms are not reported. New alarms
do get reported.
Work around:
None.
3.2._nb01970 Neighbour list on ports connected to STM-1e/o option board not

correct.
When retrieving the dcc-neighbours list of an STM-1 port connected to a
Metropolis AM STM-1e/o option card will not display that NE' s NSAP

address. Retrieving the list from the STM-1e/o option board itself displays
the neighbour DCC list correctly.
Work around:
None.
3.0_nb01974 SHDSL Trib available for station clock timing.

It is possible to select the SHDSL trib port as input for the station clock
(select TRIB_2 when an SHDSL board is present in TS2). However the
SHDSL port can not serve as a timing reference.
Work around:
Avoid using the TRIB_2 when an SHDSL board is assigned for TS2.
3.1_nb01976 VC12cBDEG always raised on BBE regardless of Threshold level.

Although the threshold level can be provisioned it will have no effect. This
because threshold levels are fixed on the Elcon modem.Work around:
Do not use threshold level provisioning when using Elcon modem as NTU.
3.0_nb01991 Threshold reporting should be disabled for NTU VC12/P12 PM.

For description see: 3.1_nb01976.
4.0_nb02873 ITM-CIT session sometimes end when changing the TUG structure of
the X8PL option board.
Changing the TS2.1 TUG structure will sometimes end the (local) ITM-CIT
session unexpectedly. Even though the session has ended, the actual
provisioning action is successfully completed.
Work Around:
Change TUG structure with ITM-SC or re-login with ITM-CIT.
4.0_nb02981 UAS increments for errors shorter then 10 secs on NTU in TU12
mode.
In case on the LTU in TU12 mode a TP2.x PM point is enabled and an error
condition exist for shorter then ten seconds, the UAS counter is increased
instead of the SES.
Work Around:
None.
4.0_nb03261 P12cAIS alarm not cleared from ITM-CIT current alarms window.
In case an NTU is attached to the LTU with the TPs set to monitored, TS0
termination as "Double Terminated ISDN" and ISDN mode as "primary", a
P12cAIS alarm for SDH to PDH is raised. If the modem is now detached
from the "SHDSL Connection list window" the alarm is cleared on the ITM-
SC but not on the ITM-CIT.
Work Around:
Update current alarm window.
4.0_nb03421 Traffic loss if LCAS in not enabled on both ends on X8PL option card.

If on an existing path LCAS is enabled, the traffic will be lost until LCAS is
enabled on the terminating TP as well.
Work Around:
None.
4.0_nb03883 SDSLcLOS and SDSLcNES not reported in ITM-SC.

When using the X12SHDSL option card (CMC417) in combination with the
ITM-SC, the alarms SDSLcLOS and SDSLcNES are not reported.
The alarms are reported on the ITM-CIT.
Work Around:
None. Refer to ITM-CIT for these alarms.
3.0_nb04148 Large clock fluctuation when retiming SHDSL E1 signals in structured

mode.
When in E1 plesiosynchronous SHDSL transport mode the retimed timing
mode is used in combination with structured SHDSL E1 signal mapping,
large clock fluctuations (>60ppm) can occur.
Work around:
Only use retiming in structured SHDSL E1 mode on Metropolis AM B
units (AM1-XxYyy-B-zC, itemcodes CMB411, CMB412, CMB413 and
CMB414) in ISDN leased line mode.
4.0_nb04356 DS3 outloop is transparent.

Although the DS3 traffic can be looped in this release by provisioning an
outloop, the set outloop acts transparent: its both looped back, as well as
transmitted on the DS3 port.
Work around:
None.
4.0_nb04758 POWBcFLR alarm can disappear.

A POWXcFLR (indicating absence of voltage source on one of the two
feeds, X=A/B) might clear unexpectedly after a reset (e.g. as a result of
changing DCN parameters).
Work Around:
Power cycle the NE.
4.0_nb04920 No frequency monitoring on DS1 when having more references.

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

4.0_nb04944 After repetitive remote Logins to an NE, that NE might get remotely
inaccessible.
After multiple remote login hops on nodes in a ring/span, it might get
impossible to login remotely to one or more NE' s of that ring/span. When
attempting to remotely login, the following Error will be displayed:
"Error ID12 (Invalid destination NSAP address or incompatible NE)". A
local ITM-CIT login to the affected NE remains possible.
Work Around:
1. Reset the affected NE.
2. Local ITM-CIT login.
3. Make use of ITM-SC management.
3.2_nb05268 Login not possible after reset of Alarm Subscription Enabled NE.
When having alarm subscription enabled, sometimes after a power cycle it
is not possible to locally login to the node which has been power cycled.
Remote login is possible.
Another issue is that sometimes subscribed nodes will not be in the
subscription list (after the recovery) and it is not able to get the nodes back.
Work Around:
Sometimes resubscribing these nodes will fix the problem. Another
recovery of the NE sometimes help. Both workarounds are not 100%
guaranteed.
4.0_nb05363 Cant retrieve DCC neighbors when Transparent DCC is set.

When a Transparent DCC channel is provisioned the DCC Neighbor NE' s
List as well as the Network Area Member List can not be retrieved after an
NE reset. When these Lists will be retrieved by ITM-CIT the CIT session
will hang up and requires an application shutdown.
Work around:
None.
5.0_nb06609 AM/AMS upgrade to Earth must be with IP tunneling disabled.

An upgrade of a Metropolis AM/AMS from a R4.X Venus release to the
R5.0 Earth release should be done with the IP Tunneling feature disabled.
Work around:
None.
5.0_nb06816 P2P Adjacency also in case of DataLinkBlockSize mismatch.

When a difference of MaxLspBufSize existing on neighboring NEs a P2P
IS Adjacency should not come up after enabling DCC channels. The
current behavior however is that a P2P Adjacency does come up.
The effect of this situation will be an unstable management network.
Preventive action:
The maximum LSP size is an area wide parameter which should be
consistent within the DCN. Inconsistent usage of the LSP size can result in

a complete or partial DCN failure. If it is required to operate different areas

with different LSP sizes, then an external router must be used which
converts the different LSP sizes.
5.0_nb06878 MaxLspBufSize mismatch not recognizable on QLAN.

When a node, which is the Designated Router for the broadcast
subnetwork (QLAN), has MaxLspBufSize fixed to 1492, this will lead to
management instability of nodes within that subnetwork which have a
MaxLspBufSize setting of 512 bytes.
Preventive action:
Refer to Preventive action of 5.0_nb06816.
5.0_nb06953 NE resets with more then 247 VLANS.

Preventive action:The maximum amount of supported VLANS has been
increased to 1000 (both with GVRP enabled and GVRP disabled).
However, due to performance, stability and resource issues, it is
recommended not to use more than 247 VLANS in total, even if the NE
allows to provision more.

Work around:
None.
5.0_nb07023 PMcWUP does not shut down the laser

When an Small Form Factor Pluggable (SFP) unit is inserted, there is a
check if the SFP contains a supported type (so if it is an STM1 SFP) if this
is not the case (like for instance it is a GbE SFP) the PMcWUP alarm will
be raised and the Laser should be shut off. That laser shutdown does not
occur in this release.
Workaround:
None
3.2_nb07184 Port lock-up after switching analyzer port from 100Mps to 10Mps.
Feeding a X4IP TransLAN port set to fixed 10Mps with a fixed 100Mps
signal sometimes bring the port in a blocked state that after correcting the
speed to 10Mps will not recover until after a hard reset of the X4IP
TransLAN unit.
Preventive action:
Match the speed of both interfaces before interconnecting or use auto
negotiating.
5.0_nb07413 Adjacency not established after changing the Max Lsp Size.
When changing the Max Lsp Size the DCC channel is not starting up
properly and therefore it is not possible to establish a adjacency with the
neighbour node even when it operated in the lsp Size.
Workaround:
Reboot the system after the Max Lsp Size provisioning value has changed
5.0_nb07414 Auto Provisioned Tunnel (TAP) is lost after Node reboot.

Auto provisioned IP tunneling over OSI will not recover after an node reboot
(e.g. after Maintenance upgrade, SNMP provisioning).
Workaround:
Disable/enable IP Tunneling.
Preventive action:
Instead of TAP use manual provisioned IP tunneling.
5.0_nb07504 When a X8PL card is unassigned and assigned the card does not get
active.
When the X8PL card is re-assigned without removing the card from the
system the card does not start up properly and can not be used to carry
any traffic.
Workaround:
Power cycle NE

3.2_nb08038 Raised MDI Alarms will clear in case of reboot even though MDI
condition remains.
In case MDI alarms are raised and the NE is going through a reset (e.g.
after DCN or SNMP provisioning) the MDI alarms are cleared after the NE
has recovered, although the actual MDI condition has not changed.
Preventive action:
Clear first all MDI alarms before doing any provisioning or maintenance
tasks.
3.2_nb08491 VCxVcLOPC alarm is not cleared when VCxVcLOTC is raised

When operating in LCAS mode with more than one member the loss of
partial capacity alarm (VCxVcLOPC) is raised when a member becomes
failed. When consequently all members fail the Loss of total capacity alarm
(VCxVcLOTC) is raised. The LOPC alarm will stay although it should be
cleared in this scenario.
Workaround:
None
3.2_nb08629 When assigning a STM-1 optical or electrical option board, DCC

communication is not possible
When a STM-1 optical or electrical option board is assigned for the first
time, the DCC channels of the two STM-1 ports do not become active even
when they are enabled.
Workaround:
Reset Node
5.0_nb09224 X8PL traffic interrupted during ITM-CIT software download

When downloading software to the backup store of a Metropolis AM/AMS,
making use of ITM-CIT, Private Line traffic (X8PL) might get interrupted
uni-directional during the download, or even totally blocked untill infinity.
There is a EMACcLOF alarm raised in the NE which suffers the traffic loss.

On retreiving the Termination Point info, the expected and accepted

sequence numbers on each of the tribs do not match.
In case of a traffic block, a power cylce is needed to restore the traffic.
Workaround:
This problem does not occur when the NE software is downloaded by use
of the ITM-SC/OMS. Both Q-LAN as DCC connected network elements will
in this case not suffer any data loss.
5.0_nb09599 VC12 SNC cross-connects limited to 40

When creating more than 40 SNC protected low-order cross-connections,
this will lead to the system going continuously through recoveries.
Management with ITM-SC and ITM-CIT is no longer possible.
Workaround:
None. Restrict to maximum 40 SNC cross-connects.

Known Problems for ITM-CIT R13.03.01
2.2_1021811/ ITM-CIT mouse pointer hourglass stays forever.

nb01940 The mouse pointer hourglass remains visible even though the provisioning
task has already finished.
Work around:
Move mouse pointer shortly after provisioning task.
2.2_1023225 Error message when opening Performance Monitoring Measurements

screen.
When the Performance Monitoring Measurements screen is opened for
P12s (<-> VC12) and the 24h counter is disabled, the following error
message is displayed: "Error ID: 4, Description: Value is not in valid range".
This error message can be ignored, and when the OK button is pressed,
the Performance Monitoring Measurements screen appears.
Work around:
Not applicable.
3.0_1018555/ Provisioning takes place while MIB is locked.

nb00527 If with an ITM-SC managed NE provisioning is performed with ITM-CIT, a
pop-up window appears, prompting the user to unlock the MIB. In case NO
is selected the ITM-CIT shall still execute the provisioning, resulting in the
same pop-up window to be displayed. This will occur three times.
Work around:
Press three times the NO button
3.0_nb01993 Cleared E12cNES alarm not automatically be removed from alarm list.
If the E12cNES alarm is set to reported and a Modem is attached and un-
attached, the E12cNES alarms is not removed from the current alarm list.
Work around:
Press Update button.
5.0_nb05755 NE can hang up when requesting X8PL TP info.

From CIT menus Open the menu Provisioning, Transmission, Termination
Point, having a Filter set as VC4 - All will provide the options (buttons)
Details, TUG Structure and CC List when TS2,1 is highlighted. Only the

button TUG structure should be available. When the Details or CC list is

selected, the NE will hang up and a power cycle is required to recover.
Work Around:
In order to access X8PL TUG structure without risk of inappropriate buttons
(and effects), make use of the filter VC4 - TS2 in stead of VC4 - All.
5.0_nb06299 CIT gives an error when the Slaved AITS DCC is disabled or enabled.
In case both DCC channels are set to AITS and slave mode The CIT gives
an error message "Unsuccessful" and also the DCC list window doesn' t
reflect the status when the DCC channels are disabled.
Work Around:
Press the update button.
5.0_nb07605 Toggling Virtual Switch LAN/WAN tab will discard provisioned values
of previous active tab.
In case the WAN or LAN tab is toggled, the provisioned parameters that
were changed in the previous active tab will be lost.
Work Around:
Press Enter, Apply or Ok button before selecting a different tab.


New Installation 3
3
Introduction
Software for Metropolis AM/AMS Release 5.0B consists of two packages:

Metropolis AM/AMS Network Element (NE) Software Release 5.0B
delivered on a CD-ROM (ComCode 109535989).
ITM-CIT (Craft Interface Terminal) Software Release R13.03.01 delivered
on a CD-ROM (ComCode 109547224).
For new installations refer to the Metropolis AM and AMS, Release 5.0 Installa-
tion Guide (&RP&RGH
AMS configured For these installations, also refer to the Metropolis AM and AMS, Release 5.0
as Lucent NTU Installation Guide (&RP&RGH

New Installation Metropolis AM/AMS, Release 5.0B

Upgrade Procedures 4
4
ITM-CIT Upgrade
De-installation To upgrade an existing ITM-CIT to R13.03.01, an installed ITM-CIT version older

previous ITM-CIT than release R13.03.01 needs to be un-installed via the MS-Windows application
release Add/Remove Programs. User-created data (saved views, data communication,
provisioning, CIT security administration, NE generic file transfers) needs to be
preserved before installing the new R13.03.01 ITM-CIT version.
Installation ITM- For installation of the ITM-CIT refer to the Metropolis AM and AMS, Release 5.0
CIT R13.03.01 Installation Guide (&RP&RGH

Upgrade Procedures Metropolis AM/AMS, Release 5.0B
NE Software Upgrade General
Upgrading To upgrade a Metropolis AM/AMS Network Element from a release older than
from releases Release 5.0, a MIB conversion is needed. MIB conversion takes place outside the
older than NE by means of ITM-SC. As this may impact your entire network this procedure
Release 5.0 to falls outside the scope of this document. For more details on this procedure
Release 5.0B please contact your local Lucent Technologies support group.
Upgrading A Metropolis AM/AMS Network Element in Release 5.0 can be upgraded to

Release 5.0 to Release 5.0B directly.
Release 5.0B
NTU Upgrade The NTU software has not changed compared to Release 5.0 and therefore no
upgrade is needed.
Required This upgrade requires you have the following software:

equipment Navis OMS
WaveStar ITM-SC + latest service pack
ITM-CIT R13.03.01 (SAA614D) (Fully supports Metropolis AM/AMS
Release 5.0B)
Metropolis AM/AMS NE Software Release 5.0B
NOTE:
Only one of the above mentioned managers is needed.

NOTE:
CIT and NE Software are available on CD-ROM (see table below):
Software ComCode for the CD-ROM

NE software Release 5.0B (SCA401B) 109535989
CIT software version R13.03.01
109547224
(SAA614D)
NOTE:
Customers that have a password and privileges can download the NE and
ITM-CIT software as a self-extracting WinZip package from website:
www.lucent.com.
Lucent engineers can also use the TSS ONG Product Support website on
the Lucent intranet (for training, test and demonstration purposes):
http://ong.nl.lucent.com/tss/
ITM-SC service packs should be obtained via your local Lucent

Technologies support contact

NE Maintenance Upgrade with

WaveStar ITM-SC
Purpose This document describes a non-traffic-affecting field upgrade of the Metropolis

AM/AMS NE Software to Release 5.0B via the WaveStar ITM-SC.
Before you begin The Metropolis AM/AMS network is running in a release not lower than Release
5.0
During the network upgrade the following actions must be avoided:

NE provisioning
Insertion of new equipment
Replacement of NE hardware
Before upgrading the NE you should:

1. Read the NE Software Upgrade General section.
2. Check that the NE is alarm free prior to beginning with the upgrade.
Task This procedure consists of the following parts, each described separately:
Install the NE software on the ITM-SC (1)
Download the NE software to the NE (2)
Activate the NE software (3)
Final check (4)

(1.a) Install the NE This procedure describes how to copy the NE software from the CD-ROM to the
Software from WaveStar ITM-SC Server or Standalone, making use of the ITM-SC CD-ROM
CD-ROM with use device.
of the ITM-SC
To install the NE software you have to perform the following action:
Action Result Time

Software will be copied to the 10
Copy NE software to ITM-SC server
/tmp directory min.
A step by step instruction is given below:
NOTE:
To preserve file integrity the CD-ROM should be mounted using PFS instead of the
normal mount command
Mounting CD-ROM on HP-UX
Login as root <password>
Create the mount point by entering:
host> mkdir /cdrom
host> ioscan -funC disk (find CD-ROM device name)

host> mount /dev/rdsk/cXtXd0 /cdrom
where cXtXd0 is the CD-ROM device file on your machine.
In case of an ITM-SC Standalone, copy the *.S3 file to the NE load directory with:
host> cp/cdrom/*.S3 /opt/itm/sc/<version>/ems/mec/cmux/
In case of an ITM-SC Client copy the *.S3 file to a temporary directory

host> cp/cdrom/*.S3 /tmp
Set up an ftp connection to the ITM-SC Server and ftp in binary mode the *.S3 file
to the following directory:
host> cd /opt/itm/sc/<version>/ems/mec/cmux/
NOTE:
To find the current release path (indicated as <version> in above
procedures), login as i2kadmin <password> using Telnet to the ITM-SC
Server or Standalone and type:

host>. itmsc_setup (mind the dot!)

host> echo $EMSAPPLDIR
Unmount CD-ROM Drive:
host> cd /
host> umount /cdrom

(1.b) Install the NE This procedure describes how to install the NE software from a CD-ROM onto the
Software from CD- WaveStar ITM-SC Server or Standalone using a Personal Computer.
ROM with use of a
PC To install the NE software you have to perform the following action:
Action Result Time

Transfer the NE load from the CD-
The software files will be copied
ROM which is inserted into the PCs
to a temporary location on the 5 min.
CD-ROM drive to the ITM-SC Server
ITM-SC Server or Standalone
or Standalone system by using ftp
Prerequisite: PC connected to ITM-SC LAN
Start ftp client on PC and connect to ITM-SC Server or Standalone using user
acount i2kadmin <password>
Go to the following directory on the ITM-SC:

cd /opt/itm/sc/<version>/ems/mec/cmux/
NOTE:
To find the current release login as i2kadmin <password> using Telnet to
the ITM-SC server or Standalone and type:
#. itmsc-setup (mind the dot!)
#echo $EMSAPPLDIR
Ftp in binary mode the *.S3 file from the CD-ROM to the ITM-SC

(1.c) Import NE This procedure describes how to import the NE software file name into
software into ITM- WaveStar ITM-SC database.
SC database
To install the NE software you have to perform the following action:
Action Result Time

The NE software will be
Import file name into ITM-SC
selectable in the ITM-SC 5 min.
database
application
Login as i2kadmin <password>
host>. itmsc_setup (mind the dot!)
host>echo $EMSDBNAME --> Get the name of the database (e.g. i2000r112)
host>nql ---> start nql (now you get the nql> prompt)
nql> database <databasename>; ---> select database (use value found with echo
$EMSDBNAME) (don' t forget the '
;'
)
database has transactions ---> response from nql
database is not in mode ANSI
Version: 12S2.E112.34
nql> insert into software_file values ("mec.S3",0); ---> (replace "mec.S3" with
the actual file name)
nql> <Ctrl> D
Now the file mec.S3 is known in the database.

(2) Download the This procedure describes how to download a new NE software release to an NE
NE Software to from the WaveStar ITM-SC and will take approximately 25 minutes.
the NE
The software download is not traffic affecting.
NOTE:
It is recommended not to execute more than 4 software downloads at a
time, in order to prevent DCN performance problems.
Step Action
In the WaveStar ITM-SC System View window, select
1 Provisioning, Equipment, NE Software Inventory
The window EMS - Provisioned NE Software Inventory appears.
Press ... to select the NE from the EMS - NE Selection Dialog
2
window and click OK.
Press Edit, Select the software version from the list of loaded files,
3
tag Start Software Download and click Apply.
4 Track the download progress in the sub window Messages.
Wait until the sub window Messages displays Download
5 Completed and close the window.
The new software load has now been downloaded to the NE.

(3) Activate the NE This procedure describes how to activate a new NE software release and will take
Software approximately 25 minutes.
NOTE:
As a result of this action, a system reset will be initiated and the
communication to the NE will be lost for approximately 20 minutes. After
this time has elapsed, the NE can once again be managed via the
WaveStar ITM-SC.
NOTE:
If the Metropolis AM/AMS is equiped with the TransLAN option card and
the rapid spanning tree protocol is active during a network element software
upgrade from Release 5.0 to Release 5.0B, there can be an ethernet traffic
outage of up to 5 seconds due to spanning tree reconfiguration. This traffic
outage does not occur in repeater mode as the spanning tree protocol is not
used in this mode. SDH traffic is not affected.
NOTE:
in R5.0B a new TransLAN FPGA image was introduced. The upgrade of this
Field Programmable Gate Array will cause a traffic hit for the Ethernet traffic
(SDH traffic unaffected) regardless of the Operating Mode of the card. This
traffic hit will last for 10sec maximum.
Activate SW from To activate the software via the ITM-SC follow the step-by-step instruction given
ITM-SC GUI below:
Step Action
In the WaveStar ITM-SC System View window, select
1 Provisioning, Equipment, NE Software Inventory
The window EMS - Provisioned NE Software Inventory appears.
Press ... to select the NE from the EMS - NE Selection Dialog
2
window and click OK.
3 Press Edit, tag Switch (No MIB Clear) and click Apply.
4 Read the warning and if you agree, click Yes.
The sub window Messages displays Operation Started and if
5 successful followed by Operation Successful.
The new software load has now been activated.
NOTE:
It can take several minutes before the ITM-SC detects the association with
the Network Element to be down!

(4) Final Check This procedure describes how to verify whether the upgrade was performed
successfully or not.
Make sure that:

the traffic is working properly;
the NE is running in the correct NE load; this can be seen in the window
EMS - Provisioned NE Software Inventory (Provisioning, Equipment,
NE Software Inventory)
other nodes in the ring show no unexpected/new alarms;
there are no new unexpected alarms on the shelf.

NE Maintenance Upgrade with the

ITM-CIT
Purpose This procedure describes a non-traffic-affecting field upgrade of the NE Software

to Release 5.0B via the ITM-CIT.
NOTE:
This section is applicable for upgrades from Release 5.0 to Release 5.0B.
To upgrade a Metropolis AM/AMS Network Element from a release older
than Release 5.0 please contact your local Lucent Technologies support
group.
Before you begin Prior to performing this task, you must:

1. Read the NE Software Upgrade General section
2. Always use the ITM-CIT version corresponding to the NE release you are
upgrading to.
3. Connect the ITM-CIT to the CIT interface of the subjected NE/ring.
4. The NE should be Alarm free prior to beginning with the upgrade.
Download the NE software
Activate the NE software
Final check
Metropolis AM/AMS NE software upgrade with ITM-CIT

This procedure describes how to download a new NE software release to a NE

from the ITM-CIT. The software download is not traffic affecting. The NE will not
be provisionable during the generic download.
Step Action Result

1 Place the CD-ROM into the CD-
ROM drive.
2 Start-up the ITM-CIT and login.
3 Goto menu Provisioning, A new window will appear.
Equipment, NE Software
Configuration, then press Edit.
4 Choose Download, goto the ISD The new NE software will be
directory and select the file to presented as being available (but
download and then press Open. inactive) in the backup store.
This may take up to 1 hour.
5 Then press on Edit again, under
Switch Store click on the box After a short while the ITM-CIT will
Retain MIB. Then press on the disconnect.
Switch button.
6 After approx. 5 minutes you can log
in again with the ITM-CIT.
7 Goto menu Provisioning,
Equipment, NE Software NOTE:
If the software switch is not
Configuration and press Edit.
committed within 2 hours, the
Then press Commit.
software will switch back to
the previous release and
leave the backup-store in the
"error" state.
8 Check that the systems works
normally and error free.

NE Maintenance Upgrade with Navis

OMS
Purpose This document describes a non-traffic-affecting field upgrade of the Metropolis

AM/AMS NE Software to Release 5.0B via the Navis OMS.
Before you begin The Metropolis AM/AMS network is running in a release not lower than Release
5.0
During the network upgrade the following actions must be avoided:

NE provisioning
Insertion of new equipment
Replacement of NE hardware
Before upgrading the NE you should:

1. Read the NE Software Upgrade General section.
2. Check that the NE is alarm free prior to beginning with the upgrade.
Install the NE software on the OMS (1)
Download the NE software to the NE (2)
Activate the NE software (3)
Final check (4)

(1) Install the NE This procedure describes how to copy the NE software from the CD-ROM to the
Software from Navis OMS.
CD-ROM with use
of the OMS To install the NE software you have to perform the following action:
Action Result Time

Software will be copied to the
10
Copy NE software to OMS server /var/opt/lucent/NE_SW/
min.
AM1PLUS directory
1] Put the CD-ROM with the NE sw in the CD/DVD.
2] Login onto the Navis OMS as an user with software management privileges.
3] Open the network element/software screen.
4] Select the New (action) button in the right top corner of the screen. A new
window will open which allows you to import the sw.
5] In the NE Type pulldown menu select Metropolis AM and the NE Generic.
6] After selecting Submit the sw will be copied to the server.
7] Wait untill you get the message "A new NE generic for Metropolis AM has
been successfully transferred to the management system".

(2) Download the This procedure describes how to download a new NE software release to an NE
NE Software to from the Navis OMS and will take approximately 25 minutes.
the NE
The software download is not traffic affecting.
1] Return to the Network Elements Software Menu and select NE generic and NE.
2] At NE type and NE name select Metropolis AM and the Name of the NE you
want to download the sw to, and press search.
3] You will get information about the active and inactive store of the NE. From the
bottom of the screen select Transfer NE generic from management system to NE
and press go.
4] Wait untill you get the message that the sw has been successfully downloaded
to the NE.

(3) Activate the NE This procedure describes how to activate a new NE software release and will take
Software approximately 25 minutes.
NOTE:
As a result of this action, a system reset will be initiated and the
communication to the NE will be lost for approximately 20 minutes. After
this time has elapsed, the NE can once again be managed via the Navis
OMS.
NOTE:
If the Metropolis AM/AMS is equiped with the TransLAN option card and
the rapid spanning tree protocol is active during a network element software
upgrade from Release 5.0 to Release 5.0B, there can be an Ethernet traffic
outage of up to 5 seconds due to Spanning Tree reconfiguration. This traffic
outage does not occur in repeater mode as the spanning tree protocol is not
used in this mode. SDH traffic is not affected.
NOTE:
in R5.0B a new TransLAN FPGA image was introduced. The upgrade of this
Field Programmable Gate Array will cause a traffic hit for the Ethernet traffic
(SDH traffic unaffected) regardless of the Operating Mode of the card. This
traffic hit will last for 10sec maximum.
Activate SW from To activate the software via the ITM-SC follow the step-by-step instruction given
OMS below:
1] Return to the Network Elements Software Menu and select NE generic and NE.
2] At NE type and NE name select Metropolis AM and the Name of the NE you
want to upgrade, and press search.
3] You will get information about the active and inactive store of the NE. Verify that
the inactive store shows the correct Item Code.
4] From the bottom of the screen select Activate: No Mib clear and go.
5] Wait untill you get the message that the operation was successful.

(4) Final Check This procedure describes how to verify whether the upgrade was performed
successfully or not.
Make sure that:
1] the traffic is working properly;
2] the NE is running in the correct NE load; this can be seen in the window
Network Elements Software Menu, NE generic, NE name, search
3] other nodes in the ring show no unexpected/new alarms;
4] there are no new unexpected alarms on the shelf.

Miscellaneous 5
5
Technical Support
Introduction This section describes the technical support available for 0HWURSROLV$0$06.
Technical support Technical support is available through:

groups Local/Regional TSS.
TSS ONG Global Product Support Netherlands.
Contacting your Local/Regional Technical Support Services (TSS) personnel troubleshoot field
Local/Regional problems 24 hours a day over the phone and on site (if necessary) based on
TSS Lucent Service Contracts.
For Technical assistance, call your Local/Regional TSS team. If the request
cannot be solved by Local Regional TSS, it will be escalated to the TSS ONG
Global Product Support Netherlands team.
Product Support Lucent Technologies TSS ONG Global Product Support Netherlands organization
is committed to providing customers with quality product support services. Each
segment of the TSS organization regards the customer as its highest priority and
understands your obligations to maintain quality services for your customers.
The TSS team maintains direct contact with Lucent Technologies manufacturing,
Bell Laboratories development, and other organizations to assure fast resolution
of all assistance requests.

Miscellaneous Metropolis AM/AMS, Release 5.0B
Services Metropolis AM/AMS is complemented by a full range of services available to

support planning, maintaining, and operating your system. Applications testing,
network integration, and upgrade/conversion support is also available.
A technical A global online trouble tracking system is used by all support teams to track
support Platform 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
Local/Regional Technical Support Services.

AM1 Software Release Description R5 0B PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

AM1 Software Release Description R5 0B PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Metropolis AM/AMS

Software Release Description

Network Element Software

0 About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

1 Problems Fixed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

2 Known Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

3 New Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

4 Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Issue 2.0 August 2004 i

NE Maintenance Upgrade with the ITM-CIT . . . . . . . . . . . . . . . . . 4-12

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

ii Issue 2.0 August 2004

This document provides important information about known problems and

Issue 2.0 August 2004 i

How to Use This Document

ii Issue 2.0 August 2004

This section provides a description of the problems from previous Metropolis

Issue 2.0 August 2004 1-1

Fixed problems in Network Element

4.0_nb03344 Virtual concatenation sequence numbers are not available.

4.0_nb04759 Retrieval of TP2 through Cross Connection List results in NE reset.

5.0_nb06739 Software Download using ITM-CIT Fails.

5.0_nb07557 Changing a Virtual Switch in repeater mode results in an unexpected

1-2 Issue 2.0 August 2004

5.0_nb07564 Sequence numbering for VC3-2v and VC12-xv always shows 0.

5.0_nb07654 Slight packet loss on X8PL.

5.0_nb08056 Preferred WAN link does not get active

Issue 2.0 August 2004 1-3

Fixed Problems for ITM-CIT R13.03.01

5.0_nb07556 Error message displayed when editing the SDH channel/VCG

5.0_nb07566 CIT presents Acceptable Frame Type parameter in IEEE 802.1ad.

5.0_nb07593 Selecting the SFP Unassign button results in meaningless error

5.0_nb07708 Unexpected behaviour on confirmation warning when editing an

5.0_nb00395 Default flow user priority modification not taking in account.

5.0_nb08432 Unexpected error message when editing CC1 VC4 TP parameters.

5.0_nb07616 Editing Virtual Switch Details can give error message.

1-4 Issue 2.0 August 2004

error message although the provisioning change will become active.

2.2_1012367/ Backup & restore with ITM-CIT not supported.

5.0_nb06600/ Essential details of the SFPs is not presented.

Issue 2.0 August 2004 1-5

1-6 Issue 2.0 August 2004

This chapter describes significant customer-affecting problems known to exist in

Issue 2.0 August 2004 2-1

Interworking between X8PL and TransLAN (X4IP-v2)

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

To prevent VC-x Virtual Concatenation sequence mismatch alarms, one

Release 5.0B E1 non intrusive monitoring (NIM) feature deferred to

Small Form Factor Plugable (SFP) validity checking

2-2 Issue 2.0 August 2004

Known Problems in Network Element

3.2_nb00634 UAS always unavailable.

3.2_nb01012 TransLAN interruption after maintenance upgrade fall back to original

2.0_nb01951 Actual parameters shown during auto-negotiation configuration.

Issue 2.0 August 2004 2-3

2.2_nb01953 CIR not restricting traffic 60msec per minute (TransLAN).

2.0_nb01962 Lining up not working correctly.

3.2._nb01970 Neighbour list on ports connected to STM-1e/o option board not

2-4 Issue 2.0 August 2004

3.0_nb01974 SHDSL Trib available for station clock timing.

3.1_nb01976 VC12cBDEG always raised on BBE regardless of Threshold level.

3.0_nb01991 Threshold reporting should be disabled for NTU VC12/P12 PM.

Issue 2.0 August 2004 2-5