Commissioning FZC

Nokia
LTE Radio Access, Rel. FDD-

LTE 16A, Operating
Documentation, Issue 02
Commissioning Flexi Zone

Controller
DN09210645
Issue 01C
Approval Date 2016-02-26
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.
f Important Notice on Product Safety

Thisproductmaypresentsafetyrisksduetolaser,electricity,heat,andothersourcesofdanger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this
productandonlyafterhavingcarefullyreadthesafetyinformationapplicabletothisproduct.
The safety information is provided in the Safety Information section in the Legal, Safety and
EnvironmentalInformationpartofthisdocumentordocumentationset.
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
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
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.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
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
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
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

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.
Changes between issues 01A (2015-09-30, FDD-LTE15A / TD-LTE15A) and 01B

(2015-12-07, FDD-LTE15A / TD-LTE15A, FDD-LTE16 / TD-LTE16)
Flexi Zone Controller commissioning workflow

Flexi Zone Controller commissioning workflowhasbeenupdated.
Verifying IPSec tunneling in Flexi Zone Controller

Verifying IPSec tunneling in Flexi Zone Controllerhasbeenadded.
Integrating Flexi Zone Access Points to the Flexi Zone Controller

Integrating Flexi Zone Access Points to the Flexi Zone Controllerhasbeenupdated.
Additional procedures for FZC commissioning

Additional procedures for FZC commissioninghasbeenadded,modifyingthe
previousappendixstructure..
Improving FZAP uplink throughput

Improving uplink throughput in Flexi Zone Controllerhasbeenadded.
Changes between issues 01 (2015-07-15, FDD-LTE15A / TD-LTE15A) and 01A

(2015-09-30, FDD-LTE15A / TD-LTE15A)
Flexi Zone Controller commissioning workflow
Flexi Zone Controller commissioning workflowhasbeenadded.
Setting up the Z1 Interface
Setting up the Z1 Interfacehasbeenupdated.
Adding DHCP Server Static MAC to IP assignment
Adding DHCP Server Static MAC to IP assignmenthasbeenupdated.
Setting up a CMP Server IP for the Flexi Zone Controller
Setting up a CMP Server IP for the Flexi Zone Controllerhasbeenupdated.
Migrating a Flexi Zone Controller to a customer provided PKI

Summaryofchanges CommissioningFlexiZoneController
Setting up the M-Plane IP address as CMP Server IP addresshasbeenupdatedand

changedtoMigrating a Flexi Zone Controller to a customer provided PKI.
Modifying the customer provided PKI of a Flexi Zone Controller
Modifying the customer provided PKI of a Flexi Zone Controllerhasbeenadded.
Backing out from a customer provided PKI to an internal PKI in a Flexi Zone
Controller
Backing out from a customer provided PKI to an internal PKI in a Flexi Zone
Controllerhasbeenupdated.
Clean installation preconditions


CommissioningFlexiZoneController IntroductiontoFlexiZoneControllercommissioning
1 Introduction to Flexi Zone Controller

commissioning
This document describes how to commission a Flexi Zone Controller (FZC).
Commissioningisaprocessofinstallingtherequiredsoftwareandthenecessary
configurationsonanetworkelement(NE).Itisperformedafterinstallingthehardware
andbeforethenetworkelementisconnectedtotheoperator'snetwork.DuetotheFZC's
SWarchitecture,twoseparatecomissioningproceduresneedtobeimplemented:
commissioningoftheFZCapplicationandembeddedsoftwarethroughSCLIviaa
fieldengineeringworkstation
commissioningoftheFZCLTEstackviatheBTSSiteManagerapplication
Theseinstructionsassumethattheuserhasabasicknowledgeofnetworkingandbase
stationssystems.
w NOTICE: Onlyproperlytrainedandauthorizedpersonnelmayperforminstallation,
commissioning,ormaintenanceoperationsonanyNokiaNetworkElement.
Screenshotsandcommandlineprintoutsareincludedasexamples,andtheinformation
depictedonthemmaydifferdependingonparticularcircumstances.
1.1 Flexi Zone Controller commissioning workflow
Purpose
TheprovisionofaZoneeNBrequiresthecommissioningoftheFlexiZoneController
moduleandtheestablishingofsouthboundandnorthboundinterfaces.Aseriesof
commissioning,configuration,andintegrationproceduresneedtobefollowedinorderto
provisionafunctionalZoneeNB.
Procedure
1 FZC HW installation and verification

SeeCommissioningFlexiZoneController(DN09210645)fordetailedinstructions.
2 FZC module software commissioning and network configuration through its

SCLI command line interface via an SSH connection from a field engineering
workstation (FEWS)
SeeCommissioningFlexiZoneController(DN09210645)andCommissioningFlexi
ZoneController(DN09210645)fordetailedinstructions.
3 Integrating the FZC module to NetAct through the NES3 interface


IntroductiontoFlexiZoneControllercommissioning CommissioningFlexiZoneController
4 Commissioning the FZC module via the BTS Site Manager application
5 Integrating the FZC module to NetAct through the NWI3 interface

6 Integrating individual FZAPs under the FZC via BTS Site Manager and WebUI
Figure 1 FlexiZoneControllercommissioningworkflow
Start
VerifyHW
installation
SCLI/FEWS ConfiguringFZC Failed FZC

Commission pre-commission cleaninstallation
OK
NES3integration FZC
toNetAct IP configuration
BTSSM
Commission
NWI3integration
toNetAct
WebUI/BTSSM
FZAP integration
Commissioned
ZoneeNB

CommissioningFlexiZoneController IntroductiontoFlexiZoneControllercommissioning
ConfiguredFZAPscanbeadded(connected)orremoved(disconnected)totheZone
eNBunderaFZCwithoutaffectingtheavailabilityoftheFZCand/oranyotherFZAPs
underthatFZC.

CommissioningFlexiZoneControllerthroughSCLI/ CommissioningFlexiZoneController
FEWS
2 Commissioning Flexi Zone Controller through

SCLI / FEWS
Thissectioncoversconfigurationstepstobeperformedafterthehardwareinstallationof
FZCnetworkelementhasbeensuccessfullycompleted.Afterconfiguration,theFZC
networkelementisreadyforsite-specificintegration.
2.1 Setting up a Field Engineering Workstation
AFieldEngineeringWorkstation(FEWS)isastardardPClaptoporworkstationwhichis
providedwiththenecessaryDHCPandTFTPservicestocommunicatewithaNEfor
configurationpurposes.
g Note: NokiadoesnotprovideFEWSasanofficialproduct.Itisuptotheuserto
acquireboththehardwareandoperatingsystem.
NokiarecommendsCentOSastheFEWSoperatingsystem,butanyequivalentLinux
distributionmayalsobeused.TheinstructionswithinthisdocumentassumeCentOSis
beingused.
2.1.1 FEWS Hardware Requirements

Thefollowingminimumhardwareconfigurationisrequiredforsettingupafield
engineeringworkstation:
512MBmemory
60GBharddiskdrive(HDD)
twonetworkinterfaces(1GB/100MB)
CD-ROMorDVD-ROM
twostraightnetworkcables
onecrossednetworkcable(Category5)
2.1.2 Logging into field engineering workstation

Purpose
Tologintothefieldengineeringworkstation(FEWS)astherootuser.Forinstructions
onlogginginremotely,seestep1.Forinstructionsonlogginginlocally,seestep2.
Procedure
1 Log in to the FEWS remotely as the root user.
a) WithSSHclient:

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.
2 Log in to the FEWS locally as the root user.
a) Intheusernamefield,enterroot.
b) Inthepasswordfield,enterthepasswordfortherootuser.
2.1.3 Configuring FEWS services

Purpose
ThischapterdescribestheprocedurethatallowstheuseoftheLinuxOS-basedlaptop
asaFEWSforcommissioningpurposes.
g Note: Thisproceduretakesapproximately30minutes.
Procedure
1 Open the FEWS terminal.

Right-clickonthedesktop,andthenselectOpen Terminalfromthemenu.
2 Disable Linux Security Modules (SELinux).
a) OpenSELinuxconfigurationfilewiththefollowingcommand:
# vi /etc/sysconfig/selinux
b) ChangetheSELinuxenforcingvaluetodisabled.Saveandexitthe
configurationfile.
Step result
SELINUX=disabled

FEWS
3 Set up tftpboot and xinetd services.
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
4 Disable DNS server resolution.

Listtheresolv.conffilewiththefollowingcommand:
#cat /etc/resolv.conf
Ifanycontentappears,openthefileinthevieditorandcommentoutallentriesby
addingthehashsign(#)atthebeginningofthelineorremovealltheentries.Save
andexittheconfigurationfile.
5 Permit all devices to access the FEWS.
a) Gotothespecifieddirectorywiththefollowingcommand:
# cd /etc
b) Allowtherootusertoeditthefilewiththefollowingcommand:
# chmod 644 hosts.allow
c) Openthe/etc/hosts.allowfileinthevieditorandmodifythefileby
commentingallentriesout.InthelastlineaddALL: ALLtoallowallusersto
accesstheFEWSremotely.
Saveandexittheconfigurationfile.
6 Ensure that no hosts are denied.
a) Allowtherootusertoeditthefile.
# chmod 644 hosts.deny
b) Openthe/etc/hosts.denyfileinthevieditorandmodifythefileby
commentingallentriesout.
7 Configure exports file.

ThisistoensurethatthecontrollerhasaccesstotheFEWSfilesystemwhenthe
applicationsoftwareisinstalled.Checkwhetherthefollowinglineisinthe
/etc/exportsfile:

FEWS
# cat /etc/exports
/opt/nsn/fews *.*.*.*(rw,no_root_squash)
Ifthelineismissing,editthefileandaddit.
8 Check FEWS services.
iptables-mustnotberunning.Todisabletheservice,enter:
service iptables stop
nfs-mustberunning.Toenabletheservice,enter:
service nfs start
xinetd-mustberunning.Toenabletheservice,enter:
service xinetd start
9 Configure services' autostart.

EnsureservicessettingsareappliedeachtimetheFEWSisstarted.Configure
services'autostart:asfollows:
a) EnterntsysvcommandtoconfigurerunlevelservicesinServiceswindow.Hit
SPACEtoswitchthatserviceisEnabledorDisabled.Theasterisk(*)means
thatserviceisEnabled
b) Disableiptables.
c) Enable:
nfs
xinetd
tftpd
dhcpd
HitTABinordertoreachOKbutton.HitOKtoexitntsysv.
Result
FEWSisnowreadytobeusedforcommissioning.
2.2 Configuring a factory pre-commissioned FZC

2.2.1 Introduction to configuring a factory-commissioned
controller
Factory commissioning and software installation
Allcontrollersthataredeliveredtocustomersarepre-commissionedinthefactory.This
includesapplicationandembeddedsoftware(eSW)installation.

FEWS
g Note: ThecommissioningandembeddedSWupgradeproceduresareprovidedto
allowoperatorstomanagetheirexistingNEpool.Newlypurchasedcontrollersare
factory-commissionedbeforebeingprovidedtothecustomer.
Commissioning procedure overview
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.2.1.1 Configuration preconditions

1. ThecontrollerHWinstallationissuccessfullycompleted.
HWinstallationisdescribedinthefollowingdocuments:
Installation Site Requirements for BCN Hardware
Flexi Zone Controller Hardware Installation Quick Guide
Installing BCN Hardware to Commercial 19-inch Cabinet
Installing BCN hardware to CAB216SET-B
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

FEWS
CLUSTERID:FZC1234
FZC_ID:FZC1234
FCPUrootpassword:root
FCPU_nokadminpassword:system
Module MGT port LMP IP addresses
Module1:192.168.10.51
2.2.1.2 Configuration overview
The main steps in configuring the factory-commissioned controller are:

ThekeytoolinconfigurationisFEWS.Itistemporarilyconnectedtothecontroller
module'smanagementport(MGT)forthecontrollernetworkelementinitialconfiguration.
VerifyingHWinstallation
Verifyingfactorysettings
Changingthecontrollercluster-ID/FZC-ID
Verifyingfactorycommissioning
2.2.2 Verifying HW installation

Purpose
Thissectiondescribeshowtoperformthehardwareinspectionbeforethecontrolleris
poweredon.
Before you start

CheckthatHWinstallationiscompletedsuccessfully.

Procedure
1 Inspect the BCN module grounding.

Makesurethatallcontrollermodulesareproperlygrounded.
2 Inspect the cabling.

FEWS
3 Inspect the interchangeability versions of the BCN modules.

Therearethreelabelsintheright-handsideofthemodule.Thelabelscontainthe
followingtext:
Upperlabel<NetworkElementID>
MiddlelabelBCNCPUSET-B
LowerlabelBCNSET-B
ThenetworkelementIDisauniqueIDforacontrollernetworkelement.Itmustbe
thesameforallmodulesinsideonenetworkelement.Themiddlelabelspecifiesthe
add-incardhardwaretype.Thelower/leftlabelspecifiestheBCNboxbasicHW
(motherboard,fanunitsandairfilter).
4 Inspect the AMC hard disks.

Harddisksareinstalledinthefirsttwomodulesandlocatedontheleftsideofthe
module.PushtheharddiskAMChandlesiniftheyarenotpushedalready.Thehard
diskisinstalledintheleftslot.
AllemptyAMCslotshavedummyAMCsinserted.
5 Inspect the location of fans and the air filter.

Twomainfansandoneauxiliaryfanareinsertedintothemodule'srear.Theairfilter
isinfront.
6 Inspect the power supply.

Twopowersuppliesareinsertedintothemodule'srear.Powermodulesareeither
ACvariantsorDCvariants.
7 Inspect the site.

Checkthatthecontrollerrackandcabinetareinstalledintotheircorrectplaces
accordingtothecustomersiteplan.
8 Power on the controller modules.

Afterpoweringon,theLEDsoneachmodule'sfrontpanelglowtoinformtheuser
aboutthecurrentunit'sbootstatus.
Phase1
PO(powermoduleLED)isgreen,indicatingthatbothpowermodulesarein
placeandworkingproperly.TheA1andA2LEDsarered,indicatingthatthe
BCNmotherboardisbootingup.P1-P2(ProcessorAdd-incardLEDs)areblue,
indicatingthattheprocessoradd-incardsareinplace,buttheyarenotactivated.
Phase2
A1andA2LEDschangeintogreen,indicatingthatthemotherboardisworking
properly.P1--P2LEDsturnredstartingfromP1.Thisindicatesthattheadd-in
cardsareactivatedandtheyarebooting.

FEWS
Phase3
P1--P2LEDsturngreen.Thisindicatesthatadd-incardsarerunningplatform
LinuxSW.
2.2.3 Verifying factory settings
2.2.3.1 Connecting FEWS to the controller

Purpose
ThissectiondescribeshowtoconnecttheFEWStothecontrollerforcommissioningand
IP-subnetconfiguringpurposes.
Procedure
1 Connect the Ethernet cable.

ConnecttheFEWSEthernetporttofirstcontrollermodule'sMGTport.Removethe
existingEthernetpatchcablefromthemodule'sMGTandconnecttheFEWScable
instead.Afterconfigurationiscompleted,reconnectthepatchcable.
Figure 2 CablingbetweenFEWSandthecontrollermodule
2 Configure Ethernet port IP address of the FEWS.

OntheFEWSenterthefollowingcommand:
# ip addr add 192.168.10.250/24 dev eth0
3 Activate FEWS Ethernet link.

# ip link set eth0 up

FEWS
4 Verify the Ethernet link status and settings.

# ip addr show eth0
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.
2.2.3.2 Checking factory settings

Purpose
LocalManagementProcessors(LMPs)andCentralProcessingUnits(FCPUs)mustbe
interconnectedforthemtocommunicatewitheachother.CheckwhetherLMPsand
FCPUsarecorrectlyinterconnected.
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
2.2.4 Verifying the Flexi Zone Controller ID format

This section shows how to verify that the FZC logical network element ID has the format
required for correct OMS/NetAct integration.

FEWS
Before you start

ThestepsdescribedinthissectionmustbeperformedwithintheFZCSCLIshell.
Procedure
1 Enter the command show config filter

(fsLogicalNetworkElemId=*) fsClusterId=ClusterRoot
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
2 Verify that the fsLogicalNetworkElemId parameter shown in the printout

includes only letters or numbers.
Sub-steps
a) If the parameter includes characters other than letters and numbers,

change it with the following command:
set config attribute fsClusterId=ClusterRoot attribute-
list fsLogicalNetworkElemId <id>
Step example
set config attribute fsClusterId=ClusterRoot attribute-
list fsLogicalNetworkElemId FZC01
Step example
fsLogicalNetworkElemId: FZC01iscorrectlyformatted.
2.2.5 Verifying factory commissioning

Purpose
Thissectiondescribeshowtocheckthecontroller'sstateafterfactorypre-
commissioning.
Before you start
AllstepsdescribedinthissectionmustbeperformedinSCLIshell.

FEWS
Procedure
1 Check the active alarms.

Viewthesummaryoftheactivealarms:
2 List information for a given active alarms:

> show alarm active filter-by specific-problem <alarm_id>
3 Check the controller nodes' state.

