1 Adding aN NE to a network 3

1.1 INTRODUCTION 3

1.2 PRECONDITIONS 4

1.3 IMPACT ON NE 5

1.4 IMPACT FOR THE NETWORK MANAGEMENT SYSTEM (NMS) 6

1.5 MIGRATION PREPARATIONS 7

1.5.1 The Migration at a Glance 10

1.5.2 Create the NE in NM Database 11

1.5.4 Physically add NE to the ring 12

1.5.5 Start Supervision of NE on 1353NM 14

1.5.6 Upload added NE 15

1.5.7 Disable Download on NEs 16

1.5.8 Add NE to the 1354RM Topology 17

1.5.9 Select Physical Connection to be split 18

1.5.10 Perform a Consistency Audit on all involved NEs 22

1.5.11 Perform Consistency Download on the QB3* 23

1.5.12 Download Enable for NMS 24

1.5.13 Datas on the existing traffic and the original configuration

OMSN to the target configuration OMSN. 24

1 ADDING A NETWORK ELEMENT IN A EXISTING NETWORK

1.1 Introduction

Overview This chapter describes the main process steps to be performed if a

Network Element has to be added to a network using the Split Physical

Connection tool on the RM. The main phases will be:

1. Name the Preconditions.

2. Describe Impact on NE.

3. Show Impact for the Network Management System (NMS).

4. Establish Migration Preparations.

5. Execute Add NE Migration Procedure.

1.2 Preconditions

Preconditions List

The following preconditions have to be met before starting with the Add

NE procedure:

The implementation state of the physical connection to split has

to be "implemented".

The technology of the physical connection has to be "sdh".

The working state of the HO-LC contained in the physical

connection has to be "normal".

The Physical port type of the 2 SDH ports of the new NE to be

inserted in the physical connection must be the same as the SDH

ports of adjacent NE.

The ring that contains the NE to insert and that contains the

physical connection has to have:

Working State = "normal"

Implementation State = "implemented"

The path status of all paths MUST NOT BE "commissioned".

They must be in "implemented" state.

The node to be inserted and the physical connection to be split

have to belong to the same topology.

The node to be inserted cannot be virtual

The switch position of all NE in the network must have the Switch

Position = "idle". If the state is "unknown" then perform a

synchronisation of the switch to reveal its state.

1.3 Impact on NE

Introduction This section describes the impact that adding an NE will have on any

other given NE, whether inside or outside the network. In this section,

the impact is described in terms of HW changes, SW upgrades, and

traffic interruption.

HW /SW Upgrades

A NE will be inserted into the network, modifying the existing network.

Therefore Hardware and Software upgrades are necessary on the NE to

be inserted in the ring if the following conditions have not been met.

The NE to be inserted must be able to operate in the network

The I/O interfaces to be used must be compatible with the I/O

interfaces of the adjacent NE to which it will be connected

Traffic Impact

The traffic impact must be check with the customer

1.4 Impact for the Network Management System (NMS)

Availability of Service

The impact on network services is dependant on the phase of the

migration discussed in the following two blocks.

Preparation Phase

During the preparation phase, all connections are fully managed,

including creating and deleting connections.

Migration Phase

The involved NEs are download disabled during the procedure.

The alarm management is not affected at all.

Time and Effort

The process of inserting an NE into a network takes time to perform.

The times are grouped to show the time necessary to update the

network and the time necessary to update the NMS.

Duration of

Operation

Configuration Mgmt.

downtime

AlarmSupervision downtime

Traffic downtime if protected

Preparation of NE

2 - 3hrs

Physically Add NE

1-10min - -< 50 ms prot.

NMS Add NE

1-2 hrs 1-2 hrs - -

1.5 Migration Preparations

Introduction It is essential to analyse and if necessary, modify the configuration of the

networkin order to minimise the impact to traffic and configuration of the

migration operation. The following chapter describes the steps to be

taken in order to prepare the network for the migration.

Pre-Migration Overview

The following list outlines the steps, which need to be completed in order

to prepare the operation. Before the migration can begin, these steps

must be completed.

Define the Equipment Configuration.

Analyse the DCN.

Define NE Address configuration.

Set the Connection Configuration ( optional)

Preparation of Synchronisation.

Preparation of I/O interfaces.

Perform Network backup.

Preparation of Slow Restoration.

Perform Consistency Notify Audit (optional).

Normally, it would not be necessary to perform Set the Connection

Configuration, Saving of Protection Mode and Adding Temporary

Protection. However, due to restriction on LO path it is advisable to

perform these steps for LO paths/trails.

Define Equipment Configuration

The new NE has to be configured before it can be inserted into the target

segment.

Therefore, define the equipment configuration tables from an ECT before

the NE can be inserted into the ring. The equipment configuration

defined with the craft terminal must correspond to the physical

equipment configuration in the subrack to avoid problems during the

migration.

Analyse the DCN

Analysis of the DCN must be done to ensure that a Q3 isolation (loss of

communication between NE and the management system) will not occur

when the target segment is disconnected. If it is foreseen that this will

happen, then the necessary steps need to be taken so that the

management information can be re-routed

Define NE Addr. Configuration

The new NE has to be configured before it can be inserted into the target

segment. The following tables, located on the NE to be added, have to be

configured from an ECT before the NE can be inserted into the ring.

1. Define Local Configuration Table.

2. Define OS Configuration Table.

3. Define LAPD Configuration Table.

4. Define Ethernet Configuration Table.

5. Send to the NE the updated Tables.

Set Connection Config. for QB3* NE

The actions described below are recommended on QB3* NE only if you

want a minimal perturbation in case problems occur with the network.

They have to be done from the craft terminal as described below.

1. Select Connections Configuration (or Connections with Full Matrix)

from the Application Menu.

2. Select in the Menu: File Default Status.

3. Save this Default Status with a chosen name and send it to the NE.

4. Set all the West and East Aggregate Payload structures, signal

labels and configure the AU4 pass through. Thus, when the NE will

be connected to the network.

These actions must be performed on Q3 equipment only from the craft

terminal.

1. Create pass through cross-connections for the I/O interfaces

that will be used to connect the adjacent NE.

Thus, when the NE will be connected between the rings, in case of

problems the traffic can be restored passing through the new NE.

Remember to set-up the pass through connections for any AU4-

4C, AU4-16C paths, etc.

Preparation of Synchronisation

The synchronisation of the NE in the ring must be performed in a way that all the NE (including the new one) are synchronised after the insertion of the new NE.The table below describes what to do:

1. Analyse synchronisation sources and settings within the ring and on the attached NE.

2. Make sure that every ring NE will still be synchronised when the new NE is inserted and if necessary change the synchronisation sources or priorities in existing NE.

Preparation of I/O interfaces

The next process steps will ensure that the optical/electrical parameters are within the defined limits when the new NE is inserted into the target segment.

1. Check that the I/O interfaces of the new NE are compatible with the NE connected currently by the target segment, e.g. check that the optical wavelengths are compatible

2. Check that the optical power budget on the receivers of all 4 involved I/O interfaces will not exceed given limits when the new NE is inserted between the NE currently connected by the target segment.

3. Install optical attenuators if the optical power on a receiver will exceed the maximum power limit. This can be done when the NE is physically being added in chapter Error: Reference source not found in order to avoid additional traffic hits.

4. Check that the ALS is configured on all 4 I/O interfaces to be connected.

Perform Network Backup

Before starting the Add NE procedure it is advisable to perform a full network backup so that it will be easy to restore the network in case of an inexplicable failure. Use RM to perform it.

Disable Slow Restoration

The slow restoration rule enables the NMS to find another alternate protection route in case a failure of path or trail is detected. Therefore, in order to ensure that the NMS does not interfere with the protection switching activities performed by the field operation engineer, you have to disable any slow restoration rule that has been configured.

Perform Consistency NotifyAudit(optional)

Before starting the procedure, it may be useful to perform a consistency notify audit on involved NE and check misalignments in order to ensure that there are no misalignments before migration. So if there are some after the migration, it will be easier to identify when and which one occurred.

1.5.1 The Migration at a Glance

