FUJITSU Software ServerView Suite FUJITSU Software ServerView Plug-in for VMware vcenter V2.6

Transcription

1 User Guide - English FUJITSU Software ServerView Suite FUJITSU Software ServerView Plug-in for VMware vcenter V2.6 Edition February 2018

2 Comments Suggestions Corrections The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs. Feel free to send us your comments by to 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 2017 FUJITSU LIMITED All rights reserved. Delivery subject to availability; right of technical modifications reserved. All hardware and software names used are trademarks of their respective manufacturers. Apache Tomcat, Tomcat, Apache, the Apache feather, and the Apache Tomcat project logo are trademarks of the Apache Software Foundation. FUJITSU Software ServerView Suite 2

3 Contents 1 Overview Integration approaches Monitoring and managing possibilities What s new Target groups and purpose of this manual Documentation for the ServerView Suite Abbreviations Typographic conventions 13 2 Installing on Windows Provisioning Requirements Installation notes Installing and registering Installing procedure Guided installing dialog Finished installation notes Verifying the deployment IPMI configuration Updating Unregistering and uninstalling Unregistering the SV Plug-in package Uninstalling the SV Plug-in Uninstalling via command line Uninstalling via Windows Control Panel 23 3 Installing on Linux Provisioning Requirements Deploying, configuring and registering the ServerView VMware vcenter Plug-in Appliance Deploying the virtual machine of the ServerView VMware vcenter Plug-in Appliance Starting the ServerView VMware vcenter Plug-in Appliance Configuring the ServerView VMware vcenter Plug-in Appliance Updating 28 FUJITSU Software ServerView Suite 3

4 Contents 3.5 Unregistering and uninstalling 29 4 Log in to vcenter Server using the vsphere Web Client Requirements and localization Procedure vsphere Web Client user interface 32 5 Configuration tasks and concepts SVvCenter Service configuration Opening the SVvCenter Service Configuration Overview Adding a vcenter to the SVvCenter Service Updating the vcenter credentials Removing a vcenter from the SVvCenter Service ServerView Profile Management Service configuration Opening the ServerView Profile Management Overview Customizing profiles Source code view Configuration wizard IPMI configuration FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on FUJITSU PRIMERGY vcenter role definitions Changing privileges of a role definition Starting irmc functions with/without single sign-on Requirements for single sign-on irmc functions with single sign-on irmc S4 Web Interface SSO enhancements Examples of using role definitions to limit irmc functionality vcenter user "monitor" and irmc access without SSO (irmc S2, S3, S4) vcenter user "monitor" and irmc access with SSO as irmc user "User" vcenter user "monitor2" and irmc "User" access and extended privilege "RemoteStorage" 48 6 SV Plug-in getting started and summary Entry point Views on the home page of the SV Plug-in Getting Started view Summary view Plug-in Definitions view Event Definitions Alarm Definitions 55 FUJITSU Software ServerView Suite 4

5 Contents Role Definitions 56 7 Monitoring ESXi-based hosts Access to the SV Plug-in information of an ESXi-based host SV Plug-in information of an ESXi-based host Information on the selected host - Status items and views Agentless management via IPMI FUJITSU PRIMERGY Actions (irmc-based operations) Starting a FUJITSU PRIMERGY Action The FUJITSU PRIMERGY Actions Storage view Prerequisites - information provider for the Storage view Information provider for the Storage view Information on the Storage view Driver Monitor view System Event Log view Monitoring vcenter or cluster host servers Access to the SV Plug-in information of the hosts of a vcenter/cluster FUJITSU PRIMERGY Actions 73 8 Monitoring FUJITSU PRIMERGY specific nodes Monitoring CX hosts Number of adjacent hosts for the selected CX host: Inventory Lists - Related Objects Information on adjacent hosts: Related Hosts tab Monitoring PRIMERGY blade servers Access to the SV Plug-in information of an MMB SV Plug-in information of an MMB node Monitor tab: Information on the selected MMB - Status items and views FUJITSU PRIMERGY Actions SVvCenter Service for MMBs Overview SNMP settings Receiving SNMP traps Monitoring PRIMEQUEST systems Access to the SV Plug-in information of a PRIMEQUEST system SV Plug-in information of a PRIMEQUEST system Monitor tab: Information on the selected PRIMEQUEST system - Status items and views FUJITSU PRIMERGY Actions 92 FUJITSU Software ServerView Suite 5

6 Contents SVvCenter Service for PRIMEQUEST systems Overview SNMP settings Receiving SNMP traps Discovering PRIMERGY Bmc Systems (for deploying) PRIMERGY Bmc Systems view Adding PRIMERGY Bmc Systems to the vcenter inventory Adding a PRIMERGY Bmc System manually Searching for PRIMERGY Bmc Systems Adding a PRIMERGY Bmc System from file SV Plug-in information of a PRIMERGY Bmc Systems FUJITSU PRIMERGY Actions Integration in the event management of the vsphere Web Client Requirements SVvCenter Service Configuration Overview Opening the SVvCenter Configuration Overview Properties of SVvCenter Services Further helpful service properties for the SVvCenter Service for events, MMBs and PRIMEQUEST systems Adding/removing a vcenter to/from the SVvCenter Service FUJITSU PRIMERGY Predefined Alarm Actions relating to SVvCenter Service Remote Management LED irmc Web Interface Remote console (AVR) irmc system report elcm Offline Update Offline update via elcm Requirements and compatibility warning Starting points Offline update via elcm started from SV Plug-in view Opening the elcm Offline Update view Opening the view of a host object Opening the view of a PRIMERGY Bmc System Checking requirements elcm Offline Update in progress 117 FUJITSU Software ServerView Suite 6

7 Contents elcm Update Workflow details Offline update via elcm started from SV Plug-in FUJITSU PRIMERGY Actions menu Starting Deploying PRIMERGY Bmc Systems Requirements Starting points Deployment via eim Opening the deployment wizard Opening the view of a PRIMERGY Bmc System Opening the view of Clusters or vcenter Servers Deployment wizard Error handling Time of data acquisition All expanded items are closed Retrieving data failed An action in the top left of the SV Plug-in interface is disabled An action in the context menu results in an error message Remote console (AVR) or irmc Web Client do not work as expected The same event generates a significant number of entries in the event management Repeated connection timeouts Editing a profile failed (using IE 11) Browsing for PRIMERGY bare metals systems failed (using IE 11) SV Plug-in cannot connect to the VMware vrealize Orchestrator (using Orchestrator V7.0) Executing SVSInstallerGUI.sh results in warnings (remote X Server, e.g. MobaXTerm) vcenter Server Appliance: Executing SVSInstallerGui.sh failed 129 FUJITSU Software ServerView Suite 7

8 1 Overview Virtualization solutions from Fujitsu Fujitsu is committed to total virtualization - from servers to storage to networks - and to virtualization software and operation management tools. The partnership between VMware and Fujitsu brings you continuity of technology assets, more efficient resource use, and steps toward the elimination of IT complexity. VMware and FUJITSU ServerView integrated virtualization support ServerView supports the CIM management standard, making it possible to monitor and manage VMware vsphere-based environments more reliably and securely. Administrators can view all physical and virtual machines through a single interface. vsphere Web Client VMware vsphere provides several interfaces for data center management and virtual machine access. Figure 1: VMware vsphere data center physical topology - (Source: support/pubs/) FUJITSU Software ServerView Suite 8

9 1.1 Integration approaches These interfaces include VMware vsphere Client (vsphere Client), vsphere Web Client for access through a Web browser, and vsphere Command Line Interface (vsphere CLI). The vsphere Web Client is the primary method for system administrators and end users to interact with the virtual data center environment created by VMware vsphere. The vsphere Web Client is a Web browser-based application that you can use to manage, monitor and administer the objects that make up your virtualized data center. It is possible to extend vsphere in different ways to create a solution for a unique IT infrastructure. vsphere Web Client can be extended by creating plug-in modules. A complete plug-in solution adds new capabilities to the vsphere Web Client graphical user interface. In this way third-party companies can integrate their GUIs and show information as desired. ServerView Suite and vsphere The ServerView Suite has implemented the ServerView ESXi CIM Provider, which is part of the VMware ESXi release. In addition, Fujitsu has implemented the FUJITSU Software ServerView Plug-in for VMware vcenter (SV Plug-in), which shows the values of a host system provided by the ServerView ESXi CIM Provider and the LSI CIM provider (Storage view). It is also possible to monitor most of the storage values via IPMI, if the IPMI credentials are configured. Via IPMI not all the values are available. The FUJITSU Software ServerView Plug-in for VMware vcenter (SV Plug-in) offers you a home page with a Getting Started view and a Summary view, which gives an overview of the information items provided by the SV Plug-in. Via the Monitor tabs for ESXi hosts, vcenters, clusters, MMBs and PRIMEQUEST systems, the SV Plug-in provides you with detailed information about FUJITSU PRIMERGY servers. This information includes properties of the system, fans, temperature sensors, power supplies, system processors, memory modules and the RAID subsystem. If the managed system is a PRIMERGY blade server, there will be additional information about management, server, storage, and connection blades. The SV Plug-in also includes the SVvCenter Service, which routes FUJITSU PRIMERGY-specific events to the vcenter event management to be monitored in the vsphere Web Client. 1.1 Integration approaches The FUJITSU Software ServerView Plug-in for VMware vcenter (SV Plug-in) integrates FUJITSU PRIMERGY-specific information into the vsphere Web Client interface. There are two approaches to do this: Data integration in the event and alarm management of the vsphere Web Client itself FUJITSU Software ServerView Suite 9

10 1.2 Monitoring and managing possibilities Full sites integrated in the vsphere Web Client offer the FUJITSU PRIMERGY-specific data of ESXi hosts, hosts of vcenters or clusters, MMBs and PRIMEQUEST systems 1.2 Monitoring and managing possibilities Figure 2: Architecture of the FUJITSU Software ServerView Plug-in for VMware vcenter Detailed information on a selected host and FUJITSU PRIMERGY actions The SV Plug-in offers various options for monitoring ESXi hosts, MMB blades or PRIMEQUEST systems: Status icons provide quick information. Detailed views provide more information on a selected host. And a number of FUJITSU PRIMERGY action items support calling a monitoring tool or making settings on the host. In regular operation the SV Plug-in generally shows the values of a host system provided by the ServerView ESXi CIM Provider. If a host has an older version of the ServerView ESXi CIM Provider, storage values are provided by the LSI CIM provider (see "Storage view" on page 66). It is also possible to monitor most of the storage values via IPMI, if the IPMI credentials are configured. See "Agentless management via IPMI" on page 62. Via IPMI not all the values are available. You can toggle between CIM and IPMI communication interfaces. Storage view The Storage view offers an overview of the RAID controllers found on the host and details of their logical drives and physical disks. FUJITSU Software ServerView Suite 10

11 1.2 Monitoring and managing possibilities If ServerView ESXi CIM Provider V8.0 or higher and ServerView RAID Core Provider are installed, the ServerView ESXi CIM Provider provides the information, on which the Storage view of the SV Plug-in is based. Otherwise, the information comes from the LSI CIM provider. Driver Monitor view Via the Driver Monitor view you can monitor and manage events relating to the components of a monitored host, as listed in the OS event log on the monitored host. System Event Log view Events of PRIMERGY systems will be forwarded to the vsphere Event Manager. You can also view the System Event Log, including specialized cause and resolution information. Monitoring vcenter or cluster host servers The SV Plug-in offers lists of the hosts assigned to a vcenter or a cluster. It offers less information on the individual host via this access point than via the inventory tree item Hosts, but all FUJITSU PRIMERGY actions are available. Monitoring CX hosts For a selected CX host the SV Plug-in shows a list of CX hosts powered on and running ESXi placed in the same chassis. Monitoring PRIMERGY blade servers To vsphere Web Client, an MMB is a custom object type. To support custom object types, the object navigator vcenter level has to be extended with a new inventory list. The SV Plug-in adds the new inventory list PRIMERGY Blade Server to the object navigator vcenter level. The SVvCenter Service is used to search for all MMBs. Monitoring PRIMEQUEST systems To vsphere Web Client, a PRIMEQUEST system is a custom object type. To support custom object types, the object navigator vcenter level has to be extended with a new inventory list. The SV Plug-in adds the new inventory list PRIMEQUEST Server to the object navigator vcenter level. The SVvCenter Service is used to search for all PRIMEQUEST systems. SVvCenter Service - Integration in event and alarm management of vcenter The SV Plug-in includes the SVvCenter Service, which routes FUJITSU PRIMERGY-specific events to the vcenter event management to be monitored in the vsphere Web Client. If a FUJITSU PRIMERGY host detects a problem, it will create a CIM indication and send it to subscribed destinations. An alarm is also created and can be configured for further actions. If SVvCenter Service is subscribed to the host, it will receive the CIM indication. It creates a vcenter event and forwards it to vcenter Server. So the FUJITSU PRIMERGY-specific event is shown in the regular Monitor-Events sub-tab of the vsphere Web Client. FUJITSU Software ServerView Suite 11

12 1.3 What s new Remote Management possibilities: Remote console (AVR), irmc Web interface and system identification LED The SV Plug-in offers some irmc-based operations - called FUJITSU PRIMERGY Actions - depending on the capabilities of the selected host. They make it very easy for the administrator to connect directly to an ESXi-based host and its irmc. The SV Plug-in enables you to start a session with the onboard management controller (irmc) of a managed PRIMERGY system via its Web interface or to contact a remote console. There are FUJITSU PRIMERGY vcenter role definitions designed for using single sign-on when starting the irmc Web interface and remote console. If the managed system is a PRIMERGY blade server, you can start the Configuration Web Application of its management board (MMB) as well. To simplify service tasks, the SV Plug-in allows you to turn the system identification LED of the PRIMERGY server on/off. Offline update via elcm (embedded Lifecycle Management) The SV Plug-in offers the option of starting an offline update via elcm on a host. elcm update management functionality is based on the ability of the irmc S4 to automatically download files from a repository server via the dedicated irmc S4 management LAN port and to store them on the irmc S4 SD card. Deploying PRIMERGY Bmc Systems Bare metal PRIMERGY systems without an operating system can be added to the SV Plug-in to deploy the ESXi operating system via ServerView profiles. The FUJITSU Software ServerView Plug-in for VMware vrealize Orchestrator Deployment provides the deployment workflow. embedded Installation Management (eim) is the elcm equivalent to the well-proven ServerView Installation Manager. Stored on the irmc S4 SD card for immediate use, no external ServerView media needed to set up and install FUJITSU PRIMERGY systems. 1.3 What s new This edition of the manual applies to FUJITSU Software ServerView Plug-in for VMware vcenter V2.6 and replaces the online manual "FUJITSU Software ServerView Suite, ServerView Plug-in for VMware vcenter V2.5", March 2017 edition. The manual features the following changes and enhancements: The values of the Storage view can be provided by the ServerView ESXi CIM Provider depending on its version, see "Storage view" on page 66. Fujitsu has implemented the ServerView VMware vcenter Plug-in Appliance for installing the SV Plug-in on Linux. The appliance offers a pre-installed virtual machine FUJITSU Software ServerView Suite 12

13 1.4 Target groups and purpose of this manual based on CentOS 6.9 and including the SV Plug-in installation, which you can deploy on an ESXi host. For further information see "Installing on Linux" on page 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 explains how you can monitor a VMware vsphere-based server with ServerView and vsphere, and describes how to deploy the FUJITSU Software ServerView Plug-in for VMware vcenter. 1.5 Documentation for the ServerView Suite The documentation can be downloaded free of charge from the Internet. You will find the online documentation at under the link x86 Servers. ServerView Sitemap For an overview of the documentation to be found under ServerView Suite as well as the filing structure, see the ServerView Suite Sitemap: 1. In the selection list on the left, select x86 Servers and then Software. 2. On the right, select ServerView Suite. 3. Click ServerView Suite Sitemap under Selected documents. 1.6 Abbreviations SV Plug-in In the following, SV Plug-in is short for FUJITSU Software ServerView Plug-in for VMware vcenter. 1.7 Typographic conventions The following typographic conventions are used: FUJITSU Software ServerView Suite 13

14 1.7 Typographic conventions Convention Explanation Indicates various types of risk, namely health risks, risk of data loss and risk of damage to devices. Indicates additional relevant information and tips. bold monospace monospace semibold blue continuous text pink continuous text <abc> [abc] [key] Indicates references to names of interface elements. Indicates system output and system elements for example, file names and paths. Indicates statements that are to be entered using the keyboard. Indicates a link to a related topic. Indicates a link to a location you have already visited. Indicates variables which must be replaced with real values. Indicates options that can be specified (syntax). Indicates a key on your keyboard. If you need to enter text in uppercase, the Shift key is specified, for example,[shift] + [A] for A. If you need to press two keys at the same time, this is indicated by a plus sign between the two key symbols. Screenshots Some of the screenshots are system-dependent, so some of the details shown may differ from your system. There may also be system-specific differences in menu options and commands. FUJITSU Software ServerView Suite 14

15 2 Installing on Windows The installation package includes both SV Plug-in and its vcenter services. The installer contains basically an executable which requests all required parameters, and a list of installers. The installer is started with a GUI. 2.1 Provisioning You can obtain the SV Plug-in in the following ways: Download from the Fujitsu website support.ts.fujitsu.com: 1. Choose Servers - PRIMERGY server - <server model> - Applications - Server Management Software - VMware Integration Solutions. Download from the ServerView Suite DVD. 2.2 Requirements The vcenter/vsphere version must be at least V6. vcenter/vsphere must be installed on Windows Server 2012 or on Windows Server 2012 R2 or on Windows Server 2016 Verify that vcenter Server is installed and that both vcenter Server and vsphere Web Client point to the same vcenter single sign-on instance. Java runtime V or higher. FUJITSU Software ServerView Plug-in for VMware vrealize Orchestrator V1.4 or higher FUJITSU Software ServerView Suite 15

