Fujitsu V6.10 User guide

Add to my manuals
282 Pages

advertisement

Fujitsu V6.10 User guide | Manualzz

User Guide - English

ServerView Suite

ServerView Update Management

ServerView Operations Manager V6.10

Edition October 2012

Comments… Suggestions… Corrections…

The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs.

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

.

Certified documentation according to DIN EN

ISO 9001:2008

To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard

DIN EN ISO 9001:2008.

cognitas. Gesellschaft für Technik-Dokumentation mbH www.cognitas.de

Copyright and trademarks

Copyright © 1998 - 2012Fujitsu Technology Solutions.

All rights reserved.

Delivery subject to availability; right of technical modifications reserved.

All hardware and software names used are trademarks of their respective manufacturers.

Contents

Contents 3

1 Introduction 9

1.1 Concepts

1.2 Prerequisites

1.2.1 Prerequisites on managed servers

1.2.2 Prerequisites on connection blades

1.2.3 Prerequisites on TFTP server 15

1.2.4 Prerequisites on the Central Management Station (CMS) 16

1.2.4.1 Update Management Logon (OS=Windows)

1.2.4.2 Configuration of Update Management (Repository, …)

16

10

12

12

14

1.2.4.3 Update Data

1.3 Notes on management stations

1.3.1 Shutdown and restart

1.3.1.1 Status after unplanned restart

1.3.1.2 Procedure for resolving the errors

1.3.2 Updating the management station with components which needs a reboot

1.3.3 Multiple management stations

1.4 Autonomous Support Packages (ASP)

1.5 PRIMERGY Support Packages (PSP)

1.5.1 Current PSP versions

1.5.2 Components of a PSP

1.5.3 Product Detection of Primergy Support Packages

1.5.4 Initial Installation of Primergy Support Packages

1.6 Notes on deleting servers from the ServerList

1.7 Typographic conventions

1.8 ServerView Suite link collection

1.9 Documentation for the ServerView Suite

18

18

20

20

20

20

21

22

23

25

20

21

21

21

26

27

28

30

2 Overview

3 Update Procedures

3.1 Online update

3.2 Update via TFTP server

3.2.1 Updating a hardware system

3.3 Access to update data

31

35

36

38

39

41

ServerView Update Management 3

Contents

4

4 Installing ServerView Update Agents

4.1 Installation on the managed server

4.1.1 Requirements for installation

4.1.2 Requirements for uninstallation

4.1.3 Installing Update Agent V6.0 (or later)

4.1.3.1 Installation under Windows

4.1.3.2 Installation under Linux or VMWare (ESX)

4.2 Installation on the TFTP server

4.2.1 Installation under Windows

4.2.2 Installation under Linux

5 User Interface 53

5.1 Update Manager Main Window

5.1.1 The tree structure

5.1.2 Server Details tab

5.1.3 Update Details tab

5.1.4 Job Details tab

5.1.5 Dialog boxes and wizards

5.1.5.1 LogOn dialog box

5.1.5.2 Cleanup Wizard

5.1.5.3 Server Details dialog box

5.1.5.4 Create Job Wizard

5.1.5.5 Update Details dialog box

5.1.5.6 PSP Details dialog box

5.1.5.7 Copy Job Wizard

5.1.5.8 Job Details dialog box

5.1.5.9 Edit Job dialog box

5.1.5.10 Change TFTP Address dialog box

5.1.5.11 Change Flash Address dialog box

5.2 Repository Manager Main Window

5.2.1 The tree structure

5.2.2 Updates tab

5.2.3 Collections tab

5.2.4 Dialog boxes

5.2.4.1 Edit Update's Properties dialog box

5.2.4.2 Import Repository Components dialog box

5.2.4.3 Import Repository Components - Results dialog box 142

5.2.4.4 Export Repository Components dialog box 144

5.2.4.5 Export Repository Components - Results dialog box 146

124

125

126

128

132

135

135

139

84

90

100

104

106

117

120

123

71

75

76

79

53

56

61

67

43

45

48

51

51

52

43

43

44

45

ServerView Update Management

Contents

5.2.4.6 Delete Repository Components dialog box 148

5.2.4.7 Delete Repository Components - Results dialog box 150

5.2.4.8 PSP Details dialog box

5.2.4.9 Create Collection dialog box

152

154

5.2.4.10 Edit Collection dialog box

5.3 Download Manager Main Window

5.3.1 The tree structure

5.3.2 Task Management Tab

156

158

159

160

5.3.3 Scheduled Tasks Tab

5.3.4 Log Files Tab

5.3.5 Dialog boxes

5.3.5.1 Add Download Server Tasks dialog box

5.3.5.2 Edit Download Server Tasks dialog box

5.3.5.3 Activate Download Server Tasks dialog box

5.4 Configuration Main Window

5.4.1 General Settings Tab

163

165

168

168

171

173

175

176

5.4.2 Mail Settings Tab

5.4.3 Download Settings Tab

5.4.4 Configuration Wizard

5.4.4.1 Start step (Configuration Wizard)

5.4.4.2 Repository step (Configuration Wizard)

5.4.4.3 Miscellaneous step (Configuration Wizard)

5.4.4.4 Download Settings step (Configuration Wizard)

5.4.4.5 Mail Settings step (Configuration Wizard)

5.4.4.6 Activate step (Configuration Wizard)

5.5 Filter dialog box

5.5.1 Standard (Filter dialog box)

5.5.2 Character strings (Filter dialog box)

5.5.3 Integer values (Filter dialog box)

178

180

182

183

184

189

190

192

194

196

196

197

198

6 Managing Updates

6.1 Update Manager

6.1.1 Opening Update Manager

6.1.2 Closing Update Manager

6.1.3 Logging on to the Server

6.1.4 Resetting the update agent of a server

6.1.5 Displaying the update log for a server

6.1.6 Displaying detailed information about an update

6.1.7 Managing jobs

199

199

199

200

200

201

203

203

203

ServerView Update Management 5

Contents

6

6.1.7.1 Creating a job

6.1.7.2 Copying a job

6.1.7.3 Releasing a job

6.1.7.4 Deleting a job

6.1.7.5 Displaying detailed information about a job

6.2 Repository Manager

6.2.1 Opening Repository Manager

6.2.2 Closing Repository Manager

6.2.3 Editing updates

6.2.4 Releasing updates

6.2.5 Managing user-defined groups (Collections)

6.2.5.1 Creating a user-defined group

6.2.5.2 Editing a user-defined group

6.2.5.3 Releasing updates in a user-defined group

6.2.5.4 Deleting a user-defined group

6.2.6 Re-Initializing the Repository

6.3 Download Manager

6.3.1 Adjusting the Download Service

6.3.2 General Information on Download Manager

6.3.3 Opening Download Manager

6.3.4 Closing Download Manager

6.3.5 Creating a new download task

6.3.6 Assigning servers to a download task

6.3.7 Editing a download task

6.3.8 Deleting a download task

6.3.9 Monitoring download tasks

6.3.10 Managing log files

6.4 Configuration

6.4.1 Opening the configuration

6.4.2 Closing the configuration

6.4.3 Setting Global Parameters

6.5 Filtering a table

7 Command-Line Interface

7.1 GFCLI (Command-Line Interface)

7.1.1 Call Parameters

7.1.2 StartFlash (Command)

7.1.3 WaitForDone (Command)

7.1.4 Reboot (Command)

ServerView Update Management

225

225

226

229

231

233

218

218

219

219

219

220

220

224

214

214

215

216

216

216

217

217

209

209

210

210

210

211

211

212

203

206

207

207

207

208

208

208

Contents

7.1.5 Cleanup (Command)

7.1.6 Cancel (Command)

7.1.7 Result Files

7.1.7.1 StartFlash (Event)

7.1.7.2 Ready (Event)

7.1.7.3 Cancel (Event)

7.1.7.4 SequenceError (Event)

7.1.7.5 ParamError (Event)

7.1.7.6 LogonError (Event)

7.1.7.7 MemoryError (Event)

7.1.8 Batch Files (Examples)

7.1.9 CLI Standalone

7.2 citfs.bat (batch job)

8 Troubleshooting

8.1 Error messages in the Update Manager

8.2 Error messages in the Download Manager

8.3 Error messages in the Configuration Wizard

8.4 Error messages in the Repository Manager

8.5 Problems with Single Sign-On

8.6 Problems with entries in the tree structure

8.7 Problems with components

8.8 Event ID 2370 on managed node

8.9 Installation/Uninstallation of updateable components without using Update Manager

Index

277

279

261

261

266

270

273

273

274

275

275

235

236

238

239

242

243

243

244

244

244

245

258

258

ServerView Update Management 7

8 ServerView Update Management

1 Introduction

ServerView Update Management allows you to manage updates for the firmware and software components of PRIMERGY servers. Update Management comprises the following applications: l

Update Manager provides a mechanism for managing updates and installing them on the monitored managed nodes.

l

Repository Manager provides a mechanism for managing the repository: o view a list of updates contained in the repository o change properties of contents o update your local repository on the management station o create collections l

Download Manager provides a mechanism for checking for available updates and downloading new ones for the monitored managed nodes from the Fujitsu Technology Solutions web server to the local repository on the management station.

l

Configuration provides a mechanism for defining the configuration settings for the o Update Manager o Repository Manager o Download Manager

ServerView Update Management 9

1 Introduction

1.1

Concepts

Update Management is based on a database concept where the GUIs and services communicate exclusively via the database:

1. The GUIs are used to define jobs for the services and write these jobs to the database.

2. The services retrieve their jobs from the database, process these in the background and write the results to the database.

3. The GUIs then display the results from the database.

The tasks performed by the various services are described below:

The Inventory Service reads the inventories of the PRIMERGY servers and writes the results to the database. (The inventory contains the entire hardware and software configuration data of a PRIMERGY server.)

The Download Service downloads updates from the download server into the repository.

In addition to the download via the Download Service, you can also import updates from the ServerView Suite DVD 1 min. 7.812 (Windows) / 10.09.09 (Linux), max. 10.12.04 or the ServerView-Update

DVD to the repository using the Repository Manager.

For the initial update (Update Manager Express) of your PRIMERGY server, load the updates from the ServerView Suite DVD 1 min. 7.812

(Windows) / 10.09.09 (Linux), max. 10.12.04 or the ServerView-Update

DVD first because otherwise this process may take a very long time to complete due to the large volume of data. Since the DVD, which is published almost monthly, may not contain the latest updates, you should then download the latest updates using the Download Service.

10 ServerView Update Management

1.1 Concepts

The Update Service performs the following tasks:

1. It detects which updates are available for the individual PRIMERGY servers based on the inventories and repositories, and returns the result to the database so that this can be displayed in the GUI.

2. It uses the jobs you define in the GUI to transfer the updates from the repository to the PRIMERGY servers.

These interrelationships are illustrated in the following graphic.

Figure 1: Interaction between the various services for Update Management

ServerView Update Management 11

1 Introduction

1.2

Prerequisites

You can get the applications ServerView Agents, ServerView Update Agent,

ServerView Operations Manager from the: l

ServerView Suite DVD 1 (bundled with PRIMERGY server) l

ServerView Suite - Update DVD ftp://ftp.ts.fujitsu.com/images/serverview /UPDATE_DVD_

<vers>.<iso> l

Download section of the Fujitsu Technology Solutions Web server: http://support.ts.fujitsu.com

1.2.1

Prerequisites on managed servers

Online server allows components to be installed only while the operating system is running.

l

ServerView Agents for Windows or Linux must be installed.

l

ServerView Update Agent (Windows >=V5.10.02, Linux >=V5.10-01) must be installed l

In a firewall configuration on the managed nodes, the following ports must be enabled: o 161 (snmp) o 3171 (ServerView Update Agent) o 3172 (SCS)

12 ServerView Update Management

1.2 Prerequisites

Security

If you need security (configuration with AccountCheck) before performing an update on the managed server, you can either use Single Sign-On or you must specify a user group.

l

Single Sign-On

Requirements: o ServerView agents as of V 5.0

o ServerView update agent as of V 5.0

o The certificate from the Central Management Station (CMS) must be copied to the managed nodes.

l

Specify a user group

Windows: during ServerView Update Agent installation

Linux: during ServerView Update Agent installation default settings are configured

Default user group: GFUSER

Default user: globalflash with password globalflash

You can change the default settings by editing the file LinuxF-

wuAgent.cfg.

Inventory

Requirements of ServerView Agents for serving firmware of l

Broadcom LAN controller

Windows: PSP Broadcom_LAN_BACS/_E / …

Linux: SV Update Agent l

RAID controller

Linux: ServerView RAID

ServerView Update Management 13

1 Introduction

1.2.2

Prerequisites on connection blades

To prepare a connection blade for update via Update Manager, configure it as follows:

1. Open the graphical user interface of the connection blade, e.g. via a browser: http://<ipadr connection blade>

2. Security > Secure Shell:

Set the following values:

Admin Mode: Enable

SSH Version 1: Disable

SSH Version 2: Enable

14 ServerView Update Management

1.2 Prerequisites

1.2.3

Prerequisites on TFTP server

A TFTP server is necessary for updating connection blades / management blades.

l

ServerView Agents for Windows or Linux >= V5.10 must be installed.

l

ServerView Update Agent (Windows >=V5.10.02, Linux >=V5.30-00) must be installed

TFTP server Windows l

Fujitsu Technology Solutions PXE server (<=1.13.0000, >=1.15.0000) must be installed.

Only the TFTP service has to be active!

For installation of TFTP Server Windows see

"Installation under Windows" on page 51

.

TFTP server Linux l

The software package for tftp service (firewall configuration must allow tftp) must be installed

For installation of TFTP server Linux see

"Installation under Linux" on page 52

.

ServerView Update Management 15

1 Introduction

1.2.4

Prerequisites on the Central Management Station (CMS)

On the central management station, ServerView Operations Manager must be installed.

1.2.4.1 Update Management Logon (OS=Windows)

Configuration l

Configuration during the menu-driven installation of the ServerView

Operations Manager:

Step Update Management Logon Information l

During silent installation of the ServerView Operations Manager, o the user account is set to Local System o the ServerView Download Service is not started automatically.

You must change the user account manually.

l

There are two ways to change the user account: o Modify ServerView Operations Manager > Step Update Man- agement Logon Information or o Services - ServerView Download Service - Properties - Log On

When you have changed the user account, you will need to restart the

ServerView Download Service.

Services - ServerView Download Service - Restart

System Policy

If the account was set during installation of ServerView Operations Manager, this user will automatically get the right to logon as a service.

If the account was changed after installation of ServerView Operations Manager, check whether the account exists. If not, please add it.

16 ServerView Update Management

1.2 Prerequisites

Administrative Tools Local Security Policy Security Settings

Local Policies User Rights Assignment Log on as a service

The following applets use this logon and the ServerView Download Service: l

Configuration Wizard l

Download Manager l

Repository Manager

Format of the account l local account: \.<user> recommended: .\Administrator l domain user account: <domain>\<user>

The remote database needs a domain user account

Requirements of this user account: l

Windows administration rights.

l

Read/Write rights for SV OM installation directory l

Read/Write rights for local repository (if configured) l

Right to download (if Download Manager is configured)

You must add this account (e.g. Administrator) to SQL Server as described in the manual ServerView Operations Manager Installation … under Windows in the chapter "Adding a user account with SQL Server admin-

istrator rights", if the following SQL Server instances are used: l

SQL Server 2008 or higher l

Remote database (regardless of version and edition)

ServerView Update Management 17

1 Introduction

1.2.4.2 Configuration of Update Management (Repository, …)

Start the Configuration Wizard of Update Management and make the initial settings for Update Management: l

ServerView Operations Manager - Base Configuration Wizard -

Update Management or l

ServerView Operations Manager - Update Management Con- figuration

The settings relate mainly to: l the Update Repository l the TFTP server l the Download Service l

Proxy and mail

In the final phase of the Configuration Wizard, update data is imported into the repository.

1.2.4.3 Update Data

Update data is the latest updates of BIOS, firmware, agents or drivers for

PRIMERGY servers.

You can get this data from the: l

ServerView Suite DVD 1 min. 7.812 (Windows) / 10.09.09 (Linux), max. 10.12.04

l

ServerView - Update DVD ftp://ftp.ts.fujitsu.com/images/serverview /UPDATE_DVD_

<vers>.<iso> l from the Download section of the Fujitsu Technology Solutions Web server: http://support.ts.fujitsu.com

18 ServerView Update Management

1.2 Prerequisites

There are two ways of maintaining the repository with the latest update data: l

Automatic maintenance

In the Download Manager, define a download task.

The task periodically checks and downloads the latest update data via the internet for servers with inventory data.

l

Manual maintenance

In the Repository Manager, import update data from the latest Server-

View Suite - Update DVD.

ServerView Update Management 19

1 Introduction

1.3

Notes on management stations

1.3.1

Shutdown and restart

A shutdown/restart of the management station is permitted if there are no servers with the job status processing on the Server Details tab in the

Update Manager. Jobs with the status waiting (Job Details tab) are executed after the management station has been restarted, when the Start Time is reached.

A shutdown/restart of the management station is not permitted if there are any servers with the job status processing on the Server Details tab in the

Update Manager.

1.3.1.1 Status after unplanned restart

After an unplanned restart of the management station, the Job Details dialog box may contains the following entries: l

Job Status: error l

Return Text: manager abort

1.3.1.2 Procedure for resolving the errors l

If the agent status on the Server Details tab is ready, you can regenerate the job by copying it (Copy Job).

l

If the agent status is error or busy, first perform a cleanup and then recreate the job by copying it (Copy Job).

1.3.2

Updating the management station with components which needs a reboot

During rebooting the management station, the connection from the web browser (workstation) to the web server (management station) is interrupted.

After rebooting the management station, re-establish this connection (e.g. by pressing F5 on the workstation).

20 ServerView Update Management

1.4 Autonomous Support Packages (ASP)

1.3.3

Multiple management stations

You can run multiple management stations in one network; however, these management stations must be responsible for different servers. This means that the server lists on the various management stations must be different.

1.4

Autonomous Support Packages (ASP)

Autonomous Support Packages (ASPs) are self-extracting, self-installing software packages that allow you to install BIOS, firmware, agents or Addon-products on your server.

To install BIOS, firmware, agents or Add-on-products on a server component, you can call up the appropriate ASP directly.

1.5

PRIMERGY Support Packages (PSP)

A PRIMERGY Support Package (PSP) is the basic element for installing and updating drivers and software products on your PRIMERGY server.

A PSP comprises several packages, which contain the different versions of the same driver or software product.

1.5.1

Current PSP versions

The current versions of PSPs are released with the ServerView Update

DVD, a new version of which comes out approximately every two months.

PSPs can also be downloaded at http://support.ts.fujitsu.com/globalflash

An overview of the components and server models that are supported by the currently released PSPs is provided in the Readme file for the relevant PSP.

ServerView Update Management 21

1 Introduction

1.5.2

Components of a PSP

Each PSP consists of the following elements: l

A zip archive containing the drivers or software products as well as the files required to install the PSP l

Release notes (relnotes.txt) l

A PSP description file (xml file)

PSP description file (xml file)

The description file contains the following information: l

Name of the PSP l

Details of the version and contents of the PSP l

Information on the installation priority of the PSP l

Description of all packages contained in the PSP

For each package contained in the PSP, information is provided on the version and on hardware and software dependencies, e.g. the chassis

ID, system board ID, PCI ID, firmware or operating system version.

Based on the information contained in the description file, the update tool can check on the managed server whether the requirements of the hardware and software dependencies are fulfilled.

22 ServerView Update Management

1.5 PRIMERGY Support Packages (PSP)

1.5.3

Product Detection of Primergy Support Packages

Product detection is available for most PSPs.

Requirements on the server: l

Primergy Support Package FSC_SCAN l

Tools PrimeUp >= V1.15.25

The version of the PSP FSC_SCAN and the PrimeUp tool which comes with the repository must be installed. (Always use the newest package version)

The ServerView Update Agent/GlobalFlash Agent calls the detection function automatically l at every boot.

or l after an update is completed.

The results of the detection are displayed on Update Manager.

Case “Not installed”

Example:

The customer has installed the hardware.The drivers of related products have to be installed for using this hardware.

A "fake" PSP with version "0.0.0.0" is created to show the required product/driver.

Then a real PSP may be installed.

ServerView Update Management 23

1 Introduction

Case “Newer version installed”

Example:

The customer has installed a very new version of a product (perhaps beta), which is not actually produced as a PSP on the FTS site.

A "fake" PSP with version "99.99.99.99" is created, to protect the customers product against accidental overwriting/ updating by Update Manager.

If a PSP with this product/driver version or newer exists at a later date, the protection is canceled and the PSP may be installed/updated with the real

PSP version belonging to this product/driver.

Case “Equal version installed”

Example:

The customer has installed the equal version by themselves, but not as a

PSP (native).

A "fake" PSP with the real version is created.

This PSP may be updated to the real version or newer.

Case “Previous version installed”

Example:

The customer has installed an older version than the version of the actual

PSP and the older version was not installed as a PSP, but by the customer themselves (native).

Because it is an older version than the version of the actual PSP, a "fake"

PSP with version "x.x.99.99" is created. (x.x version of the actual PSP - 1).

An update to the actual version (real version) is possible.

24 ServerView Update Management

1.5 PRIMERGY Support Packages (PSP)

1.5.4

Initial Installation of Primergy Support Packages

Initial installation is possible for all PSPs.

Requirements on the server: l

Primergy Support Package FSC_SCAN l

Tool PrimeUp >= V1.15.24

The version of the PSP FSC_SCAN and the PrimeUp tool which comes with the repository must be installed. (Always use the newest package version)

ServerView Update Management 25

1 Introduction

1.6

Notes on deleting servers from the ServerList

Deletion will be denied ...

Deletion of servers from the ServerList will be denied if update jobs with

Agent Status = busy and Job Details Status = transferring, transferred,

flashing or flashed exist.

Deletion will NOT be denied ...

Deletion of servers from the ServerList will not be denied if update jobs with

Agent Status = absent and Job Details Status = transferring,

transferred, flashing, flashed or rebooting exist.

To avoid error situations you must l check the GlobalFlash Agent / Update Agent on the managed server and if necessary restart it.

l check the LAN connection on the managed server and if necessary repair it.

l do a manual cleanup via the Command Line Interface of the Update

Manager.

Depending on the situation you must use

GFCLI –C

(= Cleanup) or

GFCLI –A

–S

(= forced Cancel)

Cleanup will be done l on the managed server.

l on the TFTP server (in the case a MMB flash).

26 ServerView Update Management

1.7 Typographic conventions

1.7

Typographic conventions

The following typographic conventions are used in this manual:

Convention Explanation

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

Indicates additional relevant information and tips.

bold monospace

Indicates references to names of interface elements.

Indicates system output and system elements for example, file names and paths.

monospace semibold

Indicates statements that are to be entered using the keyboard.

blue continuous text Indicates a link to a related topic.

pink continuous text Indicates a link to a location you have already visited.

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

[abc]

[key]

Indicates options that can be specified (syntax).

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

Screenshots

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

ServerView Update Management 27

1 Introduction

1.8

ServerView Suite link collection

Via the link collection, Fujitsu Technology Solutions provides you with numerous downloads and further information on the ServerView Suite and PRIM-

ERGY servers.

For ServerView Suite, links are offered on the following topics: l

Forum l

Service Desk l

Manuals l

Product information l

Security information l

Software downloads l

Training

The downloads include the following: o Current software statuses for the ServerView Suite as well as additional Readme files.

o Information files and update sets for system software components (BIOS, firmware, drivers, ServerView agents and Server-

View update agents) for updating the PRIMERGY servers via

ServerView Update Manager or for locally updating individual servers via ServerView Update Manager Express.

o The current versions of all documentation on the PRIMERGY

ServerView Suite.

You can retrieve the downloads free of charge from the Fujitsu Technology Solutions web server.

For PRIMERGY servers, links are offered on the following topics: l

Service Desk l

Manuals

28 ServerView Update Management

1.8 ServerView Suite link collection l

Product information l

Spare parts catalogue

Access to the ServerView link collection

You can reach the link collection of the ServerView Suite in various ways:

1. Via ServerView Operations Manager.

l

Select Help Links on the start page or on the menu bar.

This opens the start page of the ServerView link collection.

2. Via the ServerView Suite DVD 2 or via the start page of the online documentation for the ServerView Suite on the Fujitsu Technology Solutions manual server.

You access the start page of the online documentation via the following link: http://manuals.ts.fujitsu.com

l

In the selection list on the left, select Industry standard servers.

l

Click the menu item PRIMERGY ServerView Links.

This opens the start page of the ServerView link collection.

3. Via the ServerView Suite DVD 1.

l

In the start window of the PRIMERGY ServerView Suite DVD 1, select the option Select ServerView Software Products.

l

Click Start. This takes you to the page with the software products of the PRIMERGY ServerView Suite.

l

On the menu bar select LINKS.

This opens the start page of the ServerView link collection.

