Zone Logic and Hierarchy
As noted, when adding a new zone or sub-zone, consider where your users and devices are located and/or how you want your content to be ingested and viewed on your network.
When you configure zone hierarchies, you provide a fail-over for your content distribution if your devices in a specific zone fail for whatever reason.
For example, in the image below, the zone is nested under the zone, which is nested under the zone (which in turn is nested under ).
Users should be directed to zones based on their IP addresses. Recall that IP address ranges for a zone may be specified when you
Add a Zone.
Using an example where a user is directed to the Washington, DC zone:
1. If Rev detects that the DME associated to the zone is available, then the user will be served the video off of that DME.
However, if Rev detects that the DME is unavailable in , it will direct the user up the zone hierarchy to the zone.
2. If Rev detects that the DME associated to the zone is available, the user will be served the video off of that DME.
However, if Rev detects that the DME is unavailable, it will direct the user up the hierarchy to the zone.
This will continue for as many levels of the zone hierarchy that have been configured. If the user cannot be served video off a device in the highest level of configured zones, the system will direct the user to the default zone as a last resort.
| Note: When using Rev in the cloud, users behind a corporate firewall will appear as if they are coming from the same external IP address. To prevent this and utilize Rev’s zone logic and hierarchy to maximum effect, Rev allows you to obtain an internal IP address. See: The DME User Location Service. |
For VOD files, Rev will fail up to the Rev File Store as a last resort if all the DMEs in your configured hierarchy are offline.
| Tip: If multiple DMEs are assigned to a zone, all DMEs will be tried before the next zone in the hierarchy will be attempted. |
See Also:
