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

SIP – DECT OM System Manual Release 2.1 7 Configuration und Administration Aspects
depl-1230/1.3 Page: 127 (196)
• The support of RFC 1350 /1/ is mandatory.
• To accelerate the download of a boot image file, it is possible to increase the packet size
of the transmitted TFTP packets from 512 bytes per packet to 1468 bytes per packet. To
use this optional feature, the TFTP server has to support RFC 2347 /3/ and RFC 2348 /4/.
• To reduce the overall download time of the RFPs in a system, it is possible to use TFTP
multicast download. To use this optional feature, the TFTP server has to support RFC
2090 /2/ and RFC 2349 /5/.
To use the TFTP multicast option, the attached network has to support multicast too.
Furthermore a support of IGMP, RFC 2236 /6/ is required.
Note: If many RFPs loading the boot image simultaneously, the network load could
increase significant. To balance the network load or for backup reasons, it is
possible to configure more than one TFTP server in a network.
DHCP server requirements
A DHCP server needs to support RFC 2131 /9/. The TFTP and DHCP server need not to
reside on the same host.
7.5.2 Booting Steps
Booting is performed in two steps:
1 Starting the boot process.
2 Starting the application.
Booter startup
The RFP has only a little standalone application built into the flash. This software realizes the
so called net boot process. On startup each RFP tries to determine its own IP address and
other settings of the IP interface from the configuration settings in the internal flash memory.
If no settings are available or these settings are disabled, the RFP tries to determine these
settings via DHCP. The RFP gets the application image file from the TFTP server.
Application startup
After starting the application image the RFP checks the local network settings in its internal
flash memory once again. If no settings are available or if they are disabled, it starts a DHCP
client to determine the IP address of the OMM and other application startup settings.
Depending on the given settings the following service applications will be started in these
phase: OMM (OpenMobility Manager), SNTP, SNMP.
There is no difference in booting that RFP which is chosen to be running in OMM mode from
those which are in the RFP only mode. The decision is driven by the OMM IP address, which
is read
• within the local network settings, if active;
• via DHCP request;
• RFP configuration file (see 7.7).
The RFP which has the same IP address as the dedicated OMM IP address will be the RFP
which the OMM application runs on.