Remote cache access
In planning for RCA, consider the following recommendations:
- The participating proxy servers need to be close to one another and connected
with high-bandwidth links (for example, FDDI, SP2 bus).
- Membership in the RCA array needs to be long-term so that the configuration
is as stable as possible.
- Proxy servers need to have similar capabilities (for example, CPU, memory
size, cache size).
- Network outages must be infrequent.
- There need to be fewer than 100 members in any array.
- All members of the array must use the same version of the Caching Proxy software.
Note:
If the proxies in the RCA array use different Linux® operating
systems (for example, SUSE and Red Hat), ensure that your "nobody" user has
the same UID on all its peers. Check the password and group file entries
in the /etc/ directory on each computer and assign the same UID to "nobody."
Remote cache access is not appropriate if any of these conditions is violated
or if different organizations manage different servers that are members of
the array.
Configuring remote cache access
To configure remote cache access, in the Configuration and Administration forms, select Cache Configuration -> Remote Cache Access. The fields in this form
define a named array that shares one logical cache. Enter the required information
for each member of the array.
To configure remote cache access by editing the proxy configuration file,
see the reference sections in Appendix B. Configuration file directives for the following
directives: