Table of Contents
Advertisement
Installation, Administration and Maintenance
3.1.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 netmask 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.
• 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.
3.1.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 (OMC).
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.
3.1.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.
3.1.4
Application
After successfully downloading and starting the application the RFP will
determine the IP address of the OMM from DHCP.
The DHCP client is capable of receiving broadcast and unicast DHCP
replies. Therefore the flags field is 0x0000.
The DHCP request contains the well-known magic cookie (0x63825363)
and the end option (0xFF).
Aastra
depl-0900/0.4
Page: 22 (104)
Advertisement
Table of Contents
