Está en la página 1de 37

NokiaNetworks

WCDMA RAN, Rel. WCDMA


16, Operating Documentation,
Issue 03

Cloning RNC OMS


DN09138239
Issue 01A
Approval Date 2015-05-18

CloningRNCOMS

The information in this document applies solely to the hardware/software product (Product) specified
herein,andonlyasspecifiedherein.

ThisdocumentisintendedforusebyNokiaSolutionsandNetworks'customers(You)only,anditmaynot
beusedexceptforthepurposesdefinedintheagreementbetweenYouandNokiaSolutionsandNetworks
(Agreement) under which this document is distributed. No part of this document may be used, copied,
reproduced, modified or transmitted in any form or means without the prior written permission of Nokia
Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if that
Agreementhasexpiredorhasbeenterminated,YoumaynotusethisdocumentinanymannerandYou
areobligedtoreturnittoNokiaSolutionsandNetworksanddestroyordeleteanycopiesthereof.

The document has been prepared to be used by professional and properly trained personnel, and You
assumefullresponsibilitywhenusingit.NokiaSolutionsandNetworkswelcomeYourcommentsaspartof
theprocessofcontinuousdevelopmentandimprovementofthedocumentation.

This document and its contents are provided as a convenience to You. Any information or statements
concerningthesuitability,capacity,fitnessforpurposeorperformanceoftheProductaregivensolelyon
anasisandasavailablebasisinthisdocument,andNokiaSolutionsandNetworksreservestheright
tochangeanysuchinformationandstatementswithoutnotice.NokiaSolutionsandNetworkshasmadeall
reasonableeffortstoensurethatthecontentofthisdocumentisadequateandfreeofmaterialerrorsand
omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But,
NokiaSolutionsandNetworks'totalliabilityforanyerrorsinthedocumentisstrictlylimitedtothecorrection
ofsucherror(s).NokiaSolutionsandNetworksdoesnotwarrantthattheuseofthesoftwareintheProduct
willbeuninterruptedorerror-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE
LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,
INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF
PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY
ARISEFROMTHEUSEOFTHISDOCUMENTORTHEINFORMATIONINIT,EVENINTHECASEOF
ERRORSINOROMISSIONSFROMTHISDOCUMENTORITSCONTENT.

ThisdocumentisNokiaSolutionsandNetworksproprietaryandconfidentialinformation,whichmaynotbe
distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and
Networks.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
maybetrademarksoftheirrespectiveowners,andtheyarementionedforidentificationpurposesonly.

Copyright2016NokiaSolutionsandNetworks.Allrightsreserved.

f Important Notice on Product Safety


Thisproductmaypresentsafetyrisksduetolaser,electricity,heat,andothersourcesofdanger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this
productandonlyafterhavingcarefullyreadthesafetyinformationapplicabletothisproduct.

The safety information is provided in the Safety Information section in the Legal, Safety and
EnvironmentalInformationpartofthisdocumentordocumentationset.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its
productsandservices.Wewouldliketoencourageyouasourcustomersanduserstojoinusinworking
towardsacleaner,saferenvironment.Pleaserecycleproductpackagingandfollowtherecommendations
forpoweruseandproperdisposalofourproductsandtheircomponents.

IfyoushouldhavequestionsregardingourEnvironmentalPolicyoranyoftheenvironmentalserviceswe
offer,pleasecontactusatNokiaSolutionsandNetworksforanyadditionalinformation.

2 DN09138239 Issue:01A
CloningRNCOMS

Table of Contents
Thisdocumenthas37pages

Summaryofchanges..................................................................... 5

1 IntroductiontocloningRNCOMS.................................................. 6
1.1 Hardwarerequirementsforcloningprocedure...............................6
1.1.1 HPProLiantDL360G6.................................................................. 6
1.1.2 HPProLiantDL360pGen8............................................................ 6
1.1.3 HPProLiantBL460cGen8.............................................................6
1.2 Softwarerequirementsandpreconditionsforcloningprocedure.....
7
1.3 Mainstepsofcloningprocedure.................................................... 7

2 CloningconfigurationdatafromreferenceOMStotargetOMS......
9
2.1 Introductiontocloningconfigurationdata...................................... 9
2.2 ExportingconfigurationdatafromreferenceOMS.........................9
2.3 CreatingbootableUSBstick........................................................ 10
2.3.1 CreatingbootableUSBstickinWindows..................................... 11
2.3.2 CreatingbootableUSBstickinLinux...........................................13
2.4 Transferringthecloneimageandtheclonerunnertothebootable
USBstick......................................................................................15
2.4.1 Transferringthecloneimageandtheclonerunnertothebootable
USBstickinWindows.................................................................. 15
2.4.2 Transferringthecloneimageandtheclonerunnertothebootable
USBstickinLinux........................................................................ 17
2.5 RestoringcloningimageontargetOMS...................................... 20

3 IntegratingRNCOMStoNetAct.................................................. 27
3.1 IntroductiontointegratingRNCOMStoNetAct...........................27
3.2 ConfiguringNetActinterfacewithOMS........................................27

4 ConnectingRNCOMStoRNC.................................................... 30

5 VerifyingRNCOMSwithnewconfigurationdata.........................32

6 Appendix...................................................................................... 34
6.1 LoggingintoOMS....................................................................... 34
6.2 Emulatingterminalwiththescreencommand...........................35

Issue:01A DN09138239 3
CloningRNCOMS

List of Figures
Figure1 ProcedureofRNCOMSintegrationtoNetAct................................... 27

4 DN09138239 Issue:01A

CloningRNCOMS Summaryofchanges

Summary of changes
Changesbetweendocumentissuesarecumulative.Therefore,thelatestdocument
issuecontainsallchangesmadetopreviousissues.

Changes between issue 01 (2014-02-28, RU50) and 01A (2015-05-18, RU50)


AnotehasbeenaddedinsubchapterMainstepsofcloningprocedure.
SubchapterRestoringcloningimageontargetOMShasbeenupdated.
SubchapterExportingconfigurationdatafromreferenceOMShasbeenupdated.

ThisisthefirstissueofthisdocumentforRNCOMS3.0(RU50).

Issue:01A DN09138239 5

IntroductiontocloningRNCOMS CloningRNCOMS

1 Introduction to cloning RNC OMS


Theproceduredescribesthefollowingscenario:cloningofafullyconfiguredRNCOMS
toanewtargetRNCOMS(orseveralOMSs).

1.1 Hardware requirements for cloning procedure


TherearethreetypesofOMSsupportedbythecloningprocedure:

HPProLiantDL360G6
HPProLiantDL360pGen8
HPProLiantBL460cGen8

ItispossibletocloneRNCOMSonlybetweenhardwareunitsofthesametype,for
examplefromHPProLiantDL360pGen8toHPProLiantDL360pGen8.

1.1.1 HP ProLiant DL360 G6


IfHPProLiantDL360G6isused,itneedstomeetthefollowinghardwarerequirements:

twoIntelXeonQuad-coreprocessorsE5540(2.53GHz,8MBcache,80W)
12GB,24GB,or48GBmemory
four146GB,147GB,or300GBlargeformfactor(LFF)SASsuperfast(10000rpm)
harddrives
HPSmartArrayP410iembeddedcontroller(RAID0/1/1+0)
KVMextension
USB2.0ports(1front,2rear,1internal)

1.1.2 HP ProLiant DL360p Gen8


IfHPProLiantDL360pGen8isused,itneedstomeetthefollowinghardware
requirements:

twoIntelXeon8-coreE5-2670processors(2.60GHz,20MBcache,115W)
64GBmemory
four600GBlargeformfactor(LFF)SASsuperfast(15000rpm)harddrives
HPSmartArrayP420iembeddedcontroller(RAID0/1/1+0)
KVMextension
sevenUSB2.0ports:4rear,2front,1internal(secure)

1.1.3 HP ProLiant BL460c Gen8


IfHPProLiantBL360cGen8isused,itneedstomeetthefollowinghardware
requirements:

twoIntelXeon8-CoreE5-2670processors(2.60GHz,20MBcache,115W)
64GBmemory-SingleRankx4PC3-12800R(DDR3-1600)
two300GBsmallformfactor(SFF)SASharddrives(15000rpm)

6 DN09138239 Issue:01A

CloningRNCOMS IntroductiontocloningRNCOMS

battery-supportedHPSmartArrayP220icontroller(RAID0/1)
c-ClassBladeSUVCable(VGA,USB,serial)
integratedLights-Out4(iLO4)StandardBladeEdition

1.2 Software requirements and preconditions for


cloning procedure
ThereferenceOMSneedstomeetthefollowingsoftwarerequirements:

ThereferenceOMSisinstalledwithcorrectsoftwarebuildusingFEWS,USB,or
factorydelivery.
ThereferenceOMSisfullyconfiguredatRU50EP1level.
Commandsforthecloningproceduremustbedoneattherootlevel(su -).

ThetargetOMSneedstomeetthefollowingsoftwarerequirements:

ThetargetOMScanbeeitherclearorpre-installed(cloningscriptinstallsand
configuresthetargetOMStothecorrectSWlevel).
Commandsforthecloningproceduremustbedoneattherootlevel(su -).

1.3 Main steps of cloning procedure


ThemainadvantageofcloningOMSoverinstallingitfromscratchissavingbothtime
andmanualwork.OncethereferenceOMShasbeenconfigured,itsconfigurationdata
canbetransferredtoasmanytargetOMSsasrequired.Theoperatorneedstoprovide
onlythefollowinginformation:

OMSIPdeploymenttype(singleIPaddressornorthbound/southboundapproach)
OMSIPaddressorOMSnorthboundandsouthboundIPaddresses(dependingon
deploymenttype)
networkconfiguration:netmask,externalDNSserverIP,externalNTPserverIP,
defaultgateway
passwordsforaccountsroot,_nokfsoperator,and
_nokfssysemoperatorfallback
omsFtpUserpassword
OMSclusterID
timezone

Thecloningprocedurestepsareasfollows:

choosingthefullyconfiguredRNCOMSasareferenceone
exportingtheconfigurationdatafromthefullyconfiguredRNCOMSbyrunningof
theOMSclonerunnerscript
creatingabootableUSBstick
transferringthecloneimageandtheclonerunnerscriptfromthereferencefully
configuredRNCOMStothebootableUSBstick
restoringthecloningimageonthetargetOMS
integratingthetargetOMStoNetAct

Issue:01A DN09138239 7

IntroductiontocloningRNCOMS CloningRNCOMS

connectingthetargetOMStoRNCforthefirsttime
verifyingthetargetOMSwithnewconfiguration

g Note: Duringcloningprocedure,LDAPdatabaseisdumpedandrestored.Therefore,
allusers,groups,permissionsaddedtoLDAP(defaultornondefault)arerecreated.

8 DN09138239 Issue:01A

CloningRNCOMS CloningconfigurationdatafromreferenceOMSto
targetOMS

2 Cloning configuration data from reference


OMS to target OMS

2.1 Introduction to cloning configuration data


FollowthisproceduretocopytheconfigurationdatafromareferenceRNCOMSto
targetRNCOMS(orseveralOMSs).
ChooseonefullyconfiguredRNCOMStoperformtheprocedure.

2.2 Exporting configuration data from reference OMS


Purpose
ThisproceduresavesexistingconfigurationdataonthereferenceOMSbefore
transferringtothetargetOMS.
Ifthecloneimagesizeisbiggerthan2GB(2000MB),thenthecloneimageissplitinto
chunks<=2000MBinsize.Foreachpartasuffixisappendedtotheoriginalimagefile
name.Thesuffixcontainsapartnumberrepresentedbythreedigitnumberwithleading
0(.000,.001,).ForeachimageparttheseparateMD5sumfileisgeneratedwhose
nameiscomposedbyappending.md5 suffixtotheoriginalimagefilepartname.The
originalcloneimagefileisdeleted.

g Note: ExecutetheprocedureonthereferenceRU50EP1OMS.

Before you start


MakesurethatvaluesoffsdbBackupoftheClusterRoot\DB\DB_Topologyand
DB_AlarmparametersaresettoS.Toviewormodifyvaluesoftheseparameters,open
ParameterToolinApplicationLauncherandgothethefollowingpaths:
ClusterRoot/DB/fsdbName=DB_Topology/fsdbBackup/
ClusterRoot/DB/fsdbName=DB_Alarm/fsdbBackup/

t Tip: Iftheoperationisexecutedremotely,considerusingthescreentool.Seesection
Emulatingterminalwiththescreencommand.

Issue:01A DN09138239 9

CloningconfigurationdatafromreferenceOMSto CloningRNCOMS
targetOMS

Procedure

1 Log in to the OMS with SSH as Nemuadmin.

2 Log in as root with the su - command.

3 Run the clone runner script.


Executethefollowingcommand:
# omsswm_clone_create

w NOTICE: Theclonerunnerisstoredinthe/opt/Nokia_BP/sbin/directorybutyou
donotneedtoindicatethepathexecutingit.

TheOMSclonerunnerscripttriggersfullbackupofthereferenceRNCOMSandthe
correspondingMD5checksumfile.
Thescriptproduceson-screenoutputwithinformationaboutthecloneimageandthe
MD5filelocation.
Thecloneimageandchecksumfilenamesare:
cloning_<OMS_Id>_rnc_full_<SWRelease>_<date&time>.tar.gz
cloning_<OMS_Id>_rnc_full_<SWRelease>_<date&time>.tar.gz.md
5
wherefilenameattributesare:
<OMS_Id>-uniqueOMSidentifierinuserradionetwork;
<SWRelease>-activesoftwaresetname;
<date&time>-dateandtimeofthecloneimagecreationwithformat
yyyymmdd_hhmmss

Example
cloning_OMS-
77_rnc_full_R_GOMS6_1.103.1.0.oms.corr12_20130229_093626.tar.gz
cloning_OMS-
77_rnc_full_R_GOMS6_1.103.1.0.oms.corr12_20130229_093626.tar.gz.md5

