-
Cisco ACNS Software Configuration Guide for Locally Managed Deployments, Release 5.5
-
Preface
-
Chapter 1: Introduction
-
Chapter 2: Understanding the Basics
-
Chapter 3: Deployment Scenarios for Standalone Content Engines
-
Chapter 4: Getting Started
-
Chapter 5: Performing Other Basic Tasks for Standalone Content Engines
-
Chapter 6: Configuring Transparent Redirection for Standalone Content Engines
-
Chapter 7: Configuring Conventional Caching Services for Standalone Content Engines
-
Chapter 8: Configuring RealMedia Services on Standalone Content Engines
-
Chapter 9: Configuring WMT Streaming Media Services on Standalone Content Engines
-
Chapter 10: Configuring Content Authentication and Authorization on Standalone Content Engines
-
Chapter 11: Configuring Content Preloading and URL Filtering on Standalone Content Engines
-
Chapter 12: Configuring ICAP on Standalone Content Engines
-
Chapter 13: Configuring the Rules Template on Standalone Content Engines
-
Chapter 14: Configuring Primary and Backup Proxy Servers for Standalone Content Engines
-
Chapter 15: Configuring Advanced Transparent Caching Features on Standalone Content Engines
-
Chapter 16: Updated Configuring Additional Network Interfaces and Bandwidth on Standalone Content Engines
-
Chapter 17: Configuring Administrative Login Authentication and Authorization on Standalone Content Engines
-
Chapter 18: Configuring AAA Accounting on Standalone Content Engines
-
Chapter 19: Creating and Managing IP Access Control Lists for Standalone Content Engines
-
Chapter 20: Viewing and Modifying TCP Stack Parameters on Standalone Content Engines
-
Chapter 21: Monitoring Standalone Content Engines and Transactions
-
Chapter 22: Troubleshooting
-
Appendix A: Content Engine GUI Menu Options
-
Appendix B: Reference Material for Standalone Content Engine Deployments
-
Index
-
Table Of Contents
Troubleshooting with HTTP Statistics Tools
Troubleshooting with the Debug Tool
Troubleshooting URL Performance
Troubleshooting with the HTTP CLI Client
Troubleshooting with the Log Viewing Tool
Troubleshooting with the Telnet Client
Troubleshooting with Traceroute
Troubleshooting with the WMT Diagnostic Tools
Troubleshooting
This chapter describes how to troubleshoot locally managed deployments (standalone Content Engines). This chapter contains the following sections:
•
Troubleshooting with HTTP Statistics Tools
•
•
•
•
•
•
•
Note
For information about troubleshooting a Content Router, Content Distribution Manager, or a Content Engine that is registered with a Content Distribution Manager (as opposed to standalone Content Engines that are not registered with a Content Distribution Manager), see the Cisco ACNS Software Configuration Guide for Centrally Managed Deployments, Release 5.5.
Overview
Troubleshooting is a process of elimination, testing, and validation. It often requires you to use prior knowledge of network topology and business policies, apply protocol knowledge and application behavior, and work with network and application teams to resolve a problem.
Common problems can often be resolved by finding answers to questions such the following:
You can use the Web application troubleshooting tools described in this chapter to search out the root causes of many common problems.
Troubleshooting with HTTP Statistics Tools
Use the show statistics http savings EXEC command to verify HTTP bandwidth savings, as shown in the following example:
CE# show statistics http savingsStatistics - SavingsRequests Bytes-----------------------------------------------------------Total: 1559097021 6421538629735Hits: 1041965581 1890163375706Miss: 517131440 4531375254029Savings: 66.8 % 29.4 %Use the show statistics http performance EXEC command to verify HTTP performance as shown in the following example:
CE# show statistics http performanceStatistics - PerformanceAvg Min Max Last-------------------------------------------------------------Requests / Second: - - 432 199Bytes / Second: - - 18992735 703016Seconds / Request: 0.760 0.000 4291967.812 0.191Seconds / Hit: 0.083 0.000 4291367.331 0.030Seconds / Miss: 2.124 0.000 4291967.812 0.557-------------------------------------------------------------Object Size: 4118.8 Avg0 Min2147484671 Max3530.7 LastUse the show statistics http miss-reason EXEC command to show the reasons for a cache miss, as shown in the following example:
CE# show statistics http miss-reasonStatistics - No hit reasonsReason: No. of Requests---------------------------------------------------not_in_cache: 269562dmbuf_low: 0none_get_method: 0ftp_not_anonymous: 0http_not_anonymous: 0suspicious_url: 0ie_5_ims: 0has_if_match: 0has_invalid_if_range: 0has_if_unmodified_since: 0has_invalid_range: 0has_more_than_supported_range: 0has_pragma_no_cache: 1260has_authorization: 0has_cache_control_no_cache: 0is_https: 0invalid_ims: 0cert_check_fail: 0second_validation: 0invalid_ims_reply: 0ims_200_reply: 0xfs_open_error: 650has_unknown_length_transfer_pending: 0object_in_cache_older_than_clients: 0object_in_cache_expired_cannot_verified: 0different_protocol: 0other_error: 620Statistics - Validate reasonsReason: No. of Requests---------------------------------------------------reval_all: 0reval_text: 0max_age: 0min_fresh: 0max_stale: 0response_say_so: 0object_expired: 0reval_no_cache_req: 0rule_refresh: 0Statistics - No store reasonsReason: No. of Requests---------------------------------------------------dmbuf_low: 0none_get_method: 0ftp_not_anonymous: 0http_not_anonymous: 0suspicious_url: 0has_range: 0has_authorization: 0has_cache_control_no_store: 0invalid_ims: 0cert_check_fail: 0second_validation: 0invalid_ims_reply: 0url_too_long: 0http_0_9_reply: 0header_too_long: 0http_unknown_verion_reply: 0http_none_cachable_reply_status: 0http_unknow_reply_status: 0has_cookie: 270772object_too_big: 0has_pragma_no_cache: 46cache_control_no_cache: 46cache_control_no_store: 46cache_control_private: 0has_multipart: 0invalid_expire: 0invalid_last_modified: 0invalid_date: 0content_length_0: 0has_vary: 0transfer_encoding: 0three_to_two_way: 0xfs_open_error: 650has_unknown_length_transfer_pending: 0other_error: 620weird_server_pipe_though: 0incorrect_content_length: 0rule_no_store: 0Increasing the Cache Hit Rate
Use the following global configuration commands for cache tuning and transport tuning to increase the cache hit rate:
•
•
•
•
•
•
•
•
Troubleshooting with the Debug Tool
Use the debug http EXEC command to troubleshoot issues such as the following:
•
•
•
•
Troubleshooting URL Performance
To configure a Content Engine to monitor the performance of specific URLs, use the http monitor url url global configuration command.
This command enables you to specify up to 10 URLs that you want the Content Engine to monitor and allows you to specify the time interval (in seconds) for monitoring the specified URL(s), as well as the acceptable delay (in seconds) before the URL is retrieved. The Content Engine maintains statistics about the various response characteristics for each of the monitored URLs. (You can use the new show statistics http monitor command to view these statistics, as described later in this section.)
ContentEngine(config)# http monitor url ?WORD URL for monitoringThe http monitor url url command has two command options, the acceptable-delay and interval options. As the following sample output indicates, the acceptable-delay option is used to specify the acceptable delay in seconds (the maximum number of seconds that the specified monitored URL should be retrieved within). The default acceptable delay is 60 seconds.
ContentEngine(config)# http monitor url http://www.abc.com/ ?acceptable-delay Threshold time in seconds before which the URL should be retrieved.(default is 60 seconds)interval Interval in seconds for monitoring the URL.(default is 60 seconds)<cr>As the following sample command output indicates, the acceptable-delay option is used to specify the acceptable delay, which is the maximum number of seconds that the specified URL should be retrieved within.
ContentEngine(config)# http monitor url http://www.abc.com/ acceptable-delay ?<1-3600> Acceptable delay in seconds
Note
As the following sample command output indicates, the interval option specifies the monitoring interval (that is, how frequently the Content Engine should monitor requests for a specific URL). The monitoring interval is specified in seconds. The default monitoring interval is 60 seconds.
ContentEngine(config)# http monitor url http://www.abc.com/ acceptable-delay 100 interval ?<1-3600> Monitor interval in secondsIn the following example, the Content Engine is configured to monitor the URL named "http://www.abc.com/" using the default values (an interval of 60 seconds and an acceptable delay of 60 seconds):
http monitor url http://www.abccorp.com/In the following example, the Content Engine is configured to monitor the URL named "http://www.abc.com/." The Content Engine is configured to wait up to 100 seconds for the URL to be retrieved and to monitor requests for this URL every 100 seconds.
ContentEngine(config)# http monitor url http://www.abc.com/ acceptable-delay 100 interval 100If it takes more than 100 seconds for the URL to be retrieved, the specified acceptable delay is exceeded. The Content Engine tracks the response time (minimum and maximum delay time) as well as the number of times that the acceptable delay is exceeded for a particular URL. These statistics are shown in the output from the new show statistics http monitor EXEC command. (An example of the output from the show statistics http monitor EXEC command is provided below.)
To display statistics for the monitored URLs, use the statistics http monitor EXEC command. The following example shows the statistics that are reported for each of the monitored URLs:
ContentEngine# show statistics http monitorHTTP Monitor URL statistics---------------------------Monitor URL = http://www.abc.com/Total requests = 118Failed requests = 30Requests above acceptable delay = 37Minimum response time = 8.183 secondsMaximum response time = 210.021 secondsMonitor URL = http://www.abccorp.com/Total requests = 275Failed requests = 44Requests above acceptable delay = 26Minimum response time = 0.071 secondsMaximum response time = 164.061 secondsIn the command output shown above, note the following information:
•
•
The output of the show running-configuration EXEC command includes information about the URL monitoring configuration. In the following excerpt from the show running-configuration command output, this particular information is highlighted in bold:
ContentEngine# show running-configuration!!hostname sust-7320-ce1!http persistent-connections timeout 300http proxy incoming 8080http proxy outgoing preserve-407http tcp-keepalive enablehttp monitor url http://www.abc.com/ interval 100 acceptable-delay 100http monitor url http://www.abccorp.com/!ftp proxy incoming 8080!clock timezone US/Eastern -5 0...Only the non-default values are displayed in the output from the show running-configuration command. Consequently, because the Content Engine was configured to use the default values to monitor the URL "http://www.abccorp.com," the above sample output does not display these values for that URL.
To display a list of monitored URLs, including the interval and acceptable delay setting for each monitored URL, use the show http monitor EXEC command:
ContentEngine# show http monitorMonitor URL: http://www.abc.com/Monitor Interval: 100Acceptable Delay: 100Monitor URL: http://www.abccorp.com/Monitor Interval: 60Acceptable Delay: 60Troubleshooting with the HTTP CLI Client
In the ACNS 5.2 software and later releases, an HTTP CLI client is supported. This capability allows you to test connectivity and debug caching issues. The test-url EXEC command provides debugging capabilities to the end user from the Content Engine CLI. With this command, you can test the URL accessibility and connectivity through the web server and the proxy server. The functionality of the URL over the HTTP, HTTPS, and FTP protocols can be tested. This command tests the functionality of a URL over the HTTP and FTP proxy servers. The following command output is displayed to the standard output (the console):
ContentEngine# test-url ?ftp For request over FTPhttp For request over HTTPhttps For request over HTTPSTable 22-1 describes the test-url commands.
When using the test-url EXEC command, you can specify the test URL (test-url protocol test-URL EXEC command) in either of the following formats:
http://domain.com/path or http://user:password@domain.com/path
In the following example, the test URL (www.cisco.com) is an HTTP request, and the request succeeds:
ContentEngine# test-url http http://www.cisco.com--17:34:50-- http://www.cisco.com/=> `/dev/null'Len - 21 , Restval - 0 , contlen - 0 , Res - 134728056Resolving www.cisco.comdone.Connecting to www.cisco.com[192.168.0.0]:80... connected.HTTP request sent, awaiting response...1 HTTP/1.1 200 OK2 Date: Fri, 25 Jun 2006 17:09:06 GMT3 Server: Apache/1.0 (Unix)4 Content-Type: text/html5 Set-Cookie: CP_GUTC=172.16.0.0.133781088183346835; path=/; expires=T19-Jun-29 17:09:06 GMT; domain=.cisco.com6 Via: 1.1 Application and Content Networking System Software 5.5.17 Connection: Close(-1 to go)[<=> ] 0 --.--K/sen - 1185 ELen - 0 Keepalive - 0[ <=> ] 56,249 1.38M/s17:34:50 (1.38 MB/s) - `/dev/null' saved [56249]In the following example, the test URL (gmail.google.com) is an HTTPS request that fails because the host is not found:
ContentEngine# test-url https https://gmail.google.com head-only--17:43:13-- https://gmail.google.com/=> `/dev/null'Len - 25 , Restval - 0 , contlen - 0 , Res - 134728056Resolving gmail.google.com...Resolving gmail.google.com failed: Host not found.In the following example, the test URL is an FTP-over-HTTP request using the Content Engine as the FTP proxy for the request:
ContentEngine# test-url ftp ftp://1234567:pAB6rB7x@smartfilter.com use-ftp-proxy ?WORD Proxy-url. Format http://proxyIp:proxyPort orhttp://proxyUser:proxypasswd@proxyIp:proxyPortContentEngine# test-url ftp ftp://1234567:pAB6rB7x@smartfilter.com use-ftp-proxy172.16.0.0:8080Troubleshooting in Real Time
To obtain traffic output in real time, use the type-tail EXEC command with the follow option. This command can be used to follow any working.log or syslog.txt files. You can also use the tcpdump EXEC command to capture all of the traffic on a Content Engine interface.
The following example shows real-time output from the working log:
CE# type-tail working.log follow1143265877.603 18 10.82.163.18 TCP_IMS_HIT/304 148 GET http://www.cisco.com/swa/i/flyout_arrow_red.gif - NONE/- - ALLOW "-"1143265877.683 29 10.82.163.18 TCP_IMS_HIT/304 149 GET http://www.cisco.com/swa/i/spacer_grey.gif - NONE/- - ALLOW "-"1143265877.683 29 10.82.163.18 TCP_IMS_HIT/304 148 GET http://www.cisco.com/swa/i/flyout_arrow_red.gif - NONE/- - ALLOW "-"1143265877.690 6 10.82.163.18 TCP_IMS_HIT/304 149 GET http://www.cisco.com/swa/i/spacer_grey.gif - NONE/- - ALLOW "-"1143265877.792 45 10.82.163.18 TCP_IMS_HIT/304 148 GET http://www.cisco.com/swa/i/flyout_arrow_red.gif - NONE/- - ALLOW "-"1143265877.793 45 10.82.163.18 TCP_IMS_HIT/304 149 GET http://www.cisco.com/swa/i/spacer_grey.gif - NONE/- - ALLOW "-"1143265877.798 5 10.82.163.18 TCP_IMS_HIT/304 148 GET http://www.cisco.com/swa/i/flyout_arrow_red.gif - NONE/- - ALLOW "- "1143265877.802 239 10.82.163.18 TCP_MISS/200 238 GET http://www.cisco.com/swa/j/zag2_vs_log1.asc?Log=1&title=Cisco%20Systems,%20Inc&basepage=http://www.cisco.com/&cb=1143243947972 - DIRECT/www.cisco.com - ALLOW "-"1143265877.901 44 10.82.163.18 TCP_IMS_HIT/304 149 GET http://www.cisco.com/swa/i/spacer_grey.gif - NONE/- - ALLOW "-"1143265877.901 44 10.82.163.18 TCP_IMS_HIT/304 148 GET http://www.cisco.com/swa/i/flyout_arrow_red.gif - NONE/- - ALLOW "-"1143265914.190 123 10.82.163.18 TCP_MISS/200 3760 GET http://www.google.com/ - DIRECT/www.google.com - ALLOW "-"1143265914.881 89 10.82.163.18 TCP_REFRESH_HIT/304 8794 GET http://www.google.com/intl/en/images/logo.gif - DIRECT/www.google.com - ALLOW "-"1143265930.721 103 10.82.163.18 TCP_MISS/200 3760 GET http://www.google.com/ - DIRECT/www.google.com - ALLOW "-"1143265930.957 37 10.82.163.18 TCP_IMS_HIT/304 176 GET http://www.google.com/intl/en/images/logo.gif - NONE/- - ALLOW "-"Troubleshooting with the Log Viewing Tool
In the ACNS 5.2 software and later releases, you can use the less EXEC command to specify the filename of the ACNS software log that you want to view:
ContentEngine# less ?WORD file nameTroubleshooting with the Telnet Client
In the ACNS 5.2.1 software and later releases, a Telnet CLI client is supported. This Telnet client allows you to specify a destination port. This allows you to test websites by attempting to connect with Telnet to the website from the Content Engine CLI. To support this feature, the telnet EXEC command was added.
ContentEngine# telnet ?Hostname or A.B.C.D Remote host or IP addressTroubleshooting with Ping
To send echo packets for diagnosing basic network connectivity on networks, use the ping EXEC command:
ping {hostname | ip-address} | PING options
In the ACNS 5.2.1 software and later releases, the functionality of the ping EXEC command supports all of the standard ping options as command arguments. (For more information on the standard ping options, see the Linux man page.)
ContentEngine# ping ?LINE Destination Host or IP Address (or PING options)To use the ping EXEC command with the hostname argument, be sure that DNS functionality is configured on your Content Engine. To force the timeout of a nonresponsive host, or to eliminate a loop cycle, press Ctrl-C.
In the following example, the host with an IP address of 172.19.131.189 is pinged from the Content Engine CLI:
ContentEngine# ping 172.19.131.189PING 172.19.131.189 (172.19.131.189) from 10.1.1.21 : 56(84) bytes of data.64 bytes from 172.19.131.189: icmp_seq=0 ttl=249 time=613 usec64 bytes from 172.19.131.189: icmp_seq=1 ttl=249 time=485 usec64 bytes from 172.19.131.189: icmp_seq=2 ttl=249 time=494 usec64 bytes from 172.19.131.189: icmp_seq=3 ttl=249 time=510 usec64 bytes from 172.19.131.189: icmp_seq=4 ttl=249 time=493 usec--- 172.19.131.189 ping statistics ---5 packets transmitted, 5 packets received, 0% packet lossround-trip min/avg/max/mdev = 0.485/0.519/0.613/0.047 msIn the ACNS 5.2.1 software and later releases, the functionality of the ping command supports all of the standard ping options. (For more information on the standard ping options, see the Linux man page.)
ContentEngine# ping ?LINE Destination Host or IP Address (or PING options)Troubleshooting with Traceroute
Traceroute is a widely available utility on most operating systems. Much like ping, it is a valuable tool for determining connectivity in a network. Ping allows the user to find out if there is a connection between two end systems. Traceroute does this as well, but additionally lists the intermediate routers between the two systems. Users can therefore see the routes that packets can take from one system to another.
To find the route to a remote host, when either the hostname or IP address is known, use the traceroute EXEC command.
ContentEngine# traceroute yahoo.comtraceroute to 66.218.71.113 (66.218.71.113), 30 hops max, 38 byte packets************10 p3-3.paloalto-cr2.bbnplanet.net (4.0.26.13) 3.219 ms 2.001 ms 2.097 ms11 p7-1.paloalto-nbr2.bbnplanet.net (4.0.6.77) 3.133 ms 1.949 ms 2.076 ms12 p4-0.paloalto-nbr1.bbnplanet.net (4.0.5.65) 2.755 ms 2.204 ms 2.037 ms13 p1-0.paix-bi2.bbnplanet.net (4.0.6.98) 2.928 ms 2.146 ms 2.334 ms14 p1-0.xpaix17-level3.bbnplanet.net (4.0.1.70) 3.397 ms 3.631 ms 3.081 ms15 gige10-0.ipcolo4.SanJose1.Level3.net (64.159.2.42) 3.334 ms 2.999 ms 2.388 ms16 cust-int.level3.net (64.152.69.18) 3.871 ms 3.031 ms *17 ge-3-3-0.msr1.pao.yahoo.com (192.168.101.42) 3.695 ms ge-2-3-0.msr2.pao.yahoo.com (192.168.101.46) 6.998 ms *18 vl16.bas1.scd.yahoo.com (66.218.64.146) 6.282 ms 5.091 ms 5.162 ms19 w2.rc.scd.yahoo.com (66.218.71.113) 6.028 ms 5.782 ms 5.544 msTroubleshooting with the WMT Diagnostic Tools
In the ACNS 5.3.1 software and later releases, you can access the following three WMT diagnostic tools through the Content Engine CLI:
•
To access the asfhead tool, enter the show wmt diagnostics header-info stream-file EXEC command, as follows:
ContentEngine# show wmt diagnostics header-info stream-file wordwhere word is a local file.
•
The .nsc file is created when a multicast station is configured. This tool is useful for multicast debugging. To access the nschead tool, enter the show wmt diagnostics header-info nsc-file EXEC file, as follows:
ContentEngine# show wmt diagnostics header-info nsc-file .nsc-filenameThe following is a sample annotated output from the show wmt diagnostics header-info stream-file EXEC command. In this example, this command is used to display the headers of a .wmv file named 256.wmv. Annotations about this sample command output are highlighted in boldface text and enclosed within parentheses.
ContentEngine# show wmt diagnostics header-info stream-file 256.wmvDescription object:VBR info object (2 streams) (VBR: variable bit rate file)streamid 1 bitrate 34319 (0000860f) (in this file there are 2 bit rates)streamid 2 bitrate 195798 (0002fcd6)Global properties object:GUID = f9 dd df 7e 6c 80 85 46 83 3c c1 23 4b 2f 4f 6b (object ID)File Size = 8104309 (object size)Total Packets = 2816 (total number of data packets)Time_mkin = 0x0000000001c0debcTime_mkout = 0x00000000a9e1af60Send duration = 2817510000 (Specifies the time needed to send the filein 100-nanosecond units)Broadcast Flag = 0Seekable Flag = 1Minimum Packet Size = 2877 (Specifies the minimum data packet size in bytes)Max Packet Size = 2877 (Specifies the maximum data packet size in bytes)Max Bitrate = 230117 (Specifies the maximum instantaneous bit rate inbits per second for the entire file)Unknown object:uuid: b5 3 bf 5f 2e a9 cf 11 8e e3 0 c0 c 20 53 65 len: 0x1600000000: 11 d2 d3 ab ba a9 cf 11 8e e6 00 c0 0c 20 53 6500000010: 06 00 00 00 00 00Extended Content Description Object (two entries):WMFSDKVersion (unicode) 7.00.00.1956WMFSDKNeeded (unicode) 0.0.0.0000Codec description object (2 streams) (audio and video codec information)Type = 0x2Description = Windows Media Audio V732 kbps, 32 kHz, stereoID = 61 01Type = 0x1Description = Windows Media Video V7ID = 57 4d 56 31Index:Index #0Interval = 10000000Max_pkt# = 9Entry = 286Stream ID = 0The following is an excerpt of sample output from the show wmt diagnostics header-info nsc-file EXEC command. In this example, this command is used to display the headers of the .nsc file named testmcast.nsc. Annotations about this sample command output are highlighted in boldface text and enclosed within parentheses.ContentEngine# show wmt diagnostics header-info nsc-file testmcast.nscPress Ctrl-C to abort, if no information is shown within 30 secs.[Address]Time To Live=0x00000005 (ttl)IP Address=233.33.33.33 (Multicast address that is configured.)IP Port=0x00000D10 (Multicast port that is configured.)Delivery Mode=0x00000002NSC Format Version=3.0 (version of NSC format)[Description]Description=Auto Archive=0x00000000Format1 id 4d2Description1=http://192.168.192.4:8080 (Source of the media stream,for example, the WMT server/encoder)header information:output_head() startingDescription object:clip: WMT Live testing (title of the stream, configuredon the WMT server/encoder)author: John Doe (author of the stream,configured on the WMT server/encoder)VBR info object (2 streams)streamid 1 bitrate 34995 (000088b3)streamid 2 bitrate 253711 (0003df0f)Global properties object:GUID = 33 36 59 e6 6a 7d 4e 49 99 5e cf 71 39 b9 61 54(guid: unique identifier of this stream)File Size = 2810 (size in bytes)Total Packets = 4294967295Time_mkin = 0x0000000001c4de45Time_mkout = 0x0000000000000000Send duration = 0Broadcast Flag = 1Seekable Flag = 0Minimum Packet Size = 1444Max Packet Size = 1444Max Bitrate = 288706Unknown object:uuid: b5 3 bf 5f 2e a9 cf 11 8e e3 0 c0 c 20 53 65 len: 0x70700000000: 11 d2 d3 ab ba a9 cf 11 8e e6 00 c0 0c 20 53 6500000010: 06 00 f1 06 00 00 a9 46 43 7c e0 ef fc 4b b2 2900000020: 39 3e de 41 5c 85 27 00 00 00 00 00 00 00 01 0000000030: 0c 65 00 6e 00 2d 00 75 00 73 00 00 00 cb a5 e600000040: 14 72 c6 32 43 83 99 a9 69 52 06 5b 5a 58 00 0000000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000000060: 00 00 00 00 00 00 7d 00 00 88 13 00 00 00 00 0000000070: 00 00 7d 00 00 88 13 00 00 00 00 00 00 00 03 0000000080: 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 0000000090: 00 00 00 00 00 cb a5 e6 14 72 c6 32 43 83 99 a9000000a0: 69 52 06 5b 5a 6e 00 00 00 00 00 00 00 00 00 00000000b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 68 ad 03000000c0: 00 88 13 00 00 00 00 00 00 68 ad 03 00 88 13 00000000d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00000000e0: 00 63 17 05 00 00 00 00 00 00 00 01 00 50 94 bd000000f0: c6 7f 86 07 49 83 a3 c7 79 21 b7 33 ad 02 00 0000000100: 00 00 00 5d 8b f1 26 84 45 ec 47 9f 5f 0e 65 1f00000120: c5 af 5b 77 48 84 67 aa 8c 44 fa 4c ca e0 00 0000000130: 00 00 00 00 00 04 00 00 00 01 00 0c 00 02 00 0200000140: 00 00 00 49 00 73 00 56 00 42 00 52 00 00 00 0000000150: 00 00 00 01 00 34 00 00 00 06 00 00 00 44 00 6500000160: 00 76 00 69 00 63 00 65 00 43 00 6f 00 6e 00 6600000170: 00 6f 00 72 00 6d 00 61 00 6e 00 63 00 65 00 5400000180: 00 65 00 6d 00 70 00 6c 00 61 00 74 00 65 00 0000000190: 00 4c 00 32 00 00 00 00 00 02 00 0c 00 02 00 02000001a0: 00 00 00 49 00 73 00 56 00 42 00 52 00 00 00 00000001b0: 00 00 00 02 00 34 00 00 00 0c 00 00 00 44 00 65000001c0: 00 76 00 69 00 63 00 65 00 43 00 6f 00 6e 00 66000001d0: 00 6f 00 72 00 6d 00 61 00 6e 00 63 00 65 00 54000001e0: 00 65 00 6d 00 70 00 6c 00 61 00 74 00 65 00 00000001f0: 00 4d 00 50 00 40 00 4c 00 4c 00 00 00 74 d4 0600000200: 18 df ca 09 45 a4 ba 9a ab cb 96 aa e8 0a 05 0000000210: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...000006e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000006f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000000700: 00 00 00 00 00 00 00Extended Content Description Object (3 entries):WMFSDKVersion (unicode) 9.00.00.2980WMFSDKNeeded (unicode) 0.0.0.0000IsVBR (bool) 0Codec description object (2 streams)Type = 0x2Description = Windows Media Audio 932 kbps, 32 kHz, stereo (A/V) 1-pass CBRID = 61 01Type = 0x1Description = Windows Media Video 9ID = 57 4d 56 33Multicast object (len 0x18):00000000: 50 0f 1d 54 4b 5b cf 11 a8 fd 00 80 5f 5c 44 2b00000010: 04 00 00 00 0a 00 00 00ContentEngine#
