ServerView Agents V9.00 for Linux

Transcription

1 Installation and User Guide - English FUJITSU Software ServerView Suite ServerView Agents V9.00 for Linux (SUSE, Red Hat, and Citrix XenServer) Edition March 2019

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 Documentation creation according to DIN EN ISO 9001:2015 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:2015. cognitas. Gesellschaft für Technik-Dokumentation mbh Copyright and trademarks Copyright FUJITSU LIMITED All rights reserved. Delivery subject to availability; right of technical modifications reserved. All hardware and software names used are trademarks of their respective manufacturers. Apache Tomcat, Tomcat, Apache, the Apache feather, and the Apache Tomcat project logo are trademarks of the Apache Software Foundation.

3 Contents 1 Introduction Architecture Target groups and objectives Technical requirements Last-minute changes/corrections Managed Server What's new ServerView Suite link collection Documentation for the ServerView Suite Typographic conventions 11 2 Preparations on the managed servers Configuring the BIOS and Firmware BIOS settings Configuring servers ServerView security concept Prohibiting specific SET operations Prohibiting All SET operations SET Operations with user authentication Operating system-specific characteristics of the SNMP agents Configuring SNMP services Setting the hardware clock (CMOS clock) Settings required for using the Driver Monitor functionality Driver Monitor functionality on SLES11 and SLES12/SLES Driver monitor functionality on RedHat Settings required when default format of syslog is changed Installing the kernel modules for ServerView Agents Installing kernel modules for ServerView Agents (SUSE Linux) Getting the srvmagt-modules-<version>.iso driver kit image Providing the srvmagt-modules-<version>.iso driver kit image on the managed server 27 ServerView Agents for Linux 3

4 Contents Obtaining the kernel modules from an online repository Installing kernel modules for ServerView Agents (Red Hat Linux) Getting the srvmagt-modules-<version>.iso driver disk image Providing the srvmagt-modules-<version>.iso driver disk image on the managed server Obtaining the kernel modules from an online repository 30 3 Installing ServerView Agents Requirements Script-based installation Installation via ServerView Suite DVD Installation from a directory Installation with the rpm command Possible sources of error ServerView Agents maintenance after the installation The srvmagt script Configuring agents Improved availability of ServerView Agents Uninstalling ServerView Agents Starting and stopping the ServerView Agents Starting and stopping ServerView CIM Provider Additional information Setting an administrative user Computer information change after installation Update installation / kernel update Outputting reports with Performance Manager Temporary file under /tmp directory Source name of syslog Configuring APC UPS 46 ServerView Agents for Linux 4

5 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 the hypervisors VMware ESXi or Hyper-V installed. 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. 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. 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 ServerView Agents for Linux 5

6 1.1 Architecture 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 Architecture The architecture of ServerView Operations Manager is based on a management console, a central management station (CMS) and the managed servers. Figure 1: Architecture of ServerView Operations Manager Management console A management console allows you to manage the servers and display the determined data. All you need is a popular web browser. The following can be used as a browser: Microsoft Windows with any popular web browser SUSE/Red Hat Linux with default web browser released with distribution ServerView Agents for Linux 6

7 1.1 Architecture Central management station (CMS) On the CMS ServerView Operations Manager is installed. The optional components of the ServerView Suite, such as Virtual IO-Manager, are also installed on the CMS and integrated in ServerView Operations Manager. The CMS (and thus ServerView Operations Manager with its components) may also run in Windows-based or Linux-based virtual machines (VM) that use hypervisors such as VMware ESXi, Microsoft Hyper-V, and Red Hat Enterprise Linux KVM. The global user management of the ServerView Suite and of the irmc each centrally stores users for all 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: ApacheDS Microsoft Active Directory During the installation of ServerView Operations Manager you have the option to choose ServerView s internal directory service (ApacheDS) or an existing external directory service (Active directory). For further information about the use of directory services with ServerView, see the "User Management in ServerView" user guide. The data which ServerView creates and uses is stored in an SQL database within an SQL Server. The following SQL Server is part of the ServerView Operations Manager installation: SQL Server 2014 Express under Windows Server PostgreSQL under Linux However, other Microsoft SQL Server databases can be used under Windows. How to install 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, ServerView CIM Providers, or ServerView Agentless Service should be installed, which supply the information to the CMS. 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, and Citrix XenServer. ServerView CIM Providers are available for Windows, Linux, and VMware ESXi. ServerView Agents for Linux 7