Thelogfilefromtheclonerunnerisstoredinthelogsubdirectoryofthecloneimage
directorywiththefollowingname:
omsswm_clone_create_<clone_image_name>.log,forexample:
omsswm_clone_create_cloning_OMS-
77_rnc_full_R_GOMS6_1.103.1.0.oms.corr12_20130229_093626.log

2.3 Creating bootable USB stick

10 DN09138239 Issue:01A

CloningRNCOMS CloningconfigurationdatafromreferenceOMSto
targetOMS

2.3.1 Creating bootable USB stick in Windows


Purpose
FollowthisproceduretocreateabootableUSBstickinWindows.

Before you start


NotethatyoucancreateabootableUSBstickeitherinWindowsorinLinux,butnotin
theOMS.

g Note: UseBinary modewhenyoudownloadthesefiles.Donotuse


Automatic transfer mode.Itcausesfilecorruption.

w NOTICE:CreateabootableUSBstickforeachsoftwarerelease.UsethecorrectUSB
boot.zipfile:FP_USBboot_vX.X.X.zipwhichisdeliveredwithasoftwarereleasein
NOLS.ThedirectorystructuresmaychangeinanewreleaseofOMSsoftwareand
thenifanoldUSBstickisused,USBinstallationfails.

Procedure

1 Download file v2.5.7.zip (or newer) to your computer.


DownloadtheUSBbootzipfile(v2.5.7.zip(ornewer))fromNOLSwithother
softwarefilesthatareneededintheUSBinstallation.

g Note: UseBinary modewhenyoudownloadthefile.Donotuse


Automatic transfer mode.Itwillcausefilecorruption.

2 Connect the USB stick to one of the available USB ports of the PC.

3 Remove U3 launchpad from the device if it exists.

4 Format the stick using FAT32, set the volume name to FPRESCUE.

5 Create folder C:\temp\createusb on your computer.

6 Extract FP_USBboot_<version>.zip into C:\temp\createusb.


Filefiles.zipisdisplayedafteryouhaveextracted
FP_USBboot_<version>.zip.

7 Extract (using folder names) files.zip file.


Thereisfiles.zipfileavailableinC:\temp\createusbfolder.Extractits
contenttoyourUSBstickusingfoldernamesoption.

Issue:01A DN09138239 11

CloningconfigurationdatafromreferenceOMSto CloningRNCOMS
targetOMS

CheckthatsyslinuxdirectoryisnowfoundfromtherootoftheUSBstick.

t Tip: Copyingmaytakealongtime,iftheversionoftheUSBstickortheportonthe
computeryouuseisearlierthan2.0.

8 Install the bootloader.


ChangedirectorytoC:\temp\createusbandrunthefollowingcommandsinthe
commandprompt:
C:\temp\createusb> syslinux -mad syslinux <drive letter
for the USB stick>:
Forexample: C:\temp\createusb> syslinux -mad syslinux F:

Expected outcome
TheUSBstickcontainsthesyslinuxdirectory.

Unexpected outcome
IfUSBstickcreationfailswiththefollowingerror:
Accessing physical drive: Access is denied.
Did not successfully update the MBR; continuing.
OpenC:\temp\createusbfolder.RightclicktheUSB.batfileandchoseRun
as administratorfromthecontextmenu.Aconfirmationwindowwiththefollowing
messageopens:Doyouwanttoallowthefollowingprogramtomakechangesto
thiscomputer?.ClickYes.YouarepromptedfortheUSBstickdriveletter.
Example printout
Enter the Drive Name [Ex: "Z:"]F:

=====================================
USB Boot Image Creation Successful
=====================================
Listing Files under USB
=====================================
Volume in drive F is FPRESCUE
Volume Serial Number is 5234-354A

Directory of F:\

16.02.2011 09:53 DIR syslinux


0 File(s) 0 bytes
1 Dir(s) 7 785 570 304 bytes free
====================
Stopping Batch File
====================
Press any key to continue . . .

Press Enter to finish.

12 DN09138239 Issue:01A

CloningRNCOMS CloningconfigurationdatafromreferenceOMSto
targetOMS

9 Safely remove the USB stick.


SafelyremoveUSBmassstoragedeviceinWindows.

2.3.2 Creating bootable USB stick in Linux


Purpose
FollowthisproceduretocreateabootableUSBstickinLinux.

Before you start


YoucancreateabootableUSBstickeitherinWindowsorinLinux,butnotintheOMS.
DownloadtheFP_USBboot_<version>.zipfilefromNOLS.

g Note: UseBinary modewhenyoudownloadthesefiles.Donotuse


Automatic transfer mode.Itcausesfilecorruption.

w NOTICE:CreateabootableUSBstickforeachsoftwarerelease.UsethecorrectUSB
boot.zipfile:FP_USBboot_vX.X.X.zipwhichisdeliveredwithasoftwarereleasein
NOLS.ThedirectorystructuresmaychangeinanewreleaseofOMSsoftwareand
thenifanoldUSBstickisused,USBinstallationfails.

ThisprocedurehasbeentestedwithRedHatEnterpriseLinux(RHEL)4.

Expected outcome
TheUSBstickcontainsthesyslinuxdirectoryandFAT16filesystem.

Procedure

1 Download the correct the USB boot zip file (FP_USBboot_<version>.zip).


DownloadtheUSBbootzipfile(v2.5.7.zip(ornewer))fromNOLSwithother
softwarefilesthatareneededintheUSBinstallation.

2 Create syslinux directory and unzip the FP_USBboot_<version>.zip file


there.
Thenameofthedirectorymustbesyslinux.
Runthefollowingcommands:
# cd /root/
# mkdir syslinux
# unzip <download_dir>/FP_USBboot_<version>.zip -d \ /root/syslinux/

Issue:01A DN09138239 13

CloningconfigurationdatafromreferenceOMSto CloningRNCOMS
targetOMS

3 Insert the USB stick.


Donotmountthestick.Checkmountswiththefollowingcommand:
# mount

4 Unmount the USB stick if it is automatically mounted.


Runthefollowingcommand:
# umount /media/<usb_stick_volume_label>

5 Check the device name of the USB stick.


CheckthedevicenameoftheUSBstick.Thedevicenamecanbedeterminedfrom
dmesgoutput,forexample:
...
usb 5-4usb 5-4: new high speed USB device using ehci_hcd and address
90
usb 5-4: configuration #1 chosen from 1 choice
scsi89 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 90
usb-storage: waiting for device to settle before scanning
Vendor: SMART Model: Memory Key Rev: 1.03
Type: Direct-Access ANSI SCSI revision: 01
CCS
SCSI device sdd: 2014992 512-byte hdwr sectors (1032 MB)
sdd: Write Protect is off
sdd: Mode Sense: 23 00 00 00
sdd: assuming drive cache: write through
sdd: sdd1
sd 89:0:0:0: Attached scsi removable disk sdd
sd 89:0:0:0: Attached scsi generic sg3 type 0
usb-storage: device scan complete
AppendtheXXXtothe/dev/tocreatethefullnameforthedevice.Inthiscasethe
fullnameforthedevice /dev/sdd.
Thedevicenamecanbefoundinseveralplacesintheoutput.Forexample,fromthe
linecontainingAttached scsi removable disc sdd,wheresddisthe
exampledevicename.

6 Remove all the existing partitions from the USB stick.


Runthefollowingcommand: # fdisk /dev/<device name of the USB
stick>
Forexample:# fdisk /dev/sdd

t Tip: Donotaccidentallyclearawrongdisk.Commandfdiskremovesalldatafrom
theselecteddisk.

14 DN09138239 Issue:01A

CloningRNCOMS CloningconfigurationdatafromreferenceOMSto
targetOMS

PressEnterandusethefollowingfdiskcommandstoremoveallpartitionsfrom
theUSBstick(mprintsmenu):
pprintsthepartitiontable.
ddeletesallpartitionsbyselectingpartitionIDnumberonebyone.
wsaveschangesondiskanquitthefdiskapplication.
Removeallthepartitonsbyselectingthepartitions(partitionIDnumber)onebyone
andrepeatingtheexecutionofcommanddasmuchasneeded.Savechanges.

7 Verify the partitions removal.


Listthepartitiontableusingthefollowingcommand: # fdisk /dev/<device
name of the USB stick>
Forexample:# fdisk /dev/sdd
PressEnterandthenusethepcommandtoprintthepartitiontable(mprintsmenu).

Expected outcome
Nopartitionslisted.TheUSBstickcontainsnopartitions.

8 Go to the /root/syslinux directory you have created.

9 Execute the mkstick.sh script and give the device name.


Executethemkstick.shscriptandgivethedevicenameasaparameter:
# ./mkstick.sh / <device name of the USB stick>
Forexample:# ./mkstick.sh /dev/sdd
Continued operation will completely erase contents of /dev/sdd
Are you sure (y/N)? Y

t Tip: Copyingmaytakealongtime,iftheversionoftheUSBstickortheportonthe
computeryouuseisearlierthan2.0.

2.4 Transferring the clone image and the clone runner


to the bootable USB stick
2.4.1 Transferring the clone image and the clone runner to the
bootable USB stick in Windows
Purpose
FollowthisproceduretotransferthecloneimageandtheclonerunnertotheUSBstick
inWindows.

Issue:01A DN09138239 15

CloningconfigurationdatafromreferenceOMSto CloningRNCOMS
targetOMS

Before you start


NotethatyoucantransferthefilestotheUSBstickeitherinWindowsorinLinux,butnot
intheOMS.
TheprerequisitesforthetransferringtheclonefilestotheUSBstickareasfollows:

TheUSBstickhasbeenpreparedaccordingtotheinstructionsgivenintheprevious
sections.
TheUSBstickdoesnotcontainanyfilesotherthantheUSBbootpart(syslinux
folder).
ThefollowingfilesareavailableforcopyingtothebootableUSB:
thereferenceOMScloneimage:
cloning_<OMS_Id>_rnc_full_<SWRelease>_<date&time>.tar.gz
deliveredeitherasasingle tar.gzfileorseveralparts(.000,.001,)
thereferenceOMScloneimageMD5checksum:
cloning_<OMS_Id>_rnc_full_<SWRelease>_<date&time>.tar.gz.
md5deliveredeitherasasinglemd5fileorseveralparts(.000.md5,.001.md5,
)
clonerunnerscript:
omsswm_clone_restore

w NOTICE:Thisscriptisstoredinthe/opt/Nokia_BP/sbin/directoryonthe
referenceRNCOMS.

g Note: UseBinary modewhenyoudownloadthesefiles.Donotuse


Automatic transfer mode.Itcausesfilecorruption.

TransferthecloningfilestotheUSBstickinWindowsaccordingtothefollowingsteps.

Procedure

1 Copy files to the Windows PC.


CopyallcloningfilesmentionedabovetoWindowsPC,forexampletoC:/temp
directory.

2 Create cloning folder on the USB stick.

Example
mkdir X:\cloningwhereX:istheUSBstickdriveletter.

16 DN09138239 Issue:01A

CloningRNCOMS CloningconfigurationdatafromreferenceOMSto
targetOMS

3 Copy all cloning files to the USB boot stick cloning folder.

t Tip: Copyingmaytakesometime,iftheversionoftheUSBstickortheportonthe
computeryouuseisearlierthan2.0.

4 Verify the contents of the USB stick.


AtthispointthereshouldbetwodirectoriesontheUSBstick:
syslinux
cloning
Thecloningdirectoryshouldcontainthefollowingitems:
thereferenceOMScloneimage:
cloning_<OMS_Id>_rnc_full_<SWRelease>_<date&time>.tar.gz
deliveredeitherasasingle tar.gzfileorseveralparts(.000,.001,)
thereferenceOMScloneimageMD5checksum:
cloning_<OMS_Id>_rnc_full_<SWRelease>_<date&time>.tar.gz.
md5deliveredeitherasasinglemd5fileorseveralparts(.000.md5,.001.md5,
)
clonerunnerscript:
omsswm_clone_restore

w NOTICE: NOTICE:Ifthecloneimagefileissplitintoseveralparts,therearealsoother
MD5checksumfilescreated.TheUSBstickshouldcontainallthechecksumfiles.

5 Remove the USB stick.


UseSafelyRemoveHardwareoptiontoremovetheUSBstick.TheUSBstickis
nowreadyforinstallation.

2.4.2 Transferring the clone image and the clone runner to the
bootable USB stick in Linux
Purpose
FollowthisproceduretotransferthecloneimageandtheclonemakerrunnertotheUSB
stickinLinux.

Before you start


NotethatyoucantransferthefilestotheUSBstickeitherinWindowsorinLinux,butnot
intheOMS.
TheprerequisitesforthetransferringtheclonefilestotheUSBstickareasfollows:

TheUSBstickhasbeenpreparedaccordingtotheinstructionsgivenintheprevious
sections.

Issue:01A DN09138239 17

CloningconfigurationdatafromreferenceOMSto CloningRNCOMS
targetOMS

TheUSBstickdoesnotcontainanyfilesotherthantheUSBbootpart(syslinux
folder).
ThefollowingfilesareavailableforcopyingtothebootableUSB:
thereferenceOMScloneimage:
cloning_<OMS_Id>_rnc_full_<SWRelease>_<date&time>.tar.gz
deliveredeitherasasingle tar.gzfileorseveralparts(.000,.001,)
thereferenceOMScloneimageMD5checksum:
cloning_<OMS_Id>_rnc_full_<SWRelease>_<date&time>.tar.gz.
md5deliveredeitherasasinglemd5fileorseveralparts(.000.md5,.001.md5,
)
clonerunnerscript:
omsswm_clone_restore

w NOTICE:Thisscriptisstoredinthe/opt/Nokia_BP/sbin/directoryonthe
referenceRNCOMS.

g Note: UseBinary modewhenyoudownloadthesefiles.Donotuse


Automatic transfer mode.Itcausesfilecorruption.

TransferthecloningfilestotheUSBstickinLinuxaccordingtothefollowingsteps.

Procedure

1 Copy files to the Linux PC.


CopyallcloningfilesmentionedabovetoLinuxPC,forexampleto/root/oms.

2 Connect the USB stick.


ConnecttheUSBstick.Themountpoint/media/FPRESCUEshouldbevisibleafter
awhile.

3 Check the mount point.


Checkthemountpointsbygivingthefollowingcommand:
# mount
ThedeviceusedisSCSIdevice(/dev/sda1,/dev/sda2,andsoon).

4 Create cloning directory.


Runthefollowingcommand:
# mkdir /media/FPRESCUE/cloning

18 DN09138239 Issue:01A

CloningRNCOMS CloningconfigurationdatafromreferenceOMSto
targetOMS

5 Copy software files to the USB stick cloning directory.


CopythecloningfilestotheUSBstickcloningdirectory.
Forexample:# cp /root/oms/* /media/FPRESCUE/cloning

t Tip: Copyingmaytakesometime,iftheversionoftheUSBstickortheportonthe
computeryouuseisearlierthan2.0.

6 Verify the contents of the USB stick.


AtthispointthereshouldbetwodirectoriesontheUSBstick:
syslinux
cloning
Thecloningdirectoryshouldcontainthefollowingitems:
thereferenceOMScloneimage:
cloning_<OMS_Id>_rnc_full_<SWRelease>_<date&time>.tar.gz
deliveredeitherasasingle tar.gzfileorseveralparts(.000,.001,)
thereferenceOMScloneimageMD5checksum:
cloning_<OMS_Id>_rnc_full_<SWRelease>_<date&time>.tar.gz.
md5deliveredeitherasasinglemd5fileorseveralparts(.000.md5,.001.md5,
)
clonerunnerscript:
omsswm_clone_restore

w NOTICE: NOTICE:Ifthecloneimagefileissplitintoseveralparts,therearealsoother
MD5checksumfilescreated.TheUSBstickshouldcontainallthechecksumfiles.

7 Flush data from memory onto USB stick.


Enterthefollowingcommand:
# sync

t Tip: Executionofthiscommandmaytakeafewminutes.

8 Unmount the USB stick.


Ifyouneedtogivetheunmountcommand,changedirectoryfrom
/media/FPRESCUEbeforegivingthefollowingcommand:
# umount /media/FPRESCUE

9 Remove the USB stick.


RemovetheUSBstick.Itisnowreadyforcloning.

Issue:01A DN09138239 19

CloningconfigurationdatafromreferenceOMSto CloningRNCOMS
targetOMS

2.5 Restoring cloning image on target OMS


Purpose
Restoringthecloningimageisperformedintwostepsusingthesamerestorescript
(omsswm_clone_restore):

restoringthecloningimageafterbootingthetargetmachinefromtheUSB
restoringthecloningimagefinalizationafterthetargetisbootedfromthedisk

FollowthisproceduretocommissionthetargetOMSfromthebootableUSBstickand
performrestoringthecloningimage.

Before you start


Theprerequisitesfortherestoringareasfollows:

TheUSBstickhasbeenpreparedaccordingtotheinstructionsgivenintheprevious
sections.
TheUSBstickdoesnotcontainanyfilesotherthantheUSBbootpart(syslinux
folder)andcloningfiles(cloningfolder).
NoticethatduringUSBcommissioningOMShardwareclockmustbesetto
UTC/GMTtime(UnitedKingdomstime).
DisconnectallotherUSBdevices(forexampleopticaldrivesorotherUSBsticks)
fromtheOMSastheymaycausedevicenamesconflictsresultingininstallation
failure.

NotethatthefollowinglogiswrittentoUSBstick:
/cloning/omsswm_clone_restore_<yyyymmdd_hhmmss>.log

t Tip: Iftheoperationisexecutedremotely,considerusingthescreentool.Seesection
Emulatingterminalwiththescreencommand.

Procedure

1 Boot up the target OMS.


TobootuptheOMS,executethefollowingtasksintheordertheyarelisted:
a) ConnectVGAmonitor,keyboardandtheUSBbootsticktothec-ClassSUV
Cable.
b) ResettheOMSnodebypressingthePower Onbuttoninthefrontpanelofthe
bladeorrackmounthardware.
c) Whenprompted,pressF9ontheexternalkeyboardtoenterBIOSsetup.
d) Select"TimeandDate",andadjustBIOSclocktoUTC/GMTtime(United
Kingdom'stime).
e) ChangebootdevicetotheUSBstick.
ChooseStandard Boot Order (IPL)optionfromthemenu.MovetheUSB
DriveKeyitemtothefistpositiononthelisttochangebootorder.
f) ConnecttheUSBsticktothetargetOMS.

20 DN09138239 Issue:01A

CloningRNCOMS CloningconfigurationdatafromreferenceOMSto
targetOMS

g) ExitBIOS(pressF10).
h) Tochoosecorrectselectionfromthelist,enterthefollowingtext:
fp4_hprm(forHPProLiantRackhardware)
fp4_hpbs(forHPProLiantBladehardware)
i) Logintotheprebootsystemasrootuser(nopasswordneeded).
j) VerifytimewithdatecommandafterOMSfirstboot:
# date

#Wed Jun 12 11:56:46 UTC 2013


Timeshouldbecorrect(UTC/GMT).
k) WaitforthetargetOMStobootfromtheexternalUSBbootdevice.

2 Check the device name of the USB stick.


CheckthedevicenameoftheUSBstick.Thedevicenamecanbedeterminedfrom
dmesgoutput,forexample:
...
usb 5-4usb 5-4: new high speed USB device using ehci_hcd and address
90
usb 5-4: configuration #1 chosen from 1 choice
scsi89 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 90
usb-storage: waiting for device to settle before scanning
Vendor: SMART Model: Memory Key Rev: 1.03
Type: Direct-Access ANSI SCSI revision: 01
CCS
SCSI device sdd: 2014992 512-byte hdwr sectors (1032 MB)
sdd: Write Protect is off
sdd: Mode Sense: 23 00 00 00
sdd: assuming drive cache: write through
sdd: sdd1
sd 89:0:0:0: Attached scsi removable disk sdd
sd 89:0:0:0: Attached scsi generic sg3 type 0
usb-storage: device scan complete
AppendtheXXXto/dev/tocreatethefullnameforthedevice.Inthiscasethefull
nameforthedevicenameis /dev/sdd.
Thedevicenamecanbefoundfromseveralplacesintheoutput.Forexample,from
thelinecontainingAttachedscsiremovablediscsdd,wheresddistheexample
devicename.

3 Mount the USB stick, copy the cloning script.


SubstitutexxxwiththedevicenamefoundinstepCheckthedevicenameofthe
USBstick..Noticethepartitionnumber(1)afterthedevicename.Forexample,if
theUSBstickdevicenamefoundinstepCheckthedevicenameoftheUSBstick.is
/dev/sdd,thecompleteparameterpassedtomountcommandis/dev/sdd1.
# mkdir -p /mnt/usb
# mount /dev/xxx1 /mnt/usb
# cp /mnt/usb/cloning/omsswm_clone_restore /tmp/

