ServerView Operations Manager V8.50

Transcription

1 User Guide - English FUJITSU Software ServerView Suite ServerView Operations Manager V8.50 Server Management Edition October 2018

2 Comments Suggestions Corrections The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs. Feel free to send us your comments by to Documentation creation according to DIN EN ISO 9001:2015 To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard DIN EN ISO 9001:2015. cognitas. Gesellschaft für Technik-Dokumentation mbh Copyright and trademarks Copyright 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 are trademarks of the Apache Software Foundation. ServerView Operations Manager 2

3 Contents 1 Introduction Target groups and purpose of this manual Hardware/Software requirements What's new ServerView Suite link collection Documentation for the ServerView Suite Notational conventions Product names - conventions Naming of the PRIMEQUEST systems 25 2 Architecture and Features Architecture Features User and security concept ServerView Operations Manager - a Java application Cipher suite configuration sets Recovery functions Prefailure Detection and Analysis (PDA) Monitoring functions High Availability - HA Transaction concept of Operations Manager ServerView agentless management Agentless mode Agentless mode with Agentless Service Agentless Management with ServerView Agentless Service Support for VMware ESX Server and VMware vsphere Hypervisor (ESXi) Using a restrictive user account (Read-only) to monitor a VMware ESXi host in ServerView Operations Manager and/or ServerView RAID Switchable methods of discovering ESXi hosts version 6 and higher Functions protected by access authorizations 49 ServerView Operations Manager 3

4 Contents Using SNMPv3 with ServerView Operations Manager Integration options of ServerView Operations Manager Integrations in ServerView Operations Manager ServerView Installation Manager ServerView Virtual-IO Manager 57 3 Using ServerView Operations Manager Starting ServerView Operations Manager Starting ServerView Operations Manager on a central management station Starting ServerView Operations Manager on a management console The Central Authentication Service ServerView Operations Manager start page ServerView Operations Manager main window Exiting ServerView Operations Manager Property window Buttons in the property windows Tabs in the property windows Menus Menus in the menu bar Context menus in the ServerList window Menus in the Single System View window Menus in the ServerView <PRIMEQUEST_chassis_name> window Menus in the SV Storage window Menus in the PRIMEQUEST Partition window Icons Icons in the ServerList window Icons in the ServerView [server_name] window Icons in the Device View window Icons in the Busses and Adapters window Icons in the Alarm Monitor window Other icons Administering the server list ServerView database Server list 105 ServerView Operations Manager 4

5 Contents Blade Servers in the server list Server with Agentless Service in the server list Multi-node servers in the server list Cluster-in-a-Box (CiB) systems in the server list Virtual Servers in the server list VMware in the server list Citrix XenServer server / Xen server in the server list KVM servers in the server list Hyper-V Servers in the server list VMware ESXi hosts as normal servers in the server list PRIMEPOWER Systems in the server list Storage subsystems in the server list Baseboard Management Controller (BMC) in the server list PRIMEQUEST chassis in the server list Enabling SNMP Configuring SNMP PSA agent PRIMEQUEST chassis PRIMEQUEST chassis/primequest partition is not Manageable Server/server blade is not manageable Server not manageable/ management controller icon Defining and adding objects Adding objects via the "ServerBrowser" window Defining (includes discovering) objects via Server Address tab Defining (includes discovering) objects via the browser Adding objects to the server list Adding hosts with virtualization software as normal servers to the server list Adding VMware ESXi hosts as of version 6 and higher Adding TCP/IP devices to the server list Adding objects by importing archive data Adding objects by importing import files Importing objects via import files via ServerList menu 146 ServerView Operations Manager 5

6 Contents Importing objects via import files via command line interface Reinitializing the server Creating user-specific server groups Deleting objects Deleting networks, subnets or domains Deleting objects from the server list Deleting objects from the server list via command Clusters in the server list Checking the server list Recording archive data via the server list Suppressing the alarms for a server Creating new update jobs for servers Exporting the server list Exporting the server list via command line interface Defining settings for the server list Filtering server list entries Querying server data System status Environment Cooling Fan Configuration Temperature Mass Storage RAID information for VMware ESXi servers in the Single System View Power Supply Power Supplies Power Level Power Redundancy Configuration UPS Manager APC UPS System Board System Processors 177 ServerView Operations Manager 6

7 Contents Memory Modules Voltages BIOS Selftest Busses and Adapters Trusted Platform Module Performance Processors Memory Network Storage Others Network Network Adapters Network Interfaces Driver Monitor System Maintenance Battery Information System Event Log Server Properties ASR&R Boot Options Remote Management Remote Management (RSB, BMC) Remote Management (irmc) PrimeCollect Online Diagnostics Customer Self Service Virtualization Host Properties Virtual Machines Evacuation of virtual servers in the event of an error 207 ServerView Operations Manager 7

8 Contents 5.5 Server not manageable with management controller icon Server with BMC/iRMC, not manageable Querying blade server data Blade List BladeServer Status Environment Cooling Fan Configuration Temperature Power Supply System Maintenance Querying PRIMEQUEST Partition data System Status System Boards System Processors Memory Modules Voltages IOBs Environment Cooling Temperature Mass Storage BIOS Selftest Busses and Adapters Performance Network Interfaces System Querying PRIMEQUEST chassis data Partition List System Status Hardware Components 235 ServerView Operations Manager 8

9 Contents MMB (Management Board) SB (System Board) IOB (Input/Output Board) GSPB (Giga LAN SAS and PCI Box connector Board) DVDB (DVD Board) SASU (Serial Attached SCSI Units) PCI Box (Peripheral Component Interconnect) Environment Fans Temperature Voltages Power Supply System Maintenance Querying storage subsystem data Configuration RAID Controller Enclosures Storage Pools Storage GUI Querying BMC/iRMC data Power Monitor Starting the Power Monitor Power Monitor - Server tab Power Monitor - Data tab One server or server blade on the Data tab Multiple servers on the Data tab 264 ServerView Operations Manager 9

10 Contents 12 Power management Configuring servers remotely Starting Advanced Video Redirection Creating a user/password list ServerView Status gadget for Windows FUJITSU Software ServerView Status app for Windows Communication paths Collecting diagnostics data On Windows systems On Linux systems WMI WMI architecture WMI users WMI infrastructure Managed objects WMI security WMI support in ServerView System requirements ServerView Agents as WMI providers ServerView classes FSCSV_ASR FSCSV_ASRSetting (association class) FSCSV_AssociatedCooling (association class) FSCSV_AssociatedSensor (association class) FSCSV_AssociatedSupplyVoltageSensor (association class) FSCSV_Chassis FSCSV_ComputerSystem FSCSV_FailReaction FSCSV_FailSetting (association class) FSCSV_Fan FSCSV_FRU FSCSV_FRUPhysicalElements (association class) 299 ServerView Operations Manager 10

11 Contents FSCSV_ManagementController FSCSV_OperatingSchedule FSCSV_OperatingScheduleSetting (association class) FSCSV_PowerOnOffInformation FSCSV_PowerOnOffStatistics (association class) FSCSV_PowerSupply FSCSV_SystemEnclosure FSCSV_Tachometer FSCSV_TemperatureSensor FSCSV_VoltageSensor FSCSV_Watchdog WMI scripting Structure of a WMI script WMI script (example) WMI CIM Studio (example) Software License Agreement for End User 316 ServerView Operations Manager 11

12 1 Introduction ServerView Operations Manager (Operations Manager for short) is a free server management module of the Fujitsu ServerView Suite. It is used for central administration of industry-standard servers which run the operating systems Windows and Linux (SUSE and Red Hat) or which serve as hosts for virtual machines (VMs) that use hypervisors such as VMware ESX/ESXi, Citrix XenServer or Hyper-V. The standardized management of all servers occurs via one or more central management stations, which you can access from any workstation in the network that has a popular web browser and the Java Runtime Environment. Operations Manager controls the individual systems, including critical hardware components such as processors, RAM, hard disks, fans, pumps, 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 components and their resources ServerView Operations Manager 12

13 Very easy operation thanks to ergonomic software: clearly laid out, intelligent user guidance and supportive help system ServerView Operations Manager Operations Manager offers numerous components for the different management areas: Figure 1: Start page This manual describes Operations Manager with its main components. Other components are described in separate manuals. ServerView Operations Manager 13

14 Management area Server management (ServerList) Operations Manager component ServerList Single System View Power Management Described in chapter "Administering the server list" on page 104 chapters "Querying server data" on page 158, "Querying blade server data" on page 212, "Querying PRIMEQUEST Partition data" on page 222, "Querying PRIMEQUEST chassis data" on page 232, "Querying storage subsystem data" on page 247, "Querying BMC/iRMC data" on page 251 chapter "Power management" on page 266 Administration ServerBrowser chapter "Administering the server list" on page 104 Server Configuration Base Configuration Wizard chapter "Configuring servers remotely" on page 269 "ServerView Base Configuration Wizard", user guide Asset Management Archive Manager "ServerView Archive Manager", user guide Inventory Manager "ServerView Inventory Manager", user guide Event Management Alarm Monitor "ServerView Event Manager", user Alarm Configuration guide Threshold Manager "ServerView Threshold Manager", user guide Monitoring Performance Manager "ServerView Performance Manager", user guide Power Monitor Table 1: ServerView Operations Manager chapter "Power Monitor" on page 252 ServerView Operations Manager 14

15 Management area Operations Manager component Described in Update Management Update Manager "ServerView Update Repository Manager Management", user guide Download Manager Configuration Security User Management "User Management in ServerView, Centralized Authentication and role-based Authorization", user guide Table 1: ServerView Operations Manager Other ServerView Suite modules As well as the free ServerView Operations Manager, the Fujitsu ServerView Suite includes a number of other, mainly free server management modules as well as some chargeable modules. These include: ServerView Installation Manager ServerView Scripting Toolkit ServerView Virtual I/O Manager ServerView Operations Manager 15

16 1.1 Target groups and purpose of this manual 1.1 Target groups and purpose of this manual This manual is intended for system administrators, network administrators and service technicians who already have a basic knowledge of hardware and software. The manual provides a brief overview of the fundamentals of server monitoring and describes the user interface of ServerView Operations Manager. A separate chapter is devoted to server management with WMI (Windows Management Instrumentation). 1.2 Hardware/Software requirements The most up-to-date information on the hardware and software requirements for ServerView can be found in the ServerView Operations Manager Installation Guides (Windows/Linux), in the "Release Notes" information file, which can be opened e.g. from the ServerView program group, and in the product specifications for ServerView. ServerView Operations Manager 16

17 1.3 What's new 1.3 What's new This edition of the manual applies to ServerView Operations Manager as of V8.50 and replaces the following online manual: "ServerView Suite, ServerView Operations Manager V8.40", June 2018 edition. This manual has been updated to reflect the latest software status and offers the following changes and enhancements: Using SNMPv3 as of ServerView Operations Manager V8.50, see "Using SNMPv3 with ServerView Operations Manager" on page 51. Defining SNMP Settings, see "Server Properties" on page 196. Assigning SNMP Settings for each host, see "Creating a user/password list" on page 273. Specifying a non-default UDP port for connecting to the monitored server, see "Server Properties" on page 196 and "Tabs in the property windows" on page 72. SNMPv3 Settings via the browser, see "Defining (includes discovering) objects via the browser" on page ServerView Suite link collection Via the ServerView Suite link collection, Fujitsu provides you with numerous downloads and further information on the ServerView Suite and PRIMERGY servers. Under ServerView Suite, links are offered on the following topics: Forum Service Desk Manuals Product information Security information Software downloads Training ServerView Operations Manager 17

18 1.4 ServerView Suite link collection Software downloads includes the following downloads: o o o Current software statuses for the ServerView Suite as well as additional Readme files. Information files and update sets for system software components (BIOS, firmware, drivers, ServerView Agents and ServerView Update Agent) for updating the PRIMERGY servers via ServerView Update Manager or for locally updating individual servers via ServerView Update Manager Express. The current versions of all documentation on the ServerView Suite. You can retrieve the downloads free of charge. Under PRIMERGY Server, links are offered on the following topics: Service Desk Manuals Product information Spare parts catalogue Access to the ServerView Suite link collection You can reach the link collection of the ServerView Suite in various ways: 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. 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. ServerView Operations Manager 18

19 1.5 Documentation for the ServerView Suite 1.5 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 Operations Manager 19

20 1.6 Notational conventions 1.6 Notational conventions The following notational conventions are used in this manual: Convention Explanation Indicates various types of risk, namely health risks, risk of data loss and risk of damage to devices. Indicates additional relevant information and tips. bold monospace monospace semibold blue continuous text pink 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 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. Table 2: Notational conventions References to text or sections of text in this manual are shown with the chapter or section heading and the page on which that chapter or section begins. 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 Operations Manager 20

21 1.7 Product names - conventions 1.7 Product names - conventions In this document, product names used in the text are abbreviated as follows: Windows Server 2019 Product name Microsoft Windows Server 2019 Standard Microsoft Windows Server 2019 Datacenter Microsoft Windows Storage Server 2019 Standard Notation in the text Windows Server 2019 Windows Table 3: Product names - Windows Server 2019 Windows Server 2016 Product name Microsoft Windows Server 2016 Standard Microsoft Windows Server 2016 Essentials Microsoft Windows Server 2016 Datacenter Microsoft Windows Storage Server 2016 Standard Notation in the text Windows Server 2016 Windows Table 4: Product names - Windows Server 2016 Windows Server 2012 and 2012 R2 Product name Microsoft Windows Server 2012 Standard Microsoft Windows Server 2012 Essentials Microsoft Windows Server 2012 Datacenter Microsoft Windows Server 2012 Foundation Microsoft Windows Server 2012 R2 Standard Microsoft Windows Server 2012 R2 Essentials Microsoft Windows Server 2012 R2 Datacenter Microsoft Windows Server 2012 R2 Foundation Microsoft Windows Storage Server 2012 Standard Notation in the text Windows Server 2012 Windows Table 5: Product names - Windows Server 2012 and 2012 R2 ServerView Operations Manager 21

22 1.7 Product names - conventions Windows Server 2008 and 2008 R2 Product name Microsoft Windows Server 2008 Standard Microsoft Windows Server 2008 Enterprise Microsoft Windows Server 2008 Datacenter Microsoft Windows Server 2008 Foundation Microsoft Windows Web Server 2008 Microsoft Windows Small Business Server 2008 Standard Microsoft Windows Small Business Server 2008 Premium Microsoft Windows Server 2008 Standard x64 Edition Microsoft Windows Server 2008 Enterprise x64 Edition Microsoft Windows Server 2008 Datacenter x64 Edition Microsoft Windows Server 2008 Foundation x64 Edition Microsoft Windows Small Business Server 2008 Standard x64 Edition Microsoft Windows Small Business Server 2008 Premium x64 Edition Microsoft Windows Server 2008 R2 Standard Microsoft Windows Server 2008 R2 Enterprise Microsoft Windows Server 2008 R2 Datacenter Microsoft Windows Server 2008 R2 Foundation Microsoft Windows Web Server 2008 R2 Microsoft Windows Small Business Server 2008 R2 Standard Microsoft Windows Small Business Server 2008 R2 Premium Table 6: Product names - Windows Server 2008 and 2008 R2 Notation in the text Windows Server 2008 Windows Server 2008 x64 Windows Server 2008 R2 Windows ServerView Operations Manager 22

23 1.7 Product names - conventions Linux Product name Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 7 SUSE Linux Enterprise Server 11 SUSE Linux Enterprise Server 12 SUSE Linux Enterprise Server 15 Table 7: Product names - Linux Notation in the text Red Hat Linux RHEL6 RHEL7 SUSE Linux SUSE SLES11 or SLES 11 SUSE SLES12 or SLES 12 SUSE SLES15 or SLES 15 Linux Virtualization software Product name Notation in the text Microsoft Hyper-V Server Hyper-V Server Hyper-V Microsoft Hyper-V Server 2008 Hyper-V Server 2008 Microsoft Hyper-V Server 2008 R2 Hyper-V Server 2008 R2 Microsoft Hyper-V Server 2012 Hyper-V Server 2012 Microsoft Hyper-V Server 2012 R2 Hyper-V Server 2012 R2 Microsoft Hyper-V Server 2016 Hyper-V Server 2016 Microsoft Hyper-V Server 2019 Hyper-V Server 2019 VMware ESXi 5.5 ESXi 5.5 VMware VMware ESXi 6.0 ESXi 6.0 VMware ESXi 6.5 ESXi 6.5 Citrix XenServer Citrix XenServer Table 8: Product names - Virtualization software ServerView Operations Manager 23

24 1.7 Product names - conventions Product name Red Hat Enterprise Linux 5 Xen Red Hat Enterprise Linux KVM Notation in the text Xen Server KVM Table 8: Product names - Virtualization software ServerView Suite Software Products Product name ServerView Installation Manager ServerView Installation Manager ServerView Operations Manager ServerView Inventory Manager ServerView Archive Manager ServerView Event Manager ServerView Threshold Manager ServerView Performance Manager ServerView Virtual-IO Manager ServerView Fabric Manager ServerView Update Manager ServerView Download Manager ServerView Online Diagnostics ServerView System Monitor irmc (integrated Remote Management Controller) irmc S2 / irmc S3 / irmc S4 / irmc S5 (integrated Remote Management Controller) ServerView Remote Management Frontend PrimeUp installation tool PRIMERGY Support Package Local Service Concept Fujitsu DeskView Integration in Microsoft System Center Configuration Manager Notation in the text Installation Manager Installation Manager Operations Manager Inventory Manager Archive Manager Event Manager Threshold Manager Performance Manager Virtual-IO Manager or VIOM Fabric Manager Update Manager Download Manager Online Diagnostics System Monitor irmc irmc S2/S3/S4/S5 Remote Management Frontend PrimeUp PSP LSC DeskView-Integration Table 9: Product names - ServerView Suite Software Products ServerView Operations Manager 24

25 1.7 Product names - conventions Naming of the PRIMEQUEST systems This manual only describes PRIMEQUEST systems as of the PRIMEQUEST 1000 series. The models from the different series are referred to by the collective name PRIMEQUEST. Where a distinction is made between the individual systems, this is explicitly stated. ServerView Operations Manager 25

26 2.1 Architecture 2 Architecture and Features 2.1 Architecture The architecture of ServerView Operations Manager is based on a management console, a central management station (CMS) and the managed servers. Figure 2: 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 Operations Manager 26

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

28 2.2 Features 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 2.2 Features ServerView Operations Manager offers functions for monitoring servers and quickly correcting errors, end-of-life monitoring for the early recognition of the possible failure of a board, and an event management system with numerous options to ensure that error messages are transmitted. The archive function allows you to ascertain and store system and operating data from servers. ServerView Operations Manager also provides support for storage extension units and uninterruptible power supplies from APC and Fujitsu. ServerView Operations Manager offers a role-based user and security concept, which controls access to the ServerView Operations Manager functions. You will find an overview of the features available in ServerView Operations Manager in the following text. ServerView Operations Manager 28

29 2.2 Features User and security concept ServerView Operations Manager offers a user and security concept which comprises both an authentication mechanism including Single Sign-On (SSO), and authorization for all functions of the various ServerView components. Key elements of the user and security concept include: Authorization Central authorization Single sign-on Authorization Access to the functions of ServerView Operations Manager is protected by user IDs. So you must first log in if you want to use the functions of ServerView Operations Manager. Login occurs via predefined user names. Depending on your job within the server management, the administrator will assign you the user name that gives you access to the exact functions of ServerView Operations Manager that you need for your work. With a standard installation, ServerView Operations Manager offers four user names, each of which is assigned a predefined role. These roles are defined through the task-oriented bundling of different privileges. The following figure illustrates the concept of role-based user management with the predefined roles Administrator, Operator, Monitor and UserManager. Figure 3: Example of role-based assignment of user permissions The Monitor role (user name monitor with predefined password admin) is required for read access (e.g. to view configuration data or the status of the servers). ServerView Operations Manager 29

30 2.2 Features The Operator role (user name operator with predefined password admin) is required for read and write access. An operator, for example, can use the Threshold Manager to monitor managed nodes using defined thresholds. The Administrator role (user name administrator with predefined password admin) is required in order to use all the functions with the exception of user management. The UserAdministrator role (user name UserManager with predefined password admin) is required in order to perform comprehensive user management using the User Management wizard. Central authorization To allow you to use ServerView Operations Manager on various central management stations under the same user name, and therefore not have to remember several different user names, ServerView Operations Manager offers central authorization via a directory service. The directory service provides all the data necessary for the authorization. When you install the ServerView Operations Manager software, you have the option of also installing the directory service ApacheDS. In this case, after successful installation the three predefined standard user names are automatically available. If you decide to use an existing directory service, you must integrate the user management of ServerView Operations Manager accordingly. Single Sign-On (SSO) The login procedure is based on the single sign-on mechanism. This means that, once you have authenticated yourself to ServerView Operations Manager, you can start other components without being asked to log in again (your login is valid for 24 hours). The login data is clarified internally in each case. With the SSO mechanism, the Central Authentication Service (CAS) takes over the job of authentication. CAS is automatically installed with the ServerView Operations Manager software. A detailed description of the user and security concept is provided in the documentation "User management in ServerView". ServerView Operations Manager 30

31 2.2 Features ServerView Operations Manager - a Java application ServerView Operations Manager is a Java application that can be started on the management console with one click, without needing a web browser, provided ServerView Operations Manager has been downloaded from the central management station (CMS). Every time Operations Manager is started subsequently, the system checks whether there is a new version on the CMS. If so, only the updated software components from this version are downloaded. This avoids unnecessary downloads while ensuring that the latest version of Operations Manager is always available on the management console. Launching ServerView Operations Manager with Java Web Start Figure 4: Launching ServerView Operations Manager with Java Web Start On the management console, enter the following address via a standard web browser: This web address is used to download and open the JNLP file. This file in turn launches the Java Web Start program (1), which is installed together with the Java Runtime Environment. ServerView Operations Manager 31

32 2.2 Features On the first start, the Java Web Start program downloads the ServerView Operations Manager Java application from the management station, stores it in the cache and then launches it (2). An icon is created on the desktop for starting ServerView Operations Manager again later. Additionally under Windows, a link is automatically stored in the start menu. On subsequent starts, ServerView Operations Manager is launched directly on the management console without downloads. By default, Java Web Start automatically checks on every subsequent start whether an update is available on the management station. If so, only the updated components of the Java application are downloaded. To run, the Java Web Start program requires Oracle Java Runtime Enterprise (JRE) version 1.7 or higher Cipher suite configuration sets ServerView Operations Manager offers three defined configuration sets: Modern (strongest cipher suite set) Intermediate Old (weakest cipher suite set) These three cipher suite sets are equivalent to the Modern/Intermediate/Old sets defined in the Mozilla document Modern settings are the most secure. Only the latest SSL protocol version TLSv1.2 is allowed. So it will pass vulnerability scannings without errors. The Intermediate configuration set allows TLSv1.2, TLSv1.1 and TLSv1.0. If a client which can be connected to ServerView Operations Manager allows only the SSL protocol version SSLv3, the Old configuration set should be selected. Otherwise a connection cannot be established. This set is the weakest cipher suite set and allows TLSv1.2, TLSv1.1, TLSv1.0, and SSLv3. By default the Intermediate set is configured. The configuration of the cipher suites and SSL protocols is stored in the <ServerView Operations Manager installation directory>/tomee/conf/server.xml configuration file. Cipher suites and SSL protocols used by ServerView Application Server can be configured during ServerView Operations Manager installation. After ServerView Operations Manager is installed, you can modify the configuration of cipher suites and protocols by editing the server.xml configuration file. For further information see the "Installing ServerView Operations Manager Software under Windows" installation guide and "Installing ServerView Operations Manager Software under Linux" installation guide. ServerView Operations Manager 32

33 2.2 Features Recovery functions A server can be monitored, and its reaction in the event of an error can be defined with the help of ASR&R (Automatic Server Reconfiguration and Restart). This enables a proper shutdown to be initiated or a reboot with the automatic disabling of defective parts to be performed. The ASR&R properties of a managed server are displayed in the single system view (see "ASR&R" on page 201) Prefailure Detection and Analysis (PDA) The PDA functionality (Prefailure Detection and Analysis) is available for early detection of errors. The PDA feature enables the early detection of errors in certain server components. The following components are monitored: Cooling systems CMOS battery Hard drives on SCSI and RAID controllers that support the S.M.A.R.T. standard Memory modules Central processing unit (CPU) PDA periodically checks particular properties or activities of the components. If errors are indicated, e.g. if a defined threshold is exceeded, the administrator is informed immediately by the alarm management. This allows separate components to be exchanged in time before a total failure occurs. S.M.A.R.T. Standard S.M.A.R.T. (Self Monitoring and Reporting Technology) enables the early detection of hard disk errors. This is achieved by S.M.A.R.T. algorithms, which monitor disk parameters, detect impending failures and report them to the SCSI controller or host. The S.M.A.R.T. concept can only detect so-called predictable errors on the basis of the parameter values. Errors that occur unexpectedly due to a sudden power or mechanical failure, for example, cannot be anticipated by this method. S.M.A.R.T. is supported by all SCSI drives and is also available for a number of IDE drives. The effectiveness of the early warnings of impending errors primarily depends on the efficiency of the algorithms and the number of monitored parameters. These components are vendor-specific and may hence differ for various hard disk types. ServerView Operations Manager supports S.M.A.R.T.-compatible hard disks on both SCSI and RAID controllers. If S.M.A.R.T. reports an impending failure, a trap is triggered. For RAID controllers, the drive with the S.M.A.R.T. error is displayed in a special color (magenta). ServerView Operations Manager 33

34 2.2 Features The default setting is disabled. During the ServerView Agents setup, you are asked if the S.M.A.R.T. function should be set to enabled Monitoring functions The monitoring functions can be used to create an inventory of the hardware and permanently monitor various system parameters. This allows you, among other things, to: create an inventory of the hardware installed monitor all hardware components, including an operating time counter for server operations implement end-of-life monitoring with timely notification prior to the failure of server modules immediately recognize the failure of a power supply module obtain detailed information on the bus system, processors, main memory, hard drives (including RAID drives), network controllers and other built-in controllers record the information obtained for the purpose of long-term monitoring (performance analyses, error frequency rates) monitor the SNMP-capable uninterruptible power supplies from APC as well as the PRIMERGY storage subsystems High Availability - HA ServerView Operations Manager supports the following high-availability environments: Windows 2008 R2/2012/2016 Hyper-V cluster with ServerView Operations Manager V5.30 and higher and ServerView Virtual-IO Manager installed on a virtual machine with Windows Server operating system. VMware HA with ServerView Operations Manager and ServerView Virtual-IO Manager installed on a virtual machine with Windows Server operating system. This means that the central management station is a virtual machine running on a Windows 2008/2012/2016 Hyper-V cluster or in a VMware HA environment. ServerView Operations Manager 34

35 2.2 Features High-availability of Hyper-V cluster The following Hyper-V high-availability configurations will be supported: Operating system Admin server if HA Guest OS Hypervisor Windows Server 2008 R2 Datacenter (*) P P Windows Server 2008 R2 Enterprise (*) P P Windows Server 2008 R2 Standard (*) P P Windows Server 2008 R2 Foundation (*) P P Windows Server 2008 Standard (x86, x64) (*) P P Windows Server 2008 Enterprise (x86, x64) (*) P P Windows Server 2012 Datacenter (*) P P Windows Server 2012 Standard (*) P P Windows Server 2012 Essentials (*) P P Windows Server 2012 Foundation (*) P P Windows Server 2012 R2 Datacenter (*) P P Windows Server 2012 R2 Standard (*) P P Windows Server 2012 R2 Essentials (*) P P Windows Server 2012 R2 Foundation (*) P P Windows Server 2016 (*) P P [Hyper-V] [Hyper-V] [Hyper-V] [Hyper-V] [Hyper-V] [Hyper-V] [Hyper-V] [Hyper-V] [Hyper-V] [Hyper-V] [Hyper-V] [Hyper-V] [Hyper-V] [Hyper-V] [Hyper-V] Table 10: Supported Hyper-V high-availability configurations (*) The Windows Server Core Installation option is not supported for admin server and guest OS on VM. ServerView Operations Manager 35

36 2.2 Features To set up the Windows 2008/2012/2016 Hyper-V cluster and the virtual machine that will be controlled from it, click here for the Microsoft instructions: If there is a fault in the Hyper-V cluster node, the Microsoft cluster will perform a failover action of the Hyper-V environment to the other cluster node and restart the virtual machine that is acting as the central management station. Figure 5: Failover action of the Hyper-V environment to the other cluster node In the failover clustering of the Hyper-V environment, ServerView supports the cold migration of virtual machines. To setup the Hyper-V cluster, proceed as follows: On the primary node 1. Connect with shared storage. 2. Configure BIOS. 3. Install Hyper-V roles. 4. Install and configure EMC Solutions Enabler (if used). 5. Add a failover clustering function. 6. Create a Hyper-V virtual network. 7. Create clusters. 8. Prepare virtual machines. ServerView Operations Manager 36

37 2.2 Features 9. Register virtual machines in clusters. 10. Install and configure storage management software. 11. Install and configure VM management software. 12. Install and configure ServerView Operations Manager and ServerView Virtual-IO Manager. On the secondary node 1. Connect with shared storage. 2. Configure BIOS. 3. Install Hyper-V roles. 4. Install and configure EMC Solutions Enabler (if used). 5. Add a failover clustering function. 6. Create a Hyper-V virtual network. 7. Install Hyper-V roles. 8. Add a failover clustering function. 9. Create a Hyper-V virtual network. 10. Create clusters. 11. Prepare virtual machines. 12. Register virtual machines in clusters. 13. Operate the management station in a cluster. For details of items 7 to 13, see the Hyper-V manual. If an error occurs on a VM guest, the operation will continue if the VM guest is switched over. High availability of VMware HA To make use of the high-availability functionality of VMware HA, you must use the operating system VMware vsphere. VMware HA links up multiple ESX/ESXi servers to form a cluster with shared resources. If one host fails, VMware HA reacts immediately by restarting any affected virtual machine on a different host. The cluster is created and managed via VirtualCenter. For a detailed description of the high-availability functionality with VMware HA, visit HA functionality supported by ServerView Operations Manager HA functionality is supported by ServerView Operations Manager with the following transaction concept (see "Transaction concept of Operations Manager" on page 38). ServerView Operations Manager 37

38 2.2 Features Transaction concept of Operations Manager To support a high-availability concept on the central management station, which is located in a virtual machine in Hyper-V or on an ESX/ESXi host, the ServerView ServerList Service has been extended to allow for a transaction concept. This transaction concept guarantees that the ServerView database tables are always consistent, even in the case of a failover. For each individual server the consistency of the data is guaranteed. All data collected during a polling interval is stored within a transaction. This involves the following database tables: SERVER_LIST ServerInformation ServerNetwork SwitchBlades DeployLanInterface GROUP_LIST GROUP_SERVER ServerView Operations Manager 38

39 2.2 Features ServerView agentless management Management via the irmc S4/S5 without ServerView Agents and CIM Providers is referred to as "ServerView agentless management". There are two different modes of agentless management: Out-of-band management without installation of ServerView Agentless Service on the managed server is known as "agentless mode". Out-of-band management with additional installation of ServerView Agentless Service on the managed server is known as "agentless mode with Agentless Service" Agentless mode In agentless mode, the server is managed exclusively via the irmc S4/S5 of the managed server. On the managed server, neither ServerView Agents or CIM Providers nor ServerView Agentless Service are running. For this reason there is also no communication between the irmc S4/S5 and the operating system on the managed server. The consumers, such as ServerView Operations Manager and Nagios Plug-in, communicate with the irmc S4/S5 via the dedicated management LAN port only. There is no burden on the productive LAN. ServerView agentless management in agentless mode provides information about several system components, such as the motherboard, memory modules, power supplies, certain RAID controller and others. Nevertheless the monitoring capabilities are limited to components which are directly accessible by the irmc S4/S5 through I²C or other hardware interfaces. But there is no information available on the operating system, e.g. PrimeCollect data including OS event log. ServerView Operations Manager 39

40 2.2 Features Agentless mode with Agentless Service In agentless mode with Agentless Service, the server is managed exclusively via the irmc S4/S5 of the managed server. On the managed server, only ServerView Agentless Service is installed and activated. No ServerView Agents or CIM Providers are installed. Communication between ServerView Agentless Service and the irmc S4/S5 occurs via HTI (High Speed Transfer Interface). SNMP runs on the irmc S4/S5, not on the managed server itself. The consumers, such as ServerView Operations Manager and Nagios Plug-in, communicate with the irmc S4/S5 via the dedicated management LAN port only. Data exchange occurs via the management LAN, so there is no load at all on the productive LAN. As well as the information about several system components, such as the motherboard, memory modules, power supplies, RAID controller and others, ServerView agentless management in agentless mode with Agentless Service provides operating system-based information, e.g. PrimeCollect data including OS event log Agentless Management with ServerView Agentless Service Unlike the traditional server management of ServerView Suite, agentless management completely separates the management process from the productive process. The traditional server management requires the installation of ServerView Agents or ServerView CIM Providers on the managed server. Communication between the managed server and the central management station (CMS) occurs via the productive network if the operating system is running, and via the management network if not. ServerView agentless management requires ServerView Agentless Service, referred to as "Agentless Service" for short, to be installed on the managed server: Agentless Service collects operating system-based administrative information (currently still a subset of the information that the ServerView Agents deliver). Agentless Service communicates with the management software via the irmc S4/S5 and its dedicated management LAN port. Agentless Service needs less memory and less processing power on the managed server. ServerView agentless management therefore offers numerous advantages over the traditional server management: Optimizes resource utilization of the system Separates the productive and management networks Communicates exclusively with the irmc S4/S5, no management software connection on the managed server Supports data center security concepts ServerView Operations Manager 40

41 2.2 Features Offers management information regardless of whether the system is up and running Reduces maintenance overhead In cooperation with Agentless Service running on the server operating system, an online update extends the autonomous update capabilities of the irmc S4/S5 (embedded Lifecycle Management - elcm). The Agentless Service provides driver and firmware inventory data and finally installs the firmware updates and, on Windows systems, also the component drivers on the managed server while the system is up and running. Agentless Service is available for Windows and Linux systems, is easy to install, and requires no further configuration. As of ServerView Operations Manager V 7.0, Agentless Service is available for PRIMERGY and PRIMEQUEST servers. The concept of agentless management on PRIMEQUEST servers is slightly different from the concept presented above Support for VMware ESX Server and VMware vsphere Hypervisor (ESXi) VMware ESX Server makes it possible to use several virtual servers running different operating systems on a single computer, e.g. on the PRIMERGY RX600 S4 server. VMware ESX Server runs directly on the system hardware, thus providing a secure and uniform platform for simple implementation, administration and remote control of several operating systems. The Operations Manager also supports VMware vsphere Hypervisor (ESXi). You can use the Fujitsu CIM providers to monitor VMware vsphere based servers. In order to use the ServerView ESXi CIM providers version 6.31, you require ServerView Operations Manager version 6.31 or later. ServerView Operations Manager V6.31 for its part supports all existing versions of the ServerView ESXi CIM providers. For further information on the VMware vsphere Hypervisor (ESXi) support, see the "Installation ServerView ESXi CIM Provider" installation guide, "ServerView CIM Providers for Windows, Linux, and VMware ESXi" installation and user guide and "Monitoring of VMware-based PRIMERGY Servers with ServerView" user guide. VMware ESX Server allows you to: consolidate applications that run in different operating systems, in different operating systems in separate virtual servers on a single, scalable system, remotely control servers from any location, thus simplifying server maintenance, maintain the service level for processors, memory, network and hard disk resources via extended resource management functions and control general monitoring and management tasks via scripts. ServerView Operations Manager 41

42 2.2 Features Example: RX600 S4 Virtual Servers Windows Server Red Hat Enterprise Linux Windows Server... VMware ESXi/ESX Server Operating System ServerView Agent for VMware Server Hardware Figure 6: Virtual servers It is not possible to access the server hardware from virtual servers. Each virtual server is completely isolated and cannot access the resources of other virtual servers. VMware ESX is an additional level between the guest operating system and the server hardware. There is also an operating system-specific agent, the ServerView agent for VMware, installed at this level. VMware ESX thus ensures access to the server hardware and therefore monitoring of the hardware by ServerView. On the virtual servers, VMware supports the operating systems Microsoft Windows Server (as of Windows Server 2003), the Linux Enterprise versions of Red Hat (as of Red Hat Enterprise Linux 4) and the Linux Enterprise Versions of SuSE (as of SuSE Linux Enterprise Server 9). Information on installing the ServerView agent for VMware can be found in the "ServerView Agents for Linux" Installation and User Guide. ServerView Operations Manager 42

43 2.2 Features Since Update 4 for ESXi 3.5 and for newer versions including ESXi 4.1, VMware has disabled write access for the "free" version of ESXi. Start/stop virtual machines and Enter maintenance mode are considered by VMware to be write operations and are not available in free version. To use these operations with ESXi server, you will need to get a license (paid license) or revert back to older updates. The chargeable license version offers the same functionality as for the free versions of ESXi up to version 3.5 update 4. As of version 4, the free version of VMware is called VMware vsphere Hypervisor (ESXi). For further information follow these links: Using a restrictive user account (Read-only) to monitor a VMware ESXi host in ServerView Operations Manager and/or ServerView RAID Especially where a greater number of PRIMERGYs need to be monitored it is convenient in use to establish a read-only user. The way to do this differs on the version of VMware ESXi. This user is different from ESXi built-in account "readonly" user. Please set it up newly according to the following procedure. ServerView Operations Manager 43

44 2.2 Features Set up a read-only user in VMware ESXi 5.5/ Open vsphere Client and select Home Administration Roles Add Role. The Add New Role dialog is displayed. Figure 7: The Add New Role dialog 2. Add the new role Monitor under Name and check Host CIM CIM Interaction under All Privileges. 3. Go to Home Inventory Inventory and click on the Local Users & Groups tab. 4. Select Add... in the context menu of the Users View. The Add New User dialog is displayed. ServerView Operations Manager 44

45 2.2 Features Figure 8: The Add New User dialog 5. Add the new user monitor under Login. 6. Click to Permissions tab and select Add Permission in the context menu. The Assign Permissions dialog is displayed. Figure 9: The Assign Permissions dialog 7. Assign the role Monitor to the user monitor for the ESXi host. ServerView Operations Manager 45

46 2.2 Features 8. Click OK. 9. Login to the ESXi 5.5/6.0 host via SSH. 10. Edit /etc/group file and add the user monitor to the root group. After this your /etc/group file should look like: root:x:0:root,monitor monitor:x:1000: 11. Prevent the account (e.g. Monitor) from logging on. 12. Edit /etc/passwd file and replace the default shell for the user (e.g. Monitor) from /bin/sh into /sbin/nologin). After this your /etc/passwd file should look like: root:x:0:0:administrator:/:/bin/sh Monitor:x:1000:1000:ESXi User:/:/sbin/nologin 13. Logon to ServerView Operations Manager 14. In the Administration menu, select Users/Passwords. This opens the User Password window. 15. Under User name and Password, enter the new created user name and corresponding password respectively and confirm the password under Confirm Password. 16. Add host to the ServerView ServerList and check connectivity. Set up a read-only user in VMware ESXi 6.5 With ESXi V6.5 vsphere Client is no longer available. vsphere Web Client has to be used instead. 1. Open vsphere Web Client and select Host Manage Security & users Roles Add a role. The Add a role dialog is displayed. ServerView Operations Manager 46

