User's Manual
Table Of Contents
- nanoLTE AP Pre-Provisioning and Configuration
- Table of Contents
- 1 Introduction
- 2 Pre-Provisioning Overview
- 3 Capturing Network Policies and AP Modes
- 4 AP-Unique Parameters
- 5 System Preparation for nanoLTE AP Provisioning
- 6 Template Preparation
- 7 AP Provisioning
- 8 How to Implement Policies
- 9 Installation Checks
nanoLTE AP Pre-Provisioning and Configuration Introduction
NANO_INST_43370 v101_0.4 for N4G_1.1 © ip.access Limited 2016 Page 1
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. For
information about installing nanoLTE AP hardware on site, see [INST_43311].
1.1 Installation Tasks
To make a new nanoLTE AP ready to provide service, complete the following tasks:
• System preparation and AP pre-provisioning in the NOS, as described in this
manual - see section 2 for an overview
• Site installation of the AP hardware - see [INST_43311] for nanoLTE AP hardware
installation requirements and procedures
These tasks can be completed in any order. In most cases, however, the most practical
approach is to pre-provision an AP in the NOS before final site installation.
1.1.1 First AP Startup
In summary, assuming that all preparation and installation tasks are complete, the first AP
startup will take place as follows:
• The AP sets its date and time with NTP - this is mandatory for certificate validation
• The AP connects to the Redirector to obtain its unique OLM Package (see the
assumptions in section Assumptions About the nanoLTE AP) - the AP also
contacts a CRL as part of this procedure to validate the Redirector certificate
• The AP uses the DOCP parameters and certificate from the OLM Package (see
section Network-Wide AP Commissioning Parameters for a summary of the DOCP
parameters) to establish an IPsec tunnel with its serving SecGW - the AP also
contacts a CRL as part of this procedure to validate the SecGW certificate
• The AP connects to its serving NOS via the SecGW and performs its first Inform()
procedure to obtain the configuration that is pre-provisioned in the NOS - this may
also trigger a software update from the NOS if the current AP software is older than
the software version associated with the AP’s assigned Product Class (see section
Product Class and AP Software Version Objects)
• The AP uses the downloaded configuration to connect to the core network, bring
up its cell and enter service
Hence this manual is about ensuring that the last two phases of this process take place
successfully. See section Pre-Provisioning Overview for an overview of the activities and
procedures in this manual.
Note: For a more detailed first startup sequence, in case the AP has difficulty connecting to its
serving NOS, see [TRB_43005].