Migration Steps Overview

The procedure for the addition of an NE involves the following main

steps:

1. Create NE in NM Database

2. Physically add NE to the network

3. Start Supervision of NE on 1353NM

4. Upload added NE

5. Disable Download on NEs

6. Add NE to the 1354RM Network

7. Select Physical Connection to be split

8. Perform a Consistency Audit on all involved NEs

9. Perform Consistency Download on the QB3*

10.Download Enable for NMS

1.5.2 Create the NE in NM Database

Create NE on 1353NM

The process steps in the next table must be done BEFORE the physical addition of the NE. It details the steps to create the NE in the NM database.1. Select Declarations Create NE on the NM map menu.

2. Select Family, Type and Release fields.

3. Fill in the User Label and Location Name fields.

4. Press Apply and when new icon appears on the NM map, close the creation window.

5. Select the new NE on the NM map.

6. Select Declarations Set addresses NE address from the NM map menu and set the NSAP address plus Q3 logical number if QB3* NE.

IF NE_type = QB3*

Then Else

7. Open the equipment view of the NE -

8. Set up the board configuration of the NE in the NM database to match the physical configuration of the real NE.

-

9. Ensure that the Equipment controller type for the NE is the same as the actual equipment controller as problems may arise if the equipment controller has not been correctly set.

-

1.5.3 Physically add NE to the ring

Introduction In this process step, the new NE will be inserted into the target segment between NE34 and NE160. The activities are purely physical doing the cabling between the NE only as long as the I/O interfaces are compatible.The reason for physically inserting the NE in the ring at this stage is to make the NE reachable before performing the split physical connection in order for the RM to determine whether the ports of the new NE support AU4-4C.Performing the migration in this manner (i.e. make the NE reachable before doing the split physical connection) is better because it avoids the use of the simulator for Q3 NE. Again, this procedure can be applied to QB3* as well as Q3 NE.

Disconnect NE A from NC

In order to insert the NEB into the ring, NEA and NEC must be physically disconnected.

1. Physically disconnect NEA East – NEC West.If trib cards are used instead of aggregates (e.g. 1650SMc) then disconnect the trib cards.

Connect NEB to NEA & NEC

It is now possible to insert NEB into the network and to connect the I/O interfaces.

1. CHECK that the optical power budget will not be exceeded before inserting NE128 in the ring.

2. IF Power level too high

Then Else

Install optical attenuators temporarily on NEB.If it is needed then the Long haul I/O interfaces can be replaced with short haul I/O interfaces after the migration. See chapter Post Migration: Change Optical Interfaces

-

3. Physically connect NEB East – NEA West

4. Physically connect NEB West - NEC East

The Alarms, which occurred as a result of the cable break, should now all be cleared.After Step 4. CPE (Communication Protocol Error)/K1-K2 Mismatch alarms appear on the adjacent NE ports due to NE128 presence.

1.5.4 Start Supervision of NE on 1353NM

Introduction Now that the new NE has been inserted in the ring, it is time to start the supervision from the NM in order to properly implement the configuration changes into the network.

Start Supervision

The following steps details the procedure to start supervision of the new NE on the 1353NM

