NR1402 ALU SDH Operations and Maintenance Procedures

Training

CCOOLLTT TTeelleeccoommmmuunniiccaattiioonnss OOppeerraattiioonnss && TTeecchhnnoollooggyy TTeecchhnniiccaall TTrraaiinniinngg

TTRRAAIINNIINNGG MMAANNUUAALL

LLuucceenntt WWaavveeSSttaarr OOppeerraattiioonnss && MMaaiinntteennaannccee

PPrroocceedduurreess

Course ID NR14xx

Training Manual NR1402 Lucent O&M Procedures

O & T - Technical Training Copyright COLT Telecommunications

Document History

Issue No:

Issue Date Reason for Change Author

1 28th May 2004 New issue Mark Costin

2 8th June 2004 Clarification of the MIB rules in section 9.4 Mark Costin

3 10th June 2004 Updated multiple sections re: new standard core card, enhanced system controller and enhanced tributary cards.

Mark Costin

4 29th June 2004 Additional stores codes added for new HD cards Mark Costin

5 23rd September

2004

Updated to include AMS release 5, new DCC setting for mixed Lucent/Marconi rings and extra warnings in software download section

Mark Costin

6 26th October

2004 Addition of ADM-U Cross connect capacity in Circuit provisioning section 6.2

Mark Costin

This document is intended for training purposes only.

The current controlled version of this document is available via the Technical Training Library. Any printed copy is Uncontrolled.

Copyright notice No part of this document may be reproduced in any form or by any means for any purpose without our written permission.

Copyright COLT Telecommunications, All rights reserved. COLT Telecommunications Registered in England No. 2452736 Registered Office: Bishopsgate Court, 4 Norton Folgate, London E1 6DQ



Table of Contents

1 Document Usage & Scope ......................................................................................... 1-1

2 Introduction ................................................................................................................ 2-1

2.1.1 Further Information ...................................................................................................... 2-1

3 Required I&C Procedures using ITM-CIT .................................................................. 3-1

3.1 Checking the ITM-CIT version ............................................................................................... 3-1 3.2 Local Element Login Procedure using the ITM-CIT .............................................................. 3-2 3.3 Node Creation........................................................................................................................ 3-3 3.4 NMS-DCN & NSAP Addressing Overview ............................................................................ 3-6 3.5 DCN & NSAP Address Settings ............................................................................................ 3-7 3.6 Lucent NSAP Definitions Table ............................................................................................. 3-8 3.7 Configuring the NSAP address............................................................................................ 3-11 3.8 Configuring the DCC Channels ........................................................................................... 3-12 3.9 DCC in case of Marconi Ring or Homing Node ................................................................... 3-13

3.9.1 General ...................................................................................................................... 3-13 3.9.2 Decision Template ..................................................................................................... 3-14 3.9.3 Outband Management ............................................................................................... 3-15 3.9.4 Mixed Ring DCN settings for AMS ........................................................................... 3-16 3.9.5 Inband Management ................................................................................................. 3-17 3.9.6 General ...................................................................................................................... 3-17 3.9.7 Example Scenarios.................................................................................................... 3-17 3.9.8 Provisioning AITS for LAPD Interworking.................................................................. 3-18

4 ITM-SC Provisioning Procedures .............................................................................. 4-1

4.1 ITM-SC Login Procedure ....................................................................................................... 4-1 4.2 Creating a New Element in ITM-SC ...................................................................................... 4-3 4.3 Create a New Group in ITM-SC ............................................................................................ 4-4 4.4 Insert & Position an Element in a Group ............................................................................... 4-6 4.5 Network Element Selection ................................................................................................... 4-8 4.6 Checking the ADM Software version ..................................................................................... 4-9 4.7 Setting the ADM-U Cross Connect Size .............................................................................. 4-10 4.8 New Card Installation or Removal ....................................................................................... 4-11 4.9 Card Protection Schemes .................................................................................................... 4-13

4.9.1 Core/CC Unit Switching ............................................................................................. 4-13 4.9.2 34/45Mb & STM-1e Tributary Cards ......................................................................... 4-13 4.9.3 2Mbit/s Tributary Cards ............................................................................................. 4-14

4.10 MSP Provisioning ................................................................................................................ 4-15 4.11 MS-SPRING Provisioning .................................................................................................... 4-16 4.12 Configuring the DCC Channels ........................................................................................... 4-17 4.13 MDI alarms .......................................................................................................................... 4-18 4.14 NE Alarm Control ................................................................................................................. 4-19

4.14.1 Alarm Latching & Lining up ....................................................................................... 4-19 4.14.2 Alarm Severitys ......................................................................................................... 4-20

4.15 Port Monitoring .................................................................................................................... 4-21 4.16 Trib Port Speed Selection .................................................................................................... 4-22 4.17 Port Loopbacks .................................................................................................................... 4-22 4.18 (Trail) Termination Points .................................................................................................... 4-23 4.19 Optical Line Port Parameters .............................................................................................. 4-26

5 System Timing ............................................................................................................ 5-1

5.1 Lucent Timing Concepts ........................................................................................................ 5-1 5.2 Physical Timing References .................................................................................................. 5-1 5.3 Logical Timing References .................................................................................................... 5-2 5.4 System Timing Priorities and Modes ..................................................................................... 5-2 5.5 Sync Configuration Procedures ............................................................................................. 5-3



6 Circuit Provisioning ................................................................................................... 6-1

6.1 Connection Path Format ........................................................................................................ 6-1 6.2 ADM-U Cross Connect Capacity ........................................................................................... 6-1 6.3 Changing the TUG Structure of the Cross Connection Ports ................................................ 6-2 6.4 Provisioning VC-4 Cross connection ..................................................................................... 6-3 6.5 Provisioning a VC-12 Cross connection ................................................................................ 6-4 6.6 Manual Circuit Switching ....................................................................................................... 6-6 6.7 Cascading Cross Connections (Ring to Ring Connections) .................................................. 6-7 6.8 Provisioning of a VC-4-4c Concatenated ............................................................................ 6-11

7 Maintenance Procedures ........................................................................................... 7-1

7.1 Alarm Listing .......................................................................................................................... 7-1 7.2 Downloading NE Software ..................................................................................................... 7-4 7.3 Switching NE Software .......................................................................................................... 7-5 7.4 Replacing an SC Card ........................................................................................................... 7-6 7.5 Replacing an Entire ADM ...................................................................................................... 7-6

8 Performance Monitoring ............................................................................................ 8-1

8.1 Start Measurement ................................................................................................................ 8-1 8.2 Show Current Measurements ................................................................................................ 8-2 8.3 Create a PM Report ............................................................................................................... 8-3 8.4 Display a PM Report .............................................................................................................. 8-4

9 Appendices ................................................................................................................. 9-1

9.1 ADM-U Equipment Codes ..................................................................................................... 9-1 9.2 ADM-C Equipment Codes ..................................................................................................... 9-2 9.3 Contents of ADM-C Item codes ............................................................................................. 9-3

9.3.1 Subrack 5TAD Contents: ............................................................................................. 9-3 9.3.2 Cable and Connector Kit Contents .............................................................................. 9-3

9.4 AMS Equipment Codes ......................................................................................................... 9-3 9.5 MS-SPRING .......................................................................................................................... 9-4


O & T - Technical Training Copyright COLT Telecommunications Section: 1-1

