fujitsu software serverview plug-in for vmware...

User Guide - English

FUJITSU Software ServerView Suite

FUJITSU Software ServerView Plug-in forVMware vCenter V2.6

Edition February 2018

Comments… Suggestions… Corrections…The User Documentation Department would like to know your opinion of this manual. Yourfeedback helps us optimize our documentation to suit your individual needs.

Feel free to send us your comments by e-mail [email protected].

Certified documentation according to DIN EN ISO 9001:2008To ensure a consistently high quality standard and user-friendliness, this documentationwas created to meet the regulations of a quality management system which complies withthe requirements of the standard DIN EN ISO 9001:2008.

cognitas. Gesellschaft für Technik-Dokumentation mbH

www.cognitas.de

Copyright and trademarksCopyright 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 logoare trademarks of the Apache Software Foundation.

FUJITSU Software ServerView Suite 2

mailto:[email protected]

http://www.cognitas.de/

Contents

1 Overview 8

1.1 Integration approaches 9

1.2 Monitoring and managing possibilities 10

1.3 What’s new 12

1.4 Target groups and purpose of this manual 13

1.5 Documentation for the ServerView Suite 13

1.6 Abbreviations 13

1.7 Typographic conventions 13

2 Installing on Windows 15

2.1 Provisioning 15

2.2 Requirements 15

2.3 Installation notes 16

2.4 Installing and registering 16

2.4.1 Installing procedure 172.4.2 Guided installing dialog 182.4.3 Finished installation notes 202.4.4 Verifying the deployment 202.4.5 IPMI configuration 21

2.5 Updating 21

2.6 Unregistering and uninstalling 22

2.6.1 Unregistering the SV Plug-in package 222.6.2 Uninstalling the SV Plug-in 222.6.2.1 Uninstalling via command line 222.6.2.2 Uninstalling via Windows Control Panel 23

3 Installing on Linux 25

3.1 Provisioning 25

3.2 Requirements 25

3.3 Deploying, configuring and registering the ServerView VMware vCenter Plug-in Appliance 25

3.3.1 Deploying the virtual machine of the ServerView VMware vCenter Plug-in Appliance 253.3.2 Starting the ServerView VMware vCenter Plug-in Appliance 263.3.3 Configuring the ServerView VMware vCenter Plug-in Appliance 27

3.4 Updating 28


Contents

3.5 Unregistering and uninstalling 29

4 Log in to vCenter Server using the vSphere Web Client 31

4.1 Requirements and localization 31

4.2 Procedure 31

4.3 vSphere Web Client user interface 32

5 Configuration tasks and concepts 33

5.1 SVvCenter Service configuration 33

5.1.1 Opening the SVvCenter Service Configuration Overview 335.1.2 Adding a vCenter to the SVvCenter Service 335.1.3 Updating the vCenter credentials 345.1.4 Removing a vCenter from the SVvCenter Service 35

5.2 ServerView Profile Management Service configuration 35

5.2.1 Opening the ServerView Profile Management Overview 365.2.2 Customizing profiles 365.2.2.1 Source code view 375.2.2.2 Configuration wizard 38

5.3 IPMI configuration 40

5.4 FUJITSU PRIMERGY vCenter role definitions and iRMC single sign-on 41

5.4.1 FUJITSU PRIMERGY vCenter role definitions 425.4.2 Changing privileges of a role definition 425.4.3 Starting iRMC functions with/without single sign-on 435.4.3.1 Requirements for single sign-on 435.4.3.2 iRMC functions with single sign-on 435.4.3.3 iRMC S4 Web Interface SSO enhancements 44

5.4.4 Examples of using role definitions to limit iRMC functionality 465.4.4.1 vCenter user "monitor" and iRMC access without SSO (iRMC S2, S3, S4) 465.4.4.2 vCenter user "monitor" and iRMC access with SSO as iRMC user "User" 475.4.4.3 vCenter user "monitor2" and iRMC "User" access and extended privilege

"RemoteStorage" 48

6 SV Plug-in getting started and summary 51

6.1 Entry point 51

6.2 Views on the home page of the SV Plug-in 52

6.3 Getting Started view 52

6.4 Summary view 53

6.5 Plug-in Definitions view 54

6.5.1 Event Definitions 546.5.2 Alarm Definitions 55


Contents

6.5.3 Role Definitions 56

7 Monitoring ESXi-based hosts 58

7.1 Access to the SV Plug-in information of an ESXi-based host 59

7.2 SV Plug-in information of an ESXi-based host 59

7.2.1 Information on the selected host - Status items and views 607.2.2 Agentless management via IPMI 627.2.3 FUJITSU PRIMERGY Actions (iRMC-based operations) 637.2.3.1 Starting a FUJITSU PRIMERGY Action 637.2.3.2 The FUJITSU PRIMERGY Actions 64

7.3 Storage view 66

7.3.1 Prerequisites - information provider for the Storage view 667.3.1.1 Information provider for the Storage view 66

7.3.2 Information on the Storage view 67

7.4 Driver Monitor view 68

7.5 System Event Log view 70

7.6 Monitoring vCenter or cluster host servers 71

7.6.1 Access to the SV Plug-in information of the hosts of a vCenter/cluster 727.6.2 FUJITSU PRIMERGY Actions 73

8 Monitoring FUJITSU PRIMERGY specific nodes 77

8.1 Monitoring CX hosts 77

8.1.1 Number of adjacent hosts for the selected CX host: Inventory Lists - Related Objects 778.1.2 Information on adjacent hosts: Related Hosts tab 78

8.2 Monitoring PRIMERGY blade servers 80

8.2.1 Access to the SV Plug-in information of an MMB 808.2.2 SV Plug-in information of an MMB node 818.2.2.1 Monitor tab: Information on the selected MMB - Status items and views 828.2.2.2 FUJITSU PRIMERGY Actions 84

8.2.3 SVvCenter Service for MMBs 858.2.3.1 Overview 858.2.3.2 SNMP settings 858.2.3.3 Receiving SNMP traps 86

8.3 Monitoring PRIMEQUEST systems 87

8.3.1 Access to the SV Plug-in information of a PRIMEQUEST system 888.3.2 SV Plug-in information of a PRIMEQUEST system 898.3.2.1 Monitor tab: Information on the selected PRIMEQUEST system - Status items and

views 908.3.2.2 FUJITSU PRIMERGY Actions 92


Contents

8.3.3 SVvCenter Service for PRIMEQUEST systems 928.3.3.1 Overview 928.3.3.2 SNMP settings 938.3.3.3 Receiving SNMP traps 93

8.4 Discovering PRIMERGY Bmc Systems (for deploying) 94

8.4.1 PRIMERGY Bmc Systems view 948.4.2 Adding PRIMERGY Bmc Systems to the vCenter inventory 958.4.2.1 Adding a PRIMERGY Bmc System manually 958.4.2.2 Searching for PRIMERGY Bmc Systems 958.4.2.3 Adding a PRIMERGY Bmc System from file 97

8.4.3 SV Plug-in information of a PRIMERGY Bmc Systems 1008.4.3.1 FUJITSU PRIMERGY Actions 101

9 Integration in the event management of the vSphere Web Client 103

9.1 Requirements 104

9.2 SVvCenter Service Configuration Overview 104

9.2.1 Opening the SVvCenter Configuration Overview 1049.2.2 Properties of SVvCenter Services 1059.2.3 Further helpful service properties for the SVvCenter Service for events, MMBs and

PRIMEQUEST systems 1069.2.4 Adding/removing a vCenter to/from the SVvCenter Service 106

9.3 FUJITSU PRIMERGY Predefined Alarm 107

9.4 Actions relating to SVvCenter Service 107

10 Remote Management 109

10.1 LED 109

10.2 iRMC Web Interface 110

10.3 Remote console (AVR) 110

10.4 iRMC system report 111

10.5 eLCM Offline Update 111

11 Offline update via eLCM 112

11.1 Requirements and compatibility warning 113

11.2 Starting points 114

11.3 Offline update via eLCM started from SV Plug-in view 114

11.3.1 Opening the eLCM Offline Update view 11511.3.1.1 Opening the view of a host object 11511.3.1.2 Opening the view of a PRIMERGY Bmc System 115

11.3.2 Checking requirements 11511.3.3 eLCM Offline Update in progress 117


Contents

11.3.4 eLCM Update Workflow details 118

11.4 Offline update via eLCM started from SV Plug-in FUJITSU PRIMERGY Actions menu 119

11.4.1 Starting 119

12 Deploying PRIMERGY Bmc Systems 120

12.1 Requirements 121

12.2 Starting points 122

12.3 Deployment via eIM 122

12.3.1 Opening the deployment wizard 12212.3.1.1 Opening the view of a PRIMERGY Bmc System 12212.3.1.2 Opening the view of Clusters or vCenter Servers 124

12.3.2 Deployment wizard 124

13 Error handling 126

13.1 Time of data acquisition 126

13.2 All expanded items are closed 126

13.3 Retrieving data failed 126

13.4 An action in the top left of the SV Plug-in interface is disabled 126

13.5 An action in the context menu results in an error message 127

13.6 Remote console (AVR) or iRMC Web Client do not work as expected 127

13.7 The same event generates a significant number of entries in the event management 127

13.8 Repeated connection timeouts 127

13.9 Editing a profile failed (using IE 11) 128

13.10 Browsing for PRIMERGY bare metals systems failed (using IE 11) 128

13.11 SV Plug-in cannot connect to the VMware vRealize Orchestrator (using OrchestratorV7.0) 128

13.12 Executing SVSInstallerGUI.sh results in warnings (remote X Server, e.g. MobaXTerm) 129

13.13 vCenter Server Appliance: Executing SVSInstallerGui.sh failed 129


1 OverviewVirtualization solutions from Fujitsu

Fujitsu is committed to total virtualization - from servers to storage to networks - and tovirtualization software and operation management tools. The partnership betweenVMware and Fujitsu brings you continuity of technology assets, more efficient resourceuse, 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 andmanage VMware vSphere-based environments more reliably and securely. Administratorscan view all physical and virtual machines through a single interface.

vSphere Web Client

VMware vSphere provides several interfaces for data center management and virtualmachine access.

