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 How to Implement Policies
NANO_INST_43370 v101_0.4 for N4G_1.1 © ip.access Limited 2016 Page 61
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. To allow post-analysis connection problems, use “Report on Lost
IPSec” and “Report on Lost Gateway Connection”. The URL is specified separately for each
condition, but can be the same URL in all cases.
Periodic Upload is enabled by configuring “Report on Periodic Timeout” in ReportOn with
an associated interval in PeriodicUploadInterval. Only use this for a small number of APs for
special monitoring purposes.
8.6.2 Diagnostics Tuning
Diagnostics tuning is configured in Device.FAP.X_000295_DiagMgmt.DiagTuning.{i}.,
which is a list that can contain the following parameters in each item:
• Device.FAP.X_000295_DiagMgmt.DiagTuning.{i}.TuningName
• Device.FAP.X_000295_DiagMgmt.DiagTuning.{i}.TuningValue
The DiagTuning parameters TuningName/TuningValue should only be used on a per AP
basis under the guidance of ip.access.