Cisco Headend System Release 2.7 メンテナンスマニュアル
Recommendations to Improve Your Staging and Software Download Performance
4024836 Rev D
45
Field
Recommended Value
Display MMI for bi-directional
device
Autobinding on: inactivated (checkmark not
displayed)
Autobinding off: activated (checkmark displayed)
Autobinding off: activated (checkmark displayed)
Bidirectional timeout
Autobinding on: 180 (3 minutes)
Autobinding off: 0
Autobinding off: 0
Maximum Host Change Count Allowed
The Maximum Host Change Count Allowed field determines the maximum number
The Maximum Host Change Count Allowed field determines the maximum number
of times that a CableCARD module is allowed to autobind with a different host.
When the CableCARD exceeds this limit, it is no longer allowed to autobind with a
different host.
The DNCS allows auto-binding of Multistream CableCARDs (M-Cards) with two-
The DNCS allows auto-binding of Multistream CableCARDs (M-Cards) with two-
way Host devices. In SR 4.3, you can limit the number of autobinding requests (from
different hosts) that are honored. If the counter reaches the maximum value
configured for the system, autobinding requests are rejected by the DNCS and the
Copy Protection (CP) MMI screen is displayed.
The Maximum Host Change Count Allowed field on the CableCARD Server page
The Maximum Host Change Count Allowed field on the CableCARD Server page
defines this maximum number. The following values can be used in this field:
0 = Autobinding is not used.
1 - 98 = The valid range for the count
99 = An unlimited number of auto-bindings is allowed (default setting)
Resetting the Binding Counter
What happens when an M-Card module reaches its maximum number of
What happens when an M-Card module reaches its maximum number of
autobindings and needs to be reset? For example, if you have an M-Card that you
need to re-deploy into a different subscriber's home?
You need to reset the binding counter for this M-Card module by sending a BOSS
You need to reset the binding counter for this M-Card module by sending a BOSS
RegisterHost transaction from the billing system to the valid Host_ID associated
with the M-Card module.
The BOSS RegisterHost transaction can reset the counter even if the M-Card module
The BOSS RegisterHost transaction can reset the counter even if the M-Card module
is not physically installed in a Host device. For example, you can use a "dummy"
Host_ID to reset the counter maintained by the DNCS when preparing to reissue a
previously deployed M-Card module. In this case, you must include the
CableCARD_ID of the M-Card module in the RegisterHost transaction along with a
valid Host_ID.