Table of Contents
Advertisement
APPENDIX C — INITIALIZATION INFORMATION
a downloaded FOF and the OM local copy are the sanne and a force download flag
does not exist In that FOF, the OM does not download any additional files. It
continues booting using the values stored in non-volatile memory.
An FOF and other downloaded files are transferred through Trivial File Transfer
Protocol (TFTP).
Initialization is complete when the OM finishes loading the executable software and
operating parameters, either from a new download or from memory.
The OM is configured to perform a BOOTP request (factory default).
BOOTP Request and Reply Format
BOOTP request and reply messages use the same packet format. The BOOTP
packet includes multiple fields divided into the following areas:
Standard Area Contains fields for specifying basic BOOTP message information,
including:
• Message type (request or reply)
• MAC address of requesting device
• IP address assignment of requesting device
• Boot file name for the requesting device
• Values for some standard fields must be specified and others
are optional, depending on whether the BOOTP message is a
request or reply
Vendor-Specific Area Contains fields for use as defined by the vendor: for example, to set
values for operating parameters
BOOTP Request
In the BOOTP request, the OM Includes:
• A value indicating that the message is a BOOTP request
• A M A C a d d r e s s
The BOOTP request is transferred using UDR
BOOTP Server Reply
In the BOOTP reply to the OM, the BOOTP server includes:
• A value indicating that the message is a BOOTP reply
• T h e I P a d d r e s s o f t h e b o o t s e r v e r
• The IP address assigned to that OM Ethernet port
• The file-of-files (FOF) name for the OM (OM2000.fof)
• The path for the FOF
• T h e n e t w o r k m a s k
The BOOTP reply is transferred using UDR
58
Advertisement
Table of Contents
