atm to ip migration instruction rnc

ATM to IP Migration InstructionRNC

OPERATING INSTRUCTIONS

Copyright

© Copyright Ericsson AB 2007. All rights reserved.

Disclaimer

No part of this document may be reproduced in any form without the writtenpermission of the copyright owner.

The contents of this document are subject to revision without notice due tocontinued progress in methodology, design and manufacturing. Ericsson shallhave no liability for any error or damage of any kind resulting from the useof this document.

58/1543-FAB 102 614 Uen B 2008-02-26

Contents

Contents

1 Introduction 1

1.1 Target Group 2

1.2 Prerequisites 2

2 Overview 5

2.1 Iu and Iur Control Plane 5

2.2 Iu-PS User Plane 6

2.3 Network Synchronization 7

3 Hardware Preparations 9

3.1 Add ET-MFG 9

3.2 Add ET-MFX 11

4 Iu-CS Control Plane 17

4.1 Preparation 18

4.2 Cutover 26

4.3 Migrate Iu-CS Control Plane 27

4.4 Tidy up 27

5 Iu-PS Control Plane 29

5.1 Preparation 30

5.2 Cutover 38

5.3 Migrate Iu-PS Control Plane 39

5.4 Tidy up 39

6 Iu-PS User Plane 41

6.1 Preparation and Cutover 42

6.2 Install ET-MFG and Migrate Iu-PS User Plane 47

6.3 Tidy Up 53

7 Iub Control Plane and User Plane 55

7.1 Prerequisites 55

7.2 Preparation 55

7.3 Cutover 64

7.4 Tidy Up 64

58/1543-FAB 102 614 Uen B 2008-02-26

ATM to IP Migration Instruction

8 Iur Control Plane 67

8.1 Preparation 67

8.2 Cutover 75

8.3 Migrate Iur Control Plane 75

8.4 Tidy up 76

9 Iur User Plane 77

9.1 Preparation for Iur User Plane over IP (ET-MFG AlreadyInstalled) 77

9.2 Cutover 80

9.3 Migrate Iur User Plane 81

10 MUR 83

10.1 Preparation 83

10.2 Migration 84

58/1543-FAB 102 614 Uen B 2008-02-26

Introduction

1 Introduction

This document describes the steps in the migration process from an ATMbased transport network to an IP over Ethernet based transport network or toa mixed network. IP over Ethernet can be introduced in the Radio NetworkController (RNC) node using ET-MFG and ET-MFX interface boards.

Note: In this release of RNC (P6) it is not possible to use IP over Ethernettransport links for Iu-CS user plane.

The higher-level signaling protocols—RANAP, RNSAP and NBAP—are notdirectly affected by the kind of transport links used (ATM or Ethernet). However,there may be some disturbances on these protocols during the migrationprocess. These disturbances are described in each corresponding chapter.

It is possible to migrate the connections in an RNC node in different orders.

Note: It is possible to install the ET-MFG boards in parallel with the Iu-PSuser plane migration. For SS7 over Ethernet, however, the ET-MFGboards must be installed prior to performing the migration.

This document describes the preparation and migration of the RNC to useIP over Ethernet links instead of some ATM links, and the recommendedconfiguration for IP over Ethernet links. The following procedures are included:

• Hardware

Add ET-MFG (This includes Reallocation of Connections and Adding aBoard)

Add ET-MFX

• Preparation

Iu-CS control plane

Iu-PS control plane and user plane

Iur control plane and user plane

Iub control plane and user plane

Mur

• Migration

Iu-CS control plane

Iu-PS control plane and user plane

Iur control plane and user plane

158/1543-FAB 102 614 Uen B 2008-02-26


Iub control plane and user plane

RNC part

Mur

• Tidy up

Caution!

The preparations described in this document must be completed before startingthe migration.

The migration should be done during low traffic, because of traffic disturbancesthat may occur during the migration execution. Each of the procedures in thisdocument contains information about where these disturbances may occur.

1.1 Target Group

This document is written for the following groups:

• Personnel working with the transport network configuration management ofthe RNC node.

• Personnel working with transport network planning.

1.2 Prerequisites

The following prerequisites are assumed:

• The RNC node is equipped with P6 software.

• Two ET-MFG boards are available if Iur or Iu will be migrated. It is alsorecommended that at least two ET-MFX boards are available if Iub willbe migrated.

• Everything needed to replace an ATM board with an Ethernet board isavailable. See the Transmission Board Change document.

• The dimensioning of the RNC is in accordance with the DimensioningDescription document.

• The IP over Ethernet transport network has been prepared and is ready tobe connected with the RNC node.

• The remote nodes have been prepared for the migration.

2 58/1543-FAB 102 614 Uen B 2008-02-26

Introduction

• All IP addresses are allocated according to the WCDMA RAN documentIP Transport Network Configuration

• The use of OSS-RC is available to perform the actions in this instruction(recommended).

Ensure that you have read the following WCDMA RAN documents:

• IP Transport Network Configuration

• Introduction of IP Transport in WRAN

358/1543-FAB 102 614 Uen B 2008-02-26


4 58/1543-FAB 102 614 Uen B 2008-02-26

Overview

2 Overview

2.1 Iu and Iur Control Plane

This section describes the Iu control plane and the Iur control plane. Forsignalling Iu-CS, Iu-PS and Iur control plane must share the same IpInterface.

2.1.1 Signaling Connections That Can Be Migrated to Ethernet Links

The following signaling (SS7) connections may be migrated individually or incombination:

• Iu-CS control plane connections

• Iu-PS control plane connections

• Iur control plane connections

During the migration process it is possible to have both an ATM link and anEthernet link configured for control plane connections to the same remotenode. However, ATM and Ethernet links will not work in load sharing mode.This means that one of the links can be configured as the active link, and theother link can be configured as a standby link. When the links are configuredthis way, if the active link goes down, the backup link will be used instead.

For large networks it may be impractical to migrate the complete transportnetwork to IP over Ethernet in one step. For instance, there may be many Iurcontrol plane connections making it difficult to migrate them all at once. Or theremay be many Core Network (CN) nodes connected with the RNC (also calledIuFlex), and not all of the CN nodes can be migrated at the same time. Tomake the migration process easier, it is possible to migrate only a subset of theremote node connections to ET-MFG. The remaining remote nodes will still beconnected through ATM links (and possibly migrated in the future to ET-MFG).

Migration of SS7 connections can be done separately from migration of anyIu-PS user plane connections. It is also possible to separately migrate Iu-PS,Iu-CS, and Iur control plane connections.

Note: Except during the migration process, having a mixed configurationof both Ethernet links and ATM links for the same remote node SS7connection is not recommended.

2.1.2 Multi-Homed SCTP End Points Supported in the Core Network

Make sure that multihomed SCTP end points are supported in the core network.In RNC, multihomed SCTP is characterized as follows:

558/1543-FAB 102 614 Uen B 2008-02-26


• Two IP links are associated with an SCTP host. One of the IP links isactive and the other is standby. If the active link fails a switch-over isautomatically made to the standby link.

• In the RNC the two IP links connected with the SCTP host are configuredon different ET-MFG boards. This means that if one ET-MFG board fails,the other ET-MFG board will be able to handle all the control plane traffic.

• Only one SCTP host is needed in the RNC for Iu and Iur. The SCTP host isconfigured on the active SCCP Main Processor (MP). If the active SCCPMP fails, the standby SCCP MP will automatically take over the handling ofthe SCTP host.

• Only one M3uAssociation Managed Object (MO) instance is needed perexternal node relation to achieve the necessary redundancy on the RNCside. This depends on the remote node supporting multiple Sctp.

The SCTP multi-homing feature is an important mechanism that providesan end-to-end redundancy. As a complement to this mechanism it is alsorecommended that Router Path Supervision (rps) be used to supervise therouters connected with the RNC. The SCTP multi-homing mechanism istypically configured to act quicker (within 300 ms for example) than rps. Onthe other hand, rps can handle certain multiple failures faster than SCTPwith multi-homing. Therefore it is recommended that both rps and SCTPmulti-homing for SIGTRAN be used.

2.2 Iu-PS User Plane

This section describes the Iu-PS User Plane.

2.2.1 If Iu-PS User Plane Connections Will Be Migrated to Ethernet Links

Any number of Iu-PS user plane connections can be migrated from ATM toEthernet links.

If many CN nodes are connected with the RNC (also called IuFlex), it maybe impractical to migrate the complete transport network to IP over Ethernetin one step. To make the migration process easier, it is possible to migrateonly a subset of the CN node connections to Ethernet links. The remainingCN nodes will still be connected through ATM links (and can be migrated inthe future to Ethernet links).

Migration of Iu-PS user plane connections can be done separately frommigration of any SS7 connections.

It is possible during the migration to have both ATM links and Ethernet linksconfigured to the same Packet Switched (PS) CN node, and these links will beused simultaneously in load sharing mode.

6 58/1543-FAB 102 614 Uen B 2008-02-26

Overview

Note: Except during the migration process, having a mixed configuration ofboth Ethernet links and ATM links for the same remote node Iu-PSuser plane connection is not recommended.

2.3 Network Synchronization

