F5 ARX-VE, Planning Manual

Page: 20 / 64

Chapter 1
Site Planning
1 - 14
Using NTP
To support time-based policies, the clock on the ARX must be consistent
with the clock in its back-end servers. For example, an accurate clock is
needed to determine when to trigger age-based file migration or replication.
Accurate time is also important because the ARX keeps track of time-based
file attributes, such as last-modified time and create time.
In a redundant pair of ARX devices, time consistency between the
redundant peers is vital. A redundant peer may trigger a failover if an
improper clock setting makes a heartbeat appear to be out-of-date.
For these reasons and others, we strongly recommend using two or more
NTP servers for the servers, clients, and the ARX devices.
Automatically Discovering Your File Servers
Prior to installing an ARX, best practices recommend using
F5 Data Manager, a web-based application that can give you a detailed
understanding of your unique file storage configuration, contents, structure,
and usage. With this understanding, you can identify and apply data
management policies to create an efficient and cost-effective storage
environment.
Data Manager can give you a snapshot of your current environment as it
exists today, starting with file server discovery.
598,
5986 WINRM (Windows
Remote Management)
TCP
✓
High-Availability (HA)
49800 “rendezvous”
API (new in 5.2.0)
83 HTTP-API
✓
843 HTTPS-API
✓
Table 1.2 Ports Required by the ARX (Continued)
Port Service/Protocol
Inbound
VIP | XIP | MGMT Outbound
VIP | XIP | MGMT
Comment