ServerView Update Management 29

1 Introduction

1.9

Documentation for the ServerView Suite

The documentation for the ServerView Suite can be found on the ServerView

Suite DVD 2 supplied with each server system.

The documentation can also be downloaded free of charge from the Internet.

You will find the online documentation at http://manuals.ts.fujitsu.com

under the link Industry standard servers.

For an overview of the documentation to be found under ServerView Suite as well as the filing structure, see the ServerView Suite sitemap (Server-

View Suite Site Overview).

30 ServerView Update Management

2 Overview

ServerView Update Management allows you to remotely apply the latest updates of BIOS, firmware and drivers onto PRIMERGY servers.

General usage

1. Configure Update Management (see also

"Prerequisites on the Central

Management Station (CMS)" on page 16

) l

The Base Configuration Wizard is used to configure Update Management.

It opens automatically after new installation of ServerView Operations Manager: o Base Configuration Wizard – Update Management step n

Select Yes n

Click Start n

Configuration Wizard: Configure all necessary values

Note: Inventory data is collected automatically for all servers in the ServerList o Base Configuration Wizard – Inventory Management step n

Select “Yes” n

Configure all necessary values n

Go on to item 2 and further items.

ServerView Update Management 31

2 Overview l

The Base Configuration Wizard is not used to configure the

Update Management step.

o Go on to item 2 o Open one of the Update Management applets o Configuration Wizard: Configure all necessary values

Note: Inventory data is collected automatically for all servers in the ServerList o Go on to item 4 and further items.

2. Add managed servers to the ServerList of ServerView Operations Manager.

3. Create Inventory data.

There are two possible ways: l

Automatic maintenance

In the Inventory Manager, define a scheduled inventory task.

l

Manual maintenance

In the Inventory Manager, define a manually started inventory task.

Following collecting of the inventory data and comparison between the inventory data and update data in the repository, the result will be shown in the update icon column of the ServerList and in Update Manager itself.

4. In Update Manager - Update Details tab, create update jobs.

Unless users create update jobs explicitly, managed servers will not be updated.

If you defined security settings for ServerView Update Agent, make sure the prerequisites are met before you create update jobs, see

"Prerequisites on managed servers" on page 12

.

32 ServerView Update Management

5. When the update job is completed, the inventory data and the repository are automatically compared again to ensure that the latest update data has been correctly applied to the managed server.

When upgrading Update Management components please observe the following recommendation to prevent connection problems with the components.

Recommended update sequence:

1. ServerView Update Manager

2. ServerView Update Agent on managed node

3. ServerView Update Agent on TFTP server

ServerView Update Management 33

34 ServerView Update Management

3 Update Procedures

The Update Manager enables you to update drivers, ServerView agents, update agents, firmware and BIOS globally and locally on PRIMERGY servers. You can use the update procedures described below to do this.

Which particular components can be updated with which procedure is described in the following files on the ServerView Suite DVD 1:

Windows

SVSSoftware\Software\ServerView\Windows\GlobalFlash\Agents\

OnlineFlash\primlist_win.htm

Linux:

SVSSoftware\Software\ServerView\Linux\GlobalFlash\Agents\

OnlineFlash\primlist_lx.htm

ServerView Update Management 35

3 Update Procedures

3.1

Online update

This procedure allows you to update components under the control of the operating system that is currently running (Windows, Linux). In this case the

Update Manager uses tools which are provided by the software vendors.

Figure 2: Diagram of the update procedure (online)

1. The Inventory Manager creates inventories by collecting information on the installed software and firmware components of all servers in the server list and storing this information in a database. The Inventory Manager can create the inventories either on command or cyclically.

2. The Update Manager compares the inventories entered in the database with the software and firmware components in the repository. Based on the differences arising from this comparison, it then creates a list of components and servers that need updating.

3. If you are updating via the graphical user interface select the components which are to be updated. If you are working with the CLI use the -U option to specify the repository from which the update data is to be taken.

36 ServerView Update Management

3.1 Online update

4. The Update Manager fetches the update data required from the repository and defines the update jobs. In addition to the actual update data each online update job contains an update tool for the component concerned and the job control file with the required parameters.

5. The update jobs are transferred to the update agent (socket communication).

6. The update agent starts an update handler (an auxiliary routine of the agent), and this starts the update tool with the parameters required for the components concerned.

7. The values returned by the update tool are evaluated by the handler and returned to the agent.

8. The update agent updates the job status information.

9. The Update Manager fetches the current status and error information and presents it on the graphical user interface or, if you are using the

CLI, places it in result files.

10. Depending on the request-specific parameters, the server may need to be rebooted by the management station at the end of the update operation in order to enable the updated components.

If you use the command line interface for the update, the reboot does

NOT occur automatically. It must be explicitly executed with the command GFCLI -R.

The update procedure has then been completed.

ServerView Update Management 37

3 Update Procedures

3.2

Update via TFTP server

This procedure is used to update PRIMERGY system components which cannot be updated using the update tools available under Windows, Linux or

DOS either at all or only with great effort, or to update autonomous hardware systems on which none of these three operating systems runs. These system components and hardware systems are updated via a ServerView

Update Agent of the type TFTP Server.

The system components and hardware systems must be able to fetch an image from a TFTP server and to update themselves. They must have interfaces via which l the configuration data can be read (e.g. version, name, MAC address, etc.).

l the required parameters (IP address, path name and image name on the

TFTP server) can be set.

l the update procedure can be started.

The following control interface is currently implemented for this purpose in the Update Manager:

SNMP (reading) and HTTP (writing)

for updating a hardware system, e.g. the management blade of the blade servers BX600 and BX900

In the case of BX600 MMB S2 there may be two alternate management blades in operation (master and slave) which have just one joint update IP address for updating purposes. In this case when an update procedure takes place both management blades are always updated via this update IP address.

38 ServerView Update Management

3.2 Update via TFTP server

3.2.1

Updating a hardware system

Updating a hardware system taking a management blade as an example

Figure 3: Diagram of the update procedure (management blade via TFTP server)

1. The Inventory Manager on the management server uses SNMP commands to fetch the required inventory data from the management blade.

When you are updating via the graphical user interface the data is presented on the graphical user interface.

2. The Update Manager compares the inventories entered in the database with the software and firmware components in the repository. Based on the differences arising from this comparison, it then creates a list of components and servers that need updating.

3. BX600 MMB S2 only:

The login for HTTP is checked. This is done directly with the management blade using HTTP commands.

Update via Update Manager Linux: Login is checked during update.

ServerView Update Management 39

3 Update Procedures

4. The object-specific update job for the management blade is generated by the Update Manager.

5. The Update Manager transfers the update images and the update job

(incl. update handler and update tool) to the TFTP server and starts the update job (socket communication between the Update Manager and the update agent on the TFTP server).

6. The update agent starts the update handler, and this starts the update tool with the required parameters from the job control file supplied.

7. The update tool starts the dialog with the management blade and transfers the required update parameters using HTTP commands.

8. The download of the images from the TFTP server and the update procedure are then controlled completely by the management blade (TFTP communication).

9. The return values from the components involved are transferred in the reverse order from the update tool via the update handler to the update agent.

10. The update agent updates the job status information.

11. The Update Manager fetches the current status and error information and presents it on the graphical user interface or, if you are using the

CLI, places it in result files.

The update procedure has then been completed.

40 ServerView Update Management

3.3 Access to update data

3.3

Access to update data

To update the managed servers the Update Manager requires the corresponding update data. This data is contained in an repository with the following subdirectories:

Agent-Win Agent-Lx

FibreChannelController LanController

PrimSupportPack-Win RemoteServiceBord

SystemBoard Tools

BladeSystem

ManagementController

ScsiController

The following options are available for accessing this data: l

Via the directory Firmware on the ServerView Suite DVD 1 or on the

Update DVD.

l

Via the Fujitsu Technology Solutions web server from which the update data can be saved to a repository which you have created on an arbitrary drive of the management server.

You can update this repository regularly by means of the Download Manager from the Fujitsu Technology Solutions web server.

Content of Update Data

Following a successful systemtest the new components will be added.

After their official release, new components (BIOS, firmware, agents, drivers) and new versions are added to the repository.

For additional information about Primergy Support Packages see PRIM-

ERGY ServerView Suite DVD 1 under Software Products - ServerView -

Maintenance & Update - Update - PRIMERGY Support Packages - Info column.

ServerView Update Management 41

42 ServerView Update Management

4 Installing ServerView Update Agents

To find out which servers are supported and which system components can be updated with the various update procedures please refer to the relevant files on the ServerView Suite DVD 1 under ServerView Suite – Software

Products - ServerView – Maintenance & Update - Update (Supported

Systems and Info columns).

The ServerView Update Agent needs around 3 minutes to start up completely.

4.1

Installation on the managed server

4.1.1

Requirements for installation

l

Installation sequence: 

Install ServerView agents before ServerView Update Agent.

l

For an online update only a functioning LAN connection is required.

l

For an Update via TFTP Server refer to section

"Installation on the

TFTP server" on page 51

.

The following difference exist with regard to the components to be updated via the TFTP server:

In the case of autonomous hardware systems on which no Windows,

Linux or DOS operating system runs (e.g. management blades) it is not necessary to install the update agent on the managed system.

Management blades and connection blades are always updated via a TFTP server.

ServerView Update Management 43

4 Installing ServerView Update Agents

4.1.2

Requirements for uninstallation

If you want to uninstall ServerView Update Agent, ensure that all jobs on the involved systems (management server, TFTP server, managed server) are finished or deleted.

Uninstallation sequence:

1. Uninstall ServerView Update Agent

2. Uninstall ServerView agents

Several errors can occur if user does not use correct order of uninstallation.

44 ServerView Update Management

4.1 Installation on the managed server

4.1.3

Installing Update Agent V6.0 (or later)

4.1.3.1 Installation under Windows

The following procedures are available for installation: l

Menu-Driven Installation (FTASetup.exe) l

Installation via the Command Line Interface l

Installation via ASP (Autonomous Support Package), SV Update Agent

>=V5.50

Menu-driven Installation (FTASetup.exe)

Update agent version 4.91 and higher is only installed if the server is onlineupdate-capable, i.e. online tools for updating the firmware are available. Older systems are not supported as of Update Management V6.0.

You start the installation via the FTASetup.exe file, which you will find on the

ServerView Suite DVD 1 under SVSSoft-

ware\Software\ServerView\Windows\GlobalFlash\Agents\OnlineFlash.

Start the menu-driven installation as follows:

1. Double-click the FTASetup.exe file.

2. Confirm the license conditions.

3. Define the parameters for the security settings.

ServerView Update Management 45

4 Installing ServerView Update Agents

Figure 4: Security Settings

Security Settings

Account Check

Specifies whether access authorization should be checked when the server is accessed. If this option is enabled, you can use access authorization via certificates or via standard login.

User Group for Update

Name of the local user group l

This option is mandatory for access authorization via standard login.

l

If you use certificates, it is not really necessary to enter a user group, but it is recommended for using the update agent, if no certificate is available or the validation of a certificate fails.

46 ServerView Update Management

4.1 Installation on the managed server

All users in this group are authorized to perform the update procedure. The user group GFUSER is preset. If you want to use the

GFUSER group you must configure it under Windows.

But you can also use any other user group.

In the case of an update installation the default values are assigned to the existing configuration values.

Installation via the Command Line Interface (FTASetup.exe)

You can install the update agent at command level using the following command :

FTAsetup -noaccountcheck {0|1}

[-flashusergroup <user_group>]

FTAsetup -GFAU

The options have the following meanings:

-noaccountcheck { 0 |1}

You use this option to enable (0) or disable (1) the password query.

-flashusergroup <user_group>

When the password query is enabled this option can be used to specify the name of a local user group. All users in this user group are authorized to perform the update procedure. If this option is omitted, GFUSER is the default.

-GFAU

You use this option to start an update installation for the agents. In contrast to a complete new installation (without this option) parameters already set in the update agent are retained.

In the case of an update installation the default values are assigned to the existing configuration values.

ServerView Update Management 47

4 Installing ServerView Update Agents

Installation via ASP (Autonomous Support Package), SV Update

Agent >=V5.50

You start the installation via the installation package SVUpdateAgent_Win_

ASP_<vers>.exe, which you will find on the ServerView Update DVD under:

Firmware - Agent-Win - SV-Update-Agent.

You can install the update agent at the command level using the following command: start /wait SVUpdateAgent_Win_ASP_<vers>.exe

4.1.3.2 Installation under Linux or VMWare (ESX)

Update agent version 4.91 and higher is only installed if the server is onlineupdate-capable, i.e. online tools for updating the firmware are available. Older systems are not supported as of Update Management V6.0.

Update Agent <= V5.00

You start the installation via the installation package SMAWgfa-<Release>-

<Version>.rpm, which you will find on the ServerView Suite DVD 1 under

Firmware - Agent-Lx - SV-Update-Agent.

You can install the update agent at command level using the following command: rpm {-i | -U --nopreun --nopostun}

SMAWgfa-<Release>-<Version>.rpm

The options have the following meanings:

-i

-U

You use this option to start the initial installation.

You use this option to start an update installation.

48 ServerView Update Management

4.1 Installation on the managed server

--nopreun --nopostun (only for update installations)

If these options, which must always be specified together, are selected, the uninstallation routines do not run when an update installation takes place. Parameters already set in the update agent are retained.

Update Agent >= V5.01

You start the installation via the installation package SVUpdateAgent_Lx_

V<vers>.scexe, which you will find on the ServerView Suite DVD 1 under

SVSSoftware - Software - ServerView - Linux - GlobalFlash - Agents -

OnlineFlash.

You can install the update agent at the command level using the following command: sh SVUpdateAgent_Lx_V

<vers>.scexe

Configuration of the Update Agent

When you have executed the command, the parameters are assigned default values in the /opt/SMAW/SMAWgfa/cfg/LinuxFwuAgent.cfg file and you can change these to suit your requirements.

FlashUserGroup= <user-group>

Name of the primary user group which is entered in /etc/passwd for the user. All users in this group are authorized to execute the update procedure (default GFUSER).

If it does not yet exist the GFUSER group with the user globalflash and the password globalflash is automatically set up during installation.

This parameter is evaluated only when NoAccountCheck = 0.

NoAccountCheck= <n> n = 0 (password query enabled; default value) n = 1 (password query disabled)

ServerView Update Management 49

4 Installing ServerView Update Agents

TraceFile= <file>

File in which the agent’s actions are logged when TraceLevel > 0.

The directory must exist if given in <file>.

Default file name: /opt/SMAW/SMAWgfa/data/gf_agent.log

TraceLevel= <n> n = 0 (no tracing) n = 2 (tracing of errors) n = 3 (tracing of the commands) n = 5 (detailed tracing)

Default TraceLevel = 2

Parameter changes only become effective after the /etc/init.d/globalflash restart command has been executed.

In the case of an update installation the default values are assigned to the existing configuration values.

Uninstallation under Linux

Uninstallation is performed using the rpm -e SMAWgfa command.

50 ServerView Update Management

4.2 Installation on the TFTP server

4.2

Installation on the TFTP server

The PXE or TFTP service should be stopped, if you use other PXE/TFTP services, because a parallel use of two services might cause problems.

For how to install ServerView Update Agent, see section

"Installing Update

Agent V6.0 (or later) " on page 45

.

4.2.1

Installation under Windows

Installation sequence:

1. TFTP Server

2. ServerView Agents

3. ServerView Update Agent

To install TFTP server you have the following options: l

PRIMERGY ServerView Suite DVD 1

Use <dvd-root>:\Setup\WebUI\FjPXEServer.msi to install a TFTP service on a TFTP server system.

l

Deployment Manager (Deployment Service) l

ServerView Installation Manager > Remote Installation

ServerView Update Management 51

4 Installing ServerView Update Agents

4.2.2

Installation under Linux

Installation sequence:

1. TFTP Server

2. ServerView Agents

3. ServerView Update Agent

To install TFTP server l

Install software package tftp l

TFTP must be enabled (file /etc/xinetd.d/tftp: param disable=no) l

Network service xinetd must be running l

If a firewall is activated: allow tftp

52 ServerView Update Management

5 User Interface

The Update Management user interface comprises the interfaces of the individual applications. The Configuration wizard starts automatically the first time you open Update Management. This wizard allows you to make global settings for all applications.

l

Update Manager l

Repository Manager l

Download Manager l

Configuration

5.1

Update Manager Main Window

The main window contains the following elements (from top to bottom): l the ServerView Suite header l the ServerView Suite menu bars l the work area with the tree structure on the left and tabs on the right.

ServerView Update Management 53

5 User Interface

Figure 5: Update Manager Main Window

The appearance of the tabs is determined by the entry you select in the tree structure. The following combinations are possible:

Tree structure

Work area tabs

Servers

List of servers

Server

Details

Information about the selected servers

Update Details

Component list in the form of a tree structure (depends on the selection in the server list)

Updates for the components selected in the component list

Job Details

Information about the jobs that exist for the selected servers

54 ServerView Update Management

5.1 Update Manager Main Window

Tree structure

Work area tabs

Updates

List of updates

Jobs

List of jobs

Server

Details

Update Details

Information about all servers for which the

Server list in the form of a tree structure

(depends on selected components are relin the update evant the selection list)

Updates for all components that are relevant for the selected servers

Information about all servers for which the selected jobs are relevant

Combination not permitted

Job Details

Combination not permitted

Information about the selected jobs

ServerView Update Management 55

5 User Interface

5.1.1

The tree structure

Figure 6: Update Manager tree structure

The tree structure is on the left of the work area in the Update Manager and provides various views, divided into different groups, of the servers in a domain. You can filter these views within the groupings down to object and component level.

56 ServerView Update Management

5.1 Update Manager Main Window

Tree structure Groupings

Servers Information about Servers within the domain

All Servers

All servers within the domain

Groups

Customized groups, which you created with the Server-

List application

In the groups All Servers and Groups the symbols are showing the cumulated update status.

An update is not required

An update is recommended

An update is urgently required

ServerView Update Management 57

5 User Interface

Tree structure Groupings

Servers

(continued)

Update mandatory

Servers on which an update is urgently required

Update recommended

Servers on which an update is recommended

In the groups Update mandatory and Update rec-

ommended, instead of update status icons, server icons are displayed, because the name of the group is the same as the name of the update status of the servers in the group.

For a description of the icons, see the online help of the

ServerBrowser application.

1. Start the ServerBrowser application.

2. Click Help - ON ServerBrowser

The ServerBrowser online help is displayed.

3. In the section Browsing Pane, a description of the server icons is displayed.

Unsupported Servers

All checked servers with existing inventory data which are not supported by the current Update Manager

Unknown Servers

All servers which could not be checked because no inventory data exist.

Update done

Servers on which no update is required.

58 ServerView Update Management

5.1 Update Manager Main Window

Tree structure Groupings

Updates Software and firmware components of the servers

All Components

All components, regardless of their version

Upgrades

Components for which an upgrade is available

Downgrades

Components for which a downgrade is available

Installed Updates

All components installed on the servers

User Collections

User-defined component groups, which you create in the RepositoryManager

Update group

ServerView Update Management 59

5 User Interface

Tree structure Groupings

Jobs Jobs defined for the update of the servers

Root All Jobs

All jobs, regardless of status

Waiting Jobs

Jobs that are waiting for the time to transfer the updates from the management server to the PRIMERGY servers

Jobs in Progress

Jobs that are currently in the update phase

Ready Jobs

Jobs that were executed without errors

(if a restart is required after an update phase, this status is not displayed until the server has been restarted)

Failed Jobs

Jobs that failed

Completed jobs

Failed jobs

Jobs in process

Waiting jobs

60 ServerView Update Management

5.1 Update Manager Main Window

5.1.2

Server Details tab

The Server Details tab displays information about servers, depending on what you have already selected in the tree structure.

Tree structure Server Details Tab

Servers Information about the selected servers

Updates

Jobs

Servers for which the selected components are relevant

Servers for which the selected jobs are relevant

To open the tab, click the Server Details tab in the main window.

Figure 7: Server Details tab

In the table, a context menu is available. To open the context menu, right-click an entry in the table.

ServerView Update Management 61

5 User Interface

The columns in the table have the following meanings:

Column

Icon

Meaning

General update status of the server

An update is not required.

An update is recommended.

An update is urgently required.

Name

Network

Model

To evaluate the General update status of server, the contents of the following groups are checked: l

Unapplicable Updates l

Upgrades l

All Components

Opens the Filtering for <column> dialog box, where you specify which rows are to be displayed in the table.

Name of the server

IP address of the server

Model name of the server

62 ServerView Update Management

5.1 Update Manager Main Window

Column

Agent Status

Meaning

Status of the update agent on the server ready error

The server is ready for the update phase.

An error occurred during the update phase.

You must save the diagnostics about the failed job, then initialize the update agent with the Cleanup function.

absent busy

No update agent is installed on the server or the agent is not running.

The server is currently in the update phase.

unknown The agent status could not be determined.

not_managable The ServerView agent cannot currently be reached on the computer via SNMP.

ServerView Update Management 63

5 User Interface

Column

Agent Access

Meaning

Access status of the update agent on the server granted restricted unrestricted trusted certified not certified

Logon to the server has already been successfully completed. You have access to the server.

Access to the server is currently restricted. Log on must be performed with the appropriate user ID and password on the server.

Logon is not required to access the server.

Since the server was unavailable at the time the logon was attempted, the logon data was saved under the assumption that it was correct.

A valid certificate is installed.

The managed server is ready for single sign-on.

No valid certificate is installed.

The managed server is not ready for single sign-on.

64 ServerView Update Management

Column

Job Status

Last Check

5.1 Update Manager Main Window

Meaning

Status of the relevant jobs specified for the server done waiting processing error

All components have been updated and the job is now completed.

The job is waiting to be executed

(this is the status before the data transfer begins).

The job is currently being executed.

Possible reasons: l

The update of at least one component failed.

l

Check-Job was not successful l

Cleanup-Job was not successful l

Status could not be retrieved

Last comparison of the server inventory with the repository

<Date>

Failed

N/A

Date of the last successful check

The last check failed.

To display more information, click

Show Details and then Show Log-

File in the dialog box that appears.

A check has not been performed for this server yet.

ServerView Update Management 65

5 User Interface

Buttons

Complete Update

Automatically establishes a list of all components that can be updated on the previously selected server. The Create Job wizard then opens, via which you start the update of the identified components.

This button is only enabled if you are logged on as administrator.

Logon

Opens the Logon dialog box, where you can log on to selected servers.

This button is only activated if you have selected one or more servers in the table.

Cleanup

You can use the cleanup function to reset the update agent on a server to a defined status. This function may be required, for example, if the update agent was accessed by another management server (invalid configuration!), or if a job failed unexpectedly (Job Status = error, Returnt-

ext = Pending Job).

Show Details

Opens the Server Details dialog box, which displays information about the selected server.

This button is only activated if you have selected a server.

Additional functions in the context menu

Force Check

A job with the name Check_xx is created (xx = sequence number). It performs another comparison (check) of the server inventory with the repository. This job is displayed on the Job Details tab. The dialog box will be closed automatically.

Show Logfile

Displays the log file for the currently selected server.

Show History

Opens a web page showing the flash log for the selected server.

66 ServerView Update Management

5.1 Update Manager Main Window

Show Updates

Opens the Update Details tab to display update information about the selected server.

5.1.3

Update Details tab

The Update Details tab contains information about updates. It comprises the following elements: l

The update details list (tree structure) l

A table that contains the updates that match your selection in the server list and update details list.

To open the tab, click the Update Details tab in the main window.

Figure 8: Update Details tab

In the table, a context menu is available. To open the context menu, right-click an entry in the table.

ServerView Update Management 67

5 User Interface

The content of the update details list depends on the entry that you have already selected in the tree structure.

Tree structure

Servers

Update details list (Update Details Tab)

Displays the components belonging to the selected servers.

In the update details list, you can filter the components displayed in the table according to the following groups: l

All Components: Displays all components belonging to the servers selected in the server list l

Upgrades: Displays the upgrades associated with the servers selected in the server list l

Downgrades: shows all downgrades of the selected servers in the server list.

l

Installed Updates: Displays the updates installed on the servers selected in the server list.

l

Unapplicable Updates: Displays the updates that cannot be installed. An explanation of why the updates cannot be installed is displayed in the

Update Details dialog box. To open this dialog box, click Show Details.

l

Released Updates: Displays the updates associated with the servers selected in the server list which have been released in the Repository Manager.

l

Inventory Information: Displays all installed firmware and drivers on the servers selected in the server list, even if they are not included in the repository.

l

User Collections: Displays the user-specific update groups for the servers selected in the server list

68 ServerView Update Management

5.1 Update Manager Main Window

Tree structure

Servers

(continuation)

Updates

Jobs

Update details list (Update Details Tab)

In general, only the installed update versions contained in the underlying repository are displayed in the table.

In the case of each upgrade, only the latest version is displayed in the table and, in the case of each downgrade, only the next older version found in the repository is displayed in the table.

