ServerView Operations Manager V7.02

Transcription

1 Installation Guide - English FUJITSU Software ServerView Suite ServerView Operations Manager V7.02 Installing ServerView Operations Manager Software under Linux (Operations Manager, Update Manager, Event Manager) Edition April 2015

2 Comments Suggestions Corrections The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs. Feel free to send us your comments by to Certified documentation according to DIN EN ISO 9001:2008 To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard DIN EN ISO 9001:2008. cognitas. Gesellschaft für Technik-Dokumentation mbh Copyright and trademarks Copyright Fujitsu Technology Solutions. All rights reserved. Delivery subject to availability; right of technical modifications reserved. All hardware and software names used are trademarks of their respective manufacturers.

3 Contents 1 Introduction Target groups and objectives Technical requirements Last-minute changes/corrections Management console Central management station (CMS) ServerView database Operating-System-Dependent packages Changes since the previous version ServerView Suite link collection Documentation for the ServerView Suite Typographic conventions Product names - conventions 16 2 PRIMERGY server management Architecture Installation on the central management station Installation on the managed servers 24 3 Installing ServerView Operations Manager ServerView Operations Manager components JBoss Web server Calling and ports used Role-based user administration Managing certificates Web browser Changes on the system Requirements Management station Management console Rights Installation check list Installing the Operations Manager software 50 Installation under Linux 3

4 Contents Language settings Administrative user "svuser" in OpenDJ directory service Installation Parameters for directory service Update installation Installed Operations Manager packages Available services for operating Operations Manager Uninstalling the Operations Manager software Changing configuration parameters Collecting diagnosis data Troubleshooting Removing faulty/stuck packages Purging the system PostgreSQL server does not start ServerView Operations Manager cannot connect to the database server System with active PAM configuration JBoss does not work correctly 75 4 ServerView database Configuration files Connection to the ServerView database is interrupted Sample configuration for pgadmin Administering the ServerView database Backing up the ServerView database Restoring the ServerView database Exporting/Importing the ServerView database ServerView database on a remote database server Installation Update installation Uninstallation ServerView database backups Switching the database server Error diagnostic unixodbc Manager 85 4 Installation under Linux

5 Contents Error during installation/uninstallation Uninstalling the ServerView database System is slowing down Checking the status of PostgreSQL Starting and stopping PostgreSQL Restarting Operations Manager Changing the load distribution 89 5 Fujitsu Technology Solutions Software License Agreement for End User 91 Installation under Linux 5

6 6 Installation under Linux

7 1 Introduction ServerView Operations Manager (Operations Manager for short) is a free server management module of the Fujitsu ServerView Suite. It is used for central administration of industry-standard servers which run the operating systems Windows and Linux (SUSE and Red Hat) or which serve as hosts for virtual machines (VMs) that use hypervisors such as VMware ESX/ESXi, Citrix XenServer or Hyper-V. The standardized management of all servers occurs via one or more central management stations, which you can access from any workstation in the network that has a popular Web browser and the Java Runtime Environment. Operations Manager controls the individual systems, including critical hardware components such as processors, RAM, hard disks, fans and power supply. It monitors and controls the power consumption, analyzes the performance and utilization data and updates the server configuration. The security concept of Operations Manager includes role-based user management based on three underlying concepts: Global user management via an LDAP directory service (Lightweight Directory Access Protocol) Role-Based Access Control (RBAC) Single Sign-On (SSO) based on a Centralized Authentication Service (CAS) With RBAC you can tailor your security concept to the organizational structure of your company by assigning a task-oriented authorization profile to each role. SSO means that you only need to authenticate yourself once. Once you have done this successfully, you are given access to all ServerView components without having to sign on to any of them again. Installation under Linux 7

8 1 Introduction Server management with Operations Manager offers important benefits to operators of a comprehensive server network: Higher productivity thanks to high failsafety of the servers Reduced costs through automated monitoring of the IT infrastructure Flexible expansion possibilities for the servers, as Operations Manager can be easily adjusted to changed conditions Shorter downtimes thanks to simplified error analysis Guarantees energy-efficient and, where possible, uninterruptible server operation Quicker response times in the event of errors Reduction in total cost of ownership (TCO) through efficient use of network components and their resources Very easy operation thanks to ergonomic software: clearly laid out, intelligent user guidance and supportive help system 1.1 Target groups and objectives This manual is intended for system administrators, network administrators and service technicians that have a basic knowledge of hardware and software. The manual documents the requirements for the use of Operations Manager that are specific to the operating system and describes the installation of the products ServerView Operations Manager, ServerView Update Manager and ServerView Event Manager. 8 Installation under Linux

9 1.2 Technical requirements 1.2 Technical requirements Last-minute changes/corrections Any last-minute changes/corrections of the technical requirements can be found in the Readme file on the ServerView Suite DVD 2. You have the following options: ServerView Operations Manager On the DVD switch to the directory SVSSoftware Software ServerView Linux ServerView_S2. Start the DVD and select in the Welcome dialog ServerView Software Products Start; Info under ServerView Operations Manager Management console Standard PC, LAN with http access Microsoft Windows with Internet Explorer V9/V10 or Mozilla Firefox V16/V17 or higher. For use with JRE 1.7.0_45 or higher, Firefox as of V25 is required. SUSE/Red Hat Linux with default Web browser released with distribution Java Runtime Environment (JRE) V1.7.0_40 or higher Central management station (CMS) Hardware PRIMERGY server Only for PRIMEQUEST: PRIMEQUEST server Processors with at least two cores Main memory: at least 4 GB RAM 100 MBit-LAN At least 100 GB free disk space Graphics 1280 x 1024 (recommended: minimum 1024 x 768) Installation under Linux 9

10 1 Introduction Software SUSE (SLES 11): SP2 and SP3 Red Hat Enterprise Linux 5.9/5.10 Red Hat Enterprise Linux 6.4/6.5 Red Hat Enterprise Linux 7.0 Database (local and remote) PostgreSQL (contained in the ServerView package) Java Runtime Environment Java Runtime Environment (JRE) V1.7.0_40 or higher 1.3 ServerView database Operations Manager uses an SQL database. This database is a prerequisite for the Operations Manager software. PostgreSQL is used as the database management system. As of Operations Manager version 4.80 you can install the ServerView database separately on a remote database server. For further information, see "ServerView database on a remote database server" on page 82. The installation software contains the PostgreSQL database management system. This PostgreSQL is automatically installed when you install the Operations Manager software. This does not affect the operation of an already installed PostgreSQL database management system. For PostgreSQL administration you can use pgadmin3 (only for Windows), which you can download from Please use a version 1.8.x. For further information on the ServerView database under Linux, see "ServerView database" on page Installation under Linux

11 1.4 Operating-System-Dependent packages 1.4 Operating-System-Dependent packages Depending on the installed operating system, you must install additional packages for the various ServerView components (Operations Manager and ServerView RAID Manager). Very detailed lists on operating-system-dependent packages are provided in "Requirements" on page 31. When you update the relevant operating systems, the version specifications of the packages may change. The extra packages required for ServerView agents are described in "ServerView Agents for Linux" installation guide. SLES 11 With SUSE SLES 11, the easiest way to subsequently install the required rpm packages is via the YaST control center by selecting Software Install or delete software. YaST also resolves the dependencies and selects the installation source. Red Hat (RHEL5, RHEL6, and RHEL7) Subsequent installation of the required rpm packages should be done by YUM or by Add/Remove Software functionality available in Gnome Tool bar (Red Hat 5 in entry Application, Red Hat 6 in entry System - Administration). These tools detect themselves when a package has dependencies on other packages which are not yet installed. The missing packages are then listed and you can confirm whether you want to have these installed as well. Installation is possible from the DVD or the mounted DVD image (e.g. mount RHEL5-Server i386-DVD.iso -t iso9660 -o loop /mnt) with the rpm command. Installation under Linux 11

12 1 Introduction 1.5 Changes since the previous version This edition of the manual applies to ServerView Operations Manager V7.02 or later and replaces the online manual "ServerView Operations Manager V Installing ServerView Operations Manager Software under Linux", edition October The manual features the following changes and enhancements: As of ServerView Operations Manager V7.02, Java 8 is required on management console and central management station. 1.6 ServerView Suite link collection Via the link collection, Fujitsu Technology Solutions provides you with numerous downloads and further information on the ServerView Suite and PRIMERGY servers. For ServerView Suite, links are offered on the following topics: Forum Service Desk Manuals Product information Security information Software downloads Training 12 Installation under Linux

13 1.6 ServerView Suite link collection The downloads include the following: o o o Current software statuses for the ServerView Suite as well as additional Readme files. Information files and update sets for system software components (BIOS, firmware, drivers, ServerView agents and ServerView update agents) for updating the PRIMERGY servers via ServerView Update Manager or for locally updating individual servers via ServerView Update Manager Express. The current versions of all documentation on the ServerView Suite. You can retrieve the downloads free of charge from the Fujitsu Technology Solutions Web server. For PRIMERGY servers, links are offered on the following topics: Service Desk Manuals Product information Spare parts catalogue Access to the link collection You can reach the link collection of the ServerView Suite in various ways: 1. Via ServerView Operations Manager. Select Help Links on the start page or on the menu bar. This opens the start page of the ServerView Suite link collection. 2. Via the start page of the online documentation for the ServerView Suite on the Fujitsu Technology Solutions manual server. You access the start page of the online documentation via the following link: In the selection list on the left, select x86 Servers. On the right, click PRIMERGY ServerView Links under Selected documents. This opens the start page of the ServerView Suite link collection. Installation under Linux 13

14 1 Introduction 3. Via the ServerView Suite DVD 2. In the start window of the ServerView Suite DVD 2, select the option Select ServerView Software Products. Click Start. This takes you to the page with the software products of the ServerView Suite. On the menu bar select Links. This opens the start page of the ServerView Suite link collection. 1.7 Documentation for the ServerView Suite The documentation can be downloaded free of charge from the Internet. You will find the online documentation at under the link x86 Servers. For an overview of the documentation to be found under ServerView Suite as well as the filing structure, see the ServerView Suite sitemap (ServerView Suite Site Overview). 14 Installation under Linux

15 1.8 Typographic conventions 1.8 Typographic conventions The following typographic conventions are used: Convention Explanation bold Indicates various types of risk, namely health risks, risk of data loss and risk of damage to devices. Indicates additional relevant information and tips. Indicates references to names of interface elements. monospace Indicates system output and system elements, e.g., file names monospace semibold blue continuous text pink continuous text <abc> [abc] [key] and paths. Indicates statements that are to be entered using the keyboard. Indicates a link to a related topic. Indicates a link to a location you have already visited. Indicates variables which must be replaced with real values. Indicates options that can be specified (syntax). Indicates a key on your keyboard. If you need to enter text in uppercase, the Shift key is specified, for example, [SHIFT] + [A] for A. If you need to press two keys at the same time, this is indicated by a plus sign between the two key symbols. Screenshots Some of the screenshots are system-dependent, so some of the details shown may differ from your system. There may also be system-specific differences in menu options and commands. Installation under Linux 15

16 1 Introduction 1.9 Product names - conventions In the document, product names used in the text are abbreviated as follows: Windows Server 2012 and 2012 R2 16 Installation under Linux

17 1.9 Product names - conventions Windows Server 2008 and 2008 R2 Installation under Linux 17

18 1 Introduction Linux Virtualization software 18 Installation under Linux

19 2.1 Architecture 2 PRIMERGY server management 2.1 Architecture The architecture of ServerView Operations Manager is based on a management console, a central management station (CMS) and the managed servers. Installation under Linux 19

20 2 PRIMERGY server management Management console A browser-based console allows you to manage the servers and display the determined data. The following can be used as a browser: Microsoft Windows with Internet Explorer or Mozilla Firefox SUSE/Red Hat Linux with default Web browser released with distribution The Java Runtime Environment must also be installed. 20 Installation under Linux

