EMC® VNX® Series Security Configuration Guide for VNX

How VNX for file works on the network

At its core, VNX for file is designed to function as a Common Internet File System (CIFS) and/or as a Network File System (NFS) file server. FTP and TFTP services are also available. The methods used to access VNX for file for these purposes (for example, the ports and protocols to use) are defined by standards. Thus, the VNX for file network presence is largely dictated by these standards. In addition, like any network device, there are ancillary services (for example, VNX Replicator, User Mapper, and such) that are expected by client systems and compatibility concerns dictate that VNX for file provide these services.

There are several ways of examining or describing the VNX for file network presence. One method is to enumerate the open network ports and describe their characteristics (for example, whether they are standard network services or VNX for file-specific services). Most of these ports are standard network ports whose external properties (for example, port number, authentication method, and service provided) are determined by existing standards. These standards are usually Request for Comments (RFCs), but they may be de facto standards as well. (Most often, this occurs in conjunction with CIFS services, where compatibility with Microsoft's file services is important.)

Another method to describe the VNX for file network presence takes a higher, more contextual approach such as what services are provided to end users (who access files on VNX for file), what services are provided to manage and monitor VNX for file, and what is available to work in a network environment (for example, the portmap or rpcbind service on port 111).

Another and more contextual approach of examining or describing the VNX for file network presence would be to list the applicable services being provided, such as the following:

• which services are provided to end users (who access files on VNX for file)
• which services are provided to manage and monitor VNX for file
• which services are available to work in a network environment (for example, the portmap or rpcbind service on port 111)