Operation Manual

SFX SERIES USER’S GUIDE
Rev 2.2 75
The following fields can be edited on the XD Retriever Configuration page:
Edit Field Description
Concurrent Threads Enter the number of threads that Retriever will manage concurrently,default = 3.
Kilobits
Per Second Throttle
Approximate maximum speed over the terrestrial link for receiving files, in kilo bits/second.
Refresh Server IP
Address
Enter, in dotted decimal notation, the IP address of your Host Retriever Service in the XD Host.
Used to backchannel packets via the HTTP link.
Refresh Server Port Enter the port address to listen for the HTTP packets from the Host Retriever Service. Default is
80.
Refresh Rate (sec) Enter the interval, in seconds, between requests to the XD Hosts for missing files.
Adapter Select the adapter to be used for sending missing file requests on the return link to the XD
Host. Options are localhost, Net1(eth0), Net2(eth1). Local host selection will use first found
adapter.
Input Queue Size Enter the maximum size of the missed files list, default = 10,000.
Retry Period If this period is exceeded the XD Client abandons the attempt to retrieve the missing file.
Proxy Server Enter the IP address of the Retriever Proxy Service which is typically located locally and in turn
communicates with the XD Host Retriever Service. Leave Blank if not used.
Proxy Server Port Enter the Port address of the Retriever Proxy Service which is typically located locally and in
turn communicates with the XD Host Retriever Service. Leave blank if not used.
Logging
When the Logging Main Menu Tool Bar item is selected, the Logging page is displayed. The page displays a filtered
list of logged events of interest, relating to receiver operation and fault conditions. Events may be logged either locally
(to the hard drive) or to another network node via remote UDP/IP connection, or to both locations. The receiver
logging facility makes use of the Linux syslogd components, as well as its own custom components.
Five levels of log messages are supported. From lowest to highest priority, these are:
1. Debug Messages,
2. Informational Messages,
3. Warnings,
4. Errors,
5. Critical Errors.
The log can be filtered on these levels so that only messages at a desired priority and above are actually logged. A
time stamp, originator identifier (unit name on the network) and logged message are provided for each event logged.
Logs can be further filtered on specific keywords in the log entries by a custom filter.
Additional details on the logging features can be found in the descriptions for the Edit Fields below. A sample logging
page is shown in Figure 2- 47.