nanoLTE AP Pre-Provisioning and Configuration NANO_INST_43370 101_0.
Notices This document is provided to you by or on behalf of ip.access Ltd ("ip.access"). © ip.access Limited 2016. The documentation and any software described herein and/or provided to you in conjunction with this documentation contain proprietary and confidential information of ip.access and may only be used subject to a license agreement containing restrictions on use and disclosure. They are also protected by copyright, patent rights and other intellectual and industrial property laws.
Revision History Version Change Summary Date Author 101_0.1 First Draft for N4G_1.1 13 Oct 2015 AM4 101_0.2 Add miscellaneous parameter section to network-wide settings, move provisioning overview to a separate section 31 Mar 2016 AM4 101_0.3 Add AP Info template information and update references to other manuals 03 Jun 216 AM4 101_0.
Table of Contents 1 Introduction............................................................................................ 1 1.1 Installation Tasks ............................................................................................... 1 1.1.1 1.1.2 First AP Startup .................................................................................................... 1 Assumptions About the nanoLTE AP ................................................................... 2 1.
3.7 "Per AP" Parameters ....................................................................................... 20 3.8 Other AP Parameters....................................................................................... 22 3.8.1 3.8.2 3.8.3 3.8.4 LTE REM Configuration (Network Listen) .......................................................... 22 3G REM Configuration (Network Listen) ............................................................ 24 Additional Management Server Parameters ...........
7.3 7.3.1 7.3.2 7.3.3 7.3.4 7.3.5 7.3.6 7.4 7.4.1 7.4.2 7.5 7.5.1 7.5.2 7.5.3 7.5.4 7.5.5 Use the Create Site Wizard to Pre-Provision a New AP.................................. 46 Start the Create Site Wizard............................................................................... 46 Select an AP Template....................................................................................... 47 Enter AP Identification Details...........................................................................
1 Introduction The ip.access nanoLTE AP is an indoor Access Point for Enterprise and SOHO applications. Use the step-by-step procedures in this manual to pre-provision a new nanoLTE AP in the NOS so that the AP is ready to provide service after obtaining its configuration from the NOS. This manual only describes how to use the NOS Client to pre-provision a nanoLTE AP in the NOS. This manual provides no information about site installation of AP hardware.
1.1.2 Assumptions About the nanoLTE AP It is assumed that any secure nanoLTE AP (278 variants of the nanoLTE E40 AP) supplied to an operator has already been processed by the Redirection System. Hence the Redirector will already contain the unique OLM Package for the AP, ready for the AP to download on first startup or following a factory reset. The OLM Package contains the parameters that an AP uses to connect to its serving IPsec Security Gateway and NOS.
1.4 1.
2 Pre-Provisioning Overview The objective of the procedures in this manual is to provide a nanoLTE AP with a working configuration, stored in the NOS. That is, to pre-provision the AP in the NOS so that the AP can download the configuration from the NOS and successfully start to provide service. The topics in this section are: • 2.1 End-to-End Provisioning Summary • 2.2 Planning - Determine and Plan Network Policies and AP Parameters • 2.3 Preparation - General System Preparation and Templates • 2.
• 4 AP-Unique Parameters See this section for information about the AP parameters that must be unique to each AP. • 8 How to Implement Policies Also see this section for supplemental information on implementing AP parameter usage according to different policies. For example, see section 8.3 for information about determining an appropriate Periodic Inform Interval across the nanoLTE System. 2.
2.4 Pre-Provisioning nanoLTE APs in the NOS Use any of the following methods for pre-provisioning a nanoLTE AP in the NOS: • Use the Create Site Wizard in the NOS Client • Use the SOAP/XML interface • Use the Bulk Provisioning interface The planning and preparation phases leading up to pre-provisioning are common to all these AP pre-provisioning methods. 2.4.1 Create Site Wizard See 7 AP Provisioning for full details on using the Create Site Wizard in the NOS Client to pre-provision an AP in the NOS. 2.
3 Capturing Network Policies and AP Modes This section summarises the considerations that affect AP provisioning policies. This is inclusive of all parameters from the data fill in the CIQ that are applicable to nanoLTE AP provisioning. The topics in this section are: • 3.1 Parameter Categories • 3.2 Customer Policies • 3.3 AP Naming Policies and Management Identities • 3.4 Network-Wide AP Commissioning Parameters • 3.5 Network-Wide AP Provisioning Parameters • 3.6 Parameters Shared by a Group of APs • 3.
3.1.4 Deployment Mode Parameters These parameters reflect different AP use cases or modes of operation. These use-cases are captured in a specific collection of parameters and associated values. After initial provisioning in the NOS, apply suitable deployment mode templates to the required APs to modify their configuration from the baseline. For example: • AP group - typically for regionalising AP management 3.1.
Network-wide AP commissioning parameters, as delivered to all APs in the DOCP (Default Operator Connection Point) set of parameters: • NTP server address • IPsec configuration • CRL Mirror address • NOS address Mandatory Network-wide identities and network resources, to be set via a network-wide global template, including: • The Operator’s identities MCC/MNC • Timezone • Addresses of shared network resources (NTP Servers, IPSec GW, traffic Selectors, PM Upload Servers, Mirror CRL Server) • Some RAN details
3.3 AP Naming Policies and Management Identities It is important to have a clear policy on how APs are named for management purposes, as this affects not only the display in the NOS Client, but also the names and contents of Performance Management counter files and the contents of the SNMP Traps sent on the NOS Northbound interface. 3.3.1 Site ID and Site Name Display in the NOS Client The Site ID is a numeric identifier for the AP and the Site Name is a textual name.
3.3.2 PM Filenames and Identities in PM Files While 3GPP defines structures for filenames and file contents, it is not prescriptive on exactly how the associated identifiers are used. PM File Names The LTE AP PM file names have the following format: .-.
Identities in PM File Headers While the filename can be configured to provide a unique name related to the AP, the PM File header also includes identity information: • DN Prefix – user-configurable text. By appropriate configuration this can be combined with the Local DN to generate a full DN • Local DN - this attribute is set based on the class type and the object instance ID of the AP object. This is typically “AP#0”.
3.3.3 FM Northbound - AP Information in SNMP Traps By default the SNMP Traps sent on the NOS Northbound interface include the Managed Object Class and Managed Object Instance. The Object Instance is the full Distinguished Name (DN), which provides a unique identifier for the source. However, the operator may prefer to use another identifier. In this case the Northbound SNMP Service on the NOS can be configured to emit additional fields according to the source object class.
3.4 Network-Wide AP Commissioning Parameters The AP needs the following parameters to reach the NOS so that the AP can be provisioned: Parameter Description Comment Device.Time.X_000295_Default Default NTP Server address NTPServer Supplied to each AP in the DOCP. Device.IPsec.X_000295_Defaul IPsec Enable tIPsecEnable Supplied to each AP in the DOCP. Device.IPsec.X_000295_Defaul AP Tunnel IP Address Pool tRemoteTrafficSelectors (IPSec traffic selectors) Supplied to each AP in the DOCP. Device.
3.5 Network-Wide AP Provisioning Parameters In most deployments, all these parameters will be the same for all APs. There are some exceptions which may apply instead to groups of APs, where noted. It is recommended to set these parameters with a network-wide Global Template, as in [INST_43380]. 3.5.1 PLMNId and Timezone Parameter Description Comment Device.Services.FAPService.{i}. One or more PLMN IDs (MCC + Own PLMN that is usually CellConfig.LTE.EPC.PLMNList.{ MNC) available to the operator.
3.5.2 Security Resources Parameter Description Comment Device.Services.FAPService.{i}. secGwServer1. The first FAPControl.LTE.Gateway.SecG SecGW that a nanoLTE AP WServer1 attempts to establish a connection with. This should be the same Security Gateway as the default Security Gateway address supplied in the DOCP. Device.Services.FAPService.{i}. secGwServer2. The second FAPControl.LTE.Gateway.SecG SecGW that a nanoLTE AP WServer2 attempts to establish a connection with.
3.5.4 Management Servers Parameter Description Comment Device.ManagementServer.UR Management Server Address. A L URL specifying the NOS address for TR-069 management connections. That is, for APs to connect to the TR-069 AP Service, which allows the NOS to act as an ACS. Usually there is a single ACS (NOS) per network. This is the same for all APs connecting to the same NOS. Device.FAP.X_000295_DiagMg A list of diagnostic report mt.DiagReporting.{i}. conditions, each with a Diagnostic Server URL.
3.5.5 Network Wide Policies Parameter 3.5.6 Description Comment Device.Services.FAPService.{i}. A list of allowed Ciphering CellConfig.LTE.EPC.AllowedCip Algorithms. By default, all are heringAlgorithmList allowed: EEA0, 128-EEA1 and 128-EEA2. EEA0 means no ciphering. Remove unwanted items according to the network policy. This can be done with a global template. Device.Services.FAPService.{i}. A list of allowed Integrity CellConfig.LTE.EPC.AllowedInt Algorithms.
Parameter Description Recommended Value 10000 FAPService.{i}.CellConfig.L When a nanoLTE TE.RAN.RRCTimers.X_000 AP detects a local (Default is 3000) 295_TRRCReestablishment RL failure it waits for the UE to send RRCReestablishme ntRequest. This parameter defines how long the AP waits for a UE to send this message. 3.6 Comment Increase the time to allow UEs more time to reconnect. Parameters Shared by a Group of APs These parameters can be set with a use case Group Template, as in [INST_43380].
3.7 "Per AP" Parameters All these parameters should be considered on a per AP basis. After analysis, some parameters might be applicable to AP use cases, in which case include them in appropriate use case Group Templates. Parameter Description Comment Device.Services.FAPService.{i}. eNodeB Name; as displayed by AccessMgmt.LTE.HNBName UEs camped on the cell or when performing a manual search for cells on a UE. The default is "ip.access".
Parameter Device.Services.FAPService.{i}. CellConfig.Downlink EARFCNLTE.RAN.RF.EARFCN DL Description Comment Typically selected per AP, from DownLink EARFCN. This can be a comma separated a pool set aside for small cell list of candidate UL frequencies. usage. However, as the nanoLTE AP does not yet support self configuration, only the first entry will be used. Device.Services.FAPService.{i}. Band indicator - the frequency CellConfig.LTE.RAN.RF.FreqBa band the AP uses.
Parameter Description Comment Device.Services.FAPService.{i}. Uplink Bandwidth in resource CellConfig.LTE.RAN.RF.ULBan blocks; defaults to 50 (10MHz). dwidth This can be a comma separated list of candidate UL bandwidths. However, as the nanoLTE AP does not yet support self configuration, only the first entry will be used. Modifying the value of this parameter triggers an AP re-boot on termination of the TR-069 session.
MIB/Data Model Name FAPService.{i}.REM.LTE.Scan OnBoot Description Comment Enables or disables Radio Environment Measurement during the FAP start up. This is False by default. FAPService.{i}.REM.LTE.ScanP Enable Periodic Radio eriodically Environment Measurement on LTE EUTRAN bands. False is the recommended setting for enterprise APs. Defaults to True for periodic scans. Change this to False if periodic scans are not required. FAPService.{i}.REM.LTE.
3.8.2 3G REM Configuration (Network Listen) Parameters for Network Listen (NWL) scans of 3G neighbour cells. If all nanoLTE APs should have the same NWL configuration, include these parameters in the network-wide Global Template. Note: “Radio Environment Measurement” (REM) is the LTE standards terminology for Network Listen (NWL). MIB/Data Model Name Description Comment FAPService.{i}.REM.UMTS.WC AP REM behaviour with respect Immediate causes the AP to DMA.
MIB/Data Model Name Description Comment FAPService.{i}.REM.UMTS.WC Comma-separated list. Each DMA.UARFCNDLList entry is a 3G UARFCN in the DL direction to measure. If empty, then no specific 3G ARFCN is provided, meaning that the AP scans all ARFCNs that it is aware of. 3.8.3 Leave empty to scan all UARFCNs. However, it is recommended to specify frequencies to scan, as this will reduce scan time. If DL ARFCNs are specified on a network-wide basis, set this with a template, as in [INST_43380].
3.8.4 AP Groups MIB/Data Model Name Associated Group (associatedGroup) - set in the AP’s parent AP Info object Description Comment Refers to the group object (if any) representing the group to which the AP belongs. nanoLTE AP Pre-Provisioning and Configuration NANO_INST_43370 v101_0.4 for N4G_1.1 © ip.access Limited 2016 If used, the group name becomes part of the file name for file uploads, which allows grouping (for example) of PM files. This is optional.
4 AP-Unique Parameters The previous section deals with all of those parameters that are in some way shared and, thus, may be used to populate one or more templates. There remains a small set of parameters that must be uniquely configured on a per-AP basis. The topics in this section are: • 4.1 Parameters for AP Identification • 4.2 Network Names • 4.3 AP Location 4.1 Parameters for AP Identification Align the attributes and parameters in the following table with the naming policy. See section 3.
MIB/Data Model Name Description Device.Services.FAPService.{ This attribute defines the DN i}.DNPrefix (Distinguished Name) prefix that is included in PM reports generated by the AP in order to uniquely identify the object generating the report. Hence this allows generation of the full Distinguished Name of the reporting AP, which only knows the local part. 4.2 Comment This is configured automatically during provisioning to ensure that PM reports delivered to the NOS are associated with the AP.
4.3 AP Location MIB/Data Model Name Description LTEApInfo-> LTEAPInfoPackage> provisionedLatitude Required for static Defines the AP's expected Latitude. The value of this attribute is specified at neighbour planning. site creation time and may only be updated by a Change Location action. LTEApInfo-> LTEAPInfoPackage> provisionedLongitude Defines the AP's expected Longitude. Required for static The value of this attribute is specified at neighbour planning.
5 System Preparation for nanoLTE AP Provisioning This section describes how to setup MME Pools, AP SW Version and AP Product Class objects, ready for use during AP provisioning. Also ensure that, if used, any ACME Security Gateway objects are correctly configured. For a new system installation, also ensure that the LTE APs object exists, as all nanoLTE APs must be provisioned under this object.
5.2 MME Pools There must be at least one MME Pool with at least one MME. If they have not yet been created, create them before using the LTE AP Create Site Wizard. 5.2.1 Create an MME Pool 1) Right-click the Root > MME Pools object and select Create > Child Object, then click Next twice to get to the Set Mandatory Attributes page. 2) Optionally change the Object Name to allow easy identification of the MME Pool referenced by this MME Pool object.
5.3 Product Class and AP Software Version Objects To assist with provisioning and software updates for APs, the NOS has Product Class and AP Software Version objects. A Product Class defines an AP product in terms of an AP object class and an associated AP Software Version object. The associated AP Software Version object sets the minimum software version for any AP assigned to that Product Class.
The file name contains the following information: The software code that corresponds to the target hardware platform, which will be one of: • 251 for the nanoLTE E40 AP (hardware code 248) • 279 for the nanoLTE E40 AP with secure boot enabled (hardware code 278) Note: The hardware code appears on the information label on each nanoLTE AP.
5.4 Copy AP Software onto the NOS Server This procedure needs to be executed once for each AP software file that is required for the APs: 1) Use a graphical SCP client (such as WinSCP) to log in as user oamnorth on the NOS server hosting the Software Download Service. Alternatively, login directly to the NOS as oamnorth and use the scp command to pull the file into the directory.
5.5 Create an AP SW Version Object This is only required if there is no suitable AP SW Version object. 1) Under the NOS object, right-click the AP SW Versions object and select Create > Child Object. 2) Only one type of AP SW Version object can be created, so click Next. Note: 3) If a Template has been created for any AP SW Version object, a Template Selection screen will appear. If it is not necessary to use a template, click Next without selecting any template names.
5.6 Create an AP Product Class This is only required if there is no suitable Product Class. 1) Under the NOS object, right-click the Product Classes object and select Create > Child Object. 2) Only one type of Product Class object can be created, so click Next. Note: 3) If a Template has been created for any Product Class object, a Template Selection screen will appear. If it is not necessary to use a template, click Next without selecting any template names.
5.7 Check the LTE APs Object Only one LTE APs object is required, which must be created before provisioning the first nanoLTE AP. For a new system installation, verify that this object exists and, if needed, create the object. 5.7.1 Verify the LTE APs Object Exists 1) To check if the LTE APs object already exists, look for it under the Root > APs object. If it is present, no further action is required in this respect.
3) Click the Select button for Default Associated TR-069 AP Service. 4) In the Select the linked object box, drill down to the TR-069 AP Service and select it: 5) Click OK and the Value for Default Associated TR-069 AP Service will show the DN (Distinguished Name) of the TR-069 AP Service. 6) Click the Select button for Default Security Gateway.
5.8 Check the APs Object Ensure the APs object is configured according to the required naming policy. See section 3.3 for information about naming policies. 5.8.1 Automate the Job IDs This is only necessary if changes are required to the way that Job IDs are automatically generated for APs. By default, Generate AP Job ID is false (unchecked) and Append Equipment ID to Job ID is true (checked). 5.8.2 1) Select the Root > APs object. 2) Select the Job ID Construction Package.
5.9 Create AP Groups This is optional. Create AP Groups if the groups must be used for one or both of the following purposes: • AP management by Group - if this is enabled, it is recommended to associate an AP Info object template with each Product Class (see [INST_43380]) to ensure all APs will be pre-provisioned with a Group • Group identity in uploaded PM file names 5.9.1 Create a Group 1) In the NOS Client, select the Root > Network Orchestration System > Groups object.
6 Template Preparation Before starting AP Provisioning, create at least one AP Product Class for each AP type and create a set of templates. For templates that will always be used for every AP, associate those templates with the Product Classes, or with the Product Classes where they are applicable. If there are different use-cases for the same Product Class that need different templates then they should not be associated.
6.2 Network Global Template Use the network Global Template to configure shared aspects of AP operation. As a minimum, there should be one template for mandatory settings and one global template for baseline AP configuration.
6.4 AP Info Object Templates The main reason for associating an AP Info template with a Product Class is to automatically associate the APs in that Product Class with a Group. There are two reasons for associating APs with Groups: • PM report identification: Use the Group name to identify groups of APs for PM reporting purposes, where the Group name is used in the names of PM files that APs upload. To enable this, the Generate AP Job ID attribute in the APs object must be set to True (checked).
7 AP Provisioning Ensure the System Preparation activities in section 5 and Template Preparation in section 6 are complete before using the Create Site Wizard to provision an AP. The procedures in this section assume that the AP will connect to the NOS after the procedures are complete. That is, the AP is not powered up and connected to the backhaul until the NOS is ready for the AP. The topics in this section are: • 7.1 About the Create Site Wizard • 7.2 Pre-Provisioning a nanoLTE AP • 7.
7.2 Pre-Provisioning a nanoLTE AP The nanoLTE AP must be pre-provisioned on the NOS Server before it can be brought into service. It is recommended to do this in advance of physical site installation. An AP is pre-provisioned using the Create Site Wizard in the NOS Client. The user account used for these activities in the NOS Client must have Full Access rights to the LTE APs object. Note: 7.2.
7.3 Use the Create Site Wizard to Pre-Provision a New AP Use the Create Site Wizard in the NOS Client to create a site (AP Info) object and child AP object for an AP. The physical AP will be matched to the AP object according to its serial number. The configuration data for the AP object is stored on the AP’s serving NOS Server. When a commissioned AP starts up, it connects to the serving NOS Server and downloads the configuration.
7.3.2 Select an AP Template This is optional as, instead, it is recommended to automatically apply templates by associating them with the Product Class. However, this page can be used to apply one template that embodies, for example, a regional policy or AP operational use case. Alternatively, any number of templates can be applied to the AP on completion of the Create Site Wizard.
7.3.3 Enter AP Identification Details 9) The page for specifying AP identification details will appear: Notice that the Management Server Address and Security Gateway are set automatically according to the TR-069 object selected for invoking the wizard. The Management Server Address may not be changed. 10) Click in the Site ID box and type a numeric ID. This must be unique. As the ID number is entered, the Site Name is set automatically. Note: Do not use the AP’s serial number for the Site ID.
16) Choose the required Tracking Area Code from the drop-down list. 17) Click Next>>. • If there are any errors on this page, the error will be displayed and the wizard will stay on the AP identity details page. For example, the identification details are checked to ensure there are no duplication conflicts with existing APs. Edit the required field(s) to correct the errors then click Next again. • The wizard will go to the next page if there are no errors. 7.3.
7.3.5 Select NTP Servers 21) The page for selecting NTP servers will appear: All four NTP server addresses must be selected, as required by the AP’s NTP algorithm for setting its time and date. The NTP servers may have been automatically selected from either a template associated with the Product Class or a template selected in the Template page of the wizard. Any changes on this page of the wizard will override settings from a template.
7.3.6 Amend the Mandatory AP Parameters 24) The final page of the wizard has a selection of mandatory attributes: Use this page to check the parameters that are not configured in the previous pages of the wizard. Also, if these parameters have been set by a template as recommended, ensure that the parameters are set are correct for this AP. 25) Select Device.Security. on the left. If X_000295_CRLServerBaseUrl is not set from a template, enter the correct URL now. 26) Select Device.IPsec. on the left.
31) Click Finish. The site (AP Info object) and the AP object will be added under the LTE APs object and can now be selected for further actions. Note: 7.4 Any AP filter results in the NOS Client are cleared so that the new AP Info and AP object can be seen. Apply Templates and Configuration Files to the AP This is optional.
7.4.2 Load a Configuration File for the AP For information on preparing a configuration file for an AP, see [OPM_43005]. 1) If the AP is not currently visible, use AP filtering to make the required AP visible in the object tree in the Explorer Pane. Note: For details on using AP filtering, see [OPM_43005]. 2) To start the NOS Load Attributes Wizard, right-click on the AP object in the NOS Client and then select Load Attributes From File.
7.5 Update the Individual AP Parameters These are AP object parameters and AP Info object attributes that are either unique per AP or must be selected on a per AP basis (for example, the Physical Cell ID may not be unique, but it depends on the AP’s location). Either update the AP with these settings immediately after completing any other provisioning activities, or apply them once the AP is installed on site and is able to connect to the NOS. Note: 7.5.
7.5.2 RF Parameters 1) Select the AP object. 2) Select FAPService.{i}.CellConfig.LTE.RAN.RF.. 3) Ensure the following parameters are set correctly for this AP: • EARFCNDL • EARFCNUL • FreqBandIndicator • DLBandwidth • ULBandwidth • ReferenceSignalPower • PhyCellID • X_000295_PHICHResource 4) 7.5.3 7.5.4 Click Commit to DB to save the parameters in the NOS database. The AP will pick up the updated configuration when it connects to the NOS for the first time.
7.5.5 Save any Parameter Updates 11) 7.6 If any parameter values have changed, click Commit to DB. The AP configuration held in the NOS database is updated. The AP will pick up the updated configuration when it connects to the NOS for the first time. Assign Planned (Static) Neighbours Configure an enterprise nanoLTE E40 AP with planned "static" neighbours by using the Neighbour List Wizard. Do this when the AP’s deployment location is known.
8 How to Implement Policies The sections above describe a suggested set of mandatory parameters and templates to be considered for AP provisioning. There are other patterns of behaviour that could usefully be defined in templates for application to selected APs, but these are not usually fundamental to deployment in the way the parameter groups above are.
8.2 Optional Network Listen Policies Use Network Listen (NWL) to detect an AP’s neighbour lists and calibrate its master frequency to the surrounding macro network. Use these policies to determine Network Listen operates. It is recommended to embody these policies in a template, as in [INST_43380]. For more information about Network Listen see [GST_43415]. 8.2.1 Configure Network Listen Schedule For example, to configure a weekly update in quiet hours: • Set Device.Services.FAPService.{i}.REM.LTE.
8.3 Periodic Inform Interval The following tables summarise the recommended minimum and recommended values for setting the Periodic Inform Interval for Enterprise and SOHO APs. These values assume a population of consisting only of the specified AP type. If a mixed population is in use then calculate a pro-rata value. These initial recommendations are based on typical estimated behaviour.
8.4 PM Reporting PM reporting is enabled by default, with a default upload interval of 86400 seconds (daily) at a random time selected by the AP (thus avoiding peaks in server load/bandwidth). It is recommended to embody these policies in a template, as in [INST_43380]. A destination for PM report uploads must be entered in: • Device.FAP.PerfMgmt.Config.{i}.URL Adjust the upload interval in: • Device.FAP.PerfMgmt.Config.{i}.PeriodicUploadInterval Configure the reporting time in: • Device.FAP.PerfMgmt.
8.6 Diagnostics Settings 8.6.1 Diagnostics Reporting Including parameters from the list below in one or more Templates allows useful collections of diagnostics setting to be turned on or off!. • Device.FAP.X_000295_DiagMgmt.DiagReporting.{i} Each item in this list has a ReportOn condition and a URL for uploading a diagnostics file • Device.FAP.X_000295_DiagMgmt.PeriodicUploadInterval To allow post-analysis of AP software issues it is recommended that “Report on Crash” is configured in ReportOn.
8.7 Mobility Parameter Optimisation The sections below list the parameter groups used for tuning of handover and reselection behaviour. Contact ip.access Professional Services for further guidance. 8.7.1 Handover Control Use the parameters in the following "packages" to control handover behaviour: • FAPService.{i}.CellConfig.LTE.RAN.Mobility.ConnMode. • FAPService.{i}.CellConfig.LTE.RAN.Mobility.ConnMode.EUTRA. • FAPService.{i}.CellConfig.LTE.RAN.Mobility.ConnMode.Irat.
9 Installation Checks All the activities in this section are managed from the NOS Client. Use the procedures in this section to ensure the AP is correctly configured. For troubleshooting information, see [TRB_43005]. The activities in this section assume that the AP has now been powered up and connected to the backhaul. The topics in this section are: • 9.1 Check and Upgrade the nanoLTE AP Software Image • 9.2 Configuration Audit • 9.3 Ensure the AP is in Service 9.
9.1.2 5) Check the values of the SW Version attribute: 6) If the AP does not have the latest software image, download it to the AP from the NOS Server according to the instructions in section 9.1.2. Download the Latest Software Image from the NOS Server to the AP For instructions about how the software images (SDP files) are uploaded to the NOS Server, see section 5.4. 1) Select Device.DeviceInfo.
9.2 Configuration Audit 9.2.1 Final Attribute Changes and Checks 1) Login to the NOS Client with a user name that has Full Access to the required AP. 2) Use AP filtering to make the required AP visible in the object tree in the Explorer Pane. Note: For details on using AP filtering, see [OPM_43005]. 3) Check any AP-specific configuration changes that may not have already been applied by the Create Site Wizard or loading configuration files.
5) 9.3 When the scan is complete, view the results to verify there is some radio activity. This assumes that the AP is in a location where it can detect neighbouring LTE cells. Ensure the AP is in Service Once the AP has the latest software image, any additional configuration is complete and any frequency correction has been applied, it is ready for service. These steps ensure that all configuration changes are correctly applied to the nanoLTE AP.