Issue:01A DN09138239 21

CloningconfigurationdatafromreferenceOMSto CloningRNCOMS
targetOMS

# cd /tmp
# dos2unix omsswm_clone_restore
# chmod 744 omsswm_clone_restore

Unexpected outcome
Ifthemountingfails,doublecheckthedevicename:
less /var/log/dmesg
Ifthedevicenameiscorrect,removetheusb-storagemodule:
modprobe -r usb-storage
Waitacoupleofseconds,thenreloadthemoduleandmounttheUSBstickagain:
modprobe usb-storage
mount /dev/xxx1 /mnt/usb
Substitutexxxwiththecorrectdevicename.

4 Start the cloning script.


Startthecloningscriptbyrunningthefollowingcommand:
./omsswm_clone_restore\
/mnt/usb/cloning/cloning_<OMS_Id>_rnc_full_<SWRelease>_<date&time>.ta
r.gz

g Note: Ifthecloningimageissplit,runthefollowingcommandgivingallimagepartsas
parameters:
./omsswm_clone_restore\
/mnt/usb/cloning/cloning_<OMS_Id>_rnc_full_<SWRelease>_<date&time>.tar.
gz.000\
/mnt/usb/cloning/cloning_<OMS_Id>_rnc_full_<SWRelease>_<date&time>.tar.
gz.001

Afteryouhavegiventhecommand,thefollowingtextappearsonthescreen:
=== CLONING IMAGE RESTORE STARTED ===
Verifying cloning image...
NowwaituntilthescriptfinishesandaskstoremoveUSBstickandbootOMS.
Continuewithnextstep.

5 Remove the USB stick.


Followtheinstructionswhenthecloningscripthasbeencompleted:
__________
Remove USB stick
After reboot, change BIOS boot order to boot from hard drive and save
settings
To complete cloning please run this script again after target startup
RemovetheUSBstickfirstandthentypeytoreboottheOMS.

t Tip: IfyouuseiLOconsoleinsteadofKVM,OMSmayrebootautomaticallydepending
onHPiLOfirmwareversion.

22 DN09138239 Issue:01A

CloningRNCOMS CloningconfigurationdatafromreferenceOMSto
targetOMS

6 Change the boot order back to the hard drive.


ToreboottheOMSfromtheharddrive,executethefollowing:
a) Whenprompted,pressF9ontheexternalkeyboardtoenterBIOSsetup.
b) Changethebootorderbackbymovingtheharddrivetohighestpositiononthe
listthatmakesittheprimarybootdevice.Checkthatthebootorderiscorrect,the
harddriveishighestonthelistandenabled(noexclamationmarkinfrontofit).
Makecorrectionsifneeded.
c) SavethesettingandexitBIOS.
d) WaitfortheOMStoboot.

7 Log in to the target OMS as a root.

8 Run omsswm_clone_restore script.


Tostartrestoringofthecloningimage,runthefollowingcommand:
# ./omsswm_clone_restore
Afterthisstepyouarepromptedtoenterthenecessaryparameters.

g Note: Alloftherequesteddataismandatory.Donotleaveemptyvalues.Forexample,
IPmustbeinx.x.x.xformat.IfthereisnoexternalNTPorDNSserverinthenetwork,
giveafreeIPaddress.Allaskedvaluesmustbegiven.

t Tip: TherearetwopossibleIPdeploymenttypes:singleIPaddressforallOMS
servicesandseparateIPaddressesfornorthboundandsouthboundservices.Youare
askedtochoosetheIPdeploymenttypeduringthenetworkconfiguration.

Youareaskedtoenterthefollowingparameters:
OMSIPdeploymenttype(singleIPaddressornorthbound/southbound
approach)
OMSIPaddressorOMSnorthboundandsouthboundIPaddresses(depending
ondeploymenttype)
networkconfguration:netmask,externalDNSserverIP,externalNTPserverIP,
defaultgateway
omsFtpUser password
OMSclusterID
timezone
passwordsforaccountsroot,_nokfsoperator,and
_nokfssysemoperatorfallback

9 Configure the network addressing settings.

a) Whenyouareprompted,configurethesettings:
GOMS IP (northbound):
GOMS IP (southbound):
NETMASK: (in bits e.g. 24)

Issue:01A DN09138239 23

CloningconfigurationdatafromreferenceOMSto CloningRNCOMS
targetOMS

DNS IP:
NTP IP:
DEFAULT GATEWAY:
b) Youarepromptedtocheckwhetherthesettingsarecorrect.Ifthesettingsare
incorrect,thecommissioningfails.Modifythesettingsifneeded,andthenenter
yes.
Example
Parameters
GOMS IP (northbound): 10.8.122.162
GOMS IP (southbound): 10.8.122.163
NETMASK: /25
DNS IP: 10.8.122.67
NTP IP: 10.8.122.67
DEFAULT GATEWAY: 10.8.122.129

10 Set the omsFtpUser password


YouareaskedifyouwanttochangetheomsFtpUserpassword.Afterentering
Yes,youareabletochangethepassword.

11 Enter OMS cluster id.


Give new OMS id number <1-65535>:

12 Identify the location so that time zone rules can be set correctly.
Please identify a location so that time zone rules can be set
correctly.
Please select a continent or ocean.
1) Africa
2) Americas
3) Antarctica
4) Arctic Ocean
5) Asia
6) Atlantic Ocean
7) Australia
8) Europe
9) Indian Ocean
10) Pacific Ocean
11) none - I want to specify the time zone using the Posix TZ format.
#? 8
Please select a country.

1) Aaland Islands 18) Greece 35) Norway

2) Albania 19) Guernsey 36) Poland

3) Andorra 20) Hungary 37) Portugal

24 DN09138239 Issue:01A

CloningRNCOMS CloningconfigurationdatafromreferenceOMSto
targetOMS

4) Austria 21) Ireland 38) Romania

5) Belarus 22) Isle of Man 39) Russia

6) Belgium 23) Italy 40) San Marino

7) Bosnia & 24) Jersey 41) Serbia


Herzegovina

8) Britain (UK) 25) Latvia 42) Slovakia

9) Bulgaria 26) Liechtenstein 43) Slovenia

10) Croatia 27) Lithuania 44) Spain

11) Czech Republic 28) Luxembourg 45) Sweden

12) Denmark 29) Macedonia 46) Switzerland

13) Estonia 30) Malta 47) Turkey

14) Finland 31) Moldova 48) Ukraine

15) France 32) Monaco 49) Vatican City

16) Germany 33) Montenegro

17) Gibraltar 34) Netherlands

13 Confirm the timezone settings.


Anexampleoftheoutput:
The following information has been given:

Finland

Therefore TZ='Europe/Helsinki' will be used.


Local time is now: Tue Jan 13 16:32:08 EET 2009.
Universal Time is now: Tue Jan 13 14:32:08 UTC 2009.
Is the above information OK?
1) Yes
2) No
#?1

14 Enter and verify passwords.


