Cisco Headend System Release 2.7 Guide De Montage
Understand the Data in the Doctor Report Fields
740020 Rev H
55
IPG Data Files
The data in the IPG Data Files field verifies that the number of days of IPG data files
on the system matches the number specified in the ipgcollectconfig table in the
database. Additionally, the data in the IPG Data Files field reports the size of the IPG
data files.
on the system matches the number specified in the ipgcollectconfig table in the
database. Additionally, the data in the IPG Data Files field reports the size of the IPG
data files.
Pioneer Note: Ignore errors at sites that run the Pioneer resident application.
Important! Note these important points about errors in the IPG Data Files field:
You may not have your IPG services mapped correctly.
Your content provider may not be providing you with data for the channels you
need.
need.
The content provider may be posting files after your IPG Collector runs. You
may need to reschedule the time you run the IPG Collector.
may need to reschedule the time you run the IPG Collector.
If IPG data files are smaller than expected, your IPG provider probably did not
create or post your files correctly. Contact your IPG provider.
create or post your files correctly. Contact your IPG provider.
Finally, run the ipgCollector manually. Then, use the appControl utility to stop
and restart the ipgServer process on the Application Server.
and restart the ipgServer process on the Application Server.
Note: IPG data files typically are large files (100 KB). Small files are therefore
flagged as errors.
flagged as errors.
Ping All Active Elements
The data in the Ping All Active Elements field reports whether the communication
path between the DNCS and the following system devices is active:
path between the DNCS and the following system devices is active:
All active QAM-family modulators
All active QPSK modulators (Ethernet and RF)
The BIG
The TED
Important! If the Doctor Report reports an error, complete the following tasks to
troubleshoot the error:
troubleshoot the error:
Visually check that the device is powered on and that the cabling is secure.
Use a network analyzer to confirm that IP traffic is reaching the device.
Reboot the device.