Cisco SDV Collector Installation Guide

Cisco SDV Collector Installation Guide Overview Introduction This document provides installation procedures for Cisco Switched Digital Video (SDV) Collector software Release 4.0.x. Purpose The information in this document will enable qualified service personnel to install the operating system needed for SDV Collector 4.0.x and to install, configure, and verify the setup of SDV Collector. Audience This document is intended for authorized service personnel who have experience working with DNCS, EC, or USRM, and related equipment in the headend network. The service personnel should have appropriate background and knowledge to complete the procedures described in this document. Document Version This is the first formal release of this document. In This Document Install the Operating System... 2 Install SDV Collector... 4 Configure Log 1.0 / Log 2.0... 8 Verify SDV Collector Setup... 13 Configure Non-Cisco DNCS Systems for SDV Tools... 17

Install the Operating System Install the Operating System This section describes the steps for installing RedHat 5.7 on the designated server and adding Informix aliases, if not yet present in the DNCS. Install RedHat 5.7 1 Turn on power to the designated server. 2 While the server boots up, insert the RedHat 5.7 installation disk into the CD drive of the server. 3 When the server reaches the boot prompt, press Enter. 4 The Network Configuration screen appears and prompts you to configure eth0 and eth1. 5 Select Manually and enter collector as the server name. 6 Enter the default gateway IP address, and then click Next to continue. 7 In the Time Zone screen, choose the time zone in which the machine is located, and then click Next. The Package Installation screen appears, and the installation proceeds unattended. When the installation finishes, the server will reboot. 8 Manually eject the installation CD. 9 At the login prompt, log in as root and enter the password generic. 10 When prompted to change the password, enter 1234test or the alternate password specified by the customer. Edit the /etc/hosts file to add IP address and hostnames for Marketing, DNCS, and USRM, and then save the file. 11 At the command prompt, enter the following command to confirm 8 GB of swap space: grep SwapTotal /proc/meminfo The response should be: 2 OL-31606-02

Install the Operating System 12 Create the file route-eth0 in /etc/sysconfig/network-scripts to add routes to eth0. 13 At the command prompt, enter service network restart to restart network services. 14 Ping the USRM and DNCS to confirm that the routes are working. Add Informix Aliases If the Informix Aliases are not already in DNCS, add them as follows: 1 Edit the file /export/home/informix/etc/onconfig to add the Informix TCP servername (himalyatcpdbserver in SDV Lab) to the list of DBSERVERALIASES. 2 Edit the file /export/home/informix/etc/sqlhosts to add the TCP entry. 3 Type su - dncs to switch the DNCS user, and then source the environment as. /dvs/dncs/bin/dncssetup (note the space between. and /dvcs/dncs/...). 4 Type the following command to enable the new connection: onmode P start himalyatcpdbserver OL-31606-02 3

Install SDV Collector Install SDV Collector To install SDV Collector from CD or an ISO image: 1 Insert the installation disk into the server CD drive, or copy the ISO image to the server hard drive. 2 Enter the following commands at the root prompt: For installation from CD: mount /dev/cdrom /media/cdrom cd /media/cdrom./install For installation from ISO image: mount o loop sdv_collector-4.0.0rc33-1-appdisc.iso /media/cdrom cd /media/cdrom./install 3 Type :q! to exit vi. 4 Enable the vsftpd service on SDV Collector as follows: chkconfig --level 345 vsftpd on chkconfig --list grep -i vsftpd After these commands execute, the following output should appear: Note: Confirm that 3, 4, and 5 are all on as shown in this example. 5 To check the vsftpd service, type the following command: service vsftpd status Confirm that the response indicates running status. If not, start the service using the following command: service vsftpd start 6 Set the password for the sse user in the command line as follows: passwd sse 7 When prompted, type collector as the password, and then enter the password again for confirmation. 8 Add sdvmkt, sdvsao, and sdvcap in the /etc/hosts file. 9 Type cd /opt/sse/collector/bin. 10 Execute the script, type yes, and when prompted, enter the root password for the respective application servers../ssh_key_init sdvmkt root./ssh_key_init sdvcap root./ssh_key_init sdvsao root 4 OL-31606-02