Enterandverifypasswordsforroot,_nokfsoperator,and
_nokfssysemoperatorfallback.
Passwordsdefinedinthisstepcanberequestedinfurtherloggingoperations.

g Note: Agreethepasswordswithyoursystemadministrator.

Change root password


Changing password for user root.
New user password:

Issue:01A DN09138239 25

CloningconfigurationdatafromreferenceOMSto CloningRNCOMS
targetOMS

Retype new user password:


passwd: all authentication tokens updated successfully.
Change _nokfsoperator password
Changing password for user _nokfsoperator.
New user password:
Retype new user password:
passwd: all authentication tokens updated successfully.
Change _nokfssysemoperatorfallback password
Changing password for user _nokfssysemoperatorfallback.
New user password:
Retype new user password:
passwd: all authentication tokens updated successfully.
AfterthisstepyouareaskedtoreboottheOMS.AnswerYestoreboot.

Expected outcome
TheOMScloningiscompleted.

26 DN09138239 Issue:01A

CloningRNCOMS IntegratingRNCOMStoNetAct

3 Integrating RNC OMS to NetAct

3.1 Introduction to integrating RNC OMS to NetAct


TheRNCOMSneedstobeintegratedtoNetActbeforeittakesoverthemanagement
rolefromtheintegratedRNCOMS.Theprocedureconsistsofstepsaspresentedin
Figure1:ProcedureofRNCOMSintegrationtoNetAct.

Figure 1 ProcedureofRNCOMSintegrationtoNetAct

Start

ConfiguretheOMS
Reviewthesystem
requirements

Addmanaged ConfigureOMS
objectstotheDNS forO&Mconnection

ChecktheMR End
serviceusers

Createmanaged
objects

Taskisdonein:
OMS
NetAct

SeeIntegrating Operations and Management Server (OMS) to NetActintheOSS


documentationlibraryinNOLSfordetailsontheintegratingpartofprocedure.

3.2 Configuring NetAct interface with OMS


Purpose

g Note: ExecutethisprocedurebeforeCentralizedUserAuthenticationandAuthorization
configuration.

ThisprocedureinstructsyoutoconfiguretheconnectionfromOMStoNetAct.

Issue:01A DN09138239 27

IntegratingRNCOMStoNetAct CloningRNCOMS

Procedure

1 Open the Parameter tool using the Application Launcher.

2 Select entry to default instances of:

fsClusterId=ClusterRoot
fsFragmentId=NWI3
fsFragmentId=mediator
fsnwi3N3CFId=1
Theninitializetheattributesbelow.

3 Edit the required attributes and their values:

NetActRegistrationServiceIOR(RSIOR)fsnwi3registrationServiceIORfield
NetActRegistrationServiceusernamefsnwi3initialRegistrationUsernamefield
(Thedefaultusernameisneregn,butitshouldbechangedforsecurity
reasons.)
NetActRegistrationServicepasswordfsnwi3initialRegistrationPasswordfield
(Thedefaultpasswordisneregn,butitshouldbechangedforsecurity
reasons.)
Changethevalueofthebooleanparameter
fsnwi3takeIntoUseNext=true,whichmeansthatthisconfiguration
parametersetistakenintouseduringthenext(re)startorre-registration.

4 Take the new parameter values into use.


NWI3Adaptertakesthenewparametervaluesintousewithinare-registration
periodandregistersitselftoNetAct(thedefaultre-registrationis60minutes).There-
registrationdependsonthesituationandtheparametersintheLDAPserver.The
newparameterscanbetakenintouseimmediatelybyrestartingtheNWI3Adapter
recoverygroup.UseSSHconnectiontotheOMSandrestarttherecoverygroupby
enteringthefollowingcommand:
fshascli r /NWI3Adapter
NotethatthecommandcanbeexecutedasrootorNemuadmin.

Further information
Formoreinformation,seeRegistration of the NWI3 Adapter to NetAct failsin
Troubleshooting OMS.

5 Check the status of OMS services.


Checkthestatusbyenteringthefollowingcommand:
# zstatus -d

Expected outcome
Monitoring cluster

28 DN09138239 Issue:01A

CloningRNCOMS IntegratingRNCOMStoNetAct

CLA-0 R_GOMS6_1.103.1.0.release_oms.corr33
RecoveryGroups(@OMS, disabled):
RecoveryUnits(@/, disabled):
Processes(@/, disabled):
Monitoring cluster FINISHED

Issue:01A DN09138239 29

ConnectingRNCOMStoRNC CloningRNCOMS

4 Connecting RNC OMS to RNC


Purpose
ThisprocedureconnectstheRNCOMStoRNCbychangingtheIPconfiguration.

Before you start


TheOMSsouthboundIPaddressischangedontheRNClevelaftertheRN7.0package
hasbeeninstalled.ThechangeconcernsmodificationoftheRNC->OMSIpAddress
parameterandcanbedoneusingthefollowingtools:

NetActCMtool
OMSParameterEditor
RUOSTEserviceterminallikedescribedinthisprocedure
ThemacroasksfortheOMSIPaddressduringtheRNCupgradeandconfiguresit
automatically.

Procedure

1 Start a service terminal session with a DDS command.


Executethefollowingcommand:
ZDDS:OMU,<active omu>;

2 Remove the service terminal extension.


Executethefollowingcommand:
0000-MAN>ZL:1;

3 Load the RUOSTEQX service terminal extension.


Executethefollowingcommand:
0000-MAN>ZLE:1,RUOSTEQX;

4 Modify the IP address for the RNC O&M connection.

w NOTICE:SetthesameIPaddressasduringtheRNCOMSinstallationprocess.

Followthesteps:
a) Ifyoucreatethesouthboundaddressforthefirsttime,usetheCRcommand.
0000-MAN>Z1CR:<RNC_ID>,<OMS southbound IP address >, <RNC_name>;
Otherwise,changetheIPaddressfortheRNCO&MconnectionwiththeCI
command:
0000-MAN>Z1CI:<OMS southbound IP address>;
Connecting to RNW database...

RNC object data in RNW database:

30 DN09138239 Issue:01A

CloningRNCOMS ConnectingRNCOMStoRNC

-------------------------------------
RNC ID: xxx
RNC name: xxx
Primary OMS IP address: xx.xx.xx.xx
Secondary OMS IP address: xx.xx.xx.xx
Backup OMS IP address: xx.xx.xx.xx
Current serving OMS: 2 (secondary OMS)
Serving OMS selection: 0 (automatic)
Connection retry count: 10
-------------------------------------
Changing primary OMS IP address to: xx.xx.xx.xx

Request sent, waiting for acknowledgement...


Operation successfully completed.

Closing RNW database connection...


b) Closetheserviceterminalsessionbyexecutingthefollowingcommand:
0000-RUO>ZZE;

w NOTICE:IfBTSsareusingOMSIPaddressasanNTPIPaddress,andtheOMSIPis
changed,updatetheBTSsNTPIPaddressesrespectively.

5 Check the RNC O&M connection.