1. Verify that the NE can be pinged by using the Administration tool (If it's not reachable, it probably means that there are some problems with the DCN or the NE addresses that have not been correctly set-up - this has to be fixed first)

2. Select the added NE on the NM map.

3. Select Operations Supervision Audit/AlignUp/NoAlignment according to the NE and click Apply from the NM map menu.

4. If Supervision has started successfully

Then Else

Close the window. Ignore any misalignment messages. This will be removed by the global download from the RM.

Wait few minutes andre-try

1.5.5 Upload added NE

Synchronise EML

The steps below are needed in order to upload the ports for Q3 NE.

1. Select 1354RM icon in the 1354RM User Interface

2. Select Actions Search Main Related items... (A new window opens)

3. Select EML Domain Nofilter

4. Select the EML containing the new NE and perform a synchronisation of the EML using Actions Synchronise Synchronise EML

Upload new NE in RM Map

Follow the procedure below to upload the new NE onto the RM Map

1. Open the RM User interface (Browser) and navigate to the Ring in which the NE will be inserted.

2. Select Actions Create Node, a wizard window opens.

3. Select the node to upload in RM by means of the “….” icon.

4. Click on Finish button

5. Click on Cancel once the operation is finished.

1.5.6 Disable Download on NEs

Warning the “Download Disable” must be performed only on the node to be

inserted/added.

Introduction To add the new NE to the ring, it is necessary to disconnect the management control between the NML and the NE to avoid traffic perturbations. This is achieved by setting Download=Disable to the NE.The Virtual EML Domain (VNE) is not concerned with this procedure

Set Download =Disable

Now configuration download can be disabled to all involved NE on the RM to ensure no configuration data are downloaded to the NE until all settings have been verified. By involved NE we include all NE of the network plus the NE to be added.

The actions to disable the download are also used in the ‘Remove NE Procedure’. For this reason, please refer to Error: Reference source not found of this document.

!

1.5.7 Add NE to the 1354RM Topology

Introduction The following actions describe the procedure to be performed when adding an NE to the network on the 1354RM. Below is an overview of all the actions to be performed. It is followed by a more detailed procedure.

Add NE overview

1. Perform a synchronise EML action for the EML containing the new NE in order to upload the ports. This is necessary for Q3 NE.

2. From the browser, obtain a list of all the physical connections in the target ring

3. Select the physical connection to be split

4. Start the Split physical connection application

5. The procedure must be executed successfully before continuing with the next chapter.

Start Add NE Procedure

The procedure below details the actions to be performed when adding a NE to a network. All the actions performed below have been performed from the RM using the Split physical connection tool in the Browser (RM User Interface).

Synchronise EML

The steps below are needed in order to upload the ports for Q3 NE.

1. Select 1354RM icon in the 1354RM User Interface

2. Select Actions Search Main Related items... (A new window opens)

3. Select EML Domain Nofilter

4. Select the EML containing the new NE and perform a synchronisation of the EML using Actions Synchronise Synchronise EML

1.5.8 Select Physical Connection to be split

Display Rings

Follow the steps below to display the physical connections

1. Select 1354RM icon in the User Interface then perform Actions Search Main Related items... (A new window opens)

2. Select Network Nofilter (The Network icon is dropped into the 1354RM User Interface)

3. Select the Network icon then Actions Search Main Related items..(A new window opens)

4. Select NPAs(A new window opens)

Select Physical Connections to be split

Follow the procedure below to select the physical connections to be split.

1. In the 1354RM User Interface, select the ring icon Actions Search Main Related items...(A new window opens)

2. Select All physical connections noFilter(A new window opens containing a list of all the physical connections in the ring)

3. Select the physical connection to be split as shown in the diagram below

Figure 5-1: Select Physical Connections to be split

Select Node to insert

Follow the steps below to select the nodes to insert

1. Start the split: Actions Topology modification Split physical connection.A new window opens as shown below

2. Select the box containing the 3 white dots next to the box 'Please select a node to insert' (A new window opens as shown below)

3. Select the Node which will be inserted Apply (The selected node is dropped in the Split physical connection box)

4. Select Next (A new window opens as shown in Figure 5-8)

Select Ports Continue with the steps below to select the SDH ports which will be used in the new physical connection

1. Select the box containing the 3 white dots next to the block 'Selected port'(A new window opens as shown below)

Select Ports continued…

2. Select the first port to be used by the NE to be inserted Then select Apply (The object is dropped into the box as shown below)

Figure 5-2: Selected port is dropped into the box

3. Enter the new user label for the first physical connection under 'Please specify the new userlabel and then click on the Next button(A new window opens)

4. Select the box containing the 3 white dots next to the box 'Selected port'(The same window as shown in figure 5-9 above opens)

5. Select the second port to be used by the NE to be inserted Then select Apply (The object is dropped into the box as shown in figure 5-10)

6. Enter the new user label for the second physical connection under 'Please specify the new userlabel Next (A new window opens containing all the information provided as shown in figure 5-11)

Start Split Physical Connection

Continue with the steps below to start the split physical connection action

1. Check that all the information is correct then select Finish (A new window opens containing a report of all the ongoing actions as shown below)

2. Once the end message 'Operation successfully Terminated' will appear twice.is received select Cancel

Confirm successful completion

To confirm whether the action has been successfully performed, you can check the Et view related to the target Ring (ET). Use RM User Interface to open it and drag and drop the added NE to the main area.

Unsuccessful Split Physical Connection

Follow the procedure below if the split physical connection action was unsuccessful

If the action is not successfully terminated e.g. if any of the following messages like failed to disconnect, failed to split, failed to connect appear:

THEN ELSE

1. Return to list of physical connections

2. Select the physical connection which failed to split

3. Enter the requested information and continue with the undo split action.

4. Undo the action with Actions Topology modification Undo Split physical connection

5. Perform the split physical connection procedure again until it is successful

If problems persist, contact the TEC support center

1.5.9 Perform a Consistency Audit on all involved NEs

Warning the “Download Disable” has been performed only on the node to be added.

Introduction It is necessary to perform a consistency audit on all the involved NEs including the newly inserted NE in order to assure that all information in the network matches the information in the NMS.

We have also to do specific operations on QB3* NE due to different behaviour than Q3.

Perform Consistency Audit on QB3* NE

Due to migration restriction (see chapter Error: Reference source not found), it will be necessary to perform an Audit on all QB3* NE in the network (adjacent NE included). So, follow the procedure below.

1. Disable the download for all QB3* NE if not yet done (it is supposed to be done).

2. Perform the consistency Audit as outlined in, Error: Reference source not found, for all QB3*

Perform Consistency Audit on Q3 NE

Refer to Error: Reference source not found to perform the consistency Audit on all the ring NEs plus the NE to be added.Ignore the misalignments in the added NE but analyse the misalignments on the adjacent NE before continuing.Check the “Not aligned Objects” of each NE.

If the message some layers skipped appears, re-do the consistency Audit.The misalignments, which are likely to appear for the adjacent NEs are those with the following attributes:

ringMapinfo

MSProt.Block configuration stateThese misalignments are due to the addition of the new NE, which means that the information about the 2F-MSSPRING topology for each NE in the ring has to be updated in order for the 2F-MSSPRING topology to continue to function properly.

!

1.5.10 Perform Consistency Download on the QB3*

Introduction The consistency download verifies the misalignments between the NML and EML and performs the corrective actions using the NML database as the reference. It is advisable to perform a consistency download on the two adjacent NE, i.e. NE34 and NE160, if they are QB3* and even if no misalignments were found. In this way the operator can be sure that there are no existing misalignments. It is more a security but should be useful.It will be necessary to perform a consistency download on the newly inserted NE in order to ensure that all information in the NMS as well as the network has been updated only if it is a QB3* NE. Moreover, for all QB3* of the 2F-MSSPRING ring a global download is also needed if misalignments were found in 1.5.9 and you did not perform the global download yet.

Perform Consistency Download

Follow the procedure below to perform a consistency download on NE after all misalignments have been analysed. Return to the browser window containing all the involved QB3* NE.

QB3* NE1. Open the process monitoring

window and Actions Set Run Level 1354RM NetworkConsistency

2. Select the NE, which has been added to the ring.

3. Right click the mouse Consistency Download Global then confirm.

4. Wait until the action has successfully completed

5. Repeat steps 2-4 for all QB3* NE

Set the Run level back to Full functionality by:

6. Open the process control monitor window

7. Actions Set Run Level FullFunctionalityWait until the action is completed

NOTE: When download is enabled, a switch of the 2F-MSSPring may occur depending on the cases.

1.5.11 Download Enable for NMS

Warning the “Download Enable” has to be performed only on the node to be

inserted/added, because it has been disabled for this node only.

Introduction All the necessary configuration changes have been made to the newly added NE by the global configuration download action. In order to send these configurations to the physical NE in the network for QB3* and/or Q3 NE, it will be necessary to enable the download mode for all the involved NEs. This will also allow the user full operational access of the NMS.

Enable Download

It is necessary to enable download on all involved QB3* and Q3 NE in the RM (all NE of the ring containing the ‘Added NE’) to ensure the network is properly updated due to the introduction of the newly inserted NE. The steps to enable the download are also used in the Remove NE procedure. For this reason, please refer to Error: Reference source not found of this document.

NOTE: For Q3 the download is to be enabled- first for the added NE- second for all the other involved NEs

If ghost alarms are present, we must perform a synchronize alarms on the NE.

From the RM, select the relevant node in the browser, then select: Actions Option Synchronization All AlarmsFrom the NM: Supervision Alarms Resynchronization

!

Post Procedure

Introduction Now that the procedure is complete, some additional actions can be performed.

Split Trail for trails passing through the newly added NE (Not 1664SM nor 1670SM)

Synchronise AU4-4C

Restore “Restoration Status”

Change Optical interfaces

Split trail After the physical connection has been split and in order for the customer to use the LO resources of the newly inserted NE, the HO-Trail crossing the inserted NE must be split.After the split physical connection operation, all the HO Trails that were starting/ending at NEA and NEC will remain HO Trails starting/ending at NEAand NEC i.e. the original HO Trail is modified and a pass through is created on NEB . This means that if the operator wishes to create a LO path starting /ending at this newly inserted NE, it will not be possible to do so due to the Pass Through. In this case the user has to split the trails passing through the NEB. Follow the procedure below:

NOTE: It is not possible to split a trail, which passes through a 1664SM/1670SM, as this is not supported by these NE. Also, when defining names for the newly created trails, do not use existing trail labels.

1.Disable the download on the NE involved in the trails (target NE plus adjacent for security).

2.Obtain a list of all the trails passing through NEB and select one trail in the 1354RM User Interface.

3.Split the trail Actions Modification Split. From 1354RM User Interface

4.Execute Actions start split after filling in the necessary information in the split trail window. A new window opens

5.Select the node at which the trail will be split (i.e. node to be added) and click Ok button.

6.Wait for the message in the dialogue box Action is correctly executed.

7. Verify that the new trails are created.

8. Repeat steps 2 to 8 for the other trails.

9.

Re-enable the download. This operation is traffic affecting. The traffic-loss time is bounded by the time interval necessary for downloading a new set of configuration tables on the NE (i.e. 30s-2mn).

Now it will be possible to create paths starting/ending from target NE128. REMEMBER to upload the NAPS first.

Synchronise AU4-4C

After the physical connection has been split it may be a good idea to ensure that the physical connection supports AU4-4C (for NE that support AU4-4C). In order to do this, perform the following steps:

1. Select one of the newly created physical connection

2. Actions Display Main related items... Physical connection structure noFilter

3. Select the MS icon in the view

4. Synchronize the concatenated rates set-up Actions Configuration Supported Conc. AU4

5. Repeat steps 1 to 4 for the other newly created physical connections

Restore the Restoration status

The restoration status can now be changed to its original setting. Refer to data, which were saved in the preparation for information on which trails and paths to perform the action.

Change Optical Interfaces

If, during the preparation phase of the migration, optical attenuators were installed on the NE because the optical power budget exceeded the given limits, it should now be possible to follow a new procedure to change the optical interfaces, which are connected to the new NE, from Long Haul to Short Haul. Note that this procedure is optional. The customer can choose to keep the attenuators.

1.5.12 Datas on the existing traffic and the original configuration OMSN to the target

configuration OMSN.

You will find attached an excel file below.

On the first sheet, you will find the datas on the existing circuits to check before and after the operation.

On the second sheet, you will find the datas on the original configuration and the target configuration.Inside the sheet, you will find some details on the connections to do.

First Stage: create the circuit on the new OMSN.Second Stage: insert the new equipment in the Network.Third stage: create this new element on the NMS.4th Stage: connect the differents cables as foreseen on the Excel file.5th Stage: Check the differents circuits and impact foreseen on the traffic.6th Stage: Create the circuits missing due to the implementation of the new equipment7th Stage: Check with the traffic matrix if all circuits are risen.