3AG24101BGAAFMZZA - V1 - 1678 MCC Release 04.06.x Product Release Note

Alcatel-Lucent
1678 MCC | R4.6.x

Product Release Notes
3AG 24101 BGAA FMZZA

ED17
November 2014
Alcatel-Lucent Proprietary
Use pursuant to applicable agreements
REVISION HISTORY
ED
DATE
01
090728
02
ORIGINATOR
APPROVER
Release Note for R4.6.0
H. Bauer
C. Wulf
100512
Release Note for R4.6.1 RP1/R4.6.11
C. Wulf
C. Wulf
03
100521
Release Note for R4.6.2
C. Wulf
C. Wulf
04
100929
Update for R4.6.21
C. Wulf
C. Wulf
05
110218
Update for R4.6.22
C. Wulf
C. Wulf
06
110428
Update for R4.6.23
C. Wulf
J. Webster
07
110622
Update for R4.6.22 RP1/R4.6.23 RP1
C. Wulf
J. Webster
08
111010
Update for R4.6.24
C. Wulf
J. Webster
09
120131
Update for R4.6.11 RP2
C. Wulf
J. Webster
10
120223
C. Wulf
J. Webster
11
120503
Update for R4.6.25
C. Wulf
J. Webster
12
121001
C. Wulf
J. Webster
13
121025
C. Wulf
J. Webster
14
121214
Update for R4.6.26
C. Wulf
J. Webster
15
131220
Update for R4.6.27
C. Wulf
E. Englehart
16
140515
C. Wulf
E. Englehart
17
141107
Update for R4.6.28
C. Wulf
E. Englehart

ED17
November 2014
COMMENTS
2 of 49
CONTENTS
1
REFERENCED DOCUMENTS ..................................................................................... 5
DEFINITIONS AND ABBREVIATIONS ......................................................................... 5
KEY FEATURES ........................................................................................................ 11
PRODUCT COMPOSITION ........................................................................................ 16

4.1
4.2
4.3
4.4
INSTALLATION PROCEDURE................................................................................... 19
5.1
5.2
Software 1678MCC R4.6.x ............................................................................. 16

Hardware 1678MCC R4.6.x ............................................................................ 16
Documentation.............................................................................................. 17
SW maintenance raw patch releases............................................................. 18
New installation ............................................................................................ 19
In service update / upgrade.......................................................................... 19
SOLVED PROBLEMS/RESTRICTIONS/WARNINGS................................................. 21
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10
6.11
6.12
6.13
Solved problems/restrictions/warnings R4.6.1 RP1/R4.6.11 ........................ 21

6.1.1
6.1.2
Solved problems .............................................................................................. 21

Solved functional restrictions and warnings .................................................... 21
6.2.1
6.2.2
Solved problems .............................................................................................. 21

Solved restrictions and warnings ..................................................................... 22
6.3.1
6.3.2
Solved problems .............................................................................................. 22

6.4.1
6.4.2
Solved problems .............................................................................................. 23

6.5.1
Solved problems .............................................................................................. 23
6.6.1
Solved problems .............................................................................................. 23
6.7.1
Solved problems .............................................................................................. 24
6.8.1
6.8.2
6.8.3
6.8.4
Solved problems .............................................................................................. 24

Solved problems with workaround ................................................................... 25
Solved specific system behaviours .................................................................. 26
6.9.1
Solved problems with workaround ................................................................... 26
Solved problems/restrictions/warnings R4.6.11 RP2 .................................... 21

Solved problems/restrictions/warnings R4.6.2 ............................................. 22
Solved problems/restrictions/warnings R4.6.21 ........................................... 23
Solved problems/restrictions/warnings R4.6.22 RP1/R4.6.23 RP1 ............... 24

6.10.1 Solved problems .............................................................................................. 27
6.10.2 Solved problems with workaround ................................................................... 28
6.10.3 Solved specific system behaviours .................................................................. 28

6.11.1 Solved problems .............................................................................................. 29

6.12.1 Solved problems .............................................................................................. 29

6.13.1 Solved problems .............................................................................................. 29
6.13.2 Solved specific system behaviours .................................................................. 31

ED17
November 2014
3 of 49
6.14
6.15
6.16

6.14.1 Solved problems .............................................................................................. 31

6.15.1 Solved problems .............................................................................................. 31

6.16.1 Solved problems .............................................................................................. 32
KNOWN PROBLEMS/RESTRICTIONS/WARNINGS ................................................. 34

7.1
Known problems/restrictions/warnings in R4.6 ............................................ 34

7.1.1
7.1.2
7.1.3
7.1.4

ED17
November 2014
Known problems .............................................................................................. 34

Known problems with workaround ................................................................... 36
Functional restrictions and warnings ............................................................... 40
Specific system behaviours ............................................................................. 45
4 of 49
1
[1]
[2]
[3]
REFERENCED DOCUMENTS
Validation Release Note
Software Development Release
Feature List
3AG 24101 BGAA

3AG 24101 BGAA
3AG 24101 BGAA
FCZZA
PVZZA
FLZZA
DEFINITIONS AND ABBREVIATIONS
ABBREVIATION
MEANING
ABN
AC
ADM
AIS
ALM
ALS
AND
ANSI
APD
APS
ASIC
ASON
ASTN
ATM
ATTD
AU
AU4
AUG
AUOH
AUX
BATT
BER
BGP
BIP
BNC
BST
BST10
BTERM
BUSTERM
CE
CLNP
CMI
CO
CONGIHC
COPS
CORBA
CPE
CPLD
CPI
CPO
CPU
CSR
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
Customer Specific Release

ED17
November 2014
5 of 49
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
HPROT
ED17
November 2014
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
High Speed Protection Board
6 of 49
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
MHDLC
ED17
November 2014
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
Multi HighLevel Data Link Controller
7 of 49
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
POH
ED17
November 2014
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
Path Overhead
8 of 49
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
TX
ED17
November 2014
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
Transmission
9 of 49
U
UNI
URG
V
VCG
VCXO/VCO
VCx
VECE
VLAN
VMMF
WAN
WEEE
XFP
XFPE

ED17
November 2014
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
10 of 49
KEY FEATURES
Key functionalities introduced with previous releases:

- HO Matrix
- 160G/320G/640G HO Matrix card, 1+1 EPS
- In-service upgrade of HO matrix
- LO Matrix
- 20G/40G single-slot LO Matrix card, 1+1 EPS
- LO extension shelf, scalable up to 160G (1000 STM-1 equivalents) in steps of 40G (250
STM-1 equivalents)
- LO PM
- In-service upgrade of LO matrix
- TDM interface cards
- 16x STM-1 card (SFP)
- 16x STM-1/4 card (SFP)
- 4x/8x/16x STM16 card (SFP)
- 2x/4x STM-64 card (XFP)
- 16x STM1el./opt. cards in 1670OED drop shelf
- 24x E1 card in 1662OED drop shelf
- STM-16 Colored CWDM SFP
- STM-16 Colored DWDM SFP L-16.2 (spacing - 100 GHz)
- STM-64 Colored DWDM XFP
- MSA to XFP replacement
- 10GE LAN interface cards with XFP optical interface module
- 2x/4x 10GE LAN card
- Rate adaptive mapping VC-4-Xv (X=1 to 64)
- Port auto-negotiation configuration
- SR, LR XFP optical interface module
- EVPL push/pop
- LCAS
- Fast LPT
- Ethernet PM counters w/ PM 15min & 24h history
- Queue management (WRED, flexible buffer size)
- 1GbE interface card
- 4x/8x/16xGbE card (SFP)
- Rate adaptive mapping VC-4-Xv (X=1 to 7)
- Port auto-negotiation configuration
- SX, LX, ZX SFP optical interface module
- LCAS
- Fast LPT
- Ethernet PM counters w/ PM 15min & 24h history
- System
- Station Alarms/Housekeeping
- Event log
- 1:N MSP on STM-1/4/16/64 and S1E in OED, w/ MSP hold off time
- 128 MSP groups in mainshelf and 1670OED drop shelf
- NTP configuration via CT
- CT login security
- Auto-port monitoring
- PJE counter w/ TCA
- DDM for SFP/XFP (in 1678 MCC main shelf only)

ED17
November 2014
11 of 49
- GMPLS
- Managed classes of Services: unprotected, SBR (Source Based Rerouting), GR (Guaranteed
Restoration), protected, PRC (Protection & Restoration Combined)
- Priority based preemption (5 priority levels)
- Nominal route handling with manual/automatic hitless reversion
- Local repair capability for optimized usage of resources
- SNCP ring closure at network boundary
- IB/OOB Protection
- Serial compound links
- Multicast connections w/ SBR, GR and PRC restoration
- LO drop interface in ASON domain for LAX20/40
- Ethernet drop interface in ASON domain for 1GbE, 10GbE EPL, 10GbE EVPL and ISA-ES64
- E-NNI 1.0 management with OIF local domain restoration
Note: - Not for field deployment!
- Only for interoperability tests on protocol level to prove implementation
according to the standards.
- Graceful Migration from RM to ASON manager (RM) / GMRE part for HO-TDM, and Ethernet
(EPL & EVPL)d
- Control plane auto-discovery
- WTR time
- Disjoint links
- Bridge & Roll
- Link maintenance
- GMRE deactivation
- SNCP selector management
- PM on GMPLS LSPs
- MX loopback for GMPLS LSPs
- ISA-ES64 @ VC4 (ETSI):
- 2x20G switching capacity per system,
- 1:1 EPS protection
- Jumbo Frame (9242 bytes) support on ports 1..30 and 129..158
- Baby Jumbo Frame (2026 bytes) support on all ports
- VLAN label stacking
- ETH VLAN push/pop/swap
- Ethernet rate adaptive mapping VC-4-Xv (X=1 to 64) at logical port
- Up to 128 VC-4-Xv VCGs per board
- GFP-F mapping (framed, acc. G.7041)
- GFP-F (G.7041): null extension header without FCS
- Packet policing (network ingress)
- Dual rate token bucket
- Metering, Policing and Marking MEF compliant
- Color blind traffic Metering, Policing and Marking (SLA compliance)
- Traffic management (Packet congestion & Scheduling)
- 2 queues w/ strict priority scheduling
- 6 queues w/ WFQ (WDRR) scheduling
- W-RED congestion avoidance
- Customer protocols tunneling (transparency)
- Best Effort Traffic (PIR > 0, CIR = 0)
- Regulated Traffic (PIR > CIR > 0)
- Guaranteed Traffic (PIR = CIR > 0)
- Packet classification: port
- Ethernet priority bits classification (802.1Q)
ED17
November 2014
12 of 49
- ETH VLAN classification

- classification acc. VLAN ID + pri-bits inside same service
- 8 QoS classes
- L2-Matrix is 100% non-blocking
- ETH Unicast/MC/BC traffic forwarding
- Packet Forwarding: port
- Packet Forwarding: port + VLAN tag (outer tag lookup)
- ETH Private Line
- ETH Virtual Private Line
- up to 128 logical ports per card
- Ether Type provisioning per port
- up to 2 pairs of ES64
- Connection Admission Control (CAC)
- CIR CAC disabling per ES64 (pair)
- Preserve p-bits on VLAN push/pop
- Per port counters: Green/Yellow discards, current, history (15m/24h)
- Per Q counters: Green/Yellow discards, current, history (15m/24h)
- Up to 18 LAG groups per ES64
- 1:1 EPS for a pair of ISA-ES64 server cards
- SNMP CT (ZIC) with up to 6 simultaneous sessions
- Management interface via SNMP protocol stack
- Enable/disable policing on a per flow basis (CLI only)
- Shared traffic descriptors
- Multiple traffic descriptors per service
- LAG according to 802.3ad (1:N, LACP)
- LAG on 1GbE ports
- LCAS for VC-4-nv
- CIR oversubscription per port (provisionable factor)
- DCN
- DCC protection (<100msec.)
- DCC channel quantity: 95 MS & 16 RS per system (FLC AB type)
- DCC channel quantity: 16 MS & 16 RS per system (FLC AA and AB type)
- Multi-OSI area management
- IP over OSI tunneling
- DCC transparency
Note: Regression testing for GMPLS w/ HO-AU3 mapping will be executed on demand.
Key functionalities introduced with R4.6.0:
- GMPLS
- Resource Coloring
- Soft rerouting when SD on MS
- Scalability 260 nodes / 32 neighbors
- System
- Support of NE with SSU clock mode
Key functionalities introduced with R4.6.1 RP1/R4.6.11:
- No change
Key functionalities introduced with R4.6.11 RP2:
- No change

ED17
November 2014
13 of 49

- GMRE
GMRE: NMS event log (activity log)
10GE performance enh. by use of VC-4-64c (incl. GMRE; for demo and trials only)
Note: special ION-build required, available on request
PRC Reversion optimized for low latency

- System
Pin protection board for dirty environment ( class3.2)

User-Byte handling for 64kbit/s channel connectivity via config file (OH bytes +
2Mbit G.703)
Event log for additional event types
1662OED dual LAN interface and SYNTH resiliency
PM TCA alignment with R3.2
1GbE PM counters TRCOin/out, TTOin/out
1GbE PM 24h history counters, in NE
WTR 48h for MS-SPRING
User Activity Logging functions on NE
Reduce D/B restore time

- No change
- ISU from R4.5.1x to R4.6.22 (supported w/ NR8.1PL3, NR9.2 MNT-4)
- No change
Key functionalities introduced with R4.6.22 RP1/R4.6.23 RP1:
- No change
- No change
- No change
- No change
- No change
Key functionalities introduced with R4.6.25 RP2
- No change
- Graceful LO Shelf ISU (typically two times less than 100ms traffic interrupt per LA20, up
to few seconds in rare cases)
- ISU from R4.3.2 to R4.6.26

ED17
November 2014
14 of 49

- No change
- Win 7 support on CT
- IE9 support
- ISU R4.6.11 to R4.6.27
- No change
For detailed information regarding the supported features please refer to
[3] Feature List

ED17
November 2014
15 of 49
PRODUCT COMPOSITION
4.1
Software 1678MCC R4.6.x

Release
FLC Platform
FLC Application
FLC GMPLS
CT
R4.6.0
CORE-01J
SKY70-01E
ION80-01W
20.8.41
R4.6.1 RP1
CORE-01J
SKY70-10F + rpm
ION80-10B
20.8.41
R4.6.11
CORE-01J
SKY70-10H
ION80-10B
20.8.41
R4.6.11 RP2
CORE-01J
SKY70-10H + rpm
ION80-10B
20.8.41
R4.6.2
CORE-01J
SKY72-02Z
ION82-01V
20.8.46
R4.6.21
CORE-01J
SKY72-04L
ION83-01P
20.8.46
R4.6.22
CORE-01J
SKY72-04M
ION83-02A
20.8.46
R4.6.23
CORE-01J
SKY72-04N
ION83-02A
20.8.46
R4.6.22 RP1
CORE-01J
SKY72-04M + rpm
ION83-02A
20.8.46
R4.6.23 RP1
CORE-01J
SKY72-04N + rpm
ION83-02A
20.8.46
R4.6.24
CORE-01J
SKY72-06R
ION83-03K
20.8.50
R4.6.24 RP1
CORE-01J
SKY72-06R + rpm
ION83-03K
20.8.50
R4.6.25
CORE-01J
SKY72-07L
ION83-04E
20.8.50
R4.6.25 RP1
CORE-01J
SKY72-07L + rpm
ION83-04E
20.8.50
R4.6.25 RP2
CORE-01J
SKY72-07L + rpm
ION83-04E
20.8.50
R4.6.26
CORE-01J
SKY72-08S
ION83-04E
20.8.50
R4.6.26 RP1
CORE-01J
SKY72-08S
ION83-04E + rpm
20.8.50
R4.6.27
CORE-01J
SKY72-09E
ION83-05A
20.8.52
R4.6.28
CORE-01J
SKY72-10F
ION83-06B
20.8.52
4.2
Hardware 1678MCC R4.6.x
New HW items introduced with previous R4 releases:

4x 10GE LAN Port /XFP
3AG24339AA** (restricted use)
Low Order Adaptation LA20
3AG24150AA**
Low Order Adaptation Connection LAC40
3AG24327AA**
Low Order matrix Board LX160
3AG24328AA**
Alarm Board
3AG24262AA**
2x 10GE LAN Port /XFP
3AG24476AA**
ISA-ES64 Server Board
3AG24371AA**
1GBE ZX SFP module
1AB187280042
STM-16 CWDM SFP modules
1AB196340009...0016, 0026...0033
STM-16 DWDM SFP modules
1AB231410001...0046
STM-64 DWDM XFP modules
1AB356630001...0044
ED17
November 2014
16 of 49
New HW items introduced with R4.6.0:

None
New HW items introduced with R4.6.1 RP1/R4.6.11:
None
CONTROL AND GENERAL I/F (DUAL LAN)
COMPACT ADM 16 (WITHOUT EC, SUPP. 1678 MCC) SYNTH16N
3AL98368AAAA
3AL98282ABAA

