Services File Format - Motorola OM 1000 Installation And Operation Manual

Services File Format

The services file specified in the FOF defines the TCP/UDP ports the OM 1000 uses to
communicate with other devices in the headend LAN.
Within the services file, all lines must be either comment or data lines, and each line must be
terminated with a carriage return or a carriage return plus line feed. Comment lines begin with
a # character in the first position. Data lines define services using three fields separated by any
number of spaces or tabs:
The first field identifies the service name
The second field identifies the port number and protocol name, separated by a slash (/)
The third field identifies any aliases for the service
Figure C-3 provides an example of a services file:
Figure C-3
Sample services file
OM1000 Software Services File
#
# FILE INFO:
# $Workfile: om1000.svc
# $Revision: 1.3.1.0
# $Date: 04 Jun 2002 09:34:44
#
# DESCRIPTION:
# Services file.
#
# This file describes a number of service name to port/protocol
# mappings for the OM-1000. The only place where the OM uses this file
# is to select the "control port" in the NET/CTRL menu, which must be
# the TCP connection between the OM and DAC-6000 (i,e,, the ACC2OM2
# entry shown below).
#
# NOTES:
# This file is read by the OM during initialization. The OM uses a
# local copy of this file unless it cannot find it or is forced to
# download it from the boot server via a "force" command in the
# associated file-of-files.
#
# FORMAT:
# Service Name Port Number/Protocol
#----------------------------------------------------------------------
#ACC to OM TCP Port (control port)
ACC2OM2 5167/tcp
#
#DAC to OM TCP Port (control port)
DAC2OM2 5167/tcp
$
$
$
Initialization Information
OM 1000 Installation and Operation Manual
C-7