Figure 1: VMware vSphere data center physical topology - (Source: http://www.vmware.com/support/pubs/)


1.1 Integration approaches

These interfaces include VMware vSphere Client (vSphere Client), vSphere Web Client foraccess 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 tointeract with the virtual data center environment created by VMware vSphere. The vSphereWeb Client is a Web browser-based application that you can use to manage, monitor andadminister 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 ITinfrastructure. vSphere Web Client can be extended by creating plug-in modules. Acomplete plug-in solution adds new capabilities to the vSphere Web Client graphical userinterface. In this way third-party companies can integrate their GUIs and show informationas desired.

ServerView Suite and vSphere

The ServerView Suite has implemented the ServerView ESXi CIM Provider, which is part ofthe VMware ESXi release. In addition, Fujitsu has implemented the FUJITSU SoftwareServerView Plug-in for VMware vCenter (SV Plug-in), which shows the values of a hostsystem provided by the ServerView ESXi CIM Provider and the LSI CIM provider (Storageview). It is also possible to monitor most of the storage values via IPMI, if the IPMIcredentials are configured. Via IPMI not all the values are available.

The FUJITSU Software ServerView Plug-in for VMware vCenter (SV Plug-in) offers you ahome page with a Getting Started view and a Summary view, which gives an overview ofthe information items provided by the SV Plug-in.

Via the Monitor tabs for ESXi hosts, vCenters, clusters, MMBs and PRIMEQUEST systems, theSV Plug-in provides you with detailed information about FUJITSU PRIMERGY servers. Thisinformation includes properties of the system, fans, temperature sensors, power supplies,system processors, memory modules and the RAID subsystem. If the managed system is aPRIMERGY 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-specificevents to the vCenter event management to be monitored in the vSphere Web Client.

1.1 Integration approachesThe FUJITSU Software ServerView Plug-in for VMware vCenter (SV Plug-in) integratesFUJITSU PRIMERGY-specific information into the vSphere Web Client interface. There are twoapproaches to do this:

Data integration

in the event and alarm management of the vSphere Web Client itself


1.2 Monitoring and managing possibilities

Full sites integrated

in the vSphere Web Client offer the FUJITSU PRIMERGY-specific data of ESXi hosts, hostsof vCenters or clusters, MMBs and PRIMEQUEST systems


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 orPRIMEQUEST systems: Status icons provide quick information. Detailed views provide moreinformation on a selected host.

And a number of FUJITSU PRIMERGY action items support calling a monitoring tool ormaking settings on the host.

In regular operation the SV Plug-in generally shows the values of a host systemprovided by the ServerView ESXi CIM Provider. If a host has an older version of theServerView 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 IPMIcredentials are configured. See "Agentless management via IPMI" on page 62. ViaIPMI not all the values are available. You can toggle between CIM and IPMIcommunication interfaces.

Storage view

The Storage view offers an overview of the RAID controllers found on the host and detailsof their logical drives and physical disks.



If ServerView ESXi CIM Provider V8.0 or higher and ServerView RAID Core Provider areinstalled, the ServerView ESXi CIM Provider provides the information, on which the Storageview of the SV Plug-in is based. Otherwise, the information comes from the LSI CIMprovider.

Driver Monitor view

Via the Driver Monitor view you can monitor and manage events relating to thecomponents 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 alsoview 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 lessinformation on the individual host via this access point than via the inventory tree itemHosts, 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 ESXiplaced 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 SVPlug-in adds the new inventory list PRIMERGY Blade Server to the object navigatorvCenter 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 customobject types, the object navigator vCenter level has to be extended with a new inventorylist. The SV Plug-in adds the new inventory list PRIMEQUEST Server to the object navigatorvCenter 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-specificevents to the vCenter event management to be monitored in the vSphere Web Client. If aFUJITSU PRIMERGY host detects a problem, it will create a CIM indication and send it tosubscribed destinations. An alarm is also created and can be configured for furtheractions. If SVvCenter Service is subscribed to the host, it will receive the CIM indication. Itcreates a vCenter event and forwards it to vCenter Server. So the FUJITSU PRIMERGY-specificevent is shown in the regular Monitor-Events sub-tab of the vSphere Web Client.


1.3 What’s new

Remote Management possibilities: Remote console (AVR), iRMC Web interface andsystem 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 theadministrator 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 remoteconsole. There are FUJITSU PRIMERGY vCenter role definitions designed for using singlesign-on when starting the iRMC Web interface and remote console.

If the managed system is a PRIMERGY blade server, you can start the Configuration WebApplication of its management board (MMB) as well.

To simplify service tasks, the SV Plug-in allows you to turn the system identification LED ofthe 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 toautomatically download files from a repository server via the dedicated iRMC S4management 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-into deploy the ESXi operating system via ServerView profiles. The FUJITSU SoftwareServerView Plug-in for VMware vRealize Orchestrator Deployment provides the deploymentworkflow.

embedded Installation Management (eIM) is the eLCM equivalent to the well-provenServerView Installation Manager. Stored on the iRMC S4 SD card for immediate use, noexternal ServerView media needed to set up and install FUJITSU PRIMERGY systems.

1.3 What’s newThis edition of the manual applies to FUJITSU Software ServerView Plug-in for VMwarevCenter 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:

l The values of the Storage view can be provided by the ServerView ESXi CIM Providerdepending on its version, see "Storage view" on page 66.

l Fujitsu has implemented the ServerView VMware vCenter Plug-in Appliance forinstalling the SV Plug-in on Linux. The appliance offers a pre-installed virtual machine


1.4 Target groups and purpose of this manual

based on CentOS 6.9 and including the SV Plug-in installation, which you can deployon an ESXi host. For further information see "Installing on Linux" on page 25.

1.4 Target groups and purpose of this manualThis manual is intended for system administrators, network administrators and servicetechnicians who already have a basic knowledge of hardware and software.

The manual explains how you can monitor a VMware vSphere-based server withServerView and vSphere, and describes how to deploy the FUJITSU Software ServerViewPlug-in for VMware vCenter.

1.5 Documentation for the ServerView SuiteThe documentation can be downloaded free of charge from the Internet. You will find theonline documentation at http://manuals.ts.fujitsu.com under the link x86 Servers.

ServerView Sitemap

For an overview of the documentation to be found under ServerView Suite as well as thefiling 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 AbbreviationsSV Plug-in

In the following, SV Plug-in is short for FUJITSU Software ServerView Plug-in forVMware vCenter.

1.7 Typographic conventionsThe following typographic conventions are used:


http://manuals.ts.fujitsu.com/

http://manuals.ts.fujitsu.com/files/html/primergy/svs-sitemap/sitemap_emea_en/index.html

1.7 Typographic conventions

Convention Explanation

Indicates various types of risk, namely health risks, risk of data lossand risk of damage to devices.

Indicates additional relevant information and tips.

bold Indicates references to names of interface elements.

monospace Indicates system output and system elements for example, filenames and paths.

monospacesemibold

Indicates statements that are to be entered using the keyboard.

blue continuoustext

Indicates a link to a related topic.

pink continuoustext

Indicates a link to a location you have already visited.

<abc> Indicates variables which must be replaced with real values.

[abc] Indicates options that can be specified (syntax).

[key] Indicates a key on your keyboard. If you need to enter text inuppercase, the Shift key is specified, for example,[Shift] + [A] for A. Ifyou need to press two keys at the same time, this is indicated by aplus sign between the two key symbols.

Screenshots

Some of the screenshots are system-dependent, so some of the details shown may differfrom your system. There may also be system-specific differences in menu options andcommands.


2 Installing on WindowsThe installation package includes both SV Plug-in and its vCenter services.

The installer contains basically an executable which requests all required parameters, anda list of installers. The installer is started with a GUI.

2.1 ProvisioningYou can obtain the SV Plug-in in the following ways:

l Download from the Fujitsu website support.ts.fujitsu.com:

1. Choose Servers - PRIMERGY server - <server model> - Applications - ServerManagement Software - VMware Integration Solutions.

l Download from the ServerView Suite DVD.

2.2 Requirementsl 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

l Verify that vCenter Server is installed and that both vCenter Server and vSphere WebClient point to the same vCenter single sign-on instance.

l Java runtime V1.7.40 or higher.

l FUJITSU Software ServerView Plug-in for VMware vRealize Orchestrator V1.4 or higher


http://support.ts.fujitsu.com/

2.3 Installation notes

2.3 Installation notesInstaller 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 ApacheTomcat 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 SVvCenterService: If another vCenter system (vC2) is within the same single sign-on environment, itis possible to connect this vCenter (vC2) to the SVvCenter Service (Service1) of a vCenterinstance (vC1).

In this case, once you have entered the user name and password, the vCenter (vC2) will bemonitored by the SVvCenter Service (Service1) and the SV Plug-in will be registered onvCenter (vC2) as well. The SV Plug-in will be available for the hosts on vCenter (vC2), andyou can monitor their values.

Because the SV Plug-in will be registered on vCenter (vC2) as well, it is not necessary toperform a second installation. If you disconnect a vCenter, the SV Plug-in will beunregistered from that vCenter.

2.4 Installing and registeringA plug-in package contains all the plug-in modules in an extension solution along with apackage manifest. The package manifest provides deployment information for each plug-in module using XML metadata. The vSphere Web Client Extension Manager uses thismetadata to install and deploy each plug-in module in the plug-in package.


2.4 Installing and registering

You deploy a plug-in package to the vSphere Web Client by registering the package as anextension on vCenter Server. When you do this, your solution becomes available to anyvSphere Web Client that connects to your vSphere environment.

When a vSphere Web Client establishes a user session to vCenter Server, the vSphere WebClient application server queries vCenter Server for a list of all available plug-in packagesthat are registered as vCenter extensions. Any plug-in packages that are not present onthe 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, thecorresponding language will be selected for installing the SV Plug-in.In the case of other operating system languages, English is the default for installingthe SV Plug-in.

The SV Plug-in package:

The SV Plug-in package consists of the following folders:

l common

General installation files.

l documentation

Further documentation.

l legal

Documents like End User License Agreement (EULA).

l linux

Installation files required for linux.

l windows

Installation files required for windows.

2.4.1 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 theWindows folder (see "The SV Plug-in package:" on page 17) execute theSVSInstaller.exe file on the vCenter Server system with administrator privileges (run asAdministrator).

The installer is started with graphical user interface (GUI) and the necessaryparameters are requested via this user interface.



2.4.2 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 thenecessary 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 portsare checked for usage. If they are in use by another program, proceeding isdenied.

Service account: Use local service? / Service account: Username - Password

The Web server has to run under a user account without administratorprivileges.

You’ve got two options:

l It is possible to use the in-built account LocalService.

l You can specify an existing user account.

6. Click Next.



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 aregistration already exists for a vCenter Server system, you will be notified andthe 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 onwhich the SV Plug-in is registered is no longer reachable, a dialog box with aforce uninstall option will be displayed. If you choose forced uninstall, theregistration 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 mustensure that your entries Name of the Plug-In service station and DNS suffixof 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 andpassword 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 andpassword 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 beunregistered 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 "SNMPsettings" on page 85.

The setting SNMP community strings (comma separated) is used to searchfor blade servers, see "SNMP settings" on page 85.



8. Click Install.

The progress of the installation process is displayed.

The process of deploying package by package will be a few more minutes. ThevCenter Service is one of the last packages to deploy. But only this vCenterService registers with vCenter. Therefore the SV Plug-in will be indicated invCenter pretty late only.

2.4.3 Finished installation notes

To ensure consistency between vCenter Server extension registration and Web Clientclient plug-in administration, you should restart all vSphere Web Client services thatuse the SV Plug-in.

It is recommended that you clear both the Java cache and browser cache be afterthe 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 tovSphere Web Client can take significantly longer.

If another vCenter (vC2) is within the same single sign-on environment, it ispossible to connect this vCenter to the SVvCenter Service (Service1) of one vCenter(vC1) without a second installation (see "Installation note: Several vCenters - oneinstallation " on page 16).

2.4.4 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 thefully-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 Serversystem and add /mob.

For example: https://<domain 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 SVPlug-in is installed, login can take longer than usual (up to several minutes).


2.5 Updating

If warning messages about the SSL certificate appear, you can ignore them andcontinue logging in to the vCenter Managed Object Browser, if VMware is thecertificate 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 anentry: com.fujitsu.primergy.eventservice.

Additional check:

You will find a new SVvCenter Service dialog in the overview and administration pages ofthe SV Plug-in, see "Summary view" on page 53 and "SVvCenter Service configuration" onpage 33.

2.4.5 IPMI configuration

The IPMI credentials (user name and password) must be configured to have access to anumber of iRMC based actions on an ESXi host:

l Toggle Identify LED

l Start the iRMC Web Interface with single sign on

l Start the Remote Console (AVR)

l Start a System Report

l Start an eLCM Offline Update Workflow

In addition, when the credentials are configured, it is possible to view monitoring datafrom 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 "IPMIconfiguration" on page 40.

2.5 UpdatingDue to technical restrictions, an upgrade installation can only be performed for SVPlug-in V2.1.4 or later. Before the SV Plug-in can be installed, the previous versionmust be installed.


2.6 Unregistering and uninstalling

If you have changed the privileges in one of the FUJITSU PRIMERGY role definitionsand 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.1 Unregistering the SV Plug-in package

If you want to unregister and uninstall the SV Plug-in, see "Uninstalling the SV Plug-in" on page 22.

You can unregister the SV Plug-in package using the vCenter Managed Object Browserinterface (see "Verifying the deployment" on page 20).

Several vCenters - one installation (see "Installation note: Several vCenters - oneinstallation " 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 packagefiles that are installed locally on the vSphere Web Client Virgo server. The files are nolonger used after the package has been unregistered, but if you want to remove them forcleanup purposes, you must remove them manually. You can remove the files installed onthe vCenter Server and unregister the SV Plug-in in one step by using the uninstallprocedure (see "Uninstalling the SV Plug-in" on page 22).

2.6.2 Uninstalling the SV Plug-in

There are two ways for uninstalling:

l via command line

l via the Windows Control Panel

If the vCenter Server on which the SV Plug-in is registered is no longer reachable, adialog box with a force uninstall option will be displayed.

You should only use this option if the vCenter Server system has failed.

2.6.2.1 Uninstalling via command line

The application SVSInstaller.exe is copied to the target system:



l <PROGRAMFILES>\Fujitsu\ServerView Suite\SVSInstaller (default path)

or

l <selected path>\SVSInstaller (custom path)

In this folder execute the SVSInstaller.exe file:

\SVSInstaller.exe -u

2.6.2.2 Uninstalling via Windows Control Panel

Basically, there is the entry FUJITSU Software ServerView Installer. The packages aregiven 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 ServerViewInstaller 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



Click the button Uninstall.

The entry FUJITSU Software ServerView Installer is no longer displayed.


3.1 Provisioning

3 Installing on LinuxFujitsu has implemented the ServerView VMware vCenter Plug-in Appliance for installingthe SV Plug-in on Linux. The appliance offers a pre-installed virtual machine based onCentOS 6.9 and including the SV Plug-in installation, which you can deploy on an ESXihost.

3.1 ProvisioningYou can obtain the SV Plug-in in different ways (see "Provisioning" on page 15).

3.2 Requirementsl The vCenter/ vSphere version of the VMware vCenter Server must be at least V6.

l 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 ServerViewVMware vCenter Plug-in Appliance

3.3.1 Deploying the virtual machine of the ServerView VMware vCenterPlug-in Appliance

After downloading the OVA file, you can deploy it using the VMware vSphere Client orvSphere Web Client.

Before you begin: Identify the DNS records and host name to use for your connectorOVA deployment.

Procedure:

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.


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 canview 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 nocorresponding device is available on the host. Do you wantto try to connect this virtual device every time you poweron 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.

3.3.2 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 Appliancevia Web user interface.


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

3.3.3 Configuring the ServerView VMware vCenter Plug-in Appliance

Before you begin: Use either Firefox or Chrome browsers. Using Internet Explorercould cause problems.

1. Start the Web UI of the ServerView VMware vCenter Plug-in Appliance in a webbrowser.

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 isdisplayed.

3. Select the System tab.

Figure 6: ServerView VMware vCenter Plug-in Appliance Web UI: System Information

4. Configure time zone and system parameters.


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 forvCenter Server:.

9. Click Install and Register.

The input fields in the vCenter tab are grayed out and in the Extension Address fieldPENDING is displayed.

Installation and registration may take up to 30 minutes.

After installation and registration are finished LOCAL is displayed in the ExtensionAddress field.

3.4 Updating1. Download the latest iso image of the ServerView VMware vCenter Plug-in Appliance,

see "Provisioning" on page 25.

2. Provide the iso image on DVD in vCenter.

3. Start the Web UI of the ServerView VMware vCenter Plug-in Appliance in a web



browser.




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 uninstallingIt is necessary to unregister and uninstall the ServerView VMware vCenter Plug-inAppliance before removing the virtual machine of the appliance. Otherwise theregistration on the vCenter server will persist. You will have to remove it by usingMOB.

1. Start the Web UI of the ServerView VMware vCenter Plug-in Appliance in a webbrowser.




3. Select the vCenter tab.



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-inAppliance.


4.1 Requirements and localization

4 Log in to vCenter Server using the vSphere WebClient

4.1 Requirements and localizationRequirements:

vCenter Server and vSphere Web Client

Verify that vCenter Server is installed and that both vCenter Server and vSphere WebClient point to the same vCenter single sign-on instance.

Internet Explorer 11:

You must configure a certain option under Internet Properties. If this option isnot checked, editing a profile (see "Customizing profiles" on page 36) orbrowsing 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 Ivisit the webpage.

Localization:

The languages supported for using the SV Plug-in are English, German andJapanese.If the browser language matches one of these languages, the correspondinglanguage will be selected for the SV Plug-in.

4.2 Procedure1. Open a Web browser and enter the URL for the vSphere Web Client:

https://client-hostname:port/vsphere-client

By default the port is 9443, but this can be changed during vSphere Web Clientinstallation

2. In the Username text box, enter the user name that is registered on the vCenter singlesign-on and has permissions on vCenter Server.

3. In the Password text box, enter the password.


4.3 vSphere Web Client user interface

4. Click Login.

The vSphere Web Client connects to all the vCenter Server systems that the specifieduser 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: www.vmware.com)

The user interface layer of the vSphere Web Client contains all the Flex objects, such asdata views, toolbars and navigation interfaces, that make up the vSphere Web Clientgraphical user interface.

The main parts of the vSphere Web Client user interface are the object navigator, the mainworkspace and the tasks and alarms panel. Your selections in the object navigator drivethe contents of the vSphere Web Client main workspace.

In the object navigator vCenter level, vSphere objects are organized into inventory treesand inventory lists. When you select an object in the object navigator, information aboutit appears in the main workspace.

When you browse the virtual infrastructure using the object navigator, the mainworkspace displays an object workspace.


5.1 SVvCenter Service configuration

5 Configuration tasks and concepts

5.1 SVvCenter Service configurationYou can use the SVvCenter Service Configuration Overview to manage all the SVvCenterServices installed in your environment.

For performance reasons we recommend one SVvCenter Service per vCenter server.

5.1.1 Opening the SVvCenter Service Configuration Overview

At the bottom of the getting started tab on the home page of the SV Plug-in, youwill 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 ConfigurationOverview 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) byclicking the pencil icon seen in this section. SVvCenter Service must beconfigured as a trap destination on the registered MMBs.