Install SDV Collector 11 To verify SSH keys, try logging in from SDV Collector to all servers, as follows: Execute: ssh root@sdvmkt ssh root@sdvsao ssh root@sdvcap You should be able to log in without a password. If you are able to access the application servers (sdvmkt, sdvcap, sdvsao) via SSH successfully, the keys are set properly. 12 Type exit to return to SDV Collector, and then enter the following: cd /opt/sse/collector/bin./configsdv The Configuration Main Menu appears. 13 Select 1 to set the server type (SA or RealTime). 14 Select log1.0 or log2.0. Note: See Configure Log 1.0 / Log 2.0 (on page 8) for configuring logs in USRM. 15 Select 3 to Set Applications (sdvmkt, sdvsao, or sdvcap). 16 Select 4 to set monitors for SAO only. 17 Select 5 to Configure Apps. a Select 1 to configure App Connection Settings for each SDV application server (sdvmkt, sdvsao, and sdvcap). Enter the Marketing server IP Address, SSH User (root), SSH Pass (1234test), DB Replicate (1 for on), and DB Insert (1 for on). Similarly, set the SAO and Capacity Planner server IP addresses. b Select 2 to configure DNCS/Informix Connection. Modify fields as necessary per site. After making changes, type w to save them. Note: The credentials shown for settings 4, 5, 8, and 9 are examples only. Ensure that you use the proper login credentials for these settings. OL-31606-02 5

Install SDV Collector c Note: Perform this step only if you have billing information. Select 3 to configure Billing Imports (Customer Account and DHCT). Modify the fields, sort order, delimiter, and file name to match the billing files in /home/sse/ftp. d Select 4 to run import_migrator with option a (run everything). This takes about 4 minutes to run on a small lab system. e Select 5 to view the import log and see the results of import_migrator.sh. Note: If you skipped step 17c, you will get import billing errors which can be ignored. If you get DNCS import errors then connection and configurations to DNCS is not proper. Verify the connection and configuration settings and repeat the import. f Type q to exit from the configsdv script. Observe the "waiting for parser to fully stop" warning until it clears. (This takes approximately one minute.) 18 Reboot the server and type./chkstatus from opt/sse/collector/bin to verify the process status. Note: If only SDVMKT and SDVCAP are configured, the./chkstatus shows only three process running, as shown above. If SDVSAO is added, all processes will start running. 6 OL-31606-02

Install SDV Collector Set NTP 1 Type the following command to stop the NTP service: service ntpd stop 2 Type the following command: ntpdate dncs 3 Type the following command to open the NTP configuration file for editing: vi /etc/ntp.conf 4 Edit the NTP configuration file as follows: a Use the # character to comment out the lines for RedHat servers, such as 0.rhel.pool.ntp.org. b Add server dncs to the configuration. c Save and exit. 5 Type the following command to check the NTP configuration: chkconfig ntpd on 6 Type the following command to restart the NTP service: service ntpd start OL-31606-02 7

Configure Log 1.0 / Log 2.0 Configure Log 1.0 / Log 2.0 Log 1.0 Configuration 8 OL-31606-02

Configure Log 1.0 / Log 2.0 OL-31606-02 9

Configure Log 1.0 / Log 2.0 10 OL-31606-02

Configure Log 1.0 / Log 2.0 Log 2.0 Configuration 1 Log in to SDV Collector as a root user and run configsdv. 2 Enable Log 2.0 as follows: Note: Remain logged in to SDV Collector for additional steps to be performed later. 3 Log in to USRM and set ActivityLogFormat to TWC. 4 Navigate to the USRM Reset Software page, set ServerState to Reset, and then click Commit Changes. SDV Collector automatically connects to Tuner port 61403. The Log2 Clients page should show the SDV Collector IP address after the software Reset is issued, and should start receiving ActivityLog files in /u01/sse/common/[raw parse archive]. 5 On the Log2 Clients page, configure USRM for Log2.0 transmission of Tuner table data to SDV Collector. 6 Return to SDV Collector as a root user and verify the status of listener as not running and activitylog_listener as running, as follows: OL-31606-02 11

Configure Log 1.0 / Log 2.0 Note: For Log 2.0 (and Log 2.0 only), the event logs should not be pushed to SDV Collector. Therefore, verify that the SDV Collector IP address is not in the LogServerAddress field. If it is, remove it. 12 OL-31606-02

Verify SDV Collector Setup Verify SDV Collector Setup To verify the SDV Collector installation: 1 Log in to SDV Collector via SSH. 2 Type date in both terminals to check the time. The time should be synchronous between servers. If it is not, follow the steps in Set NTP (on page 6) to ensure that SDV Collector and other application server dates are in sync. First, synchronize the date in SDV Collector with DNCS. Then, synchronize the dates of Status and Operations, Capacity Planner, and Marketing with SDV Collector. 3 Open the browser and type the IP address of SDV Collector. 4 Log in to the SDV Collector web GUI using admin as the username and adminpass as the password. Note: See Configure Log 1.0 / Log 2.0 (on page 8) for instructions on configuring Log 1.0 or Log 2.0 in USRM. 5 To verify the logs that are coming from USRM, type tcpdump i eth0 in the command line. Note: Press Ctrl+z to stop the tcpdump. 6 Type cd /opt/sse/collector/log to open the SDV Collector log. 7 Type tail parser_stdout.log in the command line every 5 seconds to view the parser logs and verify that the logs are getting changed every 5 seconds. 8 Verify that at least some DNCS static (STB) information is getting to SDV Collector by checking the STB count. Note: Use the commands and queries shown in bold in the following example for verification. OL-31606-02 13

Verify SDV Collector Setup Verify Marketing Data in SDV Collector Enter the following command sequence to verify the existence of the viewership file, which contains Marketing data, in SDV Collector. Note: Use the commands and queries shown in bold in the following examples for verification. 1 2 3 Note: The parse folder always contains at least one file. Check the date and tail of this file and review its content. 4 5 6 14 OL-31606-02

Verify SDV Collector Setup 7 Note: Two files are available in 10 minutes. Verify SDV Collector Data in Marketing Server Use the command sequence shown below to verify the existence of SDV Collector data on the Marketing server. Note: In the following examples, the Marketing server has not yet received any files from SDV Collector. If it had, the files would be stored in the sqlldr and archive directories. Use the commands and queries shown in bold in the following examples for verification. 1 2 3 Note: SDV Collector copies the contents of the sqlldr folder to the Marketing server every hour. OL-31606-02 15

Verify SDV Collector Setup 4 16 OL-31606-02

Configure Non-Cisco DNCS Systems for SDV Tools Configure Non-Cisco DNCS Systems for SDV Tools In non-cisco DNCS systems, the DNCS servers are supplied by companies other than Cisco, so the configuration tables used by SDV Tools are empty. As part of SDV Tools configuration, these tables must be filled by feeding information into SDV Collector using text files and SQL commands. This section describes the tables imported from DNCS for each of the SDV Tools applications, and provides the procedures for filling these tables. Add USRM Details into SDV Collector The SDV_SERVER table consists of the following fields: SDV_ID SDBSERVER_OID IP_ADDR NAME SECONDARY_SDB_OID ADMIN_STAT IS_PRIMARY SOFTWARE_REVISION SSH_HOST SSH_USER SSH_PASS SNMP_HOST SNMP_COMMUNITY COLLECTOR_ID TUNER_TCP_PORT TUNER_UDP_PORT STREAM_TCP_PORT STREAM_UDP_PORT PROGRAM_TCP_PORT PROGRAM_UDP_PORT To populate these fields: 1 Make a list of USRM details in a separate text file with Insert commands, as shown in the following example. 2 Access SDV Collector via SSH and then type the following commands: SDV Collector displays a list of added USRM details, as shown in the following example. OL-31606-02 17