Nevertheless, the version of the update can be selected when executing the Create Job

Wizard later.

Displays the servers that contain the selected components

Combination not permitted

In the table, a context menu is available. To open the context menu, right-click an entry in the table.

The columns in the table have the following meanings:

Column

Icon

Meaning

Importance of the update

An update is recommended.

An update is urgently required.

An update is not required.

Opens the Filtering for <column> dialog box, where you specify which rows are to be displayed in the table.

ServerView Update Management 69

5 User Interface

Column

Server Name

Category

Component

Installed

Version

New Version

Reboot

Job Name

Meaning

Name of the server

Group to which the component belongs

Name of the component

Version of the installed update

Update version that is to replace the installed version

Indicates whether the server is restarted after the components are updated. (Yes/No)

auto (for components of the blade systems group only)

The component itself decides whether a reboot is necessary or not.

If the update is already assigned to a job, the name of this job is displayed here.

Buttons

Create Job

Opens the Create Job Wizard, which allows you to create a job for the selected updates.

Show Details

Opens the Update Details dialog box, which provides a detailed information about the selected update.

70 ServerView Update Management

5.1 Update Manager Main Window

5.1.4

Job Details tab

The Job Details tab displays information about jobs, depending on what you have already selected in the tree structure.

Tree structure

Servers

Updates

Jobs

Job Details Tab

Job information for the selected servers

Combination not permitted

Information about selected jobs

To open the tab, click the Job Details tab in the main window.

Figure 9: Job Details tab

ServerView Update Management 71

5 User Interface

In the table, a context menu is available. To open the context menu, right-click an entry in the table.

The columns in the table have the following meanings:

Column

Icon

Meaning

Status of the current jobs

All components have been updated and the job is now completed.

The job is waiting to be executed (this is the status before the data transfer begins).

The job is currently being executed.

Possible reasons: l

The update of at least one component failed.

l

Check-Job was not successful l

Cleanup-Job was not successful l

Status could not be retrieved

Opens the Filtering for <column> dialog box, where you specify which rows are to be displayed in the table.

Name Name of the job

Server Name Name of the server

72 ServerView Update Management

5.1 Update Manager Main Window

Column

Status

Start Time

Meaning

Current job status waiting transferring transferred flashing flashed rescanning rebooting done error

The job is waiting to be executed (this is the status before the data transfer begins).

The job is currently being transferred.

The job has been successfully transferred and is now waiting for the start of the update procedure.

The job is currently in the update phase.

The update has been performed successfully on the server.

The inventory of the server is being redetermined.

The server is currently rebooting.

All components have been updated and the job is now completed.

Possible reasons: l

The update of at least one component failed.

l

Check-Job was not successful l

Cleanup-Job was not successful l

Status could not be retrieved

Time when the flash of the updates is started

ServerView Update Management 73

5 User Interface

Column

Severity

Meaning

Cumulated status of the updates contained in the job (the most critical status is shown in each case)

recommended An update is recommended.

mandatory An update is urgently required.

normal An update is not required.

Released Shows whether the job is released (yes) or not (no).

Description Description of the job (comment).

Buttons

Copy Job

Opens the Copy Job Wizard, which allows you to copy the selected job to other servers.

Show Details

Opens the Job Details dialog box, which displays detailed information about the selected job.

Edit Job

Opens the Edit Job dialog box, which allows you to change some properties of the selected job.

Delete

Deletes the selected job. A confirmation prompt appears before deletion is initiated.

Release

Releases the selected jobs for execution on other PRIMERGY servers

(for example, after they have been processed without errors on a test host). Jobs are indicated as released for information purposes only.

74 ServerView Update Management

5.1 Update Manager Main Window

5.1.5

Dialog boxes and wizards

Update Manager provides the following dialog boxes and wizards.

In the Server Details tab: l

LogOn dialog box l

Cleanup wizard l

Show Server Details dialog box

In the Update Details tab: l

Create Job wizard o Change TFTP Address dialog box o Change Flash Address dialog box l

Show Update Details dialog box o Show Release Notes dialog box o Show PSP Details dialog box

In the Job Details tab: l

Copy Job wizard o Change TFTP Address dialog box o Change Flash Address dialog box l

Show Job Details dialog box

ServerView Update Management 75

5 User Interface

5.1.5.1 LogOn dialog box

The LogOn dialog box allows you to log on to all servers that require user authentication (AgentAccess = restricted or not certified).

To open the dialog box, choose any servers on the Server Details tab and click Logon.

Figure 10: LogOn dialog box

The table in the dialog box displays all servers you selected on the Server

Details tab. All servers with restricted or not certified access status are selected automatically.

If you have selected servers with an access status other than

restricted or not certified, Update Manager ignores attempts to log on to these servers.

Column

Server

Manageable

Meaning

Name of the server

Availability of the server

76 ServerView Update Management

5.1 Update Manager Main Window

Column Meaning

Agent Access Access status of the update agent on the server granted restricted unrestricted trusted certified not certified

Logon to the server has already been successfully completed. You have access to the server.

Access to the server is currently restricted. Log on must be performed with the appropriate user ID and password on the server.

Logon is not required to access the server.

Since the server was unavailable at the time the logon was attempted, the logon data was saved under the assumption that it was correct.

A valid certificate is installed.

The managed server is ready for single sign-on.

No valid certificate is installed.

The managed server is not ready for single sign-on.

User Authentication

Login user ID and password for access control.

This parameters are only required if the ServerView update agent on the managed node is configured with AccountCheck.

If the server is to be updated via a TFTP server, enter user ID and password for access to the controller (MMB, switch blade, iRMC)

ServerView Update Management 77

5 User Interface check and set Password

Checks the logon data and sets the access rights on the selected servers

(if Manageable = yes). The password is valid for the current session.

If the server is unavailable, the logon data is stored under the assumption that it is correct (if Manageable = no).

Remove Server from List

Removes the selected server from the displayed list.

78 ServerView Update Management

5.1 Update Manager Main Window

5.1.5.2 Cleanup Wizard

You can use this wizard to clean up the update agent of a server if the agent status is error.

Resetting the update agent may be necessary if a job stops with Job Status

= error and the return text contains the message Pending Jobs. You can view the return text for a job by selecting the job on the Job Details tab and opening the Show Job Details dialog. Pending Jobs is returned if the update agent is already processing jobs from another management station or jobs started via CLI.

The Cleanup Wizard comprises several dialog boxes to guide you through the individual steps. All required steps are displayed in the tree structure on the left.

To open the Cleanup Wizard, select the server on the Server Details tab and click Cleanup.

LogOn step (Cleanup Wizard)

LogOn is the first step in the wizard. Here you log on to all servers that require user authentication (AgentAccess = restrictedor not certified).

Figure 11: LogOn step

ServerView Update Management 79

5 User Interface

The table displays all servers you selected on the Server Details tab. All servers with restricted or not certified access status are selected automatically.

If you have selected servers with an access status other than

restricted or not certified, Update Manager ignores attempts to log on to these servers.

Column

Server

Meaning

Name of the server

Manageable Availability of the server

Agent Access Access status of the update agent on the server granted restricted unrestricted trusted certified not certified

Logon to the server has already been successfully completed. You have access to the server.

Access to the server is currently restricted. Log on must be performed with the appropriate user ID and password on the server.

Logon is not required to access the server.

Since the server was unavailable at the time the logon was attempted, the logon data was saved under the assumption that it was correct.

A valid certificate is installed.

The managed server is ready for single sign-on.

No valid certificate is installed.

The managed server is not ready for single sign-on.

80 ServerView Update Management

5.1 Update Manager Main Window

User Authentication

Login user ID and password for access control.

This parameters are only required if the ServerView update agent on the managed node is configured with AccountCheck.

If the server is to be updated via a TFTP server, enter user ID and password for access to the controller (MMB, switch blade, iRMC) check and set Password

Checks the logon data and sets the access rights on the selected servers

(if Manageable = yes). The password is valid for the current session.

If the server is unavailable, the logon data is stored under the assumption that it is correct (if Manageable = no).

Remove Server from List

Removes the selected server from the displayed list.

ServerView Update Management 81

5 User Interface

Enter TFTP step (Cleanup Wizard)

Enter TFTP is the second step in the wizard. This step is only displayed if the cleanup runs via TFTP server (for example, in the case of a management blade or a connection blade).

Figure 12: Enter TFTP step

The table shows a subset of the servers selected on the tab. For the servers displayed here, cleanup will be done via the TFTP server.

Column

Server

TFTP Address

Temporary Flash

Address

Meaning

Name of the server

IP address of the TFTP server

In the Cleanup Wizard this field remains empty.

Change TFTP Address

Click this button to change the IP address of the TFTP server for the selected server.

Change Flash Address

Click this button to change the temporary IP address used for flashing the management blade (MMBS2 only).

82 ServerView Update Management

5.1 Update Manager Main Window

Schedule Job step (Cleanup Wizard)

Schedule Job is the last step in the wizard. Here you specify the time at which the cleanup is to be executed.

Figure 13: Schedule Job step

Make sure that the server on which the cleanup is to be performed is up and running at the time of execution.

Job Name

Unique name of the job

Default: CLEANUP_<sequence number, starts at 1>

Description

Description of the job as a comment (optional).

Exec Time

Start time for executing the job

Immediate Starts the job as soon as you click Finish to exit the wizard.

Later Starts the job at the specified time.

Select date, hours, and minutes.

ServerView Update Management 83

5 User Interface

5.1.5.3 Server Details dialog box

The Server Details dialog box provides detailed information relating to the server you selected on the Server Details tab.

If you selected a server of the group Unsupported Servers or

Unknown Servers, no server data will be displayed in this dialog.

To open this dialog box, click Show Details on the Server Details tab.

Figure 14: Server Details dialog box

Name

System name of the server

Network

IP address of the server

84 ServerView Update Management

5.1 Update Manager Main Window

Display Name

Name of the server

For a standalone server:

<server name>

For a blade server:

<blade server name>-<slotID>

For a host system of a virtual system:

<server name of the virtual system>-host

For a guest system of a virtual system:

<server name of the virtual system>-<servername>

Update Type

Method used to perform the update online unknown illegal old agent

Update is performed while the operating system is running.

The update type could not be determined because l

The server cannot be reached.

l

No update agent is installed on the server.

l

An update agent ≥ V4.80 was manually installed on an unsupported server type (e.g. offline server).

l

The model name of the server could not be determined. In this case, there is no entry in the Model column.

A GlobalFlash agent < V4.6x is installed.

For the server to be supplied with further updates, the

GlobalFlash agent must be updated first.

ServerView Update Management 85

5 User Interface

Agent Status

Status of the update agent on the server ready error absent

The server is ready for the update phase.

An error occurred during the update phase.

You must save the diagnostics about the failed job, then initialize the update agent with the Cleanup function.

No update agent is installed on the server or the agent is not running.

busy unknown

The server is currently in the update phase.

The agent status could not be determined.

not_managable The ServerView agent cannot currently be reached on the computer via SNMP.

Agent Access

Access status of the update agent on the server granted restricted unrestricted trusted certified not certified

Logon to the server has already been successfully completed. You have access to the server.

Access to the server is currently restricted. Log on must be performed with the appropriate user ID and password on the server.

Logon is not required to access the server.

Since the server was unavailable at the time the logon was attempted, the logon data was saved under the assumption that it was correct.

A valid certificate is installed.

The managed server is ready for single sign-on.

No valid certificate is installed.

The managed server is not ready for single sign-on.

86 ServerView Update Management

5.1 Update Manager Main Window

Update Status

Cumulated update status of the server (the most critical status is displayed in each case) normal An update is not required.

recommended An update is recommended.

mandatory An update is urgently required.

Display Update Status

Here you can forcibly change the value of Update Status, if necessary.

For example, you can change the Update Status to normal (meaning an update is not required) if updates are recommended but you explicitly want the update job to skip this server.

normal Update Status forcibly becomes normal.

recommended Update Status forcibly becomes recommended.

mandatory automatic

Update Status forcibly becomes mandatory.

The value of Update Status is used as is. (default)

Check Status

Status of the last check

OK

Failed

The last check was performed successfully.

The last check failed.

To display more information, click Show Logfile.

ServerView Update Management 87

5 User Interface

Job Status

Status of the relevant jobs specified for the server done waiting processing error

All components have been updated and the job is now completed.

The job is waiting to be executed (this is the status before the data transfer begins).

The job is currently being executed.

Possible reasons: l

The update of at least one component failed.

l

Check-Job was not successful l

Cleanup-Job was not successful l

Status could not be retrieved

Comment

Description field

Last Check

Last comparison result of the server inventory with the repository

Date

Failed

N/A

Date of the last successful check.

The last check failed.

To display more information, click Show LogFile.

A check has not yet been performed for this server.

Last Inventory

Time at which the inventory was created on the server

Last Repository

Time at which the repository was last imported

Model

Model name of the server

88 ServerView Update Management

5.1 Update Manager Main Window

Operating Systems

Information about the operating system

Manageable

Availability of the server yes no

The ServerView agent can be reached via SNMP.

The ServerView agent cannot be reached.

Buttons

Force Check

A job with the name Check_xx is created (xx = sequence number). It performs another comparison (check) of the server inventory with the repository. This job is displayed on the Job Details tab. The dialog box will be closed automatically.

Show Logfile

Displays the log file for the currently selected server.

Show History

Opens a web page showing the flash log for the selected server.

ServerView Update Management 89

5 User Interface

5.1.5.4 Create Job Wizard

This wizard allows you to create new update jobs. The wizard comprises several dialog boxes to guide you through the individual steps. All required steps are displayed in the tree structure on the left.

To open the wizard, choose any servers and updates on the Update Details tab and click Create Job.

LogOn step (Create Job Wizard)

LogOn is the first step in the wizard. Here you log on to all servers that require user authentication (AgentAccess = restricted or not certified).

Figure 15: LogOn step

The table displays all servers for which the updates you selected on the

Update Details tab are relevant. All servers with restricted or not certified access status are selected automatically.

If you have selected servers with an access status other than

restricted or not certified, Update Manager ignores attempts to log on to these servers.

90 ServerView Update Management

5.1 Update Manager Main Window

Column

Server

Meaning

Name of the server

Manageable Availability of the server

Agent Access Access status of the update agent on the server granted restricted unrestricted trusted certified not certified

Logon to the server has already been successfully completed. You have access to the server.

Access to the server is currently restricted. Log on must be performed with the appropriate user ID and password on the server.

Logon is not required to access the server.

Since the server was unavailable at the time the logon was attempted, the logon data was saved under the assumption that it was correct.

A valid certificate is installed.

The managed server is ready for single sign-on.

No valid certificate is installed.

The managed server is not ready for single sign-on.

ServerView Update Management 91

5 User Interface

User Authentication

Login user ID and password for access control.

This parameters are only required if the ServerView update agent on the managed node is configured with AccountCheck.

If the server is to be updated via a TFTP server, enter user ID and password for access to the controller (MMB, switch blade, iRMC) check and set Password

Checks the logon data and sets the access rights on the selected servers

(if Manageable = yes). The password is valid for the current session.

If the server is unavailable, the logon data is stored under the assumption that it is correct (if Manageable = no).

Remove Server from List

Removes the selected server from the displayed list.

92 ServerView Update Management

5.1 Update Manager Main Window

Change Version step (Create Job Wizard)

Change Version is the second step in the wizard. The table displays all updates you selected on the Update Details tab.

Figure 16: Change Version step

Column

Server Name

Category

Component

Meaning

Name of the server

The group to which the component belongs

Name of the component

Installed Version The version that is currently installed

New Version The version that is to replace the installed version

Change Version

Opens the Update Details dialog box, where you can select another version as the new version.

ServerView Update Management 93

5 User Interface

Enter Job Name step (Create Job Wizard)

Enter Job Name is the third step in the wizard. Here you assign a name to the job.

Figure 17: Enter Job Name step

Job Name

Unique name of the job

Default: JOB_<sequence number, starts at 1>

Description

Description of the job as a comment (optional)

The following fields are provided for information purposes only. You cannot change the values.

If you create a job for multiple servers simultaneously, it may be that the values of the parameters that should be displayed in the same field are different. In this case, the string "---" will be displayed in this field.

94 ServerView Update Management

5.1 Update Manager Main Window

Example:

For one server entered in the job a reboot is necessary after the update

(Reboot=yes), while for others no reboot is necessary (Reboot=no).

In this case the Reboot field will show the string "---".

If the parameters that should be displayed in the same field have the same value, this value will be displayed.

Server

Names of the server for which the updates are relevant

Severity

Importance of the updates

recommended An update is recommended mandatory An update is urgently required normal An update is not required

If you create a job for a single server, the highest severity weighting of an update contained in the job is displayed (mandatory > recommended > normal).

Reboot

Indicates, whether a reboot is required (Reboot=yes) after the job is executed or not (Reboot=no).

auto (for components of the blade systems group only)

The component itself decides whether a reboot is necessary or not.

If you create a job for a single server, a reboot is required if at least one update needs a reboot.

Download Size (MB)

Free memory required on the relevant server for installing the updates

Install Duration (Minutes)

Time needed for installing all updates on the relevant server

ServerView Update Management 95

5 User Interface

Enter TFTP step (Create Job Wizard)

Enter TFTP is the fourth step in the wizard. This step is only displayed if the update runs via TFTP server (for example, in the case of a management blade or a connection blade).

Figure 18: Enter TFTP step

The table shows a subset of the servers selected on the tab. For the servers displayed here, update will be done via the TFTP server.

Column

Server

TFTP Address

Temporary Flash

Address

Meaning

Name of the server

IP address of the TFTP server

Temporary IP address used for flashing the management blade (MMBS2 only)

Change TFTP Address

Click this button to change the IP address of the TFTP server for the selected server.

Change Flash Address

Click this button to change the temporary IP address used for flashing the management blade (MMBS2 only).

96 ServerView Update Management

5.1 Update Manager Main Window

Schedule Job step (Create Job Wizard)

Schedule Job is the last step in the wizard. Here you specify the time at which the job is to be executed.

Figure 19: Schedule Job step

Make sure that the management station and the server on which the job is to run are up and running at the time of execution.

Transfer Time

Start time for transferring the job to the server.

Immediate

Starts the transfer as soon as you click Finish to exit the wizard.

Later

Starts the transfer at the specified time.

Select date, hours and minutes.

ServerView Update Management 97

5 User Interface

Flash Time

Start time of the update phase on the servers.

Immediate after transfer

Starts the update immediately after the transfer.

Later

Starts the update phase at the specified time. If the transfer phase is not finished at the specified time, the update begins immediately after the end of the transfer phase.

Boot Time

Start time of the server reboot (only if Reboot = yes).

If all components contained in the job DO NOT require a reboot or reboot automatically (Reboot = Auto), the following options are not activated

(grayed out).

98 ServerView Update Management

5.1 Update Manager Main Window

Immediate after flash

The restart begins immediately after the end of the update phase.

Later

The restart begins at the specified time. If the update phase is not finished at the specified time, the restart begins immediately after the end of the update phase.

The Boot Time option has no influence on the booting time of management blades and connection blades. Management blades and connection blades are booted immediately after a flash.

ServerView Update Management 99

5 User Interface

5.1.5.5 Update Details dialog box

The Update Details dialog box provides additional information about the update you selected in the table on the Update Details tab. The parameters displayed in this dialog box cannot be changed except Available Versions.

If you selected a server of the group Unsupported Servers or

Unknown Servers, no data will be displayed in this dialog.

To open this dialog box, click Show Details on the Update Details tab.

Figure 20: Update Details dialog box

Server Name

Name of the server for which the update is relevant.

Category

The group to which the component belongs.

100 ServerView Update Management

5.1 Update Manager Main Window

Component

Name of the component.

Installed Version

The version that is currently installed.

New Version

The version that is to replace the installed version.

Compare Installed Version

Evaluates the version displayed in the New Version field:

Newest

Oldest

Newer

Equal

Older

The displayed version is newer than the installed version and, at the same time, is the newest version in the repository.

The displayed version is older than the installed version and, at the same time, is the oldest version in the repository.

The displayed version is newer than the installed version.

The displayed version is the same as the installed version.

The displayed version is older than the installed version.

Additional Version

Internal version of the update package used by the Download Manager.

A component in the repository will be replaced by an update version found on the web server.

Available Versions

All versions of the update available in the repository are displayed.

Download Size (MB)

Memory requirement of the update in megabytes.

ServerView Update Management 101

5 User Interface

Vendor Severity

Severity weighting of the update from the perspective of Fujitsu Technology Solutions.

recommended An update is recommended mandatory An update is urgently required normal An update is not required

Custom Severity

Severity weighting of the update from your perspective. You can use this parameter to override the Vendor Severity setting.

recommended An update is recommended mandatory An update is urgently required normal An update is not required

Install Duration (Minutes)

The installation duration of the update in minutes.

Applicable yes no

The component can be installed.

The component cannot be installed.

Reboot yes no auto

After the job is executed, the servers needs to be rebooted.

The servers do not needs to be rebooted.

(for components of the blade systems group only)

The component itself decides whether a reboot is necessary or not.

Applicable Text

Explanation of why the component cannot be installed.

102 ServerView Update Management

5.1 Update Manager Main Window

Dependencies

Displays dependencies that are to be noted in relation to the update.

Buttons

Show Relnotes

Opens the predefined browser, showing the latest release notes.

Show PSP Details

(PSP = PRIMERGY Support Package)

Displays information about the packages included in the selected update.

ServerView Update Management 103

5 User Interface

5.1.5.6 PSP Details dialog box

A PRIMERGY Support Package (PSP) is the basic element for installing and updating drivers and software products on your PRIMERGY server.

A PSP comprises several packages, each containing the different versions of the same driver or software product.

To open this dialog, click Show PSP Details in the Update Details dialog box or the Edit Update's Properties dialog box.

Figure 21: PSP Details dialog box

The PSP Details dialog box shows information on the individual packages and their dependencies on other components.

In the header you will see the name and version of the PSP.

104 ServerView Update Management

5.1 Update Manager Main Window

Below this are blocks of information on the individual packages and their dependencies on other components. The packages are numbered consecutively within the PSP and are each displayed with their version.

Dependencies

All the dependencies together make up the requirements that have to be fulfilled before a package can be installed.

For a package to be installed, ALL dependencies shown for it must be fulfilled.

For each PSP, the first package for which all dependencies are fulfilled is installed.

Support

For each component group, AT LEAST ONE of the specified components must be present on the target system.

All components linked by the OR operand belong to a component group.

The individual component groups are linked together by the AND operand.

Exclude

Exclusion procedure

NONE of the components marked with Exclude are allowed to be on the target system.

All excluded components are linked by the OR operand.

Required

ALL the components marked with Required must be on the target system.

All required components are linked by the AND operand.

ServerView Update Management 105

5 User Interface

5.1.5.7 Copy Job Wizard

You can use this wizard to copy a job to any server in the domain. The wizard comprises several dialog boxes to guide you through the individual steps. All required steps are displayed in the tree structure on the left.

To open the wizard, select the job you want to copy on the Job Details tab and click Copy Job.

Choose Server step (Copy Job Wizard)

Choose Server is the first step in the wizard. Here you select the servers to which the job is to be copied.

Figure 22: Choose Server step

Possible Servers

A list of available servers to which the job can be copied.

Destination Server

The selected servers to which the job is to be copied.

106 ServerView Update Management

5.1 Update Manager Main Window

>>

Copies all servers from the Possible Server list to the Destination

Server list.

>

Copies the servers selected from the Possible Server list to the Des-

tination Server list.

<

Moves the servers selected from the Destination Server list back to the

Possible Server list.

<<

Moves all servers from the Destination Server list back to the Possible

Server list.

ServerView Update Management 107

5 User Interface

LogOn step (Copy Job Wizard)

LogOn is the second step in the wizard. Here you log on to all servers that require user authentication (AgentAccess = restricted or not certified).

Figure 23: LogOn step

The table displays all servers you selected in the Choose Server step.

If you have selected servers with an access status other than

restricted or not certified, Update Manager ignores attempts to log on to these servers.

Column

Server

Manageable

Meaning

Name of the server

Availability of the server

108 ServerView Update Management

5.1 Update Manager Main Window

Column Meaning

Agent Access Access status of the update agent on the server granted restricted unrestricted trusted certified not certified

Logon to the server has already been successfully completed. You have access to the server.

Access to the server is currently restricted. Log on must be performed with the appropriate user ID and password on the server.

Logon is not required to access the server.

Since the server was unavailable at the time the logon was attempted, the logon data was saved under the assumption that it was correct.

A valid certificate is installed.

The managed server is ready for single sign-on.

No valid certificate is installed.

The managed server is not ready for single sign-on.

User Authentication

Login user ID and password for access control.

This parameters are only required if the ServerView update agent on the managed node is configured with AccountCheck.

If the server is to be updated via a TFTP server, enter user ID and password for access to the controller (MMB, switch blade, iRMC)

ServerView Update Management 109

