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 10
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. When
using the NOS Create Site Wizard the NOS automatically generates a Site Name of “Site
<Site ID>”, but this can be changed by the user if desired. The Site ID must be unique. The
NOS enforces uniqueness of the numeric Site ID, but not the Site Name.
• It is recommended that the AP Serial Number is NOT used as a basis for the Site
ID as this could result in confusion if the AP is subsequently swapped. For
example, due to a failure.
• Site ID could be associated with the AP’s on-air Cell-ID, provided the customer is
confident the Cell-ID will not be changed for any reason.
Each AP Info object is labelled with the Site Name, Site ID in square brackets and the
currently provisioned Product Class in the NOS Client:
Note: The Site ID is taken from the AP Info object’s Object Instance ID. In most cases, the NOS
automatically assigns an Object Instance ID to new objects. However, in the case of APs,
this is configurable to allow the use of a meaningful numeric identifier.
Each AP object is labelled with its object name, the instance ID (always [0]) and the
currently provisioned Product Class. The object name is assigned automatically, and is the
display name of the current class of the AP object. Hence this changes automatically when
an AP is upgraded to a different Product Class that is associated with a different AP class.