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

SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects
Aastra depl-1624/1.0 Page: 163 (241)
Booter startup
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.
Depending on the RFP type, the RFP software is to be loaded:
•
A current RFP gets the application image from it’s internal flash memory.
•
An older RFP has only a little standalone application built into the flash. This
software realizes the so called net boot process. The RFP gets the application
image file from the TFTP server.
Application startup
After starting the application image, the RFP software checks the local network settings in its
internal flash memory. If no settings are available or if they are disabled, the RFP software
starts a DHCP client to determine the IP address of the OMM and other application startup
settings. The RFP software aquires the OMM IP address
•
within the local network settings, if active;
•
via DHCP request;
•
RFP configuration file (see 9.8).
If the IP address of the actual RFP device matches one of the aquired OMM IP addresses,
the RFP software continues in OMM mode. Otherwise, the RFP runs as normal RFP without
OMM mode.
Note: With SIP–DECT 3.0, only a current RFP is able to run in OMM mode while older
RFPs cannot function as OMM.
9.5.3 Booter Startup
The SIP–DECT RFP software includes a booter with the following features:
•
VLAN can be configured via the OM Configurator without a static IP configuration. This
means that the first DHCP request will be done by using VLAN.
•
To balance the network load with older RFP devices, up to three TFTP servers can be
configured. This can be done using the OM Configurator (local setting) or using the DHCP
option 150. Before starting the download, the TFTP server will be selected randomly by
the booter. But, if the option “Preferred TFTP server” was set by the OM Configurator, the
option “TFTP server address” will specify the TFTP server to use. No randomly selection
will be done in this case.
•
Older RFPs only: to reduce the number of TFTP packets sent by the TFTP server, the
packet size can be increased. This will be done by using a TFTP option (see 9.5.1 “TFTP
server requirements”).
•
Older RFPs only: Multicast TFTP download is possible if the TFTP server and the
connected network support this.
•
To indicate the actual state of the booter, the LEDs of the RFP will be used (see 9.5.5).