ServerView Agents V8.20 for Windows

Transcription

1 Installation and User Guide - English FUJITSU Software ServerView Suite ServerView Agents V8.20 for Windows (Windows Server 2008 / 2012 / 2016) Edition October 2017

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

3 Contents 1 Introduction Architecture Target groups and objectives Technical requirements Last-minute changes/corrections Managed Server What's new ServerView Suite link collection Documentation for the ServerView Suite Notational conventions 12 2 Configurations on the managed servers Configuring the BIOS and Firmware BIOS settings Configuring servers SNMP security concept Prohibiting specific SET operations Prohibiting All SET operations SET Operations with user authentication Operating system-specific characteristics of the SNMP agents Configuring SNMP services Windows Server 2008 / 2012 / For environment in which Server Core is installed 27 3 Installing ServerView Agents Installing and configuring agents Installed tools Configuring RAID Configuring APC and Masterguard UPSs Installing via the command line interface Setting after installation Setting an administrative user For Environment in which Server Core is installed 53 ServerView Agents for Windows 3

4 Inhalt 3.7 Uninstalling ServerView Agents Windows Server Windows Server 2012 / Restart 54 ServerView Agents for Windows 4

5 1 Introduction ServerView Operations Manager (Operations Manager for short) is a free server management module of the Fujitsu ServerView Suite. It is used for central administration of industry-standard servers which run the operating systems Windows and Linux (SUSE and Red Hat) or which serve as hosts for virtual machines (VMs) that use the hypervisors VMware ESXi or Hyper-V installed. The standardized management of all servers occurs via one or more central management stations, which you can access from any workstation in the network that has a popular web browser and the Java Runtime Environment. Operations Manager controls the individual systems, including critical hardware components such as processors, RAM, hard disks, fans and power supply. It monitors and controls the power consumption, analyzes the performance and utilization data and updates the server configuration. The security concept of Operations Manager includes role-based user management based on three underlying concepts: Global user management via an LDAP directory service (Lightweight Directory Access Protocol) Role-Based Access Control (RBAC) Single Sign-On (SSO) based on a Centralized Authentication Service (CAS) With RBAC you can tailor your security concept to the organizational structure of your company by assigning a task-oriented authorization profile to each role. SSO means that you only need to authenticate yourself once. Once you have done this successfully, you are given access to all ServerView components without having to sign on to any of them again. Server management with Operations Manager offers important benefits to operators of a comprehensive server network: Higher productivity thanks to high failsafety of the servers Reduced costs through automated monitoring of the IT infrastructure Flexible expansion possibilities for the servers, as Operations Manager can be easily adjusted to changed conditions Shorter downtimes thanks to simplified error analysis Guarantees energy-efficient and, where possible, uninterruptible server operation Quicker response times in the event of errors Reduction in total cost of ownership (TCO) through efficient use of network ServerView Agents for Windows 5

6 1.1 Architecture components and their resources Very easy operation thanks to ergonomic software: clearly laid out, intelligent user guidance and supportive help system 1.1 Architecture The architecture of ServerView Operations Manager is based on a management console, a central management station (CMS) and the managed servers. Figure 1: Architecture of ServerView Operations Manager Management console A Java Web Start-based console allows you to manage the servers and display the determined data. All you need is a popular web browser to download the starter file for Java Web Start. The following can be used as a browser: Microsoft Windows with any popular web browser SUSE/Red Hat Linux with default web browser released with distribution The Java Runtime Environment must also be installed. ServerView Agents for Windows 6

7 1.1 Architecture Central management station (CMS) On the central management station the ServerView Operations Manager is installed. The optional components of the ServerView Suite, such as Virtual IO-Manager, are also installed on the central management station and integrated in Operations Manager. The central management station (and thus the ServerView Operations Manager with its components) may also run in Windows-based or Linuxbased virtual machines (VM) that use hypervisors such as VMware ESXi, Microsoft Hyper-V, and Red Hat Enterprise KMV. The global user management of the ServerView Suite and of the irmc each centrally stores users for all Central Management Stations (CMS) / irmc in the directory of an LDAP directory service. This enables you to manage the users on a central server. The users can therefore be used by all the CMS and irmc that are connected to this server in the network. The ServerView Suite currently supports the following directory services: ApacheDS 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 User Management in ServerView user guide. The data which ServerView creates and uses is stored in an SQL database within an SQL Server. The following SQL Server are part of the ServerView Operations Manager installation: SQL Server 2014 Express under Windows Server PostgreSQL under Linux However, other Microsoft SQL Server databases can be used under Windows. The Java Runtime Environment is required on the central management station. How to install the ServerView Operations Manager is explained in the following manuals: Installing ServerView Operations Manager Software under Windows Installing ServerView Operations Manager Software under Linux Managed servers On the managed servers, ServerView Agents, ServerView CIM Providers, or ServerView Agentless Service should be installed, which supply the information to the central management station. ServerView RAID Manager and ServerView Update Agent should be also installed on the managed servers. The installation of ServerView Agents on virtual machines (VMs) is not released. ServerView Agents for Windows 7