47 2.2 Features Figure 10: The Add a role dialog 2. Add the new role Monitor under Role Name and check Root Host Cim. 3. Select Host Manage Security & users Users Add user. The Add a user dialog is displayed. Figure 11: The Add a user dialog 4. Add the new user monitor. 5. Select Host Actions Permissions Add user. The Manage permissions dialog is displayed. ServerView Operations Manager 47

48 2.2 Features Figure 12: The Manage permissions dialog 6. Assign the role Monitor to the user monitor for the ESXi host. 7. Click Add user. 8. Login to the ESXi 6.5 host via SSH. 9. Edit /etc/group file and add the user monitor to the root group. After this your /etc/group file should look like: root:x:0:root,monitor monitor:x:1000: 10. Prevent the account (e.g. Monitor) from logging on. 11. Edit /etc/passwd file and replace the default shell for the user (e.g. Monitor) from /bin/sh into /sbin/nologin). After this your /etc/passwd file should look like: root:x:0:0:administrator:/:/bin/sh Monitor:x:1000:1000:ESXi User:/:/sbin/nologin 12. Logon to ServerView Operations Manager 13. In the Administration menu, select Users/Passwords. This opens the User Password window. 14. Under User name and Password, enter the new created user name and corresponding password respectively and confirm the password under Confirm Password. 15. Add host to the ServerView ServerList and check connectivity. ServerView Operations Manager 48

49 2.2 Features Switchable methods of discovering ESXi hosts version 6 and higher You can discover ESXi hosts with VMware ESXi version 6 and higher via two different methods: Discovering ESXi hosts and establishing an authorized connection to the ESXi web services, using a user/password combination from the user/password list. Discovering ESXi hosts without setting credentials. This method allows you to detect ESXi hosts without attempting access to credentialprotected information on the node. This way, you can evade problems that occur due to unsuccessful authorization. An ESXi server discovered using this method will be displayed in the ServerBrowser window with its IP address as its host name and the information (no credential set) in the description. These ESXi servers can be added to the server list as usual, where they will appear as a non-manageable without any children (host and guests). To change this status, set a proper user/password combination and host name, either via the Server Properties window or the Reinitialize Server dialog box. You can switch between these methods via the Base Configuration Wizard, see the "Base Configuration Wizard" user guide Functions protected by access authorizations In some cases, ServerView Operations Manager requires a valid user/password combination in order to authenticate itself when requesting information or when executing actions on a managed server: For adding certain objects to the server list. For power management, to switch individual servers and server groups on and off from the central management station. For Threshold Manager, to change threshold definitions. The relevant user/password combinations must be stored on the managed objects with the necessary authorizations to execute these functions. ServerView Operations Manager 49

50 2.2 Features The following table shows you the objects for which this valid user/password combination must be entered in the user/password list of ServerView Operations Manager: Function Objects Authorization Adding objects to the server list BMC VMware server Citrix XenServer server / Xen server KVM server Hyper-V server ETERNUS DX60-S2/DX80- S2/DX90-S2 ETERNUS DX410-S2/DX440- S2/DX8700-S2 ETERNUS DX60-S3, DX100-S3, DX200-S3 ETERNUS DX60-S4, DX100-S4, DX200-S4, AF250 ETERNUS DX500-S3, DX600-S3, DX8700-S3, AF650 ETERNUS DX500-S4, DX600-S4, AF250-S2, AF650-S2 Read authorization Restrictive user ID (Readonly) 1) Read authorization Read authorization Administrator rights Standard authorization or administrator rights Power management PRIMERGY server with BMC Administrator rights VMware server Citrix XenServer server / Xen server KVM server Hyper-V server Administrator rights Administrator rights Read authorization Administrator rights Threshold Manager All managed servers Valid user ID Table 11: Overview of the functions protected by access authorizations 1) For further information, see "Using a restrictive user account (Read-only) to monitor a VMware ESXi host in ServerView Operations Manager and/or ServerView RAID" on page 43. You can create this user/password list via the Base Configuration Wizard (Access Control step) or via ServerView Operations Manager (Administration menu, item Users/Passwords). For how to do this, see "Creating a user/password list" on page 273. ServerView Operations Manager 50

51 2.2 Features Using SNMPv3 with ServerView Operations Manager This section describes a method for adapting SNMPv3 in ServerView Operations Manager earlier than version 8.50 that has been retained for compatibility reasons. As of ServerView Operations Manager V8.50, each monitored host can be individually configured to use SNMPv1 or SNMPv3 in any variants and with different parameters. The use of SNMPv3 by overwriting the SNMP default values of the system is not recommended. As of ServerView Operations Manager V7.10 SNMPv3 is supported. SNMPv3 introduces a new framework with a new format of SNMP messages, security issues, access control, and remote configuration of SNMP parameters. To use SNMPv3, you must make certain preparations on the managed server and the central management station. For communication between the central management station of ServerView operations manager and the ServerView Agents on the managed servers via version 3 of SNMP a common user must be configured on the communication end points. For detailed information on preparing the managed server and the central management station or technical requirements, see "Using SNMPv3 with ServerView Suite products - Overview". If you have prepared the managed server and the central management station you can enable SNMPv3 in ServerView Operations Manager. Using SNMPv3 as of ServerView Operations Manager V8.50 As of ServerView Operations Manager V8.50 you can set up different SNMP protocols for each server separately. You can simultaneously use SNMPv1 with a specified community or SNMPv3 with all variants of authentication and data protection using different access data. You can enable SNMP in ServerView Operations Manager via the SNMP Settings window of the Server Properties view, see "Server Properties" on page 196 or via the Server Browser view, see "Defining (includes discovering) objects via Server Address tab" on page 135. Using SNMPv3 up to ServerView Operations Manager V8.40 You have two options for enabling SNMPv3 in ServerView Operations Manager: via the V3 Setting configuration window via the configuration file snmp.conf ServerView Operations Manager 51

52 2.2 Features Enabling SNMPv3 via the V3 Setting configuration window You can open the V3 Setting configuration window of ServerView Operations Manager via SNMPv3 Settings in the Administration menu. The V3 Setting configuration window opens. Figure 13: V3 Setting configuration window The following information about the selected servers or server blades is provided: Enable V3 Sets protocol version 3 of SNMP. Security Name The user name defined for ServerView Operations Manager. Authentication Password The password for authentication. Privacy Password The password for encryption. ServerView Operations Manager 52

53 2.2 Features Security level The security level. None It is allowed to configure SNMPv3 without authentication and without encryption. authnopriv It is allowed to configure SNMPv3 with authentication and without encryption. authpriv It is only allowed to configure SNMPv3 with authentication and with encryption. Authentication algorithm The authentication algorithm used by the user. MD5 Message-Digest Algorithm 5 (MD5) is used for authentication. SHA Secure hash algorithm (SHA) is used for authentication. Privacy algorithm The encryption algorithm used by the user. DES Digital Encryption Standard is used for encrypting the SNMPv3 traffic. AES Advanced Encryption Standard (AES) 128-bit encryption is used for encrypting the SNMPv3 traffic.secure hash algorithm (SHA) is used for authentication. Saving the settings Click the Save button in the V3 Setting configuration window. Enabling SNMPv3 via snmp.conf SNMPv3 is enabled in ServerView Operations Manager by creating an additional configuration file snmp.conf which must be located in the following directories: Windows: C:\usr\etc\snmp\snmp.conf Linux: /etc/snmp/snmp.conf Content of snmp.conf snmp.conf must contain: defversion 3 defsecurityname <username> defsecuritylevel <level of security> defpassphrase <username> defauthtype <type of authentication algorithm type> defprivtype <type of encryption algorithm type> ServerView Operations Manager 53

54 2.2 Features defsecurityname The user name defined for ServerView Operations Manager. defsecuritylevel The security level. noauthnopriv It is allowed to configure SNMPv3 without authentication and without encryption. authnopriv It is allowed to configure SNMPv3 with authentication and without encryption. authpriv It is only allowed to configure SNMPv3 with authentication and with encryption. defpassphrase The password for both: authentication and encryption. If the passwords differ use the following settings: defauthpassphrase, defprivpassphrase. defauthpassphrase The password for authentication. defprivpassphrase The password for encryption. defauthtype The authentication algorithm used by the user. MD5 Message-Digest Algorithm 5 (MD5) is used for authentication. SHA Secure hash algorithm (SHA) is used for authentication. defprivtype The encryption algorithm used by the user. DES Digital Encryption Standard is used for encrypting the SNMPv3 traffic. AES Advanced Encryption Standard (AES) 128-bit encryption is used for encrypting the SNMPv3 traffic.secure hash algorithm (SHA) is used for authentication. Example defversion 3 defsecurityname testuser defsecuritylevel authnopriv defpassphrase testuser defauthtype MD5 defprivtype AES ServerView Operations Manager 54

55 2.2 Features For detailed information on creating a snmp.conf configuration file see "Using SNMPv3 with ServerView Suite products - Overview" Integration options of ServerView Operations Manager The use of standardized protocols and interfaces means that Operations Manager can easily be integrated into other management systems. The Operations Manager integration modules ensure the output of detailed information on the status of the servers on the console of the connected management system. PRIMERGY servers can thus be managed with a central enterprise management console (Single Point of Administration). Additional management functions such as network management, application management and software distribution can also be used without any problem for PRIMERGY servers. Integration modules are available for the following management systems: IBM Tivoli TME 10 Framework TE/C IBM Tivoli NetView HP OpenView Network Node Manager HP Operations Manager Microsoft MOM and SCOM 2007 Microsoft SMS and SCCM 2007 Nagios and BMC Patrol PRIMEPOWER ServerView Suite Some integration modules (e.g. Microsoft SMS, MOM) are provided on the ServerView Suite DVD and can be automatically installed on the management station when the Operations Manager software is installed. This is provided that the relevant management software is already installed on the system. The other integration modules (e.g. HP Operations Manager, IBM Tivoli TME NetView) are available on the special ServerView Integration CD. For further information on the integration modules, see the integration manuals and the data sheet ServerView Integration. ServerView Operations Manager 55

56 2.2 Features Integrations in ServerView Operations Manager Alongside the integration options offered by ServerView Operations Manager, it is also possible to integrate external applications in ServerView Operations Manager. These applications can then be called directly from the ServerView Operations Manager graphical user interface. As external applications could be integrated: ServerView Installation Manager ServerView Virtual-IO Manager ServerView Installation Manager The ServerView Installation Manager (referred to here as Installation Manager for short) is integrated into ServerView Operations Manager. When it is started, ServerView Operations Manager detects whether Installation Manager is installed on the central management station. If it is, the ServerView Operations Manager main window will contain the menu item Installation Manager in the Deployment menu, via which you can start Installation Manager. Installation Manager is delivered as part of the ServerView Suite. Within the ServerView Suite, Installation Manager represents the component for configuring and installing operating systems and other user management and server management software. Installation Manager also enables subsequent adjustments to system settings on systems that have already been installed. The operating system installation on the target system can be initiated locally using a DVD drive on that system or remotely with PXE boot using a deployment server. In preparation for the installation, Installation Manager wizards guide you through a series of configuration menus, where you compile all parameters required for system configuration and for the subsequent automatic operating system installation. You can save these parameters to a configuration file and use these to install additional servers with the same hardware architecture. You will find a detailed description of Installation Manager in the Installation Manager user guide. ServerView Operations Manager 56

57 2.2 Features ServerView Virtual-IO Manager ServerView Virtual-IO Manager (referred to here as Virtual-IO Manager or VIOM for short) is integrated into ServerView Operations Manager. When it is started, ServerView Operations Manager detects whether Virtual-IO Manager is installed on the central management station. If it is, the ServerView Operations Manager main window will contain the menu item Virtual-IO Manager in the Network Management menu, via which you can start Virtual-IO Manager. As an extension to ServerView Operations Manager, it is possible to manage a large number of PRIMERGY blade servers and PRIMERGY rack servers centrally by the central management station using VIOM. This includes virtualizing and, for blade servers, saving the server blade-specific I/O parameters (MAC addresses, WWN addresses, I/O connections including the boot parameters) and configuring and managing a blade server's Intelligent Blade Panel in a hardware-independent server profile. You will find a detailed description of Virtual-IO Manager in the Virtual-IO Manager user guide. ServerView Operations Manager 57

58 3 Using ServerView Operations Manager ServerView Operations Manager has a convenient graphical user interface and is hence very easy to operate. All functions can be accessed via pull-down menus. The operation of the menus and windows is based on conventional standards for graphical user interfaces and will therefore not be explained in more detail here. The following sections describe: how to start and exit ServerView Operations Manager, see "Starting ServerView Operations Manager" on page 59 and "Exiting ServerView Operations Manager" on page 69. the ServerView Operations Manager start page, see "ServerView Operations Manager start page" on page 62. the ServerView Operations Manager main window, see "ServerView Operations Manager main window" on page 64. the property windows, their buttons and tabs, see "Property window" on page 69, "Buttons in the property windows" on page 71 and "Tabs in the property windows" on page 72. an overview of the menu structure, see "Menus" on page 76. all the icons and their meanings, see "Icons" on page 90. ServerView Operations Manager also provides you with a comprehensive help system. If problems occur accessing the Operations Manager, see the "ServerView Suite Troubleshooting Guide" documentation. This documentation can be found at On a Windows-based management station you find the link under: 1. Windows Server 2012 and below: Start [All ]Programs Fujitsu ServerView Suite Operations Manager Trouble Shooting Guide 2. Windows Server 2016 and higher: Start Fujitsu Trouble Shooting Guide ServerView Operations Manager 58

59 3.1 Starting ServerView Operations Manager 3.1 Starting ServerView Operations Manager You can start ServerView Operations Manager either directly on the central management station or on any standard PC (management console) with intranet or Internet access and a web browser. If you get a security warning from Java when you start Operations Manager, you can ignore it by clicking No. How to avoid such messages in future is described in the ServerView Operations Manager Installation Guide for Windows Starting ServerView Operations Manager on a central management station To start ServerView Operations Manager on a central management station, you have the following options. 1. Enter the following web address via a suitable web browser: This web address is used to download and open the JNLP file. This will launch ServerView Operations Manager with Java Web Start. On a Windows-based management station you can also start ServerView Operations Manager with Java Web Start via the Windows start menu: 1. Windows Server 2012 and below: Start [All ]Programs Fujitsu ServerView Suite Operations Manager ServerView Operations Manager On a management station under Windows Server 2012 R2, the tiles for ServerView Operations Manager are no longer shown in the Windows Start menu. To add tiles to the Start menu proceed as follows: 1. Click on the white arrow at the bottom of the Start menu. The Apps menu is displayed. 2. Right-click on the Operations Manager app. Possible actions appear at the bottom of the Apps menu. 3. Click Pin to Start to show the Operations Manager app on the Start screen. 4. Select the Operations Manager app on the Start screen. 2. Windows Server 2016 and higher: Start Fujitsu ServerView Operations Manager The communication occurs via an SSL-secured (Secure Sockets Layer) connection. ServerView Operations Manager 59

60 3.1 Starting ServerView Operations Manager Starting ServerView Operations Manager on a management console To start ServerView Operations Manager on a management console, you have the following options. 1. Authorize yourself through the browser. The following window opens, where you can select the link to the Java Web Start file which will start ServerView Operations Manager. Figure 14: Java Web Start 2. Enter the following web address via a suitable web browser: This web address is used to download and open the JNLP file. This will launch ServerView Operations Manager with Java Web Start. The downloaded file can be opened immediately from the browser or saved on the management console to be run later. From now on, ServerView Operations Manager can be started without a web browser. ServerView Operations Manager 60

61 3.1 Starting ServerView Operations Manager The Central Authentication Service On startup the login window of the Central Authentication Service is displayed. Figure 15: Login window of the Central Authentication Service In this window, enter the user name and the password of the ID under which you are authorized to use Operations Manager. The option Domain is only displayed if the unified RBAC management is enabled. By default there are four user names with different roles: Administrator for the role Administrator (default password: admin) Operator for the role Operator (default password: admin) Monitor for the role Monitor (default password: admin) UserManager for the role UserAdministrator (default password: admin) For further information on role-based user management, see the "User Management in ServerView user guide. If the unified RBAC management is enabled and the option Domain is displayed, select the authentication domain of your user account. SERVERVIEW: Name of the ApacheDS domain. <domain>: Name of the domain of an external directory service (e.g. Active Directory). The domain name actually displayed has been determined during Operations Manager setup. ServerView Operations Manager 61

62 3.2 ServerView Operations Manager start page 3.2 ServerView Operations Manager start page When you launch ServerView Operations Manager, the following start page is displayed: Figure 16: Start page Depending on the role - or rather the privileges assigned to it - you will be allowed to use all or only some of the functions of ServerView Operations Manager. The functions you are not authorized to use are disabled (gray). For an overview of the functions available to you with a role, see the "User Management in ServerView" user guide. The title bar of the web browser contains the name of the ServerView Operations Manager component (on the start page ServerView Operations Manager, otherwise e.g. ServerList) that you have started, as well as the name of the central management station on which ServerView Operations Manager is installed. Note that, depending on the security settings of the web browser or the central management station, the URL of the current window may be displayed instead of the title. The first time you start ServerView Operations Manager as administrator after installation, the Base Configuration Wizard also starts automatically. This wizard guides you through the initial steps for using ServerView Operations Manager: Check whether the necessary requirements are met Make settings for the server browser (see "Defining and adding objects" on page 134) Create a user/password list for the managed servers (see "Creating a user/password list" on page 273) ServerView Operations Manager 62

63 3.2 ServerView Operations Manager start page Make basic definitions for the event management (see documentation for ServerView Event Manager). This requires the ServerView Event Manager to be installed on the central management station. Make basic definitions for the update management (see documentation for ServerView Update Management). This requires the ServerView Update Management to be installed on the central management station. Start and stop the performance and threshold monitoring (see documentation for ServerView Threshold Manager). If you do not want to automatically open the Base Configuration Wizard again when you start ServerView Operations Manager, select Do not show this wizard again automatically in the start window of the Base Configuration Wizard. You can also call up the wizard at any time via ServerView Operations Manager under the Administration menu. For further information see the "Base Configuration Wizard" user guide. Via the start page you can start the individual components of ServerView Operations Manager. To open the main window ServerList of ServerView Operations Manager, click the ServerList link under ServerList. ServerView Operations Manager 63

64 3.3 ServerView Operations Manager main window 3.3 ServerView Operations Manager main window Once you have started ServerList via the ServerView Operations Manager start page, the main window of ServerView Operations Manager is displayed showing the ServerView server list. Figure 17: ServerView Operations Manager main window The ServerView Operations Manager main window provides an overview of all the configured servers and user-defined groups. This window is the starting point for practically all the administrator management functions. The ServerView Operations Manager main window connects the server list with a component of the Event Manager, the Alarm Monitor. Depending on which function you have selected, a list section will contain a list of servers or alarm entries. There is also a navigation section, in which all servers and server groups are listed, and an information section, which displays details of an alarm. You select the function via the menu bar in the ServerView Operations Manager main window (ServerList or Event Management Alarm Monitor). The ServerView Operations Manager main window then is divided into five sections: ServerView Operations Manager 64

65 3.3 ServerView Operations Manager main window If you are logged in, the title bar shows the user name under which you are logged in. The title also contains the Logout link, via which you can log out. You can use the menu bar below the title bar to navigate between the ServerView Operations Manager functions: o o o o o o o ServerList Administration Asset Management Event Management Monitoring Update Management Security (only if ApacheDS is used as directory service) The individual menu-dependent menu items are listed in the bar below the menu bar. For further information on the menus in the menu bar, see "Menus in the menu bar" on page 77. The left-hand section displays the servers and server groups in a file tree structure. This is where you make your selection for the display in the right-hand section. If you move the mouse pointer over a server node in the file tree, a tooltip appears, showing the model of the node. If the server name is not displayed in full because the window is too small, the first line shows the server name and the second line shows the model. In the case of a virtualization group, the tooltip shows the virtualization type (VMware, Hyper-V, Xen / Citrix XenServer). The Server Tree bar contains a Search button on the right. You can use this to find servers with certain properties. By clicking the Search button you start the following Search Dialog. Figure 18: Search Dialog window In the Search String field you can enter the string you are looking for. The wildcards asterisk * and question mark? can be used. ServerView Operations Manager 65

66 3.3 ServerView Operations Manager main window In the Category list box you can select which server property is to be searched. You can choose from the following properties: o o o Server name: All names of servers are searched. IP address: All IP addresses connected in any way with a server are searched. This also includes internal addresses and not just the server's visible address. Serial number: All servers serial numbers are searched. You use the Search button to start searching and the Cancel button to stop the search process. If results are found, a temporary group is created, otherwise an error message is displayed. Figure 19: Search Groups window The name of the group shows the search category and the search string. All groups below Search Groups are temporary and are not stored in the database. Therefore these groups will be lost if the server list is closed. ServerView Operations Manager 66

67 3.3 ServerView Operations Manager main window The context menu for Search Groups is reduced: Figure 20: Context menu for Search Groups The top right-hand section of the window contains the list of managed servers (menu item ServerList). The icons in the status bar of the right-hand section indicate how many servers are in any particular state. You can use these icons to control the display in the server list. To do this, click the server states for which you want the corresponding servers to be displayed in the server list (e.g. only servers that are not manageable). All selected servers in the file tree are displayed in a server list below this status bar. This list contains the following information: o o o o o o o o the status icon together with the name of the associated system various icons that provide information about the server state and/or events the IP address of the server the server type and the installed operating system the serial number of the server the group membership of the server, under Group user-defined comments about the respective servers, under Local Note IPMI or SNMP protocols provided by Servers with ServerView Agentless Service, under Available Protocols You can sort the information in the server list by clicking the appropriate column in the server-list header. Depending on which column you choose, the entries are sorted alphabetically, numerically or by icon. For further information on icons, see "Icons in the ServerList window" on page 90. The width and the sequence of the columns in the ServerList window can be defined individually. The character sequence... indicates that the text does not fit in the column. ServerView Operations Manager 67

68 3.3 ServerView Operations Manager main window The ServerList window provides you with context menus for editing the server list. You can, for example: define new servers and enter them in the server list, copy servers to a user-defined server group, delete servers from the server list, access certain ServerView functions quickly, for example the entry of archive data or ignoring of alarms for a server. For further information on the context menus, see "Context menus in the ServerList window" on page 82. If you select the Alarm Monitor function by clicking an alarm icon (alarm bell) or via Event Management Alarm Monitor, the alarm list for the selected servers or server groups is displayed in this section. For further information on the alarm list, see the "ServerView Event Manager" user guide. In the bottom right-hand section of the window, you can display information on the alarm selected in the server list. You do this via the two tabs for the Alarm Monitor in the server list view: o o Alarm Details tab - contains a brief description of the alarm selected in the server list. Alarm Information tab - contains detailed information on the alarm as it is stored in the MIB. The latest alarm with the highest severity is displayed. Information on other alarms which may exist for the server is available via the Alarm Monitor. These can be alarms with older dates or lower severities. If you switch to the Alarm Monitor, you will see a further tab called Server Information in this section. This tab contains information about the server from which the alarm selected in the server list originated. For further details see the "ServerView Event Manager" user guide. This display area can be opened and closed as required. ServerView Operations Manager 68

69 3.4 Exiting ServerView Operations Manager 3.4 Exiting ServerView Operations Manager You exit ServerView Operations Manager via the Logout link in the title bar. 1. Click the Logout link. A window containing information on the logout process opens. 2. Confirm this window with OK. All ServerView Suite windows opened under your user name will be closed and you will be returned to the Central Authentication Service window. Always make sure after logout that all ServerView Suite windows opened under your user name have been closed. For security reasons you should also close the web browser. 3.5 Property window The following types of property windows exist in ServerView Operations Manager to allow you to make settings for object parameters (e.g. servers, blade servers, RSB and group parameters): If you want to define a new system (e.g. server, cluster, blade server), use the ServerBrowser property window. If you want to view or edit the parameters of a known system, use the Server Properties on <server> property window. If you want to view or edit the parameters for the ServerView Agents responsible for monitoring the system, use the ASR Properties on <server> property window. These various windows contain tabs, i.e. dialog boxes containing the parameters that you want to display or edit. There are different types of tabs for the different parameters. The property windows contain various buttons. For the meaning of these buttons, see "Buttons in the property windows" on page 71. The property windows are described in greater detail below. ServerBrowser property window You open the ServerBrowser property window via the menu Administration ServerBrowser or by selecting New Server in the server list context menu. In the property window, you can define new servers and enter them in the server list. You can use the tabs to define the parameters of the new server. When you have done this, click Apply. ServerView Operations Manager 69

70 3.5 Property window Server Properties property window You open the Server Properties property window for servers, server blades and clusters as follows: 1. Select one or more servers, server blades or clusters from the server list or select a group and then choose Server Properties from the context menu. You open the Server Properties property window for blade servers as follows: 1. Select a blade server from the server list and choose Server Properties from the context menu. If you have selected the blade server in the left-hand section of the ServerList window (in the file tree), then all the server blades associated with this blade server are displayed in the Server Properties property window. If you have selected the blade server in the list on the right of the ServerList window, then only the blade server is displayed. You open the Server Properties property window for PRIMEQUEST chassis, and PRIMEQUEST partitions as follows: 1. Select one or more PRIMEQUEST chassis or PRIMEQUEST partition systems from the server list or select a group and then choose Server Properties from the context menu. 2. If you have selected the PRIMEQUEST chassis in the left-hand section of the ServerList window (in the file tree), then all the PRIMEQUEST partitions associated with this PRIMEQUEST chassis are displayed in the Server Properties property window. If you have selected the PRIMEQUEST chassis in the list on the right of the ServerList window, then only the PRIMEQUEST chassis is displayed. Depending on your selection, you will now see all the servers in the server list (if you have chosen All Servers) or the servers in the selected server group in the right-hand column of the Server Properties property window. The first server in this list is selected by default. The values for this server are displayed on the tabs. At the bottom left-hand side of the property window, you will see the Check All button. If you click Check All, then all the listed servers are highlighted. The Check All button is then relabeled Uncheck All, which you can click to deselect all the highlighted servers. The Check All button is inactive in the Server Address, Remote Service Board and BMC tabs because the definitions in these tabs can only be entered separately for each individual server. The tabs display the values for the server that is highlighted in color in the right-hand column. You can change the values on the tabs in the Server Properties property window as you wish and select the servers for which these values are to apply. Click Apply if you want to save the values. ServerView Operations Manager 70

71 3.6 Buttons in the property windows When you click Apply, an attempt is made to log in to the selected server. If the server is configured in such a way that settings can be made without a password or if you have already saved the correct password for the server in the Login tab and the login is successful, then the values are set. If it was not possible to log in at the server successfully, then the Login dialog box is displayed before you can set the values. If an error occurs while you are setting the values, a message window is displayed. 3.6 Buttons in the property windows OK button If you click the OK button, then the values displayed in the current tab are taken over for all the selected servers. The dialog box closes. Apply button If you click the Apply button, then the values displayed in the current tab are taken over for all the selected servers. The dialog box remains open to allow you to make further settings. Cancel button If you click this button, then the dialog box is closed and no changes are made to the servers. Reset button If you click the Reset button, the changes you have made are undone and the settings revert to those of the previous Apply. Check All button Click this button if you want to select all the servers. If all the servers are selected when you click the Apply button, then the values displayed in the current property window are taken over for all the servers. If all the servers are selected, then the label of this button changes to Uncheck All. You can then click this button if you want to deselect all the servers. If you then click the Apply button, the error message No Servers Checked is output. The server values are not modified. Help button This provides you with information about how to use the currently displayed tab. ServerView Operations Manager 71

72 3.7 Tabs in the property windows 3.7 Tabs in the property windows You can set the values for the servers on the tabs. You can only edit one tab at a time. If you change the values on the current page and then move on to the next page without first clicking Apply, you will be asked whether you want to apply the values. If you click the Cancel button, then the property window is closed. If you have made changes but not confirmed these by clicking Apply, then the values are not taken over. Your changes are then lost. The table below provides an overview of which tabs are available in the various property windows: Property window ServerBrowser Server Properties on <server> Tabs Server Address, Network/SNMP, Remote Service Board, Local Note Server Address, Network/SNMP, CIM, Local Note, Login, Remote Service Board, BMC For BMC/iRMC: Server Address, Network/SNMP, Local Note For TCP/IP devices: Server Address, Network/SNMP, Local Note, TCP Application Table 12: Property windows and tabs BMC tab In this tab you can enter or change the IP address of a BMC. Under Configure BMC Network Address you can select the IP address to be used for the relevant BMC. Under Possible Addresses you will find a list of all possible addresses to choose from. If you always want to use this address, select Always use this address for the BMC. Under BMC Network Address you can specify the address explicitly. You can select the format of the IP address from the selection list (IPv4 or IPv6). You use the Test Connectivity button to test the connection to the server via the In-band Connectivity (primary address) and Out-of-band Connectivity (secondary address). ServerView Operations Manager 72

73 3.7 Tabs in the property windows In the case of server blades, you test the server blade connection via the In-band Connectivity in the Test Connectivity dialog and test the connection to the blade server via the Out-of-band Connectivity. In the case of blade servers, you can only test the In-band Connectivity in the Test Connectivity dialog. If you try to test the Out-of-band Connectivity, you will see the error message No Out-of-band Connectivity available! In the case of PRIMEQUEST chassis and PRIMEQUEST partition systems, you can test only the In-band Connectivity in the Test Connectivity dialog. If you try to test the Out-of-band Connectivity, you will see the error message No Out-of-band Connectivity available! Present in the Server Properties on <server> property window. CIM tab In this tab you can control and set the address used when creating a subscription for alarms on a server which supports a CIM Provider. The first address (Subscription address) is the CIM subscription address currently used by the Operations Manager for this VMware ESXi server. Normally it is the Operations Manager IP address. If the CMS has more than one LAN interface, the address is automatically detected by the Operations Manager as the best match to ESXi address by checking all address segments. This works currently for IPv4 addresses only. The second address (User Subscription Address) is a user-defined CIM subscription address. You can edit this field. The CIM subscription address is to be used by CMS for this VMware ESXi server. This tab is also available to other servers because in the future they will also support a CIM provider. Present in the property window Server Properties on <server>. Local Note tab In this tab you can enter local notes. Local notes are added to the server list and help to identify a server in this list more quickly. Present in the property windows ServerBrowser and Server Properties on <server>. Login tab In this tab you can define the Username and Password that are used when a set request is sent to the server. Here you also specify whether the password is to be queried on every change of setting or only on the first modification following program start. Present in the Server Properties on <server> property window. ServerView Operations Manager 73

74 3.7 Tabs in the property windows Network/SNMP tab In this tab you can set the parameters for the network operation of a server. The following parameters can be defined: Connection port, SNMP Settings, Poll Interval, Timeout and Connectivity Change Trap Present in the property windows ServerBrowser and Server Properties on <server>. Important A non-default UDP port can also be specified as the Connection Port. If Receive Trap after Change is enabled, the following trap is sent when the status of a monitored server changes. o o If the server can be monitored: Server changed state (The server <server name> has changed its state to snmpok or OK) If the server cannot be monitored: Server changed state (The server <server name> has changed its state to not manageable) The default setting is enabled with two polling intervals and no trap if the connectivity status of the managed servers is changed on startup of the ServerView management console. If the load on the network or server is too high, it can be improved by changing Poll Interval, Timeout, and Refresh Delay. Remote Service Board tab This tab displays the server name, the community and the IP address of the secondary channel if an RSB is installed. You can test the connection to the RSB by clicking the Test Connectivity button. With an RSB S2 there is no test-trap support. If the server cannot be reached via the primary channel, you can enter the server name and IP address of the secondary channel here. Once the server is reachable again, the primary channel is automatically used again. Clicking Configure starts a web browser in which you can configure the RSB. Present in the property windows ServerBrowser and Server Properties on <server>. Server Address tab (in the "ServerBrowser" window) In this tab, you can search for the IP address of a server or search for a server via its IP address. ServerView Operations Manager 74

75 3.7 Tabs in the property windows With the IP Address selection list, you specify whether you want to search for a server with an IPv4 address or an IPv6 address. You can either enter the IP address in the IP address field or as a string in the text field. The To String and To IP buttons allow you to convert your entry into the other format of the two. With an IPv6 address you cannot use the Search button to search for other entries. You use the Search button to start searching and the Test button to test the connection to the server via the In-band Connectivity (primary address) and Out-of-band Connectivity (secondary address). With blade servers, you can only test the In-Band Connectivity. If you try to test the Out-of-band Connectivity, you will get the error message No Out-of-band Connectivity available!. In the case of PRIMEQUEST chassis and PRIMEQUEST Partition systems, you can only test the In-band Connectivity in the Test Connectivity dialog. If you try to test the Out-of-band Connectivity, you will see the error message No Out-of-band Connectivity available! Server Address tab (in the "Server Properties on <server>" window) You can enter a server's IP address in this tab. Via the Network Address selection list, you specify whether you want to enter an IPv4 address or an IPv6 address. For a server blade you can configure a static IP address under Configure Blade Network Address. To do this, select the IP address you want for the server blade from the Possible Addresses list. It is necessary to define a static address if various IP addresses are provided by the MMB. You use the Test Connectivity button to test the connection to the server via the In-band Connectivity (primary address) and Out-of-band Connectivity (secondary address). In the case of server blades, you test the server blade connection via the In-band Connectivity in the Test Connectivity dialog and test the connection to the blade server via the Out-of-band Connectivity. In the case of blade servers, you can only test the In-band Connectivity in the Test Connectivity dialog. If you try to test the Out-of-band Connectivity, you will see the error message No Out-of-band Connectivity available! In the case of PRIMEQUEST chassis and PRIMEQUEST Partition systems, you can only test the In-band Connectivity in the Test Connectivity dialog. If you try to test the Out-of-band Connectivity, you will see the error message No Out-of-band Connectivity available! ServerView Operations Manager 75

76 3.8 Menus TCP Application tab In this tab, you can specify web applications (URLs) for TCP/IP devices as well as the ID number of the TCP/IP device. Present in the Server Properties on <server> property window. 3.8 Menus The following sections describe the menus that may be available to you with Operations Manager: Menus in the menu bar Context menus in the ServerList window Menus in the ServerView [server_name] window Menus in the SV Storage window Menus in the PRIMEQUEST ServerView [chassis_name] window Menus in the PRIMEQUEST Partition ServerView window Which functions are available to you depends on the user name under which you are logged in to ServerView Operations Manager. By default there are four user names with different roles: Administrator for the role Administrator (predefined password: admin) Operator for the role Operator (predefined password: admin) Monitor for the role Monitor (predefined password: admin) UserManager for the role UserAdministrator (predefined password: admin) Depending on the role - or rather the privileges assigned to it - you will be allowed to use all or only some of the functions of ServerView Operations Manager: The administrator can use all functions with the exception of user management, while the monitor can use the least. Functions which are not available to you because of your role are disabled (gray). All functions are described below as if you were the administrator. A detailed description of the meanings and functions of the menu items is available in the help texts. For further information on role-based user management, see the "User Management in ServerView" user guide. ServerView Operations Manager 76

77 3.8 Menus Menus in the menu bar ServerList In the ServerList window, the following menu items are available under Serverlist for administering the server list: Import Archive Import Server Export Server Settings Import archive data. Import server by means of csv or xml files. Export server list. Activate automatic updating of the server list and set the required interval; Configure Java applet to start Advanced Video Redirection (AVR). Table 13: Menu items in the ServerList menu Administration ServerBrowser Server Configuration Users/Passwords National Settings Base Configuration Wizard SNMPv3 Settings Opens the ServerBrowser property window in which you define new servers and enter them in the server list. Starts the ServerView Configuration Manager, via which you can define system-dependent configurations for a managed server. Create user/password list. Set national unit of measurement (temperature unit). Starts the Base Configuration Wizard, via which you can make basic settings for operation with ServerView Operations Manager. For further information on the Base Configuration Wizard, see the "Base Configuration Wizard" user guide. Opens the V3 Setting configuration window in which you can enable SNMPv3. Table 14: Menu items in the Administration menu ServerView Operations Manager 77

78 3.8 Menus Asset Management Archive Manager Inventory Manager Starts the Archive Manager, with which you can create archiving jobs for one or more servers and thus generate and compare archive data. For further information on the Archive Manager, see the "Server View Archive Manager" user guide. Starts the Inventory Manager which manages the customized collections of several types of data and their storage in the ServerView database. You can create reports based on this data and display them in graphical format on screen or export them regularly in several output formats. For further information on the Inventory Manager, see the "ServerView Inventory Manager" user guide. Table 15: Menu items in the Asset Management menu Deployment Installation Manager Starts the Installation Manager software if this software is installed on the management station. Installation Manager allows you to set up PRIMERGY servers and to install operating system software and management software. More information on Installation Manager is provided in the Installation Manager documentation. Table 16: Menu items in the Deployment menu The Deployment menu is only available if the Installation Manager is installed on the management station. ServerView Operations Manager 78

79 3.8 Menus Event Management Alarm Monitor Alarm Configuration Threshold Manager MIB Integrator Starts the Alarm Monitor which displays all received traps. In the Alarm Monitor you can control the display via filters and manage the available alarms. For further information see the "ServerView Event Manager" user guide. Starts the Alarm Configuration component, via which you can make settings for the handling of incoming alarm messages. For further information see the "ServerView Event Manager" user guide. Starts Threshold Manager, via which you can make settings for monitoring the managed servers based on threshold values. For further information see the "ServerView Threshold Manager" user guide. Starts the MIB Manager, which enables you to integrate foreign MIB files into the Event Manager. For further information on the MIB Manager, see the "ServerView Event Manager" user guide. Table 17: Menu items in the Event Management menu Monitoring Performance Manager Power Monitor Starts the Performance Manager with which you can conduct the long-term observation of various server parameters for a particular server. For further information on the Performance Manager, see the "ServerView Performance Manager" user guide. Starts the Power Monitor, with which you can manage and display values on the power consumption of a server or server blade. Table 18: Menu items in the Monitoring menu ServerView Operations Manager 79

80 3.8 Menus Update Management Update Manager Repository Manager Download Manager Configuration Starts ServerView Update Manager, with which firmware, BIOS and drivers, ServerView Agents and ServerView Update Agent can be updated via the network. This menu item is only available if ServerView Update Manager is installed on the management station. For further information on the Update Manager, see the "ServerView Update Management" user guide. Starts the ServerView Repository Manager, with which you can manage the update repository. This menu item is only available if ServerView Update Manager is installed on the management station. For further information on the ServerView Repository Manager, see the "ServerView Update Management" user guide. Starts the Download Manager which automatically downloads information and update files for low-level software components (e.g. BIOS, firmware) from the Fujitsu web server. For further information see the "ServerView Update Management" user guide. Starts a dialog for configuring general parameters for the update management. This menu item is only available if the ServerView Update Manager is installed on the management station. For further information see the "ServerView Update Management" user guide. Table 19: Menu items in the Update Management menu Network Management Virtual-IO Manager Starts the ServerView Virtual-IO Manager if the software is installed on the management station. The Virtual-IO Manager allows you to configure connection paths via special connection modules, e.g. via the Intelligent Blade Panel (IBP) and the virtualization of I/O parameters. For further information on the Virtual-IO Manager, see the "ServerView Virtual-IO Manager" user guide. Table 20: Menu items in the Network Management menu ServerView Operations Manager 80

81 3.8 Menus The Network Management menu is only available if Virtual-IO Manager is installed on the management station. The Virtual-IO Manager menu item is only available if Virtual-IO Manager is installed on the management station. Security User Management Starts the User Management wizard which helps you as a privileged user to easily perform ServerView user management with ServerView Operations Manager's internally used ApacheDS directory service. As a normal user you are only allowed to change your password. For further information on the User Management wizard, see the "User Management in ServerView" user guide and the online help of the User Management wizard. Table 21: Menu items in the Security menu The Security menu is only available if ApacheDS is used as directory service. Help The menu items under Help vary depending on the window. The following table shows all possible menu items. On Suite On <window_name> On Page Links About Calls the help system Context-sensitive help on the window Context-sensitive help on the selected function within the window Starts the ServerView link collection for more information on the ServerView Suite and PRIMERGY servers Outputs the installed version of ServerView Operations Manager Table 22: Menu items in the Help menu ServerView Operations Manager 81

82 3.8 Menus Context menus in the ServerList window The ServerList window provides you with context menus for editing the server list. The range of functions that are available depends on what is selected when you call the context menu as well as where you call it from. All the possible menu items are listed below: Open Management Configuration Import Server Export Server New Server New Group Copy to group Move to group Rename Delete Delete from group Server Properties Reinitialize Server Power Management Open the ServerView [server_name] window to request server data. Starts the web interface for the PRIMEQUEST management configuration in a new window. Import servers to a selected server group. Export servers into a file. Enter new servers in the server list. Create a new server group. Copy the servers that are selected in the server list to a server group or copy the selected server group to another group. Move the selected server or server group to another group. Rename the selected server group. Delete the selected server or server group. Delete the selected server from the server group. Open the Server Properties on <server> property window to define the server parameters. Open the Reinitialize Server dialog to reinitialize the server. Start remote power management. Available for servers with BMC, for server blades and servers on which VMware, Citrix XenServer / Xen, KVM, or Hyper-V is installed. Start Video Redirection Start Advanced Video Redirection (AVR) for the selected server. Available for servers with an irmc which support AVR and single sign-on. Test Connectivity Update Complete Server Call the Test Connectivity dialog (to test the server connection). Create new update jobs for servers. This menu item is only available if the update status is allowed (normal, warning or critical) and the update type is supported. Table 23: Menu items in the context menus of the ServerList window ServerView Operations Manager 82

83 3.8 Menus Explore Explore All Refresh From DB Clear Alarms Clear All Alarms Enable Muted Mode Disable Muted Mode Delete Archives Archive now Check the status of the selected server(s) or of a selected server group. Check the status of all the servers in the server group All Servers. The server status is refreshed on the basis of the database on the web server Delete the alarm icons for the selected server from the server list. This menu item is only available if an alarm has been received from at least one of the selected servers. Delete the alarm icons for all servers from the server list. This menu item is only available if an alarm has been received from at least one of the servers. Suppress alarm messages for the selected servers. Deactivates the suppression of alarm messages for the selected servers. Deletes archive data. This menu item is only available if archive data is present for the server. Archive selected servers or manageable servers of a selected server group immediately. Table 23: Menu items in the context menus of the ServerList window Menus in the Single System View window The following tables list all possible menus and menu items that can be offered in the Single System View window. Depending on the selected object, an appropriate subset of these menus and menu items is available. Blade List menu Blade List gives you a list of all blades belonging to the blade server (server blades, management blades, switch blades etc.). Under Details of the Selected Blade you will find detailed information on a blade selected on the table. This menu item is only available if a blade server has been selected. ServerView Operations Manager 83

84 3.8 Menus System Status or Blade Server Status menu Environment Mass Storage Power Supply System Board Performance Network Driver Monitor Information on temperature, cooling systems, fan configuration and their status in the server. Information on the controllers. You start the ServerView RAID Manager via the menu item RAID Configuration. Information on power supply configuration and status. Information on the processor, memory modules, voltages on the system board, bus systems and the result of the BIOS self-test. Detailed performance information on capacity and utilization of various components (processors, memory, network, storage) of a managed server. Information on the network configuration and the adapter statuses. Information on the components which are monitored as well as their corresponding events from the event log. Only applies to PRIMERGY servers and to servers of the PRIMEQUEST systems. Table 24: Menu items in the System Status or Blade Server Status menu System menu System Information Agent Information Operating System Processes File Systems Disk Partitions Resources Maintenance System information. Information on the SNMP agents. Information on the operating system. Information on the processes. Information on the file systems. Information on the partitions of the server. Provides tabs showing information on the utilization of operating resources by hardware components: IRQ, I/O-Port, DMA and Memory Only for PRIMEQUEST server Information about the menu items under Maintenance, including Battery Information, Server Properties, Boot Options, Remote Management and Prime Collect. Table 25: Menu items in the System menu ServerView Operations Manager 84

85 3.8 Menus Maintenance menu Battery Information System Event Log Server Properties ASR&R Boot Options Remote Management PrimeCollect Online Diagnostics Customer Self Service Blade Server View Management Blade Configuration Information on the installed battery. Information on errors and event log entries. Provides tabs for displaying the server settings: Server Address, Network/Snmp, CIM, Local Note, Login, Remote Service Board, BMC Provides tabs for ASR support: Cooling, Temperature, Restart, Power On Off, Watchdog Information on the defined boot options. The Remote Management menu offers the Remote Management view. Depending on the installed hardware of the managed server you can start the relevant Remote Management component via the corresponding button (e.g. RSB Manager, BMC Power Management, irmc Web). Further information on the Remote Management components is provided in the Remote Management documentation. If you are working with archive data, you only get Offline Agent Information in the Remote Management view. For collecting and storing information on the installed hardware and software of a managed server. This menu is only activated if the ServerView Agents for Windows as of V are installed on the managed server with the PrimeCollect component. Provides tabs for diagnostics testing: Predefined Tests, Custom Test, Status and Control This menu is only activated if the ServerView Agents for Windows V4.40 and higher are installed on the managed server. Information on CSS components. Starts the Blade ServerView for the blade server (only visible on server blades). Starts the web interface for the management blade configuration in a new window (only visible on server blades). Table 26: Menu items in the Maintenance menu ServerView Operations Manager 85

86 3.8 Menus Virtualization menu Host Properties Virtual Machines Information about the virtual host. Information about the virtual machines and how to activate/deactivate them. Table 27: Menu items in the Virtualization menu This menu is only enabled if you have selected a virtual server in the server list Menus in the ServerView <PRIMEQUEST_chassis_name> window PRIMEQUEST List menu PRIMEQUEST List gives you a list of all partitions belonging to the PRIMEQUEST chassis. Under Details of the Selected PRIMEQUEST you will find detailed information on a chassis selected in the table. This menu item is only available if a PRIMEQUEST chassis has been selected. Partition List menu Partition List Information about partitions and unused parts (Free Pool) of the selected PRIMEQUEST chassis Table 28: Menu items in the Partition List menu System Status menu Hardware Components Information on the configuration and status of the hardware components. Environment Power Supply Table 29: Menu items in the System Status menu Information on the temperature, voltage and cooling status of the server. Information on the power supply configuration and status. System menu System Information System information. Table 30: Menu items in the System menu ServerView Operations Manager 86

87 3.8 Menus Maintenance menu Server Properties Management Configuration Provides tabs for displaying the server settings: Server Address, Network/Snmp, Local Note, Login, Remote Service Board, BMC Starts the web interface for the PRIMEQUEST management configuration in a new window. Table 31: Menu items in the Maintenance menu Menus in the SV Storage window Configuration menu Status Overview System Information Information on the storage subsystem in general and its status. System information on the storage subsystem. Table 32: Menu items in the Configuration menu RAID Controller - <controller_name> menu The RAID Controller menu offers the following items for all existing RAID controllers: Overview Port List General information on the relevant RAID controller. Information on the ports of the selected RAID controller. Table 33: Menu items in the RAID Controller menu Enclosures menu The Enclosures menu offers the following items for the selected storage subsystem: Overview Physical Disk Environmental Information on the housing of the storage subsystem. Information on the physical hard disks. Information including the power supply and the cooling systems of the relevant storage subsystem. Table 34: Menu items in the Enclosures menu ServerView Operations Manager 87

88 3.8 Menus Storage Pools menu Overview Storage Volumes Host Mapping Information on the storage pools. Information on the storage volumes. Information on the assignment of the servers to the logical storage volumes. Table 35: Menu items in the Storage Pools menu Menus in the PRIMEQUEST Partition window System Status menu System Board IOBs Environment Mass Storage Power Supply BIOS Selftest Busses and Adapters Performance Network Driver Monitor Information on the processor, memory modules and voltages on the system board. List of I/O modules and their status, plus details of a selected I/O module and its status. Information on temperature, fans and their status in the PRIMEQUEST chassis. Information on the controllers. You start the ServerView RAID Manager via the menu item RAID Configuration. Information on the status and position of a power supply unit in the housing. Information on the result of the BIOS self-test. Information on the existing bus systems such as EISA or PCI with the connected controllers and their functions Detailed performance information on capacity and utilization of various components (processors, memory, network, storage) of a managed server. Information on the network configuration and the adapter statuses. Information on the components which are monitored as well as their corresponding events from the event log. Only applies to servers of the PRIMEQUEST systems. Table 36: Menu items in the System Status menu ServerView Operations Manager 88

89 3.8 Menus System menu System Information Agent Information Operating System Processes File Systems Partitions Resources System information. Information on the SNMP agents. Information on the operating system. Information on the processes. Information on the file systems. Information on the partitions of the server. Provides tabs showing information on the utilization of operating resources by hardware components: IRQ, I/O-Port, DMA and Memory Table 37: Menu items in the System menu Maintenance menu Battery Information System Event Log Server Properties Boot Options Remote Management PrimeCollect Online Diagnostics Information on the installed battery. Information on errors and event log entries. Provides tabs for displaying the server settings: Server Address, Network/Snmp, Local Note, Login, Remote Service Board, BMC Information on the defined boot options. The Remote Management menu offers the Remote Management view. Depending on the installed hardware of the managed server you can start the relevant Remote Management component via the corresponding button (e.g. RSB Manager, BMC Power Management, irmc Web). Further information on the Remote Management components is provided in the Remote Management documentation. If you are working with archive data, you only get Offline Agent Information in the Remote Management view. For collecting and storing information on the installed hardware and software of a managed server. This menu is only activated if the ServerView Agents for Windows as of V are installed on the managed server with the PrimeCollect component. Provides tabs for diagnostics testing: Predefined Tests, Custom Test, Status and Control This menu is only activated if the ServerView Agents for Windows V4.40 and higher are installed on the managed server. Table 38: Menu items in the Maintenance menu ServerView Operations Manager 89

90 3.9 Icons 3.9 Icons The icons show you the status of each object Icons in the ServerList window The following list shows the icons in the ServerList window and their meanings: OK: All components are okay. Warning: One or more components have status warning. Critical: One or more components have an error. Not manageable: The ServerView agent or CIM provider is not responding. Component is not available. Management Controller Mode: The server does not react, the management controller responds via the secondary channel. Unknown: The server cannot be reached over the network. Examine: Undefined status during the investigation process. A different TCP/IP device (e.g. a printer) has responded. Standard SNMP agent is okay. Only a standard SNMP agent responds and not a ServerView SNMP agent, e.g. for storage subsystems in the server list. Only for blades: The server is not available, but there is archive data available. Table 39: Icons in the ServerList windows ServerView Operations Manager 90

91 3.9 Icons All components of a blade server are okay. Warning: The blade server is faulty or the status of at least one manageable server blade has the status Warning Critical: The status of the blade server is critical or at least one manageable server blade has the status Critical. Examine: It is being checked whether the blade server is manageable. Not manageable: The management blade agent is not responding, but the management blade can be reached via TCP/IP. Unknown: The blade server cannot be reached over the network. Table 40: Blade server icons in the ServerList window All nodes in the cluster are manageable and have the status OK. Warning: At least one node has the status Critical, Not Manageable or Unknown. Examine: It is being checked whether the cluster is manageable. Critical: An error has occurred in at least one cluster. Not manageable: The cluster agent is not responding. Unknown: The cluster cannot be reached over the network Table 41: Cluster icons in the ServerList window ServerView Operations Manager 91

92 3.9 Icons OK: The connection to the ESX server is okay, the host has the status OK or Unknown. Warning: The connection to the ESX server is okay, but at least one of the manageable VMs or the host has the status Warning. Critical: The connection to the ESX server is okay, but at least one of the manageable VMs or the host has the status critical. Management Controller Mode: Only for servers which are not VMware vsphere Hypervisor servers (ESXi servers). The connection to the ESX server is okay, but the host is in Management Controller Mode. Not manageable: The connection to the ESX server or the host could not be established. The ESX server could be switched off or it could be unavailable because there is no valid user/password combination. Or it may be that the ServerView agent on the host is not responding. With VMware vsphere Hypervisor servers (ESXi servers), the BMC might not be configured or not responding. Unknown: The ESX server cannot be reached over the network. Table 42: VMware ESXi/ESX server icons in the ServerList window OK: The connection to the Citrix XenServer server / Xen server is OK or Unknown Warning: The connection to the Citrix XenServer server / Xen server is okay, but at least one of the manageable VMs or the host has the status Warning. Critical: The connection to the Citrix XenServer server / Xen server is okay, but at least one of the manageable VMs or the host has the status Critical. Management Controller Mode: The connection to the Citrix XenServer server / Xen server is okay, but the host is in Management Controller Mode. Not manageable: The connection to the Citrix XenServer server / Xen server or the host could not be established. The Citrix XenServer server / Xen server could be switched off or it could be unavailable because there is no valid user/password combination. Or it may be that the ServerView agent on the host is not responding. Unknown: The Citrix XenServer server / Xen server cannot be reached over the network. Table 43: Citrix XenServer server / Xen server icons in the ServerList window ServerView Operations Manager 92

93 3.9 Icons OK: The connection to the KVM server is okay, the host has the status OK or Unknown. Warning: The connection to the KVM server is okay, but at least one of the manageable VMs or the host has the status Warning. Critical: The connection to the KVM server is okay, but at least one of the manageable VMs or the host has the status critical. Management Controller Mode: The connection to the KVM server is okay, but the host is in Management Controller Mode. Not manageable: The connection to the KVM server or the host could not be established. The KVM server could be switched off or it could be unavailable because there is no valid user/password combination. Or it may be that the ServerView agent on the host is not responding. Unknown: The KVM server cannot be reached over the network. Table 44: KVM server icons in the ServerList window OK: The connection to the Hyper-V server is okay, the host has the status OK or Unknown. Warning: The connection to the Hyper-V server is okay, but at least one of the manageable VMs or the host has the status Warning. Critical: The connection to the Hyper-V server is okay, but at least one of the manageable VMs or the host has the status critical. Management Controller Mode: The connection to the Hyper-V server is okay, but the host is in Management Controller Mode. Not manageable: The connection to the Hyper-V server or the host could not be established. The Hyper-V server could be switched off or it could be unavailable because there is no valid user/password combination. Or it may be that the ServerView agent on the host is not responding. Unknown: The Hyper-V server cannot be reached over the network. Table 45: Hyper-V server icons in the ServerList window ServerView Operations Manager 93

94 3.9 Icons OK: The connection to the BMC/iRMC is okay. Warning: The connection to the BMC/iRMC is okay, the Global Error LED is on. Critical: The connection to the BMC/iRMC is okay, the Global Error LED is flashing. Not manageable: The connection to the BMC/iRMC has failed or login was not possible because there is no valid user name/password combination. Unknown: The BMC/iRMC cannot be accessed via the network. Table 46: BMC icons in the ServerList window OK: All components of the storage subsystem are okay. Warning: The status of one or more components has deteriorated. Critical: One or more components have an error. Not manageable: The SNMP agent is not responding. Standard SNMP agent is okay. Only a standard SNMP agent responds and not a ServerView SNMP agent. Unknown: The storage subsystem cannot be reached via SNMP. Table 47: Storage subsystem icons in the ServerList window OK: The connection to the switch blade is OK. OK: The connection to the switch blade (master) is OK. OK: The connection to the switch blade (slave) is OK. Not manageable: The SNMP agent is not responding. Unknown: The switch blade cannot be reached over the network. OK: The connection to the switch is OK. Unknown: The switch cannot be accessed. OK: Converged Fabric Node. Unknown: The Converged Fabric cannot be accessed. Table 48: Switch blade icons in the ServerList window ServerView Operations Manager 94

95 3.9 Icons All components of a PRIMEQUEST chassis are okay. Warning: The PRIMEQUEST chassis is faulty or the status of at least one manageable partition has deteriorated. Critical: The status of the PRIMEQUEST chassis is critical or at least one manageable server blade has the status Error. Not manageable: The PRIMEQUEST management blade is not responding, but the management blade can be reached via TCP/IP. Unknown: The status of the PRIMEQUEST chassis cannot be determined. Table 49: PRIMEQUEST chassis icons in the ServerList window OK: The event status of the PRIMEQUEST partition has the value green. Warning: The event status of the PRIMEQUEST partition has the value yellow. Critical: The event status of the PRIMEQUEST partition has the value red. Not manageable: The PAN Manager is not responding. Unknown: The PAN Manager is not accessible via the network. Table 50: PRIMEQUEST partition icons in the ServerList window Powered On: The server is on. Powered Off: The server is off. Suspended/Paused: The server is in standby mode or in pause mode. Table 51: Virtual machines without ServerView Agents icons in the ServerList window ServerView Operations Manager 95

96 3.9 Icons Icons in the status bar of the server list You can see from the icons in the status bar of the server list, how many objects in the server list have certain statuses. You can filter the server list display via the checkboxes next to the icons. OK: All components are okay. Warning: The status of one or more components has deteriorated. Critical: One or more components have an error. Standard SNMP agent is okay. The server does not react, the management controller responds via the secondary channel. Not manageable. The ServerView agent or CIM provider is not responding, but the server can be reached via TCP/IP. Unknown! The server cannot be reached over the network. A different TCP/IP device (e.g. a printer) has responded. Virtual machine without ServerView Agents: Powered On: The server is on. Virtual machine without ServerView Agents: Powered Off: The server is off. Virtual machine without ServerView Agents: Suspended/Paused: The server is in standby mode or in pause mode. Table 52: Icons in the status bar of the server list Icons in the server list The server list contains columns with icons which can describe the status of an object in more detail, e.g. in terms of its alarm level, archive data and update status. You can click the column header icon to sort the server list accordingly. ServerView Operations Manager 96

97 3.9 Icons Alarm column in the server list Column header icon. An alarm has been received. Alarm level: critical An alarm has been received. Alarm level: major An alarm has been received. Alarm level: minor An alarm has been received. Alarm level: informational An alarm has been received. Alarm level: unknown Incoming alarms for this server are ignored in accordance with the filter rules for alarm configuration. For the selected server muted mode is set by a time model. The server is outside the time model and no alarm has been received. If an alarm occurs, the assigned severity levels critical, major, minor and informational are displayed. If a time model is defined, the setting of muted mode can only be changed via the Alarm Configuration component in the Event Manager. In the case of a change, an appropriate message is issued. Table 53: Alarm icons in the server list Archive column in the server list Column header icon. Archive data is available. Archive data is being created. Table 54: Archive icons in the server list ServerView Operations Manager 97

98 3.9 Icons Update column in the server list Column header icon An update is not required. An update is recommended. An update is urgently required. Table 55: Update status icons in the server list Trust state column in the server list The trust state column shows the trust state to managed servers. Column header icon. No icon RBAC 1 -capable service and trust data are available (including certificate). The managed server trusts this management station. RBAC 1 -capable service is available but trust data is missing (including certificate). The managed server does not trust this management station The ServerView service on the managed server is not RBAC 1 -capable (older). This managed server requires user/password settings. Might be that corresponding ServerView service is not available on managed server. Table 56: Trust icons in the server list 1 RBAC: Role-Based Access Control ServerView Operations Manager 98

99 3.9 Icons Virtual-IO Manager column in the server list The Virtual-IO Manager column shows which managed servers are supervised by the Virtual-IO Manager (VIOM for short) Column header icon. Managed server is VIOM-manageable and VIOM management is active. Managed server is VIOM-manageable but VIOM management is inactive. No icon Server could not be managed by VIOM or state could not be provided. The VIOM column is only visible if VIOM is installed on the management station. Table 57: VIOM icons in the server list Icons in the ServerView [server_name] window The following list shows the icons in the ServerView [server_name] window and their meanings: Fan (green: okay; red: failure; yellow: critical; gray: not measurable) Pump (green: okay; red: failure; yellow: critical or warning; gray: not measurable) Indicator for the identification LED - localization function is activated. Indicator for the identification LED - localization function is deactivated. Table 58: Icons in the ServerView [server_name] window ServerView Operations Manager 99

100 3.9 Icons Icons in the Device View window The following list shows the icons in the Device View window and their meanings: RAID controller Host Disk Processor OTHER Other Table 59: Icons in the Device View window Icons in the Busses and Adapters window The following list shows the icons in the Busses and Adapters window and their meanings: Open branch on the selection level Closed branch on the selection level Lowest of the selection levels; no further selection possible Table 60: Icons in the Busses and Adapters window ServerView Operations Manager 100

101 3.9 Icons Icons in the Alarm Monitor window The following list shows the icons in the Alarm Monitor windows and their meanings: Red alarm: critical Orange alarm: major Yellow alarm: minor Blue alarm: informational Gray alarm: unknown Alarm is ignored. For the selected server muted mode is set by a time model. The server is outside the time model and no alarm has been received. If an alarm ocurrs, the assigned severity levels critical, major, minor and informational are displayed. The alarm was confirmed by a user entry. Some other executable program was triggered by this alarm. A broadcast message was sent for this alarm. A mail was sent for this alarm. This alarm triggered a pager call. This alarm will be passed on to a management station. This alarm will be passed on to the local system event log. Green: Pager confirmed Yellow: Pager completed Red: Pager present (still active) White: Error during paging (status unknown) Yellow: Forwarding completed Red: Forwarding present (still active) White: Error during forwarding (status unknown) Table 61: Icons in the Alarm Monitor window ServerView Operations Manager 101

102 3.9 Icons Other icons The following list shows the icons that can appear in different windows: Table columns can be filtered according to different criteria CD (red: critical; green: online; yellow: standby; blue: unknown) Communication devices (red: critical; green: online; yellow: standby; blue: unknown) CPU (red: critical; green: online; yellow: standby; blue: unknown) Jukebox, automatic CD changer (red: critical; green: online; yellow: standby; blue: unknown) MOD (red: critical; green: online; yellow: standby; blue: unknown) Printer (red: critical; green: online; yellow: standby; blue: unknown) Scanner (red: critical; green: online; yellow: standby; blue: unknown) Tape drive devices (red: critical; green: online; yellow: standby; blue: unknown) WORM Write Once Read Many (red: critical; green: online; yellow: standby; blue: unknown) Hard disk Table 62: Other icons Hard disk (red: DEAD; green: OK) Unknown device (red: critical; green: online; yellow: standby; blue: unknown) Network card All windows with network associations: Network interfaces [<Server>], Token Ring statistics [<Server>], Ethernet MAC statistics [<Server>], FDDI MAC statistics [<Server>] ServerView Operations Manager 102

103 3.9 Icons Hard disk All windows with associations to Mass Storage: Mass Storage [<Server>], Device View [<Server>], Mass Storage: Partition View [<Server>], Mass Storage: Logical View [<Server>], Mylex Disk Array windows: Device View [<Server>], Adapter View [<Server>], Physical Device View [<Server>] System board [<server name>] Table 62: Other icons ServerView Operations Manager 103

104 4.1 ServerView database 4 Administering the server list This chapter describes how to administer the server list. It explains the following: How the internal data storage works in Operations Manager (ServerView database), How the various objects are displayed in the server list, How to enter new objects in the server list, How to create user-specific server groups, How to delete objects from the server list, How to check the server list, How to create archive data via the server list. 4.1 ServerView database A SQL database is used for internal data storage. This database is required for the Operations Manager software to run. If necessary you can do the following for the SQL database: Create your own SQL queries Generate backups of the database ServerView database under Windows Under Windows you can use an SQL Server 2008 (R2), SQL Server 2008 (R2) Express, SQL Server 2012, SQL Server 2012 Express, SQL Server 2014 or SQL Server 2014 Express instance where the ServerView database is installed into. It is recommended that you always use the current service pack. The Express version of SQL Server 2014 is supplied with the Operations Manager software. In addition, you can use a remotely installed SQL Server instance to install the ServerView database into it. ServerView database under Linux Under Linux, PostgreSQL is used as the database management system. The installation software contains the PostgreSQL database management system. This PostgreSQL is automatically installed when you install the Operations Manager software. This does not affect the operation of an already installed PostgreSQL database management system. ServerView Operations Manager 104

105 4.2 Server list In addition, you can use a remotely installed PostgreSQL to install the ServerView database. Documentation on the ServerView database Detailed information on installing and managing the database is available in the Operations Manager Installation Guides for Windows and Linux. The ServerView database size limit depends on the used SQL Server edition. With a database size of 4 GB up to 200 servers can be managed (e.g. with Microsoft SQL Server 2008 R2 Express SP2 database shipped together with ServerView Operations Manager). 4.2 Server list The ServerList window is the main window in ServerView Operations Manager. It provides an overview of all the configured servers and is the starting point for all management actions. Figure 21: Server list If you want, you can display only certain of the servers present in the server list, e.g. only those that are not manageable. To do this, click the required states (status icons) in the bar above the server list. ServerView Operations Manager 105

106 4.2 Server list If a server has the status "not manageable", you can view or reconfigure certain settings. To do this, select Open on the context menu. This opens the Confirm View dialog box. Figure 22: Confirm View window - for a non-manageable server You can check or configure the following settings: Configure Server Properties Opens the Server Properties window, via which you can view or change the parameters (e.g. IP address, community, BMC address) of your server. Configure a BMC Address and start irmc Opens a window in which you can enter the BMC address and start the irmc web interface. This option is useful if your server has a BMC but the BMC was not entered in the ServerView server list. View Archive Data Shows the archived system data of your server. This option is only offered if archived data exists. If the SNMP agent has the status OK or if the BMC/iRMC address is known, the following dialog box opens. ServerView Operations Manager 106

107 4.2 Server list Figure 23: Confirm View window - for a non-manageable server The following options are possible: Start Single System View Displays a limited amount of information about your server. Configure Server Properties Opens the Server Properties window, via which you can view or change the parameters (e.g. IP address, community, BMC address) of your server. irmc Web Starts the irmc web interface. Video Redirection Starts Advanced Video Redirection (AVR) in a new browser window. AVR redirects the graphical output of the managed server to the screen of the management station and assigns the keyboard and mouse input on the management station to the managed server. For a manageable server you can start AVR via the menu Maintenance Remote Management in the ServerView [server_name] window (see "Remote Management (irmc)" on page 203). ServerView Operations Manager 107

108 4.2 Server list Blade Servers in the server list Blade servers are displayed in the server list as a special group in the All Servers view. A Cluster-in-a-Box (CiB) system based on a blade server (e.g. BX400) is displayed as a normal blade server, not as a multi-node server. When you click the group, the associated server blades are displayed. All other blades (e.g. switch blades or management blades) are only be displayed in the ServerView [blade server name] window, see "Querying blade server data" on page 212. Figure 24: Server list with blade servers The server list displays the server blades that are supported by S31 MIB or for which archive data is present. The server list also displays the blade ID and state of a server blade if the ServerView agent is installed on it. Server blades on which the ServerView agent is not running are identified as being "not manageable". The IP address of a server blade which is displayed in server list and used by Operations Manager is selected as follows: The IP address that was selected in the ServerProperties. The IP address that best matches the network IP address of the MMB. ServerView Operations Manager 108

109 4.2 Server list Server with Agentless Service in the server list Servers with ServerView Agentless Service installed are displayed in the server list under All Servers as follows: Figure 25: Server with Agentless Service in the server list The server browser recognizes the server with Agentless Service only via the available IPMI or SNMP protocols and stores this information for the central management station in the ServerView database. In the server list a server with Agentless Service is identified by an entry in the Available Protocols column. In addition, if you move the mouse pointer over the file tree, a tooltip appears showing the server name (suffix "agentless") to differentiate from servers with ServerView Agents installed supporting extended SNMP. Except for showing additional available protocols, the browsing (recognizing) and polling corresponds to the standard procedure for managed servers with ServerView Agents installed. The remaining ServerView functionality of servers with ServerView Agentless Service installed is the same as that of servers with ServerView Agents installed, where possible, or disabled if the available protocols or their subsets do not provide the required functionality. For servers with ServerView Agentless Service installed, the following functions are disabled: Server Configuration Manager (a message is displayed when the server is selected in the tree view) Threshold Management (grayed out) Performance Management (grayed out) Power Monitor (not shown in the file tree view in the Power Monitor) ServerView Operations Manager 109

110 4.2 Server list Multi-node servers in the server list Multi-node servers (CX400 servers) are displayed in the server list under All Servers as a special group of scalable servers. The tooltip indicates that it is a server of the type PRIMERGY CX400. A Cluster-in-a-box (CiB) system based on a multi-node server (e.g. CX400) is displayed as a normal cluster. No representation of the housing is displayed. If you click this group, the associated CX nodes will be displayed. Figure 26: Server list with multi-node servers Operations Manager can recognize a multi-node server only indirectly through its nodes. The node then delivers the appropriate chassis data. This data includes the chassis type and the serial number, which are used to automatically create the name of the multi-node server. You can change this name if you wish. With multi-node servers, the server list context menu does not offer the following menu items: Open Management Configuration (not applicable) Test Connectivity (not applicable) The following items on the context menu here only apply to the CX nodes: Server Properties Power Management Update Complete Server Explore Archive Now ServerView Operations Manager 110

111 4.2 Server list You can rename the selected server group by selecting Rename on the context menu. Unlike with blade servers, with multi-node servers you can delete individual CX nodes Cluster-in-a-Box (CiB) systems in the server list The server list shows Cluster-in-a-Box (CiB) systems as follows: A Cluster-in-a-Box (CiB) system based on a blade server (e.g. BX400) is displayed as a normal blade server, not as a multi-node server. For details, see "Blade Servers in the server list" on page 108. A Cluster-in-a-Box (CiB) system based on a multi-node server (e.g. CX400) is displayed as a normal cluster. No representation of the housing is displayed. For details, see "Multi-node servers in the server list" on page Virtual Servers in the server list The server list shows virtual servers as a special group. The node of this group shows the status of the Virtual Machine Monitor (VMM) or the Hypervisor. The group contains the physical server (host) and all associated virtual servers with their operating systems (guest systems). The host is always displayed first and indicates the status of the physical server. The virtual servers currently supported are: Hyper-V servers Citrix XenServer servers / Xen servers KVM servers VMware servers To allow a virtual system to be accessed, valid user/password combinations for this virtual server must be entered in the user/password list of ServerView Operations Manager. If these are present, ServerView automatically recognizes the guest system as soon as you add this virtual server to the server list. Most virtual systems do not provide IP addresses of the guest systems. Only Citrix XenServer systems and VMware systems can offer this information. But this requires for Citrix XenServer systems the Citrix XenServer tools and for VMware systems the VMware tools to be installed on the guest systems. However, as the IP addresses are not normally provided, the virtual guest systems cannot be managed until they are added to the server list. This is best done via the server browser (see "Adding objects via the "ServerBrowser" window" on page 134). Virtual servers can be identified here by their server type (model) PRIMERGY HYPER-V, PRIMERGY XEN VM, PRIMERGY VIRTUAL MACHINE or PRIMERGY XEN VK. The virtual servers are then added to the virtual system group by comparing their ServerView Operations Manager 111

112 4.2 Server list Universally Unique Identifiers (UUID). The UUIDs and for Hyper-V servers the BIOS ID are provided both by the virtual systems and by the ServerView Agents VMware in the server list As of VMware ESXi V 3.5, VMware servers are displayed in the server list as a special group under All Servers. VMware ESXi hosts can also be added as normal servers to the server list without virtual host features (see "Adding hosts with virtualization software as normal servers to the server list" on page 143). If you click this group, the VMware server and the associated virtual servers (virtual machines - VM) will be displayed in the right-hand section. Figure 27: VMware ESX Server in the server list ServerView Operations Manager 112

113 4.2 Server list Requirements The VMware tools must be installed on the virtual servers so that the IP address and the Universally Unique Identifier (UUID) can be called up. For further information, see the relevant VMware documentation. For a VMware ESX server to be displayable in the server list, there must be a valid user/password combination in the user/password list of ServerView Operations Manager. For display in the server list, the user ID only requires read access, but for power management the user must have administrator rights. The VMware ESX servers are only displayed as a special group in VMware ESX Server V3.5.0 and higher. VMware ESXi as of version 3.5 The VMware ESXi host server is identified with its network address, model and operating system information. The associated virtual servers are shown in the server list under the ESXi host server in the Name column with their current VMware names. The VMware ESXi host cannot be accessed via SNMP, but by a CIM provider. The server list shows the CIM provider status for the host node of an ESXi server. Clicking on a VMware ESXi node opens the single system for the CIM provider. If the CIM provider cannot be accessed, the "Management Controller Mode" status or the "Not Manageable" status is displayed. The "Management Controller Mode" status is available when a valid IP address and a valid user/password are configured for the irmc (for information on manual configuration, see the irmc documentation). In that case, you can open the web interface of the irmc. Since Update 4 for ESXi 3.5 and for newer versions including ESXi 4.1, VMware has disabled write access for the "free" version of ESXi. Start/stop virtual machines and Enter maintenance mode are considered by VMware to be write operations and are not available in free version. To use these operations with ESXi server, you will need to get a license (not a free license) or revert back to older updates. If server software (ESXi, for example) requires a license, it should allow full functionality instead of just read-only access as with the free version of ESXi as of version 3.5 Update 4. As of version 4, the free version of VMware is called VMware vsphere Hypervisor (ESXi). For more information, follow these links: ServerView Operations Manager 113

114 4.2 Server list How to reduce too many login/logout actions on VMware hosts If there are too many login/logout actions on a VMware host, there are various ways you can reduce the entries. 1. Increase the poll cycles. You can increase the poll cycles to reduce the login/logout actions on VMware hosts. a. Select one or more VMware hosts from the server list and then choose Server Properties from the context menu. The Server Properties property window opens for the selected VMware hosts. b. Click the Network/SNMP tab. c. Select Special under Poll interval (sec) and enter the required number of seconds (more than the default of 60 sec) for the poll interval. d. Click Apply or OK to confirm your settings. 2. Disable the discovery of virtual machines. You can disable the discovery of virtual machines via the Base Configuration Wizard. a. Disable VM Discovery in the VM Discovery step of the Base Configuration Wizard. In this case all virtual machine nodes will be removed from the server list. For further information see the Base Configuration Wizard documentation. 3. Disable the automatic discovery of hosts with virtualization software. You can disable the automatic discovery of hosts with virtualization software via the Base Configuration Wizard. a. Disable VM Host Discovery in the VM Discovery step of the Base Configuration Wizard. In this case the discovery is disabled for all hosts with virtualization software in a subnet. All virtual platforms on blades, PRIMEQUEST partitions, and cluster nodes will be converted to normal server nodes. For further information see the Base Configuration Wizard documentation Citrix XenServer server / Xen server in the server list As of Xen V3.1 and as of Citrix XenServer V5.5, Citrix XenServer servers / Xen servers on Linux systems are displayed in the server list under All Servers as a special group. Citrix Xen Server / Xen hosts can also be added as normal servers to the server list without virtual host features (see "Adding hosts with virtualization software as normal servers to the server list" on page 143). ServerView Operations Manager 114

115 4.2 Server list If you click this group, the Linux server and the associated virtual servers (PRIMERGY XEN VM) will be displayed in the right-hand section. Figure 28: Citrix XenServer servers / Xen servers in the server list The Linux server entry shows the status of the ServerView agent as well as the hardware and the operating system. In the above example the Xen server BX600PW-01 is a PRIMERGY BX620 S4 with the Xen hypervisor XenServer p. It has the status okay. The virtual servers are shown in the server list in the Name column with their current Xen name. If the ServerView Agents are installed, the server list will also show the status of the virtual servers and the Linux server. By clicking an entry in the server list you can retrieve further server data in the ServerView [server_name] window. Virtual servers on which the ServerView agent is not running are marked as "Powered On", "Powered Off", or "Suspended". Requirements For a Xen server or for a Citrix XenServer server to be displayed in the server list, the user/password list of ServerView Operations Manager must contain a valid user/password combination if it is protected by a password. For display in the server list, the user ID only requires read authorization, but for power management the user must have administrator rights. Xen is only supported as of Xen Server version 3.1. The warranty and functionality are still limited. You have to enable a valid port number for the Xen Server. The current version of ServerView Operations Manager only supports port The Citrix XenServer is accessed on port 80. ServerView Operations Manager 115

116 4.2 Server list The Citrix XenServer server only provides the IP addresses of the virtual servers if the Citrix XenServer tools are installed on the guest systems. If this is not the case, the Citrix XenServer server does not provide the IP addresses of the virtual servers. If the virtual servers cannot be automatically assigned to other servers in the server list, the virtual servers are displayed without an IP address. In this case the ServerView agent cannot be reached. If, however, a server from the server list can be assigned to a virtual server, it is automatically reassigned to the Citrix XenServer server s / Xen server s group. Figure 29: Virtual servers without IP addresses ServerView Operations Manager 116

117 4.2 Server list KVM servers in the server list Servers with Red Hat Enterprise Linux 6 or Red Hat Enterprise Linux 7 and a KVM host are shown in the server list as follows: Figure 30: KVM host in the server list If monitoring a virtual machine in RHEL6/KVM or REHL7/KVM does not work, please check whether the required packages are installed on Linux. Check the installation log of ServerView Operations Manager to see if there is a corresponding warning. To allow the KVM host to be accessed from a Windows-based management station, the authentication must be deactivated while the KVM host is being configured. How to do this depends on the type of connection you are using. TCP If you only access the KVM host from Linux-based management stations, the authentication can be activated. KVM hosts can also be added as normal servers to the server list without virtual host features (see "Adding hosts with virtualization software as normal servers to the server list" on page 143). With a TCP connection, authentication is not possible. 1. Modify the /etc/libvirt/libvirtd.conf file as follows: listen_tis = 0; listen_tcp = 1; auth_tcp = "none";//it is mandatory for access from a Windows station 2. In the /etc/sysconfig/libvirtd file, comment out the following lines: ServerView Operations Manager 117