5 User Interface check and set Password

Checks the logon data and sets the access rights on the selected servers

(if Manageable = yes). The password is valid for the current session.

If the server is unavailable, the logon data is stored under the assumption that it is correct (if Manageable = no).

Remove Server from List

Removes the selected server from the displayed list.

110 ServerView Update Management

5.1 Update Manager Main Window

Enter Job Name step (Copy Job Wizard)

Enter Job Name is the third step in the wizard. Here you assign a name to the job.

Figure 24: Enter Job Name step

Job Name

Unique name of the job

Default: JOB_<sequence number, starts at 1>

Description

Description of the job as a comment (optional)

The following fields are provided for information purposes only. You cannot change the values.

If you create a job for multiple servers simultaneously, it may be that the values of the parameters that should be displayed in the same field are different. In this case, the string "---" will be displayed in this field.

ServerView Update Management 111

5 User Interface

Example:

For one server entered in the job a reboot is necessary after the update

(Reboot=yes), while for others no reboot is necessary (Reboot=no).

In this case the Reboot field will show the string "---".

If the parameters that should be displayed in the same field have the same value, this value will be displayed.

Server

Names of the server for which the updates are relevant

Severity

Importance of the updates

recommended An update is recommended mandatory An update is urgently required normal An update is not required

If you create a job for a single server, the highest severity weighting of an update contained in the job is displayed (mandatory > recommended > normal).

Reboot

Indicates, whether a reboot is required (Reboot=yes) after the job is executed or not (Reboot=no).

auto (for components of the blade systems group only)

The component itself decides whether a reboot is necessary or not.

If you create a job for a single server, a reboot is required if at least one update needs a reboot.

Download Size (MB)

Free memory required on the relevant server for installing the updates

Install Duration (Minutes)

Time needed for installing all updates on the relevant server

112 ServerView Update Management

5.1 Update Manager Main Window

Enter TFTP step (Copy Job Wizard)

Enter TFTP is the fourth step in the wizard. Here you enter the address of the TFTP server if no update agent is installed on your server. This step is not displayed if the update agent is installed on the relevant servers.

Figure 25: Enter TFTP step

The table shows a subset of the servers selected on the tab.

Column

Server

TFTP Address

Temporary Flash

Address

Meaning

Name of the server

IP address of the TFTP server

Temporary IP address used for flashing the management blade (MMBS2 only)

Change TFTP Address

Click this button to change the IP address of the TFTP server for the selected server.

Change Flash Address

Click this button to change the temporary IP address used for flashing the management blade (MMBS2 only).

ServerView Update Management 113

5 User Interface

Schedule Job step (Copy Job Wizard)

Schedule Job is the last step in the wizard. Here you specify the time at which the job is to be executed.

Figure 26: Schedule Job step

Make sure that the management station and the server on which the job is to run are up and running at the time of execution.

Transfer Time

Start time for transferring the job to the server.

Immediate

Starts the transfer as soon as you click Finish to exit the wizard.

Later

Starts the transfer at the specified time.

Select date, hours and minutes.

114 ServerView Update Management

5.1 Update Manager Main Window

Flash Time

Start time of the update phase on the servers.

Immediate after transfer

Starts the update immediately after the transfer.

Later

Starts the update phase at the specified time. If the transfer phase is not finished at the specified time, the update begins immediately after the end of the transfer phase.

Boot Time

Start time of the server reboot (only if Reboot = yes).

If all components contained in the job DO NOT require a reboot or reboot automatically (Reboot = Auto), the following options are not activated

(grayed out).

ServerView Update Management 115

5 User Interface

Immediate after flash

The restart begins immediately after the end of the update phase.

Later

The restart begins at the specified time. If the update phase is not finished at the specified time, the restart begins immediately after the end of the update phase.

The Boot Time option has no influence on the booting time of management blades and connection blades. Management blades and connection blades are booted immediately after a flash.

116 ServerView Update Management

5.1 Update Manager Main Window

5.1.5.8 Job Details dialog box

The Job Details dialog box provides a clear and detailed overview of information relating to the job you selected on the Job Details tab.

If you selected a server of the group Unsupported Servers or

Unknown Servers, no data will be displayed in this dialog.

To open this dialog box, click Show Details on the Job Details tab.

Figure 27: Job Details dialog box

You may only change the Released parameter in this dialog box. No other parameters can be changed.

Job Name

Name of the selected job

ServerView Update Management 117

5 User Interface

Severity

Cumulated severity weighting of the updates contained in the job. The highest severity weighting of an update is displayed (mandatory > recommended > normal).

recommended An update is recommended mandatory An update is urgently required normal An update is not required

Transfer Time

Start time for transferring the update from the management station to the

PRIMERGY servers

Server

Name of the server

Reboot

This setting indicates whether at least one of the updated servers must be restarted (Reboot = yes), or alternatively, none of the servers need to be restarted (Reboot = no) after the job is executed.

auto (for components of the blade systems group only)

The component itself decides whether a reboot is necessary or not.

Exec Time

Start time for the update phase

Job Status

Current job status waiting transferring transferred

The job is waiting to be executed (this is the status before the data transfer begins).

The job is currently being transferred.

The job has been successfully transferred and is now waiting for the start of the update procedure.

118 ServerView Update Management

5.1 Update Manager Main Window flashing flashed rescanning rebooting done error

The job is currently in the update phase.

The update has been performed successfully on the server.

The inventory of the server is being redetermined.

The server is currently rebooting.

All components have been updated and the job is now completed.

Possible reasons: l

The update of at least one component failed.

l

Check-Job was not successful l

Cleanup-Job was not successful l

Status could not be retrieved

manager abort The management station was restarted while the job was being executed, see

"Notes on management stations" on page 20

.

Install Duration (Minutes)

Duration of the installation in minutes

Boot Time

Start time for the boot process (if Reboot = yes)

Download Size (MB)

Memory required for the update in megabytes

Released

This setting specifies whether the job is released (yes) or not released

(no) for execution on other PRIMERGY servers.

TFTP Adress

IP address of the TFTP server

ServerView Update Management 119

5 User Interface

Description

Description of the job (comment)

Return Text

In the event of an error, this field contains the error message of the error that occurred.

The error messages are described in section

"Error messages in the

Update Manager" on page 261 .

Category/Component/Old Version/New Version/Status

Table containing version and status information about the updates contained in the job

Buttons

Show Logfile

Displays the log file of the selected job

This button is only activated for jobs that are completed or in process.

5.1.5.9 Edit Job dialog box

In the Edit Job dialog box you can change the properties Job Name,

Released and Description for the job you selected on the Job Details tab.

Transfer Time, Flash Time and Boot Time only can be changed, if the Job

Status = Waiting.

To open this dialog box, click Edit Job on the Job Details tab.

120 ServerView Update Management

5.1 Update Manager Main Window

Figure 28: Edit Job dialog box

Job Name

Name of the selected job.

Released

This setting specifies whether the job is released (yes) or not released

(no) for execution on other PRIMERGY servers.

Description

Description of the job (comment).

ServerView Update Management 121

5 User Interface

Transfer Time

Start time for transferring the job to the server.

Immediate

Starts the transfer as soon as you click Finish to exit the wizard.

Later

Starts the transfer at the specified time.

Select date, hours and minutes.

Flash Time

Start time of the update phase on the servers.

Immediate after transfer

Starts the update immediately after the transfer.

Later

Starts the update phase at the specified time. If the transfer phase is not finished at the specified time, the update begins immediately after the end of the transfer phase.

Boot Time

Start time of the server reboot (only if Reboot = yes).

If all components contained in the job DO NOT require a reboot or reboot automatically (Reboot = Auto), the following options are not activated

(grayed out).

122 ServerView Update Management

5.1 Update Manager Main Window

Immediate after flash

The restart begins immediately after the end of the update phase.

Later

The restart begins at the specified time. If the update phase is not finished at the specified time, the restart begins immediately after the end of the update phase.

The Boot Time option has no influence on the booting time of management blades and connection blades. Management blades and connection blades are booted immediately after a flash.

5.1.5.10 Change TFTP Address dialog box

In the Change TFTP Address dialog box you enter the IP address of the

TFTP server that you want to use.

Figure 29: Change TFTP Address dialog box

IPv4

IP address in the format of Internet Protocol Version 4.

IPv6

IP address in the format of Internet Protocol Version 6.

ServerView Update Management 123

5 User Interface

Test Connectivity

Tests if a connection can be established to the specified IP address using the "ping" function.

5.1.5.11 Change Flash Address dialog box

In the Change Flash Address dialog box, you enter a free IP address that you want to use for flashing the management blade (MMB S2 only).

Figure 30: Change Flash Address dialog box

IPv4

IP address in the format of Internet Protocol Version 4.

IPv6

IP address in the format of Internet Protocol Version 6.

Test Availability

Tests if the specified IP address is available.

124 ServerView Update Management

5.2 Repository Manager Main Window

5.2

Repository Manager Main Window

Repository Manager allows you to administer the repository.

Figure 31: Repository Manager Main Window

The main window of the Repository Manager displays the current contents of the repository and contains the following elements (from top to bottom): l the ServerView Suite header l the ServerView Suite menu bars l the work area, with a tree structure on the left and various tabs on the right

ServerView Update Management 125

5 User Interface

5.2.1

The tree structure

Figure 32: Repository Manager tree structure

The tree structure, which is on the left, shows the updates that are available in the Repository Manager. In the tree structure, you select which data you want to display in the table on the Updates tab and the Collections tab.

The tree structure is shown with the following groups, in which the relevant components are listed:

All Updates

All updates in the repository.

New Updates

New updates in the repository that have been downloaded by the Download Manager or that have been imported via the import function. These updates are automatically deleted from the New Updates group after a period of two weeks.

If the repository is reloaded using the Reload button on the Updates tab, the elapsed time will be set to 0 and the time counter starts again.

126 ServerView Update Management

5.2 Repository Manager Main Window

Updates By Severity

All updates that are recommended (recommended) or urgently required

(mandatory).

Released Updates

Updates that are explicitly released by the user. This group only appears if there is at least one "released" update.

User Collections

Customized groups, which you can create and manage on the Col-

lections tab.

This node does not appear if you have not yet defined any customized groups.

ServerView Update Management 127

5 User Interface

5.2.2

Updates tab

All entries belonging to the group you selected in the tree structure are displayed in the table on the Updates tab.

Figure 33: Updates tab

128 ServerView Update Management

5.2 Repository Manager Main Window

In the table, a context menu is available. To open the context menu, right-click an entry in the table.

The columns in the table have the following meanings:

Column

Update status

(icon)

Meaning

Urgency of the update

An update is recommended.

An update is urgently required.

An update is not required.

Category

Component

Version

OS

Severity

Name of the component group

Opens the Filtering for <column> dialog box, where you specify which rows are to be displayed in the table.

Name of the component

Version of the update

Operating system variant

Urgency of the update

recommended An update is recommended.

mandatory An update is urgently required.

normal An update is not required.

Released Shows whether the update is released (yes) for execution on other PRIMERGY servers or not (no).

Install Duration The installation duration of the update in minutes

ServerView Update Management 129

5 User Interface

Column Meaning

Reboot Required Shows whether server reboot is either required (yes) or not required (no) after the update.

auto (for components of the blade systems group only)

The component itself decides whether a reboot is necessary or not.

Comments Comments about the update

Buttons

Edit

Opens the Edit Update dialog box in which you can edit the Custom

Severity, Released and Comment parameters of an update.

Import

Opens the Import Repository Components dialog box,in which you can update your repository on the management station by importing new components from the ServerView Update DVD or another existing repository.

All update components found in the specified directory (including all subdirectories) will be added to the existing repository on the management station if they are newer.

If you want to replace your complete repository, do this using the

Configuration Wizard.

Export

Opens the Export Repository Components dialog box, in which you can select components from your repository for exporting them to a directory of your choice.

Delete

Opens the Delete Repository Components dialog box, in which you can select components from your repository that you no longer need and that can be deleted.

130 ServerView Update Management

5.2 Repository Manager Main Window

Deleting components is only possible if the current repository is located on a local HDD partition of your computer or on an external USB storage device.

Components which are used in an update job cannot be deleted. You have to remove them from the update job at first.

Reload

Reloads the repository and updates the database entries. A recollection of the inventory data for all servers is executed in the background.

If the repository is reloaded, the elapsed time for the updates in the New

Updates group in the tree structure will be set to 0 and the time counter starts again.

The repository only needs be reloaded if an update was added manually.

Additional function in the context menu

Release

Releases the selected updates for execution on other PRIMERGY servers (for example, after they have been processed without errors on a test host).

ServerView Update Management 131

5 User Interface

5.2.3

Collections tab

The functions provided on the Collections tab allow you to create and manage customized update groups. The groups you create here are displayed under User Collections in the tree structure.

If you have not yet created any groups, the tree structure will not contain a node for User Collections and the tab is also blank.

Figure 34: Collections tab

In the table, a context menu is available. To open the context menu, right-click an entry in the table.

The columns in the table have the following meanings:

132 ServerView Update Management

5.2 Repository Manager Main Window

Column

Name

Meaning

Name and cumulated update status of the collection

Collection contains at least one component for which an update is recommended.

Collection contains at least one component for which an update is urgently required.

Collection contains no components that needs updating.

Name and update status of the component

An update is recommended.

An update is urgently required.

An update is not required.

Version

OS

Severity

Version of the update

Operating system variant

Urgency of the update

recommended An update is recommended.

mandatory An update is urgently required.

normal An update is not required.

Released Shows whether the update is released (yes) for execution on other PRIMERGY servers or not (no).

Install Duration The installation duration of the update in minutes

ServerView Update Management 133

5 User Interface

Column Meaning

Reboot Required Indicates whether server reboot is either required (yes) or not required (no) after the update.

auto (for components of the blade systems group only)

The component itself decides whether a reboot is necessary or not.

Description Description of the component

Buttons

Create

Opens the Create Collection dialog box, where you can create a customized group.

Delete

Deletes the groups you selected on the tab.

Edit

Opens the Edit Collection dialog box, where you can edit the settings for the selected group.

Release

Releases the selected groups for future use.

134 ServerView Update Management

5.2 Repository Manager Main Window

5.2.4

Dialog boxes

The Repository Manager provides the following dialog boxes: l

Edit Update's Properties dialog box o Show Release Notes dialog box o Show PSP Details dialog box l

Import Repository Components dialog box o Import Repository Components - Results dialog box l

Export Repository Components dialog box o Export Repository Components - Results dialog box l

Delete Repository Components - Results dialog box o Delete Repository Components - Results dialog box l

Create Collection dialog box l

Edit Collection dialog box

5.2.4.1 Edit Update's Properties dialog box

The Edit Update's Properties dialog box provides a clear and detailed overview of information relating to the update you selected on the Updates tab.

Almost none of the parameters in this dialog box can be changed. The following properties of an update can be changed: l

Released l

Custom Severity l

Comment

To open this dialog box, click Edit on the Updates tab.

ServerView Update Management 135

5 User Interface

Figure 35: Edit Update's Properties dialog box

136 ServerView Update Management

5.2 Repository Manager Main Window

Category

The group to which the component belongs.

Component

Name of the component.

Version

Update version.

Operating System

The relevant operating system.

Version Details

Details of the update version.

Reboot Required

Indicates whether server reboot is either required (yes) or not required (no) after the update.

auto (for components of the blade systems group only)

The component itself decides whether a reboot is necessary or not.

Download Size (MB)

Memory requirement of the update in megabytes.

Install Duration (min)

The installation duration of the update in minutes.

Download Time

Time at which the updates are transferred from the web server to the repository.

ServerView Update Management 137

5 User Interface

Vendor Severity

Severity weighting of the update from the perspective of Fujitsu Technology Solutions.

recommended An update is recommended mandatory An update is urgently required normal An update is not required

Released

Releases the selected updates (yes) for execution on other PRIMERGY servers ( for example, after they have been processed without errors on a test host) or not (no).

Custom Severity

Severity weighting of the update from your perspective. You can use this parameter to override the Vendor Severity setting.

recommended An update is recommended mandatory An update is urgently required normal An update is not required

Comment

Description of the update (comment).

Dependencies

Dependencies that are to be noted in relation to the update.

Buttons

Show Relnotes

Opens the predefined browser, showing the latest release notes.

138 ServerView Update Management

5.2 Repository Manager Main Window

Show PSP Details

(PSP = PRIMERGY Support Package)

Displays informations about the packages included in the selected update.

5.2.4.2 Import Repository Components dialog box

To open this dialog box, click Import on the Updates tab.

If you want to replace your complete repository, do this using the Configuration Wizard.

Figure 36: Import Repository dialog box

ServerView Update Management 139

5 User Interface

Importing components is only possible if the current repository is located on a local HDD partition of your computer or on an external USB storage device.

You can update your repository on the management station by importing new components from a local or remote repository, e.g. the ServerView Update

DVD or another existing repository, to the current repository. In the Import

Path field, specify the directory that contains the update components to be imported and click Check for Imports.

After the process has finished, all components found in the specified directory (including all subdirectories) are shown in the Source list on the left. If you only want newer updates to be displayed, enable the Filter only newer

updates option.

Copy all desired components from the Source list on the left to the Des-

tination list on the right and click OK.

All selected update components will be added to the existing repository on the management station if they did not exist before. If an older version of a component exists the newer version is additionally added to the local repository.

While the import to the repository is running, a progress bar is displayed.

If you abort the process by clicking Cancel, the import will be stopped and the result dialog box will show all components which are already imported.

Type of Drive local

The import path is located on the local management station.

remote

The import path is located somewhere in the network. This option is only available for Windows management stations.

If you enable this option, you have to enter User and Password.

140 ServerView Update Management

5.2 Repository Manager Main Window

Import Path

Absolute path of the directory to be imported. This directory may be the root of an existing repository or any subdirectory.

The Browse button is only enabled, if you started the ServerView

Operations Manager on the management station directly.

Check for Imports

Checks the directory defined in the Import Path field for available components. All found components are displayed in the Source list on the left.

Filter only newer Updates

If you enable this option, only newer updates are shown in the Source list on the left.

Source

This list shows all /all newer components available for import.

Components can be imported from a local or a remote repository.

Destination

This list shows all components selected from the Source list.

The selected components will be imported into the current repository.

ServerView Update Management 141

5 User Interface

5.2.4.3 Import Repository Components - Results dialog box

Figure 37: Import Repository Components - Results

This dialog shows the result of importing components into the current repository.

142 ServerView Update Management

Category

Name of the component group.

Component

Name of the component.

Version

Version of the update.

Result ok

Component has been imported.

error

Import failed.

ErrorMessage

Explanation why the import failed.

5.2 Repository Manager Main Window

ServerView Update Management 143

5 User Interface

5.2.4.4 Export Repository Components dialog box

To open this dialog box, click Export on the Updates tab.

Figure 38: Export Repository Components dialog

Exporting components is only possible if the current repository and the target directory are located on a local HDD partition of your computer or on an external USB storage device.

In the Source list on the left, all components of the current repository are displayed.

144 ServerView Update Management

5.2 Repository Manager Main Window

First, select the absolute path of the directory where the desired components should be exported to. This directory may be located on a local HDD partition of your computer or on an external USB storage device.

Then copy the components you want to be exported from the Source list to the Destination list.

To export the selected components, click OK.

While the components are exported, a progress bar is displayed.

If you abort the process by clicking Cancel, the export will be stopped and the result dialog box will show all components which are already exported.

Export Path

Absolute path of the directory where the selected components should be exported to.

For selecting the desired directory, use the Browse... button.

Source

This list shows all components contained in the current repository.

Destination

This list shows all components selected from the Source list.

ServerView Update Management 145

5 User Interface

5.2.4.5 Export Repository Components - Results dialog box

Figure 39: Export Repository Components - Results dialog

This dialog shows the result of exporting components from the current repository to the selected export directory.

146 ServerView Update Management

Category

Name of the component group.

Component

Name of the component.

Version

Version of the update.

Result ok

Component has been exported.

error

Export failed.

ErrorMessage

Explanation why the export failed.

5.2 Repository Manager Main Window

ServerView Update Management 147

5 User Interface

5.2.4.6 Delete Repository Components dialog box

To open this dialog box, click Delete on the Updates tab.

Figure 40: Delete Repository Components dialog

Deleting components is only possible if the current repository is located on a local HDD partition of your computer or on an external USB storage device.

Components which are used in an update job cannot be deleted. You have to remove them from the update job at first.

148 ServerView Update Management

5.2 Repository Manager Main Window

In the Source list on the left, all components of the current repository are displayed.

Select the components which should be deleted in the Source list and copy them to the Destination list.

To delete the selected components, click OK.

While the selected components are deleted, a progress bar is displayed.

If you abort the process by clicking Cancel, the delete process will be stopped and the result dialog box will show all components which are already deleted.

Repository Path

Displays the absolute path where the current repository is located.

Source

This list shows all components contained in the current repository.

Destination

This list shows all components selected from the Source list.

ServerView Update Management 149

5 User Interface

5.2.4.7 Delete Repository Components - Results dialog box

Figure 41: Delete Repository Components - Results dialog

This dialog shows the result of deleting components from the current repository.

150 ServerView Update Management

5.2 Repository Manager Main Window

Category

Name of the component group.

Component

Name of the component.

Version

Version of the update.

Result ok

Component has been deleted.

error

Delete process failed.

in use

The component was not deleted, because it is used in an update job.

ErrorMessage

Explanation why the delete process failed.

ServerView Update Management 151

5 User Interface

5.2.4.8 PSP Details dialog box

A PRIMERGY Support Package (PSP) is the basic element for installing and updating drivers and software products on your PRIMERGY server.

A PSP comprises several packages, each containing the different versions of the same driver or software product.

To open this dialog, click Show PSP Details in the Update Details dialog box or the Edit Update's Properties dialog box.

Figure 42: PSP Details dialog box

The PSP Details dialog box shows information on the individual packages and their dependencies on other components.

In the header you will see the name and version of the PSP.

152 ServerView Update Management

5.2 Repository Manager Main Window

Below this are blocks of information on the individual packages and their dependencies on other components. The packages are numbered consecutively within the PSP and are each displayed with their version.

Dependencies

All the dependencies together make up the requirements that have to be fulfilled before a package can be installed.

For a package to be installed, ALL dependencies shown for it must be fulfilled.

For each PSP, the first package for which all dependencies are fulfilled is installed.

Support

For each component group, AT LEAST ONE of the specified components must be present on the target system.

All components linked by the OR operand belong to a component group.

The individual component groups are linked together by the AND operand.

Exclude

Exclusion procedure

NONE of the components marked with Exclude are allowed to be on the target system.

All excluded components are linked by the OR operand.

Required

ALL the components marked with Required must be on the target system.

All required components are linked by the AND operand.

ServerView Update Management 153

5 User Interface

5.2.4.9 Create Collection dialog box

In the Create Collection dialog box, you can create customized update groups, which are displayed in the Update Manager on the Update Details tab under User Collections.

To open this dialog box, click Create on the Collections tab.

Figure 43: Create Collection dialog box

Name

Name of the customized update group.

Description

Description of the customized update group (comment).

154 ServerView Update Management

5.2 Repository Manager Main Window

Source

The component groups that are available for selection.

Destination

>>

The component groups that were copied to the user-defined group.

Transfers all component groups to the user-defined group.

>

Transfers the selected component groups to the user-defined group.

<

<<

Deletes the selected component groups from the user-defined group.

Deletes all component groups from the user-defined group.

Undo

Undoes the action last performed in the dialog box.

ServerView Update Management 155

5 User Interface

5.2.4.10 Edit Collection dialog box

You can edit a selected customized update group in the Edit Collection dialog box.

To open this dialog box, click Edit on the Collections tab.

Figure 44: Edit Collection dialog box

Name

Name of the customized update group (cannot be changed)

Description

Description of the customized update group (comment).

Source

The component groups that are available for selection.

156 ServerView Update Management

5.2 Repository Manager Main Window

Destination

The component groups that were copied to the user-defined group.

>>

Transfers all component groups to the user-defined group.

>

Transfers the selected component groups to the user-defined group.

<

<<

Deletes the selected component groups from the user-defined group.

Deletes all component groups from the user-defined group.

Undo

Undoes the action last performed in the dialog box.

ServerView Update Management 157

5 User Interface

5.3

Download Manager Main Window

Use the Download Manager to define download tasks, configure when and how often these are to be executed, and activate the download task by assigning selected servers to it. You can also display information on download tasks already executed.

The Download Service uses the download tasks defined to search for updates for the assigned servers, loads the updates to the default repository, and checks whether updates need to be performed on the servers for which the download task is activated.

Figure 45: Download Manager main window

158 ServerView Update Management

5.3 Download Manager Main Window

The main window of the Download Manager contains the following sections, from top to bottom: l the ServerView Suite header l the ServerView Suite menu bars l the work area, with a tree structure on the left and various tabs on the right

5.3.1

The tree structure

Figure 46: Download Manager tree structure

