At least one peer SteelHead must be set to always to estimate TCP bandwidth. When this setting is enabled on both SteelHeads, TCP bandwidth estimation does not occur. The server-side SteelHead can then detect the remote SteelHead during the connection setup and communicate with it over the satellite network. Rather than defining an in-path rule for every subnet that communicates with a remote SteelHead over a satellite link, it is easier to enable the global always setting on the remote SteelHead and this refl-peer setting on the server-side SteelHead. For example, suppose you have a large number of remote SteelHeads communicating with a server-side SteelHead. We recommend this setting on the server-side SteelHead in a satellite network. This setting makes satellite optimization easier to configure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |