3AG24101BDAAFMZZA_V1_1678 MCC Release 04.03.x Product Release Note

3AG 24101 BDAA FMZZA Alcatel-Lucent Proprietary

ED26 Use pursuant to applicable agreements

October 2012

Alcatel-Lucent 1678 MCC | R4.3.x

Product Release Notes

3AG 24101 BDAA FMZZA Alcatel-Lucent Proprietary 2 of 61


October 2012

REVISION HISTORY

ED DATE COMMENTS ORIGINATOR APPROVER

01 071219 Release Note for R4.3 H. Bauer A.Kemmler

02 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


14 090610 Update for editorials H. Bauer A.Kemmler




18 100304 Update for R4.3.20 RP1 C. Wulf A.Kemmler

19 100728 Update for R4.3.21 C. Wulf A.Kemmler

20 101216 Update for R4.3.20 RP2 C.Wulf A. Kemmler

21 110114 Update for R4.3.20 RP3 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 Update for R4.3.23 RP3 C. Wulf J. Webster

26 121001 Update for R4.3.23 RP4 C. Wulf J. Webster



October 2012

CONTENTS

1 REFERENCED DOCUMENTS........................................................................................ 6

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

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

4 PRODUCT COMPOSITION .......................................................................................... 15 4.1 Software 1678MCC R4.x ................................................................................... 15 4.2 Hardware 1678MCC R4.x ................................................................................. 15 4.3 Documentation ................................................................................................ 16 4.4 SW maintenance raw patch releases .............................................................. 16

5 INSTALLATION PROCEDURE ..................................................................................... 19 5.1 New installation .............................................................................................. 19 5.2 In service update / upgrade ............................................................................ 19

6 SOLVED PROBLEMS/RESTRICTIONS/WARNINGS .................................................. 21 6.1 Solved problems/restrictions/warnings R4.1.1 ............................................... 21

6.1.1 Solved problems with workaround ................................................................... 21 6.1.2 Solved functional restrictions and warnings .................................................... 21 6.1.3 Solved specific system behaviours .................................................................. 21

6.2 Solved problems/restrictions/warnings R4.2 .................................................. 22 6.2.1 Solved problems .............................................................................................. 22 6.2.2 Solved problems with workaround ................................................................... 22 6.2.3 Solved restrictions and warnings ..................................................................... 22 6.2.4 Solved specific system behaviours .................................................................. 22

6.3 Solved problems/restrictions/warnings R4.3 .................................................. 23 6.3.1 Solved problems .............................................................................................. 23 6.3.2 Solved problems with workaround ................................................................... 23 6.3.3 Solved restrictions and warnings ..................................................................... 24 6.3.4 Solved specific system behaviours .................................................................. 24

6.4 Solved problems/restrictions/warnings R4.3.1 ............................................... 25 6.4.1 Solved problems .............................................................................................. 25 6.4.2 Solved problems with workaround ................................................................... 25 6.4.3 Solved restrictions and warnings ..................................................................... 25

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

6.6 Solved problems/restrictions/warnings in R4.3.1 RP3 ................................... 26 6.6.1 Solved functional restrictions and warnings .................................................... 26

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

6.8 Solved problems/restrictions/warnings in R4.3.1 RP5 ................................... 26 6.8.1 Solved functional restrictions and warnings .................................................... 26

6.9 Solved problems/restrictions/warnings in R4.3.11 ......................................... 26 6.9.1 Solved problems .............................................................................................. 26 6.9.2 Solved functional restrictions and warnings .................................................... 26

6.10 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 Solved problems/restrictions/warnings in R4.3.11 RP2 .................................. 27 6.11.1 Solved problems .............................................................................................. 27 6.11.2 Solved functional restrictions and warnings .................................................... 27



October 2012

6.11.3 Solved specific system behaviours .................................................................. 27 6.12 Solved problems/restrictions/warnings in R4.3.12 ......................................... 28