118 4.2 Server list LIBVIRTD_ARGS="--listen" 3. Restart the libvirtd service: service libvirtd restart As the libvirtd client cannot authenticate under Windows, in this case the default user/password combination is used internally. TLS With a TLS connection, neither authentication nor certificate checking are possible but an encrypted connection is possible. 1. Modify the /etc/libvirt/libvirtd.conf file as follows: listen_tis = 1; listen_tcp = 0; tls_no_verify_certificate = 1; tls_no_verify_address = 1; 2. In the /etc/sysconfig/libvirtd file, comment out the following line: LIBVIRTD_ARGS="--listen" 3. Generate a certificate ( so that the libvirt daemon starts correctly. 4. Restart the libvirtd service: service libvirtd restart Hyper-V Servers in the server list On Microsoft Windows Server 2008 (x64), on Microsoft Windows Server 2008 R2 (x64), and on Microsoft Windows Server 2012, the Microsoft product Hyper-V can be installed, configured and activated. Microsoft Windows Server 2008/2012 Hyper-V and Hyper-V Server 2008/2012 are displayed in the server list as a special group under All Servers. To recognize Hyper-V server the dynamic ports for RPC (Remote Procedure Call) should be opened for the process: %SystemRoot%\System32\dllhost.exe Hyper-V hosts can also be added as normal servers to the server list without virtual host features (see "Adding hosts with virtualization software as normal servers to the server list" on page 143). If you click this group, the Hyper-V host and the associated virtual servers will be displayed in the right-hand section. ServerView Operations Manager 118

119 4.2 Server list Figure 31: Hyper-V servers in the server list The Hyper-V server entry shows you the status of the ServerView agent, the hardware status and the operating system. In the above example the Hyper-V server RX200-S6-VT2- Win2008-R2 is a PRIMERGY RX200 S6 with the operating system Windows Server 2008 Enterprise Edition (x64). It has the status okay. The virtual servers are displayed in the server list in the Name column with their current Hyper-V names. If the ServerView Agents are installed on one or all (virtual) servers involved, the server list will also show the status of the virtual servers and the Hyper-V host. By clicking an entry in the server list, you can request further server data in the ServerView[server_ name] window. Virtual servers on which the ServerView agent is not running are marked as "Powered On", "Powered Off", or "Suspended". Requirements For the connection to the server via In-band Connectivity (primary address) and Out-ofband Connectivity (secondary address) to be tested with the Test Connectivity button, the following requirements must be met. 1. The Windows Remote Manager must be configured appropriately. To do this, on Windows systems activate the authentication method Basic and deactivate the value Negotiate/Kerberos (Microsoft). Negotiate and Kerberos are Windows-specific authentication methods which are not supported under Linux. For this reason, ServerView Operations Manager does not support these two authentication methods either under Windows or under Linux. You can configure the Windows Remote Manager via the Microsoft command lines with the winrm command. ServerView Operations Manager 119

120 4.2 Server list At the command line you enter the following commands: o o o o Test the winrm command: winrm get winrm/config Get help on the configuration file config: winrm help config Start the Windows Remote Manager web service: winrm quickconfig winrm create winrm/config/listener?address=ip:...+transport=http Activate the authentication method Basic and deactivate the values Negotiate/Kerberos for the Windows Remote Manager web service: winrm set {AllowUnencrypted="true"} winrm set {Basic="true";Kerberos="false";Negotiate="false"} 2. For the virtual servers to be listed and for the power management, the user/password list of ServerView Operations Manager must contain a valid user/password combination with full administrator rights. For connections with WMI, Windows Management Instrumentation (WMI) must be activated in the Windows firewall. Special instructions for Microsoft Windows Server 2008 R2 (x64) and Windows Server 2012 For Hyper-V servers to be recognized by a Windows Server 2008 R2 (x64) or a Windows Server 2012, an entry in the Windows Registry regarding access restrictions has to be changed. Please note that to do this you must be a member of the Administrators group. Proceed as follows: 1. Log on as Administrator. 2. Start the Registry Editor regedit. A window with various keys opens. 3. Navigate to the key: HKEY_CLASSES_ROOT\ CLSID\{76A64158-CB41-11D1-8B D9B6}. 4. Select the key by right-clicking it. 5. In the context menu, select Permissions. ServerView Operations Manager 120

121 4.2 Server list Figure 32: Registry Editor regedit The Security window opens. 6. Click the Advanced button. The Advanced Security Settings window opens. 7. Select the Owner tab. The current owner displayed is TrustedInstaller. Figure 33: Advanced Security Settings - Current Owner TrustedInstaller ServerView Operations Manager 121

122 4.2 Server list 8. In the Change Owner to list, select Administrators. 9. Save the new setting by clicking Apply. The Current Owner is now set to Administrators. Figure 34: Advanced Security Settings - Current Owner Administrators 10. Confirm the new setting by clicking OK. 11. Close all dialog boxes by clicking OK. 12. Select the above key again and choose Permissions again from the context menu. Only now does the change to the access restrictions take effect. 13. Select Administrators in the Group or user names list. 14. Give the Administrators group full access by selecting the Full Control checkbox. ServerView Operations Manager 122

123 4.2 Server list Figure 35: Permissions window 15. Then click OK to confirm your selection and close the window. The configuration is complete. 16. Close regedit. So that Hyper-V can provide the IP addresses of the virtual servers, certain settings must be made, see "Defining (includes discovering) objects via the browser" on page 137. If these settings are not made, Hyper-V servers will not provide the IP addresses of the associated virtual servers. If the virtual servers cannot be automatically assigned to other servers in the server list, the virtual servers are displayed without an IP address. In this case the ServerView agent cannot be reached. If, however, a server from the server list can be assigned to a virtual server, it is automatically reassigned to the Hyper-V server s group. The assignment is performed by matching the UUID provided by the Hyper-V Server (biosid) and the ServerView agent. ServerView Operations Manager 123

124 4.2 Server list VMware ESXi hosts as normal servers in the server list VMware ESXi hosts can be added to the server list as normal servers without virtual host features (see "Adding hosts with virtualization software as normal servers to the server list" on page 143). In this case they are displayed as normal PRIMERGY servers in the server list (see "Server list" on page 105). By clicking the VMware ESXi host in the server list window you open the CIM based Single System View for this server PRIMEPOWER Systems in the server list PRIMEPOWER systems are displayed in the server list like PRIMERGY servers. If you click a PRIMEPOWER system in the server list, the web interface of the PRIMEPOWER ServerView Suite starts up. Figure 36: Server list with PRIMEPOWER system For more information on the PRIMEPOWER ServerView Suite, see the documentation PRIMEPOWER ServerView Suite - System Administration within a Domain. ServerView Operations Manager 124

125 4.2 Server list Storage subsystems in the server list The storage subsystems are indicated in the server list by the storage subsystems icon. Figure 37: Storage subsystems in the server list We distinguish between the following storage subsystems: For the following ETERNUS DX/AF storage subsystems you receive further information in the SV - Storage window of ServerView Operations Manager. Models ETERNUS DX60-S2/DX80-S2/DX90-S2 ETERNUS DX410-S2/DX440-S2/DX8700-S2 ETERNUS DX60-S3, DX100-S3, DX200-S3 ETERNUS DX60-S4, DX100-S4, DX200-S4, AF250 ETERNUS DX500-S3, DX600-S3, DX8700-S3, AF650 ETERNUS DX500-S4, DX600-S4, AF250-S2, AF650-S2 Table 63: Models of storage subsystems For the following storage subsystems you receive further information via the web interface of the storage subsystem: o o NetApp ETERNUS CS800 ETERNUS DX/AF With these ETERNUS storage subsystems, the ServerView Storage Manager (StorMan) software delivers the necessary information to ServerView Operations Manager so that it ServerView Operations Manager 125

126 4.2 Server list can be displayed within ServerView Operations Manager. If you click a storage subsystem of this type in the server list, information on this storage subsystem is displayed in the SV - Storage window (see "Querying storage subsystem data" on page 247). The storage subsystems can only be managed in ServerView Operations Manager if the following requirements are met: ServerView Storage Manager (StorMan) must be installed on the same management station as ServerView Operations Manager. The ServerView Storage Manager (StorMan) service StorMan Service (Windows) or storman (Linux) must be started. An SMI-S provider must be enabled on the ETERNUS DX/AF storage system (SMI-S - Storage Management Initiative Specification). The storage subsystem must be appropriately configured. o With the ETERNUS DX/AF models, the configuration occurs automatically when the object is added to the server list (see also "Defining and adding objects" on page 134): The ETERNUS DX/AF SMI-S functions require a valid user/password combination. This combination must be stored in the user/password list before the storage subsystem is added to the ServerView server list (see "Creating a user/password list" on page 273). If there are problems with the configuration, you should execute the following ServerView Storage Manager (StorMan) configuration command: storcfg cimom -add -ip <IP address of the storage system> -cimuser <user> - cimpwd <password> If the user/password changes, you must execute the following StorMan configuration command: storcfg cimom -mod -ip <ip-address of the storage system> -newuser <user> - newpwd <password> o If the user/password changes, you must execute the following StorMan configuration command: storcfg cimom -mod -ip <IP address of the server with the installed SMI-S provider> -newuser <user> -newpwd <password> Additional documentation For more information on StorMan, please see the ServerView Storage Manager documentation or the supplied Readme file. ServerView Operations Manager 126

127 4.2 Server list NetApp/ETERNUS CS800 Clicking one of these storage subsystems in the server list opens its web interface Baseboard Management Controller (BMC) in the server list You can recognize a BMC (Baseboard Management Controller) in the server list by the special BMC icon. Only BMCs from Fujitsu can be displayed in the server list. Figure 38: BMCs in the server list The BMC entry indicates the status of the Global Error LED. The status of this LED is not taken into account in the group status (on the left in the file tree) or in the overview of the overall status above the server list. Requirements For a BMC to be displayable in the server list, there must be a valid user/password combination in the user/password list of ServerView Operations Manager. A BMC entry is automatically deleted from the list if: You add a new server to the server list and the service ServerView Services (Windows) or SV Services (Linux) identifies a BMC with the same UUID in the server list. You add a BMC to the server list and the service ServerView Services (Windows) or SV Services (Linux) identifies the associated server with the status manageable in the server list via the UUID. You add a BMC to the server list and the server list contains a server with the same UUID but the status not manageable. The reason for this could be an invalid IP address of the server. In this case, ServerView checks whether the ServerView Agents are running on the server. If they are, ServerView then checks whether a connection to the ServerView agent can be established via SNMP using any system IP address of the ServerView Operations Manager 127

128 4.2 Server list BMC. If this is possible, the IP address of the server is changed and the BMC is deleted from the server list. The IP address of a BMC was changed and you add the BMC to the server list with the new IP address PRIMEQUEST chassis in the server list The PRIMEQUEST system and the ServerView Suite management server must both be configured before the PRIMEQUEST is added to the domain on the management server Enabling SNMP In the MMB web interface, select the menu options Network Configuration Network Protocols and enable the SNMP agent and SNMP trap. Figure 39: Enabling SNMP The following settings must be made: SNMP Agent Specify Enable. Agent Port# Set the port number to 161. SNMP-Trap Specify Enable. ServerView Operations Manager 128

129 4.2 Server list Trap Port# Set the port number to Configuring SNMP SNMP protocol parameters In the MMB web interface, select the menu options Network Configuration SNMP Configuration Community and set the parameters to match the SNMP protocol version v1 which is used. Figure 40: SNMP protocol parameters Community/User Enter a community (for SNMP v1) or a user for (SNMP v3) for communicating with the management server (up to 32 characters, default: public). IP Address/MASK Specify the IP address and net mask of the management server that manages the PRIMEQUEST. SNMP Version Set the protocol version to 1. Access Select the access authorization Read Write. ServerView Operations Manager 129

130 4.2 Server list Auth Specify noauth for no authorization, auth for authorization. SNMP trap parameters In the MMB web interface, select the menu options Network Configuration SNMP Configuration Trap and set the parameters to match the SNMP protocol version v1 which is used. Figure 41: SNMP trap Community/User Specify public. IP Address Specify the IP address of the SVS management server. SNMP Version Select SNMP version 1. Auth Specify nothing here. Auth Type Specify nothing here. Auth passphrase/priv passphrase Specify nothing here. ServerView Operations Manager 130

131 4.2 Server list PSA agent Only applies to servers of the PRIMEQUEST 1000 series. The PSA agent, which is available on the support DVD, must be installed on each partition of the PRIMEQUEST server. ServerView Operations Manager needs a correctly installed and configured PSA agent to manage these servers. Additional, you have to adjust the ipsetup.conf configuration file of the PSA agent: Under Windows Server 2008/2012: 1. Open the ipsetup.conf file in the <PSA Installation directory>\etc\opt\fjsvpsa\usr\ directory. 2. Enter the IP address of the managed partition. To reflect this setting, restart the PSA agent according to following steps: 3. Select Administrative Tools - Services. 4. Select PRIMEQUEST Server Agent in the right side window. 5. On the menu bar, click Operation Restart to restart the PSA service. Under Linux: 1. Open the ipsetup.conf file in the /etc/opt/fjsvpsa directory on a partition. 2. Enter the IP address of the managed partition. To reflect this setting, restart the PSA agent. Enter the following commands: #/sbin/service y30fjsvpsa stop #/sbin/service y30fjsvpsa start ServerView Operations Manager 131

132 4.2 Server list PRIMEQUEST chassis PRIMEQUEST chassis are displayed in the server list as a special group in the All Servers view. When you click the group, the associated PRIMEQUEST partitions are displayed. Figure 42: Server list with PRIMEQUEST chassis The server list displays the PRIMEQUEST chassis that are supported by MMB-COM-MIB or for which archive data is present PRIMEQUEST chassis/primequest partition is not Manageable If the PRIMEQUEST chassis or PRIMEQUEST partitions are displayed with the "not manageable" icon in the server list, the ServerView agent does not response. In this case please check the server and manager configuration. For further information see "Server/server blade is not manageable" on page 133. If a PRIMEQUEST chassis is not manageable, then you can check the configuration via web interface (ServerView - Maintenance - Management Configuration). ServerView Operations Manager 132

133 4.3 Server/server blade is not manageable 4.3 Server/server blade is not manageable If the servers or server blades are displayed with the "not manageable" icon in the server list, the ServerView agent does not response. In this case please check the server and manager configuration. For example, in the case of PRIMERGY servers you could proceed as follows: 1. Check that the Server Management parameter in the server's BIOS (Server menu) is set to Enabled. 2. Check that the BIOS ASR&R functions (Server menu) are enabled in all devices. 3. Check that the agents are installed in all the servers and that the SNMP services are enabled in all the devices. If a blade server is not manageable, then you can check the configuration via the web interface (Server View - RemoteView Management Blade). 4.4 Server not manageable/ management controller icon ServerView Operations Manager receives information about the servers in two ways that are independent of one another: via a primary channel if the server is running, via a secondary channel if the server is not running. However, this channel provides only limited information. The primary channel is the LAN connection that is also used by the operating system, while the secondary channel is the LAN connection that is used by the management controller (RSB, BMC, irmc). ServerView Operations Manager recognizes which channel is supplying the information on the basis of the IP address. If a server is inaccessible ( not manageable ), ServerView Operations Manager checks whether the management controller can be accessed. If the management controller responds via the secondary channel, then the icon is displayed in the server list. For how to get more information on a server which is not responding and is identified by the management controller icon see "Server with BMC/iRMC, not manageable" on page 211. ServerView Operations Manager 133

134 4.5 Defining and adding objects 4.5 Defining and adding objects There are various ways of defining new objects and adding them to the server list: via the ServerBrowser window (see "Adding objects via the "ServerBrowser" window" on page 134) by importing them from an archive (see "Adding objects by importing archive data" on page 145) by importing csv or xml files (see "Adding objects by importing import files" on page 145) Adding objects via the "ServerBrowser" window You can use the ServerBrowser property window to define new objects (e.g. servers, blade servers, clusters, Xen servers) and add them to the server list. You open the ServerBrowser window by choosing Administration ServerBrowser. Figure 43: ServerBrowser - example The top part of the window shows tabs and information on a selected object. In the bottom part of the window, you can search for objects in selected networks using the browser provided. ServerView Operations Manager 134

135 4.5 Defining and adding objects You can define a new object by specifying the corresponding name and address in the Server Address tab or by selecting one or more objects via the browser Defining (includes discovering) objects via Server Address tab On the Server Address tab, enter the server name and the IP address of the desired server. You can also enter only the server name or the IP address and use the Search button to search for further details, if any, and have them entered. Via the IP Address selection list you can specify whether you want to search for a server with an IPv4 address or an IPv6 address. In the case of an IPv6 address, you cannot use the Search button to search for further details. You can enter the IP address either in the IP address fields or as a string in the text box below them. If you click the To String button, the IP address you entered in the IP address fields is converted into a string. If you click the To IP button, the IP address you entered as a string is automatically inserted in the corresponding IP address fields. Via the Server Address tab in the Server Properties window, you can change the IP address of a server (see "Tabs in the property windows" on page 72). With the Test button you can test the connection to the server. With Clear you can delete existing entries on the tab. If you select the option Automatic in the selection list in the top right, each of the selected objects will be assigned the server type that has been automatically determined by the browser. Bear in mind that, in the case of new entries in the server list (e.g. Xen server) on the Server Address tab, the server name and also the IP address of the desired server must always be specified. ServerView also identifies Hyper-V servers, Citrix XenServer servers / Xen servers, KVM servers, and VMware servers, provided that the service ServerView Services (Windows) or SV Services (Linux) can establish a connection to the virtual server based on a valid user/password combination. To do this, the service ServerView Services (Windows) or SV Services (Linux) searches the user/password list created under ServerView Operations Manager. ServerView will only identify a BMC if the service ServerView Services (Windows) or SV Services (Linux) can establish a connection to the BMC based on a valid user/password combination. To do this, the service ServerView Services (Windows) or SV Services (Linux) searches the user/password list created under ServerView Operations Manager (see "Creating a user/password list" on page 273). ServerView Operations Manager 135

136 4.5 Defining and adding objects Storage subsystems are recognized as follows: Storage subsystem ETERNUS DX60-S2/DX80-S2/ DX90-S2/DX410-S2/DX440-S2/DX8700-S2 ETERNUS DX60-S3/DX100-S3/DX200- S3/DX500-S3/DX600-S3/DX8700- S3/AF250/AF650 ETERNUS DX60-S4/DX100-S4/DX200- S4/DX500-S4/DX600-S4/AF250-S2/AF650- S2 ETERNUS TAPE LIBRARY ETERNUS CS800 NetApp All others Recognized server type ETERNUS DX-S2 ETERNUS DX-S3 ETERNUS DX-S4 ETERNUS LT ETERNUS CS NetApp Other Table 64: Server types of the storage subsystems You can also define the server type yourself (e.g. server, blade server, cluster, PRIMEPOWER, storage). Select Other for other TCP/IP devices such as printers. If you want to add hosts with virtualization software (e.g. VMware, Hyper-V, Xen) as normal server without virtual features, you must select type Server in the selection list or disable VM Host Discovery in the VM Discovery step of the Base Configuration Wizard. If you click the Apply button, the displayed values are applied. ServerView Operations Manager 136

137 4.5 Defining and adding objects Defining (includes discovering) objects via the browser The browser consists of two parts: The left section of the window shows the network entities that serve as starting points for a search operation. The right section of the window shows the objects of the selected network entity. The name of the server with a prefix consisting of two status icons, the network address, the type description and a comment are output. The network address, type description and comment are only output if ServerView Operations Manager is able to identify them. If a BMC has not been assigned a server name, the IP address is shown here. In the lower left-hand area of the window enter 1. which subnet or domain is to be searched for objects. Domains can only be searched under Windows. Under Linux you can only search subnets. When searching a domain, please bear the following in mind: o o Searching a domain can take some time. The time required for a search can differ depending on the attempt. The results list can differ depending on the Windows Application Programming Interface (WinAPI). 2. which SNMP Settings are to be used for browsing. Clicking Configure SNMP opens the SNMP Settings window, where you can set the parameters for the SNMP connection, see "Server Properties" on page 196. By default your own subnet and the SNMP Setting (SNMP v3) AuthPriv are entered. You can also define SNMP parameters for searching for individual hosts in the Network/SNMP tab. ServerView Operations Manager 137

138 4.5 Defining and adding objects Figure 44: ServerBrowser - Network/SNMP tab ServerView Operations Manager 138

139 4.5 Defining and adding objects Starting the search You start the search by clicking the Start Browsing button. You can also use this button to cancel the search procedure (Stop Browsing) while it is in progress. At the end of the search the objects found are displayed in order of ascending IP address. The icons in front of the names show the object type. An icon in the first column identifies the objects already present in the server list. ServerView also identifies VMware ESX servers V3.x, provided that the service ServerView Services (Windows) or SV Services (Linux) can establish a connection to the VMware server based on a valid user/password combination. To do this, the service ServerView Services (Windows) or SV Services (Linux) searches the user/password list created under ServerView Operations Manager (see "Creating a user/password list" on page 273). ServerView will only identify a BMC if the service ServerView Services (Windows) or SV Services (Linux) can establish a connection to the BMC based on a valid user/password combination. To do this, the service ServerView Services (Windows) or SV Services (Linux) searches the user/password list created under ServerView Operations Manager (see "Creating a user/password list" on page 273). The browser only displays BMCs from Fujitsu in the list. An icon in the first column in front of a BMC indicates that either the BMC or the associated server is already entered in the server list. The browser recognizes Citrix XenServer servers / Xen servers and KVM servers and marks them with the corresponding icon in the second column. The associated virtual servers are indicated by PRIMERGY XEN VM or PRIMERGY XEN VK. Citrix XenServer servers / Xen servers and KVM servers do not always provide IP addresses for the associated virtual servers. But the IP address is required in order to find out the agent status of the virtual servers. The IP address can be assigned to a virtual server in the following ways: o o You can define the IP address later via the Server Properties window. You can insert the systems marked PRIMERGY XEN VM or PRIMERGY XEN VK into the server list. ServerView Operations Manager can then assign the servers to the Xen/Citrix group or the KVM group automatically on the basis of the UUID or MAC address. The virtual servers in the group therefore get an IP address and their status can be determined. ServerView Operations Manager 139

140 4.5 Defining and adding objects ServerView identifies Hyper-V servers, provided that the service ServerView Services (Windows) or SV Services (Linux) can establish a connection to the Hyper-V server based on a valid user/password combination. To do this, the service ServerView Services (Windows) or SV Services (Linux) searches the user/password list created under ServerView Operations Manager (see "Creating a user/password list" on page 273). If the browser recognizes Hyper-V servers, it marks them with the corresponding icon in the second column. The associated virtual servers are marked as PRIMERGY HYPER-V. The IP address is required in order to find out the agent status of the virtual servers. So that Hyper-V Server provides IP addresses of the virtual servers the following conditions must be met: o o o The VM guest must be running. This requires that in WMI in the class Msvm_ ComputerSystem the property EnabledState is set to Enabled. The VM guest must have current integration modules installed. VM guests running Windows Server 2008 R2 or higher already have appropriate versions of integration modules. For Windows Server 2008 VM guests and earlier, the integration modules must be upgraded. If these conditions are not made, Hyper-V servers will not provide the IP addresses for the associated virtual servers. Then, the IP address can be assigned to a virtual server in the following ways: o o You can define the IP address later via the Server Properties window. You can insert the systems marked PRIMERGY HYPER-V into the server list. ServerView Operations Manager can then assign the servers to the Hyper-V group automatically on the basis of the UUID or MAC address. The virtual servers in the group therefore get an IP address and their status can be determined. ServerView identifies blade server chassis. When you add a blade server chassis to the server list, the server blades of this blade server chassis are also added to server list automatically. The browser recognizes servers with Agentless Service based on the IPMI or SNMP protocols and stores this information in the ServerView database. The protocols provided by the servers with Agentless Service are added to the server list. Network instances which have been successfully searched are displayed in a small window next to the list of located objects. ServerView Operations Manager 140

141 4.5 Defining and adding objects Assigning a server type If you select the option Automatic in the selection list in the top right, each of the selected objects will be assigned the server type that has been automatically determined by the browser. Storage subsystems are recognized as follows: Storage subsystem ETERNUS DX60-S2/DX80-S2/ DX90-S2/DX410-S2/DX440-S2/DX8700-S2 ETERNUS DX60-S3/DX100-S3/DX200- S3/DX500-S3/DX600-S3/DX8700- S3/AF250/AF650 ETERNUS DX60-S4/DX100-S4/DX200- S4/DX500-S4/DX600-S4/AF250-S2/AF650- S2 ETERNUS TAPE LIBRARY ETERNUS CS800 NetApp All others Recognized server type ETERNUS DX-S2 ETERNUS DX-S3 ETERNUS DX-S4 ETERNUS LT ETERNUS CS NetApp Other Table 65: Server types of the storage subsystems You can also define the server type yourself (e.g. server, blade server, cluster, PRIMEPOWER, storage). Select Other for other TCP/IP devices such as printers. If you want to add hosts with virtualization software (e.g. VMware, Hyper-V, Xen) as normal server without virtual features, you must select type Server in the selection list or disable VM Host Discovery in the VM Discovery step of the Base Configuration Wizard. If you click the Apply button, the displayed values are applied to all the selected servers. ServerView Operations Manager 141

142 4.5 Defining and adding objects Possible sources of error during searches Under certain circumstances, errors may occur during browser operation. There are many possible reasons for this: ServerView Operations Manager can only find computers that are powered up. Some items of network information are sometimes not recognized when the Microsoft Windows Network is searched. This depends on the method used by Microsoft Windows to obtain network information (i.e. on the broadcast method). A subsystem may not be accessible due to security measures. In addition, a subsystem may not be available because the subsystem server cannot be accessed. In such cases, the search operation is terminated when the time limit is exceeded. However, this may take several minutes. Other network systems may not be available for similar reasons. If a server is labelled as unknown even though its IP address is known, then the computer is inactive or a network error has occurred. If it takes a long time to resolve the computer name into the IP address, then it is possible that WINS or DNS is not properly configured on the login computer. It is possible that the addresses of the primary or secondary WINS servers or the addresses of the DNS servers are invalid. If the WINS protocol has not been activated correctly, then IP address resolution is performed using the very slow broadcast name query procedure. You can configure WINS and DNS using the TCP/IP parameters in the network settings. There may be a variety of reasons why it was not possible to find any IP addresses: o o o o o TCP/IP is not installed on the remote computer. WINS has not been activated on the computer at which you have logged in. In your LAN, there is no WINS server, no DNS information or no LMHOSTS files. The WINS database has not been updated. If the address could not be resolved by WINS, DNS or via LMHOSTS files, then a broadcast name query is performed. Such queries may fail due to the network topology or because of performance problems if, for example, the routers in a subsystem do not forward the broadcast name queries. If virtual systems are not recognized, either the user/password combination could be wrong or the virtual system might not have some of the conditions ServerView needs in order to recognize and query it. Browsing a network finishes once all hosts from the IP range are explored (successfully or not). In some cases, e.g. when active firewalls are used, it is possible that established network sessions to some hosts are not closed and no data is transmitted from the hosts to the monitoring system. In this case, the browsing will end after a configurable timeout. ServerView Operations Manager 142

143 4.5 Defining and adding objects The timeout value is determined in the file tomee/shared/svom/classes/serverbrowser.properties via the BrowsingTimeout key (default: 900 seconds). Changing the parameter requires a restart of the ServerView Application Server Adding objects to the server list 1. In the ServerBrowser window, choose the objects that you want to add: o o You should either define an object in the Server Address tab, or select one or more objects in the browser. 2. Then click the Apply button. The name and network address of a configured object must be unique. If you try to create an object with the same name or the same network address as an already configured object, an error message will be displayed. You cannot create objects manually in a cluster. All the server nodes are automatically added to the cluster and the associated server objects are generated automatically. If a server object has already been defined in the All Servers group, then it is automatically added to the cluster Adding hosts with virtualization software as normal servers to the server list You can add hosts with virtualization software (e.g. VMware, Hyper-V, Xen) as a normal server without virtual features: 1. In the ServerBrowser window, choose the host with virtualization software that you want to add: o o You should either define an object in the Server Address tab, or select a host in the browser. 2. Select Server in the selection list for the server type. 3. Then click the Apply button. To discover hosts with virtualization software always as normal servers in the browser, you must disable VM Host Discovery in the VM Discovery step of the Base Configuration Wizard. For further information see the Base Configuration Wizard documentation. ServerView Operations Manager 143

144 4.5 Defining and adding objects Adding VMware ESXi hosts as of version 6 and higher You can discover ESXi hosts with VMware ESXi version 6 and higher via two different methods: Discovering ESXi hosts and establishing an authorized connection to the ESXi web services, using a user/password combination from the user/password list. Discovering ESXi hosts without setting credentials. This method allows you to detect ESXi hosts without attempting access to credentialprotected information on the node. This way, you can evade problems that occur due to unsuccessful authorization. To switch between these methods, proceed as follows: 1. Go to Administration Base Configuration Wizard (Access Control step). 2. Enable/Disable the Discover ESXis ver 6 and higher as "lack-of-credentials" hosts checkbox. An ESXi server discovered using the second method will be displayed in the ServerBrowser window with its IP address as its host name and the information (no credential set) in the description. These ESXi servers can be added to the server list as usual, see "Adding hosts with virtualization software as normal servers to the server list" on page Adding TCP/IP devices to the server list ServerView Operations Manager also supports other TCP/IP devices such as printers. These devices cannot be managed but simply respond to "ping" polling. Proceed as follows to add these devices to the server list: 1. Open the ServerBrowser window (menu Administration ServerBrowser). 2. Enter the IP address of the device and select Other as the device type. 3. Confirm by clicking Apply. The device is displayed with the corresponding icon in the server list. Defining applications You can define web applications for these TCP/IP devices. 1. In the context menu, open the Server Properties property window for the device. 2. Enter the web application's URL under Web Application (URL) to be started for this machine in the TCP Application tab. To start the application, click the device in the server list. ServerView Operations Manager 144

145 4.5 Defining and adding objects Adding objects by importing archive data To add a new server to the server list, you can also import a server's archive data. To do this, proceed as follows: 1. Select the ServerList menu and choose Import Archive. 2. In the Import Archive window, select the archive you want to import and click Import. 3. Confirm the question that follows with OK. The server with the selected archive is now entered in the server list. When you import a blade server's archive data, you must first import the blade server s archive and then the archives for the individual server blades. When you import the archive data of a PRIMEQUEST chassis, you must first import the archive of the PRIMEQUEST chassis and then the archives for the individual partitions Adding objects by importing import files You can add objects to the server list by creating an import file (csv or xml file) for these objects and then importing this file into the server list. This procedure is especially suitable for adding a list of servers and server groups to the server list. You can create the csv or xml file by exporting the server list (see "Exporting the server list" on page 154), or independently of ServerView by means of scripts. For each server the information is taken from the import file and stored to the ServerView database. Please note: 1. If an import file contains only a few entries for the objects (menu item Export File, option Short under Server Entries), a server will be added to the server list with the server type automatic. In this case, the ServerList Service will analyze the IP address and determine its type. 2. If the import file contains the parent of the group (for example, a blade server), it will be imported. The ServerList Service will explore it to determine its members. 3. If the import file contains server group members (menu item Export File, option Include Server Group Members under Server Entries), they will not be added to the Serverlist. These are server blades and servers of the server types VirtualPartition and VMHosts. 4. If an imported server is a member of a group, it will be added to this group during import. If the imported server is a parent of the group, see point 2. If the imported server is a server group member, see point 5. ServerView Operations Manager 145

146 4.5 Defining and adding objects 5. If a group contains a server group member, this server will not be added to the group during the import. You must add it manually after it has been discovered by the ServerList Service Importing objects via import files via ServerList menu To import the file, proceed as follows: 1. In the ServerList window, open the ServerList menu and select Import Server. The Import Server window opens. 2. Under Import File, click Browse to select the relevant file. 3. Under Options, select the options for the import process: o o Select Include Group Information to include the group structure when importing. If the import file has no group information, the servers will be simply imported without a group structure. Select Overwrite Duplicate Entries to overwrite an entry if a server or group is found in the ServerView database. Otherwise this server or server group will be ignored during the import. 4. If you want to check the import file first, click Parse File. The import file will be parsed. Then you will receive the following information: o o o o The number of servers that will be imported. Details gives you a list of all servers that will be added to the server list during an import. Servers which will be overwritten are indicated accordingly. The number of servers that will not be imported. Details gives you a list of servers that will not be added to the server list and the reasons why. The number of server groups that will be imported. Details gives you a list of all groups that will be added to the server list during an import. The number of server groups that will not be imported. Details gives you a list of groups that will not be added to the server list and the reasons why. During the parsing process, you can change the options described above. 5. If you want to import without an additional check or if you have already checked the import file using the Parse File button, click Import and confirm the question that follows with OK. In this case the objects from the import file are added to the server list. If a server is not yet in the server list, it is added automatically. If the server is already in the server list, the details in the server list (e.g. server name, IP address, community) are overwritten with the details from the csv file. ServerView Operations Manager 146

147 4.5 Defining and adding objects The import file must contain at least the columns Server Name, IP Address, and SNMP Community. If the server type is not specified in the import or is set to automatic, the ServerList Service determines the server type automatically, which can cause delay. Importing objects into a user-defined server group You can import objects directly into a user-defined server group. To do this, proceed as follows: 1. In the file tree in the left pane of the ServerList window, select the user-defined server group. 2. In the associated context menu, select the option Import Server. 3. In the Import Server window, select the relevant import file and proceed as described above. Start the import with OK. The objects will be imported and then added to the server group Importing objects via import files via command line interface You can add servers to the server list with the SVImportServerList command. Under Windows the script is available in the following directory: <Installation_directory>\ServerView Services\scripts\ServerView\common Under Linux the script is available in the following directory: /opt/fujitsu/serverviewsuite/web/cgi-bin/serverview/common Syntax SVImportServerList [-g <group_path>] [-o] [-l] <file> Parameters -g group_path If you want to import your servers under a certain group, you can specify the path name of the group. This path value resembles a file path and should start with /Groups. -o -l This path must exist. If it does not exist, all servers and server groups will be imported directly at the top level AllServers. Specifies that duplicate entries should be overwritten. Specifies that the actions should be logged in the SVImportServerList.log file. ServerView Operations Manager 147

148 4.6 Reinitializing the server file Name of the file containing the data of the servers to be imported. The file must contain the following details: name, IP address and community name. Example "DALLAS"," ","public1" "RX200A1"," ","public" "RX330S12"," ","public" "TX300S42"," ","public" 4.6 Reinitializing the server By reinitializing a server, you delete a server from the server list and subsequently add again in one step. Additionally, you can define or change the server name, server type, and credentials used. This functionality is not available for virtual servers. You can use this functionality to set proper credentials for an ESXi server version 6 and higher that has been added to the server list without credentials. You reinitialize a server with the Reinitialize Server dialog box. 1. Select a server in the server list, open the context menu, and click Reinitialize Server for the Reinitialize Server dialog box to appear. It is not possible to reinitialize more than one server at a time. If you select more than one server in the server list and open the context menu, the Reinitialize Server option is greyed out. 2. Set the Server name, Server type, and Credentials. The server name must be unique, have less than 64 characters, and contain only alphanumeric characters or the signs "-" and ".". The server types in the drop down list are equivalent to the server types list box in the ServerBrowser property window. If the server type is set to Automatic, the ServerList Service determines the server type automatically. The user/password combinations in the Credentials list are taken from the user/password list of Operations Manager. 3. Click Apply to reinitialize the server using the server name, server type and credentials you have set. 4. Click OK to close the window. To close the window without reinitializing the server, you use the Cancel button. To restore the default data for Server name, Server type, and Credentials, you use the Reset button. ServerView Operations Manager 148

149 4.7 Creating user-specific server groups 4.7 Creating user-specific server groups You can also group the servers together on the basis of application-specific criteria (e.g. corporate structure, organizational structure, distribution across different buildings). To do this, you set up the corresponding groups and then assign individual servers to these groups. To define a new group, choose Groups in the left-hand section of the file tree in the ServerList window and then choose New Group in the associated context window. You then enter the name of the new group and the position in the file tree in the New Group window. You can assign new servers to the group using the Copy to group menu item. 4.8 Deleting objects Deleting networks, subnets or domains To delete a network, subnet or domain in the server browser, proceed as follows: 1. Open the ServerBrowser window via the menu Administration ServerBrowser. 2. Choose the relevant subnet or domain in the Subnet/Domain list. 3. Select Delete on the context menu. The selected subnetwork or the relevant domain is deleted from the server browser. Deleting an item in the server browser does not affect the server list Deleting objects from the server list To delete objects from the server list, proceed as follows: 1. In the ServerList window, select the objects/groups that you want to delete. 2. Select Delete in the context menu. If archive data relating to the object is present, then a message is output asking you if the corresponding archives are also to be deleted. While an update is running, the relevant object cannot be deleted from the server list. ServerView Operations Manager 149

150 4.9 Clusters in the server list Deleting objects from the server list via command You can delete servers from the server list with the SVDeleteServer command. Under Windows the script is available in the following directory: <Installation_directory>\ServerView Services\scripts\ServerView\common Under Linux the script is available in the following directory: /opt/fujitsu/serverviewsuite/web/cgi-bin/serverview/common Syntax SVDeleteServer [-f <file>][[<server_name>][<server_name>]...] [*] Parameters -f file Name of the file containing the names of the servers to be deleted. server_name Name of the server to be deleted. You can specify multiple server names, separated by blanks. * Deletes all servers from the server list. 4.9 Clusters in the server list Clusters can be identified in two ways: An object located by the browser may be a cluster. This can be determined by using the associated IP address to check the MIB cluster agent. An object may be a node in a cluster. This can be determined by checking the MIB inventory agent. The server browser queries the name of the cluster from the cluster agent and, if this does not yet exist, adds an entry together with the associated cluster icon to the browser. A cluster is displayed as a special group in the server list. Clusters are subject to a number of limitations. The servers in a cluster form a fixed group that is defined by cluster management. No servers can be added to or deleted from clusters. For this reason, the New and Delete options, the move options and most of the edit options are disabled. The cluster itself may have different statuses. The status is indicated by an icon in the status column in the right-hand window section, see "Icons in the ServerList window" on page 90. ServerView Operations Manager 150

151 4.10 Checking the server list Defining and displaying cluster settings If you select a cluster in the server list and then choose Server Properties in the context menu, the Server Properties property window is displayed. For a description of the tabs, see "Tabs in the property windows" on page 72; the meanings of the buttons are described in "Buttons in the property windows" on page Checking the server list Monitoring is automatically active after you set up the server list. You can click an object to query the status of the entire system and its subsystems, e.g. mass storage, system board, power supply, cooling systems, temperature sensors and operating system. If problems occur, you should check the server list: 1. Check whether the server name and the IP address are entered correctly. 2. In the Test Connectivity window, which you can access via the context menu, check that the server responds within the defined timeout period. Four tests are performed: a. Network connectivity (Check General Access). This is performed by the ping utility. b. General SNMP connectivity (Check SNMP). This queries whether standard SNMP agents are installed on the server and whether SNMP is installed and activated. c. Fujitsu SNMP connectivity (Check Node Type). This queries whether the Fujitsu SNMP agents are installed on the server. If they are, the server type and status are determined. d. Trap test (Check SNMP Trap (Events)). This checks whether traps from this server can be received. With an RSB S2 there is no test-trap support. 3. Repeat these steps for each server. On Linux, if you perform a connection test for the local host ( /localhost), the test trap times out. This is because the system waits for the response from the local host IP address to which the ServerView console made the request, whereas the actual response to the trap received is from the real IP address of the server specified in the SNMP master agent. Monitoring can be performed without any problems in spite of the timeouts. Troubleshooting If one or more tests indicate an error, here some useful hints to probably find the reason of the problem. ServerView Operations Manager 151

152 4.11 Recording archive data via the server list Check General Access: 1. Check the firewall settings as to whether ping functionality is enabled. 2. Check whether the Remote Connector Service is installed and running. 3. Please ensure that the port number 3172 is not blocked by a firewall. Check SNMP: 1. Check whether the MIB II agent (standard SNMP agent) is installed and running. 2. Please ensure that the SNMP request port number (default 161) is not blocked by a firewall. 3. Check the SNMP configuration, especially the community (SNMPv1) or credential configuration (SNMPv3) for the specific servers. Check Node Type: 1. Check whether appropriate SNMP agents are installed and running. 2. In the case of virtual system connections (like Hyper-V, Xen, VMware) check whether necessary software packages are installed and running. 3. Please ensure that the corresponding port number(s) (default: VMware - 443, Hyper-V - 135, Xen , Citrix - 80, KVM /16514) are not blocked by firewall. For Hyper-V servers the dynamic ports for RPC should be opened for the process: %SystemRoot%\System32\dllhost.exe 4. Some virtual connections can only establish a connection using a valid user/password pair. Please ensure that the user/password pairs are match. Check SNMP Trap (Events): 1. Check whether the appropriate SNMP agents are installed and running. 2. Please ensure that the SNMP trap port number (default 162) is not blocked by a firewall. 3. Please ensure that the CIM indication port number (always 3169) is not blocked by a firewall. This number is used by ESXi servers to send the CIM indication, which is translated into an SNMP trap and forwarded to the SNMP trap port. 4. Check the SNMP configuration, especially the trap destination and that SNMP set requests are allowed Recording archive data via the server list You can record archive data for individual servers or a server group without starting the Archive Manager. In the ServerList window, select the corresponding server or group and choose Archive now in the context menu to start archiving. If you select a server group, then a separate archive is created for each server. ServerView Operations Manager 152

153 4.12 Suppressing the alarms for a server 4.12 Suppressing the alarms for a server You can also enable or disable the suppressing of alarms in the server list, via the context menu: 1. Right-click the relevant server in the server list. 2. Select Enable Muted Mode or Disable Muted Mode context menu. The icon for ignoring alarms is displayed or hidden according to your configuration. You can also use this method to configure the ignoring of alarms for server groups. But this icon is not displayed for server groups in the server list. For server groups you can only view the status of this setting via the alarm configuration of the Event Manager. For more on configuring alarms in the Event Manager, see "ServerView Event Manager" user guide Creating new update jobs for servers You can create new update jobs for individual servers without starting the Update Manager. This function is only available if the update status is allowed (normal, warning or critical) and the update type is supported. Proceed as follows: 1. In the ServerList window, select the relevant server from the server list. 2. Select Update Complete Servers from the context menu. The Create Job Wizard window opens. This wizard allows you to create new update jobs. The wizard comprises several dialog boxes to guide you through the individual steps. All required steps are displayed in the tree structure on the left. The Previous and Next buttons take you step by step through the individual screens. 3. Select the LOGON dialog. LOGON is the first step in the wizard. Here you log on to all servers that require user authentication. 4. Select the Change Version dialog. Change Version is the second step in the wizard. Change Version opens the Update Details dialog box, where you can select another version as the new version. 5. Select the Enter Job Name dialog. Enter Job Name is the third step in the wizard. Here you assign a name to the job. 6. Select the Enter TFTP dialog. Enter TFTP is the fourth step in the wizard. This step is only displayed if the update runs via TFTP server (for example, in the case of a management blade). 7. Select the Schedule Job dialog. Schedule Job is the last step in the wizard. Here you specify the time when the job is to be executed. ServerView Operations Manager 153

154 4.14 Exporting the server list 8. To confirm your entries, click Finish. Your settings will be stored in the database. Cancel quits the wizard without saving your changes. For a detailed description of the Create Job Wizard, see the ServerView Update Management user guide, chapter User Interface Exporting the server list You can export the complete server list into a file. The file format can be xml or csv. If you want to export server groups, you must use xml. 1. In the ServerList menu, select Export Server. The Export Server window opens. 2. Under Export File, select the file format (xml file format or csv file format) for the import file. When exporting groups, only the xml file format is possible. 3. Under Options, select the options for the export process: a. Select Include Group Information to include the group structure. If it is not selected, only the servers will be exported. b. Select Include Server Group Members. Server Group Members are child nodes of servers such as blade servers or Citrix XenServer servers. These types of nodes are not imported by Import Server, but will be detected by the ServerList Service. 4. Under Server Entries, select the fields of the server list which are to be exported: a. Select Complete to export all fields of the server list. b. Select Short to export a minimum number of fields. This includes the following fields: o o o ServerName NetAddress SNMP Community o o The import file must contain at least the columns Server Name, IP Address, and SNMP Community. If the server type is not specified or is set to automatic, the ServerList Service determines the server type automatically, which can cause delay when this file will be imported. 5. Click Export to start the export. The file will be created, so that you can view and edit the stored data or save it straight to a file. ServerView Operations Manager 154

155 4.14 Exporting the server list You can insert the exported server list into an existing server list via Import Server. How to import a server list is described in "Adding objects by importing import files" on page 145. If the export of the server list is not performed, check the web browser settings. Example For Internet Explorer: o o o o Select Tools Internet Options. Click the Security tab. Click Custom level... In the Download section, set Automatic prompting for file downloads to Enable. You can import the exported files from other servers. If the files contain more than just ASCII characters and are to be imported onto a central Linux-based management station, we recommend accessing to the Linux ServerView Operations Manager via a Windows PC with Microsoft Internet Explorer. If ServerView Operations Manager is the same version, import is also possible if the ServerView database or the operating system are different. But here too you must access the Linux ServerView Operations Manager via a Windows PC with Microsoft Internet Explorer if you want to import files onto the Linux-based management station Exporting the server list via command line interface You can export the server list to a file with the SVExportServerList command. Under Windows the script is available in the following directory: <Installation_directory>\ServerView Services\scripts\ServerView\common Under Linux the script is available in the following directory: /opt/fujitsu/serverviewsuite/web/cgi-bin/serverview/common Syntax SVExportServerList [-o <outfile>] [-f <xml csv>][-s][-g <grouppath>][-x <group server>][-m] If the command is specified without parameters, the server list including the group structure is exported to the XML file./exportedtables/groupandserverlist.xml. Parameters -o outfile Specifies the export file name. ServerView Operations Manager 155

156 4.15 Defining settings for the server list -f xml csv The file format can be xml or csv. When exporting server groups and servers, only the xml file format can be used. -s A minimum number of fields (short entry form) of the server list are exported. These are the following: o o o ServerName NetAddress SNMP Community -g grouppath Exports all fields of the server list as of this path name of the group (/Groups/mygroup). The path must exist and begin with /Groups. If the path does not exist, the fields of all servers and server groups are exported. -x group server Exports group and server information - or only server information. If only server information is exported, the output file is./exportedtables/server_list.[xml csv] -m When exporting Server Group Members are included such as server blades and VMs Defining settings for the server list You have the option of defining the settings for the updating of the server list. You can activate and deactivate the automatic updating and specify the update interval. Proceed as follows: 1. In the ServerList window, open the ServerList menu and select Settings. The Settings window opens. 2. In the Settings window, click the refresh ServerList on option to activate the automatic updating of the server list. 3. In the Settings window, enter under every seconds the interval at which the list is to be automatically updated. 4. Confirm your entries with OK. Cancel closes the window without applying your changes. The default setting is an automatic update every 5 seconds. ServerView Operations Manager 156

157 4.16 Filtering server list entries 4.16 Filtering server list entries You can filter the server list entries by clicking the corresponding filter icons in the header of the server list. Filter icon in the header of the server list When you click the filter icon, the associated dialog Filtering for Column <column_name> opens in each case. Make your selection and confirm it with OK. Then, only the filtered entries will be displayed, depending on what you have selected. In the standard filter (Standard), all selection elements are selected via checkboxes. In the customized filter (Customize), you either enter your selection directly or using an asterisk as a placeholder. An active filter is indicated by a blue filter icon. ServerView Operations Manager 157

158 5 Querying server data You can query server data about the following servers from the server list: Servers which have the status OK and can thus be managed. Servers for which archive data exists. Servers which have the status Not manageable and are marked with a management controller icon (see "Server not manageable with management controller icon" on page 210). Servers with BMC or irmc which have the status Not manageable (see "Server with BMC/iRMC, not manageable" on page 211). If you click a server in the list or select an entry from the list and select Open from the context menu, the ServerView [server_name] window opens, via which you can request further information about the selected server. You have one further option for opening the ServerView [server_name] window: You can also open the ServerView [server_name] window for a managed server via the Alarm Monitor of ServerView Event Manager. You do this by clicking the server name in the Server column of the alarm list. Figure 45: ServerView [server_name] window ServerView Operations Manager 158

159 The ServerView [server_name] window allows you to request detailed information on the selected server. For example, the information you receive includes data on the system, the hard disks, drives and file systems, installed network boards, extension boards and the contents of the error buffer, among other things. Some items are not supported by some server models. Unsupported items are grayed out or displayed as "N/A". The ServerView [server_name] window is divided into various sections, some of which you can open and close as necessary. The top left section shows the model name and a picture of the model. You can open or close this section as necessary. Under Information/Operation in the bottom left section of the window are menus for accessing further information or operations. By selecting the menus you control the display in the bottom right section. For an overview of the menus see "Menus in the Single System View window" on page 83. The various menus are described in brief in the following sections. Detailed descriptions are provided in the help texts. The display under Information/Operation can be opened or closed as necessary. The header of the right-hand section contains the following: Status icon The status icon indicates the server status according to the selected data of the server (current data or archive data). Alarm icon, if there is an alarm message. If there are several alarm messages for the server, the alarm icon with the highest severity is displayed. Archive icon, if there are archives for the server. VIOM icon, if VIOM is installed on the management station.you will see if the managed server is supervised by VIOM or not. If the server is managed by VIOM, you will get more information in the tooltip belonging to the icon. Displayed Data selection list. In the Displayed Data selection list, select whether you want to access the current data (Online: <date, time>) or archive data (Archive: <date, time>) of the server. You can also access the archive data if a server is not available. This may help explain the cause of the fault. The status icon on the left in the header indicates the server status according to the data selected here. Refresh button Via the Refresh button you can update the status of the selected server and the displayed page when the online data of the server is displayed. This function is not enabled if you have selected a server s archive data. ServerView Operations Manager 159

160 Alternatively the Archive Now button if the server s online data is displayed, or the Export Archive button if archive data is displayed. o o When the server s online data is displayed, you can use Archive Now to create an archive file of the current data of the server. Clicking Archive Now starts the archiving. The archiving would take about one minute or more. You can follow the archiving progress via the Archive Manager. For further information see the "ServerView Archive Manager" user guide. If the server s archive data is displayed, you can use Export Archive to export the current archive data into a new browser window. You can then save the data from the browser window as you wish using the browser command Save As. LED icon, if the server supports the identification LED. The LED icon indicates the status of the server s location function. The following statuses are possible: Table 66: LED display Location function is activated. Location function is deactivated. If you have selected the server s archive data, the LED icon is always gray. The Locate button, if the server supports the identification LED. If a server supports an identification LED, you will see the Locate button in the top right of the ServerView window. Locate allows you to activate the identification LED in order to locate a server in the server room. When the LED is activated and deactivated, the system checks whether this SET operation is allowed for the server and whether a user name and password have been configured. If this is the case, the user name and password are verified. If the authentication fails, a login dialog opens asking for the correct ID. The Locate button is also available for servers with Agentless service when connecting to the server via IPMI or SNMP protocols is possible. When connected via IPMI, user authentication is required. If the login credentials (user name and password) have not previously been saved, the user is prompted to enter the user name and password. If the authentication fails, a login dialog opens asking for the correct ID. This function is not activated if you have selected a server s archive data. Selection box after Cabinet Details ServerView Operations Manager 160

161 5.1 System status Under Cabinet Details you can also see the cabinet type, ID number and door or cabinet status (open or closed). This display can be opened or closed as necessary. 5.1 System status The System Status menu offers the following menus and menu items: Environment with the menu items o o o Cooling Fan Configuration Temperature Mass Storage with the menu item o RAID-Configuration Power Supply o Power Supplies o o o Power Level Power Redundancy Configuration System Board with the menu items o o o o System Processors Memory Modules Voltages BIOS Selftest Performance with the menu items o o o o o Processors Memory Network Storage Others Network with the menu items o o Network Adapters Network Interfaces Driver Monitor The System Status view shows a brief description of the menu items. ServerView Operations Manager 161

162 5.1 System status As well as the menu items you will see status icons, which tell you whether a component is working properly. You can get more information on a component by selecting the corresponding menu item Environment Environment provides a summary overview of the cooling systems, the fan configuration, and temperature sensors of a server and its connected storage subsystems. Further details of the cooling systems, the fan configuration, and temperature sensors are available via the menu items Cooling, Fan Configuration, and Temperature. You also get general information on the server, including the status of the door or cabinet. Please note that not all server types provide information about whether or not the door or case is open. In the case of systems that consist of two cable-connected systems then the second is displayed to the right of the first under Ext. Cab. If present, a T850 PCI Extension Box will be displayed under Ext. Cab Cooling Cooling switches to the Cooling view, which shows all cooling systems of a server in a diagram of the server as well as in the tables Fans Information and Pump Information. Figure 46: Cooling view ServerView Operations Manager 162

163 5.1 System status The tables can be expanded or collapsed as required. The status icon on the left in the tables header indicates the overall status of the cooling devices. If at least one of the fans or pumps has the status Warning or Failed the overall status is set to that state. The fans are indicated by the fan icon in the diagram and in the table. The pumps are indicated by the pump icon in the diagram and in the table. The icon tells you the following: The position of the fan/pump in the cabinet, as indicated by the position of the fan/pump icon in the diagram. The status of the fan/pump, as indicated by the color of the fan/pump icon in the table and diagram: Color Green Yellow Red Gray Meaning OK Warning Failed Cannot be determined Table 67: Status color of the fan/pump icon You can select individual fans/pumps both in the diagram and in the table via the fan/pump icon. The selected fan/pump or the corresponding table entry then has a blue background. Redundant fans/pumps are indicated by directly overlapping fan/pump control symbols. If the two control symbols are both displayed in green, the fans/pumps are redundant. ServerView Operations Manager 163

164 5.1 System status After you replace a fan, you must recalibrate the fan so that the comparative values for the aging process refer to the new fan. If you have installed the ServerView agent as of V3.0 for Windows on the server, you will find a tool as described below: On Windows Server 2008: Select Start [All ]Programs Fujitsu ServerView Suite Agents Maintenance Tools. On Windows Server 2012: 1. Open the Start screen, right-click somewhere at an empty spot, and in the lower right choose All Apps from the bar that appears. 2. Alternatively, you can access the Apps screen by pressing the Windows Logo Key + [Q] combination to go straight to the screen with all applications. The number of revolutions(%) does not change until the number of revolutions of the fan is tested. The number of revolutions of the fan is tested at the time set by the server start, and the remote management controller Fan Configuration Fan Configuration switches to the Fan Configuration view, which shows the status of the fan configuration as well as an overview of all fans of the server in a table. Figure 47: Fan Configuration view ServerView Operations Manager 164

165 5.1 System status If the fan configuration status is "critical", a message will be shown, indicating that additional fans need to be installed. The Fan Configuration view is only available if SvFanConfig is supported by the ServerView Agents. The table shows the status of the fan (indicated by a status icon), the fan number, designation, speed, normal revolutions (percent), fail reaction, shutdown delay (seconds), CSS component and state. The icon in the first column shows the status of the fan sensor: Symbol Meaning OK Critical Warning Component is not available. Table 68: Status icon of the fan sensor Temperature Temperature switches to the Temperature view, which lists all temperature sensors of a server in a table. The table includes the following information: Status of the temperature sensor, indicated by a status icon Purpose of the temperature sensor Current temperature Threshold values of the temperature sensor The icon in the first column shows the status of the temperature sensor: Symbol Meaning OK Critical Warning Table 69: Status icon of the temperature sensor ServerView Operations Manager 165

166 5.1 System status For a PRIMERGY ECONEL 100 S2, the display for the temperature sensor of the CPU is as follows. Basic Threshold: Not displayed Current Temperature: N/A (not available) The status of the temperature sensor itself can be determined by the color of the temperature sensor icon (see above) Mass Storage Mass Storage provides general information about controllers. Controller Under Controller the most important controller-related data are listed: Status, No., Type (EISA, PCI, ISA), Adapter Name. Details of Selected Controller Under Details of the Selected Controller you can find additional, more detailed information on the controller that is selected in the controller list. Depending on which controller type you have selected in the controller list, the link Device View or Raid Configuration will be available under Details of the Selected Controller. Device View link under Details of the Selected Controller You can click Device View in the Controller View to obtain the following additional information: List of attached devices The most important data concerning the devices connected to the controller is displayed under List of attached devices: No., Status, S.M.A.R.T., Type (see HD-MIB), S.M.A.R.T. Status, Name. Only one device may ever be selected in this list. Details of the selected device Further information relating to the device selected in the list is displayed under Details of the selected device: Capacity, SCSI-Channel, SCSI-Target-Id, SCSI-LUN, Sectors, Cylinders, Block Size, Sector Size and an icon for the Device Type together with a status display. S.M.A.R.T. for the selected device Under S.M.A.R.T. for the selected device you will find information provided by the S.M.A.R.T. procedure (Self Monitoring and Reporting Technology). S.M.A.R.T. is a technology used for the early identification of hard disk faults (PDA = Prefailure Detection and Analysis). Both SCSI and ATA hard disks are supported. ServerView Operations Manager 166

167 5.1 System status S.M.A.R.T. is available under Windows and Reliant UNIX as of V5.44 B. If you have selected a RAID controller and clicked Device View in the Controller view, you will receive the following additional information: Link Adapter Model This link opens the ServerView RAID Adapter View, which provides details of the hardware, cache, PCI location and PCI devices. List of logical drives Under List of logical drives the most important details of the controller s partitions are displayed: No., Name, Status and Raid level. Only one drive at a time can be selected in this list. Details of the selected logical drive Further details of the drive selected in the list are shown under Details of the selected logical drive. These include Stripe size, Physical size, Initialization status, Logical size and Operating system device name. Cache Information Under Cache Information details of the cache are displayed: Write mode, Cache mode, Read mode and Disk cache mode. Physical Devices Under Physical Devices the SCSI devices connected to the selected controller are displayed. The link opens the ServerView Raid Physical Device View, which contains further details of the device (including name, type and firmware version) and the corresponding hard disks (including status and storage capacity). RAID Configuration link under Details of the selected controller If the ServerView RAID Manager is installed on the managed servers, you can start it via System Status Mass Storage RAID Configuration. The ServerView RAID Manager offers standardized management and administration of hard disks for PRIMERGY servers. For further information on the RAID Manager, see the ServerView RAID Manager documentation. Events If the Drive Monitor is available on the managed server, you will find under Events all the events relating to the monitored mass storage adapters, as listed in the system event log on the managed server. You can view more information about an event via the +-sign in the first column of the table: ServerView Operations Manager 167

168 5.1 System status The original event log entry The cause of the problem, a summary and solution, if available If you want to view all events relating to the mass storage adapters of the server, click Show All. If you are looking for the affected component of an event, click the relevant entry under Events. This selects the relevant component under Monitored Components RAID information for VMware ESXi servers in the Single System View If a VMware ESXi host is added to the server list as a normal server without virtual host functions, you can get information about the RAID controllers via System Status Mass Storage. The right-hand window pane is divided into three sections, each preceded by a header showing the section name. Figure 48: Mass Storage view Controllers While the Single System View for a VMware ESXi host is being opened, a progress bar is displayed.once the process is completed and the data gathered, the progress bar disappears and the standard ESXi view appears. The top section Controllers lists the main details of the available RAID controllers, i.e. Status, No., Type and Adapter Name. ServerView Operations Manager 168

169 5.1 System status Details of the selected controller The middle section Details of the selected controller shows more information about the RAID controller selected in the controller list. Under List of logical drives you will see the main details of the RAID controller s virtual partitions (logical volumes), i.e. Status, No., Name, RAID level, Stripe size (KB) and Logical size. Only one drive at a time can be selected in this list. Details of the selected drive The bottom section Details of the selected drive shows information about the selected drive. Under List of physical devices you will find information about the physical devices associated with the virtual partitions (logical volumes), i.e. Status, No., Name, Manufacturer, Model and Size Power Supply Figure 49: Power Supply view The Power Supply view gives you a summary overview of the following status: Power Supplies - configuration and status of the server s power supplies. Power Level - status of power level monitoring on the server. Power Redundancy - power redundancy configuration and threshold status. Configuration - power supplies configured for redundancy on the server. Clicking the Status link in the Power Supply view or the menu items in the Power Supply menu gives you further information. ServerView Operations Manager 169

170 5.1 System status The menu items are described below Power Supplies Via System Status Power Supply Power Supplies you can display information on the configuration and status of the power supply of a server or a storage subsystem. This includes: Direct mains connections and UPSes (Uninterruptible Power Supply), if configured (only some types are supported) Cabinet pictures with internal power supply units If your system is connected to a UPS, the power supply will be monitored, and backup power will be provided for a certain period of time in the event of a power failure. During this period, you can save and close open files. If power is not restored by the end of this period, a controlled shutdown of the system is performed. The maximum buffer time is the amount of time that was set as the discharge time for the UPS by means of the management controller software. During a power outage, the length of time the system has already been supplied by the UPS is displayed on screen. Important If the value set for the discharge time is too high and the battery in the UPS is almost empty before the end of the discharge time is reached, a controlled shutdown of the system is performed. The management controller monitors the BBU, the UPS, the cooling systems, the system temperature, and the power supply and initiates a controlled shutdown of the system when required. Cabinet pictures with internal power supply units Here you will see a picture of the server cabinet and a picture for each power supply found. If the system consists of two systems connected by cables, the second system will be shown to the right of the first one under Ext. Cab. Under the picture you see three status. Overall Power Status If the power supply system is operating correctly, a green square will be shown in the lower right corner of the cabinet view picture. A yellow or red square indicates a malfunction. ServerView Operations Manager 170

171 5.1 System status Color Green Red Yellow Meaning Power okay Problems with the power supply. Red indicates an immediate shutdown condition due to one or more of the following reasons: The number of available power supplies is less than the minimum. Power failure: The unit running on a BBU or UPS. Problems with the power supply. Yellow indicates one of the following degraded conditions: Loss of redundancy when running on redundant power supplies. BBU fault: The BBU was removed, the BBU fuse has blown, or the BBU itself is damaged. Power supply: The power supply is bad or damaged. Table 70: Status color of the power supply square A double square here means power supply redundancy. There is at least one active power supply unit more than necessary to run the system. Configuration Status This indicates if the power supply units are configured properly. If multiple units are configured to be redundant, but do not have the same nominal values, you will see an error. Mains Supply with UPS Status Every power supply unit in a cabinet has a colored square to indicate its status. The following colors are used: Color Light gray Green Red Meaning The unit is not present, or its status is unknown. The unit is OK. The unit has failed. Please note that the chassis picture shown is a static one, and may match the current server configuration or not. Table 71: Status color of the power supply square ServerView Operations Manager 171

172 5.1 System status Summary of UPS and cabinet power status This sections only available with extension cabinets. It shows a summary view of all extension cabinets. It also includes option buttons for the selection of each configured extension cabinet (extension storage unit). You can select a specific extension storage unit by clicking the corresponding option button. The numbers shown on the buttons are the cabinet IDs. The squares next to the option buttons show the overall status of the cabinets: UPS (U) and Power (P). Power supplies information The Power Supply Information table shows the most important data on the power supply units. The first column contains an icon showing the status of the power supply unit. The table may also include the following columns: Cabinet ID Number of the unit/cabinet Number Number of the power supply unit Designation Description of the power supply unit (e.g. PSU) CSS Component This column indicates whether the CSS functionality (Customer Self-Service) is supported for the individual components Current Load Current power status in watts Nominal Load Nominal power status in watts State Status of the power supply unit The UPS Information table contains information on the power supply. It only appears if the UPS devices are configured accordingly. The first column contains an icon showing the status of the power supply. The table may also include the following columns: Number Number of the UPS device Vendor Name of the manufacturer (e.g. APC) Manager In the Manager column you can start the UPS Manager via the entry Start UPS Manager. Address The Address column shows the IP address of the server on which the UPS agent is installed or, if the UPS has a web card and its own web server, the IP address of the ServerView Operations Manager 172

173 5.1 System status UPS itself. The IP address of the server is displayed here as it was defined during the agent installation, and the IP address of the UPS is displayed as specified during the UPS configuration. Time on Battery (Seconds) The Time on Battery column shows the total battery time used so far in seconds. Battery State Status of the battery Communication State Status of the interconnected UPS devices State Status of the power supply For more information on the UPS Manager, see "UPS Manager" on page 175. Storage subsystem in the Power Supplies view If the system is a storage subsystem with a web interface and its own IP address (e.g. NetApp, ETERNUS CS800), the Power Supplies view will also include the Configure button, via which you can start the web interface of the storage subsystem Power Level Via System Status Power Supply Power Level you can display information on the power level monitoring and status. You can see following information: If the power control is configured or not, and how the power control is configured (Power Limit Configured). Current power consumption data (Current Power Control). Maximum limit value of the power consumption (Power Limit). Warning limit level (in percent of the maximum limit threshold) (Warning Threshold). Current power consumption (Actual) Maximal power consumption (Maximum). The Power Level link is only activated if Power Consumption Limiting is activated Power Redundancy Via System Status Power Supply Power Redundancy you can display information on the configuration of the power redundancy as well as the number of power supplies running and required for redundancy. You can also see the actual power consumption, the power level, and the threshold status of the power redundancy. ServerView Operations Manager 173

174 5.1 System status Power Supply Redundancy Status Power Supply Redundancy Information if the server is currently running on a redundant power supply. Possible values: Available None If the reduncancy is lost, you can find the reason in the tables below. Redundancy Mode The current running redundancy mode. Possible values: No Redundancy PSU Redundancy Dual AC Redundancy Triple AC Redundancy Redundancy Configuration Redundancy configuration of the power supplies. Possible Values are: No Redundancy PSU 1 PSU + 1 Spare PSU 2 PSU + 1 Spare PSU 3 PSU + 1 Spare PSU Power Supplies Required Number of power supplies needed for the current configuration. Power Supplies Running Number of power supplies running on the server. Power Supply Redundancy Configuration Here you see if the redundancy is configured correctly. Power Supplies Required Number of power supplies needed for the current configuration. Power Supplies Populated Number of power supplies found on the server. Configuration Status Shows if the redundancy was configured correctly and if the number of power supplies needed have been found. Threshold Here you see the thresholds which allow for redundancy. ServerView Operations Manager 174

175 5.1 System status Actual Power Consumption Current power consumption. Redundancy Power Level The highest level of consumption allowed to enable redundancy. Threshold Status If the actual power consumption is higher than the redundancy power level, you will see an error here, which shows that redundancy is not currently possible Configuration Via System Status Power Supply Configuration you can display detailed information about the power supplies configured for redundancy on your system. If power supplies have been configured to be redundant, it is necessary for them to have the same nominal power. This table will help you confirm the values UPS Manager To obtain detailed information on the UPS, you can start the UPS Manager via the entry Start UPS Manager in the UPS Information table (see "Power Level" on page 173). Depending on the settings, ServerView Operations Manager starts either the corresponding UPS Manager software or the Web card's web interface: If the IP address of the UPS is identical to the server's IP address or if UPS Manager software has been registered for the UPS manufacturer and type, then the corresponding UPS Manager software is started. If the IP address is not identical to the server's IP address and no UPS Manager software has been registered for the UPS manufacturer and type, then the Web card's web interface is started via a browser. Therefore, if the IP address is not identical to the server's IP address but UPS Manager software has been registered for the UPS manufacturer and type (e.g. APC UPS), then the corresponding UPS Manager software is started. If you want to manage the APC UPS with Web card via the web interface and have UPS Manager software installed, then you must specify APC WEB UPS as the UPS type. For a UPS with a serial connection, the entry Start UPS Manager only appears if the UPS Manager application has been configured for the displayed PS or a Web UPS (IP addresses of server and UPS different and no UPS Manager software found) has been detected. The following conditions must be satisfied: The UPS must be configured for the server (see the section on installation on managed servers corresponding to your operating system in the ServerView Agents installation and user guide). ServerView Operations Manager 175

176 5.1 System status The UPS Manager application (e.g. APC PowerChute Business Edition or Generex UPS Masterguard Software) must be installed on the ServerView management station. UPS with USB connection is handled as UPS with a serial connection APC UPS ServerView Operations Manager supports the following uninterruptible power supplies (UPS) from APC: UPS with serial connection to the server and corresponding SNMP agents on the managed server UPS with USB connection is handled as UPS with a serial connection. UPS with Web card and dedicated Web server together with the corresponding SNMP agents on the UPS itself APC UPS with serial connection An APC UPS with a serial connection can be monitored using the APC application PowerChute Business Edition. If the UPS Manager is activated via the entry Start UPS Manager in the UPS Information table, a Web page for the selected UPS is opened. The IP address displayed in the Address field in the Power Supply view is that of the server to which the UPS is connected or of the UPS itself if the UPS is network-capable. Before you can start the APC application, you must install the PowerChute Business Edition on the managed servers from the APC CD. The Web server runs with the PowerChute Business agents on the server. APC UPS with Web card If you have selected an APC UPS with Web card and dedicated Web server, you can select Start UPS Manager in the Power Supply view to start the Web card's web interface or the APC UPS Manager application: If the IP address is not identical to the server's IP address and no UPS Manager software has been registered for the UPS manufacturer and type, then the Web card's web interface is automatically started via a browser. If the IP address of the UPS is not identical to the server's IP address but UPS Manager software has been registered for the UPS manufacturer and type, then the APC UPS Manager software is started automatically. ServerView Operations Manager 176

177 5.1 System status If you want to manage the APC UPS with Web card via the web interface and have UPS Manager software installed, then you must specify APC WEB UPS as the UPS type. The APC Web card's web interface For more information on the UPS web interface, see the APC documentation Network management card - user guide System Board The System Board view gives you a summary overview of the following components and their statuses: System Processors - Status and quantity of physical and logical CPUs Memory Modules - Status of the memory modules and size of the memory available Voltages - Voltage status BIOS Selftest - Status of the BIOS self-test Bus and Adapter Summary - Status of the bus systems, such as the supported bus types Trusted Platform Module - Status of Trusted Platform Module (TPM) Clicking the Status link in the System Board view or the menu items in the System Board menu gives you further information. The menu item Busses and Adapters is also available under System Board. The menu items are described in brief below System Processors Via System Status System Board System Processors you can display details of the processors. All existing CPUs and their statuses are shown. Resetting the error status after replacing processors ServerView Operations Manager may report a defective processor in case of a critical error. After replacing a defective CPU, the error counter must be reset manually using one of the methods below on the respective server. ServerView Operations Manager 177

178 5.1 System status Using ServerView Maintenance Tools (Windows only) 1. Launch the ServerView Maintenance Tools: Windows Server 2008 R2 and below: Start [All] Programs Fujitsu ServerView Suite Agents Maintenance Tools Windows Server 2012 and higher: Start Apps Fujitsu Maintenance Tools 2. Choose the CPU status tab. 3. Select the CPU which shows the pre-failure status. 4. Click on Reset Status. 5. Ensure that all pre-fail / fail status issues have been resolved in ServerView Operations Manager. Using the command line (Linux only) Proceed as follows to reset the error counter of a specific processor: 1. Log in as root. 2. Enter the command below, followed by [ENTER]: For rack and tower servers (RX and TX server series): /usr/sbin/eecdcp -c oc=0609 oi=<cpu#> For blade and scale-out servers (BX and CX server series): /usr/sbin/eecdcp -c oc=0609 oi=<cpu#> cab=<cabinet nr> To identify the cabinet number, enter the following command: /usr/sbin/eecdcp -c oc=e204 <CPU#> parameters are "0" for CPU 1 and "1" for CPU If the error status cannot be reset with the method above, please use the following procedure for resetting the error counter of all processors: a. Log in as root. b. Enter the commands below, followed by [ENTER]: i. /etc/init.d/srvmagt stop /etc/init.d/srvmagt_scs stop /etc/init.d/eecd stop /etc/init.d/eecd_mods_src stop ii. cd /etc/srvmagt iii. rm -f cehist.bin ServerView Operations Manager 178

179 5.1 System status iv. /etc/init.d/eecd_mods_src start /etc/init.d/eecd start /etc/init.d/srvmagt start /etc/init.d/srvmagt_scs start 4. Ensure that all pre-fail / fail status issues have been resolved in ServerView Operations Manager Memory Modules Via System Status System Board Memory Modules you can display all memory modules with Designation, Size, Approved, Type, Actual Frequency (MHz), Maximum Frequency (MHz), Voltage, Configuration State, and Module State. Resetting the error status after replacing memory modules ServerView Operations Manager may report a defective memory module in case of a memory error. After replacing a defective memory module, please check if the error counter has been reset automatically. If the memory slot is still marked as failed, please reset the error counter manually using one of the methods below on the respective server. Using the irmc web frontend 1. Enter the ServerView irmc web frontend. 2. Select the System Information menu. 3. Under System Components, select the check boxes next to the affected memory modules. 4. From the drop down list, select Reset Error Counter. 5. Click Apply for the changes to take effect. Using ServerView Maintenance Tools (Windows only) 1. Launch the ServerView Maintenance Tools: Windows Server 2008 R2 and below: Start [All] Programs Fujitsu ServerView Suite Agents Maintenance Tools Windows Server 2012 and higher: Start Apps Fujitsu Maintenance Tools 2. Choose the Memory status tab. 3. Select the memory module which shows the pre-failure status. 4. Click on Reset Status. ServerView Operations Manager 179

180 5.1 System status The Reset Status button will only be available if the selected memory module contains errors. 5. Ensure that all pre-fail / fail status issues have been resolved in ServerView Operations Manager. Using the command line interface (Linux only) The memory error counter can be reset using the meclear utility which is part of the ServerView Agents for Linux. meclear (Memory Module Error Counter Reset Utility) allows to reset the error count collected for a memory module, for example after it has been replaced. For further details, see the meclear manual pages. 1. Log in as root. 2. Enter the command below, followed by [ENTER]: /usr/sbin/meclear 3. Select the number of a memory module with a status other than "OK" or "Not available". 4. Repeat the step above until all memory modules show the "OK" status. 5. Ensure that all pre-fail / fail status issues have been resolved in ServerView Operations Manager Voltages Via System Status System Board Voltages you can display details of the voltage on the server s system board BIOS Selftest Via System Status System Board BIOS Selftest you can display the result of the BIOS self-test. If an icon indicates that an error has caused an entry in the system event log, this icon can be reverted to normal by clicking Reset. For more information on the entry in the SEL, see "System Event Log" on page 195. However, this information is only displayed if the BIOS version has a self-test notification function. When you reinstall ServerView Agents after reverting the icon to normal by clicking Reset, the icon may indicate an error again. Both the old error may light up and a new error may have occurred. In this case, click Reset again to revert the icon to normal. ServerView Operations Manager 180

181 5.1 System status Busses and Adapters Via System Status System Board Busses and Adapters you can display details of the existing bus systems such as EISA or PCI with the connected controllers and their functions Trusted Platform Module Via System Status System Board Trusted Platform Module you can display details of the Trusted Platform Module and its status Performance The menu item Performance provides an overview of the performance and utilization of various components of a managed server. This allows you to better identify performance bottlenecks of specific server components and, if necessary, rectify them, e.g. by installing another processor, a quicker network board, or with similar measures. The necessary data is supplied by the Threshold Manager, which defines and stores threshold values for various performance parameters of a managed server. From the logged data you can display either the current utilization of the components or a graph of the utilization over a longer period. Figure 50: Performance Overview Performance takes you to the Performance Overview, which provides an overview of the status and current utilization of specific server components. At the top of the right window pane immediately below the header Performance Monitoring, you can activate or deactivate the performance monitoring. If the ServerView Operations Manager 181

182 5.1 System status performance monitoring is activated, this is indicated by the icon on the left. If you click the Deactivate button to the right of it, the performance monitoring is deactivated for this server. This button is only enabled if the performance monitoring is globally activated (Base Configuration Wizard: Threshold Management step or Threshold Manager: Settings tab). If the performance monitoring is deactivated, this is indicated by the icon on the left. If you click the Activate button to the right of it, the performance monitoring is activated for this server. This button is only enabled if the performance monitoring is globally activated (Base Configuration Wizard: Threshold Management step or Threshold Manager: Settings tab). The measured values of the different performance parameters are shown on the following tabs: Processors tab The Processors tab contains data for the utilization status of the physical and logical CPUs. Memory tab The Memory tab contains data for the status and utilization of the main memory. Network tab The Network tab contains data for the status of the network and for the utilization of the network throughput. Storage tab The Storage tab contains data for the status and utilization of the mass storage. Others tab The Others tab contains data for the status and utilization of other current performance parameters. By clicking a tab you switch to the corresponding view of the current utilization of the server component. The tabs are structured identically. Each tab contains a table with eight columns. The columns are supplied with the data ascertained by the Threshold Manager. They list the identified values and the stored threshold values. If the Threshold Manager cannot identify a value for a performance parameter, this is indicated in the table by the value N/A and the status?. The Performance Overview uses various status icons, which depict the following statuses: The status icon above the tabs shows the overall status of the selected server component. Which icon is displayed is determined by an evaluation of all performance parameters by the Threshold Manager. The status icon on the tab part of a tab sheet shows the monitoring status of the Threshold Manager specifically for this tab sheet. ServerView Operations Manager 182

183 5.1 System status The status icon in the Status column shows the status of the corresponding performance parameter. The following icons are possible: The measured value is within the normal value range. The measured value exceeds the critical threshold. The measured value exceeds the warning threshold or falls below the warning threshold. The value cannot be determined. Processing: Calculation is in progress. Not Available: There is no connection to the agent. Table 72: Status icons in the Performance Overview view By clicking a column in the table header, you can change the display of the information individually (e.g. the sorting and sequence of the columns). The table contains the following columns: Status The status icon in the Status column shows the status of the corresponding performance parameter. Parameter This column contains a set of parameters that are monitored on the basis of defined threshold values of the Threshold Manager. The parameters are server-type-specific, meaning that not all parameters are displayed for every server. Also, not every parameter is supported by all virtualization software (VMware, Hyper-V, Citrix XenServer / Xen, KVM), so potentially no values could be returned. For Hyper-V servers to be recognized by a Windows Server 2008 R2 (x64) or Windows Server 2012, an entry in the Windows Registry regarding access restrictions has to be changed, see "Hyper-V Servers in the server list" on page 118. ServerView Operations Manager 183

184 5.1 System status For Processors the following parameters are monitored: Parameter cpuall (%) cpukernel (%) cpuuser (%) cpuvm (%) cpumax (%) cpumin (%) cpuh (%) cpuv (%) Meaning Utilization of all physical processors Utilization of all physical processors in kernel mode Utilization of all physical processors in user mode Utilization of the physical processors by virtual machines Maximum processor utilization (%) over a selected interval Minimum processor utilization (%) over a selected interval CPU utilization of a virtual machine based on the host CPU utilization of a virtual machine based on the resources allocated to it Table 73: Monitored Processors parameters For Memory the following parameters are monitored: Parameter memory (%)1) memoryvm (%) Meaning Memory currently in use Amount of memory that is actively used from amount of memory available. Table 74: Monitored Memory parameters 1) For physical servers: The experience shows that if a system is having memory problems, the available swap space may be full.therefore, the total of physical memory and swap space is the basic measurement value for memory usage. The percentage is calculated as (used memory + used swap) / (available memory + available swap). Usually, this value will converge to a value given by the relationship between available memory and available swap and thus stay below the default threshold. Only if there is a memory shortage and swap space starts filling up an alert will be triggered. ServerView Operations Manager 184

185 5.1 System status For Network the following parameters are monitored: Parameter networkreceive (kb/sec) networktransmit (kb/sec) networktotal (kb/sec) Meaning Incoming network throughput Outgoing network throughput Incoming and outgoing network throughput Table 75: Monitored Network parameters For Storage the following parameters are monitored: Parameter storageread (kb/sec) storagewrite (kb/sec) storagetotal (kb/sec) storageusage (%) storageusage - <logical drive> storageusage - C:\(%) storageusage - /boot (%) Meaning Read throughput for mass storage Write throughput for mass storage Read and write throughput for mass storage File system usage File system usage of a logical drive. For example: File system usage of drive C:\ File system usage of /boot directory Table 76: Monitored Storage parameters For Others the following parameters are monitored: Parameter capacityreserved (%) Meaning Amount of memory reserved by the selected server Table 77: Monitored Others parameters Date / Time Shows the date and time of the last value measured. Current Value This column contains the currently measured performance values, regardless of whether threshold values are exceeded or not reached. Depending on the type of ServerView Operations Manager 185

186 5.1 System status parameter, the values are entered in % or kb/sec. If there is no value available, N/A is displayed. Average Value This column contains the average performance values over the selected time interval, regardless of whether threshold values are exceeded or not reached. Depending on the type of parameter, the values are entered in % or kb/sec. If there is no value available, N/A is displayed. The Average Value is the relevant one for a threshold value statement. Lower Warning Threshold which, if not reached (e.g. due to poor utilization), leads to a Warning message in the Threshold Manager. Depending on the type of parameter, the values are entered in % or kb/sec. If there is no value available, N/A is displayed. Upper Warning Threshold which, if exceeded, leads to a Warning message in the Threshold Manager. Depending on the type of parameter, the values are entered in % or kb/sec. If there is no value available, N/A is displayed. Upper Critical Threshold which, if exceeded, leads to a Critical message in the Threshold Manager. Depending on the type of parameter, the values are entered in % or kb/sec. If there is no value available, N/A is displayed. By clicking the menu items Processors, Memory, Network, Storage or Others under Performance (on the left in the structure tree), in addition to the current component values, you can also display the utilization of the server components over a longer period in the form of a graph. The menu items are described briefly below. ServerView Operations Manager 186

187 5.1 System status Deleting old performance values In the vmemanager.xml file you can define a time interval after which a stored performance value is to be deleted. The time interval specifies the period in minutes that a value is to remain stored. If this period is exceeded, the relevant performance values will be deleted. By default, performance values are deleted when the following periods expire: Performance values that are generated every minute are deleted after two weeks. Performance values that are generated every hour are deleted after two years. Performance values that are generated every day are deleted after 10 years. You can change the default time intervals according to your requirements. Proceed as follows: 1. Open the vmemanager.xml file. You will find this file in the following directory: o o for Windows: C:\Programs\Fujitsu\ServerView Suite\ServerView Services\ scripts\serverview\vmemanager\conf for Linux: /opt/fujitsu/serverviewsuite/web/cgi-bin/serverview/vmemanager/conf 2. Search for the section: <!-- performance data cleaning interval --> <minutesstoragetime>20160</minutesstoragetime> <hourstoragetime> </hourstoragetime> <daystoragetime> </daystoragetime> 3. Change the settings according to your requirements. 4. Save the file Processors Via System Status Performance Processors, you can display details of the processors. All existing CPUs, their status and utilization are displayed. You are shown both the current utilization and the utilization over a longer period. ServerView Operations Manager 187

188 5.1 System status Figure 51: Performance - Processors view Structure of the right window pane The right-hand window pane is divided into three sections, each with a header showing the section name. You can open or close each section via the selection box in front of the respective section name. The top section Current Processors Values shows the current component values of the processors. The layout and information in this section corresponds to the display on the Processors tab. In the middle section History Options you define a reporting period for the bottom section History Chart. The performance values logged over this period are displayed in a graph in the History Chart. You can specify the following periods: Time interval, or Exact period with start and end time ServerView Operations Manager 188

189 5.1 System status You activate the time interval by clicking the option Last and selecting one of the intervals offered from the corresponding pull-down menu. You can choose from the following values: 1 hour Default The measured values from the last hour. 12 hours The measured values from the last 12 hours. 1 day The measured values from the last 24 hours. 1 week The measured values from the last week. 2 weeks The measured values from the last two weeks. 1 month The measured values from the last month. 1 year The measured values from the last 12 months. The intervals at which a value is measured are determined by the Threshold Manager. For an exact period, you define the date and time by clicking the option From xxx To xxx. You can specify an exact start date and an exact end date via the calendar icons next to the date fields. A window opens for you to set the date. You can set the exact time for the start and end of the display via the arrow buttons to the right of the time fields. The new settings are applied when you click the LOAD button. The bottom section History Chart shows the performance values for the period selected in the History Options as a graph. By clicking in the graph and then holding down the left mouse button while moving the mouse to the right or left, you can enlarge or compress the section of the graph shown on the screen. This is sometimes useful for particularly elongated or compressed curves. Clicking the right mouse button restores the original diagram. Depending on how many parameters were recorded for this component, several values can be shown in the graph simultaneously. This can make the figure very confusing and therefore not very informative. In the Show box under the graph you can set how many curves you want to see simultaneously. You do this by selecting or deselecting the relevant parameters. If you move the mouse pointer over the graph, a tooltip appears with the information parameter, date, and value in % or kbytes/sec. ServerView Operations Manager 189

190 5.1 System status Memory Via System Status Performance Memory you can display performance parameter data for the status and utilization of the main memory. From the logged data you can display either the values for the current utilization or a graph of the utilization over a longer period. You can define the period for the graph yourself. By default the values from the last hour are displayed. The right-hand window Memory has the same structure and display as the Processors window. For a detailed description of the layout and the setting options, see "Processors" on page Network Via System Status Performance Network you can display performance parameter data for the status of the network and the utilization of the network throughput. From the logged data you can display either the values for the current utilization or a graph of the utilization over a longer period. You can define the period for the graph yourself. By default the values from the last hour are displayed. The right-hand window Network has the same structure and display as the Processors window. For a detailed description of the layout and the setting options, see "Processors" on page Storage Via System Status Performance Storage you can display performance parameter data for the status and utilization of the mass storage. From the logged data you can display either the values for the current utilization or a graph of the utilization over a longer period. You can define the period for the graph yourself. By default the values from the last hour are displayed. The right-hand window Storage has the same structure and display as the Processors window. For a detailed description of the layout and the setting options, see "Processors" on page Others Via System Status Performance Others you can display further performance parameters for the status and utilization of the specified server. From the logged data you can display either the values for the current utilization or a graph of the utilization over a longer period. You can define the period for the graph yourself. By default the values from the last hour are displayed. ServerView Operations Manager 190

191 5.1 System status The right-hand window Others has the same structure and display as the Processors window. For a detailed description of the layout and the setting options, see "Processors" on page Network The Network view provides a summary of the following components: Network Adapters - Status and number of network adapters, plus any related events. Network Interfaces - Number of network boards Network Adapters Selecting System Status Network Network Adapters provides information about the network adapters as well as the associated events listed in the system event log on the managed server. Monitored Components Under Monitored Components the network adapters are listed. If a component has the status Warning or Error, you can select it in the list and click Acknowledge. This confirms the event on the server side. You may have to log on to the server beforehand. The status of the component will then be set to ok. To see the new status you must refresh the Driver Monitor view with Refresh. Details If you have selected a network adapter in the list under Monitored Components, you will find additional information on this network adapter under Details. Events If the Drive Monitor is available on the managed server, you will find under Events all events relating to the network adapters, as listed in the system event log on the managed server. You can view more information about an event via the +-sign in the first column of the table: The original event log entry The cause of the problem, a summary and solution, if available If you want to view all events relating to the server, click Show All. If you are looking for the affected component of an event, click the relevant entry under Events. This selects the relevant component under Monitored Components. ServerView Operations Manager 191

192 5.1 System status Network Interfaces Selecting System Status Network Network Interfaces gives you general information on the available network boards of the selected server. If you click the name of a network component in the table under Description or in the Network Interfaces menu, detailed information on the selected component is displayed. In the view of the selected network component, the Details tab provides detailed information on the selected component. If MAC statistics are available, the Mac Statistics tab is also displayed. Lan Teaming If the selected network component (Broadcom or Intel) is assigned to a LAN team, you will find the Lan Teaming entry. If no LAN teaming is set up or the selected network component does not belong to a team, this link is not present. Figure 52: Lan Teaming view Detailed information about the LAN team is displayed. Under Network Interfaces (Summary) you will see an overview of the configured LAN teams and their components. Under Lan Team Properties the properties of the LAN team are displayed. Under Lan Team Statistics the available statistics are displayed. ServerView Operations Manager 192

193 5.1 System status During installation of the software kit IntelRPRONetworkConnectionsSoftwareDriver_168, you must select the option Intel(R) Network Connections SNMP Agent for traps to be receivable by the managed server Driver Monitor The Driver Monitor view gives you an overview of the monitored components (LAN, Fibre Channel and PCI RAID controllers) as well as the associated events contained in the System Event Log (SEL) on the managed server. Only applies to PRIMERGY servers and to servers of the PRIMEQUEST systems. This function is only activated if the ServerView Agents for Windows V5.10 and higher are installed on the managed server. Monitored Components Under Monitored Components the monitored components are listed. If a component has the status Warning or Error, you can select it in the list and click Acknowledge. This confirms the event on the server side. You may have to log on to the server beforehand. The status of the component will then be set to ok. To see the new status you must refresh the Driver Monitor view with Refresh. Details If a component has the status Warning or Error, the system status and error lamp also indicate Warning or Error. Click Acknowledge button to set the status to ok. ESXi server events in the Driver Monitor have limited functionality and do not provide information about events in the System Event Log (SEL) on the managed server. If you have selected a component in the list under Monitored Components, you will find more information on this component under Details. Events Under Events you will find all the events relating to the selected component, as listed in the System Event Log (SEL) on the managed server. You can view more information about an event via the +-sign in the first column of the table: The original event log entry The cause of the problem, a summary and solution, if available ServerView Operations Manager 193

194 5.2 System If you want to view all events relating to the server, click Show All. If you are looking for the affected component of an event, click the relevant entry under Events. This selects the relevant component under Monitored Components. 5.2 System The various items on the System menu provide the following information about the selected server: System Information System information, including the system name, server model, UUID, firmware version, installed operating system, processor type and asset tag. Agent Information Version of the inventory MIB, version number of the agents and list of the configured SNMP agents. Operating System Information about the installed operating system. Processes Information about the running processes. File Systems Information about the file system, including type, size and free space. Partitions Information about the partitions, including status, type, name and size. Resources Information about the utilization of operating resources by hardware components via the tabs IRQ, I/O-Port, DMA and Memory. ServerView Operations Manager 194

195 5.3 Maintenance 5.3 Maintenance Battery Information Under Battery Information, you obtain information on the age of the installed battery. When you replace the CMOS battery, you must reset the counters (total power-on time, total power-off time and total number of power-ups). If you have installed the ServerView agent as of V3.0 for Windows on the server, you will find a tool as described below: On Windows Server 2008: Select Start [All ]Programs Fujitsu ServerView Suite Agents Maintenance Tools. On Windows Server 2012: 1. Open the Start screen, right-click somewhere at an empty spot, and in the lower right choose All Apps from the bar that appears. 2. Alternatively, you can access the Apps screen by pressing the Windows Logo Key + [Q] combination to go straight to the screen with all applications System Event Log System Event Log displays the entries from the System Event Log (SEL). Above the table you can select which messages you want to display: Critical events Major events Minor events Informational events Any combination of the four different severities You can also specify the time zone (GMT or Local) for the displayed messages. Via the Date/Time column you can sort the table by date/time. By default the first entry in the table contains the most recent message, the last entry the oldest. Clicking the column header reverses the sort sequence. If the ServerView agent provides additional information on errors, their causes and how to remedy them, this is indicated by a box in the first column of the table. If you click this box, this information is displayed. ServerView Operations Manager 195

196 5.3 Maintenance The table also contains the additional column No. for the event number - numbered according to the order in which the agent sent the event messages. By default the event messages are listed in descending order. You can sort the table according to this column by clicking the column header. If you click the header again, the order of the entries will be reversed Server Properties The menu item Server Properties displays the Server Properties view in the right-hand section. This view contains several tabs, via which you can view or configure the various server settings. Server Address tab You can enter a server's IP address in this tab. Via the Network Address selection list, you specify whether you want to enter an IPv4 address or an IPv6 address. If you are viewing properties for a server blade, you can manually define the IP address used for this server blade. You are given a list of possible addresses to choose from. Check the box in Configure Blade Network Address area if you want to keep the server blade configured with this address. Then it will not be changed automatically. You use the Test Connectivity button to test the connection to the server via the In-band Connectivity (primary address) and Out-of-band Connectivity (secondary address). In the case of server blades, you test the server blade connection via the In-band Connectivity in the Test Connectivity dialog and test the connection to the blade server via the Out-of-band Connectivity. In the case of blade servers, you can only test the In-band Connectivity in the Test Connectivity dialog. If you try to test the Out-of-band Connectivity, you will see the error message No Out-of-band Connectivity available! In the case of PRIMEQUEST chassis and PRIMEQUEST Partition systems, you can only test the In-band Connectivity in the Test Connectivity dialog. If you try to test the Out-of-band Connectivity, you will see the error message No Out-of-band Connectivity available! Network/Snmp tab In this tab you can set the parameters for the network operation of a server. The following parameters can be defined: Connection port, SNMP Settings, Poll Interval (sec), Timeout (sec), and Connectivity Change Trap ServerView Operations Manager 196