21 2.1 Architecture Central management station (CMS) On the central management station the ServerView Operations Manager is installed. The optional components of the ServerView Suite, such as Virtual IO-Manager, are also installed on the central management station and integrated in Operations Manager. The central management station (and thus the ServerView Operations Manager with its components) may also run on a Windows or Linux virtual machine (VM). The global user management of the ServerView Suite and of the irmc each centrally stores users for all Central Management Stations (CMS) / irmc in the directory of an LDAP directory service. This enables you to manage the users on a central server. The users can therefore be used by all the CMS and irmc that are connected to this server in the network. The ServerView Suite currently supports the following directory services: OpenDS/OpenDJ (running in embedded mode on JBoss 5.1 resp. JBoss 7). Microsoft Active Directory During the installation of ServerView Operations Manager you have the option to choose ServerView s internal directory service (OpenDJ). For further information about the use of directory services with ServerView, refer to the manual User Management in ServerView (see "Documentation for the ServerView Suite" on page 14). The data which ServerView creates and uses is stored in an SQL database within an SQL Server. The following SQL Server are part of the ServerView Operations Manager installation: SQL Server 2008 R2/2005 Express under Windows Server PostgreSQL under Linux However, other Microsoft SQL Server databases can be used under Windows. Installation under Linux 21

22 2 PRIMERGY server management The Java Runtime Environment is required on the central management station. How to install the ServerView Operations Manager is explained in the following manuals: Installing ServerView Operations Manager Software under Windows Installing ServerView Operations Manager Software under Linux Managed servers On the managed servers, ServerView agents, CIM providers, or ServerView Agentless Service should be installed, which supply the information to the central management station. ServerView RAID Manager and ServerView Update Agent should be also installed on the managed servers. The installation of ServerView agents on virtual machines (VMs) is not released. The ServerView agents are available for Windows, Linux, VMware ESX and Citrix XenServer. ServerView CIM Providers are available for Windows, Linux and VMware ESXi. ServerView Operations Manager currently only supports ServerView CIM providers for VMware ESXi. How to install them is explained in the following manuals: ServerView Agents for Windows ServerView Agents for Linux Installing ServerView ESXi CIM Provider ServerView CIM Providers for Windows, Linux, and VMware ESXi 22 Installation under Linux

23 2.2 Installation on the central management station 2.2 Installation on the central management station You have to install Operations Manager (incl. ServerView Update Manager) on a management station and thus of monitoring the PRIMERGY servers via PC or notebook with a standard Web browser. Furthermore you can install the Event Manager on the central management station or on its own on another server. To display CIM indications from VMware vsphere Hypervisor server (ESXi-Server) in Event Manager, you have to install Operations Manager on the same server. You can install the Operations Manager on the following operating systems: Windows, SUSE Linux and Red Hat Linux. The Operations Manager software is supplied on the ServerView Suite DVD 2: Installation under Linux is script-based and involves the installation of Operations Manager, Update Manager, and Event Manager. The installation is described in "Installing ServerView Operations Manager" on page 25. A Installation Wizard is provided for installation under Windows. This covers the installation of Operations Manager, Update Manager, and Event Manager. In addition, the Wizard permits separate installation of the Operations Manager software on different servers. Installation can also occur in the Windows command line mode. The installation is described in "Installing ServerView Operations Manager Software under Windows" user guide. Installation under Linux 23

24 2 PRIMERGY server management 2.3 Installation on the managed servers The following components must be installed on the managed servers. These are operating-system-specific programs which supply information to the management station, which supplies information to the central management station: ServerView agents, CIM providers, or ServerView Agentless Service The ServerView agents are available for Windows, Linux, VMware ESX and Citrix XENServer. CIM providers are available for VMware ESXi. The installation is described in the "ServerView Agents for Windows", "ServerView Agents for Linux", "ServerView CIM Providers for Windows"and "Installation ServerView ESXi CIM Provider" user guides. ServerView Agentless Service is available for Windows and Linux. The ServerView System Monitor is installed automatically (via the ServerView agents installation) and allows you to monitor and check some server information locally on the server. A detailed description can be found in the "ServerView System Monitor" user guide. ServerView update agent To keep the managed servers up-to-date by Update Management functions the ServerView update agent must be installed on the managed servers. How to do this is described in the "ServerView Update Management" user guide. Additional installation on the management station ServerView RAID Manager ServerView RAID Manager offers standardized administration and management of hard disks for PRIMERGY servers. Unless the ServerView RAID Manager is installed, no information about RAID drives and their statuses will be available. The installation is described in the "RAID Management" user guide. 24 Installation under Linux

25 3.1 ServerView Operations Manager components 3 Installing ServerView Operations Manager This chapter describes how to install the Operations Manager software on the management station under Linux. Installation of the Operations Manager software involves installing Operations Manager and Event Manager. The corresponding software is supplied on the ServerView Suite DVD ServerView Operations Manager components ServerView Operations Manager installation When you install ServerView Operations Manager, the following ServerView components are also automatically installed: ServerView Configuration Manager With ServerView Configuration Manager, you can make system-dependent configurations on a managed server. (Only supported for servers on which the ServerView agents are installed.) ServerView Archive Manager With Archive Manager you can record system and operating data of PRIMERGY servers and store it centrally. This data can then be checked and evaluated. ServerView Inventory Manager With Inventory Manager you can retrieve data of a managed server or multiple servers and display it on the screen. You can also export the data from Operations Manager and store it in various formats (e.g. CSV, ODBC). ServerView Performance Manager With Performance Manager you can monitor the performance of specific server components. Performance Manager works on the basis of rules. The centrally created rules can be executed on any number of servers. ServerView Threshold Manager With Threshold Manager you can monitor one or more managed PRIMERGY servers and any virtual machines running on them centrally from the Installation under Linux 25

26 3 Installing ServerView Operations Manager management station on the basis of threshold values. ServerView Remote Management Frontend ServerView Remote Management Frontend provides a Web-based work environment for the remote management of PRIMERGY servers. ServerView Update Manager installation When you install Update Manager, the following ServerView Operations Manager components are also installed: Update Manager With Update Manager you can install and update software across an entire domain via a central management station. Repository Manager With Repository Manager you can manage the update repository. Download Manager With Download Manager you can conveniently obtain the latest statuses of firmware, BIOS, drivers and ServerView agents for your servers. Configuration With Configuration you can set global parameters for Update Manager. ServerView Event Manager installation When you install Event Manager, the following ServerView Operations Manager components are also installed: Alarm Monitor Alarm Monitor displays all incoming alarms for the selected servers and server groups in the Operations Manager main window. Alarm Configuration The Alarm Configuration component lets you define settings for alarm handling. You can define alarm rules, filter rules and general settings. 26 Installation under Linux

27 3.2 JBoss Web server 3.2 JBoss Web server The Web server used is JBoss. The necessary files for JBoss are automatically installed when ServerView Operations Manager is installed. JBoss is configured as a standalone service ServerView JBoss Application Server You can start and stop the service. Use the following command: /etc/init.d/sv_jboss start stop You can enable or disable restarting JBoss once a month. Disable is set by default. If you want to enable restarting JBoss monthly, you should call ChangeComputerDetails.sh command. The ChangeComputerDetails.sh command is located in the directory /opt/fujitsu/serverview/svom/serverview/tools. If you want to enable restarting JBoss monthly, proceed as follows. 1. Switch to the directory where ChangeComputerDetails.sh is located: cd /opt/fujitsu/serverviewsuite/svom/serverview/tools 2. Run ChangeComputerDetails.sh: sh ChangeComputerDetails.sh 3. Type yes when you are asked Do you want to restart Jboss once a month? Automatic deletion of JBoss access logs Log files localhost_access_log.<yyyy-mm-dd>.log are written in the directory <installation_path>/jboss/standalone/log. A separate log is created for each day. In previous versions they were never deleted. As of version 5.10, JBoss now includes automatic deletion. In the directory <installation_path>/jboss/standalone/svconf the sv-com-config.xml configuration file describes the parameters: <ns0:filenameprefix>localhost_access_log.</ns0:filenameprefix> List of file name prefixes, qualifying the files that are to be checked for deletion. The default is a list with the single entry "localhost_access_log.". Installation under Linux 27

28 3 Installing ServerView Operations Manager <ns0:testinterval>12:00</ns0:testinterval> Test interval, measured in minutes. The test interval can range between 1 minute and 24 hours. The behavior of the automated file deletion depends on the specified value: Number [ ] File checking begins when JBoss starts up, and is repeated at the specified time interval. Time [hh:mm] The test interval is 24 hours and the file checking occurs every day at the specified time. (The values for hh range from 00 till 23.) The default is 12:00, i.e. files are checked every day at noon. <ns0:maxage>10080</ns0:maxage><!-- one week --> Maximum age of a log file, measured in minutes. Any file matching an entry in the filenameprefix list which is older than this value is deleted. The default is 10080, i.e. seven days. If no value is specified in the configuration file, the value 4320, i.e. three days, is used Calling and ports used The entry address of the Operations Manager begins with the prefix https. Port Used for 3169 http (When trying to access this port, Operations Manager versions older than V4.92 are automatically redirected to port 3170.) 3170 https (The port must be unlocked in the firewall.) 3171 Update Management (The port must be unlocked in the firewall to allow Update Management.) 3172 Remote Connector Service (Server Configuration Manager, Power Monitor, etc.) (The port must be unlocked in the firewall.) 3173 ServerView RAID Manager 28 Installation under Linux

29 3.2 JBoss Web server Port 1325, 9999 Some additional ports are used for dynamical assignment of system components. Used for JBoss (only used for internal socket connections) 1473 non-ssl port of ServerView s directory service (OpenDJ) 1474 LDAPS, if OpenDJ is configured as directory service OpenDJ control port 9212 PostgreSQL database server (only for Linux) 9363 used by the Operations Manager to contact XEN daemons 16509, used by the KVM service For detailed security information see the White Paper Secure PRIMERGY Server Management. To gather information, Operations Manager accesses the following ports of all network nodes of a subnet which is specified on ServerBrowser and managed servers. Port Used for 80 Citrix 135 Hyper-V 161 SNMP 443 VMware 623 BMC (irmc) 3172 ServerView Remote Connector 5988 VMware 5989 VMware Installation under Linux 29

30 3 Installing ServerView Operations Manager Port Used for 9363 XEN KVM KVM Role-based user administration JBoss also enables role-based user administration. For further information on managing certificates, see "User Management in ServerView" user guide Managing certificates To communicate with the JBoss Web server, Web browsers always use an HTTPS connection (i.e. a secure SSL connection). Therefore, the JBoss Web server needs a certificate (X.509 certificate) to authenticate itself at the Web browser. The X.509 certificate contains all the information required to identify the JBoss Web server plus the public key of the JBoss Web server. For further information on managing certificates, see "User Management in ServerView" user guide. 3.3 Web browser A Web browser is required to display the data. This means that the data can be transmitted via a LAN to any other computer that has a Web browser and displayed there. The browser must be able to interpret HTML V3.2 and Javascript V1.1. If you should experience problems when accessing the Web server, make the following settings in the browser: Disable the access option for the use of a proxy entirely in the browser, or Enter the IP address at an appropriate position to specify that no proxy is to be used for the host on which the Web server is running. 30 Installation under Linux

31 3.4 Changes on the system 3.4 Changes on the system ServerView Operations Manager creates a user svuser and a group svgroup. Almost all processes are started under this ID. By default, Operations Manager installs its own directory service, OpenDJ. You cannot change the password via OpenDJ. You can only change it locally by using the script ChangeComputerDetails.sh, see "Changing configuration parameters" on page 69. For the PostgreSQL server the user postgpls is created. For regular database server activities a cron job is created. For ODBC access to the database server, additions are made to the configuration files of the ODBC Manager. For snmptrap the configuration file /etc/snmp/snmptrapd.conf is modified to contain the following entries: disableauthorization yes ignoreauthfailure yes 3.5 Requirements On 64-bit systems, the distribution includes many packages for both architectures, 32-bit and 64-bit. 32-bit packages are distinguished differently on the different platforms. On SLES systems the package name has the file extension 32bit. On RHEL systems the architecture part of the package takes the value i386, i586 or i Management station JBoss Web server The JBoss Web server is installed when you install the ServerView Operations Manager software. The corresponding service is automatically started when you start Operations Manager. Installation under Linux 31

32 3 Installing ServerView Operations Manager Before version V5.00, httpd service was required. V5.00 or higher does not require httpd service. Network configuration The commands hostname and hostname -f must deliver valid names. The network configuration can be set up in various ways. This condition is satisfied for many configurations if the server is entered in /etc/hosts with its domain name. Example myserver.mydomain The local host must be entered in /etc/hosts with the IP address to give ServerView access to the database server. With ServerView Operations Manager as of V5.30 the fully qualified hostname of the central management station is decisive for its correct working. Normally the fully qualified hostname is the host s name plus domain name. But depending on the netconfiguration it may be a simple hostname without any domainname. Your network configuration must allow access to the central management station by using the fully qualified hostname from: o o o o the central management station itself any monitoring station the managed node HW management boards like MMB, irmc Java Runtime Environment You can check whether the package is installed with the following command: rpm -q jre Install the package for the Java Runtime Environment from the ServerView Suite DVD 2: 1. Place the ServerView Suite DVD 2 in the drive. 2. Open a terminal and switch to the mounted directory. 3. Switch to the directory: 32 Installation under Linux

33 3.5 Requirements SVSSoftware Software Other_Tools Java Linux 4. Extract the package for Linux with the following command: sh jre-<version>-linux-i586-rpm.bin 5. Accept the license agreement. 6. Install the extracted rpm file. If you are also using the management station as a management console, the Java plug-in must be activated and depending on the platform 64-bit jre must be installed. SELinux must be deactivated on distributions on which it is not supported by ServerView Operations Manager. SELinux is supported on RHEL6 and RHEL7. On these distributions you may set SELinux to enforcing with default policies. On the remaining supported distributions, SELinux must be set to disabled. Root / superuser access ServerView Operations Manager creates a user postgpls. Postgpls and root require superuser access. The user postgpls is secure, as it can only be called via superuser. Directory access rights The /tmp directory must have read, write and execution rights for all. Use the package managers of the platforms to install missing packages. These are Yast on SLES platforms and Add/Remove Software in menu bar as well as YUM on RHEL platforms. These platform managers implicitly resolve all dependencies. How to configure YUM, see "Configuring YUM" on page 42. You may check whether a package is installed with the following command: rpm -q <package name> On RHEL 64-bit systems you must use the following command in order to view the architecture of the package. Please pay attention to this. rpm -q --queryformat %{NAME} %{ARCH} Installation under Linux 33

34 3 Installing ServerView Operations Manager For RHEL 64-bit platforms we always also state the architecture of the package separated by a dot from the package name. You can directly use this syntax name.arch in the package manager. Prerequisites packages per platform RHEL bit: compat-libstdc++-33 curl e2fsprogs-libs glibc gzip keyutils-libs krb5-libs libgcc libidn libselinux libsepol libtermcap libxml2 net-snmp openssl unixodbc unixodbc-libs zlib Prerequisites for special functionality: DeskView Interface: curl RHEL/KVM monitoring: libvirt RHEL bit: compat-libstdc++-33.i386 curl.i Installation under Linux

35 3.5 Requirements e2fsprogs-libs.i386 glibc.i686 gzip.x86_64 keyutils-libs.i386 krb5-libs.i386 libgcc.i386 libidn.i386 libselinux.i386 libsepol.i386 libtermcap.i386 libxml2.i386 net-snmp.x86_64 openssl.i686 unixodbc.i386 unixodbc-libs.i386 zlib.i386 Prerequisites for special functionality: DeskView Interface: curl.i386 RHEL/KVM monitoring: libvirt.x86_64 RHEL bit: See package list of "RHEL bit:" on page 34. RHEL bit: See package list of "RHEL bit:" on page 34. RHEL bit: compat-libstdc++-33 cyrus-sasl-lib glibc gzip Installation under Linux 35

36 3 Installing ServerView Operations Manager keyutils-libs krb5-libs libcom_err libcurl libgcc libidn libselinux libssh2 libstdc++ libtool-ltdl libxml2 ncurses-libs net-snmp nspr nss nss-softokn-freebl nss-util openldap openssl unixodbc zlib Prerequisites for special functionality: DeskView Interface: curl RHEL/KVM monitoring: libvirt-client RHEL bit: compat-libstdc++-33.i686 cyrus-sasl-lib.i686 glibc.i686 gzip.x86_64 36 Installation under Linux

37 3.5 Requirements keyutils-libs.i686 krb5-libs.i686 libcom_err.i686 libcurl.i686 libgcc.i686 libidn.i686 libselinux.i686 libssh2.i686 libstdc++.i686 libtool-ltdl.i686 libxml2.i686 ncurses-libs.i686 net-snmp.x86_64 nspr.i686 nss.i686 nss-softokn-freebl.i686 nss-util.i686 openldap.i686 openssl.i686 unixodbc.i686 zlib.i686 Prerequisites for special functionality: DeskView Interface: curl.x86_64 RHEL/KVM monitoring: libvirt-client.x86_64 RHEL bit: See package list of "RHEL bit:" on page 35. RHEL bit: See package list of "RHEL bit:" on page 36. Installation under Linux 37

38 3 Installing ServerView Operations Manager RHEL bit: glibc.i686 gzip.x86_64 keyutils-libs.i686 krb5-libs.i686 libcom_err.i686 libcurl.i686 libgcc.i686 libselinux.i686 libstdc++.i686 libtool-ltdl.i686 libxml2.i686 ncurses-libs.i686 net-snmp.x86_64 nss-softokn-freebl.i686 openssl-libs.i686 pcre.i686 unixodbc.i686 xz-libs.i686 zlib.i686 Prerequisites for special functionality DeskView Interface: curl RHEL/KVM monitoring: libvirt-client SLES11 SP2 32-bit: cyrus-sasl glibc gzip keyutils-libs krb5 38 Installation under Linux

39 3.5 Requirements libcom_err2 libcurl4 libgcc46 libidn libldap-2_4-2 libltdl7 libopenssl0_9_8 libstdc++33 libstdc++46 libxml2 net-snmp termcap unixodbc zlib Prerequisites for special functionality: DeskView Interface: curl RHEL/KVM monitoring: libvirt SLES11 SP2 64-bit: cyrus-sasl-32bit glibc-32bit gzip keyutils-libs-32bit krb5-32bit libcom_err2-32bit libcurl4-32bit libgcc46-32bit libidn-32bit libldap-2_4-2-32bit libltdl7-32bit Installation under Linux 39

40 3 Installing ServerView Operations Manager libopenssl0_9_8-32bit libstdc bit libstdc bit libxml2-32bit net-snmp termcap-32bit unixodbc unixodbc-32bit zlib-32bit Prerequisites for special functionality DeskView Interface: curl RHEL/KVM monitoring: libvirt SLES11 SP3 32-bit: cyrus-sasl glibc gzip keyutils-libs krb5 libcom_err2 libcurl4 libgcc_s1 libidn libldap-2_4-2 libltdl7 libopenssl0_9_8 libstdc++33 libstdc++6 libxml2 net-snmp 40 Installation under Linux

41 3.5 Requirements termcap unixodbc zlib Prerequisites for special functionality DeskView Interface: curl RHEL/KVM monitoring: libvirt SLES11 SP3 64-bit: cyrus-sasl-32bit glibc-32bit gzip keyutils-libs-32bit krb5-32bit libcom_err2-32bit libcurl4-32bit libgcc_s1-32bit libidn-32bit libldap-2_4-2-32bit libltdl7-32bit libopenssl0_9_8-32bit libstdc bit libstdc++6-32bit libxml2-32bit net-snmp termcap-32bit unixodbc unixodbc-32bit zlib-32bit Prerequisites for special functionality Installation under Linux 41

42 3 Installing ServerView Operations Manager DeskView Interface: curl RHEL/KVM monitoring: libvirt Configuring YUM You need to provide a configuration file in /etc/yum.repos.d to make the DVD or the iso-file of the RHEL distribution known to YUM. 1. Often the RHEL distribution DVD or an iso-file of the DVD is mounted to the directory /media/rhel xxx xxx xx, containing several blanks. YUM cannot handle such paths. Therefore do the following: ln -s /media/rhel xxx xxx xx /tmp/instmedia Example ln -s '/media/rhel_6.2 x86_64 Disc 1' /tmp/instmedia The automatic typing extension of the shell might insert \ before the blanks into the path name of the RHEL iso. Be sure to remove them. 2. The RHEL DVD / iso file contains several YUM repositories. You need to specify each of the repositories in the YUM configuration file, if you want to use it. The main repository is located under the directory Server. Normally you only need this. In the directory /etc/yum.repos.d create a file named rheldistro.conf with the following contents. Example for RHEL5 [instserver] name=rhel 5.x iso image / directory Server baseurl=file:/tmp/instmedia/server enabled=1 gpgcheck=0 [instvt] name=rhel 5.x iso image directory VT baseurl=file:/tmp/instmedia/vt enabled=1 gpgcheck=0 42 Installation under Linux

43 3.5 Requirements The directory VT on the DVD / iso-file contains the virtlib packages that you may need. Example for RHEL6: name=rhel 6.2 iso image Server baseurl='file:/tmp/instmedia/server' enabled=1[instserver] gpgcheck=0 3. Test your YUM configuration: yum list unixodbc should list unixodbc on all SLES / 32-Bit and RHEL / 32-Bit unixodbc.i686 and unixodbc.x86_64 on RHEL / 64-Bit unixodbc and unixodbc-32bit on SLES / 64-Bit Management console Web browser (Linux): default Web browser released with distribution Please make sure that the Java plug-in is activated. If the Java plug-in is not yet installed on the management console, proceed as follows to install it: 1. Open a terminal window. 2. Install the Java Runtime system from the ServerView Suite DVD 2, see Java Runtime. 3. Set up the link for the plug-in. On 32-bit systems ascertain the browser s plug-in directory: o On RHEL 5, this is usually the following directory: /usr/lib/<browser_name>/plugins or /opt/lib/<browser_name>/plugins or /usr/lib/mozilla/plugins or /usr/lib/browser-plugins Installation under Linux 43

44 3 Installing ServerView Operations Manager o o o o On RHEL 6 the plugin directory is /usr/lib/mozilla/plugins. On SLES 11 the plugin directory is /usr/lib/browser-plugins. To find out the directory you can also enter the following command: rpm -ql <browser_name> grep plugins Switch to the plug-in directory: cd <plugin_directory> Find out the path name of the plug-in. If a link to libjavaplugin_ oji.so exists, remove it. rpm -ql jre grep libnpjp2.so Set up the link, e.g. ln -s /usr/java/<jre1.7.0_ 51>/lib/i386/libnpjp2.so libnpjp2.so The following passage is on setting up browser plugins for 64-bit systems: For SLES bit, RHEL 5 64-bit and RHEL 6 64-bit proceed in the following way. Ascertain the browser's plugin directory: o o o o o o o On SLES bit this is usually /usr/lib64/browser-plugins. On RHEL 5 and RHEL 6 the plugin directory is /usr/lib64/mozilla/plugins. If the plugin directory does not exist, then create it. Ensure that you installed Java Runtime Environment 64-bit. Execute the following: rpm -qa --queryformat '%{Name}-%{VERSION}.% {ARCH}\n' grep jre The architecture extension must be x86_64. Switch to the plug-in directory: cd <plugin_directory> Find out the path name of the plug-in. If a link to libjavaplugin_ oji.so exists, remove it. rpm -ql jre grep libnpjp2.so Set up the link, e.g. 44 Installation under Linux

