T-Series Traffic Director Installation, Configuration and Administration Guide
1-3
Traffic Director Architecture
(or multiple, as necessary) as the destination for this traffic. The T1000 uses
session
persistency
to ensure that traffic returning from the Internet is routed back to the same OSN
from which it originated.
The T1000 performs its load balancing function across multiple ingress and egress VLANs.
HTTP-based health-checking ensures that traffic will not be routed to unavailable nodes. In
the event of a full cluster failure, the T1000 can route traffic to a backup Internet path.
To ensure there is no single point of failure within the Unison cluster, Bytemobile suggests
deploying two T1000s in an active/failover fashion. The T1000 provides redundancy
support with both soft and hard failover. Soft failover events include scheduled maintenance
or other reasons. For hard failover (caused by link or hardware failure), the T1000
redundancy mechanism ensures that service disruption is minimized and user experience is
maintained.
Sizing a T1000/Unison Deployment
The T1000 Traffic Director is available in a range of hardware variations to support
different processing and network connection needs. These include the T1010, T1100, and
the T1200.
Each T1000 provides from 2 Gbps to 100 Gbps of non-blocking throughput (depending on
hardware model). The end-to-end throughput of a T1000 deployment with Unison will be
limited by the maximum capacity of a single application blade (OSN), which ranges from
400 Mbps when used to perform lossy media optimization, up to 1 Gbps if only lossless
media and web-only optimizations are applied.
The throughput measurement for a Unison cluster includes calculations for both ingress and
egress traffic passing through the load balancer. In other words, data moving from the
Internet to the subscriber must enter and exit the Unison cluster, traversing the T1000 twice.
Therefore, if the Unison cluster replaces a router handling 10Gbps of throughput, the load
balancer should be sized to handle 20Gbps of throughput.
A second sizing factor to consider is the number and type of data ports. The Unison data
plane may employ port trunking to increase throughput; a two-port trunk configuration
doubles the required number of T1000 ports on the subscriber and Internet sides. Support
for the optional T2100 Content Accelerator (video cache) may also require additional ports.
See
“T1000 Hardware Specifications and Options”
on page 1-6 for the available port
configurations.
Sizing T1000/T3100 Deployments
The Bytemobile T3100 Adaptive Traffic Manager includes an integrated load-balancing
function. When used in combination with T3100, the T1000 extends its advanced routing
protocol support to the T3100 data plane. For example, when used with the T1000, the
T3100 can support routing protocols such as Open Shortest Path First (OSPF) and Border
Gateway Protocol (BGP).
Sizing considerations for a T1000/T3100 deployment are similar to a T1000/Unison
deployment.
Содержание ByteMobile T1010
Страница 10: ...x T Series Traffic Director Installation Configuration and Administration Guide...
Страница 14: ...Contents xiv T Series Traffic Director Installation Configuration and Administration Guide...
Страница 150: ...B 10 T Series Traffic Director Installation Configuration and Administration Guide Appendix B Replacement Parts...
Страница 168: ...Glossary Glossary 12 T Series Traffic Director Installation Configuration and Administration Guide...
Страница 172: ...Index Index 4 T Series Traffic Director Installation Configuration and Administration Guide...
