1660SM Release Notes.pdf

RELEASE NOTE t n t e c o u s n i L h s t t f n l e o e t t a g n c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m s t a m u a P o n . c e d d t t e n i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i m d r e p

CONFIDENTIAL TABLE OF CONTENT PHYSICAL RESOURCES...................... RESOURCES ...................... ...................... ...................... ...................... ............... 8 1.1.

Interfaces ...................... .................. ......................... ................... ......................... 8

1.2. Access Modules ...................... ...................... ...................... ...................... .......... 11 2.

LIST OF FEATURES.................. ...................... ...................... ...................... ............. 13 2.1.

EQUIPMENT........................... ...................... ...................... ...................... .......... 13

2.1.1. Automatic Laser Laser Shutdown..... ...................... ...................... ...................... ....... 13 2.1.2.

I/O Loop–back commands. ...................... ...................... ...................... .......... 13

2.1.3. VCi Loop–back Loop–back connections ...................... ...................... ...................... .......... 14 2.1.4.

MS Signal Degrade w/threshold selection......................... selection... ...................... ...................... .......... 14

2.1.5. VC Signal Degrade Degrade w/threshold w/threshold selection ...................... ...................... ............. 14 2.1.6.

I/O Housekeepings and Remote alarms ..................... ...................... ................ 14

2.1.7.

Programmable Programmable Alarm Severity ...................... ...................... ...................... ....... 15

2.1.8.

LAN Access for Managemen Managementt ................ ......................... ................. ................ ................. ................. ................ ................ ........ 15

2.1.9. AUX/EOW channels channels access....................... access. ...................... ...................... ...................... .......... 15 2.1.10. EOW channels extension .................... ...................... ..................... ................. 16 2.1.11. On-line BUS diagnostic ...................... ...................... ..................... ................. 16 2.1.12. ASAP configuration configuration on port and NE basis ...................... ...................... ............. 17

13 12 1

2.1.13. Enhanced FAN Unit Management.................................... ...................... .......... 17 I. Piffari M.Severi / G. Grassi Fixed bug [15]: ID bug 30/01/08 was wrong in Ed.12 E. Colizzi G. C. Caprioli I. Piffari M.Severi / G. Grassi 22/01/08 E. Colizzi G. C. Caprioli S. Schiavoni M. Severi 23/3/2005 M.Colombo G.C Caprioli

ED

DATE

CHANGE NOTE

APPRAISAL AUTHORITY

ORIGINATOR

1660SM rel. 5.2B11 (NE SW Ver. 5.7.71) Release Note

ED

10

CONFIDENTIAL 3AL 365080000 SAD

1/56

2.1.14. CONGI Power ALARM management.......................... ..................... ................. 17 t n t e c o u s n i L h s t t f n l e o e t t a g n c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m s t a m u a P o n . c e d d t t e n i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i m d r e p

2.2.

EQUIPMENT PROTECTION...................... ...................... ..................... ................. 18

2.3.

MANAGEMENT MANAGEMENT ............... ........................ .................. ................ ................ ................. ................ ................. ................. ................ ................ ........ 19

2.3.1. ANTP – time synchronization synchronization protocol protocol ..................... .................. ...................... . 20 2.3.2.

IP OVER OSI TUNNELING FOR ATM/IP............... ......................... ................... . 20

2.3.3.

OSI over IP tunneling on QB3 ...................... ...................... ...................... ....... 20

2.3.4.

SW bootstrap from Craft Terminal ...................... ................... ...................... .... 20

2.3.5.

SW download....................... ...................... ...................... ...................... ....... 20

2.3.6.

Performance Monitoring Management .................... ..................... ................... . 20

2.3.7.

2Mb/s PDH POM on on incoming incoming and and outgoing outgoing signal ...................... ................... . 22

2.3.8.

HO & LO POM - PATH OVERHEAD MONITORING MONITORING (*).......................... ............. 22

2.3.9.

PM on VC-n POM POM unidirectional unidirectional for segment monitoring monitoring (Near-End primitives) primitives) .... 22

2.3.10. PM on VC-n POM unidirectional & bi-directional for end-to-end monitoring (Far-End primitives)......................... primitives)... ...................... ..................... ................... ....................... 22 2.3.11. PM on 2Mb/s ISDN PRA ................ ......................... .................. ................ ................ .................. ................ ................ ............... ...... 23 2.3.12. Unidirectional and bi-directional PM on 2Mbit/s PDH POM for end-to-end and segment monitoring........................ monitoring.. ...................... ...................... .................. ....................... 23 2.3.13. HO & LO TCT/TCM TCT/TCM - Tandem Connection Connection Termination Termination & Monitoring Monitoring (*) ............. 23 2.3.14. Unidirectional/Bidirectional Perform. Mon. on HO & LO TCT/TCM for maintenance (*) .................... ...................... ...................... ...................... ....... 23 2.3.15. Remote Inventory .................. ...................... ...................... ...................... ....... 23 2.3.16. Operating functionalities – Configuration Configuration ...................... ...................... ............. 23 2.3.17. UAT – Unavailable Unavailable Time Alarm .................... ...................... ...................... ....... 23 2.3.18. UPA – Unavailable Unavailable Path Alarm (SSF) ................ ...................... ...................... .... 23 2.3.19. TCA – PM Threshold Crossing Alarm ..................... ................... ...................... . 23 2.3.20. Network Termination functionality on 2Mb/s 2Mb/s ISDN–PRA ..................... ................ 24 2.3.21. Access Control Domain Domain on CT CT ..................... ...................... ...................... ....... 24 2.3.22. Alarm flooding flooding control (EFD).. (EFD)........................ ...................... ...................... ...................... ....... 24

ED

10


2/56

2.3.23. Performance monitoring retrieval with simple scanner ................... ................... . 24 2.3.24. ETHERNET PERFORMANCE COUNTERS........................... COUNTERS..... ...................... ...................... .......... 24

t n t e c o u s n i L h s t t f n l e o e t t a g n c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m s t a m u a P o n . c e d d t t e n i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i m d r e p

2.3.25. AUTO MON status status on SDH and PDH ports....................... ...................... .......... 25 2.3.26. PERFORM. MONIT. ON AU3 POM .................. ...................... ...................... .... 26 2.4.

NETWORK NETWORK ................. ......................... ................. ................. ................ ................. ................ ................ .................. ................ ................ .............. ..... 26

2.4.1. VCi Signal Label Label Management ..................... ...................... ...................... ....... 26 2.4.2.

J1 - PATH TRACE Management .................... ...................... ...................... ....... 26

2.4.3.

J2 – PATH TRACE Management.............................. .................. ...................... . 27

2.4.4.

J1 –J2 HEX Management.......... ...................... ...................... ...................... .... 27

2.4.5.

J0 – SECTION TRACE management........................... ..................... ................. 27

2.4.6.

J0 – HEX Management .................... ..................... ................... ...................... . 27

2.4.7.

OH Bytes Access and Re–routing Management .................... ...................... ....... 27

2.4.8.

BWSF – Bidirectional working on single fiber..................... fiber..................... ...................... .......... 27

2.4.9. ATM TRANSPORT Management....................... Management....................... ...................... ...................... .... 27 2.4.10. AIS on PDH ports ports .................. ...................... ...................... ...................... ....... 28 2.4.11. ISA Ethernet main board........................ ...................... ...................... ............. 28 2.4.12. ISA Ethernet access board................ ..................... ................... ....................... 28 2.4.13. ISA-Gb Ethernet rate adaptive access module ...................... ...................... ....... 28 2.4.14. ISA GbEthernet rate adaptive main board ..................... ...................... ............. 29 2.4.15. LCAS functionality functionality on ISA GbEthernet rate adaptive adaptive................. ................. ...................... .... 29 2.4.16. ISA-PR Edge Aggregator unit..................... unit ..................... ...................... ...................... .......... 29 2.4.17. 4xSTM-4 4xSTM-4 port ................ ......................... ................. ................ ................. ................ ................ .................. ................ ................ .............. ..... 30 2.4.18. 16xSTM-1/ 4xSTM-4 optical port ........................ ................... ...................... .... 30 2.4.19. 12xSTM-1 12xSTM-1 optical optical access access ................ ......................... .................. ................ ................ .................. ................ ................ .............. ..... 31 2.4.20. 16xSTM-1 16xSTM-1 electrica electricall access ................ ......................... ................. ................ ................. ................. ................ ................. ........... .. 31 2.4.21. ISA-PR Matrix........................... ...................... ...................... ...................... .... 31 2.4.22. ISA PR 16xETH 10/100 access module.......... ...................... ...................... ....... 32

ED

10


3/56

2.4.23. ISA PR 2xGbE access module .................... ...................... ...................... .......... 32 2.4.24. ISA ES-1 ................ ......................... .................. ................ ................ ................. ................ ................. ................. ................ ................. ............ ... 32

t n t e c o u s n i L h s t t f n l e o e t t a g n c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m s t a m u a P o n . c e d d t t e n i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i m d r e p

2.4.25. ISA ES-4 ................ ......................... .................. ................ ................ ................. ................ ................. ................. ................ ................. ............ ... 33 2.4.26. ISA ES-16....................... ...................... ...................... ...................... ............. 33 2.4.27. 4 X ANY UNIT ............... ........................ ................. ................ ................. ................ ................ .................. ................ ................ .............. ..... 34 2.4.28. Double Multi-rate Transponder Unit.............. ...................... ...................... ....... 35 2.4.29. OADM & MUX/DEMUX MODULES .................. ...................... ...................... .... 36 2.4.30. 4 X OC3 with with AU3/TU3 conversion conversion optical unit.................... unit.................... ...................... ....... 36 2.5.

NETWORK NETWORK PROTECTI PROTECTION ON ................. ......................... ................. ................ ................ .................. ................ ................ .................. ......... 38

2.5.1.

STM–N linear single–ended 1+1 APS ..................... .................. ...................... . 38

2.5.2.

STM–N linear dual–ended 1+1 APS ................ ...................... ...................... .... 38

2.5.3.

STM-1 linear dual-ended 1:N APS ................... ...................... ...................... .... 38

2.5.4.

STM-4 linear dual-ended 1:N APS ................... ...................... ...................... .... 38

2.5.5.

SNCP/I among VCi trails (i=12,3,4) ................ ...................... ...................... .... 39

2.5.6.

SNCP/N among VCi trails (i=12,3,4) (*) .................... ..................... ................. 40

2.5.7.

Hold-Off times times for protection independency in SNCP............................... .......... 40

2.5.8.

Drop & Continue + Insertion SNCP ................. ...................... ...................... .... 40

2.5.9.

2F MS–SPRING at STM16 intefaces......... ...................... ...................... ............. 41

2.5.10. 2F MS–SPRING at STM64 interfaces....................... ................... ...................... . 41 2.5.11. D&C + Insertion on MS–SPRING protection (RIW) ................... ...................... .... 42 2.5.12. Collapsed single–node ring interconnection............................ ...................... .... 42 2.5.13. Collapsed dual–node ring interconnection................................. ...................... . 42 2.5.14. AU/TU independent independent allocation SNCP..................... SNCP ..................... ................... ...................... . 42 2.5.15. STS–3c pointer pointer management management (SS bits configuration).............................. configuration).............................. ............. 43 2.6.

CONNECTIVI CONNECTIVITY TY ................ ......................... ................. ................ ................. ................ ................ .................. ................ ................ ............... ...... 43

2.6.1. AU4–4c among STM–N interfaces interfaces (n>=4) .................... ...................... ............. 44 2.6.2. AU4-16c among STM-N interfaces interfaces (n>=16) .................... ...................... .......... 44

ED

10


4/56

Feature available available only with with Slim STM-16 STM-16 port and STM-64 port....... ...................... .......... 44 t n t e c o u s n i L h s t t f n l e o e t t a g n c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m s t a m u a P o n . c e d d t t e n i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i m d r e p

2.6.3.

Packet Concatenation on LO VCi (i=12,3) for E/FE traffic on ISA Ethernet main board and ISA Packet Ring Edge Aggregator .................... ...................... .......... 44

2.6.4.

Idle – Active management on virtually concatenated VC-4 of ISA GbE main board...................... board ...................... .................. ......................... ................... ....................... 45

2.7.

TIMING TIMING .................. ......................... ................ ................. ................ ................. ................ ................ .................. ................ ................ ................. .......... 45

2.7.1. ADM with SSU ...................... ...................... ...................... ...................... ....... 46 2.7.2. 2.8.

RETIMING ON THE 2Mb/s Interfaces (*).............................. (*)........ ...................... ...................... ....... 50

SUPPORT MANAGEMENT........................ ...................... ...................... ................ 50

2.8.1.

Event reporting management .................... ...................... ...................... .......... 50

2.8.2.

Event logging management ...................... ...................... ...................... .......... 51

2.8.3. Alarm management management ................. ...................... ...................... ...................... .... 51 2.8.4. Alarm summary, summary, alarm synthesis synthesis and abnormal abnormal condition condition synthesis .................... 51 2.9.

SECURITY MANAGEMENT .................... ..................... ................... ...................... . 51

2.10. ENVIRONMENTAL CONDITIONS................ CONDITIONS...................................... ...................... ...................... ............. 51 2.11. RELEASE RELEASE 5.2B11: 5.2B11: BUG LIST ................ ......................... .................. ................ ................ .................. ................ ................ ............... ...... 52 2.12. RELEASE 5.2B11: FIXED BUGS .................... ...................... ...................... ............. 52 2.13. RELEASE 5.2B11: RESTRICTION LIST............... ...................... ...................... .......... 53 2.14. RELEASE 5.2B11: RESTRICTIONS REMOVED....................... ...................... ............. 54 2.15. RELEASE 5.2B11: PROCEDURES TO BE BE FOLLOWED FOLLOWED & WARNINGS .................. ....... 54

ED

10


5/56

t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

LIST OF FIGURES AND TABLES Figure 1 On-line bus diagnostic.........................................................................................16 Figure 2 Power blocks and monitoring points on CONGI ..................................................... 17 Figure 3 Aggregate Ethernet counters.................................................................................25 Figure 4 Termination point monitoring state ........................................................................ 25 Figure 5 16xSTM-1/4xSTM-4 and access modules combination ............................................30 Figure 6 Client signals allocation (drawers configuration) in Enhanced slots ........................... 34 Figure 7 Client signals allocation (drawers configuration) in H.S slots........................... .......... 35 Figure 8 AU3/TU3 conversion structure .............................................................................. 37 Figure 9 HO and LO Drop & Continue protected + insert. ................................................... 41 Figure 10 ADM with SSU...................................................................................................46 Figure 11 Automatic DNU generation (SSM supported). ....................................................... 48 Figure 12 Removal of Automatic DNU generation................................................................48 Figure 13 Automatic DNU generation (SSM not supported)...................................................49 Figure 14 Removal of Automatic DNU Generation (SSM not supported) ................................. 50

Table 1 Loop back ............................................ ...............................................................13 Table 2 AUX/EOW ...........................................................................................................15 Table 3 EPS Commands....................................................................................................18 Table 4 EPS schemes ........................................................................................................ 19 Table 5 ISA PR Matrix slot positions .................................................................................... 32 Table 6 High Order/Low Order connectivity for 1660SM......................................................43 Table 7 Synchronization Equipment Timing Source .............................................................. 46

ED

10


6/56


HISTORY 01 <1660SM Rel 5.2B Product release note> 23/03/05 02 <1660SM Rel 5.2B1 Product release note> 08/07/05 03 <1660SM Rel 5.2B2 Product release note> 22/07/05 04 <1660SM Rel 5.2B3 Product release note> 12/01/06 05 <1660SM Rel 5.2B4 Product release note> 03/03/06 06 <1660SM Rel 5.2B5 Product release note> 21/04/06 07 <1660SM Rel 5.2B6 Product release note> 27/07/06 08 <1660SM Rel 5.2B7 Product release note> 06/09/06 09 <1660SM Rel 5.2B8 Product release note> 15/11/06 10 <1660SM Rel 5.2B9 Product release note> 20/06/07 11 <1660SM Rel. 5.2B10 Product release note> 10/08/07 12 <1660SM Rel. 5.2B11 Product release note> 22/01/08 13 <1660SM Rel. 5.2B11 Product release note> 30/01/08 (Edition 2)

PREFACE This document describes the functionalities of the release 5.2B11 of the 1660SM. The SWP 1660SM R5.2 level B11 is so composed: •

NE V5.7.7 1

•

CT V4.4.16

•

CTK V3.2.0.6J

•

Q3CT-K-ADD-ON V.3.1.3

The tests of CT are performed on Microsoft windows OS XP with SP1 and NT/2000 with SP2 and Java machine 1.3.1.8.

ED

10


7/56

PHYSICAL RESOURCES t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

The following items are managed: •

1660SM shelf

•

EquicoE

•

Flash Card 256 MB

•

Matrix Enhanced

1.1.

Interfaces

Here below all the items managed (at SW level) by this release of 1660SM. •

63x2 Mbit/s PORT

•

3x34/45 Mbit/s PORT

•

63x2 Mbit/s G.703/ISDN–PRA PORT

•

4x140/STM1 SWITCH. O/E PORT /1

•

4xSTM1 Electrical/Optical PORT /1

•

4xSTM1 Electrical PORT /1

•

S–4.1 Optical PORT (FC/PC) /1

•

L–4.1 Optical PORT (FC/PC) /1

•

L–4.2 Optical PORT (FC/PC) /1

•

L–4.2 JE (3200 ps/nm) Optical PORT (FC/PC) /1

•

4XSTM4 PORT (Only 2 STM-4 plug in modules can be hosted)

•

I.16.1

•

S–16.1 PORT (FC/PC) /1

•

L–16.1 PORT (FC/PC) /1

•

L–16.2 PORT (FC/PC) /1

•

L–16.2J1 PORT (FC/PC) /1

•


•


ED

10


8/56


•

S–4.1 Optical PORT (SC/PC) /1

•

L–4.1 Optical PORT (SC/PC) /1

•

L–4.2 Optical PORT (SC/PC) /1

•

L–4.2 JE (3200 ps/nm) Optical PORT (SC/PC) /1

•

S–16.1 PORT (SC/PC) /1

•

L–16.1 PORT (SC/PC) /1

•

L–16.2 PORT (SC/PC) /1

•

L–16.2J1 PORT (SC/PC) /1

•


•


•

L–16.2 PORT Colored Optics (6400 ps/nm) /1

•

L–16.2 PORT Colored Optics (12800 ps/nm) /1

•

S-16.1 PORT (FC/PC) /16C

•

L-16.1 PORT (FC/PC) /16C

•

L-16.2 PORT (FC/PC) /16C

•

L-16.2J1 PORT (FC/PC) /16C

•


•


•

S-16.1 PORT (SC/PC) /16C

•

L-16.1 PORT (SC/PC) /16C

•

L-16.2 PORT (SC/PC) /16C

•

L-16.2J1 PORT (SC/PC) /16C

•


•


•

L-16.2 PORT Colored Optics (6400 ps/nm) /16C

•

L-16.2 PORT Colored Optics (12800 ps/nm) /16C

•

STM-16 Host SFP- 2 slots wide- (SFP plug in modules must be inserted)

ED

10


9/56


•

STM64 PORT S-64.2E

•

STM 64 PORT ENH I-64.1E

•

STM 64 PORT L-64.2b (Require booster +10dbm)

•

STM16 SLIM PORT UP/SFP – 1 slot wide- (SFP plug in modules must be inserted)

•

OMSN Booster +10dbm FC/PC

•

OMSN Booster +10dbm SC/PC

•


•


•


•


•

ISA-ATM board 4x4

•

ISA-ATM board 8x8

•

ISA-Ethernet main board

•

ISA Gb-Ethernet main board rate adaptive

•

ISA Gb-Ethernet main board rate adaptive: 3AL80702AB**

•

ISA Packet Ring Edge Aggregator 4xEthernet 10/100

•

ISA Packet Ring Edge Aggregator 1xGbEthernet

•

ISA Packet Ring Matrix

•

4 X OC3 with AU3/TU3 conversion optical unit

•

4xANY unit

•

ISA ATM 4x4 Enhanced

•

ISA ES-1 8FE and ISA ES-1 8FX

•

ISA ES-1 New version (3AL98128AB**)

•

ISA ES-4

•

ISA ATM 4x4 D3

•

ISA ES-16

•

16xSTM-1/4xSTM-4 port SFP (SFP plugin modules needed)

ED

10


10/56


•

Double channel multi-rate transponder (SFP plugin modules needed)

•

STM-64 L64.2c

N.B.

”/1” new items mounting ASIC CRISTALLO Ver. 3.0C. (type N) ”/16C” new item with CRISTALLO Ver. 3.0D (type ND)

Old HW items not /1 or not /16c are not managed by this SW release.

1.2.

Access Modules

•

4*STM1 Electrical Module

•

2*140/STM1 Electrical/Optical module

•

140/155 Electrical Interface Plug–in

•

STM-1 Multimode Optical Interface Plug–In

•

S–1.1 Optical Interface Plug–In (FC/PC)

•

L–1.1 Optical Interface Plug–In (FC/PC)

•

L–1.2 Optical Interface Plug–In (FC/PC)

•

L–1.2JE Optical Interface Plug–In (FC/PC)

•

S–1.1 Optical Interface Plug–In (SC/PC)

•

L–1.1 Optical Interface Plug–In (SC/PC)

•

L–1.2 Optical Interface Plug–In (SC/PC)

•

L–1.2JE Optical Interface Plug–In (SC/PC)

•

21x2 Mbit/s connection module 120 Ohm

•

21x2 Mbit/s connection module 120 Ohm K20

•

21x2 Mbit/s connection module 75 Ohm 1.0/2.3

•


•


•

Control and Power Module (CONGI)

•

Control and Power Module XT(CONGI XT)

•

Control and Power Module Enhanced

•

ED

AUX & Synch Access Module (SERVICE)

10


11/56


•

Optical Preamplifier unit for 2.5Gb/s interface

•

ISA-Ethernet access board

•

ISA Gb-Ethernet rate adaptive access module

•

ISA Gb-Ethernet rate adaptive access module 3AL80411AB**

•

ISA PR 16xETH 10/100 access module

•

ISA PR 2xGbE access module

•

SFP Optical modules TRX S-16.1 plug in

•

SFP Optical modules TRX L-16.1 plug in

•

SFP Optical modules TRX L-16.2 plug in

•

SFP optical module 1000BASE-LX (LH)

•

SFP optical module 1000BASE-SX

•

SFP optical module 1000BASE-ZX

•

SFP optical module S-1.1

•

SFP optical module L-1.1

•


•

SFP optical module S-4.1

•


•


SFP optical modules CWDM (1470nm, 1490nm, 1510nm, 1530nm, 1550nm, 1570nm, 1590nm, 1610nm) •

•

12xSTM-1 optical access SFP (SFP plugin modules needed)

•

12xSTM-1 SLIM optical access SFP (SFP plugin modules needed) : already managed since 1

5.2B1)

1

This access module can be equipped only in the new 1660SM shelf: •

ED

10

3AL89794AAAA 1660SM SUBRACK WITH FANS SHELF


12/56


•

16xSTM-1 electrical access

•

16xSTM-1 el. High Speed Protection card

•

MUX-DEMUX CWDM optical module

•

OADM 1 channel CWDM

•

OADM 2 channels CWDM

Old HW items not/1 or not /16c are not managed by this SW release.

2. LIST OF FEATURES This chapter describes the functionalities of this release of the 1660SM.

2.1.

EQUIPMENT

2.1.1. Automatic Laser Shutdown.

ALS procedure is according to G958 and it is applicable at all STM–N interface types. 2.1.2. I/O Loop–back commands.

The equipment is able to support the internal and line loops at all PDH and SDH interfaces: both payload and overhead information are involved. The commands allow to activate/deactivate on every I/O inter-face the loopback configuration at the ”external side” or at the ”internal side”. The Shelf Controller is in charge to perform the following loopbacks on the ports: •

PDH physical interfaces (2, 34, 45 and 140 Mb)

•

Electrical and Optical STM–N Interfaces

The following table describes the supported loopbacks for 1 660SM: Table 1 Loop back

ED

Port

Type – Line Loop & Continue

STM-64

OK

Access Denied

OK

Access Denied

STM16

OK

Access Denied

OK

Access Denied

STM4

Access Denied

OK

Access Denied

OK

STM1

Access Denied

OK

Access Denied

OK

140Mb

Access Denied

OK

Access Denied

OK

34/45Mb

OK

Access Denied

OK

Access Denied

10

Type – Line Loop& Type – Internal Loop Type – Internal Loop AIS & Continue & AIS


13/56

2Mb t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

Access Denied

OK

Access Denied

OK

2.1.3. VCi Loop–back connections

VCi loopback can be independently provided at every path level by means of the same connection facilities supported on the HO/LO matrices for the payload. Each of this loopback (internal and external) is performed as Unidirectional Cross Connection. 2.1.4. MS Signal Degrade w/threshold selection

Threshold selection capability for the B2 bytes Multiplex Section Signal Degrade (MS SD) detection is possible according both to Poisson Model and Burst Model. 2.1.5. VC Signal Degrade w/threshold selection

Threshold selection capability for the B3 and Bip2 bytes Signal Degrade (SD) detection is possible both according to Poisson and Burst Model. 2.1.6. I/O Housekeepings and Remote alarms

The system, through the CONGI card placed in the Access Area, is able to provide the external connectors (housekeepings, remote alarms, Q2 interface, LAN interface....). The CONGI card has the capability to provide: •

6 HouseKeeping input contacts

•

2 HouseKeeping output contacts

•

5 output remote alarms

If two CONGI are present (CONGI–B equipped), the system is able to provide a double number of contacts (HK In/out and Remote => double capacity). The output remote alarms are typically used to report (to interface rack services or generic station devices) various equipment criteria like: power supply alarms, equipment alarm summary, Equipment Controller and QB3 interconnection status. It is possible to set the severity of the housekeeping inputs. It is possible to name the housekeeping inputs and outputs (16 characters). 2.1.6.1.

Extended Alarm Contacts Management

Output housekeeping contacts can be configured to externally report the line defect status of the STM-N interfaces; each contact can be individually setup for this behavior in alternative to the output housekeeping management.

ED

10


14/56

2.1.6.2. t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

Unit Alarms

Each port card or access card of the equipment is provided with a bicolor LED (green/red) on the front cover plate; this LED indicates: when red, internal failure. when green, in service unit. 2.1.6.3.

Centralized Equipment Alarms

All the alarms detected by the units are collected by the EQUICO. Five LEDs available in the front cover allow synthesizing alarm messages: MAJOR, MINOR, ABN, WARNING, ATTD. 2.1.7. Programmable Alarm Severity

The following classes are available by default: CRITICAL, MAJOR, MINOR, WARNING and NOT ALARMED. The operator is allowed to create his own classes on the basis of its network peculiarities. 2.1.8. LAN Access for Management

The equipment can be connected to a Local Area Network infrastructure for direct interconnection to the TMN systems; this interface provides the physical access to the QB3 communication protocol stack via the IEEE–802.3 standard. In 1660SM 10Base–T or 10Base–2 options supported by the CONGI–A card. 2.1.9. AUX/EOW channels access

SERVICE Unit can provide auxiliary interfaces to terminate the AUX/EOW bytes e xtracted from the SDH overhead according to the following table. Table 2 AUX/EOW

EOW analog access types

AUX digital access types

Q.23 (DTMF) standard phone jack V.11 Synch (Di/Do/Cko, 64 Kb/s) Q.23 (DTMF) phone extensions via V.24 Asynch (Di/Do oversampled, max RJ11 four wires conn. 38 Kb/s) G.703/G.732 synch (co-directional, 2Mb/s structured 31 x 64Kb/s) G.703 synch (co-directional, 64 Kb/s) The following auxiliary terminations are available for 1660SM: 4*V11 (64Kb/s) + 4*RS232 (64Kb/s) + 4*G.703 (64Kb/s) + 2*2Mbit/s G.703–G.732. The following EOW termination (phone interface) is available for 1660SM: Q.23 (DTMF). AUX bytes on 2Mbit/s G.703 port are managed. All the SOH bytes available for AUX/EOW terminations can be managed via ECT in order to support two types of applications: Local Access and X–Connection.

ED

10


15/56

2.1.10. EOW channels extension t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

EOW channels extension allows to extend the EOW telephone channel through the 4-wires RJ-41 connector on Sergi/Service board. Three configurations are supported: 1. EOW extension on a single NE; 2. EOW pass-though between 2 NEs on different SDH transmission network; 3. EOW party-line among multiple NEs. EOW extension on a single NE is accomplished by adopting MSN8 (see WTD Commercial Product Catalog) and getting signal from 4 wire extension on the OMSN (RJ-41 connector). EOW pass-though, between 2 NEs on different SDH transmission network, uses 4 wire extension on the two NEs to let the communication channel pass. EOW party-line among multiple NEs uses MSN8 (see WTD Commercial Product Catalog) to connect all the 4 wire extension on all the equipment. Party line function on the MSN8 allows to make the cross connection for the voice channels. 2.1.11. On-line BUS diagnostic To improve the hardware failure diagnostic and Localization a mechanism named "NGI Monitor" (NGI, New Generation Interface, is the internal signal interface (backplane) for OMSN family). NGI Monitor allows a more detailed monitoring with respect to the current generic "Card Fail" alarm. This mechanism provides information about problems affecting internal links. Figure 1 On-line bus diagnostic shows a functional sketch of what is achievable in terms of alarms, by mean of NGI monitor.

At CT Level (surveillance alarms) the number of slot where the failure occurred is reported.

Figure 1 On-line bus diagnostic

ED

10


16/56

Improvements, self test and fault isolation of ISPB bus has also been introduced by R.5.2B10 onward. t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

2.1.12. ASAP configuration on port and NE basis

The feature has the target to allow the SH/CT user to quickly configure Alarm Severity Alarm Profiles (ASAP) of all the Termination Points (TPs) of a port or a Network Element. For instance a 2Mb/s port has 4 TPs, each of them with an own ASAP: this feature allows the user to change the default ASAP of all the TPs of the board with a single command. The feature allows as well the user to configure all the ASAPs of the TPs of a selected class of ports (2Mb/s, 34Mb/s, …, STM-1, STM-4, …) of a Network Element. 2.1.13. Enhanced FAN Unit Management

This feature provides alarm monitoring to support the fan unit maintenance operations. The fan configuration is always redundant in order to be able keeping the adequate air f low with a single failure condition. This feature is fully exploited only when using new 19” fan unit together with enhanced CONGI3W. 2.1.14. CONGI Power ALARM management

The alarms management regarding the power supply from external battery and on board fuse failure has been improved on CONGI board. The Figure 2 reports the monitoring points present on the CONGI.

BranchA/ B a t. A (4 8 V)

BranchB/ B a t. B (4 8 V)

Super vision

FUSE_FAILURE / BATTERY_FAILURE of CONGI A

C O N G I

C O N G I

Super vision

FUSE_FAILURE / BATTERY_FAILURE of CONGI B

3.6V OBPS

3,6 V

OBPS

48 V

48 V

FUSE FAILURE of NE

3,6 V

Figure 2 Power blocks and monitoring points on CONGI

ED

10


17/56


If the external power supply connected to CONGI (A/B) board is faulty the alarm indication with probableCause FuseFailure is raised at NE level together with the alarm Battery Failure at equipment level on the involved CONGI (A/B). If the fuse inside the CONGI is broken, the alarm indication with probableCause FuseFailure is raised at equipment level on the CONGI which has the fuse broken. If there is a failure affecting On Board Power Supply (OBPS) device providing the 3.6v, the RUP alarm (Card Fail) is declared at equipment level on the affected CONGI.Another alarm is revealed directly by Equipment Controller when the auxiliary power supply at the voltage of 48V is missing, in this case the alarm with probableCause AndBatteryFailure is raised is raised at NE level (this is applicable to CONGI A only).

2.2.

EQUIPMENT PROTECTION

1660SM is able to manage the following cards EPS protection: 

MATRIX card protection: As the synchronization, the matrix and the shelf controller functionalities are on the MATRIX board, the equipment protection of the MATRIX board provides the duplication of all these functions. The CRU, matrix, SC functions and the Gate array present on the MATRIX board are considered in terms of EPS as a single block . Then when a failure occurs for one or more of these, a switch is performed from the main to the spare card.



Low Speed Port Protection: Protection scheme N+1 with fixed position of protecting Low Speed card.



High Speed Port Protection: Protection scheme N+1 for the electrical High Speed ports.



ATM Matrix card protection: See related ATM release note for details.

Switching time: < 50msec Performance on matrix protection is given 15min after power-up.

The following table describes the supported commands by 1660SM: Table 3 EPS Commands

Manual/Release Lockout/Release Forced/Release Matrix EPS

OK

Access Denied

Not Available

Ports EPS

OK

OK

Not Available

The following table describes the supported equipment protection scheme for 1660SM: ED

10


18/56

Table 4 EPS schemes t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

Equipment

− − −

MATRIX board (note 1) LS ports – 63x2 Mbit/s HS ports: 3x34/45 Mbit/s (note 2) 4xSTM1 Elect. 16xSTM-1 electrical

Protection Scheme

Number of protection schemes

Mode

1+1

1

Not Revertive

N+1 (N=1...6)

1

Revertive

N+1 (N=1...15)

1...8

Revertive

(note 1) For each type of fail on the MATRIX main board (matrix, CRU, SC failure) a switch is performed to spare card. (note 2) Max N=4 for 3x34/45 Mb Port. N=15 is achieved using the following access modules: 34 Mbit/s: 3AL78865 AB** and following versions 45 Mbit/s: 3AL78866 AB** and following versions

2.3.

MANAGEMENT

The 1660SM can be managed through different communication interfaces by following described: The system can be managed through the F interface, by a CMISE Craft Terminal running on a Personal Computer (Local Craft Terminal). •

A given Network Element can be configured as a Mediation Network Element in order to manage a network made up of a maximum of 32 SDH elements including the one acting as a MNE (Remote Craft Terminal). By means of the information shared through the embedded DCC channels, it’s possible to perform alarm synthesis and clock/data distribution of the configured managed network. •

The different products of the Alcatel-Lucent Network Management System can be used to supervision the one or more NE’s through the QB3 interface via a dedicated LAN port (ISO–OSI protocol stack on QB3/QECC). •

The QECC interface (D4–D12 or D1–D3 (Sw selectable)) via STM–N input ports allows further connection facility to the NMS (QECC on RS/MS– SOH bytes). •

The system can work as a Mediation Device in order to manage from CT o OS other ALCATEL-LUCENT non SDH Equipment (video, radio, access...) through the Q2/RQ2 interface (Q2–RQ2/LTS Mediation Function). •

A modification into the OSI stack has been introduced to extend the number of octets of the L2 frames received over DCC: from 512 (default value defined into standard G.784) to 1520. This modification allows the interworking with those equipment sending L2 frames over DCC exceeding 512bytes. •

ED

10


19/56

2.3.1. ANTP – time synchronization protocol t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

Feature available. 2.3.2. IP OVER OSI TUNNELING FOR ATM/IP

This feature is applicable to NEs with ISA ATM/PREA/ESx board. It consists in using QB3/QECC channels to carry IP link terminated on ISA board. This SW release supports the modification of “SEL” field of tunnels provisioning. 2.3.3. OSI over IP tunneling on QB3

This feature allows the Element Manager to reach the GNEs (and all the relevant NEs behind them) by using IP networking. This would permit to use an external DCN based on IP only. Hence, no OSI networking would be required on the external DCN. OSI over IP technique is used to meet the target. 2.3.4. SW bootstrap from Craft Terminal

Feature available. 2.3.5. SW download

Two procedure of Software downloading are managed in order to upgrade the NE’s software version: •

Local Software Downloading via ECT (Local SW download)

•

Remote Software Downloading via OS (Remote SW download)

Remote software downloading is also available from Remote ECT. Both local and Remote SW download support compressed (zipped) SW package transfer. 2.3.6. Performance Monitoring Management

The Performance Monitoring Process is performed for two different purposes: •

•

Maintenance (M2120) −

The monitoring is applied on the path or section layer

−

Events are counted (in the available period) by 15 min. and 24H counters

−

Trail is monitored in the two different directions independently

−

It is used a degradation monitoring by threshold crossing

Quality of Service (G826) −

ED

10

The monitoring is applied only on the path layer


20/56


−

Events are counted (in the available period) only by 24H counters

−

Trail is monitored at the same time in the two different directions

−

It is not used a degradation monitoring by threshold crossing

