WeatherMAX Gateway and Weather Server for Linux

WeatherMAX Gateway and Weather Server for Linux
UNISYS
NOAAPORT Gateway System for Linux
Users Guide
Version 8.0
March 13, 2012
Unisys Weather Information Services
2476 Swedesford Road
Malvern, PA 19355
800-610-9473 Voice
© Copyright 1996-2012 Unisys Corporation. All rights reserved.
The information contained in this document is proprietary to Unisys Corporation.
Unisys NOAAPORT Gateway System for Linux
The information contained in this document is proprietary to Unisys Corporation. Receipt and use of this data are
subject to the restrictions set forth in a proprietary Data Non-Disclosure Agreement. Any use of the data or disclosure
contrary to that agreement is expressly prohibited. NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THE
DOCUMENT. Any product and related material disclosed herein are only furnished pursuant and subject to the terms
and conditions of a duly executed Program Product License or Agreement to purchase or lease equipment. The only
warranties made by Unisys, if any, with respect to the products described in this document are set forth in such
License or Agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of
the information in this document or software material, including direct, indirect, special, or consequential damages.
You should be very careful to assure that the use of this information and/or software material complies with the laws,
rules, and regulations of the jurisdictions with respect to which it is used. The information contained herein is subject
to change without notice. Revisions may be issued to advise of such changes and/or additions.
Unisys™ is a registered trademark of Unisys Corporation.
WeatherMAX ™ is a registered trademark of Unisys Corporation.
Version 8.0
Page 1 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
Table of Contents
1
2
3
4
5
6
7
8
9
Overview ............................................................................................................................................... 4
NOAAPORT Ingest Description ............................................................................................................ 6
2.1
National Weather Service NOAAPORT Broadcast Channels ...................................................... 7
2.2
Unisys Broadcast Channel ............................................................................................................ 7
End Users.............................................................................................................................................. 7
3.1
Unisys Product Manager (WXP) ................................................................................................... 8
3.2
Unidata Local Data Manager (LDM) ............................................................................................. 8
3.3
Unisys Weather Server (GWIP) .................................................................................................... 8
SNMP Monitoring .................................................................................................................................. 9
System Layout..................................................................................................................................... 10
5.1
NOAAPORT System Scripts/Processes ..................................................................................... 10
5.1.1
Scripts ................................................................................................................................. 10
5.1.2
Processes ............................................................................................................................ 11
5.2
Configuration Files ...................................................................................................................... 11
5.3
Log Files ...................................................................................................................................... 12
5.4
License File ................................................................................................................................. 12
Running NOAAPORT .......................................................................................................................... 13
6.1
Automatic Startup ........................................................................................................................ 13
6.2
Manual Startup ............................................................................................................................ 13
6.3
Unisys Channel Data Feed Switch Over ..................................................................................... 13
6.4
Restarting NOAAPORT ............................................................................................................... 14
6.5
Rebooting Computer ................................................................................................................... 14
Monitoring NOAAPORT ...................................................................................................................... 14
7.1
NOAAPORT Status ..................................................................................................................... 15
7.2
NOAAPORT Skyline ................................................................................................................... 17
7.3
Receiver Status ........................................................................................................................... 18
7.4
Log Files ...................................................................................................................................... 19
7.4.1
Status Log ........................................................................................................................... 19
7.4.2
Process Logs ....................................................................................................................... 19
7.4.3
Latency Log ......................................................................................................................... 20
Serving Weather Products to Other Computers ................................................................................. 21
8.1
NFS (Network File System)......................................................................................................... 21
8.2
SMB (Windows File Sharing) ...................................................................................................... 21
Configuring NOAAPORT ..................................................................................................................... 22
9.1
[PARAMS] Section ...................................................................................................................... 22
9.1.1
LOGMASK ........................................................................................................................... 22
9.1.2
NUM_USERS ...................................................................................................................... 22
9.1.3
NOAAPORT_BUF_SIZE ..................................................................................................... 23
9.1.4
NOAAPORT_DATA_STREAM ........................................................................................... 23
9.1.5
SAVE_HDLC_FRAMES ...................................................................................................... 24
9.1.6
MULTICAST_INTERFACE ................................................................................................. 24
9.1.7
UNISYS_MULTICAST_INTERFACE .................................................................................. 24
9.1.8
S300_IP ............................................................................................................................... 24
9.1.9
SNMP_COMMUNITY .......................................................................................................... 25
9.1.10
LATENCY_LOG .................................................................................................................. 25
9.1.11
LANDCOMM_IP_INTERFACE ........................................................................................... 25
9.1.12
LANDCOMM_SOCK_RECV_BUF_SIZE ............................................................................ 25
9.1.13
LANDOMM_PORT_NUM .................................................................................................... 26
9.1.14
LANDCOMM_HEARTBEAT_TIMEOUT ............................................................................. 26
9.1.15
LANDCOMM_CONNECT_TIMEOUT ................................................................................. 26
9.1.16
UNISYS_PRIMARY_COMM ............................................................................................... 26
9.1.17
UNISYS_AUTO_FAILOVER ............................................................................................... 27
9.1.18
UNISYS_THROUGHPUT_THRESHOLD ........................................................................... 27
9.1.19
UNISYS_FILTER_ID ........................................................................................................... 27
Version 8.0
Page 2 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
9.1.20
UNISYS_FILTER_KEY ....................................................................................................... 28
9.2
[USERS] Section ......................................................................................................................... 29
9.2.1
USER_x ............................................................................................................................... 29
9.3
[FILTER] Section ......................................................................................................................... 30
9.3.1
USER_x ............................................................................................................................... 30
10
Sample NOAAPORT Configuration ................................................................................................ 32
11
Troubleshooting .............................................................................................................................. 34
12
Operating System Updates ............................................................................................................. 36
13
Mail Checking .................................................................................................................................. 36
Version 8.0
Page 3 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
1 Overview
The Unisys NOAAPORT Gateway system is a fully integrated, turn-key system that is configurable to
receive the NWS NOAAPORT broadcast data stream, to receive the Unisys Weather data stream
(satellite or landline), or receive both the NOAAPORT and the Unisys Weather data streams through
diverse communication paths. The system is licensed based on the configuration purchased for the
delivery. To shorten the name in this document, the NOAAPORT Gateway will be referred to as
NOAAPORT from this point forward.
The NOAAPORT accepts and processes the complete product set found on the National Weather
Service (NWS) NOAAPORT satellite broadcast service. This includes the GOES, NWSTG, NWSTG2,
and OCONUS broadcast channels. The Unisys NOAAPORT system is also designed to accept and
process the Unisys WeatherMAX data from the Unisys Weather Data Center on the Unisys broadcast
channel. The Unisys broadcast channel is co-located with the NWS NOAAPORT broadcast using the
SES-1 satellite, This allows use of the same satellite dish and its components for both the NOAAPORT
broadcast and the Unisys broadcast. The Unisys channel can also be received via a land line connection
to the Unisys WeatherMAX dissemination server located in Malvern, PA. The Unisys channel provides a
Unisys NOAAPORT channel with commercial weather data to supplement and complete the weather data
offered on the NWS NOAAPORT broadcast.
This system runs on an Intel platform using the Linux operating system (Red Hat or CentOS). It uses
standard TCP/IP and NFS/SMB for data access. The Unisys NOAAPORT system has been tested to to
process data at the planned 30Mbit/sec data stream from the NWS broadcast. The Unisys NOAAPORT
system can save all the data on local disks, provide product arrival notification (PAN) messages, output
the NOAAPORT data as a raw NOAAPORT packet stream, or output the data as familiar WMO bulletins
that can be further processed or displayed by Unisys Product Manager or other user software.
The Unisys NOAAPORT system currently sends the NWS NOAAPORT satellite broadcast data stream
and/or Unisys satellite broadcast data stream to end users over a TCP/IP socket connection in one of
three formats:



WXP (Unisys Weather Processor)
LDM (Unidata Local Data Manager)
GWIP (Unisys Weather Server)
The Unisys NOAAPORT system can support up to 32 end users. Each end user establishes a separate
TCP/IP socket connection to the Unisys NOAAPORT computer. More than one end user has the ability to
receive the same NWS NOAAPORT data stream and/or Unisys broadcast channel. For example, the
NWS NOAAPORT GOES and NWSTG data stream can be sent to a WXP end user and the NWS
NOAAPORT GOES and NWSTG data stream along with the Unisys broadcast channel to an LDM user.
The Unisys NOAAPORT system is SNMP enabled, and has its own publicly registered OID under Unisys
Weather. With SNMP you can monitor common functions like CPU utilization, memory usage, disk space,
and processes.
This document provides a detailed description on the configuration and operation of the Unisys
NOAAPORT computer and satellite receiver(s). Figure 1 is a diagram of a Unisys
NOAAPORT System configured to ingest the NWS NOAAPORT data stream and the Unisys broadcast
channel (both satellite and land line).
Version 8.0
Page 4 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
SES-1
Novra S300
(NWS NOAAPORT
Broadcast Channels)
Unisys NOAAPORT
Gateway
System
NOAAPORT
Display System
NWS NOAAPORT
C-Band Uplink
Unisys Channel
C-Band Uplink
(Malvern, PA)
User C-Band
Antenna
Novra S300
(Unisys Broadcast
Channel)
NOAAPORT
Display System
Uplink Control
Internet
Unisys Broadcast Channel
(Satellite)
Unisys Broadcast Channel
(TCP/IP Land Line)
NOAAPORT
Display System
Unisys Dissemination Server
(Malvern, PA)
Unisys NOAAPORT Gateway System
Figure 1
Version 8.0
Page 5 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
2 NOAAPORT Ingest Description
The Unisys NOAAPORT system is an Intel based server with hardware and software installed to receive
the NWS NOAAPORT satellite broadcast and/or the Unisys WeatherMAX broadcast data stream. The
Unisys WeatherMAX broadcast data stream can be received via satellite and/or a land line connection to
the Unisys WeatherMAX dissemination server located in Malvern, PA. To receive the satellite broadcast
requires an outdoor antenna system that consists of a C-Band capable satellite dish (size varies with
location, roughly 3.7 meters in diameter), an LNB, optional heater blanket, and cabling. The Satellite Link
Budget allows both the NWS NOAAPORT satellite broadcast and Unisys channel broadcast data streams
to be received using a single dish if it’s roughly 3.7 meters in diameter. You will need two satellite
receivers. If the satellite dish is roughly 3.0 meters in diameter two dishes and two satellite receivers are
required.
The satellite receiver is connected to the outdoor antenna by an RF cable and to the NOAAPORT system
by a network cable. The receiver converts the satellite signal to IP multicast which is processed by the
NOAAPORT system. See Figure 2.
The NOAAPORT software will process each NOAAPORT broadcast channel and/or Unisys broadcast
channel, assembling packet data into a stream and send the data over a reliable TCP/IP socket
connection to a set of client processes. Client processes include the Unisys Product Manager, LDM
(Local Data Manager from Unidata) or Unisys Weather Server (GWIP) all of which reside in the Unisys
NOAAPORT system. A user can also connect to the NOAAPORT system by IP sockets with their own
product manager. The user can receive the data as either raw NOAAPORT frames or as WMO bulletins
in a format similar to the old Family of Services (FOS) feed.
Figure 2
Version 8.0
Page 6 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
2.1
National Weather Service NOAAPORT Broadcast Channels
The NWS NOAAPORT broadcast system provides a one-way broadcast communication of NOAA
environmental data and information in near-real time to NOAA and external users. There are four logical
channels. This includes the GOES, NWSTG, NWSTG2, and OCONUS broadcast channels.




2.2
GOES - The GOES data stream consists of imagery data from the GOES East and GOES West
satellites and includes visible (VIS), infrared (IR), water vapor (WV), shortwave infrared (SWIR),
band 6 and select sounder images and products for the Eastern Conterminous United States
(ECONUS), Western Conterminous United States (WCONUS), super national composites, and
Northern Hemisphere (NH) composites.
NWSTG - The NWSTG (NWS Transmission Gateway) data stream provides observations, radar
products, forecasts, watches and warnings generated by the NWS forecast offices; as well as
model output from NCEP models.
NWSTG2 - An additional channel for NWS products including high resolution model data from
NCEP.
OCONUS/DCP - The fourth data stream is currently used for non-CONUS data such as Alaskan
and Hawaiian model data and satellite imagery (including select Polar Orbiting Satellite channels)
and as well specialized data sets such as research oriented data.
Unisys Broadcast Channel
The Unisys broadcast channel contains the Unisys WeatherMAX product data stream. The data stream
can be received via satellite broadcast (over same SES-1 satellite as NWS NOAAPORT broadcast)
and/or a land line connection to the Unisys WeatherMAX dissemination server located in Malvern, PA. If
both the satellite receiver and land line connection are configured, the user can configure the land line
connection or satellite receiver as the primary communication link and the other as a backup. If auto
failover is enabled (user configurable) and the primary fails (broken line, router failure, etc.) or the
throughput rate drops below a user configurable value, the NOAAPORT system will automatically failover
to the backup. There is no auto failback to the primary connection. The user must perform this manually
by running a script.
3 End Users
The Unisys NOAAPORT system can support up to 32 end users. Each end user establishes a separate
TCP/IP socket connection to the Unisys NOAAPORT computer. More than one end user has the
ability to receive the same NWS NOAAPORT data stream and/or Unisys channel. For example, the
NWS NOAAPORT GOES and NWSTG data stream can be sent to one user and the NWS NOAAPORT
GOES and NWSTG data stream along with the Unisys broadcast channel to another end user
The Unisys NOAAPORT system currently sends the NWS NOAAPORT satellite broadcast data stream
and/or Unisys broadcast channel to end users over a TCP/IP socket connection in one of three formats:



WXP (Unisys Weather Processor)
LDM (Unidata Local Data Manager)
GWIP (Unisys Weather Server)
Software supporting all three formats come automatically bundled with the Unisys NOAAPORT system.
Version 8.0
Page 7 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
3.1
Unisys Product Manager (WXP)
The WXP Product Manager processing is user configurable. The Product Manager uses a configuration
file to identify products based on WMO headers and saves the output to user defined files on the local
hard drives of the Ingest System. The Product Manager supports user defined data output, filenames
and directory structures.
The default setting divides data by channel (nwstg, nwstg2, goes, oconus, unisys) and then by data type.
The data is saved over 1 or 4 disks. It organizes text data into data and text directories based on
whether it is observations and model output, or manually generated text messages such as watches and
warnings. Data goes into hourly or multi-hour collections. Binary data goes into directories based on type
such as model for GRIB data, BUFR and sat (satellite imagery). Model data is organized by model and
grid type with all data going into a single file for easier file manipulation. High resolution 1km satellite
imagery is re-sampled into lower resolution 4km images for easier processing. File names are based on
time and data type.
To process real-time data such as severe weather warnings, the Product Manager transmits a Product
Arrival Notification (PAN) message sent via UDP datagram to a set of user defined clients at the time the
product is received. The message contains date/time information, WMO header and location on disk of
the product (filename, byte offset and size).
Archiving of the data is done automatically using time stamped file names. The Product Manager uses
separate scour processes to remove data off the server. This is user configurable by directory and by file
size and/or age.
Refer to the WXP User’s guide for further information regarding configuring and running WXP.
3.2
Unidata Local Data Manager (LDM)
The NOAAPORT system supports output to the Local Data Manager (LDM) software system available
from Unidata ( www.unidata.ucar.edu/software/ldm/). 64 bit LDM software is supplied with the system. LDM
provides product manager functionality comparable to the Unisys Product Manager. In addition, it
provides a store and forward function for distributing data to multiple computers/clients.
3.3
Unisys Weather Server (GWIP)
The Unisys Weather Server receives the Unisys broadcast channel data stream and archives the data to
disk. The Unisys Weather Server does not process the NWS NOAAPORT data stream.
Features of the Weather Server are:





