Cisco Internet Streamer CDS 3.0–3€¦ · 7 Enabling and Verifying the Movie Streamer Engine 8...

QUICK START GUIDE

Cisco Internet Streamer CDS 3.0–3.1

1 Introduction

2 Getting Started

3 Configuring Delivery Services

4 Configuring the Service Router

5 Verifying the Web Engine

6 Verifying the Windows Media Streaming Engine

7 Enabling and Verifying the Movie Streamer Engine

8 Enabling and Verifying the Flash Media Streaming Engine

9 Related Publications

10 Obtaining Documentation and Submitting a Service Request

2

1 IntroductionThis guide helps you quickly configure the Content Delivery System (CDS) and its components, the Content Delivery Engines (CDEs). This guide assumes the following steps have already been performed:

1. All CDEs have been rack installed.

2. All cable and power connections are completed.

3. CDS software has been installed on each CDE.

For more information about installing the CDEs, see the Cisco Content Delivery Engine 205/220/250/420 Hardware Installation Guide. For more information about configuring the CDS, see the Cisco Internet Streamer CDS 3.1 Software Configuration Guide. See the “Related Publications” section on page 55 for the links to online documentation.

CDS Network TopologyThis guide uses the CDS network illustrated in Figure 1 on page 3 to describe the configuration steps. The specific topology, as well as hostnames and device IP addresses, for your network will vary. This network example consists of the following components:

• 2 CDE220s configured as Service Engines (SEs)

– NE-DEMO-SE1 — Tier 1 location

– NE-DEMO-SE2 — Tier 2 location

• 1 CDE205 configured as a Service Router (SR)

– NE-DEMO-SR — Tier 2 location

• 1 CDE205 configured as a Content Delivery System Manager (CDSM)

– NE-DEMO-CDSM

• 2 computers set up as the following:

– Origin Server: ofqdn.cds.com

With the following software installed:

• Windows Media Server

• Windows Media Encoder

• Web Server

• Darwin Streaming Server

• Darwin Encoder

– Client computer

With the following media players installed:

• Windows Media Player

• Web browser

• Apple QuickTime Player

• Adobe Flash Player browser plug-in

• The Delivery Service example used in the configuration steps has the following parameters:

– Service name: Demo VOD Delivery Service

– Origin Server: ofqdn.cds.com

– Routed Domain: rfqdn.cds.com

3

Figure 1 CDS Topology Example

2 Getting StartedThis section consists of the following procedures:

• Network Setup

• Accessing the Device Using the Command-Line Interface

• Configuring the Devices

• Activating the Devices in the Content Delivery System

• Updating a CDE Software Image

• Configuring the Domain Name System Server

Network SetupIdentify the device mode of each device (SE/SR/CDSM), assign hostnames, and network IP addresses. For the network example illustrated in Figure 1, the CDEs are set up as follows:

Device Mode Hostname Internal IP Address External IP Address

CDE-205 CDSM NE-DEMO-CDSM 10.1.4.31/24 DHCP

CDE-205 SR NE-DEMO-SR 10.1.4.13/24 DHCP

CDE-220 SE NE-DEMO-SE1 10.1.4.10/24 DHCP

CDE-220 SE NE-DEMO-SE2 10.1.4.14/24 DHCP

4

The network uses the following parameters:

• Gateway: 10.1.4.1

• Domain Name Server: 10.1.3.10

• Domain Name: spcdn.com

Accessing the Device Using the Command-Line Interface The CDE BIOS should have the following settings:

• Redirection after BIOS POST off

• Console redirection enabled for COM1

To connect to the CDE, use a terminal server connection on COM1 with the following parameters:

• 9600 baud

• 8 bits

• No parity

Configuring the DevicesUse the Setup utility to configure the device mode and network setting for each CDE.

Note The values used in the following steps are based on the example used in this Quick Start Guide.

Step 1 Enter the Setup utility and specify the following values for the NE-DEMO-CDSM:

CDE# setupWhat is the mode of the device (SE/SR/CDSM): CDSMPlease choose an interface to configure from the following list:1: GigabitEthernet 1/02: GigabitEthernet 2/0Enter choice: 1Do you want to enable DHCP on this interface (y/n) [n]: nPlease enter the IP address of this interface: 10.1.4.31Please enter the netmask of this interface: 255.255.255.0Please enter the default gateway: 10.1.4.1Please enter the domain name server ip: 171.69.2.133Please enter the domain name: spcdn.comPlease enter the hostname: NE-DEMO-CDSMDo you want to apply the configurations (y/n) [y]: yThis may take few moments. Please wait..All CLI configurations were applied successfully.Press any key to continue

NE-DEMO-CDSM# setupWhat is the mode of the device (SE/SR/CDSM) [CDSM]:Please choose an interface to configure from the following list:1: GigabitEthernet 1/02: GigabitEthernet 2/0Enter choice: 2Do you want to enable DHCP on this interface (y/n) [n]: yDo you want to apply the configurations (y/n) [y]: yThis may take few moments. Please wait..All CLI configurations were applied successfully.Press any key to continue

Step 2 Enter the Setup utility and specify the following values for the NE-DEMO-SR:

CDE# setupWhat is the mode of the device (SE/SR/CDSM): SR

5

Please choose an interface to configure from the following list:1: GigabitEthernet 1/02: GigabitEthernet 2/0Enter choice: 1Do you want to enable DHCP on this interface (y/n) [n]: nPlease enter the IP address of this interface: 10.1.4.13Please enter the netmask of this interface: 255.255.255.0Please enter the default gateway: 10.1.4.1Please enter the domain name server ip: 171.69.2.133Please enter the domain name: spcdn.comPlease enter the hostname: NE-DEMO-SRPlease enter CDSM (Content Delivery System Manager) IP or Host name: 10.1.4.31Do you want to apply the configurations (y/n) [y]: yThis may take few moments. Please wait..All CLI configurations were applied successfully.Press any key to continue..

NE-DEMO-SR# setupWhat is the mode of the device (SE/SR/CDSM) [SR]:Please choose an interface to configure from the following list:1: GigabitEthernet 1/02: GigabitEthernet 2/0Enter choice: 2Do you want to enable DHCP on this interface (y/n) [n]: yDo you want to apply the configurations (y/n) [y]: yThis may take few moments. Please wait..All CLI configurations were applied successfully.Press any key to continue

Step 3 Enter the Setup utility and enter the following values for the NE-DEMO-SE1:

CDE# setupWhat is the mode of the device (SE/SR/CDSM): SEIs this SE going to be managed by aCDSM (Content Delivery System Manager) (y/n) [y]: yPlease choose an interface to configure from the following list:1: GigabitEthernet 1/02: GigabitEthernet 2/0Enter choice: 1Do you want to enable DHCP on this interface (y/n) [n]: nPlease enter the IP address of this interface: 10.1.4.10Please enter the netmask of this interface: 255.255.255.0Please enter the default gateway: 10.1.4.1Please enter the domain name server ip: 171.69.2.133Please enter the domain name: spcdn.comPlease enter the hostname: NE-DEMO-SE1Please enter CDSM (Content Delivery System Manager) IP or Host name: 10.1.4.31Do you want to apply the configurations (y/n) [y]: yThis may take few moments. Please wait..All CLI configurations were applied successfully.Press any key to continue..

NE-DEMO-SE1# setupWhat is the mode of the device (SE/SR/CDSM) [SE]:Please choose an interface to configure from the following list:1: GigabitEthernet 1/02: GigabitEthernet 2/0Enter choice: 2Do you want to enable DHCP on this interface (y/n) [n]: yDo you want to apply the configurations (y/n) [y]: yThis may take few moments. Please wait..All CLI configurations were applied successfully.Press any key to continue

Step 4 Enter the Setup utility and specify the following values for the NE-DEMO-SE2:

CDE# setupWhat is the mode of the device (SE/SR/CDSM): SE

6

Is this SE going to be managed by aCDSM (Content Delivery System Manager) (y/n) [y]: yPlease choose an interface to configure from the following list:1: GigabitEthernet 1/02: GigabitEthernet 2/0Enter choice: 1Do you want to enable DHCP on this interface (y/n) [n]: nPlease enter the IP address of this interface: 10.1.4.14Please enter the netmask of this interface: 255.255.255.0Please enter the default gateway: 10.1.4.1Please enter the domain name server ip: 171.69.2.133Please enter the domain name: spcdn.comPlease enter the hostname: NE-DEMO-SE2Please enter CDSM (Content Delivery System Manager) IP or Host name: 10.1.4.31Do you want to apply the configurations (y/n) [y]: yThis may take few moments. Please wait..All CLI configurations were applied successfully.Press any key to continue..

NE-DEMO-SE2# setupWhat is the mode of the device (SE/SR/CDSM) [SE]:Please choose an interface to configure from the following list:1: GigabitEthernet 1/02: GigabitEthernet 2/0Enter choice: 2Do you want to enable DHCP on this interface (y/n) [n]: yDo you want to apply the configurations (y/n) [y]: yThis may take few moments. Please wait..All CLI configurations were applied successfully.Press any key to continue

Activating the Devices in the Content Delivery SystemVerify connectivity to the CDSM.

Step 1 Using a web browser, log in via HTTPS to the CDSM using port 8443. In this example, the IP address assigned by the DHCP administrator is 172.22.30.158, so the URL is https://172.22.30.158:8443.

The Security Alert message is displayed.

Note If you are using Mozilla Firefox version 3.01 or higher as your web browser program, you need to add the CDSM IP address to the exception list. After entering the CDSM IP address with port 8443, Firefox displays a Secure Connection Failed message with a link stating “Or you can add an exception.” Click this link, then click Add Exception. The Add Security Exception dialog box is displayed. Click Get Certificate. and then click Confirm Security Exception. The CDSM IP address has been added to the exception list and you will no longer get the Secure Connection Failed message.

7

The CDSM Login page is displayed (Figure 2).

Figure 2 Internet Streamer CDSM Login Page

Step 2 Enter the default username (admin) and password (default) and click Login.

Step 3 From the CDSM home page, choose Devices > Devices. You should see all the devices (Figure 3). NE-DEMO-SE1, NE-DEMO-SE2, and NE-DEMO-SR show as “Inactive.”

Figure 3 Devices Table Page

Step 4 Create two new locations for the devices: DEMO-LOCATION-TIER1 and DEMO-LOCATION-TIER2. DEMO-LOCATION-TIER1 will be the parent location of DEMO-LOCATION-TIER2.

a. To create DEMO-LOCATION-TIER1, choose Devices > Locations > Create New Location. The Creating New Location page is displayed (Figure 4).

8

Figure 4 Creating New Location Page

b. In the Name field, enter DEMO-LOCATION-TIER1 and click Submit. The location is created.

c. To create DEMO-LOCATION-TIER2, choose Devices > Locations > Create New Location. The Creating New Location page is displayed (Figure 4).

d. In the Name field, enter DEMO-LOCATION-TIER2.

e. From the Parent Location drop-down list, choose DEMO-LOCATION-TIER1 as the parent.

f. Click Submit. The location is created.

Step 5 Activate the Service Engines and associate them with their locations. Choose Devices > Devices and click the Edit icon to the left of NE-DEMO-SE1 to edit the device. The Device home page is displayed.

Step 6 Click Show All to expand the left-panel menu.

Step 7 Choose Device Activation. The Device Activation page is displayed (Figure 5).

Figure 5 Device Activation Page—Service Engine

9

Step 8 From the Select a Location drop-down list, select DEMO-LOCATION-TIER1.

Step 9 Check the Activate check box and click Submit.

Step 10 Repeat steps 5 through 9 for NE-DEMO-SE2 and NE-DEMO-SR, selecting DEMO-LOCATION-TIER2 as the location.

Step 11 View the Devices Table page by choosing Devices > Devices. The device activation is in progress. After a while, which can be a few minutes, the status for each device displays “Online.”

Updating a CDE Software ImageIf you need to update a CDE software image for a device, place the software image on an FTP server accessible from the device’s network and use the copy ftp install <ftp-server> <remotefiledir> <remotefilename> command.

You will be prompted for the FTP username and password.

Configuring the Domain Name System ServerThe Domain Name System (DNS) server must be configured with the hostnames and IP addresses of the SEs and SR. Each hostname will resolve to the IP address.

Step 1 Log in to the DNS server, and edit the /var/named/chroot/etc/named.conf file.

//// named.conf for Red Hat caching-nameserver//

options{ directory “/var/named”; //dumpfile “/var/named/data/cache_dump.db”; //statistics-file “/var/named/data/named_stats.txt”; listen-on {2.224.22.36;}; /* * If there is a firewall between you and nameservers you want * to talk to, you might need to uncomment the query-source * questions using port 53, but BIND 8.1 uses an unprivileged * port by default. */ query-source address * port 53;};

//// a caching only nameserver config//controls { inst 127.0.0.1 allow { localhost; } keys { rndckey; };

Step 2 Add zone cds.com IN to the named.conf file.

file “named.or”;};

zone “cds.com” IN { type mater’; file “cds.com.zone”; allow-update { none; };};

Step 3 Edit the /var/named/chroot/var/named/cds.com zone entry.

10

Note Be sure to use the IP address of the primary interface on the SR (in the example, this is 10.1.4.13), otherwise a DNS query will not get a response from the SR.

