IVSP (Client Proxy) Integration Guide

Transcription

1 [ IVSP (Client Proxy) Integration Guide Overview Introduction This client proxy document contains the information required to integrate the IVSP (client proxy). Important: Browser configurations shown in this document cannot be edited. You must repeat the entire installation if changes are required in the saved configuration. Purpose You can do the following using this document: xref Audience This document was written for headend technicians. Field service engineers and Cisco Services engineers may also find the information in this document helpful. Document Version This is the first formal release of this document.

2 Post-Installation Checks Post-Installation Checks RFGW 1 Log into the RFGW using Firefox with the following URL: IP Address] 2 Click Systems > Release Management. 3 Verify the release information. 4 Click Systems > License Management. 5 Verify the license information. VSRM 1 Log into the VSRM using Firefox with the following URL: Admin IP Address] 2 Make sure that the correct VSRM RPM is installed. 3 Make sure that the USRM (VSRM1) process is running. 2 OL

3 4 Go to the VSRM1 Web UI using Firefox with the following URL: IP Address] Post-Installation Checks CDSM CDSM should list all the Servers (Vault and 2 Streamers), assuming that cdsconfig and cdsinstallation have completed in all the devices (CDSM, Vault, and 2 Streamers). 1 Log into CDSM and click Monitor > System Level. 2 Confirm the status of avsdb and network connections. Note: See CDS Servers (on page 5) for more information. OL

4 Post-Installation Checks Vault 1 Log into Vault and switch to the isa user. 2 Make sure that the status of arroyo is running. 3 Check the status of avsdb, statsd, and network connections. Note: See CDS Servers (on page 5) for more information. Streamer1 1 Log into Streamer1 and switch to the isa user. 2 Make sure that the status of arroyo is running. 3 Check the status of avsdb, statsd, and network connections. Note: See CDS Servers (on page 5) for more information. 4 OL

5 Post-Installation Checks Streamer2 1 Log into Streamer2 and switch to the isa user. 2 Make sure that the status of arroyo is running. 3 Check the status of avsdb, statsd, and network connections. Note: See CDS Servers (on page 5) for more information. CDS Servers Device IP CDSM Vault Streamer Streamer RTSP/Streamers Virtual IP VBO Make sure that the correct VBO versions are installed. OL

6 Post-Installation Checks VMs Important: Do not power on the VMs after installation. 1 Log into the vsphere client. 2 Make sure that all 6 nodes are deployed in VBO. Note: The CMS node can be deployed at a later time. 6 OL

7 Post-Installation Checks Client Proxy 1 Log into the vsphere client. 2 Make sure that all 4 nodes are deployed in the Client Proxy. OL

8 10G Switch Sample Configuration 10G Switch Sample Configuration Notes: Use copper SFP modules for VSRM and RFGW. User optical SFP for Vault, Streamer1, and Streamer2. Switch#sh run Building configuration... Current configuration : 2033 bytes Last configuration change at 04:18:39 UTC Mon Mar version 15.1 no service pad service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption service compress-config hostname Switch boot-start-marker boot system flash bootflash:cat4500euniversal.spa sg sg2.bin boot-end-marker vrf definition mgmtvrf address-family ipv4 exit-address-family address-family ipv6 exit-address-family 8 OL

9 10G Switch Sample Configuration no aaa new-model ip vrf Liin-vrf ip multicast-routing vtp mode transparent power redundancy-mode redundant spanning-tree mode pvst spanning-tree extend system-id no spanning-tree vlan 40 vlan internal allocation policy ascending vlan 40 name CDS GIGE interface FastEthernet1 vrf forwarding mgmtvrf no ip address speed auto OL

10 10G Switch Sample Configuration duplex auto interface TenGigabitEthernet1/1 description CDS GIGE switchport access vlan 40 interface TenGigabitEthernet1/2 description CDS GIGE switchport access vlan 40 interface TenGigabitEthernet1/3 description CDS GIGE switchport access vlan 40 interface TenGigabitEthernet1/4 description CDS GIGE switchport access vlan 40 interface TenGigabitEthernet1/5 description CDS GIGE switchport access vlan 40 interface TenGigabitEthernet1/6 description CDS GIGE switchport access vlan 40 interface TenGigabitEthernet1/7 description CDS GIGE switchport access vlan 40 interface TenGigabitEthernet1/8 interface TenGigabitEthernet1/9 10 OL

11 10G Switch Sample Configuration interface TenGigabitEthernet1/10 interface TenGigabitEthernet1/11 interface TenGigabitEthernet1/12 interface TenGigabitEthernet1/13 interface TenGigabitEthernet1/14 interface TenGigabitEthernet1/15 interface TenGigabitEthernet1/16 interface Vlan1 no ip address interface Vlan40 description CDS GIGE ip address ip pim sparse-mode ip igmp version 3 no ip http server ip pim rp-address ip pim ssm default line con 0 stopbits 1 OL

12 10G Switch Sample Configuration line vty 0 4 login end 12 OL

13 Workflow Configuration Important: Browser configurations shown in this document cannot be edited. You must repeat the entire installation if changes are required in the saved configuration. CDS Servers Comparing and Confirming the Installed Software 1 Log into the CDSM web UI. Note: See CDS Servers (on page 5) for a list of the CDS servers and their IP addresses. 2 Click Maintain > Software > Software Version. 3 Select the Vault IP address to check the software version. 4 Click Maintain > Software > Software Version. 5 Select the Streamer1 IP address to check the software version. OL

14 6 Click Maintain > Software > Software Version. 7 Select the Streamer2 IP address to check the software version. 14 OL

15 Comparing and Confirming the Configuration CDSM Setup 1 Click Maintain > Software > CDSM Setup. 2 Check and compare the configuration. OL

16 16 OL

17 OL

18 System Configs 1 Click Maintain > Software > System Configs. 2 Check and compare the configuration. 18 OL

19 Ingest Tuning 1 Click Configure > System Level > Ingest Tuning. 2 Compare the configuration. OL

20 MPEG Tuning 1 Click Configure > System Level > MPEG Tuning. 2 Compare the configuration. Source Output Port 1 Click Configure > System Level > Source Output Port. 2 Compare the configuration. 20 OL

21 Stream Groups Setup 1 Click Configure > Array Level > Stream Groups Setup. 2 Compare the configuration. Control/Setup IP 1 Click Configure > Array Level > Control/Setup IP. 2 Compare the configuration. OL

22 Interface Setup 1 Click Configure > Server Level > Interface Setup. 2 Select the Vault IP address. 3 Compare the configuration. 4 Click Configure > Server Level > Interface Setup. 5 Select the Streamer1 IP address. 6 Compare the configuration. 22 OL

23 7 Click Configure > Server Level > Interface Setup. 8 Select the Streamer 2 IP address. 9 Compare the configuration. OL

24 Server Setup 1 Click Configure > Server Level > Server Setup. 2 Select the Vault IP address. 3 Compare the configuration. 24 OL

25 4 Click Configure > Server Level > Server Setup. 5 Select the Streamer1 IP address. 6 Compare the configuration. OL

26 7 Click Configure > Server Level > Server Setup. 8 Select the Streamer2 IP address. 9 Compare the configuration. 26 OL

27 OL

28 Route Tables 1 Click Configure > Server Level > Route Tables. 2 Select the Vault IP address and click Display. 3 Compare the configuration. 4 Click Configure > Server Level > Route Tables. 5 Select the Streamer1 IP address and click Display. 6 Compare the configuration. 7 Click Configure > Server Level > Route Tables. 8 Select the Streamer2 IP address and click Display. 28 OL

29 9 Compare the configuration. RTSP Setup 1 Click Configure > Server Level > RTSP Setup. 2 Select the Streamer1 IP address. 3 Compare the configuration. OL

30 4 Click Configure > Server Level > RTSP Setup. 5 Select the Streamer2 IP address. 6 Compare the configuration. 30 OL

31 FSI Setup 1 Click Configure > Server Level > FSI Setup. 2 Select the Vault IP address. OL

32 3 Compare the configuration. 32 OL

33 RFGW From the dedicated RFGW, compare and confirm the RFGW settings with the illustrations in the following topics. System Configuration OL

34 IP Network Configuration Note: The SRM IP address is the VSRM server IP address. 34 OL

35 QAM Configuration Example Notes: The GbE input ports are used for 10G content distribution. The regular 1G copper SFP works for this on the RFGW side. Be sure to save the configuration by clicking Save on the main menu. This configuration is reflected in the VSRM automatically. OL

36 VSRM Make sure that you finish the RFGW configuration before working on the VSRM workflow. 1 Log into the VSRM using the Firefox browser. 2 Check for Protocol Adapters (ProtocolAdaptor ErmWebService & ProtocolAdaptor OcaiRpc). 3 Proceed only if you find the adapters as shown in the following illustration. 4 Click EDM/SdvSm > Platform > Resource Create. 5 Add an entry for the RFGW1 by entering a name (CreateName). 6 Click the commit changes tab to get the entry. 36 OL

