AASTRA SIP-DECT (Release 2.1)- OM System Manual - Installation, Administration and Maintenance EN - Manual (Page 149)

SIP – DECT OM System Manual Release 2.1 7 Configuration und Administration Aspects
depl-1230/1.3 Page: 149 (196)
RFPs scheduled for restart are marked with a yellow sign within the Web service (see
chapter 5.6.1) or in a separate column within the OM Management Portal (OMP), see
chapter 6.7.1.1.
7.10.1 Updating a Single OMM Installation
In case of a single OMM installation, a breakdown of the DECT network during the update
procedure is unavoidable.
Please note: Updating a single OMM installation will cause a breakdown of the DECT
network during the update procedure.
For the update replace the boot image file on the TFTP server(s) with the new one.
OMM in RFP mode
If the OMM is running on an RFP force the update of this RFP by pressing the
Update button
on the System settings web page (see chapter 5.4.1.2). The RFP checks the boot image
file on the TFTP server and reboots if a new one is found.
OMM in host mode (on Linux PC)
If the OMM is running on a dedicated Linux PC, install the new software as described in
section 7.9.2 on that PC with the command “omm_ffsip_install.bin”. This stops
automatically the running OMM and installs the new software. After the installation phase,
restart the OMM by running the command “/etc/init.d/omm_ffsip start”.
As soon as the RFPs lost the connection to the OMM (because of the update), the RFPs
detects that a new image file is on the TFTP server and reboots with the new image file.
7.10.2 Updating a Standby OMM Installation
Please note: Updating a standby OMM installation will cause a switch over between both
OMMs. All active calls will be dropped.
For the update replace the boot image file on the TFTP server(s) with the new one.
OMM in RFP mode
Force the update by pressing the
Update button on the System settings web page (see
chapter 5.4.1.2). The OMM-RFP checks the boot image file on the TFTP server and initiates
an update procedure, if a new image file has been found. The automated update procedure
performs the following steps:
1 Reboot the RFP residing the standby OMM.
2 Reboot the RFP residing the active OMM which causes a failover to the standby OMM.
3 Reboot all other RFPs that are able to find the new boot image file one by one. This is
managed by the new active OMM.
This procedure reduces the downtime of the SIP-DECT system to a minimum due to the
optimized failover.