None
None
None
New HW items introduced with R4.6.22 RP1/R4.6.23 RP1:
None
None
New HW items introduced with R4.6.24 RP1:
None
None
None
None
STEP-UP MONITOR CABLE
3AG 24827 AAAA
None
None
None
4.3
Documentation
Refer to OneDoc web database reference on OLCS portal.

ED17
November 2014
17 of 49
4.4
SW maintenance raw patch releases
Note: The RP installation guide is part of the related RP package on SWDL server.
R4.6.1 RP1:
- PersistProcs-SKY70-10G.ppc.rpm
- R4.6.1 RP1 installation: update based on R4.6.1, no traffic impact,
- Installation of Raw Patch 1, 3AG 26496 AAAA PCZZA, Ed. 01
R4.6.11 RP2:
- osi_ll-SKY70-10M.ppc.rpm
- 78mcc_pr-SKY70-10M.ppc.rpm
- Installation of Raw Patch 2: 3AG 26530 AAAA PCZZA, Ed.01
-
This product release is limited to the use in the Telefnica network due to customer
specific requirements (SLSks58847).
R4.6.22 RP1:
- vhm_pr-SKY72-04P.ppc.rpm
- R4.6.22 RP1 installation: update based on R4.6.22, no traffic impact
- Installation of Raw Patch 1: 3AG 26538 AAAA PCZZA, Ed. 02
R4.6.23 RP1:
- vhm_pr-SKY72-04P.ppc.rpm
R4.6.24 RP1:
- DCRIPMgt-SKY72-07A.ppc.rpm
R4.6.25 RP1:
- When to use the RP1 please refer to the ON OSI Routing Problem during Supervision
Start-Up provided by TEC
- osi_ll-SKY72-08H.ppc.rpm
- DCRIPMgt-SKY72-08H.ppc.rpm
- Installation of Raw Patch 1: 3AG 26561 AAAA PCZZA ED01
R4.6.25 RP2:
- COREUpdate-SKY72-08E.rpm
- R4.6.25 RP2 does not include RP1
- Installation of Raw Patch 2: 3AG 26564 AAAA PCZZA, Ed. 01,
InstRP2_78_4625_26564_AA_PC_01.pdf
R4.6.26 RP1
- GMRE_LGAdapt-ION83-10A.ppc.rpm
- Installation of R4.6.26 RP1: 3AG 26569 AAAA PCZZA, Ed.01,
InstRP1_78_4626_26569_AA_PC_01.pdf

ED17
November 2014
18 of 49
INSTALLATION PROCEDURE
5.1
New installation
All software delivery items will be installed via a CD-ROM drive connected to the Craft
Terminal (CT). The detailed description how to install this release can be found in the
Installation and Start-Up Manual FLC Software and in the CT Basic Operator's Handbook in
chapter Installation Procedure.
5.2
In service update / upgrade
The R4.6.x releases cover the In-Service Upgrades as per the following table:
TO
FROM
4.3.1x *)
4.6.0
4.6.11
4.6.2
4.6.21
4.6.22
4.6.23
4.6.24
4.6.25
4.6.26
4.6.27
4.6.28
SKY70-01E
SKY70-10H
SKY72-02Z
SKY72-04L
SKY72-04M
SKY72-04N
SKY72-06R
SKY72-07L
SKY72-08S
SKY72-09E
SKY72-10F
ISUSKY70
ISUSKY70
ISUSKY72
ISUSKY72
ISUSKY72
ISUSKY72
ISUSKY72
ISUSKY72
ISUSKY72
ISUSKY72
ISUSKY72
-01B
-10A
-01C
-04A
-04B
-05B
-06B
-07A
-08K
-09A
-09A
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
supported
4.3.2A (CI) not planned not planned not planned not planned not planned not planned not planned not planned supported not validated not validated
4.5.1
not planned not planned not planned not planned supported
supported
supported
supported
supported not validated not validated
4.5.1 CI
not planned not planned not planned not planned supported
supported
supported
supported
supported not validated not validated
4.6.0
4.6.11
4.6.2
4.6.21
4.6.22
4.6.23
not planned not planned not planned not planned not planned not planned not planned not planned not planned not planned
not planned not planned not planned not planned not planned not planned not planned
SW update
supported
supported
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.6.24
4.6.25
4.6.26
4.6.27
SW update
*) Note: R4.3.1x includes R4.3.20, R4.3.21, R4.3.22, R4.3.23.

Procedure details are described inside the Maintenance Handbook.
Known restrictions related to ISU:
MSP/MSSPRING traffic must be on the protected line before ISU is started.
During the ISU, depending on the start release, different FPGAs get reloaded. In
consequence the FPGAs are dysfunctional. Protocol based protections switches like
MSSPRING, dual ended MSP, sync source selection changes are partly not working during
the ISU.
- In rare cases risk of MSP/MSSPRING traffic hits for up to several seconds (single digit)
due to FPGA upgrade
- Traffic hits for up to several seconds (single digit) due to FPGA upgrade for XCs located
on 10GbE
- Risk of sub-second traffic hit for XCs located on 1GbE
- 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 rollback to the start release fails (1 FLC ok, 1 FLC nok)

ED17
November 2014
19 of 49
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 main shelf
Risk of traffic hits of up to double digit seconds for connections located in ISA ES64
During upgrade of a LO shelf configuration, there is no cold start anymore during ISU to
R4.6.26, traffic impact typically two times less than 100ms traffic interrupt per LA20,
up to few seconds in rare cases.
Note: In-service Upgrades are usually performed during off-peak hours. Normally, a
maintenance window is established.

ED17
November 2014
20 of 49
SOLVED PROBLEMS/RESTRICTIONS/WARNINGS
6.1
Solved problems/restrictions/warnings R4.6.1 RP1/R4.6.11
6.1.1
Solved problems
DDTS SLSks56549
GMRE: In context of fast restoration MS-RDI or MS-SSF alarms may not be cleared.
DDTS SLSks56550
GMRE: If one MSP leg fails during the other leg is already in a failed condition, the traffic
restoration from this MSP might take up to 5-30 seconds. Additionally the LAPD configuration
on MSP protecting port is deleted.
DDTS SLSks57887
In case the tool checkedPersBackup is used it will cause a persistency misalignment and
the FLC will stay in maintenance state.
6.1.2
Solved functional restrictions and warnings
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 SLSks55651
If Ethernet PM is configured in the node the application wont start, e.g. after FLC switch or
system restart, and the FLC will stay in maintenance state
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 SLSks56736
No alarm is reported if only one leg of Unidirectional or Multicast SNCP as well as PRC path is
failed.
DDTS SLSks56953
A MSP protected link will be used for path setup by mistake although MSP is forced to the leg,
which is cut.
6.2
6.2.1
Solved problems/restrictions/warnings R4.6.11 RP2

Solved problems
DDTS SLSks59006
When the laser is forced on (laser shutdown control is disabled) for a GbE port then a LOA
alarm is not suppressed.

ED17
November 2014
21 of 49
6.2.2
Solved restrictions and warnings
DDTS SLSks58847
In a configuration with a unidirectional or broadcast connection for GbE source port an auto
negotiation failure is not propagated as CSF. As a consequence the destination GbE ports will
not switch off their laser.
DDTS SLSks59012
A memory leak in the OSI lower layer process causes regularly that the DCR is running out of
memory. This results in a DCR reboot once per month.
6.3
6.3.1
Solved problems/restrictions/warnings R4.6.2

Solved problems
DDTS SLSks56151
During maintenance actions like reset LAX boards terminated GMRE traffic will be torn down
until the board is configured again.
DDTS SLSks56447
In very rare cases and due to high load a concatenation request is not performed in restoration
context.
DDTS SLSks60869
In very specific case of heavy NE load as well as communication problems via control plane a
SNCP was created instead of a bidirectional XC and XC IDs were re-used. As a result a wrong XC
was deleted during reversion and traffic was impacted due to missing XC.
6.3.2
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 SLSks52339
The Hold-Off time of LCAS VCG on ES64 board is not working. LCAS members are removed
immediately in case of a failure.
DDTS SLSks56616
The routing display displays a question mark for the SNCP state of SNCP/PRC LSP if only one leg
is working.

ED17
November 2014
22 of 49
6.4
6.4.1

