Addressable Controller System Documentation

DAC 6000
Quick Start Reference Guide
Release V2.97
Copyright © 2004 by Motorola Inc.
All rights reserved.
No part of this publication may be reproduced in any form or by any means or used to make any derivative work (such as
translation, transformation or adaptation) without written permission from Motorola Inc.
Motorola Inc. reserves the right to revise this publication and to make changes in content from time to time without obligation
on the part of Motorola Inc. to provide notification of such revision or change.
Motorola Inc. provides this guide without warranty of any kind, either implied or expressed, including, but not limited, to the
implied warranties of merchantability and fitness for a particular purpose. Motorola Inc. may make improvements or changes
in the product(s) described in this manual at any time.
MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. CableCARD is a trademark of
Cable Television Laboratories, Inc. All other product or service names are the property of their respective owners.
© Motorola, Inc. 2004.
 Contents

Section 1
Introduction
Using This Guide ............................................................................................. 1-1
Notation Conventions .................................................................................... 1-2
In-text Icons ................................................................................................. 1-3
Related Documentation.................................................................................. 1-4
If You Need Help ............................................................................................. 1-5

Section 2
General DAC 6000 Operations
Starting the DAC 6000 Application .................................................................... 2-1
Date/Time Change .......................................................................................... 2-1
System Backup ............................................................................................... 2-2
System Restore ............................................................................................... 2-4

Section 3
Database Maintenance
Command Line Entries ..................................................................................... 3-1

Section 4
Time Zone Management
TIMEZONE File Update ..................................................................................... 4-1
TZ Script Syntax Information ............................................................................. 4-1
Spring Ahead Considerations .......................................................................... 4-4
Fall Back Considerations ................................................................................ 4-4
Set-top Time Changes ...................................................................................... 4-5

i
DAC 6000 Release V2.97 Quick Start Guide „ Addressable Controller System Documentation

Section 5
Billing System
PortServer II Configuration............................................................................... 5-1
Configuration Procedure ................................................................................. 5-1
acc_rename Utility ......................................................................................... 5-2
BSI Expanded Result Codes .............................................................................. 5-6
BSI Port Processing........................................................................................ 5-6
Business System Tunable ............................................................................... 5-6
BSIL_Report .................................................................................................. 5-7
Expanded Result Codes .................................................................................. 5-7

Section 6
Analog Compatibility
Analog PPV Compatibility ................................................................................. 6-1
DAC 6000 Setup ........................................................................................... 6-1
ACC-4000 Setup ........................................................................................... 6-2
Define ACC-4000........................................................................................... 6-2
Defining the Service Provider ...................................................................6-2
Adding the ACC-4000..............................................................................6-2
Define Analog Service .................................................................................... 6-3
Associating the Analog Service to an Analog Device ...................................6-3
Adding a Source .....................................................................................6-3
Adding the Analog Service .......................................................................6-3
Dynamic Encryption Key Management (DEKM) .................................................... 6-4

Section 7
Key Server Operations
Unit Key List Data Save/Restore ....................................................................... 7-1
Encryption Control Center Configuration ............................................................ 7-1
Verifying ecc_config Changes .......................................................................... 7-2
Group Configuration Request/Group Rekey ........................................................ 7-3
Multiple KLS Configuration .............................................................................. 7-6
Adding a Second KLS to the DAC 6000 ............................................................ 7-6
Deleting a KLS............................................................................................... 7-7

ii
 Contents „ DAC 6000 Release V2.97 Quick Start Guide

Section 8
Configuring Multicast Addresses
Converting Multicast 16 Addresses ................................................................... 8-1

Section 9
Emergency Alert System (EAS)
Configuring an EAS Service .............................................................................. 9-1
Editing Emergency Alert Tunables...................................................................... 9-2
Valid Combinations ....................................................................................... 9-4

Section 10
Configuring an IRT Service
System Level Parameters and Verification ........................................................ 10-1
Define Devices .............................................................................................. 10-1
Define Plants................................................................................................ 10-2
Link Devices ................................................................................................. 10-2
Service Setup ............................................................................................... 10-2
Channel Map Definition ................................................................................. 10-3
Define Terminals ........................................................................................... 10-3

Section 11
Configuring an MPS Service
Configuring the MPS Trans-Remux D12 ............................................................ 11-1
Deleting a Route ........................................................................................... 11-6
Re-acquiring ACP Addresses ........................................................................... 11-7

Section 12
Interactive Service Configuration
Interactive Config Message ............................................................................ 12-1
Enabling a Set-top to Use Upstream/Downstream IDs ........................................ 12-1
Authorizing/De-authorizing INTERACT.............................................................. 12-2

iii
DAC 6000 Release V2.97 Quick Start Guide „ Addressable Controller System Documentation

Section 13
Code Download
Object Definition and Code Download Procedure ............................................... 13-1
Presentation Order ....................................................................................... 13-3
Validating the Object Name .......................................................................... 13-3
Copying the Object Files ............................................................................... 13-3
Define Source ............................................................................................. 13-3
Define Background Service ........................................................................... 13-4
Define Software Object ................................................................................. 13-6
Download Software Object to the RADD 6000(s)............................................. 13-8
Assign Software Object................................................................................. 13-8
Verifying and Troubleshooting the Code Download .................................. 13-12
Delete Software Object ............................................................................... 13-13
Verifying Deletion of the Software Object and Code
Download .................................................................................... 13-14
Changing a Software Object Assignment Destination ..................................... 13-14
Decoder Conditional Expressions .................................................................. 13-16
Defining and Assigning a Decoder Conditional Expression .............................. 13-16
Decoder Conditional Expression Terms ......................................................... 13-16
Decoder Conditional Expression Logical Operators ........................................ 13-18

Section 14
RF Polling
Systems with Multiple RADD 6000s ................................................................. 14-1
Poll Retry Count ............................................................................................ 14-1
On-plant/Off-plant Status Designators ............................................................ 14-2
RF Poll Schedule ........................................................................................... 14-2

Section 15
Telco Return
Configuring a PortServer II Using digi_rename .................................................. 15-1
Configuring Telco Return Modems ................................................................... 15-3
Configuring the RADD 6000 for Telco Return..................................................... 15-3
phret Interface Task .............................................................................. 15-3
Setting the Dial Time Interval ................................................................. 15-5

iv
 Contents „ DAC 6000 Release V2.97 Quick Start Guide

Section 16
Adding RADD 6000s
Prerequisites ................................................................................................ 16-1
Multiple Plants, Single OM 1000, New RADD 6000 ............................................ 16-2
Configuration .............................................................................................. 16-2
Switchover to the New RADD 6000 ............................................................... 16-2
Configure the Code Download ....................................................................... 16-4
Complete the Configuration Setup ................................................................. 16-4
Single Plant, Single OM 1000, New RADD 6000 ................................................. 16-5
Configuration .............................................................................................. 16-5
Switchover to the New RADD 6000 ............................................................... 16-5
Complete the Configuration Setup ................................................................. 16-7

Section 17
RADD 6000 Failover
RADD 6000 Replacement Procedure ................................................................ 17-1
Replacement Procedure ............................................................................... 17-1
Defining and Verifying Each Separate RADD 6000 Operation ........................... 17-2
Implementing Each Table Item ............................................................... 17-4

Section 18
Troubleshooting
DAC 6000-to-RADD 6000 Communication ......................................................... 18-1
Digital Set-tops Not Responding ..................................................................... 18-2
Digital Set-tops Dropping Messages ................................................................ 18-2
Cannot Communicate with One-way Digital Set-tops .......................................... 18-3
Digital Set-top Virtual Channel Map Problems................................................... 18-4
Code Download ............................................................................................. 18-4

Abbreviations and Acronyms

v
 Section 1
Introduction

This document provides commonly used procedures, such as change

time/date, database backup/restore, PortServer II configuration, etc. that
are implemented from the DAC 6000 console.

Using This Guide

This guide provides specific DAC 6000 software procedures. You will
find the following information in this guide:
Section 1 Introduction contains introductory information about the DAC 6000 software,
conventions used in this guide and instructions for calling the Technical
Response Center (TRC).
Section 2 General DAC 6000 Operations contains procedures to start the DAC 6000
application, change the time/date, and backup/restore the system.
Section 3 Database Maintenance contains scripts to initiate a database backup, to
restore backed-up database information and other maintenance functions
such as disaster recovery.
Section 4 Time Zone Management contains scripts to set the time zone.
Section 5 Billing System contains the PortServer II configuration procedure, the
Business System Interface (BSI) expanded error code set, and information to
configure multiple business systems.
Section 6 Analog Compatibility contains the DAC 6000-ACC 4000 Pay-Per-View (PPV)
setup procedures and the Dynamic Encryption Key Management description.
Section 7 Key Server Operations contains instructions to load Unit Key List (UKL) files,
configure connection to the Encryption Control Center, initiate a Group
Configuration Request (GCR), and a procedure to add a second Key List Server
(KLS).
Section 8 Multicast Addresses contains the procedure to set up a Multicast Address.
Section 9 Emergency Alert System (EAS) describes methods to force a DCT*/DVi* to
tune to a specific emergency channel.
Section 10 Configuring an IRT Service provides the procedural steps to implement a
service on the IRT 1000/2000.
Section 11 Configuring an MPS Service contains procedures to install and configure the
Trans-Remux D12 device.

1-1
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Section 12 Interactive Service Configuration contains procedure to define the INTERACT

resource.
Section 13 Code Download contains the code download procedure, decoder conditional
expression operands, and decoder conditional logical operators.
Section 14 RF Polling provides an RF polling schedule for the system.
Section 15 Telco Return contains procedures and scripts associated with modem
configuration, port/protocol, and timing/retry settings.
Section 16 Adding RADD 6000s contains prerequisites and procedures to add a
RADD 6000 to single and multiple plants.
Section 17 RADD 6000 Failover contains the RADD 6000 replacement procedure.
Section 18 Troubleshooting contains procedures to help isolate DAC 6000/RADD 6000
failures.
Abbreviations and The Abbreviations and Acronyms list contains the full spelling of the short
Acronyms forms used in this guide.

Notation Conventions
Before you begin working with the DAC 6000, familiarize yourself with
the following notation conventions:

Convention Example What It Means

Bold type Y or N Text you must type exactly as it appears. Type
T0D1507116AK commands and filenames exactly as they
grep appear in the instructions. This is necessary
because UNIX® is case-sensitive; for example,
“c” is not the same as “C.”
Also used to identify a click field or button.
Italic type filename A displayed variable or a variable on a window
xxx that indicates information that you must type.
Do not turn off. Also used for emphasis.
SMALL CAPS ENTER, F6 Keys you press on the keyboard.
DC POWER Denotes silk screening on equipment.
Courier font Are you sure? Text displayed on a window.
Processing...
KEY + KEY CTRL + X Key combinations indicating that you hold
ALT + 6 down the first key and then press the second
key

1-2
 Using This Guide DAC 6000 Release V2.97 Quick Start Guide

Convention Example What It Means

KEY, KEY ALT, 2 Key combinations indicating that you press the
first key, release it, and then press the second
key.
> Access the Define Digital Points to the next major window invoked in the
Service window with: navigation path.
DAC 6000 Main Menu >
Manage Services > Define
Digital Service.
* (asterisk) DCT* or DVi* Indicates that several versions of the same
model number exist and the information
applies to all models. When the information
applies to a specific model, the complete
model number is given.
<descriptor> Type the <file name> . . . Descriptor target when keyboarding input. It is
not the specific data typed, but a description of
it.
Type ukl_dump Indicates press ENTER after command line entry.

In-text Icons
In addition to the document style conventions, you may see in-text icons,
which indicate the following:
The procedure or actions described can result in a significant system problem if
performed incorrectly.

Contact the Technical Response Center (TRC) personnel.

Only Motorola personnel are permitted to perform this operation.

1-3
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Related Documentation
Other applicable system documentation is:
DAC 6000 Configuration Guide Release V2.97
DAC 6000 Operation Guide Release V2.97
DAC 6000 System Guide Release V2.97
RADD 6000 v1.3.x Installation and Operation Manual
HCT 1000 Headend Configuration Tool User Guide
Message Editor 1000 User Guide
SEM Software Version 1.0 Installation and Operation Manual
SEM v4 Version 4.x.x Installation and Operation Manual
SEM v8 Version 4.x.x Installation and Operation Manual
OM 1000 Out-of-band Modulator Installation and Operation Manual
IM 1000 In-band Modulator Installation and Operation Manual
IRT 1000 (or IRT 2000) Integrated Receiver Transcoder Installation
and Operation Manual
MPS Modular Processing System Mainframe Installation &
Operation Manual
C8U-L C8U-H Commander 8 Upconverter Installation Manual
C6U Commander 6 Upconverter Installation Manual
RPD 1000 Return Path Demodulator Installation and Operation
Manual
RPD 2000 Return Path Demodulator Installation and Operation
Manual
ADM 1000 Add/Drop Multiplexer Installation and Operation
Manual
KLS 1000 Key List Server Installation and Operation Manual

1-4
 If You Need Help DAC 6000 Release V2.97 Quick Start Guide

If You Need Help

If you need assistance while working with the DAC 6000

application, contact the Motorola Technical Response Center (TRC):
Inside the U.S.: 1-888-944-HELP (1-888-944-4357)
Outside the U.S.: 215-323-0044
Online: http://broadband.motorola.com/noflash/websupport.html.
The TRC is open from 8:00 AM to 7:00 PM Eastern Time, Monday
through Friday and 10:00 AM to 5:00 PM Eastern Time, Saturday.
When the TRC is closed, emergency service only is available on a
call-back basis. Web Support offers a searchable solutions database,
technical documentation, and low priority issue creation/tracking
24 hours per day, 7 days per week.

1-5
 Section 2
General DAC 6000 Operations

This section provides frequently used procedures for the DAC 6000
system.

Starting the DAC 6000 Application

The DAC 6000 code uses shared memory; therefore, it can be started
warm or cold as follows:
At the system window UNIX prompt, type start_acc or
start_acc –warm to start the DAC 6000 application with the shared
memory data.
At the system window UNIX prompt, type start_acc –cold to start
the DAC 6000 application without the shared memory initialized.

Date/Time Change
To change the date/time on the DAC 6000:
1 Stop the application by typing stop_acc on the xterm window.
2 Log in as root.
3 Type init 6 to shutdown and reboot.
4 Within eight seconds, at the following boot prompt:
SCO OpenServer™ Release 5
Press .
5 The system continues booting. Press CTRL + d at the following
prompt:
Type CONTROL-d to proceed with normal setup (or give
root password for system maintenance): CTRL + d
The system continues booting and prompts for the new time.
6 Type the new date/time <[YYMMDD]hhmm[ss]> .

2-1
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

System Backup
Multiple tapes may be required to backup a system. If prompted for an
additional tape, remove the current tape, insert a new tape, wait for tape
drive activity to stop, and then press to continue. Label all tapes
during the backup to avoid problems during the restore process.
To perform a DAC 6000 full system backup:
1 Back up the Unit Key List (UKL) to tape by typing ukl_dump if
there is no current backup.
2 Back up the database to tape by typing db_dump if there is no
current backup.
3 Shut down the billing system.
4 Insert a tape in the tape drive.
5 Initiate a system backup with:
DAC 6000 Main Menu > Manage Controller > Manage System >
Backup System > Full System Backup Window.
Type the <root password> .

The application is stopped and Sybase is shut down.

6 When the backup is complete, type init 6 to restart the system.
A typical multiple tape backup is as follows:
Terminal type is xterm
running stop_acc2
stop_acc2
running labk_test
calling kill_acc
Initiating Application Shutdown
Application Shutdown In Progress
Application Shutdown In Progress
Application Shutdown In Progress
Application Shutdown In Progress
Application Shutdown In Progress
Application Shutdown In Progress
Application Shutdown In Progress
Application Shutdown In Progress
Application Shutdown In Progress
Application Shutdown Complete - Shutting Down Logger & Message Clearing House
Logger & Message Clearing House Shutdown Complete
Remaining Processes:

UID PID PPID C STIME TTY TIME CMD

acc4000d 1304 1295 0 09:33:58 ttyp3 00:00:00 -csh -c /home/acc4000d/scripts/stop_acc
acc4000d 1326 1304 1 09:34:02 ttyp3 00:00:00 /home/acc4000d/scripts/stop_acc
acc4000d 876 1 0 09:25:01 ? 00:00:00 -csh -c startx -- -crt /dev/tty02 :0.0
acc4000d 899 876 0 09:25:02 ? 00:00:00 /bin/sh /usr/bin/startx -- -crt

2-2
 System Backup DAC 6000 Release V2.97 Quick Start Guide

/dev/tty02 :0.0
acc4000d 901 899 0 09:25:03 ? 00:00:00 xinit /bin/sh /home/acc4000d/
.startxrc -- -crt /dev/tty02 :0.0
acc4000d 902 901 2 09:25:03 pts000 00:00:12 X :0 -crt /dev/tty02 :0.0
acc4000d 910 902 0 09:25:05 pts000 00:00:00 vbiosd 8
acc4000d 917 901 0 09:25:07 ? 00:00:01 mwm
acc4000d 921 917 0 09:25:07 ? 00:00:00 xclock -title DAC 6000 -geometry -1-1
acc4000d 954 1 0 09:25:13 ? 00:00:00 /usr/bin/X11/xterm -bg LightSkyBlue
-geometry 132x20+0+0 -display patty:0.0 -tn
acc4000d 1173 979 0 09:25:28 ttyp0 00:00:00 mchtask
acc4000d 1175 979 0 09:25:30 ttyp0 00:00:01 log_task /home/acc4000d/data/op_log_file
/home/acc4000d/data/dev_log_file M 7
acc4000d 1177 979 0 09:25:32 ttyp0 00:00:00 xerrtask -dpatty:0.0 -rs -l0xC4200000 -
l0xC4100000
acc4000d 1350 1326 6 09:36:25 ttyp3 00:00:00 ps -fu acc4000d
acc4000d 979 954 0 09:25:15 ttyp0 00:00:00 ./start_acc2
acc4000d 1260 1258 0 09:30:57 ttyp1 00:00:00 csh
acc4000d 1258 1 0 09:30:57 ? 00:00:00 xterm -geometry 132x24 -sb -sl 1000
-fn -adobe-courier-bold-r-normal--12-120-75
acc4000d 1285 1278 0 09:33:48 ? 00:00:00 xterm -geometry 132x24 -fn 6x13 -e
/usr/gi/bin/sys_backup
acc4000d 1278 1 0 09:33:48 ttyp0 00:00:00 csh -c xterm -geometry 132x24
-fn 6x13 -e /usr/gi/bin/sys_backup
acc4000d 1286 1285 0 09:33:49 ttyp2 00:00:00 /usr/gi/bin/sys_backup
acc4000d 1287 1286 0 09:33:49 ttyp2 00:00:00 xterm -geometry 132x50+0+0
-sb -sl 1000 -tn vt100 -fn -adobe-courier-bold-r-nor
acc4000d 1288 1287 0 09:33:50 ttyp3 00:00:00 /usr/gi/bin/sys_backup wysiwyg
acc4000d 1345 1332 0 09:34:03 ttyp3 00:00:00 sleep 180
acc4000d 1330 1 0 09:34:02 ttyp3 00:00:00 /home/acc4000d/bin/doubleFork
/home/acc4000d/scripts/stop_acc2
acc4000d 1331 1330 0 09:34:02 ttyp3 00:00:00 sh -c /home/acc4000d/scripts/stop_acc2
acc4000d 1332 1331 0 09:34:02 ttyp3 00:00:00 /home/acc4000d/scripts/stop_acc2
Remaining Shared Memory:
m 1 0xcd2a04b1 --rw------- sybase acc4000