$TT 1D@ UB SIA Kbxdbs,cds,cin, riit,Kbxdbs,cds,cin ( 2002050200 ; serial 3H ; refresh 15M ; retry 1W ; expire 1D ; minimum TTL

;; Name Servers IN NS Lnxdns.cds.com. IN A 127.0.0.1 IN AAAA ; ; 1 IN A 2.224.22.36

;; Service Routed Domains;rfqdn IN NS NE-DEMO-SR; Primary SR

NE-DEMO-SE1 IN A 3.1.4.10NE-DEMO-SE2 IN A 3.1.4.14NE-DEMO-SR IN A 3.1.4.13

Step 4 Open the named.conf file.

//// named.conf for Red Hat caching-nameserver//

options{ directory “/var/named”; //dumpfile “/var/named/data/cache_dump.db”; //statistics-file “/var/named/data/named_stats.txt”; listen-on {2.224.22.36;}; /* * If there is a firewall between you and nameservers you want * to talk to, you might need to uncomment the query-source * questions using port 53, but BIND 8.1 uses an unprivileged * port by default. */ query-source address * port 53;};

//// a caching only nameserver config//controls { inst 127.0.0.1 allow { localhost; } keys { rndckey; };

Step 5 Edit the named.conf file.

file “named.cr”;};

zone “cds.com” IN { type mater; file “cds.com.zone”; allow-update { none; };};

include “/etc/rndc.key”;

11

Step 6 Enter the service named restart command to restart the service.

[root@Lnxdns ~] # service named restart

3 Configuring Delivery ServicesThis section includes the following procedures:

• Creating a Content Origin

• Defining a Delivery Service

Creating a Content Origin

Step 1 From the CDSM home page, choose Services > Service Definition > Content Origins. The Content Origin Table page is displayed.

Step 2 Click the Create New Content Origin icon to create a new Content Origin. The Create New Content Origin page is displayed (Figure 6).

Figure 6 Create New Content Origin Page

Step 3 In the Name field, enter a name for the Content Origin server.

Step 4 In the Origin Server field, enter the fully qualified domain name (FQDN) of the Content Origin server. In the example, this is “ofqdn.cds.com.”

Step 5 In the Service Routing Domain Name field, enter the Service Routing Domain Name to be the domain name that is published as part of the portal. Client requests are directed to this domain name. In the example, this is “rfqdn.cds.com.”

Step 6 Click Submit.

Step 7 Acknowledge the Content Origin submitted and choose the Content Origins tab to view the new entry (Figure 7).

12

Figure 7 Content Origin Table Page

Defining a Delivery ServiceTo create a delivery service, do the following:

Step 1 Choose Services > Service Definition > Delivery Services and then click the Create New Delivery Service icon (Figure 8).

Figure 8 Delivery Service Table Page

The Create Delivery Service page is displayed (Figure 9).

13

Figure 9 Create Delivery Service Page

Step 2 In the Name field, enter a name for the delivery service. In the example, this is “Demo VOD Delivery Service.”

Step 3 In the Content Origin field, select the name of the Content Origin you just created.

Step 4 In the Delivery Service Quota field, specify the delivery service quota as the total size of the contents that will be ingested in to the delivery service.

Step 5 Click Submit. The left-panel menu displays the delivery service options.

Step 6 To associate content to the delivery service that must be ingested, from the left-panel menu choose Delivery Service Content and then click the Add Content icon. The Delivery Service Content page is displayed (Figure 10).

Figure 10 Delivery Service Content Page

Step 7 In the Source URL field, provide a specific directory on the Content Origin server. All content in that directory will be preingested in to the Service Engines. In the example, “http” is selected from the drop-down list and “ofqdn.cds.com/test_prepos” is the directory.

This is a single item, so the Single Item check box is checked.

Step 8 In the Link Depth field, enter the number of directory levels below the Source URL that you want to search for content.

14


To associate another directory containing content that must be preingested, click the Add Content icon again. The Delivery Service Content page is displayed showing the list of content to be preingested in the Content Table (Figure 11).

Figure 11 Content Table Page

Step 10 Associate the Service Engines with this delivery service. From the left-panel menu, choose Assign Service Engines. The Service Engine Table page is displayed (Figure 12).

Figure 12 Service Engine Table Page

Step 11 Click the Assign icon (Figure 12) next to the Service Engine name to assign each Service Engine to this delivery service. The icon changes to a green arrow wrapped around a blue “X.”

Step 12 From the Assign Content Acquirer drop-down list, select NE-DEMO-SE1 to be the Content Acquirer.

Step 13 Click Submit. The icon next to each Service Engine assigned changes to a green check mark (Figure 13).

Figure 13 Service Engine Table Page—Assigned Service Engines

Step 14 To make sure the content has been acquired on the Content Acquirer, start an SSH session on the Content Acquirer (NE-DEMO-SE1) and enter the following commands:

15

NE-DEMO-SE1# show statistics acquirer

Statistics for delivery -service-id : 275delivery-service-name | Demo VOD Delivery Service--------------------------------------------------

Manifest:--------- Fetch Errors : 0 Parsing Errors : 0 Parsing Warnings : 0

Acquisition:------------ Total Number of Acquired Objects : 4 Disk Quota Used for Acquired Objects : 33.044 MB Total Number of Failed Objects : 0 Total Number of Re-Check Failed Objects : 0

If the acquisition is complete, the number of acquired objects is listed. In the example above, the delivery service ID “275” is displayed. The following command displays a list of the acquired content.

NE-DEMO-SE1# show statistics acquirer contents delivery-service-id 275

Contents Acquired for the Delivery Service ID:275-------------------------------------

Acquired Contents:------------------

Modification Time : Thu Oct 25 01:04:16 2007Size : 19999380 BytesUrl : http://ofqdn.cds.com/test_prepos/test.wmv

Modification Time: Thu Oct 25 01:04:16 2007Size : 1425570 BytesUr : http://ofqdn.cds.com/test_prepos/test.mov

Modification Time: Thu Oct 25 01:04:16 2007Size : 44 BytesUrl : http://ofqdn.cds.com/test_prepos/test.html

Modification Time : Thu Oct 25 01:04:16 2007Size : 283556 BytesUrl : http://ofqdn.cds.com/vod/test_prepos.flv

16

Step 15 To view the content replicated on NE-DEMO-SE2 from NE-DEMO-SE1, start an SSH session and enter the following command:

NE-DEOM-SE2# show statistics replication delivery-service

Step 16 On the CDSM home page, from the Delivery Service left-panel menu, choose Replication Status. The CDSM reports the state of the Acquirer and Receiver Types as “Completed.” See Figure 14.

Figure 14 Delivery Service Replication Status Page

4 Configuring the Service RouterThis section includes the procedure for assigning a Coverage Zone file. The Service Router was activated in the “Activating the Devices in the Content Delivery System” section on page 6.

Assigning a Coverage Zone File

Note This procedure assumes you have already created a Coverage Zone file. For information on creating a Coverage Zone file, see the “Creating Coverage Zone Files” appendix in Cisco Internet Streamer CDS 2.6 Software Configuration Guide.

Step 1 From the CDSM home page, choose System > Configuration. The System Configuration page is displayed.

Step 2 From the left-panel menu, choose Service Routing > Coverage Zone File Registration. The Coverage Zone File Table page is displayed.

Step 3 Click the Create New Coverage Zone File icon. The Coverage Zone File page is displayed (Figure 15).

http://cisco.com/en/US/docs/video/cds/cda/is/2_0/configuration/guide/coverzoneXML.html

17

Figure 15 Coverage Zone File Page

Step 4 From the File Import Method drop-down list, select Upload.

Step 5 Click the Coverage Zone File Upload Path Browse button to browse to the location of the Coverage Zone file you created.


Step 7 Choose Devices > Devices and click the Edit icon next to NE-DEMO-SR. The Device home page is displayed.


Step 9 Choose Device Activation. The Device Activation page is displayed (Figure 16).

Step 10 From the Coverage Zone File drop-down list, select the Coverage Zone file you uploaded in the previous steps and click Submit.

Figure 16 Device Activation Page—Service Router

Step 11 Open an SSH session to the Service Router and enter the show service-router routes command. All network routes to the Content Origin are displayed.

NE-Demo-SR# show service-router routes---- All network IPV4 routes to Content Origin ----domain: rfqdn.cds.com (Origin Server: ofqdn.cds.com)171.71.0.0/16 5 NE-DEMO-SE2 (Operational, Static)171.70.0.0/16 5 NE-DEMO-SE2 (Operational, Static)

18

170.50.20.0/24 5 NE-DEMO-SE1 (Operational, Static)3.1.4.0/24 20 NE-DEMO-SE1 (Operational, Static)3.1.4.0/24 20 NE-DEMO-SE2 (Operational, Static)

---- All network IPV6 routes to Content Origin ----domain: rfqdn.cds.com (Origin Server: ofqdn.cds.com)

---- Best network IPV4 routes to Content Origin ----domain: rfqdn.cis.com (Origin Server: ofqdn.cds.com)171.71.0.0/16 5 NE-DEMO-SE2171.70.0.0/16 5 NE-DEMO-SE2170.50.20.0/24 20 NE-DEMO-SE13.1.4.0/24 20 NE-DEMO-SE13.1.4.0/24 20 NE-DEMO-SE2

---- Best network IPV6 routes to Content Origin ----domain: rfqdn.cis.com (Origin Server: ofqdn.cds.com)

5 Verifying the Web EngineThis section consists of the following procedures:

• Verifying Preingested Web Content

• Verifying Dynamically Ingested Web Content

Verifying Preingested Web Content

Note Content must be preingested. This was accomplished in the “Configuring Delivery Services” section on page 11. Verify that the content has been pre-positioned by using the show distribution object-status name-of-object command.

Step 1 In a web browser on the client PC, enter the URL of the preingested HTML content using the Service Routing Domain Name in the URL. In the example, this is “http://rfqdn.cds.com/test_prepos/test.html.” Client requests are directed to this domain name and are then redirected by the Service Router to the content on the Service Engine. Figure 17 shows the initial URL on the left and the redirection on the right.

Figure 17 URL Redirection for Preingested Content

19

Step 2 On the Service Engines, verify that the request was served as a preingested hit. View the HTTP request statistics by starting an SSH session and entering the show statistics web-engine command. In this case, the Service Router redirected the request to NE-DEMO-SE2, which served the request.

NE-DEMO-SE1# show statistics web-engine

HTTP Request Info Statistics-----------------------Num Lookups : 0Preposition Hit : 0External Hit : 0Cache Hit : 0Cache Miss : 0Partial Cache Hit : 0Cache Bypass : 0Live Miss : 0Live Hit : 0ASX Meta Response : 0

HTTP Request Type Statistics-----------------------Get Requests : 0Post Requets : 0Head Requets : 0Range Requests Received : 0Range Requests Sent : 0Revalidation Requests Received : 0Revalidation Requests Sent : 0Liveness Query : 0WMT(http) Redirected Requests : 0Local Requests : 0Play Live Requests : 0Total Outgoing Requests : 0

HTTP Authorization Statistics----------------------Authorization Allow : 0 Authorization No Cache : 0 Authorization Force Revalidate : 0 Authorization Deny : 0 Authorization Rewrite : 0 Authorization GenerateSign : 0 Authorization Redirect : 0 Authorization Resolve : 0

WMT(http) Rule Statistics----------------------Allow : 0 Block : 0 Url Redirect : 0 Url Rewrite : 0 Validate Url Signature : 0 No Cache : 0

HTTP Error Statistics----------------------Client Errors : 0 Server Errors : 0 Bad Requests : 0 Error Response Miss : 0 Error Response Hit : 0

Statistics was last cleared on Thursday, 09-Sep-2010 14:15:52 PDT.


HTTP Request Info Statistics

20

-----------------------Num Lookups : 1Preposition Hit : 1External Hit : 0Cache Hit : 0Cache Miss : 0Partial Cache Hit : 0Cache Bypass : 0Live Miss : 0Live Hit : 0ASX Meta Response : 0


HTTP Authorization Statistics----------------------Authorization Allow : 1Authorization No Cache : 0Authorization Force Revalidate : 0Authorization Deny : 0Authorization Rewrite : 0Authorization Resolve : 0



HTTP Error Statistics----------------------Client Errors : 0Server Errors : 0Bad Requests : 0


21

Verifying Dynamically Ingested Web Content

Step 1 In a web browser on the client PC, enter the URL of non-preingested HTML content on the Service Router. This is content that exists on the Content Origin server or some other server that is accessible but not yet preingested. In the example, the Content Origin server has a directory “test_cache” with a content object “test.html.” Figure 18 shows the initial URL on the left and the redirection on the right.

Figure 18 URL Redirection for Non-Preingested Content

This is a cache miss scenario. Neither Service Engine had the content preingested, so the content is acquired by NE-DEMO-SE1 (the Content Acquirer). The content is then cached and replicated to NE-DEMO-SE2 (the receiver, which also happens to be the SE that is serving this client request). NE-DEMO-SE2 then serves the request (as visible by the new URL in Figure 18), having cached the content as well.

Step 2 View the HTTP request statistics by entering the show statistics web-engine command.




HTTP Authorization Statistics----------------------Authorization Allow : 1Authorization No Cache : 0Authorization Force Revalidate : 0

22

Authorization Deny : 0Authorization Rewrite : 0Authorization Resolve : 0








WMT(http) Rule Statistics----------------------Allow : 1 Block : 0 Url Redirect : 0 Url Rewrite : 0 Validate Url Signature : 0

23

No Cache : 0



Step 3 Verify that the content was cached properly on NE-DEMO-SE1 and NE-DEMO-SE2 by entering the show cache content command.

NE-DEMO-SE1# show cache contentMax-cached-entries is set as 20000000Number of cal cached assets: 1Eviction protection is disabled.Cache eviction-preferred-size configured is large------------------------------------------------Size URL------------------------------------------------44 http://ofqdn.cds.com/test_cache/test.html

NE-DEMO-SE2#show cache contentMax-cached-entries is set as 20000000Number of cal cached assets: 1Eviction protection is disabled.Cache eviction-preferred-size configured is large------------------------------------------------Size URL------------------------------------------------44 http://ofqdn.cds.com/test_cache/test.html

Step 4 Clear the cache content in the web browser in order to make sure future requests are handled by the Service Engines instead of from the browser’s local cache.

Step 5 In the web browser, request the same content again (http://rfqdn.cds.com/test_cache/test.html). Figure 19 shows the initial URL request on the left and the new URL on the right.

Figure 19 Show Statistic Requests on NE-DEMO-SE1—Cached Content

Step 6 View the HTTP request statistics again by entering the show statistics web-engine command.


HTTP Request Info Statistics-----------------------Num Lookups : 1Preposition Hit : 0External Hit : 0Cache Hit : 0Cache Miss : 1Partial Cache Hit : 0Cache Bypass : 0

24

Live Miss : 0Live Hit : 0ASX Meta Response : 0








HTTP Authorization Statistics

25

----------------------Authorization Allow : 2Authorization No Cache : 0Authorization Force Revalidate : 0Authorization Deny : 0Authorization Rewrite : 0Authorization Resolve : 0



In this case, NE-DEMO-SE2 served the request, and it is a cache hit scenario. The content was cached from the previous attempt, and now the same content is served from the cache.

6 Verifying the Windows Media Streaming EngineThis section consists of the following procedures:

• Verifying Preingested Windows Media Content

• Verifying Dynamically Ingested Windows Media Content

• Managing Windows Media Live Programs

Verifying Preingested Windows Media Content


Step 1 On the client PC, start the Windows Media Player.

Step 2 Choose File > Open URL.

Step 3 Enter the URL of the preingested content in the Open URL dialog box (Figure 20) and click OK. In the example, this is “rtsp://rfqdn.cds.com/test_prepos/test.wmv.”

Figure 20 Open URL Dialog Box

The video begins to play.

Step 4 To view the statistics on the video file, choose View > Statistics and then click the Advanced tab (Figure 21).

26

Figure 21 Windows Media Player Statistics

Step 5 To view the request flow, enter the show statistics wmt streamstat command on the SEs. In this case, the request is served from NE-DEMO-SE2.

NE-DEMO-SE1# show statistics wmt streamstatDetailed Stream Statistics=====================================

Incoming Streams:=================Stream-Id Type Source State Bytes-Recd Duration Bandwidth Server-IP Url-Requested

Outgoing Streams:=================Stream-Id Client-IP Type Transport Source State Pkts-sent Bytes-sent Duration BW Instance


Incoming Streams:=================Stream-Id Type Source State Bytes-Recd Duration Bandwidth Server-IP Url-Requested

Outgoing Streams:=================Stream-Id Client-IP Type Transport Source State Pkts-sent Bytes-sent Duration BW Instance8895 171.70.222.171 VOD NONE LOCAL Setup 0 0 0 0 test_prepos/test.wmv

Verifying Dynamically Ingested Windows Media Content



Step 3 Enter the URL of content that has not been preingested in the Open URL dialog box (Figure 22) and click OK. In the example, this is “rtsp://rfqdn.cds.com/test_cache/test.wmv.”

27





Step 5 To view the request flow, enter the show statistics wmt streamstat command on the SEs. In this case, the request is served from NE-DEMO-SE2.

NE-DEMO-SE1# clear statistics wmtNE-DEMO-SE1# show statistics wmt streamstatDetailed Stream Statistics=====================================

Incoming Streams:=================Stream-Id Type Source State Bytes-Recd Duration Bandwidth Server-IP Url-Requested20548 VOD RMT_HTTP Play 6113001 21 1012 3.1.13.6 rtsp;//ofqdn.cds.com/test_cache/test.wmvOutgoing Streams:=================Stream-Id Client-IP Type Transport Source State Pkts-sent Bytes-sent Duration BW Instance27521 3.1.4.14 VOD RTSPT RMT_HTTP Play 388 3104000 19 549 test_cache/test.wmv

NE-DEMO-SE2# clear statistics wmtNE-DEMO-SE2# show statistics wmt streamstatDetailed Stream Statistics=====================================

Incoming Streams:=================Stream-Id Type Source State Bytes-Recd Duration Bandwidth Server-IP Url-Requested12079 VOD RMT_RTSP Play 2241074 23 1550 3.1.4.10 rtsp;//ofqdn.cds.com/test_cache/test.wmv

Outgoing Streams:=================

28

Stream-Id Client-IP Type Transport Source State Pkts-sent Bytes-sent Duration BW Instance12043 171.70.222.171 VOD RTSPT RMT_RTSP Play 279 2232000 13 7201

test_cache/test.wmv

Managing Windows Media Live ProgramsEach live program uses a live delivery service to deliver the live program. This section includes the following procedures:

• Creating a Live Windows Media Delivery Service

• Configuring a Windows Media Live Program

• Verifying Windows Media Live Content Playback

Creating a Live Windows Media Delivery Service

Step 1 From the Delivery Services Table page, click the Create New Delivery Service icon (Figure 24).

Figure 24 Delivery Services Table Page



Step 2 In the Name field, enter a delivery service name. In the example, “WMTlive” is entered.

Step 3 In the Content Origin field, select the name of the Content Origin if it already exists, or create a new Content Origin by clicking the New Content Origin button and following the steps in the “Creating a Content Origin” section on page 11.

29

Step 4 Check the Live Delivery Service check box.


Step 6 Associate the Service Engines with this live delivery service. From the left-panel menu, choose Assign Service Engines. The Service Engine Table page is displayed (Figure 12 on page 14).

Step 7 Click the Assign icon next to the Service Engine name to assign each Service Engine to this delivery service. The icon changes to a green arrow wrapped around a blue “X.”


Step 9 Check the Primed check box, if required. When a delivery service is “primed,” the unicast-out stream is pulled from the Content Origin server to an SE before a client ever requests the stream. This action avoids the Real Time Streaming Protocol (RTSP) setup time that clients might experience as a delay.

Step 10 Click Submit. The icon next to each Service Engine assigned changes to a green check mark (Figure 26).

Figure 26 Service Engine Table Page—Live Delivery Service

Configuring a Windows Media Live Program

Step 1 Choose Services > Live Video. The Live Programs Table page is displayed.

Step 2 Click the Create New icon. The Adding New Program page is displayed (Figure 27).

Figure 27 Adding New Program Page

30

Step 3 In the Name field, enter the name of the live program. In the example, “WMTdemolive” is entered.

Step 4 In the Type drop-down list, select Windows Media Live.

Step 5 Click Submit. The left-panel menu displays the program options.

Step 6 From the left-panel menu, choose Select Live Delivery Service. The Live Delivery Service Table page is displayed (Figure 28).

Figure 28 Live Delivery Service Table Page

Step 7 Click the radio button next to the live delivery service (in the example, “WMTlive” is selected) and click Submit.

Step 8 From the left-panel menu, choose Assign Service Engines and verify that the SEs and Content Acquirer are assigned to this delivery service.

Step 9 From the left-panel menu, choose Live Streaming. The Live Streaming page is displayed (Figure 29).

Figure 29 Live Streaming Page

Step 10 In the Live Source URL field, enter the URL of the live source, using either the URL of the Windows Media encoder or of the Windows Media Streamer Server and port (rtsp://WMencoder or rtsp://WMStreamerServer:port/).

31

If you are running the encoder on a local host, you would enter the Internet URL obtained from the encoder.

Step 11 Check the Enable Unicast Delivery to Client check box.

Step 12 From the Unicast URL Reference drop-down list, select the unicast URL reference; for example, rtsp://rfqdn.cds.com/wmtlive.


Step 14 From the left-panel menu, choose Schedule.

Step 15 Click the Play Forever radio button.


Verifying Windows Media Live Content Playback



Step 3 Enter the URL for the live program in the Open URL dialog box (Figure 30) and click OK. In the example, this is “rtsp://rfqdn.cds.com/wmtlive.”





Step 5 To view the incoming and outgoing streams, enter the show statistics wmt streamstat command on the SEs streaming the content. In this case, the request is served from NE-DEMO-SE2.


Incoming Streams:=================

32

Stream-Id Type Source State Bytes-Recd Duration Bandwidth Server-IP Url-Requested18872 LIVE RMT_HTTP Play 84150 241 288 171.70.22.171 http://171.70.222.171:0000

Outgoing Streams:=================Stream-Id Client-IP Type Transport Source State Pkts-sent Bytes-sent Duration BW Instance18889 3.1.4.14 LIVE RTSPT RMT_HTTP Play 5393 7787492 233 288 8080


Incoming Streams:=================Stream-Id Type Source State Bytes-Recd Duration Bandwidth Server-IP Url-Requested28772 LIVE RMT_RTSP Play 8205265 246 289 3.1.4.10 rtsp;//3.1.4.10/wmt_proxy/rtsp&ofqdn.cds.com/wmtlive/__CDS/http&171.70.111.171&8080

Outgoing Streams:=================Stream-Id Client-IP Type Transport Source State Pkts-sent Bytes-sent Duration BW Instance28755 171.70.222.171 LIVE RTSPU RMT_RTSP Play 5582 8060408 241 288

wmtlive

7 Enabling and Verifying the Movie Streamer Engine

Note In CDS Release 2.6, live streaming is in full production. Prefetched, cached, and dynamically cached content remain in a demonstration state.For details of live streaming performance for Movie Streamer, please refer to the release-specific performance bulletin.

This section includes the following procedures:

• Enabling the Movie Streamer Engine

• Preparing Movie Streamer Content for Ingest

• Verifying Preingested Movie Streamer Content

• Verifying Dynamically Ingested Movie Streamer Content

• Managing Movie Streamer Live Content

Enabling the Movie Streamer Engine

Step 1 From the CDSM home page, choose Devices > Devices. The Devices Table page is displayed (Figure 32).

33


Step 2 Click the Edit icon next to NE-DEMO-SE1. The Device home page is displayed.


Step 4 Choose Application Control > Movie Streamer > General Settings. The Movie Streamer page is displayed.

Step 5 Check the Enable Movie Streamer Services check box and click Submit. Leave the other fields with their default settings. Movie Streamer is now enabled on this device.

Step 6 Repeat the above steps for all other SEs. No action is required on the SR.

Preparing Movie Streamer Content for IngestThe Movie Streamer delivers hinted MP4, hinted 3GP, and hinted MOV files to clients over the Internet and mobile networks. Hinted files contain hint tracks, which store packetization information that tell the streaming server how to package content for streaming. Apple Quicktime Pro can be used to generate the hint tracks.

Step 1 Launch Apple QuickTime Pro.

Step 2 Choose File > Open File, and select a movie file to open.

Step 3 Choose Windows > Show Movie Properties. If there is a Hinted Video Track present, as shown in Figure 33, open the next movie file.

Figure 33 Movie Properties Dialog Box

Step 4 Choose File > Export. The Save Exported File dialog box is displayed (Figure 34).

34

Figure 34 Save Exported File Dialog Box

Step 5 From the Export drop-down list, choose Movie to Hinted Movie.

Step 6 Click Options. The Hint Exporter Settings dialog box is displayed (Figure 35).

Figure 35 Hint Exporter Settings Dialog Box

Step 7 Check the Make Movie Self-Contained check box and the Optimize Hints For Server check box.

Step 8 Click OK.

Step 9 Click Save in the Save Exported File dialog box.

The movie file is ready to be either preingested or dynamically ingested.

Verifying Preingested Movie Streamer Content


Step 1 On the client PC, start the Apple QuickTime Player.


Step 3 Enter the URL of the preingested content in the Open URL dialog box (Figure 36) and click OK. In the example, this is “rtsp://rfqdn.cds.com/test_prepos/test.mov.”

35



Step 4 To view the statistics on the video file, choose Windows > Show Movie Inspector (Figure 37).

The current statistics are displayed and updated as the video streams and plays.

Figure 37 QuickTime Player Statistics

Step 5 To view the request flow, display the statistics by entering the show statistics movie-streamer all command.

NE_DEMO-SE2# show statistics movie-streamer allMovie Streamer Request Statistics Total ---------------------------------------Current RTSP sessions: 0 Total RTSP sessions: 1 Current RTP connections: 0 Total RTP connections: 1

CDN Related Statistics ---------- Preposition Hits: 1 Cache Hits: 0 Cache Miss: 0 Live Requests: 0

Cache Revalidation Statistics --------- Fresh Content Requests: 0 Revalidated Requests: 0

Movie Streamer Bandwidth Usage Statistics Total-----------------------------------------Current Incoming bandwidth: 0 bpsCurrent Outgoing bandwidth; 0 bps Current Total bandwidth: 0 bps

Average Incoming bandwidth: 0 bpsAverage Outgoing bandwidth: 0 bps Average Total bandwidth: 0 bps

By Type of Connection ---------Unicast Incoming Bandwidth: 0 bps Multicast Incoming Bandwidth: 0 bpsUnicast Outgoing Bandwidth: 0 bps Multicast Outgoing Bandwidth: 0 bps

36

By Type of Content ------ Live Incoming Bandwidth: 0 bps VOD Incoming Bandwidth: 0 bps Live Outgoing Bandwidth: 0 bps VOD Outgoing Bandwidth: 0 bps

Overall Traffic ------- Incoming Bytes: 0 Bytes Outgoing Bytes: 2103939 Bytes Total Bytes: 2103939 Bytes

Incoming Packets: 0 Outgoing Packets: 1403 Total Packets: 1403

Movie Streamer Error Statistics Total--------------------------------------- Server Error -------- Internal Error: 0 Not Implemented: 0 Server Unavailable: 0 Gateway Timeout: 0 Others: 0

Client Error -------- Bad Request: 0 File Not Found: 0 Session Not Found: 0 Method Not Allowed: 0Not Enough Bandwidth: 0 Client Forbidden: 0 Others: 0

Movie Streamer Performance Statistics Total----------------------------------------- CPU Usage: 0.000000 % UpTime: 5416 secStatistics were last cleared on Thursday, 25-Oct-2007 23:53:59 UTC.

Note In this example, current connections and bandwidth are all zero because the movie has finished playing at the time the statistics were displayed.

Note This example shows the full output for the show statistics command, which were enhanced. All remaining examples for the Movie Streamer statistics show only the relevant information.

Step 6 Play the movie again, and before it completes, display the statistics again.

As the statistics show, there are two current connections: 1 RTP and 1 RTSP.

NE_DEMO-SE2# show statistics movie-streamer allMovie Streamer Request Statistics Total---------------------------------------Current RTSP sessions: 1 Total RTSP sessions: 2Current RTP connections: 1

37

Total RTP connections: 2

CDN Related Statistics ---------- Preposition Hits: 2 Cache Hits: 0 Cache Miss: 0 Live Requests: 0

Cache Revalidation Statistics --------- Fresh Content Requests: 0 Revalidated Requests: 0

Movie Streamer Bandwidth Usage Statistics Total---------------------------------------Current Incoming bandwidth: 0 bpsCurrent Outgoing bandwidth: 0 bps Current Total bandwidth: 0 bps


...Omitted contents

Overall Traffic ---------- Incoming Bytes: 0 Bytes Outgoing Bytes: 14490660 Bytes Total Bytes: 14490660 Bytes

...Omitted contents

38

Verifying Dynamically Ingested Movie Streamer ContentWhen content requested by a client is not in the CDS, it is dynamically ingested from the original source and streamed to the client by an SE.



Step 3 Enter the URL of a sample MOV file that has not been preingested into the CDS in the Open URL dialog box (Figure 38) and click OK. In the example, this is “rtsp://rfqdn.cds.com/test_dyn.mov.”



Step 4 To view the request flow, display the statistics, enter the show statistics movie-streamer all command.

NE_DEMO-SE1# show statistics movie-streamer allMovie Streamer Request Statistics Total--------------------------------------- Current RTSP sessions: 1 Total RTSP sessions: 4Current RTP connections: 1 Total RTP connections: 4

...Omitted contents

Movie Streamer Bandwidth Usage Statistics Total-----------------------------------------Current Incoming bandwidth: 207115 bpsCurrent Outgoing bandwidth: 0 bps Current Total bandwidth: 207115 bps


...Omitted contents

Overall Traffic----------

Incoming Bytes: 12667891 Bytes Outgoing Bytes: 12609164 Bytes Total Bytes: 25277055 Bytes

...Omitted contents


39

...Omitted contents



...Omitted contents



...Omitted contents

Managing Movie Streamer Live ContentThe Movie Streamer can be configured to stream live content from a source to clients. This requires a server capable of serving live MOV content to the CDS; for example, an Apple QuickTime Streaming Server or a Darwin Streaming Server, or another compatible live source.

Creating a Live Movie Streamer Delivery Service

Step 1 Choose Services > Service Definition > Delivery Services. The Delivery Service Table page is displayed.

Step 2 Click the Create New Delivery Service icon.


40


Step 3 In the Name field, enter a delivery service name; for example, “LiveService.”

Step 4 In the Content Origin field, select the name of the Content Origin if it already exists, or create a new Content Origin by clicking the New Content Origin button and following the steps in the “Creating a Content Origin” section on page 11.

Step 5 Check the Live Delivery Service check box.


Step 7 From the left-panel menu, choose Assign Service Engines. The Service Engine Table page is displayed (Figure 40).

Figure 40 Service Engine Table Page—Movie Streamer Live Delivery Service

Step 8 Click the Assign icon next to the Service Engine name to assign each Service Engine to this delivery service. The icon changes to a green arrow wrapped around a blue “X.”


41

Step 10 Check the Primed check box, if required. When a delivery service is “primed,” the unicast-out stream is pulled from the Content Origin server to an SE before a client ever requests the stream. This action avoids the RTSP setup time that clients might experience as a delay.

Step 11 Click Submit. The icon next to each Service Engine assigned changes to a green check mark.

Configuring a Movie Streamer Live Program

Step 1 Choose Services > Live Video > Live Programs. The Live Programs Table page is displayed (Figure 41).

Figure 41 Live Programs Table Page

Step 2 Click the Create a New Program icon. The Adding New Program page is displayed (Figure 42).

Figure 42 Adding New Program Page

Step 3 In the Name field, enter the name of the live program; for example, “MovieLiveProgram.”

Step 4 In the Type drop-down list, select Movie Streamer Live.

Step 5 Click Submit. The left-panel menu displays the program options.

Step 6 From the left-panel menu, choose Select Live Delivery Service. The Live Delivery Service Table page is displayed (Figure 43).

Step 7 Click the radio button next to the live delivery service (in the example, “LiveService” is selected) and click Submit.

42

Figure 43 Live Delivery Service Table Page

Step 8 From the left-panel menu, choose Assign Service Engines and verify that the SEs and Content Acquirer are assigned to this delivery service.

Step 9 From the left-panel menu, choose Live Streaming. The Live Streaming page is displayed (Figure 44).

Figure 44 Live Streaming Page

Step 10 From the Origin Server SDP File URL drop-down list, select either RTSP or HTTP, and enter the remainder of the URL in the associated field.

Step 11 In the Backup SDP URL field, enter the backup URL. This field is only for RTSP.

When you click the Auto Populate button, the Incoming Live Streams fields (the next section on the Live Streaming page) are automatically populated based on the Origin Server SDP File URL.

43

Step 12 In the Incoming Live Streams Settings section, if the fields are not automatically populated, enter the Primary Source Server field and the Receiving Ports field manually. Receiving ports are used to define each port related to audio and video streams.

Step 13 From the Unicast URL Reference drop-down list, select a unicast URL reference. In the example, this is “rtsp://rfqdn.cds.com/movieliveprogram.sdp.”

Note Two streams are required because audio and video are considered separate streams for MOV content.


Step 15 From the left-panel menu, choose Schedule.

Step 16 Click the Play Forever radio button.


Verifying Movie Streamer Live Content Playback

Live streaming of Movie Streamer content requires a Session Description Protocol (SDP) file. The SDP file used in this procedure is the following:

v=0o=QTSS_Play_List 2079157989 2079176415 IN IP4 171.71.50.216s=C:\Program Files\Darwin Streaming Server\Playlists\untitled\unti@c=IN IP4 127.0.0.1b=AS:94t=0 0a=x-broadcastcontrol:RTSPm=video 0 RTP/AVP 96b=AS:79a=rtpmap:96 X-SV3V-ES/90000a=control:trackID=1m=audio 0 RTP/AVP 97b=AS:14a=rtpmap:97 X-QDM/22050/2a=control:trackID=2a=x-bufferdelay:4.97



Step 3 Enter the URL of the live program file in the Open URL dialog box (Figure 45) and click OK. In the example, this is “rtsp://rfqdn.cds.com/movieliveprogram.sdp.”



Step 4 To view the statistics on the video file, choose Window > Show Movie Inspector (Figure 46).

The current statistics are displayed and updated as the video streams and plays.

44

Figure 46 QuickTime Player Statistics

Step 5 To view the incoming and outgoing streams, enter the show statistics movie-streamer all command.


...Omitted contents



...Omitted contents



...Omitted contents


...Omitted contents

45



...Omitted contents



...Omitted contents

Movie Streamer Performance Statistics Total--------------------------------------- CPU Usage: 0.000000 % UpTime: 78375 secStatistics were last cleared on Friday, 26-Oct-2007 20:09:42 UTC.

Note For more information, see the “Configuring Services” chapter in the Cisco Internet Streamer CDS 2.6 Software Configuration Guide. See the “Related Publications” section on page 55 for links to the online documentation at www.cisco.com.

8 Enabling and Verifying the Flash Media Streaming EngineThis section consists of the following procedures:

• Enabling Flash Media Streaming

• Verifying Flash Media Streaming Preingested Content

• Verifying Flash Media Streaming Dynamically Ingested Content

• Verifying Flash Media Streaming—Live Streaming

Note Flash Media Streaming uses RTMP to stream live content by means of dynamic proxy. Configuration of live or rebroadcast programs is not required. When the first client requests live streaming content, the stream is created.

All RTMP calls for live content in the SWF file must be in the following format:rtmp://rfqdn/live/path/foo.flv

In this format, rfqdn is the routing domain name of the Service Router, live is the required directory, and path is the directory path to the content file that conforms to the standard URL specification.

If you are unable to store the VOD content in the required “vod” directory on your origin server, you can create a VOD virtual path for all RTMP requests. All client requests for RTMP calls still use the rtmp://rfqdn/vod/path/foo.flv format for VOD streams, but the SE replaces the “vod” directory with the string specified in the flash-media-streaming application-virtual-path vod map command.

Use the flash-media-streaming application-virtual-path vod map <mapping string> command on each SE participating in a Flash Media Streaming delivery service. The mapping string variable accepts all alpha-numeric characters and the

46

slash (/) character, and can be from 1 to 128 characters. For example, to map the “vod” directory to “media” for the go-tv-stream.com origin server, use the flash-media-streaming application-virtual-path vod map media command.

To monitor live streaming use the show statistics flash-media-streaming command and the show flash-media-streaming live command.

Enabling Flash Media Streaming

Step 1 Ensure Flash Media Streaming is enabled by using the show flash-media-streaming command.

NE-DEMO-SE2# show flash-media-streamingFlash Media Streaming is enabled.Max. allowed concurrent sessions are 2000.......Omitted contents...Allowed bandwidth is 3000000Kbps.

Step 2 If Flash Media Streaming is enabled, go to the “Verifying Flash Media Streaming Preingested Content” section on page 47. If Flash Media Streaming is not enabled, go to the next step.

Step 3 Launch a web browser, and log in to the CDSM. For more information on logging in to the CDSM, see the “Activating the Devices in the Content Delivery System” section on page 6.

Step 4 Choose Devices > Devices. The Devices Table page is displayed (Figure 47).


Step 5 Click the Edit icon next to NE-DEMO-SE1. The Device home page is displayed.


Step 7 Choose Application Control > Flash Media Streaming. The Flash Media Streaming page is displayed.

Step 8 Check the Enable check box and click Submit. Flash Media Streaming is now enabled on this device.

Step 9 Repeat the above steps for all other SEs, and also for the SR.

47

Verifying Flash Media Streaming Preingested Content


Note All RTMP calls must be in the following format:rtmp://rfqdn/vod/path/foo.flvIn this format, rfqdn is the routing domain name of the SR, vod is the required directory, and path is the directory path to the content file that conforms to the standard URL specification.

Step 1 On the client PC, start the Adobe Flash Player.

Step 2 Enter the URL of the flash file in the text box (Figure 48) and click Go. In the example, this is “rtmp://rfqdn.cds.com/vod/test_prepos.flv.”

The RTMP call is routed to a Service Engine by the Service Router.

The FLV file has been preingested on the SEs. The video begins to play.

Figure 48 Adobe Flash Player

Step 3 To view the Flash Media Streaming statistics, enter the show statistics flash-media-streaming command on the SEs.

There is one concurrent connection on NE-DEMO-SE2, which means there is an active connection to this SE. The statistics also shows a Preposition Hit of 1, which means there was preingested content being requested through this SE.

NE-DEMO-SE2# show statistics flash-media-streamingFlash Media Streaming StatisticsStatistics were last cleared on Thursday. 06-Dec-2007 37:22:58 UTC.

Connections-----------Current Connections Total : 1VOD : 1LIVE : 0DVRCast : 0Proxy : 0Max Concurrent : 1Total Connections Total : 1VOD : 1LIVE : 0DVRCast : 0Proxy : 0

48

VOD Streaming-----Current Connections : 1Total Connections : 1DownStream Bytes : 880668UpStream Bytes : 0DownStream BW : 0 KbpsPreposition Hit : 1External Hit : 0Cache Hit : 0Cache Miss : 0Proxy Case : 0Cache Hit Percentage : 0.00Local Disk Reads : 3HTTP Based Reads : 0Bytes From Local Disk: 880668Bytes Through HTTP : 0Ignore Query String : 0

Live Streaming-----Current Connections : 0Total Connections : 0UpStream BW : 0 KbpsDownStream BW : 0 KbpsUpStream Bytes : 0DownStream Bytes : 0Downstream CDS-IS total conn.: 0Ignore Query String : 0

DVRCast Streaming-----Current Connections : 0Total Connections : 0UpStream BW : 0 KbpsDownStream BW : 0 KbpsUpStream Bytes : 0DownStream Bytes : 0Ignore Query String : 0

Proxy Streaming -----Current Connections : 0Total Connections : 0UpStream BW : 0 KbpsDownStream BW : 0 KbpsUpStream Bytes : 0DownStream Bytes : 0

Rules-----------Action Allow : 0Action Block : 0Validate url Sign : 0URL Signing errors: Invalid Client : 0 Invalid Signature : 0 No signing : 0 Expired URL : 0Auth server validation: Auth Server Allow : 0 Auth Server Deny : 0

SWF Verification : ---------------------Requests

49

Performed : 0 Failed : 0 Successful : 0 Bypassed : 0 Memory Hash Hit : 0 Memory Hash Calculated: 0 Local SWF Hit : 0 Preposition SWF : 0 SWF Cache Hit : 0 SWF Cache Miss : 0 SWF Proxy : 0Errors SWF Fetch Error : 0 Local SWF Read Error : 0 Cached SWF Read Error : 0 SWF File not found : 0 SWF Incorrect Depth : 0 SWF Hash Match Fail : 0 SWF Hash Partial : 0 Edge SWF Cache Miss : 0 SWF Response Timeout : 0 SWF Client Unsupported: 0 SWF Wrong Version : 0

Error-----Disk Error File Open Error : 0 File Read Error : 0 File GetAttributes Error : 0 File Close Error : 0

HTTP Error Invalid Error : 0 Server Error : 0 Media Not Found : 0 Media Unauthorize : 0 Invalid Request : 0 Bad Gateway : 0 Service Unavailable : 0 Gateway Timeout : 0 Request Failed : 0 Invalid Response : 0 Too many Redirect : 0 Invalid Redirect : 0 Invalid Cache Type : 0

Server-----------Total UpStream BW : 0 KbpsTotal DownStream BW : 0 KbpsTotal UpStream Bytes : 0Total DownStream Bytes : 880668Total Server Bytes : 880668

Performance-----------Server Up Time : 816 SMem Usage : 5 %Max Mem Usage : 5 %Total Messages Dropped: 0

Num of Active VOD Instances : 1Num of Active Live Instances : 0Num of Active DVRCast Instances : 0

Flash Video Cache Statistics

50

-----------Hits : 0 Misses : 0 Released : 0 Bytes in cache : 0 Bytes in use : 0 Disk Usage : 4096

Verifying Flash Media Streaming Dynamically Ingested Content

Note Verifying dynamically ingested content for Flash Media Streaming includes cache miss scenarios and live streaming scenarios. Flash Media Streaming uses RTMP to stream live content by means of dynamic proxy. Configuration of live or rebroadcast programs is not required. When the first client requests live streaming content, the stream is created.

Step 1 SSH to NE-DEMO-SE1 and use the show cache content command to verify there is no cached content.

NE-DEMO-SE2# show cache contentMax-cached-entries is set as 20000000Number of cal cached assets: 0Eviction protection is disabled.Cache eviction-preferred-size configured is large--------------------------------------------------Size URL--------------------------------------------------

Step 2 On the client PC, start the Adobe Flash Player.

Step 3 Enter the URL of the flash file in the text box (Figure 49) and click Go. In the example, this is “rtmp://rfqdn.cds.com/vod/test_cache.flv.”

The RTMP call is routed to a Service Engine by the Service Router.

The FLV file has been cached on the SEs. The video begins to play.

Figure 49 Adobe Flash Player

Step 4 To view the Flash Media Streaming statistics, enter the show statistics flash-media-streaming command on the SEs.

There is one concurrent connection on NE-DEMO-SE2, which means there is an active connection to this SE. The statistics also shows a Cache Miss of 1, which means the content was not found on this SE.


51


VOD Streaming-----Current Connections : 1Total Connections : 1DownStream Bytes : 0UpStream Bytes : 0DownStream BW : 0 KbpsPreposition Hit : 0External Hit : 0Cache Hit : 0Cache Miss : 1Proxy Case : 0Cache Hit Percentage : 0.00Local Disk Reads : 2HTTP Based Reads : 1Bytes From Local Disk: 587112Bytes Through HTTP : 293556Ignore Query String : 0

Live Streaming-----Current Connections : 0Total Connections : 0UpStream BW : 0 KbpsDownStream BW : 0 KbpsUpStream Bytes : 0DownStream Bytes : 0Downstream CDS-IS total conn.: 0Ignore Query String : 0

DVRCast Streaming-----Current Connections : 0Total Connections : 0UpStream BW : 0 KbpsDownStream BW : 0 KbpsUpStream Bytes : 0DownStream Bytes : 0Ignore Query String : 0

Proxy Streaming -----Current Connections : 0Total Connections : 0UpStream BW : 0 KbpsDownStream BW : 0 KbpsUpStream Bytes : 0DownStream Bytes : 0

Rules

52

-----------Action Allow : 0Action Block : 0Validate url Sign : 0URL Signing errors: Invalid Client : 0 Invalid Signature : 0 No signing : 0 Expired URL : 0Auth server validation: Auth Server Allow : 0 Auth Server Deny : 0

SWF Verification : ---------------------Requests Performed : 0 Failed : 0 Successful : 0 Bypassed : 0 Memory Hash Hit : 0 Memory Hash Calculated: 0 Local SWF Hit : 0 Preposition SWF : 0 SWF Cache Hit : 0 SWF Cache Miss : 0 SWF Proxy : 0Errors SWF Fetch Error : 0 Local SWF Read Error : 0 Cached SWF Read Error : 0 SWF File not found : 0 SWF Incorrect Depth : 0 SWF Hash Match Fail : 0 SWF Hash Partial : 0 Edge SWF Cache Miss : 0 SWF Response Timeout : 0 SWF Client Unsupported: 0 SWF Wrong Version : 0

Error-----Disk Error File Open Error : 0 File Read Error : 0 File GetAttributes Error : 0 File Close Error : 0

HTTP Error Invalid Error : 0 Server Error : 0 Media Not Found : 0 Media Unauthorize : 0 Invalid Request : 0 Bad Gateway : 0 Service Unavailable : 0 Gateway Timeout : 0 Request Failed : 0 Invalid Response : 0 Too many Redirect : 0 Invalid Redirect : 0 Invalid Cache Type : 0

Server-----------Total UpStream BW : 0 KbpsTotal DownStream BW : 0 Kbps

53

Total UpStream Bytes : 0Total DownStream Bytes : 587112Total Server Bytes : 587112

Performance-----------Server Up Time : 933 SMem Usage : 5 %Max Mem Usage : 5 %Total Messages Dropped: 0

Num of Active VOD Instances : 1Num of Active Live Instances : 0Num of Active DVRCast Instances : 0

Flash Video Cache Statistics-----------Hits : 0 Misses : 0 Released : 0 Bytes in cache : 0 Bytes in use : 0 Disk Usage : 4096

Step 5 To verify that the content has been cached after it was requested, enter the show cache content command.

NE-DEMO-SE2# show cache contentMax-cached-entries is set as 20000000Number of cal cached assets: 1Eviction protection is disabled.Cache eviction-preferred-size configured is large--------------------------------------------------Size URL--------------------------------------------------293556 http://ofqdn.cds.com/vod/test_cache.flv

Verifying Flash Media Streaming—Live StreamingFlash Media Streaming uses RTMP to stream live content by means of dynamic proxy. Configuration of live or rebroadcast programs is not required. When the first client requests live streaming content, the stream is created. There are no limits to the number of live streams other than the system load. Live streaming uses distributed content routing to distribute streams across multiple Service Engines.

Step 1 Set up a Flash Media encoder. Enter the following information:

• FMS URL—Origin Server URL (Origin Server cannot be a CDS device.)

• Stream—Stream name for the client’s request

• Video—Choose VP6 or H.264

Step 2 Click Start to publish the stream to the Origin Server.

Step 3 In a web browser on the client PC, enter the URL rtmp://<edge SE IP address>/live/<publish stream name>.

For example, if the URL was rtmp://Temp4.se.fmslive.com/live/livestream, Temp4 is the SE assigned under the delivery service, the live directory indicates that it is a live stream, and livestream is the published name on the Flash Media Encoder.

Step 4 On the Edge SE enter the show statistics flash-media-streaming command to view the Flash Media Streaming statistics.



...Omitted contents

Live Streaming-----Current Connections : 1Total Connections : 1UpStream BW : 0 KbpsDownStream BW : 274 KbpsUpStream Bytes : 3194DownStream Bytes : 124362967Downstream CDS-IS total conn.: 1

...Omitted contents

Step 5 Enter the show flash-media-streaming stream-status live command.

NE-DEMO-SE2# show flash-media-streaming stream-status liveDisplay flash-media-streaming livestreams

Display maximum 4 applications, 8 forwarders, and 8 client stream info

Forwarder---------OsUrl : rtmp://Temp4.se.fmslive.com/live/livestreampath2OS : 2.225.2.65->2.225.2.62reqFwdUrl : rtmp://2.225.2.65/live/cds_fms_proxy/2.225.2.62/live/livestreamUpstream BW (Kbps) : 0Downstream BW (Kbps): 267Upstream Bytes : 3487Downstream Bytes : 138278573numClient : 1

...Omitted contents

Step 6 On the Content Acquirer in the delivery service, enter the show statistics flash-media-streaming command. The command shows one session connecting from the edge SE.


Current Connections Total : 1VOD : 0LIVE : 1DVRCast : 0Proxy : 0Max Concurrent : 1Total Connections Total : 1VOD : 0LIVE : 0

55

DVRCast : 0Proxy : 0

...Omitted contents

Live Streaming-----UpStream BW : 0 kbpsDownStream BW : 274 kbpsUpStream Bytes : 3487DownStream Bytes : 149456451Num of Instance Load : 1

...Omitted contents

Step 7 Enter the show flash-media-streaming stream-status live command. The command shows the client request URL connecting from the edge SE.

NE-DEMO-SE2# show flash-media-streaming stream-status liveDisplay flash-media-streaming livestreams

Display maximum 4 applications, 8 forwarders, and 8 client stream infoForwarder---------OsUrl : rtmp://2.225.2.65/live/cds_fms_proxy/2.225.2.62/live/livestreampath2OS : 2.225.2.62reqFwdUrl : rtmp://2.225.2.62/live/livestreamUpstream BW (Kbps) : 0Downstream BW (Kbps): 261Upstream Bytes : 3337Downstream Bytes : 155736798numClient : 1

...Omitted contents

9 Related PublicationsThese documents provide complete information about the CDS and are available from the Cisco.com site:

• Cisco Internet Streamer CDS 3.1 Software Configuration Guide

• Cisco Internet Streamer CDS 3.1 Command Reference

• Cisco Internet Streamer CDS 3.1 Alarms and Error Messages Guide

• Release Notes for Cisco Internet Streamer CDS 3.1

• Cisco Internet Streamer CDS 3.0-3.1 Software Installation Guide for non-CDEs

• Cisco Content Delivery Engine 205/220/250/420 Hardware Installation Guide

• Cisco Content Delivery System 3.x Documentation Roadmap

• Regulatory Compliance and Safety Information for Cisco Content Delivery Engines

• Open Sources Used in CDS IS Release 3.0

You can access the software documents at the following URL:

http://www.cisco.com/en/US/products/ps7127/tsd_products_support_series_home.html

You can access the hardware documents for the CDEs at the following URL:




Printed in the USA on recycled paper containing 10% postconsumer waste.

OL-27069-02

Americas HeadquartersCisco Systems, Inc.San Jose, CA

Asia Pacific HeadquartersCisco Systems (USA) Pte. Ltd.Singapore

Europe HeadquartersCisco Systems International BV Amsterdam, The Netherlands

Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco Website at www.cisco.com/go/offices.

You can access the hardware documents for non-CDEs at the following URLs:

• Cisco UCS C200 Installation and Service Guide

http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C200M1/install/c200M1.html

• Cisco UCS C210 Installation and Service Guide

http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C210M1/install/C210M1.html

10 Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C200M1/install/c200M1.html

http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C210M1/install/C210M1.html

Date post:	07-Aug-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

Cisco Internet Streamer CDS 3.0–3€¦ · 7 Enabling and Verifying the Movie Streamer Engine 8...

Documents