Solved problems
DDTS SLSks58552
Removal of active protected ES64 board drops GMRE traffic because the reported RUM alarm
causes the tear down of traffic by control plane, regardless of EPS switch
DDTS SLSks58586
The bandwidth / interface-speed configuration might be wrong if LCAS is disabled after it was
enabled before on an ES64 port
DDTS SLSks58459
The CSF alarm might remain on a protected ES64 board if an EPS switch is triggered during
configuration changes are ongoing.
DDTS SLSks58046:
The phase correction is not working on T4 output that might cause phase jumps at T4 output
and the T4 output must not be used for external clock sources without filtering before.
6.4.2
DDTS SLSks47281
T4 (2 MHz output signal) cannot be used as reference for another equipment. Its usage is
limited to an SSU application.
DDTS SLSks58621
The NE backup doesnt contain the GMRE part of the database.
6.5
6.5.1

Solved problems
DDTS SLSks59325
If ETH current PM data shall be displayed via GUI and the VHM application process will be
restarted (in case of FLC switch e.g.) the restart might not work on this FLC as well as (after
FLC switch) on the partner. So in rare cases both FLCs might enter in maintenance state finally.
6.6
6.6.1

Solved problems
DDTS SLSks50836
In configurations with many OED shelves (more than 5-8 OED depending on the configuration)
the ISU may abort with a time-out. The probability increased with the number of shelves.
DDTS SLSks59311
With newer FLC boards (since about end 2010) or repaired FLCs the precondition check of the
ISU may fail in the check of the boot loader.

ED17
November 2014
23 of 49
DDTS SLSks60029
During In Service Upgrade it might happen in very rare cases that the Laser is switched off on
single ports for some minutes.
DDTS SLSks60049
In case of fully equipped shelves or certain environmental temperature conditions it can
happen that temperature alarms are reported although the shelf is operating in valid
environmental conditions.
6.7
6.7.1
Solved problems/restrictions/warnings R4.6.22 RP1/R4.6.23 RP1

Solved problems
DDTS SLSks60300
After triggering a LO PM Current Data collection, it can happen that configuration requests are
blocked. A FLC switch may unblock the situation. If not successful, contact TEC.
6.8
6.8.1

Solved problems
DDTS SLSks58056
The error message of pre-ISU check script about rsvpIfRapidRetryLimit in config file
GMREProcess.cfg is wrong. It is correct that R4.6 uses the new value of rsvpIfRapidRetryLimit: 4
DDTS SLSks58580
The result for disabled connections of TP-Search dialog of CT is incorrect for protected
connections. The list contains also all enabled protected connections.
DDTS SLSks58642
Mainly newer FLCs with serial numbers starting with YP1 may report an unknown boot loader
when doing a check with "updateBootloader -check".
DDTS SLSks59005
If a manual created cross connection blocks the reversion to nominal route the failure output is
incorrect, instead of 'UsedByOtherManager' it is reported 4294967295.
DDTS SLSks59125
ES64 specific behaviour: LCAS alarm on VCG on upper Logical Data Port #x (logical ports
129..256 ) doesn't trigger appropriate update of IfSpeed for that port #x but for another port #y
(y = x - 128) instead.
DDTS SLSks59351
If both Main and Spare leg of PRC are restored after multiple cuts, and backup routes of one
leg is using nominal route of other leg, there is no notification to NMS of ReversionBlocked
state.
DDTS SLSks59397
Incomplete Ethernet PM 24h history records always show elapsedTime 24h and suspectFlag
false.

ED17
November 2014
24 of 49
DDTS SLSks59548
The configuration of a second T1 timing source in OED70 is rejected with a wrong error
message, which doesn't mention that only one timing source can be configured.
DDTS SLSks60006
The Current Instantaneous Measurement dialog for DDM modules might display garbage values
in Transmit and Receive Power row if the measured power is zero. Correct display would be
infinite dBm.
DDTS SLSks60069
In OED62 shelves it is sometimes rejected to put in service a P63E1N board, error message "The
equipment cannot be set in in-service."
DDTS SLSks60124
The switching times of MSP 1:N could be longer for some milliseconds.
DDTS SLSks60126
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 SLSks60417
On LAX boards the retrieval of Tu12/Tu3 PM current data blocks. No further retrieval of PM
current data is possible.
DDTS SLSks60593
If the ISU script has to be restarted twice due to previous errors it might skip certain steps
after second restart. This could impact traffic.
DDTS SLSks60689
In double fiber cut scenario, where restoration of 1st cut is not yet completed before 2nd cut
occurs, the restoration of 2nd cut re-uses the same transit node as 1st cut but not the same
ingress and egress TPs. However the XC IDs of 1st and 2nd restorations are identical on common
transit node so 2nd restoration deletes XC of 1st restoration wrongly.
DDTS SLSks60768
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.
DDTS SLSks60959
The wrapping mechanism for log files is not working after FLC replacement anymore. So the
available HDD space is decreased over time, which might trigger an unexpected FLC reboot.
6.8.2
Solved problems with workaround
DDTS SLSks59348
After ISU the T3 clock source might be in lockout state.
Workaround: manually release the lockout after ISU

ED17
November 2014
25 of 49
DDTS SLSks59851
If a GMRE process is restarted during reversion of PRC leg and another leg failed, the reversion
isnt completed and is stuck.
Workaround: restart GMRE application
DDTS SLSks59903
A forced switch to port x in 1:n MSP could be confirmed OK but indeed it is not executed due to
a pending force switch to another port y.
Workaround: the pending switch has to be released before performing the next force switch.
DDTS SLSks60220
If both FLCs have the same uptime of more than 490 days it might happen in rare cases that
both FLCs stay in maintenance after rebooting automatically.
DDTS SLSks60624
Wrong interpretation of Bridge and roll responses prevents reversion to nominal route.
Workaround: FLC switch or restart GMRE application
DDTS SLSks60694
In GMRE CLI the initial password change allows to enter a new password with more than 8
characters (up to 12). During further password changes via "set password" only 8 characters are
affected, so a password longer than 8 characters can not be changed anymore.
Workaround: do never enter passwords longer than 8 characters.
Corrective action: contact TEC to reset the password via superuser.
6.8.3
DDTS SLSks50656
As consequence of auto-negotiation failure on GE link no CSF frame is sent if the laser is forced
on.
6.8.4
Solved specific system behaviours
DDTS SLSks60617
The EIDP alarm can toggle quickly because the alarm detection is not filtered and reports each
current alarm state (on/off) immediately.
DDTS SLSks54538
J0 TTI values for GMRE owned ports are set automatically by GMRE and have a special
encoding. The decoded values of the J0 for DCNAddress and TCPId are not shown in human
readable form in the craft terminal.
6.9
6.9.1
Solved problems/restrictions/warnings R4.6.24 RP1

Solved problems with workaround
DDTS SLSks61350
In very rare cases routing routes learned via OSPF are lost.
Workaround: reboot DCR

ED17
November 2014
26 of 49
6.10 Solved problems/restrictions/warnings R4.6.25

6.10.1 Solved problems
DDTS SLSks60117
Switch events on ports involved in MS-SPRing can cause an increased delay on subsequent GMRE
restoration processing.
DDTS SLSks60759
Repeated restoration requests to MIB that do not succeed, overload the NE.
Failing restoration requests to NE are no longer repeated by control plane and alternative
routes are attempted.
DDTS SLSks61002
In case a LAX-board is running 497 days without restart the board restarts automatically.
DDTS SLSks61121
In case of a successive cut of both legs of a PRC it may happen that the restoration is
unexpectedly delayed.
DDTS SLSks61208
In rare cases the tool to capture system logfiles into an archive (Snoopy) may run into an
endless loop.
DDTS SLSks61270
In very rare cases it can happen that a faulty 10GbE-card can cause internal bus problems in
the shelf, which can lead to traffic problems after matrix switch.
DDTS SLSks61317
In configurations with GMRE and PRC LSPs it may happen in rare cases if the control plane is
lost to neighbours that a connection belonging to the PRC is deleted unexpectedly.
DDTS SLSks61339
In GMRE configurations the restoration of a PRC LSP may be delayed in rare cases by several
minutes if there are internal or external communication problems.
DDTS SLSks61366
In GMRE configurations certain control plane failures may unnecessarily delay the restoration of
an LSP.
DDTS SLSks61408
In case of enabled GMRE it may happen in case of system internal message congestion that the
reversion of an LSP can not be done.
DDTS SLSks61490
Under certain conditions a wrong FuseFailure alarm is reported for a PSF board after matrix
EPS.
(conditions: there was previously a power problem from this side, i.e. BatteryFailures on IOBoards and FuseFailure for the failing side on PSF if present, and an IO-board was
removed/deconfigured as far as the power problem was present; a certain time later matrixEPS)

