Iub Migration From ATM to IP for Node Bs belong to 3000 series:

Introduction: For Iub Migration from ATM to IP, the key concepts are to convert
both User plane and Control plane transport between Node B and RNC to IP
from ATM.
Firstly, IP Interfaces are required to be created for both User plane and Control
Plane at Node B as well as RNC.
Hardware requirement for creating IP Interfaces:
1. ETMFX card (allocated software ETMFX11) is required at Node B end.
Product No. is as follow: ROJ 119 2315/1 or ROJ 119 2315/2.
2. ETMFX card (allocated software ETMFX12) is required at RNC end.
Product no. is as follow: ROJ 119 2316/1 or ROJ 119 2316/2.
IP Host on ETMFX card (User Plane): IPaccesshostet
IP Host on control plane: IPaccesshostGpb
The Migration process is as follow:
1. Connect the Laptop to Node B through LAN cable and create a LAN
connection.
2. Open Command Prompt and telnet the O&M IP of Node B. Check the
clock. It should be correct and in GMT (IST-5:30) format. If not set
correctly, then set the clock.

3. Check the no. of CVs, stored inside the node. If its 50 or nearly 50, some CVs
are required to be deleted so that new CVs can be created and put into the
rollback list.

4. Now logged into the Node B through RBS Element Manager.

5. Go to software and check the existing upgrade package. The upgrade package
should be compatible with the ETMFX card, to be inserted. Otherwise, Node B is
required to be upgraded to a new package, compatible to ETMFX card. In this
test case, the upgrade package is CXP901 2073/1 Release R10AV/9. Since the
existing package is not compatible with ETMFX card (ROJ 109 2315/1), Node is
to be upgraded to a new release R11C4.

6. Before proceed to the up gradation, create a new CV and set it startable. This
will mark and save the existing configuration of Node B on ATM.

7. For software upgrade, we need an application for FTP. In this test case, BPFTP
is used. Since the new package is stored in laptop, Node B will behave as a FTP
client and package would be downloaded to Node B from laptop, configured as
FTP server.
Steps to configure BPFTP for creating a User account and initiate a FTP session is
given in following screen shots.

8. Click on On-line, once account is successfully created.

9. Now go to Element Manager --------- Software-------- Upgrade package and

then right click on it. Select the option create.

10. In User Label, write the name of Package. Put the IP address of laptop in the
field ftpServerIpAddress. User ID and Password will be rbs. In
upFilePathOnFtpServer, provide the name of upgrade file as it is saved in the
laptop. Find the notation below.
./filename.extension
11. Click on Create Package

12. Check BPFTP for file transfer.

13. Once package has been successfully created, click on Install Package --
Full Install.

14. Now loadmodules will start to get downloaded to Node B. Check BPFTP
while module transfer takes place.

15. Check the progress on Element Manager Window. Installation can be failed
for following reason:
a) FTP server is not properly configured.
b) Name of the upgrade file is wrongly spelled in upFilePathOnFtpServer
field.
c) Upgrade package is corrupted.

16. Once installation of the package is completed, click on Upgrade Node-------

Hard Upgrade.

17. It will take approximately 18 minutes to upgrade the Node. A software

upgrade often fails for following reasons:
a) Time is not properly set in Node B.
b) No. of CVs is already 50, so there is no space, available for new CVs, to be
created. In the process of Upgradation, three system-generated CVs are
created.

18. Once Upgrade is done, version of Element Manager in the Node will change.
Close the existing EM Window and re open it.

19. Go to the same window: Software-----Upgrade Package--- right click on

the new package----- Properties.

20. It will ask for Upgrade confirmation, click on Confirm Upgrade.

21. Once Upgrade is completed, a new CV would be created and set startable.
The format of the CV will be as follow:
Fi_Package Name_Release.

22. In order to mark the completion of software Upgrade a CV can be created

manually as after_Upgrade.

23. Now find the slot where ETMFX card is required to be inserted in Node B.
Refer the design for the same. Before allocating software against that slot, check
the availability of the slot. It should not be used for any other allocation.
In this test case slot 5 is used for ETMFX insertion.

Though the slot is physically vacant but it was initially configured to allocate the
software RBS_RAXB. The slot is to be made available. Follow the steps, given
below:

24. Go to SwAllocation=RBS_RAXB----right click on it- Edit Slots.

25. Drag Slot=5 from Selected slots and drop it to Available slots.

26. Go to Software Allocation----right click-create. Select Edit List under Slot

List. Transfer Slot=5 from Available slots to Selected slots.

27. Repeat the same process for repertoire. Select CPP_ETMFX11 as the repertoire
against slot=5.

28. Type RBS_ETMFX as role, Then Apply----ok.

29. Now software has been successfully allocated against Slot 5 where ETMFX
card is to be inserted.
Now insert the card.

30. Now go to Network Element------- Settings.

First, uncheck the option autoconfigarationallowed then apply it. Now check it
and apply it. Finally click on ok.

ETMFX card at slot 5 will take a reboot. Finally green and yellow LED would be
stable. It will indicate that the plug in unit is successfully created and is
operational.

31. Under Equipment tab, we will find ETMFX card is shown at slot 5. Right click
on it to unlock the card. Yellow LED would be off.

32. Create a CV and set it startable.

33. Once the card is detected and plug in unit is successfully created, following
MOs are required to be created and configured:
a) EthernetSwitch and
b) EthernetSwitchPort

Before IP Interface is created, Ethernet switch ports would be configured and

tagged with certain VLAN on Datalink Layer. VLAN would be of two types, one
is for Iub and another is for Mub (If Mub is also planned for IP migration).
The structure of ETMFX card is as follow:

The port and LED details are as follow:

Since there are 7 ports, available on ETMFX cards, 7 ethernetswitchports would