16 2.3 Installation notes 2.3 Installation notes Installer with or without GUI You can start the installer of the SV Plug-in with or without GUI, see "Installing procedure" on page 17. Installation note: Apache Tomcat Web server As of version 2.2, the SV Plug-in and the SVvCenter Service are provided by the Apache Tomcat Web server. The SV Plug-in package contains a wrapper which installs SV Plug-in. The wrapper only installs the SV Plug-in if it finds an older version or none. Otherwise the setup is skipped. Installation note: Remote installation You can install the plug-in package on a different system than where vcenter resides. The installation default for SV Plug-in is local installation on a vcenter system. Installation note: Several vcenters - one installation Requirement: The vcenter systems must be within the same single sign-on environment. Once the SV Plug-in has been installed, you can connect an other vcenter to this SVvCenter Service: If another vcenter system (vc2) is within the same single sign-on environment, it is possible to connect this vcenter (vc2) to the SVvCenter Service (Service1) of a vcenter instance (vc1). In this case, once you have entered the user name and password, the vcenter (vc2) will be monitored by the SVvCenter Service (Service1) and the SV Plug-in will be registered on vcenter (vc2) as well. The SV Plug-in will be available for the hosts on vcenter (vc2), and you can monitor their values. Because the SV Plug-in will be registered on vcenter (vc2) as well, it is not necessary to perform a second installation. If you disconnect a vcenter, the SV Plug-in will be unregistered from that vcenter. 2.4 Installing and registering A plug-in package contains all the plug-in modules in an extension solution along with a package manifest. The package manifest provides deployment information for each plugin module using XML metadata. The vsphere Web Client Extension Manager uses this metadata to install and deploy each plug-in module in the plug-in package. FUJITSU Software ServerView Suite 16

17 2.4 Installing and registering You deploy a plug-in package to the vsphere Web Client by registering the package as an extension on vcenter Server. When you do this, your solution becomes available to any vsphere Web Client that connects to your vsphere environment. When a vsphere Web Client establishes a user session to vcenter Server, the vsphere Web Client application server queries vcenter Server for a list of all available plug-in packages that are registered as vcenter extensions. Any plug-in packages that are not present on the application server are downloaded and installed. Localization: The languages supported for installation on Windows are English and Japanese. If the operating system language matches one of these languages, the corresponding language will be selected for installing the SV Plug-in. In the case of other operating system languages, English is the default for installing the SV Plug-in. The SV Plug-in package: The SV Plug-in package consists of the following folders: common General installation files. documentation Further documentation. legal Documents like End User License Agreement (EULA). linux Installation files required for linux. windows Installation files required for windows Installing procedure After a new or update installation of the SV Plug-in any changes made to an alarm (for example actions) will be lost. You must reconfigure the action as needed. 1. In the Windows folder (see "The SV Plug-in package:" on page 17) execute the SVSInstaller.exe file on the vcenter Server system with administrator privileges (run as Administrator). The installer is started with graphical user interface (GUI) and the necessary parameters are requested via this user interface. FUJITSU Software ServerView Suite 17

18 2.4 Installing and registering Guided installing dialog 1. The dialog starts with an Installation window. Click Next. 2. Check the box I agree license agreement. 3. Click Next. A summary of the packages to install is displayed. 4. Click Next. 5. In the dialog FUJITSU Software ServerView Web Server parameters provide the necessary information for Apache Tomcat. IP Address Is preset by the system. Destination folder The Destination folder can be changed, preferred is the default folder. Computer Is preset by the system. DNS Suffix HTTP Port / HTTPS Port Are preset by the system. Can be changed. Open the ports given here (default: 3169, 3170) in your firewall. The ports are checked for usage. If they are in use by another program, proceeding is denied. Service account: Use local service? / Service account: Username - Password 6. Click Next. The Web server has to run under a user account without administrator privileges. You ve got two options: It is possible to use the in-built account LocalService. You can specify an existing user account. FUJITSU Software ServerView Suite 18

19 2.4 Installing and registering 7. Provide the necessary information for SV Plug-in and its vcenter services. Only one EventService registration is allowed for a vcenter Server system. If a registration already exists for a vcenter Server system, you will be notified and the setup will be denied. If you are sure you want to change this registration, you must unregister the registered EventService first. If the vcenter Server on which the SV Plug-in is registered is no longer reachable, a dialog box with a force uninstall option will be displayed. If you choose forced uninstall, the registration will not be removed. vcenter Server FQDN <ServerName.DomainSuffix> of the vcenter Server system Only preset if vcenter is running. If you install a SVvCenter Service on a vcenter Server system, you must ensure that your entries Name of the Plug-In service station and DNS suffix of the Plug-In service station correspond to the Server FQDN entry. vcenter User/ Password Credentials for vcenter Server For registering the SV Plug-in with vcenter Server, the user name and password of a vcenter administration account are requested. Several vcenters - one installation (see "Installation note: Several vcenters - one installation " on page 16): In this case, once the user name and password have been entered, the SV Plug-in will be registered on vcenter (vc2) as well. If you disconnect a vcenter, the SV Plug-in will be unregistered from that vcenter. IP Address of the Plug-In service station (completed beforehand, constant) IP address on which the package will be installed Name of the Plug-In service station (completed beforehand, constant) Name of the system where the package will be installed DNS suffix of the Plug-In service station (completed beforehand, constant) Suffix of the system where the package will be installed SNMP community strings for MMB s (comma separated) Comma separated list of communities to be used for MMB access, see "SNMP settings" on page 85. The setting SNMP community strings (comma separated) is used to search for blade servers, see "SNMP settings" on page 85. FUJITSU Software ServerView Suite 19

20 2.4 Installing and registering 8. Click Install. The progress of the installation process is displayed. The process of deploying package by package will be a few more minutes. The vcenter Service is one of the last packages to deploy. But only this vcenter Service registers with vcenter. Therefore the SV Plug-in will be indicated in vcenter pretty late only Finished installation notes To ensure consistency between vcenter Server extension registration and Web Client client plug-in administration, you should restart all vsphere Web Client services that use the SV Plug-in. It is recommended that you clear both the Java cache and browser cache be after the SV Plug-in is installed. This is especially important after an upgrade installation. Be aware that after installation or update of the SV Plug-in, the first login to vsphere Web Client can take significantly longer. If another vcenter (vc2) is within the same single sign-on environment, it is possible to connect this vcenter to the SVvCenter Service (Service1) of one vcenter (vc1) without a second installation (see "Installation note: Several vcenters - one installation " on page 16) Verifying the deployment Use the vcenter Managed Object Browser to verify the deployment of the SV Plug-in. The vcenter Managed Object Browser runs in a Web browser and is accessed by using the fully-qualified domain name or IP address for the vcenter Server system. To access the vcenter Managed Object Browser 1. Start a Web browser. 2. Enter the fully-qualified domain name (or the IP address) for the vcenter Server system and add /mob. For example: name or IPaddress>/mob 3. Enter the user account and password for the vcenter Server. The first time you log in to the vcenter Managed Object Browser after the SV Plug-in is installed, login can take longer than usual (up to several minutes). FUJITSU Software ServerView Suite 20

21 2.5 Updating If warning messages about the SSL certificate appear, you can ignore them and continue logging in to the vcenter Managed Object Browser, if VMware is the certificate authority and you are not in a production environment. The vcenter Managed Object Browser starts up. 4. In the vcenter Managed Object Browser start window, click content. A window about the data object type ServiceContent opens. 5. In the ServiceContent window, click ExtensionManager. The ExtensionManager window opens. In this window, the extension com.fujitsu.primergy.ssv is listed and you will find an entry: com.fujitsu.primergy.eventservice. Additional check: You will find a new SVvCenter Service dialog in the overview and administration pages of the SV Plug-in, see "Summary view" on page 53 and "SVvCenter Service configuration" on page IPMI configuration The IPMI credentials (user name and password) must be configured to have access to a number of irmc based actions on an ESXi host: Toggle Identify LED Start the irmc Web Interface with single sign on Start the Remote Console (AVR) Start a System Report Start an elcm Offline Update Workflow In addition, when the credentials are configured, it is possible to view monitoring data from the system over IPMI which can be useful if problems with the CIM Provider arise. For how to configure the user name and password for IPMI configuration, see "IPMI configuration" on page Updating Due to technical restrictions, an upgrade installation can only be performed for SV Plug-in V2.1.4 or later. Before the SV Plug-in can be installed, the previous version must be installed. FUJITSU Software ServerView Suite 21

22 2.6 Unregistering and uninstalling If you have changed the privileges in one of the FUJITSU PRIMERGY role definitions and you update the SV Plug-in version, the role definitions will be overwritten (see "Changing privileges of a role definition" on page 42)! After a new or update installation of the SV Plug-in any changes made to an alarm (for example actions) will be lost. You must reconfigure the action as needed. 2.6 Unregistering and uninstalling Unregistering the SV Plug-in package If you want to unregister and uninstall the SV Plug-in, see "Uninstalling the SV Plugin" on page 22. You can unregister the SV Plug-in package using the vcenter Managed Object Browser interface (see "Verifying the deployment" on page 20). Several vcenters - one installation (see "Installation note: Several vcenters - one installation " on page 16): If you disconnect a vcenter, the SV Plug-in will be unregistered from that vcenter. Unregistering a plug-in package on vcenter Server does not delete the plug-in package files that are installed locally on the vsphere Web Client Virgo server. The files are no longer used after the package has been unregistered, but if you want to remove them for cleanup purposes, you must remove them manually. You can remove the files installed on the vcenter Server and unregister the SV Plug-in in one step by using the uninstall procedure (see "Uninstalling the SV Plug-in" on page 22) Uninstalling the SV Plug-in There are two ways for uninstalling: via command line via the Windows Control Panel If the vcenter Server on which the SV Plug-in is registered is no longer reachable, a dialog box with a force uninstall option will be displayed. You should only use this option if the vcenter Server system has failed Uninstalling via command line The application SVSInstaller.exe is copied to the target system: FUJITSU Software ServerView Suite 22

23 2.6 Unregistering and uninstalling <PROGRAMFILES>\Fujitsu\ServerView Suite\SVSInstaller (default path) or <selected path>\svsinstaller (custom path) In this folder execute the SVSInstaller.exe file: \SVSInstaller.exe -u Uninstalling via Windows Control Panel Basically, there is the entry FUJITSU Software ServerView Installer. The packages are given below. Figure 3: Uninstalling via Windows Control Panel 1. Select the entry FUJITSU Software ServerView Installer. 2. There are two ways to start the deinstallation process: Double-click on the entry FUJITSU Software ServerView Installer. or Click the button Uninstall. Once the installation has finished the entry FUJITSU Software ServerView Installer and its packages will still be displayed. 3. Refresh your screen display (e.g. [F5]). The packages are no longer displayed. The entry FUJITSU Software ServerView Installer will still be displayed. 4. Select the entry FUJITSU Software ServerView Installer. 5. Double-click on the entry FUJITSU Software ServerView Installer. or FUJITSU Software ServerView Suite 23

24 2.6 Unregistering and uninstalling Click the button Uninstall. The entry FUJITSU Software ServerView Installer is no longer displayed. FUJITSU Software ServerView Suite 24

25 3.1 Provisioning 3 Installing on Linux Fujitsu has implemented the ServerView VMware vcenter Plug-in Appliance for installing the SV Plug-in on Linux. The appliance offers a pre-installed virtual machine based on CentOS 6.9 and including the SV Plug-in installation, which you can deploy on an ESXi host. 3.1 Provisioning You can obtain the SV Plug-in in different ways (see "Provisioning" on page 15). 3.2 Requirements The vcenter/ vsphere version of the VMware vcenter Server must be at least V6. FUJITSU Software ServerView Plug-in for VMware vrealize Orchestrator V1.4 or higher Localization: The supported language for ServerView VMware vcenter Plug-in Appliance is English. 3.3 Deploying, configuring and registering the ServerView VMware vcenter Plug-in Appliance Deploying the virtual machine of the ServerView VMware vcenter Plug-in Appliance After downloading the OVA file, you can deploy it using the VMware vsphere Client or vsphere Web Client. Procedure: Before you begin: Identify the DNS records and host name to use for your connector OVA deployment. 1. In the vsphere Client or the vsphere Web Client, select File - Deploy OVF Template. 2. In the Deploy OVF Template pages, enter the information specific to your deployment. FUJITSU Software ServerView Suite 25

26 3.3 Deploying, configuring and registering the ServerView VMware vcenter Plug-in Appliance Depending on your network speed, the deployment can take several minutes. You can view the progress in the progress dialog box. 3. When the deployment is complete, select the appliance, right-click, and select Power - Power on. During Power on the following question is displayed: Cannot connect the virtual device ide0:0 because no corresponding device is available on the host. Do you want to try to connect this virtual device every time you power on the virtual machine? 4. Answer the question with No. The virtual machine is initialized. You can go to the Console tab to see the details. 5. To launch the ServerView VMware vcenter Plug-in Appliance open a remote console Starting the ServerView VMware vcenter Plug-in Appliance 1. To launch the ServerView VMware vcenter Plug-in Appliance open a remote console. 2. Start the ServerView VMware vcenter Plug-in Appliance. Figure 4: ServerView VMware vcenter Plug-in Appliance - setting the root password 3. Set the root password. A link is displayed for configuring the ServerView VMware vcenter Plug-in Appliance via Web user interface. FUJITSU Software ServerView Suite 26

27 3.3 Deploying, configuring and registering the ServerView VMware vcenter Plug-in Appliance Figure 5: ServerView VMware vcenter Plug-in Appliance - URL for starting the Web UI Configuring the ServerView VMware vcenter Plug-in Appliance Before you begin: Use either Firefox or Chrome browsers. Using Internet Explorer could cause problems. 1. Start the Web UI of the ServerView VMware vcenter Plug-in Appliance in a web browser. Login page is displayed. 2. Login with user root credentials. The main page of the Web UI of the ServerView VMware vcenter Plug-in Appliance is displayed. 3. Select the System tab. Figure 6: ServerView VMware vcenter Plug-in Appliance Web UI: System Information 4. Configure time zone and system parameters. FUJITSU Software ServerView Suite 27

28 3.4 Updating 5. Select the vcenter tab. Figure 7: ServerView VMware vcenter Plug-in Appliance Web UI: vcenter Configuration 6. Specify the vcenter Server FQDN. 7. Configure credentials and vcenter Plug-in Service Station Configuration settings. 8. Click the Save and Validate button. The ServerView VMware vcenter Plug-in Appliance complements the settings for vcenter Server:. 9. Click Install and Register. The input fields in the vcenter tab are grayed out and in the Extension Address field PENDING is displayed. Installation and registration may take up to 30 minutes. After installation and registration are finished LOCAL is displayed in the Extension Address field. 3.4 Updating 1. Download the latest iso image of the ServerView VMware vcenter Plug-in Appliance, see "Provisioning" on page Provide the iso image on DVD in vcenter. 3. Start the Web UI of the ServerView VMware vcenter Plug-in Appliance in a web FUJITSU Software ServerView Suite 28

29 3.5 Unregistering and uninstalling browser. Login page is displayed. 4. Login with user root credentials. The main page of the Web UI of the ServerView VMware vcenter Plug-in Appliance is displayed. 5. Select the Update tab. Figure 8: ServerView VMware vcenter Plug-in Appliance Web UI: Update 6. Click Check Updates. The Available Updates are listed. 7. Click Install Updates. The ServerView VMware vcenter Plug-in Appliance is updated. 3.5 Unregistering and uninstalling It is necessary to unregister and uninstall the ServerView VMware vcenter Plug-in Appliance before removing the virtual machine of the appliance. Otherwise the registration on the vcenter server will persist. You will have to remove it by using MOB. 1. Start the Web UI of the ServerView VMware vcenter Plug-in Appliance in a web browser. Login page is displayed. 2. Login with user root credentials. The main page of the Web UI of the ServerView VMware vcenter Plug-in Appliance is displayed. 3. Select the vcenter tab. FUJITSU Software ServerView Suite 29

30 3.5 Unregistering and uninstalling 4. Click Unregister and De-Install. The ServerView VMware vcenter Plug-in Appliance is unregistered from vcenter server. 5. You can remove the virtual machine of the ServerView VMware vcenter Plug-in Appliance. FUJITSU Software ServerView Suite 30

31 4.1 Requirements and localization 4 Log in to vcenter Server using the vsphere Web Client 4.1 Requirements and localization Requirements: vcenter Server and vsphere Web Client Verify that vcenter Server is installed and that both vcenter Server and vsphere Web Client point to the same vcenter single sign-on instance. Internet Explorer 11: You must configure a certain option under Internet Properties. If this option is not checked, editing a profile (see "Customizing profiles" on page 36) or browsing for PRIMERGY Bmc Systems (see "Discovering PRIMERGY Bmc Systems (for deploying)" on page 94) will fail. 1. Select Internet Properties - General - Settings - Temporary Internet Files. 2. Under Check for newer versions of stored pages check the option Every time I visit the webpage. Localization: The languages supported for using the SV Plug-in are English, German and Japanese. If the browser language matches one of these languages, the corresponding language will be selected for the SV Plug-in. 4.2 Procedure 1. Open a Web browser and enter the URL for the vsphere Web Client: By default the port is 9443, but this can be changed during vsphere Web Client installation 2. In the Username text box, enter the user name that is registered on the vcenter single sign-on and has permissions on vcenter Server. 3. In the Password text box, enter the password. FUJITSU Software ServerView Suite 31