For further information see "Properties of SVvCenter Services" on page 105.

5.1.2 Adding a vCenter to the SVvCenter Service

The following procedure will help if a connection problem with a SVvCenterService occurs: If a vCenter is connected to a failing SVvCenter Service and youconnect it to another SVvCenter Service, the vCenter will be disconnected fromthe failing SVvCenter Service and added to the new one.


5.1 SVvCenter Service configuration

If you have changed the privileges in one of the FUJITSU PRIMERGY roledefinitions and you connect the vCenter (to which the role is assigned) toanother SVvCenter Service, the role definitions will be overwritten! See"Changing privileges of a role definition" on page 42.

1. In the SVvCenter Service Configuration Overview, select a SVvCenter Service in theService 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 subscribesto the hosts found in the vCenter, and forwards any indications or traps to thevCenter.

5.1.3 Updating the vCenter credentials

It may be necessary to update the credentials of a vCenter (e.g. if the administratorpassword has changed).


5.2 ServerView Profile Management Service configuration

1. In the SVvCenter Service Configuration Overview, select a SVvCenter Service in theService Location selection box.


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.

5.1.4 Removing a vCenter from the SVvCenter Service

A SVvCenter Service requires at least one vCenter to be connected. Therefore, it isonly possible to disconnect a vCenter if more than one vCenter is connected. Todisconnect all vCenters from a SVvCenter Service, uninstall the SVvCenter Service.

1. In the SVvCenter Service Configuration Overview, select one SVvCenter Service in theService Location selection box.


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 configurationBare metal PRIMERGY systems without an operating system can be added to the SV Plug-into 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 BmcSystems to the vCenter inventory" on page 95.

2. Store a customized ServerView profile under FUJITSU PRIMERGY Administration, see"Opening the ServerView Profile Management Overview" on page 36.

3. Deploy the ESXi operating system via the ServerView Deployment vRealize OrchestratorWorkflow, see "Deploying PRIMERGY Bmc Systems" on page 120.

The ServerView Profile Management Service is part of the SV Plug-in. The service allows youto store custom profiles.



Each profile is defined in a JSON-formatted file. The file contains information aboutrepository configuration, network configuration and user data. The profile file will be sentto the SysRollout service to configure a PRIMERGY Bmc System.

5.2.1 Opening the ServerView Profile Management Overview



3. Select the sub-item ServerView Profile Management.

In the main workspace of the vSphere Web Client the ServerView Profile Managementoverview opens.

Default Profiles

Under Default Profiles you find a list of the predefined profiles which come withthe SV Plug-in:

Without adaptations these Default Profiles are not suitable for deploying.

Template ESXi IDE

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 ESXioperating system.

Template ESXi Raid Configuration

For a PRIMERGY Bmc System which needs a RAID configuration.

Customize this profile according to your needs:

l Export the profile definition.

l Adjust the RAID parameters according to your needs.

l Import the changed profile and save it as an custom profile - see"Customizing profiles" on page 36.

4. Click the arrow in front of the desired profile to expand the entry.

A summary of the values of this profile is shown.

5.2.2 Customizing profiles

You can configure your own profiles according to your needs. Use the Default Profiles andcustomize it (see "Opening the ServerView Profile Management Overview" on page 36). To



get a template you can prepare a profile leaving some values blank.

Working connections are prerequisite for handling profiles. Therefore theseconnections are regularly checked. If the Profile Management Service can not beconnected, you can not configure profiles.

If VMware vRealize Orchestrator is not connected to the vCenter or the FUJITSU SoftwareServerView Plug-in for VMware vRealize Orchestrator Deployment is not installed, you cannot start deployment processes.

Related error messages are displayed in the ServerView Profile Management overviewunder 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

Starts the configuration wizard - see "Configuration wizard" on page 38.

Edit

Starts the configuration wizard - see "Configuration wizard" on page 38.

View

Opens a window showing the source code of the profile definition - see "Sourcecode view" on page 37.

Delete

Deletes the selected profile.

5.2.2.1 Source code view

Clicking the icon opens a window showing the source code of the profile definition.



Figure 11: Profile definiton view

1. Click the Save button to save changes.

5.2.2.2 Configuration wizard


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:

l You can use a default profile or an existing custom profile as basis for yournew profile.

Select the desired profile from the list under Default Profile.

l Import a profile definition using the Browse button under Import File.



The imported profile must defined in a JSON-formatted file. The file willbe parsed and proved to be valid.

3. 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 duringthe deployment (firewalls etc.). The configuration of ESXi must match the ISOimage.

Security issue: The password is stored in plain text. For security reasons fill it injust 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 duringthe deployment (firewalls etc.).The configuration of ESXi must match the ISO image.


5. User Data Information


If the password is entered, it must match the entry in the field ConfirmPassword.

6. Common Network Information

There are two options:

l Using DHCP

l Under Manual Network Configuration you can configure individual networkparameters: Network Gateway (mandatory), IP Mask (mandatory), DomainName (mandatory), DNS Server (mandatory).

7. Save Profile

Summarizes the configuration.

Click the Finish button to store the new profile in the Profile Management Service.


5.3 IPMI configuration

5.3 IPMI configurationThe user name and password for IPMI configuration must be configured in vCenter Serverto perform certain operations:

Be careful when editing the credential information. If invalid credentials areentered, it may take a few minutes before you see an error message. If the IPMI isconfigured and the wrong credentials are entered, the configuration will take placeno change.

ESXi host:

The IPMI credentials (user name and password) must be configured to have access toa number of iRMC based actions on an ESXi host:







Procedure:

The iRMC user account must have the LAN channel privilege of Administrator orOEM to use single sign-on when starting iRMC, or to start other IPMI actions fromthe SV Plug-in. It is possible, however, to limit the iRMC privileges depending on therole of the current vCenter user. For more information see "Starting iRMC functionswith/without single sign-on" on page 43.

1. Log in to vCenter Server using the vSphere Web Client (see "Log in to vCenter Serverusing the vSphere Web Client" on page 31).

2. Start the FUJITSU PRIMERGY Action Configure IPMI (for an ESXi host see: "Starting aFUJITSU PRIMERGY Action" on page 63).

3. Click the item/icon IPMI Configuration.

The following dialog is displayed:


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 thisin the case of changes (e.g. if the credentials have been changed on the host).

5.4 FUJITSU PRIMERGY vCenter role definitions and iRMCsingle sign-onFour new role definitions have been added to the SV Plug-in. They are designed for usingsingle sign-on when starting the iRMC Web Interface and remote console (AVR). All roledefinitions 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 "FUJITSUPRIMERGY vCenter role definitions" on page 42.

It is possible to add the extended iRMC privileges to a FUJITSU PRIMERGY vCenter roledefinition, see "Starting iRMC functions with/without single sign-on" on page 43. You canalso 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 SVPlug-in (see "Role Definitions" on page 56) lists the predefined FUJITSU PRIMERGY roles. Ifthe role definitions have been reconfigured after installation, the changes relevant tocorrect processing of the SV Plug-in will be marked.



5.4.1 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 usingsingle 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 startthe iRMC Web Interface using single sign-on with the iRMC LAN channel privilege ofOperator, plus the extended iRMC privileges ConfigureBMC, RemoteStorage and AVR.

The user can make some configuration changes (but, for example, no firmwarechanges).

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-onwith the iRMC LAN channel privilege of Operator, plus the extended iRMC privilegeAVR.

The user will be able to perform shutdown/reboot on the host, but cannot make anyconfiguration changes.

The user can also acknowledge alarms.


FUJITSU PRIMERGY Plug-in Monitor

Contains only the privileges need to start the iRMC Web Interface using single sign-onwith the iRMC LAN channel privilege of User, plus the extended iRMC privilege AVR.


5.4.2 Changing privileges of a role definition

The Role Definitions sub-tab of the Plug-in Definitions view on the home page of the SVPlug-in lists the predefined FUJITSU PRIMERGY role definitions, which are generated duringthe installation process (see "Role Definitions" on page 56).

If the role definitions have been reconfigured after installation, the changes relevant tocorrect 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 userinterface.



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 SVvCenterService, the role definitions will be overwritten!


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.

5.4.3 Starting iRMC functions with/without single sign-on

Single sign-on can be used when starting the iRMC functions as Administrator. If the hosthas an iRMC S4 firmware version which is at least V7.73F, the SSO environment isenhanced to allow single sign-on for less-privileged users. When starting the iRMC WebInterface, their iRMC LAN channel privilege will be adjusted to match the privilege level ofthe vCenter user.

5.4.3.1 Requirements for single sign-on

To perform the iRMC functions with single sign-on, the following requirements must bemet:

l The IPMI credentials must be configured with an iRMC user account that has theAdministrator / OEM LAN channel privilege (see "IPMI configuration" on page 40).

l The vCenter user must have the privileges defined in the FUJITSU PRIMERGY roledefinitions. The SV Plug-in role Administrator can perform single sign-on, but less-privileged users will only be able to use single sign-on with an iRMC S4 whosefirmware version is at least V7.73F.

5.4.3.2 iRMC functions with single sign-on

Location button LED