be created.
It would be troublesome to configure Ethernet Switch Ports, manually since it
involves with a no. of MO definitions. There should be a script of ETMFX card
definition, available while migrating Iublink. We are required to run the script.
Process is as follow:

Check Halt on Errors since it will halt the script if an error is encountered in
any line.

Click on start to run the script.

Once the script is made run successfully, a message will appear, at the end of the
screen as Configuration Succeeded.

34. Now Ethernet Switch Ports are created and VLANs are tagged. Its time to
create and configure IP Interface and assign IP Addresses to interfaces.
For User Plane: IPAccessHostEt An IP host on ET Card is to be configured.
For Control Plane: IPAccessHostGpb An IP host on GPB Card is to be
configured. Since there is no GPB card present in Node B, IPAccessHostGpb is
created in CBU.
Once IPAccesshostEt of Node B is reachable from IpAccessHostEt of RNC and
vice-versa, the user plane connectivity of Iublink is built on IP. Similarly,
IpAccessHostGpb of Node B can be pinged from IpAccessHostGpb of RNC for
control Plane connectivity.
The basic concept is as follow:

To accomplish the connectivity between different interfaces, we have to configure

following:
a) IP Interface
b) IpAccessHostEt
c) IpAccessHostGpb
d) Sctp
e) IpSyncRef
We shall have a script for the same. Run the script as shown below:

35. Once Interfaces are properly configured, a media is required to be

provided between RNC and Node B. It can be through switches or
routers.
Key concepts are:
a) If the assigned Ip Addresses of Interfaces belong to Node B and RNC are
of same subnet, media can be extended through switches.
b) If they belong to different subnet, router is required in between Node B
and RNC to route the traffic from one subnet to another.
36. If an optical media is provided to Node B/RNC from switches/routers, port
G (7th Port) of ETMFX card would be used. The SFPs, to be used at G port are as
follow:

For optical media, vlan for Iub must be tagged at Port 7 and Port 7 should be
unlocked.
For electrical media, vlan for Iub must be tagged at Port 6 (Port F) and Port 6
should be unlocked.

37. Once media is extended and a link is built up between Node B and switch,
check IpAccesshostEt. If IpAccesshostEt is enabled and unlocked, the local
connectivity between Node B and switch is established.

38. Now check IpAccessHostGpb. It should be unlocked and enabled as well. It

will lead to the fact that control plane at Node B end is successfully configured.

39. In IpSyncRef, IP addresses of IpAccessHostEt of RNC are defined.

Key concept is:
RNC is the source of IPSync for Node B
IpSyncRef of Node B = IpAccessHostEt of RNC
If IpSyncRef at Node B end is enabled and unlocked, Node B is reachable from
RNC and vice versa. This will conclude that user plane connectivity is
successfully established between RNC and Node B.

To check the connectivity, we can ping IP Addresses of IpSyncRef from

IpAccessHostEt=1. The process is as follow:

40. Now go to ATM------ Synchronization. Set IPSyncRef as primary and active

Synchronization references. Process is shown below:

If active reference goes down, reference, defined at priority 2 will become active.

41. The transport network for Iublink is still on ATM and Node B is up with all
the sectors, radiating. Now, we have to change the transport of Iublink from ATM
to IP for both user plane and control plane. The definition for the same is as
follow:
ECHO "------------- 2) Set userPlaneIpResourceRef"
SET
(
mo "ManagedElement=1,NodeBFunction=1,Iub=1"
exception none

userPlaneIpResourceRef Ref
"ManagedElement=1,IpSystem=1,IpAccessHostEt=1"
)
ECHO "------------- 2) Set userplanetransport to ip in iub"
SET
(
mo "ManagedElement=1,NodeBFunction=1,Iub=1"
exception none
userPlaneTransportOption Struct
nrOfElements 2
atm Boolean false
ipV4 Boolean true
)

ECHO "------------- 2) Set controltransport to ip in iub"

SET
(
mo "ManagedElement=1,NodeBFunction=1,Iub=1"
exception none
controlPlaneTransportOption Struct
nrOfElements 2
atm Boolean false
ipV4 Boolean true
)
We can manually change it or we can do it via script as shown below:

42. Configuration for Iub Migration at Node B end is completed. Sectors will go
down and Nbap will be disabled since we need to change the transport of Iublink
from RNC as well.

43. Logged into the RNC with RNC Element Manager.

Go to Radio Network--- Iublink

Right click on particular Iublink (to be migrated) and lock it.

Again right click on Iublink and go to Properties.

44. Select IpAccessHostPool=Iub as userPlaneResourceRef

Now change userPlaneTransportOption. Set atm False and ipv4 True. Apply it.

45. Put the Ip address of IpAccessHostGpb (Node B) in remoteCpIpAddress1.

Set atm False and ipv4 True at controlPlaneTransportOption. Then Apply-ok.

46. Now unlock the Iublink and check sectors.

All the Utrancells and Nbap Common/Dedicated would be enabled.

47. Logged into the Node B. Go to Radio Network---- Iub.

NbapCommon and NbapDedicated would be enabled.

48. Expand Sectors---- Carrier. All the channels would be displayed. Now go to
Iub------right click-Properties.
Find User Plane and Control Plane Transport is on IP.

49. Create a CV to mark the completion of Migration process and set it startable.
Check traffic from RNC and test the calls (voice/video and data) along with the
representative of customer end.

50. Conclusion Following this Migration process, we can migrate any Node B
on ATM. It could be Hub/Sub-Hub or terminal site.
Once a Hub or Sub-Hub site is migrated, there is no disturbance, configured on
existing ongoing ATM link. If the physical E1 or STM is not taken out, media on
ATM can still pass through the terminal sites from Hub or Sub Hub even if the
site itself is migrated to IP.