Suse 11 installation

To start the synchronization process now, proceed with Procedure 3. To successfully synchronize the files with Csync2, make sure that the following prerequisites are met:. The same Csync2 configuration is available on all nodes. It is recommended to include this file in the list of files to be synchronized with Csync2. It is needed for authentication by Csync2. However, do not regenerate the file on the other nodes as it needs to be the same file on all nodes.

Both Csync2 and xinetd must be running on all nodes. Execute the following commands on all nodes to make both services start automatically at boot time and to start xinetd now:. On the node that you want to copy the configuration from , execute the following command:.

This will synchronize all the files once by pushing them to the other nodes. If all files are synchronized successfully, Csync2 will finish with no errors.

If one or several files that are to be synchronized have been modified on other nodes not only on the current one , Csync2 will report a conflict. You will get an output similar to the one below:.

For more information on the Csync2 options, run csync2 -help. Csync2 only pushes changes. It does not continuously synchronize files between the nodes. Each time you update files that need to be synchronized, you need to push the changes to the other nodes: Run csync2 -xv on the node where you did the changes. If you run the command on any of the other nodes with unchanged files, nothing will happen.

To enable stateful packet inspection for iptables, configure and use the conntrack tools. Configuring the conntrackd with YaST.

Configuring a resource for conntrackd class: ocf , provider: heartbeat. If you use Hawk to add the resource, use the default values proposed by Hawk. After configuring the conntrack tools, you can use them for Load Balancing with Linux Virtual Server.

Use the YaST cluster module to configure the user-space conntrackd. It needs a dedicated network interface that is not used for other communication channels. The daemon can be started via a resource agent afterward. In the YaST cluster module, switch to the Configure conntrackd category. Select a Dedicated Interface for synchronizing the connection status. It must already be configured and it must support multicast.

Define the Multicast Address to be used for synchronizing the connection status. In Group Number , define a numeric ID for the group to synchronize the connection status to. In the YaST cluster module define whether to start certain services on a node at boot time. You can also use the module to start and stop the services manually. To bring the cluster nodes online and start the cluster resource manager, OpenAIS must be running as a service. In the YaST cluster module, switch to the Service category.

To start OpenAIS each time this cluster node is booted, select the respective option in the Booting group. To start OpenAIS manually, use the rcopenais start command. If you want to use the Pacemaker GUI for configuring, managing and monitoring cluster resources, activate Enable mgmtd. This daemon is needed for the GUI. To open the ports in the firewall that are needed for cluster communication on the current machine, activate Open Port in Firewall. If you modified any options for an existing cluster node, confirm your changes and close the cluster module.

Note that the configuration only applies to the current machine, not to all cluster nodes. If you have done the initial cluster setup exclusively with the YaST cluster module, you have now completed the basic configuration steps. Proceed with Section 3. On one of the nodes, check the cluster status with the crm status command. If all nodes are online, the output should be similar to the following:.

This output indicates that the cluster resource manager is started and is ready to manage resources. After the basic configuration is done and the nodes are online, you can start to configure cluster resources, using one of the cluster management tools like the crm shell, the Pacemaker GUI, or the HA Web Konsole. For more information, refer to the following chapters. The following procedure is suitable for deploying cluster nodes which are clones of an already existing node.

Make sure the node you want to clone is correctly installed and configured. This includes the following basic steps:. Creating an AutoYaST profile. If needed, adjust the configuration in the other modules and save the resulting control file as XML. Determining the source of the AutoYaST profile and the parameter to pass to the installation routines for the other nodes. Passing the command line to the installation routines, either by adding the parameters manually or by creating an info file.

After the clone has been successfully installed, execute the following steps to make the cloned node join the cluster:. Transfer the key configuration files from the already configured nodes to the cloned node with Csync2 as described in Section 3. The CIB is automatically synchronized among the cluster nodes.

Contents Contents. Multicast A technology used for a one-to-many communication within a network that can be used for cluster communication.

Note: Switches and Multicast If you want to use multicast for cluster communication, make sure your switches support multicast. Note: Network Address for All Nodes As the same Corosync configuration will be used on all nodes, make sure to use a network address as bindnetaddr , not the address of a specific network interface. If set to none , RRP is disabled.

Procedure 3. Note: Installing Software Packages on All Parties The software packages needed for High Availability clusters are not automatically copied to the cluster nodes.

Deploy in both physical and virtual environments to maintain continuity, protect data integrity, and maximize uptime. Solve the most demanding computational and data-intensive problems and enjoy a wide variety of open-source software.

It is well suited for any decentralized computing environment such as edge, embedded or IoT deployment without vendor lock-in. Get improved usability, provisioning, power management, and new IT compliance and security features. Extend the useful life of your legacy applications.

IT Modernization. SAP Solutions. AI and Analytics. Make sure the network cable is plugged in and choose Yes, Use It. Some networks require the use of a proxy server to access the Internet.

Tick the check box Use Proxy for Accessing the Internet and enter the appropriate specifications. Click Accept to perform the network setup. The installation procedure will continue with the add-on products or repositories setup as described in Section 6.

In this dialog, select your region and time zone. Both are preselected according to the selected installation language. To change the preselected values, either use the map or the drop down lists for Region and Time Zone. When using the map, point the cursor at the rough direction of your region and left-click to zoom. Now choose your country or region by left-clicking. Right-click to return to the world map. If you run another operating system on your machine, such as Microsoft Windows, it is likely your system uses local time instead.

If you only run Linux on your machine, set the hardware clock to UTC and have the switch from standard time to daylight saving time performed automatically. The switch from standard time to daylight saving time and vice versa can only be performed automatically when the hardware clock CMOS clock is set to UTC.

This also applies if you use automatic time synchronization with NTP, because automatic syncing will only be performed if the time difference between the hardware and system clock is less than 15 minutes. Since a wrong system time can cause severe problems missed backups, dropped mail messages, mount failures on remote file systems, etc. If a network is already configured, you can configure time synchronization with an NTP server.

When finished, click Accept to continue the installation. Since the operating system is not allowed to change time and date directly, the Change option is not available on IBM System z. The selected scenario affects the package selection.

On the last step before the real installation takes place, you can alter installation settings suggested by YaST and also review the settings you made so far. Basic settings can be changed in the Overview tab, advanced options are available on the Experts tab. To modify the suggestions, either click Change and select the category to change or click on one of the headlines. After configuring any of the items presented in these dialogs, you are always returned to the Installation Settings window, which is updated accordingly.

YaST then shows the original proposal again. Review and, if necessary, change the partition setup proposed by the system. Changing the partition setup either lets you partition a specific disk or, when choosing Custom Partitioning , apply your own partitioning scheme. Modifying the partition setup opens the Expert Partitioner described in Section The default partitioning scheme is based on Ext3 file system.

So if two or more minidisks are on the same physical disk, they all have the same ID. To avoid problems when mounting the minidisks, always mount them either "by path" or "by UUID".

YaST proposes a boot configuration for your system. Other operating systems found on your computer, such as Microsoft Windows or other Linux installations, will automatically be detected and added to the boot loader.

Normally, you can leave these settings unchanged. If you need a custom setup, modify the proposal for your system.

For information, see Section Click Software to start the pattern selection and modify the installation scope according to your needs. Select your pattern from the list and see a pattern description in the right part of the window.

Each pattern contains a number of software packages needed for specific functions e. Web and LAMP server or a print server. For a more detailed selection based on software packages to install, select Details to switch to the YaST Software Manager. You can also install additional software packages or remove software packages from your system at any later time with the YaST Software Manager. For more information, refer to Chapter 9, Installing or Removing Software. Here you can change the system Language you defined in the first step of the installation.

It is also possible to add additional languages. To adjust the system language settings, select Language. Select a language from the list. The primary language is used as the system language. You can also adapt keyboard layout and time zone to the primary language if the current settings differ. Details lets you modify language settings for the user root , set UTF-8 support, or further specify the language e.

Choose secondary languages to be able to switch to one of these languages at any time without having to install additional packages. If you added a source for an add-on media earlier, it appears here. Add, remove, or modify add-on products here, if needed. This is the same configuration dialog as discussed earlier in Section 6. To change the keyboard layout, select Keyboard Layout. By default, the layout corresponds to the language chosen for installation.

Select the keyboard layout from the list. Use the Test field at the bottom of the dialog to check if you can enter special characters of that layout correctly.

Options to fine-tune various settings are available under Expert Mode. When finished, click Accept to return to the installation summary. Adjust time zone and clock settings here. Provided a network is configured, you can also set up a Network Time Protocol NTP client that automatically synchronizes your computer with a time server.

This is the same configuration as shown earlier in Section 6. Normally, there should be no need to change anything here, but if necessary set the default runlevel with this dialog. Refer to Section This dialog presents all the hardware information YaST could obtain about your computer. When called, the hardware detection routine is started. Depending on your system, this may take some time. Select any item in the list and click Details to see detailed information about the selected item.

Use Save to File to save a detailed list to either the local file system or a floppy. Using kdump, you can save a dump of the kernel in case of a crash to analyze what went wrong. Use this dialog to enable and configure kdump. Find detailed information at Chapter 18, kexec and kdump. After configuring all installation settings, click Install in the Installation Settings window to start the installation. Some software may require a license confirmation.

If your software selection includes such software, license confirmation dialogs are displayed. Click Accept to install the software package. When not agreeing to the license, click I Disagree and the software package will not be installed.

In the dialog that follows, confirm with Install again. The installation usually takes between 15 and 30 minutes, depending on the system performance and the selected software scope. After having prepared the hard disk and having saved and restored the user settings, the software installation starts.

After the software installation has completed, the basic system is set up. Next YaST boots into the new Linux system to start the system configuration. If you install SUSE Linux Enterprise Server on a machine with existing Linux installations, the installation routine automatically imports the SSH host key with the most recent access time from an existing installation.

In cases where an automatic reboot is not possible, YaST will show a dialog box containing information about from which device to do an IPL. Accept the shutdown option and perform an IPL after the shutdown. The procedure varies according to the type of installation:. Now start the loading process. Log in to the VM guest see Example 4.

The parameter length is limited to eight characters. Longer numbers must be separated by spaces:. After IPLing the installed system, establish a connection with it to complete the installation. The steps involved in this vary depending on the type of connection used at the outset. A message in the terminal asks you to connect to the Linux system using a VNC client. This message is easily missed, however, because it is mixed with kernel messages and the terminal process might quit before you become aware of the message.

If nothing happens for five minutes, try to initiate a connection to the Linux system using a VNC viewer. If you connect using a Java-capable browser, enter the complete URL, consisting of the IP address of the installed system along with the port number, in the following fashion:. When IPLing the installed system, make sure that the X server used for the first phase of the installation is up and still available before booting from the DASD. YaST opens on this X server to finish the installation.

Complications may arise if the system is booted up but unable to connect to the X server in a timely fashion. Start SSH in an xterm. Other terminal emulators lack complete support for the text-based interface of YaST. A message in the terminal asks you to connect to the Linux system with an SSH client. Once the message appears, use SSH to log in to the Linux system as root.

If the connection is denied or times out, wait for the login timeout to expire, then try again this time may vary depending on server settings.

Just executing the command yast does not suffice in this case. YaST then begins completing the installation of the remaining packages and creating an initial system configuration. The system is now installed, but not yet configured for use. The hardware, the network and other services are not yet set up. Having rebooted, the system starts the manual configuration. If the configuration fails at one of the steps of this stage, it restarts and continues from the last successful step.

Unlike regular users, who may or may not have permission to execute administrative commands on the system, root has unlimited command capacity, for instance changing the system configuration, installing programs, and setting up new hardware.

If users forget their passwords or have other problems with the system, root can help. If you activate the firewall after the installation, you must open all required ports manually. For more information about required ports, see Section 5.

You can change them according to your needs. Otherwise, it is possible to just prepare the SAP product installation with Only create SAP Business One file systems, do not install SAP products now , or completely interrupt the installation process at this point with Finish wizard and proceed to OS login and resume it after a system restart.

Otherwise, this option will not create a new file system and the installation workflow ends at this point. The functionality is the same, but the layout of the dialogs is different; the left progress pane is only displayed when continuing with the installation without a restart. The following screen shots document the installation with the SAP Product Installer that runs after a restart of the system.

The location can either be a local source or a remotely provided installation source. If you want to install from an NFS source, you must enter the name of the server and the complete path to the media data. For more information about setting up a remote installation server, see Chapter 4, Remote Installation from a Network Server.

See Figure 2. Click Help for information. Enable Preparation for autoinstallation , if you only want to enter the installation parameters, but not perform the actual installation now. The offerings of available products depend on the media set and installation master you received from SAP; for example, see Figure 2. This is repeated for all necessary SAP media, with some additional simple questions.

You are asked to provide the Location of the SAP Medium and if additional media are needed, you can also add them afterwards; see here you see the list of already copied or linked SAP media. Then you can optionally copy a Supplement or 3rd-Party Medium.

For more information about a Supplement Media, see Section 5. In the following configuration dialogs, enter the details for the SAP installation. In Figure 2. For details, see the online help on the left. The SAP installer displays a visualization of the installation steps it performs; see Figure 2. After the SAP installer has finished, you will see a short summary of the installation data.