8 1.2 Target groups and objectives 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: ServerView Agents for Windows ServerView Agents for Linux Installation ServerView ESXi CIM Provider ServerView CIM Providers for Windows, Linux, and VMware ESXi 1.2 Target groups and objectives This manual is intended for system administrators, network administrators and service technicians that have a basic knowledge of hardware and software. The manual describes the installation of the ServerView Agents for Windows Server 2008, Windows Server 2012, and Windows Server Technical requirements Last-minute changes/corrections Any last-minute changes/corrections of the technical requirements can be found in the Readme file on the ServerView Suite DVD 2. You have the following options: On the DVD switch to the directory SVSSoftware Software ServerView 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: Windows Server 2008 (x64) with SP2 Windows Server 2008 Enterprise Edition (x64) with SP2 Windows Server 2008 Datacenter Edition (x64) with SP2 Windows Server 2008 Core installations with SP2 ServerView Agents for Windows 8

9 1.4 What's new Windows Server 2008 R2 Windows Server 2008 R2 Enterprise Edition Windows Server 2008 R2 Datacenter Edition Windows Server 2008 R2 Core installations Windows Server 2012 Standard Windows Server 2012 Datacenter Windows Server 2012 Essentials Windows Server 2012 Foundation Windows Hyper-V Server 2012 Windows Storage Server 2012 Windows Server 2012 R2 Standard Windows Server 2012 R2 Datacenter Windows Server 2012 R2 Foundation Windows Hyper-V Server 2012 R2 Windows Storage Server 2012 R2 Windows Server 2016 Standard Windows Server 2016 Datacenter Windows Server 2016 Essentials 1.4 What's new This edition of the manual applies to ServerView Agents V8.00 or later and replaces the online manual "ServerView Agents V7.31 for Windows", edition November The manual features the following changes and enhancements: No 32-Bit system support. The technical requirements has been updated, see Technical requirements. ServerView Agents for Windows 9

10 1.5 ServerView Suite link collection 1.5 ServerView Suite link collection Via the ServerView Suite link collection, Fujitsu provides you with numerous downloads and further information on the ServerView Suite and PRIMERGY servers. Under ServerView Suite, links are offered on the following topics: Forum Service Desk Manuals Product information Security information Software downloads Training Software downloads includes the following downloads: o o o Current software statuses for the ServerView Suite as well as additional Readme files. Information files and update sets for system software components (BIOS, firmware, drivers, ServerView Agents and ServerView Update Agent) for updating the PRIMERGY servers via ServerView Update Manager or for locally updating individual servers via ServerView Update Manager Express. The current versions of all documentation on the ServerView Suite. You can retrieve the downloads free of charge. Under PRIMERGY Server, links are offered on the following topics: Service Desk Manuals Product information Spare parts catalogue Access to the ServerView Suite link collection You can reach the link collection of the ServerView Suite in various ways: 1. Via ServerView Operations Manager. Select Help Links on the start page or the menu bar. 2. Via the start page of the online documentation for the ServerView Suite on the Fujitsu manual server. ServerView Agents for Windows 10

11 1.6 Documentation for the ServerView Suite You access the start page of the online documentation via the following link: In the selection list on the left, select x86 Servers. On the right, click PRIMERGY ServerView Links under Selected documents. 3. Via the ServerView Suite DVD 2. 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 under the link x86 Servers. ServerView Sitemap For an overview of the documentation to be found under ServerView Suite as well as the filing structure, see the ServerView Suite Sitemap: 1. In the selection list on the left, select x86 Servers and then Software. 2. On the right, select ServerView Suite. 3. Click ServerView Suite Sitemap under Selected documents. ServerView Agents for Windows 11

12 1.7 Notational conventions 1.7 Notational conventions The following notational conventions are used in this manual: Notational conventions Indicates Indicates various types of risks, namely health risks, risk of data loss and risk of damage to devices. Indicates additional relevant information and tips. Bold monospace monospace semibold blue continuous text purple continuous text <abc> [abc] [key] Indicates references to names of interface elements. Indicates system output and system elements, for example file names and paths. Indicates statements that are to be entered using the keyboard. Indicates a link to a related topic. Indicates a link to a location you have already visited. Indicates variables which must be replaced with real values. Indicates options that can be specified (syntax). Indicates a key on your keyboard. If you need to explicitly enter text in uppercase, the Shift key is specified, for example [Shift] + [A] for A. If you need to press two keys at the same time, this is indicated by a plus sign between the two key symbols. Screenshots The screenshots are to some degree system-dependent and consequently will not necessarily match the output on your system in all the details. The menus and their commands can also contain system-dependent differences. ServerView Agents for Windows 12

13 2 Configurations on the managed servers Before starting the Operations Manager, the following preparations must be made on the managed server: Only for PRIMERGY: Certain settings must be made in the BIOS on each managed server, see "Configuring the BIOS and Firmware" on page 14. On each server, you must make configuration settings, see "Configuring servers" on page 17. ServerView offers a sophisticated security concept. Before you install the agents, you should study the information regarding the security concept thoroughly and choose the concept that best suits your security requirements. You may need to make appropriate arrangements prior to installing the agent. This is described in "SNMP security concept" on page 20. 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 23. 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. For detailed information, see the ServerView Suite SNMPv3 documentation. ServerView Agents must be installed on each server to be managed, see "Installing ServerView Agents" on page 29. 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 Update Manager requires the ServerView Update Agent to be installed on the managed servers. The installation is described in the "ServerView Update Management" user guide. 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 ServerView Agents for Windows 13

14 2.1 Configuring the BIOS and Firmware 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 ServerView RAID Manager ServerView RAID Manager offers standardized administration and management of hard disks for PRIMERGY servers. Unless the ServerView RAID Manager is installed, no information about RAID drives and their statuses will be available. The installation is described in the "RAID Management" user guide. 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. 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 Web Interface, and ServerView CIM Providers. o o ServerView System Monitor Web Interface allows you to monitor and check the server information locally on your server. You can also check whether an update for a component (BIOS and firmware as well as drivers and ServerView Agents) is available or necessary, and perform updates. The ServerView System Monitor Web Interface is described in "ServerView System Monitor" user guide. The ServerView CIM Providers are available, to manage PRIMERGY servers by using the CIM infrastructure. 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. ServerView Agents for Windows 14

15 2.1 Configuring the BIOS and Firmware 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) BIOS settings The server management firmware monitors the server until the operating system has started. After that, the agents and the Operations Manager program assume the monitoring function. You must change the BIOS settings on every server. Call the BIOS setup by rebooting the computer and pressing [F2] or [DEL] at the appropriate time in the bootup phase. On entering the BIOS setup, select the Server menu. This menu enables you to specify the settings required for server management. If the Server menu is not offered in the BIOS setup, you do not need to activate the server management functions. Note, however, that this also means that you have no explicit control over the individual server management functions. If the Server menu includes a Server Management menu item, select this item and set it to Enabled. This activates the server management functionality. You must select the value Enabled here for all the other settings to take effect. If the Server Management menu item is not available, control over the individual functions is not contingent on a general release. The fields listed below are available in the Server menu. Note that some of the fields listed below may not be available, depending on the hardware. O/S Boot Timeout Specifies whether the system is to be rebooted if the operating system cannot establish a connection with the server management firmware within a predefined time period (after ServerView Agents for Windows 15

16 2.1 Configuring the BIOS and Firmware startup). The time interval can also be set via the Operations Manager (see also section "ASR&R" in "ServerView Operations Manager" user guide). Action You must set the O/S Boot Timeout menu item to Disabled when starting the server. Otherwise, the system will reboot during the installation. Determines the action carried out after the boot watchdog expires. Timeout Value Specifies the time after which a system restart is performed if enabled by means of O/S Boot Timeout. ASR&R Boot Delay Defines the time period for which the server must wait after a shutdown due to an error (e.g. due to overheating) before it is automatically restarted. Boot Retry Counter Defines how often the server tries to restart the operating system before it either remains shut down or before RemoteView is started. 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 16

17 2.2 Configuring 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) 2.2 Configuring servers There are various functions available for configuring servers. Some of these functions are supported for all PRIMERGY servers and others are only available for certain servers, depending on the hardware and software installed in the PRIMERGY server. You can configure the servers in one of the following ways: Locally on the managed server via the Server Configuration Manager. With the Server Configuration Manager you can make settings for the general system behavior of the target system and configure any remote management components (irmc) of the target system. When the ServerView Installation Manager is started from the ServerView Suite DVD 1, you can start the Server Configuration Manager via the Server Configuration Manager button. Depending on the PRIMERGY server type of the target system, not all steps may be performed. The sequence of the individual steps and the configuration options for the individual steps may also vary from system to system. For details on the individual server configuration dialog steps, please refer to the online help of the Server Configuration Manager. To access the online help related to a dialog step, proceed as follows: 1. Click in the window area currently displaying this dialog step. 2. Press [F1]. ServerView Agents for Windows 17