37 Logging Out from the VSRM and Logging In Again 1 Locate the additional QAM entry under ERM/SdvSm > Resource Manager. 2 Expand the QAMs tree. You should see the new RFGW here. 3 Expand the new RFGW and highlight Chassis. 4 In the CtrlIpAddress field, enter the IP address of the RFGW. 5 Click Commit Changes and wait until the data is populated on the screen. Adding a Service Group Entry 1 Click Erm/SdvSm > Resource Manager > QAMs > [select QAM] > Output Ports. 2 Enter the Service Group ID (ServiceGroupId) in the RFGW ports. 3 Click Commit Changes. OL

38 Disabling the Unused GbE Ports 1 Click Erm/SdvSm > Resource Manager > QAMs > [select QAM] > Gbe Ports. 2 Disable the unused ports by selecting NotConnected for the InterfaceState as shown in the following illustration. VSRM Couchbase Configuration Creating a VM You can create a VM in any UCS machine. Use the VM settings in the following illustration to create the Couchbase VM. 1 Power on the VM and install the RHEL OS. Note: Follow the regular installation procedure. This takes approximately 30 minutes to complete. 38 OL

39 2 Using the following illustration as a guide, install the couchbase RPM after the RHEL OS installs. Configuring the Couchbase Web Browser 1 Using the Firefox browser, open Couchbase. 2 Click Setup. 3 Leave the default values and click Next. OL

40 4 Click Next. 5 Create a default bucket as shown in the following illustration. 6 Click Next. 40 OL

41 7 Agree to the terms and conditions and click Next. 8 Enter an Administrator Password and verify the Password. This is the web browser login password. 9 Click Next. 10 Log into Couchbase. Make sure that the Cluster Overview screen opens. OL

42 Creating Couchbase Buckets 1 Click the Data Buckets tab. 2 Click Create New Data Bucket. 3 Fill in the information as shown in the following illustration. 4 Click Create. The srmobjects bucket appears if the creation was successful. 42 OL

43 Integrating Couchbase and VSRM 1 Log into VSRM as an Administrator using Firefox. 2 Go to ERM/SdvSm > Platform > Platform Adaptors > DbAdaptor Couchbase > Object Database Settings. 3 Enter information only in the Couchbase Node IP Address in the ObjectDatabaseWebIP field. Leave all other parameters at their default values. 4 Click Commit Changes. OL

44 VBO 1 Log into the vsphere client. 2 Confirm that all the VMs display. 44 OL

45 Configuring the Management Node for CUSTKIT Installation 1 Do not power up any VMs after you install the OVF files. 2 Power on the Management Node using the vsphere client. 3 Log in as an Administrator. 4 Change the user name and password using your site's procedures. 5 Configure the IP Address as shown in the following illustration. Workflow Configuration 6 Select Network Configuration. 7 Enter a unique host name for the node. 8 Set the DNS server to All other nodes should use the Core Services IP address as the DNS server. 9 If the IP addresses are not obtained using DHCP, unselect that option and enter the Default Gateway. Select the eth0 interface. 10 Go to Configure Device and press Enter to continue. 11 Enable the eth0 interface. Note: If you are configuring for static addressing, unselect the DHCP option and specify the IP address and subnet mask. 12 Click Save. A restart prompt appears. Click to restart the client. 13 Log in using putty from the desktop on that IP. 14 Transfer the GET-kists tarto/home/bninet/bni/custkit directory in the Management Node. 15 Change the file permissions to chmod 777 GET-kits tar. OL

46 Configuring the Database Node 1 Power up the DB Node [PERFORM-DB] in the VBO. 2 Login using the default Administrator user name and password. 3 Select Network Configuration. 4 Select a unique host name for the node. 5 Set the DNS server to All other nodes should use the Core Services IP address as the DNS server. 6 If the IP addresses are not obtained using DHCP, unselect that option and enter the Default Gateway. Select the Eth0 interface and press Enter. 7 Go to Configure Device and press Enter to continue. 8 Enable the eth0 interface. Note: If you are configuring for static addressing, unselect the DHCP option and specify the IP address and subnet mask. 9 Click Save. A restart prompt appears. Click to restart the client. 10 After the restart, check that the provided IP is pinging from the desktop. 11 Log into the following IP address using the Firefox browser as an Administrator: [DBNodeIPAddress]: Configure the NTP server with the IP address. 46 OL

