Cisco Headend Digital Broadband Delivery System Guía Del Usuario
Chapter 12 Examine the podData File with the podDataChk Utility
170
4031374 Rev B
Introduction
Through use of the podDataChk utility, system operators are able to
examine, in summary form, the contents of the
/dvs/dvsFiles/CCardServer/podData file. The podData file contains
data that is communicated to CableCARD modules through the
Broadcast File System (BFS) carousel, such as CableCARD
configuration data, as well as data that pertains to the authorization
and deauthorization of copy protection for CableCARD modules.
examine, in summary form, the contents of the
/dvs/dvsFiles/CCardServer/podData file. The podData file contains
data that is communicated to CableCARD modules through the
Broadcast File System (BFS) carousel, such as CableCARD
configuration data, as well as data that pertains to the authorization
and deauthorization of copy protection for CableCARD modules.
The podDataChk utility helps system operators determine what
CableCARD/host (Pod/Host) pairs are included in the podData file,
and therefore transmitted via the BFS carousel. Furthermore, because
the podData file is limited to 1,500 records, the podDataChk utility
helps system operators monitor the growth of the file. If the podData
file grew larger than 1,500 records, data in the file might not be
transmitted on the BFS carousel in a timely fashion.
CableCARD/host (Pod/Host) pairs are included in the podData file,
and therefore transmitted via the BFS carousel. Furthermore, because
the podData file is limited to 1,500 records, the podDataChk utility
helps system operators monitor the growth of the file. If the podData
file grew larger than 1,500 records, data in the file might not be
transmitted on the BFS carousel in a timely fashion.
The podData file contains only "active" records—records for
CableCARD/host pairs that are currently authorized or deauthorized.
It does not include records that were authorized or deauthorized in
the past.
CableCARD/host pairs that are currently authorized or deauthorized.
It does not include records that were authorized or deauthorized in
the past.
Each time the podDataChk utility runs, it generates the
/dvs/dvsFiles/CCardServer/podData.txt file, which contains a
complete summary of the data in the podData file. You can then use
the UNIX more utility to examine the podData.txt file. However, only
data that pertains to the option you used when you ran the
podDataChk utility is displayed on the screen of the DNCS. Read
through this chapter for a description of all the options that are
supported by the podDataChk utility.
/dvs/dvsFiles/CCardServer/podData.txt file, which contains a
complete summary of the data in the podData file. You can then use
the UNIX more utility to examine the podData.txt file. However, only
data that pertains to the option you used when you ran the
podDataChk utility is displayed on the screen of the DNCS. Read
through this chapter for a description of all the options that are
supported by the podDataChk utility.