ServerView Operations Manager V7.10

Transcription

1 User Guide - English FUJITSU Software ServerView Suite ServerView Operations Manager V7.10 Server Management Edition June 2015

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

3 Contents 1 Introduction Target groups and purpose of this manual Hardware/Software requirements Changes since the previous version ServerView Suite link collection Documentation for ServerView Suite Notational conventions Product names - conventions Naming of the PRIMEQUEST systems Architecture and Features Architecture Features User and security concept 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 read-only user to monitor a VMware ESXi host in ServerView Operations Manager and/or ServerView RAID Functions protected by access authorizations Integration options of ServerView Operations Manager Integrations in ServerView Operations Manager ServerView Installation Manager ServerView Deployment Manager ServerView Virtual-IO Manager ServerView Operations Manager

4 Contents 3 Using ServerView Operations Manager Starting ServerView Operations Manager 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 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 ServerView Operations Manager

5 Contents 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 objects via Server Address tab Defining objects via the browser Adding objects to the server list Adding hosts with virtualization software as normal servers to the server list 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 Importing objects via import files via command line interface 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 ServerView Operations Manager

6 Contents 4.13 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 Memory Modules Voltages BIOS Selftest Busses and Adapters Trusted Platform Module Performance Processors Memory Network Storage Others Network Network Adapters Network Interfaces Driver Monitor ServerView Operations Manager

7 Contents 5.2 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 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 ServerView Operations Manager

8 Contents Memory Modules Voltages IOBs Environment Fan Temperature Mass Storage BIOS Selftest Busses and Adapters Performance Network Interfaces System Querying PRIMEQUEST chassis data Partition List System Status Hardware Components 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 Fan Temperature Voltages Power Supply System Maintenance Querying storage subsystem data Configuration RAID Controller Enclosures ServerView Operations Manager

9 Contents 9.4 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 Power management Configuring servers remotely Starting Advanced Video Redirection Creating a user/password list ServerView Status gadget for Windows Vista and Windows FUJITSU Software ServerView Status app for Windows Communication paths ServerView Operations Manager

10 Contents 19 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) 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 ServerView Operations Manager

11 Contents 20.3 WMI scripting Structure of a WMI script WMI script (example) WMI CIM Studio (example) Fujitsu Technology Solutions Software License Agreement for End User ServerView Operations Manager

12 Contents ServerView Operations Manager

13 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 ServerView Operations Manager 13

14 Introduction Guarantees energy-efficient and, where possible, uninterruptible server operation Quicker response times in the event of errors Reduction in total cost of ownership (TCO) through efficient use of network components and their resources Very easy operation thanks to ergonomic software: clearly laid out, intelligent user guidance and supportive help system ServerView Operations Manager Operations Manager offers numerous components for the different management areas: This manual describes Operations Manager with its main components. Other components are described in separate manuals. 14 ServerView Operations Manager

15 Introduction Management area Operations Manager component Described in Server ServerList chapter 4 management Single System View chapter 5-10 (ServerList) Power Management chapter 12 Administration ServerBrowser chapter 4 Server Configuration chapter 13 Base Configuration Wizard 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 Alarm Configuration Manager, User Guide Threshold Manager ServerView Threshold Manager, User Guide Monitoring Performance Manager ServerView Performance Manager, User Guide Power Monitor chapter 11 Update Management Update Manager Repository Manager Download Manager Configuration ServerView Update Management, User Guide Security User Management User Management in ServerView, Centralized Authentication and rolebased Authorization, User Guide Table 1: ServerView Operations Manager ServerView Operations Manager 15

16 Target groups and purpose of this manual 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 Deployment Manager ServerView Scripting Toolkit ServerView Virtual I/O Manager 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. 16 ServerView Operations Manager

17 Changes since the previous version 1.3 Changes since the previous version This edition of the manual applies to ServerView Operations Manager V7.10 and replaces the following online manual: "ServerView Suite, ServerView Operations Manager V7.00", October 2014 edition. The manual features the following changes and enhancements: The section "ServerView Suite link collection" on page 19 has been updated. Migration of the directory service OpenDJ to the directory service ApacheDS, see section "Architecture" on page 27. New chapter "Using a read-only user to monitor a VMware ESXi host in ServerView Operations Manager and/or ServerView RAID" on page 46. New login window of the Central Authentication Service, see section "Starting ServerView Operations Manager" on page 58. Information on how to avoid security warnings or blocking of ServerView applets caused by running different Java applets within a Web browser, see section "Starting ServerView Operations Manager" on page 58. Support for Microsoft SQL Server 2014, see section "ServerView database" on page 115. For Hyper-V servers the dynamic ports for RPC should be opened for the process %SystemRoot%\System32\dllhost.exe, see section "Hyper-V Servers in the server list" on page 133. So that Hyper-V server provides IP addresses of the virtual servers certain conditions must be met, see section "Defining objects via the browser" on page 159. Now pumps are also supported as cooling systems, see section "Cooling" on page 188 and 256 and section "Fan" on page 269 and 287. The Locate button is also available for servers with Agentless service when connecting to the server via IPMI or SNMP protocols is possible, see chapter "Querying server data" on page 183 and section "Blade List" on page 254. While the Single System View for a VMware ESXi host is being opened, a progress bar is displayed, see section "RAID information for VMware ESXi servers in the Single System View" on page 196. Enhanced Power Supplies view for UPS, see section "Power Supplies" on page 199. ServerView Operations Manager 17

18 Changes since the previous version Resetting the error status after replacing system processors or memory modules, see section "System Processors" on page 208 and section "Memory Modules" on page ServerView Operations Manager

19 ServerView Suite link collection 1.4 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. For ServerView Suite, links are offered on the following topics: Forum Service Desk Manuals Product information Security information Software downloads Training I The downloads include the following: Current software versions 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 agents) 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 from the Fujitsu Web server. For PRIMERGY servers, links are offered on the following topics: Service Desk Manuals Product information Spare parts catalogue ServerView Operations Manager 19

20 Documentation for ServerView Suite 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 on the menu bar. This opens the start page of the ServerView Suite link collection. 2. Via the start page of the online documentation for the ServerView Suite on the Fujitsu manual server. I 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. This opens the start page of the ServerView Suite link collection. 3. Via the ServerView Suite DVD 2. Ê Ê In the start window of the ServerView Suite DVD 2, select the option ServerView Software Products. On the menu bar select Links. This opens the start page of the ServerView Suite link collection. 1.5 Documentation for 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. For an overview of the documentation to be found under ServerView Suite as well as the filing structure, see the ServerView Suite sitemap (ServerViewSuite Site Overview). 20 ServerView Operations Manager

21 Notational conventions 1.6 Notational conventions The following notational conventions are used in this manual: V Caution I This symbol points out hazards that can lead to personal injury, loss of data or damage to equipment. This symbol highlights important information and tips. Ê semi-bold fixed font semi-bold fixed font <abc> [Key symbols] Table 2: Notational conventions This symbol refers to a step that you must carry out in order to continue with the procedure. Commands, menu items, names of buttons, options, variables, file names and path names are shown in semibold in descriptive text. System outputs are indicated using a fixed font. Commands to be entered via the keyboard are written in a semi-bold fixed font. Angle brackets are used to enclose variables which are to be replaced by actual values. Keys are shown according to their representation on the keyboard. If uppercase letters are to be entered explicitly, then the Shift key is shown, e.g. [SHIFT] - [A] for A. If two keys need to be pressed at the same time, this is shown by placing a hyphen between the two key symbols. 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. Screen outputs Please note that the screen output is dependent in part on the system used and therefore some details may not correspond exactly to the output you will see on your system. You may also see system-dependent differences in the menu items available. ServerView Operations Manager 21

22 Product names - conventions 1.7 Product names - conventions In this document, product names used in the text are abbreviated as follows: 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 Notation in the text Windows Server 2012 Windows 22 ServerView Operations Manager

23 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 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 Notation in the text Windows Server 2008 Windows Server 2008 x64 Windows Server 2008 R2 Windows ServerView Operations Manager 23

24 Product names - conventions Linux Product name Red Hat Enterprise Linux 7 Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 5 Red Hat Enterprise Linux AS (v.4) Red Hat Enterprise Linux ES (v.4) SUSE Linux Enterprise Server 11 Notation in the text Red Hat Linux RHEL7 RHEL6 RHEL5 RHEL4 SUSE Linux SUSE Linux SLES11 or SLES 11 Linux Virtualization software Product name Notation in the text Microsoft Hyper-V Server Hyper-V Server Hyper-V Microsoft Hyper-V Server 2008 R2 Hyper-V Server 2008 R2 VMware ESX 3.5 ESX 3.5 VMware VMware ESX 4.0 ESX 4.0 VMware ESX 4.1 ESX 4.1 VMware ESXi 5.0 ESX 5.0 Citrix XenServer Citrix XenServer Red Hat Enterprise Linux 5 Xen Xen Server Red Hat Enterprise Linux KVM KVM 24 ServerView Operations Manager

25 Product names - conventions Product name ServerView Installation Manager ServerView Deployment Manager ServerView Operations Manager ServerView Inventory Manager ServerView Archive Manager ServerView Event Manager ServerView Threshold Manager ServerView Performance Manager ServerView Virtual-IO Manager ServerView Update Manager ServerView Download Manager ServerView Online Diagnostics ServerView System Monitor irmc (integrated Remote Management Controller) irmc S2 / irmc S3 / irmc S4 (integrated Remote Management Controller) ServerView Remote Management Frontend PrimeUp Installationstool PRIMERGY Support Package Local Service Concept Fujitsu DeskView Integration in Microsoft System Center Configuration Manager Notation in the text Installation Manager Deployment Manager Operations Manager Inventory Manager Archive Manager Event Manager Threshold Manager Performance Manager Virtual-IO Manager or VIOM Update Manager Download Manager Online Diagnostics System Monitor irmc irmc S2/S3/S4 Remote Management Frontend PrimeUp PSP LSC DeskView-Integration 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 Product names - conventions 26 ServerView Operations Manager

27 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. ServerView Operations Manager 27

28 Architecture Management console A browser-based console allows you to manage the servers and display the determined data. The following can be used as a browser: Microsoft Windows with Internet Explorer or Mozilla Firefox SUSE/Red Hat Linux with default Web browser released with distribution The Java Runtime Environment must also be installed. Central management station (CMS) On the central management station the ServerView Operations Manager is installed. The optional components of the ServerView Suite, such as Virtual IO- Manager, are also installed on the central management station and integrated in Operations Manager. The central management station (and thus the ServerView Operations Manager with its components) may also run on a Windows or Linux virtual machine (VM). The global user management of the ServerView Suite and of the irmc each centrally stores users for all Central Management Stations (CMS) / irmc in the directory of an LDAP directory service. This enables you to manage the users on a central server. The users can therefore be used by all the CMS and irmc that are connected to this server in the network. The ServerView Suite currently supports the following directory services: ApacheDS. Microsoft Active Directory 28 ServerView Operations Manager

29 Architecture During the installation of ServerView Operations Manager you have the option to choose ServerView s internal directory service (ApacheDS). For further information about the use of directory services with ServerView, refer to the manual User Management in ServerView (see "Documentation for ServerView Suite" on page 20). The data which ServerView creates and uses is stored in an SQL database within an SQL Server. The following SQL Server are part of the ServerView Operations Manager installation: SQL Server 2008 R2/2005 Express under Windows Server 2012/2008 PostgreSQL under Linux However, other Microsoft SQL Server databases can be used. The Java Runtime Environment is required on the central management station. How to install the ServerView Operations Manager is explained in the following manuals: Installing ServerView Operations Manager Software under Windows Installing ServerView Operations Manager Software under Linux ServerView Operations Manager 29

30 Features Managed servers On the managed servers, ServerView agents, CIM providers or ServerView Agentless Service should be installed, which supply the information to the central management station. ServerView RAID Manager and ServerView Update Agent should be also installed on the managed servers. The installation of ServerView agents on virtual machines (VMs) is not released. The ServerView agents are available for Windows, Linux and Citrix XenServer. ServerView CIM providers are available for Windows, Linux and VMware ESXi. Currently ServerView Operations Manager 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 Installing ServerView ESXi CIM Provider ServerView CIM Providers for Windows, Linux, and VMware ESXi. 2.2 Features The 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. 30 ServerView Operations Manager

31 Features You will find an overview of the features available in ServerView Operations Manager in the following text 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 figure 1 illustrates the concept of role-based user management with the predefined roles Administrator, Operator, Monitor and UserManager. ServerView Operations Manager 31

32 Features Users administrator operator monitor UserManager Roles Administrator Operator Monitor UserAdministrator Privileges e.g. modify alarm config. e.g. access archive mgr. e.g. access serverlist UserMgmt Figure 1: 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). 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. 32 ServerView Operations Manager

33 Features 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. I A detailed description of the user and security concept is provided in the documentation "User management in ServerView" 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 section "ASR&R" on page 236). ServerView Operations Manager 33

34 Features 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. 34 ServerView Operations Manager

35 Features 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). I The default setting is disabled. During the ServerView Agent 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 ServerView Operations Manager 35

36 Features High Availability - HA ServerView Operations Manager V5.30 and higher supports the following highavailability environments: Windows 2008 R2 Hyper-V cluster with ServerView Operations Manager V5.30 and higher and ServerView Virtual-IO Manager V2.6 and higher installed on a virtual machine with Windows Server operating system. VMware HA with ServerView Operations Manager V5.30 and higher and ServerView Virtual-IO Manager V2.6 and higher 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 Hyper-V cluster or in a VMware HA environment. 36 ServerView Operations Manager

37 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 1 [Hyper-V] Windows Server 2008 R2 Enterprise 1 [Hyper-V] Windows Server 2008 R2 Standard 1 [Hyper-V] Windows Server 2008 R2 Foundation 1 [Hyper-V] Windows Server 2008 Standard (x86, x64) 1 [Hyper-V] Windows Server 2008 Enterprise (x86, x64) 1 [Hyper-V] Windows Server 2012 Datacenter 1 [Hyper-V] Windows Server 2012 Standard 1 [Hyper-V] Windows Server 2012 Essentials 1 [Hyper-V] Windows Server 2012 Foundation 1 [Hyper-V] Windows Server 2012 R2 Datacenter 1 [Hyper-V] Windows Server 2012 R2 Standard 1 [Hyper-V] Windows Server 2012 R2 Essentials 1 [Hyper-V] Windows Server 2012 R2 Foundation 1 [Hyper-V] Table 3: Supported Hyper-V high-availability configurations ServerView Operations Manager 37

38 Features 1 The Windows Server Core Installation option is not supported for admin server and guest OS on VM. To set up the Windows 2008/2012 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 2: Failover action of the Hyper-V environment to the other cluster node I 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. 38 ServerView Operations Manager

39 Features 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. 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, refer to the Hyper-V manual. If an error occurs on a VM guest, the operation will continue if the VM guest is switched over. ServerView Operations Manager 39

40 Features 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 section "Transaction concept of Operations Manager" on page 40) 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 40 ServerView Operations Manager

41 Features ServerView agentless management Management via the irmc S4 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 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 and the operating system on the managed server. The consumers, such as ServerView Operations Manager and Nagios Plug-in, communicate with the irmc S4 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 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 Agentless mode with Agentless Service In agentless mode with Agentless Service, the server is managed exclusively via the irmc S4 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 occurs via HTI (High Speed Transfer Interface). SNMP runs on the irmc S4, not on the managed server itself. ServerView Operations Manager 41

42 Features The consumers, such as ServerView Operations Manager and Nagios Plug-in, communicate with the irmc S4 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 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, no management software connection on the managed server 42 ServerView Operations Manager