18 2.2 Configuring servers Windows Server 2008/2016: Locally on the managed servers using the Start menu. For example, on the managed server with Windows Server 2008 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 [F1]. 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. 2. Select System Configuration on the Apps page. ServerView Agents for Windows 18

19 2.2 Configuring servers Via the ServerView Configuration Manager, which is integrated in the graphical user interface of Operations Manager. This allows you to configure servers from the remote workstation via a web interface. You start the ServerView Configuration Manager on the Operations Manager start page or via the menu bar by selecting Administration Server Configuration. For further information, see "ServerView Operations Manager" user guide. You can only configure servers on which the ServerView Agents are installed. Depending on the system, some of the configured settings are written to the BIOS. Among other things, you can do the following: Read the most important data of the server, the system board and the integrated management controller. Read and set the Boot and Software Watchdog settings. Read and edit the error counter for the memory modules. For PRIMERGY only: Read and delete the error and event logs of the server. Monitor and calibrate the system fan. Read and set the chassis ID (preset on delivery). Read and set the counters for the system runtimes. Configure the settings for HTTP and Telnet and the setting for the Remote Management Controller for HTTP. Configure the IP and DNS settings for the irmc web interface. Configure the SNMP communities and the trap target for the SNMP interface of the remote management controller. Manage user identification for the remote management controller. Configure the serial interface of the RSB and the remote management controller. Configure Operations Manager UPS management integration. Configure the information shown on the display of the ServerView Local Service Display. ServerView Agents for Windows 19

20 2.3 SNMP security concept 2.3 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: Prohibit specific SET operations. Prohibit all SET operations. Protect SET operations with a user authentication. If you select the user authentication option, the system will run a user authentication routine each time you start a SET operation. If the authentication routine is successful, the system will also check if the user belongs to one of the user groups defined by the administrator. The user authentication only operates with ServerView Manager. It does not work with other SNMP tools. You can also reduce the risk of unauthorized access by changing the default configuration of the SNMP service. For further information, see "Configuring SNMP services" on page Prohibiting specific SET operations Some SET operations cause the system to shutdown or restart. You can permit these special SET operations or forbid them. 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 Agents are installed and on the version of the ServerView Agents. For a detailed description, "Installing ServerView Agents" on page 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 Agents are installed and on the version of the ServerView Agents. For a detailed description, "Installing ServerView Agents" on page 29. ServerView Agents for Windows 20

21 2.3 SNMP security concept This option only applies to ServerView Agents. SET operations for other SNMP agents are not affected SET Operations with user authentication You can restrict access to SET operations and protect the execution of SET operations with a user authentication. Here you can choose between starting the user authentication routine at the beginning of each session on a managed server or starting the user authentication at the start of each new SET operation. For user authentication, you must make the following settings on the managed server as well as on the management station. Entity Settings managed server Define user and user group Assign user to specific user group State the specified user group during installation of the agent management station Specify the user in the Operations Manager Login tab. 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 identification. You define the user in the Login tab in the Server Properties window. In this example this would be SVUSER. ServerView Agents for Windows 21

22 2.3 SNMP security concept Figure 2: 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 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. ServerView Agents for Windows 22

23 2.4 Configuring SNMP services SNMP security concept Configure the security settings under Windows during installation of the agent: 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. 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 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: 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. 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. ServerView Agents for Windows 23

24 2.4 Configuring SNMP services 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. 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). Trap Destination IP address of the management station to which the ServerView Agents send traps. 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. ServerView Agents for Windows 24

25 2.4 Configuring SNMP services Windows Server 2008 / 2012 / 2016 When you have completed installing Windows Server 2008, Windows Server 2012, or Windows Server 2016 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/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 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. Doubleclick 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. ServerView Agents for Windows 25

26 2.4 Configuring SNMP services 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. 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. ServerView Agents for Windows 26

27 2.4 Configuring SNMP services 4. Start SNMP service Start the SNMP service under Services. Select Start from the context menu 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 2016, Windows Server 2012, or Windows Server 2008 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 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 ServerView Agents for Windows 27

28 2.4 Configuring SNMP services 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. ServerView Agents for Windows 28

29 3.1 Installing and configuring agents 3 Installing ServerView Agents When using PKI (Public Key Infrastructure) for client authentication: Client authentication prevents the managed server from being accessed by a nontrusted management station or by a non-privileged application running on the management station. You have the option to either initially install the certificate files together with the ServerView Agents or to install the certificate files on a managed server where the ServerView Agents have already been installed. Installing the certificate files together with the ServerView Agents requires that the certificate files have already been installed on the managed server before the agents are actually installed. For details refer to the "User Management in ServerView" user guide. 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 agent 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 23). Before you start installation, you should carefully plan your security concept of ServerView. For further information, see "SNMP security concept" on page 20. After ServerView Agents is installed, you will find a ThirdPartyLicenseReadme.txt file in the installation directory (default: C:\Program Files\Fujitsu\ServerView Suite\Agents). This file contains information on the third party software in ServerView Agents for Windows. 3.1 Installing and configuring agents Silent installation of the ServerView Agents is described in "Installing via the command 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 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. ServerView Agents for Windows 29

30 3.1 Installing and configuring agents 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 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. 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: Typical (High security) Typical (Administrator account based security) ServerView Agents for Windows 30

31 3.1 Installing and configuring agents Typical (Without any security) 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 42. 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. 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. ServerView Agents for Windows 31

32 3.1 Installing and configuring agents Expert (Advanced users) The expert mode provides the following options: 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. Figure 4: Expert Settings window Agents... Opens a window where you can change the ServerView Agents 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. ServerView Agents for Windows 32

33 3.1 Installing and configuring agents 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 47). 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 17). 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. Trap Forwarding tab System Shutdown tab Security Settings tab Threshold Monitoring tab 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: critical (for critical traps) major (for important traps) minor (for less important traps) informational (for informative traps) ServerView Agents for Windows 33

34 3.1 Installing and configuring agents Weighting for the event log types is as follows: Trap weighting critical and major traps Error minor traps informational traps Event log type Warning 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. Figure 5: 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 ServerView Agents for Windows 34

35 3.1 Installing and configuring agents seconds. If you have to save large amounts of data to the hard drive you should increase this value accordingly. You can choose to start an application (a shutdown job) before the soft shutdown is initiated. 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 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%. 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. ServerView Agents for Windows 35

36 3.1 Installing and configuring agents 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. You can define the security settings on the tab shown below: Figure 7: 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. ServerView Agents for Windows 36

37 3.1 Installing and configuring agents 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. 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. Threshold Monitoring tab Via the Threshold Monitoring you can activate or deactivate threshold monitoring for the Threshold Manager. Figure 8: Threshold Monitoring tab ServerView Agents for Windows 37

38 3.1 Installing and configuring agents 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. Figure 9: Destination Folder window By default the ServerView Agents 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 38

39 3.1 Installing and configuring agents Figure 10: 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. ServerView Agents for Windows 39

40 3.1 Installing and configuring agents If you select Custom and then Next, the following window opens: Figure 11: Custom Setup window This window offers the following features for selection: Feature Standard Agents S.M.A.R.T. Support Microsoft SMS Integration MIB Files Configuration Tools Description SNMP agents required for Operations Manager. S.M.A.R.T. support for event monitoring. Software for automatically creating MIF files for Microsoft SMS V 1.2 and V 2.0. ServerView MIB files. Tools for agent and system configuration. Support Tools Tools for service technician Diagnostic Tools Various diagnostic tools (e.g. for installation testing), for support purposes only. ServerView Agents for Windows 40

41 3.1 Installing and configuring agents Feature System Monitor Web Interface Windows Management Integration Virtualization Management Agent HP Systems Integration Asset CLI PrimeCollect Help Files Remote Connector Service Server Control Service CIM Provider Description Tool for system monitoring and updating the managed server locally. Integration into Microsoft Windows Management (WMI). Provides performance data for virtual machines (Xen, Hyper-V, VMWare). Integration into HP SIM (System Insight Manager) Custom line utility for reading system asset information Tool for collecting and storing information about the hardware and software of PRIMERGY servers. Help files Provides HTTP-based services. Basic service required. 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. ServerView Agents for Windows 41

42 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 tools Windows Server 2008/2016: After successful installation, different tools are available in the Start menu. For example, Windows Server 2008: Start Programs Fujitsu ServerView Suite Agents 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. ServerView Agents for Windows 42

43 3.2 Installed tools On the Start page you can build applications groups. Select the relevant applications and 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 Start page, e.g. group ServerView. ServerView Agents for Windows 43