3AG24101BDAAFMZZA - V1 - 1678 MCC Release 04.03.x Product Release Note

Alcatel-Lucent
1678 MCC | R4.3.x

Product Release Notes
3AG 24101 BDAA FMZZA

ED26
October 2012
Alcatel-Lucent Proprietary
Use pursuant to applicable agreements
REVISION HISTORY
ED
DATE
01
071219
02
ORIGINATOR
APPROVER
Release Note for R4.3
H. Bauer
A.Kemmler
080122
Update for editorials
H. Bauer
A.Kemmler
03
080307
Release Note for R4.3.1
H. Bauer
A.Kemmler
04
080605
Update for R4.3.1 RP2
H. Bauer
A.Kemmler
05
080707
Update for R4.3.1 RP3 and R4.3.11
H. Bauer
A.Kemmler
06
080912
Update for R4.3.12 and R4.3.12 RP1
H. Bauer
A.Kemmler
07
081013
Update for R4.3.2A (CI)
H. Bauer
A.Kemmler
08
081203
Update for R4.3.13, R4.3.11 RP1 and R4.3.12 RP2
H. Bauer
A.Kemmler
09
081218
Update for R4.3.1 RP4, R4.3.12 RP3, R4.3.13 RP2
H. Bauer
A.Kemmler
10
090210
Update for R4.3.1 RP5, R4.3.11 RP2, R4.3.14
H. Bauer
A.Kemmler
11
090311
Update for R4.3.12 RP4, R4.3.13 RP4, R4.3.15
H. Bauer
A.Kemmler
12
090515
Update for R4.3.16
H. Bauer
A.Kemmler
13
090529
Update for R4.3.17
H. Bauer
A.Kemmler
14
090610
Update for editorials
H. Bauer
A.Kemmler
15
090807
Update for R4.3.18
H. Bauer
A.Kemmler
16
091120
Update for R4.3.19
H. Bauer
A.Kemmler
17
091218
Update for R4.3.20
H. Bauer
A.Kemmler
18
100304
C. Wulf
A.Kemmler
19
100728
Update for R4.3.21
C. Wulf
A.Kemmler
20
101216
C.Wulf
A. Kemmler
21
110114
C.Wulf
A. Kemmler
22
110331
Update for R4.3.22
C. Wulf
J. Webster
23
110531
Update for R4.3.23
C. Wulf
J. Webster
24
111028
Update for R4.3.23 RP1, R4.3.23 RP2
C. Wulf
J. Webster
25
120209
C. Wulf
J. Webster
26
121001
C. Wulf
J. Webster

ED26
October 2012
COMMENTS
2 of 61
CONTENTS
1
REFERENCED DOCUMENTS........................................................................................6
DEFINITIONS AND ABBREVIATIONS ...........................................................................6
NEW FEATURES ..........................................................................................................12
PRODUCT COMPOSITION ..........................................................................................15

4.1
4.2
4.3
4.4
INSTALLATION PROCEDURE .....................................................................................19

5.1
5.2
Software 1678MCC R4.x...................................................................................15

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

6.1
Solved problems/restrictions/warnings R4.1.1...............................................21

6.1.1
6.1.2
6.1.3
6.2
Solved problems/restrictions/warnings R4.2 ..................................................22

6.2.1
6.2.2
6.2.3
6.2.4
6.3
Solved functional restrictions and warnings .................................................... 26
Solved problems/restrictions/warnings in R4.3.11 .........................................26

6.9.1
6.9.2
6.10
Solved problems .............................................................................................. 26
Solved problems/restrictions/warnings in R4.3.1 RP5 ...................................26

6.8.1
6.9

6.7.1
6.8
Solved problems .............................................................................................. 25

6.6.1
6.7
Solved problems .............................................................................................. 25

Solved problems with workaround ................................................................... 25
Solved restrictions and warnings ..................................................................... 25

6.5.1
6.6
Solved problems .............................................................................................. 23

Solved specific system behaviours .................................................................. 24
Solved problems/restrictions/warnings R4.3.1...............................................25

6.4.1
6.4.2
6.4.3
6.5
Solved problems .............................................................................................. 22

Solved problems/restrictions/warnings R4.3 ..................................................23

6.3.1
6.3.2
6.3.3
6.3.4
6.4

Solved problems .............................................................................................. 26

Solved problems/restrictions/warnings in R4.3.11 RP1..................................27

6.10.1 Solved functional restrictions and warnings .................................................... 27
6.10.2 Solved specific system behaviours .................................................................. 27
6.11

6.11.1 Solved problems .............................................................................................. 27

ED26
October 2012
3 of 61
6.12

6.12.1
6.12.2
6.12.3
6.12.4
6.13
Solved problems .............................................................................................. 28


6.14

6.14.1 Solved problems .............................................................................................. 29
6.15

6.15.1 Solved problems .............................................................................................. 29
6.15.2 Solved problems with workaround ................................................................... 29
6.16

6.17

6.17.1 Solved problems .............................................................................................. 31
6.18

6.19

6.19.1 Solved problems .............................................................................................. 32
6.20

6.20.1 Solved problems .............................................................................................. 32
6.21

6.21.1 Solved problems .............................................................................................. 33
6.22

6.22.1 Solved problems .............................................................................................. 34
6.23

6.23.1
6.23.2
6.23.3
6.23.4
6.24
Solved problems .............................................................................................. 36


6.24.1 Solved problems .............................................................................................. 37
6.25

6.25.1
6.25.2
6.25.3
6.25.4
6.26
Solved problems .............................................................................................. 38


6.26.1 Solved problems .............................................................................................. 38

ED26
October 2012
4 of 61
6.27

6.27.1 Solved problems .............................................................................................. 39
6.27.2 Specific system behaviours ............................................................................. 39
6.28

6.28.1 Solved problems .............................................................................................. 39
6.29

6.29.1 Solved problems .............................................................................................. 40
6.30

6.30.1 Solved specific systems behaviour .................................................................. 40
6.31

6.31.1 Solved problems .............................................................................................. 40
6.32

6.32.1 Solved problems .............................................................................................. 41
6.33

6.33.1 Solved problems .............................................................................................. 43
6.34

6.34.1 Solved problems .............................................................................................. 43
6.35

6.35.1 Solved problems .............................................................................................. 43
6.36

6.36.1 Solved problems .............................................................................................. 43
6.37

6.37.1 Solved problems .............................................................................................. 44
6.38
Solved problems/restrictions/warnings in R4.3.2A (CI) .................................44

6.38.1
6.38.2
6.38.3
6.38.4
Solved problems .............................................................................................. 44

KNOWN PROBLEMS/RESTRICTIONS/WARNINGS ...................................................45

7.1
Known problems/restrictions/warnings found in R4.1.1 ................................45

7.1.1
7.1.2
7.1.3
7.1.4
7.2
Known problems/restrictions/warnings found in R4.2 ...................................56

7.2.1
7.2.2
7.2.3
7.2.4
7.3
ED26
October 2012
Known problems .............................................................................................. 58

Known problems with workaround ................................................................... 59
Functional restrictions and warnings ............................................................... 59
Specific system behaviours ............................................................................. 60
Known problems/restrictions/warnings found in R4.3.2 CI ............................60

7.5.1

Known problems/restrictions/warnings found in R4.3.1x ..............................58

7.4.1
7.4.2
7.4.3
7.4.4
7.5
Known problems .............................................................................................. 56

Known problems/restrictions/warnings found in R4.3 ...................................57

7.3.1
7.3.2
7.3.3
7.4
Known problems .............................................................................................. 45


5 of 61
REFERENCED DOCUMENTS
[1]
[2]
[3]
Validation Release Note

Software Development Release
Feature List
DEFINITIONS AND ABBREVIATIONS
3AG 24101 BDAA FAZZA

3AG 24101 BDAA PVZZA
3AG 24101 BDAA FLZZA
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

ED26
October 2012
6 of 61
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
ED26
October 2012
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
7 of 61
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
ED26
October 2012
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
8 of 61
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
ED26
October 2012
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
9 of 61
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
ED26
October 2012
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
10 of 61
TX
U
UNI
URG
V
VCG
VCXO/VCO
VCx
VECE
VLAN
VMMF
WAN
WEEE
XFP
XFPE

ED26
October 2012
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
11 of 61
NEW FEATURES
Key functionalities introduced with R4.1.1:

- LO-Matrix (LO-matrix shelf) scalable up to 160G (1000 STM-1 equivalents) in steps of 40G
(250 STM-1 equivalents)
- STM-16/OC-48 (I-16.1/SR-1) SFP optical interface module
- 4 x 10GE LAN card with XFP interface
- 10GE rate adaptive mapping VC-4-Xv (X=1 to 64)
- EVPL (push/pop/swap) @ 10GE
- Ethernet PM counters (for 10GE)
- GbE port auto-negotiation configuration
- Serial compound links
- ISU (SW) from 1678MCC R3.2PL2 to R4.1.1 with certain limits
- ISU (SW) from 1678MCC R4.1 to R4.1.1
Key functionalities introduced with R4.2:
- 2x 10GE card / XFP
- 10GE enh. w/ LCAS
- 160G LO matrix enh. w/ LO PM & ALM board support
- ISU from R3.2P2,3,4 to R4.2 & from R4.1.1 CSR to R4.2
Note: GMRE/GMPLS is not validated for R4.2
- Colored STM-16 DWDM optical interface L-16.2 (spacing - 100 GHz)
- 1GbE ZX module
- 1GbE enhancements for PM, HPT alarms, fast LAG, fast LPT
- Event log
- 1:N MSP for S1E in OED
- NTP configuration via CT
- ISU (SW) from 1678MCC R3.2P3-P6 to R4.3
- GMPLS:
- Uni-directional signaled multicast connections w/ SBR
- Uni-directional signaled multicast connections w/ GR
- 10GE EPL drop interface in ASON domain
- GMRE deactivation
- Graceful Migration from RM to ASON manager (RM) / GMRE part (NE readiness)
- ES64 @ VC4 (ETSI):
- ES64: 2x20G switching capacity per system,
- ES64: 1:1 EPS protection
- ES64: Jumbo Frame (9242 bytes) support on ports 1..30 and 129..158
- ES64: Baby Jumbo Frame (2026 bytes) support on all ports
- ES64: VLAN label stacking
- ES64: ETH VLAN push/pop/swap
- ES64: Ethernet rate adaptive mapping VC-4-Xv (X=1 to 64) at logical port
- ES64: Up to 128 VC-4-Xv VCGs per board
- ES64: GFP-F mapping (framed, acc. G.7041)
- ES64: GFP-F (G.7041): null extension header without FCS
- ES64: Packet policing (network ingress)
- ES64: Dual rate token bucket
- ES64: Metering, Policing and Marking MEF compliant
- ES64: Color blind traffic Metering, Policing and Marking (SLA compliance)
ED26
October 2012
12 of 61
- DCN
-
ES64: Traffic management (Packet congestion & Scheduling)

ES64: 2 queues w/ strict priority scheduling
ES64: 6 queues w/ WFQ (WDRR) scheduling
ES64: W-RED congestion avoidance
ES64: Customer protocols tunneling (transparency)
ES64: Best Effort Traffic (PIR > 0, CIR = 0)
ES64: Regulated Traffic (PIR > CIR > 0)
ES64: Guaranteed Traffic (PIR = CIR > 0)
ES64: Packet classification: port
ES64: Ethernet priority bits classification (802.1Q)
ES64: ETH VLAN classification
ES64: classification acc. VLAN ID + pri-bits inside same service
ES64: 8 QoS classes
ES64: L2-Matrix is 100% non-blocking
ES64: ETH Unicast/MC/BC traffic forwarding
ES64: Packet Forwarding: port
ES64: Packet Forwarding: port + VLAN tag (outer tag lookup)
ES64: ETH Private Line
ES64: ETH Virtual Private Line
ES64: up to 128 logical ports per card
ES64: Ether Type provisioning per port
ES64: up to 2 pairs of ES64
ES64: Connection Admission Control (CAC)
ES64: CIR CAC disabling per ES64 (pair)
ES64: Preserve p-bits on VLAN push/pop
ES64: Per port counters: Green/Yellow discards, current, history (15m/24h)
ES64: Per Q counters: Green/Yellow discards, current, history (15m/24h)
ES64: 1:1 static LAG for 1GbE interconnect (CLI only)
ES64: Maximum No. of ports per LAG group: 2
ES64: Maximum No. of LAG groups per ES64: 9
ES64: 1:1 EPS for a pair of ISA-ES64 server cards
ES64: SNMP CT (ZIC) with up to 6 simultaneous sessions
ES64: Management interface via SNMP protocol stack
ES64: Enable/disable policing on a per flow basis (CLI only)
ES64: Shared traffic descriptors
ES64: Multiple traffic descriptors per service
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)
IP over OSI tunneling
DCC transparency
Note: Regression testing for GMPLS w/ HO-AU3 mapping will be executed on demand.
- none
- Serial compound links not supported
ED26
October 2012
13 of 61

- Colored STM-64 DWDM optical interface
- Configurable termination of N1/K3 bytes
- none
- none
- none
- PRC Reversion optimized for low latency (to be activated via config file)
Note: use of RP3 is supporting the reversion to any of the nominal legs, while preventing
the reversion from Spare nominal to Main nominal.
- ASON Migration with 1/10GbE
- DCN with 95MS & 135 RS DCC channels: condition GMRE not active
- none
- STM-64 loopback (on XFP boards)
Key functionalities introduced with R4.3.2 CI:
- MSA to XFP replacement
- Colored STM-64 DWDM optical interface
For detailed information regarding the supported features please refer to

[3] Feature List

ED26
October 2012
14 of 61
4
4.1
PRODUCT COMPOSITION
Software 1678MCC R4.x
Release
FLC Platform
FLC Application
FLC GMPLS
CT
R4.1.1
CORE-01J
SKY40-10Z
ION70-10Q
CT20.7.18
R4.2.0
CORE-01J
SKY42-05K
--
CT20.8.9
R4.2.1
CORE-01J
SKY42-06B
--
CT20.8.9
R4.3.1
CORE-01J
SKY55-40K
ION75-10G
CT20.8.25
R4.3.11
CORE-01J
SKY55-40M
ION75-10G
CT20.8.25
R4.3.12
CORE-01J
SKY55-41F
ION75-10J
CT20.8.25
R4.3.13
CORE-01J
SKY55-43C
ION75-11D
CT20.8.25
R4.3.14
CORE-01J
SKY55-44B
ION75-11H
CT20.8.25
R4.3.15
CORE-01J
SKY55-46C
ION75-12B
CT20.8.25
R4.3.16
CORE-01J
SKY55-47W
ION75-13B
CT20.8.25
R4.3.17
CORE-01J
SKY55-48F
ION75-13B
CT20.8.25
R4.3.18
CORE-01J
SKY55-49N
ION75-13B
CT20.8.25
R4.3.19
CORE-01J
SKY55-60P
ION75-14B
CT20.8.25
R4.3.20
CORE-01J
SKY55-61G
ION75-15C
CT20.8.25
R4.3.21
CORE-01J
SKY55-62S
ION75-16G
CT20.8.25
R4.3.22
CORE-01J
SKY55-63U
ION75-17F
CT20.8.25
R4.3.23
CORE-01J
SKY55-64L
ION75-17F
CT20.8.25
R4.3.2A (CI)
CORE-01J
SKY55-51F
ION75-20T
CT20.8.27
4.2
Hardware 1678MCC R4.x
New HW items introduced with R4.1.1:

4x 10GE LAN Port /XFP
Low Order Adaptation LA20
Low Order Adaptation Connection LAC40
Low Order matrix Board LX160
3AG24339AA** (restricted use)

3AG24150AA**
3AG24327AA**
3AG24328AA**
New HW items introduced with R4.2:

Alarm Board
2x 10GE LAN Port /XFP
3AG24262AA**
3AG24476AA**
New HW items introduced with R4.3:

ISA-ES64 Server Board
1GBE ZX SFP module
STM-16 CWDM SFP modules
STM-16 DWDM SFP modules
3AG24371AA**
1AB187280042
1AB196340009...0016, 0026...0033
1AB231410001...0046

ED26
October 2012
15 of 61
STM-64 DWDM XFP modules
1AB356630001...0044
(1)
Note (1): supported in R4.3.12 RP4, R4.3.13 RP4, R4.3.15...R4.3.21 and R4.3.2 CI
For the current released HW part numbers and additional information please refer to
Equipping Options List 3AG24399BBAA.
4.3
Documentation
CD-ROM Costumer Documentation R4.3 3AG24399BDAA
4.4
SW maintenance raw patch releases
Note: The RP installation guide is part of the related RP package on SWDL server.
R4.3.1 RP2:
- vhm_pr-SKY55-40L.ppc.rpm
- 78mcc_pr-SKY55-40L.ppc.rpm
R4.3.1 RP2 installation: update based on R4.3.1, no traffic impact.
R4.3.1 RP3:
-
78mcc_pr-SKY55-40M.ppc.rpm

R4.3.1 RP4:
-
vhm_pr-SKY55-40N.ppc.rpm

R4.3.1 RP5:
R4-3-1_RP5_patch_install.tar.gz, which includes
-
COREUpdate-SKY55-43L.ppc.rpm
CSU-SKY55-43L.ppc.rpm
DCRSupervisionDCR-SKY55-43L.ppc.rpm
DCRSupervisionEM-SKY55-43L.ppc.rpm
GMRE_LM-ION75-10H.ppc.rpm
LSWMan-SKY55-43L.ppc.rpm
R4-3-1_RP5_patch_install.sh

