Mitel Deutschland GmbH 68635RFP36U-01 用户手册
SIP-DECT OM System Manual
226
7.5.3.1.2 DHCP Offer
The DHCP client selects the DHCP server according to the following rules:
The DHCP client selects the DHCP server according to the following rules:
•
The
public option 224 (code 224) has a value equal to the string “OpenMobility”,
or
•
the
public option 224 (code 224) has a value equal to the string “OpenMobilitySIP-DECT”.
If none of the two rules above match, the DHCP offer is ignored.
Information retrieved from the DHCP offer:
•
The IP address to use is taken from the
yiaddr field in the DHCP message.
•
The IP net mask is taken from the
subnet mask option (code 1).
•
The default gateway is taken from the
router option (code 3).
•
The TFTP server IP address is taken from the
siaddr field in the DHCP message and additionally
DHCP option 150, if available.
•
The boot image filename is taken from the
file field in the DHCP message, if this field is empty, the
default filename is used.
7.5.3.1.3 Retries
If the DHCP client does not get an appropriate DHCP offer, a new DHCP request is send after 1 second.
After 3 DHCP requests are sent the DHCP client will sleep for 60 seconds. During this time the booter
will accept a local configuration with the OM Configurator.
If the DHCP client does not get an appropriate DHCP offer, a new DHCP request is send after 1 second.
After 3 DHCP requests are sent the DHCP client will sleep for 60 seconds. During this time the booter
will accept a local configuration with the OM Configurator.
This cycle will repeat every 3 minutes until either
all the required DHCP options are provided or the
system is manually configured using the OM Configurator tool.
7.5.3.2 TFTP Client
The TFTP client will download the application image from the TFTP server. Both TFTP server and the
name of the application image are supplied via the DHCP client. The application image is checksum
protected.
The TFTP client will download the application image from the TFTP server. Both TFTP server and the
name of the application image are supplied via the DHCP client. The application image is checksum
protected.
Downloading the application image via TFTP is mandatory for older 2
nd
generation RFPs only. 3
rd
generation RFPs will load the application image from the internal flash, and (if configured) also download
the application image via TFTP for update.
the application image via TFTP for update.
7.5.3.3 Booter Update
With older second generation RFPs, each application software image comes with the latest released
booter software. The application software will update the booter automatically. With third generation
RFPs, the booter will only be updated if you update the software.
With older second generation RFPs, each application software image comes with the latest released
booter software. The application software will update the booter automatically. With third generation
RFPs, the booter will only be updated if you update the software.
If you downgrade the RFP’s application software image to an older release, the booter will not
downgrade automatically. In addition, if you want to use the OM Configurator tool (see 7.7), the OM
Configurator version must match the booter software version.
downgrade automatically. In addition, if you want to use the OM Configurator tool (see 7.7), the OM
Configurator version must match the booter software version.