Installation and User Guide - English
FUJITSU Software ServerView Suite
ServerView Agents V8.10 for Linux
(SUSE, Red Hat, and Citrix XenServer)
Edition July 2017
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 e-mail to
[email protected].
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
www.cognitas.de
Copyright and trademarks
Copyright 1998 - 2017 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.
Contents
1 Introduction
5
1.1 Architecture
6
1.2 Target groups and objectives
8
1.3 Technical requirements
8
1.3.1 Last-minute changes/corrections
1.3.2 Managed Server
8
8
1.4 What's new
9
1.5 ServerView Suite link collection
9
1.6 Documentation for the ServerView Suite
10
1.7 Notational conventions
11
2 Preparations on the managed servers
12
2.1 Configuring the BIOS and Firmware
13
2.1.1 BIOS settings
13
2.2 Configuring servers
16
2.3 ServerView security concept
17
2.3.1 Prohibiting specific SET operations
2.3.2 Prohibiting All SET operations
2.3.3 SET Operations with user authentication
2.3.4 Operating system-specific characteristics of the SNMP agents
18
18
18
21
2.4 Configuring SNMP services
21
2.5 Setting the hardware clock (CMOS clock)
23
2.6 Settings required for using the Driver Monitor functionality
24
2.6.1 Driver Monitor functionality on SLES11 and SLES12
2.6.2 Driver monitor functionality on RedHat
2.7 Installing the kernel modules for ServerView Agents
2.7.1 Installing kernel modules for ServerView Agents (SUSE Linux)
2.7.1.1 Getting the srvmagt-modules-<version>.iso driver kit image
2.7.1.2 Providing the srvmagt-modules-<version>.iso driver kit image on the managed
server
2.7.1.3 Obtaining the kernel modules from an online repository
2.7.2 Installing kernel modules for ServerView Agents (Red Hat Linux)
2.7.2.1 Getting the srvmagt-modules-<version>.iso driver disk image
ServerView Agents for Linux
24
24
25
25
25
26
26
27
27
3
Inhalt
2.7.2.2 Providing the srvmagt-modules-<version>.iso driver disk image on the managed
server
2.7.2.3 Obtaining the kernel modules from an online repository
27
28
3 Installing ServerView Agents
30
3.1 Requirements
31
3.2 Script-based installation
32
3.2.1 Installation via ServerView Suite DVD 2
3.2.2 Installation from a directory
33
33
3.3 Installation with the rpm command
34
3.4 Possible sources of error
35
3.5 ServerView Agents maintenance after the installation
35
3.5.1 The srvmagt script
3.5.2 Configuring agents
3.5.3 Improved availability of ServerView Agents
3.5.4 Uninstalling ServerView Agents
3.5.5 Starting and stopping the ServerView Agents
3.5.6 Starting and stopping ServerView CIM Provider
3.5.7 Additional information
3.5.8 Setting an administrative user
3.5.9 Computer information change after installation
3.5.10 Update installation / kernel update
3.5.11 Outputting reports with Performance Manager
3.5.12 Temporary file under /tmp directory
3.5.13 Source name of syslog
35
37
40
40
40
41
41
42
43
43
44
44
45
3.6 Configuring APC UPS
ServerView Agents for Linux
45
4
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 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:
l
Global user management via an LDAP directory service (Lightweight Directory Access
Protocol)
l
Role-Based Access Control (RBAC)
l
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:
l
Higher productivity thanks to high failsafety of the servers
l
Reduced costs through automated monitoring of the IT infrastructure
l
Flexible expansion possibilities for the servers, as Operations Manager can be easily
adjusted to changed conditions
l
Shorter downtimes thanks to simplified error analysis
l
Guarantees energy-efficient and, where possible, uninterruptible server operation
l
Quicker response times in the event of errors
l
Reduction in total cost of ownership (TCO) through efficient use of network
ServerView Agents for Linux
5
1.1 Architecture
components and their resources
l
1.1
Very easy operation thanks to ergonomic software: clearly laid out, intelligent user
guidance and supportive help system
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 Java Web Start-based console allows you to manage the servers and
display the determined data. All you need is a popular web browser to
download the starter file for Java Web Start. The following can be used as a
browser:
l
Microsoft Windows with any popular web browser
l
SUSE/Red Hat Linux with default web browser released with distribution
The Java Runtime Environment must also be installed.
ServerView Agents for Linux
6
1.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 in Windows-based or Linuxbased virtual machines (VM) that use hypervisors such as VMware ESXi,
Microsoft Hyper-V, and Red Hat Enterprise KMV.
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:
l
ApacheDS
l
Microsoft Active Directory
During the installation of ServerView Operations Manager you have the option to choose
ServerView’s internal directory service (ApacheDS). 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 10).
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:
l
SQL Server 2014 Express under Windows Server
l
PostgreSQL under Linux
However, other Microsoft SQL Server databases can be used under Windows.
The Java Runtime Environment is required on the central management station.
How to install the ServerView Operations Manager is explained in the following manuals:
l
l
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 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.
ServerView Agents for Linux
7
1.2 Target groups and objectives
l
The ServerView Agents are available for Windows, Linux, and Citrix XenServer.
l
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:
1.2
l
ServerView Agents for Windows
l
ServerView Agents for Linux
l
Installation ServerView ESXi CIM Provider
l
ServerView CIM Providers for Windows, Linux, and VMware ESXi
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
1.3.1
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:
l
l
1.3.2
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:
l
SUSE (SLES 11): SP3 and SP4
l
SUSE (SLES 12): SP1 and SP2
l
Red Hat Enterprise Linux 6.7/6.8/6.9
l
Red Hat Enterprise Linux 7.2/7.3
l
Oracle Linux OL 6.7/6.8
ServerView Agents for Linux
8
1.4 What's new
1.4
l
Oracle Linux OL 7.2/7.3
l
Oracle VM 3.3
l
Citrix XenServer 6.5
l
Citrix XenServer 7.0/7.1
What's new
This edition of the manual applies to ServerView Agents V8.00 or higher and replaces the
online manual "ServerView Agents V7.31 for Linux", edition November 2016.
The manual features the following changes and enhancements:
1.5
l
No 32-Bit system support.
l
The technical requirements has been updated, see "Technical requirements" on page 8.
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:
l
Forum
l
Service Desk
l
Manuals
l
Product information
l
Security information
l
Software downloads
l
Training
Software downloads includes the following downloads:
o
Current software statuses for the ServerView Suite as well as additional Readme
files.
o
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.
o
The current versions of all documentation on the ServerView Suite.
You can retrieve the downloads free of charge.
ServerView Agents for Linux
9
1.6 Documentation for the ServerView Suite
Under PRIMERGY Server, links are offered on the following topics:
l
Service Desk
l
Manuals
l
Product information
l
Spare parts catalogue
Access to the ServerView Suite link collection
You can reach the link collection of the ServerView Suite in various ways:
1. Via ServerView Operations Manager.
l
Select Help – Links on the start page or the menu bar.
2. 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:
http://manuals.ts.fujitsu.com
l
In the selection list on the left, select x86 Servers.
l
On the right, click PRIMERGY ServerView Links under Selected documents.
3. Via the ServerView Suite DVD 2.
l
l
In the start window of the ServerView Suite DVD 2, select the option ServerView
Software Products.
On the menu bar select Links.
This opens the start page of the ServerView Suite link collection.
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 http://manuals.ts.fujitsu.com 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.
ServerView Agents for Linux
10
1.7 Notational conventions
1.7
Notational conventions
The following notational conventions are used in this manual:
Notational
conventions
Indicates
Indicates various types of risks, namely health risks,
risk of data loss and risk of damage to devices.
Indicates additional relevant information and tips.
Bold
Indicates references to names of interface elements.
monospace
Indicates system output and system elements, for
example file names and paths.
monospace
semibold
Indicates statements that are to be entered using
the keyboard.
blue continuous
text
Indicates a link to a related topic.
purple continuous Indicates a link to a location you have already
text
visited.
<abc>
Indicates variables which must be replaced with
real values.
[abc]
Indicates options that can be specified (syntax).
[key]
Indicates a key on your keyboard. If you need to
explicitly 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
The screenshots are to some degree system-dependent and consequently will not
necessarily match the output on your system in all the details. The menus and their
commands can also contain system-dependent differences.
ServerView Agents for Linux
11
2
Preparations on the managed servers
Before starting the Operations Manager, the following preparations must be made on the
managed server:
l
Only for PRIMERGY: Certain settings must be made in the BIOS on each managed
server, see "Configuring the BIOS and Firmware" on page 13.
On each server, you must make configuration settings, see "Configuring servers" on
page 16.
l
l
l
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 17.
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 21.
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.
l
l
l
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 23.
The settings required for using the Driver Monitor functionality must be configured.
See "Settings required for using the Driver Monitor functionality " on page 24.
ServerView Agents must be installed on each server to be managed, see "Installing
ServerView Agents" on page 30.
The installation of ServerView Agents on virtual machines (VMs) is not
released.
l
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
12
2.1 Configuring the BIOS and Firmware
l
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
l
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.
2.1.1
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.
ServerView Agents for Linux
13
2.1 Configuring the BIOS and Firmware
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.
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.
ServerView Agents for Linux
14
2.1 Configuring the BIOS and Firmware
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.
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: Storage Extension is not available on all servers)
ServerView Agents for Linux
15
2.2 Configuring 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:
l
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.
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].
l
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.
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:
l
Read the most important data of the server, the system board and the integrated
management controller.
ServerView Agents for Linux
16
2.3 ServerView security concept
l
Read and set the Boot and Software Watchdog settings.
l
Read and edit the error counter for the memory modules.
For PRIMERGY only:
l
Read and delete the error and event logs of the server.
l
Monitor and calibrate the system fan.
l
Read and set the chassis ID (preset on delivery).
l
Read and set the counters for the system runtimes.
l
l
l
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.
l
Manage user identification for the remote management controller.
l
Configure the serial interface of the RSB and the remote management controller.
l
Configure Operations Manager UPS management integration.
l
2.3
Configure the settings for HTTP and Telnet and the setting for the Remote Management
Controller for HTTP.
Configure the information shown on the display of the ServerView Local Service
Display.
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:
l
Prohibit specific SET operations.
l
Prohibit all SET operations.
l
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 21.
ServerView Agents for Linux
17
2.3 ServerView security concept
2.3.1
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 37 - AgentShut.
2.3.2
Prohibiting All SET operations
You can prohibit all SET operations for ServerView Agents. Enter these specifications during
agent installation, see "Configuring agents" on page 37 - AgentPermission.
This option only applies to ServerView Agents. SET operations for other SNMP
agents are not affected.
2.3.3
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
managed server
Settings
l
Define user and user group
l
Assign user to specific user group
l
State the specified user group during installation of the
agent
management station Specify the user in the Operations Manager Login tab.
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
ServerView Agents for Linux
18
2.3 ServerView security concept
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 37.
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
19
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
20
2.4 Configuring SNMP services
2.3.4
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 30.
2.4
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).
l
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.
l
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
21
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.
l
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.
l
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 37.
l
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.
l
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 .1.3.6.1.4.1.1608 mylex
l
If you have made changes, restart the service snmpd or the server.
ServerView Agents for Linux
22
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:
l
l
l
l
2.5
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)
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:
o
SUSE:
Assign the local time to the CMOS clock in YaST – System.
SUSE SLES 11:
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.
o
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
23
2.6 Settings required for using the Driver Monitor functionality
2.6
Settings required for using the Driver Monitor
functionality
2.6.1
Driver Monitor functionality on SLES11 and SLES12
l
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); };
l
SUSE SLES 12:
1. Insert the following line into the file /etc/rsyslog.conf:
*.info;mail.none;news.none;authpriv.none;cron.none
|/dev/HWLog/syslog_fifo
l
SUSE SLES 11 and SUSE SLES 12:
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) 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)
2.6.2
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
ServerView Agents for Linux
24
2.7 Installing the kernel modules for ServerView Agents
During uninstallation this entry is removed and the syslog daemon is restarted.
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.
2.7.1
Installing kernel modules for ServerView Agents (SUSE Linux)
For detailed information on the Partner Linux Driver Process (PLDP) for PRIMERGY
Servers, please visit:
http://ts.fujitsu.com/products/standard_servers/linux_readmes_popup.html
2.7.1.1
Getting the srvmagt-modules-<version>.iso driver kit image
To get the srvmagt-modules-<version>.iso disk image, you have the following options:
l
l
l
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 (http://ts.fujitsu.com/support/downloads.html):
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:
a. Select Software - ServerView - Operation - Agents and Providers, which
leads you to the Downloads for Agents and Providers page.
b. Select your preferred SUSE Linux version page.
c. 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).
ServerView Agents for Linux
25
2.7 Installing the kernel modules for ServerView Agents
2.7.1.2
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-smbus-kmp-$KERNEL_FLAVOR
$KERNEL_FLAVOR is "default" or "xen" depending on the installed kernel.
When asked about the package signing key with fingerprint
A6E12DAE581F5A2C016C58E45FE63BCE79444536, choose to trust the key.
3. Deactivate the repository again:
# zypper rr srvmagt
# umount /mnt/img
2.7.1.3
Obtaining the kernel modules from an online repository
Alternatively, you can configure your system to access the Fujitsu driver package
repositories from http://patches.ts.fujitsu.com/linux/index_pldp.html (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.
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
http://patches.ts.fujitsu.com/linux/pldp/SLE11/sles11-sp3/
primergy-sles11-sp3
2. Install the module:
# zypper install primergy-smbus-kmp-$KERNEL_FLAVOR
ServerView Agents for Linux
26
2.7 Installing the kernel modules for ServerView Agents
2.7.2
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:
http://ts.fujitsu.com/products/standard_servers/linux_readmes_popup.html
2.7.2.1
Getting the srvmagt-modules-<version>.iso driver disk image
To get the srvmagt-modules-<version>.iso disk image, you have the following options:
l
l
l
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 (http://ts.fujitsu.com/support/downloads.html):
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:
a. Select Software - ServerView - Operation - Agents and Providers, which
leads you to the Downloads for Agents and Providers page.
b. Select your preferred Red Hat Linux version.
c. Select Server Management Software - ServerView Agents & CIM
Providers.The disk image can be found in the RHDUP driver package
srvmagt-modules<version> for RHEL<version> file name: FTS_
RHDUPdriverpackagesrvmagtmodules<version>.zip).
2.7.2.2
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
ServerView Agents for Linux
27
2.7 Installing the kernel modules for ServerView Agents
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_
8.00.10*\install --nogpgcheck primergy-dup
When asked about the package signing key with fingerprint
A6E12DAE581F5A2C016C58E45FE63BCE79444536, 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_
8.00.10*\install kmod-smbus
# umount /mnt/img
When asked to confirm the driver signing key 0x79444536, please agree.
6. Disable the repository again:
# sed -i '/enabled/s/= yes/= no/' \
/etc/yum.repos.d/srvmagt.repo
2.7.2.3
Obtaining the kernel modules from an online repository
Alternatively, you can configure your system to access the Fujitsu driver package
repositories from http://patches.ts.fujitsu.com/linux/index_pldp.html (or from a mirror
thereof if your system has no direct internet access).
In this case, you don't need to download the ISO file
Proceed as follows:
1. Make the repository known if necessary:
# cd /etc/yum.repos.d
ServerView Agents for Linux
28
2.7 Installing the kernel modules for ServerView Agents
Before submitting the following command, you have to substitute the
operating system version corresponding your needs.
# curl -o primergy-rhel6-u4.repo
http://patches.ts.fujitsu.com/linux/pldp/RHEL6/rhel6-u4.repo
2. Make the Fujitsu GPG key known if necessary:
# yum install --nogpgcheck primergy-dup
3. Install the modules:
# yum install kmod-smbus
When asked to confirm the driver signing key 0x79444536, please agree.
ServerView Agents for Linux
29
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
(http://support.ts.fujitsu.com/download/).
It includes the necessary software packages, scripts that support installation, and
configuration and release documentation.
ServerView Agents for Linux
30
3.1 Requirements
3.1
Requirements
Before the ServerView Agents are installed, several prerequisites must be fulfilled:
l
l
The relevant Net-SNMP packages must be installed in accordance with the operating
system platform:
SUSE SLES
net-snmp
Red Hat Enterprise
Linux
net-snmp and net-snmp-utils
Oracle Linux
net-snmp and net-snmp-utils
Citrix XenServer
net-snmp
The ServerView Agents require the following software packages:
These packages can be installed using YaST / YUM (recommended).
o
o
SUSE SLES (The naming of the packages depends on SLES Version):
SLES 11
libstdc++6, libcurl4 and
libopenssl0_9_8
SLES 12
libstdc++6, libcurl4 and libopenssl1_0_0
Red Hat, Oracle Linux, Citrix XenServer:
RHEL/OL
openssl
libstdc++
libcurl
Citrix XenServer openssl
libstdc++
l
Additional requirement for ServerView CIM Provider:
o
l
l
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 and click the
ServerView Agents for Linux
31
3.2 Script-based installation
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:
l
Identify the Linux distribution (e.g. SUSE, Red Hat).
l
Identify the kernel version.
l
Identify the PRIMERGY server model using BIOS data.
l
l
l
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 127.0.0.1 public
com2sec svSec default public
group svGroup v1 svSec
view svView included .1
access svGroup "" any noauth exact svView svView none
trapsink 127.0.0.1
For further information, see "Configuring SNMP services" on page 21.
ServerView Agents for Linux
32
3.2 Script-based installation
3.2.1
Installation via ServerView Suite DVD 2
The ServerView Suite DVD 2 contains the rpm packages of the ServerView Agents and the
shell archive srvmagtDVD.sh. You will find the script on the ServerView Suite DVD 2 in the
following directory:
SVSSoftware\ Software\ServerView\Linux\Agents- V8xx\x86-64
To install the agent proceed as follows:
1. Insert the ServerView Suite DVD 2 and mount it if necessary.
2. Open (as root) a terminal.
3. Change to the directory SVSSoftware\ Software\ServerView\Linux\Agents- V8xx\x86-64
.
4. Enter the following command:
./srvmagtDVD.sh [-R] [--ssm install | not-install]
-R
Installs the ServerView RAID Manager RPM package if it is supplied together with
the other RPM packages.
--ssm install | not-install
Determines the installation of the ServerView System Monitor Web Interface.
Default is to install the package.
This option is only evaluated on Red Hat, SUSE and Oracle Linux systems.
The script then executes the installation automatically.
If the installation of ServerView System Monitor or CIM Provider fails, the
installation of ServerView Agents is not aborted.
3.2.2
Installation from a directory
You can download the ZIP file containing the shell archive srvmagt.sh and the RPM
packages of the ServerView Agents from the Fujitsu web server
(http://support.ts.fujitsu.com/download/) in any directory.
ServerView Agents for Linux
33
3.3 Installation with the rpm command
Important note:
The procedure decribed below prerequisites that the srvmagt-modules<version>.iso driver kit/disk has been already mounted on the managed server
(see sections "Installing kernel modules for ServerView Agents (SUSE Linux)" on
page 25 "Installing kernel modules for ServerView Agents (SUSE Linux)" on page
25).
To install the agent proceed as follows:
1. Download the appropriate ServerView Agents Linux package (FTS_
ServerViewAgentsLinux_<version>_<nnnnnnn>.zip as described below:
a. In the Driver & Downloads page website
(http://ts.fujitsu.com/support/downloads.html), select Software - ServerView Operation - Agents and Providers, which leads you to the Downloads for Agents
and Providers page.
b. Select your preferred Red Hat / SUSELinux version.
c. Select Server Management Software - ServerView Agents & CIM ProvidersSeverView Agents for Linux.
2. Save the installation RPM packages and the shell archive srvmagt.sh in any directory.
3. Open (as root) a terminal.
4. Change to the corresponding directory:
cd <path>
5. Grant permission for execting srvmagt.sh:
chmod +x srvmagt.sh
6. Enter the following command:
./srvmagt.sh [option] install
The options are described in "The srvmagt script" on page 35.
The script installs all RPM packages.
3.3
Installation with the rpm command
When installing with the rpm command, proceed as follows:
1. Start (as root) a terminal.
2. Mount the ServerView Suite DVD 2.
3. Switch to the directory containing the Linux Agents:
cd /mnt/cdrom/SVSSoftware/Software/
ServerView/Linux/Agents
ServerView Agents for Linux
34
3.4 Possible sources of error
4. Install the following RPM packages:
rpm -U ServerViewConnectorService-<scs-version><release>.x86_64.rpm
rpm -U srvmagt-mods_src-<version>-<release>.x86_64.rpm
rpm -U srvmagt-eecd-<version>-<release>.x86_64.rpm
rpm -U srvmagt-agents-<version>-<release>.x86_64.rpm
rpm -U srv-cimprovider-<version>.x86_64.rpm
rpm -U SSMWebUI-<version>.noarch.rpm
The packages must be installed in the above order.
<scs-version>
Specify the version and the release number of the Remote Connector Service (e.g.
2.21.00).
<version>
Specify the version and the release number of the ServerView Linux Agents (e.g.
8.00-10).
3.4
Possible sources of error
l
l
If errors occur during compilation, this may be because the suitable kernel source code
is not available on the server.
If you want to start compilation of the modules subsequently by hand, you can do this
with the command:
/etc/init.d/eecd_mods_src start
If you want to have the compiler outputs displayed, you start make directly in
directory /etc/srvmagt/sources.
3.5
ServerView Agents maintenance after the installation
3.5.1
The srvmagt script
Once you have installed the ServerView Agents for Linux, as described in "Installation via
ServerView Suite DVD 2" on page 33 or in "Installation from a directory" on page 33,
further functions are provided for maintenance via the srvmagt script.
ServerView Agents for Linux
35
3.5 ServerView Agents maintenance after the installation
1. Open a terminal (as root)
2. Enter the command, see syntax.
Syntax
[/usr/sbin/]srvmagt [option] [action]
For option you can specify:
-f
Forces the intended action against an issued warning/rejection.
In that case you act on your own risk and responsibility. The behavior and
functionality is undefined.
-h | --help
Displays the command syntax and exits.
-n
Does not start any ServerView Agents' daemon during installation with the install
action.
-p <path>
Here you can specify the directory containing the RPM packages.
<path> is a path to a directory in a local or remote file system.
The path option must not contain spaces or special characters.
-R
Installs the ServerView RAID Manager RPM package, if it is supplied together with the
other RPM packages.
--ssm install | not-install
Determines the installation of the ServerView System Monitor Web Interface. Default is
to install the package.
This option is only evaluated on Red Hat, SUSE and Oracle Linux systems.
-v <vers>
Indicates the version to handle. Default is the version of the script.
--version
Prints the script version and exits.
-V
Prints verbose information.
ServerView Agents for Linux
36
3.5 ServerView Agents maintenance after the installation
For action you can specify:
install
Installs (repairs, updates) all ServerView Agents Linux RPM packages according to the
already installed configuration and the version supplied with the -v option. The
corresponding services (i.e. daemons) are started afterwards unless the -n option is
also given.
start
Starts ServerView Agents Linux.
restart
Restarts ServerView Agents Linux.
status
Shows status of ServerView Agents Linux.
diag
Collects diagnostic material by calling PrimeCollect(8).
stop
Stops ServerView Agents Linux.
remove
Removes all ServerView Agents Linux RPM packages.
If the operating system is Citrix XenServer, the ServerView RAID package is also
removed at the same time.
3.5.2
Configuring agents
The file /etc/srvmagt/config contains information which enables you to restrict access to
the managed system and select other operating parameters.
Lines that begin with the "#" sign are comment lines and the other lines have the
following format:
<keyword>=<value>
AgentPermission Basic permission for other systems to set values on the local server with
the help of SNMP commands (2: not allowed, 3: allowed, default: 2
(default for Japanese OS environment: 3)). If you want to permit SNMP
SetRequests you must set the value to 3 here and configure the SNMP
services appropriately (see "Configuring SNMP services" on page 21).
ServerView Agents for Linux
37
3.5 ServerView Agents maintenance after the installation
AgentShut
Permission for remote shutdown/reboot of the local server using SNMP
commands (2: not allowed, 3: allowed, default: 2, i.e. not allowed
(default for Japanese OS environment: 3)). If you want to permit SNMP
SetRequests you must set the value to 3 here and configure the SNMP
services appropriately (see "Configuring SNMP services" on page 21).
ShutdownDelay Indicates the time delay (in minutes) between an SNMP shutdown
request and the shutdown.
NoAccountCheck If a value other than 0 is specified for this entry, you are not prompted
for a password when you modify settings via ServerView. The default
value is 0, i.e. the user group authentication is enabled by default. In
this case a user group must be entered under UserGroup, to which the
user that wishes to change the SNMP settings must belong.
Please note that a deactivated password query can pose a considerable
security risk.
UserGroup
If 0 was specified for NoAccountCheck, Operations Manager requires a
user/password combination on the management station in order for the
SNMP settings to be changed. In order for a user to be granted access
permission, the user must belong to the user group specified for
UserGroup. The default setting is bin, which includes root. (The default
setting for Japanese OS environment is svagtuser.)
If the user group specified here does not exist, it must be created using
operating system-specific resources.
ScanTapeDevices If this is set to something other than zero, the tape devices /dev/nst*
are opened in order to get their current status. The opening of the tape
device might cause (depending on the driver) an unintentional change
of its read/write position. If the tape device is shared among servers,
this parameter makes sure that Operations Manager does not impact
tape operations (e.g. backup) by state queries. The default is zero, i.e.
tape devices are not opened.
TraceFileLimit
Controls the size of the trace files stored under /var/log/srvmagt (1 is
the default value, required space approx. 200 MB, 0 means no trace
files, 2 means extra large trace files approx. 400 MB).
InventoryRescan Specifies the time period (in minutes) within which the inventory data
of the server is updated. Supported values are: 0, 120...34560. The
value 0 disables the update. Values between 1 and 120 are set to 120.
Values greater than 34560 are set to 0. The default value is 120 (The
default value for Japanese OS environment is 0).
ServerView Agents for Linux
38
3.5 ServerView Agents maintenance after the installation
Note that changes made to the config file will only take effect on restarting the
agent. You can do this by restarting the server or by entering the following
command as the system administrator:
/usr/sbin/srvmagt restart
Citrix Xen or Xen
To support the performance and threshold manager for Citrix Xen or Xen in the ServerView
Operations Manager, it is necessary to configure account information for the system within
ServerView VME agent. In order to do so, the following steps are necessary:
1. Edit the file /etc/srvmagt/VME/etc/app.config.xml.
2. Search for the section titled <authentication>.
3. Fill in user and password information as necessary.
Example
E.g. <User>us123</User><Password>123passwd</Password>
The password is in plain text, so you must limit access to this file and you
should not use a privileged user.
4. Save the file.
5. Restart the ServerView Agents.
KVM virtual hosts don't require username and password.
ServerView Agents for Linux
39
3.5 ServerView Agents maintenance after the installation
3.5.3
Improved availability of ServerView Agents
The start script srvmagt(8) of ServerView Agents invokes the srvmagt cron script
srvmagtCron to run every 15 minutes.
srvmagtCron checks the eecd daemon, the ServerView Agents, SVRemoteConnector and the
SNMP daemon snmpd and restarts them if they are not running. Additionally the script
writes the time of each check into the first line of the file
/var/log/srvmagt/log.srvmagtCron.
Stopping the ServerView Agents with srvmagt(8) turns this periodical supervision off.
srvmagtCron will not be removed from the root's crontab in order to keep changes of the
sensitive crontab to a minimum. Actual execution depends on existence of the
srvmagtCronOn file in the srvmagt root directory. This file is created during start of
ServerView Agents and removed when they are stopped.
3.5.4
Uninstalling ServerView Agents
The items saved on the server's BIOS are not restored, even when ServerView Agents are
uninstalled. Restore the settings to the original state, and then uninstall the ServerView
Agents.
Make sure you do the following before uninstalling ServerView Agents.
1. Disable the Software Watchdog, BOOT Watchdog and Power ON/OFF settings.
2. If threshold monitoring and report creation have been applied by Performance
Manager, cancel these services to the server.
3. When uninstalling the ServerView Agents, some settings that are configured using
ServerView Operations Manager are deleted. The option to take over the settings
automatically is not provided, so make sure you keep a copy of the settings before
uninstalling, as you will have to configure them again after the update installation.
To uninstall the ServerView Agents, enter the following:
/usr/sbin/srvmagt remove
On Citrix XenServer, ServerView RAID Manager is also uninstalled using this command.
3.5.5
Starting and stopping the ServerView Agents
After the ServerView Agents have been installed, the agents are started automatically with
each system startup. For diagnostic purposes, it may be meaningful to explicitly stop and
then restart the agent.
ServerView Agents for Linux
40
3.5 ServerView Agents maintenance after the installation
Starting agents
You start the agents with the following call:
/usr/sbin/srvmagt start
You must make sure that you start the SNMP master agent snmpd before you start
the Linux agent.
Stopping agents
You stop the agents with the following call:
/usr/sbin/srvmagt stop
3.5.6
Starting and stopping ServerView CIM Provider
Starting and stopping of the ServerView CIM Provider is done by the CIMOM.
For startup and shutdown of the CIMOM, see the documentation of the respective CIMOM.
3.5.7
Additional information
l
If an S30 or S40 is connected to a server via SCSI (SAF-TE), but not registered by the
agents it may be that there are not sufficient device files set up in Linux. These device
files are necessary for the communication of SNMP agents and the storage expansion
units. By default, Linux sets up 16 device files for the SCSI connections: /dev/sg0
through /dev/sg15. If you wish to connect more than 16 devices via SCSI you will need
to add additional device files. The number of SCSI device files can be found in the file
/proc/scsi/scsi. Additional device files (/dev/sg) can be added using the following
command:
mknod /dev/sg<number> c 21 <number>
In place of <number> enter the numbers in sequence in relation to the last existing
entry (for example, 16 and above, if the last entry contains the number 15). After you
have created new device files you must restart the server.
l
If new hardware (e.g. a remote service board) has been installed or a new storage
expansion unit has been added and not recognized then you will need to carry out a
“rescan” of the eecd (environment enclosure control daemon). Restart the eecd using
the following commands:
/etc/init.d/srvmagt stop
/etc/init.d/eecd stop
/etc/init.d/eecd rescan
/etc/init.d/srvmagt start
ServerView Agents for Linux
41
3.5 ServerView Agents maintenance after the installation
3.5.8
Setting an administrative user
Only users belonging to the group that have Administrator privileges for ServerView can
perform operations such as configuring Automatic Server Reconfiguration & Restart (ASR)
settings (e.g. fans, temperature, restart settings) for the monitored server and shutting
down the server from ServerView Operations Manager. These operations require the
administrative user's name and password.
The group with Administrator privileges is a group set to UserGroup, as described in
"Configuring agents" on page 37.
To set an administrative user, proceed as follows:
l
Create a new user as an administrative user:
Log in as a root and execute the following commands:
1. Specify the group name that has Administrator privileges in the G option of the
useradd command:
# useradd -G <group name that has Administrator
privileges> <user name>
# passwd <user name>
For <user name>, specify a name for the user to be created.
2. Use the passwd command to set the password for the new user. The password
must be entered twice for verification.
The newly created user name is enabled when the password is set. For details of each
command, refer to the useradd (8) and passwd (1) man page.
l
Set the existing user as an administrative user.
Contact the system administrator to check whether the existing user to be set belongs
to multiple groups and then execute the following command.
ServerView Agents for Linux
42
3.5 ServerView Agents maintenance after the installation
If the user only belongs to the main group:
# usermod -G <group name that has Administrator privileges>
<user name>
If the user belongs to multiple groups:
# usermod -G <group name that has Administrator
privileges>,<user group,...> <user name>
Specify the group name that has Administrator privileges in the G option of the
usermod command. To specify multiple groups, separate them with a comma ",". If the
group to which the user previously belonged is not specified, the user is deleted from
that group. Specify all groups to which the user is to belong.
For <user name>, specify the user name as an administrative user.
For details of the usermod command, refer to the usermod (8) man page.
You can also set the groups directly by using the vigr command or set them using GUI
tools. For details, refer to the vigr (8) man page or the Red Hat Linux manuals.
3.5.9
Computer information change after installation
If the computer name or IP address of the server in which the ServerView Agents are
installed for management is changed, you do not need to change the settings etc. on the
ServerView Agents.
However, if you have previously edited the snmpd.conf file for an individual environment,
edit the snmpd.conf file again if necessary.
After you have edited the snmpd.conf file, restart the snmpd service and the ServerView
Linux Agent as follows:
1. Log in as root.
2. Execute the following command.
# /usr/sbin/srvmagt stop
# /etc/init.d/snmpd stop
# /etc/init.d/snmpd start
# /usr/sbin/srvmagt start
3.5.10 Update installation / kernel update
This section describes the update installation process of ServerView Linux Agents.
1. If you have set the software watchdog and the BOOT watchdog to Enable, set them to
Disable.
2. Update the kernel via kernel update and then reboot the operating system.
ServerView Agents for Linux
43
3.5 ServerView Agents maintenance after the installation
3. /etc/snmp/snmpd.conf_svsave file creation (Japanese environment only).
Check whether the file /etc/snmp/snmpd.conf_svsave exists.
If the file does not exist, create it with the following command:
# cp /etc/snmp/snmpd.conf /etc/snmp/snmpd.conf_svsave
If the snmpd.conf_svsave file exists, it is not edited in the installation script.
4. Update the ServerView Linux Agents.
5. If you have disabled the software and BOOT watchdog in step 1, enable them again.
3.5.11 Outputting reports with Performance Manager
The report settings of Performance Manager enable outputting reports.
Storing the report data
The report data is stored in the following folder: /var/srvmagt/reports/
Files of report data
The following files are created for each report. xxx indicates a report name which is set in
Performance Manager:
l
xxx.dat
l
xxx.ind
l
xxx.names
If you delete the report settings in Performance Manager, these files will also be deleted.
If you do not set Maximum number of recorded report entries for the report
definition in Performance Manager, or if you output reports for a long time by
polling the server at short intervals, this may lead to disk space constraints
because a file grows too large. To avoid this, make sure you set the number of
entries and the interval for outputting reports correctly.
3.5.12 Temporary file under /tmp directory
When the ServerView Agents are started, a temporary file with the size 0 bytes is created in
the /tmp directory with the name S.xxxxxx (xxxxxx is an arbitrary alphanumeric string).
This file allows the subagent of the ServerView Agents and snmpd to communicate.
The location of this file cannot change.
Moreover, the ServerView Agents might not operate normally if you delete the file
manually.
ServerView Agents for Linux
44
3.6 Configuring APC UPS
3.5.13 Source name of syslog
When the ServerView Agents detect a hardware error, it reports the error in syslog. The
source name of the events reported by ServerView Agents is Serverview.
3.6
Configuring APC UPS
The following description is only valid for PRIMERGY.
In order to monitor the UPS, the corresponding agents (APC) must be installed on the
server. For an APC UPS with a web card, the relevant SNMP agent is pre installed on the
web card.
If you want the existing UPS configuration to be displayed in the Operations Manager
application, then you must first enter it via the installation program. Automatic detection
of the UPS has not yet been implemented. Every UPS entry will then contain, among other
things, the hardware that it monitors.
The oemups utility is available for configuring the UPS. To add UPS entries, enter the
following command:
oemups -a
The Vendor Name, UPS Type, IP Address and Cabinet ID parameters will then be queried.
Default values (American Power Conversion, APC UPS, 0.0.0.0, 0) will initially appear in
these fields. For IP Address, you have to enter the IP address of the server or the IP
address of the UPS with a web card.
You can list all existing UPS entries using the following command:
oemups -l
You can delete a UPS entry with the command:
oemups -d <number of the UPS entry>
Note that any changes made will only become active after the server has been
rebooted.
ServerView Agents for Linux
45