If the IPMI credentials have been configured (see "IPMI configuration" on page 40), anyvCenter 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 definedin the FUJITSU PRIMERGY Plug-in Administrator role (see "FUJITSU PRIMERGY vCenter role



definitions" on page 42); however, AVR can be started by any user from within the iRMCWeb Interface.

iRMC Web Interface

If the vCenter user has the privileges defined in the FUJITSU PRIMERGY Plug-inAdministrator role (see "FUJITSU PRIMERGY vCenter role definitions" on page 42), they willbe able to start iRMC with single sign-on.

In all other cases, iRMC can be started via login by the iRMC user.

5.4.3.3 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 accesswill be extended to the vCenter users with the Super Operator, Operator and Monitorroles.

The iRMC S4 Web Interface can be started with one of three iRMC roles:

l Administrator

l Operator

l User

iRMC extended privileges

iRMC also offers four extended privileges which can be granted together with the roles:

l ConfigureBMC - perform system configuration on the host

l AVR - start AVR (Advanced Video Redirection)

l ConfigureUsers - configure user accounts (iRMC, CAS, LDAP)

l RemoteStorage - perform remote image and media operations

These extended privileges can be used together with the iRMC roles. All users can start AVRfrom within the iRMC Web Interface. Since the ConfigureBMC privileges allow extensiveaccess to iRMC configuration functionality, it is recommended to use the predefined SVPlug-in Super Operator role (see "FUJITSU PRIMERGY vCenter role definitions" on page 42).

The RemoteStorage and ConfigureUsers privileges map to just one vCenter privilege:

l RemoteStorage : Host.Config.Storage

l ConfigureUsers : Host.Local.ManageUserGroups

So they can be easily added to a SV Plug-in Operator or Monitor role (see "Examples ofusing role definitions to limit iRMC functionality" on page 46.

Correlation between the FUJITSU PRIMERGY SV Plug-in roles and iRMC S4 Web Interfacefunctionality

The following table shows the correlation between the FUJITSU PRIMERGY SV Plug-in roledefinitions and iRMC S4 Web Interface functionality:



Predefined FUJITSUPRIMERGY vCenterrole definition

iRMC LAN channelprivilege

iRMC Web Interface functionality

FUJITSU PRIMERGYPlug-in Administrator

Administrator Can perform all functions of the iRMCWeb Interface

l View settings and information

l Toggle location button LED on/off

l Perform system shutdown/reboot

l Remote image mount

l Configure media options

l Configure system settings

l RAID configuration

l Prime Collect

l AIS Connect

l System report

l BIOS backup and update

l iRMC reboot and update

l Internal event log view/clear

l Configure users

l Start AVR

FUJITSU PRIMERGYPlug-in Super Operator

Operator +

ConfigureBMC

RemoteStorage

AVR






l Configure system settings

l Start AVR

FUJITSU PRIMERGYPlug-in Operator

Operator +RemoteStorage AVR






l Start AVR



Predefined FUJITSUPRIMERGY vCenterrole definition

iRMC LAN channelprivilege

iRMC Web Interface functionality

FUJITSU PRIMERGYPlug-in Monitor

User +

AVR

l View limited set of settings andinformation


l Start AVR

5.4.4 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 theiRMC with single sign-on.

The administrator might wish to create a user with very limited privileges. The user shouldbe able to start the iRMC Web Interface with the LAN channel privilege of User, but notmake any changes on the system or perform a system shutdown.

1. A user is created (for examplemonitor).

2. The target (vCenter, cluster or single host) is configured to have the permission:

l user: monitor

l role: FUJITSU PRIMERGY Plug-in Monitor

5.4.4.1 vCenter user "monitor" and iRMC access without SSO (iRMC S2, S3, S4)

Situation:

l When the user logs in, they can start the iRMC Web Interface, but must log in using aniRMC user name and password.

l They will have the LAN channel privileges corresponding to that account.

l The IPMI credentials will not be used.



vSphere Web Client:

User without SSO privileges (and iRMC firmware version below V7.73F) or no IPMIcredentials 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

5.4.4.2 vCenter user "monitor" and iRMC access with SSO as iRMC user "User"

Situation:

l To provide SSO access for a Super Operator, Operator or Monitor vCenter user, a hostmust have an iRMC S4 with a firmware version of at least V7.73F.

l The IPMI credentials must be configured with an iRMC user who has the LAN channelprivilege of Administrator / OEM (see "Starting iRMC functions with/without singlesign-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 theyonly 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-inMonitor role, IPMI credentials are configured (admin / admin) and the host has a newversion of iRMC firmware which is at least V7.72F.



Figure 15: Example: vCenter user "monitor" and iRMC access with SSO as iRMC user "User" - vSphere WebClient

SV Plug-in:

The figure below shows the iRMC Web Interface with the user admin logged in but with theLAN channel privilege user. The user admin can only perform actions that are allowed fora user (e.g. Toggle location button LED) but cannot perform system shutdowns orconfigure the system in any way.

Figure 16: Example: vCenter user "monitor" and iRMC access with SSO as iRMC user "user" - SV Plug-in

5.4.4.3 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 beable to start iRMC S4 with SSO as the iRMC user User, but also be able to mount a remoteimage.

In this case it is necessary to grant the role more privileges than are predefined.



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-inversion, or connect the vCenter to another SVvCenter Service, the role definitions willbe 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 ofadministrator 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 theFUJITSU 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 startthe iRMC Web Interface:

Figure 17: vCenter user "monitor2" and iRMC "User" access and extended privilege "RemoteStorage" -vSphere Web Client



SV Plug-in:

The user is logged in as the iRMC administrator admin, but only with the LAN channelprivilege 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


6.1 Entry point

6 SV Plug-in getting started and summaryThe SV Plug-in home page FUJITSU PRIMERGY starts with a Getting Started view. The linksunder the navigator tree item FUJITSU PRIMERGY offer the views of the SV Plug-in homepage. The FUJITSU PRIMERGY Summary view gives an overview of the information itemsprovided by the SV Plug-in. There is also a Plug-in Definitions view, which lists all FUJITSUPRIMERGY events and shows the FUJITSU PRIMERGY alarms and the role definitions that canbe used to assign permissions to an entity (see "FUJITSU PRIMERGY vCenter role definitionsand iRMC single sign-on" on page 41).

6.1 Entry pointOn the Home page of the vSphere Web Client you will find two links:

l In the object navigator of the vSphere Web Client the link FUJITSU PRIMERGY.

l 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


6.2 Views on the home page of the SV Plug-in

6.2 Views on the home page of the SV Plug-inThe 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 generalinformation 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 itemsprovided 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 sub-tabs, 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 theSV Plug-in lists the event definitions that are set by the SV Plug-in (see "EventDefinitions" on page 54).

The Alarm Definitions sub-tab of the Plug-in Definitions view on the home page of theSV Plug-in lists the predefined FUJITSU PRIMERGY alarms (see "Alarm Definitions" onpage 55).

The Role Definitions sub-tab of the Plug-in Definitions view on the home page of theSV 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 andiRMC single sign-on" on page 41).

6.3 Getting Started view1. 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 informationabout 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).


6.4 Summary view

Manage the ServerView vCenter Services

Links to the SVvCenter Service Configuration Overview view (see "Integration in theevent management of the vSphere Web Client" on page 103 and "SVvCenter Service forPRIMEQUEST systems" on page 92).

Manage ServerView Profiles for Deployment

Links to the ServerView Profile Management overview (see "Opening the ServerViewProfile Management Overview" on page 36).

ServerView Plug-in Manual

Links to the online version of the user guide FUJITSU Software ServerView Plug-in forVMware vCenter.

6.4 Summary view1. 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 providedby 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. Youcan 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


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 canalso 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 thisPRIMEQUEST system (see "SV Plug-in information of a PRIMEQUEST system" onpage 89).

Cluster Views

An overview of all clusters discovered by the SVvCenter Service. You can also see thestatus of the hosts of the clusters.

1. Click the title of an item box to open the view with detailed information about thiscluster (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 thestatus of the hosts of the vCenters.

1. Click the title of an item box to open the view with detailed information about thisvCenter (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 ofthe hosts of the SVvCenter Services.

1. Click the title of an item box to open the view with detailed information about thisSVvCenter Service (see "Properties of SVvCenter Services" on page 105).

6.5 Plug-in Definitions view1. 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.

6.5.1 Event Definitions

The Event Definitions sub-tab of the Plug-in Definitions view on the home page of the SVPlug-in lists the event definitions that are set by the SV Plug-in. If you have more than one



vCenter in your environment, you can choose which vCenter you would like to view thedefinitions for under Providers.

If the hosts are monitored by the SVvCenter Service, these indications will be forwarded tothe vCenter event management (see "Integration in the event management of the vSphereWeb Client" on page 103). The SVvCenter Service also listens to SNMP traps sent byregistered 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 andcan be sorted according to these items.

More information on the selected list entry is displayed on the right.

6.5.2 Alarm Definitions

The Alarm Definitions sub-tab of the Plug-in Definitions view on the home page of the SVPlug-in lists the predefined FUJITSU PRIMERGY alarms. If you have more than one vCenterin your environment, you can choose which vCenter you would like to view the definitionsfor under Providers.



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 thetarget 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 andare disabled. To use them you must enable them, and possibly configure an action foreach.

The Defined In field gives you the name of the vCenter in which this alarm is defined. Thisname 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 nameof the vCenter in the Defined In field.

6.5.3 Role Definitions

The Role Definitions sub-tab of the Plug-in Definitions view on the home page of the SVPlug-in lists the predefined FUJITSU PRIMERGY roles. If you have more than one vCenter inyour environment, you can choose which vCenter you would like to view the definitions forunder Providers.

This view shows the FUJITSU PRIMERGY vCenter role definitions that are generated duringthe installation process. They describe the minimum privilege level to perform SV Plug-inactions and can be used to assign permissions to an entity. For more information see"FUJITSU PRIMERGY vCenter role definitions" on page 42.



For more information about the concept and about using these role definitions to limitiRMC functionality, see "FUJITSU PRIMERGY vCenter role definitions and iRMC single sign-on" 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 roledefinition is assigned. You can also see the user to whom the role definition has beenassigned.

If the role definitions have been reconfigured after installation, the changes relevant tocorrect processing of the SV Plug-in will be marked as follows:

*

This privilege was not predefined and has been added after installation. It is notrequired for correct processing of the SV Plug-in.

*** (in red)

This privilege is missing. It has been removed since installation and must be addedagain for correct processing of the SV Plug-in.


7 Monitoring ESXi-based hostsThe 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 systemprovided by the ServerView ESXi CIM Provider. If a host has an older version of theServerView 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 storagevalues via IPMI, if the IPMI credentials are configured. See "Agentless managementvia IPMI" on page 62. Via IPMI not all the values are available. You can togglebetween 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 considerthe privileges of the current user - see "Starting iRMC functions with/without single sign-on" on page 43.

Integration in event management of the vSphere Web Client

The SV Plug-in includes the SVvCenter Service, which routes FUJITSU PRIMERGY-specificevents 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. Systemcomponents such as network or storage controller firmware can be updated using theoffline update mode.

The SV Plug-in allows you to start an offline update via eLCM on a host (see "Offlineupdate via eLCM" on page 112).


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-basedhost1. 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 "MonitoringCX hosts" on page 77.

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 SVPlug-in.

The FUJITSU PRIMERGY second-level tab is only available if two conditions aremet:

l The vendor of the selected host is Fujitsu.

l The version of the ESXi operating system is at least V5.0.

5. 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



7.2.1 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 CIMProvider on the host. Whenever you click the status item tree, the SV Plug-inretrieves 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 systemprovided by the ServerView ESXi CIM Provider. If a host has an older version of theServerView 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 IPMIcredentials are configured. See "Agentless management via IPMI" on page 62. ViaIPMI not all the values are available. You can toggle between CIM and IPMIcommunication 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.

l 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 ofthe status item tree.

unknown

retrieving data

l You can collapse or expand the status item tree to allow more/less space fordetailed information on the right.

l The detailed information on the right is displayed in tables. You can change thecolumn 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).



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 caseof an error.

Information

General information about the host:

System Name, Model, UUID, Serial Number, Asset Tag, BIOS Version, CIM ProviderVersion, iRMC Firmware Version, Operating System Version, Image Profile, TotalMemory

Fans

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)

Information about the fans is not available if you have selected a blade. Forinformation about the fans of an MMB node, see "SV Plug-in information of anMMB node" on page 81.

Temperature

Detailed information about the temperature sensors installed on the system:

Status, Designation, Temperature, Warning Level, Critical Level, Fail Reaction, State

Power

Information about the power supplies installed in the system:

Status, Designation, State, Product Name (SVCIMp >=V6.31), CSS (SVCIMp >=V6.31)

Information about the power supplies is not available if you have selected ablade. For information about the power supplies of an MMB node, see "SV Plug-in information of an MMB node" on page 81.

Processors

Detailed information about the system processor configuration:

Status, Designation, Frequency (MHz), Manufacturer, Type, L1 Cache, L2 Cache, L3Cache, 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)



Storage

Overview of the RAID controllers found and details of their logical drives and physicaldisks (see "Storage view" on page 66).

Driver Monitor

Overview of the components of a host as well as of the associated events contained inthe 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

If a component is not accessible, there is no status information available for it.

Watchdogs

Information about the watchdogs configured on the system:

Type, Active, Action, Timeout

If a component is not accessible, there is no status information available for it.

System Event Log

A list of the entries found in the System Event Log together with cause/resolutioninformation.

The ServerView ESXi CIM Provider V6.31 or later supports the System Event Logview. The entries will be retrieved automatically via CIM.If the version of the ServerView ESXi CIM Provider is older than 6.31, you willneed to configure the IPMI credentials (see "IPMI configuration" on page 40) toretrieve the System Event Log entries from the host.

7.2.2 Agentless management via IPMI

It is also possible to monitor most of the storage values via IPMI, if the IPMI credentialsare 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.



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.

7.2.3 FUJITSU PRIMERGY Actions (iRMC-based operations)

The SV Plug-in offers some FUJITSU PRIMERGY Actions depending on the capabilities of theselected host.

The IPMI credentials (user name and password) must be configured to have accessto a number of iRMC based actions on an ESXi host:







These IPMI-based actions are always enabled in the context menu, even if thecredentials are not configured or the user does not have the privilege to perform theaction. 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 "IPMIconfiguration" on page 40.

7.2.3.1 Starting a FUJITSU PRIMERGY Action

There are two ways to start one of these FUJITSU PRIMERGY Actions:



l In the top left of the SV Plug-in interface in the main workspace, up to ten icons aredisplayed.

l 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 thetop left.

7.2.3.2 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 SVPlug-in - not of the vSphere Web Client.Consequently, this function is only available among the icons in thetop left of the SV Plug-in interface - not in the Actions menu.

Configure IPMI ...

1. Click this icon to start the IPMI configuration dialog (see "IPMIconfiguration" 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.


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.



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 viaiRMC (S4) directly for a host.

The ServerView eLCM Offline Update Workflow is part of the FUJITSUSoftware ServerView Plug-in for VMware vRealize Orchestrator eLCMOffline 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 SVvCenterService on/off (see "Integration in the event management of the vSphereWeb Client" on page 103).

This action is depicted in four ways, depending on the currentsubscription status:

The host is subscribed to the SVvCenter Service. Events will be monitored bythe SVvCenter Service and forwarded.

The host is not subscribed to the SVvCenter Service. No events will bemonitored by the SVvCenter Service or forwarded.

The subcription status of the host is unknown due to connection problemswith the SVvCenter Service. No action will be performed.

The host cannot be subscribed, because the vCenter is not connected to theSVvCenter Service. No action will be performed.

Invoke Test Event

1. Click this icon to request the host to send a test event (see "Integrationin the event management of the vSphere Web Client" on page 103).


7.3 Storage view

Export Data ...

1. Click this icon to open a frame where you can choose data to beexported (host information and System Event Log information).

If you choose all System Event Log entries, the retrieval of data willtake some time. There is a Cancel button to leave this frame withoutaction. As long as the export process is running, it cannot be stoppedand the buttons are locked.

When the requested data has been retrieved, a new window opens showingthe requested data - with the option to save it to a file.


7.3 Storage viewThe Storage view offers an overview of the RAID controllers found on the host and detailsof their logical drives and physical disks. In regular operation the SV Plug-in generallyshows the values of a host system provided by the ServerView ESXi CIM Provider. If a hosthas an older version of the ServerView ESXi CIM Provider, storage values are provided bythe LSI CIM provider (see "Prerequisites - information provider for the Storage view" onpage 66).

It is also possible to monitor most of the storage values via IPMI, if the IPMIcredentials are configured. You can toggle between CIM and IPMI communicationinterfaces. Via IPMI the Storage view offers a list of the physical disks and theirstatus. Via IPMI not all the values are available. See "Agentless management viaIPMI" on page 62.

7.3.1 Prerequisites - information provider for the Storage view

To ensure the optimum supply of RAID information it is recommended to install on thehost:

l ServerView ESXi CIM Provider V8.0 or higher

l ServerView RAID Core Provider

7.3.1.1 Information provider for the Storage view

The information shown in the Storage view is provided either from the ServerView ESXi CIMProvider or from the LSI CIM provider depending on the version of the ServerView ESXi CIMProvider.


7.3 Storage view

ServerView ESXi CIM Provider V8.0 or higher and the ServerView RAID Core Provider areinstalled:

The information comes from ServerView ESXi CIM Provider, and you will see an iconabove the Storage Details list on the right side.

1. Click the icon above the Storage Details list on the right side to gatherinformation 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.

7.3.2 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 whichthe 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 wellas 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 isopened:

Figure 26: Storage view of the SV Plug-in - expanded controller entry, Controller tab


7.4 Driver Monitor view

Storage Details - Controller tab

Information shown here includes:

Vendor, protocol, memory size, firmware package version, firmware version, BIOSversion, driver version, patrol read iterations, vendor/device ID, subvendor/device ID,PCI bus/device/function numbers, number and status of the logical drives (can beexpanded), 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 Detailsview).

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.


Stripe size in KB, read mode, write mode, disk cache mode, number and status of theconfigured physical disks (can be expanded).

Physical Disks - overview

1. Click the Physical Disks tab in an expanded controller entry view (Storage Detailsview).

An overview of the physical disks of the selected controller is displayed.


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 beexpanded if more than one logical drive uses this disk).

7.4 Driver Monitor viewThe Driver Monitor view isn’t available via IPMI.

Via the Driver Monitor view you can monitor and manage events relating to thecomponents of a monitored host, as listed in the OS event log on the monitored host.


7.4 Driver Monitor view

Figure 27: Driver Monitor view of the SV Plug-in

Requirements

l ServerView ESXi CIM Provider V7.31.06 or later must be installed on the ESXi-basedhost.

l 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 PCIinformation.

1. Click the arrow in front of a component entry to get more detailed information.

Show all

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 theserver side and set the status of this component to ok.

If a component has the status Warning or Error, the system status and errorlamp also indicates Warning or Error. If you click the button Acknowledge, thesystem 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.


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 beacknowledged.

1. Click the button Acknowledge on the right, in the line of the table headingComponents.

7.5 System Event Log viewIf the version of the ServerView ESXi CIM Provider is older than 6.31, it you will needto configure the IPMI credentials (see "IPMI configuration" on page 40) to retrievethe 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 latersupports 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 configurationare 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 onlythe Critical and Major entries showing.

1. If you wish to see entries of other severities, check/uncheck the boxes at the top of theSystem Event Log Details list:


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 theevent 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 seenabove the table.

1. Change these settings as required.

ErrorCode

Defines the type of the entry.

CSS 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 serversThe 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 theinventory tree item Hosts (see "Monitoring ESXi-based hosts" on page 58), but all FUJITSUPRIMERGY actions are available.



7.6.1 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 displayedif you click the title of an item box of a vCenter/cluster in the Summary tab on thehome 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 SVPlug-in.

The FUJITSU PRIMERGY second-level tab is only available if two conditions aremet:

l The vendor of the selected host is Fujitsu.

l 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 isavailable), SVvCenter Service monitoring status (subscribed/ not subscribed), networkaddress, model, operating system, serial number



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 thestatus item tree.

unknown

retrieving data

7.6.2 FUJITSU PRIMERGY Actions

Action icons

The SV Plug-in offers some FUJITSU PRIMERGY Actions, depending on the capabilities of theselected host.

In the main workspace of the SV Plug-in interface, you will see the action icons in the topleft.

Time of data acquisition: If the SV Plug-in is called, it will retrieve the data of theServerView 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


This Refresh function only refreshes the views/information of the SVPlug-in - not of the vSphere Web Client. Therefore, this function isonly available among the icons in the top left of the SV Plug-ininterface - not in the Actions menu.



SVvCenterService Connection

1. Click this icon to start a connection dialog similar to the dialog in theSVvCenter Service Configuration Overview (see "SVvCenter Serviceconfiguration" on page 33).

If the vCenter is already connected to a SVvCenter Service, you can updatethe connection or disconnect the vCenter from the SVvCenter Service.

If the vCenter is not connected to a SVvCenter Service, you can connect it toa 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 thecontext menu" on page 74).

Actions in the context menu

(For how to open this context menu see "Action icons " on page 73)

Configure IPMI ...

1. Click this icon to start the IPMI configuration dialog (see "IPMIconfiguration" on page 40).

Toggle Identify LED





Start iRMC

















1. Click this icon to turn the subscription of the host to the SVvCenterService on/off (see "Integration in the event management of the vSphereWeb Client" on page 103).






Invoke Test Event

1. Click this icon to request the host to send a test event (see "Integrationin the event management of the vSphere Web Client" on page 103).

Export Data ...

1. Click this icon to open a frame where you can choose data to beexported (host information and System Event Log information).

If you choose all System Event Log entries, the retrieval of data willtake some time. There is a Cancel button to leave this frame withoutaction. As long as the export process is running, it cannot be stoppedand the buttons are locked.

When the requested data has been retrieved, a new window opens showingthe requested data - with the option to save it to a file.




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-ininformation of the hosts of a vCenter/cluster" on page 72). The Single System View ofthe desired host is opened.


8.1 Monitoring CX hosts

8 Monitoring FUJITSU PRIMERGY specific nodes

8.1 Monitoring CX hostsInformation on the chassis itself is not available as there is no chassis managementcomponent in a CX chassis.

The following possiblities to monitor a CX host areoffered by the SV Plug-in:

l Related Hosts:

The number of adjacent hosts for the selected CXhost is shown as Related Hosts (with therecorresponding count) - see "Number of adjacenthosts for the selected CX host: Inventory Lists -Related Objects" on page 77.

l CX chassis support:

For a selected CX host the SV Plug-in shows a listof CX host powered on and running ESXi placedin the same chassis - see "Information onadjacent 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 InventoryLists.

1. In the object navigator of the vSphere Web Client select vCenter.

2. Under Inventory Lists select Hosts.

3. Select the desired host.

8.1.1 Number of adjacent hosts for the selected CX host: Inventory Lists -Related Objects

1. Select a CX host - see "Monitoring CX hosts" on page 77.

2. Click the > icon at the end of the selected host entry.



The list of Related Objects is displayed with there corresponding count in the objectnavigator.

The number of adjacent hosts for the selected CX host is shown as Related Hosts.

Figure 30: Related Objects of a CX host

8.1.2 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 ESXiplaced in the same chassis.

Information on the chassis itself is not available as there is no chassis managementcomponent in a CX chassis.

1. Select a CX host - see "Monitoring CX hosts" on page 77.

2. 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 theRelated Hosts sub-tab.

List of Related Hosts:

The list gives following information:

Name

Name of the host



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


8.2 Monitoring PRIMERGY blade servers

8.2 Monitoring PRIMERGY blade serversThe SV Plug-in adds the inventory list PRIMERGY Blade Server to the object navigator ofthe vSphere Web Client user interface (see "vSphere Web Client user interface" on page 32).

The following options are available for monitoring anMMB in the SV Plug-in:

l Information about the selected MMB

Status icons provide quick information anddetailed views provide more information - see"Monitor tab: Information on the selected MMB -Status items and views" on page 82 and "SVvCenterService for MMBs" on page 85.

l FUJITSU PRIMERGY actions

A number of action items support calling amonitoring tool or making settings on the MMB -see "FUJITSU PRIMERGY Actions" on page 84.

l Integration in event management of the vSphereWeb Client

The SV Plug-in includes the SVvCenter Service,which routes FUJITSU PRIMERGY-specific events tothe vCenter event management to be monitored inthe vSphere Web Client (see "Integration in theevent management of the vSphere Web Client" onpage 103).

8.2.1 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 anESXi-based host from the set of the assigned vCenter.

The SVvCenter Service (see "SVvCenter Service configuration" on page 33) performs aninitial search for all MMBs.

The SVvCenter Service repeats the search when specific events occur:



l Every time the SVvCenter Service starts

l If a new ESXi-based server is added to a vCenter

l If an ESXi-based server is removed from a vCenter

l Whenever the connection changes (i.e. startup, shutdown)

Procedure:

The SV Plug-in information about the hosts of a vCenter or a cluster is alsodisplayed if you click the title of an item box of a vCenter/cluster in the Summarytab on the home page of the SV Plug-in (see "Summary view" on page 53).


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 PRIMERGYActions" on page 84).

8.2.2 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 page80) or in the object navigator of the vSphere Web Client, select the desired MMB node.



The information for the selected MMB node opens in the main workspace, organized inthe 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, ConnectionBlade 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" onpage 82).

Related Objects

The Related Objects tab shows the ESXi hosts that are associated with the selectedMMB node.

In the Related Objects tab of a host node, there is a sub-tab showing the inverserelationship.

