3AG24101BFAAFMZZA - V1 - 1678 MCC Release 04.05.x Product Release Note

Alcatel-Lucent
1678 MCC | R4.5.x

Product Release Notes
3AG 24101 BFAA FMZZA

ED04
November 2009
Alcatel-Lucent Proprietary
Use pursuant to applicable agreements
REVISION HISTORY
ED
DATE
01
081205
02
ORIGINATOR
APPROVER
Release Note for R4.5
H. Bauer
A.Kemmler
090610
Update for R4.5.1 CI
H. Bauer
A.Kemmler
03
090807
Update for R4.5.1 RP1 CI
H. Bauer
A.Kemmler
04
091109
Update for R4.5.1
H. Bauer
A.Kemmler

ED04
November 2009
COMMENTS
2 of 33
CONTENTS
1
REFERENCED DOCUMENTS........................................................................................4
DEFINITIONS AND ABBREVIATIONS ...........................................................................4
KEY FEATURES ...........................................................................................................10
PRODUCT COMPOSITION ..........................................................................................14

4.1
4.2
4.3
4.4
INSTALLATION PROCEDURE .....................................................................................15

5.1
5.2
Software 1678MCC R4.5.x ..............................................................................14

Hardware 1678MCC R4.5.x ............................................................................14
Documentation ................................................................................................14
SW maintenance raw patch releases ..............................................................14
New installation ..............................................................................................15
In service update / upgrade ............................................................................15
SOLVED PROBLEMS/RESTRICTIONS/WARNINGS ..................................................16

6.1
Solved problems/restrictions/warnings R4.5.1 CI ............................................16

6.1.1
6.1.2
6.1.3
6.1.4
6.2
Solved problems/restrictions/warnings R4.5.1 RP1 CI ....................................19
6.3
Solved problems/restrictions/warnings R4.5.1 ................................................20
6.2.1
6.3.1
6.3.2
6.3.3
6.3.4
Solved problems .............................................................................................. 16

Solved problems with workaround ................................................................... 16
Solved functional restrictions and warnings .................................................... 18
Solved specific system behaviours .................................................................. 19
Solved problems .............................................................................................. 20
Solved problems with workaround ................................................................... 20
Solved specific system behaviours .................................................................. 20
KNOWN PROBLEMS/RESTRICTIONS/WARNINGS ...................................................22

7.1
Known problems/restrictions/warnings in R4.5.x ..........................................22

7.1.1
7.1.2
7.1.3
7.1.4

ED04
November 2009
Known problems .............................................................................................. 22

Known problems with workaround ................................................................... 24
Functional restrictions and warnings ............................................................... 25
Specific system behaviours ............................................................................. 31
3 of 33
1
[1]
[2]
[3]
REFERENCED DOCUMENTS
Validation Release Note
Software Development Release
Feature List
3AG 24101 BFAA

3AG 24101 BFAA
3AG 24101 BFAA
FCZZA ED02
PVZZA ED01
FLZZA ED03
DEFINITIONS AND ABBREVIATIONS
ABBREVIATION
MEANING
ABN
AC
ADM
AIS
ALM
ALS
AND
ANSI
APD
APS
ASIC
ASON
ASTN
ATM
ATTD
AU
AU4
AUG
AUOH
AUX
BATT
BER
BGP
BIP
BNC
BST
BST10
BTERM
BUSTERM
CE
CLNP
CMI
CO
CONGIHC
COPS
CORBA
CPE
CPLD
CPI
CPO
CPU
Abnormal condition
Alternate Current
Add/Drop Multiplexer
Alarm Indication Signal
Alarm Board
Automatic Laser Shutdown
Alarm on both station batteries
American National Standards International
Avalanche Photodiode
Automatic Protection Switching
Application Specific Integrated Circuit
Automatically Switched Optical Network
Automatically Switched Transport Network
Asynchronous Transfer Mode
Attended (alarm storing)
Administrative Unit
Administrative unit level 4
Administrative Unit Group
AU Pointer
Auxiliary
Battery
Bit Error Rate
Border Gateway Protocol
Bit Interleaved Parity
Bayonet Not Coupling
Optical Booster
Optical Booster 10dBm output power
Bus Termination Board (1670SM)
Bus Termination Board (Main Shelf)
European Conformity
ConnectionLess Network Protocol
Code Mark Inversion
Central Office
Control and General Interface Board (High Capacity) in 1670SM
Common Open Policy Server
Common Object Request Broker Architecture
Customer premises equipment
Complex Programmable Logic Device
Incoming parallel contacts
Outgoing parallel contacts
Central Processing Unit

ED04
November 2009
4 of 33
CSR
CT
DC
DCC
DCCM
DCCP
DCCR
D&C
DCM
DCN
DCR
DCU
DDF
DXC
EC
ECC
ECT
EIDEC
EMI/EMC
EPS
EQUICO
ESD
ETSI
FC/PC
FCS
FEBE
FEC
FEPROM
FERF
FLC
FLCCONGI
FLCSERV
FPE
FPGA
G.ASTN GMPLS
GbE
GBOS
GETHA
GFP
gGOS
GMPLS
GMRE
GND
GNE
GRE
GUI
HMU
HO
HOA
HOI
HPC
HPOM
ED04
November 2009
Customer Specific Release

Craft Terminal
Direct Current
Data Communication Channel
DCC on Multiplex Section (D4D12)
DCC on Path Overhead
DCC on Regenerator Section (D1D3)
Drop and Continue
Dispersion Compensation Module
Data Communication Network
DCC Router
Dispersion Compensation Unit
Digital Distribution Frame
Digital Cross Connect
Equipment Controller
Embedded Control Channel
Equipment Craft Terminal
Enhanced IDE Controller
Electromagnetic interference / Electromagnetic compatibility
Equipment Protection Switching
Equipment Controller
Electrostatic discharges
European Telecommunication Standards Institute
Type of optical connector
Frame Check Sequence
Far End Block Error
Forward Error Correction
Flesh Electrically erasable programmable read only memory
Far End Receive Failure
First Level Controller
First Level Controller+Control and General Interface Board
FLCSERVICE (First Level Controller + SERVICE Board)
Functional Protection Earth
Field Programmable Gate Array
Automatically Switched Transport Network
Gigabit Ethernet
Generic Basic Operating System
Gigabit Ethernet Access card
Generic Frame Procedure
Performance improved version of GBOS
Generalized Multiprotocol Label Switching
GMPLS Routing Engine
Ground
Gateway Network Element
Generic Routing Encapsulation
Graphical User Interface
Housekeeping Monitoring Unit
High Order
High Order Adaptation
High Order Interface
High order Path Connection
High order Path Overhead Monitoring
5 of 33
HPROT
HPT
HSUT
HW
II
ICS
IEC
IEEE
IETF
ILM
IN
INNI
IND
INT
ION
I/O
IP
IPCC
ISA
ISO
ISPB
ISU
JE1 JE2 JE3
L
LA20
LAC40
LAN
LAX40
LAX20
LC
LCAS
LDSSHUT
LED
LIU
LMP
LO
LOI
LOM
LOP
LOPP
LOS
LPA
LPC
LPM
LPOM
LPT
LSUT
LSX
LX160
MAC
MCC
MCF
ED04
November 2009
High Speed Protection Board

