F5 ARX-VE, Planning Manual

Page: 30 / 64

Chapter 1
Site Planning
1 - 24
Linux Samba
The ARX is often required to support file servers other than Windows,
Network Appliance, and EMC. Some environments can include file servers
that are Samba-based.
Samba is an open source suite of programs for Linux and UNIX that has
been in use since 1992. Samba provides file and print services for clients
using the SMB/CIFS protocol. Samba uses the winbind daemon to integrate
Linux/UNIX servers and desktops into Active Directory environments.
If you plan to deploy the ARX in a Samba environment, disable Samba
name mangling.
Windows 3.x and earlier used an 8.3 naming scheme, meaning that files had
eight places for a name, following by a dot, followed by three places for an
extension. To deal with files that have more than 8 characters followed by a
dot and then three characters for a file extension, Samba uses
name
mangling .
To disable name mangling, insert the following line in your mb.conf file in
the [global] section:
mangled names = no
The ARX supports Samba for multi-protocol namespaces without persistent
ACLs. Without POSIX ACL and extended attribute support, the ARX
namespace cannot support persistent ACLs.
If you intend to deploy Samba, work with your F5 SE and consult the latest
version of the F5 Data Solutions Compatibility Matrix for details on the
level of support provided.
The Data Solutions Compatibility Matrix (also called the Interoperability
Matrix) is included in the standard ARX documentation (v5.01.000 and
higher). There is also an F5 solution on askf5 linking to the document:
https://support.f5.com/kb/en-us/solu.../sol10909.html
Configuring Windows Domain Controllers
If you plan to offer CIFS services, your Windows Domain Controllers
(DCs) must have the following ports accessible from the ARX:
• 389/TCP, used by the ARX for a Kerberos health check.
• 88/TCP, required for Kerberos queries and responses.
To support NTLM or NTLMv2, each DC requires a separate Secure Agent
installation. Refer to the
ARX® Secure Agent Installation Guide for details
on this type of installation.
To support NTLM authentication and the Secure Agent, the DC firewall
must also allow the ARX to access the following ports:
• 139/TCP or 445/TCP, used by an ARX health check.