32 4.3 vsphere Web Client user interface 4. Click Login. The vsphere Web Client connects to all the vcenter Server systems that the specified user has permissions for, allowing you to view and manage your inventory. 4.3 vsphere Web Client user interface Figure 9: Main parts of the vsphere Web Client user interface (Source: The user interface layer of the vsphere Web Client contains all the Flex objects, such as data views, toolbars and navigation interfaces, that make up the vsphere Web Client graphical user interface. The main parts of the vsphere Web Client user interface are the object navigator, the main workspace and the tasks and alarms panel. Your selections in the object navigator drive the contents of the vsphere Web Client main workspace. In the object navigator vcenter level, vsphere objects are organized into inventory trees and inventory lists. When you select an object in the object navigator, information about it appears in the main workspace. When you browse the virtual infrastructure using the object navigator, the main workspace displays an object workspace. FUJITSU Software ServerView Suite 32

33 5.1 SVvCenter Service configuration 5 Configuration tasks and concepts 5.1 SVvCenter Service configuration You can use the SVvCenter Service Configuration Overview to manage all the SVvCenter Services installed in your environment. For performance reasons we recommend one SVvCenter Service per vcenter server Opening the SVvCenter Service Configuration Overview At the bottom of the getting started tab on the home page of the SV Plug-in, you will find the Manage the SVvCenter Services link. 1. In the object navigator of the vsphere Web Client, select the item Administration. 2. Select the sub-item FUJITSU PRIMERGY Administration. 3. Select the sub-item SVvCenter Service Configuration Overview. In the main workspace of the vsphere Web Client the SVvCenter Service Configuration Overview opens. The Default Snmp Communities setting is used to search for blade servers (see "SNMP settings" on page 85). You can edit this list (comma-separated) by clicking the pencil icon seen in this section. SVvCenter Service must be configured as a trap destination on the registered MMBs. For further information see "Properties of SVvCenter Services" on page Adding a vcenter to the SVvCenter Service The following procedure will help if a connection problem with a SVvCenter Service occurs: If a vcenter is connected to a failing SVvCenter Service and you connect it to another SVvCenter Service, the vcenter will be disconnected from the failing SVvCenter Service and added to the new one. FUJITSU Software ServerView Suite 33

34 5.1 SVvCenter Service configuration If you have changed the privileges in one of the FUJITSU PRIMERGY role definitions and you connect the vcenter (to which the role is assigned) to another SVvCenter Service, the role definitions will be overwritten! See "Changing privileges of a role definition" on page In the SVvCenter Service Configuration Overview, select a SVvCenter Service in the Service Location selection box. The current properties of the selected SVvCenter Service are displayed. 2. Click the + icon. A dialog opens: Figure 10: Add a vcenter to the SVvCenter Service 3. Select one vcenter in the Available vcenters selection box. The current connection status of the selected vcenter is displayed. 4. Enter the user name and password of the administrator account of the vcenter. 5. Click Connect. The vcenter is added to the SVvCenter Service. The SVvCenter Service searches for blade servers or PRIMEQUEST systems subscribes to the hosts found in the vcenter, and forwards any indications or traps to the vcenter Updating the vcenter credentials It may be necessary to update the credentials of a vcenter (e.g. if the administrator password has changed). FUJITSU Software ServerView Suite 34

35 5.2 ServerView Profile Management Service configuration 1. In the SVvCenter Service Configuration Overview, select a SVvCenter Service in the Service Location selection box. The current properties of the selected SVvCenter Service are displayed. 2. In the vcenter Name list, select the desired vcenter. 3. Click the pencil icon. A dialog opens. 4. Enter the user name and password of the administrator account of the vcenter. 5. Click Update Connection. The vcenter credentials are updated on the SVvCenter Service Removing a vcenter from the SVvCenter Service A SVvCenter Service requires at least one vcenter to be connected. Therefore, it is only possible to disconnect a vcenter if more than one vcenter is connected. To disconnect all vcenters from a SVvCenter Service, uninstall the SVvCenter Service. 1. In the SVvCenter Service Configuration Overview, select one SVvCenter Service in the Service Location selection box. The current properties of the selected SVvCenter Service are displayed. 2. In the vcenter Name list, select the desired vcenter. 3. Click the X icon. The vcenter is disconnected from the SVvCenter Service. 5.2 ServerView Profile Management Service configuration Bare metal PRIMERGY systems without an operating system can be added to the SV Plug-in to deploy the ESXi operating system via ServerView profiles. To do so you must 1. Add the PRIMERGY Bmc System(s) to the SV Plug-in, see "Adding PRIMERGY Bmc Systems to the vcenter inventory" on page Store a customized ServerView profile under FUJITSU PRIMERGY Administration, see "Opening the ServerView Profile Management Overview" on page Deploy the ESXi operating system via the ServerView Deployment vrealize Orchestrator Workflow, see "Deploying PRIMERGY Bmc Systems" on page 120. The ServerView Profile Management Service is part of the SV Plug-in. The service allows you to store custom profiles. FUJITSU Software ServerView Suite 35

36 5.2 ServerView Profile Management Service configuration Each profile is defined in a JSON-formatted file. The file contains information about repository configuration, network configuration and user data. The profile file will be sent to the SysRollout service to configure a PRIMERGY Bmc System Opening the ServerView Profile Management Overview 1. In the object navigator of the vsphere Web Client, select the item Administration. 2. Select the sub-item FUJITSU PRIMERGY Administration. 3. Select the sub-item ServerView Profile Management. In the main workspace of the vsphere Web Client the ServerView Profile Management overview opens. Default Profiles Under Default Profiles you find a list of the predefined profiles which come with the SV Plug-in: Template ESXi IDE Without adaptations these Default Profiles are not suitable for deploying. For a PRIMERGY Bmc System with IDE adapter. Template ESXi Any Configuration For a PRIMERGY Bmc System with a complete RAID configuration. The template does not change the RAID configuration, it simply installs the ESXi operating system. Template ESXi Raid Configuration For a PRIMERGY Bmc System which needs a RAID configuration. Customize this profile according to your needs: Export the profile definition. Adjust the RAID parameters according to your needs. Import the changed profile and save it as an custom profile - see "Customizing profiles" on page Click the arrow in front of the desired profile to expand the entry. A summary of the values of this profile is shown Customizing profiles You can configure your own profiles according to your needs. Use the Default Profiles and customize it (see "Opening the ServerView Profile Management Overview" on page 36). To FUJITSU Software ServerView Suite 36

37 5.2 ServerView Profile Management Service configuration get a template you can prepare a profile leaving some values blank. Working connections are prerequisite for handling profiles. Therefore these connections are regularly checked. If the Profile Management Service can not be connected, you can not configure profiles. If VMware vrealize Orchestrator is not connected to the vcenter or the FUJITSU Software ServerView Plug-in for VMware vrealize Orchestrator Deployment is not installed, you can not start deployment processes. Related error messages are displayed in the ServerView Profile Management overview under Issues. Internet Explorer 11: You must configure a certain option under Internet Properties, see "Requirements and localization" on page 31. If this option is not checked, editing a profile or browsing for PRIMERGY Bmc Systems will fail. 1. Select the desired profile. 2. Click one of the icons: Add Edit View Delete Starts the configuration wizard - see "Configuration wizard" on page 38. Starts the configuration wizard - see "Configuration wizard" on page 38. Opens a window showing the source code of the profile definition - see "Source code view" on page 37. Deletes the selected profile Source code view Clicking the icon opens a window showing the source code of the profile definition. FUJITSU Software ServerView Suite 37

38 5.2 ServerView Profile Management Service configuration Figure 11: Profile definiton view 1. Click the Save button to save changes Configuration wizard Internet Explorer 11: You must configure a certain option under Internet Properties, see "Requirements and localization" on page 31. If this option is not checked, editing a profile or browsing for PRIMERGY Bmc Systems will fail. 1. Clicking the Add icon or the Edit icon starts a profile configuration wizard. 2. Choose Profile Profile Name (mandatory Name of the profile Description Comment on the profile Profile Definition Source (mandatory) There are two options: You can use a default profile or an existing custom profile as basis for your new profile. Select the desired profile from the list under Default Profile. Import a profile definition using the Browse button under Import File. FUJITSU Software ServerView Suite 38

39 5.2 ServerView Profile Management Service configuration 3. Image Repository Information The imported profile must defined in a JSON-formatted file. The file will be parsed and proved to be valid. Defines the repository where the ISO image for ESXi is stored in. Ensure the accessibility of the repository for the PRIMERGy Bmc System during the deployment (firewalls etc.). The configuration of ESXi must match the ISO image. Security issue: The password is stored in plain text. For security reasons fill it in just before the deployment. 4. Image Repository Information Defines the repository where the ISO image for ESXi is stored in. Ensure the accessibility of the repository for the PRIMERGy Bmc System during the deployment (firewalls etc.). The configuration of ESXi must match the ISO image. Security issue: The password is stored in plain text. For security reasons fill it in just before the deployment. 5. User Data Information Security issue: The password is stored in plain text. For security reasons fill it in just before the deployment. If the password is entered, it must match the entry in the field Confirm Password. 6. Common Network Information There are two options: Using DHCP Under Manual Network Configuration you can configure individual network parameters: Network Gateway (mandatory), IP Mask (mandatory), Domain Name (mandatory), DNS Server (mandatory). 7. Save Profile Summarizes the configuration. Click the Finish button to store the new profile in the Profile Management Service. FUJITSU Software ServerView Suite 39

40 5.3 IPMI configuration 5.3 IPMI configuration The user name and password for IPMI configuration must be configured in vcenter Server to perform certain operations: ESXi host: Be careful when editing the credential information. If invalid credentials are entered, it may take a few minutes before you see an error message. If the IPMI is configured and the wrong credentials are entered, the configuration will take place no change. The IPMI credentials (user name and password) must be configured to have access to a number of irmc based actions on an ESXi host: Toggle Identify LED Start the irmc Web Interface with single sign on Start the Remote Console (AVR) Start a System Report Start an elcm Offline Update Workflow In addition, when the credentials are configured, it is possible to view monitoring data from the system over IPMI which can be useful if problems with the CIM Provider arise. Procedure: The irmc user account must have the LAN channel privilege of Administrator or OEM to use single sign-on when starting irmc, or to start other IPMI actions from the SV Plug-in. It is possible, however, to limit the irmc privileges depending on the role of the current vcenter user. For more information see "Starting irmc functions with/without single sign-on" on page Log in to vcenter Server using the vsphere Web Client (see "Log in to vcenter Server using the vsphere Web Client" on page 31). 2. Start the FUJITSU PRIMERGY Action Configure IPMI (for an ESXi host see: "Starting a FUJITSU PRIMERGY Action" on page 63). 3. Click the item/icon IPMI Configuration. The following dialog is displayed: FUJITSU Software ServerView Suite 40

41 5.4 FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on Figure 12: IPMI configuration dialog of the SV Plug-in (example for an ESXi host) 4. Enter Login and Password. 5. Click Configure to send and store the user credentials in vcenter Server. Once this user information is stored in vcenter Server, you only have to do this in the case of changes (e.g. if the credentials have been changed on the host). 5.4 FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on Four new role definitions have been added to the SV Plug-in. They are designed for using single sign-on when starting the irmc Web Interface and remote console (AVR). All role definitions contain the system privileges as well as the privilege Host.CIM.CIM Interaction, which is needed to operate the SV Plug-in itself. For more information see "FUJITSU PRIMERGY vcenter role definitions" on page 42. It is possible to add the extended irmc privileges to a FUJITSU PRIMERGY vcenter role definition, see "Starting irmc functions with/without single sign-on" on page 43. You can also use the FUJITSU PRIMERGY vcenter role definitions to limit irmc functionality, see "Examples of using role definitions to limit irmc functionality" on page 46. The Role Definitions sub-tab of the Plug-in Definitions view on the home page of the SV Plug-in (see "Role Definitions" on page 56) lists the predefined FUJITSU PRIMERGY roles. If the role definitions have been reconfigured after installation, the changes relevant to correct processing of the SV Plug-in will be marked. FUJITSU Software ServerView Suite 41

42 5.4 FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on FUJITSU PRIMERGY vcenter role definitions Four new role definitions have been added to the SV Plug-in: FUJITSU PRIMERGY Plug-in Administrator Contains all the privileges needed to start the irmc Web Interface and AVR using single sign-on with the irmc LAN channel privilege level of Administrator. The user can also change the configuration for alarms. FUJITSU PRIMERGY Plug-in Super Operator Contains a subset of the SV Plug-in Administrator privileges that are needed to start the irmc Web Interface using single sign-on with the irmc LAN channel privilege of Operator, plus the extended irmc privileges ConfigureBMC, RemoteStorage and AVR. The user can make some configuration changes (but, for example, no firmware changes). The user can also acknowledge alarms. The user can start AVR from within the irmc Web Interface. FUJITSU PRIMERGY Plug-in Operator Contains only the privileges need to start the irmc Web Interface using single sign-on with the irmc LAN channel privilege of Operator, plus the extended irmc privilege AVR. The user will be able to perform shutdown/reboot on the host, but cannot make any configuration changes. The user can also acknowledge alarms. The user can start AVR from within the irmc Web Interface. FUJITSU PRIMERGY Plug-in Monitor Contains only the privileges need to start the irmc Web Interface using single sign-on with the irmc LAN channel privilege of User, plus the extended irmc privilege AVR. The user can start AVR from within the irmc Web Interface Changing privileges of a role definition The Role Definitions sub-tab of the Plug-in Definitions view on the home page of the SV Plug-in lists the predefined FUJITSU PRIMERGY role definitions, which are generated during the installation process (see "Role Definitions" on page 56). If the role definitions have been reconfigured after installation, the changes relevant to correct processing of the SV Plug-in will be marked. Configuring the FUJITSU PRIMERGY role definitions To change the privileges in one of these role definitions, use the vsphere Web Client user interface. FUJITSU Software ServerView Suite 42

43 5.4 FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on If you need to change the privileges in one of the FUJITSU PRIMERGY role definitions, clone the role and change the privileges in the clone. If you update the SV Plug-in version, or connect the vcenter to another SVvCenter Service, the role definitions will be overwritten! 1. In the object navigator of the vsphere Web Client, select the item Administration. 2. Select the sub-item Roles. 3. Select a vcenter server system from the drop-down menu. 4. Select a role and click Edit role action. 5. Select privileges for the role. 6. Click OK Starting irmc functions with/without single sign-on Single sign-on can be used when starting the irmc functions as Administrator. If the host has an irmc S4 firmware version which is at least V7.73F, the SSO environment is enhanced to allow single sign-on for less-privileged users. When starting the irmc Web Interface, their irmc LAN channel privilege will be adjusted to match the privilege level of the vcenter user Requirements for single sign-on To perform the irmc functions with single sign-on, the following requirements must be met: The IPMI credentials must be configured with an irmc user account that has the Administrator / OEM LAN channel privilege (see "IPMI configuration" on page 40). The vcenter user must have the privileges defined in the FUJITSU PRIMERGY role definitions. The SV Plug-in role Administrator can perform single sign-on, but lessprivileged users will only be able to use single sign-on with an irmc S4 whose firmware version is at least V7.73F irmc functions with single sign-on Location button LED If the IPMI credentials have been configured (see "IPMI configuration" on page 40), any vcenter user can toggle the location button LED on/off. Remote console (AVR) To start AVR directly with single sign-on, the vcenter user must have the privileges defined in the FUJITSU PRIMERGY Plug-in Administrator role (see "FUJITSU PRIMERGY vcenter role FUJITSU Software ServerView Suite 43

44 5.4 FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on definitions" on page 42); however, AVR can be started by any user from within the irmc Web Interface. irmc Web Interface If the vcenter user has the privileges defined in the FUJITSU PRIMERGY Plug-in Administrator role (see "FUJITSU PRIMERGY vcenter role definitions" on page 42), they will be able to start irmc with single sign-on. In all other cases, irmc can be started via login by the irmc user irmc S4 Web Interface SSO enhancements If a host has an irmc S4 with a firmware version of at least V7.73F, single sign-on access will be extended to the vcenter users with the Super Operator, Operator and Monitor roles. The irmc S4 Web Interface can be started with one of three irmc roles: Administrator Operator User irmc extended privileges irmc also offers four extended privileges which can be granted together with the roles: ConfigureBMC - perform system configuration on the host AVR - start AVR (Advanced Video Redirection) ConfigureUsers - configure user accounts (irmc, CAS, LDAP) RemoteStorage - perform remote image and media operations These extended privileges can be used together with the irmc roles. All users can start AVR from within the irmc Web Interface. Since the ConfigureBMC privileges allow extensive access to irmc configuration functionality, it is recommended to use the predefined SV Plug-in Super Operator role (see "FUJITSU PRIMERGY vcenter role definitions" on page 42). The RemoteStorage and ConfigureUsers privileges map to just one vcenter privilege: RemoteStorage : Host.Config.Storage ConfigureUsers : Host.Local.ManageUserGroups So they can be easily added to a SV Plug-in Operator or Monitor role (see "Examples of using role definitions to limit irmc functionality" on page 46. Correlation between the FUJITSU PRIMERGY SV Plug-in roles and irmc S4 Web Interface functionality The following table shows the correlation between the FUJITSU PRIMERGY SV Plug-in role definitions and irmc S4 Web Interface functionality: FUJITSU Software ServerView Suite 44

45 5.4 FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on Predefined FUJITSU PRIMERGY vcenter role definition FUJITSU PRIMERGY Plug-in Administrator FUJITSU PRIMERGY Plug-in Super Operator FUJITSU PRIMERGY Plug-in Operator irmc LAN channel privilege Administrator Operator + ConfigureBMC RemoteStorage AVR Operator + RemoteStorage AVR irmc Web Interface functionality Can perform all functions of the irmc Web Interface View settings and information Toggle location button LED on/off Perform system shutdown/reboot Remote image mount Configure media options Configure system settings RAID configuration Prime Collect AIS Connect System report BIOS backup and update irmc reboot and update Internal event log view/clear Configure users Start AVR View settings and information Toggle location button LED on/off Perform system shutdown/reboot Remote image mount Configure media options Configure system settings Start AVR View settings and information Toggle location button LED on/off Perform system shutdown/reboot Remote image mount Configure media options Start AVR FUJITSU Software ServerView Suite 45

46 5.4 FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on Predefined FUJITSU PRIMERGY vcenter role definition FUJITSU PRIMERGY Plug-in Monitor irmc LAN channel privilege User + AVR irmc Web Interface functionality View limited set of settings and information Toggle location button LED on/off Start AVR Examples of using role definitions to limit irmc functionality In this example, a FUJITSU PRIMERGY SV Plug-in user Monitor is given limited access to the irmc with single sign-on. The administrator might wish to create a user with very limited privileges. The user should be able to start the irmc Web Interface with the LAN channel privilege of User, but not make any changes on the system or perform a system shutdown. 1. A user is created (for example monitor). 2. The target (vcenter, cluster or single host) is configured to have the permission: user: monitor role: FUJITSU PRIMERGY Plug-in Monitor vcenter user "monitor" and irmc access without SSO (irmc S2, S3, S4) Situation: When the user logs in, they can start the irmc Web Interface, but must log in using an irmc user name and password. They will have the LAN channel privileges corresponding to that account. The IPMI credentials will not be used. FUJITSU Software ServerView Suite 46

47 5.4 FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on vsphere Web Client: User without SSO privileges (and irmc firmware version below V7.73F) or no IPMI credentials configured. Figure 13: Example: vcenter user "monitor" and irmc access without SSO - vsphere Web Client SV Plug-in: Figure 14: Example: vcenter user "monitor" and irmc access without SSO - SV Plug-in vcenter user "monitor" and irmc access with SSO as irmc user "User" Situation: To provide SSO access for a Super Operator, Operator or Monitor vcenter user, a host must have an irmc S4 with a firmware version of at least V7.73F. The IPMI credentials must be configured with an irmc user who has the LAN channel privilege of Administrator / OEM (see "Starting irmc functions with/without single sign-on" on page 43), e.g. admin / admin. When the user logs in, they will be able to start the irmc Web Interface with SSO but they only have the LAN channel privileges of user. vsphere Web Client: The figure below shows the view for a vcenter user with the FUJITSU PRIMERGY Plug-in Monitor role, IPMI credentials are configured (admin / admin) and the host has a new version of irmc firmware which is at least V7.72F. FUJITSU Software ServerView Suite 47

48 5.4 FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on Figure 15: Example: vcenter user "monitor" and irmc access with SSO as irmc user "User" - vsphere Web Client SV Plug-in: The figure below shows the irmc Web Interface with the user admin logged in but with the LAN channel privilege user. The user admin can only perform actions that are allowed for a user (e.g. Toggle location button LED) but cannot perform system shutdowns or configure the system in any way. Figure 16: Example: vcenter user "monitor" and irmc access with SSO as irmc user "user" - SV Plug-in vcenter user "monitor2" and irmc "User" access and extended privilege "RemoteStorage" Situation: In this example, the vcenter administrator will create a user monitor2. This user should be able to start irmc S4 with SSO as the irmc user User, but also be able to mount a remote image. In this case it is necessary to grant the role more privileges than are predefined. FUJITSU Software ServerView Suite 48

49 5.4 FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on If you need to change the privileges in one of the FUJITSU PRIMERGY role definitions, clone the role and change the privileges in the clone. If you update the SV Plug-in version, or connect the vcenter to another SVvCenter Service, the role definitions will be overwritten! The vcenter administrator must perform the following: 1. Updating the firmware of the irmc S4 to at least V7.73F. 2. Configuring IPMI credentials with a user account that has the LAN channel privilege of administrator or OEM. 3. In the object navigator of the vsphere Web Client under Administration - Roles: a. Choosing the FUJITSU PRIMERGY Plug-in Monitor role and cloning this role. b. Renaming this clone PluginMonitorPlusStorage. c. Adding the privilege Host->Configuration->Storage Partition Configuration to the FUJITSU PRIMERGY Plug-in Monitor role. d. Saving the FUJITSU PRIMERGY Plug-in Monitor role. 4. Creating a new vcenter user named monitor2. 5. Navigating to the vcenter or host for which the user is to have this functionality: a. Selecting All vcenteractions - Add Permission in the context menu. b. Selecting the user monitor2 and assigning the role PluginMonitorPlusStorage. vsphere Web Client: Logged in as monitor2, the user can navigate to the SV Plug-in view for the host and start the irmc Web Interface: Figure 17: vcenter user "monitor2" and irmc "User" access and extended privilege "RemoteStorage" - vsphere Web Client FUJITSU Software ServerView Suite 49

50 5.4 FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on SV Plug-in: The user is logged in as the irmc administrator admin, but only with the LAN channel privilege of User. But they can also perform remote storage actions: Figure 18: Example: vcenter user "monitor2" and irmc "User" access and extended privilege "RemoteStorage" - SV Plug-in FUJITSU Software ServerView Suite 50

51 6.1 Entry point 6 SV Plug-in getting started and summary The SV Plug-in home page FUJITSU PRIMERGY starts with a Getting Started view. The links under the navigator tree item FUJITSU PRIMERGY offer the views of the SV Plug-in home page. The FUJITSU PRIMERGY Summary view gives an overview of the information items provided by the SV Plug-in. There is also a Plug-in Definitions view, which lists all FUJITSU PRIMERGY events and shows the FUJITSU PRIMERGY alarms and the role definitions that can be used to assign permissions to an entity (see "FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on" on page 41). 6.1 Entry point On the Home page of the vsphere Web Client you will find two links: In the object navigator of the vsphere Web Client the link FUJITSU PRIMERGY. In the main workspace of the vsphere Web Client the link FUJITSU ServerView Suite. Both links lead to the Getting Started view on the home page of the SV Plug-in. Figure 19: Links to the Getting Started view on the home page of the SV Plug-in FUJITSU Software ServerView Suite 51

52 6.2 Views on the home page of the SV Plug-in 6.2 Views on the home page of the SV Plug-in The home page of the SV Plug-in contains the following views: Getting Started The Getting Started view on the home page of the SV Plug-in gives general information about the SV Plug-in (see "Getting Started view" on page 52). Summary The Summary view on the home page gives an overview of the information items provided by the SV Plug-in (see "Summary view" on page 53). Plug-in Definitions The Plug-in Definitions view on the home page of the SV Plug-in offers several subtabs, among them Event Definitions, Alarm Definitions and Role Definitions. The Event Definitions sub-tab of the Plug-in Definitions view on the home page of the SV Plug-in lists the event definitions that are set by the SV Plug-in (see "Event Definitions" on page 54). The Alarm Definitions sub-tab of the Plug-in Definitions view on the home page of the SV Plug-in lists the predefined FUJITSU PRIMERGY alarms (see "Alarm Definitions" on page 55). The Role Definitions sub-tab of the Plug-in Definitions view on the home page of the SV Plug-in lists the role definitions that can be used to assign permissions to an entity (see "Role Definitions" on page 56 and "FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on" on page 41). 6.3 Getting Started view 1. In the object navigator of the vsphere Web Client select the item FUJITSU PRIMERGY. The Getting Started view on the home page of the SV Plug-in opens. The Getting Started view on the home page of the SV Plug-in gives general information about the SV Plug-in. At the bottom of the getting-started page of the SV Plug-in, you will find several links, including: View the Summary of Blade and PRIMEQUEST Servers and other plug-in components Links to the Summary view (see "Summary view" on page 53). Manage Event, Alarm and Role Descriptions Links to the Plug-in Definitions view (see "Plug-in Definitions view" on page 54). FUJITSU Software ServerView Suite 52

53 6.4 Summary view Manage the ServerView vcenter Services Links to the SVvCenter Service Configuration Overview view (see "Integration in the event management of the vsphere Web Client" on page 103 and "SVvCenter Service for PRIMEQUEST systems" on page 92). Manage ServerView Profiles for Deployment Links to the ServerView Profile Management overview (see "Opening the ServerView Profile Management Overview" on page 36). ServerView Plug-in Manual Links to the online version of the user guide FUJITSU Software ServerView Plug-in for VMware vcenter. 6.4 Summary view 1. In the object navigator of the vsphere Web Client select the item FUJITSU PRIMERGY - Summary. The Summary view on the home page of the SV Plug-in opens. The Summary view on the home page gives an overview of the information items provided by the SV Plug-in: Figure 20: Summary view on the home page of the SV Plug-in MMB Views An overview of all PRIMERGY blade servers discovered by the SVvCenter Service. You can also see the status of the hosts of the PRIMERGY blade servers. 1. Click the title of an item box to open the view with detailed information about this FUJITSU Software ServerView Suite 53

54 6.5 Plug-in Definitions view MMB node (see "SV Plug-in information of an MMB node" on page 81). PRIMEQUEST Views An overview of all PRIMEQUEST systems discovered by the SVvCenter Service. You can also see the status of the partitions of the PRIMEQUEST systems. 1. Click the title of an item box to open the view with detailed information about this PRIMEQUEST system (see "SV Plug-in information of a PRIMEQUEST system" on page 89). Cluster Views An overview of all clusters discovered by the SVvCenter Service. You can also see the status of the hosts of the clusters. 1. Click the title of an item box to open the view with detailed information about this cluster (see "Monitoring vcenter or cluster host servers" on page 71). vcenter Views An overview of all vcenters discovered by the SVvCenter Service. You can also see the status of the hosts of the vcenters. 1. Click the title of an item box to open the view with detailed information about this vcenter (see "Monitoring vcenter or cluster host servers" on page 71). SVvCenter Services An overview of all SVvCenter Services that are available. You can also see the status of the hosts of the SVvCenter Services. 1. Click the title of an item box to open the view with detailed information about this SVvCenter Service (see "Properties of SVvCenter Services" on page 105). 6.5 Plug-in Definitions view 1. In the object navigator of the vsphere Web Client select the item FUJITSU PRIMERGY - Plug-in Definitions. The Plug-in Definitions view on the home page of the SV Plug-in opens. The Plug-in Definitions view on the home page of the SV Plug-in offers several sub-tabs, among them Event Definitions, Alarm Definitions and Role Definitions Event Definitions The Event Definitions sub-tab of the Plug-in Definitions view on the home page of the SV Plug-in lists the event definitions that are set by the SV Plug-in. If you have more than one FUJITSU Software ServerView Suite 54

55 6.5 Plug-in Definitions view vcenter in your environment, you can choose which vcenter you would like to view the definitions for under Providers. If the hosts are monitored by the SVvCenter Service, these indications will be forwarded to the vcenter event management (see "Integration in the event management of the vsphere Web Client" on page 103). The SVvCenter Service also listens to SNMP traps sent by registered MMBs (see "SVvCenter Service for MMBs" on page 85) and PRIMEQUEST systems (see "SVvCenter Service for PRIMEQUEST systems" on page 92). Figure 21: Event Definitions in the Plug-in Definitions view on the home page of the SV Plug-in The general list in this tab has the columns Event Type, Monitor Type and Description and can be sorted according to these items. More information on the selected list entry is displayed on the right Alarm Definitions The Alarm Definitions sub-tab of the Plug-in Definitions view on the home page of the SV Plug-in lists the predefined FUJITSU PRIMERGY alarms. If you have more than one vcenter in your environment, you can choose which vcenter you would like to view the definitions for under Providers. FUJITSU Software ServerView Suite 55

56 6.5 Plug-in Definitions view Figure 22: Alarm Definitions in the Plug-in Definitions view on the home page of the SV Plug-in The new alarm definitions help you to define specific alarm actions depending on the target type (Host, MMB, PRIMEQUEST) of the event. After a new or update installation of the SV Plug-in any changes made to an alarm (for example actions) will be lost. You must reconfigure the action as needed. There is also a test alarm which you can use to test the event/alarm handling in general. This will be triggered from a test event. All of these new definitions have no actions and are disabled. To use them you must enable them, and possibly configure an action for each. The Defined In field gives you the name of the vcenter in which this alarm is defined. This name forms a link to the Alarm Manager of the vcenter: 1. To open the Alarm Manager of the vcenter in which an alarm is defined, click the name of the vcenter in the Defined In field Role Definitions The Role Definitions sub-tab of the Plug-in Definitions view on the home page of the SV Plug-in lists the predefined FUJITSU PRIMERGY roles. If you have more than one vcenter in your environment, you can choose which vcenter you would like to view the definitions for under Providers. This view shows the FUJITSU PRIMERGY vcenter role definitions that are generated during the installation process. They describe the minimum privilege level to perform SV Plug-in actions and can be used to assign permissions to an entity. For more information see "FUJITSU PRIMERGY vcenter role definitions" on page 42. FUJITSU Software ServerView Suite 56

57 6.5 Plug-in Definitions view For more information about the concept and about using these role definitions to limit irmc functionality, see "FUJITSU PRIMERGY vcenter role definitions and irmc single signon" on page 41. Figure 23: Role Definitions in the Plug-in Definitions view on the home page of the SV Plug-in The Defined For field gives you the name of the vcenter (cluster, host), to which this role definition is assigned. You can also see the user to whom the role definition has been assigned. If the role definitions have been reconfigured after installation, the changes relevant to correct processing of the SV Plug-in will be marked as follows: * This privilege was not predefined and has been added after installation. It is not required for correct processing of the SV Plug-in. *** (in red) This privilege is missing. It has been removed since installation and must be added again for correct processing of the SV Plug-in. FUJITSU Software ServerView Suite 57

58 7 Monitoring ESXi-based hosts The SV Plug-in offers various options for monitoring ESXi-based hosts: Information on the selected host Status icons provide quick information and detailed views provide more information - see "Information on the selected host - Status items and views" on page 60. In regular operation the SV Plug-in generally shows the values of a host system provided by the ServerView ESXi CIM Provider. If a host has an older version of the ServerView ESXi CIM Provider, storage values are provided by the LSI CIM provider (see "Storage view" on page 66). It is also possible to monitor most of the storage values via IPMI, if the IPMI credentials are configured. See "Agentless management via IPMI" on page 62. Via IPMI not all the values are available. You can toggle between CIM and IPMI communication interfaces. For further information see "Agentless management via IPMI" on page 62. FUJITSU PRIMERGY actions A number of action items support calling a monitoring tool or making settings on the host - see "FUJITSU PRIMERGY Actions (irmc-based operations)" on page 63. If a remote console (AVR) or the irmc Web Interface is started, the SV Plug-in will consider the privileges of the current user - see "Starting irmc functions with/without single signon" on page 43. Integration in event management of the vsphere Web Client The SV Plug-in includes the SVvCenter Service, which routes FUJITSU PRIMERGY-specific events to the vcenter event management to be monitored in the vsphere Web Client (see "Integration in the event management of the vsphere Web Client" on page 103). Managing a selected host by starting an elcm Offline Update An offline update extends the autonomous update capabilities of the irmc S4. System components such as network or storage controller firmware can be updated using the offline update mode. The SV Plug-in allows you to start an offline update via elcm on a host (see "Offline update via elcm" on page 112). FUJITSU Software ServerView Suite 58

59 7.1 Access to the SV Plug-in information of an ESXi-based host 7.1 Access to the SV Plug-in information of an ESXi-based host 1. In the object navigator of the vsphere Web Client, select vcenter Inventory Lists. 2. Under Resources select Hosts. 3. Select the desired host. If the desired host is an CX host, you will find further information in "Monitoring CX hosts" on page Click the Monitor tab. The Monitor tab is displayed, with a set of second-level tabs at the top. One of these second-level tabs is FUJITSU PRIMERGY, which opens the views of the SV Plug-in. The FUJITSU PRIMERGY second-level tab is only available if two conditions are met: The vendor of the selected host is Fujitsu. The version of the ESXi operating system is at least V Click the FUJITSU PRIMERGY sub-tab to display the interface of the SV Plug-in. 7.2 SV Plug-in information of an ESXi-based host Figure 24: SV Plug-in information of an ESXi host FUJITSU Software ServerView Suite 59

60 7.2 SV Plug-in information of an ESXi-based host Information on the selected host - Status items and views Time of data acquisition: If the SV Plug-in is called, it will retrieve the data of the ServerView ESXi CIM Provider on the host. Whenever you click the status item tree, the SV Plug-in retrieves the data of the ServerView ESXi CIM Provider again. If you click the Refresh icon of vsphere, a new data retrieval cycle will be initiated. In regular operation the SV Plug-in generally shows the values of a host system provided by the ServerView ESXi CIM Provider. If a host has an older version of the ServerView ESXi CIM Provider, storage values are provided by the LSI CIM provider (see "Storage view" on page 66). It is also possible to monitor most of the storage values via IPMI, if the IPMI credentials are configured. See "Agentless management via IPMI" on page 62. Via IPMI not all the values are available. You can toggle between CIM and IPMI communication interfaces. For further information see "Agentless management via IPMI" on page 62. In the main workspace, on the left of the SV Plug-in view, you will find a status item tree: 1. Clicking an item provides detailed information to the right of the status item tree. Each item is preceded by a status icon: ok degraded error not present If you click this item, no information will be shown to the right of the status item tree. unknown retrieving data You can collapse or expand the status item tree to allow more/less space for detailed information on the right. The detailed information on the right is displayed in tables. You can change the column widths and sort the columns as needed. Status items and views With the ServerView ESXi CIM Provider V6.31, some new values are available (marked SVCIMp in the following). FUJITSU Software ServerView Suite 60

61 7.2 SV Plug-in information of an ESXi-based host For some components the new value CSS (customer self-service) may be shown. These are components that can be replaced by the customer themselves in the case of an error. Information Fans General information about the host: System Name, Model, UUID, Serial Number, Asset Tag, BIOS Version, CIM Provider Version, irmc Firmware Version, Operating System Version, Image Profile, Total Memory Information about the fans installed on the system: Status, Designation, Current Speed, Maximum Speed (SVCIMp< V6.31), Nominal Speed (SVCIMp< V6.31), Fail Reaction, Shutdown Delay, State, Quality (Current Speed / Nominal Speed) (SVCIMp >=V6.31), CSS (SVCIMp >=V6.31) Temperature Power Information about the fans is not available if you have selected a blade. For information about the fans of an MMB node, see "SV Plug-in information of an MMB node" on page 81. Detailed information about the temperature sensors installed on the system: Status, Designation, Temperature, Warning Level, Critical Level, Fail Reaction, State Information about the power supplies installed in the system: Status, Designation, State, Product Name (SVCIMp >=V6.31), CSS (SVCIMp >=V6.31) Processors Information about the power supplies is not available if you have selected a blade. For information about the power supplies of an MMB node, see "SV Plugin information of an MMB node" on page 81. Detailed information about the system processor configuration: Status, Designation, Frequency (MHz), Manufacturer, Type, L1 Cache, L2 Cache, L3 Cache, Enabled Cores, Cores, Logical Threads, State, CSS (SVCIMp >=V6.31) Memory Detailed information about the memory modules installed in the system: Status, Designation, Type, Size, Frequency (MHz), State, Maximum Frequency (SVCIMp >=V6.31), Voltage (SVCIMp >=V6.31), CSS (SVCIMp >=V6.31), Manufacturer (SVCIMp >=V6.31), Serial Number (SVCIMp >=V6.31) FUJITSU Software ServerView Suite 61

62 7.2 SV Plug-in information of an ESXi-based host Storage Overview of the RAID controllers found and details of their logical drives and physical disks (see "Storage view" on page 66). Driver Monitor Overview of the components of a host as well as of the associated events contained in the OS event log on the managed server (see "Driver Monitor view" on page 68). Network Information about the network interfaces configured on the system: Name, Address Type (primary or irmc), IP Address, MAC Address Watchdogs If a component is not accessible, there is no status information available for it. Information about the watchdogs configured on the system: Type, Active, Action, Timeout System Event Log If a component is not accessible, there is no status information available for it. A list of the entries found in the System Event Log together with cause/resolution information. The ServerView ESXi CIM Provider V6.31 or later supports the System Event Log view. The entries will be retrieved automatically via CIM. If the version of the ServerView ESXi CIM Provider is older than 6.31, you will need to configure the IPMI credentials (see "IPMI configuration" on page 40) to retrieve the System Event Log entries from the host Agentless management via IPMI It is also possible to monitor most of the storage values via IPMI, if the IPMI credentials are configured, see "IPMI configuration" on page 40. In particular the following views change: Driver Monitor view The Driver Monitor view isn t available via IPMI. Storage view Via IPMI the Storage view offers a list of the physical disks and their status. Via IPMI not all the values are available. FUJITSU Software ServerView Suite 62

63 7.2 SV Plug-in information of an ESXi-based host Toggle between CIM and IPMI In the main workspace, on the left of the SV Plug-in view, you will find the status item tree (see "Information on the selected host - Status items and views" on page 60). On the left, above the status item tree, two icons are displayed: The CIM communication interfaces are in use. 1. Click this icon to toggle to using the IPMI communication interfaces. The IPMI communication interfaces are in use. 1. Click this icon to toggle to using the CIM communication interfaces FUJITSU PRIMERGY Actions (irmc-based operations) The SV Plug-in offers some FUJITSU PRIMERGY Actions depending on the capabilities of the selected host. The IPMI credentials (user name and password) must be configured to have access to a number of irmc based actions on an ESXi host: Toggle Identify LED Start the irmc Web Interface with single sign on Start the Remote Console (AVR) Start a System Report Start an elcm Offline Update Workflow In addition, when the credentials are configured, it is possible to view monitoring data from the system over IPMI which can be useful if problems with the CIM Provider arise. These IPMI-based actions are always enabled in the context menu, even if the credentials are not configured or the user does not have the privilege to perform the action. In this case an error message will be shown if the action is started. For how to configure the user name and password for IPMI configuration, see "IPMI configuration" on page Starting a FUJITSU PRIMERGY Action There are two ways to start one of these FUJITSU PRIMERGY Actions: FUJITSU Software ServerView Suite 63

64 7.2 SV Plug-in information of an ESXi-based host In the top left of the SV Plug-in interface in the main workspace, up to ten icons are displayed. The FUJITSU PRIMERGY Actions can be started independently of the SV Plug-in interface: 1. In the center pane of the vsphere Web Client, select the desired host in the inventory tree. 2. In the Actions menu you will find the submenu FUJITSU PRIMERGY. This submenu offers the irmc Actions submenu and the Event Actions submenu. Figure 25: Submenus for FUJITSU PRIMERGY Actions The Start MMB Management GUI action is only available as an icon in the top left The FUJITSU PRIMERGY Actions Refresh 1. Click this icon to refresh the current view of the SV Plug-in. This Refresh function only refreshes the views/information of the SV Plug-in - not of the vsphere Web Client. Consequently, this function is only available among the icons in the top left of the SV Plug-in interface - not in the Actions menu. Configure IPMI Click this icon to start the IPMI configuration dialog (see "IPMI configuration" on page 40). Toggle Identify LED 1. Click this icon to toggle the Locate LED between on and off: Locate icon is blue: locate LED is on. Locate icon is gray: locate LED is off. The icon is displayed if an irmc address is available. FUJITSU Software ServerView Suite 64

65 7.2 SV Plug-in information of an ESXi-based host Start irmc 1. Click this icon to launch the irmc Web interface in a new window. The icon is displayed if an irmc address is available. See "Starting irmc functions with/without single sign-on" on page 43. Start Remote Console 1. Click this icon to launch a remote console (AVR) in a new window. The icon is displayed if an irmc address is available. See "Starting irmc functions with/without single sign-on" on page 43. Start a System Report 1. Click this icon to start an irmc system report in a new window. See "irmc system report" on page 111. Start an elcm Offline Update Workflow 1. Click this icon to start the ServerView elcm Offline Update Workflow via irmc (S4) directly for a host. The ServerView elcm Offline Update Workflow is part of the FUJITSU Software ServerView Plug-in for VMware vrealize Orchestrator elcm Offline Update package. See "Offline update via elcm" on page 112. Toggle FUJITSU Event Monitoring 1. Click this icon to turn the subscription of the host to the SVvCenter Service on/off (see "Integration in the event management of the vsphere Web Client" on page 103). This action is depicted in four ways, depending on the current subscription status: The host is subscribed to the SVvCenter Service. Events will be monitored by the SVvCenter Service and forwarded. The host is not subscribed to the SVvCenter Service. No events will be monitored by the SVvCenter Service or forwarded. The subcription status of the host is unknown due to connection problems with the SVvCenter Service. No action will be performed. The host cannot be subscribed, because the vcenter is not connected to the SVvCenter Service. No action will be performed. Invoke Test Event 1. Click this icon to request the host to send a test event (see "Integration in the event management of the vsphere Web Client" on page 103). FUJITSU Software ServerView Suite 65

66 7.3 Storage view Export Data Click this icon to open a frame where you can choose data to be exported (host information and System Event Log information). If you choose all System Event Log entries, the retrieval of data will take some time. There is a Cancel button to leave this frame without action. As long as the export process is running, it cannot be stopped and the buttons are locked. When the requested data has been retrieved, a new window opens showing the requested data - with the option to save it to a file. The icon is displayed if an irmc address is available. 7.3 Storage view The Storage view offers an overview of the RAID controllers found on the host and details of their logical drives and physical disks. In regular operation the SV Plug-in generally shows the values of a host system provided by the ServerView ESXi CIM Provider. If a host has an older version of the ServerView ESXi CIM Provider, storage values are provided by the LSI CIM provider (see "Prerequisites - information provider for the Storage view" on page 66). It is also possible to monitor most of the storage values via IPMI, if the IPMI credentials are configured. You can toggle between CIM and IPMI communication interfaces. Via IPMI the Storage view offers a list of the physical disks and their status. Via IPMI not all the values are available. See "Agentless management via IPMI" on page Prerequisites - information provider for the Storage view To ensure the optimum supply of RAID information it is recommended to install on the host: ServerView ESXi CIM Provider V8.0 or higher ServerView RAID Core Provider Information provider for the Storage view The information shown in the Storage view is provided either from the ServerView ESXi CIM Provider or from the LSI CIM provider depending on the version of the ServerView ESXi CIM Provider. FUJITSU Software ServerView Suite 66

67 7.3 Storage view ServerView ESXi CIM Provider V8.0 or higher and the ServerView RAID Core Provider are installed: The information comes from ServerView ESXi CIM Provider, and you will see an above the Storage Details list on the right side. icon 1. Click the icon above the Storage Details list on the right side to gather information from the Device Control Tree. You can save the gathered information to a JSON file. ServerView ESXi CIM Provider of a lower version is installed: The information comes from the LSI CIM provider Information on the Storage view Storage Details Overview of the RAID controllers found. This information includes: Status of the controller shown as an icon, name of the controller, SAS ports to which the controller is connected, number of physical disks attached to the controller, number of logical drives configured on the controller, status of the BBU if available, textual status of the controller. The entry for a controller can be expanded to view details about the controller as well as its logical drives and physical disks: 1. Click the arrow in front of a controller entry to get more detailed information. An expanded controller entry is displayed. There are three tabs, the Controller tab is opened: Figure 26: Storage view of the SV Plug-in - expanded controller entry, Controller tab FUJITSU Software ServerView Suite 67

68 7.4 Driver Monitor view Storage Details - Controller tab Information shown here includes: Vendor, protocol, memory size, firmware package version, firmware version, BIOS version, driver version, patrol read iterations, vendor/device ID, subvendor/device ID, PCI bus/device/function numbers, number and status of the logical drives (can be expanded), number and status of the physical drives (can be expanded). Logical Drives tab 1. Click the Logical Drives tab in an expanded controller entry view (Storage Details view). An overview of the logical drives of the selected controller is displayed. The information shown includes: Status of the drive depicted as an icon, name of the drive, RAID level of the drive, logical size of the drive in MB, number of physical disks configured to this drive, textual status of the drive. Logical Drives - details 1. Click the arrow in front of a logical drive entry to get more detailed information. The information shown includes: Stripe size in KB, read mode, write mode, disk cache mode, number and status of the configured physical disks (can be expanded). Physical Disks - overview 1. Click the Physical Disks tab in an expanded controller entry view (Storage Details view). An overview of the physical disks of the selected controller is displayed. The information shown includes: Vendor, model, serial number, firmware version, SAS address, link speed (GB/s), number and status of the logical drives that have configured this disk (can be expanded if more than one logical drive uses this disk). 7.4 Driver Monitor view The Driver Monitor view isn t available via IPMI. Via the Driver Monitor view you can monitor and manage events relating to the components of a monitored host, as listed in the OS event log on the monitored host. FUJITSU Software ServerView Suite 68

69 7.4 Driver Monitor view Figure 27: Driver Monitor view of the SV Plug-in Requirements ServerView ESXi CIM Provider V or later must be installed on the ESXi-based host. The ESXi-based host has to be subscribed. Managing the events In regular operation the Driver Monitor view shows the events of a selected component. Expand the information You can call further information about a component, such as slot, driver or PCI information. Show all 1. Click the arrow in front of a component entry to get more detailed information. You can call all Driver Monitor events relating to the components of a monitored host, as listed in the OS event log on the monitored host. 1. Click the check box Show all on the right, in the line of the table heading Logs. Acknowledge If a component has the status Warning or Error, you can confirm this event on the server side and set the status of this component to ok. If a component has the status Warning or Error, the system status and error lamp also indicates Warning or Error. If you click the button Acknowledge, the system status and error lamp also is turned off. Confirming all events If no component is selected, all events relating to the host will be acknowledged. FUJITSU Software ServerView Suite 69

70 7.5 System Event Log view Confirming the events relating to an individual component If a component is selected, all events relating to this component will be acknowledged. 1. Click the button Acknowledge on the right, in the line of the table heading Components. 7.5 System Event Log view If the version of the ServerView ESXi CIM Provider is older than 6.31, it you will need to configure the IPMI credentials (see "IPMI configuration" on page 40) to retrieve the System Event Log entries from the host. Requirements If ServerView ESXi CIM Provider V6.31 or later is installed on the ESXi-based host: If an irmc address is available, the ServerView ESXi CIM Provider V6.31 or later supports the System Event Log view. The entries will be retrieved via CIM. If a version of ServerView ESXi CIM Provider < 6.31 is installed on the ESXi-based host: If an irmc address is available and the user name and password for IPMI configuration are configured in vcenter Server, you can open this System Event Log view: System Event Log view of the SV Plug-in Figure 28: System Event Log view of the SV Plug-in Choosing the quantity and severity of entries shown A host can have many log entries. Therefore the System Event Log view starts with only the Critical and Major entries showing. 1. If you wish to see entries of other severities, check/uncheck the boxes at the top of the System Event Log Details list: FUJITSU Software ServerView Suite 70

71 7.6 Monitoring vcenter or cluster host servers Displayed information The following information is displayed for each entry: 1. Click the arrow to get more detailed data. These details can contain different information, such as about the cause of the event or helpful information to solve the problem. Not all messages have these details. The severity of the entry is indicated by an icon. Date/Time Date and time either in UTC or local time, depending on the settings seen above the table. Error Code CSS 1. Change these settings as required. Defines the type of the entry. Shows whether this entry relates to a CSS (customer self-service) component. (Message) Details of the message. Column sorting The System Event Log table allows you to sort by multiple columns. 1. Click one column header to sort. Use [Ctrl] and click a second column to sort the table by both columns. The first column cannot be sorted. 7.6 Monitoring vcenter or cluster host servers The SV Plug-in offers lists of the hosts assigned to a vcenter or a cluster. Via this access point the SV Plug-in offers less information on the single host than via the inventory tree item Hosts (see "Monitoring ESXi-based hosts" on page 58), but all FUJITSU PRIMERGY actions are available. FUJITSU Software ServerView Suite 71

72 7.6 Monitoring vcenter or cluster host servers Access to the SV Plug-in information of the hosts of a vcenter/cluster The SV Plug-in information about the hosts of a vcenter or cluster is also displayed if you click the title of an item box of a vcenter/cluster in the Summary tab on the home page of the SV Plug-in (see "Summary view" on page 53). 1. In the object navigator of the vsphere Web Client, select vcenter. 2. Under Inventory Lists select vcenter Servers or Clusters. 3. Select the desired vcenter or cluster. 4. Click the Monitor tab. The Monitor tab is displayed, with a set of second-level tabs at the top. One of these second-level tabs is FUJITSU PRIMERGY, which opens the views of the SV Plug-in. The FUJITSU PRIMERGY second-level tab is only available if two conditions are met: The vendor of the selected host is Fujitsu. The version of the ESXi operating system is at least V5.0. Figure 29: Access to the SV Plug-in information of vcenter servers 5. Click the FUJITSU PRIMERGY sub-tab to display the interface of the SV Plug-in. A list of the hosts found in the vcenter/cluster is shown. The list gives general information about each host of the vcenter/cluster: Status, host name (with a link to the Single System View for the host, if the host is available), SVvCenter Service monitoring status (subscribed/ not subscribed), network address, model, operating system, serial number FUJITSU Software ServerView Suite 72

73 7.6 Monitoring vcenter or cluster host servers Each host name is preceded by a status icon: ok degraded error not present If you click this item, no information will be shown to the right of the status item tree. unknown retrieving data FUJITSU PRIMERGY Actions Action icons The SV Plug-in offers some FUJITSU PRIMERGY Actions, depending on the capabilities of the selected host. In the main workspace of the SV Plug-in interface, you will see the action icons in the top left. Time of data acquisition: If the SV Plug-in is called, it will retrieve the data of the ServerView ESXi CIM Provider on the host. Whenever you click the status item tree, the SV Plug-in retrieves this data again. 1. If you click the Refresh icon of vsphere, a new data retrieval cycle will be initiated. Refresh 1. Click this icon to refresh the current view of the SV Plug-in. This Refresh function only refreshes the views/information of the SV Plug-in - not of the vsphere Web Client. Therefore, this function is only available among the icons in the top left of the SV Plug-in interface - not in the Actions menu. FUJITSU Software ServerView Suite 73

74 7.6 Monitoring vcenter or cluster host servers SVvCenterService Connection 1. Click this icon to start a connection dialog similar to the dialog in the SVvCenter Service Configuration Overview (see "SVvCenter Service configuration" on page 33). If the vcenter is already connected to a SVvCenter Service, you can update the connection or disconnect the vcenter from the SVvCenter Service. If the vcenter is not connected to a SVvCenter Service, you can connect it to a selected SVvCenter Service. Actions This icon will be displayed if a host is selected in the Monitor tab view. 1. Click this icon to open the actions context menu (see "Actions in the context menu" on page 74). Actions in the context menu (For how to open this context menu see "Action icons " on page 73) Configure IPMI Click this icon to start the IPMI configuration dialog (see "IPMI configuration" on page 40). Toggle Identify LED 1. Click this icon to toggle the Locate LED between on and off: Locate icon is blue: locate LED is on. Locate icon is gray: locate LED is off. The icon is displayed if an irmc address is available. Start irmc 1. Click this icon to launch the irmc Web interface in a new window. The icon is displayed if an irmc address is available. See "Starting irmc functions with/without single sign-on" on page 43. Start Remote Console 1. Click this icon to launch a remote console (AVR) in a new window. The icon is displayed if an irmc address is available. See "Starting irmc functions with/without single sign-on" on page 43. FUJITSU Software ServerView Suite 74

75 7.6 Monitoring vcenter or cluster host servers Start a System Report 1. Click this icon to start an irmc system report in a new window. See "irmc system report" on page 111. Start an elcm Offline Update Workflow 1. Click this icon to start the ServerView elcm Offline Update Workflow via irmc (S4) directly for a host. The ServerView elcm Offline Update Workflow is part of the FUJITSU Software ServerView Plug-in for VMware vrealize Orchestrator elcm Offline Update package. See "Offline update via elcm" on page 112. Toggle FUJITSU Event Monitoring 1. Click this icon to turn the subscription of the host to the SVvCenter Service on/off (see "Integration in the event management of the vsphere Web Client" on page 103). This action is depicted in four ways, depending on the current subscription status: The host is subscribed to the SVvCenter Service. Events will be monitored by the SVvCenter Service and forwarded. The host is not subscribed to the SVvCenter Service. No events will be monitored by the SVvCenter Service or forwarded. The subcription status of the host is unknown due to connection problems with the SVvCenter Service. No action will be performed. The host cannot be subscribed, because the vcenter is not connected to the SVvCenter Service. No action will be performed. Invoke Test Event 1. Click this icon to request the host to send a test event (see "Integration in the event management of the vsphere Web Client" on page 103). Export Data Click this icon to open a frame where you can choose data to be exported (host information and System Event Log information). If you choose all System Event Log entries, the retrieval of data will take some time. There is a Cancel button to leave this frame without action. As long as the export process is running, it cannot be stopped and the buttons are locked. When the requested data has been retrieved, a new window opens showing the requested data - with the option to save it to a file. The icon is displayed if an irmc address is available. FUJITSU Software ServerView Suite 75

76 7.6 Monitoring vcenter or cluster host servers Opening the Single System View for a host of a vcenter/cluster The Single System View will be opened if an irmc address is available. 1. Click the host name of the desired host in the list (see "Access to the SV Plug-in information of the hosts of a vcenter/cluster" on page 72). The Single System View of the desired host is opened. FUJITSU Software ServerView Suite 76

77 8.1 Monitoring CX hosts 8 Monitoring FUJITSU PRIMERGY specific nodes 8.1 Monitoring CX hosts Information on the chassis itself is not available as there is no chassis management component in a CX chassis. The following possiblities to monitor a CX host are offered by the SV Plug-in: Related Hosts: The number of adjacent hosts for the selected CX host is shown as Related Hosts (with there corresponding count) - see "Number of adjacent hosts for the selected CX host: Inventory Lists - Related Objects" on page 77. CX chassis support: For a selected CX host the SV Plug-in shows a list of CX host powered on and running ESXi placed in the same chassis - see "Information on adjacent hosts: Related Hosts tab" on page 78. CX hosts in the Inventory Lists The object navigator of the vsphere Web Client shows CX hosts as Hosts in the Inventory Lists. 1. In the object navigator of the vsphere Web Client select vcenter. 2. Under Inventory Lists select Hosts. 3. Select the desired host Number of adjacent hosts for the selected CX host: Inventory Lists - Related Objects 1. Select a CX host - see "Monitoring CX hosts" on page Click the > icon at the end of the selected host entry. FUJITSU Software ServerView Suite 77

78 8.1 Monitoring CX hosts The list of Related Objects is displayed with there corresponding count in the object navigator. The number of adjacent hosts for the selected CX host is shown as Related Hosts. Figure 30: Related Objects of a CX host Information on adjacent hosts: Related Hosts tab For a selected CX host the SV Plug-in shows a list of CX hosts powered on and running ESXi placed in the same chassis. Information on the chassis itself is not available as there is no chassis management component in a CX chassis. 1. Select a CX host - see "Monitoring CX hosts" on page Click the Related Objects tab. The Related Objects tab is displayed, with a set of second-level tabs at the top. 3. Click the Related Hosts sub-tab. Information on adjacent hosts for the selected CX host is displayed as a list on the Related Hosts sub-tab. List of Related Hosts: The list gives following information: Name Name of the host FUJITSU Software ServerView Suite 78

79 8.1 Monitoring CX hosts State Possible values: Connected - Disconnected - Maintenance Mode Status Health state of the host Cluster Name of the cluster if the host is part of a cluster Consumed CPU % Consumed Memory % Uptime FUJITSU Software ServerView Suite 79

80 8.2 Monitoring PRIMERGY blade servers 8.2 Monitoring PRIMERGY blade servers The SV Plug-in adds the inventory list PRIMERGY Blade Server to the object navigator of the vsphere Web Client user interface (see "vsphere Web Client user interface" on page 32). The following options are available for monitoring an MMB in the SV Plug-in: Information about the selected MMB Status icons provide quick information and detailed views provide more information - see "Monitor tab: Information on the selected MMB - Status items and views" on page 82 and "SVvCenter Service for MMBs" on page 85. FUJITSU PRIMERGY actions A number of action items support calling a monitoring tool or making settings on the MMB - see "FUJITSU PRIMERGY Actions" on page 84. Integration in event management of the vsphere Web Client The SV Plug-in includes the SVvCenter Service, which routes FUJITSU PRIMERGY-specific events to the vcenter event management to be monitored in the vsphere Web Client (see "Integration in the event management of the vsphere Web Client" on page 103) Access to the SV Plug-in information of an MMB The object navigator of the vsphere Web Client shows all MMB nodes that are related to an ESXi-based host from the set of the assigned vcenter. The SVvCenter Service (see "SVvCenter Service configuration" on page 33) performs an initial search for all MMBs. The SVvCenter Service repeats the search when specific events occur: FUJITSU Software ServerView Suite 80

81 8.2 Monitoring PRIMERGY blade servers Every time the SVvCenter Service starts If a new ESXi-based server is added to a vcenter If an ESXi-based server is removed from a vcenter Whenever the connection changes (i.e. startup, shutdown) Procedure: The SV Plug-in information about the hosts of a vcenter or a cluster is also displayed if you click the title of an item box of a vcenter/cluster in the Summary tab on the home page of the SV Plug-in (see "Summary view" on page 53). 1. In the object navigator of the vsphere Web Client, select vcenter. 2. Under Inventory Lists, under FUJITSU PRIMERGY select PRIMERGY Blade Server. A list of all MMB nodes is displayed: Figure 31: List of all MMB nodes The list gives general information about each MMB: System name, IP address, model, status, MMB count, server blade count, uptime FUJITSU PRIMERGY Actions Actions This icon will be open if a host is selected in the Monitor tab view. 1. Click this icon to display the actions context menu (see "FUJITSU PRIMERGY Actions" on page 84) SV Plug-in information of an MMB node 1. In the MMB node list (see "Access to the SV Plug-in information of an MMB" on page 80) or in the object navigator of the vsphere Web Client, select the desired MMB node. FUJITSU Software ServerView Suite 81

82 8.2 Monitoring PRIMERGY blade servers The information for the selected MMB node opens in the main workspace, organized in the tabs Summary, Monitor and Related Objects: Figure 32: MMB node: Summary tab There are three tabs with information on the selected MMB node: Summary The Summary tab gives general information about the MMB node: System Name, Model, Status, Uptime, System Contact, System Location, Management Blade Count, Server Blade Count, Storage Blade Count, Connection Blade Count, Power Supply Count, Rear Fan Unit Count Monitor The Monitor tab provides detailed information to the right of the status item tree (see "Monitor tab: Information on the selected MMB - Status items and views" on page 82). Related Objects The Related Objects tab shows the ESXi hosts that are associated with the selected MMB node. In the Related Objects tab of a host node, there is a sub-tab showing the inverse relationship Monitor tab: Information on the selected MMB - Status items and views Time of data acquisition: The data is retrieved from the SNMP agent of the MMB every time you select an item in the status tree. If you click the Refresh icon of vsphere, a new data retrieval cycle will be initiated. FUJITSU Software ServerView Suite 82

83 8.2 Monitoring PRIMERGY blade servers In the main workspace, on the left of the SV Plug-in view, you will find a status item tree: 1. Clicking an item provides detailed information to the right of the status item tree. Each item is preceded by a status icon: ok warning critical unknown retrieving data You can collapse or expand the status item tree to allow more/less space for detailed information on the right. The detailed information on the right is displayed in tables. You can change the column widths and sort the columns as needed. FUJITSU PRIMERGY Actions: Actions This icon will be displayed if a host is selected in the Monitor tab view. 1. Click this icon to open the actions context menu (see "FUJITSU PRIMERGY Actions" on page 84). Status items and views Information Fans General information about the MMB node: System Name, Model, Management Address, Serial Number, Firmware Version, Asset Tag, Rack Name, Managed by VIOM, Status of the Identify LED Information about the fans installed in the chassis: Status, Designation, Current Speed, Maximum Speed, Nominal Speed, Fail Reaction, State Temperature Power Detailed information about the temperature sensors installed in the chassis: Status, Destination, Temperature, Warning Level, Critical Level, Fail Reaction, State Information about the power supplies installed in the chassis: Status, Designation, State FUJITSU Software ServerView Suite 83

84 8.2 Monitoring PRIMERGY blade servers Management Blades Detailed information about the installed management blades: Status, Name with Slot ID, Role, Model, Serial Number, Asset Tag Server Blades Detailed information about the installed server blades: Status, Name with Slot ID, Host Name, Model, Serial Number, Asset Tag, Status of the Identify LED, Textual Status If the MMB hosts an ESXi-based host, the Host Name is displayed as a hyperlink. You can switch directly to the host view by clicking the link. Storage Blades Detailed information about the installed storage blades: Status, Name with Slot ID, Model, Serial Number, Asset Tag, Status of the Identify LED, Textual Status Connection Blades Detailed information about the installed connection blades: Status, Name with Slot ID, Model, Firmware Number, Serial Number, Asset Tag, Status of the Identify LED, Textual Status FUJITSU PRIMERGY Actions The SV Plug-in offers some FUJITSU PRIMERGY Actions. In the top left of the SV Plug-in interface, up to three icons are displayed: For security reasons, a test trap from an MMB can only be triggered on the remote management page of the MMB. Refresh 1. Click this icon to refresh the current view of the SV Plug-in. This Refresh function only refreshes the views/information of the SV Plug-in - not of the vsphere Web Client. Consequently, this function is only available among the icons in the top left of the SV Plug-in interface - not in the Actions menu. Configure SNMP Click this icon to start the SNMP community configuration dialog, where you can set the community for the selected MMB (see "SVvCenter Service for MMBs" on page 85). Start MMB GUI 1. Click this icon to launch the MMB GUI in a new window. FUJITSU Software ServerView Suite 84

85 8.2 Monitoring PRIMERGY blade servers SVvCenter Service for MMBs If a PRIMERGY CPU blade is found as a host on a connected vcenter, the SVvCenter Service searches for blade servers. The SVvCenter Service listens to SNMP traps sent by registered MMBs Overview The SVvCenter Service performs an initial search for MMBs. It repeats this search whenever specific events occur. The SVvCenter Service performs the following steps for all hosts of its vcenter list: Checks if a host is a server blade Retrieves information about the associated hosts (i.e. IP address) Stores information about the relationship in an internal database Stores additional information about the MMB in an internal database (i.e. instance, system name, model, IP address, SNMP community) It performs this procedure when specific events occur: ServerView ESXi CIM Provider must be installed on the ESXi-based host. Every time the SVvCenter Service starts If a new ESXi-based host is added to a vcenter If an ESXi-based host is removed from a vcenter Whenever the connection changes (i.e. startup, shutdown) SNMP settings To use the blade server support of the SV Plug-in, the following requirements must be met: In the SVvCenter Service Configuration Overview: Specify the default SNMP communities to be used when a new MMB is detected by the SVvCenter Service, see "Opening the SVvCenter Configuration Overview" on page 104. In the MMB view: Set the community for the selected MMB, see "FUJITSU PRIMERGY Actions" on page 84. For example, if the value has changed for the MMB. The SVvCenter Service also listens to SNMP traps sent by registered MMBs. To use this feature you need to make sure that the SVvCenter Service is configured as a trap destination. FUJITSU Software ServerView Suite 85

86 8.2 Monitoring PRIMERGY blade servers Receiving SNMP traps The SVvCenter Service listens to SNMP traps sent by registered MMBs. SVvCenter Service must be configured as a trap destination on the registered MMBs. Unlike CIM indications, an SNMP trap is processed for all ESXi-based hosts associated with the sending MMB. You will therefore find the SNMP trap in the event management and logs of the vcenter that hosts the ESXi-based node. If an MMB has multiple hosts in the same vcenter, you will find the event multiple times. Only SNMP traps with the severity major or critical and the test trap will be processed. For security reasons, a test trap from an MMB can only be triggered on the remote management page of an MMB. FUJITSU Software ServerView Suite 86

87 8.3 Monitoring PRIMEQUEST systems 8.3 Monitoring PRIMEQUEST systems The SV Plug-in adds the inventory list PRIMEQUEST Server to the object navigator of the vsphere Web Client user interface (see "vsphere Web Client user interface" on page 32). The following options are available for monitoring a PRIMEQUEST system in the SV Plug-in: Information about the selected PRIMEQUEST system Status icons provide quick information and detailed views provide more information - see "Monitor tab: Information on the selected PRIMEQUEST system - Status items and views" on page 90 and "SVvCenter Service for PRIMEQUEST systems" on page 92. FUJITSU PRIMERGY actions A number of action items support calling a monitoring tool or making settings for PRIMEQUEST systems - see "FUJITSU PRIMERGY Actions" on page 92. Integration in event management of the vsphere Web Client The SV Plug-in includes the SVvCenter Service, which routes FUJITSU PRIMERGYspecific events to the vcenter event management to be monitored in the vsphere Web Client (see "Integration in the event management of the vsphere Web Client" on page 103). FUJITSU Software ServerView Suite 87

88 8.3 Monitoring PRIMEQUEST systems Access to the SV Plug-in information of a PRIMEQUEST system The object navigator of the vsphere Web Client shows all PRIMEQUEST systems, that are related to an ESXi-based host from the set of the assigned vcenter. The SVvCenter Service (see "SVvCenter Service configuration" on page 33) performs an initial search for all PRIMEQUEST systems. The SVvCenter Service repeats the search when specific events occur: Every time the SVvCenter Service starts If a new ESXi-based server is added to a vcenter If an ESXi-based server is removed from a vcenter Whenever the connection changes (i.e. startup, shutdown) Procedure: The SV Plug-in information about the hosts of a vcenter or a cluster is also displayed if you click the title of an item box of a vcenter/cluster in the Summary tab on the home page of the SV Plug-in (see "Summary view" on page 53). 1. In the object navigator of the vsphere Web Client, select vcenter. 2. Under Inventory Lists, under FUJITSU PRIMERGY select PRIMEQUEST Server. A list of all PRIMEQUEST systems is displayed: Figure 33: List of all PRIMEQUEST systems The list gives general information about each PRIMEQUEST system: System name, IP address, model, status, MMB count, partition count, uptime FUJITSU PRIMERGY Actions Actions This icon will be open if a host is selected in the Monitor tab view. 1. Click this icon to display the actions context menu (see "FUJITSU PRIMERGY Actions" on page 92). FUJITSU Software ServerView Suite 88

89 8.3 Monitoring PRIMEQUEST systems SV Plug-in information of a PRIMEQUEST system 1. In the PRIMEQUEST Server list (see "Access to the SV Plug-in information of a PRIMEQUEST system" on page 88) or in the object navigator of the vsphere Web Client, select the desired PRIMEQUEST system. The information for the selected PRIMEQUEST system opens in the main workspace, organized in the tabs Summary, Monitor and Related Objects: Figure 34: PRIMEQUEST system: Summary tab There are three tabs with information on the selected PRIMEQUEST system: Summary The Summary tab gives general information about the PRIMEQUEST system: System Name, Model, Status, Uptime, System Contact, System Location, Management Blade Count, Partition Count, System Board (SB) Count, IO Unit (IOU) Count, Power Supply Count Monitor The Monitor tab provides detailed information to the right of the status item tree (see "Monitor tab: Information on the selected PRIMEQUEST system - Status items and views" on page 90). Related Objects The Related Objects tab shows the ESXi hosts that are associated with the selected PRIMEQUEST node. In the Related Objects tab of a host node, there is a sub-tab showing the inverse relationship. FUJITSU Software ServerView Suite 89

90 8.3 Monitoring PRIMEQUEST systems Monitor tab: Information on the selected PRIMEQUEST system - Status items and views Time of data acquisition: The data is retrieved from the SNMP agent of the PRIEMQUEST system every time you select an item in the status tree. If you click the Refresh icon of vsphere, a new data retrieval cycle will be initiated. In the main workspace, on the left of the SV Plug-in view, you will find a status item tree: 1. Clicking an item provides detailed information to the right of the status item tree. Each item is preceded by a status icon: ok warning critical unknown retrieving data You can collapse or expand the status item tree to allow more/less space for detailed information on the right. The detailed information on the right is displayed in tables. You can change the column widths and sort the columns as needed. FUJITSU PRIMERGY Actions: Actions This icon will be displayed if a host is selected in the Monitor tab view. 1. Click this icon to open the actions context menu (see "FUJITSU PRIMERGY Actions" on page 92). Status items and views Information General information about the PRIMEQUEST system: System Name, Model, Management Address, Serial Number, Firmware Version Fans Information about the fans installed in the chassis: Status, Designation, Speed (RPM), Fail Reaction, State FUJITSU Software ServerView Suite 90

91 8.3 Monitoring PRIMEQUEST systems Temperature Detailed information about the temperature sensors installed in the chassis: Status, Designation, Temperature, Warning Level, Critical Level, Fail Reaction, State Power Information about the power supplies installed in the chassis: Status, Designation, State Management Blades Detailed information about the installed management blades: Status, Name, Serial Number, Asset Tag Partitions Detailed information about the system partitions: Status, Name, Current Boot State, Asset Tag, State SB Details Detailed information about the installed system boards: Status, Name, Serial Number, Asset Tag, State IOU Details Detailed information about the installed I/O units: Status, Name, Serial Number, Asset Tag, State DU Details Detailed information about the installed disk units: Status, Name, Serial Number, Asset Tag, State PciBoxes Detailed information about the installed PRIMEQUEST PCI boxes: Status, Name, Serial Number, Asset Tag, State Processors Detailed information about the system processor configuration: Status, Designation, Type, L3 Cache (KB), State Memory Detailed information about the memory modules installed in the system: Status, Designation, Size (MB), State Voltages Detailed information about the voltage sensors within the system: Status, Designation, Current Value, Minimum Level, Maximum Level, State FUJITSU Software ServerView Suite 91

92 8.3 Monitoring PRIMEQUEST systems FUJITSU PRIMERGY Actions The SV Plug-in offers some FUJITSU PRIMERGY Actions. In the top left of the SV Plug-in interface, up to three icons are displayed: Refresh 1. Click this icon to refresh the current view of the SV Plug-in. This Refresh function only refreshes the views/information of the SV Plugin - not of the vsphere Web Client. Therefore, this function is only available among the icons in the top left of the SV Plug-in interface - not in the Actions menu. Configure SNMP Click this icon to start the SNMP community configuration dialog, where you can set the community for the selected MMB (see "SNMP settings" on page 93). Start MMB GUI 1. Click this icon to launch the PRIMEQUEST Management Board Web UI in a new window SVvCenter Service for PRIMEQUEST systems The SVvCenter Service searches for PRIMEQUEST systems. The service checks for each ESXi host on the connected vcenters whether the host is a PRIMEQUEST partition. If so, the SVvCenter Service adds the associated PRIMEQUEST to the inventory list and listen to SNMP traps sent from the discovered PRIMEQUEST systems Overview The SVvCenter Service performs an initial search for PRIMEQUEST systems and repeats this search whenever specific events occur. On startup, the SVvCenter Service performs the following steps for all hosts of its vcenter list: Checks if a host is a partition or a PRIMEQUEST system Retrieves information about the associated PRIMEQUEST (i.e. IP address) Stores information about the relationship in an internal database Stores additional information about the PRIMEQUEST system in an internal database (i.e. instance, system name, model, IP address, SNMP community) It performs this procedure when specific events occur: FUJITSU Software ServerView Suite 92

93 8.3 Monitoring PRIMEQUEST systems ServerView ESXi CIM Provider must be installed on the ESXi-based host. Every time the SVvCenter Service starts If a new ESXi-based host is added to a vcenter If an ESXi-based host is removed from a vcenter Whenever the connection changes (i.e. startup, shutdown) SNMP settings To use the PRIMEQUEST system support of the SV Plug-in, the following requirements must be met: In the SVvCenter Service Configuration Overview: 1. Specify the default SNMP communities to be used when a new PRIMEQUEST system is detected by the SVvCenter Service, see "SVvCenter Service Configuration Overview" on page 104. In the PRIMEQUEST view: 1. Set the community for the selected PRIMEQUEST system, see "FUJITSU PRIMERGY Actions" on page 92. For example, if the value has changed for the PRIMEQUEST system. 2. The community must be registered on the PRIMEQUEST Management Board Web UI for the SVvCenter Service and the vsphere Web Client. You will find this setting on the PRIMEQUEST Management Board Web UI in the menu: Network Configuration - SNMP Configuration - Community The SVvCenter Service also listens to SNMP traps sent by registered PRIMEQUEST systems. To use this feature you need to make sure that the SVvCenter Service is configured as a trap destination Receiving SNMP traps The SVvCenter Service listens to SNMP traps sent by registered PRIMEQUEST systems. SVvCenter Service must be configured as a trap destination on the registered PRIMEQUEST systems. 1. Configure SVvCenter Service as a trap destination on the registered PRIMEQUEST system. You will find this setting on the PRIMEQUEST Management Board Web UI in the menu: Network Configuration - SNMP Configuration - Trap FUJITSU Software ServerView Suite 93

94 8.4 Discovering PRIMERGY Bmc Systems (for deploying) Unlike CIM indications, an SNMP trap is processed for all ESXi-based hosts associated with the sending PRIMEQUEST system. You will therefore find the SNMP trap in the event management and logs of the vcenter that hosts the ESXi-based node. If a PRIMEQUEST system has multiple hosts in the same vcenter, you will find the event multiple times. Only SNMP traps with the severity major or critical and the test trap will be processed. For security reasons, a test trap from a PRIMEQUEST system can only be triggered on the remote management page of a PRIMEQUEST system. 8.4 Discovering PRIMERGY Bmc Systems (for deploying) Bare metal PRIMERGY systems without an operating system can be added to the SV Plug-in to deploy the ESXi operating system via ServerView profiles. To do so you must 1. Add the PRIMERGY Bmc System(s) to the SV Plug-in, see "Adding PRIMERGY Bmc Systems to the vcenter inventory" on page Store a customized ServerView profile under FUJITSU PRIMERGY Administration, see "ServerView Profile Management Service configuration" on page Deploy the ESXi operating system via the ServerView Deployment vrealize Orchestrator Workflow, see "Deploying PRIMERGY Bmc Systems" on page PRIMERGY Bmc Systems view The SV Plug-in adds the inventory list PRIMERGY Bmc Systems to the object navigator of the vsphere Web Client user interface (see "vsphere Web Client user interface" on page 32). 1. In the object navigator of the vsphere Web Client, select vcenter Inventory Lists. 2. Under FUJITSU PRIMERGY select PRIMERGY Bmc Systems. The PRIMERGY Bmc Systems view is displayed: Figure 35: PRIMERGY Bmc Systems view FUJITSU Software ServerView Suite 94

95 8.4 Discovering PRIMERGY Bmc Systems (for deploying) Adding PRIMERGY Bmc Systems to the vcenter inventory The connection with the PRIMERGY Bmc System runs via IPMI. Each PRIMERGY Bmc System therefore is configured with a BMC IP address, user name and password. Initially empty, the PRIMERGY Bmc Systems view (see "PRIMERGY Bmc Systems view" on page 94) allows to add a PRIMERGY Bmc System manually (see "Adding a PRIMERGY Bmc System manually" on page 95), to search for such systems (see "Searching for PRIMERGY Bmc Systems" on page 95) or to add a PRIMERGY Bmc System from file (see "Adding a PRIMERGY Bmc System from file" on page 97). Internet Explorer 11: You must configure a certain option under Internet Properties, see "Requirements and localization" on page 31. If this option is not checked, editing a profile or browsing for PRIMERGY Bmc Systems will fail Adding a PRIMERGY Bmc System manually 1. In the PRIMERGY Bmc Systems view click the icon. A dialog opens. 2. In the Create new Bmc System dialog make the following settings: Name, Address (IP address of the BMC of the system), Login, Password. All settings are required. 3. Click the Test button to test the connection with the BMC of the PRIMERGY Bmc System. 4. Click the OK button. The selected PRIMERGY Bmc System is added to the vcenter inventory. To see the added PRIMERGY Bmc System in the Summary view for PRIMERGY Bmc Systems: Refresh the Summary view manually. See "SV Plug-in information of a PRIMERGY Bmc Systems" on page Searching for PRIMERGY Bmc Systems Internet Explorer 11: You must configure a certain option under Internet Properties, see "Requirements and localization" on page 31. If this option is not checked, editing a profile or browsing for PRIMERGY Bmc Systems will fail. FUJITSU Software ServerView Suite 95

96 8.4 Discovering PRIMERGY Bmc Systems (for deploying) 1. In the PRIMERGY Bmc Systems view click the icon. The Discover BMC Systems dialog opens. Figure 36: PRIMERGY Bmc System: Discover BMC Systems In this dialog you must make the following settings: Select the credentials of at least one BMC of a targeted PRIMERGY Bmc System. See "Selecting/ Configuring credentials" on page 96. Specify a range of IP addresses within those the service has to search. See "Specify a range of IP addresses and start searching" on page 97. Add a PRIMERGY Bmc System found to the vcenter inventory. See "Add a PRIMERGY Bmc System found to the vcenter inventory" on page 97. Selecting/ Configuring credentials 1. In the Discover BMC Systems dialog window click the Configure Credentials button. The Configure Credentials dialog opens. The window lists defined combinations of user name and password. To add To edit In the Configure Credentials dialog click the icon. The Add Login dialog opens. To define a combination of user name and password you must specify a unique Credential Name. To add the combination to the list of defined combinations click the OK button. If the Credential Name already exists, adding is rejected. In the list of defined combinations select the desired combination. In the Configure Credentials dialog click the The Edit Login dialog opens icon To add the combination to the list of defined combinations click the OK button FUJITSU Software ServerView Suite 96

97 8.4 Discovering PRIMERGY Bmc Systems (for deploying) To delete In the list of defined combinations select the desired combination. In the Configure Credentials dialog click the The selected combination is deleted from the list. icon. 2. In the Configure Credentials dialog select a credentials combination from the list. 3. To close the Configure Credentials dialog click the Close button. Specify a range of IP addresses and start searching 1. In the Discover BMC Systems dialog use the fields From Address and To Address to specify the range of IP addresses within those the service has to search. 2. To start the searching process click the Start Discovery button. A progress bar indicates the process progress as percentage value. As soon as results are available they are shown in the list in the lower part of the Discover BMC Systems dialog. This table is successfully completed. To cancel the searching process click the Stop Discovery button. Add a PRIMERGY Bmc System found to the vcenter inventory 1. Select one of the PRIMERGY Bmc Systems or several of them in the list in the lower part of the Discover BMC Systems dialog. 2. Click the icon. The selected PRIMERGY Bmc Systems are added to the vcenter inventory. To see the added PRIMERGY Bmc Systems in the Summary view for PRIMERGY Bmc Systems: Refresh the Summary view manually. See "SV Plug-in information of a PRIMERGY Bmc Systems" on page Adding a PRIMERGY Bmc System from file Via the dialog Add BMC Systems from File you can search for a CSV file containing a list of PRIMERGY Bmc Systems. Via this list you can add these PRIMERGY Bmc Systems to the vcenter inventory. CSV file The CSV file must contain at least two columns in a fixed order: first column Must contain the names of the PRIMERGY Bmc Systems. last column Must contain the addresses of the PRIMERGY Bmc Systems. FUJITSU Software ServerView Suite 97

98 8.4 Discovering PRIMERGY Bmc Systems (for deploying) Examples: Figure 37: CSV file - example 1 Figure 38: CSV file - example 2 Example 2: For detecting the header line the same locale must be used for export and import. Proceeding 1. In the PRIMERGY Bmc Systems view click the icon. A dialog opens. Figure 39: PRIMERGY Bmc System: Add BMC Systems from File FUJITSU Software ServerView Suite 98

99 8.4 Discovering PRIMERGY Bmc Systems (for deploying) 2. Click the botton Browse... to select a CSV file. In the lower part of the dialog window the first and the last column of the selected file are displayed under the headings Name and Address. If a value in the last column of the selected file doesn t comply with the IPv4 address format, an error message is displayed. After confirming the error message the message itself, just as the dialog Add Bmc Systems from File are closed. 3. Specify Login and Password, which apply for all PRIMERGY Bmc Systems in the selected list. These settings are required. Once you have completed these entries the icon is enabled. 4. Click the icon. The PRIMERGY Bmc Systems from the selected list are added to the vcenter inventory. After completion of adding the PRIMERGY Bmc Systems to the vcenter inventory a report window is displayed: Figure 40: PRIMERGY Bmc System: Add Bmc Systems (results) 5. Click OK. If a PRIMERGY Bmc System could not be added to the vcenter inventory, the reason is given in parentheses. The reason Operation timeout can have various causes: password is wrong, PRIMERGY Bmc System is not reachable, a specified system isn t a PRIMERGY Bmc System. To see the added PRIMERGY Bmc Systems in the Summary view for PRIMERGY Bmc Systems: Refresh the Summary view manually. See "SV Plug-in information of a PRIMERGY Bmc Systems" on page 100. FUJITSU Software ServerView Suite 99

100 8.4 Discovering PRIMERGY Bmc Systems (for deploying) SV Plug-in information of a PRIMERGY Bmc Systems 1. In the PRIMERGY Bmc Systems list select the desired PRIMERGY Bmc System. 2. Double click on the selected item. The information for the selected PRIMERGY Bmc System opens in the main workspace, organized in the tabs Summary, Monitor and Related Objects Figure 41: PRIMERGY Bmc System: Summary tab There are three tabs with information on the selected PRIMERGY Bmc System: Summary The Summary tab gives general information about the PRIMERGY Bmc System which has been delivered by the system s BMC: Name, Model, Address, Serial Number, Asset Number, Model Type, BIOS Version, Firmware Version, UUID, Operating System, System Name, System Type, Location, Contact Manage The Manage tab is starting point for updating or deploying a PRIMERGY Bmc System. If the BMC of a PRIMERGY Bmc System belongs to a host, updating or deploying will not be possible. You will find information about this on the tab Summary in the field General Information. Start Update The elcm Offline Update view is helpful when planning an update. It shows details of meeting requirements, progress information, details and parameters of the update workflow. See "Offline update via elcm" on page 112. FUJITSU Software ServerView Suite 100

101 8.4 Discovering PRIMERGY Bmc Systems (for deploying) Start Deployment Starts a wizard for deploying a PRIMERGY Bmc System. See "Deploying PRIMERGY Bmc Systems" on page 120. Assign Host The SV Plug-in checks if an ESXi operating system is already installed on the PRIMERGY Bmc System. If an ESXi operating system is found, a third button Assign Host is displayed. Clicking this button launches a window: Here you can select the desired destination (data center or cluster), the PRIMERGY Bmc System should be added to. To perform this task a VMware vrealize Orchestrator workflow will be started. Related Objects FUJITSU PRIMERGY Actions The SV Plug-in offers some FUJITSU PRIMERGY Actions. In the top left of the SV Plug-in interface, up to seven icons are displayed: Refresh 1. Click this icon to refresh the current view of the SV Plug-in. This Refresh function only refreshes the views/information of the SV Plug-in - not of the vsphere Web Client. Consequently, this function is only available among the icons in the top left of the SV Plug-in interface - not in the Actions menu. Toggle Identify LED 1. Click this icon to toggle the Locate LED between on and off: Locate icon is blue: locate LED is on. Locate icon is gray: locate LED is off. The icon is displayed if an irmc address is available. Start irmc 1. Click this icon to launch the irmc Web interface in a new window. The icon is displayed if an irmc address is available. See "Starting irmc functions with/without single sign-on" on page 43. FUJITSU Software ServerView Suite 101

102 8.4 Discovering PRIMERGY Bmc Systems (for deploying) Start Remote Console 1. Click this icon to launch a remote console (AVR) in a new window. The icon is displayed if an irmc address is available. See "Starting irmc functions with/without single sign-on" on page 43. Start a System Report 1. Click this icon to start an irmc system report in a new window. See "irmc system report" on page 111. Start an elcm Offline Update Workflow 1. Click this icon to start the ServerView elcm Offline Update Workflow via irmc (S4) directly for a host. Deploy The ServerView elcm Offline Update Workflow is part of the FUJITSU Software ServerView Plug-in for VMware vrealize Orchestrator elcm Offline Update package. See "Offline update via elcm" on page Click this icon to start the ServerView Deployment Workflow via irmc (S4) directly for a PRIMERGY Bmc System. The ServerView Deployment Workflow is part of the FUJITSU Software ServerView Plug-in for VMware vrealize Orchestrator Deployment package. See "Deploying PRIMERGY Bmc Systems" on page 120. FUJITSU Software ServerView Suite 102

103 9 Integration in the event management of the vsphere Web Client The SV Plug-in includes a SVvCenter Service which routes FUJITSU PRIMERGY-specific events to the vcenter event management to be monitored in the vsphere Web Client. If a FUJITSU PRIMERGY host detects a problem, it will create a CIM indication and send it to subscribed destinations. If the SVvCenter Service is subscribed to the host, it will receive this CIM indication. It creates a corresponding vcenter event and forwards it to vcenter Server. The SVvCenter Service also performs a search for blade servers or PRIMEQUEST systems if a PRIMERGY CPU blade or PRIMEQUEST system is found as a host on a connected vcenter (see "SVvCenter Service configuration" on page 33). The SVvCenter Service listens to SNMP traps sent by registered MMBs (see "SVvCenter Service for MMBs" on page 85) or registered PRIMEQUEST systems (see "SVvCenter Service for PRIMEQUEST systems" on page 92). In certain situations, some further settings can help you enhance the performance of the SVvCenter Service for events, MMBs and PRIMEQUEST systems (see "Further helpful service properties for the SVvCenter Service for events, MMBs and PRIMEQUEST systems" on page 106). So the FUJITSU PRIMERGY-specific event is shown in the regular Monitor-Events sub-tab of the vsphere Web Client: Figure 42: FUJITSU PRIMERGY-specific events in the Monitor-Events sub-tab of the vsphere Web Client FUJITSU Software ServerView Suite 103

104 9.1 Requirements 9.1 Requirements CIM and SNMP ESXi-based host MMB ServerView ESXi CIM Provider must be installed on the ESXi-based host whose events are to be displayed in the vsphere Web Client interface. SVvCenter Service must be configured as a trap destination on the registered MMBs. PRIMEQUEST system SVvCenter Service must be configured as a trap destination on the registered PRIMEQUEST systems. SVvCenter Service must be connected to the vcenter to which the host is assigned to (see "SVvCenter Service configuration" on page 33). SVvCenter Service must be subscribed to this host (see "Monitoring vcenter or cluster host servers" on page 71). You can find an overview of the hosts subcribed to a SVvCenter Service in the SVvCenter Configuration Overview (see "SVvCenter Service Configuration Overview" on page 104). 9.2 SVvCenter Service Configuration Overview You can use this view to manage all the SVvCenter Services installed in your environment Opening the SVvCenter Configuration Overview At the bottom of the Getting Started tab on the home page of the SV Plug-in, you will find the Manage the SVvCenter Services link. 1. In the object navigator of the vsphere Web Client, select the item Administration. 2. Select the sub-item FUJITSU PRIMERGY Administration. 3. Select the sub-item SVvCenter Service Configuration Overview. In the main workspace of the vsphere Web Client, the SVvCenter Service Configuration Overview opens: FUJITSU Software ServerView Suite 104

105 9.2 SVvCenter Service Configuration Overview Figure 43: SVvCenter Service Configuration Overview Properties of SVvCenter Services The properties of a SVvCenter Service are also displayed if you click the title of an item box of a SVvCenter Service in the Summary tab on the home page of the SV Plug-in (see "Summary view" on page 53). 1. Select a SVvCenter Service in the Service Location selection box. The current properties of the selected SVvCenter Service are displayed: Connection State Address Port Version Default Snmp Communities vcenter Name Current status and connection between the vsphere Web Client and the SVvCenter Service Address used for the connection Port used for the connection Version of the SVvCenter Service For discovering blade servers (see "SVvCenter Service for MMBs" on page 85) and PRIMEQUEST systems (see "SVvCenter Service for PRIMEQUEST systems" on page 92). You can edit this list (commaseparated) by clicking the pencil icon seen in this section. vcenters connected to this SVvCenter Service. The icon in front of it shows the status between the SVvCenter Service and the vcenter. It also shows how many hosts are monitored (subscribed) and how many are not. FUJITSU Software ServerView Suite 105

106 9.2 SVvCenter Service Configuration Overview Further helpful service properties for the SVvCenter Service for events, MMBs and PRIMEQUEST systems In certain situations, some further settings can help you enhance the performance of the SVvCenter Service for events, MMBs and PRIMEQUEST systems. You can set these properties in the service.properties file of the service. The file is located on the same system as the service:...\fujitsu\vcenter Integration\service\conf\service.properties Further service properties trap.forward.limit=30 Time limit for event forwarding. Default value: 30 seconds. Only numeric values. Note: Sometimes events are sent with high frequency. In this case the same event is sent repeatedly by the same host and generates a significant number of entries in the event management of vsphere Web Client. The same event sent by the same host during this time limit will not be forwarded to the vcenter event management. cim.client.timeout=3000 Timeout value for CIM connections. Default value: 3000 milliseconds. Only numeric values. Note: Low connectivity in the network or older versions of CIM providers cause connection timeouts. If you increase this value, there will be fewer connection timeouts but the processing will take longer! snmp.client.timeout=3000 Timeout value for SNMP connections. Default value: 3000 milliseconds. Only numeric values. Note: Low connectivity in the network or older versions of SNMP agents cause connection timeouts. If you increase this value, there will be fewer connection timeouts but the processing will take longer! Adding/removing a vcenter to/from the SVvCenter Service For further information on the following procedures see: "SVvCenter Service configuration" on page 33. FUJITSU Software ServerView Suite 106

107 9.3 FUJITSU PRIMERGY Predefined Alarm 9.3 FUJITSU PRIMERGY Predefined Alarm The SV Plug-in offers a predefined alarm that will be triggered if a warning or error-level event is received by the vsphere Web Client event management. This alarm is enabled but has no actions defined. You can define a convenient action for this predefined alarm in the vsphere Web Client: Requirements: Required privilege: Alarms.Create Alarm or Alarm.Modify Alarm Procedure: After a new or update installation of the SV Plug-in any changes made to an alarm (for example actions) will be lost. You must reconfigure the action as needed. 1. In the object navigator of the vsphere Web Client, select an inventory object. 2. Click the Manage tab. 3. Click the Alarm Definitions sub-tab. 4. Right-click the list of alarms and select one of the options to add or edit an alarm. For further information see the documentation for VMware vsphere. 5. Click Finish. 9.4 Actions relating to SVvCenter Service In the vsphere Web Client views for ESXi-based hosts (see "SV Plug-in information of an ESXi-based host" on page 59 and "FUJITSU PRIMERGY Actions (irmc-based operations)" on page 63, you will find the following actions relating to the SVvCenter Service: Toggle FUJITSU Event Monitoring 1. Click this icon to turn the subscription of the host to the SVvCenter Service on/off. This action is depicted in four ways, depending on the current subscription status: The host is subscribed to the SVvCenter Service. Events will be monitored by the SVvCenter Service and forwarded. The host is not subscribed to the SVvCenter Service. No events will be monitored by the SVvCenter Service or forwarded. FUJITSU Software ServerView Suite 107

108 9.4 Actions relating to SVvCenter Service The subcription status of the host is unknown due to connection problems with the SVvCenter Service. No action will be performed. The host cannot be subscribed, because the vcenter is not connected to the SVvCenter Service. No action will be performed. Invoke Test Event 1. Click this icon to request the host to send a test indication. The selected host will be requested to send a test indication to its subscribed nodes. If the host is not subscribed to the SVvCenter Service (see "SVvCenter Service configuration" on page 33), you will not see the event in the vcenter Event Manager (Monitor-Events sub-tab of the vsphere Web Client). FUJITSU Software ServerView Suite 108

109 10.1 LED 10 Remote Management The SV Plug-in offers some irmc-based operations - called FUJITSU PRIMERGY Actions - depending on the capabilities of the selected host. They make it very easy for the administrator to connect directly to an ESXi-based host and its irmc. To perform the irmc-based operations (irmc Web Interface together with single sign-on (SSO), AVR, location button LED and, with ServerView ESXi CIM Provider V6.31 and below, the System Event Log view), the user name and password for the IPMI credentials must be configured in the vcenter Server (see "IPMI configuration" on page 40). Click the on page 40). icon to start the IPMI configuration dialog (see "IPMI configuration" These IPMI-based actions are always enabled in the context menu, even if the credentials are not configured or the user does not have the privilege to perform the action. In this case an error message will be shown if the action is started. Starting one of these irmc-based FUJITSU PRIMERGY Actions ESXi-based host See "Starting a FUJITSU PRIMERGY Action" on page 63. vcenter or cluster host server See "FUJITSU PRIMERGY Actions" on page 73. PRIMERGY blade server See "SV Plug-in information of an MMB node" on page 81. PRIMEQUEST server See "SV Plug-in information of a PRIMEQUEST system" on page 89. PRIMERGY Bmc System See "SV Plug-in information of a PRIMEQUEST system" on page LED LED To facilitate identification of a system, for instance if it is installed in a fully populated rack, you can activate the identification LED. FUJITSU Software ServerView Suite 109

110 10.2 irmc Web Interface Toggle Identify LED 1. Click this icon to toggle the Locate LED between on and off: Locate icon is blue: locate LED is on. Locate icon is gray: locate LED is off. The icon is displayed if an irmc address is available irmc Web Interface irmc S4 permits system control, diagnosis, configuration and server restarting by remote access via the integrated web interface - even if the operating system or hardware fails. The irmc 4 supports Centralized Authentication Service (CAS) configuration, which allows you to configure the irmc S4 web interface for CAS-based single sign-on (SSO) authentication. Start irmc 1. Click this icon to launch the irmc Web interface in a new window. The icon is displayed if an irmc address is available. See "Starting irmc functions with/without single sign-on" on page Remote console (AVR) Advanced Video Redirection (AVR) with irmc S4 offers the following benefits: Operation via a standard web browser (as of FW version 8.05F you can select HTML5). System-independent graphical and text console redirection (including mouse and keyboard). Remote access for boot monitoring, BIOS administration and control of the operating system. Local monitor-off support. Low bandwidth support. Start Remote Console 1. Click this icon to launch a remote console (AVR) in a new window. The icon is displayed if an irmc address is available. See "Starting irmc functions with/without single sign-on" on page 43. FUJITSU Software ServerView Suite 110

111 10.4 irmc system report 10.4 irmc system report Requirements The irmc must be version S4. The irmc credentials must be configured as follows: For further information see "FUJITSU PRIMERGY vcenter role definitions and irmc single sign-on" on page 41. o o The irmc credentials must be configured with an irmc user account that has the Administrator LAN channel privilege. The vcenter user must have the privileges defined in the FUJITSU PRIMERGY role FUJITSU PRIMERGY Plug-in Administrator. Start a System Report 1. Click this icon to start an irmc system report in a new window. See "irmc system report" on page elcm Offline Update The SV Plug-in offers the option for starting an offline update via elcm on a host or on a PRIMERGY Bmc System. To perform the update, a new ServerView elcm Offline Update Workflow has been developed. It is part of the FUJITSU Software ServerView Plug-in for VMware vrealize Orchestrator elcm Offline Update package (for more information see the manual "FUJITSU Software ServerView Plug-in for VMware vrealize Orchestrator"). Start an elcm Offline Update Workflow 1. Click this icon to start the ServerView elcm Offline Update Workflow via irmc (S4) directly for a host. The ServerView elcm Offline Update Workflow is part of the FUJITSU Software ServerView Plug-in for VMware vrealize Orchestrator elcm Offline Update package. See "Offline update via elcm" on page 112. FUJITSU Software ServerView Suite 111

112 11 Offline update via elcm elcm - embedded LifeCycle Management As well as making it possible to manage a PRIMERGY server out-of-band, the enhanced functionality of the newest version of the irmc S4, which comes with an integrated SD card, allows for comprehensive lifecycle management of a PRIMERGY server. As lifecycle management is largely integrated ("embedded") in and entirely controlled by the irmc S4, it is called "embedded LifeCycle Management" (elcm). elcm update management functionality elcm update management functionality is based on the ability of the irmc S4 to automatically download files from a repository server via the dedicated irmc S4 management LAN port and to store them on the irmc S4 SD card. The repository server can be the FTS Support Server or a separate server running the ServerView Repository Server (see the manual "ServerView Update Repository" for details). Some server components can only be updated by the server operating system. To make the corresponding update packages available to the server operating system, the irmc S4 downloads these packages, makes an ISO image from them, and mounts the ISO image as a virtual CD-ROM device. Offline update mode of the irmc An offline update extends the autonomous update capabilities of the irmc S4. System components like network or storage controller firmware can be updated using the offline update mode. In this case, a bootable update image that was previously downloaded from the repository server onto the irmc S4 SD card is mounted by the irmc S4 via remote image mount as a system USB CD/DVD-ROM device. Like the common Update DVD, the bootable update image consists of two main parts: a boot loader for booting CentOS and the elcm offline update manager itself, which is a slim version of the ServerView Update Manager Express. Once the USB CD/DVD-ROM is mounted, the irmc S4 automatically shuts down the server and reboots it from the mounted USB CD/DVD-ROM device. Offline update via elcm The SV Plug-in offers the option for starting an offline update via elcm on a host or on a PRIMERGY Bmc System. To perform the update, a new ServerView elcm Offline Update Workflow has been developed. It is part of the FUJITSU Software ServerView Plug-in for VMware vrealize Orchestrator elcm Offline Update package. Workflows combine actions, decisions and results that, when performed in a particular order, complete a specific task or process in a FUJITSU Software ServerView Suite 112

113 11.1 Requirements and compatibility warning virtual environment (for more information see the manual "FUJITSU Software ServerView Plug-in for VMware vrealize Orchestrator"). Offline update via elcm on a host (not valid for PRIMERGY Bmc Systems): Before the update is started, the host will be put into maintenance mode and shut down. Once started, the workflow will connect to the elcm and start the update Requirements and compatibility warning Compatibility warning! This action will update the system s BIOS and firmware components, depending on the contents of the FUJITSU Update Repository. Updating could cause a violation of the VMware hardware compatibility list requirements. Please consider this when using specific configurations. Offline update via elcm on a host (not valid for PRIMERGY Bmc Systems): Shutdown by ServerView elcm Offline Update Workflow Before the update is started, the ServerView elcm Offline Update Workflow will put the host into maintenance mode and shut it down. Once started, the workflow will connect to the elcm and start the update. The following requirements must be met in order to start the update. irmc o irmc must have an S4 and a minimum version 8.03F o o o irmc credentials must be configured for the BMC The irmc must be licensed to perform elcm The user must have Administrator privileges for the host/ the PRIMERGY Bmc System The repository and proxy configuration must be done via the irmc Web Interface. If the configuration is not correct, the update workflow will fail. The view is not able to check the presence and validity of this configuration. VMware vrealize Orchestrator must be installed (minimum version 6.0) and must be connected to the vcenter. o The FUJITSU Software ServerView Plug-in for VMware vrealize Orchestrator elcm Offline Update (minimum version 1.2.5) must be installed in VMware vrealize Orchestrator FUJITSU Software ServerView Suite 113

114 11.2 Starting points VMware vrealize Orchestrator V7.0: VMware vrealize Orchestrator V7.0 has TSLv1 protocol disabled by default. The vsphere WebClient V6.0 as well as the SV Plug-in perform the connections using this version, Therefore it will not be able to connect to the VMware vrealize Orchestrator and manage the update and deploy workflows. For this reason, it is necessary to configure the VMware vrealize Orchestrator to accept TSLv1 requests: 1. Connect to the VMware vrealize Orchestrator appliance. 2. Edit the file /etc/vco/app-server/server.xml. 3. Replace the attribute sslenabledprotocols="tlsv1.1, TLSv1.2" with sslenabledprotocols="tlsv1, TLSv1.1, TLSv1.2". 4. Save the file /etc/vco/app-server/server.xml. 5. Restart the VMware vrealize Orchestrator service using the command service vco-server restart Starting points You have two options for starting an offline update via elcm: From a separate elcm Offline Update view of the SV Plug-in user interface. The elcm Offline Update view is helpful when planning an update. It shows information on meeting requirements, progress information, and details and parameters of the update workflow. See "Offline update via elcm started from SV Plug-in view" on page 114. From an item on the SV Plug-in FUJITSU PRIMERGY Actions menu. Starting the offline update this way gives you less information on workflow progress. If you start the update here, the system checks that the requirements are met and, if so, starts the elcm Offline Update Workflow. Otherwise an error message is displayed. See "Offline update via elcm started from SV Plug-in FUJITSU PRIMERGY Actions menu" on page Offline update via elcm started from SV Plug-in view The elcm Offline Update view is helpful when planning an update. It shows details of meeting requirements, progress information, details and parameters of the update workflow. FUJITSU Software ServerView Suite 114

115 11.3 Offline update via elcm started from SV Plug-in view Opening the elcm Offline Update view Opening the view of a host object 1. In the object navigator of the vsphere Web Client, select a host object. 2. Click the Configure tab. In the main workspace of the vsphere Web Client the view Configure opens. 3. In the menu tree on the left of the Configure view select FUJITSU PRIMERGY. The elcm Offline Update view of the SV Plug-in opens Opening the view of a PRIMERGY Bmc System 1. In the object navigator of the vsphere Web Client, select vcenter Inventory Lists. 2. Under FUJITSU PRIMERGY select PRIMERGY Bmc Systems. The PRIMERGY Bmc Systems view is displayed. Here you find a list of the known PRIMERGY Bmc Systems. 3. In PRIMERGY Bmc Systems list select the desired PRIMERGY Bmc System. 4. Double click on the selected item. The information for the selected PRIMERGY Bmc System opens in the main workspace, organized in the tabs Summary, Manage and Related Objects. 5. Select the tab Manage. 6. Click the Start Update button Checking requirements First the elcm Offline Update functionality checks its requirements. Requirements failed If one or more requirements are not met, the following information is displayed. FUJITSU Software ServerView Suite 115

116 11.3 Offline update via elcm started from SV Plug-in view For a host system: Figure 44: elcm Offline Update view - Requirements failed For a PRIMGERY Bmc System: Figure 45: PRIMERGY Bmc Systems view - Requirements failed The elcm Offline Update can only be started if the requirements are met. 1. Identify the problem and, if possible, perform the required actions. Requirements met - ready to start If all requirements are met, the Start Update button is displayed: FUJITSU Software ServerView Suite 116

117 11.3 Offline update via elcm started from SV Plug-in view Figure 46: elcm Offline Update view - Requirements met 1. Click the Start Update button to start the elcm Offline Update workflow. It takes some time for the workflow to start, and you will get a message saying whether or not it was started successfully elcm Offline Update in progress Figure 47: elcm Offline Update view - In progress FUJITSU Software ServerView Suite 117

118 11.3 Offline update via elcm started from SV Plug-in view The elcm Offline Update itself will take some time, so the view will be refreshed once to see the progress of the workflow. You must then refresh the view manually if you want to keep monitoring the progress: Click the view of the SV Plug-in. icon to refresh the current It is now no longer possible to restart the update elcm Update Workflow details The SV Plug-in provides information about the progress of a workflow.you can select either a workflow that is currently running or one which is complete. If no logs are present, they might have been deleted by VMware vrealize Orchestrator. 1. In the list of update runs, click the [+] icon in front of the selected item. The logs and parameters of the workflow are displayed. There are two tabs for switching between Logs and Parameters. Checking the parameters used to start an unsuccessful workflow might help you understand why it failed. Figure 48: elcm Offline Update view - Workflow logs Deleting update history items You can delete some of the update history items. FUJITSU Software ServerView Suite 118