Higher Order Path Termination
High order Supervisory Unequipped Termination
Hardware
intra-Office
item Change Status
International Electrotechnical Committee
Institute of Electrical and Electronic Engineering
Internet Engineering task Force
Integrated Laser Modulator
Input
Internal NetworktoNetwork Interface
Indicative alarm
Internal Local Alarms
Intelligent Optical Network
Input/Output
Internet Protocol
IP Control Channel
Integrated Service Adapter
International Organisation for standardization
Intra Shelf Processor Bus
In Service Upgrade
Joint Engineering
Long Haul
LO Adaptation Board 20G
Lower Order Matrix Link 40G
Local Area Network
LO Adaption and Matrix Board 40G
LO Adaption and Matrix Board 20G
Link Capacity Adjustment Scheme
Command for ALS
Light Emission Diode
Line Interface Unit
Link Management Protocol
Low Order
Low Order Interface
Loss Of Multiframe
Loss Of Pointer
Low Order Pointer Processing
Loss Of Signal
Lower order path adaption
Lower order path connection
Loopback line side (remote)
Lower Order Path Monitoring
Lower order path termination or Loopback equipment side
Lower order Supervisory Unequipped Termination
LAN Switch
LO Centerstage Matrix 160GBIT/S
Media Access Controller
Metro Core Connect
Message Communication Function
6 of 33
MHDLC
MLM
MMF
MPLS
MS
MSA
MSOH
MSP
MSSPRING
MST
MX640
MX320
MX160
NAD
NCA
NCI
NE
NGTRU
NM
NMI
NMS
NNI
NP
NPE
NPOS
NRZ
NURG
OBPS
ODF
OED
OFA
OH
OHBUS
OIF
OMSG
OMSN
OOF
ORALIM
OS
OSI
OTH
OTN
OUNI
OUT
PC
PCB
PCI
PDH
PFAIL
PI
PJE
P/N
ED04
November 2009
Multi HighLevel Data Link Controller

Multi Longitudinal mode
Multimode Fiber
Multi Protocol Label Switching
Multiplex Section
Multiplex section adaptation
Multiplex Section OverHead
Multiplex Section Protection
Multiplex Section Shared Protection Ring
Multiplex Section Termination
Matrix Board 640GBIT/S
Network Access Domain
Network Control Adapter
NE Control Interface
Network Element
New Generation Top Rack Unit
Network Management
Network Management Interface
Network Management System
Network to Network Interface
Network Processor (Restoration Manager 1354NP)
Network Protection Element
Network Protection Operating System
No return to zero
Not Urgent alarm
On Board Power Supply
Optical Distribution Frame
Optical Edge Device
Optical Fiber Amplifier
OverHead
Dedicated housekeeping stream
Optical Internetworking Forum
Optical Multiservice Gateway and CrossConnect
Optical Multiservice Node
Out Of Frame
ORing of station power supply alarm
Operation System
Open Systems Interconnection
Optical Transport Hierarchy
Optical Transport Network
Optical UserNetwork Interface
Output
Personal Computer
Printed Circuit Board
Peripheral Component Interconnect
Plesiochronous Digital Hierarchy
Power supply failure
Physical interface
Pointer Justification Event
Part Number
7 of 33
POH
PPI
ppm
PPS
PWALM
Q2/QB2
Q3/QB3
RA
RAI
RAM
RCK
RDI
REI
REL
RL
RMS
RNURG
RS
RSOH
RST
RURG
S
SBR
SC
SC
SDH
SEC
SEMF
SETG
SETS
SFF
SFP
SNCP
SOH
SONET
S/P
SPC
SPI
SQ
SSF
SSM
SSU
STM
SW
TANC
TMN
TOR
TORC
TRIB
TSD
TSF
TTF
ED04
November 2009
Path Overhead
Plesiochronous Physical interface
parts per million
Path Protection Switching
Power supply alarm
TMN interface with B2 protocol; interface towards PDH equip.
TMN Interface with B3 protocol; interface towards TMN
Rack Alarm
Remote Alarm Indication
Random Access Memory
Received clock
Remote Defect Indication
Remote Error Indication
Release
Rack Lamp
Root Mean Square
Not urgent Alarm command. Lights up the relative rack red LED
Regenerator Section
Regenerator Section OverHead
Regenerator Section Termination
Urgent Alarm command. Lights up the relative rack red LED
Short Haul
Source Based Restoration
Shelf Controller
Synchronous Digital Hierarchy
SDH Equipment Clock
Synchronous Equipment Management Function
Synchronous Equipment Timing Generation
Synchronous Equipment Timing Source
Small Form Factor (not plugable)
Small Form Plugable
Subnetwork Connection Protection
Section OverHead
Synchronous Optical Network
Serial/Parallel Converter
Soft Permanent Connection
Synchronous Physical Interface
Squelch
Server Signal Fail
Synchronization Status Message
System Startup and Supervision
Synchronous Transport Module
Software
Remote alarm due to failure of all power supply units
Telecommunication Management Network
Remote alarm indicating loss of one of the station batteries
Remote alarm due to a faulty/missing power supply unit
Tributary
Trail Signal Degrade
Trail Signal Fail
Transport Terminal Function
8 of 33
TX
U
UNI
URG
V
VCG
VCXO/VCO
VCx
VECE
VLAN
VMMF
WAN
WEEE
XFP
XFPE

ED04
November 2009
Transmission
Ultra Long Haul
User to Network Interface
Urgent
Very Long Haul
Virtual Concatenation Group
Voltage controlled oscillator
Virtual Container
Virtual Equipment Control Element
Virtual LAN
Virtual Machine Management Function
Wide Access Network
Waste of Electrical and Electronic Equipment
10 Gigabit Small Form Factor Pluggable Module
XFP Extended
9 of 33
KEY FEATURES
Key functionalities introduced with previous releases:

- HO Matrix
- 160G/320G/640G HO Matrix card, 1+1 EPS
- In-service upgrade of HO matrix
- LO Matrix
- 20G/40G single-slot LO Matrix card, 1+1 EPS
- LO extension shelf, scalable up to 160G (1000 STM-1 equivalents) in steps of 40G (250
STM-1 equivalents)
- LO PM
- In-service upgrade of LO matrix
- TDM interface cards
- 16x STM-1 card (SFP)
- 16x STM-1/4 card (SFP)
- 4x/8x/16x STM16 card (SFP)
- 2x/4x STM-64 card (XFP)
- 16x STM1el./opt. cards in 1670OED drop shelf
- 24x E1 card in 1662OED drop shelf
- STM-16 Colored CWDM SFP
- STM-16 Colored DWDM SFP L-16.2 (spacing - 100 GHz)
- STM-64 Colored DWDM XFP
- MSA to XFP replacement
- 10GE LAN interface cards with XFP optical interface module
- 2x/4x 10GE LAN card
- Rate adaptive mapping VC-4-Xv (X=1 to 64)
- Port auto-negotiation configuration
- SR, LR XFP optical interface module
- EVPL push/pop
- LCAS
- Fast LPT
- Ethernet PM counters
- 1GbE interface card
- 4x/8x/16xGbE card (SFP)
- Rate adaptive mapping VC-4-Xv (X=1 to 7)
- Port auto-negotiation configuration
- SX, LX, ZX SFP optical interface module
- LCAS
- Fast LPT
- Ethernet PM counters
- System
- Station Alarms/Housekeeping
- Event log
- 1:N MSP on STM-1/4/16/64 and S1E in OED, w/ MSP hold off time
- 128 MSP groups in mainshelf and 1670OED drop shelf
- NTP configuration via CT
- GMPLS
- Managed classes of Services: unprotected, SBR (Source Based Rerouting), GR (Guaranteed
Restoration), protected, PRC (Protection & Restoration Combined)
- Priority based preemption (5 priority levels)
ED04
November 2009
10 of 33
Nominal route handling with manual/automatic hitless reversion