45 3.6 Rights ln -s /usr/java/<jre1.7.0_ 13>/lib/amd64/libnpjp2.so libnpjp2.so Web browser for Windows: o o Internet Explorer V9/V10 Mozilla Firefox V16/V17 or higher. For use with JRE 1.7.0_45 or higher, Firefox as of V25 is required. Web browser for Linux: o Default Web browser released with distribution 3.6 Rights For installation and configuration, you must have administrator rights, i.e. you must be logged onto the server as the superuser root. 3.7 Installation check list Web browser No. Check point 1 Supported version Configuration Supported Web browser for Windows is the following: Internet Explorer V9/V10 Mozilla Firefox V16/V17 or higher. For use with JRE 1.7.0_ 45 or higher, Firefox as of V25 is required. Supported Web browser for Linux is the following: Default Web browser released with distribution. Installation under Linux 45

46 3 Installing ServerView Operations Manager No. Check point 2 Trusted sites Configuration If you use Internet Explorer, add the URL of SVOM into Trusted sites. 1. Open Internet Explorer. 2. Select Tools Internet Options. 3. Click the Security tab and select Local intranet or Trusted sites. 4. Click Sites and enter the URL of the server on which SVOM is installed. 3 Proxy It cannot access to SVOM via proxy. Disable to use proxy on Web browser configuration bit/64- bit Table 1: Check list Web browser Java Runtime Environment (JRE) You can use the same architecture of Firefox as the system OS. i.e. 32-bit version of Firefox on 32-bit Linux, and 64-bit version of Firefox on 64-bit Linux. No. Check point Configuration 1 Supported version V1.7.0_40 or higher JRE must be installed on both server side (system where SVOM is installed) and client side bit/64-bit You can use the same architecture of JRE as the system OS. i.e. 32-bit version of JRE on 32-bit Linux, and 64-bit version of JRE on 64-bit Linux. 46 Installation under Linux

47 3.7 Installation check list No. Check point Configuration 3 Java Plug-in (only for Windows) Enable the next-generation Java Plug-in must be checked. This item is checked in default. 1. Open Java Control Panel. 2. Select Advanced tab. 3. Open Settings Java Plug-in. 4. Make sure that Enable the next-generation Java Plug-in is checked. 4 Security Configure security settings as follows: 5 Symbolic link (only for Linux) Table 2: Check list JRE OS settings No. Check point 1 host name resolve 1. Open Java Control Panel. 2. Select Advanced tab. 3. Open Settings Security Mixed code (sandboxed vs. trusted security verification. 4. Check Enable - hide warning and run with protections. Set up the link for the plug-in to access from Linux by Firefox. Please see "Requirements" on page 31. Configuration Hostname of the CMS must be available to resolve from both CMS itself (system where SVOM is installed) and client side. Make sure that the name resolve is available by the following commands. Windows: > tracert <hostname>.<dns suffix> Linux: # traceroute <hostname>.<dns suffix> Installation under Linux 47

48 3 Installing ServerView Operations Manager No. Check point 2 Network ports Configuration SVOM uses some network ports. Which ports SVOM requires is described in "Calling and ports used" on page host name Hostname and DNS suffix of CMS must not contain underscore ('_'). 4 SQL instance (only for Windows) 5 Active Directory 6 Network drive 7 Terminal Server (only for Windows) 8 /etc/hosts (only for Linux) 9 SELinux (only for Linux) Table 3: Check list OS settings If you want to use not a bundled SQL Server but your own SQL Server, you must setup a suitable SQL Server instance before installing SVOM. Important: Please consider the notes for a local SQL Server and for a remote SQL Server. If you want to use Active Directory for directory service of SVOM, Active Directory must be installed and configured for SVOM before SVOM installation. When you install SVOM, the connection to Active Directory must be available. Details of configuration of Active Directory are described in the "User Management in ServerView" user guide. It is not possible to install SVOM to network drives. If the Terminal Services/Remote Desktop Services server role is installed, a special installation mode is required for installing Operations Manager. localhost must be resolved to It should be configured in /etc/hosts. Disable SELinux on distributions on which it is not supported by SVOM. 48 Installation under Linux

49 3.7 Installation check list Update Installation No. Check point 1 Base version Configuration Update installation is only possible from version or newer. Table 4: Check list update installation Installation under Linux 49

50 3 Installing ServerView Operations Manager 3.8 Installing the Operations Manager software The Operations Manager software (Operations Manager, Event Manager, and the Update Manager) and the database management system PostgreSQL can be installed under Linux (SUSE and Red Hat). You can install the ServerView database on a remote database server. For further information, see "ServerView database on a remote database server" on page 82. During installation the following messages can be ignored: warning: commands will be executed using /bin/sh warning: waiting to reestablish exclusive database lock Installation is script-based. The log file of the installation process (install.log or upgrade.log) is stored in the directory /var/log/fujitsu/serverviewsuite/serverview. 50 Installation under Linux

51 3.8 Installing the Operations Manager software If you have several different versions of ServerView Operations Manager, make sure to install the latest ServerView Operations Manager version. If an newer version of Operations Manager is already installed, you cannot perform a downgrade installation. To downgrade, you must uninstall the existing Operations Manager first. To install ServerView Operations Manager, use runlevel 3 or runlevel 5. Runlevel 1 (single mode) is not supported. When you install ServerView Linux Agents and ServerView Operations Manager on the same server, and if the Operations Manager is installed before the Agent, the server is not automatically registered to ServerView Operations Manager. Restart the system, or execute the following commands. /usr/bin/sv_services stop /usr/bin/sv_services start You cannot install both 64-bit ServerView agents for Linux and ServerView Operations Manager on the same server. During installation of Operations Manager, the system checks whether the ServerView agents for Linux are installed on the server. If so, the installation is aborted. To operate ServerView Operations Manager properly, a definition of the localhost line in /etc/hosts is required. Do not delete the definition of the localhost line. Edit/addition/deletion of ServerView-related files may give influences on operations. Make sure not to do any other operations than the ones explained in this documentation. Installation under Linux 51

52 3 Installing ServerView Operations Manager For Red Hat 7.0, it is mandatory to install the necessary ServerView Operations Manager prerequisites to avoid package inconsistencies. Therefore the necessary prerequisites will be checked before package installation starts. If there are missing prerequisites a warning message is given, e.g. Before installation please install package: libgcc.i686. The installation is aborted. For Red Hat 7.0, compat-libstdc++-33 library is installed automatically during ServerView Operations Manager installation. But compat-libstdc++-33 library will not be uninstalled, when ServerView Operations Manager is uninstalled Language settings You can set the language for the Operations Manager. Therefore you have the following possibilities: Calling up the script-based installation with the option -l --lang. If you call up the script without the language option and without the -q option, then a message is displayed for querying the language Administrative user "svuser" in OpenDJ directory service This section is only relevant if the OpenDJ directory service is used, which is the default for ServerView Operations Manager on Linux. The administrative user svuser is created in the OpenDJ database during installation of ServerView Operations Manager. In previous versions it was always installed with the default password admin, but as of ServerView Operations Manager version 5.50 you may specify the password for user svuser during a dialog-based installation. You may change the password at any time by executing the command ChangeComputerDetails.sh. Please note that this user svuser in the directory service OpenDJ is different from the operating system account svuser created during a new installation of ServerView Operations Manager. The password for svuser must not be an empty string. 52 Installation under Linux

53 3.8 Installing the Operations Manager software Installation Installation is performed with the install.sh script. For RHEL7 it is mandatory to install the necessary ServerView Operations Manager prerequisites to avoid package inconsistencies. Therefore the necessary prerequisites will be checked before package installation starts. If there are missing prerequisites a warning message is given, e.g. Before installation please install package: libgcc.i686. The installation is aborted. Proceed as follows: 1. Place the ServerView Suite DVD 2 in the drive. 2. Open a terminal and switch to the mounted directory. 3. Switch to the directory: SVSSoftware Software ServerView Linux ServerView_S2 4. Start the installation with the following command:./install.sh <option> Installation under Linux 53

54 3 Installing ServerView Operations Manager If you do not specify an option, the complete Operations Manager software will be installed by default. For <option> you can specify: -OM Only Operations Manager is installed. -UM Operations Manager and the Update Manager (as of version 4.91) are installed. -EM Only Event Manager is installed. -l --lang [en ja] You choose the language for the installation (English, or Japanese). --base Installs the ServerViewBase package. Use this option if you want to install the ServerView database on a remote database server, see "ServerView database on a remote database server" on page remotedbserver --RDBS Installs the packages ServerViewPostgresql and ServerViewDB. Use this option if you want to install the ServerView database on a remote database server, see "ServerView database on a remote database server" on page 82. -q --quiet Starts a silent installation. -f --force Forces an installation. If this option is set, the installation will continue even if one of the individual packages fails to install. Normally the installation would abort. This option should be used with caution. -i --installdir <directory> Specify the directory containing the RPM packages. Example -i <CD_root>/SVSSoftware/RPMS 54 Installation under Linux

55 3.8 Installing the Operations Manager software -v --verbose --debug Writes additional information to the log file during the installation. --snmp-community <community> By default the SNMP community is set to public. If it is different, you can specify the relevant community here. --ipaddr <IP_address> By default the first IP address found is used as local IP address for the central management station. If several IP addresses are available for the central management station you may specify another valid one. --ipchangecheck [yes no] By default the ServerListService service checks whether the IP address of the central management station has changed. You can deactivate this function by specifying no. You must specify this value if you specified an IP address different from the default IP address. --chgtrap [yes no] Change settings for connectivity changed notification during an upgrade installation.to change it for all servers to enabled, specify yes. --fqhostname <hostname> Fully qualified name of the server. Normally the name is extended to include the domain name. Depending on the network configuration, you can also specify just the server name without the domain name. If you cannot start the script, invoke it with /bin/bash install.sh. You can specify further parameters for directory server, see "Changing configuration parameters" on page 69. You close the license display by entering q and then confirming with yes. If you did not specify the language as argument, the following dialog will be displayed: Which language? Please enter en (for English) or ja (for Japanese): Enter the relevant language. Installation under Linux 55

56 3 Installing ServerView Operations Manager With a non-silent installation the following dialog is displayed unless the options --fqhostname or ipaddr were specified: Fully-qualified hostname: xxx.yyy.zzz (or sometimes only xxx) ok? (yes no): IP address:<ip address> ok? (yes no): The fully qualified name of the server and the IP address are determined automatically. The following dialog is only displayed if you use the directory service OpenDJ (default). You must specify password for opendj account svuser. Echo is off during password input. Password: Please repeat password: Provide the password that you want to give to the administrative user svuser for the OpenDJ directory service. Make sure you remember it, as you might need it later on for administration of OpenDJ. The password for svuser must not be an empty string. How to change the parameters after the installation is described in "Changing configuration parameters" on page Parameters for directory service ServerView Operations Manager makes use of a directory service, which stores information for authorization. By default, Operations Manager installs its own directory service, OpenDJ. Alternatively you may use your own directory service. Alternatively the use of Microsoft Active Directory Service is supported. During installation of Operations Manager you can specify further parameters for the Active Directory service. 56 Installation under Linux

57 3.8 Installing the Operations Manager software Installation via the install.sh script Two options are available: Either invoke a dialog or specify all parameters in command line. Invoking a dialog The dialog is not displayed by default. It is invoked by specifying an option in the command line. install.sh -d --ds-dialog This starts the dialog for you to enter parameters for the directory service. The dialog will be as follows: Specify parameters for directory service: Currently only Active Directory is supported). Host?: Port?: Use a LDAP backup server (yes no)?: If you answer with yes, the following parameter is displayed: LDAP backup server?: SSL (yes no; recommended: yes)?: Base DN?: User Search Base (e.g. CN=Users)?: User Search Filter (e.g. samaccountname=%u)?: User?: Password?: Do you want to configure a warning for the case of a user's password expiry? (yes no): Answering with "yes" invokes the following dialog which allows you to enter the parameters for the LDAP Password Policy Enforcement (LPPE): Installation under Linux 57

58 3 Installing ServerView Operations Manager Configuring the first three of the following parameters enables the LPPE, which is disabled by default. The fourth parameter is optional. LPPE handles a variety of login exceptions which would otherwise prevent user authentication. For more information see the manual "User Management in ServerView". Domain Distinguished Name (Example: dc=example,dc=com) Number of days a password is valid (e.g.: 90)?: Number of days a user is warned before the password expiry (e.g.: 30)?: Do you want to specify an URL to which the user will be redirected in order to change the password? (yes no)?: Answering with "yes",displays the following prompt: URL to which the user will be redirected in orderto change the password?: For each of the above parameters you must confirm your input as follows (example): Host?: xxxxx Host specified: xxxxx, ok? (yes no): no Host?: xxxxxy Host specified: xxxxxy, ok? (yes no): yes Then the next parameter will be displayed. Command line interface You can specify the following parameters via the command line interface: install.sh --ds-host <hostname> --ds-port <port> --ds-backup <yes no> --ds-backup-host <backup host name> --ds-ssl <yes no> --ds-basedn <dn> --ds-user <username> --ds-password <password> --ds-user-searchbase <searchbase> 58 Installation under Linux

59 3.8 Installing the Operations Manager software --ds-user-searchfilter <user search filter> --ds-domain <Domain Distinguished Name> --ds-val-days <days> --ds-warn-days <days> --ds-pw-url <URL> --ds-host <hostname> Fully-qualified name of the server on which the directory service is running.the fully qualified name is an unambiguous name which specifies the system in the network. It is important that this name can be always properly resolved! This can occur by use of an DNS or NIS server, or by appropriate entries in the hosts file of the central management station. If you are not sure whether you can provide for a proper name resolution, you can issue the system's IP address here. --ds-port <port> Port number used for access to the directory service. By default, port 389 is used for LDAP and port 636 is used for LDAPS (i.e. LDAP with SSL). --ds-backup <yes no> You can specify if a backup server for LDAP is used (yes) or not (no). If you answer with yes, the following parameter can be set: --ds-backup-host <backup host name> Fully-qualified server name on which a backup for the directory service is running. --ds-ssl <yes no> yes is enabled by default to protect the data transfer with SSL encryption. It is recommended that you always protect the connection to the directory service, as the user passwords transferred via this connection are not separately encrypted. Bear in mind, however, that Microsoft Active Directory does not offer SSL encryption as standard; a certificate must be installed on the Windows server system for this purpose. For further details, see "User Management in ServerView" user guide (section "Integrating ServerView user management into Microsoft Active Directory"). Installation under Linux 59

60 3 Installing ServerView Operations Manager --ds-basedn <dn> Base directory for the ServerView authorization data, e.g. OU=application,DC=fujitsu,DC=com. You can specify any directory in the Active Directory here. The Operations Manager setup procedure generates an LDIF file for importing the authorization data, which you must then import after the Operations Manager installation. For further details, see "User Management in ServerView" user guide (section "Integrating ServerView user management into Microsoft Active Directory"). --ds-user <username> User ID for read access to the data. The user ID should only have basic read rights. This password is stored in a text file so only a user with simple read access should be chosen. The user ID should be specified in the notation USERNAME@DOMAIN, as displayed in the Active Directory in the user s account settings under User logon name. --ds-password <password> Password for read access. --ds-user-searchbase <searchbase> Starting point for the user search in the directory server e.g. CN=Users,DC=fujitsu,DC=com. --ds-user-searchfilter <user search filter> Filter for user search, e.g. samaccountname=%u. --ds-domain <Domain Distinguished Name> Base directory for LPPE settings e.g. dc=example,dc=com --ds-val-days <days> Number of days a password is valid --ds-warn-days <days> Number of days a user is warned before the password expires. --ds-pw-url <URL> Optional. URL to which the user will be redirected in order to change the password, e.g Installation under Linux

61 3.8 Installing the Operations Manager software Parameters in the configuration file The file /etc/fujitsu/serverviewsuite/serverview/global.conf contains parameters for the configuration of the active directory service. Please do not change these parameters for the directory service manually. You may specify them during installation/upgrade as parameters or dialog to the script install.sh. You may change them any time by calling the script ChangeComputerDetails.sh. COM_DS_SERVER Directory service type: Active Directory Service or OpenDJ (Value: opendj or ad) COM_DS_HOST Fully-qualified name of the server on which the directory service is running.the fully qualified name is an unambiguous name which specifies the system in the network. It is important that this name can be always properly resolved! This can occur by use of an DNS or NIS server, or by appropriate entries in the hosts file of the central management station. If you are not sure whether you can provide for a proper name resolution, you can issue the system's IP address here. COM_DS_PORT Port number used for access to the directory service. By default, port 389 is used for LDAP and port 636 is used for LDAPS (i.e. LDAP with SSL). COM_DS_SSL yes is enabled by default to protect the data transfer with SSL encryption. It is recommended that you always protect the connection to the directory service, as the user passwords transferred via this connection are not separately encrypted. Bear in mind, however, that Microsoft Active Directory does not offer SSL encryption as standard; a certificate must be installed on the Windows server system for this purpose. For further details, see "User Management in ServerView" user guide (section "Integrating ServerView user management into Microsoft Active Directory"). COM_DS_BASE_DN Base directory for the ServerView authorization data, e.g. OU=application,DC=fujitsu,DC=com. You can specify any directory in the Installation under Linux 61

62 3 Installing ServerView Operations Manager Active Directory here. The Operations Manager setup procedure generates an LDIF file for importing the authorization data, which you must then import after the Operations Manager installation. For further details, see "User Management in ServerView" user guide (section "Integrating ServerView user management into Microsoft Active Directory"). COM_DS_USER User ID for read access to the data. The user ID should only have basic read rights. This password is stored in a text file so only a user with simple read access should be chosen. The user ID should be specified in the notation USERNAME@DOMAIN, as displayed in the Active Directory in the user s account settings under User logon name. COM_DS_USER_SEARCHBASE Starting point for the user search in the directory server e.g. CN=Users,DC=fujitsu,DC=com. COM_DS_SEARCHFILTER Filter for user search, e.g. samaccountname=%u. COM_DS_DOMAIN Base directory for LPPE settings, e.g. dc=example,dc=com COM_DS_VAL_DAYS Number of days a password is valid, e.g. 90. COM_DS_WARN_DAYS Number of days a user is warned before the password expires, e.g. 30. COM_DS_PW_URL Optional. URL to which the user will be redirected in order to change the password, e.g Update installation Update installation to version 6.10 is only supported as of Operations Manager version Do not stop Postgresql when you execute the update installation. The update installation is not correctly done. 62 Installation under Linux

63 3.8 Installing the Operations Manager software In the case of an upgrade installation, user-specific changes to the PostgreSQL configuration files postgresql.conf and pg_hba.conf, pg_ident.conf are not taken over, therefore you must make these changes again. The log file of the upgrade process (upgrade.log) is stored in the directory /var/log/fujitsu/serverviewsuite/serverview. How to perform an update installation when using a remote ServerView database is described in "Update installation" on page 84. Script-based upgrade The upgrade installation is performed with the install.sh script. Proceed as follows: 1. Place the ServerView Suite DVD 2 in the drive. 2. Open a terminal and switch to the mounted directory. 3. Switch to the directory SVSSoftware Software ServerView Linux ServerView S2. 4. Start the installation with the following command:./install.sh <option> If you do not specify an option, the complete Operations Manager software will be updated by default. For <option> you can specify, see "Installation" on page 53. In a non-silent upgrade of a ServerView Operations Manager installation using the OpenDJ directory service, you will be asked whether you want to change the password for the administrative user svuser in OpenDJ. If you agree, you will be asked for the old password for svuser. If you specify this correctly you will be asked for the new password. When upgrading from a version previous to SVOM 6.10 you are always requested to specify the password for svuser. During a non-silent upgrade from ServerView Operations Manager versions prior to V6.10, you will have to provide a password for the OpenDJ user svuser. You will also need to specify the password used in the prior version, default was admin. The password for svuser must not be an empty string. Installation under Linux 63

64 3 Installing ServerView Operations Manager Installed Operations Manager packages The installable packages are located on the ServerView Suite DVD 2 in the directory SVSSoftware/RPMS. The installation installs the following rpm packages: ServerViewBase Configuration files for Operations Manager and the Operations Managerspecific Web server instance. ServerViewPostgresql Package for PostgreSQL database server. Operations Manager version 4.71 and later come with the separate PostgreSQL database server. The ServerViewPostgresql package sets up a user called postgpls for PostgreSQL. The database processes run under this user, who is also the owner of the files from ServerViewPostgresql. This user needs super user access. The PostgreSQL database server set up via ServerViewPostgresql uses TCP/IP port ServerViewDB Package for the ServerView database. ServerViewJBoss Packages for the JBoss Web server. ServerViewJBossCommon Package with utilities for the directory services OpenDJ and Active Directory. ServerViewCommon Libraries and files used by Operations Manager and Event Manager. ServerView_S2 Package for installation of Operations Manager (without Update Manager and Event Manager). ServerViewUpdateManager Package for installation of Update Managers. ServerViewEventManager Package for installation of Event Manager. 64 Installation under Linux

65 3.8 Installing the Operations Manager software ServerViewOperationsManager Virtual package containing the dependencies to the other packages. ServerViewConnectorService Package for remote connection to Operations Manager. The packages ServerViewBase, ServerViewPostgresql, ServerViewDB, ServerViewJBoss, ServerViewJBossCommon and ServerViewCommon are always installed. (If only a remote DB is installed, only the packages ServerViewBase, ServerViewPostgresql and ServerViewDB are installed.) By default, the complete Operations Manager software including the database management system is installed. The database management system is installed in the directory /opt/fujitsu/serverviewsuite/postgresql by default. Installation under Linux 65

66 3 Installing ServerView Operations Manager 3.9 Available services for operating Operations Manager The following services are available for operating Operations Manager: /etc/init.d/sv_watchdogd /etc/init.d/sv_jboss /etc/init.d/sv_downloadd /etc/init.d/sv_updated /etc/init.d/sv_inventoryd /etc/init.d/sv_fwdserver /etc/init.d/sv_exportd /etc/init.d/sv_archivd /etc/init.d/sv_serverlistservice /etc/init.d/sv_bmcservice /etc/init.d/sv_vme /etc/init.d/sv_dbserver /etc/init.d/sv_postgresql /etc/init.d/srvmagt_scs Stopping/starting/restarting all services You can stop, start and restart all services with the following command: /usr/bin/sv_services stop start restart [service] service The following services are only stopped if additional options are specified: -withpostgres Service /etc/init.d/sv_postgresql -withjboss Service /etc/init.d/sv_jboss -withscs Service /etc/init.d/srvmagt_scs 66 Installation under Linux

67 3.9 Available services for operating Operations Manager Stopping services individually You stop the ServerView services - in the order listed above - with the following command: <service> stop You can check whether all services have been stopped with the following command: ps ax grep SV Services which are still running can be terminated with the kill command (kill - 9). Child services must also be terminated with this command. Starting services individually <service> start The services must be started in reverse order (see above list). Watchdog for services Each ServerView service, e.g. ServerListService, creates a so called pid file on startup and deletes it on closure. The watchdog checks the existence of the pid file and, if it exists, checks whether the process is running. If not, it restarts the service. All services to be monitored are configured in the file /etc/fujitsu/serverviewsuite/serverview/sv_watchdogdrc. It is possible to list services that may not exist when the watchdog starts up. Service are monitored as soon as they come into existence. The exact location of the pid file is listed for each service in this configuration file. The watchdog itself is a normal service with init script /etc/init/sv_watchdogd. It is the last of all ServerView services to start. The watchdog is integrated in the overall service handling script, /usr/bin/sv_ services. So the watchdog is implicitly started / stopped together with all other services. If the product Virtual-IO Manager is installed, then the script /usr/bin/sv_services also handles the services of VIOM. Installation under Linux 67

