nano3G AP Installation Manual
Configuration File Preparation
N3G_INST_300 v8.1 for N3G_2.0.5 © ip.access Limited 2011
Page 26
4
Configuration File Preparation
The attribute values for configuring a nano3G AP can be stored in a text file, and then
loaded via the OMC-R Client to provision the AP. A text file of attributes can be loaded
when creating the site for the AP or at any time after that once the AP object exists.
This section describes how to prepare one or more text files of attributes for provisioning
nano3G APs. This can be done in combination with configuration adjustments from the
OMC-R Client, according to whichever method is best suited for given configuration tasks.
4.1
Overview of Attribute Configuration Files
An attribute configuration file is a text file containing an object class followed by a list of
attribute names and the value applied to each attribute. The file can also contain comment
lines anywhere that start with the # character. Hence, the file content is of the form:
# some comment about the object type
Object=class_nnn
# some other comment
attribute1=value
attribute2=value
...
attributeN=value
The file must contain the Object type. The OMC-R Client will not load a file that does not
have an Object type defined. For N3G_2.0.5, the Object for a nano3G AP must be
apNano8_020
or
apNano_020
. So in each case the file must start like this:
• For a nano3G S8 AP or nano3G E8 AP:
Object=apNano8_020
• For a nano3G S4 AP:
Object=apNano_020
An attribute configuration file can be created from scratch. More conveniently, a file can be
saved from within the OMC-R Client from an object of the same type and then customized
for a different object of the same class. The resulting configuration file can then be imported
against the target object, which in this case will be an AP. An example file is provided in
section 4.3.
Configuration files must be imported one at a time, but there is no restriction on the number
of configuration files that can be imported to configure any given object. This means it is
possible to create a generic template file, which contains attribute values common to all
APs of the same type. Typically, this can be started by exporting the configuration from an
AP that has already been fully configured, and then edited to remove non-generic
attributes. Once the generic template has been created, optionally create a file for each
individual AP with additional settings particular to each AP. However, if the majority of
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.
