Changes

5,579 bytes added , 00:52, 13 December 2023

add info from Bug re graphic res

Line 1: Line 1:

<noinclude>{{Languages}}</noinclude>

−

===Installing And Configuring Your SME Server Software===

==Installing And Configuring Your SME Server Software==

The following sections explain in detail the process of installing the SME Server software.

−

{{Note box|If you have previously installed and configured a server and are reinstalling the software, please be aware that you should use the procedure described ~~in section 1.5.3. Upgrading From A Previous Version~~ in order to preserve your existing configuration and data. Simply performing a new installation will erase all previously existing user accounts, user directories, i-bay contents and web site and configuration parameters. If you have not already done so, you may wish to back up the contents of your server onto one of your desktop computers. You can do so easily by selecting "Backup or restore" from the server manager, as explained in chapter 10.1.||

{{Note box|It is recommnded that a user take note of details in the [[https://wiki.koozali.org/SME_Server:10.0#Installing | Release Notes for SME10 - Installing ]] and in particular the section covering [[https://wiki.koozali.org/index.php?title=SME_Server:10.0&mobileaction=toggle_view_desktop#Known_issues_upgrade_from_SME9 | Known Issues ]]

}}

{{Note box|If you have previously installed and configured a server and are reinstalling the software, please be aware that you should use the procedure described [[#Upgrading_From_A_Previous_Version|here]] in order to preserve your existing configuration and data. Simply performing a new installation will erase all previously existing user accounts, user directories, i-bay contents and web site and configuration parameters. If you have not already done so, you may - depending on the size of the data - wish to back up the contents of your server onto one of your desktop computers. You can do so easily by selecting "Backup or restore" from the server manager, as explained in chapter 10.1.||

}}

===Install Targets===

−

Koozali SME Server 10 can be installed on physical or virtual hardware, either on a local virtual host such as Proxmox or Virtual Box, or in a cloud instance.

Koozali SME Server 10 can be installed on physical or virtual hardware, either on a local virtual host such as Proxmox, Linux KVM or Virtual Box, or in a cloud instance.

The installer will generally pick the correct options for the install but these can be overwritten if you have another preference, please see the install boot options below and the RAID page https://wiki.koozali.org/Raid for more details.

−

When the installer sees a single disk whether on virtual or physical hardware it will not install any RAID functions for obvious reasons, but LVM will be selected: ~~on virtual hardware~~ you may prefer to not use LVM depending on your deployment plan. This can be ~~specifed~~ as shown below.

When the installer sees a single disk whether on virtual or physical hardware it will not install any RAID functions for obvious reasons, but LVM will be selected: you may prefer to not use LVM depending on your deployment plan. This can be specified as shown below.

−

====Licensing Terms and Conditions====

===Licensing Terms and Conditions===

In installing the SME Server software, you are agreeing to the open source licensing terms and conditions associated with it. You can read these terms and conditions in Chapter 1.2. of this guide under the title Software Licensing Terms and Conditions .

−

====RAID Support (Disk Mirroring and striping)====

===RAID Support (Disk Mirroring and striping)===

With SME Server, you have the ability to set up disk mirroring and striping, also called RAID. In disk mirroring, your data is written to two separate hard disks installed in your server. One is the mirror of the other. Should the primary disk experience a hardware failure, the mirror disk will continue operations as if nothing had happened. All of your data will be protected from the single disk failure. This does NOT replace the need for backups! Other levels of RAID offer similar protections with more disks incorporated.

Line 28: Line 32:

=====Hardware RAID=====

−

With hardware RAID, you use a special RAID disk controller to perform the actual striping across multiple disks. As RAID is performed in hardware, the performance may be faster than software mirroring, depending on the ~~capabilites~~ of the various hardware. Additionally Hardware RAID can simplify configuration and array rebuilds because to the operating system, the entire RAID disk system looks like one single disk. You should be able to use any supported SATA or SCSI hardware RAID controller. NB: other options than mirroring may be supported by the controller.

With hardware RAID, you use a special RAID disk controller to perform the actual striping across multiple disks. As RAID is performed in dedicated hardware, the performance may be faster than software mirroring, depending on the capabilities of the various hardware. Additionally Hardware RAID can simplify configuration and array rebuilds because to the operating system, the entire RAID disk system looks like one single disk. You should be able to use any supported SATA or SCSI hardware RAID controller. NB: other options than mirroring may be supported by the controller.

===Upgrading From A Previous Version===

−

** If you are going to ~~use hardware RAID~~, ~~you should NOT choose Install - Dual hard disk~~ with software RAID-1 mirroring during the installation process described in section 1.5.4. Installing the Software. (Doing so will enable software mirroring.) Instead, you should do a regular installation of the ~~software~~. ~~See [[Booting]]~~

Upgrading is somewhat more complex than a clean install on a system as settings and data from the old system need to be preserved. For this reason, we start with the Upgrade procedures.

−

~~====Upgrading From A Previous Version====~~

Please make sure to be familiar with - https://wiki.koozali.org/SME_Server:10.1 - in particular Known issues updating from SME10.0

=====Upgrade from 9.x to 10.x=====

−

{{Note box|msg=In-place upgrades to SME 10.x using yum or CD are ~~not~~ supported due to design constraints imposed by CentOS.

{{Note box|msg=In-place upgrades to SME 10.x using yum or CD are NOT supported due to design constraints imposed by CentOS and the move to systemd.

−

It is necessary to backup the old server & then restore to the new server. Contribs will need to be reinstalled.}}

It is necessary to backup the old server and then restore to the new server. Contribs will need to be reinstalled.}}

−

~~The~~ simplest way to do this is via a Console Backup to ~~attached~~ USB disk on the old server. Alternatively use one of the Backup & Restore options available in ~~server manager~~ panel, ie backup to desktop, or backup to workstation (either to attached USB or network share). Other non standard options exist to Backup virtual servers that do not have USB ports etc, & Restore to similar virtual systems, eg using ~~ssh~~.

With a physical server the simplest way to do this is via a [[SME_Server:Documentation:Administration_Manual:Chapter6#Option 8: Perform backup to USB device|Console Backup]] to a USB disk attached to the old server. Alternatively use one of the Backup & Restore options available in the Server Manager panel, i.e. backup to desktop, or backup to workstation (either to attached USB or network share). Other non-standard options exist to Backup virtual servers that do not have USB ports etc, and Restore to similar virtual systems, e.g. using SSH. Many virtual servers can also be configured to pass-through USB ports from the host to the hosted machines allowing a USB drive to be mounted, but this is an advanced topic and cannot be covered here: consult the documentation of the virtual host system in use.

−

{{Tip box|msg=The Restore from USB on first boot function (on a newly installed SME 10 server), will only utilise backups that are saved as smeserver.tgz files, which are the Console ~~backup~~ to USB or the ~~server manager~~ backup to Desktop. The ~~server manager backup~~ to Workstation (either to USB or network share) creates a "backupdate.dar" type filename (or multiple split parts) & cannot be used to restore using the Restore on first boot function, it can only be used for restores from ~~server manager~~. The new install must have its backup to workstation configured as per the old install.}}

{{Tip box|msg=The Restore from USB on first boot function (on a newly installed SME 10 server), will only utilise backups that are saved as '''smeserver.tgz''' files, which are the [[SME_Server:Documentation:Administration_Manual:Chapter6#Option 8: Perform backup to USB device|Console Backup]] to USB or the Server Manager backup to Desktop. The Server Manager "Backup to Workstation" (either to USB or network share) creates a "backupdate.dar" type filename (or multiple split parts) and cannot be used to restore using the "Restore on first boot" function, it can only be used for restores from the Server Manager. The new install must have its backup to workstation configured as per the old install.}}

{{Note box|msg=It is highly recommended that USB drives to be used for backing up '''SME 9.x''' servers prior to an upgrade to 10.n be formatted with a Linux file system. When formatting a USB to use for restore it can be type FAT or FAT32, and is preferred to be ext3 or ext4. If ext4 it should '''not''' be formatted with an OS more recent than RHEL6 for SME9; this is because ext4 has seen multiple incompatible options added with time that are not back-compatible with earlier releases. So, the simple way is to mount the USB dive to the SME 9.x server you wish to back up and format it ext 3 or 4. Ensure that is is then unmounted. The USB drive must '''not''' be mounted before running console/Server Manager backup or the backup will fail to find the drive.}}

======<big>Upgrade via Console backup to USB drive</big>======

−

* Log in as admin & Backup the '''old server''' via a Console Backup to attached USB disk. This may take many hours if you have a lot of data on your server, depending on USB port speed, USB drive speed, & types of files being backed up ie whether already compressed or not etc. Typically for 250Gb of data on your server hard drive, 2 to 4 hours.

* Log in as admin and Backup the '''old server''' via a [[SME_Server:Documentation:Administration_Manual:Chapter6#Option 8: Perform backup to USB device|Console Backup]] to an attached USB disk. This may take many hours, even days, if you have a lot of data on your server, depending on USB port speed, USB drive speed, and types of files being backed up, i.e. whether already compressed or not etc. Typically for 250Gb of data on your server hard drive, 2 to 4 hours. Multiple terabytes may take multiple days.

−

* Install the SME 9.x OS ~~from CD~~ on the new hardware (on new server).

* Install the Koozali SME 10.x OS on the new hardware (on the new server).

−

* Select to do a Restore on first boot of the newly installed SME Server 9. Only attach USB containing the backup file, when asked on first reboot. Restore may take a few hours depending on data size etc. Make sure you wait for the Restore complete message.

* Select to do a Restore on first boot of the newly installed Koozali SME Server 10. Only attach the USB containing the backup file, when asked on first reboot. Restore may take a few hours or longer depending on data size etc. Make sure you wait for the Restore complete message.

======<big>Upgrade via server manager backup to Desktop or Workstation (USB or network)</big>======

−

* On the old server in ~~server manager~~, configure the required backup in the Backup or Restore panel. Schedule the backup to run at a suitable time. This backup can be to a workstation desktop for systems with a smaller amount of data, which creates a smeserver.tgz backup file, or to a locally connected USB drive or to a network share, & creates xx...xx.dar files, split into multiple parts if configured & data size is large. This may take many hours to run depending on data size etc.

* On the old server in Server Manager, configure the required backup in the Backup or Restore panel. Schedule the backup to run at a suitable time. This backup can be to a workstation desktop for systems with a smaller amount of data, which creates a smeserver.tgz backup file, or to a locally connected USB drive or to a network share, and creates xx...xx.dar files, split into multiple parts if configured & data size is large. This may take many hours to run depending on data size, file size, etc.

−

* On the new ~~SME9~~ server, manually configure the '''identical''' backup job in the ~~server manager~~ Backup or Restore panel. The backup job MUST point to the exact same location that the original backup file is saved to.

* On the new Koozali SME10 server, manually configure the '''identical''' backup job in the Server Manager Backup or Restore panel. The backup job MUST point to the exact same location that the original backup file is saved to.

−

* Select the Restore function within ~~server manager~~ & select the full backup you want to restore from. This may take many hours to run depending on data size, network speed etc. Make sure you wait for the Restore complete message.

* Select the Restore function within Server Manager & select the full backup you want to restore from. This may take many hours to run depending on data size, network speed etc. Make sure you wait for the Restore complete message.

−

* Basic networking configuration of the new and/or restored ~~SME9~~ server will be required if different from original server.

* Basic networking configuration of the new and/or restored Koozali SME 10 server will be required if different from original server.

======<big>Upgrade using command line restore via ssh or USB</big>======

−

* It is possible to use the command line to transfer a backup file via ssh (or USB) to the new server & then to run the restore. Standard & non standard backup concepts & procedures are outlined in the Backup server config Howto, http://wiki.contribs.org/Backup_server_config If using any non standard method, then the integrity of your SME server data cannot be guaranteed.

* It is possible to use the command line to transfer a backup file via ssh (or USB) to the new server and then to run the restore. Standard and non standard backup concepts and procedures are outlined in the Backup server config Howto, http://wiki.contribs.org/Backup_server_config If using any non standard method, then the integrity of your SME server data cannot be guaranteed.

−

* To do a standard backup & restore using CLI, on the old server log in as admin & perform the Console Backup to USB drive (to a locally connected USB). Alternatively using suitable commands, a smeserver.tgz backup file could be created & saved to / folder, refer Howto.

* To do a standard backup & restore using CLI, on the old server log in as admin and perform the Console Backup to USB drive (to a locally connected USB). Alternatively using suitable commands, a smeserver.tgz backup file could be created & saved to the / folder, refer Howto.

−

* Install the SME 9.x OS from CD on the new hardware (on new server).

* Install the Koozali SME 10.x OS from CD on the new hardware (on new server).

* Answer No when asked if you want to restore from USB during the first boot.

* If you created or have the backup file on the old server, transfer the smeserver.tgz backup file via ssh from your old server to your new server. Both servers must be connected & remote access enabled

Line 69: Line 78:

mount /media/usbdisk

cp /media/usbdisk/Backup-date-folder/smeserver.tgz /

−

(replace usbdisk with actual mount point name & Backup-date-folder with actual folder date name)

(replace usbdisk with actual mount point name and Backup-date-folder with actual folder date name)

* After the backup file has been copied to the new server, on the new server do:

cd /

Line 80: Line 89:

cd /

rm smeserver.tgz

−

*Note the backup & restore may take many hours to complete depending on data size etc.

* Note the backup & restore may take many hours or even days to complete depending on data size etc.

* After restore, the Configuration of the new server should be identical to the old server.

−

* Note with two servers connected during ssh copying operations, basic networking configuration of the new unrestored ~~SME9~~ server will need to be temporarily different to the old server to avoid clashes.

* Note with two servers connected during ssh copying operations, basic networking configuration (IP address at least) of the new unrestored SME10 server will need to be temporarily different to the old server to avoid clashes.

−

======<big>Migrate using the Lazy Admin Tools</big>======

Line 91: Line 99:

======<big>Reinstall Contribs after restore</big>======

−

Add on contrib ~~rpm~~ packages will need to be re-installed on the new SME 10.x server as these are NOT included in the backup. Contrib data & configuration is included in backups & will be restored, but its usefulness will depend on the contrib design being unchanged between older (SME9/el6) & SME10/el7 package versions. Due to major changes in the underlying system files, this may not work, and is contrib dependent.

Add-on contrib RPM packages will need to be re-installed on the new SME 10.x server as these are NOT included in the backup. Contrib data and configuration is included in backups and will be restored, but its usefulness will depend on the contrib design being unchanged between older (SME9/el6) & SME10/el7 package versions. Due to major changes in the underlying system files, this may not work, and is contrib dependent.

======<big>Delete and Reconfigure Manual tweaks</big>======

Other manual tweaks e.g. custom templates or scripts, will need to be deleted and recreated in line with SME 10.x template code and base code.

−

~~======<big>Delete & Reconfigure Manual tweaks</big>======~~

Where extensive modifications have been made to the "old server (eg SME9.2)", it is recommended to carry out a test backup and restore upgrade first, to discover any problems and ascertain suitable fixes and workarounds. Removing contribs and custom templates before upgrading is recommended.

−

~~Other manual tweaks~~ eg ~~custom templates or scripts~~, ~~will need~~ to ~~be deleted & recreated in line with SME 10~~.~~x template code & base code~~.

−

~~Where extensive modifications have been made to~~ the "old server (eg SME9.2)", it is recommended to carry out a test backup & restore upgrade first, to discover any problems & ascertain suitable fixes & workarounds. Removing contribs & custom templates before upgrading is recommended.

===Installing the Software===

−

~~====Installing~~ the ~~Software====~~

{{Tip box|For Koozali SME Server 10 there are options that can be appended to the initial command to specify whether LVM, RAID and XFS are used. See below.}}

−

{{Tip box|You have some command Line Options that you can use to set some parameters such as LVM (activated by default), '''SME9 only''' - software Raid option (none,0,1,5,6). You can use the function keys F1 to F5 to get more information about different boot options. see [[Booting]]}}

−

~~After showing the boot prompt for some time SME will start~~ the ~~installation process automatically. It will then afford you the opportunity~~ to ~~test the installation medium.~~

{{Tip box| A user reported install failing to complete with no readily found reason, went through a number of attempts finally found resetting systems Graphic Resolution to a lower than default, set to 800x600 enabled the install to complete without error see [[Bugzilla:12432]]}}

−

~~Afterwards you can choose which language you want to use for the following installation process.~~

−

{{Note box|If you are configuring your system with RAID1 support, notice that your step 4 below will be slightly different. If you skipped section 5.2 RAID1 Support (Disk Mirroring), it would be advisable to read it before proceeding.}}

After showing the boot prompt for some time SME will start the installation process automatically. By default the option to test the installation medium will be selected, and the system will then proceed to the graphical mode install. Alternatively you can select to go directly to the install, either in graphical or text mode.

In text mode: you choose which language you want to use for the following installation process.

'''Step 1''': Insert the USB or CD-ROM media.

−

'''Step 2''': You will be given the option of testing the media before beginning installation. Choose '''Test this media and install...''' to test the media and after success run the installer or choose the default ~~grpahical~~ install or the text mode install as you prefer. The graphical mode screens are shown below.

'''Step 2''': You will be given the option of testing the media before beginning installation. Choose '''Test this media and install...''' to test the media and after success run the installer or choose the top option for the default graphical mode install or the second option for the text mode install as you prefer.

{{Note box|The '''graphical mode''' screens are shown below. The '''text mode installer''' uses text-based screens but follows the same sequence: see [[Text-mode installer sequence]]}}

−

{{Note box|The ~~'''text mode installer''' uses text-based screens but~~ follows the same sequence}}

{{Note box|The installation shown below is for the full iso image. The net install image follows the same sequence in either mode but the network MUST be enabled for the machine to download its executables}}

[[Image:1.initialinstallmenu-noselection.jpg|center|850px]]

−

{{Note box|At this time if you select the first menu item and press the tab key you will be able to ~~add~~ options ~~such as nolvm, noraid~~ to the menu items commands}}

{{Note box|At this time if you select the first menu item and press the tab key you will be able to append options to the menu items commands.

Currently these are:

*nolvm - Do not enable LVM

*noraid - Do not enable RAID (this is the default for a single target disk installation)

*noxfs - Do not use XFS as the default filesystem as is standard for CentOS 7

These are added to the end of the line starting with '''vmlinuz''' with a space left between them. An example screen for the '''nolvm''' option is shown below.

}}

[[Image:2.selectmenu1-tab-nolvm.jpg|center|850px]]

−

'''Step 3''': Select the language you would like to use during the installation process.

'''Step 3''': The screen below will appear. Select the language you would like to use during the installation process. Select '''Continue''' when finished. The following steps can be done in any order.

[[Image:3.gui-installation-langselect.jpg|center|850px]]

−

'''Step 4''': Select ~~the defaults to use~~.

'''Step 4a''': Enable the network if desired: required for net install. It is enabled using the switch on the right. Select '''Done''' when finished.

−

{{Warning box| At this juncture the partioning scheme and treatment of multiple disks is automated by the customised Koozali install routines and any options you set eg 3 HDs eguals Raid 1 with a hotspare See the wiki [https://wiki.contribs.org/Raid Raid] . If you select the item "'''Installation Destination'''" those customised setups will be removed and the installer will fall back to the standard install of auto partitioning where the default CentOS scheme is used ie EFI if needed, boot and one huge LVM using all the remaining space on ALL disks are treated as one and a single large LVM. If you are sure of the process you may enter the "'''Installation Destination'''" section and setup your customised partioning, Raid, LVM and file system, '''Beware''' an above average understanding and knowledge of the procedure is required}}

[[Image:6.installsummaryscreen-dateandkeyboardtod.jpg|center|850px]]

[[Image:9.installsummaryscreen-networksetupselecttutnon.jpg|center|850px]]

Network enabled:

[[Image:9a.installsummaryscreen-networksetup-ON.jpg|center|850px]]

[[Image:7.installsummarydate time.jpg|center|850px]]

'''Step 4b''': Select the keyboard defaults to use. Select '''Done''' when finished.

[[Image:8.installsummarykeyboard.jpg|center|850px]]

Install

{{Warning box| At this juncture the partioning scheme and treatment of multiple disks is automated by the customised Koozali install routines and any options you have set as above, eg 3 HDs equals RAID 1 with a hotspare: See the wiki [https://wiki.contribs.org/Raid Raid]. If you select the item "'''Installation Destination'''" those customised setups will be removed and the installer will fall back to the standard install of auto partitioning where the default CentOS scheme is used ie EFI if needed, boot and one huge LVM using all the remaining space on ALL disks are treated as one and a single large LVM. If you are sure of the process you may enter the "'''Installation Destination'''" section and setup your customised partioning, Raid, LVM and file system.

'''Beware''' if you do this an above-average understanding and knowledge of the procedure is required}}

[[Image:10installsummaru begfininstall.jpg|center|850px]]

'''Step 5''': You are informed that no disks will be formatted and hence data lost until '''Begin Installation''' is selected. You must choose '''Begin Installation''' to proceed.

Line 148: Line 186:

{{Warning box|The installation (or upgrade) process rewrites the boot sector on your hard drive. This may cause machines with BIOS boot sector virus detection to not boot unattended. This detection should be disabled in your system's BIOS.}}

−

====Restoring a Backup====

===Restart after install===

−

If you have a tar backup (usually smeserver.tgz) you are prompted if you wish to restore. Enter your media, CD, DVD, USB Disk or Tape drive

On restart, when rebooting from the installed Koozali SME Server Linux image, you will see this screen:

[[Image:Restart after gui text install.jpg|center|850px]]

====Option: Restoring a Backup====

The next screen offers you the opportunity to restore from tar backup. If you have a tar backup (usually smeserver.tgz) you are prompted if you wish to restore. Enter your media, CD, DVD, USB Disk or Tape drive

[[Image:13.restart-atofferofrestore.jpg|center|850px]]

−

If you have a DAR backup perform your restore from the server-manager after configuration.

If you have a DAR backup you must perform your restore from the server-manager after intial configuration.

−

====Configuring your SME Server====

===Configuring your Koozali SME Server===

{{Tip box|To change configuration settings, you have set during install, at a later date you can login as admin user to your server console and choose the option to Reconfigure your server. You will be take through the configuration routine just like during installation. Make your necessary changes or use the Keep option to preserve the settings you have set previously.}}

Once your system has restarted (so that it is no longer booting from the installation CD), you are ready to configure your system.

Line 176: Line 223:

Anyone who gains access to this password has the power to make any change to your server!

−

[[Image:5.~~6%20setting%20your%20admin%20password.png~~]]

[[Image:Installreboot-2.jpg|center|850px]]

After you enter the password once, you will be asked to type it again to confirm that the password was recorded correctly. The password will also be examined to determine how strong it is from a security point-of-view. If it is found to be weak (for instance, a dictionary word), you will see an additional screen asking if you really want to use this password. You will have the option to go back and change to a stronger password or to continue using the weaker password.

Line 185: Line 232:

As shown below, your next step is to enter the primary domain name that will be associated with your SME Server. (You can later configure other virtual domains that work with the server.)

−

[[Image:~~Set_primary_domain_name~~.~~png~~]]

[[Image:Installreboot-4.jpg|center|850px]]

Next you need to provide a name for your server. You should think carefully about this as changing it later may create additional work. (For instance, Windows client computers may be mapping drives to your server using its name. Those clients would need to remap the drive using the new name.)

Line 191: Line 238:

{{Tip box|You should make the system name as unique as possible in case you someday decide to link your server to another server using an IPSEC VPN. When you do, each server will need a unique name. Using some type of theme, such as location names, may be an effective way to ensure unique names.}}

−

[[Image:~~Select_system_name~~.~~png~~]]

[[Image:Installreboot-5.jpg|center|850px]]

====Configuring Your Local Network====

Line 202: Line 249:

You will first need to select the appropriate driver for the ethernet adapter connected to your local network, a shown in the screen below:

−

[[Image:~~Select_local_enet_driver~~.~~png~~]]

[[Image:Installreboot-6.jpg|center|850px]]

If you are using a PCI ethernet adapter that appears on our supported list, it is likely that your server will be able to detect your hardware automatically and you will simply be able to choose option 1, "Use xxxx (for chipset yyyy)", where 'xxxx' and 'yyyy' are specific to your hardware. If the software fails to detect it correctly, you can manually select the appropriate driver for your ethernet adapter from a list of drivers or from a list of ethernet adapter models. After the appropriate driver is selected, select "OK" and proceed to the next screen.

Line 211: Line 258:

Your SME Server needs information about your local network in order to communicate with the other computers on your network. This includes the IP address and the subnet mask on your server's internal interface. Because your server acts as a gateway and firewall, these will differ from the IP address and subnet mask on the external interface.

−

{{Warning box|If you configure your server in server-gateway mode make sure the IP address for the internal interface and the one for the external interface are in different ranges that do not overlap. Unless you know why you don't want to do so, it is best to use addresses from the ARIN reserved IPv4 blocks as follows:

*10.0.0.0/8 IP addresses: 10.0.0.0 – 10.255.255.255

*172.16.0.0/12 IP addresses: 172.16.0.0 – 172.31.255.255

*192.168.0.0/16 IP addresses: 192.168.0.0 – 192.168.255.255

Do please note "that only a portion of the “172” and the “192” address ranges are designated for private use. The remaining addresses are considered “public,” and thus are routable on the global Internet". The 172 block can be problematic and is perhaps best avoided.}}

If you plan to operate in server and gateway mode (explained in greater detail below), your server will act as a relay between your local network and the Internet. Because no computer on your local network, other than your server, directly interacts with the external world, the IP addresses assigned to those computers need only be unique with regards to your local network. (It doesn't matter if a computer on someone else's local network uses the same IP address, because the two machines will not be in direct contact.) As a result, we are able to use special "non-routable IP addresses" for your local network, including the internal interface of your server.

−

[[Image:~~Select_local_network~~.~~png~~]]

[[Image:Installreboot-7.jpg|center|850px]]

[[Image:Installreboot-8.jpg|center|850px]]

If you have no reason to prefer one set of IP addresses over another for your local network, your server will prompt you with default parameters that are probably appropriate in your situation.

Line 222: Line 276:

If, however, you are operating your server in "server-only" mode and there are already servers on your network, you will need to obtain an unused IP address for your local network.

{{Tip box|The careful admin will "ping" the intended address from any available workstation on the network to be certain it is not in use.}}

Next, you will be prompted to enter the subnet mask for your local network. If you are adding your server to an existing network, you will need to use the subnet mask used by the local network. Otherwise, unless you have a specific need for some other setting, you can accept the default setting.

Line 228: Line 284:

After configuring your SME Server for your local network, you will see the following screen. This is where you select your server's operation mode.

−

[[Image:~~Select_operation_mode~~.~~png~~]]

[[Image:Installreboot-9.jpg|center|850px]]

=====Option 1: Server and gateway mode=====

Line 234: Line 290:

If you configure your server to operate in server and gateway mode, your server will require either:

−

1. two ethernet adapters (one to communicate with the local network and the other to communicate with the external network/Internet)

−

1. one ethernet adapter (for the local network) and a modem for a dialup connection

*two ethernet adapters (one to communicate with the local network and the other to communicate with the external network/Internet)

*one ethernet adapter (for the local network) and a modem for a dialup connection, or a fibre modem for a fast connection

With server and gateway mode, there are a number of extra parameters that will need to be configured. These will be discussed in the next section.

Line 247: Line 304:

All services are available on the internal network. The differences are entirely in how your server is seen by the external world.

−

You would select this mode ~~only~~ if you wish to use the server as a gateway, but do not wish to publish any services to the external Internet.

You would select this mode if you wish to use the server only as a gateway, but do not wish to publish any services to the external Internet.

=====Option 3: Server-only mode=====

−

Server-only mode is appropriate if you do not wish to use the gateway capabilities of your server. In this configuration, your server connects only to the local network and does not connect directly to the outside world (although it may connect indirectly through your firewall or another server).

{{Warning box|SME 9.2 ISO only, DO NOT enable nic bonding on an initial install when server only mode is selected. See [[SME_Server:9.2|HERE]] for details }}

−

{{Warning box|Because the server "trusts" the local network to be secure in server-only mode, it must be behind a firewall of some type. Under no conditions should it be directly connected to the Internet.}}

{{Warning box|Because the server "trusts" the local network to be secure in server-only mode, it must be behind a firewall of some type. Under no conditions should it in server-only mode be directly connected to the Internet.}}

Your network will resemble the image below:

−

[[Image:Network4.png]]

[[Image:Network4.png|center|850px]]

If you have a connection to the Internet by way of another gateway or corporate firewall, you can configure your server to provide services (including e-mail, web services, file and print-sharing) to your network. In this instance, you do not need your server to provide the gateway role because that role is fulfilled by your firewall. If you select Option 3, " Server-only mode - protected network ", your server will provide your local network with web, e-mail, file and print-sharing.

Line 266: Line 323:

If you are configuring your server to operate in server and gateway mode, you must select one of two Internet connection types - a dedicated connection (such as ADSL or cable modem) or a dialup connection (in which case you will be connecting to your ISP via a modem).

−

[[Image:Select_ext_access_mode.png]]

[[Image:Select_ext_access_mode.png|center|850px]]

The next step after selecting a connection type is to enter the specific parameters representing that connection.

Line 276: Line 333:

As you did previously with your local ethernet adapter, you need to configure the driver for your external ethernet adapter. As before, the software will attempt to detect the card. If it correctly identifies the card, you can proceed using Option 1, "Keep current driver". If it does not, you will need to manually select the driver.

−

[[Image:Select_ext_enet_driver.png]]

[[Image:Select_ext_enet_driver.png|center|850px]]

=====Assigning Your Ethernet Adapters to Network Connection=====

Line 283: Line 340:

If you don't know which ethernet adapter is designated to eth0 and which is designated to eth1, we suggest you leave it in the default configuration while completing the rest of the screens. You will later have the opportunity to "Test Internet Access" from the server console. If your test fails at that time, return to this screen, swap the card assignment and retry the test.

−

[[Image:Select_ethernet_card_assignment.png]]

[[Image:Select_ethernet_card_assignment.png|center|850px]]

{{Tip box|If you are using two different network interface cards, you will see which driver is associated with eth0 and which is associated with eth1. This information can help you determine which card is eth0 and which is eth1. If you have two cards that use the identical driver you will see a screen such as the one above where the actual driver is not listed.}}

Line 290: Line 347:

With a dedicated connection in server and gateway mode, you will be presented with the following screen:

−

[[Image:Select_ext_interface_config.png]]

[[Image:Select_ext_interface_config.png|center|850px]]

Your server must know three additional things to communicate on the Internet:

Line 312: Line 369:

PPPoE is the Point-to-Point Protocol over Ethernet . Essentially, it is an implementation of the popular PPP protocol used for dialup connections - only configured to run over an Ethernet connection. Many ISPs that provide fibre and ADSL connections use PPPoE as the method of connecting their customers to the Internet over ADSL.}}

−

=====Configuring Dynamic DNS=====

<!-- =====Configuring Dynamic DNS=====

If you choose either of the DHCP options or PPPoE, you will be presented with an additional screen where you can choose which dynamic DNS service you wish to use.

−

[[Image:Select_dyn_dns.png]]

[[Image:Select_dyn_dns.png|center|850px]]

The server is pre-configured to operate with four dynamic DNS organizations: yi.org, dyndns.com, dyndns.org, and tzo.com. (You can elect to use a different service, but doing so would require some customization of the server.) Once the service is selected, the subsequent two screens will prompt you to enter your account name and the password for your account. (These two parameters would be given to you by the service. Note that the dynamic DNS service may place restrictions on which domain name you can use for your company.) Please read [[SME_Server:Documentation:Administration_Manual:Appendix#Appendix_B._Dynamic_DNS_Services|Appendix B]] on dynamic DNS for more information about whether a dynamic DNS is right for you.

NB. the script for "dyndns.com - Commercial service" doesn't work, if you wish to use this service select custom and write your own script.

-->

====Configuring the Server for Server and Gateway Mode - Dialup Access====

Line 336: Line 394:

After configuring this policy for "work" hours, you can then configure the policy for time outside of office hours and additionally for the weekend. Notice that you do have the choice of never, which would allow you to restrict your system from connecting on weekends or during off-hours.

−

[[Image:Select_connect_policy.png]]

[[Image:Select_connect_policy.png|center|850px]]

The connection policy defines several choices including Short, Medium or Long. These specify how long the server should wait before disconnecting the dialup connection. If your office only shares a single phone line, the Short option minimizes the amount of connection time and frees up the phone line for later use. The down side to this is that if someone is reading a long page on the web site or steps away from their computer for a brief moment, when they want to then go to another web page, the server will probably have disconnected and will need to redial and connect. On the other hand, setting the Long connection time will result in users experiencing fewer delays while waiting for the server to reconnect. However, the phone line will used for a larger amount of time.

Line 392: Line 450:

We recommend configuring your server to use DHCP to configure all of your network clients. IMPORTANT! You should not do this if there is an existing DHCP server on your network as there should typically be only one DHCP server per network.

−

[[Image:~~Select_dhcp_server_config~~.png]]

[[Image:Dhcp.png|center|850px]]

=====Configuring the DHCP Address Range=====

Trex

Administrators

1,574

edits

Retrieved from "https://wiki.koozali.org/Special:MobileDiff/39521...42411"

Changes

SME Server:Documentation:Administration Manual:Chapter5 (view source)

Revision as of 00:52, 13 December 2023

Navigation menu

Search