R4.3.11 RP1:
-
GMRE_CFG_FLC_DCR-ION75-11D.ppc.rpm
GMRE_CFG_FLC_EM-ION75-11D.ppc.rpm
GMRE_LM-ION75-11D.ppc.rpm
GMRE_PM-ION75-11D.ppc.rpm
GMRE_RH-ION75-11D.ppc.rpm
GMRE_SH-ION75-11D.ppc.rpm
COREUpdate-SKY55-43C.ppc.rpm
CSU-SKY55-43C.ppc.rpm
DCRSupervisionDCR-SKY55-43C.ppc.rpm
DCRSupervisionEM-SKY55-43C.ppc.rpm
R4.3.11 RP1 installation: update based on R4.3.11, no traffic impact

ED26
October 2012
16 of 61
R4.3.11 RP2:
-
GMRE_PM-ION75-11H.ppc.rpm
GMRE_CN-ION75-11H.ppc.rpm
GMRE_SH-ION75-11H.ppc.rpm
GMRE_RH-ION75-11H.ppc.rpm
GMRE_LM-ION75-11H.ppc.rpm
DCRSupervisionEM-SKY55-43L.ppc.rpm
LSWMan-SKY55-43L.ppc.rpm
DCRSupervisionDCR-SKY55-43L.ppc.rpm

R4.3.12 RP1:
-
G4fw_pr-SKY55-42A.ppc.rpm
BoardMgtProc-SKY55-42A.ppc.rpm

R4.3.12 RP2:
-
78mcc_pr-SKY55-43C.ppc.rpm

R4.3.12 RP3:
-
78mcc_pr-SKY55-43H.ppc.rpm

R4.3.12 RP4:
R4-3-12_RP4_patch_install.tgz, which contains
-
DCRSupervisionEM-SKY55-45F.ppc.rpm
LSWMan-SKY55-45F.ppc.rpm
mibIM2-SKY55-45F.ppc.rpm
vhm_pr-SKY55-45F.ppc.rpm
78mcc_pr-SKY55-45F.ppc.rpm
CSServerProc-SKY55-45F.ppc.rpm
DCRIPMgt-SKY55-45F.ppc.rpm
DCRSupervisionDCR-SKY55-45F.ppc.rpm

R4.3.13 RP1:
-

R4.3.13 RP2:
-
78mcc_pr-SKY55-43J.ppc.rpm
vhm_pr-SKY55-43J.ppc.rpm

R4.3.13 RP4:
R4-3-13_RP4_patch_install.tgz, which contains
-
GMRE_RH-ION75-12B.ppc.rpm
DCRSupervisionEM-SKY55-45F.ppc.rpm
GMRE_SH-ION75-12B.ppc.rpm
LSWMan-SKY55-45F.ppc.rpm
MIBServer-ION75-12B.ppc.rpm
mibIM2-SKY55-45F.ppc.rpm
vhm_pr-SKY55-45F.ppc.rpm
GMRE_CFG_FLC_DCR-ION75-12B.ppc.rpm

ED26
October 2012
17 of 61
GMRE_CFG_FLC_EM-ION75-12B.ppc.rpm
GMRE_CN-ION75-12B.ppc.rpm
GMRE_LGAdapt-ION75-12B.ppc.rpm
GMRE_LM-ION75-12B.ppc.rpm
GMRE_MA-ION75-12B.ppc.rpm
GMRE_MC-ION75-12B.ppc.rpm
CSServerProc-SKY55-45F.ppc.rpm
GMRE_PH-ION75-12B.ppc.rpm
DCRIPMgt-SKY55-45F.ppc.rpm
GMRE_PM-ION75-12B.ppc.rpm
DCRSupervisionDCR-SKY55-45F.ppc.rpm
R4.3.20 RP1:
-
GMRE_LGAdapt_ION75-15D.ppc.rpm
vhm_pr-SKY55-62A.ppc.rpm
mibIM2-SKY55-62A.ppc.rpm

R4.3.20 RP2:
-
DCRSupervisionDCR-SKY55-63E.ppc.rpm
R4.3.20 RP2 installation: update based on R4.3.20, no traffic impact,

-> Installation of Raw Patch 2: 3AG 26492 AAAA PCZZA, Ed. 01
R4.3.20 RP3:
-
GMRE_PM-ION75-15E.ppc.rpm
R4.3.20 RP3 installation: update based on R4.3.20, no traffic impact,

-> Installation of Raw Patch 2+3: 3AG 26525 AAAA PCZZA, Ed. 01
R4.3.23 RP1:
- to be used in GMRE networks only
- GMRE_LGAdapt-ION75-17G.ppc.rpm
- R4.3.23 RP1 installation: update based on R4.3.23, no traffic impact,
-> Installation of 1678MCC R4.3.23 RP1: 3AG 26548 AAAA PCZZA Ed.02
- Note 1: R4.3.23 RP1 and R4.3.23 RP2 are not cumulative since they address different
applications
- Note 2: R4.3.23 RP1 can also be installed on top of R4.3.22.
R4.3.23 RP2:
- Only to be used on nodes with configured MSSPRING or MSSPRING nodes in GMRE
network
- fwa_pr-SKY55-64M.ppc.rpm
- R4.3.23 RP2 installation: update based on R4.3.23, no traffic impact,
- Note 1: R4.3.23 RP1 and R4.3.23 RP2 are not cumulative since they address different
applications
- Note 2: R4.3.23 RP2 can also be installed on top of R4.3.22.

ED26
October 2012
18 of 61
R4.3.23 RP3:
- Combines R4.3.23 with the R4.3.23 RP1.
- Includes the direct update from R4.3.1x to R4.3.23 RP1 in one step
- SKY55-64L + ISUSKY55-63C
- R4.3.23 RP3 installation: update based on R4.3.1x, no traffic impact,
R4.3.23 RP4:
- When to use the RP4 please refer to the ON OSI Routing Problem during Supervision
Start-Up provided by TEC
- osi_ll-SKY55-64N.ppc.rpm
- The RP4 can be installed on top of R4.3.23 RP1, RP2 and RP3.
- RP4 does include neither RP1, nor RP2 nor RP3.
- R4.3.23 RP4 installation: update based on R4.3.23, no traffic impact
- Installation of Raw Patch 4: 3AG 26563 AAAA PCZZA ED01
5
5.1
INSTALLATION PROCEDURE
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.3 releases cover the In-Service Upgrades as per the table 1, s. next page.
Procedure details are described inside the Maintenance Handbook.
Known restrictions in the area of update and ISU:
- MSP/MSSPRING traffic must be on the protected line before ISU is started
- Risk of few seconds traffic hits for XCs located in OED.
- Risk of B3 errors for XCs located in OED1670
Fallback: In rare cases, the ISU 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
- ISU to R4.3.2 CI: In rare cases temporary fake alarms may occur for 1GbE interfaces, traffic is
not affected
Notes:
- Starting with R4.3.18, the fallback has to be performed using the backup taken prior of the
SW update.
- In-service Upgrades are usually performed during off-peak hours. Normally, a maintenance
window is established.

ED26
October 2012
19 of 61
TO
4.3.1
4.3.11
4.3.12
4.3.13
4.3.14
4.3.15
4.3.16
4.3.17
4.3.18
4.3.19
4.3.20
4.3.21
4.3.22
4.3.23
SKY55-40K
SKY55-40M
SKY55-41F
SKY55-43C
SKY55-44B
SKY55-46C
SKY55-47W
SKY55-48F
SKY55-49N
SKY55-60P
SKY55-
SKY55-62S
SKY55-63U
SKY55-64L
ISUSKY55-40B
ISUSKY55-40E
FROM
ISUSKY55-40B ISUSKY55-40B
3.2.3
supported w/o
GMRE
not planned
not planned
supported w/o
GMRE; rel. under
PLM control
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
3.2.4
3.2.5
supported
supported
supported
not planned
not planned
not planned
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
3.2.5+
3.2.6
supported
supported
not planned
supported
not planned
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
3.2.61
not planned
not planned
not planned
supported w/o
GMRE; rel. under
PLM control
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
4.1.1
supported
ISUSKY55-35F
supported
not planned
not planned
not planned
not planned
not planned
not planned
not planned
not planned
not planned
not planned
not planned
not planned
4.2.0
not planned
not planned
supported w/o 10GE

ISUSKY55-35F
not planned
not planned
not planned
not planned
not planned
4.2.1
not planned
not planned
not planned
not planned
not planned
not planned
not planned
not planned
not planned
SW Update
SW Update
SW Update
SW Update
rel. under PLM

control
SW Update
not planned
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
4.3.1
4.3.11
4.3.12
4.3.13
4.3.14
4.3.15
4.3.16
4.3.17
4.3.18
ISUSKY55-40F ISUSKY55-40F ISUSKY55-41A ISUSKY55-41A ISUSKY55-43A ISUSKY55-43A ISUSKY55-43A ISUSKY55-62B ISUSKY55-63C ISUSKY55-63C
should work, to be verified by local team