47 13 Click Save. 14 Unselect the Deploy Management Service option. 15 Change the Mgmt Service Address to [MgmtNodeIPAddress]. 16 Set the Data Center name to DC1. 17 Click Configure. Configuring the Management Node 1 Open the following IP address in the Firefox browser: [MgmtNodeIPaddress]: Login as the Administrator. 3 Configure the NTP server with the IP address. 4 Click Save. OL

48 5 Unselect the Deploy Database in the UI option. 6 Leave the Management Service address field blank. 7 Change the DataCenter field to DC1. 8 Click Configure. 9 Provide the Peer DB IP or a remote database address as <DBNodeIPAddress>[IP of DB Node]. Configuring the UI Node 1 Power on the UI node. 2 Log in as an Administrator. 3 Change the password to the standard password. The following screen opens. 4 Select a unique host name for the node. 5 Unselect the DNS Server option. 6 Leave the DNS servers and search domain fields blank or at their defaults. Note: If you are not using DHCP to obtain IP addresses, unselect the DHCP option, enter the Default Gateway, and select the eth0 interface. 7 Go to Configure Device and press Enter to continue. 8 Enter the values for IP Address and Subnet Mask. 9 Click Save. A restart prompt appears. 48 OL

49 10 Click to restart the client. 11 After the restart, open the following IP address with the Firefox browser: [UINodeIP]: Login as an Administrator. The NODE IP displays as default. 13 Enter the Management Services Node IP per your configuration. 14 Change the Data Center field to DC1. 15 Click Configure. 16 Open the [UINodeIP]::8080/bnimgmt and log in as an Administrator. 17 Verify that a screen similar to the following displays: OL

50 Configuring the SM Node 1 Repeat the steps given in Configuring the UI Node (on page 48) for booting up the server and assigning the passwords and IP addresses for the SM node. 2 Open the following URL in the Firefox browser: [SMNodeIP]: Log in as the Administrator. 4 Select the following options: Install Session Manager Install Edge Resource Manager Install OnDemand Resource Manager 5 Enter the following information: Management Service Node IP: [MGMTNodeIP] Data Center Name: DC1 50 OL

51 Esx Host Name: esx1 Configuring the DataGrid Node 1 Repeat the steps given in Configuring the UI Node (on page 48) for booting up the server and assigning the passwords and IP addresses for the DataGrid node. 2 Open the following URL in the Firefox browser: [DataGridNodeIP]: Log in as the Administrator. 4 Select the Install DataGrid option. 5 Enter the following information: Management Service Node IP: [MGMTNodeIP] Data Center Name: DC1 OL

52 Esx Host Name: esx1 Configuring the PC Node 1 Repeat the steps given in Configuring the UI Node (on page 48) for booting up the server and assigning the passwords and IP addresses for the SM node. 2 Open the following URL in the Firefox browser: [PCNodeIP]: Log in as the Administrator. 52 OL

53 4 Enter the following information: Management Service Node IP: [MGMTNodeIP] Data Center Name: DC1 5 Select the Delay Streamin Server PC option. Service Verification 1 Log into the UI node ([UINodeIP]:8080/) as Administrator. 2 Click Navigation > Administration > Solution Management. 3 Select Core and verify the Service Status. The Operational State should be UP. 4 Select CATV_SM and verify the Service Status. The Operational State should be UP. OL

54 Setting Up VBO to Support Cisco One-Way VOD 1 Log into the UI node in VBO using the CLI credentials. 2 Go to the following directory: /home/bninet/jbossesb/server/default/conf/bni/metadata/cust omer-view-conf/data-conf 3 Edit the menu.cust.xml file as follows: Note: Change the bolded entry from "isavailable=false" to "isavailable=true". <entity-constraint type="customerview" entityref="topologyedgeinputgroups" isavailable="true" /> 4 Log into the UI node in VBO using the CLI credentials. 5 Go to the following directory: /home/bninet/jbossesb/server/default/conf/bni/metadata/cach e/ 6 Delete all the files present in page-conf and data-conf. 7 Reboot the UI node through the vsphere console. 8 After a few moments, open the Topology in the UI node and make sure that the controller is available. 54 OL