Local repair capability for optimized usage of resources
SNCP ring closure at network boundary
IB/OOB Protection
Serial compound links
Multicast connections w/ SBR and GR restoration
LO drop interface in ASON domain for LAX20/40
Ethernet drop interface in ASON domain for 1GbE, 10GbE EPL
Graceful Migration from RM to ASON manager (RM) / GMRE part for HO-TDM, and Ethernet
(EPL)
- Control plane auto-discovery
- OIF UNI 2.0 for SDH services
- Disjoint links
- Bridge & Roll
- Link maintenance
- GMRE deactivation
- ISA-ES64 @ VC4 (ETSI):
- 2x20G switching capacity per system,
- 1:1 EPS protection
- Jumbo Frame (9242 bytes) support on ports 1..30 and 129..158
- Baby Jumbo Frame (2026 bytes) support on all ports
- VLAN label stacking
- ETH VLAN push/pop/swap
- Ethernet rate adaptive mapping VC-4-Xv (X=1 to 64) at logical port
- Up to 128 VC-4-Xv VCGs per board
- GFP-F mapping (framed, acc. G.7041)
- GFP-F (G.7041): null extension header without FCS
- Packet policing (network ingress)
- Dual rate token bucket
- Metering, Policing and Marking MEF compliant
- Color blind traffic Metering, Policing and Marking (SLA compliance)
- Traffic management (Packet congestion & Scheduling)
- 2 queues w/ strict priority scheduling
- 6 queues w/ WFQ (WDRR) scheduling
- W-RED congestion avoidance
- Customer protocols tunneling (transparency)
- Best Effort Traffic (PIR > 0, CIR = 0)
- Regulated Traffic (PIR > CIR > 0)
- Guaranteed Traffic (PIR = CIR > 0)
- Packet classification: port
- Ethernet priority bits classification (802.1Q)
- ETH VLAN classification
- classification acc. VLAN ID + pri-bits inside same service
- 8 QoS classes
- L2-Matrix is 100% non-blocking
- ETH Unicast/MC/BC traffic forwarding
- Packet Forwarding: port
- Packet Forwarding: port + VLAN tag (outer tag lookup)
- ETH Private Line
- ETH Virtual Private Line
- up to 128 logical ports per card
- Ether Type provisioning per port
ED04
November 2009
11 of 33
- up to 2 pairs of ES64
- Connection Admission Control (CAC)
- CIR CAC disabling per ES64 (pair)
- Preserve p-bits on VLAN push/pop
- Per port counters: Green/Yellow discards, current, history (15m/24h)
- Per Q counters: Green/Yellow discards, current, history (15m/24h)
- 1:1 EPS for a pair of ISA-ES64 server cards
- SNMP CT (ZIC) with up to 6 simultaneous sessions
- Management interface via SNMP protocol stack
- Enable/disable policing on a per flow basis (CLI only)
- Shared traffic descriptors
- Multiple traffic descriptors per service
- S-LAG (1:1)
- DCN
- DCC protection (<100msec.)
- DCC channel quantity: 95 MS & 16 RS per system (FLC AB type)
- DCC channel quantity: 16 MS & 16 RS per system (FLC AA and AB type)
- Multi-OSI area management
- IP over OSI tunneling
- DCC transparency
Note: Regression testing for GMPLS w/ HO-AU3 mapping will be executed on demand.
Key functionalities introduced with R4.5:

- Auto-port monitoring
- PJE counter w/ TCA
- DDM
- 10GE PM history counters 15min & 24h
- 10GE queue management (WRED, flexible buffer size)
- GMRE:
- E-NNI 1.0 with OIF local domain restoration
- Graceful Migration from RM to ASON manager (RM) / GMRE part for EVPL
- SNCP selector management
- PM on GMPLS LSPs
- 10GE EVPL drop interface in GMPLS domain
- ES64 drop interface in GMPLS domain
- Multicast connections w/ PRC restoration
- WTR extension to minimum of 5min. WTR time
- MX loopback for GMPLS LSPs
- ES64:
- LAG according to 802.3ad (1:N, LACP)
- LAG on 1GbE ports
- LCAS for VC-4-nv
- up to 18LAG groups per ES64 card
- CIR oversubscription per port (provisionable factor)
- CT/NMS:
- CT login security

ED04
November 2009
12 of 33
For detailed information regarding the supported features please refer to

[3] Feature List

ED04
November 2009
13 of 33
PRODUCT COMPOSITION
4.1
Software 1678MCC R4.5.x

Release
FLC Platform
FLC Application
FLC GMPLS
CT
R4.5
CORE-01J
SKY62-02P
ION78-03A
CT20.8.35
R4.5.1 CI
CORE-01J
SKY62-10V
ION78-12D
CT20.8.38
R4.5.1
CORE-01J
SKY62-13D
ION78-12N
CT20.8.41
4.2
Hardware 1678MCC R4.5.x
New HW items introduced with previous R4 releases:

4x 10GE LAN Port /XFP
3AG24339AA** (restricted use)
Low Order Adaptation LA20
3AG24150AA**
Low Order Adaptation Connection LAC40
3AG24327AA**
Low Order matrix Board LX160
3AG24328AA**
Alarm Board
3AG24262AA**
2x 10GE LAN Port /XFP
3AG24476AA**
ISA-ES64 Server Board
3AG24371AA**
1GBE ZX SFP module
1AB187280042
STM-16 CWDM SFP modules
1AB196340009...0016, 0026...0033
STM-16 DWDM SFP modules
1AB231410001...0046
STM-64 DWDM XFP modules
1AB356630001...0044
New HW items introduced with R4.5:
None
For the current released HW part numbers and additional information please refer to
Equipping Options List 3AG24101BBAA.
4.3
Documentation
CD-ROM Costumer Documentation R4.5 3AG24399BFAA

4.4
SW maintenance raw patch releases
Note: The RP installation guide is part of the related RP package on SWDL server.
R4.5.1 RP1 CI:
mibIM2-SKY62-11F.ppc.rpm
fwa_pr-SKY62-11F.ppc.rpm
78mcc_pr-SKY62-11F.ppc.rpm
RP1 installation: update based on R4.5.1 CI, no traffic impact.
ED04
November 2009
14 of 33
INSTALLATION PROCEDURE
5.1
New installation
All software delivery items will be installed via a CD-ROM drive connected to the Craft
Terminal (CT). The detailed description how this release has to be installed, can be found in
Installation and Start-Up Manual FLC Software and in CT Basic Operator's Handbook Chapter
Installation Procedure.
5.2
In service update / upgrade
The R4.5 releases cover the In-Service Upgrades as per the following table:
TO
FROM
4.3.1x
4.3.2A CI
4.5
4.5.1 CI
4.5.1
SKY62-02P
SKY62-02V
SKY62-13D
ISUSKY62-01J
rel. under PLM
control
not planned
ISUSKY62-10A
rel. under PLM
control
not planned
ISUSKY62-20C
not planned
not planned
4.5
supported
not planned
not planned
4.5.1 CI
4.5.1
Procedure details are described inside the Maintenance Handbook.

Known
-
restrictions related to ISU:

MSP/MSSPRING traffic must be on the protected line before ISU is started
Risk of few seconds traffic hits for XCs located in OED1662
Risk of B3 errors for XCs located in OED1670
Fallback: In rare cases, the rollback to the start release fails (1 FLC ok, 1 FLC nok)
In very rare cases, there might be traffic hits of up to a few hundreds of milliseconds
for XCs located on STM-N cards in mainshelf
Risk of traffic hits of up to double digit seconds for connections located in ISA ES64
During upgrade of a LO shelf configuration, the system will execute a cold-start of the LO
shelf causing all connections of the LO shelf to be interrupted temporarily.

ED04
November 2009
15 of 33
6
6.1
SOLVED PROBLEMS/RESTRICTIONS/WARNINGS
Solved problems/restrictions/warnings R4.5.1 CI
6.1.1 Solved problems