The area on the left of the Download Manager contains a tree structure showing all servers in a domain and the customized groups.

ServerView Update Management 159

5 User Interface

All Servers

Shows the servers in a domain which are supported by the current Update

Manager.

Groups

Shows the groups defined by the user.

Server icons

The icon in front of the server in the tree structure indicates the status of the server:

No updates or updates with Severity = normal are required.

Updates with Severity = recommended are required.

Updates with Severity = mandatory are required.

Undefined, no existing inventory available.

5.3.2

Task Management Tab

The Task Management tab shows all currently available download tasks.

You can create new download tasks, or change, delete, activate or deactivate existing download tasks.

When creating a download task, you define when, and how often the download task is to be executed, and how many of the related log files are to be saved. In order to use a download task, use the Activate function to then assign servers to it for which searches for updates are to be carried out later.

160 ServerView Update Management

5.3 Download Manager Main Window

Figure 47: Task Management tab

In the table, a context menu is available. To open the context menu, right-click an entry in the table.

Active

Shows whether or not at least one server is assigned to the download task.

Time Unit

Shows a summary of the download schedule entered for the download task.

Servers

Shows the names of the servers assigned to the download task.

ServerView Update Management 161

5 User Interface

Buttons

Add ...

Starts a dialog box in which you specify a new download task.

Edit ...

Starts a dialog box in which you can change the download task selected in the table.

Delete

Deletes the download task selected in the table.

However, you can only delete a download task if NO servers are assigned to it.

Activate ...

Starts a dialog box in which you can assign one or more servers to the download task selected in the table.

Deactivate

Stops the download tasks selected in the table. All servers are removed from the download task.

162 ServerView Update Management

5.3 Download Manager Main Window

5.3.3

Scheduled Tasks Tab

This tab contains an overview of the servers available in a domain. The

Schedule column shows whether the server was assigned to a download task, and if so, to which one.

By selecting certain servers or groups in the tree structure (left), you can restrict the number of servers shown in this tab.

Figure 48: Scheduled Tasks tab

In the table, a context menu is available. To open the context menu, right-click an entry in the table.

The columns in the table have the following meanings:

ServerView Update Management 163

5 User Interface

Server icons

The icon in front of the server name indicates the status of the server.

No updates or updates with Severity = normal are required.

Updates with Severity = recommended are required.

Updates with Severity = mandatory are required.

Undefined, no existing inventory available.

Name

Shows the name of the server.

Group

Shows the name of the server group.

Schedule

Shows a summary of download schedule for the download task.

Status icons

This icon indicates the status of the download task.

Undefined - no download task was started

OK - last download task performed was successful

Error - last download task performed failed

Processing - a check or download is running

Last Result

Shows when a search for updates was last performed successfully.

Next Run

Shows when a search for updates will next be performed.

164 ServerView Update Management

5.3 Download Manager Main Window

Buttons

Once Immediately

Click this button to start a search for updates for the servers selected in the table.

Deactivate

Removes the server selected in the table from the assigned download task.

5.3.4

Log Files Tab

This tab contains information on download tasks already completed.

Figure 49: Log Files tab

In the table, a context menu is available. To open the context menu, right-click an entry in the table.

The columns in the table have the following meanings:

ServerView Update Management 165

5 User Interface

Status icon

OK - Last download task performed was successful

Error - last download task performed failed

Time

Shows when the download task was started.

Name

Shows the name of the server.

Result

Shows when the log file was created.

Group

Shows the name of the server group for group tasks.

Schedule

Shows the description of the download task belonging to this entry.

The description changes, if the properties of the download task are changed or the download task is deleted.

Error

Shows what caused a download task to fail in the event of an error.

The error messages are described in section

"Error messages in the

Download Manager" on page 266 .

166 ServerView Update Management

5.3 Download Manager Main Window

Buttons

View

Shows the log file of the download task selected in the table.

Delete

Deletes the log file of the download task selected in the table.

Delete All

Deletes all log files.

This button remains inactive as long as a check or download is running.

ServerView Update Management 167

5 User Interface

5.3.5

Dialog boxes

The Download Manager provides the following dialog boxes.

l

Add Download Server Tasks dialog box l

Edit Download Server Task Settings dialog box l

Activate Download Server Tasks dialog box

5.3.5.1 Add Download Server Tasks dialog box

In this dialog box, you specify when and how often a download task will be executed, and whether the related log files are to be saved.

You open the dialog box on the Task Management tab by clicking Add....

Figure 50: Add Download Server Tasks dialog box

168 ServerView Update Management

5.3 Download Manager Main Window

Select Date and Time to Start

You specify when the download task is to be executed here.

now later

Starts the download task as soon as it has been activated.

Starts the download task at the specified time.

Select the date, hour, and minutes.

Frequency

You specify how often the download task is to be executed here.

Once

Hourly

Execute download task once

Execute download task hourly

(This option is currently not available.)

Daily

Weekly

Execute download task daily

Execute download task weekly

Monthly Execute download task monthly

Journalize Log Data

Here, you specify whether log files are to be saved, and if so, how many.

Last

None

All

Only save the last log files

You can specify the number of last log files.

Do not save any log files

(This option is currently not available.)

Save all log files

Summary

A summary of the values specified is displayed in this output field.

ServerView Update Management 169

5 User Interface

Buttons

Create

Saves the values entered for the download task and closes the dialog box.

Close

Discards the values entered and closes the dialog box.

Help

Opens the help for the current dialog box.

170 ServerView Update Management

5.3 Download Manager Main Window

5.3.5.2 Edit Download Server Tasks dialog box

In this dialog box, you change the setting that specifies when a download task is executed and how many of the related log files are to be saved.

To open the dialog box for a previously selected download task, click Edit ... on the Task Management tab.

Figure 51: Edit Download Server Tasks dialog box

Select Date and Time to Start

You specify when the download task is to be executed here.

now later

Starts the download task as soon as it has been activated.

Starts the download task at the specified time.

Select the date, hour, and minutes.

ServerView Update Management 171

5 User Interface

Frequency

You can see how often the download task is to be executed here.

The value can only be changed as long as no server is assigned to this download task.

Once

Hourly

Execute download task once

Execute download task hourly

(This option is currently not available.)

Daily

Weekly

Execute download task daily

Execute download task weekly

Monthly Execute download task monthly

Journalize Log Data

Here, you specify whether log files are to be saved, and if so, how many.

Last

None

All

Only save the last log files

You can specify the number of last log files.

Do not save any log files

(This option is currently not available.)

Save all log files

Summary

A summary of the values specified is displayed in this output field.

Buttons

Create

Saves the values entered for the download task and closes the dialog box.

Close

Discards the values entered and closes the dialog box.

172 ServerView Update Management

5.3 Download Manager Main Window

5.3.5.3 Activate Download Server Tasks dialog box

In this dialog box, you assign one or more servers to a download task.

To open the dialog box for a previously selected download task, click Acti-

vate ... on the Task Management tab.

Figure 52: Activate Download Server Tasks dialog box

The output field at the top of the window shows a summary of the values specified for the download task.

The area on the left of the window contains a tree structure showing all available servers in the domain and the customized groups. Select the servers you want to assign to the download task here.

The area on the right of the window contains a list of servers assigned to the download task.

ServerView Update Management 173

5 User Interface

Buttons

>>

Copies all servers from the list on the left to the list of servers assigned to the download task on the right.

>

Copies the servers selected in the list on the left to the list of servers assigned to the download task on the right.

<

Removes the entries selected in the list on the right from the list of servers assigned to the download task.

<<

Removes all entries from the list of servers assigned to the download task from the right-hand side of the window.

Undo

Undoes the action last performed in the dialog box.

Assign

Saves the current setting and closes the dialog box.

Close

Discards all changes and closes the dialog box.

Help

Opens the help for the current dialog box.

174 ServerView Update Management

5.4 Configuration Main Window

5.4

Configuration Main Window

The main window contains the following elements (from top to bottom): l the ServerView Suite header l the ServerView Suite menu bars l the work area with the tabs

The Mail Settings and the Download Settings tab are disabled

(grayed out) if you have set a remote repository for updating your software.

You only need these tabs if you want to update your local repository via the Download Service (Download Manager).

ServerView Update Management 175

5 User Interface

5.4.1

General Settings Tab

The configuration parameters listed below are displayed on the General Set-

tings tab.

To modify the properties click Change Configuration.

Figure 53: General Settings tab

Repository State

State of the repository ok

File system repository and database table

UpdateRepository are complete incomplete

Copy to file system failed.

176 ServerView Update Management

5.4 Configuration Main Window

Repository Location

Absolute path of the repository.

Default TFTP Address

IP address of a TFTP server (for components that are updated via TFTP server, e.g. management blades or connection blades).

Default Boot Duration

The length of time that Update Manager waits for an updated server to restart after reboot. The time you enter here is added to the length of time the server is unavailable during the update. If the duration is exceeded, the job is set to status error.

For Windows management station only:

If the repository is located on another system in the network instead of the local management station:

User

User name on the system in the network where the repository is located.

Password

Password on the system in the network where the repository is located.

Buttons

Change Configuration

Starts the Configuration wizard.

ServerView Update Management 177

5 User Interface

5.4.2

Mail Settings Tab

The Mail Settings tab is disabled (grayed out) if you have set a remote repository for updating your software.

You only need this tab if you want to update your local repository via the Download Service (Download Manager).

The Mail Settings tab displays the mail settings for the persons who are to be informed about new updates downloaded via the Download Service.

To modify the properties click Change Configuration.

Figure 54: Mail Settings tab

178 ServerView Update Management

5.4 Configuration Main Window

Mail To

Recipient address(es) of the e-mail

If more than one address is entered, they are separated by commas.

CC

Additional recipient addresses

If more than one address is entered, they are separated by commas.

From

E-mail address of the sender

SMTP Server

IP address of the SMTP server

Port

Port number of the SMTP server

User

User ID for logging on to the mail server

Password

Password for logging on to the mail server

Buttons

Change Configuration

Starts the Configuration wizard.

ServerView Update Management 179

5 User Interface

5.4.3

Download Settings Tab

The Download Settings tab is disabled (grayed out) if you have set a remote repository for updating your software.

You only need this tab if you want to update your local repository via the Download Service (Download Manager).

The Download Settings tab shows the details of the connection to the web server of Fujitsu Technology Solutions via which the Download Service is to download new updates.

To modify the settings displayed click Change Configuration.

Figure 55: Download Settings tab

180 ServerView Update Management

5.4 Configuration Main Window

Download Web Address

URL of the web server use by the Download Service. Default is the web server of Fujitsu Technology Solutions.

Protocol used for transferring data from web server

Type of the protocol used

The comment displays the current kind of connection.

One of the following messages is shown: l

Download Manager uses predefined proxy settings defined on

Management Station l

Download Manager uses proxy server defined in Configuration

Wizard l

No proxy server is currently set for Download Manager

Example for "How to find predefined Proxy Settings on a Windows Management Station":

Click Start - Control Panel - Internet Options - Connections - LAN Set-

tings.

Server name

Name or IP address of the proxy server

Port

Number of the port used by the proxy server

User name

User name (ID) for logging on to the proxy server

Password

Password for logging on to the proxy server

Buttons

Change Configuration

Starts the Configuration wizard.

ServerView Update Management 181

5 User Interface

5.4.4

Configuration Wizard

You use this wizard to configure the global parameters for Update Management. The wizard has several steps. All required steps are displayed in the tree structure on the left.

By choosing Next or Previous, you can navigate the wizard from step to step. If a step contains mandatory parameters, Next is deactivated until you have entered the required values.

This wizard opens automatically the first time you access Update Management.

You can open this wizard again at any time to change the settings by choosing Change Configuration.

182 ServerView Update Management

5.4.4.1 Start step (Configuration Wizard)

Start is the first step in the wizard.

5.4 Configuration Main Window

Figure 56: Start step

Repository

Specifies whether l a new repository is to be created.

l an existing repository is to be used.

ServerView Update Management 183

5 User Interface

5.4.4.2 Repository step (Configuration Wizard)

The selection you made at the Start step (use an existing or create a new

repository) determines which fields are displayed in this step.

Use existing Repository

Figure 57: Use Existing Repository step

Repository on Management Station

The repository is located on the local management station.

Repository Location

Absolute path of the repository on the management station.

Format for Windows: <drive letter>:\<directory name>\...

Format for Linux: /<directory name>/...

The globalflash directory, in which the repository is located, is not entered with the path.

184 ServerView Update Management

5.4 Configuration Main Window

The Browse button is only enabled, if you started the Server-

View Operations Manager on the management station directly.

Repository on Network Drive

The repository is located on an other system in the network.

Repository Location (UNC Path)

Absolute path of the repository on the network drive

For Windows:

UNC notation should be used

\\<server name>\<share name>\<path>

User

User name on the system in the network where the repository is located.

Password

Password on the system in the network where the repository is located.

If the user and/or password for the connection to the

Repository on the Network Drive has been changed, proceed as follows:

ServerView Update Management 185

5 User Interface

1. Reboot the management station.

2. In the ServerView Operations Manager open the Configuration applet .

3. Click Change Configuration.

4. In the Start step, select Use existing Repos-

itory.

5. Enable option Repository on Network Drive.

6. Enter User and Password.

Important:

Do not open any other applets before finishing these steps.

Test Connectivity

Tests the connection to the system in the network

For Linux:

After each reboot the remote drive must be mounted manually by an administrator beforehand.

//<absolute pathname>

The mount point itself and the directories above must have read / execute access for user svuser.

186 ServerView Update Management

Create Repository

5.4 Configuration Main Window

Figure 58: Create Repository step

The Browse button is only enabled, if you started the Operations

Manager on the management station directly.

Import from DVD

Imports the repository from the ServerView Update DVD.

Source Path

Absolute path of the repository to be imported on the DVD.

The Browse button is only enabled, if you started the Server-

View Operations Manager on the management station directly.

Examples

For Windows: E:\Firmware

For Linux: /media/Firmware

ServerView Update Management 187

5 User Interface

Download from Web Server

Loads the repository from the web server of Fujitsu Technology Solutions.

Repository Location

Absolute path of the repository on the management station.

If the specified directory does not exist yet, it is created.

If the specified directory already exists, a warning will be issued. If you proceed, all files and directories in the specified directory will first be deleted. Then the repository is created in the specified directory.

Linux:

The user svuser must have authorization to create the repository directory and further subdirectories.

The Browse button is only enabled, if you started the Server-

View Operations Manager on the management station directly.

188 ServerView Update Management

5.4 Configuration Main Window

5.4.4.3 Miscellaneous step (Configuration Wizard)

Figure 59: Miscellaneous step

Default TFTP Address

IP address of a TFTP server (for components that are updated via TFTP server, for example, management blades or connection blades).

Change

Opens the Change IP Address dialog box, where you can enter a new

TFTP address and test the establishment of a connection to the new

TFTP address.

Default Boot Duration

The length of time that Update Manager waits for an updated server to reboot. The time you enter here is added to the length of time the server is unavailable during the update.

ServerView Update Management 189

5 User Interface

5.4.4.4 Download Settings step (Configuration Wizard)

In this step you define the proxy settings for the Download Service.

Figure 60: Download Settings step

HTTP / HTTPS

Select the type of the protocol you want to use for transferring data from the web server.

Web Server

Enter the URL of the web server for the Download Service. Default is the web server of Fujitsu Technology Solutions.

Reset to Default Value

Resets the address of the web server to the default value of Fujitsu

Technology Solutions. This is useful in the case that the user has changed the value to test an own web server.

190 ServerView Update Management

5.4 Configuration Main Window

Do not use proxy server

Enable this option if you want to use the Download Manager without a proxy server. The Download Manager will then ignore all proxy settings.

Use predefined proxy settings defined on Management Station

Enable this option if you want to use the proxy settings defined on the

Management Station.

This option is only available under Windows.

Example for "How to find predefined Proxy Settings on a Windows Management Station":

Click Start - Control Panel - Internet Options - Connections - LAN Set-

tings.

Use proxy server

Enable this option if you want to use a proxy server only defined for the

Download Manager.

For details of the Port of the proxy server, contact your network administrator.

Server name

Name or IP address of the proxy server you want to use

Port

Number of the port used by the proxy server

User name

User name (ID) for logging on to the (pre)defined proxy server

Password

Password for logging on to the (pre)defined proxy server

Test Connectivity

Tests the connection to the web server

ServerView Update Management 191

5 User Interface

Mail Service

If you enable this option, the next step will be Mail Settings.

The persons you define in step Mail Settings are to be informed by email about new updates that have been downloaded by the Download Serv-

ice.

If this option is disabled, the next step will be Activate.

5.4.4.5 Mail Settings step (Configuration Wizard)

This step is only displayed if you selected the Mail Service option in the previous step. Here you define who is to be informed by email about new updates that have been downloaded by the Download Service.

Figure 61: Mail Settings step

192 ServerView Update Management

5.4 Configuration Main Window

Mail To

Recipient address(es) of the e-mail

If more than one address is entered, they are separated by commas.

CC

Additional recipient addresses

If more than one address is entered, they are separated by commas.

From

E-mail address of the sender

SMTP Server

IP address of the SMTP server

Port

Port number of the SMTP server

User

User ID for logging on to the mail server

Password

Password for logging on to the mail server

Confirm Password

Input the same password for confirmation

Buttons

Test Connectivity

Tests the connection to the SMTP server

ServerView Update Management 193

5 User Interface

5.4.4.6 Activate step (Configuration Wizard)

Activate is the last step in the wizard.

Figure 62: Activate step

Activate

Activates parameter changes in the database. If you have changed the repository, the inventory data of all servers is recreated. The new repository data is read into the database. If you selected to use a remote repository, this can take a long time (depending on your network).

While the new repository data is read into the database, a progress bar is displayed.

If you abort the process by clicking Cancel, the status of the repository will be set to incomplete. The current configuration will be deleted and a new configuration will be necessary.

194 ServerView Update Management

5.4 Configuration Main Window

To use the old repository again, start the configuration wizard.

In the Start step, select use existing repository

In the Repository step, specify the old repository.

ServerView Update Management 195

5 User Interface

5.5

Filter dialog box

You can specify which table entries are displayed in a table using the tabs in the Filtering for Column <column name> dialog box. Tables display all rows by default. You can filter a table based on a column and: l a specific value (Standard tab) l a value range, which may comprise several values (Customize tab)

To open the dialog box, click the filter icon in a table header. A filter icon is displayed for each column that can be filtered.

5.5.1

Standard (Filter dialog box)

Figure 63: Standard tab in the Filter dialog box

The Standard tab lists all values and the frequency with which they occur in the selected column:

Select all

Deselect all

<value> selects all table rows for display deselects all table rows shows all table rows with the selected value

196 ServerView Update Management

5.5 Filter dialog box

5.5.2

Character strings (Filter dialog box)

You can enter a character string on the Customize tab. A corresponding table row is displayed for each value in the selected column that coincides with this character string.

Figure 64: Tab for character strings in the Filter dialog box

<column> column pattern

The character string serves as a filter criterion. You can use any alphanumeric characters in the character string, in addition to the following placeholders:

?

represents a single character

* represents any number of characters

\ a wildcard character that allows you to filter using the characters * and ?.

Example:

\* shows all rows that contain a single asterisk in the filtered column.

You can enter any number of characters as a filter criterion. Filtering by regular expression is not permitted.

ServerView Update Management 197

5 User Interface

5.5.3

Integer values (Filter dialog box)

You can enter a specific number range on the Customize tab. A corresponding table row is displayed for each value in the selected columns that coincides with this number range.

Figure 65: Tab for integer values in the Filter dialog box

<column>

List with logical operators and an input field for the first integer in the range, which you can use to formulate a condition.

logical AND or OR operator

AND both conditions must be fulfilled

OR one of the conditions must be fulfilled

<column>

List with logical operators and an input field for the last integer in the range, which you can use to formulate a condition.

198 ServerView Update Management

6 Managing Updates

The applications in Update Management enable effective management of updates for your servers and their components.

6.1

Update Manager

Update Manager allows you to install and update firmware and software components within a domain on PRIMERGY servers using a central management station.

Initial installation is possible for drivers and add-on products.

The following can be updated: l

Firmware l

BIOS l

Drivers l

ServerView agents l

ServerView update agents l

Add-on products

6.1.1

Opening Update Manager

There are two ways to open the Update Manager in the ServerView Operations Manager: l

On the start page of the ServerView Operations Manager, choose

Update Management/Update Manager.

l

In the ServerView menu bar, choose Update Management/Update

Manager.

The Update Manager opens with the main window.

ServerView Update Management 199

6 Managing Updates

6.1.2

Closing Update Manager

You can close the Update Manager by closing the main window.

l

To close the Update Manager main window, click the Close icon in the browser window.

6.1.3

Logging on to the Server

You must log on to servers that have restricted or not certified access status in order to obtain access to these.

1. On the Server Details tab, select the server that you want to log on to, see

"Server Details tab" on page 61 .

2. Click Logon.

The Logon dialog box opens.

3. You can further restrict your selection in the table on the left of this dialog box.

If you have also selected servers that have an access status other than restricted or not certified, these also appear in the table. However, logging on to these servers has no effect.

4. Enter your user ID and password under User Authentication.

5. Click check and set password.

Result:

If a connection to the server can be established, this is indicated by Man-

ageable = yes. In this case, the logon data is checked and access privileges are set for the selected servers. The access status changes from restricted to granted and the password is then valid for the current session.

If a connection to the server cannot be established, this is indicated by Man-

ageable = no. In this case, the logon data is saved under the assumption that it is correct. The access status changes from restricted to trusted. As soon as the server can be reached again, the status changes from trusted to

granted and the password is valid for the current session.

200 ServerView Update Management

6.1 Update Manager

6.1.4

Resetting the update agent of a server

If the update agent of a server is terminated with an undefined status, it may be necessary to reset the agent using the Cleanup function.

The update agent must be reset, for example, if a job ends with the error

Pending Jobs.

After a Cleanup without errors, the update agent is fully functional again and can execute new update jobs.

1. On the Server Details tab, select the relevant server, see

"Server

Details tab" on page 61

.

2. Click Cleanup. The Cleanup wizard opens with the first step Logon.

You must log on to servers that have restricted or not certified access status in order to obtain access to these.

3. You can further restrict your selection from the tab in the table on the left of this dialog box.

If you have also selected servers that have an access status other than restricted or not certified, these also appear in the table. However, logging on to these servers has no effect.

4. Enter your user ID and password under User Authentication.

5. Click check and set password.

Result:

If a connection to the server can be established, this is indicated by

Manageable = yes. In this case, the logon data is checked and access privileges are set for the selected servers. The access status changes from restricted (or not certified) to granted and the password is then valid for the current session.

ServerView Update Management 201

6 Managing Updates

If a connection to the server cannot be established, this is indicated by

Manageable = no. In this case, the logon data is saved under the assumption that it is correct. The access status changes from restrict-

ed (or not certified) to trusted. As soon as the server can be reached again, the status changes from trusted to granted and the password is valid for the current session.

6. Click Next. The Enter TFTP step opens.

This step is only displayed if the cleanup runs via TFTP .

7. Select a management blade or connection blade in the table.

8. Check the IP address of the TFTP server in the TFTP Address field.

The value that you configured using the Configuration Wizard is displayed as default.

If you want to change the TFTP address, click Change TFTP

Address.

The Change TFTP Address dialog box opens.

Enter the IP address of the TFTP server you want to use.

Click OK to confirm your changes.

9. If the table contains more than one management blade or connection blade, repeat steps 7-8 for each individual management blade or connection blade.

10. Click Next. The Schedule Job step opens.

11. Specify the time at which the cleanup job is to be executed in the Exec

Time field.

12. Click Finish to complete the cleanup job.

If you clean up the update agent, all updates that have already been transferred to the PRIMERGY server are deleted.

202 ServerView Update Management

6.1 Update Manager

6.1.5

Displaying the update log for a server

1. On the Server Details tab, select the relevant server, see

"Server

Details tab" on page 61

.

2. Click Show Details. The Show Server Details dialog box is displeyed.

3. Click History. A web page opens with information about all jobs that have been run on the server.

6.1.6

Displaying detailed information about an update

1. On the Update Details tab, choose the update for which you require detailed information, see

"Update Details tab" on page 67

.

2. Click Show Details. The Update Details dialog box opens with additional information about the update you selected, see

"Update Details dialog box" on page 100 .

6.1.7

Managing jobs

The following procedures describe how to manage your jobs.

6.1.7.1 Creating a job

1. Go to the Update Details tab, see

"Update Details tab" on page 67

.

2. In the tree structure, either on the Servers tab or the Updates tab, choose the group for which you want to create a new job.

3. On the left of the Update Details tab, choose either the component group or server for which you want to create a new job.

4. On the right of the Update Details tab, choose the server specific update for which you want to create a new job.

5. Click Create Job. The Create Job wizard opens with the first step

Logon. You must log on to servers that have restricted or not certified access status in order to obtain access to these.

ServerView Update Management 203

6 Managing Updates

6. You can further restrict your selection from the tab in the table on the left of this dialog box.

If you have also selected servers that have an access status other than restricted, these also appear in the table. However, logging on to these servers has no effect.

7. Enter your user ID and password under User Authentication.

8. Click check and set password.

l

If a connection to the server can be established, this is indicated by Manageable = yes. In this case, the logon data is checked and access privileges are set for the selected servers. The access status changes from restricted (or not certified) to granted.

l

If a connection to the server cannot be established, this is indicated by Manageable = no. In this case, the logon data is saved under the assumption that it is correct. The access status changes from restricted (or not certified) to trusted.

9. Click Next. The Change Version step opens.

10. If required, select a different version of the update.

Click Change Version.

The Update Details dialog box opens.

Select a different version from the Available Versions list.

Click Close.

11. Click Next. The Enter Job Name step opens.

12. Assign a name to the new job in the Job Name field.

13. Assign a description to the new job in the Description field (optional).

14. Click Next. The Enter TFTP step opens. This step is only displayed for components that are updated via TFTP server.

15. Select a management blade or connection blade in the table.

204 ServerView Update Management

6.1 Update Manager

16. Check the IP address of the TFTP server in the TFTP Address field.

The value that you configured using the Configuration Wizard is displayed as the default.

If you want to change the TFTP address, click Change TFTP

Address.

The Change TFTP Address dialog box opens.

Enter the IP address of the TFTP server you want to use.

Click OK to confirm your changes.

17. Only MMBS2:

Click Change Flash Address.

The Change Flash Address dialog box opens.

Enter the IP address used for flashing the management blade.

Click OK to confirm your changes.

For all other components that are updated via TFTP server, do not enter anything in this field.

18. If the table contains more than one management blade or connection blade, repeat steps 15-17 for each individual management blade or connection blade.

19. Click Next. The Schedule Job step opens.

20. Specify the time at which the job is to be transferred to the servers in the Transfer Time field.

21. Specify the time at which the update phase is to be started on the servers in the Flash Time field.

23. Only for updates that require a reboot of the system

(indicated by Reboot = yes):

Enter the time at which the servers are to be rebooted in the Boot Time field.

24. Click Finish to create the new job.

ServerView Update Management 205

6 Managing Updates

6.1.7.2 Copying a job

You use this procedure to copy a job to selected servers.

1. On the Job Details tab, select the job that you want to copy, see

"Job

Details tab" on page 71

.

2. Select Copy Job. The Copy Job wizard opens with the first step

Choose Server.

3. Select a server to which the job is to be copied from the Possible

Server list.

4. Click >. The selected server is copied to the Destination Server list.

5. Repeat steps 3 and 4 for each server to which you want to copy the job.

6. Click Next. The LogOn step opens.

7. Log on to all servers that require user authentication (Agent Access =

restricted or not certified).

8. Click Next. The Enter Job Name step opens.

9. Assign a name to the job in the Job Name field.

10. Assign a description to the job in the Description field if required.

11. Click Next. The last step Schedule Job opens.

12. Specify the time at which the job is to be transferred to the servers in the Transfer Time field.

13. Specify the time at which the update phase is to be started on the servers in the Flash Time field.

14. Specify the time at which the server is to be rebooted in the Boot Time field (only if Reboot = yes).

15. Click Finish to start the copy process.

206 ServerView Update Management

6.1 Update Manager

6.1.7.3 Releasing a job

If you establish that jobs can be processed without errors (for example, after a test run on a test computer), you can indicate that these jobs are released.

This is for information purposes only and indicates that the jobs can be executed without errors on the individual PRIMERGY servers.

1. On the Job Details tab, select the jobs that you want to release, see

"Job Details tab" on page 71 .

2. Click Release. The Confirmation dialog box opens.

3. Click Yes to confirm the release of the job.

6.1.7.4 Deleting a job

1. On the Job Details tab, select the jobs that you want to delete, see

"Job Details tab" on page 71 .

2. Click Delete.

The Confirmation dialog box opens, where you must confirm that the job is to be deleted.

3. Click Yes to confirm the deletion of the job.

6.1.7.5 Displaying detailed information about a job

1. On the Job Details tab, select the job for which you require detailed information, see

"Job Details tab" on page 71 .

2. Click Show Details. The Job Details dialog box opens.

Diagnostic data is also displayed here for jobs that have failed.

ServerView Update Management 207

6 Managing Updates

6.2

Repository Manager

The Repository Manager has the following characteristics: l

It recognizes the relevant update information in the repository l

It can change properties of the update information (for example, severity) l

It can release updates l

It can import the Firmware file directory from the ServerView Update

DVD. An import of components with the same version from the DVD overwrites the contents of the repository.

6.2.1

Opening Repository Manager

There are two ways to open the Repository Manager in the ServerView Operations Manager: l

On the start page of the ServerView Operations Manager, choose

Update Management/Repository Manager.

l

In the ServerView menu bar, choose Update Man-

agement/Repository Manager.

The Repository Manager opens with the main window.

6.2.2

Closing Repository Manager

You close the Repository Manager by closing the main window.

l

To close the Repository Manager main window, click the Close icon in the browser window.

208 ServerView Update Management

6.2 Repository Manager

6.2.3

Editing updates

You can edit the individual updates.

1. Select a group in the tree structure.

2. Go to the Updates tab in the Repository Manager, see

"Updates tab" on page 128

.

3. Select the update you want to edit.

4. Click Edit.

The Edit Update's Properties dialog box opens.

5. Change the required properties of the update.

6. Click OK to confirm your changes. The dialog box closes and the changed properties are applied to the update.

6.2.4

Releasing updates

You can release updates once a test update has been completed with satisfactory results for one or more components.

You cannot undo this command. If you want to undo the release, you must edit each update.

1. Select the relevant group in the tree structure.

2. Go to the Updates tab in the Repository Manager, see

"Updates tab" on page 128

.

3. Select the update(s) you want to release.

4. Click Release. Repository Manager opens a dialog box where you must confirm that you want the selected updates to be released.

5. Click Yes to confirm the release. The dialog box closes and the value

yes appears in the Released column for all selected updates.

ServerView Update Management 209

6 Managing Updates

6.2.5

Managing user-defined groups (Collections)

You can use the following procedures to manage user-defined groups.

6.2.5.1 Creating a user-defined group

To create a user-defined group, follow the steps below:

1. Go to the Collections tab in the Repository Manager, see

"Collections tab" on page 132 .

2. Click Create.

The Create Collection dialog box opens.

3. Assign a name to the new group under Name.

4. Assign a comment describing the group under Description.

5. Click >> to copy all component groups from the Source list to the Des-

tination list.

6. If you do not want to copy all component groups, select the component groups that you want to add to the new group under Source and click >.

7. Click OK to create your customized group. The dialog box closes and the new group is created. The selected component groups are assigned to the new group in the ServerView database.

6.2.5.2 Editing a user-defined group

To edit a user-defined group, follow the steps below:

1. Go to the Collections tab in the Repository Manager, see

"Collections tab" on page 132 .

2. Select the group you want to edit.

3. Click Edit.

The Edit Collection dialog box opens.

4. If necessary, change the comment describing the group under Descrip-

tion.

210 ServerView Update Management

6.2 Repository Manager

5. Edit the group.

6. Click OK to confirm your changes. The dialog box closes and the changes are assigned to the selected component groups and components in the ServerView database.

6.2.5.3 Releasing updates in a user-defined group

You can release updates once a test update has been completed with satisfactory results for the components in your user-defined group.

You cannot undo this command. If you want to undo the release, you must edit each update.

1. In the tree structure, select one or more groups under User Collections or the group itself.

2. Go to the Collections tab in the Repository Manager, see

"Collections tab" on page 132 .

3. Select one or more groups whose updates you want to release.

4. Click Release. Repository Manager opens a dialog box where you must click Yes to confirm that you want the updates to be released.

5. Click Yes to confirm the release.

The dialog box closes and the value yes appears in the Released column for all updates for the components in the group.

6.2.5.4 Deleting a user-defined group

To delete a user-defined group, follow the steps below:

1. In the tree structure, select one or more groups under User Collections or the group itself.

2. Go to the Collections tab in the Repository Manager, see

"Collections tab" on page 132 .

3. Select one or more groups that you want to delete.

ServerView Update Management 211

6 Managing Updates

4. Click Delete.

The Repository Manager opens a dialog box where you must confirm deletion with Yes.

5. To confirm deletion, click Yes.

The dialog box closes and the group is deleted. All assignments entered by Repository Manager in the ServerView database are also deleted.

6.2.6

Re-Initializing the Repository

You can update your repository on the management station by importing new components from the ServerView Update DVD or another existing repository.

If you want to replace your complete repository, do this using the Configuration Wizard.

1. Go to the Updates tab in the Repository Manager, see

"Updates tab" on page 128

.

2. Click Import.

The Import Repository dialog box opens.

3. In the Import Path field, specify the directory that contains the update components to be imported.

4. Click Check for Imports.

After the process has finished, all components found in the specified directory (including all subdirectories) are shown in the Source list on the left. If you only want newer updates to be displayed, enable the

Filter only newer updates option.

5. Copy all desired components from the Source list on the left to the Des-

tination list on the right.

212 ServerView Update Management

6.2 Repository Manager

6. Click OK to confirm the import.

All selected update components will be added to the existing repository on the management station if they did not exist before. If an older version of a component exists the newer version is additionally added to the local repository.

When the process is finished the result of importing components into the current repository is shown.

7. After the import, start the Download Service to download the latest updates from the download site of Fujitsu Technology Solutions.

ServerView Update Management 213

6 Managing Updates

6.3

Download Manager

The Download Manager provides you with a convenient way to get the latest versions of firmware, BIOS, drivers, and ServerView agents for your server.

The Download Manager relieves you of the task of performing time-consuming searches for suitable update information.

Information and update files are provided on the web server of Fujitsu Technology Solutions for your server update. The Download Manager first loads the information files to a download directory. The data in these information files provides the Download Manager and the other components of the Server-

View Suite with an overview of the available updates.

In the next step, the required update files are retrieved from the web server.

These contain update information for firmware, BIOS, drivers, or ServerView agents, which can then be distributed to the relevant servers by the Update

Manager. This step-by-step procedure minimizes the load times for the download.

On the user interface, you define download tasks that search for available updates for selected servers in the time intervals you have chosen. The

Download Service of the Download Manager then automatically loads the required files from the web server to a directory on your management server.

6.3.1

Adjusting the Download Service

You can limit the number of download tasks (concurrent jobs) that can be executed in parallel as follows:

1. Make sure that no download tasks are running . Check the status icons on the Schedules Tasks tab.

2. Stop the Download Service.

3. Edit the DownloadServer.ini file in the

<scripts>/ServerView/Download directory.

This directory is located on the management station.

214 ServerView Update Management

6.3 Download Manager

Change the value of the ConcurrentJobsAllowed parameter.

The default value is 30.

The maximum value is 99.

The value 0 is not advisable, as it allows an infinite number of parallel download tasks.

When using a small database system with reduced concurrent access, the value should be set to 5.

4. Start the Download Service.

If you upgrade the Download Manager software, the value of the Con-

currentJobsAllowed parameter will be reset to the default value.

6.3.2

General Information on Download Manager

Use Download Manager to define download tasks for one or more servers and specify when, and how often the download tasks are to be executed.

You can also display information on download tasks already executed.

It is recommended that you execute at least one download task a month.

This ensures that the latest Update Manager information files and Version

Manager database are loaded every month.

The Download Service of the Download Manager executes the defined download tasks automatically as follows:

1. Search on the web server of Fujitsu Technology Solutions for new information files.

2. Load all new information files to the default download directory.

3. The Download Manager uses the information files loaded to check whether updates need to be performed for each server for which the download task is activated.

4. Load all required update files from the web server to the repository directory.

5. Show the results for each defined server via the graphical user interface.

ServerView Update Management 215

6 Managing Updates

6.3.3

Opening Download Manager

There are two ways to open the Download Manager in the ServerView Operations Manager: l

On the start page of ServerView Suite, choose Download Manager under Update Management.

l

In the ServerView menu bar, choose Update Management/Download

Manager.

The main window of Download Manager is displayed.

6.3.4

Closing Download Manager

Use the Close icon in the browser window to close the main window of the

Download Manager.

6.3.5

Creating a new download task

In a first step, you create a download task to suit your requirements. To this download task, you then assign the servers for which searches for updates are to be carried out at the specified time.

1. Go to the Task Management tab.

2. Click Add....

3. Specify when the download task is to be executed under Select Date

and Time to Start.

4. Specify how often the download task is to be executed under Frequen-

cy.

5. Specify how many of the log files are to be saved under Journalize

Log Data.

The Summary output field shows a summary of the values you specified.

6. Click Create to save the new download task. The dialog box closes and the download task is created.

Click Close to cancel processing and discard all entries.

216 ServerView Update Management

6.3 Download Manager

6.3.6

Assigning servers to a download task

In order to use a download task, you assign the required servers to it.

1. Go to the Task Management tab.

2. In the table, select the download task you want to use for your server(s).

3. Click Activate ... .

The dialog box for assigning servers is displayed.

4. In the list on the left, select the server(s) you want to assign to the download task.

5. Click >. The servers selected in the list on the left are shown in the list on the right.

6. Repeat steps 4 and 5 until all the required servers are shown in the list on the right.

7. Click Assign to save the assignment of servers to the download task.

Click Close to cancel processing and discard all changes.

6.3.7

Editing a download task

1. Go to the Task Management tab.

2. Select the download task you want to edit in the table.

3. Click Edit ... .

l

You can change the time at which the download task is to be executed under Select Date and Time to Start.

l

You can change the number of required log files under Journalize

Log Data.

l

As long as no server is assigned to this download task, you can change how often the download task is to be executed under

Frequency.

4. Click Create to save the download task.

Click Close to cancel processing and discard all changes.

ServerView Update Management 217

6 Managing Updates

6.3.8

Deleting a download task

If you no longer need the download task, you can delete it. However, you can only delete a download task if NO servers are assigned to it.

1. Go to the Task Management tab.

2. Select the download task you want to delete in the table.

3. If servers are still assigned to the download task, remove this assignment by clicking Deactivate.

All the services assigned to the download task are stopped.

4. Then click Delete.

The download task selected in the table is deleted.

6.3.9

Monitoring download tasks

The Scheduled Tasks tab shows an overview of the servers available in a domain.

By selecting the required servers or server groups in the tree structure (left), you can restrict the number of servers shown in the tab.

Start service l

To search for updates for a server immediately, select the server in the table and click Once Immediately.

Stop service l

To stop the search for updates for a server, select the server in the table and click Deactivate. The server assignment to a download task is removed.

218 ServerView Update Management

6.4 Configuration

6.3.10 Managing log files

The Log Files tab shows information on download tasks already completed.

Show log file l

If you want to display the entire log file, select the log file in the table and click View.

Delete log file l

If you want to delete log files, select them in the table and click Delete.

l

If you want to delete all log files, click Delete All.

6.4

Configuration

In the Configuration window, you can make global settings, optional and mandatory settings, for the Update Management applications. The current settings are displayed on the General Settings tab, the Mail Settings tab and the Download Settings tab.

To change these settings you use the Configuration wizard.

6.4.1

Opening the configuration

There are two ways to open the configuration in the ServerView Operations

Manager: l

On the start page of the ServerView Operations Manager, choose

Update Management/Configuration.

l

In the ServerView menu bar, choose

Update Management/Configuration

The configuration opens with the main window.

ServerView Update Management 219

6 Managing Updates

6.4.2

Closing the configuration

To close the configuration, close the main window.

l

To close the configuration main window, click the Close icon in the browser window.

6.4.3

Setting Global Parameters

This procedure allows you to configure the global parameters for Update Management. You use the Configuration wizard to do this, which opens automatically the first time you access Update Management.

1. Click Change Configuration. The Configuration wizard opens with the Start dialog box, see

"Start step (Configuration Wizard)" on page

183

.

2. Under Repository, specify whether you want to create a new repository or use an existing repository.

3. Click Next. The Repository step opens.

Different parameters are displayed according to whether you want to configure a new repository or an existing repository:

You can download updates from the download server of Fujitsu

Technology Solutions only if the repository is located on the local management station.

220 ServerView Update Management

6.4 Configuration

Create Repository

4. Specify the location from where the new repository is to be loaded: l from the ServerView Update DVD (Import from DVD) l from the web server (Download from Web Server)

5. If you want to import the repository from DVD, select Import from

DVD and enter the absolute path of the repository on the DVD in the Source Path field.

Examples:

For Windows: E:\Firmware

For Linux: /media/Firmware

If you want to load the repository from the web server, select

Download from Web Server.

6. Enter the absolute path of the repository on the management station in the Repository Location field.

If the specified directory does not exist yet, it is created.

ServerView Update Management 221

6 Managing Updates

Use Existing Repository

4. Enter the location of the repository: l on the local management station (Repository on Man-

agement Station) l on a system in the network (Repository on Network Drive)

5. Enter the absolute path of the repository in the Repository Loca-

tion field in UNC notation.

6. If the repository is on an other system in the network:

Enter the name and password of the user on the system in the

User and Password fields.

7. Click Next. The Miscellaneous step opens.

8. Enter the IP address of a TFTP server (for components that are updated via TFTP server, for example, management blades or connection blade) in the Default TFTP Address field.

9. Enter the length of time that Update Manager is to wait for an updated server to reboot in the Default Boot Duration field. The time you enter here is added to the length of time the server is unavailable during the update.

10. Click Next. The Download Settings step opens.

11. Select the protocol (HTTP/HTTPS) which the Download Service uses for transferring data from the web server.

12. Enter the URL of the web server in the Web Server field. The default

URL is entered here. You can use the Reset to Default Value button to reset this address to the default setting (for example, if it was changed in a new version of Update Management).

13. Select Mail Settings if you want to configure the notification function for new downloads.

222 ServerView Update Management

6.4 Configuration

14. Click Next. If you selected the Mail Settings option, the Mail Settings step opens; otherwise the Activate step opens. In this case, skip the next steps and continue with 24.

15. Enter the recipient address(es) in the Mail To field. Multiple addresses must be separated by commas.

16. Enter the additional recipient addresses if necessary in the CC field.

17. Enter the mail address of the sender in the From field.

18. Enter the IP address of the SMTP server in the SMTP Server field.

19. Enter the port number of the SMTP server in the Port field.

20. Enter the user ID for logging on to the mail server in the User field.

21. Enter the password for logging on to the mail server in the Password field.

22. Enter the password a second time in the Confirm Password field for security purposes.

23. Click Next. The Activate dialog box opens.

24. Click Activate to activate the new settings in the database. If you have changed the repository default, the inventory data of all servers is recreated.

ServerView Update Management 223

6 Managing Updates

6.5

Filtering a table

You can use the values or value ranges in a specific column to filter the entries in a table. A filter icon on the right of the table header indicates which columns can be filtered: .

To filter the entries in a table, follow the steps below:

1. Click the filter icon next to the column. The Filtering for Column dialog box opens with the Standard tab displayed,

"Standard (Filter dialog box)" on page 196

.

2. If you want to filter the columns based on one value, select the value for which you want to display the corresponding table rows on the Stand-

ard tab.

3. If you want to filter the columns based on a value range, select the Cus-

tomize tab.

4. On the Customize tab, formulate the condition for the values that are to be displayed in this column.

5. Select OK to confirm your entries. The dialog box closes and the table entries are displayed according to your selection. The filter icon for the filtered column now appears dark blue.

224 ServerView Update Management

7 Command-Line Interface

The Command-Line Interface (CLI) in Update Manager provides a scripting environment for updating system components, and is part of the ServerView

Operations Manager. The CLI is installed automatically with the Update Manager.

The Command-line interface consists of two parts: l

GFCLI, commands and parameters l citfs.bat, a batch job to update a new server and add the server to the

ServerList

7.1

GFCLI (Command-Line Interface)

The CLI runs without user interaction (quiet mode), creates log files if required and returns various return values. You should test these return values, for example, by checking the %errorlevel% system variable (Windows) or $? (Linux), or similar script and language elements.

The structure of the individual commands flollows the convention:

GFCLI <command> <parameter>

Each command consists of the constant GFCLI, followed by the <command> parameter, which defines the command and subsequent commanddependent parameters.

Parameter

-S (StartFlash)

Description

Starts update with version check

This option only updates system components for which a newer version is found.

-O (StartFlash) Starts update without version check

-W (WaitForDone) Waits for the end of the update jobs

-R (Reboot) Starts an explicit reboot

ServerView Update Management 225

7 Command-Line Interface

Parameter

-C (Cleanup)

-A (Cancel)

-H (Help)

Description

Checks whether all update jobs are finished. If so, the update jobs are deleted.

Deletes unfinished update jobs

Displays the command syntax

If the managed server is protected by access control, you must specify the parameters -L and -P when you use the CLI. These parameters are only used for the StartFlash, Cleanup and Cancel commands, which change the status.

The CLI writes detailed results to a results file so that you can reproduce an update procedure. If the parameter for the results file is missing when the command is called, the default logfile.txt file is used.

In addition, you receive return values to help you program complete update cycles for various results.

7.1.1

Call Parameters

-S (StartFlash command)

Starts update with version check

This option only updates system components for which a newer version is found.

-O (StartFlash command)

Starts update without version check.

In this case all system components are updated with the latest version of the specified repository, without performing a version check, i.e. even if versions are equal or the installed version is newer (leading to a downgrade). This parameter is therefore risky!

It should only be used by persons who have detailed knowledge of the specified repository and of the dependencies between the installed versions (for example, quality test and support employees).

226 ServerView Update Management

7.1 GFCLI (Command-Line Interface)

-W (WaitForDone command)

Waits for the end of the update jobs (Job Status = READY or REBOOT)

-R (Reboot command)

Starts an explicit restart.

-C (Cleanup command)

Checks whether all update jobs are finished (Job Status = READY). If so, the update jobs are deleted.

-A (Cancel command)

Deletes unfinished update jobs.

-H

Displays the command syntax.

-D

The StartFlash only updates Microsoft-certified system components as standard. This parameter allows you to update non-certified components also.

-N <system>

DNS name or IP address of the managed PRIMERGY server.

-U <path>

Absolute path of the repository.

-F <results file>

File to which the results of the update procedure are written.

Default:logfile.txt

-L <user>

Login user ID for access control.

-P <password>

-S

Login password for access control.

Forced variant of the Cancel command.

ServerView Update Management 227

7 Command-Line Interface

-M

Specifies that the managed system is a management blade server. The parameters -T and -I must also be specified to enable communication with the TFTP server (the latter parameter is only required in the Start-

Flash ) command.

-B

Specifies that the managed system is a connection blade server. The parameters -T and -Z must also be specified. -T in order to enable communication with the TFTP server,-Z in order to specify the IP address of the management blade server, since inventory data for the connection blade server is collected and provided via the management blade server.

-E

Specifies that the managed system is an iRMC. The parameters -T and -

Y must also be specified, -T in order to enable communication with the

TFTP server,-Y because the data for the VersionView.sav

file cannot be collected by the program and an external inventory is required.

-Z <IP-addr>

IP address of the management blade server. The IP address is only needed for updating connection blade servers (see option -B).

-T <IP-addr>

IP address of the TFTP server for updates via TFTP server (for example, in case of a management blade or connection blade).

-I {<IP-addr> | NO_ADDR}

Update IP address of the management blade for updates via TFTP server.

This address must be unique across the network. In the case of newer management blade versions (for example, MMBS3), where it is not necessary to specify an IP address, you must specify NO-ADDR here.

-Y <path>

Absolute path of the Inventory file "VersionView.sav" of the managed system.

Mandatory on Linux if the managed system is a management blade or connection blade or if the managed node is an iRMC.

228 ServerView Update Management

7.1 GFCLI (Command-Line Interface)

When ServerView Operations Manager is installed the Inventory file can be found in the working directory of the Update Manager following the subdirectory "versionviewsav/<name of MMB>"

-K <community>

SNMP Community String if not public.

7.1.2

StartFlash (Command)

Syntax

GFCLI {-S|-O} [-D] -N <system> -U <path>

[-F <results file>] [-L <user> [-P <password>]]

[-M -T <IP-addr> -I {<IP-addr>|NO_ADDR} [-K <Community>] | -T <IP-addr> [-K <Community>]]

[-B –Z <IP-addr> -T <IP-addr>]

[-E -T <IPaddr> -Y <inventory>]

Description

When the -S parameter is used, StartFlash reads the inventory of the

PRIMERGY server and compares all components with the versions in the specified repository. An update is only initiated for a component if a newer version is found in the repository. A downgrade is not possible with this parameter.

When the -O parameter is used, there is no version check, that is, all components are updated with the latest version found in the specified repository.

Parameter -O is risky! This parameter should only be used by persons who have detailed knowledge of the repository used and of the dependencies between the installed versions. If, for example, a version of a component in the repository is older than the installed version, the installed version is downgraded in this case.

The command ends as soon as all steps to start the update are completed.

