Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:dpi:dpi_components:mediaserver:cache_requirements:start [2020/02/05 16:45] – ↷ Links adapted because of a move operation lexx26 | en:dpi:dpi_components:mediaserver:cache_requirements:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== 1 Hardware requirements ====== | ||
- | {{indexmenu_n> | ||
- | The media server operates in connection with the installed DPI platform. [[en: | ||
- | To support media server, the DPI platform can be operated inline, or on the outbound traffic only, or even use PBR configuration on port 80 of the outbound traffic. | ||
- | |||
- | The media server is a computer with the dedicated software. It runs WEB server NGINX. It is connected into the operator' | ||
- | |||
- | The media server software requires CentOS 6.5. | ||
- | |||
- | Here are the minimal requirements for an operator with overall external bandwidth 100 Gb/s (expected cache load is up to 20% of the overall bandwidth): | ||
- | |||
- | - DPI platform (for outbound traffic only): SCAT-40 Complete | ||
- | - The computer: | ||
- | < | ||
- | 2 x Xeon E5-2650v2 | ||
- | 32 GB RAM | ||
- | 24 X 2TB HD 7200 RPM (RAID-10 | ||
- | 2 x 10GB Ethernet to deliver the content to subscribers | ||
- | 1 x 10Gb Ethernet for controls and content upload | ||
- | </ |