Cisco Headend System Release 2.5 User Guide

Page of 282
 
Chapter 7    Troubleshoot the EAS with the getEASdata Utility 
 
 
 
68 
4031374 Rev B 
Introduction 
The Federal Communications Commission established the Emergency 
Alert System (EAS) in 1994 as a tool for government officials to quickly 
transmit important emergency information that is targeted to specific 
geographical areas. Digital cable system operators need a reliable EAS 
at their headend to ensure that their subscribers receive national, state, 
and local warning messages about emergency conditions. 
The getEASdata utility was developed to ensure the reliability of a 
system operator's EAS. The utility helps system operators troubleshoot 
their EAS by reporting EAS-related errors and retrieving data 
associated with system components that pertain to the EAS. The 
following list includes some of the EAS-related data retrieved by the 
getEASdata utility: 
 
Emergency Alert Controller (EAC) network configuration 
 
Emergency Alert Receiver (EAR) and Multi-Media Message 
(MMM) Server processes 
Note:  The EAR server monitors and receives EAS-related 
messages and then passes the messages to the MMM server for 
formatting and processing. 
 
Files in the /export/home/easftp directory 
 
Files converted to audio interchange file format (AIFF) and loaded 
onto the broadcast file server (BFS) carousel 
Note:  Files in AIFF are high-quality sound files 
 
EAS timing data 
Important:  The use of the getEASdata utility is only intended for 
those sites that use the DNCS for EAS messages.