Antenna Sharing Hub User’s Guide
@2018 CommScope, Inc All rights reserved
or contact your local CommScope representative or Business Partner for more information
.
7831237 G Page 35 of 38
If the loaded configuration does not have an antenna model in the
‘Files View’ list, then the following message is
displayed.
Figure 29 Message for non-availability of antenna model for loaded configuration from file.
The configuration can be changed and saved to file usi
ng the ‘Save Configuration’ button click.
3.4 Downloading Antenna Sharing Configurations Using Third Party
Controllers
Any AISG2.0/3GPP-compliant BTS/RRH controller can be utilized to send a new antenna model configuration to
the Antenna Sharing Hub. This can be accomplished in two ways:
1. Using
AISG 2.0 software download
. The controller must simply use the .dat binary file, created by the
Antenna Sharing Hub Configuration Tool, as the payload for the software download to any addressed
RET behind the ASH unit. (Note that the commanding operator port must have the Full Access Policy
enforced.) The hub will recognize the command payload as a new configuration, intercept and store the
data, and reboot with the new configuration applied.
2. Using
AISG 2.0 Send Configuration Data
(for SRET) or
AISG 2.0 Antenna Send Configuration Data
(for MRET). Again, the controller will use the .dat file as the payload for the configuration command, and
the command can be addressed to any RET behind the ASH unit. (The commanding operator port can
have Full Access or Restricted Access Policy enforced.) The hub will recognize the command payload as
a new configuration, intercept and store the data, and reboot with the new configuration applied.
After the hub antenna sharing configuration has changed, it is best for all controllers connected to the hub to re-
scan for RETs as RET access may have changed.
