Table of Contents
Advertisement
Media Flow Controller 2.0.5 Release Notes
object is received, Media Flow Controller delivers the partial file to the client and makes a
byte-range request to the origin for the remainder of the file. If the origin does not support
byte-range requests, it responds with a 200 OK response but does not deliver the byte-
range request and the partial file is not deleted.
Workaround: When your origin is known to not support byte-range requests, do not
configure the namespace origin-fetch cache-fill policy to be client-driven.
ID: 5609
Logging
•
Not all transactions are recorded in the accesslog.
When Media Flow Controller is running at transactions per second (TPS) greater than
40,000, some events are lost to the accesslog.
Workaround: None.
ID: 6210
Origin Server—Platform
•
Multiple bond interfaces are not supported.
Although you can configure more than one bonded interface, only the first one is usable.
Workaround: None.
ID: 6586
Release Installation for VXA Series: Upgrading to the
Latest Release
We recommend that you upgrade to the latest Media Flow Controller software before
configuring and using a VXA Series Media Flow Engine.
Important!
or available, for Media Flow Manager.
You obtain the Media Flow Controller Release 2.0.5 upgrade image from the Juniper
Networks Download page at:
http://www.juniper.net/support/products/mediaflow
Either download the image to your server, or copy the URL of the image.
See
"Upgrading (Web Interface)" on page 14
upgrading Media Flow Controller.
This upgrade is recommended for Media Flow Controller. It is not recommended,
Release Installation for VXA Series: Upgrading to the Latest Release
or
"Upgrading (CLI)" on page 15
Release 2.0.5
for details on
11
Advertisement
Table of Contents
Need help?
Do you have a question about the MEDIA FLOW CONTROLLER 2.0.5 - RELEASE NOTES REV 15-11-2010 and is the answer not in the manual?
Questions and answers