not planned
not planned
not planned
not planned
not planned
not planned
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
SW Update
4.3.19
4.3.20
4.3.21
4.3.22
4.3.23
4.3.2A (CI)
Table 1: In-Service Upgrades to R4.3.x

ED26
October 2012
20 of 61
6
6.1
SOLVED PROBLEMS/RESTRICTIONS/WARNINGS
Solved problems/restrictions/warnings R4.1.1
6.1.1
Solved problems with workaround
DDTs SLSks38276
If the left SYNTH16 is active and plugged out/in, the EPS state keeps in mode "AutoFail".
Workaround for previous releases:
After one hour, after the SYNTH16 boards are aligned again, a cold reset has to be sent to the
active SYNTH16 board via CT/SH.
DDTs SLSks39611
After a coldstart of the active SYNTH16 while the link boards are "out of service", the LED of
the passive SYNTH16 is red. The matrix redundancy is not affected.
After a warmstart of the passive SYNTH16 the LED is orange.
6.1.2
Solved functional restrictions and warnings
DDTs SLSks38458
If the left LAX board is plugged out a RMAF/RMBF is signalled for both matrix boards. The
alarms are raised due to a erroneous detected NGI failure. The HO matrix redundancy is not
affected and the alarms should be ignored.
DDTs SLSks39438
During persistency restore session the LLMan process may block PC-CT.
Workaround:
Stop the whole CT application (NES-IM). If the LLMan is not stopped automatically, please kill it
additionally.
DDTs SLSks40756
OED70: Only 48 MSP groups in OED shelf are managed. Additional groups can be created but are
not manageable.
DDTs SLSks41230
For the 1662SMC Subrack the AIS alarm duration time reported for the E1CTP is 4-5 secs too
long. The real alarm time is 4-5 secs shorter.
6.1.3
Solved specific system behaviours
DDTs SLSks33997
A terminal loop produces B3 errors if the incoming signal of the loopback port is not
synchronous to the local clock. The terminal loop is also ok if there is no incoming signal.
DDTs SLSks47085
If there is a communication failure within a GMRE application restart, and no response is
received from the neighbour node, the LSPs are torn down and GMRE does not repeat the RSVP
recovery procedure when communication is restored.

ED26
October 2012
21 of 61
6.2
Solved problems/restrictions/warnings R4.2
6.2.1
Solved problems
DDTs SLSks41371
SD threshold configuration on AU TPs does not work.
The SD alarms raised by 10E-6 error rate of B3 are inserted, independently of the configured
threshold of 1,10,100,1000.
DDTs SLSks43712
If the auto-negotiation mechanism fails, there is no indication for the operator.
DDTs SLSks44465
H4 byte (coming from LAX) on STM-1 signal structured to TU12 is not according to ITU
Recommendation G.707/Y.1322 (12/2003). 1678MCC sends H4 = 000000cc (cc denotes
multiframe counter bits) while the standard requests H4 = XX11XXcc (XX denotes arbitrary
values). Those wrong bits do not affect the traffic, but may lead to unexpected alarms on
remote NEs of other vendors which may check those bits. Alcatel equipment does not raise an
alarm.
6.2.2
DDTs SLSks37229
On lower order termination point (TU12) PM before matrix does not count FEBBE as long as only
Far End is activated.
Activate Near End as well and FEBBE is counting correctly.
6.2.3
Solved restrictions and warnings
DDTs SLSks40936
The GBE LCAS alarm CPE (FOP) is not implemented according G.806.
DDTs SLSks43576
Internal link monitoring functionality for Lower Order Matrix shelf is not available.
DDTs SLSks44281
During InServiceUpdate to R4.1.1 there are traffic interruptions up to 22 minutes for traffic on
the 10GE-boards.
DDTs SLSks44674
OED-Links are usually 1+1 MSP protected and must not be changed to 1:N MSP scheme. This
change is not inhibited at the GUI.
DDTs SLSks44681
For T1 timing sources derived from a S.64 port the reporting of DRIFT events may be incorrect,
if a LOS alarm is active at the same time.
6.2.4
DDTs SLSks44782
To put LA20 boards in/out of service a special documented procedure must be followed

ED26
October 2012
22 of 61
6.3
Solved problems/restrictions/warnings R4.3
6.3.1
Solved problems
DDTs SLSks40810
in rare cases wrong timeout value causes ISPB access problems resulting in wrong configured
MSP memory of protection board (1:n MSP)
DDTs SLSks41900
SNCP switches may occur before HOT time is elapsed. (revertive SNCP only)
DDTs SLSks46387
GBE: Sporadic, transient Communication Subsystem Failure (CSF) alarms on HO Matrix can
happen, which are not traffic affecting.
DDTs SLSks46894
GBE: According Standard System shall report Total Loss of Capacity Received but System
reports AIS.
DDTs SLSks46896
10GBE: In case of a total loss of capacity SSF (TSF) and LOF are reported.
DDTs SLSks47138
In an 10 GE LCAS scenario the deactivation of a failed member may lead to an unwanted
reduction of bandwidth for some seconds.
DDTs SLSks47143
In an 1GE - 10 GE interworking LCAS scenario the deactivation of the last member may lead to
a traffic interruption in 10GE - 1GE direction of about one second.
6.3.2
DDTs SLSks44019
Installation of Core and SKY packages may failed on install server PCs using Windows-XP with
the Microsoft update (KB923191).
De-installation of Microsoft update (KB923191) solves the problem.
DDTs SLSks44846
In rare cases, late LSP Create Notification could cause RM GMRE Inconsistency. This is not
traffic affecting
Correct on lower level via CLI
DDTs SLSks44701
In very rare cases there is an unexpected toggling LAN failure alarm on both matrix copies.
The alarm can be cleared by resetDCR on both DCRs.
DDTs SLSks46511
If several thousand crossconnections are found while searching in the CC Dialog window, the
emlim might crash and has to be restarted.
As precaution use an appropriate filter for searching.
ED26
October 2012
23 of 61
DDTs SLSks46852
PM/GbE: configuring multiple PM-TPs on GbE using clipboard functionality can cause a crash
on the emlim.
In this case the USM has to be restarted.
DDTs SLSks47251
Pressing the LO-Matrix reset button at active LX160 can cause problems with possible traffic
loss at other LX160, when becoming active.
Use CT to perform a manual switch.
6.3.3
DDTs SLSks45295
LO-Shelf: No PM-Alignment after first EPS switch. PM Data lost after first EPS Switch (after PM
creation). The suspect Data Flag is on.
DDTs SLSks47167
TCA alarms raised for TPs in the LO-Shelf, are sometimes not cleared correctly, if a LX160
switch takes place while the TCA is active.
DDTs SLSks47182
TimeStamp of SSF on MST may be wrong if raiseTime 0.1sec
DDTs SLSks47318
LO_ES: Internal supervision of shelf internal clock drift is not working.
DDTs SLSks48782
10GE: During ISU from R4.1.1 to R4.2, it may happen that SW download is not finished
correctly, and traffic is impacted.
Corrective action:
Push / pull the affected board.
DDTs SLSks48577
When a database restore is executed via Craft Terminal, the following wrong error message
will be displayed:
"Due to a communication problem with the network element, the operation\\ you requested
could not be completed. You may retry the operation once the network element is reachable
again."\\
The real status/progress of the restore operation shall be checked in the B&R view in the field
"Progress". E.g.: Last command: Restore State: Success
6.3.4
DDTs SLSks43545
In some rare cases SSM and RUP alarms may be raised temporarily during a matrix EPS. Those
alarms are cleared automatically when the switch is completed.
DDTs SLSks46185
If there is a GbE board in slot#2 (i.e. internal port 0) with LCAS enabled, the deactivation of a
VC4v cross-connection of another GbE board with LCAS enabled will lead to an MND alarm and
a traffic hit on a VC4v in slot#2.
Therefore it is recommended not to use slot#2 for any 1/10GbE-boards.
ED26
October 2012
24 of 61
6.4
Solved problems/restrictions/warnings R4.3.1
6.4.1
Solved problems
DDTs SLSks48031
LO_shelf: Configuration reload of LX160 card could be blocked in case of too many SNCP's
configured.
DDTs SLSks50360
Configuration reload of LAX could be blocked in case of too many SNCP's configured.
DDTs SLSks50675
Ports 5 and 13 of 1GbE card are dropping traffic, when other 1GbE ports of this card are under
a LOA or CSF conditions.
DDTs SLSks51098
Only one trail per LO matrix (LAX or LO_shelf) can be structured to LO paths when operating
via 1354RM.
6.4.2
DDTs SLSks50542
In very rare cases, the LAPD communication between two nodes could be disrupted whereby
only one node does not receive any RSVP-TE packets from its neighbour. In accordance with
RSVP standards, this node stops sending RSVP refresh packets. The neighbour will tear down
the LSPs because it receives Hello packets but not Refresh.
Workaround:
Reset the FLC-DCR of the node which receives no RSVP packets and reports the RSVP control
plane interface to the neighbour is Down.
6.4.3
DDTs SLSks49491
Restoration time of 1GbE path without LCAS might be up to 30 seconds
DDTs SLSks50666
NM-PM collection is not supported by ES64
DDTs SLSks50709
Configuration of more than 8 OEDs could fail due to time out setting of CSServer on FLC main
controller. Problem is not affecting traffic, however, supervision is lost.
6.5
Solved problems/restrictions/warnings in R4.3.1 RP2
Note: This RP fix is not cumulative, ie. does fix specifically the deficiencies as listed in this
section.
6.5.1
Solved problems
DDTs SLSks51972
LO shelf: Creating an SNCP with destination TP on last TP per IO board in the 1662OED shelf
fails and brings the system into a blocking state.