6.12.1 Solved problems .............................................................................................. 28 6.12.2 Solved problems with workaround ................................................................... 28 6.12.3 Solved functional restrictions and warnings .................................................... 28 6.12.4 Solved specific system behaviours .................................................................. 28

6.13 Solved problems/restrictions/warnings in R4.3.12 RP1 .................................. 28 6.13.1 Solved functional restrictions and warnings .................................................... 28

6.14 Solved problems/restrictions/warnings in R4.3.12 RP2 .................................. 28 6.14.1 Solved problems .............................................................................................. 29 6.14.2 Solved functional restrictions and warnings .................................................... 29

6.15 Solved problems/restrictions/warnings in R4.3.12 RP3 .................................. 29 6.15.1 Solved problems .............................................................................................. 29 6.15.2 Solved problems with workaround ................................................................... 29 6.15.3 Solved functional restrictions and warnings .................................................... 29

6.16 Solved problems/restrictions/warnings in R4.3.12 RP4 .................................. 30 6.16.1 Solved problems with workaround ................................................................... 30 6.16.2 Solved functional restrictions and warnings .................................................... 30

6.17 Solved problems/restrictions/warnings in R4.3.13 ......................................... 31 6.17.1 Solved problems .............................................................................................. 31 6.17.2 Solved functional restrictions and warnings .................................................... 31 6.17.3 Solved specific system behaviours .................................................................. 31

6.18 Solved problems/restrictions/warnings in R4.3.13 RP1 .................................. 31 6.18.1 Solved functional restrictions and warnings .................................................... 31



6.21 Solved problems/restrictions/warnings in R4.3.14 ......................................... 33 6.21.1 Solved problems .............................................................................................. 33 6.21.2 Solved problems with workaround ................................................................... 34 6.21.3 Solved functional restrictions and warnings .................................................... 34


6.23 Solved problems/restrictions/warnings in R4.3.16 ......................................... 36 6.23.1 Solved problems .............................................................................................. 36 6.23.2 Solved problems with workaround ................................................................... 37 6.23.3 Solved functional restrictions and warnings .................................................... 37 6.23.4 Solved specific system behaviours .................................................................. 37

6.24 Solved problems/restrictions/warnings in R4.3.17 ......................................... 37 6.24.1 Solved problems .............................................................................................. 37

6.25 Solved problems/restrictions/warnings in R4.3.18 ......................................... 38 6.25.1 Solved problems .............................................................................................. 38 6.25.2 Solved problems with workaround ................................................................... 38 6.25.3 Solved functional restrictions and warnings .................................................... 38 6.25.4 Solved specific system behaviours .................................................................. 38




October 2012

6.27 Solved problems/restrictions/warnings in R4.3.20 ......................................... 39 6.27.1 Solved problems .............................................................................................. 39 6.27.2 Specific system behaviours ............................................................................. 39

6.28 Solved problems/restrictions/warnings in R4.3.20 RP1 .................................. 39 6.28.1 Solved problems .............................................................................................. 39


6.30 Solved problems/restrictions/warnings in R4.3.20 RP3 .................................. 40 6.30.1 Solved specific systems behaviour .................................................................. 40

6.31 Solved problems/restrictions/warnings in R4.3.21 ......................................... 40 6.31.1 Solved problems .............................................................................................. 40 6.31.2 Solved problems with workaround ................................................................... 41

6.32 Solved problems/restrictions/warnings in R4.3.22 ......................................... 41 6.32.1 Solved problems .............................................................................................. 41 6.32.2 Solved specific system behaviours .................................................................. 42






6.38 Solved problems/restrictions/warnings in R4.3.2A (CI) ................................. 44 6.38.1 Solved problems .............................................................................................. 44 6.38.2 Solved problems with workaround ................................................................... 44 6.38.3 Solved functional restrictions and warnings .................................................... 44 6.38.4 Solved specific system behaviours .................................................................. 45

7 KNOWN PROBLEMS/RESTRICTIONS/WARNINGS ................................................... 45 7.1 Known problems/restrictions/warnings found in R4.1.1 ................................ 45