1 Document Usage & Scope This document focuses on the procedures used when installing or commissioning Lucent WaveStar SDH equipment using the Lucent CIT local craft terminal interface. It should be used in conjunction with the following Lucent hardware guides:

NR1482/83 Lucent AMS Hardware Guide, NR1422/23 Lucent ADM16 Hardware Guide, NR1922/23 Lucent ADM-C Hardware Guide & NR1912/13 Lucent ADM-U Hardware Guide

Training materials such as training manuals, sheets and lab exercises are not intended to replace COLT engineering guides. Therefore procedures, rules, methods & instructions described in COLT Engineering guides always precede those described in training material. The TransLAN card has not been described in this manual. Please refer to course NR1453 to find information on this subject. The content of this document is based on Lucents Venus & Earth release of software, which is the COLT standard as time of writing (September 2004) and relate to the following systems releases:

System Software Release Load name CIT Version

Required

ITM-SC 12

ADM-U

3.0.2 STM-64 STM-16 2.0 STM-64 STM-16 1.1.3 STM-64 STM-16 1.1.2 STM-64 STM-16

SCA333C SCA231A SCA229A SCA131F SCA129F SCA131E SCA129E

13.04.00 12.01.01 11.11.02 11.11.02

ADM16/1 6.2 SCA121C

AMS 3.2 (Mercury) 4.0 (Venus) 5.0B (Earth)

- SCA136 SCA401B

11.11.2 13.00.16 13.03.01

ADM-C 3.3 SCA207E 13.04.00

This document is intended for training purposes only.

The current controlled version of this document is available via the Technical Training

Library. Any printed copy is Uncontrolled.

This course and its materials have been developed for Pan European COLT usage, e.g. OneCOLT;

Local or National documentation and deviations from European Engineering

standards have not been taken into account.



2 Introduction The Lucent Metropolis AMS, ADM-16, ADM-C and ADM-U SDH multiplexers have been selected by COLT as the Next Generation Access CPE (NGA). The original goal of the NGA project was to implement a solution that will significantly reduce the financial outlay required in providing Ethernet services over the existing SDH/Fiber network. Note: The ADM16/1 is now obsolete and is being replaced by the ADM-U and the ADM-C. The demand for Ethernet services will continue to increase the following years as Ethernet is the dominant LAN technology (>80% of Corporate LAN connections). Traditional solutions such as TinyBridge, E-Link and ADVA are expensive and wasteful of fiber and bandwidth. There are two main scenarios for application of this Lucent equipment:

Green-field customer applications for both TDM and Ethernet services

Ethernet connectivity between sites where an existing SDH ADM is installed. In this case the NGA device would either interface with the existing SDH CPE or will be cut-in in addition to the existing CPE.

The existing Marconi Regions Germany, Zurich, Austria, UK, France, Belgium, Portugal and Spain will stop deployment of Marconi SDH Multiplexers. About 85% of the existing customer sides are equipped with equipment that has been declared obsolete by Marconi i.e. Release 1.1d ADMs. Note: The decision was made to deploy NGA Equipment initially into all Marconi countries although the deployment has now been extended to all COLT regions. Navis Optical Management Solution Support The NGA equipment is supported by the Navis Optical Management Solution family. This includes the local ITM-CIT network management software for interfacing at the network element, and ITM-SC network element management software for centralised management of all Lucent SDH equipment.

2.1.1 Further Information Information on the Lucent product range (including Engineering Guides and Software), can be found via the Engineering folders at: http://intranets/0x0a6405b7_0x00252d6d;internal&action=frameset.action The COLT training documentation can be found at: U:\Logical\Technical Training Library Note: in some countires you may need to access the folders via O: Universal\Logical. Usage of the Cross-Connect and deployment rules are described in the COX guide: NSAP address structure and DCN settings can be found at: \\frafil06\cbsshare$\IP-Data\05_Knowledge_Base\DCN_Network\Address Allocations\03 -

NSAP Address Allocations>



3 Required I&C Procedures using ITM-CIT This chapter shows the minimum commissioning procedures needed for an ADM to be brought under ITM-SC management control. These procedures are performed with the ITM-CIT connected locally to the element.

Any configuration differences between types of equipment will be noted in each section

3.1 Checking the ITM-CIT version Important Note: Some Lucent CIT versions are NOT Backwards Compatible! If you have a NE with obsolete software, you may need to use an old release of CIT to access the equipment before you can download the new software load. It is possible to have multiple versions of the CIT software on your laptop at the same time. Older versions of CIT software can be found on the COLT LAN in the following folder: U:\Logical\Network Architecture Public\SDH_PDH_Access Documentation and Software



3.2 Local Element Login Procedure using the ITM-CIT 1. Connect the laptop to the equipment using the CIT-interface. 2. On the CIT select File>NE Login>Login 3. The login speed for ADM-16, ADM-U and ADM-C systems is 38k4. For the AMS it is

115k. The interface speed can be changed using the Edit menu of the NE login screen. 4. Choose CONFIG mode to be able to commission the system. No password is required.

Now you should get into the ITM-CIT Main Menu where the top bar shows the element name.



3.3 Node Creation Note: The Node Creation command can only be done with ITM-CIT (not with ITM-SC)

When a WaveStar multiplexer comes from the factory the MIB (Management Information Base) is empty.

1. When commissioning a new element the first step is run a Node Creation command: Management > Node Creation. This will CLEAR the MIB of any configuration data

VERY IMPORTANT NOTE: NODE CREATION IS ALWAYS SERVICE AFFECTING. DO NOT PERFORM THIS ACTION ON A LIVE TRAFFIC CARRYING MUX.

2. Assign the Core units: SC card, LS1/2, CC1/2 (when the CC card is assigned on the

ADM-U & ADM-C the LS and TIM cards are automatically configured), Fan and Power modules as appropriate, then press Finish. The ADM will now start to commission the cards. This can take up to 10 minutes during which the CIT mouse pointer icon will be an egg timer and no further work can be done.



3. Finally we need to confirm the MIB changes. This stores the configuration onto the motherboard.

The ADM will drop the CIT connection and save the configuration. After the save is completed the NE will reboot. This can take up to 15 minutes. The red LED on the SC card will go out when it is complete.

4. Press Confirm MIB.

Note: The NE will now reboot. This is traffic affecting and should not be carried out on a live traffic carrying mux.



5. Once the ADM has rebooted, return to the Node Details window and confirm that the MIB State is now Filled.

6. If the ADM is connected to the management LAN the ITM-SC manages may now start to

communicate with the element. If further configuration changes are needed it may be necessary to Lock the MIB. This allows local changes to be made via the CIT.

7. When the CIT responds again you can assign the Tributary cards and Paddleboards if

necessary, by selecting Provisioning>Equipment>Provisioned NE Components:

Tip: Press Details to see the card type that is physically installed



3.4 NMS-DCN & NSAP Addressing Overview The ITM-SC communicates with the managed network via a Q-LAN. Communication with the Network Elements which cannot be reached via the LAN directly proceeds via a gateway Network Element on the LAN. The communication path between the gateway Network Element and the destination Network Element makes use of DCC communication paths which are in-band in the Section Overhead (DCC bytes). For routing within the network the IS/IS protocol in the transport layer of the OSI stack is used. The ITM-SC communicates with the managed NGA network via the COLT Network Management Systems-Data Communication Network (NMS-DCN).

