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

SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects
Aastra depl-1624/1.0 Page: 190 (241)
9.11.4 Specific Commands – Troubleshooting
The OMM software has been installed but does not work automatically when the PC starts.
The command below stops or starts OMM manually (User root):
/etc/init.d/sip-dect [start|stop|restart].
The command line interface for OMM is accessible via telnet on port 8107.
Malfunction
To check whether OMM is working, see the list of procedures for the “SIP-DECT” process. If
OMM does not start, delete the lock file “/var/lock/subsys/SIP-DECT”.
To delete the OMM configuration remove the OMM configuration file “/opt/SIP-
DECT/tmp/omm_conf.txt” (by default).
9.11.5 Upgrade from OMM Version 2.x to 3.x in Host Mode
To update a OMM system from version 2.x to 3.x, you must delete the old OMM software
package rpm –e omm_ffsip-OMM omm_ffsip-HANDSET and install the SIP-
DECT_<version>.bin software.
In this case the installation routine copies automatically the OMM database.
If there are changes in start parameters you can copy the old saved config file from
/etc/sysconfig/omm_ffsip.rpmsave to /etc/sysconfig/SIP-DECT.
9.12 Updating the OMM
To prevent a full breakdown of the DECT network for large systems during an update, a new
mechanism has been introduced.
The procedures for updating an existing DECT installation with a new software depend on
•
is a single OMM or standby OMM installation used and
•
is the OMM running on an RFP or PC.
The OMM “standby” feature is described in section 9.13.
Especially for installations using a standby OMM this new update mechanism allows an
update of the RFPs with a minimum impact to the DECT services.
All RFPs check the availability of new boot image file automatically when:
•
the DHCP lease is refreshed,
•
the RFP lost the connection to the OMM,
•
one of the service applications running on the RFP must be restarted, and
•
an RFP configuration file update check is done (see chapter 9.8).
As soon as an RFP detects a new boot image file on the TFTP server it notifies this to the
OMM. The OMM keeps track when it is save to restart an RFP in order to leave the DECT
service synchronal.
RFPs scheduled for restart are marked with a yellow sign within the Web service (see
chapter 7.6.1) or in a separate column within the OM Management Portal (OMP), see
chapter 8.7.1.1.