This How-To has been created to help NWS Field Site Users, the CRS Support Team and the AWIPS Site Support Team expedite troubleshooting the data interface between the AWIPS system and the CRS system.

CRS System Assumptions

Alert Monitor

The site is monitoring the CRS Alert Monitor window in the CRS Main Window. If the Alert Monitor window has been closed for any reason, the user should reopen it by go to System -> Alert Monitor. The Alert Monitor window may be minimized. If the window is minimized and an alert condition is sensed, the window will open automatically.

Message Monitor

The site is monitoring the CRS Message Monitor window active on the CRS Main Window. If the Message Monitor icon or window is not present, the user should place the mouse cursor over any blank area of the main window, press the right mouse button and select Message Monitor. The Message Monitor window may be minimized. If the window is minimized and an alert condition is sensed, the window will open automatically.

AWIPS Interface Configured

The site has configured the CRS system to acquire data from the AWIPS LAN data interface. This can be verified by opening the Maintenance -> Site Configuration -> AFOS/AWIPS tab. Verify the Select Interface button indicates AWIPS.

NOTE: The CRS system will only accept data from either the AWIPS or AFOS (Serial) data interface. CRS can NOT be configured to accept data from both interfaces simultaneously.

AWIPS System Assumptions

The /data/fxa/workFiles/nwr/nwr.cfg file has been correctly configured on the site DS1 node. The file should contain, in strict order, the following information: crs user name, crs user password and the interface type LAN. See the following example:

ds1-nmtw{awipsusr}2: cat /data/fxa/workFiles/nwr/nwr.cfg
crs
XXXXX Verify the correct crs user password here.
LAN
ds1-nmtw{awipsusr}3:

NOTE: The user must be crs. It can not be anything else. Do not use special characters in the password. Do not use the "#" character. This character will be interpreted as a "comment" by the /awips/fxa/bin/transferNWR program.

The site DS1 /etc/hosts file contains the correct entries for the site CRS network. Note that this file is pushed by NIS to all site AWIPS nodes. See this example from the NMTW system:

# CRS (Console 
Replacement System) Devices - NOAA Weather Radio 165.92.20.111 0mp-nmtw 0MP # 
Multi-processor 165.92.20.112 5mp-nmtw 5MP # Multi-processor 165.92.20.113 1fe-nmtw 
1FEP # Front End Processor 165.92.20.114 2fe-nmtw 2FEP # Front End Processor 165.92.20.115 
3fe-nmtw 3FEP # Front End Processor 165.92.20.116 4bk-nmtw 4BKUP # Backup 165.92.20.117 
ps8-nmtw ps8 #

AWIPS-CRS Connectivity

The integrity of the LAN between the AWIPS system and the CRS system can be verified by executing the following steps. The site can perform a UNIX ping command to determine basic connectivity. At an AWIPS workstation, open a UNIX shell window and at the prompt type ping 0MP -n 5

See the following example:

ds1-nmtw{awipsusr}4: ping 0MP -n 5
PING 0mp-nmtw: 64 byte packets
64 bytes from 165.92.20.111: icmp_seq=0. time=1. ms
64 bytes from 165.92.20.111: icmp_seq=1. time=1. ms
64 bytes from 165.92.20.111: icmp_seq=2. time=1. ms
64 bytes from 165.92.20.111: icmp_seq=3. time=0. ms
64 bytes from 165.92.20.111: icmp_seq=4. time=0. ms

----0mp-nmtw PING Statistics----
5 packets transmitted, 5 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/1
ds1-nmtw{awipsusr}5:

Repeat for 5MP. Type ping 5MP -n 5

See the following example:

ds1-nmtw{awipsusr}5: ping 5MP -n 5
PING 5mp-nmtw: 64 byte packets
64 bytes from 165.92.20.112: icmp_seq=0. time=1. ms
64 bytes from 165.92.20.112: icmp_seq=1. time=0. ms
64 bytes from 165.92.20.112: icmp_seq=2. time=0. ms
64 bytes from 165.92.20.112: icmp_seq=3. time=0. ms
64 bytes from 165.92.20.112: icmp_seq=4. time=0. ms

----5mp-nmtw PING Statistics----
5 packets transmitted, 5 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/1
ds1-nmtw{awipsusr}6:

At a CRS workstation, open a Maintenance -> Unix Shell window. At the prompt type /usr/sbin/ping as1 followed by /usr/sbin/ping as2

See the following example:

0MP{admin} /usr/sbin/ping as1
as1 is alive
0MP{admin} /usr/sbin/ping as2
as2 is alive
0MP{admin}

If the ping tests fail, examine the following components for possible solutions.

CRS LANTRONIX LB2 LAN Bridge

Verify the following front panel indicators.

PWR - ON
SER - Blinking green at an approximately one (1) second rate
1 and 2 - Flashing green intermittently, indicating data flow

LAN Transceivers
NOTE: The type of transceiver(s) installed may vary site by site.

