Setting Up File Services on FlashArray

User Guides for VMware Solutions

Audience
Public
Content Type
User Guides
Source Type
Documentation

The Server Creation Wizard greatly simplifies the configuration of a new file server. Currently, you can configure only one file server, referred to as the Default Array Server. We are working on adding the ability to define multiple File Services servers in the future.

The File Server Creation Wizard provides an easy-to-use configuration for File Services, including:

  • File Services Virtual Network Interface for resilient and high-performance communication with client computers. This interface (also known as a file VIF) typically consists of four or more physical Ethernet ports distributed across both FlashArray controllers. This setup protects the array from individual port or network link failures, as well as from controller failures.

  • File Services-Specific DNS Configuration for hostname resolution related to File Services. This additional, dedicated DNS configuration often uses the domain controller's DNS server, which contains records for all hostnames within Active Directory.

  • Active Directory Integration for delegated authentication of SMB and NFS users against your Active Directory domain.

FlashArray Network Link Aggregation

FlashArray File Services uses a virtual interface to communicate with the client environment for both resiliency and performance. The File Service virtual interface (also known as a file VIF) consists of four physical Ethernet ports, two per array controller. This design protects the array from individual port or network link failures, as well as from controller failures.

FlashArray supports two different file virtual interface configurations:

  • Physical Bonding (Recommended): The file virtual interface uses pairs of the same physical ports on both controllers. For example, ct0.eth4 and ct1.eth4, or ct0.eth5 and ct1.eth5.

  • LACP (Link Aggregation Control Protocol) Bonding: The file virtual interface uses a pair of LACP virtual interfaces, each on a different controller. An LACP virtual interface can use up to four physical Ethernet ports on the same controller. For example, ct0.eth4 and ct0.eth5.

Note: Your network infrastructure (switches and routers) must support the LACP standard (IEEE 802.3ad).
Warning:

FlashArray does not support separate routing tables for IP networks with overlapping address spaces. Purity treats multiple IP networks with identical or overlapping address ranges as a single network address range.

For example, using 192.168.0.x/24 for a management VIF and 192.168.1.0/24 for file services is acceptable, as each network maintains a distinct address space. However, configuring 192.168.0.x/22 for the management VIF and 192.168.1.0/23 for the file services VIF may cause failures. In such cases, traffic on one interface may be routed to the incorrect interface due to the overlapping network address space.

The wizard also supports Virtual LAN (VLAN) tagging, a networking technology that allows for the logical division of a network into multiple virtual networks, or VLANs, improving network security, performance, and flexibility.

FlashArray File Services-Specific DNS Configuration

The FlashArray File Server Wizard allows for multiple DNS server configurations:

  • Management DNS Configuration: This is the default configuration used for the resolution of all hostnames that the array requires (e.g., SMTP servers, other arrays). If no File Services-specific DNS configuration is set, these DNS servers will also handle File Services hostname resolution (e.g., Active Directory hostnames). FlashArray allows for only one management DNS configuration.

  • File DNS Configuration: This configuration is dedicated to resolving hostnames related to File Services. Often, this DNS configuration uses the domain controller's DNS server, which contains records for all hostnames within Active Directory. FlashArray allows for only one File DNS configuration.

FlashArray Active Directory Integration

By default, FlashArray uses local users and groups. Alternatively, you can join your array to an Active Directory or LDAP domain to enable user and group resolution via a directory server.

FlashArray does not currently support simultaneous lookups in both Active Directory and LDAP, and the SMB protocol does not support LDAP directory servers.

FlashArray can authenticate SMB and NFS users against an Active Directory domain. To do this, you must first create an account for the FlashArray in your target Active Directory domain. You can either create a new computer account for your array or use an existing one (pre-created by your Active Directory administrator) in Active Directory.