8 1.2 Target groups and objectives 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 Installation ServerView ESXi CIM Provider ServerView CIM Providers for Windows, Linux, and VMware ESXi 1.2 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 describes the installation of the ServerView Agents for Linux SUSE, Red Hat, and Citrix XenServer. 1.3 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: On the DVD switch to the directory SVSSoftware Software ServerView Linux Agents. Start the DVD and select ServerView Software Products; Info under ServerView Agents and Providers Managed Server ServerView Agents are available for: SUSE (SLES 11): SP4 SUSE (SLES 12): SP3 and SP4 SUSE (SLES 15): GA Red Hat Enterprise Linux 6.10 Red Hat Enterprise Linux 7.4/7.5/7.6 Oracle Linux OL 6.7/6.9 Oracle Linux OL 7.3/7.4 ServerView Agents for Linux 8

9 1.4 What's new Oracle VM 3.3/3.4 Citrix XenServer 6.5 Citrix XenServer 7.1/7.2/7.3/ What's new This edition of the manual applies to ServerView Agents V9.00 or higher and replaces the online manual "ServerView Agents V9.00 for Linux", edition October The manual features the following changes and enhancements: The documentation has been adapted to the currently supported operating systems. Therefore the section "Technical requirements" on page 8, among others, has been updated. The packages inside the srvmagt-modules-<version>.iso file have been renamed (see section "Installing kernel modules for ServerView Agents (Red Hat Linux)" on page 28) ServerView Operations Manager has a new HTML5 Web graphical user interface. A Java Runtime Environment is no longer necessary. Therefore, the section "Architecture" on page 6 has been updated. The manual has been adapted to the new typographic conventions (see section "Typographic conventions" on page 11). 1.5 ServerView Suite link collection Via the ServerView Suite link collection, Fujitsu provides you with numerous downloads and further information on the ServerView Suite and PRIMERGY servers. Under ServerView Suite, links are offered on the following topics: Forum Service Desk Manuals Product information Security information Software downloads Training ServerView Agents for Linux 9

10 1.5 ServerView Suite link collection Software downloads includes the following downloads: 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 Agent) 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. Under PRIMERGY Server, links are offered on the following topics: Service Desk Manuals Product information Spare parts catalogue Access to the ServerView Suite link collection You can reach the link collection of the ServerView Suite in various ways: Via ServerView Operations Manager. 1. Select Help Links on the title bar. Via the start page of the online documentation for the ServerView Suite on the Fujitsu manual server. You access the start page of the online documentation via the following link: 1. In the selection list on the left, select x86 Servers. 2. On the right, click PRIMERGY ServerView Links under Selected documents. Via the ServerView Suite DVD In the start window of the ServerView Suite DVD 2, select the option ServerView Software Products. 2. On the menu bar select Links. This opens the start page of the ServerView Suite link collection. ServerView Agents for Linux 10

11 1.6 Documentation for the ServerView Suite 1.6 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. ServerView Sitemap For an overview of the documentation to be found under ServerView Suite as well as the filing structure, see the ServerView Suite Sitemap: 1. In the selection list on the left, select x86 Servers and then Software. 2. On the right, select ServerView Suite. 3. Click ServerView Suite Sitemap under Selected documents. 1.7 Typographic conventions The following typographic conventions are used: Convention Explanation Various types of risk, namely health risks, risk of data loss and risk of damage to devices. Additional relevant information and tips. bold monospace monospace monospace semibold blue continuous text purple continuous text <abc> References to names of interface elements. System output and system elements, e.g., file names and paths inside Text blocks. Commands, system output, syntax and statements that are to be entered using the keyboard outside Text blocks. Process example for statements that are to be entered using the keyboard. A link to a related topic. A link to a location you have already visited. Variables which must be replaced with real values. Table 1: Typographic conventions ServerView Agents for Linux 11

12 1.7 Typographic conventions Convention [abc] [Key] Quotation marks Explanation Options that can be specified (syntax). Key on your keyboard. If you need to enter text in uppercase, the Shift key is specified,e.g.,[shift] + [A] for an A. If you need to press two keys at the same time, this is indicated by a plus sign between the two key symbols. For names of chapters and manuals. Table 1: Typographic conventions 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. ServerView Agents for Linux 12

