Cisco Headend System Release 2.7 Installation Guide

Page of 252
 
Chapter 3    Reset DHCT Configuration with the delete-sm Utility 
 
 
 
16 
4020695 Rev C 
Supported Options for the delete-sm Utility 
The delete-sm Utility Options 
The delete-sm utility supports three main options: -a-o, and ..OOS.. (dot, dot, OOS, 
dot, dot). The -a and -o options are used to reset the configuration of a single DHCT 
or a list of DHCTs. The delete-sm utility, when used with the -o option, checks for 
the presence of active packages on the DHCT(s) and resets the configuration of out-
of-service DHCTs and in-service DHCTs with no active packages. The -a option 
makes no such check and resets the configuration of the DHCT(s) regardless of the 
presence of active packages. 
The ..OOS.. option of the delete-sm utility is a special feature reserved for helping a 
site prepare to support session-based encryption (SBE).   
Note:  SBE is a feature that provides a high degree of security for video-on-demand 
(VOD) content. Through SBE, the DBDS is capable of sending secured VOD content 
only to those DHCTs that are authorized to receive VOD. 
The ..OOS.. option provides the following services: 
 
When used with the ..OOS.. option by itself, the utility de-provisions all DHCTs 
marked as out-of-service in the database. No list of MAC addresses is required. 
 
When the -o option is used in conjunction with the ..OOS.. option, in addition to 
de-provisioning DHCTs marked out-of-service in the database, the utility also 
deletes records from the secure_micro table for DHCTs with an in-service status 
that have no active packages. When DHCT records are removed from the 
secure_micro table, the DHCT can be re-staged through transactions transmitted 
by the billing vendor. 
When you run the delete-sm utility with no options, the utility resets the DHCT 
configuration only if the DHCT is not already listed as in-service in the database. 
In most cases, when the configuration of a DHCT is reset, the DHCT is assigned a 
status of out-of-service. Some sites, however, use an environmental variable called 
HCTM_PROVISIONING_APP to facilitate the deployment of DHCTs at those sites. 
When the configuration of a DHCT is reset at sites that use the 
HCTM_PROVISIONING_APP variable (variable set to 1), the DHCT is assigned a 
status of deployed.