FUJITSU Software ServerView Suite
know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs.
Feel free to send us your comments by e-mail to
Certified documentation
according to DIN EN ISO 9001:2008
To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard DIN EN ISO 9001:2008.
cognitas. Gesellschaft für Technik-Dokumentation mbH
www.cognitas.de
Copyright and Trademarks
Copyright © 2015 Fujitsu Technology Solutions GmbH. All rights reserved.
Delivery subject to availability; right of technical modifications reserved.
1 Introduction . . . 13
1.1 Target groups and purpose of this manual . . . 16
1.2 Hardware/Software requirements . . . 16
1.3 Changes since the previous version . . . 17
1.4 ServerView Suite link collection . . . 19
1.5 Documentation for ServerView Suite . . . 20
1.6 Notational conventions . . . 21
1.7 Product names - conventions . . . 22
1.7.1 Naming of the PRIMEQUEST systems . . . 25
2 Architecture and Features . . . 27
2.1 Architecture . . . 27
2.2 Features . . . 30
2.2.1 User and security concept . . . 31
2.2.2 Recovery functions . . . 33
2.2.3 Prefailure Detection and Analysis (PDA) . . . 34
2.2.4 Monitoring functions . . . 35
2.2.5 High Availability - HA . . . 36
2.2.5.1 Transaction concept of Operations Manager . . . 40
2.2.6 ServerView agentless management . . . 41
2.2.6.1 Agentless mode . . . 41
2.2.6.2 Agentless mode with Agentless Service . . . 41
2.2.6.3 Agentless Management with ServerView Agentless Service 42
2.2.7 Support for VMware ESX Server and VMware vSphere Hypervisor (ESXi) . . . 43
2.2.7.1 Using a read-only user to monitor a VMware ESXi host in ServerView Operations Manager and/or ServerView RAID . 46 2.2.8 Functions protected by access authorizations . . . 52
3 Using ServerView Operations Manager . . . . 57
3.1 Starting ServerView Operations Manager . . . . 58
3.2 ServerView Operations Manager start page . . . . 61
3.3 ServerView Operations Manager main window . . . . 63
3.4 Exiting ServerView Operations Manager . . . . 69
3.5 Property window . . . . 70
3.6 Buttons in the property windows . . . . 72
3.7 Tabs in the property windows . . . . 73
3.8 Menus . . . . 79
3.8.1 Menus in the menu bar . . . . 80
3.8.2 Context menus in the ServerList window . . . . 86
3.8.3 Menus in the Single System View window . . . . 88
3.8.3.1 Menus in the ServerView <PRIMEQUEST_chassis_name> window . . . . 91
3.8.4 Menus in the SV Storage window . . . . 92
3.8.5 Menus in the PRIMEQUEST Partition window . . . . 94
3.9 Icons . . . . 97
3.9.1 Icons in the ServerList window . . . . 97
3.9.2 Icons in the ServerView [server_name] window . . . 109
3.9.3 Icons in the Device View window . . . 110
3.9.4 Icons in the Busses and Adapters window . . . 110
3.9.5 Icons in the Alarm Monitor window . . . 111
3.9.6 Other icons . . . 113
4 Administering the server list . . . 115
4.2.5.4 Hyper-V Servers in the server list . . . . 133
4.2.6 VMware ESXi hosts as normal servers in the server list . . . . 139
4.2.7 PRIMEPOWER Systems in the server list . . . . 139
4.2.8 Storage subsystems in the server list . . . . 140
4.2.9 Baseboard Management Controller (BMC) in the server list . . 146 4.2.10 PRIMEQUEST chassis in the server list . . . . 148
4.2.10.1 Enabling SNMP . . . . 148
4.2.10.2 Configuring SNMP . . . . 149
4.2.10.3 PSA agent . . . . 152
4.2.10.4 PRIMEQUEST chassis . . . . 153
4.2.10.5 PRIMEQUEST chassis/PRIMEQUEST partition is not Manageable . . . . 153
4.3 Server/server blade is not manageable . . . . 154
4.4 Server not manageable/ management controller icon . . . . 155
4.5 Defining and adding objects . . . . 156
4.5.1 Adding objects via the "ServerBrowser" window . . . . 156
4.5.1.1 Defining objects via Server Address tab . . . . 157
4.5.1.2 Defining objects via the browser . . . . 159
4.5.1.3 Adding objects to the server list . . . . 165
4.5.1.4 Adding hosts with virtualization software as normal servers to the server list . . . . 165
4.5.1.5 Adding TCP/IP devices to the server list . . . . 166
4.5.2 Adding objects by importing archive data . . . . 167
4.5.3 Adding objects by importing import files . . . . 167
4.5.3.1 Importing objects via import files via ServerList menu . . . . 168
4.5.3.2 Importing objects via import files via command line interface . . . . 170
4.6 Creating user-specific server groups . . . . 171
4.7 Deleting objects . . . . 171
4.7.1 Deleting networks, subnets or domains . . . . 171
4.7.2 Deleting objects from the server list . . . . 172
4.7.3 Deleting objects from the server list via command . . . . 172
4.8 Clusters in the server list . . . . 173
4.9 Checking the server list . . . . 174
4.13 Exporting the server list . . . 178
4.13.1 Exporting the server list via command line interface . . . 180
4.14 Defining settings for the server list . . . 181
4.15 Filtering server list entries . . . 182
5 Querying server data . . . 183
5.1 System status . . . 187 5.1.1 Environment . . . 188 5.1.1.1 Cooling . . . 188 5.1.1.2 Fan Configuration . . . 191 5.1.1.3 Temperature . . . 192 5.1.2 Mass Storage . . . 193
5.1.2.1 RAID information for VMware ESXi servers in the Single System View . . . 196 5.1.3 Power Supply . . . 198 5.1.3.1 Power Supplies . . . 199 5.1.3.2 Power Level . . . 203 5.1.3.3 Power Redundancy . . . 204 5.1.3.4 Configuration . . . 205 5.1.3.5 UPS Manager . . . 206 5.1.3.6 APC UPS . . . 207 5.1.4 System Board . . . 208 5.1.4.1 System Processors . . . 208 5.1.4.2 Memory Modules . . . 210 5.1.4.3 Voltages . . . 212 5.1.4.4 BIOS Selftest . . . 212
5.1.4.5 Busses and Adapters . . . 212
5.1.4.6 Trusted Platform Module . . . 212
5.1.5 Performance . . . 213
5.1.5.1 Processors . . . 221
5.2 System . . . . 229
5.3 Maintenance . . . . 230
5.3.1 Battery Information . . . . 230
5.3.2 System Event Log . . . . 230
5.3.3 Server Properties . . . . 231
5.3.4 ASR&R . . . . 236
5.3.5 Boot Options . . . . 238
5.3.6 Remote Management . . . . 238
5.3.6.1 Remote Management (RSB, BMC) . . . . 239
5.3.6.2 Remote Management (iRMC) . . . . 240
5.3.7 PrimeCollect . . . . 240
5.3.8 Online Diagnostics . . . . 241
5.3.9 Customer Self Service . . . . 242
5.4 Virtualization . . . . 243
5.4.1 Host Properties . . . . 243
5.4.2 Virtual Machines . . . . 244
5.4.3 Evacuation of virtual servers in the event of an error . . . . 245
5.5 Server not manageable with management controller Icon . 249 5.6 Server with BMC/iRMC, not manageable . . . . 250
6 Querying blade server data . . . . 251
6.1 Blade List . . . . 254 6.2 BladeServer Status . . . . 256 6.2.1 Environment . . . . 256 6.2.1.1 Cooling . . . . 256 6.2.1.2 Fan Configuration . . . . 257 6.2.1.3 Temperature . . . . 258 6.2.2 Power Supply . . . . 259 6.3 System . . . . 261 6.4 Maintenance . . . . 261
7.1.1.2 Memory Modules . . . 267 7.1.1.3 Voltages . . . 267 7.1.2 IOBs . . . 267 7.1.3 Environment . . . 268 7.1.3.1 Fan . . . 269 7.1.3.2 Temperature . . . 270 7.1.4 Mass Storage . . . 271 7.1.5 BIOS Selftest . . . 273
7.1.6 Busses and Adapters . . . 273
7.1.7 Performance . . . 273
7.1.8 Network Interfaces . . . 274
7.2 System . . . 276
8 Querying PRIMEQUEST chassis data . . . 277
8.1 Partition List . . . 280
8.2 System Status . . . 281
8.2.1 Hardware Components . . . 282
8.2.1.1 MMB (Management Board) . . . 282
8.2.1.2 SB (System Board) . . . 283
8.2.1.3 IOB (Input/Output Board) . . . 284
8.2.1.4 GSPB (Giga LAN SAS and PCI Box connector Board) . . . 285
8.2.1.5 DVDB (DVD Board) . . . 285
8.2.1.6 SASU (Serial Attached SCSI Units) . . . 286
8.2.1.7 PCI Box (Peripheral Component Interconnect) . . . 286
9.4 Storage Pools . . . . 299
9.5 Storage GUI . . . . 300
10 Querying BMC/iRMC data . . . . 301
11 Power Monitor . . . . 303
11.1 Starting the Power Monitor . . . . 304
11.2 Power Monitor - Server tab . . . . 306
11.3 Power Monitor - Data tab . . . . 310
11.3.1 One server or server blade on the Data tab . . . . 316
11.3.2 Multiple servers on the Data tab . . . . 317
12 Power management . . . . 321
13 Configuring servers remotely . . . . 325
14 Starting Advanced Video Redirection . . . . 329
15 Creating a user/password list . . . . 331
16 ServerView Status gadget for Windows Vista and Windows 7 . . . . 333
19 Collecting diagnostics data . . . 341 19.1 On Windows systems . . . 341 19.2 On Linux systems . . . 341 20 WMI . . . 343 20.1 WMI architecture . . . 344 20.1.1 WMI users . . . 345 20.1.2 WMI infrastructure . . . 345 20.1.3 Managed objects . . . 346 20.1.4 WMI security . . . 346
20.2 WMI support in ServerView . . . 347
20.2.1 System requirements . . . 347
20.2.2 ServerView agents as WMI providers . . . 348
20.2.3 ServerView classes . . . 348
20.2.3.1 FSCSV_ASR . . . 351
20.2.3.2 FSCSV_ASRSetting (association class) . . . 352
20.2.3.3 FSCSV_AssociatedCooling (association class) . . . 354
20.2.3.4 FSCSV_AssociatedSensor (association class) . . . 355
20.2.3.5 FSCSV_AssociatedSupplyVoltageSensor (association class) . . . 356
20.2.3.6 FSCSV_Chassis . . . 357
20.2.3.7 FSCSV_ComputerSystem . . . 359
20.2.3.8 FSCSV_FailReaction . . . 360
20.2.3.9 FSCSV_FailSetting (association class) . . . 362
20.2.3.10 FSCSV_Fan . . . 363
20.2.3.11 FSCSV_FRU . . . 364
20.2.3.12 FSCSV_FRUPhysicalElements (association class) . . . 365
20.2.3.13 FSCSV_ManagementController . . . 366
20.3 WMI scripting . . . . 380
20.3.1 Structure of a WMI script . . . . 380
20.3.2 WMI script (example) . . . . 381
20.4 WMI CIM Studio (example) . . . . 382
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
– 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
Management area Operations Manager component Described in Server management (ServerList) ServerList chapter 4
Single System View chapter 5 - 10 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
Manager, User Guide Alarm Configuration
Threshold Manager ServerView Threshold Manager, User Guide Monitoring Performance Manager ServerView Performance
Manager, User Guide
Power Monitor chapter 11
Update Management
Update Manager ServerView Update Management, User Guide Repository Manager
Download Manager Configuration
Security User Management User Management in
ServerView, Centralized Authentication and role-based Authorization, User Guide
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
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.
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
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:http://manuals.ts.fujitsu.com
Ê 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
1.6
Notational conventions
The following notational conventions are used in this manual:
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
V
Caution This symbol points out hazards that can lead to personal injury, loss of data or damage to equipment.I
This symbol highlights important information and tips. Ê This symbol refers to a step that you must carry out inorder to continue with the procedure.
semi-bold Commands, menu items, names of buttons, options, variables, file names and path names are shown in semi-bold in descriptive text.
fixed font System outputs are indicated using a fixed font.
semi-bold fixed font
Commands to be entered via the keyboard are written in a semi-bold fixed font.
<abc> Angle brackets are used to enclose variables which are to be replaced by actual values.
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 Notation in the text
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
Windows Server 2012
Windows Server 2008 and 2008 R2
Product name Notation in the text
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 ®
Windows Server 2008
Windows 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
Windows Server 2008 x64
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
Linux
Virtualization software
Product name Notation in the text
Red Hat Enterprise Linux 7
Red Hat Linux
Linux RHEL7
Red Hat Enterprise Linux 6 RHEL6
Red Hat Enterprise Linux 5 RHEL5
Red Hat Enterprise Linux AS (v.4) RHEL4 Red Hat Enterprise Linux ES (v.4)
SUSE Linux Enterprise Server 11 SUSE Linux SUSE Linux SLES11 or SLES 11
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
1.7.1
Naming of the PRIMEQUEST systems
This manual only describes PRIMEQUEST systems as of the PRIMEQUEST Product name Notation in the text
ServerView Installation Manager Installation Manager ServerView Deployment Manager Deployment Manager ServerView Operations Manager Operations Manager ServerView Inventory Manager Inventory Manager ServerView Archive Manager Archive Manager ServerView Event Manager Event Manager ServerView Threshold Manager Threshold Manager ServerView Performance Manager Performance Manager ServerView Virtual-IO Manager Virtual-IO Manager or VIOM ServerView Update Manager Update Manager
ServerView Download Manager Download Manager ServerView Online Diagnostics Online Diagnostics ServerView System Monitor System Monitor iRMC (integrated Remote Management
Controller)
iRMC
iRMC S2 / iRMC S3 / iRMC S4 (integrated Remote Management Controller)
iRMC S2/S3/S4
ServerView Remote Management Frontend
Remote Management Frontend
PrimeUp Installationstool PrimeUp
PRIMERGY Support Package PSP
Local Service Concept LSC
Fujitsu DeskView Integration in Microsoft System Center Configuration Manager
2.1
Architecture
The architecture of ServerView Operations Manager is based on a
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.
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
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
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
You will find an overview of the features available in ServerView Operations Manager in the following text.
2.2.1
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.
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.
Operator
administrator operator monitor
e.g. access archive mgr.
e.g. modify alarm config. e.g. access serverlist
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".2.2.2
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.
2.2.3
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.
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.2.2.4
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)
2.2.5
High Availability - HA
ServerView Operations Manager V5.30 and higher supports the following high-availability 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.
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 Datacenter1 3 3
[Hyper-V]
Windows Server 2008 R2 Enterprise1 3 3
[Hyper-V]
Windows Server 2008 R2 Standard1 3 3
[Hyper-V]
Windows Server 2008 R2 Foundation1 3 3
[Hyper-V] Windows Server 2008 Standard (x86, x64)1 3 3
[Hyper-V] Windows Server 2008 Enterprise (x86, x64)1 3 3
[Hyper-V]
Windows Server® 2012 Datacenter1 3 3
[Hyper-V]
Windows Server® 2012 Standard1 3 3
[Hyper-V]
Windows Server® 2012 Essentials1 3 3
[Hyper-V]
Windows Server® 2012 Foundation1 3 3
[Hyper-V]
Windows Server® 2012 R2 Datacenter1 3 3
[Hyper-V]
Windows Server® 2012 R2 Standard1 3 3
[Hyper-V]
Windows Server® 2012 R2 Essentials1 3 3
[Hyper-V]
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:
http://technet.microsoft.com/en-us/library/cc732181%28v=ws.10%29.aspx
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, ServerView1 The Windows Server Core Installation option is not supported for admin server and guest
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.
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 http://www.vmware.com/de/products/datacenter-virtualization/vsphere/high-availability.html.
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).
2.2.5.1 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:
2.2.6
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".
2.2.6.1 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.
2.2.6.2 Agentless mode with Agentless Service
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.
2.2.6.3
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.
– Supports data center security concepts
– 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 (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.
2.2.7
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.
– 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.
Figure 3: Virtual servers (example RX600 S4)
It is not possible to access the server hardware from virtual servers. Each virtual Example: RX600 S4
Virtual Servers
Linux
...
Windows Red Hat Windows
Server Enterprise Server
Server Hardware VMware ESX Server Operating System ServerView Agent for VMware
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.
I
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:
http://communities.vmware.com/thread/203414
2.2.7.1 Using a read-only user 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.
Set up a read-only user in VMware ESXi V 5.0.X
Ê Open vSphere Client and select Home – Administration – Roles – Add Role.
Ê Go to Home – Inventory – Inventory and click on the Local Users & Groups tab.
Ê Click Users on the Local Users & Groups tab to change to the Users View. Ê Select Add... in the context menu of the Users View. The Add New User
dialog is displayed.
Figure 5: The Add New User dialog
Ê Click to Permissions tab and select Add Permission in the context menu. The Assign Permissions dialog is displayed.
Figure 6: The Assign Permissions dialog
Set up a read-only user in VMware ESXi 5.1/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
Ê Add the new role Monitor under Name and check Host – CIM – CIM Interaction under All Privileges.
Ê Go to Home – Inventory – Inventory and click on the Local Users & Groups tab.
Ê Select Add... in the context menu of the Users View. The Add New User dialog is displayed.
Figure 8: The Add New User dialog
Ê Click to Permissions tab and select Add Permission in the context menu. The Assign Permissions dialog is displayed.
Figure 9: The Assign Permissions dialog
Ê Assign the role Monitor to the user monitor for the ESXi host. Ê Click OK.
Ê Login to the ESXi 5.1/5.5 host via SSH.
Ê 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 …
2.2.8
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 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:
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 the chapter "Creating a user/password list" on page 331.
Function Objects Authorization
Adding objects to the server list
BMC Read authorization
VMware server Read authorization Citrix XenServer server /
Xen server
Read authorization
KVM server Read authorization
Hyper-V server Administrator rights ETERNUS DX60/DX80/DX90/ DX60-S2/DX80-S2/ DX90-S2/DX400-S2 DX100-S3/DX200-S3 DX500-S3/DX600-S3 Standard authorization or administrator rights
Power management PRIMERGY server with BMC
Administrator rights
VMware server Administrator rights Citrix XenServer server /
Xen server
Administrator rights
KVM server Read authorization
2.2.9
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.
2.2.10 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 Deployment Manager – ServerView Virtual-IO Manager
2.2.10.1 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.
I
You will find a detailed description of Installation Manager in the2.2.10.2 ServerView Deployment Manager
ServerView Deployment Manager (referred to here as Deployment Manager for short) is integrated into ServerView Operations Manager. When it is started, ServerView Operations Manager detects whether Deployment Manager is installed on the central management station. If it is, the ServerView Operations Manager main window will contain the Deployment menu with the menu item Deployment Manager, via which you can start Deployment Manager.
Deployment Manager is a tool for installing a large number of servers quickly and correctly. The key point is that the process is completed entirely over the network.
I
You will find a detailed description of Deployment Manager in the Deployment Manager user guide.2.2.10.3 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 the 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.
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 section "Starting ServerView Operations Manager" on page 58 and section "Exiting
ServerView Operations Manager" on page 69.
– the ServerView Operations Manager start page, see section "ServerView Operations Manager start page" on page 61.
– the ServerView Operations Manager main window, see section "ServerView Operations Manager main window" on page 63.
– the property windows, their buttons and tabs, see section "Property window" on page 70, section "Buttons in the property windows" on page 72 and section "Tabs in the property windows" on page 73.
– an overview of the menu structure, see section "Menus" on page 79. – all the icons and their meanings, see section "Icons" on page 97.
ServerView Operations Manager also provides you with a comprehensive help system.
I
If problems occur accessing the Operations Manager, please refer to the "ServerView Suite Troubleshooting Guide" documentation.This documentation can be found at
http://manuals.ts.fujitsu.com/file/11310/
On a Windows-based management station you find the link under Start – [All ]Programs – Fujitsu – ServerView Suite – Operations
3.1
Starting ServerView Operations Manager
You can start ServerView Operations Manager either directly on the central management station or on any standard PC with intranet or Internet access and a Web browser.
Ê Enter the following Web addresses via a suitable Web browser: https://<system_name>.<domainname>:3170/sv_www.html On a Windows-based management station you can also start ServerView Operations Manager via the Windows start menu:
Ê Select Start – [All ]Programs – Fujitsu – ServerView Suite – Operations Manager – Operations Manager.
I
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:Ê Click on the white arrow at the bottom of the Start menu. The Apps menu is displayed.
Ê Right-click on the Operations Manager app. Possible actions appear at the bottom of the Apps menu.
Ê Click Pin to Start to show the Operations Manager app on the Start screen.
Ê Select the Operations Manager app on the Start screen. The communication occurs via an SSL-secured (Secure Socket Layer) connection.
On startup the login window of the Central Authentication Service is displayed.
I
● Make sure that your Web browser connects to your ServerView● If you use Mozilla Firefox as your Web browser, you may find that not all pop-up windows (e.g. context menus) are displayed. To unblock the pop-ups, open the browser and proceed as follows.
– Select Edit – Preferences.
– In the Content category list, select Pop-up Window. – Uncheck Block unrequested pop-up windows.
– In the Privacy category make sure that third-party cookies are accepted.
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.
Entering access data directly with the Web address
If you start ServerView Operations Manager via the Web address, you can enter the access data directly with the URL. You do this by specifying the user name and password with the username and password parameters.
Example
https://<system_name>.<domain_name>:3170/sv_www.html? Lang=ja&username=administrator&password=admin
https://<system_name>.<domain_name>:3170/ServerView/ sv_www.html?username=operator&password=admin
3.2
ServerView Operations Manager start page
When you launch ServerView Operations Manager, the following start page is displayed:
Figure 11: Start page
I
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.
I
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 section "Defining and adding objects" on page 156)
– Create a user/password list for the managed servers (see chapter "Creating a user/password list" on page 331)
– 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.
I
If you get a security warning from Java when you start Operations3.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 12: 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.
The ServerView Operations Manager main window then is divided into five sections:
● 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:
– 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.
● 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.
I
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 13: 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.
In the Category list box you can select which server property is to be searched. You can choose from the following properties:
– 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:
If results are found, a temporary group is created, otherwise an error message is displayed.
Figure 14: Search Groups window
The context menu for Search Groups is reduced:
Figure 15: 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:
– 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
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 section "Icons in the ServerList window" on page 97.
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.
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 section "Context menus in the ServerList window" on page 86.
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:
– Alarm Details tab - contains a brief description of the alarm selected in the server list.
3.4
Exiting ServerView Operations Manager
You exit ServerView Operations Manager via the Logout link in the title bar. Ê Click the Logout link. A window containing information on the logout
process opens.
Ê 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.