General Design of OSI routing layer NMS-DCN



3.5 DCN & NSAP Address Settings The Lucent NGA network will be managed centrally via the element management system ITM-SC. The ITM-SC communicates with the managed NGA network via the COLT Network Management Systems-Data Communication Network (NMS-DCN). Lucent NSAP addresses have the following set structure:

390000800000000000 01

For the UK the COLT Domain is 0044. For Germany, 0049. For NL 0031. etc.

The Management Area (always 4 digits 2 for city, 2 for node) reflects the span of control of the ITM-SC manager. This will be used to define the city and node from where the equipment is managed.

Note: See the Error! Reference source not found. below for the standard COLT management addressing scheme

SID or System ID, is the MAC address of the NE. The SID has to be communicated from Field Ops to NMC to bring the element under ITM-SC management.

Note: The SID is held on the physical chassis and cannot be changed.

For Address structure use: Flexible

In AMS release 5.0B there is a new feature for the DCC inter-working with the Marconi muxes: LSP Buffer Size. The default value is 512 bytes (Lucent value), the other option is 1492 bytes (Marconi value ISO 8473) used when the AMS is introduced into mixed Marconi rings.

Foe more details see the engineering guide: O:\Universal\Logical\Network Architecture Public\SDH_PDH_Access Documentation and Software\01 Engineering Guides\01 Lucent\01 AM-S\EUNA-Access-Lucent-EG-004- AM-S Monitoring in COLT existing SDH infrastructure.doc



3.6 Lucent NSAP Definitions Table The following tables comes from the new COLT Wide NSAP Addressing scheme, March 25, 2004, by IP Engineering - Internal Networks (Jimmy Ehrbar & Alwin Jansen).

Fixed Value 39.0000.8000.0000

Each city will have unique ID starting from 01

Each node will have unique ID starting from 01

Digit Digit in Blue (1-digit) is used to identify the IS-type (L1/L2) and Vendor

b DCN Backbone Level-2 only areas

0 Level-1 areas for SDH NEs



3 Level-1 areas for Marconi Servers

4 Level-1 areas for Lucent Servers

5 Level-1 areas for Nortel Servers

6

F

Digits in Red (3-digits) are used to assign the AREA ID:

Incremental number for AREA ID

With 3-digits, 4096 combinations are possible

Exception for ISIS Backbone Areas Level-2: the field "City/Node" is reserved with "bbbb" digits

Same code will be used as used for the phone number system.

Country-code Fields

Area field definition

Area number xxx

Area field: Axxx

Dedicated digit A

NSAP Field definitions

AFI + IDI Fields

City and Node Fields



Country City Node

NSAP Address Fields

AFI + IDI Country

Code City

Code Node Code

Area SID Selector

UK

UK London KJC 39.0000.8000.0000 0044 01 01 0001 01

UK London CTF 39.0000.8000.0000 0044 01 02 0001 01

UK London BGT 39.0000.8000.0000 0044 01 03 0001 01

UK London PBP 39.0000.8000.0000 0044 01 04 0001 01

UK London MBY 39.0000.8000.0000 0044 01 05 0001 01

UK London SMH 39.0000.8000.0000 0044 01 06 0001 01

UK London Can Whrf 39.0000.8000.0000 0044 01 07 0001 01

UK London Tele Hse 39.0000.8000.0000 0044 01 08 0001 01

UK London PGT 39.0000.8000.0000 0044 01 09 0001 01

UK Manchester MAN 39.0000.8000.0000 0044 02 01 0001 01

UK Birmingham BHX 39.0000.8000.0000 0044 03 01 0001 01

UK all BB 39.0000.8000.0000 0044 bb bb b000

Germany

GE Frankfurt FEL 39.0000.8000.0000 0049 01 01 0001 01

GE Frankfurt FGS 39.0000.8000.0000 0049 01 02 0001 01

GE Frankfurt FSS 39.0000.8000.0000 0049 01 03 0001 01

GE Frankfurt FHS 39.0000.8000.0000 0049 01 04 0001 01

GE Stuttgart STU 39.0000.8000.0000 0049 02 01 0001 01

GE Berlin BKP 39.0000.8000.0000 0049 03 01 0001 01

GE Berlin BWS 39.0000.8000.0000 0049 03 02 0001 01

GE Cologne CGN 39.0000.8000.0000 0049 04 01 0001 01

GE Hamburg HDB 39.0000.8000.0000 0049 05 01 0001 01

GE Hamburg HWS 39.0000.8000.0000 0049 05 02 0001 01

GE Dsseldorf DTH 39.0000.8000.0000 0049 06 01 0001 01

GE Hanover HAJ 39.0000.8000.0000 0049 07 01 0001 01

GE all BB 39.0000.8000.0000 0049 bb bb b000

France

FR Paris CHA 39.0000.8000.0000 0033 01 01 0001 01

FR Paris WAT 39.0000.8000.0000 0033 01 02 0001 01

FR Paris DEF 39.0000.8000.0000 0033 01 03 0001 01

FR Malakoff VAL 39.0000.8000.0000 0033 02 01 0001 01

FR Noisy NOI 39.0000.8000.0000 0033 03 01 0001 01

FR Trappes POL 39.0000.8000.0000 0033 04 01 0001 01

FR Lyon BAR 39.0000.8000.0000 0033 05 01 0001 01

FR Marseille PRA 39.0000.8000.0000 0033 06 01 0001 01

FR Strasbourg LUM 39.0000.8000.0000 0033 07 01 0001 01

FR Bordeaux PER 39.0000.8000.0000 0033 08 01 0001 01

FR Toulouse GEN 39.0000.8000.0000 0033 09 01 0001 01

FR Nantes EBO 39.0000.8000.0000 0033 0a 01 0001 01

FR Velizy EUR 39.0000.8000.0000 0033 0b 01 0001 01

FR Massy FEM 39.0000.8000.0000 0033 0c 01 0001 01

FR Villebon NOR 39.0000.8000.0000 0033 0d 01 0001 01

FR Aubervilliers JAU 39.0000.8000.0000 0033 0e 01 0001 01

FR Lognes CAM 39.0000.8000.0000 0033 0f 01 0001 01

FR Les Ulis ULI 39.0000.8000.0000 0033 10 01 0001 01

FR Lille LIL 39.0000.8000.0000 0033 11 01 0001 01

FR all BB 39.0000.8000.0000 0033 bb bb b000



Spain

ES Madrid TLM 39.0000.8000.0000 0034 01 01 0001 01

ES Madrid STL 39.0000.8000.0000 0034 01 02 0001 01

ES Barcelona GVA 39.0000.8000.0000 0034 02 01 0001 01

ES Valencia EPN 39.0000.8000.0000 0034 03 01 0001 01

ES all BB 39.0000.8000.0000 0034 bb bb b000

Italy

IT Milan JEN 39.0000.8000.0000 0039 01 01 0001 01

IT Milan LAB 39.0000.8000.0000 0039 01 02 0001 01

IT Turin LIV 39.0000.8000.0000 0039 02 01 0001 01

IT Rome MAR 39.0000.8000.0000 0039 03 01 0001 01

IT all BB 39.0000.8000.0000 0039 bb bb b000

The Netherlands

NL Amsterdam MAD 39.0000.8000.0000 0031 01 01 0001 01

