Installation Instructions

© ip.access Ltd
COMPANY CONFIDENTIAL CENG0336_XE_nanoBTS_Installation_and_Test_Manual.doc
- 81 -
displayed may or may not be up to date. These values are fetched from the nanoBTS
as follows:
• When automatic configuration of the nanoBTS is performed, and the non-
volatile attributes configuration phase is enabled, then any non-volatile
attributes that are configured on the nanoBTS are read back. BTS Installer
does this to check that the values set have been correctly stored by the
nanoBTS. Attributes which are not being set are also not read back, so in a
typical automatic configuration run only some of the “NV values in BTS” are
fetched.
• When the manual Set/Get NV Attributes command is run some or all of the
NV values in BTS will be fetched from the nanoBTS, as specified by the user
(see section 6.5.5.4).
The Curren
t values in BTS are only present if these have been fetched from the
nanoBTS, and depending on when they were last fetched from the nanoBTS the
values displayed may or may not be up to date. These values are fetched from the
nanoBTS as follows:
• When the manual Set/Get NV Attributes command is run some or all of the
Current values in BTS will be fetched from the nanoBTS, as specified by the
user (see section 6.5.5.4).
Note that only the Desired values of attributes a
re ever read from or stored to
configuration files. The NV values in BTS and Current values in BTS are never
present in configuration files.
For some attributes there is no useful concept of any “current value” in which cases no
current values are shown on the expanded dialog box.
The BTS Configuration Dialog box can be returned to displaying only the Desired
values by selecting the << button.
6.7.3 Identifying a nanoBTS
There is no single nanoBTS parameter that can always be used to uniquely identify a
nanoBTS’ configuration data in the BTS Database, thus the most appropriate
parameter to regard as the “identity” of the nanoBTS will vary depending on what the
user is doing:
• During physical installation of nanoBTS, ie actually screwing them to the wall,
the Location string is likely to be the most useful identifier, and if a
configuration file is prepared in advance it will most likely identify the nanoBTS
by the Location string. At this point the configuration file probably doesn’t
contain a MAC address for the nanoBTS, as this would unnecessarily constrain
the installer to install specific units at specific locations.
• When a nanoBTS is physically installed the installer can make a note of the
MAC address of the nanoBTS installed at each location, and can edit the
configuration file or the BTS Database to add this information for each
nanoBTS. The MAC address now becomes the most useful identifier for a
nanoBTS, as it is the MAC address that the DHCP server component of BTS
Installer uses to work out what data to send to which nanoBTS.
• Once the DHCP process has run, if desired, each nanoBTS will know its IP
address. At this point the IP address becomes the most useful identifier for a