******************** Shutting down SYBASE ********************

******************** Shutting down SYBASE ********************

********************* Shutting down SYBASE *********************

********************* Purging log files *********************

************************* MAKING SYSTEM BACKUP *************************

Touching file /home/acc4000d/temp/dosysbackup

Rewinding tape ...

Complete system backup started at Wed Mar 10 09:36:43 EST 1999

/home/acc4000d/temp/budate
10 blocks

Building backup list ...

Backing up Unix files ...Reached end of medium on output.
Device /dev/nrStp0: Insert a new tape. Wait until the tape drive stops. Then, press
<Enter> to go on ...

2-3
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Backing up SYBASE files ...

opt/K/SCO/Unix/5.0.4Eb/lib/scohelp/OSAdminG/buC.blocksize.html.Z
1092476 blocks
125640 blocks

------------ SA1sysbkp Finish ------------------------------------------

End Time: Wed Mar 10 10:53:12 EST 1999

You must do an init 6 to restart the DAC 6000 System.

Press <Enter> to continue

System Restore
When restoring, the hardware must be the same: Proliant with
PortServer II to Proliant with PortServer II, not Proliant with
PortServer II to Proliant with Corollary.
To perform a DAC 6000 full system restore:
1 Insert the appropriate DAC 6000 SCO boot disk into the floppy drive
(Compaq Proliant 5500).
2 Insert the system backup tape into the tape drive.
3 Reboot the system by pressing the STANDBY button.
4 When prompted, insert the DAC 6000 SCO Install disk.
5 When prompted, press to shutdown the UNIX operating system.
6 If multiple tapes were prepared during system backup, insert the
additional tapes when prompted.
7 When prompted to Power-Off or Press Any Key:
Remove the tape from tape drive and disk from floppy drive.

If the install disk is not removed within 10 minutes, the

system will automatically reboot and fail because the install disk
is not bootable.
Reboot the system by toggling the STANDBY button. The system
will reboot several times.
If the reboot does not complete, toggle the STANDBY button
again.
8 Stop the application.
9 Insert the database backup tape.

2-4
 System Restore DAC 6000 Release V2.97 Quick Start Guide

10 Start the restore by typing db_restore .

11 Start the application.

12 Insert the UKL backup tape.

13 Start the restore by typing ukl_restore .

2-5
 Section 3
Database Maintenance

Command Line Entries

Type the following command line entries for database utilities to
enable/disable nightly backups, to restore backed-up database
information, or for other maintenance purposes, as described below:

/home/acc4000d/scripts/bucron_start
This utility enables automatic nightly backup of the DAC 6000 database.
The backup is to the tape if one is inserted in the tape drive; otherwise,
it is to disk.

/home/acc4000d/scripts/bucron_stop
This utility disables nightly backup of the DAC 6000 database.

/home/acc4000d/scripts/db_dump
The application can be running when this utility is implemented. It
saves the database to the acc4000dump disk file and then copies it to
tape if one is inserted in the tape drive. The nightly backup cron job calls
this script.

/home/acc4000d/scripts/db_restore
The application must not be running and ISQL sessions must not be
open when this utility is implemented.
This utility restores from tape to the acc4000dump disk file and then
loads the database. If the database versions do not match, the following
message is displayed:
Unable to match database versions! Continue (y/n):

/home/acc4000d/scripts/db_recovery
The application must not be running and ISQL sessions must not be
open when this utility is implemented. Also, the user must be root.
This utility is used for disaster recovery to restore the complete database
from tape. If the database versions do not match, the following message
is displayed:
Unable to match database versions! Continue (y/n):

3-1
DAC 6000 Release V2.97 Quick Start Guide „ Addressable Controller System Documentation

/home/acc4000d/scripts/sybase/savedb <full path file_name>

(for example, savedb /tmp/my_test_db)
The application can be running when this utility is implemented. It
saves the database to the acc4000dump disk file and then moves it to a
specified disk file name. This script saves only the database data.

/home/acc4000d/scripts/sybase/restoredb <full path file_name>

(full path name is optional)
The application must not be running and ISQL sessions must not be
open when this utility is implemented.
This utility restores the last or named disk file dump of the database by
first moving the user specified file name to the acc4000dump disk file
and then loading the database.

/home/acc4000d/scripts/dbupstat
The application can be running when this utility is implemented.
It updates the statistics on the DAC 6000 database tables, which
improves Sybase’s ability to choose the best query technique for the
tables.

/home/acc4000d/scripts/upstat_cron_start
This utility enables automatic daily execution of the dbupstat script.
Each execution of this script replaces the previous one. Only one
dbupstat time can be scheduled for execution using upstat_cron_start.

/home/acc4000d/scripts/upstat_cron_stop
This utility disables the automatic daily execution of the dbupstat script.

/home/acc4000d/scripts/db_maintenance_script <num>
(where num is a value between 1 and 5; 1 specifies the minimal set of
most likely fragmented tables and 5 specifies the full set of tables with
indexes)

FAILURE TO STOP THIS APPLICATION WILL CORRUPT

THE DATABASE!
The application must not be running, as the database can be
corrupted. Also, ISQL sessions must not be open when this utility is
implemented.
This utility removes and rebuilds the indexes in the tables for
fragmentation cleanup. The db_maintenance_script utility records its
output to the maintlog file located in /home/acc4000d/data.

3-2
 Section 4
Time Zone Management

In the DAC 6000, the SCO UNIX environment variable TIMEZONE (TZ)
is used to control output formatting and the input parsing of date/time
information. The TZ variable affects the system clock display, the PPV
program input times, and PPV program display times.
The TZ variable is also used to specify the start and end times of
Daylight Savings Time (DST) each year, regardless of the date the
transition occurs, as it can be made to mimic the first Sunday in April
and last Sunday in October. In addition, the TZ string can be modified to
accommodate DST differences for locations other than the United States.

TIMEZONE File Update

The TZ variable is set by commands in the TIMEZONE file located in
the etc subdirectory (/etc/TIMEZONE). To update this file:
Stop the DAC 6000 application software.
Modify the /etc/TIMEZONE file with an ASCII editor.
Reboot the system to make the changes take affect.

At installation time, the /etc/TIMEZONE file should be modified to

contain the correct TZ setting for the DAC 6000 time zone/DST. The
system should also be rebooted before downloading the event for April;
otherwise, the April events will have incorrect start/end times.

TZ Script Syntax Information

The syntax for the TZ script specifies the following information:
Base Time Zone Hours Offset from Alternate Time Spring Ahead Fall Back
Name GMT Zone Name Date/Time Rule Date/Time Rule
(Required) (Required) (Optional) (Optional) (Optional)
EST, CST, MST, 5,4,3,2,1,0, −1, EDT, CDT, etc. First Sunday of Last Sunday of
PST, etc. −2,−3, etc. specified month specified month
and time. and time.

Do not deviate from the base and alternate time zone names (for
example, EST/EDT) currently running on the DAC 6000 application.

4-1
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

If the TZ script contains only the required fields (Base Time Zone
Name and Hours Offset from GMT), DST adjustments are not
performed.
If the TZ script contains the required fields (Base Time Zone Name
and Hours Offset from GMT) as well as the Alternate Time Zone
Name, DST is performed in accordance with US guidelines (Spring
Forward is 2 AM on the 1st Sunday of April, and Fall Back is 2 AM
on the last Sunday of October).
TZ Script Examples
Eastern Standard Time switching at 4:00 AM:
TZ=“EST5EDT,M4.1.0/04:00, M10.5.0/04:00”
Base Time Zone Hours Offset from Alternate Time Spring Ahead Fall Back
Name GMT Zone Name Date/Time Rule Date/Time Rule
(Required) (Required) (Optional) (Optional) (Optional)
“EST 5 EDT, M4.1.0/04:00, M10.5.0/04:00”
Eastern Standard Five hours after Eastern Daylight *Spring ahead *Fall back occurs
Time. GMT. Time. occurs on the first on the last
Sunday (1) of the Sunday (5) of the
fourth month tenth month
(April) at 4:00 (October) at 4:00
AM. AM. The last
Sunday is
specified with a 5
even if there are
only four weeks
in the month.

*The operating system ascertains the exact dates for spring ahead and
fall back from the parameters given. Also, 4:00 AM is a typical switch
over time with most pay service providers.

Central Standard Time, switching at 3:00 AM:

TZ=“CST6CDT,M4.1.0/03:00, M10.5.0/03:00”
Base Time Zone Hours Offset from Alternate Time Spring Ahead Fall Back
Name GMT Zone Name Date/Time Rule Date/Time Rule
(Required) (Required) (Optional) (Optional) (Optional)
“CST 6 CDT, M4.1.0/03:00, M10.5.0/03:00”
Central Standard Six hours after Central Daylight Spring ahead Fall back occurs
Time. GMT. Time. occurs on the first on the last
Sunday (1) of the Sunday (5) of the
fourth month tenth month
(April) at 3:00 (October) at 3:00
AM. AM.

4-2
TZ Script Syntax Information DAC 6000 Release V2.97 Quick Start Guide

Mountain Standard Time, switching at 5:00 AM:

TZ=“MST7MDT,M4.1.0/05:00, M10.5.0/05:00”
Base Time Zone Hours Offset from Alternate Time Spring Ahead Fall Back
Name GMT Zone Name Date/Time Rule Date/Time Rule
(Required) (Required) (Optional) (Optional) (Optional)
“MST 7 MDT, M4.1.0/05:00, M10.5.0/05:00”
Mountain Seven hours after Mountain Spring ahead Fall back occurs
Standard Time. GMT. Daylight Time. occurs on the first on the last
Sunday (1) of the Sunday (5) of the
fourth month tenth month
(April) at 5:00 (October) at 5:00
AM. AM.

Pacific Standard Time, switching at 2:00 AM standard:

TZ=“PST8PDT”
Base Time Zone Hours Offset from Alternate Time Spring Ahead Fall Back
Name GMT Zone Name Date/Time Rule Date/Time Rule
(Required) (Required) (Optional) (Optional) (Optional)
“PST 8 PDT, No parameters; use standard US
guidelines.
Pacific Standard Eight hours after Pacific Daylight Spring ahead Fall back occurs
Time. GMT. Time. occurs on the first on the last
Sunday of April at Sunday of the
2:00 AM. October at 2:00
AM.

Saudi Standard Time, switching at 3:00 AM:

TZ=“SST-3SDT,M4.1.0/03:00, M10.5.0/03:00”
Base Time Zone Hours Offset from Alternate Time Spring Ahead Fall Back
Name GMT Zone Name Date/Time Rule Date/Time Rule
(Required) (Required) (Optional) (Optional) (Optional)
“SST −3 SDT, M4.1.0/03:00, M10.5.0/03:00”
Saudi Standard Three hours Saudi Daylight Spring ahead Fall back occurs
Time. before GMT. Time. occurs on the first on the last
Sunday (1) of the Sunday (5) of the
fourth month tenth month
(April) at 3:00 (October) at 3:00
AM. AM.

4-3
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Saudi Standard Time, no daylight savings time:

TZ=“SST-3”
Base Time Zone Hours Offset from Alternate Time Spring Ahead Fall Back
Name GMT Zone Name Date/Time Rule Date/Time Rule
(Required) (Required) (Optional) (Optional) (Optional)
“SST −3” TZ contains only required fields; therefore, DST adjustments
are not performed.
Saudi Standard Three hours
Time. before GMT.

Spring Ahead Considerations

Most analog cable systems perform the time change at 4:00 AM,
consonant with PPV provider time changes. This time is usually less
intrusive than the standard 2:00 AM time change. The hour of the time
change is an invalid period for PPV program start times. For example, if
the TZ Spring Ahead variable is configured to perform a system seasonal
time change at 4:00 AM, the system clock goes from 3:59:59 to 5:00:00.
PPV program start times of 4:00 AM, 4:30 AM, etc., are invalid, as they
will probably cause program overlap errors. If a two hour program starts
at 2:00 AM, the next program should be given a start time of 5:00 AM to
avoid a program overlap error.

Fall Back Considerations

In the fall, there is a two hour invalid time window. For example, if the
TZ Fall Back variable is configured to perform a system seasonal time
change at 4:00 AM, the system clock goes from 3:59:59 to 3:00:00 and
counts back up to 03:59:59 again. The two hour window includes the
original 3:00:00 to 3:59:59 interval and the repeat 3:00:00 to 3:59:59
interval to set the clock back an hour. Therefore, PPV program start
times of 3:00 AM, 3:30 AM, etc., are invalid, as they will probably cause
program overlap errors. Programs must not have a start time from
3:00:00 to 3:59:59 AM because the correct 3:00:00 instance of the hour
(original 3:00:00 or repeat) cannot be resolved by the system.

4-4
 Set-top Time Changes DAC 6000 Release V2.97 Quick Start Guide

Set-top Time Changes

The actual DAC 6000 time zone change occurs using the time settings in
the TX script. The set-tops will be commanded to change their clocks at
2:00 AM on the day specified by the TZ script. The set-tops receive the
new daylight savings entry and exit times from the DAC 6000 whenever
they are refreshed or initialized.
A global time zone configuration refresh can also be configured from the
DAC 6000 with:
DAC 6000 Main Menu > Manage Operations > Define Operations.
1 Click Operation Type; invokes the Zoom: Operation Type window.
2 Scroll to and highlight Refresh and click Accept.
3 On the Define Operations window, click Add; invokes the Edit
Refresh Operation window.
4 In the Operation Information panel, type the Operation Name (for
example, DST_east).
5 In the Operation Attributes panel, type the Start Time.
6 Type the End Time.
7 Type a value of 250 (for 250 msec) in Delay Between Terminals.
8 In the Criteria panel, select All Terminals (filled), if not targeting a
single terminal or a range of terminals.
9 In the Configure Messages panel, select Time Zone (filled).
10 Click Accept.

This refresh operation should be run several times before the DST
change to ensure every set-top has the new settings.

To monitor the refresh operation, access the Control Operations window

with:
DAC 6000 Main Menu > Manage Operations > Control Operations.
1 In the Select Operation Information panel, click All (filled) for the
RADD Name field and click All (filled) for the OM Name field.
2 In the Status Filter panel, click All Statuses (filled).
3 In the Type Filter panel, click Refresh (filled); ensure all other
buttons in the panel are clicked off (hollow).

4-5
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

4 Click Accept.
5 In the Database Operation panel, click Select to activate the
Operations panel.
6 In the Operations panel, scroll to and highlight the <Operation
Name row>.
7 In the Operation Control Options panel, as determined by the
buttons that are active for the selected operation, you can:
Cancel the operation
Pause and resume it
Retrieve status
Display Statistics
Invoke the Display Detail Operations window (this window
shows the status of each RADD 6000 if all RADD 6000s were
chosen)
Retry the operation

4-6
 S e cti o n 5
Billing System

The billing system requires a configured PortServer II for

communication with the DAC 6000, which it does through WireLink
commands. Errors encountered by the billing system are reported to the
DAC 6000 as result codes.

PortServer II Configuration
Although the PortServer II can be configured to run on any of the
Network Interface Cards (NIC 1 through NIC 3), NIC 3 should be used
to keep additional network traffic off the headend networks. The
PortServer II hardware kit includes a crossover cable for direct
connection to NIC 3 and a standard patch cable for connection to a pre-
existing hub on NIC 3.

It is strongly recommended to use NIC 2 as the private network for

KLS connection(s) and NIC 3 for the PortServer II connection.
The individual ports on the PortServer II are designated as ttya1
through ttya16. Up to 3 expansion PortServer IIs can be added to
support 64 ports maximum (ttya1-16, ttya17-32, ttya33-48, and
ttya49-64). During the DAC 6000 boot-up, both port 1 on the
PortServer II (ttya1) and COM1 on the DAC 6000 (tty1a) are tested for
the diagnostic modem. It is recommended the diagnostic modem be
connected to tty1a (COM1) in case of a PortServer II failure. For this
modem connection, the ECC configuration must be updated by running
ecc_config located in /home/acc4000d/scripts.
When running acc_rename or digi_rename, up to 15 PortServer IIs may
now be configured (each of the 15 may have up to 3 expansion boxes).
The local device/port names are designated as ttya1-64 through ttyo1-64
for PortServer IIs 1 through 15, respectively.

Configuration Procedure
To install and configure the PortServer II:
1 Ensure the Corollary MUX board is removed from the DAC 6000
before the release tape is installed.
2 Connect the power cable to the PortServer II.

5-1
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

3 Connect the PortServer II directly either to NIC 3 or the hub on

NIC 3 using the appropriate cable. (If using a PortServer rather than
a PortServer II, set the Ethernet switch on the side of the unit to
twisted pair.)
4 Run the acc_rename utility (below) to configure the DAC 6000 and
PortServer II after the release installation and application startup.

acc_rename Utility
The acc_rename utility is used to modify the DAC 6000’s network cards
and related files. It also automatically configures the SQL server name
and related files. The latest version of acc_rename includes the same
functionality that acc_rename upgrade previously performed. You can
use acc_rename to configure up to 15 PortServers, each with up to three
expansion units. You can invoke acc_rename when the DAC 6000
application is running.

You can run the acc_rename script from any directory; however, do
not run it in the background.
To implement acc_rename:
1 Type acc_rename from a 132 window (shuts down the DAC 6000
application and Sybase).
2 When acc_rename is completed, log in as root.
3 Type init 6 to reboot (the DAC 6000 application starts up
automatically).
A sample output of acc_rename follows:
**************************************************************************************
WARNING: Super user password must be entered to rename the system.
**************************************************************************************
Password:

Terminal type is xterm

running stop_acc2
stop_acc2
running labk_test
calling kill_acc
Initiating Application Shutdown
Application Shutdown In Progress
Application Shutdown In Progress
Application Shutdown In Progress
Application Shutdown In Progress
Application Shutdown In Progress
Application Shutdown In Progress
Application Shutdown In Progress

5-2
 PortServer II Configuration DAC 6000 Release V2.97 Quick Start Guide

Application Shutdown In Progress