ED26
October 2012
25 of 61
6.6
section.
6.6.1
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.
6.7
section.
6.7.1
Solved problems
DDTs SLSks51972
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.
6.8
section.
6.8.1
DDTs SLSks53086
Under exceptional instabilities in the DCC environment and processing load it was observed in
rare cases that login to the DCR was no more possible.
6.9
Solved problems/restrictions/warnings in R4.3.11
6.9.1
Solved problems
DDTs SLSks51972
6.9.2
DDTs SLSks52488

ED26
October 2012
26 of 61
6.10 Solved problems/restrictions/warnings in R4.3.11 RP1

6.10.1
DDTs SLSks53019
Paths should not be torn down if there is a control plane failure (RSVP Hello dead) during
neighbor resynchronization.
DDTs SLSks53086
DDTs SLSks53522
To prevent paths being torn down during neighbor resynchronization, GMRE should not initiate
neighbor resynchronization unless local application startup is fully completed.
6.10.2
DDTs SLSks53214
Changing the current route when the Tail node is not reachable (control plane failure) should
not tear down the path.
DDTs SLSks53809
Physical links set to ShuttingDown and carrying traffic are automatically set to Locked and
triggers restoration after application restart or FLC switch.
This RP includes the fixes of R4.3.11 RP1, and additionally the fixes listed in this section.
6.11.1
Solved problems
DDTs SLSks54475
The ReadyToRevert notification is not sent to the NMS in the case where both legs of a PRC
path are restored, but only one leg is ready to revert.
6.11.2
DDTs SLSks54404
If an alarm appears during a MoveFrom nominal route request, the Nominal flow is not
released.
DDTs SLSks54585
If contention occurs during backup activation, there could be a delay in activation of up to one
minute.
6.11.3
DDTs SLSks41628
During restoration of active traffic, the concurrent set up of new pre-calculated backup paths
leads to an imbalanced load of the control plane communication channels when multiple fibres
and a high number of paths are affected.
DDTs SLSks54459
In case of facing a large network with many pre-calculated paths in a permanent state
NoBackup (due to insufficient network resources), control plane background load is increased.

ED26
October 2012
27 of 61
DDTs SLSks54463
Non optimized background control plane communication load is caused by too detailed protocol
information in routing protocol messages regarding resources used on pre-calculated routes.
DDTs SLSks54492
During control plane application startup of a central node with a high number of neighbor
nodes, the routing adjacency converges after re-try when applied simultaneously with all
neighbors.
6.12 Solved problems/restrictions/warnings in R4.3.12
6.12.1
Solved problems
DDTs SLSks52850
MS-SPRING: When a double failure is present in MS-SPRING, also traffic of some AU4 channels
might be affected on sections, which are not isolated.
DDTs SLSks53029
LO shelf: RUM alarm might be reported on LA20 boards after EPS switch of LX160 for 20 sec.
6.12.2
DDTs SLSks52878
LO shelf: In rare cases the lasers of LA20 modules keep off while setting the board InService or
when a board is plugged in.
The problem can be cleared by re-initialization of the board, i.e. reset or plugout/plugin once
more.
6.12.3
DDTs SLSks51237
LO shelf: In a single rack solution, when LO shelf is located in the same rack carrying the main
shelf, the supervision of Step-Up Converters is not working for the LO shelf.
6.12.4
DDTs SLSks51191
LO shelf: VC12 broadcast connections are only supported with up to two legs, even if creation
of more legs is not rejected but marked as Connection Failed.
DDTs SLSks53082
LO shelf: MSP switch on LA20 hangs when LX160 is equipped non-redundant
6.13.1
DDTs SLSks53236
LO-Shelf: After laser shut down on LAC40, no alarm is reported for linked port on LA20.
section.

ED26
October 2012
28 of 61
6.14.1
Solved problems
DDTs SLSks53481
In rare cases a SSM-alarm can be raised on standby HOMX due to a threshold limit in alarm
detection, which is too small.
6.14.2
DDTs SLSks51808
If slot position 7 is equipped and left HOMX is active a wrong TOOR or HT alarm could raise on
lower FAN due to wrong measured value of temperature.
DDTs SLSks53384
MS-SPRING: In very rare cases it might happen that traffic is not running in protection channels,
SD alarm could be displayed on AU4.
6.15
6.15.1
Solved problems
DDTs SLSks54264
In very rare cases protection channels of MS-SPRing might be wrongly squelched in case of a
fibre cut.
6.15.2
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.
6.15.3
DDTs SLSks52488
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.

ED26
October 2012
29 of 61
6.16
6.16.1
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
7
8
9
10
11
12
13
14
15
16
Laser off/on
Port(s) executed
1
1&2
1&3
1&4
2&5
2&6
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.16.2
DDTs SLSks54388
In rare cases alarm time stamps of clearing time could be reported earlier than appearing time
DDTs SLSks54588
PM records with elapsed time not equal to interval time are not archived on NM.

ED26
October 2012
30 of 61

6.17.1
Solved problems
DDTs SLSks53481
In rare cases a SSM-alarm can be raised on standby HOMX due to a threshold limit in alarm
detection, which is too small.
6.17.2
DDTs SLSks51808
If slot position 7 is equipped and left HOMX is active a wrong TOOR or HT alarm could raise on
lower FAN due to wrong measured value of temperature.
DDTs SLSks53019
Paths should not be torn down if there is a control plane failure (RSVP Hello dead) during
neighbor resynchronization.
DDTs SLSks53086
DDTs SLSks53384
MS-SPRING: In very rare cases it might happen that traffic is not running in protection channels,
SD alarm could be displayed on AU4.
DDTs SLSks53522
To prevent paths being torn down during neighbor resynchronization, GMRE should not initiate
neighbor resynchronization unless local application startup is fully completed.
6.17.3
DDTs SLSks53214
Changing the current route when the Tail node is not reachable (control plane failure) should
not tear down the path.
DDTs SLSks53809
Physical links set to ShuttingDown and carrying traffic are automatically set to Locked and
triggers restoration after application restart or FLC switch.
6.18
6.18.1
DDTs SLSks52488

ED26
October 2012
31 of 61
6.19
6.19.1
Solved problems
DDTs SLSks54199
DDTs SLSks54264
fibre cut.
6.19.2
DDTs SLSks53780
6.19.3
DDTs SLSks54423
6.20
6.20.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.
6.20.2
DDTs SLSks54612
routing protocol.

ED26
October 2012
32 of 61
DDTs SLSks54687
Laser off/on
Port requested
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Laser off/on
Port(s) executed
1
1&2
1&3
1&4
2&5
2&6
2&7
2&8
3&9
3 & 10
3 & 11
3 & 12
4 & 13
4 & 14
4 & 15
4 & 16
6.20.3
DDTs SLSks54388
DDTs SLSks54588
DDTs SLSks54615
Reversion by bridge and roll to nominal route fails if signal degrade is on current route
6.21.1
Solved problems
DDTs SLSks54199
DDTs SLSks54264
fibre cut.

ED26
October 2012
33 of 61
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
6.21.2
DDTs SLSks53780
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".
6.21.3
DDTs SLSks52488
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 SLSks54423
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.
6.22.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.
6.22.2
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.

ED26
October 2012
34 of 61
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 SLSks54612
routing protocol.
DDTs SLSks54687
Laser off/on
Port requested
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Laser off/on
Port(s) executed
1
1&2
1&3
1&4
2&5
2&6
2&7
2&8
3&9
3 & 10
3 & 11
3 & 12
4 & 13
4 & 14
4 & 15
4 & 16

ED26
October 2012
35 of 61
6.22.3
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 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
DDTs SLSks54588
DDTs SLSks54615
Reversion by bridge and roll to nominal route fails if signal degrade is on current route
6.23.1
Solved problems
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.

ED26
October 2012
36 of 61
6.23.2
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.
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.
6.23.3
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 SLSks54432
OED62: RI data of CONGI board are not updated after replacement.
DDTs SLSks54959
Transparency of N1 & K3 bytes is set hard-coded, ie. the Serial Compound Link functionality is
not supported. Starting with R4.3.16 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.23.4
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.24.1
Solved problems
DDTs SLSks54925
In high load situations on a NE it can happen that some AU4 trails get UNEQ alarm egress which
is not visible in POM.
ED26
October 2012
37 of 61

