VBrick dme Admin Manual page 100

Multiple DME Configuration (Sample Network Diagram)
To access the Caching fields:

1. Navigate to
When configuring a DME, the first step is to designate one
content type. Also identify a
by one of the other parents.
In the following example for simplicity, only a
Content Specific Parents
matrices exist for each content type.
In order to minimize the amount of required information, the master parent (DME A)
should be at the "center" of the caching mesh, although you can actually designate any DME
as the master. Each DME should designate as its parent the DME most efficiently on the
path to the master parent. The master parent should designate all other DMEs that may be
generating content as
It is recommended (but not required) that any DMEs which can not be efficiently accessed
on the master parent path, be entered as
The table below shows the recommended configuration for the image displayed above.
Table 1. Recommended Sample Configuration
DME Default Parent
G E
F D
D A
A None
In another example, suppose a client co-located with DME E in the image above wants to
access an HLS stream initiated on DME G. Since this configuration defines DME A as the
Master Parent, the ultimate path for content delivery would be as follows (with asterisks
showing where caching occurs):
DME G* > DME E > DME D > DME A* > DME D* > DME E*
Note that if DME G was designated as an alternate source for DME E, the path would
simply be: DME G* > DME E*. Although this example designates a DME as master parent
(as often happens if the content to be cached is HLS or HDS where content is not sourced
from a DME, e.g. Smooth Streaming), the master parent will likely be an HTTP server.
88
>
System Configuration Caching.
Default Parent
. When
Content Specific Parents
(i.e. siblings).
Alternate Sources
Alternate Source
None
G
E, F, G
B, C, D, E, F, G
Content Specific Parent
for the DME for content not explicitly handled
for each DME is defined- no
Default Parent
are present, separate caching
.
Alternate Sources
for each
© Vbrick Systems, Inc.