7.1.1 Known problems .............................................................................................. 45 7.1.2 Known problems with workaround ................................................................... 47 7.1.3 Functional restrictions and warnings ............................................................... 48 7.1.4 Specific system behaviours ............................................................................. 54

7.2 Known problems/restrictions/warnings found in R4.2 ................................... 56 7.2.1 Known problems .............................................................................................. 56 7.2.2 Known problems with workaround ................................................................... 56 7.2.3 Functional restrictions and warnings ............................................................... 56 7.2.4 Specific system behaviours ............................................................................. 56

7.3 Known problems/restrictions/warnings found in R4.3 ................................... 57 7.3.1 Known problems with workaround ................................................................... 57 7.3.2 Functional restrictions and warnings ............................................................... 57 7.3.3 Specific system behaviours ............................................................................. 58

7.4 Known problems/restrictions/warnings found in R4.3.1x .............................. 58 7.4.1 Known problems .............................................................................................. 58 7.4.2 Known problems with workaround ................................................................... 59 7.4.3 Functional restrictions and warnings ............................................................... 59 7.4.4 Specific system behaviours ............................................................................. 60

7.5 Known problems/restrictions/warnings found in R4.3.2 CI ............................ 60 7.5.1 Specific system behaviours ............................................................................. 60



October 2012

1 REFERENCED DOCUMENTS

[1] Validation Release Note 3AG 24101 BDAA FAZZA [2] Software Development Release 3AG 24101 BDAA PVZZA [3] Feature List 3AG 24101 BDAA FLZZA

2 DEFINITIONS AND ABBREVIATIONS

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



October 2012

CSR Customer Specific Release CT Craft Terminal DC Direct Current DCC Data Communication Channel DCCM DCC on Multiplex Section (D4D12) DCCP DCC on Path Overhead DCCR DCC on Regenerator Section (D1D3) D&C Drop and Continue DCM Dispersion Compensation Module DCN Data Communication Network DCR DCC Router DCU Dispersion Compensation Unit DDF Digital Distribution Frame DXC Digital Cross Connect EC Equipment Controller ECC Embedded Control Channel ECT Equipment Craft Terminal EIDEC Enhanced IDE Controller EMI/EMC Electromagnetic interference / Electromagnetic compatibility EPS Equipment Protection Switching EQUICO Equipment Controller ESD Electrostatic discharges ETSI European Telecommunication Standards Institute FC/PC Type of optical connector FCS Frame Check Sequence FEBE Far End Block Error FEC Forward Error Correction FEPROM Flesh Electrically erasable programmable read only memory FERF Far End Receive Failure FLC First Level Controller FLCCONGI First Level Controller+Control and General Interface Board FLCSERV FLCSERVICE (First Level Controller + SERVICE Board) FPE Functional Protection Earth FPGA Field Programmable Gate Array G.ASTN GMPLS Automatically Switched Transport Network GbE Gigabit Ethernet GBOS Generic Basic Operating System GETHA Gigabit Ethernet Access card GFP Generic Frame Procedure gGOS Performance improved version of GBOS GMPLS Generalized Multiprotocol Label Switching GMRE GMPLS Routing Engine GND Ground GNE Gateway Network Element GRE Generic Routing Encapsulation GUI Graphical User Interface HMU Housekeeping Monitoring Unit HO High Order HOA High Order Adaptation HOI High Order Interface HPC High order Path Connection HPOM High order Path Overhead Monitoring



October 2012

HPROT High Speed Protection Board HPT Higher Order Path Termination HSUT High order Supervisory Unequipped Termination HW Hardware II intra-Office ICS item Change Status IEC International Electrotechnical Committee IEEE Institute of Electrical and Electronic Engineering IETF Internet Engineering task Force ILM Integrated Laser Modulator IN Input INNI Internal NetworktoNetwork Interface IND Indicative alarm INT Internal Local Alarms ION Intelligent Optical Network I/O Input/Output IP Internet Protocol IPCC IP Control Channel ISA Integrated Service Adapter ISO International Organisation for standardization ISPB Intra Shelf Processor Bus ISU In Service Upgrade JE1 JE2 JE3 Joint Engineering L Long Haul LA20 LO Adaptation Board 20G LAC40 Lower Order Matrix Link 40G LAN Local Area Network LAX40 LO Adaption and Matrix Board 40G LAX20 LO Adaption and Matrix Board 20G LC Type of optical connector LCAS Link Capacity Adjustment Scheme LDSSHUT Command for ALS LED Light Emission Diode LIU Line Interface Unit LMP Link Management Protocol LO Low Order LOI Low Order Interface LOM Loss Of Multiframe LOP Loss Of Pointer LOPP Low Order Pointer Processing LOS Loss Of Signal LPA Lower order path adaption LPC Lower order path connection LPM Loopback line side (remote) LPOM Lower Order Path Monitoring LPT Lower order path termination or Loopback equipment side LSUT Lower order Supervisory Unequipped Termination LSX LAN Switch LX160 LO Centerstage Matrix 160GBIT/S MAC Media Access Controller MCC Metro Core Connect MCF Message Communication Function



October 2012

MHDLC Multi HighLevel Data Link Controller MLM Multi Longitudinal mode MMF Multimode Fiber MPLS Multi Protocol Label Switching MS Multiplex Section MSA Multiplex section adaptation MSOH Multiplex Section OverHead MSP Multiplex Section Protection MSSPRING Multiplex Section Shared Protection Ring MST Multiplex Section Termination MX640 Matrix Board 640GBIT/S MX320 Matrix Board 320GBIT/S MX160 Matrix Board 160GBIT/S NAD Network Access Domain NCA Network Control Adapter NCI NE Control Interface NE Network Element NGTRU New Generation Top Rack Unit NM Network Management NMI Network Management Interface NMS Network Management System NNI Network to Network Interface NP Network Processor (Restoration Manager 1354NP) NPE Network Protection Element NPOS Network Protection Operating System NRZ No return to zero NURG Not Urgent alarm OBPS On Board Power Supply ODF Optical Distribution Frame OED Optical Edge Device OFA Optical Fiber Amplifier OH OverHead OHBUS Dedicated housekeeping stream OIF Optical Internetworking Forum OMSG Optical Multiservice Gateway and CrossConnect OMSN Optical Multiservice Node OOF Out Of Frame ORALIM ORing of station power supply alarm OS Operation System OSI Open Systems Interconnection OTH Optical Transport Hierarchy OTN Optical Transport Network OUNI Optical UserNetwork Interface OUT Output PC Personal Computer PCB Printed Circuit Board PCI Peripheral Component Interconnect PDH Plesiochronous Digital Hierarchy PFAIL Power supply failure PI Physical interface PJE Pointer Justification Event P/N Part Number



October 2012

POH Path Overhead PPI Plesiochronous Physical interface ppm parts per million PPS Path Protection Switching PWALM Power supply alarm Q2/QB2 TMN interface with B2 protocol; interface towards PDH equip. Q3/QB3 TMN Interface with B3 protocol; interface towards TMN RA Rack Alarm RAI Remote Alarm Indication RAM Random Access Memory RCK Received clock RDI Remote Defect Indication REI Remote Error Indication REL Release RL Rack Lamp RMS Root Mean Square RNURG Not urgent Alarm command. Lights up the relative rack red LED RS Regenerator Section RSOH Regenerator Section OverHead RST Regenerator Section Termination RURG Urgent Alarm command. Lights up the relative rack red LED S Short Haul SBR Source Based Restoration SC Shelf Controller SC Type of optical connector SDH Synchronous Digital Hierarchy SEC SDH Equipment Clock SEMF Synchronous Equipment Management Function SETG Synchronous Equipment Timing Generation SETS Synchronous Equipment Timing Source SFF Small Form Factor (not plugable) SFP Small Form Plugable SNCP Subnetwork Connection Protection SOH Section OverHead SONET Synchronous Optical Network S/P Serial/Parallel Converter SPC Soft Permanent Connection SPI Synchronous Physical Interface SQ Squelch SSF Server Signal Fail SSM Synchronization Status Message SSU System Startup and Supervision STM Synchronous Transport Module SW Software TANC Remote alarm due to failure of all power supply units TMN Telecommunication Management Network TOR Remote alarm indicating loss of one of the station batteries TORC Remote alarm due to a faulty/missing power supply unit TRIB Tributary TSD Trail Signal Degrade TSF Trail Signal Fail TTF Transport Terminal Function