> show has filter node state managed-object /*
Step result
Statusforallnodesis:UNLOCKED/ENABLED/ACTIVE
4 Save the configuration snapshot.
g Note: Notethattheconfigurationneedstobesavedtopreserveoversystemrestart.
Tosaveasnapshot,enter:
> save snapshot
2.3 Flexi Zone Controller IP configuration
Theseproceduresmustbeperformedviathecontroller'sfsclishbashbeforeanyfurther
integrationcanbeinitiated.
2.3.1 Ethernet Interfaces on Flexi Zone Controller
WhentheFZCisfirstpoweredupforfieldcommissioning,theFZCisconfiguredwiththe
followingstandardconfigurations:
Card Interface SFP Interface Label

FCPU 1G SFP13 nbmplane,nbcplane
FZBU 10G SFP+12 sbzplane
FZBU 10G SFP+11 nbuplane
Whenthisconfigurationisdeployed,nochangesareneededtotheEthernetinterface
configuration.

FEWS
g Note: TheInterfacelabelsarehard-codedintothecontrollerswitchinglogic.Theymust
beintroducedfollowingtheexactsamespellingpresentedinthisdocument.
Twootherconfigurationsaresupportedthatrequirereconfigurationduringfield
commissioning.
WhenM-planeandC-planeinterfacesareseparatedontheFCPU.

FCPU 1G SFP13 nbcplane
FCPU 1G SFP14 nbmplane
WhenthesouthboundZ1sbzplaneiscomprisedofasetof1Ginterfacesinsteadof
asingle10Ginterface.
g Note: Thenumberofavailable1Ginterfacesisdependentonhowmany1Ginterfaces
areinusefortheNorthboundinterfaces.Thereare101Gportsavailable:ifSFP14is
usedfornorthboundinterfacing,onlySFP15toSFP22willbeavailablefor
southbound.

FZBU 1G SFP14/15-SFP22 sbzplane
2.3.1.1 Confirming that the Ethernet Interfaces on Flexi Zone Controller are
configured correctly
Procedure
1 To veryfy the configuration status of the Flexi Zone Controller ethernet

interfaces, execute the following command:
show networking interface owner <owner> {[iface <iface>]?}
Where<owner>= FCPU-0 / FZBU-0and<iface> = nbmplane /
nbcplane / sbzplane / nbuplane
2.3.2 Changing interface IP addresses in the controller
Purpose
InordertochangetheIPaddressofinterfaceswithinthe,youneedtofirstdeletethe
existinginterface.

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
2 Re-add the interface with a new IP adress:

add networking address <owner> ip-address x.x.x.x/xx iface
<iface>
Wherex.x.x.x/xxisequaltothedesiredIP/mask.
Step example
add networking address /FZBU-0 ip-address 192.168.55.1/24
iface sbzplane
2.3.3 Setting up the Z1 Interface
Purpose
TheZ1interfaceconnectstheFZCtothenetworkofFZAPs.Itisamandatoryinterface
ontheControllerandfunctionsasthedefaultrouteforallFZAPsinaflatlayer2network
fortheZoneeNB.Inanon-flatlayer2network,suchasonewithmultipleenterprises
behindarouterorrouters,theZ1interfacewouldfunctionasthedefaultroutefromthe
edgerouteroneachenterprise.ThissectionshowshowtosetuptheZoneeNB
southboundZ1interfacewithinaFlexiZoneControllerthroughtheuseofSCLI
commands.
g Note: ThenameoftheZ1interfacemustbesbzplane.
Procedure
1 Setting up the Z1 Interface. The Z1 interface can be set up with or without a

VLAN.
Sub-steps
a) To set up the Z1 Interface without VLAN, enter the following command:

add networking instance default ether /FZBU-0 port sfp11
iface sbzplane admin up ipv4forwarding yes mtu 1500
ipv4rpfilter no proxy-arp no

FEWS
b) To set up the Z1 Interface with VLAN, enter the following commands:

add networking instance default ether /FCPU-0 port sfp11
iface ethsfp11 admin up ipv4forwarding yes ipv4rpfilter
no proxy-arp no
add networking instance default vlan /FCPU-0 realiface
ethsfp11 vid 520 vlaniface sbzplane
2 To set up the Z1 IP, enter the following command:

add networking address /FZBU-0 ip-address 192.168.55.1/24
iface sbzplane
Further information
WhentheZ1InterfaceissetupwithaVLANandtheIVIFobjectisnotprovidedtothe
FZAP,theFZAPsderivetheIVIFparametersfromtheresponsereceivedfromtheDHCP
serverandfromasubsetoftheIEIFparametersprovidedtotheFZAP.
TheVLANIDissettothevalueoftheVLANthattheDHCPserverison,andthelocalIP
addressissettothevalueprovidedbytheDHCPserver.Theremainingattributevalues
oftheIVIFarecopiedfromtheIEIF.TheIEIF::qosEnabledvaluemustbesetto
True.
Object Parameter Value

IVIF vlanId DHCP Server VLAN
localIpAddr Provided by DHCP Server
qosEnabled True(copiedfromIEIF)
sir (copiedfromIEIF)
sbs (copiedfromIEIF)
wfqSchedQueueWeigh (copiedfromIEIF)
Derived IVIF parameters
Related descriptions
EthernetInterfacesonFlexiZoneControlleronpage24
2.3.4 Setting up Flexi Zone Controller northbound interfaces
Purpose
AFlexiZoneControllerrequiresthesetupofatleasttwonorthboundinterfaces:a
dedicatedU-planeinterface,andajoinedM/C-planeinterface.
Alternatively,theM-planeandC-planeinterfacescanbesetupseparately,makinga
totalofthreenorthboundinterfaces.

FEWS
Related descriptions
EthernetInterfacesonFlexiZoneControlleronpage24
Related procedures
SettinguptheFZCU-planeinterfaceonpage28
SettinguptheFZCM-planeinterfaceonpage28
SettinguptheFZCC-planeinterfaceonpage29
2.3.4.1 Setting up the FZC U-plane interface
Purpose
TheU-planeinterfaceconnectstheFZCtotheServingGateway.Itisamandatory
interfaceontheControllerandfunctionsastheonlyinterfacethattransmitsandreceives
GTP-Ubearertrafficonthebackhaul(S1-U).ManagementandC-planeservicesarenot
providedonthisinterface.ThissectionshowshowtosetuptheZoneeNBnorthbound
U-planeinterfacewithinaFlexiZoneControllerthroughtheuseofSCLIcommands.
g Note: ThenameoftheU-planeinterfacemustbenbuplane.
Procedure
1 Set up the U-pane interface

TheU-planeinterfacecanbesetupwithorwithoutaVLAN
Select from available options
SetuptheU-planeInterfacewithoutVLANbyenteringthefollowingcommand:
iface nbuplane admin up ipv4forwarding yes mtu 1500
SetuptheU-planeInterfacewithVLANbyenteringthefollowingcommands:
no proxy-arp no
ethsfp12 vid 530 vlaniface nbuplane
2 Set up the U-plane IP by entering the following command:

add networking address /FCPU-0 ip-address 10.10.30.1/24
iface nbuplane
2.3.4.2 Setting up the FZC M-plane interface
Purpose

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
1 Set up the M-pane interface

TheM-planeinterfacecanbesetupwithorwithoutaVLAN.
SetuptheM-planeInterfacewithoutVLANbyenteringthefollowingcommand:
iface nbmplane admin up ipv4forwarding yes mtu 1500
SetuptheM-planeInterfacewithVLANbyenteringthefollowingcommands:
no proxy-arp no
ethsfp13 vid 540 vlaniface nbmplane
2 To set up the M-plane IP, enter the following command:

iface nbmplane add-user /SSH /Ne3sAgent /ClusterDNS
/ClusterNTP /RuimReplicator
3 Verify the interface creation:

show networking address iface 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
2.3.4.3 Setting up the FZC C-plane interface
Purpose

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
1 Set up the C-pane interface

TheC-planeinterfacecanbesetupwithorwithoutaVLAN.
SetuptheU-planeInterfacewithoutVLANbyenteringthefollowingcommand:
iface nbcplane admin up ipv4forwarding yes mtu 1500
SetuptheU-planeInterfacewithVLANbyenteringthefollowingcommands:
no proxy-arp no
ethsfp14 vid 530 vlaniface nbcplane
2 Set up the C-plane IP by entering the following command:

iface nbcplane
2.3.5 Flexi Zone Controller integrated DHCP server

TheFlexiZonecontrollerprovidesanintegratedDHCPservertoprovideIPaddress
assignmenttoaccesspoints.TheDHCPserverwillautomaticallyconfigurethe
parametersthatitprovidetotheaccesspointsbasedontheconfigurationofthe
sbzplane.TheDHCPserverlooksattheIPAddressandsubnetmaskofthesbzplane
andcreatesadynamicpoolofaddressesbasedonstandardIPaddressingruleswhere
thenetworkaddress,broadcastaddressandthedefaultgateway(sbzplane)addressare
excludedfromthepoolbutallotheraddressesinthesubnetareavailableforassignment
toaFZAP.
ForadditionalinformationonthecommandsshowninthissectionrefertoFlexi Zone
Controller SCLI Commands.
2.3.5.1 Adding DHCP Server Static MAC to IP assignment

Purpose
TheDHCPserversupportsstaticmappingofanIPaddresstoMACaddress.Inorderto
assignastaticmappingthefollowingstepsshouldbeperformed.

FEWS
Before you start
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
2 Add the static mapping to the IP address.add flexizone dhcp ip <apip>

mac <mac>
add flexizone dhcp ip <apip> mac <mac>
Where<apip>istheFZAPIPaddressand<mac>itscorrespondingMACaddress.
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
3 If step 1 showed that the IP address is currently used by a different FZAP, do

one of the following before connecting the FZAP that is getting the static
mapped IP to the network:
a) Waitonehourtoallowtheexistingleasetoexpire.
b) UsetheconfigurationresetbuttonontheFZAPthatcurrentlyhastheleaseto
resetitbackastatethattheFZAPwillacquireadifferentleasefromtheDHCP
server.
c) Shutoff(ordisconnectfromthenetwork)theFZAPthatcurrentlyhasthelease
foronehourtoallowtheleasetoexpire.

FEWS
g Note: FailuretoperformoneoftheabovestepswillresultinduplicateIPaddress
usageinthenetwork.
2.3.5.2 Configuring DHCP server for additional enterprises
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

FEWS
Thisisoptional.TheMTUrangemustbewithin576-1644octets,andissettoa
defaultvalueof1500iftheMTUsizeisnotprovided.
8. AnystaticIPtoMACmappings
StatipIPstoMACmappingscanbeaddedpostconfigurationbyfollowingstepsin
AddingDHCPServerStaticMACtoIPassignment.
Procedure
1 Check that the system is configured for shared-backhaul.

Sub-steps
a) Execute following command to verify the state of shared-backhaul.

show flexizone shared-backhaul state
b) If shared-backhaul state is OFF, enable it by using the following command:

set flexizone shared-backhaul state L3 route-ip <Gateway
router on the sbzplane network>
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
3 (Optional) Add a static IP to MAC mappings.

RefertoAddingDHCPServerStaticMACtoIPassignment.

FEWS
2.3.6 Setting up a CMP Server IP for the Flexi Zone Controller
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.
Migrating a Flexi Zone Controller to a customer provided PKI
Modifying the customer provided PKI of a Flexi Zone Controller
Backing out from a customer provided PKI to an internal PKI
2.3.6.1 Migrating a Flexi Zone Controller to a customer provided PKI
Purpose
TomigratetheFZCfromtheinternalPublicKeyInfrastructure(PKI)toacustomer
providedPKI,aseriesofcommandsmustbeintroducedintotheFZCfsclishbash.
Procedure
1 Start a read-write transaction in the Configuration Directory:

start transaction

FEWS
2 set security cert default cmp ip-addr <IP address of CA

server> port <port number> psk <psk-value> ref-num <refnum-
value> server-path <path> ca-subjectname <subject name>
3 set security cert default ee-cert-profile subject-name

<subject name>
4 One of these two commands:

Sub-steps
a) set security cert default ee-candidate-key file keyfile

/share/eekey.pem
b) set security cert default ee-candidate-key autogenerate
5 start security cert default cmp-request initialize

certdirectory /share/
6 set security cert default ca-cert cert-file

/share/default.rootca.cacert.pem ca-id <ca-id>

/share/default.interca1.cacert.pem ca-id <int-ca-id>
8 set security cert default ee-cert cert-file

/share/default.eecert.pem key-file /share/eekey.pem
validation enabled
9 show security cert default ee-cert
10 show security cert default ca-cert intermediate
11 show security cert default ca-cert trust-anchor
12 Commit the Configuration Directory transaction.

commit transaction

FEWS
13 add fzc-ipsec sb bypass allzone
Result
OncetheabovecommandsarerunontheFZC,theFZAPwillbetriggeredtousethe
sameCMPserveranddownloadcertificatesusingCMP.
g Note: Theaboveorderandsetofcommandsalsocoversthefollowingscenarios:
UpdateRootCAcertificate(duetoexpiration/revocation)
ReplacementofEndEntitycertificate(duetoexpiration/revocation)
ChangeinPKIhierarchy(additionorremovalofIntCA)
2.3.6.2 Modifying the customer provided PKI of a Flexi Zone Controller
Purpose
TomigratefromonecustomerprovidedPublicKeyInfrastructure(PKI)toanother
customerprovidedPKI,aseriesofcommandsmustbeintroducedintotheFZCfsclish
bash.
Procedure

start transaction

FEWS

server> port <port number> psk <psk-value> ref-num <refnum-
value> server-path <path> ca-subjectname <subject name>
3 set security cert default ee-cert-profile subject-name

<subject name>

Sub-steps

/share/eekey.pem
5 start security cert default cmp-request initialize

certdirectory /share/

/share/default.rootca.cacert.pem ca-id <ca-id>


validation enabled

commit transaction

FEWS
13 delete fzc-ipsec sb bypass allzone
14 add fzc-ipsec sb bypass allzone
Result
ThiswillensurethatthepoliciesareupdatedwiththenewCMPserverIPaddress.
2.3.6.3 Backing out from a customer provided PKI to an internal PKI in a

Flexi Zone Controller
Purpose
TomigratefromonecustomerprovidedPublicKeyInfrastructure(PKI)backtothe
internalPKI,aseriesofcommandsmustbeintroducedintotheFZCfsclishbash.
Procedure

start transaction
2 set security cert default cmp ip-addr 0.0.0.0
3 delete security cert <domain> ca-cert all

commit transaction
2.3.7 Managing certificates on the Flexi Zone Controller
2.3.7.1 Updating internal CA certificates

Purpose
ForthecaseswhereanendentityorIntCAcertificatesneedstobeupdatedorrenewed,
thefollowingcommandsneedtobeexecutedintheordershown.

FEWS
Procedure
1 start transaction

server> port <port number> server-path <path>

Sub-steps

/share/eekey.pem
4 start security cert default cmp-request key-update cert-

directory /share/


validation enabled

commit transaction
2.3.7.2 Checking certificates expiration in NE3S/WS

Purpose
Tochecktheexpirationdateoftheinstalledcertificateswiththecertificatesmanagement
SCLIcommands.

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)

FEWS
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
.........
.........
##############################################################
2.3.7.3 Certificate expiration alarm handling in NE3S
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.
Before you start

YoumusthavethefsConfigViewpermissiontoviewtheNE3Sservice
configuration.
GothroughthesectionCertificate expirationtoknowthattheexpiredcertificateisa
CAcertificate.

FEWS
Procedure
1 Check if the expired CA certificate is for:
TheNE3Sdomain,gotostepCheck whether NE3S is using the TLS mode.

TheDefaultdomain,gotostepEnter the SCLI shell.
2 Enter the SCLI shell.
3 Confirm if the certificate alarm in the default domain affects the certificate
belonging to NE3S.
Enteroneofthefollowingcommanddependingonwhethertheexpiredcertificatea
CAoranEEone:
show security cert ne3s-ws ca-cert ca-id common cert-type

new-with-new
show security cert ne3s-ws ee-cert
Thecommandoutputcanresultinthefollowingscenario:
Certificateisdisplayed.ItmeansthatNE3Sserviceisusingitsowncertificate
fromthene3sdomainandisnotimpactedbythealarm.Youcanabortthe
instructions.
Nocertificateisdisplayed.ItmeansthatNE3Sserviceisusingthecertificate
presentinthe defaultdomainandisimpactedbythealarm,gotostep
Check whether NE3S is using the TLS mode.
Example output:
###########################################################
####
Domain : ne3s
CA-ID : common
Certificate Type : new-with-new
###########################################################
####
No CA certificate installed with this cert-type
###########################################################
####
4 Check whether NE3S is using the TLS mode.

TocheckwhetherNE3SisusingtheTLSmode,enterthefollowingcommand:
show mgmt-service ne3s-ws config common all
IftheoutputindicatesthatConnection mode : clear-text,thenNE3Sisnot
usingcertificatesandtheexpiryofthecertificatewillnotimpactNE3Sfunctionality.
Youcanaborttheinstructions.

FEWS
IftheoutputindicatesthatConnection mode : tls,thenNE3Swillnotbeable

tosenddatatoand/orreceiveddatafromNetActunlessthecertificateisreplaced.
Connection between NE and Netact over NE3S
ThereareEEandCAcertificates.
IfEEcertificateexpires,itimpactsnetactconnectingtoNEbutNEcanconnectto
netact.IfCAcertificateexpires,itimpactsNEconnectingtonetactbutnetactcan
connecttoNE.
g Note: Formoreinformationonhowtoreplacethecertificate,referto
Replacing the expired certificated with a new active certificate
Replacing the expired certificate with a new active certificate.

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.
Replacing the expired certificate with a new active certificate.

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.
2.3.8 Managing IPSec policies in the Flexi Zone Controller
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).

FEWS
Related procedures
ActivatingandconfiguringLTE2017:IPSecSupportforFlexiZoneControlleronpage45
DeactivatingLTE2017:IPSecSupportforFlexiZoneControlleronpage49
2.3.8.1 Activating and configuring LTE2017: IPSec Support for Flexi Zone
Controller
Before you start

TheactivationoffeatureLTE2017: IPSec Support for Flexi Zone Controllerassumesthat
theFlexiZoneControllerissuccessfullycommissionedandconnectedviaSSHtoafield
engineeringworkstation(FEWS).TheFEWSSSHconnectionwillserveastheinterface
tocommunicatewiththecontroller.
Theaddoperationwithinthefzc-ipseccommanddomainisusedforestablishing
andbypassingIPsecprotectionwithinaspecifictrafficplane.Theshowoperationwithin
thatsamefzc-ipsecdomaincanbeusedtoconsultthepolicystatusofsaid
connections.
Table 2 add fzc-ipseccommands

Command Parameter Attribute Description
addfzc-ipsec nb Eithernborsbis AddsnorthboundIPsec
mandatory configuration.
sb AddssouthboundIPsec
configuration.
addfzc-ipsecsb bypass Eitherbypassor AddssouthboundIPsecbypass
protectoptionis policyrule.
mandatory
protect AddssouthboundIPsec
configurationwithprotectpolicy
rule.
addfzc-ipsecsb allzone Mandatory AddssouthboundIPsecbypass
bypass policyruleforallplanes.
addfzc-ipsecsb allzone Mandatory AddssouthboundIPsec
protect configurationwithprotectpolicy
ruleforallplanes.
addfzc-ipsecnb bypass Eitherbypassor AddsnorthboundIPsecbypass
protectoptionis policyrule.
mandatory
protect AddsnorthboundIPsec
rule.
addfzc-ipsecnb cmp Eithercmp,cplaneor AddsnorthboundIPsecbypass
bypass mplaneoptionis policyruleforCMPserver
mandatory
cplane AddsnorthboundIPsecbypass
policyruleforC-plane.
mplane AddsnorthboundIPsecbypass
policyruleforM-plane.
addfzc-ipsecnb cplane Eitheruplane,cplane AddsnorthboundIPsec
protect ormplaneoptionis configurationwithprotectpolicy
mandatory ruleforC-plane.

FEWS
Table 2 add fzc-ipseccommands(Cont.)

mplane AddsnorthboundIPsec
ruleforM-plane.
uplane AddsnorthboundIPsec
ruleforU-plane.
addfzc-ipsecnb remote-tep< Mandatory remoteIPSectunnelendpoint
protectcplane remote-tep- IPv4address
value>
addfzc-ipsecnb template< Optional IKEtemplatename
protectcplane template-
remote-tep<remote- value>
tep-value>addfzc-
ipsecnbprotect vpn<vpn- VPNobjectname
mplane value>
ike-version< IKEversion[ikev1|ikev2],
ike-version- default=ikev2
value>
Private-key< privatekeyfilename,default=
private-key- defaultPrivatekey.pem
value>
certificate< certificatefileforIKE
certificate- authentication,default=
value> defaultCertificate.pem
ca-certificate CAcertificatefileforIKE
<ca- authentication,default=
certificate- defaultCaCertificate.pem
value>
addfzc-ipsecnb remote-tep< Mandatory remoteIPSectunnelendpoint
protectmplane remote-tep- IPv4address
value>
addfzc-ipsecnb template< Optional IKEtemplatename
protectmplane template-
tep-value>
vpn<vpn- VPNobjectname
value>
ike-version< IKEversion[ikev1|ikev2],
ike-version- default=ikev2
value>
value>
<ca- authentication,,default=
certificate- defaultCaCertificate.pem.
value>

FEWS
Table 2 add fzc-ipseccommands(Cont.)

remote-tep Mandatory remoteIPSectunnelendpoint
<remote-tep- IPv4address
value>
addfzc-ipsecnb template Optional IKEtemplatename
protectuplane <template-
tep-value>
vpn<vpn- VPNobjectname
value>
ike-version IKEversion[ikev1|ikev2],
<ike-version- default=ikev2
value>
value>
<ca- authentication,,default=
certificate- defaultCaCertificate.pem.
value>
ThefollowingsectionsprovidethewrappercommandscoveringthemostcommonIPsec
activationusecases.
FormoreinformationontheseandothercommandsseeFlexi Zone Controller SCLI
Commands (DN09210703).
Applying IPsec to the FZC southbound interface Z1

add fzc-ipsec sb bypass allzone
add fzc-ipsec sb protect allzone
Applying IPsec to the FZC southbound interface (Z1) and to the northbound
user plane
Sub-steps
1 add fzc-ipsec nb protect uplane remote-tep <IP>

Where<IP>istheparticularIPforthenorthboundU-plane.
2 Protect the southbound interface


FEWS
control and management planes
Sub-steps
1 add fzc-ipsec nb protect cplane remote-tep <IP>

Where<IP>istheparticularIPforthenorthboundC-plane.
2 add fzc-ipsec nb protect mplane remote-tep <IP>

Where<IP>istheparticularIPforthenorthboundM-plane.
3 add fzc-ipsec nb bypass cmp

control, management and user planes
Sub-steps





FEWS
Applying IPsec to the FZC northbound control, management and user planes
Sub-steps



2.3.8.2 Deactivating LTE2017: IPSec Support for Flexi Zone Controller
Before you start

ThedeactivationoffeatureLTE2017: IPSec Support for Flexi Zone Controllerassumes
thattheFlexiZoneControllerissuccessfullycommissionedandconnectedviaSSHtoa
fieldengineeringworkstation(FEWS).TheFEWSSSHconnectionwillserveasthe
interfacetocommunicatewiththecontroller.
Thedeleteoperationwithinthefzc-ipseccommanddomainisusedforestablishing
andbypassingIPsecprotectionwithinaspecifictrafficplane.Theshowoperationwithin
thatsamefzc-ipsecdomaincanbeusedtoconsultthepolicystatusofsaid
connections.
Table 3 delete fzc-ipseccommands

Command Parame Attribute Description
ter
deletefzc- nb Eithernborsboption DeletesnorthboundIPsecconfiguration.
ipsec ismandatory
sb DeletessouthboundIPsecconfiguration.
deletefzc- bypass Eitherbypassor DeletessouthboundIPsecbypasspolicyrule.
ipsecsb protectoptionis
protect mandatory DeletessouthboundIPsecprotectpolicyrule.
deletefzc- allzone Mandatory DeletessouthboundIPsecbypasspolicyrule

ipsecsb forallzone.
bypass
deletefzc-
ipsecsb
protect allzone Mandatory DeletessouthboundIPsecconfigurationwith
protectruleforallzone.

FEWS
Table 3 delete fzc-ipseccommands(Cont.)

Command Parame Attribute Description
ter
deletefzc- bypass Eitherbypassor DeletesnorthboundIPsecbypasspolicyrule.
ipsecnb protectoptionis
protect mandatory DeletesnorthboundIPsecprotectpolicyrule.
deletefzc- cmp Eithercmp,cplaneor DeletesnorthboundIPsecbypasspolicyrule

ipsecnb mplaneoptionis forCMPserver.
bypass mandatory
cplane DeletesnorthboundIPsecbypasspolicyrule
forC-plane.
mplane DeletesnorthboundIPsecbypasspolicyrule
forM-plane.
deletefzc- cplane Eitheruplane,cplane DeletesnorthboundIPsecconfigurationwith
ipsecnb ormplaneoptionis protectpolicyruleforC-plane.
protect mandatory
mplane DeletesnorthboundIPsecconfigurationwith
protectpolicyruleforM-plane.
uplane DeletesnorthboundIPsecconfigurationwith
protectpolicyruleforU-plane.
ThefollowingsectionsprovidethewrappercommandscoveringthemostcommonIPsec
deactivationusecases.
FormoreinformationontheseandothercommandsseeFlexi Zone Controller SCLI
Commands (DN09210703).
Removing IPsec from the FZC southbound interface Z1

delete fzc-ipsec sb bypass allzone
Removing IPsec from the FZC southbound interface (Z1) and the northbound
user plane
Sub-steps
1 delete fzc-ipsec nb protect uplane remote-tep <IP>

2 Revoke protection of the southbound interface


FEWS
Removing IPsec from the FZC southbound interface (Z1) and from the
northbound control and management planes
Sub-steps
1 delete fzc-ipsec nb protect cplane remote-tep <IP>

2 delete fzc-ipsec nb protect mplane remote-tep <IP>

3 delete fzc-ipsec nb bypass cmp

Removing IPsec to the FZC southbound interface (Z1) and to the northbound
control, management and user planes
Sub-steps
1 delete fzc-ipsec nb protect cplane remote-tep <IP>

2 delete fzc-ipsec nb protect mplane remote-tep <IP>

3 delete fzc-ipsec nb protect uplane remote-tep <IP>

4 delete fzc-ipsec nb bypass cmp

2.3.9 Configuring static routes for IPv4

Purpose
ToconfigurethestaticroutesforIPv4.

FEWS
Before you start

Ifthevirtualroutingisused,checkthattheroutinginstancesarecreatedandinterfaces
aresettothecorrectroutinginstances.Inthecommandspresentedinthischapter,the
routinginstancesaredefinedwiththeoptionalinstance <name>parameterthatis
attachedinthecommands.Inthecommandsyntaxtheparameterisplacedrightafter
theroutingparameter.
g Note: Usetransactionstobundlemultiplechangesintoonebiggerchange.Use
configurationlockingfeaturetopreventotherusersfrominterferingwithyour
configurationchanges.
Procedure
1 Define a static route to the next hop gateway.

Youcandefinemultiplestaticroutestonexthopgateways.Thestaticroutedefinesa
nexthopgatewayforpacketsthataredestinedtoaspecifiedIPaddressrange.
Definetheroutewiththefollowingcommand:
set routing [instance <name>] node <name> static-route
<IP_PREFIX|default> nexthop gateway address <address> [priority <1-
8>] on
Further information
Anindividualstaticroutepergatewaycanberemovedwiththefollowingcommand:
<IP_PREFIX|default> nexthop gateway address <address> off
Allroutesforagivensubnetcanberemovedwiththefollowingcommand:
<IP_PREFIX|default> off
Fornodeswheretheroutingdaemonisnotdeployed,theMTUsizeandsourceIP
addresscanbesetforthedefaultstaticrouteusingthefollowingcommands:
<IP_PREFIX|default> mtu <mtu-size>
<IP_PREFIX|default> source <IP-address>
2 Enable packet rejecting.

Insteadofforwardingpacketstothenexthop,youcanoptionallycreaterejector
blackholetyperoutes.Rejectcausespacketstobedroppedandunreachable
messagestobesenttopacketoriginators.
Blackholecausespacketstobedroppedbutdoesnotcauseunreachablemessages
tobesent.Thesecanbeused,forexample,todroptemporarilyallpackets
generatedbyadenialofserviceattack.

FEWS
Therejectandblackholetyperoutesarecreatedwiththefollowingcommands:
set routing [instance <name>] node <node> static-route
<IP_PREFIX|default> nexthop reject
<IP_PREFIX|default> nexthop blackhole
3 Enable or disable the BFD protocol for an existing static route.

Thesingle-hopBFDcanbeenabledordisabledusingthefollowingcommand:
set routing [instance <name>] node <node_name> static-route
<IP_PREFIX|default> nexthop gateway address <address> [priority <1-
8>] [bfd-tx-interval <tx-interval |default>] [bfd-rx-interval <rx-
interval|default>] [bfd-monitoring <enabled|disabled>] [bfd-detect-
mult <multvalue|default>] on
Toenablethesingle-hopBFDsession,setthebfd-monitoringparameterto
enabled.Todisablethesingle-hopBFDsession,setthe bfd-monitoring
parametertodisabled.
g Note: Formulti-hopBFDconfiguration,seeBFD configuration.
4 Configure the BFD hold time for existing routes.

Theparameterbfd-static-holdtimeisusedtoconfiguretheholdtimeforall
BFDsessionsforstaticroutes.Thecommandisasfollows:
set routing [instance <name>] node <node> bfd-static-holdtime <bfd-
static-holdtime>
TodisplaytheBFDholdtimeparameterconfiguredforthestaticroute,enterthe
followingcommands:
show routing [instance <name>] node <node> bfd-static-holdtime config
show routing node <node> bfd-static-holdtime config all
5 Configure protocol rank for existing routes.

Definetheprotocolrankfortheexistingstaticroutes.Rankisusedtodetermine
whichrouteisusedwhenthereareseveralroutesfromdifferentprotocolstothe
samedestination.
Thenewrankforthegivenstaticrouteisdefinedwiththefollowingcommand:
<IP_PREFIX|default> rank <0-255>
6 Monitor static routes.

Monitorthestatusofthestaticrouteswiththecommand:
show routing [instance <name>] node <name> static-route config [all]
Further information

FEWS
Detailsoftheparametersoftheroutingcommandareshowninthetablebelow.
Table 4 Parametersforconfiguringstaticroutes
Parameter Description Value range
instance <name> Theroutingconfigurationis -

appliedtothevirtualrouting
instancespecifiedbythis
parameter.Ifnoinstanceis
specified,therouting
configurationisappliedtothe
defaultroutinginstance.Thisis
anoptionalparameter.
node <node-name> Thisparameterspecifiesthe -

nodenamewherethestatic
routeconfigurationtakesplace.
address <address> ThisparameterspecifiestheIP -

addressofthegateway.
mtu <mtu-size> Thisparameterspecifiesthe Theallowedvaluerangeis

MTUvalueofthedefaultstatic 1280to9000.
route.Thisparameteris
optional.
g Note: Thisparameteris
supportedonlyfornodes
inwhichtheRouting
Daemonisnotdeployed.
source <IP-address> Thisparameterspecifiesthe -

sourceIPaddressorrangeof
IPaddressesselectorwrittenin
format<IP-address/mask>.
Optionalparameter.
g Note: Thisparameteris
supportedonlyfornodes
inwhichtheRouting
Daemonisnotdeployed.
<IP_PREFIX|default> Thisparameterspecifiesthe Theallowedvaluesare:

destinationnetworkaddressin
theformofprefix/mask,where prefix:unicastIPv4
theprefixisunicastIPv4 address
addressandthemaskisa mask:networkmaskinthe
networkmask. range1to32.
priority <1-8> Thisparameterspecifiesthe Theallowedrangeisfrom1to

priorityofthestaticroute. 8.

FEWS
Table 4 Parametersforconfiguringstaticroutes(Cont.)
Thehigherpriority(lowervalue)
nexthopsarepreferred.
Switchingovertothenextroute
inthelisthappensonlyifthe
interfacefails.Itdoesnot
happenfornon-reachablenext
hopsiftheinterfaceisstillup.If
thepriorityisthesameandthe
interfaceisup,itwillbean
equalcost,multipathroute.
bfd-tx-interval Thisparameterspecifiesthe Theallowedvaluesareinthe

<tx-interval minimumintervalbetweenthe range50msto60000mswitha
|default> transmittedBFDcontrol granularityof50ms.The
packetsinmilliseconds.This defaultvalueis1000ms.
parameterisoptional.
g Note: Thisparameter
acceptseitherthe
numericvalueorthe
valuedefault.Ifthe
valuedefaultisused,
thenthevalueof
bfd-tx-intervalis
settoadefaultvalueof
1000ms.
bfd-rx-interval Thisparameterspecifiesthe Theallowedvaluesareinthe

<rx- minimumintervalbetweenthe range50msto60000mswith
interval|default> receivedBFDcontrolpackets agranularityof50ms.The
inmilliseconds.Thisparameter defaultvalueis1000ms.
isoptional.
acceptseitherthe
numericvalueorthe
valuedefault.Ifthe
valuedefaultisused,
thenthevalueof
bfd-rx-intervalis
1000ms.
bfd-detect-mult Thisparameterspecifiesthe Theallowedvaluerangeis

<mult- desireddetectiontimemultiplier from1to50.Thedefaultvalue
value|default> fortheBFDcontrolpacketson is4.
thelocalsystem.The
negotiatedcontrolpacket
transmissioninterval,multiplied
bythisparameter,isthe
detectiontimeforaparticular
BFDsession.Thisparameteris
optional.

FEWS
Table 4 Parametersforconfiguringstaticroutes(Cont.)
acceptseitherthe
numericvalueorthe
valuedefault.Ifthe
valuedefaultisused,
thenthevalueof
bfd-detect-multis
4.
bfd-monitoring Thisparameterenablesor Theallowedvaluesare

<enabled|disabled> disablestheBFDprotocolfor enabledanddisabled.
thestaticroute.Thisparameter Thedefaultvalueisdisable.
isoptional.
bfd-static-hold- Thisparameterdefinesthe Theallowedvaluesrangeis0

time <bfd-static- hold-uptimetimerforstatic to900seconds.Thedefault
hold-time> route.Theholduptimedelays valueis0seconds.
thestaticrouteswitch,when
Thevalue0disablesthebfd-
thefailedpathrecovers.When
staticholdtimeparameter.
theBFDsessionisactive
again,thesystemdefersthe
reinstallationoftheboundstatic
routesbackintotherouting
tableforaconfigurabletime.
Thisholduptimetimerprevents
therecurringswitchoverincase
ofunstablelinks.
2.3.10 Configuring NTP

Purpose
TheNetworkTimeProtocol(NTP)isusedforsynchronizingtheinternaltimeofthe
clustertoanexternalreferencetimesource,anditsuseisstronglyrecommended.For
redundancy,uptothreeexternalNTPserverscanbeusedbythesystem.NTPprovides
accuracywithinamillisecondinalocalareanetwork(LAN)anduptoafewtensof
millisecondsinawideareanetwork(WAN).
TheNTPdaemonrunninginaclientorservermakesstatisticalcalculationsfromthe
incomingtimestamps.Theaccuracyofthetimeimprovesthelongerthedaemonis
running.Clocksinthenetworkmakeanabruptjumptothecorrecttimeonlyduringtime
initialization(ifthetimedifferenceisgreaterthan1000seconds).Otherwise,clientsor
serversmaintaintheircorrecttimeonacontinuousbasisbyrequestingtimestampsfrom
acommonNTPserveratregularintervals.
TheaccuracyoftheNTPserverisindicatedbyastratumnumber.Theprimaryservers

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
1 Check the current NTP configuration.

ToseethecurrentNTPconfiguration,enterthefollowingcommand:
show networking-service ntp
IftheNTPaddressesarenotadded,therewillbenoprintout.
2 If an NTP configuration exists in the system, delete the current NTP

configuration.
ToaddanewNTPconfiguration,thecurrentconfigurationmustbedeletedfirst.
DeletethecurrentNTPconfigurationbyenteringthefollowingcommand:
delete networking-service ntp
3 Assign the addresses of external NTP servers to the system.

Usetheadd networking-service ntpcommandtoassigntheIPaddresses
oftheexternalNTPservers(forwarders)tothesystem.UptothreeexternalNTP
serverscanbeassigned.
Thesyntaxofthecommandisasfollows:
add networking-service ntp forwarder <IP address or host name of an
external NTP server>
4 Modify the NTP configuration.

TomodifythecurrentNTPconfiguration,enterthefollowingcommand:
set networking-service ntp [add-forwarder <IP address or host name of
an external NTP server>] [delete-forwarder <IP address or host name
of an external NTP server>]

FEWS
5 Verify the NTP configuration.

ToseethecurrentNTPconfiguration,enterthefollowingcommand:
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:
Theprintoutinthisexampleisasfollows:
forwarder: 10.20.30.40
forwarder: 10.20.30.50
Further information
Table5:ParametersforNTPconfigurationshowstheparametersfornetworking-
service dnscommands:
Table 5 ParametersforNTPconfiguration
Parameter Description Value Range
forwarder <address> TheIPaddressorthehost UptothreeexternalNTP

nameoftheexternalNTP serverscanbeassignedto
server. thesystem.
add-forwarder <IP ThisparameteraddstheIP

address or host name addressorthehostnameofan
of an external NTP externalNTPserver.
server>
delete-forwarder <IP ThisparameterremovestheIP

address or host name addressorthehostnameofan
of an external NTP externalNTPserver.
server>
2.3.11 Configuring DNS

Purpose
Thedomainnamesystem(DNS)isadistributeddatabasethatoffers,amongothers,
mappingbetweenIPaddressesanddomainnames(hostnames).TheDNS
infrastructureconsistsofDNSservers(alsocallednameservers)andDNSclients(also
calledresolvers)withthemaintaskofqueryinginformationfromDNSservers.

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
1 Check the current DNS configuration.

TocheckthecurrentDNSconfiguration,enterthefollowingcommand:
show networking-service dns
IftheDNSaddressesarenotadded,thereisnoprintout.
2 If a DNS configuration exists in the system, delete the current DNS

configuration.
ToaddanewDNSconfiguration,deletethecurrentconfigurationfirst.Deletethe
currentDNSconfigurationbyenteringthefollowingcommand:
delete networking-service dns
3 Assign the addresses of external DNS servers to the system.

Usetheadd networking-service dnscommandtoassigntheIPaddresses
oftheexternalDNSservers(forwarders)tothesystem.Thesyntaxofthecommand
isasfollows:
add networking-service dns forwarder <forwarder_address>
4 Modify the DNS configuration.

TomodifythecurrentDNSconfiguration,enterthefollowingcommand:
set networking-service dns [add-forwarder <forwarder_address>]
[delete-forwarder <forwarder_address>]

FEWS
5 Verify the DNS configuration.

ToseethecurrentDNSconfiguration,enterthefollowingcommand:
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:
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:
Further information
Table 6 ParametersforDNSconfiguration
Parameter Description Value Range
forwarder <address> TheIPaddressoftheexternal UptothreeexternalDNS

DNSserver. serverscanbeassignedto
thesystem.
ForwarderisoneoftheDNS
serversthatloadsthezone
informationfromaDNSserver
higherupinthehierarchy
(eitheramasterserveror
anotherforwardingserver).
add-forwarder ThisparameteraddsanIP
<forwarder_address> addressofanexternalDNS
server.
delete-forwarder ThisparameterremovesanIP
<forwarder_address> addressofanexternalDNS
server.

FEWS
2.3.12 Setting up the primary LDAP server & RUIM service on a

This section shows how to set up the primary LDAP server and configure the RUIM
service within a Flexi Zone Controller.
Purpose
Thecorrectconfigurationofanremoteuserinformationmanagement(RUIM)serviceis
requiredfortheFlexiZoneControllerO&Mintegtation.
Procedure
1 Enter the following command to configure the RuimReplicator service on the

M-plane interface:
set networking address dedicated /FCPU-0 add-user
/RuimReplicator ip-address 10.10.40.1 iface nbmplane
Sub-steps
a) Verify the procedure:

show networking address iface nbmplane
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
2 Configure the RUIM server:

set user-management ruim nms-ldap-config {{primary-server-
port <primary-server-port> secondary-server-port
<secondary-serverport> primary-server-ip <primary-server-
ip> secondary-server-ip <secondary-server-ip> primary-
config-root-dn <primary-configroot-dn> secondary-config-
root-dn <secondary-config-root-dn> primary-people-root-dn
<primary-people-root-dn> secondarypeople-root-dn
<secondary-people-root-dn> primary-serverconnection- mode
<primary-server-connection-mode> secondaryserver-
connection-mode <secondary-server-connection-mode> primary-
server-verification-policy <primary-serververification-
policy> secondary-server-verification-policy <secondary-
server-verification-policy>}}
Wherethecommandparametersstandforthefollowing:

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.

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
set user-management ruim nms-ldap-config primary-server-

port 389 primary-server-ip 10.10.40.5 primary-config-root-
dn cn=FlexiPlatform4,ou=LDAPConfData,ou=ruim,ou=region-
911080,ou=regions,ou=netact,dc=noklab,dc=net,dc=localdomain
primary-people-root-dn ou=people,ou=accounts,ou=region-
911080,ou=regions,ou=netact,dc=noklab,dc=net,dc=localdomain
primary-serverconnection-mode plain-text primary-server-
verification-policy ignore
Sub-steps

show user-management ruim nms-ldap-config
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,

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
Secondary NMS LDAP Server Configuration

IP address :
Port : default (389)
Config location in NMS :
Account location in NMS :
Connection mode : default (tls)
Verification policy : default (full-except-hostname-check)
3 Configure the RUIM user:

show user-management ruim nms-ldap-account user
<user_name> password <user_password>
Step example
show user-management ruim nms-ldap-account user 111111
password test123
Sub-steps

show user-management ruim nms-ldap-account
Step example
NMS LDAP Username : uid=111111,
ou=People,
ou=accounts,
ou=region-911080,
ou=regions,
ou=netact,
dc=noklab,
dc=net,

FEWS
dc=localdomain
NMS LDAP Password : test123
2.4 Managing FZC physical management port

This section describes how to enable and disable the physical management port in a
Flexi Zone Zontroller.
Purpose
Disablingthephysicalmanagementportisrecommendedinordertominimizesecurity
risksatZoneeNBdeployments.
g Note: ThisprocedureshouldonlybecarriedoutafterallSCLI/FEWScommissioning
stepshavebeensuccessfullycompleted.ItshouldbecarriedoutthoughaSSH
session.ItisrecommendedtowaituntiltheentireZoneeNBhasbeencompletely
commissioned.
Before you start

ThestepsdescribedinthissectionmustbeperformedwithintheFZCSCLIshell.
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

IntegratingFlexiZoneControllertoNetActthroughthe CommissioningFlexiZoneController
NES3link
3 Integrating Flexi Zone Controller to NetAct

through the NES3 link
This section describes how to integrate the Zone eNB to NetAct through the NES3
interface.
TheintegrationoftheFlexiZoneControllertoNetActthroughtheNE3S/WSinterfaceis
documentedseparatelyintheIntegrating Flexi Zone Controller to NetActdocument
(DN09188976).

CommissioningFlexiZoneController CommissioningFlexiZoneControllerthroughBTSSite
Manager
4 Commissioning Flexi Zone Controller through

BTS Site Manager
This section describes how to commission a Flexi Zone Controller through BTS Site
Manager.
BeforethecommissioningoftheFZCLTEstackcanbegin,itisnecessarytoverify
softwarecomponentsviaSCLI/FEWScommissioning.Seeformoreinformation.
4.1 About BTS Site Manager

Description of BTS Element Manager.
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.
ToaccesshelpfromtheHelpmenu,chooseHelpBTS Site Manager Help.

Toaccesshelpfromviewsanddialogboxes,pressF1andthehelpsystemwill
displaytherelevanthelptopic.

Ifthereisa buttoninaview,dialogboxormessagebox,clickingitwillalso
displaythecorrespondinghelptopic.
4.1.1 Installing BTS Site Manager

Purpose
FollowtheseinstructionstoinstallBTSSiteManagersoftwareonyourPC.
Before you start

YoushouldbefamiliarwithhowtoinstallsoftwareonyourPCandhowtomanageit.
Notethatitisrecommendedthatyouhaveadministratorrightsonyouroperatingsystem.
TosetupandinstalltheBTSSiteManager,youneedtohaveanInternetconnection
availabletodownloadtheBTSSiteManagerinstallationfilefromNokiaNetworksOnline
Services(NOLS).Theinstallationfilecanalsobedeliveredonaremovablemedia(CD-
ROM,forexample).

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
1 Download the BTS Site Manager installation file.

SavethefileonyourPC.Ifthefileiszipped,unzipitandthenlocatethe.exefile.
NotethattheaboveexampleisforaPCrunningonWindowsOS.Withother
operatingsystemsalsochangetothe.binfilemayberequired.
2 If you have BTS Site Manager running on your PC, close it before starting the
installation.
3 Double-click the .exe file to start the installation.

IfyouareusingLinux,followthesesteps:
a) UseXmanagertoconnecttoLinuxcomputer.

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).
4.1.2 Launching BTS Site Manager

This section describes how to launch the BTS Site Manager application.
Before you start

Makesurethefollowingconditionsarefulfilled:
IfthePCisconnectedtotheFSMLMPport,specifyyourPC'snetworksettingsto
matchthefollowingsettings:

Manager
IPaddress:192.168.255.130
Subnetmask:255.255.255.0
IfyouwanttoestablishaconnectiontotheBTSsitelocally,connectthePCtothe
FlexiZoneControllerLANport1usingatwistedpairEthernetcablewithanRJ-45
connector.Inaremoteconnection,theconnectionisestablishedviaDCN(Data
CommunicationNetwork)network.
Procedure
1 Start BTS Site Manager by clicking the icon on your desktop.

TheTaskSelectionviewopens.
Figure 3 TaskSelectionview
2 If you want to establish a local connection, select the Local option from the IP
Address list.
connector.
3 If you want to establish a local connection, select the Local option from the IP
Address list.
connector.

Manager
4 If you want to establish a remote connection, enter the FTM IP address.

UsetheM-planeaddress.
5 Enter the User name and Password.

ThedefaultusernameisNemuadminandthedefaultpasswordnemuuser.
Usingwebinterfaceathttps://192.168.255.129,localuseraccountinformationcan
beresettofactorydefaults(Nemuadmin/nemuuser)vialocalconnection.TheFTM
transportmoduleprovidesaservicetorecoverthetransportmodule.Recoverywill
deletetheconfigurationexcept:
Superuseraccountcredentials
NEaccountcredentials(ifexisting)
BTSkeypair(BTScertificateandBTSprivatekey,ifexisting)
CAcertificate(ifexisting)
Recoverywillresetthetransportmodule.
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.
4.1.3 Updating BTS site software

Purpose
Notethatthesystemreleaseupgradeshouldalwaysbedoneinatopdownapproach,
thatis:
1. NetActupgrade
2. OMSupgrade
3. eNBupgrade.

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
1 Launch BTS Site Manager.
2 Choose the Software Update SW to BTS Site menu item.

TheUpdate SW to BTS Sitedialogboxopens.
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.

Manager
5 Click the Update button.

TheUpdatebuttonisenabledifavalidmasterfilehasbeenselected.
SWdownloadtakesabout20minutes.Theexacttimedependsonthenumberof
itemstobedownloadedandthebandwidthoftheDCNconnection,forexample.The
UpdateProgressstepsshowthetransferstatus.WaitfortheSWupdatetobe
completed.IftheActivate SW after updatecheckboxwasselected,theSWwillbe
activatedandthesitewillbereset.
IfyouwanttostoptheSWupdate,clicktheStopbutton.
IftheSWdownloadfails,updatethesoftwareagain.NotethatiftheSWdownload
fails,theexistingSWversionisstillinuse.
6 If you want to view information on the SW download, click the View Report
button.
TheSoftware Update Reportdialogboxopens.
7 Click Close to close the Update SW to BTS Site dialog box.
4.1.4 Monitoring autoconnection in BTS Site Manager

This section describes how to monitor the correct autoconnection of BTS instances
through BTS Site Manager.
Purpose
Theautoconnectionfeatureenablestheautomatedconnectionofanuncommissioned
BTStoaserverinthenetwork.TheBTScommissioningmaythenbeautomatically
performedviathisserver.
TheprocedureconsistsoftheautomaticestablishmentofIPconnectivitysothatIP-
basedregistrationmessagescanbesent.Usingthelocationinformationofthenewly
installedBTS,OMScancorrelatetheBTSwiththerequiredlogicalconfiguration.
Afterinstallation,theautomaticestablishmentofaconnectionallowsthecommissioning
proceduretobecompletedremotely,withouttheneedforacommissioningengineerto
visitthesite.Operatorsbenefitfromacheaperandquickernetworkrollout.

Manager
Figure 4 Autoconfigurationdialogbox
ThedialogshownaboveisdisplayedautomaticallywhentheuserestablishestheBTS
SiteManagersessionbeforethestartoftheautoconnectionprocess.Thewhole
autoconnectionprocessisdividedintoseveralphases,andtheirprogressisdisplayedin
theabovedialogbox.
Before you start

ABTSmustbeuncommissionedfortheautoconnectionandautoconfigurationtostart.
AnuncommissionedBTSdoesnothaveavalidcommissioningfile.
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

Manager
2 Observe the autoconnection phases.

ThesephasesconsistofIPconnectivityestablishment,DHCPserverconnection,
andconnectionstodedicatedandfinalO&Mmediators.
Ifautoconnectionfails,theAutoconnectionRegistrationdialogboxisopened.
Figure 6 AutoconnectionRegistrationdialogbox
Here,theAutoconnectionsiteIDneedstobeprovidedsothattheBTSisidentifiable
totheuppernetworkelementandtheautoconnectionprocesscancontinue.
3 Observe the autoconfiguration phases.

ThesephasesconsistofSWdownload,SWactivationandreset,configurationfile
download,configurationfileactivation,andresetphases.Allthephasesarefully
automatedandnomanualinterventionisrequired.
AutoconfigurationcanbedisabledbyclickingtheDisablebutton(forexample,ifa
siteneedstobecommissionedmanually).Ifautoconfigurationisnotusedatall,the
dialogboxcanbeclosedbyclickingtheClosebutton.ClickingtheEnablebutton
enablestheautoconfiguration.
4.2 Introduction to Zone BTS site commissioning

Generic commissioning tasks
Commissioninginvolvesasequenceoftasks,suchasvisualchecksandinspections,
parameterandSWconfigurations,testsandreporting,toensurethatthestand-alone
equipmentinquestionhasbeenproperlyinstalled,hasnofaultymodulesandisready
forintegration.
ThegenericcommissioningstepscanbeseeninCommissioningoverview.Thedetails
ofeachstepdependontheequipmentandversioninquestionandcanbefoundinthe
relevantdocumentation.

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?
Complete Template None
Sitereset Planned Template Manual

(if SWupdated)
Entersite-specific Enterall
Commissioningfile
parameters parameters
downloadfrom
NetAct
Sitereset
Sitereset Commissioning
tests(optional)
Autoconfiguration Commissioning
report report
Integrated
Completed
Performing commissioning

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).

Manager
Commissioning file download from NetAct

Thisstepisautomaticifautoconnectionandautoconfigurationfeaturesareenabled.
NetActdownloadstheconfigurationfiletotheBTSandactivatesit.Onactivation,the
siteisreset.
Integration (relevant only for LTE releases)
Withtheconfigurationendphase,theBTSstartsestablishingS1connectionwiththe
configuredMME.IfIPsecisactivated,thentheappropriateIPSecTunnel(ortunnels)-
createdbeforetheSCTPassociations-areestablished.Incaseofcompletelypre-
configuredneighborsiteconfigurations,therelevantX2SCTPconnectionsaresetupas
well.
Parameter setup
Incaseautoconnectionandautoconfigurationarenotenabled,theparametershaveto
beenteredlocallyorremotelyafterenteringbasicparametersforO&Mconnection.This
canbedoneinthreeways(SWupdatemaybenecessarybeforetheparametersetup):
Usingaplannedcommissioningfilewhereallparametersarepredefined.
Usingatemplatecommissioningfilewherethesite-specificparametersneedtobe
enteredmanually.
Byenteringalltheparametersmanually.
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

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.
4.2.1 Starting manual commissioning

Purpose
Ifnocommissioningfileisavailable,theBTShastobecommissionedmanually.The
BTSiscommissionedwiththeCommissioningWizardintheBTSSiteManager(see
CommissioningWizard).
AllparametersneededtoconfiguretheBTSaredefinedintheplanningphase.
g Note: TheWizardsupportsEnglishalphabetonly.Pleaserememberthiswhenentering
textinthefields.

Manager
Procedure
1 Choose the View Commissioning menu item or click the Commissioning

button on the View Bar.
TheCommissioning-Introductionpageopens.
2 Select the commissioning target by clicking the appropriate option: BTS and
TRS.
3 Select the Manual option.
4 Click the Next button.

SeeCommissioning - BTS Settingsashowtocontinue.
4.2.2 Creating commissioning file

Purpose
Youcancreateormodifyacommissioningfileincreatecommissioningfilemodeusing
BTSSiteManager.ThecreatedfilecanbeusedintheTemplateorPlanned
commissioning.
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.
2 Select the Create File task.
3 Select the BTS Site Manager version you want to use.
4 Click the Create button.

TheBTSSiteManagerislaunchedinfilemodeandtheCreateCommissioningFile-
IntroductionWizardpageopens.

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.

TheCreateCommissioningFile-HWSelectionpageopens.
7 Define the modules in the HW configuration.

SelectthemodulesfromtheAdd <module>lists.
ThePropertiesviewinHWselectionshowstheunitcapabilities.SWsupportmay
becomeavailableinlaterreleases,however.

Continuethefilecreationbyenteringtherequiredparametersmanuallytaskbytask
guidedbyBTSSiteManager.SeetheCommissioningandCreate Commissioning
Filewizarddescriptions.

AfteralltherequiredWizardpageshavebeengonethroughclickingNext opensthe
Create Commissioning File - Summarypage.
10 Click the button to save the commissioning file.
11 Click the Finish button.

Amessageboxopensaskingyouifyouwanttocreateanothercommissioningfileor
exitthewizard.
Tocreateanotherfile,selecttheappropriateoption:Use current configurationor
Define new configuration,andclicktheCreatebutton.
Toexitthewizard,clicktheClosebutton.BTSSiteManagerclosesandtheTask
Selection viewopens.
4.2.3 Performing template commissioning

Purpose
Templatecommissioningprovidesanoptiontocommissionnetworkelementsusinga
predefinedtemplatefile.Sincethesameconfigurationsarecommonlyusedinseveral
networkelements,youcanstoreacommissioningfileanduseitasatemplatefilewhen
commissioningelementswithasimilarhardwareconfiguration,forexample.Thiswill

Manager
reducesignificantlythenumberofparametersthatneedtobeconfiguredsothat
basicallyonlysite-specificparameters,suchasBTSname,idandIPaddress,needto
bechanged.
Site-specificparametersareconfiguredontheBTSSettingsandRadioNetwork
Configurationcommissioningpages.
textinthefields.
Procedure

2 Select the commissioning target by clicking the appropriate option: BTS.
3 Select the Template option.
4 Select the commissioning file.

YoucanselectthefilefromtheSelectlistthatdisplaysBTScommissioningfilesfrom
thedefaultfolder.Youcanalsoenterthepathandfilenameinthefieldorbrowsefor
thecommissioningfilebyselectingtheBrowseoption.
Whentheselectedfileisopened,thefieldsintheWizardpageswillbefilled
automaticallyaccordingtotheparametersinthefile.

4.2.4 Performing planned commissioning

Purpose
Plannedcommissioningprovidesanoptiontocommissionnetworkelementsbyloading
acommissioningfiletotheBTS.Thecommissioningfileismadespecificallyforthesite
withtheNetActPlannerandNetActRadioAccessConfiguration-PlanEditortools.The
fileisdownloadedtothePCbymeansoftheNetActRadioAccessConfigurator-Site
ConfigurationTool.YoucanalsocreatethecommissioningfilewiththeBTSSite
Managerincreatecommissioningfilemode.
Thecommissioningfilecontainsalltheneededparametersandafterselectingthefile
theCommissioningWizardproceedsdirectlytotheCommissioning - Send Parameters
page.

Manager
textinthefields.
Procedure

3 Select the Planned option.
4 Select the commissioning file.

YoucanselectthefilefromtheSelectlistthatdisplaysBTScommissioningfilesfrom
thedefaultfolder.Youcanalsoenterthepathandfilenameinthefieldorbrowsefor
thecommissioningfilebyselectingtheBrowseoption.

TheCommissioning-SendParameterspageopens.
g Note: IftheselectedfilehasXMLvalidationerrorsorthecommissioningfileversion
differsfromtheversionthatBTSSiteManagerusesorcommissioningfilecontains
othererrors,youneedtogothroughalltheWizardpages.Inthatcasesee
Commissioning - BTS Settingsashowtocontinue.
4.2.5 Performing reconfiguration commissioning

Purpose
Reconfigurationcommissioningprovidesanoptiontocommissionalreadycommissioned
networkelements.Thereconfigurationcanbeusedwhenanewconfigurationcansolve
problemsorwhenanewconfigurationcanreleaseHWresourcesforanothersiteand/or
makeanelementtofunctionmoreefficiently.
Duringthereconfiguration,thesiteremainsoperationalupuntilapossiblesiteresetat
theendofthecommissioning.Whetheraresetisrequiredornotdependsonthe
changesdoneduringreconfiguration,thatisifparameterchangesaresuchthatrequire
areset.
textinthefields.

Manager
Procedure

3 Select the Reconfiguration option.

SelectingthisoptionenablestheBackup Commissioning Filesbutton.Clickingthe
buttonopenstheBackup Commissioning Filesdialogbox,whereyoucansavethe
commissioningfileforbackupbeforechangingtheconfiguration.Thedefaultfile
nameisBackupCommissioning_<Sitename>_<element>_<yyyymmdd>.xml.The
defaultlocationisthefolderwhereyouhavesavedbackupfilespreviouslyoryour
defaultworkingfolder(MyDocuments,forexample).
ClickGo to Radio Network Configuration pagetoproceeddirectlytoRadioNetwork
Configurationpage.ThislinkisenablediftheBTSiscommissionedandconnected.
Linkisalsoenablediftherearenoerrorsorwarningsinthesiteconfigurationfile.

4.2.6 BTS Site Manager Commissioning Wizard

This section describes the functionality of the BTS Site Manager Commissioning Wizard.
4.2.6.1 Commissioning - Introduction
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

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.
4.2.6.2 Create Commissioning File - Introduction
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

Manager
SelectCreate file from existing commissioning fileifyouwanttouseanexistingfileasa

templateforanewfile.IfyouselectedtheCreate file from existing commissioning file
checkbox,selectthetemplatefiletobeusedfromthedrop-downlistthatdisplaysall
BTSsitecommissioningfilesfromthedefaultfolder,orbrowseforthecommissioning
file.ThecommissioningfileformatisanXMLfile.Ifthecheckboxisnotselected,the
commissioningfilewillbecreatedfromscratch.
Next
ClickNexttocontinuetotheCreateCommissioningFile-HWConfigurationpage.
4.2.6.3 Create Commissioning File - HW Selection
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.

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.
4.2.6.4 Commissioning - HW Selection

IntheCommissioning-HWSelectionpageyoucandefineHWconfigurationfortheFZC
site.IfyouselectedtouseanexistingcommissioningfileasatemplateintheCreate
CommissioningFile-Introductionpage,theEquipment view displaystheHW
configurationfromthecommissioningfile.Otherwise,anemptycabinetisshown.The
PropertiesviewinHWselectionshowstheunitcapabilities.

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.

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.
4.2.6.5 Commissioning - BTS Settings
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
LED in use SelecttheLED in usecheckboxtoenableLEDvisibility

control.
Timer EnterthetimervalueinminutesintheTimerfield.Value0
meansthatLEDisalwayson.
Module location
EnterthelocationfortheFZCmoduleinthefield(maximumof50characters).Entering
thisinformationisoptional.
Passive units
ClickPassive Units toopenthePassiveUnitsdialogbox,whereyoucandefine
informationonpassiveunits.

Manager
Toggling faults
ClickBlock Toggling FaultstoopentheBlock Toggling Faultdialogbox,whereyoucan
definethetogglingfaultblockingrules.TheBlockTogglingFaultdialogboxcanbeused
toreducetheamountoffaultsintheBTStothereallyimportantonesandtopreventthe
systemfromgettingloadedwithfaultswhicharefillingthefaultviewbutdonotprovide
furtherimportantinformation,faultswhichareraisedandclearedinashortperiodoftime
andwhichdonotgivefurtherinformationforfaultanalysisandfaultlocalization.
Equipment view
TheEquipmentviewdisplaystheHWconfigurationgraphically.
Next
ClickNexttocontinue.
4.2.6.6 Commissioning - Passive Units
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
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.

Manager
4.2.6.7 Commissioning - BTS Synchronization Settings
In the Commissioning - BTS Settings and Create Commissioning File - BTS Settings
pages you can define synchronization settings for the BTS under commissioning.
Related topics
Network synchronization mode
Selectthenetworksynchronizationmodefromthedrop-downlist:Frequency
synchronizationorPhase synchronization.
Holdover mode in SelecttheHoldover mode in temperature controlcheck

temperature control boxifyouwishtoenablethisfunction.Thissettingcanbe
enabledifphasesynchronizationisselectedasnetwork
synchronizationmode.
Additional GNSS receiver settings
Activate GLONASS SelectActivate GLONASS synchronizationcheckboxto

synchronization takeGLONASSinuse.Thecheckboxisenabledandnot
checkedbydefault.
Equipment view TheEquipmentviewdisplaystheHWconfiguration

graphically.
Next ClickNexttocontinue.
4.2.6.8 Commissioning - Cell Resources
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
New Cells... ClickNew Cells...tocreatenewlocalcellsintheNew

Cellsdialogbox.Thebuttonisenabledifthemaximum
allowednumberoflocalcellsarenotyetcreated.
Cell ID [0...255] TheCellID[0...255]columnliststhecellsbycellid.
Flexi Zone AP TheFlexi Zone APcolumnshowstheAPtypeandAPID.
ColumnissortedbyAPID.
FRx TheFRxcolumnandtheANTxdrop-downlistsshowthe
antennaTX/RXusageinasortabledrop-downlist.
MIMO mode TheMIMO modecolumnshowstheantennasusingMIMO
inasortabledrop-downlist.

Manager
Carrier power TheCarrier power columnshowstheantennas'power

valuesinwatts,dBmandmilliwattsasapplicablein
sortabledrop-downlists.
Delete UsetheXcolumntodeleteacell.
Equipment view TheEquipmentviewdisplaystheselectedlocalcelland
antennasassignedtoithighlighted.
Next ClickNexttocontinue.Thisbuttonisenabledwhenall
localcellIDsareentered.
4.2.6.9 Commissioning - LTE Carriers
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
Downlink (TX) carriers Flexi Zone AP TheFlexi Zone APcolumnshowsthe

APtypeandIDinasortabledrop-
downlist.
Local cell TheLocal cellcolumnshowsthelocal
celliddefinedintheCommissioning -
Cell Resourcespageinasortable
drop-downlist.
Frequency TheFrequency bandcolumnshows
band thefrequencybandinwhichthelocal
celloperatesinasortabledrop-down
list.
Bandwidth TheBandwidthcolumnshowsthe
bandwidthforthelocalcellina
sortabledrop-downlist.Selectthe
appropriateoptionfromthedrop-
downlist.Thebandwidthisassigned
thenautomaticallytoglobalcell
(LNCEL)andshownasreadonly
informationoncommissioningRadio
NetworkConfigurationpage.The
allowedbandwidthvaluesareshown
accordingtotheautodetectedradio
modules.SameTXandRX
bandwidthvaluemustbeusedforall
cellsinBTS.
EARFCN TheEARFCNcolumnshowsthe
definedEUTRAAbsoluteRadio
FrequencyChannelNumber
(EARFCN)values.Enteratleastone

Manager
EARFCNforafrequencyband;upto
fourdifferentvaluescanbedefined
foreachfrequencyband.Thenumber
ofdifferentEARFCNvaluesdepends
onthecommissionedconfiguration.
3GPPstandardspecifiesthe
supportedEARFCNvaluesforeach
E-UTRAfrequencyband.The
supportedMHzfrequencybandand
E-UTRAfrequencybandareshown
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.
Frequency TheFrequency (MHz)columnshows

(MHz) thefrequenciescalculatedaccording
totheenteredEARFCNvalues.
Configure in ClickConfigure in Batch...buttonto
Batch... opentheConfigure LTE Carriers in
Batchdialogbox,whereyoucan
performbatchoperationsonthe
carriers.

Manager
Uplink (RX) carriers Uplinkcarriersareshownandcalculatedbasedonthe

downlinkcarriersentered.
Flexi Zone AP TheFlexi Zone APcolumnshowsthe
APtypeandIDinasortabledrop-
downlist.
Local cell TheLocal cellcolumnshowsthelocal
celliddefinedintheCommissioning -
Cell Resourcespageinasortable
drop-downlist.
Frequency TheFrequency bandcolumnshows
band thefrequencybandinwhichthelocal
celloperatesinasortabledrop-down
list.
Bandwidth TheBandwidthcolumnshowsthe
bandwidthforthelocalcellina
sortabledrop-downlist.
EARFCN TheEARFCNcolumnshowsthe
definedEUTRAAbsoluteRadio
FrequencyChannelNumber
(EARFCN)valuesinasortabledrop-
downlist.EnteratleastoneEARFCN
forafrequencyband;uptofour
differentvaluescanbedefinedfor
eachfrequencyband.Thenumberof
differentEARFCNvaluesdependson
thecommissionedconfiguration.
3GPPstandardspecifiesthe
supportedEARFCNvaluesforeach
E-UTRAfrequencyband.The
supportedMHzfrequencybandand
E-UTRAfrequencybandareshown
modules.Spacingbetweenthecell's
TXcenterfrequencyandcell'sRX
centerfrequencymustbeinthe
distancewhatcanbecalculated
takingintoaccountlowerfrequency
limitsofTXandRXEARFCNlimits.
Example:2100MHz(E-UTRA1).
AllowedTXEARFCNvalues0-599
andallowedRXEARFCNvalues
18000-18599.Spacingvalueisgetby
18000-0=18000.WhenenteringTX
centerfrequency100thenRXcenter
frequencymustbe18100.
EARFCN range ShowstheallowedEARFCNvalues
forthefrequencybandinasortable
drop-downlist.
Frequency TheFrequency (MHz)columnshows
(MHz) thefrequenciescalculatedaccording
totheenteredEARFCNvaluesina
sortabledrop-downlist.
Equipment view TheEquipmentviewshowstheselectedlocalcell

highlighted.

Manager
4.2.6.10 Commissioning - Antenna Line Settings
In the Commissioning - Antenna Line Settings and Create Commissioning File - Antenna
Line Settings pages you can define antenna settings.
Related topics
Flexi Zone AP TheFlexi Zone APcolumnshowstheAPsinasortable

drop-downlist.
Antennas TheAntennascolumnliststheantennasofradiomodules
assignedtothelocalcellsintheCommissioning-Cell
Resourcespage.
RTT delay EntertheRTTdelayvaluesinthissortabledrop-downlist.
Configure in Batch... ClickConfigure in Batch...buttonopenstheConfigure
Antenna Line Settings in Batchdialogboxwhereyoucan
performbatchoperationonantennalines.
Equipment view TheEquipmentviewdisplaystheantennaconnectorsas
highlighted.

Manager
4.2.6.11 Commissioning - Radio Network Configuration
In the Commissioning - Radio Network Configuration and Create Commissioning File -

Radio Network Configuration pages you can define radio network configuration for the
site.
Related topics
Parameter area Intheparametertreeviewontheleftyoucanselecta

managedobject(MO)andviewandmodifyitssettingsin
theparameterarea.Youcanalsosearchparametersinthe
Searchbarabovethetreeview.TheSearchbarincludesa
comboboxwiththefollowinglistofstaticselections:Show
only existing,Show all,orRelated features.WhenShow
only existingisselected,onlytheexistingconfigurationis
visibleandonlyvisiblepartmatchesareincludedinfound
matchingitemsfield.WhenShow allisselected,the
existingconfigurationisvisibletogetherwithmatching
searchresultsfromnotconfiguredMO,listsandparameter
includingparentMOandlist.MOandlistlevelsiblingitems
thatdonotmatcharenotshown.Hiddenparametersare
notshownandarenotincludedinsearchresults.These
non-configureditemslabelsappearaseditable,but
modificationisnotpossibleasthisisdisabled.Allsearch
matchesareincludedinfoundmatchingitemsfield.Show
moredetailsdialogboxwillbeshownfornon-configured
items.WhenRelated featuresisselected,feature
informationisusedinsearchresults.Onlyconfigured
parametersareincludedinthesearchsimilarlywithShow
only existingabove.
YoucanusetheNewandCopybuttonstoaddorcopy
managedobjectstothetree.Itisalsopossibletodelete
andcopyobjectsbymovingthemouseoveranobjectand
right-clickingonittoopenthemenuforcopy/deleteactions
orforcreatinganewMO.Itisalsopossibletocompare
twomanagedobjectsorlistitems.YoucanalsouseCopy
Data Fromdrop-downlisttocopydatafromthesource
LNCELtotargetLNCELincludingallchild-managed
objects(MOs).Drop-downlistisshownwhenLNCEL
managedobjectisselectedandthereareatleasttwo
LNCELMOs.
Copybuttonisnotavailablewhenfunctioncannotbe
performedontheselectedMO.
Intheparameterareaontherightyoucanmanagethe
parametersettings.Sortingdrop-downlistcanbeusedto
sorttheinformationintwoways:AlphabeticalorRelated
functions.
MRBTS/LNBTS Selectamanagedobject(MO)orlist
iteminthetreeviewtoviewits
parametersormanagetheselected
MO/listitem.Parametersare
displayednexttothetree.The
parameterareadisplaystheRNW
parametersoftheMRBTSmainlevel

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.
Next ClickNext tocontinue.Nextbuttonisenabledwhenall

mandatoryparameters/MO/listitemshavebeenfilledin
andalldataisvalidbasedonthePDDBmetadata.
Cancel ClickCancel tocanceltheoperation.

Manager
4.2.6.11.1 Setting Zone eNB APMOD Parameters with BTSSM
Purpose
TheparametertreeviewontheleftoftheBTSSiteManagerRadioConfigurationpage
allowsyoutoselectmanagedobjects(MO)SMOD-1/APMOD-N,inordertoviewand
modifygeneralsettingsoftheAPMOD.YoucandefineAPAutoConfiguration
parametersandothercommonAPMODconfigurationoptions.
Procedure
1 Verify the fixed Access point module identifier.

ThisisthesamethesameastheassociatedAPMODcreatedintheHWSelection
screen.
2 (Optional) Enter the 1 Pulse Per Second (PSS) source line delay.
ThisparameterspecifiesthelinedelayinthecableusedbetweentheGPSantenna
andtheAP.
3 (Optional) Enter the Air Frame timing as for 1 PPS reference .

Thisparameterdefinestheshiftforairframephasetowardsthe1PPSfortheAP.

Manager
4 Enter the APMOD Auto Connection parameters.

TheprocessinwhichtheFZCidentifiesanewlyconnectedFZAPandmapsittoone
oftheAccessPointModuleIdentifiers(APMODs)isreferredtoasAPDiscovery.
g Note: TherearethreetypesofAccessPoint(AP)identityrelatedparametersusedby
thesystemwheneveranAPisconnectedtotheFlexiZoneController(FZC)forthefirst
time.TheFZCrequiresat least onetypeofAPidentityparameterstobeprovisioned
bytheoperatorinordertouniquelymapanAPtooneoftheconfiguredAPMODs.This
inturnallowsthesystemtoassignthepropercellconfigurationtotheresourcesofthe
newlydiscoveredAP.ConfiguringtheFZCwithmorethanonetypeofAPidentity
parametersisalsosupported.
Sub-steps
a) Enter the Auto Connection Hardware ID parameter.

EachFZAPisassignedauniquehardwareidentifier(i.e.serialnumber)atthe
factory.Thehardwareidentifier(HwID)isprogrammedintotheAPsinternal,
protectedmemoryintheformofanelectronicidentification(EID)aswellas
labeledontheoutsideofeachunit.TheFZAPwillalwaysprovideitsHwIDtothe
FZCaspartoftheAPDiscoveryprocess.InorderforanAPtobeidentified
basedontheHwIDduringAPDiscovery,thisparametermustbeprovisioned
withtheexactHwIDstringassignedtotheAP.Validationruleswillpreventmore
thanoneAPMODtobeprovisionedwiththesameAutoConnectionHardwareID
value.
b) Enter the Auto Connection Site ID.

DuringtheAPinstallationprocess,theoperatorhastheoptionofassigningthe
APafreeformtextstringcalledSiteIDviatheBTSSiteManager(FZAP)orvia
WebUI.TheexactsametextstringenteredattheAPneedstobeprovisioned
hereaswell.IfprovisionedatboththeFZAPandFZC,SiteIDwillbeusedto
identifytheAPaspartoftheAPDiscoveryprocess.TheSiteIDforeachAP
connectedtothesameFZCmustbeunique.TheSiteIDacceptstextstringsof
upto4000charactersinlength.
Step example
SomevalidSiteIDtextstrings:FZC-4,APMOD-22,122CASSST,Floor5
East,Mainlibraryhall-MiskatonicUniversity.
5 Enter the Geo Coordinates of the APMOD.

APMODconfiguredlatitude,longitude,altitude
Geolocationtolerance
APsconfiguredtouseGPSasitstimingsourcecanautomaticallyobtaintheir
geographicallocationandwillreporttheirlatitude,longitudeandaltitudetotheFZC
duringAPDiscovery.ThecorrespondinggeographicallocationoftheAPneedstobe

Manager
provisionedattheFZCviatheAPMODconfiguredlatitude,longitudeandaltitude
parameters.TheGeolocationtoleranceparameterallowstheoperatortospecifythe
amountofdistance(inmeters)allowedbetweentheAPreportedlocationandthe
configuredAPlocation(attheFZClevel)toallowtheFZCtopositivelyidentifythe
APbasedonlocation.
TheuseofgeographicallocationtoidentifyanAPrequireseachAPtobeinstalled
withadedicatedGPSantennawithinanunobstructedviewofthesky.Aremotely
locatedGPSantennawillprovidethelocationofthephysicalantenna,notthe
physicalAP.APDiscoveryviageographicallocationisnotsupportedforindoor
FZAPsandconfigurationswhereAPssharethesameGPSantenna.
6 Enter the External GPS as reference source.

ThisparameterdefinesiftheAPhasGPSinuse.Thisparametermustbesetto
'true'whenanexternalGPSreceiverisconnectedtothe1pps/GPSsyncinput.
7 Enter the Location Mode.

Whenthisparameterisin"navigated"mode,FZAPlocationisdetermindedby
satellitetransmissions.
8 (Optional) Enter the Module Location.

ThisparameterdefinesanAPmodulelocationinfreetext.Amaximumof50
charactersisaccepted.
9 Enter the Transmission synchronization (TDM/SyncE/ToP) in use.

WhensettotrueuseofTDMsyncsourceisenabled.
4.2.6.11.2 Configuring FZAP Ethernet settings with BTSSM
Purpose
allowsyoutoselectmanagedobjects(MO)SMOD-1/APMOD-N/APELNK-Xtoviewand
modifyEthernetinterfacesettingsoftheAPMOD.YoucandefinetheAdministrativestate
oftheinterfaceandotherphysicalinterfacepropertiesforEthernetInterfaces.BTSSM
withautomaticallyincludethecorrectnumberofethernetinterfacesbaseduponthe
APMODtypebeingprovisioned.
100 2016Nokia DN09210645Issue:01C

Manager
Procedure
1 Select Speed and duplex configuration options for the Ethernet interfaces:
EIF1:
Autodetect
1000Mbit/sFullDuplex
EIF2:
Autodetect
100Mbit/sFullDuplex
1000Mbit/sFullDuplex
EIF3(PortC,applicabletosomeAPMODsonly):
Autodetect
4.2.6.11.3 Configuring Zone and AP Bluetooth Settings with BTSSM
Purpose
TherearetwoseparateBluetoothCommissioningscreenswheretheZoneeNBwide
andperAPMODBluetoothconnectivitysettingscanbeset.
DN09210645Issue:01C 2016Nokia 101

Manager
Procedure
1 Configure the Zone eNB bluetooth settings

TheparametertreeviewontheleftoftheBTSSiteManagerRadioConfiguration
pageallowsyoutoselectthemanagedobject(MO)LNBTS-X/FTM-1/BTOOTH-1to
viewandmodifytheBluetoothconnectivitysettingscommonacrossthewholeZone
eNB.
102 2016Nokia DN09210645Issue:01C

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.
2 Configure the APMOD bluetooth settings

TheparametertreeviewontheleftoftheBTSSiteManagerRadioConfiguration
pageallowsyoutoselecttheselectthemanagedobject(MO)SMOD-1/APMOD-
X/APB2TH-1toviewandmodifytheBluetoothconnectivitysettingsspecificforthat
APMOD.
DN09210645Issue:01C 2016Nokia 103

Manager
Sub-steps
a) Select Enabled in the Activate interface support for AP drop-down list to

enable Bluetooth interface support.
b) Select the Allow inquidy scan response check box to allow inquiry scan
response.
c) Enter Bluetooth name.
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.
4.2.6.11.4 Configuring Zone and AP QOS Settings with BTSSM
Purpose
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.
104 2016Nokia DN09210645Issue:01C

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
DN09210645Issue:01C 2016Nokia 105

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.
106 2016Nokia DN09210645Issue:01C

Manager
4.2.6.11.5 Configuring AP Timing Over Packet Settings with BTSSM
Purpose
allowsyoutoviewandmodifytheTimingoverPacketsettings.
Procedure
1 Select the relevant Managed Object to configure.

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.
DN09210645Issue:01C 2016Nokia 107

Manager
2 Enable or Disable Phase Synchronization mode by setting Feature Activation

Flag Top with phase synchronization to enabled or disabled.
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.
4 Enter the phase error compensation value in ns in the Phase Error

Compensation field.
5 Enter the PTP domain number value in the PTP domain number field.
Therangeis0...255.ThedefaultvalueisasfollowsdependingontheTimingover
PacketCommunicationsMode:
108 2016Nokia DN09210645Issue:01C

Manager
IEEE-1588-2008:0
ITU-TG.8265OptI/II:4
ForIPunicastcommunicationmodeitisIEEE1588partialonpathsupportandfor
EthernetmulticastcommunicationmodeitisITU-TG.8275.1fullonpathsupport.
6 Select Timing over Packet Communication Mode.

TheavailableoptionsundertheTiming over Packet Communication Modedrop-
downlistare:
IPunicast
Ethernetmulticast
7 Set Top over Ethernet Multicast Address

ThisparameterconfigureswhethertheTimingoverPacketoverEthernetframesare
sentusingEthernetmulticastMACaddress01-80-C2-00-00-0Eor01-1B-19-
00-00-00.
g Note: ThisvalueisonlyusedwhentheTimingoverPacketCommunicationsMode
settingofEthernetMulticastisselected.
4.2.6.12 Commissioning - Send Parameters
In the Commissioning - Send Parameters page you can send the parameters entered
during the commissioning procedure to the BTS site.
Related topics
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
DN09210645Issue:01C 2016Nokia 109

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.
4.2.6.13 Commissioning - Additional Site Settings
In the Commissioning - Additional Site Settings page you can manage the local user
account.
Related topics
Change Local Account ClickChange Local AccounttoopentheChange Local

Accountdialogbox,whereyoucanchangetheusername
andpasswordofthelocalaccount.
Certificate Management ClickCertificate ManagementtoopentheCertificate
Managementdialogbox,whereyoucandownload
110 2016Nokia DN09210645Issue:01C

Manager
certificatefiles,checkcertificatestatusanddelete
certificatefiles.
4.2.6.14 Commissioning - View Parameters
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
Close ClickClosetoreturnintheCommissioning - Send

Parameterspage.
4.2.6.15 Commissioning - View File Changes
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
Close ClickClosetoreturnintheCommissioning - Send

Parameterspage.
4.2.6.16 Commissioning - Commissioning Report
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
DN09210645Issue:01C 2016Nokia 111

Manager
<element> Commissioning parameters:theparametersenteredinthe

Commissioningpagesforthecommissionedelements
Clickthe buttontoopentheSave Commissioning Reportdialogbox,whereyoucan

definethefilenameandthelocationfortheCommissioningReport.Thedefaultfile
nameisCommissioningReport_<Sitename>_<yyyymmdd>.txt.Thedefaultlocationis
thefolderwhereyouhavesavedthepreviouscommissioningreportsoryourdefault
workingfolder(MyDocuments,forexample).
Related topics

Finish ClickFinishtofinishthecommissioning.Ifyoudonotsave
theCommissioningReportbeforeclickingtheFinish
button,amessageboxopensaskingyoutoconfirmifyou
wanttofinishthecommissioningwithoutsavingthe
CommissioningReport.Youcansavethereportbyclicking
Save As,orfinishthecommissioningwithoutsavingthe
reportbyclickingDon't Save.Youcancheckthestatus
fromtheStatusbaroftheBTSSiteManagermainwindow.
Ifthecommissioningwassuccessful,thestatusbarshould
displayCommissionedor"Integrated"or"Testdedicated"
or"Onair"whenexitingthewizard.Afterthesuccessful
commissioning,thereshouldbenoCommissioning
parametermismatchfaultsshownintheFault view.
Typicallythenetworkconfigurationisstoredonindividual
moduleserialnumberleveltoenablefastandefficient
searchinthenetwork,incasesuchinformationisneeded.
Oneoftheentrypointsforthisdataisaftercommissioning.
DependingontherequirementsoftheIMsystemwhere
thisinformationisstored,theremightbeseveraloptionsto
collectthedata.Themosttypicalistoscanthemodules
withabarcodereader.NokiaSolutionsandNetworks
recommendsacertainbarcodereaderHWandSWto
enablemoreautomatedtransferofdatatoNetAct.More
informationisavailableintheNetActdocumentationUsing
Bar Code ScannerandUsing Asset Managerdocuments.
4.2.6.17 Create Commissioning File - Summary
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
112 2016Nokia DN09210645Issue:01C

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.
DN09210645Issue:01C 2016Nokia 113

IntegratingFlexiZoneControllertoNetActthroughthe CommissioningFlexiZoneController
NWI3link
5 Integrating Flexi Zone Controller to NetAct

through the NWI3 link
This section describes how to integrate the Zone eNB to NetAct through the NWI3
interface.
TheintegrationsolutionoftheFlexiZoneControllerthroughtheNWI3interfaceisthe
sameasthatofFlexiMultiradioBTSLTE.TointegrateFlexiZoneControllerApplication
toNetAct,refertotheIntegrating Flexi Multiradio BTS LTE to NetActdocument
(DN09118114).
114 2016Nokia DN09210645Issue:01C

CommissioningFlexiZoneController IntegratingFlexiZoneAccessPointstotheFlexiZone
Controller
6 Integrating Flexi Zone Access Points to the

Integrating a Flexi Zone Access Point (FZAP) into a Zone eNB involves the discovery of
Flexi Zone Micro BTS modules by the Flexi Zone 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.
DN09210645Issue:01C 2016Nokia 115

IntegratingFlexiZoneAccessPointstotheFlexiZone CommissioningFlexiZoneController
Controller
Figure 8 IntegratingFZAPstoaZoneeNB
FZC
Zone
Integration
BTSSM-or- FZM FZAP FZAP FZAP

WEBUI
FlexiZone AccessPointCluster
FZAP integration and Z1 IPSec protection

ThefollowinginstallationproceduresarevalidforscenarioswheretheZ1interface
betweenFZCandFZAPsisprotectedviaIPSec,andinthosescenarioswherethis
protectionisnotenabled.SeesectionManagingIPSecpoliciesintheFlexiZone
ControllerforinstructionsonhowtoactivateIPSecprotection.
g Note: ItisrecommendedtoactivateZ1IPSecprotectionbeforeinitiatingFZAP
integration.
OncetheFZAPintegrationhasbeencompleted,theAPoperationalstateshouldbe
verifiedviaNetActortheFZCBTSSMinterface.
IncasetheFZAPfunctionalstateappearsasUnknown,theAPhasnotbeen
successfullydiscoveredbytheFZC:
1. VerifytheconfigurationofthecorrespondingFZAPAPMOD.
2. IfIPSecprotectionhasbeenactivatedontheZ1interface,followtheprocedure
describedinVerifyingIPSectunnelinginFlexiZoneController.
3. Iftheissuespersist,contactNokiasupport.
6.1 Integrating a Flexi Zone Micro to the FlexiZone

Controller using BTSSM
This section describes how a FEWS hosting the BTS Site Manager application enables
the integration of a Flexi Zone Micro BTS under a Zone eNB.
116 2016Nokia DN09210645Issue:01C

Controller
6.1.1 Introducing the Flexi Zone Micro Autoconnection Site ID in

BTSSM
FZM BTS can be easily discovered by the FZC within a Zone eNB by providing the FZC
with an Autoconnection Site ID via BTSSM.
Purpose
ThisprocedureisnecessaryonlyiftheAutoconnectionSiteIDisbeingusedasthe
identityparameterfortheFZM/FZAPintheFZC.
Before you start
AconnectionbetweenBTSSMandtheFlexiZoneMicroisestablished.
Procedure
1 Navigate to the Autoconnection Registration Dialog.
2 Enter the Autoconnection Site Id. See figure for the Autoconnection
Registration dialog screen.
Figure 9 BTSSMAutoconnectionRegistrationdialogscreen
6.1.2 Checking the Flexi Zone Micro Autoconfiguration progress

in BTSSM
This procedure verifies the FZM BTS Autoconfiguration as a FZAP in BTSSM.
Before you start

DN09210645Issue:01C 2016Nokia 117

Controller
Procedure
1 Navigate to the Autoconfiguration progress dialog to check the progress of

various steps associated with integrating into the Flexi Zone Controller.
2 Verify that Autoconfiguration is enabled.
3 Verify that Autoconfiguration has been completed.
Result
OnceAutoconfigurationiscompletetheFZCwillhaveoptionallydownloadednewSWto
thedevice,sentandactivatedtheconfigurationfileandtheFZMisnowconsidered
integratedtotheFZCasaFZAP,readytoprovideservicewithintheZoneeNB.
Example
Figure 10 BTSSMAutoconfigurationdialog
6.1.2.1 Uncommissioning a Flexi Zone Micro to allow FZAP

Autoconfiguration in BTSSM
Previously commissioned FZM BTS need to be uncommissioned prior to their Zone eNB
integration.
Purpose
IftheAutoconnectionRegistrationDialogisgreyedoutwhenaccessingthe
Autoconfigurationdialog,itcouldbethattheFlexiZoneMicrohasbeenpreviously
configuredandcommissionedforoperationatadifferentsite.
118 2016Nokia DN09210645Issue:01C

Controller
Before you start

Perform a configuration reset when the Flexi Zone Micro is running release
15A or later SW.
Sub-steps
1 Access the configuration reset dialog within the configuration menu.
Figure 11 BTSSMConfigurationresetdialog
DN09210645Issue:01C 2016Nokia 119

Controller
2 click the Reset button.
Perform a configuration reset when the Flexi Zone Micro is running a software
version previous to release 15A.
Sub-steps
1 Connect to the FZM LMP via address 192.166.255.129
2 Access the Tools > Recover TRS menu
3 Clear transport software (TRS) persistent data by clicking Delete

configuration and REBOOT
Figure 12 FlexiTransportModuleRecover TRSmenu
4 Press and hold the reset button on the Flexi Zone Micro BTS for more than
5 seconds.
120 2016Nokia DN09210645Issue:01C

Controller
6.2 Integrating a Flexi Zone Micro to the FlexiZone

Controller using WebUI
This section describes how to integrate a Flexi Zone Micro BTS under a Zone eNB via
the WebUI interface.
6.2.1 Introducing the Flexi Zone Micro Autoconnection Site ID in

WebUI
RL15A FZM BTS can be easily discovered by the FZC within a Zone eNB by providing
the FZC with an Autoconnection Site ID via WebUI.
Before you start

TheFlexiZoneMicroneedstobeusingFL15A/TL15ASWorlater.Theprocedure
assumesthataWebUIinterfacetotheFlexizoneMicroisestablished.
Procedure
1 Navigate to the Auto-Connection > Configure Site ID dialog
2 Enter the Autoconnection Site ID.
Figure 13 WebUIConfigureSiteIDdialog
3 Press the configure button.
6.2.2 Checking the Flexi Zone Micro Auto Connection &

Configuration progress in WebUI
This procedure verifies the FZM BTS configuration as a FZAP via the integrated WebUI.
Before you start
DN09210645Issue:01C 2016Nokia 121

Controller
TheFlexiZoneMicroneedstobeusingFL15A/TL15ASWorlater.Theprocedure
assumesthataWebUIinterfacetotheFlexizoneMicroisestablished.
Procedure
1 Navigate to the Auto Connection & Configuration progress dialog.
Figure 14 AutoConnection&Configurationprogressdialog
2 Verify that all steps are completed.
Result
OnceAutoConnection&ConfigurationiscompletetheFZCwillhaveoptionally
downloadednewSWtothedevice,sentandactivatedtheconfigurationfileandtheFZM
isnowconsideredintegratedtotheFZCasaFZAP,readytoprovideservicewithinthe
ZoneeNB.
6.2.2.1 Uncommissioning a Flexi Zone Micro to allow FZAP Auto

Connection & Configuration in WebUI
Previously commissioned FZM BTS need to be uncommissioned prior to their Zone eNB
integration.
Purpose
IftheFlexiZoneMicroisinthecommissionedstatewithaconfigurationforapriorsite
andnotconnectingtotheFlexiZoneControlleritmaybenecessarytoissuea
configurationreset.
Before you start
TheFlexiZoneMicroneedstoberunningrelease15ASWorlater.AWebUIinterfaceto
theFlexiZoneMicroisestablished.
122 2016Nokia DN09210645Issue:01C

Controller
Procedure
1 Perform a configuration reset when the Flexi Zone Micro is running release
15A or later SW.
Sub-steps
a) Access the configuration reset dialog within the configuration menu.
Figure 15 WebUIConfigurationresetdialog
b) click the Confirm button.
6.3 Verifying IPSec tunneling in Flexi Zone Controller

The correct setup of IPSec tunneling in the Z1 interface can be verified through SCLI
commands.
Before you start

TheseproceduresassumesthattheoperatorhasaccessedtheFlexiZoneController
fsclishbash.
DN09210645Issue:01C 2016Nokia 123

Controller
Procedure
1 Trigger the negotiation by pinging a target FZAP.

ping SOURCE_ADDRESS -i DESTINATION ADDRESS
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.
124 2016Nokia DN09210645Issue:01C

CommissioningFlexiZoneController AdditionalproceduresforFZCcommissioning
7 Additional procedures for FZC

commissioning
7.1 System restoration in FZC

7.1.1 Introduction to restoring the system
Systemrestorationisaprocedurethatdecreasesthecontrolleroutagetimecausedby
bothharddisccrash.Duringthisprocedurethesystemisre-commissionedusinga
backupISOasthebasebuild.
User responsibilities
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.
7.1.2 Preparing backup ISO
DN09210645Issue:01C 2016Nokia 125

AdditionalproceduresforFZCcommissioning CommissioningFlexiZoneController
7.1.2.1 Overview of backup and restore
Makingregularbackupcopiesoftheexecutablesoftwareandconfigurationdatausedby
itensuresthatyoucanrestorethesoftwaretoaprevioussoftwarelevelwhichfunctions
normally,forexampleinthecaseofaharddiskcrashoraconfigurationerror.
7.1.2.2 Making an active software backup

Purpose
Thischapterprovidesinstructionsonhowtomakeanactivesoftwarebackupfor
restoringthenetworkelementfunctionalityincaseofsoftwareorhardwarecorruption.
g Note: Youarerecommendedtoperformbackupoperationaftereveryconfiguration
changein,forexample,RNWconfigurationorLDAPconfiguration.Beforeyoudoso,
makesurethatthenetworkelementrunssmoothlywiththechangedconfiguration.
Before you start

Ensurethat:
thenetworkelementisupandrunningasnormal.
thebackupisnotperformedduringlargefiletransferstothenetworkelement.
thebackupisnotperformedduringpeakhoursbecauseitcauseshighCPU
utilization.
anyotheroperationswhichcancausehighCPUloadarenotperformedinparallel.
Procedure
1 Check the state of the FSClusterStateServer recovery unit.

TofindouttheFCPUnode,inwhichtheactiveinstanceoftheFSClusterStateServer
recoveryunitislocated,executethefollowingcommand:
show has state managed-object /FCPU*/FSClusterStateServer
Expected outcome
Thefollowingoutcomeisdisplayed:
OBJECT ADMINISTRATIVE OPERATIONAL USAGE ROLE PROCEDURAL DYNAMIC
/FCPU-0/FSClusterStateServer UNLOCKED ENABLED ACTIVE ACTIVE - -

/FCPU-1/FSClusterStateServer UNLOCKED ENABLED ACTIVE HOTSTANDBY - -
Therolefielddisplayswhethertherecoveryunitisinactiveorstandbymode.Ifthe
FSClusterStateServerrecoveryunitisnotactiveonthecurrentnode(showninthe
promptoftheSCLIsession),transfertheSCLIsessiontotheotherCFPUnodeby
executingthefollowingcommandshell scli peer.
2 Check and make sure the state of the database recovery group (QNDBRNW) is
UNLOCKED
a) Checkthestateofthedatabaserecoverygroupusingthefollowingcommand:
126 2016Nokia DN09210645Issue:01C

show has state managed-object <mo-name>

where,<mo-name>isthenameofthemanagedobject,whichisQNDBRNWin
thecontroller.
Example: Checking the state of the /QNDBRNW database recovery group
Tocheckthestateofthedatabaserecoverygroup,executethefollowing
command:
show has state managed-object /QNDBRNW
Expected outcome
Thefollowingoutputisdisplayed:
/QNDBRNW UNLOCKED ENABLED ACTIVE - - -

Theadministrativefielddisplayswhetherthedatabaserecoverygroupis
lockedorunlocked.
b) IftherecoverygroupQNDBRNWisLOCKED,unlockitusingthefollowing
command:
set has unlock managed-object /QNDBRNW
3 Check the available disk space
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.
4 Start the active software backup session.