13 2 Preparations on the managed servers Before starting the Operations Manager, the following preparations must be made on the managed server: Only for PRIMERGY: Certain settings must be made in the BIOS on each managed server, see "Configuring the BIOS and Firmware" on page 14. On each server, you must make configuration settings, see "Configuring servers" on page 17. ServerView offers a sophisticated security concept. Before you install the agents, you should study the information regarding the security concept thoroughly and choose the concept that best suits your security requirements. You may need to make appropriate arrangements prior to installing the agent. This is described in "ServerView security concept" on page 18. You must install and configure the SNMP services of the current operating system on each managed server and the management station. If you do not do this, the management station will be unable to monitor the servers. The SNMP services must be activated either before or after installing the agents, depending on the operating system. This is described in "Configuring SNMP services" on page 22. As of version 7.01, ServerView Agents are capable of monitoring a server via SNMPv3. In order to use SNMPv3 in ServerView Agents communication the Net-SNMP master agent is recommended. The Net-SNMP master agent is shipped with most Linux distributions. For detailed information, see the ServerView Suite SNMPv3 documentation. The CMOS clock must be set to local time and not to GMT. Otherwise the automatic Power ON/Power OFF will not start at the configured time. This is described in "Setting the hardware clock (CMOS clock)" on page 24. The settings required for using the Driver Monitor functionality must be configured. See "Settings required for using the Driver Monitor functionality " on page 25. ServerView Agents must be installed on each server to be managed, see "Installing ServerView Agents" on page 31. The installation of ServerView Agents on virtual machines (VMs) is not released. ServerView Update Manager requires the ServerView Update Agent to be installed on the managed servers. The installation is described in the "ServerView Update Management" user guide. ServerView Agents for Linux 13

14 2.1 Configuring the BIOS and Firmware If the ServerView Operations Manager on the central management station is configured to be accessed using a name instead of an IP address, you must ensure that the central management station is accessible from the managed node by this address. This is preferably accomplished by an appropriate entry in DNS. If there is no DNS available, then you must provide an appropriate entry in the hosts file on the managed node. You will find this file in the /etc directory on the Linux system. Additional installations on the managed servers 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. 2.1 Configuring the BIOS and Firmware The following description is only valid for PRIMERGY. Since the various PRIMERGY types work with different BIOS versions, depending on which system board is used, the individual settings and the operation of the BIOS setup are not dealt with in detail here. A detailed description of each BIOS version can be found in the corresponding "BIOS Setup Utility" reference manual or the technical reference manual of the system board. When you start the server, you must set the menu item O/S Boot Timeout in the system BIOS setup to Disabled. If you do not do this, the system will restart during the installation. You may only set the O/S Boot Timeout menu item to Enabled when you restart the system after you have completed all installations (including the ServerView Agents). Please also check that, on installing Linux, the value for the O/S Boot Timeout is set in such a way that a file system check will be performed. If this value is not set correctly, the system will be restarted during the file system check. ServerView Agents for Linux 14

15 2.1 Configuring the BIOS and Firmware BIOS settings The server management firmware monitors the server until the operating system has started. After that, the agents and the Operations Manager program assume the monitoring function. You must change the BIOS settings on every server. Call the BIOS setup by rebooting the computer and pressing [F2] or [DEL] at the appropriate time in the bootup phase. On entering the BIOS setup, select the Server menu. This menu enables you to specify the settings required for server management. If the Server menu is not offered in the BIOS setup, you do not need to activate the server management functions. Note, however, that this also means that you have no explicit control over the individual server management functions. If the Server menu includes a Server Management menu item, select this item and set it to Enabled. This activates the server management functionality. You must select the value Enabled here for all the other settings to take effect. If the Server Management menu item is not available, control over the individual functions is not contingent on a general release. The fields listed below are available in the Server menu. Note that some of the fields listed below may not be available, depending on the hardware. O/S Boot Timeout Specifies whether the system is to be rebooted if the operating system cannot establish a connection with the server management firmware within a predefined time period (after startup). The time interval can also be set via the Operations Manager (see also section "ASR&R" in "ServerView Operations Manager" user guide). You must set the O/S Boot Timeout menu item to Disabled when starting the server. Otherwise, the system will reboot during the installation. Action Determines the action carried out after the boot watchdog expires. ServerView Agents for Linux 15

16 2.1 Configuring the BIOS and Firmware Timeout Value Specifies the time after which a system restart is performed if enabled by means of O/S Boot Timeout. ASR&R Boot Delay Defines the time period for which the server must wait after a shutdown due to an error (e.g. due to overheating) before it is automatically restarted. Boot Retry Counter Defines how often the server tries to restart the operating system before it either remains shut down or before RemoteView is started. Diagnostic System Determines whether or not RemoteView is to be started on reaching the number of system restarts set under Boot Retry Counter. Hardware Watchdog Specifies whether the server is to be rebooted if the server management BIOS cannot reset a hardware counter within a specific time interval. Next Boot uses Determines whether or not RemoteView is started at the next boot. Temperature Monitoring Determines whether or not the system is shut down on exceeding the critical temperature value. Memory Scrubbing Determines whether or not memory is tested and single-bit errors are eliminated. BIOS Runtime Logging Specifies whether processor, memory and PCI errors are to be saved in the error log file. CPU Status Defines whether the processor may be used. Memory Status Enables certain memory modules to be identified as defective. These modules will then no longer be used at the next system start. Console Redirection Defines the settings for operating a terminal on the system. ServerView Agents for Linux 16

17 2.2 Configuring servers RomPilot Defines the settings for RomPilot. RomPilot is part of ServerView Remote Management and Operations Manager. RomPilot provides access from a remote console via LAN to the system start phase (POST) and MS-DOS. Storage Extension Defines the settings for the group configuration and the communication bus (CAN bus). Note that Storage Extension is not available on all servers. 2.2 Configuring servers There are various functions available for configuring servers. Some of these functions are supported for all PRIMERGY servers and others are only available for certain servers, depending on the hardware and software installed in the PRIMERGY server. You can configure the servers in one of the following ways: Locally on the managed server via the Server Configuration Manager. With the Server Configuration Manager you can make settings for the general system behavior of the target system and configure any remote management components (irmc) of the target system. When the ServerView Installation Manager is started from the ServerView Suite DVD 1, you can start the Server Configuration Manager via the Server Configuration Manager button. o o Depending on the PRIMERGY server type of the target system, not all steps may be performed. The sequence of the individual steps and the configuration options for the individual steps may also vary from system to system. For details on the individual server configuration dialog steps, please refer to the online help of the Server Configuration Manager. To access the online help related to a dialog step, proceed as follows: 1. Click in the window area currently displaying this dialog step. 2. Press [F1]. Via the ServerView Configuration Manager, which is integrated in the graphical user interface of Operations Manager. This allows you to configure servers from the remote workstation via a web interface. ServerView Agents for Linux 17

18 2.3 ServerView security concept You start the ServerView Configuration Manager on the Operations Manager start page or via the menu bar by selecting Administration Server Configuration. For further information, see "ServerView Operations Manager" user guide. You can only configure servers on which the ServerView Agents are installed. Depending on the system, some of the configured settings are written to the BIOS. Among other things, you can do the following: Read the most important data of the server, the system board and the integrated management controller. Read and set the Boot and Software Watchdog settings. Read and edit the error counter for the memory modules. For PRIMERGY only: Read and delete the error and event logs of the server. Monitor and calibrate the system fan. Read and set the chassis ID (preset on delivery). Read and set the counters for the system runtimes. Configure the settings for HTTP and Telnet and the setting for the Remote Management Controller for HTTP. Configure the IP and DNS settings for the irmc web interface. Configure the SNMP communities and the trap target for the SNMP interface of the remote management controller. Manage user identification for the remote management controller. Configure the serial interface of the RSB and the remote management controller. Configure Operations Manager UPS management integration. Configure the information shown on the display of the ServerView Local Service Display. 2.3 ServerView security concept The ServerView SNMP agents together with the ServerView Manager provide a complete security concept to prevent unauthorized SNMP SET operations on a server. You can restrict access to SNMP SET operations on the managed server. Here you have the following options: Prohibit specific SET operations. Prohibit all SET operations. ServerView Agents for Linux 18

19 2.3 ServerView security concept Protect SET operations with a user authentication. If you select the user authentication option, the system will run a user authentication routine each time you start a SET operation. If the authentication routine is successful, the system will also check if the user belongs to one of the user groups defined by the administrator. The user authentication only operates with ServerView Manager. It does not work with other SNMP tools. You can also reduce the risk of unauthorized access by changing the default configuration of the SNMP service. For further information, see "Configuring SNMP services" on page Prohibiting specific SET operations Some SET operations cause the system to shutdown or restart. You can permit these special SET operations or forbid them, see "Configuring agents" on page 39 - AgentShut Prohibiting All SET operations You can prohibit all SET operations for ServerView Agents. Enter these specifications during agent installation, see "Configuring agents" on page 39 - AgentPermission. This option only applies to ServerView Agents. SET operations for other SNMP agents are not affected SET Operations with user authentication You can restrict access to SET operations and protect the execution of SET operations with a user authentication. Here you can choose between starting the user authentication routine at the beginning of each session on a managed server or starting the user authentication at the start of each new SET operation. For user authentication, you must make the following settings on the managed server as well as on the management station. Entity Settings managed server Define user and user group Assign user to specific user group State the specified user group during installation of the agent management station Specify the user in the Operations Manager Login tab. ServerView Agents for Linux 19

