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 Template Preparation
NANO_INST_43370 v101_0.4 for N4G_1.1 © ip.access Limited 2016 Page 43
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).
• AP management by Group:
This overrides the default mechanism of using the AP Collection objects to provide
AP management permissions to users. In this scenario, assigning APs to Groups
is effectively mandatory as any APs that are not in a Group will not be available to
any normal NOS Client users. Hence the most effective way to ensure Group
membership for all APs is to also organise the Product Classes by Group and
associate each Product Class with an AP Info template that points to the correct
Group for that Product Class.
To enable AP management by Group, ensure the Enable Search Filter By User AP
Groups option is checked in the Manage Users dialogue box in the NOS Client.
Once the first AP Info template exists, optionally copy it to create additional templates for
each AP Group.
6.5 Associating Templates with Product Classes
Templates may be associated with a Product Class, and this is recommended for:
• Speeding up AP pre-provisioning
• Ensuring consistent and error free configuration of APs
• Applying planned values for new parameters where an upgrade requires a new
Product Class, instead of staying with default values for any new parameters
In most cases it should only be necessary to associate two or three templates with each
Product Class, but it is possible to associate up to 10 templates with each Product Class.
A template used for a Product Class should only provide the default and/or specific values
that are applicable to all APs of that Product Class. To ensure this, it is strongly
recommended to create templates for Product Classes either from scratch (as in
[INST_43380]) or by copying a prior template that is known to work for a Product Class. To
copy an existing template, use Create > Duplicate then use Morph Template to change
the target object version.
ALERT: Do not create a template for a Product Class from an existing AP object. This will avoid
accidentally including any AP-specific parameters in the template that will cause usage of
the associated Product Class to fail during site creation and upgrades.
Information on creating Product Classes is in the section 5.
6.6 Create the AP Templates
If templates have not yet been created, create them now and associate them with the
Product Classes created during system preparation (section 5.6).
See [INST_43380] for information on creating different types of templates.