ServerView Agents 8.30 for Windows - Fujitsu...

Installation and User Guide - English

FUJITSU Software ServerView Suite

ServerView Agents V8.40 for Windows(Windows Server 2008 / 2012 / 2016)

Edition June 2018

Comments… Suggestions… Corrections…The User Documentation Department would like to know your opinion of this manual. Yourfeedback helps us optimize our documentation to suit your individual needs.

Feel free to send us your comments by e-mail [email protected].

Certified documentation according to DIN EN ISO 9001:2008To ensure a consistently high quality standard and user-friendliness, this documentation wascreated to meet the regulations of a quality management system which complies with therequirements of the standard DIN EN ISO 9001:2008.

cognitas. Gesellschaft für Technik-Dokumentation mbH

www.cognitas.de

Copyright and trademarksCopyright 1998 - 2018 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 aretrademarks of the Apache Software Foundation.

mailto:[email protected]

http://www.cognitas.de/

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 81.3.2 Managed Server 8

1.4 What's new 9

1.5 ServerView Suite link collection 10

1.6 Documentation for the ServerView Suite 11

1.7 Notational conventions 12

2 Configurations on the managed servers 13

2.1 Configuring the BIOS and Firmware 14

2.1.1 BIOS settings 15

2.2 Configuring servers 17

2.3 SNMP security concept 20

2.3.1 Prohibiting specific SET operations 202.3.2 Prohibiting All SET operations 202.3.3 SET Operations with user authentication 212.3.4 Operating system-specific characteristics of the SNMP agents 22

2.4 Configuring SNMP services 23

2.4.1 Windows Server 2008 / 2012 / 2016 252.4.2 For environment in which Server Core is installed 27

3 Installing ServerView Agents 29

3.1 Installing and configuring agents 29

3.2 Installed tools 42

3.3 Configuring RAID 45

3.4 Configuring APC and Masterguard UPSs 45

3.5 Installing via the command line interface 47

3.6 Setting after installation 51

3.6.1 Setting an administrative user 523.6.2 For Environment in which Server Core is installed 53

ServerView Agents for Windows 3

Inhalt

3.7 Uninstalling ServerView Agents 53

3.7.1 Windows Server 2008 543.7.2 Windows Server 2012 / 2016 54

3.8 Restart 54


1 IntroductionServerView Operations Manager (Operations Manager for short) is a free servermanagement module of the Fujitsu ServerView Suite. It is used for central administrationof industry-standard servers which run the operating systems Windows and Linux (SUSEand Red Hat) or which serve as hosts for virtual machines (VMs) that use the hypervisorsVMware ESXi or Hyper-V installed.

The standardized management of all servers occurs via one or more central managementstations, which you can access from any workstation in the network that has a popularweb browser and the Java Runtime Environment.

Operations Manager controls the individual systems, including critical hardwarecomponents such as processors, RAM, hard disks, fans and power supply. It monitors andcontrols the power consumption, analyzes the performance and utilization data andupdates the server configuration.

The security concept of Operations Manager includes role-based user management basedon three underlying concepts:

l Global user management via an LDAP directory service (Lightweight Directory AccessProtocol)

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 yourcompany by assigning a task-oriented authorization profile to each role.

SSO means that you only need to authenticate yourself once. Once you have done thissuccessfully, you are given access to all ServerView components without having to sign onto any of them again.

Server management with Operations Manager offers important benefits to operators of acomprehensive 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 easilyadjusted 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


1.1 Architecture

l Reduction in total cost of ownership (TCO) through efficient use of networkcomponents and their resources

l Very easy operation thanks to ergonomic software: clearly laid out, intelligent userguidance and supportive help system

1.1 ArchitectureThe architecture of ServerView Operations Manager is based on a management console, acentral 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 anddisplay the determined data. All you need is a popular web browser todownload the starter file for Java Web Start. The following can be used as abrowser:

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.


1.1 Architecture

Central management station (CMS)

On the CMS ServerView Operations Manager is installed. The optionalcomponents of the ServerView Suite, such as Virtual IO-Manager, are alsoinstalled on the CMS and integrated in Operations Manager.

The CMS (and thus ServerView Operations Manager with its components)may also run in Windows-based or Linux-based virtual machines (VM)that use hypervisors such as VMware ESXi, Microsoft Hyper-V, and Red HatEnterprise KMV.

The global user management of the ServerView Suite and of the iRMC each centrally storesusers for all CMS / iRMC in the directory of an LDAP directory service. This enables you tomanage the users on a central server. The users can therefore be used by all the CMS andiRMC 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 chooseServerView’s internal directory service (ApacheDS) or an existing external directory service(Active directory). For further information about the use of directory services withServerView, see the "User Management in ServerView" user guide.

The data which ServerView creates and uses is stored in an SQL database within an SQLServer. The following SQL Server are part of the ServerView Operations Managerinstallation:

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 CMS.

How to install ServerView Operations Manager is explained in the following manuals:

l Installing ServerView Operations Manager Software under Windowsl Installing ServerView Operations Manager Software under Linux

Managed servers

On the managed servers, ServerView Agents, ServerView CIM Providers, orServerView Agentless Service should be installed, which supply the informationto the CMS. ServerView RAID Manager and ServerView Update Agent should bealso installed on the managed servers.

The installation of ServerView Agents on virtual machines (VMs) is not released.


http://manuals.ts.fujitsu.com/index.php?id=5406-5873-5925-5928

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 forVMware ESXi.

How to install them is explained in the following manuals:

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

1.2 Target groups and objectivesThis manual is intended for system administrators, network administrators and servicetechnicians that have a basic knowledge of hardware and software. The manual describesthe installation of the ServerView Agents for Windows Server 2008, Windows Server 2012,and Windows Server 2016.

1.3 Technical requirements

1.3.1 Last-minute changes/corrections

Any last-minute changes/corrections of the technical requirements can be found in theReadme file on the ServerView Suite DVD 2. You have the following options:

l On the DVD switch to the directory SVSSoftware – Software – ServerView – Windows– Agents.

l Start the DVD and select in the Welcome dialog ServerView Software Products; Infounder ServerView – Agents and Providers.

1.3.2 Managed Server

ServerView Agents are available for:

l Windows Server 2008 (x64) with SP2

l Windows Server 2008 Enterprise Edition (x64) with SP2

l Windows Server 2008 Datacenter Edition (x64) with SP2

l Windows Server 2008 Core installations with SP2


1.4 What's new

l Windows Server 2008 R2

l Windows Server 2008 R2 Enterprise Edition

l Windows Server 2008 R2 Datacenter Edition

l Windows Server 2008 R2 Core installations

l Windows Server 2012 Standard

l Windows Server 2012 Datacenter

l Windows Server 2012 Essentials

l Windows Server 2012 Foundation

l Windows Hyper-V Server 2012

l Windows Storage Server 2012

l Windows Server 2012 R2 Standard

l Windows Server 2012 R2 Datacenter

l Windows Server 2012 R2 Foundation

l Windows Hyper-V Server 2012 R2

l Windows Storage Server 2012 R2

l Windows Server 2016 Standard

l Windows Server 2016 Datacenter

l Windows Server 2016 Essentials

l Windows Server 2016 RS3 Standard

l Windows Server 2016 RS3 Datacenter

l Windows Server 2016 RS3 Essentials

l Windows Server 2016 RS4 Standard

l Windows Server 2016 RS4 Datacenter

l Windows Server 2016 RS4 Essentials

1.4 What's newThis edition of the manual applies to ServerView Agents V8.40 or later and replaces theonline manual "ServerView Agents V8.30 for Windows", edition March 2018.

The manual features the following changes and enhancements:

l The technical requirements has been updated, see "Technical requirements" on page 8.

l The section "Architecture" on page 6 has been updated.


1.5 ServerView Suite link collection

1.5 ServerView Suite link collectionVia the ServerView Suite link collection, Fujitsu provides you with numerous downloadsand 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 Readmefiles.

o Information files and update sets for system software components (BIOS,firmware, drivers, ServerView Agents and ServerView Update Agent) forupdating the PRIMERGY servers via ServerView Update Manager or for locallyupdating 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.

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 Fujitsumanual server.


1.6 Documentation for the ServerView Suite

You access the start page of the online documentation via the followinglink:

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 In the start window of the ServerView Suite DVD 2, select the option ServerViewSoftware Products.

l On the menu bar select Links.

This opens the start page of the ServerView Suite link collection.

1.6 Documentation for the ServerView SuiteThe documentation can be downloaded free of charge from the Internet. You will find theonline 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 thefiling 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.


http://manuals.ts.fujitsu.com/

http://manuals.ts.fujitsu.com/

http://manuals.ts.fujitsu.com/files/html/primergy/svs-sitemap/sitemap_emea_en/index.html

1.7 Notational conventions

1.7 Notational conventionsThe following notational conventions are used in this manual:

Notationalconventions

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, forexample file names and paths.

monospacesemibold

Indicates statements that are to be entered usingthe keyboard.

blue continuoustext

Indicates a link to a related topic.

purple continuoustext

Indicates a link to a location you have alreadyvisited.

<abc> Indicates variables which must be replaced withreal values.

[abc] Indicates options that can be specified (syntax).

[key] Indicates a key on your keyboard. If you need toexplicitly enter text in uppercase, the Shift key isspecified, for example [Shift] + [A] for A. If you needto press two keys at the same time, this is indicatedby a plus sign between the two key symbols.

Screenshots

The screenshots are to some degree system-dependent and consequently will notnecessarily match the output on your system in all the details. The menus and theircommands can also contain system-dependent differences.


2 Configurations on the managed serversBefore starting the Operations Manager, the following preparations must be made on themanaged server:

l Only for PRIMERGY: Certain settings must be made in the BIOS on each managedserver, see "Configuring the BIOS and Firmware" on page 14.

On each server, you must make configuration settings, see "Configuring servers" onpage 17.

l ServerView offers a sophisticated security concept. Before you install the agents, youshould study the information regarding the security concept thoroughly and choosethe concept that best suits your security requirements. You may need to makeappropriate arrangements prior to installing the agent. This is described in "SNMPsecurity concept" on page 20.

l You must install and configure the SNMP services of the current operating system oneach managed server and the management station. If you do not do this, themanagement station will be unable to monitor the servers. The SNMP services must beactivated either before or after installing the agents, depending on the operatingsystem. This is described in "Configuring SNMP services" on page 23.

l 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 MicrosoftWindows SNMP service has to be replaced. As replacement for MicrosoftWindows SNMP service the Net-SNMP master agent is recommended. Fordetailed information, see the ServerView Suite SNMPv3 documentation.

l ServerView Agents must be installed on each server to be managed, see "InstallingServerView Agents" on page 29.

The installation of ServerView Agents on virtual machines (VMs) is notreleased.

For the RXI servers there are special ServerView Agents which come with theserver on the separate IA 64 ServerSupport CD.

