Cisco Headend System Release 2.7 User Guide

 

4031374 Rev B 

95 

 

network. 

 

Examine and correct any laser calibration issues present on your network. A 
laser that is incorrectly calibrated may produce a distorted signal. 

 

DHCTs lose the contents of their volatile memory when they reboot. After they 
reboot, DHCTs sign back on to the network and their network configuration data is 
then reloaded. Too many sign-on attempts by DHCTs contribute to network 
congestion and could cause DHCTs to become non-responders. 

The signonCount utility can help the system operator monitor the following DHCT 
network sign-on activities: 

 

DAVIC connections and UN-Config requests on a minute-by-minute basis 

 

Excessive DHCT sign-on requests 

 

QPSK modulator reboots 

 

DHCTs signing on with an incorrect type, revision, or OUI 

 

Successful sign-on statistics 

 

Run the DHCT Status Reporting Utility regularly. The DHCT Status Reporting 
Utility is designed to test and analyze two-way communications between the DHCT 
and the headend. The DHCT Status Reporting Utility provides system operators 
with the following data: 

 

Provides a current summary of the statuses of a system's DHCT population 

 

Polls all DHCTs that have an IP address and reports the following data: 

DHCT transmit levels 

DHCT delay values 

Currently loaded resident application and operating system 

 

Provides the following reports: 

DHCT non-responders by QPSK modulator and demodulator 

DHCT transmit levels by QPSK modulator and demodulator 

DHCT delay values by QPSK modulator and demodulator 

Operating system and resident application by DHCT type and revision 

General DHCT summary