197 5.3 Maintenance When assigning the SNMP settings to a server node, clicking Configure opens the SNMP Settings window, where you can choose between SNMPv1 and SNMPv3 and set the parameters for the SNMP connection. Figure 53: SNMP Settings window The following settings can be made in the SNMP Settings window: SNMP v1 Sets protocol version 1 of SNMP. Community Sets the community of SNMPv1. The community name must consist of one-byte alphanumeric characters. Special characters (such as " # & ~ \ + *? / :) cannot be used. SNMP v3 Sets protocol version 3 of SNMP. User Select a user name from a credential set containing the user name. ServerView Operations Manager 197

198 5.3 Maintenance Authorization Specify the authorization algorithm used by the user. None You are allowed to configure SNMPv3 without authorization. MD5 Message-Digest Algorithm 5 (MD5) is used for authentication. SHA Secure hash algorithm (SHA) is used for authentication. Password from set: Selection of a password for authorization from a credential set containing the user name. Privacy Specify the encryption algorithm used by the user. None You are allowed to configure SNMPv3 without encryption. DES Digital Encryption Standard is used for encrypting the SNMPv3 traffic. AES Advanced Encryption Standard (AES) 128-bit encryption is used for encrypting the SNMPv3 traffic. Secure hash algorithm (SHA) is used for authentication. Password from set: Selection of a password for encryption from a credential set containing the user name. SNMP Port Specify a common port for SNMPv1 and SNMPv3. Saving the settings Click the OK button in the SNMP Settings window. ServerView Operations Manager 198

199 5.3 Maintenance Important A non-default UDP port can also be specified as the Connection Port. If Receive Trap after Change is enabled, the following trap is sent when the status of a monitored server changes. o o If the server can be monitored: Server changed state (The server <server name> has changed its state to snmpok or OK) If the server cannot be monitored: Server changed state (The server <server name> has changed its state to not manageable) The default setting is enabled with two polling intervals and no trap if the connectivity status of the managed servers is changed on startup of the ServerView management console. If the load on the network or server is too high, it can be improved by changing Poll Interval, Timeout, and Refresh Delay. CIM tab In this tab you can control and set the address used when creating a subscription on a server which supports a CIM Provider. The first address (Subscription address) is the CIM subscription address currently used by the Operations Manager for this VMware ESXi server. Normally it is the Operations Manager IP address. If the CMS has more than one LAN interface, the address is automatically detected by the Operations Manager as the best match to ESXi address by checking all address segments. This works currently for IPv4 addresses only. The second address (User Subscription Address) is a user-defined CIM subscription address. You can edit this field. The CIM subscription address is to be used by CMS for this VMware ESXi server. This tab is also available to other servers because in the future they will also support a CIM provider. Local Note tab In this tab you can enter local notes. Local notes are added to the server list and help to identify a server in this list more quickly. Login tab In this tab, you can define the Username and Password that are used when a set request is sent to the server. Here you also specify whether the password is to be queried on every ServerView Operations Manager 199

200 5.3 Maintenance change of setting or only on the first modification following program start. Your password is only stored temporarily, for as long as you have ServerView Operations Manager windows open. You can select the checkbox Take Username as default login. The user name will then be taken as the default when a new server is added to the server list. Remote Service Board tab This tab displays the server name, the community and the IP address of the secondary channel if an RSB is installed. You can test the connection to the RSB by clicking the Test Connectivity button. With an RSB S2 there is no test-trap support. If the server cannot be reached via the primary channel, you can enter the server name and IP address of the secondary channel here. Once the server is reachable again, the primary channel is automatically used again. Clicking Configure starts a web browser in which you can configure the RSB. BMC tab In this tab you can enter or change the IP address of a BMC. Under Configure BMC Network Address you can select the IP address to be used for the relevant BMC. Under Possible Addresses you will find a list of all possible addresses to choose from. If you always want to use this address, select Always use this address for the BMC. Under BMC Network Address you can specify the address explicitly. You can select the format of the IP address from the selection list (IPv4 or IPv6). You use the Test Connectivity button to test the connection to the server via the In-band Connectivity (primary address) and Out-of-band Connectivity (secondary address). In the case of server blades, you test the server blade connection via the In-band Connectivity in the Test Connectivity dialog and test the connection to the blade server via the Out-of-band Connectivity. In the case of blade servers, you can only test the In-band Connectivity in the Test Connectivity dialog. If you try to test the Out-of-band Connectivity, you will see the error message No Out-of-band Connectivity available! In the case of PRIMEQUEST chassis and PRIMEQUEST Partition systems, you can only test the In-band Connectivity in the Test Connectivity dialog. If you try to test the Out-of-band Connectivity, you will get the error message No Out-of-band Connectivity available! ServerView Operations Manager 200

201 5.3 Maintenance ASR&R The ASR&R Properties view displays values for the agents monitoring the system. These include cooling control, temperature sensor control, watchdog control and power-on/off control and tell the system how to react when an error occurs in this area. You can only see the configuration of these properties in this view. You can change the configuration via System Configuration. Not all ASR settings are supported on all servers. If, when you select a server, you see that N/A is set for a field, this means that the parameters are not supported. This view will not be automatically refreshed. If an error occurs, appropriate measures can be taken. o o A server can be set to automatically shut down if it is about to overheat (temperature monitoring), and then start up again after a specified period of time. A system can, for example, initiate an automatic restart if it could not be started because of a temporary failure in a SCSI cable or SCSI hard disk (see boot monitoring). For monitoring VMware ESXi server the user can set watchdog settings. Configuring the watchdog for VMware ESXi server is only possible via irmc and not via the ServerView Configuration Manager. Cooling tab This tab displays a list of the cooling systems (fans/pumps) which are configured in the server. The Action and Shutdown Delay (sec) columns show how the system will react if the fan/pump fails. Temperature tab This tab displays a list of temperature sensors which are configured in this server. The Action column shows how the server will react when the sensor reaches its critical temperature. Restart tab This tab displays the actions after a power failure as well as the time period for the automatic power-up delay and the specified number/default number of possible reboot attempts. The tab also shows which action is performed if the defined number of reboot attempts is exceeded. Power On Off tab This tab displays the schedule of the defined power-on/power-off times for a server. ServerView Operations Manager 201

202 5.3 Maintenance The settings of the managed server are written to the BIOS. Make sure you disable the server s power on/off scheduling before ServerView is uninstalled from the server. If you uninstall ServerView with the scheduling enabled, the server may be shut down at an unexpected time. Watchdog tab This tab displays the watchdogs and their actions which are configured in this server. Type Type of the watchdog Software The software watchdog is a timer that is periodically reloaded by the server control agent. If the system crashes and the agent stops working (usually because of a software problem), the action for this watchdog will be executed. This automatic mechanism can be used to fix any hang-up situations on your server. Boot The boot watchdog is a timer that is started once by the server control agent. If the system crashes and the agent stops working (usually because of a software problem), the action for this watchdog will be executed. This automatic mechanism can be used to fix any hang-up situations on your server. Active Indicates whether the watchdog is currently running or not. Manageable Indicates whether the server is currently manageable or not. Action The action that is triggered if the watchdog timeout is exceeded. Timeout The defined time interval Boot Options The Boot Options menu item opens the Boot Options view. This view shows details of the boot status and the reason for the last startup or shutdown. Reasons why a server was started up or shut down are assigned to the server and displayed under Last PowerOn Reason and Last PowerOff Reason. If a server model does not allow the reasons to be determined, Unknown is displayed. Under Restart Options you will see whether a standard boot is performed (Standard Boot) or whether at the next startup the diagnostic system is to be started (Boot Diagnostic System). ServerView Operations Manager 202

203 5.3 Maintenance Under Shutdown Delay you can find out how long the system will wait before it shuts down Remote Management Under System LAN, information on the network configuration is displayed: address type, IP address and MAC address. Under Baseboard Management Controller, information about the controller is displayed. The view differs depending on the type of the remote management controller in the managed server: For a server with a RemoteView Service Board (RSB) or a Baseboard Management Controller (BMC), you will find the description of the Remote Management view in "Remote Management (RSB, BMC)" on page 203. For a server with an integrated Remote Management Controller (irmc), you will find the description of the Remote Management view in "Remote Management (irmc)" on page Remote Management (RSB, BMC) This view offers the following buttons: RSB Manager (for RSB only) Starts the RSB s web interface if the managed server incorporates an RSB. BMC Power Management (for BMC only) Starts the Power Management via the BMC if a BMC is integrated in the managed server. Details of the ServerView Remote Management front-end and the web interface of the RSB are provided in the Remote Management documentation Remote Management (irmc) This view offers the following buttons: irmc Web Starts the web interface of the irmc. This button is only available if the server supports it. Video Redirection Starts Advanced Video Redirection (AVR) in a new browser window. AVR redirects the graphical output of the managed server to the screen of the management station and assigns the keyboard and mouse input on the management station to the managed server. You can also start AVR via a context menu in the server list (see "Server list" on page 105). ServerView Operations Manager 203

204 5.3 Maintenance For more information on the ServerView Remote Management front-end, see the Remote Management documentation PrimeCollect With PrimeCollect you can collect and store information about the hardware and software of PRIMERGY servers. To collect the data, you click the Collect Data button. To store the results data, you click the displayed link. For further information see the documentation on ServerView PrimeCollect Online Diagnostics Online Diagnostics allows you to carry out a range of hardware tests on the managed PRIMERGY server from the remote workstation: Memory test CPU stress test Hard disk test Optical drive test Various tabs are available for this: Predefined Tests tab You use this tab to start predefined test sequences. Custom Test tab This tab allows you to configure all the available test parameters individually. You can also define a schedule for the conduct of the individual tests. Status and Control tab You use this tab to obtain information about the status of the tests and control test execution. In addition, any messages or alerts logged during the tests are listed here. For more information on the Online Diagnostics tool, please see the documentation ServerView Operations Manager Online Diagnostics. ServerView Operations Manager 204

205 5.3 Maintenance Customer Self Service Figure 54: Customer Self Service view Customer Self Service provides an overview of the Customer Self-Service (CSS) components of a managed server. This menu is only displayed if the ServerView Agents for Windows/Linux as of V4.52 are installed on the managed server. A CSS component is a server component that you can replace yourself. The following are CSS components: Hot-plug hard disk drives Hot-plug power supply units Main memory System fans Expansion cards The following information is displayed for the individual components: Status of the component Name of the component Type of the component (CSS component or non-css component) If applicable, a link to the Illustrated Spares catalogue With the newer PRIMERGY servers (e.g. TX 150 S6, RX300 S4 and RX200 S4), a link after the entries in the table takes you directly to the relevant Illustrated Spares catalogue, via which you can order a replacement for the defective CSS component. If no relevant page is found for the server, the overview page for the Illustrated Spares catalogues is displayed. ServerView Operations Manager 205

206 5.4 Virtualization If no CSS component is found, a corresponding error message is output. You can filter the display in this view to show all components, CSS components or non-css components as appropriate, via the selection list under CSS Component. 5.4 Virtualization The Virtualization menu is only enabled if you have selected a server with virtualization software in the server list. The menu offers the following items: Host Properties Virtual Machines These menu items are briefly described in the Virtualization Overview Host Properties The menu item Host Properties provides details of the virtualization host: Its status Server identification data Hardware data Virtualization software Operating system information Virtual Machines The menu item Virtual Machines provides details of the virtual machines. All virtual machines are listed on the left in the tree structure. On the right is a list of all virtual machines of the virtualization host selected in the server list. The table contains the following columns: Column with selection boxes You can select the virtual machine by clicking its box. Status Status of the virtual machine. Name Name of the virtual machine. Power State Power status of the virtual machine. ServerView Operations Manager 206

207 5.4 Virtualization Network Network name of the virtual machine. OS Installed operating system. OS Description Description of the installed operating system. Clicking the name of a virtual machine in the table or in the tree structure opens the individual view containing details of this virtual machine. In the Virtual Machine view you can also activate and deactivate virtual machines. 1. Select the relevant virtual machines in the list by clicking the boxes in front of them. 2. Then click the appropriate button: Start Activates the virtual machine. Stop Deactivates the virtual machine. Suspend Suspends the virtual machine. Resume Resumes running of a temporarily suspended virtual machine. The individual buttons are enabled or disabled depending on the status of the virtual machines Evacuation of virtual servers in the event of an error The ServerView Operations Manager functions for server monitoring and alarm management allow you to evacuate virtual servers on VMware systems in the event of an error. You can thus take preventive action in the case of imminent system errors or overloads. Evacuation of the virtual servers of affected systems onto other, unaffected systems occurs during operation. Users can still access their running systems, despite actual server failure. Possible downtimes can thus be eliminated. The function for evacuating virtual servers relies on the script evacuate.ps1. You must copy this script into your chosen target directory and customize certain variables within it. The events that trigger an evacuation are defined by the user via the Alarm Configuration component in the Event Management. If one of these predefined events occurs, for example PDA will start and initiate previously defined reaction chains, the virtual machines are evacuated in the event of an error. The administrator is always kept up-to-date by s from the Alarm Management. ServerView Operations Manager 207

208 5.4 Virtualization Requirements To allow virtual servers to be evacuated in the event of a fault, the following requirements must be met: ServerView Operations Manager and the Event Management must be installed and configured on a Windows-based management station. Windows PowerShell must be installed. You can install Windows PowerShell 1.0 on Windows Server 2008/2012/2016 via the Features option of the Windows Server Manager (see the "ServerView Operations Manager - Installation under Windows" user guide). VMware vsphere PowerCLI must be installed. You can download VMware vsphere PowerCLI from the VMware download area. The installation is interactive. When you have downloaded VMware vsphere PowerCLI, you must install it. Proceed as follows: Figure 55: VMware vsphere PowerCLI 1. Click Continue. 2. Open the PowerShell input prompt (right mouse button). 3. Enter R (for RunOnce). 4. Enter Set-ExecutionPolicy Remote-Signed. 5. Copy the PDA script evacuate.ps1 into the desired target directory (e.g. C:\FTS\scripting). As of ServerView Operations Manager V5.0 you will find the PDA script evacuate.ps1 under: C:\Program Files\Fujitsu\ServerView Suite\svom\bin\ServerView\common 6. Customize the following variables of the PDA script evacuate.ps1: $LOGDIR = "c:\tmp\evacuate" $LOGFILE = $LOGDIR + "\\evacuate.log" # Log directory # Log filename ServerView Operations Manager 208

209 5.4 Virtualization $DEBUG = $false $VISERVER = " " $ADMIN = "Administrator" $PW = "password" # Verbose Logging # vcenter Server # vcenter account # vcenter password 7. Specify which alarms are to lead to evacuation of the virtual servers. To do this you must define Alarm Rules, Filter Rules and General Settings as per the general alarm handling via the Alarm Configuration component in the Event Management. For a detailed description of the settings for the alarm handling, see "ServerView Event Manager" user guide, chapter "Alarm Configuration". Only the special features are described below. When defining the alarms that trigger evacuation, you can choose any alarms you wish (Alarm Rules Assign Alarms), but it makes sense to only choose those which indicate a potential server failure or which belong to the error class critical or major. The following alarms can lead to a system failure: Alarm ID Component Description Error class 673 CPU Impending CPU error major 2081 CPU Impending CPU error major 668 RAM Error in memory module anticipated 2068 RAM Impending failure of memory module major major 2013 Fan/Pump Fan/Pump critical major 678 Battery Impending battery failure major 2054 Battery Impending battery failure major Disk The relevant hard disk could soon fail minor Table 78: Critical events In the dialog box Alarm Rules Assign Destinations, you must define as the action to be triggered by an alarm that an executable program (Execute) will be started. When you have selected Execute for the forwarding, the New Execute Configuration window opens. In this window, on the Exec Settings tab, you must specify a (descriptive) name for the Execute settings in the Description field and enter the following statement via the Command field. C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -psc "D:\Program Files (x86)\vmware\infrastructure\vsphere PowerCLI\vim.psc1" ServerView Operations Manager 209

210 5.5 Server not manageable with management controller icon -c ". \"D:\FTS\Scripting\evacuate.ps1\" \"$_SRV\" \"$_TRP\" \"$_TYP\" \"$_IPA\" \"$_CTY\" \"$_SEV\" \"$_TIM\" \"$_IDN\" " Then in the Working directory field, enter the name of the working directory in which Command is to be located. When you have made your settings, activate (Enable) your configuration. 5.5 Server not manageable with management controller icon If you click a non-manageable server with a management controller icon, you only see the Remote Management view in the ServerView [server_name] window. In this case there will only be a few menu items available under Information/Operation. You can choose whether you see the online data of the managed server or, if available, the archive data of the managed server. The following options are available in the Remote Management view: Starting the RSB web interface using the RSB Manager button. Starting the Power Management via the BMC using the BMC Power Management button. Starting the web interface of the irmc via irmc Web. Video Redirection Starts Advanced Video Redirection (AVR) in a new browser window. AVR redirects the graphical output of the managed server to the screen of the management station and assigns the keyboard and mouse input on the management station to the managed server. You can also start AVR via a context menu in the server list (see "Server list" on page 105). Further information on the web interface of the RSB and on the ServerView Remote Management front-end is provided in the Remote Management documentation. ServerView Operations Manager 210

211 5.6 Server with BMC/iRMC, not manageable 5.6 Server with BMC/iRMC, not manageable If a server with BMC or irmc has the status not manageable, clicking the entry in the server list takes you to the Confirm View window. Figure 56: Confirm View window - Example for BMC You have the following options: With View Archive Data you can access archive data. With BMC Power Management you can start the ServerView Remote Management front-end via the Baseboard Management Controller (BMC) - provided that a BMC is installed on the managed server. For more information on the ServerView Remote Management front-end, see the Remote Management documentation. ServerView Operations Manager 211

212 6 Querying blade server data By clicking a blade server in the ServerList window you open the ServerView [blade_ server_name] window. To begin with, the Blade List view is displayed, showing all blades of a blade server (e.g. server blades, switch blades, management blades) and their statuses. Figure 57: ServerView [blade_server_name] The ServerView [blade_server_name] window is divided into various sections, some of which you can open and close as necessary. The top left section shows the model name and two pictures of the model. You can open or close these pictures as required. The display of the front and rear views of the blade server (BX600/900) is dynamic and is updated depending on which blades it contains. The individual blades of the blade server can be selected in these views. The selected blade will be marked accordingly in the table under the menu item Blade List. Under Information/Operation in the bottom left section of the window are menus for accessing further information or operations. By selecting the menus you control the display in the bottom right section. The various menus are described in brief in the following sections. Detailed descriptions are provided in the help texts. The display under Information/Operation can be opened or closed as necessary. ServerView Operations Manager 212

213 The header of the right-hand section contains the following: Status icon The status icon indicates the server status according to the selected data of the blade server (current data or archive data). Alarm icon, if there is an alarm message. If there are several alarm messages for the blade server, the alarm icon with the highest severity is displayed. Archive icon, if there are archives for the blade server. Displayed Data selection list. In the Displayed Data selection list, select whether you want to access the current data (Online: <date, time>) or archive data (Archive: <date, time>) of the blade server. You can also access the archive data if a blade server is not available. This may help explain the cause of the fault. The status icon on the left in the header indicates the blade server status according to the data selected here. Refresh button Via the Refresh button you can update the status of the selected blade server and the displayed page when the online data of the blade server is displayed. This function is not enabled if you have selected a blade server s archive data. Alternatively the Archive Now button if the blade server s online data is displayed, or the Export Archive button if archive data is displayed. o o When the blade server s online data is displayed, you can use Archive Now to create an archive file for the blade server. Clicking Archive Now starts the archiving. You can follow the archiving progress via the Archive Manager. For further information see the "ServerView Archive Manager" user guide. If the blade server s archive data is displayed, you can use Export Archive to export the current archive data into a new browser window. You can then save the data from the browser window as you wish using the browser command Save As. ServerView Operations Manager 213

214 6.1 Blade List LED icon, if the server supports the identification LED. The LED icon indicates the status of the blade server s location function. The following statuses are possible: Location function is activated. Location function is deactivated. Flashing: The LED icon indicates a system problem. In this case the Locate button cannot be used. Table 79: LED display If you have selected the blade server s archive data, the LED icon is always gray. 6.1 Blade List If you select the menu item Blade List under Information/Operation, you will see in the Blade List view below the header a table, which lists all blades of a blade server (e.g. server blades, switch blades, management blades) and their statuses. The status is determined and forwarded by the management blade agent. ServerView Operations Manager 214

215 6.1 Blade List The different blade types can be identified in the Blade List by the following icons: Management blade (master) Management blade (slave) Switch Blade (master) Switch Blade (slave) Switch Blade Fibre Channel pass-through blade LAN pass-through blade KVM blade Fibre Channel switch blade Storage blade Server blade Front Side I/O module Table 80: Blade types If you select an object in the table, it will likewise be selected in the front or rear view of the blade server. Vice versa, you can select an object in the blade server views which is then likewise selected in the table. With some blade types (e.g. server blade, switch blade, management blade), the name in the Name column is a link: With a switch blade or management blade, this link opens the interface for configuring the blade. How to configure a blade server is described in the RemoteView Management Blade manual, and how to configure switch blades is described in the LAN Switch Blade manual. With a server blade, the link opens the ServerView [server_name] window. ServerView Operations Manager 215

216 6.2 BladeServer Status Details of Selected Blade Below the table, the Details of Selected Blade section shows further information on the blade selected in the table. With server blades and switch blades, you will also see the Locate button in the bottom right. This button switches the LED function on and off for the relevant blade. The status icon next to the button indicates the following two statuses: Flashing Location function is activated. Location function is deactivated. Table 81: LED display for a server blade or switch blade The Locate button is also available for servers with Agentless service when connecting to the server via IPMI or SNMP protocols is possible. When connected via IPMI, user authentication is required. If the login credentials (user name and password) have not previously been saved, the user is prompted to enter the user name and password. If the authentication fails, a login dialog opens asking for the correct ID. 6.2 BladeServer Status The BladeServer Status menu offers the following menus and menu items: Environment with the menu items o o o Cooling Fan Configuration Temperature Power Supply The BladeServer Status view shows a brief description of the menu items. As well as the menu items, you will see status icons, which tell you whether a component is working properly. You can get more information on a component by selecting the corresponding menu item Environment The menu item Environment provides a summary overview of the cooling systems, the fan configuration, and temperature sensors. More detailed information is available via the respective menu items Cooling, Fan Configuration, and Temperature. ServerView Operations Manager 216

217 6.2 BladeServer Status Cooling Cooling switches to the Blade Server Cooling view, which shows all cooling systems of a blade server in a diagram of the blade server as well as in a table. The fans are indicated by the fan icon in the diagram and in the table. The pumps are indicated by the pump icon in the diagram and in the table. The icon tells you the following: The position of the fan/pump in the cabinet, as indicated by the position of the fan/pump icon. The status of the fan/pump, as indicated by the color of the fan/pump icon: Color Green Yellow Red Gray Meaning OK Warning Failed Cannot be determined Table 82: Status color of the fan/pump icon You can select individual fans/pumps both in the diagram and in the table via the fan/pump icon. The selected fan/pump or the corresponding table entry then has a blue background Fan Configuration Fan Configuration switches to the Fan Configuration view, which shows the status of the fan configuration as well as an overview of all fans of the server in a table. This view supports by problems with the fan configuration. If the fan configuration status is "critical" a message will be shown, that it is necessary to install additional fans. The Fan Configuration view is only available if SvFanConfig is supported by the ServerView Agents. The table displays the status of the fan (indicated by a status icon), the fan number, the designation, the speed, the normal revolutions (percent), the fail reaction, the shutdown delay (seconds), the CSS component and the state. The icon in the first column shows the status of the fan sensor: ServerView Operations Manager 217

218 6.2 BladeServer Status Symbol Meaning OK Critical Warning Component is not available. Table 83: Status icon of the fan sensor Temperature Temperature switches to the Temperature view, which lists all temperature sensors of a blade server in a table. The table includes the following information: Status of the temperature sensor, indicated by a status icon Purpose of the temperature sensor Current temperature Threshold values of the temperature sensor The icon in the first column shows the status of the temperature sensor: Symbol Meaning OK Critical Warning Table 84: Status icon of the temperature sensor ServerView Operations Manager 218

219 6.2 BladeServer Status Power Supply Power Supply gives you information on the blade server s power supply. Figure 58: Power Supply view The power supply units are indicated in a diagram of the blade server by a square. The square tells you the following: The position of a power supply unit in the housing, as indicated by the position of the square in the diagram. The status of the power supply unit, as indicated by the color of the square: Color Green Red Gray Meaning Power supply unit working okay Power supply unit failed Agent not responding Table 85: Status color of the power supply square ServerView Operations Manager 219

220 6.3 System The Overall Power Status indicator shows the overall status of the power supply in the blade server. The color of the square means: Color Green Red Yellow Meaning Power okay Power interrupted Problems with the power supply Table 86: Status color of the overall power supply square The Mains Supply Status indicator shows the status of the mains power supply via the following icons: Symbol Meaning Server or storage subsystem working okay Fault in server or storage subsystem Table 87: Status icon of the mains power supply The Power Supply Information table shows the most important data on the power supply units. The UPS Information table contains information on the power supply. It only appears if the UPS (Uninterruptible Power Supply) devices are configured accordingly. In the Manager column of the UPS Information table, you can start the UPS Manager via the entry Start UPS Manager. The Address column shows the IP address of the UPS agent. This is the IP address of the UPS agent as specified during configuration of the UPSes via the RemoteView management blade. For more information on the Power Supply view see "Power Supply" on page System System offers the menu item System Information, which provides details such as the system name, server model, UUID, firmware version, installed operating system, processor type and asset tag. ServerView Operations Manager 220

221 6.4 Maintenance 6.4 Maintenance Maintenance offers you the following menu items: System Event Log, via which you can view the entries in the System Event Log (SEL). For more information see "System Event Log" on page 195. Server Properties, via which you can view and configure various ServerView settings. For more information see "Server Properties" on page 196. Management Blade Configuration, via which you can start the Management Blade Configuration Tool in a new window. The menu items under Maintenance are not activated if the blade server s archive data is displayed. ServerView Operations Manager 221

222 7 Querying PRIMEQUEST Partition data You can query server data about the following servers from the server list: Servers which have the status OK and can thus be managed. Servers for which archive data exists. If you click a server in the list or select an entry from the list and select Open from the context menu, the ServerView [server_name] window opens, via which you can request further information about the selected server. You have one further option for opening the ServerView [server_name] window: You can also open the ServerView [server_name] window for a managed server via the Alarm Monitor of ServerView Event Manager. You do this by clicking the server name in the Server column of the alarm list. By clicking a PRIMEQUEST Partition server in the ServerList window you open the ServerView [PRIMEQUEST_partition_server_name] window. Figure 59: Window ServerView [PRIMEQUEST partition server name] The ServerView [PRIMEQUEST partition server name] window allows you to request detailed information on the selected partition. For example, the information you receive includes data on the system, the hard disks, drives and file systems, installed network boards, extension boards and the contents of the error buffer, among other things. ServerView Operations Manager 222

223 The ServerView [PRIMEQUEST partition server name] window is divided into various sections, some of which you can open and close as necessary. The top left section shows the partition name and a picture of the partition logo. You can open or close this section as necessary. Under Information/Operation in the bottom left section of the window are menus for accessing further information or operations. By selecting the menus you control the display in the bottom right section. For an overview of the menus see "Menus in the Single System View window" on page 83. The various menus are described in brief in the following sections. Detailed descriptions are provided in the help texts. The display under Information/Operation can be opened or closed as necessary. The header of the right-hand section contains the following: Status icon The status icon indicates the server status according to the selected data of the server (current data or archive data). Alarm icon, if there is an alarm message. If there are several alarm messages for the server, the alarm icon with the highest severity is displayed. Archive icon, if there are archives for the server. Displayed Data selection list. In the Displayed Data selection list, select whether you want to access the current data (Online: <date, time>) or archive data (Archive: <date, time>) of the server. You can also access the archive data if a server is not available. This may help explain the cause of the fault. The status icon on the left in the header indicates the server status according to the data selected here. Refresh button Via the Refresh button you can update the status of the selected server and the displayed page when the online data of the server is displayed. This function is not enabled if you have selected a server s archive data. Alternatively the Archive Now button if the server s online data is displayed, or the Export Archive button if archive data is displayed. o o When the server s online data is displayed, you can use Archive Now to create an archive file of the current data of the server. Clicking Archive Now starts the archiving. You can follow the archiving progress via the Archive Manager. For further information see the "ServerView Archive Manager" user guide. If the server s archive data is displayed, you can use Export Archive to export the current archive data into a new browser window. You can then save the data from ServerView Operations Manager 223

224 7.1 System Status the browser window as you wish using the browser command Save As. Selection box after Cabinet Details Under Cabinet Details you can see the cabinet ID, cabinet type and ID number, also door or cabinet status (open or closed). This display can be opened or closed as necessary. 7.1 System Status The System Status menu offers the following menus and menu items: System Boards with the menus of the system boards SB#<number> and the respective associated menu items o o o IOBs System Processors Memory Modules Voltages Environment with the menu items o o Cooling Temperature Mass Storage with the menu item o RAID-Configuration BIOS Selftest Busses and Adapters Performance Network Interfaces The System Status view shows a brief description of the menu items. As well as the menu items you will see status icons, which tell you whether a component is working properly. You can get more information on a component by selecting the corresponding menu item. ServerView Operations Manager 224

225 7.1 System Status System Boards The System Boards view provides a summary of the system board components. For more detailed information you can select a system board directly via the menu item SB#<number>. For details of CPUs, memory and voltages, select the menu items System Processors, Memory Modules and Voltages. Clicking the Status link in the System Board view or the menu items in the System Boards menu gives you further information. The menu items are described in brief below System Processors Via System Status System Board SB#<number> System Processors you can display details of the processors. The details include the number of physical CPUs and their status Memory Modules Via System Status System Board SB#<number> Memory Modules you can display all memory modules with Designation, Module State and Size Voltages Via System Status System Board SB#<number> Voltages you can display details of the voltage on the server s system board IOBs The IOBs view (Input/Output Board) gives you a summary of the I/O boards. It shows a list of the I/O boards and their status. For more detailed information you can select an I/O board directly via the menu item IOB#<number>. ServerView Operations Manager 225

226 7.1 System Status Environment Figure 60: Environment view Environment provides a summary overview of the cooling systems and temperature sensors of a PRIMEQUEST partition. More detailed information is available via the menu items Cooling and Temperature Cooling Cooling switches to the Cooling view, which shows all cooling systems of a PRIMEQUEST Partition in a diagram of the PRIMEQUEST Partition as well as in a table. The fans are indicated by the fan icon in the diagram and in the table. The pumps are indicated by the pump icon in the diagram and in the table. The icon tells you the following: The position of the fan/pump in the cabinet, as indicated by the position of the fan/pump icon. The status of the fan/pump, as indicated by the color of the fan/pump icon: ServerView Operations Manager 226

227 7.1 System Status Color Green Yellow Red Gray Meaning OK Warning Failed Cannot be determined Table 88: Status color of the fan/pump icon You can select individual fans/pumps both in the diagram and in the table via the fan/pump icon. The selected fan/pump or the corresponding table entry then has a blue background Temperature Temperature switches to the Temperature view, which lists all temperature sensors of a PRIMEQUEST Partition in a table. The table includes the following information: Status of the temperature sensor, indicated by a status icon Purpose of the temperature sensor Current temperature Threshold values of the temperature sensor The color of the temperature sensor icon in the first column shows the status of the temperature sensor: Symbol Meaning OK Critical Warning Table 89: Status icon of the temperature sensor ServerView Operations Manager 227

228 7.1 System Status Mass Storage Figure 61: Mass Storage view Mass Storage provides general information about controllers. Under Controller the most important controller-related data are listed: Status, No., Type (ex. PCI), Adapter Name. Under Details of Selected Controller you can find additional, more detailed information on the controller that is selected in the controller list. Depending on which controller type you have selected in the controller list, the link Device View or Raid Configuration will be available under Details of Selected Controller. Device View You can click Device View in the Controller View to obtain the following additional information: List of the attached devices The most important data concerning the devices connected to the controller is displayed under List of the attached devices : No., Status, S.M.A.R.T., Type (see HD- MIB), S.M.A.R.T. Status, Name. Only one device may ever be selected in this list. Details of the selected device Further information relating to the device selected in the list is displayed under Details of the selected device: Capacity, SCSI-Channel, SCSI-Target-Id, SCSI-LUN, Sectors, Cylinders, Block Size, Sector Size and an icon for the Device Type together with a status display. ServerView Operations Manager 228

229 7.1 System Status S.M.A.R.T. for the selected device Under S.M.A.R.T. for the selected device you will find information provided by the S.M.A.R.T. procedure (Self Monitoring and Reporting Technology). S.M.A.R.T. is a technology used for the early identification of hard disk faults (PDA = Prefailure Detection and Analysis). Both SCSI and ATA hard disks are supported. S.M.A.R.T. is available under Windows. RAID Configuration If the ServerView RAID Manager is installed on the managed servers, you can start it via System Status Mass Storage RAID Configuration. The ServerView RAID Manager offers standardized management and administration of hard disks for PRIMERGY servers. For more information on the RAID Manager, see the ServerView RAID Manager documentation BIOS Selftest Via System Status System Board BIOS Selftest you can display the result of the BIOS self-test Busses and Adapters Via System Status System Board Busses and Adapters you can display details of the existing bus systems such as PCI with the connected controllers and their functions Performance Via Performance you can start the Performance application. It provides an overview of the performance and utilization of various components of a managed server. This allows you to identify performance bottlenecks on specific components and correct them if necessary. For further details see "Performance" on page 181. ServerView Operations Manager 229

230 7.1 System Status Network Interfaces Figure 62: Network Interfaces view Network Interfaces gives you general information on the network boards of the selected PRIMEQUEST partition. If you click the name of a network component in the table under Description or in the Network Interfaces menu, detailed information on the selected component is displayed. In the view of the selected network component, the Details tab provides detailed information on the selected component. If MAC statistics are available, the Mac Statistics tab is also displayed: Lan Teaming If the selected network component (Broadcom or Intel) is assigned to a LAN team, you will find the Lan Teaming entry. If no LAN teaming is set up or the selected network component does not belong to a team, this link is not present. Detailed information about the LAN team is displayed. Under Network Interfaces (Summary) you will see an overview of the configured LAN teams and their components. Under Lan Team Statistics the available statistics are displayed. Under Lan Team Properties the properties of the LAN team are displayed. ServerView Operations Manager 230

231 7.2 System 7.2 System The various items on the System menu provide the following information about the selected server: System Information System information, including the system name, server model, UUID, firmware version, installed operating system, processor type and asset tag. Agent Information Version of the inventory MIB, version number of the agents and list of the configured SNMP agents. Operating System Information about the installed operating system. Processes Information about the running processes. File Systems Information about the file system, including type, size and free space. Partitions Information about the partitions, including status, type, name and size. Resources Information about the utilization of operating resources by hardware components via the tabs IRQ, I/O-Port, DMA and Memory. Maintenance Information about the menu items under Maintenance, including Battery Information, Server Properties, Boot Options, Remote Management and Prime Collect. ServerView Operations Manager 231

232 8 Querying PRIMEQUEST chassis data By clicking a PRIMEQUEST chassis in the ServerList window you open the ServerView [PRIMEQUEST_chassis_name] window. To begin with, the Partition List view is displayed, showing all partitions of a PRIMEQUEST chassis and their statuses. Figure 63: ServerView [PRIMEQUEST chassis name] The ServerView [PRIMEQUEST_chassis_name] window is divided into various sections, some of which you can open and close as necessary. The top left section shows the model name and a pictures of the model. You can open or close this picture as required. The individual partitions of the PRIMEQUEST chassis can be selected in these views. The selected partition will be marked accordingly under the menu item Partition List. Under Information/Operation in the bottom left section of the window are menus for accessing further information or operations. By selecting the menus you control the display in the bottom right section. The various menus are described in brief in the following sections. Detailed descriptions are provided in the help texts. The display under Information/Operation can be opened or closed as necessary. ServerView Operations Manager 232

233 The header of the right-hand section contains the following: Status icon The status icon indicates the server status according to the selected data of the PRIMEQUEST chassis (current data or archive data). Alarm icon, if there is an alarm message. If there are several alarm messages for the PRIMEQUEST chassis, the alarm icon with the highest severity is displayed. Archive icon, if there are archives for the PRIMEQUEST chassis. Displayed Data selection list. In the Displayed Data selection list, select whether you want to access the current data (Online: <date, time>) or archive data (Archive: <date, time>) of the PRIMEQUEST chassis. You can also access the archive data if a PRIMEQUEST chassis is not available. This may help explain the cause of the fault. The status icon on the left in the header indicates the PRIMEQUEST chassis status according to the data selected here. Refresh button Via the Refresh button you can update the status of the selected PRIMEQUEST chassis and the displayed page when the online data of the PRIMEQUEST chassis is displayed. This function is not enabled if you have selected the archive data of a PRIMEQUEST chassis. Alternatively the Archive Now button if the online data of the PRIMEQUEST chassis is displayed, or the Export Archive button if archive data is displayed. o o When the online data of the PRIMEQUEST chassis is displayed, you can use Archive Now to create an archive file for the PRIMEQUEST chassis. Clicking Archive Now starts the archiving. You can follow the archiving progress via the Archive Manager. For further information see the "ServerView Archive Manager" user guide. If the archive data of the PRIMEQUEST chassis is displayed, you can use Export Archive to export the current archive data into a new browser window. You can then save the data from the browser window as you wish using the browser command Save As. Selection box after Cabinet Details Under Cabinet Details you can see the cabinet ID, cabinet type and ID number, also door or cabinet status (open or closed). This display can be opened or closed as necessary. ServerView Operations Manager 233

234 8.1 Partition List 8.1 Partition List If you select the menu item Partition List under Information/Operation, you will see on the right in the Partition List view a table listing all the Physical Partitions of a PRIMEQUEST chassis and their status. If a part of the PRIMEQUEST chassis is not used, this part is listed in the table as Free. If you select a physical partition, additional views will open in the bottom section of the window. Each section is preceded by a header showing the section name. Logical Partitions Under Logical Partitions is a table showing the virtual partitions associated with the selected physical partitions. The table shows the Name, ID, associated Physical partition and Status of the virtual partitions. This section is only opened if PRIMEQUEST 2000 series are used. Details of the Partition Under Details of the Partition <number> you will see detailed information on the selected partition. The details include the IP address, power status, boot status and operating system. Hardware components Under Hardware components is a table showing details of the hardware components of the selected partition. The table contains the following columns: Status icon ID Designation Model Name Manufacturer Serial Number ServerView Operations Manager 234

235 8.2 System Status 8.2 System Status The System Status menu offers the following menus and menu items: Hardware Components with the menu items o o o o o o o MMB SB IOB GSBP DVDB SASU PCI Box Environment with the menu items o o o Fans Temperature Voltages Power Supply The Server Status view shows a brief description of the menu items. As well as the menu items, you will see status icons, which tell you whether a component is working properly. You can get more information on a component by selecting the corresponding menu item Hardware Components Hardware Components opens the Hardware Components view, which shows you the statuses of the hardware components of a PRIMEQUEST chassis. For each server cabinet, you will see details of the type and the associated status. You can view further information on the status and number of the components MMB, SB, IOB, GSPB, DVDB, SASU and PCI Box by selecting the respective menu items. ServerView Operations Manager 235

236 8.2 System Status MMB (Management Board) The MMB view provides a table of the management boards and their statuses. The columns in the table have the following meanings: Column Status icon ID Number Designation Model Name Manufacturer Serial Number Meaning The status icon indicates the overall status of the management board Identification/product number of the management board Unit/cabinet number of the management board Designation of the management board Model name of the management board Manufacturer of the management board Serial number of the management board Table 90: Hardware details of the management boards SB (System Board) The SB view provides a table of the system boards and their details. The columns in the table have the following meanings: Column Status icon ID Number Designation Model Name Manufacturer Serial Number Meaning The status icon indicates the overall status of the system board Identification/product number of the system board Unit/cabinet number of the system board Designation of the system board Model name of the system board (e.g.: SB) Manufacturer of the system board Serial number of the system board Table 91: Hardware details of the system boards You can get more information by directly selecting a system board via the menu item SB#<number>. Under Details you will then see a table with details of the processors (CPU) and memory modules (Memory) of this system board. ServerView Operations Manager 236

237 8.2 System Status The columns in the CPU table have the following meanings: Column Status icon Number Designation Model Name Step Current Speed Status Meaning The status icon indicates the overall status of the CPU CPU (socket) number CPU designation (e.g.: SB#2-CPU#0) CPU model/family name CPU step / revision CPU speed (frequency in MHz) CPU status Table 92: Hardware details of a directly selected system board The columns in the Memory table have the following meanings: Column Status icon Number Designation Capacity Status Meaning The status icon indicates the overall status of the memory Memory module (socket) number Memory module designation (e.g. SB#2-DIMM#0A0) Memory module size (capacity in Mbytes) Memory module status Table 93: Hardware details of a memory module ServerView Operations Manager 237

238 8.2 System Status IOB (Input/Output Board) The IOB view provides a table of the IO boards and their details. The columns in the table have the following meanings: Column Status icon ID Number Designation Model Name Manufacturer Serial Number Meaning The status icon indicates the overall status of the IO board Identification/product number of the IO board Unit/cabinet number of the IO board Designation of the IO board Model name of the IO board Manufacturer of the IO board Serial number of the IO board Table 94: Hardware details of the IO boards GSPB (Giga LAN SAS and PCI Box connector Board) The GSPB view provides details of the Giga LAN SAS and PCI box connector board. The columns in the table have the following meanings: Column Status icon ID Number Designation Model Name Manufacturer Serial Number Meaning The status icon indicates the overall status of the GSPB Identification/product number of the GSPB Unit/cabinet number of the GSPB Designation of the GSPB Model name of the GSPB Manufacturer of the GSPB Serial number of the GSPB Table 95: Hardware details of the GSPB DVDB (DVD Board) The DVDB view provides a table of the DVD boards and their details. The columns in the table have the following meanings: ServerView Operations Manager 238

239 8.2 System Status Column Status icon ID Number Designation Model Name Manufacturer Serial Number Meaning The status icon indicates the overall status of the DVDB Identification/product number of the DVDB Unit/cabinet number of the DVDB Designation of the DVDB Model name of the DVDB Manufacturer of the DVDB Serial number of the DVDB Table 96: Hardware details of the DVDB SASU (Serial Attached SCSI Units) The SASU view provides a table of the serial-attached SCSI units and their details. The columns in the table have the following meanings: Column Status icon ID Number Designation Model Name Manufacturer Serial Number Meaning The status icon indicates the overall status of the SASU Identification/product number of the SASU Unit/cabinet number of the SASU Designation of the SASU Model name of the SASU Manufacturer of the SASU Serial number of the SASU Table 97: Hardware details of the SASU ServerView Operations Manager 239

240 8.2 System Status PCI Box (Peripheral Component Interconnect) The PCI Box view provides a table of the PCI boxes and their details. The columns in the table have the following meanings: Column Status icon ID Number Designation Model Name Manufacturer Serial Number Meaning The status icon indicates the overall status Identification/product number of the PCI box Unit/cabinet number of the PCI box Designation of the PCI box Model name of the PCI box Manufacturer of the PCI box Serial number of the PCI box Table 98: Hardware details of the PCI box ServerView Operations Manager 240

241 8.2 System Status Environment The menu item Environment provides a summary overview of the fans, temperature, and voltages sensors. More detailed information is available via the respective menu items Fans, Temperature and Voltages Fans Fans switches to the PRIMEQUEST Server Fans view, which shows all fans of a PRIMEQUEST chassis in a diagram of the PRIMEQUEST chassis as well as in a table. The fans are indicated by the fan icon in the diagram and in the table. The fan icon tells you the following: The position of the fan in the cabinet, as indicated by the position of the fan icon. The status of the fan, as indicated by the color of the fan icon the table and diagram: Color Green Yellow Red Gray Meaning OK Warning Failed Cannot be determined Table 99: Status color of the fan You can select individual fans both in the diagram and in the table via the fan icon. The selected fan or the corresponding table entry then has a blue background. Redundant fans are indicated by directly overlapping fan control symbols. If the two control symbols are both displayed in green, the fans are redundant. After you replace a fan, you must recalibrate the fan so that the comparative values for the aging process refer to the new fan. If you have installed the ServerView agent as of V3.0 for Windows on the server, you will find a tool for this under Start [All ]Programs Fujitsu ServerView Suite Agents Maintenance Tools. ServerView Operations Manager 241

242 8.2 System Status Temperature Temperature switches to the Temperature view, which lists all temperature sensors of a PRIMEQUEST chassis in a table. The table includes the following information: Status of the temperature sensor, indicated by a status icon Purpose of the temperature sensor Current temperature Threshold values of the temperature sensor The color of the temperature sensor icon in the first column shows the status of the temperature sensor: Symbol Meaning OK Critical Warning Table 100: Status icon of the temperature sensor ServerView Operations Manager 242

243 8.2 System Status Voltages Figure 64: Voltages view Voltages takes you to the Voltages view, with a table containing information on all voltage sensors of this server. This information includes the voltage thresholds (minimum, maximum), the nominal value, the present value of the voltage, and the voltage status. If the voltage is sufficient, the status ok is displayed. If the voltage is too low or too high, the status warning is displayed. ServerView Operations Manager 243

244 8.2 System Status Power Supply Power Supply gives you information on the power supply of the PRIMEQUEST chassis. Figure 65: Power Supply view The power supply units are indicated in a diagram of the PRIMEQUEST chassis by a square. The square tells you the following: The position of a power supply unit in the housing, as indicated by the position of the square in the diagram. The status of the power supply unit, as indicated by the color of the square: Color Green Red Gray Meaning Power supply unit working okay Power supply unit failed Agent not responding Table 101: Status color of the power supply unit ServerView Operations Manager 244

245 8.2 System Status The Overall Power Status indicator shows the overall status of the power supply in the PRIMEQUEST chassis. The color of the square means: Color Green Red Yellow Meaning Power okay Power interrupted Problems with the power supply Table 102: Status color of the overall power supply The Mains Supply Status indicator shows the status of the mains power supply via the following icons: Icon Meaning PRIMEQUEST chassis working okay Fault in PRIMEQUEST chassis Table 103: Status icon of the mains power supply The Power Supply Information table shows the most important data on the power supply units. The UPS Information table contains information on the power supply. It only appears if the UPS (Uninterruptible Power Supply) devices are configured accordingly. In the Manager column of the UPS Information table, you can start the UPS Manager via the entry Start UPS Manager. The Address column shows the IP address of the UPS agent. This is the IP address of the UPS agent as specified during configuration of the UPSes via the RemoteView management blade. For more information on the Power Supply view see "Power Supply" on page 169. ServerView Operations Manager 245

246 8.3 System 8.3 System System offers the menu item System Information. The following information is displayed for PRIMEQUEST servers: the symbolic name of the server a description of the server the contact person and the location Enterprise: The vendor's unique identification of the network management subsystem Below these details you will see the Network Routing Table with the following columns: Interface Destination Next Hop Route Type Route Protocol Route Mask 8.4 Maintenance Maintenance offers you the following menu items: Server Properties, via which you can view and configure the ServerView settings Server Address, Network/Snmp, Local Note, Login and Remote Service Board. For more information see "Server Properties" on page 196. Management Configuration, via which you can start the Management Configuration Tool in a new window. The menu items under Maintenance are not activated if the archive data of the PRIMEQUEST chassis is displayed. ServerView Operations Manager 246

247 9 Querying storage subsystem data ServerView Operations Manager allows you to query further information about a storage subsystem. Depending on the model, you can request information about the storage subsystem directly via ServerView Operations Manager or start the web interface of the storage subsystem. For the following ETERNUS DX/AF storage subsystems you receive further information in the SV - Storage window of ServerView Operations Manager: Models ETERNUS DX60-S2/DX80-S2/DX90-S2 ETERNUS DX410-S2/DX440-S2/DX8700-S2 ETERNUS DX60-S3, DX100-S3, DX200-S3 ETERNUS DX60-S4, DX100-S4, DX200-S4, AF250 ETERNUS DX500-S3, DX600-S3, DX8700-S3, AF650 ETERNUS DX500-S4, DX600-S4, AF250-S2, AF650-S2 Table 104: Models of storage subsystems What information you can call up and how is described in this chapter. For the following storage subsystems you receive further information via the web interface of the storage subsystem: NetApp ETERNUS CS800 You start the web interface by clicking the relevant storage subsystem in the server list. Requesting information via ServerView Operations Manager For storage systems of types ETERNUS DX/AF, you can request information directly via ServerView Operations Manager. You do this by clicking the relevant storage subsystem in the server list in the ServerList window. This opens the SV - Storage window for the relevant storage subsystem. ServerView Operations Manager 247

248 Figure 66: SV - Storage The SV - Storage window will only open if ServerView Operations Manager recognizes the storage system as such. This requires the following: ServerView Storage Manager (StorMan) must be installed on the same management station as ServerView Operations Manager. The ServerView Storage Manager (StorMan) service StorMan Service (Windows) or storman (Linux) must be started. An SMI-S provider must be enabled on the ETERNUS DX/AF storage system (SMI-S - Storage Management Initiative Specification). The storage subsystem must be appropriately configured. o With the ETERNUS DX/AF models, the configuration occurs automatically when the object is added to the server list (see also "Defining and adding objects" on page 134). The ETERNUS DX/AF SMI-S functions require a valid user/password combination. This combination must be stored in the user/password list before an ETERNUS DX/AF storage subsystem is added to the ServerView server list (see "Creating a user/password list" on page 273). If there are problems with the configuration, you should execute the following ServerView Storage Manager (StorMan) configuration command: storcfg cimom -add -ip <IP address of the storage system> -cimuser <user> - cimpwd <password> ServerView Operations Manager 248

249 9.1 Configuration If the user/password changes, you must execute the following StorMan configuration command: storcfg cimom -mod -ip <ip-address of the storage system> -newuser <user> - newpwd <password> If the user/password changes, you must execute the following StorMan configuration command: storcfg cimom -mod -ip <IP address of the server with the installed SMI-S provider> -newuser <user> -newpwd <password> Additional documentation For more information on StorMan, please see the ServerView Storage Manager documentation or the supplied Readme file. Under View in the left-hand section of the window are menus which you can use to query further information. For an overview of the menus, see "Menus in the SV Storage window" on page 87. The different views are described in the following sections. Some fields in the various views may be empty. In these cases, the information that you can configure via the ServerView Storage Manager (StorMan) CLI is missing. For more information on configuring, see the ServerView Storage Manager (StorMan) documentation. With a storage subsystem you can only access the current data of the system (Online Data under Displayed Data). 9.1 Configuration The Configuration menu offers the commands Status Overview and System Information: Status Overview: Information on the storage subsystem (e.g. system name, manufacturer, model) as well as its status (status icon, detailed status information). System Information: Information on the storage subsystem, e.g. model, product, version, contact, location. 9.2 RAID Controller The RAID Controller menu offers the Overview and Port List commands for each RAID controller. The names of the RAID controllers are displayed as they are provided by ServerView Storage Manager (StorMan) (here: A and B). They are displayed in the same order in which the information arrived from ServerView Storage Manager (StorMan) (here: B before A). ServerView Operations Manager 249

250 9.3 Enclosures Overview: General information on the relevant RAID controller Port List: Information on the ports of the relevant RAID controller The Port type column in the right of the window shows the type of the storage subsystem connection. Possible values are: o o Fibre Channel iscsi 9.3 Enclosures The Enclosures menu offers the commands Overview, Physical Disk and Environmental for each storage subsystem. The names of the storage subsystems are displayed as they are provided by ServerView Storage Manager (StorMan). They are displayed in the same order in which the information arrived from ServerView Storage Manager (StorMan). It is recommended that you give the servers more descriptive system names via ServerView Storage Manager (StorMan) CLI for easier identification. For more information on configuring the server names, see the ServerView Storage Manager (StorMan) documentation. Overview: General information on the selected storage subsystem Physical Disk: Information on the physical hard disks Environmental: Information on the power supply and fans etc. 9.4 Storage Pools The Storage Pools menu offers the commands Overview, Storage Volumes and Host Mapping for each storage subsystem: Overview: Information on the storage pools Storage Volumes: Displays the storage volumes Host Mapping: Assignment of the managed servers to the storage volumes. It is recommended that you give the servers more descriptive system names via ServerView Storage Manager (StorMan) CLI for easier identification. For more information on configuring the server names, see the ServerView Storage Manager (StorMan) documentation. 9.5 Storage GUI The Storage GUI link starts the web interface of the relevant storage subsystem. ServerView Operations Manager 250

251 10 Querying BMC/iRMC data If you click a BMC/iRMC in the server list, the ServerView [IP address] window opens. Figure 67: Remote Management view This window shows the Remote Management view, which contains current data on the BMC/iRMC. For further information see "Remote Management" on page 203. ServerView Operations Manager 251

252 11 Power Monitor You can manage and display measurement data on power consumption for both individual and multiple servers from a central management station. This is done using the Power Monitor component of the Operations Manager. The measurement data is recorded by the ServerView Agents on the managed servers. This requires that on the managed servers the ServerView Agents V or later for Windows or Linux are installed, the ServerView Agents are configured appropriately and allow power monitoring. The agents are configured via the ServerView Configuration Manager, which you can call up in several ways, including directly from ServerView via Administration Server Configuration (see "Configuring servers remotely" on page 269). The series of measurements can be displayed on the screen for evaluation in a table or, illustratively, in a graph. Using various parameters, you can adjust the output in the table or graph to suit your needs, e.g.: Display the power consumption over a certain period for one or more servers (e.g. an hour, a week, a year) Display different kinds of consumption values (e.g. current and average) of a server in a multiple-curve graph Display the consumption values of multiple servers in a multiple-curve graph The measurement data is stored on the managed servers and is available for up to a year, after which time it is overwritten. This means that you can display at most the measurement data for the last 12 months. Power monitoring is currently available for servers and server blades. ServerView Operations Manager 252

253 11.1 Starting the Power Monitor 11.1 Starting the Power Monitor You start the Power Monitor by selecting Monitoring Power Monitor in the start window of the Operations Manager or from the menu bar. Figure 68: Power Monitor start window Immediately after you start the Power Monitor, the values in the Current/Total power (Watt) column are set to 0.0/0.0, as the current power measurements first have to be retrieved. During this time, another window opens to keep you informed of the retrieval progress. Once the data is retrieved, the values in the Current/Total power (Watt) column are updated. The file tree in the left pane of the window shows all servers and server groups that support power monitoring according to the ServerView server list. You use this tree to select the managed servers and server blades for which you want to view the measurement data. You can also select blade servers and groups. If you select a group, it must not contain any subgroups. In this case an appropriate error message will be displayed. ServerView Operations Manager 253

254 11.1 Starting the Power Monitor The icons in the file tree indicate the server type and status. The server supports power monitoring. The server blade supports power monitoring. The blade server supports power monitoring. The ESX Server supports power monitoring. The Hyper-V Server supports power monitoring. The Citrix XenServer server / Xen server supports power monitoring. The KVM server supports power monitoring. Table 105: Icons for the server type and status The right pane of the start page contains two tabs: Server tab The Server tab provides general information on the servers or server blades selected in the file tree. Data tab The Data tab provides an overview of the measured values for one or more servers/server blades in the form of a table and/or a graph. The Power Monitor offers the following buttons: Refresh serverlist button The Refresh serverlist button refreshes the file tree in the left pane of the window. Refresh data button The Refresh data button refreshes the display in the right pane of the window (only on the Data tab). ServerView Operations Manager 254

255 11.2 Power Monitor - Server tab 11.2 Power Monitor - Server tab The Server tab gives you general information on the servers or server blades selected in the file tree. Figure 69: Power Monitor - Server tab The following information about the selected servers or server blades is provided: Name Server name Network IP address Model Server model, if this information is available System Operating system, if this information is available Current/Total power The current and maximum power consumption in watts, if this information is available. The values overlie a bar chart, which shows the current value as a proportion of the maximum consumption. Each entry is also preceded by an icon: ServerView Operations Manager 255

256 11.2 Power Monitor - Server tab Icon in the first column Indicates the server type and status. The server allows power monitoring. The server blade allows power monitoring. The ESX Server allows power monitoring. The Hyper-V Server allows power monitoring. The Citrix XenServer server / Xen server allows power monitoring The KVM server allows power monitoring. Table 106: Icons for the server type and status In the columns (except for Current/Total power) you can filter the display of the Server tab via an icon: Filter icon An active filter is indicated by a blue filter icon. Activating the filters Clicking the filter icon in the relevant column opens a dialog box. Figure 70: Example: Filtering for Column System The standard filter selection options are displayed. In the standard filter (Standard), all selection elements are selected via checkboxes. In the customized filter (Custom), you select either via direct input (e.g. Windows Server 2008) or using the asterisk or question mark as a wildcard. ServerView Operations Manager 256

257 11.2 Power Monitor - Server tab Wildcards: * for any characters in any number of positions, e.g. Win*? for any character in one exact position, e.g. Windows Server 200? Make your selection and then confirm it with OK. Depending on what you have selected, only the filtered servers or server blades will then be shown on the Server tab. The filtering does not affect the server selection in the file tree. More than one column can be filtered. In the following figure the columns Model and System are filtered. Figure 71: Power Monitor - example of multiple filters active If you want to reset all filters in one go, click the filter icon of any column. In the dialog box which opens, click Reset All. The following warning message appears: Figure 72: Power Monitor - warning regarding resetting the filters Confirm that you want to reset the filters with OK. ServerView Operations Manager 257

258 11.3 Power Monitor - Data tab 11.3 Power Monitor - Data tab The Data tab provides an overview of the power consumption of the servers and server blades listed on the Server tab. You can select additional servers or server blades later. To do this, hold down [Ctrl] and click the ones you want in the file tree. Displaying more than eight servers in the graph is confusing and therefore of little use. Therefore if more than eight servers are selected, a warning message appears below Settings. The warning disappears when the selection is reduced to less than eight servers. The power consumption can be displayed both in a table and, illustratively, in a graph. For evaluating and displaying the series of measurements, the Data tab offers various parameters via which you can control the display. Figure 73: Power Monitor - Data tab The above example shows the power consumption for the server RX200S52 both as a graph and in table form. The Data tab is divided into three sections: The Settings bar allows you to make various settings to adjust the output in the bottom section of the tab to your needs. ServerView Operations Manager 258

259 11.3 Power Monitor - Data tab chart table Default value: both Via chart and table you can select whether to display the measurement data on power consumption in a graph and/or in a table. For the selected servers for which there is no measurement data available, error messages are shown below Settings. You can remove (-) or display (+) these messages via messages. A lack of measurement data can be caused by the following: o o o No ServerView Agents of V or later are installed on the managed server. Power monitoring is not activated on the managed server (this is done via the ServerView Configuration Manager). The ServerView Agents have been reinstalled on the managed server, causing existing measurements to be deleted. An update installation would avoid these values being overwritten. There are also three pull-down menus via which you can control the output of the measurement data. On the left pull-down menu you specify the time interval for which the power consumption is to be displayed in the graph. You can choose from the following: 1 hour Default value The measured values from the last hour (60 values). Because a measurement is produced every minute, this means that all measurements from the last hour are displayed. 12 hours The measured values from the last 12 hours. One value for every five minutes is displayed (every 5th value, 144 values in total). 24 hours The measured values from the last 24 hours. One value for every 10 minutes is displayed (every 10th value, 144 values in total) 1 week The measured values from the last week. One value for every hour is displayed (every 60th value, 168 values in total). 1 month The measured values from the last month. One value for every four hours (approx.) is displayed (every 240th value, 180 values in total). ServerView Operations Manager 259

260 11.3 Power Monitor - Data tab 6 months The measured values from the last six months. Approximately one value for every day is displayed (every 1440th value, 180 values in total). 12 months The measured values from the last 12 months. One value for every two days is displayed (every 2880th value, 180 values in total). On the middle pull-down menu you select the values you want to display in the graph. You can choose from the following: current Default value Current values for the selected interval. Minimum Minimum value for the selected interval. Maximum Maximum value for the selected interval. Average Average value over the selected interval. All All values On the right pull-down menu you specify the unit for the electrical power. You can choose from the following: Watt Default value Unit of electrical power. BTU/h British Thermal Unit/hour Unit of electrical power BTU/h = 293 W Display of measured values in a graph Depending on the configuration in the Settings bar, the measured values are displayed in a graph in this section of the window. If you have selected more than one server, the power consumption of each individual server is shown in the graph. If there is more than one curve, the curves are distinguished by different colors, with a key to the right of the diagram. Please note that displaying too many servers will make the graph confusing and therefore not very helpful. ServerView Operations Manager 260

261 11.3 Power Monitor - Data tab Figure 74: Power Monitor - tooltip in graph If you move the mouse pointer over the graph, a tooltip appears containing the server name, date, and value in watts or BTU/h. You can change the display size of the graph. If you click in the graph and then, holding down the left mouse button, move the mouse to the right or left, this expands or compresses the depicted section of the graph. This can be useful with particularly elongated or compressed curves. If you then click the right mouse button, the diagram returns to its original view. The changed section is indicated by a gray oblong. Figure 75: Power Monitor - changed section in the graph Display of measured values in a table In the bottom section of the window the measured values for the selected interval are displayed in a table. The table varies, depending on whether you have selected one server or several. If you have only selected one, all the measured values for the selected interval are listed. If you have selected more than one server, there will only be one entry per server, each with the latest measurement. For further information see "One server or server blade on the Data tab" on page 263 and "Multiple servers on the Data tab" on page 264. ServerView Operations Manager 261

262 11.3 Power Monitor - Data tab The first column of the table, the Status (PCS) column (PCS - Power Control Status) indicates the power mode of a server. The following entries may appear: disabled The BMC (Baseboard Management Controller)/iRMC (integrated Remote Management Controller) checks the operating system and not the power consumption. best-performance The BMC/iRMC controls the server such that it has the best performance. In this case the power consumption can increase. minimum-power The BMC/iRMC controls the server such that it consumes as little power as possible. In this case the performance is not always ideal. scheduled The BMC/iRMC controls the power consumption according to user-defined timing (via the ServerView Configuration Manager). unknown Unknown PCS. The following information is also displayed: Date and time when the measurement was recorded Current value in watts Minimum value in watts Maximum value in watts Average value in watts Current value in BTU/h Current value/maximum possible value in watts ServerView Operations Manager 262

263 11.3 Power Monitor - Data tab One server or server blade on the Data tab Figure 76: Power Monitor - Data tab (one server) If you have only selected one server or server blade, the table will show all measured values for the selected interval for that server or server blade. ServerView Operations Manager 263

264 11.3 Power Monitor - Data tab Multiple servers on the Data tab You can select multiple servers or server blades for which you want to display measured values on their power consumption on the Data tab. The display is different from the display for an individual server. Figure 77: Power Monitor - Data tab (multiple servers) The table shows the latest measured value for each server. It also contains the Summation line, which totals the latest power consumption values for all selected servers. The values for a server over the complete interval are shown in the graph. The display in the graph can become very confusing if you select too many servers or too many values (current, average, maximum values, etc.). You can optimize the display by: only selecting a few servers or server blades from the server list, only selecting one series of measurements (current, minimum, maximum, average), only selecting a few servers in the table. You do this by clicking the relevant box in the first line of the table. Current power consumption of all servers in the graph You can display the current power consumption of all selected servers by clicking the Summation line in the table. ServerView Operations Manager 264

265 11.3 Power Monitor - Data tab Figure 78: Total of current values in the graph The timestamps of the available series of measurements are rounded off, e.g.: With an interval of one hour there are 60 measured values. The timestamps for these values are rounded up to the next full minute and then the values from the same minutes are added together. With an interval of one week there are over 168 measured values. The timestamps for these values are rounded up to the next full hour and then the values from the same hours are added together. If you have only selected one server, the graph will only show the power consumption of this server. ServerView Operations Manager 265

266 12 Power management ServerView Operations Manager offers a remote power management function. This means that you can switch individual servers and server groups on and off from the central management station. Remote power management is possible on the following PRIMERGY servers: servers with a Baseboard Management Controller (BMC) server blades VMware servers Citrix XenServer servers / Xen servers KVM servers Hyper-V servers You start the power management via the context menu in the server list - provided that ServerView Operations Manager finds a valid user/password combination in the user/password list (see "Creating a user/password list" on page 273). The remote power management function can be started for selected servers or groups. With a selected group, power management is possible for all servers in the group but not for a subgroup. 1. Select the server(s) or server group. 2. By clicking Power Management in the context menu, you start the power management for the selected server(s). ServerView Operations Manager 266

267 Figure 79: Power Management window The following commands are available for power management: Power On Switches the server(s) on. Immediate Power Off Switches the server off, regardless of the operating system status. Immediate Reset Completely restarts the server, regardless of the operating system status (cold start). Graceful Power Off (Shutdown) Graceful shutdown and power off. The ServerView agent on the managed server prompts the operating system to shut down the server correctly, and then switches it off. Graceful Reset (Reboot) Graceful shutdown and reboot. The ServerView agent on the managed server prompts the operating system to shut down the server correctly, and then restarts it. Soft Shutdown Graceful shutdown. The ServerView agent on the managed server prompts the operating system to shut down the server correctly. ServerView Operations Manager 267

268 Suspend Standby mode. Only Power On is possible. Citrix XenServer servers / Xen servers, KVM servers, and VMware servers only. Power Cycle Switches the server off completely and, after a period defined on the server, switches it on again. Only servers with BMC. Resume If the server is in standby mode (Suspend), this mode is cancelled. Citrix XenServer servers / Xen servers and KVM servers only. 3. Click the desired command and confirm with Apply. A confirmation window opens. 4. If you confirm the request with OK, the command is started. The display in the window now documents whether or not the commands were forwarded successfully to the relevant server(s). Figure 80: Power Management Result window Depending on the task and the result, different headings can be displayed, which show you the progress of the task distribution. In the event of an error, under the heading Attach failed/command failed you will see the name of the affected server, an error message, a brief description of the error, and the application which returned the error message. 5. The result of the power management action can then be seen in the server list. ServerView Operations Manager 268

269 13 Configuring servers remotely You can configure managed servers remotely via the ServerView Configuration Manager. This is integrated in ServerView Operations Manager and can be started via Administration Server Configuration. Configuring the watchdog under VMware vsphere Hypervisor (ESXi) is only possible via irmc and not via the ServerView Configuration Manager. 1. From the Operations Manager start page select the following entry: Administration Server Configuration This opens the following window: Figure 81: Server Configuration window - Server list (1) tab 2. In the hierarchy tree of the Server list tab, select the server to be configured. If the server to be configured has the certificates of all trusted central management stations installed, the Server Configuration Manager gets the current user s privileges from the Central Authentication Service (CAS) and no longer needs to authenticate via user login prompt as in previous versions. If the selected server does not have a certificate of the current central management station, single sign-on cannot be used. If the agents are configured such that SET ServerView Operations Manager 269

270 operations are only allowed after user ID/password authentication, the following window opens. Figure 82: User authentication - Login window 3. Enter the user authentication and click OK. The following window opens: Figure 83: Server Configuration window - Server list (2) tab 4. In the right-hand section of the window, specify the details of the selected server and confirm by clicking Go... The following window opens with the Configuration tab activated: ServerView Operations Manager 270

271 Figure 84: Server Configuration window - Configuration tab 5. In the navigation area of the Configuration tab, click the required function. The associated setting options are then offered in the right-hand section of the window. 6. Configure the settings you require and save them with Save Page or Save all. Activate the configured settings for each server either separately for each function with Save Page or, when you have completed the entire configuration, with Save all. When you have finished configuring a server, you can select further servers for configuration in the Server list tab. ServerView Operations Manager 271

272 14 Starting Advanced Video Redirection You can start Advanced Video Redirection (AVR) for a server directly via the server list. This function is available for servers whose irmc supports AVR and single sign-on. You start AVR as follows: 1. Select the relevant server in the server list. 2. Select Start Video Redirection from the context menu. If the server supports AVR and single sign-on, AVR will be started and the AVR window will open. 3. Once AVR is started, you will find yourself in read-only mode. Confirm the following question with OK to gain full control of the server. You can also start AVR for the irmc via the Java applet. To do this you must select the option Java Web-Start before you start AVR (default): 1. On the menu bar select ServerList Settings. The Settings window opens. 2. Select the option Java Web-Start under AVR-Settings. Requirements for AVR Advanced Console Redirection requires the following: The irmc must support AVR. The irmc must support single sign-on. You need a valid license key and a valid certificate to use AVR. You need a valid user ID. If force https is activated, you must disable the Internet Explorer option Do not save encrypted pages to disk: 1. In Internet Explorer, open the Tools menu and select Internet Options. 2. In the Internet Options window, select the Advanced tab. 3. Under Settings scroll down to Security and select the option Do not save encrypted pages to disk. 4. Click OK. More information For more information on AVR, see the "ServerView Suite, irmc S2/S3 - integrated Remote Management Controller", "irmc S4 - Web Interface" or "irmc S5 - Web Interface" user guide. ServerView Operations Manager 272

273 15 Creating a user/password list In some cases ServerView Operations Manager requires a valid user ID in order to authenticate itself when retrieving information or performing actions on a managed server. User IDs are required, for example, To add virtual servers (VMware servers, Citrix XenServer servers / Xen servers, KVM servers, Hyper-V servers) to the server list. The server browser will only recognize a virtual system if ServerView Operations Manager can authenticate itself with a valid user ID. If you want to test the connection to a VMware ESX server, a Citrix XenServer/Xen server, a KVM server or a Hyper-V server (Test Connectivity). To add a ETERNUS DX/AF storage subsystem to the server list. ETERNUS DX/AF systems will only be recognized correctly if ServerView Operations Manager can authenticate itself with a valid user ID (CIM user, CIM password). To add a BMC to the server list. The server browser will only recognize a BMC if ServerView Operations Manager can authenticate itself with a valid user ID. For power management tasks to be executed on the following servers: o o o o o VMware servers Citrix XenServer servers / Xen servers KVM servers Hyper-V servers Servers with BMC to set performance thresholds (Threshold Manager). For these authentication cases, ServerView Operations Manager allows you to store user IDs in a user/password list with the password encrypted. If necessary, ServerView Operations Manager searches this list for a valid user ID. ServerView Operations Manager works through the list in sequence. For this reason the list should only contain as many entries as necessary. You create the user/password list via Users/Passwords in the Administration menu. 1. In the Administration menu, select Users/Passwords. This opens the User Password window. ServerView Operations Manager 273

274 Figure 85: Creating a user/password list 2. Under User name and Password, enter the user name and corresponding password respectively and confirm the password under Confirm Password. Please note that the user requires administrator rights to execute power management actions. For Hyper-V servers, the user always requires administrator rights. 3. Under Node Type, select the server type for which the user name is to be valid. 4. Under Set Name, enter the name of the credential set to be used for the node type. SNMPv3 requires either one (authentication only) or two credentials sets (authentication and privacy - encryption), as there may be separate passwords for authentication and privacy. 5. Under Comment you can enter a comment, which will also be saved. 6. Click Apply if you simply want to confirm your input, or OK if you want to confirm your input and close the window. Cancel closes the window without saving your changes. To delete a user ID, mark it by selecting the checkbox and then click Delete. ServerView Operations Manager 274

275 16 ServerView Status gadget for Windows 7 If Windows 7 is installed on a standard PC, a ServerView status gadget is offered. This gadget allows you to display the number of servers in the different status situations. You can start ServerView Operations Manager via a link. Installation You can install the gadget in one of the following ways: Double-click the file StatusGadget.gadget. This file is located on the ServerView Suite DVD in the following directory: SVSSoftware/Software/ServerView/Windows/ServerView_S2/StatusGadget Via the ServerView Suite DVD. Execute the file StatusGadget.gadget. This file is located under ServerView Suite Operations Manager. If the status gadget is already installed, you will be asked whether you want to replace the current version. Configuration After installation the following dialog is displayed: Figure 86: ServerView status gadget - start dialog For connecting to a ServerView Operations Manager installation (on a central management station) you need to enter the corresponding URL. By clicking the tool icon (see figure above) you start the SV Status Gadget dialog to enter the URL. ServerView Operations Manager 275

276 Figure 87: SV Status Gadget dialog After this, the name of the central management station is displayed as a link in the status gadget, see figure below. Via this link you can start ServerView Operations Manager, which is located on this central management station. Figure 88: ServerView status gadget The icons identifies the status of the servers. The meaning of the icons is described in "Icons in the ServerList window" on page 90. Opening the status gadget If you have closed the gadget, you can reopen it as follows: 1. Right-click anywhere on the desktop. 2. Select Gadget. 3. On the displayed gadget overview, select the ServerView status gadget. 4. Select Add from the context menu. After reopening the gadget, you will need to configure it again, see "Configuration" on page 275. ServerView Operations Manager 276

277 Opening multiple status gadgets You can open more than one status gadget. This allows you to display the number of servers in the different status situations from different central management stations. Uninstalling the status gadget To uninstall the gadget proceed as follows: 1. Right-click anywhere on the desktop. 2. Select Gadget. 3. On the displayed gadget overview, select the ServerView status gadget. 4. Select Uninstall from the context menu. ServerView Operations Manager 277

278 17 FUJITSU Software ServerView Status app for Windows 8 The ServerView Status app allows you to display the status of your managed servers at a glance on a desktop running Windows 8 or to be notified of warnings caused by one of your managed servers. Simply download the FUJITSU Software ServerView Status app onto your desktop. The ServerView Status app presents all server status information in the same way as the Operations Manager installed on the central management station (CMS). In addition, at the touch of a button on your desktop, you can open a connection to the web interface of the CMS in your data center for further analysis. The following table lists the displayed icons and the associated server status information. OK: All components are okay. Warning: The status of one or more components has deteriorated. Critical: One or more components have an error. Standard SNMP agent is okay. The server does not react, the management controller responds via the secondary channel. Not manageable. The ServerView agent or CIM provider is not responding, but the server can be reached via TCP/IP. Unknown! The server cannot be reached over the network. A different TCP/IP device (e.g. a printer) has responded. Virtual machine without ServerView Agents: Powered On: The server is on. Virtual machine without ServerView Agents: Powered Off: The server is off. Virtual machine without ServerView Agents: Suspended/Paused: The server is in standby mode or in pause mode. Table 107: Server status icons of the ServerView Status app ServerView Operations Manager 278

279 18 Communication paths The components of the ServerView Suite communicate with each other on different paths. A detailed description of the communication paths, the protocols and the standard ports used is provided in the White Paper Secure PRIMERGY Server Management. This White Paper can be found at under: x86 Servers Software ServerView Suite Security and User Management ServerView Operations Manager 279

280 19.1 On Windows systems 19 Collecting diagnostics data After Operations Manager is installed on the central management station, a script is available to collect various diagnostics data On Windows systems After Operations Manager is installed on the central management station, the CmsCollect.bat script is available in the directory Programs Fujitsu ServerView Suite. This script allows you to collect various diagnostics data (e.g. information about ServerView Services, log files, to the web server). For diagnostic purposes you can send this file to your Fujitsu Customer Service Desk. To collect the data, proceed as follows: 1. Switch to the directory Programs Fujitsu ServerView Suite. 2. To start the collection double-click the file CmsCollect.bat. The result of the collection is stored in the zip file cmscollect.zip in the directory...\serverview Suite\svom\data On Linux systems After Operations Manager is installed on the central management station, the cmscollect.sh script is available in the directory /opt/fujitsu/serverviewsuite/svom/serverview/tools. This script allows you to collect various diagnostics data (e.g. information about ServerView Services, log files). For diagnostic purposes you can send this file to your Fujitsu Customer Service Desk. To collect the data, proceed as follows: 1. Switch to the directory /opt/fujitsu/serverviewsuite/svom/serverview/tools. 2. To start the collection execute the following command: sh cmscollect.sh The result of the collection is stored in the file cmscollect.tar.gz in the directory /var/log/fujitsu/serverviewsuite. ServerView Operations Manager 280

281 20.1 WMI architecture 20 WMI Windows Management Instrumentation (WMI) is an implementation of the WBEM industry initiative by Microsoft. WBEM (Web-Based Enterprise Management) and its underlying data model CIM (Common Information Model) are subject to a strict standardization process under the leadership of the DMTF (Distributed Management Taskforce). WBEM standardizes the description and use of managed resources (managed objects) and offers a wide range of tools for accessing, configuring, administering and monitoring these resources in a corporate network. Support for the WMI standard in ServerView permits WMI-based administration and monitoring of servers. This chapter deals with the following topics: Overview of the concept behind WMI WMI support in ServerView including descriptions of the classes provided in ServerView Overview of WMI scripting Example of WMI CIM Studio This chapter is aimed at Administrators who wish to gain an overview of WMI in the ServerView environment. Administrators who want to manage servers using administrative WMI scripts. The latter group require expertise in a script language, such as VBScript or JScript and indepth knowledge of the WMI and CIM models which are beyond the scope of the introduction offered in this chapter WMI architecture The WMI architecture comprises three basic segments: WMI users WMI infrastructure Managed objects The following figure illustrates the way in which the individual components of WMI, which are described below, interact. ServerView Operations Manager 281

282 20.1 WMI architecture Figure 89: WMI architecture WMI users A WMI user can be a script or a management application, for instance, which processes and presents the management information provided by the WMI infrastructure. ServerView Operations Manager 282

283 20.1 WMI architecture WMI infrastructure The WMI infrastructure forms the link between the WMI users and the managed objects and comprises the following components: WMI scripting library CIM Object Manager (CIMOM), namespaces and WMI Repository WMI providers WMI scripting library The WMI scripting library contains a set of automation objects which ensure a uniform, consistent scripting model. Script languages such as Visual Basic Script use these automation objects to access the WMI scripting library (see "WMI scripting" on page 313). CIM Object Manager (CIMOM) and WMI Repository The Common Information Model (CIM) is a standardized, object-oriented data model which ensures a uniform representation of the managed resources from the point of view of server management by providing them in the form of classes and class instances (objects). The classes feature attributes, properties and methods. The attributes and properties provide information on the status and configuration of the managed object and the methods make it possible to apply actions to the managed object. The CIM Object Manager (CIMOM) coordinates and controls the object queries issued by the WMI users. To provide an overview of the available classes, CIMOM stores the class definitions and the WMI providers responsible in the WMI repository. Class definitions are stored in Managed Object Format (MOF). WMI namespace WMI organizes the classes and objects into namespaces. The namespaces CIMv2, Default Directory, Security and WMI are located below the root namespace and some of these in turn contain subordinate namespaces. For the purposes of server management using ServerView, the namespace root\cimv2 is of particular importance, as it contains the classes corresponding to the resources managed by ServerView. A WMI user can only access a given object using the namespace which contains this object. Namespaces also represent the level of granularity used for WMI security: WMI authorizations are granted on the level of namespaces. ServerView Operations Manager 283

284 20.2 WMI support in ServerView WMI providers WMI providers mediate between the managed objects and WMI. The WMI providers communicate with the managed objects over the appropriate resource-specific interfaces. To communicate with WMI, WMI providers use the COM/DCOM ((Distributed) Component Object Model) API. ServerView Agents act as WMI providers in order to provide WMI support in ServerView Managed objects A managed object is understood to be any hardware or software component which can be managed over WMI using ServerView. This can be an entire server, but can also be a single component such as a fan or file system WMI security A management application must authenticate itself before WMI permits it to access CIM data and methods. Access authorizations are checked by DCOM security (Distributed Component Object Model) and the CIMOM. WMI security is implemented on the level of namespaces. A management application which has been granted access to a namespace has full access rights to all objects in this namespace WMI support in ServerView ServerView supports the WMI standard. This means that a wide range of different information on servers can be passed to the CIMOM and forwarded to WMI users. However, not all data provided by the familiar SNMP-based solution in ServerView with its easy-to-use graphical frontend is currently passed to the CIMOM System requirements The CIMOM is included in all current versions of the Microsoft operating systems. The ServerView Agents as of version 3.0 must be installed to permit integration in the CIMOM. When they are configured appropriately, these agents make server data available to the CIMOM. See the "ServerView Agents for Linux" or "ServerView Agents for Windows" installation and user guide for information on configuring the ServerView Agents to provide WMI support. ServerView Operations Manager 284

285 20.2 WMI support in ServerView ServerView Agents as WMI providers ServerView Agents store server data in the CIMv2namespace of the CIMOM. You can request the server data from the CIMv2 namespace using the Microsoft communication methods COM/DCOM and then prepare the data graphically for output. Figure 90: ServerView Agents as WMI providers ServerView Operations Manager 285

286 20.2 WMI support in ServerView ServerView classes The classes provided by ServerView are located in the CIMv2 namespace and are indicated by the name prefix FSCSV_. All the classes supported by ServerView are of the type dynamic, i.e. each time a request is received from a WMI user or from the WMI infrastructure, the WMI provider determines the current values for the managed object. You can obtain detailed information on the individual classes, the inheritance hierarchies of the classes and on the class instances using WMI tools such as the test program for WMI (wbemtest.exe), the WMI Object Browser or the WMI CIM Studio. You will find an example for WMI Studio in section "WMI CIM Studio (example)" on page 315. WMI CIM Studio and the test program for WMI furthermore provide you with the facility of creating instances and modifying or deleting existing instances. The test program for WMI is part of your standard Windows installation. The WMI Object Browser and WMI CIM Studio are provided together with WMI-SDK. System properties All ServerView classes include a number of system properties which are automatically included in each class and class instance, even though they are not present in the class definitions in the.mof files. These properties have constant values which provide information on such things as the namespace of the class and its position in the class hierarchy of the namespace. The following table lists the system properties with descriptions. Property name CLASS DERIVATION DYNASTY GENUS NAMESPACE PATH PROPERTY_COUNT RELPATH SERVER SUPERCLASS Description Name of the class Inheritance hierarchy Topmost class of the inheritance hierarchy Number of topmost classes Namespace to which the class belongs Path of the class on the server Number of properties of the class Relative path of the class on the server Server on which the class is located Immediate parent class Table 108: System properties of the ServerView classes ServerView Operations Manager 286

287 20.2 WMI support in ServerView Description of the classes The following description of the individual ServerView classes contains the following information for each class: Overview of the parent classes and the position of the ServerView classes in the inheritance hierarchy. The name of the base class is always shown in bold. In the navigation area of CIM Studio (see "WMI CIM Studio (example)" on page 315), you navigate to the relevant ServerView class via the base class and the inheritance hierarchy. Properties defined in the class and properties which form the key. Methods defined in the class. Association with another class. The descriptions of the ServerView classes apply to Windows platforms. It is possible that individual classes or properties are not supported on other platforms. You will find a general description of the CIM and win32 classes from which ServerView classes are derived at the following Web address: ServerView Operations Manager 287

288 20.2 WMI support in ServerView FSCSV_ASR The class FSCSV_ASR defines the ASR&R settings for a server. Parent classes Properties Name Type Description SettingID string Key (inherited). Identifies an instance of FSCSV_ASR. ActionAfterAcFail uint8 Action to be taken after interruption of the power supply: 3: Restore previous state. 4: Server remains off. 5: Switch on server. ActionAfterRestartFail uint8 Action to be taken when the permitted number of restart/reboot attempts (see property RestartRetriesLeft) has been exceeded: 2: Switch off server. 3: Boot diagnostic system. 4: No diagnostic system. 5: Boot remote image disk. ErrorOffRestartDelay uint16 Delay (in realtime) before the server is switched on again after it had been switched off due to an error. PostErrorHalt uint8 Action to be taken if a POST error occurs: 2: Halt on any error. 3: Do not halt. RestartRetriesDefault uint8 Default value for the number of reboot/restart attempts on the server after it has been shut down with Power off. This value is used in order to reset the RestartRetriesLeft property to the default value after the counter has reached 0. RestartRetriesLeft uint8 Maximum number of permitted reboot/restart attempts on the server after it has been shut down with Power off. As soon as the maximum number of permitted attempts has been exceeded without success, the action specified in the property ActionAfterRestartFail is executed. Table 109: Properties of the FSCSV_ASR class ServerView Operations Manager 288

289 20.2 WMI support in ServerView Methods The class FSCSV_ASR does not inherit or define any methods. Association The class FSCSV_ASR is associated with the class CIM_UnitaryComputerSystem via the association class FSCSV_ASRSetting FSCSV_ASRSetting (association class) The association class FSCSV_ASRSetting associates the classes CIM_ UnitaryComputerSystem and FSCSV_ASR. Parent classes Properties Name Type Description Element Ref: CIM_UnitaryComputerSystem Key (inherited). References the server on which the ASR&R settings are used. Setting Ref: FSCSV_ASR Key (inherited). References the FSCSV_ASR instance whose settings apply to the server referenced by Element. Table 110: Properties of the FSCSV_ASRSetting class Methods The class FSCSV_ASRSetting does not inherit or define any methods. ServerView Operations Manager 289

290 20.2 WMI support in ServerView Association FSCSV_AssociatedCooling (association class) The association class FSCSV_AssociatedCooling associates the classes CIM_CoolingDevice and CIM_LogicalDevice. It describes the relationship between the fan and the component to be cooled. Parent classes Properties Name Type Description Antecedent Ref: CIM_CoolingDevice Key (inherited). References the fan. Dependent Ref: CIM_LogicalDevice Key (inherited). References the component to be cooled. Table 111: Properties of the FSCSV_AssociatedCooling class Methods The class FSCSV_AssociatedCooling does not inherit or define any methods. Association ServerView Operations Manager 290

291 20.2 WMI support in ServerView FSCSV_AssociatedSensor (association class) The association class FSCSV_AssociatedSensor associates the classes CIM_Sensor and CIM_ LogicalDevice. It describes the relationship between the sensor and the component to be monitored. Parent classes Properties Name Type Description Antecedent Ref: CIM_Sensor Key (inherited). References the sensor. Dependent Ref: CIM_LogicalDevice Key (inherited). References the monitored component. Table 112: Properties of the FSCSV_AssociatedSensor class Methods The class FSCSV_AssociatedSensor does not inherit or define any methods. Association ServerView Operations Manager 291

292 20.2 WMI support in ServerView FSCSV_AssociatedSupplyVoltageSensor (association class) The association class FSCSV_AssociatedSupplyVoltageSensor associates the classes FSCSV_ VoltageSensor and FSCSV_PowerSupply. It describes the relationship between the voltage sensor and the power supply to which the sensor is assigned. Parent classes Properties Name Type Description Antecedent Ref: FSCSV_VoltageSensor Key (inherited). References the sensor. Dependent Ref: FSCSV_PowerSupply Key (inherited). References the monitored power supply. Table 113: Properties of the FSCSV_AssociatedSupplyVoltageSensor class Methods The class FSCSV_AssociatedSupplyVoltageSensor does not inherit or define any methods. Association ServerView Operations Manager 292

293 20.2 WMI support in ServerView FSCSV_Chassis The class FSCSV_Chassis describes the housing for a storage extension unit. Parent classes Properties Name Type Description Day string Key (inherited). Identifies a housing for one storage extension unit (instance of FSCSV_Chassis). CreationClassName string Key (inherited). Specifies the name of the class or subclass used to create the instance. GroupNumber uint8 Group number for the storage extension unit communication bus. PowerSupplySlots uint8 Number of power supply slots in the housing (maximum number of power supplies that can be installed). Table 114: Properties of the FSCSV_Chassis class Methods The class FSCSV_Chassis does not define any methods. Association The class FSCSV_Chassis is associated with the class FSCSV_PowerOnOffInformation via the association class FSCSV_PowerOnOffStatistics. ServerView Operations Manager 293

294 20.2 WMI support in ServerView FSCSV_ComputerSystem The class FSCSV_ ComputerSystem provides information on a computer system. Parent classes Properties Name Type Description Name string Key (inherited). Identifies an instance of FSCSV_ComputerSystem. Status string Status of the system. The following values are possible: OK, Error, Degraded, Pred Fail. CabinetsConfigured uint16 Number of housings which can be configured (servers and storage extension units). The value should be at least 1 (value for the server). PostStatus string OK: The most recent/current POST phase was successful. Error: The most recent/current POST phase failed. Table 115: Properties of the FSCSV_ComputerSystem class Methods The class FSCSV_ComputerSystem does not define any methods. Association The class FSCSV_ComputerSystem is not associated with any other class via an FSCSV_... association class. ServerView Operations Manager 294

295 20.2 WMI support in ServerView FSCSV_FailReaction The class FSCSV_FailReaction specifies the action to be taken when an error situation is detected. The sequence of the actions is defined as follows, depending on the values of the properties described in the table "Properties of the FSCSV_FailReaction class" on page 295. After the error situation occurs, no action is taken for a period of WaitTime seconds. If the error situation persists, a script is called with the parameters ScriptParameters. After ScriptTime seconds have elapsed, a warning with the text specified in WarningMessage is output. After a further WarningTime seconds have elapsed, the action specified in Reaction is taken. Parent classes Properties Name Type Description SettingID string Key (inherited). Identifies an instance of FSCSV_FailReaction. WaitTime uint32 Wait time before calling the script. ScriptTime uint32 Time reserved for executing the script before a warning is issued. WarningTime uint32 Time between generating the warning and triggering the action specified in Reaction. Reaction uint16 Action to be taken after the error situation has been detected: 2: Continue processing. 3: Shutdown and switch off. Script: string Pathname of an executable program or script started after the error situation has been detected. ScriptParameters string Parameters for the script. WarningMessage string Message text to be output. Note that the message output mechanism varies between operating systems and that it is possible that the message will not be issued at all. Table 116: Properties of the FSCSV_FailReaction class ServerView Operations Manager 295

296 20.2 WMI support in ServerView Methods The class FSCSV_FailSetting does not inherit or define any methods. Association The class FSCSV_FailReaction is associated with the class CIM_ManagedSystemElement via the association class FSCSV_FailSetting FSCSV_FailSetting (association class) The association class FSCSV_FailSetting associates the classes CIM_ ManagedSystemElement and FSCSV_FailReaction. Parent classes Properties Name Type Description Element Ref: CIM_ ManagedSystemElement Key (inherited). References the system component to be monitored on which the FSCSV_FailReaction settings are used. Setting Ref: FSCSV_FailReaction Key (inherited). References the instance of FSCSV_FailReaction Table 117: Properties of the FSCSV_FailSetting class whose settings apply to the system component to be monitored. Methods The class FSCSV_FailSetting does not inherit or define any methods. ServerView Operations Manager 296

297 20.2 WMI support in ServerView Association FSCSV_Fan The class FSCSV_Fan describes the properties of a fan on a server. Parent classes Properties Name Type Description DeviceID string Key (inherited). Identifies an instance of FSCSV_Fan. Table 118: Properties of the FSCSV_Fan class Methods The class FSCSV_Fan does not define any methods. Association The class FSCSV_Fan is not associated with any other class via an FSCSV_... association class. ServerView Operations Manager 297

298 20.2 WMI support in ServerView FSCSV_FRU The class FSCSV_FRU describes a vendor-defined collection of products and physical elements in connection with an FRU (Field Replaceable Unit). FRUs are system components which can be released and removed from the system. Parent classes Properties Name Type Description FRUNumber string Key (inherited). Information on ordering FRU. IdentifyingNumber string Key (inherited). FRU ID, e.g. a software serial number or the number on a hardware chip. Vendor string Key (inherited). Name the FRU dealer. FirmwareVersion string Firmware version of a component. ManufacturingDateTime string Date and time the component was installed. Table 119: Properties of the FSCSV_FRU class Methods The class FSCSV_FRU does not inherit or define any methods. Association The class FSCSV_FRU is associated with the class CIM_PhysicalElements via the association class FSCSV_FRUPhysicalElements. ServerView Operations Manager 298

299 20.2 WMI support in ServerView FSCSV_FRUPhysicalElements (association class) The association class FSCSV_FRUPhysicalElements associates the classes CIM_ PhysicalElements and FSCSV_FRU. It specifies the physical components of the FRU (Field Replaceable Unit). Parent classes Properties Name Type Description Component Ref: CIM_PhysicalElements Key (inherited). References the physical component. FRU Ref: FSCSV_FRU Key (inherited). References the FRU. Table 120: Properties of the FSCSV_FRUPhysicalElements class Methods The class FSCSV_FRUPhysicalElements does not inherit or define any methods. Association ServerView Operations Manager 299

300 20.2 WMI support in ServerView FSCSV_ManagementController The class FSCSV_ManagementController describes a management controller. Parent classes Properties Name Type Description DeviceID string Key (inherited). Identifies the management controller. FirmwareVersion string Firmware version of the management controller. Table 121: Properties of the FSCSV_ManagementController class Methods The class FSCSV_ManagementController does not define any methods. Association The class FSCSV_ManagementController is not associated with any other class via an FSCSV_... association class. ServerView Operations Manager 300

301 20.2 WMI support in ServerView FSCSV_OperatingSchedule The class FSCSV_ OperatingSchedule describes the regular shutdown/power on settings: Power on is controlled by a realtime clock. Power off with shutdown is carried out by the operating system. Parent classes Properties Name Type Description SettingID string Key (inherited). Identifies an instance of FSCSV_OperatingSchedule. When uint16 Time (unit: number of minutes after midnight) at which the operation is to be carried out. Table 122: Properties of the FSCSV_ OperatingSchedule class Methods The class FSCSV_OperatingSchedule does not inherit or define any methods. Association The class FSCSV_OperatingSchedule is associated with the class CIM_System via the association class FSCSV_OperatingScheduleSetting. ServerView Operations Manager 301

302 20.2 WMI support in ServerView FSCSV_OperatingScheduleSetting (association class) The association class FSCSV_OperatingScheduleSetting associates the classes CIM_System and FSCSV_OperatingSchedule. Parent classes Properties Name Type Description Element Ref: CIM_System Key (inherited). References the system on which the FSCSV_ OperatingSchedule settings are used. Setting Ref: FSCSV_OperatingSchedule Key (inherited). References an instance of FSCSV_ OperatingSchedule whose values apply to the assigned system. Table 123: Properties of the FSCSV_OperatingScheduleSetting class Methods The class FSCSV_OperatingScheduleSetting does not inherit or define any methods. Association ServerView Operations Manager 302

303 20.2 WMI support in ServerView FSCSV_PowerOnOffInformation The class FSCSV_PowerOnOffInformation provides statistical information on the operating time and on power-on/power-off operations. Parent classes Properties Name Type Description Name string Key (inherited). Identifies an instance of FSCSV_PowerOnOffInformation. LastPowerOffSource uint16 Cause for the most recent power-off of the chassis: 2: Software Off 3: Power Switch 4: AC Power Failure 5: Clock or Timer 6: Fan Failure 7: Critical Temperature 8: Damage Temperature 9: Power Supply Failure 10: Watchdog Timeout 11: Remote Off 14: CPU Error 16: System Power Off 29: Keyboard Button 31: Remote Manager 243: Housing Opened Table 124: Properties of the FSCSV_PowerOnOffInformation class ServerView Operations Manager 303

304 20.2 WMI support in ServerView Name Type Description LastPowerOnSource uint16 Cause for the most recent power-on or reset of the chassis: 2: Software On 3: Power Switch 4: AC Power Failure 5: Clock or Timer 6: Fan Failure 7: Critical Temperature 8: Damage Temperature 9: Power Supply Failure 10: Watchdog Timeout 11: Remote On 12: Hardware Failure 13: Peripheral Bus Error 14: CPU Error 20: NMI 23: Hardware Reset 24: Warm Start 25: Reset Button 26: AC Power Failure 27: Management Processor Failure 31: Remote Manager 32: Reset by Remote Manager 242: Firmware Restart 243: Housing Closed PowerOnCounts uint32 Specifies how often the chassis was switched on during its lifetime. PowerOnDuration uint32 Specifies how many hours the chassis was switched on during its lifetime. PowerOffDuration uint32 Specifies how many hours the chassis was switched off during its lifetime. SystemBootResult uint8 Status of the most recent attempt to boot the Server: 2: Operating system booted successfully. 3: Diagnostic system booted successfully. 4: No boot CPU found. 5: No bootable media found. 6: Operating system failed to load. 7: Diagnostic system boot failed. 8: Hardware failure Table 124: Properties of the FSCSV_PowerOnOffInformation class ServerView Operations Manager 304

305 20.2 WMI support in ServerView Name Type Description SystemBootStatus uint8 Current server status: 2: Server switched off. 3: No boot CPU found. 4: System is in POST phase. 5: Setup has been started. 6: Operating system booted. 7: Diagnostic system booting. 8: Operating system running. 9: Diagnostic system running. 10: Operating system shutting down. 11: Diagnostic system and shutting down. 12: System is being reset. WarmStart boolean true: The system performed a warm start (reset) before the most recent boot attempt. false: The system performed a cold start (power on) before the most recent boot attempt. Table 124: Properties of the FSCSV_PowerOnOffInformation class Methods The class FSCSV_PowerOnOffInformation does not inherit or define any methods. Association The class FSCSV_PowerOnOffInformation is associated with the class FSCSV_Chassis via the association class FSCSV_PowerOnOffStatistics. ServerView Operations Manager 305

306 20.2 WMI support in ServerView FSCSV_PowerOnOffStatistics (association class) The association class FSCSV_PowerOnOffStatistics associates the classes FSCSV_Chassis and FSCSV_PowerOnOffInformation. Parent classes Properties Name Type Description Element Ref: FSCSV_ Chassis Key (inherited). References the housing for which the statistical data in the instance of FSCSV_PowerOnOffInformation is recorded. Stats Ref: FSCSV_ PowerOnOffInformation Key (inherited). References an instance of FSCSV_PowerOnOffInformation. Table 125: Properties of the FSCSV_PowerOnOffStatistics class Methods The class FSCSV_PowerOnOffStatistic does not inherit or define any methods. Association ServerView Operations Manager 306

307 20.2 WMI support in ServerView FSCSV_PowerSupply The class FSCSV_PowerSupply describes the properties and administration of a power supply unit on a server. Parent classes Properties Name Type Description DeviceID string Key (inherited). Identifies an instance of FSCSV_PowerSupply. Table 126: Properties of the FSCSV_PowerSupply class Methods The class FSCSV_PowerSupply does not define any methods. Association The class FSCSV_PowerSupply is associated with the class FSCSV_VoltageSensor via the association class FSCSV_AssociatedSupplyVoltageSensor. ServerView Operations Manager 307

308 20.2 WMI support in ServerView FSCSV_SystemEnclosure The class FSCSV_SystemEnclosure provides information on a server housing. Parent classes Properties Name Type Description Tag string Key (inherited). Identifies the housing of a server. GroupNumber uint8 Group number of the CAN bus for the storage extension unit. PowerSupplySlots uint8 Number of power supply slots in the housing (maximum number of power supplies that can be installed). Table 127: Properties of the FSCSV_SystemEnclosure class The values of the following properties inherited from the class Win32_ SystemEnclosure are overwritten in FSCSV_SystemEnclosure: string CreationClassName string Caption string Description string Manufacturer Model Name PoweredOn SerialNumber ServerView Operations Manager 308

309 20.2 WMI support in ServerView Methods The class FSCSV_SystemEnclosure does not define any methods. Association The class FSCSV_SystemEnclosure is not associated with any other class via an FSCSV_... association class FSCSV_Tachometer The class FSCSV_Tachometer extends the default tachometer. Parent classes Properties Name Type Description DeviceID string Key (inherited). Identifies an instance of FSCSV_Tachometer. CurrentMaximum sint32 Maximum speed the tachometer can currently display (unit: rpm). DailyTestTime uint16 Time (unit: minutes after midnight), at which a fan test starts and peak speeds are measured. Table 128: Properties of the FSCSV_Tachometer class Methods Signature uint32 StartTest() Description Allows peak speed data to be gathered at any time. Table 129: Methods of the FSCSV_Tachometer class ServerView Operations Manager 309

310 20.2 WMI support in ServerView Association The class FSCSV_Tachometer is not associated with any other class via an FSCSV_... association class. ServerView Operations Manager 310

311 20.2 WMI support in ServerView FSCSV_TemperatureSensor The class FSCSV_TemperatureSensor describes the properties of a temperature sensor on a server. Parent classes Properties Name Type Description DeviceID string Key (inherited). Identifies an instance of FSCSV_TemperatureSensor. Table 130: Properties of the FSCSV_TemperatureSensor class Methods The class FSCSV_TemperatureSensor does not define any methods. Association The class FSCSV_TemperatureSensor is not associated with any other class via an FSCSV_... association class. ServerView Operations Manager 311

312 20.2 WMI support in ServerView FSCSV_VoltageSensor The class FSCSV_VoltageSensor extends the standard voltage sensor. Parent classes Properties Name Type Description DeviceID string Key (inherited). Identifies an instance of FSCSV_VoltageSensor. OutputLoad uint8 Current output voltage (in %) at the voltage sensor. Table 131: Properties of the FSCSV_VoltageSensor class Methods The class FSCSV_VoltageSensor does not define any methods. Association The class FSCSV_VoltageSensor is associated with the class FSCSV_PowerSupply via the association class FSCSV_AssociatedSupplyVoltageSensor. ServerView Operations Manager 312

313 20.3 WMI scripting FSCSV_Watchdog The class FSCSV_Watchdog represents a timer implemented in the system hardware which permits monitoring of the operating system, BIOS and other software components of a server. Parent classes Properties Name Type Description DeviceID string Key (inherited). Identifies an instance of FSCSV_Watchdog. Table 132: Properties of the FSCSV_Watchdog class Methods The class FSCSV_Watchdog does not define any methods. Association The class FSCSV_Watchdog is not associated with any other class via an FSCSV_... association class WMI scripting The WMI scripting library contains a number of automation objects which allow you to use script languages such as VBScript or JScript to access the CIM classes and instances in the WMI infrastructure. In this way, you can create scripts for a wide range of administration and monitoring tasks on your servers. The WMI scripting library is implemented in the component <Windows root directory>\wbem directory\wbemdisp.dll. ServerView Operations Manager 313

314 20.3 WMI scripting Structure of a WMI script One key advantage of WMI scripts is that their structure is largely uniform, which means that they are capable of carrying out different administration tasks with only minor modifications. Every WMI script is made up of the following steps: 1. Establish connection to the WMI service on the managed server. 2. Call up instances (managed objects) of a particular class. 3. Show properties of the managed objects. In the next section, these steps are explained on the basis of the sample script written in the script language Microsoft Visual Basic Scripting Edition (VBScript). You can find further detailed information on WMI scripting on the following Web pages, for instance: WMI script (example) The following script outputs the device ID for the fan(s) of the local server: adminserver = "." Set wbemservices = GetObject("winmgmts:\\" & adminserver) (1) Set wbemobjectset = wbemservices.instanceof("fscsv_fan") (2) For each wbemobjectset In wbemobjectset WScript.echo "Device ID of the fan " & wbemobject.deviceid (3) Establish connection to the WMI service on the managed server (1) To establish the connection to the managed server, the script passes the moniker name of the WMI scripting library as an argument to the VBScript function GetObject(). The moniker name is made up of the string "winmgmts" plus the name of the managed server. GetObject() returns an SWbemServices object of the WMI scripting library referenced by the variable wbemobjectset. This means that the SWbemServices method InstanceOf() is available. This method returns all managed objects (instances) of a particular type (in this case a fan or class FSCSV_Fan). Call up instances (managed objects) of a particular class (2) The InstanceOf() method returns all instances of the class FSCSV_Fan as an SWbemObjektSet list referenced by the variable wbemobjectset. SWbemObjectSet is an object of the WMI scripting library. ServerView Operations Manager 314

315 20.4 WMI CIM Studio (example) Show properties of the managed objects (3) The elements of an SWbemObjectSet list, i.e. the FSCSV_FAN instances, are objects of the type SWbemObject. They represent the individual instances of the requested class (in this example FSCSV_Fan) and thus make available the values for the properties defined in FSCSV_Fan for each instance. In our example, the DeviceID is evaluated. SWbemObject is an object of the WMI scripting library WMI CIM Studio (example) The following figure illustrates how the class FSCSV_ManagementController is represented in WMI CIM Studio. The navigation area of the window indicates the position of the class in the class hierarchy of the CIMv2 namespace. The right-hand side of the window provides information on the properties of FSCSV_ManagementController. Clicking on the icon in front of _Derivation opens a child window listing the parent classes of FSCSV_ ManagementController. Figure 91: Representation of the class FSCSV_ManagementController in WMI CIM Studio You can also view the methods, associations and instances of the class as well as the properties. ServerView Operations Manager 315