1660SM supports: bidirectional Performance Monitoring function on Trail Termination Points (VCn–TTP, n=12,3,4) with the QoS purpose. •

unidirectional Performance Monitoring function on Trail Termination Points (RS, MS, VCn– TTP, n=12,3,4) with the Maintenance purpose. •

Types of counters: •

Errored Second (ES)

•

Severely Errored Second (SES)

•

Background Block Error (BBE)

•

Unavailable Second (UAS)

Hereafter all kind of counters available for each level are reported: •

•

•

Regenerator Section Termination −

RS-TTP (NE)

STM–N Port RS Section BBE/ES evaluation on 15m and 24H NE

−

RS-TTP (NE)

STM–N Port RS Section SES evaluation on 15m and 24H NE

−

RS-TTP (NE)

STM–N Port RS Section UAT evaluation on 15m and 24H NE

Multiplexer Section Termination −

MS-TTP (NE and FE)

STM–N Port MS Section BBE/ES evaluation on 15m and 24H NE/FE

−

MS-TTP (NE and FE)

STM–N Port MS Section SES evaluation on 15m and 24H NE/ FE

−

MS-TTP (NE and FE)

STM–N Port MS Section UAT evaluation on 15m and 24H NE/ FE

Multiplex Section Adaptation −

•

High Order Path Termination −

ED

AU4-CTP-BidR1 (AU4 PJE)

10

VC4-TTPBidR1 (NE and FE)

STM–N Port VC4TTP BBE/ES evaluation on 15m and 24H NE/FE CONFIDENTIAL 3AL 365080000 SAD

21/56


•

−

VC4-TTPBidR1

STM–N Port VC4TTP BBE/ES evaluation on bidir 24H (Q)

−


STM–N Port VC4TTP SES evaluation on 15m and 24H NE/FE

−

VC4-TTPBidR1

STM–N Port VC4TTP SES evaluation on bidir 24H (Q)

−


STM–N Port VC4TTP UAT evaluation on 15m and 24H NE/FE

−

VC4-TTPBidR1

STM–N Port VC4TTP UAT evaluation on bidir 24H (Q)

Low Order Path Termination −

VCn-TTPBidR1 (NE and FE)

VCn Port BBE/ES evaluation on 15m and 24H NE/FE

−

VCn-TTPBidR1

VCn Port BBE/ES evaluation on bidir 24H (Q)

−


VCn Port SES evaluation on 15m and 24H NE/FE

−

VCn-TTPBidR1

VCn Port SES evaluation on bidir 24H (Q)

−


VCn Port UAT evaluation on 15m and 24H NE/FE

−

VCn-TTPBidR1

VCn Port UAT evaluation on bidir 24H (Q)

2.3.7. 2Mb/s PDH POM on incoming and outgoing signal

Applicable to the 2Mb/s ports carrying ITU–T G.704 (63x2Mb G.703/ISDN–PRA PORT) basic and multi-frame standard signals; enable/disable programmability is supported per individual 2Mb/s Port. PM capabilities according to the standard data collection modes: G.826 bi-directional for QoS, M2120 unidirectional near–end/far–end for Maintenance are supported. 2.3.8. HO & LO POM - PATH OVERHEAD MONITORING (*)

The Path Overhead Monitor function is applicable to the supervision of equipped VCi paths. The POM function processes the overhead (POH) to monitor VC-n (n=12, 3, 4, 4-4c, 4-16c, 4-64c). 2.3.9. PM on VC-n POM unidirectional for segment monitoring (Near-End primitives)

Feature Available (For STM-16 concatenated signal only on STM-16 slim port). 2.3.10. PM on VC-n POM unidirectional & bi-directional for end-to-end monitoring (FarEnd primitives)

Feature Available (For STM-16 concatenated signal only on STM-16 slim port). PM LPOM@VC-12, VC-3 available.

ED

10


22/56

2.3.11. PM on 2Mb/s ISDN PRA t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

The feature provides both unidirectional and bi-directional PM data collection at 2Mbit/s ISDN PRA terminations. 2.3.12. Unidirectional and bi-directional PM on 2Mbit/s PDH POM for end-to-end and segment monitoring.

Feature available. 2.3.13. HO & LO TCT/TCM - Tandem Connection Termination & Monitoring (*)

TCM allows monitoring within the operator domain. The quality within the operator’s own domain can be proven regardless of the received quality of the signal at the entry point of the network. At the input point the reference value is set to zero by using the TCM feature. 2.3.14. Unidirectional/Bidirectional Perform. Mon. on HO & LO TCT/TCM for maintenance (*)

Only near end unidirectional PM available. 2.3.15. Remote Inventory

Factory labeling with the electronic inventory data of each replaceable NE’s hardware unit can be retrieved by OS and CT interface; OMSN’s manufacturing inserts the inventory data in a dedicated non–volatile memory hosted in the unit itself according to the Alcatel-Lucent standard format. 2.3.16. Operating functionalities – Configuration

1660SM manages the following configuration: −

IP and LAN addresses (A MAC ADDRESS in accordance of IEEE standard is available in the system; the Mac Address is unchanged by the operator but its utilization is software selectable).

−

Dual addressing of OS.

−

Is/Is Routing.

2.3.17. UAT – Unavailable Time Alarm

The PM data collection reports to OS/CT the transitions between the availability and the unavailability status of the monitored trail. 2.3.18. UPA – Unavailable Path Alarm (SSF)

Unavailable Path Alarm (SSF) available at all path levels. 2.3.19. TCA – PM Threshold Crossing Alarm

Feature available.

ED

10


23/56

2.3.20. Network Termination functionality on 2Mb/s ISDN–PRA t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

Applicable to the 2Mb/s ports carrying ITU–T G.704 multi-frame standard signals. The feature provides: −

the handling of the ISDN–PRA standard NT1 functionality as per ETS 300 233.

−

the handling on ISDN leased line according to DT specification.

2.3.21. Access Control Domain on CT

The security management provides a set of functions to protect the system against unauthorized access by users, procedures or other influences. 2.3.22. Alarm flooding control (EFD)

This feature improves alarms management to prevent alarms f looding. 2.3.23. Performance monitoring retrieval with simple scanner

This feature improves the PM collection from NM. 2.3.24. ETHERNET PERFORMANCE COUNTERS

A set of performance counters is foreseen for QoS and maintenance purposes. The counters apply to "rate adaptive" transport of Ethernet packets over SDH Virtual Containers. Ethernet/FastEthernet and GigabitEthernet application: counters apply to ISA Ethernet 10/100 and the relevant access module and ISA-Gb Ethernet (rate adaptive) unit. Physical interface counters and aggregate counters are available: Physical interface counters: to monitor the working status of the transceiver (defined in RFC 2665 and RFC 2668): symbolError, MediaAvailableExits, JabberState, FalseCarrier •

•

ED

Aggregate counters: to monitor all Ethernet traffic passing through the same aggregate port:

10

-

TRCO = total number of received correct Ethernet Octets;

-

TRCF = total number of received correct Ethernet Frames;

-

TTO = total number of transmitted Ethernet Octets;

-

TTF = total number of transmitted Ethernet Frames;

-

TRSEF = total number of received Service Error Ethernet Frames.

-

TDF = total discarded framesThe aggregate counters are reported in Figure 3


24/56


TRCO TRCF

TRSEF ISA Eth / GbE port

TTO TTF

TRCO TRCF

Node_A

TTO TTF

TRSEF

Node_B

SDH VC-n pipe

TDF

TDF

OMSN

ISA Eth / GbE port

OMSN Figure 3 Aggregate Ethernet counters

2.3.25. AUTO MON status on SDH and PDH ports

In order to prevent alarms from being raised and f ailures being reported during trail provisioning actions, trail termination functions have the ability to enable and disable fault cause declaration. This is controlled via their termination point mode or port mode parameter. The termination point mode (Figure 4) shall be either "monitored" (MON) or "not monitored" (NMON). The state shall be MON if the termination function is part of a trail and provides service and NMON if the termination function is not part of a trail or is part of a trail which is in the process of set-up, breakdown or re-arrangement.

Figure 4 Termination point monitoring state

In physical section layers, the termination point mode is called the port mode. It has three modes (see ): MON, AUTO, and NMON. The AUTO mode is like the NMON mode with one exception: if the LOS defect clears, the port mode is automatically changed to MON. This allows for alarmfree installation without the burden of using a management system to c hange the monitor mode. The AUTO mode is optional. When it is supported, it shall be the default mode; otherwise, NMON shall be the default mode.

ED

10


25/56


AS described above, the “AUTO-MON” implementation on OMSNs is compliant to ITU-T G.806 rec. In addition the following feature-enhancement have been introduced: 

Provisioning at the Network Element level for the expected behavior in order to avoid impact on other customer networks;



A parameter at the physical port level allows management of the current state of the port (AUTO / MANUAL);



No impact on current ASAP mechanism.

No Hold Off time is foreseen (only F4 filter applied). 2.3.26. PERFORM. MONIT. ON AU3 POM

The feature applies to 4xOC3 with AU3/TU3 conversion optical unit. It consists of a set of counters related to Path Overhead Monitoring on AU3. AU PJE (Administrative unit point justification event) are not included in the set of counters.

2.4.

NETWORK

2.4.1. VCi Signal Label Management

C2 byte and 5–7 bits of V5 byte are used for HO–VCs and LO–VCs signal label; the EC configures the VCi Signal Label Management in two different ways: •

•

Automatic way according to the Connections Manual way, forcing ”Equipped–non–specific” Signal Label

In the system the signal label mismatch detection is managed according to ITU G.783 Aug.97 recommendation: it causes the ”all 1” insertion downstream and the PLM alarm is also generated. 2.4.2. J1 - PATH TRACE Management

The feature provides the ability to setup the Trail trace handling on VC3 and VC4.

ED

10


26/56

2.4.3. J2 – PATH TRACE Management t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

The feature provides the ability to setup the Trail trace handling on the VC12. 2.4.4. J1 –J2 HEX Management

This feature provides J1 and J2 management with hexadecimal figures by Craft Terminal. 2.4.5. J0 – SECTION TRACE management

The feature provides the ability to setup the section trace handling on the STM-N interface at Regenerator layer. The J0 byte of the RS-OH is used, according to the standard 16 bytes multiframe format defined in the G.707 recommendation. 2.4.6. J0 – HEX Management

This feature provides J0 management with hexadecimal figures by Craft Terminal. 2.4.7. OH Bytes Access and Re–routing Management

1660SM offers a wide range of service channels in the Section Overhead (SOH) and Path Overhead (POH) bytes of the synchronous frame. These bytes are used as alignment word, parity check, network management operations, performance monitoring; some data and orderwire channels are available to the user. The OH bytes to manage are the following: •

MSOH bytes: E2, National Use, Future Use, Gen. Use for pass–through

•

RSOH bytes: E1, F1, National Use, Future Use

•

VC4/VC3 OH bytes: F2, F3

All such bytes can be flexibly cross–connected from/to any SDH or PDH port in the system or from/to local AUX/EOW terminations. The system has the capability to manage and configure upon management request only unprotected bidirectional OverHead (OH) cross–connection. The functional types of OH cross–connections are: •

Bidirectional terminated point–to–point cross–connections

•

Bidirectional point–to–point cross–connections

2.4.8. BWSF – Bidirectional working on single fiber

This functionality allows using only one fiber for the two direction TX and RX; for this purpose an external optical passive coupler must be used. This application is provided on STM16, STM1 (not on STM4). 2.4.9. ATM TRANSPORT Management

Specific ISA-ATM matrix units and dedicated software load support the integration of ATM datatransport services inside the OMSN. References between OMSN releases and ISA ATM releases and information about release note of the ISA cards can be retrieved from the document: ED

10


27/56

2.4.10. AIS on PDH ports t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

AIS alarm on 2 and 34 Mb/s ports is provided on unframed 2/34 Mb/s signals. 2.4.11. ISA Ethernet main board

10/100 Mb/s Ethernet units allow creating inside of OMSN’s a LAN to LAN connection as a point to point between two routers or switches through an SDH network. The board acts as a gateway towards the SDH network. Ethernet frames are mapped over a SDH VC using Generic Framing Procedure (GFP) encapsulation. The Ethernet traffic, opportunely mapped in the SDH transport structures, is then sent toward the SDH matrix from the back–Plane, which has 4 STM–1 equivalent bandwidth throughput. Ethernet frames are mapped over an SDH VC among the following: •

