User's Manual

6–7070-20000340-01 Rev A
CHAPTER 6. BSU AND S UBSCRIBER CONFIGURATION
Storage Location
To be accessed by the Base Station Units and subscriber Indoor Units when they boot,
the configuration files must be specified in the DHCP server’s configuration file and
stored in the default directory (typically, \tftpboot) of the TFTP server. You can save
directly to that directory when creating the configuration files, or save to a different
location and then transfer the files before booting the configured units.
Configuration Template Files
It will often be efficient to create generic configuration files which can be used as
templates when adding new BSUs, WSSs, or subscribers.
You create and save a configuration template the same way you create and save a con-
figuration file, but save it with a descriptive file name rather than a file name linking
it by MAC address to a specific unit. Then, when you want to use the template as the
basis for a new configuration file, you load the template, make any changes necessary,
and save the file using the correct file name for the new unit.
NOTE: Similarly, you can base a new configuration file on an existing configuration
file by loading the existing file, editing it, and saving it using the proper file name
for the new unit.
Downloading Configuration Files
After the configuration files have been created and stored on the TFTP server, the con-
figured devices need to be booted up. (The Base Station Unit must be operational
when a subscriber Indoor Unit is initialized, or the initialization will fail.) The booted
device will then automatically download its configuration from the TFTP server.
Each Base Station Unit and subscriber Indoor Unit stores its configuration in
non-volatile memory. When it reboots, it downloads the latest configuration from
the TFTP server if it is able to, and then makes any changes to its configuration
based on a comparison of the downloaded configuration with the stored configu-
ration. If the device cannot successfully download its configuration from the
TFTP server, it operates with its stored configuration.
Table6-B Suggested Convention for Naming Configuration Files
Configured Entity File Name Format Example
Base Station Unit bsc_<MACaddress>.cfg bsc_00013b0002e4.cfg
(for MAC 00:01:3b:00:02:e4)
Subscriber cpe_<MACaddress>.cfg cpe_00013b00025d.cfg
(for MAC 00:01:3b:00:02:5d)