6.25.1
Solved problems
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 for previous releases: perform manual HO MX EPS
DDTs SLSks55434
In rare cases a SFP or XFP module might be misdetected after matrix switch and RUTM alarm is
raised.
DDTs SLSks55692
During in-service upgrade (ISU) MS-SPRing traffic is dropped if the upgraded node participates
as nodeId #0.
Corrective action: switch HOMX after finishing the ISU manually to recover the traffic.
Afterwards reset also the passive HOMX.
6.25.2
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.
6.25.3
DDTs SLSks55313
The collection of PM history fails on NM if the related TP is in switched state of MSP/MS-SPRing.
DDTs SLSks55634
FLC controller uptime of more than 497 days (i.e., no FLC reboot within this time) might cause
an incorrect behaviour of the FLC application.
Workaround: perform a FLC reboot once within 450 days. The resulting FLC switch does not
impact the traffic.
6.25.4
DDTs SLSks54658
In rare cases the clearing TC alarm time is less than the raising time.
DDTs SLSks55536
The ASAP attributes are not cleared internally after board is plugged out. These attributes are
restored after the board is plugged again.
DDTs SLSks55895
In rare cases, the SW maintenance tool Snoopy with use of support selector may cause HO
matrix crashes to appear at a later date.
6.26
6.26.1
Solved problems
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.
ED26
October 2012
38 of 61
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.26.2
DDTs SLSks54240
In very rare cases, after an FLC switch it might happen that all LAPDs are down and report a
CSF alarm.
Workaround for previous releases: Perform HO matrix switch and reset the new standby matrix.
DDTs SLSks56217
In rare cases the OSPF process gets blocked. This leads to loss of OSPF functionality and loss of
IP communication possibly.
Workaround for previous releases: Reset DCR board of affected FLC.
6.26.3
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.
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 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.
6.27
6.27.1
Solved problems
DDTs SLSks56497
OED62: The LAX20-LAX40 upgrade fails with an error message if the configuration contains an
OED62 drop shelf.
6.27.2
Specific system behaviours
DDTs SLSks56532
GMRE: GMRE does not become operational if the rack ID of the main shelf is not equal to 1.
Workaround for previous releases: In case of initial installations configure the rack ID of the
main shelf to 1.
6.28
6.28.1
Solved problems
DDTS SLSks57077
In nodes with more than 500 LO SNCPs it might happen that GMRE does not complete startup
and remains degraded after node's restart or FLC switch.

ED26
October 2012
39 of 61
6.29
6.29.1
Solved problems
DDTS SLSks58932
In rare cases problems might occur with internal buffer deallocation on DCR, which could slow
down GMRE processing and potentially could lead to functional misbehaviour.
6.30
6.30.1
Solved specific systems behaviour
DDTS SLSks59274
PRC reversion optimized for low latency also applies for the reversion from Spare nominal to
Main nominal.
6.31
6.31.1
Solved problems
DDTS SLSks56967
In configurations with GMRE and LAX it may happen that the LAX traffic is not reestablished
after a system coldstart.
DDTS SLSks56983
During ISU a RUP alarm might be reported on V-64.2M, L-64.2M or U-64.2M boards and not
cleared automatically. Even traffic is not lost bit errors would appear due to incorrect
preamplifier/booster settings.
DDTS SLSks57142
Paths on 1GbE and 10GbE port cannot be migrated from NP to ASON/GMRE.
DDTS SLSks57307
In rare cases the configuration of host-ID and OSPF router-ID is not properly done in the
system.
DDTS SLSks57347
The CT shows an empty position for 10G BASE-S modules if the port is selected even if the
module is present.
DDTS SLSks57356
GMRE: A LSP will be restored even if only one MSP leg failed. This might happen after a
previous alarm where both MSP legs failed.
DDTS SLSks57503
In case of a fiber cut the static route of in-band communication is not re-created properly on
protected LAPD, which impacts the GMRE control plane and RSVP message exchange. In
consequence the restoration of traffic couldn't be performed properly. The Out-Of-Band
communication isn't affected by this problem.
DDTS SLSks58055
In very rare cases traffic might be lost if a tail node restarts during a reversion.
DDTS SLSks58400
In GMRE node with LAX, the LO traffic might not be reestablished after a system coldstart.
ED26
October 2012
40 of 61
6.31.2
DDTS SLSks49727
In very rare cases, it may happen that either HOMX or LAX protection group is lost even if
untouched reported on GUI. This problem could appear if
(1) HOMX and LAX boards are configured in the system and
(2) whole configuration of both - HOMX and LAX - boards will be loaded at the same time.
If happened, problem will persist. During presence of that problem, manual EPS would be
blocked but autoswitch will fail.
This hidden problem will be detected in a health check (No. 3.2.4), which can be requested via
TEC Germany and applied remotely and non-intrusive by TAC without TEC support.
A single FORCE command via GUI to currently active HOMX / LAX board, followed by RELEASE
command will neutralise this problem.
DDTS SLSks57673
After a SW update installation within R4.3.x the NE backup does not contain the persistency of
the GMRE processes.
Workaround for previous releases: perform the command 'reinitialiseCSServer' on the active FLC
as user appl.
DDTS SLSks58528
A nominal path might be reported "Not Ready To Revert" due to a failure of the control plane
on a transit node. However this message is incorrect and the path could be reverted.
Workaround: The FLC should be switched on the transit node reporting the CP failure to
neighbour.
6.32
6.32.1
Solved problems
DDTS SLSks54387
In very rare case that an external instability of clock network would cause an internal phase
jump in LO-shelf, traffic of several paths might be affected with SD alarm reporting until
manual repair action.
DDTS SLSks56889
During In Service Update it might happen in very rare cases that the Laser is switched off on
single ports for some minutes.
DDTS SLSks58110
After NE cold start SSF alarm might be reported on single STM-64 ports in rare cases (with
traffic impact).
DDTS SLSks58923
All recognized HW errors on LAX boards are reported as POWER_FAIL in log file.
DDTS SLSks58932
In rare cases problems might occur with internal buffer consumption on DCR, which could slow
down GMRE processing and potentially could lead to functional misbehaviour.
DDTS SLSks59039
In very rare cases OSPF routes may get lost in the routing table.
ED26
October 2012
41 of 61
DDTS SLSks59133
Sometimes ghost alarms might be reported, which are not physically present and dont impact
traffic. The triggered consequent actions are not needed and might impact traffic.
DDTS SLSks59225
In GMRE configuration with OED70 a temporary CSF alarm could be reported for OED during an
LSP with drop port in the OED is set-up.
DDTS SLSks59266
If a non-intrusive RUP alarm is reported on drop ports traffic will be affected due to
unsuccessful restoration because it triggers the LSP deletion but re-creation is impossible due
to reported RUP alarm.
DDTS SLSks59284
GMRE: In context of fast restoration MS-RDI or MS-SSF alarms may not be cleared.
DDTS SLSks59311
The boot loader check might fail during ISU preparation in case of newer FLC boards (since
about end of 2010) or repaired FLC boards.
DDTS SLSks59313
When a craft terminal is connected via the F-interface the memory on the DCR gets slowly
consumed due to a memory leak in the corresponding driver. This may lead to an unexpected
DCR reboot.
DDTS SLSks59328
In very rare cases the path label (C2) or section / path traces (J0, J1) might be reported
incorrect due to read errors on HW devices. Consequent actions would impact traffic.
DDTS SLSks59516
In nodes containing more than five OED shelves the In Service Upgrade might be aborted by
timeout.
6.32.2
DDTS SLSks57705
In fully equipped shelves temperature alarms might be reported even it is operating normal.
DDTS SLSks58656
In case of negative values of environment temperature an invalid temperature alarm is
reported
DDTS SLSks59290
Several HO matrix boards with specific HW parameters (age of devices, temperature etc.)
might not work correctly (especially after cold start or EPS).
DDTS SLSks59871
One traffic hit (e.g. due to a protection switch in subsequent equipment) could cause a second
hit within the following second.

ED26
October 2012
42 of 61
6.33
6.33.1
Solved problems
DDTS SLSks58750
The creation of a line loop on P16S16 boards might impact an already existing line loop on
another port of the same board.
DDTS SLSks59847
The archived PM history data In NM does not contain the data for lower order TPs.
DDTS SLSks60065
In very rare cases the osi_ll process on the FLC may cyclically restart. This causes both FLCs to
go into the maintenance state.
6.33.2
DDTS SLSks60207
FLC controller uptime of more than 497 days (i.e., no FLC reboot within this time) might
cause an incorrect behaviour of the FLC application .
Workaround: perform a FLC reboot once within 450 days. The resulting FLC switch does not
impact the traffic.
6.33.3
DDTS SLSks58952
Internal loops on STM-64 ports might cause bit errors on the same and other ports on this board
or short toggling alarms.
DDTS SLSks59920
Problems with J0 / J1 trace identifiers might be caused by inproper initialisation of FPGA on IO
board
6.34
6.34.1
Solved problems
DDTS SLSks60768 (root cause for SLSks60759)
Repeated restoration requests to NE SW might not succeed but overloads the NE. Failing
restoration requests to NE are no longer repeated by control plane and alternative routes are
attempted.
6.35
6.35.1
Solved problems
DDTS SLSks61127
In rare cases a Signal Degraded alarm might be reported on concatenated paths after MS-SPRing
switch to the protection channels.
Corrective action: perform a matrix switch.
6.36
6.36.1
Solved problems
See R4.3.23 RP1 (but supports the direct update from R4.3.1x to R4.3.23 RP1).