VC–12

•

VC–3

•

VC4

One Ethernet interface is mapped in one SDH VC: no grooming of Ethernet frames in the SDH network is provided within this release. Protection occurs at SDH level. Service requirements for the unit: •

Point-to-Point interconnection;

No MAC Address Filtering: all what is received is transported. Local traffic is rerouted by an external switch; •

•

Max Density of Ethernet 10/100 interfaces;

•

Protocol Transparency: Ethernet frames are transported on the other side as they are;

Bandwidth Compression: the allocated bandwidth on the SDH network is less than max bandwidth of the Ethernet interface (10 Mb/s, 100 Mb/s). •

2.4.12. ISA Ethernet access board

The Ethernet access card is placed in the access area and is able to provide 14 x 10 /100 Mb/s Ethernet interfaces to allow LAN to LAN connections. On this access card only the physical interface function is implemented, so it must be used in conjunction with the relevant ETHERNET port where the signal is processed in order to be transported in the SDH v irtual containers. 2.4.13. ISA-Gb Ethernet rate adaptive access module

It this SW release it is possible to use 2 out of 4 GbE interfaces in the ISA-Gb Ethernet rate adaptive access module in conjunction with the ISA Ethernet 10/100 port. Each GbE i/f is mapped into 1xVC4 using the GFP encapsulation. The ISA Ethernet 10/100 port controls the GbEthernet access module.

ED

10


28/56

2.4.14. ISA GbEthernet rate adaptive main board t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

The board allows carrying Gigabit Ethernet packets over SDH Virtual Containers, by mean of Generic Frame Protocol (ITU-T G.7041). Different bandwidth compression ratios are available: · 1:1 --> GE mapped in 7 VC-4 with Virtual Concatenation; · 1:2 --> GE mapped in 4 VC-4 with Virtual Concatenation; · 1:4 --> GE mapped in 2 VC-4 with Virtual Concatenation; · 1:8 --> GE mapped in 1 VC-4. The capability of transporting GE traffic over a single VC4 as VC4-1v is managed. 802.3x Ethernet Flow Control is supported. The board has 4 GE interfaces; it can be housed in any port slot of 1660SM. 1.2Gb/s max throughput toward the back-plane is achievable, while when used in a non-enhanced slot the throughput is limited to 622Mb/s. Auto negotiation feature is available in this release. In this release the frame length supported is extended to 2K. 2.4.15. LCAS functionality on ISA GbEthernet rate adaptive

The Link Capacity Adjustment Scheme (LCAS) functionality has been introduced in the ISA GbE board. LCAS implementation is compliant to ITU-T G.7042/Y.1305 LCAS for virtual concatenated signals allows to cope with the following needs, relevant to ethernet signals mapped over a bundle of SDH VCs (1 to 7 VC4s):  variable bandwidth management ; 

fault and recovery management.

LCAS enables hitless bandwidth management through the following capabilities: On-demand “add” server VC4v to increase the bandwidth devoted to Ethernet transport service;



On-demand “remove” server VC4v to decrease the bandwidth devoted to Ethernet transport service.



2.4.16. ISA-PR Edge Aggregator unit

The board is an ISA "packet ring" edge aggregator, suitable to be used on OMSN equipment. It is able to manage an MPLS “server” layer that can transport and aggregate in the SDH network the Ethernet “client” layer. References between OMSN releases and ISA Packet Ring Edge Aggregator releases and information about release note of the ISA cards can be retrieved from the document:

ED

10


29/56

2.4.17. 4xSTM-4 port t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

The board is able to manage up to 2 x STM-4 streams. The board hosts up to 2 interfaces into the front panel, which can be equipped with S.4.1/L.4.x (x= 1, 2) optical plug in. The configuration is done by CT/ NM. On each interface, the automatic Laser Shut-down is available according to theG.958 recommendation. It can be hosted on 1660SM in 'Enhanced HS slots" to manage up to 2 x STM-4 streams (access module not applicable). Only HO structured is available. This board is used to optimize the interconnection with ISA PR Matrix. 2.4.18. 16xSTM-1/ 4xSTM-4 optical port This board can manage up to 16 x STM- 1 or up to 4 x STM-4 optical streams. The board is 1 slot wide. Up to 4 interfaces can be hosted on the main board: •

4xSTM-1 optical SFP;

•

4xSTM-4 optical SFP.

Short haul and long haul interface are available and can be used on the same module. Mixed configuration of STM-1 and STM-4 SFP on the same card is not allowed. When the main board is equipped with STM-1 SFP it is possible to extend the i/f density with additional 12xSTM-1 SFP on the dedicated access module (see paragraph below).

12xS TM-1 opt. acces s

16xS TM-1 el. access

4xSTM-1 I/f

No optical I/f

4xS T M-4 i/f

Figure 5 16xSTM-1/4xSTM-4 and access modules combination

