Guest

Cisco Media Delivery Engine 1100

Cisco ECDS 2.5 Quick Start Guide

  • Viewing Options

  • PDF (1.1 MB)
  • Feedback
Quick Start Guide

Table Of Contents

Cisco ECDS 2.5

Introduction

ECDS Network Topology

Getting Started

Network Setup

Accessing the Device Using the Command-Line Interface

Configuring the Devices

Activating the Devices in the Enterprise Content Delivery System

Configuring the Domain Name System Server

Configuring Delivery Services

Creating a Content Origin

Defining a Delivery Service

Configuring the Service Router

Assigning a Coverage Zone File

Verifying the Web Engine

Verifying Preingested Web Content

Verifying Dynamically Ingested Web Content

Verifying the Windows Media Streaming Engine

Verifying Preingested Windows Media Content

Verifying Dynamically Ingested Windows Media Content

Managing Windows Media Live Programs

Creating a Live Windows Media Delivery Service

Configuring a Windows Media Live Program

Verifying Windows Media Live Content Playback

Enabling and Verifying the Movie Streamer Engine

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

Creating a Live Movie Streamer Delivery Service

Configuring a Movie Streamer Live Program

Verifying Movie Streamer Live Content Playback

Enabling and Verifying the Flash Media Streaming Engine

Enabling Flash Media Streaming

Verifying Flash Media Streaming Preingested Content

Verifying Flash Media Streaming Dynamically Ingested Content

Verifying Flash Media Streaming—Live Streaming

Related Publications

Obtaining Documentation and Submitting a Service Request


Quick Start Guide

Cisco ECDS 2.5


1 Introduction

This guide helps you quickly configure the Enterprise Content Delivery System (ECDS) and its components, the Media Delivery Engines (MDEs). This guide assumes the following steps have already been performed:

1. All MDEs have been rack installed.

2. All cable and power connections are completed.

3. ECDS software has been installed on each MDE.

For more information about installing the MDEs, see the Cisco MDE hardware installation guide for your model of MDE. For more information about configuring ECDS, see the Cisco Enterprise CDS 2.5 Software Configuration Guide.

See the "Related Publications" section for the links to all Cisco ECDS and MDE documentation.

ECDS Network Topology

This guide uses the ECDS network illustrated in Figure 1 to describe the configuration steps. The specific topology, hostnames, and device IP addresses for your network will vary. This network example consists of the following components:

2 MDEs configured as Service Engines (SEs)

NE-DEMO-SE1 — Tier 1 location (MDE 3100)

NE-DEMO-SE2 — Tier 2 location (MDE 1100)

1 MDE 1100 configured as a Service Router (SR)

NE-DEMO-SR — Tier 2 location

1 MDE 1100 configured as an Enterprise Content Delivery System Manager (ECDSM)

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

Figure 1 ECDS Topology Example

2 Getting Started

This section consists of the following procedures:

Network Setup

Accessing the Device Using the Command-Line Interface

Configuring the Devices

Activating the Devices in the Enterprise Content Delivery System

Configuring the Domain Name System Server

Network Setup

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

Device
Mode
Hostname
Primary IP Address

MDE 1100

ECDSM

NE-DEMO-CDSM

10.1.4.31/24

MDE 1100

SR

NE-DEMO-SR

10.1.4.13/24

MDE 3100

SE

NE-DEMO-SE1

10.1.4.10/24

MDE 1100

SE

NE-DEMO-SE2

10.1.4.14/24


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

To access the device, you must have configured the following during the hardware setup:

Configured an IP address on the device management (CIMC) interface

Enabled Serial over LAN at 9600 bps in the Cisco Integrated Management Controller (CIMC) (CIMC > Remote Presence > Serial over LAN)

To connect to the command line interface of the server, do the following:


Step 1 Open an SSH session to the device management interface, for example:

ssh -l admin ip_address
 
   

Step 2 At the command prompt, enter connect host.


Configuring the Devices

Use the Setup utility to configure the device mode and network setting for each MDE.


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

This procedure configures a single interface on the MDE 1100 Service Engines for both ECDS management and streaming traffic. You can later change this configuration to port channel the GigabitEthernet 1/0 and GigabitEthernet 2/0 interfaces to provide greater bandwidth or as two separate interfaces to provide a separate management network interface. See the Cisco Enterprise CDS 2.5 Software Configuration Guide for more information.

The MDE 3100 in this example uses GigabitEthernet 3/0 through GigabitEthernet 6/0 in a port channel (EtherChannel) configuration for the streaming interface.

Configuring DHCP on the interfaces is not supported in this release.



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

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

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

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

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

MDE# setup
What is the mode of the device (SE/SR/CDSM): SE
Is this SE going to be managed by a
CDSM (Content Delivery System Manager) (y/n) [y]: y
Please choose an interface to configure from the following list:
1: GigabitEthernet 1/0
2: GigabitEthernet 2/0
3: GigabitEthernet 3/0
4: GigabitEthernet 4/0
5: GigabitEthernet 5/0
6: GigabitEthernet 6/0
Enter choice: 1
Do you want to enable DHCP on this interface (y/n) [n]: n
Please enter the IP address of this interface: 10.1.4.10
Please enter the netmask of this interface: 255.255.255.0
Please enter the default gateway: 10.1.4.1
Please enter the domain name server ip: 171.69.2.133
Please enter the domain name: spcdn.com
Please enter the hostname: NE-DEMO-SE1
Please enter CDSM (Content Delivery System Manager) IP or Host name: 10.1.4.31
Do you want to apply the configurations (y/n) [y]: y
This may take few moments. Please wait..
All CLI configurations were applied successfully.
Press any key to continue..
 
   
NE-DEMO-SE1# configure terminal
NE-DEMO-SE1(config)# interface PortChannel 1
NE-DEMO-SE1(config-if)# ip address 10.1.4.11 255.255.255.0
NE-DEMO-SE1(config-if)# exit
NE-DEMO-SE1(config)# interface GigabitEthernet 3/0
NE-DEMO-SE1(config-if)# channel-group 1
NE-DEMO-SE1(config-if)# exit
NE-DEMO-SE1(config)# interface GigabitEthernet 4/0
NE-DEMO-SE1(config-if)# channel-group 1
NE-DEMO-SE1(config-if)# exit
NE-DEMO-SE1(config)# interface GigabitEthernet 5/0
NE-DEMO-SE1(config-if)# channel-group 1
NE-DEMO-SE1(config-if)# exit
NE-DEMO-SE1(config)# interface GigabitEthernet 6/0
NE-DEMO-SE1(config-if)# channel-group 1
NE-DEMO-SE1(config-if)# exit
NE-DEMO-SE1#(config) streaming-interface PortChannel 1
 
   

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

MDE# setup
What is the mode of the device (SE/SR/CDSM): SE
Is this SE going to be managed by a
CDSM (Content Delivery System Manager) (y/n) [y]: y
Please choose an interface to configure from the following list:
1: GigabitEthernet 1/0
2: GigabitEthernet 2/0
Enter choice: 1
Do you want to enable DHCP on this interface (y/n) [n]: n
Please enter the IP address of this interface: 10.1.4.14
Please enter the netmask of this interface: 255.255.255.0
Please enter the default gateway: 10.1.4.1
Please enter the domain name server ip: 171.69.2.133
Please enter the domain name: spcdn.com
Please enter the hostname: NE-DEMO-SE2
Please enter CDSM (Content Delivery System Manager) IP or Host name: 10.1.4.31
Do you want to apply the configurations (y/n) [y]: y
This may take few moments. Please wait..
All CLI configurations were applied successfully.
Press any key to continue..
 
   
NE-DEMO-SE2# configure terminal
NE-DEMO-SE2# streaming-interface GigabitEthernet 1/0
 
   

Activating the Devices in the Enterprise Content Delivery System

Verify connectivity to the ECDSM.


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

The Security Alert message is displayed.


Note If you are using Mozilla Firefox version 3.01 or higher as your web browser, you need to add the ECDSM IP address to the exception list. After entering the ECDSM 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. In the Add Security Exception dialog box, click Get Certificate. and then click Confirm Security Exception. The ECDSM IP address has been added to the exception list and you will no longer get the Secure Connection Failed message.


The ECDSM Login page is displayed (Figure 2).

Figure 2 Enterprise CDSM Login Page

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

Step 3 From the ECDSM 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." (NOTE: the IP addresses in Figure 3 differ from the current example).

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).

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

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."


Configuring the Domain Name System Server

The 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.


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 10.1.4.10
NE-DEMO-SE2     IN A 10.1.4.14
NE-DEMO-SR      IN A 10.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";
 
   

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

[root@Lnxdns ~] # service named restart
 
   

3 Configuring Delivery Services

This section includes the following procedures:

Creating a Content Origin

Defining a Delivery Service

Creating a Content Origin


Step 1 From the ECDSM 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).

Figure 7 Content Origin Table Page


Defining a Delivery Service


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).

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." The field does not accept spaces.

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 Click Submit.

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 9 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 10 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 11 From the Assign Content Acquirer drop-down list, select NE-DEMO-SE1 to be the Content Acquirer.

Step 12 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 13 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:

NE-DEMO-SE1# show statistics acquirer
 
   
Statistics for delivery -service-id : 275	delivery-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 2007
Size          :   19999380 Bytes
Url           :   http://ofqdn.cds.com/test_prepos/test.wmv
 
   
Modification Time	: Thu Oct 25 01:04:16 2007
Size          :   1425570 Bytes
Ur            :   http://ofqdn.cds.com/test_prepos/test.mov
 
   
Modification Time	: Thu Oct 25 01:04:16 2007
Size           :  44 Bytes
Url            :  http://ofqdn.cds.com/test_prepos/test.html
 
   
Modification Time  : Thu Oct 25 01:04:16 2007
Size           :  283556 Bytes
Url            :  http://ofqdn.cds.com/vod/test_prepos.flv
 
   

Step 14 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 15 On the ECDSM home page, from the Delivery Service left-panel menu, choose Replication Status. The ECDSM 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 Router

This section includes the procedure for assigning a Coverage Zone file. The Service Router was activated in the "Activating the Devices in the Enterprise Content Delivery System" section.

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 the Cisco Enterprise CDS 2.5 Software Configuration Guide. See the "Related Publications" section for links to the online documentation on Cisco.com.



Step 1 From the ECDSM 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).

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 6 Click Submit.

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

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

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 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)
170.50.20.0/24 5 NE-DEMO-SE1 (Operational, Static)
10.1.4.0/24 20 NE-DEMO-SE1 (Operational, Static)
10.1.4.0/24 20 NE-DEMO-SE2 (Operational, Static)
 
   
---- Best network routes to Content Origin ----
domain: rfqdn.cis.com (Origin Server: ofqdn.cds.com)
171.71.0.0/16 5 NE-DEMO-SE2
171.70.0.0/16 5 NE-DEMO-SE2
170.50.20.0/24 20 NE-DEMO-SE1
10.1.4.0/24 20 NE-DEMO-SE1
10.1.4.0/24 20 NE-DEMO-SE2
 
   

5 Verifying the Web Engine

This 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. 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

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 http requests command. In this case, the Service Router redirected the request to NE-DEMO-SE2, which served the request.

NE-DEMO-SE1# show statistics http requests
 
   
    Caching Statistics
    ------------------
            Cache Hits :  0
            Cache Miss :  0
        Range Requests :  0
Partial HIts - Live fill : 0
    Partial HIt - Refill : 0
Partial Caching - Bypassed : 0
 
   
Prepositioned Content Statistics
--------------------------------
       Preposition Hits :  0
             Reply Meta :  0
         Alternate Media : 0
 
   
    Others
    ------
            Num Lookups : 0
           Lookup Errors :0
Streaming redirected requests : 0
        WMT Liveness requests : 0
Hierarchical Cache Liveness requests : 0
 
   
                    Total      % of requests
                    -----      -------------
             Client Errors :    0   0.00
             Server Errors :    0   0.00
         Http/0.9 Requests :    0   0.00
         Http/1.0 Requests :    0   0.00
         Http/1.1 Requests :    0   0.00
     Http Invalid Requests :    0   0.00
                   Blocked :    0   0.00
                   Allowed :    0   0.00
 
   
NE-DEMO-SE2# show statistics http request
 
   
Caching Statistics
------------------
            Cache Hits :   0
            Cache Miss :   0
        Range Requests :   0
Partial HIts - Live fill : 0
    Partial HIt - Refill : 0
Partial Caching - Bypassed : 0
 
   
Prepositioned Content Statistics
--------------------------------
       Preposition Hits : 1
            Reply Meta  : 0
        Alternate Media : 0
 
   
    Others
    ------
             Num Lookups : 1
            Lookup Errors :0
Streaming redirected requests : 0
         WMT Liveness requests :0
Hierarchical Cache Liveness requests : 0
 
   
                    Total      % of requests
                    -----      -------------
             Client Errors :    0   0.00
             Server Errors :    0   0.00
         Http/0.9 Requests :    0   0.00
         Http/1.0 Requests :    0   0.00
         Http/1.1 Requests :    0 100.00
     Http Invalid Requests :    0   0.00
                   Blocked :    0   0.00
                   Allowed :    0 100.00
 
   

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 http requests command.

NE-DEMO-SE1# show statistics http requests
 
   
Caching Statistics
------------------
            Cache Hits :  0
            Cache Miss :  1
        Range Requests :  0
Partial HIts - Live fill : 0
    Partial HIt - Refill : 0
Partial Caching - Bypassed : 0
 
   
Prepositioned Content Statistics
--------------------------------
    Preposition Hits :  0
          Reply Meta :  0
     Alternate Media :  0
        Others
        ------
  Num Lookups : 1
Lookup Errors :  0
Streaming redirected requests : 0
WMT Liveness requests :0
Hierarchical Cache Liveness requests : 1
 
   
                 Total    % of requests
                 -----    --------------
 Client Errors :     0     0.00
 Server Errors :     0     0.00
Http/0.9 Requests :  0     0.00
Http/1.0 Requests :  0     0.00
Http/1.1 Requests :  2   100.00
Http Invalid Requests :0   0.00
        Blocked :    0     0.00
        Allowed :    2   100.00
 
   
NE-DEMO-SE2# show statistics http requests
 
   
Caching Statistics
------------------
   Cache Hits : 0
   Cache Miss : 1
Range Requests : 0
Partial HIts - Live fill :0
Partial HIt - Refill : 0
Partial Caching - Bypassed : 0
 
   
Prepositioned Content Statistics
--------------------------------
   Preposition Hits : 0
         Reply Meta : 0
    Alternate Media : 0
 
   
        Others
        ------
  Num Lookups :1
Lookup Errors :0
Streaming redirected requests : 0
WMT Liveness requests :0
Hierarchical Cache Liveness requests : 0
 
   
                 Total   % of requests
                 -----   -------------
Client Errors :     0     0.00
Server Errors :     0     0.00
Http/0.9 Requests : 0     0.00
Http/1.0 Requests : 0     0.00
Http/1.1 Requests : 1   100.00
Http Invalid Requests :0  0.00
        Blocked :   0     0.00
        Allowed :   1   100.00
 
   

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 content
Max-cached-entries is set as 3000000
Number of cal cached assets: 1
------------------------------------------------
Priority   Size    URL
------------------------------------------------
5.41532e-01 44    http://ofqdn.cds.com/test_cache/test.html
 
   
NE-DEMO-SE2#show cache content
Max-cached-entries is set as 3000000
Number of cal cached assets: 1
------------------------------------------------
Priority    Size   URL
------------------------------------------------
6.20339e-01 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 http requests command.

NE-DEMO-SE1# show statistics http requests
 
   
Caching Statistics
------------------
            Cache Hits :  0
            Cache Miss :  1
        Range Requests :  0
Partial HIts - Live fill : 0
    Partial HIt - Refill : 0
Partial Caching - Bypassed : 0
 
   
Prepositioned Content Statistics
--------------------------------
    Preposition Hits :  0
          Reply Meta :  0
     Alternate Media :  0
        Others
        ------
  Num Lookups : 1
Lookup Errors :  0
Streaming redirected requests : 0
WMT Liveness requests :0
Hierarchical Cache Liveness requests : 1
 
   
                 Total    % of requests
                 -----    --------------
 Client Errors :     0     0.00
 Server Errors :     0     0.00
Http/0.9 Requests :  0     0.00
Http/1.0 Requests :  0     0.00
Http/1.1 Requests :  2   100.00
Http Invalid Requests :0   0.00
        Blocked :    0     0.00
        Allowed :    2   100.00
 
   
NE-DEMO-SE2# show statistics http requests
 
   
 
   
Caching Statistics
------------------
    Cache Hits : 1
    Cache Miss : 1
Range Requests : 0
Partial HIts - Live fill :0
Partial HIt - Refill : 0
Partial Caching - Bypassed : 0
 
   
Prepositioned Content Statistics
--------------------------------
   Preposition Hits :  0
         Reply Meta :  0
    Alternate Media :  0
        Others
        ------
  Num Lookups : 2
Lookup Errors :  0
Streaming redirected requests : 0
WMT Liveness requests :0
Hierarchical Cache Liveness requests : 0
 
   
                 Total    % of requests
                 -----    --------------
 Client Errors :     0     0.00
 Server Errors :     0     0.00
Http/0.9 Requests :  0     0.00
Http/1.0 Requests :  0     0.00
Http/1.1 Requests :  2   100.00
Http Invalid Requests :0   0.00
        Blocked :    0     0.00
        Allowed :    2   100.00
 
   

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 Engine

This 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


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



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).

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 streamstat
Detailed Stream Statistics
=====================================
 
   
Incoming Streams:
=================
Stream-Id  Type  Source State  Bytes-Recd   Duration   Bandwidth  Server-IP  Url-Requested
 
   
Outgoing Streams:
=================
Client-IP  Type  Transport Source  State Pkts-set  Bytes-sent  Duration  BW Filename Stream-id
 
   
NE-DEMO-SE2# show statistics wmt streamstat
Detailed Stream Statistics
=====================================
 
   
Incoming Streams:
=================
Stream-Id  Type  Source State  Bytes-Recd   Duration   Bandwidth  Server-IP  Url-Requested
 
   
Outgoing Streams:
=================
Client-IP     Type  Transport Source  State Pkts-set  Bytes-sent  Duration  BW Filename          Stream-id
171.70.222.171 VOD  NONE      LOCAL   Setup  0        0           0         0  test_prepos/test.wmv   8895
 
   