68 3 Installing ServerView Operations Manager 3.10 Uninstalling the Operations Manager software If you want to uninstall a web component and then install an older version of this component, you must delete all caches beforehand. How to uninstall when using a remote ServerView database is described in "Uninstallation" on page 84. The database backup files are located in the directory /var/fujitsu/serverviewsuite/serverviewdb. For reasons of space, you should delete any files that are no longer required. Before you uninstall Operations Manager, it is recommended that you remove all report configurations of the Performance Manager according to the description in the "Performance Manager" user guide. If you do not remove them, there will be discrepancies between Operations Manager and agents after Operations Manager is installed again. Please check before removal whether there are any other Operations Manager installations which use these reports too. If Virtual-IO Manager, Deployment Manager or Installation Manager are still installed on the system, you will be asked to uninstall them first. Do not stop the uninstallation while it is running. Please wait until the process is completed. For Red Hat 7.0, compat-libstdc++-33 library is installed automatically during ServerView Operations Manager installation. But compat-libstdc++-33 library will not be uninstalled, when ServerView Operations Manager is uninstalled. You uninstall the software with the UninstallServerView.sh script, located in the directory /opt/fujitsu/serverviewsuite/serverview/scripts and /usr/bin. By default, the complete Operations Manager software including the database management system is uninstalled. Syntax UninstallServerView.sh <option> 68 Installation under Linux

69 3.11 Changing configuration parameters For <option> you can specify: -OM Only Operations Manager is uninstalled. An installed Update Manager is also uninstalled. -UM Only Update Manager is uninstalled. -EM Only Event Manager is uninstalled. -v --verbose --debug Writes additional information to the log file. -f --force Forces an uninstallation. If this option is set, the uninstallation will continue even if one of the individual packages fails to uninstall. -q --quiet No console outputs are generated. If the file /etc/cron.d/pg_crontabentry exists even after finishing the uninstallation, remove this file Changing configuration parameters If either the fully qualified hostname or the IP address of the central management station changes, you can reconfigure ServerView Operations Manager by calling the ChangeComputerDetails.sh command. If you want to change the directory service used by ServerView Operations Manager, you can do this by calling ChangeComputerDetails.sh. The ChangeComputerDetails.sh command is located in the directory /opt/fujitsu/serverviewsuite/svom/serverview/tools. If you change the hostname, you must remove the managed server from the server list and add it again. Otherwise, the old hostname will be retained in the server list. Installation under Linux 69

70 3 Installing ServerView Operations Manager If you want to change parameters other than the fully qualified hostname, IP address or parameters for the active directory service, proceed as follows. The ServerView Operations Manager configuration parameters are stored in the file /etc/fujitsu/serverviewsuite/serverview/global.conf. In the rare event that you might need to change them, you should do so with caution. You can either change them during the installation or after it (to change the SNMP community, change the COM_SNMP_COMMUNITY parameter.). You should only change the parameters COM_SNMP_COMMUNITY and COM_ IPCHANGECHECK in this way: Changing during the installation Proceed as follows: 1. Install the ServerViewBase package: sh install.sh --base 2. Edit the file /etc/fujitsu/serverviewsuite/serverview/global.conf, e.g. with vi. 3. Install all the other packages: sh install.sh For a partial installation, add the relevant option -OM (Operations Manager), -UM (Update Manager) or -EM (Event Manager). Changing after the installation Proceed as follows: 1. Stop all ServerView services: /usr/bin/sv_services stop 2. Edit the /etc/fujitsu/serverviewsuite/serverview/global.conf file, e.g. with vi. 3. Execute the reconfiguration: /usr/bin/configure-serverview.sh 4. Start all ServerView services: /usr/bin/sv_services start If you have changed the SNMP community you must execute the following script: /opt/fujitsu/serverviewsuite/serverview/ scripts/configure/20-svdbclient.sh 70 Installation under Linux

71 3.12 Collecting diagnosis data If you have changed the COM_IPAddress or COM_IPCHANGECHECK parameters, you must also execute the following: PACKAGE=ServerViewCommon; /usr/bin/configure-serverview.sh Both instructions must be entered in the same line Collecting diagnosis data After installing Operations Manager on the central management station, the script cmscollect.sh is available in the directory /opt/fujitsu/serverviewsuite/svom/serverview/tools. The script allows you to collect various diagnosis data (e.g. information about JBoss, ServerView Services, log files). For diagnostics purposes you can send this file to your Fujitsu Technology Solutions Customer Service Desk. To collect the data, proceed as follows: 1. Switch to the directory /opt/fujitsu/serverviewsuite/svom/serverview/tools. 2. To start the collection execute the following command: sh cmscollect.sh The result of the collection is stored in the file cmscollect.tar.gz in the directory /var/log/fujitsu/serverviewsuite Troubleshooting Removing faulty/stuck packages Very rarely it may occur that an Operations Manager package cannot be uninstalled. Because of the dependencies of the various packages, they must be uninstalled in the following order: 1. ServerViewOperationsManager 2. ServerViewUpdateManager 3. ServerView_S2 Installation under Linux 71

72 3 Installing ServerView Operations Manager 4. ServerViewEventManager 5. ServerViewCommon 6. ServerViewJBossCommon 7. ServerViewJBoss 8. ServerViewDB 9. ServerViewPostgresql 10. ServerViewBase 11. ServerViewConnectorService (But this package could still be required by a ServerView agent that might be installed.) You can use the following command to check whether any other packages are dependent on the one you wish to uninstall: rpm -q --whatrequires <package> If there are dependent packages, uninstall these first with the following command: rpm -e <package> Or, if you get error messages, uninstall the packages with the following command: rpm -e --noscripts <package> Purging the system Very rarely an installation / uninstallation process might not run to completion. To purge the system, first uninstall all dependent packages and then the packages themselves (see "Removing faulty/stuck packages" on page 71). You must then delete the following directories: /etc/fujitsu/serverviewsuite/postgresql /etc/fujitsu/serverviewsuite/serverview /opt/fujitsu/serverviewsuite/postgresql /opt/fujitsu/serverviewsuite/serverview /opt/fujitsu/serverviewsuite/serverviewdb /opt/fujitsu/serverviewsuite/updatemanager /opt/fujitsu/serverviewsuite/jboss 72 Installation under Linux

73 3.13 Troubleshooting /opt/fujitsu/serverviewsuite/opends /opt/fujitsu/serverviewsuite/svcommon /opt/fujitsu/serverviewsuite/svom /opt/fujitsu/serverviewsuite/web This might also delete archives and regular archive and export tasks. /usr/bin/uninstallserverview.sh /usr/bin/setserverviewenviron* /usr/bin/configure-serverview.sh The following directories contain log files of the installation and uninstallation. You can keep these files: /var/log/fujitsu/serverviewsuite/serverview /var/log/fujitsu/serverviewsuite/serverviewdb /var/log/fujitsu/serverviewsuite/jboss /var/log/fujitsu/serverviewsuite/vme /var/fujitsu/serverviewsuite/serverviewdb (Please decide whether you need the backup files in this directory) PostgreSQL server does not start Check whether the initlog files and the server log file serverlog in the directory /opt/fujitsu/serverviewsuite/postgresql/pgsql contain error messages. Check that directory /tmp has read, write and execution rights for all. Ensure that no old PostgreSQL server is running, by executing the following command: ps ax grep -i postgres If an old PostgreSQL process is running, try to end it. If nothing helps, kill it. Then remove /tmp/.s.pgsql.9212.* files. If no old PostgreSQL process is running, check that there are no /tmp/.s.pgsql.9212.* files. If there are, remove them. Installation under Linux 73

74 3 Installing ServerView Operations Manager Installation fails If the installation script aborts with the message "which: no java...", enter your Java path in the path variable. Example If java is in the directory /usr/java/jre /bin, execute export PATH=$PATH:/usr/java/jre /bin followed by the installation script. If the installation of ServerViewDB fails, check whether PostgreSQL is running. If not, perform the steps as described in "PostgreSQL server does not start" on page ServerView Operations Manager cannot connect to the database server If ServerView Operations Manager cannot connect to the database server, you will find relevant messages in the following files: /opt/fujitsu/serverviewsuite/web/cgi-bin/serverview/ common/svdbserver.log and/or /opt/fujitsu/serverviewsuite/web/cgi-bin/ ServerView/common/SVDBTrace*.log As well as in the log files of Postgresql located in: /opt/fujitsu/serverviewsuite/postgresql/pgsql/data/pg_log Check whether the /etc/hosts file includes the entry for localhost with the IP address System with active PAM configuration Installation fails or database backups are not performed. System update Following an update of the operating system on which PAM is activated, ServerView Operations Manager might no longer work. Check your PAM configuration, in particular to make sure that the users postgpls and root can be called with superuser access. 74 Installation under Linux

75 3.13 Troubleshooting JBoss does not work correctly Very occasionally you may find that JBoss starts up and the process is running but it is somehow not working properly. For example, the graphical user interface might not start up properly. One possible reason is that it could not find all the TCP ports that it needs. Normally there will be an indication in the log file /var/log/fujitsu/serverviewsuite/jboss/jboss.log, e.g. a Java exception and possibly a URL including a port, e.g. Bad URL path:rh/jndi/rmi://samnaun_rh:1401/jmxconnector. binding failed, TCP connection already in use. Sometimes it helps to restart JBoss, with /etc/init.d/sv_jboss restart. But in rare situations you may need to reboot the system. If you wish to analyze the situation further, you may enter the following: /opt/fujitsu/serverviewsuite/jboss/bin/portcheck -v -f /opt/fujitsu/serverviewsuite/jboss/bin/jbports >/tmp/ports_v 2>&1 for port in $(cat /tmp/ports_v grep read cut -d" " -f3); do netstat -antp grep $port; done This would normally list all the processes that use ports required by SVOM. If a port is only bound but not actually opened for listening, it will not be displayed by netstat, but it still cannot be opened. Further information on problems with JBoss can be found in the log files of JBoss located in: /opt/fujitsu/serverviewsuite/jboss/standalone/log Installation under Linux 75

76 76 Installation under Linux

77 4.1 Configuration files 4 ServerView database The ServerView database has been replaced by an SQL database. Under Linux the database management system PostgreSQL is used. Operations Manager does not use the PostgreSQL server from the distribution, but comes with its own. This is installed via the rpm package ServerViewPostgresql. After installation, a description of PostgreSQL can be found in the following directories: /opt/fujitsu/serverviewsuite/postgresql/pgsql/share/doc /opt/fujitsu/serverviewsuite/postgresql/pgsql/share/man For more information on PostgreSQL, visit Configuration files Directory /opt/fujitsu/serverviewsuite/postgresql/pgsql/data The directory /opt/fujitsu/serverviewsuite/postgresql/pgsql/data contains the following configuration files for PostgreSQL: postgresql.conf This file contains default values for individual options, including the maximum number of users, who is allowed to access the ServerView database, the port number used (default port: 9212) and installation paths. pg_hba.conf This file defines access authorization to databases. It specifies which system is allowed to log on, the access authorizations for each system, and which system can access which database. In an upgrade installation, the most recent status of each of these files is saved in the directory /var/fujitsu/serverviewsuite/serverviewdb. The complete history of these files is stored in the directory /etc/fujitsu/serverviewsuite/postgresql. Directory /etc/fujitsu/serverviewsuite/serverview The directory /etc/fujitsu/serverviewsuite/serverview contains the configuration file global.conf, in which global settings are defined. This file is Installation under Linux 77

78 4 ServerView database created during installation of the ServerViewBase package. 4.2 Connection to the ServerView database is interrupted If the connection to the ServerView database is interrupted, e.g. in the case of LAN problems, the following occurs: The ServerView Services service and, if present, the ServerView Download Service service are stopped. A message (see figure below) is written to the file /var/log/messages. If Operations Manager is running, the following screen is displayed: Figure 1: Error message Once the connection to the ServerView database has been restored, the services ServerView Services and ServerView Download Service must be restarted. Start the services with following command: /usr/bin/sv_services start -withpostgres 4.3 Sample configuration for pgadmin3 For the database administration, pgadmin3 can be used under Windows. To be able to access the data of the ServerView database from a Windows system, you must make various settings in the configuration files. postgresql.conf In the configuration file, the entry under listen_addresses specifies whether only the local server or also remote servers can access the PostgreSQL database 78 Installation under Linux

