F5 ARX-VE, Руководство по планированию

Страница: 31 / 64

Planning for a Namespace
ARX Site Planning Guide 1 - 25
• 25805/TCP, used by default for NTLM or NTLMv2 communication.
You can change this port from the ARX and from the Secure Agent’s
management interface.
If you have a Windows firewall on your DCs, you may need to manually
allow the ARX to access the above ports. We recommend leaving the
firewall disabled on Windows 2003 and Windows 2000 DCs; the firewall is
disabled by default on those releases.
Planning for a Namespace
If you have a single authentication domain for your network, a single
namespace for all of your storage typically makes sense. You can offer the
namespace through a single, consolidated VIP or through a series of VIPs,
depending on the configuration of your client subnets.
If you have multiple authentication domains, you must set up one
namespace for each.
Namespace Volumes
A namespace can contain up to three types of volumes: managed volumes,
direct volumes, and/or shadow volumes. A
managed volume keeps metadata
about all of its files and directories. Metadata is information about the
location of the files on back-end filers, among other things. The managed
volume uses the metadata to manage these file locations through namespace
policy. A
direct volume does not have any metadata and therefore does not
support any policy. A shadow volume is a copy of a managed volume,
possibly located on another ARX.
Maximum Namespaces and Volumes per Platform
The number of supportable namespaces, volumes, or shares is dependent on
the amount of memory and number of processors available for namespace
software. The ARX-1500 and ARX-2500 each have multi-core processors,
where each processor has a dedicated memory region. The ARX-4000 uses
an 8-way symmetric multiprocessor, which runs as 8 independent processors
each with a dedicated memory region. The ARX-2000 uses a 4-way
multiprocessor, which runs as 4 independent processors. The ARX-500 has
a single processor that runs management software in addition to namespace
processes. The ARX-VE is a virtual machine, and has a configurable
amount of processor time and memory.
The maximum namespaces, volumes, shares, and files per platform are
controlled by these system resources and by the license that you purchase
fromF5. The specific limits for each model are published here:
http://support.f5.com/kb/en-us/solutions/public/13000/100/sol13129.html