User's Guide
Table Of Contents
- nano3G AP Installation Manual
- Table of Contents
- 1 Introduction
- 2 Installation Overview and Requirements
- 2.1 Installation Tasks
- 2.2 Requirements for All nano3G APs
- 2.2.1 General Requirements
- 2.2.2 nano3G AP Cooling
- 2.2.3 Information Required for Pre-Provisioning
- 2.2.4 Parameters for Enterprise Deployments
- 2.2.5 Parameters for Residential Deployments
- 2.2.6 Access Control
- 2.2.7 Closed Access with CSG Parameter Broadcast
- 2.2.8 Closed Access in Legacy Mode
- 2.2.9 Pre-Prepared Configurations - Optional
- 2.2.10 Information Required for Commissioning
- 2.2.11 Other Items for Commissioning
- 2.3 nano3G S8 AP Site Requirements
- 2.4 nano3G S16 AP Site Requirements
- 2.5 nano3G E8 AP and nano3G E16 AP Site Requirements
- 3 Pre-Provisioning a nano3G AP
- 4 Configuration File Preparation
- 5 Commission a nano3G AP
- 6 nano3G AP Hardware Installation
- 7 Finalize Installation
- 8 Troubleshooting
- 9 nano3G AP and PSU Regulatory Information
nano3G AP Installation Manual Finalize Installation
N3G_INST_300 v292_1.0 for N3G_2.92 © ip.access Limited 2012 Page 83
7.2 Finalize Configuration
7.2.1 Final Attribute Changes and Checks
1) Login to the NOS Client with a user name that has Full Access to the required AP.
2) Make any AP-specific configuration changes that have not already been applied by
the Create Site Wizard or loading configuration files. In particular, ensure the static
neighbour lists are correctly configured. See [OPM_300] for information on
neighbour list configuration.
3) Spot check any or all of the following packages to verify the attributes are set to the
correct values:
• Cell Package
•NAS Package
• Location Package
7.2.2 Automatic Stored Configurations
This feature provides storage of a number of previous configurations for a collection of
managed objects and provides a command whereby a user can revert the configuration of
some of the system to a selected stored configuration. Each stored configuration is
identified by:
• The name of the user who made the changes represented by the stored
configuration
• The Date and Time (start and stop timestamps) during which the changes
represented by the stored configuration were made
• A description, generated automatically but which can be edited by the user, which
provides information about how or why this set of changes were made
A stored configuration contains information about what changes need to be made to a
managed object sub-tree in order to return its configuration to what it was at a particular
point in time.
The first time any managed Object is created, there is no configuration stored. Only when
the Managed Object has changes applied will the configuration first store the original
configuration and also the changed configuration. For each Managed Object there isa
maximum number of stored configurations that can be stored. This number can vary
depending on the Managed Object. To find out how many stored configurations a Managed
Object is allowed, look in the Stored Configurations Package Attribute for a specific
Managed Object.
When a stored configuration maximum has been reached the oldest stored configuration
will be deleted to make way for the newly stored configuration of a Managed Object.