Configure Non-Cisco DNCS Systems for SDV Tools Configure the src_des.txt File 1 Create a file named src_des.txt in the path /opt/sse/collector/ftp. 2 In the src_des.txt file, add a record for each source in the form: SOURCE_ID, SOURCE_DESCRIPTION Use the comma (,) as shown to delimit the values in each record. 3 In the file /opt/sse/collector/etc/collector.cfg, set the mdn flag to 1. This imports the /home/sse/ftp/src_des.txt data into the IPG_SAM_CHANNEL_MAP table. Note: If this table is not filled, the UI displays the message No Channels found. Try Refreshing after a few minutes. 18 OL-31606-02

Configure Non-Cisco DNCS Systems for SDV Tools 4 The HUBS table must be populated with a fake hub_id=0 and name="fake Hub". Using mysql, insert this record into the HUBS table: Note: If this table is empty, the Marketing dashboard displays the message No Hubs found. Try refreshing after a few minutes. SDV Collector copies the contents of the sqlldr folder to the Marketing server every hour. Configure the DHCTS.txt File The DHCTS table is used in the Capacity Planner application server for populating three other tables: DHCTS_DAILY, DHCTS_WEEKLY, and DHCTS_MONTHLY. These tables are used to display the STB load by SG, STB Load by Node, or STB load by SDV Server data in the web GUI. The CAP server will not show these features if the DHCTS table is empty. The DHCTS.txt file is used to fill the DHCTS table in SDV Collector. To create this file: 1 Create a file named DHCTS.txt in the path /opt/sse/collector/ftp. 2 In the DHCTS.txt file, add a record for each DHCTS in the form: DHCT_ID HUB_ID QPSK_MOD_ID QPSK_DEMOD_ID SG_ID NODE_ID MAC_ADDR SERIAL_NUM IP_ADDR OPER_STATUS ADMIN_STATUS PRIVACY_OPT DHCT_TYPE DHCT_REV ACCT_NUM ZIP_CODE Use the pipe ( ) as shown to delimit the values in each record. Configure Billing System Related Text Files Two files, customer.txt and dhct.txt, are required to fill billing-related information tables in both Cisco DNCS and non-cisco DNCS environments. Configure the Customer.txt File The BILLING_ADDRESS table is used by the SAO application server to display the customer account number and contact details. The customer.txt file is used to fill the BILLING_ADDRESS table in SDV Collector. To create this file: 1 Create a file named customer.txt in the path /opt/sse/collector/ftp. 2 In the customer.txt file, add a record for each customer account in the form: ACCT_NUM LAST_NAME FIRST_NAME HOUSE_NUM STREET_NAME CITY STATE ZIP_CODE CUR_PAY_STATUS NODE_ID NODE_NAME NODE_NOTES OL-31606-02 19

Configure Non-Cisco DNCS Systems for SDV Tools Use the pipe ( ) as shown to delimit the values in each record. Configure the dhct.txt File The DHCT_BILLINGS table is used by the SAO application server to display the MAC address of the corresponding account number. The dhct.txt file is used to fill the DHCT_BILLINGS table in collector. To create this file: 1 Create a file named dhct.txt in the path /opt/sse/collector/ftp. 2 In the dhct.txt file, add a record for each MAC address in the form: MAC_ADDR ACCT_NUM DNCS_ADMIN_STATUS_IND DHCT_LOCATION NODE_ID NODE_NAME AMP1 AMP2 AMP3 AMP4 AMP5 PWR_SPLY1 PWR_SPLY2 PWR_SPLY3 DIVISION1 SYSTEM1 HUB_SITE HUB_SECTION Use the pipe ( ) as shown to delimit the values in each record. Note: The data is loaded automatically from text files the next day. To load the data from text files immediately, use the option 4.Run import_migrator, select option a in./configsdv, and quit properly. 20 OL-31606-02

For Information For Information If You Have Questions If you have technical questions, contact Cisco Services at the following URL: http://www.cisco.com/web/services/ OL-31606-02 21

Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-6387 Fax: 408 527-0883 Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Product and service availability are subject to change without notice. 2014 Cisco and/or its affiliates. All rights reserved. March 2014 Part Number OL-31606-02