Today we continue to read the Riverbed optimization systems. We started discussing the clustering options. We saw that even the series connected appliances can have a benefit. They make use of the of the feature of RiOS to pass traffic through unoptimized when the appliance is over limit. The next appliance therefore gets the chance to optimize it.
Moreover a single RiOS device can be plugged in-path on multiple network links. It can support simultaneous in-path deployment on 6 copper links or 6 fiber links, or even a mixture. In addition, the separation of server side and client side connection forwarding enables RiOS devices to co-operate across multiple redundant links when there are too many links for a single device or multiple links that are too far apart for a single device.
The deployment can also be out of path for redundancy and scale. In this mode, a pool of devices work together to handle incoming requests. When a device fails, the requests are failed over to the next device which handles the requests. This kind of deployment can be done using a Layer 4 switch, WCCP or PBR.
We now look at the notion of an interceptor. This is an optional role for Riverbed devices. It functions as a specialized connection distribution device for a bank of RiOS devices. In addition to functioning as an L4 switch, it can perform asymmetric routing. Besides it eliminates the need for WCCP or PBR which are difficult to configure. The interceptor is typically used for large Datacenter deployments where it can be deployed without requiring any static route configuration. The interceptor can handle upto 1 million concurrent connections. Moreover it can scale up to 12Gbps and maintain uniform performance over extended duration by monitoring the peers.
RiOS also supports warm standby between designated primary and backup devices. Using automated data store synchronization, both the data segments and the references created via Data Streamlining are copied from primary to backup appliance. On failovers, the backup functions as a hot data store and can begin serving immediately.
Moreover a single RiOS device can be plugged in-path on multiple network links. It can support simultaneous in-path deployment on 6 copper links or 6 fiber links, or even a mixture. In addition, the separation of server side and client side connection forwarding enables RiOS devices to co-operate across multiple redundant links when there are too many links for a single device or multiple links that are too far apart for a single device.
The deployment can also be out of path for redundancy and scale. In this mode, a pool of devices work together to handle incoming requests. When a device fails, the requests are failed over to the next device which handles the requests. This kind of deployment can be done using a Layer 4 switch, WCCP or PBR.
We now look at the notion of an interceptor. This is an optional role for Riverbed devices. It functions as a specialized connection distribution device for a bank of RiOS devices. In addition to functioning as an L4 switch, it can perform asymmetric routing. Besides it eliminates the need for WCCP or PBR which are difficult to configure. The interceptor is typically used for large Datacenter deployments where it can be deployed without requiring any static route configuration. The interceptor can handle upto 1 million concurrent connections. Moreover it can scale up to 12Gbps and maintain uniform performance over extended duration by monitoring the peers.
RiOS also supports warm standby between designated primary and backup devices. Using automated data store synchronization, both the data segments and the references created via Data Streamlining are copied from primary to backup appliance. On failovers, the backup functions as a hot data store and can begin serving immediately.
No comments:
Post a Comment