Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Configuring an FTP server
- Using Veritas Access as an Object Store server
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VII. Configuring cloud storage
- Section VIII. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Compressing files
- Section X. Reference
About FTP server options
Veritas Access lets you set various configurable options for the FTP server.
For the changes to take effect, restart the FTP server.
Table: FTP options
Option | Definition |
---|---|
allow_delete | Specifies whether or not to allow users to delete files on the FTP server. This option only applies to users. It does not apply to anonymous logins. Anonymous logins are never allowed to delete files. Enter yes (default) to allow users to delete files on the FTP server. Enter no to prevent users from deleting files on the FTP server. |
allow_non_ssl | Specifies whether or not to allow non-secure (plain-text) logins into the FTP server. Enter yes (default) to allow non-secure (plain-text) logins to succeed. Enter no to allow non-secure (plain-text) logins to fail. |
anonymous_login_dir | Specifies the login directory for anonymous users. Valid values of this parameter start with /vx/. Make sure that the anonymous user (UID:40 GID:49 UNAME:ftp) has the appropriate permissions to read files in login_directory. |
anonymous_logon | Tells the FTP server whether or not to allow anonymous logons. Enter yes to allow anonymous users to log on to the FTP server. Enter no (default) to not allow anonymous logons. |
anonymous_write | Specifies whether or not anonymous users have the [write] value in their login_directory. Enter yes to allow anonymous users to modify contents of their login_directory. Enter no (default) to not allow anonymous users to modify the contents of their login_directory. Make sure that the anonymous user (UID:40 GID:49 UNAME:ftp) has the appropriate permissions to modify files in their login_directory. |
chroot_users | Specifies whether users should be restricted to their home directories. A value of yes limits users to their home directory. A value of no allows users to view files in parent directories. Users are restricted by their homedir_path. If security is local, then chroot_users should be set to yes. |
create_homedirs | Specifies if home directories should be created when a user logs in, if the home directory does not exist. A value of yes allows FTP to create a user's home directory, if it does not already exist. If the value is no, then a home directory should exist for this user, and the user should have permissions to read and execute in this directory. Otherwise, the login fails. |
homedir_path | Specifies the location of the login directory for users. Valid values include any path that starts with /vx/. This option is required if user_logon is set to yes. |
idle_timeout | Specifies the amount of time in minutes after which an idle connection is disconnected. Valid values for time_in_minutes range from 1 to 600 (default value is 15 minutes). |
listen_ipv6 | Specifies whether the FTP service should listen on IPv6 for connections. Valid values for this parameter are yes or no. The default value is no. |
listen_port | Specifies the port number on which the FTP service listens for connections. Valid values for this parameter range from 10-1023. The default value is 21. |
max_connections | Specifies the maximum number of simultaneous FTP clients allowed. Valid values for this parameter range from 1-9999. The default value is 2000. |
max_conn_per_client | Specifies the maximum number of simultaneous FTP connections that are allowed from a single client IP address. Valid values for this parameter range from 1-9999. The default value is 2000. |
passive_port_range | Specifies the range of port numbers to listen on for passive FTP transfers. The port_range defines a range that is specified as startingport:endingport. A port_range of 30000:40000 specifies that port numbers starting from 30000 to 40000 can be used for passive FTP. Valid values for port numbers range from 30000 to 50000. The default value of this option is 30000:40000. |
security | Specifies the type of users that are allowed to log in to the FTP server. Enter nis_ldap (default) to allow users with accounts configured on NIS or LDAP servers to log in to the FTP server. Users that are created with the FTP> local user add command cannot log in. Enter local to allow users with accounts created with the FTP> local user add command to log in to the FTP server. NIS and LDAP users cannot log in. The ads option allows access to users configured on Windows Active Directory as specified in the CIFS> show command. NIS, LDAP, and local users are not allowed to log in. |
umask | Specifies the mask for permissions with which files or directories are created using FTP. If the file_umask is set to 177, then new files and directories are created with permissions 600, which defines rw--------. The owner of the file or directory has read and write permissions to the file or directory. Members in the users group do not have read or write permissions. |
user_logon | Specifies whether to allow FTP access for users. A value of yes allows normal users (non-anonymous users) to log in. If user_logon is set to yes, then the homedir_path also must be set or the FTP server cannot start. |