Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
cloudappliance/applinstallv1901 [2019_04_17 00:09] – [Introduction] stevencloudappliance/applinstallv1901 [2019_07_03 15:52] – [Part I - Configure Networking] steven
Line 5: Line 5:
 The SME File Fabric platform is shipped as a virtual appliance, and once you have deployed it into your environment you have to follow a few steps to get the product set up and ready for use. This document will walk you through the initial steps needed to get started. The SME File Fabric platform is shipped as a virtual appliance, and once you have deployed it into your environment you have to follow a few steps to get the product set up and ready for use. This document will walk you through the initial steps needed to get started.
  
-This document does not cover how to deploy the File Fabric in your virtual environment, only how to configure the software once the virtual appliance is deployed.+This document does not cover how to deploy the File Fabric in your virtual environment, only how to configure the software once the virtual appliance is deployed. For production deployments see [[sizingguide|]].
  
 For deployment on the Google Cloud Platform see [[googlecloud-gettingstarted]]. For deployment on the Google Cloud Platform see [[googlecloud-gettingstarted]].
Line 13: Line 13:
 You need to prepare/collect the following information before you can complete this configuration guide: You need to prepare/collect the following information before you can complete this configuration guide:
  
--        Linux smeconfiguser password + - Provided with trial email 
- +  * Linux smeconfiguser password 
--        Linux root user password +  * Linux root user password 
- +  * Appliance appladmin password 
--        Access to request / update DNS names for appliance +  * File Fabric license key 
- + - Access to request / update DNS names for appliance (recommended) 
--        Appliance appladmin password + - Outbound mail relay information (recommended) 
- + - Default storage system connectivity details 
--        SME File Fabric license key + - Active Directory service account, for connecting to AD (optional)
- +
--        Outbound mail relay information. +
- +
--        Default storage system connectivity details +
- +
--        Active Directory service account, for connecting to AD +
  
 # Part I - Configure Networking # Part I - Configure Networking
  
-Out of the box, the SME appliance comes configured for DHCP. For most production environments you want to assign a static address. You can easily do this with tools provided and installed on the appliance. If you have DHCP with dynamic DNS enabled, you should be able to simply connect to “appliance.yourcompany.tld”. If not, and you do not know the IP of the appliance, connect over a console session from your hypervisor.+Out of the box, the SME appliance comes configured for DHCP. For most production environments you will assign a static IP address. You can easily do this with tools provided and installed on the appliance. If you have DHCP with dynamic DNS enabled, you should be able to simply connect to “appliance.yourcompany.tld”. If not, and you do not know the IP address of the appliance, connect over a console session from your hypervisor.
  
 Once the SME appliance is booted and you are ready to start, you need to log in with “smeconfiguser” to the Linux shell and start the configuration server. Before we start the web-based configuration tool, let us update the hostname. Once the SME appliance is booted and you are ready to start, you need to log in with “smeconfiguser” to the Linux shell and start the configuration server. Before we start the web-based configuration tool, let us update the hostname.
© Copyright 2024 Nasuni.