Installation Instructions

© ip.access Ltd
COMPANY CONFIDENTIAL CENG0336_XE_nanoBTS_Installation_and_Test_Manual.doc
- 82 -
nanoBTS, as it is the IP address that BTS Installer will use to contact each
nanoBTS for later configuration phases.
In addition, when BTS Installer connects to a BTS via a Primary OML Proxy, BTS
Installer identifies the nanoBTS it wants to talk to by quoting the Unit ID to the proxy,
so in this case it is the Unit ID that is the most useful identifier for the nanoBTS. See
section 6.9 for more information about proxy mode.
BTS Installe
r does not therefore require that any of these parameters have unique
values, as to do so would restrict the usefulness of the tool in some circumstances.
6.7.4 How Defaults Work
You do not need to enter a value for every parameter for every nanoBTS to be
configured; most parameter values can be picked up using BTS Installer’s system for
handling default values.
When BTS Installer wants to know the value of a parameter to apply to a particular
nanoBTS:
• First it will look in the BTS Database entry for that nanoBTS, to see whether a
value has been specified explicitly for that nanoBTS, either in a
[BTS:<location>] section in the configuration file or manually via the user
interface;
• If it doesn’t find an explicit value for that nanoBTS it will look at a special
“default” BTS Database entry, which the user can set in the [Default] section in
the configuration file or via the Defaults button on the user interface
• If the user hasn’t specified a Default value then a built-in default value will be
used.
The built-in default values are mostly things like zero, null strings, “off” or “don’t”. If the
user specifies no parameters at all then BTS Installer will do nothing at all, and thus
will do nothing harmful.
In a typical installation there will be several parameters which will have the same
settings for all nanoBTS, for example the router (default gateway) DHCP parameter.
The user is recommended to set these as default values using the [Default] section in
the configuration file or the Defaults button on the user interface; it will not then be
necessary to specify these values separately for each nanoBTS.
Note however that if you use the Edit button (or some other means) to edit the
configuration for a nanoBTS what you will see in the dialog box is not just the
parameters you have specified explicitly for this nanoBTS but the result of merging
values from all three of the sources above. If you change a default value using the
Defaults button then you will change what you see in the dialog box for those
nanoBTSs that do not have an explicit setting for this parameter.
6.7.5 Enabling Configuration Phases
The various configuration phases can be enabled and disabled separately, and
whether each phase is enabled or disabled is indicated by the various tabs of the BTS
Configuration dialog box, which are grey if the relevant phase is enabled or white if the
relevant phase is disabled.