8.2.2.1 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 MMBevery 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.






ok

warning

critical

unknown

retrieving data



l FUJITSU PRIMERGY Actions:

Actions

This icon will be displayed if a host is selected in the Monitor tabview.

1. Click this icon to open the actions context menu (see "FUJITSUPRIMERGY Actions" on page 84).


Information

General information about the MMB node:

System Name, Model, Management Address, Serial Number, Firmware Version, AssetTag, Rack Name, Managed by VIOM, Status of the Identify LED

Fans

Information about the fans installed in the chassis:

Status, Designation, Current Speed, Maximum Speed, Nominal Speed, Fail Reaction,State

Temperature

Detailed information about the temperature sensors installed in the chassis:

Status, Destination, 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 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 theIdentify LED, Textual Status

If the MMB hosts an ESXi-based host, the Host Name is displayed as a hyperlink. Youcan 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, Statusof the Identify LED, Textual Status

8.2.2.2 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 remotemanagement page of the MMB.

Refresh


This Refresh function only refreshes the views/information of the SVPlug-in - not of the vSphere Web Client. Consequently, this function isonly available among the icons in the top left of the SV Plug-ininterface - not in the Actions menu.

Configure SNMP...

1. Click this icon to start the SNMP community configuration dialog, whereyou can set the community for the selected MMB (see "SVvCenter Servicefor MMBs" on page 85).

Start MMB GUI

1. Click this icon to launch the MMB GUI in a new window.



8.2.3 SVvCenter Service for MMBs

If a PRIMERGY CPU blade is found as a host on a connected vCenter, the SVvCenter Servicesearches for blade servers. The SVvCenter Service listens to SNMP traps sent by registeredMMBs.

8.2.3.1 Overview

The SVvCenter Service performs an initial search for MMBs. It repeats this search wheneverspecific events occur.

The SVvCenter Service performs the following steps for all hosts of its vCenter list:

l Checks if a host is a server blade

l Retrieves information about the associated hosts (i.e. IP address)

l Stores information about the relationship in an internal database

l 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.


l If a new ESXi-based host is added to a vCenter

l If an ESXi-based host is removed from a vCenter


8.2.3.2 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 theSVvCenter 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 usethis feature you need to make sure that the SVvCenter Service is configured as atrap destination.



8.2.3.3 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 withthe sending MMB. You will therefore find the SNMP trap in the event management andlogs of the vCenter that hosts the ESXi-based node. If an MMB has multiple hosts in thesame 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 remotemanagement page of an MMB.


8.3 Monitoring PRIMEQUEST systems

8.3 Monitoring PRIMEQUEST systemsThe SV Plug-in adds the inventory list PRIMEQUEST Server to the object navigator of thevSphere Web Client user interface (see "vSphere Web Client user interface" on page 32).

The following options are available formonitoring a PRIMEQUEST system in the SVPlug-in:

l Information about the selectedPRIMEQUEST system

Status icons provide quick informationand detailed views provide moreinformation - see "Monitor tab:Information on the selected PRIMEQUESTsystem - Status items and views" on page90 and "SVvCenter Service for PRIMEQUESTsystems" on page 92.

l FUJITSU PRIMERGY actions

A number of action items support calling amonitoring tool or making settings forPRIMEQUEST systems - see "FUJITSUPRIMERGY Actions" on page 92.

l Integration in event management of thevSphere Web Client

The SV Plug-in includes the SVvCenterService, which routes FUJITSU PRIMERGY-specific events to the vCenter eventmanagement to be monitored in thevSphere Web Client (see "Integration inthe event management of the vSphereWeb Client" on page 103).



8.3.1 Access to the SV Plug-in information of a PRIMEQUEST system

The object navigator of the vSphere Web Client shows all PRIMEQUEST systems, that arerelated to an ESXi-based host from the set of the assigned vCenter.

The SVvCenter Service (see "SVvCenter Service configuration" on page 33) performs aninitial search for all PRIMEQUEST systems.

The SVvCenter Service repeats the search when specific events occur:


l If a new ESXi-based server is added to a vCenter

l If an ESXi-based server is removed from a vCenter


Procedure:

The SV Plug-in information about the hosts of a vCenter or a cluster is alsodisplayed if you click the title of an item box of a vCenter/cluster in the Summarytab on the home page of the SV Plug-in (see "Summary view" on page 53).


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 PRIMERGYActions" on page 92).



8.3.2 SV Plug-in information of a PRIMEQUEST system

1. In the PRIMEQUEST Server list (see "Access to the SV Plug-in information of aPRIMEQUEST 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, ManagementBlade Count, Partition Count, System Board (SB) Count, IO Unit (IOU) Count, PowerSupply 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 andviews" on page 90).

Related Objects

The Related Objects tab shows the ESXi hosts that are associated with the selectedPRIMEQUEST node.

In the Related Objects tab of a host node, there is a sub-tab showing the inverserelationship.



8.3.2.1 Monitor tab: Information on the selected PRIMEQUEST system - Status itemsand views

Time of data acquisition: The data is retrieved from the SNMP agent of thePRIEMQUEST 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.




ok

warning

critical

unknown

retrieving data



l FUJITSU PRIMERGY Actions:

Actions

This icon will be displayed if a host is selected in the Monitor tabview.

1. Click this icon to open the actions context menu (see "FUJITSUPRIMERGY Actions" on page 92).


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



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:


DU Details

Detailed information about the installed disk units:


PciBoxes

Detailed information about the installed PRIMEQUEST PCI boxes:


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





In the top left of the SV Plug-in interface, up to three icons are displayed:

Refresh


This Refresh function only refreshes the views/information of the SV Plug-in - not of the vSphere Web Client. Therefore, this function is onlyavailable among the icons in the top left of the SV Plug-in interface - notin the Actions menu.

Configure SNMP ...

1. Click this icon to start the SNMP community configuration dialog, where youcan set the community for the selected MMB (see "SNMP settings" on page93).

Start MMB GUI

1. Click this icon to launch the PRIMEQUEST Management Board Web UI in anew window.

8.3.3 SVvCenter Service for PRIMEQUEST systems

The SVvCenter Service searches for PRIMEQUEST systems. The service checks for each ESXihost on the connected vCenters whether the host is a PRIMEQUEST partition. If so, theSVvCenter Service adds the associated PRIMEQUEST to the inventory list and listen to SNMPtraps sent from the discovered PRIMEQUEST systems.

8.3.3.1 Overview

The SVvCenter Service performs an initial search for PRIMEQUEST systems and repeats thissearch whenever specific events occur.

On startup, the SVvCenter Service performs the following steps for all hosts of its vCenterlist:

l Checks if a host is a partition or a PRIMEQUEST system

l Retrieves information about the associated PRIMEQUEST (i.e. IP address)

l Stores information about the relationship in an internal database

l 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:



ServerView ESXi CIM Provider must be installed on the ESXi-based host.


l If a new ESXi-based host is added to a vCenter

l If an ESXi-based host is removed from a vCenter


8.3.3.2 SNMP settings

To use the PRIMEQUEST system support of the SV Plug-in, the following requirements mustbe met:

In the SVvCenter Service Configuration Overview:

1. Specify the default SNMP communities to be used when a new PRIMEQUEST system isdetected by the SVvCenter Service, see "SVvCenter Service Configuration Overview" onpage 104.

In the PRIMEQUEST view:

1. Set the community for the selected PRIMEQUEST system, see "FUJITSU PRIMERGYActions" on page 92. For example, if the value has changed for the PRIMEQUESTsystem.

2. The community must be registered on the PRIMEQUEST Management Board Web UI forthe 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 PRIMEQUESTsystems. To use this feature you need to make sure that the SVvCenter Service isconfigured as a trap destination.

8.3.3.3 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 registeredPRIMEQUEST systems.

1. Configure SVvCenter Service as a trap destination on the registered PRIMEQUESTsystem.

You will find this setting on the PRIMEQUEST Management Board Web UI in the menu:

Network Configuration - SNMP Configuration - Trap


8.4 Discovering PRIMERGY Bmc Systems (for deploying)

Unlike CIM indications, an SNMP trap is processed for all ESXi-based hosts associated withthe sending PRIMEQUEST system. You will therefore find the SNMP trap in the eventmanagement and logs of the vCenter that hosts the ESXi-based node. If a PRIMEQUESTsystem 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 onthe 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-into deploy the ESXi operating system via ServerView profiles.

To do so you must


2. Store a customized ServerView profile under FUJITSU PRIMERGY Administration, see"ServerView Profile Management Service configuration" on page 35.

3. Deploy the ESXi operating system via the ServerView Deployment vRealize OrchestratorWorkflow, see "Deploying PRIMERGY Bmc Systems" on page 120.

8.4.1 PRIMERGY Bmc Systems view

The SV Plug-in adds the inventory list PRIMERGY Bmc Systems to the object navigator ofthe 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



8.4.2 Adding PRIMERGY Bmc Systems to the vCenter inventory

The connection with the PRIMERGY Bmc System runs via IPMI. Each PRIMERGY Bmc Systemtherefore is configured with a BMC IP address, user name and password.

Initially empty, the PRIMERGY Bmc Systems view (see "PRIMERGY Bmc Systems view" onpage 94) allows to add a PRIMERGY Bmc System manually (see "Adding a PRIMERGY BmcSystem manually" on page 95), to search for such systems (see "Searching for PRIMERGYBmc Systems" on page 95) or to add a PRIMERGY Bmc System from file (see "Adding aPRIMERGY Bmc System from file" on page 97).