The command does not wait for the update procedure to be completed.

The command terminates with a SequenceError if a previous update procedure has not yet been completed with the Cleanup command or cancelled with the Cancel command. In this case, update jobs still exist that have one of the job status specified above.

ServerView Update Management 229

7 Command-Line Interface

If a connection cannot be established, the command terminates immediately with a timeout.

Return values

 0 Update started without errors.

 1 Ok, no obsolete components found.

 2 Timeout (no connection to the managed server).

 3 SequenceError - command is not permitted during this phase.

 4 An error occurred when the update phase was started.

 5 GFI error

 6 The required parameters for access control do not exist.

 7 Access denied

10 Parameter error

11 Memory bottleneck

12 Multiple starting of CLI denied.

13 The results file (option -F or logfile.txt) could not be opened.

14 The GFLog.txt log file could not be opened.

16 Rebuild of the inventory in progress. Try again later

17 Check command successfull, reboot needed by at least one component

18 Managed server type not supported (virtual server / old offline server)

230 ServerView Update Management

7.1 GFCLI (Command-Line Interface)

7.1.3

WaitForDone (Command)

Syntax

GFCLI -W -N <system> [-F <results file>]

[-M -T <IP-addr>]

[-B –Z <IP-addr> -T <IP-addr>]

[-E -T <IPaddr> -Y <inventory>]

Description

WaitForDone returns a return value of 0, 4, 8 or 9 if all update jobs have been processed (with or without errors).

In contrast to the Cleanup command, the update results are not deleted on the managed server when this command is executed. You can execute Wait-

ForDone more than once, and the results file will be updated each time.

If a connection cannot be established, the command returns a timeout after a maximum of 60 seconds. In this case, you can execute the command again to query the status.

ServerView Update Management 231

7 Command-Line Interface

Return values

 0

Update Ok (job status is READY)

All update jobs have been executed without errors.

 1

No current job exists (connection established)

 2

Timeout (no connection to the managed server)

 3

SequenceError - command is not permitted during this phase (a job has PREPARED status)

If a GlobalFlash Agent up to V 4.71 is installed on your system, please notice the additional description below.

 4

Update with errors (job status is READY)

At least one job could not be executed without errors.

 5

GFI error

 8

Update ok (job status is REBOOT)

A job is waiting for the reboot to be executed.

 9

Update with errors (job status REBOOT)

A job is waiting for the reboot to be executed. However, in addition to the jobs that have been executed successfully without errors and now require a reboot, there are also jobs with errors. The reboot must be executed explicitly by restarting the managed server or using the

Reboot CLI command.

10 Parameter error

11 Memory bottleneck

12 Multiple starting of CLI denied

13 The results file (option -F or logfile.txt) could not be opened.

14 The GFLog.txt log file could not be opened.

16 Rebuild of the inventory in progress. Try again later

17 Check command successfull, reboot needed by at least one component

18 Managed server type not supported (virtual server / old offline server)

232 ServerView Update Management

7.1 GFCLI (Command-Line Interface)

Update job using GlobalFlash Agent up to V 4.71

When you start an update job, the following dialog is displayed on the managed server:

If the dialog is answered with Cancel, the command GFCLI -W(=WaitForDone) returns the value 3.

In <result file>, the message Flash Cancelled by User is logged.

To cleanup the managed server, the following command has to be used:

GFCLI -A -S (=Cancel, forced variant)

7.1.4

Reboot (Command)

Syntax

GFCLI -R -N <system> [-F <results file >]

[-L <user> [-P <password>]]

Description

Reboot initiates the reboot that is required by at least one job (indicated by

Job status REBOOT). When the reboot is done, the status of these jobs automatically changes to READY.

If a connection cannot be established, the command returns with a timeout after a maximum of 60 seconds.

ServerView Update Management 233

7 Command-Line Interface

Return values

0

Immediate reboot initiated

1

No current job exists (connection established)

2

Timeout (no connection to the managed server)

3

SequenceError - command is not permitted during this phase.

- Flash boot status is not Online Reboot required or

- no job found with the status REBOOT

5

GFI error

6

The required parameters for access control do not exist.

7

Access denied

10 Parameter error

11 Memory bottleneck

12 Multiple starting of CLI denied

13 The results file (option -F or logfile.txt) could not be opened.

14 The GFLog.txt log file could not be opened.

16 Rebuild of the inventory in progress. Try again later

17 Check command successfull, reboot needed by at least one component

18 Managed server type not supported (virtual server / old offline server)

234 ServerView Update Management

7.1 GFCLI (Command-Line Interface)

7.1.5

Cleanup (Command)

Syntax

GFCLI -C -N <system> [-F <results file>]

[-L <user> [-P <password>]] [-M -T <IP-addr>]

[-B –Z <IP-addr> -T <IP-addr>]

[-E -T <IPaddr> -Y <inventory>]

Description

Cleanup executes the same steps as WaitForDone, but also deletes the update results on the managed server and completes the update procedure.

The managed server returns to its original status and the update results are no longer available on the server.

If a connection cannot be established, the command returns with a timeout after a maximum of 60 seconds.

A cleanup is only permitted when the Job status = Ready.

A cleanup is not permitted if a job has been transferred and is waiting to be executed (Job Status = Prepared) or is currently being executed (Job Stat-

us = Working)

After this command is executed, the update results are written once only to a results file. You cannot write the last update results to the results file several times, as you can with the WaitForDone command.

Cleanup must also be executed after a WaitForDone (with a subsequent

Reboot if necessary) to complete the update procedure.

ServerView Update Management 235

7 Command-Line Interface

Return values

0

Update Ok (job status is READY)

All update jobs have been executed without errors.

1

No current job exists (connection established)

2

Timeout (no connection to the managed server)

3

SequenceError - command is not permitted during this phase (a job has PREPARED status)

4

Update with errors (job status is READY)

At least one job could not be executed without errors.

5

GFI error

6

The required parameters for access control do not exist.

7

Access denied

10 Parameter error

11 Memory bottleneck

12 Multiple starting of CLI denied

13 The results file (option -F or logfile.txt) could not be opened.

14 The GFLog.txt log file could not be opened.

16 Rebuild of the inventory in progress. Try again later

17 Check command successfull, reboot needed by at least one component

18 Managed server type not supported (virtual server / old offline server)

7.1.6

Cancel (Command)

Syntax

GFCLI -A -N <system> [-F <results file>]

[-L <user> [-P <password>]] [-M -T <IP-addr>] [-S]

[-B –Z <IP-addr> -T <IP-addr>]

[-E -T <IPaddr> -Y <inventory>]

236 ServerView Update Management

7.1 GFCLI (Command-Line Interface)

Description

Cancel cancels the execution of the update jobs that have already been transferred to the managed server, and deletes the PREPARED update status.

The PREPARED status may exist if another user has used the GUI to execute a Prepare Updates but has not yet executed an Execute Updates; or in the case of an exception, which only arises if an error has occurred.

If a connection cannot be established, the command is terminated with a timeout after a maximum of 60 seconds.

Return values

0

No errors

1

No update status

2

Timeout (no connection to the managed server)

3

SequenceError, command not permitted during this phase

- job status PREPARED does not exist or

- job status READY/REBOOT exists (only if option -S is not set)

5

GFI error

6

The required parameters for access control do not exist.

7

Access denied

10 Parameter error

11 Memory bottleneck

12 Multiple starting of CLI denied

13 The results file (option -F or logfile.txt) could not be opened.

14 The GFLog.txt log file could not be opened

16 Rebuild of the inventory in progress. Try again later

17 Check command successfull, reboot needed by at least one component

18 Managed server type not supported (virtual server / old offline server)

ServerView Update Management 237

7 Command-Line Interface

7.1.7

Result Files

All results of an update procedure are written to the specified results file. In this case, the results are added, which means that the files increase in size.

You must manage (delete or rename) these results files yourself. The information is contained in the files in the form of event blocks.

In the case of the StartFlash, Cleanup, and Cancel commands, the results are also written to the GFLog.txt log file. You will find this file in the following directory:

Windows:

<ServerView Installation Dir>\UpdateManager

Linux:

<ServerView Installation Dir>/UpdateManager/log

Events

StartFlash

Ready

Cancel

SequenceError

ParamError

LogonError

MemoryError

Additional sub-events

Count

Result

GFI Error

Timeout

As well as the return values of the commands, the results files also contain additional information about the updated objects and the results.

238 ServerView Update Management

7.1 GFCLI (Command-Line Interface)

Job Statuses

The following statuses are documented for each individual job in the specific results file:

PREPARED

WORKING

REBOOT

READY

The update job has been transferred to the server.

The update job is currently being executed.

The update job has been processed correctly. A reboot is required to become Job Status = READY

The update job has been processed (correctly or with errors).

7.1.7.1 StartFlash (Event)

The StartFlash event normally contains the Count sub-event. This sub-event is always entered as the header. The number specified in this entry indicates the total number of objects selected for the update (for which newer versions are available). Each object has its own StartFlash event with a Result subevent.

ServerView Update Management 239

7 Command-Line Interface

Event.0=StartFlash

SubEvent.0=Count

CompCount.0=1

NoError.0=0

Event: StartFlash

Sub-event: Count

Number of components

(may be 0)

Number of errors

Event.1=StartFlash

SubEvent.1=Result

Event: StartFlash

Sub-event: Result

ObjTypeName.1=MAH3091MC Object type (component)

ObjName.1=Disk:PCI1.11.1.SCSI0.0.0

Relevant object

OldVersion FW.1=5207

NewVersion FW.1=5208

LastCommand.1=

Old FW/BIOS version of the object

New FW/BIOS version of the object

Last command of the CLI

Error.1=0

ErrorText.1=ERROR[0]] faultless execution

Error number in the event of an error

Description of the return value

If an error occurs in the SVUMI.dll when a command is being executed, the entries in the results file depend on the current phase of the StartFlash process. The LastCommand.# field may contain the following entries: l

AddJob l

GetUpdatableComponentsS l

StartUpdate l

WaitForPreparedStatus l

DoFlashBoot

240 ServerView Update Management

7.1 GFCLI (Command-Line Interface)

Examples

Error executing AddJob; the list contains error codes for each component.

Event.0=StartFlash

SubEvent.0=Count

CompCount.0=1

NoError.0=1

Event.1=StartFlash

SubEvent.1=Result

ObjTypeName.1=MAH3091MC

ObjName.1=Disk:PCI1.11.1.SCSI0.0.0

OldVersion FW.1=5207

NewVersion FW.1=5208

LastCommand.1=AddJob

Error.1=91

ErrorText.1=ERROR[91] couldn't build control file name

Error executing StartUpdate; a component list is not available because the error refers to the StartUpdate GFI request.

Event.0=StartFlash

SubEvent.0=Error

CompCount.0=2

LastCommand.0=StartUpdate

Error.0=12

ErrorText.0=ERROR[12] flash file missing

(cannot copy file)

If no obsolete components exist (compared with the repository), only the header is shown.

Event.0=StartFlash

SubEvent.0=Count

CompCount.0=0 number of obsolete FW versions = 0

NOERROR.0=0

ServerView Update Management 241

7 Command-Line Interface

7.1.7.2 Ready (Event)

If the CLI detects the READY job status after it is started, the return values of all updated components appear as follows:

Event.0=Ready

SubEvent.0=Count

CompCount.0=2

NoError.0=0

Event: Ready

Sub-event: Count

Number of components

(may be 0)

Number of errors

Event.1=StartFlash

SubEvent.1=Result

Event: Ready

Sub-event: Result

ObjTypeName.1=DAC1164P Object type (component)

ObjName.1=SCSIController:PCI6.8.1

Relevant object

Type.1=0

Status.1=5

Error.1=0

ErrorText.1=ERROR[0] faultless execution

Status (5) = READY

Return value of the job

Description of the return value

Event.2=Ready

SubEvent.2=Result

ObjTypeName.2=ST336704LC

ObjName.2=Disk:PCI1.15.1.SCSI0.0.0

Type.2=0

Status.2=5

Description of the error

242 ServerView Update Management

7.1 GFCLI (Command-Line Interface)

Error.2=0

ErrorText.2=ERROR[0] faultless execution

7.1.7.3 Cancel (Event)

Event.0=Cancel

Error.0=0

ErrorText.0=ERROR[0] faultless execution

Event: Cancel

Error number in the event of an error

Description of the return value

7.1.7.4 SequenceError (Event)

This event has no sub-events. This event indicates that a command cannot be executed because Update Manager has an incorrect status.

Examples l

An update status should not exist when StartFlash is called.

l Cleanup is only possible if the status is READY.

l Cancel (without parameter -S) is only possible if the status is PRE-

PARED .

Event.0=SequenceError A command was called during the wrong phase (unauthorized update status).

ServerView Update Management 243

7 Command-Line Interface

7.1.7.5 ParamError (Event)

This event has no sub-events. This event indicates that an unauthorized parameter was used for the specified command. All parameters are checked each time the CLI is called. If unauthorized parameters are used, one line is used to specify where the problem occurred in each case.

Event.0=ParamError Incorrect number/combination of parameters or an invalid update path.

7.1.7.6 LogonError (Event)

This event has no sub-events. This event indicates that an attempt to log on to the managed server has failed.

Event.0=LogonError Access denied

7.1.7.7 MemoryError (Event)

Event.0=MemoryError Insufficient memory is available.

244 ServerView Update Management

7.1 GFCLI (Command-Line Interface)

7.1.8

Batch Files (Examples)

The following examples are based on Windows. If a Linux shell is used, the

Linux variable $? must be queried instead of the %errrorlevel% Windows variables in order to test the return value of the CLI command, for example:

GFCLI -S -N <system name> -U <path name> if [ $? = 0 ]; then ....

File 1

@echo off rem ******************************************************** rem * cli-exa.bat ****************************************** rem ******************************************************** rem * Batch file to flash all components of PRIMERGY servers, supported by rem * GlobalFlash to their newest version.

rem * All servers have to be listed in a ServerList. The firmware must be rem * available in local GlobalFlash FirmwareTree.

rem * Two other batch files are called: rem * cli-init.bat: Check states and availibility of a server and execute rem * StartFlash for the server rem * cli-work.bat: Wait for completion of the flash for each server rem * ------------------------rem * Input-parameters: rem * The actual directory has to contain 2 Control-files for this batch: rem * 1.)ServerList-file "serverls.txt" rem * Each line consists of 3 fields:Server,user,password rem * If the line beginns with ";" in ServerList, the line will be ignored rem * 2.)File "fwpath.txt" with the absolut path of the FirmwareTree rem * Output-parameters: rem * 1.)File "oklist.txt" with the list of servers, which are updated withrem * out any errors or which are not flashed because they are actual rem * 2.)Result-Files <servername>.txt for each server rem ******************************************************* rem

:start

ServerView Update Management 245

7 Command-Line Interface rem rem ******************************************************* rem * WaitServerlist initialisation rem * (WaitServerList: temporary subset of Serverlist) rem ******************************************************** rem if exist svwaitls.txt del svwaitls.txt

if exist oklist.txt del oklist.txt

rem rem ******************************************************** rem * Check actual states of all server of the ServerList and StartFlash rem * Only State "No Flash states" expected - other states will be cleaned rem * or aborted first rem * Only for servers with "No flash states" "StartFlash" is executed rem * Thease servers were added to WaitServerlist (WaitForDone-cycle) rem * StartFlash is executed with Path of FirmwareTree contained rem * in file fwpath.txt

rem * Batch-File cli-init.bat is called for each server with the parameters rem * of the fields in ServerList rem ***************************************************** rem for /F "eol=; tokens=1-3 delims=, " %%i in (serverls.txt) do call cliinit %%i %%j %%k rem rem *************************************************** rem * WaitForDone cycle rem * The flashs are running rem * Now is time to WaitForDone (status ready - hopefully without any error) rem * All servers in flashingmode are listed in svwaitls.txt

rem * Each server, returns with timeout is set in svtmpls and WaitForDone rem * is started again rem * Each server, which returns without errors, is set to oklist.txt

rem * (After CleanUp) rem * Each server, which finished with errors will left be in error state rem * all information in the speziell result-file rem * Batch-File cli-work.bat is called for each server with the

246 ServerView Update Management

7.1 GFCLI (Command-Line Interface) parameters rem * of the fields in WaitServerList (subset of ServerList) rem ******************************************************** rem if not exist svwaitls.txt goto doneall

:waitnxt if exist del svtmpls.txt

for /F "eol=; tokens=1-3 delims=, " %%i in (svwaitls.txt) do call cliwork %%i %%j %%k if not exist svtmpls.txt goto doneall copy svtmpls.txt svwaitls.txt

goto waitnxt

:doneall

@echo All activities done. Listed servers have returned flash without any error!

@echo -----------------------------------------------------type oklist.txt

ServerView Update Management 247

7 Command-Line Interface

File 2 rem ********************************************************* rem * cli-init.bat ************************ rem * **************************************************** rem * Batch File to check states of a special server rem * and to execute StartFlash if states are ok rem * -----------------------------------------------------rem * Input-parameters: rem * - cli-init server(%1) user(%2) Password(%3) rem * - File "fwpath.txt" with the absolut path of the FirmwareTree rem ******************************************************* rem

:start

@echo off rem rem ******************************************************** rem * Return-File initialisation rem ******************************************************** rem

@echo off >%1.txt

:start1 rem rem ******************************************************** rem * "WaitForDone" to check whether there are old flashs rem * (prepared, ready) or not rem * If there are states, they are canceled or ceaned rem * If server is not "online" Timeout occured rem * Only a server without flash-states will be token for flash rem * Means returncode 1 is the only one to go on for flash!

rem ******************************************************** rem gfcli -W -N %1 -L %2 -P %3 -F %1.txt

if %errorlevel%==1 goto nostates if %errorlevel%==2 goto timeout if %errorlevel%==3 goto statenok if %errorlevel%==4 goto errors if %errorlevel%==5 goto gfierror if %errorlevel%==6 goto nologop

248 ServerView Update Management

7.1 GFCLI (Command-Line Interface) if %errorlevel%==7 goto noaccess if %errorlevel%==10 goto parerror if %errorlevel%==11 goto memerror if %errorlevel%==0 goto old-ok

@echo.

@echo Undefined returncode!

goto endchk rem rem ******************************************************** rem * Old Flashs (prepared) detected Cancel them rem ******************************************************** rem

:statenok

@echo.

@echo Unknown Flash States or flash states "prepared" for server %1 available

@echo Who has started them ? Please check!

@echo After continue the old flashs are canceled pause

@echo Cancel flash states for server %1 gfcli -A -N %1 -L %2 -P %3 -F %1.txt

if %errorlevel%==1 goto nothtodo if %errorlevel%==2 goto timeout if %errorlevel%==3 goto statenok if %errorlevel%==5 goto gfierror if %errorlevel%==6 goto nologop if %errorlevel%==7 goto noaccess if %errorlevel%==10 goto parerror if %errorlevel%==11 goto memerror if %errorlevel%==0 goto cancok

@echo.

@echo Undefined returncode!

goto chkend

:cancok

@echo.

@echo All jobs canceled for server %1 goto start1 rem

ServerView Update Management 249

7 Command-Line Interface rem ******************************************************** rem * Old Flashs (ready) detected CleanUp them rem ******************************************************* rem

:old-ok

@echo.

@echo Flash States "ready"(without errors) for server %1 available rem

:old-nok

@echo.

@echo Flash States "ready"(with errors) for server %1 available goto cleanall rem

:cleanall

@echo Who has started them ? Please check!

@echo After continue the old flashs are reseted pause

@echo CleanUp flash states for server %1 gfcli -C -N %1 -L %2 -P %3 -F %1.txt

if %errorlevel%==1 goto nothtodo if %errorlevel%==2 goto timeout if %errorlevel%==3 goto statenok if %errorlevel%==4 goto c-oldnok if %errorlevel%==5 goto gfierror if %errorlevel%==6 goto nologop if %errorlevel%==7 goto noaccess if %errorlevel%==10 goto parerror if %errorlevel%==11 goto memerror if %errorlevel%==0 goto c-oldok

@echo.

@echo Undefined returncode!

goto chkend rem

:c-oldok

@echo.

@echo CleanUP - Jobs detected all ok goto start1 rem

250 ServerView Update Management

7.1 GFCLI (Command-Line Interface)

:c-oldnok

@echo.

@echo CleanUP - Jobs detected not all ok goto start1 rem rem ******************************************************** rem * Errors in Check phase rem ******************************************************** rem

:nothtodo

@echo.

@echo CleanUp or cancel- No flash states ?????

goto endchk rem

:timeout

@echo.

@echo - Timeout goto endchk rem

:statenok

@echo.

@echo CleanUp, cancel or StartFlash- Wrong state goto endchk rem

:gfierror

@echo.

@echo Wait for done, CleanUp or Cancel - gfi error goto endchk rem

:sferror

@echo.

@echo StartFlash - generic error goto endchk rem

:gfierro1

@echo.

@echo StartFlash - gfi error goto endchk

ServerView Update Management 251

7 Command-Line Interface rem

:nologop

@echo.

@echo - No logon parameters goto endchk rem

:noaccess

@echo.

@echo - access denied goto endchk rem

:parerror

@echo.

@echo - Parameter error goto endchk rem

:memerror

@echo.

@echo - Memory error goto endchk rem

:nostates for /F %%i in (fwpath.txt) do set fwp=%%i rem rem ******************************************************** rem * "StartFlash" for the server rem ******************************************************** rem gfcli -S -N %1 -L %2 -P %3 -U %fwp% -F %1.txt

if %errorlevel%==1 goto nothtodo if %errorlevel%==2 goto timeout if %errorlevel%==3 goto statenok if %errorlevel%==4 goto sferror if %errorlevel%==5 goto gfierro1 if %errorlevel%==6 goto nologon if %errorlevel%==7 goto noaccess if %errorlevel%==10 goto parerror if %errorlevel%==11 goto memerror

252 ServerView Update Management

7.1 GFCLI (Command-Line Interface) if %errorlevel%==0 goto stflok

@echo.

@echo Undefined returncode!

goto endchk rem

:nothtodo rem rem ******************************************************** rem * "StartFlash"- nothing to do ! - All componentsare up to date rem ******************************************************** rem

@echo Server %1: "StartFlash"- nothing to do ! - All components are up to date

@echo %1 -Nothing to do - Actual Firmware already installed >>oklist.txt

goto endchk rem

:stflok rem rem ******************************************************* rem * "StartFlash"- ok -Flash process running - wait for done for this server rem * Server is added to WaitServerList rem ********************************************************* rem

@echo Server %1: "StartFlash"- ok -Flashprocess running - Please wait for done

@echo %1,%2,%3 >>svwaitls.txt

rem endchk

ServerView Update Management 253

7 Command-Line Interface

File 3 rem ******************************************************** rem * cli-work.bat ************************ rem * ****************************************************** rem * Batch File to check states after flash of a special server rem * If WaitForDone returned timeout, the server will be added to rem * tmp-list (=WaitServerlist for next schedule) rem * if WaitForDone returned with ready and no error the server will be rem * to oklist rem * -----------------------------------------------------rem * Input-parameters: rem * - cli-work server(%1) user(%2) Password(%3) rem ******************************************************** rem

:start

@echo off echo off >%1.txt

gfcli -W -N %1 -L %2 -P %3 -F %1.txt

if %errorlevel%==1 goto nothtodo if %errorlevel%==2 goto timeout if %errorlevel%==3 goto statenok if %errorlevel%==4 goto readynok if %errorlevel%==5 goto gfierror if %errorlevel%==6 goto nologop if %errorlevel%==7 goto noaccess if %errorlevel%==10 goto parerror if %errorlevel%==11 goto memerror if %errorlevel%==0 goto ready-ok

@echo.

@echo Undefined returncode!

goto endwk rem rem ******************************************************** rem * Timeout in this phase is normal rem * - during Flash there will be more Timeouts rem * Server is set in tmplist to be scheduled next time rem ******************************************************** rem

254 ServerView Update Management

7.1 GFCLI (Command-Line Interface)

:timeout

@echo.

@echo - Timeout Server %1 - Go on waiting for a minute

@echo %1,%2,%3 >>svtmpls.txt

goto endwk rem rem ******************************************************** rem * In case of error after flash, no Cleanup is done rem * Error situation has to be analyzed (see return-file) rem ******************************************************** rem

:readynok

@echo.

@echo - Ready Server %1 - errors detected - Analysing necessary goto endwk rem rem ******************************************************** rem * Great! Flashs are ready (without error) CleanUp them rem ***************************************************** rem rem ******************************************************* rem * All component of the server were flashed without error rem * The jobs have to CleanUp rem ******************************************************* rem

:ready-ok

@echo.

@echo Flash States "ready"(without errors) for server %1 available

@echo CleanUp flash states for server %1 gfcli -C -N %1 -L %2 -P %3 -F %1.txt

