Typical Om Bootp Packet Files; Reference Specifications - Motorola OM 2000 Installation & Operation Manual

APPENDIX C — INITIALIZATION INFORMATION

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
OM2000.fof
OM2000.cod
OM2000.ini
Fec_fpga_v01.rbf
OMem.jar
OM2000.HST
OM2000.SVC
OM2000.GTW
OM2000.HTM

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.
59
Purpose
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.
Host application code for main OM processor
Contains OM configuration settings for application firmware
Field programming gate array personality file for FEC FPGA
Executable OM-EM Java based application
Example Hosts File
Example Services File
Example Gateways File
HTML File used by internal HTTP Server