Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
cloudappliance/applinstallv1901 [2019_06_14 16:54] – [Preparation] steven | cloudappliance/applinstallv1901 [2019_07_03 15:52] – [Part I - Configure Networking] steven | ||
---|---|---|---|
Line 17: | Line 17: | ||
* Linux root user password | * Linux root user password | ||
* Appliance appladmin password | * Appliance appladmin password | ||
- | * SME File Fabric license key | + | * File Fabric license key |
- Access to request / update DNS names for appliance (recommended) | - Access to request / update DNS names for appliance (recommended) | ||
- Outbound mail relay information (recommended) | - Outbound mail relay information (recommended) | ||
Line 25: | Line 25: | ||
# 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 |
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. |