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 Capturing Network Policies and AP Modes
NANO_INST_43370 v101_0.4 for N4G_1.1 © ip.access Limited 2016 Page 7
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.7 "Per AP" Parameters
• 3.8 Other AP Parameters
3.1 Parameter Categories
3.1.1 Mandatory Network-Wide Parameters
Many of these parameters have no default value, but are common across the whole
network. They are typically identities representing the network and its common resources
(e.g. NTP Servers). When pre-provisioning APs in the NOS, use templates to consistently
apply these parameters to all APs. For example:
• PLMN ID (MCC + MNC) - usually the same across the whole network
3.1.2 Network-Wide Policy Parameters
These are parameters that have a sensible default value, but the default may not match an
operator’s preferred policy. Once selected, the value is common across the network. When
pre-provisioning APs in the NOS, use templates to consistently apply these parameter
changes to all APs. For example:
• Management traffic DSCP marking
3.1.3 Shared Parameters
These are parameters that may have no sensible default value, but the same value is
shared by many or all APs. When pre-provisioning APs in the NOS, use templates to
consistently apply these parameters to all APs. For example:
• PLMN IDs to scan with Network Listen