ED26
October 2012
43 of 61
6.37
6.37.1
Solved problems
DDTS SLSks62553
In rare cases the 1678MCC accepts a Q3 OSI supervision request from NMS addressed to another
remote NE which is connected e.g. via DCC and for which the 1678MCC acts as OSI gateway NE.
The problem does not exist for NEs managed via IP/RFC1006.
6.38 Solved problems/restrictions/warnings in R4.3.2A (CI)

6.38.1
Solved problems
DDTs SLSks51097
Replacing a STM-64 board containing redundant links to 1670OED will cause URU alarms on all
related IOBs within the OED. This triggers a GMRE SPCENDPOINT OpState down and a LSP
Failure for affected paths. This alarm stays even if the board is already exchanged.
Corrective action:
A warm reset of active HCMATRIX board after board replacement clears the alarms.
6.38.2
DDTS SLSks49727
In very rare cases, it may happen that either HOMX or LAX protection group is lost even if
reported untouched on GUI. This problem could appear if
(1) HOMX and LAX boards are configured in the system and
(2) whole configuration of both - HOMX and LAX - boards will be loaded at the same time.
If happened, problem will persist. During presence of that problem, manual EPS would be
blocked but auto-switch will fail.
This hidden problem will be detected in a health check (No. 3.2.4), which can be requested via
TEC Germany and applied remotely and non-intrusive by TAC without TEC support.
A single FORCE command via GUI to currently active HOMX / LAX board, followed by RELEASE
command will neutralise this problem.
6.38.3
DDTs SLSks45187
The signal degraded alarm is not considered for LCAS.
DDTs SLSks50403
No support of transparent client TCM information. TCM is always terminated on the node.
DDTs SLSks50664
The 1678 router OSPF priority, which is configured via GUI, is not configured in reality.
DDTs SLSks51043
When connecting the GBE ports in 1678 to an external GE equipment it shall be ensured that
flow control on both sides is enabled and is effective.
Not working flow control may drive the 1678 GbE port into an overflow condition that in rare
cases might result in hits of several seconds on the GbE traffic on all ports of the affected GbE
board. The problem does not arise if LCAS is enabled on the port.

ED26
October 2012
44 of 61
6.38.4
DDTs SLSks50858
If flow control of a GBE port is not effective, this laser might be switched off periodically, even
if LaserForcedOn is set.
DDTs SLSks51026
In rare cases and high amount of configured low order SNCP it may happen that the board LAX
once reset may stay longer in download than typically.
DDTs SLSks51113
After a FLC file system recovery (e.g., after NE cold-start), the NTP server configuration will be
reverted to the state after the last in service upgrade or initial installation. If the NTP
configuration has been changed since then, the configuration has to be repeated after the file
system recovery is completed.
KNOWN PROBLEMS/RESTRICTIONS/WARNINGS
This chapter contains all known potentially customer relevant problems for the 1678 Metro
Core Connect R4.3 system working under normal operating conditions.
7.1
Known problems/restrictions/warnings found in R4.1.1
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 a 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.

ED26
October 2012
45 of 61
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.
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 SLSks46908
In an 1GE LCAS scenario a differential delay exceeding 17 ms for one VC4 may lead to an SSF
alarm and link down on GE side.
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.

ED26
October 2012
46 of 61
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 SLSks48624
On the alarms SQM and PLTM there might PM not be counted and therefore UAT count and
alarm indications are missing.
DDTs SLSks49244
For disconnected ports the reported J1/C2 may be not equal to 0.
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.

ED26
October 2012
47 of 61
DDTs SLSks44581
If an MSP protected LA20-port is in Lockout together with a pending SF, there may be a
problem with the MSP protocol on the protecting port.
Workaround:
This can be avoided if the remote side of the Lockout LA20 is set in state lockout, too.
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.
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.
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.
DDTs SLSks33767
In rare cases the switching times for STM-1e equipment protection may exceed 50ms (up to
100ms).
ED26
October 2012
48 of 61
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.
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 S-value and not the one with the least concatenation level is chosen.

ED26
October 2012
49 of 61
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.

ED26
October 2012
50 of 61
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 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.
ED26
October 2012
51 of 61
DDTs SLSks47057
In rare cases plug out / plug in of a STM64 V board may result in a LOP on MV642 module
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
The 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 SLSks48546
If a defect FLC is replaced with a spare FLC which was already installed and in usage before,
old backup data might be still stored on the spare FLC.
To avoid restore of these old backup data by accident, it is recommended to create a new
backup of the NE configuration after successful completion of the FLC replacement procedure.
Alternatively, am existing backup can be transferred to both FLCs, to make sure that both FLCs
have the same backup data.
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.
ED26
October 2012
52 of 61
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 SLSks49718
TCP throughput limitation may happen in EVPL mode due to tail packet discard (TPD) applied
instead of an active queue management with random early discard (RED). Tail packet discard
(TPD) fills up the buffer to maximum and subsequent packets are dropped - leading to restart
of TCP window size, hence causing a throughput limitation.
Problem is not present in EPL mode due to 802.3x flow control avoiding buffer overload from
source side, which is not available for EVPL.
DDTs SLSks49913
1662 OED shelves shall not be configured to have shelf id 2.
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 SLSks50244
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:
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 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 SLSks50327
Backup and restore using RM consistency download for GMRE with LO traffic terminated in LAX
is not supported.
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.
ED26
October 2012
53 of 61
DDTs SLSks51145
Battery failure on PSF boards are not alarmed. In case of maintenance actions the PSF alarm
state shall be checked via HealthCheck tool.
DDTs SLSks51162
On 10GE ports, oversized frames in the in direction from Ethernet towards TDM side are
dropped, but not counted neither in TRSEF nor in TDF.
DDTs SLSks51312
Calculation of the alarms "Temperature Out Of Range" as well as "High Temperature"
is not correct if HO matrix A is active and slot position 7 is equipped.
7.1.4
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 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 SLSks50587
For 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 the alarm profile, both alarms are
reported - even if LCAS is disabled and TLCR alarm shouldnt be raised.
DDTs SLSks34399
If a Databearer is set to shutting down, the GMRE node of the link shall not be restarted, until
the traffic is moved away from the link and the link is then in admin down state.
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.
ED26
October 2012
54 of 61
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 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".
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.
ED26
October 2012
55 of 61
DDTs SLSks51084
EBER alarm is not reported correctly on MSTTP in AS and it has to be ignored.
DDTs SLSks51126
Inconsistent setting of GbE parameters does not lead to warning. For example, it is possible to
disable laser shutdown control while bidirectional fault propagation is enabled. It is up to the
operator to set the GbE parameters consistently for the desired services.
See operator handbook for supported configurations.
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.
DDTs SLSks51191
LO shelf: VC12 broadcast connections are only supported with up to two legs, even if creation
of more legs is not rejected but marked as Connection Failed.
7.2
Known problems/restrictions/warnings found in R4.2
7.2.1
Known problems
DDTs SLSks47296
During an InServiceUpgrade the IO-EPS in the OEDs is not working.
7.2.2
DDTs SLSks50741
After restoring persistency data with forced MSP switches on LAC40/LA20, traffic of the related
link might be down.
Workaround:
The release of the MSP switch recovers the traffic. In general, MSP switches have to be
released on LAC40/LA20 before creating a backup.
7.2.3
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 SLSks51237
In a single rack solution, when the LO shelf is located in the same rack carrying the main shelf,
the supervision of Step-Up Converters is not working for the LO shelf.
7.2.4
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.

ED26
October 2012
56 of 61
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.
7.3
Known problems/restrictions/warnings found in R4.3
7.3.1
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 SLSks51024
Performing manual switch for ES64 EPS can lead to traffic outages.
Workaround:
Perform a reset operation on the active ES64 using Craft Terminal and wait some minutes until
the card is in service again. Do not use the reset operation from ES64 ZIC.
DDTs SLSks53545
The Tool ./GMRE_PM_PersEdit fails when there are NEW LINES inside lspDescriptor.
Workaround: Avoid new lines in LSP names
7.3.2
DDTs SLSks50355
In case of having 10GE LAN IO card connected to a ES64 server card and 64 byte frames on the
10GE LAN card, with fill grades higher than 60%, up to 10% of the traffic may be dropped.
For standard random packet distribution scenarios, the system works as expected.
DDTs SLSks50607
In case of an active SQM alarm, the 10GE board with a VC4xv configuration will generate
additionally the LOA alarm.
DDTs SLSks50507
In the ES64 ZIC it is not possible to modify a traffic descriptor (TD) after activating.
DDTs SLSks50639
In the ES64 ZIC the total number of TDs is limited to 400
DDTs SLSks50582
In the ES64 ZIC all ports (1-252) are shown even though only port numbers 1-64 & 129-192 are
valid.
ES64: During establishment of an ES64 protection group, facility provisioning on the active
ES64 is not allowed until synchronization is complete
Workaround:
Wait for all alarms on the ES64 protect card to clear and the card to go IS before provisioning
facilities on the main card.
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.

