Cisco Headend Digital Broadband Delivery System User Guide
Chapter 11 Troubleshoot the EAS with the getEASdata Utility
86
4020694 Rev B
Before Running the getEASdata Utility
These Conditions Must Exist on Your System
Before you run the getEASdata utility, the following system conditions must be true:
The debug flag L must be set in the .profile file.
The L debug flag indicates that logging is turned on for the MMM server group.
The getEASdata utility needs access to the MMM server logs in order to retrieve
EAS-related data.
Note: For System Release (SR) 2.1 and later, the .profile file containing debug
flag L is on the DNCS; for system software earlier than SR 2.1, the .profile file is
on the Application Server.
The L debug flag indicates that logging is turned on for the MMM server group.
The getEASdata utility needs access to the MMM server logs in order to retrieve
EAS-related data.
Note: For System Release (SR) 2.1 and later, the .profile file containing debug
flag L is on the DNCS; for system software earlier than SR 2.1, the .profile file is
on the Application Server.
You have successfully sent EAS messages in the past.
The getEASdata utility is a troubleshooting tool. Use the getEASdata utility only
if you know that the EAS has worked successfully in the past.
The getEASdata utility is a troubleshooting tool. Use the getEASdata utility only
if you know that the EAS has worked successfully in the past.
It has been at least 5 minutes and less than 15 minutes since you transmitted the
EAS message.
It sometimes takes up to 5 minutes for EAS data to reach the necessary system
components. EAS data typically remains in the system for up to 15 minutes.
EAS message.
It sometimes takes up to 5 minutes for EAS data to reach the necessary system
components. EAS data typically remains in the system for up to 15 minutes.
You know the IP address of a test DHCT in the headend that should have
received the EAS message.
received the EAS message.
The DHCT is currently responding to a ping request.