System Configuration
DME Admin Guide 91
DME) incoming HLS playback URLs. In this example, the identificationString we use is \/i\/ -
- which will uniquely identify the ‘/i/’ within the playback URL. Any URL with that string
will be processed as an Akamai HLS playback URL.
These settings (
hostname and identificationString) are specified on the Cache page within the
DME vbadmin GUI. Entering them requires the following format:
hostname::{80 if http, 0 otherwise}::{443 if https, 0 otherwise}::identificationString
Special attention should be paid to make sure that the notation matches this format,
including the double colon separators, without spaces.
For example, the following will treat any HLS (http or https) URL that contains ‘/i/’ to be
serviced by myCompany.akamaihd.net publishing point.
myCompany.akamaihd.net::80::443::\/i\/
Once entered, you can hover over the field to review the ports and
identificationString.
Special note about
identificationString: The identificationString must uniquely match the
playback URL associated with one and only one Akamai
hostname. If more than one Akamai
hostname is configured, the identificationString must be sufficiently unique to differentiate
between playback URLs. For example, the following entries:
myCompany-1.akamaihd.net::80::443::\/i\/
myCompany-2.akamaihd.net::80::443::\/i\/2
Both of these entries match the following presented URL:
http://dmeIP/i/2/streamName@streamID/master.m3u8
The system would use the
myCompany-1.akamaihd.net publishing point as opposed to the
myCompany-1.akamaihd.net version. This illustrates and stresses the need for unique
identificationString across all entries.
Mesh with Rev Caching Configuration
Me s h w ith Re v Cac h in g Co n fig u ratio n
DME Mesh Architecture
If you are using Rev with your DME(s), you will automatically utilize a shared cache that
takes advantage of the DME mesh architecture. The goal of this architecture is for all your
DMEs to communicate and reduce out-of-network bandwidth costs as a result. This, in turn,
will reduce bandwidth for both DME to Rev-cloud communications and within your network
topology from DME to DME. The DME mesh architecture also focuses on delivering
content as close to the edge as possible. Once the content is within the DME mesh
architecture, DMEs communicate between themselves to distribute the content effectively.
In terms of reducing network bandwidth, Vbrick’s first approach is to support reducing the
number of DMEs to which Rev will pre-positioned content. This reduces out-of-band
Note: This feature is available for general use, but Rev (or hybrid)
customers will begin to see Rev overwriting these stream specifications in
early 2017. VEMs customers can continue to use this feature.
If your Akamai hosts do not support port 443 (SSL), then you should not
enable the “Use HTTPs to Browser”.
To Next Page
Loading...
General