APPENDIX C — INITIALIZATION INFORMATION
59
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:
Filename Purpose
OM2000.fof
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.
OM2000.cod
Host application code for main OM processor
OM2000.ini
Contains OM configuration settings for application firmware
Fec_fpga_v01.rbf
Field programming gate array personality file for FEC FPGA
OMem.jar
Executable OM-EM Java based application
OM2000.HST
Example Hosts File
OM2000.SVC
Example Services File
OM2000.GTW
Example Gateways File
OM2000.HTM
HTML File used by internal HTTP Server
Reference Specifications
To support TFTP and BOOTP the OM conforms to the following RFC specifications:
•
BOOTP Vendor Extensions, RFC 2132
•
Bootstrap Protocol, RFC 951
•
The TFTP 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.