If there are no SFP modules on the main board it is possible to use the 16xSTM-1 electrical access module for electrical STM-1 connections (see Figure 5). Only 4 interfaces among the 16 can be selected as Synchronization source , for the DCCchannel or for Auxiliary cross-connection. The configuration is done by CT/ NM. Linear MSP can be configured among STM-1 and STM-4 i/f between ports equipped in the same type of slot: all ports equipped in the HS slots (slot#24,27,30,31,32,33,36,39)or all ports equipped in the Enhanced slot (slot# 25,26,28,29,34,35,37,38). EPS protection can be enabled with the electrical access: the protecting (spare) port has to be plugged at the left side of the protected (main) port or ports, HPROT Enhanced access card must be plugged at the left side of the electrical access module or modules. Up to 15+1 EPS protection scheme is supported or up to 8 groups 1+1 EPS protected are supported. Revertive mode is available.

ED

10


30/56

2.4.19. 12xSTM-1 optical access t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

This access module can be used in conjunction with the 16xSTM-1/4xSTM-4 port when STM-1 optical modules are plugged into the port. Up to 12xSTM-1 optical SFP modules can be equipped on this access module. The module is 2 slots wide. 2.4.20. 16xSTM-1 electrical access

This access module can be used in conjunction with the 16xSTM-1/4xSTM-4 port when no optical modules are equipped on the port. The module is one slot wide. 2.4.21. ISA-PR Matrix

ISA PR unit is a "packet-ring" add-drop multiplexer sub-system operating as an embedded "overlay" ring, which is transported on top of 1660SM equipment. The main capabilities of the boards are the following:· ethernet traffic aggregation from multiple edge ethernet interfaces onto Ethernet uplinks at the central gateway node;· full bandwidth sharing through MPLS statistical multiplexing of ring bandwidth between ethernet ports/services among end users; customers segregation via MPLS; traffic engineering is guaranteed by the presence of the “connection oriented“ MPLS server layer; three distinct classes of service for different application requirements and customer Service Level Agreement; multiple physical ethernet access types/interfaces (10/100Mbps and GbEinterfaces); point-to-point and multipoint-to-multipoint connections; ring-wide load balancing during ring congestion condition; sub 50ms packet based ring-protection through “wrapping”. It can be deployed in ring topologies with a maximum supported packet throughput of 6.4Gbps. The unit consists of a packet add-drop multiplexer card (2slots/8TE width), to be plugged in the basic area of 1660SM and one or two line access modules (2slots/8TEwidth) to be plugged in access area of 1660SM. The packet matrix card has 2 West + 2 East STM-4 optical SFP ports and it is able to manage a single STM-4 or dual STM-4 optical ring. Slot positions for packet ADM card and access modules are specified in the table below. References between OMSN releases and ISA Packet Ring Matrix releases and information about release note of the ISA cards can be retrieved from the document:

Port module slots 24-25 25-26 26-27 27-28 28-29 29-30 30-31 31-32 32-33 33-34 34-35 35-36 36-37

ED

10

Left Access Module slots

Right Access Module slots

1-2 2-3 3-4 4-5 5-6 6-7 7-8 or 8-9 8-9

3-4 4-5 5-6 6-7 7-8 8-9

13-14 14-15 15-16 16-17

Comments Also single Access Also single Access Also single Access Also single Access Also single Access Also single Access

13-14 13-14 or 14-15 15-16 16-17 17-18 18-19

at 2-3 at 3-4 at 4-5 at 5-6 at 6-7 at 7-8

Also single Access at 14-15 Also single Access at 15-16 Also single Access at 16-17 Also single Access at 17-18


31/56


Port module slots 37-38 38-39

Left Access Module slots

Right Access Module slots

Comments

17-18 18-19

19-20 20-21

Also single Access at 18-19 Also single Access at 19-20

Table 5 ISA PR Matrix slot positions

2.4.22. ISA PR 16xETH 10/100 access module

The Ethernet access card is placed in the access area and is able to provide 16 x 10 /100 Mb/s Ethernet interfaces. This access card must be used in conjunction with the ISA PR Matrix port where the signal is processed. Please refer to table 5 for the slot positions of ISA PR Matrix and access module. 2.4.23. ISA PR 2xGbE access module The GbEthernet access card is placed in the access area and is able to provide 2 x 1000 SX/LX Ethernet interfaces. This access card must be used in conjunction with the ISA PR Matrix port where the signal is processed. Please refer to table 5 for the slot positions of ISA PR Matrix and access module. 2.4.24. ISA ES-1

ISA ES1 provides bridging functionality enhancing the Ethernet over SDH transport capability of 1660SM. On top of performing classification, policing and scheduling, standard mapping over VC-12xv and VC3xv is performed in accordance with ITU-T G.7041, ITU-T G.7042 (LCAS) and ITU-T G.707. Two versions of the boards are available: •

Eight Ethernet electrical ports 10/100 are available on the front panel of the boards and the backpanel capacity is 1xVC4 equivalent;

Eight Ethernet optical ports 10/100, to be equipped with SFP S-1.1 are available on the front panel of the boards and the backpanel capacity is 1xVC4 equivalent. LCAS for virtual concatenated signals allows to cope with the following needs, relevant to ethernet signals mapped over a bundle of SDH VCs:  variable bandwidth management ;  fault and recovery management. •

LCAS enables hitless bandwidth management through the following capabilities:  On-demand “add” server VC12v/VC3v to increase the bandwidth devoted to Ethernet transport service;  On-demand “remove” server VC12v/VC3v to decrease the bandwidth devoted to Ethernet transport service. For more information please refer to the relevant ISA ES1 release note. In this release the maximum number of VC12 concatenated part of a VCG is extended to 50.

ED

10


32/56

2.4.25. ISA ES-4 t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

ISA ES4 provides bridging functionality enhancing the Ethernet over SDH transport capability of 1660SM. On top of performing classification, policing and scheduling, standard mapping over VC-12xv and VC3xv is performed in accordance with ITU-T G.7041, ITU-T G.7042 (LCAS) and ITU-T G.707. Eight Ethernet ports 10/100 and 1 GB Ethernet port (1000 Base SX/LX SFP) are available on the front of the card. The backpanel capacity is 4xVC4 equivalent. LCAS for virtual concatenated signals allows to cope with the following needs, relevant to ethernet signals mapped over a bundle of SDH VCs:  variable bandwidth management ;  fault and recovery management. LCAS enables hitless bandwidth management through the following capabilities:  On-demand “add” server VC12v/VC3v to increase the bandwidth devoted to Ethernet transport service;  On-demand “remove” server VC12v/VC3v to decrease the bandwidth devoted to Ethernet transport service. The GbE interface is managed in this release. In this release the maximum number of members of each VCG is extended to: •

VC-12: 63

•

VC-3: 12

•

VC-4: 4 (HO virtual concatenation is supported)

GMII on ISA ES4 is supported. For more information please refer to the relevant ISA ES4 release note. ISA/OMSN SW compatibility tables: 3AL 78911 0378 2.4.26. ISA ES-16

ISA-ES16 has up to 16 VC-4 of bandwidth available (depending on the back panel capacity of the OMSN equipment). ISA-ES16 is a port less card that can use specific access modules: 14 x FE access module: 14 x Fast Ethernet ports (10/100 BaseT) 4 x GE access module: 4 x GB Ethernet ports with SFP plugs (Optical SX, LX/LH or ZX) ISA ES16 blade has the following main characteristics: 1 slot wide (4TE) it can be housed in any port slot of 1660SM 2.4 Gb/s max packet throughput Interfaces (2 versions) 14 x ETH 10/100 interfaces o 4 x ETH 1000 interface SFP (SX, LX/LH or ZX) o MPLS mapping onto VC-x (x = 12, 3, 4) trunk and ETH ports (IETF Martini) with per flow QoS and supports any topology • •

• • • •

For more information please refer to the relevant ISA ES16 release note. ED

10


33/56

ISA/OMSN SW compatibility tables: 3AL 78911 0378 t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

2.4.27. 4 X ANY UNIT

The 4xANY board allows multiplexing in the time domain up to 4 client signals into one single 2.5Gb/s optical channel (server signal). A mixing of SDH and Data Services is possible. Multiplexing scheme delivers a fully compliant SDH frame. The signal can hence be directly connected to a SDH ADM/DXC without requiring prior de-concentration. Up to 4 client signals can be independently handled among the following types: Fast Ethernet, FDDI (125Mbps), ESCON (200Mbps), Digital Video (270Mbps), Fiber Channel (1.0625Gbps), FICON (1.0625Gbps), Gigabit Ethernet (1.25Gbps). Server STM-16 signal is connected to SDH matrix through 1660SM back panel. The board (8TE wide) is applicable to 1660SM only. It can be plugged in "Enhanced HS slots" (slots: 25&26, 28&29, 34&35, 37&38) to fully exploit up to 2.5Gb/s (16 x AU4s) throughput; if plugged in standard "HS slots" (slots: 30&31, 32&33), up to 1.2Gb/s (4 x AU4s) bandwidth is available. Insertion of the board across hybrid slots ("enhanced HS slots" + "HS slots") is not managed. As far as client signals allocation is concerned three cases has to be distinguished: •

4xANY unit plugged in "enhanced HS slots": client signal allocation is shown in Figure 6;

•

4xANY unit plugged in "HS slots": client signals allocation is shown in Figure 7.

FE, FDDI, ESCON, DV, STM1 (OC-3), #1 STM4 (OC12)*, #3 N.eq.

FE, FDDI, ESCON, DV, STM1 (OC-3), STM4 (OC-12), N.eq.

FE, FDDI, ESCON, DV, STM1 (OC-3), N.eq.


#2

FE, FDDI, ESCON, DV, #1 STM1 (OC-3), N.eq.

N.eq.

#2

#4

#3


GE, FC, #4 FICON, N.eq.

N.eq.

#1

#2

#3

FE, FDDI, ESCON, DV, STM1 (OC-3), N.eq.

#4

N.eq.

#1

#3

N.eq.

#2

#4

GE, FC, FICON, N.eq.




Figure 6 Client signals allocation (drawers configuration) in Enhanced slots

ED

10


34/56

FE, FDDI, ESCON, DV, t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

#1 N.eq .

#2

FE, FDDI, ESCON, DV, N.eq .

FE, FDDI, ESCON, DV,

#3

#4

N.eq .

FE, FDDI, ESCON, DV,

N.eq .

#1

#3 N.eq .

#2


N.eq.

#4

N.eq .

Figure 7 Client signals allocation (drawers configuration) in H.S slots

2.4.28. Double Multi-rate Transponder Unit

The board provides the capability to manage two different separate channels, each of them able to achieve two different functionalities: • transponder function, namely "b&w" to "colored" conversion; • regenerator function, namely "colored" to "colored" conversion. It can host all the 8 possible Coarse WDM modules with SFP transceiver. CWDM transceiver are ITU-T grid compliant (1470-1490-1510-1530-1550-1570-1590-1610 nm). In addition "b&w" modules with SFP transceivers (up to 2.5Gb/s) are available. It supports STM-1, STM-4 and STM-16 rate. Also the following SFP types are supported on transponder module: •

•

•

•

•

•

CWDM GbE SFP on Transponder board management: this functionality is enabled using the multirate SFP modules already used for STM-16 application (1AB196340001...8 and 1AB196350001...8) BW SFP GbE on Transponder board management: SX, LX/LH, ZX. CWDM STM4 SFP on Transponder board management: this functionality is enabled using the multirate SFP modules already used for STM-16 application (1AB196340001...8 and 1AB196350001...8) BW STM4 SFP on Transponder board management: S-4.1, L-4.1, L-4.2 CWDM STM1 SFP on Transponder board management: this functionality is enabled using the multirate SFP modules already used for STM-16 application (1AB196340001...8 and 1AB196350001...8) BW STM1 SFP on Transponder board management: S-1.1, L-1.1, L-1.2

Two separate RS_POM blocks, perform the ‘RS layer not intrusive monitoring’ of SDH client signals (without FEC) handled by optical: the operator has the chance to monitor with no restriction 2 out of 4 signals received from ‘server’ or ‘client’ lines. The board is 4 TE wide and can be installed in any slot of the basic area.

ED

10


35/56

2.4.29. OADM & MUX/DEMUX MODULES t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

The modules described below allow the multiplexing of CWDM signals on the optical link. The CWDM signals may come either from a double multi-rate transponder or an STM-16 port slim or STM-16 SFP (8TE) equipped with CWDM plug-ins. 2.4.29.1.

1 X CHANNEL OADM MODULE

The module provides the capability to drop a single channel from a multi-channels CWDM signal. 8 modules are available to drop each CWDM wavelengths of ITU-T grid (1470, 1490,1510, 1530, 1550, 1570, 1590, 1610 nm). "Loss of signal" detection on received CWDM signal is provided in order to support the "standard" management of OMSNs. The "CWDM LOS" detection allows the operator to achieve an efficient and specific maintenance of the network in case of break of ring/linear cables, carrying mulltplexed signals. The board (8 TE wide) can be equipped in access area of 1660SM. 2.4.29.2.

2 X CHANNEL OADM MODULE

The module provides the capability to drop 2 channels from a multi-channels CWDM signal. 4 modules are available to drop the following couple of CWDM wavelengths: 1470/1490 nm, 1510/1530 nm, 1550/1570 nm, 1590/1610 nm. "Loss of signal" detection on received CWDM signal is provided in order to support the "standard" management of OMSNs. The "CWDM LOS" detection allows the operator to achieve an efficient and specific maintenance of the network in case of break of ring/linear cables, carrying mulltplexed signals. The board (8 TE wide) can be equipped in access area of 1660SM. 2.4.29.3.

8 X CHANNEL MUX/DEMUX MODULE

The module provides the capability to terminate 8 channels from a multi-channels CWDM signal. 8 CWDM ITU-T grid compliant filters are equipped on the MUX/DEMUX module: 1470,1490, 1510, 1530, 1550, 1570, 1590, 1610 nm. "Loss of signal" detection on received CWDM signal is provided in order to support the "standard" management of OMSNs. The "CWDM LOS" detection allows the operator to achieve an efficient and specific maintenance of the network in case of break of ring/linear cables, carrying mulltplexed signals. The board (8 TE wide) can be equipped in access area of 1660SM. 2.4.30. 4 X OC3 with AU3/TU3 conversion optical unit

This board can manage up to 4 x OC-3 (SONET) streams. The board hosts up to 2 interfaces into the front panel, which can be e quipped with 155Mb/s electrical plug-in or S.1.1/L.1.x (x= 1, 2, 2JE) optical plug in. The other two interfaces can be hosted in the Access area using the 2 x OC3 electrical/optical module (namely 2 x 140/STM-1 module) plus the electrical/ optical plugin. The 2 x OC3 electrical/optical module have to be equipped in the access slot corresponding to the traffic unit slot. Each combination of interfaces (electrical,S.1.1,L.1.1,..) can be equipped in the same board. On OC-3 interface the Sonet mapping is managed therefore the RS and MS sections are terminated, the 3 AU3 are processed to extract or insert the 3 VC3. This unit performs the AU3/TU3 conversion, which allows the transport in SDH network of Sonet VC3 traffic. ED

10


36/56

The conversion is performed on OC-3 interface: t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

the 3 VC3 are extracted, then re-mapped in SDH VC4 container, this container is passed to the matrix where it is managed as a structured VC4. The AU3/TU3 conversion mechanism achieved by 4xOC3 board is shown in Figure 8. The Sonet interface (OC3) have not to be configured as Synchronization source. The OH byte of RS and MS section are managed according SDH ITU standard. The configuration is done by CT/ NM. No EPS is supported for this board.

Figure 8 AU3/TU3 conversion structure

ED

10


37/56


2.5.

NETWORK PROTECTION

2.5.1. STM–N linear single–ended 1+1 APS

1+1 Single Ended Protection (Not Revertive, K1/K2 Management in accordance with G783 ITU–T Recs) Switching time: < 50 msec. No extra traffic available. APS protection can be enabled only between ports equipped in the same type of slots: HS/HS or Enhanced/Enhanced; furthermore for STM-16 ports the same type of modules must be used: 2xSTM-16 port (8TE) or 2xSTM-16 slim port. 2.5.2. STM–N linear dual–ended 1+1 APS

1+1 Dual Ended Protection (Not Revertive, K1/K2 Management in accordance with G783 ITU–T Recs) Switching time: < 50 msec. No extra traffic available. Switching Criteria: SF + SD (SD always enabled) APS protection can be enabled only between ports equipped in the same type of slots: HS/HS or Enhanced/Enhanced; furthermore for STM-16 ports the same type of modules must be used: 2xSTM-16 port (8TE) or 2xSTM-16 slim port. 2.5.3. STM-1 linear dual-ended 1:N APS

STM-1 linear dual-ended N+1 APS. 1:N linear protection without extra traffic (Revertive, K1/K2 Management in accordance with G783 ITU–T Recs). N= 1-15. Switching time: < 50 msec. No extra traffic available. APS protection can be enabled only between ports equipped in the same type of slots: HS/HS or Enhanced/Enhanced. 2.5.4. STM-4 linear dual-ended 1:N APS

Bi-directional 1+N Linear protection applied at STM4 level (Revertive, K1/K2 Management in accordance with G783 ITU–T Recs).

ED

10


38/56

N =1-15. t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

Switching time: < 50 msec. No extra traffic available. APS protection can be enabled only between ports equipped in the same type of slots: HS/HS or Enhanced/Enhanced. Commands: Manual/Release

Lockout/Release

Forced/Release

OK

OK

OK

MSP

2.5.5. SNCP/I among VCi trails (i=12,3,4)

Sub–network connection protection in the SDH transport network is performed on a network layer basis (HO or LO path layer). It is a 1+1 automatic protection type, which can be revertive or non-revertive, and the protection switch is always unidirectional single–ended. When establishing a protected connection: – From CT/OS can be selected: •

the revertive/non-revertive mode;

AIS and LOP are used as switch criteria. – It’s not possible to select: •

the Wait To Restore time (is fixed: 5 min.);

The switching decision can be taken at the NE level (automatic switch) or at the OS level (management switch). The following table describes the supported commands by 1660SM:

SNCP

Manual/Release

Lockout/Release

Forced/Release

Not available

OK

OK

The automatic switch is initiated upon detection of failure on the receiving end (sink side).

ED

10


39/56


SNCP/I (inherent)

Switching Type

Switching criteria

mode

Wait To Restore time

unidirectional/ single–ended

AIS (SSF) AU– LOP (SSF)

revertive / non-revertive

5 min.

Switching time: < 50 msec. Note 2: The switching time doesn’t include the time to detect the alarm. 2.5.6. SNCP/N among VCi trails (i=12,3,4) (*)

For general info, see below. For SNCP/N the switching criteria are: •

•

The TSFprot condition generated by the POM function defined in Rec. G.783. TSFprot= SSF+dTIM+dEXBER (optional)+dUNEq. the SD generated by POM.

2.5.7. Hold-Off times for protection independency in SNCP

It provides the ability to set an interval delay between the detection/clearing of the failure causes and the activation/releasing of the protection switches .The programmability rules for the delay values are the following: Range: from 0 to 10s. Steps: 0,30ms,50ms,70ms,100ms,300ms,500ms,700ms,1s,3s,5s,10s. 2.5.8. Drop & Continue + Insertion SNCP

Protected connection modes specifically dedicated to upgrade the basic SNCP protection in order to support the Dual–Node interconnection between two rings by using STM–N links according to the G.842 architecture schemes: Path Selector functionality. The figure below, describes the multi–point connection used to interconnect two SNCP rings inter-working;

ED

10


40/56


Figure 9 HO and LO Drop & Continue protected + insert.

2.5.9. 2F MS–SPRING at STM16 intefaces

It provides the support to the standard MS–SPRING protection scheme according to the G.841 recommendation in two fibers bidirectional rings (max number of nodes: 16). Main characteristics: •

K1/K2 management: bridge & switch actions according to G841.

•

Switched entity: VC4.

•

Switching criteria: MS–AIS, LOS, LOF, B2exBER, B2Degrade.

Revertive switching: programmable WTR=0–15m with step of 1 min. (Programmable WTR on MS–SPRING). •

•

Extra traffic: not supported.

G841 supported commands: Clear, Lockout of working ch. rings, lockout of protection, forced switch ring and manual switch ring. •

MS-SPRING @ STM-16 is available with STM-16 slim port and with STM-16 8TE. The ports involved in the protection scheme equipped in the same shelf must be of the same type and must be inserted in the same type of slots HS/HS or Enhanced/Enhanced. 2.5.10. 2F MS–SPRING at STM64 interfaces

It provides the support to the standard MS–SPRING protection scheme according to the G.841 recommendation in two fibers bidirectional rings (max number of nodes: 16). Main characteristics: •

K1/K2 management: bridge & switch actions according to G841.

•

Switched entity: VC4.

ED

10


41/56

•


Switching criteria: MS–AIS, LOS, LOF, B2exBER, B2Degrade.

Revertive switching: programmable WTR=0–15m with step of 1 min. (Programmable WTR on MS–SPRING). •

•

Extra traffic: not supported.

G841 supported commands: Clear, Lockout of working ch. rings, lockout of protection, forced switch ring and manual switch ring. •

Mixed STM-64 and STM-16 MS-SPring configuration: Up to 4 x 2fibers MS-SPRing at STM-16 and 2 x 2fibers MS-SPRing at STM-64 can be managed by each 1660SM. Only STM-16 MS-Spring configuration: Up to 8x2fibers MS-Spring at STM-16 can be managed by each 1660SM. Only 16AU4 can be structured when MSSPRING protection is used since up to 32 AU4 out of 64 can be structured on STM-64 port. 2.5.11. D&C + Insertion on MS–SPRING protection (RIW)

It is applicable where no extra traffic is managed; in our case on 2F MS–SPRING. The feature is applicable to the architecture which uses STM–N interfaces for interconnecting the two rings (4 nodes Architecture), as well to collapsed ring in dual node interconnection, which means that rings are interconnected inside the matrix. 2.5.12. Collapsed single–node ring interconnection

Protected connection modes specifically dedicated to upgrade the basic SNCP protection in order to support the Single–Node interconnection between two rings using VCi connections (through internal matrix). The difference with respect to the traditional approach is that, two protected connections in SNCP are now interconnected inside the Matrix and no Tributary interconnecting the two rings are needed: consequently the two protected connections are integrated on a single collapsed node. Collapsed single node interconnection is now performed with one node instead of two. 2.5.13. Collapsed dual–node ring interconnection

Protected connection modes specifically dedicated to upgrade the basic SNCP protection in order to support the Dual–Node interconnection between two rings using VCi connections (through internal matrix). The difference with respect to the traditional approach is that, two protected connections supporting the traditional Drop & Continue Interconnection are integrated on a single collapsed node. Collapsed dual node interconnection is now performed with two nodes instead of four. 2.5.14. AU/TU independent allocation SNCP

The feature provides the ability to connect every SNCP protected Path to different AU# (HO– SNCP) or TU# (LO–SNCP) on the two server trails devoted to the transport the working and the protection payload.

ED

10


42/56

2.5.15. STS–3c pointer management (SS bits configuration) t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

The feature provides the interworking with SONET equipments by providing the SW ability to setup the output value of the SS–bits in the H1 byte of the AU4 pointer (structure equivalent to the STS–3c in the SONET standard).

2.6.

CONNECTIVITY

The 1660SM SDH Cross–Connect is built upon a full non–blocking matrix that can interconnect VC4s, VC3s, VC12s between any SDH or PDH ports accessing the system. All Ports cross– connected by the matrix may be low order structured; several types of connections are below listed. •

VCi xC bidirectional point to point (i=12,3,4) a) bidirectional point to point Protected and Unprotected