DDTs SLSks45485
After repair of control plane communication failure or a node application restart, a race
condition in the signalling protocol resynchronisation with upstream and downstream neighbour
could result in a local alarm on the node not being correctly reported to the ingress node. The
traffic will not be restored and remain failed.
DDTs SLSks54199
LO shelf: Due to a potential MX-internal routing problem, existing traffic might be affected in
rare cases during implementing new LO cross-connections.
DDTs SLSks54264
In very rare cases protection channels of MS-SPRing might be wrongly squelched in case of a
fibre cut.
DDTs SLSks54536
In rare cases of SPI bus problems, the HO matrix EPS could trigger a cold-start of IO boards,
which will cause a temporary traffic impact on the boards affected
DDTs SLSks54577
P16S4-1 board: In very rare cases a re-configuration from STM-4 to STM-1 might not have been
completed successfully on standby matrix, thus traffic can be affected after matrix EPS due to
pending configuration completion on new active matrix.
DDTs SLSks54995
In case of ASON drop ports being located on LAX boards, and LAX boards being re-configured,
the GMRE is informed about the unavailability of the active LAX card and all AU4VC4 termination connections are deleted, so LO ASON traffic is impacted during this time.
DDTs SLSks55110
OED: Transmitted signal of 3rd port of P16OS1 board might include B1 B2 B3 errors due to a
cross talk on P16OS1 board.
DDTs SLSks55152
Changing the concatenation structure on S-64 XFP ports might cause the path provisioning to
fail under special condition. For this rare case, new paths cannot be implemented and UNEQ
alarm will be reported on neighbour node.
6.1.2 Solved problems with workaround
DDTs SLSks43793
If the module configuration is changed from STM4 to STM1, sometimes a LOF alarm is reported
and it is not possible to establish the transmission.
Workaround for previous releases: Remove all connections and STM-1 configuration of affected
group and re-configure it to STM-4. Remove the STM-4 configurations again and re-provision
STM-1 modules to start new commissioning.

ED04
November 2009
16 of 33
DDTs SLSks52242
OED70: In rare cases, an OED70 Matrix switch might lead to a RUTM alarm for A12OS1 boards.
Workaround for previous releases: Push / Pull the module, if even this short traffic impact is
not acceptable contact TEC.
DDTs SLSks52496
OED70: In rare cases, an OED70 Matrix switch might lead to a RUTM alarm for modules of the
P16OS1 board.
Workaround for previous releases: Push / Pull the module, if even this short traffic impact is
not acceptable contact TEC.
DDTs SLSks53780
If more than 64 MSP groups are configured in main shelf, ghost CPE alarms might be reported
permanently or temporarily.
Workaround for previous releases: perform a warm reset of active matrix.
DDTs SLSks54339
In rare cases, an FLC switch, which was triggered via EP dialog, might fail even if reported
successful on GUI. Correct status can be verified according to current reported state on the
FLCs.
Workaround for previous releases: repeat this action.
DDTs SLSks54605
Closing "CS Configuration" of EP Dialog window with "OK" button will de-configure external NTP
servers and OSI stack configuration (Area Address, System Id).
As corrective action, NTP servers and OSI stack configuration have to be reconfigured via
Comm/Routing dialog.
Workaround for previous releases: Close the EP Dialog via "Cancel".
DDTs SLSks54612
When the LAN between 1678MCC GNE and DCN router is split into two segments, e.g. due to a
LAN cable problem or failure of an intermediate L2 switch, the IP connection between NMS and
the local node fails, despite of possibly available DCN redundancy (via LAPD) and enabled OSPF
routing protocol.
Workaround for previous releases: The problem is solved by explicit advertising of additional
host routes for the active FLC.
DDTs SLSks54687
The operation Laser Forced OFF/ON is not executed correctly on P16S1 boards (3AG 24183
AA**). Instead of only forcing off/on the laser at the requested port, the laser will also be
forced off/on at one additional port according the table below.
Laser off/on
Port requested
1
2
3
4
5
6
ED04
November 2009
Laser off/on
Port(s) executed
1
1&2
1&3
1&4
2&5
2&6
17 of 33
7
8
9
10
11
12
13
14
15
16
2&7
2&8
3&9
3 & 10
3 & 11
3 & 12
4 & 13
4 & 14
4 & 15
4 & 16
Workaround for previous releases: Toggle ALS on the additional port (1, 2, 3, 4) to bring the
laser back to its original status.
6.1.3 Solved functional restrictions and warnings
DDTs SLSks50244
OED70: A HW problem is discovered on port board 3AL80948AAAA 01, where each GTLP is
connected via two ingress to ISPB instead of one. Due to this problem access to ISPB might fail.
If more than 12 boards are inserted RUP alarm will appear on standby HO-SMX after download
or EPS.
Workaround for previous releases: Only a limited number of P16OS1 boards (3AL80948AAAA 01)
per shelf prevents the problem. Because each of them needs to be counted like two:
- in single configuration of P16OS1 only 8 boards should be configured per shelf instead of 16
and
- in mixed configuration one P16OS1 of this special type has to be counted like two usual IO
boards.
DDTs SLSks51145
Battery failure on PSF boards is not alarmed. Before starting maintenance actions the power
redundancy has to be checked via Health Care tool.
DDTs SLSks52488
Transparency of N1/K3 bytes is suspended for use of Internal Tandem Connection Monitoring
(ITC). ITC is enabled on the whole node per default. This influences end-to-end usage of N1 /
K3 bytes, e.g. external TCM.
DDTS SLSks53470
OED62: In marginal conditions of some SYNTH16 cards (3AL98038AC**/AD**) bit errors may
occur of less than 5 ES/SES within 2-48 hours
DDTs SLSks54333
LO-shelf: When force command for MSP between LAC40 and LA20 is released on LAC40, the
traffic is affected for 10 seconds after WTR.
DDTs SLSks54388
In rare cases alarm time stamps of clearing time could be reported earlier than appearing time
DDTs SLSks54423
In exceptional cases, an MS-SPRing switch might be delayed after fibre cut due to a simultaneous matrix switch and traffic is interrupted in the range of 2-3digit seconds.
ED04
November 2009
18 of 33
DDTS SLSks54425
OED62: In very rare cases it may happen that after power up of the OED1662 shelf the SYNTH16
cards report a RMAF or RMBF alarm.
DDTs SLSks54432
OED62: RI data of CONGI board are not updated after replacement.
DDTs SLSks54588
PM records with elapsed time not equal to interval time are not archived on NM.
DDTs SLSks54615
Reversion by bridge and roll to nominal route fails if signal degrade is on current route
DDTs SLSks54959
Transparency of N1 & K3 bytes is set hard-coded, ie. the Serial Compound Link functionality is
not supported. Starting with R4.5.1 this transparency is configurable per node.
DDTs SLSks54963
After finishing ISU, external reference clocks T1 might enter in lockout state when
configuration of synchronization will be changed.
Workaround for previous releases: Release Lockout state via menu commands
6.1.4 Solved specific system behaviours
DDTs SLSks42066
In case one IO board cannot be reached via ISPB bus, a RUP alarm is reported and the related
board is periodically cold started as internal repair action. During internal cold start traffic of
this board is impacted.
DDTs SLSks54620
Manual reversion is prevented due to pending SF on a port of nominal route.
DDTs SLSks54886
Loosing the SDH signal, the laser of the GBE port on client side might remain switched-on due
to auto-negotiation. For this case, the GBE traffic will be impacted until the SDH circuit is
restored.
6.2
Solved problems/restrictions/warnings R4.5.1 RP1 CI

DDTs SLSks55518
1GE Ethernet PM: End time of period set incorrectly.
DDTs SLSks55543:
1GE Ethernet PM: TRSEF counter not uploaded into the PMDS tool of NM.
DDTs SLSks55622
1GE Ethernet PM: Force PM Collection might cause an Emilm DXC crash.
DDTs SLSks55585
1GE Ethernet PM: EthPM Counter values at midnight GMT are not reported towards NM.
ED04
November 2009
19 of 33
6.3
Solved problems/restrictions/warnings R4.5.1
6.3.1 Solved problems