NL Amsterdam SPA 39.0000.8000.0000 0031 01 02 0001 01

NL Amsterdam MAF 39.0000.8000.0000 0031 01 03 0001 01

NL Amsterdam LUC 39.0000.8000.0000 0031 01 04 0001 01

NL Rotterdam CON 39.0000.8000.0000 0031 02 01 0001 01

NL Den Hague DIN 39.0000.8000.0000 0031 03 01 0001 01

NL all BB 39.0000.8000.0000 0031 bb bb b000

Belgium

BE Brussels BRU 39.0000.8000.0000 0032 01 01 0001 01

BE Brussels AND 39.0000.8000.0000 0032 01 02 0001 01

BE Gent GNE 39.0000.8000.0000 0032 02 01 0001 01

BE Antwerp ANR 39.0000.8000.0000 0032 03 01 0001 01

BE all BB 39.0000.8000.0000 0032 bb bb b000

Sweden

SE Stockholm LUN 39.0000.8000.0000 0046 01 01 0001 01

SE Stockholm SOL 39.0000.8000.0000 0046 01 02 0001 01

all BB 39.0000.8000.0000 0046 bb bb b000

Denmark

DK Copenhagen BCG 39.0000.8000.0000 0045 01 01 0001 01

DK all BB 39.0000.8000.0000 0045 bb bb b000

Switzerland

CH Zurich ZMU 39.0000.8000.0000 0041 01 01 0001 01

CH Basel BVI 39.0000.8000.0000 0041 02 01 0001 01

CH Geneva GMB 39.0000.8000.0000 0041 03 01 0001 01

CH all BB 39.0000.8000.0000 0041 bb bb b000

Austria

AU Vienna VKR 39.0000.8000.0000 0043 01 01 0000 01

AU all BB 39.0000.8000.0000 0043 bb bb b000

Portugal

PO Lisbon OTL 39.0000.8000.0000 0051 01 01 0000 01

PO all BB 39.0000.8000.0000 0051 bb bb b000

Ireland

IRE Dublin DUB 39.0000.8000.0000 0035 01 01 0000 01

IRE all BB 39.0000.8000.0000 0035 bb bb b000

COLT will implement the Flexible Address Structure, as this is the only structure that allows us to implement the new COLT Wide NSAP Addressing scheme



3.7 Configuring the NSAP address 1. Select Management>Overlay Comms Network>DCN. 2. Configure the parameters as shown below using the information in the Error! Reference

source not found.:



3.8 Configuring the DCC Channels Lucent WaveStar multiplexers use the D-bytes of the MS overhead for DCC traffic.

When the ADMs are used in a ring topology the DCC channels on the Aggregate Line Ports are enabled as default.

When the ADMs is used as a homing node the customer rings will terminate on the STM tributary cards. By default the DCC channels on Tributary cards are Disabled. Before you can manage the customer sites through the tributary cards you must ensure that the DCCs are enabled.

If the Lucent equipment if terminating on a Marconi Homing node, then you must modify the DCC channels on the Marconi element as they are set to RS comms by default.

1. To configure the DCC setting select Management>Overlay Comms Network>DCC.



3.9 DCC in case of Marconi Ring or Homing Node This chapter is based upon Engineering Note Monitoring of Lucent AM S Systems in COLT existing SDH Infrastructure version 1.0; author T. Kulke, dated 15.01.04.

3.9.1 General The Introduction of Lucent Next Generation Access (NGA) Device is divided into different phases. One of the reasons is the Software Roadmap of the Lucent AMS. This SW Roadmap includes different Data Communication Network (DCN) interworking features with the current COLT SDH Infrastructure. The main interworking features are:

OSI stack

UITS/AITS LAP-d protocol mode

LAPd Frame Size

LSP Buffer Size

OSI Stack Marconi (formerly GPT), developed a different OSI stack on all R1 SMA Systems. This OSI stack is incompatible for interworking with Lucent ADMs.

Marconi R1 systems (SMA1.1d), can not communicate using Data Communication Channels (DCCx), with Lucent systems.

LAPd Mode The user can select the LAP-D protocol to be based on AITS (Acknowledged Information Transfer Service) or UITS (Unacknowledged Information Transfer Service). In the AITS mode the receive side sends an acknowledgement back to the transmit side, if a data packet has been received. If this acknowledgement does not arrive, the transmitter sends the packet again. In the UITS mode no acknowledgements are sent. Marconi implemented AITS for Series 2 & 3 equipment and Lucent used UITS. Data Communication Channels using different modes can not be connected. New AMS software allows the user to configure the lapd mode settings.

LAP-d interworking between Lucent AM S and Marconi Series 2 and 3 equipment is only possible when using AMS Release 4.0 or higher.

LAPd Frame & Buffer Sizes The LAP-d Frame Size on Marconi S2/3 systems can be set between 512 and 1492 Byte per STM-n interface. The Lucent system has a fixed value of 512 Byte for all interfaces. If the LSP Buffer Size is changed, than all Elements of that Area (all Elements connected to one Gateway) need to have the same LSP Buffer Size. COLT agreed as interims solution to change the LSP Buffer Size on Marconi systems in case of required DCN interworking. Due to the operational effort COLT only accept that as interims solution.

The user will need to change the LAP-d Frame Size and LSP Buffer Size of all Marconi Series 2 & 3 equipment on the homing ring area to 512 Byte if the lucent AMS is pre v5.0 If the Lucent AMS has version 5 or higher software, the frame and buffer size should be changed on each AMS to 1492 bytes.

Due to the above limitations COLT is going to introduce INBAND MANGEMENT and OUTBAND MANAGEMENT.



Order for CITY/

EURO or

International

LANLink

new Customer?Marconi Series 2/

3 on siteNo

Can PacketSpan be

used?

- Stock available

- B-end PacketSpan as

well

Yes

Marconi

PacketSpan

installation

Yes

SMA or MSH with

free STM-1o Slot

capacity?

No

No

subtended AM S

installation to the

existing CPE with

ouband

Management

Yes

Lucent Homing

Node available?

Yes

Marconi HN only

for Lucent rings

available?

No

AM S Cut-in into

the Lucent ring

using inband

Management

Yes

No

Yes

Marconi HN with

purly Lucent ring

available (other

rings with MSH or

SMA)?

No

AM S Cut-in into

the Lucent ring

using outband

Management

Yes

AM S Cut-in into

Marconi ring using

DCC pass through

mode and ouband

Management

No

3.9.2 Decision Template



3.9.3 Outband Management Outband Management means the use of SDH Payload to route the management traffic of the AMS to the OSI- or NMS-DCN of the Network Management System and not to use SDH Overhead functionality e.g. DCC bytes. This will be realised by using an Shared Bandwidth LANLink over SDH, which will be provided by the TransLAN optional board within the AMS and the Fast Ethernet card of the InterAccess Gateway at the COLT Node. See also the TransLAN course manual NR1453 for more specific information on this subject.

Outband Management will mainly be used for subtended and mixed ring applications where the homing or head end multiplexer is a Marconi series 1.

Note: In both cases the AM S management streams are complete isolated from the neighbour Network Elements. Subtended: Connecting the AMS via STM-1o to existing Marconi CPE using Terminal configuration

Mixed Ring: Cut-in of AMS systems into a ring with Marconi ADMs.

STM-1 ring

