1. No category

Installation and User Guide - English
FUJITSU Software ServerView Suite
ServerView Agents V7.10 for
Windows
(Windows Server 2008/2012)
Edition April 2015
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 - 2015 Fujitsu Technology Solutions.
All rights reserved.
Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective
manufacturers.
Contents
1 Introduction
1.1 Architecture
1.2 Target groups and objectives
1.3 Technical requirements
1.3.1 Last-minute changes/corrections
1.3.2 Managed Server
1.4 Changes since the previous version
1.5 ServerView Suite link collection
1.6 Documentation for the ServerView Suite
1.7 Typographic conventions
5
7
11
11
11
11
12
12
14
15
2 Configurations on the managed servers
2.1 Configuring the BIOS and Firmware
2.1.1 BIOS settings
2.2 Configuring servers
2.3 SNMP security concept
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
2.4 Configuring SNMP services
2.4.1 Windows Server 2008/Windows Server 2012
2.4.2 For environment in which Server Core is installed
17
19
19
23
26
27
27
28
30
30
32
35
3 Installing ServerView agents
3.1 Installing and configuring agents
3.2 Installed tools
3.3 Configuring RAID
3.4 Configuring APC and Masterguard UPSs
3.5 Installing via the command line interface
3.6 Setting after installation
3.6.1 Setting an administrative user
3.6.2 For Environment in which Server Core is installed
37
38
56
60
60
63
68
68
70
ServerView Agents for Windows
3
Contents
3.7 Uninstallation
3.7.1 Windows Server 2008
3.7.2 Windows Server 2012
3.8 Restart
4
71
71
72
72
ServerView Agents for Windows
1
Introduction
ServerView Operations Manager (Operations Manager for short) is a free server
management module of the Fujitsu ServerView Suite. It is used for central
administration of industry-standard servers which run the operating systems
Windows and Linux (SUSE and Red Hat) or which serve as hosts for virtual
machines (VMs) that use hypervisors such as VMware ESXi, Citrix XenServer or
Hyper-V.
The standardized management of all servers occurs via one or more central
management stations, which you can access from any workstation in the
network that has a popular Web browser and the Java Runtime Environment.
Operations Manager controls the individual systems, including critical hardware
components such as processors, RAM, hard disks, fans and power supply. It
monitors and controls the power consumption, analyzes the performance and
utilization data and updates the server configuration.
The security concept of Operations Manager includes role-based user
management based on three underlying concepts:
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.
ServerView Agents for Windows
5
1 Introduction
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
l
l
l
l
l
6
Flexible expansion possibilities for the servers, as Operations Manager can
be easily adjusted to changed conditions
Shorter downtimes thanks to simplified error analysis
Guarantees energy-efficient and, where possible, uninterruptible server
operation
Quicker response times in the event of errors
Reduction in total cost of ownership (TCO) through efficient use of network
components and their resources
Very easy operation thanks to ergonomic software: clearly laid out,
intelligent user guidance and supportive help system
ServerView Agents for Windows
1.1 Architecture
1.1
Architecture
The architecture of ServerView Operations Manager is based on a management
console, a central management station (CMS) and the managed servers.
ServerView Agents for Windows
7
1 Introduction
Management console
A browser-based console allows you to manage the servers
and display the determined data. The following can be used
as a browser:
l
l
Microsoft Windows with Internet Explorer or Mozilla
Firefox
SUSE/Red Hat Linux with default Web browser released
with distribution
The Java Runtime Environment must also be installed.
8
ServerView Agents for Windows
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 on a
Windows or Linux virtual machine (VM).
The global user management of the ServerView Suite and of
the iRMC each centrally stores users for all Central
Management Stations (CMS) / iRMC in the directory of an
LDAP directory service. This enables you to manage the users
on a central server. The users can therefore be used by all the
CMS and iRMC that are connected to this server in the
network.
The ServerView Suite currently supports the following
directory services:
ApacheDS (running on JBoss 7).
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 14).
l
l
The data which ServerView creates and uses is stored in an
SQL database within an SQL Server. The following SQL Server
are part of the ServerView Operations Manager installation:
SQL Server 2008 R2/2005 Express under Windows Server
PostgreSQL under Linux
However, other Microsoft SQL Server databases can be used
under Windows.
l
l
ServerView Agents for Windows
9
1 Introduction
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, 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.
l
l
The ServerView agents are available for Windows, Linux,
and Citrix XenServer.
ServerView CIM Providers are available for Windows,
Linux, and VMware ESXi.
ServerView Operations Manager currently only supports
ServerView CIM providers for VMware ESXi.
How to install them is explained in the following manuals:
l
ServerView Agents for Windows
l
ServerView Agents for Linux
l
Installing ServerView ESXi CIM Provider
l
10
ServerView CIM Providers for Windows, Linux, and
VMware ESXi
ServerView Agents for Windows
1.2 Target groups and objectives
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 Windows Server
2008 and Windows Server 2012.
1.3
1.3.1
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:
l
l
1.3.2
On the DVD switch to the directory SVSSoftware – Software – ServerView
– Windows – Agents.
Start the DVD and select in the Welcome dialog ServerView Software
Products; Info under ServerView – Agents and Providers.
Managed Server
ServerView agents are available for:
l
Windows Server 2008
l
Windows Server 2008 x64
l
Windows Server 2008 R2
l
Windows Server 2012 Datacenter
l
Windows Server 2012 Standard
l
Windows Server 2012 Foundation
l
Windows Server 2012 R2 Datacenter
l
Windows Server 2012 R2 Standard
l
Windows Server 2012 R2 Foundation
l
Windows Storage Server 2012 Standard
ServerView Agents for Windows
11
1 Introduction
1.4
Changes since the previous version
This edition of the manual applies to ServerView Agents V7.10 or later and
replaces the online manual "ServerView Agents V7.00 for Windows", edition
October 2014.
The manual features the following changes and enhancements:
l
l
l
l
1.5
As of version 7.10, ServerView Operations Manager supports the directory
service ApacheDS instead of OpenDJ. Therefore the section "Architecture"
has been updated, see "Architecture" on page 7.
The section "ServerView Suite link collection" has been updated, see
"ServerView Suite link collection" on page 12.
As of ServerView Agents V7.01, the ServerView System Monitor Web
Interface is a new feature which is installed with the agents (see "Installing
and configuring agents" on page 38, "Installing via the command line
interface" on page 63, and "Installed tools" on page 56).
As of version 7.01, ServerView agents are capable of monitoring a server via
SNMPv3. Therefore the section "Configurations on the managed servers" on
page 17 has been updated. See also the new documentation "Usage of
SNMPv3 with ServerView Agents 7.01".
ServerView Suite link collection
Via the ServerView Suite link collection, Fujitsu Technology Solutions provides
you with numerous downloads and further information on the ServerView Suite
and PRIMERGY servers.
For ServerView Suite, links are offered on the following topics:
l
Forum
l
Service Desk
l
Manuals
l
Product information
l
Security information
12
ServerView Agents for Windows
1.5 ServerView Suite link collection
l
Software downloads
l
Training
The downloads include the following:
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
agents) 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 from the Fujitsu Technology
Solutions Web server.
For PRIMERGY servers, 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 on the menu bar.
This opens the start page of the ServerView Suite link collection.
2. Via the start page of the online documentation for the ServerView Suite on
the Fujitsu Technology Solutions manual server.
You access the start page of the online documentation via the
following link:
http://manuals.ts.fujitsu.com
l
In the selection list on the left, select x86 Servers.
ServerView Agents for Windows
13
1 Introduction
l
On the right, click PRIMERGY ServerView Links under Selected
documents.
This opens the start page of the ServerView Suite link collection.
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.
For an overview of the documentation to be found under ServerView Suite as
well as the filing structure, see the ServerView Suite sitemap (ServerView Suite
– Site Overview).
14
ServerView Agents for Windows
1.7 Typographic conventions
1.7
Typographic conventions
The following typographic conventions are used:
Convention Explanation
Indicates various types of risk, 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, e.g., file names
and paths.
monospace Indicates statements that are to be entered using the keyboard.
semibold
blue
Indicates a link to a related topic.
continuous
text
pink
Indicates a link to a location you have already visited.
continuous
text
<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 enter text in
uppercase, the Shift key is specified, for example, [SHIFT] + [A] for
A. If you need to press two keys at the same time, this is indicated
by a plus sign between the two key symbols.
Screenshots
Some of the screenshots are system-dependent, so some of the details shown
may differ from your system. There may also be system-specific differences in
menu options and commands.
ServerView Agents for Windows
15
16
ServerView Agents for Windows
2
Configurations 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 19.
On each server, you must make configuration settings, see "Configuring
servers" on page 23.
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 "SNMP security concept" on page 26.
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 30.
As of version 7.01, ServerView agents are capable of monitoring a server via
SNMPv3.
In order to use SNMPv3 to manage a Windows-based server
Microsoft Windows SNMP service has to be replaced. As
replacement for Microsoft Windows SNMP service the Net-SNMP
master agent is recommended (see "Usage of SNMPv3 with
ServerView Agents 7.01" description).
l
ServerView agents must be installed on each server to be managed, see
"Installing ServerView agents" on page 37.
The installation of ServerView agents on virtual machines (VMs) is
not released.
For the RXI servers there are special ServerView agents which come
with the server on the separate IA 64 ServerSupport CD.
ServerView Agents for Windows
17
2 Configurations on the managed servers
l
l
ServerView Update Manager requires the ServerView update agent to be
installed on the managed servers. The installation is described in
"ServerView Update Management" user guide.
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 %WINDIR%\system32\drivers\etc directory on
Windows systems.
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 "RAID Management" user guide.
l
ServerView Online Diagnostics
During installation of the ServerView agents for Windows, Online Diagnostics
is also installed. You can use Online Diagnostics to perform a series of
hardware tests on a managed PRIMERGY server from the remote
workstation.
l
18
When installing the ServerView agents (for Windows) in Expert mode, you
can choose whether to install additional components, including Asset CLI,
Configuration Tools, Prime Collect, ServerView System Monitor and
ServerView CIM providers.
o
ServerView System Monitor allows you to monitor and check server
information locally on the server. The ServerView System Monitor is
described in "ServerView System Monitor" user guide.
o
The ServerView CIM providers are available, to manage PRIMERGY
servers by using the CIM infrastructure.
ServerView Agents for Windows
2.1 Configuring the BIOS and Firmware
If the operating system is not support by CIM Provider, the
ServerView CIM Provider feature is not offered in the Custom
Setup step.
For details refer to the "ServerView CIM Providers for the management
of PRIMERGY servers" user guide, which describes in detail the profiles
supported by the ServerView CIM providers.
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).
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.
You must change the BIOS settings on every server.
Call the BIOS setup by rebooting the computer and pressing the F2 or DEL key at
the appropriate time in the bootup phase.
ServerView Agents for Windows
19
2 Configurations on the managed servers
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.
20
ServerView Agents for Windows
2.1 Configuring the BIOS and Firmware
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.
ServerView Agents for Windows
21
2 Configurations on the managed servers
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)
22
ServerView Agents for Windows
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 or iRMC S2/S3) 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 the F1 key.
ServerView Agents for Windows
23
2 Configurations on the managed servers
l
On Windows Server 2008: Locally on the managed servers using the Start
menu.
On the managed server select Start – All Programs – Fujitsu – ServerView
Suite – Agents – System Configuration.
You can only configure servers on which the ServerView agents for
Windows are installed.
For details on the individual server configuration dialog steps,
please refer to the online help.
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 the F1 key.
l
On Windows Server 2012: Locally on the managed servers using the Start
page:
1. There are different ways to configure the servers. One possibility is to
switch to the Apps page. To open this page click on the right upper or
lower corner on the Start page. In the displayed window select Search.
24
ServerView Agents for Windows
2.2 Configuring servers
2. Select System Configuration on the Apps page.
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.
ServerView Agents for Windows
25
2 Configurations on the managed servers
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.
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
l
l
l
l
2.3
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 RSB 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.
SNMP 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.
26
ServerView Agents for Windows
2.3 SNMP security concept
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 30.
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.
The specific entries you need to make during the installation in order to prohibit
these SET operations depend on the operating system under which the
ServerView agent is installed and on the version of the ServerView agent. For a
detailed description, "Installing ServerView agents" on page 37.
2.3.2
Prohibiting All SET operations
You can prohibit all SET operations for ServerView agents. Enter these
specifications during agent installation.
The specific entries you need to make during the installation in order to prohibit
these SET operations depend on the operating system under which the
ServerView agent is installed and on the version of the ServerView agent. For a
detailed description, "Installing ServerView agents" on page 37.
This option only applies to ServerView agents. SET operations for other
SNMP agents are not affected.
ServerView Agents for Windows
27
2 Configurations on the managed servers
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
management
station
State the specified user group during installation of
the agent
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 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 page 45.
Specifying users on the management station
On the management station you must specify in Operations Manager the user
permitted to execute SET operations on the current server. Executing a SET
operation through the management station, the user is prompted to provide
28
ServerView Agents for Windows
2.3 SNMP security concept
identification. You define the user in the Login tab in the Server Properties
window. In this example this would be SVUSER.
Figure 1: 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 Operations Manager. You a achieve a higher
degree of security, if you activate Always Ask for Password because in this case
the password is not saved.
On the left-hand side of the property 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.
How to open the property window is described in "ServerView Operations
Manager" user guide.
ServerView Agents for Windows
29
2 Configurations on the managed servers
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
Configure the security settings under Windows during installation of the agent:
l
You can allow or forbid SNMP SET operations for the ServerView agents. If
you forbid SET operations, all SNMP SETs are refused, regardless of the SET
tool used to execute them. (Shown on the management station in
Operations Manager on the tabs Restart Settings and Power ON/OFF in
the settings under Set Enabled on server).
This option only applies for ServerView agents. SET operations for
other SNMP agents are not affected.
l
l
You can turn the user authentication for SET operations on or off. You can
enter the user group to which the user must belong to be allowed to carry
out SET operations on the server.
Some SET operations (e.g. Restart/Shutdown/Abort Shutdown in the
Recovery window) cause the system to shutdown or restart. You can allow
or forbid these special SET operations.
For further information on installing the agents, see "Installing ServerView
agents" on page 37.
2.4
Configuring SNMP services
You must install and configure the SNMP services on every server to be managed
and every management station.
When you install and configure the SNMP services default values are provided.
You can modify these values for the SNMP service. If you change the values you
must also remember to change them on the management station.
Configure the following values:
30
ServerView Agents for Windows
2.4 Configuring SNMP services
l
Community string for accepting SNMP requests
The Community name (Community string) is part of every SNMP request
sent from the manager to the agent.
After installing the SNMP services, no community name is available. You can
use the community name public. This default entry is used by most SNMP
services. For reasons of security, we recommend that you change this entry.
In principle you can define an individual community for each server or server
group. Remember to make corresponding changes on the management
station.
l
l
l
Community names are case sensitive.
You can configure the community names. How to do this is
described in the White Paper “Secure PRIMERGY Server
Management“.
Rights for the community
Rights can be assigned to the community (e.g. read-only, read-write). If
you want to use the entire range of Operations Manager functions, you
must assign read-write rights to the community. You can restrict access to
certain functions by assigning (read-only) access rights to them.
The ServerView Manager only supports one community per server for SNMP
requests. For this reason you cannot configure different communities with
different access rights for a server.
l
Accept SNMP packets from selected server/any server
We recommend that you only enter the IP address of the server which is to
function as central management station (CMS). This will prevent the agent
from accepting requests from unauthorized servers.
If you limit access to dedicated CMS, you are recommended to additionally
add the managed node itself (by its own IP address or localhost) to the list
of allowed servers. This is necessary because the agents on the CMS are
requesting data from other SNMP agents on that server (required by the
report and the inventory agent).
l
Trap Destination
IP address of the management station to which the ServerView agents send
traps.
ServerView Agents for Windows
31
2 Configurations on the managed servers
l
Community string for sending traps
Here, enter the community name that is to be sent to the management
station as part of a SNMP trap. The SNMP service on the management
station must be configured so that it accepts traps with this community
name.
You should take care to ensure that installation and configuration of the
SNMP services takes place at the correct time. This depends on the
operating system you are using. SNMP services are configured and
installed before or after installing the agent depending on the
operating system being used.
2.4.1
Windows Server 2008/Windows Server 2012
When you have completed installing Windows Server 2008 or Windows Server
2012 on the server, you must perform the following steps before you install the
ServerView agents, unless you have already completed them during the system
installation:
1. Install SNMP
For installation on Windows Server 2008:
1. Select Start – Control Panel – Administrative Tools – Server
Manager.
2. In the Server Manager window, click Features. If the SNMP Services
feature is not yet listed, click Add Features.
3. Activate the SNMP Services option and click Next.
4. In the Confirm Installation Selections window click Install.
5. After successful installation click Close.
For installation on Windows Server 2012:
1. Go to the Windows Start page.
2. Launch Server Manager dashboard.
3. Click Add roles and features.
4. Select Role-based or feature-base installation option and click Next.
5. Select the server you want to manage and click Next.
6. Skip the Server Roles page and just click Next.
32
ServerView Agents for Windows
2.4 Configuring SNMP services
7. On the Features page search for the item SNMP Service.
8. If the SNMP Service feature is not installed, select it and click Next.
9. Click Install to finish the SNMP service installation.
10. You may close the installation window at any time without interrupting
the running tasks.
2. Configure SNMP
1. On Windows Server 2008: Call the Server Manager (if not already is
opened) by clicking Start – Control Panel – Administrative Tools –
Server Manager. Double-click Configuration, then click Services.
On Windows Server 2012: On the Server Manager page select Tools Services.
2. Select the service SNMP Service and then select Properties from the
context menu.
3. In the SNMP Service Properties window select the Traps tab.
4. Enter a name under Community name or confirm the default entry
public.
In some cases the default community public may not exist.
Community Name is used to control the management station access
rights. Only a management station belonging to the community
entered here can query the server. If you do not select public, then you
must also change the community entered in the management station
for the relevant server.
5. Under Trap destinations, enter the IP address or the domain name of
the management station for the specified community, using Add....
Traps are only sent to the management station entered here.
6. Click OK.
3. Configure security
1. In the SNMP Service Properties window select the Security tab.
2. Accepted community names: For each community that should have
access to the SNMP agents, the access rights can be defined.
ServerView Agents for Windows
33
2 Configurations on the managed servers
Click Add..., enter a valid community name (e.g. public) and select
Community rights as READ WRITE for SNMP GET/SET access or READ
ONLY for GET access of this community.
Set the Rights for the community to READ WRITE (in the case of a
default entry for public).
3. Accept SNMP packets from any host / Accept SNMP packets from
these hosts: You can select the managed server from which SNMP
packets are to be accepted, or you can select them all here.
SNMP is installed with the highest level of access protection. You must
therefore specify the management station, or select the option Accept
SNMP packets from any host.
Since SNMP is an open protocol without password protection,
you should only enter those management stations that
function as such. Otherwise, unauthorized network users could
alter important system parameters and thus disrupt server
operation.
4. Activate the option Send authentication trap to allow the SNMP
service sending an authentication failure trap whenever an
unauthenticated management station tries to access this server.
5. Click OK.
You may also click on the link Learn more about SNMP to get
detailed information about the SNMP configuration options.
4. Start SNMP service
Start the SNMP service under Services. Select Start from the context menu.
34
ServerView Agents for Windows
2.4 Configuring SNMP services
2.4.2
For environment in which Server Core is installed
In the local console environment of Server Core, the GUI based management
tool of Microsoft management console (MMC) is not available. You need to start
the management tool from another terminal with Windows 8, Windows 7,
Windows Server 2012, Windows Server 2008, or Windows XP and connect it
remotely. The procedure is shown below.
To configure the setting of SNMP Service, another Windows terminal (installed
other than Server Core of Windows Server 2008) is required. Prepare it in
advance.
1. On the terminal with Server Core, execute the following command, to check
whether SNMP Service is installed and has started.
> sc query SNMP
When SNMP service is not installed execute the following command, to
install the SNMP service.
> start /w ocsetup SNMP-SC
2. Log in as an administrator or a user with administrator privileges.
3. Execute the following commands at the command prompt.
For Windows Server 2008, the firewall is enabled by default. It is necessary
to permit the access to manage it remotely.
> netsh firewall set service remoteadmin enable
> netsh advfirewall set currentprofile settings
remotemanagement enable
On another Windows terminal, follow the steps below to connect Server
Core.
4. On another Windows terminal, start a command prompt and execute the
following command. During the operation, you are prompt to enter
Administrator password. Enter IP address of monitoring server (Server Core)
in "xxx.xxx.xxx.xxx" of the following command.
net use \\xxx.xxx.xxx.xxx\c$ /u:Administrator
5. Execute the following commands.
>services.msc
ServerView Agents for Windows
35
2 Configurations on the managed servers
6. Select Connect to another computer... from the Action menu.
The Select Computer window opens.
7. Enter the IP address or the machine name of the above-mentioned Server
Core server to Another computer, and click OK.
The service list of Server Core server is displayed.
Make sure that SNMP Service exists in the service.
Neither the setting nor the changes of SNMP in the local console
environment are supported.
36
ServerView Agents for Windows
3
Installing ServerView agents
When using PKI (Public Key Infrastructure) for client
authentication:
Client authentication prevents the managed server from being
accessed by a non-trusted 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.
If a newer version of the ServerView agents is already installed, you
cannot perform a downgrade installation. To downgrade, you must
uninstall any existing ServerView agents first.
Before you install the ServerView agents for Windows, it is essential that you
install and activate the SNMP services in the operating system. If you do not do
this, the management station cannot monitor the servers (for further
information, see "Configuring SNMP services" on page 30). Before you start
installation, you should carefully plan your security concept of ServerView. For
further information, see "SNMP security concept" on page 26.
ServerView Agents for Windows
37
3 Installing ServerView agents
3.1
Installing and configuring agents
Silent installation of the ServerView agents is described in "Installing via
the command line interface" on page 63.
Install the ServerView agents for Windows from the ServerView Suite DVD 2:
1. Place the ServerView Suite DVD 2 in the DVD-ROM drive. If the DVD does not
start automatically, click the start.html file in the DVD’s root directory.
2. Select the option ServerView Software Products.
3. Select the desired language in the displayed window.
4. Select ServerView – Agents and Providers.
5. Start the relevant program: ServerViewAgents_Win_i386.exe or
ServerViewAgents_Win_x64.exe
When it starts, a window opens for you to select the language for the
installation:
1. Select the language and click OK.
Select the most suitable installation for your requirements.
1. Install the agents using the commands specific to your operating system.
2. Follow the instructions on the screen.
Starting the Setup Wizard
When you have confirmed that you agree to the license conditions, the system
setup will check if an older version of ServerView agents is already installed on
the server. In this case you can perform an upgrade installation. During this, the
present configuration is saved, then the old version is deleted and the new one
is installed based on the previous configuration. In this case you cannot make
any changes.
38
ServerView Agents for Windows
3.1 Installing and configuring agents
If no agents are present on the system, the window shown below will be
opened:
Figure 2: Setup Level window
ServerView Agents for Windows
39
3 Installing ServerView agents
The setup level window offers the four default levels for agent installation:
l
Typical (High security)
l
Typical (Administrator account based security)
l
Typical (Without any security)
l
Expert (Advanced users)
If you choose one of the first three default installation modes, no further entries
are required. In these modes, the SNMP agents required for Operations
Manager and the main tools (i.e. Configuration, Maintenance, Diagnostic) will
be installed, see "Installed tools" on page 56. In these three modes the setup
uses the default values for the security level selected.
If you choose the Expert (Advanced users) mode you must enter the
installation and configuration values individually. In this mode, the wizard will
guide you through the installation and configuration values necessary.
If you do not choose any setup level, Typical (High security) is set per default.
Typical (High security)
The standard installation mode has the highest security level and does not
permit any SNMP SET operations. SET operations are also prevented if the SNMP
community used has write permissions.
You can change the configuration of the standard installation, for example by
assigning read/write rights to the community, or by creating new user groups
and users and reconfigure the agent accordingly.
Typical (Administrator account based security)
In this standard installation mode, SNMP SET operations are permitted.
Management station SET operations are password protected and have local
administrator and user authentication. Local passwords and administrator access
rights. However, there is no password protected security for SET operations which
have been run using other SNMP tools. The SNMP community which is used
requires write permissions to execute SET operations. Otherwise the SET
operation will be prevented by the security mechanisms of the operating system.
40
ServerView Agents for Windows
3.1 Installing and configuring agents
You can change the configuration of the standard installation, for example by
setting up new user groups and users with operating system-specific resources or
reconfigure the agent with the configuration tool Agents Configuration.
Typical (Without any security)
In this standard installation mode, SNMP set operations are permitted without
any password protected security further user authentication. This installation
mode should only be used on secure internal networks. The SNMP community
which is used requires write permissions to execute SET operations. Otherwise
the SET operation will be prevented by the security mechanisms of the operating
system.
Expert (Advanced users)
The expert mode provides the following options:
l
l
l
l
Select other components.
Configure agent packages individually. Here you can individually configure
SNMP trap forwarding, SNMP security settings and system shutdown
behavior.
Pre-configure the remote management controller. During installation can
define the main settings of the remote manager controller and then
transfer these to the system during setup.
Create a configuration file for automatic installation (i.e. “unattended
setup”) at a later date. You can save your settings for the management
controller configuration and agent configuration in this file and then use
these later for an unattended setup.
ServerView Agents for Windows
41
3 Installing ServerView agents
Figure 3: Expert Settings window
Agents ...
Opens a window where you can change the ServerView agent configuration.
For more information, see the next section below.
Restrict SNMP access to local system
This option defines the value Restrict access to these host only in the
SNMP settings and enters the LOOPBACK adapter. If you select this option
you will not be able to access the system from outside. This option only
makes sense if the Event Manager is installed on the server and if the server
is not being used as a management station.
Save file ...
Opens a window where you can enter the path for saving the Setup.pre
configuration file.
This file will be used for automatic installations (“unattended setup”) (see
also "Installing via the command line interface" on page 63).
42
ServerView Agents for Windows
3.1 Installing and configuring agents
The configuration file must be in the same directory as the
Setup.exe.
< Back
Returns you to the previous window.
Next >
Displays the next window.
Cancel
Cancels the installation.
Due to architectual changes the launch of the System Configuration
Tool (via the System ... button) is no longer available within the setup
wizard. To configure the system settings now, finish the agents setup
and launch the System Configuration utility (see "Configuring servers"
on page 23).
Configuring ServerView agents
To start configuration of the ServerView agents, click the Agents ... button. The
ServerView SNMP agents settings (offline) window opens.
This window has the following tabs.
l
Trap Forwarding tab
l
System Shutdown tab
l
Security Settings tab
l
Threshold Monitoring tab
ServerView Agents for Windows
43
3 Installing ServerView agents
Trap Forwarding tab
All SNMP traps generated by ServerView agents can be reported to the system’s
event log or forwarded as an administrator alert message. Forwarding depends
on the weight assigned to the trap. The following weights are available:
l
critical (for critical traps)
l
major (for important traps)
l
minor (for less important traps)
l
informational (for informative traps)
Weighting for the event log types is as follows:
Trap weighting
Event log type
critical and major traps Error
minor traps
Warning
informational traps
Information
The reporting service on the server must be configured and running before a trap
can be forwarded to the administrator. The message targets must already be
defined in the properties of Windows Server Manager.
The source name of the events reported by ServerView agents is ServerView
Agents. ServerView agents report to the Application log.
44
ServerView Agents for Windows
3.1 Installing and configuring agents
Figure 4: Trap Forwarding tab
Use the Trap Forwarding tab to select which types of SNMP traps will be
forwarded. In the default setting, critical and major traps will be reported to the
system event log.
System Shutdown tab
ServerView agents can initiate a system shutdown. The shutdown can be
triggered by an operation on the management station or by the occurrence of a
system error.
By default, ServerView agents always initiate a “soft” shutdown, i.e. the user is
asked to close any running applications and then to explicitly confirm the
shutdown. After a preset time delay has elapsed, the ServerView agents will
initiate a hard shutdown and shutdown the operating system even though the
shutdown has not been explicitly confirmed and not all the data has been saved
to the hard disk. The default value for this delay is 120 seconds. If you have to
save large amounts of data to the hard drive you should increase this value
accordingly.
ServerView Agents for Windows
45
3 Installing ServerView agents
You can choose to start an application (a shutdown job) before the soft
shutdown is initiated.
Figure 5: System Shutdown tab
On the System Shutdown tab you can define the following shutdown settings:
Start Delay (sec)
This setting defines the delay (in seconds) which must elapse before the
shutdown is started. During this delay the shutdown can be interrupted from
the system console.
Timeout (sec)
This setting defines the time interval (in seconds) during which the soft
shutdown (with data saving) must be completed. When this time period
elapses, the system will start a hard shutdown without saving any data.
Executable Path
Path name of an executable program or script.The path may also contain
environment variables, e.g. %SystemRoot%.
46
ServerView Agents for Windows
3.1 Installing and configuring agents
Working Directory
Indicates the working directory for the job.
Maximum execution time (sec)
Indicates the maximum duration of the job. The shutdown will be started
once the maximum time set in this field has elapsed.
Security Settings tab
The ServerView agents used in combination with management station provide a
complete security concept restricting access to SNMP SET operations on the
server. You can prevent access to SET operations or, using user authentication
protection, enable access to these operations when performed together with
management station.
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.
This user authentication system only operates with Operations Manager
on management station. It does not work with other SNMP tools.
ServerView Agents for Windows
47
3 Installing ServerView agents
You can define the security settings on the tab shown below:
Figure 6: Security Settings tab
Enable Password Protection
This checkbox enables/disables the user authentication routine protecting
access to SNMP SET operations.
User Group
Indicates the user group to which the user must belong in order to perform
SET operations on the server. Here, you can create a user group of your
choice.
If the user group does not exist already, you need to create this group using
methods specific to your operating system.
Do not assign a user to a user group at this point. Wait until later. You assign
a user to a user group at the operating system level, either before or after
installing the agent. For security reasons, we recommend that you enter
one user only.
48
ServerView Agents for Windows
3.1 Installing and configuring agents
If you do not enter a name in User Group, only local system
administrators will be allowed access to SET operations on the
server.
When installing the ServerView agents by using ServerView
Installations Manager, User Groupis set to "FUJITSU SVUSER".
Enable ServerView SET operations on server
Enables SNMP SET operations by ServerView agents . If you forbid SET
operations, this will prevent access to all SNMP SETs irrespective of the tool
used to run the SET.
This option is for ServerView agents only. This option has no effect
on other SNMP agents.
Enable remote shutdown via SNMP request
Some SET operations trigger a shutdown or a system restart. Use this
checkbox to enable/disable these special types of SET operation.
ServerView Agents for Windows
49
3 Installing ServerView agents
Threshold Monitoring tab
Via the Threshold Monitoring you can activate or deactivate threshold
monitoring for the Threshold Manager.
Figure 7: Threshold Monitoring tab
Selecting the destination folder
Confirm the agent configuration in the Expert Settings window by clicking OK.
Next, go to the Destination Folder window to change the installation folder.
50
ServerView Agents for Windows
3.1 Installing and configuring agents
Figure 8: Destination Folder window
By default the ServerView agent is installed by default in the installation
directory. You can change the folder via the Change... button.
If you use the Performance Manager, report data is stored by default in the
installation directory. However, this data can easily amount to 50 Mbytes or
more, depending on the application. You therefore have the option of selecting
a different directory with sufficient space via the Change... button.
Defining the setup type
Confirm the agent configuration in the Expert Settings window by clicking OK.
Next, go to the Setup Type window to select the setup type.
ServerView Agents for Windows
51
3 Installing ServerView agents
Figure 9: Setup Type window
Select the setup type you require.
Complete
Select this option to start an installation where all the features are installed.
This type requires the most memory space.
Custom
Select this option if you want to select individual features and define the
path. You can also specify the storage location for the report data and the
port for the ServerView Remote Connector service.
52
ServerView Agents for Windows
3.1 Installing and configuring agents
If you select Custom and then Next, the following window opens:
Figure 10: Custom Setup window
This window offers the following features for selection:
Feature
Description
Standard
Agents
SNMP agents required for Operations Manager.
S.M.A.R.T.
Support
S.M.A.R.T. support for event monitoring.
Microsoft SMS Software for automatically creating MIF files for Microsoft SMS V
Integration 1.2 and V 2.0.
MIB Files
ServerView MIB files.
Configuration Tools for agent and system configuration.
Tools
ServerView Agents for Windows
53
3 Installing ServerView agents
Feature
Description
Support Tools Tools for service technician
Diagnostic
Tools
Various diagnostic tools (e.g. for installation testing), for support
purposes only.
System
Tool for system monitoring (Web-based).
Monitor Web
Interface
System
Monitor
Tool for system monitoring (local tool).
Windows
Integration into Microsoft Windows Management (WMI).
Management
Integration
Virtualization Provides performance data for virtual machines (Xen, Hyper-V,
Management VMWare).
Agent
HP Systems
Integration
Integration into HP SIM (System Insight Manager)
Asset CLI
Custom line utility for reading system asset information
PrimeCollect Tool for collecting and storing information about the hardware
and software of PRIMERGY servers.
Help Files
Help files
Remote
Connector
Service
Provides HTTP-based services.
Server
Control
Service
Basic service required.
54
ServerView Agents for Windows
3.1 Installing and configuring agents
Feature
Description
CIM Provider If the operating system is not support by CIM Provider, the
ServerView CIM provider feature is not offered in the Custom
Setup step.
Installs the ServerView CIM providers, to manage PRIMERGY
servers by using the CIM infrastructure, see also "ServerView CIM
Providers for the management of PRIMERGY servers" user guide.
Once you have selected the components, the following window opens:
Click Install to start the installation.
ServerView Agents for Windows
55
3 Installing ServerView agents
3.2
Installed tools
l
On Windows Server 2008: After successful installation, different tools are
available under:
Start – Programs – Fujitsu – ServerView Suite – Agents
l
On Windows Server 2012: After successful installation, different tools are
available on the Apps page. Via the Pin to Start icon you can move
applications to the Start page.
On the Start page you can build applications groups. Select the relevant
applications and click on the minus sign on the right below.
56
ServerView Agents for Windows
3.2 Installed tools
A dialog opens to enter a name for the group. The new group is displayed
on the Start page, e.g. group ServerView.
After installation it takes some time to complete the configuration. As a
result you might find that when you query the configuration, the
system will continue to display the old values.
ServerView Agents for Windows
57
3 Installing ServerView agents
Maintenance Tools
CPU
Status
Shows the CPU overview.
Memory Displays a detailed list of all the memory modules installed. Use this
Status tool to reset the error counters of memory modules.
We recommend that you reset the error counter after having changed
a memory module.
*)
Resets the counter to zero (total time ON, total time OFF, total
Counters number of system power up cycles).
We recommend that you reset the counter after having changed the
CMOS battery.
*) For PRIMERGY only
Diagnostic Tools menu
Diagnostics Report
Tests the installation of the ServerView features.
Restart Agents
Restarts the ServerView agents.
*) System Message Log
Viewer
Displays the error message log of the service
processor.
*) For PRIMERGY only
PrimeCollect
Tool for collecting and storing information about the hardware and software of
PRIMERGY servers.
Agents Configuration
Enables configuration of the ServerView agents.
System Configuration
Enables configuration of the server firmware.
58
ServerView Agents for Windows
3.2 Installed tools
System Monitor Web Interface/System Monitor
Via this entry you start the ServerView System Monitor Web interface or the local
ServerView System Monitor. The ServerView System Monitor allows you to
monitor and check the following server information locally on your server:
l
l
l
Environment information, including fan and temperature sensor
information.
Power supply information.
Mass storage information. This information is only available if ServerView
RAID Manager is installed on the system.
l
System board information.
l
Network information.
l
Driver monitor information.
l
Update Status information.
l
The contents of the System Event log (SEL) (only ServerView System Monitor
Web Interface) .
For a description of the System Monitor, see "ServerView System Monitor" user
guide.
ServerView Agents for Windows
59
3 Installing ServerView agents
3.3
Configuring RAID
For the RAID configuration you can use ServerView RAID Manager, which you will
find on the ServerView Suite DVD 2 under RAID Manager.
3.4
Configuring APC and Masterguard UPSs
The following description is only valid for PRIMERGY.
You must configure the uninterruptible power supply (UPS) connected to the
system or the additional cabinet if you want to:
l
Display the UPS in Operations Manager.
l
Display the current UPS status.
To display the UPS status you must install a UPS SNMP agent on the server. The
SNMP agent will be supplied by the UPS manufacturer. For UPS with a web card,
the SNMP agent necessary should be pre-installed on the web card.
In order to be able to communicate with the UPS SNMP agents, Operations
Manager requires the following items of data:
l
Manufacturer
l
Model designation
l
Basis object identifier (OID) of the SNMP agents.
l
Name or IP address of the host.
You must give an IP address because this is necessary for SNMP communications
with the agents. Enter the IP address of the server and the UPS.
For UPS models made by APC and Masterguard there is no need to enter the
Basis OID for the SNMP agents. Operations Manager recognizes the model and
manufacturer name of these two models and automatically assigns the relevant
SNMP OIDs. For these types we recommend that you use the default settings
provided and only change the IP address.
Installing UPS applications
If you want the existing UPS configuration to be displayed in
ServerView/Operations Manager, first you must install the PowerChuteBusiness
60
ServerView Agents for Windows
3.4 Configuring APC and Masterguard UPSs
Edition application (for APC UPS with serial connection) or upsmon (for
Masterguard UPS) on the management station. During the installation, the
appropriate entries will be made in the registry (see also the section concerning
APC UPS in the Operations Manager user guide).
The PowerChuteBusiness Edition is available on the APC CD. upsmon
is an independent product.
Configuring a UPS under Windows Server 2008/2012
You can configure a UPS locally on managed Windows-based servers using the
Start menu.
1. Windows Server 2008: On the managed server select:
Start – All Programs – Fujitsu – ServerView Suite – Agents – System
Configuration
Windows Server 2012: On the managed server by using the Start page.
There are different ways to start the configuration. One possibility is to
switch to the Apps page. To open this page click on the right upper or lower
corner on the Start page. In the displayed window select Search.
2. On the System Configuration start page select the features and click Go....
ServerView Agents for Windows
61
3 Installing ServerView agents
3. In the tree view select UPS Integration.
Figure 11: UPS Integration
For details on the parameters, please refer to the online help of the Server
Configuration Manager.
To access the online help, proceed as follows:
1. Click in the window area currently displaying this dialog step.
2. Press the F1 key.
62
ServerView Agents for Windows
3.5 Installing via the command line interface
3.5
Installing via the command line interface
You can install the agents via a command in the command line. Operations
Manager also allows the silent installation of agents. With the help of the silent
installation, Software sharing systems such as Microsoft System Management
Server (SMS) can share software automatically. The simplest form of software
sharing is the unattended execution of setups with standard configuration. You
are also able to fit the installation to your needs with the help of environment
variables.
The ServerView agent setup is based on Microsoft Windows Installer technology.
The setup data is found in the installer database, ServerView Agents.msi. The
setup data are packed in Data1.cab.
Command syntax of Setup.exe
Switch to the command-line level and enter the Setup command on the highest
level of the installation directory as follows:
Setup.exe [/x]|[[/a][/s][/V]]
The options have the following meaning:
/x
(Uninstalled mode)
The setup uninstalls the product.
/a
(Administrative mode)
The setup is run in administrator mode. In this mode all data files are
extracted and placed in a directory. No registry entries or connections are
made.
/s
(Silent mode)
Suppresses all messages on the screen. The installation is completed in the
background.
ServerView Agents for Windows
63
3 Installing ServerView agents
/V
(Microsoft Installer Option)
Allows the transfer of arguments directly to the Microsoft Installer
(MSIEXEC.EXE).
Microsoft installer properties
You can influence the installation by setting properties. The name of the
property is always written in capital letters. Values are case sensitive.
INSTALLDIR
Resets the standard installation directory.
Valid path names, e.g.:
INSTALLDIR=C:\Programs\Fujitsu\ServerView Suite\ServerView agents
Standard: System Folder
REBOOT
Influences actions when the system reboots after the installation. For
example, this option prevents a system from rebooting after an automatic
installation if components can only be changed after the restart. Possible
values:
F
The system always reboots.
R
The system never reboots.
SETUP_LEVEL
Sets the Setup mode for installation. Possible values:
LevelHigh
(Standard)
Installs in setup mode: Typical (High Security).
The installation with the highest level of security, allows no SNMP SET
operations.
64
ServerView Agents for Windows
3.5 Installing via the command line interface
LevelAdmin
Installs in setup mode: Typical (Administrator account based
security).
ServerView SNMP SET operations are checked for local administrator
rights and password.
LevelAll
Installs in setup mode: Typical (Without any Security).
ServerView SNMP SET operations are allowing without any checks. This
installation mode is a sensible choice for secured internal networks.
LevelUser
Installs in setup mode: Expert (Advanced users)
ADDLOCAL
States which features are to be installed. If you do not choose any features,
a standard selection is installed. If you wish to make an individual choice,
you must state the variables with ADDLOCAL. The feature names are listed
separated by commas. Possible values:
All
Installs all modules.
ServerControl
(Standard, must always be installed)
Installs the ServerView Base Service.
SnmpAgents
(Standard)
Installs the ServerView agents.
MIBFiles
Installs the ServerView agent MIB data.
SmartSupport
(Standard)
Installs ServerView S.M.A.R.T. support.
ServerView Agents for Windows
65
3 Installing ServerView agents
Configuration
(Standard)
Installs the ServerView Configurations Tools.
Diagnostic
(Standard)
Installs the ServerView Diagnostic Tools.
Maintenance
(Standard)
Installs the Support Tools.
SMS
Installs the ServerView Integration in SMS.
WMI
Installs the ServerView Integration in WMI.
WCS
Installs the ServerView Remote Connector.
AssetCLI
Installs the ServerView Asset CLI tool.
OnlineDiagnostic
Installs the Online Diagnostic tool.
PrimeCollect
Installs the PrimeCollect tool.
Help
ServerView help files.
SSM
Installs the ServerView System Monitor (local) for system monitoring.
SSMWeb
(Standard)
Installs the ServerView System Monitor Web Interface for system
monitoring.
CIM
Installs the ServerView CIM provider.
66
ServerView Agents for Windows
3.5 Installing via the command line interface
HPSIM
Installs the ServerView Integration in HP SIM (HP Systems Insight
Manager).
Example
ADDLOCAL=ServerControl,MIBFiles,WMI
The program features ServerView Base Service, ServerView agents MIB
data and ServerView Integration in WMI are installed.
Installation with a configuration file
To set up a configuration file proceed as follows:
1. Start the Setup Wizard.
2. Select the Expert (Advanced users) mode.
3. In the Expert Settings window configure the settings for the agents via the
Agents... button.
4. Click Save file ... button, to select the directory where the configuration file
Setup.pre should be saved. The configuration file must be saved in the
same directory as the Microsoft Installer data file (ServerView Agents.msi).
The configuration data is taken from the file onto the system by a Setup.exe
command, regardless of which setup mode you have chosen.
Examples of Setup.exe
Setup.exe /s/V“/qn“
Automatic installation of the standard configuration. The setup mode is
Typical (High security), i.e. no SNMP SET operations are allowed, critical
traps are entered in the system log.
The installation path is the folder of the system (e.g. C:\Programs\).
The following features are installed:
l
ServerView Base Service
l
ServerView agent
l
ServerView Configuration Tools
l
ServerView Diagnostics Tools
l
ServerView Maintenance Tools
ServerView Agents for Windows
67
3 Installing ServerView agents
l
ServerView Remote Connector
ServerView PrimeCollect
Setup.exe /s/V“/qn SETUP_LEVEL=LevelAll
INSTALLDIR=“C:\My Programs“
l
Appropriate automatic installation in setup mode: Typical (Without any
security) and changed installation path.
Setup.exe /s/V“/qn ADDLOCAL=ServerControl,WMI
INSTALLDIR=“C:\My Programs“
Automatic installation of the basic features for integration in the Windows
Management Instrumentation (WMI) with altered installation path.
Setup.exe /s/V“/qn ADDLOCAL=ServerControl,WMI
Reboot=R“
Automatic minimal installation for integration in Windows Management
Instrumentation (WMI) without system reboot.
3.6
Setting after installation
After the installation of ServerView agents or CIM providers for Windows, perform
the following settings to ensure that agent operates properly.
3.6.1
Setting an administrative user
Only users belonging to the group (FUJITSU SVUSER) 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. At this time, the administrative user's name and password
are required to be input. Follow the steps below to set an administrative user.
The FUJITSU SVUSER group and users belonging to the group are not created
automatically. Create a group each monitored server and add the ServerView
administrative user to the FUJITSU SVUSER group.
An administrative user in ServerView means a user who belongs to the FUJITSU
SVUSER group. In Windows Servers, administrative privileges are not given if the
password is not set for the administrative user account. Be sure to set the
password.
68
ServerView Agents for Windows
3.6 Setting after installation
Even when a "global" group is added to the FUJITSU SVUSER group,
administrative privileges are not given to the users in the added group. Add only
users to the FUJITSU SVUSER group. If an administrative user is set for another
group than FUJITSU SVUSER, the logon immediately after starting the program
may fail. In this case, click Cancel to exit the logon window.
Then, set the logon settings again on the Login tab of Properties on the server.
1. Open Control Panel and double-click the Administrative Tools icon.
2. Double-click the Computer Management icon. The Computer
Management window opens.
3. Select Local Users and Groups – Groups from the left tree view.
4. Click the Action menu and select New Group....
5. Enter FUJITSU SVUSER in Group name and click Create. A new group is
created. Click Close to close the New Group window.
6. Select Local Users and Groups – Users from the left tree view.
7. Click the Action menu and select New User....
8. Set the necessary items and click Create. A new user is created. Click Close
to close the New User window.
9. Select the added user and click the Action menu and select Properties.
10. Click the Member of tab and click Add. The Select Groups window opens.
11. Click Properties.
12. Click Search Now.
13. Select the FUJITSU SVUSER groups, and click OK. The Select Groups
window opens again.
14. Click OK. The display returns to the user Properties window. Confirm that
FUJITSU SVUSER is added to Member of, and click OK.
15. Click OK. Close the Computer Management window.
ServerView Agents for Windows
69
3 Installing ServerView agents
3.6.2
For Environment in which Server Core is installed
In the local console environment of Server Core, the GUI based management
tool of Microsoft management console (MMC) is not available. Execute the
following command to set the group and administrative user.
1. Execute the following commands to create the FUJITSU SVUSER group.
>net localgroup "FUJITSU SVUSER" /add
2. Create an administrative user and set a password.
>net user <user name> /add *
After executing the command, you are prompted to enter a password.
3. Add the newly created user to the FUJITSU SVUSER group.
>net localgroup "FUJITSU SVUSER" /add <user name>
To refer to or delete the created group and administrative user, execute the
following commands.
To refer to the group:
>net localgroup "FUJITSU SVUSER"
To refer to the administrative user:
>net user <user name> /
To delete the group:
>net localgroup "FUJITSU SVUSER" /delete
To delete the administrative user:
>net user <user name> /delete
70
ServerView Agents for Windows
3.7 Uninstallation
3.7
Uninstallation
This section explains how to uninstall the ServerView Windows agent.
The items saved on the server's BIOS are not restored even when ServerView
Windows agent is uninstalled. Restore the settings to the original state, and then
uninstall ServerView Windows agent.
Make sure to do the following before uninstalling ServerView Windows agent.
1. Disable Software Watchdog, BOOT Watchdog and Power ON/OFF settings.
2. If threshold monitoring and report creation are applied by Performance
Manager, cancel these performances to the server.
To uninstall ServerView Windows agent, perform the following steps.
You do not need to restart Windows after uninstalling ServerView
Windows agent.
3.7.1
Windows Server 2008
1. Log in as an administrator or a user with administrator privileges.
2. Exit all running applications.
3. Open Control Panel and click Programs – Programs and Features.
4. Select Fujitsu ServerView Agents and click Uninstall.
ServerView Windows Agent will be uninstalled.
For Environment in which Server Core is Installed
1. Insert the PRIMERGY Startup Disc.
2. Execute the following file.
<CD/DVD
drive>:\PROGRAMS\Japanese2\Svmanage\WinSVAgent\Unagents.bat
ServerView Agents for Windows
71
3 Installing ServerView agents
3.7.2
Windows Server 2012
1. Log in as an administrator or a user with administrator privileges.
2. Go to the Windows Start page.
3. Launch the Control Panel.
4. In section Programs click Uninstall a program.
5. Select Fujitsu Server View Agents x64 Edition and click Uninstall.
ServerView Windows Agent will be uninstalled.
3.8
Restart
The service name of the ServerView agents is ServerView Server Control.
If this service was restarted, you must also restart the SNMP service.
We recommend using Restart Agents from the Diagnostic Tools menu. This
tool can restart both the ServerView Server Control service and the SNMP
service.
72
ServerView Agents for Windows