Application Shutdown In Progress
Application Shutdown Complete - Shutting Down Logger & Message Clearing House
Logger & Message Clearing House Shutdown Complete
Remaining Processes:
UID PID PPID C STIME TTY TIME CMD
acc4000d 1636 1627 0 09:14:53 ttyp3 00:00:00 -csh -c
/home/acc4000d/scripts/stop_acc
acc4000d 1658 1636 3 09:14:57 ttyp3 00:00:00 /home/acc4000d/scripts/stop_acc
acc4000d 879 1 0 17:01:03 ? 00:00:00 -csh -c startx -- -crt /dev/tty02
:0.0
acc4000d 904 902 0 17:01:05 ? 00:00:00 xinit /bin/sh
/home/acc4000d/.startxrc -- -crt /dev/tty02 :0.0
acc4000d 902 879 0 17:01:05 ? 00:00:00 /bin/sh /usr/bin/startx -- -crt
/dev/tty02 :0.0
acc4000d 905 904 12 17:01:05 pts000 13:57:19 X :0 -crt /dev/tty02 :0.0
acc4000d 913 905 0 17:01:07 pts000 00:00:00 vbiosd 8
acc4000d 920 904 0 17:01:09 ? 00:00:03 mwm
acc4000d 924 920 0 17:01:09 ? 00:00:00 xclock -title DAC 6000 -geometry -
1-1
acc4000d 927 920 0 - - 00:00:00 <defunct>
acc4000d 952 1 0 17:01:13 ? 00:00:00 /usr/bin/X11/xterm -bg
LightSkyBlue -geometry 132x20+0+0 -display dac6000:0.0 -
acc4000d 994 952 0 17:01:16 ttyp0 00:00:00 ./start_acc2
acc4000d 1175 994 0 17:01:31 ttyp0 00:00:00 xerrtask -ddac6000:0.0 -rs -
l0xC4200000 -l0xC4100000
acc4000d 1678 1658 1 09:17:21 ttyp3 00:00:00 ps -fu acc4000d
acc4000d 1217 1210 0 17:05:15 ? 00:00:00 xterm -geometry 132x24 -fn 6x13
acc4000d 1210 1 0 17:05:15 ttyp0 00:00:00 csh -c xterm -geometry 132x24 -fn
6x13
acc4000d 1218 1217 0 17:05:16 ttyp1 00:00:00 csh
acc4000d 1602 1218 0 09:14:13 ttyp1 00:00:00 vi curt
acc4000d 1611 1604 0 09:14:30 ? 00:00:00 xterm -geometry 132x24 -fn 6x13
acc4000d 1604 1 0 09:14:30 ttyp0 00:00:00 csh -c xterm -geometry 132x24 -fn
6x13
acc4000d 1612 1611 0 09:14:30 ttyp2 00:00:00 csh
acc4000d 1676 1664 0 09:14:58 ttyp3 00:00:00 sleep 180
acc4000d 1662 1 0 09:14:57 ttyp3 00:00:00 /home/acc4000d/bin/doubleFork
/home/acc4000d/scripts/stop_acc2
acc4000d 1663 1662 0 09:14:57 ttyp3 00:00:00 sh -c
/home/acc4000d/scripts/stop_acc2
acc4000d 1664 1663 0 09:14:57 ttyp3 00:00:00 /home/acc4000d/scripts/stop_acc2
Remaining Shared Memory:
m 1 0xcd2a045d --rw------- sybase acc4000
******************** Shutting down SYBASE ********************

********************* Shutting down SYBASE *********************

********************* Purging log files *********************

*************************************
DAC 6000 RENAME
/usr/gi/bin/acc_rename
*************************************

################################ Version 5.0.0 ################################

WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING

This program allows for the reconfiguration of the DAC 6000 Controller.
The following parameters can be changed using this program: HOSTNAME,

5-3
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

IP ADDRESS, NETWORK MASK and DEFAULT GATEWAY for any of the network adapters
installed in the DAC 6000 controller. If you do not know all of the
parameters needed to run this program please seek assistance.

**************** CURRENT CONTROLLER NAME is dac6000 ******************

#################################################################################

Enter c to continue or e to exit:

Network Card Count: 3 Controller Type: digital
Enter new HOSTNAME for card number 1 [dac6000]: (default data given)
Enter new HOSTNAME for card number 2 [netcard2]:
Enter new HOSTNAME for card number 3 [netcard3]:
Enter new IP ADDRESS for card number 1 [193.1.6.10]:
Enter new IP ADDRESS for card number 2 [193.1.7.10]:
Enter new IP ADDRESS for card number 3 [193.1.8.10]:
Enter new NETWORK MASK for card number 1 [255.255.255.0]:
Enter new NETWORK MASK for card number 2 [255.255.255.0]:
Enter new NETWORK MASK for card number 3 [255.255.255.0]:
Enter new BROADCAST ADDRESS for card number 1 [193.1.6.255]:
Enter new BROADCAST ADDRESS for card number 2 [193.1.7.255]:
Enter new BROADCAST ADDRESS for card number 3 [193.1.8.255]:
Enter new default Gateway IP address [0]:
The following information will be used to rename the DAC 6000 Controller:

CARD # HOSTNAME IP ADDRESS NETMASK BROADCAST ADDRESS ROUTER INFO DRIVER

NAME
------ -------- ---------- ------------- ----------------- ------------ ----------
-
1 dac6000 193.1.6.10 255.255.255.0 193.1.6.255 0 net0
2 netcard2 193.1.7.10 255.255.255.0 193.1.7.255 net1
3 netcard3 193.1.8.10 255.255.255.0 193.1.8.255 net2

SQL SERVER NAME: dac6000SQL BACKUP SQL SERVER NAME: SYB_BACKUP

Enter c to continue or e to exit:

Finished Processing networks.info File
Removing old host names
Removing net chains
<dac6000 193.1.6.10 255.255.255.0 193.1.6.255 netcard2 193.1.6.11 255.255.255.0
193.1.6.255 netcard3 193.1.6.12 255.255.255.0 193.1.6.255>
</gi/5.0.4d/bin/netscript: dac6000 193.1.6.10 255.255.255.0 193.1.6.255 netcard2
193.1.6.11 255.255.255.0 193.1.6.255 netcard3 193.1.6.12
255.255.255.0 193.1.6.255 >
Testing PCI Network Cards in Digital HX System
/gi/5.0.4d/bin/netscript: Digital DE450 found in slot #4.
/gi/5.0.4d/bin/netscript: adding <dac6000 193.1.6.10 255.255.255.0 193.1.6.255>
Removing old host names
/gi/5.0.4d/bin/netscript: Digital DE450 found in slot #5.
/gi/5.0.4d/bin/netscript: adding <netcard2 193.1.6.11 255.255.255.0 193.1.6.255>
Removing old host names
/gi/5.0.4d/bin/netscript: Digital DE450 found in slot #6.
/gi/5.0.4d/bin/netscript: adding <netcard3 193.1.6.12 255.255.255.0 193.1.6.255>

5-4
 PortServer II Configuration DAC 6000 Release V2.97 Quick Start Guide

Removing old host names

***** No more chains *****
<Router address 0>
Target: net0 193.1.6.10
Target: net1 193.1.6.11
Target: net2 193.1.6.12
/gi/5.0.4d/bin/swapifcs: open file '/etc/tcp' for reading.
Finished Creating New Kernel Files
No License File Present
Finished Creating License File
Finished Processing interfaces File
Finished Processing RUN_SERVER Files
Finished Processing sqlserver.name File
cp: /usr/sybase/dac6000SQL.cfg and /usr/sybase/dac6000SQL.cfg are identical, not copied
Finished Updating Configuration Files
RELINKING KERNEL

The UNIX Operating System will now be rebuilt.

This will take a few minutes. Please wait.

Root for this system build is /

The UNIX Kernel has been rebuilt.

Backing up unix to unix.old
Installing new unix on the boot file system
Setting up new kernel environment
Running nlsym for U386MON

PLEASE REBOOT FOR CHANGES TO TAKE EFFECT!!!

************************ ACC_RENAME DONE ************************

************************************
PORTSERVER SETUP VERSION 1.0.0
************************************

***************************** Version 1.0.0 ********************************

This program will prompt the user to enter the number of

PortServers, PortServer's MAC ADDRESS, IP ADDRESS, and HOST NAME.

****************************************************************************

Enter the number of PortServers to configure [1]: < Enter >

Enter the MAC (Ethernet) address of First PortServer [0:40:9D:20:ED:C9]: <

xx.xx.xx.xx.xx.xx >
Enter the IP address for First PortServer [168.84.250.138]: < Enter >
Enter the host name for First PortServer [PrtSvr1]: < Enter >
Enter the number of expansion ports connected to this PortServer [0]: < Enter >

5-5
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

The following information will be used to configure PortServers:

PORTSERVER MAC ADDRESS IP ADDRESS HOSTNAME EXPANSIONS

------------- --------------------- ------------------ ----------- ------------
1 0:40:9D:20:ED:C9 168.84.250.138 PrtSvr1 0

Enter c to continue, e to exit, or <Enter> to re-enter: c

*****************************************************************************

IMPORTANT NOTES:
----------------

WHILE THE DAC 6000 IS REBOOTING, FOLLOW THE INSTRUCTIONS BELOW TO RESET THE PORTSERVERS
TO FACTORY DEFAULTS (THE PORTSERVERS WILL ACQUIRE THE NEW SETUP AUTOMATICALLY):

1. Turn off the PortServer II's power switch.

2. Press and Hold the PortServer II's left and right "arrow" buttons at the same
time.
3. Turn on the PortServer II's power switch.
4. Hold the PortServer II's left and right "arrow" buttons in until "CL" ("EP"
on PortServer) appears on the front panel display, then release the buttons.
5. Repeat steps 1, 2, 3, and 4 for all PortServers which are to configure.

*****************************************************************************
******************************* DIGI_RENAME DONE ****************************
PRESS <ENTER> TO CONTINUE ...

5-6
 BSI Expanded Result Codes DAC 6000 Release V2.97 Quick Start Guide

BSI Expanded Result Codes

The expanded business system interface (BSI) result codes report all
WireLink errors that are discovered by the BSI. This includes:
Errors discovered by BSI validation checks
Timeouts caused by other subsystems failing to return a response
Operational errors caused by the BSI receiving an error response
from another DAC 6000 subsystem when processing a command

BSI Port Processing

Due to the synchronous nature of the BSI, an algorithm is used to
implement the error codes. A global result code value, used by the
bsiport task, tracks an error. When a WireLink command is received by
the bsiport task, the global result code is set to 0. Whenever an error
occurs in the BSI during the processing of the WireLink command, or if a
DAC 6000 subsystem reports an error, the global result code value is set
to one of the expanded result codes.

Business System Tunable

A business system tunable is used to differentiate between business
systems that are capable of supporting the expanded codes in a
multi-business system environment.
To enable a business system to support expanded result codes, access the
Edit Business System Tunables window with:
DAC 6000 Main Menu > Manage Controller > Manage Tunables.
1 Click Edit BSI Tunables; invokes the Edit Business System
Tunables window.
2 Click Select; enables BSI Name in the Information panel.
3 Click BSI Name; invokes the Zoom: Business System Names
window.
4 Scroll to and highlight the <target business system>.
5 Click Accept.
6 On the Edit Business System Tunables window, click Accept;
enables Change.
7 Click Change.

5-7
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

8 Click WireLink Support Expanded Result Codes (filled).

9 Click Accept.
After clicking Accept on the Edit Business System Tunables window, an
MSO_BSI_TUNABLES_MSG is sent to the bsiserv task. The bsiserv
task stores the information in the business system table and a response
is then returned to the window.
In order for the changes to take affect, stop and restart each of the
bsiport tasks that are associated with the selected business system or
restart the DAC 6000 application.

BSIL_Report
The BSI Report Generator is used to track business system transactions
processed by each bsiport task. The user can filter results based upon
bsiport task as well as transaction start and end times.
Report generator results display the encoded status word, the error code
word, and data words if applicable. Successful transfers are indicated
with an error code of 0. Error codes 220, 226, 231, or 232 indicate a
failure, with error codes 220 and 232 occurring most frequently. To help
isolate the cause of a problem, the report generator displays a textual
representation for the expanded result codes along with the value.

Expanded Result Codes

The basic set of result codes that the DAC 6000 supports is:
R e sul t C ode D es c rip ti on
001 No error.
220 Protocol I/O error (retry command).
226 Packet checksum error (recalculate checksum, retry command).
231 Packet size error (recalculate size, retry command).
232 Packet time out error (retry command).

The expanded list of result codes that the DAC 6000 supports is:
R e sul t C ode D es c rip ti on
Validation Errors
1001 Validation failed (generic validation error used only if a more specific error is not
defined).

5-8
BSI Expanded Result Codes DAC 6000 Release V2.97 Quick Start Guide

R e sul t C ode D es c rip ti on

1002 Invalid BSI code (not assigned to this WireLink port).
1003 BSI code in the business system owner component does not exist.
1004 Invalid serial number (the field is formatted incorrectly).
1005 Serial number does not exist.
1006 Serial number already exists.
1007 Invalid unit address.
1008 Unit address already exists.
1009 Invalid equipment type.
1010 Invalid equipment subtype.
1011 Headend handle does not exist.
1012 Upstream plant handle does not exist.
1013 Downstream plant handle does not exist.
1014 VCM handle does not exist.
1015 Invalid operation code in the state component.
1016 Illegal operation code in the state component – set-top off plant.
1017 Region config handle in the feature component does not exist.
1018 Invalid type in the authorization component.
1019 Package handle does not exist for this business system.
1020 Service handle does not exist for this business system.
1021 Program handle does not exist for this business system.
1022 Program handle already exists for this business system.
1023 Epoch duration is longer than the maximum allowed.
1024 Interstitial period is longer than the epoch duration.
1025 Preview time is longer than the epoch duration.
1026 Impulse purchasable is longer than the epoch duration.
1027 Program time overlaps an existing program.
1028 Invalid action code.
1029 Service handle is invalid.
1030 Total number of services is out of range.
1031 Program handle is out of range.
1032 MPAA advisory not valid.
1033 Violent content advisory is not valid.
1034 Sexual content advisory is not valid.
1035 Language content advisory is not valid.
1036 Epoch start time is invalid (formatted incorrectly).

5-9
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

R e sul t C ode D es c rip ti on

1037 Epoch end time is before epoch start time.
1038 Epoch start time is in the past.
1039 Duplicate program.
1040 Rating region is invalid
1041 Invalid number of entries.
1042 Invalid authorization flag.
1043 Bit mask value is out of range.
1044 Illegal component was received.
1045 Duplicate component was received.
1046 Illegal operation (cannot delete last program handle).
1047 Invalid country code, currency region, and EPG region combination.
1048 Invalid VCM name.
1049 Terminal not on plant.
1050 BSG handle not found.
1051 Epoch start time not found.
1052 Not all purchases marked for upload.
1053 Set-top features not found.
1054 Duplicate type component error.
1055 Duplicate plant component error.
1056 Duplicate state component error.
1057 Duplicate feature component error.
1058 Duplicate authorization component error.
1059 Unknown component error.
1060 Authorization records not last error.
1061 Duplicate BSI error.
1062 Missing type component in 760 command.
1063 BSI code and set-top serial number mismatch error.
1064 Maximum services exceed limits error.
Operational Errors (may warrant retry)
2001 Terminal add failed (terminal was not added to database).
2002 Terminal change failed (terminal data was not changed in database).
2003 Terminal delete failed (terminal was not deleted).
2004 Terminal authorization failed.
2005 Terminal state operation, defined by the operation code of the state component,
failed.

5-10
BSI Expanded Result Codes DAC 6000 Release V2.97 Quick Start Guide

R e sul t C ode D es c rip ti on

2006 Program add failed (program was not added).
2007 Program change failed (program was not changed).
2008 Program delete failed (program was not deleted).
2009 Query of terminal data failed – set-top off plant.
2010 Query of terminal data failed – set-top not responding.
2011 Poll of terminal failed – set-top off plant.
2012 Poll of terminal failed – set-top not responding.
2013 Purchase upload failed.
2014 Terminal authorization refresh failed – set-top off plant.
2015 Terminal authorization refresh failed – set-top not responding.
2016 Terminal initialization failed – set-top off plant.
2017 Terminal initialization failed – set-top not responding.
2018 Terminal clear PIN operation failed.
2019 Terminal activation operation failed.
2020 Terminal refresh operation failed.
2021 Terminal channel map change failed.
2022 Terminal cold initialization failed.
2023 Terminal warm reset failed.
2024 Terminal de-activation operation failed.
2025 Terminal factory reset failed.
2026 PPV authorization update failed.
2027 Custom refresh failed – set-top on plant.
2028 Interactive refresh operation failed.
2029 Mark event purchase failed.
2030 Change set-top features operation failed.
Low Level Operational Errors
3001 Destination task is not available.
3002 Memory allocation error.
3003 Database access error.
3004 IPPV tier not found.
3005 On plant not found.
3006 Error collecting purchases.
3007 Undefined state component error on 760 command.
3009 Interactive return path not found.
3010 Get all services database stored procedure failed.

5-11
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

R e sul t C ode D es c rip ti on

3011 Invalid message type.
3012 Bad request type in identifier component on 760 command.
3013 Invalid program date format error.
3014 Check duplicate programs database stored procedure error.
3015 Get program handles database stored procedure error.
3016 Get package handles database stored procedure error.
3017 Get service handles database stored procedure error.
3018 Error collecting IPPV purchases.
3019 Error collecting set-top purchases.
3020 Get package tiers database stored procedure error.
3021 Get service tiers database stored procedure error.
3022 Get program tiers database stored procedure error.
4001 Clear PIN timeout error on 760 command.
4002 Delete set-top timeout error.
4003 Set-top activation timeout error.
4004 Change set-top features timeout error.
4005 Set-top terminal refresh timeout error.
4006 Change VCM name timeout error.
4007 PPV authorization timeout error.
4008 Set-top authorization timeout error.
4009 Authorization refresh timeout error.
4010 Interactive custom refresh timeout error.
4011 Set-top add timeout error.
4012 Set-top initialization timeout error.
4013 Program add timeout error.
4014 Program change timeout error.
4015 Program delete timeout error.
4016 Mark event purchase timeout error.
4017 Single set-top poll timeout error.
4018 Terminal state operations timeout error.

5-12
 Section 6
Analog Compatibility

ACC-4000-to-DAC 6000 analog-shared resources are analog PPV

programming and Dynamic Encryption Key Management (DEKM).

Analog PPV Compatibility

The DAC 6000 analog compatibility feature allows replication of analog
PPV programs from one or more ACC-4000s. After the DAC 6000 is
properly configured for this function, it automatically reads the analog
data at regular intervals (the default is once per hour), or by request,
using the Define Analog Service window.
To implement analog PPV program compatibility:
Set up the DAC 6000 and ACC-4000 to enable the analog
compatibility feature
On the DAC 6000, define the ACC-4000s from which analog
programming information will be read
On the DAC 6000, define the analog PPV services to be replicated