October 2012

TX Transmission U Ultra Long Haul UNI User to Network Interface URG Urgent V Very Long Haul VCG Virtual Concatenation Group VCXO/VCO Voltage controlled oscillator VCx Virtual Container VECE Virtual Equipment Control Element VLAN Virtual LAN VMMF Virtual Machine Management Function WAN Wide Access Network WEEE Waste of Electrical and Electronic Equipment XFP 10 Gigabit Small Form Factor Pluggable Module XFPE XFP Extended



October 2012

3 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 Key functionalities introduced with R4.3.1: - 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)



October 2012

- 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

- DCN - 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. Key functionalities introduced with R4.3.1: - none Key functionalities introduced with R4.3.11: - Serial compound links not supported Key functionalities introduced with R4.3.12: - Serial compound links not supported



October 2012

Key functionalities introduced with R4.3.13: - Serial compound links not supported Key functionalities introduced with R4.3.14: - Serial compound links not supported Key functionalities introduced with R4.3.15: - Colored STM-64 DWDM optical interface - Serial compound links not supported Key functionalities introduced with R4.3.16: - Configurable termination of N1/K3 bytes Key functionalities introduced with R4.3.17: - none Key functionalities introduced with R4.3.18: - none Key functionalities introduced with R4.3.19: - none

Key functionalities introduced with R4.3.20: - 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.

Key functionalities introduced with R4.3.21: - ASON Migration with 1/10GbE - DCN with 95MS & 135 RS DCC channels: condition GMRE not active Key functionalities introduced with R4.3.22: - none Key functionalities introduced with R4.3.23: - 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



October 2012

4 PRODUCT COMPOSITION

4.1 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 3AG24339AA** (restricted use)

Low Order Adaptation LA20 3AG24150AA**

Low Order Adaptation Connection LAC40 3AG24327AA**

Low Order matrix Board LX160 3AG24328AA**

New HW items introduced with R4.2: Alarm Board 3AG24262AA**

2x 10GE LAN Port /XFP 3AG24476AA**

New HW items introduced with R4.3: 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



October 2012

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


- vhm_pr-SKY55-40N.ppc.rpm

R4.3.1 RP4 installation: update based on R4.3.1, no traffic impact. 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


- 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



October 2012

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


- G4fw_pr-SKY55-42A.ppc.rpm - BoardMgtProc-SKY55-42A.ppc.rpm


- 78mcc_pr-SKY55-43C.ppc.rpm


- 78mcc_pr-SKY55-43H.ppc.rpm

R4.3.12 RP3 installation: update based on R4.3.12, no traffic impact. 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


- 78mcc_pr-SKY55-43F.ppc.rpm


- 78mcc_pr-SKY55-43J.ppc.rpm - vhm_pr-SKY55-43J.ppc.rpm

R4.3.13 RP2 installation: update based on R4.3.13, no traffic impact. 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



October 2012

- 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 - 78mcc_pr-SKY55-45F.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.13 RP4 installation: update based on R4.3.13, no traffic impact.

R4.3.20 RP1:

- GMRE_LGAdapt_ION75-15D.ppc.rpm - vhm_pr-SKY55-62A.ppc.rpm - mibIM2-SKY55-62A.ppc.rpm


- 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,

-> Installation of 1678MCC R4.3.23 RP2: 3AG 26549 AAAA PCZZA Ed.01 - 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.



October 2012

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,

-> Installation of 1678MCC R4.3.23 RP3: 3AG 26550 AAAA PCZZA Ed.01

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 INSTALLATION PROCEDURE

5.1 New installation

All software delivery items will be installed via a CD-ROM drive connected to the Craft Terminal (CT). The detailed description how this release has to be installed, can be found in Installation and Start-Up Manual FLC Software and in CT Basic Operator's Handbook Chapter Installation Procedure.

5.2 In service update / upgrade

The R4.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.



October 2012

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

FROM ISUSKY55-40B ISUSKY55-40B ISUSKY55-40B ISUSKY55-40E ISUSKY55-40F ISUSKY55-40F ISUSKY55-41A ISUSKY55-41A ISUSKY55-43A ISUSKY55-43A ISUSKY55-43A ISUSKY55-62B ISUSKY55-63C ISUSKY55-63C

3.2.3supported w/o

GMREnot planned not planned

supported w/o

GMRE; rel. under

PLM control

supported supported supported supported supported supported supported supported supported supported

3.2.4 supported supported not planned supported supported supported supported supported supported supported supported supported supported supported

3.2.5 supported not planned not planned supported supported supported supported supported supported supported supported supported supported supported

3.2.5+ supported not planned not planned supported supported supported supported supported supported supported supported supported supported supported

3.2.6 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.1supported

ISUSKY55-35Fsupported 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 plannedsupported w/o 10GE

ISUSKY55-35Fnot 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 plannedrel. under PLM

controlnot planned not planned not planned not planned not planned not planned

4.3.1 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

4.3.11 not planned SW Update SW Update SW Update SW Update SW Update SW Update SW Update SW Update SW Update SW Update SW Update

4.3.12 SW Update SW Update SW Update SW Update SW Update SW Update SW Update SW Update SW Update SW Update SW Update

4.3.13 SW Update SW Update SW Update SW Update SW Update SW Update SW Update SW Update SW Update SW Update

4.3.14 SW Update SW Update SW Update SW Update SW Update SW Update SW Update SW Update SW Update

4.3.15 SW Update SW Update SW Update SW Update SW Update SW Update SW Update SW Update

4.3.16 SW Update SW Update SW Update SW Update SW Update SW Update SW Update

4.3.17 SW Update SW Update SW Update SW Update SW Update SW Update

4.3.18 SW Update SW Update SW Update SW Update SW Update

4.3.19 SW Update SW Update SW Update SW Update

4.3.20 SW Update SW Update SW Update

4.3.21 SW Update SW Update

4.3.22 SW Update

4.3.23

4.3.2A (CI)

should work, to be verified by local team

Table 1: In-Service Upgrades to R4.3.x



October 2012

6 SOLVED PROBLEMS/RESTRICTIONS/WARNINGS

6.1 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. Workaround for previous releases: 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.



October 2012

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 Solved problems with workaround DDTs SLSks37229 On lower order termination point (TU12) PM before matrix does not count FEBBE as long as only Far End is activated. Workaround for previous releases: 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 Solved specific system behaviours DDTs SLSks44782 To put LA20 boards in/out of service a special documented procedure must be followed



October 2012

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 Solved problems with workaround DDTs SLSks44019 Installation of Core and SKY packages may failed on install server PCs using Windows-XP with the Microsoft update (KB923191). Workaround for previous releases: 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 Workaround for previous releases: Correct on lower level via CLI DDTs SLSks44701 In very rare cases there is an unexpected toggling LAN failure alarm on both matrix copies. Workaround for previous releases: 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. Workaround for previous releases: As precaution use an appropriate filter for searching.



October 2012

DDTs SLSks46852 PM/GbE: configuring multiple PM-TPs on GbE using clipboard functionality can cause a crash on the emlim. Workaround for previous releases: 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. Workaround for previous releases: Use CT to perform a manual switch. 6.3.3 Solved restrictions and warnings 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 Solved specific system behaviours 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.



October 2012

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 Solved problems with workaround 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 Solved restrictions and warnings 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.



October 2012


Note: This RP fix is not cumulative, ie. does fix specifically the deficiencies as listed in this section. 6.6.1 Solved functional restrictions and warnings 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.


Note: This RP fix is not cumulative, ie. does fix specifically the deficiencies as listed in this section. 6.7.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. 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.


Note: This RP fix is not cumulative, ie. does fix specifically the deficiencies as listed in this section. 6.8.1 Solved functional restrictions and warnings 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 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. 6.9.2 Solved functional restrictions and warnings 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.



October 2012


6.10.1 Solved functional restrictions and warnings DDTs SLSks53019 Paths should not be torn down if there is a control plane failure (RSVP Hello dead) during neighbor resynchronization. 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. 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 Solved specific system behaviours 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 Solved functional restrictions and warnings 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 Solved specific system behaviours 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.



October 2012

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.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 Solved problems with workaround 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. Workaround for previous releases: The problem can be cleared by re-initialization of the board, i.e. reset or plugout/plugin once more. 6.12.3 Solved functional restrictions and warnings 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 Solved specific system behaviours 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 Solved functional restrictions and warnings DDTs SLSks53236 LO-Shelf: After laser shut down on LAC40, no alarm is reported for linked port on LA20.


Note: This RP fix is not cumulative, ie. does fix specifically the deficiencies as listed in this section.



October 2012

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 Solved functional restrictions and warnings 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.


This RP includes the fixes of R4.3.12 RP2, and additionally the fixes listed in this section. 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 Solved problems with workaround 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 Solved functional restrictions and warnings DDTs SLSks52488 Transparency of N1/K3 bytes is suspended for use of Internal Tandem Connection Monitoring (ITC). ITC is enabled on the whole node per default. This influences end-to-end usage of N1 / K3 bytes, e.g. external TCM. DDTs SLSks54423 In exceptional cases, an MS-SPRing switch might be delayed after fibre cut due to a simul-taneous matrix switch and traffic is interrupted in the range of 2-3digit seconds.



October 2012


6.16.1 Solved problems with workaround 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

Laser off/on Port(s) executed

1 1

2 1 & 2

3 1 & 3

4 1 & 4

5 2 & 5

6 2 & 6

7 2 & 7

8 2 & 8

9 3 & 9

10 3 & 10

11 3 & 11

12 3 & 12

13 4 & 13

14 4 & 14

15 4 & 15

16 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 Solved functional restrictions and warnings 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.



October 2012


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 Solved functional restrictions and warnings 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 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. 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 Solved specific system behaviours 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 Solved problems/restrictions/warnings in R4.3.13 RP1

6.18.1 Solved functional restrictions and warnings 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.



October 2012


This RP includes the fixes of R4.3.13 RP1, and additionally the fixes listed in this section. 6.19.1 Solved problems DDTs SLSks54199 LO shelf: Due to a potential MX-internal routing problem, existing traffic might be affected in rare cases during implementing new LO cross-connections. DDTs SLSks54264 In very rare cases protection channels of MS-SPRing might be wrongly squelched in case of a fibre cut. 6.19.2 Solved problems with workaround 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.19.3 Solved functional restrictions and warnings DDTs SLSks54423 In exceptional cases, an MS-SPRing switch might be delayed after fibre cut due to a simul-taneous matrix switch and traffic is interrupted in the range of 2-3digit seconds.


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 Solved problems with workaround 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.



October 2012

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.



1 1

2 1 & 2

3 1 & 3

4 1 & 4

5 2 & 5

6 2 & 6

7 2 & 7

8 2 & 8

9 3 & 9

10 3 & 10

11 3 & 11

12 3 & 12

13 4 & 13

14 4 & 14

15 4 & 15

16 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.20.3 Solved functional restrictions and warnings 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. 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 LO shelf: Due to a potential MX-internal routing problem, existing traffic might be affected in rare cases during implementing new LO cross-connections. DDTs SLSks54264 In very rare cases protection channels of MS-SPRing might be wrongly squelched in case of a fibre cut.



October 2012

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 Solved problems with workaround DDTs SLSks53780 If more than 64 MSP groups are configured in main shelf, ghost CPE alarms might be reported permanently or temporarily. Workaround for previous releases: perform a warm reset of active matrix. DDTs 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 Solved functional restrictions and warnings DDTs SLSks52488 Transparency of N1/K3 bytes is suspended for use of Internal Tandem Connection Monitoring (ITC). ITC is enabled on the whole node per default. This influences end-to-end usage of N1 / K3 bytes, e.g. external TCM. DDTS SLSks53470 OED62: In marginal conditions of some SYNTH16 cards (3AL98038AC**/AD**) bit errors may occur of less than 5 ES/SES within 2-48 hours DDTs SLSks54423 In exceptional cases, an MS-SPRing switch might be delayed after fibre cut due to a simul-taneous matrix switch and traffic is interrupted in the range of 2-3digit seconds. 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 Solved problems with workaround 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.



October 2012

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



1 1

2 1 & 2

3 1 & 3

4 1 & 4

5 2 & 5

6 2 & 6

7 2 & 7

8 2 & 8

9 3 & 9

10 3 & 10

11 3 & 11

12 3 & 12

13 4 & 13

14 4 & 14

15 4 & 15

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



October 2012

6.22.3 Solved functional restrictions and warnings DDTs SLSks50244 OED70: A HW problem is discovered on port board 3AL80948AAAA 01, where each GTLP is connected via two ingress to ISPB instead of one. Due to this problem access to ISPB might fail. If more than 12 boards are inserted RUP alarm will appear on standby HO-SMX after download or EPS. Workaround for previous releases: Only a limited number of P16OS1 boards (3AL80948AAAA 01) per shelf prevents the problem. Because each of them needs to be counted like two: - in single configuration of P16OS1 only 8 boards should be configured per shelf instead of 16 and - in mixed configuration one P16OS1 of this special type has to be counted like two usual IO boards. DDTs SLSks54333 LO-shelf: When force command for MSP between LAC40 and LA20 is released on LAC40, the traffic is affected for 10 seconds after WTR. DDTs SLSks54388 In rare cases alarm time stamps of clearing time could be reported earlier than appearing time DDTs SLSks54588 PM records with elapsed time not equal to interval time are not archived on NM. DDTs SLSks54615 Reversion by bridge and roll to nominal route fails if signal degrade is on current route


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 termi-nation 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.



October 2012

6.23.2 Solved problems with workaround DDTs SLSks43793 If the module configuration is changed from STM4 to STM1, sometimes a LOF alarm is reported and it is not possible to establish the transmission. Workaround for previous releases: Remove all connections and STM-1 configuration of affected group and re-configure it to STM-4. Remove the STM-4 configurations again and re-provision STM-1 modules to start new commissioning. 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 Solved functional restrictions and warnings 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 Solved specific system behaviours DDTs SLSks42066 In case one IO board cannot be reached via ISPB bus, a RUP alarm is reported and the related board is periodically cold started as internal repair action. During internal cold start traffic of this board is impacted. DDTs SLSks54620 Manual reversion is prevented due to pending SF on a port of nominal route. DDTs SLSks54886 Loosing the SDH signal, the laser of the GBE port on client side might remain switched-on due to auto-negotiation. For this case, the GBE traffic will be impacted until the SDH circuit is restored.


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



October 2012


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 Solved problems with workaround DDTs SLSks47016 Initialization of P16S16, P16S1 and P16S1-4 boards will fail if terminal loopbacks are configured on ports 9 to 12. This happens after cold start of system, insertion of boards or during ISU. Workaround for previous releases: Release terminal loopbacks after usage. 6.25.3 Solved functional restrictions and warnings 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 Solved specific system behaviours 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.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.



October 2012

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 Solved problems with workaround 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 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 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.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.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.



October 2012


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

3AG24101BDAAFMZZA_V1_1678 MCC Release 04.03.x Product Release Note

Documents

Transcript of 3AG24101BDAAFMZZA_V1_1678 MCC Release 04.03.x Product Release Note