79 4.4 Administering the ServerView database server. This entry is preset to localhost. For the use of Operations Manager, also from a remote system, this is sufficient. For access from a remote system to the data of the ServerView database with pgadmin3, listen_addresses= * must be specified. pg_hba.conf Under the line IP1, you enter the system from which the ServerView database can be accessed: # IP1: allow all users on the client <Client IP address> host all postgpls <IP address/network> <Access method> <IP address/network> Specify the IP address and the netmask in CIDR notation. For example, /32 means one system, while /24 means that all systems in the network ( ) can access the database. <Access method> Specify the authentication: trust 4.4 Administering the ServerView database For administering the ServerView database under Linux, the following tools are available: Tool psql The CLI is part of the supplied database management system PostgreSQL. The ServerView database is set up under the database user svuser. Call up the tool as follows: /opt/fujitsu/serverviewsuite/postgresql/ pgsql/bin/psql -p U svuser -d ServerViewDB pgadmin3 Graphical tool for administration of PostgreSQL. This tool is available via For a description of pgadmin3, visit Installation under Linux 79

80 4 ServerView database For PostgreSQL administration you can use pgadmin3 (only for Windows), which you can download from Please use a version 1.8.x. If you want to use this version to manage the ServerView database, you must make appropriate access settings in the database management system PostgreSQL after installation, see "Sample configuration for pgadmin3" on page 78. In the connection dialog, enter postgpls or svuser. The corresponding entries must be adjusted in the configuration examples. phppgadmin Web-based graphical tool for administration of PostgreSQL. This tool is available via Backing up the ServerView database By default, the ServerView database is backed up once a day and once a week. These settings for regular backup are contained in the crontab table /etc/cron.d/pg_crontabentry and you can adjust them with the crontab command. Independent of your settings, only one backup per weekday is created. The pg_dump command is used for backup. The generated backup file is then compressed with the program gzip. You should additionally save the ServerView database to external media so that you have a backup available, for example in the event of a disk error. This should also be done at regular intervals. Use the archiving programs such as tar, cpio or backup for this. The ServerView database backups are kept in the directory /var/fujitsu/serverviewsuite/serverviewdb/backup. 4.6 Restoring the ServerView database In the event of an error, you can restore the ServerView database from the backups. The errored database must not be deleted before the restoration. The backup files are located in the directory: 80 Installation under Linux

81 4.7 Exporting/Importing the ServerView database /var/fujitsu/serverviewsuite/serverviewdb/backup To restore a ServerView database from a backup, proceed as follows: 1. Stop the ServerView services: /usr/bin/sv_services stop 2. Deactivate the regular backup: mv /etc/cron.d/pg_crontabentry /tmp 3. Import the ServerView database: gzip -cd /var/fujitsu/serverviewsuite/serverviewdb/ backup/serverviewdb_<type>.gz /opt/fujitsu/serverviewsuite/postgresql/ pgsql/bin/psql -p d ServerViewDB -U svuser For <type>, enter the backup type (weekly or daily): Week_<week number> <week number> is the number of the week in which the weekly backup took place. Monday,..., Sunday Weekday of the daily backup. 4. Activate the regular backup: mv /tmp/pg_crontabentry /etc/cron.d 5. Start the ServerView services: /usr/bin/sv_services start 4.7 Exporting/Importing the ServerView database You can export the ServerView database, for example to send it to the Service Center for diagnostics. Use the pg_dump command. The backup file contains the user data, scripts and SQL statements of the database. To export the database, use the pg_dump command as follows: /opt/fujitsu/serverviewsuite/postgresql/pgsql/bin/pg_ dump -p U svuser ServerViewDB --clean gzip > <directory>/serverviewdb_<name>.gz Installation under Linux 81

82 4 ServerView database <directory> Directory of the database backup. <name> Optional specification of your own identifier for the backup. To import the ServerView database during operation, proceed as follows: 1. Stop the ServerView services: /usr/bin/sv_services stop 2. Import the ServerView database: gzip -cd /var/fujitsu/serverviewsuite/serverviewdb /backup/serverviewdb_<type>.gz /opt/fujitsu/serverviewsuite/postgresql/pgsql/bin/p sql -p d ServerViewDB -U svuser 3. Start the ServerView services: /usr/bin/sv_services start 4.8 ServerView database on a remote database server As of ServerView Operations Manager version 4.80 you can install the ServerView database on a remote database server. The following sections describe the steps necessary for installation, update installation and uninstallation on the remote database server and on the central management station Installation Installation on the remote database server Proceed as follows on the remote database server: 1. Install the packages ServerViewBase, ServerViewPostgresql, and ServerViewDB with the following command:./install.sh --remotedbserver or./install.sh --RDBS 82 Installation under Linux

83 4.8 ServerView database on a remote database server The packages are installed.the ServerView database itself is not generated during installation of the ServerViewDB package, but only when the installation is performed on the central management station. Installation on the central management station Proceed as follows on the central management station: 1. Install the ServerViewBase package with the following command:./install.sh --base 2. When you install the ServerViewBase package, the configuration file global.conf is also installed in the directory /etc/fujitsu/serverviewsuite/serverview. Open this file and enter the IP address of the remote database server at the following entry: export COM_DB_SERVER=" " e.g.: export COM_DB_SERVER=" " 3. Install further required packages with the following command:./install.sh Unless you specify an option, all packages will be installed, see "Installed Operations Manager packages" on page 64. If you only want to install individual packages, you must specify the relevant option, see "Installation" on page 53. During installation of the ServerViewDB package, the ServerView database is generated on the remote database server. Installation under Linux 83

84 4 ServerView database Update installation Before you begin an update installation you must stop all ServerView services on the central management station. Do this by entering the following command: /usr/bin/sv_services stop Proceed as follows: 1. For an update installation of the ServerView database on the remote database server, enter the following command:./install.sh --remotedbserver or./install.sh --RDBS 2. Start the service with following command (on the central management station): /usr/bin/sv_services start For an update installation on the central management station, enter the following command:./install.sh The entire Operations Manager software is updated. For an update installation of individual components, you must specify the relevant option, see "Installation" on page Uninstallation For uninstallation you must first uninstall the Operations Manager software on the central management station and then the ServerView database on the remote database server. Uninstallation is described in "Uninstalling the Operations Manager software" on page Installation under Linux

85 4.9 Error diagnostic ServerView database backups By default the ServerView database on the remote database server is backed up daily. The ServerView database is also backed up once a day on the central management station. The backups of the ServerView database are kept in the directory /var/fujitsu/serverviewsuite/serverviewdb/backup Switching the database server Switching from local database server to remote database server Install the remote database server as described in the previous sections. On the central management station, execute the following command: /opt/fujitsu/serverviewsuite/serverview/ scripts/change-db.sh --remote <IP address of the remote server> Switching from remote database server to local database server On the central management station, execute the following command: /opt/fujitsu/serverviewsuite/serverview/ scripts/change-db.sh --local When you have switched the database server, you can uninstall the Operations Manager software on the former remote database server. 4.9 Error diagnostic unixodbc Manager The Operations Manager software and the database management system PostgreSQL can only be installed if the unixodbc Manager is installed (see also "Requirements" on page 31). Installation under Linux 85