AWIPS Four (4) Port Hub

Power - ON
Link/Transmit - Flashing green intermittently, indicating data flow

What-to-Do to correct Physical Connection Problems

If problems are suspected in the physical connections between AWIPS and CRS, verify all physical connections at the AWIPS Four Port Hub and the LB2 LAN Bridge, including the seating of the AUI Transceivers. Inspect cables, connectors and terminators for visable breaks, loose connections, etc. Replace physical components as needed.

AWIPS to CRS Data Transfer Process

Voice ready products are transferred from the AWIPS system to the CRS system by the UNIX ftp process. The AWIPS script /awips/fxa/bin/transferNWR accomplishes this task. The script is able to determine which CRS Main Processor (MP) is currently the Master. Once the true Master Processor has been determined, normally 0MP, formatted products are ftp transferred to the CRS system. The transferNWR script takes formatted products from the /data/fxa/workFiles/nwr/pending directory on AWIPS and places them in the /crs/data/CP/awips directory on the CRS Master Processor.

The transferNWR script utilizes built-in logging of events and error conditions. Log data is written to the /data/logs/fxa/<Current_Date> directory. The current days log directory can be quickly reached by typing logs at the AWIPS UNIX shell command prompt. All log entries are written to the logStreamExpect file. The user can inspect the log file for pertinent messages and error reports. See the following example from the NMTW system:

ds1-nmtw{awipsusr}1: logs
ds1-nmtw{awipsusr}2: ll logStream*
-rw-rw-r-- 1 fxa fxalpha 18232 May 10 13:11 logStreamExpect
ds1-nmtw{awipsusr}3: tail logStreamExpect
13:11:33.274 TclLogStream.C EVENT: File /data/fxa/workFiles/nwr/pending/WBCHWRLWX will be automatically transferred
13:11:33.510 TclLogStream.C EVENT: Successful ping to 0MP
13:11:33.809 TclLogStream.C EVENT: Successful ping to 5MP
13:11:40.111 TclLogStream.C EVENT: Master processor is 0MP
13:11:40.112 TclLogStream.C EVENT: 7 ss_ms processes running on 0MP currently
13:11:40.116 TclLogStream.C EVENT: file WBCHWRLWX will be transmitted to CRS as WBCHWRLWX.AW

13:11:44.274 TclLogStream.C EVENT: transfer complete to 0MP
13:11:44.321 TclLogStream.C EVENT: Successful transfer of /data/fxa/workFiles/nwr/pending/WBCHWRLWX to 0MP
ds1-nmtw{awipsusr}4:

In the example product WBCHWRLWX was sent from AWIPS to CRS with a file name of WBCHWRLWX.AW The transferNWR script was able to determine that 0MP was the current CRS Master processor and reports that the subsequent ftp transfer was successful.

The AWIPS based CRS formatters can be configured to send products to CRS on a delayed basis. This allows the user the opportunity to inspect and/or edit the products for subsequent transfer to CRS. The NWRBrowser window is used to monitor those products that are in this pending state. Messages in the pending column may be edited for content or corrections. Manually highlighting the pending product and clicking the Send button, transfers the product to CRS using the transferNWR script. Consult the pertinent AWIPS documentation for details.

If the CRS application software is running and operating correctly and the site data interface configuration is set to AWIPS, formatted products will be processed by the CRS communications software for possible storage in the database and scheduling on a broadcast channel. Products will then be removed from the /crs/data/CP/awips directory. If the CRS application is not running or the data interface is set to AFOS, formatted products will remain queued in the /crs/data/CP/awips directory.

BAD Data Received at CRS

If the CRS system detects something wrong with the formatted product, as received from the AWIPS system, CRS will place the suspect product into the Master Proceessor /crs/data/CP/recovery directory. Normally this directory will be empty. Every time a product with suspect data is detected, an Alert Monitor message is generated that describes the problem with the product. These products are available for inspection and/or correction by opening the Messages -> Weather Message Correction window.

Click on the Get Error File button to select the recovery directory.

Click the Recovery Directory radio button and click OK to open a list of messages. Highlight a filename in the right hand column and click OK.

Click the Cancel button to close the directory selection popup box.

The Weather Message Correction Error message popup is displayed with the error.

Example types of errors are: Invalid Listening Area Code (LACs), invalid effective and/or expiration times, invalid headers or trailers, etc. Consult the "CRS Operational Build 6.4 Site Operator's Manual, dated May 2000, Appendix II" for Weather Message Format Specifications and the pertinent AWIPS Weather Message Product Formatter documentation.

Troubleshooting Contact Points

AWIPS Related

Network Control Facility - 301.713.9344

Support is available 24 hours/day, 7 days/week

CRS Related

CRS Support Team - 301.713.0191

Support is available 0700 to 1530 Eastern Time, Monday through Friday excluding Federal Holidays.

Joel Nathan (Team Leader) - Extension 119