User's Manual

nano3G AP Installation Manual Configuration File Preparation
N3G_INST_300 v292_1.0 for N3G_2.92 © ip.access Limited 2012 Page 45
4 Configuration File Preparation
The attribute values for configuring a nano3G AP can be stored in an XML file, and then
loaded via the NOS Client to provision the AP. This configuration 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 configuration files of attributes for
provisioning nano3G APs. This can be done in combination with the Create Site Wizard and
configuration adjustments from the NOS Client, according to whichever method is best
suited for given configuration tasks.
4.1 Overview of Configuration Files
A configuration file is an XML file containing an AP object that has named attributes and the
value for each attribute. Each attribute definition is of the form:
<cd:attribute registeredAs="NUM" name="NAME">VALUE</cd:attribute>
Where:
• NUM is the Registered As number, as specified in the MIB for this attribute
• NAME is the attribute name, as specified in the MIB for this attribute
• VALUE is the attribute value, which must conform to the attribute’s definition in the
MIB
The attribute types and values they may take are formally described in [REF_110].
Note: In the configuration file, the values of compound attributes, such as RAB types, are defined
within brackets (). In the NOS Client, the compound types are the complex attributes that
have multiple levels within the Navigation and Properties panes. To work with compound
attributes in a configuration file, it is recommended to use the structure in the OMC-R Client
as a guide to editing the compound attribute.
Note: In [REF_110], there is a distinction between expert and non-expert attributes. As a general
rule, it is recommended to leave expert attributes at their default values.
The configuration file must contain the correct distinguished name (DN) for the target AP.
The NOS Client will not load a file if the DN does not match. In the configuration file, the DN
is the localDn field near the beginning of the file. To change which AP this file applies to,
edit the last part of the DN which defines the connection instance (the site) and AP
instance.
Although a configuration file can be created from scratch, it is more practical to save a file
from within the NOS Client from an object of the same type and then edit the file for the
target object. The resulting configuration file can then be imported against the target object,
which in this case will be an AP.
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 configuration 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 file has been created, it must be saved for each AP, with the
correct DN.