ED17
November 2014
27 of 49
DDTS SLSks61520
In configurations with GMRE and PRCs with concatenated traffic it may happen in very specific
preemption scenarios that a PRC LSP is disturbed in the consolidation phase.
DDTS SLSks61811
In configurations with many OED shelves it may happen that the ISU feasibility check fails due
to a wrong timeout configuration.
DDTS SLSks61814
In system configurations with GMRE and enabled minimal tracing in zero-loss mode the FLCs
will go into maintenance when reaching 497 days uptime (R4.6.24 only).
DDTS SLSks61826
In configurations with more than 16 OED shelves the ISU to this release may abort due to a
wrong timeout configuration in the ISU tool.
DDTS SLSks61879
During the ISU it may happen in rare cases that temporary internal bus problems are causing an
abortion of the ISU.
6.10.2 Solved problems with workaround
DDTS SLSks59978
In case of an incorrect board calibration at startup of STM64-boards the alarm information for
instances on that card can be wrong (ghost alarms).
Workaround: board cold start
DDTS SLSks60224
In rare cases after a laser force off and on sequence for a port with an unprotected LAPD the IP
communication via this LAPD is not working properly.
DDTS SLSks60897, SLSks61350
DDTS SLSks61350
6.10.3 Solved specific system behaviours
DDTS SLSks57812
The system does not send any alarm if the passive FLC is not operational (e.g. while in
maintenance state).
DDTS SLSks58625
When a LOS-alarm clears at a STM64-port on U-64.2M or V-64.2 boards the board reports a
temporary (10 seconds) RUP-alarm.

ED17
November 2014
28 of 49
DDTS SLSks61120
Short LOS-alarms on SDH-ports are prolonged to 3 seconds to avoid wrong alarm clearing in
case of ALS-pulsing (mainly needed when LCAS is used on the peer side).
Because this is not only done when Automatic-Laser-Shutdown is active this can lead to short
traffic interruptions when very short LOS occurs in normal operation.
DDTS SLSks61229
GMRE configurations only: the behaviour concerning automatic reversion to the main nominal
leg is not configurable.
DDTS SLSks61860
The alarm clearing time for alarms on synchronisation inputs does not include a WTR time.
In case of alarms (phys. alarms like LOS, LOF or AIS and frequency offset) the clearing time is
in range 30 to 40 seconds but with an additional WTR-time (before alarm clearing and probably
reselection) a security time to select a good sync source is added.
DDTS SLSks61403
In case of very short power interruptions (some milli-seconds) it can happen, that some optical
interfaces don't work anymore and are not repaired automatically without manual interaction.
6.11 Solved problems/restrictions/warnings R4.6.25 RP1
DDTS SLSks62562
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.
DDTS SLSks61878
In case of GMRE with configured out-of-band tunnels for the control plane it may happen in
case all in-band links to a neighbour go down that the out-of-band tunnel loses GMRE control
plane packets. This may lead to GMRE misbehaviour like delayed restoration.
DDTS SLSks62624
The logrotate mechanism ensures a limited memory to be occupied by log files.
Under special condition while the logrotate is active it may happen that the wrapped logfiles
are in a state which blocks further logrotate runs.
As a consequence the logfiles are no longer wrapped. Due to a logfile size limitation for some
services this may result in an instable system behaviour.
DDTS SLSks61335
In configurations with LO extension shelf and LO SNCPs it may happen in very rare cases that a
switch to the protecting LA20 and back leads to a traffic loss of all protected LA20 traffic.

ED17
November 2014
29 of 49
DDTS SLSks61367
In configurations with LO extension shelf it may happen in rare cases when creating or
modifying LO SNCPs or broadcast connections that the connection is marked as
connectionFailed. As consequence the requested configuration change will not work properly.
DDTS SLSks61878
In case of GMRE with configured out-of-band tunnels for the control plane it may happen in
case all in-band links to a neighbour go down that the out-of-band tunnel loses GMRE control
plane packets. This may lead to GMRE misbehaviour like delayed restoration.
DDTS SLSks61939
For all synchronization related alarms the alarm clearing time stamp is reported identical to
the alarm raising time stamp in the alarm list.
DDTS SLSks62035
In very rare cases a MS-SD alarm may be active even if the alarm condition is not given. The
corresponding PM counters show no errors.
DDTS SLSks62102
The wrapping mechanism for log files may stop working if a EM/DCR reboot happens during the
wrapping is ongoing. This will lead to a full hard disk and as consequence to a recovery of the
corresponding FLC.
DDTS SLSks62116
In very rare cases a MS-SD alarm may be active even if the alarm condition is not given. The
corresponding PM counters show no errors.
DDTS SLSks62294
Short power outages in the range of a few milliseconds may lead to RUP alarms and a
permanent traffic loss on 10GE boards.
DDTS SLSks62368
In configurations with LO extension shelf it may happen in very rare cases that a switch to the
protecting LA20 leads to unequipped alarms on all modVC4s of the protected LA20.
DDTS SLSks62468
The creation of a line loop on P16S1S4 boards might impact an already existing line loop on
another port of the same board.
DDTS SLSks62562 (see also R4.6.25 RP1)
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.
DDTS SLSks62595
In configurations with LO extension shelf the setting outOfService of a LAC40 board may lead to
a cyclic application process crash and may as consequence result in the FLC going into the
maintenance state.
DDTS SLSks62648
In configurations with GMRE it may happen that after restoration events PM points are not
counting anymore even if configured properly.
ED17
November 2014
30 of 49
DDTS SLSks62667
In configurations with LO extension shelf it may happen in rare cases after an FLC switch or
system cold start that both LX160 report permanently a CSF alarm. As consequence a
configuration of the LO shelf is not possible and also no alarms are reported.
DDTS SLSks62682
In configurations with LO extension shelf the LO-SNCPs with the output TP on a modVC4 of the
LO-shelf are not working properly when executing manual or force commands. The switches
will not be done. Automatic switches are done as expected.
6.13.2 Solved specific system behaviours
DDTS SLSks58656
In case of negative environment temperature an invalid temperature alarm is reported.
DDTS SLSks62003
In rare cases it can happen that short temporary HighTemperature alarms are reported and
immediately cleared (without a TOOR/Temperature-Out-Of-Range alarm before). These alarms
can be ignored.
DDTS SLSks62078
Initialization of boards of type P16S16, P16S1 and P16S1-4 will fail when terminal loops are
configured on port 9 to 12. This happens after cold start of system or when these boards are
pulled/plugged or during ISU.
Precaution:
After any maintenance action it is recommended to remove loopbacks when they are not
longer needed.
DDTS SLSks63584
If a GMRE drop port is part of MS-SPRING the traffic may get lost if GMRE processes are
restarted while MS-SPRING is not in IDLE state.
(only fixed in R4.6.26 RP1, not fixed in R4.6.27 and R4.6.28)
DDTS SLSks62632
Following an equipment switch of the matrix, sometimes transitory LAPD CSF alarms occur for
one or more termination points. The alarms persist for just a few seconds, but are visible in
the alarm list and GUI for some minutes. These are harmless false alarms and can be ignored.
DDTS SLSks62830
When a unidirectional SNCP/N path is established via GMRE, an RDI condition is incorrectly
detected and alarmed for that path.

ED17
November 2014
31 of 49
DDTS SLSks62866
When a board is deleted from the system, loopbacks that were present on the board may not be
properly deleted from the system. This has been resolved by adding a restriction that boards only
can be deleted if no loopback is present.
DDTS SLSks63163
Performance monitoring counts for low order connections (both low order shelf and LAX
connections) can be incorrectly displayed as 0, 32768 or 65537. This applies to both 15 minute
and 24 hour counts. Additionally, the elapsed time indicated for current data may not be
displayed correctly.
DDTS SLSks63241
In the synchronization view block diagram in both the CT and OMS GUI, the quality of the
internal oscillator is incorrectly displayed as G.811 instead of G.813 whenever an external
G.811 timing source is connected. If the external G.811 source is disconnected the internal
oscillator is correctly displayed as G.813. This behavior occurs only in R4.6.26.
DDTS SLSks63261
When a large number of low order cross-connects are connected in a snake configuration in a
low order shelf, TU-AIS is sometimes generated somewhere along the path when an LA20 MSP
switch is performed. Traffic is interrupted. Traffic can be recovered by resetting the LX160
boards involved.
DDTS SLSks63274
False high temperature alarms are still sometimes incorrectly reported in R4.6.26. In R4.6.27
the software polling of temperature indicators has been made more robust by performing
multiple reads and discarding inconsistent or invalid data.
DDTS SLSks63475
SW on Windows XP PCs might be configured that 1678 CT installation wont be completed. In
such cases the CT will not start correctly afterwards.