DAC 6000 Setup

To set up the DAC 6000:
1 Stop the DAC 6000 application.
2 Type accisql acc4000 your_initials .
3 Type the following command:
update tunables
set tunable_int_value = 1
where tunable_class = “system” and tunable_name =
“analog_compatibility_enabled”
go
4 Type quit to exit the database.
5 Log in as root.
6 Edit /etc/hosts to add the name and IP address of the
ACC-4000(s).
7 Edit /etc/hosts.equiv to add the name of the ACC-4000(s).

6-1
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

8 Type acc_rename interfaces to allow SYBASE access to the

ACC-4000.

ACC-4000 Setup
The ACC-4000 application can be running. To set up the ACC-4000:
1 Insert the Analog PPV Install Disk (note: scripts also reside in
/home/acc4000d/install_acc/analog_rep on the DAC 6000).
2 Type cd /tmp .
3 Type tar xvf /dev/rfd0 .
4 Type ./install_ppv_shadow .

Define ACC-4000
Defining an ACC-4000 requires defining a service provider and adding
the ACC-4000.

D e fin ing the S e rv ice P rov ide r

On the DAC 6000, each ACC-4000 is associated with one service
provider, which must be added using the Define Service Provider
window. This window is accessed with:
DAC 6000 Main Menu > Manage Services > Define Service Provider.
The service provider that is added will be associated with each analog
service from the ACC-4000.

Adding the AC C- 4000

The ACC-4000 is added using the Define ACC4000 window, which is
accessed with:
DAC 6000 Main Menu > Manage Controller > Define ACC4000.
On the Define ACC4000 window, enter the ACC-4000 name and the
unique service provider previously defined in the Define Service Provider
window. Ensure Enable Data Collection is active (filled) and, if
applicable, enter the ACC-4000 failover information.

6-2
 Analog PPV Compatibility DAC 6000 Release V2.97 Quick Start Guide

Define Analog Service

Defining the analog PPV service requires associating the analog service
to a named analog device, adding a source for the analog service, and
adding the analog service.

A s s oc ia ting t he Ana log Se rv ic e to a n A na log D evi ce

Associate the tuned channel of the ACC-4000 service to an analog device
name entered for the ACC-4000 in the Define Upconverter Device
window. This window is accessed with:
DAC 6000 Main Menu > Manage Devices > Define Upconverter Device.
On the Define Upconverter Device window, toggle the device type from
digital to analog, enter a device name, and the tuned channel associated
with the analog service on the ACC-4000.

A dd ing a Sour c e
Add a source for this analog PPV service by accessing the Define Source
window with:
DAC 6000 Main Menu > Manage Services > Define Source.
Add a new source for each analog PPV service.

A dd ing the Ana log Se rv ice

Access the Define Analog Service window with:
DAC 6000 Main Menu > Manage Services > Define Analog Service.
Select the source and provider names that were previously associated
with the ACC-4000. Select Externally Supplied for the Program
Provision. On the Location panel, ensure the location is the analog
device name previously defined. Return to the Identification panel and
click Accept to add the analog service. The DAC 6000 automatically
retrieves all programs associated with this service. Click the Define
Programs button to view the results.

6-3
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Dynamic Encryption Key Management (DEKM)

The DAC 6000 Dynamic Encryption Key Management (DEKM) feature
enables the DAC 6000 to receive and process DEKM commands from the
ACC-4000 DEKM master.
The updated version of the DEKM that is provided with DAC 6000
application software release V2.97 is compatible with ACC-4000 DEKM
release 11.2, which also includes the security counter measures project.
It is also backward compatible with the previous ACC-4000 DEKM
release 4.0.
Additional DAC 6000 setup is not required for this feature; however, on
the ACC-4000, the DAC 6000 name must be added to the
dekmconfig.dat file located in /home/acc4000/data. The
dekmconfig.dat file contains the list of DEKM slaves.

6-4
 Section 7
Key Ser ver Operations

Key server operations comprise the utilities, scripts, and procedures

necessary to backup/restore data, logon to the Encryption Control Center
(ECC) system, load a Group Configuration Request (GCR)/Group Rekey
(GRK), and add a second KLS to the DAC 6000 system.

Unit Key List Data Save/Restore

The Unit Key List backup and restore scripts that follow can be used to
save and recover the content of the DAC 6000 Unit Key List (UKL).
Insert the tape into the tape drive (tape must NOT be write protected).
Type cd/home/acc4000d/scripts
Type ukl_dump
This script saves the master UKL data and all append UKL data to tape.
The DAC 6000 application can be running when this script is executed.

Type cd/home/acc4000d/scripts
Type ukl_restore
This script restores the archived master UKL data and all append UKL
data from tape to a disk file. The DAC 6000 application must be running
when this script is executed.

Encryption Control Center Configuration

To establish a connection from a customer site to the Encryption Control
Center (ECC) system in San Diego, California, a login account and
password must be obtained. After a successful connection is made to the
ECC computer system, the DAC 6000 will be able to request Group
Configuration Requests (GCRs) for each registered KLS. A backup of
these configuration files will be made automatically when the next
scheduled database backup occurs.
To establish a connection from the customer site to the ECC:
1 Login as user acc4000d or open a new window.
2 Run the ECC configuration script: ecc_config .
3 When prompted, enter the root password.

7-1
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

4 When the Main Menu is displayed, select each option to verify that
the information is correct.
5 Obtain the ECC customer login and password from San Diego
security for the menu item Customer Login and Password.
6 In response to the prompt: Modem configuration, configure the
diagnostic modem for ECC access. The default modem configuration
is for a Multitech modem, on device port tty1A, using 9 to access
the outside phone line. If this is not correct, then modify the
parameters as necessary.
7 Select Add ECC to the hosts file, to add an entry in the
/etc/hosts file if one is not already present.
8 Select Restart PPP driver, to restart the PPP driver for the new
configuration changes to take effect (this is faster than rebooting the
DAC 6000).

Verifying ecc_config Changes

To verify that the ecc_config setup is correct, use the Obtain Group
Configuration Request window to request a GCR for the target KLS. The
Obtain Group Configuration Request window is accessed with:
DAC 6000 Main Menu > Manage Devices > Manage Security > Obtain
Group Configuration Request.
1 Ensure Send GCR to Key List Server is deselected for testing
purposes.
2 Select a <Group> and click Accept.
3 Open a new 132 window and execute a tail –f on the
/home/acc4000d/data/op_log_file to check for any errors that
may occur when connecting to the ECC system in San Diego.
4 Click Send Request on the Obtain Group Configuration Request
window and wait for the process to complete. Any errors encountered
are logged in the op_log_file.
5 Correct any erroneous setup information, for example, an incorrect
ECC password.

7-2
 Group Configuration Request/Group Rekey DAC 6000 Release V2.97 Quick Start Guide

Group Configuration Request/Group Rekey

To load a GCR/GRK:
1 Login as user acc4000d or open a new window.
2 Verify that there is an entry for the kls001 in the /etc/hosts file
and ping it for a response by typing ping -c 1 kls001 (or use
ping kls001 and break ).
3 Type cd scripts to access the scripts directory.
4 Type start_acc to start the DAC 6000 application software (if it is
not already started).
5 Open a new window and access the scripts directory again by typing
cd scripts .
6 Insert the floppy disk containing the Group Configuration Request
(GCR).
7 Access the directory to display the filename by typing dosdir a:
8 Copy the file from the floppy to the UNIX hard disk by typing
doscp a:filename . (note that the period ‘.’ must be included).
9 Now load the GCR using the ed-tool:
Type ed-tool .
Type 3 for Group Rekey.
Type the current password acc4000d .
Type the <filename> that was found on the DOS floppy.
Press (ENTER) twice to accept the default values.
After sending the GCR message to the security subsystem:
Press (ENTER) to continue.
Type b to return back to the main menu.
Verify that the GCR was successful:
Type r to remove the old reply file.
Type 2 for Send Key List Server (KLS) Request.
Type 1 for Send KLS Request once.
Press (ENTER) to accept the default value and wait several
seconds.

7-3
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Type d to display the new reply file.

Verify that the first keyserver element activity status is active as
indicated with a ‘2’ and that the remaining keyserver elements are
inactive, as indicated with a ‘1’.
If all four elements are still active,
Press the SPACEBAR or (ENTER) or type q to quit viewing
the output.
Type q to quit the ed-tool.
Repeat the procedure from step 1.
Example of successful GCR delivery output:

Open sessions - 1 Initial lifetime - 360

Initial validation rate - 65535 Keyserver elements - 4
Ram test - 1 Rom test - 1
Customer number - 00010004 Keyserver Tag Number - 034602912601122
Firmware Revision - 15

KEYSERVER ELEMENT 1 - ACTIVE

eee address - 00 12 72 98 f1
group sequence number - 133
Category epochs processed - 5
ECMS processed - 878
Transactions processed - 1585508
Transaction errors - 0

KEYSERVER ELEMENT 2 - INACTIVE

eee address - 00 12 72 98 f2
group sequence number - 133
Category epochs processed - 5
ECMS processed - 860
Transactions processed - 1585286
Transaction errors - 0

KEYSERVER ELEMENT 3 - INACTIVE

eee address - 00 12 72 98 f2
group sequence number - 133
Category epochs processed - 5
ECMS processed - 860
Transactions processed - 1585286
Transaction errors - 0

KEYSERVER ELEMENT 4 - INACTIVE

eee address - 00 12 72 98 f4

7-4
Group Configuration Request/Group Rekey DAC 6000 Release V2.97 Quick Start Guide

group sequence number - 133

Category epochs processed - 5
ECMS processed - 823
Transactions processed - 1585259
Transaction errors – 0

Exit ed-tool by typing:

Press the SPACE BAR or (ENTER) or type q to stop viewing
the output.
Type q to quit ed-tool.
10 After the GCR is successfully loaded, restart the DAC 6000
application software by typing stop_acc ; start_acc .
11 Verify that the new category epoch is established by using the ed-tool
again in the scripts directory to access the KLS and display the
reply file:
Type ed-tool .
Type r to remove the old reply file.
Type 2 for Send KLS Request.
Type 1 for Send KLS Request once.
Press (ENTER) to accept the default value and wait several
seconds.
Type d to display the new reply file.
Press the SPACE BAR to proceed to the second screen of data if
necessary.
The first keyserver element (active) should display a category epoch
value that is non-zero, for example:
Keyserver Element 1
EEE address – 00 12 72 90 XX
EEE health - 255
Group Sequence Number - 2
TD test result - 0
Category Epochs Processed – 5
Acceptable if Category Epochs Processed = 0 and keyserver was
‘healthy.’
Acceptable if Category Epochs Processed is greater than 0 and
keyserver was not ‘healthy.’

7-5
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Unacceptable if Category Epochs Processed = 0 and keyserver was

not ‘healthy.’ Repeat the GCR/GRK procedure again.
12 Remove the floppy with the GCR.

Multiple KLS Configuration

The DAC 6000 Application Software provides support for two KLSs.
Before a second KLS can be added to the DAC 6000, it must be
registered with the ECC in San Diego. Contact BCS Systems
Configuration Management with an e-mail to [email protected].
The e-mail must contain the serial number of the KLS. Also, system
access to the ECC in San Diego must be established by obtaining a site
logon and password (see “Encryption Control Center [ECC]
Configuration”). For multiple KLS support, the DAC 6000 diagnostic
modem must be configured with ecc_config for direct access dial out to
the ECC, San Diego.

It is important to note that when two KLSs are configured, the ed-tool
cannot handle multiple keyserver GCR files.

Adding a Second KLS to the DAC 6000

To add a KLS to the DAC 6000:
1 Configure the KLS on the HCT 1000 using the MAC address and
assign a unique IP address. Save the configuration.
2 Connect the new KLS to the Ethernet network and apply power.
3 Add an entry (for example, kls002) to the DAC 6000 /etc/hosts
file for the new KLS.
4 Ping the new KLS (for example, ping kls002).
5 Login to the DAC 6000 application software.
6 Access the Define Key List Server window with: DAC 6000 Main
Menu > Manage Devices > Manage Security > Define Key List
Server.
7 Click Add.
8 Type the name of the new KLS that was entered into the
/etc/hosts file.
9 Click Accept and wait approximately 2½ to 3 minutes for the
process to complete.

7-6
Multiple KLS Configuration DAC 6000 Release V2.97 Quick Start Guide

10 Invoke the X pop-up menu and select Open Operation Log.

11 View the op_log_file to determine if the second KLS was added

successfully.

Deleting a KLS
When deleting KLSs, the last KLS in a group cannot de deleted;
however, it can be swapped-out.
To delete a KLS:
1 Login to the DAC 6000 application software.
2 Access the Define Key List Server window with: DAC 6000 Main
Menu > Manage Devices > Manage Security > Define Key List
Server.
3 Click Select.
4 Type the target <KLS name> in the Name field or click Name to
invoke the Zoom: Device Name window.
5 In the Zoom: Device Name window, scroll to and highlight the
<target KLS>.
6 Click Accept, the Zoom: Device Name window disappears.
7 In the Define KLS window, click Accept.
8 Click Delete.
9 Click Yes on the confirmation pop-up window that is displayed and
wait approximately 2 to 2½ minutes for the process to complete.
10 Invoke the X pop-up menu and select Open Operation Log.

11 View the op_log_file to determine if the KLS was successfully

deleted.

7-7
 Section 8
Configuring Multicast Addresses

A background service, such as TVGOS1, must be set up and assigned to

a channel map prior to creating the multicast 16 address set.
Multicast address values are entered in a byte.byte format from the
Define Multicast 16 Address Set window. This window is accessed with:
DAC 6000 Main Menu > Manage Terminals > Define Multicast 16
Address Set.
The multicast address set is then linked to a downstream plant from the
Define Downstream Plant and Edit Downstream Plant windows, which
are accessed with:
DAC 6000 Main Menu > Manage Plants > Define Downstream Plant >
Edit Downstream Plant.

Converting Multicast 16 Addresses

The multicast 16 addresses received from the service provider must be
converted to highbyte.lowbyte format for use on the Define Multicast 16
Address Set window. A scientific calculator that supports binary
conversion is recommended. The following example illustrates how to
convert a multicast 16 address:

8093 (decimal) = 1111110011101 (binary)

Eight from right = 10011101

Remaining characters = 11111

Decimal values = 31 157

Highbyte.Lowbyte format = 31.157

8-1
 Section 9
Emergency Alert System (EAS)

Emergency Alert System (EAS) tunables can now be edited from the Edit
Emergency Alert Tunables window after they are initially configured
from the Configure EAS Service window.

Configuring an EAS Service

The EAS is initially defined with the Configure EAS Service window,
which is accessed with: Main Menu > Manage Services > Configure EAS
Service.
To configure an EAS service:
1 In the OM Information panel of the Configure EAS Service window,
deselect All (hollow).
2 Click Name to invoke the Zoom: Device Name window.
3 Scroll to and highlight a <target OM 1000>.
4 Click Accept.
5 On the Configure EAS Service window, click Add to invoke the Edit
EAS Service window.
6 Click Source & Provider Name to invoke the Zoom: Source &
Provider Name window.

The selected OM 1000 and Service/Provider must both be

associated to the same downstream plant.
7 Scroll to, and highlight a <target Service Name – Provider Name
row> and click Accept.
8 Click RF Device to invoke the Zoom: Device Name window.
9 Scroll to and highlight the <target RF device> and click Accept.
10 Click Accept.

11 Repeat steps 2 through 10 for each OM 1000 on the system.

9-1
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Editing Emergency Alert Tunables

The Edit Emergency Alert Tunables window replaces the need to execute
the om_eas_setup script that was implemented for installations and
upgrades. This window can be used to configure or reconfigure EAS at
any time. It is not necessary to reboot the DAC 6000 for the changes to
take effect. The changes become active when the Accept button is clicked
on the window,
The Edit Emergency Alert Tunables window can be accessed with:
Main Menu > Manage Controller > Manage Tunables > Edit Emergency
Alert Tunables.

If the EAS is not configured, when the Edit Emergency Alert

Tunables window is accessed, a popup displays the message “Unable to
obtain EAS Tunable data.”
An illustration of the Edit Emergency Alert Tunables window is as
follows:

1 2

9-2
Editing Emergency Alert Tunables DAC 6000 Release V2.97 Quick Start Guide

Field definitions are as follows:

1 Force Tune Message - when active (filled), it causes set-tops to be
tuned to the EBS channel and does not restore each set-top back to
the channel prior to the alert. The channel must be retuned
manually.
2 Channel Override Message - when active (filled), it prevents
suppression of EAS messaging even if the set-top is tuned to an
analog channel. It forces set-tops to switch channel tuning from the
current channel to the EAS channel for the emergency message, and
then return to the channel prior to the alert.

Should be used only with DCT2000 or greater set-tops, as channel

override requires a modification to set-top firmware to support a
wildcard value (0) for the VCT_ID field of the channel override
message.
3 Suppress Channel Override on Analog Channels - when active
(filled), it enables the emergency alert to appear as a banner on those
set-tops already tuned to analog channels. This field affects the
Force Tune Message and Channel Override Message, as set-tops will
display an alert banner on analog channels without being forced to
do it.
4 Enable CEAS Standard Message - when active (filled), it enables
CableCARD™/host terminals to tune to the cable emergency alert
system (CEAS) channel. CableCARD/host terminals will always tune
to the emergency alert channel, even if the tuned channel prior to
the alert is analog or digital.
5 Enable PID Blocking - when active (filled), it enables the PID to
Block on OM field.
6 PID to Block on OM - PID blocking only affects CEAS. This value
specifies the logical OM 1000 network port to block. The default
value is 3. Enable PID Blocking must be active (filled) for this field
to take affect.

9-3
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Valid Combinations
Valid combinations are:
Force Tune Message with/without Suppress Channel Override on
Analog Channels
Force Tune Message with/without Suppress Channel Override on
Analog Channels and Enable CEAS Standard Message
Channel Override Message with/without Suppress Channel Override
on Analog Channels
Channel Override Message with/without Suppress Channel Override
on Analog Channels and Enable CEAS Standard Message
with/without Enable PID Blocking

9-4
 Section 10
Configuring an IRT Ser vice

This procedure assumes the IRT 1000/2000 screen set was implemented
to set up an IRT 1000/2000 to process services for a specific multiplex,
but no other services and devices were defined. Reference the specific
subsection for incremental additions (for example, Service Setup if
adding only services).

System Level Parameters and Verification

When configuring system level parameters, device names must not
exceed nine characters and RADD 6000 names must not exceed seven
characters.
1 In the /etc/hosts file, add devices and their associated
IP addresses:
Entry Example Applicable Device
193.1.5.6 irt001 IRT 1000/2000
193.1.5.9 om001 OM 1000
193.1.5.7 rpd1 RPD 1000/2000
193.1.5.8 kls001 KLS 1000
193.1.5.19 radd7 RADD 6000
193.1.5.255 radd7BA RADD 6000 broadcast address

2 Ping each device to verify communication.

3 Ensure service ports are defined as set up on the base tape.

Define Devices
From the Manage Devices selection on the Main Menu, add the following
devices to the system and verify the correct IP address was retrieved
from the /etc/hosts file for each device.
1 Add the RADD 6000.
2 Add the IRT 1000/2000 (wait a minute, and then verify that the
TSODA addresses were acquired from the device).
3 Add the upconverter device (digital, <tuned channel number
accessed from the C6U front panel>).

10-1
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

4 Add the OM 1000.

Tuned channel is A1.
Insertion bandwidth is 1000.
5 Add the RPD 1000/2000.
6 Add the demod boards (DM 1000s).

Define Plants
Add the headend, downstream plant, and upstream plant.
1 Add the headend (a typical carrier definition table is EIA Standard
- center frequency).
2 Define the downstream plant. Link the OM 1000 and the C6U to the
downstream plant.
3 Add the upstream plant. Link the RPD 1000/2000 channels to the
upstream plant.

Link Devices
Add two links.
1 Add a link from the RADD 6000 (output device) to the OM 1000
(input device) through the RADD2OM device port.
2 Add a link from the RPD 1000/2000 (output device) to the
RADD 6000 (input device) through the RPD2RADD device port.

Service Setup
Define a source, service provider, and digital service.
1 Define a source (source type is service).
2 Define a service provider or use default.
3 Define a digital service:
Service type is subscription.
Encryption mode is full.

10-2
 Channel Map Definition DAC 6000 Release V2.97 Quick Start Guide

4 Define a digital service location.

RF device is C6U.
Queuing device is IRT 1000/2000.
MPEG service is found in the MPLX definition.
5 Link the service to the IRT 1000/2000 by assigning it to the
decrypting TSODA based on the satellite MPLX definition.

Channel Map Definition

Define and link the channel map.
1 Define the channel map.
2 Link the channel map to the previously defined downstream plant.
3 Add the previously defined service to the virtual channel map.

Define Terminals
The unit address and serial number can be found on the set-top when
adding a terminal.
1 Add a terminal.
2 Authorize the service.
3 Initialize the set-top.

10-3
 Section 11
Configuring an MPS Ser vice

This section provides the procedure to configure the DAC 6000 for the
MPS Trans-Remux D12 device.

DCT 1000s running off of the platform ROM may not reliably tune
the multiplex generated by the MPS Trans-Remux D12 device. This is
remedied by downloading the V6.22 platform code.
Instructions to delete a route and re-acquire Access Control Processor
(ACP) addresses are also provided in this section.

Configuring the MPS Trans-Remux D12

To configure the DAC 6000 for an MPS Trans-Remux D12:
1 On the DAC 6000, add an entry to the /etc/hosts file containing
the name and IP address of the MPS Trans-Remux D12.
2 Ping the MPS Trans-Remux D12 from the DAC 6000 to verify it is
accessible with:
DAC 6000 Main Menu > Manage Controller > Manage Site >
Open System (xterm) Window.
At the xterm window prompt, type ping <target name or IP
address>.
Terminate the ping with Ctrl+C.
3 If required, access the Define Upconverter Device window to add any
new upconverter devices (C6Us/C8Us), which are connected to the
MPS Trans-Remux D12's output ports.
4 Access the Define Downstream Plant window with: DAC 6000 Main
Menu > Manage Plants > Define Downstream Plant.
From the Define Downstream Plant window, add the associations
between the new upconverters and downstream plants.
5 Add the MPS Trans-Remux D12 device to the DAC 6000.
Access the Define MPS window with: DAC 6000 Main Menu >
Manage Devices > Define MPS.
Click Add.

11-1
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Type the <device name> in the Name field.

Select the time source: DAC, if the DAC 6000 supplies the time;
NTP Server, if an NTP server or an input transport stream
supplies the time.
Click Accept.
6 After an MPS Trans-Remux D12 device is added to the system, the
DAC 6000 queries it for its configuration (for example, input ports,
output ports, ACP addresses, etc.). Check the MPS Trans-Remux
D12 device input ports data to ensure it is configured properly on the
DAC 6000.
Access the input ports configuration data with: DAC 6000 Main
Menu > Manage Devices > Define MPS.
− Click Select.
− Click Name; invokes the Zoom: Device Name window.
− Scroll to and highlight the <target device name>.
− Click Accept.
− On the Define MPS window, click Accept.
− Click Configure Input Ports.
− View the input ports configuration data on the Configure
MPS Input Ports window.
You have the option to assign a name to each input port.
− Click Select on the Configure MPS Input Ports window.
− In the Input Ports panel, click the target Port Name to be
changed.
− Click Change; invokes the Edit MPS Input Port window.
− Type a new <input port name>.
− Click Accept.

The DAC 6000 automatically extracts the MPEG service

numbers for the services available on each input port. To verify
the list of MPEG service numbers:
− Click Select on the Configure MPS Input Ports window.
− Click Change; invokes the Edit MPS Input Port window.
− On the Edit MPS Input Port window, click Input Sources in
the Active Panel.
− Click Select in the Table Operation panel.
− Scroll through and inspect the MPEG service numbers that
are displayed, which are obtained from the last extraction of
the PAT table on the transport stream.

11-2
Configuring the MPS Trans-Remux D12 DAC 6000 Release V2.97 Quick Start Guide

You have the option to assign a name to each input MPEG

source. By default, there are no names associated with the
sources.
− Ensure the source names to be assigned to each input MPEG
source are in the DAC 6000 database. Restore the DAC 6000
Main Menu.
− Access the Define Source window with: DAC 6000 Main
Menu > Manage Services > Define Source.
− Click Select.
− Click Name; invokes the Zoom: Source Name window.
− Scroll through the <target source name> to ensure it
exists.
− If a source name does not appear, click Exit.
− On the Define Source window, click Cancel.
− Click Add.
− Type a <source name>.
− Select a Service Type.
− Type a <Source ID value>.
− Click Accept.
− On the Edit MPS Input Port window, click the MPEG
Service Number to be assigned a source name.
− Click Change; invokes the Edit MPS Input Source window.
− On the Edit MPS Input Source window, click Source Name;
invokes the Zoom: Source Name window.
− Scroll to and highlight a <target source name>.
− Click Accept.
− On the Edit MPS Input Source window, click Accept.

7 Check the MPS Trans-Remux D12 device output ports data to ensure
it is configured properly on the DAC 6000.
Access the output ports configuration data with: DAC 6000 Main
Menu > Manage Devices > Define MPS.
− Click Select.
− Click Name; invokes Zoom: Device Name window.
− Scroll to and highlight <target device name>.
− Click Accept.
− On the Define MPS window, click Accept.
− Click Configure Output Ports.
− View the output ports configuration data on the Configure
MPS Output Ports window.

11-3
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

You have the option to change the output port name, QAM
modulation, and transport stream ID.
− Click Select on the Configure MPS Output Ports window.
− In the Output Ports panel, click the <target Port Name> to
be changed.
− Click Change; invokes the Edit MPS Output Port window.
− Type a new Port Name.
− Type a new <Transport Stream ID>; the value must be
greater than 0 and less than 65536.
− If applicable, select a new <Modulation Format>. (This
value and the value set on the Java-enabled console must
agree. Changing one requires updating the other.)
− If applicable, select a new <Inner Coding> mode.
− If applicable, select a new <Outer Coding> mode.
− Type a new <Symbol Rate> in Msymbols/sec.
− Click Accept.
8 Add a service with DAC 6000 Main Menu > Manage Services >
Define Digital Service. (The MPS Trans-Remux D12 does not
perform service decryption.)
Click Add.
On the Identification Active Panel:
− Type the Service and Provider names.
− Select the <Program Provider>.
− Select the <Encryption Mode>.
− Select the <Antitaping Vendor>.
− Click Location on the Active Panel.
For the MPS Trans-Remux D12, a service location is associated
with a specific port. On the Location Active Panel:
− Click Add; invokes the Edit Digital Service Location window.
− On the Edit Digital Service Location window, click RF
Device; invokes the Zoom: Device Name window.
− Scroll to and highlight the <C6U wired to the MPS
Trans-Remux D12 output port>.
− Click Accept.
− On the Edit Digital Service Location window, type an MPEG
Service #. (The MPS Trans-Remux D12 is capable of MPEG
service number remapping; therefore, the output MPEG
service number does not have to match the service number
on the input of the device.)

11-4
Configuring the MPS Trans-Remux D12 DAC 6000 Release V2.97 Quick Start Guide

− Click Queuing Device; invokes the Zoom: Device Name

window.
− Scroll to and highlight the <target queuing device>.
− Click Accept.
− On the Edit Digital Service Location window, click Port;
invokes the Zoom: Port Names window.
− Scroll to and highlight the <MPS Trans-Remux D12
output port>.
− Click Accept.
− On the Edit Digital Service Location window, click Accept.
− On the Define Digital Service window, click Business
System on the Active Panel.
On the Business System Active Panel:
− Click Add; invokes the Edit Service Business System
Assignment window.
− Click Business System Name; invokes the Zoom: Business
System Names window.
− Scroll to and highlight the <target business system> for the
service.
− Click Accept.
− On the Edit Service Business System Assignment window,
type the <BSG Service Handle value>.
− Click Accept.
− On the Define Digital Service window, click Identification.
− Click Accept.
9 Route the service. The DAC 6000 now has the MPEG service
numbers associated with the MPS Trans-Remux D12 input ports and
the service locations defined for the output ports. The input port is
connected to the output port by routing an MPEG service number to
a service location.
Access the Route Services window with: DAC 6000 Main Menu >
Manage Devices > Define MPS.
− Click Select.
− Click Name; invokes Zoom: Device Name window.
− Scroll to and highlight the <target device name>.
− Click Accept.
− On the Define MPS window, click Accept.

11-5
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

− Click Route Services; invokes the Route Services window,

which shows the existing routes for the currently selected
MPS Trans-Remux D12 device.
To add a route to a service location of a specific output port:
− On the Route Services window, click All to de-activate
(hollow) it.
− Click Name; invokes the Zoom: Port Names window.
− Scroll to and highlight the <output port name>.
− Click Accept.
− On the Route Services window, click Add; invokes the Edit
Route Service window.
− Click Output: Source Name/Provider Name/MPEG SN;
invokes the Zoom: Source Name/Provider Name/MPEG SN
window.
− Scroll to and highlight the <output target row for the
appropriate service location previously defined for this
device and port>.
− Click Accept.
− Click Input Port; invokes the Zoom: Port Names window.
− Scroll to and highlight the <input port that carries the
service you want to route through the MPS
Trans-Remux D12 device>.
− Click Accept.
− On the Edit Route Service window, click Input: Source
Name/MPEG SN; invokes the Zoom: Source Name/MPEG
SN window.
− Scroll to, and highlight the <service number for the
service you want to route through the MPS
Trans-Remux D12 device>.
− Click Accept.
− On the Edit Route Service window, click Accept.

Deleting a Route
A route is automatically deleted when you delete the service location
that was the route’s endpoint. A route can also be deleted as follows:
1 Access the Route Services window with: DAC 6000 Main Menu >
Manage Devices > Define MPS.
2 Click Select.

11-6
 Re-acquiring ACP Addresses DAC 6000 Release V2.97 Quick Start Guide

3 Click Name; invokes Zoom: Device Name window.

4 Scroll to and highlight the <target device name>.
5 Click Accept.
6 On the Define MPS window, click Accept.
7 Click Route Services; invokes the Route Services window.
8 On the Route Services window, click Select.
9 Scroll to and highlight the <target row in the Associated Services
panel>.
10 Click Delete.

11 Click Accept.

Re-acquiring ACP Addresses

The DAC 6000 is not capable of dynamically resolving an MPS
Trans-Remux D12 configuration change from non-cascaded to cascaded
mode (or vice-versa) when set on the MPS Java-enabled console. When
this occurs, you must re-acquire ACP addresses as follows:
1 Power cycle the MPS Trans-Remux D12.

Never reboot the MPS Trans-Remux D12 device using the

Java-enabled console or from the DAC 6000.
2 After power cycling the MPS, ensure the DC POWER OK and
CONFIGURED LEDs are active. The AUTHORIZED LED should also be
active if the MPS is queuing a fully encrypted service.
3 On the DAC 6000, access the Define MPS window with: DAC 6000
Main Menu > Manage Devices > Define MPS.
4 On the Define MPS window, click Select.
5 Click Name; invokes the Zoom: Device Name window.
6 Scroll to and highlight <target device>.
7 Click Accept.
8 On the Define MPS window, click Accept.
9 Click Re-Acquire ACP Addresses.
10 Click Yes to the Confirmation window that pops-up.

11 On the Define MPS window, click Exit.

11-7
 Section 12
Interactive Ser vice Configuration

Interactive support provides the billing system the capability to

enable/disable the INTERACT resource for a digital set-top terminal
through standard Wirelink commands (for example, 660, 662, 663, 664,
666 and 760).

Interactive Config Message

When the INTERACT resource is authorized or de-authorized for a
digital set-top through the billing system or the Authorize
Objects/Resources window, the interactive capability is enabled or
disabled.
When a digital set-top is enabled for interactivity through Wirelink
commands or the Authorize Objects/Resources window, the
DAC 6000 automatically sends an interactive config message to
the set-top.
If a set-top is disabled or deleted through Wirelink commands or the
Authorize Objects/Resources window, an interactive config message
is sent to the set-top to disable the interactive capability.
If a set-top is re-activated, the set-top is automatically enabled for
INTERACT if it was previously authorized for interactivity.

Enabling a Set-top to Use Upstream/Downstream IDs

Each interactive upstream and downstream ID is associated with an
RPD 1000 channel and OM 1000 respectively. By default, the DAC 6000
creates a unique upstream and downstream interactive ID for each
RPD 1000 channel and OM 1000 in the system. A digital set-top must be
enabled for interactivity to use the ID values. The values can be viewed
and updated using ISQL commands as follows:
Select * from rpd_channel (shows each RPD 1000, card slot, and
interactive upstream ID)
Select * from downstream_plant (shows each OM 1000 and
interactive downstream ID)

12-1
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Authorizing/De-authorizing INTERACT
When the database upgrade is performed, the INTERACT resource is
inserted into the database with an external handle of 0 for the default
billing system. A non-zero return status in the range of 520-2048 will be
returned for this operation, but it does not indicate an error. The value
returned is the tier that was assigned to the INTERACT resource. The
script will also authorize the INTERACT resource for each digital set-top
that previously had interactivity enabled.

You must coordinate the upgrade with the billing systems; after the
INTERACT resource has external handles defined; any Wirelink
commands that authorize services (for example, 660, 662, 664 and 760)
have the potential to clear the interactive capability from the set-top.
The following steps must be performed in conjunction with the database
upgrade:
1 Bring down the Wirelink interface to the billing systems.
2 Shut-down the DAC 6000 application software.
3 Upgrade the DAC 6000 to Release V2.97.x.
4 Restart the DAC 6000 software application.
An external handle must be assigned to the INTERACT resource for
each billing system that will enable/disable the interactive
capability. The external handles to be used must be defined by the
MSO in conjunction with each billing system.
5 Access the Define Resource window with: DAC 6000 Main Menu >
Manage Services > Define DCT Resource > Define Resource.
To add a billing system that will enable/disable interactive
capability (must be performed for each billing system added):
− On the Define Resource window, click Add.
− Click Name; invokes the Zoom: Object Name window.
− Scroll to and highlight INTERACT.
− Click Accept; the Name and Version fields are updated on
the Define Resource window.
− On the Define Resource window, click Business Systems in
the Active Panel.
− In the Table Operation panel, Click Add; invokes the Edit
Resource/Software Object Business System window.

12-2
Authorizing/De-authorizing INTERACT DAC 6000 Release V2.97 Quick Start Guide

− Click BSI Name; invokes the Zoom: Business System

Names window.
− Scroll to and highlight the <target business system>.
− Click Accept.
− Type a value (must be greater than 32767) for the BSG
Service Handle.
− Click Accept.
− When all of the business system handles have been defined,
click Identification on the Define Resource window.
− Click Accept.
To change a billing system that will enable/disable interactive
capability:
− On the Define Resource window, click Select.
− Click Name; invokes the Zoom: Object Name window.
− Scroll to and highlight INTERACT.
− Click Accept; the Name and Version fields are updated on
the Define Resource window.
− On the Define Resource window, click Accept.
− Click Business Systems in the Active Panel.
− Click Select in the Table Operation panel.
− Scroll to and highlight a <billing system name>.
− Click Change in the Table Operation panel; invokes the Edit
Resource/Software Object Business System window.
− Click BSI Name; invokes the Zoom: Business System Names
window.
− Scroll to and highlight the <target business system>.
− Click Accept.
− Type a value (must be greater than 32767) for the BSG
Service Handle.
− Click Accept.
− On the Define Resource window, click Identification.
− Click Accept.
6 For each billing system that has an external handle defined for the
INTERACT resource, authorize all of the set-tops that were
previously enabled for interactivity.
7 Bring up the Wirelink interface to the billing system. The DAC 6000
is now ready to receive Wirelink commands to enable/disable the
interactive capability.

12-3
 Section 13
Code Download

Object Definition and Code Download Procedure

This procedure is valid for DCT 1000/1200/2000 firmware version 7.52 or
greater and all Advanced Set-top Boxes (ASTBs) such as the DCT 5000,
DCT 5100, DCT 5200, DVi 3000, DVi 4000, and DVi 5000.
As shown in the illustrations that follow, there are two phases⎯object
definition and object assignment⎯to implementing a code download:
Object Definition
− The object to be downloaded is associated with its source
files.
− The background service is created that associates the object
to the applicable OM 1000(s), business system, and Virtual
Channel Maps (VCMs) of the targeted set-tops.
− The object is identified to the RADD 6000(s).

Identify to the RADD 6000(s) what is to be downloaded

DAC 6000 RADD 6000

(object) (object)

Define source

Define background service

13-1
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Object Assignment
− The object is downloaded to the RADD 6000(s).
− The targeted set-tops are specified.
− The download start/end date and time are specified, as well
as the repetition rate.
− The object is downloaded to the targeted set-tops.

Assign object to RADD 6000(s), specify targeted set-top(s),

download start date/time and repetition rate, then download object to targeted set-top(s)

Media RADD 6000

DAC 6000
(Floppy or (object
(assignment)
CD-ROM) assignment)

Define software object

Assign software object

Specify decoder conditionals

OM 1000(s)

Targeted DCT*
population

Targeted DVi*
population

13-2
Object Definition and Code Download Procedure DAC 6000 Release V2.97 Quick Start Guide

Presentation Order
Validating the object name.
Copying the Object Files
Define Source
Define Background Service
Define Software Object
Assign Software Object
− Verifying and Troubleshooting the Code Download
Delete Software Object
− Verifying Deletion of the Software Object and Code
Download
Changing a Software Object Assignment Destination

Validating the Object Name

Ensure the name assigned to each object matches the name assigned by
the manufacturer. For example, a platform object for the DCT 2000
version would be 0_8_0673, where 0 is fixed, 8 indicates the ROM-ID,
and 0673 is the new code version.

Copying the Object Files

From the media source (CD-ROM, floppy disk, or ftp), copy the four files
(filename.dat, filename.obj, filename.oca, and
filename.ecd), to the home/acc4000d/dls/data directory.
Typical filenames are: UPC_0518, BP_OB450. Filename.oca and
filename.ecd are applicable only to ASTBs.

Define Source
This procedure is the first step in identifying the objects for the database
that will be loaded from media (CD-ROM, floppy disk, or ftp). It is used
to create a source of type application for the code objects or ir_blaster, if
IR Blaster is configured. It is not necessary if a predefined source is
used.
1 From the DAC 6000 Main Menu, click Manage Services.
2 From the Manage Services window, click Define Source.
3 On the Define Source window, click Add.

13-3
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

4 Type a <source name>.

5 Select Application or IR Blaster, as applicable, for the Source
Type.
6 Click Accept.

Define Background Service

For a set-top to acquire a code object, the code object must first be
associated to a background service. The background service must also be
in the channel map assigned to the set-top. Create a background service
using the source name assigned on the Define Source window. If the code
download background service that will be used to transmit the code
object already exists, then go to the Define Software Object procedure.
1 From the Manage Services window, click Define Background
Service.
2 On the Define Background Service window, click Add.
3 Click Source and Provider Name.
From the Zoom: Source Name window that displays, select the
<source name> that was typed in step 4 of the Define Source
procedure.
Click Accept.
From the Zoom: Provider Name window, select the same
<name> used for all other services.
Click Accept.
4 On the Define Background Service window, click the Location radio
button (filled).
5 In the Table Operations panel, click Add.
6 On the Edit Background Service Location window, create a service
location entry for each OM 1000 that will pass this service. Type a
unique number (value from 1 to 65536) in the MPEG Service #
field. This number must not be in use by other existing background
service.
7 Leave Queuing State at Queuing Enabled.

13-4
Object Definition and Code Download Procedure DAC 6000 Release V2.97 Quick Start Guide

8 Click Queuing Device.

Select the <applicable OM 1000> from the Zoom: Device Name
window that appears.
Click Accept.
9 On the Edit Background Service Location window, leave the Port
Name empty.
10 Click Accept.

11 On the Define Background Service window, click the Business

Systems radio button (filled).
12 In the Table Operations panel, click Add.

On the Edit Service Business System Assignment window, click

BSI Name and select the applicable <business system name>
that appears in the Zoom: Business System Names window.
On the Zoom: Business System Names window, click Accept.
13 On the Edit Service Business System Assignment window, type a
<value> for the BSG Service handle.
14 On the Edit Service Business System Assignment window, click
Accept.
15 On the Define Background Service window, click the Identification
radio button (filled).
16 Click Accept and verify a pop-up error window does not appear. If a
pop-up error occurs, check the dev_log for messages and verify all
service numbers (MPEG, BSG, etc.) are unique on the system.
17 After successfully creating a background service assign it to all
channel maps that will carry this service; click Assign to Virtual
Channel Map.

This step is necessary even if performing bootcode downloads of

this file version.
18 On the Assign to Virtual Channel Map window, click Add.

19 On the Edit Assign to VCM window, click VCM Name/Status.

Select a <channel map> from the Zoom: VCM Name/Status

window.
On the Zoom: VCM Name/Status window, click Accept.

13-5
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

20 On the Assign to Virtual Channel Map window, click Accept.

21 In the Assign Virtual channel Map window, click Select and in the
Object Information panel, select the <VCM Name> (for example,
vcm1). The Channel Map should indicate Not Built, as a new
(background) service is being added to it.
22 In the Assign to Virtual Channel Map window, click Build Channel
Map (invokes the Build This Channel Map popup).
23 Click Yes.

24 In the Assign to Virtual Channel Map window, click Refresh to see

the status change from Not Built to Building, and then eventually to
Built.
25 In the Assign to Virtual Channel Map window, click Exit.

26 In the Define Background Service window, click Exit.

Define Software Object

The object is added to the DAC 6000 from the Define Software Object
screen-set and then loaded to the applicable RADD 6000s that service
the targeted set-tops. In most cases, the code object will be loaded to all
of the RADD 6000s.
To define a software object and load it:
1 From the Manage Services window, click Define Software Object.
2 On the Define Software Object window, click Add.
3 In the Object Name field, type the <object name>.
4 Type the <Version> of this file in xx.yy format (for example, 05.18).
5 Select PROS, Standard, Base Platform, ASTB Application
Data, or IR Blaster, as applicable, for Group.
6 Type a <filename> in the File Name field (this name must be
identical to the filename.obj name on the medium or in the dls/data
directory).
7 Type a <rate> in the Insertion Rate field:
Standard = 50
PROS and Base Platform = 200
IR Blaster and ASTB Application Data = 1

13-6
Object Definition and Code Download Procedure DAC 6000 Release V2.97 Quick Start Guide

8 Click the Business Systems radio button (filled).

9 In the Table Operations panel, Click Add.
10 On the Edit Resource/Software Object Business System window,
click BSI Name.
On the Zoom: Business System Names window, select the
applicable <business system>.
On the Zoom: Business System Names window, click Accept.
11 On the Edit Resource/Software Object Business System window,
type a <BSG Service Handle value>.
12 Click Accept.
13 On the Define Software Object window, click the Identification
radio button (filled).
14 Click Accept.
15 If the object is not already loaded in the home/acc4000d/dls/data
directory, insert the floppy disk or CD-ROM in the applicable device;
otherwise, go to step 16.
16 On the Define Software Object window, click Load Software
Object to read in the attributes from the applicable filename.dat
file.
17 On the Load Software Object window, type the <filename without
extension> in the field provided (for example, for the UPC_0518.dat
file, type UPC_0518).
18 For Medium, select the applicable <device>; otherwise, choose
Loaded if the filename.dat file is already in the
/home/acc4000d/dls/data directory.
19 On the Load Software Object window, click Accept.
20 On the Define Software Object window, click Display Attributes.
Ensure the information in the Edit Software Object Attributes
window is correct and not corrupted, especially in the
Class, Storage, and Type fields.
ASTB objects undergo PROS processing prior to shipment. For
these set-top types, when PROS is the selected group, ensure the
ID field is not NULL and is greater than zero.
There are no attributes associated with an IR Blaster object if it
is the selected group.
21 On the Display Software Object Attributes window, click Exit.

13-7
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Download Software Object to the RADD 6000(s)

1 On the Define Software Object window, click Download Software
Object.
2 On the Download Software Object window, click Add.
3 On the Edit Download Software Object window, deselect All (not
filled) if downloading to a single RADD 6000, and then:
Click Name.
On the Zoom: Device Name window, select the applicable
<RADD 6000> device.
On the Zoom: Device Name window, click Accept.
4 On the Edit Download Software Object window, click Accept.
5 On the Download Software Object window, click Accept.
6 On the Define Software Object window, click Accept, and then click
Exit.

Assign Software Object

To download a software object, the defined object must be linked to the
defined service by creating an object assignment. The assignment
instructs the system how to address the code object, when to start and
stop it, and what data rate to use. It is prudent to target a single set-top
to initiate a new code object, even if implementing decoder conditionals,
to ensure it functions as anticipated. After the code download is verified
on the single set-top, it is safe to switch the destination to broadcast.

Whenever a change is made to an object assignment, it must be

downloaded to the RADD 6000 again to update the targeted set-top(s).
Code downloads for the DCT 1000/1200/2000, DCT 5000/5100/5200, and
DVi 3000/4000/5000 have minor differences. Unlike the
DCT 1000/1200/2000, ASTBs must first receive a base platform code
object to enable its base features.

For ASTBs, the base platform and application operating system are
combined into one object; therefore, they can be downloaded under the
base platform option.

13-8
Object Definition and Code Download Procedure DAC 6000 Release V2.97 Quick Start Guide

To assign a code object:

1 From the Manage Services window, click Assign Software Object.
2 On the Assign Software Object window, click Assign Type.
3 From the Zoom: Assign Type window, select as applicable:
Include Object (DCT 1000s/1200s/2000s) – is an upgrade
download.
Delete Object - removes a code object from targeted set-tops.
The delete object can be broadcast to all set-tops, targeted to a
group of set-tops with a broadcast plus decoder conditional, or
targeted to a single set-top. This assignment does not require a
service.
Include Base Platform (ASTBs) - is used for the non-upgrade
bootcode control type download.
Include Base Platform Upgrade (ASTBs) - is used for the
ASTB and OCAM type download, referred to as upgrading.
Purge Object - enables removal from the targeted set-tops
previous versions of code objects under the same object name.
The purge can be broadcast to all set-tops, targeted to a group of
set-tops with a broadcast plus decoder conditional, or targeted to
a single set-top. This assignment does not require a service and
works only if the object names match. For example, if targeted
set-tops contain the objects PLAT2000 version 07.52 and
PLAT2000 version 06.73, purging object name PLAT2000 will
remove version 06.73 from the set-tops.
Include ASTB Application Data Object (ASTBs) – for VOD
data objects.
Include Code Suite – the object must first be defined as a code
suite.
Enable Object – sends a message down the EMM PID stream
to restart a disabled code object in the set-tops.
Disable Object – sends a message down the EMM PID stream
to disable a currently enabled object.
4 On the Zoom: Assign Type window, click Accept.
5 On the Assign Software Object window, click Add.

13-9
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

6 On the Edit Assign Software Object window, click Object Name.

On the Zoom: Object Name window, scroll to and highlight the
target Object Name, Object Version, Object Group row.
Click Accept.
7 Click Source & Provider Name to invoke the Zoom: Service &
Provider Name window. From the Zoom window, select the <service
that was created in the Define Background Service window or
an existing service that does not currently have a code object
assigned to it>. If selecting an existing service, it must be assigned
to the channel map(s) of the targeted set-tops.
On the Zoom: Service & Provider Name window, scroll to and
highlight the target <Service Name and Provider Name> row.
Click Accept.
8 On the Edit Assign Software Object window, click the Description
field and type a <download description>.
9 On the Edit Assign Software Object window, type the <Platform
ID> if Include Base Platform was selected; otherwise, go to step 9.
Platform IDs are as follows:
DVi 3000 36
DVi 4000 256
DVi 5000 32
DCT 5000 598
DCT 5100/5200 599
DCT 5100 (with DVI interface) 601
10 On the Edit Assign Software Object window, modify the <Start> and
<Stop> times as necessary. The Start and Stop times default to now
and max GPS time.
11 On the Edit Assign Software Object window, For ASTBs, Auto
Enable (filled) and Auto Purge (filled) should be selected.

13-10
Object Definition and Code Download Procedure DAC 6000 Release V2.97 Quick Start Guide

12 If setting up a targeted (non-broadcast) Include Base Platform

Upgrade download, click the Destination radio button (filled) on the
Edit Assign Software Object window. (This step is not applicable for
Include Base Platform downloads, as the destination type must be
Broadcast with no decoder conditionals for ASTB set-tops. These
set-tops can only receive broadcast messages when trying to load
their respective base platforms for the first time.)
13 On the Edit Assign Software Object window Destination panel, select
either Broadcast or Terminal as the destination. It is
recommended that a single set-top destination be selected when
setting up a code download service for the first time. After the
download is verified as working correctly, the destination can be
changed to broadcast.
14 Select a defined Decoder Conditional Name if applicable. (See
“Decoder Conditional Expressions,” which follows the code download
procedure in this section of the book.)
15 On the Edit Assign Software Object window, click Include Delete.

16 On the Table Operation panel, click Add.

17 On the Edit Include Delete window, click Object/Resource Name.

On the Zoom: Object Name window, select the <object that

must be removed from the set-tops> so the new object can
function properly. (For example, the current version of the EPG
might have to be removed to load a new version of the operating
system.)
Click Accept.
18 On the Edit Include Delete window, click Accept and repeat step 17
for each object that must be deleted.
19 On the Edit Assign Software Object window, click Identification.

20 Click Accept.

21 The object just created should now appear on the Object

Information panel of the Assign Software Object window.
22 Prior to downloading the assignment to the RADD 6000, it is
recommended that the assignment and object load status first be
reviewed. On the Assign Software Object window, click Select and
highlight the <assignment just created>.

13-11
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

23 Click Display Detail Assignment. On the Display Detail

Assignments window all statuses should indicate in progress
(pending download). Verify there is an entry for the conditional tune
code object, object enable, and any delete streams (for ASTBs, it will
be identified as a boot code or ASTB tune message).
24 On the Display Detail Assignments window, click Exit.

25 On the Assign Software Object window, click Display Object Load

Status to ensure the object has been downloaded to each
RADD 6000 (Load Status indicates Complete).
It takes longer (approximately 10 minutes or more) for ASTB objects
to download to the RADD 6000(s).
26 Click Refresh Screen periodically until Complete appears for Load
Status.
27 Click Exit.

28 On the Assign Software Object window, click Select and again

highlight the assignment just created.
29 Click Load Object Assignment (the RADD 6000 starts spooling
code and appropriate commands).
30 Click Yes to the confirmation window (“Load this object
assignment?”) that appears.
31 Click Display Detail Assignment and verify status is Complete
for all items.

V er i fyi ng and T roub le shoo ti ng t he C ode Down load

To verify the code download:
1 From the DAC 6000 Main Menu, click Manage Operations.
2 From the Manage Operations menu, click Control Operations.
3 On the Control Operations window, in the Filter Type panel, deselect
All Types (hollow) and then click Code Download (filled).
4 Click Accept.
5 On the Control Operations window Database Operations panel,
click Select.
6 On the Operations panel, scroll to and highlight the <target
operation>.

13-12
Object Definition and Code Download Procedure DAC 6000 Release V2.97 Quick Start Guide

7 The Status column should indicate Active; if not, click the Retry
Operation radio button.
8 Click Display Detail Operations and verify all operations indicate
Active.
9 When initially downloading to a single set-top, on the targeted
set-top verify the code object is loading or has loaded. The set-top
will first tune to the object, and then it will wait for the appropriate
synch point and begin to load the object.
10 Using the set-top onscreen display, verify the object is successfully
loaded and enabled.
11 If problems still exist, on the Control Operations window, click
Pause Operation, repeat steps 1 through 6, and then click Resume
Operation.

Delete Software Object

Object files in the /home/acc4000d/dls/data directory for the
software object that is being deleted from the DAC 6000 database are also
deleted from this directory as part of delete software object processing. If
you intend to redefine and reload this same object, ensure that the files in
the /home/acc4000d/dls/data directory are first saved before
performing the delete. Save the files by creating a hold directory, and
copying the files into this directory.

If the software object being deleted was assigned to multiple

RADD 6000s for download, then deleting this object will cause the code
downloads on all of the RADD 6000s to be deleted.
To delete a software object:
1 From the Manage Services window, click Define Software Object.
2 On the Define Software Object window, click Select and then click
Object Name.
From the Zoom: Object Name window, select the <object> to be
deleted.
Click Accept.
3 On the Define Software Object window, click Accept, which causes
data to be populated on the window fields.

13-13
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

4 Click Delete, and then click Yes when the confirmation window
(Delete this software object?) appears.
5 On the Define Software Object window, click Exit.

V er i fyi ng De le ti on o f t he S o f twa re O bje c t a nd Co de D ownl oad

To verify deletion of the software object and code download:
1 From the DAC 6000 Main Menu, click Manage Operations.
2 From the Manage Operations menu, click Control Operations.
3 On the Control Operations window, in the Filter Type panel, deselect
All Types (hollow) and then click Code Download (filled).
4 Click Accept.
5 On the Control Operations window, Database Operation panel, click
Select.
6 On the Operations panel, scroll to and highlight the code download
operation for the object just deleted. The status should indicate
Deleted.
7 From a DAC 6000 system window, go to the
/home/acc4000d/dls/data directory and verify that the software
files were deleted.

Changing a Software Object Assignment Destination

The assignment destination (for example, single terminal versus
broadcast) can be changed at any time. However, once a change is made
to an assignment, it must be downloaded to the RADD 6000(s) again for
it to take affect.
To change a software object assignment destination:
1 From the Assign software object window, click Select.
2 Highlight the <target object row> in the Object Information panel.
3 Click Accept.
4 Click Change.
5 On the Edit Assignment Software Object window, edit all necessary
Identification fields and then click Destination.
6 On the Edit Assignment Software Object window, edit all applicable
Destination fields and then click Identification.

13-14
Object Definition and Code Download Procedure DAC 6000 Release V2.97 Quick Start Guide

7 Click Accept.
8 On the Assign Software Object window, click Select and again
highlight the assignment just edited.
9 Click Load Object Assignment.
10 Click Yes to the confirmation window (“Load this object
assignment?”) that appears.

13-15
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Decoder Conditional Expressions

Code download messages can be addressed to specific sets of terminals
using decoder conditional expressions. A decoder conditional expression
contains conditional terms with parenthetical arguments, and when
necessary, logical operators. A decoder conditional expression can be
used with other addressing modes, such as broadcast or multicast, etc.

Defining and Assigning a Decoder Conditional Expression

A decoder conditional expression is defined on the Define Decoder
Conditional window, which is accessed with:
DAC 6000 Main Menu > Manage Terminals > Define Decoder
Conditional.
The defined decoder conditional expression is assigned on the
Destination panel of the Edit Assign Software Object window, which is
accessed with:
DAC 6000 Main Menu > Manage Services > Assign Software Object >
Edit Assign Software Object (Destination panel).

Decoder Conditional Expression Terms

The following terms (with parenthetical arguments) are available for
decoder conditional expressions:
channel_locked_out( )
free_preview( )
enabled_for_ippv( )
tvpc_problems( )
too_late_to_buy( )
full_encryption( )
support_mode( )
connected( )
analog( )
subscribed(program_epoch_number)
authorized(program_epoch_number)
authorizable(program_epoch_number)
bought(program_epoch_number)
can_buy(program_epoch_number)
circular_blacked_out(program_epoch_number)

13-16
Decoder Conditional Expressions DAC 6000 Release V2.97 Quick Start Guide

regional_blacked_out(program_epoch_number)
ippv_problems(program_epoch_number)
rating_locked(program_epoch_number)
taping_allowed(program_epoch_number)
interstitial_period(program_epoch_number)
region(region_id)
tvpc_version(TvPC_version)
category_sequence(sequence_number)
unreported_purchases(num_purchases)
currency_region(currency_region_id)
rating_region(rating_region_id)
auth_state(state)
multicast_address(address)
credit_balance(credit_balance_threshold)
group_inclusion(group_id)
tsoda_version(version_num)
snap_version(version_num)
dena_version(major, minor)
rom_id(rom_id or platform_id)
family_id(family_id)
model_id(model_id)
time_zone(time_zone_id)
package_purchase(package_provider_id, package_id)
country_code(country_code)
current_channel(current_VCT_id, current_virtual_channel)
tier_match(category_sequence, tier)
appl_version(application_id, application_version_level)
circle(circle)
program_purchase(service_provider_id, epoch_start_time, source_id)
acp_generic(acm_termLength, test_id, generic_term[ ] )
activation_time(activation_time)
on_off (reserved – recommend the value 0 be used)
vct_id(VCT_id)
os_type(application_OS_type, code_active_status)
application_priority (reserved – recommend the value 0 be used)

13-17
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Decoder Conditional Expression Logical Operators

You can combine terms using logical operators:
and
or
not
For example: family_id(1) and model_id(1)
For clarity, and to minimize the possibility of creating an erroneous
expression, offset complex operations with parentheses:
(family_id(1) or family_id(2)) and not enabled_for_ippv()

13-18
 Section 14
RF Polling

Poll data is redundant in the system to ensure purchases are not lost in
the event there are hardware, software, or related equipment problems.
During a poll, the set-top still retains the data after the DAC 6000
collects it. The DAC 6000 retains the data while it is being uploaded to
the billing system. The purchase history is cleared from the set-top and
is removed from the DAC 6000 only after the billing system
acknowledges that the data has been successfully uploaded. Purchases
become orphaned (cannot be authenticated and therefore unrecoverable),
as determined by a preselected time interval (for example, 60 days).

Although several polls can be initiated at one time on a DAC 6000

system, to reduce the possibility of data interference, run one poll at time.
Purchases are not lost or corrupted from polling data interference.

Systems with Multiple RADD 6000s

For multi-RADD 6000 systems, if the poll start time is the same for all of
the RADD 6000s, then the poll definition does not need to contain a
specific RADD 6000. The DAC 6000 maintains and tracks the poll across
all of the RADD 6000s. The DAC 6000 also maintains the poll statistics
per RADD 6000 and all of the RADD 6000 statistics are summed
together.

Poll Retry Count

It is recommended that the poll retry count be set to zero (0). This value
instructs the RADD 6000 to try polling set-tops again when there is no
response. In most cases, set-tops do not respond because the power level
is wrong, or because they are incapable of responding (for example,
power plug is removed from receptacle). Polling set-tops again usually
does not improve the response rate, but adds another second per set-top,
which equates to 5.5 additional poll hours per 20,000 set-tops.

14-1
DAC 6000 Release V2.97 Quick Start Guide „ Addressable Controller System Documentation

On-plant/Off-plant Status Designators

For more expedient poll times, do not indiscriminately assign set-tops to
on-plant; only set-tops in subscribers’ residences should be designated
on-plant. Every on-plant set-top is polled; therefore, a large population of
set-tops on a single RPD 1000/2000 channel erroneously designated
on-plant will dramatically increase poll time. For example, a warehouse
demod card with 20,000 on-plant set-tops requires 5.5 hours to complete
a non-power level poll and 38 hours to complete a power level poll. Even
if all other RPD 1000/2000 demod cards finish in just two hours, the poll
will still continue until the warehouse demod card is complete.
If it is unavoidable that the warehouse demod card has a large number
of set-tops designated on-plant, yet not connected, designating the
demod card off-line can still reduce poll time. Any demod card
designated off-line does not participate in a scheduled poll. It will,
however, still participate in all billing operations. This can remove
several hours from the overall poll time.

RF Poll Schedule
The recommended RF poll schedule is as follows:
RF Pol l Schedu le
Type Frequency Priority Comments
Global Daily Medium Polls can be run anytime but it is best to run polls outside the normal business
(non-power (warehouse) shifts. Run polls until they are complete, as premature termination can
leveling) cause higher non-responder rates in the unpolled population.
Power level Weekly Low The power level poll can take up to two days to complete on very large systems.
for non- (every
responders 7 days) The RPD 1000/2000 demod card power level ranges should be defined to include
realistic minimum and maximum amplitudes. The factory default is 24 to 60. Most
cable plants do not respond at 24. If this is true, the power level range should be
redefined. Setting the minimum value to 32, for example, will remove 2 seconds from
every terminal in a power level poll. Spreading this time savings across 20,000 set-tops
will reduce the poll duration by 11 hours.
Auto- Suspect that N/A This poll is an option only for multi-RADD 6000 systems and typically is not required, as
discovery set-tops upstream auto-discovery is always active for all purchase and diagnostic polls. The
have been DAC 6000 manages each RADD 6000 set-top population to accommodate set-top
mis-assigned additions and deletions. An auto-discovery poll should be defined and initiated only
to a when it is determined that a group of set-tops were erroneously assigned to a
RADD 6000 RADD 6000. When specifying an auto-discovery poll, the poll attributes should select
the smallest grouping of set-tops as possible, for example, all non-responding set-tops
on Upstream Plant 1.

14-2
 Section 15
Te l c o R e t u r n

Setting up the RADD 6000 for Telco Return requires configuring the
PortServer IIs dedicated to the RADD 6000, as well as the Telco Return
modems and the RADD 6000 itself.

Configuring a PortServer II Using digi_rename

The individual ports on the PortServer II are designated as ttya1-ttya16.
Up to three expansion PortServer IIs can be added to support a total of
64 ports (ttya1-ttya64) on a single Ethernet connection. Running
digi_rename provides the capability to configure up to 15 PortServer IIs,
with each one having up to three expansion units. Fully populated local
device/port names are ttya1-ttya64 through ttyo1-ttyo64 for
PortServers IIs 1-15 (each with three expansion PortServer IIs).

The RADD 6000 must have its own dedicated PortServer IIs for Telco
Return; it cannot share the PortServer IIs on the DAC 6000.
Reference the PortServer II Hardware Installation Guide for installation
instructions. If a PortServer is used in lieu of a PortServer II, ensure the
Ethernet switch on the side of the unit is set to twisted pair.
The digi_rename utility is used to configure the number of RADD 6000
PortServer IIs, and each PortServer II’s MAC address, IP address, and
host name. The MAC address is located on the bottom of the
PortServer II, in xx:xx:xx:xx:xx:xx format.
1 At the radd6000 console login prompt, type radd6000 .
2 Type your <password> at the password prompt.
3 At the radd6000:/export/home/radd6000% prompt, type
radd_rename .
4 Type your <password> at the Enter the Root Password prompt.
5 Type 4 to select Run digi_rename.
6 Type the <MAC address> of the first PortServer II.
7 Type the <IP address> of the first PortServer II.
8 Type the <host name> of the first PortServer II.

15-1
DAC 6000 Release V2.97 Quick Start Guide „ Addressable Controller System Documentation

9 Type the <number of expansion ports> connected to this

PortServer II.
10 Repeat steps 6 through 9 for each PortServer II.

In the digi_rename session example that follows, defaults are taken

for all entries:

# digi_rename
****************************************
PORTSERVER INTERFACE VERSION 1.0.4
****************************************
***************************** Version 1.0.4 ********************************
This program will prompt the user to enter the number of
PortServers, PortServer's MAC ADDRESS, IP ADDRESS, and HOST NAME.
****************************************************************************
Enter the total number of PortServers connected [2]:
Enter the MAC (Ethernet) address of First PortServer [0:40:9D:20:ED:C9]:
Enter the IP address for First PortServer [192.1.15.185]:
Enter the host name for First PortServer [port1]:
Enter the number of expansion ports connected to this PortServer [1]:

Enter the MAC (Ethernet) address of Second PortServer [0:40:9D:21:6C:59]:

Enter the IP address for Second PortServer [192.1.15.186]:
Enter the host name for Second PortServer [port2]:
Enter the number of expansion ports connected to this PortServer [0]:

The following information will be used to configure PortServers:

PORTSERVER MAC ADDRESS IP ADDRESS HOSTNAME EXPANSIONS

---------- ----------- ---------- -------- ----------
1 0:40:9D:20:ED:C9 192.1.15.185 port1 1
2 0:40:9D:21:6C:59 192.1.15.186 port2 0
Enter c to continue, e to exit, or <Enter> to re-enter: c
pkill -9 ncxd
*****************************************************************************

IMPORTANT NOTES:
----------------
PLEASE, FOLLOW THE FOLLOWING INSTRUCTIONS TO RESET THE PORTSERVERS TO FACTORY
DEFAULTS (THE PORTSERVERS WILL ACQUIRE THE NEW SETUP AUTOMATICALLY):
1. Turn off the PortServer II's power switch.
2. Press and Hold the PortServer II's left and right "arrow" buttons at the same time.
3. Turn on the PortServer II's power switch.
4. Hold the PortServer II's left and right "arrow" buttons in until "CL" ("EP" on PortServer)
appears on the front panel display, then release the buttons.
5. Repeat steps 1, 2, 3, and 4 for all PortServers which are to configure.
*****************************************************************************
When all the above steps are performed, press <Enter> to continue ...
Please, wait while PortServers are configuring for RealPorts ...
**********************************************
/usr/local/bin/digi4rport VERION 1.0.1
**********************************************
************************************************************************
This program is used to configure the Digi PorServers for
RealPort. It is assumed that you have installed and properly
configured RealPort Software and PortServer Devices.
************************************************************************
****************** TEST PORTSERVERS CONNECTIONS **********************
****************** PORTSERVER "port1" IS ALIVE **********************
************ CONFIGURE PORTSERVER "port1" FOR REALPORT ****************

15-2
 Configuring Telco Return Modems „ DAC 6000 Release V2.97 Quick Start Guide

******** DONE CONFIGURING PORTSERVER "port1" FOR REALPORT *************

****************** PORTSERVER "port2" IS ALIVE ************************
************ CONFIGURE PORTSERVER "port2" FOR REALPORT ****************
******** DONE CONFIGURING PORTSERVER "port2" FOR REALPORT *************
DIGI_RENAME IS DONE. PRESS <ENTER> TO CONTINUE ...
#

11 Verify that the information displayed is correct, then type c .

12 Type su at the radd6000:/export/home/radd6000% prompt.
13 Type the <root password> .
14 Type init 6 at the # prompt to reboot the RADD 6000.

Configuring Telco Return Modems

Each modem must be connected to an RS-232 port on the back of the
PortServer II (see the PortServer II Hardware Installation Guide). Ports
ttya1-ttya16 are usually dedicated for the Telco Return modems.
To configure each modem:
1 Type stop_radd to stop the RADD 6000 application.
2 Type su to login as root.
3 Type initmodem and specify the proper port and initialization
option (Starfone-Digital).
4 After the initmodem script completes, restart the RADD 6000
application by typing start_radd .

Configuring the RADD 6000 for Telco Return

Configuring the RADD 6000 for Telco Return requires building the
phret tasklist.txt file with the required port/protocol and
timing/retry line entries. The accisql utility must also be implemented to
set the dial time interval of the Telco Return modems.

ph re t In te r fac e Task
A modem interface task (phret) must be configured by PortServer II port
designator (for example, ttya1) for each Telco Return modem. This
configuration information is supplied to the modem interface task on its
command line at startup. There must be a separate line in the
tasklist.txt file for each phret task attached to a port.

15-3
DAC 6000 Release V2.97 Quick Start Guide „ Addressable Controller System Documentation

default values. The performance characteristics are of two types:

port/protocol and timing/retry.
The port/protocol characteristics are all set simultaneously with a single
command line argument. This argument must be present or the phret
task will not execute.
The format of a port/protocol tasklist.txt file entry is as follows:
phretx phret /dev/ttyxx:baud:d:s:p
phretx The name used to reference the task for inter-process messaging in
the RADD 6000
phret /dev Task and device specifier (does not change)
xx Multiplexer port specifier (for example, a1)
baud Baud rate (300 is currently used for the RADD 6000)
d Number of data bits (8 is currently used for the RADD 6000)
s Number of stop bits (1 is currently used for the RADD 6000)
p Parity specifier (E, for even, is currently used for the RADD 6000)
A typical tasklist.txt file line is:
phret1 phret /dev/ttya1:300:8:1:E
where phret1 is the name used to reference the task for inter-process
messaging in the RADD 6000 and the a1 (in ttya1) specifies the first port
on the multiplexer. The remaining characters set the port to 300 baud, 8
data bits, 1 stop bit, and even parity.
Within the phret task there is a group of named global variables that
control the timing and retry values used by the program when
communicating with digital set-top terminals. The variables and their
application are as follows:
Variable Default Description
Value
retry_limit 3 The number of times a command is retried.
modem_timeout 30 DCT/modem response timeout in seconds per expected
report back packet.
carrier_settle_timeout 2 Seconds to wait between the carrier and sending the first
digital set-top command.
hangup_command_timeout 2 Seconds to wait after hangup command, but before
hanging up (dropping data terminal ready [DTR]).
drop_dtr_timeout 1 Seconds DTR is dropped to hang up.

15-4
Configuring the RADD 6000 for Telco Return „ DAC 6000 Release V2.97 Quick Start Guide

The values for any of these variables can be modified by supplying

command line arguments to the phret task at its startup in the
tasklist.txt file. Typical examples are as follows:
modem1 phret -carrier_settle_timeout=5 /dev/ttya1:300:8:1:E
modem2 phret -hangup_command_timeout=4 /dev/ttya2:300:8:1:E
modem3 phret -drop_dtr_timeout=5 /dev/ttya3:300:8:1:E
modem4 phret -retry_limit=5 -modem_timeout=9 /dev/ttya1:300:8:1:E

Se t tin g th e D ial Tim e Inte rv al

The time interval must be set in the database to specify the time
between dial commands during a phone poll. The time interval is
calculated by the following formula:
poll_spacing_time = (average_call_time_seconds) /
(number_of_modems_in_bank)
where, #_of_modems_in_bank is the number of modems connected to the
rotary dialin lines.
Initially, set average_call_time_seconds to 45 and adjust as
necessary.
A typical example to set the poll_spacing_time
(tunable_int_value) for a bank of five modems is as follows:
1 Type stop_radd to stop the RADD 6000 application.
2 Type su to login as root.
3 Type accisql <username><initials> .
4 Type update tunables .
5 Type set tunable_int_value = 9 . Dividing
average_call_time_seconds (45) by number_of_modems_in_bank (5)
gives the tunable_int_value (9).
6 Type where tunable_class = “phone” and tunable_name =
“poll_spacing_time” .
7 Type go to execute the command.
8 Type exit to quit accisql.
9 After the assisql script completes, restart the RADD 6000
application by typing start_radd .

15-5
 Section 16
Adding RADD 6000s

Adding RADD 6000s to a system requires either re-assigning

downstream plants from existing RADD 6000s to the newly added units
or defining new downstream plants that are assigned to the new
RADD 6000s.

Prerequisites
Before upgrading the system with additional RADD 6000s:
Reconfigure the IP network with an isolated subnet for every
RADD 6000 to ensure broadcast traffic from each RADD 6000 is
isolated to its assigned OM 1000(s).
Ensure the linkage path for the RPD 1000/2000s is not cross-nested
into the wrong RADD 6000 assignment path: RPD 1000/2000s that
are moved with downstream plants for RADD 6000 re-assignment
cannot be linked to upstream plants which in turn are also linked to
other downstream plants.
The most recent software and new IP address must be installed on
each RADD 6000 (reference the RADD 6000 Installation and
Operation Manual for software loading and IP address assignment
procedures).
The new RADD 6000 IP addresses should be loaded on the
RPD 1000/2000s.

It is recommended you maintain the old IP address as well, in the

event it is necessary to fall back on the previous configuration if there
are any unforeseen issues moving the downstream plant to the new
RADD 6000.
Establish a list of set-top terminals that can be used as test boxes to
verify new RADD 6000 functionality.

16-1
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Multiple Plants, Single OM 1000, New RADD 6000

The RADD 6000 configuration and switchover phases for multiple plants
are as follows:

Configuration
To configure the new RADD 6000 into the DAC 6000 database:
1 Add the new RADD 6000 to the DAC 6000 host file (the RADD 6000
name cannot be longer than seven characters).
2 Add the RADD 6000 broadcast to the DAC 6000 host file with:
<RADD NAME>BA.
3 Add a new OM 1000 device to the system with a bandwidth of
500 kbps tuned to channel A1. A new OM 1000 must be created
rather than just moving it because the OM 1000 linked to the
downstream plant being moved also has other links as well. Just
moving the OM 1000 would leave the other linked downstream
plants without an OM 1000, which is an invalid configuration.
4 Define the new RADD 6000(s) on the DAC 6000.
5 Using the Define RADD window, verify that each newly added
RADD 6000 is online and connected. Do not proceed until the status
indicates an established connection.

Switchover to the New RADD 6000

To switchover to the new RADD 6000(s):
1 Refresh each test set-top to ensure that it is responding prior to the
new RADD 6000 installation for that subnet. Each two-way RF
set-top will indicate that it has been autodiscovered.
2 Send out the appropriate notifications and place the billing system
ports offline.
3 Backup the DAC 6000 database.
4 Cancel any active polls or pending polls that will start during this
procedure.
5 Pause any active Global Authorization Refresh or pending Global
Authorization Refreshes that will start during this procedure.
6 Apply network changes to isolate the new RADD 6000. Verify that
the broadcast traffic from the existing RADD 6000 is no longer seen
in the new RADD 6000’s subnet.

16-2
Multiple Plants, Single OM 1000, New RADD 6000 DAC 6000 Release V2.97 Quick Start Guide

7 Move each downstream plant from the source RADD 6000 or old
OM 1000 to the destination RADD 6000 or new OM 1000.
8 Define a Fill Only event for the new RADD 6000 (component device)
and verify the event completes successfully.
9 Define a Fill Only event for the new RADD 6000 (component
streams) and verify the event completes successfully.
10 Define a Fill Only event for the new RADD 6000 (component
terminal configuration) and verify the event completes successfully.
11 Build each channel map associated with the downstream plants that
were moved.
12 Verify that all operations for the new RADD 6000 are Active. This
only includes those operations with start times in the past. Events
with future start times should be in a Pending or Download state.
13 Switch the destination IP address on one of the RPD 1000/2000s
associated with the terminal test list to the new RADD 6000. From
the front panel of the RPD:
Change the destination host(s) name(s) to match the RADD 6000
and its corresponding IP address.
Change all destination svr (service) names to RPD2RADD and
Port/PRTCL to 5861/udp.
Save changes and reboot the RPD 1000/2000 after the selections
are made.
Verify the changes from the RPD 1000/2000 front panel.
14 Initialize the test set-top associated with the reconfigured
RPD 1000/2000 to ensure that it is still functioning correctly. (Prior
to sending the Init or Refresh command, you must first toggle the
set-top off plant then on plant from the Define Terminal window.
This is done to ensure the terminal is loaded on the new
RADD 6000.)
15 Define a Fill Only event for the new RADD 6000 (component
terminals) and verify that it is Active.

This event can take several hours to complete; however, it does not
need to be completed to continue on with this procedure. The
approximate load rate is 80,000 terminals per hour without billing
traffic and 40,000 terminals per hour with billing traffic.

16-3
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Configure the Code Download

To configure the code download:
1 Add a new service location for the new OM 1000 to each download
service on the new RADD 6000.
2 Associate new OM 1000 with the proper background services on the
new RADD 6000.
3 To add the objects to the new RADD 6000, record and then delete
current code assignments that are desired to be operating on the new
RADD 6000.
4 Select and add the objects that are to be loaded on the new
RADD 6000.
5 Using the recorded configuration data, re-create the assignments
and verify that the objects are running on all RADD 6000s.
6 Modify existing background services to remove any service locations
that contain the old OM 1000.
7 Delete the old OM 1000 from the DAC 6000 database.
8 Configure any EAS services for the new OM 1000.
9 Cold initialize a test set-top on each RADD 6000 and verify all code
objects load each set-top.

Complete the Configuration Setup

To complete the configuration set-up:
1 Configure any RPD 1000/2000s that have not been switched to point
to the new RADD 6000.
2 Define a Flush & Fill Only event for the new RADD 6000
(component device) and verify the event successfully completes.
3 Define a Flush & Fill Only event for the new RADD 6000
(component streams) and verify the event successfully completes.
4 Define a Flush & Fill Only event for the new RADD 6000
(component terminal configuration) and verify the event successfully
completes.
5 Define a Flush & Fill Only event for the new RADD 6000
(component periodics) and verify the event successfully completes.

16-4
 Single Plant, Single OM 1000, New RADD 6000 DAC 6000 Release V2.97 Quick Start Guide

6 Define a Flush & Fill Only event for the new RADD 6000
(component configuration messages) and verify the event successfully
completes.
7 Define a Flush & Fill Only event for the new RADD 6000
(component channel maps) and verify the event successfully
completes.
8 Define a Flush & Fill Only event for the new RADD 6000
(component terminal terminal) and verify the event successfully
completes
9 Re-activate BSI and start normal operations.
10 After all Flush & Fill or Fill Only activities are complete, create a
Fill Only event (component EMM) for the new RADD 6000.

Single Plant, Single OM 1000, New RADD 6000

The RADD 6000 configuration and switchover phases for a single plant
are as follows:

Configuration
To configure the new RADD 6000 into the DAC 6000 database:
1 Add the new RADD 6000 to the DAC 6000 host file (the RADD 6000
name cannot be longer than seven characters).
2 Add the RADD 6000 broadcast to the DAC 6000 host file with:
<RADD NAME>BA.
3 Using the Define RADD window, verify that the newly added
RADD 6000 is online and connected. Do not proceed until the status
indicates an established connection.

Switchover to the New RADD 6000

To switchover to the new RADD 6000(s):
1 Refresh each test set-top to ensure that it is responding prior to the
new RADD 6000 installation. Each two-way RF set-top will indicate
that it has been autodiscovered.
2 Send out the appropriate notifications and place the billing system
ports offline.
3 Backup the DAC 6000 database.

16-5
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

4 Cancel any active polls or pending polls that will start during this
procedure.
5 Pause any active Global Authorization Refresh or pending Global
Authorization Refreshes that will start during this procedure.
6 Apply network changes to isolate the new RADD 6000. Verify that
the broadcast traffic from the existing RADD 6000 is no longer seen
in the new RADD 6000’s subnet.
7 Move each downstream plant from the source RADD 6000 to the
destination RADD 6000.
8 Define a Fill Only event for the new RADD 6000 (component device)
and verify the event completes successfully.
9 Define a Fill Only event for the new RADD 6000 (component
streams) and verify the event completes successfully.
10 Define a Fill Only event for the new RADD 6000 (component
terminal configuration) and verify the event completes successfully.
11 Build each channel map associated with the downstream plants that
were moved.
12 Verify that all operations for the new RADD 6000 are Active. This
only includes those operations with start times in the past. Events
with future start times should be in a Pending or Download state.
13 Switch the destination IP address on one of the RPD 1000/2000s
associated with the terminal test list to the new RADD 6000. From
the front panel of the RPD:
Change the destination host(s) name(s) to match the RADD 6000
and its corresponding IP address.
Change all destination svr (service) names to RPD2RADD and
Port/PRTCL to 5861/udp.
Save changes and reboot the RPD 1000/2000 after the selections
are made.
Verify the changes from the RPD 1000/2000 front panel.
14 Initialize the test set-top associated with the reconfigured
RPD 1000/2000 to ensure that it is still functioning correctly. (Prior
to sending the Init or Refresh command, you must first toggle the
set-top off plant then on plant from the Define Terminal window.
This is done to ensure the terminal is loaded on the new
RADD 6000.)

16-6
Single Plant, Single OM 1000, New RADD 6000 DAC 6000 Release V2.97 Quick Start Guide

15 Define a Fill Only event for the new RADD 6000 (component
terminals) and verify that it is Active.
This event can take several hours to complete; however, it does not
need to be completed to continue on with this procedure. The
approximate load rate is 80,000 terminals per hour without billing
traffic and 40,000 terminals per hour with billing traffic.

Complete the Configuration Setup

To complete the configuration set-up:
1 Configure any RPD 1000/2000s that have not been switched to point
to the new RADD 6000.
2 Define a Flush & Fill Only event for the new RADD 6000
(component device) and verify the event successfully completes.
3 Define a Flush & Fill Only event for the new RADD 6000
(component streams) and verify the event successfully completes.
4 Define a Flush & Fill Only event for the new RADD 6000
(component terminal configuration) and verify the event successfully
completes.
5 Define a Flush & Fill Only event for the new RADD 6000
(component periodics) and verify the event successfully completes.
6 Define a Flush & Fill Only event for the new RADD 6000
(component channel maps) and verify the event successfully
completes.
7 Define a Flush & Fill Only event for the new RADD 6000
(component terminal terminal) and verify the event successfully
completes
8 Re-activate BSI and start normal operations.
9 After all Flush & Fill or Fill Only activities are complete, create a
Fill Only event (component EMM) for the new RADD 6000.

16-7
 Section 17
RADD 6000 Failover

A RADD 6000 failover requires unit replacement as described in this

section.

RADD 6000 Replacement Procedure

Prerequisites to replacing a RADD 6000 are as follows:
The replacement RADD 6000 is configured and loaded with the
RADD 6000 software that is compatible with that DAC 6000
software release.
The replacement RADD 6000 is rack mounted and defined in the
DAC 6000.
The replacement RADD 6000 has the same IP address as the target
unit being replaced.

RADD 6000s must be associated with the Downstream Plant

through the RADD2OM device_port linkage.

Replacement Procedure
To replace a targeted RADD 6000:
1 Disconnect the Ethernet cable from the target RADD 6000 and
reconnect it to the replacement RADD 6000.
2 Power up the replacement RADD 6000 and wait five minutes for all
task execution to complete.
3 Ensure that the DAC 6000 is communicating with the replacement
RADD 6000 from the Display RADD Device Status window as
follows:
From the Main Menu, click Manage Devices, and then click
Define RADD.
On the Define RADD window, click Select, which highlights
Name, and then click Name.
From the Device Names list, select the <appropriate
RADD 6000> and then click Accept.
On the Define RADD window, click Accept.

17-1
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

On the Define RADD window, ensure the Communication

Established with RADD and Online buttons are on (filled).

Defining and Verifying Each Separate RADD 6000 Operation

Define separate flush and/or fill operations for each RADD 6000 object
attribute. Create a separate flush and/or fill operation type for each
attribute or set of attributes listed in the Flush and Fill Operations for
Replacement RADD 6000 table.
Creation of operations must be ordered exactly as listed in the table.
The End Time on the Define Operations window must be increased
by the End Time Increment listed for each Attribute/Attribute Set in
the table.
Follow all special instructions provided in the table.

17-2
RADD 6000 Replacement Procedure DAC 6000 Release V2.97 Quick Start Guide

Flush and Fill Operations for Replacement RADD 6000

Item Operation Attribute(s) End Time Special Instructions
Type Increment
1 Flush and Devices and 5 minutes
Fill streams
2 Flush and Terminal 5 minutes
Fill configuration
3 Flush and Channel 5 minutes
Fill maps
4 Flush and Terminals 5 minutes EMMs are flushed as part of the Flush and Fill
Fill per terminals operation; therefore, only a Fill
1000 operation is required for EMMs on the
terminals RADD 6000 as listed in item 8.
5 Flush and Periodics 5 minutes Any Cancelled operations for this RADD 6000
Fill may restart as a result of this operation;
however, Paused or Deleted operations will not
restart.
6 Flush and Configuration 5 minutes
Fill requests
7 Flush and Poll requests 5 minutes
Fill
8 Fill EMMs 10 minutes On systems running the persistent init feature,
per when the operation is complete, from a System
1000 window on the DAC 6000, run the script:
terminals $HOME/scripts/reset_emm_config<radd_name>
9 Flush and Download 120 After the Flush and Fill is complete, any code
Fill objects minutes download that was active before the RADD 6000
per was replaced must be restarted from the Control
download Operations window (Main Menu > Manage
object Operations > Control Operations).
previously
defined on In some cases, the delete and redefinition
the of a code object (or objects) takes precedence
RADD 6000 over defining a Flush and Fill operation. See the
note that follows this table.

17-3
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Imp leme nting Ea ch Tabl e I tem

Access the Define Operations window by clicking Manage Operations
from the Main Menu, and then clicking Define Operations.

Repeat steps 1 through 7 for each item in the Flush and Fill
Operations for Replacement RADD 6000 table.
1 On the Define Operations window, click Operation Type
Select Flush and Fill or Fill Only, as applicable, from the
Zoom: Operation Type window that appears.
Click Accept.
Click Add on the Define Operations window.
2 On the Edit Flush and Fill Operation window, in the Operation
Name field, type a descriptive operation name, for example, “Flush
and Fill Devices and Streams.
3 On the Edit Flush and Fill Operation window, in the End Time field,
update the End Time by the given increment for the table entry you
are processing.
4 On the Edit Flush and Fill Operation window, click Device Name
On the Zoom: Device Name window that appears, select the
<name of the RADD 6000 device that you are replacing>
(the operation is performed only on the RADD 6000 that is
selected).
Click Accept.
5 On the Edit Flush and Fill Operation window, in the Operation
Attributes panel, click on (filled) the radio buttons applicable to the
attributes of the item you are processing from the Flush and Fill
Operations for Replacement RADD 6000 table.
Click Accept to schedule the operation.
Click Exit to return to the Manage Operations menu.
6 From the Manage Operations menu, click Control Operations.

17-4
RADD 6000 Replacement Procedure DAC 6000 Release V2.97 Quick Start Guide

7 On the Control Operations window, in the Type Filter panel, select

the Flush & Fill filter (filled).
Click Accept.
In the Operations panel, reference the Status field and ensure
the operation just scheduled has a Completed status before
scheduling the next item from the Flush and Fill Operations for
Replacement RADD 6000 table.

17-5
 Section 18
Tr oubleshooting

This section provides basic troubleshooting procedures to help isolate

problems that manifest themselves as RADD 6000 related failures, such
as:
DAC 6000 is not communicating with the RADD 6000
Digital set-tops are not responding
Digital set-tops are dropping messages
Cannot communicate with one-way digital set-tops
Digital set-top virtual channel map (VCM) problems
Digital set-tops are not receiving code objects

DAC 6000-to-RADD 6000 Communication

If the DAC 6000 is not communicating with the RADD 6000, ensure the
unit is functioning online as follows:
Invoke the Define RADD window and check the Online and
Communication Established with RADD indicators to ensure the
RADD 6000 is online and that communication is established with it.
Ping the RADD 6000 from the DAC 6000:
− If the ping fails, ensure the RADD 6000 power indicator
is illuminated.
− If the power indicator is illuminated, the unit may be at the “ok”
prompt; reboot the RADD 6000.
− If the RADD 6000 is at the UNIX prompt, verify the RADD 6000
IP address. If different, it may indicate a DHCP server is on
the network.
Disable the DHCP server and reconfigure the RADD 6000 using
the HCT 1000.
Disable the DHCP services on the RADD 6000 and reconfigure
the RADD 6000 manually using radd_rename.
− If the power indicator is not illuminated, the unit is unplugged or
there is a power supply failure.
If the ping works from the Define RADD window, switch the
RADD 6000 offline and back online. This will cause a new ‘connect
request’ from the DAC 6000 to the RADD 6000.

18-1
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Digital Set-tops Not Responding

If the digital set-top terminals are not responding, perform the following
checks:

If any changes are required, it is necessary to fill streams.

Ensure the OM 1000 port number is changed to 6157.
Ensure the RPD 1000/2000 port number is changed to 5861 and the
destination address is changed to the RADD 6000 IP address.
Verify that the RADD 6000 broadcast address is set up in the
DAC 6000 /etc/hosts file (IP Address <name>BA).
Verify that the RADD 6000 broadcast address is correct based on the
network class (A, B, or C).
If all RADD 6000s are not communicating with their respective
OM 1000s, logon to a RADD 6000 and ping its broadcast address as
defined in the DAC 6000 /etc/hosts file (IP Address <name>BA).
Examine the return addresses for OM 1000s that should not be
receiving data from this RADD 6000.
Access the Java-enabled console screens of each RADD 6000 to
determine the status of streams and bandwidth utilization.

Digital Set-tops Dropping Messages

If the digital set-top terminals are dropping messages, perform the
following checks:
Ensure two RADD 6000s are not communicating with the same
OM 1000 by logging-on to a RADD 6000 and pinging its broadcast
address as defined in the DAC 6000 /etc/hosts file. Examine the
return addresses for OM 1000s that should not be receiving data
from this RADD 6000.
Access the Java-enabled console screens of the RADD 6000 to
determine the status of streams and bandwidth utilization.
Check the Control Operation window for any failed events. If any
events are in the Failed Operation state or Insert Failed
Operation state, select Retry Operation. If Retry Operation does
not rectify the problem, fill streams.

18-2
Cannot Communicate with One-way Digital Set-tops DAC 6000 Release V2.97 Quick Start Guide

Check the Control Operation window for any failed events. If any
events are in the Build Failed Operation state, do the following:
− VCM or PCM – fill channel maps.
− Multiplex – fill streams.
− Macrovision – fill terminal configuration.
− Analog Clear Service – next event will begin in approximately 15
minutes; verify that the error goes away.
− Global Authorization – wait for active event to finish then
examine operation statistics to determine the number of
terminals that failed. If the percentage is small (less than 10%),
wait for a convenient time when the access controller is not
loaded and fill EMMs (the fill rate is approximately 4-to-6 per
second). If the percentage is large, schedule a more immediate
time to reload EMMs.
− Code Download – if the tune/enable events are in a Build Failed
Operation state, reload assignment. If the code object event is in
a Build Failed Operation state, reload code object, then reload
the assignment. If the problem persists, ensure that the object
attributes are correct.

Cannot Communicate with One-way Digital Set-tops

For communication failures with one-way digital set-tops, perform
checks at the DAC 6000 and RADD 6000.
Determine the RADD 6000 and OM 1000 of the terminal.
From the DAC 6000, perform the following checks:
− Check the operational and development log files.
− Verify the DAC 6000-to-RADD 6000 connection status.
− Check the DAC 6000/RADD 6000 database counts and fill where
necessary.
− Check the status of the multiplex insertion.
− Verify that the OM 1000 is listed in the DAC 6000 /etc/hosts
file. If not, add it, then fill streams.
− Ensure the RADD 6000 broadcast address is listed in the
/etc/hosts file.
From the RADD 6000, perform the following checks:
− At the Java console, check the multiplex insertion, terminal
definition, and device and stream definition.
− Examine the development logs using Telnet.

18-3
DAC 6000 Release V2.97 Quick Start Guide Addressable Controller System Documentation

Digital Set-top Virtual Channel Map Problems

VCM problems can occur if the VCM is not built or the physical channel
map is not built.
Verify that the VCM is built:
− Examine the channel map status.
− Examine the operation manager event status.
− Check RADD 6000 status and fill where necessary.
If the virtual channels tune, but are lost when the subscriber
releases the channel button, verify that the physical channel map is
built:
− Examine the operation manager event status.
− Check RADD 6000 status and fill where necessary.

Code Download
Set-top terminals not loading requested code.
Using the screen sets provided under Manage Operations, ensure the
insertion event and its sub-events are active.
Verify that the out-of-band (OOB) multiplexer associated with the
OM 1000 is active. Ensure the Program Association Table (PAT) and
Program Map Table (PMT) messages are active and that the PMT
associated with the downloaded service is also active.
Verify that the download service is on the channel map assigned to
the digital set-top.

If the tuning message does not appear on the Code Object

window, then the decoder conditional may be incorrect, contact the
Motorola BCS Technical Response Center (TRC) at
1-888-944-HELP (1-888-944-4357).

18-4
Abbreviations and Acronyms

ACP Access Control Processor

ASCII American Standard Code for Information Interchange
BSI business system interface
C6U Commander 6 Upconverter
C8U Commander 8 Upconverter
DAC 6000 Digital Addressable Controller 6000
DCT Digital Consumer Terminal
DEKM Dynamic Encryption Key Management
DST Daylight Savings Time
DVi Digital Versatile Interactive (terminal)
EAS Emergency Alert System
ECC Encryption Control Center
EMM Entitlement Management Message
GCR Group Configuration Request
GRK Group Rekey
GUI graphical user interface
HCT 1000 Headend Configuration Tool 1000
ID identifier, identification code
IRT1000/2000 Integrated Receiver Transcoder 1000 or 2000
ISQL Interactive Structure Query Language
KLS 1000 Key List Server 1000
MAM Multiple Application Manager
MPS Modular Processing System
NIC Network Interface Card
NTP Network Time Protocol
NVRAM non-volatile random-access memory
OM 1000 Out-of-band Modulator 1000
OOB out-of-band
PAT Program Association Table
PCM Physical Channel Map
PMT Program Map Table
PPV Pay-Per-View

Abbreviations and Acronyms-1

DAC 6000 Release V2.97 Quick Start Guide „ Addressable Controller System Documentation

RADD Remote Addressable DANIS/DLS

RAID redundant array of independent disks
RF radio frequency
SQL structured query language
TRC Technical Response Center
TZ time zone
UKL Unit Key List
VCM virtual channel map

Abbreviations and Acronyms-2

487127-001
5/04 MGBI