User's Manual
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 Installation Overview and Requirements
N3G_INST_300 v292_1.0 for N3G_2.92 © ip.access Limited 2012 Page 19
2.2.11 Other Items for Commissioning
The items in this section can only be used if the commissioning terminal is running a web
server that provides a path to any ip.access AP software download packages. That is, the
required .sdp files must be present on the commissioning terminal.
Setting up a web server for this purpose on the commissioning terminal is outside the scope
of this manual.
Software Image
If there is a requirement to update the AP’s software during commissioning, the relevant
.sdp file must be present on the commissioning terminal.
ATAS File
If there is a requirement to update the trust anchors in the AP during commissioning, the
relevant .sdp file containing the ATAS package must be present on the commissioning
terminal, ready to be downloaded to the AP. The ATAS package contains augmenting trust
anchors which allow an AP to trust specific security gateways.
This will be necessary where the security gateway certificates are not supplied by ip.access
Limited, to ensure the ATAS package is correct for the security gateway terminating IPsec.
The .sdp file containing the ATAS package must be created for the specific security
gateways used in each implementation of the nano3G System. This must be done in
consultancy with ip.access Limited prior to system deployment.