User's Manual
Table Of Contents
- nano3G AP Installation Manual
- Table of Contents
- 1 Introduction
- 2 Installation Requirements
- 3 nano3G AP Hardware Installation
- 4 Commission a nano3G AP
- 5 Configuration File Preparation
- 6 Configuring a nano3G AP from the OMC-R
- 7 Troubleshooting
- 8 nano3G AP and PSU Regulatory Information
nano3G AP Installation Manual Configuration File Preparation
N3G_INST_300 v6.3 for N3G_2.0 © ip.access Limited 2010 Page 32
required settings are in the generic template, it may be easier to simply load the template
then use the OMC-R Client for fine tuning the configuration of an individual AP.
The ObjectInstance must be removed from a generic template if the original file was created
by export from the OMC-R Client. If required, a configuration file for a specific AP can
include the ObjectInstance value for that AP. This will ensure the file can only be loaded
against the target AP. However, this must be reproduced exactly or the configuration file will
not load against the target AP. A way around this is to save a configuration file for that AP,
regardless of its configuration state, then copy and paste the ObjectInstance into the file
that has the correct configuration.
Note: All of the attributes can be configured from the OMC-R Client. After initial provisioning from
a configuration file the OMC-R Client can be used to set attributes or the configuration file
can be edited to set more parameters, for example when importing configuration
information from a radio planning system. To obtain a sample file with all the attributes that
can be configured, export a configuration file as described in section 5.2 and inspect its
content.
5.1.1 Attribute Types and Values
The attribute types and values conform to the attribute definitions in the MIB. See
[REF_110] for a full description of each object type, the attributes it may contain and the
valid values that may be assigned to each attribute.
The following attribute types are available, which are also formally described in [REF_110]:
• Base types:
• Integer - a whole number numeric value, often must be within a range of valid
values
tos=0
• Enumeration, or enum - a value name from a pre-defined set of names with
specific values
t300=T300_4000_MSEC
• Boolean - a true or false value
soipHeartbeatEnabled=true
• String - a value enclosed in double-quotes (the double-quote character itself
cannot be part of the value)
mnc="12"
• Compound types that are made of multiple instances of any types:
• Array - a comma delimited set of values of the same type within square
brackets [ ]
ascPersistenceScalingFactors=[6,6,6,6,6,6]
• Structure - a comma delimited set of values within curly brackets { }, and
each value can be of any type
cellBroadcastMessage={50,GSM_DEFAULT,"nano3G"}
• Set - similar to an array, this a comma delimited set of values of the same
type within round brackets ( ), however, each value must be different
rfParamsCandidateList=({1062,437,1})