55 Configuring the CMS Node 1 Power on the CMS node. 2 Log in as an Administrator. 3 Change the password to the standard password. 4 Select a unique host name for the node. 5 Unselect the DNS Server option. 6 Leave the DNS servers and search domain fields blank or at their defaults. Note: If you are not using DHCP to obtain IP addresses, unselect the DHCP option, enter the Default Gateway, and select the eth0 interface. 7 Go to Configure Device and press Enter to continue. 8 Enter the values for IP Address and Subnet Mask. 9 Click Save. 10 A restart prompt appears. Click to restart the client. 11 After the restart, open the following IP address with the Firefox browser: [UINodeIP]: Login as an Administrator. The NODE IP displays as default. 13 Enter the Management Services Node IP per your configuration. 14 Change the Data Center field to DC1. 15 Click Configure. 16 Click Configure. 17 Log into the UI node in VBO using the CLI credentials. 18 Go to the following directory: /home/bninet/jbossesb/server/default/conf/bni/metadata/cach e/ 19 Delete all the files present in page-conf and data-conf. 20 Reboot the UI node through the vsphere console. OL

56 21 After a few moments, open the Topology in the UI node and make sure that the CMS is available. Service Verification 1 Log into the UI node ([UINodeIP]:8080/) as Administrator. 2 Click Navigation > Administration > Solution Management. 3 Select CMS and verify the Service Status. The Operational State should be UP. 56 OL

57 Topology 1 Log into the UI node ([UINodeIP:8080/). 2 Log in as Administrator. 3 Go to Topology > 3rd Party Services. 4 Click the + to create a VSRM. OL

58 Creating a Controller 1 Go to Topology > Controllers. 2 Click the + to create a controller. Creating a Headend 1 Go to Topology > Places > Headends. 2 Click the + to create a headend. 58 OL

59 Creating a Streaming Server 1 Go to Topology > Streaming Server. 2 Click the + to create a streaming server. 3 You must obtain the IP (virtual IP) from the CDSM: a Log into the CDSM as Administrator. b Go to Configure > ServerLevel > RTSP Setup. OL

60 c Highlight the IP address and click Display. You will see the Master streaming IP. Creating a SOP Group 1 Go to Topology > SOP Groups. 2 Click the + to create an SOP group. 60 OL

61 Configuring the Streaming Server Ports 1 Open the streaming server. 2 Click Ports on the right side of the screen. 3 Enter the port-related information by comparing the CDSM SOP page: Workflow Configuration OL

62 Assigning SOPs to the SOP 1 Click the green link (.-.). 2 Associate the port to the SOP. Creating the Streaming Zone 1 Go to Topology > Streaming Zones. 2 Click the + to create a the streaming zone. 62 OL

63 Creating the Edge Device 1 Go to Topology > Edge Devices. 2 Click the + to create an edge device (RFGW). OL

64 Creating the Edge Input Group 1 Go to Topology > Edge Input Groups. 2 Click the + to create an edge input group. 3 Open the Edge Input Group. 4 Open the Options section on the right side of the screen. 5 Link the Edge Input Group with the RFGW. 6 Link the SOP group with the Edge Input Group. 64 OL

65 Example of a fully configured page: OL

66 Content Ingestion Content Ingestion 1 Log into the CMS node. You can see the watchfolder in the home directory of the CMS (/home/bninet/) if you created it as explained earlier. 2 Create a folder in /home/bninet/watchfolder. 3 Copy the video file (for example, NachBaliye.ts) and its related ADI.XML file to this folder. Example: If the folder name is dabang, then move the video and ADI.XML file to /home/bninet/watchfolder/dabang/. Note: The ingest begins automatically once the files are transferred to the new folder 4 Verify the status of the ingestion by going to Content Manager > Propagation. 66 OL

67 Verifying Content Ingestion in the CDSM Server 1 Log into the CDSM server. 2 Go to Monitor > System Level > Completed Ingest, where you can see successful ingests. Content Ingestion Example ADI.XML File OL

68 Content Ingestion 68 OL

69 Content Ingestion OL

70 Restclient Testing Restclient Testing You can test the restclient using Firefox with the plugin installed. The SM Node IP address is 'Body' covers the following details: ClientId is the set-top MAC address. Streaming zone is the information given during the Topology configuration. ContentId covers Provider ID (apalya.com) and Asset ID (Apalya_127). Service Group as configured in the VSRM. Sessions are built in the VSRM if the response to RESTCLIENT is OL

71 Restclient Testing The Response Body (preview) appears as follows: OL

72 For Information If You Have Questions If you have technical questions, contact Cisco Services for assistance. Follow the menu options to speak with a service engineer. Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA Tel: Fax: Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1009R) Product and service availability are subject to change without notice Cisco and/or its affiliates. All rights reserved. April 2014 Part Number OL