•

VCi xC unidirectional point to point (i=12,3,4) b) unidirectional point to point Protected and Unprotected

•

VCi xC unidirectional multi point (i=12,3,4)

About the VCixC unidirectional multi point are available max 50 multileg and all can be SNCP/I protected. Table 6 High Order/Low Order connectivity for 1660S M

STM-64; STM–16; STM–4; STM– 140Mb 1 ports ports

STM.-64 STM–16; STM–4; STM–1 ports 140Mb ports 3x34Mb; 3x45Mb ports 2Mb ports

3x34Mb; 3x45Mb ports

2Mb ports

AU–4 Yes –

TU–3 – Yes

TU–12 – –

VC–4 Yes –

VC–3 – Yes

VC–12 – –

–

–

Yes

–

–

Yes

VC–4

Yes

–

–

Yes

–

–

VC–3

–

Yes

–

–

Yes

–

VC–12

–

–

Yes

–

–

Yes

AU–4 TU–3 TU–12

Up to 32 AU4 can be structured for each STM-64 port.

ED

10


43/56

2.6.1. AU4–4c among STM–N interfaces (n>=4) t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

It provides the ability to transport a single STM–N payload on a set of N (N>=4) contiguous AU-4s according to the ITU–T G.707 recs. 2.6.2. AU4-16c among STM-N interfaces (n>=16)

Feature available only with Slim STM-16 port and STM-64 port 2.6.3. Packet Concatenation on LO VCi (i=12,3) for E/FE traffic on ISA Ethernet main board and ISA Packet Ring Edge Aggregator

This feature allows to map data traffic entering OMSNs through an Ethernet/FastEthernet port of ISA-Ethernet board and ISA Packet Ring Edge Aggregator into a GFP pipe, made of ixVC12 or jxVC3, with i and j in the following range: •

i = 1..8 (max. 8xVC12);

•

j = 1..2 (max. 2xVC3).

No mixed configurations are allowed (it is not possible to transport the signal over a nonhomogeneous group of VC12 and VC3). The functionality model (in terms of Q3 interface) is the same as LO virtual concatenation. Each VC12 or VC3 of a packet concatenated GFP pipe can be independently transported over the SDH network in a standard way, following its own path. Packet concatenation allows the following capabilities in terms of bandwidth management: bandwidth increase/decrease (add/remove a VCx to GFP pipe), failure recovery after a single VCx fault, monitoring of the VCx path to be added without traffic interruption. Migration aspects In order to increase the bandwidth of an Ethernet path created in a release not supporting packet concatenation functionality (i.e.: rel. 3.1, 4.0), it is necessary to perform the following steps: · remove the path; · create the new packet concatenated path (with the right GFP mapping); Bandwidth increase is not hitless. Starting from SW release which supports packet concatenation functionality, all the new LO paths (including the one mapped i a single VCx) are created in a com patible way with respect to packet concatenation. Bandwidth increase can be performed in hitless way without removing the old path. References between OMSN releases and ISA Packet Ring Edge Aggregator releases and information about release note of the ISA cards can be retrieved from the document: ISA/OMSN SW compatibility tables: 3AL 78911 0378

ED

10


44/56

2.6.4. Idle – Active management on virtually concatenated VC-4 of ISA GbE main board t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

This feature is meant to provide a mechanism to allow variable bandwidth management of GbE traffic transport. It allows to add/remove one VC4v from a bundle of virtually concatenated VC4, carrying GbEthernet traffic between two ISA-GbE (rate adaptive) boards. Management of "idle" status of VC4 on NE allows NM system to implement a new VC4 trail through the network without adding it to the NxVC4v bundle supporting GbE traffic. Collection of alarms relevant new "idle" VC4 allows the operator to check that no faults are affecting the trail, before to add it to the NxVC4 bundle, by mean of an "activation" command. Once the operator has triggered the "activation" command, the new "active" VC4 will be virtually concatenated together with the other NxVC4 to support GbE traffic.

2.7.

TIMING

The Synchronization Subsystem (SETS SDH Equipment Timing Source according to ITU–T G.783) provides the timing reference required by all the components in the network element and represents the SDH Equipment Clock (SEC). The Synchronization Subsystem generates the internal synchronizing clock locking one of three configurable (by software via CT and/or OS commands) references: •

STM–N lines (STM–N synch references).

•

2Mbit/s traffic ports (2Mbs synch references)

2MHz/2Mbit/s external input (2MHz/2Mbs synch references). 2Mbit/s synch w SSM is managed in this release. •

•

Internal Oscillator

Up to 6 independent references can be defined among STM–N and 2Mbit/s traffic ports in the system (Programmable multiple synch sources (max 6)) . Automatic selection of one of the above references is available through an internal selector, which uses Quality (Synchronization Status Message algorithm) or priority criteria (SSM standard interworking). The SSM algorithm can be disabled via ECT or OS. An external 2MHz or 2Mb/s output is generated as a possible source for external devices. Additionally the SSM protocol is supported according to the standard rules based on the information field in time-slot 16 of the 2Mbs frame format. SEC (SDH Equipment Clock) is used as internal timing source and to time the outgoing STM–N signals. When all the selected references are missing or the reference quality of incoming signals is under a software selectable threshold the SETS (Synchronization Equipment Timing Source) goes into holdover mode or into free–running mode if a reference stable for more than 30 minutes was not stored. It is possible to force the free–running mode. A dedicated alarm is provided when the node enters in holdover or free–running mode due to either quality criteria or signal validity (Hold/Free–running alarm).

ED

10


45/56

The holdover mode guarantees less than .37ppm of frequency drift per day (.37 ppm/day holdover accuracy). t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

SEC characteristics according to G.813 (opt. 1) (Free–running stability: 4.6ppm). The managed SDH synchronization quality levels are: Table 7 Synchronization Equipment Timing Source

SDH S1 BITS 5–8

QUALITY LEVEL

0010

G811 PRC

0100

G812 SSU Transit

1000

G812 SSU Local

1011

G813 SEC

1111

Don’t use

2.7.1. ADM with SSU

This feature allows using OMSNs in conjunction with Synchronization Supply Unit (SSU). Here below the implementation of this functionality for both 2MHz and 2Mbit/s synchronization reference signals, is described. Figure 10 shows the block diagram for implementing these functionalities. The output quality is (generally) the same of the Q1 quality of the T4 selected timing source

SSU

T3 2MHz

T0 (quality Q1)

Sel B T1 (quality Q1)

T4 Sel A 2 MHz

DNU ADM SEC

Figure 10 ADM with SSU

ED

10


46/56


ADM with SSU using 2MHz reference signal.

The synchronization chain from STM-N (T1) signal to SEC (passing through SSU) consists of the following steps: •

•

•

The Output External Reference (T4) is locked to a timing reference (T1) according to the SSM (Synchronization Status Message) algorithm; SSU is locked to 2MHz signal (T4) coming form SEC (or it is in free-running if the received 2MHz is squelched); SEC (Synchronous Equipment Clock) is locked to the filtered T3 (2MHz) coming from SSU;

The quality of the SEC output timing reference (T0) is set to: •

•

•

•

When SEC is locked to T3 coming form SSU, the quality of the timing reference selected to generate T4 (Q1 in the figure); The quality of the SSU's Internal Oscillator when T4 is squelched (T4 is squelched if the quality of the selected T1/T2 (in Selector A) is lower than SSU's internal Oscillator); The quality of the SEC internal oscillator if no timing references are available to generate T0; The quality of the timing reference selected at the input T1 or T2, when T3 coming from SSU fails.

DNU (Do Not Use) is transmitted back to the interface selected as timing source for T4. 2.7.1.2.

ADM with SSU using 2Mbit/s reference signal with SSM supported.

Automatic DNU Generation. When ‘ADM with SSU’ using 2Mbit/s clock signal with SSM supported is configured, the DNU generation, for avoiding timing loop, is performed according to ITU-T G.781 fig.12-13-14. As long as the ADM transmits to SSU a T5 clock signal with a certain ‘SSM value’ and receives from SSU a T6 clock signal with the same SSM value, the ADM assumes that the SSU selects the T5 clock signal provided by the ADM itself as reference clock. This will result in DNU insertion in the traffic output port associated with the traffic input port used as source for the ADM clock. All other ADM outgoing signals will have the same SSM extracted by T6 clock signal coming from SSU (Figure 11).

ED

10


47/56


Figure 11 Automatic DNU generation (SSM supported).