DDTs SLSks54984
OED62: A forced switch from protected to protecting SYNTH16 boards leads to a traffic hit of
some seconds if IO EPS is forced to protecting currently. There is no hit if SYNTH16 is forced to
protected (during EPS is forced to protecting) or if IO EPS is forced to protected side.
DDTs SLSks55354
OED62: If CRC mode is changed during PM is enabled at PM will be disabled by accident.
DDTs SLSks56282
In configurations with LAX boards it might happen in rare cases that the AU4 termination is
rejected even if resources are still available.
6.3.2 Solved problems with workaround
DDTs SLSks47016
Initialization of P16S16, P16S1 and P16S1-4 boards will fail if terminal loopbacks are configured
on ports 9 to 12. This happens after cold start of system, insertion of boards or during ISU.
Workaround for previous releases: Release terminal loopbacks after usage.
DDTs SLSks50741
After restoring persistency data with forced MSP switches on LAC40/LA20 traffic of the related
link might be down.
Workaround for previous releases:
The release of MSP switch recovers the traffic.
In general, MSP switches have to be released on LAC40/LA20 before creating a backup.
DDTs SLSks56161
10GE EVPL configuration via 1354RM is not written in HW correctly.
Workaround for previous releases: Configure 10GE EVPL via NM or CT.
DDTs SLSks54353
OSPF Area Configuration: After executing a dedicated sequence of actions the DELETE button
for default OSPF area (0.0.0.0) might not be greyed out. Even in this case the default OSPF
area should not be deleted otherwise it wont be possible to recreate it again.
6.3.4 Solved specific system behaviours
DDTs SLSks50587
In LCAS configuration, the failing of all (received) members has to be reported by TLCR alarm
on PTC and the termination of the virtual concatenated signal (VCnXV) will report SSF alarm as
well. If either TLCR or SSF alarm reporting is enabled in alarm profile, both alarms are
reported - even if LCAS is disabled and TLCR alarm shouldnt be raised.
DDTs SLSks51084
EBER alarm is not reported correctly on MSTTP in AS and it has to be ignored.
DDTs SLSks51336
OED62: Upon an EPS switch of SYNTH16 boards the FAN, which is connected to CONGI board in
slot 1, reports a ghost RUP alarm during one second.
ED04
November 2009
20 of 33
DDTs SLSks55313
The collection of PM history fails on NM if the related TP is in switched state of MSP/MS-SPRing.

ED04
November 2009
21 of 33
KNOWN PROBLEMS/RESTRICTIONS/WARNINGS
This chapter contains all known potentially customer relevant problems for the 1678 Metro
Core Connect R4.5 system working under normal operating conditions.
7.1
Known problems/restrictions/warnings in R4.5.x
7.1.1 Known problems

DDTs SLSks31753
The T5 SSM information is wrong if connected to T0.
DDTs SLSks31755
If the clock input is configured to T3, a 2 Mbit/s signal is accepted.
DDTs SLSks32406
Creating/deleting a board in a 1670 OED shelf leads to a hit that looks like being 3 seconds, if
an I/O protection on another board is active.
In fact there two small hits that are about 3 seconds apart which is wrongly displayed on the
measurement device.
DDTs SLSks34863
PM current and history data for one interval on the two LAX40 boards can be different after a
protection switch (EPS), if one of the two boards is plugged in after the beginning of the
interval.
DDTs SLSks35425
After disabling the threshold supervision on 1662 OED only the 24h threshold crossing alarms
are cleared immediately. The 15m threshold crossing alarms are only cleared after the next
15m interval.
DDTs SLSks36161
Enabling the LCAS mode for GBE at only one end of the SDH network would interrupt existing
traffic. Make sure that LCAS is enabled or disabled at both sides before control path activation
is used to establish traffic.
DDTs SLSks36290
An LCAS transition between 6 Vc4vs and 7 Vc4vs may lead to a packet loss of approx. 7 pkts, if
during the transition the traffic on the 1GbE port is more than 97.9%.
DDTs SLSks36323
Interworking between 1678MCC and Lambda Gate is disturbed on DCC-RSOH by error frames
and CRC errors.
DDTs SLSks37385
In the LCAS monitoring view the received control word is only reliable for VCs which are active
in transmit direction.
DDTs SLSks37431
When taking a P16GE board in service without any module plugged in, the LED may remain red
until the first module is plugged in.

ED04
November 2009
22 of 33
DDTs SLSks38071
An SSF alarm on a Vc4XV, which is a consequence of an SDH alarm on a Vc4v, may persist after
enabling LCAS, even if the primary alarm is cleared. This is only a wrong alarm indication, and
it is cleared with the first control path activation (ie. with the initiation of real traffic).
DDTs SLSks39512
A loss of an OOB IP tunnel is not signalized to the operator and GMRE still operates with a nonredundant control plane.
DDTs SLSks42694
If the mainshelf-matrix is configured with the wrong size no RUTM alarm is raised, i.e. the
operator can not detect directly, why the matrix does not become active.
DDTs SLSks46966
System shall report GFP LOF but no alarm is raised.
DDTs SLSks47038
GbE LCAS: According to the standard a LCAS source should continue sending traffic with the
last member state in case of a unidirectional failure of all members of a VCG, but the system
blocks entirely the transmit side.
DDTs SLSks47097
In case of a 1 GbE connection with LCAS enabled, which is split over more than one STM-N link,
incoming traffic will be lost in case of a bidirectional link failure on one local STM-N link
(terminated on 1678MCC) if the affected VCG member is not the last one. In the opposite
direction traffic is OK with reduced BW (LCAS is acting as expected).
Important note: this problem is not present in case of having GbE to GbE EPL service between
two 1678MCC nodes.
DDTs SLSks47256
At PM-creation on TU12 it may occur that TCN for 15min NE or FE (BBE, ES and SES) is reported
and cleared simultaneously (same second), if threshold crossed notifications are set for 15min
and 24h for NE and FE (BBE,ES and SES) prior to deleting of PM on TU12.
DDTs SLSks47296
During an InServiceUpgrade the IO-EPS in the OEDs is not working.
DDTs SLSks49244
For disconnected ports the reported J1/C2 may be not equal to 0.
DDTs SLSks56038
GMRE: In case of CSF (Communication Subsystem Failure) alarms on both LAX boards the
terminated LSPs are torn down as long as the CSF alarm is active.
DDTs SLSks56550
GMRE: If one leg of a MSP configuration fails during the other leg is already in a failing
condition, the restoration of this traffic might take up to 5-30 seconds. Additionally LAPD on
protecting leg is deleted.

ED04
November 2009
23 of 33
7.1.2 Known problems with workaround

DDTs SLSks30990
It is not possible to force T0 (system clock) to the internal oscillator - neither forced freerun
nor forced holdover.
Workaround: Lockout of all timing sources forces the system clock implicitly to holdover.
DDTs SLSks33211
If the F-interface cable is plugged out/in during connection to the NE, it may happen that the
connection is not re-established automatically.
Workaround:
1. Stop the 1320CT application
2. Disable and enable the LAN connection
3. Restart the 1320CT application
DDTs SLSks34235
Restoring saved configuration data and starting the application, the configuration is not
reloaded automatically to the SLCs (MXxxxGE).
Workaround: Reset all the SLCs manual.
DDTs SLSks36384
Control Plane failures do not affect the Dataplane traffic.
If however the Operator tries to de-implement the path when there is a control plane failure,
the resources are freed from the Head node up to the point where there is no CP
communication. The remaining path resources remain allocated until the CP failure is repaired.
Workaround: Free the remaining resources via the CLI from Tail node (config lsp lspindex <123>
adminState Down).
DDTs SLSks38999
Equipment Provisioning: After changing the active EM address via EP dialog, the SH/CT
connection to the NE will break.
Workaround: Restart the application or perform an FLC switch.
DDTs SLSks45477
Canceling the TP Search, by pressing the cancel Button, can sometimes block the work with the
USM. No other activities are possible.
Workaround: Restart the emlim (EMLIMDXCQ3) of this Network Element on NM.
DDTs SLSks46312
LCAS Bandwidth modification on GbE pathes using RM may lead to traffic hits if the reduction
of the bandwidth is done in the wrong way (single step).
Workaround:
It has to be proceeded in two steps as follows:
- server trail deactivation
- removal of those deactivated server trails
DDTs SLSks48208
If the type of OSI protocol stack is changed, e.g. from level 2 IS to level 1 IS, the change might
not be recognized by all adjacent 1678 systems.
Workaround: An FLC switch on those systems will resolve the problem.