Make sure that Network Synchronization of the RNC is provided from atleast two separate sources after the removal of the ATM ET boards. See theWCDMA RAN Synchronization document for a description of synchronizationfunctions within the WCDMA Radio Access Network (RAN). This may requirethat a new synchronization link is configured on an existing ATM ET board thatwill not be replaced by an ET-MFG board.

758/1543-FAB 102 614 Uen B 2008-02-26


8 58/1543-FAB 102 614 Uen B 2008-02-26

Hardware Preparations

3 Hardware Preparations

This section describes the introduction of ET boards used for IP migration.

3.1 Add ET-MFG

Take the following steps to prepare for the migration:

• Decide which slots to use in the main subrack for the two ET-MFG boards.

• Make sure that network synchronization is provided on the ET boardsthat remain after the migration. Change the synchronization source ifnecessary. See the WCDMA RAN Synchronization document for moreinformation on synchronization requirements.

• Perform reallocation of connections if necessary. These connections mustbe reallocated to other ATM ET boards if they are currently allocated to thetwo ET boards that will be replaced by ET-MFG boards.

If reallocation of connections is required, it must be done before theET-MFG integration starts.

It is possible to free a slot in the main subrack that is occupied by an ATMboard by moving Iub traffic to an extension subrack.

• Complete the replacement according to the Transmission Board Changeinstruction.

• Decide whether to use one or both of the two Ethernet ports on theET-MFG board.

To provide redundancy, two ET-MFG boards must be installed in the mainsubrack of the RNC. If there are no empty Exchange Terminal (ET) boardslot positions, it is necessary to identify which ATM ET boards to replacewith ET-MFG boards. See the Hardware Configuration Data document forinformation about ET board configurations. An example is shown in Figure 1on page 10: two ET-MFG boards, marked as X and Y, are installed in slotpositions 24 and 25.

958/1543-FAB 102 614 Uen B 2008-02-26


X Y

24 256 7 26 27

C0001424A

Figure 1 The Main Subrack with Allowed Slot Positions for ET Boards.

Note: It is possible to plug the two ET-MFG boards into slots 6, 7, 24, 25,26, or 27 in the main subrack. However, the recommended slots are24 and 25.

If necessary it is possible to save slot positions by first replacing existing ET-M4boards with the more powerful ET-MF4 boards. This board can be used tocarry more traffic after reallocation. After this replacement has been done, theET-MFG boards can be installed in two empty slots.

3.1.1 Reallocation of Connections

If two ATM ET boards must be replaced to free up slots for the ET-MFG boards,it may be necessary to reallocate the connections that are allocated to theseATM ET boards. This means that these connections must be moved to otherATM ET boards that will remain after the migration.

Note: If Iu-PS user plane connections are migrated to ET-MFG, it is notnecessary to reallocate these connections to other ATM ET boards.See the procedure description in section 6.2. In this case traffic wouldbe down until the end of the procedure.

3.1.1.1 Reallocate Connections in the Main Subrack

Reallocation of connections is required in the following cases:

• If an Iu-CS user plane connection is allocated to the ET boards to bereplaced.

• If an Iur user plane connection is allocated to the ET boards to be replaced.

• If any of the Mu connections (Mur, Mub, Mut) are allocated to the ETboards to be replaced.

• If an Iub connection is allocated to the ET boards to be replaced.

• If a signaling connection (Iu-PS, Iu-CS, and Iur control plane connections)is allocated to the ET boards to be replaced.

10 58/1543-FAB 102 614 Uen B 2008-02-26


• If Iu-PS user plane connections will remain ATM based and they areallocated to the ET boards to be replaced.

• If a Network Synchronization reference is allocated to the ET boards tobe replaced.

3.1.2 Add Board

If telecom grade IP infrastructure is used there is no need to use both ports oneach ET-MFG, but if simple single point of failure routers or switches are used itis advisable to connect both ports, to limit fault spreading.

Redundancy can be achieved on different levels for ET-MFG connections. Themost important redundancy mechanisms are listed below in no particular order:

• Using more than one port on the ET-MFG board. If one Ethernet portfails because of an Ethernet link failure between the RNC node and theconnected switch or router, then the secondary Ethernet port will be able totake over the traffic.

• Using more than one ET-MFG board. If one ET-MFG board fails, the otherET-MFG board is available to handle the traffic.

For Control Plane this will be handled by SCTP multi-homing, which in caseof failure will automatically switch-over to another IP address on anotherET-MFG board.

For Iu-PS user plane traffic this will be handled by configuring several Iu-PSuser plane connections that can serve traffic in load sharing mode. If oneET-MFG board fails, the connections that are associated with the otherET-MFG board will be able to handle all the traffic.

• Connecting the RNC to more than one router through different Ethernetpaths. This will ensure that if a router is disabled or if there is a link failureat the IP level, traffic will still be able to go through the other path.

To add an ET-MFG board follow the instruction in Transmission BoardExpansion.

3.2 Add ET-MFX

The ET-MFX is used for Iub traffic, and possibly Mub. The ET-MFX boards canbe installed in any free slot designated for ET boards. In the main subrack, slots6, 7, and 24 to 27 are used for ET boards. In the Extension subracks slots 2 to5 and 24 to 27 are used for ET boards.

It is recommended to chose an ES for the ET-MFX boards. While there aresome ET boards that must be in MS, the number of ET slots in MS is lower thanin ES (6 versus 8). As a result, the MS runs the higher risk of running out of ETslots that might be needed for capacity expansion.

1158/1543-FAB 102 614 Uen B 2008-02-26


Each ET-MFX contains an on-board Ethernet switch connected to sevenconnectors on the front panel. Connecting several ET-MFX boards togetherusing cables on the front panel creates an Ethernet network.

Figure 2 on page 12 shows a simplified view of an RNC with ET-MFX boards.Each ET-MFX has seven Ethernet connectors on the front panel, shown asfilled circles for electrical connectors, and non-filled squares for SFP, a slot thatcan be equipped with an optical connector. In this figure, extension subracks1 and 2 each contain three ET-MFX boards, two for full capacity and one toprovide redundancy, in case one of the boards fails. The main subrack containstwo ET-MFX boards, one for full capacity and one to provide redundancy.

ET-MFX13ES2

Main cabinet

ES1

MS

ICF

ET-MFX12

C0001423A

Figure 2 C Node with Seven ET-MFX12 and One ET-MFX13

Two slightly different variants of ET-MFX can be used in the RNC:

• ET-MFX12 has six electrical connectors and one optical

• ET-MFX13 has one electrical connector and six optical.

The maximum number of ETs in any subrack is six. This maximum holds alsofor ET-MFX. In a normal configuration two slots in the main subrack will beneeded for ET-MFG, which leaves a maximum of four slots for ET-MFX inthis subrack.

12 58/1543-FAB 102 614 Uen B 2008-02-26


The ET-MFX13 variant will be delivered only as an upgrade kit, and cannotbe ordered factory installed.

The electrical ports use EMILY connectors. Each port adapts to the transferspeed of the opposite end of the line in a range between 10 Mbps and 1000Mbps.

The optical ports are SFP slots. This provides a flexibility in choice oftransmission standards. For supported SFPs add link to ET-MFX UnitDescriptions (UDs). Each module contains an optoelectrical conversion unitand a connector.

Connecting Ethernet cables to the connectors normally creates a network thataggregates traffic from several ETs to a few lines that are connected to the offsite transmission resources. It is also possible to use the ET-MFX network tohandle traffic in a large number of off-site transmission lines. Transmissionlines external to the RNC are normally connected via the ICF but can also beconnected directly to the ET-MFX front panel.

3.2.1 Redundancy

Rapid Spanning Tree Protocol (RSTP) is used for protection switching in theEthernet network, so that a failure in a single board does not stop the trafficfrom any other board and so that for any one failing link there is always acombination of other links that can transfer the traffic.

One phase in the RSTP algorithm selects one of the switches to be the rootnode in the tree network that is to be built. This choice is based on the bridgepriority value that is set in each switch and the MAC address of the switch.Normally one of the switches that is connected to the main external transmissionline should be the root switch. The operator chooses freely between the two.Then the attribute bridgePriority in the MIB for that switch is set to a value thatis lower than the default value. This could be done using OSS/RC.

3.2.2 Managed Objects

The objects represented by white boxes in Figure 3 on page 14 are createdby the RNC EM Expand RNC Tool (the white boxes with double frame arecreated indirectly). The objects represented by grey boxes with a double frameare created by auto configuration. The objects represented by grey boxes areincluded only for reference.

1358/1543-FAB 102 614 Uen B 2008-02-26


PlugInUnit

IpSystem

GigabitEthernet

1 11 1

1

0..7

1

IpInterface IpTrafficDescriptor

EthernetSwitch

EthernetSwitchPort

ExchangeTerminalIp EtMfg

InternalEthernetPort

SwitchStp

SwitchPortStp

C0001425A

1 1

Figure 3 The Ethernet Transport in RNC MOM View

The new object that represents the ET-MFX board, created by autoconfiguration (grey box with double frame), is as follows:

• ExchangeTerminalIp

New objects that represent parts of the ET-MFX board, created by the RNC EMExpand RNC Tool (white boxes without double frame), are as follows:

• EthernetSwitch

• EthernetSwitchPort

• InternalEthernetPort

New objects that represent parts of the ET-MFX board, created indirectly by theRNC EM Expand RNC Tool (white boxes with double frame), are as follows:

• SwitchStp (created automatically whenever an EthernetSwitch instance iscreated)

• SwitchPortStp (created automatically whenever an EthernetSwitchPortinstance is created)

3.2.3 Add Board

To add an ET-MFX board, follow the instruction in Transmission BoardExpansion.

Set the value of systemPort to true for the ports that provide access to theexternal network ant to false for the other ports.

14 58/1543-FAB 102 614 Uen B 2008-02-26


Table 1 Attributes to be Set in EthernetSwitchPort MO

Attribute Value Comments

Parent ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<slot>,PlugInUnit=1,ExchangeTerminalIp=1,EthernetSwitcht=1

Id <n> The EthernetSwitchPortthat provide access tothe external network.

systemPort true

1558/1543-FAB 102 614 Uen B 2008-02-26


16 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-CS Control Plane

4 Iu-CS Control Plane

Figure 4 on page 17 shows the MOs and structure involved in the migrationof the Iu-CS Control Plane.

GigaBitEthernet

Mtp3bSr

Mtp3bSp<standard>

Mtp3bSrs

Mtp3bSr

for ATM for IP

Sctp

IpAccessHostGpb

slot

PlugInUit

M3uAssociation

TransportNetwork

IpSystem

IpInterface

GeneralProcessorUnit

C0001418A

Figure 4 The MOs and Structure Involved in the Migration of the Iu-CS Control Plane

The migration of the Iu-CS Control Plane to Ethernet links may includereallocation and replacement of boards.

The following migration cases are described in this chapter and depend uponone of the following being true:

• ET-MFG boards already exist in the RNC

• ET-MFG will be added to an existing free slot

• ET-MFG will be added but there is no free slot in the RNC subrack

1758/1543-FAB 102 614 Uen B 2008-02-26


C0001402A

ET-MFG Present?

YES

Start

Migrate Iu-CSControl plane

NO

NO

Free slots?

YES

Install ET-MFG

Preparation

Cut over Tidy up

End

Figure 5

It is recommended to have at least two ET-MFG for the Iu-CS Control Plane. Inthis case the steps need to be repeated for each board.

4.1 Preparation

1. If it is not already present, install the ET-MFG board. See Section 3.1 onpage 9.

2. If it has not already been created for previously migrated interfaces suchas Iu-PS or Iur, create an IpInterface for each ET-MFG. Set attributes asdescribed in Table 2 on page 18 .

Table 2 Attributes to be Set in IpInterface MO


Parent ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<slot>, PlugInUnit=1, EtMfg=1,GigaBitEthernet=1

18 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-CS Control Plane


Id <n> The number of theinterface on thisET-MFG.

defaultRouter0

defaultRouter1

defaultRouter2

<routerIPaddress> The IP address for thedefault router. At leastdefaultRouter0 must beset.

vid It is recommended thatthe virtual LAN (VLAN)feature is used for thesubnets. If used, VLANattributes must be setas well. The VLAN isdefined by the attributesvid and vLan.

vLan It is recommended thatthere is a one-to-onemapping betweensubnet and VLAN. Sofor one subnet, thesame VLAN should beused, and the oppositeis also true. UsingVLAN is mandatory ifmore than one subnetis allocated to the sameET-MFG board.

networkPrefixLength <networkPrefixLength> networkPrefixLengthmust be between 20and 30.

Example: networkPrefixLength = 24, meansthat it is equivalent witha subnet mask that is255.255.255.0


1958/1543-FAB 102 614 Uen B 2008-02-26



rps true Specifies whetherRouter Path Supervisionis performed onthe links defined byownIpAddressActiveand ownIpAddressPassive.

ownIpAddressActive <ipaddress>

ownIpAddressPassive <ipaddress>

Set if rps = true.

The attributes: ownIpAddressActive andownIpAddressPassive,must be set for eachIpInterface (the formerattribute is used tomonitor the activelink, and the latterattribute is used tomonitor the passivelink). However, theownIpAddressPassiveis only needed if bothports are used on theET-MFG board.

mtu If frameformat =ETHERNET_2_DIXthe mtu should be set to1500. If frameformat =IEEE_802_3_LLC_SNAP the mtu should be setto 1492.

userLabel Free for use.

3. If it has not already been created for other interfaces, create oneIpAccessHostGpb MO for the SCCP MP in the node. Set the attributes asdescribed in Table 3 on page 20.

Table 3 Attributes to be Set in IpAccessHostGpb MO


Parent ManagedElement=1,IpSystem=1

Id <subrack>-<slot>-

Where subrack and slotare the same as wherethe SCTP MP is locatedin the RNC.

20 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-CS Control Plane


administrativeState 1 1=unlocked

generalProcessorUnitId ManagedElement=1,Equipment=1,Subrack=MS,Slot=8,PlugInUnit=1,GeneralProcessorUnit=1

Reference to the SCCPMP

interface1 ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<slot>,PlugInUnit=1,EtMfg=1,GigaBitEthernet=1,IpInterface=1

Created in Step 2 onpage 18.

interface2 ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<slot>,PluginUnit=1,EtMfg=1,GigaBitEthernet=1,IpInterface=1


Needs to be done ifredundant board isused.

ipAddress1 <ipAddress1> The first IP address ofthe host.

This IP address mustbe unique with respectto other hosts in thenode. This IP addressmust belong to thesubnet that is indicatedin the MO referenced byinterface1.

The subnet addressis constructedfrom the addressin defaultRouter0and the attributenetworkPrefixLengthof the IpInterface MO.

2158/1543-FAB 102 614 Uen B 2008-02-26



ipAddress2 <ipAddress2> The second IP addressof the host.



userLabel Free for use

4. Find the RPU to be used when creating the Sctp MO. The ID dependson the node history:

• Nodes that have the Sctp loaded on the SCCP MP at the factory willhave rpu Id=sctp_host_sccp

• Nodes that have the Sctp loaded on the SCCP MP during an upgradewill have the id set to a random integer. To find this rpu you need tofind those rpus that have ReliableProgramLabel=sctp_host and theadmActiveSlot = ’Subrack=MS,slot=8’.

5. If it has not already been created by other interfaces, create one SctpMO referring to IpAccessHostGpb created in Step 3 on page 20. Set theattributes as described in Table 4 on page 22.



Parent ManagedElement=1,TransportNetwork=1

Id Iu_Iur

22 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-CS Control Plane


ipAccessHostGpbId ManagedElement=1,IpSystem=1,IpAccessHostGpb=<x>

Reference to theIpAccessHostGpbcreated above.

The related Slot to thegeneralProcessorUnitIdon the IpAccessHostGpb should bethe same as theadmActiveSlot on theReliableProgramUniterMO that the rpuId refersto (see further down inthis table).

maxUserDataSize 556 Must be set to mtu(Maximum TransferUnit size for an IPpacket, defined in theIpInterface MO) minussize of IP header.

mBuffer 256 kB

maxIncomingStream 17 (=default)

maxOutgoingStream 17 (=default)

nThreshold 192 kB 3/4 of mBuffer size

numberOfAssociations 128 The number ofM3uAssociationssupported. Thisvalue must be set toat least the numberof SS7 connectionsthat are migrated toET-MFG includingIu-CS, Iu-PS and IurCP connections. Thisattribute is restrictedand cannot be changedonce the Sctp MOhas been created.Therefore it is importantto set a sufficiently largevalue that will allowfor the total number ofsignalling connectionsthat may be needed inthe future.

2358/1543-FAB 102 614 Uen B 2008-02-26



rpuId ManagedElement=1,SwManagement= 1,ReliableProgramUniter=<X>

The RPU found in Step4 on page 22

minimumRto 10 (100 ms)

maximumRto 40 (400 ms)

pathMaxRtx 4

associationMaxRtx 8


6. One M3uAssociation MO is needed per SS7 connection that is migrated toET-MFG. The SCTP multi-homing mechanism will ensure the necessaryredundancy is achieved. See Section 2.1.1 Signaling Connections ThatCan Be Migrated to Ethernet Links on page 5.

Note: Multihomed SCTP is always used on the RNC side.

The attributes in the M3uAssociation MO are recommended to be set totheir default values, except for the ones listed in Table 5 on page 24.

Table 5 Attributes to be Set in M3uAssociation MO


Parent ManagedElement=1,TransportNetwork=1,Mtp3bSp<standard>

<standard> is eitherANSI, Ttc, Itu or Chinastandard.

Id cs

autoStartAssociation True

dscp 10 The value correspondsto the AssuredForwarding Class 1 PerHop Behavior (PHB),Low Loss Precedence(AF11). For information,see the IETF RFC 2597Assured ForwardingPHB Group .

localIpMask MULTI_HOMED This value must beset when configuringa multihomed SCTPconnection.

24 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-CS Control Plane


mtp3bSrsId This parameter refers tothe MTP3b signalingroute set whosedestination point codecorresponds to theremote end point ofthe M3UA association(destination).

remoteIpAddress1 Specifies the primary IPaddress of the remotenode.

remoteIpAddress2 Specifies the secondaryIP address of the remotenode, and is applicableonly when the remoteSCTP end point ismultihomed, in whichcase it is mandatory.

role CLIENT

sctpId This value is set to theSctp MO created above.

7. One Mtp3bSr MO is needed per SS7 connection that is migrated toET-MFG.

The Mtp3bSr MO is created as a normal signaling route, except for thedifferences shown in Table 6 on page 25.

Table 6 Attributes to be Set in Mtp3bSr MO


Parent ManagedElement=1,TransportNetwork=1,Mtp3bSp<standard>=<x>, Mtp3bSrs=<y>

2558/1543-FAB 102 614 Uen B 2008-02-26



Id <nodeType><x>(<y>)(<z>)

<nodeType> = corenetwork node type,coded as follows: c=CS(MSC), p=PS (SGSN)

< x> = user protocol,only s=signalingrelevant in this context

<y>= active (=a) orstandby (=b) MP usedfor the signaling linktermination (not relevantfor IP based signalling)

<z> = connectionnumber in case ofmultiple connections(only if needed, forexample when bothIP and ATM basedsignaling is configured)

linkSetM3uId Previously createdM3uAssociation.

priority This attribute must beset to lowest priority.It has to be changedduring the cut over.

4.2 Cutover

1. Unlock the GigaBitEthernet MO for the created ET-MFG boards.

2. Make a new CV. See Creating a CV in Software Management.

3. Make sure the Mtp3brSr created in the Preparation stage isNOT_BLOCKED.

4. Set the priority of all Iu-CS signaling routes to a low value, thereby makingsure that the new IP signaling connections will be used when they aredeblocked.

Go through all ATM signaling route Mtp3bSr MOs for the connections thatwill be migrated. For all these signal routes, set the priority (priority inMtp3bSr) value to the highest value (5).

26 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-CS Control Plane

Go through all signaling route Mtp3bSr MOs for the connections that will bemigrated. For all these signal routes, set the priority (priority in Mtp3bSr)value to the lowest value (1).

5. If the M3uAssociation MOs created in the Preparation stage are notactive, set them to Auto Activate, via the action setAutoActivate on theM3uAssociation MO. For an association with role = CLIENT, this settingwill set the attribute autoStartAssociation = true. If a new CV is madeafter this action the associations will be automatically started after a noderestart with this CV.

6. Verify that no M3uAssociation alarms are raised, and that the usageStateof the newly created Mtp3bSr MOs are set to active.

Wait until the usageState in all related ATM Mtp3bSr MOs are set to idle.This should take less than a minute. When this happens all signalingis going through IP routes.


4.3 Migrate Iu-CS Control Plane

This procedure describes how Iu-CS Control Plane connections are migrated toET-MFG, and how the two ET-MFG boards are installed during this migration.It is assumed that the necessary preparations have been completed, and thatthe RNC node is running P6 software with no ET-MFG boards installed.

In the procedure steps, the letters X and Y are used to denote the first andthe second ET board to be replaced.

1. Make sure that a backup CV is stored.

2. Make sure the board is not used for any traffic. See Section 3.1.1Reallocation of Connections on page 10.

3. Choose the ET-board that will be replaced by the first ET-MFG board (X). Ifthe preparation has been completed properly the board will be idle.

4. Install the ET-MFG board by following the Transmission Board Changeinstruction.

5. Verify that the following MOs have been created: EtMfg andGigaBitEthernet.

6. Follow Step 2 on page 18 through Step 7 on page 25 in Section 4.1 onpage 18.

4.4 Tidy up

1. Delete all ATM signal routes (all Mtp3bSr MOs related to ATM) that are notto be used anymore.

2758/1543-FAB 102 614 Uen B 2008-02-26


Note: This may impact traffic (both Iu-PS and Iu-CS user plane) that iscurrently controlled by the deleted signal routes — these callsmight be dropped.

2. If ATM board is not used remove it.


4. Remove the previous CV created during the preparation and cutover phase.

28 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-PS Control Plane

5 Iu-PS Control Plane

Figure 6 on page 29 shows the MOs and structure involved in the migrationof the Iu-PS Control Plane.

GigaBitEthernet

Mtp3bSr

Mtp3bSp<standard>

Mtp3bSrs

Mtp3bSr

for ATM for IP

Sctp

IpAccessHostGpb

slot

PlugInUit

M3uAssociation

TransportNetwork

IpSystem

IpInterface


C0001418A

Figure 6 The MOs and Structure Involved in the Migration of the Iu-PS Control Plane

The migration of the Iu-PS control plane to Ethernet links may includereallocation and replacement of the board.


• ET-MFG boards already exist in RNC.

• ET-MFG will be added to an existing free slot.

• ET-MFG will be added but there is no free slot in RNC subrack.

2958/1543-FAB 102 614 Uen B 2008-02-26


C0001403A

ET-MFG Present?

YES

Start

Migrate Iu-PSControl plane

NO

NO

Free slots?

YES

Install ET-MFG

Preparation

Cut over Tidy up

End

Figure 7

It is recommended to have at least two ET-MFG for the Iu-PS Control Plane. Inthis case the steps need to be repeated for each board.

5.1 Preparation1. If it is not already present, install the ET-MFG board. See Section 3.1 on

page 9.

2. If it has not already been created for previously migrated interfaces such asIu-CS or Iur then create an IpInterface for each ET-MFG. Set attributes asdescribed in Table 7 on page 30.



Parent ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<slot>,PlugInUnit=1, EtMfg=1,GigaBitEthernet=1

Id <n> The number of theinterface on this EtMfg.

30 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-PS Control Plane


defaultRouter0

defaultRouter1

defaultRouter2



vLan It is recommended thatthere is a one-to-onemapping betweensubnet and VLAN. Sofor one subnet, thesame VLAN should beused, and the oppositeis also true. UsingVLAN is mandatory ifmore than one subnetis allocated to the sameET-MFG board.




rps true Specifies whetherRouter Path Supervisionis performed on the linksdefined by

ownIpAddressActiveand ownIpAddressPassive.

3158/1543-FAB 102 614 Uen B 2008-02-26





Set if rps = true.




3. If it has not already been created by other interfaces, create oneIpAccessHostGpb MO for the SCCP MP in the node. Set the attributes asdescribed in Table 8 on page 32.



Parent ManagedElement=1,IpSystem=1,





This must refer to thesame subrack and slotthat the SCCP MP isexecuted on.

32 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-PS Control Plane






Needs to be done ifredundant board isused.




3358/1543-FAB 102 614 Uen B 2008-02-26







4. Find the RPU to be used when creating the Sctp MO. The ID dependson the node history:

• Nodes that have the Sctp loaded on the SCCP MP at the factory willhave rpu Id=sctp_host_sccp

• Nodes that have the Sctp loaded on the SCCP MP during an upgradewill have the id set to a random integer. To find this rpu you need tofind those rpus that have ReliableProgramLabel=sctp_host and theadmActiveSlot = ’Subrack=MS,slot=8’.

5. If it has not already been created by other interfaces, create one SctpMO referring to IpAccessHostGpb created in Step 3 on page 32. Set theattributes as described in Table 9 on page 34.

Table 9 Attributes to be Set in Sctp MO


Parent ManagedElement=1,TransportNetwork=1

Id Iu_Iur

34 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-PS Control Plane





maxUserDataSize 1480 Must be set to mtu(Maximum TransferUnit size for an IPpacket, defined in theIpInterface MO) minussize of IP header.

mBuffer 256 kB




numberOfAssociations 128 The number ofM3uAssociationssupported. Thisvalue must be set toat least the numberof SS7 connectionsthat are migrated toET-MFG includingIu-CS, Iu-PS and IurCP connections. Thisattribute is restrictedand cannot be changedonce the Sctp MOhas been created.Therefore it is importantto set a sufficiently largevalue that will allowfor the total number ofsignalling connectionthat may be needed inthe future.

3558/1543-FAB 102 614 Uen B 2008-02-26



rpuId ManagedElement=1,SwManagement=1,ReliableProgramUniter=<X>

The RPU found in Step4 on page 34

minimumRto 10 (100 ms)

maximumRto 40 (400 ms)

pathMaxRtx 4

associationMaxRtx 8


6. One M3uAssociation MO is needed per SS7 connection that is migrated toET-MFG. The SCTP multi-homing mechanism will ensure the necessaryredundancy is achieved. SeeSection 2.1.2 on page 5.

Note: Multihomed SCTP is always used on the RNC side.

The attributes in the M3uAssociation MO are recommended to be set totheir default values, except for those listed in Table 10 on page 36.




<standard> is eitherANSI, Ttc, Itu or Chinastandard.

Id ps


dscp 10 The value correspondsto the AssuredForwarding Class 1 PerHop Behavior (PHB),Low Loss Precedence(AF11). For information,see the IETF RFC 2597Assured ForwardingPHB Group.

maxIncomingStream


36 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-PS Control Plane





role CLIENT

sctpId This value is set tothe Sctp MO createdpreviously.


The Mtp3bSr MO is created as a normal signaling route, except for thedifferences shown in Table 11 on page 37.




3758/1543-FAB 102 614 Uen B 2008-02-26








linkSetM3uId Must be set to theM3uAssociation createdfor this signaling link,


5.2 Cutover


2. Make sure the Mtp3brSr created in the Preparation stage is unlocked.

3. Set the priority of all applicable signaling routes to a low value, therebymaking sure that the new IP signaling connections will be used when theyare deblocked.

Go through all ATM signaling route Mtp3bSr MOs for the connections thatwill be migrated. For all these signal routes, set the priority (priority inMtp3bSr) value to the highest value (5).

Go through all signaling route Mtp3bSr MOs for the connections that will bemigrated. For all these signal routes, set the priority (priority in Mtp3bSr)value to the lowest value (1).

38 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-PS Control Plane

4. If the M3uAssociation MOs created in the Preparation stage are not active,set them to Auto Activate. For an association with role = CLIENT, thissetting will set the attribute autoStartAssociation = true. If a new CV ismade after this action the associations will be automatically started after anode restart with this CV.

5. Verify that no M3uAssociation alarms are raised and that the usageState ofthe newly created Mtp3bSr MOs are set to active.

Wait until the usageState in all related ATM Mtp3bSr MOs are set toidle. When this happens all signaling is going through IP routes. If theusageState attribute is not set to idle within a certain time period, it isrecommended to proceed with the next step.


5.3 Migrate Iu-PS Control Plane

This procedure describes how Iu-PS Control Plane connections are migrated toET-MFG and how the two ET-MFG boards are installed during this migration. Itis assumed that the necessary preparations have been completed, and that theRNC node is running P6 software with no ET-MFG boards installed.


1. Make sure that a backup Configuration Version (CV) is stored.


3. Choose the ET-board that will be replaced by the first ET-MFG board (X). Ifthe preparation has been made properly the board will be idle.



6. Follow Step 2 on page 30 through Step 7 on page 37 in Section 5.1Preparation on page 30.

5.4 Tidy up1. Delete all ATM signal routes (all Mtp3bSr MOs related to ATM) that are not

to be used anymore.

Note: This might impact traffic (both Iu-PS and Iu-CS user plane) that iscurrently controlled by the deleted signal routes — these calls willmight be dropped.

2. If ATM board is not used remove it.

3958/1543-FAB 102 614 Uen B 2008-02-26



4. Remove the previous CV created during the preparation and cut overphase.

40 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-PS User Plane

6 Iu-PS User Plane

Figure 8 on page 41 shows the MOs and structure involved in the migration ofthe Iu-PS User Plane.

GigaBitEthernet

IpInterface

IpSystem

Ip AccessHostspb

SpDevicePool

IpEthPacketDataRouter

PdrDevice

C0001419A

Figure 8 The MOs and Structure Involved in the Migration of the Iu-PS User Plan

The migration of Iu-PS User Plane to Ethernet links could include reallocationand replacement of the board.


• ET-MFG boards already exist in the RNC.


• ET-MFG will be added but there is no free slot in the RNC subrack.

4158/1543-FAB 102 614 Uen B 2008-02-26


C0001404A

ET-MFG Present?

YES

Start

Install ET-MFGand Migrate

Iu-PS User Plane

NO

NO

Free slot?

YES

AddET-MFG

Preparation and Migration of Iu-PS User Plane

Cut over Tidy up

End

Figure 9 Workflow for Migrating Iu-PS User Plane

6.1 Preparation and Cutover

This section describes the migration of Iu-PS user plane to Ethernet linksincluding preparation and cutover procedures. The installation of the Ethernetinterface is a part of the procedure if it is not already installed.

6.1.1 Preparation and Migration of Iu-PS User Plane (ET-MFG AlreadyInstalled)

This procedure describes how Iu-PS user plane connections are migrated toET-MFG when the RNC node already has two ET-MFG boards installed. Itis assumed that the necessary preparations have been completed, and thatthe RNC node is running P6 software.


2. If it hasn’t already been created by the Iur User Plane and sharing isgoing to be used, configure one IpInterface MO on each ET-MFG board.

42 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-PS User Plane

For each IpInterface MO, the attributes are recommended to be set asdescribed in Table 12 on page 43.





defaultRouter0

defaultRouter1

defaultRouter2

<routerIPaddress> The IP address for thedefault router At leastdefaultRouter0 must beset.


vLan It is recommended touse separate subnetsfor User Plane andControl Plane.




4358/1543-FAB 102 614 Uen B 2008-02-26






Set if rps = true.

The attributes: ownIpAddressActive andownIpAddressPassive,must be set for eachIpInterface (the formerattribute is used tomonitor the activelink, and the latterattribute is used tomonitor the passivelink). However, theownIpAddressPassiveis needed only if bothports are used on theET-MFG board.



3. Configure one IpAccessHostSpb MO per PDR SP. Set the attributes asdescribed in Table 13 on page 44

Table 13 Attributes to be Set in IpAccessHostSpb MO





44 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-PS User Plane


spmId ManagedElement=1,Equipment=1,Subrack=MS,Slot=<x>,PlugInUnit=1,Spu=1,Spm=1

Reference to the Spmwhere the PDR device isrunning Add Userlabelnew Attribute same inother tables


ipAddress <ipaddress> The first IP address

ipAddress2 <ipaddress> The second IP address

ipInterface ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<x>,PluginUnit=1,EtMfg=1,GigaBitEthernet=1,IpInterface=1

interface2 ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<x>,PluginUnit=1,EtMfg=1,GigaBitEthernet=1,IpInterface=1

Two different IpInterfaceMOs (ipInterface,ipInterface2) needto be referenced —one reference per IPaddress. The twompIpInterface MOsmust belong to differentET-MFG boards.


Note: The attribute ipAddress is associated with ipInterface, and ipAddress2is associated with interface2.

4. Configure two IpEthPacketDataRouter instances per PDR SP.

The attributes in the IpEthPacketDataRouter MOs are recommended to beset to their default values, except for those listed in Table 14 on page 45.

Table 14 Attributes to be Set in IpEthPacketDataRouter MO


Parent ManagedElement=1,Equipment=1, SpDevicePool=PdrDevice,PdrDevice=<Subrack><Slot>


Where subrack and slotare the same as wherethe SCCP MP is locatedin the RNC.

4558/1543-FAB 102 614 Uen B 2008-02-26



ipAccessHostSpbRef Set to the IpAccessHostSpb MO on theassociated PDR SP.

ipAddressSelection Set to IP_ADDRESS_1for one of the twoIpEthPacketDataRouterinstances on thesame PDR device,and for the otherIpEthPacketDataRouterinstance on the samePDR device it is set toIP_ADDRESS_2.

Note: Load sharing will take place between the packet data routers. Thismeans that the load will be distributed between all associatedIpInterfaces, and as a result both ET-MFG boards will be used forIu-PS user plane traffic.

6.1.2 Cutover

1. Unlock the IpEthPacketDataRouter instances.

2. Configure the migrated Iu-PS user plane connections so new PS calls aresetup only on the ET-MFG board, and not on ATM boards.

For each IuLink MO that represents a migrated CN node, addpacketDataRouterRef references to all IpEthPacketDataRouterinstances. Also remove any existing packetDataRouter references toPacketDataRouter MOs.

If there are any CNs that will remain connected via ATM, make sure thatthe packetDataRouterRef attribute in the corresponding IuLink MOs are setto the PacketDataRouter MOs that will remain after the migration.

The packetDataRouterRef attribute is used to control which CN node canuse a specific Packet Data Router (normally used for the IuFlex feature).

3. Verify that new Iu-PS connections are possible. The verificationcan be done by checking that the pmNoRoutedIpPacketsUland pmNoRoutedIpPacketsDl counters are stepped in the newIpEthPacketDataRouter MOs. If the counters are stepped, new PSconnections are established on the new IpEthPacketDataRouter MOinstances.


5. Lock and delete any existing PacketDataRouter MO instances that arenot supposed to be used anymore.

46 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-PS User Plane

Note: This may affect the Iu-PS user plane; PS calls remaining on any ofthe PacketDataRouter instances will be dropped.


6.2 Install ET-MFG and Migrate Iu-PS User Plane

This procedure describes how Iu-PS user plane connections are migrated toET-MFG, and how the two ET-MFG boards are installed during this migration.It is assumed that the necessary preparations have been completed, and thatthe RNC node is running P6 software with no ET-MFG boards installed.




3. Choose the ET-board that will be replaced by the first ET-MFG board (X). Ifthe preparations have been completed properly, there will only be Iu-PSuser plane connections using this board (and they must all be migrated).If there are no unlocked and enabled PacketDataRouter Managed Object(MO) instances allocated to X (that is, the ET board is not used), go toStep 5 on page 47.

4. Deactivate the PacketDataRouter MOs that have Virtual Channels (VC)associated with X. Before proceeding with this step make sure that thereexists at least one PacketDataRouter MO instance that is unlocked andenabled, and that has a VC associated with an ATM ET board differentfrom X.

Go through all PacketDataRouter MO instances associated with X andlock them.

Note: This will affect the Iu-PS user plane, because traffic that iscurrently running on these PacketDataRouter MO instances will betemporarily dropped (the RAB sessions will be setup again on thePacketDataRouter MOs that are not blocked).

5. Install the ET-MFG board following the Transmission Board Changeinstruction.


7. Configure one IpInterface MO on the ET-MFG board. See Table 15 onpage 48 for recommended attribute values.

4758/1543-FAB 102 614 Uen B 2008-02-26






defaultRouter0

defaultRouter1

defaultRouter2


vid It is recommended thatthe virtual LAN (VLAN)feature is used for thesubnets. If used, VLANattributes must be setas well. The VLAN isdefined by the attributes:vid and vLan.