Tomakeanactivebackup,executethefollowingcommand:
start backup active
5 Commit the backup session

Tocommitthebackupsession,enterthefollowingcommand:
commit backup
g Note: Ifyouwanttocancelthebackupsessioninitiatedbythestart backup

command,entertherollback backupcommandbeforethebackupsessionis
committed.
DN09210645Issue:01C 2016Nokia 127

Theresultingisoimageisstoredinthe"/mnt/backup/backup"directory.
Unexpected outcome
Whenbackupfails,thesystemraisesthealarm70064BACKUPERRORonthe
activeFCPUnode.
Youcanchecklogsrelatedtotheerrortogetmoreinformation.
7.1.2.3 Transferring the backup archive file to an external storage server
Summary
Usethescpcommandtotransferthebackupimagetotheexternalstorageserverand
verifytheintegrityofthefilewiththemd5checksum.
Purpose
Totransferthebackuparchivefilefromthelocalharddisktoanexternalstorageserver
asasafetyprecaution.Thisalsofreeslocalharddiskspaceandkeepsahistoryof
differentbackupversions.
Procedure
1 Check the state of the FSClusterStateServer recovery unit.

TofindouttheFCPUnode,inwhichtheactiveinstanceoftheFSClusterStateServer
recoveryunitislocated,executethefollowingcommand:
show has state managed-object /FCPU*/FSClusterStateServer
Expected outcome
Thefollowingoutcomeisdisplayed:
/FCPU-0/FSClusterStateServer UNLOCKED ENABLED ACTIVE ACTIVE - -

/FCPU-1/FSClusterStateServer UNLOCKED ENABLED ACTIVE HOSTSTANDBY - -
Therolefielddisplayswhethertherecoveryunitisinactiveorstandbymode.Ifthe
FSClusterStateServerrecoveryunitisnotactiveonthecurrentnode(showninthe
promptoftheSCLIsession),transfertheSCLIsessiontotheotherCFPUnodeby
executingthefollowingcommandshell scli peer.
2 Start a bash shell session.

shell bash full
128 2016Nokia DN09210645Issue:01C

3 Compute the md5 checksum of the backup image.

# md5sum FZC603_active_backup_20120607_1008.iso
>backup_20120607_1008.md5
Thiscomputesthechecksumofthebackupimageandwritesitintoaseparatefile
underthe/mnt/backup/backupfolder.
4 Transfer the backup image and the checksum file to the desired location.
# scp /mnt/backup/backup/<backup image> <username>@<external server
IP address>:<target location>
scp /mnt/backup/backup/<checksum file> <username>@<external server IP

address>:<target location>
Theparametersarelistedinthetablebelow:
Table 8 Parametersfortransferringthebackupimageandchecksumfiletothe
desiredlocation
Parameter Description
<backup image> <backup image>isthefullpathofthebackupfiletobe

restored.Bydefault,thebackupimagesarestoredinthe
/mnt/backupdirectory.
<username> <username>isaloginnamewhichhaswritepermission
toexternalstorageserver
<external server <external server IP address>isanIPaddress

IP address> forexternalstorageserverwherebackupimagewillbe
stored.
<target <target location>isthefullpathtoanexisting

location> directoryonanexternalstorageserverwherethebackup
imagewillbestored.
<checksum file> <checksum file>isthefullpathofthefilethat

containsresultofMD5sumofthebackupimage
performedbythemd5sumcommand.Thisisusedto
validatethebackupimage.
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
DN09210645Issue:01C 2016Nokia 129

5 Log into the external storage server.
6 Verify the checksum of the transferred image.

Usethemd5sumcommandtoverifythatnobiterrorshappenedwhenthefilewas
transferred.Anexampleofthecommandisasfollows:
# md5sum --check backup_20120607_1008.md5
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.
7 Exit the bash shell session.

Enterthecommand:
exit
7.1.3 Preparing backup SW delivery on the FEWS
7.1.3.1 Extracting the backup software .ISO image to a delivery folder

Purpose
ThischapterdescribeshowtoextractbackupSWbuildintodeliveryfoldertoobtain
softwareimagefileforrestoration.
Before you start
Backup.ISOislocatedontheFEWSin<target location>,for
example/tmp/myDelivery.
Procedure
1 Define <env_name> variable.

Definethevariablewiththefollowingcommand:
130 2016Nokia DN09210645Issue:01C

# env_name=<FZCxxx>
<FZCxxx>standsforclusterIDofthecontrollerunderrestoration.
Step example
#env_name=FZC646
2 Verify <env_name> value.

#echo $env_name
Step result
FZC646
3 Mount the .ISO delivery under /mnt/myPoint directory.

UsetheSS_FEWSsubsystemfromthesoftwaredelivery( .ISOimage)toensure
compatibilitythroughoutthecommissioningprocess.TheSS_FEWSsubsystem
containscommandlinetoolsforextractingandmountingthesoftwaredeliveryinthe
FEWS.
Createtemporarymountingpointwiththefollowingcommand:
# mkdir -p /mnt/myPoint
Mountthe.ISOdeliverywiththefollowingcommand:
# mount -o loop <target
location>/${env_name}_active_backup_<yyyymmdd_hhmm>.iso
/mnt/myPoint
Step example
# mount -o loop
tmp/myDelivery/${env_name}_active_backup_20150418_1030.iso
/mnt/myPoint
4 Check that builds does not overlap.

Backupbuildnamemighthasthesamenameasdownloadedbuildusedforclean
installation.ThelattermaybestillmountedonyourFEWSanditmustberemoved.
Gotothefollowingdirectoryusingthefollowingcommand:
Checkbuildavailabilitywiththefollowingcommand:
./fsetupcli --delivery --list
Incaseanybuildnameisonthelist,removeit.Runthefollowingcommand:
./fsetupcli --delivery --remove
Fromthegivenlist,selectbuildorbuildstoremove.
Step result
DN09210645Issue:01C 2016Nokia 131

Whenallremainingbuildsareremovedcorrectly,runningfsetupcliispossibleno
more.
5 Patch (extract) the .ISO delivery using the fsetupcli script.

# /mnt/myPoint/MISC/SS_FEWS/bin/fsetupcli --delivery --
patch <target
location>/${env_name}_active_backup_<yyyymmdd_hhmm>.iso
Step example
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.
6 Verify that the patched delivery is on the delivery list.

Checkifthe*.imgsoftwareimagesarecreatedunderthespecifiedfolderdirectory
onFEWS.Typethefollowingcommand:
# /mnt/myPoint/MISC/SS_FEWS/bin/fsetupcli --delivery -list
Step result
<build_name>:OK
7.1.3.2 Creating session-specific files for system restore

Purpose
Preparefilesusedduringcommissioningsession.
Procedure
1 Create a temporary mounting point.

132 2016Nokia DN09210645Issue:01C

2 Mount the extracted software image file.

Mount<build_name>.WR.mips.rmptogetaccesstosession-specificfile:
qn_fsetup.conf.
Sub-steps
a) Go to the directory where the system image is stored
Step example
b) Mount the image

# mount -o loop sysimg-<build_name>.WR.mips.rmp-mips64-
wnd.img.gz /mnt/mypoint/
Step example
# mount -o loop sysimg-R_QNCB.14.26.4_6.4.WR.mips.rmp-mips64-
wnd.img.gz /mnt/myPoint/
3 Create a directory for session files.

# mkdir /root/mySession
4 Copy the session configuration file and initialization script.

Sub-steps
a) Copy the session configuration file

Copytheqn_fsetup.confandsaveitasfsetup.conffile.The
fsetup.conffileisnecessarytoperformapplicationSWdownload,transfer
andmoduleinitialization.
Step example
b) Copy the initialization script (optional).

Ifyouperformcopythepre-configurationscriptincludedinbcninit.tgz
archive.
# cp -v /mnt/myPoint/opt/nsn/SS_QNTools/bcninit/*
/root/mySession
5 Verify if the copied files are in the session directory.

# ll /root/mySession
DN09210645Issue:01C 2016Nokia 133

Step result
ThemySessionfolderincludesthefollowingfile:
fsetup.conf
6 Unmount the temporary mounting point.

# umount /mnt/myPoint
# rmdir /mnt/myPoint
7.1.4 Creating restore session
7.1.4.1 Modifying the system restore session-specific fsetup.conf file

Purpose
Thissectiondescribeshowtomodifythefsetup.conffileaccordingtothepredicted
controllerconfiguration.
Before you start
/root/mySession/containsfsetup.conffile
Procedure
1 Log in to the FEWS.

LogintotheFEWSwithrootcredentialsandopentheterminalwindow.
2 Edit the fsetup.conf file.

Enterthesessiondirectoryandmodifythefsetup.conffileinatexteditor(for
example,nanoorvi)
# cd /root/mySession
# vi fsetup.conf
3 Edit the parameter values.

Fillintheparametersinthefsetup.conffilerequiredforthecommissioning
sessionaspresentedin.
4 Insert additional entry to the fsetup.conf file.

Insertthefollowingline:
TARGETS="FCPU-0"
134 2016Nokia DN09210645Issue:01C

Step result
(...)
COMM_NODE="FCPU"
TARGETS="FCPU-0"
COMM_VLAN="9"
(...)
5 Verify modifications.
# cat fsetup.conf
7.1.4.2 Starting restoring session

Purpose
Thissectiondescribeshowtostarttherestoringsessionwiththepre-defined
configurationstoredinthefsetup.conf file.
Procedure
1 Enter the SW delivery SS_FEWS/bin directory.
g Note: Directory<sw_build_name>.WR.mips.rmpindicatesdeliveryname,notthe
backupversion.
2 Create the commissioning session.

Writedownpasswordsspecifiedhere.Theyarenecessarylater.
# ./fsetupcli --session --create <session_name>
/root/mySession/fsetup.conf
Whenprompted,providethecorrectinformationforthesessionanddefinethe
followingparameters:
selectthefzc_sw_build
passwordforthe root
passwordforthe_nokfsoperator
3 Verify that the session is created.

# ./fsetupcli --session --list
DN09210645Issue:01C 2016Nokia 135

4 Make sure FEWS services are in correct status.

# service iptables stop
# service rpcbind restart
# service nfs restart
5 Start the session on the FEWS terminal.

StartthesessionfromtheSS_FEWS/bin/folder.
# ./fsetupcli --session --start <session name>
Verifythatthestartedsessionexists:
7.1.5 Replacing the failed hard disk drive

TheharddiskdrivecarrierAMC(HDSAM-A)isdeliveredwiththeharddiskdrivealready
inplace.QuarterlymaintenanceroutinesshouldbeperformedonHDDusingthe
DiskDiagnostictest.SeePerforming quarterly maintenance routinessectionin
Preventive Maintenance in Multicontroller RNC.
Youmayalsoneedtoreplacetheharddiskdrivefaultyorneedtobeupgradedor
serviced.
Purpose
Replacingfailedharddiskdrive.
Before you start
f CAUTION! Electrostatic discharge (ESD) damages components in the module or

other units.
WearanESDwriststraporuseacorrespondingmethodwhenhandlingtheunits,and
donottouchtheconnectorsurfaces.
TheHDSAM-AsupportsbothSASandSATAharddiskdrivesandincludesaSAS/SATA
switchforselectingthedisktype.TheBCNplatformsupportsonlytheSASharddisk
drive,thusalwayscheckthattheswitchissettoSAS,beforestartingthereplacement
procedure.
136 2016Nokia DN09210645Issue:01C

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
7.1.5.1 Removing faulty HDD
Procedure
1 Remove the AMC from the AMC bay.

FollowtheinstructionsinsectionRemoving an AMC.
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.
3 Disconnect the faulty hard disk drive.

Detachthefaultyharddiskdrivefromtheconnectorbypullingitgently(fromrightto
leftinthefollowingfigure).
Figure 17 TheharddiskdriveontheharddiskdrivecarrierAMC
Harddiskdrive
DN0945257
DN09210645Issue:01C 2016Nokia 137

7.1.5.2 Installing the new HDD
Procedure
1 Connect the new HDD to the SAS connector of the HDSAM-A.

ConnectthenewHDDtotheSASconnectorintheHDSAM-Abypushingitgently
(fromlefttorightinthefollowingfigure).
Figure 18 InstallingaharddiskdriveontotheharddiskdrivecarrierAMC
Harddiskdrive
SASconnector
DN0945245
Insertedscrew
2 Turn the AMC over and attach the new HDD to the AMC with four screws.
Tightenthescrewssothattheirheadsareinlinewiththemetalbracket.
3 Install the AMC module back into the AMC bay.

FollowtheinstructionsinsectionInstalling AMC HDD.
4 Perform a full system restore.

Performafullsystemrestore.
7.1.6 Comissioning CFPU-0
7.1.6.1 Connecting FEWS to the controller for system restore

Purpose
ThissectiondescribesconnectingFEWStoserialportandmanagementportofthe
controllerfortherestorepurposes.
138 2016Nokia DN09210645Issue:01C

Procedure
1 Connect the Ethernet and serial cables.

ConnecttheFEWSserialportandEthernetporttothecorrespondingcontroller
module'sports.Aftertheconfigurationiscomplete,connectthepatchcableback.
MgmntPort
2 Verify that the Ethernet link exists with the correct IP address.
# 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
# ping c 3 192.168.10.51
theFEWSisnotconnectedtothecontrollerfactory-commissionedmoduleone
theFEWSeth0configurationhasnotbeendoneproperly
Iftheproblemwasinthemodule'sinitialconfiguration,runtheLMPpre-configuration
accordingtoPerforming module pre-configurationinCleaninstallation.
7.1.6.2 Deactivating nodes

Before you start
Deactivateallofthecomputingnodesineverycontroller'smodule,exceptthecomputing
nodeone(FCPU-0)inthemoduleone.SWimagedownloadusesonlyFCPU-0andif
theothernodesareactiveatthesametimeadisturbancemayoccur.Thefollowing
stepsaretheinstructionsonhowtodeactivatenodeswithoutusingthecontrollermodule
DN09210645Issue:01C 2016Nokia 139

serialports.IfyouhaveconnectionfromFEWStoserialportsyoucangivethesame
deactivationcommandfromthere.
Procedure
1 Open the new terminal window from FEWS to (LMP-1-1-1).

# ssh root@192.168.10.51
Password:root
2 Deactivate all the nodes except the first one (FCPU-0) in module one.
3 Exit from LMP-1-1-1.

# exit
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
5 Deactivate all the nodes in module <N>.
6 Exit from the module <N> LMP.

# exit
7 Return to the LMP-1-1-1 by moving FEWS Ethernet connection back to the

module one MGT port.
OpentheterminalwindowfromFEWStothecontrollermoduleoneLMP(LMP-1-1-
1)
# ssh root@192.168.10.51
7.1.6.3 Downloading the SW image

Before you start
Openthesetwoterminalwindowsiftheyarenotalreadyopened:
TerminalwindowstoFEWS
SerialportterminalwindowtothecontrollermoduleoneLMP(LMP-1-1-1)
140 2016Nokia DN09210645Issue:01C

Procedure
1 Log in to the module.

Usemodule'sdedicatedIPaddressandloginviasshconnectionfromtheFEWS.
# ssh root@192.168.10.5<module number>
Step example
Ifyouwanttologintothefirstmoduleusethefollowingcommand:
# ssh root@192.168.10.51
Thentypethepasswordandyouwilllogintothefirstmodulewiththefollowing
prompt:
root@LMP-1-1-1:~#
2 Open console connection to the FCPU-0.

Logintothefirstmodulefromserialport.
Typethefollowingcommandintheprompt
root@LMP-1-1-1:~#
:
root@LMP-1-1-1:~# telnet localhost 3001
3 Enter the U-boot prompt.
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#
4 Start the DHCP client in the FCPU-0 U-boot prompt.

Kontron S1901# dhcp
DN09210645Issue:01C 2016Nokia 141

5 Upload the netboot start-up script.

Intheu-bootprompttypethefollowingcommand:
Kontron S1901# tftp 21000000 <session_name>/initial.img
Usethe<session_name>ofsessioncreatedinCreating commissioning session.
Step example
Kontron S1901# tftp 21000000 controller37/initial.img
6 Run the netboot starter script.

Kontron S1901# autoscr 21000000
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
#==================================#
7 Collect the FSETUP.LOG.

Ifcommissioningfails,capturetheFSETUP.LOGfiletoinvestigatewhatisthecause
ofthefailure.
GotoFEWSandtype:
# tail f
/opt/nsn/fews/sessions/<session_name>/log/FSETUP.LOG
g Note: Incasethefollowingprintoutappearsonthescreen:
Connection closed by foreign host.
OpenanewtelnetconnectiontoCFPU-0typingthefollowingcommand:
root@BCNMB-B:~# telnet localhost 3001
8 Reboot the FCPU-0 with the new SW image.

Whentheinstallationscriptends,thefollowingchoicesaregiven:
0: reboot node
1: debugging shell
Please select "0" or "1".
142 2016Nokia DN09210645Issue:01C

Select"0"toreboottheFCPU-0node.
9 Log in to the FCPU as _nokadmin.

Log-inis_nokadminandpasswordissystem.
10 Terminate the TELNET session and return to the LMP terminal.
a) PushCTRL+].
b) TypeQuitafterthepromptchangedto
telnet>
.
Step result
Theuseroperatesfromthe
LMP-1-1-1
.Itisindicatedbytheprompt:
root@LMP-1-1-1
7.1.7 Performing post-configuration of the controller

This section describes how to post-configure the controller. Post-configuration syncs time
on all the nodes, and unlocks the cluster.
Purpose
Tocompletecommissioning,thepost-configurationneedstobeexecutedbytheuseron
theFCPU-0.Theclusterisnotreadyfornormaloperationuntilpost-configurationis
executed.Afterthepost-configurationiscompleted,thecontrollerSWisstarted,
unlocked,andreadyforoperation.
Procedure
1 Log in from LMP-1-1-1 to FCPU-0 as _nokfsoperator user.

# ssh _nokfsoperator@FCPU-0
The_nokfsoperatorpasswordwasgiveninsession-specificfsetup.conffile.
2 Run the post-configuration script.

# fsetupcli post configure --nodes=CFPU-0,CFPU-1
# fsetupcli post configure --nodes=FCPU-0
g Note: Thepostconfigurescriptapproximatelytakes40minutestoaccomplish.
DN09210645Issue:01C 2016Nokia 143

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]
#
7.1.8 Restoring from backup ISO

Procedure of restoring the system and configuration from backup ISO.
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
Checkthestatuswiththeshow has state managed-object /<mo-name>
Step example
show has state managed-object /CLM
144 2016Nokia DN09210645Issue:01C

Step result
OBJECT ADMINISTRATIVE OPERATIONAL USAGE ROLE PROCEDURAL

DYNAMIC
/CLM LOCKED DISABLED IDLE - NOTINITIALIZED -
2 Lock file system recovery groups.

Lockthefilesystemrecoverygroupsconfiguredtobeautomaticallyincludedinthe
backupandrestore.LockthefilesystemRGsbyexecutingthefollowingcommands:
set has lock managed-object /CLM
set has lock force managed-object /QNOMU
3 Lock database recovery group.

set has lock managed-object /QNDBRNW
4 Perform full restore.

Performfullrestorewiththefollowingcommands:
start restore backup-iso <path-to-backup.iso> full
commit restore
Step example
root@FCPU-0 [mc-646] > start restore backup-iso /backup/FZC
-646_active_backup_20150325_1030.iso full
root@FCPU-0 [mc-646] > commit restore
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
DN09210645Issue:01C 2016Nokia 145

5 Unlocking file system and database recovery group.

Whenrestoreoperationissucceeded,thefilesystemandrecoverygroupare
unlocked.
Unlockthefilesystemrecoverygroupsconfiguredtobeautomaticallyincludedinthe
backupandrestore.
#fsclish
set has unlock managed-object /QNDBRNW
set has unlock managed-object /QNOMU
set has unlock managed-object /CLM
6 Restart the controller.

Toactivatetherestoredconfiguration,restarttheclusterbyexecutingthefollowing
commandfromFCPU-0:
set has restart config-check no-check managed-object /
Step result
Systemrestartsnormally
7.1.9 Activating and unlocking nodes

Purpose
Thissectiondescribeshowtoactivateandunlockthecontrollernodes.
Procedure
1 Activate the remaining nodes.

AftertheFCPU-0nodesarerestarted,waituntiltheyareinitialized.Logintothe
nodestoverifytheirinitialization.
Afteractivatingthenodes,theybootupandmaybeinthelockedstate.Thefollowing
stepsaretheinstructionsonhowtoactivatethenodesinthemodule.
Activateallthenodesinmoduleonewiththefollowingcommand:
Activateallthenodesinmodule<N>.
g Note: Beforemovingtothenextstep,ensurethatalltheactivatednodesarebooted
up.
Step result
Allnodesbootupnormally.
2 Unlock the nodes.

FromFCPU
146 2016Nokia DN09210645Issue:01C

-0,executethefollowingcommand:
#fsclish
set has unlock all
Step result
Allnodesunlocksnormally.
7.1.10 Checking system states and saving configuration

Purpose
Thissectiondescribeshowtocheckthecontroller'sstateaftertheapplicationsoftware
installation.
Procedure
1 Log in to FCPU-0 as _nokadmin user

# ssh _nokadmin@FCPU-0
Password: system

show alarm active-summary
3 List information for a given active alarms.

show alarm active filter-by specific-problem <alarm_id>