user configurable control files for product directory structure, site/product filtering, and product file
naming specifications
automatic archiving (i.e., maintains a specified number of copies of each product and deletes files
as they age)
creates storm attributes products from NEXRAD Composite Reflectivity products
sends PAN (Product Arrival Notices) messages via a UDP socket connection to a list of
registered clients upon receipt of a weather product
monitors the Unisys broadcast channel data feed showing product count and any errors
Refer to Unisys Weather Server User’s guide further information regarding configuring and running GWIP.
Version 8.0
Page 8 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
4 SNMP Monitoring
The Unisys NOAAPORT system is SNMP enabled, and has its own publicly registered OID under
Unisys Weather. An OID or object identifier is an identifier used to name an object . Structurally, an OID
consists of a node in a hierarchically-assigned namespace, formally defined using the ITU-T's ASN.1
standard. Successive numbers of the nodes, starting at the root of the tree, identify each node in the
tree. Designers set up new nodes by registering them under the node's registration authority. With
SNMP you can monitor common functions like CPU utilization, memory usage, disk space, and
processes. The NOAAPORT system will also let you monitor NOAAPORT functions like throughput and
frame loss, and provide information about the Novra S300 satellite receiver.
HP Openview, HostMonitor, Nagios, and MRTG are some of the 3rd party tools used for processing
SNMP. These tools can also be used for monitoring, alarming, and notification, as well as generating
graphs to give you a historical perspective on resources and how they are being used over time. They
can send SMS messages and/or email your support staff when a threshold has been reached and
something needs attention. With SNMP there is no need to write special monitoring scripts, or be in the
dark about an overused resource.
An SNMP OID (object identifier) is assigned to an individual object within a Management Information
Base (MIB). An MIB can be broken down into a tree structure. Within this structure, individual OIDs are
representative of the leaves on the tree. More specifically, an OID is a string of numbers readable only to
the MIB.
The OID for Unisys is 223. The OID for Unisys Weather is 27. The OID for NOAAPORT system is 1. The
OID for the Novra S300 satellite receiver is 2
The OID for accessing NOAAPORT functions is:
iso.org.dod.internet.private.enerprises.unisys.unisysweather.noaaport
1.3.6.1.4.1.223.27.1
The OID for accessing the Novra S300 satellite receiver statistics is:
iso.org.dod.internet.private.enterprises.unisys.unisysweather.s300
1.3.6.1.4.1.223.27.2
Following NOAAPORT functions are monitored:
Function
Throughput (bps) for last minute (each channel)
Throughput (bps) for last 5 minutes (each channel)
Number of lost frames (each channel)
Number of products (each channel)
Throughput for last minute (total of all channels)
Throughput for last 5 minutes (total of all channels)
Number of lost frames (total of all channels)
Number of products (total of all channels)
Version 8.0
OID
1.3.6.1.4.1.223.27.1.2.1.3.n
where n = channel number (1 ..8)
1.3.6.1.4.1.223.27.1.2.1.4.n
where n = channel number (1 ..8)
1.3.6.1.4.1.223.27.1.2.1.5.n
where n = channel number (1 ..8)
1.3.6.1.4.1.223.27.1.2.1.6.n
where n = channel number (1 ..8)
1.3.6.1.5.1.227.1.3.0
1.3.6.1.5.1.227.1.4.0
1.3.6.1.5.1.227.1.5.0
1.3.6.1.5.1.227.1.6.0
Page 9 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
Following Novra S300 satellite receiver functions are monitored:
Function
SIGNAL_STRENGTH_AS_DBM
SIGNAL_LOCK
DATA_LOCK
UNCORRECTABLES
CARRIER_TO_NOISE
TOTAL_DVB_PACKETS_ACCEPTED
TOTAL_UNCORRECTABLE_TS_PACKETS
OID
1.3.6.1.4.1.223.27.2.1.0
1.3.6.1.4.1.223.27.2.2.0
1.3.6.1.4.1.223.27.2.3.0
1.3.6.1.4.1.223.27.2.4.0
1.3.6.1.4.1.223.27.2.5.0
1.3.6.1.4.1.223.27.2.6.0
1.3.6.1.4.1.223.27.2.7.0
5 System Layout
The NOAAPORT system is under the following directories:
Directory
/usr/noaaport
/usr/noaaport/bin
/usr/noaaport/etc
/usr/noaport/logs
/usr/noaaport/logs/latency
/usr/noaaport/logs/availability
5.1
Description
Base directory for all software, configuration and log files
Executables and scripts
Configuration files
Log files
Latency log files (only applies to Unisys broadcast channel)
Availability log files (only applies to Unisys broadcast channel)
NOAAPORT System Scripts/Processes
The scripts/processes that compose the NOAAPORT system are located in the /usr/noaaport/bin
directory.
5.1.1
Scripts
Following is a list of scripts. These scripts start, stop and restart various NOAAPORT processes. A
directory path need not be specified when running the scripts.
Script
noaaport
switch_land
switch_sat
noaaport_stats
noaaport_skyline1,
noaaport_skyline2,
noaaport_skyline3,
noaaport_skyline4,
noaaport_skyline5,
noaaport_skyline6
Version 8.0
Description
Starts, stops and restarts the NOAAPORT processes. It makes sure the
processes are started under the “unisys” user account.
Manually switches the data ingest feed from the satellite receiver to a
land line connection. Only applies to the Unisys broadcast channel
Manually switches the data ingest feed from a land line connection to
the satellite receiver. Only applies to the Unisys broadcast channel.
Starts the NOAAPORT status display process in a new window.
Starts the NOAAPORT skyline display process for a particular NWS
NOAAPORT broadcast channel and/or Unisys channel (1-6) in a new
window.
Page 10 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
5.1.2
Processes
Following is a list of NOAAPORT processes. These processes are loaded and started via the
NOAAPORT system scripts listed in section 5.1.1. They should not be started manually.
Process
noaaport_startup
noaaport_kill
noaaport_xstats
noaaport_skyline
noaaport_distrib,
noaaport_prodgen
noaaport_satcomm
noaaport_landcomm
noaaport_snmpstats_np
noaaport_snmpstats_s300
noaaport_ether
noaaport_switch_unisys_comm
5.2
Description
Starts the NOAAPORT system processes
Stops the NOAAPORT system processes
Displays a status screen for monitoring the NOAAPORT data
processing
Displays a graph showing the latest 30 seconds of NOAAPORT data
throughput for a selected channel
Sends products to end user
Generates products for end user
Satellite communications
Unisys channel TCP/IP land line communications
Collects SNMP stats for NOAAPORT system
Collects SNMP stats for Novra S300 satellite receiver
Reads configuration from Ethernet interface
Switches reading data stream between satellite receiver and TCP/IP
land line connection for the Unisys broadcast channel
Configuration Files
The configuration files are located in the /usr/noaaport/etc directory. These include:
Configuration File
noaaport.cfg
gwid###.fil
gwid###.asc
Version 8.0
Description
NOAAPORT system configuration file. It specifies input ports, output
streams and license.
Product filter file. It is an encrypted file that lists the products a user is
licensed to receive. This file only applies to products received over the
Unisys broadcast channel.
ASCII version of the product filter file. This is not used by the
NOAAPORT system but is available to let the users view which
products they are licensed to receive.
Page 11 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
5.3
Log Files
The log files are saved into the /usr/noaaport/logs directory. These include:
Log File
noaaport.log
distrib_n-mmdd
prodgen_n-mmdd
satcomm_n-mmdd
landcomm_n-mmdd
snmpstats_s300-mmdd
snmpstats_np-mmdd
satcomm_0.out
5.4
Description
Log file for the NOAAPORT system
Log file for the noaaport_distrib process (n = user number, mmdd =
month/day)
Log file for the noaaport_prodgen process (n = user number, mmdd =
month/day)
Log file for the noaaport_satcomm process (n = channel number,
mmdd = month/day)
Log file for the noaaport_landcomm process (n = channel number,
mmdd = month/day)
Log file for the noaaport_snmpstats_s300 process (mmdd =
month/day)
Log file for the noaaport_snmpstats_np process ( mmdd = month/day)
Raw frames from the NWS NOAAPORT broadcast channels and is
user mostly for debugging.
License File
The license file is created and stored on the NOAAPORT computer by Unisys when the
NOAAPORT system is assembled and configured. The license file is stored in
“ /usr/noaaport/etc/noaaport.lic” . Do not delete or modify this file. If you do, the NOAAPORT
software will not run.
Version 8.0
Page 12 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
6 Running NOAAPORT
The NOAAPORT system is a set of processes that will start up and run independent of each other. The
NOAAPORT computer is initially configured with two accounts (unisys and root). The initial password for
each account is “unisys”.
6.1
Automatic Startup
The NOAAPORT system is set up to start on system bootup. The “noaaport” script in the /etc/init.d
directory is set to run on init levels 3 and 5 (Graphical Login). When the system boots, the NOAAPORT
system will load and run in the background. Data will be processed even though there is no one logged
in or no status screen showing its running.
6.2
Manual Startup
To start the NOAAPORT system manually, log into the computer as “unisys”. Once logged in, a
graphical desktop will appear. For those familiar with Linux, this is the Gnome desktop. Open up a
terminal window, which can be selected from the right click menu on the desktop.
The NOAAPORT system can be started with the “noaaport” script which actually runs noaaport_startup.
It’s recommended to start the NOAAPORT system with this script since it ensure’s all the prerequisite
programs are run and that the processes are run under the “unisys” user account.
In each situation, the script may prompt the user for the “unisys” user account password. This is to
ensure the scripts start under the “unisys” user account. If you log into the terminal window as “root”,
(using the command “su –“) the script (noaaport) will not prompt for the “unisys” user account password.
Normally, manual startup is generally not needed since the NOAAPORT system is started when the
system boots up.
6.3
Unisys Channel Data Feed Switch Over
Data feed switch over only applies to the Unisys broadcast channel. If the NOAAPORT system is
configured to receive the Unisys broadcast channel over both the satellite feed and a land line connection
to the Unisys WeatherMAX dissemination server, the user can manually switch over from either the
satellite receiver or the land line connection by running a script in a terminal window. The script may
prompt the user for the “unisys” user account password. This is to ensure the scripts start under the
“unisys” user account. If you are logged in as “root”, the scripts will not prompt you for the “unisys” user
account password.
Script
switch_sat
switch_land
Version 8.0
Description
Switches the data ingest feed from the satellite receiver to the land
line connection
Switches the data ingest feed from the land line connection to the
satellite receiver.
Page 13 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
6.4
Restarting NOAAPORT
If at any point, the NOAAPORT system need to be restarted or stopped, the following scripts with the “kill”
or “restart” options can be run. No option indicates to start the NOAAPORT system.
Script
noaaport kill
noaaport start
noaaport restart
6.5
Description
Stops the NOAAPORT system
Starts the NOAAPORT system
Restarts the NOAAPORT system
Rebooting Computer
Once the shutdown command is run, the system will shutdown and restart. The “/etc/init.d/noaaport”
startup script will once again start the NOAAPORT Ingest system.
There are a number of ways to reboot a Linux computer. Here are three ways to perform a reboot.