vLan It is recommended thatthere is a one-to-onemapping betweensubnet and VLAN. So,for one subnet, thesame VLAN should beused, and for one VLANthe same subnet shouldbe used. Using VLAN ismandatory if more thanone subnet is allocatedto the same ET-MFGboard.

48 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-PS User Plane




Example: networkPrefixLength = 28, meansthat it is equivalentwith a subnet maskthat is subnet mask is255.255.255.240




Set if rps = true.

The attributes: ownIpAddressActive andownIpAddressPassive,must be set for eachIpInterface (the formerattribute is used tomonitor the activelink, and the latterattribute is used tomonitor the passivelink). However, theownIpAddressPassiveis needed only if bothports are used on theET-MFG board.



4958/1543-FAB 102 614 Uen B 2008-02-26


8. Configure one IpAccessHostSpb MO per PDR SP. In this step only one IPaddress can be configured per MO because the second ET-MFG board isnot yet installed.

It is recommended that one IpAccessHostSpb MO is defined per PDR SPdevice, that is, five MO instances in total.

The attributes in the IpAccessHostSpb MOs are recommended to be set totheir default values, except for those listed in Table 16 on page 50.

Table 16 Attributes to be Set in IpAccessHostSpb MO







This must refer to thesame subrack and slotas the SCCP MP

interface1 ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<slot>,PlugInUnit=1,EtMfg=1,GigaBitEthernet=1,IpInterface=1


50 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-PS User Plane






When choosing IP addresses used for the IpAccessHostSpb MOs it is possibleto reuse existing IP addresses from any PacketDataRouter MOs that are lockedand that are not intended to be used anymore.

9. Configure one IpEthPacketDataRouter MO instance per PDR SP.

The attributes in the IpEthPacketDataRouter MOs are recommended to beset to their default values, except for those listed in Table 17 on page 51.

Table 17 Attributes to be Set in IpEthPacketDataRouter MO


Parent ManagedElement=1,Equipment=1, SpDevicePool=PdrDevice,PdrDevice=<Subrack><Slot>



5158/1543-FAB 102 614 Uen B 2008-02-26



ipAccessHostSpbRef Set to the IpAccessHostSpb MO on theassociated PDR SP.

ipAddressSelection IP_ADDRESS_1 Set to IP_ADDRESS_1for one of the twoIpEthPacketDataRouterinstances on the samePDR device.

10. Unlock the IpEthPacketDataRouter MO instances.

11. Configure the migrated Iu-PS user plane connections so new PS calls areset up only on the ET-MFG board, and not on ATM boards.

For each IuLink MO that represents a migrated CN node, addpacketDataRouterRef references to all IpEthPacketDataRouterinstances. Also remove any existing packetDataRouter references toPacketDataRouter MOs.

If there are any CNs that will remain connected via ATM, make sure thatthe packetDataRouterRef attribute in the corresponding IuLink MOs are setto the PacketDataRouter MOs that will remain after the migration.

The packetDataRouterRef attribute is used to control which CN node canuse a specific Packet Data Router (normally used for the IuFlex feature).



14. Lock all PacketDataRouter instances that are currently allocated to the nextATM ET board to be replaced (Y).

Note: This may affect the Iu-PS user plane; PS connections remaining onany of the PacketDataRouter instances might be dropped.

15. At this point there is no traffic on the second ATM board (Y). Replace thisboard (Y) by installing a second ET-MFG board according to TransmissionBoard Change.

16. Configure one IpInterface MO on the ET-MFG board according to Step 7on page 47.

52 58/1543-FAB 102 614 Uen B 2008-02-26

Iu-PS User Plane

17. Update the IpAccessHostSpb MOs that were configured previously.Set values for ipAddress2 and ipInterface2 by performing the actionaddinterface2AutoConfigOff.

18. Configure one additional IpEthPacketDataRouter MO instance per PDRSP according to Step 9 on page 51.

19. Unlock the IpEthPacketDataRouter MO instances.

20. For each IuLinkMO that represents a migrated CN node, addpacketDataRouterRef references to the new IpEthPacketDataRouterinstances.



6.3 Tidy Up

1. Lock and delete any existing PacketDataRouter MO instances that are notto be used anymore.

Note: This may affect the Iu-PS user plane; PS calls remaining on any ofthe PacketDataRouter instances might be dropped.


5358/1543-FAB 102 614 Uen B 2008-02-26


54 58/1543-FAB 102 614 Uen B 2008-02-26

Iub Control Plane and User Plane

7 Iub Control Plane and User Plane

The three stages of preparation; cut over, tidy up and configuration of objects,are shown in Figure 10 on page 55 and are described in this chapter

Sctp

IpAccessHostGpb

slot

Iub Control Plane

PlugInUnit

TransportNetwork

lubLinkIpSystem

Iub User Plane

IpAccessHostEt

IpAccessHostPool


ExchangeTerminalIp

InternalEthernetPort

IpInterface

HW

C0001420A

Figure 10 Managed Objects Related to Iub Migration Preparation and Adding IP Iub

7.1 Prerequisites

The RNC Modules which will be prepared for Iub over IP must be of R4hardware or later.

7.2 Preparation

This section describes the preparations.

5558/1543-FAB 102 614 Uen B 2008-02-26


7.2.1 Planning for Iub Over IP

For Iub migration to IP the following preconditions are necessary:

• There must be free slots in the subrack for two IP interface boards(ET-MFX). Two ET-MFX boards must be installed according toTransmission Board Expansion.

• Iub control plane and user plane must be migrated together.

• Network Synch-servers must be configured.

• RNC must be running on P6 software.

• The following data must be known:

ipAddress1: The IP address for the host of the Iub control plane. Oneper RNC Module is needed..

ipAddress2: The secondary IP address for the host of the Iub controlplane. One per RNC Module is needed.

ipAddress: The IP address for the host of the Iub user plane. One perETMFX board is needed.

routerIpAddress: The IP address to the default router or routers. Up tothree addresses can be configured and at least one is mandatory. Ifno router is going to be used in the network a fictitious address mustbe used because this attribute is used to determine the subnet mask.See networkPrefixLength.

networkPrefixLength: Used to specify which part of the routerIpAddressis the subnet address.

7.2.2 Preparation for Iub over IP in RNC (ET-MFX Already Installed)

This procedure describes how Iub links are migrated to IP.

7.2.2.1 General

1. General attribute changes for Iub user plane in RNC. Set the attributes onthe RncFunction=1 MO as described in Table 18 on page 57.

The DSCP values match the default values in the TNLQoS feature. If thevalues in TNLQoS is changed these values needs to be reevaluated. If theTNLQoS is not used, the default values are to be used.

56 58/1543-FAB 102 614 Uen B 2008-02-26


Table 18 Attributes to be Set in RncFunction MO


cchDscpEgress 18 DiffServ Code Pointvalue for FACH1,FACH2, RACH andPCH egress.

cchDscpIngress 18 DiffServ Code Pointvalue for FACH1,FACH2, RACH, andPCH ingress IP packets.

2. Create an IpInterface for each ET-MFX. Set the attributes as described inTable 19 on page 57.



Parent ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<slot>,PlugInUnit=1,ExchangeTerminalIp=1,InternalEthernetPort=1

Id <n> The number of theinterface on thisET-MFX.


vLan It is recommended thatthere is a one-to-onemapping betweensubnet and VLAN. So,for one subnet, thesame VLAN should beused, and the oppositeis also true. UsingVLAN is mandatory ifmore than one subnetis allocated to the sameET-MFX board.

5758/1543-FAB 102 614 Uen B 2008-02-26



defaultRouter0

defaultRouter1

defaultRouter2

<routerIPaddress> The IP address for thedefault router; at leastdefaultRouter0 must beset.




rps false Specifies whetherRouter Path Supervisionis performed onthe links defined byownIpAddressActiveand ownIpAddressPassive.



7.2.2.2 Prepare the Iub User Plane

3. Create one IpAccessHostEt for each ET-MFX. Set the attributes asdescribed in Table 20 on page 58.

Table 20 Attributes to be Set in IpAccessHostEt MO



58 58/1543-FAB 102 614 Uen B 2008-02-26



Id <subrack>-<slot>-<interface>

Where subrack, slot andinterface are equal towhere the interface forthe ET-MFX of this hostis located.


ipAddress <ipaddress> The IP address that willbe assigned to this host.

ipInterfaceMoRef ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<slot>,PlugInUnit=1,ExchangeTerminalIp=1,InternalEthernetPort=1,IpInterface=<n>

Reference to theinterface on the ET-MFXcreated above.

Where subrack= thesubrack where theET-MFX is located andslot is the slot wherethe ET-MFX is locatedwithin the subrack, andn is the interface on theET-MFX.

ntpServerMode If this board will serveas an ntp Server for theRBSs, this must be setto ENABLED, otherwisethe default can be used(DISABLED).

At least two ET-MFXmust have this set toENABLED in the RNCto provide redundancy.


4. Create one IpAccessHostPool. There must be one for Iub per RNC. Setthe attribute as described in Table 21 on page 59. If the IpAccessHostPoolalready exists, make sure all IpAccessHostEt for the ET-MFX are includedin the ipAccessHostRef attribute, otherwise add all the IpAccessHostEt.

Table 21 Attributes to be Set in IpAccessHostPool MO


Parent ManagedElement=1,IpSystem= 1

