Operator Handbook

CONTENTS

GENERAL INFORMATION .................................................................................................. 15 INTRODUCTION................................................................................................................................. 15 CONVENTIONS USED IN THIS HANDBOOK .................................................................................. 15 SYSTEM ARCHITECTURE ................................................................................................................ 16 Local Craft Terminal: Local Connection ........................................................................................... 16 Local Craft Terminal: Remote Login ................................................................................................ 17 Element Manager Plug-in................................................................................................................. 18 SOFTWARE FEATURES ................................................................................................................... 19 NE Configuration (ADM-4) (ADM-16) .............................................................................................. 19 Unit Management ............................................................................................................................. 19 Access Management........................................................................................................................ 19 Equipment Configuration Management ........................................................................................... 19 Maintenance Management............................................................................................................... 20 Fault Management............................................................................................................................ 20 SYSTEM COMPOSITION................................................................................................................... 20 Local Craft Terminal Hardware Composition................................................................................... 20 Local Craft Terminal Software Composition .................................................................................... 20

ACTIVATING THE LOCAL CRAFT TERMINAL..................................................................21 CONNECTION OF THE PERSONAL COMPUTER .......................................................................... 21 SOFTWARE INSTALLATION............................................................................................................. 22 ACCESS THE LOCAL CRAFT TERMINAL SOFTWARE ................................................................. 22 CONFIGURATION OF COMMUNICATION PARAMETERS ............................................................ 23

MAIN FUNCTIONS.................................................................................................................25 MENU BAR AND MENUS .................................................................................................................. 25 GRAPHICAL AREA............................................................................................................................. 26 ALARM SUMMARY............................................................................................................................. 27 TOOL BAR........................................................................................................................................... 28 The Connection Status Indication .................................................................................................... 29 Exit Button......................................................................................................................................... 29 Operator Access Button ................................................................................................................... 29 Script Execution Button .................................................................................................................... 29 Script Upload Button......................................................................................................................... 30 Synchronisation Configuration Button (ADM) .................................................................................. 30 Cross-connection / Labels Operations Button (ADM) .................................................................... 30 Ethernet Line Protection Button (ADM-16) (ADM-64)...................................................................... 30 Alarm/Event Log Button.................................................................................................................... 30

COPYRIGHT - Refer To Title Page

339-1268/06

.

Navigation Page

Book Contents

MSHXXX - OPERATOR’S HANDBOOK CONTENTS

Performance Button.......................................................................................................................... 30 Help Button ....................................................................................................................................... 30 ALARM AND EVENT MONITOR WINDOW ...................................................................................... 31 PROGRESS BAR................................................................................................................................ 31

FILE AND SECURITY............................................................................................................33 LOGIN.................................................................................................................................................. 33 Local Access..................................................................................................................................... 33 Remote Access................................................................................................................................. 34 LOGOUT.............................................................................................................................................. 34 EXIT ..................................................................................................................................................... 34 LC SETTINGS ..................................................................................................................................... 34 General Settings ............................................................................................................................... 34 Alarm Settings................................................................................................................................... 36 Alarm Colours ................................................................................................................................... 36 Ground Contact Alarm Name........................................................................................................... 37 CHANGE PASSWORD....................................................................................................................... 38

CONFIGURATION AND INVENTORY .................................................................................40 SYSTEM SETUP: INFO...................................................................................................................... 40 SYSTEM SETUP: PROTOCOL.......................................................................................................... 41 SYSTEM SETUP: DCC....................................................................................................................... 41 SYSTEM SETUP: FILES DOWNLOAD ............................................................................................. 42 SYSTEM SETUP: FILES UPLOAD (ADM-16) (REG-4/16) (ADM-64) (REG-64).............................. 43 SYSTEM SETUP: ROUTING TABLES (ADM-16) (REG-4/16) (ADM-64) (REG-64)........................ 44 CROSS CONNECTIONS (ADM) ........................................................................................................ 46 Cross Connections: Multiply SDH Frame (ADM-4) ......................................................................... 47 Cross Connections: Bidirectional ..................................................................................................... 49 Cross Connections: Unidirectional ................................................................................................... 50 Cross Connections: Broadcast......................................................................................................... 50 Cross Connections: Loopback ......................................................................................................... 51 Cross Connections: Concatenated .................................................................................................. 52 Cross Connections: Drop and Continue (ADM-4) (ADM-16) .......................................................... 53 Cross Connections: Path Info........................................................................................................... 54 How to Create a Cross connection .................................................................................................. 55 Cross Connections: SNC Protection Configuration ......................................................................... 58 Cross Connections: SNC Protection Switch .................................................................................... 60 AUTOMATIC CIRCUIT TEST (ADM-16) (ADM-64) ........................................................................... 61 LABEL OPERATIONS CONFIGURATION (ADM)............................................................................. 62 Label Operations: Cross Connections Management....................................................................... 63 Labels Operations: DCCs Management .......................................................................................... 67 Labels Operations: System Synchronisation Management............................................................. 68 Labels Operations: Synchronisation Output Management.............................................................. 68 Labels Operations: Performance Data Management ...................................................................... 68


339-1268/06

.

Navigation Page

2

Book Contents


MSP PROTECTION (ADM) ................................................................................................................ 68 ETHERNET LINE PROTECTION (ADM-16)(ADM-64)...................................................................... 69 EQUIPMENT PROTECTION (ADM) .................................................................................................. 70 SYSTEM SYNCHRONISATION SOURCES (ADM).......................................................................... 73 System Synchronisation Switch Operations .................................................................................... 77 SYNCHRONISATION OUTPUTS (ADM)........................................................................................... 78 Synchronisation Output Switch Operations ..................................................................................... 82 SYNCHRONISATION OUTPUT QUALITY (ADM) ............................................................................ 83 GROUND CONTACTS ....................................................................................................................... 83 MS-SPRING (ADM)............................................................................................................................. 86 MS-SPRing Configuration ................................................................................................................ 87 MS-SPRing Cross Connection......................................................................................................... 89 MS-SPRing NUT .............................................................................................................................. 90 SOFTWARE INVENTORY.................................................................................................................. 92 HARDWARE INVENTORY................................................................................................................. 93 CHANNEL OVERWIEW (ADM).......................................................................................................... 93 TERMINATION POINT LABELS (ADM)............................................................................................. 96

MAINTENANCE AND FAULT MANAGEMENT...................................................................99 TEST MODE........................................................................................................................................ 99 SOFTWARE DOWNLOAD ................................................................................................................. 99 BANK SWITCH.................................................................................................................................. 101 SOFTWARE COMMIT ...................................................................................................................... 101 MIB RESET ....................................................................................................................................... 101 MIB UPLOAD .................................................................................................................................... 101 SCRIPT EXECUTION ....................................................................................................................... 102 REALIGN SHELF .............................................................................................................................. 103 ALARM LOG REPORTING............................................................................................................... 103 LOG SETUP ...................................................................................................................................... 104 LOG RECORDS................................................................................................................................ 105 ALARM REPORTING ....................................................................................................................... 106 ALARM SEVERITY ........................................................................................................................... 107 CLEAR WINDOW ALARMS ............................................................................................................. 108 ACTIVE ALARMS.............................................................................................................................. 108

UNIT FUNCTIONS ...............................................................................................................109 COMMON FUNCTIONS: CREATE .................................................................................................. 109 COMMON FUNCTIONS: ALARMS .................................................................................................. 111 COMMON FUNCTIONS: ALARM SEVERITY ................................................................................. 112 COMMON FUNCTIONS: DELETE................................................................................................... 113 COMMON FUNCTIONS: UNIT RESET ........................................................................................... 113 COMMON FUNCTIONS: BANK SWITCH........................................................................................ 113 COMMON FUNCTIONS: SOFTWARE COMMIT ............................................................................ 113 COMMON FUNCTIONS: PROPERTY............................................................................................. 114


339-1268/06

.

Navigation Page

3

Book Contents


SPECIFIC FUNCTIONS: MIB RESET.............................................................................................. 114 SPECIFIC FUNCTIONS: MIB UPLOAD........................................................................................... 114 SPECIFIC FUNCTIONS: MAINTENANCE/SERVICE ..................................................................... 116 SPECIFIC FUNCTIONS: LAMP TEST ............................................................................................. 116 SPECIFIC FUNCTIONS: OUTPUT QUALITY (ADM)...................................................................... 116 SPECIFIC FUNCTIONS: LASER CONFIGURATION ..................................................................... 117 SPECIFIC FUNCTIONS: MSP PROTECTION (ADM)..................................................................... 118 MSP Switch Operations (ADM)...................................................................................................... 119 SPECIFIC FUNCTIONS: EQUIPMENT PROTECTION (ADM)....................................................... 120 SPECIFIC FUNCTIONS: MS-SPRING (ADM) ................................................................................. 121 Specific Functions: MS-SPRing Manual Command/BSHR Status ............................................... 121 Section Status Info.......................................................................................................................... 125 West/East Info................................................................................................................................. 125 Specific Functions: MS-SPRing Cross Connection ....................................................................... 126 Specific Functions: MS-SPRing NUT............................................................................................. 126 SPECIFIC FUNCTIONS: GROUND CONTACTS............................................................................ 128 SPECIFIC FUNCTIONS: SYSTEM RESTART ................................................................................ 128 SPECIFIC FUNCTIONS: PORTS SETUP (ADM)............................................................................ 128 LOOPBACK....................................................................................................................................... 129 TANDEM CONNECTION (ADM) ...................................................................................................... 131 Tandem Connection Configuration ................................................................................................131 SPECIFIC FUNCTIONS: CHANNELS - STM-N UNITS/WDM STM-16/DWDM STM-16/METRO STM-16/DWDM STM-64 ................................................................................................................... 133 STM-n Units Loopback Management ............................................................................................ 141 STM-n Units Performance Data ..................................................................................................... 141 STM-n Units Alarm Management...................................................................................................142 STM-n Units TC Management (ADM)............................................................................................ 142 SPECIFIC FUNCTIONS: CHANNELS - NX140/155MBIT/S TRIBUTARY UNITS (ADM).............. 142 nx140/155Mbit/s Units Loopback Management ............................................................................ 157 nx140/155Mbit/s Units Performance Data ..................................................................................... 157 nx140/155Mbit/s Units Alarm Management................................................................................... 158 nx140/155Mbit/s Units TC Management........................................................................................ 158 SPECIFIC FUNCTION: CHANNELS - 3X45MBIT/S AND 3X34MBIT/S TRIBUTARY UNITS (ADM4) ........................................................................................................................................................ 158 34-45Mbit/s Units Loopback Management .................................................................................... 160 34-45Mbit/s Units Performance Data .............................................................................................160 34-45Mbit/s Units Alarm Management........................................................................................... 160 SPECIFIC FUNCTIONS: CHANNELS - 2MBIT/S TRIBUTARY UNITS (ADM-4)........................... 160 2Mbit/s Units Loopback Management............................................................................................ 162 2Mbit/s Units Performance Data .................................................................................................... 162 2Mbit/s Units Alarm Management .................................................................................................. 163 SPECIFIC FUNCTIONS: OPTICAL MEASURE - BOOSTER AND PREAMPLIFIER UNIT .......... 163 Booster and Preamplifier Units Performance Data........................................................................ 164 Booster and Preamplifier Units Alarm Management ..................................................................... 164


339-1268/06

.

Navigation Page

4

Book Contents


SPECIFIC FUNCTIONS: CHANNELS - STM-16 FOR VC-4-4C/4V AND 16C/16V (ADM-64) (ADM16) ...................................................................................................................................................... 165 STM-16 for VC-4-4c/4v and 16c/16v Unit Performance Data ....................................................... 168 STM-16 for VC-4-4c/4v and 16c/16v Unit Alarm Management..................................................... 169 Delay setting ................................................................................................................................... 169 SPECIFIC FUNCTIONS: CHANNELS - GIGABIT ETHERNET UNITS (ADM-16) (ADM-64) ........ 169 Gigabit Ethernet Unit Performance Data........................................................................................ 176 Gigabit Ethernet Loopback Management ...................................................................................... 176 Gigabit Ethernet Alarm Management............................................................................................. 176 SPECIFIC FUNCTIONS: CHANNELS - AUXILIARY UNIT ............................................................. 177 EOW Channels............................................................................................................................... 177 Auxiliary Channels .......................................................................................................................... 181 DAM UNIT CONFIGURATION .........................................................................................................182 Input Collector................................................................................................................................. 182 Output Collector.............................................................................................................................. 184 8XFAST ETHERNET UNIT COMMISSIONING............................................................................... 185 8XFAST ETHERNET UNIT: UNIT CONFIGURATION.................................................................... 186 8xFast Ethernet Unit: Ethernet Ports Configuration folder............................................................. 186 8xFast Ethernet Unit: Groups Configuration folder........................................................................ 191 8xFast Etherent Unit: Bandwidth Allocation folder......................................................................... 195 8xFast Etherent Unit: Port folder .................................................................................................... 198

PERFORMANCE..................................................................................................................202 PERFORMANCE: ALL PERFORMANCES ..................................................................................... 202 PERFORMANCE MANAGEMENT: THRESHOLD PROFILES ...................................................... 211 LOCAL ETHERNET DATA PERFORMANCE ................................................................................. 214 REMOTE ETHERNET DATA PERFORMANCE.............................................................................. 217 QUEUE ETHERNET DATA PERFORMANCE ................................................................................ 220

CONFIGURATION FILES....................................................................................................222 OSI CONFIGURATION..................................................................................................................... 222 CHANGING THE OSI PROTOCOL PARAMETERS ....................................................................... 223 OSI.INI FILE FOR COMMUNICATION AND CONTROL UNIT TYPE C......................................... 223 OSID.INI FILE FOR COMMUNICATION AND CONTROL UNIT TYPE D...................................... 224 PARAMETERS OF OSI.INI FILE...................................................................................................... 226 Transport Layer .............................................................................................................................. 226 Network Layer................................................................................................................................. 228 Operative Indications ...................................................................................................................... 237 Examples ........................................................................................................................................ 239 DESCRIPTION OF AGENT.CNF FILE............................................................................................. 254 MAIN section................................................................................................................................... 255 CONFIG section ............................................................................................................................. 256 B_INTERFACE section .................................................................................................................. 257 LAMP section.................................................................................................................................. 257


339-1268/06

.

Navigation Page

5

Book Contents


FAULT DETECTION PROCEDURE ...................................................................................258 ALARM TYPES ................................................................................................................................. 260 AU4: n AIS ...................................................................................................................................... 260 AU4: n DEG .................................................................................................................................... 261 AU4: n EXC .................................................................................................................................... 262 AU4: n LOP..................................................................................................................................... 263 AU4: n RDI...................................................................................................................................... 263 AU4: n TIM...................................................................................................................................... 264 AU4: n UNEQ ................................................................................................................................. 264 Buffer Overflow ............................................................................................................................... 264 DC/DC 1 Fault ................................................................................................................................ 265 DC/DC 2 Fault ................................................................................................................................ 265 DCC-x: n LAPD Disconnected ....................................................................................................... 265 Disparity Fail ................................................................................................................................... 265 Ethernet Link Down ........................................................................................................................ 266 Fan Assy Absent............................................................................................................................. 266 Fan Fail ........................................................................................................................................... 266 FEC_DEGRADE............................................................................................................................. 267 General Supply Fail ........................................................................................................................ 267 High Temperature........................................................................................................................... 267 Laser Bias Out ................................................................................................................................ 267 Laser Pwr Out................................................................................................................................. 268 Laser Tmp Out................................................................................................................................ 268 Laser Tx Power Thr High................................................................................................................ 268 Laser Tx Power Thr Low ................................................................................................................ 268 Loss of Multi Frame ........................................................................................................................ 269 Loss of Sequencing ........................................................................................................................ 269 LTU w Fail....................................................................................................................................... 269 Missing Unit .................................................................................................................................... 271 MS OH: n DISP FAIL...................................................................................................................... 271 MS OW: n DISP FAIL..................................................................................................................... 272 MS: n AIS........................................................................................................................................ 273 MS: DAC ......................................................................................................................................... 273 MS: n DEG...................................................................................................................................... 273 MS: n EXC ...................................................................................................................................... 274 MS: IAC........................................................................................................................................... 274 MS: INV........................................................................................................................................... 274 MS: NIM .......................................................................................................................................... 275 MS: PAM......................................................................................................................................... 275 MS: n RDI ....................................................................................................................................... 275 MS: SCM......................................................................................................................................... 276 MS: TMOUT.................................................................................................................................... 276 OCH-AIS ......................................................................................................................................... 276 OCH-LOF........................................................................................................................................ 277


339-1268/06

.

Navigation Page

6

Book Contents


OCH-LOM....................................................................................................................................... 277 OTU-TIM......................................................................................................................................... 277 OTU-BDI ......................................................................................................................................... 277 OTU-SSF ........................................................................................................................................ 278 ODU-AIS ......................................................................................................................................... 278 ODU-BDI......................................................................................................................................... 278 ODU-SSF........................................................................................................................................ 278 ODU-OCI ........................................................................................................................................ 279 ODU-TIM......................................................................................................................................... 279 ODU-PLM ....................................................................................................................................... 279 OH Bus Rx Fail ............................................................................................................................... 279 OH Bus Tx Fail ............................................................................................................................... 280 OR Batt ........................................................................................................................................... 280 Plug Module Missing ...................................................................................................................... 280 Protection State Unstable............................................................................................................... 280 Protection State Mismatch.............................................................................................................. 280 Power Fail ....................................................................................................................................... 281 QI/F Link Down ............................................................................................................................... 281 Received Power High Low ............................................................................................................. 281 RS OH: n Disp Fail ......................................................................................................................... 282 RS OW: n Disp Fail......................................................................................................................... 282 RS UC: n Disp Fail.......................................................................................................................... 283 RS: 1 DEG ...................................................................................................................................... 283 RS: 1 EXC....................................................................................................................................... 283 RS: n LOF ....................................................................................................................................... 284 RS: n TIM........................................................................................................................................ 284 Sync Fail ......................................................................................................................................... 284 T. PDH: n AIS ................................................................................................................................. 285 T. PDH: n DEG ............................................................................................................................... 285 T. PDH: n DEG (In – Faw).............................................................................................................. 285 T. PDH: n DEG (In - CRC-4) .......................................................................................................... 286 T. PDH: n EXC................................................................................................................................ 286 T. PDH: n EXC (In – Faw) .............................................................................................................. 287 T. PDH: n EXC (In - CRC-4)........................................................................................................... 287 T. PDH: n LOF ................................................................................................................................ 287 T. PDH: n LOF (In).......................................................................................................................... 288 T. PDH: n LOS................................................................................................................................ 288 T. PDH: n CRC-4 mismatch (In)..................................................................................................... 288 T. PDH: n RAI (In)........................................................................................................................... 288 T. PDH: n AIS (Out) ........................................................................................................................ 289 T. PDH: n DEG (Out - CRC-4) ....................................................................................................... 289 T. PDH: n EXC (Out - CRC-4)........................................................................................................ 289 T. PDH: n LOF (Out)....................................................................................................................... 290 T. PDH: n CRC-4 mismatch (Out).................................................................................................. 290 T. PDH: n Tx Fail ............................................................................................................................ 290


339-1268/06

.

Navigation Page

7

Book Contents


T. SDH: n LOS................................................................................................................................ 291 TC: n DEG ...................................................................................................................................... 291 TC: n EXC....................................................................................................................................... 291 TC: n IncAIS.................................................................................................................................... 292 TC: n UNEQ.................................................................................................................................... 292 TUy: n-k-l-m AIS ............................................................................................................................. 293 TUy: n-k-l-m DEG ........................................................................................................................... 293 TUy: n-k-l-m EXC............................................................................................................................ 293 TUy: n-k-l-m LOP............................................................................................................................ 294 Tx Fail ............................................................................................................................................. 294 Unit Fail ........................................................................................................................................... 294 Unit Type Mismatch........................................................................................................................ 294 VC4: n DEG .................................................................................................................................... 295 VC4: n EXC .................................................................................................................................... 295 VC4: n LOM .................................................................................................................................... 296 VC4: n PLM .................................................................................................................................... 296 VC4: n RDI...................................................................................................................................... 297 VC4: n TIM...................................................................................................................................... 297 VC4: n UNEQ ................................................................................................................................. 297 VCy: n DEG .................................................................................................................................... 298 VCy: n EXC..................................................................................................................................... 298 VCy: n PLM..................................................................................................................................... 299 VCy: n RDI ...................................................................................................................................... 299 VCy: n TIM...................................................................................................................................... 300 VCy: n UNEQ.................................................................................................................................. 300 Wavelength drift.............................................................................................................................. 300 Wavelengthmis_LaserOff ............................................................................................................... 300 COMMON PROCEDURES............................................................................................................... 301 Unit Internal Fault Trouble-Shooting Procedure ............................................................................ 301 PDH LOS Fault Trouble-Shooting Procedure................................................................................ 301 SDH LOS Fault Trouble-Shooting Procedure................................................................................ 301 Preamplifier and Booster LOS Fault Trouble-Shooting Procedure ............................................... 302 Bit Error Rate on the STM-N Optical Signal (MS-EXC/DEG and RS-EXC/DEG)......................... 302 Bit Error Rate on the PDH and STM-1 Electrical Signal (PDH EXC/DEG and MS EXC/DEG).... 303 Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG) .......................................... 304 Input Ground Contact ..................................................................................................................... 304 EQUIPMENT EVENTS ..................................................................................................................... 305 8XFAST ETHERNET UNIT ALARMS .............................................................................................. 310 Ethernet Port Alarms ...................................................................................................................... 310 VCG Alarms.................................................................................................................................... 311 VC-n Alarms.................................................................................................................................... 312

ERROR MESSAGES ...........................................................................................................316 INVALID INI FILE............................................................................................................................... 316 WRONG IDM..................................................................................................................................... 316


339-1268/06

.

Navigation Page

8

Book Contents


ENABLE SWITCH UNIT FIRST!....................................................................................................... 316 DISABLE PATH PROTECTION FIRST!........................................................................................... 316 INVALID FILE .................................................................................................................................... 316 IT'S IMPOSSIBLE TO DELETE THE UNIT. IT'S SYNCHRONISATION SOURCE ....................... 316 IT'S IMPOSSIBLE TO DELETE THE UNIT. DCC ACTIVE ............................................................. 316 CANNOT DELETE UNIT: USED IN BSHR PROTECTION............................................................. 316 CANNOT DELETE MATRIX: EQUIPMENT PROTECTION IN MANUAL/FORCED/LOCKOUT ... 316 CANNOT DELETE UNIT: USED IN MSP PROTECTION ............................................................... 316 CANNOT DELETE UNIT: USED IN EQUIPMENT PROTECTION ................................................. 316 MODULE VERSION JUST UPDATE ............................................................................................... 316 WRONG SERVER! ........................................................................................................................... 317 BOOT/ACTIVE VERSION MISMATCH. COMMIT REQUIRED! ..................................................... 317 SOFTWARE VERSION JUST PRESENT!....................................................................................... 317 SOFTWARE MODULE NOT SELECTED........................................................................................ 317 UNIT TYPE NOT PRESENT............................................................................................................. 317 CODE FILE NOT FOUND!................................................................................................................ 317 ERROR READING CODE FILE ....................................................................................................... 317 ERROR STORING RECORD DATA................................................................................................ 317 WRONG RECORD SEQUENCE NUMBER .................................................................................... 317 TIME OUT ON REPLY...................................................................................................................... 317 STAND-BY VERSION UNAVAILABLE............................................................................................. 317 OPERATION NOT ALLOWED ......................................................................................................... 317 COMMIT FAILED! ............................................................................................................................. 317 DEMULTIPLEXING UNAVAILABLE!................................................................................................ 317 INPUT DATA MISSING..................................................................................................................... 318 WRONG DATA.................................................................................................................................. 318 OUTPUT DATA MISSING................................................................................................................. 318 TIME OUT.......................................................................................................................................... 318 INSUFFICIENT PRIVILEGE ............................................................................................................. 318 OUT OF SEQUENCE COMMAND................................................................................................... 318 UNDEFINED ERROR ....................................................................................................................... 318 NOT LOGGED IN.............................................................................................................................. 318 OPERATION FAILURE..................................................................................................................... 318 IF CONFIGURATION PERFORMED DURING MAINTENANCE STATE IS DIFFERENT FROM THE PREVIOUS ONE, A SYSTEM RESTART MAY BE NECESSARY IN ORDER TO CORRECTLY ACTIVATE THE NEW SETTINGS OVER THE TRAFFIC UNITS........................... 318 “DATA” OUT OF BOUNDS MIN=”MIN” MAX=”MAX” ...................................................................... 318 "DATA” IS AN INVALID NUMERIC FORMAT.................................................................................. 318 OPERATION ABORTED................................................................................................................... 318 MISSING INPUT DATA..................................................................................................................... 318 MISSING OUTPUT DATA................................................................................................................. 319 NOT IMPLEMENTED........................................................................................................................ 319 TIMEOUT EXPIRED ......................................................................................................................... 319 PROTOCOL ERROR ........................................................................................................................ 319 NO PRIVILEGE ................................................................................................................................. 319


339-1268/06

.

Navigation Page

9

Book Contents


OUT OF SEQUENCE ....................................................................................................................... 319 INVALID OPERATION ...................................................................................................................... 319 FAILURE : LOGICAL PROBLEM ..................................................................................................... 319 FAILURE : PHYSICAL PROBLEM ................................................................................................... 319 FAILURE : XCONN/PATH/MSP/AUX CONN PRESENT ................................................................ 319 FAILURE : ACTIVE PERFORMANCES FOUND ON PORT........................................................... 319 FAILURE : UNKNOWN CODE .........................................................................................................319 PASSWORD CHECK FAILURE : PLEASE RE-ENTER.................................................................. 319 REMOTE CONNECTION DOWN: DISCONNECT FROM LC AND WAIT 2 MINUTES. THEN LOGIN AGAIN. .................................................................................................................................. 320 DISCONNECT FROM EQUIPMENT BEFORE ............................................................................... 320 REMOTE CONNECTION FAILED. REMOTE LC UNREACHABLE............................................... 320 REMOTE CONNECTION FAILED: ATTEMPTED REMOTE CONNECTION ON LOCAL SHELF320 WRONG PASSWORD...................................................................................................................... 320 LOGIN FAILED: LC RETURNED CODE “CODE”............................................................................ 320 TWO CONNECTIONS ON THE SAME PORT AND SAME BYTE ................................................. 320 RINGMASTER NEED A CAI DESTINATION................................................................................... 320 TYPE CONNECTION ALREADY PRESENT ON THIS EOW......................................................... 320 AUXILIARY UNIT OUT OR IN ERROR: OPERATION REJECTED. .............................................. 320 CONNECTION ALREADY PRESENT ON SAME ASIC, MUST USE SAME EXTERNAL PORT . 320 FAILURE : DCC CONNECTED FOUND OR AUXCON .................................................................. 320 GTP NOT AVAILABLE ON AU4 WITH MUX1 ................................................................................. 320 UNIT IN EQUIPMENT PROTECTION: THIS UNIT IS IN STANDBY.............................................. 321 CANNOT SWITCH ON: UNIT OUT OR FAILED ............................................................................. 321 CANNOT LOCKOUT PROTECTING: ONE O MORE UNIT OUT OR IN FAIL STATE.................. 321 MANUAL COMMAND ACTIVE ON THIS PROTECTION: RELEASE IT BEFORE DISMISS........ 321 “UNIT” NOT SUPPORTED FOR UNITS PROTECTION ................................................................. 321 NO EQUIPMENT AVAILABLE FOR EQUIPMENT PROTECTION ................................................ 321 NO MS AVAILABLE FOR MSP ........................................................................................................321 MSP DELETION. ARE YOU SURE ?............................................................................................... 321 COMMAND AVAILABLE ONLY ON PROTECTING........................................................................ 321 INVALID NODE ................................................................................................................................. 321 NODE ALREADY PRESENT............................................................................................................ 321 INVALID NSAP ADDRESS LENGTH MIN 8 - MAX 20 DIGITS ...................................................... 321 LAST DIGITS MUST BE 01 .............................................................................................................. 321 UNKNOWN EQUIPMENT TYPE...................................................................................................... 321 UNIT WITH MULTIPLIED PORT. DEMULTIPLY BEFORE BUILD SPRING PROTECTION ........ 322 UNIT WITH GROUPED PORTS. UNGROUP IT BEFORE BUILD SPRING PROTECTION......... 322 UNIT WITH PORT CONNECTED ON SPRING PROTECTION SIDE. REMOVE IT BEFORE BUILD SPRING PROTECTION.................................................................................................................... 322 UNIT WITH BROADCAST TYPE CONNECTIONS PRESENT. REMOVE IT BEFORE BUILD SPRING PROTECTION.................................................................................................................... 322 RING NODES NOT CONFIGURED! ................................................................................................ 322 CANNOT BUILD BROADCAST CONNECTION WITH MORE THAN “N” LEGS........................... 322 REACHED MAX MATRIX ALLOCATION FOR THIS POSITION!................................................... 322


339-1268/06

.

Navigation Page

10

Book Contents


OUTPUT MESSAGE LENGTH TOO LONG .................................................................................... 322 OUTPUT CODED MESSAGE LENGTH TOO LONG...................................................................... 322 ERROR IN LINE “NUMLINE” : “STATEMENT” - “MESSAGE” ........................................................ 322 ALREADY LOGGED-IN .................................................................................................................... 322 INVALID TP TYPE............................................................................................................................. 322 INVALID ATTRIBUTE ASSIGNMENT.............................................................................................. 323 INVALID LOOP TYPE ....................................................................................................................... 323 INVALID PAYLOAD TYPE................................................................................................................ 323 INVALID KIND ................................................................................................................................... 323 UNKNOWN ALARM CAUSE ............................................................................................................323 INVALID ALARM TYPE .................................................................................................................... 323 INVALID ALARM ASSIGNMENT...................................................................................................... 323 ALARM NUMBER OUT OF RANGE ................................................................................................ 323 INVALID KIND FOR SLOT:............................................................................................................... 323 INVALID TIME FORMAT .................................................................................................................. 323 INVALID SLOT NUMBER ................................................................................................................. 323 INVALID PORT STRING................................................................................................................... 324 INVALID EQUIPMENT...................................................................................................................... 324 SLOT ALREADY EQUIPPED ........................................................................................................... 324 OPERATION NOT AVAILABLE........................................................................................................324 INVALID TP(S) .................................................................................................................................. 324 INVALID FROM TP(S) ...................................................................................................................... 324 INVALID TO TP(S) ............................................................................................................................ 324 INVALID PROT TP(S) ....................................................................................................................... 324 TP NOT CONNECTED ..................................................................................................................... 324 UNDEFINED MSP PROTECTION ................................................................................................... 324 INVALID INSTANCE ......................................................................................................................... 324 NO MANUAL COMMAND TO RELEASE ........................................................................................ 324 INVALID SOURCE STATUS ............................................................................................................ 325 INVALID LEVEL ................................................................................................................................ 325 UNIT NOT SUPPORTING MULTIPLY ............................................................................................. 325 PORT NOT AVAILABLE ................................................................................................................... 325 PORT CONNECTED OR GROUPED .............................................................................................. 325 WRONG TRAFFIC TYPE ................................................................................................................. 325 PORT NOT MULTIPLIED ................................................................................................................. 325 INVALID SYNCHRONISATION SOURCE ....................................................................................... 325 INVALID QUALITY LEVEL................................................................................................................ 325 INVALID SYNCHRONISATION GROUP ......................................................................................... 325 CAN'T ADD HOLDOVER.................................................................................................................. 325 CAN'T ADD SYSTEM ....................................................................................................................... 326 CAN'T DELETE HOLDOVER ........................................................................................................... 326 CAN'T DELETE SYSTEM................................................................................................................. 326 SYNC SOURCE NOT CONFIGURED ............................................................................................. 326 INVALID SPRING TYPE ................................................................................................................... 326 MAXIMUM LABEL LENGTH IS 8 ..................................................................................................... 326


339-1268/06

.

Navigation Page

11

Book Contents


LABEL NOT DEFINED...................................................................................................................... 326 CARD NOT EQUIPPED OR MISSING............................................................................................. 326 INVALID DCC TYPE ......................................................................................................................... 326 INVALID CARD TYPE OR PORT TYPE .......................................................................................... 326 INVALID CONNECTION TYPE ........................................................................................................326 UNEXPECTED TOKEN .................................................................................................................... 327 INVALID VALUE IN CSES THRESHOLD ........................................................................................ 327 INVALID VALUE IN ALARM THRESHOLD ..................................................................................... 327 PORT ALREADY MULTIPLIED........................................................................................................327 INVALID SS BYTE ............................................................................................................................ 327 SOCKET CALL FAILED.................................................................................................................... 327 NO LOCKOUT COMMAND TO RELEASE...................................................................................... 327 FAILURE : CROSS CONNECTION OR PORT GROUP FOUND................................................... 327 FAILURE : AUXILIARY CROSS CONNECTION FOUND ............................................................... 327 FAILURE : DCC ENABLED FOUND OR AUXCON......................................................................... 327 FAILURE : MSP/SPRING PROTECTION FOUND.......................................................................... 327 FAILURE : EQUIPMENT PROTECTION FOUND ........................................................................... 327 FAILURE : SYNC SOURCE FOUND ............................................................................................... 328 FAILURE : MANUAL SWITCH ON EQUIPMENT PROTECTION................................................... 328 ONE SIDE OF THIS CROSSCON IS ON EXTRA TRAFFIC SWITCHED OUT............................. 328 PLEASE DON'T EXTRACT THE UNIT AND WAIT FOR CONTROLLER REBOOT. .................... 328 ERROR IN THE DIMENSION OF PACKET..................................................................................... 328 TO COMPLETE LOCKOUT IT IS NECESSARY A SECOND LOCKOUT ON THE ADJACENT NODE ELSE, IN CASE OF PROBLEM ON THE RING, THE MS-SPRING SHOULD BE NOT CORRECT AND LOSE TRAFFIC..................................................................................................... 328 EXTRA TRAFFIC NOT AVAILABLE................................................................................................. 328 MATRIX UNITS INSERTED IN SHELF HAVE DIFFERENT HARDWARE TYPES, IN CASE OF SWITCH THIS MAY CAUSE LOSING OF TRAFFIC....................................................................... 328 MSP CONFIGURATION NOT ALLOWED ....................................................................................... 328 THE EQUIPMENT YOU ARE CONNECTED TO HAS DIFFERENT COMMITTED AND RUNNING SOFTWARE VERSION. REMEMBER TO PERFORM A GLOBAL COMMIT TO MAINTAIN RUNNING VERSION ........................................................................................................................ 328 MANUAL COMMAND ACTIVE ON THIS PROTECTION: CONTINUE ANYWAY?....................... 328 NO LINE CARDS AVAILABLE FOR MS SPRING........................................................................... 329 TIME OUT IN RESPONSE FROM SHELF: OK TO FORCE A LOGOUT NOW CANCEL TO IGNORE............................................................................................................................................. 329 AFTER LOCKING EFD THE STATE CHANGE MESSAGES ARE NOT NOTIFIED FROM THE EQUIPMENT AND THE PROTECTION AND SYNC STATUS WINDOWS ARE NOT UPDATED RUN-TIME." ....................................................................................................................................... 329 AFTER UNLOCKING EFD IS NECESSARY TO PERFORM A GENERAL EQUIPMENT REALIGNMENT USING REFRESH BUTTON IN THE MAIN VIEW".............................................. 329 INVALID MAC ADDRESS LENGTH MUST BE 6 DIGITS............................................................... 329 FILE “FILENAME” NOT FOUND OR EMPTY. PLEASE CHECK IT ............................................... 329 ANOTHER APPLICATION HAS CHANGED THE CDL FILE LOADED. DO YOU WANT TO RELOAD IT?...................................................................................................................................... 329 DOWNLOAD ABORTED .................................................................................................................. 329


339-1268/06

.

Navigation Page

12

Book Contents


DOWNLOAD RUNNING ................................................................................................................... 329 DOWNLOAD COMPLETED .............................................................................................................329 FOUND CHANNELS NOT MONITORED ........................................................................................ 329 MSP PROTECTION SWITCH; PLEASE RELOAD THIS MASK IN ORDER TO REFRESH DATA329 EQUIPMENT PROTECTION SWITCH; PLEASE RELOAD THIS MASK IN ORDER TO REFRESH DATA ................................................................................................................................................. 330 SPRING PROTECTION SWITCH; PLEASE RELOAD THIS MASK IN ORDER TO REFRESH DATA ................................................................................................................................................. 330 IT'S IMPOSSIBLE TO RENAME THIS ALARM ............................................................................... 330 FROM AND TO ARE EQUAL, DISCONNECT WILL CAUSE THE DELETION OF BROADCAST CROSS CONNECTION: CONTINUE?" ........................................................................................... 330 WARNING: FOUND SOME EXTRA TRAFFIC SWITCHED OUT; CHECK FOR CROSS CONNECTION DATA ON GENERATED CDL FILE........................................................................ 330

HOW TO................................................................................................................................331 PROCEDURE TO EXECUTE A DATABASE DOWNLOAD............................................................ 331


339-1268/06

.

Navigation Page

13

Book Contents

GENERAL INFORMATION INTRODUCTION The equipment is connected to the Control Application which allows its management for monitoring and configuration operations. The equipment control system functions are provided by the software resident in the Communication and Control Unit fully supporting the Information model (*). The Control Application can be: n the Local Craft Terminal (LCT): it is a software application running on a personal computer (based on MS Windows operating system) with a serial connection to the equipment. n Plug-in: it is a software application, part of the Element Manager program, running on a HP server (based on Unix operating system) able to offer a Graphical User Interface for controlling the equipment.

CONVENTIONS USED IN THIS HANDBOOK The symbol (ADM) indicates that the relevant option is available only for the ADM equipment. The symbol (ADM-4) indicates that the relevant option is available only for the ADM-4 equipment. The symbol (ADM-16) indicates that the relevant option is available only for the ADM-16 equipment. The symbol (ADM-64) indicates that the relevant option is available only for the ADM-64 equipment. The symbol (REG) indicates that the relevant option is available only for the REG equipment. The symbol (REG-4/16) indicates that the relevant option is available only for the REG-4/16 equipment. The symbol (REG-64) indicates that the relevant option is available only for the REG-64 equipment. The symbol [LC] indicates that the relevant option is available only in the LCT application and it can not be managed by the relevant plug-in. All the figures shown in this Handbook are examples; they do not refer to specific equipment. Note(*)

The equipment Information Model is compliant to the following specification: ITU-T M.3010, M.3100, G.707, G.708, G.709, G.774, G.774-01, G.774-02, G.774-03, G.774-04, G.774-05, G.781, G.782, G.783, G.784, G.803, Q.821, Q.822, X.700, X.701, X.710, X.711, X.720, X.721, X.722, X.730, X.731, X.733, X.734, X.735, X.737, X.738, X.739, X.745, G.744-01, G.826 ETSI DE/TM-2201, DE/TM-2208, RE/TM-2213, RE/TM 2213-1, RE-TM-2229, DE/SPS-3014.1


339-1268/06

.

Navigation Page

Book Contents

MSHXXX - OPERATOR’S HANDBOOK GENERAL INFORMATION

SYSTEM ARCHITECTURE Local Craft Terminal: Local Connection It can control the equipment via a local connection. The dialogue between the Control Application and the controlled Network Element (see Fig. 1) is based on a F-Interface with transport protocol fully supporting the information model and based on V.24 interface (RS232 link).

Fig. 1 Local Control using the Control Application


339-1268/06

.

Navigation Page

16

Book Contents


Local Craft Terminal: Remote Login The Remote Login option permits the management of an equipment via the SDH Data Communication Channel using the routing function of a NE locally connected (Fig. 2).

Control Application PERSONAL COMPUTER

LAN Control Application software

NE

F Interface

Q Interface

NE

DCC

DCC

NE

NE

DCC

DCC

NE

Fig. 2 Remote Control using the Control Application (Ring Network example)


339-1268/06

.

Navigation Page

17

Book Contents


Element Manager Plug-in The operator can manage all the network elements belonging to the controlled network using the facilities provided by the Element Manager application. The Element Manager consists of two main parts: n a core module provides all the common functions shared by all the plug-in applications; n plug-in modules, one for each network element type, provide the specific control functions for each equipment. The controlled network elements are connected to the Element Manager application by means of a Data Communication Network (DCN) based on ISO/OSI protocol.

HP SERVER CORE

EM-IMO Plug-in

EM-11C Plug-in

EM-xx Plug-in

DCN

DXC ADM

DXC

ADM xx NE

Fig. 3 Centralized Manager

xx NE

Control

using

the

Element

For information regarding the installation and process description refer to the Element Manager manual. Refer To: ServiceOn Optical Element Manager Manual


339-1268/06

.

Navigation Page

18

Book Contents


SOFTWARE FEATURES The following functions are performed by the Control Application.

NE Configuration (ADM-4) (ADM-16) The equipment can be configured as either ADM or Regenerator. By modifying the AGENT.cnf file, the operator can change the default configuration (ADM) and use the equipment as Regenerator.

Unit Management Manages for each electronic Unit the following functions: n Configuration Management; n Active Alarm Report; n Performance Management; n Utilities.

Access Management It manages the following functionality: n Operator Access Rights [LC]; n Equipment Password Management [LC].

Equipment Configuration Management It groups together all sub-applications for the management of: n Cross Connection Management (ADM); n Line Protection Configuration (ADM); n Network Protection Configuration (ADM); n Equipment Protection (ADM); n Equipment Synchronisation Management (ADM); n Network Address Management; n Date and Time Configuration. Cross connection management deals with cross connections and path protection. Cross connections configuration defines how the incoming/outgoing traffic should be multiplexed/demultiplexed and allocated to/taken from the channels of the STM-N frame Virtual Containers (VC). Each channel is identified by an acronym that indicates the type and position of traffic, the connection can be unidirectional, bidirectional, broadcast type or loopback. Line protection configuration perform configuration of the Multiplex Section Protection parameters. Network protection configuration perform configuration of the SNC Protection and Multiplex Section Shared Ring Protection parameters. Equipment protection configures the parameters of the Switch Unit or Tributary 1:N or 1+1 protection parameters. Equipment synchronisation enables the management of equipment synchronisation scheme.


339-1268/06

.

Navigation Page

19

Book Contents


Network address management enables the management of network addresses (NSAP address) used to control the SDH network via a NMC (Network Management Centre). Date and time configuration sets the equipment date and time.

Maintenance Management Groups together all sub-applications for the management of: n Software Download [LC]; n Performance Monitoring; n General Functions. Software download downloads from the Control Application computer the new releases of unit application software. Performance Monitoring initiates a performance data collection on different monitored entities. General Functions facility to obtain the Software Version or Inventory Data Information from each unit.

Fault Management Fault management functions: n Event Reports Listing. Event reports listing can display the content of the Equipment Alarm Log and Event Log databases.

SYSTEM COMPOSITION The information regarding the Element Manager can be found in the relevant manual while those regarding the LCT application are given in the following. Refer To: ServiceOn Optical Element Manager Manual

Local Craft Terminal Hardware Composition n CPU INTEL PENTIUMÔ 100MHz or higher; n 1Gb Hard Disk; n at least 32Mb RAM; n floppy 3.5”; n monitor VGA or SVGA (14” or 17” colour); n video card VGA or SVGA 800x600pixel, 256 colours or higher; n mouse; n one RS232 dedicated line.

Local Craft Terminal Software Composition n MS DOSÔ 6.0 (or higher) and WINDOWS 95Ô (or higher); n Local Craft Terminal Software (available on 3.5” floppy disks).


339-1268/06

.

Navigation Page

20

Book Contents

ACTIVATING THE LOCAL CRAFT TERMINAL CONNECTION OF THE PERSONAL COMPUTER The PC’s RS232 serial port (COM1 or COM2) must be connected to the Communication and Control Unit of the equipment via the RS232 ports. Manufacture the serial cable using the 9 pin male connector supplied with the F interface connector set for the equipment connection and a proper connector (25 or 9 pin female connector) for the PC side connection (refer to Fig. 4 or Fig. 5). PC RS232 (9 PIN) 1 2 3 4 5 6 7 8 9

DCE

1 2 3 4 5 6 7

(*) 1 2 Rx 3 Tx (*) 4 GND 5 (*) 6 (*) 7 (*) 8 (*) 9

(*) Tx Rx (*) GND (*) (*)

8 (*) 9 (*)

Equipment

1 2 3 4 5 6 7 8 9

PC (*) not used

DTE

Fig. 4 Cable that connects the RS232 equipment DCE Interface and a 9 Pin RS232 PC Interface. PC RS232 (25 PIN) 1 2 3 4 5 6 7 8 9

DCE

1 2 3 4 5 6 7

(*) 1 2 Tx 3 Rx (*) 4 GND 5 (*) 6 (*) 7 (*) 8 (*) 9

(*) Tx Rx (*) GND (*) (*)

8 (*) 9 (*)

Equipment

(*)

Fig. 5 Cable that connects the RS232 equipment DCE Interface and a 25 Pin RS232 PC Interface.


.

Navigation Page

25

PC

(*) not used

339-1268/06

1 2 3 4 5 6 7 8 9 10

Book Contents

DTE

MSHXXX - OPERATOR’S HANDBOOK ACTIVATING THE LOCAL CRAFT TERMINAL

To connect the Personal Computer ports to the equipment proceed as follows: * Check that the Personal Computer is not powered then insert the cable connector into the PC RS232 interface. * Insert the other cable connector into the equipment RS232 interface. The Personal Computer is now connected to the equipment and the operator can turn it on to begin software installation.

SOFTWARE INSTALLATION Before starting the software installation ensure that the DOS Operating System has been correctly installed together with the Microsoft WindowsÔ program (or check the correct installation of Windows 95Ô Operating System). For more information refer to the relevant handbooks.

To install the LCT: * Insert the 3.5 inch diskette in the appropriate drive. * Execute the program SETUP.EXE; the following window will be displayed:

Follow the procedure clicking on the Next button. The procedure is self-explaining.

To install the LCT's Help on Line: * Insert the 3.5 inch diskette in the appropriate drive. * Follow the same procedure as described for the LCT installation.

ACCESS THE LOCAL CRAFT TERMINAL SOFTWARE From MS-DOS operating system

n enter the command WIN \ADM_xx\ADM_xx.EXE . From the WINDOWS desktop

n open the ADM-xx program group; n double-click on the ADM-xx icon with the mouse or pressing the key on the keyboard.


339-1268/06

.

Navigation Page

22

Book Contents

MSHXXX - OPERATOR’S HANDBOOK ACTIVATING THE LOCAL CRAFT TERMINAL

CONFIGURATION OF COMMUNICATION PARAMETERS The following paragraph describes the operation necessary to configure all the communication parameters for the equipment. This operation has to be performed before the connection with the equipment.

To configure the connection parameters: * Click on the Connection Status button in the main window or select File -> Communication settings… from the main menu.

The Communication window becomes accessible. * Select the serial port used for the connection of the LCT by selecting the relevant Port radio button. * Select the MSH11 mode to use the serial port at 9600baud. This option is used when it is necessary to perform a remote login by means of an old ADM-1. Local Craft Terminal

9600baud F Interface DCC ADM-1

NE STM-1

NE = ADM/REG-4/16/64 ADM-1 = MSH11 (old ADM equipment)

Fig. 6 Remote Login by means of an old ADM-1 equipment

* Use Apply to confirm the settings or Cancel to disable them.


339-1268/06

.

Navigation Page

23

Book Contents

MAIN FUNCTIONS There are seven main parts on the Control Application (CA) window: the Menu bar, the Title bar (with the NSAP indication), the Tool bar, the Graphical area, the Alarm and Event monitor window, the Progress bar and the Alarm Summary. Menu Bar

Title Bar

Graphical Area

Alarm and Event Monitor Window Progress Bar

Tool Bar

Alarm Summary

MENU BAR AND MENUS In the title bar is displayed the type of equipment as ADM-xx (ADM) and the NSAP indication (in case of remote login it will be displayed the network element NSAP code or just the indication ‘Local Access’ in case the Control Application is connected to the local equipment). Beneath the Control Application title bar is the menu bar, which is used to access all the menus. The menu bar is always visible during the connection with the Control Application.

To display a menu using a mouse, click the menu title on the menu bar. To close the menu, click another part of the screen. There are two ways to display a menu using the keyboard:


339-1268/06

.

Navigation Page

Book Contents

MSHXXX - OPERATOR’S HANDBOOK MAIN FUNCTIONS

1. Press to activate the menu bar. Use the arrow keys to move to the menu title to select and press . To close a menu without selecting a command, press . 2. Press plus the first letter of the menu title to display. Note that the first letter of each menu title on the menu bar is underlined. Select the required command with the arrow keys and press . To close a menu without selecting a command, press .

GRAPHICAL AREA The graphical area is a representation of the equipment layout.

Note

(ADM-4) / (ADM-16) If the equipment has been configured as regenerator the Tributary and Switch Unit are not accessible (the relevant slots are displayed in light grey colour) furthermore several command buttons (and the associated function) are not available. The push buttons disabled are: Synchronisation Configuration, Cross Connection, MSP, MS-SPRing Configuration and Card Protection.

All the units are displayed, the colour of the unit is the status indication: Colour

Status

Red Yellow

Failed Maintenance (only for Communication and Control Unit)

Dark grey

Configured

Light grey

Not Configured

A configured unit is displayed in dark grey, a fitted but not configured card is displayed in light grey.


339-1268/06

.

Navigation Page

26

Book Contents


If a wrong card is inserted according to the configured card, it is drawn in a red colour.

If a unit is configured and it is not inserted in the sub-rack, it is drawn outside the sub-rack.

On the top of each unit there is a LED that becomes red when one or more alarms are detected inside the unit.

ALARM SUMMARY The Alarm Summary allows to display the summarising alarms for the equipment. The indications are:


339-1268/06

.

Navigation Page

27

Book Contents


n URG (red) lights on when an urgent alarm is detected; n NURG (red) lights on when a not-urgent alarm is detected; n IND (yellow) lights on when an indication alarm is detected; n SUMM (red) lights on when one or more alarms are detected; n INT (red) lights on when an internal alarm is detected; n EXT (red) lights on when an external alarm is detected; n ABN (yellow) lights on when an abnormal operation is detected; n MEM (yellow) lights on after an alarm acknowledge operation (pushing the button on the front panel all the red LEDs switch off, the yellow one lights on). Note

(ADM-64) For the ADM-64 instead of the MEM indication is present the MEM/PARK indication. When after an alarm acknowledge operation the indication becomes MEM, when the parking mode is activated the indication becomes PARK.

By clicking with the right mouse button, next to the Alarm Summary and Alarm and Event Monitor Window area, the following commands will be available: Active Alarms, Acknowledge, Clear Window Alarms, Realign Shelf. The Active Alarms item allows to display a summary of the active alarms. The Acknowledge can be used as the alarm memorisation push button present on the physical EOS (End of Shelf Unit). By selecting this item the alarm conditions are acknowledged; all the active alarm lamps are switched off and the MEM LED lights on. The Clear Window Alarms can be used to erase the alarm/event displayed in the Alarm and Event Monitor Window, to perform a general refresh select the Realign Shelf item. The ABN (Abnormal) LED lights on when: n an internal loopback is activated; n a "lockout of protection" or "forced switch" is activated on the MSP; n LOS at booster and preamplifier input interface; n the optical protection function is disabled or the laser is forced off (*). Note(*)

The ABN optical indication activated in case of optical protection function disabled or laser forced off can be inhibited via software.

See Also: Specific Functions: Laser Configuration

TOOL BAR The Tool bar is a bar of command buttons for reaching in a faster way the main functionalities of the Control Application software.

By stopping the mouse pointer on a command button for a few seconds, a pop-up menu will appear, indicating the main functionality that can be activated by using the selected button (as shown in the following example).


339-1268/06

.

Navigation Page

28

Book Contents


The Connection Status Indication The connection status indication is a button which carries the information on the status of the connection between the PC and the equipment. n link to the equipment is up;

n the equipment is unreachable;

Note

Before the connection with the equipment this button allows the communication parameters set up (i.e. serial port used)

Exit Button Used to exit from the Control Application.

(as after the selection of File ->Exit from the main menu).

Operator Access Button This button indicates the access status: n not logged in (red lamp on);

n read only (yellow lamp on);

n read and modify (green lamp on).

By clicking on the button, when the operator is not logged in, a Login window, with user name and password request, will appear, to log in either the local or remote equipment. By clicking on the button, when the operator is already logged in, you are logged out from the connected equipment. (as selecting File->Logout from the main menu).

Script Execution Button This button is used to execute scripts.

(as selecting Maintenance->Execution of Scripts from the main menu).


339-1268/06

.

Navigation Page

29

Book Contents


Script Upload Button This button is used to generate CDL scripts.

(as selecting Maintenance->MIB Upload from the main menu).

Synchronisation Configuration Button (ADM) This button is used to displays the synchronisation configuration window.

(as selecting Configuration->Synchronization from the main menu).

Cross-connection / Labels Operations Button (ADM) The following button is used to manage the cross connections.

(as selecting Configuration->Cross Connections from the main menu). When the Port Label functions are enabled, the cross-connection button is substituted by the Port Labels Button.

(as selecting Configuration->Labels Operations from the main menu).

Ethernet Line Protection Button (ADM-16) (ADM-64) This button is used to manage the Ethernet line protections.

(as selecting Configuration->Ethernet Line Protection from the main menu).

Alarm/Event Log Button This button is used to visualise the alarm/event log.

(as selecting Fault->Alarm Log /Reporting from the main menu).

Performance Button This button is used to visualise the equipment performances.

(as selecting Performance->Performance Report from the main menu).

Help Button This button is used to accesses the Control Application help.


339-1268/06

.

Navigation Page

30

Book Contents


(as selecting Help->Index from the main menu).

ALARM AND EVENT MONITOR WINDOW In this window will appear, in real time, any new alarm or events indication. The maximum number of events/alarms that can be displayed depends on the system composition because the information is stored in the PC RAM memory.

Note

The Port Label information is displayed only when this option is enabled otherwise the Unit information will take place.

By clicking with the right mouse button, next to the Alarm Summary and Alarm and Event Monitor Window area, the following commands will be available: Active Alarms, Acknowledge, Clear Window Alarms, Realign Shelf. The Clear Window Alarms item can be used to erase the alarm/event displayed in the Alarm and Event Monitor window. The Acknowledge item is used to store the active alarms. Using the Active Alarms item only the active alarms will be displayed in the alarm and event monitor window, to perform a general refresh select the Realign Shelf item

PROGRESS BAR The progress bar is divided into three different areas from left to right: n send/receive message counter indicating the number of messages sent to the equipment and received from the equipment by the Control Application; n procedure in progress indicating the string of the current procedure carried out by the equipment; n percentage of procedure completion indicating the percentage number of the current procedure carried out by the equipment.


339-1268/06

.

Navigation Page

31

Book Contents

FILE AND SECURITY LOGIN Path (File -> Login) [LC] Selecting the Login item the Login window becomes accessible. In this window the operator can choose between a local or remote access.

There are three types of user: n Read User: enabled to access but not to make modifications. This type of user doesn’t need password; n Write User: enabled to access and to make modifications. The default password for this type of user is SDHNE; n Supervisor: enabled to access, to make modifications and to change Write User's password. The default password for this type of user is S_SDHNE. There are two kinds of Access Mode: n Local Access: when the equipment to manage is locally connected to the Control Application via a serial link; n Remote Access: when the equipment to manage is achievable using pass-through functionality of a NE locally connected to the Control Application.

Local Access To perform a local access: * Select Local Access in the access mode. * Select the user type and insert the password. * Confirm by clicking the OK button. Once the operator has confirmed his login operation, in case of a Write or Administrator user, the access to the equipment is enabled and the light on the Operator Access button becomes green. In case of a Read user the access is enabled but no modifications are allowed. Light on the Operator Access button is yellow. In the case of a login failure the light will be red.


339-1268/06

.

Navigation Page

Book Contents

MSHXXX - OPERATOR’S HANDBOOK FILE AND SECURITY

Remote Access To perform a remote access: * Select Remote Access in the Access mode. * Select the remote node NSAP by using the Enter Remote NSAP scroll list. * Select the user type and insert the password. * Confirm by clicking on the OK button. A node can be added by clicking on the Add Node button. Then in the Add Node window the operator has to insert the NSAP address and an identifier of the node.

By clicking on the Delete Node button and selecting a node in the list, the operator can remove the node. The Edit Node button is used to change the name or the NSAP address of an existing node. See Also: Logout, Change Password

LOGOUT Path (File -> Logout) [LC] Selecting the Login item the user closes his connection to the equipment. The light on the Operator Access button becomes red. See Also: Local Craft Terminal: Remote Login, Change Password

EXIT Path (File -> Exit) By selecting the Exit item the operator exits the Control Application software.

LC SETTINGS Path (File -> LC settings) By selecting the Lc Settings menu item (File main menu), the User Settings window will become accessible.

General Settings Path (File -> Lc Settings -> General) This folder is used to enable the label operations and to configure the Control Application language. General folder by clicking on the General button in the upper part of the User Settings window.


339-1268/06

.

Navigation Page

34

Book Contents


To enable the port label functionality (ADM): * Click on the Port Labels check box. * Confirm the setting by clicking on the Apply push button. This function allows the operator to use the port label indication (properly entered by using the Channels item in the Unit menus or the Tp Labels item in the Configuration menu) and a new configuration window. In the configuration windows, the ports will be indicated by the previously entered labels and the default names will be exclusively used when no port label has been assigned. When this function is enable, the cross connection toolbar button in the main window will disappear and will be substituted by the port label button. In the Rotation field the Horizontal and Vertical radiobuttons are present, they are used to change the strings display in the graphical area. Vertical rotation has two possible options: 90* and 270*.


339-1268/06

.

Navigation Page

35

Book Contents


To change the Control Application language: * Select the language to be used, by clicking on it in the Language scroll list. * Confirm the setting by clicking on the Apply push button. Note

For changing the Control Application language, the proper file (containing all the local controller strings in the required language) must be present in the local controller directory.

See Also: Label Operations Configuration (ADM), Termination Point Labels (ADM), Specific Functions: Channels - STM-n Units/WDM STM-16/DWDM STM-16/METRO STM16/DWDM STM-64, Specific Functions: Channels - nx140/155Mbit/s Tributary Units (ADM)

Alarm Settings Path (File -> Lc Settings -> Alarm Settings) This folder is used to enable or disable the notification of some alarm in real time monitor window. * Select the Alarm Settings folder by clicking on the relevant button in the upper part of the User Settings window.

* Enable the alarm notification function by checking the relevant check buttons. * Confirm the settings by clicking on the Apply push button.

Alarm Colours Path (File -> Lc Settings -> Alarm Colours) This folder is used to change alarm message colour in real time monitor window. * Select the Alarm Colours folder by clicking on the relevant button in the upper part of the User Settings window.


339-1268/06

.

Navigation Page

36

Book Contents


Any alarm message can be displayed, in alarm and event monitor window, with a custom colour, this in accordance to the alarm category. The categories are: n urgent alarm; n not urgent alarm; n indicative alarm; n not defined alarm (indicated by ”------”); n alarm status cleared.

To modify the alarm message colour proceed as follows: * Select one of the available alarm category by clicking on it and press the Edit command button. A colour palette window become accessible

* Select one of the available colours and click on OK. * Confirm the settings by clicking on the Apply push button.

Ground Contact Alarm Name Path (File -> Lc Settings -> GC Alarm Name) This folder is used to change the alarm names relevant to the ground contacts managed by the equipment.


339-1268/06

.

Navigation Page

37

Book Contents


To change a ground contact alarm name: * Select one of the available ground contact alarm names, by clicking on it in the list. * Enter the new name in the New: text field. * Press Apply to confirm the settings, now the new name is available in the alarm list.

To restore the original settings: * Click on the Default button. See Also: Ground Contacts, Specific Functions: Ground Contacts

CHANGE PASSWORD Path (Security -> Change Password) [LC] Selecting the Change Password item the Supervisor user can modify his password and the password of the Write user, while the write user is only allowed to change his own password.

To change the Write User password: When the logged user is the Write User: * Select the Change Password item and click on the Write User folder. * Type the current Write User password. * Type the new Write User password, retype the new password as a confirmation of the operation. * Confirm by clicking on the Apply button. When the logged user is the Supervisor: * Select the Change Password item and click on the Write User folder. * Type the new Write User password, retype the new password as a confirmation of the operation. * Confirm by clicking on the Apply button.

To change the Supervisor password: * Select the Change Password item and click on the Supervisor folder. * Type the current Supervisor password. * Type the new Supervisor password, retype the new password as a confirmation of the operation. * Confirm by clicking on the Apply button.


339-1268/06

.

Navigation Page

38

Book Contents

CONFIGURATION AND INVENTORY In this chapter all the operations necessary to configure general parameters of the system (i.e. NSAP and MAC address, date and time, etc.), cross connections, MSP, equipment protection, synchronisation sources and ground contacts are described.

SYSTEM SETUP: INFO Path (Configuration -> System Setup -> Info) This function is used to introduce the NE name, the NE version and its date and time.

To configure the general system parameters: * Select the Info folder by clicking on the Info button in the upper part of the NE Installation window.

* Set the name of the equipment, by writing it into the System text field. * Set any Additional information about the equipment (optional). * Set the version of the equipment, by writing it into the Version text field (optional). * When the path trace bytes (J0, J1 and C2) and any SOH bytes are not used, it is possible to set their value to “all 0” or “all 1” by checking the relevant radio button Fixed to 0 value or Fixed to 1 value. * Set the system date and time, using the relevant spinners. Two buttons are available for extracting the date and time from the computer (Set to Computer time) or from the equipment (Request from shelf). * Click on the Apply button to validate the new configuration parameters.


339-1268/06

.

Navigation Page

Book Contents

MSHXXX - OPERATOR’S HANDBOOK CONFIGURATION AND INVENTORY

SYSTEM SETUP: PROTOCOL Path (Configuration -> System Setup -> Protocol) [LC] This function is used to introduce the NSAP and MAC addresses and to enable the use of Q interface.

To configure the network parameters: * Select the Protocol folder by clicking on the Protocol button in the upper part of the NE Installation window.

* Input the NSAP address, by writing it into the relevant text field (20 bytes in hexadecimal code). * Define whether the system is used as a Level 1 Intermediate System or as a Level 2 Intermediate System (for routing purposes), by checking the relevant radio button. * Enable the use of Ethernet, by checking the relevant check box Enabled (this option is used to enable the use of Q interface). * Introduce the MAC address of the equipment, by writing it into the relevant text field (6 bytes in hexadecimal code). * Define the size of packets (in bytes) used on the DCC link. * Define the size of packets (in bytes) used on the ethernet link. * Click on the Apply button to validate the new configuration parameters. * Use the Restart button to force the start-up of the communication protocol.

SYSTEM SETUP: DCC Path (Configuration -> System Setup ->DCC) [LC]


339-1268/06

.

Navigation Page

41

Book Contents


This function is used to enable the use of DCC and to configure their parameters (DCC side and status).

To configure the DCC: * Select the DCC folder by clicking on the DCC button in the upper part of the NE Installation window.

A list of the available DCCs with their settings, is displayed. * Select the DCC to be configured, by clicking on it in the relevant list. * Enable the use of the selected DCC by checking the Used radio button (State field). * Enable the selected DCC, by checking the Unlocked radio button (the Locked radio button is used to disable a DCC). * Define the DCC side by checking the relevant radio button. Remember that a Network DCC on the local equipment must correspond to a User DCC on the remote equipment and vice versa. * Click on the Apply button to confirm the new settings.

To delete the DCCs: * Select the DCC to be deleted, by clicking on it in the relevant list. * Disable the selected DCC, by checking the Locked radio button. * Click on the Apply button to confirm the new settings.

SYSTEM SETUP: FILES DOWNLOAD Path (Configuration -> System Setup -> Files Download) [LC] This function is used to download external configuration files into the system.


339-1268/06

.

Navigation Page

42

Book Contents


To download the file: * Select the Files Download folder by clicking on the Files button in the upper part of the NE Installation window.

A list of the available files is displayed. New files can be added clicking on Add File command button. A new window appears where it’s possible select the files, exploring the personal computer directories. * Clicking on Start command button the files display in the list are download into the sequence. The status of the downloading files changes from ”To be load” in a number which indicates the percent of file downloaded.

To abort the file download: * Clicking on Stop command button the download procedures will be aborted.

To edit a file before download: * Selects the file to be edited clicking on it in the list. Clicking on Edit command button it’s possible modify on line the file.

To delete a file from the list before download: * Selects the file to be edited clicking on it in the list. Clicking on Delete command button it’s possible to delete the file from the download file list.

SYSTEM SETUP: FILES UPLOAD (ADM-16) (REG-4/16) (ADM-64) (REG-64) Path (Configuration -> System Setup -> Files Upload) [LC] This function is used to upload the system configuration files.

To upload the file:


339-1268/06

.

Navigation Page

43

Book Contents


* Select the Files Upload folder by clicking on the Files button in the upper part of the NE Installation window.

A list of the available files is displayed. Clicking on Dest. F. Name command button a new window appears where it’s possible select the destination folder, exploring the personal computer directories. * Clicking on Start command button the file will be upload. The status of the uploading files changes from ”To be load” in a number which indicates the percent of file downloaded.

To edit a file before upload: * Selects the file to be edited clicking on it in the list. Clicking on Edit command button it’s possible modify on line the file.

SYSTEM SETUP: ROUTING TABLES (ADM-16) (REG-4/16) (ADM-64) (REG-64) Path (Configuration -> System Setup -> Routing Tables) [LC] This function is used to display information about the NE routing in the net. Note

The Routing Tables are only available when the NE is equipped with a Communication and Control Unit Type D. * Select the Routing Tables folder by clicking on the Files button in the upper part of the NE Installation window.


339-1268/06

.

Navigation Page

44

Book Contents


If the equipment is configured as Level 1 Intermediate System only the Level 1routing tables are available, while if it is configured as Level 2 Intermediate System both Level 1 and Level 2 routing tables are available. * Press Read Local Routing Tables (level 1) to view the values for this level. The fields for the Local Routing Tables (level 1) are listed in the following: SystemID: it displays the NE identifier reachable from the route; NextHopSysId: it displays the NE identifier of the next hop; Port: it indicates the type of circuit used for the routing (DCC or Ethernet); DccIdentifier: It indicates the slot number and the port that recognises the connection. (This field will be empty if the circuit is Ethernet). MacAddress: it contains the SNAP (Sub Network Point Attachment) in case of the connection is via Ethernet, otherwise it is empty (via DCC); Lev2Capability: it displays if the Network Element is able to perform a level 2 routing; Entry: this field indicates if the next hop is manual, virtual, IS-IS (Intermediate System) or ES-IS (End System); Metric: this field contains the global cost of the route. * Press Read Area Routing Tables (level 2) to view the values for this level. The fields for the Local Routing Tables (level 2) are listed in the following: Area Prefix Len: this field indicates the length of the area prefix; Area Prefix: it indicates the value of the reachable areas prefixes: NextHopSysId: it displays the NE identifier of the next hop;


339-1268/06

.

Navigation Page

45

Book Contents


Port: it indicates the type of circuit used for the routing (DCC or Ethernet); CircuitID: it indicates the slot number and the port that recognises the connection. (This field will be empty if the circuit is Ethernet). MacAddress: it contains the SNAP (Sub Network Point Attachment) in case of the connection is via Ethernet, otherwise it is empty (via DCC); Entry: it indicates if the next hop is manual, virtual, IS-IS (Intermediate System) or ES-IS (End System); Metric:it contains the global cost of the route. * Press Export to save the routing tables data on a file on the PC.

CROSS CONNECTIONS (ADM) Path (Configuration -> Cross Connections) This function allows to create cross connections at the every level managed by the equipment. Note that the ADM-16 and the ADM-64 can manage only the VC-4 level, while the ADM-4 can manage up to the TU-12 level, (it is also possible to manage VC-2-nc and VC-4Xc concatenated traffic type). The cross connection can be unidirectional, bidirectional, broadcast, concatenated, drop & continue and loopback. By selecting this item, the Cross Connection window becomes accessible.

In the Cross Connection window there are two fields (From and To) with the currently selected elements to be connected and the protection information field (Protection). When a channel is selected the push buttons relevant to the possible options will appear under the protection information field.


339-1268/06

.

Navigation Page

46

Book Contents


To refresh the Cross Connections status of a specific unit (either line or tributary), click on the Slot button, allocated below each tributary channel list, to perform a global refresh click on the Request push button. See Also: Cross Connections: Bidirectional, Cross Connections: Drop and Continue (ADM-4) (ADM-16), Cross Connections: Concatenated, Cross Connections: Loopback, Cross Connections: SNC Protection Configuration, Cross Connections: SNC Protection Switch, Cross Connections: Unidirectional, How to Create a Cross connection, Cross Connections: Path Info

Cross Connections: Multiply SDH Frame (ADM-4) The Multiply push buttons are used to explode the higher level elements of the SDH frame structure into the lower level ones. Note

When the MS-SPRing is active, the protected channels can be multiplied and if the Extra Traffic option has been selected it is also possible to multiply the channels used as protection.

To explode an AU-4, a TU-3 or a TU-2 into its lower order components (down to TU-12 level): * Select an AU-4, a TU-3 or a TU-2 in a STM-1 frame by double clicking on it. * Click on the Mul. TU12 (Multiply TU12) push button to split the selected element into its lower level components (TUG-3s, TUG-2s and TU-12s for the AU-4, TUG-2s and TU-12s for the TU-3, TU-12s for the TU-2). Note

To deselect a channel the operator can double click again on it or click on the Cancel push button.


339-1268/06

.

Navigation Page

47

Book Contents


To explode an AU-4 or a TU-3 into its lower order components (down to TU-2 level): * Select an AU-4 or a TU-3 in a STM-1 frame by double clicking on it. * Click on the Mul. TU2 (Multiply TU2) button to split the selected element into its lower level components (TU-3s and TU-2s for the AU-4, TU-2s for the TU-3).


339-1268/06

.

Navigation Page

48

Book Contents


To explode an AU-4 into its TU-3 components: * Select an AU-4 in a STM-1 frame by double clicking on it. * Click on the Mul. TU3 (Multiply TU3) button to split the selected element into its lower level components (TU-3s). Once an element of the SDH frame is split into its lower level elements, these are still available in some eventual future access to the Cross Connection window. NOTICE

It is not possible to multiply an AU-4 or a TU already cross-connected.

To remove a multiply operation: * Select the multiplexing level to be removed, by double clicking on the upper level (i.e. TU2 for the TU-12s), or click on the Demultiply button. * A warning window will be displayed. Select Yes to confirm. NOTICE

It is not possible to remove a multiply operation of a selected level if some of the lower TU level are still cross-connected.

See Also: Cross Connections: Bidirectional, Cross Connections: Loopback Cross Connections: Drop and Continue (ADM-4) (ADM-16), , Cross Connections: SNC Protection Configuration, Cross Connections: SNC Protection Switch, Cross Connections: Unidirectional, How to Create a Cross connection

Cross Connections: Bidirectional To create a bidirectional cross connection: * Select the first channel to connect, by double clicking on it. The selected channel will be displayed in a red colour, and the channel indication will appear in the From box. * Select the second channel to connect, by double clicking on it. The selected channel will be displayed in a red colour, and the channel indication will appear in the To box. * Create the connection by clicking on the Bidir. button. After these operations the cross connected channels will be displayed in green and they will show the symbol ”-” to indicate their ”connected” status.


339-1268/06

.

Navigation Page

49

Book Contents


To delete a bidirectional cross connection: * Double click on one of the involved channels and click on the Yes button in the confirmation window that will be displayed. or: * Click on one of the involved channels, press the DEL CC button and confirm the operation by pressing the Yes button in the confirmation window that will appear. See Also: Cross Connections: SNC Protection Configuration, Cross Connections: SNC Protection Switch, Cross Connections: Path Info, How to Create a Cross connection

Cross Connections: Unidirectional To create an unidirectional cross connection: * Select the first channel to connect (input), by double clicking on it. The selected channel will be displayed in a red colour, and the channel indication will appear in the From box. * Select the second channel to connect (output), by double clicking on it. The selected channel will be displayed in a red colour, and the channel indication will appear in the To box. * Create the connection by clicking on the Unidir. button. After these operations each bidirectional channel will be split into two unidirectional ones (reception and transmission). The cross connected channels will be displayed in green and they will show the symbol ”-” to indicate their ”connected” status.

To delete a unidirectional cross connection: * Double click on one of the involved channels and click on the Yes button in the confirmation window that will be displayed. or: * Click on one of the involved channels, press the DEL CC button and confirm the operation by pressing the Yes button in the confirmation window that will appear. See Also: Cross Connections: SNC Protection Configuration, Cross Connections: SNC Protection Switch, Cross Connections: Path Info, How to Create a Cross connection

Cross Connections: Broadcast To create a broadcast cross connection:


339-1268/06

.

Navigation Page

50

Book Contents


* Select the first channel to cross connect (Master), by double clicking on it. The selected channel will be displayed in a red colour, and the channel indication will appear in the From box. * Select the leg channels to cross connect, by double clicking on them. The selected channels will be displayed in red colour, and the channel indication will appear in the To box. Note

It is possible to create a broadcast cross connection with a single leg channel. * Create the cross connection by clicking on the Broad. button.

After these operations the cross connected channels will be displayed in green and they will show the symbol ”-” to indicate that they are connected to another channel. Modify push button is displayed when a broadcast cross connection is selected and allows to add or disconnect leg channels.

To delete a broadcast cross connection: * Double click on one of the involved channels and click on the Yes button in the confirmation window that will be displayed. or: * Click on one of the involved channels, press the DEL CC button and confirm the operation by pressing the Yes button in the confirmation window that will appear. See Also: Cross Connections: SNC Protection Configuration, Cross Connections: SNC Protection Switch, Cross Connections: Path Info, How to Create a Cross connection

Cross Connections: Loopback To create a loopback cross connection: * Select the channel to loopback by double clicking on it. The selected channel will be displayed in a red colour, and the channel indication will appear in the From box. * Create the loopback connection by clicking on the Loopback button. The selected channel will be split into two unidirectional channels, transmission and the reception.


339-1268/06

.

Navigation Page

51

Book Contents


To delete a loopback cross connection: * Double click on the involved channel and click on the Yes button in the confirmation window that will be displayed. or: * Click on the involved channel, press the DEL CC button and confirm the operation by pressing the Yes button in the confirmation window that will appear. See Also: Cross Connections: Unidirectional, How to Create a Cross connection

Cross Connections: Concatenated This cross connection is applicable to two types of SDH traffic: VC-2-nc and VC-4-Xc (only the ADM-4 can manage the VC-2nc). In the first case the VC-2 must be contained in the same VC-4; for this reason only up to 21 VC-2 could be concatenated. In the second case four is the maximum number of VC-4 to be concatenated.

To create a VC-4-Xc/VC-2-nc cross connection: * Select the first channel of the VC-4 -Xc/VC-2-nc by double clicking on it. The selected channel will be displayed in a red colour, and the channel indication will appear in the From box. * Press the Group button or keeping pushed the "SHIFT" button on the keyboard and repeat step 1 for all the other channels of the VC-4-Xc/VC-2-nc. All the selected channels will be displayed in the From box. * Use the Group Port button to create the VC-4-Xc/VC-2-nc. * Repeat the steps from 1 to 3 in order to create the second VC-4-Xc/VC-2-nc. * Select the first VC-4-Xc/VC-2-nc, by double clicking on one of its component channels. * Select the second VC-4-Xc/VC-2-nc, by double clicking on one of its component channels. * Create the cross connection by clicking on the relevant push button (for example Bidir. for a bidirectional cross connection).

To delete a concatenated cross connection: * Double click on one of the channels and click on the Yes button in the confirmation window that will be displayed. or: * Click on one of the channels, press the DEL CC button and confirm the operation by pressing the Yes button in the confirmation window that will appear.

To ungroup concatenated ports: * Select the ports group (by clicking on it) and press the UNGROUP button. See Also: Cross Connections (ADM)


339-1268/06

.

Navigation Page

52

Book Contents


Cross Connections: Drop and Continue (ADM-4) (ADM-16) To create a drop and continue cross connection: * Create a broadcast cross connection as previously described. * Select the broadcast cross connection by clicking on the leg channel to be protected with the drop & continue cross connection. The Dr. & Cnt. button becomes accessible. * Click the Dr. & Cnt. button. The mouse cursor will be modified into a vertical arrow. * Double click the desired protection channel; it will appear in the Protection area. * Click the Apply button in the Cross Connection window. The Set Protection Data for Drop & Continue window, with information about the protected and the protection channels, will appear.

In the example the protected channel is the slot 11 channel n. 1-2-1. In normal conditions, it receives data from Slot 1 channel n. 1-3-4; in case of failure, it receives data from Slot 6 channel n. 1-1-5. * Click the OK button and the Cancel button in the Set Protection Data for Drop & Continue window. In the Cross Connection window, the protection channel is displayed in a dark green and the channels directly involved in the drop & continue cross connection, show the symbol “^”.


339-1268/06

.

Navigation Page

53

Book Contents


To delete a drop & continue cross connection: First of all the protection must be disabled, then the cross connection can be deleted. * Select the drop & continue cross connection, by clicking one of the involved channels. * Click the Protection button. * Click on the Delete button in the Set Protection Data for Drop & Continue window and on the Yes button in the confirmation window. * Select the cross connection and click the DEL CC button. See Also: Cross Connections: Multiply SDH Frame (ADM-4), Cross Connections: SNC Protection Configuration, Cross Connections: SNC Protection Switch, Cross Connections: Path Info, How to Create a Cross connection

Cross Connections: Path Info This additional information associated to a cross connection is mandatory if the channel must be protected through a Multiplex Section Shared Protection ring.

To create a cross connection path information: * Select the AU4 channel on which add the path information, by double clicking on it. The selected channel will be displayed in a red colour. * Click on the Path Info button. The Path Info window will appear on the screen.


339-1268/06

.

Navigation Page

54

Book Contents


Note

When MS-SPRing is active the Path Info window is displayed automatically. If the selected cross connection is involved in a SNCP or is an Drop & Continue , the Path Info displays the information for the Protected and Protection channel. * For the selected AU4 channel specify the source and the destination node identification in the range 0 to 15.

This must be set also into the intermediate node where the AU4 channel is cross connected in passing-through mode. The node identification number must be univocal, consecutive and defined following the East to West directionality as shown in the figure below. The Routing Path information is not managed yet. E

W 1

E

W 2

5 E

W

W 3 E

4

Sequence 1 2 3 4 5

E W

See Also: Cross Connections: Bidirectional, Cross Connections: Unidirectional, How to Create a Cross connection

How to Create a Cross connection In this paragraph there is an example of the procedure to follow to create a cross connection.

Standard Cross Connection In this case the cross connection is bidirectional between an AU-4 channel on an Optical STM-64 unit and an AU-4 channel on an STM-16 tributary unit. * Select an AU-4 in an STM-64 frame by double clicking on it. The selected channel will become red. * Select an AU-4 channel on the STM-16 line, by double clicking on it. The selected channel will become red.


339-1268/06

.

Navigation Page

55

Book Contents


* Create a bidirectional cross connection between the selected channels, by clicking on the Bidir button. After these operations the cross connected channels will be displayed in green and they will show the symbol ”-” to indicate they are connected to another channel. To remove this cross connection double click on one of the two channels and click on the Yes button in the confirmation window that will be displayed. To remove a cross-connections is also possible to click on one of the channels, press the DEL CC button and confirm the operation by pressing the Yes button in the confirmation window that will appear.

Concatenated Cross Connection (ADM-4) In this case a bidirectional VC-2-nc cross connection between two STM-1 units is created. * Select an AU-4 in a STM-1 frame by double clicking on it. The selected channel will become red. * Click on the Mul. TU2 button to split the selected AU-4 into TU-2. * Select a TU-2 channel on a tributary unit, by double clicking on it; then, press the GROUP button (or keeping pushed the “SHIFT” button on the keyboard) select the other channels to concatenate. Remember that only consecutive channels can be selected. The selected channels will become red. * Click on the Group Port push button. The grouped ports will be indicated with the symbol “:”. * Repeat the first four steps for the other STM-1 unit. * Create a bidirectional cross connection between the selected channels, by clicking on the Bidir button. After these operations the cross connected channels will be displayed in green and they will show the symbol ”-” to indicate they are connected to another channel. To ungroup the previously connected ports, select the ports group (by clicking on it) and press the UNGROUP button.


339-1268/06

.

Navigation Page

56

Book Contents


Concatenated Cross Connection In this case a unidirectional VC-4-Xc cross connection between two STM-16 units is created. * Select an AU-4 in an STM-16 frame by double clicking on it. The selected channel will become red. * Press the GROUP button (or keeping pushed the “SHIFT” button on the keyboard) and select the other channels to concatenate. Remember that only consecutive channels can be selected. The selected channels will become red. * Click on the Group Port push button. The grouped ports will be indicated with the symbol “:”. * Repeat the first three steps for the other STM-16 unit. * Create a unidirectional cross connection between the selected channels, by clicking on the Unidir. button. After these operations each bidirectional channel will be split into two unidirectional ones (reception and transmission). The cross connected channels will be displayed in green and they will show the symbol ”-” to indicate they are connected to another channel. To ungroup the previously connected ports, select the ports group (by clicking on it) and press the UNGROUP button. When a loopback is enabled on a channel, the indication ’L’ is displayed after the channel identifier in the Cross Connection window

The protection units, in Equipment protection, are not accessible in the Cross Connection window and are displayed with a proper indication.

The protection units, in MSP, are not accessible in the Cross Connection window and are displayed with a proper indication.

If the Extra Traffic option is disabled, the protection units, in MS-SPRing, are not accessible in the Cross Connection window and are displayed with a proper indication, while if the Extra Traffic is active, the relevant channels can be cross connected; this condition is indicated by the letter “E”.


339-1268/06

.

Navigation Page

57

Book Contents


Extra Traffic Disabled

Extra Traffic Enabled

See Also: Cross Connections: Bidirectional, Cross Connections: Loopback, Cross Connections: Multiply SDH Frame (ADM-4), Cross Connections: SNC Protection Configuration, Cross Connections: SNC Protection Switch, Cross Connections: Unidirectional

Cross Connections: SNC Protection Configuration To create a SNC protection: * Select an existing connection, by clicking on one of the involved channels. IMPORTANT In case of bidirectional cross connection, the first selected channel in the cross connection will be the protected one (it will be used as Protected Slot in the Protection Setting window). * Click on the Protection button. The cursor will be modified into a vertical arrow. * Select the protecting channel (it must be of the same type of the protected one) by a double click on it. The Protection Setting window will be displayed.


339-1268/06

.

Navigation Page

58

Book Contents


* Select if the protection is revertive or not, by checking the relevant radio button. * For a revertive protection, set also the Wait to Restore time (from 0.5 to 30.0 minutes), using the relevant spinner. This time is expressed in minutes and represents the time waited by the system before switching back to the protected channel, once it returns available. * Set the Holdoff time (from 0.0 to 20.0 seconds), which is the time waited by the system before triggering the protection. If the selected channel is an AU-4 it is also possible to set the parameters concerning the SNCP Inherent or Not intrusive. * Set Inherent or Not-intrusive SNC protection, by clicking on the relevant radio button. * If the Not-intrusive selection is done, you can also enable the detection of EXC, TIM and SD alarms as switching criteria by clicking on the corresponding check boxes. Note

The SD option is not available yet. * Confirm the SNC protection creation, by clicking on the Apply button.

Note

A red cross indicates that both channels (protection and protected) are faulty; in this case the “Current State” indicates the message: “SF Switch Pend” (Switch Pend due a Signal Failure).

IMPORTANT The SNCP/N can be managed only if the involved AU-4 channels have previously been set with the monitor enabled. In the Cross Connections window the protecting channel will be displayed in a darker green. After selecting a protected cross connection, the operator can modify the protection parameters, by clicking on the Protection button. The Protection Setting window will be displayed.


339-1268/06

.

Navigation Page

59

Book Contents


To delete a SNC Protection: * Select an existing SNC Protection, by clicking on one of the involved channels. * Click on the Protection button. The Protection Setting window will be displayed. * Click on the Delete button. See Also: Cross Connections: Bidirectional, Cross Connections: Drop and Continue (ADM-4) (ADM-16), Cross Connections: Multiply SDH Frame (ADM-4), Cross Connections: SNC Protection Switch, How to Create a Cross connection

Cross Connections: SNC Protection Switch To perform a Manual Switch between the channels involved in a SNC protection: * Select an existing SNC Protection, by clicking on one of the involved channels. * Click on the Protection button. The Protection Setting window will be displayed. * Click Manual switch button on the left to perform a manual switch to the Protected slot, or on the right one to perform the switch to the Protecting slot. If this second channel is not available the system does not execute the switch. Note

For a Revertive SNC protection the Manual Switch to the Protected slot is not available. When the Protecting slot is not available, the right Manual switch button is not accessible.

To perform a Forced Switch between the channels involved in a SNC protection: * Select an existing SNC Protection, by clicking on one of the involved channels. * Click on the Protection button. The Protection Setting window will be displayed. * Click Forced switch button on the left to perform a forced switch to the Protected slot, or on the right one to perform the switch to the Protecting slot. Even if this second channel is not available the system executes anyway the switch. If a card, on which a Forced Switch has been performed, get failed, no protection switch takes place. Note

For a Revertive SNC protection the Forced Switch to the Protected slot is not available.

Note

When the Protecting slot is not available, the right Forced switch button is not accessible.

To perform a port Swap between the channels involved in a SNC protection: * Select an existing SNC Protection, by clicking on one of the involved channels. * Click on the Protection button. The Protection Setting window will be displayed.


339-1268/06

.

Navigation Page

60

Book Contents


* Click on the Swap Ports button to invert the roles in the protection scheme. The protection channel will become the protected one and vice versa.

To disable the use of a protecting channel involved in a SNC protection: * Select an existing SNC Protection, by clicking on one of the involved channels. * Click on the Protection button. The Protection Setting window will be displayed. * Click on the Lockout button (available only for the Protecting slot).

To activate again a previously disabled channel or to return from a switch operation: * Click on the Clear button. See Also: Cross Connections: Bidirectional, Cross Connections: SNC Protection Configuration, How to Create a Cross connection

AUTOMATIC CIRCUIT TEST (ADM-16) (ADM-64) The ACT (Automatic Circuit Test) has been implemented to perform automatically a circuit test and it is available on all STM-N traffic interfaces. IMPORTANT The ACT is not hitless, for further details about this functionality please refer to the Information for the System Engineer Chapter in the Equipment Description Handbook * Selecting a cross connection the ACT button will become available. * Click on the ACT button and the Automatic Circuit Test will be displayed.

* Define if the ACT is Generate, Terminate or Disabled using the Sautés scroll list. * When the ACT is generated, define the sent value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Send field). * When the ACT is terminate, define the expected value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Expected field).


339-1268/06

.

Navigation Page

61

Book Contents


For the expected and sent value of J1 path trace, five different configurations can be selected: E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen Hexadecimal characters Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros Disable The path trace management is not used

LABEL OPERATIONS CONFIGURATION (ADM) Path (Configuration -> Labels Operations) This menu item can be used to perform cross connections, to start and set up performance, to configure synchronism and data communication channels. By selecting this item, the Labels Operations window becomes accessible.

In the upper part of this window, in the Tp Label scroll list, the different tributary and line ports are listed by using their labels. If no labels have been previously entered (by using the Channels item in the Unit menus or the Tp Labels item in the Configuration menu), the ports will be displayed with their default name. The klm scroll list indicates, in case of STM-n ports, the selectable channels by using the SDH standard channel numbering. The Details area provides additional information regarding the selected port. The Int Synch text field indicates if the port is used or not as system synchronisation source, the Ext Synch text field shows if the port is configured as external output synchronisation source and the DCC field is used when a data communication channel of the selected STM-n port is unlocked. In the rightmost part of the window, the Cross Connection area contains all fields and push buttons for performing connections.


339-1268/06

.

Navigation Page

62

Book Contents


In the middle of the window, the Performances area contains the push buttons to activate and setup the collection of information quality data of the selected port. The DCC management and the synchronisation sources configuration can be performed by using the relevant push buttons present in the centre of the window, as described in the following. When a channel is selected the push buttons relevant to the possible options will appear. See Also: Termination Point Labels (ADM)

Label Operations: Cross Connections Management Cross connection functionality can be performed by using this menu item (as described in the following) or selecting the Cross Connections item. Starting the Label Operations window, the Cross Connections window can be displayed and used by pressing the Browse... push button. See Also: Cross Connections (ADM), Label Operations Configuration (ADM)

To multiply SDH frame (ADM-4): * Choose the STM-n port in the Tp Label scroll list and the channel to be multiplied in the klm scroll list. * Click on the “>” button of the From field to confirm the selection. The selected channel will be displayed in the relevant field. * Click on: Mul. TU12 to split the selected element into: TUG-3s, TUG-2s and TU-12s for the AU-4, TUG-2s and TU-12s for the TU-3, TU-12s for the TU-2. Mul. TU2 to split the selected element into: TU-3s and TU-2s for the AU-4, TU-2s for the TU-3. Mul. TU3 to split the selected element into its lower level components (TU-3s).

NOTICE

It is not possible to multiply an AU-4 or a TU already cross-connected.

Once an element of SDH frame is split into its lower elements, these are still available in some eventual future access to the Cross Connection or to the Labels Operations windows.

To remove a multiply operation (ADM-4): * Choose the port in the Tp Label scroll list and its multiplexing level to be removed in the klm scroll list. * Click on the Demultiply button. * A warning window will be displayed. Select Yes to confirm. NOTICE

It is not possible to remove a multiply operation of a selected level if some of the lower TU level are still cross-connected.

See Also: Cross Connections: Multiply SDH Frame (ADM-4)


339-1268/06

.

Navigation Page

63

Book Contents


To create a unidirectional, bidirectional or broadcast cross connection: * Choose, the port in the Tp Label scroll list and, in case of STM-n interfaces, the first channel to cross connect in the klm scroll list. * Click on the “>” button of the From field to confirm the selection. The selected channel will be displayed in the relevant field. * Repeat step 1 for selecting the second channel to cross connect.

* Click on the “>” button of the To field to confirm the selection. The selected channel will be displayed in the relevant field. * Create the cross connection by clicking on: Unidir. push button to create a unidirectional cross connection Bidir. push button to create a bidirectional cross connection Broad. push button to create a broadcast cross connection (with one leg channel)

If the operator want to create a broadcast cross connection with n leg channels, he will have to repeat n times steps 3 and 4, before clicking on the Broad. push button.

See Also: Cross Connections: Bidirectional, Cross Connections: Unidirectional, Cross Connections: Broadcast


339-1268/06

.

Navigation Page

64

Book Contents


To create a drop & continue cross connection: * Create a broadcast cross connection, as previously explained. * Select the broadcast cross connection by clicking on the leg channel to be protected with the drop & continue cross connection. The Dr. & Cnt. button becomes accessible. * Click the Dr. & Cnt. button. The mouse cursor will be modified into a vertical arrow. * Choose, the port in the Tp Label scroll list and, in case of STM-n interfaces, the channel in the klm scroll list. This channel will protect the leg channel previously selected in the cross connection. * Click on the “>” button of the Protection field to confirm the selection. The Set Protection Data for Drop & Continue window, with information about the protected and the protection channels, will appear. * Click the Apply button and the Close button in the Set Protection Data for Drop & Continue window. In the Labels Operations window, the protection channel is displayed in the Protection field and the channels directly involved in the drop & continue cross connection, show the symbol “^”.

See Also: Cross Connections: Broadcast, Cross Connections: Drop and Continue (ADM-4) (ADM-16)

To create a loopback cross connection: * Choose the port in the Tp Label scroll list and, in case of STM-n interfaces, the channel on which create the loopback cross connection in the klm scroll list. * Click on the “>” button of the From field to confirm the selection. The selected channel will be displayed in the relevant field. * Create the cross connection by clicking on the Loopback push button. See Also: Cross Connections: Loopback


339-1268/06

.

Navigation Page

65

Book Contents


To create a concatenated cross connection: This cross connection is applicable to two types of SDH traffic: VC-2-nc and VC-4-Xc (only the ADM-4 can manage the VC-2nc). In the first case the VC-2 must be contained in the same VC-4, for this reason only up to 21 VC-2 could be concatenated. In the second case four is the maximum number of VC-4 to be concatenated. The following list describes the steps necessary to perform a bidirectional VC-2-nc cross connection between two STM-1 unit: * Select an AU-4 in a STM-1 port, by using the Tp Label and the klm scroll lists. * Click on the “>” button of the From field to confirm the selection. The selected channel will be displayed in the relevant field. * Press the Mul. TU2 push button to split the selected AU-4 into TU-2. * Select a TU-2, by using the Tp Label and the klm scroll lists. * Press the GROUP push button (the pointer will become a vertical arrow) and select the other channels to concatenate. * Click on the Group Port push button. The grouped ports will be indicated with the symbol “:”. * Repeat the first six steps for the other STM-1 unit. * Create a bidirectional connection between the two port groups. See Also: How to Create a Cross connection

To undo a channel selection: * Select the channel in the relevant field. * Click on the “<” button of the relevant field or press the Cancel push button to remove the selection. The selected channel will disappear from the field.

To remove a cross connection: * Choose the port in the Tp Label scroll list and, in case of STM-n interfaces, the involved channel in the cross connection to be removed by checking the klm scroll list. * Select the cross connection by clicking on one of the involved channels in the From or To fields. * Press the DEL CC push button and then confirm by clicking on Yes in the warning window that will be displayed.


339-1268/06

.

Navigation Page

66

Book Contents


To create a cross connection path information: This additional information associated to a Cross Connection is mandatory if he channel must be protected through a Multiplex Section Shared protection ring. * Choose the port in the Tp Label scroll list and the channel to add the path information in the klm scroll list. * Click on the “>” button of the From field to confirm the selection. The selected channel will be displayed in the relevant field. * Create click on the Path Info push button. The Path Info window will be displayed. See Also: Cross Connections: Path Info

To create a SNC Protection: * Choose the port in the Tp Label scroll list and, in case of STM-n interfaces, the connected channel to be protected in the klm scroll list. * Select the cross connection by clicking on the channel to be protected in the relevant field (From or To fields). * Press the Protection push button. The cursor will be modified into a vertical arrow. * Choose the port in the Tp Label scroll list and, in case of STM-n interfaces, the protection channel in the klm scroll list. * Click on the “>” button of the Protection field to confirm the selection. The selected channel will be displayed in the relevant field. The Protection Setting window will be displayed. * Choose the SCN Protection characteristics (Revertive or Not Revertive, Inherent or Not intrusive, ...) and click on the Apply button.

To delete a SNC Protection: * Choose the port in the Tp Label scroll list and, in case of STM-n interfaces, one channel of the cross connection that is protected by checking the klm scroll list. * Select the cross connection by clicking on one of the involved channels in the From, To or Protection fields. * Press the Protection push button. The Protection Setting window will be displayed. * Click on the Delete button. See Also: Cross Connections: SNC Protection Configuration, Cross Connections: SNC Protection Switch

Labels Operations: DCCs Management This function can be used to manage the use of DCCs and to configure their parameters (DCC side and status). By clicking on the DCC push button, the NE Installation window will be displayed. See Also: Label Operations Configuration (ADM), System Setup: DCC


339-1268/06

.

Navigation Page

67

Book Contents


Labels Operations: System Synchronisation Management This function can be used to manage the synchronism sources used by the equipment. By clicking on the System Sync... push button, the System window will be displayed. See Also: Label Operations Configuration (ADM), System Synchronisation Sources (ADM)

Labels Operations: Synchronisation Output Management This function can be used to manage the synchronism sources provided by the equipment as outgoing clock reference. By clicking on the Extern Sync... push button, the External window will be displayed. See Also: Label Operations Configuration (ADM), Synchronisation Outputs (ADM)

Labels Operations: Performance Data Management According to the type of selected port, by clicking on the push buttons that will appear in the Performances area, the proper windows for configuring the performance data collection will be displayed. See Also: Label Operations Configuration (ADM), STM-n Units Performance Data, 2Mbit/s Units Performance Data, nx140/155Mbit/s Units Performance Data, 34-45Mbit/s Units Performance Data

MSP PROTECTION (ADM) Path (Configuration -> MSP Protection) By selecting the MSP Protection item, the Create New MSP window becomes accessible. This window allows to create MSP protection pairs.

To create a MSP Protection:


339-1268/06

.

Navigation Page

68

Book Contents


* Select the protection type, by checking the relevant radio button (1:N Protection or 1+1 Protection). * Select the unit to act as working, by clicking on it in the relevant list. * Click on the Worker button. The selected unit will be displayed in the Worker list. * Define the worker channel Priority by means of the relevant scroll list (in case of 1:N Protection only). Note

If no manual priority selection is performed, a default priority setting is assigned to the channel in according to their selection order. * Repeat the steps from 2 to 4, for the working units involved in the 1:N Protection (this procedure is not performed if the 1+1 Protection has been selected). * Select the unit to act as protection, by clicking on it in the relevant list. * Click on the Protection button. The selected unit will be displayed in the Protection list. * In case of 1:N protection, define the priority level (Low or High) for SF and SD switching criteria for every protected channel, using the relevant check buttons. When High is selected, the switch is performed only if there is a serious problem; when Low is selected, the switch is performed with every type of problem. * In case of 1:N protection, assign a Priority number (from 1 to 14) to every protected channel, to define a hierarchy among peer MSP channel priority (1 is the highest priority), by means of the relevant scroll list. This number must be univocal. If different protected channels have the same priority level for switching criteria, the protected channel with the lowest Priority number takes priority. * Select the mode of the MS Protection, revertive or not revertive, by checking the relevant check box.

Note

The 1:N protection can be only Revertive. * If the protection is revertive, set the Wait To Restore time (from 0 to 12 minutes). * Click on the DCC Protected check box in order to configure a MSP with DCC protection.

Note

The operator has to control that on the worker leg a Multiplex Section DCC is enabled and that on the protection leg a Multiplex Section DCC can be enabled or is already enabled. * Define whether or not the protection is Bidirectional, by checking the relevant check box.

Two Undo buttons, one for Worker units and the other for Protection ones, can be used to cancel the relevant selection operations. If the use of extra traffic has been selected, also the protection line will be available in the Cross Connection window. This allows the insertion of lower priority traffic (Extra Traffic) on the protection line. See Also: MSP Switch Operations (ADM), Specific Functions: MSP Protection (ADM)

ETHERNET LINE PROTECTION (ADM-16)(ADM-64) Path (Configuration -> Ethernet Line Protection) By selecting the Ethernet Line Protection item, the Create New Line Protection window becomes accessible. This window allows to create Ethernet Line Protection pairs.


339-1268/06

.

Navigation Page

69

Book Contents


To create an Ethernet Line Protection: * Select the unit to act as working, by clicking on it in the relevant list. * Click on the Worker button. The selected unit will be displayed in the Worker list. * Select the unit to act as protection, by clicking on it in the relevant list. * Click on the Protection button. The selected unit will be displayed in the Protection list. * Select the mode of the Ethernet Line Protection, revertive or not revertive, by checking the relevant check box. * If the protection is revertive, set the Wait To Restore time. Two Undo buttons, one for Worker units and the other for Protection ones, can be used to cancel the relevant selection operations. See Also: Specific Functions: Channels - Gigabit Ethernet Units (ADM-16) (ADM-64)

EQUIPMENT PROTECTION (ADM) Path (Configuration -> Equipment Protection) This function is used to create Equipment Protection groups; it is available for the following units: n 32x1.5/2Mbit/s Tributary Unit (1:N Protection with 1£N£4) (ADM-4); n 63x1.5/2Mbit/s Tributary Unit (1:N Protection with 1£N£4) (ADM-4); n 3x34Mbit/s Tributary Unit (1+1 Protection) (ADM-4); n 3x45Mbit/s Tributary Unit (1+1 Protection) (ADM-4); n STM-1 Electrical/Mux Unit (1:N Protection with 1£N£4) (ADM-4); n 2x140/155Mbit/s Tributary Unit (1:N Protection with 1£N£2) (ADM-4);


339-1268/06

.

Navigation Page

70

Book Contents


n 2x140/155Mbit/s Tributary Unit (1:N Protection with 1£N£4) (ADM-16); n 4x140/155Mbit/s Tributary Unit (1:N Protection with 1£N£4) (ADM-16) / (ADM-64); n switch unit (1+1 Protection). For the switch unit, the protection is automatically performed as soon as a second switch unit is configured.

Protection Groups (ADM-16) For the protection groups on the ADM-16 it is manadatory to use determinated slot positon: Group 1 1:1

Worker: slot 1

Protection: slot 3

1:2

Worker: slot 1 and 4

Protection: slot 3

1:3

Worker: slot 1, 2 and 4

Protection: slot 3

1:4

Worker: slot 1, 2, 4 and 5

Protection: slot 3

1:1

Worker: slot 6

Protection: slot 8

1:2

Worker: slot 6 and 9

Protection: slot 8

1:3

Worker: slot 6, 7 and 9

Protection: slot 8

1:4

Worker: slot 6, 7, 9 and 10

Protection: slot 8

Group 2


339-1268/06

.

Navigation Page

71

Book Contents


By selecting this item, the Create New Equipment Protection window becomes accessible.

To create an Equipment Protection group: * Select a unit to act as working, by clicking on it in the relevant list. * Click on the Worker button. The selected unit will be displayed in the Worker list. Repeat step 1 and 2 for all the units to act as working. * Select the unit to act as protection, by clicking on it in the relevant list. * Click on the Protection button. The selected unit will be displayed in the Protection list. * Select the type of equipment protection, revertive or not revertive, by checking the relevant check box. * If the protection is revertive, set the Wait to Restore time (from 1 to 12 minutes), by using the relevant spinner. This time is expressed in minutes and represents the time waited by the system before switching back to the worker unit, once it returns available. Two Undo buttons, one for Worker units and the other for Protection ones, can be used to cancel the relevant selection operations. * Click the OK button to confirm the settings. IMPORTANT Each protection group is displayed on the main window with a different geometrical symbol. The working card of the group shows this symbol in green.


339-1268/06

.

Navigation Page

72

Book Contents


See Also: Specific Functions: Equipment Protection (ADM)

SYSTEM SYNCHRONISATION SOURCES (ADM) Path (Configuration -> Synchronisation -> System) This folder is used to manage the synchronisation source used by the equipment. By selecting the System folder, on the top of the Synchronisation window, the System folder becomes accessible. Note

If the equipment has been configured as regenerator this function is disabled and the system works in through timing mode.

The main element of this window is a list of synchronisation sources used by the equipment, with their quality level, their priority, their status and their bit error rate enable (Ena) /disable (Dis) /not supported (---) status.


339-1268/06

.

Navigation Page

73

Book Contents


When the in use synchronisation source fails, the equipment will switch on the available source with the highest priority. If the quality management is enabled, the highest quality source is always the in use one (on two sources with the same quality the choice is done on the basis of their priority). Note

(ADM-4) / (ADM-16)

The type of matrix used by the equipment limits the number of synchronisation sources configurable for a card. (ADM-4) If the ADM-4 uses a Switch Unit Type A (XILINX matrix), only one synchronisation source can be configured for each card. This source can be configured only on port n.1, except for PDH cards and for the 2x140/155Mbit/s Tributary Unit (port n.1 or port n.2 can be configured indifferently). If the ADM-4 uses a Switch Unit Type B (TIMEX ASIC matrix), the operator can configure up to two synchronisation sources for each card, except for the 2x140/155Mbit/s Tributary Unit. For this card only one synchronisation source can be configured, choosing between port n.1 and port n.2. (ADM-16) If the ADM-16 uses a Switch Unit Type A (XILINX matrix), only one synchronisation source can be configured for each card. This source can be configured only on port n.1, except for the 2x140/155Mbit/s Tributary Unit (port n.1 or port n.2 can be configured indifferently) and for 4x140/155Mbit/s Tributary Unit (port n.1 or port n.3 can be configured indifferently). It is impossible to configure sources on slots n. 7, 9, and 10. If the ADM-16 uses a Switch Unit Type B (TIMEX ASIC matrix), the operator can configure up to two synchronisation sources for each card, except for the 2x140/155Mbit/s Tributary Unit. For this card only one synchronisation source can be configured, choosing between port n.1 and port n.2. For the 4x140/155Mbit/s Tributary Unit the operator can configure up to two synchronisation sources, choosing one source between port n.1 and port n.3 and the other source between port n.2 and port n.4. It is possible to configure sources on each slot.

To add a new synchronisation source: * Click on the Add button. A list of possible synchronisation sources is displayed.


339-1268/06

.

Navigation Page

74

Book Contents


* Select the unit (or external clock reference) to be used as a synchronisation source, by clicking on it in the relevant list. When an STM-n unit is selected as a synchronisation source, the quality information cannot be defined, since the system uses only the content of S1 byte, but deselecting the Do not overwrite box the quality can be changed by the user. * Select the synchronisation source, by clicking on it in the relevant list. * Select the quality level to be assigned to the synchronisation source, by clicking on it in the Quality scroll list. The following quality levels can be selected: G811 (PRC) Primary Reference Clock G812 Transit (SSUT) Synchronisation Supply Clock Transit G812 Local (SSUL) Synchronisation Supply Clock Local G813 (SEC) SDH Equipment Clock DNU Do Not Use

This field is only available for external synchronisation sources or for synchronisation sources based on signals received from systems which can not manage S1 byte or when the Do not overwrite option has been deselected. * Select the Priority of the synchronisation source, by using the relevant spinner. * Check the EXC Enable, for enabling the change-over function in case of excessive bit error rate detected on the synchronisation source. This field is not available for the 2MHz and 2Mbit/s not CRC framed inputs and PDH 140Mbit/s sources. * Confirm the settings by clicking on the OK button.

To modify an existing synchronisation source: * Select the synchronisation source to be modified, by clicking on it in the list. * Click on the Edit button. The properties of the selected synchronisation source are displayed, the priority and the quality level can be modified.


339-1268/06

.

Navigation Page

75

Book Contents


The quality information cannot be set on STM-n units if the Do not overwrite is selected. * Select the new value for the quality level, by using the Quality scroll list. * Select the new value for the priority, by using the Priority scroll list. * Check the EXC Enable, for enabling the change-over function in case of excessive bit error rate detected on the synchronisation source. * Confirm the new settings, by clicking on the OK button.

To remove an existing synchronisation source: * Select one of the existing synchronisation sources, by clicking on it in the list. * Click on the Delete button.


339-1268/06

.

Navigation Page

76

Book Contents


To configure the general synchronisation parameters: * Define the protection type used for the system synchronisation sources (revertive or not revertive), by checking the relevant radio button. When the use of quality information is enabled, the type of protection is meaningless. In fact the source in use is always the available one with the highest quality level. * If the protection is of the Revertive type, set the value for the Wait To Restore time (from 0 to 60 minutes), by using the relevant spinner. This time is expressed in minutes and represents the time waited by the system before returning to the original working source, once it returns available. * Enable (or not) the use of quality information, by checking (or not) the SSM Enable check box. * If the management of quality information is enabled, define the minimum quality level accepted by using the Min. Quality Level scroll list. Once this parameter is defined, if no synchronisation source with a quality level equal or superior to this threshold is available, the system enters a Free Running or Holdover mode. * Confirm the new settings by clicking on the Apply button. See Also: System Synchronisation Switch Operations, Synchronisation Outputs (ADM)

System Synchronisation Switch Operations To perform a Manual Switch: * Select the synchronisation source to which the switch has to be performed, by clicking on it in the list. * Click on the Manual switch button. If this second synchronisation is not available the system does not execute the switch.

To perform a Forced Switch: * Select the synchronisation source to which the switch has to be performed, by clicking on it in the list. * Click on the Forced switch button. In this case the system executes anyway the switch to the new synchronisation source. If a synchronisation source to which a Forced Switch has been performed, gets failed, no switch to the highest priority (or quality) available source takes place.

To disable the use of a synchronisation source: * Select the synchronisation source to be disabled, by clicking on it in the list. * Click on the Lockout button.


339-1268/06

.

Navigation Page

77

Book Contents


To cancel a previous Lockout operation on a synchronisation source: * Select the previously disabled synchronisation source, by clicking on it in the scroll list. * Click on the Clear button.

To cancel a previous Switch operation on a synchronisation source: * Select the synchronisation source on which the switch has been performed, by clicking on it in the scroll list. * Click on the Clear button. See Also: System Synchronisation Sources (ADM)

SYNCHRONISATION OUTPUTS (ADM) Path

(Configuration -> Synchronisation -> Ext Out 1 / Ext Out 2)

These folders are used to manage the synchronisation sources sent as clock reference outputs by the equipment. IMPORTANT (ADM-4) / (ADM-16) If the equipment uses a Switch Unit Type B (TIMEX ASIC matrix), both Ext out #1 and Ext Out #2 can be set. If the equipment uses a Switch Unit Type A (XILINX matrix), only Ext out #1 can be set. By clicking on the Ext out button, on the top of the Synchronisation window, the Ext Out Synchronisation folder becomes accessible.

The main element of this window is a list of synchronisation outputs supplied by the equipment, with their quality level and their priority.


339-1268/06

.

Navigation Page

78

Book Contents


The output can be selected between the internal source or an external SDH source. The type of matrix used by the equipment limits the number of synchronisation sources configurable for a card (refer to System Synchronisation Sources). For selecting the internal source click on the System button. When the System mode is selected, the output will be locked to the internal clock used by the equipment (the possible sources in the list are not used). For selecting the external source click on the External button. When the External mode is selected, the output will be locked to the best source available in the list (the Internal Source is not used). When the active synchronisation output fails, the equipment switches to the available output source with the highest priority. Note

In the Ext Out #1/ Ext Out #2, an indication about the current state of the synchronisation output (squelched or not) is present. When the output is squelched a red cross is displayed on the current state symbol. Current State Indication

To add a new synchronisation output: * Click on the Add button. * A list of possible synchronisation sources to be used as output references is displayed. * Select the unit (or the external reference) to be used as a synchronisation output, by clicking on it in the Unit area. * Select the port to use as a synchronisation output, by clicking on it in the Port list. * Select the quality of the synchronisation output, by clicking on it in the Quality scroll list. The following quality levels can be selected: G811 PRC (Primary Reference Clock) G812 Transit SSUT (Synchronisation Supply Clock Transit) G812 Local SSUL (Synchronisation Supply Clock Local) G813 SEC (SDH Equipment Clock) Do Not Use Do not use

This field is only available for external synchronisation sources or for synchronisation sources based on signals received from units which can not manage S1 byte or when the Do not overwrite option has been deselected. * Select the priority of the synchronisation output, by using the Priority scroll list.


339-1268/06

.

Navigation Page

79

Book Contents


* Check the EXC Enable, for enabling the change-over function in case of excessive bit error rate detected on the synchronisation source. This field is not available for the 2MHz and 2Mbit/s not CRC framed inputs and PDH 140Mbit/s sources. * Confirm the settings by clicking on the OK button.


339-1268/06

.

Navigation Page

80

Book Contents


To modify an existing synchronisation output: * Select the synchronisation output to be modified, by clicking on it in the list. * Click on the Edit button. The properties of the selected synchronisation source are displayed, the priority and the quality level can be modified. The quality information on STM-n interfaces cannot be modified if the Do not overwrite check box is selected. * Select the new value for the quality level, by using the Quality scroll list. * Select the new value for the priority, by using the Priority scroll list. * Check the EXC Enable, for enabling the change-over function in case of excessive bit error rate detected on the synchronisation source. This field is not available for the 2MHz and 2Mbit/s not CRC framed inputs and PDH 140Mbit/s sources. * Confirm the new settings, by clicking on the OK button.

To remove an existing synchronisation output: * Select one of the existing synchronisation output, by clicking on it in the list. * Click on the Delete button.

To configure the general parameters: * Define the protection type used for the output synchronisation sources (revertive or not revertive), by checking the relevant radio button. * When the use of quality information is enabled, the type of protection is meaningless. In fact the source in use is always the available source with the highest quality level. * If the protection is of Revertive type, set the value for the Wait To Restore time (from 0 to 60 minutes), by using the relevant scroll list. This time is expressed in minutes and represents the time waited by the system before returning to the original working source, once it returns available. * Enable (or not) the use of quality information, by checking (or not) the SSM Enable check box. * If the management of quality information is enabled, define the quality used to squelch the synchronisation output, by using the Squelch Threshold scroll list. Once this threshold is defined, if no synchronisation sources with a quality level equal or superior to this threshold are available, the synchronisation output is squelched. * If the fitted switch unit type allows this functionality, define the type of outgoing signal: analogue (2MHz) or digital (2Mb/s), by using the Type spinner. * Confirm the new settings by clicking on the Apply button. See Also: Synchronisation Output Switch Operations, Synchronisation Output Quality (ADM)


339-1268/06

.

Navigation Page

81

Book Contents


Synchronisation Output Switch Operations To perform a Manual Switch: * Select the synchronisation source to which the switch has to be performed, by clicking on it in the list. * Click on the Manual switch button. If this second synchronisation is not available the system does not execute the switch.

To perform a Forced Switch: * Select the synchronisation output to which the switch has to be performed, by clicking on it in the list. * Click on the Forced switch button. In this case the system executes anyway the switch to the new synchronisation reference signal. If a synchronisation output to which a Forced Switch has been performed, gets failed, no switch to the highest priority (or quality) available synchronisation reference signal takes place.

To disable the use of a synchronisation output: * Select the synchronisation output to be disabled, by clicking on it in the list. * Click on the Lockout button.

To cancel a previous Lockout operation on a synchronisation output: * Select the previously disabled synchronisation output, by clicking on it in the scroll list. * Click on the Clear button.

To cancel a previous Switch operation on a synchronisation output: * Select the synchronisation output on which the switch has been performed, by clicking on it in the scroll list. * Click on the Clear button.

To force the use of the system synchronisation source as output clock references: * Click on the System button. After this operation the list of synchronisation sources used by the system is used also for the synchronisation outputs.

To disable the use of the system synchronisation sources as output clock references: * Click on the External button. After this operation the list of synchronisation outputs, returns to the one defined in the Ext Out #1 / Ext Out #2 folder. See Also: Synchronisation Outputs (ADM)


339-1268/06

.

Navigation Page

82

Book Contents


SYNCHRONISATION OUTPUT QUALITY (ADM) Path

(Configuration -> Synchronisation -> Output Quality)

This folder is used to manage the synchronisation source quality sent as clock reference outputs by the equipment. By selecting the Output Quality folder, on the top of the Synchronisation window, the Output Quality folder becomes accessible.

* Select the synchronisation source to be modified, by clicking on it in the relevant scroll list. This option is available only for SDH units. * Deselect the Do not overwrite and set the new quality in the relevant list. * Confirm the new settings, by clicking on the Apply button. See Also: Synchronisation Outputs (ADM), Specific Functions: Output Quality (ADM)

GROUND CONTACTS Path (Configuration -> Ground Contacts) When the Ground Contacts window is selected, different pictures can be displayed according to the ground contact configuration and to the Connection Unit equipped. The two possible configurations are able to manage either 32 single wire output ground contacts or 11 double wire output loop contacts. Each contact can be configured associating parameters, such as the alarm which activate it or the logical state. The window also gives access to the parameters associated to 4 input ground contacts.


339-1268/06

.

Navigation Page

83

Book Contents


To configure an output ground contact: * Click on the button representing the selected output ground contact. The Output Contact n window (where n is the number of the selected ground contact) becomes accessible.

The Location name shows the number of the pin used on the physical connector by default, for the selected ground contact, but can be also customised by the user. * Define the Severity of the alarm, by checking the relevant radio button (Urgent, Noturgent, etc.). * Select the Alarm causes necessary to activate the output contact, by selecting them in the relevant scroll list.


339-1268/06

.

Navigation Page

84

Book Contents


* Select from the relevant scroll list the Alarm sources, to which the output contact will be associated. * Define the Alarm kind, by checking the relevant radio button (INT, EXT, etc.). * Define whether the output contact is active when connected to ground (active high) or not (active low), by checking the relevant Polarity radio button. * Confirm the settings by clicking the OK button. Note

When check box “Disable” is active, no indication of alarm will be given by means of the selected ground contacts. The disable ground contacts will be displayed in the Ground Contacts window with a dark grey.

Acting on the Current State can modify the current state of the alarm. Note

When in the Location name the output contact is followed by the indication ”HardWired”, its settings cannot be modified.


339-1268/06

.

Navigation Page

85

Book Contents


To set the parameters of each input ground contact: * Click on the button which represents the selected input ground contact. The Input Contact n window (where n is the number of the selected ground contact) becomes accessible.

The Location name shows the number of the pin used on the physical connector by default, for the selected ground contact, but can be also customised by the user. * Set the Additional information about the generated alarm, by writing into the relevant text field. * Set the type of Generated alarm, by using the relevant scroll list. The alarm names present in the Generated alarm scroll list are the same configured in the “Ground Contact Alarm Name”. * Define whether the input contact is active when connected to ground (active high) or not (active low), by checking the relevant Polarity radio button. The Current state of the alarm, in this case, is read only. These ground contact inputs are used to monitor environmental parameters (such as temperature, humidity, etc.). NOTICE

When some of the causes selected for a ground contact are active, the relevant button in the Ground Contacts window will display a red colour, instead of the default blue one. Further the contact will be shown as an opened or closed switch according respectively to Active high or Active low Polarity selection.

See Also: Specific Functions: Ground Contacts

MS-SPRING (ADM) Path (Configuration -> MS-SPring) By clicking on the MS-SPring item in the Configuration menu, the MS-SPRing Configuration window becomes accessible. This window gives access to Multiplex Section Shared Protection ring configuration functions. Note

This protection requires the SS bits equal to Sdh (these bits can be set in the Port Configuration window).


339-1268/06

.

Navigation Page

86

Book Contents


See Also: MS-SPRing Configuration, MS-SPRing Cross Connection, Specific Functions: MSSPRing (ADM), Specific Functions: Channels - STM-n Units/WDM STM-16/DWDM STM-16/METRO STM-16/DWDM STM-64, Specific Functions: Channels nx140/155Mbit/s Tributary Units (ADM)

MS-SPRing Configuration Path (Configuration -> MS-SPRing -> Ring Config) This folder is used to manage the MS-SPRing Protection. By clicking on the Ring Config. folder, the ring configuration window becomes accessible.

To create a MS-SPRing Protection proceed as follows:

* Define the MS-SPRing type: Two Fibres, Four Fibres,Two Fibre NUT or Four Fibres NUT, by selcting it in the Protection Type scroll list. * Define the local node identification number to be associated to the equipment by clicking in the Node Id scroll list (every equipment involved in the MS-SPRing must have a node identification number). After this operation the local node number will be automatically displayed next to the Node Id field and also included in the Ring Map. Note

These numbers must be univocal but they can be chosen in a casual order. * Define the Ring Map by inserting the node identification number of the neighbouring nodes, for each node select the node number by clicking in the Ring List.


339-1268/06

.

Navigation Page

87

Book Contents


IMPORTANT The node identification numbers must be univocal, consecutive, and inserted in the map list following a clockwise path. In other words, the last node number inserted in the map list must be the first network element number in an anticlockwise path. For example, suppose that the network configuration is the following (W = west, E = east):

In the equipment with node number 1, the ring map list will be 1, 2, 3, 4, 5; in the equipment with node number 2, the ring map list will be 2, 3, 4, 5, 1. If a mistake occurs, select the node identification number in the ring map list and delete it using << Undo command button. * Define whether the protection channel will be used to carry low priority traffic in MSSPRing (1:1 Protection) or not, by checking the relevant Extra Traffic check box. Note

This option is available only for 2 Fibres MS-SPRing protection scheme. * Setup the Wait To Restore time (from 5 to 12 minutes), by using the relevant scroll list.

This time is expressed in minutes and represents the time waited by the system before switching back to the original working path, once it returns available. In case of 2 Fibres MS-SPRing: * Select from the Line West field, the line card connected with the first node identification number located in anticlockwise direction (West). * Confirm it clicking on West Work/Prot>> command button. * Select from the Line East field, the line card connected with the first node identification number located in clockwise direction (East). * Confirm it clicking on East Work/Prot>> command button. If some mistake occurs, remove the MS-SPRing configuration using <

339-1268/06

.

Navigation Page

88

Book Contents


* Confirm it clicking on West Work>> command button. * Select from the Line West field, the line card to act as protection connected with the first node identification number located in anticlockwise direction (West). * Confirm it clicking on West Prot>> command button. * Select from the Line East field, the line card to act as worker connected with the first node identification number located in clockwise direction (East). * Confirm it clicking on East Work>> command button. * Select from the Line East field, the line card to act as protection connected with the first node identification number located in clockwise direction (East). * Confirm it clicking on East Prot>> command button. If some mistake occurs, remove the MS-SPRing configuration using <
To delete a MS-SPRing * Click on a unit involved in the MS-SPRing, using the right button of the mouse. * Select the MS-SPRing protection item in the unit menu, the MS-SPRing Configuration window becomes accessible. * Click on the Delete button. See Also: Cross Connections: Path Info, MS-SPRing Cross Connection, MS-SPRing NUT, Specific Functions: MS-SPRing (ADM)

MS-SPRing Cross Connection Path

(Configuration -> MS-SPRing -> Cross Conn.)

This folder displays for a selected AU-4 channel the Source and the Destination Node identification numbers. Selecting the Cross Conn. folder, the Cross Connection window becomes accessible.


339-1268/06

.

Navigation Page

89

Book Contents


* Select an AU4 channel and its path information, if defined, are shown in Source Node and Destin. Node fields. The time slot interchange (TSI) information are not managed yet. By using the Request button, the Cross Conn. window will be updated. See Also: Cross Connections: Path Info, MS-SPRing Configuration, MS-SPRing NUT, Specific Functions: MS-SPRing (ADM)

MS-SPRing NUT Path (Configuration -> MS-SPRing ->NUT) This folder is used to manage the NUT and becomes accessible only if it has been configured a MS-SPRing NUT type. Selecting the NUT folder, the NUT window becomes accessible.


339-1268/06

.

Navigation Page

90

Book Contents


* Click on the Create Nut button to configure the type of NUT and the Create NUT window will be displayed.

* Select the NUT type in the scroll list and than click on the Apply button to confirm or the Cancel button After having configured the NUT type the Port NUT Info button becomes accessible. * Select an AU-4 channel. * Click on the Port NUT Info button and the Port NUT Info window will be displayed.

* Define the AU4 channel type, by clicking on it in the scroll list. The following channel types can be selected:


339-1268/06

.

Navigation Page

91

Book Contents


Absent The channel works normally NUT Ring The Ring Switchs are disabled on this channel while the Span Switchs are still enabled NUT The Ring and Span Switchs are disabled on this channel.

* Click on the Apply button to confirm the new configuration. See Also: Cross Connections: Path Info, MS-SPRing Configuration, Specific Functions: MSSPRing (ADM)

SOFTWARE INVENTORY Path ( Inventory -> Shelf Inventory -> Inventory Data (SW)) This function is used to display the software versions loaded on both memory FLASH banks and the software boot version loaded on the EPROM of the units present in the equipment. For each unit the relevant slot is specified. * Select the Inventory Data (SW) folder by clicking on the Inventory Data (SW) button in the upper part of the Inventory window. The Inventory Data (SW) window becomes accessible.

In Inventory window, information about the SW present in each slot are available. Next to the software version present on the FLASH banks there is also an indication of the active bank (*). To save the software inventory data on a file on the PC, click on Export button. See Also:


339-1268/06

.

Navigation Page

92

Book Contents


Hardware Inventory

HARDWARE INVENTORY Path (Inventory -> Shelf Inventory -> Inventory Data (HW)) This function is used to display the hardware versions of the units present in the equipment. For each unit the relevant slot is specified. * Select the Inventory Data (HW) folder by clicking on the Inventory Data (HW) button in the upper part of the Inventory window. The Inventory Data (HW) window becomes accessible.

In Inventory window, information about the HW present in each slot are available. To save the hardware inventory data on a file on the PC, click on Export button. See Also: SoftwaRe Inventory

CHANNEL OVERWIEW (ADM) Path (Inventory -> Channel Overview) This function is used to summarise the information regarding the configured HO Supervisory Unequipped monitoring, Tandem Connection, Equipment Protection and MSP.

To access general information: * Select the Channel Overview item in the Inventory menu. * Select the General folder.


339-1268/06

.

Navigation Page

93

Book Contents


In this folder the units, with the relevant channels, are displayed. The fields can show that the relevant unit channel is monitored (Mon), is using the HO Supervisory Unequipped (Hosu), is involved in a Tandem Connection (Tandem), has a loopback (Loop), etc.


339-1268/06

.

Navigation Page

94

Book Contents


To access Tandem Connection information: * Select the Channel Overview item in the Inventory menu. * Select the Tandem folder.

In this folder the units involved in a Tandem Connection are displayed. The Source field displays the particular unit channel; the Matrix Side and Line Side display how the Tandem Connection has been configured.

To access Equipment Protection information: * Select the Channel Overview item in the Inventory menu. * Select the Equip. Prot. folder.

In this folder the units involved in a Equipment Protection are displayed. The window displays in which slot there is the protected unit (Workers) and in which slot there is the protection unit (Prot.).


339-1268/06

.

Navigation Page

95

Book Contents


To access MSP information: * Select the Channel Overview item in the Inventory menu. * Select the MSP folder.

In this folder the configured MS Protections are displayed. For an MSP the following information are displayed: the MSP type (1+1, 1:N), the slots in which there are the protection and the protected units (Prot., Workers), if the MSP is Unidirectional or Bidirectional (Bidir.), if extra-traffic or DCC are managed (ExtraTr., DccProt.).

TERMINATION POINT LABELS (ADM) Path (Configuration -> Tp Labels) By selecting this item the Port Label window will be displayed.


339-1268/06

.

Navigation Page

96

Book Contents


The Tp Labels (termination point labels) of the configured units can be added, modified or deleted by using this window. The Resume button can be used whenever an update of the window is not automatically performed.

To add or modify a port label: * Select a port by clicking on it in the list. * Enter the new label or modify the old one in the text field. * Press Apply to confirm the new settings.

To delete a port label: * Select a configured port label by clicking on it in the list. * Delete it in the text field. * Press Apply to confirm the new settings. See Also: Label Operations Configuration (ADM)


339-1268/06

.

Navigation Page

97

Book Contents

MAINTENANCE AND FAULT MANAGEMENT In the following pages maintenance operations, such as software download and FLASH banks switch, and fault operation, such as alarm reporting are described.

TEST MODE Path (Maintenance -> Maintenance / Service State) By clicking on the Maintenance item, the Communication and Control Unit will be off-line. This command will affect the Communication and Control Unit database and will not be forwarded to the peripheral units. When the Communication and Control Unit is in maintenance mode the yellow LED on its front panel lights on and its graphical representation on the Control Application main window is yellow highlighted. To exit the Maintenance mode, select the Service option on the Communication and Control Unit menu. When the Service option is selected all the units will be reconfigured according to the new configuration database (if any). NOTICE

It is only allowed to add new configuration data to the existing database when the Communication and Control Unit is in Maintenance mode. In the new configuration you can add new data, but you can not neither delete the existing ones nor replace them with other ones. The new configuration must be a superset (or at least equal) of the previous one. In order to force a different configuration it is necessary to perform a System Restart after the Service mode (that will affect the traffic).

See Also: Specific Functions: Maintenance/Service

SOFTWARE DOWNLOAD Path (Maintenance -> Software Download) [LC] This item is used to download the application software on the units (via local or remote login).


339-1268/06

.

Navigation Page

Book Contents

MSHXXX - OPERATOR’S HANDBOOK MAINTENANCE AND FAULT MANAGEMENT

The Communication and Control Unit software is contained in a file bigger than 1.4Mbyte; for this reason this file is split into two or three diskettes.

To perform a software download operation using diskettes: * Create a temporary directory on the hard disk. * Copy the content of the diskettes in the temporary directory (the diskettes contain files with the same name X4xxxxxx.00y but each of them is identified by a different extension: for example .001, .002, .003, etc.). * Copy the program MERGE.EXE in the temporary directory. * In order to rebuild the controller module, execute in the temporary directory the program MERGE.EXE as following: merge.exe C1xxxxxx C1xxxxxx.C3D

where X4xxxxxx.C3D is the destination file in which the source files will be merged. IMPORTANT The destination file name must be the same of the Communication and Control Unit one in the download.ini file. * Remove the temporary files: del X4xxxxxx.001 del X4xxxxxx.002 del *.EXE

* Move the program files from the temporary directory to the Control Application’s installation directory. * Copy the download.ini file from the Control Application’s installation disk, to the Control Application’s installation directory. * Select the Software Download item in the Maintenance menu.


339-1268/06

.

Navigation Page

100

Book Contents


* Select the unit types to upgrade, by checking them in the available list. * Start the download operation by clicking on the Start button. Click on the Hide button to have the download operation performed in background mode (other operations can be performed on the equipment while the software download takes place). See Also: Bank Switch, Common Functions: Bank Switch, Common Functions: Software Commit, Software Commit

BANK SWITCH Path (Maintenance -> Bank Switch) This item is used to perform a bank switch, after a software download operation from the Maintenance menu (a confirmation is required to the operator). This operation, performed on all the upgraded units, consists in a change of the active FLASH banks (the software download operation is performed on the inactive FLASH banks). A switch on the old software version can not be performed using this item. IMPORTANT After the completion of bank switch procedure on the Communication and Control Unit, remember to exit Control Application and connect with new Control Application’s software. See Also: Common Functions: Bank Switch, Common Functions: Software Commit, Software Download, Software Commit, Software Download

SOFTWARE COMMIT Path (Maintenance -> Software Commit) This item is used to validate a new software version, after a bank switch operation from the Maintenance menu (a confirmation is required to the operator). A FLASH bank with new loaded application software should be validated by means of this operation, to confirm the new software version. If the software commit isn't executed, the new software version can be used until an equipment switch off, a unit extraction, a unit reset or a system restart happens; after these events the unit will switch on the old FLASH bank. A software commit on the old software version can not be performed using this item. See Also: Bank Switch, Common Functions: Bank Switch, Common Functions: Software Commit, Software Download

MIB RESET Path (Maintenance -> MIB Reset) By selecting the MIB Reset item in Maintenance menu, the equipment configuration database is erased (after confirmation).

MIB UPLOAD Path (Maintenance -> MIB Upload) [LC]


339-1268/06

.

Navigation Page

101

Book Contents


This function is used to store the configuration database on a CDL file. NOTICE

Before performing a cdl upload please check that all protections are in “No Request State”. This means that no active alarms must be present on the NE.

To save the MIB on a CDL file: * Select the item MIB Upload in the Maintenance menu. * Select Upload Network Element to save the complete NE configuration in a CDL file. * You can also save a partial configuration database just selecting the desired items. * One or more items can be selected at the same time for creating a customised configuration database. * Click on Start to activate the file selection folder.

To select the file to be uploaded: * Select the driver and the folder where to save the file. * Digit the desired file name ended with the extension cdl. * Press OK. See Also: Script Execution Button, Specific Functions: MIB Upload

SCRIPT EXECUTION Path (Maintenance -> Execution of Scripts) [LC] This item is used to execute CDL scripts, with predefined configuration sequences. By selecting this item in the Maintenance menu, the CDL Interpreter window becomes accessible.

To execute a CDL script: * Use the Load button to get a CDL file. A file selection window will be displayed. * Select the CDL file to be loaded. * Use the Start button to execute the script.


339-1268/06

.

Navigation Page

102

Book Contents


* Use the Edit button to modify the uploaded CDL file. * Use the Parse button to perform the syntactic control of the script file. IMPORTANT The MIB can be stored on a CDL file, therefore the download of the MIB is performed using the CDL Interpreter. See Also: MIB Upload, Specific Functions: MIB Upload

REALIGN SHELF Path (Maintenance -> Realign Shelf) With this menu, the operator can perform a refresh of all the equipment functions.

ALARM LOG REPORTING Path (Fault Management -> Alarm Log/Reporting -> Reporting) This option is used to enable filtering or to disable the alarm/event report to the Network Element Manager.

To disable the alarm/event report: * Check on Locked check button. In this configuration the alarms/events detected into the equipment will be not forwarded to the Control Application and the Network Management Centre. * Click on the Apply button to set the parameters or Close to exit the ”Alarm report” data configuration. NOTICE When the Locked check box is checked the spontaneous event reporting from the NE is completely disabled. That will affect


339-1268/06

.

Navigation Page

103

Book Contents


the Control Application behaviour: e.g. no unit extraction or alarm is detected in real time.

To enable/filter the alarm/event report: * Verify that Locked box is not checked. * Check the Default EFD check button in order to send to the Network element Manager all the events and alarms. * In the Severity area, the operator can enable or disable the alarm report recording to the alarm severity, by checking or not the relevant check box. * In the Alarm type area, the operator can enable or disable the alarm report recording to the alarm type, by checking or not the relevant check box. * In the AIS/RDI reporting area, the operator can enable or disable the report of the AIS and RDI alarms, by checking or not the relevant check box. * In the Other Notifications area, the operator can enable or disable the alarm report recording to a state change or a change in an attribute value, by checking or not the relevant check box. * Use the F4 Time (Sec) scroll list to set the persistence of an alarm condition (expressed in seconds) before the system emits an alarm indication. * Click on the Apply button to set the parameters or Close to exit the ”Alarm report” data configuration. See Also: Common Functions: Alarms, Log Records, Alarm Log Reporting

LOG SETUP Path (Fault Management-> Alarm Log/Reporting -> Log Setup) This option is used to enable the alarm/event report into a log file and to set the ‘Log Full’ alarm threshold. The alarm log file can contain a maximum number of 200 events and/or alarms. Using the ‘Log Full’ alarm threshold, the operator can set a threshold for the number of detected events/alarms: when this threshold is exceeded, a ‘Log Full’ alarm indication will be displayed.


339-1268/06

.

Navigation Page

104

Book Contents


This window contains all the settings for the log file implemented on the equipment.

To disable the alarm/event report: * Check on Locked check button.

To enable the alarm/event report into the log file: * Verify that Locked box is not checked.

To set the ‘Log Full’ alarm threshold: * Verify that the alarm/event report is enabled. * Select the Alarm threshold (0 to 100%) using the relevant scroll list. It is expressed as the occupied percentage of the Log. Four different thresholds are available and are used to emit different warning messages on Control Application. * Select Discriminator Construct parameters (Any notification, Alarms, Alarms and Events) in order to decide which types of alarms/events have to be stored in the log file. * Select the mode of storage in the log file in the Log Full Action field; Halt parameter indicates that alarm/event collection is stopped when the threshold is reached, Wrap parameter indicates that oldest alarm/event information are overwritten by the new ones when the threshold is reached. * Click on the Apply button to set the parameters or Close to abort the ‘Log Full’ data configuration. * Click on the Clear All Log to reset the alarm log file. See Also: Alarm Log Reporting, Common Functions: Alarms, Log Records

LOG RECORDS Path (Fault Management -> Alarm Log/Reporting -> Log Records)


339-1268/06

.

Navigation Page

105

Book Contents


Using this function the operator can view all the alarms/events stored by equipment in the log file. IMPORTANT This will be available only if the Log Setup window in (Fault -> Alarm Log/Reporting -> Log Setup) the Locked check box is not checked.

To view the details relevant to an alarm/event stored: * Select a stored alarm/event, by clicking on it in the scroll list. According to the different types of selected data, different details will be available.

To save the Log on a file: * Click on the Export Log button. A Save As window will be displayed. * Insert the name of the file. * Confirm the operation by clicking on the OK button. See Also: Alarm Log Reporting, Common Functions: Alarms

ALARM REPORTING Path (Fault Management -> Alarm Log/Reporting -> Alarm Reporting) Using this function the operator can view all the alarms which parameters has been modified and can restore the default settings.


339-1268/06

.

Navigation Page

106

Book Contents


The alarm parameters relevant to a selected unit can be modified using the Alarm Severity common function.

To restore the original settings: * Click on the Default button. See Also: Alarm Log Reporting, Common Functions: Alarms, Log Setup

ALARM SEVERITY Path (Fault Management -> Alarm Log/Reporting -> Alarm Severity) Using this function the operator can view all the alarms which severity parameter has been modified by the operator and can restore the default settings.


339-1268/06

.

Navigation Page

107

Book Contents


The alarm parameters relevant to a selected unit can be modified using the Alarm Severity common function.

To restore the original settings: * Click on the Default button. See Also: Alarm Log Reporting, Common Functions: Alarms, Log Setup

CLEAR WINDOW ALARMS Path (Fault Management -> Clear Window Alarms) With this menu, the operator can delete all the alarms/events present in the Alarm and Event Monitoring window.

ACTIVE ALARMS Path (Fault Management -> Active Alarms) With this menu, the operator can delete all the inactive alarms/events present in the Alarm and Event Monitoring window; on this window only the active alarms/events remain


339-1268/06

.

Navigation Page

108

Book Contents

UNIT FUNCTIONS The unit functions are accessible by clicking on the units in the main window. Some functions are common for every type of unit, some other are specific.

COMMON FUNCTIONS: CREATE NOTICE

This function is present on every type of unit, except on the Communication and Control Unit and on the End Of Shelf Unit.

If a unit is not configured it can be created by clicking on the unit itself, on the main window, and selecting the item Create in the scroll menu.

To create a new unit: * Click on the selected unit, using the right button of the mouse. * Select the Create item in the unit menu. The Select Unit Type window becomes accessible.

* Select the desired unit by clicking on it in the list. * Confirm the selection by clicking the OK button.


339-1268/06

.

Navigation Page

Book Contents

MSHXXX - OPERATOR’S HANDBOOK UNIT FUNCTIONS

All the available traffic interfaces that can be created are written in the following list: ADM-64 STM-64 Opt

ADM-16

ADM-4

REG-64

X

X

STM-64 Opt for X DWDM

X

STM-16 Opt

REG-4/16

X

X

X

STM-16 Opt High X Power

X

X

STM-16 FOR X Integrated WDM

X

X

STM-16 Opt for X DWDM

X

X

STM-16 Opt for X Metro

X

X

STM-4 Opt

X

X

X

X

X

STM-1 Opt STM-1 El

X

2xSTM-1 Opt

X

X

4xSTM-1 Opt

X

X

1x140/155Mbit/s (VC-12) El

X

X

2x140/155Mbit/s (VC-4) El

X

2x140/155Mbit/s (VC-12) El 4x140/155Mbit/s (VC-4) El

X

X X

X

X

3x34/45Mbit/s

X

32x1,5/2Mbit/s

X

63x1,5/2Mbit/s

X

Booster +10, +12, X +16

X

Booster +17

X

Preamplifier

X

X

X

X

X

X

X

X

X

X

2 Channel Bidir. X WDM

X

X

X


339-1268/06

.

Navigation Page

110

Book Contents


ADM-64

ADM-16

Mux

X

X

X

Demux for DWDM

X

X

X

Demux for X Integrated WDM

X

X

Splitter

X

X

X

Combiner

X

X

X

Pre & OSC EXT

X

X

X

OSC X

X

X

Metro Filter

X

X

Gigabit Ethernet

X

X

Pre & EXT/INS

ADM-4

REG-64

REG-4/16

See Also: Common Functions: Delete

COMMON FUNCTIONS: ALARMS In a configured unit the log of active alarms/events can be displayed by clicking on the unit itself and selecting the Alarms item in the scroll menu.

To access the active alarms of a unit: * Click on the selected unit, using the right button of the mouse. * Select the Alarms item, in the unit menu. The Alarms/Events window relevant to the unit will become available.


339-1268/06

.

Navigation Page

111

Book Contents


In this window the operator can see the active alarms on the unit. The Refresh button can be used whenever an update of the active alarms is not automatically performed. See Also: Alarm Log Reporting, Log Records, Log Setup

COMMON FUNCTIONS: ALARM SEVERITY The operator can display an alarm severity configuration window for a configured unit or for a single channel. In the first case, the operator has to click on the desired unit and select the Alarm Severity item in the unit menu. The window will display only the hardware alarm of the selected unit. In the second case, the operator has to click on the desired unit, select the Channels item in the unit menu and click on the Alarm Management button (for the Booster and the Preamplifier unit, select the Optical Measure option in the unit menu: the Alarm Management button will become accessible). The window will display different alarms according to the different channel types.

* Disable/enable the reporting of the alarms relevant to this source, by selecting/deselecting the Alarm Inhibit check box. * Select the alarm category (Urgent, Not urgent or Indication) by acting on the Alarm Severity scroll list. * Choose the fault action by selecting the relevant check box: AIS cons. action to enable the injection of AIS, RDI cons. action to enable the injection of RDI. * Press Default to set all the alarms to their original settings. * Click on Apply to confirm the latest configurations. See Also: Alarm Log Reporting, Log Records, Log Setup


339-1268/06

.

Navigation Page

112

Book Contents


COMMON FUNCTIONS: DELETE NOTICE

This function is present on every type of unit, except on the Communication and Control Unit and on the End Of Shelf Unit.

When a unit is configured it can be deleted by clicking on the unit itself and selecting the Delete item in the scroll menu.

To delete a unit: * Click on the selected unit, using the right button of the mouse. * Select the Delete item, in the unit menu. See Also: Common Functions: Create

COMMON FUNCTIONS: UNIT RESET A configured unit can be reset clicking on the unit itself and selecting the item Unit Reset in the scroll menu.

To restart the microprocessor of a unit: * Click on the selected unit, using the right button of the mouse. * Select the Unit Reset item, in the unit menu. IMPORTANT For a ”in traffic” unit the reset operation is not hitless. This function is present on every type of unit, except on the End Of Shelf Unit. See Also: Specific Functions: System Restart

COMMON FUNCTIONS: BANK SWITCH This item is used to perform a bank switch for the single unit. IMPORTANT The database compatibility is not granted when the operator performs a bank switch towards an old software version on the Communication and Control Unit. See Also: Bank Switch, Common Functions: Software Commit, Software Commit, Software Download

COMMON FUNCTIONS: SOFTWARE COMMIT This item is used to validate a new software version, after a bank switch operation. A FLASH bank with the application software should be validated by means of this operation, to confirm the current software version. If the software commit isn’t executed, the current software version can be used until an equipment switch off, a unit extraction, a unit reset or a system restart happens; after these events the unit will switch on the previously committed FLASH bank. See Also: Bank Switch, Common Functions: Bank Switch, Software Commit, Software Download


339-1268/06

.

Navigation Page

113

Book Contents


COMMON FUNCTIONS: PROPERTY When a unit is configured, its inventory data are accessible by clicking on the unit, in the main window, and selecting the item Property in the scroll menu.

To access the inventory data of a unit: * Click on the selected unit, using the right button of the mouse. * Select the Property item, in the unit menu. The Inventory window becomes accessible.

In this window information about the HW (equipment code and serial number) and about the SW (SW versions present in the boot EPROM and in the FLASH banks) are available. Next to the SW version present on the FLASH banks there is also an indication of the in-use bank (it is indicated with a check mark).

SPECIFIC FUNCTIONS: MIB RESET This function is present on the Communication and Control Unit. By clicking on the Communication and Control Unit, for the Type D in the MAN section, on the main window and selecting the MIB Reset item in the scroll menu, the equipment configuration database is erased (after confirmation).

SPECIFIC FUNCTIONS: MIB UPLOAD Path [LC] This function is present on the Communication and Control Unit.


339-1268/06

.

Navigation Page

114

Book Contents


By clicking on the Communication and Control Unit on the main window and selecting the MIB Upload item in the scroll menu, the equipment configuration database can be saved in a CDL file. NOTICE

Before performing a cdl upload please check that all protections are in “No Request State”. This means that no active alarms must be present on the NE.

To save the configuration database in a CDL file: * Select Upload Network Element to save the complete NE configuration in a CDL file. * You can also save a partial configuration database just selecting the desired items. * One or more items can be selected at the same time for creating a customised configuration database. * Click on Start to activate the file selection folder.


339-1268/06

.

Navigation Page

115

Book Contents


To select the file to be uploaded: * Select the driver and the folder where to save the file. * Digit the desired file name ended with the extension cdl. * Press OK. See Also: MIB Upload

SPECIFIC FUNCTIONS: MAINTENANCE/SERVICE This function is only present on the Communication and Control Unit. By selecting the Maintenance item the Communication and Control Unit, for the Type D in the MAN section, will be off-line. This is indicated on the main window as Communication and Control graphical representation highlighted in yellow. To restore normal operation, the operator has to select the Service menu again. See Also: Test Mode

SPECIFIC FUNCTIONS: LAMP TEST This function is present on the End Of Shelf Unit only. It is used to perform a test on the End Of Shelf Unit LEDs.

SPECIFIC FUNCTIONS: OUTPUT QUALITY (ADM) This function is present only on the SDH units. This function is used to manage the synchronisation source quality sent as clock reference outputs by the equipment.

* Select the synchronisation source to be modified by clicking on it.


339-1268/06

.

Navigation Page

116

Book Contents


* Deselect the Do not overwrite box and set the new quality in the relevant list. * Confirm the new settings, by clicking on the Apply button. See Also: Synchronisation Output Quality (ADM)

SPECIFIC FUNCTIONS: LASER CONFIGURATION This function is present only on the optical units. This function is used to perform actions on an optical unit laser (i.e. Manual restart, Automatic Restart, to disable the Automatic Laser Shutdown, etc.) NOTICE

Before performing any laser configuration please refer to the Safety Rules handbook.

To perform action on a laser: * Click on the desired optical unit, using the right button of the mouse. * Select the Laser Configuration item, in the unit menu. The Laser Configuration window will become accessible.

The available options are: Man. Rest. (2 sec) (Short Manual Restart) the laser is re-activated for 2 seconds, for testing purposes Man. Rest. (90 sec) (Long Manual Restart) the laser is re-activated for 90 seconds, for testing purposes. Aut. Rest. (2 sec after 60 sec) (Automatic Restart 60 seconds) the laser is automatically re-activated for two seconds every 60 seconds Aut. Rest. (2 sec after 180 sec) (Automatic Restart 100 seconds) the laser is automatically re-activated for two seconds every 100 seconds


339-1268/06

.

Navigation Page

117

Book Contents


Aut. Rest. (2 sec after 300 sec) (Automatic Restart 300 seconds) the laser is automatically re-activated for two seconds every 300 seconds Laser on – ABN on the laser is forced on, the ABN led is switched on Laser off – ABN on the laser is forced off, the ABN led is switched on Laser off - ABN off the laser is forced off, but no abnormal condition is displayed (the yellow LEDs on the optical unit and the EOS remain OFF) Laser on - ABN off the laser is forced on, but no abnormal condition is displayed (the yellow LEDs on the optical unit and the EOS remain OFF)

* If the selected optical unit is a NxSTM-1 Optical/Mux Unit, N folders (Laser1 to LaserN) will be accessible in the Laser Configuration window. * Click on the Apply button to confirm the latest configurations.

SPECIFIC FUNCTIONS: MSP PROTECTION (ADM) This function is present only on the STM-n units. This function is used to perform action on an existing MSP group (i.e. forced switch, manual switch, etc.). By clicking on an STM-n unit on the main window and selecting the MSP Protection item in the scroll menu, the MSP Protection menu becomes accessible.

To access the MSP functions: * Click on the selected unit, using the right button of the mouse. * Select the MSP Protection item, in the unit menu. The MSP Protection window becomes accessible.


339-1268/06

.

Navigation Page

118

Book Contents


A list of the units belonging to the MSP Protection group is displayed in the upper part of the folder, together with information relevant to their port identifier (MS#), the Protection Status (Local SF Switch Pend, Auto Switch (SF), No Request, etc.), the State (Service or Stand-by) and the Priority (it can be set for 1:N Protection). * Change, if necessary, the protection settings in the relevant area (Revertive, Not revertive, Bidirectional; Unidirectional protection is a default setting). * If a Revertive protection was set, the operator can modify the Wait to Restore time, using the relevant scroll list. * Click the Apply button to confirm the latest configurations.

To access the MSP protection data: * Click on the Protection Data button. The Protection Data window will appear. See Also: Performance: All Performances, Performance Management: Threshold Profiles, MSP Switch Operations (ADM), Specific Functions: MSP Protection (ADM)

MSP Switch Operations (ADM) To perform a Manual Switch on a MSP group: * Select the stand-by unit by clicking on it in the list. * Click on the Manual switch button. A letter ’W’ or ’P’ indicates whether the switch is performed towards the Working or Protection unit. If the stand-by unit is not available the system does not execute the switch.

To perform a Forced Switch on a MSP group: * Select the stand-by unit by clicking on it in the list. * Click on the Forced switch button. A letter ’W’ or ’P’ indicates whether the switch is performed towards the Working or Protection unit. In this case the system always executes the switch to the stand-by unit.

To disable the use of a unit in a MSP group: * Select the unit to be excluded by clicking on it in the list. * Click on the Lockout button. By acting this way the selected unit are not deleted from the list, but they are not used until the operator decides to activate them again.

To return from a switch or a lockout operation in a MSP group: * Select the unit on which a switch or lockout operation has been performed, by clicking on it in the list. * Click on the Clear button. See Also:


339-1268/06

.

Navigation Page

119

Book Contents


MSP Protection (ADM), Specific Functions: MSP Protection (ADM)

SPECIFIC FUNCTIONS: EQUIPMENT PROTECTION (ADM) This function is used to manage the protection switch operations and the equipment protection configuration. It is available for the following units: n 32x1.5/2Mbit/s Tributary Unit (1:N Protection with 1£N£4) (ADM-4); n 63x1.5/2Mbit/s Tributary Unit (1:N Protection with 1£N£4) (ADM-4); n 3x34Mbit/s Tributary Unit (1+1 Protection) (ADM-4); n 3x45Mbit/s Tributary Unit (1+1 Protection) (ADM-4); n STM-1 Electrical/Mux Unit (1:N Protection with 1£N£4) (ADM-4); n 2x140/155Mbit/s Tributary Unit (1:N Protection with 1£N£2) (ADM-4); n 2x140/155Mbit/s Tributary Unit (1:N Protection with 1£N£4) (ADM-16); n 4x140/155Mbit/s Tributary Unit (1:N Protection with 1£N£4) (ADM-16) / (ADM-64); n switch unit (1+1 Protection). By selecting this item, the Equipment protection window becomes accessible.

A list of the units belonging to the Equipment Protection group is displayed in the upper part of the window, together with information relevant to the Protection Status (Local SF Switch Pend, Auto Switch (SF), No Request, etc.) and the State (Service or Stand by).

To modify the parameters of an existing protection group: * The operator can modify the protection type (Revertive or Not revertive), by checking the relevant radio button. * In case of a Revertive protection, the operator can change the Wait to Restore time. IMPORTANT For the Switch Unit the protection is always Not revertive.


339-1268/06

.

Navigation Page

120

Book Contents


To perform a Manual Switch: * Select the unit (working or protection one) to switch to, by clicking on it in the scroll list. * Click on the Manual Sw. button. A letter ’W’ or ’P’ indicates whether the switch is performed towards the Working or Protection unit. If this second unit is not available the system does not execute the switch.

To perform a Forced Switch: * Select the unit (working or protection one) to switch to, by clicking on it in the scroll list. * Click on the Forced Sw. button. A letter ’W’ or ’P’ indicates whether the switch is performed towards the Working or Protection unit. Even if this second unit is not available the system executes the switch. If the unit, to which a forced switch has been performed, gets failed, no protection switch takes place.

To disable the use of a unit within a protection group: * Select the unit (working or protection one) to be disabled, by clicking on it in the scroll list. * Click on the Lockout button.

To cancel a previous Lockout operation of a unit within a protection group: * Select the previously disabled unit, by clicking on it in the scroll list. * Click on the Clear button.

To cancel a previous Switch operation of a unit within a protection group: * Select the unit on which the switch has been performed, by clicking on it in the scroll list. * Click on the Clear button. IMPORTANT For the Switch Unit, only the forced switch is available. See Also: Equipment Protection (ADM), Common Functions: Create

SPECIFIC FUNCTIONS: MS-SPRING (ADM) This function is used to manage the protection switch operations and the protection configuration. It is available for the units involved in the MS-SPRing scheme.

Specific Functions: MS-SPRing Manual Command/BSHR Status Via this folder is possible set manual commands and view the protection status. By clicking on the Man Cmd/BSHR Status. button the Manual command/Bidirectional Self Healing Ring protection window becomes accessible.


339-1268/06

.

Navigation Page

121

Book Contents


Different commands are available for the two sides of the ring (West and East).

To lock the switch protection function on ring configuration: * Click on the Lock W ring (Lockout on working channels - ring switch) command button. This command prevents the working channels, over the addressed span, from accessing the protection channels for a ring switch. This is obtained by disabling the response of the node to a request of ring protection switch of any kind. If any working traffic channel is already on protection, the ring bridge is dropped regardless of the condition of the working channels. If no other bridges requests are active on the ring, the No request code is transmitted. This command has no impact on the use of protection channels for any other span. For example the node can go into any of pass-through modes.


339-1268/06

.

Navigation Page

122

Book Contents


To lock the switch protection function on local span: This command is available only if a 4 fibre MS-SPRing configuration is configured. * Click on the Lock W span (Lockout on working channels - span switch) command button. This command prevents the working channels, over the addressed span, from accessing the protection channels for a span switch. If any working traffic channel is already on protection, the span switch is dropped regardless of the condition of the working channels. If no other bridges requests are active on the ring, the No Request code is transmitted. This command has no impact on the use of protection channels for any other span.

To clear a lock command: * Click on the Clear command button. This command reset all the previously lock commands.

To force a switch protection function on ring: * Click on the Forced P (Forced switch working to protection - ring) command button in Ring area This command performs the ring switch from working channels to protection channels for the span between the node at which the command is initiated and the adjacent node to which the command is destined. This switch occurs regardless of the state of the protection channels unless the protection channels are satisfying a higher priority bridge request.

To set a manual switch protection function on ring: * Click on Manual P (Manual switch - ring) command button in Ring area This command performs the ring switch from working channels to protection channels for the span between the node at which the command is initiated and the adjacent node to which the command is destined. This occurs if the protection channel is not in signal degrade condition and are not satisfying an equal or higher priority bridge request, including failure of the protection channels.

To test the ring switch protection function: * Click on the Exercise command button in Ring area This command exercises ring protection switching of the requested channel without completing the actual bridge and switch. This command is issued and the responses are checked, but no working traffic is affected.


339-1268/06

.

Navigation Page

123

Book Contents


To force a switch protection function on local span: This command is available only if a 4 fibre MS-SPRing configuration is configured. * Click on the Forced P (Forced switch working to protection - span) command button in Span area. This command switches the traffic from the working channels to protection channels of that span. This switch occurs regardless of the state of the protection channels unless the protection channels are satisfying a higher priority bridge request or a signal failure or a K byte failure exists on the protection channels of the span.

To set a manual switch protection function local span: This command is available if a 4 fibre MS-SPRing configuration is defined only. * Click on the Manual P (Manual switch - span) command button in Span area. This command performs the ring switch from working channels to protection channels for the same span on which the command is initiated. This occurs if the protection channel is not in signal degrade condition and are not satisfying an equal or higher priority bridge request, including failure of the protection channels.

To test the span switch protection function: * Click on the Exercise command button in Ring area This command exercises span protection switching of the requested channel without completing the actual bridge and switch. This command is issued and the responses are checked, but no working traffic is affected.

To switch the working traffic on protection channel : This command is available only if a 4 fibre MS-SPRing configuration is configured. * Click on the Lock P span (Lockout of protection - span) command button. This command prevents the usage of the span for any protection activity. If any working traffic is already using the protection on this span, this command causes this traffic to switch back to the working channels. Thus, all ring switching that uses the protection capacity of the locked-out span is prevented and prompted. Span switching is prevented only on the locked-out span.


339-1268/06

.

Navigation Page

124

Book Contents


To lock the switch protection function on ring spans: This command is available only if a 4 fibre MS-SPRing configuration is configured. * Click on the Lockout - all span - all span command button. This command prevents protection switching on the entire ring. If any working traffic channel is using the protection facility on any span this command causes working traffic to switch back to working channels regardless of the condition of the working channels. Note that the K1 and K2 bytes do not support this command. Thus, the command has to be sent to each of the network element and the Lockout of Protection - Span request is used by each network element to coordinate activities with the far end.

To clear a ring switch command: * Click on the Clear command button. This command reset all the previously ring switch (forced/manual), span switch (forced/manual) and exercise commands.

To delete a MS-SPRing: * Click on the Delete command button to remove the MS-SPRing scheme. See Also: MS-SPRing Configuration, MS-SPRing Cross Connection, Section Status Info, MSSPRing NUT, West/East Info

Section Status Info Section Status information indicates the local node status. The local node status could assume the following value: n Idle: a node that is not generating, detecting or passing-through bridge requests or bridge request status information; n Bridged-Switched: the action of transmitting identical traffic on both the working and protection channels; n Full pass-through: the action of transmitting the same K1, K2 and protection channels that are being received. Full pass-through is bidirectional; n K Bytes pass-through: the action of transmitting the same K1 and K2 bytes that are being received. Protection channels are not passed through. K-byte pass-through is bidirectional. See Also: Specific Functions: MS-SPRing Manual Command/BSHR Status

West/East Info In these fields are reported information concerning the local node section status. If the local node status is Idle the card status west Working/Protection, east Working/Protection are in No request status. If the local node status is Bridged-Switched, Full pass-through or K Bytes pass-through in the West/East Info area are reported information about the local node status causes: n local or remote failure;


339-1268/06

.

Navigation Page

125

Book Contents


n lockout command (locked); n wait to restore during a MS-SPRing re-routing configuration. See Also: Specific Functions: MS-SPRing Manual Command/BSHR Status

Specific Functions: MS-SPRing Cross Connection This folder displays for a selected AU-4 channel the Source and the Destination Node identification numbers. Selecting the Cross Conn. folder, the Cross Connection window becomes accessible.

* Select an AU4 channel and its path information, if defined, are shown in Source Node and Destin. Node fields. The time slot interchange (TSI) information are not managed yet. By using the Request button, the Cross Conn. window will be updated. See Also: Cross Connections: Path Info, MS-SPRing Configuration, Specific Functions: MSSPRing Manual Command/BSHR Status

Specific Functions: MS-SPRing NUT This folder is used to manage the NUT and becomes accessible only if it has been configured an MS-SPRing NUT type. Selecting the NUT folder, the NUT window becomes accessible.


339-1268/06

.

Navigation Page

126

Book Contents


* Click on the Create Nut button to configure the type of NUT and the Create NUT window will be displayed.

* Select the NUT type in the scroll list and than click on the Apply button to confirm or the Cancel button After having configured the NUT type the Port NUT Info button becomes accessible. * Select an AU-4 channel. * Click on the Port NUT Info button and the Port NUT Info window will be displayed.

* Define the AU4 channel type, by clicking on it in the scroll list. The following channel types can be selected: Absent The channel works normally


339-1268/06

.

Navigation Page

127

Book Contents


NUT Ring The Ring Switchs are disabled on this channel while the Span Switchs are still enabled NUT The Ring and Span Switchs are disabled on this channel.

* Click on the Apply button to confirm the new configuration.

SPECIFIC FUNCTIONS: GROUND CONTACTS This function is only present on the End Of Shelf Unit. This function is also accessible by selecting Configuration -> Ground Contacts in the main menu or by clicking the Ground Contacts Button in the toolbar, and it is used to configure the input and output ground contacts.

To access the ground contact settings: * Click on the End Of Shelf Unit, using the right button of the mouse. * Select the Ground Contacts item, in the unit menu. The Ground Contacts window becomes accessible. * Proceed as described in Section ”Configuration and Inventory”. See Also: Ground Contacts

SPECIFIC FUNCTIONS: SYSTEM RESTART This function is only present on the Communication and Control Unit. All the configured units can be reset clicking on the Communication and Control Unit, for the Type D in the MAN section, and selecting the System Restart item in the scroll menu.

To restart the microprocessor of all the units: * Click on the Communication and Control Unit, using the right button of the mouse. * Select the System Restart item, in the unit menu. By acting this way each unit micro-controller is restarted. This operation is the same as a unit reset performed on every unit (except on the End Of Shelf Unit). IMPORTANT This operation is not hitless; during the restart period the traffic will be affected. See Also: Common Functions: Unit Reset

SPECIFIC FUNCTIONS: PORTS SETUP (ADM) This item is accessible only on Nx140/155Mbit/s Tributary Units and is used to define, for each port, the traffic rate (140Mbit/s or 155Mbit/s).

To configure the ports of a Nx140/155Mbit/s Tributary Unit: * Click on the selected unit, using the right button of the mouse. * Select the Ports Setup item in the unit menu. The Port Configuration window will be displayed.


339-1268/06

.

Navigation Page

128

Book Contents


* For each port select the traffic type. When the port is used for Cross-Connections, Synchronisation, DCC, etc., it is not possible to change its traffic type. In the relevant Port field the radio buttons are shown in a grey colour and a string is shown to indicate the current state of the port. * Press OK to confirm. See Also: Common Functions: Create

LOOPBACK Loopback connections are diagnostic tools used by the equipment to locate the fault on a specific part of the network. By means of these loopbacks, after the detection of an alarm on a traffic unit, the source of a fault can be isolated. If the operator performs a loopback on an STM-N unit, he performs the loopback on all the N AU-4 of the STM-N unit. In this case the operator has to click on the relevant unit and select the Channels item; in the General folder the Loopback button is available. If the operator performs a loopback on a PDH unit he has to choose the port on which the loopback will be performed. In this case the operator has to click on the relevant unit and select the Channels item; in the resulting window the Loopback button is available and is related to the selected port. Clicking on the Loopback push button, the Loopback window will be displayed.


339-1268/06

.

Navigation Page

129

Book Contents


In order to select the desired loopback type: * Check the relevant radio button. The available loopback types are: Front End Transparent if the operator needs the incoming signal looped back and, at the same time, transmitted forward the Switch Unit Back End Transparent if the operator needs the outgoing signal looped back and, at the same time, transmitted forward the output interface Front End Non Transparent if the operator needs the incoming signal looped back but an AIS signal transmitted forward the Switch Unit Back End Non Transparent if the operator needs the outgoing signal looped back but an AIS signal transmitted forward the output interface Disable if the operator needs to disable the Loopback function

* Click on the Apply button to confirm the latest configurations. Not all the units are able to support all the loop-back configurations. In the following a detailed table is given relevant to the equipment types and the loopback types: UNIT

FET

BET

FENT

BENT

Stm-64 Optical/ Mux unit

X

X

X

X

Stm-64 Optical/ Mux Unit for DWDM

X

Stm-16 Optical/ Mux unit

X

X

Stm-16 Optical/ Mux Unit for DWDM

X

STM-16 Optical/ Mux for Integrated WDM

X

STM-16 Optical/ Mux Unit for Metro Applications

X

STM-16 High Power Optical/ Mux Unit

X

Stm-4 Optical/ Mux unit type 1

X

X

X

X

UNIT

FET

BET

FENT

BENT

Stm-4 Optical/ Mux unit type 1a

X

X

X

X

Stm-4 Optical/ Mux unit type 2

X

X

X

X

2XStm-1 Optical/ Mux unit type 2

X

X

X

X

2XStm-1 Optical / Mux unit type 3

X

X

X

X

4xStm-1 Optical / Mux unit

X

X

X

X

Stm-1 electrical/ Mux unit type 1

X

X

X

X

X

X

X

Stm-1 electrical/ Mux unit type 2


339-1268/06

X

.

Navigation Page

130

Book Contents


Stm-1 Optical /Mux unit type 2

X

Stm-1 Optical /Mux unit type 3

X

4X140/155Mbit/s (VC-4) Tributary unit

X

2X140/155Mbit/s (VC-4) Tributary unit

X

X

X

X

X

X

X

X

X

X

X

2X140/155Mbit/s (VC-12) Tributary unit type 2

X

X

X

X

2X140/155Mbit/s (VC-12) Tributary unit type 3

X

X

X

X

3X34Mbit/s Tributary unit

X

X

X

X

3X45Mbit/s Tributary unit

X

X

X

X

63X1.5/2Mbit/s Tributary unit

X

X

X

X

32x1.5/2Mbit/s Tributary unit

X

X

X

X

Gigabit Ethernet unit

X

X

8xFast Ethernet unit

x

x

FET = Front End Transparent,BET = Back End Transparent, FENT = Front End Non Transparent, BENT = Back End Non Transparent See Also: STM-n Units Loopback Management, nx140/155Mbit/s Units Loopback Management, 34-45Mbit/s Units Loopback Management, 2Mbit/s Units Loopback Management, Gigabit Ethernet Loopback Management

TANDEM CONNECTION (ADM) This option allows defining the Tandem Connection Termination. A Tandem Connection (TC) is setup to provide monitoring for a segment of a path. The TC Termination function marks the end points (Generation and Termination) of a Tandem Connection. Specific information is added at the generation side of a TC; this information will be interpreted and terminated at the termination side of the TC to detect defects and monitor performance for the relevant path segment.

Tandem Connection Configuration In order to configure a TC follow the next steps: * Click on an STM-n Unit or Nx140/155Mbit/s Tributary Unit (set as SDH interface), and select the Channels options from the unit menu. * Select the channel on which VC TC has to be created, in the Port folder for a STM-n Unit and the Mon./Sup. folder for a Nx140/155Mbit/s Tributary Unit (set as SDH interface). IMPORTANT The TC functionality is implemented at VC-4 level in the ADM-16 and ADM-64, from VC-4 to VC-12 level in the ADM-4. * Click on the Tandem Connection button. The following window will appear.


339-1268/06

.

Navigation Page

131

Book Contents


* Decide if the TC will be opened on matrix side or on line side and decide the role of the selected channel. The possible configurations are: Disabled the selected channel is not used for the Tandem Connection Generate the selected channel generates the Tandem Connection Terminate the selected channel terminates the Tandem Connection Gen. + Term. the selected channel generates and the terminates the Tandem Connection Bidirectional if the user want to create a Bidirectional Tandem Connection Monitor if the user want to create a monitor Tandem Connection

NOTICE

The Bidirectional and Monitor options are not available yet.

Not all the units, which manage the Tandem Connection, support the functionality on both sides. In the following a detailed table is given: UNIT

Term./gen.

Term./gen.

Matrix side

line side

Stm-16

X

X

Stm-4

X

X


339-1268/06

.

Navigation Page

132

Book Contents


Stm-1 Electrical (MUX 1)

X

Stm-1 Optical (MUX 1)

X

1x140/155Mbit/s Electrical

X

X

1-2-4xStm-1 Optical

X

X

4x140/155Mbit/s

X

X

Besides a TC can be generated and terminated only on line side if: - there is a cross connection with a PDH stream; - the VC is terminated; - the VC is supervisory unequipped. * If the Terminate or Gen. + Term. options have been selected, set the TC signal degrade in the TC Signal Deg. Field. The TC signal degrade can be set using two different evaluation models: ITUT values from 10-5 to 10-9 ETSI from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the Bad threshold is exceeded, the MS signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire

Check the relevant check boxes to enable one of these evaluation models. * Define the expected, received and sent value of the TC access point identifier (the operator can select it with the pool down menu into the Expected, Received and Send field in the Identifier area). For the expected, received and sent value of TC access point identifier, five different configurations can be selected: E164 Ascii View the access point identifier is represented as a string of fifteen ASCII characters E164 Hex View the access point identifier is represented as a string of fifteen Hexadecimal characters Blank Fill the access point identifier is represented as a string of blanks Zero Fill the access point identifier is represented as a string of all zeros Disabled the access point identifier management is not used

* Click on the Apply button to confirm the settings.

SPECIFIC FUNCTIONS: CHANNELS - STM-N UNITS/WDM STM16/DWDM STM-16/METRO STM-16/DWDM STM-64 For each TU or AU port inside an STM-N Unit several parameters can be configured, such as the path trace identifier (byte J0 of SOH and byte J1 of VC-4 POH) or the signal label (byte C2). N can be equal to:


339-1268/06

.

Navigation Page

133

Book Contents


n N = 1: STM-1 Electrical/Mux Unit (ADM-4), STM-1 Optical/Mux Unit (ADM-4) (ADM-16), 2xSTM-1 Optical/Mux Unit (ADM), 4xSTM-1 Optical/Mux Unit (ADM-16) (ADM-64) n N = 4: STM-4 Optical/Mux Unit (ADM) (REG-4/16) n N = 16: STM-16 Optical/Mux Unit (ADM-16) (ADM-64) (REG-4/16), STM-16 Optical/Mux Unit for DWDM (ADM-16) (ADM-64) (REG-4/16), STM-16 Optical/Mux Unit for Integrated WDM (ADM-16) (ADM-64) (REG-4/16), STM-16 Metro Standard Power (ADM-16) (ADM-64) (REG-4/16) n N = 64: STM-64 Optical/Mux Unit (ADM-64) (REG-64), STM-64 Optical/Mux Unit for DWDM (ADM-64) (REG-64) NOTICE

The byte C2 management on the 2xSTM-1 Unit is not available yet.

To configure an STM-n Unit: * Click on the selected unit, using the left button of the mouse. * Select the Channels item in the unit menu. The Termination Point Parameters window becomes accessible.

The Optical folder shows read only information about the unit: the Optical Reach and the laser Wave Freq – Length. If the selected STM-n unit is an electric STM-1, the Optical Reach and the Wave Freq – Length fields are empty and the Optical Measure push button is not displayed. The following options are only available for the STM-64 G.709: * Configure the wavelength using the Wave Length – Freq scroll list. * Set the bit rate 9,9Gb/Sec or 10,7Gb/Sec using the relevant radio button.


339-1268/06

.

Navigation Page

134

Book Contents


Note

The 10,7Gb/Sec bit rate must be set to use the OOB FEC and the Digital Wrapper functions. * Select the Pilot Tone check box to enable the Pilot Tone. This option can be used when the STM-64 is working in a WDM link with amplifiers which use the pilot tones to recognise the number of the channels. * Select the OOB FEC check box to enable the Out Of Band Forward Error Correction. * Select the Digital Wrapper check box to enable this function.

When the Digital Wrapper is enabled the Optical Channel Transport and the Optical Channel Data parameters become accessible.

* Define the expected value of SAPI (Source Access Point Identifier) for the OTU (Optical channel Transport Unit), by the Sapi Expected pull down menu into the Opt. Channel Transport field. * Define the sent value of SAPI (Source Access Point Identifier) for the OTU (Optical Transmission Unit), by the Sapi Sent pull down menu into the Opt. Channel Transport field. * Define the expected value of SAPI (Source Access Point Identifier) for the ODU (Optical channel Data Unit), by the Sapi Expected pull down menu into the Opt. Channel Data field. * Define the sent value of SAPI (Source Access Point Identifier) for the ODU (Optical Data Unit), by the Sapi Sent pull down menu into the Opt. Channel Data field. For the expected and sent value of SAPI, five different configurations can be selected:


339-1268/06

.

Navigation Page

135

Book Contents


Disabled The path trace management is not used E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen HEX characters Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros

* Set the threshold of errors corrected in one second by the FEC overt that the pre-FEC Degrade alarm will be risen, by using the Error Trh scroll list. In the Error Statistic field is displayed the number of errors corrected in one second by the FEC.

* Insert the Port Label in the Tp Label (Termination Point Label) field (optional). The Current State filed displays the unit state. * Set the Port Mode functionality, this functionality is used to monitor the LOS, the following options are available: Mon (Monitored) In case of LOS the equipment displays the relevant alarm Nmon (Not monitored) In case of LOS the equipment does not display the relevant alarm


339-1268/06

.

Navigation Page

136

Book Contents


Auto The LOS alarm is not displayed if the port is not connected to the traffic. The LOS alarm is displayed only when the port loses its traffic. When the first LOS is cleared the Porte Mode status pass from Auto to Mon

Note

The FEC (Tx) and FEC (Rx) fields are present only on the STM-64 Units * Set the Forward Error Correction for the transmission side (select it with the pull down menu into the FEC (Tx) field). * Set the Forward Error Correction for the receiving side (select it with the pull down menu into the FEC (Rx) field).

Enabled The FEC is enabled Inhibited The FEC is disabled

* Set the MS Signal Degrade threshold in the SD Threshold area (MS area). (ADM) The MS signal degrade threshold can be set using two different evaluation models: ITUT values from 10-5 to 10-9 ETSI from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the Bad threshold is exceeded, the MS signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire

Check the relevant radio button to enable one of these evaluation models. * Define the expected value of RS path trace, on J0 byte (select it with the pull down menu into the J0 Path Trace Expected field). * Define the sent value of RS path trace, on J0 byte (select it with the pull down menu into the J0 Path Trace Send field). For the expected and sent value of RS path trace, five different configurations can be selected: Disabled The path trace management is not used E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen HEX characters Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros

* Define the RS LOF Step (expressed in seconds), which is the duration of a loss of frame alignment state necessary to emit a RS LOF alarm, by using the relevant scroll list. * Click on the Apply button to validate the new configuration parameters. The Refresh button can be used whenever an update of the window is not automatically performed.


339-1268/06

.

Navigation Page

137

Book Contents


* Select the Port folder, by clicking on the relevant button at the window’s top. The Port Configuration window becomes accessible. (ADM)


339-1268/06

.

Navigation Page

138

Book Contents


If the AU-4 is not multiplied and not connected the following window will appear.

If the AU-4 is not multiplied and connected the following window will appear.

Different parameters will be available depending on the type of channel selected (the type of available channels depends on the demultiplexing level chosen in the Cross connection window, for the unit to be configured).


339-1268/06

.

Navigation Page

139

Book Contents


To configure a not connected AU-4: The operator has to do different actions if the not connected AU-4 is multiplied or not multiplied. If the not connected AU-4 isn’t multiplied: (ADM)

* Select the AU-4 to be configured, by clicking on it in the list. * Click on the HO Supervisor U. check-box.

* Define the expected value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Expected field). * Define the sent value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Send field). For the expected and sent value of J1 path trace, five different configurations can be selected: E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen Hexadecimal characters Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros Disable The path trace management is not used

Note

If the received J1 path trace value can’t be read, the J1 Path Trace Received field will contain a string of fixed byte, represented by the string Fixed Byte.


339-1268/06

.

Navigation Page

140

Book Contents


* Set the SDH SD Threshold (Signal Degrade Threshold) to be used. The threshold can be set using two different evaluation models: ITUT values from 10-5 to 10-9 ETSI from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire

Check the relevant check boxes to enable one of these evaluation models. * Define the SS Bit format for both sides (Tx and Rx). * Confirm the new settings by clicking on the Apply button.

STM-n Units Loopback Management To activate a loopback, after the port selection: Use the Loopback button in the General folder in order to select the desired type of loopback. See Also: Cross Connections: Loopback

STM-n Units Performance Data To enable the RS performance monitoring: * Select the Channels item in the unit menu and click on the SDH General folder. * Select the AU-4 to be monitored, by clicking on it in the list. * Click on RS Performance to enable the performance data collection on the Regenerator Section. See Also: Performance: All Performances, Performance Management: Threshold Profiles

To enable the MS performance monitoring: (ADM) * Select the Channels item in the unit menu and click on the SDH Generalfolder. * Select the AU-4 to be monitored, by clicking on it in the list. * Click on MS Performance to enable the performance data collection on the Multiplex Section. See Also: Performance: All Performances, Performance Management: Threshold Profiles


339-1268/06

.

Navigation Page

141

Book Contents


To enable the optical parameters monitoring: * Select the Channels item in the unit menu and click on the Optical folder. * Use the Optical Measure button to check the optical parameters (in case of STM-n optical interface). See Also: Performance: All Performances, Performance Management: Threshold Profiles

To enable the MS adaptation data monitoring: (ADM) * Select the Channels item in the unit menu and click on the Port folder. The Port folder in the Termination Point Parameter window becomes accessible. * Select the AU-4 to be monitored, by clicking on it in the list. * Click on the MS Adapt. Data button; the performance data collection on the selected port can be started. See Also: Performance: All Performances, Performance Management: Threshold Profiles

STM-n Units Alarm Management Use the Alarm Management button in the General or in the Port folders to enable the alarms reporting and to set the alarms category. See Also: Common Functions: Alarm Severity, Alarm Log Reporting, Log Setup, Log Records

STM-n Units TC Management (ADM) In order to set a Tandem Connection on an STM-n unit: * Select the Channels item in the unit menu and click on the Port folder. * Select the AU-4 (ADM) or the TU (ADM-4) to be monitored, by clicking on it in the list. * Click on the Tandem Connection push button. See Also: Tandem Connection (ADM)

SPECIFIC FUNCTIONS: CHANNELS - NX140/155MBIT/S TRIBUTARY UNITS (ADM) Each channel on a nx140/155Mbit/s Tributary Unit can be configured either as 140Mbit/s or as STM-1. n can be equal to: n n = 1 related to 1x140/155Mbit/s Tributary Unit (ADM-4); n n = 2 related to 2x140/155Mbit/s (VC-12)Tributary Unit (ADM-4) and to 2x140/155Mbit/s (VC-4)Tributary Unit (ADM-4) (ADM-16); n n = 4 related to 4x140/155Mbit/s (VC-12)Tributary Unit (ADM-16) (ADM-64).

To configure a nx140/155Mbit/s Tributary Unit: * Click on the selected unit, using the right button of the mouse.


339-1268/06

.

Navigation Page

142

Book Contents


* Select the Channels item in the unit menu. The Termination Point Parameter window becomes accessible. Different parameters will be available for channels configured as a 140Mbit/s and as an STM-1.

For a 140Mbit/s channel:

In the Port folder: * Select the VC-4 to be configured, by clicking on it in the scroll list. * Insert the Port Label in the Tp Label (Termination Point Label) field (optional). * Define the expected value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Expected field). * Define the sent value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Send field). For the expected and sent value of J1 path trace, five different configurations can be selected: Disabled The path trace management is not used E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen HEX characters Blank Fill The path trace is represented as a string of blanks


339-1268/06

.

Navigation Page

143

Book Contents


Zero Fill The path trace is represented as a string of all zeros

Note

If the received J1 path trace value can’t be read, the J1 Path Trace Received field will contain a string of fixed byte, represented by the string Fixed Byte. * Set the SDH SD Threshold (Signal Degrade Threshold) to be used.

The threshold can be set using two different evaluation models: ITUT values from 10-5 to 10-9 ETSI from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire

Check the relevant radio button to enable one of these evaluation models. * Define whether the PDH signal is framed or unframed, by using the PDH Framed check box. * For testing purpose by checking PRBS 23 Inject box, the PDH unit generates 223-1 (140Mbit/s) Pseudo Random Bit Sequence and sends it towards the Switch Unit. In the selected channel the payload is replaced by the PRBS. * For testing purpose by checking PRBS 23 Verify, the PDH unit checks the received PRBS. * Click on the Apply button to validate the new configuration parameters. The Refresh button can be used whenever an update of the window is not automatically performed.


339-1268/06

.

Navigation Page

144

Book Contents


For an STM-1 channel:

In the Port folder: * Select the AU-4 to be configured, by clicking on it in the scroll list. * Insert the Port Label in the Tp Label (Termination Point Label) field (optional). * Set the SDH SD Threshold (Signal Degrade Threshold) to be used. The threshold can be set using two different evaluation models: ITUT values from 10-5 to 10-9 ETSI from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire

Check the relevant radio button to enable one of these evaluation models. * Define the expected value of RS path trace, on byte J0 (select it with the pull down menu into the J0 Path Trace Expected field). * Define the sent value of RS path trace, on byte J0 (select it with the pull down menu into the J0 Path Trace Send field). For the expected and sent value of RS path trace, five different configurations can be selected: Disabled The path trace management is not used


339-1268/06

.

Navigation Page

145

Book Contents


E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen HEX characters Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros

* Define the LOF Step (expressed in seconds), which is the duration of a loss of frame alignment state, necessary to emit a RS LOF alarm. * Click on the Apply button to validate the new configuration parameters. The Refresh button can be used whenever an update of the window is not automatically performed.

To configure a not connected AU4: The operator has to do different actions if the not connected AU-4 is multiplied or not multiplied. If the not connected AU-4 isn’t multiplied: (ADM)

* Select the Mon./Sup. folder. * Select the AU-4 to be configured, by clicking on it in the list. * Click on the HO Supervisor U. check-box.

* Define the expected value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Expected field). * Define the sent value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Send field). For the expected and sent value of J1 path trace, five different configurations can be selected:


339-1268/06

.

Navigation Page

146

Book Contents


Disabled The path trace management is not used E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen HEX characters Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros

Note



Check the relevant radio button to enable one of these evaluation models. * Define the SS Bit format for both sides (Tx and Rx). * Confirm the new settings by clicking on the Apply button. The Refresh button can be used whenever an update of the window is not automatically performed. If the not connected AU-4 is multiplied: (ADM-4)

* Select the Ports folder in the Termination Point Parameter window. * Select the AU-4 to be configured, by clicking on it in the list.


339-1268/06

.

Navigation Page

147

Book Contents


NOTICE

This window can be displayed whether the unit can perform VC-12 handling only.

* Define the expected value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Expected field). * Define the sent value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Send field). For the expected and sent value of J1 path trace, five different configurations can be selected: Disabled The path trace management is not used E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen HEX characters Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros

Note


The threshold can be set using two different evaluation models: ITUT values from 10-5 to 10-9


339-1268/06

.

Navigation Page

148

Book Contents


ETSI from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire

Check the relevant radio button to enable one of these evaluation models. * Define the SS Bit format for both sides (Tx and Rx). * Confirm the new settings by clicking on the Apply button. The Refresh button can be used whenever an update of the window is not automatically performed.

To configure a connected AU-4: The operator has to do different actions if the connected AU-4 is multiplied or not multiplied. If the connected AU-4 isn’t multiplied: (ADM)

* Select the Mon./Sup. folder. * Select the AU-4 to be configured, by clicking on it in the list. * Click on the Monitor Active check-box. NOTICE

If the AU-4 is working in Supervisory Unequipped mode, the monitoring is automatically enabled when the connection is made; otherwise the channel monitoring is not performed this way.

* Define the expected value of signal label, on byte C2. * Define the expected value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Expected field). IMPORTANT It is important to enable the Monitoring when the VC-4 SNCP/N is required.


339-1268/06

.

Navigation Page

149

Book Contents


For the expected value of J1 path trace, five different configurations can be selected: Disabled The path trace management is not used E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen HEX characters Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros

Note



Check the relevant check boxes to enable one of these evaluation models. * Define the SS Bit format for both sides (Tx and Rx). * Confirm the new settings by clicking on the Apply button. The Refresh button can be used whenever an update of the window is not automatically performed. If the connected AU-4 is multiplied: (ADM-4)

NOTICE

This functionality is available whether the unit can perform VC-12 handling.


339-1268/06

.

Navigation Page

150

Book Contents


To configure a not connected TU-3: * Select the not connected TU-3 to be configured, by clicking on it in the list. * Click on the LO Supervisor U. check-box.

* Define the expected value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Expected field). * Define the sent value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Send field). For the expected and sent value of J1 path trace, five different configurations can be selected: Disabled The path trace management is not used E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen HEX characters Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros

Note



339-1268/06

.

Navigation Page

151

Book Contents


* Set the SDH SD Threshold (Signal Degrade Threshold) to be used. The threshold can be set using two different evaluation models: ITUT values from 10-5 to 10-9 ETSI from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire

Check the relevant check boxes to enable one of these evaluation models. * Confirm the new settings by clicking on the Apply button. The Refresh button can be used whenever an update of the window is not automatically performed.


339-1268/06

.

Navigation Page

152

Book Contents


To configure a connected TU-3: * Select the connected TU-3 to be configured, by clicking on it in the list.

* Click on the Monitor Active check-box. * Define the expected value of signal label, on byte C2. Define the expected value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Expected field). For the expected value of J1 path trace, five different configurations can be selected: Disabled The path trace management is not used E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen HEX characters Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros

Note


IMPORTANT The J1 Path Trace area (lower order monitoring) is displayed only if the unit is equipped with TUREG-B ASIC. * Set the SDH SD Threshold (Signal Degrade Threshold) to be used. The threshold can be set using two different evaluation models:


339-1268/06

.

Navigation Page

153

Book Contents


ITUT values from 10-5 to 10-9 ETSI from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire


To configure a not connected TU-2/TU-12: * Select the not connected TU-2/TU-12 to be configured, by clicking on it in the list. * Click on the LO Supervisor U. check-box.

* Define the expected value of path trace, on byte J2 (select it with the pull down menu into the J2 Path Trace Expected field). * Define the sent value of path trace, on byte J2 (select it with the pull down menu into the J2 Path Trace Send field). For the expected and sent value of J2 path trace, five different configurations can be selected: Disabled The path trace management is not used


339-1268/06

.

Navigation Page

154

Book Contents



Note





339-1268/06

.

Navigation Page

155

Book Contents


To configure a connected TU-2/TU-12: * Select the connected TU-2/TU-12 to be configured, by clicking on it in the list.

* Click on the Monitor Active check-box. * Define the expected value of signal label, on byte V5. Define the expected value of path trace, on byte J2 (select it with the pull down menu into the J2 Path Trace Expected field). For the expected value of J2 path trace, five different configurations can be selected: Disabled The path trace management is not used E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen HEX characters Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros

IMPORTANT The J2 Path Trace area (lower order monitoring) is displayed only if the unit is equipped with TUREG-B ASIC. * Set the SDH SD Threshold (Signal Degrade Threshold) to be used. The threshold can be set using two different evaluation models:


339-1268/06

.

Navigation Page

156

Book Contents


ITUT values from 10-5 to 10-9 ETSI from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire

Check the relevant check boxes to enable one of these evaluation models. * Confirm the new settings by clicking on the Apply button. The Refresh button can be used whenever an update of the window is not automatically performed

nx140/155Mbit/s Units Loopback Management To activate a loopback, after the port selection: Use the Loopback button in the Port folder in order to select the desired type of loopback. See Also: Cross Connections: Loopback

nx140/155Mbit/s Units Performance Data To enable the RS performance monitoring on an STM-1 channel: * Select the Channels item in the unit menu and click on the Port folder. * Select the AU-4 to be monitored, by clicking it in the list. * Click on RS Performance to enable the performance data collection on the Regenerator Section Termination. See Also: Performance: All Performances, Performance Management: Threshold Profiles

To enable the MS performance monitoring on an STM-1 channel: * Select the Channels item in the unit menu and click on the Port folder. * Select the AU-4 to be monitored, by clicking it in the list. * Click on MS Performance to enable the performance data collection on the Multiplex Section Termination. See Also: Performance: All Performances, Performance Management: Threshold Profiles

To enable the MS adaptation data monitoring on the STM-1 channel: * Select the Channels item in the unit menu and click on the Port folder. * Select the AU-4 to be monitored, by clicking it in the list. * By means of MS Adapt. Data the performance data collection on the Multiplex Section Adaptation can be started. See Also: Performance: All Performances, Performance Management: Threshold Profiles


339-1268/06

.

Navigation Page

157

Book Contents


To enable the performance monitoring on a 140Mbit/s channel: * Select the Channels item in the unit menu and click on the Port folder. * Select a VC-4 to be monitored, by clicking it in the list. * By means of Path Term.Data the performance data collection on the selected channel can be started. See Also: Performance: All Performances, Performance Management: Threshold Profiles

nx140/155Mbit/s Units Alarm Management Use the Alarm Management button in the General or in the Port folder to enable the alarms reporting and to set the alarm category. See Also: Common Functions: Alarm Severity, Alarm Log Reporting, Log Setup, Log Records

nx140/155Mbit/s Units TC Management In order to set a Tandem Connection on an nx140/155Mbit/s unit for an SDH port: * Select the Channels item in the unit menu and click on the Mon./Sup. folder. * Select the AU-4 (ADM) or the TU (ADM-4) to be monitored, by clicking on it in the list. * Click on the Tandem Connection push button. See Also: Tandem Connection (ADM)

SPECIFIC FUNCTION: CHANNELS - 3X45MBIT/S AND 3X34MBIT/S TRIBUTARY UNITS (ADM-4) For each 34/45Mbit/s port inside a 3x34/45Mbit/s Tributary Unit several parameter can be configured, such as the path trace identifier (byte J1) or the signal label (byte C2).

To configure a 3x34/45Mbit/s Tributary Unit: * Click on the selected unit, using the right button of the mouse. * Select the Channels item in the unit menu. The Termination Point Parameter window becomes accessible.


339-1268/06

.

Navigation Page

158

Book Contents


* Select the port to be configured, clicking on it in the scroll list. * Insert the Port Label in the Tp Label (Termination Point Label) field (optional). * Define the expected value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Expected field). * Define the sent value of path trace, on byte J1 (select it with the pull down menu into the J1 Path Trace Send field). For the expected value of J1 path trace, five different configurations can be selected: Disabled The path trace management is not used E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen HEX characters Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros

NOTICE


* Set the expected and the send value for the signal label, by means of byte C2 (for byte C2 there is an additional field with the received value). * Set the values of signal degrade thresholds. The threshold can be set using two different evaluation models: ITUT values from 10-5 to 10-9 ETSI from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the


339-1268/06

.

Navigation Page

159

Book Contents


Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire

Check the relevant check boxes to enable one of these evaluation models. * Set the status of RDI (former FERF) on received tributary signal (bit 8 in byte V5), using the FERF State scroll list. For the FERF State these different configurations can be selected: Auto The RDI signal is generated only when there is a remote defect indication Forced ON The RDI signal will always be generated; this option is used for testing Forced OFF The RDI signal will never be generated

* Confirm the new settings by clicking on the Apply button. The Refresh button can be used whenever an update of the window is not automatically performed.

34-45Mbit/s Units Loopback Management To activate a loopback, after the port selection: Use the Loopback button in the Port folder in order to select the desired type of loopback. See Also: Cross Connections: Loopback

34-45Mbit/s Units Performance Data * Select the Channels item in the unit menu. * Select the channel to be monitored, by clicking it in the list. * Click on the Path Term Data button in the Termination Point Parameter window. See Also: Performance: All Performances, Performance Management: Threshold Profiles

34-45Mbit/s Units Alarm Management Use the Alarm Management button in the Termination Point Parameter window to enable the alarms reporting and to set the alarm category. See Also: Common Functions: Alarm Severity, Alarm Log Reporting, Log Setup, Log Records

SPECIFIC FUNCTIONS: CHANNELS - 2MBIT/S TRIBUTARY UNITS (ADM-4) For each 2Mbit/s port inside a 2Mbit/s Tributary Unit several parameters can be configured, such as the path trace identifier (byte J2) or the signal label (bits 5-7 of byte V5).

To configure a 2Mbit/s Tributary Unit: * Click on the selected unit, using the right button of the mouse. * Select the Channels item in the unit menu. The Termination Point Parameter window becomes accessible.


339-1268/06

.

Navigation Page

160

Book Contents


The Refresh button can be used whenever an update of the window is not automatically performed. * Select the port to be configured, clicking on it in the scroll list. * Define the port as: 2Mbit/s Unframed, 2Mbit/s Framed, 2Mbit/s Multiramed, 1.5Mbit/s AMI code or 1.5Mbit/s B8ZS code. * Set the Port Mode functionality, this functionality is used to monitor the LOS, the following options are available: Mon (Monitored) In case of LOS the equipment displays the relevant alarm Nmon (Not monitored) In case of LOS the equipment does not display the relevant alarm Auto The LOS alarm is not displayed if the port is not connected to the traffic. The LOS alarm is displayed only when the port loses its traffic. When the first LOS is cleared the Porte Mode status pass from Auto to Mon

* Insert the Port Label in the Tp Label (Termination Point Label) field (optional). * Define the expected value of path trace, on byte J2 (select it with the pull down menu into the J2 Path Trace Expected field). * Define the sent value of path trace, on byte J2 (select it with the pull down menu into the J2 Path Trace Send field). For the expected value of J2 path trace, five different configurations can be selected: Disabled The path trace management is not used E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen HEX characters


339-1268/06

.

Navigation Page

161

Book Contents


Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros

* Set the expected and the send value for the signal label, by means of byte V5 (for byte V5 there are two additional fields with the received and send values). * Set the values of signal degrade thresholds by means of the relevant scroll lists in the SD Threshold area. The threshold can be set using two different evaluation models: ITUT values from 10-5 to 10-9 ETSI from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire

Check the relevant check boxes to enable one of these evaluation models. * Set the status of RDI (former FERF) on received tributary signal (bit 8 in byte V5), using the FERF State scroll list. For the FERF State these different configurations can be selected: Auto The RDI signal is generated only when there is a remote defect indication Forced ON The RDI signal will always be generated; this option is used for testing Forced OFF The RDI signal will never be generated

* Confirm the new settings by clicking on the Apply button. The Refresh button can be used whenever an update of the window is not automatically performed.

2Mbit/s Units Loopback Management To activate a loopback, after the port selection: Use the Loopback button in the Termination Point Parameter window in order to select the desired type of loopback. See Also: Cross Connections: Loopback

2Mbit/s Units Performance Data Path Termination Data * Select the Channels item in the unit menu. * Select the port to be monitored, by clicking it in the list. * Use the Path Term Data button in the Termination Point Parameter window. See Also: Performance: All Performances, Performance Management: Threshold Profiles


339-1268/06

.

Navigation Page

162

Book Contents


PDH Incoming Data Thai option is only available when the 2Mbit/s is set framed or multiframed. * Select the Channels item in the unit menu. * Select the port to be monitored, by clicking it in the list. * Use the PDH Input Data button in the Termination Point Parameter window. See Also: Performance: All Performances, Performance Management: Threshold Profiles

PDH Outgoing Data Thai option is only available when the 2Mbit/s is set multiframed. * Select the Channels item in the unit menu. * Select the port to be monitored, by clicking it in the list. * Use the PDH Output Data button in the Termination Point Parameter window. See Also: Performance: All Performances, Performance Management: Threshold Profiles

2Mbit/s Units Alarm Management Use the Alarm Management button in the General or in the Port folder to enable the alarms reporting and to set the alarm category. See Also: Common Functions: Alarm Severity, Alarm Log Reporting, Log Setup, Log Records

SPECIFIC FUNCTIONS: OPTICAL MEASURE - BOOSTER AND PREAMPLIFIER UNIT This function is used to manage optical measures and alarm management for Booster and Preamplifier Units. It is available, by clicking the Optical Measure option in the unit menu, for the following units: n Booster +10, +12, +16dBm; n Booster +17dBm (ADM-16) (ADM-64) (REG); n Preamplifier (ADM) (REG-64). By clicking the Optical Measure option in the unit menu, the following window will appear.


339-1268/06

.

Navigation Page

163

Book Contents


In this window there are some read only information about the unit Current State, the Optical Reach and the laser Wave Length. The operator can write additional information in the relevant field. * Set the Port Mode functionality, this functionality is used to monitor the LOS, the following options are available: Mon (Monitored) In case of LOS the equipment displays the relevant alarm Nmon (Not monitored) In case of LOS the equipment does not display the relevant alarm Auto The LOS alarm is not displayed if the port is not connected to the traffic. The LOS alarm is displayed only when the port loses its traffic. When the first LOS is cleared the Porte Mode status pass from Auto to Mon

Booster and Preamplifier Units Performance Data * Select the Optical Measure item in the unit menu. * Use the Optical Measure button in the Optical Measure window. See Also: Performance: All Performances, Performance Management: Threshold Profiles

Booster and Preamplifier Units Alarm Management Use the Alarm Management button in the Optical Measure window to enable the alarms reporting and to set the alarms category. See Also: Common Functions: Alarm Severity, Alarm Log Reporting, Log Setup, Log Records


339-1268/06

.

Navigation Page

164

Book Contents


SPECIFIC FUNCTIONS: CHANNELS - STM-16 FOR VC-4-4C/4V AND 16C/16V (ADM-64) (ADM-16) To configure an STM-16 for VC-4-4c/4v and 16c/16v Unit: * Click on the selected unit, using the left button of the mouse. * Select the Channels item in the unit menu. The Termination Point Parameters window becomes accessible.

The SDH Termination window shows read only information about the unit Current State, the Optical Reach and the laser Wave Freq – Length. * Insert the Port Label in the Tp Label (Termination Point Label) field (optional). * Set the MS Signal Degrade threshold in the SD Threshold area (MS area). The MS signal degrade threshold can be set using two different evaluation models: ITUT values from 10-5 to 10-9 ETSI from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the Bad threshold is exceeded, the MS signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire

Check the relevant radio button to enable one of these evaluation models. * Define the expected value of RS path trace, on J0 byte (select it with the pull down menu into the J0 Path Trace Expected field).


339-1268/06

.

Navigation Page

165

Book Contents


* Define the sent value of RS path trace, on J0 byte (select it with the pull down menu into the J0 Path Trace Send field). For the expected and sent value of RS path trace, five different configurations can be selected: Disabled The path trace management is not used E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen HEX characters Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros

* Define the RS LOF Step (expressed in seconds), which is the duration of a loss of frame alignment state necessary to emit a RS LOF alarm, by using the relevant scroll list. * Set the Port Mode functionality, this functionality is used to monitor the LOS, the following options are available: Mon (Monitored) In case of LOS the equipment displays the relevant alarm Nmon (Not monitored) In case of LOS the equipment does not display the relevant alarm Auto The LOS alarm is not displayed if the port is not connected to the traffic. The LOS alarm is displayed only when the port loses its traffic. When the first LOS is cleared the Porte Mode status pass from Auto to Mon


339-1268/06

.

Navigation Page

166

Book Contents


* Click on the Apply button to validate the new configuration parameters. The Refresh button can be used whenever an update of the window is not automatically performed. * Select the Port folder, by clicking on the relevant button at the window’s top. The Termination Point window becomes accessible.

* Define the expected value of path trace, on byte J1 (select it with the pull down menu into the J1 Line field). * Define the sent value of path trace, on byte J1 (select it with the pull down menu into the J1 Line field). For the expected and sent value of J1 path trace, five different configurations can be selected: Disabled The path trace management is not used E164 Ascii View The path trace is represented as a string of fifteen ASCII characters E164 Hex View The path trace is represented as a string of fifteen HEX characters Blank Fill The path trace is represented as a string of blanks Zero Fill The path trace is represented as a string of all zeros

Note



339-1268/06

.

Navigation Page

167

Book Contents


* Define the expected value of signal label, on byte C2. * Set the SDH SD Threshold (Signal Degrade Threshold) to be used. The threshold can be set using two different evaluation models: ITUT values from 10-5 to 10-9 ETSI from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire

Check the relevant radio button to enable one of these evaluation models.

STM-16 for VC-4-4c/4v and 16c/16v Unit Performance Data To enable the RS performance monitoring: * Select the Channels item in the unit menu and click on the General folder. * Click on RS Performance to enable the performance data collection on the Regenerator Section. See Also: Performance: All Performances, Performance Management: Threshold Profiles

To enable the MS performance monitoring: (ADM) * Select the Channels item in the unit menu and click on the General folder. * Click on MS Performance to enable the performance data collection on the Multiplex Section. See Also: Performance: All Performances, Performance Management: Threshold Profiles

To enable the optical parameters monitoring: * Select the Channels item in the unit menu and click on the General folder. * Use the Optical Measure button to check the optical parameters (in case of STM-n optical interface). See Also: Performance: All Performances, Performance Management: Threshold Profiles

To enable the MS adaptation data monitoring: (ADM) * Select the Channels item in the unit menu and click on the Port folder. The Port folder in the Termination Point Parameter window becomes accessible. * Select the first VC4V ( for the VC-4-4c/4v application select the first VC4V of each group) by clicking on it in the list. * Click on the MS Adapt. Data button; the performance data collection on the selected port can be started. See Also: Performance: All Performances, Performance Management: Threshold Profiles


339-1268/06

.

Navigation Page

168

Book Contents


STM-16 for VC-4-4c/4v and 16c/16v Unit Alarm Management Use the Alarm Management button in the General or in the Port folders to enable the alarms reporting and to set the alarms category. See Also: Common Functions: Alarm Severity, Alarm Log Reporting, Log Setup, Log Records

Delay setting To set the delay time * Select the Channels item in the unit menu and click on the Port folder. * Select the first VC4V ( for the VC-4-4c/4v application select the first VC4V of each group) and click on the Delay setting button, the Conversion Delay window will be displayed.

There are two possible ways to configure the delay time: Auto Adaptive or Max Delay. * Check the Auto Adaptive button, the unit automatically sets the right delay time value. * Use the Max Delay spinner to set the desired delay time value, the configuration range for the delay time is between 125 microsec and 128msec with step of 125 microsec. * There are two ways to perform the configured delay time: Delayed/hitless The delay time is not configured immediately but this operation it is hitless Immediate/noising The delay time is configured immediately but this operation it is not hitless

SPECIFIC FUNCTIONS: CHANNELS - GIGABIT ETHERNET UNITS (ADM-16) (ADM-64) To configure a Gigabit Ethernet Unit: * Click on the selected unit, using the left button of the mouse. * Select the Channels item in the unit menu. The Termination Point Parameters window becomes accessible.


339-1268/06

.

Navigation Page

169

Book Contents


* Select either Eth#1 or Eth#2 folders to modify the Ethernet parameters for the port one or two . The Optical Interface shows read only information about the unit: the Optical Reach and the laser Wave Freq – Length. * Insert the Port Label in the Tp Label (Termination Point Label) field (optional). * Enable or disable the Auto Negotiation process by checking the relevant check box. IMPORTANT For the Gigabit Ethernet line protection the Auto Negotiation must be set enabled. * Check the Port Enable field to start the transmission of the data traffic. * Set the Max Ethernet Size by the M.t.u. (Max transmitted unit) spinner (from 64 to 1600 bytes). In the Bit Rate field is displayed the line rate value (1000Mbit/s) and in the Duplex field is displayed the duplex status of the interface (full duplex). * Enable or disable the Shaper function by checking the relevant check box. This option is used to define the traffic data rate desired by using the Rate spinner (from 10 to 1000Mb/s) By clicking on the Mapper Performances button the Ethernet Statistic window will be displayed


339-1268/06

.

Navigation Page

170

Book Contents


The parameters relevant to the data incoming/outgoing into/from the Ethernet interface are displayed in the Input/Output field, the meaning of them is explained in the following: Allignement The number of octets in valid MAC frames received on this interface, including the MAC header and FCS. This does include the number of octets in valid MAC Control frames received on this interface. Unicast The total number of unicast packets without errors. Note that this does not include MAC Control frames, since MAC Control frames are consumed by the interface layer and are not passed to any higher layer protocol. Multicast The total number of good packets that were directed to a multicast address. Note that this number does not include packets directed to the broadcast. Note that this does not include MAC Control frames, since MAC Control frames are consumed by the interface layer and are not passed to any higher layer protocol.


339-1268/06

.

Navigation Page

171

Book Contents


Broadcast The total number of good packets that were directed to the broadcast address. Note that this does not include multicast packets. Note that this does not include MAC Control frames, since MAC Control frames are consumed by the interface layer and are not passed to any higher layer protocol. Discarded The number of inbound packets discarded even though no errors had been detected to prevent their being delivered. Includes RxFIFO overflow count.

The parameters relevant to the Ethernet errors are displayed in the Errors Summary field, the meaning of them is explained in the following: Allignement Count of frames received with a length between 64 bytes and the maximum packet size, a nonintegral byte count and a CRC error. UnderSized The total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed. fcs Count of frames received with a length between 64 bytes and the maximum packet size, an integral byte count and a CRC error. FrmTooLong The total number of packets received that were longer than the configured Max Ethernet Size (excluding framing bits, but including FCS octets) and were otherwise well formed. Int.MAC rx A count of frames for which reception fails due to an internal MAC sublayer receive error. Int.MAC tx A count of frames for which transmission fails due to an internal MAC sublayer receive error

By means of Request push button, a query on the status of the current register can be performed. By selecting Continuous check box, the status of the current register is displayed every n seconds (n stands for the number configured by the Refresh interval spinner). By means of Disable push button, the performance data collection is stopped. By means of Cnt. Reset push button, the counters’ value in the current aggregation period is reset.


339-1268/06

.

Navigation Page

172

Book Contents


By clicking on the Queue Performances button the Queue Performances window will be displayed.

The parameters relevant to the queue function are displayed in the Current Data field, the meaning of them is explained in the following: DisPackts The number of inbound packets discarded even though no errors had been detected to prevent their being delivered. Includes RxFIFO overflow count. DiscBytes The number of bytes discarded even though no errors had been detected to prevent their being delivered.

By means of Request push button, a query on the status of the current register can be performed. By selecting Continuous check box, the status of the current register is displayed every n seconds (n stands for the number configured by the Refresh interval spinner). By means of Disable push button, the performance data collection is stopped. By means of Cnt. Reset push button, the counters’ value in the current aggregation period is reset.


339-1268/06

.

Navigation Page

173

Book Contents


* Select the Mapping folder, by clicking on the relevant button at the window’s top.

* For the port one and port two define the mapping mode using the relevant scroll lists. For the mapping different configurations can be selected: VC-4 The data incoming from the Ethernet interface are mapped in a single VC-4 VC-4-4C The data incoming from the Ethernet interface are mapped in a contiguous concatenation of four VC-4 VC-4-4-nV The data incoming from the Ethernet interface are mapped in a virtual concatenation of n VC-4, n from 2 to 8

For the virtual VC-4 concatenation mapping see the following steps: * Number of the virtual VC-4 make part of the concatenation using the VC-4-nV channels spinner * Check the Auto Adaptive button, the unit automatically sets the right delay time value. * Use the Max Delay spinner to set the desired delay time value, the configuration range for the delay time is between 125 microsec and 128msec with step of 125 microsec. * There are two ways to perform the configured delay time:


339-1268/06

.

Navigation Page

174

Book Contents


Delayed/hitless The delay time is not configured immediately but this operation it is hitless Immediate/noising The delay time is configured immediately but this operation it is not hitless

* Define the dLOM Threshold (expressed in milliseconds) by using the relevant scroll list, this parameter indicates the duration of the loss of multiframe state necessary to emit a dLOm alarm, * Define the dSQM Thresholdby using the relevant scroll list., it is the number of multiframes with wrong sequence necessary to emit an alarm of dSQM. * Define the dSQM Recovery by using the relevant scroll list., it is the number of multiframes with right sequence necessary to remove an alarm of dSQM. * Confirm the new settings by clicking on the Change Map Settings button. * Select the Port folder, by clicking on the relevant button at the window’s top. The Termination Point window becomes accessible.

* Define the expected value of path trace, on byte J1 (select it with the pull down menu into the J1 Line field). * Define the sent value of path trace, on byte J1 (select it with the pull down menu into the J1 Line field). For the expected and sent value of J1 path trace, five different configurations can be selected: Disabled The path trace management is not used


339-1268/06

.

Navigation Page

175

Book Contents



Note

If the received J1 path trace value can’t be read, the J1 Path Trace Received field will contain a string of fixed byte, represented by the string Fixed Byte. * Define the expected value of signal label, on byte C2. * Set the SDH SD Threshold (Signal Degrade Threshold) to be used.


Check the relevant radio button to enable one of these evaluation models.

Gigabit Ethernet Unit Performance Data To enable the performance monitoring on a 140Mbit/s channel: * Select the Channels item in the unit menu and click on the Port folder. * Select a VC-4 to be monitored, by clicking it in the list. * By means of the Path Term.Data the performance data collection on the selected channel can be started. See Also: Performance: All Performances, Performance Management: Threshold Profiles

Gigabit Ethernet Loopback Management To activate a loopback, after the port selection: Use the Loopback button in the General folder in order to select the desired type of loopback. See Also: Cross Connections: Loopback

Gigabit Ethernet Alarm Management Use the Alarm Management button in the General or in the Port folders to enable the alarms reporting and to set the alarms category. See Also: Common Functions: Alarm Severity, Alarm Log Reporting, Log Setup, Log Records


339-1268/06

.

Navigation Page

176

Book Contents


SPECIFIC FUNCTIONS: CHANNELS - AUXILIARY UNIT The function Channels, on the Auxiliary Unit menu, allows configuring the EOW and the auxiliary 64kbit/s channels.

To modify the telephone number of the equipment: * Click on the Auxiliary Unit and select the Channels item. * Select the General folder. * Set the Phone Number (from 11 to 99) by using the relevant scroll list. * Use the Apply button to confirm the settings. See Also: Auxiliary Channels, EOW Channels

EOW Channels To configure the EOW Areas: * Select either EW1 or EW2 folders (depending on the EOW Area to be configured).


339-1268/06

.

Navigation Page

177

Book Contents


* Select the connection type to be configured, by using the Type scroll list. The available connection types are Direct, Bypass Line, and Ring.

In order to set a direct connection: * Choose the Direct option in the Type field. * Select the line or tributary interface to be used for carrying the EOW channel, by double clicking on it in the list. * Select the SOH byte to be used (E1 or E2). * Use the Add button to confirm the creation of the EOW channel. The configured EOW channel will be displayed followed by the symbol ’-’.


339-1268/06

.

Navigation Page

178

Book Contents


In order to set a bypass connection:

* Choose the Bypass Line option in the Type field. * Select the line or tributary interface to be used for carrying the incoming EOW channel, by double clicking on it in the list. * Select the SOH byte to be used on the incoming EOW channel (E1 or E2). * Select the line or tributary interface to be used for carrying the outgoing EOW channel, by double clicking on it in the list. * Select the SOH byte to be used on the outgoing EOW channel (E1 or E2). * Use the Add button to confirm the creation of the EOW channel. The configured EOW channels will be displayed followed by the symbol ’-’.


339-1268/06

.

Navigation Page

179

Book Contents


In order to set a ring connection:

* Choose the Ring option in the Type field. * Select the line or tributary interface to be used for carrying the EOW channel on the East side of the ring, by double clicking on it in the list. * Select the SOH byte to be used on the EOW channel on the East side of the ring (E1 or E2). * Select the line or tributary interface to be used for carrying the EOW channel on the West side of the ring, by double clicking on it in the list. * Select the SOH byte to be used on the EOW channel on the West side of the ring (E1 or E2). * Define whether or not the current system is used as Ring Master, by checking the relevant check box. * If the current system has been selected as Ring Master, use the Send CAI to scroll list to define the side of the EOW ring, on which must be sent a tone to check the ring integrity. * Use the Add button to confirm the creation of the EOW channel. The configured EOW channels will be displayed followed by the symbol ’-’.

To remove configured EOW channels: * Select on of the two EOW areas, by selecting the relevant folder. * Select the configured EOW channel to be removed by clicking on it in the list. * Remove it by using the Delete button. See Also: Specific Functions: Channels - Auxiliary Unit


339-1268/06

.

Navigation Page

180

Book Contents


Auxiliary Channels To configure the G.703 64kbit/s auxiliary channels: * Select G703 folder.

* Select the line or tributary interface to be used for carrying the auxiliary channel by double clicking on it in the list. * Select a spare SOH byte to be used to carry the auxiliary channel. The RSOH and MSOH bytes are displayed as MS: x-y, where x is the number of the row and y the number of the column. * Use the Add button to confirm the creation of the auxiliary channel.


339-1268/06

.

Navigation Page

181

Book Contents


To configure the V11 64kbit/s auxiliary channels: * Select V11 folder.

* Select the line or tributary interface to be used for carrying the auxiliary channel by double clicking on it in the list. * Select a spare SOH byte to be used to carry the auxiliary channel. The RSOH and MSOH bytes are displayed as MS:x-y, where x is the number of the row and y the number of the column. * Use the Add button to confirm the creation of the auxiliary channel. See Also: Specific Functions: Channels - Auxiliary Unit

DAM UNIT CONFIGURATION By selecting the Configuration item in a DAM unit menu, the DAM Unit Configuration window becomes accessible. By clicking on the General folder, the General folder is displayed, there are two possible configurations for the DAM Unit: Input Collector or Output Collector.

Input Collector To configure the unit as Input Collector: * Select the Input Collector, in this case the summary alarms (external) are collected from the input (B interface) and sent to the DAM configured as Output Collector.


339-1268/06

.

Navigation Page

182

Book Contents


* Select the number of ground contacts to send in the In contacts number scroll list (the maximum number of available contacts depends on the configured Dam address). * Select the correct Dam address, this one must be unique and consecutive in the network. * Confirm the new settings by clicking on the APPLY button. To configure the DAM connections to the lines: * Click on the Connection folder.


339-1268/06

.

Navigation Page

183

Book Contents


* Select an available unit in the list and define if it is used for the East or West connection by clicking on the East Line or West Line button. * Repeat the previously step for the other connection (the configured units will be displayed in the Line West and Line East fields). * Confirm the settings by clicking on the APPLY button.

To display the ground contacts: * Click on the GC 1-20 folder and will be displayed the configured ground contacts and their status (active or not active).

Output Collector To configure the unit as Output Collector: * Select the Output Collector, in this case the summary alarms are collected from the remote Network Elements and returned on the DAM subrack connector (B interface).


339-1268/06

.

Navigation Page

184

Book Contents


* Confirm the settings by clicking on the APPLY button.

To configure the DAM connections to the lines: * Click on the Connection folder. * Select an available unit in the list and define if it is used for the East or West connection by clicking on the East Line or West Line button. * Repeat the previously step for the other connection (the configured units will be displayed in the Line West and Line East fields). * Confirm the settings by clicking on the APPLY button.

To display the ground contacts: * Click on the GC “n”-“n” folder and will be displayed the configured ground contacts and their status (active or not active).

8XFAST ETHERNET UNIT COMMISSIONING The channels of a 8xFast Ethernet Unit must be equipped, then several parameters or fault actions to be performed as consequence of some detected events, has to be configured.

How to create a 8xFastEthernet Unit * In the Select Unit Type window, select the 8xFast Ethernet Unit and the following picture will be displayed.


339-1268/06

.

Navigation Page

185

Book Contents


By means of this window it is possible to commissioning each Ethernet port. * Under the column called “Conversion” it is possible enable or not the single port. Two options are available for activate a port: nV The physical interface is able to manage virtual concatened streams only LCAS The physical interface is able to manage virtual concatened streams with LCAS function supported.

* Under the column called “Connector” it is possible set the port as electrical (RJ45) or optical. * Click on the OK button to confirm and exit from this window. Note

In order to create the 8xFast Ethernet Unit it is mandatory enabled one or more Ethernet port.

Note

It is possible change the configuration of the physical ports as described in the paragraph “8xFast Ethernet Unit: Ethernet Ports Configuration folder”.

See Also: 8xFast Ethernet Unit: Ethernet Ports Configuration folder

8XFAST ETHERNET UNIT: UNIT CONFIGURATION By means of the selection of the Channel item in a 8x Fast Ethernet Unit menu, it is possible exceed to its relevant configuration window.

8xFast Ethernet Unit: Ethernet Ports Configuration folder Path (8xFast Ethernet Unit Menu -> Channel -> Ethernet ports) By clicking on the Ethernet ports button, the Ethernet Port Configuration folder is displayed.


339-1268/06

.

Navigation Page

186

Book Contents


This window displays three sections: * Physical Interface: This section permits to configure the physical interface as either electrical or optical. * Ethernet Negotiation: This section permits to configure the Ethernet parameters. * Mac/Service: This section permits to configure the MAC parameters. The three sections briefly described above are explained in the following

8xFast Etherenet Unit: Physical Interface section Path (8xFast Ethernet Unit Menu -> Channel -> Ethernet ports) In this section is described the physical interface configuration procedure for the Fast Ethernet Unit.

To configure the Fast Ethernet physical port * Select the port number to be configured in the Ext Line# column list. * Type in the Tp Label field as reminder for the specific port. * Select the Interface type in the Connector field coherently with the hardware interface fitted on the port (optical or electrical) by using the relevant scroll list. * Switch the physical interface from a not operative status (Disabled) to an active status by using the relevant scroll list. Two options are available: Enable NV The physical interface is able to manage concatenated stream only. Enabled LCAS The physical interface is able to manage concatenated streams with LCAS supported.


339-1268/06

.

Navigation Page

187

Book Contents


* Click on the Loopback button in order to show the Loopback window. * Click on the Alarm Management button in order to show the Alarm Severity window for the Ethernet port. Note

Please refer to the “t.b.d.” paragraph in the “t.b.d.” chapter within of this handbook for the description of the Loopback features.

See Also: 8xFast Ethernet Unit: Ethernet Ports Configuration folder, Fault Detection Procedure, Alarm Reporting

8xFast Ethernet Unit: Ethernet Negotiation section Path (8xFast Ethernet Unit Menu -> Channel -> Ethernet ports) In this section is described the Ethernet parameters configuration procedure for the Fast Ethernet Unit. Note

Only the ports previously equipped can be available for the Ethernet parameters Configuration.

To configure the Ethernet parameters * Select the port number to be configured in the Ext Line# column list. * Define whether the Auto Negotiation function is enabled or disabled by checking or not the relevant check box respectively. Note

When the Auto Negotiation function is enabled, the Local Config. Capabilities field will be available (see the following picture) and simultaneously the only read Remote Capabilities (if enabled) field will be shown.


339-1268/06

.

Navigation Page

188

Book Contents


If the Auto Negotiation function is enabled * Select the type of Auto Negotiation parameters to be used by checking the relevant check box within the field. * Enable or disable the Asymmetrical Pause by using the relevant scroll list. When this option is enabled the port will send PAUSE control messages on the Ethernet Line, to request the remote device to pause, but PAUSE requests from the remote device are not accepted. Note

The Auto Negotiation function is disabled for the optical interface

Note

The Asymmetrical Pause is available only for the Full-Duplex links. * Click on the Apply button to confirm the choices.

Note

When two or more Auto Negotiation parameters are simultaneously enabled, the equipment will select the best signal available on the link.

Note

Click on Restart Negotiation button in order to reactivate the Auto Negotiation request.

If the Auto Negotiation function is disabled When the Auto Negotiation function is disabled the Ethernet Manual configuration parameters are shown (see the following picture) instead of the Local Config. capabilities.

* Set the bit rate by using the relative radio buttons. Two option are available: 10Mb/s bit rate The bit rate is set to 10Mb/s 100Mb/s bit rate The bit rate is set to 100Mb/s

* Set the Half duplex or Full duplex function by using the relative radio buttons. * Enable or disable the Asymmetrical pause function by using the relevant scroll list. Note

For the optical interface the bit rate is permanent set as 100Mb/s and the duplex is permanent set as Half duplex.

In order to summarize the current state of Ethernet parameter configuration of both the local and remote ports, are shown several read only parameters under the label Used Setting and Remote Status respectively as listed in the following: n ·

Auto Neg.

n ·

Bit Rate

n ·

Duplex

n ·

Pause


339-1268/06

.

Navigation Page

189

Book Contents


See Also: 8xFast Ethernet Unit: Ethernet Ports Configuration folder

8xFast Ethernet Unit: MAC_Service section Path (8xFast Ethernet Unit Menu -> Channel -> Ethernet ports) In this section is described the MAC and Service parameters configuration procedure for the Fast Ethernet Unit.

To Configure the MAC parameters * Select the port number previously equipped to be enabled in the relevant scroll list. * Define the size of the Ethernet packets using the scroll list in the field Mtu size [byte]. (The range of these value is between from 64 to 1600 byte, 1-byte step).

Enable or disable the Shaping Function The Shaper function delay the transition of packets within a data stream. * Define whether the Shaper function is enabled or disabled by checking or not the Shaper Enable check box respectively.

To Configure the Tail Drop parameters * Set the Queue configuration by using the relative check boxes. The following options are alternatively available: Pseudo Red Pseudo – Random Early Discard is used in correlation with the TCP congestion control mechanism to avoid the packet congestions. By randomly dropping packet prior to periods of high congestion, the P-RED tells the packet source to decrease its transmission rate. Tail Drop The excess packets are discarded if incoming Ethernet packets exceeds the capacity of the queue (overflow).

To Configure the Pseudo Red parameters * Define the upper threshold for the packet number, by using the relevant scroll list (the range of this value is between from 3 to 512, 1 packet step). * Define the lower threshold for the packet number, by using the relevant scroll list (the range of this value is between from 1 to 512, 1 packet step).

To Configure the Tail Drop parameters * Define the Queue Threshold [packet] by using the relevant scroll list (the range of this value is between from 7 to 512, 1 packet step). Note

The Queue Size is a only read field.

To Manage the Ethernet Data Performance * Click on the Rmon Performance button in order to show the Rmon Performance window. * Click on the Mon Performance button in order to show the Mon Performance window.


339-1268/06

.

Navigation Page

190

Book Contents


* Click on the Eth Queue Statistics button in order to show the Eth Queue Statistics window. * Click on the Apply button to confirm the choice. See Also: 8xFast Ethernet Unit: Ethernet Ports Configuration folder, Local Ethernet Data Performance, Remote Ethernet Data Performance, Queue Ethernet Data Performance

8xFast Ethernet Unit: Groups Configuration folder Path (8xFast Ethernet Unit Menu -> Channel -> Groups Configuration) By clicking on the Groups Configuration button, the relevant folder is displayed.

To configure the Virtual Container Group * Select the VCG to be configured in the relevant scroll list.

To enable/disable the LCAS function * Define whether the LCAS function is enabled or disabled by using the Mapping scroll list. The LCAS function provides hitless insertion or deletion of VC-ns (n=12 or n=3 depending on the requested bandwidth) to /from a VCG. Moreover, the LCAS function provides automatic re-sizing of the SDH capacity if one or more VC-ns in the VCG fails, and automatic hitless re-insertion of the VC-n(s) when the fault is cleared. Note

Some parameters described in the following will be displayed on the VCH Par. Config window only if the LCAS function is enabled as shown in the following picture.


339-1268/06

.

Navigation Page

191

Book Contents


To Configure the Seq.Numering function (LCAS funct. disabled) * Set the Seq.Numering function by using the relative radio buttons. The following options are alternatively available: automatic The sent Sequence Number is defined allocating consecutive sequence numbers to all VCs in a VCG.

Note

For automatic configuration, when a VC is added to an existing VCG, automatically a sequence number sent one higher than the current highest sequence number is allocated to it, while when a VC is deleted from an existing VCG, automatically a “close the gap” procedure is performed (i.e., the sequence number sent of the members with sequence numbers higher than the one removed are decrement).

manual Manually insertion of both the expected and sent values for each VC in the VCG.

Note

For manual configuration, the value of SQ must be unique within the VCG. Moreover the SQ number must be consecutive.

To Configure the Delay functions * Set the delay insertion type by using the relative radio buttons. The following options are alternatively available: Delayed – hitless The delay time is not configured immediately but this operation it is hitless. Immediate – noising The delay time is configured immediately but this operation it is not hitless.


339-1268/06

.

Navigation Page

192

Book Contents


Note

If the Delayed – hitless option is set, it is possible enable or not the Auto Adaptive function by clicking on the relevant check box.

If Delayed – hitless option is set * Define whether the Auto Adaptive function is enabled or disabled by checking or not the relevant check box respectively. When enabled the Unit automatically sets the right delay time value. * If the Auto Adapative function is disabled, define the delay period by using the Delay value [ ms] scroll list (the range of this value is between from 25ms to 64ms, 0.5ms step). The default value is set as 32ms. IMPORTANT For the VC12 channels is strongly suggested not over 32 msec for the Delay value.

To Configure the Encapsulation mode * Set the GFP (Generic Framing Procedure) function by using the relative radio button. This functionality is a generic mechanism for protocol data unit (PDU)-oriented (Ethernet) client signal adaptation to enable data mapping into a SDH virtual container. Note

The GFP function is only available encapsulation mode. * Enable or disable the FCS (Frame Ceck Sequency) function by using the relative check box. This function is a count of frames received with a length between 64 bytes and the maximum packet size, an integral byte count and a CRC error. * Define the Link Fail Persistence by using the relevant scroll list (the range of this value is between from 1 to 10, 1 step).

To Configure the Alarm Parameters (when LCAS is enabled) * Define the Crc Alarm Threshold value, by using the relevant scroll list (the range of this value is between from 1 to 16, 1 step). This function defines the number of excessive consecutive detection errored multi-frames necessary to raise an alarm. of CRC errors. * Define whether the LOPC alarm relative to the Sink is enabled or disabled by checking or not the Sink Enable State check box respectively. * Define whether the LOPC alarm relative to the Source is enabled or disabled by checking or not the Source Enable State check box respectively.

If the LOPC parameter relative to the Sink is enabled * Define the Threshold relate to the Sink by using the relevant scroll list (the range of this value is between from 1 to 6 (1 step). This parameter indicates the number of channels failed necessary to raise an alarm.

If the LOPC parameter relative to the Source is enabled * Define the Threshold relate to the Source by using the relevant scroll list (the range of this value is between from 1 to 6, 1 step). This parameter indicates the number of channels failed necessary to raise an alarm.

To Configure the LCAS Protection Parameters (when LCAS is enabled)


339-1268/06

.

Navigation Page

193

Book Contents


* Define the PathFail Holdoff [sec] by using the relevant scroll list (the range of this value is between from 0s to 20s, 0.1s step). This parameter indicates the waiting time before raising a LOPC/LOTC (loss of partial capacity, loss of total capacity) alarm. * Define the PathFail WTR [min] by using the relevant scroll list (the range of this value is between from 0m to 20m, 1m step. This parameter indicates the waiting time before cleaning a LOPC/LOTC (loss of partial capacity, loss of total capacity) alarm. * Set the TFS Criteria to be enabled by checking the relevant check boxes. In the TSF Criteria field it is possible to select the alarm criteria to have the relevant VC-4 /Vc-3/VC12 disabled. In the following are described the TFS Criteria options available to be enabled. n Deg n Lom n Tim n Plm n Exc n Loa n Unequipped n Ais n Lop

To configure the LCAS mapping (when LCAS is enabled) * Define the Loa Mode type: either Group or Path by using the Loa Mode scroll list. This parameter is used to set the Loa alarm either to the whole Virtual Concatenated Group (Group) or to the single VC-4/VC-3-Xv/VC-12-Xv channel (Path). * Set the dLOM Treshold [ms] by using the relevant scroll list. This parameter indicates the duration of the loss of multiframe state necessary to raise an alarm, (the range of this value is between from 1ms to 5ms, 1ms step). * Define the dSQM Threshold [#MFr] by using the relevant scroll list. This parameter indicates the number of multiframes with wrong sequence necessary to emit an alarm of dSQM, (the range of this value is between from 1 to 10, 1 step). * Define the dSQM Recovery [#MFr] by using the relevant scroll list. This parameter indicates the number of multiframes with right sequence necessary to remove an alarm of dSQM, (the range of this value is between from 3 to 10, 1 step). * Click on the Alarm Management button site on the right side of the window in order to visualize the Alarm Severity window for the adaptation. * Click on the Alarm Management button site on the left side of the window in order to visualize the Remote Alarm Severity window for the group. See Also: 8xFast Ethernet Unit: Ethernet Ports Configuration folder, Fault Detection Procedure, Alarm Reporting


339-1268/06

.

Navigation Page

194

Book Contents


8xFast Etherent Unit: Bandwidth Allocation folder Path (8xFast Ethernet Unit Menu -> Channel -> Bandwidth Allocation.) By clicking on the Bandwidth Allocation button, the relevant folder is displayed.

To allocate a VC-n channel in a Virtual Container Group On the left side of this folder are shown two columns . Under the column called “Assigned channel” are shown the Virtual Container Groups (VCG) and the Virtual Container (VC) within of the Virtual Container Groups (VCG), while under the column called “Free Channel” are shown the Virtual Container channel (VC-n) not yet involved in a Virtual Container Group (VCG). The VCG associate to the physical port, has been previously configured either as nV or LCAS mapping. The insertion procedure of a VC channel in a VCG is function of these different VCG mapping modes. Note

The VC-n can be a VC-12,VC-3 and VC-4 for MSH41C only, while the VC-n is always a VC-4 for MSH51C/64C.

To explode a VC-4 into its lower order components In the following will be described the case of a VC-4 exploded into its lower order component. The same description can be applicable to the VC-3 channels. * Select one of two VC-4s available under the column Free channels by double clicking on it. * Select the multiplex level in order to split the VC-4 into its lower level components (3 VC-3 channels for the TU3 and 63 VC-12 channels for the TU12.). The following picture shows the case of VC-4 exploded into 3 VC-3. Please note that only the TU12 button is now available to explode the VC-3s into 21 VC-12 for each VC-3.


339-1268/06

.

Navigation Page

195

Book Contents


The following picture shows the case of the first VC-3 (VC-3 obtained from VC-4 as described above) exploded into 21 VC-12 . In order to visualize all channels under the Free Channels column, using the relevant scroll list.

To demultiplex a VC4/VC3 channel * Select the VC-4/VC-3 previously exploded into its lower order components by double clicking on it Note

It is not possible demultiplex a VC-4/VC-3 channel associated either to a VCG and/or to a cross connection. When the channel is not free, before de-associate the channel from either the VCG and/or from the cross connection and then proceed with its demultiplexing.

If the selected VCG is configured as nV * Under the column Assigned channels select the VCG associated to the port number previously equipped. * Under the column Free channels select the a VC-n not yet involved in a Virtual Container Group. * Enable the Source Allocation function by checking on the relevant check box and simultaneously the Sink Allocation function will be enabled. * Click on the Apply button in order to insert the VC-n channel into the VCG. * Repeat the steps from n. 2 to n.4 in order to insert another VC-n channel into the selected Virtual Container Group, otherwise jump to the next step.


339-1268/06

.

Navigation Page

196

Book Contents


* Repeat the steps from n.1 to n.5 in order to insert another Virtual Container Group, otherwise jump to the next step. * When the Bandwidth allocation procedure is ended, click on the OK button to confirm last action and close this window, while click on the Close button to reject the last action and close this window.

If the selected VCG is configured as LCAS * Under the column Assigned channels select the VCG associated to the port number previously equipped. * Under the column Free channels select the a VC-n not yet involved in a Virtual Container Group. * Define whether the Source Allocation function is enabled or disable by checking or not the relevant check box. * Define whether the Sink Allocation function is enabled or disable by checking or not the relevant check box. Note

It is mandatory always enable either the Source Allocation or the Sink Allocation. It is also possible to enable both the functions simultaneously. * Click on the Apply button in order to insert the VC-n channel into the VCG. * Repeat the steps from n. 2 to n.5 in order to insert another VC-n channel into the selected Virtual Container Group, otherwise jump to the next step. * Repeat the steps from n.1 to n.6 in order to insert another Virtual Container Group, otherwise jump to the next step. * When the Bandwidth allocation procedure is ended, click on the OK button to confirm last action and close this window, while click on the Close button to reject the last action and close this window.

To De-allocate a VC-n channel from a Virtual Container Group * Under the column Assigned channels select the VC-n channel. * Disable both the Source Allocation (if previously enabled) and Sink Allocation (if previously enabled) functions by checking on the relevant check boxes. * Click on the Apply button in order to confirm the request of de-allocation of the VC-n channel from the VCG. After this action the selected VC-n will be collocate under the column Free Channels. * Repeat the steps from n. 2 to n.3 in order to de-allocate another VC-n channel from the selected Virtual Container Group, otherwise jump to the next step. * Repeat the steps from n.1 to n.4 in order to de-allocate another VC-n channel from a new Virtual Container Group, otherwise jump to the next step. * Click on the OK button to confirm the last action and close this window, while click on the Close button to reject the last action and close this window .


339-1268/06

.

Navigation Page

197

Book Contents


Description of the icon text channel shown under the column “Assigned Channels” within of the “Bandwidth Allocation” folder Generally the icon text representative the VC-n channel allocate into a VCG could be different, because different are the situations where the channel could be involved (the Vc-n channel could be allocate into a VCG where a LCAS mapping is enabled and only the Source Allocation is active or the VC-n channel could be allocate into a VCG where a nV mapping is enabled and consequently both the Source and the Sink Allocation function are active, and so on.). In all cases a arrow icon, site near on the right side of the icon text representative of the VC-n channel will be shown. This arrow can be shown in three different mode as described in the following: n Left arrow “->” On the generic VC-n channel is active only the Sink Allocation function (only for LCAS enabled); n Right arrow “<-“ On the generic VC-n channel is active only the Source Allocation function (only for LCAS enabled); n Bidirectional arrow “<->” On the generic VC-n channel are active both the Sink and the Source Allocation function. See Also: 8xFast Ethernet Unit: Unit Configuration

8xFast Etherent Unit: Port folder Path (8xFast Ethernet Unit Menu -> Channel -> Unit Config.) By clicking on the Port button, the relevant folder is displayed.


339-1268/06

.

Navigation Page

198

Book Contents


Note

The picture shown above is only an example and it is displayed when a VC-4 or VC-3 channel is selected. If a VC-12 is selected the “J2 Path Trace” and “V5 Signal label” fields will be shown instead of the “J1 Path Trace” and “C2 Signal label” ones respectively.

In this folder it is possible to set the SDH parameter of the VC-n channel previously allocated into the VCGs.

To Configure the VC-4/VC3 (*) Channel Parameters Note(*)

For MSH51C/64 equipments, only VC-4 channels are available. * Select the VC-4 or VC-3 to be configured in the Port scroll list. * Define the expected value of path trace, on byte J1 by using the relevant scroll list as shown in the following picture.

Define the expected value of path trace, on byte J1 by using the relevant scroll list as shown in the following picture. For the expected and sent value of J1 path trace, five different configurations can be selected: E164 Ascii View The path trace is represented as a string of fifteen ASCII characters; E164 Hex View The path trace is represented as a string of fifteen Hexadecimal characters; Disable The path trace management is not used; Blank Fill The path trace is represented as a string of blanks; Zero Fill The path trace is represented as a string of all zeros.

Note

If the received J1 path trace value can’t be read, the J1 Path Trace Received field will contain a string of fixed byte, represented by the string Fixed Byte. * Define the expected value of path trace, on byte C2 by using the relevant arrow button. Several options are available as listed in the following:

n Not spec. n GFP encap


339-1268/06

.

Navigation Page

199

Book Contents


* Set the SDH SD Threshold (Signal Degrade Threshold) to be used by clicking on the relevant radio buttons. Two options are alternatively available: ITUT Values from 10-9 to 10-5 ETSI From 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire.

* Click on the Apply button to confirm the actions. * Click on the Refresh button to update the window.

To Configure the VC-12 (*) Channel Parameters Note(*)

The VC-12 channels are not available for the MSH51C/64 equipments. * Select the VC-12 to be configured in the Port scroll list. * Define the expected value of path trace, on byte J2 by using the relevant scroll list as shown in the following picture.

* Define the expected value of path trace, on byte J2 by using the relevant scroll list as shown in the following picture. For the expected and sent value of J2 path trace, five different configurations can be selected: E164 Ascii View The path trace is represented as a string of fifteen ASCII characters; E164 Hex View The path trace is represented as a string of fifteen Hexadecimal characters; Disable The path trace management is not used; Blank Fill The path trace is represented as a string of blanks; Zero Fill The path trace is represented as a string of all zeros.

Note

If the received J2 path trace value can’t be read, the J2 Path Trace Received field will contain a string of fixed byte, represented by the string Fixed Byte. * Define the expected value of path trace, on byte V5 by using the relevant arrow button. Several options are available as listed in the following:


339-1268/06

.

Navigation Page

200

Book Contents


n Not spec. n GFP encap * Set the SDH SD Threshold (Signal Degrade Threshold) to be used by clicking on the relevant radio buttons. Two options are alternatively available: ITUT Values from 10-9 to 10-5 ETSI From 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is under the configured Good threshold, the alarm will expire.

* Click on the Path Term Data button in order to show the relevant window. * Click on the Alarm Management button in order to show the Alarm Severity window for the VC-n channels. * Click on the Apply button to confirm the actions. * Click on the Refresh button to update the window. See Also: 8xFast Ethernet Unit: Unit Configuration, Fault Detection Procedure, Alarm Reporting


339-1268/06

.

Navigation Page

201

Book Contents

PERFORMANCE PERFORMANCE: ALL PERFORMANCES Path (Performance -> All Perf) This item is used to start and set-up the collection of the information quality data.

To delete a performance data collection: * Select the monitored entity from the list. * Click on the Delete button.

To read the performance data or modify the parameters of an enabled monitored entity: * Select the monitored entity from the list. * Click on the Modify button or double click on the monitored entity and the related performance window will appear. * Click on the Export push button to save the collected data on a file on the pc. * Click on the Suspend or Resume push button to stop or to restart the whole performance data collection (all registers are stopped or restarted). * Click on the Clear History push button to delete all the data collected in the performance registers. * Click on the Cnt Reset push button to reset the current counters on all performance registers. *

Use Request to access the value of the current register.


339-1268/06

.

Navigation Page

Book Contents

MSHXXX - OPERATOR’S HANDBOOK PERFORMANCE

* Clicking on the Select button the Item Search and Selection window will appear. Within this window several options relevant to string selection and searching are available. Select the Select push button allows to select all the items containing the searched string inserted String to search field Search the Search push button allows to search all the items containing the searched string inserted String to search field Unselect the Unselect push button allows to select all the items selected using the Select push button Cancel This button allows to exit the window

* Click on Close to exit the performance window. The possible performance windows are the following: RS Data

Both the 15 minutes and the 24 hours registers are available in order to store the performance data in 15 minutes periods (15 Min. folder) or in 24 hours periods (24 Hrs. folder). In order to enable the data collection: * Choose the register in which the performance data collection will be enabled, by clicking on the 15 Min. or 24 Hrs. folder. * Set the exception threshold set by means of Perf Trh pull down menu. * Set the CSES Threshold using the relevant scroll list. When this threshold is exceeded, the number of the detected CSES and the period in which they are detected are shown in the window placed on the right side in the upper part of the folder. * Enable the performance data collection by clicking on the Enable button.


339-1268/06

.

Navigation Page

203

Book Contents


In the History Data window the performance samples are displayed with the information relevant to the monitored performance parameters (BBE, ES, SES, UAS and OFS). If no protection event happens during the aggregation period (parameters equal to zero during 15 minutes or 24 hours), the relevant sample will not be displayed in the History Data window and the # Suppressed field will be incremented. By means of the Delete push button, the samples present in the History Data window are deleted. By means of Request push button, a query on the status of the current register can be performed. By selecting Continuous check box, the status of the current register is displayed every second. By means of Suspend and Resume push buttons, the operator can suspend and restart the performance data collection. By means of Disable push button, the performance data collection is stopped. By means of Cnt. Reset push button, the counters’ value in the current aggregation period is reset. See Also: STM-n Units Performance Data, nx140/155Mbit/s Units Performance Data MS Data and Path Termination Data VC-3/VC-2/VC-12

Four registers are available in order to store the performance data with attention to the duration of the collection periods (15 minutes periods or 24 hours periods) and to the location of the termination point where the performance is calculated (Near End = Local; Far End = Remote). In order to enable the data collection: * Choose the register in which the performance data collection will be enabled, by clicking on the Near End 15 Min., Near End 24 Hrs., Far End 15 Min. or Far End 24 Hrs. folder. * Select the exception threshold set by means of Perf Trh pull down menu. * Set the CSES Threshold using the relevant scroll list. When this threshold is exceeded, the number of the detected CSES and the period in which they are detected are shown in the window placed on the right side in the upper part of the folder.


339-1268/06

.

Navigation Page

204

Book Contents


* Enable the performance data collection by clicking on the Enable button. In the History Data window the performance samples are displayed with the information relevant to the monitored performance parameters (BBE, ES, SES, UAS and OFS). If no protection event happens during the aggregation period (parameters equal to zero during 15 minutes or 24 hours), the relevant sample will not be displayed in the History Data window and the # Suppressed field will be incremented. By means of the Delete push button, the samples present in the History Data window are deleted. By means of Request push button, a query on the status of the current register can be performed. By selecting Continuous check box, the status of the current register is displayed every second. By means of Suspend and Resume push buttons, the operator can suspend and restart the performance data collection. By means of Disable push button, the performance data collection is stopped. By means of Cnt. Reset push button, the counters’ value in the current aggregation period is reset. See Also: STM-n Units Performance Data, nx140/155Mbit/s Units Performance Data, 34-45Mbit/s Units Performance Data, 2Mbit/s Units Performance Data


339-1268/06

.

Navigation Page

205

Book Contents


Optical Measure

By means of this option the following parameters, related to the laser of the STM-N optical unit, are monitored: - TxPw (dB): transmitted optical power expressed in dBm; - RxPw (dB): received optical power expressed in dBm; - Bias (mA): laser pump bias current expressed in mA; - Temp (C): laser pump temperature expressed in Celsius degrees. In order to enable the data collection: * Use the Enable button to start a measure (an existing measure can be stopped or disabled). By means of Request push button, a query on the status of the current register can be performed. By selecting Continuous check box, the status of the current register is displayed every second. By means of Suspend and Resume push buttons, the operator can suspend and restart the performance data collection. By means of Disable push button, the performance data collection is stopped. See Also: STM-n Units Performance Data, Booster and Preamplifier Units Performance Data


339-1268/06

.

Navigation Page

206

Book Contents


MS Adapt. Data

Both the 15 minutes and the 24 hours registers are available in order to store the performance data in 15 minutes periods (15 Min. folder) or in 24 hours periods (24 Hrs. folder). In order to enable the data collection: * Choose the register in which the performance data collection will be enabled, by clicking on the 15 Min. or 24 Hrs. folder. * Set the exception threshold set by means of Perf Trh pull down menu. * Enable the performance data collection by clicking on the Enable button. In the History Data window the performance samples are displayed with the information relevant to the monitored performance parameters (pJC+ and pJC-). If no protection event happens during the aggregation period (parameters equal to zero during 15 minutes or 24 hours), the relevant sample will not be displayed in the History Data window and the # Suppressed field will be incremented. By means of the Delete push button, the samples present in the History Data window are deleted. By means of Request push button, a query on the status of the current register can be performed. By selecting Continuous check box, the status of the current register is displayed every second. By means of Suspend and Resume push buttons, the operator can suspend and restart the performance data collection. By means of Disable push button, the performance data collection is stopped. By means of Cnt. Reset push button, the counters’ value in the current aggregation period is reset. See Also: STM-n Units Performance Data, nx140/155Mbit/s Units Performance Data


339-1268/06

.

Navigation Page

207

Book Contents


Protection Data

Both the 15 minutes and the 24 hours registers are available in order to store the performance data in 15 minutes periods (15 Min. folder) or in 24 hours periods (24 Hrs. folder). In order to enable the data collection: * Choose the register in which the performance data collection will be enabled, by clicking on the 15 Min. or 24 Hrs. folder. * Select the exception threshold set by means of the Perf Trh pull down menu. * Enable the performance data collection by clicking the Enable push button. In the History Data window the performance samples are displayed with the information relevant to the monitored performance parameters (PSC and PSD). If no protection event happens during the aggregation period (parameters equal to zero during 15 minutes or 24 hours), the relevant sample will not be displayed in the History Data window and the # Suppressed field will be incremented. By means of the Delete push button, the samples present in the History Data window are deleted. By means of Request push button, a query on the status of the current register can be performed. By selecting Continuous check box, the status of the current register is displayed every second. By means of Suspend and Resume push buttons, the operator can suspend and restart the performance data collection. By means of Disable push button, the performance data collection is stopped. By means of Cnt. Reset push button, the counters’ value in the current aggregation period is reset. See Also: Specific Functions: MSP Protection (ADM)


339-1268/06

.

Navigation Page

208

Book Contents


Path Termination Data VC-4, PDH In Data, PDH Out Data

Both the 15 minutes and the 24 hours registers are available in order to store the performance data in 15 minutes periods (15 Min. folder) or in 24 hours periods (24 Hrs. folder). In order to enable the data collection: * Choose the register in which the performance data collection will be enabled, by clicking on the 15 Min. or 24 Hrs. folder. * Set the exception threshold set by means of Perf Trh pull down menu. * Enable the performance data collection by clicking on the Enable button. In the History Data window the performance samples are displayed with the information relevant to the monitored performance parameters (BBE, ES, SES, UAS and OFS). If no protection event happens during the aggregation period (parameters equal to zero during 15 minutes or 24 hours), the relevant sample will not be displayed in the History Data window and the # Suppressed field will be incremented. By means of the Delete push button, the samples present in the History Data window are deleted. By means of Request push button, a query on the status of the current register can be performed. By selecting Continuous check box, the status of the current register is displayed every second. By means of Suspend and Resume push buttons, the operator can suspend and restart the performance data collection. By means of Disable push button, the performance data collection is stopped. By means of Cnt. Reset push button, the counters’ value in the current aggregation period is reset. See Also: nx140/155Mbit/s Units Performance Data, 2Mbit/s Units Performance Data


339-1268/06

.

Navigation Page

209

Book Contents


Path Termination Data 8xFast Ethernet Unit

Four registers are available in order to store the performance data with attention to the duration of the collection periods (15 minutes periods or 24 hours periods) and to the location of the termination point where the performance is calculated (Near End = Local; Far End = Remote). In order to enable the data collection: * Choose the register in which the performance data collection will be enabled, by clicking on the Near End 15 Min., Near End 24 Hrs., Far End 15 Min. or Far End 24 Hrs. folder. * Select the exception threshold set by means of Perf Trh pull down menu. * Set the CSES Threshold using the relevant scroll list. When this threshold is exceeded, the number of the detected CSES and the period in which they are detected are shown in the window placed on the right side in the upper part of the folder. * Enable the performance data collection by clicking on the Enable button. In the History Data window the performance samples are displayed with the information relevant to the monitored performance parameters (BBE, ES, SES, UAS and OFS). If no protection event happens during the aggregation period (parameters equal to zero during 15 minutes or 24 hours), the relevant sample will not be displayed in the History Data window and the # Suppressed field will be incremented. By means of the Delete push button, the samples present in the History Data window are deleted. By means of Request push button, a query on the status of the current register can be performed. By selecting Continuous check box, the status of the current register is displayed every second. By means of Suspend and Resume push buttons, the operator can suspend and restart the performance data collection. By means of Disable push button, the performance data collection is stopped. By means of Cnt. Reset push button, the counters’ value in the current aggregation period is reset. See Also: 8xFast Ethernet Unit: Unit Configuration, Local Ethernet Data Performance, Remote Ethernet Data Performance


339-1268/06

.

Navigation Page

210

Book Contents


PERFORMANCE MANAGEMENT: THRESHOLD PROFILES Path (Performance -> Trh profiles) This option is used to set the eight available exception threshold sets for the performance parameters related to the selected entity type and its associated aggregation period. When an exception threshold is exceeded, a message related to its performance parameters appears in the Alarm and Event Monitor Window.

The pull down menu at the top of the window contains the entity types on which the operator can enable a performance exception threshold. These entity types are listed in the following: Path Term. Data for VC2, VC12 15min (ADM-4) Performance data related to a VC-2, VC-12 stored in a Near End 15 minutes register and in a Far End 15 minutes register Path Term. Data for VC-2, VC12 24h (ADM-4) Performance data related to a VC-2, VC-12 stored in a Near End 24 hours register and in a Far End 24 hours register Path Term. Data for VC4, VC3 15min (ADM-4) Performance data related to a VC-4, VC-3 stored in a Near End 15 minutes register and in a Far End 15 minutes register Path Term. Data for VC4, VC3 24h (ADM-4) Performance data related to a VC-4, VC-3 stored in a Near End 24 hours register and in a Far End 24 hours register Path Term. Data for AU4-VC4 15min (ADM-16) (ADM-64) Performance data related to an AU-4, VC-4 stored in a Near End 15 minutes register and in a Far End 15 minutes register for ADM-16, only in a Near End 15 minutes register for ADM-64


339-1268/06

.

Navigation Page

211

Book Contents


Path Term. Data for AU4-VC4 24h (ADM-16) (ADM-64) Performance data related to an AU-4, VC-4 stored in a Near End 24 hours register and in a Far End 24 hours register for ADM-16, in a Near End 24 hours register for ADM-64 MS Data 15min (ADM) Performance data related to a Multiplex Section stored in a Near End 15 minutes register and in a Far End 15 minutes register for ADM-4 and ADM-16, only in a Near End 15 minutes register for ADM-64 MS Data 24h (ADM) Performance data related to a Multiplex Section stored in a Near End 24 hours register and in a Far End 24 hours register for ADM-4 and ADM-16, only in a Near End 24 hours register for ADM-64 RS Data 15min Performance data related to a Regenerator Section stored in a 15 minutes register RS Data 24h Performance data related to a Regenerator Section stored in a 24 hours register MS/TU Adapt. Data 15min (ADM) Performance data related to an AU-4 stored in a 15 minutes register for all ADM equipment and related to a TU stored in a 15 minutes register for ADM-4 MS/TU Adapt. Data 24h (ADM) Performance data related to an AU-4 stored in a 24 hours register for all ADM equipment and related to a TU stored in a 15 minutes register for ADM-4 Protection Data 15min (ADM) Performance data related to a MSP stored in a 15 minutes register Protection Data 24h (ADM) Performance data related to a MSP stored in a 24 hours register TC Path Term Data for VC2-VC12 15m (ADM-4) Performance data related to a VC-2, VC-12 involved in a Tandem Connection stored in a Near End 15 minutes register TC Path Term Data for VC2-VC12 24h (ADM-4) Performance data related to a VC-2, VC-12 involved in a Tandem Connection stored in a Near End 24 hours register TC Path Term Data for VC4-VC3 15m (ADM-4) Performance data related to a VC-4, VC-3 involved in a Tandem Connection stored in a Near End 15 minutes register TC Path Term Data for VC4-VC3 24h (ADM-4) Performance data related to a VC-4, VC-3 involved in a Tandem Connection stored in a Near End 24 hours register TC Path Term Data for VC4 15m (ADM-16) Performance data related to a VC-4 involved in a Tandem Connection stored in a Near End 15 minutes register TC Path Term Data for VC4 24h (ADM-16) Performance data related to a VC-4 involved in a Tandem Connection stored in a Near End 24 hours register


339-1268/06

.

Navigation Page

212

Book Contents


For each entity type the operator can set different exception threshold related to different performance parameters. For the Path Term. Data for VC-2, VC-12 15min, Path Term. Data for VC-2, VC-12 24h, Path Term. Data for VC-4, VC-3 15min, Path Term. Data for VC-4, VC-3 24h, Path Term. Data for AU-4-VC-4 15min, Path Term. Data for AU-4-VC-4 24h, MS Data 15min, MS Data 24h, TC Path Term Data for VC2-VC12 15m, TC Path Term Data for VC2-VC12 24h, TC Path Term Data for VC4-VC3 15m, TC Path Term Data for VC4-VC3 24h, TC Path Term Data for VC4 15m, TC Path Term Data for VC4 24h entity types, the following performance parameters appear: n BBE (Background Block Error) n ES (Errored Second) n SES (Severely Errored Second) n CSES (Consecutive SES) For the RS Data 15min and RS Data 24h entity types, the following performance parameters appear: n BBE n ES n SES n CSES n OFS (Out of Frame Second) For the MS/TU Adapt. Data 15min and MS/TU Adapt. Data 24h entity types, the following performance parameters appear: n PJC+ (Pointer Justification Counter +): indicates the number of increments in the pointer value n PJC- (Pointer Justification Counter -): indicates the number of decrements in the pointer value For the Protection Data 15min and Protection Data 24h entity types, the following performance parameters appear: n PSC (Protection Switching Counter): indicates the number of protection switching n PSD (Protection switching Duration): indicates the protection duration in seconds To set the exception thresholds for an entity: * Select the entity type with its aggregation period by mean of the pull down menu. * Use the arrow buttons to set the eight exception threshold sets. Each set has two configurable values: Max when the number of the monitored events exceeds this value, a reporting message appears in the Alarm and Event Monitor Window Min when the number of the monitored events does not exceed this value during all the related aggregation period, the reporting message disappears from the Alarm and Event Monitor Window

* Press Apply to confirm the new settings.


339-1268/06

.

Navigation Page

213

Book Contents


* Use Request to access the value of the current entity type and its associated aggregation period. * Click on Default and then confirm by pressing the Apply button to restore the default values. See Also: Performance: All Performances

LOCAL ETHERNET DATA PERFORMANCE Path (8xFast Ethernet Unit Menu -> Channel -> Ethernet ports -> MON Performances). By means of this folder it is possible to enable/disable and read the local Ethernet data Performance of the monitored port. The local Ethernet data Performances are shown as snapshots wich represent a cumulative report of the number of occourrences since the local Ethernet interface was last reset, or since the snapshot counts were last manually reset.

To enable the Local Ethernet performance monitoring * Select the Channel item in the 8xFast Ethernet Unit menu (step n.1). * Click on the Ethernet Ports button in order to display the relevant folder (step n.2). * Select the port previously configured from the ports list field (step n.3). * Click on the on the MON Performance button in order to display the local Performance Monitoring Management folder (see the picture below) for the selected port (step n.4).

* Define whether the Data Collection counters are enabled or disabled by clicking on the relevant button (step n.5).


339-1268/06

.

Navigation Page

214

Book Contents


* Define whether the Automatic counters Reset function is Enabled or Disabled by checking or not the relevant check box respectively (step n.6). * Define whether the Automatic refresh function of the current register status is enabled or disabled by checking or not the Continuous check box respectively (step n.7). Note

Perform the step n.8, only if the “Continuous” check box is enabled, otherwise jump to the step n.9 . * Set the refresh time of the current register status using the relevant scroll list (The range of these value is between from 1s to 3600s, 1s step) (step n.8). * Click on the Apply button to confirm the choices (step n.9). * Finally, by means of Request button, a query on the status of the current register can be performed (step n.10).

The following table describers all snapshots shown in the local Performance Monitoring Management folder shown above. Local Ethernet Data Performance Snapshot Counters Counter name

Direction

Description

Notes

In

Out

ü

ü

---

ü

ü

Note1

ü

ü

Note2, Note3

ü

ü

Note4, Note5

ü

ü

Note6

The total number of octets of data (including those in bad Octets

packets) received on the network (excluding framing bits but including FCS octets)

Unicast Fr. Multicast Fr.

Broadcast Fr.

Pause Fr.

The total number of unicast packets without errors. The total number of good packets that were directed to a multicast address. The total number of good packets that were directed to the broadcast address. A count of MAC control frames received/transmitted on the interface with an opcode indicating the PAUSE operation.

InErrors

The number of incoming packets containing errors.

ü

---

---

OutErrors

The number of outgoing packets containing errors.

ü

---

---

Count of frames received with a length between 64 bytes fcs

and the maximum packet size, an integral byte count and a

ü

---

ü

Note7

ü

---

ü

Note8

CRC error. FrmTooLong

MauJabEntry

The total number of packets received that exceed the maximum permitted frame size. The number of times that MauJabberState for this MAU instance enters the state jabbering. The number of times that the carrier sense condition was

CarrierSense

lost or never asserted when attempting to transmit a frame on a particular interface.


339-1268/06

.

Navigation Page

215

Book Contents


Discarded Fr.

The number of packets discarded by the queue even though no errors had been detected to prevent their delivery.

ü

ü

A count of successfully transmitted frames on a particular SingColl Fr.

interface for which transmission is inhibited by exactly one

ü

Note9

ü

Note10

collision. A count of successfully transmitted frames on a particular MultiColl Fr.

interface for which transmission is inhibited by more than one collision.

A count of frames for which the first transmission attempt on DeferColl Fr.

ü

a particular interface is delayed because the medium is busy.

LateColl Fr.

ExcColl Fr.

The number of times that a collision is detected on a particular interface during the transmission of a packet. A count of frames for which transmission on a particular interface fails due to excessive collisions.

Note11, Note12

ü

Note13

ü

Note14

The following notes are referred to the Local Ethernet Data Performance Snapshot Counters table show above. Note 1

The Unicast Frame value does not include MAC Control frames, since MAC Control frames are consumed by the interface layer and are not passed to any higher layer protocol.

Note 2

The Multicast Frame value does not include packets directed to the broadcast.

Note 3

The Multicast Frame value does not include MAC Control frames, since MAC Control frames are consumed by the interface layer and are not passed to any higher layer protocol.

Note 4

The Broadcast Frame value does not include multicast packets.

Note 5

The Broadcast Frame value does not include MAC Control frames, since MAC Control frames are consumed by the interface layer and are not passed to any higher layer protocol.

Note 6

The Pause Frame counter is not applicable for half-duplex interfaces.

Note 7

The Frame To Long counter is only applicable to 10Mb/s interfaces. This counter will always indicate 0 for MAUs above 10Mb/s.

Note 8

The Carrier sense counter is not applicable for full-duplex operation mode.

Note 9

The Single Collision Frame counter is not applicable for full-duplex operation mode.

Note 10 The Multiple Collision Frame counter is not applicable for full-duplex operation mode. Note 11 The Deferred Transmissions count does not include frames involved in collisions. Note 12 The Deferred Transmissions counter is not applicable for full-duplex operation mode. Note 13 The Late Collision counter is not applicable for full-duplex operation mode. Note 14 The Excessive Collisions counter is not applicable for full-duplex operation mode


339-1268/06

.

Navigation Page

216

Book Contents


See Also: Queue Ethernet Data Performance, Remote Ethernet Data Performance, 8xFast Ethernet Unit: Ethernet Ports Configuration folder

REMOTE ETHERNET DATA PERFORMANCE Path (8xFast Ethernet Unit Menu -> Channel -> Ethernet Config-> RMON Performance). By means of this folder it is possible to enable/disable and read the remote Ethernet data Performance of the selected port. The remote Ethernet data Performances are shown as snapshots which represents a cumulative report of the number of occurrences since the remote Ethernet interface was last reset, or since the snapshot counts were last manually reset.

To enable the Remote Ethernet performance monitoring * Select the Channel item in the 8xFast Ethernet Unit menu (step n.1). * Click on the Ethernet ports button in order to display the relevant folder (step n.2). * Select the port previously configured from the ports list field (step n.3) * Click on the on the RMON Performance button in order to display the remote Performance Monitoring Management folder (see the picture below) for the selected port (step n.4)

* Define whether the Data Collection counters are Enabled or Disabled by clicking on the relevant buttons (step n.5)


339-1268/06

.

Navigation Page

217

Book Contents


* Define whether the Automatic Counters Reset function is enabled or disabled by checking or not the relevant check box respectively (step n.6). * Define whether the Automatic Refresh function of the current register status is enabled or disabled by checking or not the Continuous check box respectively (step n.7) Note

Perform the step n.8, only if the “Continuous” check box is enabled, otherwise jump to the step n.9 . * Set the refresh time of the current register status using the relevant scroll list (The range of these value is between from 1s to 3600s, 1s step) (step n.8). * Click on the Apply button to confirm the choices (step n.9)) * Finally, by means of Request button, a query on the status of the current register can be performed (step n.10).

The following table describers all snapshots shown in the remote Performance Monitoring Management folder shown above. Remote Ethernet data Performance Snapshot Counters Counter name

Direction

Description

Notes

In

Out

ü

ü

---

ü

ü

---

ü

ü

ü

ü

ü

ü

---

ü

ü

---

ü

ü

---

The total number of octets of data (including those in bad Octets

packets) received on the network (excluding framing bits but including FCS octets)

Packets MulticastPackets

BroadcastPackets

The total number of good packets that were directed to a multicast address. The total number of good packets that were directed to the broadcast address.

Note15, Note16 Note17, Note18

The total number of packets received that were less than UndersizePkt

64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed. The total number of packets received that were longer

OversizePkt

than 1518 octets in length inclusive (excluding framing bits but including FCS octets) and were otherwise well formed. The total number of packets that had a length (excluding framing bits, but including FCS octets) of between 64 and

CrcAlignErrors

1518 octets, inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).


339-1268/06

.

Navigation Page

218

Book Contents


The total number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had either a bad Frame Check Sequence Fragments

(FCS) with an integral number of octets (FCS Error) or a

Note19,

ü

ü

ü

ü

Note21

ü

ü

---

ü

ü

---

ü

ü

---

ü

ü

---

ü

ü

---

ü

ü

---

bad FCS with a non-integral number of octets (Alignment

Note20

Error).

The total number of packets received that were longer than 1518 octets (excluding framing bits, but including Jabbers

FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). The total number of packets (including bad packets)

Fr.64bit

received that were 64 octets in length (excluding framing bits but including FCS octets). The total number of packets (including bad packets)

Fr.65-127bit

received that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets)

Fr.128-255bit


Fr,256-511bit


Fr.512-1032bit


Fr.1024-1518

received that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets).

The following notes are referred to the Remote Ethernet Data Performance Snapshot Counters table show above. Note 15 The MulticastPackets value does not include packets directed to the broadcast. Note 16 The MulticastPackets value does not include MAC Control frames, since MAC Control frames are consumed by the interface layer and are not passed to any higher layer protocol. Note 17 The BroadcastPackets value does not include multicast packets. Note 18 The BroadcastPackets value does not include MAC Control frames, since MAC Control frames are consumed by the interface layer and are not passed to any higher layer protocol.


339-1268/06

.

Navigation Page

219

Book Contents


Note 19 The Fragments counter computes both runts (which are normal occurrences due to collisions) and noise hits. Note 20 The Fragments counter in not available for full duplex interfaces Note 21 The jabber definition in this handbook is different than the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These handbook define jabber as the condition where any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150 ms. See Also: Queue Ethernet Data Performance, Local Ethernet Data Performance, 8xFast Ethernet Unit: Ethernet Ports Configuration folder, Queue Ethernet Data Performance

QUEUE ETHERNET DATA PERFORMANCE Path (8xFast Ethernet Unit Menu -> Channel -> Ethernet Config -> Queue Performance). By means of this folder it is possible to enable/disable and read the Queue Ethernet data Performance of the selected port. The Queue Ethernet data Performances are shown as snapshots wich represents a cumulative report of the number of occurrences since the Ethernet interface was last reset, or since the snapshot counts were last manually reset.

To enable the Queue Ethernet performance monitoring * Select the Channel item in the 8xFast Ethernet Unit menu * Click on the Ethernet ports button in order to display the relevant folder. * Select the port previously configured from the ports list field. * Click on the on the Queue Performance button in order to display the queue Performance Monitoring Management folder (see the picture below) for the selected port.

* Define whether the Data Collection counters are enabled or disabled by clicking on the relevant buttons. * Define whether the Automatic counters reset function is enabled or disabled by checking or not the relevant check box respectively.


339-1268/06

.

Navigation Page

220

Book Contents


* Define whether the Automatic refresh function of the current register status is enabled or disabled by checking or not the Continuous check box respectively. Note

Perform the step n.8, only if the “Continuous” check box is enabled, otherwise jump to the step n.9 . * Set the refresh time of the current register status using the relevant scroll list (The range of these value is between from 1s to 3600s, 1s step). * Click on the Apply button to confirm the choices. * Finally, by means of Request push button, a query on the status of the current register can be performed.

The meaning of the fields is explained in the following: n Discards Packets: The number of packets discarded by the queue even though no errors had been detected to prevent their delivery. n Discards Bytes: The number of bytes discarded by the queue even though no errors had been detected to prevent their delivery. See Also: Remote Ethernet Data Performance, Local Ethernet Data Performance, 8xFast Ethernet Unit: Ethernet Ports Configuration folder


339-1268/06

.

Navigation Page

221

Book Contents

CONFIGURATION FILES In this chapter are described the configuration files that can be downloaded to the equipment. The configuration files are text files that may be edited by the user and loaded via the control application into the equipment in order to change some of the equipment default values. Configuration files distributed with the equipment Software Kit are normally meant as template files that should be saved before any changes are introduced.

OSI CONFIGURATION An ASCII configuration file with the parameters of second, third and fourth layers of OSI protocol stack, used for the communication with the Network Management Centre (both on the Ethernet and on the DCCs), can be sent to the Communication and Control Unit. The SDH equipment implement the protocols specified by the following recommendations. On layer 2: n On Ethernet: ISO 8802-3 (CSMA/CD) ISO 8802-2 (LLC) n On DCC: CCITT Q.920/921 (LAPD) On layer 3: n ISO 8473 (CLNP) n ISO 9542 (ESIS) n ISO 10589 (ISIS) On layer 4: n ISO 8073 (OSI Transport) The information contained in this document, and related to the second, third and fourth OSI layers, may be used for a first check of the interoperability at the DCN level between our SDH equipment and equipment by another manufacturer. Such interoperability may be desirable both on ethernet Qinterface (QB3) and on QECC. Note that, with few exceptions (such as the System Id length which should be the same for two systems within the same ISIS domain, or the LAPD frame size which, together with its header and its footer, should be equal or smaller than the Maximum Data packet Size on the other side of the STM-1 connection), it is not necessary that the parameters are configured exactly in the same way. This capability allows interoperability between systems by different manufacturers. However, big discrepancies in the values of some parameters, such as the LAPD, ESIS and ISIS timers, may prevent the communication from working properly. The information related to layer 4 profiling may be useful to try and improve the performance of the communication between a Network Element and its Element Manager.


339-1268/06

.

Navigation Page

Book Contents

MSHXXX - OPERATOR’S HANDBOOK CONFIGURATION FILES

CHANGING THE OSI PROTOCOL PARAMETERS To change the OSI protocol parameters on the equipment it is necessary to prepare a file to be sent with all the settings. All the parameters are included in the ’OSI.ini’ file. The first part of the message contains type information and cannot be modified, the remaining part contains the customisable configuration parameters. Every value in the message is given in hexadecimal format and the parameters length cannot be modified. For parameters with length of two or more bytes, the first byte is the high order byte (ex: dec. 256 on a parameter of two byte length -> 01 00, dec. 2 on a parameter of four byte length -> 00 00 00 02). Range and default values of each message parameter are shown in the following pages. All the values are given in decimal format. In the following a printout is given of ’OSI.ini’, followed by an explanation of the meaning of each parameter, inclusive of its allowed and default values. Anyway, some parameters can also be entered by the Control Application. Such parameters are the following: n For the whole equipment: NSAP address. n For the ethernet circuit (if any): ethernet MAC address. n For each DCC circuit: LAPD side (User or Network) DCC profile identifier This is all the information needed by the OSI stack implementation in equipment to run the default configuration. IMPORTANT Sending a file with wrong parameters can interrupt the communication with the Network Management Centre.

OSI.INI FILE FOR COMMUNICATION AND CONTROL UNIT TYPE C In the following is given an example of OSI.ini file that the user can eventually change and load on the Communication and Control Unit Type C data base. @OSI.ini@ [OSI_CONFIG] PSAP = not_used ; PRESENTATION = not_used ; SSAP = not_used ; SESSION = not_used ; TSAP = not_used ; TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8; NSAP = 20, 4901020304050607080900004402051111110601 ; NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2; ISIS_SYS_ID = 6 , 020511111106 ; ISIS_MAN_AREA_ADDR_0 = 13 , 49010203040506070809000044 ; ISIS_MAN_AREA_ADDR_1 = 0 , ; ISIS_MAN_AREA_ADDR_2 = 0 , ; ISIS_NUM_RA_PREFIXES = 0 ; ISIS_RA_PREFIX_0 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111;


339-1268/06

.

Navigation Page

223

Book Contents


ISIS_RA_PREFIX_2 ISIS_RA_PREFIX_3 ISIS_RA_PREFIX_4 ISIS_RA_PREFIX_5 ISIS_RA_PREFIX_6 ISIS_RA_PREFIX_7 ISIS_RA_PREFIX_8 ISIS_RA_PREFIX_9 CLNS_PARAM = 0 ,

Note(*)

= = = = = = = = 0

0,0,6,490102,20,000205111111; 0,0,6,490102,20,000205111111; 0,0,6,490102,20,000205111111; 0,0,6,490102,20,000205111111; 0,0,6,490102,20,000205111111; 0,0,6,490102,20,000205111111; 0,0,6,490102,20,000205111111; 0,0,6,490102,20,000205111111; , 1 ;

ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,10,1800,30,600,3; MAC_ADDR = 020511111106 ; DCC_PROFILE_0 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_1 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_2 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_3 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_CONFIG_0 = 0 , 0 , 0 ; DCC_CONFIG_1 = 0 , 0 , 0 ; DCC_CONFIG_2 = 0 , 0 , 0 ; DCC_CONFIG_3 = 0 , 0 , 0 ; DCC_CONFIG_4 = 0 , 0 , 0 ; DCC_CONFIG_5 = 0 , 0 , 0 ; DCC_CONFIG_6 = 0 , 0 , 0 ; DCC_CONFIG_7 = 0 , 0 , 0 ; SOH_SLOT_0 = 1,4,5,6,13,11,9,10; SLOT_PORT_0 SLOT_PORT_1 SLOT_PORT_2 SLOT_PORT_3 SLOT_PORT_4 SLOT_PORT_5 SLOT_PORT_6 SLOT_PORT_7

= = = = = = = =

0 0 0 0 0 0 0 0

, , , , , , , ,

0 0 0 0 0 0 0 0

, , , , , , , ,

0 0 0 0 0 0 0 0

; ; ; ; ; ; ; ;

# ~

Note(*)

The “ETH_CONFIG“ values shown in the row are the default values for the ADM-4, ADM-16 and REG-4/16. The “ETH_CONFIG“ default values for the ADM-64 and REG64 are shown in the following: ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,3,1800,10,600,3;

OSID.INI FILE FOR COMMUNICATION AND CONTROL UNIT TYPE D In the following is given an example of OSId.ini file that the user can eventually change and load on the Communication and Control Unit Type D data base. @OSI.ini@ [OSI_CONFIG] PSAP = not_used ; PRESENTATION = not_used ; SSAP = not_used ; SESSION = not_used ; TSAP = not_used ; TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8; NSAP = 20, 4901020304050607080900004402051111110601 ; NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2; ISIS_SYS_ID = 6 , 020511111106 ; ISIS_MAN_AREA_ADDR_0 = 13 , 49010203040506070809000044 ; ISIS_MAN_AREA_ADDR_1 = 0 , ; ISIS_MAN_AREA_ADDR_2 = 0 , ;


339-1268/06

.

Navigation Page

224

Book Contents


ISIS_NUM_RA_PREFIXES = 0 ; ISIS_RA_PREFIX_0 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111; CLNS_PARAM = 0 , 0 , 1 ;

Note(*)

ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,10,1800,30,600,3; MAC_ADDR = 020511111106 ; DCC_PROFILE_0 = 1513,1492,1,7,20,20,0,0,1,3,10,20,150,10,7,10,30,3; DCC_PROFILE_1 = 1513,1492,1,7,20,20,0,0,0,3,10,20,150,10,7,10,30,3; DCC_PROFILE_2 = 1513,1492,1,7,20,20,0,0,1,3,10,20,150,10,7,10,30,3; DCC_PROFILE_3 = 1513,1492,1,7,20,20,0,0,0,3,10,20,150,10,7,10,30,3; DCC_CONFIG_0 = 0 , 0 , 0 ; DCC_CONFIG_1 = 0 , 0 , 0 ; DCC_CONFIG_2 = 0 , 0 , 0 ; DCC_CONFIG_3 = 0 , 0 , 0 ; DCC_CONFIG_4 = 0 , 0 , 0 ; DCC_CONFIG_5 = 0 , 0 , 0 ; DCC_CONFIG_6 = 0 , 0 , 0 ; DCC_CONFIG_7 = 0 , 0 , 0 ; DCC_CONFIG_8 = 0,0,0; DCC_CONFIG_9 = 0,0,0; DCC_CONFIG_10 = 0,0,0; DCC_CONFIG_11 = 0,0,0; DCC_CONFIG_12 = 0,0,0; DCC_CONFIG_13 = 0,0,0; DCC_CONFIG_14 = 0,0,0; DCC_CONFIG_15 = 0,0,0; DCC_CONFIG_16 = 0,0,0; DCC_CONFIG_17 = 0,0,0; DCC_CONFIG_18 = 0,0,0; DCC_CONFIG_19 = 0,0,0; DCC_CONFIG_20 = 0,0,0; DCC_CONFIG_21 = 0,0,0; DCC_CONFIG_22 = 0,0,0; DCC_CONFIG_23 = 0,0,0; DCC_CONFIG_24 = 0,0,0; DCC_CONFIG_25 = 0,0,0; DCC_CONFIG_26 = 0,0,0; DCC_CONFIG_27 = 0,0,0; SLOT_PORT_0 = 0,0,0; SLOT_PORT_1 = 0,0,0; SLOT_PORT_2 = 0,0,0; SLOT_PORT_3 = 0,0,0 ; SLOT_PORT_4 = 0,0,0 ; SLOT_PORT_5 = 0,0,0 ; SLOT_PORT_6 = 0,0,0 ; SLOT_PORT_7 = 0,0,0 ; SLOT_PORT_8 = 0,0,0; SLOT_PORT_9 = 0,0,0; SLOT_PORT_10 = 0,0,0; SLOT_PORT_11 = 0,0,0; SLOT_PORT_12 = 0,0,0; SLOT_PORT_13 = 0,0,0; SLOT_PORT_14 = 0,0,0; SLOT_PORT_15 = 0,0,0; SLOT_PORT_16 = 0,0,0;


339-1268/06

.

Navigation Page

225

Book Contents


SLOT_PORT_17 = 0,0,0; SLOT_PORT_18 = 0,0,0; SLOT_PORT_19 = 0,0,0; SLOT_PORT_20 = 0,0,0; SLOT_PORT_21 = 0,0,0; SLOT_PORT_22 = 0,0,0; SLOT_PORT_23 = 0,0,0; SLOT_PORT_24 = 0,0,0; SLOT_PORT_25 = 0,0,0; SLOT_PORT_26 = 0,0,0; SLOT_PORT_27 = 0,0,0; #Note(*) The “ETH_CONFIG“ values shown in the row are the default values for the ADM-4, ADM-16 and REG-4/16. The “ETH_CONFIG“ default values for the ADM-64 and REG-

64 are shown in the following: ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,3,1800,10,600,3;

PARAMETERS OF OSI.INI FILE Transport Layer TRANSPORT: The parameters associated to this entry are: n lay4_init_win_size: Initial window size. The initial number of unacknowledged TPDUs that can be outstanding on a connection. Transport will automatically adjust the window size up to the Credit value. Range is [1-255]. Default: 2. n lay4_credit: Target window size. The expected window size, that is a target value for the maximum number of unacknowledged TPDUs that can be outstanding on a connection. Range is [1-255]. Default: 8. n lay4_max_TPDU_size: Max TPDU size (in octets). The maximum size of a TPDU. Range is {0,1,2,3} (0=128, 1=256, 2=512, 3=1024). Default: 3. n inactivity: Inactivity time (in tenths of second). The amount of time Transport maintains a layer 4 connection on which no data is being transferred before it terminates the connection. Range is [1-65535]. Default: 3000 (300 seconds). n initial_retrans: Initial Retransmit time (in tenths of second). The amount of time Transport initially waits without receiving a TPDUs acknowledgement before it retransmits the TPDU. Transport automatically adjusts this parameter's value individually for each connection, based on network performance. Range is [-]. Default: 120 (12 seconds). n lower_retrans: Lower Retransmit time bound (in tenths of second). Lower bound for the retransmit timer. Range is [1-].


339-1268/06

.

Navigation Page

226

Book Contents


Default: 120 (12 seconds). n upper_retrans: Initial Retransmit time (in tenths of second). Upper bound for the retransmit timer. Range is [-65535]. Default: 120 (12 seconds).


339-1268/06

.

Navigation Page

227

Book Contents


n window_tmr: Window timer. The period of inactivity that can occur before Transport sends a hello packet to the peer entity with which a connection is established (in tenths of second). Must be bigger than the Local Acknowledgement delay (note that the Local Acknowledgement delay is expressed in milliseconds). Range is [1-65535]. Default: 750 (75 seconds). n local_ack: Local acknowledgement delay. The maximum amount of time Transport can delay acknowledging a TPDU it receives (in milliseconds). Must be lower than the Window timer (note that the Window timer is expressed in tenths of seconds). Range is [1-65535]. Default: 1 (0.001 seconds). n local_flow_ctrl: Local flow control. Available resources check interval (in milliseconds). If Transport has no receive credit available, it checks the available resources each time the interval specified by this parameter has passed, until credit becomes available. Range is [1-65535]. Default: 100 (0.1 seconds). n retrans_cnt: Number of retransmission. Maximum number of times which the local transport entity will continue to transmit a TPDU that requires acknowledgement. Range is [1-255]. Default: 8. TRANSPORT = 2,8,3,3000,120,20,120,750,1,100,8;

Network Layer NSAP: parameters associated to this entry are: n nsap_len: length of NSAP address, expressed in bytes. n nsap_addr[20]: field containing the NSAP (Network Service Access Point) identifier or network address of the equipment. NSAP = 20, 4901020304050607080900004402051111110601 ;

NETWORK: parameters associated to this entry are: n lev1_buffer_size: Level 1 Buffer Size. Default originating level 1 LSP Buffer Size. Range is [512-1492]. Default: 1492. n lev2_buffer_size: Level 2 Buffer Size. Default originating level 2 LSP Buffer Size. Range is [512-1492]. Default: 1492. n DR_isis_hello_tmr: Default dr ISIS hello timer. Default Designated Router ISIS hello timer. Range is [1-65535]. Default: 1.


339-1268/06

.

Navigation Page

228

Book Contents


n part_repair_flag: ISO 10589 Partition Repair Supported (TRUE/FALSE). Default: FALSE. n CLNP_lifetime: CLNP lifetime. Lifetime of the ISO 8473 Data Packets generated by this system. The lifetime is expressed in units of 500 milliseconds. Range is [1-255]. Default: 64 (32 seconds). n max_path_split: Maximum Path Split. Default maximum number of equal cost paths which are recorded by the decision process. Range is [1-2]. Default: 2. n max_area_addrs: Maximum Area Addresses. Default maximum number of Area Addresses handled by the router. The only use of this parameter is that, within an area, all the level 1 Intermediate Systems must have the same value for it (note that the parameter value is output within the ISIS PDUs). Range is [1-12]. Default: 3. n min_LSP_tx_interval: Minimum LSP Transmission Interval. Default minimum LSP Transmission interval, in seconds. Range is [1-65535]. Default: 5. n max_LSP_gen_interval: Maximum LSP Generation interval. Default maximum LSP generation interval, in seconds. Range is [1-65535]. Default: 900. n min_LSP_gen_interval: Minimum LSP Generation interval. Default minimum LSP generation interval, in seconds. Range is [1-65535]. Default: 30. n min_broadcast_LSP_tx: Minimum broadcast LSP TX interval. Default minimum broadcast LSP transmission interval, in seconds. Range is [1-65535]. Default: 33. n CSNP_interval: Complete SNP interval. Default complete Sequence Numbering PDU interval, in seconds. Range is [1-600]. Default: 10. PSNP_interval: Partial SNP interval. Default partial Sequence Numbering PDU interval, in seconds.


339-1268/06

.

Navigation Page

229

Book Contents


Range is [1-65535]. Default: 2. n ES_poll_rate: ES polling rate. Default End System Hello rate. Range is [1-65535]. Default: 50. n wait_time: Default Waiting Time. Range is [1-65535]. Default: 60. n max_virt_adjs: Maximum Number of Virtual Adjacencies. Default maximum number of virtual adjacencies (virtual adjacencies are used for Partition Repair). Range is [0-31]. Default: 2. NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2;

ISIS_SYS_ID: parameters associated to this entry are: n sys_id_len: system identifier length, expressed in bytes n isis_sys_id[6]: the contents of the system ID field are taken from the NSAP address. ISIS_SYS_ID = 6 , 020511111106 ;

ISIS_MAN_AREA_ADDR_: parameters associated to this entry are: n len n addr[20] Entry ISIS_MAN_AREA_ADDR_0 contains the area address (which is taken from the first part of the NSAP) of the router. Entry ISIS_MAN_AREA_ADDR_1 and entry ISIS_MAN_AREA_ADDR_2 contain two area addresses that the router recognises as synonymous of its own area address. Each area address is preceded by its length. Default: no synonymous, len = 0. ISIS_MAN_AREA_ADDR_0 = 13 , 49010203040506070809000044 ; ISIS_MAN_AREA_ADDR_1 = 0 , ; ISIS_MAN_AREA_ADDR_2 = 0 , ;

ISIS_NUM_RA_PREFIXES: parameter associated to this entry is: n num_RA_prefixes: Number of prefixes. Number of prefixes configured on the equipment. ISIS_NUM_RA_PREFIXES = 0 ; ISIS_RA_PREFIX_: parameters associated to this entry are:


339-1268/06

.

Navigation Page

230

Book Contents


n RAP_id: An integer value which uniquely identifies the Reachable Address Prefix within the Network Element. Value 0 is used when the RAP with this identifier is not defined. Default: 0 (prefix undefined). n RAP_type: Type of the RAP. 0 (BDC, for Broadcast RAP), 1 (PP, for Point to Point RAP), 2 (BDC_MA, for Broadcast MESA), (PP_MSA, for Point to Point MESA) (MESA, Manual End System Adjacencies). n RAP_len: Prefix length. If Prefix Type is 0 or 1, range is [0-40]. Note that the value 0 is allowed, and allows to redirect on a given interface all the packets which may not be routed otherwise. If Prefix Type is 2 or 3, the range is [-(20/SystemIdLength)], identifying the number of End Systems manually connected on the selected unit. n RAP_addr[20]: RAP data. If Prefix Type is 0 or 1, this field contains the Reachable Address Prefix. If Prefix Type is 2 or 3, this field contains prefix_length System Identifier of the End Systems which may be reached through this adjacency. Note that only the first prefix_length semioctets, if Prefix Type is 0 or 1, or the first prefix_length*SystemIdLength bytes, if Prefix Type is 2 or 3, they are meaningful. n RAP_metric: Prefix default metric. Default metric value for the reachable address prefix, or the Manual End System Adjacency. This value is used for the computation of the shortest path. Range is [1-128]. Default: 20. n RAP_cid[6]: If the prefix type is PP, or PP_MA, this field will contain the DCC channel id of the DCC channel carrying the point to point circuit to which the RAP, or MESA, is associated, on two bytes, and the remaining four bytes will be meaningless. If the prefix type is BDC, or BCD_MA, this field will contain the Ethernet MAC address, on 6 bytes, to which the packets addressed to the configured prefix, or Manual End Systems must be delivered. ISIS_RA_PREFIX_0 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111;


339-1268/06

.

Navigation Page

231

Book Contents


CLNS_PARAM: parameters associated to this entry are: n clns_options: CLNS Options. Bit mask for the CLNS options. Considering that bit 0 is the least significant bit, and bit 7 is the most significant bit, the meaning of the bits is the following: bit 0 -> Complete source routing supported bit 1 -> Partial source routing supported bit 2 -> Set E/R flags in originated data NPDUs bit 3 -> US GOSIP V1 Unclassified Security supported bit 4 -> US GOSIP Vd21 Unclassified Security supported Default: 0 (no options supported). n clnp_chksum_flag: CLNP checksum flag. Enabling flag for the checksum of the ISO 8473 data packets. Allowed values are TRUE, FALSE. Default: FALSE. n router_type: Router type. May take one of the following values: 1 (LEVEL 1 ROUTER): level 1 router (local router), as defined in the ISIS protocol (ISO 10589). 3 (LEVEL 2 ROUTER): level 2 router (area router), as defined in the ISIS protocol. Default: 1 (LEVEL 1 ROUTER). CLNS_PARAM = 0 , 0 , 1 ; ETH_CONFIG: parameters associated to this entry are: n ISO9542_opts: ISO 9542 (ESIS) functions supported. bit 1 = configuration bit 2 = redirect bit 3 = notification bit 4 = checksum Default: configuration | redirect | notification. n ext_domain: External domain circuit status. Default external domain circuit status. Range is [TRUE,FALSE]. Default: FALSE. n l2_only: Level 2 only circuit status. Level 2 only status for the Ethernet circuit. If the level 2 status is TRUE, the system will only act as a level 2 router, not as a level 1 router. Range is [TRUE,FALSE]. Default: FALSE. n gateway_enable: Managed Object operational state. This field may take the following values: 0 - circuit not enabled 1 - circuit enabled.


339-1268/06

.

Navigation Page

232

Book Contents


n ETH_max_size: Max Data Packet Size. Maximum size of the data packet output on this circuit. Range is [500-1500]. Default: 1492. n ETH_lev1metric: Default level 1 circuit metric. Value of the default metric on this circuit, for level 1 routing. Range is [1-63]. Default: 20. n ETH_lev2metric: Default level 2 circuit metric. Value of the default metric on this circuit, for level 2 routing. Range is [1-63]. Default: 20. n ETH_lev1pri: Default level 1 priority. Priority to become the level 1 designated router. The highest the priority, the highest the chances of this system to become the designated router. Range is [1-127]. Default: 64. n ETH_lev2pri: Default level 2 priority. Priority to become the level 1 designated router. The highest the priority, the highest the chances of this system to become the designated router. Range is [1-127]. Default: 64. n ISIS_hello_tmr: ISIS Hello Timer default. Timer defining the default interval of generation of the ISIS Hello PDUs, in seconds. Range is [1-65535]. Default: 10. (ADM-4), (ADM-16), (REG-4/16) Default: 3. (ADM-64), (REG-64) n ISO9542_redirect_tmr: ISO 9542 redirect timer. Default ISO 9542 redirect timer, in seconds. Range is [1-65535]. Default: 1800. n ISO9542_IS_conf_tmr: IS configuration timer. Default ISO 9542 IS configuration timer, in seconds. Range is [1-21845]. Default: 30. (ADM-4), (ADM-16), (REG-4/16) Default: 10. (ADM-64), (REG-64)


339-1268/06

.

Navigation Page

233

Book Contents


n ISO9542_ES_conf_tmr: ES configuration timer. Default ISO 9542 Suggested ES configuration timer, in seconds. Range is [1-65535]. Default is 600. n ETH_Hold: Holding time multiplier. Default ISO 9542 Holding time multiplier. Range is [2-63]. Default: 3. ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,10,1800,30,600,3; (ADM-4), (ADM-16), (REG-4/16) ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,3,1800,10,600,3; (ADM-64), (REG-64)

MAC_ADDR: parameter associated to this entry is: n MAC_addr[6]: Ethernet MAC address, six-bytes field used by the equipment as the physical address on the LAN. MAC_ADDR = 020511111106 ;

DCC_PROFILE_: parameters associated to this entry are: n n201: Frame Size. Maximum frame length allowed on LAPD, in bytes. Range is [0-1513]. Default: 1513. n maxsize: Max Packet Size. Maximum size of data packets generated by layer 3 on this circuit. Range is [500-1500]. Default: 1492. n lapd_mod: Modulo. LAPD modulo of operation; must be either 8 or 128. Default: 1 (128). n win_size: Window Size. Range is [0-7], if modulo 8, and [0-127], if modulo 128. Default: 7. n lev1metric: Default level 1 circuit metrics. Range is [1-63]. Default: 20. n lev2metric: Default level 2 circuit metrics. Range is [1-63]. Default: 20. n unused


339-1268/06

.

Navigation Page

234

Book Contents


n ext_domain: External domain flag. Flag saying whether the external domain attribute is set for this DCC channel. Range is [TRUE, FALSE]. Default: FALSE. n dcc_r_m: DCCR/DCCM selector. A flag saying whether DCCR or DCCM should be used for this profile. Range is [0(DCCR),1(DCCM)]. n retrans_cnt: Retransmission count. Limit is MAX_CNTR (1024). Default: 3. n cong_tmr: Congestion Timer. Limit is MAX_TIMER (1024). Default: 10 tenths of second, that is, one second. n retrans_tmr: Retransmit Timer. LAPD T200 timer; the value is expressed in tenths of second. The maximum allowed value for this timer is MAX_TIMER (1024); it must be smaller than T203 timer. Default: 20. n idle_tmr: Idle Timer. LAPD T203 timer; the value is expressed in tenths of second. The maximum allowed value for this timer is MAX_TIMER (1024); it must be bigger than T200 timer. Default: 200 tenths of second, that is 20 seconds. n isis_hello_tmr: ISIS Hello Timer default, in seconds. Range is [1-65535]. Default: 15. n ISO_9542_opts: ISO 9542 (ESIS) functions supported. bit 1 = configuration bit 2 = redirect bit 3 = notification bit 4 = checksum Default: configuration | redirect | notification. n ish_tmr: IS configuration timer. Default ISO 9542 IS configuration timer, in seconds. Range is [1-21845]. Default: 300. n esc_tmr: ES configuration timer. Default ISO 9542 Suggested ES configuration timer, in seconds. Range is [1-65535]. Default is 600.


339-1268/06

.

Navigation Page

235

Book Contents


n Hold: Holding time multiplier. Default ISO 9542 Holding time multiplier. n Range is [2-63]. n Default: 3. DCC_PROFILE_0 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_1 = 1513,1492,1,7,20,20,0,0,0,3,10,20, 200,15,7,300,600,3; DCC_PROFILE_2 = 1513,1492,1,7,20,20,0,0,1,3,10,20, 200,15,7,300,600,3; DCC_PROFILE_3 = 1513,1492,1,7,20,20,0,0,1,3,10,20, 200,15,7,300,600,3;

DCC_CONFIG_: parameters associated to this entry are: n profile: A number which uniquely identifies the profile which contains the layer 2 and layer 3 configuration for this DCC. n user_network: Management parameter for LAPD. This field may assume values in the range [USER,NETWORK]. n enabled: Operational state of the interface. Flag saying whether the DCC is enabled. Range is [TRUE,FALSE]. DCC_CONFIG_0 = 0 , 0 , 0 ; DCC_CONFIG_1 = 0 , 0 , 0 ; DCC_CONFIG_2 = 0 , 0 , 0 ; DCC_CONFIG_3 = 0 , 0 , 0 ; DCC_CONFIG_4 = 0 , 0 , 0 ; DCC_CONFIG_5 = 0 , 0 , 0 ; DCC_CONFIG_6 = 0 , 0 , 0 ; DCC_CONFIG_7 = 0 , 0 , 0 ;

SOH_SLOT_: parameter associated to this entry is: n soh_slots[8]: The controller is able to manage 8 OverHead buses at the same time. DCC1 <-> slot 1 DCC2 <-> slot 4 DCC3 <-> slot 5 DCC4 <-> slot 6 DCC5 <-> slot 13 DCC6 <-> slot 11 DCC7 <-> slot 9 DCC8 <-> slot 10 SOH_SLOT_0 = 1,4,5,6,13,11,9,10;


339-1268/06

.

Navigation Page

236

Book Contents


SLOT_PORT: parameters associated to this entry are: n slot: slot number. n port: port number. n dcc: dcc number associated to slot and port. SLOT_PORT_0 = 0 , 0 , 0 ; SLOT_PORT_1 = 0 , 0 , 0 ; SLOT_PORT_2 = 0 , 0 , 0 ; SLOT_PORT_3 = 0 , 0 , 0 ; SLOT_PORT_4 = 0 , 0 , 0 ; SLOT_PORT_5 = 0 , 0 , 0 ; SLOT_PORT_6 = 0 , 0 , 0 ; SLOT_PORT_7 = 0 , 0 , 0 ;

Operative Indications How to modify NSAP * Look for the row identified by the entry NSAP. * Modify nsap_length and nsap_value. |

|

NSAP = 20,4901020304050607080900004402051111110601 ;

How to enable/disable Ethernet * Look for the row identified by the entry ETH_CONFIG. * To enable Ethernet write 1 in the fourth parameter of the row, write 0 to disable. For example in | ETH_CONFIG = 7,0,0,1,1492,20,20,64,64,10,1800,30,600,3;

Ethernet is enabled.

How to modify MAC ADDRESS * Look for the row identified by the entry MAC_ADDR. * Modify the MAC_addr value. | MAC_ADDR = 020511111106 ;

How to enable/disable a DCC The involved entries have the "DCC_CONFIG_" prefix; the number of such entries is 8, referred from 0 to 7. The parameter that indicates if the dcc is enabled (1) or not (0) is the third: | DCC_CONFIG_0 = 0 , 0 , 1 ;

To modify the state (enabled/disabled) of the DCCi: * Look for the row identified by the entry DCC_CONFIG_i.


339-1268/06

.

Navigation Page

237

Book Contents


* Modify the value of the third parameter writing: 0 to disable the dcc 1 to enable the dcc

How to modify the profile of a DCC There are four profiles, referred from 0 to 3: every dcc can use one of these profiles. Profiles are the entries DCC_PROFILE_0.DCC_PROFILE_3. In the entries with prefix "DCC_CONFIG_" the parameter that indicates the profile used is the first. | DCC_CONFIG_0 = 0 , 0 , 1 ;

To modify the profile of the DCCi: * Look for the row identified by the entry DCC_CONFIG_i. * Modify the value of the first parameter writing the number of the chosen profile.


339-1268/06

.

Navigation Page

238

Book Contents


How to modify the LAPD side (USER/NETWORK) of a DCC Every dcc may be USER or NETWORK. In the entries with prefix "DCC_CONFIG_" the parameter that indicates the LAPD side of the dcc is the second (0 for USER, 1 for NETWORK). | DCC_CONFIG_0 = 0 , 0 , 1 ;

To modify the LAPD side of the DCCi: * Look for the row identified by the entry DCC_CONFIG_i. * Modify the value of the second parameter writing: 0 for USER 1 for NETWORK.

How to modify the type (DCCR/DCCM) of a DCC Every dcc uses a profile; the ninth parameter of the profile indicates the type of the dcc (0 for CCR, 1 for DCCM). | DCC_PROFILE_0 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;

To modify the type in the DCC_PROFILE_i: * Look for the row identified by the entry DCC_PROFILE_i. * Modify the value of the ninth parameter writing: 0 for DCCR 1 for DCCM

How to modify router_type * Look for the row identified by the entry CLNS_PARAM. * To enable local router write 1 in the third parameter of the row, to enable area router write 3 in the third parameter of the row; for example in: | CLNS_PARAM = 0 , 0 , 1 ;

local router is enabled.

Examples Management of Static Routing Information Static Routing information may be of two different types, as described by the IS-IS protocol (ISO 10589): RAP:s (Reachable Address Prefixes) and MESA:s (Manual End System Adjacencies). Note that Manual End System Adjacencies are not supported by all the equipment and releases supporting OSI management. Reachable address prefixes may be used, on an equipment which is configured as a level 2 router, to set up static routes, both on point to point and on broadcast circuits, based on a prefix of the destination NSAP contained in each data packet. Note that the systems reachable by means of a RAP must be in a different area from any other area in the network, where an area is a fully connected partition of the network, in which the area address part of the NSAP is the same for all the systems, and different from the area address of any system in the network outside such partition.


339-1268/06

.

Navigation Page

239

Book Contents


Manual End System Adjacencies may be used to set-up a static route from a SDH NE (which is always an Intermediate System) to up to [20/SystemIdLength] (3, if SystemIdLength is 6, as usual) End Systems belonging to the same area, for which it is not possible (or desirable) to establish a dynamic adjacency by means of ES-IS protocol (ISO 9542). For example, it may be that such End Systems don’t implement IS-IS on the considered circuit. Manual End System Adjacencies have the advantage that it is not necessary to use a different area for each configured route. On the other hand, they have the disadvantage that each route may give access to [20/SystemIdLength] (typically 3) End Systems, at most, while a single RAP may give access to a virtual unlimited number of systems. For examples. If there were a STM-N ring containing 20 elements, it would be possible to reach all the elements from the gateway by configuring just one rap, but 7 MESA:s would be needed. In the following some examples of stating routing configuration necessary for the communication between two equipment are given.

Configuration of Static Routing on a DCC Link

Eqt. A

DCC

Eqt. B

Fig. 7 Configuration between equipment A and B using DCC

Example 1 (RAP, different areas) DCC equipment A ---------------------- equipment B equipment A NSAP: 4901020304050607080900004402052179710601 equipment B NSAP: 4955555555555555555555555502051010100601


339-1268/06

.

Navigation Page

240

Book Contents


equipment A configuration file

OSIA.ini ********************************** @OSI.ini@ [OSI_CONFIG] PSAP = not_used ; PRESENTATION = not_used ; SSAP = not_used ; SESSION = not_used ; TSAP = not_used ; TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8; NSAP = 20, 4901020304050607080900004402052179710601 ; NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2; ISIS_SYS_ID = 6 , 020521797106 ; ISIS_MAN_AREA_ADDR_0 = 13 , 49010203040506070809000044 ; ISIS_MAN_AREA_ADDR_1 = 0 , ; ISIS_MAN_AREA_ADDR_2 = 0 , ; ISIS_NUM_RA_PREFIXES = 1 ; ISIS_RA_PREFIX_0 = 1,1,20,49555555555555555555,20,000600000000; ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111; CLNS_PARAM = 0 , 0 , 3 ; ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,3,1800,10,600,3; MAC_ADDR = 020521797106 ; DCC_PROFILE_0 = 1513,1492,1,7,20,20,0,1,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_1 = 1513,1492,1,7,20,20,0,0,0,3,10,20,200,15,7,300,600,3; DCC_PROFILE_2 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_3 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_CONFIG_0 = 0 , 0 , 0 ; DCC_CONFIG_1 = 0 , 0 , 0 ; DCC_CONFIG_2 = 0 , 0 , 0 ; DCC_CONFIG_3 = 0 , 0 , 0 ; DCC_CONFIG_4 = 0 , 0 , 0 ; DCC_CONFIG_5 = 0 , 0 , 0 ; DCC_CONFIG_6 = 0 , 1 , 1 ; DCC_CONFIG_7 = 0 , 0 , 0 ; # ~ **********************************


339-1268/06

.

Navigation Page

241

Book Contents


File notes NSAP = 20, 4901020304050607080900004402052179710601 ISIS_NUM_RA_PREFIXES = 1 (number of configured prefixes) ISIS_RA_PREFIX_0: field RAP_id=1 field RAP_type=1 (point to point circuit) field RAP_len=20 field RAP_addr=49555555555555555555 field RAP_metric=20 field RAP_cid=00060000000 (seventh DCC) this prefix supplies to equipment A the information necessary to connect to equipment B (equipment B NSAP is NSAP = 20, 4955555555555555555555555502051010100601) CLNS_PARAM: field router_type=3 (area router) DCC_PROFILE_0 = 1513,1492,1,7,20,20,0,1,1,3,10,20,200,15,7,300,600,3 (eighth field ext_domain=1) DCC_CONFIG_6 = 0,1,1 (seventh DCC, profile 0, network, enable)


339-1268/06

.

Navigation Page

242

Book Contents


equipment B configuration file

OSIB.ini ********************************** @OSI.ini@ [OSI_CONFIG] PSAP = not_used ; PRESENTATION = not_used ; SSAP = not_used ; SESSION = not_used ; TSAP = not_used ; TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8; NSAP = 20, 4955555555555555555555555502051010100601 ; NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2; ISIS_SYS_ID = 6 , 020510101006 ; ISIS_MAN_AREA_ADDR_0 = 13 , 49555555555555555555555555 ; ISIS_MAN_AREA_ADDR_1 = 0 , ; ISIS_MAN_AREA_ADDR_2 = 0 , ; ISIS_NUM_RA_PREFIXES = 1 ; ISIS_RA_PREFIX_0 = 1,1,20,49010203040506070809,20,000400000000; ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111; CLNS_PARAM = 0 , 0 , 3 ; ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,3,1800,10,600,3; MAC_ADDR = 020510101006 ; DCC_PROFILE_0 = 1513,1492,1,7,20,20,0,1,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_1 = 1513,1492,1,7,20,20,0,0,0,3,10,20,150,15,7,300,600,3; DCC_PROFILE_2 = 1513,1492,1,7,20,20,0,0,1,3,10,20,150,15,7,300,600,3; DCC_PROFILE_3 = 1513,1492,1,7,20,20,0,0,1,3,10,20,150,15,7,300,600,3; DCC_CONFIG_0 = 0 , 0 , 0 ; DCC_CONFIG_1 = 0 , 0 , 0 ; DCC_CONFIG_2 = 0 , 0 , 0 ; DCC_CONFIG_3 = 0 , 0 , 0 ; DCC_CONFIG_4 = 0 , 0 , 1 ; DCC_CONFIG_5 = 0 , 0 , 0 ; DCC_CONFIG_6 = 0 , 0 , 0 ; DCC_CONFIG_7 = 0 , 0 , 0 ; # ~ **********************************


339-1268/06

.

Navigation Page

243

Book Contents


File notes NSAP = 20, 4955555555555555555555555502051010100601 ISIS_NUM_RA_PREFIXES = 1 (number of configured prefixes) ISIS_RA_PREFIX_0: field RAP_id=1 field RAP_type=1 (point to point circuit) field RAP_len=20 field RAP_addr=49010203040506070809 field RAP_metric=20 field RAP_cid=000400000000 (fifth DCC) this prefix supplies to the equipment B the information necessary to connect to the equipment A (the equipment A NSAP is: NSAP = 20, 4901020304050607080900004402052179710601) CLNS_PARAM: field router_type=3 (area router) DCC_PROFILE_0 (eighth field ext_domain=1)

=

1513,1492,1,7,20,20,0,1,1,3,10,20,200,15,7,300,600,3

DCC_CONFIG_4 = 0,0,1 (fifth DCC, profile 0, user, enable)

Configuration of Static Routing on an Ethernet Link LAN

ADM-64

ADM-64

Fig. 8 Connection between the equipment A and B using Ethernet

Example 2 (RAP, different areas) Ethernet equipment A ---------------------- equipment B equipment A NSAP: 4901020304050607080900004402052179710601 equipment B NSAP: 4955555555555555555555555502051010100601


339-1268/06

.

Navigation Page

244

Book Contents



OSIAMEt.ini ********************************** @OSI.ini@ [OSI_CONFIG] PSAP = not_used ; PRESENTATION = not_used ; SSAP = not_used ; SESSION = not_used ; TSAP = not_used ; TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8; NSAP = 20, 4901020304050607080900004402052179710601 ; NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2; ISIS_SYS_ID = 6 , 020521797106 ; ISIS_MAN_AREA_ADDR_0 = 13 , 49010203040506070809000044 ; ISIS_MAN_AREA_ADDR_1 = 0 , ; ISIS_MAN_AREA_ADDR_2 = 0 , ; ISIS_NUM_RA_PREFIXES = 1 ; ISIS_RA_PREFIX_0 = 1,0,20,49555555555555555555,20,020510101006; ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111; CLNS_PARAM = 0 , 0 , 3 ; ETH_CONFIG = 7,1,0,1,1492,20,20,64,64,3,1800,10,600,3; MAC_ADDR = 020521797106 ; DCC_PROFILE_0 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_1 = 1513,1492,1,7,20,20,0,0,0,3,10,20,200,15,7,300,600,3; DCC_PROFILE_2 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_3 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_CONFIG_0 = 0 , 0 , 0 ; DCC_CONFIG_1 = 0 , 0 , 0 ; DCC_CONFIG_2 = 0 , 0 , 0 ; DCC_CONFIG_3 = 0 , 0 , 0 ; DCC_CONFIG_4 = 0 , 0 , 0 ; DCC_CONFIG_5 = 0 , 0 , 0 ; DCC_CONFIG_6 = 0 , 0 , 0 ; DCC_CONFIG_7 = 0 , 0 , 0 ; # ~**********************************

File notes


339-1268/06

.

Navigation Page

245

Book Contents


NSAP = 20, 4901020304050607080900004402052179710601 ISIS_NUM_RA_PREFIXES = 1 (number of configured prefixes) ISIS_RA_PREFIX_0: field RAP_id=1 field RAP_type=0 (broadcast circuit) field RAP_len=20 field RAP_addr=49555555555555555555 field RAP_metric=20 field RAP_cid=020510101006 (MAC) this prefix supplies to equipment A the information necessary to connect to equipment B (equipment B NSAP is: NSAP = 20, 4955555555555555555555555502051010100601) CLNS_PARAM: field router_type=3 (area router) ETH_CONFIG = 7,1,0,1,1492,20,20,64,64,10,1800,30,600,3 (second field ext_domain=1, fourth field gateway_enable=1, Ethernet enabled)


339-1268/06

.

Navigation Page

246

Book Contents



OSIBMEt.ini ********************************** @OSI.ini@ [OSI_CONFIG] PSAP = not_used ; PRESENTATION = not_used ; SSAP = not_used ; SESSION = not_used ; TSAP = not_used ; TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8; NSAP = 20, 4955555555555555555555555502051010100601 ; NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2; ISIS_SYS_ID = 6 , 020510101006 ; ISIS_MAN_AREA_ADDR_0 = 13 , 49555555555555555555555555 ; ISIS_MAN_AREA_ADDR_1 = 0 , ; ISIS_MAN_AREA_ADDR_2 = 0 , ; ISIS_NUM_RA_PREFIXES = 1 ; ISIS_RA_PREFIX_0 = 1,0,20,49010203040506070809,20,020521797106; ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111; CLNS_PARAM = 0 , 0 , 3 ; ETH_CONFIG = 7,1,0,1,1492,20,20,64,64,3,1800,10,600,3; MAC_ADDR = 020510101006 ; DCC_PROFILE_0 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_1 = 1513,1492,1,7,20,20,0,0,0,3,10,20,200,15,7,300,600,3; DCC_PROFILE_2 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_3 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_CONFIG_0 = 0 , 0 , 0 ; DCC_CONFIG_1 = 0 , 0 , 0 ; DCC_CONFIG_2 = 0 , 0 , 0 ; DCC_CONFIG_3 = 0 , 0 , 0 ; DCC_CONFIG_4 = 0 , 0 , 0 ; DCC_CONFIG_5 = 0 , 0 , 0 ; DCC_CONFIG_6 = 0 , 0 , 0 ; DCC_CONFIG_7 = 0 , 0 , 0 ; # ~**********************************

File notes


339-1268/06

.

Navigation Page

247

Book Contents


NSAP = 20, 4955555555555555555555555502051010100601 ISIS_NUM_RA_PREFIXES = 1 (number of configured prefixes) ISIS_RA_PREFIX_0: field RAP_id=1 field RAP_type=0 (broadcast circuit) field RAP_len=20 field RAP_addr=49010203040506070809 field RAP_metric=20 field RAP_cid=020521797106 (MAC) this prefix supplies to equipment B the information necessary to connect to equipment A (equipment A NSAP is: NSAP = 20, 4901020304050607080900004402052179710601) CLNS_PARAM: field router_type=3 (area router) ETH_CONFIG = 7,1,0,1,1492,20,20,64,64,110,1800,30,600,3 (second field ext_domain=1, fourth field gateway_enable=1, Ethernet enabled)

Example 3 (MESA, different areas) DCC equipmentA ---------------------- equipment B equipmentA NSAP: 4901020304050607080900004402052179710601 equipment B NSAP: 4901020304050607080900004402054444440601


339-1268/06

.

Navigation Page

248

Book Contents



OSIAM.ini ********************************** @OSI.ini@ [OSI_CONFIG] PSAP = not_used ; PRESENTATION = not_used ; SSAP = not_used ; SESSION = not_used ; TSAP = not_used ; TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8; NSAP = 20, 4901020304050607080900004402052179710601 ; NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2; ISIS_SYS_ID = 6 , 020521797106 ; ISIS_MAN_AREA_ADDR_0 = 13 , 49010203040506070809000044 ; ISIS_MAN_AREA_ADDR_1 = 0 , ; ISIS_MAN_AREA_ADDR_2 = 0 , ; ISIS_NUM_RA_PREFIXES = 1 ; ISIS_RA_PREFIX_0 = 1, 3, 1, 020544444406, 20, 000600000000; ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111; CLNS_PARAM = 0 , 0 , 1 ; ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,3,1800,10,600,3; MAC_ADDR = 020521797106 ; DCC_PROFILE_0 = 1513,1492,1,7,20,20,0,1,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_1 = 1513,1492,1,7,20,20,0,0,0,3,10,20,200,15,7,300,600,3; DCC_PROFILE_2 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_3 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_CONFIG_0 = 0 , 0 , 0 ; DCC_CONFIG_1 = 0 , 0 , 0 ; DCC_CONFIG_2 = 0 , 0 , 0 ; DCC_CONFIG_3 = 0 , 0 , 0 ; DCC_CONFIG_4 = 0 , 0 , 0 ; DCC_CONFIG_5 = 0 , 0 , 0 ; DCC_CONFIG_6 = 0 , 0 , 0 ; DCC_CONFIG_7 = 0 , 0 , 0 ; # ~**********************************

File notes


339-1268/06

.

Navigation Page

249

Book Contents


NSAP = 20, 4901020304050607080900004402052179710601 ISIS_NUM_RA_PREFIXES = 1 (number of configured prefixes) ISIS_RA_PREFIX_0: field RAP_id=1 field RAP_type=3 (point to point MESA) field RAP_len=1 (1 MESA configured) field RAP_addr=020544444406 (equipment B ISIS_SYS_ID) field RAP_metric=20 field RAP_cid=00060000000 (seventh DCC) this prefix supplies to equipment A the information necessary to connect to equipment B (equipment B NSAP is: NSAP = 20, 4901020304050607080900004402054444440601) CLNS_PARAM: field router_type=1 (local router) DCC_PROFILE_0=1513,1492,1,7,20,20,0,1,1,3,10,20,200,15,7,300,600,3 (eighth field ext_domain=1) DCC_CONFIG_6=0,1,1 (seventh DCC, profile 0, network, enabled)


339-1268/06

.

Navigation Page

250

Book Contents



OSIBM.ini ********************************** @OSI.ini@ [OSI_CONFIG] PSAP = not_used ; PRESENTATION = not_used ; SSAP = not_used ; SESSION = not_used ; TSAP = not_used ; TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8; NSAP = 20, 4901020304050607080900004402054444440601 ; NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2; ISIS_SYS_ID = 6 , 020544444406 ; ISIS_MAN_AREA_ADDR_0 = 13 , 49010203040506070809000044 ; ISIS_MAN_AREA_ADDR_1 = 0 , ; ISIS_MAN_AREA_ADDR_2 = 0 , ; ISIS_NUM_RA_PREFIXES = 1 ; ISIS_RA_PREFIX_0 = 1,3,1,020521797106,20,000400000000; ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111; CLNS_PARAM = 0 , 0 , 1 ; ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,3,1800,10,600,3; MAC_ADDR = 020544444406 ; DCC_PROFILE_0 = 1513,1492,1,7,20,20,0,1,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_1 = 1513,1492,1,7,20,20,0,0,0,3,10,20,200,15,7,300,600,3; DCC_PROFILE_2 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_3 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_CONFIG_0 = 0 , 0 , 0 ; DCC_CONFIG_1 = 0 , 0 , 0 ; DCC_CONFIG_2 = 0 , 0 , 0 ; DCC_CONFIG_3 = 0 , 0 , 0 ; DCC_CONFIG_4 = 0 , 0 , 0 ; DCC_CONFIG_5 = 0 , 0 , 0 ; DCC_CONFIG_6 = 0 , 0 , 0 ; DCC_CONFIG_7 = 0 , 0 , 0 ; # ~**********************************

File notes


339-1268/06

.

Navigation Page

251

Book Contents


NSAP = 20, 4901020304050607080900004402054444440601 ISIS_NUM_RA_PREFIXES = 1 (number of configured prefixes) ISIS_RA_PREFIX_0: field RAP_id=1 field RAP_type=3 (point to point MESA) field RAP_len=1 (1 MESA configured) field RAP_addr=020521797106 (equipment B ISIS_SYS_ID) field RAP_metric=20 field RAP_cid=00040000000 (fifth DCC) this prefix supplies to equipment B the information necessary to connect to equipment A (equipment A NSAP is: NSAP = 20, 4901020304050607080900004402052179710601) CLNS_PARAM: field router_type=1 (local router) DCC_PROFILE_0=1513,1492,1,7,20,20,0,1,1,3,10,20,200,15,7,300,600,3 (eighth field ext_domain=1) DCC_CONFIG_6=0,1,1 (fifth DCC, profile 0, user, enabled)

Example 4 (MESA, different areas) Ethernet equipment A ---------------------- equipment B equipment A NSAP: 4901020304050607080900004402052179710601 equipment B NSAP: 4901020304050607080900004402054444440601


339-1268/06

.

Navigation Page

252

Book Contents



OSIAMEt.ini ********************************** @OSI.ini@ [OSI_CONFIG] PSAP = not_used ; PRESENTATION = not_used ; SSAP = not_used ; SESSION = not_used ; TSAP = not_used ; TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8; NSAP = 20, 4901020304050607080900004402052179710601 ; NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2; ISIS_SYS_ID = 6 , 020521797106 ; ISIS_MAN_AREA_ADDR_0 = 13 , 49010203040506070809000044 ; ISIS_MAN_AREA_ADDR_1 = 0 , ; ISIS_MAN_AREA_ADDR_2 = 0 , ; ISIS_NUM_RA_PREFIXES = 1 ; ISIS_RA_PREFIX_0 = 1, 2, 1, 020544444406, 20, 020544444406; ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111; ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111; CLNS_PARAM = 0 , 0 , 1 ; ETH_CONFIG = 7,1,0,1,1492,20,20,64,64,3,1800,10,600,3; MAC_ADDR = 020521797106 ; DCC_PROFILE_0 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_1 = 1513,1492,1,7,20,20,0,0,0,3,10,20,200,15,7,300,600,3; DCC_PROFILE_2 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_PROFILE_3 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3; DCC_CONFIG_0 = 0 , 0 , 0 ; DCC_CONFIG_1 = 0 , 0 , 0 ; DCC_CONFIG_2 = 0 , 0 , 0 ; DCC_CONFIG_3 = 0 , 0 , 0 ; DCC_CONFIG_4 = 0 , 0 , 0 ; DCC_CONFIG_5 = 0 , 0 , 0 ; DCC_CONFIG_6 = 0 , 0 , 0 ; DCC_CONFIG_7 = 0 , 0 , 0 ; # ~**********************************

File notes


339-1268/06

.

Navigation Page

253

Book Contents


NSAP = 20, 4901020304050607080900004402052179710601 ISIS_NUM_RA_PREFIXES = 1 (number of configured prefixes) ISIS_RA_PREFIX_0: field RAP_id=1 field RAP_type=2 (broadcast MESA) field RAP_len=1 (1 MESA configured) field RAP_addr=020544444406 (equipment B ISIS_SYS_ID) field RAP_metric=20 field RAP_cid=020544444406 (seventh DCC) this prefix supplies to equipment A the information necessary to connect to equipment B (equipment B NSAP is NSAP = 20, 4901020304050607080900004402054444440601) CLNS_PARAM: field router_type=1 (local router) ETH_CONFIG=7,1,0,1,1492,20,20,64,64,10,1800,30,600,3 (second field ext_domain=1, fourth field gateway_enable=1, Ethernet enabled)

DESCRIPTION OF AGENT.CNF FILE The AGENT.cnf file is an ASCII file which must be used when a two-wires alarm contact management is required and when the equipment must be configured as Regenerator. The two-wires alarm contact management requires an AGENT.cnf file download procedures and hardware pre-setting on End Of Shelf Unit. The Equipment will read AGENT.cnf, after a reset command of the Communication and Control Unit or a Physical Reset. In the following is given the default AGENT.cnf file, that a user eventually can change and load on the Communication and Control Unit database. @AGENT.cnf@ [MAIN] INST_TYPE = LOCAL HIDDEN = 0 F4TIME = 3 DELAY = 0 DEBUG = OFF [CONFIG]

Note

EQ_NAME = please refer to default values table MD95 = NO_MD95

Note

EQ_TYPE = please refer to default values table

Note

N_SLOT = please refer to default values table

N_SHELF = 1 N_EXT_OUT = 32 N_EXT_IN = 4 N_LAMP = 11 GC_CONF = ONE_WIRE ALARM_SHOW = YES [B_INTERFACE] OUT_1 = *,URG,*,*


339-1268/06

.

Navigation Page

254

Book Contents


OUT_2 OUT_3 OUT_4 OUT_5 OUT_6 OUT_7 OUT_8 OUT_9 OUT_10 OUT_11 OUT_12 OUT_13 OUT_14 OUT_15 OUT_16 OUT_17 OUT_18 OUT_23 OUT_24 OUT_28 [LAMP] LAMP_1 LAMP_2 LAMP_3 LAMP_4 LAMP_5 LAMP_6 LAMP_7 LAMP_8

Note

= = = = = = = = = = = = = = = = = = = =

*,NURG,*,* *,IND,*,000001101000000000001 EXT,*,*,000001101000000000001 INT,*,*,000001101000000000001 *,IND,*,000000000111100000000 EXT,*,*,000000000111100000000 INT,*,*,000000000111100000000 *,IND,*,000000000000000001110 EXT,*,*,000000000000000001110 INT,*,*,000000000000000001110 *,IND,*,011000000000000000000 EXT,*,*,011000000000000000000 INT,*,*,011000000000000000000 *,IND,*,000110000000000000000 EXT,*,*,000110000000000000000 INT,*,*,000110000000000000000 *,*,30,* *,*,29,* *,URG,*,000000000000000100000 *,URG,*,000000000000011110000 = = = = = = = =

*,*,*,* MEM,*,*,* *,URG,*,* *,NURG,*,* INT,*,*,* EXT,*,*,* *,IND,*,* ABN,*,*,*

In the following table are listed the default values for the fields: EQ_TYPE, N_SLOT EQ_NAME

EQ_TYPE

N_SLOT

ADM-4

MSH41C

ADM

16

ADM_16

MSH51C

ADM

26

ADM-64

MSH64

ADM

15

MSH53C

REG

?

MSH63

REG

?

REG-4/16 REG-64

EQ_NAME,

Tab. -1 Default values of the AGENT.cnf file

Here are described the entry fields of AGENT.cnf section. NOTICE

the first line after @AGENT.cnf@ section must be blank.

NOTICE

If a field is empty or not present, the equipment uses the default value.

MAIN section n INST_TYPE: distinguish Name Type; the value is GLOBAL or LOCAL (default is LOCAL). With MV36 the value LOCAL must be used; n HIDDEN: if the value is 1 then the attributes in Information Model added in the equipment are hidden to Manager : in this way the Q interface is fully standard; if 0 the attributes are not hidden (default is 0). With MV36 the value 0 must be used;


339-1268/06

.

Navigation Page

255

Book Contents


n F4TIME: it is the integration time in seconds for F4 filter, that is the time an alarm must stay on or off in order to be reported or cleared by the controller unit. It may vary from 1 second to 20 seconds (default is 3 seconds); n DELAY: Delay time to wait after a message is send to the management (in milliseconds). Default value is 0, that is there is no wait; using a value different from 0 slows down the equipment management (such behaviour may be useful with some management centre too slow: this is not the case for MV36); n DEBUG: if this option is ON the debugging mode is enabled. Default is OFF. The use of this option is reserved to lab personnel.

CONFIG section n EQ_NAME: Equipment Name (for the default value see Tab. -1); n EQ_TYPE: Equipment Type. For the ADM-4 and ADM-16 the value may be ADM or REG (default is ADM). If ADM is selected the equipment acts as an Add Drop Multiplexer allowing cross connections and the use of matrix unit. If REG is selected, the equipment acts as a Regenerator. For the ADM-64 the value is always ADM and for the REG-4/16 and REG-64 is always REG. n N_SHELF: Managed shelf number (for the default value see Tab. -1); n N_SLOT: Slot number in the shelf (for the default value see Tab. -1); n N_EXT_OUT: Number of outgoing Ground Contacts; default is 32 for One Wire Ground Contacts; in Two Wire case, the number is 11; n N_EXT_IN: Number of incoming Ground Contacts (default is 4); n N_LAMP: Number of lamps in End Of Shelf card, managed by the equipment (default is 8); n GC_CONF: Type of outgoing Ground Contacts; there are two cases: ONE_WIRE and TWO_WIRE (default is ONE_WIRE). In case of TWO_WIRE contacts, the number N_EXT_OUT must be 11; n ALARM_SHOW: this option offers the possibility to enable/disable the LED indication by means of EOS LEDs in case of acknowledged alarm. The value may be YES or NOT; n RACK_LAMP: The RAU, fitted with three LEDs, can be set according to three configurations:


339-1268/06

.

Navigation Page

256

Book Contents


Configur ation A

LEFT LED LED Colour

Meaning

Red

Urgent

MIDDLE LED LED Colour Yellow or

Meaning Not Urgent

Green B

C

Red

Red

RIGHT LED LED Colour Green or

Meaning (*)

Yellow

Any active

Green or

EOW call

alarm

Red

received

Urgent or

Yellow

Indicative

Yellow

Green

(*)

(*)

Not Urgent Note(*)

This LED is illuminated after an alarm acknowledgement operation (pushing the button on the front panel of the End Of Shelf Unit or via software procedure).

n The possible values of RACK_LAMP are URG_NURG_MEM (A configuration), NORMAL (B configuration) and MAJ_IND_MEM (C configuration). n AU4_DEFAULT: AU-4 Supervisory Unequipped mode. The value may be AU4_UNEQUIPPED or AU4_HOSU (default is AU4_UNEQUIPPED). When AU4_HOSU is selected, the High Order Supervisory Unequipped mode is automatically enabled for the next created AU-4; n MD95: DLC management via V.11 interface. The value may be NO_MD95 or YES_MD95 (default is NO_MD95). When YES_MD95 is selected, the V.11 interface is enabled. If NO_MD95 id selected, the V.11 interface is disabled; n LOWPATH: TU SNC Protection switching criteria. The value may be INHERENT or NOT_INTRUSIVE (default is NOT_INTRUSIVE). To use the Inherent switching criteria as default, select INHERENT.

B_INTERFACE section n OUT_N: it describes the characteristic of the N-Th Ground Contact, that is the conditions affecting the status of the ground contact. There are 4 comma-separated fields, which mean: alarm type (EXT, INT, ABN, MEM), alarm severity (URG, NURG, IND); alarm probable cause numeric code; bit mask defining the cards involved; if a field has "*" value, then it means DONT_CARE (any value are possible).

LAMP section n LAMP_N: See description for B_INTERFACE section.


339-1268/06

.

Navigation Page

257

Book Contents

FAULT DETECTION PROCEDURE All the alarms managed by the equipment are listed in the following, with their meanings, their default severity (it can be changed by the operator via software), their possible causes and detection procedures. The alarms can refer to a physical port or the AU-4 number within the STM-N frame. The following table shows how many ports (first column) and AUs (second column) can be managed by each unit. This value, starting from now, will be identified by the letter N. Furthermore the last five columns identify the correspondence between the equipment and the managed units. Tab. 2 Correspondence among equipment, unit and N

N (Ports)

N (AU)

ADM-64

ADM-16

ADM-4

STM-64 Opt

1

1 to 64

X

STM-16 Opt

1

1 to 16

X

X

STM-4 Opt

1

1 to 4

X

X

X

STM-1 Opt

1

1

X

X

STM-1 El

1

1

X

1x140/155Mbit/s (VC-12) El

1

1

X

2xSTM-1 Opt

1 to 2

1

2x140/155Mbit/s (VC-4) El

1 to 2

1

2x140/155Mbit/s (VC-12) El

1 to 2

1

4xSTM-1 Opt

1 to 4

1

4x140/155M

1 to 4

1

3x34/45Mbit/s

1 to 3

-

X

32x1,5/2Mbit/s

1 to 32

-

X

63x1,5/2Mbit/s

1 to 63

-

X

Booster +10, +12, +16

-

-

X

X

Booster +17

-

-

X

Preamplifier

-

-

X

X

REG-64

REG-16

X X

X

X

X

X

X

X

X

X

bit/s (VC-4) El

X

X

X

X

X

X

X

X


339-1268/06

X

.

Navigation Page

Book Contents

MSHXXX - OPERATOR’S HANDBOOK FAULT DETECTION PROCEDURE

Tab. 2 Correspondence among equipment, unit and N

2 Channel WDM Gigabit Unit

Bidir.

Ethernet

-

-

1 to 2

_

X X

X

X

The alarms can refer to the Regenerator or Multiplex Section which letter x can be: n x = R: Regenerator Section n x = M: Multiplex Section In case of ADM 4 the alarms can refer to the TU, which multiplex level ”y” can be: n y = 12, 2, or 3 for the STM-4 Optical/Mux Unit, STM-1 Optical/Mux Unit, STM-1 Electrical/Mux Unit, 2xSTM-1 Optical/Mux Unit, 2x140/155Mbit/s (VC-12) Tributary Unit and 1x140/155Mbit/s (VC-12) Tributary Unit (when the last two units are set as SDH interfaces). In case of ADM 4, the alarms can refer to the VC, which multiplex level ”y” can be: n y = 4 for the 2x140/155Mbit/s (VC-4) Tributary Unit, 2x140/155Mbit/s (VC-12) Tributary Unit and 1x140/155Mbit/s (VC-12) Tributary Unit (when these units are set as PDH interfaces); n y = 4 when the alarmed AU-4 is demultiplexed at lower levels for the STM-4 Optical/Mux Unit, STM-1 Optical/Mux Unit, STM-1 Electrical/Mux Unit, 2xSTM-1 Optical/Mux Unit, 2x140/155Mbit/s (VC-12) Tributary Unit and 1x140/155Mbit/s (VC-12) Tributary Unit (when the last two units are set as SDH interfaces); n y = 3 for the 3x34Mbit/s Tributary Unit and 3x45Mbit/s Tributary Unit; n y = 12 for the (16+16)x1.5/2Mbit/s Tributary Unit, 32x1.5/2Mbit/s Tributary Unit and 63x1.5/2Mbit/s Tributary Unit. NOTICE

ADM 64 and ADM 16 are able to manage VC-4 level only then, relevant to these equipment, this field is meaningless because it always has the value 4.

The alarms can refer to the LTU (Line Termination Unit) which number ”w” can be: n w =1 for the STM-1 Electrical/Mux Unit, 2x140/155Mbit/s (VC-4) Tributary Unit, 2x140/155Mbit/s (VC-12) Tributary Unit, 1x140/155Mbit/s (VC-12) Tributary Unit, 3x34Mbit/s Tributary Unit and 3x45Mbit/s Tributary Unit; n w =4 for the (16+16)x1.5/2Mbit/s Tributary Unit and 32x1.5/2Mbit/s Tributary Unit; n w =8 for the 63x1.5/2Mbit/s Tributary Unit.


339-1268/06

.

Navigation Page

259

Book Contents


The alarms are detected by functional blocks on the units shown in the following diagram. LINE Rx

RS RS Rx

Rx

RS MS Rx Rx

MATRIX AU4/VC4 Rx

TRIBUTARY SDH

RS TUy

TUy Tx

Rx

Rx

RS MS

RS AU4 Rx

Tx

RS RS

RS MS

Tx

Tx

Rx

Rx

RS Tx Rx

LT U (*)

INT

INT

Tx

RS Tx

Rx

Tx

AU4 Tx

RS TUy

TUy Rx

Rx

Tx

AU4/VC4 Rx

RS Rx

MS Rx

RS Rx Rx

TRIBUTARY PDH 2, 34, 45Mb/s PDH Tx

VCy Tx

LT U (*)

INT

(*) Only for electrical interfaces PDH Rx

VCy Rx

NOTE 1: There aren’t detectable alarms for the blocks surrounded by the dashed rectangles NOTE 2: The blocks show with a gray background are managed by ADM-4 only.

TRIBUTARY PDH nx140Mb/s AU4 Tx

VC4 Tx

LT U (*)

INT

VC4 Rx

PDH Tx

PDH Rx

ALARM TYPES In the following all the alarms detected are reported.

AU4: n AIS Severity: INDICATIVE Detected on the AU4 Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). Detected on the AU4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as PDH interface). This is an Administrative Unit Alarm Indication Signal received from the remote equipment; AU-AIS defect is detected when all "1" in the entire AU including AU pointer are observed (for three frames). In case of PDH unit:


339-1268/06

.

Navigation Page

260

Book Contents


Problem: 1. Consequence of the following alarms: LOS, LOF, MS-EXC, MS-AIS, RS-TIM detected on the STM-N unit which is providing the incoming VC4 to the PDH unit 2.

Switch unit fail

3.

Failure on the STM-N unit which is providing the incoming VC4 to the PDH unit Action:

1.

Follow the trouble-shooting procedure for the relevant alarms

2. Perform a forced switch to the protecting switch unit. If the alarm goes off, problem on the switch unit and follow: Unit Internal Fault Trouble-Shooting Procedure 3.

Check the status of the STM-N unit which is providing the incoming VC4 to the PDH unit

In case of SDH unit: Problem: 1.

Failure in the far-end equipment. Action:

1.

Check the status of the far-end equipment

AU4: n DEG Severity: NOT URGENT Detected on the AU4 Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). Detected on the AU4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as PDH interface). This is an indication of a bit error rate from e³10-5 to e³10-9 (threshold pre-settable via Software) on the received high level payload (check on B3 byte) on port n. This alarm can be detected when the relevant AU-4 is under monitor (AU-4 monitor enabled via Software). Problem: 1.

Excessive degradation of the optical fibre Coupling attenuation Failure on the far-end transmitter

2.

Unit internal failure Action:

1. Check if the same alarm is detected at the termination of the path. If the alarm is DETECTED, follow: Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG) 2. Check if the same alarm is detected at the termination of the path. If the alarm is NOT DETECTED, follow: Unit Internal Fault Trouble-Shooting Procedure


339-1268/06

.

Navigation Page

261

Book Contents


AU4: n EXC Severity: URGENT Detected on the AU4 Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is an indication of a bit error rate e³10-3 on the received high level payload (check on B3 byte) on port n or AU-4 n. This alarm can be detected when the relevant AU-4 is under monitor (AU-4 monitor enabled via Software). Problem: 1.


2.

Unit internal failure


339-1268/06

.

Navigation Page

262

Book Contents


Action: 1. Check if the same alarm is detected at the termination of the path. If the alarm is DETECTED, follow: Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG) 2. Check if the same alarm is detected at the termination of the path. If the alarm is NOT DETECTED, follow: Unit Internal Fault Trouble-Shooting Procedure

AU4: n LOP Severity: URGENT Detected on the AU4 Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This alarm is an indication of a Loss Of Administrative Unit Pointer on port n or AU-4 n. Problem: 1. Transmitter of the far-end equipment is configured for a different multiplexing path (AU3/AU4) or for a different standard (SONET/SDH) 2.

Consequence of far-end equipment transmitter failure or Unit internal failure Action:

1. 2.

Use the Software to check the local configuration, check the remote configuration Proceed as described in: SDH LOS Fault Trouble-Shooting Procedure

AU4: n RDI Severity: INDICATIVE Detected on the AU4 Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is a High Order Remote Defect Indication on port n or AU-4 n received from the remote multiplexer. This alarm can be detected when the relevant AU-4 is under monitor (AU-4 monitor enabled via Software). It indicates that the far-end port has detected some problems into the received stream. Problem: 1.

Consequence of the following alarms, detected on the far-end equipment: AU4: n LOP AU4: n AIS VC4: n EXC VC4: n TIM VC4: n UNEQ VC4: n PLM


339-1268/06

.

Navigation Page

263

Book Contents


Action: 1. Check the status of the far-end port and follow the “Fault Detection Procedure” for the detected alarm.

AU4: n TIM Severity: URGENT Detected on the AU4 Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is an indication of a mismatch between the received and expected J1 Trace Identifier on port n or AU-4 n. This alarm can be detected when the relevant AU-4 is under monitor (AU-4 monitor enabled via Software). Problem: 1.

Transmitter on the far-end equipment configured with a different path trace Action:

1. Check, using the Software facilities, the local and destination J1 equipment configuration and the status of the intermediate Digital Cross-connector Equipment

AU4: n UNEQ Severity: URGENT Detected on the AU4 Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). The UNEQUIPPED indicates that in the far-end equipment the AU-4 on port n or AU-4 n is not connected. The unexpected reception of AU-4 unequipped indicates that a connection error has occurred on the path. This alarm can be detected when the relevant AU-4 is under monitor (AU-4 monitor enabled via Software). Action: 1.

Check the cross connection in the remote equipment

Buffer Overflow Severity: URGENT Detected on the VC-4 Rx block of the following units: Gigabit Ethernet Units and .STM-16 for VC4-4c/4v and 16c/16v Units This alarm indicates that one or more channels are missing in a group of virtual VC-4 connection. Problem: 1. Wrong Virtual VC-4 configuration or problem in the Virtual VC-4 Action: 1. Check the Virtual VC-4 configuration and the status of the Virtual VC-4


339-1268/06

.

Navigation Page

264

Book Contents


DC/DC 1 Fault Severity: URGENT Detected on: Communication and Control Unit Action: 1.

Proceed as indicated in: Input Ground Contact

DC/DC 2 Fault Severity: INDICATIVE Detected on: Communication and Control Unit Action: 1.


DCC-x: n LAPD Disconnected Detected on the RS Rx or MS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is an indication of errors in the link access protocol data or loss of DCC channel of DCC R or M in the port n. Problem: 1.

Wrong LAPD configuration

2.

Consequence of the following alarms: T.SDH: n LOS RS: n LOF

3.

Loss of DCC channel from the remote equipment Action:

1. Using the Software check the local and remote LAPD configuration for the STM-N interfaces (NETWORK must be connected to USER and vice-versa) 2.

Follow the procedure for the T.SDH: n LOS alarm

3.

Check the remote equipment

Disparity Fail Severity: NOT URGENT Detected on the MS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). There is a problem of communication with the Auxiliary Unit concerning auxiliary channels on port n. Problem: 1.

Consequence of the alarms: T.SDH: n LOS


339-1268/06

.

Navigation Page

265

Book Contents


Missing Unit Unit Fail 2.

Problem on the Auxiliary Unit Action:

1.

Follow the procedure for the detected alarms

2.

Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

Ethernet Link Down Severity: URGENT Detected on the Rx block of the Gigabit Ethernet Units. This alarm indicates that the unit has not received idle signal for 200ms. Problem: 1 Possible problem in the autonegotiation process 2. Failure on the far-end transmitter or problem in the line 3. Internal failure on the local or far-end protection Line Unit Action: 1 Disable the autonegotiation process, if the alarm does not go off check the causes 2. Check the status of the far-end transmitter and the line 3. Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

Fan Assy Absent Severity: INDICATIVE Detected on: Communication and Control Unit Action: 1.


Fan Fail Severity: NOT URGENT Detected on: Communication and Control Unit. This alarm indicates a failure in the Environmental Control Unit. Problem: 1.

Both the two Power Supply for Environmental Control Units are faulty or switched off

2.

One or more Environmental Control Units are not fitted

3.

One or more Environmental Control Units are faulty Action:


339-1268/06

.

Navigation Page

266

Book Contents


1.

Check that the Power Supply for Environmental Control Units are working properly

2.

Insert the missing Environmental Control Unit(s)

3.

Replace the faulty Environmental Control Unit(s) with the spare one(s)

FEC_DEGRADE Severity: NOT URGENT Detected on the Rx block of the STM-64 G.709 Units. This is an indication of the number of corrected errors in one second exceeds the threshold of X errors, X is presettable via Software in the range from 10-5 to 10 6 equivalent to BER of e³10-15 to e³10-4. Problem: 1.

Degradation of the line Coupling attenuation Failure on the far-end transmitter

2.


1.

If optical unit, proceed as indicated in: Bit Error Rate on the STM-N Optical Signal (MS-EXC/DEG and RS-EXC/DEG)

General Supply Fail Severity: NOT URGENT Detected on: Communication and Control Unit. Action: 1.


High Temperature Severity: URGENT Detected on: Communication and Control Unit. Action: 1.


Laser Bias Out Severity: NOT URGENT Detected on the Tx block of the STM-N and NxSTM-1 Optical units, Preamplifier and Booster Unit. This alarm indicates that laser bias current is out of range. Problem: 1.

Unit Internal failure


339-1268/06

.

Navigation Page

267

Book Contents


Action: 1.


Laser Pwr Out Severity: NOT URGENT Detected on the Tx block of the STM-N and NxSTM-1 Optical units, Preamplifier and Booster Unit. This alarm indicates failure of the laser module. Problem: 1.

Unit Internal failure Action:

1.


Laser Tmp Out Severity: URGENT Detected on the Tx block of the STM-N and NxSTM-1 Optical units, Preamplifier and Booster Unit. This alarm indicates that the laser temperature value is out of range (±7º C from the factory calibration value for all optical units except ±2º C for STM-16 for WDM). Problem: 1.

Unit Internal failure Action:

1.


Laser Tx Power Thr High Severity: INDICATIVE Detected on the Tx block of the following units: STM-16 Optical/Mux Unit for WDM. This alarm indicates that the laser transmission power has been configured, via Software, too high (grater than -1dBm). Problem: 1.

Wrong transmission power configuration. Action:

1.

Check the transmission power value and reduce it to an acceptable one

Laser Tx Power Thr Low Severity: INDICATIVE Detected on the Tx block of the following units: STM-16 Optical/Mux Unit for WDM.


339-1268/06

.

Navigation Page

268

Book Contents


This alarm indicates that the laser transmission power has been configured, via Software, too low (less than -12dBm). Problem: 1.

Wrong transmission power configuration Action:

1.

Check the transmission power value and increase it to an acceptable one

Loss of Multi Frame Severity: URGENT Detected on the VC-4 Rx block of the following units: Gigabit Ethernet Units and .STM-16 for VC4-4c/4v and 16c/16v Units Loss of Multiframe in a VC-4-nV concatenated traffic type. If several H4 values are received consecutively not correctly in sequence with any part of the multiframe sequence, then a loss of multiframe (LOM) event is reported.. Problem: 1. Errors during the reconstruction of the virtual concatenated traffic type. Action: 1. Check the remote equipment where the VC-4s come from and their paths.

Loss of Sequencing Severity: URGENT Detected on the VC-4 Rx block of the following units: Gigabit Ethernet Units and .STM-16 for VC4-4c/4v and 16c/16v Units Loss of Sequence defect is detected if the accepted sequence number does not match the expected sequence number. The received sequence number is recovered from the H4 byte, bits 14 in multiframe 14 and 15. Problem: 1. The number of received multiframes with not correct sequence number has exceeded the threshold set. Action: 1. Check the far-end equipment where the VC-4s come from and their paths.

LTU w Fail Severity: URGENT Detected on the Rx block of the following units: STM-1 Electrical/Mux Unit, Nx140/155Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit, 3x45Mbit/s Tributary Unit, (16+16)x1.5/2Mbit/s Tributary Unit, 32x1.5/2Mbit/s Tributary Unit and 63x1.5/2Mbit/s Tributary Unit.. This is an indication of Line Terminal Unit malfunction. The Line Terminal Unit, according to the connected traffic unit, can be:


339-1268/06

.

Navigation Page

269

Book Contents


n 140/155Mbit/s Connection Unit for the STM-1 Electrical/Mux Unit and for 1x140/155Mbit/s (VC-12) Tributary Unit; n 2x140/155Mbit/s Connection Unit for the 2x140/155Mbit/s (VC-4) Tributary Unit and 2x140/155Mbit/s (VC-12) Tributary Unit; n 4x34/45Mbit/s Connection Unit for the 3x34Mbit/s Tributary Unit and 3x45Mbit/s Tributary Unit; n Tx 16x2Mbit/s Connection Unit and Rx 16x2Mbit/s Connection Unit for the (16+16)x1.5/2Mbit/s Tributary Unit, 32x1.5/2Mbit/s Tributary Unit and 63x1.5/2Mbit/s Tributary Unit. Problem: 1.

Line Terminal Unit not fitted

2.

Problems with the connectors

3.

Line Terminal Unit internal failure Action:

1.

Insert the missing connection unit

2. Check whether all pins of the male subrack connector corresponding to the alarmed connection unit are straight 3.

Replace the faulty connection unit

The numbering of the Line Terminal Units will follow the physical position into the subrack according to the figure shown below.

L L L L

L L

T T T T U U U U

T T U U

L

2 4 6 8

2 4

U

T 1

L L L L

L L

T T T T

T T

U U U U

U U

1 x 140/155Mbit/s

1 3 5 7

1 3

2 x 140/155Mbit/s

1 x 155Mbit/s

3 x 34Mbit/s 63 x 1.5/2Mbit/s

32 x 1.5/2Mbit/s

3 x 45Mbit/s

Fig. 9 ADM-4 LTU numbering


339-1268/06

.

Navigation Page

270

Book Contents


L L L L L L L L L L L L T T T T T T T T T T T T U U U U U U U U U U U U 1 2 3 4 5 6 7 8 9 10 11 12 4x140/155Mbit/s

1

2

3

4

5

6

7

8

9 10

Fig. 10 ADM-16 LTU numbering

For ADM-64 the LTU numbering does not follow any particular rule because the equipment managed only one unit that needs the connectors interface: the 4x140/155Mbit/s electrical unit.

Missing Unit Severity: NOT URGENT Detected on: all the units excepted for the Communication and Control Unit. This alarm indicates that a unit, configured into the database, it is not inserted. Problem: 1.

Unit not fitted

2.

Problems with the connectors Action:

1.

Insert the missing unit

2. Check whether all pins of the male subrack connector corresponding to the alarmed unit are straight

MS OH: n DISP FAIL Detected on the MS Rx block of the following units: 4x140/155Mbit/s Tributary Unit (when set as SDH interface), STM-64 Optical/Mux Unit, STM-16 Optical/Mux Unit, STM-4 Optical/Mux Unit, 2xSTM-1 Optical/Mux Unit. This is an indication of disparity fail on the Over Head Bytes. Problem of communication with the Auxiliary Unit concerning auxiliary channels using MS spare bytes on port n. Problem: 1. Consequence of the alarms T.SDH: n LOS, Missing Unit, Unit Fail concerning the 4x140/155Mbit/s Tributary Unit, STM-64 Optical/Mux Unit, STM-16 Optical/Mux Unit, STM-4 Optical/Mux Unit, 2xSTM-1 Optical/Mux Unit. 2.


1.

Follow the procedure for the detected alarm


339-1268/06

.

Navigation Page

271

Book Contents


2.


MS OW: n DISP FAIL Detected on the MS Rx block of the following units: 4x140/155Mbit/s Tributary Unit (when set as SDH interface), STM-64 Optical/Mux Unit, STM-16 Optical/Mux Unit, STM-4 Optical/Mux Unit, 2xSTM-1 Optical/Mux Unit. This is an indication of disparity fail on the Order Wire Bytes. Problem of communication with the Auxiliary Unit concerning auxiliary channels using E2 byte on port n. Problem: 1. Consequence of the alarms T.SDH: n LOS, Missing Unit, Unit Fail concerning the 4x140/155Mbit/s Tributary Unit, STM-64 Optical/Mux Unit, STM-16 Optical/Mux Unit, STM-4 Optical/Mux Unit, 2xSTM-1 Optical/Mux Unit. 2.

Problem on the Auxiliary Unit


339-1268/06

.

Navigation Page

272

Book Contents


Action: 1.


2.


MS: n AIS Severity: INDICATIVE Detected on the MS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is an Alarm Indication Signal, on Multiplex Section port, received from a remote regenerator equipment on the port n (the pattern 111 is observed in bits 6,7 and 8 of K2 byte in at least 3 consecutive frames). Problem: 1. Fault on the reception side of the far-end regenerator or the far-end regenerator has detected some problems into the received stream Action: 1.

Check the alarm status of the far-end regenerator equipment

MS: DAC Severity: URGENT Default APS Code, it is risen when the default value of APS Code (k1 and k2 are equal zero ) for three consecutive frames. Problem: 1. Internal failure on the local or far-end protection Line Unit Action: 1. Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

MS: n DEG Severity: NOT URGENT Detected on the MS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is an indication of a bit error rate from e³10-5 to e³10-9 (threshold presettable via Software) on the Multiplex Section port n. in the received signal (check on B2 byte). Problem: 1.


2.



339-1268/06

.

Navigation Page

273

Book Contents


Action: 1.


2.

If electrical unit, proceed as indicated in: Bit Error Rate on the PDH and STM-1 Electrical Signal (PDH EXC/DEG and MS EXC/DEG)

MS: n EXC Severity: URGENT Detected on the MS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is an indication of a bit error rate e³10-3 on the Multiplex Section port n in the received signal (check on B2 byte). Problem: 1.


2.


1.


2.

If electrical unit, proceed as indicated in: Bit Error Rate on the PDH and STM-1 Electrical Signal (PDH EXC/DEG and MS EXC/DEG)

MS: IAC Severity: URGENT Improper APS Code, it is risen when the received APS value is wrong for three consecutive frames. Problem: 1. Internal failure on the local or far-end protection Line Unit Action: 1. Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

MS: INV Severity: URGENT Invalid APS (Automatic Protection Switch) protocol (MSP). Mismatch between the expected value of the received K2 (bits 1 to 5 of byte K2) and sent K1 byte. MSP bytes is accepted as valid only when identical bytes are received in three consecutive frames


339-1268/06

.

Navigation Page

274

Book Contents


Note

A detected failure of the received K1 or K2 is considered as equivalent to an SF (Signal Failure) condition on the protection section (MSP bytes are transmitted on the protection section) Problem:

1. Wrong MSP configuration 2. Internal failure on the local or far-end protection Line Unit Action: 1. Check with the Control Application the local MSP configuration Check the far-end MSP configuration 2. Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

MS: NIM Severity: URGENT Node Id Mismatch, it is raised when the fields relevant to the source and destination node id in the byte k1 and k2 are mismatching for three consecutive frames. Problem: 1. Internal failure on the local or far-end protection Line Unit Action: 1. Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

MS: PAM Severity: URGENT Multiplex Section Protection Architecture Mismatch. Mismatch between the MSP (multiplexing section protection) architecture configuration (1+1, 1:N or 1+N) Problem: 1. Wrong MSP configuration Action: 1. Check with the Control Application the local MSP configuration Check the far-end MSP configuration

MS: n RDI Severity: INDICATIVE Detected on the MS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is a Remote Defect Indication on the Multiplex Section port, received from the remote multiplexer on the port n (the pattern 110 is observed in bits 6,7 and 8 of K2 byte in at least 3 consecutive frames).


339-1268/06

.

Navigation Page

275

Book Contents


It indicates that the far-end multiplexer equipment has detected some problems into the received stream. Problem: 1.

Consequence of the alarms: MS: n AIS MS: n EXC RS: n LOF RS: n TIM T.SDH: n LOS (*) Detected on the receive side of the far-end multiplexer Action:

1. Check the alarm status of the far-end multiplexer equipment and follow the trouble shooting procedure for the detected alarm Note(*)

The MS: n RDI alarm can be detected in case of LOS only if the Automatic Laser Shutdown is not enabled or in case of electrical interface.

MS: SCM Severity: URGENT Selector Control Mismatch, it is risen when the far-end equipment sends a signalling of executed bridge for a different channel from the request one. It must persist over more 50ms. Problem: 1. Internal failure on the local or far-end protection Line Unit Action: 1. Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

MS: TMOUT Severity: URGENT It is risen when the tail-end does not get the answer from the head-end (the Reverse Request) by 50ms Problem: 1. Internal failure on the local or far-end protection Line Unit Action: 1. Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

OCH-AIS Severity: INDICATIVE Detected on the Rx block of the STM-64 G.709 Units.


339-1268/06

.

Navigation Page

276

Book Contents


This is an Alarm Indication Signal on the Optical Channel layer received from the remote equipment. Problem: 1. Fault on the reception side of the far-end equipment or the far-end equipment has detected some problems into the received stream Action: 1.

Check the alarm status of the far-end equipment

OCH-LOF Severity: URGENT Detected on the Rx block of the STM-64 G.709 Units. This is a Loss of Frame alarm detected at the Optical Channel layer. Action: 1.

Proceed as indicated in: SDH LOS Fault Trouble-Shooting Procedure

OCH-LOM Severity: URGENT Detected on the Rx block of the STM-64 G.709 Units. This is a Loss of Multi-frame alarm detected at the Optical Channel layer. Action: 1.


OTU-TIM Severity: URGENT Detected on the Rx block of the STM-64 G.709 Units. This is an indication of a Source Access Point Identifier Mismatch. Problem: 1. Transmitter on the far-end equipment configured with a different path trace identifier from the expected one Action: 1. Check, using the Software, that the remote transmitted SAPI is configured as the local expected one

OTU-BDI Severity: INDICATIVE Detected on the Rx block of the STM-64 G.709 Units. This is a Backward Defect Indication received from the remote equipment. Problem:


339-1268/06

.

Navigation Page

277

Book Contents


1. The far-end equipment has detected some problems into the received stream Action: 1. Check the alarm status of the far-end equipment and follow the trouble shooting procedure for the detected alarm

OTU-SSF Severity: INDICATIVE Detected on the Rx block of the STM-64 G.709 Units. This is an indication of Server Signal Failure at the Optical channel Transport Unit layer. Problem: 1. Problem on the Optical Physical Section in the trail termination Action: 1. Check the status of the Optical Physical Section in the trail termination

ODU-AIS Severity: INDICATIVE Detected on the Rx block of the STM-64 G.709 Units. This is an Alarm Indication Signal at the Optical Channel Data Unit layer. Problem: 1.

Consequence of fault in the far-end equipment Action:

1.

Check the alarm status of the far-end equipment

ODU-BDI Severity: INDICATIVE Detected on the Rx block of the STM-64 G.709 Units. This is a Backward Defect Indication received from the remote equipment. Problem: 1. The far-end equipment has detected some problems into the received stream Action: 1. Check the alarm status of the far-end equipment and follow the trouble shooting procedure for the detected alarm

ODU-SSF Severity: INDICATIVE Detected on the Rx block of the STM-64 G.709 Units. This is an indication of Server Signal Failure at the Optical channel Data Unit layer, this alarm is generated when the OTU-TIM is detected. Action:


339-1268/06

.

Navigation Page

278

Book Contents


1. Proceed as indicated in the OTU-TIM alarm

ODU-OCI Severity: URGENT Detected on the Rx block of the STM-64 G.709 Units. This is an Open Connection Indication and indicates that the connection in an upstream element is open. Action: 1.

Check the configuration of the connection in the remote equipment

ODU-TIM Severity: URGENT Detected on the Rx block of the STM-64 G.709 Units. This is an indication of a Source Access Point Identifier Mismatch. Problem: 1. Transmitter on the far-end equipment configured with a different path trace identifier from the expected one Action: 1. Check, using the Software, that the remote transmitted SAPI is configured as the local expected one

ODU-PLM Severity: URGENT Detected on the Rx block of the STM-64 G.709 Units. This is an indication of a Source Access Point Identifier Mismatch. Problem: 1. Transmitter on the far-end equipment configured with a different path trace identifier from the expected one Action: 1. Check, using the Software, that the remote transmitted SAPI is configured as the local expected one

OH Bus Rx Fail Severity: INDICATIVE Detected on the INT block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is an indication of mismatch during the parity check on the Rx overhead bus. Problem: 1.



339-1268/06

.

Navigation Page

279

Book Contents


Action: 1.


OH Bus Tx Fail Severity: INDICATIVE Detected on the INT block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is an indication of mismatch during the parity check on the Tx overhead bus. Problem: 1. Unit internal failure Action: 1. Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

OR Batt Severity: NOT URGENT Detected on: Communication and Control Unit. This is an indication of loss of power supply from one of the two batteries. 1. 1.

Problem: Power supply cable disconnected or loss of power supply Action: Plug the power supply cable; check fuses, breakers and battery

Plug Module Missing Severity: NOT URGENT Detected on the Int block of the Gigabit Ethernet Units. This alarm indicates that a plug module of the Gigabit Ethernet unit, configured into the database, it is not inserted.

1.

Problem: Plug module not fitted Problems with the insertion of the module Action: Insert the missing plug module

2.

Check if the module is right fitted in the unit

1. 2.

Protection State Unstable Detected on the Switch Unit. This alarm indicates that the configurable threshold for the maximum number of the protection switches has been crossed and any new protection switch report will be suspended. The alarm will be cleared when the number of protection switches gets back under the configured threshold. Please note that the threshold can be configured by editing the “Agent.cnf” file.

Protection State Mismatch Detected on the Switch Unit.


339-1268/06

.

Navigation Page

280

Book Contents


Due to the crossing of the protection switches threshold, it is possible that the Control Application does not report the current data of the unit protection status. 1.

Action: Restart the Control and Communication Unit to realign the reports

Power Fail Detected on the INT block of the following units: all the unit of the equipment excepted for the Communication and Control Unit. This is an indication of on board DC/DC converter faulty. Problem: 1.


1.


QI/F Link Down Detected on: Communication and Control Unit. This is an indication of loss of Ethernet communication. Problem: 1.

Failure of the ethernet connection

2.


1. 2.

Check the ethernet link Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

Received Power High Low Severity: NOT URGENT Detected on the Rx block of the STM-N and NxSTM-1 Optical units (with a minimum sensitivity less or equal 8dBm). This alarm indicates that the incoming optical signal is grater than -8dBm. For the minimum sensitive value of the optical units, please refer to the table "Optical Performances" in the chapter "Technical Specifications" of the section 1 "Information for the System Engineer" in the "Equipment Manual". 1.

Problem: Wrong transmission power configuration of far-end equipment

2.

Fixed attenuators removed from the link

3.

Wrong unit type on far-end equipment

4.

Optical output power regulation loop malfunction on the far-end transmitter Action:


339-1268/06

.

Navigation Page

281

Book Contents


1.

Check the transmission power value of far-end equipment

2.

Check the presence of the possible fixed attenuators

3.

Check the unit type

4.


RS OH: n Disp Fail Detected on the RS Rx block of the following units: 4x140/155Mbit/s Tributary Unit (when set as SDH interface), STM-64 Optical/Mux Unit, STM-16 Optical/Mux Unit, STM-4 Optical/Mux Unit, 2xSTM-1 Optical/Mux Unit. This is an indication of disparity fail on the Over Head Bytes. Problem of communication with the Auxiliary Unit concerning auxiliary channels using RS spare bytes on port n. Problem: 1.

Consequence of the alarms: T.SDH: n LOS Missing Unit Unit Fail

2.


1.


2.


RS OW: n Disp Fail Detected on the RS Rx block of the following units: 4x140/155Mbit/s Tributary Unit (when set as SDH interface), STM-64 Optical/Mux Unit, STM-16 Optical/Mux Unit, STM-4 Optical/Mux Unit, 2xSTM-1 Optical/Mux Unit. This is an indication of disparity fail on the Order Wire Bytes. Problem of communication with the Auxiliary Unit concerning auxiliary channels using E1 byte on port n. Problem: 1.


2.


1.


2.



339-1268/06

.

Navigation Page

282

Book Contents


RS UC: n Disp Fail Detected on the RS Rx block of the following units: 4x140/155Mbit/s Tributary Unit (when set as SDH interface), STM-64 Optical/Mux Unit, STM-16 Optical/Mux Unit, STM-4 Optical/Mux Unit, 2xSTM-1 Optical/Mux Unit. This is an indication of disparity fail on the User Channel Bytes. Problem of communication with the Auxiliary Unit concerning auxiliary channels using F1 byte on port n. Problem: 1.


2.


1.


2.


RS: 1 DEG Severity: NOT URGENT Detected on the RS Rx block of the STM-4 and STM-16 Optical/Mux Unit, when the equipment is configured as regenerator only and on the RS Rx block of the STM-64 in the REG-64. This is an indication of a bit error rate e from 10-5 to 10-9 (threshold presettable via software) on the Regenerator Section port 1, in the received signal (check on B1 byte). Problem: 1.

Degradation of the line Coupling attenuation Failure on the far-end transmitter Unit internal failure Action:

1.

Proceed as indicated in: Bit Error Rate on the STM-N Optical Signal (MS-EXC/DEG and RS-EXC/DEG)

RS: 1 EXC Severity: URGENT Detected on the RS Rx block of the STM-4 and STM-16 Optical/Mux Unit, when the equipment is configured as regenerator only and on the RS Rx block of the STM-64 in the REG-64. This is an indication of a bit error rate e³10-3 on the Regenerator Section port 1 in the received signal (check on B1 byte).


339-1268/06

.

Navigation Page

283

Book Contents


Problem: 1.


1.

Proceed as indicated in: Bit Error Rate on the STM-N Optical Signal (MS-EXC/DEG and RS-EXC/DEG)

RS: n LOF Severity: URGENT Detected on the RS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is a Loss of Frame alarm detected at the incoming Regenerator Section of port n. Action: 1.


RS: n TIM Severity: URGENT Detected on the RS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is an indication of a J0 Trace Identifier Mismatch on Regenerator Section port n. Problem: 1. Transmitter on the far-end equipment configured with a different path trace identifier from the expected one Action: 1. Check, using the Software, that the remote transmitted J0 is configured as the local expected one

Sync Fail Severity: NOT URGENT Detected on: Communication and Control Unit. The clock signal extracted from the Rx interface of one port or one 2MHz/2Mbit/s external synchronisation source input is missing. Problem: 1.

Consequence of an Rx alarm detected on the involved port

2.

Internal failure on the unit involved in the synchronisation scheme

3.

Failure on the far-end transmitter


339-1268/06

.

Navigation Page

284

Book Contents


4.

Loss of the external synchronisation source input Action:

1.

Follow the trouble-shooting procedure for the main alarm

2.

Proceed as indicated in:

3.

Unit Internal Fault Trouble-Shooting Procedure

4.

Check the external synchronisation source input cable and the external clock generator.

T. PDH: n AIS Severity: INDICATIVE Detected on the PDH Rx block of the following unit: (16+16)x1.5/2Mbit/s Tributary Unit, 32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s G.703/G.704 CRC-4 Tributary Unit, 3x34Mbit/s Tributary Unit, 3x45Mbit/s Tributary Unit and Nx140/155Mbit/s Tributary Unit (when set as PDH interface). This is a Termination PDH - Alarm Indication Signal on port n, received from the connected PDH equipment. Action: 1.

Check the alarm status of the PDH equipment connected to the local Tributary Unit

T. PDH: n DEG Severity: NOT URGENT Detected on the PDH Rx block of the following unit: 3x34Mbit/s Tributary Unit, 3x45Mbit/s Tributary Unit and Nx140/155Mbit/s Tributary Unit (when set as PDH interface). This is an indication of a bit error rate from e³10-5 to e³10-9 (threshold presettable via Software) on the received PDH stream port n. Problem: 1.


1.

Proceed as indicated in: Bit Error Rate on the PDH and STM-1 Electrical Signal (PDH EXC/DEG and MS EXC/DEG)

T. PDH: n DEG (In – Faw) Severity: NOT URGENT Detected on the PDH Rx block of the following unit: 63x1.5/2Mbit/s G.703/G.704 CRC-4 Tributary Unit (when the 2Mbit/s signal is set framed),. This is an indication of a bit error rate from e³10-5 to e³10-9 (threshold presettable via Software) on the received PDH stream port n.


339-1268/06

.

Navigation Page

285

Book Contents


Problem: 1.


1.


T. PDH: n DEG (In - CRC-4) Severity: NOT URGENT Detected on the PDH Rx block of the following unit: 63x1.5/2Mbit/s G.703/G.704 CRC-4 Tributary Unit (when the 2Mbit/s signal is set CRC-4 multiframed). This is an indication of a bit error rate from e³10-5 to e³10-9 (threshold presettable via Software) on the received PDH stream port n. Problem: 1.


1.


Bit Error Rate on the PDH and STM-1 Electrical Signal (PDH EXC/DEG and MS EXC/DEG)

T. PDH: n EXC Severity: URGENT Detected on the PDH Rx block of the following unit: 3x34Mbit/s Tributary Unit, 3x45Mbit/s Tributary Unit and Nx140/155Mbit/s Tributary Unit (when set as PDH interface). This is an indication of a bit error Rate e³10-3 on the received PDH stream on port n. Problem: 1.


1.



339-1268/06

.

Navigation Page

286

Book Contents



T. PDH: n EXC (In – Faw) Severity: URGENT Detected on the PDH Rx block of the following unit: 63x1.5/2Mbit/s G.703/G.704 CRC-4 Tributary Unit (when the 2Mbit/s signal is set framed). This is an indication of a bit error Rate e³10-3 on the received PDH stream on port n. Problem: 1.


1.


T. PDH: n EXC (In - CRC-4) Severity: URGENT Detected on the PDH Rx block of the following unit: 63x1.5/2Mbit/s G.703/G.704 CRC-4 Tributary Unit (when the 2Mbit/s signal is set CRC-4 multiframed). This is an indication of a bit error Rate e³10-3 on the received PDH stream on port n. Problem: 1.


1.



T. PDH: n LOF Severity: URGENT Detected on the PDH Rx block of the following unit: 3x34Mbit/s Tributary Unit, 3x45Mbit/s Tributary Unit and Nx140/155Mbit/s Tributary Unit (when set as framed PDH interface). This is a Loss of Frame alarm detected at the incoming circuit level over a PDH framed signal in accordance ITU G751 on port n. Action:


339-1268/06

.

Navigation Page

287

Book Contents


1.

Proceed as indicated in: PDH LOS Fault Trouble-Shooting Procedure

T. PDH: n LOF (In) Severity: URGENT Detected on the PDH Rx block of the following unit: 63x1.5/2Mbit/s G.703/G.704 CRC-4 Tributary Unit (when the 2Mbit/s signal is set framed or CRC-4 multiframed). This is a Loss of Frame alarm detected at the incoming circuit level over a PDH framed signal on port n. Action: 1.


T. PDH: n LOS Severity: URGENT Detected on the PDH Rx block of the following unit: (16+16)x1.5/2Mbit/s Tributary Unit, 32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s G.703/G.704 CRC-4 Tributary Unit, 3x34Mbit/s Tributary Unit, 3x45Mbit/s Tributary Unit and Nx140/155Mbit/s Tributary Unit (when set as PDH interface). This is a Loss of Signal alarm detected at the incoming circuit level over a PDH signal on port n. Action: 1.


T. PDH: n CRC-4 mismatch (In) Severity: NOT URGENT Detected on the PDH Rx block of the following unit: 63x1.5/2Mbit/s G.703/G.704 CRC-4 Tributary Unit (when the 2Mbit/s signal is set CRC-4 multiframed). Wrong CRC4 bit sequence received on port n. Problem: 1. Wrong configuration of the connected PDH equipment. It is probably preset for not using the CRC4 function Action: 1. Check configuration of the PDH equipment

T. PDH: n RAI (In) Severity: INDICATIVE Detected on the PDH Rx block of the following unit: 63x1.5/2Mbit/s G.703/G.704 CRC-4 Tributary Unit (when the 2Mbit/s signal is set framed or CRC-4 multiframed). Remote Alarm Indication received from the connected PDH equipment, which is detecting errors on the received 2Mbit/s signal on port n.


339-1268/06

.

Navigation Page

288

Book Contents


Problem: 1. Excessive bit error rate or failures along the line which connects the local tributary output and the remote PDH equipment Action: 1. Check the line and the PDH equipment status

T. PDH: n AIS (Out) Severity: INDICATIVE Detected on the PDH Tx block of the following unit: 63x2Mbit/s G.703/G.704 CRC-4 Tributary Unit (when the 2Mbit/s signal is set framed or CRC-4 multiframed). This is an Alarm Indication Signal on the received PDH stream, from the matrix side, connected to the port n. Problem: 1. Consequence of the following alarms, detected on the far-end equipment: INCOMING LOS INCOMING AIS Action: 1. Check the far-end PDH equipment status

T. PDH: n DEG (Out - CRC-4) Severity: NOT URGENT Detected on the PDH Tx block of the following unit: 63x1.5/2Mbit/s G.703/G.704 CRC-4 Tributary Unit (when the 2Mbit/s signal is set CRC-4 multiframed). This is an indication of a bit error rate from e³10-5 to e³10-9 (threshold presettable via Software) on the received PDH stream, from the matrix side, connected to the port n. Problem: 1.


1.



T. PDH: n EXC (Out - CRC-4) Severity: URGENT Detected on the PDH Tx block of the following unit: 63x1.5/2Mbit/s G.703/G.704 CRC-4 Tributary Unit (when the 2Mbit/s signal is set CRC-4 multiframed).


339-1268/06

.

Navigation Page

289

Book Contents


This is an indication of a bit error Rate e³10-3 on the received PDH stream, from the matrix side, connected to the port n. Problem: 1.


1.



T. PDH: n LOF (Out) Severity: URGENT Detected on the PDH Tx block of the following unit: 63x1.5/2Mbit/s G.703/G.704 CRC-4 Tributary Unit (when the 2Mbit/s signal is set CRC-4 multiframed). This is a Loss of Frame alarm detected on the received PDH stream, from the matrix side, connected to the port n. Problem: 1. Wrong configuration of the remote PDH equipment. It is probably preset for not using the framed or the CRC-4 multiframed function Action: 1. Check the configuration of the far-end PDH equipment

T. PDH: n CRC-4 mismatch (Out) Severity: NOT URGENT Detected on the PDH Tx block of the following unit: 63x1.5/2Mbit/s G.703/G.704 CRC-4 Tributary Unit (when the 2Mbit/s signal is set CRC-4 multiframed). Wrong CRC4 bit sequence received on the matrix side. Problem: 1. Wrong configuration of the remote PDH equipment. It is probably preset for not using the CRC4 function Action: 1. Check configuration of the PDH equipment

T. PDH: n Tx Fail Severity: URGENT Detected on the PDH Tx block of the following unit: (16+16)x1.5/2Mbit/s Tributary Unit, 32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit, 3x45Mbit/s Tributary Unit and Nx140/155Mbit/s Tributary Unit (when set as PDH interface).


339-1268/06

.

Navigation Page

290

Book Contents


This alarm indicates that the Tx output circuit of the port n is not working properly. Problem: 1.


1.


T. SDH: n LOS Severity: URGENT Detected on the SDH Rx block of the STM-N, NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces), Preamplifier and Booster Unit. This is a Loss of Signal alarm detected at the incoming circuit level over a SDH signal on port n. Action: 1. If the involved unit is a 4x140/155Mbit/s Tributary Unit or a STM-N Optical/Mux Unit, proceed as indicated in: SDH LOS Fault Trouble-Shooting Procedure 1.

If the involved unit is a Preamplifier Unit or Booster Unit, proceed as indicated in: Preamplifier and Booster LOS Fault Trouble-Shooting Procedure

TC: n DEG Severity: NOT URGENT Detected on the VC-4 Rx block of the STM-N, NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is an indication of a bit error rate e from 10-5 to 10-9 (threshold presettable via software) on the received high level payload on port n or VC-4 n, between the end points of the Tandem Connection. Problem: 1.


2.



TC: n EXC Severity: URGENT


339-1268/06

.

Navigation Page

291

Book Contents


Detected on the VC-4 Rx block of the STM-N, NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is an indication of a bit error rate e³10-3 on the received high level payload on port n or VC-4 n, between the end points of the Tandem Connection. Problem: 1.


2.



TC: n IncAIS Severity: URGENT Detected on the VC-4 Rx block of the STM-N, NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This alarm indicates that a defect is present on the VC before the input end point of the Tandem Connection. It indicates that there are not defects on the Tandem Connection path. Problem: 1.

Failure in the far-end equipment before the input end point of the Tandem Connection Action:

1. Check the status of the far-end equipment before the input end point of the Tandem Connection

TC: n UNEQ Severity: URGENT Detected on the VC-4 Rx block of the STM-N, NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). The UNEQUIPPED indicates that the VC-4 on port n or VC-4 n is not connected, via switching matrix, to any source point. The unexpected reception of VC unequipped indicates that a connection error has occurred on the Tandem Connection path or indicates that the TC receive side (termination point) has been enabled while the TC transmit side is disabled (generation point). Action: 1.

Check the cross connection in local and remote equipment of the TC


339-1268/06

.

Navigation Page

292

Book Contents


TUy: n-k-l-m AIS Severity: INDICATIVE Detected on TUy Rx block of the STM-N, NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This alarm is an Tributary Unit Alarm Indication Signal received from the remote equipment on port n or AU-4 n, channel k-l-m. This alarm can be detected by the above units when the AU-4 is demultiplexed at lower levels. Action: 1.


TUy: n-k-l-m DEG Severity: NOT URGENT Detected on TUy Rx block of the STM-N, NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is an indication of a bit error rate e from 10-5 to 10-9 (threshold presettable via software) on the received low level payload (check performed by BIP-8 on B3 byte for the TU-3 or by BIP-2 on V5 byte for the TU-2 and TU-12) on port n or AU-4 n, channel k-l-m. This alarm can be detected by the above units when the AU-4 is demultiplexed at lower level and the TU is terminated to a stream with SNC Protection. Action: 1. Check if the same alarm is detected at the termination of the path. If the ALARM DETECTED, proceed as indicated in: Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG) 1. Check if the same alarm is detected at the termination of the path. If the ALARM NOT DETECTED, proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

TUy: n-k-l-m EXC Severity: URGENT Detected on TUy Rx block of the STM-N, NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This is an indication of a bit error rate e³10-3 on the received low level payload (check performed by BIP-8 on B3 byte for the TU-3 or by BIP-2 on V5 byte for the TU-2 and TU-12) on port n or AU-4 n, channel k-l-m. This alarm can be detected by the above units when the AU-4 is demultiplexed at lower level and the TU is terminated to a stream with SNC Protection. Action: 1. Check if the same alarm is detected at the termination of the path. If the ALARM DETECTED, proceed as indicated in: Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG)


339-1268/06

.

Navigation Page

293

Book Contents


2. Check if the same alarm is detected at the termination of the path. If the ALARM NOT DETECTED, proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

TUy: n-k-l-m LOP Severity: URGENT Detected on TUy Rx block of the STM-N, NxSTM-1 units (or Nx140/155Mbit/s units set as SDH interfaces). This alarm indicates the Loss Of Pointer of the Tributary Unit on port n or VC-4 n, channel k-l-m. This alarm can be detected by the above units when the AU-4 is demultiplexed at lower level. Problem: 1.


2.


Tx Fail Severity: URGENT Detected on the Tx block of the STM-N and NxSTM-1 Optical units, Preamplifier and Booster Unit. This alarm indicates failure of the laser module. Problem: 1.


1.


Unit Fail Severity: URGENT Detected on the INT block of all the units excepted for the Communication and Control Unit. This alarm indicates an unit internal failure. Problem: 1.


1.


Unit Type Mismatch Severity: NOT URGENT Detected on: all the units excepted for the Communication and Control Unit.


339-1268/06

.

Navigation Page

294

Book Contents


This alarm indicates mismatch between the database unit type commission and the unit inserted. Problem: 1.

Wrong peripheral unit inserted or wrong equipment configuration Action:

1. Check the configuration and the inserted unit, replace the unit or change the database according to the required configuration

VC4: n DEG Severity: NOT URGENT Detected on the VC-4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as PDH interface). This alarm can be detected by the STM-N Unit, NxSTM-1 units and Nx140/155Mbit/s units set as SDH interfaces when the AU-4 is demultiplexed at lower levels and the monitoring is active. This is an indication of a bit error rate from e³10-5 to e³10-9 (threshold presettable via Software) on the received high level payload (check performed by BIP-8 on B3 byte) on port n or VC-4 n. Problem: 1.


2.



VC4: n EXC Severity: URGENT Detected on the VC-4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as PDH interface). This alarm can be detected by the STM-N Unit, NxSTM-1 units and Nx140/155Mbit/s units set as SDH interfaces when the AU-4 is demultiplexed at lower levels and the monitoring is active. This is an indication of a bit error rate e³10-3 on the received high or low level payload (check on B3 byte) on port n or VC-4 n. Problem: 1.

Excessive degradation of the optical fibre Coupling attenuation


339-1268/06

.

Navigation Page

295

Book Contents


Failure on the far-end transmitter 2.



VC4: n LOM Severity: URGENT Detected on the VC-4 Rx block of the following units: STM-4 Optical/Mux Unit, 2xSTM-1 Optical/Mux Unit, STM-1 Optical/Mux Unit, STM-1 Electrical/Mux Unit, 2x140/155Mbit/s (VC-12) Tributary Unit, and 1x140/155Mbit/s (VC-12) Tributary Unit (when the last two units are set as SDH interfaces). Detected on the VC-4 Tx block of the following units: 2x140/155Mbit/s (VC-4) Tributary Unit, 2x140/155Mbit/s (VC-12) Tributary Unit, and 1x140/155Mbit/s (VC-12) Tributary Unit (when the last three units are set as PDH interfaces). This alarm indicates the Loss Of Multi-frame (byte H4) of the TU-2 and TU-12 levels on port n or VC-4 n. This alarm can be detected by the STM-4 Optical/Mux Unit, 2xSTM-1 Optical/Mux Unit, STM-1 Optical/Mux Unit and STM-1 Electrical/Mux Unit, 2x140/155Mbit/s (VC-12) Tributary Unit, and 1x140/155Mbit/s (VC-12) Tributary Unit (when the last two units are set as SDH interfaces) when the AU-4 is demultiplexed at TU-2 and TU-12 levels and the monitoring is active. Action: 1.


VC4: n PLM Severity: URGENT Detected on the VC-4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as PDH interface). This alarm can be detected by the STM-N Unit, NxSTM-1 units and Nx140/155Mbit/s units set as SDH interfaces when the AU-4 is demultiplexed at lower levels and the monitoring is active. This is an indication of a mismatch between the received and expected Payload Label value (C2 byte) on port n. Problem: 1.

Local and destination equipment has been configured with a different Payload Label Action:


339-1268/06

.

Navigation Page

296

Book Contents


1. Check the local and destination C2 byte configuration and the status of the intermediate Digital Cross-connector Equipment

VC4: n RDI Severity: INDICATIVE Detected on the VC4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as PDH interface). This alarm can be detected by the STM-N Unit, NxSTM-1 units and Nx140/155Mbit/s units set as SDH interfaces when the AU-4 is demultiplexed at lower levels and the monitoring is active. This is a High Order Remote Defect Indication on port n received from the remote multiplexer. It indicates that the far-end port has detected some problems into the received stream. Problem: 1.

Consequence of the alarms AU4: n AIS VC4: n EXC VC4: n PLM VC4: n TIM VC4: n UNEQ Action:

1. Check the status of the far-end port and follow the trouble-shooting procedure for the detected alarm

VC4: n TIM Severity: URGENT Detected on the VC4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as PDH interface). This alarm can be detected by the STM-N Unit, NxSTM-1 units and Nx140/155Mbit/s units set as SDH interfaces when the AU-4 is demultiplexed at lower levels and the monitoring is active. This is an indication of a mismatch between the received and expected J1 Trace Identifier on port n. Problem: 1. Transmitter on the far-end equipment configure with a different path trace identifier from the expected one Action: 1. Check, using the Software, that the remote transmitted J1 is configured as the local expected one

VC4: n UNEQ Severity: URGENT Detected on the VC4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as PDH interface).


339-1268/06

.

Navigation Page

297

Book Contents


This alarm can be detected by the STM-N Unit, NxSTM-1 units and Nx140/155Mbit/s units set as SDH interfaces when the AU-4 is demultiplexed at lower levels and the monitoring is active. The UNEQUIPPED indicates that in the far-end equipment the VC4 on port n is not connected. The unexpected reception of VC4 unequipped indicates that a connection error has occurred on the path. Action: 1.

Check the cross connection in the remote equipment

VCy: n DEG Severity: NOT URGENT Detected on the VCy Tx block for the following units: (16+16)x1.5/2Mbit/s Tributary Unit, 32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit and 3x45Mbit/s Tributary Unit. This is an indication of a bit error rate from e³10-5 to e³10-9 (threshold presettable via software) on the received high or low level payload (check performed by BIP-8 on B3 byte for the VC-3 or by BIP2 on V5 byte for the VC-12) on port n. Problem: 1.


2.


1. Check if the same alarm is detected at the termination of the path. If ALARM DETECTED, proceed as indicated in: Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG) 2. Check if the same alarm is detected at the termination of the path. If ALARM NOT DETECTED, proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

VCy: n EXC Severity: URGENT Detected on the VCy Tx block for the following units: (16+16)x1.5/2Mbit/s Tributary Unit, 32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit and 3x45Mbit/s Tributary Unit. This is an indication of a bit error rate e³10-3 on the received high or low level payload (check performed by BIP-8 on B3 byte for the VC-3 or by BIP-2 on V5 byte for the VC-12) on port n. Problem: 1.



339-1268/06

.

Navigation Page

298

Book Contents


2.


1. Check if the same alarm is detected at the termination of the path. If ALARM DETECTED, proceed as indicated in: Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG) 2. Check if the same alarm is detected at the termination of the path. If ALARM NOT DETECTED, proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

VCy: n PLM Severity: URGENT Detected on the VCy Tx block for the following units: (16+16)x1.5/2Mbit/s Tributary Unit, 32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit and 3x45Mbit/s Tributary Unit. This is an indication of a mismatch between the received and expected Payload Label Message (C2 byte for the VC-3 or bit 5, 6 and 7 of V5 byte for the VC-12) on port n. Problem: 1.

Local and destination equipment has been configured with a different Payload Label Action:

1. Check the local and destination C2 or V5 byte configuration and the status of the intermediate Digital Cross connector Equipment

VCy: n RDI Severity: INDICATIVE Detected on the VCy Tx block for the following units: (16+16)x1.5/2Mbit/s Tributary Unit, 32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit and 3x45Mbit/s Tributary Unit. This is a High or Low Order Remote Defect Indication (bit n. 5 in G1 byte for the VC-3 or bit n.8 in V5 byte for the VC-12) on port n received from the remote multiplexer. It indicates that the far-end port has detected some problems into the received stream. Problem: 1.

Consequence of the alarms: TUy: n-k-l-m LOP TUy: n-k-l-m AIS VCy: n EXC VCy: n PLM VCy: n TIM VCy: n UNEQ Action:


339-1268/06

.

Navigation Page

299

Book Contents


1. Check the status of the far-end port and follow the trouble-shooting procedure for the detected alarm

VCy: n TIM Severity: URGENT Detected on the VCy Tx block for the following units: (16+16)x1.5/2Mbit/s Tributary Unit, 32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit and 3x45Mbit/s Tributary Unit. This is an indication of a mismatch between the received and expected Trace Identifier (byte J1 for the VC-3 or J2 for the VC-12) on port n. Problem: 1. Transmitter of the far-end equipment configured with a different path trace identifier from the expected one Action: 1. Check, using the Control Application, that the remote transmitted J1 or J2 is configured as the local expected one

VCy: n UNEQ Severity: URGENT Detected on the VCy Tx block for the following units: (16+16)x1.5/2Mbit/s Tributary Unit, 32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit and 3x45Mbit/s Tributary Unit. The UNEQUIPPED indicates that the virtual container on port n is not connected, via switching matrix, to any source point. The unexpected reception of VC unequipped indicates that a connection error has occurred on the path. Action: 1.

Check the cross connection in local and remote equipment

Wavelength drift Severity: URGENT Detected on Tx block of the STM-16 WDM Optical/Mux Unit. The wavelength stabilisation loop is out of control. Action: 1.

Follow: Unit Internal Fault Trouble-Shooting Procedure

Wavelengthmis_LaserOff Severity: INDICATIVE Detected on the INT block of the STM-64 G.709 Units.


339-1268/06

.

Navigation Page

300

Book Contents


This alarm indicates the wavelength configured in the database is not present in the set of configurable wavelengths for the unit inserted. The unit will not be configured and the laser will remain OFF. Problem: 1. Wrong unit fitted or wrong database configuration Action: 1. Check the kind of unit fitted or check if the kind of unit configured in the database is right

COMMON PROCEDURES Unit Internal Fault Trouble-Shooting Procedure When a unit internal fault condition is detected proceed in the following way: 1. Using the Software select from the main menu the option Unit Reset and perform a Software reset for the relevant unit. If the alarm condition remains active: 2.

Perform a unit hardware reset (pull out and re-insert the faulty unit).

If the alarm condition remains active: 3.

Replace the unit.

PDH LOS Fault Trouble-Shooting Procedure 1.

Disconnect the Tx and Rx connectors.

2.

Loop output with input using a coaxial cable.

3. If the alarm goes OFF, the problem is a consequence of far-end equipment transmitter failure; check the status of the far-end equipment. 4.

If the alarm is still ON, the problem is an unit internal failure; proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

SDH LOS Fault Trouble-Shooting Procedure 1.

Disconnect the Tx and Rx connectors.

If the unit is optical: 2. Loop output with input using an optical fibre patch-cord (set an optical attenuator, with a proper dB value, when the Tx power overtakes the minimum overload of the Rx side as reported in the Optical Performances Chapter in the Technical Specifications Section of the Equipment Manual. 3. Restart the laser (this operation is not necessary when the Automatic Laser Shutdown is permanently disabled). If the unit is electrical: 4.

Loop output with input using a coaxial cable

For both optical and electrical unit: 5. If the alarm is OFF, the problem is consequence of far-end equipment transmitter failure; check the status of the far-end equipment. 6.

If the alarm is ON, the problem is due to an unit internal failure; proceed as indicated in:


339-1268/06

.

Navigation Page

301

Book Contents


Unit Internal Fault Trouble-Shooting Procedure

Preamplifier and Booster LOS Fault Trouble-Shooting Procedure 1.

Disconnect the Rx cable.

2.

Connect an optical power meter to the Rx cable.

3. Restart the laser on the optical STM-N unit by pressing the front panel push-button or via Software procedure (this procedure is not necessary if the Automatic Laser Shutdown is permanently disabled). 4.

Check the received power.

In case of Preamplifier: 5. 6.

If the received power is less than -48dBm: problem on the line or remote equipment. If the received power is greater than -48dBm; proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

In case of Booster: 5. If the received power is less than -15dBm: problem on the optical connection path cord on the local STM-N transmitter. 6.

Check the status of the optical path cord and the STM-N Optical Mux/Unit.

7. If the received power is greater than -15dBm: Booster internal failure; proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

Bit Error Rate on the STM-N Optical Signal (MS-EXC/DEG and RSEXC/DEG) IMPORTANT The following procedure will set out of service the line traffic. Proceed therefore only if it is actually necessary or if the traffic is protected. 1. Disconnect the Tx and Rx connectors, loop output with input using an optical fibre patchcord (set an optical attenuator with a proper dB value, when the Tx power overtakes the minimum overload of the Rx side as reported in the Optical Performances Chapter in the Technical Specifications Section of the Equipment Manual. 2. Restart the laser by pressing the front panel push-button or via Software procedure (this procedure is not necessary if the Automatic Laser Shutdown is permanently disabled). 3.

If the alarm stays ON, proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

4.

If the alarm goes OFF, proceed with the next step.

5.

Remove the local loop and replace the previous connection.

6. In the remote equipment disconnect the Tx and Rx connectors and loop the line towards the local equipment. Restart the local laser. 7.

If the alarm goes OFF, the problem is due to a fault in the far-end equipment.

8.

If the alarm stays ON, proceed with the next step.

9.

In the local equipment disconnect the Tx and Rx optical fibre cables.

10. Using an optical fibre patch-cord connect the Tx side of the STM-n Optical/Mux Unit to the Rx side of an optical adjustable attenuator.


339-1268/06

.

Navigation Page

302

Book Contents


11. Force the laser on (Manual Restart for Test) by pressing the front panel push-button for 12 seconds or via Software procedure (this procedure is not necessary if the Automatic Laser Shutdown is permanently disabled). 12. Set the attenuator to measure on its Tx side an optical power according to the tables reported in the Optical Performances Chapter in the Technical Specifications Section of the Equipment Manual. 13. Using a proper optical cable connect the Tx side of the attenuator with the Rx side of the STM-N Optical/Mux Unit. 14. Restart the laser by pressing the front panel push-button or via Software procedure (this procedure is not necessary if the Automatic Laser Shutdown is permanently disabled). 15.


16. If the alarm goes OFF, the problem is caused by an excessive degradation of the optical fibre or by a failure of the far-end transmitter; proceed with the next step. 17. Check if the received optical power is between the values according to the tables reported in the Optical Performances Chapter in the Technical Specifications Section of the Equipment Manual For measuring the received optical power, the Automatic Laser Shutdown in the remote equipment must be disabled. 18.

If the measured value is between the range, proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

19.

If the measured value is out of the range, proceed with the next step.

20. Check if the measured value is below the minimum sensitivity or above the minimum overload of the tables. 21. If the measured value is below the Minimum Sensitivity, probable signal attenuation is due to poor connector coupling or to the optical fibre line or faulty far-end equipment. 22. If the measured value is above the Minimum Overload, optical power transmitted from the far-end equipment is higher than the acceptable one or faulty optical output power regulation loop on the far-end transmitter

Bit Error Rate on the PDH and STM-1 Electrical Signal (PDH EXC/DEG and MS EXC/DEG) IMPORTANT The following procedure will set the line traffic out of service. Proceed therefore only if it is actually necessary or if the traffic is protected. 1. 2.

Disconnect the Tx and Rx connectors, loop output with input using a proper cable. If the alarm stays ON, proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

3.

If the alarm goes OFF, proceed with the next step.

4.

Remove the local loop and replace the previous connection.

5. In the remote equipment disconnect the Tx and Rx connectors and loop the line towards the local equipment. 6.

If the alarm goes OFF, the problem is due to a failure in the far-end equipment.


339-1268/06

.

Navigation Page

303

Book Contents


7.

If the alarm stays ON, the problem is on the connectors or on the coaxial cable.

Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG) IMPORTANT The following step will set out of service the VC. Proceed therefore only if it is actually necessary or if the traffic is protected. 1. Delete on the far-end equipment where the path is terminated the VC connection and create a loop on the STM-N Interface on the alarmed VC. 2.

If the alarm goes OFF, the problem is due to a failure in the far-end equipment.

3.

If the alarm stays ON, proceed with the next step.

IMPORTANT The following procedure will put the line traffic out of service. Proceed therefore only if it is actually necessary or if the traffic is protected. 4. Disconnect the Tx and Rx connectors, loop output with input using a proper cable (set an optical attenuator, with a proper dB value, when the Tx power overtakes the minimum overload of the Rx side as reported in the Optical Performances Chapter in the Technical Specifications Section of the Equipment Manual) and restart the laser (this procedure is not necessary if the Automatic Laser Shutdown is permanently disabled). If the unit is electrical: 5.

Loop output with input using a coaxial cable

For both optical and electrical unit: 6.


7. If the alarm goes OFF, the problem is due to a degradation of the optical/electrical power, problems in connectors coupling or failure in transit equipment; check the connections and the status of the transit equipment.

Input Ground Contact Detected on: Communication and Control Unit In the Communication and Control Unit are displayed the alarm names relevant to the input ground contacts. The equipment can manage up to four input ground contacts, in the following list are reported some of the default alarm names: General Supply Fail DC/DC 1 Fault DC/DC 2 Fault Fan Assy Absent High Temperature When one is detected, it indicates that a ground criteria is incoming from the exchange. Action: 1.

Proceed with the appropriate maintenance procedure of the relevant device


339-1268/06

.

Navigation Page

304

Book Contents


EQUIPMENT EVENTS This paragraph describes the format of the protection switch report messages in the CA Alarm and Management window. The Control Application manages the switch report of the following types of protections: n Internal Synchronism Protection (Int Sync) n External Synchronism Protection (Ext Sync) n Equipment Protection (Equip) n MS Protection (MSP) n MS SPRING Protection (Bshr) The operator can start the report using a configuration window and can configure the colours used to show the report.

Messages Format: The information reported in the alarms list are the following: n Date: date; n Time: event time; n Slot: position of the involved unit; n Source: entity which causes the event; n Unit: unit type and involved port; n Severity: event category; n Alarm Cause: event cause.

The Severity field is always null for protection switches. The essential information are concentrated in the Alarm Cause field; they are divided in 3 parts: n the unit status in the protection; n the involved group protection; n the service status of the unit involved in the protection. The contents are indicated in the chapters in which the different protection types are managed.


339-1268/06

.

Navigation Page

305

Book Contents


Synchronism Status Changes: These changes notify the switches of synchronism protection group.

The involved fields are Source, that indicates the involved port or the source, Unit, that indicates the involved unit type and Alarm Cause. This field gives three different information: * The protection source status, that can be: "No request" Available, not active "Auto switch" Active synchronism source "Manual switch" Active, selected with manual switch "Forced switch" Active, selected with forced switch "Lockout” Not included in protection "Failed" Signal not present or not suitable for synchronism "WTR" Input signal waiting for restoration "OOF" Input signal out of frequency limits "Forced & Failed" Selected with forced switch with failed input "Forced & OOF" Selected with forced switch with out of frequency signal "Forced & WTR" Selected with forced switch waiting for restoration

* The involved group of synchronism, that can be: (Int Sync) Equipment internal Synchronism (Ext Sync) Unique Group External Synchronism (old type switch) (Ext Sync(T41)) First Group External Synchronism (new type switch)


339-1268/06

.

Navigation Page

306

Book Contents


(Ext Sync(T42)) Second Group External Synchronism (new type switch)

* The indication of active source, that can be: * (asterisk) The source is selected as the actual synchronisation source S Only for External Sync. It indicates that the protection is squelched (no output signal)

Equipment Protection Status Changes: These changes indicate the switches of equipment protection group.

The involved fields are Unit, that indicates the involved unit type and Alarm Cause. This field gives three different information: * The Protection status, that can be: "No request" Normal Status of the not switched protection "Auto switch" The protection has switched "Do not revert" Switched without restoration "Auto switch pending" Failed switching "Manual switch" Manual switch "Forced switch” Forced switch "Lockout" Card not included in protection "Wait to restore" Waiting for restoration

* The Protection type: it always indicates (Equip). * The indication of active source, that can be: * (asterisk) The card is in service


339-1268/06

.

Navigation Page

307

Book Contents


MSP Status Changes: These changes indicate the switches of MSP line protection groups.

The involved fields are Source, that indicates the involved port (MS), Unit, that indicates the involved unit type and Alarm Cause. This field gives three different information: * The Protection status, that can be: "No request" Normal Status of the not switched protection "Auto Switch (SF)" Switched for failure of protected line "Auto Switch (DEG)" Switched for degrade of protected line "Do not revert" Switched without restoration "SF Switch Pend" Failed switch with signal loss "DEG Switch Pend" Failed switch with signal degrade "Manual switch” Manual Switch "Forced switch" Forced Switch "Failed" Failed Protection "Lockout" Card not included in protection "Wait to restore" Waiting for restoration

* The Protection type: it always indicates (MSP) * The indication of active source, that can be: * (asterisk) The involved port is in service


339-1268/06

.

Navigation Page

308

Book Contents


MS-SPRING Status Changes: These changes indicate the switches of the MS-SPRING protection groups.

The involved fields are Unit, that indicates the involved unit type and Alarm Cause. This field gives two different information: the Protection Status and the Protection Type. Besides the switches of the two protection sub-parts are reported: (Bshr Sc) Protection Status (Bshr Ring) Ring side The reported status are the following: * Protection Status (Bshr Sc): “Idle" Normal condition; actual protection not active "Full Passthrough" There is a protection ring switch in other nodes of the ring; the traffic switches on protection channels “K bytes Passthrough" There was a span switch on the ring or a failed protection; this node doesn’t switch and doesn’t squelch extra-traffic "Bridged-Switched" Node switch and traffic on protection (different if the type is span or ring)

"Isolated Node" Double fault on the two ring group and loss of communication with the other parts of the ring. If the node is passing-through there is no traffic loss "Rule S4B" Not switched protection because of a the presence of ring fault of the same priority on the ring nodes (ES: double ring SD or double MANUAL RING); this situation doesn’t allow to restore the faults on not adjacent nodes "Drop Br Sw" Protection failure; in case of failure on protected cards the traffic will be lost

* Ring side (Bshr Ring): "No request" Normal Status of the not switched protection "Auto Switch (SF)" Switched for failure of protected line


339-1268/06

.

Navigation Page

309

Book Contents


"Auto Switch (DEG)" Switched for degrade of protected line "SF Switch Pend" Failed switch with signal loss "DEG Switch Pend" Failed switch with signal degrade "Manual switch" Manual Switch "Forced switch" Forced Switch "Lockout Working" The indicated side is not included in protection "Wait to restore" Protection waiting restoration

8XFAST ETHERNET UNIT ALARMS In the following all the alarms involved on the 8xFast Ethernet Unit are described.

Ethernet Port Alarms In the following all the alarms relevant to the Eth port (Ethernet Signal Physical Interface) are reported.

Los

(Ethernet Port)

Severity: URGENT Loss of signal relevant to the Rx side of the port. Problem: 1. Consequence of a line loopback. 2. Consequence of far-end equipment transmitter failure or line interruption 3. Unit Internal Failure Action: 1. Remove, if necessary, the line loopback 2. Disconnect the Tx and Rx connectors and loop output to input using a test patch cord. If the alarm goes OFF, check the status of the far-end equipment and the line. 3. Disconnect the Tx and Rx connectors and loop output to input using a test patch cord. If the alarm stays ON, proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

TxFail

(Ethernet Port)

Severity: URGENT Failure of the transmission section. Problem: 1. Unit internal failure. Action: 1. Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure


339-1268/06

.

Navigation Page

310

Book Contents


EthernetLink Down

(Ethernet Port)

Severity: URGENT Ethernet Link Down: This alarm indicates that the unit has not received idle signal for 200ms. Problem: 1. Possible problem in the auto-negotiation process 2. Failure on the far-end transmitter or problem in the line 3. Internal failure on the local or far-end protection Line Unit Action: 1. Disable the auto-negotiation process, if the alarm does not go off check the causes 2. Check the status of the far-end transmitter and the line 3. Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

PlugModuleMissing

(Ethernet Port)

Severity: URGENT Module Missing: This alarm indicates that a pluggable module of the 8XFast Ethernet Unit, configured into the database, it is not inserted. Problem: 1. Plug Module not fitted 2. Problems with the insertion of the module Action: 1. Insert the missing pluggable module. 2. Check if the module is right fitted in the unit.

wrongPortConfiguration

(Ethernet Port)

Severity: URGENT This alarm indicates mismatch between the port type configured via software and the port fitted on the unit. Problem: 1. An electrical port is configured instead of an optical one or vice versa. Action: 1. Check the configuration and the inserted unit, replace the unit or change the database according to the required configuration.

VCG Alarms In the following all the alarms relevant to the VCG (Virtual Container Group) are reported.

R-LOA

(VCG)

Severity: URGENT Recoverable - Loss of Alignment: It is detected if the alignment process cannot perform the alignment of the individual VC-nv to a common Multiframe start. The alignment process is performed by means of a signal buffering that allows the accommodation of a Xms differential delay between the VC-n of reference and any other VC-n-v in the same Multiframe.


339-1268/06

.

Navigation Page

311

Book Contents


Problem: 1. The value set with manual method is inadequate to recover the differential delay but the buffer overflow is recoverable with the auto-adaptive method. Action: 1. Try to set the Adaptive option in the delay value configuration.

RS-ACKPending

(VCG)

Severity: INDICATIVE Problem: 1. In a virtual connection on or more VC12s or VC3s has been inserted in a wrong position and consequently it are not received into the expected position. Action: 1. Check the cross connections.

GIDMismatch

(VCG)

Severity: URGENT Problem: 1. This alarm indicates that the received GID of a VCG member is not equal to the GID of the first VCG member. Action: 1. Check the cross-connection configuration on the near-end and far end equipment.

VC-n Alarms In the following all the alarms relevant to the VC-n channels are reported.

DEG

(VC-n)

Severity:NOT URGENT This is an indication of a bit error rate from e³10-9 to e³10-5 (threshold configurable via Software) on the received high level payload (check performed by BIP-8 on B3 byte or by BIP-2 on B2 byte) on port n. Problem: 1. Excessive degradation of the optical fibre Coupling attenuation Failure on the far-end transmitter Unit internal failure Action: 1. Check if the same alarm is detected at the termination of the path. If the alarm is NOT DETECTED, proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

RDI

(VC-n)

Severity:INDICATION Remote Defect Indication


339-1268/06

.

Navigation Page

312

Book Contents


Problem: 1. Consequence of the following alarms detected on the receive side of the far-end multiplexer: AU-AIS VCn EBER VCn: x PLM VCn TIM VCn Unequipped Action: 1. Check the status of the far-end port and follow the trouble shooting procedure for the detected alarm

PLM

(VC-n)

Severity:URGENT Payload Label Mismatch Problem: 1. Local and far-end equipments has been configured with a different Payload Label Action: 1. Check the local and destination C2 byte configuration and the status of the intermediate Digital Cross-Connect equipment.

EXC

(VC-n)

Severity:URGENT This is an indication of a bit error rate e³10-3 on the received high or low level payload (check on B3/B8 byte) on port n. Problem: 1. Excessive degradation of the optical fibre Coupling attenuation Failure on the far-end transmitter Unit internal failure Action: 1. Check if the same alarm is detected at the termination of the path. If the alarm is NOT DETECTED, proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

TIM

(VC-n)

Severity: URGENT Trace Identifier Mismatch: This is an indication of a mismatch between the received and expected J1/J2 Trace Identifier for VC-4/(VC-3 and VC-12) on port n. Problem: 1. Transmitter on the far-end Equipment is configured with a different path trace identifier from the expected one. Action:


339-1268/06

.

Navigation Page

313

Book Contents


1. Check, using the Software, that the remote transmitted J1/J2 is configured as the local expected one.

dLossOfMultiframe

(VC-n)

Severity: URGENT Problem: 1. This alarm indicates a loss of multiframe alignment word detected on port n. Action: 1. Check the status of the far-end transmitter and the line

excCRCErrors

(VC-n)

Severity: URGENT Excessive CRC ErrorS: This alarm indicates an excessive consecutive detection of the number of CRC errors. This value is settable via LCT. Problem: 1. Excessive degradation of the optical link 2. Coupling attenuation 3. Failure on the far-end transmitter 4. Unit internal failure Action: 1. Check the fibre status 2. Check the presence of optical attenuator 3. Check the far-end transmitter 4. Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure

UNEQ

(VC-n)

Severity: URGENT The UNEQUIPPED indicates that in the far-end Equipment the VC-n is not connected. Problem: 1. The unexpected reception of VC-n unequipped indicates that a connection error has occurred on the path. Action: 1. Check the local and destination C2 for VC-4 and V5 byte for VC-3/VC-12 configuration and the status of the intermediate Digital Cross-Connect Equipment.


339-1268/06

.

Navigation Page

314

Book Contents

ERROR MESSAGES These messages are managed by the Control Application and are displayed on the user interface by means of dialogue boxes.

INVALID INI FILE Invalid initialisation ADM file.

WRONG IDM Unrecognised Message Identification. Protocol error: unknown command or missing message.

ENABLE SWITCH UNIT FIRST! Switch unit must be configured before proceeding.

DISABLE PATH PROTECTION FIRST! A path protection is present. Disable it before proceeding (i.e.: deletion of path protected cross connection).

INVALID FILE Invalid format or name of download.ini or of files related to it.

IT'S IMPOSSIBLE TO DELETE THE UNIT. IT'S SYNCHRONISATION SOURCE A unit used as synchronisation source can not be deleted.

IT'S IMPOSSIBLE TO DELETE THE UNIT. DCC ACTIVE The units with DCC channel enabled can not be deleted.

CANNOT DELETE UNIT: USED IN BSHR PROTECTION A unit involved in MS-SPRing protection can’t be deleted.

CANNOT DELETE MATRIX: EQUIPMENT PROTECTION IN MANUAL/FORCED/LOCKOUT A matrix in service for a Manual/Forced/Lockout switch can’t be deleted.

CANNOT DELETE UNIT: USED IN MSP PROTECTION The selected unit is involved in a MSP. Disable MSP before deleting it.

CANNOT DELETE UNIT: USED IN EQUIPMENT PROTECTION The selected unit is involved in Equipment protection. Disable the equipment protection before deleting it.

MODULE VERSION JUST UPDATE Software version has been already loaded on the unit flash bank.


339-1268/06

.

Navigation Page

Book Contents

MSHXXX - OPERATOR’S HANDBOOK ERROR MESSAGES

WRONG SERVER! Control Application version or type mismatch.

BOOT/ACTIVE VERSION MISMATCH. COMMIT REQUIRED! There is a mismatch between boot and active software version. It’s necessary to execute a software commit.

SOFTWARE VERSION JUST PRESENT! The equipment software version has been already downloaded.

SOFTWARE MODULE NOT SELECTED A software module must be selected before proceeding.

UNIT TYPE NOT PRESENT The selected unit type isn’t present.

CODE FILE NOT FOUND! The code file isn’t present in the archive.

ERROR READING CODE FILE Problems in reading file operation (corrupted file or software problem on the PC side) during a module download. Download failed.

ERROR STORING RECORD DATA Problems in writing file on the equipment side. Download failed.

WRONG RECORD SEQUENCE NUMBER Wrong sequence during the software download. Download failed.

TIME OUT ON REPLY File transfer expired due to a time-out during the software download.

STAND-BY VERSION UNAVAILABLE The operator tried to execute a bank switch but no valid software version is present in the stand-by bank.

OPERATION NOT ALLOWED Operation not possible. Check the current configuration.

COMMIT FAILED! A commit operation failed.

DEMULTIPLEXING UNAVAILABLE! It is impossible to demultiplex the selected stream. Check the unit type or the unit setting.


339-1268/06

.

Navigation Page

317

Book Contents


INPUT DATA MISSING Some mandatory data have not been inserted (i.e.: User or Password not specified).

WRONG DATA The inserted data are wrong or out of range.

OUTPUT DATA MISSING The output data are not complete.

TIME OUT The time necessary to complete the operation is expired.

INSUFFICIENT PRIVILEGE A superior privilege is needed (i.e.: a read only user can not modify the configuration).

OUT OF SEQUENCE COMMAND The command is not available for the current configuration.

UNDEFINED ERROR The error type is not present in the archive.

NOT LOGGED IN The Control Application is not connected.

OPERATION FAILURE The Communication and Control Unit tells the operator that an operation mismatch occurred.

IF CONFIGURATION PERFORMED DURING MAINTENANCE STATE IS DIFFERENT FROM THE PREVIOUS ONE, A SYSTEM RESTART MAY BE NECESSARY IN ORDER TO CORRECTLY ACTIVATE THE NEW SETTINGS OVER THE TRAFFIC UNITS Procedure of changing configuration during maintenance state.

“DATA” OUT OF BOUNDS MIN=”MIN” MAX=”MAX” The inserted data is too large or too short.

"DATA” IS AN INVALID NUMERIC FORMAT The inserted data type isn’t recognised.

OPERATION ABORTED The operation has been interrupted.

MISSING INPUT DATA The inserted data are not complete.


339-1268/06

.

Navigation Page

318

Book Contents


MISSING OUTPUT DATA The output data are not complete.

NOT IMPLEMENTED The feature isn’t yet available.

TIMEOUT EXPIRED The time spent for the operation is too long.

PROTOCOL ERROR The used protocol isn’t suitable with the operation (i.e.: channels involved in SNCP/N - Not Intrusive switching criteria - are not monitored).

NO PRIVILEGE The operator has no privileges for the current operation.

OUT OF SEQUENCE There was a problem in data sequence.

INVALID OPERATION The operation isn’t permitted.

FAILURE : LOGICAL PROBLEM The requested action can not be performed because it presents a logical error (i.e.: cross connection on a channel that is already busy or with a wrong traffic type).

FAILURE : PHYSICAL PROBLEM The requested action can not be performed because the involved "physical object" is not available (i.e.: cross connection on a "missing" channel).

FAILURE : XCONN/PATH/MSP/AUX CONN PRESENT The requested action can not be performed: cross connection, SNC/MS Protection or Auxiliary connection have been found on the selected unit/port/channel (Deletion).

FAILURE : ACTIVE PERFORMANCES FOUND ON PORT The requested action can not be performed: an active performance monitoring has been found on the selected port (Deletion).

FAILURE : UNKNOWN CODE The used code type is unknown.

PASSWORD CHECK FAILURE : PLEASE RE-ENTER Error in the confirmation of the new password (change password).


339-1268/06

.

Navigation Page

319

Book Contents


REMOTE CONNECTION DOWN: DISCONNECT FROM LC AND WAIT 2 MINUTES. THEN LOGIN AGAIN. Disable the local connection before performing a remote connection.

DISCONNECT FROM EQUIPMENT BEFORE Disconnect from Control Application before setting serial unit parameters.

REMOTE CONNECTION FAILED. REMOTE LC UNREACHABLE The remote connection failed. There is a problem in the network or the remote LC isn’t connected.

REMOTE CONNECTION FAILED: ATTEMPTED REMOTE CONNECTION ON LOCAL SHELF The remote access on the local equipment via F interface failed. There is a problem in the network.

WRONG PASSWORD The operator must insert the correct password.

LOGIN FAILED: LC RETURNED CODE “CODE” Error in "Login" operation.

TWO CONNECTIONS ON THE SAME PORT AND SAME BYTE On the Auxiliary Unit, two connections on the same port and on the same byte aren’t allowed.

RINGMASTER NEED A CAI DESTINATION During the configuration of an Auxiliary Unit ring connection, the operator hasn’t specified a cai destination for the Ring Master.

TYPE CONNECTION ALREADY PRESENT ON THIS EOW An Auxiliary Unit ring connection has been already configured.

AUXILIARY UNIT OUT OR IN ERROR: OPERATION REJECTED. The operation can’t be performed because there are problems with the Auxiliary Unit (failure or missing).

CONNECTION ALREADY PRESENT ON SAME ASIC, MUST USE SAME EXTERNAL PORT The selected channel is already involved in another connection or is not available.

FAILURE : DCC CONNECTED FOUND OR AUXCON It is not possible to delete the Auxiliary Unit when the DCC channels are enabled or when an auxiliary cross connection is present.

GTP NOT AVAILABLE ON AU4 WITH MUX1 No group port operation is allowed on the selected AU-4 belonging to a MUX1 Unit.


339-1268/06

.

Navigation Page

320

Book Contents


UNIT IN EQUIPMENT PROTECTION: THIS UNIT IS IN STANDBY The requested switch operation can not be performed because the involved unit is in stand-by state.

CANNOT SWITCH ON: UNIT OUT OR FAILED It is not possible to perform a manual switch on a unit which is out or failed.

CANNOT LOCKOUT PROTECTING: ONE O MORE UNIT OUT OR IN FAIL STATE The protection unit can not be "locked" because it is "in service" state.

MANUAL COMMAND ACTIVE ON THIS PROTECTION: RELEASE IT BEFORE DISMISS Disable manual commands before deleting the protection.

“UNIT” NOT SUPPORTED FOR UNITS PROTECTION The Unit Protection can not be performed on the selected unit (due to its position or type).

NO EQUIPMENT AVAILABLE FOR EQUIPMENT PROTECTION No card is available for equipment protection.

NO MS AVAILABLE FOR MSP No card is available for MSP.

MSP DELETION. ARE YOU SURE ? The operator has to confirm the MSP deletion.

COMMAND AVAILABLE ONLY ON PROTECTING The selected action can be performed only on protection unit/channel.

INVALID NODE The operator has set an incorrect node address value during a MS-SPRing configuration.

NODE ALREADY PRESENT In MS-SPRing configuration, the node identifier must be univocal.

INVALID NSAP ADDRESS LENGTH MIN 8 - MAX 20 DIGITS During a remote connection configuration, the operator has defined a too long or too short NSAP address value.

LAST DIGITS MUST BE 01 The NSAP address last digits must be 01.

UNKNOWN EQUIPMENT TYPE The Control Application doesn’t know the equipment type.


339-1268/06

.

Navigation Page

321

Book Contents


UNIT WITH MULTIPLIED PORT. DEMULTIPLY BEFORE BUILD SPRING PROTECTION Before building an MS-SPRing protection, demultiply the ports.

UNIT WITH GROUPED PORTS. UNGROUP IT BEFORE BUILD SPRING PROTECTION Before building an MS-SPRing protection, ungroup the ports.

UNIT WITH PORT CONNECTED ON SPRING PROTECTION SIDE. REMOVE IT BEFORE BUILD SPRING PROTECTION Before building an MS-SPRing protection, remove the connected ports.

UNIT WITH BROADCAST TYPE CONNECTIONS PRESENT. REMOVE IT BEFORE BUILD SPRING PROTECTION Before building an MS-SPRing protection, remove the broadcast cross connections.

RING NODES NOT CONFIGURED! During an MS-SPRing configuration, the ring node in the ring map list must be configured.

CANNOT BUILD BROADCAST CONNECTION WITH MORE THAN “N” LEGS The operator tried to build a broadcast cross connection with a number of legs greater than n = Max.

REACHED MAX MATRIX ALLOCATION FOR THIS POSITION! No more space for cross connections in matrix.

OUTPUT MESSAGE LENGTH TOO LONG Reduce output message length.

OUTPUT CODED MESSAGE LENGTH TOO LONG Needed to reduce output coded message length.

ERROR IN LINE “NUMLINE” : “STATEMENT” - “MESSAGE” Error message during the CDL file configuration. “Numline” indicates the line number in which there is the error; “statement” indicates the error cause and “message” is the error explanation.

ALREADY LOGGED-IN It is one possible “message” in the error message of CDL file. It indicates that the operator has attempted two consecutive connections.

INVALID TP TYPE It is one possible “message” in the error message of CDL file. It indicates that the Termination Point type isn’t present in the archive.


339-1268/06

.

Navigation Page

322

Book Contents


INVALID ATTRIBUTE ASSIGNMENT It is one possible “message” in the error message of CDL file. It indicates that the attribute isn’t suitable for the unit selected.

INVALID LOOP TYPE It is one possible “message” in the error message of CDL file. It indicates that the Loopback type isn’t suitable for the operation.

INVALID PAYLOAD TYPE It is one possible “message” in the error message of CDL file. It indicates that the payload type isn’t suitable for the operation.

INVALID KIND It is one possible “message” in the error message of CDL file. It indicates that the attribute kind isn’t suitable for the operation.

UNKNOWN ALARM CAUSE It is one possible “message” in the error message of CDL file. It indicates that an alarm occurred but is not possible to comprehend its cause.

INVALID ALARM TYPE It is one possible “message” in the error message of CDL file. It indicates that the alarm type is not present in the archive.

INVALID ALARM ASSIGNMENT It is one possible “message” in the error message of CDL file. It indicates that the alarm assignment is invalid.

ALARM NUMBER OUT OF RANGE It is one possible “message” in the error message of CDL file. It indicates that the alarm number is out of range.

INVALID KIND FOR SLOT: It is one possible “message” in the error message of CDL file. It indicates that the assignment is not suitable with the selected slot.

INVALID TIME FORMAT It is one possible “message” in the error message of CDL file. It indicates that the format time is incorrect.

INVALID SLOT NUMBER It is one possible “message” in the error message of CDL file. It indicates that the slot number is incorrect.


339-1268/06

.

Navigation Page

323

Book Contents


INVALID PORT STRING It is one possible “message” in the error message of CDL file. It indicates that the port string is incorrect.

INVALID EQUIPMENT It is one possible “message” in the error message of CDL file. It indicates that the equipment is not suitable for the network.

SLOT ALREADY EQUIPPED It is one possible “message” in the error message of CDL file. It indicates that the operator attempted to equip two consecutive slots.

OPERATION NOT AVAILABLE It is one possible “message” in the error message of CDL file. It indicates that the software useful for the operation wasn’t downloaded.

INVALID TP(S) It is one possible “message” in the error message of CDL file. It indicates that the TP(s) is incorrect.

INVALID FROM TP(S) It is one possible “message” in the error message of CDL file. It indicates that the FROM TP(s) is incorrect.

INVALID TO TP(S) It is one possible “message” in the error message of CDL file. It indicates that the TO TP(s) is incorrect.

INVALID PROT TP(S) It is one possible “message” in the error message of CDL file. It indicates that the PROT TP(s) is incorrect.

TP NOT CONNECTED It is one possible “message” in the error message of CDL file. It indicates that there are problems in TP connection or in the network.

UNDEFINED MSP PROTECTION It is one possible “message” in the error message of CDL file. It indicates that the operator tried to use a MSP protection that isn’t configured correctly.

INVALID INSTANCE It is one possible “message” in the error message of CDL file. It indicates that the instance is incorrect.

NO MANUAL COMMAND TO RELEASE It is one possible “message” in the error message of CDL file. It indicates that the operator wants to release a manual command that isn’t available.


339-1268/06

.

Navigation Page

324

Book Contents


INVALID SOURCE STATUS It is one possible “message” in the error message of CDL file. It indicates that the source status format isn’t recognised.

INVALID LEVEL It is one possible “message” in the error message of CDL file. It indicates that the multiplexing level is incorrect.

UNIT NOT SUPPORTING MULTIPLY It is one possible “message” in the error message of CDL file. It indicates that the multiply function is not available on the selected unit.

PORT NOT AVAILABLE It is one possible “message” in the error message of CDL file. It indicates that the selected port isn’t available for cross connections because it isn’t configured.

PORT CONNECTED OR GROUPED It is one possible “message” in the error message of CDL file. It indicates that the operator tried to connect or to group ports already connected or grouped.

WRONG TRAFFIC TYPE It is one possible “message” in the error message of CDL file. It indicates that the operation requires a not supported traffic type on the selected port.

PORT NOT MULTIPLIED It is one possible “message” in the error message of CDL file. It indicates that the operator tried to demultiply a not multiplied port .

INVALID SYNCHRONISATION SOURCE It is one possible “message” in the error message of CDL file. It indicates that the operator tried to use an invalid synchronisation source.

INVALID QUALITY LEVEL It is one possible “message” in the error message of CDL file. It indicates that the quality level (for example for the synchronisation source) is wrong.

INVALID SYNCHRONISATION GROUP It is one possible “message” in the error message of CDL file. It indicates that the synchronisation group is invalid.

CAN'T ADD HOLDOVER It is one possible “message” in the error message of CDL file. It indicates that for the synchronisation source the holdover function can’t be used.


339-1268/06

.

Navigation Page

325

Book Contents


CAN'T ADD SYSTEM It is one possible “message” in the error message of CDL file. It indicates that for the synchronisation source the system function can’t be used.

CAN'T DELETE HOLDOVER It is one possible “message” in the error message of CDL file. It indicates that for the synchronisation source the holdover function can’t be deleted.

CAN'T DELETE SYSTEM It is one possible “message” in the error message of CDL file. It indicates that for the synchronisation source the system function can’t be deleted.

SYNC SOURCE NOT CONFIGURED It is one possible “message” in the error message of CDL file. It indicates that for the selected synchronisation source was not previously configured.

INVALID SPRING TYPE It is one possible “message” in the error message of CDL file. It indicates that for the MS-SPRing type isn’t present in the archive.

MAXIMUM LABEL LENGTH IS 8 It is one possible “message” in the error message of CDL file. It indicates that the label used by the operator in the CDL file code is too long.

LABEL NOT DEFINED It is one possible “message” in the error message of CDL file. It indicates that the label used by the operator in the CDL file code isn’t defined.

CARD NOT EQUIPPED OR MISSING It is one possible “message” in the error message of CDL file. It indicates that a card is not absent or not equipped.

INVALID DCC TYPE It is one possible “message” in the error message of CDL file. It indicates that the DCC type isn’t present in the archive.

INVALID CARD TYPE OR PORT TYPE It is one possible “message” in the error message of CDL file. It indicates that the card or port type isn’t present in the archive.

INVALID CONNECTION TYPE It is one possible “message” in the error message of CDL file. It indicates that the connection type isn’t present in the archive.


339-1268/06

.

Navigation Page

326

Book Contents


UNEXPECTED TOKEN It is one possible “message” in the error message of CDL file. It indicates that the keyword in the code isn’t recognised.

INVALID VALUE IN CSES THRESHOLD It is one possible “message” in the error message of CDL file. It indicates that the CSES Threshold is incorrect.

INVALID VALUE IN ALARM THRESHOLD It is one possible “message” in the error message of CDL file. It indicates that the Alarm Threshold is incorrect.

PORT ALREADY MULTIPLIED It is one possible “message” in the error message of CDL file. It indicates that the selected port has been already multiplied.

INVALID SS BYTE It is one possible “message” in the error message of CDL file. It indicates that the SS byte must be configured as SDH or SONET.

SOCKET CALL FAILED There are problems in the connection between the equipment and MV-36, via Q interface.

NO LOCKOUT COMMAND TO RELEASE No lockout command has been performed; clear command is not necessary.

FAILURE : CROSS CONNECTION OR PORT GROUP FOUND The requested action can not be performed because a cross connection has been found on the selected channel/unit (Deletion).

FAILURE : AUXILIARY CROSS CONNECTION FOUND The requested action can not be performed because an auxiliary cross connection has been found on the selected channel/unit (Deletion).

FAILURE : DCC ENABLED FOUND OR AUXCON The requested action can not be performed because an auxiliary cross connection or as active DCC has been found on the selected channel/unit (Deletion).

FAILURE : MSP/SPRING PROTECTION FOUND The requested action can not be performed because a MSP or MS-SPRing has been found on the selected channel/unit (Deletion).

FAILURE : EQUIPMENT PROTECTION FOUND The requested action can not be performed because an Equipment Protection has been found on the selected unit (Deletion).


339-1268/06

.

Navigation Page

327

Book Contents


FAILURE : SYNC SOURCE FOUND The requested action can not be performed because the selected channel has been configured as synchronisation source (Deletion).

FAILURE : MANUAL SWITCH ON EQUIPMENT PROTECTION The operator tried to delete an Equipment Protection while a manual command was active.

ONE SIDE OF THIS CROSSCON IS ON EXTRA TRAFFIC SWITCHED OUT One side of the connection, which carried low priority traffic, has been switched out due to a protection switch.

PLEASE DON'T EXTRACT THE UNIT AND WAIT FOR CONTROLLER REBOOT. During a database reset, the operator has to wait the operation end.

ERROR IN THE DIMENSION OF PACKET The packet dimension in DCC interface is wrong.

TO COMPLETE LOCKOUT IT IS NECESSARY A SECOND LOCKOUT ON THE ADJACENT NODE ELSE, IN CASE OF PROBLEM ON THE RING, THE MS-SPRING SHOULD BE NOT CORRECT AND LOSE TRAFFIC Packet dimensioning procedure message.

EXTRA TRAFFIC NOT AVAILABLE The configured MSP doesn’t support extra traffic.

MATRIX UNITS INSERTED IN SHELF HAVE DIFFERENT HARDWARE TYPES, IN CASE OF SWITCH THIS MAY CAUSE LOSING OF TRAFFIC The hardware types of the matrix units must be the same.

MSP CONFIGURATION NOT ALLOWED There are not available units to perform the MSP configuration.

THE EQUIPMENT YOU ARE CONNECTED TO HAS DIFFERENT COMMITTED AND RUNNING SOFTWARE VERSION. REMEMBER TO PERFORM A GLOBAL COMMIT TO MAINTAIN RUNNING VERSION The used software has not been validated.

MANUAL COMMAND ACTIVE ON THIS PROTECTION: CONTINUE ANYWAY? There is a software manual command which force the protection.


339-1268/06

.

Navigation Page

328

Book Contents


NO LINE CARDS AVAILABLE FOR MS SPRING There are not line units inserted in the shelf to perform the MS-SPring.

TIME OUT IN RESPONSE FROM SHELF: OK TO FORCE A LOGOUT NOW CANCEL TO IGNORE Some hardware configuration has changed during the login.

AFTER LOCKING EFD THE STATE CHANGE MESSAGES ARE NOT NOTIFIED FROM THE EQUIPMENT AND THE PROTECTION AND SYNC STATUS WINDOWS ARE NOT UPDATED RUN-TIME." The alarm state changes are no longer notified.

AFTER UNLOCKING EFD IS NECESSARY TO PERFORM A GENERAL EQUIPMENT REALIGNMENT USING REFRESH BUTTON IN THE MAIN VIEW" The alarm state change are notified now.

INVALID MAC ADDRESS LENGTH MUST BE 6 DIGITS The MAC address must be composed by six groups of two digits.

FILE “FILENAME” NOT FOUND OR EMPTY. PLEASE CHECK IT Software application error in the initialisation.

ANOTHER APPLICATION HAS CHANGED THE CDL FILE LOADED. DO YOU WANT TO RELOAD IT? The configuration file has been changed and can be loaded.

DOWNLOAD ABORTED The unit software download is failed.

DOWNLOAD RUNNING The unit software download is in progress.

DOWNLOAD COMPLETED The unit software download has been completed.

FOUND CHANNELS NOT MONITORED The channels involved in a not intrusive path protection must be monitored.

MSP PROTECTION SWITCH; PLEASE RELOAD THIS MASK IN ORDER TO REFRESH DATA Exit and re-enter the MSP protection window application in order to refresh the window.


339-1268/06

.

Navigation Page

329

Book Contents


EQUIPMENT PROTECTION SWITCH; PLEASE RELOAD THIS MASK IN ORDER TO REFRESH DATA Exit and re-enter the equipment protection window application in order to refresh the window.

SPRING PROTECTION SWITCH; PLEASE RELOAD THIS MASK IN ORDER TO REFRESH DATA Exit and re-enter the MS SPRING protection window application in order to refresh the window.

IT'S IMPOSSIBLE TO RENAME THIS ALARM The input ground-contact name can’t be changed.

FROM AND TO ARE EQUAL, DISCONNECT WILL CAUSE THE DELETION OF BROADCAST CROSS CONNECTION: CONTINUE?" The master port and leg port is the same; if the operator deletes the leg, the entire cross connection will be deleted.

WARNING: FOUND SOME EXTRA TRAFFIC SWITCHED OUT; CHECK FOR CROSS CONNECTION DATA ON GENERATED CDL FILE The information concerning the switched out extra-traffic are not available.


339-1268/06

.

Navigation Page

330

Book Contents

HOW TO This chapter describes how to perform the operations that require the execution of a proper sequence of commands in the Control Application software.

PROCEDURE TO EXECUTE A DATABASE DOWNLOAD This procedure explains how to download a previously saved database with no traffic effecting.

To execute a MIB download: * Enter the Maintenance mode, by selecting the Maintenance/Service State item in the Maintenance menu. * Erase the current database, by selecting the MIB Reset item in Maintenance menu. * Execute a software download (using the download.ini file related to the current release), by selecting the Software Download item in the Maintenance menu. * Execute a bank switch, by selecting the Bank Switch item in the Maintenance menu. * Execute a software commit, by selecting the Software Commit item in the Maintenance menu. * Download the CDL file related to the previously saved database, by selecting the Execution of Script item in the Maintenance menu. * Exit the Maintenance mode, by selecting the Service item in the Communication and Control Unit menu.


339-1268/06

.

Navigation Page

Book Contents

Operator Handbook

Recommend Documents