DDTS SLSks63434
Malformed LSP packets are improperly forwarded by the 1678 MCC. Such packets should be
dropped instead.
DDTS SLSks63572
A large volume of PM data collection was exhausting internal buffer space on the LAX40,
causing continuous reboots. This could have happened on an Active or Standby LAX40 with
enough PM events, but it was most likely on the Standby LAX40 just after booting, when it has
to synchronize its PM data from the Active pack.
The buffer management was reworked to prevent this, regardless of the PM data load.
DDTS SLSks63595
LO-TU12 SNCP rings on a low order box cannot successfully be de-implemented by the RM.

ED17
November 2014
32 of 49
DDTS SLSks63626
Communications between the MIB and VHM processes sometimes fails. This results in new
provisioning request such as cross-connects from actually being implemented in the hardware.
This situation can be recovered by restarting the VHM process.
DDTS SLSks63725
In the case of certain power supply failures on P4S64 cards, the card is properly alarmed as
RUP, but no indication of an optical line failure is made. As a result, downstream MS-SPRING
will not occur and traffic will not be protected.
DDTS SLSks63769
An indication of "backup FAILED" is sometimes incorrectly displayed on the CT after a backup is
executed via the equipment view.
DDTS SLSks63777
Memory that is used to support MSP switching sometimes becomes loaded with inconsistent
values that result in subsequent MSP switches being blocked. In R4.6.28 changes have been
made to both prevent such inconsistent values from being written to memory and to make the
MSP switch function tolerant of such values.
DDTS SLSks63785
Zombies are created by process vmstat which is invoked in context of perl script HAD on FLC
which is running on EM and DCR. Zombies are usually a minor problem but they block an entry
in process list.
DDTS SLSks63787
In releases prior to R4.6.28, the SKY, ION and CORE CDs will fail to automatically start up and
initiate the software copy process in a Windows 7 environment. Further, if manual processes
are used to overcome this and initiate the software copy, the version of cygwin and some shell
scripts that are installed on the PC are not fully compatible with Windows 7 and will not
support the software installation process.
In R4.6.28 the auto-start issue has been corrected for the SKY and ION CDs, but is still an issue
for the CORE CD. The version of cygwin and associated shell scripts have been updated so as to
be fully compatible with Windows 7.

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

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

ED17
November 2014
34 of 49
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 cannot detect directly, why the matrix does not become active.
DDTS SLSks46966
System shall report GFP LOF but no alarm is raised.
DDTS SLSks47038
GbE LCAS: According to the standard a LCAS source should continue sending traffic with the
last member state in case of a unidirectional failure of all members of a VCG, but the system
blocks entirely the transmit side.
DDTS SLSks47256
At PM-creation on TU12 it may occur that TCN for 15min NE or FE (BBE, ES and SES) is reported
and cleared simultaneously (same second), if threshold crossed notifications are set for 15min
and 24h for NE and FE (BBE,ES and SES) prior to deleting of PM on TU12.
DDTS SLSks47296
During an InServiceUpgrade the IO-EPS in the OEDs is not working.
DDTS SLSks49244
For disconnected ports the reported J1/C2 may be not equal to 0.
DDTS SLSks53801
For all synchronization related alarms the alarm clearing time stamp is reported identical to
the alarm raising time stamp in the alarm list.
DDTS SLSks57307
In rare cases the configuration of host-ID and OSPF router-ID is not properly done in the
system. Please contact TEC.

ED17
November 2014
35 of 49
DDTS SLSks57788
On 10GE and ES64 the PM counter of TDFin is not counting the following cases:
* frames out of bandwidth according to traffic descriptor.
* frames out of the classifier (priority from Q-tagged stream changed).
As both cases cause packet loss TDFin should be counted in current PM and Maintenance PM.
DDTS SLSks58779
If an already created internal loopback is re-created on PxS64X board the traffic is affected for
some seconds.
DDTS SLSks60107
In rare cases highTemperature alarms might be reported temporary even if the temperature
conditions are in the specification.
DDTS SLSks60266
The archived PM history data in NM does not contain the data for modVC4 TPs.
DDTS SLSks60356
The RST convergence time might be up to 16 seconds while the external LAN cable is unplugged
on one FLC.
DDTS SLSks60579
A FLC switch might take up to 15 minutes in case of huge number of LO XC; the supervision is
lost during this time.
DDTS SLSks61038
The "Maximum number of VCG" is limited on 10GE boards in EVPL configuration. Only 16 VCGs
are supported and the creation of additional VCGs is rejected with error message "HW
capability of this card is exceeded". So the maximum supported number of VCGs is 32.
DDTS SLSks62015
In configurations with more than 16 OED shelves it may happen that the ISU aborts in step 29
(saveConfigData) due to a missing synchronization of the single steps.
DDTS SLSks62341
In the craft terminal Station Alarm Filter dialog the probable cause for TOOR (Temperature Out
Of Range) is missing in the list of available causes.
DDTS SLSks62633
During ISU from R4.3.x ES64 boards may declare a RUP alarm resulting in the loss of all ES64
traffic.
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.
ED17
November 2014
36 of 49
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 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 SLSks36384
Control Plane failures do not affect the Dataplane traffic.
If however the Operator tries to de-implement the path when there is a control plane failure,
the resources are freed from the Head node up to the point where there is no CP
communication. The remaining path resources remain allocated until the CP failure is repaired.
Workaround:
Free the remaining resources via the CLI from Tail node (config lsp lspindex <123> adminState
Down).
DDTS SLSks38999
Equipment Provisioning: After changing the active EM address via EP dialog, the SH/CT
connection to the NE will break.
Workaround:
Restart the application or perform an FLC switch.
DDTS SLSks45477
Canceling the TP Search, by pressing the cancel Button, can sometimes block the work with the
USM. No other activities are possible.
Workaround:
Restart the emlim (EMLIMDXCQ3) of this Network Element on NM.
DDTS SLSks46312
LCAS Bandwidth modification on GbE pathes using RM may lead to traffic hits if the reduction
of the bandwidth is done in the wrong way (single step).
Workaround:
It has to be proceeded in two steps as follows:
- server trail deactivation
- removal of those deactivated server trails
ED17
November 2014
37 of 49
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 SLSks50241
Event Log filtering may block the application Event Log Browsing on local CT.
Workaround:
Within the file C:/ALCATEL/CT-Kv3.3.0/elb/conf/LogBrowsing.cfg the parameter
Q3_PROTOCOL has to be changed from DIRECT to NESIM.
DDTS SLSks51072
Using the OED70, the HCMATRIX reboots once opening the transmission view of link board slot
29.
Workaround: Use the alarm list to check alarms on this port.
DDTS SLSks55801
In AUTO Port Mode it is not possible to change the ASAP.
Workaround: set Port Mode to MONITORED.
DDTS SLSks62571
On nodes with GMRE when opening in RM/ASON GUI the LSP console it may happen that the CLI
command output is truncated if it is a long output.
Workaround:
Make a ssh/telnet login on the FLC and start a local CLI session from there. The outputs in this
session are not truncated.
DDTS SLSks56367:
When the LCAS WTR time on a ES64 or 10GE board is set to a value below 10s then the actual
LCAS WTR time will be 10s.
DDTS SLSks56459
If a port view is open on a port which is involved in a GMRE soft rerouting it may happen that
the icon indicating an active TrailMonitor appears and stays even if it is not configured
anymore.
Workaround: hide and unhide the TPs.
DDTS SLSks56621:
10GE continues to send PAUSE after remote side transmit is stopped.
DDTS SLSks58148
Changes of ES64 traffic descriptor of a flow might cause a loss of a few frames.
DDTS SLSks60414
In rare cases unexpected Threshold Crossing alarms might be reported after LX160 board reset.
Workaround: perform an LX160 EPS switch

ED17
November 2014
38 of 49
DDTS SLSks61920
An FLC switch triggered via the EP (Equipment Provisioning) dialog may lead to a partial loss of
the OSI forwarding table.
Workaround:
Perform the FLC switch with command line 'SSUDiag -c switch' on the active FLC.
DDTS SLSks63312
Unplugging an active SYNTH16 version 3AL98282ABAA after a cold start of the pack leads to an
approximately 10 second traffic hit or permanent traffic loss.
Workaround:
This can be avoided by toggling EPS or MSP manually after the cold start. This does not occur
with other versions of the board.
DDTS SLSks63335 (SLSks47097, SLSks40960)
For GbE virtual concatenated traffic and LCAS enabled between a 1GBE port of 1678MCC and
other vendor equipment traffic might be impacted if a corrupted member of the GbE signal
would destroy the proper sequence of the members.
Traffic might be impacted in this way. Most probably this member corruption would be created
if the LCAS transition state is not detected correctly by the HW device. One possibility of a
destroyed member could be an exceeded differential delay, which is alarmed by the Exceeded
Differential Delay (EDD) alarm.
Workaround:
Depending on the nature of the issue the following sequence of actions has to be followed:
1.
If an exceeded differential delay is reported by EDD alarm this condition has to be

removed first, e.g. by rerouting the relevant members.
2.
Once no EDD alarm is reported the suspected Ethernet members have to be

deactivated/activated on the remote site whereby LCAS is recreated.

ED17
November 2014
39 of 49
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).
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

ED17
November 2014
40 of 49
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 Svalue and not the one with the least concatenation level is chosen.
DDTS SLSks35823
ALS is not working on STM64 boards in case of a configured terminal loop.
DDTS SLSks36469
For enabled LCAS the P16GEFC board sends the LCAS control word ADD instead of DNU from
source side to sink side.
DDTS SLSks36761
For a P16GEFC, P8GEFC or P4GEFC board all ports must be configured either with VC4XV or
VC3XV. It is not possible to have a mixture of VC4XV and VC3XV on the same board.
DDTS SLSks36829
Sometime the cross-connection on an AU3#2 is not working properly (B3 errors).
DDTS SLSks37270
GbE: LOF of GFP frames not implemented
DDTS SLSks37725
Single Ended MSP 1:N does not work on 1670OED for STM-4 when mixed configuration AU4 and
AU4-4c is used.
DDTS SLSks37996
The 2 sec restoration requirement is not fulfilled in contention scenarios.
DDTS SLSks38661
After inserting P16S1N in the 1670 OED shelf it may happen that the internal clock of shelf goes
to holdover which is indicated by a TIP alarm at CT. After a few seconds the timing is working
well and the alarm disappears.
DDTS SLSks38692
On 1662 OED EPS can exceed switching time of 50ms if WTR is active.
ED17
November 2014
41 of 49
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.
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 cannot 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
InServiceUpgrade.
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.
ED17
November 2014
42 of 49
DDTS SLSks47049
ISUs that include an upgrade of the NEWTON FPGA cause an interruption on 10GE EPL traffic.
DDTS SLSks47053
ISUs that include an upgrade of the NEWTON FPGA cause an interruption on 10GE EVPL traffic.
DDTS SLSks47057
In rare cases plug out / plug in of a STM64 V board may result in a LOP on MV642 module
DDTS SLSks47196
During 10 GE operation the displayed counter values for the TxFrame counter show a variance
due to not exactly synchronized time intervals. Nevertheless the total number of frames
counted is correct.
DDTS SLSks47828
If a 1 GbE port has Auto-negotiation enabled, it might not be put into service if the signal is
looped on itself.
DDTS SLSks48133
If there is a LOS on the incoming signal of a 1GbEth port, and an internal loop of is applied, the
consequent action will switch off the laser of this port.
DDTS SLSks48358
OSI Reachable Address Prefixes (RAP) are not supported.
DDTS SLSks48423
Frames with multiple failures might be counted multiple times in error counters.
DDTS SLSks48440
Using a GBEVCG with LCAS enabled, deleting VCs from it might leave the deleted members
with incorrect control words. The functionality of the remaining members in the VCG is not
affected.
DDTS SLSks48592
UNEQ detection of all GbE boards might be corrupted by a valid GFP mapped Ethernet signal
generated by a port in slot position 2.
DDTS SLSks48630
The 1GbE board has the limitation not to rise the Signal Degrade alarm if it receives B3 errors
from TDM side. Nevertheless do B3 errors result in PM counting.
DDTS SLSks48721
In rare cases it might occur that after a MX switch all 1-day TCA alarms are re-reported, which
were already reported before.
DDTS SLSks48797
Using the 1678 GbE interface, runt frames in the in direction, i.e. undersized frames with
correct FCS from Ethernet to TDM side, are discarded as expected. But they are not counted in
any of the available counters. They should be counted in TRSEF counter.

ED17
November 2014
43 of 49
DDTS SLSks49471
If a GBE port receives from TDM side a GFP frame without user data, the payload type of the
frame cannot be determined exactly. Therefore the default assumption is that all frames of
this kind are CSF frames. Therefore, any received unexpected payload type is reported as CSF.
DDTS SLSks50125
As RUP alarm is not evaluated by GMRE, the local GMRE will continue to operate in normal
mode in case. This means that inactive backups will not be rerouted, and node will continue to
advertise resources. If cause for RUP alarm is traffic affecting the neighboring GMREs will
trigger restoration.
DDTS SLSks50320
If GbE paths are setup using Odd and Even diverse routing but without LCAS enabled, there
could be total traffic loss if no diverse routes are found during restoration. It is recommended
for GbE paths to enable LCAS with Odd and Even diverse routing or to avoid Odd and Even
diverse routing.
DDTS SLSks50507
In the ES64 ZIC it is not possible to modify a traffic descriptor (TD) after activating.
DDTS SLSks50582
In the ES64 ZIC all ports (1-252) are shown even though only port numbers 1-64 & 129-192 are
valid.
DDTS SLSks50607
In case of an active SQM alarm, the 10GE board with a VC4xv configuration will generate
additionally the LOA alarm.
DDTS SLSks50816
In a scenario with a 1GbE board receiving a User Payload Mismatch from TDM side, it will not
generate a CSF indication even if bidirectional server fault propagation is enabled.
DDTS SLSks50822
On 1GE ports, there is no aAIS (consequent action) generation after/upon detection of PLTM
(dPLTM). Instead, the GBE traffic coming from the SDH/TDM-side is forwarded.
DDTS SLSks54135
All CT users have always operator permissions, even if the role in the profile is different.
DDTS SLSks55242
In rare cases PM TC alarm time stamps of clearing time could be reported earlier than
appearing time
ES64: If invalid C2 value is received on VCG, an SSF alarm is raised instead of PLTM alarm.
ES64: ES64 facilities pass undersized (runt) Ethernet frames. The ES64 pads them to 64 bytes.
ES64: Per-Q PM octet counters do not count correctly for all frame sizes. The Per-Q counters
are inaccurate by up to four bytes less per frame.

ED17
November 2014
44 of 49
DDTS SLSks56127
OED1662: A manual clock switch from a clock source connected to main shelf to a T2-clock
source connected to an OED1662 (and vice versa) could cause traffic hits.
DDTS SLSks57772
On PM per Flow 24h History counters first interval may change Suspected Flag from True to
False after the interval is closed.
DDTS SLSks57790
On PM per Queue 24h History Suspected Flag may be inconsistent on some intervals after reset
of counters.
DDTS SLSks57792
On PM per Queue 24h History interval is not cleared after stopping and starting of the counters
DDTS SLSks57656
In the bar graphics, the 15min / 24h Ethernet History Data counters are not correct. Counters
are too small by factor 10
DDTS SLSks59704
The MS near-end PM counters may not be counting correctly in case of phase shifts.
DDTS SLSks61063
For using the ES64 ZIC only the Microsoft Internet Explorer is supported.
DDTS SLSks62628
For new laptops/PC which shall be installed with a craft terminal the Cygwin installation should
be done from a SKYxx-CD before the craft terminal installation. The Cygwin installation from
the craft terminal CD should be disabled during installation.
DDTS SLSks63538
Transparent DCC configurations, with a real network element connected on one port of the
connection and a loopback on the other, can generate an excessive amount of DCN traffic.
Multiple instances of such a configuration can generate enough DCN traffic to cause the DCC
Router (DCR) on the FLC to reboot continuously. Multiple instances of such configurations
should be avoided.
.
7.1.4
Specific system behaviours
DDTS SLSks34638
If you perform a lockout action on a protected LO connection immediately after a forced
switch (to protected or protecting side) the protection state in the cross-connection dialogue is
not updated correctly: forced is shown instead of lockout.
Correcting action:
Refresh the dialogue using the 'search' button or use a 'release force' before the 'lockout'.
DDTS SLSks36744
2F-MSSPRING should not be combined with path monitoring on the ring. A monitor on a path
that is part of an 2F-MSSPRING protection scheme will only work as long as the monitored path
runs over the nominal working section.