First, when the user logs out, a dialog box comes up with the options: Logout, Halt or Reboot.
Select Reboot to restart the computer.
A Shutdown selection is also available on the Login Screen.
The “shutdown” command can be run from a terminal window. This must be done as root.
# su # shutdown –r (-r option indicates to reboot system after shutdown)
Once the shutdown command is run, the system will shutdown and restart. The “/etc/init.d/noaaport”
startup script will once again start the NOAAPORT system.
7 Monitoring NOAAPORT
There are no status windows started up when the NOAAPORT system is started. This is done to allow
background processing of the data. To run monitoring programs for visual evidence that the NOAAPORT
system is running properly, the following scripts can be run from a terminal window:
Script
noaaport_stats
comm_skyline1,
comm_skyline2,
comm_skyline3,
comm_skyline4,
comm_skyline5,
comm_skyline6
Version 8.0
Description
Starts the NOAAPORT Status display for monitoring the
NOAAPORT Ingest data processing
Starts the NOAAPORT Skyline program which displays a graph
showing the latest 30 seconds of data throughput for a selected
broadcast channel (1-6).
Page 14 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
7.1
NOAAPORT Status
Following is an example of the NOAAPORT System status display:
Unisys NOAAPORT System v 8.0
Jan 7 23:47:28
--- Channel Status --Port#
1
2
3
4
5
6
7
8
Data Type
DVB_NWSTG
DVB_GOES
DVB_NWSTG2
DVB_OCONUS
LAND_UNISYS
-
Status
Sat
Sat
Sat
Sat
Conn
-
Throughput(bps)
1145765
865445
1172496
384
4898763
0
0
0
Last Data Recv Time
23:47:27
23:47:27
23:47:27
23:41:28
23:41:27
----------------------
Products
320559
406
48494
79959
138591
0
0
0
Lost Frames
9
14
3
0
0
0
0
0
--- User Status --User#
1
2
3
4
5
6
Data Type
DVB_NWSTG
DVB_GOES
DVB_NWSTG2
DVB_OCONUS
LAND_UNISYS
LAND_UNISYS
Format
WXP
WXP
WXP
WXP
LDM
GWIP
IP Address/Port
127.0.0.1/5001
127.0.0.1/5003
127.0.0.1/5004
127.0.0.1/5005
*/5105
127.0.0.1/5201
Status Throughput(bps)
Conn
1139887
Conn
876642
Conn
967072
Conn
6785
Conn
24589231
Conn
34589321
Free Buf
100%
100%
100%
94%
99%
96%
Low Buf
95%
60%
72%
92%
99%
84%
System Started: Dec 22 23:49:07
Version 8.0
Page 15 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
The Channel Status section shows the data coming in from the satellite receiver and/or land line
connection from the Unisys WeatherMAX dissemination server. This is the input to the system. The
columns are as follows:
Column
Port#
Data Type
Status
Throughput
Last Data Recv Time
Products
Lost Frames
Description
Port number (1-8)
Data stream type (NWS NOAAPORT channel or Unisys channel)
Connection Status
Sat = satellite receiver
Conn/Disc = connection status if Unisys Channel land line connection
Data throughput in bps (if data is flowing it will show a positive number not 0)
Last time data was received
Number of products received
Number of lost frames. Lost frames could be an indication of a weak
signal or some kind of data problem. This number should be low
The User Status section shows the output of the NOAAPORT system. These are socket connections to a
post processing program. The columns are as follows:
Column
User #
Data Type
Format
IP Address/Port
Status
Throughput
Free Buf/Low Buf
Version 8.0
Description
User number (1-32)
Data stream type (NWS NOAAPORT channel or Unisys channel) being
sent to user
User data format (WXP, LDM, GWIP)
User IP Address/Port (socket connection) that the NOAAPORT system
connected to (* = NOAAPORT system is a server to user - user sends
connect request)
Connection status
Conn = connected, Disc = disconnected
Data throughput in bps. This is the output data flow to the user socket
connection. If the end user software is not running properly, this
throughput will be significantly lower than the upper throughput value
“Free Buf” and “ Low Buf” are critical for monitoring load on the system. If
the Free Buffers drops low, then the user is unable to keep up with the
data flow. The Low Buffer value shows how low the buffers have gotten. If
this is below 25%, the buffer size on the NOAAPORT system (see
noaaport.cfg file) needs to be increased.
Page 16 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
7.2
NOAAPORT Skyline
The skyline is a graphical representation of the product ingest feed (satellite/land line) data flow. Vertical
bars represent bandwidth consumption. The values are in 500Kbps increments from 0 – 6Mbit. The
longer the bar, the more data is flowing. Continuous high bandwidth can tax the system. If the skyline is
showing little or no dataflow, then there is a problem with the feed. This can be the result of a weak data
signal, rain fade, or a Weather Service or Unisys related data outage. Following is an example of the
NOAAPORT Skyline status display:
NOAAPORT SKYLINE
LAND_UNISYS
6
5
4
3
2
1
0
Seconds
Version 8.0
Page 17 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
7.3
Receiver Status
There is one command available for checking the status of the Novra S300 satellite receiver:
Command
s300status
Description
Displays the status (XML format) of the S300 satellite receiver
Following is an example of the S300 satellite receiver status:
<RECEIVER_STATUS TIME_STAMP="2012/02/21 12:05:15.266">
<DEVICE_TYPE>S300</DEVICE_TYPE>
<RECEIVER_MAC>00-06-76-05-02-34</RECEIVER_MAC>
<RECEIVER_IP>192.168.1.2</RECEIVER_IP>
<STATUS_TIMESTAMP>2012/02/21 12:05:15.260</STATUS_TIMESTAMP>
<DATA_SYNC_LOSS>0</DATA_SYNC_LOSS>
<CARRIER_FREQUENCY>1154 MHz (+175 kHz)</CARRIER_FREQUENCY>
<DVB_SIGNAL_TYPE>DVBS2</DVB_SIGNAL_TYPE>
<VITERBI_RATE>1/2 QPSK</VITERBI_RATE>
<MODCOD>2/3 8PSK</MODCOD>
<SIGNAL_STRENGTH_AS_DBM>-50</SIGNAL_STRENGTH_AS_DBM>
<SIGNAL_LOCK>Locked</SIGNAL_LOCK>
<DATA_LOCK>Locked</DATA_LOCK>
<LNB_FAULT>No Fault</LNB_FAULT>
<VBER>0.00e+00</VBER>
<PER>0.00e+00</PER>
<UNCORRECTABLES>0</UNCORRECTABLES>
<CARRIER_TO_NOISE>12.100000</CARRIER_TO_NOISE>
<FREQUENCY_OFFSET>175000</FREQUENCY_OFFSET>
<LOCKED_SYMBOL_RATE>15119</LOCKED_SYMBOL_RATE>
<SPECTRAL_INVERSION_FLAG>Normal</SPECTRAL_INVERSION_FLAG>
<PILOT_SYMBOL_FLAG>On</PILOT_SYMBOL_FLAG>
<FRAME_LENGTH>Short</FRAME_LENGTH>
<PID_COUNT>5</PID_COUNT>
<DVB_ACCEPTED>1776</DVB_ACCEPTED>
<TOTAL_DVB_PACKETS_ACCEPTED>739323460</TOTAL_DVB_PACKETS_ACCEPTED>
<TOTAL_UNCORRECTABLE_TS_PACKETS>3</TOTAL_UNCORRECTABLE_TS_PACKETS>
<ETHERNET_TRANSMIT>272</ETHERNET_TRANSMIT>
<ETHERNET_RECEIVE>0</ETHERNET_RECEIVE>
<ETHERNET_PACKET_DROPPED>0</ETHERNET_PACKET_DROPPED>
<ETHERNET_RECEIVE_ERROR>0</ETHERNET_RECEIVE_ERROR>
<TOTAL_ETHERNET_PACKETS_OUT></TOTAL_ETHERNET_PACKETS_OUT>
<DVB_SCRAMBLED>0</DVB_SCRAMBLED>
<DVB_CLEAR>1776</DVB_CLEAR>
</RECEIVER_STATUS>
The key status value to look at is the CARRIER_TO_NOISE. IT should be above 9.0. See Section 11
Troubleshooting for additional usage of s300status command.
Version 8.0
Page 18 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
7.4
Log Files
Log files are written to the “/usr/noaaport/logs” directory. Latency logs are written to the
“/usr/noaaport/logs/latency” directory.
7.4.1
Status Log
The output of NOAAPORT startup process goes into the “noaaport.log” file. In general this is only
useful in debugging potential problems with the NOAAPORT system.
7.4.2
Process Logs
Separate log files are created for each of the supporting processes. A new log file is created each day.
Following is the format of the log file names.
Process
noaaport_prodgen
noaaport_distrib
noaaport_satcomm
noaaport_landcomm
noaaport_snmpstats_s300
noaaport_snmpstats_np
Version 8.0
Log Format
prodgen_n-mmdd.log
where: n = user number
mmdd = month/day
distrib_n-mmdd.log
where: n = user number
mmdd = month/day
satcomm_n-mmdd.log
where: n = ingest port number
mmdd = month/day
landcomm_n-mmdd.log
where: n = ingest port number
mmdd = month/day
snmpstats_s300-mmdd.log
where: mmdd = month/day
snmpstats_np-mmdd.log
where: mmdd = month/day
Page 19 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
7.4.3
Latency Log
Latency logs are only created for the Unisys broadcast channel data stream where the end user format is
the Unisys Weather Server (GWIP). Latency logs show the latency time in seconds for each product
written to the Unisys Weather Server disk. A separate log file is created each day. Latency is defined as:

Time product written to Unisys Weather Server - Time product was received by Unisys
WeatherMAX
Format:
Each record written to the latency log consists of the following fields:
time site prod latency steady_state comm_type
where:
time =
site =
prod =
latency =
steady_state =
comm_type =
timestamp record written to log
site id
product id
latency time is seconds
Y/N
Y = no backlog of products being received
N = backlog of products being received (normally occurs after a restart of
the NOAAPORT, reboot of the NOAAPORT computer or restart of the
Unisys Dissemination System) and lasts for approximately 1-3 minutes
depending on the down time)
L/S
L = products being received via land line connection
S = products being received via satellite receiver
Note: Executing the command “tail –f
performance.
Version 8.0
<log file>” in a terminal window allows a user to observe latency
Page 20 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
8 Serving Weather Products to Other Computers
All weather product data is stored under the /data directory. There are two methods for accessing the
data on the server: NFS and SMB. The table below shows the location of the product data for the various
file formats.
User Format
Unisys WXP Product Manager (WXP)
Unidata Local Data Manager (LDM)
Unisys Weather Server (GWIP)
8.1
Location
/data/goes, /data/goesw, /data/nwstg, /data/nwstg2,
/data/oconus, /data/unisys
/data/ldm/ldm.pq
/data/wxmax
NFS (Network File System)
The NOAAPORT computer exports the /data directory as read-only for mounting by other Unix based
systems.
To mount the data directory on another Unix system, the root administrator of that computer will have to
invoke a command like:
# mount
noaaport:/data/wxmax
/mnt/data
This assumes that the WeatherMAX computer has been entered into the local host table as “noaaport”
and that an appropriate mount point such as “/mnt/data” has been created on the local computer.
8.2
SMB (Windows File Sharing)
The NOAAPORT computer is set up to make the /data directory available to Windows PCs (Win98,
WinNT, Win2K, WinXP Win7) using the Samba program. It is configured as read-only and with guest
access. In other words, all PC computers can map a drive without a password. The computer name will
be “noaaport” (or whatever is set as hostname) and the mapping will be:
\\noaaport\data\wxmax
Version 8.0
Page 21 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
9 Configuring NOAAPORT
The NOAAPORT computer is pre-configured by Unisys to meet your operational needs. However, you
can change the operational characteristics of the NOAAPORT computer through its configuration file. The
file is located at /usr/noaaport/etc/noaaport.cfg
The configuration file is divided into three sections:



[PARAMS]
[USERS]
[FILTER]
Defines system parameters
Defines the end users to receive data via TCP/IP socket connection.
Defines WMO bulletins to be filtered (i.e., not sent to end user)
Within each section is a list of keywords followed by an equal (=) sign and one or more parameters. All
keywords and parameters must be in upper case. Spaces and tabs are permitted, but not necessary
between the keyword, equal sign and value(s).
Continuation lines are specified by terminating the line with a backslash (\). A space must precede the
backslash.
A semicolon (;) is used for comments. A comment may appear anywhere. Anything entered after the
semicolon character is ignored.
The following sections describe the valid keywords within each section.
9.1
[PARAMS] Section
This section has the following configuration parameters:
The [PARAMS] section specifies system parameters. All keywords are optional. If the keyword is not
specified, a default value is assigned as described below.
9.1.1
LOGMASK
Specify message types to be written to the NOAAPORT process logs. This feature is mainly used for
trouble shooting purposes.
Format:
LOGMASK = 0xhh, size
where: hh = log mask. Following lists the log mask settings:
0x01 Satellite Protocol Messages
0x02 Error Messages
0x04 Status Messages
0x08 Debug Messages
0x10 TCP/IP Protocol Messages
size = log file size in megabytes
Example:
LOGMASK = 0x19, 5
Log TCP/IP Protocol, Debug, and Satellite Protocol Messages.
File Size = 5 megabytes.
Default:
9.1.2
0x06, 5
NUM_USERS
Specifies the number of end users (i.e., socket connections) receiving the NOAAPORT data stream(s).
Version 8.0
Page 22 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
Format:
NUM_USERS = n
where: n = number of users (1-32)
Example:
NUM_USERS = 6
Default:
4
9.1.3
NOAAPORT_BUF_SIZE
Specifies input buffer sizes for storing the NOAAPORT broadcast data streams as received from the
satellite receivers and/or Unisys broadcast land line connection
Format:
NOAAPORT_BUF_SIZE = size1, size2, size3, size4,... (up to 8)
where:
sizen = buffer sizes (in megabytes) for Port #1, Port #2 … Port#8
maximum allowable value = 10 megabytes
Typical value = 1 megabyte.
Example:
NOAAPORT_BUF_SIZE = 3, 1, 4, 10
Port #1 = 3 megabytes, Port #2 = 1 megabyte, Port #3 = 4 megabytes,
Port #4 = 10 megabytes
Default:
9.1.4
1 megabyte
NOAAPORT_DATA_STREAM
Specifies the NOAAPORT broadcast data stream types to be received on each port.
Format:
NOAAPORT_DATA_STREAM = {stream1,ipaddrs}, {stream2,ipaddrs} … (up to 8)
where: streamn = data stream type on Port #1, Port #2, … Port#8
DVB_NWSTG =
DVB_GOES =
DVB_NWSTG2
DVB_OCONUS =
DVB_UNISYS =
LAND_UNISYS =
DVB NWSTG data stream (satellite)
DVB GOES data stream (satellite)
DVB NWSTG2 data stream (satellite)
DVB OCONUS/DCP data stream (satellite)
Unisys channel data stream (satellite)
Unisys channel data stream (land line)
ipaddrs = multicast address (satellite feed)
IP address of NIC card (land line)
Multicast address for each satellite channel is as follows:
DVB_NWSTG 224.0.1.1
DVB_GOES
224.0.1.2
DVB_NWST2 224.0.1.3
DVB_OCONUS 224.0.1.4
DVB_UNISYS 224.0.1.200
Example:
Version 8.0
NOAAPORT_DATA_STREAM = {DVB_NWSTG,224.0.1.1}, {DVB_GOES,224.0.1.2}, \
{DVB_UNISYS,224.0.1.200}, \
{LAND_UNISYS,192.168.51.70}
Page 23 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
Port #1 = DVB_NWSTG (satellite), Port #2 = DVB_GOES (satellite),
Port #3 = DVB_UNISYS (satellite), Port#4 = LAND_UNISYS (land line)
Default:
9.1.5
None
SAVE_HDLC_FRAMES
Specifies if the NOAAPORT HDLC frames as received from the satellite receiver should be saved to a file
on disk. This feature is mainly used for trouble shooting purposes. The files are located in
/usr/noaaport/logs directory and named as satcomm_#.out.
SAVE_HDLC_FRAMES = {1,min}, {2,min}, {3,min}, … (up to 8 ports)
Format:
where: 1-8 = port #
min = minutes worth of data to be saved (zero = do not save)
Example:
SAVE_HDLC_FRAMES = {1,60}, {2,0}, {3,30}, {4,0}
Save 60 minutes worth of data for port #1 and 30 minutes worth of data
on port #3.
Default:
9.1.6
No data is saved.
MULTICAST_INTERFACE
Specifies the IP address of the NIC interface to listen on for DVB multicast packets from the NWS
broadcast stream. When you configure the LAN for the DVB receiver, use the IP address of the NIC card
for that LAN.
Format:
MULTICAST_INTERFACE = ipaddrs
where: ipaddrs = IP address of the NIC card connected to the DVB receiver.
Example:
MULTICAST_INTERFACE = 10.0.0.2
Default:
None
9.1.7
UNISYS_MULTICAST_INTERFACE
Specifies the IP address of the NIC interface to listen on for DVB multicast packets from the Unisys
broadcast channel. This is not required if the same NIC interface is used for both the NWS NOAAPORT
broadcast S300 receiver and the Unisys broadcast S300 receiver. When you configure the LAN for the
DVB receiver, use the IP address of the NIC card for that LAN.
Format:
UNISYS_MULTICAST_INTERFACE = ipaddrs
where: ipaddrs = IP address of the NIC card connected to the DVB receiver.
Example
UNISYS_MULTICAST_INTERFACE = 10.0.0.3
Default:
None
9.1.8
S300_IP
Specifies the IP address of the Novra S300 satellite receiver.
Version 8.0
Page 24 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
Format:
S300_IP = ipaddrs
where: ipaddrs = S300 IP address
Example:
S300_IP = 192.168.1.2
Default:
None
9.1.9
SNMP_COMMUNITY
Specifies the SNMP community string for accessing SNMP statistics
Format:
SNMP_COMMUNITY = string
where: string = SNMP community string
Example:
SNMP_COMMUNITY = public
Default:
None
9.1.10 LATENCY_LOG
Specifies whether to create a latency log. This only applies if the Unisys broadcast channel is configured.
Format:
LATENCY_LOG = n
Where: n = YES/NO
Example:
LATENCY_LOG = YES
Default:
NO
9.1.11 LANDCOMM_IP_INTERFACE
Specifies the IP address of the NIC interface for receiving data from the Unisys WeatherMAX
Dissemination server. This only applies if the Unisys broadcast channel is configured as a land line
connection.
Format:
LANDCOMM_IP_INTERFACE = ipaddrs
where: ipaddrs = IP address of the NIC card used for receiving data from the Unisys
WMAX Dissemination server.
Example
LANDCOMM_IP_INTERFACE = 10.0.0.4
Default:
None
9.1.12 LANDCOMM_SOCK_RECV_BUF_SIZE
Specifies the socket receive buffer size. This only applies if a Unisys broadcast channel land line
connection is configured.
Format:
Version 8.0
LANDCOMM_SOCK_RECV_BUF_SIZE = n
Page 25 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
where: n = socket receive buffer size
Example:
LANDCOMM_SOCK_RECV_BUF_SIZE = 131072
Default:
65536
9.1.13 LANDOMM_PORT_NUM
Specifies the socket port number for establishing a connection to the Unisys WeatherMAX dissemination
server. This only applies if the Unisys broadcast channel is configured as a land line connection.
Format:
LANDCOMM_PORT_NUM = n
where: n = port number
Example:
LANDCOMM_PORT_NUM = 5003
Default:
None.
9.1.14 LANDCOMM_HEARTBEAT_TIMEOUT
Specifies the timeout in seconds to wait for receipt of a heartbeat message or product data from the
Unisys Dissemination server prior to resetting the socket connection. This only applies if the Unisys
broadcast channel is configured as a land line connection.
Format:
LANDCOMM_HEARTBEAT_TIMEOUT = n
where: n = timeout in secs
Example:
LANDCOMM_HEARTBEAT_TIMEOUT = 5
Default:
10
9.1.15 LANDCOMM_CONNECT_TIMEOUT
Specifies the timeout in seconds to wait for establishing a land line connection to the Unisys
Dissemination server prior to failover to the satellite receiver. This only applies if the Unisys broadcast
channel is configured both as a land line connection and satellite and auto failover is enabled.
Format:
LANDCOMM_CONNECT_TIMEOUT = n
where: n = timeout in secs
Example:
LANDCOMM_CONNECT_TIMEOUT = 500
Default:
300
9.1.16 UNISYS_PRIMARY_COMM
Specifies the primary communications connection (satellite or land line) for the Unisys broadcast channel.
This only applies if the Unisys broadcast channel is configured both as a land line connection and
satellite.
Format:
UNISYS_PRIMARY_COMM = x
where: x = communications type (LAND,SAT)
Version 8.0
Page 26 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
Example;
UNISYS_PRIMARY_COMM = LAND
Default:
LAND
9.1.17 UNISYS_AUTO_FAILOVER
Specifies if auto failover is enabled for the Unisys broadcast channel. This only applies if the Unisys
broadcast channel is configured both as a land line connection and satellite.
Format:
UNISYS_AUTO_FAILOVER = x
where: x = YES/NO
YES = automatically failover to backup if primary connection fails
NO = disable auto failover to backup if primary connection fails
Example:
UNISYS_AUTO_FAILOVER = YES
Default:
YES
9.1.18 UNISYS_THROUGHPUT_THRESHOLD
Specifies the data throughput threshold (bps) prior to switching the Unisys broadcast channel data feed
from the primary connection to the backup. This only applies if the Unisys broadcast channel is
configured both as a land line connection and satellite.
Format:
UNISYS_THROUGHPUT_THRESHOLD = rate,time
where: rate = bps
time = validation time in secs
Example:
UNISYS_THROUGHPUT_THRESHOLD = 500000,120
The data throughput must average 500000 bps over 120 second time frame. If less than
500000 bps, the NOAAPORT system will switch from the primary connection to the
backup.
Default:
256000,600
9.1.19 UNISYS_FILTER_ID
Specifies a 3 character ID for the Unisys broadcast channel filter file (giwdnnn.asc) file. This only applies
if the Unisys broadcast channel is configured.
Format:
UNISYS_FILTER_ID = nnn
where: nnn = 3 character D for the filter file (gwidnnn.fil)
Example:
UNISYS_FILTER_ID = 223
Filter file name = gwid223.fil
Default:
Version 8.0
None
Page 27 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
9.1.20 UNISYS_FILTER_KEY
Specifies an 8 character key for decrypting the Unisys broadcast channel filter file (giwdnnn.asc) file. This
only applies if the Unisys broadcast channel is configured.
Format:
UNISYS_FILTER_KEY = nnnnnnn
where: nnnnnnn = 8 character key
Example:
UNISYS_FILTER_KEY = 2BH567FQ
Default:
None.
Version 8.0
Page 28 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
9.2
[USERS] Section
9.2.1
USER_x
Specifies configuration data for each user. There must be one USER_n keyword for each user.
Format:
USER_n = stream, format, bufsiz, mode, ipaddr, port
where: n = user number (1-32)
stream = data stream to be received. Possible values are:
DVB_NWSTG, DVB_GOES, DVB_NWSTG2, DVB_OCONUS,
DVB_UNISYS, LAND_UNISYS
format = Data format type. Possible values are: WXP, LDM, GWIP, FRM
WXP = Unisys Weather Radar Display Processor
LDM = Unidata Local Data Manager
GWIP = Unisys Weather Server
FRM = Raw NWS NOAAPORT broadcast frames as received (unaltered)
bufsiz = Buffer size (in megabytes) for queing data to be sent to the end
user over the TCP socket connection. This buffer is a circular queue.
The buffer size needs to be large enough not to allow it to wrap if
the user cannot receive the data fast enough. Typical value is 50
megabytes.
mode = Indicates if the end user is a server or client. A server listens for TCP
socket connection requests. A client sends socket connection requests.
Possible values are:
SERVER, CLIENT
Ipaddr = IP address of end user. If the user is a client, enter an asterisk (*).
port = TCP port number that the NOAAPORT data stream will be sent over to
the end user
Example:
Version 8.0
USER_1
USER_2
USER_3
USER_4
=
=
=
=
DVB_GOES,
DVB_NWSTG,
DVB_NWSTG2,
DVB_OCONUS,
WXP, 5,
WXP, 5,
WXP, 10,
WXP, 5,
SERVER,
SERVER,
SERVER,
SERVER,
Page 29 of 36
127.0.0.1,
127.0.0.1,
127.0.0.1,
127.0.0.1,
5001
5002
5003
5004
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
9.3
[FILTER] Section
9.3.1
USER_x
Specifies WMO bulletin filtering information for each user. This information determines which bulletins are
sent over the TCP/IP socket connection to the end user. There must be one USER_n keyword for each
user (i.e., number specified on NUM_USERS keyword in [PARAMS] section).
Format:
USER_n = mod {x,x ... x} {x,x ... x} {x,x ... x} {x,x ... x} {x,x ... x} {x,x ... x}, \
{x,x ... x} {x,x ... x} {x,x ... x} {x,x ... x} {x,x ... x} {x,x ... x}, \
.
.
.
{x,x... x} {x,x... x} {x,x... x} {x,x... x} {x,x... x} {x,x... x}
where: n = user number (1-32). This number must agree with the user number specified
on the USER_n keywords in the [USERS] section.
mod = NONE_EXCEPT or ALL_EXCEPT
NONE_EXCEPT = filter bulletins that match the specified pattern(s)
ALL_EXCEPT = do not filter bulletins that match the specified pattern(s)
x = character matching pattern
{ } is a position to match with a pattern. Valid patterns are: *, c1-c2 and c
* = any single character
c1-c2 = range of characters
c = single character
Notes: Each group of six patterns define a candidate for a bulletin name. Bulletins are
separated by a comma.
Example:
USER_1 = ALL_EXCEPT {H} {A-H,K} {F,K,S,U} {*} {*} {Y}, \
{*} {B} {F-M,R,T,W} {H} {*} {*}
Above example shows two patterns for filtering WMO bulletins. All bulletins will be filtered
except if one of the following two conditions are satisfied:
Condition #1
• 1st character must be H
• 2nd character must be A-H or K
• 3rd character must be F,K,S or U
• 4th character may be anything
• 5th character may be anything
• 6th character must be Y
Condition #2
• 1st character may be anything
• 2nd character must be B
• 3rd character must be F-M, R, T or W
• 4th character must be H
Version 8.0
Page 30 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
• 5th character may be anything
• 6th character may be anything
Default:
Version 8.0
ALL_EXCEPT {*} {*} {*} {*} {*} {*}
No filtering (all bulletins are sent to end user).
Page 31 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
10 Sample NOAAPORT Configuration
Example #1
Following configuration file is an example of a NOAAPORT system receiving the the four NWS
NOAAPORT data streams and Unisys Channel data stream over satellite. There are 5 end users (4 WXP
users and 1 LDM) receiving data.
;GENERAL_PARAMS
[PARAMS]
LOGMASK = 0X06,5
NOAAPORT_BUF_SIZE = 10,10,10,10,10
NUM_USERS = 5
SAVE_HDLC_FRAMES = {1,0}, {2,0}, (3,0}, {4,0}
NOAAPORT_DATA_STREAM = {DVB_NWSTG, 224.0.1.1}, {DVB_GOES, 224.0.1.2}, \
{DVB_NWSTG2, 224.0.1.3}, {DVB_OCONUS, 224.0.1.4}, \
{DVB_UNISYS, 224.0.1.200}
MULTICAST_INTERFACE = 10.0.0.2
UNISYS_MULTICAST_INTERFACE = 10.0.0.2
S300_IP = 192.168.1.2
;UNISYS_CHANNEL_PARAMS
UNISYS_FILTER_ID = 234
UNISYS_FILTER_KEY = DG54F0KL
[USERS]
;
USER_1 =
USER_2 =
USER_3 =
USER_4 =
USER_5 =
DATA TYPE
DVB_NWSTG,
DVB_GOES,
DVB_NWSTG2,
DVB_OCONUS,
DVB_UNISYS,
FORMAT
WXP,
WXP,
WXP,
WXP,
LDM,
BUFSIZE
100,
50,
50,
50,
200,
[FILTER]
USER_1 =
USER_2 =
USER_3 =
USER_4 =
USER_5 =
ALL_EXCEPT
ALL_EXCEPT
NONE_EXCEPT
ALL_EXCEPT
NONE_EXCEPT
{*}
{H}
{A}
{*}
{H}
{*}
{*}
{*}
{*}
{*}
Version 8.0
{*}
{*}
{B-G}
{*}
{*}
Page 32 of 36
MODE
SERVER,
SERVER,
SERVER,
SERVER,
CLIENT,
{*}
{*}
{*}
{*}
{D-E,T} {*}
{*}
{*}
{*}
{*}
IPADDRS
127.0.0.1,
127.0.0.1,
127.0.0.1,
127.0.0.1,
*,
PORT
5001
5003
5004
5005
5105
{*}
{*}
(*}
{*}
{*}
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
Example #2
Following configuration file is an example of a NOAAPORT system receiving the Unisys Channel via
satellite feed and also a line connection to the Unisys WeatherMAX dissemination server. There are 4
end users (LDM user receiving Unisys Channel (satellite), LDM user receiving Unisys channel (land line),
GWIP user receiving Unisys channel (satellite) and GWIP user receiving Unisys channel (land line).
[PARAMS]
;GENERAL_PARAMS
LOGMASK = 0X0E,5
NOAAPORT_BUF_SIZE = 5,5
NUM_USERS = 2
SAVE_HDLC_FRAMES = { 1,0} , {2,0}, (3,0}, {4,0}
NOAAPORT_DATA_STREAM = {DVB_UNISYS, 224.0.1.200}, {LAND_UNISYS,192.168.51.35}
UNISYS_MULTICAST_INTERFACE = 10.0.0.2
S300_IP = 192.168.1.2
LATENCY_LOG = YES
;UNISYS_CHANNEL_PARAMS
UNISYS_FILTER_ID = 232
UNISYS_FILTER_KEY = 87030DF56
UNISYS_THROUGHTPUT_THRESHOLD = 256000,600
UNISYS_PRIMARY_COMM = LAND
UNISYS_AUTO_FAILOVER = YES
;UNISYS_LANDCOMM_PARAMS
LANDCOMM_SOC_RECV_BUF_SIZE = 131072
LANDCOMM_IP_INTERFACE = 10.0.0.2
LANDCOMM_PORT_NUM = 5002
LANDCOMM_HEARTBEAT_TIMEOUT = 10
LANDCOMM_CONNECT_TIMEOUT = 300
[USERS]
;
USER_1 =
USER_2 =
USER_3 =
USER_4 =
DATA TYPE
DVB_UNISYS
LAND_UNISYS,
DVB_UNISYS,
LAND_UNISYS,
FORMAT
LDM,
LDM,
GWIP,
GWIP,
BUFSIZE
100,
100,
50,
50,
[FILTER]
USER_1 =
USER_2 =
USER_3 =
USER_4 =
ALL_EXCEPT
NONE_EXCEPT
ALL_EXCEPT
ALL_EXCEPT
{*}
{*}
{G-K,M,Q,R}
{*}
{*}
{*}
{*}
{*}
{T}
{*}
{*}
Version 8.0
Page 33 of 36
MODE
CLIENT,
CLIENT,
SERVER,
SERVER,
{*}
{F-L}
{*}
{*}
{*}
{*}
{*}
{*}
IPADDRS
*,
*,
127.0.0.1,
127.0.01,
{*}
{*}
{*}
{*}
PORT
5001
5002
5201
5201
{*}
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
11 Troubleshooting
Problem
Possible Cause and Solution
Disk is full
This is a rare problem since the archive depth is set such that no more than 2GB
of data is saved at any one time. Run a “df” and see if the /data partition is not
full.
Unisys Weather
Server is down
The Unisys Server is usually not the problem but checking the Server with
“gwip_stats” is usually good enough to make sure it’s running. Otherwise, do a
“ps -ef” and look for processes starting with “gwip”.
NOAAPORT system The NOAAPORT system performs little more than reformatting the packets into a
is down
data stream. It rarely encounters a situation where it would die. Again like with the
Unisys Weather Server, checking “noaaport_stats” should indicate whether the
NOAAPORT system is running. Also, running a “ps -ef” and checking for
processes starting with “noaaport” is recommended.
Receiver is down
Even though receivers don't fail that often, there are situations where it could fail
as in a near lightning strike or other power surge. Checking the status lights on
the front of the receiver is a starting point. First, make sure the green Power light
is lit. If not, check the power cable and the power off and on the switch in the
back of the receiver. Second, there should be a couple of steady green lights
(Signal and Sync). Both should be lit for clean signal. If the red Fault light is lit,
then there is a signal problem. Also, a flashing Signal light means weak signal.
Also, the “s300status” command can be run to test the receiver. If there is no
response, the receiver could be a problem (check to make sure serial cable is
hooked up before making this conclusion).
Connection to
satellite dish is
broken
There is a possibility that the connection to the satellite dish has been
compromised. This will result in a Fault light or a flashing Signal light. In some
cases, cut wiring can add noise to the line and potentially result in signal loss.
Water can get into the connections and compromise signal quality. In other
cases, line amplifiers and even LNBs can be fried by nearby lightning strikes. In
this case, a satellite technician should be called in to rectify the situation.
Satellite dish is out
of alignment, dish
out of round or
something on the
dish or in the LNB
shield (bees nest)
In most cases, this is where data is lost. If the dish isn't pointed exactly at the
satellite, the signal will be too weak to lock on to it. This would result in a Fault
light on the receiver going red or a flashing Signal light. Also, run the “s300status”
command and check the signal to noise ratio. The signal to noise ration should
be above 9.0. In this case, a satellite technician should be called out to check the
dish alignment, roundness and clean the dish of possible signal interfering items.
Also, the technician can check for the possibility of signal interference.
Rain fade
The satellite feed is subject to rain fade. During heavy rains either over the site or
just to the south (in line of site to satellite), the satellite signal will be attenuated to
the point where the receiver will lose sync and signal. This is temporary and will
end once the rain has moved by the site. Also, the uplink transmission from
Unisys in Malvern, PA can be affected by heavy rain. In these cases,
transmission will be halted at the uplink and continued after the rain has ceased to
prevent loss of data.
The satellite feed is
down
There are rare situations when the satellite feed is down. If this does occur,
Unisys will notify the client either ahead of time of potential outages or during an
unscheduled outage. Call the Help Desk (800-610-9474) for status.
Land line connection If the Unisys channel is configured for land line connection and no data is being
Version 8.0
Page 34 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
is down
received, check with local Telco company for any reported problems. Unisys will
notify client if a problem with the land line connection exists at Unisys in Malvern,
PA.
A specific data feed
is down
Since the NWS NOAAPORT broadcast or Unisys broadcast data stream is a
combination of several data feeds, the data stream may be up while a particular
feed is unavailable. If this is the result of a maintenance issue at NWS or Unisys,
the client will be notified ahead of time. If it’s the result of hardware failure at
NWS or Unisys, again, the client will be notified as the backup systems are put
into place.
A data source is
down
At times, the data feed from the source is down. Unisys has little control over
the data coming from a vendor such as the National Weather Service. In general,
vendor outages will not result in client notification. But Unisys monitors these
outages and tries to determine a cause and time frame for recovery. Clients may
call the 24x7 help desk if information is needed on these types of outages.
Version 8.0
Page 35 of 36
March 13, 2012
Unisys NOAAPORT Gateway System for Linux
12 Operating System Updates
Updates to the operating system generally do not affect the Unisys NOAAPORT Ingest system.
13 Mail Checking
Some scripts that run out of cron can create a significant amount of mail. It is recommended to check
root and unisys mail from time to time (once every other month or so) in order to make sure disk space
isn’t exhausted. Log in as root or unisys and type in “mail”. You can check individual mail messages or
type “d *” to delete all the messages. Type “q” to quit mail when done.
Version 8.0
Page 36 of 36
March 13, 2012
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement