Setting Up SUSE® Managerfor a SAP HANAScale-out Scenario

Guide

Guidewww.suse.com

System Management

Table of Contents page

Executive Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Installation of SUSE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Using SUSE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Miscellaneous/Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2

System Management GuideSetting Up SUSE Manager for a SAP HANA Scale-out Scenario

Within a SAP HANA scale-out it becomes more important to have all machines updated . The most valid and trusted method is using SUSE® Manager . This document will describe how to install a SUSE Manager Server and how it could be used to update an SAP HANA scale-out scenario .

The main purpose of SUSE Manager is to efficiently manage a set of Linux systems and keep them up-to-date . This is done by connecting SUSE Manager to package and update sources organized as repositories .

Repositories are grouped into channels, which are assigned to client systems . SUSE Manager then compares packages installed on the clients with packages available in assigned channels and reports any uninstalled updates .

To see and get all benefits from SUSE Manager and also get a solution designed for the environment it has to be used in, please contact SUSE Consulting .

OverviewSUSE Manager is an open source (GPLv2) Linux systems man-agement solution that allows you to:

Inventoryyoursystems(hardwareandsoftwareinformation) Installandupdatesoftwareonyoursystems Collectanddistributeyourcustomsoftwarepackagesinto

manageablegroups Provision(usingAutoYaST/Kickstart)yoursystems Manageanddeployconfigurationfilestoyoursystems Monitoryoursystems Provisionandstart/stop/configurevirtualguests

Distributecontentacrossmultiplegeographicalsitesinanefficientmanner

TrackcomplianceofmanagedsystemswithOpenSCAP

Using a single SUSE Manager to serve your entire network is adequate to service a medium-sized group of clients, like a SAP HANA scale-out setup . For larger networks you can have more SUSE Manager Servers or even have a tiered setup with use of SUSE Manager Proxy .

Installation of SUSE Manager

This chapter will discuss the installation and the post tasks needed to run SUSE Manager Server . How the content can be configured will be discussed in the next chapter .

Executive SummaryAs more and more customers decide to use SAP HANA solutions, they need a valid method of updating their SAP HANA servers.

3www.suse.com

For all examples here we used SUSE Manager version 1 .7 . There is more detailed documentation available on: www.suse.com/documentation/suse_manager

PreparationBefore the server can be installed, the following must be checked:

ValidregistrationkeyforSUSEManager.Pleasekeepthisavailableduringinstallation.

Validcustomercentermirrorcredentials.Pleasekeepthisavailableduringinstallation.

Therootpassword,userandpasswordtobeusedforSUSEManagerandapasswordfortheCAcertificate.Thesepasswordsshouldbestoredinasafeplace.Withoutthesepasswords,forexample,noSUSEManagerProxyservercanbeinstalled.

Designoverview:whichchannelsareneeded,howthisshouldbeclonedandwhichkeysareneeded.

NetworkinformationfortheSUSEManagerServer:

–  IP address, netmask, gateway –  DNS server and the server should have been resolvable

in DNS –  Proxy server (when needed)

Inthefirewalltheportsneededshouldbeopen.

The following hardware is needed for SUSE Manager:

Memory:minimum8GB,recommended12GB Processor cores:minimum2,recommended4 Network-controllers:1 Storage:atleastaround250GBofstorage.Thebestpractice

forstorageistousedifferentdisksforthedatabaseandthedatastore.Thestoragewillbedividedasfollows:

–  OS 20 GB –  Postgresql database 20 GB –  Spacewalk datastore (RPMs and backup Postgresql

Database) > 200 GB

InstallationThe following procedure has been used to install the SUSE Manager 1 .7 Server:

PreparetherealhardwareoruseavirtualizationsolutionlikeXEN,KVMorVMwareguest,andboottheserverwiththefollowingISO(https://download.suse.com/download?buildid=wDk-hfm0gO0~):SUSE_Manager_Server.x86_64-1.7.0.iso

Selecttheoption:Install/Restore SUSE-Manager-Serverandpressenter.

Theinstallationwillstart.The“-pg”indicatesthatPostgreSQLisusedasthedatabase.

Ifthereismorethanonediskavailable,theinstallationwillaskonwhichdisktheOSshouldbeinstalled.Alldataonthisdiskwillbedeleted.Selectthecorrectdiskandpressenter:

4

System Management GuideSetting Up SUSE Manager for a SAP HANA Scale-out Scenario

ThelanguageforallserversisEnglishUS.Selectthekeyboardlayoutneeded.Selectthecorrectvaluesandpress<ALT><n>

Acceptthelicenseagreement. Enteryourrootpassword. Configurethenetworkcard.EntertheIPaddress,DNSserver

andthedefaultgateway. Selectthecorrecttimezone. SettheproperNTPsettings. NowtheNovellCustomerCenter(NCC)Configurationhasto

becompleted.Press<ALT><e><ALT><n>:

Selectcontinueinthenextscreen:

Enteryouremailaddress*(twice)andtheSUSEManagerServerregistrationkey.Thesystemnameisoptional.Select‘submit’andpress<enter>:

__________

* Bestpractice:Useaspecialmailaddressthatcanbeassignedtomultipleemployees.Don’tuseapersonalizedmailaddress.

5www.suse.com

Afterthemessageappearsthattheregistrationhasbeensuccessful,closethewindowwith‘q’and‘y’.

Press<ALT><n>.Thiswillcompletetheregistration.Insomecasestherecouldbeaproblemconnectingtothecustomercenterserver(currentlyNovellCustomerCenter,NCC).Pleasetryagainasthisismostlikelyatimeoutinthecommunication.

Thiscompletesthefirstpartoftheinstallation.SelectFinishtoreboottheserver.

Aftertheserverisbooted,loginasroot. Ifyouwanttouseseparatedisksforthedatabase

(/var/lib/pgsql)and/orthedatastore(/var/ spacewalk),createtheneededdiskorLVMvolumesandfilesystemsbeforeyoucontinue.Makesuretheyhavetherightpermissionsandaremountedautomatically.

Beforecontinuing,updatetheservertothelatestpatchlevel.Applyallpatcheswith:# zypper ref; zypper -n patch -l;zypper -n patch -l; zypper -n up -l

Afterthepatchinghasbeenfinished,reboottheserver. Aftertheserverisbooted,loginwithroot. Tocompletetheinstallationstart:# yast susemanager_ setup

Select‘Set up SUSE Manager from scratch’andselectnext.

EntertheemailaddressthatshouldreceivenotificationsfromSUSEManager:

EnterthecorrectinformationfortheSSLCACertificate.Please write down and remember the password.WithoutthispasswordnoSUSEManagerProxyservercanbeinstalled:

6

System Management GuideSetting Up SUSE Manager for a SAP HANA Scale-out Scenario

Enterapasswordfortheembeddeddatabase.TherecommendationistousethesamepasswordasfortheSSLcertificate:

Enterthecustomercentercredentials:

Alldatahasbeencollectedandtheconfigurationcanstart.Press<enter>.

Whenthesetupiscompleted,press‘next’. Theinstallationisnowfinished.

The next paragraph will discuss the actions needed after the installation .

Post TasksThis part will discuss the action needed after the installation has been finished . This will include:

Creationofanadminaccount Neededchangestoconfigurationfilesandadditional

softwareneeded Initialdownloadingthechannelsfromthecustomercenter Cronjobfornightlydownloadfromthecustomercenter Cronjobfordailybackup Fixbootstrapproblem

CREATION OF ADMIN ACCOUNT

The admin account will be created the first time the SUSE Manager GUI is loaded:

OnaworkstationstartabrowserandconnecttoSUSEManager:http://susemanager_server

EntertheIDfortheadmin,password,firstname,lastname,mail-address.

Clickonsave.

This account has rights to the entire SUSE Manager sys-tem . The recommendation is to create separate (admin) accounts for all persons working with SUSE Manager .

NEEDED CHANGES TO CONFIGURATION FILES AND

ADDITIONAL SOFTWARE NEEDED

The following packages should be installed:

spacewalk-utils.Thiscanbeinstalledusingthefollowingcommand:zypper in spacewalk-utils

7www.suse.com

Some changes to the configuration files could be made to have a smoother setup:

In/etc/rhn/rhn.confaddthefollowinglines:web.min_database_lifetime = 28800 taskomatic.maxmemory = 2048

In/etc/sysconfig/rhn/reposyncchangethefollowinglineto:MAX_DAYS=”7”Thiswilllimitthestoredlogsin/var/log/rhn/reposynctoamaximumofsevenandpreventthefilesystemfromfillingup.

In/etc/motdremovethefollowingline:To set up SUSE Manager please execute yast2 susemanager_setup

ToenableSUSEManagertosendmails,arelayhosthastobeenteredinthepostfixconfiguration.In/etc/postfix/main.cfchangethefollowingparameter:relayhost=your_relay_hostAfterthechangerestartpostfixwith:rcpostfix restart

Topreventtimeoutsduringasynchronizationwiththecustomercenter,createthefollowingfilewiththefollowingcontent:# mkdir -p /etc/rhn/spacewalk-repo-sync # vim /etc/rhn/spacewalk-repo-sync/yum.conf [main] timeout=300

RestartSUSEManagertoactivateallchanges.Thiscanbedonebyusingthefollowingcommand:spacewalk-service restart .

INITIAL DOWNLOAD OF CHANNELS FROM THE

CUSTOMER CENTER

Channels are collections of repositories which are assigned to client systems . Without a channel, clients cannot be grouped nor can they receive updates .

During installation, a first synchronization between the customer center and SUSE Manager is automatically done by mgr-ncc-sync . At this point in time, it only downloads the subscriptions to the products you are registered for, but it does not synchronize any channel data yet . After installation, you need to import the channels you need .

Execute mgr-ncc-sync--list-channels or mgr-ncc-sync–list-products on the SUSE Manager Server to view all channels that you are allowed to synchronize with SUSE Manager .

The following procedure can be used to import the needed channels:

OpenanSSHconsoletotheSUSEManagerServerasroot. Runthecommand#mgr-ncc-sync–add-product. ChoosetherightServicePackforSUSELinuxEnterprise

Server11forSAPApplications[x86_64].YouneedtorunthisseparatelyforeveryServicePack.

Or if you would like assign to the minimal needed channels manu-ally, use the following commands:

SP1 # mgr-ncc-sync -c sle11-sp1-sap-aio-pool-x86_64 # mgr-ncc-sync -c sle11-sp1-sap-aio-updates-x86_64 # mgr-ncc-sync -c sles11-sp1-pool-x86_64-sap-aio # mgr-ncc-sync -c sles11-sp1-updates-x86_64- sap-aio

# mgr-ncc-sync -c sle11-hae-sp1-pool-x86_64- sap-aio

# mgr-ncc-sync -c sle11-hae-sp1-updates-x86_64- sap-aio

# mgr-ncc-sync -c sles11-sp1-ltss-updates-x86_64- sap-aio

# mgr-ncc-sync -c sles11-sp1-suse-manager-tools- x86_64-sap-aio

SP2 # mgr-ncc-sync -c sle11-sp2-sap-updates-x86_64 # mgr-ncc-sync -c sles11-sp2-core-x86_64-sap-sp2 # mgr-ncc-sync -c sle11-hae-sp2-pool-x86_64- sap-sp2

# mgr-ncc-sync -c sle11-hae-sp2-updates-x86_64- sap-sp2

# mgr-ncc-sync -c sles11-sp1-pool for x86_64 sap-sp2

# mgr-ncc-sync -c sles11-sp1-updates for x86_64 sap-sp2

# mgr-ncc-sync -c sles11-sp2-updates-x86_64- sap-sp2

# mgr-ncc-sync -c sles11-sp2-ltss-updates-x86_64- sap-sp2

# mgr-ncc-sync -c sles11-sp2-suse-manager-tools- x86_64-sap-sp2

8

System Management GuideSetting Up SUSE Manager for a SAP HANA Scale-out Scenario

SP3 # mgr-ncc-sync -c sle11-sp3-sap-pool-x86_64 # mgr-ncc-sync -c sle11-sp3-sap-updates-x86_64 # mgr-ncc-sync -c sles11-sp3-pool-x86_64-sap-sp3 # mgr-ncc-sync -c sles11-sp3-updates-x86_64- sap-sp3

# mgr-ncc-sync -c sle11-hae-sp3-pool-x86_64- sap-sp3

# mgr-ncc-sync -c sle11-hae-sp3-updates-x86_64- sap-sp3

# mgr-ncc-sync -c sles11-sp2-suse-manager-tools- x86_64-sap-sp3

Downloading these channels will take some time . Until the sync is completely finished and all information has been imported in the database, no actions can be done

on these channels . Check /var/log/rhn/rhn_taskomatic_daemon.log and the representative files in /var/log/rhn/reposync on the progress . Please do not continue with the next steps before the synchronization is finished.

Continuing with the cloning before the synchronization is completed will cause data corruption! Unfortunately, there is no proper way to check if everything has finished .

SUSE Consulting advices to leave this finishing overnight .

CRON JOB FOR NIGHTLY DOWNLOADS FROM THE

CUSTOMER CENTER

To update the patches and packages from the customer center on a daily schedule, the following cron job can be created:

/etc/cron.d/suman withthefollowingcontent:0 5 * * * root /usr/sbin/mgr-ncc-sync

CRON JOB FOR A DAILY BACKUP

To ensure a proper backup of the database, it is recommended to create a hot-backup of the database on a daily schedule . The tool smdba could be used to create such hot-backups .

FIX BOOTSTRAP PROBLEM

To register the server with bootstrap.sh, some additional RPMs need to be installed on the receiving server . These RPMs are stored in sub-directories under /srv/www/htdocs/pub/repositories.

These repositories have to be created with the following com-mand: mgr-create-bootstrap-repo .

After the latest updates for SUSE Manager 1 .7, the following error happens when performing the command:

# mgr-create-bootstrap-repo Take care that the following packages are not on your system:

* spacewalk-client-repository-sle-10-4 * spacewalk-client-repository-sle-10-3 * spacewalk-client-repository-sle-11-1 * spacewalk-client-repository Aborted.

To correct this error, a few RPMs have to be removed from the server . This can be done with the following command:

# rpm -e spacewalk-client-repository-sle-10-3-0.1- 0.7.2 -e spacewalk-client-repository-0.1-0.7.1 -e spacewalk-client-repository-sle-11-1-0.1-0.7.1 -e spacewalk-client-repository-sle-10-4-0.1-0.7.2

The repositories can then be created with:

# mgr-create-bootstrap-repo

Use this command three times for all three Service Packs of SUSE Linux Enterprise Server for SAP Applications 11 SP3 .

Using SUSE ManagerThis chapter will describe how to use SUSE Manager in the environment .

Custom ChannelsWith SAP HANA you also need to install software packages from the vendor who delivers the SAP HANA hardware . To ease install-ing and updating, this software should be made available in a channel as well . This will make upcoming procedures easier . The packages must be provided in the RPM format .

Please contact SUSE Consulting when this is needed in a bigger environment .

9www.suse.com

For each vendor, a separate child channel should be created . The method on how to add packages to these channels depends on how the vendor provides the RPMs .

The easiest way occurs when a vendor has a subscription channel available via the Internet .

In 3 .1 .2 there is an example for including the HP SPP channel .

In 3 .1 .3 are instructions on how to add RPMs manually to a channel . If a vendor is not providing RPMs, SUSE Manager will not be able to make these patches available to the SAP HANA server .

Each specified procedure described below can be used for SUSE Linux Enterprise Server 11 SP1, SUSE Linux Enterprise Server 11 SP2 and SUSE Linux Enterprise Server 11 SP3 .

VENDOR-SPECIFIC REPOSITORY

When the vendor has a repository that will provide specific up-dates for the SAP HANA, perform the following instructions .

As an example we are using the HP repositories which are pub-licly available for SUSE Linux Enterprise Server .

To install, e .g ., the HP Service Pack for ProLiant (SPP) using RPMs, the RPM packages have to be made available via a channel . Be aware that the HP SPP tools can prevent updating to the latest kernel due to missing dependencies . The following procedure describes how to create this channel:

StartanInternetbrowserandconnecttotheSUSEManagerServerandlogin.

ClickonChannels|ManageSoftwareChannels. Clickon‘createnewchannel’. Enterthefollowinginformation:

ChannelName:hp-spp-sles11sp3ChannelLabel:hp-spp-sles11sp3ParentChannel:SLE11-SP3-SAP-Pool for x86_64ChannelSummary:hp-spp-sles11sp3OrganizationSharing:“This channel is public .....”

Clickon‘create channel’tocompletetheprocess.

OpenanSSHsessiontotheSUSEManagerServerandissuethefollowingcommandtodownloadallinformationforthissubscriptionchannel:# spacewalk-repo-sync --channel hp-spp-sles11sp3 --url=http://downloads.linux.hp.com/SDR/repo/spp/SUSE_LINUX/SLES11-SP3/x86_64/current/

ForSUSELinuxEnterpriseServer11SP1usethefollowing:ChannelName,ChannelLabel,ChannelSummary:hp-spp-sles11sp1 ParentChannel:SLE11-SP1-SAP-Updates for x86_64Synchronizationcommand:# spacewalk-repo-sync -- channel hp-spp-sles11sp1 --url=http://downloads.linux.hp.com/SDR/repo/spp/SUSE_LINUX/SLES11-SP1/x86_64/current/

ForSUSELinuxEnterpriseServer11SP2usethefollowing:ChannelName,ChannelLabel,ChannelSummary:hp-spp-sles11sp2ParentChannel:SLE11-SP2-SAP-Updates for x86_64Synchronizationcommand:# spacewalk-repo-sync -- channel hp-spp-sles11sp2 --url=http://downloads.linux.hp.com/SDR/repo/spp/SUSE_LINUX/SLES11-SP2/x86_64/current/

VENDOR RPMS

If a vendor provides RPMs, they can be added to SUSE Manager using the following procedure:

StartanInternetbrowserandconnecttotheSUSEManagerServerandlogin.

ClickonChannels|ManageSoftwareChannels. Clickon‘createnewchannel’. Enterthefollowinginformation:

ChannelName:vendor-sles11sp3ChannelLabel:vendor-sles11sp3ParentChannel:SLE11-SP3-SAP-Pool for x86_64ChannelSummary:vendor-sles11sp3OrganizationSharing:“This channel is public .....”

Clickon‘create channel’tocompletetheprocess. OpenanSSHsessiontotheSUSEManagerServer. UploadtheRPMstotheSUSEManagerServer.

Recommended:createadirectory/workandunderneathcreateadirectorypervendor.

Issuethefollowingcommandtodownloadallinformationforthissubscriptionchannel:# mgrpush --channel= vendor-sles11sp3 /location/of/vendor-specific-rpm

10

System Management GuideSetting Up SUSE Manager for a SAP HANA Scale-out Scenario

Creating a (Tree) Clone of a ChannelIt is strongly recommended to use a staging model . This consists of four types of channels:

Channelsthataredirectlybeingdownloadedfromnu.novell.com.These channels should never be assigned to a subscription key or servers.Thesechannelswillbeupdateddaily.

Development channels:Thesechannelsareclonedfromthechannelsupdateddailyfromnu.novell.com.Thesepatcheswillbetestedonadedicatedtestingservertocheckiftheupdatesarecausingproblems.Thechannelnameswillstartwith:dev-

Test channels:Thesechannelsareacloneofthedevelopmentchannels.Aftersuccessfullytestingindevelopment,thesechannelswillbesynchronized.Normallythesechannelsareassignedtoserversthataremoreliketheserversinproduction.Thechannelnameswillstartwith:test-

Production channels:Thesechannelsareacloneofthetestchannels.Thesechannelswillbeusedtopatchallproductionservers.Thechannelnameswillstartwith:prod-

These examples here give you default base for your channels . PLEASE TAKE INTO ACCOUNT TO CHECK WITH YOUR SAP HANA HARDWARE VENDOR WHAT SHOULD BE USED INSIDE THE CHANNELS . You can add or delete any package in channels .

The tool used for creating a clone is spacewalk-manage- channel-lifecycle .

Each clone should only be performed when the previous clone has been completely finished and all information has been imported in the database . Before that, no

actions can be done on these channels .

Continuing with the next step before all is completed will cause data corruption. Unfortunately, there is no proper way to check if everything has finished .

SUSE Consulting advises to leave this finishing overnight .

To create the initial development channel with the latest pack-ages from nu.novell.com issue the following command: # spacewalk-manage-channel-lifecycle -c sle11-sp3-sap-pool-x86_64 --init

When the testing in development is successful, promote the packages from development to test with: # spacewalk-manage-channel-lifecycle -c dev-sle11-sp3-sap-pool-x86_64 --promote

To promote the packages from test to production issue the fol-lowing: # spacewalk-manage-channel-lifecycle -c test-sle11-sp3-sap-pool-x86_64 --promote

Every night the latest packages will be downloaded from nu.novell.com . To make the latest updates available to the de-velopment channel issue the following command: # spacewalk-manage-channel-lifecycle -c sle11-sp3-sap-pool-x86_64 --promote

The other channels can be updated with the commands also used to create the initial channel .

Creating an Activation Key and Bootstrap ScriptAn activation key is being used to identify the type of server and to which channels it should be assigned . The registration itself is done on the server by a process that is called “boot-strapping .” The bootstrap process will install some additional RPMs if needed and performs the actual registration against SUSE Manager Server . As an example we show here the com-mands using SP3; the same procedure can be used for SUSE Linux Enterprise Server for SAP Applications 11 SP1, SUSE Linux Enterprise Server for SAP Applications 11 SP2 .

To represent the channel design for, e .g ., SUSE Linux Enterprise Server 11 SP3 for SAP, the following activation keys should be created:

dev-sle11-sp3-sap test-sle11-sp3-sap prod-sle11-sp3-sap

11www.suse.com

The following will give an example how to create an activation key:

StartanInternetbrowserandgototheSUSEManageradministrationpageandclickonSystems|Activationkeys.

Clickon‘Createnewkey’. Fordescriptionenter:dev-sle11-sp3-sap

Forkeyenter:dev-sle11-sp3-sapForbasechannelselect:dev-sle11-sp3-sap-pool-x86_64Foradd-onentitlementsselect:Provisioning

CreatethekeyandselectChildChannels.Allavailablechildchannelsshouldbeselected.

UpdatethekeyandselectPackages.Thefollowingpackageshouldbeinstalled,sopleaseenterthefourlinesbelow:osad rhncfg-actions rhncfg-client rhncfg-management

Updatethekey.Allconfigurationwithintheadminpageiscompleted.

OpenanSSHconsoletoSUSEManagerServerandperformthefollowing:# mgr-bootstrap --activation-keys= 1-dev-sle11-sp3-sap --script bootstrap-dev-sle11-sp3-sap.sh --no-up2date --allow-config- actions --allow-remote-commands

These actions have to be done for all 3 keys mentioned above.

Registering a (Client) Server To register a server (e .g ., a test SUSE Linux Enterprise Server 11 SP3 SAP HANA) the following actions are needed:

For example, for the test system:

OpenanSSHconsoletotheserverthatneedstoberegistered,

Executethefollowingcommandtoregistertheserver:# curl -Sks https://susemanager-server/pub/ bootstrap/bootstrap-test-sle11-sp3-sap.sh | /bin/bash

The registration process will take some time . After this is com-pleted, there are two methods to update the server:

UPDATE SERVER FROM CONSOLE

To update the server from the console enter the following com-mand: # zypper ref;zypper -n patch -l;zypper -n patch -l;zypper -n up -l

It is correct that the option patch has to be entered twice . The first time, only zypper related packages will be updated . After the update is completed, reboot the server, when needed . (Do not forget to stop SAP HANA before the reboot . A possibility is to configure SAP HANA for start and stop with the system .)

UPDATE SERVER FROM webGUI

To update the server from the webGUI use the following pro cedure:

StartanInternetbrowserandgototheSUSEManageradministrationpageandclickonSystems|Systems.

Findtheserverthatneedstobeupdated. Clickonthenumberdisplayedunderpatches. Scrolldownandclickon‘SelectAll’andthenclickon

‘ApplyAll’. Scrolldownandforscheduleselect‘Scheduleactionas

soonaspossible’andclickon‘Confirm’. Thepatcheswillbeapplied.Thiswilltakesometimeand

canbemonitoredunderthetabEvents. Sometimesitisnecessarytoapplypackagesseparately.

When,afterapplyingthepatches,therearestillupdateslistedforpatchesorpackages,clickonthenumberunderpackages.

Scrolldownandclickon‘SelectAll’andthenclickon‘Upgradepackages’.

Scrolldownandforscheduleselect‘Scheduleactionassoonaspossible’andclickon‘Confirm’.

Thepackageswillbeupdated.ThiswilltakesometimeandcanbemonitoredunderthetabEvents.

Whenallupdatesarefinished,under“Details”thesystemwilldisplayiftheserverneedsareboot.Ifneeded,clickon‘ScheduleSystemReboot’.

Forscheduleselect‘Scheduleactionassoonaspossible’andclickon‘ScheduleReboot’.

Thiswillinitiatea‘/sbin/shutdown +r -3’ontheserver.Afterthreeminutestheserverwillberebooted.

12

System Management GuideSetting Up SUSE Manager for a SAP HANA Scale-out Scenario

System Set Management (SSM)Most of the actions done on a single system can be also be per-formed on multiple systems at the same time . This feature is called System Set Management or SSM, which is very useful in a SAP HANA scale-out scenario .

There are several ways to select the systems to be grouped and managed via SSM:

Selectthesystemindividually:

–  Start an Internet browser, go to the SUSE Manager administration page, click on Systems | Systems and select the system to be part of SSM .

–  In the upper-right corner the screen displays how many systems are selected . Click on ‘Manage’ next to this number, and the SSM page will be shown . Please select the action that is needed .

Selectallsystemsinonesystemgroup:

–  Start an Internet browser, go to the SUSE Manager administration page, click on Systems | System Groups and select the system group in which the systems are to be managed with SSM .

–  Select ‘Work with Union’ or ‘Work with Intersection’ . –  The upper-right corner displays how many systems are

selected . Click on ‘Manage’ next to this number and the SSM page is shown . Please select the action that is needed .

Selectsystemsinmultiplesystemsgroups:

–  Start an Internet browser, go to the SUSE Manager administration page, click on Systems | System Groups and select the system groups in which the systems are to be managed with SSM .

–  Select ‘Work with Union’ if all systems should be selected that are in one of the groups or ‘Work with Intersection’ when selecting systems that are present in all selected groups .

–  The upper-right corner displays how many systems are selected . Click on ‘Manage’ next to this number and the SSM page will be shown . Please select the action that is needed .

Miscellaneous/Other

Firewall SettingsTo enable communication between the SUSE Manager Server and the SUSE Manager Proxy Servers the following TCP ports need to be opened for inbound and outbound traffic:

80 443 4545 5222 5269 25

More detailed information is available at the Installation Guide, Table 3 .1, 3 .2 + 3 .3 (www.suse.com/documentation/suse_manager/ singlehtml/book_susemanager_install/book_susemanager_install.html#s1-requirements-additional) .

Log FilesThere are several log files that should be checked at regular times (e .g ., once a week) . The following lists the most important logfiles and a short description of their content:

/var/log/rhn/mgr-ncc-sync.logThislogshowstheinformationfromthecommandmgr-ncc-sync.Thecontentofthelogisthesameasthecontentdisplayedwhenexecutingthecommand.

/var/log/rhn/mgr-register.logThislogshowstheinformationwhenregisteringasystem.

/var/log/rhn/osa-dispatcher.logInthislogallcommunicationinregardstoOSA/jabberdisregistered.ThislogshouldbecheckedwhenthesystemfailstoexecutecommandsonsystemsinitiatedfromthewebGUI.

/var/log/rhn/rhn_server_xmlrpc.logInthisloginformationontheAPIisstored,e.g.,executedAPIcallsandwhoexecutedthesecalls.

/var/log/rhn/rhn_taskomatic_daemon.logThisshowsactionsinitiatedbytaskomatic.Themostcommonistheoutputfromthecommandspacewalk-repo-sync.Separatelogsfromeachchannelcanbefoundinthedirectory:/var/log/rhn/reposync

/var/log/rhn/rhn_web_api.logThislogshowstasksstartedfromthewebGUI.

Useful CommandsSUSE Manager comes with many tools . Most of these tools start with spacewalk- or mgr- . Most are usually not needed for daily work and should be left unused . All tools have a man-page or good documentation available at the option --help .

13www.suse.com

The following tools are used on a regular basis:

smdbaThistoolsisusedtomanagethedatabase.Ithasthefollowingoptions:backup-hot:Enablecontinuousarchivingbackup.backup-restore:RestoretheSUSEManagerDatabasefrombackup.backup-status:Showbackupstatus.db-start:StarttheSUSEManagerDatabase.db-status:Showdatabasestatus.db-stop:StoptheSUSEManagerDatabase.space-overview:Showdatabasespacereport.

mgr-ncc-syncThiscommandisusedtomanagesubscriptionstothecustomercenter.Runningthecommandwithoutanoptionwillinitiateanimmediatesynchronizationoftheassignedchannels.Runningthecommandwiththeoption-lwillshowallchannelsavailablefortheassignedcredentials.Theoption-cchannelnamewillassignthechannelnameandwillstartanimmediatesynchronization.Theoption-rwillrefreshtheinformationstoredwiththeinformationinthecustomercenter.

mgr-bootstrapThiscommandisusedtocreatethebootstrapscriptusedforregisteringaserverandhasbeendiscussedinError:Referencesourcenotfound.

mgr-create-bootstrap-repoThiscommandisusedtogeneratetheneededrepositoriesusedduringregisteringaserverandhasbeendiscussedinError:Referencesourcenotfound.

mgrpushUpoadingRPMstoa(custom)channelisdonewiththistool.Pleaseseetheman-pagefordetailedinformation.

spacewalk-data-fsckThistoolwillcheckiftheinformationregardingthepackagesreportinthedatabaseispresentonthefilesystemandviceversa.

spacewalk-reportRunningwithoutanoption,thiswillshowalistorpredefinedreports.Runningthisoptionwithareportnamewillcreateacsv-formattedoutput.

spacecmdThisutilityprovidesalmostthesamefunctionalityasthatavailableinthewebGUI.Whenstartingspacecmdtherewillbeanownprompt.Withhelp,allavailableoptionsaredisplayed.

Updating the SUSE Manager ServerThe SUSE Manager Server itself is not registered (and should NOT be registered) in SUSE Manager, only to the customer center .

Updating this server is a manual action that should be done at least once per month . There are two supported ways to update the SUSE Manager:

1. Updating via an in-house SMT server containing the SUSE Manager channels

2. Updating via the customer center

Please use the following procedure:

Checkwiththefollowingcommandiftherearepatchesavailable:# zypper lu

Iftherearepatchesforspacewalk/SUSEManageravailableperformthefollowingactions:# spacewalk-service stop # zypper -n patch -l; zypper -n up -l # spacewalk-schema-upgrade # spacewalk-service start

IfthereareSUSELinuxEnterpriseServer11SP2/SP3patches,applypatchesandifneededreboottheserver.

Audit LogSUSE Manager has the ability to log all user actions to an external log sink . This give SUSE Manager full audit-log capabilities a re-quired by compliance rules .

It is enabled by adding the following line to /etc/rhn/rhn .conf

audit .enabled = 1

See http://wiki.novell.com/index.php/AuditLogKeeper for de-tails on the setup of the log consumer .

www.suse.com

Contact your local SUSE Solutions Provider, or call SUSE at:

1 800 796 3700 U .S ./Canada1 801 861 4500 Worldwide

SUSEMaxfeldstrasse 590409 NurembergGermany

264-000005-001 | 06/14 | © 2014 SUSE LLC. All rights reserved. SUSE and the SUSE logo are registered trademarks of SUSE LLC in the

United States and other countries. All third-party trademarks are the property of their respective owners.