ED04
November 2009
24 of 33
DDTs SLSks50241
Event Log filtering may block the application Event Log Browsing on local CT.
Workaround: Within the file C:/ALCATEL/CT-Kv3.3.0/elb/conf/LogBrowsing.cfg the parameter
Q3_PROTOCOL has to be changed from DIRECT to NESIM.
DDTs SLSks51072
Using the OED70, the HCMATRIX reboots once opening the transmission view of link board slot
29.
Workaround: Use the alarm list to check alarms on this port.
DDTs SLSks54240
In very rare cases, after an FLC switch it might happen that all LAPDs are down and report CSF
alarm.
Workaround: Perform HO matrix switch and reset the new standby matrix.
DDTs SLSks56150
GMRE: After restoring both SNCP legs of a PRC path, the reversion is blocked if the restored
legs occupy the nominal route of other legs.
Workaround: To rectify, the backup of spare leg should be moved from TE links of main
nominal.
DDTs SLSks56217
In rare cases the OSPF process gets blocked. This leads to loss of OSPF functionality and loss of
IP communication possibly.
Workaround: Reset DCR board of affected FLC.
DDTs SLSks56240
GMRE: A path might be reported as Not Ready To Revert due to control plane communication
failure on transit node even if no CP failure is present, so it could be reverted.
Workaround: The FLC should be switched on transit node reporting the CP failure to neighbour.
DDTs SLSks56362
If the Port Mode is set to AUTO, it is not possible to change the ASAP.
Workaround: Set the Port Mode to MONITORED.
7.1.3 Functional restrictions and warnings
DDTs SLSks31236
Line loopback of a concatenated signal is not possible.
DDTs SLSks31342
J0 works only in 16-byte mode and not in single-byte mode.
DDTs SLSks32150
Line loop does not reflect alarms inserted into the signal.
DDTs SLSks32265
On STM-16 and STM-64 boards an internal loop with AIS is not possible.
DDTs SLSks33281
If LSPs are configured with different labels for input and output on an intermediate node, it
may happen that a high prio LSP preempts more than one low prio LSP.

ED04
November 2009
25 of 33
DDTs SLSks33767
In rare cases the switching times for STM-1e equipment protection may exceed 50ms (up to
100ms).
DDTs SLSks33794
The WTR time for the timing source is fixed to 30s, instead of 5 min as required by ITU-T.
Furthermore, dependent on the outage of the timing source, it may happen that the WTR
time is up to about 60s.
DDTs SLSks34296 Within the 1662 OED it is not possible to create more than one protection
group for the left and for the right side. The LPROT board can only be inserted into slot 2 and
slot 16.
DDTs SLSks34741
The F4 filter of GbE TPs are 5 seconds for raising time and 10 s for clearing time independently
of the configured values.
DDTs SLSks34898
Even if eight unprotected 2 Mbit/s boards can be handled in one 1662 OED shelf, PM can only
be configured for six 2 Mbit/s boards, namely the slots dedicated to working boards. Even if
there are less than six boards plugged in the shelf the protection slots cannot do PM.
DDTs SLSks34937
During broken LAN connection between HC-SMX and FLC a transmission alarm appears. The
time stamp of the reported alarm was not related to the event time but to the time when the
LAN connection was re-established.
DDTs SLSks35244
The received C2 signal label is not set to unequipped if a cross-connection on a Vc4V is
deleted. It keeps his old value (in normal case '27').
DDTs SLSks35365
GbE: VC4V TIM not implemented
DDTs SLSks35643
Backup/Restore with GMRE in Network Context is only supported with RM/ASON, and succeeds
only if the Databearer and TELink configuration has not changed since the last Backup was
stored. Thus it is absolutely mandatory to perform a backup operation after each configuration
change of TELink, Databearer or other GMRE interface.
If a restore is performed with a different interface configuration, the Mark Audit operation of
RM can fail. This situation cannot be resolved without traffic loss of all GMRE-controlled
connections on the node in restore phase. The traffic is impacted until the completion of the
RM Global Download operation.
The restore can cause traffic interruptions of GMRE traffic which has been rerouted between
backup and restore, e.g. due to restoration. To limit the potential impact the restore
procedure described in the handbook mandates to move pass-through traffic away from the
node to restore before starting the restore action.

ED04
November 2009
26 of 33
DDTs SLSks35693
During pre-emtion, if there are multiple locations with the same pre-emption priority available
within a TELink, with the same number of affected connections, the one with the lowest Svalue and not the one with the least concatenation level is chosen.
DDTs SLSks35823
ALS is not working on STM64 boards in case of a configured terminal loop.
DDTs SLSks36469
For enabled LCAS the P16GEFC board sends the LCAS control word ADD instead of DNU from
source side to sink side.
DDTs SLSks36761
For a P16GEFC, P8GEFC or P4GEFC board all ports must be configured either with VC4XV or
VC3XV. It is not possible to have a mixture of VC4XV and VC3XV on the same board.
DDTs SLSks36829
Sometime the cross-connection on an AU3#2 is not working properly (B3 errors).
DDTs SLSks37270
GbE: LOF of GFP frames not implemented
DDTs SLSks37725
Single Ended MSP 1:N does not work on 1670OED for STM-4 when mixed configuration AU4 and
AU4-4c is used.
DDTs SLSks37996
The 2 sec restoration requirement is not fulfilled in contention scenarios.
DDTs SLSks38661
After inserting P16S1N in the 1670 OED shelf it may happen that the internal clock of shelf goes
to holdover which is indicated by a TIP alarm at CT. After a few seconds the timing is working
well and the alarm disappears.
DDTs SLSks38692
On 1662 OED EPS can exceed switching time of 50ms if WTR is active.
DDTs SLSks38977
1GE: If we have a transition of the timing generator from tracking to free running (i.e. the time
in state tracking was not sufficient to have the preferred transition from tracking to holdover)
and simultaneously an LCAS state transition is caused by failed member paths, the following
may happen:
- The traffic interruption is longer (about 30 seconds) than we normally expect for LCAS state
transitions.
- Some of the paths may have no SDH alarms, but cannot be deskewed.
DDTs SLSks39862
In case of more than one restoration within a time interval of about 35 seconds, the second
restoration is not a fast restoration and can take more than 35 seconds.
DDTs SLSks40901
A 1GbEth board does not drop or ignore received pause frames.
ED04
November 2009
27 of 33
DDTs SLSks40960
For GBE virtual concatenation with LCAS the transmission delay of the individual paths can be
compensated up to 15ms. This is sufficient for usual network configurations. But for (testing)
cases, where the differential delay cannot be compensated, the paths which cannot be aligned
(MND, member not deskewable alarm) are not excluded properly from the demapping process
in the VOLTA ASIC. Therefore the traffic is instable. The problem occurs only in case of
interworking of GBE ports of the 1678MCC with other types of NEs using the (standardized) DNU
control for failed channels. With 1678MCC at both ends of the SDH/SONET network the problem
does not occur, because it uses the IDLE control also for failed channels.
IDLE channels are removed properly from demapping.
DDTs SLSks41172
After removing a derived reference, selected or not selected, by inserting a LOS signal, an
alarm SSF appears, which is correct. When the inserted LOS is removed (after about 10s) the
SSF disappears and a Frequency Offset Alarm is raised for about 1s.
This is wrong and misleading for the operator.
DDTs SLSks41846
I16.1 module can not be used in the 1662OED.
DDTs SLSks44508
FLC switches caused by plug out of the active FLC may take several minutes.
DDTs SLSks44554
When a Mx-EPS switch is triggered manually it takes several seconds until the switch is
completed on the HW. During this time there is no indication in the GUI that there is a switch
ongoing.
DDTs SLSks44856
If NM is connected to the NE only via DCC the supervision is interrupted during ISU.
DDTs SLSks45483
If a bidirectional Gigabit Ethernet cross-connection is split and one of the unidirectional crossconnections is deactivated and activated again, there will be a transient TIM alarm for a few
seconds despite TIM is not supported.
DDTs SLSks45908
In OED1662 and OED1670 the Suspect Flag after PM creation is not set.
DDTs SLSks46812
A 1 GbE port might indicate the auto-negotiation status of the remote side wrongly as
"enabled" while the remote side is in fact in manual state.
DDTs SLSks46918
The switching time of a dual ended 1:N MSP on a OED70 does not fulfil the required switching
time of 50 ms. Sometimes the switching time is up to 250 ms.
DDTs SLSks46983
A high amount of OSPF instances in the network running in at least 2 different OSPF areas
might lead to repeated restarts of the OSPF process.
ED04
November 2009
28 of 33
DDTs SLSks47049
ISUs that include an upgrade of the NEWTON FPGA cause an interruption on 10GE EPL traffic.
DDTs SLSks47053
ISUs that include an upgrade of the NEWTON FPGA cause an interruption on 10GE EVPL traffic.
DDTs SLSks47057
In rare cases plug out / plug in of a STM64 V board may result in a LOP on MV642 module
DDTs SLSks47196
During 10 GE operation the displayed counter values for the TxFrame counter show a variance
due to not exactly synchronized time intervals. Nevertheless the total number of frames
counted is correct.
DDTs SLSks47281
T4 (2 MHz output signal) cannot be used as reference for another equipment. Its usage is limited
to an SSU application.
DDTs SLSks47828
If a 1 GbE port has Auto-negotiation enabled, it might not be put into service if the signal is
looped on itself.
DDTs SLSks48133
If there is a LOS on the incoming signal of a 1GbEth port, and an internal loop of is applied, the
consequent action will switch off the laser of this port.
DDTs SLSks48358
OSI Reachable Address Prefixes (RAP) are not supported.
DDTs SLSks48423
Frames with multiple failures might be counted multiple times in error counters.
DDTs SLSks48440
Using a GBEVCG with LCAS enabled, deleting VCs from it might leave the deleted members
with incorrect control words. The functionality of the remaining members in the VCG is not
affected.
DDTs SLSks48592
UNEQ detection of all GbE boards might be corrupted by a valid GFP mapped Ethernet signal
generated by a port in slot position 2.
DDTs SLSks48630
The 1GbE board has the limitation not to rise the Signal Degrade alarm if it receives B3 errors
from TDM side. Nevertheless do B3 errors result in PM counting.
DDTs SLSks48721
In rare cases it might occur that after a MX switch all 1-day TCA alarms are re-reported, which
were already reported before.
DDTs SLSks48797
Using the 1678 GbE interface, runt frames in the in direction, i.e. undersized frames with
correct FCS from Ethernet to TDM side, are discarded as expected. But they are not counted in
any of the available counters. They should be counted in TRSEF counter.
ED04
November 2009
29 of 33
DDTs SLSks49471
If a GBE port receives from TDM side a GFP frame without user data, the payload type of the
frame cannot be determined exactly. Therefore the default assumption is that all frames of
this kind are CSF frames. Therefore, any received unexpected payload type is reported as CSF.
DDTs SLSks50125
As RUP alarm is not evaluated by GMRE, the local GMRE will continue to operate in normal
mode in case. This means that inactive backups will not be rerouted, and node will continue to
advertise resources. If cause for RUP alarm is traffic affecting the neighboring GMREs will
trigger restoration.
DDTs SLSks50320
If GbE paths are setup using Odd and Even diverse routing but without LCAS enabled, there
could be total traffic loss if no diverse routes are found during restoration. It is recommended
for GbE paths to enable LCAS with Odd and Even diverse routing or to avoid Odd and Even
diverse routing.
DDTs SLSks50507
In the ES64 ZIC it is not possible to modify a traffic descriptor (TD) after activating.
DDTs SLSks50582
In the ES64 ZIC all ports (1-252) are shown even though only port numbers 1-64 & 129-192 are
valid.
DDTs SLSks50607
In case of an active SQM alarm, the 10GE board with a VC4xv configuration will generate
additionally the LOA alarm.
DDTs SLSks50816
In a scenario with a 1GbE board receiving a User Payload Mismatch from TDM side, it will not
generate a CSF indication even if bidirectional server fault propagation is enabled.
DDTs SLSks50822
On 1GE ports, there is no aAIS (consequent action) generation after/upon detection of PLTM
(dPLTM). Instead, the GBE traffic coming from the SDH/TDM-side is forwarded.
DDTs SLSks51296
In very rare cases, as a result of HO MX EPS the XFP/SFP modules may be alarmed with RUTM,
traffic will be not affected.
Workaround: perform manual HO MX EPS
DDTs SLSks54135
All CT users have always operator permissions, even if the role in the profile is different.
ES64: If invalid C2 value is received on VCG, an SSF alarm is raised instead of PLTM alarm.
ES64: ES64 facilities pass undersized (runt) Ethernet frames. The ES64 pads them to 64 bytes.
ES64: Per-Q PM octet counters do not count correctly for all frame sizes. The Per-Q counters
are inaccurate by up to four bytes less per frame.

ED04
November 2009
30 of 33
DDTs SLSks54953
In 10GE EVPL configurations the VCG #65 can be configured but traffic wont run.
DDTs SLSks55787
In rare cases, autonomous DCR resets might occur on active FLC. As a consequence, external
communication via LAN or DCC will be impacted for approx. one minute.
DDTs SLSks56140
If the upload of the event logs is aborted in the CT event log browser the supervision is lost and
needs to be restarted.
DDTs SLSks56351
GMRE: If two adjacent nodes are restarted in parallel the delayed response of one node could
cause an unnecessary recovery cycle of the other node, whereby the overall recovery period is
extended.
7.1.4 Specific system behaviours
DDTs SLSks34638
If you perform a lockout action on a protected LO connection immediately after a forced
switch (to protected or protecting side) the protection state in the cross-connection dialogue is
not updated correctly: forced is shown instead of lockout.
Correcting action:
Refresh the dialogue using the 'search' button or use a 'release force' before the 'lockout'.
DDTs SLSks36744
2F-MSSPRING should not be combined with path monitoring on the ring. A monitor on a path
that is part of an 2F-MSSPRING protection scheme will only work as long as the monitored path
runs over the nominal working section.
DDTs SLSks39473
On a STM-64 board, a line loop is only possible if the port is cross connected.
DDTs SLSks46953
In case of a total loss of capacity in one direction on a 1GE port with LCAS enabled an
unexpected BWR alarm is reported additionally to the expected SSF.
DDTs SLSks48945
If in an MSP 1:N protection scheme two working channels show failure conditions at the same
time, the protection mechanism does not take the channel ID into account. Therefore it is not
guaranteed that the section with the lowest section numbers takes priority.
DDTs SLSks49628
With double simultaneous fibre cuts where both I-NNI link are in one 1+1 MSP protection group,
the restoration times are not below 2 seconds. Since both MSP links are affected, there is no
50msec protection. Furthermore, the dual fibre alarms are reported to GMRE slowly from the
hardware resulting in restoration times above 2 secs and in the region of up to 4 secs.
DDTs SLSks48055
After cold-start of a STM-16/OC48 board, a LOF that was declared before is not re-declared.
Instead, a LOP is reported.

