Cisco Internet Streamer CDS 2.0–2.3 Software Configuration Guide April 2009 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
CONTENTS Preface xiii Document Revision History Audience xiv Objective xiv Document Organization xiv Document Conventions xv Related Publications xiii xvi Obtaining Documentation and Submitting a Service Request CHAPTER 1 Product Overview xvii 1-1 Overview 1-1 Ingest and Distribution 1-3 Prefetch Ingest 1-3 Dynamic Ingest 1-3 Hybrid Ingest 1-3 Live Stream Ingest and Split 1-4 Delivery 1-4 3-Screen Session Shifting 1-5 Management 1-7 Content Delivery System Architecture 1-7 Service Engine
Contents Content Acquirer Redundancy 1-27 Internet Streamer Redundancy 1-27 Service Router Redundancy 1-27 Internet Streaming CDSM Redundancy CHAPTER 2 Network Design 1-27 2-1 Cisco CDS Topology 2-1 Device Groups 2-2 Baseline Groups 2-3 Delivery Service 2-3 Origin Servers 2-5 Proxy Server 2-5 Manifest File 2-5 Crawling 2-5 Content Acquirer 2-6 SMB Servers 2-6 HTTP Servers 2-7 Internet Streamer 2-7 HTTP Download—Disabling Service Workflow 2-7 2-7 Programs 2-9 Live Programs 2-9 Rebroadcasts 2-10 API
Contents CHAPTER 4 Configuring Devices 4-1 Configuring Locations 4-1 Configuring Device Groups 4-3 Device Group Overlap 4-5 Configuring the Service Engine 4-6 Activating a Service Engine 4-6 Assigning Devices to Device Groups 4-9 Configuring Bandwidth for Replication and Ingest 4-10 Default Bandwidth 4-11 Scheduled Bandwidth 4-12 Service Control 4-14 Configuring Service Rules 4-15 Configuring ICAP 4-19 Configuring PCMM QoS Policy 4-22 Configuring URL Signing 4-23 Configuring Transaction Logs 4-26 App
Contents Configuring Troubleshooting 4-86 Configuring Service Router Settings 4-86 Configuring the Service Router 4-87 Activating a Service Router 4-87 Configuring Routing Settings 4-88 IP-Based Redirection 4-90 Configuring Application Control 4-90 General Settings—Last Resort 4-91 Configuring the CDSM CHAPTER 5 Configuring Services 4-91 5-1 Configuring Delivery Services 5-1 Content Origins 5-1 Creating Delivery Service 5-4 Identifying Content 5-11 Identifying Content Using the CDSM 5-11 Identifyin
Contents Configuring Service Routing 6-9 Coverage Zone File Registration 6-9 Configuring Global Routing 6-11 CHAPTER 7 Monitoring the Internet Streamer CDS 7-1 System Monitoring 7-1 System Status 7-1 Device Alarms 7-2 Troubleshooting Devices Using the System Status Bar Service Alarms 7-3 System Home Page 7-4 System Audit Logs 7-5 Device Monitoring 7-6 Devices Table 7-6 Device Home Page 7-7 Using show and clear Commands 7-9 Using the CDSM show or clear Command Tool CPU Utilization 7-13 7-3 7-9 Repor
Contents Archive Working Log 7-34 Exporting Log Files 7-34 Windows Media Transaction Logging CHAPTER 8 Maintaining the Internet Streamer CDS 7-35 8-1 Software Upgrade 8-1 Getting a Software File from Cisco.
Contents APPENDIX A Troubleshooting A-1 Troubleshooting Service Router Configurations Troubleshooting the Distribution Hierarchy Troubleshooting Content Acquisition Enabling the Kernel Debugger APPENDIX B Creating Manifest Files A-1 A-2 A-3 A-6 B-1 Introduction B-1 Manifest File Requirements B-2 Working with Manifest Files B-2 Specifying a Single Content Item B-2 Specifying a Crawl Job B-3 Writing Common Regular Expressions B-5 Scheduling Content Acquisition B-5 Specifying Shared Attributes
Contents host B-25 proxyServer B-27 item B-28 crawler B-35 item-group B-38 matchRule B-41 match B-41 contains B-43 XML Schema B-44 Manifest XML Schema B-44 PlayServerTable XML Schema B-48 Default PlayServerTable Schema B-49 Manifest File Time Zone Tables APPENDIX Creating Coverage Zone Files C Introduction B-50 C-1 C-1 Coverage Zone XML Schema C-2 Coverage Zone File Examples C-3 Scenario 1: Coverage Zone with Client Network Only C-3 Scenario 2: Coverage Zone with Geographical Location of the Data
Contents Session Lookup APPENDIX E CLI Commands D-9 E-1 Configuring Port Channel E-1 Redundant Dedicated Management Ports Configuring Last-Resort Routing Configuring Standby Interfaces E-1 E-6 E-6 Other CLI Commands E-10 CDNFS cleanup Command E-10 Disk Commands E-11 cache content Command E-12 APPENDIX F URL Signing and Validation F-1 Introduction F-1 URL Signing Components F-1 Supported Protocols and Media F-2 Configuring the CDS for URL Signing F-2 URL Signing Script F-2 Example of a Pyt
Contents Testing Flash Media Streaming Dynamically Ingested Content Testing Flash Media Streaming—Live Streaming G-24 APPENDIX H Software Licensing Information Notices H-1 OpenSSL/Open SSL Project License Issues H-1 G-22 H-1 H-1 Cisco Internet Streamer CDS 2.0-2.
Preface This preface describes the audience, use, and organization of the Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide. The preface also outlines the document conventions and support information.
Preface Note All information, fields, and features that are marked as a Release 2.1 feature are also available in Releases 2.2 and 2.3. All information, fields, and features that are marked as a Release 2.2 feature are also available in Release 2.3. All information, fields, and features that are marked as a Release 2.0 feature are only available in Release 2.0.
Preface Chapter or Appendix Description Chapter 6, “Configuring the System” Provides information on system configuration for the Internet Streamer CDS. Chapter 7, “Monitoring the Internet Streamer CDS” Provides information on monitoring the Internet Streamer CDS. Chapter 8, “Maintaining the Internet Streamer CDS” Provides information on upgrading the Internet Streamer CDS software, deleting devices from the system, performing disk maintenance, and removing content from the system.
Preface Caution Convention Description ^ The symbol ^ represents the key labeled Control—for example, the key combination ^D in a screen display means hold down the Control key while you press the D key. < > Nonprinting characters, such as passwords, are in angle brackets in contexts where italics are not available. !, # An exclamation point ( ! ) or a pound sign ( # ) at the beginning of a line of code indicates a comment line. Means reader be careful.
Preface 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.
Preface Cisco Internet Streamer CDS 2.0-2.
CH A P T E R 1 Product Overview This chapter provides an introduction to the Cisco Internet Streamer Content Delivery System (CDS). This chapter has the following major topics: • Overview, page 1-1 • Content Delivery System Architecture, page 1-7 Overview The Cisco Content Delivery System (CDS) is a distributed network of Content Delivery Engines (CDEs) running Content Delivery Applications (CDAs) that collaborate with each other to deliver multi-format content to a variety of client devices.
Chapter 1 Product Overview Overview The Service Engine can function as a Content Acquirer and Internet Streamer, or just as an Internet Streamer. Figure 1-1 shows the major elements of a CDS network. How content flows, from ingest to distribution within the CDS, to delivery to client devices, is dictated by the content delivery services defined for each Content Origin.
Chapter 1 Product Overview Overview Ingest and Distribution The Service Engine designated as the Content Acquirer for a delivery service is the ingest device. Cisco Internet Streamer CDS Releases 2.0–2.3 supports the following methods of content ingest: • Prefetch ingest • Dynamic ingest • Hybrid ingest • Live stream ingest and split The distribution of content within the CDS is determined by the method of ingest used. Note The recommended maximum number of prefetched content items is 200,000.
Chapter 1 Product Overview Overview that is cached on the Service Engines by using this method is subject to the same deletion rules as the dynamic ingest method. The metadata that is propagated can be used to specify explicit controls and policies for streaming the content. Live Stream Ingest and Split The live stream ingest method distributes a live content feed to all the Service Engines participating in the content delivery service and helps to scale the content delivery to a very large audience.
Chapter 1 Product Overview Overview Table 1-2 Supported Content Types (continued) Content Types and Formats Transport Protocols Typical Client Types Access Network Type Other Hypertext and HTTP image files (HTML, JPEG, and so on) Web browsers and other HTTP clients Wired Wi-Fi Cellular MPEG (MP1, MP2, MP4) RTP, RTSP MPEG clients Wired Adobe Flash (SWF, FLV, MP3) RTMP, HTTP Adobe Flash Player 9 for Windows, Mac OS, and Wired Linux Wi-Fi Cellular H.2642 RTMP, HTTP H.
Chapter 1 Product Overview Overview XML files is available upon request. The operator can enable session shifting on a delivery service basis and also configure a TV streamer IP address and port for each delivery service. The operator also needs to specify which Service Router has the session database. The Content map aggregates same semantic content across the TV CDS and Internet Streamer CDS systems.
Chapter 1 Product Overview Content Delivery System Architecture Management The Internet Streaming CDSM, a secure Web browser-based user interface, is a centralized system management device that allows an administrator to manage and monitor the entire CDS network. All devices, Service Engines and Service Routers, in the CDS are registered to the Internet Streaming CDSM.
Chapter 1 Product Overview Content Delivery System Architecture • Maintenance of information about the entire CDS topology and all the delivery services. This includes upkeep of a list of Service Engines in the same delivery service that is used for distributing prefetched, dynamic, and live stream content. • Maintenance of the database that stores and distributes metadata about the content, and the topology and delivery service information.
Chapter 1 Product Overview Content Delivery System Architecture The Internet Streamer function is implemented as a set of protocol engine applications. The protocol engine applications are: • Web Engine • Windows Media Engine • Movie Streamer Engine • Flash Media Streaming Engine Web Engine All HTTP client requests that are redirected to a Service Engine by the Service Router are handled by the Web Engine.
Chapter 1 Product Overview Content Delivery System Architecture The Web Engine communicates to the upstream Service Engine for cache fill operations. This interaction is based on HTTP. This cache fill operation is on demand and hence only occurs when the content is not stored locally. The upstream Service Engine can be selected dynamically by means of the Hierarchical Cache Routing Module, or can be configured statically through the Internet Streaming CDSM.
Chapter 1 Product Overview Content Delivery System Architecture The Windows Media Engine streams Windows Media content, with the capability of acting both as a server and as a proxy. It streams prefetched content to the Windows Media Player, acts as a proxy for client requests, splits a live stream into multiple live streams, and caches content requested from remote servers. Windows Media Engine acts as Windows Media Server for prefetched or cached content stored locally.
Chapter 1 Product Overview Content Delivery System Architecture is already stored locally is generally better than using content from the origin server; this is because the Service Engine is typically closer to the requesting clients, and therefore network bandwidth to the origin server is freed up. Note When using Windows Media Server 2008 as the origin server, the source content type must be a playlist or encoder type.
Chapter 1 Product Overview Content Delivery System Architecture With pass-through authentication, the Windows Media Engine establishes a tunnel between the client and the origin server so that the origin server can authenticate the client. Bandwidth Management Bandwidth management of Windows Media content can be controlled by setting limits for incoming and outgoing bandwidth and session bit rate and Fast Start maximum bandwidth.
Chapter 1 Product Overview Content Delivery System Architecture The Movie Streamer Engine is an RTSP streaming engine that supports Third Generation Partnership Project (3GPP) streaming files (.3gp). Support of 3GPP provides for the rich multimedia content over broadband mobile networks to multimedia-enabled cellular phones. Note The streaming capability of Movie Streamer Engine only depends on the movie file format or stream transport type. It is independent of codec types.
Chapter 1 Product Overview Content Delivery System Architecture • Accelerated—This method supports only RTP over UDP. Content must be reprocessed by the Movie Streamer Linear Hinter. The linear hinter process can be initiated manually by the administrator or dynamically triggered by the first request for the content. The Movie Streamer Linear Hinter process may take a while, so the first request that triggers this process is served by means of the non-accelerated method.
Chapter 1 Product Overview Content Delivery System Architecture No client information is sent to the origin server. No per-client control connection is present between edge to origin server for VOD streaming. Note The Cisco CDS Flash Media Streaming Engine supports the Adobe Flash Media Rights Management Server (FMRMS) for VOD content; it is not supported for live streaming. Adobe FMRMS protects media content delivered to Adobe Media Player and Adobe AIR applications.
Chapter 1 Product Overview Content Delivery System Architecture “Cache Fill Operations” section on page 1-9. This interaction uses HTTP. Once the content is in the process of being retrieved by the Web Engine, the Flash Media Streaming Engine uses RTMP to begin streaming the content. The following describes the characteristics of caching content using HTTP for RTMP client requests; 1. Origin server-based cache validation is still honored for the cached content. 2.
Chapter 1 Product Overview Content Delivery System Architecture Codecs The Flash Media Streaming codec that is supported in Release 2.1 is On2 VP6. The Flash Media Streaming codecs supported in Release 2.2, in addition to On2 VP6, are listed in Table 1-4. Table 1-4 Codecs Supported in CDS Releases 2.2 and 2.3 for Flash Media Streaming Standard Details ISO/IEC 14496-3 MPEG-4 Part 3, also known as AAC+, HE-AAC.
Chapter 1 Product Overview Content Delivery System Architecture The Adobe Flash Media Encoder can publish the streams to any Adobe Flash Media Server acting as the origin server. Clients use the RFQDN to get the live content. The request from the client for “streamname” is mapped to origin_appinst_streamname internally in the CDS to differentiate between two streams with the same name in two different delivery services.
Chapter 1 Product Overview Content Delivery System Architecture Service Router The Service Router mediates requests from the client devices and redirects the requests to the most appropriate Service Engine. It monitors the load of the devices and does automatic load balancing. The Service Router is the authoritative Domain Name System (DNS) server for the routed request for the Fully Qualified Domain Name (FQDN) of the origin server.
Chapter 1 Product Overview Content Delivery System Architecture Service Router Workflow The Service Router workflow for clients connected to the service provider’s network is as follows: 1. The client sends the DNS query for the routed FQDN to the local DNS server. 2. The DNS server replies with the Service Router IP address. 3. The client issues an HTTP or RTSP request to the Service Router. 4. If the Service Router finds the client’s subnet in the Coverage Zone file, the following occurs: a.
Chapter 1 Product Overview Content Delivery System Architecture When content is requested by a client, the Service Router checks the client’s IP address to find the coverage zone that contains that IP address. The Service Router then selects the Service Engine that serves this coverage zone. If a specific IP address is in multiple coverage zones, the one with the more specific range is selected.
Chapter 1 Product Overview Content Delivery System Architecture Note In Release 2.2, the keepalive messages between the Service Router and Service Engine are transmitted and received on port 2323. However, the Release 2.2 software interoperates with older software releases that do not use port 2323 for keepalive messages. If a firewall is configured between the Service Engine and the Service Router, port 2323 (UDP) must be opened for the keepalive message to go through.
Chapter 1 Product Overview Content Delivery System Architecture geographical location of the Service Engines listed in the Coverage Zone file, and the closest and least-loaded Service Engine is selected. Geographically locating a client is used when users roam outside of their home network. In order to provide routing to off-net clients, the Service Router communicates with a Geo-Location server, which maps IP addresses to a geographic location.
Chapter 1 Product Overview Content Delivery System Architecture In content-based routing, the Service Router redirects the request based on the Uniform Resource Identifier (URI). Requests for the same URI are redirected to the same Service Engine, provided the Service Engine’s thresholds are not exceeded. The number of redundant copies of content is configurable for content-based routing.
Chapter 1 Product Overview Content Delivery System Architecture As part of the network management process, the administrator can perform basic administration operations on the Internet Streaming CDSM database, including backup and restore. Device Management The Internet Streaming CDSM sends device configuration changes to the selected device or group of devices once the change has been submitted.
Chapter 1 Product Overview Content Delivery System Architecture Resiliency and Redundancy A CDS that is designed with full redundancy and no single point of failure includes redundant Internet Streaming CDSMs and Service Routers. The redundancy mechanisms for the Content Acquirer and Internet Streamer applications running on the Service Engines operate differently.
Chapter 1 Product Overview Content Delivery System Architecture that the administrator cannot change configurations or monitor the CDS. As soon as a failure to connect to the CDSM is noticed, the administrator can activate the standby CDSM. For information on making the standby CDSM the primary CDSM, see the “Changing a Standby to a Primary CDSM” section on page 3-9. Cisco Internet Streamer CDS 2.0-2.
CH A P T E R 2 Network Design Provisioning the Cisco CDS consists of two stages: • Register the devices to the Internet Streaming CDSM and define the network topology and device groups. • Configure the delivery services that deliver content to the clients. This chapter describes the details of the two stages of provisioning a Cisco CDS network and how metadata and content flow through the Cisco CDS.
Chapter 2 Network Design Cisco CDS Topology Figure 2-1 Location Trees Example San Francisco - Financial Concord Tier 1 South San Francisco San Francisco - Mission Pleasant Hill Walnut Creek Tier 2 Daly City San Mateo San Francisco Bay View District San Ramon 211812 Tier 3 Half Moon Bay Tier 4 The Location Trees define preferred distribution routes. The Tier 1 locations are located closest to the Internet or backbone. Tier 1 locations can communicate with all other Tier 1 locations.
Chapter 2 Network Design Delivery Service Baseline Groups A baseline group is a special type of device group that denotes a group of devices for a particular service. There are three baseline groups: • Web Baseline Group—Used for web-based content • Video Baseline Group—Used for video content • Platform Baseline Group—Used for platform-specific configurations A device group can be configured as a baseline group. A device can be assigned to a baseline group in the following three ways: 1.
Chapter 2 Network Design Delivery Service Figure 2-2 Delivery Service Distribution Tree Example Origin server Concord San Francisco - Financial Tier 1 Content Aquirer South San Francisco San Francisco - Mission Pleasant Hill Walnut Creek Tier 2 Daly City San Mateo San Francisco Bay View District San Ramon 211782 Tier 3 Half Moon Bay Tier 4 The Cisco CDS supports two types of delivery services: 1.
Chapter 2 Network Design Delivery Service Origin Servers Content is stored on origin servers. Each delivery service is configured with one content origin. The same origin server can be used by multiple live delivery services. However, only one prefetch/caching delivery service is allowed per content origin.
Chapter 2 Network Design Delivery Service later processing. The crawler starts with a list of URLs to visit, identifies every web link in the page, and adds every link to the list of URLs to visit. The process ends after one or more of the following conditions are met: • Links have been followed to a specified depth. • Maximum number of objects has been acquired. • Maximum content size has been acquired. The crawler works as follows: 1.
Chapter 2 Network Design Service Workflow HTTP Servers The no-cache directive in an HTTP server response header tells the client that the content requested is not cacheable. When an HTTP server responds with a no-cache directive, the Content Acquirer behaves as follows: • If the content to be ingested is specified in an - tag in the Manifest file, the Content Acquirer ignores the no-cache directive and fetches the content anyway.
Chapter 2 Network Design Service Workflow Figure 2-3 Delivery Service Workflow Diagram 1. The topology is propagated to all the devices registered and activated in the Internet Streaming CDSM. The delivery service configuration is propagated to all the Service Engines subscribed to the delivery service. The Manifest file information is sent to the Content Acquirer for the delivery service. 2. The Content Acquirer parses the Manifest file and generates the metadata.
Chapter 2 Network Design Programs The Service Engine processes the user request, and based on the metadata, determines the content was prefetched and pinned in its local storage. The Service Engine looks up the policies for the content and streams the content to the user. • Dynamic Ingest/Cached Content Flows 10, 11, 12, “Non-ingested contents—Hierarchical cache resolution,” “Native Protocol Response,” and “Dynamic ingest response.
Chapter 2 Network Design Programs Rebroadcasts In a scheduled rebroadcast, prefetched content is scheduled to be streamed from the Service Engines using multicast. Content can only be selected from one delivery service. The Service Engines and device groups assigned to the delivery service are automatically selected when the content files are chosen for the program. API Program File Programs can be defined through the Internet Streaming CDSM or through an API.
CH A P T E R 3 Getting Started This chapter discusses initial device configuration, logging into and navigating the Internet Streaming CDSM, and a typical CDS configuration workflow.
Chapter 3 Getting Started Logging In to the Internet Streaming CDSM Step 2 Note If you are using Mozilla Firefox version 3.01 or higher as your web browser, 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.
Chapter 3 Getting Started Activating and Synchronizing the Devices Activating and Synchronizing the Devices The CDS administrator approves a device by making it active. This security feature prevents unauthorized devices from joining the CDS. Caution All devices must be synchronized with each other in order for the CDS to function properly. Synchronization ensures accurate timestamps in all the logs and accuracy in caching decisions determined by If Modified Since (IMS) lookups.
Chapter 3 Getting Started Activating and Synchronizing the Devices Note Step 3 If the device you want to activate is not listed in the Devices Table, restart the CMS for that device by telneting to it and entering no cms enable followed by cms enable in global configuration mode. Click Activate in the Device home page. The Location dialog box is displayed (Figure 3-3). Figure 3-3 Step 4 Device Home Page—Location Dialog Box Create or choose a location.
Chapter 3 Getting Started Activating and Synchronizing the Devices Tip For a quick way to get to other SEs, click the Display All Devices icon located to the left of the Expand All button. This icon toggles between the Display All Devices and Menu icons.
Chapter 3 Getting Started Navigating the Internet Streaming CDSM If you are creating a new location, you can select a parent location, or leave the default of “none.” Step 3 Click Submit to save the settings. The Status in the Devices Table for all the inactive SEs shows “pending” until the devices have been fully activated. Note All devices activated in this way need to have the NTP settings configured. See Step 6 through Step 9 in the “Activating and Setting NTP for Each Device” section on page 3-3.
Chapter 3 Getting Started Navigating the Internet Streaming CDSM The System Status bar, tabs, tab options, and tools are accessible from any page in the CDSM. The left panel menu changes depending on which tab and tab option you choose. Devices, Services, and Other Tables The Devices Table page shows all the devices registered in the CDSM. Figure 3-7 shows an example of the Devices Table page.
Chapter 3 Getting Started Configuring Primary and Standby CDSMs • Telnet to the device (In Release 2.3, Telnet is disabled by default.) • Update the device software • Assign the device to baseline groups From the Device home page you can access the delivery services and device groups the device is assigned to, by clicking the appropriate link. All delivery services, or device groups (depending on which link you clicked), configured in your CDS are displayed.
Chapter 3 Getting Started Configuring Primary and Standby CDSMs Step 2 Configure the standby CDSM. CDE(config)# cdsm role standby Step 3 Identify the IP address of the primary CDSM. CDE(config)# cdsm ip 10.1.1.90 Step 4 Initiate the Centralized Management System (CMS). CDE(config)# cms enable Step 5 Save the configuration. CDE# copy running-config startup-config Step 6 Activate the standby CDSM by using the web interface of the primary CDSM.
Chapter 3 Getting Started Typical Configuration Workflow Typical Configuration Workflow Once you have completed activating and configuring the NTP servers for all the devices in the CDSM, you are ready to configure the CDS for content delivery. For information about activating and configuring the NTP servers for a device, see the “Activating and Setting NTP for Each Device” section on page 3-3.
Chapter 3 Getting Started Typical Configuration Workflow Table 3-1 Configuration Workflow (continued) Task Description Where to Find More Information Create Coverage Zone File Map SEs to client service areas by IP Appendix C, “Creating Coverage Zone address or geographic location Files” Import or Upload Coverage Zone File Apply Coverage Zone mappings to CDS “Coverage Zone File Registration,” page 6-9 Configure Global Routing Method Set the Coverage Zone file “Configuring Global Routing” sectio
Chapter 3 Getting Started Typical Configuration Workflow Cisco Internet Streamer CDS 2.0-2.
CH A P T E R 4 Configuring Devices This chapter discusses configuring locations and device groups for devices, and detailed instructions on configuring the different types of devices–CDSMs, SEs, and, SRs.
Chapter 4 Configuring Devices Configuring Locations Figure 4-1 Step 2 Locations Table Page In the task bar, click the Create New Location icon. The Creating New Location page is displayed (Figure 4-2). To edit a location, click the Edit icon next to the location name. Figure 4-2 Step 3 Creating New Location Page Enter the settings as appropriate. See Table 4-1 for a description of the fields. Cisco Internet Streamer CDS 2.0-2.
Chapter 4 Configuring Devices Configuring Device Groups Table 4-1 Step 4 Location Fields Field Description Name Name of the location. Parent Location Choose a location from the drop-down list. A location with no parent, None, is level 1. The location level is displayed after you choose a parent location. Comments Enter any information about the location. Click Submit to save the settings.
Chapter 4 Configuring Devices Configuring Device Groups Figure 4-3 Step 2 Device Groups Table Page In the task bar, click the Create New Device Group icon. The Creating New Device Group page is displayed (Figure 4-4). To edit a device group, click the Edit icon next to the device group name. Figure 4-4 Creating New Device Group Page Step 3 In the Name field, enter the name of the device group.
Chapter 4 Configuring Devices Configuring Device Groups For information about baseline groups, see the “Baseline Groups” section on page 2-3. Step 6 To customize the left panel menu for this device group, click the Select pages to hide from the menu for this device group arrow, and check the pages you want to hide. To collapse these settings, click the arrow again. Use this feature to remove from view any configuration pages that you do not need for the device group.
Chapter 4 Configuring Devices Configuring the Service Engine If you disable device group overlap after you have assigned devices to multiple device groups, existing overlaps are maintained. Any newly added groups will not allow assignment of devices that are already assigned to another group, and new devices cannot be added to any groups with overlapping devices.
Chapter 4 Configuring Devices Configuring the Service Engine Figure 4-5 Devices Table Page Step 2 Click the Edit icon next to the device you want to configure. The Device home page is displayed. Step 3 Click Show All to display the top-level menu options, and click Device Activation. The Device Activation page is displayed (Figure 4-6). Figure 4-6 Device Activation Page Cisco Internet Streamer CDS 2.0-2.
Chapter 4 Configuring Devices Configuring the Service Engine Step 4 Enter the settings as appropriate. See Table 4-2 for a description of the fields. Table 4-2 Device Activation Fields Field Description Name Name of the device. Activate To activate or deactivate the device, check or uncheck the Activate check box. Server Offload To offload this device for maintenance or a software upgrade, check the Server Offload check box.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-2 Device Activation Fields (continued) Field Description Set Default Coverage Zone File When checked, which is the default setting, a default Coverage Zone file is generated with the SE serving the local subnet it resides on. The coverage zone is a CDS network-wide mapping of client IP addresses to SE IP addresses that should respond to client requests.
Chapter 4 Configuring Devices Configuring the Service Engine • Through the device Assignment page • Through the Device home page, if the device group is a baseline group To assign devices to device groups through the Assignment page, do the following: Step 1 Choose Devices > Devices, and click the Edit icon next to the device you want to assign. Step 2 Click Show All, and then click Assignments > Device Groups. The Assignment page is displayed (Figure 4-7).
Chapter 4 Configuring Devices Configuring the Service Engine • Scheduled Bandwidth Default Bandwidth The default bandwidth settings can be configured for acquisition (ingest) and distribution (replication) of content. The default settings are used unless a scheduled bandwidth is configured for a specified time period. To set the default bandwidth for replication, do the following: Step 1 Choose Devices > Devices > Replication > Default Bandwidth.
Chapter 4 Configuring Devices Configuring the Service Engine Bandwidth Graph To view a graphical representation of the bandwidth settings, click the Display Graph icon in the task bar. The Acquisition and Distribution Bandwidth graph is displayed in a new window. The vertical axis of the graph represents the amount of bandwidth in Kbps (kilobits per second) and the horizontal axis represents the days of the week.
Chapter 4 Configuring Devices Configuring the Service Engine Figure 4-9 Step 2 Replication Scheduled Bandwidth Table Page Aggregate Settings is set to Yes by default. If this SE belongs to a device group, and the settings have not been configured using the device group, you can enter the settings and they will apply to the device group as well. If the settings are previously configured through the device group, the current configuration is displayed for view only.
Chapter 4 Configuring Devices Configuring the Service Engine Figure 4-10 Step 4 Replication Scheduled Bandwidth Page Enter the settings as appropriate. See Table 4-5 for a description of the fields. Table 4-5 Replication Scheduled Bandwidth Fields Field Description Bandwidth Type Distribution-in—For incoming content distribution traffic from SEs. Distribution-out—For outgoing content distribution traffic to SEs. Acquisition-in—For incoming content acquisition traffic from origin servers.
Chapter 4 Configuring Devices Configuring the Service Engine • Configuring PCMM QoS Policy • Configuring URL Signing • Configuring Transaction Logs Configuring Service Rules Note This is a licensed feature. Please ensure that you have purchased a Service Rule license for this advanced feature.
Chapter 4 Configuring Devices Configuring the Service Engine Note Step 6 The last configuration submitted for the device, whether it is the device group configuration or the individual device configuration, is the configuration the device uses. Click the Create New icon in the task bar. The Service Rules page is displayed (Figure 4-11). To edit a service rule, click the Edit icon next to the service rule you want to edit.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-6 Service Rules Pattern Types Pattern Type Description Syntax domain rule pattern-list list_num Matches the domain name in the URL or the host header against a regular expression. For example, “.*ibm.*” matches any domain name domain dn_regexp that contains the “ibm” substring. “\.foo\.com$” matches any domain name that ends with the “.foo.com” substring.
Chapter 4 Configuring Devices Configuring the Service Engine Note Table 4-7 Movie Streamer and Flash Media Streaming support URL signing in Release 2.2. Flash Media Streaming only supports the following actions: allow, block, and validate-url-signature. Service Rule Actions Action Type Description Syntax allow Allows incoming requests that match the pattern list.
Chapter 4 Configuring Devices Configuring the Service Engine Execution Order of Rule Actions The order in which the rule actions are executed is as follows: 1. block or allow Note Note The allow and block actions carry the same precedence. The order of execution depends on the order of configuration between allow and block actions. Other actions always take precedence over allow. 2. redirect (before cache lookup) 3. rewrite (before cache lookup) 4.
Chapter 4 Configuring Devices Configuring the Service Engine Caution The maximum file size supported is 2 GB. Files that exceed this size limit are not supported for ICAP processing. To configure ICAP settings, do the following: Step 1 Choose Devices > Devices > Service Control > ICAP. The ICAP page is displayed (Figure 4-12).
Chapter 4 Configuring Devices Configuring the Service Engine Step 8 Click the Create New icon in the task bar. The ICAP Services page is displayed (Figure 4-13). To edit the ICAP service, click the Edit icon next to the ICAP service you want to edit. Figure 4-13 ICAP Services Page Step 9 In the Name field, enter a name for the ICAP service. Step 10 Check the Enable check box to enable ICAP service.
Chapter 4 Configuring Devices Configuring the Service Engine Figure 4-14 Step 15 ICAP Server Page Enter the settings as appropriate. See Table 4-8 for a description of the fields. Table 4-8 ICAP Server Fields Field Description Server Host Hostname or IP address of the ICAP server. Server Port Port number on which the ICAP server is to be configured to process HTTP requests. The default port number is 1344. If no port number is specified, the default is used.
Chapter 4 Configuring Devices Configuring the Service Engine To configure a PCMM QoS Policy, do the following: Step 1 Choose Devices > Devices > Service Control > PCMM QoS Policy. The PCMM QoS Policy page is displayed (Figure 4-15). Figure 4-15 PCMM QoS Policy Page Step 2 Check the Enable check box to enable policy server settings for the device. Step 3 Check the Set Config File or URL check box to specify the configuration file for the HTTP callout to the policy server.
Chapter 4 Configuring Devices Configuring the Service Engine To create a URL signature key, do the following: Step 1 Choose Devices > Devices > Service Control > URL Signing. The URL Signing Table page is displayed. Step 2 Aggregate Settings is set to Yes by default. If this SE belongs to a device group, and the settings have not been configured using the device group, you can enter the settings and they will apply to the device group as well.
Chapter 4 Configuring Devices Configuring the Service Engine metafile (.asx file extension), Movie Streamer file, or Flash Media Streaming file, and to validate the URL signature on incoming requests to the SE. For more information on creating service rules, see the “Configuring Service Rules” section on page 4-15. URL signature key authentication is implemented by using the generate-url-signature and validate-url-signature rule actions that can be applied to specific rule patterns.
Chapter 4 Configuring Devices Configuring the Service Engine Note When configuring service rules, you must configure the same service rules on all SEs participating in a delivery service in order for the service rules to be fully implemented. The rule action must be common for all client requests because the SR may redirect a client request to any SE in a delivery service depending on threshold conditions.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-11 Transaction Log Settings Fields (continued) Field Description Archive occurs How often the working log is archived and the data is cleared from the working log. Choose one of the following: Choose every to archive every so many seconds, and enter the number of seconds for the interval.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-11 Transaction Log Settings Fields (continued) Field Description Windows Media Settings Enable Windows Media Settings Enables Windows Media transaction logging. Log File Format Sets Windows Media Streaming Engine to generate transaction logs in the following formats: • • extended Uses the standard Windows Media Services 4.
Chapter 4 Configuring Devices Configuring the Service Engine • Configuring Windows Media Streaming Multicast Station • Configuring Windows Media Streaming Multicast Station Schedule • Configuring Windows Media Streaming—Broadcast Alias • Configuring Windows Media Streaming—Bypass List • Configuring Movie Streamer—General Settings • Configuring RTSP Advanced Settings • Configuring Flash Media Streaming • Configuring Web Engine HTTP Connections • Configuring Web Engine HTTP Caching • Conf
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-12 Application Control Default and Maximum Bandwidth Fields (continued) Field Description Windows Media Default Default bandwidth allowed for outgoing Windows Media traffic from Outgoing Bandwidth the SE. Maximum Maximum bandwidth permitted by system license.
Chapter 4 Configuring Devices Configuring the Service Engine If you remove all device group settings, all device settings displayed with Aggregate Settings enabled are removed as well. Note Step 3 The last configuration submitted for the device, whether it is the device group configuration or the individual device configuration, is the configuration the device uses. Click Create New in the task bar. The Scheduled Bandwidth page is displayed.
Chapter 4 Configuring Devices Configuring the Service Engine The vertical axis of the graph represents the amount of bandwidth in kilobits per second (kb/s) , and the horizontal axis represents the days of the week. The units shown on the vertical axis are determined dynamically based on the bandwidth rate for a particular bandwidth type. The units shown on the horizontal axis represent 24 hours per each day of the week. Each type of bandwidth is represented by a different color.
Chapter 4 Configuring Devices Configuring the Service Engine Figure 4-16 Windows Media Streaming Page—General Settings Cisco Internet Streamer CDS 2.0-2.
Chapter 4 Configuring Devices Configuring the Service Engine Step 2 Enter the settings as appropriate. See Table 4-15 for a description of the fields. Table 4-15 Windows Media Streaming General Settings Fields Field Description Enable Windows Media Services When checked, Windows Media Services is enabled. To disable services, uncheck the check box.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-15 Windows Media Streaming General Settings Fields (continued) Field Description HTTP Allowed Extensions List of allowable extensions for HTTP. You can add or delete filename extensions from this list with the following restrictions: • Each extension must be alphanumeric, with the first character in the extension being an alphabetic character. • You cannot have more than 10 characters in a filename extension.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-15 Step 3 Windows Media Streaming General Settings Fields (continued) Field Description Maximum TTL The maximum time-to-live for objects in the cache. The value ranges are the following: 1 to 157680000 seconds 1 to 2628000 minutes 1 to 43800 hours 1 to 1825 days The default is 1 day. Minimum TTL The minimum time-to-live (in minutes) for objects in the cache. The default is 60. The range is from 0 to 86400.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-16 Multicast Station Fields Field Description Station Name Name for the multicast station. Address Class D IP address to be used as the multicast station IP address. Port The port number to be used by this station. Media The source URL of the Windows Media streaming media. The source file, for example source.asf, can be stored on any Windows Media server or SE. For multicast-in multicast-out, the source file is an .nsc file.
Chapter 4 Configuring Devices Configuring the Service Engine Configuring Windows Media Streaming Multicast Station Schedule To configure the Windows Media Streaming Multicast Station Schedule, do the following: Step 1 Choose Devices > Devices > Application Control > Windows Media Streaming > Multicast Station Schedules. The Windows Media Streaming Multicast Station Schedule Table page is displayed. Step 2 Aggregate Settings is set to Yes by default.
Chapter 4 Configuring Devices Configuring the Service Engine If the settings are previously configured through the device group, the current configuration is displayed for view only. New settings must be configured through the associated device group. If you want to configure settings for this SE only, and override the device group settings on this SE, set Aggregate Settings to No. If you remove all device group settings, all device settings displayed with Aggregate Settings enabled are removed as well.
Chapter 4 Configuring Devices Configuring the Service Engine To configure the list of hosts for bypassing incoming bandwidth limits, follow these steps: Step 1 Choose Devices > Devices > Application Control > Windows Media Streaming > Bypass List. The Bypass List page is displayed. Step 2 In the Windows Media BW Incoming Bypass List field, enter up to four IP addresses or hostnames of hosts you want to bypass the incoming bandwidth check. Separate each entry with a space.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-17 Movie Streamer General Settings Fields (continued) Field Description Enforce Maximum Outgoing Bitrate Enforces the maximum stream bit rate for serving content when checked. Maximum Outgoing Bitrate The maximum streaming bit rate that can be served in kilobytes per second (Kbps). The range is from 1 to 2147483647, depending on the hardware model.
Chapter 4 Configuring Devices Configuring the Service Engine Configuring RTSP Advanced Settings To configure RTSP advanced settings for the Movie Streamer, do the following: Step 1 Choose Devices > Devices > Application Control > RTSP Advanced Settings. The RTSP Advanced Settings page is displayed. Step 2 Enter the settings as appropriate. See Table 4-18 for a description of the fields.
Chapter 4 Configuring Devices Configuring the Service Engine Step 4 Click Submit to save the settings. To enable Flash Media Streaming Service Monitoring, do the following: Step 1 Choose Devices > Devices > Application Control > Flash Media Streaming > Service Monitoring. The Service Monitoring page is displayed. Step 2 Check the Enable Service Monitoring check box. Service Monitoring monitors the Flash Media Streaming engine memory usage. If the memory usage reaches the 1.
Chapter 4 Configuring Devices Configuring the Service Engine Figure 4-17 Step 2 HTTP Connections Page Enter the settings as appropriate. See Table 4-20 for a description of the fields. Table 4-20 HTTP Connections Fields Field Description Webengine Maximum Concurrent Connections The maximum concurrent sessions the Web engine supports. The range is from 100 to 6000. The default is 2000. Enable Incoming Proxy When enabled, accepts incoming requests on configured ports, in addition to port 80.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-20 Step 3 HTTP Connections Fields (continued) Field Description Username If authentication is required, enter a username. This username is used for both NTLM and basic authentication. Password Enter the password for the user. Confirm Password Re-enter the password for the user. NTLM User Domain The NTLM server domain name used to authenticate the user.
Chapter 4 Configuring Devices Configuring the Service Engine Step 3 Click Submit to save the settings. Configuring Web Engine HTTP Cache Freshness To configure the web engine HTTP cache freshness, do the following: Step 1 Choose Devices > Devices > Application Control > Web > HTTP > HTTP Cache Freshness. The HTTP Cache Freshness page is displayed (Figure 4-19). Figure 4-19 Step 2 HTTP Cache Freshness Page Enter the settings as appropriate. See Table 4-21 for a description of the fields.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-21 HTTP Cache Freshness Fields (continued) Field Description Max Object TTL The minimum time-to-live (TTL) for objects in cache. The valid ranges are as follows: 1 to 1825 days 1 to 43800 hours 1 to 2628000 minutes 1 to 157680000 seconds Step 3 Minimum TTL The minimum time-to-live (in minutes) for objects in the cache. The range is from 0 to 86400. The default value is 30.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-22 Advanced HTTP Caching Fields Field Description Enable Cache Cookies When enabled, the Web engine caches requests with a cookie header in the response. Enable Cache Fill Range When enabled, the complete content is cached when the range request for the same is given by the client. The range request starts with zero (0).
Chapter 4 Configuring Devices Configuring the Service Engine Step 1 Choose Devices > Devices > General Settings > Content Management. The Content Management page is displayed. Step 2 In the Max Cache Content Entries field, enter the value for the maximum entries of cached content allowed. The range is from 1 to 5000000. The default is 3000000. Step 3 Click Submit to save the settings.
Chapter 4 Configuring Devices Configuring the Service Engine Step 2 Enter the settings as appropriate. See Table 4-23 for a description of the fields. Table 4-23 Login Authentication Fields Field Description Enable Failover Server If Enable Failover Server Unreachable is enabled, the device fails over to Unreachable the secondary server only if the primary server is unreachable.
Chapter 4 Configuring Devices Configuring the Service Engine Note Step 5 Select the SSH version. a. To allow clients to connect using SSH protocol version 1, check the Enable SSHv1 check box. b. To allow clients to connect using SSH protocol version 2, check the Enable SSHv2 check box. Note Step 6 When changing the Login Grace Time, you need to first uncheck the Enable check box and click Submit. Enter the new Login Grace Time, check Enable, and click Submit.
Chapter 4 Configuring Devices Configuring the Service Engine Note In the Message of the Day (MOTD) Banner, EXEC Process Creation Banner, and Login Banner fields, you can enter a maximum of 980 characters. A new line character (or Enter) is counted as two characters, as it is interpreted as \n by the system. You cannot use special characters such as `, % ,^ , and " in the MOTD text.
Chapter 4 Configuring Devices Configuring the Service Engine To create, edit, or delete a user account, do the following: Step 1 Choose Devices > Devices > General Settings > Login Access Control > Users > Usernames. The User Table page is displayed. Step 2 Aggregate Settings is set to Yes by default. If this SE belongs to a device group, and the settings have not been configured using the device group, you can enter the settings and they will apply to the device group as well.
Chapter 4 Configuring Devices Configuring the Service Engine The Login Authentication page allows you to choose an external access server or the internal (local) device-based authentication, authorization, and accounting (AAA) system for user access management. You can choose one method or a combination of the two methods. The default is to use the local database for authentication. Configuring a RADlUS Server Note The CDSM does not cache user authentication information.
Chapter 4 Configuring Devices Configuring the Service Engine Configuring an Access Control List To configure an access control list (ACL) for group authorization, do the following: Step 1 Choose Devices > Devices > General Settings > Authentication > Access Control List > Configure Access Control List. The Access Control List Table page is displayed. Step 2 Click the Create New icon in the task bar. The Configure Access Control List page is displayed.
Chapter 4 Configuring Devices Configuring the Service Engine Step 2 Enter the settings as appropriate. See Table 4-27 for a description of the fields. Table 4-27 Field Database Maintenance Settings Fields Description Full Database Maintenance Settings Enable When enabled, a full database maintenance routine is performed on the SE. Every Day The days of the week when the maintenance is performed Sun-Sat When Every Day is enabled, all days of the week are also enabled.
Chapter 4 Configuring Devices Configuring the Service Engine Step 5 Check the Enable Disk Error Handling Threshold check box if you want to set the number of disk errors allowed before the disk is marked as bad, and enter a number (0 to 100) in the Threshold field. The default threshold is 10. Step 6 Click Submit to save the settings. Network Settings The Network pages provide settings for network connectivity.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-28 Step 3 DNS Settings Fields Field Description Enable Enables Domain Name System (DNS) on the SE. List of DNS Servers Space-delimited list of IP addresses for up to eight name servers for name and address resolution. Domain Names A space-delimited list of up to three default domain names. A default domain name allows the system to resolve any unqualified hostnames.
Chapter 4 Configuring Devices Configuring the Service Engine Setting the Time Zone If you have an outside source on your network that provides time services, such as an NTP server, you do not need to set the system clock manually. When manually setting the clock, enter the local time. The SE calculates Coordinated Universal Time (UTC) based on the time zone set. Note Caution Two clocks exist in the system: the software clock and the hardware clock. The software uses the software clock.
Chapter 4 Configuring Devices Configuring the Service Engine The start and end dates for summer time can be configured in two ways: absolute dates or recurring dates. Absolute dates apply once and must be reset every year. Recurring dates apply every year. a. Click the Absolute Dates radio button to configure summer settings once. b. In the Start Date and End Date fields, specify the month, day, and year that the summer time savings starts and ends in mm/dd/yyyy format.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-29 Time Zone—Offset from UTC (continued) Time Zone Offset from UTC (in hours) Time Zone Offset from UTC (in hours) Atlantic/Cape_Verde –1 Europe/Athens +2 Asia/Almaty +6 Europe/Berlin +1 Asia/Baghdad +3 Europe/Bucharest +2 Asia/Baku +4 Europe/Helsinki +2 Asia/Bangkok +7 Europe/London 0 Asia/Colombo +6 Europe/Moscow +3 Asia/Dacca +6 Europe/Paris +1 Asia/Hong_Kong +8 Europe/Prague +1 Asia/Irkutsk +8 E
Chapter 4 Configuring Devices Configuring the Service Engine Step 1 Choose Devices > Devices > General Settings > Network > External IP. The External IP Settings page is displayed. Step 2 Check the Enable check box. Step 3 In the External IP Address fields (1–8), enter up to eight IP addresses. Step 4 Click Submit to save the settings.
Chapter 4 Configuring Devices Configuring the Service Engine Step 1 Choose Devices > Devices > General Settings > Network > TCP. The TCP Settings page is displayed. Step 2 Enter the settings as appropriate. See Table 4-30 for a description of the fields. Table 4-30 TCP Settings Fields Field Description TCP General Settings Enable Explicit Congestion Notification Enables reduction of delay and packet loss. For more information, see the “Explicit Congestion Notification” section on page 4-65.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-30 TCP Settings Fields (continued) Field Description TCP Client Settings Enable Client Satellite Sets client TCP compliance to the RFC 1323 standard. For more information, see the “TCP-Over-Satellite Extensions” section on page 4-66. Note If you enable a client satellite, the server satellite is automatically enabled. Client Max Segment Size Maximum packet size sent to clients. The default is 1432 bytes.
Chapter 4 Configuring Devices Configuring the Service Engine Step 3 Click Submit to save the settings. Explicit Congestion Notification The TCP Explicit Congestion Notification (ECN) feature allows an intermediate router to notify the end hosts of impending network congestion. It also provides enhanced support for TCP sessions associated with applications that are sensitive to delay or packet loss, including Telnet, web browsing, and transfer of audio and video data.
Chapter 4 Configuring Devices Configuring the Service Engine (Initially, the value of the ssthresh variable is adjusted to the receiver’s maximum window size [RMSS]. However, when congestion occurs, the ssthresh variable is set to half the current value of the cwnd variable, marking the point of the onset of network congestion for future reference.
Chapter 4 Configuring Devices Configuring the Service Engine Step 3 Click Submit to save the settings. Configuring IP ACL Note This is a Release 2.1 feature. Access control lists (ACLs) provide a means to filter packets by allowing a user to permit or deny IP packets from crossing specified interfaces. Packet filtering helps to control packet movement through the network. Such control can help limit network traffic and restrict network use by certain users or devices.
Chapter 4 Configuring Devices Configuring the Service Engine • When the IP ACL name is numeric, numbers 1 through 99 denote standard IP ACLs and numbers 100 through 199 denote extended IP ACLs. IP ACL names that begin with a number cannot contain nonnumeric characters. • Extended IP ACLs cannot be used with SNMP applications. Creating a New IP ACL To create a new IP ACL, do the following: Step 1 Choose Devices > Devices > General Settings > Network > IP ACL. The IP ACL Table page is displayed.
Chapter 4 Configuring Devices Configuring the Service Engine d. Click Submit. The Modifying IP ACL page is displayed showing the new condition and its configuration. e. To add another condition to the IP ACL, repeat the steps. f. To reorder your list of conditions in the Modifying IP ACL page, use the Up arrow or Down arrow in the Order column, or click a column heading to sort by any configured parameter. Note g.
Chapter 4 Configuring Devices Configuring the Service Engine g. When you have finished adding conditions to the IP ACL, and you are satisfied with all your entries and the order in which the conditions are listed, click Submit in the Modifying IP ACL page to commit the IP ACL to the device database. A green “Change submitted” indicator appears in the lower right corner of the Modifying IP ACL page to indicate that the IP ACL is being submitted to the device database.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-33 Extended IP ACL Conditions (continued) Field Default Value Description Extended Type Destination IP 0.0.0.0 IP address of the network or host to which the packet is being sent, specified as a 32-bit quantity in 4-part dotted decimal format. Generic, TCP, UDP, ICMP Destination IP Wildcard 255.255.255.255 Wildcard bits to be applied to the source, specified as a 32-bit quantity in 4-part dotted decimal format.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-33 Extended IP ACL Conditions (continued) Field Use ICMP Code ICMP Code 1 1 Default Value Description Extended Type Unchecked When checked, enables the ICMP Code field. ICMP 0 Number from 0 to 255. Message code option that allows ICMP ICMP messages of a particular type to be further filtered by an ICMP message code. 1. Required field. Table 4-34 lists the UDP keywords that you can use with extended access control lists.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-36 Keywords for ICMP Message Type and Code Message Description administratively-prohibited Messages that are administratively prohibited from being allowed access. alternate-address Messages that specify alternate IP addresses. conversion-error Messages that denote a datagram conversion error. dod-host-prohibited Messages that signify a Department of Defense (DoD) protocol Internet host denial.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-36 Keywords for ICMP Message Type and Code (continued) Message Description option-missing Messages that specify the requirement of a parameter, but that parameter is not available. packet-too-big Messages that specify that the ICMP packet requires fragmentation but the Do Not Fragment (DF) bit is set. parameter-problem Messages that signify parameter-related problems.
Chapter 4 Configuring Devices Configuring the Service Engine To reorder your list of conditions, use the Up arrow or Down arrow in the Order column, and click Submit. Applying an IP ACL to an Interface The IP ACLs can be applied to a particular interface (such as management services to a private IP address) so that the SE can have one interface in a public IP address space that serves content and another interface in a private IP address space that the administrator uses for management purposes.
Chapter 4 Configuring Devices Configuring the Service Engine Step 3 In the Destination Network Address field, enter the destination network IP address. Step 4 In the Netmask field, enter the destination host netmask. Step 5 In the Gateway’s IP Address field, enter the IP address of the gateway interface. Step 6 Click Submit to save the settings.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-37 Viewing SE Alarms (continued) Command Syntax Description show alarms history Displays a history of alarms that have been raised and cleared on the SE. The CLI retains the last 100 alarm raise and clear events only. show alarms status Displays the counts for the currently raised alarms on the SE. Also lists the alarm-overload state and the alarm-overload settings.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-38 Service Monitor Fields (continued) Field Description Sample Period Time interval (in seconds) between two consecutive samples. The sample period is the time during which the SE and the SR exchange keep-alive messages that contain the SE load information. The range is from 1 to 60. The default is 5. Number of Samples Number of most recently sampled values used when calculating the average. The range is from 1 to 120.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-38 Service Monitor Fields (continued) Field Description Sample Period Time interval (in seconds) between two consecutive samples. The range is from 1 to 60. The default is 5. Number of Samples Number of most recently sampled values used when calculating the average. The range is from 1 to 120. The default is 6. Movie Streamer Settings1 Enable Allows the SR to collect stream count information from the SE.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-39 Field SNMP General Settings Fields Description Traps Enable SNMP Settings Enables the SNMP agent to transmit traps to the SNMP server. Service Engine Enables SNMP traps: SNMP SE Alarm • Disk Read—Enables disk read error trap. • Disk Write—Enables disk write error trap. • Disk Fail—Enables disk failure error trap. • Transaction Logging—Enables transaction log write error trap.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-40 SNMP Community Fields Field Description Community Community string used as a password for authentication when you access the SNMP agent of the SE. The “Community Name” field of any SNMP message sent to the SE must match the community string defined here in order to be authenticated. You can enter a maximum of 64 characters in this field. Group name/rw Group to which the community string belongs.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-41 SNMP Group Fields (continued) Field Description Write View Name of the view (a maximum of 64 characters) that enables you to enter data and configure the contents of the agent. By default, no view is defined. Notify View Name of the view (a maximum of 64 characters) that enables you to specify a notify, inform, or trap. By default, no view is defined. Step 11 Click Submit to save the settings.
Chapter 4 Configuring Devices Configuring the Service Engine Step 15 Click Submit to save the settings. Step 16 To define a SNMPv2 MIB view, click View from the left-panel menu. The SNMP View Table page is displayed. The maximum number of SNMPv2 views that can be created is ten. Step 17 Click the Create New icon in the task bar. The SNMP View page is displayed. Click the Edit icon next to the username to edit a view. Step 18 Enter the settings as appropriate.
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-44 SNMP Host Fields (continued) Field Description Retry Number of retries (1 to 10) allowed for the inform request. The default is 2. Timeout Timeout for the inform request in seconds (1 to 1000). The default is 15. Step 23 Click Submit to save the settings. Step 24 From the left-panel menu, click Asset Tag. The SNMP Asset Tag page is displayed. Step 25 In the Asset Tag Name field, enter a name for the asset tag.
Chapter 4 Configuring Devices Configuring the Service Engine Note If your browser is located behind a firewall or you are connecting to the Internet with a DSL modem and you are unable to access this file folder, you must change your web browser compatibility settings. In the Internet Explorer (IE) web browser, choose Tools > Internet Options > Advanced, and check the Use Passive FTP check box. Enabling System Logs Use the System Logs page to set specific parameters for the system log file (syslog).
Chapter 4 Configuring Devices Configuring the Service Engine Table 4-45 Field System Logs Settings Fields (continued) Description Host Settings Step 3 Enable Enables sending the system log file to a host. You can configure up to four hosts. Hostname A hostname or IP address of a remote syslog host. Priority Severity level of the message that should be sent to the specified remote syslog host. Port The destination port on the remote host. The default is 514.
Chapter 4 Configuring Devices Configuring the Service Router The keep-alive interval is used by the SE to send keep-alive messages to the SR. To configure the keep-alive interval the SE uses for messages to this SR, do the following: Step 1 Choose Devices > Devices > General Settings > Service Routing Settings. The Service Routing Settings page is displayed. Step 2 In the Keepalive-Interval field, enter the number of seconds the messages from the SR should be kept alive on this SE.
Chapter 4 Configuring Devices Configuring the Service Router Table 4-46 Service Router Activation Fields (continued) Field Description Coverage Zone File To have a local Coverage Zone file overwrite the CDS network-wide Coverage Zone file, choose a file from the Coverage Zone drop-down list. See the “Coverage Zone File Registration” section on page 6-9 for information about creating and registering a Coverage Zone file. Otherwise, choose None.
Chapter 4 Configuring Devices Configuring the Service Router Table 4-47 Service Router Routing Settings Fields Field Description Least Loaded Routing Note This is a Release 2.0 and Release 2.1 feature. In Release 2.2 and Release 2.3, Least Loaded Routing is enabled by default. When enabled, the SR redirects the client request to the SE that reports the lowest average load, given that each SE in the routing table has the same metric value (weight).
Chapter 4 Configuring Devices Configuring the Service Router Step 3 Click Submit to save the settings. IP-Based Redirection Note IP-based redirection is a Release 2.3 feature. IP-based redirection uses IP addresses to route client requests to the SR and on to the SE. For more information, see the “IP-Based Redirection” section on page 1-20. To enable IP-based redirection, do the following: Step 1 Choose Devices > Devices > IP-based Redirection. The IP-based Redirection page is displayed.
Chapter 4 Configuring Devices Configuring the CDSM General Settings—Last Resort For information on configuring all general settings, except Last Resort, see the “General Settings” section on page 4-48. Note This is a Release 2.1 feature. To configure last resort routing for Release 2.0, see the “Configuring Last-Resort Routing” section on page E-6.
Chapter 4 Configuring Devices Configuring the CDSM Cisco Internet Streamer CDS 2.0-2.
CH A P T E R 5 Configuring Services This chapter provides information on configuring the CDS. This chapter covers the following major topics: • Configuring Delivery Services, page 5-1 • Configuring Programs, page 5-26 • Viewing Programs, page 5-39 • Copying a Program, page 5-41 Configuring Delivery Services Delivery services are configured for prefetch ingest, hybrid ingest, and live programs.
Chapter 5 Configuring Services Configuring Delivery Services To create a Content Origin, do the following: Step 1 Choose Services > Service Definition > Content Origins. The Content Origin Table page is displayed (Figure 5-1). Figure 5-1 Step 2 Content Origin Table Page Click the Create New icon in the task bar. The Content Origin page is displayed (Figure 5-2). Cisco Internet Streamer CDS 2.0-2.
Chapter 5 Configuring Services Configuring Delivery Services Figure 5-2 Content Origin Page To edit a Content Origin, click the Edit icon next to the Content Origin name. Step 3 Enter the settings as appropriate. See Table 5-1 for a description of the fields. Table 5-1 Content Origin Fields Field Description Name Unique name of the origin server. Origin Server Fully qualified domain name (FQDN) of the origin server. Service Routing Domain Name The FQDN to route client requests.
Chapter 5 Configuring Services Configuring Delivery Services Step 4 Click Submit to save the settings. To delete a Content Origin, from the Content Origin Table page, click the Edit icon next to the Content Origin you want to delete, and click the Trash icon in the task bar. Creating Delivery Service A delivery service is a configuration used to define how content is acquired, distributed, and stored in advance of a client request.
Chapter 5 Configuring Services Configuring Delivery Services Figure 5-3 Step 3 Delivery Service Definition Page Enter the settings as appropriate. See Table 5-2 for a description of the fields. Table 5-2 Delivery Service Definition Fields Field Description Delivery Service Information Name Unique name for the delivery service. Content Origin All Content Origins that have been created are listed in the drop-down list. The delivery service and the Content Origin have a one-to-one relationship.
Chapter 5 Configuring Services Configuring Delivery Services Table 5-2 Delivery Service Definition Fields (continued) Field Description Acquisition and Distribution Properties Distribution Priority Content distribution priority setting. Options are High, Normal, and Low. The default is Normal. The priority of content acquisition also depends on the origin server. Requests from different origin servers are processed in parallel.
Chapter 5 Configuring Services Configuring Delivery Services Note Step 5 Use either Assign Service Engines, or Assign Device Groups to assign Service Engines and select a Content Acquirer. From the left-panel menu, click Assign Service Engines. The Service Engine Assignment page is displayed (Figure 5-4). Figure 5-4 Step 6 Service Engine Assignment Page Click the Assign icon (blue cross mark) next to the SE you want to assign to this delivery service.
Chapter 5 Configuring Services Configuring Delivery Services A green circle with a check mark indicates an SE is assigned to this delivery service. To unassign the SE, click this icon, or click Unassign All Service Engines in the task bar. Click Submit to save the changes. Note To view all the Service Engines assigned to the delivery service, in the left-panel menu, click List assigned Service Engines. PCMM Configuration Step 9 From the left-panel menu, click PCMM Config.
Chapter 5 Configuring Services Configuring Delivery Services Table 5-3 PCMM Configuration Fields (continued) Field Description WMT Streaming When checked, an HTTP callout to the policy server is done for each stream request. Progressive Download When checked, an HTTP callout to the policy server is done for each download request.
Chapter 5 Configuring Services Configuring Delivery Services This option disables all HTTP-based content serving from this delivery service. The Web Engine will return a 403 forbidden message.
Chapter 5 Configuring Services Configuring Delivery Services Table 5-4 Session Shifting Fields (continued) Field Description Content File Subscriber File For each session shifting file, click the Browse button to locate each XML file. The Choose File dialog box is displayed. Navigate to the file and click Open. Profile File To remove a file, click the Trash icon next to the file type. To view the file, click List.
Chapter 5 Configuring Services Configuring Delivery Services • Select individual items by performing a quick crawl, and select the items from the crawl result list to be included in the content list. For more information about the crawler feature, see the “Crawling” section on page 2-5. To identify content for acquisition using the CDSM, do the following: Step 1 Choose Services > Service Definition > Delivery Services > Delivery Service Content.
Chapter 5 Configuring Services Configuring Delivery Services Figure 5-8 Content Manager Page To edit a content item, click the Edit icon next to the content. For more information about manipulating the content items in the Content Table page, see the “Configuring Proxy Server Settings” section on page 5-21. Step 3 Choose a protocol from the Source URL drop-down list, and enter the source URL in the associated field.
Chapter 5 Configuring Services Configuring Delivery Services The crawler feature starts with the Source URL, identifies every web link in the page, and adds every link to the list of URLs to search, until the links have been followed to the specified depth. The Link Depth field specifies how many levels of a website to crawl or how many directory levels of an FTP server to search. This is optional. The range is –1 to 2147483636. If the depth is –1, there is no depth constraint.
Chapter 5 Configuring Services Configuring Delivery Services Figure 5-9 Step 4 Enter the settings as appropriate. See Table 5-5 for a description of the fields. Table 5-5 Step 5 Content Manager Page—Acquisition Rules Fields Acquisition Rule Fields Field Description MIME Type A content item qualifies for acquisition only if its MIME type matches this MIME type (for example, video/mpeg). Extension A content item is acquired only if its extension matches this extension.
Chapter 5 Configuring Services Configuring Delivery Services A maximum of ten rules can be configured for each crawl task. Note To modify a content acquisition rule, click the Edit icon next to the rule. Once you have finished, click the small Update button in the content acquisition rules section to save the edits. To delete a content acquisition rule, click the Edit icon next to the rule. Click the Delete button in the content acquisition rules section. The rule is removed from the rules listing.
Chapter 5 Configuring Services Configuring Delivery Services Table 5-6 Step 3 Quick Crawl Filter Fields (continued) Field Description Max Item Count The maximum number of content items that is listed in the results. The maximum value is 1000. Domain The host.domain portion of the source URL. Edit this field to limit the search to a specific host on a domain. Username The username to log in to host servers that require authentication. Password The password for the user account.
Chapter 5 Configuring Services Configuring Delivery Services Figure 5-10 Step 2 Content Manager Page—Advanced Settings Fields Enter the settings as appropriate. See Table 5-7 for a description of the fields. Table 5-7 Advanced Settings for Serving Content Field Description Content Serving Time High Priority Content Specifies the importance, and therefore the processing order, of the item acquisition or crawl task. Start Serving Time Specifies the time for the SE to start delivering content.
Chapter 5 Configuring Services Configuring Delivery Services Table 5-7 Advanced Settings for Serving Content (continued) Field Description Stop Serving Time Specifies the time for the SE to stop delivering content. Use the dd-mm-yyyy hh:mm:ss [TMZ] format, where TMZ (the time zone) is optional. UTC is the default. Alternatively, click the Calendar icon to choose a date from the calendar and enter a time, and click Apply.
Chapter 5 Configuring Services Configuring Delivery Services Step 3 Click Submit to process the content request. When you click Submit, the local Manifest file for this delivery service is automatically reparsed, changes are detected, and the corresponding items are acquired or removed. This action, however, does not trigger a recheck of all the content in the delivery service.
Chapter 5 Configuring Services Configuring Delivery Services change the content acquisition method, any content items that you added are removed. For information about the Manifest file, see the “Identifying Content Using a Manifest File” section on page 5-22 and Appendix B, “Creating Manifest Files.” To edit multiple content items, check the check box next to each item you want to edit, and click Edit Selected Items.
Chapter 5 Configuring Services Configuring Delivery Services Table 5-8 Proxy Server Fields (continued) Field Description Disable Basic Authentication When checked, NTLM headers cannot be stripped off that would allow fallback to the basic authentication method.
Chapter 5 Configuring Services Configuring Delivery Services d. In the confirmation dialog box, click OK. The Content Manager page displays the Manifest file settings (Figure 5-12). Note When you change the content acquisition method from Use the GUI to specify content acquisition to Specify external Manifest file for an existing delivery service, any content items that you added using the CDSM are removed. To save the existing settings, click the Save Settings Locally icon in the task bar.
Chapter 5 Configuring Services Configuring Delivery Services Table 5-9 Manifest File Settings Fields (continued) Field Description Check Manifest Every Frequency in minutes (0 to 52560000) at which the Content Acquirer assigned to the delivery service checks for updates to the Manifest file. To fetch the Manifest file now, click Fetch Manifest Now. Weak Certificate Verification When checked, enables weak certificate verification for fetching the Manifest file.
Chapter 5 Configuring Services Configuring Delivery Services Table 5-9 Field Description Disable Proxy Basic Authentication When checked, NTLM headers will not be stripped off to allow fallback to the basic authentication method against Microsoft Internet Information Services (IIS) servers. Proxy NTLM User Domain Name NTLM user domain name to be allowed access by the NTLM authentication scheme configured on the proxy.
Chapter 5 Configuring Services Configuring Programs Configuring Programs A program in the CDS is defined as a scheduled live or rebroadcast event that streams content to client devices. The CDS streams live or rebroadcast content by using the Movie Streamer or the Windows Media Engine. For more information, see the “Programs” section on page 2-9. To view existing programs, see the “Viewing Programs” section on page 5-39.
Chapter 5 Configuring Services Configuring Programs Defining a Program To define a live or rebroadcast program, do the following: Step 1 Choose Services > Live Video > Live Programs. The Program Table page is displayed. Step 2 Click the Create New icon in the task bar. The Program Definition page is displayed. To edit an existing program, click the Edit icon next to the program name. Step 3 In the Name field, enter a unique name for the program.
Chapter 5 Configuring Services Configuring Programs c. Step 3 Click Submit to save the settings. From the left-panel menu, choose Assign Service Engines. The Service Engine Assignment page is displayed (Figure 5-13). Figure 5-13 Step 4 Service Engine Assignment Page Click the Assign icon (blue cross mark) next to the SE you want to assign to this delivery service. Or, in the task bar, click the Assign All Service Engines icon. The SE assignment states are described in Figure 5-14.
Chapter 5 Configuring Services Configuring Programs Step 8 In the left-panel menu, choose Live Streaming. The Live Stream Settings page is displayed. The Live Stream Setting page differs depending on whether you are configuring a Movie Streamer live stream or a Windows Media live stream. Step 9 Enter the settings as appropriate. See Table 5-10 for a description of the Windows Media Live Stream Settings fields, and Table 5-11 for a description of the Movie Streamer Live Stream Settings fields.
Chapter 5 Configuring Services Configuring Programs Table 5-10 Windows Media Live Stream Settings Fields (continued) Field Description Customized URL Note This is a Release 2.0 feature. This field is available when the Customized Reference URL is selected in the Multicast URL Reference field. Use the following format for the custom URL for multicast: http://any SEinLiveDeliveryService/customized-name.
Chapter 5 Configuring Services Configuring Programs Table 5-11 Movie Streamer Live Stream Settings Fields Field Description Origin Server SDP File URL The URL for the Session Description Protocol (SDP) file generated on the encoder. From the drop-down list, select either rtsp or http, and enter the remainder of the URL in the field. The remainder of the URL format is host [:port]/[filename], where the port and filename are optional.
Chapter 5 Configuring Services Configuring Programs Table 5-11 Movie Streamer Live Stream Settings Fields (continued) Field Description Unicast URL Reference This field is auto-populated with a list of suggested URLs by using the Origin Server and the Service Routing Domain Name fields associated with the live delivery service. Choose one from the drop-down list. Customized URL Note This is a Release 2.0 feature.
Chapter 5 Configuring Services Configuring Programs Table 5-11 Movie Streamer Live Stream Settings Fields (continued) Field Description Content Acquirer Port The port number on the Content Acquirer that will receive the stream. Note Multicast Address and Port To activate failover support for the Content Acquirer, you must enter zero (0). The multicast address and port to use for streaming this program using multicast. The address range is 224.0.0.0 to 239.255.255.255.
Chapter 5 Configuring Services Configuring Programs Step 14 Click Submit to save the settings. Click Add Playtime to add additional playtimes to an existing schedule. The Playtime Editor is displayed in the page. Priming a Live Delivery Service The first client requesting a program often experiences the longest wait time for the program to begin playing. Users can experience long wait times because of the full RTSP negotiation that is required to pull the live stream from the source.
Chapter 5 Configuring Services Configuring Programs To choose a new delivery service to choose files from, click All Delivery Services, choose a delivery service, and click Show Media in Selected Delivery Service. Step 4 Check the Pick check box next to each file you want to rebroadcast and click Add Media. The files are displayed in the Media Files in Program pane. To select all files, click All. To deselect all files, click None. The file list can span several pages.
Chapter 5 Configuring Services Configuring Programs A green circle with a check mark indicates an SE is assigned to this delivery service. To unassign the SE, click this icon, or click the Unassign All Service Engines in the task bar. Click Submit to save the changes. Step 12 From the left-panel menu, choose Streaming. The Streaming Settings page is displayed. Step 13 Enter the settings as appropriate.
Chapter 5 Configuring Services Configuring Programs Table 5-14 Movie Streamer Rebroadcast Stream Settings Fields Field Description Multicast URL Reference This field is auto-populated with a list of suggested URLs by using the Origin Server and the Service Routing Domain Name fields associated with the rebroadcast. Choose one from the drop-down list. Customized URL Note The Content Acquirer port must be zero (0) if the source is multicast push. Note This is a Release 2.0 feature.
Chapter 5 Configuring Services Configuring Programs Table 5-15 Playtime Fields Field Description Start Playback on The start date and time for the program. UTC or SE (Local) Time Which clock the start time should use, UTC or SE local. Duration The length of the program. In the drop-down list, choose minutes, hours, or days as the unit of time.
Chapter 5 Configuring Services Viewing Programs Step 2 In the Start Address field, specify the first multicast IP address in the pool. The range is 224.0.0.0 to 239.255.255.255. Step 3 In the End Address field, specify the last multicast IP address in the pool. The range is 224.0.0.0 to 239.255.255.255. Step 4 In the TTL field, specify the time-to-live (number of hops) for all addresses configured in the pool. The range is 1 to 255. Step 5 Click Submit to save your settings.
Chapter 5 Configuring Services Viewing Programs Table 5-16 Programs Table Page Information (continued) Item Description Program Listing Table Program Program name, which must be unique to the CDSM. Type Program type. Program types are: Schedule • Movie Streamer live • Movie Streamer rebroadcast • Windows Media live • Windows Media rebroadcast Describes the schedule.
Chapter 5 Configuring Services Copying a Program Previewing a Program You can preview live programs by live split or by joining a multicast broadcast. Live programs can only be viewed during the scheduled playtime. You can preview a rebroadcast program by joining the multicast broadcast during the scheduled playtime. To preview a live Movie Streamer or Windows Media program or scheduled rebroadcast, follow these steps: Step 1 Choose Services > Live Video > Live Programs.
Chapter 5 Configuring Services Copying a Program Note You cannot change the program type. Step 5 Click Submit to save the settings. Step 6 Edit any of the other program properties found in the left-panel menu, such as the program schedule, program, or device assignments. Cisco Internet Streamer CDS 2.0-2.
CH A P T E R 6 Configuring the System This chapter provides information on configuring the system parameters of the CDS. This chapter has the following major topics: • Configuring AAA, page 6-1 • Changing a Password, page 6-5 • Configuring System Settings, page 6-6 Configuring AAA Authentication determines who the user is and whether that user should be allowed access to the network or a particular device. It allows network administrators to bar intruders from their networks.
Chapter 6 Configuring the System Configuring AAA privileges. The user account information is stored in the AAA database. When the user attempts to log in, the CDSM compares the person’s username, password, and privilege level to the user account information that is stored in the database. Each user account can be assigned to a role and a domain. A role defines which CDSM configuration pages the user can access and which services the user has authority to configure or modify.
Chapter 6 Configuring the System Configuring AAA Note The User Account page can only be accessed by users with administrator-level privileges. Step 3 In the Username field, enter the user account name. Step 4 If you want to create a local user account with a password and privilege level from the CDSM, check the Create CLI User check box. The user account is created automatically in the CLI. To prevent the creation of a CLI user account from the GUI, leave the check box unchecked.
Chapter 6 Configuring the System Configuring AAA Note Deleting a user account from the CLI does not delete the corresponding account in the CDSM database. User accounts created in the CDSM should always be deleted from within the CDSM. Creating, Editing, and Deleting Roles Although the CDSM provides many types of services, not all users have access to all services. Users are assigned a role, which indicates the services to which they have access. A role is a set of enabled services.
Chapter 6 Configuring the System Changing a Password To create or edit a domain, follow these steps: Step 1 Choose System > AAA > Domains. The Domains Table page is displayed. Step 2 Click the Create New icon in the task bar. The Domain page is displayed. To edit a domain, click the Edit icon next to the domain name. Step 3 In the Name field, enter the name of the domain. Step 4 From the Entity Type drop-down list, choose Service Engines, Device Groups, or Delivery Services.
Chapter 6 Configuring the System Configuring System Settings Step 3 In the Confirm New Password field, re-enter the password for confirmation. Step 4 Click Submit to save the settings.
Chapter 6 Configuring the System Configuring System Settings Table 6-1 System Properties Fields (continued) Field Description System.monitoring.enable SE statistics monitoring (enable or disable). System.monitoring.monthly ConsolidationFrequency Frequency (in days) with which the CDSM consolidates daily monitoring records into monthly records. System.monitoring.record LimitDays Maximum number of days of monitoring data to maintain in the system. System.repstatus.
Chapter 6 Configuring the System Configuring System Settings To configure Fast Detection of Offline SEs, do the following: Step 1 Choose System > Configuration > Fast SE Offline Detection. The Configure Fast SE Offline Detection page is displayed. Note Step 2 The Fast Detection of Offline SEs feature is in effect only when the CDSM receives the first UDP heartbeat packet and a getUpdate request from an SE. Check the Enable check box to enable the CDSM to detect the offline status of SEs quickly.
Chapter 6 Configuring the System Configuring System Settings Step 2 Check the Set QoS for Unicast Data check box to enable system-wide QoS settings for unicast data. Step 3 Set the QoS value for each priority by choosing the Differentiated Service Code Point (DSCP) value from the QoS value drop-down list or by entering a decimal value in the corresponding field. Step 4 Check the Set QoS Value for Metadata Replication check box to enable QoS settings for metadata replication.
Chapter 6 Configuring the System Configuring System Settings Note If you apply a Coverage Zone file locally for a device, this file overwrites the global Coverage Zone file for that device. To register a Coverage Zone file, follow these steps: Step 1 Choose System > Configuration > Service Routing > Coverage Zone File Registration. The Coverage Zone File Table page is displayed. Step 2 Click the Create New icon in the task bar. The Registering Coverage Zone File page is displayed.
Chapter 6 Configuring the System Configuring System Settings Table 6-3 Import Method for Coverage Zone Files Property Description NTLM user Domain NT LAN Manager (NTLM) user domain name for NTLM authentication. Disable Basic Authentication When checked, NTLM headers cannot be stripped off to allow fallback to the basic authentication method.
Chapter 6 Configuring the System Configuring System Settings Cisco Internet Streamer CDS 2.0-2.
CH A P T E R 7 Monitoring the Internet Streamer CDS The CDSM provides tools that can be used for system monitoring and system diagnostics.
Chapter 7 Monitoring the Internet Streamer CDS System Monitoring When you roll your mouse over an alarm light in the System Status bar, a pop-up message provides further details about the device or delivery service status. See Figure 7-1. Figure 7-1 System Status Bar When you click the alarm light, a troubleshooting window opens (Troubleshooting Devices or Troubleshooting Service), listing the individual devices or delivery services that need attention.
Chapter 7 Monitoring the Internet Streamer CDS System Monitoring Troubleshooting Devices Using the System Status Bar To troubleshoot a device from the System Status bar, do the following: Step 1 In the System Status bar, click the Devices alarm light or click the Device link. The Troubleshooting Devices window is displayed. Step 2 In the Alarm Information column, hold your mouse over the alarm message until the Troubleshooting Tools menu is displayed. See Figure 7-2.
Chapter 7 Monitoring the Internet Streamer CDS System Monitoring Step 3 Click the troubleshooting tool that you want to use. The link takes you to the corresponding page in the CDSM. Table 7-4 describes the tools available for all service alarms. Table 7-4 Troubleshooting Tools for Content Alarms Item Navigation Description View Replication Status Services > Delivery Services > Replication Status Displays second-level replication status for a delivery service.
Chapter 7 Monitoring the Internet Streamer CDS System Monitoring The information displayed in the graphs is based on a snapshot of your CDS network and represents the state of your SEs at the end of every two polling periods. You can change the interval between polls by changing the System.datafeed.pollRate field in System > Configuration > System Properties. The default polling rate is 300 seconds (5 minutes).
Chapter 7 Monitoring the Internet Streamer CDS Device Monitoring Step 2 To determine the number of rows that you want to display, choose a number from the Rows drop-down list. Device Monitoring This section covers the following topics: • Devices Table • Device Home Page • Using show and clear Commands • CPU Utilization For more detailed statistics on HTTP, Web Media, Movie Streamer, and Flash Media Streaming traffic, see the “Viewing Statistics” section on page 7-27.
Chapter 7 Monitoring the Internet Streamer CDS Device Monitoring Table 7-5 Device Table Columns Column Heading Description Device Name Host name of the device. Type Device type: SE, SR, CDSM (Primary), CDSM (Secondary) IP Address Primary IP address of the device. Status Status is one of the following: • Online—Device has been activated through the CDSM and is able to send and receive data and control traffic. • Offline—Device has failed to communicate with the CDSM.
Chapter 7 Monitoring the Internet Streamer CDS Device Monitoring Figure 7-6 SE Device Home Page The Bytes Served by Service Engine and the Bandwidth Efficiency Gain graphs are also displayed. For more information, see the “Reports” section on page 7-14. The Device home page for an SE or an SR provides several task bar options. Table 7-6 describes these options. The CDSM home page has a subset of the task bar options.
Chapter 7 Monitoring the Internet Streamer CDS Device Monitoring Using show and clear Commands The show and clear commands offer more detailed monitoring of the device. Table 7-7 lists only the show command parameters where arguments are required or are optional. Table 7-8 lists only the clear command parameters where arguments are required. A full list of the show and clear commands is available from the drop-down list on the respective page.
Chapter 7 Monitoring the Internet Streamer CDS Device Monitoring Table 7-7 show Command Arguments (continued) show Command Arguments Device cms {database {content {dump filename | text | xml} | maintenance [detail]} | info | processes} SE, SR, CDSM content all | url SE device-mode {configured | current} SE, SR, CDSM disks [current | details | failed-sectors [disk_name] | raid-state | SMART-info [details] ] SE, SR, CDSM distribution [delivery-services [delivery-service-id delivery-servic
Chapter 7 Monitoring the Internet Streamer CDS Device Monitoring Table 7-7 show Command Arguments (continued) show Command Arguments Device processes [cpu | debug pid | memory | system [delay 1-60 | count 1-100]] SE, SR, CDSM proxy-protocols outgoing-proxy SE rea agent SE rtsp {gateway} SE rule {action {action-type | all} [protocol {http | rtsp}] | all | pattern-list {1-512 pattern-type | all}} SE service-router On SE: {keepalive-interval | service-monitor} SE, SR On SR: [content-bas
Chapter 7 Monitoring the Internet Streamer CDS Device Monitoring Table 7-7 show Command Arguments (continued) show Command Arguments Device statistics icap SE, SR, CDSM icmp ip movie-streamer {all | bw-usage | errors | performance | requests | rule} netstat qos {policy} radius replication rtsp server1 services service-router {all | content-origin {content-origin} | dns | history | keepalive | se {se-name} | summary} snmp tcp transaction-logs udp wmt {all | bytes [incoming | outgoing] | cache | er
Chapter 7 Monitoring the Internet Streamer CDS Device Monitoring Table 7-8 clear Command Arguments clear Command Arguments Device cache [all | content {1-1000000}] SE content url url SE ip access-list counters 1-99 SE, SR, CDSM statistics {access-lists 300 | all | authentication | SE, SR, CDSM bandwidth advanced errors | distribution {all | metadata-receiver | metadata-sender | unicast-data-receiver | unicast-data-sender} | history | http {all | ims | object | pcmm | requests | rule} | icap
Chapter 7 Monitoring the Internet Streamer CDS Reports To export the report to a CSV (comma-separated value) file, click the Export icon in the task bar. A dialog box is displayed. Choose either Open or Save. If you choose Open, the tabular report is displayed in a new browser window. If you choose Save, you are prompted to choose a location where to save the file. The file can be opened with any spreadsheet program. To print the report, click the Print icon in the task bar.
Chapter 7 Monitoring the Internet Streamer CDS Reports To export the report to a CSV (comma-separated value) file, click the Export icon in the task bar. A dialog box is displayed. Choose either Open or Save. If you choose Open, depending on your browser, the tabular report is displayed in either a new browser window or the same browser window. If you choose Save, you are prompted to choose a location where to save the file. The file can be opened with any spreadsheet program.
Chapter 7 Monitoring the Internet Streamer CDS Reports Table 7-11 describes the report settings. Table 7-11 Tip Bandwidth Efficiency Gain Report Settings Field Description Series The series options are In, Out, and Efficiency Gain. The In option creates a graph for bandwidth used for incoming data. The Out option is for outgoing data, and Efficiency Gain is the combination of the two. Chart Size The chart display size choices are small, medium, or large.
Chapter 7 Monitoring the Internet Streamer CDS Delivery Service Monitoring Table 7-12 Streaming Sessions Report Settings (continued) Field Description Time Zone The time zone choices are SE local time, CDSM local time, or UTC. Custom Date Range The custom date range is used when Time Frame is set to custom. Enter the dates, beginning and end, for the chart in the mm/dd/yyyy format, or choose the dates by using the calendar icons.
Chapter 7 Monitoring the Internet Streamer CDS Delivery Service Monitoring Figure 7-7 Step 2 Delivery Services Table Page View the replication status information for each delivery service. Table 7-13 describes the status information that is displayed on this page. Table 7-13 System-Wide Replication Status by Delivery Service Column Heading Description Delivery Service Name of the delivery service. Type Type of delivery service. The delivery service types are Live and Content.
Chapter 7 Monitoring the Internet Streamer CDS Delivery Service Monitoring Table 7-13 System-Wide Replication Status by Delivery Service (continued) Column Heading Description State State of the delivery service. States are reported for the Content Acquirer and for receiver SEs. (See Table 7-15 for a definition of the different delivery service states.
Chapter 7 Monitoring the Internet Streamer CDS Delivery Service Monitoring Table 7-15 defines the different delivery service states. Table 7-15 Delivery Service States in Replication Status State Description Completed All receiver SEs are in the Completed state, and the Content Acquirer is in the Completed, Re-checking Content, Retrieving Manifest, or Processing Manifest state. (See Table 7-18 on page 7-22 for a description of SE states.
Chapter 7 Monitoring the Internet Streamer CDS Delivery Service Monitoring Figure 7-8 Delivery Service Replication Status Page Table 7-16 describes the fields in Acquisition Status section of this page. This page also allows you to do the following: • See a detailed view of replication status using search criteria. (See the “Content Replication Status by Delivery Service” section on page 7-23.) • Query the replication status of content items (by pattern) for a selected SE in the delivery service.
Chapter 7 Monitoring the Internet Streamer CDS Delivery Service Monitoring Table 7-17 describes the information about the devices in this delivery service shown at the bottom of the Replication Status page. Table 7-17 Replication Status for Devices Assigned to a Delivery Service Field Description Device Name of the SE assigned to the delivery service. Type Type of SE: Acquirer, Receiver, or Temporary Acquirer. Status Graphical display indicating acquisition, replication, and device errors.
Chapter 7 Monitoring the Internet Streamer CDS Delivery Service Monitoring Table 7-18 Device States (continued) State Description Re-checking Content The Content Acquirer is checking the content or crawl job freshness. No Status Reported No Status Reported can mean: Completed • The Content Acquirer is unreachable for three consecutive polling periods. • The Content Acquirer is offline. • The CDSM has recently restarted and has not yet received a report from the Content Acquirer.
Chapter 7 Monitoring the Internet Streamer CDS Delivery Service Monitoring Figure 7-9 Replication Status for Searched Content Items in a Delivery Service Table 7-19 describes the information displayed for the replication items. Table 7-19 Replication Status of Items for a Delivery Service Column Heading Description Url URL of the origin server that stores the content. Size Size of the file to be acquired or crawled. Status Status of replication of content in the delivery service.
Chapter 7 Monitoring the Internet Streamer CDS Delivery Service Monitoring Figure 7-10 Replication Status for Searched Content Items in a Delivery Service—Detail The Replication Item page is specifically designed to limit listings to 5000 objects for scalability reasons. These are system limits and not specifically enforced for replication status reporting.
Chapter 7 Monitoring the Internet Streamer CDS Delivery Service Monitoring b. In the Content Items Using field, enter a string that specifies the type of content items that you want displayed and click Go. Use an asterisk (*) to match one or more characters, or a question mark (?) to match only a single character. Note The Replication Items page for the selected device is displayed (Figure 7-11). Table 7-21 describes the fields displayed in this page.
Chapter 7 Monitoring the Internet Streamer CDS Viewing Statistics Step 4 To return to the Replication Status page, click the Back icon in the task bar. Viewing Statistics The Statistics pages track system-wide delivery, replication, and routing traffic in the CDS. You can view statistics on delivery traffic (Movie Streamer, Windows Media, HTTP, and Flash Media) listed by SE or device group. The Routing Statistics page lists client requests and redirects.
Chapter 7 Monitoring the Internet Streamer CDS Viewing Statistics Table 7-22 Service Engine and Device Group Statistics (continued) Statistic Description Hit Rate Average number of content items per minute successfully served from the cache of the SE or from all the SEs in the device group. Updated Timestamp indicating when the statistics were updated. Windows Media Concurrent Requests Total number of simultaneous requests the Windows Media Streaming Engine has served.
Chapter 7 Monitoring the Internet Streamer CDS Viewing Statistics Table 7-23 Service Router Statistics Statistic Description Routing Requests Total Requests Total number of content requests received from clients. HTTP Requests Number of ASX and traditional HTTP web requests received. RTSP Requests Number of RTSP requests received. RTMP Requests Number of RTMP requests received. Updated Timestamp indicating when the statistics were updated.
Chapter 7 Monitoring the Internet Streamer CDS Viewing Statistics Table 7-24 Device Replication Status Page Column Heading In Process Step 2 Description In Process can mean: • Number of delivery services reporting this SE (as a Content Acquirer) in the Retrieving Manifest, Processing Manifest, Acquiring Content, or Re-checking Content state. • Number of delivery services reporting this SE (as a receiver SE) in the Pending Update from Acquirer, Replicating, or Recovering from Failure state.
Chapter 7 Monitoring the Internet Streamer CDS Transaction Logs Step 7 To further qualify your search, change the item type from the drop-down list, if you wish, or specify another file type (such as *.html, *.mpg, or *.jpg) in the Content Items Using field. To retrieve the specified items, click Go. Step 8 To forcibly refetch the latest content replication information, click the Force Replication Information Refresh icon in the task bar.
Chapter 7 Monitoring the Internet Streamer CDS Transaction Logs An Extended Squid-style log format example looks like this: 1012429341.115 100 172.16.100.152 TCP_MISS/302 184 GET http://www.cisco.com/cgi-bin/login DIRECT/www.cisco.com Apache The Apache format is the Common Log File (CLF) format defined by the World Wide Web Consortium (W3C) working group. This format is compatible with many industry-standard log tools.
Chapter 7 Monitoring the Internet Streamer CDS Transaction Logs Table 7-26 Custom Format Log Format String Values (continued) Format Token Value %q Query string (which is preceded by a question mark (?) if a query string exists; otherwise, it is an empty string). %r First line of the request. %>s Status. The translog code always returns the HTTP response code for the request. %t Time in common log time format (or standard English format).
Chapter 7 Monitoring the Internet Streamer CDS Transaction Logs • Note Flash Media Streaming logs are logged to a working log on the local disk in /local1/logs/fms_access/working.log and /local1/logs/fms_authorization/working.log For Movie Streamer, client requests that join the multicast group do not appear in the transaction log because multicast clients do not contact the server.
Chapter 7 Monitoring the Internet Streamer CDS Transaction Logs • Path of the directory where transferred files are written Use a fully qualified path or a relative path for the user login. The user must have write permission to the directory. You can also compress archived log files into gzip format before exporting them to external FTP servers. The compressed filename has a .gz extension.
Chapter 7 Monitoring the Internet Streamer CDS Transaction Logs The SE’s transaction logging format for Windows Media streaming is consistent with that of the Windows Media Services and the World Wide Web Consortium (W3C)-compliant log format. A log line is written for every stream accessed by the client. The location of the log is not configurable. These logs can be exported using FTP. When transaction logging is enabled, daemons create a separate working.
Chapter 7 Monitoring the Internet Streamer CDS Transaction Logs Cisco Internet Streamer CDS 2.0-2.
Chapter 7 Monitoring the Internet Streamer CDS Transaction Logs Cisco Internet Streamer CDS 2.0-2.
CH A P T E R 8 Maintaining the Internet Streamer CDS This chapter explains how to perform common administrative tasks including updating system software, hard disk drive maintenance, and rebooting and deleting devices.
Chapter 8 Maintaining the Internet Streamer CDS Software Upgrade Step 3 Click Cisco Content Delivery Systems (CDS). The Downloads page is displayed. Step 4 Click the Cisco Content Delivery Applications folder to expand it, and click the Cisco Internet Streamer Application. The page refreshes and the software releases are displayed. Step 5 Click the software release you want. The page refreshes and the software image files are displayed. Step 6 Click the link for the software image file you want.
Chapter 8 Maintaining the Internet Streamer CDS Software Upgrade The server name or IP address of the URL in the Manifest file (and in the Software File URL field in the Software File Settings page must match either the Origin Server field or the Service Router Domain Name field in the Content Origin page). Finding the Software Version of the Devices The CDSM Home page gives a brief summary of the software versions in use on all the devices in the CDS network.
Chapter 8 Maintaining the Internet Streamer CDS Software Upgrade Figure 8-1 Step 3 Software Image Page In the Software Image URL field, enter the URL for the .bin software file that you downloaded from Cisco.com. a. Choose a protocol (http or ftp) from the drop-down list. b. Enter the URL of the software file; for example, a valid URL might look like this: http://internal.mysite.com/cds/CDS-2.x.x-K9.bin In this URL, CDS-2.x.x-K9 is the name of the software upgrade file.
Chapter 8 Maintaining the Internet Streamer CDS Software Upgrade Step 4 If your server requires user login authentication, enter your username in the Username field and enter your login password in the Password field. Enter the same password in the Confirm Password field. Step 5 Enter the software version number in the Software Version field. You can copy this number from the version portion of the software filename in the software file URL. Specify the version in one of two formats: X.Y.Z-bB or X.Y.Z.
Chapter 8 Maintaining the Internet Streamer CDS Software Upgrade The software file that you want to use is now registered with the CDSM. When you perform the software upgrade or downgrade, the URL that you just registered becomes one of the choices available in the Update Software page. (See the “Upgrading the Software” section on page 8-6.) Upgrading the Software When upgrading software in your CDS network, begin with Service Engines and Service Routers before upgrading the CDSM.
Chapter 8 Maintaining the Internet Streamer CDS Software Upgrade • While being upgraded, a node will be unavailable for a short time. • All nodes, other than the node being upgraded, continue to operate at full capacity. The availability of other nodes is not affected during an upgrade. • Content is preserved during an upgrade or downgrade unless you remove a delivery service. • All logs are preserved during an upgrade or downgrade, unless you change the disk configuration.
Chapter 8 Maintaining the Internet Streamer CDS Software Upgrade Table 8-1 Upgrade Status Messages Upgrade Status Message Condition Pending The request has yet to be sent from the CDSM to the device, or receipt of the request has yet to be acknowledged by the device. Downloading The download method for the software file is being determined. Proceeding with Pre-positioned Download The download method for the software file is detected as pre-positioned.
Chapter 8 Maintaining the Internet Streamer CDS Rebooting Devices Software Upgrades by Device Use this upgrade procedure for Service Routers and CDSMs. You can also use this upgrade procedure to upgrade Service Engines one at a time. To upgrade your software on a single device, do the following: Step 1 Choose Devices > Devices. The Devices Table page is displayed. Step 2 Click the Edit icon of the device that you want to upgrade. The Device home page is displayed.
Chapter 8 Maintaining the Internet Streamer CDS Deleting a Device Deleting a Device You can delete a device if the device is experiencing unresolvable problems or when its network address or configuration has changed and you need to add the device back to the CDS network using its new address and configuration information. Caution If you delete the only SR in your CDS network, you are removing the ability of your CDS network to fill user requests.
Chapter 8 Maintaining the Internet Streamer CDS Deleting a Device Step 2 In global configuration mode, enter the no cms enable command. SE# configure SE(config)# no cms enable Note Step 3 Issuing the no cms enable command does not disable acquisition and distribution services on the device; however, issuing the cms deregister command does. The cms deregister command disables the CMS, all acquisition and distribution services, and all routing communications to and from this device.
Chapter 8 Maintaining the Internet Streamer CDS Replacing a Device Step 4 To execute your request, click OK. The device is removed from the CDSM. Step 5 If possible, access the device CLI to deregister the device. Step 6 In the CLI, enter the cms deregister force command. Note Step 7 You must use the cms deregister force command after deleting a device in the CDSM. This is because once the device has been deleted, the CDSM no longer has a record of the device.
Chapter 8 Maintaining the Internet Streamer CDS Replacing a Device Replacing a CDSM To replace a CDSM in a CDS you must first add the new CDSM into the network as a standby CDSM. For procedural information, see the “Configuring Primary and Standby CDSMs” section on page 3-8. Note The primary and standby CDSMs must be running the same version of software. You must first add the new CDSM with the same version as the existing CDSM.
Chapter 8 Maintaining the Internet Streamer CDS Replacing a Device Step 2 In global configuration mode, enter the no cms enable command to disable CMS on the device that needs to be replaced. SE# configure SE(config)# no cms enable Step 3 From the CDSM, choose Devices > Devices > Device Activation. The Device Activation page is displayed. Step 4 Uncheck the Activate check box and click Submit. The page refreshes and displays a Replaceable check box.
Chapter 8 Maintaining the Internet Streamer CDS Backup and Recovery Procedures Step 15 Once the new device is up and running, as noted by the online status, the old device can be removed from the CDS network. Backup and Recovery Procedures This section provides CDSM database backup and CDS software recovery procedures.
Chapter 8 Maintaining the Internet Streamer CDS Backup and Recovery Procedures Type set to I. Sending:PASV Entering Passive Mode (10,86,32,82,112,221) Sending:CWD /incoming CWD command successful. Sending PASV Entering Passive Mode (10,86,32,82,203,135) Sending:STOR cds-db-9-22-2002-17-36.dump Opening BINARY mode data connection for cds-db-9-22-2002-17-36.dump. Transfer complete. Sent 18155 bytes Step 3 Delete the existing CMS database.
Chapter 8 Maintaining the Internet Streamer CDS Backup and Recovery Procedures The .sysimg component is provided for recovery purposes, and allows for repair of flash memory only, without modifying the disk contents. Getting the Cisco CDS Software Recovery File from Cisco.com To get a software file from Cisco.com, do the following: Step 1 Launch your web browser and enter the following URL: http://www.cisco.com/kobayashi/sw-center/sw-video.shtml The Log In page is displayed. Step 2 Log in to Cisco.
Chapter 8 Maintaining the Internet Streamer CDS Backup and Recovery Procedures Step 3 When the installer menu appears, choose Option 7: Wipe Out Disks and Install .bin Image. (The installer menu options are described in the next section.) Step 4 Wait for the process to complete. Step 5 Before you reboot the device, remove the USB CD-ROM drive from the USB port so that the device boots from flash memory. Step 6 Reboot the device by choosing Option 8: Exit and Reboot.
Chapter 8 Maintaining the Internet Streamer CDS Backup and Recovery Procedures Option 7: Wipe Out Disks and Install .bin Image Caution Option 7 erases the content from all disk drives in your device. This option provides the preferred procedure for installing the Cisco CDS software. This option performs the following steps: 1. Checks that flash memory is formatted to Cisco specifications. If yes, continues to number 2. If no, the following takes place: a.
Chapter 8 Maintaining the Internet Streamer CDS Backup and Recovery Procedures in flash had been corrupted.
Chapter 8 Maintaining the Internet Streamer CDS Backup and Recovery Procedures Restarting system. Initializing memory. Please wait. Step 4 Log in to the device as username admin. Verify that you are running the correct version by entering the show version command. Username: admin Password: Console> enable Console# show version Content Delivery System Software (CDS) Copyright (c) 2007 by Cisco Systems, Inc. Content Delivery System Software Release 2.0.0 (build b460 July 5 2007) Version: se507-2.0.
Chapter 8 Maintaining the Internet Streamer CDS Backup and Recovery Procedures Step 4 When the device completes the boot sequence, you are prompted to enter the username to access the CLI. Enter the default administrator username (admin). Cisco Service Engine Console Username: admin Step 5 When you see the CLI prompt, set the password for the user using the username password command in global configuration mode.
Chapter 8 Maintaining the Internet Streamer CDS Backup and Recovery Procedures Note • Degraded—One of the disks has failed. It is highly recommended that a new disk is added to repair the volumes. • Bad—Both disks have failed. The system has likely lost all but basic functionality. If both system disks fail, a CDS state of “missing disk-based software” occurs. Normally, when a problem occurs on one system disk, a disk failure or RAID alarm is triggered. If this occurs, replace the failed disk.
Chapter 8 Maintaining the Internet Streamer CDS Backup and Recovery Procedures Check whether first-disk is bad, or use 'disk recover-system-volumes' to recover first-disk. ******************************************** Step 5 Log in as admin. Cisco Service Engine Console Username: admin Password: System Initialization Finished.
Chapter 8 Maintaining the Internet Streamer CDS Backup and Recovery Procedures Recovering CDS Network Device Registration Information Device registration information is stored both on the device itself and on the CDSM. If a device loses its registration identity or needs to be replaced because of hardware failure, the CDS network administrator can issue a CLI command to recover the lost information or, in the case of adding a new device, assume the identity of the failed device.
Chapter 8 Maintaining the Internet Streamer CDS Disk Maintenance c. From the left-panel menu, choose Device Activation. The Service Engine status should be Online. d. Check the Activate check box and click Submit. Disk Maintenance This section covers removing and replacing disk drives, and manual content removal. For information about disk error handling, see the “Enabling Disk Error Handling” section on page 4-56.
Chapter 8 Maintaining the Internet Streamer CDS Disk Maintenance The variable diskname is the name of the drive to be unmounted. See Figure 8-2 for the disk numbering used for the disk name. Following are some examples of the command and the resultant actions: se# disk unuse disk01 Disk01 has mounted SYSFS and can not be unused! se# disk unuse disk02 This will restart applications currently using disk02 and unmount all partitions on disk02. Do you want to continue? (yes/no) [no]no Disk02 not unused.
Chapter 8 Maintaining the Internet Streamer CDS Disk Maintenance SE# reload Removing Content The Content Removal page allows you to delete content manually, either by referencing a single URL or by using an XML file for batch deletions. Single Content Removal To delete content manually, do the following: Step 1 Choose Services > Service Definition > Delivery Service.
Chapter 8 Maintaining the Internet Streamer CDS Disk Maintenance Step 1 Create an XML file containing the URLs of the content you want to delete by using the XML example shown in the Content Removal—Batch File Help page. Figure 8-3 shows the URL Removal XML file example displayed when you click Help. Figure 8-3 Content Removal—Batch File Help Page Step 2 In the Batch File field for a Batch URL removal, enter the URL of the XML file. Step 3 Click Submit. Cisco Internet Streamer CDS 2.0-2.
Chapter 8 Maintaining the Internet Streamer CDS Disk Maintenance Cisco Internet Streamer CDS 2.0-2.
A P P E N D I X A Troubleshooting This appendix provides information on troubleshooting. The following topics are covered in this appendix: • Troubleshooting Service Router Configurations, page A-1 • Troubleshooting the Distribution Hierarchy, page A-2 • Troubleshooting Content Acquisition, page A-3 • Enabling the Kernel Debugger, page A-6 For more troubleshooting tools, see Chapter 7, “Monitoring the Internet Streamer CDS.
Appendix A Troubleshooting Troubleshooting the Distribution Hierarchy – Is there a delivery service created for the requested domain and a serving Service Engine assigned to this delivery service? See the “Creating Delivery Service” section on page 5-4. – Is the serving Service Engine alive? Use the show statistics service-routing se command to show the status of a Service Engine. See the “Using show and clear Commands” section on page 7-9.
Appendix A Troubleshooting Troubleshooting Content Acquisition se1# show distribution remote ? max-hop Max-hop to trace-till-good traceroute trace-till-root traceroute traceroute unicast-sender delivery-service-id 133 probe traceroute to till probe is good or the object is found till the root se se1# show distribution remote traceroute unicast-sender delivery-service-id 133 probe trace-till-root Polling .... se3 [10.255.0.43] Fwdr_Id:1100 Polling .... se3 [128.107.193.
Appendix A Troubleshooting Troubleshooting Content Acquisition • Use the show statistics acquirer delivery-service-id or show statistics acquirer delivery-service-name EXEC command to obtain the detailed acquisition statistics for a given delivery service. In the following example, there was an error acquiring two items. SE# show statistics acquirer delivery-service-id 793 Querying Database.......
Appendix A Troubleshooting Troubleshooting Content Acquisition Replication: Done File State: Ready for distribution Multicast for Delivery Service: Not Enabled Replication Lock: Received by Unicast-Receiver/Acquirer Reference Count: 1 Total Size: 2756437 Transferred Size: 2756437 MD5 of MD5: tjS#DxqE5oUc024Z8XtFDw.. Source Url: http://172.18.81.168/Videos/SM-final%20Innebandy%202003.
Appendix A Troubleshooting Enabling the Kernel Debugger By comparing fields, such as Total Size, Transferred Size, and Source URL in the Object Replication output and Actual File Size and Source URL in the Source-URL to CDN-Object Mapping output, you can determine whether or not the object that is stored is the same as the object that was requested.
A P P E N D I X B Creating Manifest Files This appendix describes the process for creating Manifest files used to acquire and distribute content within the CDS network.
Appendix B Creating Manifest Files Working with Manifest Files Manifest File Requirements The Manifest file needs to support different attributes and tags to support content prefetching and hybrid ingest. The basic requirements for a Manifest file are the following: • Specify Content to Be Prefetched—There are two ways to specify prefetched content. One is to use a single item, where users specify a single URL and the Content Acquirer ingests only the content pointed to by this URL.
Appendix B Creating Manifest Files Working with Manifest Files For a single item, you specify the item’s URL in the src attribute. There are two ways to specify the item URL: • Specify the src attribute with the absolute URL as shown in the following format: proto://username:password@/domain-name:port/file-path/file-name In the example, the first - tag uses the full path.
Appendix B Creating Manifest Files Working with Manifest Files Table B-1 Website or FTP Server Crawl Job Attributes (continued) Attribute Description prefix (Optional) Combines the hostname from the tag and this field to create a full prefix. Only content with URLs that match the full prefix are acquired, as shown in this example: PAGE 293Appendix B Creating Manifest Files Working with Manifest Files Note If you specify both the max-number and maxTotalSizeIn attributes as the criteria to use to stop a crawl job, the condition that is met first takes precedence. The crawl job stops either when the maximum number of objects is acquired or when the maximum content size is reached, whichever occurs first.
Appendix B Creating Manifest Files Working with Manifest Files In the following example, page freshness is scheduled to be crawled and checked every hour to a link depth value of 2: If the content is not yet available at a particular URL, the prefetch attribute can be used to specify the start time for acquisition at the specified URL.
Appendix B Creating Manifest Files Working with Manifest Files You can also use the tag to share attributes at the top-most level of the Manifest file. Shared attributes in the tag can be shared by every - tag or by the tag in the Manifest file. However, if a shared attribute is specified in both the and the
- tags or the and
- tags, attribute values in the
- tags take precedence over the and tags.
Appendix B Creating Manifest Files Working with Manifest Files Table B-2 Subtag Attributes (continued) Attribute Description prefix (Optional.) Specifies a prefix as a match rule to filter out websites during a crawl job. url-pattern (Optional.) Specifies a regular expression as a match rule to filter out certain URLs. A subtag can specify multiple attributes. Attributes within a tag have a Boolean AND relationship.
Appendix B Creating Manifest Files Working with Manifest Files To calculate content priority, use one of the following formulas: • If there is a priority value for this content specified in the Manifest file priority attribute, use the following formula: Content priority = Delivery service priority * 10000 + Item priority In this formula, Item priority can be any integer and is unrestricted.
Appendix B Creating Manifest Files Working with Manifest Files The tag is used to generate a playserver list for each content type.
Appendix B Creating Manifest Files Working with Manifest Files Table B-3 Attributes for Content Serving (continued) Attribute Description ignoreQueryString Playback attribute that can be used with the , , - , and tags. If ignoreQueryString is set to true, then the CDS software ignores any string after a question mark (?) in the request URL for playback. If this attribute is omitted, then the default value is false.
Appendix B Creating Manifest Files Working with Manifest Files
Appendix B Creating Manifest Files Working with Manifest Files If the expires attribute is specified inside an - tag, it applies to that item; if it is specified inside a tag, the attribute applies to the crawl job. You can monitor the status of content replication and freshness by enabling and then viewing the transaction log files that reside on the Service Engines.
Appendix B Creating Manifest Files Manifest Validator Utility Note For type="cache", and tags are not used. Note Currently, only serveStartTime and serveStopTime are supported for type=”cache.” Manifest Validator Utility Because correct Manifest file syntax is so important to the proper deployment of prefetched content on your CDS network, Cisco makes available a Manifest file syntax validator.
Appendix B Creating Manifest Files Manifest Validator Utility - PAGE 304
Appendix B Creating Manifest Files Manifest Validator Utility In the preceding example, although there are no warnings, two errors are found, and this Manifest file is syntactically incorrect, as shown in the following message: ERROR (/state/dump/tmp.xml.1040667979990 line: 23 col: 1 ):No character data is allowed by content model ERROR (/state/dump/tmp.xml.1040667979990 line: 23 col: 9 ):Expected end of tag 'host' Manifest File: /state/dump/tmp.xml.
Appendix B Creating Manifest Files Manifest File Structure and Syntax • CORRECT—Contains possible syntax irregularities but is syntactically valid and ready for deployment on your CDS network • INCORRECT—Contains syntax errors and is unsuitable for deployment on your CDS network Syntax Errors The Manifest Validator issues syntax errors only when it cannot identify a source file for a listed content item, either because it is not listed or because it is listed using improper syntax.
Appendix B Creating Manifest Files Manifest File Structure and Syntax Table B-4 Manifest File Tag Summary Tag Name Subelements Attributes Description CdnManifest
Appendix B Creating Manifest Files Manifest File Structure and Syntax Table B-4 Manifest File Tag Summary (continued) Tag Name Subelements Attributes item src authCookie cdn-url disableBasicAuth enableCookies expires failRetryInterval host ignoreOriginPort ignoreQueryString noProxy ntlmUserDomain password playServer port crawler Description prefetch priority proto proxyServer server serveStartTime serveStopTime sslAuthType ttl type user userDomainName uuencoded
Appendix B Creating Manifest Files Manifest File Structure and Syntax Table B-4 Manifest File Tag Summary (continued) Tag Name Subelements Attributes item-group
Appendix B Creating Manifest Files Manifest File Structure and Syntax Table B-5 Manifest File Nested Tag Relationships (continued) -
CdnManifest The tag set is required and marks the beginning and end of the Manifest file content. At a minimum, each tag set must contain at least one item, or content object, that is fetched and stored.
Appendix B Creating Manifest Files Manifest File Structure and Syntax playServerTable The tag set is optional and provides a means for you to set default mappings for a variety of media types. Mappings can be set for both MIME-type content (the preferred mapping) and file extensions. Playserver tables allow you to override default mappings on the Service Engine for content types from a particular origin server.
Appendix B Creating Manifest Files Manifest File Structure and Syntax Note Do not confuse the tag with the playserver attribute in an - or tag. An
- or tag specifies a server type to be used for an individual content object or group of related content objects.
Appendix B Creating Manifest Files Manifest File Structure and Syntax Attributes The name attribute is required and provides the file extension for a mapped content type. When files with the named extension are requested, the mapped playserver is used to serve them.
Appendix B Creating Manifest Files Manifest File Structure and Syntax • priority • wmtRequireAuth • server • sslAuthType • ttl • type Subelements (See the “item” section on page B-28 for descriptions of these subelements.) server The and tag fields configure the origin content source server. The tag field inside the tag field configures the content source host. Having multiple tag fields in one tag field is not supported.
Appendix B Creating Manifest Files Manifest File Structure and Syntax The noProxy attribute is optional. If set to true, no proxy is used for the origin server. The default is false. • ntlmUserDomain The ntlmUserDomain attribute is optional and specifies the user domain name for NTLM authentication. • password The password attribute is optional and identifies the password for the user account that is required to access the host server.
Appendix B Creating Manifest Files Manifest File Structure and Syntax • user The user attribute is optional and identifies the secure login used for host access. • userDomainName See the “item” section on page B-28 for a description of this attribute. • uuencoded The uuencoded attribute is optional. If set to true, the password is not encoded. The uuencoded attribute default setting is false. Subelements None proxyServer The tag specifies proxy server information.
Appendix B Creating Manifest Files Manifest File Structure and Syntax item The -
tag set identifies the specific content that is to be acquired. The - tag names a single piece of content or a content object on the origin server, such as a graphic, MPEG video, or RealAudio sound file. Content items can be listed individually or grouped using the tag. The
- tag must be enclosed within the tag set and can also be enclosed within tags.
Appendix B Creating Manifest Files Manifest File Structure and Syntax
Appendix B Creating Manifest Files Manifest File Structure and Syntax The playServer attribute is optional and names the server used to play back the content. Valid playservers are wmt (Windows Media Technologies), qtss (QuickTime Streaming Server), fms (Flash Media Streaming), and http (Web Engine). The value in this field is either one playserver or multiple playservers separated by commas.
Appendix B Creating Manifest Files Manifest File Structure and Syntax The serveStartTime attribute is optional and designates a time in yyyy-mm-dd hh:mm:ss format when the CDS software is allowed to start serving the content. If the time to serve is omitted, content is ready to serve once it is distributed to the Service Engine or other edge device.
Appendix B Creating Manifest Files Manifest File Structure and Syntax • Number of Minutes Action 0 Crawl 4 Recheck failed 8 Recheck failed 10 Recrawl 14 Recheck 18 Recheck 20 Recrawl ignoreQueryString The ignoreQueryString attribute is a playback attribute that can be used with the , , - , and tags. If the value is set to true, then CDS software ignores any string after a question mark (?) in the request URL for playback.
Appendix B Creating Manifest Files Manifest File Structure and Syntax Note • Both userDomainName and ntlmUserDomain cannot coexist in the Manifest file; only one attribute can be used at a time. enableCookies The enableCookies attribute enables cookie support for the item. When this attribute is set to true, the Content Acquirer, after sending a request for an item to the origin server, parses the server response for cookie name/value pairs.
Appendix B Creating Manifest Files Manifest File Structure and Syntax • user • uuencoded Subelements • • The subelement and its attributes specify a time for a recrawl or an item refetch to begin. You can have multiple subelements under the subelement. The attributes time, start, and end specify the day of the month or day of the week and the duration of the specified repeat.
Appendix B Creating Manifest Files Manifest File Structure and Syntax ttl="3000" /> crawler The tag set supports crawling a website or an FTP server. Attributes • start-url The start-url attribute is required. It defines the URL at which to start the process of crawling the website or FTP server. It is identical to the src attribute used in the - tag. (See the “ •src” section on page B-28 under the item section.
Appendix B Creating Manifest Files Manifest File Structure and Syntax – The prefix attribute applies to a URL including all of its links or subdirectories. However, the accept attribute allows the URL and its links and subdirectories to be evaluated separately. • reject The reject attribute is optional and uses a regular expression to reject a URL if it matches the reject regular expression. The reject regular expression is checked after checking for a prefix URL match.
Appendix B Creating Manifest Files Manifest File Structure and Syntax • externalPrefixes The externalPrefixes attribute is optional and specifies additional prefixes for crawl jobs to crawl multiple protocols or multiple websites. Prefixes are separated with a bar (|). • externalServers The externalServers attribute is optional and can be used for multiple host crawling jobs where each host has a different user account.
Appendix B Creating Manifest Files Manifest File Structure and Syntax • user • uuencoded The following attributes described under the - tag attributes can also be specified by the tag.
Appendix B Creating Manifest Files Manifest File Structure and Syntax - or per tag basis. For example, if every
- tag is using the same server and ttl attributes, you can create an tag on top of these
- tags and place the server and ttl attributes in the tag. Using shared attributes makes any Manifest file with many
- tags more efficient by consolidating the
- tags with shared attributes.
Appendix B Creating Manifest Files Manifest File Structure and Syntax • proto • proxyServer • sslAuthType • user • uuencoded Additionally, the following two attributes can be placed within the tag. See the “crawler” section on page B-35 for a detailed description of the following two attributes: • srcPrefix • cdnPrefix These two attributes convert the prefix of the src-url (content acquisition URL) to the cdn-url (publishing URL) for multiple content objects.
Appendix B Creating Manifest Files Manifest File Structure and Syntax (See the “item” section on page B-28 for descriptions of the subelements.) Example - PAGE 330
Appendix B Creating Manifest Files Manifest File Structure and Syntax You can specify multiple tags within the tag. The tags have a Boolean OR relationship (to form a logical inclusion) with other tags. You must specify at least one tag per tag. Attributes • mime-type The mime-type attribute specifies MIME-types. • extension The extension attribute specifies file extensions.
Appendix B Creating Manifest Files Manifest File Structure and Syntax Examples
Appendix B Creating Manifest Files XML Schema XML Schema In the case of the Manifest file, an XML schema defines the custom markup language of the Manifest file and the appearance of a given set of XML documents. The XML schema specifies which tags or elements you can use in your documents, the attributes those tags can contain, and their arrangement. Manifest XML Schema An XSD is a library that provides an application programming interface (API) for manipulating the components of an XML schema.
Appendix B Creating Manifest Files XML Schema PAGE 334Appendix B Creating Manifest Files XML Schema
Appendix B Creating Manifest Files XML Schema
Appendix B Creating Manifest Files XML Schema name="maxFileSizeInB" type="xs:int" use="optional"/> name="minFileSizeInKB" type="xs:int" use="optional"/> name="maxFileSizeInKB" type="xs:int" use="optional"/> name="minFileSizeInMB" type="xs:int" use="optional"/> name="maxFileSizeInMB" type="xs:int" use="optional"/> name="extension" type="xs:string" use="optional"/
Appendix B Creating Manifest Files XML Schema Default PlayServerTable Schema The following XML code defines the default PlayServerTable:
Appendix B Creating Manifest Files Manifest File Time Zone Tables Manifest File Time Zone Tables To convert to local time, you must know the time difference between Greenwich mean time (GMT) and local time for both standard time and summer time (daylight saving time). Table B-6 through Table B-21 list the time zones supported by the Manifest file.
Appendix B Creating Manifest Files Manifest File Time Zone Tables Table B-6 Standard Time Zones and GMT Offsets (continued) Time Zone: GMT Offset Time Zone: GMT Offset Time Zone: GMT Offset Etc/GMT+4:-:04:00 GMT:00:00 WET:00:00 Etc/GMT+5:-:05:00 Greenwich:00:00 Zulu:00:00 Etc/GMT+6:-:06:00 HDT:-:09:00 — Table B-7 Africa GMT Offsets Time Zone: GMT Offset Time Zone: GMT Offset Time Zone: GMT Offset Africa/Abidjan:00:00 Africa/Djibouti:+:03:00 Africa/Maputo:+:02:00 Africa/Accra:00:00 A
Appendix B Creating Manifest Files Manifest File Time Zone Tables Table B-8 America GMT Offsets (continued) Time Zone: GMT Offset Time Zone: GMT Offset Time Zone: GMT Offset America/Barbados:-:04:00 America/Ind/Indian:-:05:00 America/Porto_Acre:-:05:00 America/Belem:-:03:00 America/Ind/Knox:-:05:00 America/Porto_Velho:-:04:00 America/Belize:-:06:00 America/Ind/Marengo:-:05:00 America/Puerto_Rico:-:04:00 America/Boa_Vista:-:04:00 America/Ind/Vevay:-:05:00 America/Rainy_River:-:06:00 Ameri
Appendix B Creating Manifest Files Manifest File Time Zone Tables Table B-9 Antarctica/Arctic GMT Offsets Time Zone: GMT Offset Time Zone: GMT Offset Time Zone: GMT Offset Antarctica/Casey:+:08:00 Antarctica/McMurdo:+:12:00 Antarctica/Vostok:+:06:00 Antarctica/Davis:+:07:00 Antarctica/Palmer:-:04:00 Arctic/Longyearbyen:+:01:00 Antarctica/DtDUrville:+:10:00 Antarctica/South_Pole:+:12:00 — Antarctica/Mawson:+:06:00 Antarctica/Syowa:+:03:00 — Time Zone: GMT Offset Time Zone: GMT Offset Tim
Appendix B Creating Manifest Files Manifest File Time Zone Tables Table B-11 Atlantic GMT Offsets Time Zone: GMT Offset Time Zone: GMT Offset Time Zone: GMT Offset Atlantic/Azores:-:01:00 Atlantic/Faeroe:00:00 Atlantic/South_Georgia:-:02:00 Atlantic/Bermuda:-:04:00 Atlantic/Jan_Mayen:+:01:00 Atlantic/St_Helena:00:00 Atlantic/Canary:00:00 Atlantic/Madeira:00:00 Atlantic/Stanley:-:04:00 Atlantic/Cape_Verde:-:01:00 Atlantic/Reykjavik:00:00 — Table B-12 Australia GMT Offsets Time Zone: GMT
Appendix B Creating Manifest Files Manifest File Time Zone Tables Table B-15 Egypt/Eire/Europe GMT Offsets (continued) Time Zone: GMT Offset Time Zone: GMT Offset Time Zone: GMT Offset Europe/Athens:+:02:00 Europe/Luxembourg:+:01:00 Europe/Tallinn:+:02:00 Europe/Belfast:00:00 Europe/Madrid:+:01:00 Europe/Tirane:+:01:00 Europe/Belgrade:+:01:00 Europe/Malta:+:01:00 Europe/Tiraspol:+:02:00 Europe/Berlin:+:01:00 Europe/Minsk:+:02:00 Europe/Uzhgorod:+:02:00 Europe/Bratislava:+:01:00 Europe/Mo
Appendix B Creating Manifest Files Manifest File Time Zone Tables Table B-19 Pacific/Poland/Portugal GMT Offsets Time Zone: GMT Offset Time Zone: GMT Offset Time Zone: GMT Offset Pacific/Apia:-:11:00 Pacific/Johnston:-:10:00 Pacific/Ponape:+:11:00 Pacific/Auckland:+:12:00 Pacific/Kiritimati:+:14:00 Pacific/Port_Moresby:+:10:00 Pacific/Chatham:+:12:45 Pacific/Kosrae:+:11:00 Pacific/Rarotonga:-:10:00 Pacific/Easter:-:06:00 Pacific/Kwajalein:+:12:00 Pacific/Saipan:+:10:00 Pacific/Efate:+:11
A P P E N D I X C Creating Coverage Zone Files This appendix describes the Coverage Zone file and provides several Coverage Zone file examples. Introduction A Coverage Zone file is an XML file used to specify a user-defined coverage zone. The Coverage Zone file supports different tags to support different types of proximity configurations.
Appendix C Creating Coverage Zone Files Coverage Zone XML Schema Table C-1 Coverage Zone File Elements (continued) Tag Element Value Description CDNNetwork revision 1.0 Not used in this CDS release. customerName customer name Not used in this CDS release. coverageZone This can have one or more coverage zones. Note The metric value of a default coverage zone is set to 20.
Appendix C Creating Coverage Zone Files Coverage Zone File Examples PAGE 348Appendix C Creating Coverage Zone Files Coverage Zone File Examples CDE-200-SE5 CDE-200-SE6 10 Scenario 2: Coverage Zone with Geographical Location of the Datacenter Only 1.
Appendix C Creating Coverage Zone Files Coverage Zone File Examples 20 -120 CDE-200-SE3 CDE-200-SE4 10 192.1.4.0/24 CDE-200-SE5 CDE-200-SE6 10 Cisco Internet Streamer CDS 2.0-2.
Appendix C Creating Coverage Zone Files Coverage Zone File Examples Cisco Internet Streamer CDS 2.0-2.
A P P E N D I X D Creating and Manipulating Session Shifting Files This appendix describes the process of creating Session Shifting files, and includes the following topics: Note • Introduction, page D-1 • Content Manager, page D-2 • Subscriber Manager, page D-4 • Profile Manager, page D-5 • Session Manager, page D-7 3-Screen Session Shifting is a Release 2.2 feature and supports RTSP streaming for Windows Media Streaming and the Movie Streamer. Introduction Note Release 2.
Appendix D Creating and Manipulating Session Shifting Files Content Manager Session Shifting and Delivery Services The CDS uses the delivery services to implement most of its functions. Each delivery service is associated with an origin server. A Content Origin in the CDS defines a Service Routing Domain Name, which is used by the clients to receive the content delivery from the CDS platform. The Service Routing Domain Name is only used for serving content.
Appendix D Creating and Manipulating Session Shifting Files Content Manager rtsp://cds.com/pirates.tv.mov rtsp://cds.com/pirates.pda.wmv rtsp://cds.com/lost.mov rtsp://cds.com/lost.pc.
Appendix D Creating and Manipulating Session Shifting Files Subscriber Manager To retrieve a Content List with the contents of the database, use the following wget command: wget http://cds.com/api/services/content_mgr/ Note This URL can also be called from a web browser such as Internet Explorer. Subscriber Manager The Subscriber Manager facilitates the management of 3-Screen Session Shifting users. Subscriber Lists can be posted to a Web Services interface in order to add or delete subscribers.
Appendix D Creating and Manipulating Session Shifting Files Profile Manager kate This Subscriber List has two sets of subscribers, one for the Smith Family and one for the Jones Family. Their grouping indicates that all the listed terminal addresses may correspond to the same viewers group.
Appendix D Creating and Manipulating Session Shifting Files Profile Manager For example, for the delivery service with a Service Routing Domain Name of sr.cds.com, the following link can be used to address the Profile Manager to provision profiles: http://sr.cds.com/api/services/profile_mgr Profile Lists Profile Lists in XML format are used to add, append, and delete profile entries through the Profile Manager. The following is an example of a Profile List for a delivery service:
Appendix D Creating and Manipulating Session Shifting Files Session Manager rtsp://cds.com/pirates.tv.mov rtsp://cds.com/pirates.pda.wmv In this Content List, rtsp://cds.com/pirates.
Appendix D Creating and Manipulating Session Shifting Files Session Manager STB-MAC = 02:05:05:74:AA:EE, paused, and then continued watching from his PC with LOGIN=bob from the URL rtsp://cds.com/pirates.pc.mov. The movie restarts from where he last paused it, even though the URL is different (though it is in the same content set) and the terminal address is different (though it is in the same BillableEntity).
Appendix D Creating and Manipulating Session Shifting Files Session Manager Session Lookup To look up the last play time, you need to provide the content and terminal address for which you are querying the centralized session manager. Because the GET method does not support providing information to the centralized session manager, you must use an overloaded POST message with the GET method as shown in the following example: wget --post-file=session_lookup.xml http://cds.
Appendix D Creating and Manipulating Session Shifting Files Session Manager Cisco Internet Streamer CDS 2.0-2.
A P P E N D I X E CLI Commands This appendix covers the following topics: • Configuring Port Channel, page E-1 • Configuring Last-Resort Routing, page E-6 • Configuring Standby Interfaces, page E-6 • Other CLI Commands, page E-10 Configuring Port Channel To configure an EtherChannel, you use the PortChannel interface configuration command. Port Channel, also known as EtherChannel, supports the grouping of up to four same-speed network interfaces into one virtual interface.
Appendix E CLI Commands Configuring Port Channel Note If an EtherChannel (also known as port channel) is used between the upstream router or switch and the SE for streaming real-time data, the EtherChannel load balance algorithms on the upstream switch or router and the SE should be configured as “src-ip” and “dst-ip” respectively. Using this configuration ensures session stickiness and general balanced load distribution based on clients’ IP addresses.
Appendix E CLI Commands Configuring Port Channel Step 6 Set the client and server TCP compliance to the RFC 1323 standard. SE(config)# tcp client-satellite SE(config)# tcp server-satellite Step 7 Configure a static route to the CDSM (4.0.5.5) to specify that all management traffic will go through this interface. SE(config)# ip route 4.0.5.5 255.255.255.255 3.1.8.1 Step 8 Configure the port channel and VLANs on the switch that the SE is directly connected to.
Appendix E CLI Commands Configuring Port Channel To verify the setup before application traffic is sent, use the following: SE# clear statistics all SE# show interface portChannel 1 Interface PortChannel 1 (2 physical interface(s)): GigabitEthernet 3/0 (active) GigabitEthernet 4/0 (active) GigabitEthernet 5/0 (active) GigabitEthernet 6/0 (active) --------------------Type:Ethernet Ethernet address:00:04:23:D8:86:02 Internet address:3.1.7.73 Broadcast address:3.1.7.255 Netmask:255.255.255.
Appendix E CLI Commands Configuring Port Channel GigabitEthernet 6/0 (active) -------------------Type:Ethernet Ethernet address:00:04:23:D8:86:02 Internet address:3.1.7.73 Broadcast address:3.1.7.255 Netmask:255.255.255.
Appendix E CLI Commands Configuring Last-Resort Routing Device Mode = se Current CDSM address = 4.0.5.5 Registered with CDSM = 4.0.5.5 Status = Online Time of last config-sync = Thu May 3 16:56:54 2007 CMS services information : Service cms_se is running In the Devices Table page on the CDSM (Devices > Devices), the SE or SR status should be “Online.” The IP address for the device always shows the IP address of the primary interface.
Appendix E CLI Commands Configuring Standby Interfaces A standby group must have at least two interfaces. Interfaces that are part of a standby group are called member interfaces. After you create a standby group, you define which interfaces should be assigned to this logical group. As part of defining the member interfaces, you specify the priority of each member interface in a standby group.
Appendix E CLI Commands Configuring Standby Interfaces Tip If an interface belongs to more than one standby group, you can configure the interface with a different priority in each standby group for better load balancing. For example, interfaces FE 0/0 and FE 0/1 are both in standby group 1 and in standby group 2.
Appendix E CLI Commands Configuring Standby Interfaces priority_level Each member interface is assigned a priority number. The member interface with the highest priority number is the active interface for that standby group. Only the active interface uses the group IP address. If the priority option is specified without a priority number, the default value of 100 is used. shutdown (Optional) Shuts down the specified standby group (Standby Group 1, 2, 3, or 4).
Appendix E CLI Commands Other CLI Commands The following example shows how to add two Fast Ethernet interfaces to Standby Group 1 and then assign each of these member interfaces a priority within the group: 1. Add a Fast Ethernet interface (slot 0/port 0) to Standby Group 1 and assign a priority of 150. ServiceEngine(config)# interface FastEthernet 0/0 ServiceEngine(config-if)# standby 1 priority 150 2.
Appendix E CLI Commands Other CLI Commands Syntax Description browse Browses the cdnfs directories and files. cleanup Cleans up the unwanted entries in the cdnfs. info Summarizes the information about unwanted entries without starting the cleanup process. start Starts the cleanup of unwanted entries in the cdnfs. stop Stops the cleanup of unwanted entries in the cdnfs. The CDNFS cleanup command is an EXEC command.
Appendix E CLI Commands Other CLI Commands reformat Performs a low-level format of the SCSI, IDE, or SATA disks and remaps disk errors. diskname Name of the disk to be added (disk01, disk02, and so on.) unuse Stops applications from using a disk drive. diskname Name of the disk to be added (disk01, disk02, and so on.) The disk commands are EXEC commands. The disk reformat diskname EXEC command performs a low-level format of the SCSI, IDE, or SATA disks.
A P P E N D I X F URL Signing and Validation This appendix describes the URL signing and validation method for the Cisco Internet Streamer CDS. This appendix contains the following sections: • Introduction, page F-1 • Configuring the CDS for URL Signing, page F-2 • URL Signing Script, page F-2 • Understanding the Signing Procedure , page F-5 Introduction The Cisco Internet Streamer CDS accepts and fulfills requests for video content from client devices in the form of content URLs.
Appendix F URL Signing and Validation Configuring the CDS for URL Signing CDS has incorporated an open and well-documented signing mechanism that uses standard hashing schemes. The URL signing mechanism offers the flexibility to either use the provided signing script, or you can develop a signing application in the platform or language of your choice, as long as it adheres to the specified format.
Appendix F URL Signing and Validation URL Signing Script import time import sys def sign_url(url,key): """ Signs url using key and returns the signed URL with the signature appended. """ # Generate a MD5 hash of the key string (not the url) foo = md5.new(key) # Update the hash generated with the url string # This effectively means concatenating key and url and generating # a hash for the two foo.update(url) # Get the digest in hex format (human readable) return url+foo.
Appendix F URL Signing and Validation URL Signing Script url URL to sign. client-ip IP address of the client for which this URL is being signed, in dotted decimal format (A.B.C.D). The signed URL will be rejected if sent from any other client if signature validation is enabled. expiry-delay-seconds Seconds (from now) when the URL expires. The request will be rejected if the time period has passed when the URL is validated at the device.
Appendix F URL Signing and Validation Understanding the Signing Procedure The following two devices are synchronized: • Device 1: – Local Time: 11:00:59 AM, October 12, 2008 – Time Zone: PST • Device 2: – Local Time: 2:00:59 PM, October 12, 2008 – Time Zone: EST Understanding the Signing Procedure To customize the URL signing script for your portal, or to write your own signing application in the platform and language of your choice, and still be able to validate URLs within the CDS, follow the steps
Appendix F URL Signing and Validation Understanding the Signing Procedure Cisco Internet Streamer CDS 2.0-2.
A P P E N D I X G Testing the Internet Streamer CDS This appendix covers the steps to test the CDS by using the different media players.
Appendix G Testing the Internet Streamer CDS Testing the Web Engine Step 1 In a web browser on a 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 G-1 shows the initial URL on the left and the redirection on the right.
Appendix G Testing the Internet Streamer CDS Testing the Web Engine 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 : 0 Reply Meta : 0 Alternate Media : 0 Others -----Num Lookups : 1 Lookup Errors :0 Streaming redirected requests : 0 WMT Liveness requests :0 Hierarc
Appendix G Testing the Internet Streamer CDS Testing the Web Engine 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 G-2), having cached the content as well.
Appendix G Testing the Internet Streamer CDS Testing the Web Engine 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.
Appendix G Testing the Internet Streamer CDS Testing the Web Engine 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 : 18 Total % of requests -----------------Client Errors : 0 0.00 Server Errors : 0 0.00 Http/0.9 Requests : 0 0.00 Http/1.
Appendix G Testing the Internet Streamer CDS Testing the Windows Media Streaming Engine 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 cache.
Appendix G Testing the Internet Streamer CDS Testing the Windows Media Streaming Engine Figure G-5 Step 5 Windows Media Player Statistics 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.
Appendix G Testing the Internet Streamer CDS Testing the Windows Media Streaming Engine Figure G-6 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 G-7). Figure G-7 Step 5 Windows Media Player Statistics To view the request flow, enter the show statistics wmt streamstat command on the SEs. In this case, the request is received from NE-DEMO-SE2.
Appendix G Testing the Internet Streamer CDS Testing the Windows Media Streaming Engine 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 Testing Windows Media Live Content Playback Note Each live program uses a live delivery service to deliver the live program. See the “Configuring Programs” section on page 5-26 for more information.
Appendix G Testing the Internet Streamer CDS Testing the Movie Streamer Engine NE-DEMO-SE1# show statistics wmt streamstat Detailed Stream Statistics ===================================== Incoming Streams: ================= Stream-Id Type Source State 18872 LIVE RMT_HTTP Play http://171.70.222.171:0000 Bytes-Recd Duration 84150 241 Bandwidth Server-IP Url-Requested 288 171.70.22.
Appendix G Testing the Internet Streamer CDS Testing the Movie Streamer Engine Preparing Movie Streamer Content for Ingest The Movie Streamer delivers hinted MPEG-4, hinted 3GPP, 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.
Appendix G Testing the Internet Streamer CDS Testing the Movie Streamer Engine Figure G-12 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. Testing Preingested Movie Streamer Content Note Content must be preingested.
Appendix G Testing the Internet Streamer CDS Testing the Movie Streamer Engine Figure G-14 Step 5 QuickTime Player Statistics To view the request flow, display the statistics. For CDS Releases 2.0 and 2.1, enter the show statistics rtsp server movie-streamer all command. For CDS Releases 2.2 and 2.3, enter the show statistics movie-streamer all command.
Appendix G Testing the Internet Streamer CDS Testing the Movie Streamer Engine Overall Traffic ------Incoming Bytes: Outgoing Bytes: Total Bytes: Incoming Packets: Outgoing Packets: Total Packets: 0 Bytes 2103939 Bytes 2103939 Bytes 0 1403 1403 Movie Streamer Error Statistics Total --------------------------------------Server Error -------Internal Error: Not Implemented: Server Unavailable: Gateway Timeout: Others: 0 0 0 0 0 Client Error -------Bad Request: File Not Found: Session Not Found: Method No
Appendix G Testing the Internet Streamer CDS Testing the Movie Streamer Engine --------------------------------------Current Incoming bandwidth: Current Outgoing bandwidth: Current Total bandwidth: Average Incoming bandwidth: Average Outgoing bandwidth: Average Total bandwidth: Incoming Bytes: Outgoing Bytes: Total Bytes: 0 bps 0 bps 0 bps 0 bps 863879 bps 863879 bps 0 Bytes 14490660 Bytes 14490660 Bytes Testing Dynamically Ingested Movie Streamer Content When content requested by a client is not in t
Appendix G Testing the Internet Streamer CDS Testing the Movie Streamer Engine Average Total bandwidth: Incoming Bytes: Outgoing Bytes: Total Bytes: 407176 bps 12667891 Bytes 12609164 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 Inco
Appendix G Testing the Internet Streamer CDS Testing the Movie Streamer Engine 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 G-16) and click OK. In the example, this is “rtsp://rfqdn.cds.com/movieliveprogram.sdp.” Figure G-16 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 G-17).
Appendix G Testing the Internet Streamer CDS Testing the Flash Media Streaming Engine Current Total bandwidth: 744166 bps Average Incoming bandwidth: Average Outgoing bandwidth: Average Total bandwidth: 192102 bps 203980 bps 396082 bps Incoming Bytes: Outgoing Bytes: Total Bytes: 4478769 Bytes 4499370 Bytes 8978139 Bytes NE_DEMO-SE2# show statistics movie-streamer all Movie Streamer Request Statistics Total --------------------------------------Current RTSP sessions: 0 Current RIP connections: 0 Tot
Appendix G Testing the Internet Streamer CDS Testing the Flash Media Streaming Engine Testing Flash Media Streaming Preingested Content Note Content must be preingested. This was accomplished in the “Configuring Delivery Services” section on page 5-1. Note All RTMP calls must be in the following format: rtmp://rfqdn/vod/path/foo.
Appendix G Testing the Internet Streamer CDS Testing the Flash Media Streaming Engine Live Streaming ----UpStream BW : DownStream BW : UpStream Bytes : DownStream Bytes: Num of Instance Load: 0 kbps 0 kbps 0 0 0 Performance ----------Server Up Time : Mem Usage : Max Mem Usage : 816 S 5 % 5 % Cache ----Cache Cache Proxy Cache Hit : Miss : Case : HIt Percentage: Preposition ----------Preposition Hit: 0 0 0 0.
Appendix G Testing the Internet Streamer CDS Testing the Flash Media Streaming Engine Testing Flash Media Streaming Dynamically Ingested Content Note Testing 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.
Appendix G Testing the Internet Streamer CDS Testing the Flash Media Streaming Engine Max Concurrent : Total : 1 1 Live Streaming ----UpStream BW : DownStream BW : UpStream Bytes : DownStream Bytes: Num of Instance Load: 0 kbps 0 kbps 0 0 0 Performance ----------Server Up Time : Mem Usage : Max Mem Usage : 933 S 5 % 5 % Cache ----Cache Cache Proxy Cache Hit : Miss : Case : HIt Percentage: Preposition ----------Preposition Hit: 0 1 0 0.
Appendix G Testing the Internet Streamer CDS Testing the Flash Media Streaming Engine -------------------------------------------------1.71425e-01 293556 http://ofqdn.cds.com/vod/test_cache.flv Testing Flash Media Streaming—Live Streaming Note Live streaming using Flash Media Streaming is a Release 2.2 feature. Flash Media Streaming uses RTMP to stream live content by means of dynamic proxy. Configuration of live or rebroadcast programs is not required.
Appendix G Testing the Internet Streamer CDS Testing the Flash Media Streaming Engine 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.
Appendix G Testing the Internet Streamer CDS Testing the Flash Media Streaming Engine Cisco Internet Streamer CDS 2.0-2.
A P P E N D I X H Software Licensing Information This appendix provides software license information related to the Internet Streamer CDS. Notices The following notices pertain to this software license. OpenSSL/Open SSL Project This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.
Appendix H Software Licensing Information Notices 4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org. 5. Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear in their names without prior written permission of the OpenSSL Project. 6.
Appendix H Software Licensing Information Notices 4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: “This product includes software written by Tim Hudson (tjh@cryptsoft.com)”. THIS SOFTWARE IS PROVIDED BY ERIC YOUNG “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
Appendix H Software Licensing Information Notices Cisco Internet Streamer CDS 2.0-2.
