Cisco Headend Digital Broadband Delivery System Guida Utente
Chapter 13 Ensure the Presence of Type-8 Staging EMMs with the type8helper Utility
110
4020694 Rev B
Place the type8helper Utility into cron
After running the type8helper utility manually the first time, you are now ready to
place the utility into the crontab file of the DNCS. When the utility runs from cron, it
automatically generate type-8 EMMs for newly staged devices that need type-8
EMMs. When you place the utility in cron, be sure to schedule execution for no more
than once a day. Furthermore, our engineers recommend that you schedule
execution for off-peak hours.
place the utility into the crontab file of the DNCS. When the utility runs from cron, it
automatically generate type-8 EMMs for newly staged devices that need type-8
EMMs. When you place the utility in cron, be sure to schedule execution for no more
than once a day. Furthermore, our engineers recommend that you schedule
execution for off-peak hours.
Important: Do not attempt to edit the crontab file unless you are skilled in the use of
the UNIX vi editor, and have a good working knowledge regarding how crontab
entries are structured. Call Cisco Services if you need help in adding this utility to
the crontab file.
1 If necessary, open an xterm window on the DNCS.
2 Type export EDITOR=vi and then press Enter.
3 Type crontab -e and then press Enter. The crontab file opens for editing using
the UNIX vi editor, and have a good working knowledge regarding how crontab
entries are structured. Call Cisco Services if you need help in adding this utility to
the crontab file.
1 If necessary, open an xterm window on the DNCS.
2 Type export EDITOR=vi and then press Enter.
3 Type crontab -e and then press Enter. The crontab file opens for editing using
the UNIX vi text editor.
4 Append an entry to the crontab file similar to the following example for the
type8helper utility.
Example:
40 2 * * * (. /dvs/dncs/bin/dncsSetup ; /dvs/dncs/bin/delete-sm -o ..OOS..) >
/dvs/dncs/tmp/deprovisioned.out 2>&1
10 3 * * * (. /dvs/dncs/bin/dncsSetup ; /dvs/dncs/bin/type8helper.sh ) > /dev/null
Notes:
Example:
40 2 * * * (. /dvs/dncs/bin/dncsSetup ; /dvs/dncs/bin/delete-sm -o ..OOS..) >
/dvs/dncs/tmp/deprovisioned.out 2>&1
10 3 * * * (. /dvs/dncs/bin/dncsSetup ; /dvs/dncs/bin/type8helper.sh ) > /dev/null
Notes:
In this example, the delete-sm utility executes at 2:40 AM each day. The
type8helper utility then executes at 3:10 AM each day.
type8helper utility then executes at 3:10 AM each day.
The reason the delete-sm utility is coupled with the type8helper utility in the
crontab entry, is so the delete-sm utility will delete all secure_micro row
entries from the database for out-of-service devices. These devices will then
automatically restage (and receive type-8 EMMs) the next time the billing
system transmits a modifyDhctConfiguration transaction. Without the delete-
sm entry, if these devices are suddenly placed back into service, the
type8helper utility might encounter its 500-devices limit the next time it tries
to run from cron.
crontab entry, is so the delete-sm utility will delete all secure_micro row
entries from the database for out-of-service devices. These devices will then
automatically restage (and receive type-8 EMMs) the next time the billing
system transmits a modifyDhctConfiguration transaction. Without the delete-
sm entry, if these devices are suddenly placed back into service, the
type8helper utility might encounter its 500-devices limit the next time it tries
to run from cron.
5 Save the crontab file and close the vi editor.