Mitel Deutschland GmbH 68635RFP36U-01 Manuale Utente
SIP-DECT OM System Manual
224
•
To reduce the overall download time of the older 2
nd
generation RFPs in a system, it is possible to use
TFTP multicast download. To use this optional feature, the TFTP server must support RFC 2090 /2/
and RFC 2349 /5/.
and RFC 2349 /5/.
To use the TFTP multicast option, the attached network must support multicast too. Furthermore a
support of IGMP, RFC 2236 /6/ is required.
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.
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.
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.
1 Starting the boot process.
2 Starting the application.
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:
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 3
rd
generation RFP gets the application image from internal flash memory.
•
An older 2
nd
generation RFP only has a small 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
acquires the OMM IP address
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
acquires the OMM IP address
•
within the local network settings, if active
•
via DHCP request
•
RFP configuration file (see 7.7.7)
If the IP address of the actual RFP device matches one of the acquired OMM IP addresses, the RFP
software continues in OMM mode. Otherwise, the RFP runs as normal RFP without OMM mode.
software continues in OMM mode. Otherwise, the RFP runs as normal RFP without OMM mode.
Note: Only 3
rd
generation RFPs are able to run in OMM mode while
older 2
nd
generation RFPs cannot function as OMM.