8.4.2.1 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 (IPaddress 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 BmcSystems: Refresh the Summary view manually. See "SV Plug-in information of aPRIMERGY Bmc Systems" on page 100.

8.4.2.2 Searching for PRIMERGY Bmc Systems





The Discover BMC Systems dialog opens.

Figure 36: PRIMERGY Bmc System: Discover BMC Systems

In this dialog you must make the following settings:

l Select the credentials of at least one BMC of a targeted PRIMERGY Bmc System.

See "Selecting/ Configuring credentials" on page 96.

l 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.

l 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 username and password.

To add

In the Configure Credentials dialog click the icon.

The Add Login dialog opens. To define a combination of user name and passwordyou 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.

To edit

In the list of defined combinations select the desired combination.

In the Configure Credentials dialog click the icon

The Edit Login dialog opens

To add the combination to the list of defined combinations click the OK button



To delete

In the list of defined combinations select the desired combination.

In the Configure Credentials dialog click the icon.

The selected combination is deleted from the list.

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 tospecify 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 theDiscover 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 partof 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 PRIMERGYBmc Systems: Refresh the Summary view manually. See "SV Plug-in informationof a PRIMERGY Bmc Systems" on page 100.

8.4.2.3 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 ofPRIMERGY Bmc Systems. Via this list you can add these PRIMERGY Bmc Systems to thevCenter 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.



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 exportand import.

Proceeding


A dialog opens.

Figure 39: PRIMERGY Bmc System: Add BMC Systems from File



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 fileare displayed under the headings Name and Address.

If a value in the last column of the selected file doesn’t comply with the IPv4address format, an error message is displayed. After confirming the errormessage the message itself, just as the dialog Add Bmc Systems from File areclosed.

3. Specify Login and Password, which apply for all PRIMERGY Bmc Systems in the selectedlist.

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 areport window is displayed:

Figure 40: PRIMERGY Bmc System: Add Bmc Systems (results)

If a PRIMERGY Bmc System could not be added to the vCenter inventory, thereason is given in parentheses. The reason Operation timeout can have variouscauses: password is wrong, PRIMERGY Bmc System is not reachable, a specifiedsystem isn’t a PRIMERGY Bmc System.

5. Click OK.

To see the added PRIMERGY Bmc Systems in the Summary view for PRIMERGYBmc Systems: Refresh the Summary view manually. See "SV Plug-in informationof a PRIMERGY Bmc Systems" on page 100.



8.4.3 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 Systemwhich 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 BmcSystem.

If the BMC of a PRIMERGY Bmc System belongs to a host, updating ordeploying will not be possible. You will find information about this on thetab Summary in the field General Information.

Start Update

The eLCM Offline Update view is helpful when planning an update. It showsdetails of meeting requirements, progress information, details and parametersof the update workflow.

See "Offline update via eLCM" on page 112.



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 thePRIMERGY Bmc System. If an ESXi operating system is found, a third buttonAssign Host is displayed.

Clicking this button launches a window: Here you can select the desireddestination (data center or cluster), the PRIMERGY Bmc System should beadded to. To perform this task a VMware vRealize Orchestrator workflow willbe started.

Related Objects



In the top left of the SV Plug-in interface, up to seven icons are displayed:

Refresh


This Refresh function only refreshes the views/information of the SVPlug-in - not of the vSphere Web Client. Consequently, this function isonly available among the icons in the top left of the SV Plug-ininterface - not in the Actions menu.

Toggle Identify LED





Start iRMC
















Deploy

1. 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 SoftwareServerView Plug-in for VMware vRealize Orchestrator Deploymentpackage. See "Deploying PRIMERGY Bmc Systems" on page 120.


9 Integration in the event management of thevSphere Web ClientThe SV Plug-in includes a SVvCenter Service which routes FUJITSU PRIMERGY-specific eventsto 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 tosubscribed destinations. If the SVvCenter Service is subscribed to the host, it will receivethis CIM indication. It creates a corresponding vCenter event and forwards it to vCenterServer.

The SVvCenter Service also performs a search for blade servers or PRIMEQUEST systems if aPRIMERGY 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 trapssent by registered MMBs (see "SVvCenter Service for MMBs" on page 85) or registeredPRIMEQUEST systems (see "SVvCenter Service for PRIMEQUEST systems" on page 92).

In certain situations, some further settings can help you enhance the performance of theSVvCenter Service for events, MMBs and PRIMEQUEST systems (see "Further helpful serviceproperties for the SVvCenter Service for events, MMBs and PRIMEQUEST systems" on page106).

So the FUJITSU PRIMERGY-specific event is shown in the regular Monitor-Events sub-tab ofthe vSphere Web Client:

Figure 42: FUJITSU PRIMERGY-specific events in the Monitor-Events sub-tab of the vSphere Web Client


9.1 Requirements

9.1 Requirementsl CIM and SNMP

ESXi-based host

ServerView ESXi CIM Provider must be installed on the ESXi-based host whoseevents are to be displayed in the vSphere Web Client interface.

MMB

SVvCenter Service must be configured as a trap destination on the registeredMMBs.

PRIMEQUEST system

SVvCenter Service must be configured as a trap destination on the registeredPRIMEQUEST systems.

l SVvCenter Service must be connected to the vCenter to which the host is assigned to(see "SVvCenter Service configuration" on page 33).

l SVvCenter Service must be subscribed to this host (see "Monitoring vCenter or clusterhost servers" on page 71). You can find an overview of the hosts subcribed to aSVvCenter Service in the SVvCenter Configuration Overview (see "SVvCenter ServiceConfiguration Overview" on page 104).

9.2 SVvCenter Service Configuration OverviewYou can use this view to manage all the SVvCenter Services installed in your environment

9.2.1 Opening the SVvCenter Configuration Overview

At the bottom of the Getting Started tab on the home page of the SV Plug-in, youwill find the Manage the SVvCenter Services link.



3. Select the sub-item SVvCenter Service Configuration Overview.

In the main workspace of the vSphere Web Client, the SVvCenter Service ConfigurationOverview opens:


9.2 SVvCenter Service Configuration Overview

Figure 43: SVvCenter Service Configuration Overview

9.2.2 Properties of SVvCenter Services

The properties of a SVvCenter Service are also displayed if you click the title of anitem box of a SVvCenter Service in the Summary tab on the home page of the SVPlug-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:

ConnectionState

Current status and connection between the vSphere Web Client and theSVvCenter Service

Address Address used for the connection

Port Port used for the connection

Version Version of the SVvCenter Service

DefaultSnmpCommunities

For discovering blade servers (see "SVvCenter Service for MMBs" onpage 85) and PRIMEQUEST systems (see "SVvCenter Service forPRIMEQUEST systems" on page 92). You can edit this list (comma-separated) by clicking the pencil icon seen in this section.

vCenterName

vCenters connected to this SVvCenter Service. The icon in front of itshows the status between the SVvCenter Service and the vCenter. It alsoshows how many hosts are monitored (subscribed) and how many arenot.


9.2 SVvCenter Service Configuration Overview

9.2.3 Further helpful service properties for the SVvCenter Service forevents, MMBs and PRIMEQUEST systems

In certain situations, some further settings can help you enhance the performance of theSVvCenter Service for events, MMBs and PRIMEQUEST systems.

You can set these properties in the service.properties file of the service. The file is locatedon 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 issent repeatedly by the same host and generates a significant number of entries in theevent management of vSphere Web Client. The same event sent by the same hostduring 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 causeconnection timeouts. If you increase this value, there will be fewer connectiontimeouts 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 causeconnection timeouts. If you increase this value, there will be fewer connectiontimeouts but the processing will take longer!

9.2.4 Adding/removing a vCenter to/from the SVvCenter Service

For further information on the following procedures see: "SVvCenter Serviceconfiguration" on page 33.


9.3 FUJITSU PRIMERGY Predefined Alarm

9.3 FUJITSU PRIMERGY Predefined AlarmThe SV Plug-in offers a predefined alarm that will be triggered if a warning or error-levelevent is received by the vSphere Web Client event management. This alarm is enabled buthas no actions defined.

You can define a convenient action for this predefined alarm in the vSphere Web Client:

Requirements:

l 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 ServiceIn the vSphere Web Client views for ESXi-based hosts (see "SV Plug-in information of anESXi-based host" on page 59 and "FUJITSU PRIMERGY Actions (iRMC-based operations)" onpage 63, you will find the following actions relating to the SVvCenter Service:


1. Click this icon to turn the subscription of the host to the SVvCenterService on/off.





9.4 Actions relating to SVvCenter Service



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 itssubscribed nodes.

If the host is not subscribed to the SVvCenter Service (see "SVvCenterService configuration" on page 33), you will not see the event in thevCenter Event Manager (Monitor-Events sub-tab of the vSphere WebClient).


10.1 LED

10 Remote ManagementThe 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 andits iRMC.

To perform the iRMC-based operations (iRMC Web Interface together with singlesign-on (SSO), AVR, location button LED and, with ServerView ESXi CIM ProviderV6.31 and below, the System Event Log view), the user name and password for theIPMI credentials must be configured in the vCenter Server (see "IPMI configuration"on page 40).

Click the icon to start the IPMI configuration dialog (see "IPMI configuration"on page 40).

These IPMI-based actions are always enabled in the context menu, even if thecredentials are not configured or the user does not have the privilege to performthe 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 89.

10.1 LEDLED To facilitate identification of a system, for instance if it is installed in a fully populatedrack, you can activate the identification LED.


10.2 iRMC Web Interface

Toggle Identify LED





10.2 iRMC Web InterfaceiRMC S4 permits system control, diagnosis, configuration and server restarting by remoteaccess via the integrated web interface - even if the operating system or hardware fails.

The iRMC 4 supports Centralized Authentication Service (CAS) configuration, which allowsyou to configure the iRMC S4 web interface for CAS-based single sign-on (SSO)authentication.

Start iRMC




10.3 Remote console (AVR)Advanced Video Redirection (AVR) with iRMC S4 offers the following benefits:

l Operation via a standard web browser (as of FW version 8.05F you can select HTML5).

l System-independent graphical and text console redirection (including mouse andkeyboard).

l Remote access for boot monitoring, BIOS administration and control of the operatingsystem.

l Local monitor-off support.

l Low bandwidth support.






10.4 iRMC system report

10.4 iRMC system reportRequirements

l The iRMC must be version S4.

l The iRMC credentials must be configured as follows:

For further information see "FUJITSU PRIMERGY vCenter role definitions and iRMCsingle sign-on" on page 41.

o The iRMC credentials must be configured with an iRMC user account that has theAdministrator LAN channel privilege.

o The vCenter user must have the privileges defined in the FUJITSU PRIMERGY roleFUJITSU PRIMERGY Plug-in Administrator.




10.5 eLCM Offline UpdateThe SV Plug-in offers the option for starting an offline update via eLCM on a host or on aPRIMERGY Bmc System.

To perform the update, a new ServerView eLCM Offline Update Workflow has beendeveloped. It is part of the FUJITSU Software ServerView Plug-in for VMware vRealizeOrchestrator eLCM Offline Update package (for more information see the manual "FUJITSUSoftware ServerView Plug-in for VMware vRealize Orchestrator").


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 FUJITSUSoftware ServerView Plug-in for VMware vRealize Orchestrator eLCM OfflineUpdate package. See "Offline update via eLCM" on page 112.


11 Offline update via eLCMeLCM - embedded LifeCycle Management

As well as making it possible to manage a PRIMERGY server out-of-band, the enhancedfunctionality of the newest version of the iRMC S4, which comes with an integrated SDcard, allows for comprehensive lifecycle management of a PRIMERGY server. As lifecyclemanagement 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 toautomatically download files from a repository server via the dedicated iRMC S4management LAN port and to store them on the iRMC S4 SD card. The repository servercan be the FTS Support Server or a separate server running the ServerView RepositoryServer (see the manual "ServerView Update Repository" for details).

Some server components can only be updated by the server operating system. To make thecorresponding update packages available to the server operating system, the iRMC S4downloads these packages, makes an ISO image from them, and mounts the ISO image asa virtual CD-ROM device.

Offline update mode of the iRMC

An offline update extends the autonomous update capabilities of the iRMC S4. Systemcomponents like network or storage controller firmware can be updated using the offlineupdate mode.

In this case, a bootable update image that was previously downloaded from therepository server onto the iRMC S4 SD card is mounted by the iRMC S4 via remote imagemount as a system USB CD/DVD-ROM device. Like the common Update DVD, the bootableupdate image consists of two main parts: a boot loader for booting CentOS and the eLCMoffline update manager itself, which is a slim version of the ServerView Update ManagerExpress. Once the USB CD/DVD-ROM is mounted, the iRMC S4 automatically shuts down theserver 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 aPRIMERGY Bmc System.

To perform the update, a new ServerView eLCM Offline Update Workflow has beendeveloped. It is part of the FUJITSU Software ServerView Plug-in for VMware vRealizeOrchestrator eLCM Offline Update package. Workflows combine actions, decisions andresults that, when performed in a particular order, complete a specific task or process in a


11.1 Requirements and compatibility warning

virtual environment (for more information see the manual "FUJITSU Software ServerViewPlug-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 shutdown. Once started, the workflow will connect to the eLCM and start the update.

11.1 Requirements and compatibility warningCompatibility warning!

This action will update the system’s BIOS and firmware components, depending onthe contents of the FUJITSU Update Repository. Updating could cause a violation ofthe VMware hardware compatibility list requirements. Please consider this whenusing 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 putthe host into maintenance mode and shut it down. Once started, the workflow willconnect to the eLCM and start the update.

The following requirements must be met in order to start the update.

l iRMCo iRMC must have an S4 and a minimum version 8.03Fo iRMC credentials must be configured for the BMCo The iRMC must be licensed to perform eLCMo The user must have Administrator privileges for the host/ the PRIMERGY Bmc

System

l 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 notable to check the presence and validity of this configuration.

l VMware vRealize Orchestrator must be installed (minimum version 6.0) and must beconnected to the vCenter.

o The FUJITSU Software ServerView Plug-in for VMware vRealize Orchestrator eLCMOffline Update (minimum version 1.2.5) must be installed in VMware vRealizeOrchestrator


11.2 Starting points

VMware vRealize Orchestrator V7.0:

VMware vRealize Orchestrator V7.0 has TSLv1 protocol disabled by default. ThevSphere WebClient V6.0 as well as the SV Plug-in perform the connectionsusing this version, Therefore it will not be able to connect to the VMwarevRealize Orchestrator and manage the update and deploy workflows.

For this reason, it is necessary to configure the VMware vRealize Orchestratorto 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" withsslEnabledProtocols="TLSv1, TLSv1.1, TLSv1.2".

4. Save the file /etc/vco/app-server/server.xml.

5. Restart the VMware vRealize Orchestrator service using the commandservice vco-server restart.

11.2 Starting pointsYou have two options for starting an offline update via eLCM:

l 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 showsinformation on meeting requirements, progress information, and details andparameters of the update workflow.

See "Offline update via eLCM started from SV Plug-in view" on page 114.

l 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, ifso, 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 119.

11.3 Offline update via eLCM started from SV Plug-in viewThe eLCM Offline Update view is helpful when planning an update. It shows details ofmeeting requirements, progress information, details and parameters of the updateworkflow.


11.3 Offline update via eLCM started from SV Plug-in view

11.3.1 Opening the eLCM Offline Update view

11.3.1.1 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.

11.3.1.2 Opening the view of a PRIMERGY Bmc System



The PRIMERGY Bmc Systems view is displayed. Here you find a list of the knownPRIMERGY Bmc Systems.

3. In PRIMERGY Bmc Systems list select the desired PRIMERGY Bmc System.


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.

11.3.2 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.



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:



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 sayingwhether or not it was started successfully.

11.3.3 eLCM Offline Update in progress

Figure 47: eLCM Offline Update view - In progress



The eLCM Offline Update itself will take some time, so the view will be refreshed onceto see the progress of the workflow. You must then refresh the view manually if you

want to keep monitoring the progress: Click the icon to refresh the currentview of the SV Plug-in.

It is now no longer possible to restart the update.

11.3.4 eLCM Update Workflow details

The SV Plug-in provides information about the progress of a workflow.You can select eithera workflow that is currently running or one which is complete.

If no logs are present, they might have been deleted by VMware vRealizeOrchestrator.

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 youunderstand why it failed.

Figure 48: eLCM Offline Update view - Workflow logs

Deleting update history items

You can delete some of the update history items.


11.4 Offline update via eLCM started from SV Plug-in FUJITSU PRIMERGY Actions menu

1. Select an item in the list of update runs.

2. Press the [DEL].

or

1. Click the icon in the Update History title bar.

11.4 Offline update via eLCM started from SV Plug-in FUJITSUPRIMERGY Actions menuIf 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.

11.4.1 Starting

There are two ways to start one of these FUJITSU PRIMERGY Actions:

l In the main workspace of the SV Plug-in interface, you will see some icons in the topleft.

1. Select the icon .

l The FUJITSU PRIMERGY Actions can be started independently of the SV Plug-in interface(not valid for PRIMERGY Bmc Systems):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 All FUJITSU PRIMERGY Actions.

3. Select the entry Start an eLCM Offline Update Workflow.


12 Deploying PRIMERGY Bmc SystemsFUJITSU Software ServerView Plug-in for VMware vRealize Orchestrator Deployment

PRIMERGY Bmc systems without an operating system can be added to the SV Plug-in todeploy the ESXi operating system via ServerView profiles. For doing so the followingcomponents come into play:

l FUJITSU Software ServerView Plug-in for VMware vRealize Orchestrator Deployment.

l The vCenter inventory must know the PRIMERGY Bmc System and its basic data.

l A ServerView profile, which defines the deploying parameters.

The FUJITSU Software ServerView Plug-in for VMware vRealize Orchestrator Deploymentprovides the deployment workflow. The deployment workflow bundles the basic data ofthe PRIMERGY Bmc System and the ServerView profile definitions and delivers them to theServerView SysRollout Service, which performs deployment process. Once the deploymentprocess is completed and the new ESXi-based host is reachable, the new ESXi-based hostwill be added a data center or a cluster destination.

eLCM - embedded LifeCycle Management

As well as making it possible to manage a PRIMERGY server out-of-band, the enhancedfunctionality of the newest version of the iRMC S4, which comes with an integrated SDcard, allows for comprehensive lifecycle management of a PRIMERGY server. As lifecyclemanagement is largely integrated ("embedded") in and entirely controlled by the iRMC S4,it is called "embedded LifeCycle Management" (eLCM).

One of the eLCM functions (as of eLCM version 1.2):

eIM - embedded Installation Management

embedded Installation Management (eIM) is the eLCM equivalent to the well-provenServerView Installation Manager. Stored on the iRMC S4 SD card for immediate use, noexternal ServerView media needed to set up and install FUJITSU PRIMERGY systems.

eIM provides a fast and secure server configuration and installation. The server is deployedeither unattended or menu-driven, locally or remotely. In preparation for the requiredoperating system all configurable system components are identified and the necessarydrivers are provided automatically.

Processing

PRIMERGY Bmc systems without an operating system can be added to the SV Plug-in todeploy the ESXi operating system via ServerView profiles.


12.1 Requirements

To do so you must


2. Store a customized ServerView profile under FUJITSU PRIMERGY Administration, see"ServerView Profile Management Service configuration" on page 35.

3. Deploy the ESXi operating system via the ServerView Deployment vRealizeOrchestrator Workflow, see "Deploying PRIMERGY Bmc Systems" on page 120.

Working connections are prerequisite for handling profiles. Therefore theseconnections are regularly checked. If the Profile Management Service can not beconnected, you can not configure profiles. If VMware vRealize Orchestrator is notconnected to the vCenter or the FUJITSU Software ServerView Plug-in for VMwarevRealize Orchestrator ’Deployment’ is not installed, you can not start deploymentprocesses. Related error messages are displayed in the ServerView ProfileManagement overview under Issues.

12.1 RequirementsThe following requirements must be met in order to start the deployment process.

l IRMCo iRMC must have an S4 and a minimum version 8.24F

o iRMC credentials must be configured for the BMC

o The iRMC must be licensed to perform eLCM

o The user must have Administrator privileges for the host/ the PRIMERGY BmcSystem

l eIM (embedded Installation Management - see "Deploying PRIMERGY Bmc Systems" onpage 120) must be installed on the integrated SD card.

eIM is part of eLCM as of eLCM version 1.2. eIM must have a minimum version11.16.06.

l VMware vRealize Orchestrator must be installed (minimum version 6.0) and must beconnected to the vCenter.

o The FUJITSU Software ServerView Plug-in for VMware vRealize OrchestratorDeployment (minimum version 1.3.4) must be installed in VMware vRealizeOrchestrator

VMware vRealize Orchestrator V7.0:

VMware vRealize Orchestrator V7.0 has TSLv1 protocol disabled by default. ThevSphere WebClient V6.0 as well as the SV Plug-in perform the connectionsusing this version, Therefore it will not be able to connect to the VMware


12.2 Starting points

vRealize Orchestrator and manage the update and deploy workflows.

For this reason, it is necessary to configure the VMware vRealize Orchestratorto accept TSLv1 requests:





5. Restart the VMware vRealize Orchestrator service using the commandservice vco-server restart.

12.2 Starting pointsYou have two options for starting a deployment via eIM:

l From the PRIMERGY Bmc Systems view of the SV Plug-in user interface.

See "Opening the view of a PRIMERGY Bmc System" on page 122.

l From the view of Clusters or vCenter Servers via an item on the SV Plug-in FUJITSUPRIMERGY Actions menu.

If you start the deployment wizard here, it will check all known PRIMERGY Bmc Systemsfor requirements. The wizard allows you to select available systems. Successfullydeployed hosts will be added to the vCenter or cluster destination.

See "Opening the view of Clusters or vCenter Servers" on page 124.

12.3 Deployment via eIM

12.3.1 Opening the deployment wizard

12.3.1.1 Opening the view of a PRIMERGY Bmc System



The PRIMERGY Bmc Systems view is displayed. Here you find a list of the knownPRIMERGY Bmc Systems.

3. In PRIMERGY Bmc Systems list select the desired PRIMERGY Bmc System.




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.

First the Deployment functionality checks its requirements.

Requirements failed

If one or more requirements are not met, the following information is displayed:

Figure 49: PRIMERGY Bmc Systems view - Requirements failed

The Deployment process 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 Deployment button is displayed:

Figure 50: PRIMERGY Bmc Systems view - Requirements met

1. Click the Start Deployment button to start the deployment wizard.



12.3.1.2 Opening the view of Clusters or vCenter Servers


2. Under Inventory Lists select vCenter Servers or Clusters.

3. In the center pane of the vSphere Web Client, select the desired host in the inventorytree.

4. In the Actions menu you will find the submenu FUJITSU PRIMERGY.

This submenu offers the Start a Deployment Workflow item.

5. Click the Start a Deployment Workflow item to start the deployment wizard.

If you start the deployment wizard here, a additional step Choose Bmc Systems isadded at the beginning of the deployment wizard.

All known PRIMERGY Bmc Systems are checked for requirements and the result of thischeck is displayed in a list under Choose Bmc Systems.

Each item of this list is preceded by a status icon (see "Information on the selectedhost - Status items and views" on page 60).

ok

You can choose this system for deployment.

warning

An operating system is found on this system. You can choose this system fordeployment.

error

You can not choose this system for deployment.

6. Select the desired PRIMERGY Bmc Systems.

7. Click the Next button.

The deployment wizard continues as described in "Deployment wizard" on page 124.

Successfully deployed hosts will be added to the vCenter or cluster destination.

12.3.2 Deployment wizard

The first steps of this wizard are equivalent to the configuration wizard of theServerView Profile Management Service.

1. Complete the configuration steps for the ServerView Profile Management Service - see"Configuration wizard" on page 38:

l Choose Profile

l Image Repository Information



l User Data Information

l Common Network Information

In the deployment wizard all settings for the ServerView Profile ManagementService are mandatory

2. Host Network

If DHCP is enabled, no input is needed.

If you are using manual network settings, these input files define the name of the newhost and its IP address.

The predefined network interface identifier is vmnic0. You can change it as needed.

3. Host Destination (only if the wizard is started from the view of a PRIMERGY BmcSystem)

You can add the new host to an existing data center or cluster:

Check the box Add Host To Destination an select the desired destination.

4. Start Deployment Workflow

Summarizes the configuration.

Click the Finish button to start the Deployment workflow.

Once the vCenter inventory knows a former PRIMERGY Bmc System as (deployed)ESXi-based host, you can not start another deployment action. To do so, removethe ESXi-based host from the vCenter inventory.

If the wizard is started from the view of Clusters or vCenter Servers (see"Deployment via eIM" on page 122), successfully deployed hosts will be addedto the vCenter or cluster destination. If adding a PRIMERGY Bmc System (withESXi) fails, a button Assign Host will be displayed. See "SV Plug-in informationof a PRIMERGY Bmc Systems" on page 100.


13.1 Time of data acquisition

13 Error handling

13.1 Time of data acquisitionIf the SV Plug-in is called, it will retrieve the data of the ServerView ESXi CIM Provider orthe LSI CIM provider (Storage view) on the host. Whenever you click the status item tree(see "Information on the selected host - Status items and views" on page 60), 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.

13.2 All expanded items are closedOnce a view with expanded items is refreshed, all expanded items are closed.

You will therefore have to expand the desired items again to see the specific data again.

13.3 Retrieving data failedIf retrieving data fails, an error icon will be displayed in the bottom right of the SV Plug-ininterface.

If loading a content view fails, a message box will open showing the possible cause andthe original error text.

13.4 An action in the top left of the SV Plug-in interface isdisabledAn action in the top left of the SV Plug-in interface will be disabled if the user does nothave the required privilege. There will be a tooltip saying not privileged to start... .



13.5 An action in the context menu results in an error message

13.5 An action in the context menu results in an errormessageRequesting an action in the context menu will result an error message if the user does nothave the required privilege.


13.6 Remote console (AVR) or iRMC Web Client do not work asexpectedIf the remote console (AVR) or the iRMC Web Client are started from vSphere Web Client,they will be started in the role that matches the current user privileges as previouslydefined.

If these privilege definitions are not enough to enable the desired functions, AVR and iRMCWeb Client will show unexpected behavior.


13.7 The same event generates a significant number ofentries in the event managementSometimes events are sent with high frequency. In this case the same event is sentrepeatedly by the same host and generates a significant number of entries in the eventmanagement of vSphere Web Client.

The SV Plug-in includes a SVvCenter Service which routes FUJITSU PRIMERGY-specific eventsto the vCenter event management to be monitored in the vSphere Web Client.

You can set the trap.forward.limit property of this service to enhance itsperformance.

See "Further helpful service properties for the SVvCenter Service for events, MMBs andPRIMEQUEST systems" on page 106.

13.8 Repeated connection timeoutsLow connectivity in the network or older versions of ServerView ESXi CIM Provider or SNMPagents causes connection timeouts.

The SV Plug-in includes a SVvCenter Service which routes FUJITSU PRIMERGY-specific eventsto the vCenter event management to be monitored in the vSphere Web Client.


13.9 Editing a profile failed (using IE 11)

You can set the <cim/snmp>.client.timeout property of this service to enhance itsperformance during connection timeouts.

If you increase this value, there will be fewer connection timeouts but the processing willtake longer!

See "Further helpful service properties for the SVvCenter Service for events, MMBs andPRIMEQUEST systems" on page 106

13.9 Editing a profile failed (using IE 11)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.

13.10 Browsing for PRIMERGY bare metals systems failed(using IE 11)


13.11 SV Plug-in cannot connect to the VMware vRealizeOrchestrator (using Orchestrator V7.0)VMware vRealize Orchestrator V7.0 has TSLv1 protocol disabled by default. The vSphereWebClient 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 managethe update and deploy workflows.

For this reason, it is necessary to configure the VMware vRealize Orchestrator to acceptTSLv1 requests:





5. Restart the VMware vRealize Orchestrator service using the command servicevco-server restart.


13.12 Executing SVSInstallerGUI.sh results in warnings (remote X Server, e.g. MobaXTerm)

13.12 Executing SVSInstallerGUI.sh results in warnings (remoteX Server, e.g. MobaXTerm)If SVSInstallerGUI.sh is executed with a remote X Server (e.g. MobaXTerm), some warningswill be displayed.

Example:

QXcbConnection: XCB error: 147 (Unknown), sequence: 161,resource id: 0, major code: 140 (Unknown), minor code: 20

This a is a known problem of the Qt libraries which will be solved in future versions of Qt.

You can ignore these warnings, and the installer will nevertheless work correctly.

Additionally SVSInstaller can be executed without GUI. Then no warnings will be displayed.

13.13 vCenter Server Appliance: Executing SVSInstallerGui.shfailedSVSInstallerGui.sh can not be executed on the vCenter Server Appliance (based on SLES11), because prerequisites are missing.

You must use SVSInstaller.sh here.

For further information see "Installing on Linux" on page 25.
