Dhcp offer, Retries, Tftp client – AASTRA SIP-DECT (Release 2.1)- OM System Manual - Installation, Administration and Maintenance EN User Manual

Page 129: Booter update, 2 dhcp offer 7.5.3.1.3 retries 7.5.3.2, 2 tftp client, 3 booter update

Advertising
background image

SIP – DECT OM System Manual Release 2.1

7 Configuration und Administration Aspects

depl-1230/1.3

Page: 129 (196)

7.5.3.1.2 DHCP Offer

The DHCP client selects the DHCP server according to the following rules:

The public options (code 224) has a value equal to the string “OpenMobility”,
or

the file field in the DHCP message has a sub string equal to “ip_rfp.cnt”.

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 “iprfp.bin” 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.

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.

7.5.3.3 Booter Update

Each application SW comes with the latest released booter SW. The application SW will
update the booter automatically.

Please note:

After an upgrade from an older OpenMobility Release (< 2.0) to an
OpenMobility Release 2.x the booter of the RFPs will be updated to Version
3.4.x. The OpenMobility Configurator 2.x is required to configure RFPs with
this new booter version. If you downgrade the RFP to an older release, the
booter will not downgrade automatically.

Advertising