CHAPTER 6: REMOTE DEVICE ALERTS
6-6
MDU Solutions
®
– UCrypt
®
Monitoring Server - Operation Manual
either rectified itself or required an automatic re-start of the CableCARD by the UCrypt equipment to rectify.
6 .8 .7 Next Steps
1. Check if the problem has corrected itself by checking ‘status’ of program in question on ‘Channel View’ page.
2. This problem may correct itself the next time entitlement messages are distributed on the network. The CableCARD
entitlement per program normally expires after a time and is refreshed automatically. If the CableCARD module ID
and Host ID are not setup correctly in the billing system there is a possibility the refresh does not happen as expected
or required. There may be other issues that could potentially cause this within the billing system.
3. If this problem has not corrected itself, contact the Cable Service Provider’s administration to ensure that the
CableCARD/host slot pair are properly recorded in the billing system. Find the CableCARD module and Host ID
numbers by following paths:
a) Cisco:
CableCARD View>CableCARD Setup>Cisco CableCARD/Host ID screen.
b) Motorola:
CableCARD View>CableCARD Setup>CableCARD Pairing.
Report the CableCARD module and Host ID numbers to your administrator.
4. Pay particular attention to the ‘DATA’ field in Cisco/SA environments as this field changes over time, but must be re-
entered with the correct current data if a card is being re-validated or re-hit.
5. Have the administrator resend (Hit) the entitlement message to the CableCARD module.
6. Repeated problems with the same CableCARD may indicate a problem deeper within the DAC/DNCS which cannot
be resolved by access at the billing system level. In this case, the assistance of a DAC/DNCS administrator may be
necessary to completely remove the CableCARD module and host IDs from the DAC/DNCS inventory and re-enter
it from scratch.
7. There is a problem with the physical CableCARD module and replacement may be necessary.
6 .9 UCrypt Tuner Lost PCR Lock Error
6 .9 .1 Refers to
The loss of Program Clock Reference on a specific multiplex or QAM channel.
PCR is required to process programs so
it is necessary to maintain PCR lock at all times.
6 .9 .2 Repetition of Alert
This alert is sent once per event, so if PCR lock is lost and is reacquired, the alert will be sent again if/when it loses lock again.
If lock is not reacquired, the Alert will not be sent again.
6 .9 .3 Customer Symptoms
Customer experiences loss of all programs on the affected tuner for the duration that the error condition exists.
6 .9 .4 Urgency
Medium - High.
6 .9 .5 Cases Where Alert is Likely a Result of:
Outside influence or normal operation
It would be expected that during certain operations such as plant maintenance when disrupting a tuned QAM or an RF outage,
the PCR lock would be lost. A loss due to a factor similar to this does not require any action as the UCrypt will regain lock when
the QAM is properly restored. It could be considered normal to lose PCR lock occasionally if this does not reoccur repeatedly.
The occasional loss does not require any attention.
An Internal Issue
Repeated occurrences of loss of PCR lock will require attention to determine the cause, which can be either internal or
external to the UCrypt.
6 .9 .6 Probable Causes
1. The subject QAM was not available on the cable system at the time of the error.
2. Plant distortions make it difficult for the UCrypt tuner to maintain lock on the subject QAM.
3. Plant maintenance has been occurring at the time of the error.
4. An internal service affecting operation within the UCrypt (such as hitting ‘apply’ or reboot) was performed just prior
to the alert.