Verifying Dynamically Ingested 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 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."

Figure 22 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 23).

Figure 23 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# clear statistics wmt
NE-DEMO-SE1# show statistics wmt streamstat
Detailed Stream Statistics
=====================================
 
   
Incoming Streams:
=================
Stream-Id  Type  Source State  Bytes-Recd   Duration   Bandwidth  Server-IP  Url-Requested
 
   
Outgoing Streams:
=================
Client-IP   Type  Transport Source  State Pkts-set  Bytes-sent  Duration  BW Filename            Stream-id
10.1.4.14    VOD   RTSPT    RMT_HTTP Play  388       3104000     19        549 test_cache/test.wmv  27521
 
   
NE-DEMO-SE2# clear statistics wmt
NE-DEMO-SE2# show statistics wmt streamstat
Detailed Stream Statistics
=====================================
 
   
Incoming Streams:
=================
Stream-Id  Type  Source    State  Bytes-Recd   Duration   Bandwidth  Server-IP  Url-Requested
12079      VOD   RMT_RTSP Play   2241074     23         1550       10.1.4.10    rtsp;//ofqdn.cds.com/test_cache/test.wmv
 
   
Outgoing Streams:
=================
Client-IP       Type  Transport Source   State Pkts-set  Bytes-sent  Duration  BW Filename         Stream-id
171.70.222.171  VOD   RTSPT     RMT_RTSP Play  279       2232000     13      7201 test_cache/test.wmv  12043
 
   

Managing Windows Media Live Programs

Each 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

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

Figure 25 Create Delivery Service 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.

Step 4 Check the Live Delivery Service check box.

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

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).

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 8 From the Assign Content Acquirer drop-down list, select NE-DEMO-SE1 to be the Content Acquirer.

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

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/).

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 13 Click Submit.

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

Step 15 Click the Play Forever radio button.

Step 16 Click Submit.


Verifying Windows Media Live Content Playback


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

Step 2 Choose File > Open URL.

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."

Figure 30 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 31).

Figure 31 Windows Media Player Statistics

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.

NE-DEMO-SE1# show statistics wmt streamstat
Detailed Stream Statistics
=====================================
 
   
Incoming Streams:
=================
Stream-Id  Type  Source    State  Bytes-Recd Duration  Bandwidth  Server-IP  Url-Requested
18872      LIVE  RMT_HTTP  Play   84150      241       288     171.70.22.171  http://171.70.222.171:0000
 
   
Outgoing Streams:
=================
Client-IP  Type  Transport Source   State Pkts-set  Bytes-sent  Duration  BW Filename  Stream-id
10.1.4.14   LIVE  RTSPT     RMT_HTTP  Play 5393      7787492     233      288 8080      18889
 
   
NE-DEMO-SE2# show statistics wmt streamstat
Detailed Stream Statistics
=====================================
 
   
Incoming Streams:
=================
Stream-Id  Type  Source    State  Bytes-Recd Duration  Bandwidth  Server-IP  Url-Requested
28772      LIVE  RMT_RTSP Play   8205265   246       289        10.1.4.10   
rtsp;//10.1.4.10/wmt_proxy/rtsp&ofqdn.cds.com/wmtlive/__CDS/http&171.70.111.171&8080
 
   
Outgoing Streams:
=================
Client-IP       Type  Transport Source   State Pkts-set  Bytes-sent  Duration  BW  Filename  Stream-id
171.70.222.171  LIVE  RTSPU     RMT_RTSP  Play  5582     8060408     241       288 wmtlive   28755
 
   

7 Enabling and Verifying the Movie Streamer Engine

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 ECDSM home page, choose Devices > Devices. The Devices Table page is displayed (Figure 32).

Figure 32 Devices Table Page

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

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

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 Ingest

The 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).

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


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



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

Step 2 Choose File > Open URL.

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."

Figure 36 Open URL Dialog Box

The video begins to play.

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, enter the show statistics movie-streamer all command.

NE_DEMO-SE2# show statistics movie-streamer all
Movie Streamer Request Statistics
                                     Total
    ---------------------------------------
Current RTSP sessions:                    0
  Total RTSP sessions:                    1
   Current RIP 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 bps
Current Outgoing bandwidth;                 0 bps
   Current Total bandwidth:                 0 bps
 
   
