T Y P I C A L O M B O O T P P A C K E T F I L E; R E F E R E N C E S P E C I Fi C A T I O N - Motorola OM 2000 Installation & Operation Manual

A P P E N D I X C — I N I T I A L I Z AT I O N I N F O R M AT I O N
Typical OM BOOTP Packet Files
The BOOTP packet file mix is not fixed, as files are added/removed consistent with
OM functionality enhancements. A typical list of files is as follows:
F i l e n a m e Purpose
O M Z O O O . f o f
File of files that contains three field columns: source path, destination
path, and force flag.
Do not change the symbolic name of the OM in the second field, as It
can cause an initialization failure.
O M 2 0 0 0 . c o d Host application code for main OM processor
O M 2 0 0 0 . i n i Contains OM configuration settings for application firmware
Fec_fpga_v01.rbf
Field programming gate array personality file for FEC FPGA
O M e m . j a r
Executable OM-EM Java based application
O M 2 0 0 0 . H S T Example Hosts File
O M 2 0 0 0 . S V C
Example Services File
O M 2 0 0 0 . G T W
Example Gateways File
O M 2 0 0 0 . H T M
HTML File used by internal HTTP Server
Reference Specifications
To support 1 h 1P and BOOTP the OM conforms to the following RFC specifications:
• BOOTP Vendor Extensions, RFC 2132
• Bootstrap Protocol, RFC 951
• TheTFTP Protocol, Revision 2, RFC 1350
• Clarifications and Extensions for the Bootstrap Protocol, RFC 1542
Refer to these specifications for complete information on the BOOTP packet format
and field descriptions.
5 9