ED26
October 2012
57 of 61
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.
7.3.3
DDTs SLSks44510
The GbE ZX SFP module is noted in the port view as "1000BaseLX"
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 SLSks54754
In rare cases during HO MX switch an additional warm reset might happen. No traffic is
impacted.
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.
Workaround:
Configure two services that share the same TD.
7.4
Known problems/restrictions/warnings found in R4.3.1x
7.4.1
Known problems
DDTS SLSks59548
The configuration of a second T1 timing source in OED70 is rejected with a wrong error
message, which doesnt mention that only one timing source can be configured.
DDTS SLSks59735
PSF boards with ICS greater than 01 report a RUP alarm due to missing power (switch off stepup converter) instead of expected BF (Battery Failure) alarm.
DDTS SLSks59835
Fans with ANV number ACAA report a RUP alarm due to missing power (switch off step-up
converter) instead of expected BF (Battery Failure) alarm.

ED26
October 2012
58 of 61
DDTS SLSks60224
In rare cases the IP communication via unprotected LAPD might not work properly after a laser
force off
DDTS SLSks60266
The archived PM history data in NM does not contain the data for modVC4 TPs.
DDTS SLSks60356
The RST convergence time may be up to 16 seconds when unplugging the external Lan cable on
one of the FLCs.
DDTS SLSks60357
In all default ASAPs except the noAlarms ASAP the ExtIFDevProblem (external interface device
problem) alarm is missing. As a consequence the alarm is cleared unexpectedly in case of an
FLC switch or an alarm resynchronisation from CT/NM.
The alarm can be made visible again by the following procedure:
1) Clone ASAP 'noAlarms' and set the ExtIFDevProblem to a defined severity, for instance 'minor'
2) Apply the ASAP 'noAlarms' to the affected board.
3) Apply now the cloned ASAP to the affected board. Now the lost alarm is shown correctly.
7.4.2
DDTS SLSks56864
The following sequence of operator commands leads to an inconsistent display of the alarm
counters: 'Supervision->Alarms->Inhibit Notifs', close the EMLUSM window, reopen the EMLUSM
window.
Workaround: stop and restart supervision while EMLUSM is kept open.
DDTS SLSks59419
If a Force Switch command on a reference clock source is replaced immediately by a Lockout
command without releasing the Force Switch command, this reference clock source will be
selected after matrix EPS if the node was in Holdover during the EPS.
Workaround: First release the Force Switch command before entering the Lockout command.
7.4.3
DDTS SLSks58556
The IP address of a node should never be changed if GMRE is active even if it is offered in the
EP dialog.
DDTS SLSks58560
During ISU when executing 'GMRE_ISU_LinkMaint.pl deactivate' it has to be ensured that the
GMRE on the neighbor nodes are up. Otherwise the link maintenance is not deactivated
properly.
DDTS SLSks58952
Internal loops on STM-64 ports might cause bit errors on the same and other ports on this board
or short toggling alarms.

ED26
October 2012
59 of 61
7.4.4
DDTS SLSks35852
On a P16S1S P16S1-4 or P16S16 boards the Internal Loop does not work at module slot 9-12.
B3 errors or AU-AIS alarms will be transmitted reverse.
Workaround:
Create additional Internal Loopback according to this scheme
- internal loopback on port 9 works when loopback is created on ports 9 and 13
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 SLSks54872
The PM counts for LOS alarms are about 4 seconds higher than the physical LOS alarm on SDH
ports in case that ALS is enabled.
Workaround: force Laser on (ALS disabled).
DDTs SLSks54890
When port boards P4ES1 resp. P16ES1 were switched to lockout before extracting and
afterwards the lockout is released before re-inserting, the ports of the access boards A4ES1
resp. A16ES1 remain empty. Workaround: push / pull the access board
DDTs SLSks54914
In rare cases in configurations of 10GE with LCAS and more than about 20 members the actual
LCAS hold-off time is smaller than the configured value.
DDTs SLSks54951
It may happen that FAN unit reports a RUP alarm and red LED lights on FAN unit after lost
power redundancy (switched off Step-Up Converter) for some seconds.
DDTS SLSks58580
When searching with the CT in TP-Search dialog for disabled connections the result is not
correct for protected connections. The list contains also all enabled protected connections.
DDTS SLSks59896
Bit errors might appear during the first HO matrix EPS after a nodes cold start.
7.5
Known problems/restrictions/warnings found in R4.3.2 CI
7.5.1
DDTs SLSks53560
ISU to R4.3.2: In rare cases temporary fake alarms on GbE ports might be raised after the FPGA
download to 1GbE board. The fake alarms are cleared automatically before ISU is finished.
Traffic is not affected.

ED26
October 2012
60 of 61
DDTs SLSks53641
ISU to R4.3.2: In very rare cases, during ISU from R3.2.61 to R4.3.2, there might be traffic hits
of up to a few hundreds of milliseconds for XCs located on STM-1/4/16 cards in mainshelf.
End of Document
ED26
October 2012
61 of 61

3AG24101BDAAFMZZA - V1 - 1678 MCC Release 04.03.x Product Release Note

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

3AG24101BDAAFMZZA - V1 - 1678 MCC Release 04.03.x Product Release Note

Загружено:

Авторское право:

Доступные форматы

Alcatel-Lucent

1678 MCC | R4.3.x

3AG 24101 BDAA FMZZA

Release Note for R4.3

Update for editorials

Release Note for R4.3.1

Update for R4.3.1 RP2

Update for R4.3.1 RP3 and R4.3.11

Update for R4.3.12 and R4.3.12 RP1

Update for R4.3.2A (CI)

Update for R4.3.13, R4.3.11 RP1 and R4.3.12 RP2

Update for R4.3.1 RP4, R4.3.12 RP3, R4.3.13 RP2

Update for R4.3.1 RP5, R4.3.11 RP2, R4.3.14

Update for R4.3.12 RP4, R4.3.13 RP4, R4.3.15

Update for R4.3.16

Update for R4.3.17

Update for editorials

Update for R4.3.18

Update for R4.3.19

Update for R4.3.20

Update for R4.3.20 RP1

Update for R4.3.21

Update for R4.3.20 RP2

Update for R4.3.20 RP3

Update for R4.3.22

Update for R4.3.23

Update for R4.3.23 RP1, R4.3.23 RP2

Update for R4.3.23 RP3

Update for R4.3.23 RP4

3AG 24101 BDAA FMZZA

DEFINITIONS AND ABBREVIATIONS ...........................................................................6

NEW FEATURES ..........................................................................................................12

PRODUCT COMPOSITION ..........................................................................................15

INSTALLATION PROCEDURE .....................................................................................19

Software 1678MCC R4.x...................................................................................15

SOLVED PROBLEMS/RESTRICTIONS/WARNINGS ..................................................21

Solved problems/restrictions/warnings R4.1.1...............................................21

Solved problems/restrictions/warnings R4.2 ..................................................22

Solved functional restrictions and warnings .................................................... 26

Solved problems/restrictions/warnings in R4.3.11 .........................................26

Solved problems .............................................................................................. 26

Solved problems/restrictions/warnings in R4.3.1 RP5 ...................................26

Solved functional restrictions and warnings .................................................... 26

Solved problems/restrictions/warnings in R4.3.1 RP4 ...................................26

Solved problems .............................................................................................. 25

Solved problems/restrictions/warnings in R4.3.1 RP3 ...................................26

Solved problems .............................................................................................. 25

Solved problems/restrictions/warnings in R4.3.1 RP2 ...................................25

Solved problems .............................................................................................. 23

Solved problems/restrictions/warnings R4.3.1...............................................25

Solved problems .............................................................................................. 22

Solved problems/restrictions/warnings R4.3 ..................................................23

Solved problems with workaround ................................................................... 21

Solved problems .............................................................................................. 26

Solved problems/restrictions/warnings in R4.3.11 RP1..................................27

Solved problems/restrictions/warnings in R4.3.11 RP2..................................27

3AG 24101 BDAA FMZZA

6.11.3 Solved specific system behaviours .................................................................. 27

Solved problems/restrictions/warnings in R4.3.12 .........................................28

Solved problems .............................................................................................. 28

Solved problems/restrictions/warnings in R4.3.12 RP1..................................28

Solved problems/restrictions/warnings in R4.3.12 RP2..................................28

Solved problems/restrictions/warnings in R4.3.12 RP3..................................29