existing Marconi CPE

interconnection via STM-1ounprotected

AM S

Homing Node

STM-1 ring

existing Marconi CPEAM S

Homing Node



3.9.4 Mixed Ring DCN settings for AMS A complete DCCr routing of Marconi Management Information around the STM-1 Homing Node ring must still be guaranteed, even if the AM S is cut in between of two Marconi ADMs. To be in line with this rule, the to be cut-in AM S must be run in DCC Through Mode. That means all traffic coming via DCCr into an AM(S) on LP1.1 will be transparency switched to the DCCr on LP2.1 and vice versa. The following picture shows the basic Network Management Architecture for a mixed ring & subtended configuration. The AMS installed on Customer premises is configured as DCN Gateway. All Management traffic of this node will be routed to the Q3-Management port of the AMS. The aim of the Shared Bandwidth LanLink is to connect all Q3-Management ports of one Homing Node ring to a virtual switch including the TransLAN card of the InterAccess Gateway within the Node. This TransLAN card in the Node is connected to the OSI / NMS LAN of the Management Systems. Note: The limitation to cascade all AM S Systems of only one ring is to prevent too many monitoring outages during a fibre break.

Marconi Homing Node

Marconi CPE Lucent AM S

Lucent InterAcess Gateway

COLT Node

DCN OSI Router

Connection betwenn Q3- port and TransLAN port



Marconi

Homing Node

Marconi CPE

Lucent AM S

COLT Node

DCN OSI Router

Marconi

Homing Node

Marconi CPE

Lucent AM S

COLT Node

DCN OSI Router

3.9.5 Inband Management

3.9.6 General In cases where an AMS ring is terminated on a Marconi homing node the monitoring function inband makes use of DCCm communication to the neighbours NEs. To establish this DCCm communication, the LAPD mode of the AMS must be equal to the Marconi NE.

The user will need to change the LAP-d Frame Size and LSP Buffer Size of all Marconi Series 2 & 3 equipment on the homing ring area to 512 Byte if the lucent AMS is pre v5.0

If the Lucent AMS has version 5 or higher software, the frame and buffer size should be changed on each AMS to 1492 bytes.

Note: The configuration of LSP & Frame parameters for Marconi SMA systems can be done via EMOS (remotely). To configure the MSH11x kits a site visit is necessary (LCT setting).

3.9.7 Example Scenarios Scenario 1: Marconi Homing Node for only Lucent AMS

All Marconi Homing Node rings are managing only Lucent AM S systems using DCCm.

The Homing Node is connected to the OSI DCN LAN via the Q3-port.

LSP Buffer Size set to 512 Byte for Marconi Homing Node

LAPd DCCm Frame Size set to 512 Byte for the Line Cards of the Marconi Homing Node

AM S Systems using AITS mode for LAPd interworking

Scenario 2: Marconi Homing Node for mixed Network

All Marconi Systems terminated on that Marconi Homing Node needs to be Series 2/3 or MSH11c systems

The Homing Node is connected to the OSI DCN LAN via the Q3-port.

LSP Buffer Size set to 512 Byte for Marconi Homing Node and all Marconi ADMs within the rings (SMA can be set by EMOS; MSH11c needs to be visit on site)

LAPd DCCm Frame Size set to 512 Byte for the AM S neighbour NEs (SMA can be set by EMOS; MSH11c needs to be visit on site)

AM S Systems using AITS mode for LAPd interworking



3.9.8 Provisioning AITS for LAPD Interworking As described earlier to establish this DCCm communication, the LAPD mode of the AMS must be equal to Marconi NE and set to AITS. In this chapter the steps to do so are described: 1. Select Management -> Overlay Comms Network-> DCC 2. Select LP1.1 and click on Edit 3. Set DCC Status to Enabled and LAP-d Mode

to Aits;

4. For the LAP-D Side field:

If AITS mode is selected: then the LAPD Side parameter must be also configured to match the Marconi settings:

LP1.1 Network LP1.2 User

If UITS mode is selected: the LAPD Side parameter is not used.

5. Perform the same configuration for LP2.1



6. In AMS release 5.0B there is a new feature for the DCC inter-working with the Marconi muxes called LSP Buffer Size. The default value is 512 bytes (Lucent default), the other option is 1492 bytes (Marconi default ISO 8473) which must be used when the AMS is introduced into mixed Marconi rings.

For more details see the engineering guide: O:\Universal\Logical\Network Architecture Public\SDH_PDH_Access Documentation and Software\01 Engineering Guides\01 Lucent\01 AM-S\EUNA-Access-Lucent-EG-004- AM-S Monitoring in COLT existing SDH infrastructure.doc



4 ITM-SC Provisioning Procedures This chapter shows how the provisioning procedures for ADMs are performed with the ITM-SC.

4.1 ITM-SC Login Procedure To communicate with the ITM-SC system we will be using a graphical interface called an X-terminal. On the course we will use a X-terminal emulation program for that called Exceed; 1. So the first step is to start Exceed in the broadcast mode (see below). During the courses

we will be using the standby ITM-SC server, this could be either lucluc20 or lucluc21.

Instead of logging directly to that server we will use a sort of graphical front end; Colt has two of these at the proper release, the first one is lucluc01 and the second one is madluc02.

2. The 2nd step is to login either lucluc01 or madluc02

3. After successfully logging into the graphical X-server (lucluc01 or madluc02) a taskbar

appears at the bottom of the screen; the next step would be to select the second icon from the left



4. Next we are going to select with which ITM-SC server we are going to work, select Any ITM-SC NE Management

5. As time of writing the NGA project has allocated two servers: lucluc20 and lucluc21. One

of these servers (lucluc20) acts as the worker and the other has the standby (lucluc21). For training purposes we want to use the standby server: so select lucluc20 or lucluc21 and then enter lowercase y

6. Wait for a while

(depending on load) and then the ITM-SC Main Menu will appear,

Note: If you see live customer elements it means youre just logged on to the active database server -> during training this is not allowed so logoff and selects the standby server:



4.2 Creating a New Element in ITM-SC As described earlier some actions need to be done locally by Installation personnel using the CIT. During the commissioning process the area address will be configured and the engineer needs to inform the NOC of the system address or SID. Without the SID the NE cannot be managed. 1. The first step is to select Equipment>Create >MIB Image From NE. This uploads the

MIB from the element and stores it onto the ITM-SC database. The MIB contains all the element configuration data such as cards, ports, cross connects, TUG-structures etc.

2. Select the correct NE Type 3. Type Element Name 4. Select Flexible NSAP Format 5. Type in Area Address (inc. Domain Address) 6. Type in SID (provided by local Installation engineer) 7. Select Dynamic



8. After filling out the above form, press the Apply button and a Message appears at the bottom of the above form: Operation Started. The ITM-SC will now try to connect to the element via the DCN using the NSAP parameters you have filled in.

9. When the connection is made a new icon appears on the top menu of the ITM-SC representing the new element. The ITM-SC will now upload the MIB from the element to the ITM-SC database. After a while another Message will appear to indicate the success or failure of this operation.

10. Now Close the form and position the element under a group as described next

4.3 Create a New Group in ITM-SC A group in ITM-SC represents a group of elements, for instance all elements in the UK. To create a new group follow these steps: 1. Select the right hand icon to Modify

the groupings of nodes