Average Incoming bandwidth:                 0 bps
Average Outgoing bandwidth:                 0 bps
  Average Total bandwidth:                  0 bps
 
   
    By Type of Connection
                ---------
Unicast Incoming Bandwidth:                     0 bps
  Multicast Incoming Bandwidth:                 0 bps
Unicast Outgoing Bandwidth:                     0 bps
  Multicast Outgoing Bandwidth:                 0 bps
 
   
        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:                           0
Not Enough Bandwidth:                           0
    Client Forbidden:                           0
              Others:                           0
 
   
Movie Streamer Performance Statistics
                                   Total
-----------------------------------------
        CPU Usage:                      0.000000 %
           UpTime:                      5416 sec
Statistics 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 all
Movie Streamer Request Statistics
                                 Total
---------------------------------------
Current RTSP sessions:                1
  Total RTSP sessions:                2
Current RIP connections:              1
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 bps
Current Outgoing bandwidth:            0 bps
   Current Total bandwidth:            0 bps
 
   
Average Incoming bandwidth:            0 bps
Average Outgoing bandwidth:       863879 bps
  Average Total bandwidth:        863879 bps
 
   
          Incoming Bytes:                   0 Bytes
          Outgoing Bytes:            14490660 Bytes
             Total Bytes:            14490660 Bytes
 
   

Verifying Dynamically Ingested Movie Streamer Content

When content requested by a client is not in the ECDS, it is dynamically ingested from the original source and streamed to the client by an SE.


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

Step 2 Choose File > Open URL.

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

Figure 38 Open URL Dialog Box

The video begins to play.

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 all
Movie Streamer Request Statistics
                                 Total
---------------------------------------
  Current RTSP sessions:              1
Current RIP connections:              1
  Total RTP connections:              4
 
   
Movie Streamer Bandwidth Usage Statistics
                                   Total
-----------------------------------------
Current Incoming bandwidth:        207115 bps
Current Outgoing bandwidth:             0 bps
   Current Total bandwidth:        207115 bps
 
   
Average Incoming bandwidth:        199244 bps
Average Outgoing bandwidth:        207932 bps
  Average Total bandwidth:         407176 bps
 
   
           Incoming Bytes:        12667891 Bytes
           Outgoing Bytes:        12609164 Bytes
              Total Bytes:        25277055 Bytes
 
   
NE_DEMO-SE2# show statistics movie-streamer all
Movie Streamer Request Statistics
                                 Total
---------------------------------------
  Current RTSP sessions:               0
Current RIP connections:               0
  Total RTP connections:               3
 
   
Movie Streamer Bandwidth Usage Statistics
                                    Total
-----------------------------------------
Current Incoming bandwidth:         194974 bps
Current Outgoing bandwidth:              0 bps
   Current Total bandwidth:         194974 bps
 
   
Average Incoming bandwidth:         174557 bps
Average Outgoing bandwidth:              0 bps
  Average Total bandwidth:           74557 bps
 
   
          Incoming Bytes:         13283705 Bytes
          Outgoing Bytes:                0 Bytes
             Total Bytes:         13283705 Bytes
 
   

Managing Movie Streamer Live Content

The 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 ECDS; 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.

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

Figure 39 Create Delivery Service Page

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.

Step 5 Check the Live Delivery Service check box.

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

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."

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

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.

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.

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 14 Click Submit.

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

Step 16 Click the Play Forever radio button.

Step 17 Click Submit.


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

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

Step 2 Choose File > Open URL.

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."

Figure 45 Open URL Dialog Box

The video begins to play.

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.

Figure 46 QuickTime Player Statistics

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

NE_DEMO-SE1# show statistics movie-streamer all
Movie Streamer Request Statistics
                                  Total
---------------------------------------
  Current RTSP sessions:               1
Current RIP connections:               1
  Total RTP connections:               3
 
   
Movie Streamer Bandwidth Usage Statistics
                                    Total
-----------------------------------------
Current Incoming bandwidth:         161526 bps
Current Outgoing bandwidth:         582640 bps
   Current Total bandwidth:         744166 bps
 
   
Average Incoming bandwidth:          192102 bps
Average Outgoing bandwidth:          203980 bps
   Average Total bandwidth:          396082 bps
 
   
          Incoming Bytes:          4478769 Bytes
          Outgoing Bytes:          4499370 Bytes
             Total Bytes:          8978139 Bytes
 
   
NE_DEMO-SE2# show statistics movie-streamer all
Movie Streamer Request Statistics
                                 Total
---------------------------------------
  Current RTSP sessions:              0
Current RIP connections:              0
  Total RTP connections:              1
 
   
