Scribd
Upload
379 views

ATM To IP Conversion Process

The document provides instructions for migrating a node from ATM to IP transport by running a series of script commands from the Element Manager. Key steps include: 1) Configuring the laptop IP address and installing necessary management tools; 2) Running initial scripts to enable the Ethernet switch and verify IP connectivity; 3) Configuring the Iub interface on the RNC to use IP transport; 4) Running additional scripts to complete the migration from ATM to IP.

Uploaded by

manojkumartomar7513
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
379 views

ATM To IP Conversion Process

The document provides instructions for migrating a node from ATM to IP transport by running a series of script commands from the Element Manager. Key steps include: 1) Configuring the laptop IP address and installing necessary management tools; 2) Running initial scripts to enable the Ethernet switch and verify IP connectivity; 3) Configuring the Iub interface on the RNC to use IP transport; 4) Running additional scripts to complete the migration from ATM to IP.

Uploaded by

manojkumartomar7513
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

1) Set Laptop Configuration IP Address: 10.131.200.

10 (one more or less than the node IP address through which you are logging for e.g. UPN001-IP address->10.131.200.9) Net Mast: 255.255.255.248 Gateway: 10.131.200.9 (UPN001-IP address->10.131.200.9) 2) Install filezilla server Settings: In shared folder add path to folder containing upgrade package. 3) Install Element Manager for RBS 4) Install Element Manager for RNC. Login site through EM 5) Check Node time it should be in UTC time context i.e. five and hour less than the real time. Software Upgradation Open filezilla server Go back to EM -> Go to Software ->Upgrade Package (Right click create) ->copy the name of folder containing the new s/w package paste in user label. Set ftpServerIpAddress as laptop IP Address (i.e. 10.131.200.10). Username=rbs, Password=rbs. --> upFilePathonFtpServer = ./<Name of the .XML file in S/W Package folder>. Click Create Package Click Install Package Click Verify Package Click Upgrade Node -> Hard Upgrade Then go back to Software->Upgrade Package-> Right click on new package on right side of the window -> go to properties to show progress status Close error message after completion. Close EM and reopen EM Again go to Software-Upgrade Package-> right click the new package and click confirm upgrade. Make CV. Enable IP Card 11) Go to Configuration on EM -> Run Command file-> browse Select script Updated_ETMFX11_Script.mo.txt Check halt on error Check Verbose Logging 12) Go to Software Allocation Select ETMFX Edit Slot List -> slot 2 Apply ok

6) 7)

8) 9) 10)

Nothing in fan list 13) N/W Element -> Setting ->Uncheck Autoconfig Apply Check Autoconfig Apply Ok 14) Equipment -> Sub rack=MS-> unlock card-> refresh 15) Make CV after ETMFX Scripts Migration Scripts 16) Go to Configuration on EM -> Run Command file-> browse Select script 01_UPN001_ETMFX_Def.mo Check halt on error Check Verbose Logging Go to Equipment ETMFX->Ethernet Switch->status Go to 6th slots properties->Operating mode -> Change from 6 to 4 ( 4 is for 100 base T (fe port) and 6 is for 1000 Base t (Ge port) check continuity From Node B (GPB) to RNC(GPB) ie Control Plane and Node B (AccessET) to RNC(AccessET) which is user plane Two Methods ping (open cygwin session to the node from laptop) can be used to check continuity between both planes and through element manager we can check continuity for User plane. If User plane continuity check using EM IP -> IP System -> IP AccessEThost-> property->action-> rncaccess host et address (there will be two check one by one)-> execute Ping Method Open moshell session via cygwin to the node: Ping User plane: St ipaccess -> get <proxy of IPacceshotET > acc <proxy of accessET> ping Ping control plane: To get IPaddress of GPB-> i.e Control plane of Node B Get <proxy of AccessGPB> -> not Ip Address

Ipac_ping z <source address is Node B GPB Ip address> -d <Destination adrresof RNC access GPB> (Note: There will be six ip of RNC GPS , ping each of them) After checking continuity, run second script 02_UPN001_IP_Def.mo. Run 03_ATM_Switch_To_IP.mo Run 04_change_synch.mo note : ( if synch is not enable u can reset ETMFX in RNC) Check Synch status of Node B -> ATM ->synchronization->synch priority active Now make changes in Iub at RNC End: Lock Iub of site from EM of RNC Go to properties of Iub Put ipaddress of access gpb of node b in remotecpipaddress1 Preferred Subrack = MS Userplane resourceref -> select path from Drop Down Button Atm -> false Ip True Click apply Atm -> false Ip True Click apply Unlock Iub Make CV Check Traffic St carrier -> in Node B If some problem do Resub <iub> subrack=ms

17)

18) 19) 20) 21)

CHANGES TO BE DONE IN SCRIPTS In 01_UPN001_ETMFX_Def.mo replace 1) vid Integer 461 with the vid of site to be migrated -> total three replacements would be done. 2) vid Integer 961 with the vid of site to be migrated -> total twelve replacements would be done. In 03_ATM_Switch_To_IP.mo replace 1) 2) 3) 4) 5) vid Integer 461 with the vid of site to be migrated -> total one replacements would be done. Change in ipAccessHostEt=1 ipAddress String "10.128.27.4", should be as per dld Change IpAccessHostGpb=1 ipAddress String "10.128.27.5", should be as per dld Check defaultRouter0 String "10.128.27.1" should be as per dld Check ntpServerIpAddress String "10.128.17.133" syncref 2 , should be as per dld. (Not to be changed-Different for HUB, SUBHUB, Direct Node Bs)

6) Check ntpServerIpAddress String "10.128.17.132" syncref 1, should be as per dld. (Not to be changed (Not to be changed-Different for HUB, SUBHUB, Direct Node Bs))

You might also like