split_abr_encoding
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
split_abr_encoding [2019/04/26 07:38] – walkeradmin | split_abr_encoding [2023/03/09 22:35] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Split ABR Encoding ====== | ====== Split ABR Encoding ====== | ||
- | <color # | + | <color # |
+ | <color # | ||
\\ | \\ | ||
\\ | \\ | ||
+ | ---- | ||
+ | |||
+ | ==== Note ==== | ||
+ | \\ | ||
+ | As of v11 (v11.0.1.4 is what is being used in this document) it is possible to do <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | ==== Overview ==== | ||
---- | ---- | ||
When encoding ABR Profiles, there can be times when the number and complexity of profiles exceeds the capabilities of a single server, for example: | When encoding ABR Profiles, there can be times when the number and complexity of profiles exceeds the capabilities of a single server, for example: | ||
Line 18: | Line 27: | ||
</ | </ | ||
This profile list could not be produced by a single server (at the time of writing) and so two or three servers might be required, but as this is ABR, and all the profiles need to be I-Frame aligned, we need a way to achieve this. | This profile list could not be produced by a single server (at the time of writing) and so two or three servers might be required, but as this is ABR, and all the profiles need to be I-Frame aligned, we need a way to achieve this. | ||
+ | \\ | ||
\\ | \\ | ||
To overcome this we can use Split ABR encoding, where we can use several servers to encode different parts of the profile list, but still aligned in time. For this to work we need the following: | To overcome this we can use Split ABR encoding, where we can use several servers to encode different parts of the profile list, but still aligned in time. For this to work we need the following: | ||
\\ | \\ | ||
- | < | + | \\ |
- | Servers must be time synchronised | + | ==== Requirements ==== |
+ | ---- | ||
- | A multicast is used for synchronisation, | + | **Servers |
- | support multicasts. | + | |
- | Interfaces on all servers must be identical in name and operation (so if eth1 is the | + | **A multicast is used for synchronisation, |
+ | support multicasts.** | ||
+ | |||
+ | **Interfaces on all servers must be identical in name and operation (so if eth1 is the | ||
IP input, all servers must use the name eth1 for the interface, and it must be the | IP input, all servers must use the name eth1 for the interface, and it must be the | ||
- | input interface) | + | input interface)** |
- | </ | + | |
- | <color # | + | **While it is possible |
---- | ---- | ||
Line 37: | Line 50: | ||
\\ | \\ | ||
\\ | \\ | ||
+ | <color # | ||
+ | |||
+ | ---- | ||
+ | ==== Configuration ==== | ||
+ | ---- | ||
+ | |||
Create an ABR service as normal, but don't assign any servers to the configuration. | Create an ABR service as normal, but don't assign any servers to the configuration. | ||
\\ | \\ | ||
Line 120: | Line 139: | ||
\\ | \\ | ||
\\ | \\ | ||
- | ==== Alarm ==== | ||
\\ | \\ | ||
+ | \\ | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== Sync Alarm ==== | ||
\\ | \\ | ||
If you see this alarm, or similar | If you see this alarm, or similar |
split_abr_encoding.txt · Last modified: 2023/03/09 22:35 by 127.0.0.1