20 2.3 ServerView security concept Defining user and user group and assigning users You must define user and user group on each managed server, using the methods specific to your operating system. You may choose any name for the user or the user group (including Administrator). You need to decide in advance, whether or not you want to create identical user and group identifications for several servers. Specifying a user group during the installation of the agent During the installation of the agent on the server you need to specify the user group to which the user, permitted to execute SET operations, must belong. Installation and configuration of the ServerView Agents differs according to operating system and version. For more information about installation and configuration in these cases, see the agent descriptions beginning at "Configuring agents" on page 39. Specifying users on the management station On the management station you must specify the user permitted to execute SET operations on the current server. You define the user in the Login tab in the Server Properties window. In this example this would be SVUSER. Figure 2: Defining a user identification for the user authentication If you have assigned a password to a user, for reasons of security, we recommend that you enter the password here as well (Set Password). The option Always Ask for Password allows you to specify whether user name and password are required after each change made to the settings, or only after the first alteration made after starting the Operations Manager. You can achieve a higher degree of security, if you activate Always Ask for Password because in this case the password is not saved. ServerView Agents for Linux 20

21 2.3 ServerView security concept On the left-hand side of the Server Properties window you can select those servers to which the settings are to apply. You can also select several servers at once. This allows you to specify settings for each server individually or to apply an identical setting to several servers collectively. The following example demonstrates the procedure in the case of an activated user authentication. Example The user svuser was set up on the server and specified in Operations Manager in the Login tab on the management station. Executing a SET operation through the management station, the user is prompted to provide identification. Figure 3: User authentication ServerView Agents for Linux 21

22 2.4 Configuring SNMP services Operating system-specific characteristics of the SNMP agents The following sections describe the procedures, specific to the operating system and agent versions, involved in realizing the security concept of ServerView. SNMP security concept If you want to monitor the server from the management station, then you must set up a user belonging to the bin group after installing the operating system. You must enter this user name and its corresponding password in the management station to activate the corresponding function. For further information on installing the agents, see "Installing ServerView Agents" on page Configuring SNMP services You must install and configure the SNMP services of the current operating system on each managed server and the management station. The ServerView Linux Agents require configuration parameters in the configuration file of the system s SNMP service. You will find this file under the name /etc/snmp/snmpd.conf. You must edit this configuration file, e.g. with the help of the vi. Information on the syntax is provided in the manpages for snmpd.conf (call: man snmpd.conf). Specify the appropriate contact under syscontact and the location of the server under syslocation. Set authtrapenable to 1 (enable). This sends a trap if, during a SET operation, the community of the management station is unknown or the rights required for the SET operation are not present. With 2 (disable), you can disable this function (default). You will find further information on this in the snmpd.conf manpages. The following example shows a configuration which you must adapt to suit your network and your server environment: com2sec svsec localhost public com2sec svsec <subnet>/<netmask> public group svgroup v1 svsec view svview included.1 access svgroup "" any noauth exact svview none none You have to adapt <subnet>/<netmask> accordingly for your environment. By default read-only SNMP access is allowed. ServerView Agents for Linux 22

23 2.4 Configuring SNMP services If you are using more than two com2sec definitions, the order is of significance. The first com2sec definition that matches the IP address and the community of an incoming SNMP request is used. Thus the com2sec definitions for specific IP areas, must be set before the definitions for general access (with the same community). For further information, in particular on the syntax of subnet and netmask refer to the manpages for snmpd.conf. In the example, the community name is public. If, for security reasons, you decide to use another community name, replace the community name public used in the example with the chosen name. You must not forget to enter the chosen community name in the management station on the property page Network/Snmp in the Server Properties property window. To change values via SNMP access is not permitted by default. If you want to allow the management station to change values on the managed servers or to shut down, you have to permit SNMP SetRequests. To do so, change the last line of the example configuration shown above to: access svgroup "" any noauth exact svview svview none You must also check that the values for AgentPermission and AgentShut are set to 3. For further information on the definition of these values in the config file, see "Configuring agents" on page 39. Specify the target address for SNMP traps. For trapsink, enter the IP address or the name of the management station. You can enter more than one management station. Add one line for each management station in snmpd.conf: trapsink <host> <community name> For <community name>, enter public or the community name you wish to use. The GAM agent for LSI/Mylex RAID controller communicates with the SNMP master agent via the SMUX protocol (SNMP Multiplex Protocol). If the GAM agent is installed, you have to add the following line into the SNMP configuration file: smuxpeer mylex If you have made changes, restart the service snmpd or the server. ServerView Agents for Linux 23

