Professional Documents
Culture Documents
Commissioning FZC
Commissioning FZC
CommissioningFlexiZoneController
The information in this document applies solely to the hardware/software product (Product) specified
herein,andonlyasspecifiedherein.ReferencetoNokialaterinthisdocumentshallmeantherespective
companywithinNokiaGroupofCompanieswithwhomyouhaveenteredintotheAgreement(asdefined
below).
ThisdocumentisintendedforusebyNokia'scustomers(You)only,anditmaynotbeusedexceptforthe
purposes defined in the agreement between You and Nokia (Agreement) under which this document is
distributed.Nopartofthisdocumentmaybeused,copied,reproduced,modifiedortransmittedinanyform
or means without the prior written permission of Nokia. If You have not entered into an Agreement
applicabletotheProduct,orifthatAgreementhasexpiredorhasbeenterminated,Youmaynotusethis
documentinanymannerandYouareobligedtoreturnittoNokiaanddestroyordeleteanycopiesthereof.
The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia welcomes your comments as part of the process of
continuousdevelopmentandimprovementofthedocumentation.
This document and its contents are provided as a convenience to You. Any information or statements
concerningthesuitability,capacity,fitnessforpurposeorperformanceoftheProductaregivensolelyon
an as is and as available basis in this document, and Nokia reserves the right to change any such
information and statements without notice. Nokia has made all reasonable efforts to ensure that the
content of this document is adequate and free of material errors and omissions, and Nokia will correct
errors that You identify in this document. Nokia's total liability for any errors in the document is strictly
limitedtothecorrectionofsucherror(s).NokiadoesnotwarrantthattheuseofthesoftwareintheProduct
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 BE LIABLE FOR ANY DAMAGES,
INCLUDINGBUTNOTLIMITEDTOSPECIAL,DIRECT,INDIRECT,INCIDENTALORCONSEQUENTIAL
OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS
DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS
FROMTHISDOCUMENTORITSCONTENT.
ThisdocumentisNokiaproprietaryandconfidentialinformation,whichmaynotbedistributedordisclosed
toanythirdpartieswithoutthepriorwrittenconsentofNokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
maybetrademarksoftheirrespectiveowners.
Copyright2016Nokia.Allrightsreserved.
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.
Nokiaiscontinuallystrivingtoreducetheadverseenvironmentaleffectsofitsproductsandservices.We
would like to encourage you as our customers and users to join us in working towards a cleaner, safer
environment.Pleaserecycleproductpackagingandfollowtherecommendationsforpoweruseandproper
disposalofourproductsandtheircomponents.
IfyoushouldhavequestionsregardingourEnvironmentalPolicyoranyoftheenvironmentalserviceswe
offer,pleasecontactusatNokiaforanyadditionalinformation.
2 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController
Table of Contents
Thisdocumenthas187pages
Summaryofchanges..................................................................... 9
1 IntroductiontoFlexiZoneControllercommissioning....................11
1.1 FlexiZoneControllercommissioningworkflow............................ 11
2 CommissioningFlexiZoneControllerthroughSCLI/FEWS.......14
2.1 SettingupaFieldEngineeringWorkstation................................. 14
2.1.1 FEWSHardwareRequirements...................................................14
2.1.2 Loggingintofieldengineeringworkstation................................... 14
2.1.3 ConfiguringFEWSservices......................................................... 15
2.2 Configuringafactorypre-commissionedFZC..............................17
2.2.1 Introductiontoconfiguringafactory-commissionedcontroller..... 17
2.2.1.1 Configurationpreconditions......................................................... 18
2.2.1.2 Configurationoverview.................................................................19
2.2.2 VerifyingHWinstallation.............................................................. 19
2.2.3 Verifyingfactorysettings.............................................................. 21
2.2.3.1 ConnectingFEWStothecontroller..............................................21
2.2.3.2 Checkingfactorysettings............................................................. 22
2.2.4 VerifyingtheFlexiZoneControllerIDformat............................... 22
2.2.5 Verifyingfactorycommissioning...................................................23
2.3 FlexiZoneControllerIPconfiguration..........................................24
2.3.1 EthernetInterfacesonFlexiZoneController............................... 24
2.3.1.1 ConfirmingthattheEthernetInterfacesonFlexiZoneController
areconfiguredcorrectly................................................................25
2.3.2 ChanginginterfaceIPaddressesinthecontroller....................... 25
2.3.3 SettinguptheZ1Interface...........................................................26
2.3.4 SettingupFlexiZoneControllernorthboundinterfaces...............27
2.3.4.1 SettinguptheFZCU-planeinterface...........................................28
2.3.4.2 SettinguptheFZCM-planeinterface.......................................... 28
2.3.4.3 SettinguptheFZCC-planeinterface...........................................29
2.3.5 FlexiZoneControllerintegratedDHCPserver.............................30
2.3.5.1 AddingDHCPServerStaticMACtoIPassignment.................... 30
2.3.5.2 ConfiguringDHCPserverforadditionalenterprises.................... 32
2.3.6 SettingupaCMPServerIPfortheFlexiZoneController........... 34
2.3.6.1 MigratingaFlexiZoneControllertoacustomerprovidedPKI.....34
2.3.6.2 ModifyingthecustomerprovidedPKIofaFlexiZoneController.....
36
2.3.6.3 BackingoutfromacustomerprovidedPKItoaninternalPKIina
FlexiZoneController....................................................................38
2.3.7 ManagingcertificatesontheFlexiZoneController......................38
2.3.7.1 UpdatinginternalCAcertificates..................................................38
2.3.7.2 CheckingcertificatesexpirationinNE3S/WS.............................. 39
2.3.7.3 CertificateexpirationalarmhandlinginNE3S..............................41
DN09210645Issue:01C 2016Nokia 3
CommissioningFlexiZoneController
2.3.8 ManagingIPSecpoliciesintheFlexiZoneController..................44
2.3.8.1 ActivatingandconfiguringLTE2017:IPSecSupportforFlexiZone
Controller......................................................................................45
2.3.8.2 DeactivatingLTE2017:IPSecSupportforFlexiZoneController.....
49
2.3.9 ConfiguringstaticroutesforIPv4................................................. 51
2.3.10 ConfiguringNTP...........................................................................56
2.3.11 ConfiguringDNS.......................................................................... 58
2.3.12 SettinguptheprimaryLDAPserver&RUIMserviceonaFlexi
ZoneController............................................................................ 61
2.4 ManagingFZCphysicalmanagementport.................................. 65
3 IntegratingFlexiZoneControllertoNetActthroughtheNES3link..
66
4 CommissioningFlexiZoneControllerthroughBTSSiteManager...
67
4.1 AboutBTSSiteManager............................................................. 67
4.1.1 InstallingBTSSiteManager.........................................................67
4.1.2 LaunchingBTSSiteManager...................................................... 69
4.1.3 UpdatingBTSsitesoftware..........................................................71
4.1.4 MonitoringautoconnectioninBTSSiteManager.........................73
4.2 IntroductiontoZoneBTSsitecommissioning..............................75
4.2.1 Startingmanualcommissioning................................................... 79
4.2.2 Creatingcommissioningfile......................................................... 80
4.2.3 Performingtemplatecommissioning............................................ 81
4.2.4 Performingplannedcommissioning............................................. 82
4.2.5 Performingreconfigurationcommissioning.................................. 83
4.2.6 BTSSiteManagerCommissioningWizard.................................. 84
4.2.6.1 Commissioning-Introduction.......................................................84
4.2.6.2 CreateCommissioningFile-Introduction.................................... 85
4.2.6.3 CreateCommissioningFile-HWSelection................................. 86
4.2.6.4 Commissioning-HWSelection....................................................87
4.2.6.5 Commissioning-BTSSettings.................................................... 89
4.2.6.6 Commissioning-PassiveUnits....................................................90
4.2.6.7 Commissioning-BTSSynchronizationSettings..........................91
4.2.6.8 Commissioning-CellResources................................................. 91
4.2.6.9 Commissioning-LTECarriers..................................................... 92
4.2.6.10 Commissioning-AntennaLineSettings...................................... 95
4.2.6.11 Commissioning-RadioNetworkConfiguration........................... 96
4.2.6.11.1 SettingZoneeNBAPMODParameterswithBTSSM.................. 98
4.2.6.11.2 ConfiguringFZAPEthernetsettingswithBTSSM......................100
4.2.6.11.3 ConfiguringZoneandAPBluetoothSettingswithBTSSM........101
4.2.6.11.4 ConfiguringZoneandAPQOSSettingswithBTSSM............... 104
4.2.6.11.5 ConfiguringAPTimingOverPacketSettingswithBTSSM........107
4.2.6.12 Commissioning-SendParameters........................................... 109
4.2.6.13 Commissioning-AdditionalSiteSettings...................................110
4 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController
4.2.6.14 Commissioning-ViewParameters.............................................111
4.2.6.15 Commissioning-ViewFileChanges.......................................... 111
4.2.6.16 Commissioning-CommissioningReport....................................111
4.2.6.17 CreateCommissioningFile-Summary......................................112
5 IntegratingFlexiZoneControllertoNetActthroughtheNWI3link..
114
6 IntegratingFlexiZoneAccessPointstotheFlexiZoneController..
115
6.1 IntegratingaFlexiZoneMicrototheFlexiZoneControllerusing
BTSSM....................................................................................... 116
6.1.1 IntroducingtheFlexiZoneMicroAutoconnectionSiteIDin
BTSSM....................................................................................... 117
6.1.2 CheckingtheFlexiZoneMicroAutoconfigurationprogressin
BTSSM....................................................................................... 117
6.1.2.1 UncommissioningaFlexiZoneMicrotoallowFZAP
AutoconfigurationinBTSSM...................................................... 118
6.2 IntegratingaFlexiZoneMicrototheFlexiZoneControllerusing
WebUI........................................................................................ 121
6.2.1 IntroducingtheFlexiZoneMicroAutoconnectionSiteIDinWebUI
................................................................................................... 121
6.2.2 CheckingtheFlexiZoneMicroAutoConnection&Configuration
progressinWebUI......................................................................121
6.2.2.1 UncommissioningaFlexiZoneMicrotoallowFZAPAuto
Connection&ConfigurationinWebUI........................................122
6.3 VerifyingIPSectunnelinginFlexiZoneController..................... 123
7 AdditionalproceduresforFZCcommissioning.......................... 125
7.1 SystemrestorationinFZC......................................................... 125
7.1.1 Introductiontorestoringthesystem........................................... 125
7.1.2 PreparingbackupISO................................................................125
7.1.2.1 Overviewofbackupandrestore................................................ 126
7.1.2.2 Makinganactivesoftwarebackup............................................. 126
7.1.2.3 Transferringthebackuparchivefiletoanexternalstorageserver..
128
7.1.3 PreparingbackupSWdeliveryontheFEWS............................ 130
7.1.3.1 Extractingthebackupsoftware.ISOimagetoadeliveryfolder.130
7.1.3.2 Creatingsession-specificfilesforsystemrestore...................... 132
7.1.4 Creatingrestoresession............................................................ 134
7.1.4.1 Modifyingthesystemrestoresession-specificfsetup.conffile.
134
7.1.4.2 Startingrestoringsession...........................................................135
7.1.5 Replacingthefailedharddiskdrive.......................................... 136
7.1.5.1 RemovingfaultyHDD.................................................................137
7.1.5.2 InstallingthenewHDD...............................................................138
7.1.6 ComissioningCFPU-0................................................................138
7.1.6.1 ConnectingFEWStothecontrollerforsystemrestore.............. 138
7.1.6.2 Deactivatingnodes.....................................................................139
DN09210645Issue:01C 2016Nokia 5
CommissioningFlexiZoneController
7.1.6.3 DownloadingtheSWimage.......................................................140
7.1.7 Performingpost-configurationofthecontroller.......................... 143
7.1.8 RestoringfrombackupISO........................................................144
7.1.9 Activatingandunlockingnodes..................................................146
7.1.10 Checkingsystemstatesandsavingconfiguration..................... 147
7.2 FZCcleaninstallation.................................................................148
7.2.1 Introductiontocleaninstallation.................................................149
7.2.1.1 Cleaninstallationpreconditions................................................. 149
7.2.1.2 Applicationsoftwareinstallationoverview..................................149
7.2.2 PreparingSWdeliveryontheFEWS......................................... 150
7.2.2.1 Copyingsoftwaredelivery.ISOimagetoFEWS........................150
7.2.2.2 Extractingsoftware.ISOimagetoadeliveryfolder................... 151
7.2.2.3 Creatingsession-specificfiles....................................................152
7.2.3 UpgradingFZCembeddedsoftware.......................................... 153
7.2.3.1 PreparingFEWSforeSWupgrade............................................ 154
7.2.3.2 ConnectingFEWStothecontrollermodule............................... 156
7.2.3.3 UpgradingtheBCNmotherboard'seSW................................... 158
7.2.3.4 UpgradingtheBMPP2-Badd-incards'eSW..............................160
7.2.4 Performingmodulepre-configuration.........................................166
7.2.4.1 Runningpre-configurationscript................................................ 166
7.2.4.2 SettingtheLMPdate..................................................................169
7.2.4.3 ActivatingtheLMPpre-configurationchanges...........................170
7.2.4.4 Verifyingmodule'sLMPpre-configuration..................................170
7.2.5 InstallingtheSWpackageapplicationtothecontroller..............174
7.2.5.1 Modifyingthesession-specificfsetup.conffile.................... 174
7.2.5.2 Creatingcommissioningsession................................................176
7.2.5.3 ConnectingFEWStothecontrollerwithEthernetportconfigured...
177
7.2.5.4 DownloadingtheSWimage.......................................................178
7.2.6 FZCmodulepost-configuration..................................................181
7.2.6.1 Runningpost-configurationscriptaftercleaninstallation...........181
7.2.6.2 SynchronizingLMPflashbanks.................................................. 182
7.2.7 Verifyingcontrollercommissioningaftercleaninstallation......... 183
7.3 ReturningControllertofactorysettings......................................185
7.4 ImprovingFZAPuplinkthroughput.............................................186
6 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController
List of Figures
Figure1 FlexiZoneControllercommissioningworkflow.................................. 12
Figure2 CablingbetweenFEWSandthecontrollermodule............................21
Figure3 TaskSelectionview............................................................................ 70
Figure4 Autoconfigurationdialogbox.............................................................. 74
Figure5 EnterAutoconnectionParametersManuallydialogbox.....................74
Figure6 AutoconnectionRegistrationdialogbox............................................. 75
Figure7 Commissioningoverview....................................................................76
Figure8 IntegratingFZAPstoaZoneeNB.....................................................116
Figure9 BTSSMAutoconnectionRegistrationdialogscreen......................... 117
Figure10 BTSSMAutoconfigurationdialog...................................................... 118
Figure11 BTSSMConfigurationresetdialog................................................... 119
Figure12 FlexiTransportModuleRecover TRSmenu.................................... 120
Figure13 WebUIConfigureSiteIDdialog........................................................121
Figure14 AutoConnection&Configurationprogressdialog............................122
Figure15 WebUIConfigurationresetdialog.....................................................123
Figure16 TheSAS/SATAswitchintheHDSAM-A........................................... 137
Figure17 TheharddiskdriveontheharddiskdrivecarrierAMC................... 137
Figure18 InstallingaharddiskdriveontotheharddiskdrivecarrierAMC..... 138
Figure19 CablingbetweenFEWSandthecontrollermodule..........................139
Figure20 CablingbetweenFEWSandthecontrollermodule..........................157
Figure21 CablingbetweenFEWSandthecontrollermodule..........................178
DN09210645Issue:01C 2016Nokia 7
CommissioningFlexiZoneController
List of Tables
Table1 ............................................................................................................27
Table2 add fzc-ipseccommands............................................................45
Table3 delete fzc-ipseccommands.....................................................49
Table4 Parametersforconfiguringstaticroutes.............................................54
Table5 ParametersforNTPconfiguration...................................................... 58
Table6 ParametersforDNSconfiguration......................................................60
Table7 SystemHWandSWrequirementsforBTSSiteManager................. 68
Table8 Parametersfortransferringthebackupimageandchecksumfileto
thedesiredlocation.......................................................................... 129
Table9 Backupnamingconvention.............................................................. 144
Table10 LMPeth0portconfiguration............................................................. 166
Table11 Requiredpre-configurationscriptparameters.................................. 169
Table12 Commissioningparametersinfsetup.conffile.......................... 174
Table13 LMPeth0portconfiguration............................................................. 175
8 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController Summaryofchanges
Summary of changes
Changesbetweendocumentissuesarecumulative.Therefore,thelatestdocument
issuecontainsallchangesmadetopreviousissues.
Setting Zone eNB APMOD Parameters with BTSSM
StepEnter the Geo Coordinates of the APMODhasbeenupdated.
Creating session-specific files for system restore
StepCopy the session configuration file and initialization scripthasbeenupdated.
Running pre-configuration script
Prerequisitesfortheprocedurehavebeenupdated.
Thepurposeoftheprocedurehasbeenupdated.
DN09210645Issue:01C 2016Nokia 9
Summaryofchanges CommissioningFlexiZoneController
10 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController IntroductiontoFlexiZoneControllercommissioning
Commissioningisaprocessofinstallingtherequiredsoftwareandthenecessary
configurationsonanetworkelement(NE).Itisperformedafterinstallingthehardware
andbeforethenetworkelementisconnectedtotheoperator'snetwork.DuetotheFZC's
SWarchitecture,twoseparatecomissioningproceduresneedtobeimplemented:
commissioningoftheFZCapplicationandembeddedsoftwarethroughSCLIviaa
fieldengineeringworkstation
commissioningoftheFZCLTEstackviatheBTSSiteManagerapplication
Theseinstructionsassumethattheuserhasabasicknowledgeofnetworkingandbase
stationssystems.
w NOTICE: Onlyproperlytrainedandauthorizedpersonnelmayperforminstallation,
commissioning,ormaintenanceoperationsonanyNokiaNetworkElement.
Screenshotsandcommandlineprintoutsareincludedasexamples,andtheinformation
depictedonthemmaydifferdependingonparticularcircumstances.
Purpose
TheprovisionofaZoneeNBrequiresthecommissioningoftheFlexiZoneController
moduleandtheestablishingofsouthboundandnorthboundinterfaces.Aseriesof
commissioning,configuration,andintegrationproceduresneedtobefollowedinorderto
provisionafunctionalZoneeNB.
Procedure
DN09210645Issue:01C 2016Nokia 11
IntroductiontoFlexiZoneControllercommissioning CommissioningFlexiZoneController
4 Commissioning the FZC module via the BTS Site Manager application
SeeCommissioningFlexiZoneController(DN09210645)fordetailedinstructions.
6 Integrating individual FZAPs under the FZC via BTS Site Manager and WebUI
SeeCommissioningFlexiZoneController(DN09210645)fordetailedinstructions.
Figure 1 FlexiZoneControllercommissioningworkflow
Start
VerifyHW
installation
OK
NES3integration FZC
toNetAct IP configuration
BTSSM
Commission
NWI3integration
toNetAct
WebUI/BTSSM
FZAP integration
Commissioned
ZoneeNB
12 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController IntroductiontoFlexiZoneControllercommissioning
ConfiguredFZAPscanbeadded(connected)orremoved(disconnected)totheZone
eNBunderaFZCwithoutaffectingtheavailabilityoftheFZCand/oranyotherFZAPs
underthatFZC.
DN09210645Issue:01C 2016Nokia 13
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
Thissectioncoversconfigurationstepstobeperformedafterthehardwareinstallationof
FZCnetworkelementhasbeensuccessfullycompleted.Afterconfiguration,theFZC
networkelementisreadyforsite-specificintegration.
AFieldEngineeringWorkstation(FEWS)isastardardPClaptoporworkstationwhichis
providedwiththenecessaryDHCPandTFTPservicestocommunicatewithaNEfor
configurationpurposes.
g Note: NokiadoesnotprovideFEWSasanofficialproduct.Itisuptotheuserto
acquireboththehardwareandoperatingsystem.
NokiarecommendsCentOSastheFEWSoperatingsystem,butanyequivalentLinux
distributionmayalsobeused.TheinstructionswithinthisdocumentassumeCentOSis
beingused.
Procedure
a) WithSSHclient:
14 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
OpentheSSHclient.
Fillintherelevantfields,includingtheFEWShostnameorIPaddress(and
port22).SelectLogin.
Attheloginprompt,enterthefollowing:root
Attheroot@<IP_address>prompt,enterthepasswordfortheroot
user.TheremoteconnectiontoFEWSisopened.
b) Usingaterminal:
Enterthefollowingcommand:ssh root@<FEWS_hostname_or_IP>
ConfirmthehostkeyauthenticitybygivingtheYesanswer.
Attheroot@<IP_address>prompt,enterthepasswordfortheroot
user.TheremoteconnectiontoFEWSisopened.
a) Intheusernamefield,enterroot.
b) Inthepasswordfield,enterthepasswordfortherootuser.
g Note: Thisproceduretakesapproximately30minutes.
Procedure
a) OpenSELinuxconfigurationfilewiththefollowingcommand:
# vi /etc/sysconfig/selinux
b) ChangetheSELinuxenforcingvaluetodisabled.Saveandexitthe
configurationfile.
Step result
SELINUX=disabled
DN09210645Issue:01C 2016Nokia 15
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
a) Openthetftpbootconfigurationfilewiththefollowingcommand:
# vi /etc/xinetd.d/tftp
b) Findthefollowingline:
server_args = -s /var/lib/tftpboot
c) Editittogetthefollowingline:
server_args = -s /tftpboot
d) Lookforservice tftpentryandensurethatthelinedisable=nois
present.Incasedisable=yesispresent,editthefile,andchangethelineto
disable=no.Saveandexittheconfigurationfile.
e) Restartthexinetddaemonafterfilemodificationwiththefollowingcommand:
# service xinetd restart
a) Gotothespecifieddirectorywiththefollowingcommand:
# cd /etc
b) Allowtherootusertoeditthefilewiththefollowingcommand:
# chmod 644 hosts.allow
c) Openthe/etc/hosts.allowfileinthevieditorandmodifythefileby
commentingallentriesout.InthelastlineaddALL: ALLtoallowallusersto
accesstheFEWSremotely.
Saveandexittheconfigurationfile.
a) Allowtherootusertoeditthefile.
# chmod 644 hosts.deny
b) Openthe/etc/hosts.denyfileinthevieditorandmodifythefileby
commentingallentriesout.
Saveandexittheconfigurationfile.
16 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
# cat /etc/exports
/opt/nsn/fews *.*.*.*(rw,no_root_squash)
Ifthelineismissing,editthefileandaddit.
Saveandexittheconfigurationfile.
iptables-mustnotberunning.Todisabletheservice,enter:
service iptables stop
nfs-mustberunning.Toenabletheservice,enter:
service nfs start
xinetd-mustberunning.Toenabletheservice,enter:
service xinetd start
HitTABinordertoreachOKbutton.HitOKtoexitntsysv.
Result
FEWSisnowreadytobeusedforcommissioning.
DN09210645Issue:01C 2016Nokia 17
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
g Note: ThecommissioningandembeddedSWupgradeproceduresareprovidedto
allowoperatorstomanagetheirexistingNEpool.Newlypurchasedcontrollersare
factory-commissionedbeforebeingprovidedtothecustomer.
Verifyingthecontroller'sHWinstallation
Verifyingthecontroller'sfactorysettings
Verifyingthecontroller'slogicalnetworkelementID
Verifyingthecontroller'sfactorycommissioning
Controller site-specific installation parameters needed for commissioning
TheCluster-ID/Radio-NetworkFZC-IDisnecessaryinordertoconfigureLMPs,
backplaneconnectionsandswitches.Itiswrittenonthestickerplacedonthefrontpanel
oftheFZCnode.
2. TheeSW(embeddedSW)installationissuccessfullycompletedintheNokiafactory.
3. LMPpre-configurationissuccessfullycompletedintheNokiafactory.
4. Cablestobeusedduringcommissioning:
straight-throughEthernetcableusedtoconnecttheFEWSorotherlaptoptothe
controller'smanagement(MGT)port
5. Anti-staticequipmenttobeusedduringcommissioning
wristband
anti-staticmat
6. Thecontrollersite-specificinstallationparametersneededforconfiguration:
FZC-ID,auniqueidentifierwithinRANsetbytheoperatorbasedonaradio
networkplan
NE-ID(configuredintheNokiafactory)
g Note: TheFZC-IDmustnotincludeanycharactersotherthanlettersandnumbers.
Example:FZC19insteadofFZC-19.ThisisarequirementfornorthboundNetAct
integration.
7. LaptopwithEthernetinterface.
g Note: TheinstructionsinthisdocumentassumethataLinux-basedPClikeFEWSis
availableforperformingtheprocedures,butitisnotnecessary.Theusercanusea
Windows-basedPCaslongashehastherequiredpermissionstochangeIP
addressesonit.
Controller network element factory settings
18 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
CLUSTERID:FZC1234
FZC_ID:FZC1234
FCPUrootpassword:root
FCPU_nokadminpassword:system
Module MGT port LMP IP addresses
Module1:192.168.10.51
VerifyingHWinstallation
Verifyingfactorysettings
Changingthecontrollercluster-ID/FZC-ID
Verifyingfactorycommissioning
Procedure
DN09210645Issue:01C 2016Nokia 19
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
20 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
Phase3
P1--P2LEDsturngreen.Thisindicatesthatadd-incardsarerunningplatform
LinuxSW.
Procedure
Figure 2 CablingbetweenFEWSandthecontrollermodule
DN09210645Issue:01C 2016Nokia 21
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
5 Verify connection between FEWS and the controller module's MGT port.
Sendapingpackettocheckwhethertheconnectionisconfiguredproperly.Onthe
FEWSenterthefollowingcommand:
# ping c 3 192.168.10.51
Nopingpacketreplyoccurswhen:
theFEWSisnotconnectedtothecontrollerfactory-commissionedmoduleone
theFEWSeth0configurationhasnotbeendoneproperly
Iftheproblemwasinthemodule'sinitialconfiguration,runtheLMPpre-configuration
accordingtoPerforming module pre-configurationinCleaninstallation.
Procedure
1 Log in to LMP-1-1-1.
Enterthefollowingcommand:
# ssh root@192.168.10.51
Password:root
2 Ping FCPU-0.
Enterthefollowingcommands:
# ping c 3 FCPU-0
Step result
3 packets transmitted, 3 received, 0% packet loss, time 206
22 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
Procedure
Step example
dn: fsClusterId=ClusterRoot
objectClass: FSCluster
objectClass: extensibleObject
fsClusterId: ClusterRoot
fsLayer: FlexiPlatformBase FlexiPlatformFull FZBCN
fsDeployment: create_fzc_bcnb_2slots.sh
fsMeshConfiguration: full-mesh
fsMOID: 1
fsLastMOID: 168
fsLogicalNetworkElemId: FZC01
Step example
set config attribute fsClusterId=ClusterRoot attribute-
list fsLogicalNetworkElemId FZC01
Step example
fsLogicalNetworkElemId: FZC01iscorrectlyformatted.
DN09210645Issue:01C 2016Nokia 23
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
Procedure
Step result
Statusforallnodesis:UNLOCKED/ENABLED/ACTIVE
g Note: Notethattheconfigurationneedstobesavedtopreserveoversystemrestart.
Tosaveasnapshot,enter:
> save snapshot
Theseproceduresmustbeperformedviathecontroller'sfsclishbashbeforeanyfurther
integrationcanbeinitiated.
WhentheFZCisfirstpoweredupforfieldcommissioning,theFZCisconfiguredwiththe
followingstandardconfigurations:
Whenthisconfigurationisdeployed,nochangesareneededtotheEthernetinterface
configuration.
24 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
g Note: TheInterfacelabelsarehard-codedintothecontrollerswitchinglogic.Theymust
beintroducedfollowingtheexactsamespellingpresentedinthisdocument.
Twootherconfigurationsaresupportedthatrequirereconfigurationduringfield
commissioning.
WhenM-planeandC-planeinterfacesareseparatedontheFCPU.
WhenthesouthboundZ1sbzplaneiscomprisedofasetof1Ginterfacesinsteadof
asingle10Ginterface.
g Note: Thenumberofavailable1Ginterfacesisdependentonhowmany1Ginterfaces
areinusefortheNorthboundinterfaces.Thereare101Gportsavailable:ifSFP14is
usedfornorthboundinterfacing,onlySFP15toSFP22willbeavailablefor
southbound.
2.3.1.1 Confirming that the Ethernet Interfaces on Flexi Zone Controller are
configured correctly
Procedure
Purpose
InordertochangetheIPaddressofinterfaceswithinthe,youneedtofirstdeletethe
existinginterface.
DN09210645Issue:01C 2016Nokia 25
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
Procedure
1 Delete interface:
delete networking address <owner> iface <iface> ipaddress
<ip-address>
Step example
delete networking address /FZBU-0 iface sbzplane ip-address
192.168.55.1
Step example
add networking address /FZBU-0 ip-address 192.168.55.1/24
iface sbzplane
Purpose
TheZ1interfaceconnectstheFZCtothenetworkofFZAPs.Itisamandatoryinterface
ontheControllerandfunctionsasthedefaultrouteforallFZAPsinaflatlayer2network
fortheZoneeNB.Inanon-flatlayer2network,suchasonewithmultipleenterprises
behindarouterorrouters,theZ1interfacewouldfunctionasthedefaultroutefromthe
edgerouteroneachenterprise.ThissectionshowshowtosetuptheZoneeNB
southboundZ1interfacewithinaFlexiZoneControllerthroughtheuseofSCLI
commands.
g Note: ThenameoftheZ1interfacemustbesbzplane.
Procedure
26 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
Further information
WhentheZ1InterfaceissetupwithaVLANandtheIVIFobjectisnotprovidedtothe
FZAP,theFZAPsderivetheIVIFparametersfromtheresponsereceivedfromtheDHCP
serverandfromasubsetoftheIEIFparametersprovidedtotheFZAP.
TheVLANIDissettothevalueoftheVLANthattheDHCPserverison,andthelocalIP
addressissettothevalueprovidedbytheDHCPserver.Theremainingattributevalues
oftheIVIFarecopiedfromtheIEIF.TheIEIF::qosEnabledvaluemustbesetto
True.
Related descriptions
EthernetInterfacesonFlexiZoneControlleronpage24
Purpose
AFlexiZoneControllerrequiresthesetupofatleasttwonorthboundinterfaces:a
dedicatedU-planeinterface,andajoinedM/C-planeinterface.
Alternatively,theM-planeandC-planeinterfacescanbesetupseparately,makinga
totalofthreenorthboundinterfaces.
DN09210645Issue:01C 2016Nokia 27
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
Related descriptions
EthernetInterfacesonFlexiZoneControlleronpage24
Related procedures
SettinguptheFZCU-planeinterfaceonpage28
SettinguptheFZCM-planeinterfaceonpage28
SettinguptheFZCC-planeinterfaceonpage29
Purpose
TheU-planeinterfaceconnectstheFZCtotheServingGateway.Itisamandatory
interfaceontheControllerandfunctionsastheonlyinterfacethattransmitsandreceives
GTP-Ubearertrafficonthebackhaul(S1-U).ManagementandC-planeservicesarenot
providedonthisinterface.ThissectionshowshowtosetuptheZoneeNBnorthbound
U-planeinterfacewithinaFlexiZoneControllerthroughtheuseofSCLIcommands.
g Note: ThenameoftheU-planeinterfacemustbenbuplane.
Procedure
SetuptheU-planeInterfacewithoutVLANbyenteringthefollowingcommand:
add networking instance default ether /FZBU-0 port sfp12
iface nbuplane admin up ipv4forwarding yes mtu 1500
ipv4rpfilter no proxy-arp no
SetuptheU-planeInterfacewithVLANbyenteringthefollowingcommands:
add networking instance default ether /FCPU-0 port sfp12
iface ethsfp12 admin up ipv4forwarding yes ipv4rpfilter
no proxy-arp no
add networking instance default vlan /FCPU-0 realiface
ethsfp12 vid 530 vlaniface nbuplane
Purpose
28 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
TheM-planeinterfaceconnectstheFZCtoiOMS/NetAct.Itisamandatoryinterfaceon
theControllerandfunctionsastheonlyinterfacethattransmitsandreceives
managementtrafficonthebackhaul.U-plane(bearer)servicesarenotprovidedonthis
interface.IfnodistinctC-planeinterfaceiscreated,M-plane(nbmplane)andC-plane
trafficiscollapsedontotheM-planeinterface.TheM-planeinterfaceaddressalsoserves
astheinterfaceforFZAPmanagement.ThissectionshowshowtosetuptheZoneeNB
northboundM-planeinterfacewithinaFlexiZoneControllerthroughtheuseofSCLI
commands.
g Note: ThenameoftheM-planeinterfacemustbenbmplane.
Procedure
SetuptheM-planeInterfacewithoutVLANbyenteringthefollowingcommand:
add networking instance default ether /FCPU-0 port sfp13
iface nbmplane admin up ipv4forwarding yes mtu 1500
ipv4rpfilter no proxy-arp no
SetuptheM-planeInterfacewithVLANbyenteringthefollowingcommands:
add networking instance default ether /FCPU-0 port sfp13
iface ethsfp13 admin up ipv4forwarding yes ipv4rpfilter
no proxy-arp no
add networking instance default vlan /FCPU-0 realiface
ethsfp13 vid 540 vlaniface nbmplane
Step result
Youshouldseethefollowingprintout:
IP addresses in default instance:
nbmplane
address : 10.10.40.1/24
owner : /FCPU-0
user : /SSH /Ne3sAgent /ClusterDNS /ClusterNTP /RuimReplicator
Purpose
DN09210645Issue:01C 2016Nokia 29
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
TheC-planeinterfaceconnectstheFZCtoiOMS/NetAct.Itisanoptionalinterfaceon
theControllerwhennotcollapsedw/theM-planeinterfaceandfunctionsastheonly
interfacethattransmitsandreceivescallcontroltrafficonthebackhaulwiththeMME.U-
plane(bearer)servicesarenotprovidedonthisinterface.M-plane(management)
servicesarenotprovidedonthisinterface.ThissectionshowshowtosetuptheZone
eNBnorthboundC-planeinterfacewithinaFlexiZoneControllerthroughtheuseofSCLI
commands.
g Note: ThenameoftheC-planeinterfacemustbenbcplane.
Procedure
SetuptheU-planeInterfacewithoutVLANbyenteringthefollowingcommand:
add networking instance default ether /FZBU-0 port sfp14
iface nbcplane admin up ipv4forwarding yes mtu 1500
ipv4rpfilter no proxy-arp no
SetuptheU-planeInterfacewithVLANbyenteringthefollowingcommands:
add networking instance default ether /FCPU-0 port sfp14
iface ethsfp14 admin up ipv4forwarding yes ipv4rpfilter
no proxy-arp no
add networking instance default vlan /FCPU-0 realiface
ethsfp14 vid 530 vlaniface nbcplane
30 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
g Note: TheMACaddressfortheFZAPinuseshouldbetheMACaddressassignedto
theprimarybackhaulinterface.TheprimarybackhaulMACaddressisusedforpackets
to/fromtheFZCsDHCPserver.AninternalMACaddressisusedforallotherpackets
betweentheFZAPandtheFZC.
Procedure
1 Check that the IP address is not currently leased to another FZAP. Show
flexizone dhcp ip <apip>
Show flexizone dhcp ip <apip>
Where<apip>istheFZAPIPaddress.
g Note: Thesbzplaneaddresswillnotbeshownbytheabovecommandbuttheadd
commandinthenextstepwillfailifthesbzplaneaddressisused.
Step example
show flexizone dhcp ip 192.168.55.2
Step result
IP: 192.168.55.2 maps to MAC: 74:fe:48:01:90:3b
Step example
add flexizone dhcp ip 192.168.55.2 mac 00:0f:bb:d7:27:d2
Step result
added static mapping between MAC 00:0F:BB:D7:27:D2 and IP
Address 192.168.55.2
a) Waitonehourtoallowtheexistingleasetoexpire.
b) UsetheconfigurationresetbuttonontheFZAPthatcurrentlyhastheleaseto
resetitbackastatethattheFZAPwillacquireadifferentleasefromtheDHCP
server.
c) Shutoff(ordisconnectfromthenetwork)theFZAPthatcurrentlyhasthelease
foronehourtoallowtheleasetoexpire.
DN09210645Issue:01C 2016Nokia 31
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
g Note: FailuretoperformoneoftheabovestepswillresultinduplicateIPaddress
usageinthenetwork.
Purpose
Whenthesharedbackhaulfeatureisenabled,theDHCPserversupportsupto9
additionalenterpriseconfigurations.Thefirsthoproutersintheenterprisenetworkneed
tobeconfiguredasaDHCPrelayagenttoforwardtheDHCPrequeststotheFZC
sbzplaneinterface.TheDHCPserverrequiresconfigurationwithinformationaboutthe
enterprisesothatitcanprovidethecorrectIPinformationforFZAPlocatedinthe
enterprise.ThefollowingstepsareperformedtoconfiguretheDHCPserverforan
enterprise.
Before you start
FullIPSecshouldbeestablishedonthesbzplaneinterfacebeforeenablingshared-
backhaul.Thefollowingarerequiredbeforestartingtheprocess:
1. Theoperatormanages/ownstheL3routeranditsconfiguration.
2. AllFZAPsareconnectedtotheaggregationswitchviaEthernetcabling.
3. TheL3routermustnotbeconfiguredwithanyofthefollowing:
NetworkAddressTranslation(NAT)
NetworkAddressandPortTranslation(NAPT)
4. TheFZAPsmustbedeployedwithinuniquesubsetsacrosstheenterpriseVLANs.
5. TheuseofIPSecismandatorywithintheZonedeployment.
6. OutgoingtrafficfromanFZAPviaanL3routerneedstogothroughtheFZC
southbound(SB)interface.
7. L2/L3markingsmustbeconfiguredandhonoredbytheintermediatezonedevices.
Thefollowinginformationisrequiredbeforestartingtheconfigurationprocess:
1. Gatewayrouteronthesbzplanenetwork
Thesameaddressisusedforalladditionalenterprises.
2. EnterpriseName
Maximumof15characters.
3. IPaddressfortheenterprisedefaultgateway
4. CIDRSubnetmasklengthforthesubnet
Example:aclassCnetworkhasalengthof24,aclassAnetworkhasalengthof8.
5. StartIPaddressesfordynamicassignment
6. EndIPaddressesfordynamicassignment
g Note: Alladdressesinthesubnetexceptnetworkaddress,broadcastaddressand
defaultgatewayaddressareassumedtobeavailableforassignmentifthestartand
endaddressesarenotprovided.
7. MaximumTransmissionUnit(MTU)ofthenetwork
32 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
Thisisoptional.TheMTUrangemustbewithin576-1644octets,andissettoa
defaultvalueof1500iftheMTUsizeisnotprovided.
8. AnystaticIPtoMACmappings
StatipIPstoMACmappingscanbeaddedpostconfigurationbyfollowingstepsin
AddingDHCPServerStaticMACtoIPassignment.
Procedure
Step example
set flexizone shared-backhaul enterprise L3 route-ip
196.169.10.10
2 Add enterprise to the DHCP server by executing the following SCLI command:
add flexizone shared-backhaul enterprise ent-name <Unique
Enterprise Name> gw-ip <Gateway router on the Enterprise
Network> subnet-addr <CIDR Subnet mask length for the
subnet> {mtu <Maximum Transmission Unit (MTU) of the
network> allocation-start <Start IP addresses for dynamic
assignment> allocation-end <End IP addresses for dynamic
assignment>}
g Note: mtu,allocation-startandallocation-endareoptionalandcanbe
omittedfromtheabovecommand.
Step example
add flexizone shared-backhaul enterprise ent-name
enterprise1 gw-ip 168.10.10.10 subnet-addr 192.10.11.12/26
mtu 1644 allocation-start 192.168.11.40 allocation-end
192.168.11.63
DN09210645Issue:01C 2016Nokia 33
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
Purpose
WhentheFZCisfirstpoweredupforfieldcommissioning,itissetuptousetheM-Plane
IPaddressasthecertificatemanagementprotocol(CMP)serverIPaddress.This
configurationisusedtoprotecttheZ1C-PlaneandM-PlanetrafficwithIPSec.Thisis
thedefaultconfiguration.
ThefollowingtypesoftrafficcannotbesecuredusingtheM-PlaneIPaddress
configuration:
Z1U-PlanetrafficusingIPsec
AnytrafficfromFZCtocorenetworkusingIPsec
M-planetrafficfromFZCtoNetActusingTLS
M-PlanetrafficfromFZCtoCNUMLDAPserverusingTLS
Inordertosecuretheabovetraffic,theFZChastobeconfiguredwithacustomer
providedCMPserverIPaddress.Thereareseveralconfigurationscenariosfor
configuringtheCMPPublicKeyInfrastructureinaFlexiZoneController.
Purpose
TomigratetheFZCfromtheinternalPublicKeyInfrastructure(PKI)toacustomer
providedPKI,aseriesofcommandsmustbeintroducedintotheFZCfsclishbash.
Procedure
34 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
DN09210645Issue:01C 2016Nokia 35
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
Result
OncetheabovecommandsarerunontheFZC,theFZAPwillbetriggeredtousethe
sameCMPserveranddownloadcertificatesusingCMP.
g Note: Theaboveorderandsetofcommandsalsocoversthefollowingscenarios:
UpdateRootCAcertificate(duetoexpiration/revocation)
ReplacementofEndEntitycertificate(duetoexpiration/revocation)
ChangeinPKIhierarchy(additionorremovalofIntCA)
Purpose
TomigratefromonecustomerprovidedPublicKeyInfrastructure(PKI)toanother
customerprovidedPKI,aseriesofcommandsmustbeintroducedintotheFZCfsclish
bash.
Procedure
36 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
DN09210645Issue:01C 2016Nokia 37
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
Result
ThiswillensurethatthepoliciesareupdatedwiththenewCMPserverIPaddress.
Purpose
TomigratefromonecustomerprovidedPublicKeyInfrastructure(PKI)backtothe
internalPKI,aseriesofcommandsmustbeintroducedintotheFZCfsclishbash.
Procedure
38 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
Procedure
1 start transaction
DN09210645Issue:01C 2016Nokia 39
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
g Note: Youcancheckcertificatesexpirationdatefromthene3s-wsdomain.Ifthe
certificatesisnotpresentinthene3s-wsdomain,thenyoucancheckitfromthe
defaultdomain.
Procedure
1 If
thecertificateshasbeeninstalledunderne3s-wsdomain.
Then
Check the expiration date of the certificates from the ne3s-wsdomain.
show security cert ne3s-ws ee-cert
Thefollowingisasampleprintoutofthecommandresults.
ThevalidityofthecertificatesisspecifiedunderheadingValidity.
##############################################################
Domain: ne3s-ws
##############################################################
certificates
Data:
Version: 3 (0x2)
Serial Number: 10658 (0x29a2)
Signature Algorithm: sha1WithRSAEncryption
Issuer: C=MyCountry, O=MyCompany Tampere, CN=MRTampereRootCA
Validity
Not Before: Feb 22 15:36:35 2010 GMT
Not After: Feb 20 15:36:35 2020 GMT
Subject: C=MyCountry, O=MyCompany Tampere, CN=MRTampereRootCA
.........
.........
##############################################################
Else
Check the expiration date of the certificates from defaultdomain.
show security cert default ee-cert
Thefollowingisasampleprintoutofthecommandresults.
ThevalidityofthecertificatesisspecifiedunderheadingValidity.
##############################################################
Domain: default
##############################################################
certificates
Data:
Version: 3 (0x2)
40 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
Summary
TocheckwhethertheexpiredCAorEEcertificateisrelatedtoNE3S.
TheNE3SserviceconnectstoanexternalNetActLDAPservereitherthroughaplain-
textoraTLSencryptedconnection.Also,theNE3Sserviceactsasaserviceandlistens
toexternalmessages.Thus,theNE3Sserviceactssimultaneouslyasaclientanda
server.HencerequiresbothCAandEEcertificates.
IfatrustanchorCAcertificaterelatedtotheNE3Sserviceexpires,theNE3Sservicein
theTLSmodecannotestablishnewTLSconnectionstotheexternalNetActserverasit
cannotauthenticatethereceivedservercertificate.
IfanEEcertificaterelatedtotheNE3Sserviceexpires,theNE3Sserviceclients
(NetAct)cannotconnecttoit.
TheexpiredCAorEEcertificatealarmcancomefromeitherthedefaultortheservice-
specificcertificatedomain(NE3Sinthiscase).Analarmfromthedefaultcertificate
domaincanaffecttheNE3SserviceifthealarmisgeneratedforitstrustanchorCA
certificateorEEcertficateandtheNE3Sserviceisusingthedefaultcertificatedomain.
AnalarmfromtheNE3ScertificatedomainalwaysaffectstheNE3Sservice.
Formoreinformationoncertificatealarm,refertoCertificate expirationinAdministration
Guide.
FormoreinformationoncertificateSCLIcommands,refertoCertificate management
SCLI commandsinAdministration Guide.
Formoreinformationoncertificatealarm,refertoAlarm description.
DN09210645Issue:01C 2016Nokia 41
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
Procedure
3 Confirm if the certificate alarm in the default domain affects the certificate
belonging to NE3S.
Enteroneofthefollowingcommanddependingonwhethertheexpiredcertificatea
CAoranEEone:
42 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
g Note: Formoreinformationonhowtoreplacethecertificate,referto
Replacing the expired certificated with a new active certificate
Manual installation:
UploadthecertificatesfiletotheNEusingfiletransferprocess,forexample
SFTP/SCPfromanexternallocation,andusethebelowSCLIcommandtoinstall
them:
EEcertificate:
set security cert <domain> ee-cert cert-file <cert-file>
key-file <key-file>
CAcertificate:
set security cert default ca-cert cert-file /share/ca.pem
ca-id common cert-type new-with-new
Formoreinformation,refertoInstalling certificates manually in NE3S/WS.
FordetailedinstructiononSFTP/SCP,refertoFile management.
Using CMP:
TheprocedurediffersbasedonwhetherthecertificatesareretrievedusingCMP
initializationrequestorCMPkeyupdaterequest.ItisrecommendedtouseCMPkey
updaterequesttorenewtheEEorintermediatecertificateunlessthecertificateshas
alreadyexpired.UseCMPinitializationrequestifthecertificatehasalreadyexpired.
CMPinitializationrequest:
FetchanewcertificatefromtheCMPserverandinstallitintotheconfiguration
directory.
Formoreinformation,refertoInstall certificates retrieved automatically via the
CMP server in NE3S/WS.
CMPkeyupdaterequest:
FetchanewcertificateusingtheCMPkeyupdaterequestandinstallintothe
configurationdirectory.
Formoreinformation,refertosectionUpdating certificates in NE3S/WS.
DN09210645Issue:01C 2016Nokia 43
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
Ifthecertificateisexpiredorabouttoexpire,obtainandinstallanewonebyfollowing
thebelowinstructions.Theproceduretofollowdiffersbasedonwhetherthecertificates
aremanuallyinstalledorautomaticallyfetchedthroughCertificateManagementProtocol
(CMP).
Manual installation:
UploadthecertificatesfiletotheNEusingfiletransferprocess,forexample
SFTP/SCPfromanexternallocation,andusethebelowSCLIcommandtoinstall
them:
EEcertificate:
set security cert <domain> ee-cert cert-file <cert-file>
key-file <key-file>
CAcertificate:
set security cert default ca-cert cert-file /share/ca.pem
ca-id common cert-type new-with-new
Formoreinformation,refertoInstalling certificates manually in NE3S/WS.
FordetailedinstructiononSFTP/SCP,refertoFile management.
Using CMP:
TheprocedurediffersbasedonwhetherthecertificatesareretrievedusingCMP
initializationrequestorCMPkeyupdaterequest.ItisrecommendedtouseCMPkey
updaterequesttorenewtheEEorintermediatecertificateunlessthecertificateshas
alreadyexpired.UseCMPinitializationrequestifthecertificatehasalreadyexpired.
CMPinitializationrequest:
FetchanewcertificatefromtheCMPserverandinstallitintotheconfiguration
directory.
Formoreinformation,refertoInstall certificates retrieved automatically via the
CMP server in NE3S/WS.
CMPkeyupdaterequest:
FetchanewcertificateusingtheCMPkeyupdaterequestandinstallintothe
configurationdirectory.
Formoreinformation,refertosectionUpdating certificates in NE3S/WS.
Purpose
IPsecprotectionisafunctionalityincludedinfeatureLTE2017: IPSec Support for Flexi
Zone Controller
WhentheFZCisfirstpoweredupforfieldcommissioning,itisconfiguredwiththe
followingIPsecpolicies:
ProtectpoliciesforZ1C-PlaneandM-Planetraffic.
BypasspoliciesforZ1DHCP,CMPandLDAPtraffic.
WhentheFZCisconfiguredwithacustomerprovidedPKI(CMPserver),thefollowing
policiescanbeconfigured:
ProtectpolicyforZ1U-Plane(SB).
Protect,bypassanddiscardpoliciesforconnectionsfromFZCtoCore(NB).
44 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
Related procedures
ActivatingandconfiguringLTE2017:IPSecSupportforFlexiZoneControlleronpage45
DeactivatingLTE2017:IPSecSupportforFlexiZoneControlleronpage49
2.3.8.1 Activating and configuring LTE2017: IPSec Support for Flexi Zone
Controller
DN09210645Issue:01C 2016Nokia 45
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
46 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
ThefollowingsectionsprovidethewrappercommandscoveringthemostcommonIPsec
activationusecases.
FormoreinformationontheseandothercommandsseeFlexi Zone Controller SCLI
Commands (DN09210703).
Applying IPsec to the FZC southbound interface (Z1) and to the northbound
user plane
Sub-steps
DN09210645Issue:01C 2016Nokia 47
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
Applying IPsec to the FZC southbound interface (Z1) and to the northbound
control and management planes
Sub-steps
Applying IPsec to the FZC southbound interface (Z1) and to the northbound
control, management and user planes
Sub-steps
48 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
Applying IPsec to the FZC northbound control, management and user planes
Sub-steps
DN09210645Issue:01C 2016Nokia 49
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
ThefollowingsectionsprovidethewrappercommandscoveringthemostcommonIPsec
deactivationusecases.
FormoreinformationontheseandothercommandsseeFlexi Zone Controller SCLI
Commands (DN09210703).
Removing IPsec from the FZC southbound interface (Z1) and the northbound
user plane
Sub-steps
50 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
Removing IPsec from the FZC southbound interface (Z1) and from the
northbound control and management planes
Sub-steps
Removing IPsec to the FZC southbound interface (Z1) and to the northbound
control, management and user planes
Sub-steps
DN09210645Issue:01C 2016Nokia 51
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
g Note: Usetransactionstobundlemultiplechangesintoonebiggerchange.Use
configurationlockingfeaturetopreventotherusersfrominterferingwithyour
configurationchanges.
Procedure
Further information
Anindividualstaticroutepergatewaycanberemovedwiththefollowingcommand:
set routing [instance <name>] node <name> static-route
<IP_PREFIX|default> nexthop gateway address <address> off
Allroutesforagivensubnetcanberemovedwiththefollowingcommand:
set routing [instance <name>] node <name> static-route
<IP_PREFIX|default> off
Fornodeswheretheroutingdaemonisnotdeployed,theMTUsizeandsourceIP
addresscanbesetforthedefaultstaticrouteusingthefollowingcommands:
set routing [instance <name>] node <name> static-route
<IP_PREFIX|default> mtu <mtu-size>
set routing [instance <name>] node <name> static-route
<IP_PREFIX|default> source <IP-address>
52 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
Therejectandblackholetyperoutesarecreatedwiththefollowingcommands:
set routing [instance <name>] node <node> static-route
<IP_PREFIX|default> nexthop reject
set routing [instance <name>] node <node> static-route
<IP_PREFIX|default> nexthop blackhole
Further information
DN09210645Issue:01C 2016Nokia 53
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
Detailsoftheparametersoftheroutingcommandareshowninthetablebelow.
Table 4 Parametersforconfiguringstaticroutes
g Note: Thisparameteris
supportedonlyfornodes
inwhichtheRouting
Daemonisnotdeployed.
g Note: Thisparameteris
supportedonlyfornodes
inwhichtheRouting
Daemonisnotdeployed.
54 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
Table 4 Parametersforconfiguringstaticroutes(Cont.)
Thehigherpriority(lowervalue)
nexthopsarepreferred.
Switchingovertothenextroute
inthelisthappensonlyifthe
interfacefails.Itdoesnot
happenfornon-reachablenext
hopsiftheinterfaceisstillup.If
thepriorityisthesameandthe
interfaceisup,itwillbean
equalcost,multipathroute.
g Note: Thisparameter
acceptseitherthe
numericvalueorthe
valuedefault.Ifthe
valuedefaultisused,
thenthevalueof
bfd-tx-intervalis
settoadefaultvalueof
1000ms.
g Note: Thisparameter
acceptseitherthe
numericvalueorthe
valuedefault.Ifthe
valuedefaultisused,
thenthevalueof
bfd-rx-intervalis
settoadefaultvalueof
1000ms.
DN09210645Issue:01C 2016Nokia 55
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
Table 4 Parametersforconfiguringstaticroutes(Cont.)
g Note: Thisparameter
acceptseitherthe
numericvalueorthe
valuedefault.Ifthe
valuedefaultisused,
thenthevalueof
bfd-detect-multis
settoadefaultvalueof
4.
56 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
(stratum1)aresynchronizeddirectlytocoordinateduniversaltime(UTC)byradio,
satellite,ormodem.Thesecondaryservers(stratum2)aresynchronizedtotheprimary
servers.Thesecondaryserversareusuallylocatedinanoperator'sorInternetservice
provider'snetwork.
ThesystemautomaticallyselectsthebesttimesourcefromthenetworkofNTPservers
andautomaticallyadjuststhepollingrate,thatis,howoftenthetimestampisrequested.
Theminimumpollingintervalis16secondsandthemaximumpollingintervalis1024
seconds.
InasinglenodedeploymentNTPisonlyusedtoguaranteetheaccuracyofthetime
stampsinthelogs,alarmsandreportsgeneratedbytheplatform.Iftherearenoexternal
serversdefined,thesystemusesthetimeinformationstoredintheinternalhardware
clock.
g Note: IntheZoneeNB,theFlexiZoneControlleractsasNTPserverforitsFlexiZone
AccessPoints.
Procedure
DN09210645Issue:01C 2016Nokia 57
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
Example:
1. AssignIPv4addresses10.20.30.40and10.20.30.50ofexternalNTPservers
byenteringthefollowingcommand:
add networking-service ntp forwarder 10.20.30.40 forwarder
10.20.30.50
2. Verifythattheconfigurationwasassignedcorrectly.Enterthefollowingcommand:
show networking-service ntp
Theprintoutinthisexampleisasfollows:
forwarder: 10.20.30.40
forwarder: 10.20.30.50
Further information
Table5:ParametersforNTPconfigurationshowstheparametersfornetworking-
service dnscommands:
Table 5 ParametersforNTPconfiguration
58 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
DNSserversareorganizedinahierarchicalstructureconsistingofmasterDNSservers
andforwardingDNSservers.MasterDNSserverscontainthezoneinformationin
nonvolatilememory.AzoneisasubsetoftheDNSnamespacethatismanagedbya
specificDNSserver.AmasterDNSserverthatcontainsthecompleteinformationfor
aparticularzoneiscalledtheauthoritativeDNSserverforthatzone.
ForwardingDNSserversloadthezoneinformationfromaDNSserverhigherupinthe
hierarchy(eitheramasterserveroranotherforwardingserver).Thisreplication
processiscalledzonetransfer.
EveryhostinanyIPnetworkisequippedwitharesolver,aDNSclientthatisableto
retrieveinformationfromaDNSserver.Anapplicationthatneedstofindamapping
betweenadomainnameandanIPaddressusestheresolvertoqueryanappropriate
DNSserver.BesidessendingqueriestoDNSservers,resolversalsointerpretthe
responsesreceivedfromtheDNSserversbeforereturningtheresultstothe
applications.
Inthesimplestformthedomainnamesystem(DNS)isconfiguredbyassigningtheIP
address(es)oftheexternalDNSserver(s)tothesystem.Forredundancy,onetothree
externalDNSserverscanbeusedbythesystem.
g Note: IntheZoneeNB,theFlexiZoneControlleractsasDNSserverforitsFlexiZone
AccessPoints.
Procedure
DN09210645Issue:01C 2016Nokia 59
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
Example:
Assigntheaddresses10.20.30.41and10.20.30.51forexternalDNSserversby
enteringthefollowingcommand:
add networking-service dns forwarder 10.20.30.41 forwarder 10.20.30.51
Verifythattheconfigurationisassignedcorrectly.Enterthefollowingcommand:
show networking-service dns
Example:
Assigntheaddress10.20.30.61andremovetheaddress10.20.30.51ofexternal
DNSserversbyenteringthefollowingcommand:
set networking-service dns add-forwarder 10.20.30.61 delete-forwarder
10.20.30.51
Verifythattheconfigurationisassignedcorrectly.Enterthefollowingcommand:
show networking-service dns
Further information
Table 6 ParametersforDNSconfiguration
add-forwarder ThisparameteraddsanIP
<forwarder_address> addressofanexternalDNS
server.
delete-forwarder ThisparameterremovesanIP
<forwarder_address> addressofanexternalDNS
server.
60 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
Purpose
Thecorrectconfigurationofanremoteuserinformationmanagement(RUIM)serviceis
requiredfortheFlexiZoneControllerO&Mintegtation.
Procedure
Sub-steps
Step result
Youshouldsee/RuimReplicatorlistedintheinterfacedata:
IP addresses in default instance:
nbmplane
address : 10.10.40.1/24
owner : /FCPU-0
user : /SSH /Ne3sAgent /ClusterDNS /ClusterNTP
/RuimReplicator
DN09210645Issue:01C 2016Nokia 61
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
primary-configroot- dn Primaryconfigurationinformationrepositorylocation
pathinNMSinthedistinguishednameformat.
primary-peopleroot- Primaryaccountinformationrepositorylocationpathin
dn NMSinthedistinguishednameformat.
primary- SpecifiestheconnectionmodetotheprimaryNMS,with
serverconnection- thefollowingoptions:
mode
tls Sendandreceivedataencrypted
usingTLS.
plain-text Sendandreceivedatainplaintext,
includingRUIMpassword.
try-tls Defaultmode:connectionisfirst
triedwithtlsmode,iftheconnection
failsaplain-textconnectionis
stablishedinstead.
primary-server-ip PrimaryNMSLDAPserverIPaddress.
primary-server-port PrimaryNMSLDAPserverport.Thedefaultvalueof
thisparameteris"389".
primary- Definesthecertificationverificationpolicythatisapplied
serververification- whenconnectingtotheprimaryNMS,withthefollowing
policy options.
full Theserver'scertificateisverified.If
therequiredtrustedcertificatesare
notprovided,thenthesessionwill
notbeestablished.
full-except- Sameasthefullmode,exceptthat
hostname- thehostnamecheckisomitted.
check
ignore Thesessionwillbeestablished
withoutverifyingthecertificates.
secondary-configroot- SpecifiesthesecondaryNMSconfigurationinformation
dn repositorylocationpathinNMSinthedistinguished
nameformat.
secondary-peopleroot- Thisparameterspecifiesthesecondaryaccount
dn informationrepositorylocationpathinNMSinthe
distinguishednameformat.
secondary- SpecifiestheconnectionmodetothesecondaryNMS,
serverconnection- withthefollowingoptions:
mode
tls Sendandreceivedataencrypted
usingTLS.
plain-text Sendandreceivedatainplaintext,
includingRUIMpassword.
62 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
try-tls Defaultmode:connectionisfirst
triedwithtlsmode,iftheconnection
failsaplain-textconnectionis
stablishedinstead.
secondary-server-ip SecondaryNMSLDAPserverIPaddress.
secondary-server-port SecondaryNMSLDAPserverport.Thedefaultvalueof
thisparameteris"389".
secondary- Definesthecertificationverificationpolicythatisapplied
serververification- whenconnectingtothesecondaryNMS,withthe
policy followingoptions.
full Theserver'scertificateisverified.If
therequiredtrustedcertificatesare
notprovided,thenthesessionwill
notbeestablished.
full-except- Sameasthefullmode,exceptthat
hostname- thehostnamecheckisomitted.
check
ignore Thesessionwillbeestablished
withoutverifyingthecertificates.
Step example
Sub-steps
Step example
Primary NMS LDAP Server Configuration
IP address : 10.10.40.5
Port : 389
Config location in NMS : cn=FlexiPlatform4,
ou=LDAPConfData,
ou=ruim,
ou=region-911080,
DN09210645Issue:01C 2016Nokia 63
CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
ou=regions,
ou=netact,
dc=noklab,
dc=net,
dc=localdomain
Account location in NMS : ou=people,
ou=accounts,
ou=region-911080,
ou=regions,
ou=netact,
dc=noklab,
dc=net,
dc=localdomain
Connection mode : plain-text
Verification policy : ignore
Step example
show user-management ruim nms-ldap-account user 111111
password test123
Sub-steps
Step example
NMS LDAP Username : uid=111111,
ou=People,
ou=accounts,
ou=region-911080,
ou=regions,
ou=netact,
dc=noklab,
dc=net,
64 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughSCLI/
FEWS
dc=localdomain
NMS LDAP Password : test123
Purpose
Disablingthephysicalmanagementportisrecommendedinordertominimizesecurity
risksatZoneeNBdeployments.
g Note: ThisprocedureshouldonlybecarriedoutafterallSCLI/FEWScommissioning
stepshavebeensuccessfullycompleted.ItshouldbecarriedoutthoughaSSH
session.ItisrecommendedtowaituntiltheentireZoneeNBhasbeencompletely
commissioned.
Disable the Flexi Zone Contoller MGMT port by entering this command:
set flexizone mgmt disable
Enable the Flexi Zone Contoller MGMT port by entering this command:
set flexizone mgmt enable
DN09210645Issue:01C 2016Nokia 65
IntegratingFlexiZoneControllertoNetActthroughthe CommissioningFlexiZoneController
NES3link
TheintegrationoftheFlexiZoneControllertoNetActthroughtheNE3S/WSinterfaceis
documentedseparatelyintheIntegrating Flexi Zone Controller to NetActdocument
(DN09188976).
66 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
BeforethecommissioningoftheFZCLTEstackcanbegin,itisnecessarytoverify
softwarecomponentsviaSCLI/FEWScommissioning.Seeformoreinformation.
NokiaBTSSiteManagerisaJavabasedapplicationusedtocommissionandmaintain
BTSandFlexiTransportelements.
TheBTSSiteManagercanbeusedinconnected,snapshot,orcreate commissioning
filemode.
YoucanconnecttotheBTSsitelocallyorremotely.Localconnectionmeansdirect
connectionfromaPCwithBTSSiteManagertotheBTSusing10baseTEthernetcable
withRJ-45connector.Remoteconnectioncanbeestablishedthroughdata
communicationnetwork(DCN).Increate commissioning filemodeyoucancreatea
commissioningfilewithoutaconnectiontotheBTSsite.
Nokia BTS Site Manager Online Help
ThehelpsysteminNokiaBTSSiteManagerisavailablethroughtheHelpmenuand
fromthesoftwareascontext-sensitivehelp.
DN09210645Issue:01C 2016Nokia 67
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
Makesurethatyourcomputermeetsthesystemrequirementslistedinthefollowing
table.
Table 7 SystemHWandSWrequirementsforBTSSiteManager
Item Specification
Processor Minimum:1GHz
Recommended:2GHzdualcore
Memory Minimum:1GB
Recommended:2GB
Harddiskspace 260MB
Ethernetconnection 10/100/1000Mbit/sEthernetcard
Communicationcable(EthernetcablewithRJ-45connector)
Display 1024x768
Pointingdevice Mouse,touchpad,trackball,orequivalentwithtwoclickbuttons
CD-ROMdrive(for Optional
installation)
Printer Optional
Operatingsystem MicrosoftWindowsXP/Vista/7/8
WindowsServer2003and2008
RedHatEnterpriseLinux5/6ESGNOMEdesktop(glibc-2.12-1.107ornewer)
Procedure
2 If you have BTS Site Manager running on your PC, close it before starting the
installation.
68 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
b) UsethefollowingcommandlinestoinstallBTSSiteManager:
1. chmod775nameofthe.bin.Notethatifyouareusing64-bitLinuxOSthefile
nameisinformnameofthe_x64.bin.
2. ./nameofthe.binfile
c) ClicktheNextbuttontocompletetheinstallationwhentheinstallationwindow
popsup.
4 Click Next, and read and accept the terms of the license agreement.
5 Click Next.
DefinethelocationwheretoinstalltheBTSSiteManager.Ifyouhaveearlier
versionsoftheBTSSiteManageronyourPC,youneedtoremovetheinstalled
versionsbeforeyoucanchangethelocation.InthiscaseClean installationmustbe
used.
DonotenterdoublespacesintheinstallationpathasBTSSiteManagercannotbe
thenuninstalled.
ItisnotrequiredtoremoveearlierversionsoftheBTSSiteManagerwhenanew
versionisinstalled.ThecorrectBTSSiteManagerversionisselectedautomatically
whentheconnectiontotheBTSisestablished.
IftheinstallationoftheBTSManagerisunsuccessful,usetheClean installation
optiontoremoveallBTSSiteManagerversionsfromyourPCandstartthe
installationagain.
6 Click Next, and inspect the summary information for the installation procedure.
7 Click Install.
TheBTSSiteManagerinstallerinstallsthesoftwareinthespecifiedlocation.
8 Click Finish.
BTSSiteManagerinstallerclosesandyoucanusetheBTSSiteManager(see
Launching BTS Site Manager).
IfthePCisconnectedtotheFSMLMPport,specifyyourPC'snetworksettingsto
matchthefollowingsettings:
DN09210645Issue:01C 2016Nokia 69
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
IPaddress:192.168.255.130
Subnetmask:255.255.255.0
IfyouwanttoestablishaconnectiontotheBTSsitelocally,connectthePCtothe
FlexiZoneControllerLANport1usingatwistedpairEthernetcablewithanRJ-45
connector.Inaremoteconnection,theconnectionisestablishedviaDCN(Data
CommunicationNetwork)network.
Procedure
Figure 3 TaskSelectionview
2 If you want to establish a local connection, select the Local option from the IP
Address list.
IfyouwanttoestablishaconnectiontotheBTSsitelocally,connectthePCtothe
FlexiZoneControllerLANport1usingatwistedpairEthernetcablewithanRJ-45
connector.
3 If you want to establish a local connection, select the Local option from the IP
Address list.
IfyouwanttoestablishaconnectiontotheBTSsitelocally,connectthePCtothe
FlexiZoneControllerLANport1usingatwistedpairEthernetcablewithanRJ-45
connector.
70 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
g Note: TheFTMwebinterfaceisnotsupportedifyouareusingFSMFandWindowsXP
togetherwithanyInternetExplorerversion.
6 Click Connect.
TheprogressoftheoperationisdisplayedintheTaskSelectionview.
IfmultipleversionsofBTSSiteManagerareinstalledonthePC,theappropriate
BTSSiteManagerversionisselectedautomatically.
Whentheconnectionisestablished,theTaskSelectionviewclosesandtheBTSSite
Managermainviewopens.
Ifyoureceiveamessagewiththetext"TheBTScertificateisself-signed",clickthe
AcceptbuttontoconnecttotheBTS.
g Note: DonotchangeWindowsDateandTimesettingsafterlaunchingBTSSite
ManagerorestablishingaconnectiontoBTS.DateandTimechangemaycrashBTS
SiteManager.
1. NetActupgrade
2. OMSupgrade
3. eNBupgrade.
DN09210645Issue:01C 2016Nokia 71
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
g Note: ThesoftwarefortheFlexiZoneControllerandFlexiZoneAccessPointsare
includedinthesamesoftwarepackagefortheBTSsitemanagerandcannotbe
upgradedseparately.
UpdatingtheBTSsitesoftwareisoptional.YoushoulddoitonlyiftheBTSdoesnot
havetherequiredsoftwareversion.NotethatifyouareupdatingjusttheBTSSite
ManagerSW,youmustobtainaseparateinstallationpackageviaoperator-specific
channels.
IntheUpdate SW to BTS SitedialogboxyoucanupdatenewsoftwaretotheBTSsite.
ThisproceduredoesnotdownloadapplicationfilesexistingintheFlexiMultiradioBTS
LTEorFlexiTransportsub-modulethathavethesameversioninformation.Youcanview
thecurrentSWversionsintheSite InformationdialogboxbychoosingtheSoftware
SW Versionsmenuitem.
g Note: IftheBTSsitehasaconnectiontoNokiaNetAct,theNetActwillmanagethe
BTSsiteSW(thatis,willchecktheSWversionand,iffounddifferentthantheSWin
theNetActdatabase,willdownloadnewSWtotheBTSsite).
Procedure
3 Click the Select File button to locate the master file containing the new
software.
TheSelect Build Descriptordialogboxopens.
Locateandselectthemasterfile(TargetBD.xmlorSWpackagezipfile),andclickthe
Openbutton.Ifyouselectthezipfile,thefileswillbedecompressedwhenyouclick
Open.ThenewSWversionisdisplayedintheUpdate SW to BTS Sitedialogbox.
4 Select the Activate SW after update check box to enable the activation of the
new software in accordance with SW updating.
Notethatifyoudonotwanttoactivatethenewsoftwareondownloadingit,youcan
leavetheoptionunchecked.TheSWisthenonlydownloadedtotheBTSsite.If
thereisaneedtoupdatetheSWfilesatonetimeandperformtheactivationlater,
youcanleavetheActivate SW after updatecheckboxunselected.Thisway,only
thefileupdateisperformed,andthesitedoesnotgotoreset.ToactivateSWlater,
gothroughtheupdateprocedureagain,withtheActivate SW after updatecheck
boxselected.ThistimeBTSSiteManagerdoesnotdownloadthefilesthatalready
existinBTSSite.
72 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
6 If you want to view information on the SW download, click the View Report
button.
TheSoftware Update Reportdialogboxopens.
Purpose
Theautoconnectionfeatureenablestheautomatedconnectionofanuncommissioned
BTStoaserverinthenetwork.TheBTScommissioningmaythenbeautomatically
performedviathisserver.
TheprocedureconsistsoftheautomaticestablishmentofIPconnectivitysothatIP-
basedregistrationmessagescanbesent.Usingthelocationinformationofthenewly
installedBTS,OMScancorrelatetheBTSwiththerequiredlogicalconfiguration.
Afterinstallation,theautomaticestablishmentofaconnectionallowsthecommissioning
proceduretobecompletedremotely,withouttheneedforacommissioningengineerto
visitthesite.Operatorsbenefitfromacheaperandquickernetworkrollout.
DN09210645Issue:01C 2016Nokia 73
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
Figure 4 Autoconfigurationdialogbox
ThedialogshownaboveisdisplayedautomaticallywhentheuserestablishestheBTS
SiteManagersessionbeforethestartoftheautoconnectionprocess.Thewhole
autoconnectionprocessisdividedintoseveralphases,andtheirprogressisdisplayedin
theabovedialogbox.
Procedure
1 For the commissioning of Flexi Zone Access Points under a Flexi Zone
Controller, the Identification server IP address needs to be manually added.
TheIdentificationserverIPaddressisaddedviatheEnterAutoconnection
ParametersManuallydialog.
Figure 5 EnterAutoconnectionParametersManuallydialogbox
74 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
Figure 6 AutoconnectionRegistrationdialogbox
Here,theAutoconnectionsiteIDneedstobeprovidedsothattheBTSisidentifiable
totheuppernetworkelementandtheautoconnectionprocesscancontinue.
DN09210645Issue:01C 2016Nokia 75
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
g Note: FromWN6.0onwardstheautoconnectionprocedurestartsautomaticallywhen
theBTSstartsupandinitializestransportconnectionstotheuppernetworkelements.
Duringtheautoconnectionprocedure,thetransportpartforonlinechangesisdisabled.
TheautoconnectionprocedurestopswhenafullconfigurationfileissenttotheBTS
andactivated.
g Note: FlexiZoneControllermustbemanuallyprovisionedusingSCLIbefore
connectingwithBTSSiteManager.SeeCommissioning Flexi Zone Controller
documentformoredetails.
Figure 7 Commissioningoverview
Start
Autoconnection
Localconnect
enabled No
SWupdate
Yes (ifnecessary)
Autoconfiguration
Remoteconnect
enabled No Sitereset
(if SWupdated)
Yes
SWupdate Commissioning
(ifnecessary) file?
Entersite-specific Enterall
Commissioningfile
parameters parameters
downloadfrom
NetAct
Sitereset
Sitereset Commissioning
tests(optional)
Autoconfiguration Commissioning
report report
Integrated
Completed
Performing commissioning
76 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
TheFlexiBTSand/orFlexiTransportsub-module(TRS)arecommissionedwiththe
CommissioningwizardinBTSSiteManager.Commissioningcanbestartedwhenthe
modulesarein'Initialised'state.
ThewizardfeaturesBack,Next,CancelandHelpbuttonsfornavigating.TheNext
buttonconfirmstheenteredparametersandbringsupthefollowingpageineach
commissioningline.TheBackbuttonreversestothepreviouspageinthewizard.The
Cancelbuttoncancelsalltheenteredparametersandclosesthewizard.TheHelp
buttondisplayshelptopic.Allfieldsmarkedwitharedstararemandatoryandneedto
filledinordertoproceedtonextstep.
Formoredetailedinformationonvariouscommissioningparametersandoptions,see
contextsensitivehelptopicforeachpage,byeitherpressingF1keyorusingthehelp
icon.
AllparameterchangesaresenttotheBTSsiteaftergoingthroughalltheavailable
commissioningsteps,intheSend Parametersstepandthesiteresetisdone(if
required),onlythenchangesarereflected.Commissioningparameterscanbesavedin
anXMLfileforfuturereference.
Autoconnection enabled
Thisstepisautomaticiftheautoconnectionfeatureisenabled.Ifautoconnectionisnot
enabled,theconnectiontotheBTSmustbedonelocally.
Thisfeatureenablesautomaticconnectiontoserversinthenetwork,andanautomatic
establishmentoftheO&MconnectionoftheBTStotheO&Msystem.OnlyHWand
cablingneedtobeinstalledatthesite.Thereisnoneedforanexperiencedtelecom
personneltobeatthesiteduringthecommissioningoftheBTS,astheintegrationofa
newlyinstalledBTSisfullyautomated.WhentheBTSispoweredup,itwillautomatically
checktheBTScommissioningstatus,establishIPconnectivity,andretrieveoperator
certificateandtrustanchors(optional).Assoonasthefinalcertificatesareavailable,the
BTSstartsthesecureO&MplaneconnectiontotheNetActframework.
Foradetaileddescriptionoftheautoconnectionfeature,seetheSON Management
document.
Autoconfiguration enabled
Thisstepisautomaticifautoconfigurationisenabled.Ifautoconfigurationisnotenabled,
theBTScanbeconfiguredremotelyusingO&Mconnection,establishedbythe
autoconnectionfeatureorlocally.
TheBTSautoconfigurationfeatureprovidesautomaticcommissioningandconfiguration
ofneworre-homedbasestationsfromaremotenetworkoperationcenterwithminimal
manualintervention.TheautomatedconfigurationisinitiatedbytheeNBauto
configurationagentandcontrolledbytheNetActautoconfigurationapplication,which
belongstotheoverallNetActSONcoordinatorapplication.
Foradetaileddescriptionoftheautoconfigurationfeature,seetheSON Management
document.
SW update
Thisstepcontainsalltheactionsrequiredtoupdateand/ordownloadSWtothe
equipmentortothePCforon-siteequipmentmanagement.Whenautoconnectionand
autoconfigurationareenabled,softwareupdatesarefullyautomated.Whendisabled,
softwaremustbeupdatedlocally(autoconnectiondisabled)orremotely
(autoconfigurationdisabled).
DN09210645Issue:01C 2016Nokia 77
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
Thiscontainsalltheactionsrequiredtosetuptheparametersforcommissioningandfor
integration.Parametersmightincludesoftwareparametersfedinmanuallyorasafile.
Theequipmentspecificproductdocumentationdescribesthedetails.Thesitewillbe
resetafteralltherequiredparametershavebeenenteredusingoneoftheabove
mentionedmethods.
g Note: Whenaparameterisnotmentionedinacommissioninginstruction,the
parametershouldbeleftatitsdefaultvalueeventhoughitispossibletochangeit.
Troubleshooting
Thepurposeoftroubleshootingistorectifytheproblemsfoundbyanalyzingthetest
resultsandperhapsrunningsomefurtherteststoidentifythecauseoftheproblem.
Informationabouttroubleshootinghintsandoptionaltestscanbefoundintheequipment
specificdocumentation.Toavoidrepetition,itisessentialtobeawareofthecurrent
knownproblems.TheTechnicalNotes(TN),ListofGenericFaultsandChange
Deliveries(CD)needtobestudiedfromtimetotimeforlatestinformationaboutknown
problemsandwork-aroundsolutions.
BasedontheexperienceandHWrepairstatisticsaboutthecauseofthefaultsone
majorgroupis'nofaultfound'.Tominimizeunnecessaryshipping,sparewaitingand'no
faultfound'reports,itisessentialtodouble-checkthesuspectedmoduleonemoretime
beforesendingitforrepairs.
Oncethemoduleissuspectedandthereplacementseemstorectifytheproblem,the
originalsuspectedmoduleneedstobetriedoncemore.Inmanycasestheactualreason
whichrectifiedtheproblemispoweroff/on-resetorplugoff/pushinreset.
Whenthemoduleissuspectedorprovenfaulty,theappropriateerrorreportattached
withpossiblelogortestreportfilesisfilled.Thefollowinginformationneedstobeclearly
availableinthereport:
siteandequipmentidentification
78 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
moduleidentification
basedonwhichtestthemodulewassuspectedfaulty
whatothermodulesweresuspected
whatparameterswereused
whatothertestsfailed
whatwastheerror/faultmessage/alarmnumber
whatwastheusedSWversion
responsibleengineer(reportfilledby)andcontactinfo
Incaseofmodulereplacementthesiteinventoryneedstobeupdated.
Reporting
Themostimportantpartofcommissioningisreporting.Withoutrelevantreportsthe
equipmentcanbeconsidereduncommissioned.Thepurposeofreportingistokeep
trackofthelateststatusoftheequipmentandtheworkdone.Somenewequipment
supportsfeatureswherethereportsareautomaticallyupdatedtothemaindatabasein
theNetActsystem,someneedafewmanualsteps,andsomereportsneedtobe
saved/printedmanually.Typicalreportsare:
commissioningreportproducedbytheCommissioningwizardofBTSSiteManager
autoconfigurationreport
snapshotfilesavedbyBTSSiteManager
siteinventoryreport
deliveryreclamationformissingitems
failurereportforeachfaultymodule
failurereportforeachnewproblem
sitedeficiencyreportforoutstandingproblems
siteprogressreport
Someofthereportscanbeusedasatechnicalappendixforsiteacceptancedocuments.
g Note: TheWizardsupportsEnglishalphabetonly.Pleaserememberthiswhenentering
textinthefields.
DN09210645Issue:01C 2016Nokia 79
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
Procedure
2 Select the commissioning target by clicking the appropriate option: BTS and
TRS.
g Note: TheWizardsupportsEnglishalphabetonly.Pleaserememberthiswhenentering
textinthefields.
Procedure
1 Launch BTS Site Manager or, if BTS Site Manager is already running, choose
the File Create File menu item.
TheTask Selection viewopens.
80 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
5 Define the Target elements for which the commissioning file will be created,
and select the commissioning file if you want to use an existing file as a
template for a new file.
DN09210645Issue:01C 2016Nokia 81
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
reducesignificantlythenumberofparametersthatneedtobeconfiguredsothat
basicallyonlysite-specificparameters,suchasBTSname,idandIPaddress,needto
bechanged.
Site-specificparametersareconfiguredontheBTSSettingsandRadioNetwork
Configurationcommissioningpages.
g Note: TheWizardsupportsEnglishalphabetonly.Pleaserememberthiswhenentering
textinthefields.
Procedure
82 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
g Note: TheWizardsupportsEnglishalphabetonly.Pleaserememberthiswhenentering
textinthefields.
Procedure
g Note: IftheselectedfilehasXMLvalidationerrorsorthecommissioningfileversion
differsfromtheversionthatBTSSiteManagerusesorcommissioningfilecontains
othererrors,youneedtogothroughalltheWizardpages.Inthatcasesee
Commissioning - BTS Settingsashowtocontinue.
g Note: TheWizardsupportsEnglishalphabetonly.Pleaserememberthiswhenentering
textinthefields.
DN09210645Issue:01C 2016Nokia 83
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
Procedure
Choosing the View Commissioning menu item or clicking the Commissioning button
on the View Bar opens the Commissioning - Introduction page for starting the
commissioning of the BTS site.
Related topics
Startingmanualcommissioning
Performingtemplatecommissioning
Performingplannedcommissioning
Performingreconfigurationcommissioning
Target
SelectBTS and TRStocommissiontheBTSandTRS.
Commissiong type
84 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
SelecttheTemplate optionifyouareusinganexistingcommissioningfileasatemplate
filethatcontainstheparameterstobeusedinthecommissioning.Youcanchangethe
parameterswhengoingthroughtheWizardpages.Thetemplatecommissioningisused
forsitesthathavesimilarconfigurationsandonlysite-specificparametersdiffer.Select
thePlanned optionifyouhaveacommissioningfilethathasbeenspecificallymadefor
thesiteandcontainsalltheneededparameterstobeusedinthecommissioning.You
needtogothroughtheWizardpagesifplannedcommissioningfilecontainserrors.
SelecttheManual optionifthereisnocommissioningfileavailable.Themanual
commissioningrequiresyoutodefinealltheparametersmanually.Selectthe
Reconfiguration optiontochangetheexistingparametervaluesofanalready
commissionedBTSsitetomakeitfunctionproperly.Inthereconfigurationyoucankeep
theBTSsiteupandrunningwhilechangingitscurrentconfigurationupuntilthepossible
siteresetattheendofthecommissioning.Whetheraresetisrequiredornotdepends
onthechangesdoneduringreconfiguration,thatisifparameterchangesaresuchthat
requireareset.ClickGo to Radio Network Configuration pagetoproceeddirectlyto
RadioNetworkConfigurationpage.ThislinkisenablediftheBTSiscommissionedand
connected.SelectingtheReconfigurationoptionenablestheBackup Commissioning
Filesbutton.ClickingthebuttonopenstheBackup Commissioning Filesdialogbox,
whereyoucansavethecommissioningfilesforbackupbeforechangingthe
configuration.ThedefaultfilenameisBackupCommissioning_<Site
name>_<yyyymmdd>.xmlwhenalltheelement-specificXMLfileswillbesavedtoone
xmlfileandBackupCommissioning_<Sitename>_<element>_<yyyymmdd>.xmlwhen
onlyBTSspecificconfigurationparameterswillbesaved.Thedefaultlocationisthe
folderwhereyouhavesavedbackupfilespreviouslyoryourdefaultworkingfolder(My
Documents,forexample).
Commissioning file
IfyouselectedtheTemplateorPlannedoption,selectthecommissioningfilefromthe
drop-downlistwhereyoucanbrowseforthecommissioningfile(s)byselectingBrowse.
AtooltipdisplaysthepathandfilenameforBTScommissioningfilesunderSelected
files.Clickingthe buttonopensaninformationpanethatdisplaysinformationon
parametersinthepage.Thisbuttonisdisabledifthereisnodataavailable.
Equipment view
TheEquipmentviewshowsthestatesandinformationreceivedfromtheelements.
Next
ClickNext tocontinue.
You can create commissioning files with BTS Site Manager in file mode. When you
select the Create File task in the Task Selection view, BTS Site Manager opens and
displays the Create Commissioning File - Introduction page (see Creating commissioning
file).
Target
SelectBTS and TRSasthetargetelementsforwhichthecommissioningfilewillbe
created.
Commissioning file
DN09210645Issue:01C 2016Nokia 85
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
In the Create Commissioning File - HW Selection page you can define HW configuration
for the FZC site.
IfyouselectedtouseanexistingcommissioningfileasatemplateintheCreate
CommissioningFile-Introductionpage,theEquipment view displaystheHW
configurationfromthecommissioningfile.ThePropertiesviewinHWselectionshows
theunitcapabilities.
Related topics
Creating commissioning file
Add AP Module
SelecttheAPModulefromtheAdd AP ModulelistthatdisplaysallsupportedAP
Modules.YoucanremoveanAPmodulefromthesamelistbyselectingRemoveafterat
leastoneAPhasbeenadded.
86 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
AP ID starts from
EntertheAPIDstartingnumberinthisfield.
AP amount
EnterthetotalnumberofAPsinthisfield.
Copy data from
SelecttheAPfromwhichtocopythedatainthisdrop-downlist.Thelistisenabledif
thereareexistingAPs.
g Note: TheCopyDatafromoptioncopiesallthedata(AP,Cell,etc)oftheexistingAPto
thenewAP.ThisoptionisonlysupportedwhencopyingdatafromanAPthatisthe
sametype.CertaindatamustbeuniquebetweenAPMODsandLNCELsandthiswill
correctedinthevalidationphaseintheRadioNetworkScreenlater.
Add
ClickAddtoaddtheAPsintoHWselection.SelectthenAdd AP Moduletoadd
additionalsAPs,ifrequired.
Next
ClickNexttocontinuethefilecreationbyenteringtherequiredparametersmanuallytask
bytaskguidedbyBTSSiteManager.NotethateventhoughyoulaterreturntotheHW
SelectionpageusingtheBackbutton,youcannotmodifytheHWconfigurationyouhave
selected.TochangetheHWconfiguration,youhavetogototheintroductionpageand
fromthereproceedtotheHWselectionpage.
DN09210645Issue:01C 2016Nokia 87
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
Related topics
Creatingcommissioningfile
Add APs>>
ClickAdd APs>>buttontoenableAddAPModulefunctions.YoucanaddAPsand
assignthemIDsaswellaschoosetheirnumberfortheselectedAPvariant.Clickingthe
Add APs<<buttonagainhidestheAddAPModulefunctions.
Remove APs>>
ClickRemove APs>>toopenalistofAPs.SelecttheAPsyouwanttoremoveby
selectingthecheckboxesasrequired.ThisselectioncanbemadeeitherforallAPsofa
certainvariantorindividually.ClickingtheRemove APs<<buttonhidesthisview.
Add AP Module
SelecttheAPModulefromtheAdd AP ModulelistthatdisplaysallsupportedAP
Modules.
AP ID starts from
EntertheAPIDstartingnumberinthisfield.
AP amount
EnterthetotalnumberofAPsinthisfield.
Copy data from
SelecttheAPfromwhichtocopythedatainthisdrop-downlist.Thelistisenabledif
thereareexistingAPs.
88 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
g Note: TheCopyDatafromoptioncopiesallthedata(AP,Cell,etc)oftheexistingAPto
thenewAP.ThisoptionisonlysupportedwhencopyingdatafromanAPthatisthe
sametype.CertaindatamustbeuniquebetweenAPMODsandLNCELsandthiswill
correctedinthevalidationphaseintheRadioNetworkScreenlater.
Add
ClickAddtoaddtheAPsintoHWselection.SelectthenAdd AP Moduletoadd
additionalsAPs,ifrequired.
Next
ClickNexttocontinuebyenteringtherequiredparametersmanuallytaskbytaskguided
byBTSSiteManager.NotethateventhoughyoulaterreturntotheHWSelectionpage
usingtheBackbutton,youcannotmodifytheHWconfigurationyouhaveselected.To
changetheHWconfiguration,youhavetogototheintroductionpageandfromthere
proceedtotheHWselectionpage.
In the Commissioning - BTS Settings and Create Commissioning File - BTS Settings
pages you can define identification information for the BTS under commissioning.
Related topics
Commissioning-Introduction
BTS ID
EntertheBTSidentifierintheBTSIDfield.TheBTSIDhastobedefinedaccordingto
agreedvalue,whichisusuallydeterminedatthenetworkplanningstage.Donotassign
arbitraryvalueforthisparameter.Note,thatBTSIDinIPNO:btsId(BTSID),MRBTS
(mrbtsId)andLNBTS(lnBtsId)parametersmustallhavethesameBTSIDvaluein
commissioningfile.Ifthevalueischangeditmustbedoneinsitecommissioning.
BTS name
EntertheBTSnameintheBTS namefield(maximumof80characters).
Time zone
SelectthelocaltimezonefromtheTime zonelist.Inthemanualcommissioningandin
thecasethetimezoneisnotreceivedfromthecommissioningfile,thecomputer'stime
zoneisselectedbydefault.
LED visibility control
DN09210645Issue:01C 2016Nokia 89
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
Toggling faults
ClickBlock Toggling FaultstoopentheBlock Toggling Faultdialogbox,whereyoucan
definethetogglingfaultblockingrules.TheBlockTogglingFaultdialogboxcanbeused
toreducetheamountoffaultsintheBTStothereallyimportantonesandtopreventthe
systemfromgettingloadedwithfaultswhicharefillingthefaultviewbutdonotprovide
furtherimportantinformation,faultswhichareraisedandclearedinashortperiodoftime
andwhichdonotgivefurtherinformationforfaultanalysisandfaultlocalization.
Equipment view
TheEquipmentviewdisplaystheHWconfigurationgraphically.
Next
ClickNexttocontinue.
Clicking the Passive Units button in the page or in the Commissioning - BTS Settings
page opens this dialog box, where you can enter information on passive units of the BTS
site.
Related topics
Commissioning-Introduction
Unit Enterthenameofthepassiveunit(maximumof60
characters)orselectitfromthelistintheUnit column.The
listdisplaysthenamesofpassiveunitsreadfromtheBTS
SiteManagermapfile.IfyouselectaNokiapassiveunit
fromthelist,thevaluesforothercontrolsarereadfromthe
file.
Comment EnterthedescriptionofthepassiveunitintheComment
column(maximumof60characters).
Version EntertheversionofthepassiveunitintheVersion column
(maximumof20characters).
Product code Entertheproductcodeofthepassiveunit(maximumof60
characters)orselectitfromthelistintheProduct code
column.ThelistdisplaystheproductcodesofNokia
passiveunitsreadfromtheBTSSiteManagermapfile.If
youselectaproductcodefromthelist,thevaluesforother
controlsarereadfromthefile.
Serial number EntertheserialnumberintheSerial number column
(maximumof60characters).
Delete Selectthecheckboxinthe columnifyouwanttodelete
apassiveunit.
OK ClickOK tosavethechangesandclosethedialogbox
andreturntotheBTS Settings page.
Cancel ClickCancelandreturntotheBTS Settings page.
90 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
In the Commissioning - BTS Settings and Create Commissioning File - BTS Settings
pages you can define synchronization settings for the BTS under commissioning.
Related topics
Commissioning-Introduction
Network synchronization mode
Selectthenetworksynchronizationmodefromthedrop-downlist:Frequency
synchronizationorPhase synchronization.
In the Commissioning - Cell Resources and Create Commissioning File - Cell Resources
pages you can define local cells and assign antennas of Radio Modules to the local cells.
Local Cell Resource (LCR/LCELL) is a concept for defining all hardware that a global cell
(LNCEL) requires in the base station. Local cells are then mapped to global cells
(LNCEL) on commissioning RNW page.
g Note: Localcellidentifiersaredeterminedatthenetworkplanningstage.Itisessential
thatthevalueinputmatchestheexpectedvalueintheradionetworkplan.Youshould
notselectthevaluesarbitrarily.
Related topics
Commissioning-Introduction
DN09210645Issue:01C 2016Nokia 91
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
In the Commissioning - LTE Carriers and Create Commissioning File - LTE Carriers
pages you can define LTE carriers for local cells and those are assigned then
automatically to global cells (LNCEL) and shown as read only information on
commissioning Radio Network Configuration page. The allowed E-UTRAN Absolute
Radio Frequency Channel Number (EARFCN) values for frequency bands are displayed
below the Carrier candidate table. LTE carrier candidates are determined at the network
planning stage. It is essential that the value input matches the expected value in the
radio network plan. You should not select the values arbitrarily.
Related topics
Commissioning-Introduction
92 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
EARFCNforafrequencyband;upto
fourdifferentvaluescanbedefined
foreachfrequencyband.Thenumber
ofdifferentEARFCNvaluesdepends
onthecommissionedconfiguration.
3GPPstandardspecifiesthe
supportedEARFCNvaluesforeach
E-UTRAfrequencyband.The
supportedMHzfrequencybandand
E-UTRAfrequencybandareshown
accordingtotheautodetectedradio
modules.Spacingbetweenthecell's
TXcenterfrequencyandcell'sRX
centerfrequencymustbeinthe
distancewhatcanbecalculatedby
takingintoaccountlowerfrequency
limitsofTXandRXEARFCNlimits.
Example:2100MHz(E-UTRA1).
AllowedTXEARFCNvalues0-599
andallowedRXEARFCNvalues
18000-18599.Spacingvalueisgetby
18000-0=18000.WhenenteringTX
centerfrequency100thenRXcenter
frequencymustbe18100.
EARFCN range ShowstheallowedEARFCNvalues
forthefrequencyband.TheEARFCN
valuemustbeatabandwidth-
dependentdistancefromthelower
andupperlimitsoftheallowedrange.
gNote: Allvaluesincalculation
rulebelowareinEARFCNvalue:
LowerEARFCNlimit:
Minimum3GPPEARFCN
value+LCRx
Planned.Carrier.Bandwidth/2
=LowestEARFCNvaluethat
canbeused.
HigherEARFCNlimit:
Maximum3GPPEARFCN
value-(LCRx
Planned.Carrier.Bandwidth/2
-1)=HighestEARFCNvalue
thatcanbeused.
DN09210645Issue:01C 2016Nokia 93
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
94 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
Next ClickNexttocontinue.
In the Commissioning - Antenna Line Settings and Create Commissioning File - Antenna
Line Settings pages you can define antenna settings.
Related topics
Commissioning-Introduction
DN09210645Issue:01C 2016Nokia 95
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
Related topics
Commissioning-Introduction
96 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
anditssub-levelsandpossiblelist
items.Selectanobject/iteminthe
treetoviewitsRNWparameters.
<MO>/<List Thisfieldliststheparametersofthe
item> selectedMOorlistitem.Parameters
parameters aretakenfromtheexistingBTSsite
commissioningfileandPDDBmeta
data.Ifthedefaultisnotspecifiedin
PDDB,emptyvaluefieldisdisplayed.
Pointingtoparametersnameyoucan
seeparameter'sabbreviatedname
whichistheparameter'snamewhen
theparameterissavedtoBTSsite
commissioningfile.Iftheparameter
alsohasdescriptioninfo,Show more
detailslinkisenabledwhereyoucan
seemoreinformationonthe
parameteraswellasinformationon
parameter'srelationshipstoother
parameters.WhenCompareselection
isenabledyoucancomparethe
contentsoftwomanagedobjects/list
items.
Errors IntheErrorstableatthebottomofthepageyoucanseeif
thereareanyerrorsintheparametersconfiguration.
ClickingaparameterintheParametercolumnpointstothe
parameterinquestionandtheDetailed error description
columndescribestheerrorindetail.IfManagedObjectis
missingfortheparameterinquestionthenclickinga
parameterpointstoparentManagedObjectwhichmustbe
createdfirst.Followtheinstructionstocorrectany
problems.
Type TheTypecolumnshowsthetypeof
error:WarningorError.
Managed TheManaged objectcolumnshows
object thenameoftheobjectforRNW
objects.
Error TheError descriptioncolumnshows
description Incompleteconfigurationformissing
mandatoryparametersandforlogical
checkingandIncorrectparameterfor
incorrectparametervalues.
Parameter TheParametercolumnshowsthe
nameoftheparameter.Clicka
parametertofinditintheparameters
area.
Detailed error TheDetailed error descriptioncolumn
description showsamoredetaileddescriptionof
theerror.
DN09210645Issue:01C 2016Nokia 97
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
Purpose
TheparametertreeviewontheleftoftheBTSSiteManagerRadioConfigurationpage
allowsyoutoselectmanagedobjects(MO)SMOD-1/APMOD-N,inordertoviewand
modifygeneralsettingsoftheAPMOD.YoucandefineAPAutoConfiguration
parametersandothercommonAPMODconfigurationoptions.
Procedure
2 (Optional) Enter the 1 Pulse Per Second (PSS) source line delay.
ThisparameterspecifiesthelinedelayinthecableusedbetweentheGPSantenna
andtheAP.
98 2016Nokia DN09210645Issue:01C
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
g Note: TherearethreetypesofAccessPoint(AP)identityrelatedparametersusedby
thesystemwheneveranAPisconnectedtotheFlexiZoneController(FZC)forthefirst
time.TheFZCrequiresat least onetypeofAPidentityparameterstobeprovisioned
bytheoperatorinordertouniquelymapanAPtooneoftheconfiguredAPMODs.This
inturnallowsthesystemtoassignthepropercellconfigurationtotheresourcesofthe
newlydiscoveredAP.ConfiguringtheFZCwithmorethanonetypeofAPidentity
parametersisalsosupported.
Sub-steps
Step example
SomevalidSiteIDtextstrings:FZC-4,APMOD-22,122CASSST,Floor5
East,Mainlibraryhall-MiskatonicUniversity.
APMODconfiguredlatitude,longitude,altitude
Geolocationtolerance
APsconfiguredtouseGPSasitstimingsourcecanautomaticallyobtaintheir
geographicallocationandwillreporttheirlatitude,longitudeandaltitudetotheFZC
duringAPDiscovery.ThecorrespondinggeographicallocationoftheAPneedstobe
DN09210645Issue:01C 2016Nokia 99
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
provisionedattheFZCviatheAPMODconfiguredlatitude,longitudeandaltitude
parameters.TheGeolocationtoleranceparameterallowstheoperatortospecifythe
amountofdistance(inmeters)allowedbetweentheAPreportedlocationandthe
configuredAPlocation(attheFZClevel)toallowtheFZCtopositivelyidentifythe
APbasedonlocation.
TheuseofgeographicallocationtoidentifyanAPrequireseachAPtobeinstalled
withadedicatedGPSantennawithinanunobstructedviewofthesky.Aremotely
locatedGPSantennawillprovidethelocationofthephysicalantenna,notthe
physicalAP.APDiscoveryviageographicallocationisnotsupportedforindoor
FZAPsandconfigurationswhereAPssharethesameGPSantenna.
Purpose
TheparametertreeviewontheleftoftheBTSSiteManagerRadioConfigurationpage
allowsyoutoselectmanagedobjects(MO)SMOD-1/APMOD-N/APELNK-Xtoviewand
modifyEthernetinterfacesettingsoftheAPMOD.YoucandefinetheAdministrativestate
oftheinterfaceandotherphysicalinterfacepropertiesforEthernetInterfaces.BTSSM
withautomaticallyincludethecorrectnumberofethernetinterfacesbaseduponthe
APMODtypebeingprovisioned.
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
Procedure
1 Select Speed and duplex configuration options for the Ethernet interfaces:
Select from available options
EIF1:
Autodetect
1000Mbit/sFullDuplex
EIF2:
Autodetect
100Mbit/sFullDuplex
1000Mbit/sFullDuplex
EIF3(PortC,applicabletosomeAPMODsonly):
Autodetect
Purpose
TherearetwoseparateBluetoothCommissioningscreenswheretheZoneeNBwide
andperAPMODBluetoothconnectivitysettingscanbeset.
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
Procedure
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
Sub-steps
a) Select the Bluetooth enabled alarm in use check box to enable the alarm.
b) Select the Allow Bluetooth secure simple pairing check box to allow secure
simple pairing.
c) Select the Allow legacy pairing check box to allow legacy pairing.
d) Enter the pairing relationship timeout value (in hours= in the Pairing
relationship timeout field.
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
Sub-steps
b) Select the Allow inquidy scan response check box to allow inquiry scan
response.
d) Enter the legacy pairing OTP mode in the Legacy pairing OTP mode field.
e) Enter the legacy pairing secret parameter in the Legacy pairing secret field.
ThisfieldismandatoryifOTPmodeissetto-2andlegacypairingisallowed.
Otherwisethefieldisoptional.
f) Enter the secure simple pairing secret parameter in the Secure simple
pairing secret field.
Purpose
TheparametertreeviewontheleftoftheBTSSiteManagerRadioConfigurationpage
allowsyoutoselecttheselectthemanagedobject(MO)LNBTS-X/FTM-1/QOS-1toview
andmodifytheQOSsettingappliedforallFZAPs.Youcandefinethefollowing:
PerHopBehaviourqueueweights
MappingsDSCPstoPHBsandPCPbits.
MappingtraffictypestoDSCPs.
Procedure
1 Enter the weight for each Per Hop Behavior queue in the Weight column.
EntertheweightforeachqueueintheWeightcolumn.Thevaluerangeisfrom1to
10000.Thebiggertheweightvalue,themoredatacanbetransportedthroughthe
correspondingqueue.TheweightforExpeditedForwardingcannotbechanged.
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
2 Define the DSCP values for the traffic types in the DSCP column.
Thedefaultmappingisasfollows:
TrafficType DSCP (PHB)
----------------------
CPLANE: 46
ICMP: 10
IKE: 34
MPLANE: 34
SPLANE: 46
BFD1 to BFD16: 34
HighPrioICMPv6:56
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
3 Define the mapping of DCSPs to PHBs and PCP bits, entering the DSCP and
VLAN priority values for the traffic types
SelectthePerHopBehavior(Queue)foreachtraffictypefromthelistinthePerHop
Behaviorcolumn.Ifyouwishtodeleteanentryfromthetable,selectthe
correspondingcheckboxintheDeletecolumn.
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
Purpose
TheparametertreeviewontheleftoftheBTSSiteManagerRadioConfigurationpage
allowsyoutoviewandmodifytheTimingoverPacketsettings.
Procedure
Selectthemanagedobject(MO)SMOD-1/APMOD-N/TOPB-1/TOPF-1toview
andmodifytheTimingoverPacket,Frequencysynchronizationsettingsofthe
APMOD.
Selectthemanagedobject(MO)SMOD-1/APMOD-N/TOPB-1/TOPP-1toview
andmodifytheTimingoverPacket,Phasesynchronizationsettingsofthe
APMOD.
YoucandefinethePacketCommunicationsMode,eitherIPUnicastorEthernet
Multicastandvarioussettingassociatedwiththeselectedmode.Thesesettings
shouldmatchthesettingsontheTimingoverPacketmasterconfiguredinthe
network.
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
3 Select how often the synchronization message is to be sent by the Timing over
Packet master.
YoucanselecttwopossiblevaluesfortheLogMeanSynchronizationValue:
-6:64synchronizationmessagespersecond
-7:128synchronizationmessagespersecond
g Note: ThisvalueisonlyusedwhentheTimingoverPacketCommunicationsMode
settingofIPUnicastisselected.WhentheTimingoverPacketCommunicationsMode
settingofEthernetMulticastisusedadefaultvalueof16times/secondisusedinthe
APMOD.
5 Enter the PTP domain number value in the PTP domain number field.
Therangeis0...255.ThedefaultvalueisasfollowsdependingontheTimingover
PacketCommunicationsMode:
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
IEEE-1588-2008:0
ITU-TG.8265OptI/II:4
ForIPunicastcommunicationmodeitisIEEE1588partialonpathsupportandfor
EthernetmulticastcommunicationmodeitisITU-TG.8275.1fullonpathsupport.
g Note: ThisvalueisonlyusedwhentheTimingoverPacketCommunicationsMode
settingofEthernetMulticastisselected.
In the Commissioning - Send Parameters page you can send the parameters entered
during the commissioning procedure to the BTS site.
Related topics
Commissioning-Introduction
Send WhenBTSandisincommissionedstateandRNWstatus
iscorrectyoucanchoosefromtheSend:Only changes
(may require reset)andSend:All parameters (requires
reset)radiobuttonsthelevelwithwhichtosendthe
changedparameterinformation.ClicktheView File
Changes...buttontoopentheView commissioning
parametersdialogboxwhereyoucanviewthechanged
parameterinformation.Theradiobuttonsareshownas
disabledandAllparameters(requiresreset)radiobuttonis
selectedbydefaultwhen:
BTSIDischangedincommissioning
LNCELID(s)ischangedincommissioning
BTSiscommissioned,butradionetworkconfiguration
contentisinvalid
Commissioningfileisnotreceivedfromthe
commissionedBTSsite
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
Parameters,whichcanbemodifiedonlyinobject
creation,havebeenchanged.
WhenAll parameters (requires reset)radiobuttonis
selected,allparametersfromBTSandRNWpartof
commissioningfilearesenttotheBTS.WhenOnly
changes (may require reset)-radiobuttonisselected,
changesfromBTSandRNWpartofcommissioningfile
aresenttoBTSsite.
View File Changes... ClicktheView File Changes...buttontoopenthe
Commissioning - View File Changesdialogboxwhereyou
canviewthechangedparameterinformation.
Send Parameters ClickSend Parameterstosendthecommissioning
parameterstotheBTSsite.NotethatoncetheSend
Parametersbuttonisclickedtheprocesscannotbe
canceled.ClickingtheCancelbuttoninthecommissioning
wizardpagescancelsthecommissioningwizard.
Transfer status Showsthetransferstatusofsendingthecommissioning
parameterstotheBTSsite.
Elapsed time Showstheelapsedtimeofsendingthecommissioning
parameters.
View Parameters ClickView ParameterstoopentheCommissioning - View
Parametersdialogbox,whereyoucanviewthe
parametersenteredduringthecommissioning.
Save Parameters ClickSave ParameterstoopentheSave Commissioning
Parametersdialogbox,whereyoucandefinethefilename
andselectthelocationforthefile.Thedefaultfilenameis
Commissioning_<Sitename>_<yyyymmdd>.xmlwhen
commissioningthewholesiteandCommissioning_<Site
name>_<element>_<yyyymmdd>.xmlwhen
commissioningoneelement.Thedefaultlocationisthe
folderwhereyouhavesavedthepreviouscommissioning
parametersfileoryourdefaultworkingfolder(My
Documents,forexample).Savingtheparameters
producesacommissioningfilethatcanbeusedinthe
templateandplannedcommissioning.
Equipment view TheEquipmentviewdisplaystheHWconfiguration.
Next ClickNexttocontinue.
In the Commissioning - Additional Site Settings page you can manage the local user
account.
Related topics
Commissioning-Introduction
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
certificatefiles,checkcertificatestatusanddelete
certificatefiles.
Equipment view TheEquipmentviewdisplaystheHWconfiguration.
Next ClickNexttocontinue.
Clicking the View Parameters button in the Commissioning - Send Parameters page
opens the Commissioning - View Parameters dialog box. The commissioning parameters
are split into sublevels, which you can expand or collapse by clicking the arrows. You
can expand all at the same time by clicking the button or collapse all by clicking the
button. You can view the entered parameters by scrolling down the list. You can save
the parameters by clicking the button.
Related topics
Commissioning-Introduction
Clicking the View File Changes... button in the Commissioning - Send Parameters page
opens the Commissioning - View File Changes dialog box where you can view
information on the changed parameters. The commissioning parameters are split into
sublevels, which you can expand or collapse by clicking the arrows. You can expand all
at the same time by clicking the button or collapse all by clicking the button. You
can view the entered parameters by scrolling down the list. You can save the parameters
by clicking the button.
Related topics
Commissioning-Introduction
In the Commissioning - Commissioning Report page you can view information defined
during the commissioning. The report is split into sublevels, which you can expand or
collapse by clicking the arrow. You can expand all levels at the same time by clicking the
button or collapse all levels by clicking the button. You can view the contents of
the report by scrolling down the list. The Commissioning Report contains the following
information:
Report identification:Date,Author,CommissioningType,CommissionedElements,
NTPconnectionandBTSState
CommissioningFlexiZoneControllerthroughBTSSite CommissioningFlexiZoneController
Manager
In the Create Commissioning File - Summary page you can view the parameters entered
during the file creation and save them in a commissioning file that can then be used in
the Template or Planned commissioning. The parameters are split into sublevels, which
you can expand or collapse by clicking the arrows. You can expand all levels at the same
time by clicking the button or collapse all levels by clicking the button. Click the
button to open the Save Commissioning File dialog box, where you can define the file
name and the location for the file. When the file is created for the whole BTS site, the
default file name is <Site name>.xml. When the file is created for the BTS, the default file
name is <Site name>_<element>.xml. The default location is the folder where you have
saved the previous commissioning files or your default working folder (My Documents,
for example).
Related topics
CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
Creatingcommissioningfile
Finish ClickFinishtofinishthecommissioningfilecreation.After
thatyoucanselectwhetheryouwanttocreateanother
commissioningfileornot.Ifyouwanttocreateanotherfile
forthesameconfiguration,selecttheUse Current
Configurationoption,andclickCreate.Thefirstpage
opens.Ifyouwanttocreateanotherfilefromscratch,
selecttheDefine New Configurationoption,andclick
Create.TheCreate Commissioning File - Introduction
pageopens.Ifyoudonotwanttocreatemorefiles,click
Exit.BTSSiteManagerclosesandtheTask Selection view
opens.
IntegratingFlexiZoneControllertoNetActthroughthe CommissioningFlexiZoneController
NWI3link
TheintegrationsolutionoftheFlexiZoneControllerthroughtheNWI3interfaceisthe
sameasthatofFlexiMultiradioBTSLTE.TointegrateFlexiZoneControllerApplication
toNetAct,refertotheIntegrating Flexi Multiradio BTS LTE to NetActdocument
(DN09118114).
CommissioningFlexiZoneController IntegratingFlexiZoneAccessPointstotheFlexiZone
Controller
TheprocessinwhichtheFZCidentifiesanewlyconnectedFZMBTSandmapsitasa
FZAPtooneoftheAccessPointModuleIdentifiers(APMODs)isreferredtoasAP
Discovery.TherearethreetypesofAccessPoint(AP)identityrelatedparametersthat
canbeusedbythesystemwheneveranAPisconnectedtotheFlexiZoneController
(FZC):
AutoConnectionHardwareID
AutoconfigurationSiteID
GeoCoordinatesoftheAPMOD
TheFZCrequiresatleastonetypeofAPidentityparametertobeprovisionedbythe
operatorinordertouniquelymapanAPtooneoftheconfiguredAPMODs.
BoththeintroductionofanAutoconfigurationSiteIDandthemonitoringoftheAP
discoveryprocessareproceduresthatmaybecarriedouteitherviaBTSSMorvia
WebUI:
AlocalBTSSMconnectionwiththeFlexiZoneMicro,canbeestablishedeitherby:
connectingthePCtotheBH2portusingatwistedpairEthernetcablewithan
RJ-45connector.
establishingabluetoothconnection.
AWebUIinterfaceisavailableiftheFlexiZoneMicroisrunningFL15A/TL15ASWor
later.
ToestablishaBTSSMconnectionwiththeFlexiZoneMicrolocally,connectthePCto
theBH2portusingatwistedpairEthernetcablewithanRJ-45connector,orestablisha
bluetoothconnectioninstead.AlternativelyandifFlexiZoneMicroisrunningrelease15A
orlaterSWtheWebUIinterfacecanbeusedinstead.
IntegratingFlexiZoneAccessPointstotheFlexiZone CommissioningFlexiZoneController
Controller
Figure 8 IntegratingFZAPstoaZoneeNB
FZC
Zone
Integration
g Note: ItisrecommendedtoactivateZ1IPSecprotectionbeforeinitiatingFZAP
integration.
OncetheFZAPintegrationhasbeencompleted,theAPoperationalstateshouldbe
verifiedviaNetActortheFZCBTSSMinterface.
IncasetheFZAPfunctionalstateappearsasUnknown,theAPhasnotbeen
successfullydiscoveredbytheFZC:
1. VerifytheconfigurationofthecorrespondingFZAPAPMOD.
2. IfIPSecprotectionhasbeenactivatedontheZ1interface,followtheprocedure
describedinVerifyingIPSectunnelinginFlexiZoneController.
3. Iftheissuespersist,contactNokiasupport.
CommissioningFlexiZoneController IntegratingFlexiZoneAccessPointstotheFlexiZone
Controller
Purpose
ThisprocedureisnecessaryonlyiftheAutoconnectionSiteIDisbeingusedasthe
identityparameterfortheFZM/FZAPintheFZC.
Before you start
AconnectionbetweenBTSSMandtheFlexiZoneMicroisestablished.
Procedure
2 Enter the Autoconnection Site Id. See figure for the Autoconnection
Registration dialog screen.
Figure 9 BTSSMAutoconnectionRegistrationdialogscreen
IntegratingFlexiZoneAccessPointstotheFlexiZone CommissioningFlexiZoneController
Controller
Procedure
Result
OnceAutoconfigurationiscompletetheFZCwillhaveoptionallydownloadednewSWto
thedevice,sentandactivatedtheconfigurationfileandtheFZMisnowconsidered
integratedtotheFZCasaFZAP,readytoprovideservicewithintheZoneeNB.
Example
Figure 10 BTSSMAutoconfigurationdialog
Previously commissioned FZM BTS need to be uncommissioned prior to their Zone eNB
integration.
Purpose
IftheAutoconnectionRegistrationDialogisgreyedoutwhenaccessingthe
Autoconfigurationdialog,itcouldbethattheFlexiZoneMicrohasbeenpreviously
configuredandcommissionedforoperationatadifferentsite.
CommissioningFlexiZoneController IntegratingFlexiZoneAccessPointstotheFlexiZone
Controller
Perform a configuration reset when the Flexi Zone Micro is running release
15A or later SW.
Sub-steps
Figure 11 BTSSMConfigurationresetdialog
IntegratingFlexiZoneAccessPointstotheFlexiZone CommissioningFlexiZoneController
Controller
Perform a configuration reset when the Flexi Zone Micro is running a software
version previous to release 15A.
Sub-steps
4 Press and hold the reset button on the Flexi Zone Micro BTS for more than
5 seconds.
CommissioningFlexiZoneController IntegratingFlexiZoneAccessPointstotheFlexiZone
Controller
Procedure
Figure 13 WebUIConfigureSiteIDdialog
IntegratingFlexiZoneAccessPointstotheFlexiZone CommissioningFlexiZoneController
Controller
TheFlexiZoneMicroneedstobeusingFL15A/TL15ASWorlater.Theprocedure
assumesthataWebUIinterfacetotheFlexizoneMicroisestablished.
Procedure
Figure 14 AutoConnection&Configurationprogressdialog
Result
OnceAutoConnection&ConfigurationiscompletetheFZCwillhaveoptionally
downloadednewSWtothedevice,sentandactivatedtheconfigurationfileandtheFZM
isnowconsideredintegratedtotheFZCasaFZAP,readytoprovideservicewithinthe
ZoneeNB.
Previously commissioned FZM BTS need to be uncommissioned prior to their Zone eNB
integration.
Purpose
IftheFlexiZoneMicroisinthecommissionedstatewithaconfigurationforapriorsite
andnotconnectingtotheFlexiZoneControlleritmaybenecessarytoissuea
configurationreset.
Before you start
TheFlexiZoneMicroneedstoberunningrelease15ASWorlater.AWebUIinterfaceto
theFlexiZoneMicroisestablished.
CommissioningFlexiZoneController IntegratingFlexiZoneAccessPointstotheFlexiZone
Controller
Procedure
1 Perform a configuration reset when the Flexi Zone Micro is running release
15A or later SW.
Sub-steps
Figure 15 WebUIConfigurationresetdialog
IntegratingFlexiZoneAccessPointstotheFlexiZone CommissioningFlexiZoneController
Controller
Procedure
2 Check the security associations (SA) and SPI of the IPSec Tunnel.
setkey -D
Step result
BoththeSAandtheSPIshouldbepopulated.AsuccessfulIPSectunnelshould
haveapairSA.
Example
IftheruleconfiguredintheFZCisasfollows:
Rule name Owner Src addr Dst addr
Prot VPN Src port Dst port Prio
------------------------ -------- ------------------ ------------------
---- ---------- -------- -------- ----
PROTECT-SB-ALL /FZBU-0 192.168.55.1/32 192.168.55.2/32
0 ZONEVPN 0 0 NA
Theoutputoftheprocedureshouldresemblethefollowingprintout:
#setkey -D
192.168.55.1 192.168.55.2
esp mode=tunnel spi=3332365992(0xc69fdea8) reqid=2(0x00000002)
E: aes-cbc a6c73795 681f901f 307ca099 9e26dea9
A: hmac-sha1 463eace7 aad61a93 e5df41df 74778a65 4ae0ddf2
seq=0x00000000 replay=32 flags=0x11000000 state=mature
created: Jan 21 21:55:17 2015 current: Jan 21 22:15:33 2015
diff: 1216(s) hard: 86400(s) soft: 72430(s)
last: hard: 0(s) soft: 0(s)
current: 433508(bytes) hard: 0(bytes) soft: 0(bytes)
allocated: 2165 hard: 0 soft: 0
sadb_seq=1 pid=24267 refcnt=0
vrfid=0 xvrfid=0
192.168.55.2 192.168.55.1
esp mode=tunnel spi=3349187904(0xc7a08d40) reqid=2(0x00000002)
E: aes-cbc e51b772e 5bd95864 684953f7 f6b785e8
A: hmac-sha1 8f57be67 9899af39 fdd2f5e8 5700a619 0e28b27d
seq=0x00000000 replay=32 flags=0x10000000 state=mature
created: Jan 21 21:55:17 2015 current: Jan 21 22:15:33 2015
diff: 1216(s) hard: 86400(s) soft: 75731(s)
last: hard: 0(s) soft: 0(s)
current: 11575032(bytes) hard: 0(bytes) soft: 0(bytes)
allocated: 16653 hard: 0 soft: 0
sadb_seq=0 pid=24267 refcnt=0
vrfid=0 xvrfid=0
Post requisites
IncasetheSAorSPIappearempty,thenegotiationisnotsuccessful.Pleasecontact
NokiaSupport.
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
w BackupISOismandatoryforrestoringtheentiresystemandre-commissioningthe
controller.TheoperatorcreatesbackupISOandstoresitintheexternalstorage(for
example,intheFEWS).ItiscrucialthatbackupISOhadbeencreatedbeforeSWor
HWgotbroken.
w Restoringprocedurerequirethat:
1. TheuserisfamiliarwithharddiskreplacingprocedureasdescribedinReplacing
harddisks.
Restoring procedure overview
ThemaintoolintheprocedureisFEWS.Itistemporarilyconnectedtothecontroller
module'smanagementport(MGT).Performthefollowingstepstofullyrestore
controller'ssystem:
1. Ifnecessary,replaceallofthebrokenharddiskswithanewoneswhicharethe
sameorhighercapacity.
2. UseapreviouslysavedandstoredbackupISObuildasyourSWdeliveryonFEWS.
3. Create:
a) session-specificfiles
b) commissioningsession
4. ConnectFEWStothecontroller.
5. CommissionFCPU-0.
6. Performmodulepost-configuration.
7. Lockfilesystemanddatabaserecoverygroups.
8. Performfullrestore.
9. Unlockfilesystemanddatabaserecoverygroups.
10. Restartthecontroller.
11. Unlockthenodes.
12. Checksystemstatesandsaveconfiguration.
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Makingregularbackupcopiesoftheexecutablesoftwareandconfigurationdatausedby
itensuresthatyoucanrestorethesoftwaretoaprevioussoftwarelevelwhichfunctions
normally,forexampleinthecaseofaharddiskcrashoraconfigurationerror.
g Note: Youarerecommendedtoperformbackupoperationaftereveryconfiguration
changein,forexample,RNWconfigurationorLDAPconfiguration.Beforeyoudoso,
makesurethatthenetworkelementrunssmoothlywiththechangedconfiguration.
thenetworkelementisupandrunningasnormal.
thebackupisnotperformedduringlargefiletransferstothenetworkelement.
thebackupisnotperformedduringpeakhoursbecauseitcauseshighCPU
utilization.
anyotheroperationswhichcancausehighCPUloadarenotperformedinparallel.
Procedure
2 Check and make sure the state of the database recovery group (QNDBRNW) is
UNLOCKED
a) Checkthestateofthedatabaserecoverygroupusingthefollowingcommand:
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
a) Enterthebashshell:
shell bash full
b) Checktheavailablediskspaceforthebackup:
df -kh /mnt/backup/
c) Exitthebashshell:
exit
Thediskspaceyouneedforabackupmayvarydependinguponthesizeofthe
databasesandapplicationfilesystemstobebackedup.
Iftheremainingdiskspaceisnotenough,freediskspacebytransferringbackupsto
anexternalserveranddeletingunnecessaryfiles.Forinstructions,see Transferring
the backup archive file to an external storage server.
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Theresultingisoimageisstoredinthe"/mnt/backup/backup"directory.
Unexpected outcome
Whenbackupfails,thesystemraisesthealarm70064BACKUPERRORonthe
activeFCPUnode.
Youcanchecklogsrelatedtotheerrortogetmoreinformation.
Summary
Usethescpcommandtotransferthebackupimagetotheexternalstorageserverand
verifytheintegrityofthefilewiththemd5checksum.
Purpose
Totransferthebackuparchivefilefromthelocalharddisktoanexternalstorageserver
asasafetyprecaution.Thisalsofreeslocalharddiskspaceandkeepsahistoryof
differentbackupversions.
Procedure
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
4 Transfer the backup image and the checksum file to the desired location.
Enterthefollowingcommands:
# scp /mnt/backup/backup/<backup image> <username>@<external server
IP address>:<target location>
Table 8 Parametersfortransferringthebackupimageandchecksumfiletothe
desiredlocation
Parameter Description
<username> <username>isaloginnamewhichhaswritepermission
toexternalstorageserver
Forexample:
# scp /mnt/backup/backup/FZC603_active_backup_20120607_1008.iso
fpuser@10.10.10.2:/archive
scp /mnt/backup/backup/backup_20120607_1008.md5
fpuser@10.10.10.2:/archive
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Expected outcome
Ifthebackuparchivefileiscopiedtothedesiredstorageserverwithnoerrors,the
printoutofthemd5sumcommandisasfollows:
# FZC603_active_backup_20120607_1008.iso: OK
Unexpected outcome
# md5sum: FZC603_active_backup_20120607_1008.iso: No such file or
directory
backup_20120607_1008.iso: FAILED open or read
Themessageaboveindicatesthateitherthebackupimageisnottransferredoritis
locatedinadifferentdirectoryfromthatofthechecksumfileintheexternalstorage
server.
# FZC603_active_backup_20120607_1008.iso: FAILED
md5sum: WARNING: 1 of 1 computed checksum did NOT match
Themessageaboveindicatesthatbiterrorshavearisenduringtransferring.Insuch
situations,re-transferthefilesandverifythechecksumagain.
Procedure
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
# env_name=<FZCxxx>
<FZCxxx>standsforclusterIDofthecontrollerunderrestoration.
Step example
#env_name=FZC646
Step result
FZC646
Step example
# mount -o loop
tmp/myDelivery/${env_name}_active_backup_20150418_1030.iso
/mnt/myPoint
Step result
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Whenallremainingbuildsareremovedcorrectly,runningfsetupcliispossibleno
more.
Step example
# /mnt/myPoint/MISC/SS_FEWS/bin/fsetupcli --delivery --
patch
/tmp/myDelivery/${env_name}_active_backup_20150418_1030.iso
Step result
Patchingthedeliverytakesabout5-20minutes.Duringthattime,thereisno
indicationofprogressvisibleonthescreen.
Oncethepatchingisdone,the*.imgsoftwareimagesarecreatedunderthe
followingdirectoryonFEWS:
g Note: Patchedandcreateddirectoryindicates<build_name>,notthenameof.ISO
imagefile.
Step result
<build_name>:OK
Procedure
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Step example
Step example
# mount -o loop sysimg-R_QNCB.14.26.4_6.4.WR.mips.rmp-mips64-
wnd.img.gz /mnt/myPoint/
Step example
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Step result
ThemySessionfolderincludesthefollowingfile:
fsetup.conf
Procedure
# cd /root/mySession
# vi fsetup.conf
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Step result
(...)
COMM_NODE="FCPU"
TARGETS="FCPU-0"
COMM_VLAN="9"
(...)
5 Verify modifications.
# cat fsetup.conf
Procedure
g Note: Directory<sw_build_name>.WR.mips.rmpindicatesdeliveryname,notthe
backupversion.
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Purpose
Replacingfailedharddiskdrive.
TheHDSAM-AsupportsbothSASandSATAharddiskdrivesandincludesaSAS/SATA
switchforselectingthedisktype.TheBCNplatformsupportsonlytheSASharddisk
drive,thusalwayscheckthattheswitchissettoSAS,beforestartingthereplacement
procedure.
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Figure 16 TheSAS/SATAswitchintheHDSAM-A
HDSAM-A
Handle
IPMB-L
Switch
MMC
Switch
ON
1
Mechanical!adapter
AMC!Connector
SAS SATA 2.5 SAS!or!SATA Drive
5V 12V
Power
2!X!SAS
LEDs
DN0945027
Procedure
2 Place the AMC so that the faulty hard disk drive side is facing down. Unscrew
the four screws on the metal bracket of the AMC module, then turn the module
over.
Figure 17 TheharddiskdriveontheharddiskdrivecarrierAMC
Harddiskdrive
DN0945257
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Procedure
Figure 18 InstallingaharddiskdriveontotheharddiskdrivecarrierAMC
Harddiskdrive
SASconnector
DN0945245
Insertedscrew
2 Turn the AMC over and attach the new HDD to the AMC with four screws.
Tightenthescrewssothattheirheadsareinlinewiththemetalbracket.
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Procedure
Figure 19 CablingbetweenFEWSandthecontrollermodule
MgmntPort
2 Verify that the Ethernet link exists with the correct IP address.
Enterthefollowingcommand:
# ip addr show eth0
Step result
EthernetportmusthavetwoactiveIPaddresses:192.168.10.250and10.10.10.1
3 Verify connection between FEWS and the controller module's MGT port.
Sendapingpackettocheckwhethertheconnectionisconfiguredproperly.Onthe
FEWSenterthefollowingcommand:
# ping c 3 192.168.10.51
Nopingpacketreplyoccurswhen:
theFEWSisnotconnectedtothecontrollerfactory-commissionedmoduleone
theFEWSeth0configurationhasnotbeendoneproperly
Iftheproblemwasinthemodule'sinitialconfiguration,runtheLMPpre-configuration
accordingtoPerforming module pre-configurationinCleaninstallation.
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
serialports.IfyouhaveconnectionfromFEWStoserialportsyoucangivethesame
deactivationcommandfromthere.
Procedure
2 Deactivate all the nodes except the first one (FCPU-0) in module one.
4 Move FEWS Ethernet connection temporary to the next module's MGT port.
Remove the existing patch cable.
g Note: Rememberthewaythepatchcablesareconnectedsoastoconnectthemback
aftertheoperations.
OpentheterminalwindowfromFEWStothecontrollermodule<N>(LMP-1-<N>-
1)
# ssh root@192.168.10.5<N>
Password:root
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Procedure
Step example
Ifyouwanttologintothefirstmoduleusethefollowingcommand:
# ssh root@192.168.10.51
Thentypethepasswordandyouwilllogintothefirstmodulewiththefollowing
prompt:
root@LMP-1-1-1:~#
t Tip: Ifthepromptshownonthescreenis
Kontron S1901#
,rebootisunnecessary.
RebootFCPU-0fromLMP.Typethefollowingcommandsintheterminalwindow
whichisloggedinviasshconnectionfromFEWS:
# reboot f
f Interrupttheboot,hittheukey.Thefollowingtextisdisplayed:
autoboot in 3 seconds...type 'u' to abort
Step result
SuccessfulU-bootinterruptionallowstheusertooperatefromtheFCPU-0andis
indicatedbythefollowingprompt:
Kontron S1901#
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Step example
Kontron S1901# tftp 21000000 controller37/initial.img
w NOTICE: Donottypeanythingwhilethecommissioningisongoing.Theexpected
installationtimeisapproximately20minutes.
Step result
Whenthedownloadisready,thefollowingmessageisdisplayed:
#==================================#
COMMISSIONING: FINISHED OK (0)
START DATE: 2013-09-12-102523
END DATE: 2013-09-12-104159
ELAPSED TIME: 00:16:36
#==================================#
g Note: Incasethefollowingprintoutappearsonthescreen:
Connection closed by foreign host.
OpenanewtelnetconnectiontoCFPU-0typingthefollowingcommand:
root@BCNMB-B:~# telnet localhost 3001
0: reboot node
1: debugging shell
Please select "0" or "1".
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Select"0"toreboottheFCPU-0node.
a) PushCTRL+].
b) TypeQuitafterthepromptchangedto
telnet>
.
Step result
Theuseroperatesfromthe
LMP-1-1-1
.Itisindicatedbytheprompt:
root@LMP-1-1-1
Purpose
Tocompletecommissioning,thepost-configurationneedstobeexecutedbytheuseron
theFCPU-0.Theclusterisnotreadyfornormaloperationuntilpost-configurationis
executed.Afterthepost-configurationiscompleted,thecontrollerSWisstarted,
unlocked,andreadyforoperation.
Procedure
g Note: Thepostconfigurescriptapproximatelytakes40minutestoaccomplish.
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Step result
Whenpost-configureiscompletedsuccessfullyfollowingmessageisdisplayed:
2015-01-25 09:17:21,060 - Total: 0:01:04.666169
---------------------------------------------------------------
2015-01-25 09:17:21,062 - PostConfig finished.
---------------------------------------------------------------
Started: 2015-01-25 08:47:15.650624
Stopped: 2015-01-25 09:17:21.061897
Total: 0:30:05.411273
STATUS: OK
----------------------------------------------------------------
[root@FCPU-0(FZC195) /root]
#
Purpose
TheuserisloggedintheSCLIshell,whichisindicatedbythe>prompt.Toenterthe
shelltype# fsclish
Backup.ISOnamingconventionis:
Table 9 Backupnamingconvention
Backup type ISO name
Activebackup <env_name>_active_backup_<yyyymmdd_hhmm>.iso
Procedure
1 Check the status of the file system and database recovery groups.
EnsurethattheADMINISTRATIVEstatusofspecifiedfilesystemanddatabase
recoverygroupisLOCKED.Therecoverygroup's<mo_name>,whichneedtobe
checkedare:
/QNDBRNW
/QNOMU
/CLM
Step example
show has state managed-object /CLM
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Step result
Step example
root@FCPU-0 [mc-646] > start restore backup-iso /backup/FZC
-646_active_backup_20150325_1030.iso full
g Note: ThebackupISOfromtheservertothetargetmachineisimmediatelyavailable
fortherestoreoperationsaftercommissioning.Ifyouwanttocheckthecontentofthe
ISO,executethefollowingcommand:
show restore content backup-iso <path-to-backup.iso>
Thedefaultpathforbackupimageismnt/backup/
Step result
Thefullrestoreoperationissucceededandthefollowingmessageisdisplayed:
fsrestore: INFO: all restore completed successfully with exit status
0
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Step result
Systemrestartsnormally
Procedure
g Note: Beforemovingtothenextstep,ensurethatalltheactivatednodesarebooted
up.
Step result
Allnodesbootupnormally.
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
-0,executethefollowingcommand:
#fsclish
set has unlock all
Step result
Allnodesunlocksnormally.
Procedure
Step result
Statusforallnodesis:
UNLOCKED / ENABLED / ACTIVE
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Step result
Statusforalltherecoverygroupsis:
UNLOCKED / ENABLED / ACTIVE
Step result
ThestatusoftherunningSWbuildis
BU
.
SW Build status: BU (Active)
Step result
ThecleaninstallationprocedureshouldonlybeperformediftheFlexiZoneController
failedtohaveitspre-commissionedfactorysettingsverified.
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
2. Cablestobeusedduringcommissioning:
straight-throughEthernetcableusedtoconnecttheFEWStocontrollers's
management(MGT)port
serialcableusedtoconnecttheFEWStothecontrollerSERport
3. Anti-staticequipmenttobeusedduringcommissioning:
wristband
anti-staticmat
4. Thecontrollersite-specificinstallationparametersneededforconfiguration:
RNC-ID(itisauniqueidentifierwithinRANsetbytheoperatorbasedonaradio
networkplan)
NE-ID(writtenonthestickerplacedonthefrontpanel,configuredintheNokia
factory)
5. FEWSwithbothEthernetandserialinterfaces.
TherecommendedoperatingsystemonFEWSisCentOSLinux.Itcanbeinstalled
fromtheCentOSnetworkinstallationrepository.SeeCreating Field Engineering
Workstation formoreinformation.
ItisallowedtousealsostandardRedHatLinuxversion4.8orabove,orany
equivalentOS.
6. Accesstosoftwaredelivery(forexampleNOLS).
AnISOimagecontainingthecontroller'sSWandeSWisnecessary.
ThekeytoolinapplicationSWinstallationistheFEWS.Itisalaptoporotherworkstation
thatisusedforpreparationoftasksthatmustbeperformedbeforethesoftware
commissioningisstarted.Italsooffersservicesforbootingupthecommissioningnode
forthefirsttime,storageforthesoftwarebuilddelivery,andforthecommissioning
configurationfilesandlogs.
The main steps in clean installation are:
PreparingSWdeliveryonFEWS
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
InstallingapplicationSWpackagetothecontroller
Performingpost-configuration
Upgradingembeddedsoftware
Verifyingcommissioning
Procedure
1 Log in to FEWS (directly or via ssh connection) as root user and open the
terminal window.
YoucanlogintoFEWS:
directly,usingtherootlogincredentials.
remotely,viasshconnectionusingtherootlogincredentials.
# ssh root@<FEWS_IP_address>
Step result
ThefollowingpromptshowsyouareloggedontheFEWSwithrootprivileges:
[root@localhost ~]#
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Result
FLC15A_ENB_1411_001_66.iso
TargetBD_FLC15A_ENB_1411_001_66.xml
Procedure
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
# /mnt/myPoint/MISC/SS_FEWS/bin/fsetupcli --delivery --
patch /tmp/myDelivery/${build}.iso
t Tip: Patchingthedeliverytakesabout5-20minutes.Duringthattime,thereisno
indicationofprogressvisibleonthescreen.
Oncethepatchingisdone,the*.imgsoftwareimagesarecreatedunderthefollowing
directoryonFEWS:
/opt/nsn/fews/deliveries/<build_name>/
Step result
<build_name>:OK
Procedure
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Step example
Step example
# mount -o loop R_QNCB.14.26.4_6.4.WR.mips.rm.img /mnt/myPoint
4 Copy the session configuration file, and eSW upgrade files, and initialization
script.
Copythefzc_fsetup.confasfsetup.conffilefromthemountedimageto
thesessiondirectory.CopyeSWpackageforeSWupgradeandpost-configuration
scriptincludedinbcninit.tgzarchive.Usethefollowingcommands:
# cp -v /mnt/myPoint/opt/nsn/SS_FZCRefConfigs/script/fzc_fsetup.conf
/root/mySession/fsetup.conf
# cp -v /mnt/myPoint/opt/nsn/SS_FirmwareBCN/esw_file/*.tar.gz
/root/mySession
# cp -v /mnt/myPoint/opt/nsn/SS_FZCTools/bcninit/* /root/mySession
Step result
ThemySessionfolderincludesthefollowingfilesandpackages:
fsetup.confandbcninit.tgz,and<esw_build_name>.tar.gz.
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Procedure
g Note: Definedvariableisvalidonlyforaterminalsessionduringwhichitwasdefined.
Step example
mySessionincludes R_BCNESW_14_39_FP1.tar.gzamongotherfiles.
# esw=R_BCNESW_14_39_FP1
Step result
Seedefinedvariablewiththefollowingcommand:
# echo ${esw}
3 Go to mySession directory.
Enterthefollowingcommand:
# cd /root/mySession
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
a) Listthecontentofthe/tftpboot/${esw}/folderwiththefollowing
command:
# ll /tftpboot/${esw}/
Checkwhetherfollowinglistappears:
rw-r--r-- 1 root root 782 Jul 15 08:33 autorun.scr
-rw-r--r-- 1 root root 46 Jul 15 08:33 autorun.scr.md5
-r--r--r-- 1 root root 283 Jul 15 08:33 bcninit.readme
-r--r--r-- 1 root root 45161 Jul 15 08:33 bcninit.tgz
drwxr-xr-x 2 root root 4096 Jul 15 08:34 bmpp2-b
-rw-r--r-- 1 root root 3801 Jul 15 08:33 ncp20000.dtb
-rw-r--r-- 1 root root 47 Jul 15 08:33 ncp20000.dtb.md5
-rw-r--r-- 1 root root 197722358 Jul 15 08:33 ncp20000-initrd-
upgrade-5.9.6.gz.uboot
-rw-r--r-- 1 root root 73 Jul 15 08:33 ncp20000-initrd-
upgrade-5.9.6.gz.uboot.md5
-rwxr-xr-x 1 root root 650 Jul 15 08:33 setip.sh
-rw-r--r-- 1 root root 43 Jul 15 08:33 setip.sh.md5
-rw-r--r-- 1 root root 1807242 Jul 15 08:33 uImage
-rw-r--r-- 1 root root 41 Jul 15 08:33 uImage.md5
b) WritedowntheneededmotherboardeSWversionasmbeswvariable.Itis
applicableduringtheeSWdownloadprocess.CheckthemotherboardeSW
versionfromthe:
ncp20000-initrd-upgrade-5.9.6.gz.uboot
mbesw=5.9.6
c) WritedowneSWcomponentsfilenames.
Listthecontentofthe/tftpboot/${esw}/bmpp2-bfolderwiththefollowing
command:
# ll /tftpboot/${esw}/bmpp2-b
Writedownfilenamesmarkedwiththeboldfont:
-rwxr-xr-x 1 root root 235013 Sep 23 13:47 S1901-Errata-
v2.16.0000.pdf
-rwxr-xr-x 1 root root 2866 Sep 23 13:47 bmpp2-
b_kn_frud_02_16_0000.tgz
-rwxr-xr-x 1 root root 9771 Sep 23 13:47 bmpp2-
b_kn_mmbl_02_09_0000.tgz
-rwxr-xr-x 1 root root 276674 Sep 23 13:47 bmpp2-
b_kn_mmcf_02_15_0000.tgz
-rwxr-xr-x 1 root root 1268454 Sep 23 13:47 bmpp2-
b_kn_octf_02_16_0000.tgz
-rwxr-xr-x 1 root root 240819 Sep 23 13:47 bmpp2-
b_kn_pcpl_02_15_0000.tgz
-rwxr-xr-x 1 root root 1039 Sep 23 13:47 bmpp2-
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
b_kn_spif_02_09_0000.tgz
-rwxr-xr-x 1 root root 219210 Sep 23 13:47 rn_bmpp2-
b_02_16_0000.pdf
Example:bmpp2-b_kn_octf_02_16_0000.tgz
Definethevariablewiththefollowingcommand:#
cpu_esw_build=02_16_0000
g Note: Definevariableisvalidonlyforaterminalsessionduringwhichitwascreated.
Procedure
g Note: Itislikelythatduringthecommissioningprocedureyouarepromptedtoconnect
totheother(next)controllermodulesaswell.
Theseriallinesettingsfortheconsoleconnectionareasfollows:
Daterate:115200
Parity:N
Databits:8
Stopbits:1
Flowcontrol:Xon/Xoff
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Figure 20 CablingbetweenFEWSandthecontrollermodule
MgmntPort
4 Verify that the Ethernet link exists with the correct IP address.
Enterthefollowingcommand:
# ip addr show eth0
Step result
EthernetportmusthavetwoactiveIPaddresses:192.168.10.250and10.10.10.1
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Procedure
Step result
Sinceautobootstoppedthefollowingpromptappears:
BCNMB#
Step example
# esw=R_BCNESW_14_39_FP1
# mbesw=5.9.6
5 Define the boot variables for the network boot from FEWS.
FEWSEthernetportIPaddressissetto192.168.10.250.Defineotherbootvariables
withthefollowingcommands:
# set ipaddr 192.168.10.59
# set serverip 192.168.10.250
# set netmask 255.255.255.0
# set gatewayip 192.168.10.250
# set ramdiskfile ${esw}/ncp20000-initrd-upgrade-${mbesw}.gz.uboot
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
7 Run ramboot.
# run ramboot
Step result
Thefollowingpromptappears:
root@BCN-UPGRADE#
Selectupgradeoption:
3. BCNMB upgrade (BCNMB only)
Step result
MotherboardLMPeSWisbeingupgradedautomatically.
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
g Note: Donotinterrupttheautobootprocess.AftertheLMPboothasbeencompleted,
loginasroot.
Step result
Motherboardcomponents'eSWhavesoftwareinversionsdescribedintherelease
notes.
g Note: Thetermmoduleinthefollowinginstructionsreferstothecurrentmodulewhere
theuserisconnected.
Procedure
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Enterthepassword:root
Step example
Foradd-incardnumberone,loginwiththefollowingcommand:# telnet
localhost 3001
Enterthepassword:root
Logintoeachadd-incardofFZCmodulestartingfromfirstcard.Establishatelnet
connectionwiththefollowingcommand:# telnet localhost 300<x>
Sub-steps
a) Enter the reboot command and stop autoboot by pressing the u key when
the following prompt appears: Hit key 'u' to stop autoboot
Step example
BusyBox v1.15.3 (2012-11-08 20:03:25 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.
#
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
esw=<esW_build_name>
sw="GA\s"
ver=<cpu_esw_build>
# example:
# esw=R_BCNESW_13_45_FP1
# sw="GA\s"
# ver=02_09_0000
#
#
# Usage
#
if [ ${#} -ne 2 ]; then
echo "Usage:"
echo "${0} <FEWS IP> <mgmt0 IP>"
exit 1
fi
#
# Get FEWS and and mgmt0 IP arguments
#
fewsip=$1
mgmt0ip=$2
#
# Check bootloader security hash and version
#
cat /proc/mtd
md5sum /dev/mtd0 /dev/mtd5
strings /dev/mtd0 /dev/mtd5 | grep ${sw}
#
# Set cpu mgmt0 IP
#
ifconfig mgmt0 ${mgmt0ip}
err=$?;if [ ${err} -ne 0 ]; then exit 1; fi
ping -c 1 ${fewsip}
err=$?;if [ ${err} -ne 0 ]; then exit 1; fi
echo
"====================================================================
"
echo "bmpp2-b ${sw} ${ver} upgrade from ${esw}"
echo "FEWS ${fewsip}"
ifconfig mgmt0
echo
"====================================================================
"
#
# Get bmpp2-b GA ${ver} images from FEWS
#
cd /tmp
echo "Get firmware from FEWS, make sure that /tftpoot/ contains esw:"
echo ${esw}
scp root@${fewsip}:/tftpboot/${esw}/bmpp2-b/bmpp2-b*${ver}.tgz .
err=$?;if [ ${err} -ne 0 ]; then exit 1; fi
tar -xzvf bmpp2-b_kn_mmcf_${ver}.tgz
err=$?;if [ ${err} -ne 0 ]; then exit 1; fi
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Step example
esw=R_BCNESW_14_39_FP1
ver=02_16_0000
8 After the script work is completed, activate the eSW. This swaps the
flashbanks. firmware-activate --swap powercycle
Step result
Theadd-incardstartstobootup.
9 Stop autoboot
Whenthispromptappears:Hit key 'u' to stop autoboot ,Hitukeyto
breaktheautoboot.
Step result
BusyBox v1.15.3 (2012-11-08 20:03:25 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.
#
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
12 Copy and paste the edited script to add-in card prompt. Hit Enter to run the
prompted script.
g Note: Donotinterrupttheautobootprocess.
Procedure for setting-up and running the factory pre-configuration script for the LMP of
the module.
Purpose
Intheresultofthescriptexecutionthecorrectdefaultvaluesforthefollowingsettings
aregiven:
mch-conf file
resilientback-plane
NetworkElementID
rackandnodenumber
LMPeth0portIPaddress
TheconfiguredLMPeth0address(10.10.10.10)ischangedtothenewaddressafter
runningthepre-configurationscript.ForthenewLMPeth0portIPaddress,seeLMP
eth0portconfiguration:
Table 10 LMPeth0portconfiguration
Module number IP Address
1 192.168.10.51/24
2 192.168.10.52/24
g Note: WhentheLMPeth0IPaddressissettoanyotherthan10.10.10.10theIPpre-
configurationscriptdoesnotchangeit.
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Procedure
Step result
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
t Tip: IfpingpacketsarelostitmeansthattheconnectionbetweenFEWSandthe
controllermoduleisnotsetproperly.CheckthecablesbetweentheserialandEthernet
ports.ThispacketlossmightalsoindicatethatLMPeth0addressiswrong.This
happenedduetotheattemptofrunninganLMPpre-configurationonacontroller
modulethatisalreadypre-configured,andwhichmighthaveadifferentIPaddressthan
10.10.10.10.UseoneoftheIPaddressesassignedtoLMPeth0portafterrunningthe
pre-configurationscript.Forexample,sendpingpacketstooneofthepre-configured
modulesusingfollowingcommand:
# ping c 3 192.168.10.51
Checkifallpingpacketsarereceived.Thisindicatesiftheconnectionisestablished
properly.
Step example
Sendpingpacketstooneofthepre-configuredmodulesusingfollowingcommand:
# ping c 3 192.168.10.51
Checkifallpingpacketsarereceived.Thisindicatesiftheconnectionisestablished
properly.
Step result
Ifpingpacketsarereceived,theIPaddressingschemeofLMP'seth0isequalto
LMPeth0portconfiguration.
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Removeerror-causingIPwiththefollowingcommand:
ssh-keygen -R 10.10.10.10
Performthesecurecopy(scp)again.
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Table 11 Requiredpre-configurationscriptparameters
Parameter Acceptable values Action
<Modulenumber> 1to8 Typethenumberofmodulewhichareyoupre-
configuring.
<Add-incardtype> BMPP2-B Typethenameofadd-incard.
<NE-ID>(NetworkElementID) 11-digitnumber ReadNE-IDfromthestickerplacedonthe
module'sfrontpanel.Inserttheneedednumber
ofzeroesinfrontofthenumericalvaluetogeta
11digitnumber.Typethe11-digitnumber.
Step example
Modulenumberone(1)ofthecontroller(withBMPP2-Badd-incardtype)isunder
pre-configuration.TheNE-IDwrittendownfromthestickeris123456.Invokethe
scriptwiththefollowingcommand:
# ./node.sh 1 BMPP2-B 00000123456
Procedure
2 Set the date and time equal to Coordinated Universal Time (UTC), if needed:
# date --s "<day month year hour:minute:second>"
Example:
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Procedure
Step result
Aftermessageshownascommandrespond,BCNresetlostconnectiontothe
moduleunderpre-configuration.
Stopping services ...
Broadcast message from root (Mon Dec 23 11:40:14 2013):
The system is going down for reboot NOW!
root@BCNMB-B:/mnt/fastpath# Connection to 10.10.10.10 closed by
remote host.
Connection to 10.10.10.10 closed.
[root@fi-sateri01942 mySession]#
TheFEWSpromptappearsintheFEWSterminalwindowafterthecontrollermodule
reset.
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Procedure
Step example
# ping -c 3 192.168.10.51
Step example
Ifyouwanttologintothefirstmoduleusethefollowingcommand:
# ssh root@192.168.10.51
Thentypethepasswordandyouwilllogintothefirstmodulewiththefollowing
prompt:
root@LMP-1-1-1:~#
Step result
Allcontrollermoduleshavethesameracknumber:
1
Step result
Nodenumberisthesameasmodule(chassis)number.
1
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
5 Verify the network element ID of the controller module against NE-ID on the
sticker.
AllboxesintheclustermusthavethesameNE-ID.
TogettheNE-ID,enter:
root@lmp-1-1-1:~# mch_cli GetNetworkElementId
Step result
ThereturnedvalueisNE-IDprecededbyzeros(containselevendigitsintotal).
00000123456
6 Verify the plug-in units bootscript configuration from the mch.conf file.
root@lmp-1-1-1~# grep bootscript /etc/ipmi/mch.conf
Forthemodule:
1.bootscript=02
2.bootscript=03
Step result
For<modulenumber>thefollowingmessageappears:
1 lrwxrwxrwx 1 root root 16 Sep 5 06:38 module ->
/opt/cluster/m<module number>0
Forproperlydonemoduleone'sresilientback-planeconfiguration,thefollowing
messageappears:
1 lrwxrwxrwx 1 root root 16 Sep 5 06:38 module -> /opt/cluster/m10
Step result
echo post 10
0:sleep quiet 1
0:local module 10
0:mod port 0 29 my_modid=@module
0:mod modport_map 0x0 7424 higig_port_bitmap=0x00000000
0:mod src_modid_block 0x1400 256 port_block_mask_bitmap=0x1fffffff
0:mod src_modid_block 0x1500 256 port_block_mask_bitmap=0x1fffffff
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Step result
echo "extension post ver 2.0.0"
echo "/mnt/fastpath2/module/post.soc"
linkscan interval=10000
setreg PKTPORTMAXBUCKETCONFIG PKT_PORT_MAX_THD_SEL=0x400
PKT_PORT_MAX_REFRESH=0x400
Sub-steps
AfterthemodulepowercyclesyoushouldrestarttheLMPverificationfromthe
beginning.
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
11 Repeat all the steps for all of the modules inside the deployed controller
cluster.
Procedure
# cd /root/mySession
# vi fsetup.conf
Table 12 Commissioningparametersinfsetup.conffile
Variable Definition
DELIVERY <build name>.WR.mips.rmp
TIMEZONE Thisparameterdefinesthetimezone.
CLUSTERID Thisparameterdefinesthenameofthenetworkelement.Thename
isvisibleinthecontrollerpromptafterthecommissioningisdone.
TheparameterformatisFZCxx.
COMM_IFACE ThisparameterdefinesthenetworkinterfaceintheFEWSthatis
usedforthecommissioning.ForFZCthevalueshouldbeeth0.
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Table 12 Commissioningparametersinfsetup.conffile(Cont.)
Variable Definition
COMM_FEWSIP ThisparameterdefinestheIPaddressandthenetworkmaskofthe
COMM_NETWORK commissioninginterfaceoftheFEWS.Itisrecommendedthatyou
usethefollowingIPaddresses:
COMM_NETWORK="192.168.10.00/24"***
COMM_FEWSIP="192.168.14.250/24"***.
COMM_VLAN ThisparameterisoptionalanditisusedtodefinetheVLANIDofthe
commissioninginterface.
IftheVLANisnotused,commentouttheline#COMM_VLAN
orremovetheparameterfromthefile.
AUTO_POSTCONFIG
g Note: AssigningtheFEWSIPaddressas192.168.10.250/24simplifiesthe
establishmentofaconnectionbetweenthecontrollerandtheFEWS.Modulepre-
configurationintheNokiafactoryandLMPpre-configurationduringeSWinstallation
setsthefollowingIPaddressestodifferentmoduleLMPs:
Table 13 LMPeth0portconfiguration
Module number IP Address
1 192.168.10.51/24
2 192.168.10.52/24
Note: Oncethesessionisstarted,IPconnectivitybetweentheFEWSandthe
controller'smoduleoneLMPisheld.
4 Verify modifications.
# cat fsetup.conf
Step result
Thefollowingexamplesshowconfiguredfsetup.conffilecontentforaFlexiZone
Controllerdeployment.
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
zone
TIMEZONE="America/Chicago"
# to interface that has hosts that are not meant to get IP's from
this network. Session starts dhcpd service
# can be configured
COMM_USER_CONFDIR="/user_cfg"
# For debug
DEBUG="1"
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Procedure
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Procedure
Figure 21 CablingbetweenFEWSandthecontrollermodule
Step result
TheEthernetportmusthavetwoactiveIPaddresses:192.168.10.250and
10.10.10.1.
3 Verify connection between FEWS and the controller module one LMP.
Sendpingpackttocheckwhethertheconnectionisconfiguredproperly.Onthe
FEWSenterthefollowingcommand:
# ping c 3 192.168.10.51
Nopingpacketreplyoccurswhen:
theFEWSisnotconnectedtothecontrollermoduleone
theFEWSEthernetlinkconfigurationhasnotbeendoneproperly
theLMPpre-configurationhasfailed
IftheproblemisinmoduleinitialconfigurationrunLMPpre-configurationaccording
toPerforming module pre-configuration.
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Openthesetwoterminalwindowsiftheyarenotalreadyopened:
TerminalwindowstoFEWS
SerialportterminalwindowtothecontrollermoduleoneLMP(LMP-1-1-1)
Procedure
Step example
Ifyouwanttologintothefirstmoduleusethefollowingcommand:
# ssh root@192.168.10.51
Thentypethepasswordandyouwilllogintothefirstmodulewiththefollowing
prompt:
root@LMP-1-1-1:~#
t Tip: Ifthepromptshownonthescreenis
Kontron S1901#
,rebootisunnecessary.
RebootFCPU-0fromLMP.Typethefollowingcommandsintheterminalwindow
whichisloggedinviasshconnectionfromFEWS:
# reboot f
f Interrupttheboot,hittheukey.Thefollowingtextisdisplayed:
autoboot in 3 seconds...type 'u' to abort
Step result
SuccessfulU-bootinterruptionallowstheusertooperatefromtheFCPU-0andis
indicatedbythefollowingprompt:
Kontron S1901#
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Step example
Kontron S1901# tftp 21000000 controller37/initial.img
w NOTICE: Donottypeanythingwhilethecommissioningisongoing.Theexpected
installationtimeisapproximately20minutes.
Step result
Whenthedownloadisready,thefollowingmessageisdisplayed:
#==================================#
COMMISSIONING: FINISHED OK (0)
START DATE: 2013-09-12-102523
END DATE: 2013-09-12-104159
ELAPSED TIME: 00:16:36
#==================================#
g Note: Incasethefollowingprintoutappearsonthescreen:
Connection closed by foreign host.
OpenanewtelnetconnectiontoCFPU-0typingthefollowingcommand:
root@BCNMB-B:~# telnet localhost 3001
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
0: reboot node
1: debugging shell
Please select "0" or "1".
Select"0"toreboottheFCPU-0node.
a) PushCTRL+].
b) TypeQuitafterthepromptchangedto
telnet>
.
Step result
Theuseroperatesfromthe
LMP-1-1-1
.Itisindicatedbytheprompt:
root@LMP-1-1-1
Procedure
1 Connect to the module's one LMP (LMP-1-1-1) if you do not have connection
already.
Enterthefollowingcommand:
# ssh root@192.168.10.51
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Passwordis:root.
g Note: Thepostconfigurescripttakesapproximatelyupto40minutestoaccomplish.
This section shows how to synchronize the configuration data located on LMP flashbank
0 and 1
Procedure
Step result
INFO Configuring backup flash bank LMP-1-1-1
INFO Backup configuration on lmp OK
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Step result
1 lrwxrwxrwx 1 root root 16 Sep 5 06:38 module ->
/opt/cluster/m<module number>0
Step result
echo "extension post ver 2.0.0"
echo "/mnt/fastpath2/module/post.soc"
linkscan interval=10000
setreg PKTPORTMAXBUCKETCONFIG PKT_PORT_MAX_THD_SEL=0x400
PKT_PORT_MAX_REFRESH=0x400
Procedure
1 Connect to the module's one LMP (LMP-1-1-1) if you do not have connection
already.
Enterthefollowingcommand:
# ssh root@192.168.10.51
Passwordis:root.
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Step result
Statusforallnodesis:
UNLOCKED / ENABLED / ACTIVE
Step result
Statusforalltherecoverygroupsis:
UNLOCKED / ENABLED / ACTIVE
Step result
ThestatusoftherunningSWbuildis
BU
.
SW Build status: BU (Active)
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Step result
AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
Procedure
Step result
AsaresultBCNisrebootedoncethefollowingmessageappears:
Stopping services ...
Broadcast message from root (Mon Dec 23 11:40:14 2013):
The system is going down for reboot NOW!
Step result
TheIPaddressofmodule'seth0portis
10.10.10.10
Step result
ModuleNetworkElementIDisxxxxxxxxxxx.
CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
Procedure
g Note: EachconfiguredcellisrepresentedbyitsownLNCELobject.
3 Create a new Uplink power control configuration for PUSCH / SRS component
ClicktheNewmenubelowtheobjectlistpanelandselectUplink power
control PUSCH configuration.
Result