Deploying the virtual Appliance
Read this section to learn how to deploy the Virtual Appliance in one of the supported environments.
Information to gather for install
- Internal IP address for the appliance, along with gateway and DNS settings.
- Public IP to be used for NAT when services are available on the internet.
- Url to be used for the site ( files.example.com ).
- SSL certificate to be used for the website.
- RSA key to be used for securing SFTP.
The Virtual Appliance is tested and supported in the following environments:
- VMware vCenter 5.5, 6.0
- VMware ESXi 5.5, 6.0
- Microsoft HyperV
- Amazon AWS
- Microsoft Azure
- Linux KVM
Download the Virtual Appliance
SmartFile provides the virtual appliance for download as an Open Virtualization Archive (OVA) file. This format is importable in most formats. Below is a list of the best file format to use for your environment.
Appliance Minimum Requirements
Our appliance requires the following requirements to run in any of the above platforms.
CPU: 4 cores at 2.4 GHz or Greater
Memory: 10 GB of memory
Primary Disk Drive: 64 GB
Data Disk Drive: This is up to the customer it is recommended to be as large as your environment can support. All data on the appliance is saved to this drive. We support a maximum of 13 TB.
For AWS deployments we require a minimum c5.xlarge instance for our AMI to be deployed to. In addition to the instance you will require an additional EBS volume for storing.
For Azure instances we require a minimum of B4MS instance.
Depending on your user load you may wish to increase these resources.
The virtual appliance is deployed with the expectation that the appliance will be publicly available. It is also assumed that it will be deployed behind a corporate firewall and access granted to it internally. It is highly recommend that the appliance be deployed behind a corporate firewall.
External Incoming Port Requirements
|ICMPv4||Used for verifying the server is up and accessible.|
|80||Used for non secure web GUI access to the application. Does not need to be made available publicly.|
|443||Used for secure Web GUI access to the application. Does not need to be made available publicly. Also used by the API.|
|21||Used for FTP access to the appliance. Does not need to be open if the FTP service is not used externally.|
|22||User for SFTP access to the appliance. Does not need to be open if the SFTP service is not used externally.|
|990||Used for FTPS access to the appliance. Does not need to be open if the FTPS service is not used Externally.|
Internal Incoming Ports requirements
|ICMPv4||Used for verifying the server is up and accessible.||YES|
|80||Redirects to HTTPS port 443||YES|
|443||Used for secure Web GUI access to the application. Does not need to be made available publicly. Also used by the API.||YES|
|21||Used for FTP access to the appliance. Does not need to be open if the FTP service is not used externally.||NO|
|22||User for SFTP access to the appliance. Does not need to be open if the SFTP service is not used externally.||NO|
|990||Used for FTPS access to the appliance. Does not need to be open if the FTPS service is not used Externally.||NO|
|10022||Used for support sessions to the appliance. ( for support sessions SSH access is required running on port 10022 )||YES|
|9002||Used to access the appliance manager web GUI ( for setup and management of the appliance )||YES|
|2377||Cluster communication for HA multinode deployments||NO|
|7946||TCP and UDP: for multinode communication among nodes||NO|
|4789||UDP: For multinode communication among nodes||NO|
Internal Outgoing Port Requirements
|443||Used to download updates from our servers||YES|
|53||DNS services to resolve names for updates||YES|
|25||For sending notification emails to end users||NO|