Movie Streamer Bandwidth Usage Statistics
                                    Total
-----------------------------------------
Current Incoming bandwidth:         175399 bps
Current Outgoing bandwidth:              0 bps
   Current Total bandwidth:         175399 bps
 
   
Average Incoming bandwidth:              0 bps
Average Outgoing bandwidth:              0 bps
  Average Total bandwidth:               0 bps
 
   
          Incoming Bytes:           1248165 Bytes
          Outgoing Bytes:           1080984 Bytes
            Total Bytes:            2329149 Bytes
 
   
Movie Streamer Performance Statistics
                                  Total
---------------------------------------
       CPU Usage:              0.000000 %
          UpTime:                 78375 sec
Statistics were last cleared on Friday, 26-Oct-2007 20:09:42 UTC.
 
   


Note For more information, see the "Configuring Services" chapter in the Cisco Enterprise CDS 2.5 Software Configuration Guide. See the "Related Publications" section for links to the online documentation on Cisco.com.


8 Enabling and Verifying the Flash Media Streaming Engine

This 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 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 livestreams 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-streaming
Flash Media Streaming is enabled.
Max. allowed concurrent sessions are 2000.
Max. allowed bandwidth is 3000000Kbps.
 
   

Step 2 If Flash Media Streaming is enabled, go to the "Verifying Flash Media Streaming Preingested Content" section. If Flash Media Streaming is not enabled, go to the next step.

Step 3 Launch a web browser, and log in to the ECDSM. For more information on logging in to the ECDSM, see the "Activating the Devices in the Enterprise Content Delivery System" section.

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

Figure 47 Devices Table Page

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

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

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.


Verifying Flash Media Streaming Preingested Content


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



Note All RTMP calls must be in the following format:
rtmp://rfqdn/vod/path/foo.flv
In this format, rfqdn is the routing domain name of the Service Router, 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-streaming
Flash Media Streaming Statistics
Statistics were last cleared on Thursday. 06-Dec-2007 37:22:58 UTC.
 
   
Connections
-----------
Current               :     1
Current VOD           :     1
Current LIVE          :     0
Current DVRCast       :     0
Max Concurrent        :     1
Total                 :     1
Total VOD Req         :     0
Total LIVE Req        :     0
Total DVRCast Req     :     0
Total Other Proxy Req :     0
 
   
Live Streaming
-----
UpStream BW          :      0 kbps
DownStream BW        :      0 kbps
UpStream Bytes       :      0
DownStream Bytes     :      0
Num of Instance Load :      0
 
   
DVRCast Streaming
-----
UpStream BW          :                    0 Kbps
DownStream BW        :                    0 Kbps
UpStream Bytes       :                    0
DownStream Bytes     :                    0
Num of Instance Load :                    0
 
   
Flash Video Cache Statistics
-----------
Hits                 :                    0
Misses               :                    0
Released             :                    0
Bytes in cache       :                    0
Bytes in use         :                    0
 
   
Performance
-----------
Server Up Time        :     816 S
Mem Usage             :     5 %
Max Mem Usage         :     5 %
 
   
Cache
-----
Cache Hit             :     0
Cache Miss            :     0
Proxy Case            :     0
Cache HIt Percentage  :     0.00 %
 
   
Preposition
-----------
Preposition Hit       :      1
 
   
Bytes Served
------------
Total Server Bytes    :  880668
Local Disk Reads      :       3
HTTP Based Reads      :       0
Bytes From Local Disk :  880668
Bytes Through HTTP    :       0
 
   
Rules
------------
Action Allow       :      0
Action Block       :      0
Validate url Sign  :      0
Errors             :      0
Auth Server Allow  :      0
Auth Server Deny   :      0
 
   
Error
-----
Invalid Error      :      0
Server Error       :      0
Media Not Found    :      0
Media Unauthorized :      0
Invalid Request    :      0
 
   

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 content
Max-cached-entries is set as 3000000
Number of cal cached assets: 0
--------------------------------------------------
Priority      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.