ED17
November 2014
45 of 49
DDTS SLSks39473
On a STM-64 board, a line loop is only possible if the port is cross connected.
DDTS SLSks46953
In case of a total loss of capacity in one direction on a 1GE port with LCAS enabled an
unexpected BWR alarm is reported additionally to the expected SSF.
DDTS SLSks48945
If in an MSP 1:N protection scheme two working channels show failure conditions at the same
time, the protection mechanism does not take the channel ID into account. Therefore it is not
guaranteed that the section with the lowest section numbers takes priority.
DDTS SLSks49628
With double simultaneous fibre cuts where both I-NNI link are in one 1+1 MSP protection group,
the restoration times are not below 2 seconds. Since both MSP links are affected, there is no
50msec protection. Furthermore, the dual fibre alarms are reported to GMRE slowly from the
hardware resulting in restoration times above 2 secs and in the region of up to 4 secs.
DDTS SLSks48055
After cold-start of a STM-16/OC48 board, a LOF that was declared before is not re-declared.
Instead, a LOP is reported.
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.

ED17
November 2014
46 of 49
DDTS SLSks50351
Upon generation of an ES64 EPS protection group
- a CSF alarm is visible on CT for about 30s on both involved ES64 boards.
- a RUP alarm is visible on CT for 4 minutes on the protecting ES64
- an ICP alarm is present on CT for the protecting ES64 and stays present during the DL state.
- the protecting ES64 shows a download state for about 5 minutes.
- after the DL both ES64 boards show CSF alarm again for about 1 minute.
- all alarm disappear
DDTS SLSks50520
On 1GE ports, FCS errored frames are not discarded in the OUT-direction from TDM to the
Ethernet line. Such frames are counted in the TRSEF counter.
DDTS 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.
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 SLSks51164
If there are bit errors on the nominal route, reversion to nominal will not succeed. The revert
to nominal using bridge and roll will be retried periodically but not succeed.
In such situations, the Operator is recommended to check the nominal route for bit errors and
repair them. Until the bit errors are repaired, it is recommended to modify such links, with
signal degrade alarms, to administrative state ShuttingDown to prevent new traffic using the
links.
ES64: All Layer 2 control packets are tunnelled through the ES64 board.
ES64: Setting service of two classifiers:
vlan x pri a
vlan y pri b
Packets with vlan x pri b and vlan y pri a will pass as well, in other words, vlan+pri filtering
allows more traffic through than it should
ES64: Two classifiers, one with vlan dont care and the other with untagged, cannot be
configured to the same service.
ED17
November 2014
47 of 49
DDTS SLSks56179
Etsflow activation can take up to 9 seconds
DDTS SLSks57243
LACP Interop between 7750 and 1678 MCC(ES64) - the following has been observed:
- If LACP is disabled at ES64 first and then at far-end NE, traffic is down.
- If LACP is disabled at far-end NE and then at ES64, everything is ok.
DDTS SLSks57917
In MSP 1+1 dual-ended configuration + ALS is enabled on the involved ports the traffic is
switched back to working channel unexpectedly after clearing a double failure.
DDTS SLS58562
SDH/SONET SNCP protected EPL services with LPT function may cause transient local faults at
SNCP switches on the 10GE interface, which are cleared within few milliseconds. A client
device should use a fault persistent time filter (hold-off time) before triggering any actions like
rerouting.
DDTS SLSks59896
Bit errors might appear during the first HO matrix EPS after a nodes cold start.
DDTS SLSks61070
An auto switch is triggered after an internal loop has been created on MSP port. It is triggered
by a section alarm, which is also counted in PM data, but not displayed.
DDTS SLSks61400
An EIDP (External Interface Device Problem) alarm for an IO board may be cleared and redeclared during a HO matrix switch.
DDTS SLSks62678
In configurations with OED62 and Dual LAN cabling the LAN redundancy is not effective as long
as the Synth16 boards are not aligned.
DDTS SLSks62691
Internal loopbacks on P16S1S4 and P16S16 boards may generate unexpected UAT alarms and
UAS PM counters are counting for MS/RSTTPs.
DDTS SLSks62743
In configurations with LO-Shelf the MSP switching times for the internal cabling between main
shelf and LO-shelf (LAC40-LA20 cabling) may slightly exceed 50ms.
DDTS SLSks63774
In addition to EPL service, supported in R4.3.x, from R4.5.x EVPL service is supported.
Consequent to EVPL introduction with GMRE support of ISA ES64 the internal naming scheme
used thus far could not be used anymore due to higher number of possible flows. This is why
the GMRE internal format had to be changed to handle all ETH SPC Endpoints.
In relevant NMS (RM R8.1.P3 / OMS 9.x etc) only the new format is supported for ETH trail
implementation. Therefore with these NMS releases a ETH bandwidth expansion of a path
previously implemented in an earlier NMS release (according to old format) doesnt work
without unless such ETH paths (according to old format) are first deleted and then re-created
in advance, this effectively clean-ups the ETH port configuration in NMS database and thus will
consequently allow ETH bandwidth expansion as and if required.
ED17
November 2014
48 of 49
Due to the change of the internal numbering scheme for ETH paths in 1678 R4.5, the band
width of ETH paths whose trails were created with the old format cannot be expanded with
trails using the new format.
NB: Though the expansion will not succeed, the existing ETH traffic will not be impacted.
Both, restoration of existing ETH traffic and path provisioning of the new ETH traffic work
without any impact.
The band width of former implemented ETH paths can be expanded, once they are deleted
then re-created in advance to clean-up the ETH port configuration in NMS database.
Solution: ETH paths, which require deletion and recreation to ensure bandwidth expansion can
be performed, can be identified using the 1678 Health Care Check tool (test 10.2.6). From this,
proactive maintenance can be performed to remove and re-create the ETH path and enable
bandwidth expansion.
End of Document
ED17
November 2014
49 of 49

3AG24101BGAAFMZZA - V1 - 1678 MCC Release 04.06.x Product Release Note

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3AG24101BGAAFMZZA - V1 - 1678 MCC Release 04.06.x Product Release Note

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent

1678 MCC | R4.6.x

3AG 24101 BGAA FMZZA

Release Note for R4.6.0

Release Note for R4.6.1 RP1/R4.6.11

Release Note for R4.6.2

Update for R4.6.21

Update for R4.6.22

Update for R4.6.23

Update for R4.6.22 RP1/R4.6.23 RP1

Update for R4.6.24

Update for R4.6.11 RP2

Update for R4.6.24 RP1

Update for R4.6.25

Update for R4.6.25 RP1

Update for R4.6.25 RP2

Update for R4.6.26

Update for R4.6.27

Update for R4.6.26 RP1

Update for R4.6.28

3AG 24101 BGAA FMZZA

REFERENCED DOCUMENTS ..................................................................................... 5

DEFINITIONS AND ABBREVIATIONS ......................................................................... 5

KEY FEATURES ........................................................................................................ 11

PRODUCT COMPOSITION ........................................................................................ 16

Software 1678MCC R4.6.x ............................................................................. 16

Solved problems/restrictions/warnings R4.6.1 RP1/R4.6.11 ........................ 21

Solved problems .............................................................................................. 21

Solved problems .............................................................................................. 21

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

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

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

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

Solved problems .............................................................................................. 24

Solved problems .............................................................................................. 24

Solved problems with workaround ................................................................... 26

Solved problems/restrictions/warnings R4.6.11 RP2 .................................... 21

Solved problems/restrictions/warnings R4.6.24 RP1 .................................... 26

Solved problems/restrictions/warnings R4.6.25 RP1 .................................... 29

Solved problems/restrictions/warnings R4.6.25 RP2 .................................... 29

Solved problems/restrictions/warnings R4.6.26 ........................................... 29

3AG 24101 BGAA FMZZA

Solved problems/restrictions/warnings R4.6.26 RP1 .................................... 31

Solved problems/restrictions/warnings R4.6.27 ........................................... 31

Solved problems/restrictions/warnings R4.6.28 ........................................... 32

KNOWN PROBLEMS/RESTRICTIONS/WARNINGS ................................................. 34

Known problems/restrictions/warnings in R4.6 ............................................ 34

3AG 24101 BGAA FMZZA

Known problems .............................................................................................. 34

3AG 24101 BGAA

DEFINITIONS AND ABBREVIATIONS

3AG 24101 BGAA FMZZA

Higher Order Path Termination

Multi Longitudinal mode

Plesiochronous Physical interface

3AG 24101 BGAA FMZZA

Ultra Long Haul

Key functionalities introduced with previous releases:

3AG 24101 BGAA FMZZA

- ETH VLAN classification

3AG 24101 BGAA FMZZA

Key functionalities introduced with R4.6.2:

GMRE: NMS event log (activity log)