24 2.5 Setting the hardware clock (CMOS clock) If a firewall is activated on your server, you must make sure that the SNMP ports are open. You must ensure that the following are accepted: Incoming packages on port 161 (service name snmp) for the protocol udp. Outgoing packages on port 162 (service name snmptrap) for the udp protocol which ensures that traps can be sent. Port 3172 (Remote Connector Service) and port 3173 (ServerView RAID Manager) for the tcp protocol. CIM server ports 5988 (for HTTP) or 5989 ( for HTTPS) 2.5 Setting the hardware clock (CMOS clock) The CMOS clock must be set to local time and not to GMT. Otherwise the automatic Power ON/Power OFF will not start at the configured time. The local time is set on the different operating systems as follows: SUSE: Assign the local time to the CMOS clock in YaST System. Observe the following specification: The Hardware Clock Set To UTC option must be disabled. In the Date and Time window, select the Local Time entry from the Hardware Clock Set To selection list. Red Hat: Assign the local time to the CMOS clock in linuxconf: Observe the following specifications: On the Time Zone tab in the Date and Time Properties window you can use the System Clock option. The System Clock uses UTC option must be disabled. Select System Administration Date & Time. Use the date command to output the system time, use hwclock --show to output the CMOS time. If the times are different, use the hwclock command to change the CMOS time to match the system time. More information about the hwclock command can be obtained using hwclock --help. ServerView Agents for Linux 24

25 2.6 Settings required for using the Driver Monitor functionality 2.6 Settings required for using the Driver Monitor functionality Driver Monitor functionality on SLES11 and SLES12/SLES 15 SUSE SLES 11: 1. Insert the following lines into the file /etc/syslog-ng/syslog-ng.conf: destination hwlog { pipe("/dev/hwlog/syslog_fifo"); }; log { source(src); destination(hwlog); }; SUSE SLES 12/SLES 15: 1. Insert the following line into the file /etc/rsyslog.conf: *.info;mail.none;news.none;authpriv.none;cron.none /dev/hwlog/syslog_fifo SUSE SLES 11 and SUSE SLES 12/SLES 15: 1. Start YaST and select AppArmor Configuration - Manage Existing Profiles 2. Choose the name of the active syslog daemon (/sbin/syslog-ng (SLES11) or /sbin/syslogd (SLES12/SLES 15) and click Edit. 3. Enter /dev/hwlog/syslog_fifo in the Enter or modify Filename field. 4. Under Permissions activate the Read and Write option. 5. Save this entry. 6. Restart AppArmor by: /etc/init.d/boot.apparmor restart 7. Restart syslog services by: /etc/init.d/syslog restart (SLES 11) systemctl restart rsyslog (SLES12/SLES 15) ServerView Agents for Linux 25

26 2.7 Installing the kernel modules for ServerView Agents Driver monitor functionality on RedHat For driver monitor function on Red Hat the following applies: During installation the following line is inserted into the syslog daemon configuration file and the syslog daemon is restarted: *.info;mail.none;news.none;authpriv.none;cron.none /opt/fujitsu/serverviewsuite/hwlog/path/syslog_fifo During uninstallation this entry is removed and the syslog daemon is restarted Settings required when default format of syslog is changed When the default format of syslog is changed manually by an administrator then please follow the instructions described in the Driver Monitor configuration text file included in the ServerView Agents Linux package. 2.7 Installing the kernel modules for ServerView Agents On some PRIMERGY server types, kernel modules are needed for full ServerView Agents functionality. This section describes how to install these kernel modules for SLES and RHEL Installing kernel modules for ServerView Agents (SUSE Linux) For detailed information on the Partner Linux Driver Process (PLDP) for PRIMERGY Servers, please visit: Getting the srvmagt-modules-<version>.iso driver kit image To get the srvmagt-modules-<version>.iso disk image, you have the following options: From the ServerView Suite DVD 2: Select SVSLinux - Novell-KMP, and then, in sequence, click in sequence through folders containing your preferred SLES version and Service pack. From ftp://ftp.ts.fujitsu.com/images/serverview, you can download the DVD ISO image UPD_LINUX_<version>.iso. Select Novell-KMP, an then, in sequence, click in sequence through folders containing your preferred SLES version and Service pack. From the Driver & Downloads website ( ServerView Agents for Linux 26

27 2.7 Installing the kernel modules for ServerView Agents A quick-search using the string "PLDP svrmagt-modules" in the Driver Quicksearch field will result in the list of all available PLDP driver package srvmagt-modules, from which you can select an appropriate package. Alternatively, you can proceed as follows: 1. Select Software - ServerView - Operation - Agents and Providers, which leads you to the Downloads for Agents and Providers page. 2. Select your preferred SUSE Linux version page. 3. Select Server Management Software - ServerView Agents & CIM Providers. The disk image can be found in the package PLDP driver package srvmagt-modules <version> for SLES<nn> SP<n> (file name: FTS_ PLDPdriverpackagesrvmagtmodules<version>.zip) Providing the srvmagt-modules-<version>.iso driver kit image on the managed server To provide the downloaded packages on the managed server, proceed as follows: 1. Loop-mount the iso image and make the repository known to the system: # mount -o loop /tmp/srvagt-modules-*.iso /mnt/img # zypper ar /mnt/img srvmagt 2. Install the module: # zypper install primergy-srvmagt-kmp-$kernel_flavor $KERNEL_FLAVOR is default or xen depending on the installed kernel. When asked about the package signing key with fingerprint A6E12DAE581F5A2C016C58E45FE63BCE , choose to trust the key. 3. Deactivate the repository again: # zypper rr srvmagt # umount /mnt/img Obtaining the kernel modules from an online repository Alternatively, you can configure your system to access the Fujitsu driver package repositories from (or from a mirror thereof if your system has no direct internet access). In this case, it is not necessary to download the ISO file. ServerView Agents for Linux 27

28 2.7 Installing the kernel modules for ServerView Agents Proceed as follows: 1. Make the driver repository known if necessary: Before submitting the following command, you have to substitute the operating system version corresponding your needs. # zypper ar primergy-sles12-sp3 2. Install the module: # zypper install primergy-smbus-kmp-$kernel_flavor Installing kernel modules for ServerView Agents (Red Hat Linux) For more information on the the Red Hat Driver Update Process (RHDUP) for PRIMERGY Servers, please visit: Getting the srvmagt-modules-<version>.iso driver disk image To get the srvmagt-modules-<version>.iso disk image, you have the following options: From the ServerView Suite DVD 2: Select SVSLinux - RHDUP, an then, in sequence, click in sequence through folders containing your preferred RHEL version and version update. From ftp://ftp.ts.fujitsu.com/images/serverview, you can download the DVD ISO image UPD_LINUX_<version>.iso. Select RHDUP, an then, in sequence, click in sequence through folders containing your preferred RHEL version and version update. From the Driver & Downloads website ( A quick search using the string "RHDUP svrmagt-modules" in the Driver Quicksearch field will result in the list of all available RHDUP driver package srvmagt-modules, from which you can select an appropriate package. Alternatively, you can proceed as follows: 1. Select Software - ServerView - Operation - Agents and Providers, which leads you to the Downloads for Agents and Providers page. 2. Select your preferred Red Hat Linux version. 3. Select Server Management Software - ServerView Agents & CIM Providers.The disk image can be found in the RHDUP driver package srvmagt-modules<version> ServerView Agents for Linux 28

29 2.7 Installing the kernel modules for ServerView Agents for RHEL<version> file name: FTS_ RHDUPdriverpackagesrvmagtmodules<version>.zip) Providing the srvmagt-modules-<version>.iso driver disk image on the managed server To provide the downloaded packages on the managed server, proceed as follows: 1. Loop-mount the iso image and make the repository known to the system: # mount -o loop /tmp/srvmagt-modules-*.iso /mnt/img # cp /mnt/img/dud.repo /etc/yum.repos.d/srvmagt.repo 2. Set path to mount point in the.repo file: # sed -i 's,<insert_mount_point_here>,mnt/img,' \ /etc/yum.repos.d/srvmagt.repo 3. Install primergy-dup with the GPG key: This step is only necessary if primergy-dup has never been installed on the system. # yum --disablerepo=\* --enablerepo=srvmagt_modules_ *\ install --nogpgcheck primergy-dup When asked about the package signing key with fingerprint A6E12DAE581F5A2C016C58E45FE63BCE , choose to trust the key. 4. Uncomment GPG key from primergy-dup package in the.repo file: This step is only necessary if primergy-dup has never been installed on the system. # sed -i '/gpgkey = file.*/s/^# //'\ /etc/yum.repos.d/srvmagt.repo 5. Install the modules: # yum --disablerepo=\* --enablerepo=srvmagt_modules_ *\ install kmod-srvmagt # umount /mnt/img When asked to confirm the driver signing key 0x , please agree. 6. Disable the repository again: # sed -i '/enabled/s/= yes/= no/' \ /etc/yum.repos.d/srvmagt.repo ServerView Agents for Linux 29