NE-DEMO-SE2# show statistics flash-media-streaming
Flash Media Streaming Statistics
Statistics were last cleared on Thursday. 06-Dec-2007 37:22:58 UTC.
 
   
Connections
-----------
Current        :        1
Current VOD    :        1
Current LIVE   :        0
Max Concurrent :        1
Total          :        1
Total VOD Req         :     0
Total LIVE Req        :     0
Total DVRCast Req     :     0
Total Other Proxy Req :     0
 
   
Live Streaming
-----
UpStream BW          :      0 kbps
DownStream BW        :      0 kbps
UpStream Bytes       :      0
DownStream Bytes     :      0
Num of Instance Load :      0
 
   
DVRCast Streaming
-----
UpStream BW          :                    0 Kbps
DownStream BW        :                    0 Kbps
UpStream Bytes       :                    0
DownStream Bytes     :                    0
Num of Instance Load :                    0
 
   
Flash Video Cache Statistics
-----------
Hits                 :                    0
Misses               :                    0
Released             :                    0
Bytes in cache       :                    0
Bytes in use         :                    0
 
   
Performance
-----------
Server Up Time  :      933 S
Mem Usage       :        5 %
Max Mem Usage   :        5 %
 
   
Cache
-----
Cache Hit       :           0
Cache Miss      :           1
Proxy Case      :           0
Cache HIt Percentage:   0.00 %
 
   
Preposition
-----------
Preposition Hit  :       0
 
   
Bytes Served
------------
Total Server Bytes:   :587112
Local Disk Reads    :       2
HTTP Based Reads    :       1
Bytes From Local Disk: 587112
Bytes Through HTTP:    293556
 
   
Rules
------------
Action Allow       :      0
Action Block       :      0
Validate url Sign  :      0
Errors             :      0
Auth Server Allow  :      0
Auth Server Deny   :      0
 
   
Error
-----
Invalid Error      :      0
Server Error       :      0
Media Not Found    :      0
Media Unauthorized :      0
Invalid Request    :      0
 
   

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 content
Max-cached-entries is set as 3000000
Number of cal cached assets: 1
--------------------------------------------------
Priority       Size              URL
--------------------------------------------------
1.71425e-01    293556            http://ofqdn.cds.com/vod/test_cache.flv
 
   

Verifying Flash Media Streaming—Live Streaming

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. 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 an ECDS 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.

NE-DEMO-SE2# show statistics flash-media-streaming
Flash Media Streaming Statistics
Statistics were last cleared on Thursday. 06-Dec-2007 37:22:58 UTC.
 
   
Connections
-----------
Current               :     1
Current VOD           :     0
Current LIVE          :     1
Max Concurrent        :     1
Total                 :     3
Total VOD Req         :     0
Total LIVE Req        :     0
Total DVRCast Req     :     0
Total Other Proxy Req :     0
 
   
Live Streaming
-----
UpStream BW          :          0 kbps
DownStream BW        :        274 kbps
UpStream Bytes       :       3194
DownStream Bytes     :  124362967
Num of Instance Load :          1
 
   

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

NE-DEMO-SE2# show flash-media-streaming stream-status live
Display flash-media-streaming livestreams
 
   
Display maximum 4 applications, 8 forwarders, and 8 client stream info
 
   
Forwarder
---------
ClientReqUrl        : rtmp://Temp4.se.fmslive.com/live/livestream
path2OS             : 2.225.2.65->2.225.2.62
reqFwdUrl           : rtmp://2.225.2.65/live/cds_fms_proxy/2.225.2.62/live/livestream
Upstream BW (Kbps)  : 0
Downstream BW (Kbps): 267
Upstream Bytes      : 3487
Downstream Bytes    : 138278573
numClient           : 1
 
   

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.

NE-DEMO-SE2# show statistics flash-media-streaming
Flash Media Streaming Statistics
Statistics were last cleared on Thursday. 06-Dec-2007 37:22:58 UTC.
 
   
Connections
-----------
Current               :     1
Current VOD           :     0
Current LIVE          :     1
Max Concurrent        :     1
Total                 :     1
Total VOD Req         :     0
Total LIVE Req        :     0
Total DVRCast Req     :     0
Total Other Proxy Req :     0
 
   
Live Streaming
-----
UpStream BW          :        0 kbps
DownStream BW        :      274 kbps
UpStream Bytes       :     3487
DownStream Bytes     : 149456451
Num of Instance Load :         1
 
   

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 live
Display flash-media-streaming livestreams
 
   
Display maximum 4 applications, 8 forwarders, and 8 client stream info
Forwarder
---------
ClientReqUrl        : rtmp://2.225.2.65/live/cds_fms_proxy/2.225.2.62/live/livestream
path2OS             : 2.225.2.62
reqFwdUrl           : rtmp://2.225.2.62/live/livestream
Upstream BW (Kbps)  : 0
Downstream BW (Kbps): 261
Upstream Bytes      : 3337
Downstream Bytes    : 155736798
numClient           : 1
 
   

9 Related Publications

To see the complete set of information about the Enterprise Content Delivery System, see Documentation for the Cisco Enterprise Content Delivery System on Cisco.com:

http://www.cisco.com/en/US/docs/video/ecds/documentation.html

10 Obtaining Documentation and Submitting a Service Request

For 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.