Executethefollowingcommand:
ZQRS:OMU,<active OMU index>;
ThecorrectstateisESTABLISHED.
Ifthestateisincorrect,dothefollowing:
a) Setdateandtime.
ZDCS:<date>,<time>:ST=<summer time identification>;
b) Setthetimezone.
ZDCE:<sign of time difference>:<time difference>;
c) SettheNTPserverIPaddress.
ZDCM:4,<NTP server IP address>;

Result

TheRNCOMSisreadytotakeovertheoperationandmanagementrole.
AftertheRNCOMSconnectiontoRNCisestablished,theRNCOMSautomatically
performstheuploadofmeasurementplantoRNC.Next,theRNWmeasurementsstart
automatically.

Issue:01A DN09138239 31

VerifyingRNCOMSwithnewconfigurationdata CloningRNCOMS

5 Verifying RNC OMS with new configuration


data
Purpose
FollowthisproceduretocheckwhethertheRNCOMSisreadytobeused.

Procedure

1 Log in to the RNC OMS with SSH as Nemuadmin.

2 Log in to the OMS as root with the su - command.

3 Check the completeness of the cloning procedure.


Executethefollowingcommandtochecktheversionofthecurrentsoftwareset:
Executethefollowingcommandtomonitortheclusterstatus:
# zstatus -d
Monitoring cluster
CLA-0 R_GOMS6_1..1.0.release_oms.corr20

RecoveryGroups(@OMS, disabled):

RecoveryUnits(@/, disabled):

Processes(@/, disabled):

Monitoring cluster FINISHED


Theexampleprintoutshowsthecloningprocedureiscompletedsuccessfully.

w NOTICE:Thecloningprocedurefailswhenthefollowingmessageappearsonthe
screen:
/MeaHandler (disabled)
/PMGeneric (disabled)

4 Check the OMS connectivity to OMU.


PingtheRNCOMUaddresstoensurethattheconnectionisestablished.Execute
thefollowingcommand:
# ping <RNC OMU address>

5 Check that all necessary firewall ports are opened between the RNC and the
RNC OMS.
Formoredetailsonthelistofrequiredports,seeWCDMA Communication Matrixin
NOLSunderReference -> Securitycategory.

32 DN09138239 Issue:01A

CloningRNCOMS VerifyingRNCOMSwithnewconfigurationdata

6 Check that the RNC topology is fully uploaded.


UsetheOMSElementManagerWebUItocheckwhethertheRNCtopologyisfully
uploaded.
Ifthereareproblemswithtopologyview,reloadthetopologybyexecutingthe
followingcommand:
# /opt/Nokia/SS_Affe/script/oms_reinstall_topology_db.sh

Result

TheRNCOMSisreadytobeused.

Issue:01A DN09138239 33

Appendix CloningRNCOMS

6 Appendix

6.1 Logging in to OMS


Purpose
FollowthisproceduretologintotheOMS.Forinstructionsonremotelogging,seeLog
intotheOMSremotely.Forinstructionsonlogginginlocally,seeLogintotheOMS
locally.

Log in to the OMS remotely


Follow the steps below for remote logging in to the OMS.

Purpose
Remotelogginginfortherootaccountisdisabledforsecurityreasons.Toobtainthe
rootprivileges,login,forexample,asthe_nokfsoperatorortheNemuadminuser
firstandthenswitchtotherootuserusingthesu -commandasinstructedbelow.

Procedure

1 Logging in to OMS remotely with SSH client.


Sub-steps

a) Open the SSH client.

b) Fill in the relevant fields.


Fillintherelevantfields,includingtheOMShostnameoranIPaddress(and
port22)andtriggertheconnection.

c) At the login prompt, enter the user credentials (for example, Nemuadmin).

d) Enter the user password.


TheremoteconnectiontotheOMSisopened.

e) For administering the OMS, change to the root user.


Enterthefollowingcommand:
su -

t Tip: Usethesu -command,notthesucommand.

34 DN09138239 Issue:01A

CloningRNCOMS Appendix

f) Enter the password for the root user.

2 Logging in to OMS using a terminal.


Sub-steps

a) Enter the following command:


ssh <username>@<OMS_hostname_IP>

b) Confirm the host key authenticity if needed.


IfthePuTTY Security Alertwindowappears,confirmthehostkeyauthenticity
bypressingtheYesbutton.

c) Enter the password for the <username>.


TheremoteconnectiontotheOMSisopened.

d) For administering the OMS, change to the root user.


Enterthefollowingcommand:
su -

t Tip: Usethesu -command,notthesucommand.

e) Enter the password for the root user.

6.2 Emulating terminal with the screen command


Summary
screenisaterminalemulatorthatallowsmultiplexingaphysicalterminalbetween
severalsimultaneousprocesses.ItmakesremoteOMSmanagementdowntime-proof
andthusmorestablebecausethealreadystartedprocesscontinuesindependentlyof
theSSHconnectionavailability.
Formoredetails,seethescreenmanualpagesinCommand Line Interface Tools and
Management Scripts in OMS.

Purpose
Securingtime-consumingandcriticalprocesseslikeOMSbackup,restore,incremental
softwaredeliveriesinstallation,ormajorsoftwareupgradefromnetworkproblems.

Issue:01A DN09138239 35

Appendix CloningRNCOMS

Before you start


Ensurethatyouhaverootaccessrights.

Steps

1 Run the tool.


Torunthescreentool,executethecommand:
screen -LS [screenName]
where[screenName]isthenameyougivetothecurrentterminaltofacilitate
terminalsmanagementinthefuture.
The-Lparameterturnsontheautomaticlogcollection.Asaresult,the
screenlog.nlogfileissavedinthecurrentdirectory,wherenisthewindow
number(startingfrom0).Toviewit,executethecommand:
more screenlog.n
Notethatthefilemaycontainlogsalsofrompreviousscreensessions.

2 Verify if screen is running.


Tocheckifthetoolhasstartedworking,enterthecommand:
screen -ls
AssumingthesessionnamewassettoOMSbackup,theexampleoutputis:
There is a screen on:
2269.OMSbackup (01/08/2013 03:40:03 PM)
(Attached)
1 Socket in /var/run/screen/S-root.

3 Start the OMS management process.


Enterthecommandasinaregularterminal.

Expected outcome
TheSSHconnectionwasnotbroken.Theprocessendedsuccessfully.

Unexpected outcome
TheSSHconnectionwaslostbeforetheprocessendedsuccessfully.Reattachthe
existingsessionusingthecommand:
screen r [screenName]
where[screenName]isthenameyouprovidedtotheterminalemulatorinStep1.
Waitfortheprocesstoendandthenexitthesession.

4 Exit the terminal.


Exitthescreenterminalusingthecommand:
exit

36 DN09138239 Issue:01A

CloningRNCOMS Appendix

Youshouldgetthefollowingoutput:
[screen is terminating]

w NOTICE: Itisrecommendedtoexitallinactiveterminals.Thelistofallrunning
terminalscanberetrievedbyenteringthescreen -lscommand.Toreattachan
alreadystartedterminal,executethescreen -r [screenName]command.

Issue:01A DN09138239 37