l ServerView Update Manager requires the ServerView Update Agent to be installed onthe managed servers. The installation is described in the "ServerView UpdateManagement" user guide.

l If the ServerView Operations Manager on the central management station isconfigured to be accessed using a name instead of an IP address, you must ensure


2.1 Configuring the BIOS and Firmware

that the central management station is accessible from the managed node by thisaddress. This is preferably accomplished by an appropriate entry in DNS. If there is noDNS available, then you must provide an appropriate entry in the hosts file on themanaged node. You will find this file in the%WINDIR%\system32\drivers\etc directoryon Windows systems.

Additional installations on the managed servers

l ServerView RAID Manager

ServerView RAID Manager offers standardized administration and management ofhard disks for PRIMERGY servers. Unless the ServerView RAID Manager is installed, noinformation about RAID drives and their statuses will be available.

The installation is described in the "RAID Management" user guide.

l ServerView Online Diagnostics

During installation of the ServerView Agents for Windows, Online Diagnostics is alsoinstalled. You can use Online Diagnostics to perform a series of hardware tests on amanaged PRIMERGY server from the remote workstation.

l When installing the ServerView Agents (for Windows) in Expert mode, you can choosewhether to install additional components, including Asset CLI, Configuration Tools,Prime Collect, ServerView System Monitor Web Interface, and ServerView CIM Providers.

o ServerView System Monitor Web Interface allows you to monitor and check theserver information locally on your server. You can also check whether an updatefor a component (BIOS and firmware as well as drivers and ServerView Agents) isavailable or necessary, and perform updates. The ServerView System Monitor WebInterface is described in "ServerView System Monitor" user guide.

o The ServerView CIM Providers are available, to manage PRIMERGY servers by usingthe CIM infrastructure.

If the operating system is not support by CIM Provider, the ServerViewCIM Provider feature is not offered in the Custom Setup step.

For details refer to the "ServerView CIM Providers for the management of PRIMERGYservers" user guide, which describes in detail the profiles supported by theServerView CIM Providers.

2.1 Configuring the BIOS and FirmwareThe following description is only valid for PRIMERGY.

Since the various PRIMERGY types work with different BIOS versions, depending on whichsystem board is used, the individual settings and the operation of the BIOS setup are notdealt 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 thesystem board.

When you start the server, you must set the menu item O/S Boot Timeout in thesystem BIOS setup to Disabled. If you do not do this, the system will restart duringthe installation.

You may only set the O/S Boot Timeoutmenu item to Enabled when you restartthe system after you have completed all installations (including the ServerViewAgents).

2.1.1 BIOS settings

The server management firmware monitors the server until the operating system hasstarted. After that, the agents and the Operations Manager program assume themonitoring function.

You must change the BIOS settings on every server.

Call the BIOS setup by rebooting the computer and pressing [F2] or [DEL] at theappropriate time in the bootup phase.

On entering the BIOS setup, select the Server menu. This menu enables you to specify thesettings required for server management.

If the Server menu is not offered in the BIOS setup, you do not need to activate theserver management functions. Note, however, that this also means that you haveno explicit control over the individual server management functions.

If the Server menu includes a Server Managementmenu item, select this item and set itto Enabled. This activates the server management functionality. You must select the valueEnabled here for all the other settings to take effect.

If the Server Managementmenu item is not available, control over the individualfunctions 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 thehardware.

O/S Boot Timeout

Specifies whether the system is to be rebooted if the operating system cannot establish aconnection 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 Timeoutmenu item to Disabled when starting theserver. 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/SBoot 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 remainsshut down or before RemoteView is started.

Diagnostic System

Determines whether or not RemoteView is to be started on reaching the number of systemrestarts set under Boot Retry Counter.

Hardware Watchdog

Specifies whether the server is to be rebooted if the server management BIOS cannot reseta 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 temperaturevalue.

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.


2.2 Configuring servers

Memory Status

Enables certain memory modules to be identified as defective. These modules will then nolonger 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 andOperations Manager. RomPilot provides access from a remote console via LAN to thesystem 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)

2.2 Configuring serversThere are various functions available for configuring servers. Some of these functions aresupported 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 systembehavior 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 Managerbutton.

Depending on the PRIMERGY server type of the target system, not all stepsmay be performed. The sequence of the individual steps and the configurationoptions for the individual steps may also vary from system to system.

For details on the individual server configuration dialog steps, please refer tothe 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 Windows Server 2008/2016: Locally on the managed servers using the Startmenu.

For example, on the managed server with Windows Server 2008 select Start – AllPrograms – Fujitsu – ServerView Suite – Agents – System Configuration.

You can only configure servers on which the ServerView Agents for Windowsare installed.

For details on the individual server configuration dialog steps, please refer tothe online help.

To access the online help related to a dialog step, proceed as follows:


2. Press [F1].

l 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 theApps page. To open this page click on the right upper or lower corner on the Startpage. In the displayed window select Search.

2. Select System Configuration on the Apps page.



l Via the ServerView Configuration Manager, which is integrated in the graphical userinterface of Operations Manager. This allows you to configure servers from the remoteworkstation via a web interface.

You start the ServerView Configuration Manager on the Operations Manager start pageor 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 integratedmanagement 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 Configure the settings for HTTP and Telnet and the setting for the Remote ManagementController for HTTP.

l Configure the IP and DNS settings for the iRMC web interface.

l Configure the SNMP communities and the trap target for the SNMP interface of theremote 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 Configure the information shown on the display of the ServerView Local ServiceDisplay.


2.3 SNMP security concept

2.3 SNMP security conceptThe ServerView SNMP agents together with the ServerView Manager provide a completesecurity 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 thefollowing 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 authenticationroutine 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 theadministrator.

The user authentication only operates with ServerView Manager. It does notwork with other SNMP tools.

You can also reduce the risk of unauthorized access by changing the default configurationof the SNMP service. For further information, see "Configuring SNMP services" on page 23.

2.3.1 Prohibiting specific SET operations

Some SET operations cause the system to shutdown or restart. You can permit thesespecial SET operations or forbid them.

The specific entries you need to make during the installation in order to prohibit these SEToperations depend on the operating system under which the ServerView Agents areinstalled and on the version of the ServerView Agents. For a detailed description,"Installing ServerView Agents" on page 29.

2.3.2 Prohibiting All SET operations

You can prohibit all SET operations for ServerView Agents. Enter these specifications duringagent installation.

The specific entries you need to make during the installation in order to prohibit these SEToperations depend on the operating system under which the ServerView Agents areinstalled and on the version of the ServerView Agents. For a detailed description,"Installing ServerView Agents" on page 29.



This option only applies to ServerView Agents. SET operations for other SNMPagents 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 witha user authentication. Here you can choose between starting the user authenticationroutine at the beginning of each session on a managed server or starting the userauthentication at the start of each new SET operation.

For user authentication, you must make the following settings on the managed server aswell as on the management station.

Entity Settings

managed server l Define user and user group

l Assign user to specific user group

l State the specified user group during installation of theagent

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 specificto 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 andgroup 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 towhich the user, permitted to execute SET operations, must belong. Installation andconfiguration of the ServerView Agents differs according to operating system and version.For more information about installation and configuration in these cases, see the agentdescriptions beginning at page 45.

Specifying users on the management station

On the management station you must specify in Operations Manager the user permitted toexecute SET operations on the current server. Executing a SET operation through themanagement station, the user is prompted to provide identification. You define the user inthe Login tab in the Server Properties window. In this example this would be SVUSER.



Figure 2: User authentication

If you have assigned a password to a user, for reasons of security, we recommend that youenter the password here as well (Set Password). The option Always Ask for Passwordallows you to specify whether user name and password are required after each changemade to the settings, or only after the first alteration made after starting OperationsManager. You a achieve a higher degree of security, if you activate Always Ask forPassword 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 thesettings are to apply. You can also select several servers at once. This allows you to specifysettings for each server individually or to apply an identical setting to several serverscollectively.

How to open the property window is described in "ServerView Operations Manager" userguide.

2.3.4 Operating system-specific characteristics of the SNMP agents

The following sections describe the procedures, specific to the operating system and agentversions, involved in realizing the security concept of ServerView.


2.4 Configuring SNMP services

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 forbidSET operations, all SNMP SETs are refused, regardless of the SET tool used to executethem. (Shown on the management station in Operations Manager on the tabs RestartSettings and Power ON/OFF in the settings under Set Enabled on server).

This option only applies to ServerView Agents. SET operations for other SNMPagents are not affected.

l You can turn the user authentication for SET operations on or off. You can enter theuser group to which the user must belong to be allowed to carry out SET operations onthe server.

l Some SET operations (e.g. Restart/Shutdown/Abort Shutdown in the Recoverywindow) cause the system to shutdown or restart. You can allow or forbid thesespecial SET operations.

For further information on installing the agents, see "Installing ServerView Agents" onpage 29.

2.4 Configuring SNMP servicesYou must install and configure the SNMP services on every server to be managed andevery management station.

When you install and configure the SNMP services default values are provided. You canmodify these values for the SNMP service. If you change the values you must alsoremember to change them on the management station.

Configure the following values:

l Community string for accepting SNMP requests

The Community name (Community string) is part of every SNMP request sent from themanager to the agent.

After installing the SNMP services, no community name is available. You can use thecommunity name public. This default entry is used by most SNMP services. For reasonsof security, we recommend that you change this entry. In principle you can define anindividual community for each server or server group. Remember to makecorresponding changes on the management station.

l Community names are case sensitive.

l You can configure the community names. How to do this is described inthe White Paper “Secure PRIMERGY Server Management“.



l Rights for the community

Rights can be assigned to the community (e.g. read-only, read-write). If you want touse the entire range of Operations Manager functions, you must assign read-writerights 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 rightsfor 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 ascentral management station (CMS). This will prevent the agent from acceptingrequests from unauthorized servers.

If you limit access to dedicated CMS, you are recommended to additionally add themanaged 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 SNMPagents 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.

l Community string for sending traps

Here, enter the community name that is to be sent to the management station as partof a SNMP trap. The SNMP service on the management station must be configured sothat it accepts traps with this community name.

You should take care to ensure that installation and configuration of the SNMPservices takes place at the correct time. This depends on the operating system youare using. SNMP services are configured and installed before or after installing theagent depending on the operating system being used.



2.4.1 Windows Server 2008 / 2012 / 2016

When you have completed installing Windows Server 2008, Windows Server 2012, orWindows Server 2016 on the server, you must perform the following steps before youinstall the ServerView Agents, unless you have already completed them during the systeminstallation:

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 notyet 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/2016:

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.

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 therunning tasks.

2. Configure SNMP

1. On Windows Server 2008: Call the Server Manager (if not already is opened) byclicking Start – Control Panel – Administrative Tools – Server Manager. Double-click Configuration, then click Services.

On Windows Server 2012/2016: 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 amanagement station belonging to the community entered here can query theserver. If you do not select public, then you must also change the communityentered in the management station for the relevant server.

5. Under Trap destinations, enter the IP address or the domain name of themanagement 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 theSNMP agents, the access rights can be defined.

Click Add..., enter a valid community name (e.g. public) and select Communityrights as READ WRITE for SNMP GET/SET access or READ ONLY for GET access ofthis community.

Set the Rights for the community to READ WRITE (in the case of a default entry forpublic).

3. Accept SNMP packets from any host / Accept SNMP packets from these hosts: Youcan select the managed server from which SNMP packets are to be accepted, oryou can select them all here.

SNMP is installed with the highest level of access protection. You must thereforespecify the management station, or select the option Accept SNMP packets fromany host.

Since SNMP is an open protocol without password protection, you shouldonly enter those management stations that function as such. Otherwise,unauthorized network users could alter important system parameters andthus disrupt server operation.

4. Activate the option Send authentication trap to allow the SNMP service sendingan authentication failure trap whenever an unauthenticated management stationtries to access this server.

5. Click OK.

You may also click on the link Learn more about SNMP to get detailedinformation about the SNMP configuration options.



4. Start SNMP service

Start the SNMP service under Services. Select Start from the context menu.

2.4.2 For environment in which Server Core is installed

In the local console environment of Server Core, the GUI based management tool ofMicrosoft management console (MMC) is not available. You need to start the managementtool from another terminal with Windows 8, Windows 7, Windows Server 2016, WindowsServer 2012, or Windows Server 2008 and connect it remotely. The procedure is shownbelow.

To configure the setting of SNMP Service, another Windows terminal (installed other thanServer Core of Windows Server 2008) is required. Prepare it in advance.

1. On the terminal with Server Core, execute the following command, to check whetherSNMP Service is installed and has started.

> sc query SNMP

When SNMP service is not installed execute the following command, to install theSNMP 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 permitthe access to manage it remotely.

> netsh firewall set service remoteadmin enable

> netsh advfirewall set currentprofile settingsremotemanagement 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 followingcommand. During the operation, you are prompt to enter Administrator password.Enter IP address of monitoring server (Server Core) in "xxx.xxx.xxx.xxx" of thefollowing command.

net use \\xxx.xxx.xxx.xxx\c$ /u:Administrator

5. Execute the following commands.

>services.msc

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 aresupported.


3.1 Installing and configuring agents

3 Installing ServerView AgentsWhen 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 themanagement station. You have the option to either initially install the certificatefiles together with the ServerView Agents or to install the certificate files on amanaged server where the ServerView Agents have already been installed.

Installing the certificate files together with the ServerView Agents requires that thecertificate files have already been installed on the managed server before theagents 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 cannotperform a downgrade installation. To downgrade, you must uninstall any existingServerView agent first.

Before you install the ServerView Agents for Windows, it is essential that you install andactivate the SNMP services in the operating system. If you do not do this, the managementstation cannot monitor the servers (for further information, see "Configuring SNMPservices" on page 23). Before you start installation, you should carefully plan your securityconcept of ServerView. For further information, see "SNMP security concept" on page 20.

After ServerView Agents is installed, you will find a ThirdPartyLicenseReadme.txtfile in the installation directory (default: C:\Program Files\Fujitsu\ServerViewSuite\Agents). This file contains information on the third party software inServerView Agents for Windows.

3.1 Installing and configuring agentsSilent installation of the ServerView Agents is described in "Installing via thecommand line interface" on page 47.

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 startautomatically, 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 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 willcheck if an older version of ServerView Agents is already installed on the server. In thiscase you can perform an upgrade installation. During this, the present configuration issaved, then the old version is deleted and the new one is installed based on the previousconfiguration. In this case you cannot make any changes.

If no agents are present on the system, the window shown below will be opened:

Figure 3: Setup Level window

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 arerequired. In these modes, the SNMP agents required for Operations Manager and the maintools (i.e. Configuration, Maintenance, Diagnostic) will be installed, see "Installed tools"on page 42. In these three modes the setup uses the default values for the security levelselected.

If you choose the Expert (Advanced users) mode you must enter the installation andconfiguration values individually. In this mode, the wizard will guide you through theinstallation 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 anySNMP SET operations. SET operations are also prevented if the SNMP community used haswrite permissions.

You can change the configuration of the standard installation, for example by assigningread/write rights to the community, or by creating new user groups and users andreconfigure the agent accordingly.

Typical (Administrator account based security)

In this standard installation mode, SNMP SET operations are permitted. Managementstation SET operations are password protected and have local administrator and userauthentication. Local passwords and administrator access rights. However, there is nopassword protected security for SET operations which have been run using other SNMPtools. The SNMP community which is used requires write permissions to execute SEToperations. Otherwise the SET operation will be prevented by the security mechanisms ofthe operating system.

You can change the configuration of the standard installation, for example by setting upnew user groups and users with operating system-specific resources or reconfigure theagent with the configuration tool Agents Configuration.

Typical (Without any security)

In this standard installation mode, SNMP set operations are permitted without anypassword protected security further user authentication. This installation mode shouldonly be used on secure internal networks. The SNMP community which is used requireswrite permissions to execute SET operations. Otherwise the SET operation will be preventedby the security mechanisms of the operating system.



Expert (Advanced users)

The expert mode provides the following options:

l Select other components.

l Configure agent packages individually. Here you can individually configure SNMP trapforwarding, SNMP security settings and system shutdown behavior.

l Pre-configure the remote management controller. During installation can define themain settings of the remote manager controller and then transfer these to the systemduring setup.

l Create a configuration file for automatic installation (i.e. “unattended setup”) at alater date. You can save your settings for the management controller configurationand agent configuration in this file and then use these later for an unattended setup.

Figure 4: Expert Settingswindow

Agents ...Opens a window where you can change the ServerView Agents configuration. For moreinformation, see the next section below.

Restrict SNMP access to local systemThis option defines the value Restrict access to these host only in the SNMP settingsand enters the LOOPBACK adapter. If you select this option you will not be able toaccess the system from outside. This option only makes sense if the Event Manager isinstalled 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 configurationfile.

This file will be used for automatic installations (“unattended setup”) (see also"Installing via the command line interface" on page 47).

The configuration file must be in the same directory as the Setup.exe.

< BackReturns you to the previous window.

Next >Displays the next window.

CancelCancels the installation.

Due to architectual changes the launch of the System Configuration Tool (via theSystem ... button) is no longer available within the setup wizard. To configure thesystem settings now, finish the agents setup and launch the System Configurationutility (see "Configuring servers" on page 17).

Configuring ServerView Agents

To start configuration of the ServerView Agents, click the Agents ... button. The ServerViewSNMP 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

Trap Forwarding tab

All SNMP traps generated by ServerView Agents can be reported to the system’s event logor forwarded as an administrator alert message. Forwarding depends on the weightassigned 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 beforwarded to the administrator. The message targets must already be defined in theproperties of Windows Server Manager.

The source name of the events reported by ServerView Agents is ServerView Agents.ServerView Agents report to the Application log.

Figure 5: Trap Forwarding tab

Use the Trap Forwarding tab to select which types of SNMP traps will be forwarded. In thedefault 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 anoperation 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 toclose any running applications and then to explicitly confirm the shutdown. After a presettime delay has elapsed, the ServerView Agents will initiate a hard shutdown and shutdownthe operating system even though the shutdown has not been explicitly confirmed and notall 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 increasethis value accordingly.

You can choose to start an application (a shutdown job) before the soft shutdown isinitiated.

Figure 6: 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 isstarted. 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 willstart a hard shutdown without saving any data.

Executable PathPath name of an executable program or script.The path may also contain environmentvariables, e.g. %SystemRoot%.

Working DirectoryIndicates the working directory for the job.

Maximum execution time (sec)Indicates the maximum duration of the job. The shutdown will be started once themaximum time set in this field has elapsed.



Security Settings tab

The ServerView Agents used in combination with management station provide a completesecurity concept restricting access to SNMP SET operations on the server. You can preventaccess to SET operations or, using user authentication protection, enable access to theseoperations when performed together with management station.

If you select the user authentication option, the system will run a user authenticationroutine each time you start a SET operation. If the authentication routine is successful, thesystem will also check if the user belongs to one of the user groups defined by theadministrator.

This user authentication system only operates with Operations Manager onmanagement station. It does not work with other SNMP tools.

You can define the security settings on the tab shown below:

Figure 7: Security Settings tab

Enable Password ProtectionThis checkbox enables/disables the user authentication routine protecting access toSNMP SET operations.

User GroupIndicates the user group to which the user must belong in order to perform SEToperations 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 methodsspecific to your operating system.



Do not assign a user to a user group at this point. Wait until later. You assign a userto a user group at the operating system level, either before or after installing theagent. For security reasons, we recommend that you enter one user only.

If you do not enter a name in User Group, only local system administratorswill be allowed access to SET operations on the server.

When installing the ServerView Agents by using ServerView InstallationsManager, User Groupis set to "FUJITSU SVUSER".

Enable ServerView SET operations on serverEnables SNMP SET operations by ServerView Agents . If you forbid SET operations, thiswill 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 otherSNMP agents.

Enable remote shutdown via SNMP requestSome SET operations trigger a shutdown or a system restart. Use this checkbox toenable/disable these special types of SET operation.

Threshold Monitoring tab

Via the Threshold Monitoring you can activate or deactivate threshold monitoring for theThreshold Manager.

Figure 8: Threshold Monitoring tab



Selecting the destination folder

Confirm the agent configuration in the Expert Settings window by clicking OK. Next, go tothe Destination Folder window to change the installation folder.

Figure 9: Destination Folder window

By default the ServerView Agents is installed by default in the installation directory. Youcan change the folder via the Change... button.

If you use the Performance Manager, report data is stored by default in the installationdirectory. However, this data can easily amount to 50 Mbytes or more, depending on theapplication. You therefore have the option of selecting a different directory with sufficientspace via the Change... button.

Defining the setup type

Confirm the agent configuration in the Expert Settings window by clicking OK. Next, go tothe Setup Type window to select the setup type.



Figure 10: Setup Type window

Select the setup type you require.

CompleteSelect this option to start an installation where all the features are installed. This typerequires the most memory space.

CustomSelect this option if you want to select individual features and define the path. Youcan also specify the storage location for the report data and the port for theServerView Remote Connector service.



If you select Custom and then Next, the following window opens:

Figure 11: Custom Setupwindow

This window offers the following features for selection:

Feature Description

StandardAgents

SNMP agents required for Operations Manager.

S.M.A.R.T.Support

S.M.A.R.T. support for event monitoring.

MicrosoftSMSIntegration

Software for automatically creating MIF files for Microsoft SMS V 1.2 and V2.0.

MIB Files ServerView MIB files.

ConfigurationTools

Tools for agent and system configuration.

Support Tools Tools for service technician

DiagnosticTools

Various diagnostic tools (e.g. for installation testing), for supportpurposes only.



Feature Description

SystemMonitor WebInterface

Tool for system monitoring and updating the managed server locally.

WindowsManagementIntegration

Integration into Microsoft Windows Management (WMI).

VirtualizationManagementAgent

Provides performance data for virtual machines (Xen, Hyper-V, VMWare).

HP SystemsIntegration

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 andsoftware of PRIMERGY servers.

Help Files Help files

RemoteConnectorService

Provides HTTP-based services.

ServerControlService

Basic service required.

CIM Provider If the operating system is not support by CIM Provider, the ServerView CIMProvider feature is not offered in the Custom Setup step.

Installs the ServerView CIM Providers, to manage PRIMERGY servers byusing the CIM infrastructure, see also "ServerView CIM Providers for themanagement of PRIMERGY servers" user guide.


3.2 Installed tools

Once you have selected the components, the following window opens:

Figure 12: Ready to Install the Program window

Click Install to start the installation.

3.2 Installed toolsl Windows Server 2008/2016: After successful installation, different tools are availablein the Startmenu.

For example, Windows Server 2008:

Start – Programs – Fujitsu – ServerView Suite – Agents

l Windows Server 2012: After successful installation, different tools are available on theApps page. Via the Pin to Start icon you can move applications to the Start page.


3.2 Installed tools

On the Start page you can build applications groups. Select the relevant applicationsand click on the minus sign on the right below.

A dialog opens to enter a name for the group. The new group is displayed on the Startpage, e.g. group ServerView.


3.2 Installed tools

After installation it takes some time to complete the configuration. As a result youmight find that when you query the configuration, the system will continue todisplay the old values.

Maintenance Tools

CPUStatus

Shows the CPU overview.

MemoryStatus

Displays a detailed list of all the memory modules installed. Use this tool toreset the error counters of memory modules.

We recommend that you reset the error counter after having changed amemory module.

*)Counters

Resets the counter to zero (total time ON, total time OFF, total number ofsystem power up cycles).

We recommend that you reset the counter after having changed the CMOSbattery.

*) 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 PRIMERGYservers.

Agents Configuration

Enables configuration of the ServerView Agents.

System Configuration

Enables configuration of the server firmware.


3.3 Configuring RAID

System Monitor Web Interface

Via this entry you start the ServerView System Monitor Web Interface. The ServerViewSystem Monitor allows you to monitor and check the following server information locallyon your server:

l Environment information, including fan and temperature sensor information.

l Power supply information.

l Mass storage information. This information is only available if ServerView RAIDManager 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).

3.3 Configuring RAIDFor the RAID configuration you can use ServerView RAID Manager, which you will find onthe ServerView Suite DVD 2 under RAID Manager.

3.4 Configuring APC and Masterguard UPSsThe following description is only valid for PRIMERGY.

You must configure the uninterruptible power supply (UPS) connected to the system or theadditional 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 SNMPagent will be supplied by the UPS manufacturer. For UPS with a web card, the SNMP agentnecessary should be pre-installed on the web card.

In order to be able to communicate with the UPS SNMP agents, Operations Managerrequires 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.


3.4 Configuring APC and Masterguard UPSs

You must give an IP address because this is necessary for SNMP communications with theagents. 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 forthe SNMP agents. Operations Manager recognizes the model and manufacturer name ofthese two models and automatically assigns the relevant SNMP OIDs. For these types werecommend 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/OperationsManager, first you must install the PowerChuteBusiness Edition application (for APC UPSwith 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 thesection concerning APC UPS in the Operations Manager user guide).

The PowerChuteBusiness Edition is available on the APC CD. upsmon is anindependent product.

Configuring a UPS under Windows Server 2008/2012

You can configure a UPS locally on managed Windows-based servers.

1. Windows Server 2008/2016: by using the Startmenu.

For example, under Windows 2008 select:

Start – All Programs – Fujitsu – ServerView Suite – Agents – System Configuration

Windows Server 2012: by using the Start page.

There are different ways to start the configuration. One possibility is to switch to theApps page. To open this page click on the right upper or lower corner on the Startpage. In the displayed window select Search.

2. On the System Configuration start page select the features and click Go....


3.5 Installing via the command line interface

3. In the tree view select UPS Integration.

Figure 13: UPS Integration

For details on the parameters, please refer to the online help of the Server ConfigurationManager.

To access the online help, proceed as follows:


2. Press F1.

3.5 Installing via the command line interfaceYou can install the agents via a command in the command line. Operations Manager alsoallows the silent installation of agents. With the help of the silent installation, Softwaresharing systems such as Microsoft System Management Server (SMS) can share softwareautomatically. The simplest form of software sharing is the unattended execution of setupswith standard configuration. You are also able to fit the installation to your needs withthe help of environment variables.

The ServerView Agents setup is based on Microsoft Windows Installer technology. The setupdata is found in the installer database, ServerView Agents.msi. The setup data are packedin Data1.cab.

Command syntax of Setup.exe

Switch to the command-line level and enter the Setup command on the highest level ofthe 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 andplaced in a directory. No registry entries or connections are made.

/s(Silent mode)

Suppresses all messages on the screen. The installation is completed in thebackground.

/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 isalways written in capital letters. Values are case sensitive.

INSTALLDIRResets the standard installation directory.

Valid path names, e.g.:

INSTALLDIR=C:\Programs\Fujitsu\ServerView Suite\ServerView Agents

Standard: System Folder

REBOOTInfluences actions when the system reboots after the installation. For example, thisoption prevents a system from rebooting after an automatic installation ifcomponents can only be changed after the restart. Possible values:

FThe system always reboots.

RThe system never reboots.

SETUP_LEVELSets 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.



LevelAdminInstalls in setup mode: Typical (Administrator account based security).

ServerView SNMP SET operations are checked for local administrator rights andpassword.

LevelAllInstalls in setup mode: Typical (Without any Security).

ServerView SNMP SET operations are allowing without any checks. This installationmode is a sensible choice for secured internal networks.

LevelUserInstalls in setup mode: Expert (Advanced users)

ADDLOCALStates which features are to be installed. If you do not choose any features, a standardselection is installed. If you wish to make an individual choice, you must state thevariables with ADDLOCAL. The feature names are listed separated by commas.Possible values:

AllInstalls all modules.

ServerControl(Standard, must always be installed)

Installs the ServerView Base Service.

SnmpAgents(Standard)

Installs the ServerView Agents.

MIBFilesInstalls the ServerView Agents MIB data.

SmartSupport(Standard)

Installs ServerView S.M.A.R.T. support.

Configuration(Standard)

Installs the ServerView Configurations Tools.

Diagnostic(Standard)

Installs the ServerView Diagnostic Tools.

Maintenance(Standard)

Installs the Support Tools.



SMSInstalls the ServerView Integration in SMS.

WMIInstalls the ServerView Integration in WMI.

WCSInstalls the ServerView Remote Connector.

AssetCLIInstalls the ServerView Asset CLI tool.

OnlineDiagnosticInstalls the Online Diagnostic tool.

PrimeCollectInstalls the PrimeCollect tool.

HelpServerView help files.

SSMWeb(Standard)

Installs the ServerView System Monitor Web Interface for system monitoring andupdating.

CIMInstalls the ServerView CIM Providers.

HPSIMInstalls the ServerView Integration in HP SIM (HP Systems Insight Manager).

ExampleADDLOCAL=ServerControl,MIBFiles,WMI

The program features ServerView Base Service, ServerView Agents MIB data andServerView 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.preshould be saved. The configuration file must be saved in the same directory as theMicrosoft Installer data file (ServerView Agents.msi).


3.6 Setting after installation

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.exeSetup.exe /s/V“/qn“

Automatic installation of the standard configuration. The setup mode is Typical (Highsecurity), i.e. no SNMP SET operations are allowed, critical traps are entered in thesystem 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 Agents

l ServerView Configuration Tools

l ServerView Diagnostics Tools

l ServerView Maintenance Tools

l ServerView Remote Connector

l ServerView PrimeCollect

l ServerView System Monitor Web Interface

Setup.exe /s/V“/qn SETUP_LEVEL=LevelAll INSTALLDIR=“C:\MyPrograms“

Appropriate automatic installation in setup mode: Typical (Without any security) andchanged installation path.

Setup.exe /s/V“/qn ADDLOCAL=ServerControl,WMI INSTALLDIR=“C:\MyPrograms“

Automatic installation of the basic features for integration in the WindowsManagement Instrumentation (WMI) with altered installation path.

Setup.exe /s/V“/qn ADDLOCAL=ServerControl,WMI Reboot=R“

Automatic minimal installation for integration in Windows ManagementInstrumentation (WMI) without system reboot.

3.6 Setting after installationAfter the installation of ServerView Agents or CIM Providers for Windows, perform thefollowing settings to ensure that agent operates properly.


3.6 Setting after installation

3.6.1 Setting an administrative user

Only users belonging to the group (FUJITSU SVUSER) that have administrator privilegesfor ServerView can perform operations such as configuring Automatic ServerReconfiguration & Restart (ASR) settings (e.g. fans, temperature, restart settings) for themonitored server and shutting down the server from ServerView Operations Manager. Atthis time, the administrative user's name and password are required to be input. Followthe steps below to set an administrative user. The FUJITSU SVUSER group and usersbelonging to the group are not created automatically. Create a group each monitoredserver and add the ServerView administrative user to the FUJITSU SVUSER group.

An administrative user in ServerView means a user who belongs to the FUJITSU SVUSERgroup. In Windows Servers, administrative privileges are not given if the password is notset for the administrative user account. Be sure to set the password.

Even when a "global" group is added to the FUJITSU SVUSER group, administrativeprivileges are not given to the users in the added group. Add only users to the FUJITSUSVUSER group. If an administrative user is set for another group than FUJITSU SVUSER, thelogon immediately after starting the program may fail. In this case, click Cancel to exit thelogon 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 windowopens.

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. ClickClose 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 theNew 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 opensagain.

14. Click OK. The display returns to the user Properties window. Confirm that FUJITSU


3.7 Uninstalling ServerView Agents

SVUSER is added to Member of, and click OK.

15. Click OK. Close the Computer Management window.

3.6.2 For Environment in which Server Core is installed

In the local console environment of Server Core, the GUI based management tool ofMicrosoft management console (MMC) is not available. Execute the following command toset 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 followingcommands.

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

3.7 Uninstalling ServerView AgentsThe items saved on the server's BIOS are not restored even when ServerView Agents areuninstalled. Restore the settings to the original state before uninstalling ServerViewAgents.

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 are applied by Performance Manager,cancel these performances to the server.


3.8 Restart

To uninstall ServerView Windows agent, perform the following steps.

You do not need to restart Windows after uninstalling ServerView Agents.

3.7.1 Windows Server 2008


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

3.7.2 Windows Server 2012 / 2016


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 RestartThe 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 restartboth the ServerView Server Control service and the SNMP service.


ServerView Agents 8.30 for Windows - Fujitsu...

Documents

Transcript of ServerView Agents 8.30 for Windows - Fujitsu...