2. On the resulting screen (below) select Create Group



3. Type in the New Group Name. 4. The Parent Group Name represents the group/level where this new group will be

inserted. It is possible to nest groups, e.g. create sub-groups within groups and so forth. When youre done select Apply.

5. The Group has been successfully created and should now appear in the Parent Group

youve selected in this example at Top Level.

6. The colour of the group will indicate the highest alarm of all elements grouped within the

group (and have association with the ITM-SC). In this case the group is new and no elements are in the group. The next chapter will explain how to do that.



4.4 Insert & Position an Element in a Group When an element needs to be moved to a group follow these steps: 1. Select the right hand icon to Modify the

groupings of nodes

2. Highlight the element you wish to place using the LMB. Hold the Middle Mouse Button

(MMB), a little white hand will appear, keep MMB pressed and drag the element into the group where you want to position it. (Note: in Exceed this will be done using MMB emulation. You may need to press the Left and the Right Mouse Buttons simultaneously).

3. A message at the bottom of the form should appear indicating the result of your action

4. As a result of this operation the element is

removed from the Top Level and placed into the group. Double clicking on the group will take you inside that particular group.



5. As can be seen in the following figure when an element is placed in a group it needs to be positioned. The default position is in the left upper corner.

6. Highlight the element you wish to place using the LMB. Hold the Middle Mouse Button

(MMB), a little white hand will appear, keep MMB pressed and drag the element to the required position. (Note: in Exceed this will be done using MMB emulation. You may need to press the Left and the Right Mouse Buttons simultaneously).



4.5 Network Element Selection

Note: Before any task is performed always check that it will be performed on the correct element.

The name of the selected element is always displayed in the top halve of the active window.

A different element can be selected by clicking on

A list of all manageable elements is displayed from which the right one can be selected.

Name of selected element



4.6 Checking the ADM Software version The software version must be checked for every new NE. 1. Select Provisioning>Equipment>NE Software Inventory

The current COLT approved release levels (November 2004) are: For an ADM16/1 = R6.2, item code is SCA121C For an AMS = R5.0B, item code is SCA401B For an ADM-C = R3.3, item code is SCA207E For an ADM-U STM-16 core = R3.0.2, item code is SCA333C Note: The Active and Backup Stores should have the same loads.



4.7 Setting the ADM-U Cross Connect Size Setting the Cross Connect Size is only applicable to the ADMU, and by default the size is 10Gbit/s.

The number of lower order Cross Connect ports is related to the Cross Connect size:

10 Gbit/s is 64 CC-ports

20 Gbit/s is 128 CC-ports. 1. Select: Provisioning>Equipment>NE Information>Upgrade Low Order Cross

connect Size 2. The COLT default selected option is Yes (20Gbit/s)

3. Select Apply Note: after setting the Cross Connect size to 20Gbit/s the button Upgrade Low Order Cross connect Size is not displayed anymore in the NE Information window.



4.8 New Card Installation or Removal When a new card and/or Paddleboard has been physically installed in the ADM it needs to be provisioned with either the CIT or the ITM-SC system. This is known as assigning a unit. When a card and/or Paddleboard has been removed it has to be unassigned.

Trib cards must be assigned before assigning the corresponding Paddleboards Paddleboards must be Unassigned before Unassigning the corresponding Trib cards

1. To have a look at the shelf configuration with all

its cards select the element (LMB) and then press RHM Button. The Node Action Menu will appear:

2. Select Shelf Display to display the Subrack Overview :



3. Select the card which needs to be commissioned/decommissioned by using the LHM or alternatively using the main menu Provisioning>Equipment>Slot.

Note: Lucent recommends physically installing the paddleboard before the tributary card.

Important Note: For an ADM-16 the default port type for the quad port STM-1 cards (LJB439) after card provisioning is OPTICAL. If Electrical working is required you must modify the port type using the menu command: Provisioning>Equipment>Ports>select req. port>Modify. This must be done before the electrical paddle boards can be assigned.

4. After selecting the card, you should get the following form in which you can modify Slot

State to commission/decommission a card/Paddleboard. Notice that the Actual Item Code identifies which card has been auto-detected.

Use the short codes that can be found on a sticker on the boards (e.g. LJB439, PBB1) to assign Cards or use the Details button to find out which board has been installed

In this example we have added a new STM-1 card in TS2: see alarm below:



4.9 Card Protection Schemes Equipment/Card protection switching provides hardware redundancy in case of equipment failure. When units of the same type are present, certain units are designated for protection purposes. When a working unit fails, the NE will automatically issue a switch command to its protecting unit.

4.9.1 Core/CC Unit Switching

4.9.2 34/45Mb & STM-1e Tributary Cards 34/45Mbit/s and STM-1e tributary interface card are always 1+1 protected.



4.9.3 2Mbit/s Tributary Cards 2Mbit/s Tributary interface card are always 1:N protected.

for ADM-16 and ADM-U, slot TS9 is the protection slot

for ADM-C, slot TS5 is the protection slot



4.10 MSP Provisioning MSP transmission protection schemes are only available for SDH Optical interfaces.

Where MSP is used it should be configured as Non-Revertive and Uni-Directional.



4.11 MS-SPRING Provisioning MS-SPRING transmission protection is available for ADM-16, ADM-U and ADM-C. Note: At the moment the use of MS-SPRING on the aggregate line is country dependent. Please consult your local engineering team for details. Use Protection>Transmission>select ADM type>MS-SPRING 1. The Line State of both Line Ports should be Active. The Switch Status should be Idle.



4.12 Configuring the DCC Channels

Lucent WaveStar multiplexers use the D-bytes of the MS overhead for DCC traffic.

The DCCm channels on the Aggregate Line Ports (LPs) are enabled as default.

If the ADM is used as a Homing Node the customer rings will terminate on the STM tributary cards. By default the DCCm channels on Tributary cards are Disabled. Before you can manage the customer sites through the tributary cards you must ensure that the DCCs are enabled.

If the Lucent equipment is connecting to a Marconi node, then you may need to modify the DCC channels on the Marconi element as they are set to DCCr (RS) by default.

1. Select Management>NE status>DCC List> Highlight MS port >Edit



4.13 MDI alarms Each ADM has Miscellaneous Discrete Input (MDI) alarms that can be used to monitor external events. COLT will use these MDI alarms to monitor:

The opening of Presentation Panel & Equipment Cabinet Doors

Power Supply Status both 220 VAC and 48VDC

Note: When a MDI alarm is not installed fill in the description Not equipped

Ports should be configured as follows:

ID1 - Door Open

ID2 - 220VAC Failure

ID3 - Urgent Power Alarm

ID4 - General Power Alarm



4.14 NE Alarm Control

4.14.1 Alarm Latching & Lining up

For every active NE Alarm Latching must be active. This means that cleared alarms are not automatically removed from the alarm list but must be manually acknowledged.

Lining up suppresses all alarms from an NE and should not be active for operational NEs. Lining up may be active for non-operational NEs such as decommissioned elements.



4.14.2 Alarm Severitys After an NE has been brought under management some Alarm Severitys must be set to the correct value. The severity settings on the ITM-SC are only a global indication of the importance of an alarm, always check out any alarm and make your own decision about the urgency. Until now Engineering has no recommended settings for the ADM Severitys.