30 2.7 Installing the kernel modules for ServerView Agents Obtaining the kernel modules from an online repository Alternatively, you can configure your system to access the Fujitsu driver package repositories from (or from a mirror thereof if your system has no direct internet access). In this case, you do not need to download the ISO file. Proceed as follows: 1. Make the repository known if necessary: # cd /etc/yum.repos.d Before submitting the following command, you have to substitute the operating system version corresponding your needs. # curl -o primergy-rhel6-u4.repo 2. Make the Fujitsu GPG key known if necessary: # yum install --nogpgcheck primergy-dup 3. Install the modules: # yum install kmod--srvmagt When asked to confirm the driver signing key 0x , please agree. ServerView Agents for Linux 30

31 3 Installing ServerView Agents When using PKI (Public Key Infrastructure) for client authentication: Client authentication prevents the managed server from being accessed by a nontrusted management station or by a non-privileged application running on the management station. You have the option to either initially install the certificate files together with the ServerView Agents or to install the certificate files on a managed server where the ServerView Agents have already been installed. Installing the certificate files together with the ServerView Agents requires that the certificate files have already been installed on the managed server before the agents are actually installed. For details refer to the "User Management in ServerView" user guide. The extra packages required for ServerView Operations Manager and ServerView RAID Manager are described in the "Installation under Linux" installation guide. Installation of ServerView Agents on Citrix XenServer is offered via the XenServer Supplement CD. The CD is available via the ServerView Suite DVD 2 (ServerView - XenServer Supplements or SVSSoftware\Software\XenServer-Supplements). You can also download the ISO image from the Fujitsu web server ( It includes the necessary software packages, scripts that support installation, and configuration and release documentation. ServerView Agents for Linux 31

32 3.1 Requirements 3.1 Requirements Before the ServerView Agents are installed, several prerequisites must be fulfilled: The relevant Net-SNMP packages must be installed in accordance with the operating system platform: SUSE SLES Red Hat Enterprise Linux Oracle Linux Citrix XenServer net-snmp net-snmp and net-snmputils net-snmp and net-snmputils net-snmp The ServerView Agents require the following software packages: These packages can be installed using YaST / YUM (recommended). o SUSE SLES (The naming of the packages depends on SLES Version): SLES 11 SLES 12/ SLES 15 libstdc++6, libcurl4 and libopenssl0_9_8 libstdc++6,libcurl4 and libopenssl1_0_0 o Red Hat, Oracle Linux, Citrix XenServer: RHEL/OL openssl libstdc++ libcurl Citrix XenServer openssl libstdc++ Additional requirement for ServerView CIM Provider: o A CIMOM (CIM Object Manager) service must be available. Supported CIMOMs are SFCB and OpenPegasus. For management of your RAID peripherals you must also install ServerView RAID Manager on your system. The installation is described in the "RAID Management" user guide. Mount the ServerView Suite DVD 2 and, in the CD s root directory, open the start.html file in the web browser. Switch to ServerView Agents and Providers ServerView Agents for Linux 32

33 3.2 Script-based installation and click the ServerView Agents Linux and VMware link in the table. You will find the list of released PRIMERGY systems under Supported Systems. 3.2 Script-based installation You install ServerView Agents via the srvmagt script. It tries to test and verify all the dependencies known from experience, catches all the necessary preparations and finally performs the required actions to establish ServerView Agents Linux on the system. The script performs the following: Identify the Linux distribution (e.g. SUSE, Red Hat). Identify the kernel version. Identify the PRIMERGY server model using BIOS data. Identify, whether PLDP (Partner Linux Driver Process) and DUP (Driver Update Process) is supported. In this case, the script tries automatically to install the ServerView kernel module packages (KMP) if necessary. Verify presence of SNMP packages and other packages for specific models or distributions. Setting of snmpd.conf (for Japanese OS environment only) If you install ServerView Agents on a Japanese operating system, the installation script checks whether the SNMP service has to be configured. If so, a backup file /etc/snmp/snmpd.conf_svsave is created and the following entries are added to the file /etc/snmp/snmpd.conf: com2sec svsec localhost public com2sec svsec public com2sec svsec default public group svgroup v1 svsec view svview included.1 access svgroup "" any noauth exact svview svview none trapsink For further information, see "Configuring SNMP services" on page 22. ServerView Agents for Linux 33