Id Iub[-1] Where -1 is an optionalpostfix

5958/1543-FAB 102 614 Uen B 2008-02-26




ipAccessHostRef List of: ManagedElement=1,IpSystem=1,IpAccessHostEt=<x>

Include all IpAccessHostEt created above forthe ET-MFX board.


5. The RNC is now prepared to handle Iub user plane over IP. Each existingIub link will continue to run on ATM until its userPlaneTransportOptionis changed.

7.2.2.3 Prepare One Iub Control Plane

1. Create one IpAccessHostGpb MO for each RNC Module that should beable to handle Iub over IP traffic. R3 hardware, and earlier versions, cannotsupport Iub over IP. Due to module MP pooling, all modules in a subrackneed to be configured to handle moved IP Iub links. Set the attributes asdescribed in Table 22 on page 60.





Where subrack and slotare the same as wherethe RNC Module for thisIpAccessHostGpb islocated.


generalProcessorUnitId ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<slot>,PlugInUnit=1, GeneralProcessorUnit=1

This must refer to thesame subrack and slotas the correspondingRncModule. OneIpAccessHostGpb MOmust be created foreach RncModule in theRNC.

60 58/1543-FAB 102 614 Uen B 2008-02-26



interface1 ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<slot>,PlugInUnit=1,ExchangeTerminalIp=1,InternalEthernetPort=1,IpInterface=<x>

Reference to the maininterface.

Where subrack= thesubrack where theET-MFX is located,slot is the slot wherethe ET-MFX is locatedwithin the subrack, andx is the interface on theET-MFX.

If possible, select theET-MFX in the samesubrack or the ET-MFXin the lowest Subrack.

interface2 ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<slot>,PlugInUnit=1,ExchangeTerminalIp=1,InternalEthernetPort=1,IpInterface=<x>

This is an optionalreference to thesecondary interface.

Where subrack= thesubrack where theET-MFX is located,slot is in which slotthe ET-MFX is locatedwithin the subrack, andx is the interface on theET-MFX.

If possible, select theET-MFX in the SameSubrack or the ET-MFXin the lowest Subrack.

6158/1543-FAB 102 614 Uen B 2008-02-26










2. For each IpAccessHostGpb create one Sctp MO. Set the attributes asdescribed in Table 23 on page 63.

62 58/1543-FAB 102 614 Uen B 2008-02-26




Parent ManagedElement=1Transportnetwork=1

Id Iub_<m> Where m is the same asthe id of the RncModule.






numberOfAssociations 128 The maximum numberof associations thatcan be handled by thisSCTP MO.

rpuId ManagedElement=1,SwManagement=1,ReliableProgramUniter=sctp_host_<m>

Where m is the same asthe id of the RncModule.


associationMaxRtx 12

heartbeatInterval 1

initialAdRecWin 16384

mBuffer 16

nThereshold 12

pathMaxRtx 12

3. The RNC is now prepared to handle Iub control plane over IP. Each existingIub link will continue to run on ATM until its controlPlaneTransportOptionis changed.

6358/1543-FAB 102 614 Uen B 2008-02-26


7.3 Cutover• Make a new CV. See Creating a CV in Software Management.

• In the IubLink add a reference to a IpAccessHostPool, by setting theuserPlaneIpResourceRef attribute in the IubLink MO created above.

Table 24 Attributes to be Set in IubLink MO

Attribute Value Comment

userPlaneIpResourceRef

ManagedElement=1,IpSystem=1,IpAccessHostPool=<Iub[-1]>

The IpAccessHostPoolcreated duringpreparation.

• Set the IP addresses for the Iub control plane by using the attributes asdescribed in Table 25 on page 64.

Table 25 Attributes to be Set in IubLink MO

Attribute Value Comment

remoteCpIpAddress1 <RemoteCP1Ipaddress>

The main IP address ofthe RBS control plane.

remoteCpIpAddress2 <RemoteCP2Ipaddress>

The secondary IPaddress of the RBScontrol plane.

• Switch to IP traffic by switching the IubLink attributes: userPlaneTransportOption and controlPlaneTransportOption to IPv4.

Note: The IubLinks need to be locked before changingcontrolPlaneTransportOption to IPv4, and afterwords the IubLinksneed to be unlocked.

Note: The RNC NBAP MO’s (NbapCommon, NbapDedicated) aresuperfluous at this stage, and may assume unexpected states.This can safely be ignored.

7.4 Tidy Up

Delete all ATM configuration that is not to be used anymore. The following MOsfor the relevant link can now be deleted.

• VclTp

• AtmCrossConnection

• Aal2PathVccTp

• UniSaalTp

• Aal2Ap(1)

64 58/1543-FAB 102 614 Uen B 2008-02-26


• Aal2PathDistributionUnit

• Aal2RoutingCase(2)

• Aal5TpVccTp

• NbapCommon

• NbapDedicated

6558/1543-FAB 102 614 Uen B 2008-02-26


66 58/1543-FAB 102 614 Uen B 2008-02-26

Iur Control Plane

8 Iur Control Plane

Figure 11 on page 67 shows the MOs and structure involved in the migration ofthe Iur Control Plane.

GigaBitEthernet

Mtp3bSr

Mtp3bSp<standard>

Mtp3bSrs

Mtp3bSr

for ATM for IP

Sctp

IpAccessHostGpb

slot

PlugInUit

M3uAssociation

TransportNetwork

IpSystem

IpInterface


C0001418A

Figure 11 The MOs and Structure Involved in the Migration of the Iur Control Plane

The migration of Iur control plane to Ethernet links may include reallocation andreplacement of board.

The migration cases described in this chapter depend upon one of the followingbeing true:



• ET-MFG will be added but there is no free slot in a RNC subrack.

The procedure in this chapter needs to be performed for both the DRNC andthe SRNC.

8.1 Preparation

1. Install ET-MFG. See Section 3.1 on page 9.

6758/1543-FAB 102 614 Uen B 2008-02-26


2. If it has not already been created for previously migrated interfaces suchas Iu-PS CP and Iu-CS CP, create an IpInterface for each ET-MFG. Setattributes as described in Table 26 on page 68.





defaultRouter0

defaultRouter1

defaultRouter2



vLan It is recommended touse separate subnetsfor Use Plane andControl Plane.




68 58/1543-FAB 102 614 Uen B 2008-02-26

Iur Control Plane





Set if rps = true.




3. If it has not already been created for other interfaces, create oneIpAccessHostGpb MO for the SCCP MP in the node. Set the attributes asdescribed in Table 27 on page 69.




Id MS-8 Where subrack and slotare the same as wherethe SCCP MP is locatedin RNC.

6958/1543-FAB 102 614 Uen B 2008-02-26





This must refer to thesame subrack and slotthat the SCCP MPresides in.

interface1 ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<slot>,PlugInUnit=1,EtMfg,GigaBitEthernet,IpInterface=<x>

Created in Section 8.1Preparation on page 67.

interface2 ManagedElement=1,Equipment=1,Subrack=<subrack>,Slot=<slot>,PlugInUnit=1,EtMfg,GigaBitEthernet,IpInterface=<x>

Created in Section 8.1Preparation on page 67.




70 58/1543-FAB 102 614 Uen B 2008-02-26

Iur Control Plane






4. Find the RPU to be used when creating the Sctp MO. Depending on thenode history it will have a different Id

• Nodes that have the SCTP loaded on the Module MP at the factoryhave rpu Id=sctp_host_sccp

• Nodes that have the SCTP loaded on the Module MP during anupgrade will have the id set to a random integer. To find this rpu youneed to find those rpus that have ReliableProgramLabel=sctp and theadmActiveSlot = the same slot as the Module MP is executing on.

5. If it has not been created for other interfaces, create one Sctp MO referringto IpAccessHostGpb created in Step 3 on page 69. Set the attributes asdescribed in Table 28 on page 71.



Parent ManagedElement=1,Transportnetwork=1,

Id Iu[_Iur]

7158/1543-FAB 102 614 Uen B 2008-02-26



IpAccessHostGpbId ManagedElement=1,IpSystem=1,IpAccessHostGpb=MS-8

Reference to theIpAccessHostGpbcreated in Step 3 onpage 69.





numberOfAssociations 128 The maximum numberof M3uAssociationssupported. Thisvalue must be set toat least the numberof SS7 connectionsthat are migrated toET-MFG includingIu-CS, Iu-PS and IurCP connections. Thisattribute is restrictedand cannot be changedonce the Sctp MOhas been created.Therefore it is importantto set a sufficiently largevalue that will allowfor the total number ofsignalling connectionsthat may be needed inthe future.

rpuId ManagedElement=1,SwManagement=1,ReliableProgramUniter=<X>

The Rpu found in Step4 on page 71.


72 58/1543-FAB 102 614 Uen B 2008-02-26

Iur Control Plane

6. One M3uAssociation MO is needed per SS7 connection that is migratedto ET-MFG. The SCTP multi-homing mechanism will ensure that thenecessary redundancy is achieved.

Note: Multi-homed SCTP is always used on the RNC side.

The attributes in the M3uAssociation MO are recommended to be set totheir default values, except for those listed in Table 29 on page 73.




Id Iu[_Iur]


dscp 10 The value correspondsto the AssuredForwarding Class 1 PerHop Behavior (PHB),Low Loss Precedence(AF11). For information,see the IETF RFC 2597Assured ForwardingPHB Group.