86 4 ServerView database Error during installation/uninstallation Installation The installation process is logged in log files. To receive debugging information, specify the option -v for install.sh. If an error occurs during installation, the error will be displayed and all actions so far will be undone. The log files of the database management system PostgreSQL are stored under: /opt/fujitsu/serverviewsuite/postgresql /pgsql/initlog /opt/fujitsu/serverviewsuite/postgresql /pgsql/data/serverlog /var/log/fujitsu/serverviewsuite/serverview/install.log /var/log/fujitsu/serverviewsuite/serverview/upgrade.log /var/log/fujitsu/serverviewsuite/serverviewdb/serverview_ Debug/ServerViewError.log /var/log/fujitsu/serverviewsuite/jboss/jboss.log If you can resolve the error using the log files /opt/fujitsu/serverviewsuite/postgresql/pgsql/data/pg_log/*.log, you can then restart the installation. If you have problems starting JBoss or accessing the Web server after installation, you may be able to diagnose them with the help of the file /var/log/fujitsu/serverviewsuite/jboss/jboss.log. If you cannot resolve the error, send the above-listed log files to the Service Center for diagnostics. You can delete old files from the directory /opt/fujitsu/serverviewsuite/postgresql/pgsql/data/pg_log if you do not need them for problem diagnostics. Uninstallation The uninstallation process is logged in the file /var/log/fujitsu/serverviewsuite/serverview/uninstall.log. 86 Installation under Linux

87 4.9 Error diagnostic Uninstalling the ServerView database If the ServerView database is blocked by another program, it is not possible to uninstall the ServerView database and the database management program. To solve the problem, stop all external programs that have access to PostgreSQL, e.g. programs for PostgreSQL administration System is slowing down If you notice that your system is slowing down, you can rebuild the indexes of the ServerView database. This is done using the REINDEX command, which is described in the PostgreSQL documentation which can be found in the following directories: /opt/fujitsu/serverviewsuite/postgresql/pgsql/share/doc /opt/fujitsu/serverviewsuite/postgresql/pgsql/share/man Checking the status of PostgreSQL In some cases it may be necessary to check the status of the database management system. Use the following command: /etc/init.d/sv_postgresql status Starting and stopping PostgreSQL In some cases it may be necessary to stop or start the database management system manually or to restart a database management system that is already running. Starting PostgreSQL /etc/init.d/sv_postgresql start Stopping PostgreSQL /etc/init.d/sv_postgresql stop Installation under Linux 87

88 4 ServerView database Startup problems under SLES 11 can be resolved as follows: 1. Start YaST via the start menu. 2. Select System and then click System Services (Runlevel). The System Services (Runlevel): Services window opens. 3. Select Expert Mode. 4. Select the sv_postgresql service from the list. 5. Under Service will be installed in following run levels: activate levels 3 and Click Set/Reset and then select Enable the service. 7. Save your settings and then click Finish. In the case of systems with Red Hat, please use the product ServiceConfiguration available under Menu System Settings Server Settings Services. Restarting a running PostgreSQL /etc/init.d/sv_postgresql restart Restarting Operations Manager You can restart Operations Manager completely on the Linux system. Proceed as follows: /usr/bin/sv_services restart -withpostgres -withjboss -withscs The following services are started via the additional options: Service /etc/init.d/sv_postgresql: -withpostgres Service /etc/init.d/sv_jboss: -withjboss Service /etc/init.d/srvmagt_scs: -withscs 88 Installation under Linux

89 4.10 Changing the load distribution 4.10 Changing the load distribution ServerView allows you to influence the system load it incurs or the number of concurrent jobs. The following services start jobs whose concurrent number may be defined in an ini file. ArchiveService ExportService InventoryService <scripts>/serverview/snmparchive/svarchiveserver.ini <scripts>/serverview/snmpexport/exportserver.ini <scripts>/serverview/snmpinventory/ SVInventoryServer.ini <scripts>: directory /opt/fujitsu/serverviewsuite/web/cgi-bin Each of these configuration files holds a variable ConcurrentJobsAllowed in the section GLOBALS. The number given there states how many concurrent jobs are started. Example Archiving is activated for all servers and 100 manageable servers are present in the server list. If ConcurrentJobsAllowed is set to 30 in SVArchiveServer.ini, there will always be at most 30 servers being archived at the same time. Once archiving is finished for one server of the 30 started jobs, then archiving for another server is started. This is repeated until all 100 servers are archived. The current default values for ConcurrentJobsAllowed are: SVArchiveServer.ini 30 DownloadServer.ini 30 ExportServer.ini 100 SVInventoryServer.ini 10 If you upgrade the Operations Manager software, the value for ConcurrentJobsAllowed parameter will be reset to the default value. Installation under Linux 89

90 4 ServerView database 1. Before changing the number of ConcurrentJobsAllowed: Before changing the number of ConcurrentJobsAllowed, please ensure that no jobs of the respective service are running. For ArchiveService, DownloadService and ExportService this can easily be verified via the respective GUI in the tab settings. If there are blue arrows displayed for the status of a task then a job is running for the server. For InventoryService please check in the process list whether a process called SVSnmpInventory is running. In Linux you can view the process list via the command ps. 2. Effect of reducing the number of concurrent jobs: Reducing the number of concurrent jobs has two effects: On the one hand it reduces the system load; on the other it increases the time required by a job to process a group of servers. 90 Installation under Linux

91 5 Fujitsu Technology Solutions Software License Agreement for End User 1. Subject of this Agreement 1.1 For the purposes of this agreement Software shall mean the software with the object code, the version and the specification indicated in the software product data sheet of Fujitsu Technology Solutions. The Software consists of machine-readable instructions and/or printed documentation and related licensed materials. 1.2 Please read this agreement carefully before you use the Software. If you do not agree with the license terms in this agreement, you are not permitted to use the Software and must immediately return all copies of the Software and all accompanying items to the Licensor/Sublicensor (either Fujitsu Technology Solutions or the reseller who supplied you with the Software) with proof of purchase for a full refund. 1.3 Any use of the Software requires the proper payment of the applicable license fees. By using the Software you agree to be bound by the terms of this agreement. 1.4 Fujitsu Technology Solutions reserves the right to implement at any time in the future an additional software license key and/or license certificates as countermeasures against software piracy. 1.5 Software components from third-party software suppliers which are part of the scope of the delivery are subject to separate license agreements that are included with the Software or that are transmitted by Fujitsu Technology Solutions upon request. 2. End User License 2.1 Fujitsu Technology Solutions grants you a non-exclusive and nontransferable license to use the Software on the number of workstations for which you have purchased licenses. Unless you purchase additional licenses, you are not permitted to operate the Software on more than the maximum number of licensed workstations or on hardware that exceeds the specified type. You are permitted to make a backup copy of the Software for archiving purposes, provided you properly mark the copy or partial copy of the Software with the copyright notice and any other ownership information. Installation under Linux 91

92 5 Fujitsu Technology Solutions Software License Agreement for End User 2.2 You are not permitted to copy, modify or distribute the Software. Furthermore, you are not permitted to re-compile, re-engineer, convert, revise, compile or modify the Software. You may not sub-license, without selling the related hardware, assign, rent, lease or transfer the Software except as expressly permitted by this agreement or due to mandatory legal regulations. 2.3 If you acquired the Software as a program upgrade, your license for the use of the old software version ends automatically with the installation of the upgrade version of the Software. If parts of the old software version are not replaced by the upgrade version, the license for the old version continues to be effective until the remnants of the old software version are also replaced or deactivated or shut down in any other way. 2.4 Unless specified otherwise in the respective software data sheet of Fujitsu Technology Solutions, the license for a software version or release does not give you any rights to new releases (updates), new versions (upgrades) or technical support services for the Software. Supplemental software support contracts and maintenance services, including or excluding new releases and new versions and additional technical support services, can be purchased separately either from Fujitsu Technology Solutions directly or from authorized software resellers. 3. Downloading For Software supplied by Fujitsu Technology Solutions over a network or a similar distribution path, the following additional conditions shall apply: All products supplied for downloading by Fujitsu Technology Solutions are selected, made available and if supplied by third parties provided without modification. However, you are fully responsible for ensuring the most current version and usability of downloadable material for your own purposes and on your own system. You download Software at your own risk. Fujitsu Technology Solutions will not accept any liability, particularly not for transmission errors or problems that arise during the downloading process (line failures, connection interruptions, server failures, data corruption, etc.). The website of Fujitsu Technology Solutions is operated and administered only for those countries in which Fujitsu Technology Solutions has one or more offices. Fujitsu Technology Solutions accepts no responsibility that Software and/or documentation can or may be downloaded from a Fujitsu Technology Solutions website also in locations other than the countries mentioned above. If you access a website of Fujitsu Technology Solutions from abroad, you are fully responsible for complying with any local regulations. Fujitsu Technology 92 Installation under Linux

93 Solutions expressly prohibits the downloading of Software and/or documentation from a Fujitsu Technology Solutions website in countries where such downloading is considered illegal. 4. Copyright All rights and licenses, unless they are expressly granted to you in this license terms, as well as all property and usage rights related to the Software (including parts of the Software) remain fully with Fujitsu Technology Solutions and/or its third-party licensors. The license terms do not authorize you to use the brands, logos or trademarks of Fujitsu Technology Solutions or its third-party licensors, nor are you permitted to use any other brands which are deceptively similar to the brands, logos or trademarks of Fujitsu Technology Solutions. Each and any use of brands, logos or trademarks with respect to the Software or Fujitsu Technology Solutions requires the express consent of Fujitsu Technology Solutions. 5. Licensor s warranty and liability disclaimer, if Software is sold and delivered by Reseller If you acquire the Software directly from an authorized reseller (called Reseller ), the right to install and use the Software may be subject to additional software license conditions agreed upon between you as the licensee and the respective reseller. In all cases of an authorized software resale, the software is sublicensed and made available to the licensee directly by the Reseller. In such cases, Fujitsu Technology Solutions is not a contractual party of the software license agreement between you, as licensee and the Reseller, as far as the procurement of the software licenses are concerned. Legal claims in connection with the software licensing can therefore be asserted only on the basis of the agreements with the Reseller. Under no circumstances, however, will the respective scope of the license for the licensee exceed the scope of the license agreements as specified in sections 1, 2, 3 and 4 of this agreement. Subject to mandatory legal regulations, particularly those governing liability and/or warranties, which cannot be excluded in connection with end user license agreement regulations and with reference to the licensee s claims against the Reseller, Fujitsu Technology Solutions disclaims all warranties for the Software in this agreement. For the same reason, Fujitsu Technology Solutions disclaims any and all liability/claims for any violations of third parties rights as well as any implied Installation under Linux 93

94 5 Fujitsu Technology Solutions Software License Agreement for End User warranties for the software s marketability and its suitability for a particular purpose. This disclaimer of liability does not apply in cases of willful or malicious behavior by Fujitsu Technology Solutions. In this End User License Agreement, Fujitsu Technology Solutions grants no warranties of any kind, either express or implied. 6. Disclaimer of liability with respect to shareware, freeware and/or open source software components 6.1 The Software may contain freeware or shareware which Fujitsu Technology Solutions received from a third party. Fujitsu Technology Solutions paid no license fees for the use of this freeware or shareware. Accordingly, the licensee is not charged any license fees for the use of the freeware or shareware. You recognize and accept that Fujitsu Technology Solutions therefore grants no warranties with respect to such freeware or shareware components and does not assume any liability in connection with the ownership, the distribution and/or the use of the respective freeware or shareware. 6.2 The Software may also contain open source software components that were developed according to the open source model and which are distributed exclusively on the basis of the GPL (General Public License: terms and conditions or other standard open source standard license terms and conditions applicable to the respective open source components at the time of their dissemination. You recognize and accept that the licensing of such open source software components is governed exclusively by the above-mentioned GPL terms or by the conditions which are otherwise included with the open source software components. Fujitsu Technology Solutions receives neither license fees nor any other compensation for the delivered open source software components. As far as Fujitsu Technology Solutions or a third party receives any compensation in connection with open source software components, it is received exclusively for additional delivery items and/or services. Because of the special nature of the development and distribution of open source software components, Fujitsu Technology Solutions assumes no express or implied liability for such components and excludes any kind of warranty for such open source software components, particularly in connection with missing specifications, lack of functionality, programming errors or any other malfunctions. 94 Installation under Linux

95 7. General limitations of liability 7.1 Neither Fujitsu Technology Solutions nor its suppliers are liable for any consequential or indirect damages, including damages arising as a result of or in connection with an operational interruption, lost profits or sales, lost data, or costs of capital. Fujitsu Technology Solutions and its suppliers will not be liable for additional ancillary or consequential costs or for any other losses, costs or expenses of any kind which arise as a result of the holding, sale, use or impossibility of use of the Software, independent of whether such claims are asserted due to warranty rights, contracts, tort or any other legal theory. 7.2 The liability of Fujitsu Technology Solutions for direct damage caused as a result of a contract violation and/or other action or lapse on the part of Fujitsu Technology Solutions which have not been excluded or cannot be completely excluded due to mandatory law are limited to no more than 250, Any and all other liabilities for direct damage are excluded. Damage caused by Fujitsu Technology Solutions as a result of slight negligence are excluded to the extent permitted by applicable legal regulations. 7.3 Limitations and exclusions of liability resulting from this agreement do not apply to damage where Fujitsu Technology Solutions carries compulsory liability according to applicable laws and where such liability cannot be limited to a maximum amount (for example, liability for bodily damage; product liability or fraudulently incorrect information). Installation under Linux 95

96 5 Fujitsu Technology Solutions Software License Agreement for End User 8. Export controls Due to its components as well as the nature or purpose of these components, the export of the Software and/or its accompanying documents may be subject to official or regulatory approval. In cases where the Software is intended for export, you are obliged to get all approvals and authorizations required to comply with all relevant export regulations. The Software may not be exported if there is reason to assume that the Software will be used in connection with nuclear, chemical or biological weapons or for missile technology. Furthermore, you may not deliver the Software or have it delivered indirectly to such companies or persons who are listed in the applicable U.S. export regulations (particularly the Table of Denial Orders/U.S. Denied Persons Lists (DPL) or in the E.U. export regulations (particularly the EU Terrorist List) or in the applicable warnings issued by the German export authorities or any other competent authorities in any country. Under no circumstances is Fujitsu Technology Solutions obligated to deliver software, patches, updates or upgrades, to provide software for download or to fulfill any other contractual commitments if this would be a violation of the applicable export regulations of the Federal Republic of Germany, the European Union, the United States of America or of any other countries. If you export or re-export the Software or a copy of it, this may be a violation of applicable export laws and a severe violation of the terms of this agreement. 9. Miscellaneous 9.1 If any term or condition in this agreement or any other contract that is subject to the terms and conditions of this agreement turns out to be invalid or unenforceable (partly or in full), the validity of all other terms and conditions remains unaffected, unless complying with the remaining terms and conditions would represent an unreasonable hardship for either contract party, even with the application of applicable legal regulations to close the legal gap. 9.2 If you/ the licensee do not pay the license fees due and/or if the licensee does not comply with essential terms and conditions of this license agreement, Fujitsu Technology Solutions reserves the right to cancel the license. In case of such cancellation, you must immediately return any and all copies of the software in your possession and confirm the complete return [of the software copies] or the destruction of these copies in writing. 96 Installation under Linux

97 9.3 Neither you nor Fujitsu Technology Solutions is responsible or liable for the respective party s non-compliance with its obligations if the reason for such noncompliance is outside the party s control due to force majeure. 9.4 Any and all modifications and/or amendments to these license terms and conditions are only valid if they are made in writing. 10. Applicable law 10.1 These license terms and conditions are governed by the laws of the Federal Republic of Germany In the event that provisions of clause 10.1 are unenforceable, these license terms and conditions shall be governed by the laws of the country in which you acquire the Software, with the following exceptions: 1) In Australia, the terms and conditions of this license are governed by the laws of the state or sovereign territory in which the business contract is being concluded; 2) in Albania, Armenia, Belarus, Bosnia-Herzegovina, Bulgaria, Croatia, the Czech Republic, Georgia, Hungary, Kazakhstan, Kirgizia, the former Yugoslavian Republic of Macedonia (FYROM), Moldavia, Poland, Romania, Russia, Slovakia, Slovenia, the Ukraine and the Federal Republic of Yugoslavia, the terms and conditions of this license are governed by the laws of the Federal Republic of Germany; 3) in the United Kingdom [Great Britain], all disputes with respect to these license terms and conditions are governed by English law, and English courts have exclusive jurisdiction; 4) in Canada, the terms and conditions of this license are governed by the laws of the Province of Ontario; 5) in the United States of America and in Puerto Rico as well as in the People s Republic of China the terms and conditions of this license are governed by the laws of the U.S. State of New York. Installation under Linux 97

98 98 Installation under Linux