Removal of Automatic DNU generation. If the transmitted and received SSM are no longer identical, the automatic DNU insertion in the traffic output port associated with the traffic input port used as source for the ADM clock is removed. All ADM outgoing signals will have the same SSM extracted by T6 clock signal coming from SSU (Figure 12).

Figure 12 Removal of Automatic DNU generation

ED

10


48/56


ADM with SSU using 2Mbit/s reference signal with SSM not supported.

When ‘ADM with SSU’ using 2Mbit/s clock signal with ‘SSM not supported’ is configured, the DNU generation, for avoiding timing loop, is performed according to ITU-T G.781 fig.9-10-11. Automatic DNU Generation. As long as the ADM transmits to SSU a T5 clock output which is not set to AIS, the ADM assumes that the SSU selects this T5 clock signal as reference clock. This will result in DNU insertion in the traffic output port associated with the traffic input port used as source for the ADM clock. All other ADM outgoing signals will have, as SSM value, the value forced by operator for signal coming from SSU (Figure 13).

Figure 13 Automatic DNU generation (SSM not supported).

ED

10


49/56

Removal of Automatic DNU Generation. t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

Figure 14 Removal of Automatic DNU Generation (SSM not supported)

If the T5 clock signal is set to AIS, the automatic DNU insertion in the traffic output port associated with the traffic input port used as source for the ADM clock is removed. All ADM outgoing signals will have, as SSM value, the value forced by operator for signal coming from SSU (Figure 14). 2.7.2. RETIMING ON THE 2Mb/s Interfaces (*)

Basically the retiming function applies to the outgoing signal of the 2Mb/s traffic interfaces the SEC timing: i.e. in the normal condition the synch reference of the SDH network. (*) FEATURE AVAILABLE only on 63x2 Mbit/s G.703/ISDN–PRA PORT HW.

2.8.

SUPPORT MANAGEMENT

The Support domain is divided into four parts: •

Event reporting management;

•

Event logging management;

•

Alarm management;

•

Alarm synthesis & summarization;

The Alarm management receives alarm notifications from other domains (transmission, connection, equipment, software synchronization and communication). 2.8.1. Event reporting management

The Event Reporting function is used by the System to notify events to OS. ED

10


50/56

2.8.2. Event logging management t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

The Event Logging function is used by the System to log events in OS and to control that logging by OS. 2.8.3. Alarm management

The Alarm function is used by the System to manage alarm reporting, alarm logging, alarm severity assignment, alarm status monitoring in OS. 2.8.4. Alarm summary, alarm synthesis and abnormal condition synthesis

The Alarm synthesis & summarization function is used by the System to summarize the current alarms of Network Element and provide audible and visual local alarm indications in OS. Abnormal condition synthesis management functions are used by a managed system to synthesize unusual conditions on the NE (like a loopback or not configured slots). An ”Abnormal Condition” status is present when: •

Equipment Expected = NULL

•

Equipment Actual <> NULL

2.9.

SECURITY MANAGEMENT

This facility is used by the OS to configure the access rights on the local terminal; the NE checks the OS address and verify if it is in the allowed OS list. Only in this case the OS connection is allowed, otherwise it is refused.

2.10. ENVIRONMENTAL CONDITIONS Operating Condition: ETS 300 019, class 3.2 Storage Condition: ETS 300 019, class 1.2 Transportation Condition: ETS 300 019, class 2.2 EMI/EMC Condition: ETS 300 386–1, ” Telecommunication centres”

ED

10


51/56

2.11. RELEASE 5.2B11: BUG LIST t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

[1]

TSDrd03119: In case of LCAS alarm the CPE/MND are not reported.

[2]

TSDrd03596: Keeping spare path configuration on VC12 and VC3 causes error.

[3]

TSDrd03597: The alarm LOMF and sequence Mismatch are not reported on ISA-ES1 board.

[4]

ONDvx03419: Packet loss during LCAS monitoring

[5]

ONDvx02101: GB Eth SFP STM1/4 optical information wrongly reported

[6]

PSCit31647: Toggling of TSF alarm after creation of new path on ISA-ES16 W.A. disable /enable LCAS

2.12. RELEASE 5.2B11: FIXED BUGS [1]

PSCit30988: 1660SM Matrix not stable traffic (Vodafon Spain)

[2]

PSCit30932: (MSP Toggling alarm LOS on spare)

[3]

PSCit33700: RUP on P4E4N after plug in board (power off/on NE is OK) (Telecom NZ)

[4]

PSCit34184: Reset counter PM Far End is not performed (CT)

[5]

ONDvx07283/PSCit34977: IP static route is not possible to delete (transpower)

[6]

ATSsn12777: Telenet: NGI alarm No EPS matrix is performed (Telenet)

[7]

ED

: Toggling NGI alarm (increase F4 filter)

[8]

PSCit34394: Modify STM-16 to CO16 after reset EC lost concatenated path

[9]

PSCit34518/PSCit34422: Full equipped node with 2 STM-64 boards plus 8 ISA-ES16 (Orange Spain)

[10]

PSCit34149: trail protected configured from RM SC restart (Portugal)

[11]

PSCit34487: False Tx Fail alarm on 10 Gbit port in 5.2.B10

[12]

PSCit34574: it is not possible to reconfigure module on P16_S1 (China Telecom)

[13]

PSCit34824: MIB corruption traffic down after plug in matrix (problem wrong Max number of VC4/VC3/VC12 terminated on ISA-ES16

[14]

PSCit34446/ONDvx11830: Problems with LCAS in ES-16/ES4 board

[15]

PSCit32559/PSCit31707: inter-working ISA-ES1 to ISA-ES16 Ethernet traffic is broken (BCC)

10


52/56


[16]

PSCit34488: L16.2 to L16.2+DDM (telecom Austria)

[17]

PSCit33509: LAPD problem after fail of matrix oscillator (Telenet)

2.13. RELEASE 5.2B11: RESTRICTION LIST

ED

[1]

Nectas for Q2 and QB3* manages one application per time.

[2]

Internal loop-back on STM16 ports which are synchronization sources causes timing loops

[3]

Internal loop-back command on STM-64 ports is not available.

[4]

ALS test mode in laser off: line alarms caused by laser switch-on at remote side are not filtered

[5]

HPOM and TCM & TCT on AU4-16c paths for STM-16 slim and STM-64.

[6]

MSP 1:N protection time switching is about 150ms.

[7]

No insertion of Tandem connection RDI/ODI for HTCT

[8]

Gigabit-Ethernet rate adaptive main board and access card: RUTM alarm is not managed on optical drawer.

[9]

Card fail alarm is reported by 3x34/45Mb access card when a failure occurs on the relevant main board.

[10]

EPS 1+1 3x34/45 Mb/s card switching time is higher then 50ms

[11]

TCT on VC4 of 4xANY unit is not available

[12]

The 4xANY unit is not managed when equipped into HS slot (30&31-32&33)

[13]

It is not possible to modify the VCx on ISA ES4 board.

[14]

4xSTM-4 board used for interconnection with ISA-PR board the MSP protection on second drawer is not available.

[15]

ISA ES4: Adding new member to group of VC12xV/VC3xV configured without LCAS protocol is only allowed if it is allocated on timeslot higher than the last implemented.

[16]

Remote Inventory of GbEthernet SFP module on ISA ES4 board is not available.

[17]

RQ2/Q2 is not managed on Node Network mode

[18]

MSP protection on P4S4N board 2nd drawer are not available

[19]

AU-4 16c is available only with slim STM-16 port and STM-64 port

[20]

NGI monitoring feature does not work when the node is in free-running status

10


53/56

2.14. RELEASE 5.2B11: RESTRICTIONS REMOVED t n t e o c s n u i L h s t t f n l e o e t t g n a c n o l i y c A p s t m o i c f o r d o f n n n a i o i o t n t a o a c z i g i r n n u o i h s m t s a m u a P o n . c e d d t e n t i v a r r w e e t s s u e r u o , h s t t i t h n w e g i d r m e l u t l c t A o i d m r e p

None

2.15. RELEASE 5.2B11: PROCEDURES TO BE FOLLOWED & WARNINGS

ED

[1]

Before to delete the synchronization source, release all active commands

[2]

In order to have the fully capability of the system, after a power up or pull–in of the EQUICO and EPS Matrix, it’s necessary to wait 10 minutes

[3]

Removal of EPS/MSP protection has to be done with Main Board actives

[4]

MS-SPRING: matrix EPS has to be executed in synchronization locked mode for hitless switch.

[5]

FAN Shelf Alarm Cable has to be connected to CONGI-A board.

[6]

Path trace identifier (TIM) on TCT in repeat-byte mode is not managed even if it is reported on CT.

[7]

G-ETH: only the two upper optical drawer of Access board are available when used in conjunction with ISA Ethernet card.

[8]

On VC12 terminated paths TCT alarms and PM are available after enabling the consequent action.

[9]

SW activation can be performed from Rel. 4.4B6 and 5.2A.

[10]

Virtual concatenated groups can inter-work only if LCAS protocol is either enable or disable on both end sides

[11]

In order to change configuration from VC12-xv to VC3-xv and on ISA ES1 the following procedure must be followed: a.

Delete cross connection of VCX-xv;

b.

Set idle status to all VC of the VCX-xv and disable LCAS;

c.

Delete VCX-xv port configuration;

d.

Create new VCX-xv port configuration;

e.

Enable LCAS configuration and set active status to the VCX-xv;

f.

Create new cross-connection of VCX-xv

[12]

The first installation of ES1, ES4 and ES16 extended package is managed only after activation of release 5.2B.

[13]

Traffic impact of 1sec is expected on ISA GbE board during migration to release 5.2.

10


54/56


ED

[14]

ISA Ethernet main board: in order to be able to configure the board it is necessary to wait until it is active: the status can be verified either on the led on the front panel or via the watch icon on craft terminal. The time necessary to complete the activation is depending on the number of ISA Eth boards equipped in the shelf. For example: 1xISA Ethernet board: 25 minutes; 2 ISA Ethernet boards: the first board becomes active after 40 minutes and the second after 50; 3 ISA Ethernet boards: the first board becomes active after 55 minutes, the second after 65 and the third after 75.

[15]

ISA GbE main board: in order to be able to configure the board it is necessary to wait until it is active: the status can be verified either on the led on the front panel or via the watch icon on craft terminal. The time necessary to complete the activation is depending on the number of ISA GbE boards equipped in the shelf. For example: 1xISA GbE board: 40 minutes; 2 ISA GbE boards: the first board becomes active after 60 minutes and the second after 80; 3 ISA GbE boards: the first board becomes active after 80 minutes, the second after 100 and the third after 120.

[16]

In 2F MS-SPRING before powering on a NE is mandatory to perform a double forced switch ring on the adjacent nodes, facing the switched off NE. These commands can be released only when the NE start-up procedure is successfully completed.

[17]

EPS N+1 protection on P16S1_E4 board time switching is about 180 ms

[18]

When the spare board of EPS N+1 group of P16S1_E4 is active due to a equipment failure and the second failure of another P16S1_E4 board in the same protection group and inserted into a slot between main port and spare port occurs, before replacing the second failed board is recommended to repair the first otherwise hit of about 8 ms on protected traffic happen when the board is plugged out and again 24 ms when is plugged in.

[19]

Change configuration of board P16S1_E4 from Electrical to Optical Access port is also necessary to de-configure and re-configure the port P16S1_E4.

[20]

2F MS-SPRING: plug in of STM64 board causes a double traffic hit when the WTR is set to a value <180 sec.

[21]

Migration from release 5.2Ax/5.2Bx (x <3) to 5.2.B7 errors appear on electrical path on board P16S1_E4

[22]

Byte F1 of related RS section cannot be used when F3 Overhead of VC4 terminated on matrix is configured and byte 3,2 of RS Overhead cannot be used when MS passthrough is configured.

[23]

Board S4.1, L4.1, P4S1, S16.1, S16.2, L16.1, L16.2 (former Cristallo version <3) is not managed.

[24]

If an internal loopback and continue is created on STM-16 port (8-TE wide) and at the same time a LOS is present on this interface, sometimes errors or AIS is reported on some E1 or E3 cross-connected to this STM-16 interface.

[25]

SW migration from release 4.2Bx to 5.2B11 causes connections lost in CO-16 board

10


55/56

1660SM Release Notes.pdf

Recommend Documents