maxIncomingStream




7358/1543-FAB 102 614 Uen B 2008-02-26




role CLIENT

sctpId This value is set to theSctp MO defined forSIGTRAN


The Mtp3bSr MO is created as a normal signaling route, except for thedifferences show in Table 30 on page 74.









74 58/1543-FAB 102 614 Uen B 2008-02-26

Iur Control Plane


linkSetM3uId Previously createdM3uAssociation.


8.2 Cutover


2. Set the priority of all applicable signaling routes to a low value, therebymaking sure that the new IP signaling connections will be used instead ofwhen they are deblocked.

Go through all signaling route Mtp3bSr MOs that are to be migrated. Forall these signal routes, set the priority (in Mtp3bSr) value to a low value(for instance 2).

3. If the M3uAssociation MOs created in the Preparation stage are not active,set them to Auto Activate . This order will, for an association with role =CLIENT, set the attribute autoStartAssociation = true. If a new CV is madeafter this action, the associations will be automatically started after a noderestart with this CV.

4. Verify that no M3uAssociation alarms are raised, and that the usageStateof the newly created Mtp3bSr MOs are set to active.

Wait until the usageState in all related ATM Mtp3bSr MOs are set toidle. When this happens all signaling is going through IP routes. If theusageState attribute is not set to idle within a certain time period, it isrecommended to proceed with the next step.

Mtp3bsr should be deblocked by action deBlockSignallingRoute otherwiseit will not get active state.


8.3 Migrate Iur Control Plane

This procedure describes how Iur Control plane connections are migrated toET-MFG and how the two ET-MFG boards are installed during this migration. Itis assumed that the necessary preparations have been completed, and that theRNC node is running P6 software with no ET-MFG boards installed.


7558/1543-FAB 102 614 Uen B 2008-02-26







6. Follow Step 2 on page 68 to Step 7 on page 74 in Section 8.1 Preparationon page 67.

8.4 Tidy up

1. Delete all ATM signal routes (all Mtp3bSr MOs related to ATM) that arenot supposed to be used anymore.

Note: This will impact traffic (both Iu-PS and Iu-CS user plane) that arecurrently controlled by the deleted signal routes — these calls willtemporarily be dropped.

2. If the ATM-ET board is not used, remove it.

76 58/1543-FAB 102 614 Uen B 2008-02-26

Iur User Plane

9 Iur User Plane

GigaBitEthernet lurLink

IpInterface

IpSystem

IpAccessHostPool

IpAccessHostEt

C0001421A

Figure 12 Managed Objects Related to Iur Migration

The migration of the Iur user plane to Ethernet links may include reallocationand replacement of the board.




• ET-MFG will be added but there is no free slot in the RNC subrack.

For Iur user plane migration to IP:

• Decide if all Iur links will be migrated at the same time.

• Decide if Serving and Drift RNC will be migrated at the same time.

Having at least two ET-MFG for Iur user plane is recommended.

9.1 Preparation for Iur User Plane over IP (ET-MFGAlready Installed)

This procedure describes how Iur User Plane connections are migrated toET-MFG, provided that the RNC node already has two ET-MFG boardsinstalled. It is assumed that the RNC node is running P6 software.

1. Create one IpInterface for each ET-MFG board. If other interfaces havealready been migrated this MO may already exist and can be used. Set theattributes as described in Table 31 on page 78.

7758/1543-FAB 102 614 Uen B 2008-02-26





Id <n> The number of theinterface on thisET-MFG.


defaultRouter0

defaultRouter1

defaultRouter2

<routerlPaddress> The IP address for thedefault router. At leastdefaultRouter0 must beset.


vLan It is recommended touse separate subnetsfor Use Plane andControl Plane.




78 58/1543-FAB 102 614 Uen B 2008-02-26

Iur User Plane





Set if rps = true.




2. Create one IpAccessHostEt for each ET-MFG board to use. Set theattributes as described in Table 32 on page 79.

Table 32 Attributes to be Set in IpAccessHostEt MO



Id <subrack>-<slot>-<interface>

Where subrack, slot,and interface are equalto where this host islocated.


7958/1543-FAB 102 614 Uen B 2008-02-26



ipAddress <ipaddress> The IP address that willbe assigned to this host.

ipInterfaceMoRef ManagedElement=1,Equipment=1,Subrack=<MS>,Slot=<slot>,PlugInUnit=1,EtMfg=1,GigaBitEthernet=1,IpInterface=<n>

Reference to theinterface on theET-MFG created above,or use an existing one.

Where slot = where theET-MFG is located andn is the interface on theET-MFG.


3. Create one IpAccessHostPool MO for Iur. Set the attributes as described inTable 33 on page 80.

Table 33 Attributes to be Set in IpAccessHostPool MO


Parent ManagedElement=1,IpSystem= 1

Id Iu_Iur[-1] There is one commonIpAccessHost used forboth Iu and Iur. The -1is an optional postfix.


ipAccessHostRef List of: ManagedElement=1,IpSystem=1,IpAccessHostET=<x>

Include all IpAccessHostEt created above forthe ET-MFG board.


9.2 Cutover

1. Configure the Iur link to use the IpAccessHostPool by setting the attributesas described in Table 34 on page 80.

Table 34 Attributes to be Set in IurLink MO


userPlaneIpResourceRef

ManagedElement=1,IpSystem=1,IpAccessHostPool=<Iu_Iur [-1]>

The IpAccessHostPoolcreated above.

2. Check configuration in the other RNC.

80 58/1543-FAB 102 614 Uen B 2008-02-26

Iur User Plane

3. Switch the traffic over to IP by setting the attributes as described in Table35 on page 81.

Table 35 Attributes to be Set in IurLink MO


userPlaneTransportOption

[Ipv4] = true , [ATM] =false

4. Observe the traffic. If there is a fault, revert to ATM transport by setting theuserPlaneTransportOption [Ipv4] = false [ATM] = true

9.3 Migrate Iur User Plane

This procedure describes how Iur user plane connections are migrated toET-MFG and how the two ET-MFG boards are installed during this migration. Itis assumed that the necessary preparations have been completed, and that theRNC node is running P6 software with no ET-MFG boards installed.



2. Make sure the board is not being used for any traffic. See Section 3.1.1Reallocation of Connections on page 10.




6. Follow steps from Section 9.1 on page 77 and Section 9.2 on page 80.

8158/1543-FAB 102 614 Uen B 2008-02-26


82 58/1543-FAB 102 614 Uen B 2008-02-26

MUR

10 MUR

10.1 Preparation

Migrating from IPoATM for Mur to Ethernet, means that O&M traffic will nottravel via IPoATM links toward the O&M router but rather via fast Ethernet andIP/Ethernet infrastructure switching toward the O&M router. There are twopossible ways to configure Mur over IP/Ethernet:

• Via Fast Ethernet on the GPB to site infrastructure

• Via Fast Ethernet and ET-MFX

Figure 13 on page 83 shows how the GPB Ethernet can be connected to theET-MFX. The cables between board and ICF are connected at the factory, butthe “loop cable” on the ICF needs to be attached if switching of Mur in theET-MFX is to be used.

Note: The pair of cables that are connected to the pair of Central MPs mustnot be connected to the same ET-MFX board. Also the pair of cablesthat is connected to the Mur must not be connected to the sameET-MFX. This is to prevent the failure of one board making both cablesin the pair useless.

ET-MFX

Eth

Local terminal

Mur

ICF

GPB

C0001422A

Figure 13 How to connect GPB Ethernet to ET-MFX

8358/1543-FAB 102 614 Uen B 2008-02-26


For Mur migration to IP the following preconditions are necessary:

• ET-MFX boards are installed in the RNC according to the TransmissionBoard Expansion instruction.

• RNC is running on P6 software.

• RNC Element Manager is available.

10.2 Migration

This procedure describes Migrating from IPoATM for Mur to Ethernet, meaningthat O&M traffic will not travel via IPoATM links toward the O&M router butrather via fast Ethernet and IP/Ethernet infrastructure switching toward O&M.There are two possible ways to configure Mur over IP/Ethernet:

In this procedure it is assumed that the RNC node is running P6 software, andthat the RNC Element Manager is available.

1. Attach the Ethernet to a known position that connects to ET-MFX on ICF.

2. Insert the loop cable in ICF to connect the GPB ports with two ports on theET-MFX if ET-MFX aggregation is to be used (two cables—one per GPB).

3. Run the Site Basic Wizard in RNC Element Manager, Fast Ethernetconfiguration with ET-MFX (O&M connection to the node will be lost).

4. Select an XML file with the configuration data. Viewing the configurationdata in the file can be done using the Wizard’s interface. If any of theconfiguration data needs to be changed, edit the file and then open itagain in the tool.

5. Click Finish to configure the node. When this is done, the Mur is configuredin the RNC and ready to be connected. Insert the WAN cable to ET-MFX.

6. If the update has been successful, O&M communication with the node willnow use the Ethernet connection. Verify that this is the case and if soremove the following MOs for tidying up purposes:

• IpAtmLink

• Aal5TpVccTp

• VclTp

7. Remove the ATM based transport equipment unless it is used by other links.

84 58/1543-FAB 102 614 Uen B 2008-02-26

atm to ip migration instruction rnc

Technology