show has filter node state managed-object /*
Step result
Statusforallnodesis:
UNLOCKED / ENABLED / ACTIVE
5 Check the recovery groups state.

Usethefollowingcommand:
show has filter rg state managed-object /*
DN09210645Issue:01C 2016Nokia 147

Step result
Statusforalltherecoverygroupsis:
6 Check the SW build status.

> show sw-manage app-sw-mgmt builds
Step result
ThestatusoftherunningSWbuildis
BU
.
SW Build status: BU (Active)
7 Change SW build status if it is not BU (Active)

set sw-manage app-sw-mgmt change-status current-sw-build-
status NW new-sw-build-status BU
8 Save the running build's configuration.

> save snapshot
9 Verify that a fallback package exists.

Whenfallbackiscreatedcorrectly,aSWBuildinstatusFBexists.Verifythiswiththe
followingcommand:
Step result
Iffallbackdoesnotexist,createitwithcommand:save sw-manage app-sw-

mgmt fb-build build-name <build_name>
7.2 FZC clean installation

This section describes how to commission a Flexi Zone Controller through a clean
installation procedure.
ThecleaninstallationprocedureshouldonlybeperformediftheFlexiZoneController
failedtohaveitspre-commissionedfactorysettingsverified.
148 2016Nokia DN09210645Issue:01C

7.2.1 Introduction to clean installation

Cleaninstallationreferstothecommissioningtasksthatareperformedonthesiteafter
thehardwareinstallationhasbeensuccessfullycompleted.Performacleaninstallation
whenassumingincorrecteSWorSWbuildinstalledontheharddisk.
AftercleaninstallationFZCnetworkelementisreadyforsitespecificintegration.
7.2.1.1 Clean installation preconditions

1. ThecontrollerHWinstallationissuccessfullycompleted.
HWinstallationisdescribedinthefollowingdocuments:
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.
7.2.1.2 Application software installation overview
ThekeytoolinapplicationSWinstallationistheFEWS.Itisalaptoporotherworkstation
thatisusedforpreparationoftasksthatmustbeperformedbeforethesoftware
commissioningisstarted.Italsooffersservicesforbootingupthecommissioningnode
forthefirsttime,storageforthesoftwarebuilddelivery,andforthecommissioning
configurationfilesandlogs.
The main steps in clean installation are:
PreparingSWdeliveryonFEWS
DN09210645Issue:01C 2016Nokia 149

InstallingapplicationSWpackagetothecontroller
Performingpost-configuration
Upgradingembeddedsoftware
Verifyingcommissioning
7.2.2 Preparing SW delivery on the FEWS

Purpose
Thischapterdescribeshowtoextractandcopyallthenecessaryfilesfromthedelivery
.ISOimage.PerformontheFEWSalltheproceduresdescribedinthischapter.
7.2.2.1 Copying software delivery .ISO image to FEWS
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 ~]#
2 Define the build_name that you are going to install.

# build=<build_name>
Example
SWdeliverynameisR_QNCB.13.5.5_10.WR.mips.rmp.iso
# build=R_QNCB.13.5.5_10
3 Define the build_name that you are going to install.

# build=<build_name>
Example
SWdeliverynameisFLC15A_ENB_1411_001_66.iso
# build=FLC15A_ENB_1411_001_66
4 Create a temporary directory (myDelivery) for the ISO delivery.

Example
# mkdir -p /tmp/myDelivery
150 2016Nokia DN09210645Issue:01C

5 Copy the ISO delivery to the FEWS.

Usescpcopy,FileZilla,orremovablemedia(usingLinuxGUI).
TosecurelycopytheISOdelivery,typethefollowingcommand:
# scp <user@xx.xx.xx.xx>:/<path>/${build}.WR.mips.rmp.iso
/tmp/myDelivery
6 Copy the ISO delivery to the FEWS.

Usescpcopy,FileZilla,orremovablemedia(usingLinuxGUI).
TosecurelycopytheISOdelivery,typethefollowingcommand:
# scp <user@xx.xx.xx.xx>:/<path>/${build}.WR.mips.rmp.iso
/tmp/myDelivery
Example
#scp user@chling14.americas.nsn-net.net: /fzmRel/FZC_ISO/
FLC15A_ENB_1411_001_66_release_BTSSM_downloadable.zip
/tmp/myDelivery
#cd /tmp/MyDelivery #unzip
FLC15A_ENB_1411_001_66_release_BTSSM_downloadable.zip # ls
/tmp/MyDelivery/
Result
FLC15A_ENB_1411_001_66.iso
TargetBD_FLC15A_ENB_1411_001_66.xml
7.2.2.2 Extracting software .ISO image to a delivery folder
Procedure
1 Mount the .ISO delivery under /mnt/myPoint directory.

UsetheSS_FEWSsubsystemfromthesoftwaredelivery(.ISOimage)toensure
compatibilitythroughoutthecommissioningprocess.TheSS_FEWSsubsystem
containscommandlinetoolsforextractingandmountingthesoftwaredeliveryinthe
FEWS.
Createtemporarymountingpointwiththefollowingcommand:
Mountthe.ISOdeliverywiththefollowingcommand:
# mount -o loop /tmp/myDelivery/${build}.iso /mnt/myPoint
2 Patch (extract) the .ISO delivery using the fsetupcli script.

Typethefollowingcommand:
DN09210645Issue:01C 2016Nokia 151

patch /tmp/myDelivery/${build}.iso
t Tip: Patchingthedeliverytakesabout5-20minutes.Duringthattime,thereisno
indicationofprogressvisibleonthescreen.
Oncethepatchingisdone,the*.imgsoftwareimagesarecreatedunderthefollowing
directoryonFEWS:
/opt/nsn/fews/deliveries/<build_name>/
3 Verify that the patched delivery is on the delivery list.

Checkifthe*.imgsoftwareimagesarecreatedunderthespecifiedfolderdirectory
onFEWS.Typethefollowingcommand:
# /mnt/myPoint/MISC/SS_FEWS/bin/fsetupcli --delivery -list
Step result
<build_name>:OK

7.2.2.3 Creating session-specific files

Purpose
Thischapterdescribeshowtocopyfilesusedduringacommissioningsessiontoa
session-specificfolder.ThesefilesarenecessarytoperformapplicationSWdownload,
moduleinitialization,andembeddedSWupgrade.
Procedure
1 Create a temporary mounting point.

2 Mount the extracted software image file.

Mount*.rm.imgtogetaccesstosession-specificfiles.
Sub-steps
a) Go to the directory where the system image is stored
152 2016Nokia DN09210645Issue:01C

Step example
b) Mount the image

# mount -o loop ${build}.WR.mips.rm.img /mnt/myPoint
Step example
# mount -o loop R_QNCB.14.26.4_6.4.WR.mips.rm.img /mnt/myPoint
3 Create a directory for session files.

# mkdir /root/mySession
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
# 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
5 Verify if the copied files are in the session directory.

# ll /root/mySession
Step result
ThemySessionfolderincludesthefollowingfilesandpackages:
fsetup.confandbcninit.tgz,and<esw_build_name>.tar.gz.

7.2.3 Upgrading FZC embedded software

This section presents how to perform a manual eSW upgrade for the FZC's motherboard
or add-in card.
DN09210645Issue:01C 2016Nokia 153

7.2.3.1 Preparing FEWS for eSW upgrade

Before you start
ThischapterdescribeshowtoprepareeSWfilesfortransfertothecontrollermodule.
Procedure
2 Define the esw variable.

TheeswvariableisusedlateronduringeSWupgradeprocedure.Defineitwiththe
followingcommand:
# esw=<esw_build_name>
Example
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.
4 Extract and copy motherboard eSW files to the /tftpboot/<esw> folder.

# tar -zxvf ${esw}.tar.gz
# tar -zxvf ${esw}/bcnmb-b/bcnmb-b_ad_advtool*.tgz
# mkdir /tftpboot/${esw}
# cp -vr bcnmb-b_ad_tool*/LMP/* /tftpboot/${esw}/
5 Copy add-in cards eSW files to the destination folder.

CopyBMPP2-BeSWfilesto /tftpboot/<esw>folderwiththefollowing
command:
# cp -vr ./${esw}/bmpp2-b /tftpboot/${esw}/
154 2016Nokia DN09210645Issue:01C

6 Copy the LMP pre-configuration tool to the destination folder.

LMPpre-configurationtoolisdeliveredasagroupofbcninitfiles.Copythemto
/tftpboot/<esw>folderwiththefollowingcommand:
# cp -vr bcninit.* /tftpboot/${esw}/
7 Verify if the eSW-upgrade files are copied to tftpboot directory.
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
b_kn_mmbl_02_09_0000.tgz
b_kn_mmcf_02_15_0000.tgz
b_kn_octf_02_16_0000.tgz
b_kn_pcpl_02_15_0000.tgz
DN09210645Issue:01C 2016Nokia 155

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
8 Define the cpu_esw_build variable.

Sub-steps
a) Go the specific folder with the following command # ll

/tftpboot/${esw}/bmpp2-b/
b) Check the variable name from the bmpp2-

b_kn_octf_<cpu_esw_build>.tgz file.
c) See defined variable with the command: # echo ${cpu_esw_build}
Example:bmpp2-b_kn_octf_02_16_0000.tgz
Definethevariablewiththefollowingcommand:#
cpu_esw_build=02_16_0000
g Note: Definevariableisvalidonlyforaterminalsessionduringwhichitwascreated.
7.2.3.2 Connecting FEWS to the controller module

Purpose
ThischapterdescribeshowtoconnectFEWStothecontrollermoduleusingserialand
Ethernetcables.
Procedure
1 Connect the Ethernet and serial cables.

ConnecttheFEWSserialportandEthernetporttothecorrespondingcontroller
module'sports.Startfromthefirstmoduleinordertoupgrade.
g Note: Itislikelythatduringthecommissioningprocedureyouarepromptedtoconnect
totheother(next)controllermodulesaswell.
Theseriallinesettingsfortheconsoleconnectionareasfollows:
Daterate:115200
Parity:N
Databits:8
Stopbits:1
Flowcontrol:Xon/Xoff
156 2016Nokia DN09210645Issue:01C

MgmntPort
2 Configure the Ethernet port IP addresses of FEWS.

ConfigurethetwoIPaddressesfortheFEWSEthernet:
10.10.10.1/24forconnectiontothecontrollerwithfactorysettings
192.168.10.250forconnectiontothecontrollermoduleafterLMPpre-
configurationorforeSWdownload
Example:
3 Activate the FEWS Ethernet link.

EnterthefollowingcommandonFEWS:
# ip link set eth0 up
4 Verify that the Ethernet link exists with the correct IP address.
# ip addr show eth0
Step result
EthernetportmusthavetwoactiveIPaddresses:192.168.10.250and10.10.10.1
5 Make sure that FEWS services are in the correct status.

DN09210645Issue:01C 2016Nokia 157

7.2.3.3 Upgrading the BCN motherboard's eSW

Before you start
UsetheserialportconnectiontoupgradetheBCNmotherboardupgradeableparts.
Procedure
1 Log in to the module's LMP using the serial connection.

Username:root
Password:root
2 Check the current software version.

IntheLMPusethefollowingcommandtochecktheversion:
root@LMP-1-1-1:~# sw_fw_versioninfo
3 Reboot the LMP and stop autoboot.

ReboottheLMPwithCLIcommandandstopautobootbypressingtheukeywhena
promptappears.
# reboot
Hit key 'u' to stop autoboot
Step result
Sinceautobootstoppedthefollowingpromptappears:
BCNMB#
4 Define the esw_build_name and motherboard_esw_version variables in

the controller.
# esw=<esw_build_name>
# mbesw=<motherboard_esw_version>
Step example
# 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
158 2016Nokia DN09210645Issue:01C

# set bootfile ${esw}/uImage

# set fdtfile ${esw}/ncp20000.dtb
# set othbootargs ramdisk_size=350000k
# saveenv
6 Verify the boot variables.

# printenv
7 Run ramboot.
# run ramboot
8 Log in as root after the ramboot process is finished.

# BCN-UPGRADE login:root
Password:root
Step result
Thefollowingpromptappears:
root@BCN-UPGRADE#
9 Upgrade the botherboard by running the upgrade script.

Invokeupgrade.shscriptwiththefollowingcommand:
root@BCN-UPGRADE:~#/opt/upgrade/upgrade.sh
Thefollowingmenuappears:
BCN Upgrade Program SW ver 5.9.6 VCMC 5.9.4
===================================================
1. Fully automatic upgrade (BCNMB + BOC-A WR 4.x)
2. Simple automatic upgrade (BCNMB + BOC-A WR 4.x without Linux)
3. BCNMB upgrade (BCNMB only)
4. Manually upgrade
5. Repair options
6. Full Box Upgrade w/ OcteonII {[BCNMB] + [BMPP2-B(u-Boot)]}
7. Full Box Upgrade w/ OcteonII {[BCNMB] + [BMPP2-B(u-
boot/kernel/rootfs)]}
0. QUIT
===================================================
Selectupgradeoption:
3. BCNMB upgrade (BCNMB only)
Step result
MotherboardLMPeSWisbeingupgradedautomatically.
DN09210645Issue:01C 2016Nokia 159

10 Quit the upgrading script.

Whenmotherboardupgradeisready,thesamemenuappears.Select0. QUITand
hitENTERinordertoquitandreturnbacktotheLMPprompt.
11 Restart the LMP and log in again.

Inordertoreboot,enterthefollowingcommand:
# reboot
g Note: Donotinterrupttheautobootprocess.AftertheLMPboothasbeencompleted,
loginasroot.
12 Verify that the eSW is upgraded successfully.

# sw_fw_versioninfo
Step result
Motherboardcomponents'eSWhavesoftwareinversionsdescribedintherelease
notes.
7.2.3.4 Upgrading the BMPP2-B add-in cards' eSW

Before you start
Add-incardsembeddedsoftwareisinstalledcard-by-cardineachFZCmodule
separately.Duringtheupgradeprocessyoumustconnecttoeachmoduleviaserialand
Ethernetconnection.
g Note: Thetermmoduleinthefollowinginstructionsreferstothecurrentmodulewhere
theuserisconnected.
Procedure
1 Log in to the module's LMP using the serial connection.

Sub-steps
a) If a motherboard eSW upgrade or factory settings restoration has been

done:
Enter# ssh root@10.10.10.10
Enterthepassword:root
b) Otherwise enter # ssh root@192.168.10.5<N>

<N>standsformodulenumber.
160 2016Nokia DN09210645Issue:01C

2 Log in to the add-in card of the module.
Step example
Foradd-incardnumberone,loginwiththefollowingcommand:# telnet
localhost 3001
Logintoeachadd-incardofFZCmodulestartingfromfirstcard.Establishatelnet
connectionwiththefollowingcommand:# telnet localhost 300<x>
Add-in card Telnet port

number
1 3001
2 3002
3 Reboot the add-in card and stop autoboot.

Sub-steps
a) Go to the u-boot prompt, Kontron S1901#
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
4 Load the add-in card's Linux from add-in card flash.

Enterthefollowingcommand:# run bootscript_70
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.
#
DN09210645Issue:01C 2016Nokia 161

5 Copy the bmpp2-b-upgrade.sh script shown below to a text editor.

rm /tmp/bmpp2-b-upgrade.sh
cat <<\! > /tmp/bmpp2-b-upgrade.sh
#!/bin/ash
# bmpp2-b KONTRON Octeon II upgrade
#
# Steps in cpu Linux
# Upgrade SPIF,MMC,FRU,OCT
# Swap FLASH bank,
# Upgrade SPIF,MMC,FRU,OCT
# Swap FLASH bank
# Done
#
# Step in LMP
# Upgade cpu power CPLD <cpu>
# Done
#
# Execute bmpp2-b-upgrade.sh.<md5> in cpu Linux:
# ...
# u
# Kontron S1901# run bootscript_70
#
# chmod +x /tmp/bmpp2-b-upgrade.sh.<md5>
# /tmp/bmpp2-b-upgrade.sh.<md5> <FEWS IP> <mgmt0 IP>
#
# firmware-activate --swap --powercycle
# ...
# u
# Kontron S1901# run bootscript_70
#
# chmod +x /tmp/bmpp2-b-upgrade.sh.<md5>
# /tmp/bmpp2-b-upgrade.sh.<md5> <FEWS IP> <mgmt0 IP>
#
#
# Before use put bmpp2-b*${ver}.tgz images to FEWS /tftpboot/${esw}/
directory.
#
# History:
#
# 0.0.1 -- initial implementation
# 0.0.2 -- input cpu number as $1 e.g. bmpp2-b-upgrade.sh 1
# and some echo's added
# 0.0.3 -- get cpu mgmt0 IP and FEWS ${net} by using FEWS DHCP.
# 0.0.4 -- file integrity hash check added bmpp2-b-upgrade.sh.<md5>
# 0.0.5 -- No DHCP lease check added
# 0.0.6 -- fewsip and mgmt0ip arguments added, DHCP removed
# 0.0.7 -- spif
# 0.0.8 -- Usage: prompt, err exits, clean up /tmp
#
# Set eSW and bmpp2-b firmware GA version
#
162 2016Nokia DN09210645Issue:01C

esw=<esW_build_name>
sw="GA\s"
ver=<cpu_esw_build>
# example:
# 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}
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 .
tar -xzvf bmpp2-b_kn_mmcf_${ver}.tgz
DN09210645Issue:01C 2016Nokia 163

tar -xzvf bmpp2-b_kn_frud_${ver}.tgz

tar -xzvf bmpp2-b_kn_octf_${ver}.tgz bmpp2-b_kn_octf_${ver}/bmpp2-
b_kn_octf_${ver}.pkg
tar -xzvf bmpp2-b_kn_spif_${ver}.tgz
tar -xzvf bmpp2-b_kn_pcpl_${ver}.tgz
#
# Updating the PCIe EEPROM (SPIF)
#
echo "firmware-update --apply --type SPIF bmpp2-
b_kn_spif_${ver}/bmpp2-b_kn_spif_${ver}.pkg"
firmware-update --apply --type SPIF bmpp2-b_kn_spif_${ver}/bmpp2-
b_kn_spif_${ver}.pkg
#
# MMC
#
echo "time firmware-update --apply --type IPMI bmpp2-
b_kn_mmcf_${ver}/bmpp2-b_kn_mmcf_${ver}.pkg"
time firmware-update --apply --type IPMI bmpp2-
b_kn_mmcf_${ver}/bmpp2-b_kn_mmcf_${ver}.pkg
#
# FRU
#
echo "time firmware-update --apply --type FRUDATA bmpp2-
b_kn_frud_${ver}/bmpp2-b_kn_frud_${ver}.pkg"
time firmware-update --apply --type FRUDATA bmpp2-
b_kn_frud_${ver}/bmpp2-b_kn_frud_${ver}.pkg
#
# OCT
#
echo "time firmware-update --apply --type ALL --image backup bmpp2-
b_kn_octf_${ver}/bmpp2-b_kn_octf_${ver}.pkg"
time firmware-update --apply --type ALL --image backup bmpp2-
b_kn_octf_${ver}/bmpp2-b_kn_octf_${ver}.pkg
#
# Check bootloader security hash and version
#
cat /proc/mtd
md5sum /dev/mtd0 /dev/mtd5
strings /dev/mtd0 /dev/mtd5 | grep ${sw}
#
# Clean up /tmp
#
rm /tmp/bmpp2-b-upgrade.sh
rm -rf /tmp/bmpp2-b_kn*
#
164 2016Nokia DN09210645Issue:01C

# swap FLASH banks (better give this one from shell)

#
echo "Please give command: firmware-activate --swap --powercycle"
!
chmod +x /tmp/bmpp2-b-upgrade.sh
/tmp/bmpp2-b-upgrade.sh 192.168.10.250 192.168.10.59
6 Edit the required lines of the script.

esw=<esw_build_name>
ver=<cpu_esw_build>
Step example
esw=R_BCNESW_14_39_FP1
ver=02_16_0000
7 Run the script.

Copyandpastetheeditedscripttoadd-incardprompt.HitEntertorunthe
promptedscript.
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.
10 Load the add-in card's Linux from add-in card flash.

Enterthefollowingcommand:# run bootscript_70
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.
#
11 Assign IP address to mgmt0 port.

# ifconfig mgmt0 192.168.10.59
DN09210645Issue:01C 2016Nokia 165

12 Copy and paste the edited script to add-in card prompt. Hit Enter to run the
prompted script.
13 Activate updated add-in card's eSW.

WhenscriptcompletesactivateupgradedeSWandswapflashbank.Typethe
followingcommand:firmware-activate --swap --powercycle
g Note: Donotinterrupttheautobootprocess.
14 Repeat steps 2 to 14 to all add-in card inside one module.
7.2.4 Performing module pre-configuration
7.2.4.1 Running pre-configuration script
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.
Before you start

ForthecleaninstallationofthenewmcRNCsystemprepare:relevantracknumber,
andNetworkElementIDforthenewnetworkelement.
ForrestoringthemcRNCsystemonthenewcontrollerclusterprepare:relevantrack
number,NetworkElementIDoftheoriginalcontroller.
166 2016Nokia DN09210645Issue:01C

Procedure
1 Log in to FEWS as root and open the terminal window.

Userootaccountcredentialstologin.Opentheterminalwindowafteryouloggedin.
2 Verify the connection from FEWS to module under pre-configuration.

# ping c 3 10.10.10.10
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.
3 Troubleshoot connection (optional):

IfpingpacketsarelostitmeansthattheconnectionbetweenFEWSandthe
controllermoduleisnotsetproperly.
CheckthecablesbetweentheserialandEthernetports.
ThispacketlossmightalsoindicatethatLMPeth0addressiswrong.This
happenedduetotheattemptofrunninganLMPpre-configurationonthe
controllermodulethatisalreadypre-configuredanditsIPaddressmightbe
differentthan10.10.10.10.
Step example
Sendpingpacketstooneofthepre-configuredmodulesusingfollowingcommand:
# ping c 3 192.168.10.51
Checkifallpingpacketsarereceived.Thisindicatesiftheconnectionisestablished
properly.
Step result
Ifpingpacketsarereceived,theIPaddressingschemeofLMP'seth0isequalto
LMPeth0portconfiguration.
DN09210645Issue:01C 2016Nokia 167

4 Copy the bcninit.tgz package to the module under pre-configuration.

# scp bcninit.* root@10.10.10.10:/opt/bcntools
Securecopyingrequestmaycausesecuritywarnings.Theseareindicatedinthe
followingmessages:
YoumustaddRSAkeytothelistofknownhosts.
The authenticity of host '10.10.10.10 (10.10.10.10)' can't be
established.
RSA key fingerprint is
74:4d:26:00:75:22:a2:98:d3:74:a2:16:91:d0:a9:4a.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.10.10.10' (RSA) to the list of
known hosts.
root@10.10.10.10's password: root Last login: Wed Sep 4 10:44:28
2013
TheSSHconnectionattemptfailsandyougettheRSAhostkeychangewarning
thatrequireschecking.
@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION

HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle
attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
da:b8:e4:c2:5e:8e:dc:da:65:ef:82:5f:1b:22:20:1e.
Please contact your system administrator. Add correct host key in
/root/.ssh/known_hosts to get rid of this message.
Offending key in /root/.ssh/known_hosts:4 RSA host key for
10.10.10.10 has changed
and you have requested strict checking.
Host key verification failed. lost connection
Removeerror-causingIPwiththefollowingcommand:
ssh-keygen -R 10.10.10.10
Performthesecurecopy(scp)again.
5 Log in to the module under the pre-configuration LMP.

Intheterminalwindow,enterthefollowingcommand:
# ssh root@10.10.10.10
Password:root
6 Extract the bcninit.tgz package.

IntheLMP,enterthefollowingcommands:
# cd /opt/bcntools/
# tar -zxf bcninit.tgz -C /opt/bcntools
168 2016Nokia DN09210645Issue:01C

7 Enter the pre-configuration script folder.

# cd /opt/bcntools/bcninit
Checkwhetherthenode.shscriptislocatedinthefolderbyusingthels -lsa
command.
8 Run pre-configuration script.

Thepre-configurationscriptisnamedasnode.sh.
Invokethescriptwiththefollowingcommand:
./node.sh <Module number> <Add-in card type> <NE-ID>
UseparametersaccordingtotheTable11:Requiredpre-configurationscript
parameters
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
7.2.4.2 Setting the LMP date
Procedure
1 Check the date.

# date
2 Set the date and time equal to Coordinated Universal Time (UTC), if needed:
# date --s "<day month year hour:minute:second>"
Example:
DN09210645Issue:01C 2016Nokia 169

# date --s "22 Jan 2015 14:15:00"
3 Show the current hardware clock.

# hwclock -show
4 Synchronize the hardware clock if needed.

# hwclock --systohc
5 Check if the hardware clock is synchronized with the system date.

# hwclock -show
7.2.4.3 Activating the LMP pre-configuration changes
Procedure
1 Activate the LMP pre-configurations

ActivatetheLMPpre-configurationswiththecontrollermoduleresetusing#
mch_cli Reset BCNcommand.
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.
7.2.4.4 Verifying module's LMP pre-configuration

Purpose
ThischapterdescribeshowtoverifyiftheLMP'spre-configurationrestorationisdone
correctly.
170 2016Nokia DN09210645Issue:01C

Procedure
1 Test the connection to the module.

Performthisstepfiveminutesafterrestart.
# ping -c 3 192.168.10.5<module number>
Step example
# ping -c 3 192.168.10.51

Step example
# ssh root@192.168.10.51
prompt:
root@LMP-1-1-1:~#
3 Verify the rack number of the controller module.

Everymoduleintheclusterneedstohavethesameracknumberbutthenode
numberchangesconsecutivelyfrom1to2.
root@lmp-1-1-1:~# mch_cli GetRackNumber
Step result
Allcontrollermoduleshavethesameracknumber:
1
4 Verify the module number against its position in the cabinet.

root@lmp-1-1-1:~# mch_cli GetNodeNumber
Step result
Nodenumberisthesameasmodule(chassis)number.
1
DN09210645Issue:01C 2016Nokia 171

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
7 Verify the correct back-plane resiliency configuration.

# pwd; ls -lsa /mnt/fastpath/ | grep module
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
8 Verify the correct switch configuration:

# cat /mnt/fastpath/module/post.soc
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
172 2016Nokia DN09210645Issue:01C



0:modreg ing_egrmskbmap.2 bitmap=0x00000000
0:linkscan spbm=0x1fffffff interval=10000
0:setreg CPUPKTPORTMAXBUCKETCONFIG PKT_PORT_MAX_THD_SEL=0x400
PKT_PORT_MAX_REFRESH=0x400
9 Continue verifying the correct switch configuration:

# cat /mnt/fastpath2/module/post.soc
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
10 Verify the trunk interface configuration:

# grep -I trunk /mnt/fastpath*/module/post.soc
Ifanyoftheselinesisfound,performthesub-stepsbelow:
/mnt/fastpath/module/post.soc:trunk add id=0 pbmp=0x18
/mnt/fastpath2/module/post.soc:trunk add id=0 pbmp=0x3000000
Sub-steps
a) Enter this command:

# sed -ie '/^trunk/d' /mnt/fastpath*/module/post.soc
b) Power Cycle the module (Physically restart the controller).
AfterthemodulepowercyclesyoushouldrestarttheLMPverificationfromthe
beginning.
DN09210645Issue:01C 2016Nokia 173

11 Repeat all the steps for all of the modules inside the deployed controller
cluster.
7.2.5 Installing the SW package application to the controller

Purpose
ThischapterdescribeshowtoinstallthecontrollerSWtotheFCPUharddiskdrive.
7.2.5.1 Modifying the session-specific fsetup.conf file

Purpose
Thissectiondescribeshowtomodifythefsetup.conffileaccordingtothepredicted
controllerconfiguration.
Procedure

LogintotheFEWSwithrootcredentialsandopentheterminalwindow.
2 Edit the fsetup.conf file.

Enterthesessiondirectoryandmodifythefsetup.conffileinatexteditor(for
example,nanoorvi)
# vi fsetup.conf
3 Edit the parameter values.

ParametersthatarerequiredforthecommissioningsessionarepresentedinTable
12:Commissioningparametersinfsetup.conffile.
Fillintheparametersinthefsetup.conffileaccordingtothetable.
Table 12 Commissioningparametersinfsetup.conffile
Variable Definition
DELIVERY <build name>.WR.mips.rmp
TIMEZONE Thisparameterdefinesthetimezone.
CLUSTERID Thisparameterdefinesthenameofthenetworkelement.Thename
isvisibleinthecontrollerpromptafterthecommissioningisdone.
TheparameterformatisFZCxx.
COMM_IFACE ThisparameterdefinesthenetworkinterfaceintheFEWSthatis
usedforthecommissioning.ForFZCthevalueshouldbeeth0.
174 2016Nokia DN09210645Issue:01C

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.
BCN-B one-box/two-card configuration (FZC):

# Used deployment script, if left empty (DEPLOYMENT="") it will
ask
which deployment is used
DEPLOYMENT="create_fzc_bcnb_2slots.sh"
# Used delivery, if left empty (DELIVERY="") it will ask which

delivery is used
DELIVERY=""
# Wanted timezone, if left empty (TIMEZONE="") it will ask which

time
DN09210645Issue:01C 2016Nokia 175

zone
TIMEZONE="America/Chicago"
# Wanted cluster ID in format FZCXXX, where XXX is the used FZC ID

CLUSTERID="FZC1"
# Following describes what interface and network is used in FEWS

server, be carefull not to enable this
# to interface that has hosts that are not meant to get IP's from
this network. Session starts dhcpd service
# that gives ip addresses to whoever wants to have it.

COMM_IFACE="eth2"
COMM_NETWORK="192.168.11.0/24"
COMM_FEWSIP="192.168.11.250/24"
# This directory can include SCLI scripts that are executed as

part
of postconfig, uncomment the line in case
# this feature is wanted to be used. Noticed that all SW is not

yet
up in postconfig phase so mainly ip config
# can be configured
COMM_USER_CONFDIR="/user_cfg"
# For debug
DEBUG="1"
# Session will start automatically if this value is true

COMM_SESSION_AUTOSTART="true"
# Following must not be changed

COMM_NODE="FCPU"
SINGLECLA="true"
HW_PLATFORM="BCN"
CPU_TYPE="mips64"
COMM_IPMGMT_INTERNAL_IFACE="xaui0"
COMM_IPMGMT_MGMT_SUBNET="169.254.240.0/24"
COMM_IPMGMT_INTERNAL_SUBNET="169.254.241.0/24"
AUTO_POSTCONFIG="false"
7.2.5.2 Creating commissioning session

Purpose
Thissectiondescribeshowtocreatethecommissioningsessionwiththepre-defined
configurationstoredinthefsetup.conf file.
176 2016Nokia DN09210645Issue:01C

Procedure
1 Enter the SW delivery SS_FEWS/bin directory.

# cd
/opt/nsn/fews/deliveries/<sw_build_name>/MISC/SS_FEWS/bin/
2 Create the commissioning session.

Writedownpasswordsspecifiedhere.Theyarenecessarylater.
# ./fsetupcli --session --create <session_name>
Whenprompted,providethecorrectinformationforthesessionanddefinethe
followingparameters:
selectthefzc_sw_build
passwordforthe root
passwordforthe_nokfsoperator
3 Verify that the session is created.

4 Make sure FEWS services are in correct status.

# service rpcbind restart
5 Start the session on the FEWS terminal.

StartthesessionfromtheSS_FEWS/bin/folder.
# ./fsetupcli --session --start <session name>
Verifythatthestartedsessionexists:
7.2.5.3 Connecting FEWS to the controller with Ethernet port configured

Purpose
ThissectiondescribeshowtoconnecttheFEWStothecontrollerforthecommissioning
purposesandconfigureIPsubnet.
DN09210645Issue:01C 2016Nokia 177

Procedure
1 Connect the Ethernet cable.

ConnecttheFEWSEthernetporttothecontroller'smoduleoneMGTport.Remove
theexistingEthernetpatchcablefromthemoduleoneMGTandconnecttheFEWS
cable.Aftertheconfigurationiscomplete,connectthepatchcableback.
2 Verify the Ethernet link status and settings.

OntheFEWS,enterthefollowingcommand:
# ip addr show eth0
Step result
TheEthernetportmusthavetwoactiveIPaddresses:192.168.10.250and
10.10.10.1.
3 Verify connection between FEWS and the controller module one LMP.
Sendpingpackttocheckwhethertheconnectionisconfiguredproperly.Onthe
# ping c 3 192.168.10.51
theFEWSisnotconnectedtothecontrollermoduleone
theFEWSEthernetlinkconfigurationhasnotbeendoneproperly
theLMPpre-configurationhasfailed
IftheproblemisinmoduleinitialconfigurationrunLMPpre-configurationaccording
toPerforming module pre-configuration.
7.2.5.4 Downloading the SW image

Before you start
178 2016Nokia DN09210645Issue:01C

Openthesetwoterminalwindowsiftheyarenotalreadyopened:
TerminalwindowstoFEWS
SerialportterminalwindowtothecontrollermoduleoneLMP(LMP-1-1-1)
Procedure

Step example
# ssh root@192.168.10.51
prompt:
root@LMP-1-1-1:~#
2 Open console connection to the FCPU-0.

Logintothefirstmodulefromserialport.
Typethefollowingcommandintheprompt
root@LMP-1-1-1:~#
:
root@LMP-1-1-1:~# telnet localhost 3001
3 Enter the U-boot prompt.
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#
DN09210645Issue:01C 2016Nokia 179

4 Start the DHCP client in the FCPU-0 U-boot prompt.

Kontron S1901# dhcp
5 Upload the netboot start-up script.

Intheu-bootprompttypethefollowingcommand:
Kontron S1901# tftp 21000000 <session_name>/initial.img
Usethe<session_name>ofsessioncreatedinCreating commissioning session.
Step example
Kontron S1901# tftp 21000000 controller37/initial.img
6 Run the netboot starter script.

Kontron S1901# autoscr 21000000
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
#==================================#
7 Collect the FSETUP.LOG.

Ifcommissioningfails,capturetheFSETUP.LOGfiletoinvestigatewhatisthecause
ofthefailure.
GotoFEWSandtype:
# tail f
/opt/nsn/fews/sessions/<session_name>/log/FSETUP.LOG
g Note: Incasethefollowingprintoutappearsonthescreen:
Connection closed by foreign host.
OpenanewtelnetconnectiontoCFPU-0typingthefollowingcommand:
root@BCNMB-B:~# telnet localhost 3001
180 2016Nokia DN09210645Issue:01C

8 Reboot the FCPU-0 with the new SW image.

Whentheinstallationscriptends,thefollowingchoicesaregiven:
0: reboot node
1: debugging shell
Please select "0" or "1".
Select"0"toreboottheFCPU-0node.
9 Log in to the FCPU as _nokadmin.

Log-inis_nokadminandpasswordissystem.
10 Terminate the TELNET session and return to the LMP terminal.
a) PushCTRL+].
b) TypeQuitafterthepromptchangedto
telnet>
.
Step result
Theuseroperatesfromthe
LMP-1-1-1
.Itisindicatedbytheprompt:
root@LMP-1-1-1
7.2.6 FZC module post-configuration
7.2.6.1 Running post-configuration script after clean installation

Purpose
Thissectiondescribeshowtopost-configurethecontroller.Tocompletecleaninstallation
commissioning,thepost-configurationneedstobeexecutedbytheuserontheFCPU-0.
Post-configurationsynchronizestimeonallthenodes,andunlocksthecluster.The
clusterisnotreadyfornormaloperationuntilthepost-configurationisexecuted.Afterthe
post-configurationiscompleted,thecontrollerSWisstarted,unlocked,andreadyfor
operation.
Procedure
1 Connect to the module's one LMP (LMP-1-1-1) if you do not have connection
already.
# ssh root@192.168.10.51
DN09210645Issue:01C 2016Nokia 181

Passwordis:root.
2 Log in from LMP-1-1-1 to FCPU-0 as _nokfsoperator user.

# ssh _nokfsoperator@FCPU-0
The_nokfsoperatorpasswordwasgiveninsession-specificfsetup.conffile.
3 Run the post-configuration script.

# fsetupcli post configure
g Note: Thepostconfigurescripttakesapproximatelyupto40minutestoaccomplish.
4 Move back to LMP prompt.

# exit
7.2.6.2 Synchronizing LMP flashbanks
This section shows how to synchronize the configuration data located on LMP flashbank
0 and 1
Before you start

YouneedtobeloggedintoFCPU-0as_nokfsoperatorwithrootprivilegesinorderto
performthisprocedure.
Procedure
1 Run # fslmpconf -flashbank-sync all
Step result
INFO Configuring backup flash bank LMP-1-1-1
INFO Backup configuration on lmp OK
182 2016Nokia DN09210645Issue:01C

2 Verify the backup flashbank 1

Sub-steps
a) Log into the LMP
b) Enter the command root@LMP-1-1-1# ls -lsa

/mnt/backupfs/mnt/fastpath/ | grep module
Step result
1 lrwxrwxrwx 1 root root 16 Sep 5 06:38 module ->
/opt/cluster/m<module number>0
c) Verify that m10 is visible in the printout
d) Enter the command root@LMP-1-1-1# cat

/mnt/backupfs/mnt/fastpath2/module/post.soc
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
7.2.7 Verifying controller commissioning after clean installation

Purpose
Thissectiondescribeshowtocheckthecontroller'sstateaftertheapplicationsoftware
installation.
Procedure
1 Connect to the module's one LMP (LMP-1-1-1) if you do not have connection
already.
# ssh root@192.168.10.51
Passwordis:root.
DN09210645Issue:01C 2016Nokia 183

2 Log in to FCPU-0 as _nokadmin user

# ssh _nokadmin@FCPU-0
Password: system

show alarm active-summary
4 List information for a given active alarms.

show alarm active filter-by specific-problem <alarm_id>

show has filter node state managed-object /*
Step result
Statusforallnodesis:
6 Check the recovery groups state.

Usethefollowingcommand:
show has filter rg state managed-object /*
Step result
Statusforalltherecoverygroupsis:
7 Check the SW build status.

Step result
ThestatusoftherunningSWbuildis
BU
.
SW Build status: BU (Active)
184 2016Nokia DN09210645Issue:01C

8 Change SW build status if it is not BU (Active)

set sw-manage app-sw-mgmt change-status current-sw-build-
status NW new-sw-build-status BU
9 Save the running build's configuration.

> save snapshot
10 Make a fallback of the system.

Makesurethatthesystemhasallunitsupandrunningandtherearenocritical
activealarms.
Displayallthecreatedavailablesoftwarepackagesofthesystem:
show sw-manage app-sw-mgmt builds
Inanormaloperation,anactivesoftwarepackageisatBU-state.Fallbackisonly
takenwhensoftwarepackagesareattheBU-state.
Tocreateafullfallbackoftheapplicationsoftware,enter:
save sw-manage app-sw-mgmt fb-build build-name <build_name>
11 Verify that a fallback package exists.

WhenfallbackiscreatedcorrectlyaSWBuildinstatusFBexists.Verifythiswiththe
followingcommand:
Step result
SW Build name: R_QNCB.13.5.5_13.1

SW Build status: FB
7.3 Returning Controller to factory settings

Purpose
Itisrecommendedthatuserreturnstohismodule'sfactorysettingsbeforedoingLMP
pre-configuration.Thisoperation:
showsthemotherboardstatus.
allowstocheckiftheinternalUSBflashisemptysothatanyexistingconfigurationis
notoverwritteninthenextboot-up.
setsLMP'sMGTportIPaddressto10.10.10.10/24
DN09210645Issue:01C 2016Nokia 185

Procedure
1 Log in to module's LMP using serial connection.

Username:root
Password:root
2 Activate LMP pre-configurations with the controller module reset.

# mch_cli Reset BCN
Step result
AsaresultBCNisrebootedoncethefollowingmessageappears:
Stopping services ...
Broadcast message from root (Mon Dec 23 11:40:14 2013):
The system is going down for reboot NOW!
Connection to 10.10.10.10 closed.

[root@fi-sateri01942 mySession]#
3 Verify eth0 port's factory settings.

# ip address show dev eth0
Step result
TheIPaddressofmodule'seth0portis
10.10.10.10
4 Verify factory settings in Network Element ID.

# mch_cli GetNetworkElementId
Step result
ModuleNetworkElementIDisxxxxxxxxxxx.
7.4 Improving FZAP uplink throughput

Performing this procedure is recommended in order to improve uplink throughput in the
FZAPs under a Zone eNB.
Before you start

ThisprocedureassumesthattheoperatorisrunningtheBTSSiteManagerapplication,
andhasaconnectiontotheFlexiZoneControllerwithinaZoneeNB.
186 2016Nokia DN09210645Issue:01C

Procedure
1 Proceed to the Radio Network Configuration page.
2 Select to the LNCEL object of a particular FZAP.

Objectpath:MRBTSLNBTSLNCEL
g Note: EachconfiguredcellisrepresentedbyitsownLNCELobject.
3 Create a new Uplink power control configuration for PUSCH / SRS component
ClicktheNewmenubelowtheobjectlistpanelandselectUplink power
control PUSCH configuration.
4 Set the value of parameter ulpcLowqualSch to 18.

ParameterulpcLowqualSchshouldappearvisibleunderthenameLower SINR
threshold for PUSCH power command decision.Itsdefaultvalueis0.
5 Commit the updated commissioning plan.

Sub-steps
a) Go to the Send Parameters page.
b) Select the Only changes Send option.
c) Click Send Parameters.
Result
SettingLower SINR threshold for PUSCH power command decisiontovalue18

shouldimproveFAZPuplinkthroughputintheCellwheretheparameterwasmodified.
DN09210645Issue:01C 2016Nokia 187

Commissioning FZC

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Commissioning FZC

Caricato da

Copyright:

Formati disponibili

Nokia

LTE Radio Access, Rel. FDD-

Commissioning Flexi Zone

f Important Notice on Product Safety

Changes between issues 01A (2015-09-30, FDD-LTE15A / TD-LTE15A) and 01B

Flexi Zone Controller commissioning workflow

Verifying IPSec tunneling in Flexi Zone Controller

Integrating Flexi Zone Access Points to the Flexi Zone Controller

Additional procedures for FZC commissioning

Improving FZAP uplink throughput

Changes between issues 01 (2015-07-15, FDD-LTE15A / TD-LTE15A) and 01A

Setting up the M-Plane IP address as CMP Server IP addresshasbeenupdatedand

1 Introduction to Flexi Zone Controller

1.1 Flexi Zone Controller commissioning workflow

1 FZC HW installation and verification

2 FZC module software commissioning and network configuration through its

3 Integrating the FZC module to NetAct through the NES3 interface

5 Integrating the FZC module to NetAct through the NWI3 interface

SCLI/FEWS ConfiguringFZC Failed FZC

2 Commissioning Flexi Zone Controller through

2.1 Setting up a Field Engineering Workstation

2.1.1 FEWS Hardware Requirements

2.1.2 Logging into field engineering workstation

1 Log in to the FEWS remotely as the root user.

2 Log in to the FEWS locally as the root user.

2.1.3 Configuring FEWS services

1 Open the FEWS terminal.

2 Disable Linux Security Modules (SELinux).

3 Set up tftpboot and xinetd services.

4 Disable DNS server resolution.

5 Permit all devices to access the FEWS.

6 Ensure that no hosts are denied.

7 Configure exports file.

8 Check FEWS services.

9 Configure services' autostart.

2.2 Configuring a factory pre-commissioned FZC

Commissioning procedure overview

2.2.1.1 Configuration preconditions

2.2.1.2 Configuration overview

The main steps in configuring the factory-commissioned controller are:

2.2.2 Verifying HW installation

Before you start

Installation Site Requirements for BCN Hardware

1 Inspect the BCN module grounding.

2 Inspect the cabling.

Flexi Zone Controller Hardware Installation Quick Guide

3 Inspect the interchangeability versions of the BCN modules.

4 Inspect the AMC hard disks.

5 Inspect the location of fans and the air filter.

6 Inspect the power supply.

7 Inspect the site.

8 Power on the controller modules.

2.2.3 Verifying factory settings

2.2.3.1 Connecting FEWS to the controller

1 Connect the Ethernet cable.

2 Configure Ethernet port IP address of the FEWS.

3 Activate FEWS Ethernet link.

4 Verify the Ethernet link status and settings.

2.2.3.2 Checking factory settings

2.2.4 Verifying the Flexi Zone Controller ID format

Before you start

1 Enter the command show config filter

2 Verify that the fsLogicalNetworkElemId parameter shown in the printout

a) If the parameter includes characters other than letters and numbers,

SCLI/FEWS ConfiguringFZC Failed FZC