10.2.2.7. Loading new Loadware on a HG 3575 
For the load concept via HTTPS for HG 3575 and HG 3500 please refer
to “Gateways HG 3500 and HG 3575“, Chapter 5, “Load Concept for Gateway Boards”.
The loadware for a HG 3575 is very extensive. If, while the module
is being loaded, it is determined that the loadware in the flash memory
of the module does not match the loadware stored in the hard disk of
the OpenScape 4000 central system, the loadware is reloaded on the HG
3575.
The loadware is transferred via FTP-Push (load functionality via hhtps
hasn’t been used, i.e. loading via LW Update Manager), with the HG
3575 downloading the loadware from the FTP server of the HiPath 4000
central processor (in the RMX system).
The FTP server can only transfer loadware to up to five HG 3575 boards
at a time. If there are multiple HG 3575s in the system (up to 83 access
points are possible), the other modules wait their turn in case of a
system reload. This takes quite a long time and considerably slows down
startup of the system.
IMPORTANT:
With the feature “AP Multicast Loading” the
downtime of a system in case of a system update (system relaod with software/loadware
version) will be reduced. For details please refer to Section 2.2.8,
“Updating Access Point Loadware during an RMX Upgrade (New Fix Release/Minor Release)”.
It is therefore possible for a HG 3575 to download new loadware from
the FTP server in the background, which means while the system is running.
Therefore the loadware update manager of the HiPath 4000 should be used
(see „Gateways HG 3500 and HG 3575“, Section 5.5,
“Updating Loadware with "LW Update Manager"”).
Alternative the loadware can be transferred via FTP-Push while the
system is running, without executing it immediately. Actions of this
type should be performed at off-peak times, as the loadware transfer
reduces the bandwidth for signaling messages. The load operation can
also be performed with signaling survivability. The effect on the available
bandwidth is particularly critical in this case.
 |
Configuration Management > System Data
> IPDA > IPDA Access Point
Click Search and select
the access point.
Click Execute on the Action pull-down
menu and select the mode of action Background Loading of NCUI LW Files,
select LW under Files to be Loaded and confirm with OK.
|
 |
EXEC-USSU:MODE=NCUILOAD,LTU=xx,FILES=LW;If
the LTU number is not specified, all HG 3575s that are ready
(READY)
at this time are loaded. |
SIU files can also be loaded in this way.
FILE= |
||
SIUTONES |
TONES |
|
SIURECV |
SIU-RECEIVERS |
|
SIUANN |
SIU-ANNOUNCEMENTS |
|
SIUMOH |
SIU -MUSIC ON HOLD |
|
SIUTDS |
SIU -TDS |
|
LW |
LW file -- NCUI |
|
ALLSIU |
All possible SIUs |
|
|
ALL
|
All loadable files
|
To apply the loadware while the system is active, the following actions
are required:
|
|
Configuration Management > System Data
> IPDA > IPDA Access Point
Click Search and select
the access point.
Click Deactivate on the Action
pull-down menu.
Once the system has confirmed deactivation of
the AP, reactivate it with Activate.
|
|
|
DEACTIVATE-USSU:LTG=1,LTU=xx; ACTIVATE-USSU:UNIT=LTG,LTG=1,LTU=xx; |
IMPORTANT:
Connections are cleared down without further
warning!
Changing the music on hold (MOH) in the system (AMO ZAND:MELODY=X)
When changing the MELODY setting, the following command sequence must
be executed (for each AP) so that the changes become effective immediately:
|
|
Configuration Management > System Data
> IPDA
> IPDA Access Point
Click Search
and select the access point.
Click Deactivate on the Action
pull-down menu.
Once the system has confirmed deactivation of
the AP,
reactivate it with Activate.
|
|
|
DEACTIVATE-USSU:LTG=1,LTU=xx; ACTIVATE-USSU:UNIT=LTG,LTG=1,LTU=xx; |