4.15 Port Monitoring The Port Mode controls whether input signals should be monitored or not monitored. The default is Not Monitored! Use Provisioning>Equipment>Ports to change.

For all active ports the Port Mode should always be set to Auto. If this is not done then alarms on these ports like LOS, AIS, Loss of Pointer etc. do not appear on ITM-CIT & ITM-SC.

Monitored: the port is configured to provide service and the port signal is monitored. Alarms are generated for this port

Not Monitored (Default): the port is configured to not monitor the signal on the port. No alarms are generated for this port. If there still is a signal present on the not monitored port it is possible to receive a Not Expected Input Signal (NES) alarm.

Auto: the port is configured not to provide service yet. Use this mode when the signal source in the remote NE is not operational yet. As soon as the NE establishes the continuous presence of a fault-free signal for a certain period (the Port Mode Time), the port automatically changes to Monitored. COLT Engineering recommends to use this mode for all ports which are going to be used.



4.16 Trib Port Speed Selection On the ADM-U & ADM-C some of the tributary cards have configurable port speeds:

System Card Types

ADM16/1 LJB439(B) STM-1e or STM-1o

ADMU LKA39 STM-1o for ports 1 to 12 or STM-4o for ports 1, 5, 9 & 10

ADMC/U LKA8 34 Mbit/s or 45 Mbit/s

1. To configure/view Port Speeds select Provisioning>Transport>Ports(select

port)...>Details>Edit

4.17 Port Loopbacks Note: Loopbacks are not possible on STM-16 aggregate, STM-1 electrical or LAN card ports. Loopbacks are not transparent i.e. traffic is not forwarded while looped. Note: Inloops on E1 cards are exclusive i.e. there is a maximum of one per card.

Inloop (loop towards the customer interface): The equipment provides loopbacks on incoming signals, looping the incoming signals back to their corresponding outputs while maintaining the signal format.

Outloop (loop towards the network interface): Routes an output signal coming from the cross connect, at the physical port back to the corresponding input port.

1. To configure/view Port Loopbacks select Provisioning Equipment>Ports>Edit



4.18 (Trail) Termination Points The trail termination points enable the user to set or view parameters derived from data stored in the overhead bytes of the signals i.e. Internal SDH alarms and Path Traces

Both Termination Points of a circuit must be set to monitored to raise SHDH alarms such as AIS, LOP, TIM or REI.

Termination points for the Trib Ports should be set after provisioning the circuit path.

In the termination points the path overhead of the VC-4, VC-3 or VC-12 signal is terminated (added or removed).

In the AU-4, TU-3 and TU-12 termination points the path overhead is not terminated, but can be monitored.

For all Trail Termination Point Provisioning the following rules apply: TP Mode should be Monitored Trace Identifier Mismatch Detection MUST be DISABLED

The reason for disabling the TIM Mismatch Detection is that COLT does not want live traffic interrupted because of the consequent actions of an incorrect Trail Trace. Upon mismatch the consequent actions are Alarm Indication Signal (AIS) insertion in the downstream signal (traffic affecting) and Remote Defect Indicator (RDI) insertion in the upstream signal.

NE A

NE C

NE B NE D

Termination Point

Termination Point

Termination BIP check

TP

Defect: AIS, LOP, TIM, REI

RDI, REI



As can be seen above and in the next figure, it is possible to use the Trail Termination Identifier (TTI) to check the end-to-end connectivity of a trail. In this case the specific string From Zurich will be received at the remote termination point of this trail and apparently the remote Termination Point is transmitting From Madrid TP2.



Note: TTI functionality can be very useful to check end-to-end connectivity of SDH-circuits and should be configured if possible. For COLT use, insert the customer circuit number; therefore use the ASCII Access Point Identifier Format;



4.19 Optical Line Port Parameters In the same menu as Port Monitoring, the optical port parameters for Line Ports can be monitored. On the ADM-16 only, the ALS parameters can be changed. ALS is a safety mechanism that must be enabled (if possible) on optical ports. When ALS is enabled the laser automatically stops sending when the fibre is cut. The laser will automatically restart for 2s, every 62s until the transmission path is restored. 1. To view/edit the transmission parameters of the optical line ports select:

Provisioning>Equipment>Port (select port)...>Optics



5 System Timing

5.1 Lucent Timing Concepts COLT has a high quality G.811 conformant clock system in every node, which feeds a satellite-derived PRC quality clock signal into the Station Clock Input of all ADM homing nodes. As shown below, Lucent uses the concept of assigning a Physical Timing reference to a Logical Timing Source. The Physical Timing references are indicated on the left side, the Logical Timing Sources on the right side.

5.2 Physical Timing References For Lucent ADM's the different physical ports that accept the clock signals are the:

Station Clock Inputs (EXT SYNC IN). Note: When a station clock input is to be used, be sure the main timing ports (MTPs) are provisioned and monitored.

Aggregate line interfaces

One of the 2Mbit/s ports if connected to a structured signal source such as a DXC.



As explained above the Station Clock Input will be used as the main Timing Reference. This means that we have to assign this physical Timing References to the corresponding Logical Timing Reference. Also the monitoring has to be enabled to enable the monitoring of Timing Source faults. The ADMs support the SSM byte in accordance with ETSI recommendation ETS 300 417-6. When using the Line Ports as Timing Sources the Quality is read from the S1-byte in the Section Overhead, it is reflected in the QL-in parameter. The quality level of the timing references can be provisioned by the user. The provisioned quality level is called QL Provisioned. In case of a timing reference without an S1-byte, QL Provisioned allows the user to provision a quality level. In this case the timing reference does have an S1-byte (QL in can be read by the system).

For ADMs used as homing node: QL-Provisioned should be set to PRC. Outgoing S1bytes on all STM-x Ports will then be PRC indicating a good Timing Source.

5.3 Logical Timing References Lucent ADM's have the following logical timing sources available: STCLK_1, STCLK_2, LINE_1, LINE_2, TRIB_1, TRIB_2through to...TRIB_x (etc where x is the number of Trib ports on the element). Note: that the logical timing reference is just a name. It can actually be associated with any physical timing port. However logic dictates that they should be used in the following manner:

STCLK_1 is assigned to EXT SYNC IN_1 or MPT1.1

STCLK_2 is assigned to EXT SYNC IN_2 or MPT1.2

LINE_1 is assigned to line LP1.1

LINE_2 is assigned to line LP2.1

TRIB_1 is assigned to a source port on TP1

TRIB_2..as above

5.4 System Timing Priorities and Modes Each ADM equipped with an internal oscillator that provides a clock signal to the system cards and can either be free running or locked to an external timing reference.

For pure transmission purposes, the oscillator can be set to a Free running mode, in which no synchronisation reference is used. For COLT purposes this timing mode is not accurate enough for transmission.

Within COLT all network elements must be synchronised, or Locked, to an accurate timing reference clock. When a timing reference fails the system can be programmed to select a lower priority timing reference as a backup.

When all timing references have failed the system will switch over to Holdover mode.



5.5 Sync Configuration Procedures 1. First the Signal Type of the External Timing Source called MTP1.1 (if used), which relates

to Ext Sync 1, has to be specified and this Port has to be set to monitored and have its signal type specified (2Mbit/s).

For AMS, ADM-U & ADM-C select Provisioning>Transport>Ports or for ADM-16 select Provisioning>ADM-16 Sync>Timing port as shown below:



2. Next the Logical Timing Source has to be assigned to the Physical Timing Source. Select Provisioning>Timing>Timing Source and configure the parameters as shown in section 5.3 above:



Homing Node ADM Timing Sources Window under Normal Conditions 3. Finally the Timing Mode has to be locked to the primary clock reference, which must be

provisioned as Priority 1. The secondary source is configured as priority 2.

Select Provisioning>Timing>System Timing and configure the parameters as shown overleaf:

4. Configure the timing parameters as shown below:

Homing Node ADM-U System Timing Sources under Normal Conditions



Note: These are the COLT standard setting but Local/Country differences may be used.

For all ADMs in the Node: the Station Clock Input (External 1 or MPT1.1) will be used as Timing Reference Priority 1

For all ADMs in the Network: Line 2 (LP2.1), will always be used as Timing Reference Priority 1 with Line 1 (LP1.1) as Priority 2.

The System Timing Mode must always be set to Locked.

Holdover or Free Running in the Timing State field indicates a fault in the Timing Distribution chain



6 Circuit Provisioning In the following sections the provisioning of circuits is explained. Since the ITM-SC is an element management system one has to create all individual Cross Connections, on all individual elements, across the circuit. Remember: STM-1 paths are connected directly, whilst VC-12 and VC-3 path must go via the LO-CC unit.

6.1 Connection Path Format Lucent paths are always provisioned in the following format: Worker LineTributary TerminationProtection Line Example 1: A protected VC-12 from the first port on a 2Mbit/s Trib card connected to port 2 on the LO-CC needs to be connected to the first channel on line port 1 and protected by the first channel on line port 2. LP1 is connected to LO-CC port 1, LP2 on LO-CC port 3. This connection would be written as:

CC1-1,111CC1-2,111CC1-3,111 Example 2: A protected VC-4 from the first port on a STM-1 Trib card in slot 8 needs to be connected to the third channel on line port 1 and protected by the third channel on line port 2. This connection would be written as:

LP1.1-3TP8-1LP2.1-3

6.2 ADM-U Cross Connect Capacity The CC capacity of each new ADM-U must be changed from the default setting of 64 to 128. 1. Select Provisioning->Transport->CC Capacity

2. Change the LO-CC capacity to 128 x VC-4. Select OK



6.3 Changing the TUG Structure of the Cross Connection Ports By default VC-4 Termination Points on the LO-CC are TUG-structured for 63 x VC-12. When a VC-3 needs to be transported via the LO-CC the TUG-structure of the port needs being changed to have at least one free TUG-3. Select: Provisioning>Termination Points(select port & VC4)...>TUG Structure>Edit 1. Select the first of the 21 TU-21 (in this example that is the 22nd TU-12 of the VC-4); 2. Then select the VC-3 tick box and the TU-3 appears instead of 21 TU-12s



6.4 Provisioning VC-4 Cross connection To provision a VC-4 Add Drop Cross-Connect from TP3.1 and CC1.5: BEWARE: Dont forget to enable monitoring for VC-4 Termination Points



6.5 Provisioning a VC-12 Cross connection To provision a VC-12 Cross Connect with SNCP-protection between the 2 LO-CC ports representing first port on E1-card in TS8 and the first timeslot in the AMS-ring. The following SNCP VC-12 has to be created: CC1.5,111CC1.19,111CC1.6,111



BEWARE: Dont forget to enable monitoring for Lower Order Termination Points; This can also be done directly via selecting TP2 in the above window



6.6 Manual Circuit Switching Using the Switch Button it is possible to switch the VC from Worker to Protection: Important Notes:

A forced switch will remain in its forced position regardless the status of the Received signal.

A Manually switched Cross Connection will automatically switch when there is a failure

Always return the circuit to Clear after switching



6.7 Cascading Cross Connections (Ring to Ring Connections) VC-12/3/4 Cascading cross connections are used when a circuit is routed between two rings terminated on the same homing node. This is commonly known within COLT as a 4-point switch. Instead of terminating the two protected paths each on their own termination point and connecting them together directly, the two protected paths are terminated on one Virtual Point which is called a Cascaded Cross Connect.

Cascaded Cross Connect

In the following example showing the next steps we have chosen:

Point A = CC1.9.111

Point B = CC1.11.111

Point C = CC1.10.111

Point D = CC1.12.111 1. Use the standard circuit provisioning procedure described in section 6.4 to connect Point

A to Point B and protect it with Point C.

Make sure you use the correct sequence in selecting the CC ports for the cascaded cross connect!

2. The remaining Point D has to be connected as a Cascaded Protection cross connect

using a virtual point. 3. Highlight the connection we have just added and press Edit.

HN

VP

Ring 1 Ring 2

Point A

Point C

Point B worker

Point D



4. Change the connection type to Virtual by selecting Add Virtual Point and press OK. 5. As can be seen above the connection has disappeared from the normal Cross Connect

List; it will show up again, including the newly created virtual point, when you select Cascaded Protection;



6. As can be seen above our original connection in now in 2 parts.

The original Ring 1 connection now has a virtual point A as its To (TP2) parameter.

The Ring 2 side has become the From (TP1) parameter of a new entry and has a virtual point B as its To (TP2) parameter.

7. Select the Ring2 part of the connection and press Edit. Now we can add the Point D

part of the connection:



6.8 Provisioning of a VC-4-4c Concatenated The ADM-16, ADM-U and ADM-C are capable of delivering 600 Mbit/s (aprox) leased line services using the STM-4 optical Trib card. In the SDH network these services have to be transported as four concatenated VC-4s. ITM- Before the actual VC-4-4c cross connects can be made the used TP and LP ports must first be grouped:

1. The first step is to Provision a Group of 4 AU-4s on one STM-4 Termination Point.

13

12

11

8

7

14

6

15

4

5

3

2

16

1

10

9

13

12

11

8

7

14

6

15

4

5

3

2

16

1

10

9

ST

M-1

6 p

ort

s

ST

M-1

6 p

ort

s

1 2 3 4

STM-4 TP

Straight through AU4-4c

Add drop AU4-4c



Notice the difference before and after the grouping: TP4.1,1 TP4.1,2 TP4.1,3 and TP4.1,4 have been grouped into TP4.1,1-4;

2. The second step is to Provision a Group of 4 AU-4 Termination Points on one of the

Aggregates.



3. The third and last step is to create the VC-4-4c Add Drop Cross Connect.



7 Maintenance Procedures

7.1 Alarm Listing In the screenshot below the Alarm List has been opened. In this window one can make a choice to see:

All current/outstanding alarms

All history/cleared alarms

Both current/outstanding alarms and history/cleared alarms 1. To view alarms select Events>Alarm List

2. Ticking the Show Time button will show the Time Raised/Cleared per Alarm, this can be

very useful when correlating alarms in the network.



3. Another useful feature is the Details buttonbar. Selecting this bar will generate a more detailed Information Window. In this window the user can request the ITM-SC system for a Probable Cause:



4. It is possible to refine your query in the Main Alarm List by applying Alarm Filters. On the right hand side window all filter options are depicted.

Other ways of obtaining filtered Alarm list are available in other parts of the ITM-SC Menu. For instance double-clicking an NE will result in an Alarm List with all outstanding alarms for that particular NE.

Training Manual

Documents

NR1402 ALU SDH Operations and Maintenance Procedures