ED04
November 2009
31 of 33
DDTs SLSks48461
Using the 1678 GbE interface, the frames with a frame size greater than 9796 octets are being
discarded when going from TDM to the Ethernet IF as expected. But they are not being counted
neither in the TDFout, nor in TRSEFout counter, but in the TRCFout counter.
DDTs SLSks48660
With the 1678 GBE interface, the raise time for the alarm LOMF is 1.4s, instead of 2.5s. Other
alarm types are not affected.
DDTs SLSks49274
Using the 1678 GbE interface, runt frames in the out direction, i.e. undersized frames < 64
Bytes with correct FCS transmitted from TDM to Ethernet side, are treated as follows:
- frame length below 18 Bytes: they are discarded and counted in TRSEFout counter, which is
the required behaviour.
- frame length between 18 Bytes and 64 Bytes: they are not discarded and not counted in the
TRSEF counter.
DDTs SLSks50004
When disterminating AU4 in non-supported way (delete AU4-VC4 Crossconnection), then this
low order configuration is kept and the alarm status can become inconsistent.
Workaround:
Normal way is to disterminate AU4 using the "Disterminate TP" Pulldown Menu in Transmission
View or Port Details View. Then all cross connection (high and low order) are deleted.
Corrective action:
Reestablish higher order cross connection and disterminate TP.
DDTs SLSks50351
Upon generation of an ES64 EPS protection group
- a CSF alarm is visible on CT for about 30s on both involved ES64 boards.
- a RUP alarm is visible on CT for 4 minutes on the protecting ES64
- an ICP alarm is present on CT for the protecting ES64 and stays present during the DL state.
- the protecting ES64 shows a download state for about 5 minutes.
- after the DL both ES64 boards show CSF alarm again for about 1 minute.
- all alarm disappear
DDTs SLSks50520
On 1GE ports, FCS errored frames are not discarded in the OUT-direction from TDM to the
Ethernet line. Such frames are counted in the TRSEF counter.
DDTs SLSks50656
On 1GE ports, as consequence of auto-negotiation failure on the GE link, no CSF frame is sent if
the laser is operated as forced on.
DDTs SLSks50746
Restore with a large amount of CCs may suggest the operator that it has not finished with
success even if the procedure has completed.
Workaround:
If not sure that the restore has finished, retry the procedure.
DDTs SLSks50884
With the 1678 GBE LCAS implementation, an activated member VC4V in a failure state is
reported as "idle", instead of "failure".
ED04
November 2009
32 of 33
DDTs SLSks50894
The GbE LCAS implementation shows wrong alarm behaviour at remote LCAS in case of total
local failure (TLCT and TLCR):
The remote LCAS termination shows:
- SSF/TLCR and TLCT on VC4XV, and
- WR on VC4XV,
which are not expected.
DDTs SLSks51132
On systems, configured with more than 8 OEDs, it may happen that changing the CS
Configuration (add other IP hosts or change NTP server address) leads to the error message:
"Request timed out, no response from CSServer".
Nevertheless configuration change is done but takes longer. Later configuration check (max. 1
hour) will show correct state.
DDTs SLSks51146
The 10 GE LCAS implementation shows a bandwidth reduced alarm BWR even if VC4s are
created but not activated or cross-connected on the port.
DDTs SLSks51164
If there are bit errors on the nominal route, reversion to nominal will not succeed. The revert
to nominal using bridge and roll will be retried periodically but not succeed.
In such situations, the Operator is recommended to check the nominal route for bit errors and
repair them. Until the bit errors are repaired, it is recommended to modify such links, with
signal degrade alarms, to administrative state ShuttingDown to prevent new traffic using the
links.
ES64: All Layer 2 control packets are tunnelled through the ES64 board.
ES64: Setting service of two classifiers:
vlan x pri a
vlan y pri b
Packets with vlan x pri b and vlan y pri a will pass as well, in other words, vlan+pri filtering
allows more traffic through than it should
ES64: Two classifiers, one with vlan dont care and the other with untagged, cannot be
configured to the same service.
DDTs SLSks54771
The alarm "External IF Device Problem" is not represented by an icon in board view.
DDTs SLSks56532
GMRE: GMRE does not become operational if the rack ID of the main shelf is not equal to 1.
Workaround: In case of initial installations configure the rack ID of the main shelf to 1.
End of Document
ED04
November 2009
33 of 33

3AG24101BFAAFMZZA - V1 - 1678 MCC Release 04.05.x Product Release Note

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3AG24101BFAAFMZZA - V1 - 1678 MCC Release 04.05.x Product Release Note

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent

1678 MCC | R4.5.x

3AG 24101 BFAA FMZZA

Release Note for R4.5

Update for R4.5.1 CI

Update for R4.5.1 RP1 CI

Update for R4.5.1

3AG 24101 BFAA FMZZA

DEFINITIONS AND ABBREVIATIONS ...........................................................................4

KEY FEATURES ...........................................................................................................10

PRODUCT COMPOSITION ..........................................................................................14

INSTALLATION PROCEDURE .....................................................................................15

Software 1678MCC R4.5.x ..............................................................................14

SOLVED PROBLEMS/RESTRICTIONS/WARNINGS ..................................................16

Solved problems/restrictions/warnings R4.5.1 CI ............................................16

Solved problems/restrictions/warnings R4.5.1 RP1 CI ....................................19

Solved problems/restrictions/warnings R4.5.1 ................................................20

Solved problems .............................................................................................. 16

KNOWN PROBLEMS/RESTRICTIONS/WARNINGS ...................................................22

Known problems/restrictions/warnings in R4.5.x ..........................................22

3AG 24101 BFAA FMZZA

Known problems .............................................................................................. 22

3AG 24101 BFAA

DEFINITIONS AND ABBREVIATIONS

3AG 24101 BFAA FMZZA

Customer Specific Release

High Speed Protection Board

Multi HighLevel Data Link Controller

3AG 24101 BFAA FMZZA

Key functionalities introduced with previous releases:

Nominal route handling with manual/automatic hitless reversion

Key functionalities introduced with R4.5:

3AG 24101 BFAA FMZZA

For detailed information regarding the supported features please refer to

3AG 24101 BFAA FMZZA

Software 1678MCC R4.5.x

Hardware 1678MCC R4.5.x

New HW items introduced with previous R4 releases:

CD-ROM Costumer Documentation R4.5 3AG24399BFAA

SW maintenance raw patch releases

In service update / upgrade

Procedure details are described inside the Maintenance Handbook.

restrictions related to ISU:

3AG 24101 BFAA FMZZA

6.1.1 Solved problems

3AG 24101 BFAA FMZZA

Solved problems/restrictions/warnings R4.5.1 RP1 CI

6.2.1 Solved functional restrictions and warnings

Solved problems/restrictions/warnings R4.5.1

6.3.1 Solved problems

3AG 24101 BFAA FMZZA

Known problems/restrictions/warnings in R4.5.x

7.1.1 Known problems

3AG 24101 BFAA FMZZA

3AG 24101 BFAA FMZZA

7.1.2 Known problems with workaround

3AG 24101 BFAA FMZZA

3AG 24101 BFAA FMZZA

3AG 24101 BFAA FMZZA

3AG 24101 BFAA FMZZA

3AG 24101 BFAA FMZZA

You might also like