if %errorlevel%==1 goto nothtodo if %errorlevel%==2 goto timeoutc if %errorlevel%==3 goto statenok if %errorlevel%==4 goto c-oldnok if %errorlevel%==5 goto gfierror if %errorlevel%==6 goto nologop if %errorlevel%==7 goto noaccess if %errorlevel%==10 goto parerror

ServerView Update Management 255

7 Command-Line Interface if %errorlevel%==11 goto memerror if %errorlevel%==0 goto cu-ok

@echo.

@echo Undefined returncode!

goto endwk rem rem ******************************************************** rem * All component of the server were flashed without error rem * Clean up is done - the Server is set to OK-list rem ******************************************************** rem

:cu-ok

@echo.

@echo Server %1:All components are flashed without errors

@echo %1 -All components are flashed without errors >>oklist.txt

goto endwk rem

:c-oldnok

@echo.

@echo CleanUP - Jobs detected not all ok goto start rem rem ******************************************************** rem * Errors in Wait phase rem ******************************************************** rem

:nothtodo

@echo.

@echo CleanUp or WaitForDone- No flash states ?????

goto endwk rem

:timeoutc

@echo.

@echo CleanUp, - Timeout???

goto endwk rem

:statenok

@echo.

256 ServerView Update Management

7.1 GFCLI (Command-Line Interface)

@echo CleanUp or WaitForDone- Wrong state ???

goto endwk rem

:gfierror

@echo.

@echo CleanUp or WaitForDone - gfi error ???

goto endwk rem

:nologop

@echo.

@echo CleanUp or WaitForDone - No logon parameters ???

goto endwk rem

:noaccess

@echo.

@echo CleanUp or WaitForDone - access denied ???

goto endwk rem

:parerror

@echo.

@echo CleanUp or WaitForDone - Parameter error ???

goto endwk rem

:memerror

@echo.

@echo CleanUp or WaitForDonep - Memory error ???

goto endwk rem

:endwk

Input File "ServerList (serverls.txt)"

: aster,Administrator,Password tulip,Administrator,Password rose,Administrator,Password carnation,Administrator,Password

Input File "FirmwarePath (fwpath.txt)":

H:\GlobalFlash\GF_Primergy_Firmware

ServerView Update Management 257

7 Command-Line Interface

7.1.9

CLI Standalone

There is a seperate product "UpdateManagerCLI" that is deliberately meant for environments where there is no ServerView Operations Manager.

But because there is no SVOM there is one major restriction, when running under Linux and intending to update a management blade or connection blade:

As documented in description of the call parameters (Y option) the Inventory of the management blade or connection blade must exist as a file (VersionView.sav) and has to be passed via the Y option.

But since there is no SVOM there is no Inventory-Service running and thus no Inventory file is built on the system.

Thus without providing the Inventory file via other means it is not possible to update the management blade / connection blade under Linux.

7.2

citfs.bat (batch job)

This tool is programmed for Windows command line to add a new server to the ServerList and update this server to the latest versions of BIOS, firmware and drivers. Afterwards the new servers can be administered as usual by the

ServerView GUI.

Requirements

If the ServerView update agent is configured with security (AccountCheck), a user group must be specified (see

"Prerequisites on managed servers" on page 12

and

"Prerequisites on the Central Management Station (CMS)" on page 16 ).

Usage of the tool

The tool CITFS (CLI Integration Tool For ServerView) is located on the following directory:

<sv om installation path> \svom\bin\ServerView\OnlineUpdate

.

258 ServerView Update Management

7.2 citfs.bat (batch job)

To execute the tool, open a command prompt and change to specified directory (see above).

citfs.bat {<IP-Addr> <servername> <community>}[<User>

<Password>][force]

Description of the parameters

IP-Addr

IP-Address of the new server.

servername

Name of the new server.

community

SNMP-community string.

User / Password

Login user ID and password for access control.

This parameters are only required if the ServerView update agent on the managed node is configured with AccountCheck.

force

Causes the tool to reboot without the interaction of the administrator after the updates.

log files

Log files are created in the following directory:

<sv om installation path> \svom\data\ServerView\OnlineUpdate\Logs\<servername>\

ServerView Update Management 259

7 Command-Line Interface

Restrictions

l

The repository path might not be a network path.

l

Only standard PRIMARGY server can be integrated, l

Blade server or ESXi systems cannot be integrated.

Return values

 0 Script finished successful

 1 Server already exists in the ServerList

 2 Server not reachable

 3 Server status = not manageable

 4 No access to the repository (see restrictions)

 5 SVOM directory not found

 6 No access to the managed node

 7 Server added to the ServerList but update/flash failed

9 Syntax error

260 ServerView Update Management

8 Troubleshooting

8.1

Error messages in the Update Manager

Below is an overview of the error messages displayed in the Return Text field in the Job Details dialog box (see

"Job Details dialog box" on page

117 ).

For each message there is a description of the action you can take to eliminate the error.

APPL_CURRENTLY_RUNNING

Internal overlap of program runs

Action l

In the Job Details dialog, click Show Logfile.

In the log file which opens, you will find a hyperlink to a zip file containing the diagnostics files for the selected job.

l

Save the zip file and send it to your Support of Fujitsu Technology

Solutions.

If the update was done successfully but the inventory could not be created because the scheduled task of Inventory Manager is already running for this server: l

Check the inventory and the listed updates in Update Manager.

If data is still old: l

Create the inventory manually via Inventory Manager - Server List tab - Recollect Asset Data from Agents button.

ServerView Update Management 261

8 Troubleshooting add job failed

Job initialization error cleanup failed

Job cannot be deleted flash failed

Error while updating the managed server flash timeout

Timeout during completion of the job manager timeout

Timings exceeded in Update Manager prepare update failed

Job transfer error reboot failed

Error while booting the managed server

Action l

In the Job Details dialog, click Show Logfile.

In the log file which opens, you will find a hyperlink to a zip file containing the diagnostics files for the selected job.

l

Save the zip file and send it to your Support of Fujitsu Technology

Solutions.

262 ServerView Update Management

8.1 Error messages in the Update Manager could not transfer job(s)

Job initialization error pending jobs

Job is in progress or has not been cleaned up update process aborted

Update process was aborted because the CMS was booted

Action l

Execute the CLEANUP function (see

"Cleanup Wizard" on page 79

).

l

Copy the errored job and restart it.

boot timeout

Timeout during boot process timeout wait for boot inactive

Error while booting the update agent

Action l

Check the boot sequence in the BIOS and correct it if necessary.

In the BIOS setup, LAN/PXE must be the first entry in the boot sequence.

l

Then restart the managed server.

agent offline

Update agent not found

Action l

Rectify any connection problems.

l

If this does not help, reinstall the update agent.

ServerView Update Management 263

8 Troubleshooting

Flash Cancelled by User

User aborted Flash Abort dialog with Cancel

Action l

Restart the update (via Create Job or Copy Job) after consulting the user of the updating server.

Applies: o Managed server with operating system Windows o GlobalFlash Agent Win <=V4.71.xx configured with Flash Abort dialog o User was logged in to the console of the managed server and aborted the Flash Abort dialog with Cancel jobs on same server not accepted: ”<jobname>” is active

A previously started job is already running on the server

Action l

Check Job Details tab for running jobs relating to this server.

l

Wait until the running job has finished before starting a new job.

Previous job for this server was unexpectedly interrupted

Action l

Execute a manual cleanup (Server Details tab > select the server > click Cleanup).

l

If the cleanup job produces the same error as the update job, manually do the following on the management station: o Change to directory …\ServerView\ServerView Serv-

ices\scripts\ServerView\OnlineUpdate.

o Check the existence and content of the file <server>.lck.

o If the <jobname> indicated in the error message is mentioned in the file <server>.lck, delete this file.

264 ServerView Update Management

8.1 Error messages in the Update Manager job canceled by second failover

Error due to multiple switching of the high availability Cluster

Action l

Execute Cleanup.

l

Copy the job and restart it.

ERROR_DC_DATA

Rescanning error caused by Inventory Task

Action l

Within applet Inventory Manager > tab Manage Diagnostics, check the inventory log-file.

o Select the corresponding server name in the tree view.

o In the table, select the task Once Immediately with Descrip-

tion = Inventory Data.

o Select Log: Select the corresponding date.

The content of the selected log file will be shown in the output field below.

o Check the DB Status l

If following values for DB Status are reported the Inventory was created successful but Inventory contains converted data.

o Data Status = Incomplete o Message = Non-Ascii data converted

ServerView Update Management 265

8 Troubleshooting

8.2

Error messages in the Download Manager

If the Download Service has stopped working due to missing credentials or other reasons the following will occur: l

Scheduled download tasks will not be started l

Once immediate tasks will remain in the status running

All defined tasks will be executed automatically after the ServerView Download Service is started again.

For trouble shooting, please, see

"Error messages in the Configuration Wizard" on page 270 .

Below is an overview of the error messages displayed in the Error column on the LogFiles tab (see

"Log Files Tab" on page 165

).

For each message there is a description of the action you can take to eliminate the error.

Server not in database

The server of this task is not in the database.

Download action is not started, logging file is not created.

Server not manageable

The server of this task is not manageable.

Download action is not started, logging file is not created.

Unsupported server

The download task is not supported for the selected server type.

Download action is not started, logging file is not created.

266 ServerView Update Management

8.2 Error messages in the Download Manager

No supported and manageable server in group

The group of servers that was assigned for the download task does not contain supported manageable servers.

Download action is not started, logging file is not created.

Task aborted

The download task is aborted.

Logging file may not be created.

Task aborted due to timeout

The download task is aborted due to a timeout.

Task time not determined

The task time cannot be determined.

Download action is not started, logging file is not created.

Task time not in future

The task is not started because the task time defined is not in the future.

Logging file is not created.

Task not started

The task cannot be started .

Logging file is not created.

Another task for this server already started

Another task is currently running a download for the server.

Logging file is not created.

Task settings invalid

The task cannot be started because the task settings are invalid.

Logging file is not created.

ServerView Update Management 267

8 Troubleshooting

Initialization error

The download action could not be started successfully.

Logging file is not created.

Possible reason: missing access permissions in the file system (for creating/removing file or directory in workdir or repository directory).

Download error

The file download from the web server failed.

Uncompression error

The uncompression of the downloaded files failed.

Network problems

The download from the web server failed due to network problems.

Update check not started

The update check failed to start.

Unsupported Server Model

The server model is not supported.

No/Illegal Agent

Missing or illegal update agent on the managed node.

Missing Inventory

The inventory is missing.

1. Start the Inventory Manager.

2. Click the Server List tab.

3. Check the Data State column for this server.

If the Data State is not OK, recollect the inventory for this server.

4. Select the server on the tab.

5. Click Recollect Asset Data from Agents.

If the Data State is still not OK:

268 ServerView Update Management

8.2 Error messages in the Download Manager

6. Check the ServerView agents on the server.

Remote Access to Repository failed

Remote access to the repository failed.

Update Check Failed

The update check failed.

ServerView Update Management 269

8 Troubleshooting

8.3

Error messages in the Configuration Wizard

The following error message can occur after activating the configuration task:

Configuration task has not been started on Central Management Station. Please, check if ServerView Download Service is stopped and restart the service. For more details, check system event log messages with source 'ServerView Update Manager'. It may be that Server-

View Download Service has no credentials for accessing database

ServerViewDB.

Troubleshooting on Windows CMS:

1. Look for entries in the event viewer:

Windows logs > Application with source ServerView Update Man-

ager and MSSQL$SQLSERVERVIEW

2. If there are entries containing messages like

Login failed for user '…….'. [CLIENT: <local machine>] or

Application=DownloadService

Function=resetRepositoryState resetRepositoryState: am_openDB failed, errMsg=[Microsoft][SQL

Native Client][SQL Server]Login failed for user '……..'.

then the ServerView Download Service has no credentials for accessing the database ServerViewDB.

In this case: l

Stop the ServerView Download Service.

l

Modify the credentials for logon user for the ServerView Download

Service as described in section Update Management Logon in

"Prerequisites on the Central Management Station (CMS)" on page

16 .

270 ServerView Update Management

8.3 Error messages in the Configuration Wizard l

Check via the Task Manager if the DownloadServer.exe process is still running . The process retries several times to connect to the database and it may take up to 15 minutes until it gives up.

l

Stop DownloadServer.exe via the Task Manager or wait until it stops running.

l

Restart the ServerView Download Service using the new credentials.

3. In other error situations: l

Restart the ServerView Download Service.

Troubleshooting on Linux CMS:

Look for error entries under /var/log/messages with source ServerView

Update Manager and restart the ServerView Download Server.

Linux Mgmt.Station using Repository on Network Drive

Error situation with ntfs filesystems mounted with type cifs

(Samba, occurred with SLES11 SP1, RHEL6)

Samba-mount might use a 64-bit-file-pointer depending on kernel-version/Samba-version/size of file systems on Linux. This might force problems with our 32-bit-applets.

The following error can occur during setting values with Configuration Wiz-

ard > Use existing Repository > Repository on Network Drive although content of Repository is correct:

Error Remote path <value> does not contain repository

Workaround:

Use additional option

-o noserverino for mounting the network drive.

ServerView Update Management 271

8 Troubleshooting

Management Station with OS=RHEL6, using local DVD drive for initializing repository from DVD

If you want to initialize your repository from DVD this may fail because you do not have the right permissions for reading the DVD.

The mount point itself and the directories above must have read access for user svuser.

When you have inserted the DVD into the local DVD drive the automounter will mount it automatically to /media/<DVD volume>.

l

Check the permissions of this directory.

If you have read permissions for user root only l

Umount the DVD drive.

l

Mount DVD drive again with the command: mount -t udf -o ro,mode=555,nodev <DVD drive> <mountpoint> .

272 ServerView Update Management

8.4 Error messages in the Repository Manager

8.4

Error messages in the Repository Manager

The following error message can occur after activating an action in the Repository Manager:

Repository task has not been started on Central Management Station.

Please, check if ServerView Download Service is stopped and restart the service. For more details, check system event log messages with source 'ServerView Update Manager'. It may be that ServerView Download Service has no credentials for accessing database Server-

ViewDB.

Tasks from the Repository Manager has been executed from the ServerView

Download Service on the central management station. This error message will occur if the ServerView Download Service has stopped working. For detailed troubleshooting, see

"Error messages in the Configuration Wizard" on page 270 .

8.5

Problems with Single Sign-On

For ServerView Operations Manager since V5.0 and ServerView Update

Agent since V5.0 configured with AccountCheck.

If any of the steps to validate the manager certificate on the managed server fail (communication between requester and provider, remote connector service) the access status of the managed server will be set to restricted and authentication via logon (user/password) will be used.

ServerView Update Management 273

8 Troubleshooting

8.6

Problems with entries in the tree structure

A managed server was displayed in the tree structure of the Update Manager

/ Download Manager.

After a check run the managed server is no longer visible in the tree structure.

Possible reason

The management controller on the managed server is no longer working.

This causes

1. The inventory has the value N/A for Chassis.

This can be checked with applet Inventory Manager - Show Inven- tory.

2. The check for the supported model returns unsupported model.

The managed server is removed from the tree structure of Update Manager / Download Manager.

Solution

Repair the management controller on the managed server.

274 ServerView Update Management

8.7 Problems with components

8.7

Problems with components

Situation

BXxxx with 2 management blades.

One of these management blades is degraded.

Solution

Before you update the management blade firmware:

1. Repair the degraded management blade.

or

1. Remove the degraded management blade from Chassis.

2. Recollect the inventory of BXxxx again.

8.8

Event ID 2370 on managed node

Concerns Event ID 2370

Windows: Event Viewer

Linux: /var/log/messages

/var/log/fujitsu/ServerViewSuite/SCS/log.SVRemoteConnector

WARN: SSL sends error for the 'handshake tests'. This request will be ignored ! It might be missing encryption or problems with authentications. For more technical information see following data:

IP=<ipadr>

SOAP-ENV:Receiver

SSL_ERROR_SSL error:140890B2:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:no certificate returned

SSL_accept() failed in soap_ssl_accept()

ServerView Update Management 275

8 Troubleshooting

Event ID 2370 on managed node, caused by Update Management

Configuration requirement:

CMS: l

ServerView Update Manager Win/LX (applet of SV Operations Manager) >=V 5.0 (includes Remote Connector Service >1.06)

Managed node: l

ServerView Agent Win/LX >=V 5.0 (includes Remote Connector Service >1.06) l

ServerView Update Agent Win/LX >=V 5.0 configured with Account

Check l

Certificate of CMS ist not installed on managed node !

(=> Update Manager: Agent Access = not certified for this managed node)

To avoid Event ID 2370 on those servers:

l

Install certificate of CMS (IP Address is content of Event ID Entry) on managed node.

or l

The owner of the CMS should remove this server from applet Server-

List if not needed.

276 ServerView Update Management

8.9 Installation/Uninstallation of updateable components without using

8.9

Installation/Uninstallation of updateable components without using Update Manager

Recommendation: Use ServerView Update Manager to update updateable components.

If updateable components were updated without Update Manager, follow the instructions below to update data within the ServerView Operations Manager database (Update Manager, Inventory Manager, ...):

"drivers and add-on-products" which are contained in Primergy Support Packages (PSPs):

1. Update the registry on the managed node (concerning PSPs)

Restart ServerView Update Agent / GlobalFlash Agent (implicit Pri-

meUp -reginit is executed) or

Change to directory <inst-path>\PrimeUp\current\FSC_SCAN and call PrimeUp -reginit

2. Update the inventory on the managed node.

ServerView Agents for Windows:

Restart Agents.

3. Update the inventory on the management station (implicit check is executed)

Inventory Manager:

Recollect Asset Data from Agents.

ServerView Update Management 277

8 Troubleshooting

Firmware/BIOS

1. Update the inventory on the managed node.

Windows: ServerView Agents for Windows:

Linux:

Restart Agents.

ServerView Agents for Linux : sh /etc/init.d/SVforceVV.sh

2. Update the inventory on the management station (implicit check is executed):

Inventory Manager:

Recollect Asset Data from Agents.

SV Update Agent Win <=V4.81.02, Linux <=V4.80-07/GlobalFlash

Agent Win/Linux <=V4.71.01

1. Update the inventory on the managed node.

Windows: ServerView Agents for Windows:

Linux:

Restart Agents.

ServerView Agents for Linux : sh /etc/init.d/SVforceVV.sh

2. Update the inventory on the management station (implicit check is executed):

Inventory Manager:

Recollect Asset Data from Agents.

278 ServerView Update Management

Index

A

ASP

21

Autonomous Support Packages

21

B

Batch File Examples (CLI)

C

Call Parameters

Cancel (Command)

Cancel (Event)

Change IP Address

Change TFTP Address

Cleanup (Command)

Cleanup Wizard

Enter TFTP Address

Logon

Schedule Job

CLI

Batch Files (Examples)

Call Parameters

Cancel

Cleanup

Reboot

Result Files

Standalone

StartFlash

WaitForDone

Closing

Configuration

Download Manager

Repository Manager

Update Manager

Collections Tab

Column filter

245

245

226

236

235 ,

246

233

238

258

229

231 ,

246

220

216

208

200

132

226

236

243

124

123

235

79

82

79

83

197

Command

Cancel

Cleanup

GFCLI

Reboot

Result Files

StartFlash

WaitForDone

Command-Line Interface

Concepts

Configuration

Closing

Main Window

Opening

Setting Global Parameters

Configuration Wizard

Activate

Configurations

Download Settings

Mail Settings

Miscellaneous

Repository

Start

Configurations

Configuration Wizard

General Settings Tab

Mail Settings Tab

Proxy Settings Tab

Copy Job Wizard

Choose Server

Enter Job Name

Enter TFTP Address

LogOn

Schedule Job

Copying a Job

Create Job Wizard

Change Version

Enter Job Name

Enter TFTP Address

Logon

Schedule Job

Creating a Job

236

235

225

,

258

233

238

229

231

225

,

258

10

219

220

175

219

220

182

176

178

180

194

182

190

192

189

184

183

106

111

113

108

114

206

90

93

94

96

90

97

203

ServerView Update Management 279

Index

Creating User Defined Groups

210

D

Deleting a Job

207

Deleting a UserDefined Group

211

Display Job Information

Display Log File

207

203

Display Update Information

Download Manager

Activate Download Server

Tasks

203

214-215

173

Add Download Server Tasks

168

Assigning Servers to Task

217

Closing

Creating a New Download

Task

216

216

Deleting a Download Task

218

Dialog Boxes

168

Edit Task Settings

Editing a Download Task

171

217

Log Files Tab

Main Window

165

158

Managing Log Files

219

Monitoring Download Tasks

218

Opening

Scheduled Tasks Tab

216

163

Task Management Tab

Tree structure

Download Service

Download Tasks

160

159

214

Assigning Servers

Create

Delete

Edit

217

216

218

217

Managing Log Files

219

Monitoring Download Tasks

218

E

Editing a User Defined Group

210

Editing Updates

209

Event

Cancel

243

280

LogonError

MemoryError

ParamError

Ready

SequenceError

StartFlsh

F

Filter

Filtering column table

Flash-Protokoll

Server

G

General Settings Tab

GFCLI

196-198

196

,

198 ,

224

196

,

198 ,

224

225 ,

,

224

244

176

258

244

244

244

242

243

239

H

History

J

Job Details Tab

203

I

Icon filter

196-198 ,

224

Initial Installation of PSPs

25

Introduction

9

71

L

Log Files Tab

Logon

Server

LogOn

LogonError (Event)

165

200

76

244

M

Mail Settings Tab

178

ServerView Update Management

Index

Main Window

Configuration

Download Manager

Repository Manager

Update Manager

Management station

Update

Management Station

Restart

Shutdown

Managing Jobs

Copying a Job

Creating a Job

Deleting a Job

Display Job Information

Releasing a Job

Managing Log Files

Managing Updates

175

158

125

53

20

Configuration

Download Manager

Repository Manager

Update Manager

219

214

208

199

Managing User Defined Groups

210

Create

210

Delete

Edit

211

210

Release Updates

MemoryError (Event)

211

244

20

20

203

206

203

207

207

207

219

199

O

Online Update

Opening

Configuration

Download Manager

Repository Manager

Opening Update Manager

P

ParamError (Event)

Prerequisites

Prerequisites on Central Management Station (CMS)

36

219

216

208

199

244

12

16

Prerequisites on connection blades

14

Prerequisites on managed servers

12

Prerequisites on TFTP server

15

PRIMERGY Support Packages

21

Product Detection of PSP

Proxy Settings

23

180

PSP

PSP Details

21 ,

23 ,

25

104 ,

152

R

Re-Initializing the Repository

Ready (Event)

Reboot (Command)

Releasing a Job

Releasing Updates

Repository Manager

Closing

Collections Tab

Create Collection

Edit Collection

Edit Update's Properties

Editing Updates

Import Repository

Main Window

139 ,

146

,

142

,

148 ,

212

242

233

207

209 ,

211

208

208

132

154

156

135

209

144 ,

150

125 ,

220

Managing User Defined Groups

210

Opening

208

Re-Initializing the Repository

212

Releasing Updates

209

Tree structure

Updates tab

Resetting the Update Agent

Result Files

Results Files

Cancel

126

128

201

238

LogonError

MemoryError

ParamError

Ready

243

244

244

244

SequenceError

StartFlash

242

243

239

ServerView Update Management 281

Index

S

Scheduled Tasks Tab

SequenceError (Event)

Server Details Tab

Setting Global Parameters

StartFlash (Command)

StartFlash (Event)

Status

Update

T

Table filter

Tabs

Collections Tab

General Settings Tab

Job Details Tab

Log Files Tab

Mail Settings Tab

Proxy Settings Tab

Scheduled Tasks Tab

Server Details Tab

Task Management Tab

Update Details Tab

Updates tab

Task Management Tab

TFTP

TFTP Address

Tree structure

Download Manager

Repository Manager

Update Manager

Troubleshouting

Typographic conventions

56 ,

126

U

Update Agent

Installation on the managed

Server

197

43

43 ,

48

159

126

56

261

27

163

243

61

220

229

239

61

160

67

128

160

113

96

132

176

71

165

178

180

163

Installation on the PXE/TFTP

Server

Installation Update Agent

V4.91

Update Data

Update Details Tab

Update Information

Update Manager

Closing

Copy Job Wizard

Display Log File

51

45

Display Update Information

203

Edit Job

120

Job Details Tab

Main Window

71

53

Managing Jobs

Opening

203

199

PSP Details

104 ,

152

Resetting the Update Agent

201

41

67

203

199

200

106

203

Server Details Tab

Server Logon

Show Job Details

Show Server Details

Tree structure

Update Details

Update Details Tab

Update Procedures

Access to Update Data

Online Update

Update via TFTP Server

Update via TFTP Server

Updates tab

User Interface

UserDefined Group

Create

Delete

Edit

Releasing Updates

41

36

38

38

128

53

61

200

117

84

56

100

67

35

210

211

210

211

W

WaitForDone (Command)

231

282 ServerView Update Management

advertisement

Was this manual useful for you? Yes No
Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Related manuals

Download PDF

advertisement