Fujitsu Update Management User Guide
Fujitsu Update Management is a powerful tool that allows you to easily update the firmware and BIOS of your PRIMERGY servers. With its intuitive graphical user interface, Update Manager Express makes it easy to manage updates for multiple servers, even if they are located in different locations. Update Manager Express also supports PXE-based mass updates, so you can update a large number of servers simultaneously without having to manually install the updates on each server.
Advertisement
Advertisement
User Guide - English
FUJITSU Software ServerView Suite
Local System Update for PRIMERGY
Servers
Edition September 2021
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]
.
Documentation creation according to DIN EN ISO 9001:2015
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:2015.
cognitas. Gesellschaft für Technik-Dokumentation mbH www.cognitas.de/en/
Copyright and trademarks
Copyright 2021 FUJITSU LIMITED
All rights reserved.
Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective manufacturers.
Contents
1.2 Target groups and objectives
1.3 Documentation for the ServerView Suite
1.4 ServerView Suite link collection
2.3 Local updates for Windows systems
2.4 Local updates for Linux systems
2.5.1 Starting Update Manager Express via PXE 16
2.5.2 Step 1: Setting up the <TFTP Root>/UME_<version> directory on the PXE server (Phase 1) 17
19 2.5.3 Step 2: Setting up the data server (Phase 2)
2.5.3.1 Setting up the data server using the PXE server as TFTP server or a separate TFTP server 19
2.5.3.2 Setting up the data server using a separate HTTP server
2.5.4 Step 3: Creating the server type-specific XML control files
2.5.4.2 Calling the XML converter
2.5.4.3 Assigning the profiles
2.5.5 Step 4: Adapting the start.sh script
2.5.6 Step 5: Initiating and monitoring the PXE-based update
3.3 Creating the USB stick using Content Collector
3.4 Booting the server in Legacy mode
Local System Update for PRIMERGY Servers 3
Contents
3.5 Booting the server in UEFI mode
4.1 Starting Update Manager Express GUI
4.6.2 Extracting the log files
5 PRIMERGY Support Packages (PSP)
5.1 Current versions of PrimeUp and PSPs
5.2.2 Tree structure of a PSP repository
5.3.2 Installing PSPs using PrimeUp (overview)
5.3.2.1 Starting PSP installation
5.3.2.2 PrimeUp version handling
5.3.2.3 How PrimeUp detects the chassis ID, system board ID, and model ID of your server
5.3.2.5 How PrimeUp interacts with the Windows registry
5.3.3 Requirements for PrimeUp
5.3.4 Installing / uninstalling PrimeUp
Local System Update for PRIMERGY Servers 4
5.3.6 PrimeUp - Parameters and options
5.3.8 Evaluating the installation process
6 Autonomous Support Packages (ASP)
6.1 Current BIOS/firmware versions
6.2.3 Starting the ASP in Windows Explorer
6.2.3.1 Displaying the release notes
6.2.3.3 Starting the BIOS/firmware installation
6.2.4 Calling ASPs via the command line interface (CLI)
6.2.5 Calling an ASP via the Windows PowerShell
6.2.6.3 Firmware update with return code
6.2.6.4 Firmware update with return code (using Windows PowerShell)
Local System Update for PRIMERGY Servers
Contents
5
6.2.6.5 Keeping the contents of the ASP target directory
6.3.3 Calling ASPs via the command line interface (CLI)
6.3.5.2 Extracting ASP user data
6.3.5.3 Performing the installation in the background
6.3.5.4 Keeping the contents of the ASP target directory
6.5 Log file Setup.log (ASPs for Windows only)
Contents
Local System Update for PRIMERGY Servers 6
1 Introduction
With Update Manager Express from the ServerView Suite or by executing ASPs, you can install firmware and BIOS of the various server components on the current PRIMERGY servers.
For local system updates on PRIMERGY servers the following tools are available: l l l
ServerView Update Manager Express (GUI-based and no interaction in case of PXE)
Self-extracting and self-installing software packages, so-called Autonomous Support
Packages (ASPs)
PRIMERGY Support Packages (PSPs) and the PrimeUp installation tool
In contrast to Update Manager from the ServerView Suite, which can supply entire data centers with firmware, Update Manager Express, PrimeUp and ASPs are ideally suited for local updates of individual systems.
ASPs and PSPs are used in the ServerView Suite by all update management components
(including ServerView Update Manager and Download Manager).
An overview of which PRIMERGY servers or which server components can be installed via
ASPs is provided in the Update Manager Express data sheet.
1.1
Update Manager Express
Using Update Manager Express, you can install firmware or BIOS for the following server components: l l l l l l
LAN controller: firmware
Management controller (e.g. iRMC S4): firmware
Microcontroller: firmware
System board: BIOS
SCSI controller: firmware
Fibre Channel controller: firmware
For updating installations of BIOS and firmware it is recommended to use Update Manager
Express because it takes care of dependencies and applies updates in sequence.
Update Manager Express is started either from a booted DVD image (e.g. ServerView Update
DVD and Update DVD base) or via PXE boot.
There is the option to access Update Manager Express from anywhere in the same network not only from the local host. For this purpose you must set the UME - Open Network Mode
Local System Update for PRIMERGY Servers 7
1.2 Target groups and objectives option while creating a bootable USB stick or ISO image via ServerView Content Collector, see
"Creating the USB stick using Content Collector" on page 31
.
For installing BIOS and firmware Update Manager Express internally uses self-extracting and self-installing software packages (Autonomous Support Packages, ASPs)
To allow safe resetting in the case of errors, you should perform an appropriate backup of your system before doing any updates.
1.2
Target groups and objectives
For more recent PRIMERGY servers, this manual describes: l l
The various options for installing BIOS and firmware with the help of Update Manager
Express and ASPs.
How to install PSPs (driver software) with the help of PrimeUp (on Windows Server operating systems).
The manual is aimed at system administrators, network administrators and service specialists with a sound knowledge of hardware and software.
1.3
Documentation for the ServerView Suite
The documentation can be downloaded free of charge from the Internet. You will find the online documentation on the download area of the Fujitsu Technical Support pages.
To download the documentation, proceed as follows:
1. Open the web page https://support.ts.fujitsu.com/IndexDownload.asp?PaOpenTab=manuals .
2. Click Browse For Product . A list with product lines opens.
3. Select Software ServerView Operation . A list with products opens.
4. Select the appropriate product from the product list.
The corresponding page with the Documents tab opens.
Only for English and German Fujitsu Technical Support pages: If no tab is displayed, select OS Independent (BIOS, Firmware, etc.) under Selected operating system and then click Documents tab.
Local System Update for PRIMERGY Servers 8
1.4 ServerView Suite link collection
1.4
ServerView Suite link collection
Via the ServerView Suite link collection, Fujitsu provides you with numerous downloads and further information on the ServerView Suite and PRIMERGY servers.
Under ServerView Suite , links are offered on the following topics: l l l l l
Forum
Service Desk
Manuals
Product information
Security information l
Software downloads l
Training
Software downloads includes the following downloads: 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 ServerView Update Agent) 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 ServerView Suite.
You can retrieve the downloads free of charge.
Under PRIMERGY Server , links are offered on the following topics: l l l l
Service Desk
Manuals
Product information
Spare parts catalogue
Access to the ServerView Suite link collection
You can reach the link collection of the ServerView Suite in various ways: l
Via the following link: http://support.ts.fujitsu.com/prim_supportcd/SVSSoftware/start.html
l
Via the ServerView Suite DVD 2.
1. In the start window of the ServerView Suite DVD 2, select the option ServerView
Local System Update for PRIMERGY Servers 9
1.5 What's new
Software Products .
2. On the menu bar select Links .
This opens the start page of the ServerView Suite link collection.
1.5
What's new
This manual replaces the following online manual: "Local System Update for PRIMERGY
Servers", June 2021 edition.
The manual includes the following updates: l
In chapter "Graphical user interface" the screenshots were renewed, see
"Graphical user interface" on page 35 .
l
The Save Log File function is available in all windows of the graphical user interface.
l
A description of how to extract the saved log files is added.
l
New ASP return codes are added.
1.6
Typographic conventions
The following typographic conventions are used:
Convention Explanation
Various types of risk, namely health risks, risk of data loss and risk of damage to devices.
Additional relevant information and tips.
bold monospace monospace monospace semibold
References to names of interface elements.
System output and system elements, e.g., file names and paths inside text blocks.
Commands, system output, syntax and statements that are to be entered using the keyboard outside text blocks.
Process example for statements that are to be entered using the keyboard.
blue continuous text A link to a related topic.
purple continuous text
A link to a location you have already visited.
Table 1: Typographic conventions
Local System Update for PRIMERGY Servers 10
1.6 Typographic conventions
Convention
<abc>
[abc]
[Key]
Explanation
Variables which must be replaced with real values.
Options that can be specified (syntax).
Key on your keyboard. If you need to enter text in uppercase, the Shift key is specified, e.g.,[Shift] + [A] for an A. If you need to press two keys at the same time, this is indicated by a plus sign between the two key symbols.
For names of chapters and manuals.
Quotation marks
Table 1: Typographic conventions
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.
Local System Update for PRIMERGY Servers 11
2 Update Types
A distinction is made between offline and online update procedures: l
Offline update
Update Manager Express is started either from a booted DVD image (e.g. ServerView
Update DVD and Update DVD base) or via PXE boot. During an offline update it is only possible to update firmware or BIOS for the inserted controllers and the System Board.
The DVD ISO image on the ServerView Update DVD includes a bootable OS (CentOS).
With it a Fujitsu PRIMERGY server can be booted and BIOS or firmware updates can be installed autonomously of the disk storage system within the server. The Update DVD itself no longer contains any PSPs.
l
Online update
Update Repository Image provides System Monitor, ASPs, PrimeUp (PSPs) which are executed on a running supported operating system. During an online update you must ensure that the prerequisites required for performing the update are met (e.g. System
Monitor requires that a running released operating system with ServerView Agents running is installed.
Only online update allows you to update device drivers and ServerView Agents software.
On the other hand, some firmware updates might not be possible due to lack of operating system support.
2.1
Download Locations
Update Manager Express, ASPs and PSPs are available from the Download section for system-specific ASPs and PSPs on the Fujitsu support web site .
BIOS, firmware and drivers (and Update Manager Express) for your PRIMERGY server are available for download as follows: l
DVD base archive UPDATE_DVD_<version>.zip
(ServerView Update DVD Base) l
Update Repository Image REPOIMAGE<version>.iso
(ServerView Update
Repository Image)
You can create an ISO image from the ServerView Update DVD Base repository located in
<UpdateDVDBase>\USBStick-data . For further information, see "ServerView
Update DVD Base and ServerView Content Collector" User Guide.
Local System Update for PRIMERGY Servers 12
2.1 Download Locations l
DVD ISO image UPDATE_DVD_<version>.iso
(ServerView Update DVD)
You can update your server’s BIOS and firmware by downloading the DVD ISO image
UPDATE_DVD_<version>.iso
of the latest version, creating an Update DVD from it, and then using this for the BIOS and firmware update.
For more information, see section
"Booting the server in UEFI mode" on page 33 .
l
Latest BIOS, firmware, or drivers available for download
Also in the period between two successive editions of the ServerView Update DVD Fujitsu offers constantly updated versions of BIOS, firmware, or drivers, and ASPs for downloading at https://support.ts.fujitsu.com/ .
Therefore, if you need a BIOS, firmware, or driver version even newer than the BIOS, firmware, or driver version provided on the most recent Update DVD, check https://support.ts.fujitsu.com/ to see whether such a version exists.
Because these BIOS, firmware, or drivers are not contained on the Update DVD, you cannot use Update Manager Express to install them.
l l
For information how to install BIOS or firmware, see chapter
For information how to install drivers and software kits, see chapter
Support Packages (PSP)" on page 53
.
As an alternative for the manual download of ASPs you can use Content Collector. With the wizard of Content Collector you can select the systems and components for which the newest ASPs should be downloaded step by step. The wizard also offers download of
PSPs.
Differences between ServerView Update DVD, Update Repository and Update DVD Base
The download variants ServerView Update DVD, ServerView Update Repository Image and
ServerView Update DVD Base differ in size and other details:
Size
Format
Direct bootable
ASP / PSP repository available
ServerView
Update DVD
Update
Repository
Image
> 7 GB 15 GB
ISO
Yes
ISO
No
Yes Yes
ServerView Update DVD Base
< 1 GB
ZIP
No. The Bootable USB Update Stick or ISO image needs to be created.
No. Must be created with Content
Collector.
Table 2: Differences between ServerView Update DVD, Update Repository and Update DVD Base
Local System Update for PRIMERGY Servers 13
2.2 Supported device classes
ServerView
Update DVD
Update
Repository
Image
Yes No
ServerView Update DVD Base
Create bootable USB
Update stick or ISO image
Yes.
Table 2: Differences between ServerView Update DVD, Update Repository and Update DVD Base
2.2
Supported device classes
Update Manager Express can be used to update devices of the classes shown in the following table.
Component type iRMC firmware
BIOS
Microcontroller
SAS controller
RAID controller
LAN controller
FC controller
GPGPU (Intel)
GPGPU (NVIDIA)
Intel Infiniband
Mellanox Infiniband
HDD firmware
SSD firmware
Windows driver (PSP)
ServerView agents
MMB firmware
Switch firmware
Online Update
Windows Linux
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
Offline Update
CentOS
X
X
X
X
X
X
X
Table 3: Devices that can be updated using Update Manager Express
Local System Update for PRIMERGY Servers 14
2.3 Local updates for Windows systems
2.3
Local updates for Windows systems
On PRIMERGY servers running under Windows Server operating systems, you have the following installation options: l l l
With the PrimeUp installation tool you can install drivers for all server components jointly, or selectively for individual components (see chapter
In Windows Explorer you can start the individual ASPs by clicking the *.exe file of the relevant ASP. You then install the ASP via its GUI with the help of a wizard (see chapter
"Autonomous Support Packages (ASP)" on page 90 ).
Under the Windows input prompt you can use the commands of the ASP command line interface (CLI). You can choose to use the wizard or run the installation in the background.
For virtual machines, BIOS, firmware, or driver updates are not possible.
For PRIMERGY servers running Microsoft Hyper-V, BIOS, firmware, or driver updates are possible with restrictions.
2.4
Local updates for Linux systems
On PRIMERGY servers running under Linux operating systems, you can start the individual
ASPs via the respective self-extracting *.scexe
files (see section
).
For virtual machines, BIOS, firmware, or driver updates are not possible.
For PRIMERGY servers running Xen/KVM (1), BIOS, updates are possible with restriction: Some ASPs, BIOS ASPs in particular, are not executable on Red Hat Linux systems with Xen. A respective return code (offline update) or message (online update) is output in such cases. On the Fujitsu web server
( http://support.ts.fujitsu.com
), no Red Hat Linux operating systems with Xen are listed for the ASPs concerned.
For updating BIOS/ firmware on ESXi 5 systems, use the ServerView Update Manager
Express in offline mode.
Local System Update for PRIMERGY Servers 15
2.5 PXE-based mass update
2.5
PXE-based mass update
PXE-based update is primarily designed for huge server farms. This solution involves more prerequisites but does enable unattended and massive parallel processing.
To use the PXE-based mass update function, you have to integrate the PXE functions provided on the Update DVD into your already existing PXE environment.
2.5.1
Starting Update Manager Express via PXE
The target system to be booted must be within the reach of a PXE server and a DHCP server.
Both the PXE server and the DHCP server must be located within the same subnet as the target system.
PXE-based server update is then processed in two phases:
First phase
In the first phase, the PXE server also acts as a TFTP server: The data needed for the PXE boot itself (e.g. the bootloader) is pulled from this TFTP server.
On the PXE server, you have therefore to create the following directory structure:
<TFTP Root>/UME_<version> providing the data for the PXE boot itself.
Although the name of directory is arbitrary, it is recommended to use UME_
<version> as directory name. This will make it easy for you to mentally associate the name with the contents of the directory.
Second phase
In the second phase, the application (Update Manager Express) and the Update
Repository are pulled from a server. You have two possibilities to make the application and the Update Repository available: l
On a TFTP server.
In this case, you can either use the PXE server as TFTP server or a separate TFTP server.
In the following, the TFTP server used in the second phase of the PXE boot process is called "data TFTP server" for short.
On the data TFTP server, you have to create the following directories unter
<relative TFTP path> (e.g. Fujitsu):
- /Firmware
- /Tools
Local System Update for PRIMERGY Servers 16
2.5 PXE-based mass update l
On a HTTP server.
Starting with Update DVD version 12.20.01.00 there is a possibility to use the
HTTP protocol in the second phase of the PXE-based server update to download the OS image and update objects files much faster and reliable to the PXE booted system.
In the following, the HTTP server used in the second phase of the PXE boot process is called "data HTTP server" for short.
After the target system has been booted in PXE boot mode, the CentOS is loaded.
Finally the start.sh
script is loaded from the data server.
The required files can be copied from the Update DVD as described in the sections below.
Steps for starting Update Manager Express via PXE
1.
"Step 1: Setting up the <TFTP Root>/UME_<version> directory on the PXE server (Phase
(second phase of a PXE-based server update)
2. Setting up the data server (second phase of a PXE-based server update):
Using the PXE server as TFTP server or a separate TFTP server:
Using a separate HTTP server:
"Setting up the data server using a separate HTTP server" on page 21
3.
"Step 3: Creating the server type-specific XML control files" on page 23
4.
"Step 4: Adapting the start.sh script" on page 26
5.
"Step 5: Initiating and monitoring the PXE-based update" on page 27
Each time you use a new version of the Update DVD, you have to perform the above steps once again.
2.5.2
Step 1: Setting up the <TFTP Root>/UME_<version> directory on the
PXE server (Phase 1)
The <TFTP Root>/UME_<version> directory provides the data needed for the PXE boot itself in the first phase.
Although the name of directory is arbitrary, it is recommended to use
UME_<version> as directory name. This will make it easy for you to mentally associate the name with the contents of the directory.
Local System Update for PRIMERGY Servers 17
2.5 PXE-based mass update
PXE Boot may be started in legacy environment or in UEFI, depending on customers setup requirements. This requires different bootloaders.
UpadateDVD by default supports both of them - PXELinux from Syslinux suite, and GRUB2.
Depending on which mode the updated server runs, different configuration files are used to boot. Legacy mode PXE configuration is covered in pxelinux.cfg
folder while UEFI aware files are placed in grub.cfg
file.
In current chapter, all mentioned configuration changes related to default file in pxelinux.cfg
folder must be also done in grub.cfg
file. This is important to successfully boot pxe in UEFI mode.
Proceed as follows:
1. Copy the following files as well as the pxelinux.cfg
directory with its contents from the Tools/GENERAL/UMEpxeBoot directory on the Update DVD to the UME_
<version> directory: l
Files linux , linux.0
(bootloader), and initrd l
Directory pxelinux.cfg
with its contents
Figure 1: Directory structure on the PXE server and PXE features on the Update DVD
Usually, the boot loader (linux.0
) is the only file that must be registered via
PXE boot administration ( dhcpd.conf
). All other files can simply be copied or created.
Next step:
Proceed with step
"Step 2: Setting up the data server (Phase 2)" on page 19 .
Local System Update for PRIMERGY Servers 18
2.5 PXE-based mass update
2.5.3
Step 2: Setting up the data server (Phase 2)
2.5.3.1 Setting up the data server using the PXE server as TFTP server or a separate
TFTP server
Defining the data TFTP server by adapting the default file in pxelinux.cfg
folder
In the last line of the default ASCII file configure the following: l l l
TFTP server that is used as the data TFTP server.
Relative path name for the application files (Update Manager Express and the Update
Repository) on the data TFTP server.
Add the noFirewall parameter (optional).
Defining a separate data TFTP server
By default, the PXE server is used as the data TFTP server.
If you want to use a separate data TFTP server, you have to modify the parameter root=tftp://$tftpserver$/<relativeTFTPpath> in the last line of the default file as follows:
1. Replace the string $tftpserver$ with the IP address of the data TFTP server. The IP address must be in dotted decimal notation (e.g. 121.145.12.6).
Do not forget to delete both $-signs.
Defining the relative path name for the application files on the TFTP server
To define the relative path name for the application files, you have to modify the parameter root=tftp://$tftpserver$/<relativeTFTPpath> in the last line of the default file as follows:
1. Replace the string <relativeTFTPpath> by the path name where the application files (i.e. Update Manager Express and the Update Repository) are located on the data
TFTP server. The empty string is allowed if the root directory of the TFTP server is used as path name.
The no_supervisor parameter
Default configuration contains flag "no_supervisor". Unless the pxe boot process is run by SV
Deployment Manager, this directive must stay intact.
Local System Update for PRIMERGY Servers 19
2.5 PXE-based mass update
Adding the noFirewall parameter
Firewall configuration sometimes causes problems while executing updates in PXE mode. To disable the firewall, add the noFirewall parameter between the initrd and mac parameters in the last line of the of the default file:
Append initrd=initrd noFirewall mac=901b0e310236 root= tftp://<ip-address>/Fujitsu
Setting up the directory on the data TFTP server
Depending on the settings you have made in the default file, you create this directory on
the PXE server or on the separate data TFTP server ( "Step 1: Setting up the <TFTP
Root>/UME_<version> directory on the PXE server (Phase 1)" on page 17 ).
In both cases you can arbitrarily choose the relative path name (e.g. Fujitsu) of the target folder into which you copy the application (Update Manager Express) and the Update
Repository from the Update DVD. In the following, this path name is referred to as
<relativeTFTPpath> .
Figure 2: Directory structure on the data TFTP server and data sources on the Update DVD
In detail, proceed as follows:
1. Under <relativeTFTPpath> , create the folders Tools and Firmware .
2. Copy the complete Firmware folder from the Update DVD to the
<relativeTFTPpath>/Firmware folder.
3. Under <relativeTFTPpath>/Tools , create the folder GENERAL .
4. In the GENERAL folder, create the folders UpdateMgrExpress and lib .
Local System Update for PRIMERGY Servers 20
2.5 PXE-based mass update
5. From the Tools/GENERAL/UpdateMgrExpress folder on the Update DVD, copy the ume.py
and ume.sig
file to the
<relativeTFTFpath>/Tools/GENERAL/UpdateMgrExpress folder.
6. From the Tools/GENERAL/UMEpxeBoot folder on the Update DVD, copy the files squashfs.img
and start.sh
to the
<relativeTFTFpath>/Tools/GENERAL/UpdateMgrExpress folder.
squashfs.img
contains the adapted CentOS.
start.sh
establishes the connection for starting Update Manager Express.
Next step:
Proceed with step
"Step 3: Creating the server type-specific XML control files" on page
2.5.3.2 Setting up the data server using a separate HTTP server
Starting with Update DVD version 12.20.01.00 there is a possibility to use the HTTP protocol in the second phase of the PXE-based server update to download the OS image and update objects files much faster and reliable to the PXE booted system.
Defining the HTTP server by adapting the boot config files
In the last line of the default ASCII file configure the following: l
HTTP server that is used as the data HTTP server.
Figure 3: The content of grub.cfg
l
Relative path name for the application files (Update Manager Express and the Update
Repository) on the data HTTP server.
Figure 4: The content of pxelinux.cfg/default
Local System Update for PRIMERGY Servers 21
2.5 PXE-based mass update
Copying the application files
In detail, proceed as follows:
1. Under <relativeHTTPpath> , create the folders Tools and Firmware .
Figure 5: Directories under <relativeHTTPpath> on the HTTP server
2. Copy the complete Firmware folder from the Update DVD to the
<relativeHTTPpath>/Firmware folder.
3. Under <relativeHTTPpath>/Tools , create the folder GENERAL .
4. In the GENERAL folder, create the folders UpdateMgrExpress and lib .
5. From the Tools/GENERAL/UpdateMgrExpress folder on the Update DVD, copy the ume.py
and ume.sig
file to the
<relativeHTTPpath>/Tools/GENERAL/UpdateMgrExpress folder.
6. From the Tools/GENERAL/UMEpxeBoot folder on the Update DVD, copy the files squashfs.img
and start.sh
to the
<relativeHTTPpath>/Tools/GENERAL/UpdateMgrExpress folder.
The UMEAABBCCFFEEFF directory is the arbitrary folder of the data HTTP server used in step 3.
Next step:
Proceed with step
"Step 3: Creating the server type-specific XML control files" on page
Local System Update for PRIMERGY Servers 22
2.5 PXE-based mass update
2.5.4
Step 3: Creating the server type-specific XML control files
System-specific control is done using XML profiles. Such an XML profile may contain either generic settings applying to all PRIMERGY servers of a group or exactly one update list for a specific PRIMERGY server type.
The following steps are required to create the server type-specific XML control files:
1.
Copying additional program files from the Update DVD into an arbitrary folder on the data server .
2.
Calling the XML-Converter to create the server type-specific control profiles .
3.
Assigning the profiles to the individual server instance.
2.5.4.1 Copy additional files
Copy the following program files from the Tools/GENERAL/UMEpxeTools directory on the Update DVD into an arbitrary directory on the data server (the UMEAABBCCFFEEFF directory on the data HTTP server): l l l
XML-Converter.jar
, which allows you to create the server type-specific control file
BuildLabelFile.jar
, which is needed by the XML Converter lib/jdom-2.0.2.jar
l genericProfile.xml
(generic XML control file)
2.5.4.2 Calling the XML converter
The XML converter creates server type-specific XML control files. Each call of XML-
Converter.jar
will generate a separate UserProfile.xml
file (i.e. the profile) for the corresponding PRIMERGY type. You can use each profile for updating an arbitrary number of PRIMERGY servers of the corresponding type.
As the UserProfile.xml
will be overwritten by the next execution of the XML converter, save the UserProfile.xml
from the XML converter’s output directory into a directory of your choice.
Parameters -architecture and -operatingsystem are optional. Default values are
Not available .
1. Find out which types of PRIMERGY servers are involved in the PXE-based update.
2. For each affected PRIMERGY type, start the XML converter with the appropriate -system parameter as described below: java –jar XML-Converter.jar –F|-f|-firmware|
-firmware [...\]Firmware –nxml genericProfile.xml –system|
-s|-S Dnnnn-XXnnnSn –output|-o UserProfile.xml
[-architecture|-arch x86|x64] [-operatingsystem|-os|
-OS <operatingSystem> ]
Local System Update for PRIMERGY Servers 23
2.5 PXE-based mass update
The parameters -arch and -OS are optional (default: Not available).
Dnnnn
D number of the PRIMERGY system board type (e.g. D3249)
XXnnnSn (or XXnnnnMn)
PRIMERGY type (e.g. TX300S7, TX1310M1)
XX stands for BX, RX, or TX.
n: 0 .. 9
<operating system>
Possible values (Windows): l l
Windows Server 2008
Windows Server 2008 R2 l l
Windows Server 2012
Windows Server 2012 R2 l
Windows Server 2016
Possible values (Linux): l
RedHat 5.11
l l
RedHat 6.4
RedHat 6.5
l l l l
RedHat 6.6
RedHat 6.10
RedHat 7.0
RedHat 7.1
l l l l l l l l
RedHat 7.4
RedHat 7.5
SuSE 10.0
SuSE 11.0
SuSE 11.2
SuSE 11.3
SuSE 11.4
SuSE 12 l
SuSE 15
3. Modify the UserProfile.xml
files in order to save logging information concerning the update process.
Local System Update for PRIMERGY Servers 24
2.5 PXE-based mass update
For each UserProfile.xml
file, enter in the <postsequence> field of the
<Control Settings> container the access data of the FTP server on which the logging files are to be stored with the following command sequence:
<command>,<ip-address>,<folder>,<username>,<password>
<command>
Enter get-trace to save trace information.
Enter get-log to save logging information.
<ip address>
IP address of the FTP server
<folder>
Folder on the FTP server where the logging / trace information will be saved.
<username>
User name of the account on the FTP server.
<password>
Password for <username>
Example:
<postsequence> get-trace,172.0.0.1,UMERX600S4,Administrator,PASSWORD
</postsequence>
2.5.4.3 Assigning the profiles
In the last step you assign the created profiles to the individual PRIMERGY servers.
1. For each PRIMERGY server to be updated, create a folder UME<mac> in the root directory of the data TFTP server.
<mac>
MAC address of the PRIMERGY server. The MAC address is represented by a string containing six groups of two hexadecimal digits without separators in between (e.g.
A0B1C2D3E4F5).
2. Assign the appropriate profile to each PRIMERGY server by copying the corresponding
UserProfile.xml
into the UME<mac> folder of this server.
Next step:
Proceed with step
"Step 4: Adapting the start.sh script" on page 26 .
Local System Update for PRIMERGY Servers 25
2.5 PXE-based mass update
2.5.5
Step 4: Adapting the start.sh script
The settings in the start.sh
script apply to all systems. This means that it should be as universal as possible. To distinguish individual machines the MAC address may be used. The
MAC address is passed to the script as first argument ($1).
For more sophisticated settings (e.g. for tailoring the settings to fit each individual target system), you can configure your settings in the <postsequence> field of the <Control
Settings> container in the related XML control files ( UserProfile.xml
):
<postsequence>
{reboot | shutdown | | stay}
</postsequence>
In case both are configured, settings from UserProfile.xml
overwrite settings from start.sh
.
To control on how the updated PRIMERGY servers behave once the update has been completed, you can modify the start.sh
script.
The last command in the start.sh
script is as follows: python3.6 ume.pyz -L trace.txt -mac $1 -F tftp://$2 -D 10 -R pxe $RELPATH
Modify this command as follows:
1. Use exactly one of the following parameters to control how the target system will behave once the update has successfully completed:
-R
The -R parameter is preset in the start.sh
script.
The target system will reboot and subsequently evaluate whether additional updates are to be made (e.g. in case of firmware dependencies).
-shutdown
The target system will shutdown if -shutdown is used instead of the -R parameter.
-stay
The target system will remain in the "CentOS booted" state if -stay is used instead of the -R parameter.
Next step:
Proceed with step
"Step 5: Initiating and monitoring the PXE-based update" on page 27 .
Local System Update for PRIMERGY Servers 26
2.5 PXE-based mass update
2.5.6
Step 5: Initiating and monitoring the PXE-based update
1. To initiate the PXE-based update, press [F12] on a PXE client (i.e. a managed server that is registered at the PXE server).
You can login on any of the managed servers during the update (after CentOS has booted) as well as once the update has completed. Logging information concerning the update process is displayed on the monitor.
1. Press [ALT]+[F2] to access the second monitor.
2. On the second monitor, login with user "root" and password "ServerView" in the directory
/tmp/srcUME , you will find the Update Manager Express and all of its logging files and trace files.
3. For debugging and/or troubleshooting purposes, save the *.txt files from the
/tmp/srcUME directory.
Local System Update for PRIMERGY Servers 27
3 Bootable USB stick
For creating a bootable USB stick, you can use the Update DVD ISO image UPDATE_DVD_
<version>.iso
or a (physical) Update DVD burned from it. The USB stick is mostly a simple copy of the Update DVD. Differences can only be found in those parts which make the DVD / stick bootable. Therefore, you can use the stick and the Update DVD in the same way.
You can also use the ServerView Content Collector for initializing the Firmware repository of the USB stick. With Content Collector you can select and download the latest firmware for
PRIMERGY systems. Content Collector for the Bootable USB Update Stick is found l l on the FUJITSU Drivers & Downloads web page on the full blown Update DVD, Update DVD Base archive and on the created update stick at .\Tools\GENERAL\ContentCollector
A USB stick built on a Windows system can be used on both Windows and Linux systems.
System requirements l l
PC running a supported / released Windows or Linux operating system (e.g. Windows 8 or Windows 10).
Administrator rights on this PC.
l l
If you use Content Collector: Java Runtime Environment version 7 or higher or openJDK version 8.
Working internet connection.
USB stick requirements l
Storage capacity of 8 GB or higher l l
USB 2.0 (Recommended: USB 3.0)
The USB stick must be bootable.
As large amounts of data are to be copied to the USB stick, it is recommended to use a high speed USB stick.
Software requirements
All the software needed for creating the USB stick is contained in the DVD ISO image
UPDATE_DVD_<version>.iso
/ Update DVD. You will find the main script createUSBStick.bat
in the directory Tools\General\UMEtoStick .
Local System Update for PRIMERGY Servers 28
3.1 Preparing the USB stick
To use the script from the Update DVD, you must make the Update DVD visible in the file system of your PC.
You can achieve this as follows: l l
If you have burned the DVD ISO image UPDATE_DVD_<version>.iso
on a physical
DVD, insert this media and mount it.
If only the DVD ISO image UPDATE_DVD_<version>.iso
is available, the ISO image can only be mounted in Windows Explorer from Windows 7 / Windows Server 2012 and later. . However, there is a wide range of third-party tools you can use for this purpose, regardless of the version of Windows.
3.1
Preparing the USB stick
You need to prepare the USB stick only once. If you have already formatted the USB stick according to requirements no further preparation is necessary.
Before you can start the createUSBStick.bat
script, you first have to prepare the USB stick to meet the following requirements: l l l
The USB stick is empty.
The USB stick is formatted as a normal disk with a partition table.
On the USB stick, there is exactly one primary partition formatted as FAT32 file system.
FAT32 is chosen because both Windows and Linux can handle this file system type.
To prepare your USB stick, proceed as follows:
1. Connect the USB stick to your PC.
2. In the command line start the diskpart tool with administrator rights (cmd.exe).
In contrast to the usual notation, drive letters in diskpart are not followed by a ":".
Example: In diskpart , the notation "D" is used instead of "D:".
Enter the following diskpart commands: a. Enter list disk to get a list of all disks.
Identify the line representing your USB stick.
Normally, you can identify the line representing your USB stick via the Size field of the line. Otherwise, compare the output lists the list disks command provides when the USB stick is connected and when the USB stick disconnected.
Ensure to correctly identify the USB stick because all data will be removed from the selected device.
b. Enter select disk <No> to change to your USB stick.
For <No>, enter the number displayed in the first field of your selected line.
c. Enter clean to remove all data and the complete partition structure from the stick.
Local System Update for PRIMERGY Servers 29
3.2 Creating the USB stick d. Enter create partition primary to create the one partition required on the stick. A drive letter will be automatically assigned to this partition.
e. Enter list partition to detect the partition number assigned by the create partition primary command.
There must be only one single line in the output list of the list partition command.
f. Enter select partition partition <No> to define the partition as the current partition. <No> is the number displayed in the output list of the list partition command.
g. Enter detail partition to display all details of the new partition. The drive letter can be seen in the second output field.
h. Enter exit to exit the diskpart tool.
The new partition is in raw format, i.e. the partition does not yet have a file system set up. As the partition cannot be used in this state, it must be formatted into a
FAT32 file system as described below.
3. Enter the format command to format the new drive into a FAT32 file system:
In the following, for drive letters the usual notation (e.g. "D:") is mandatory.
format <drive letter> /FS:FAT32 /Q
4. Answer any questions asked by the program with pressing the [Enter] key on your keyboard.
3.2
Creating the USB stick
After having prepared the USB stick as described above you can run the createUSBStick.bat
script that copies contents from the Update DVD to the USB stick.
You need to know the drive letter the system uses to refer to the USB stick. You have already got the drive letter in the preparation phase. This drive letter is still valid if the USB stick has not been removed since then.
Proceed as follows:
1. Change to the Tools/GENERAL/UMEtoStick directory on the Update DVD.
2. Start the createUSBStick.bat
script with administrative rights: createUSBStick.bat <drive letter>
(e.g
createUSBStick.bat d: )
The execution of the script will take some time because the files are copied from the
Update DVD to the USB stick. To keep you updated, the script outputs information in the following order:
Local System Update for PRIMERGY Servers 30
3.3 Creating the USB stick using Content Collector l l
Formatting information
Names of the files being copied to the USB stick
Normally, the names are displayed one after another without delay. In the case of large files, however, it may take some time before the name of the next file is displayed.
l
The following message is shown once the script has successfully completed:
USBStick sucessfully created
If this message is not displayed, the execution of the createUSBStick.bat
script has failed. Look at the output which may contain the problem description. To locate the problem, you can additionally investigate the createUSBStick.bat
, which is a pure text file.
3. After the createUSBStick.bat
script has successfully completed, disconnect the
USB stick from your PC using the "safe hardware remove" function.
3.3
Creating the USB stick using Content Collector
The following description is given in short form. For further information see the "ServerView
Update DVD Base and ServerView Content Collector" manual stored on the Fujitsu Technical
Support pages.
There is the option to access Update Manager Express from anywhere in the same network not only from the local host. For this purpose you must set the UME - Open
Network Mode option while creating a bootable USB stick or ISO image via
ServerView Content Collector. For further information see the "ServerView Update DVD
Base and ServerView Content Collector" manual stored on the Fujitsu Technical
Support pages.
1. On the FUJITSU Downloads page, select a PRIMERGY server system and an operating system.
2. Open the section Server Management Software / ServerView Content Collector for
Bootable USB Update Stick and download the latest version.
3. Extract the downloaded archive to your local hard disk.
4. Run the application ContentCollector.exe
with administrative privileges.
5. Define a Proxy server and the appropriate port if necessary.
6. Select the location where the update files are saved to (local hard disk, already created update stick or network share are possible).
7. Select the PRIMERGY server system(s) that you intend to update.
8. Select the component(s) that need to be updated.
9. Download the selected updates.
Local System Update for PRIMERGY Servers 31
3.4 Booting the server in Legacy mode
10. After having downloaded all updates you need, copy the files to the update stick.
The main directory Firmware should be located in the root of the update stick.
3.4
Booting the server in Legacy mode
If the server has been booted from the Update DVD or USB stick you cannot install PSPs with
Update Manager Express.
If your system does not reboot automatically after BIOS or firmware installation is completed, terminate Update Manager Express explicitly to reboot your system.
To start Update Manager Express from the (physical) Update DVD or from a USB stick, proceed as follows:
1. Switch on the server.
2. Insert the current Update DVD in the server’s DVD-ROM drive or connect the USB stick to your server.
3. Reboot the server, e.g. by pressing the reset button on the front or switching the server off and then on again after a few seconds.
4. Once the server is started, press [F2] (BIOS setup) or [F12] (Boot Menu).
5. In the BIOS setup / in the boot menu, change the boot sequence to "Boot from CD" /
"Booting from USB device".
6. While booting the server from the Update DVD / USB stick, you will be asked to select your preferred GUI language.
Local System Update for PRIMERGY Servers 32
3.5 Booting the server in UEFI mode
Figure 6: Booting Update Manager Express from Update DVD/USB stick: Select Language
7. Select your preferred GUI language.
The Update Manager Express opens the main window (for more information see section
).
In this case Update Manager Express can only update BIOS or firmware versions that are provided on the Update DVD / USB stick.
3.5
Booting the server in UEFI mode
You can run the Update DVD / USB stick in UEFI mode beginning from Update DVD 11.15.07
version.
You can enable UEFI support:
1. During the boot process press [F2].
2. Open the BIOS menu.
3. Select the Advanced tab.
4. Select CSM Configuration .
5. Set the Launch CSM field to enabled .
6. Set the BOOT option filter to UEFI only.
7. Save your settings.
8. Reboot the system.
Local System Update for PRIMERGY Servers 33
3.5 Booting the server in UEFI mode
9. Press [F12].
10. Select UEFI DVD / USB as the boot device.
The only difference between Legacy and UEFI modes for booting from DVD / USB stick is the bootloader output.
Figure 7: Bootloader output by booting from DVD / USB stick in UEFI mode
It has the same functions as in Legacy mode.
Local System Update for PRIMERGY Servers 34
4 Graphical user interface
Via the graphical user interface (GUI) of Update Manager Express you can install BIOS and firmware for all server components jointly or selectively for individual components.
BIOS and firmware are installed locally on the server on which Update Manager Express is started.
Update Manager Express is started either from a booted DVD image (e.g. ServerView Update
DVD and Update DVD base) or via PXE boot.
Update modes
There are different update modes within the Update Manager Express GUI. In Quick Mode and Normal Mode, Update Manager Express automatically identifies all server components for which newer versions of BIOS or firmware images exist in the repository.
l l l
In Quick Mode you start an update for all displayed components.
In Normal Mode you update selected components.
In Expert Mode you can update a single component.
It may be that Update Manager Express does not display all available updates within the first run. In this case, additional updates will be displayed in additional runs. It may therefore be necessary to start Update Manager Express several times to ensure that all available updates are installed.
4.1
Starting Update Manager Express GUI
Update Manager Express is started either from a booted DVD image (e.g. ServerView Update
DVD and Update DVD base) or via PXE boot.
1. Insert the Update DVD in the drive of your PRIMERGY server or connect the USB stick to your PRIMERGY server.
When the server is booted from the Update DVD, ServerView Update Manager
Express starts automatically.
Note the settings for booting in the BIOS menu for the PRIMERGY server.
Remember to reset certain boot settings after booting for security reasons.
Local System Update for PRIMERGY Servers 35
4.1 Starting Update Manager Express GUI
Figure 8: Update Manager Express main window opens
For more information on starting the Update Manager Express via PXE, see section
Update Manager Express via PXE" on page 16 .
Login window (if 'UME - Open Network Mode' set)
There is also the option to access Update Manager Express from anywhere in the same network not only from the local host. For this purpose you must set the UME - Open
Network Mode option while creating a bootable USB stick or ISO image via ServerView
Content Collector, see
"Creating the USB stick using Content Collector" on page 31 .
If ServerView Update Manager Express is started from a bootable USB stick or an ISO image created with the UME - Open Network Mode option set, a login window will be displayed:
Local System Update for PRIMERGY Servers 36
4.1 Starting Update Manager Express GUI
Figure 9: Update Manager Express - login window (if 'UME - Open Network Mode' set)
You have to enter the credentials.
You cannot change the credentials in ServerView Update Manager Express itself. You can only change the credentials via the ServerView Content Collector.
Default credentials are:
Username root
Password
ServerView
For further information see the "ServerView Update DVD Base and ServerView Content
Collector" manual stored on the Fujitsu Technical Support pages.
Local System Update for PRIMERGY Servers 37
4.2
Main Window
Update Manager Express opens its GUI with the main window.
4.2 Main Window
Figure 10: Update Manager Express - main window
From top to bottom the main window consists of: l l l l
The title bars
Several tabs to set the parameters for different install modes
The Exit button, that closes the program
The information bar
The System Type tab is displayed by default. It displays information about the server
Update Manager Express is currently running on.
Localization
The languages supported for using the Update Manager Express GUI are English and
Japanese.
In the line of tabs you find the Language item on the far right.
Local System Update for PRIMERGY Servers 38
4.3 Quick mode tab
To change the language for using the GUI:
1. Click on the Language item.
2. A selection list of available GUI languages will be displayed.
3. In the selection list click on the desired language.
4.3
Quick mode tab
In Quick Mode Update Manager Express automatically identifies all server components for which newer versions of BIOS or firmware images exist in the repository. These information is displayed in a table together with the BIOS or firmware versions to be installed.
Figure 11: Quick Mode tab
The columns of the table have the following meaning: icon
Expands the table entry for this component.
Selected
If checked, the related entry is selected for an update.
Local System Update for PRIMERGY Servers 39
4.3 Quick mode tab
Severity
Characterizes the necessity of the update by icon.
Additional information is displayed when the mouse pointer is moved over the icon.
Leaf
Identification of a component and information about its driver in the Updated ISO image.
Status
Update status, this column is displayed once the update is started.
The Status field gives you the following information on the updates of the individual components:
Entry waiting updating done-ok reboot done-error
Meaning
Waiting to be updated.
Update is running.
Update successfully completed.
Update successfully completed. The system must be explicitly restarted.
Update failed.
Table 4: Status of the updates
Columns of the expanded table
The table entry for a component can be expanded by clicking on the icon. The table entry for a component is automatically expanded when an update is started for this component.
Installed Version
Version of the currently installed driver.
Installation Time
Estimated installation time in minutes.
Legal Documents
Opens a new tab with legal documents.
Release Notes
Opens a new tab with release notes.
Progress:
Informs about the progress of the update for this component.
Update Logs:
Displays log files of the update process as soon as an update is started.
Local System Update for PRIMERGY Servers 40
4.4 Normal Mode tab
Save Log File
Opens the Choose Folder dialog box in which you can select a folder to save the log files, see
"Saving the log file" on page 51 .
Reboot
Starts a system reboot. This button is only enabled after a successful update.
Start
Starts the BIOS/firmware/driver update for all displayed components.
Abort
Aborts the installation process. This button is only enabled after the update has begun.
When you click this button the installation process currently running on the relevant server component is completed first, but no further update installations are performed.
Updating in Quick Mode
In Quick Mode you update all displayed components automatically. To update all relevant components in a single run:
1. Start the Update Manager Express GUI on the local server.
2. Open the Quick Mode tab.
3. Check the components and their Severity to be updated.
4. Click Start .
When an update is started for a component the table entry for this component is automatically expanded.
5. The installation starts and the Abort button becomes activated.
The Status field gives you information on the updates of the individual components.
4.4
Normal Mode tab
In the Normal Mode tab, Update Manager Express shows a table with the automatically identified server components together with the BIOS or firmware versions to be installed.
Clicking an entry in the Version column displays the associated release information.
Unlike in Quick Mode, in Normal Mode you can choose the server components whose BIOS or firmware you want to update, by checking the options in front of the relevant component.
Local System Update for PRIMERGY Servers 41
4.4 Normal Mode tab
Figure 12: Normal Mode tab
The columns of the table have the following meaning: icon
Expands the table entry for this component.
Selected
If checked, the related entry is selected for an update.
Severity
Characterizes the necessity of the update by icon.
Additional information is displayed when the mouse pointer is moved over the icon.
Leaf
Identification of a component and information about its driver in the Updated ISO image.
Local System Update for PRIMERGY Servers 42
4.4 Normal Mode tab
Status
Update status, this column is displayed once the update is started.
The Status field gives you the following information on the updates of the individual components:
Entry waiting updating done-ok reboot done-error
Meaning
Waiting to be updated.
Update is running.
Update successfully completed.
Update successfully completed. The system must be explicitly restarted.
Update failed.
Table 5: Status of the updates
Columns of the expanded table
The table entry for a component can be expanded by clicking on the icon. The table entry for a component is automatically expanded when an update is started for this component.
Installed Version
Version of the currently installed driver.
Installation Time
Estimated installation time in minutes.
Legal Documents
Opens a new tab with legal documents.
Release Notes
Opens a new tab with release notes.
Progress:
Informs about the progress of the update for this component.
Update Logs:
Displays log files of the update process as soon as an update is started.
Save Log File
Opens the Choose Folder dialog box in which you can select a folder to save the log files, see
"Saving the log file" on page 51 .
Reboot
Starts a system reboot. This button is only enabled after a successful update.
Start
Starts the BIOS/firmware/driver update for all displayed components.
Local System Update for PRIMERGY Servers 43
4.5 Expert Mode tab
Abort
Aborts the installation process. This button is only enabled after the update has begun.
When you click this button the installation process currently running on the relevant server component is completed first, but no further update installations are performed.
Updating in Normal Mode
In Normal Mode you only update the selected components.
1. Start the Update Manager Express GUI on the local server.
2. Open the Normal Mode tab.
3. Select the components to be updated by checking the option at the beginning of the entry.
4. Click Start .
When an update is started for a component the table entry for this component is automatically expanded.
5. The installation starts and the Abort button becomes activated.
The Status field gives you information on the updates of the individual components.
4.5
Expert Mode tab
The Expert Mode allows you to update BIOS or firmware.
Expert Mode should only be used by experts who have experience with BIOS or firmware installation and know exactly the current hardware configuration (including installed BIOS or firmware versions) of your server.
In Expert Mode Update Manager Express does not create a list of the BIOS or firmware installations to be performed. Instead, you must select and start each BIOS or firmware image individually in the Expert Mode tab.
In Expert Mode you can only perform the BIOS or firmware installation on one server component per installation process.
Local System Update for PRIMERGY Servers 44
4.5 Expert Mode tab
Figure 13: Expert Mode tab
The Expert Mode tab contains a navigation area and a display area.
The navigation area on the left shows entries for the various categories of server components: LanController, ManagementController, ScsiController, FibreChannelController, and SystemBoard.
A double-click on an entry (e.g. SystemBoard) in the navigation area expands a list of all
BIOS or firmware components of the corresponding category installed on your server and enables the Start button.
If you select an individual component in the navigation area one or more BIOS or firmware images are offered for installation in the display area.
Local System Update for PRIMERGY Servers 45
4.5 Expert Mode tab
Figure 14: Expert Mode tab
The table for displaying the images to be installed has the following columns: icon
Clicking on this icon expands the table entry for this component.
Selected
If checked, the related entry is selected for an update.
Leaf
Identification of a component and information about its driver in the Updated ISO image.
Local System Update for PRIMERGY Servers 46
4.5 Expert Mode tab
Status
Update status, this column is displayed once the update is started.
The Status field gives you the following information on the updates of the individual components:
Entry waiting updating done-ok reboot done-error
Meaning
Waiting to be updated.
Update is running.
Update successfully completed.
Update successfully completed. The system must be explicitly restarted.
Update failed.
Table 6: Status of the updates
Columns of the expanded table
The table entry for a component can be expanded by clicking on the icon. The table entry for a component is automatically expanded when an update is started for this component.
Legal Documents
Opens a new tab with legal documents.
Release Notes
Opens a new tab with release notes.
Progress:
Informs about the progress of the update for this component.
Update Logs:
Displays log files of the update process as soon as an update is started.
Save Log File
Opens the Choose Folder dialog box in which you can select a folder to save the log files, see
"Saving the log file" on page 51 .
Reboot
Starts a system reboot. This button is only enabled after a successful update.
Local System Update for PRIMERGY Servers 47
4.5 Expert Mode tab
Start
Starts the installation of the selected ISO image of the selected component. Update
Manager Express performs the installation in the foreground and shows the status.
During the installation, Update Manager Express performs compatibility and dependency checks and in the case of discrepancies, aborts the installation process with an error message.
Compatibility/dependency checks normally comprise checking for example the system
ID, chassis ID/board ID, operating system, availability of hardware and dependencies between installed and offered firmware versions.
Updating in Expert Mode
In Expert Mode you update only selected ISO images of selected components.
1. Start the Update Manager Express GUI on the local server.
2. Open the Expert Mode tab.
3. In the navigation area click the category you want to update (e.g. SystemBoard).
This displays all components of this category - distinguished by server and system board
- for which the repository contains firmware images.
4. Click the component which is installed on your server.
In the display area of the Expert Mode tab, one or more BIOS or firmware images are offered for installation.
5. Clicking on the icon expands the table for this component.
In the Release Notes column click the Go to notes link to display the associated release information.
6. Select the BIOS or firmware image you want to use for the installation by checking its checkbox at the beginning of its entry.
7. Click Start to start the installation.
When an update is started for a component the table entry for this component is automatically expanded.
Local System Update for PRIMERGY Servers 48
4.6 Maintenance tab
4.6
Maintenance tab
The Maintenance tab allows you to run the PrimeCollect tool, which collects and stores information on the hardware and software of your PRIMERGY server. This can be useful for the diagnosis of server problems.
Figure 15: Maintenance tab
Progress: ...%
Progress bar indicating the data collection progress.
Messages:
Displays messages output by the PrimeCollect tool.
For example, messages are displayed in this field while the PrimeCollect tool is running.
Local System Update for PRIMERGY Servers 49
4.6 Maintenance tab
Figure 16: Messages displayed while the PrimeCollect tool is running
Save Log File
Opens the Choose Folder dialog box in which you can select a folder to save the log files, see
"Saving the log file" on page 51 .
Collect Data
Starts the PrimeCollect tool
Abort
Aborts the PrimeCollect tool.
Local System Update for PRIMERGY Servers 50
4.6.1
Saving the log file
When you click Save Log File the Choose Folder dialog box opens:
4.6 Maintenance tab
Figure 17: Choose Folder dialog box
New
Creates a new folder in which you can save the log file.
Show Hidden Folders
Displays hidden folders.
Sort By: Name/Date
Sorts the folders by name or by date. Clicking on the Sort By: item displays a selection list. Click on the Sort By: Name or the Sort By: Date option. Clicking again on the chosen option changes the order.
To save the log file proceed as follows:
1. Select the folder in which you want to save the log files.
2. Click Select folder .
Saving of the log files is started.
After successfully saving the logs the following message is displayed.
Local System Update for PRIMERGY Servers 51
4.6 Maintenance tab
Figure 18: Log file saved
In the selected folder a new sub folder will be created. Its name is a stamp of the current date and time. Inside all related log files including PrimeCollect archives (if run beforehand) are saved.
4.6.2
Extracting the log files
You can use different methods to extract the log files:
Use an USB stick:
1. Prepare an USB stick as described in
"Preparing the USB stick" on page 29 . For easy
identification the usage of a FAT file system label is recommended.
2. Insert the USB stick into the machine from which logs will be collected or mount the USB stick to this machine using the Virtual Media feature of the iRMC . The USB stick will be mounted on the /media/<fs-label><counter> folder. If no file system label was used, the default path name is /media/Fujitsu0 .
Use a temporary folder:
1. Save the log files inside the /tmp , see
"Saving the log file" on page 51
.
2. Then connect to the machine using an SCP client (for example WinSCP) with the following credentials:
User name : root
Password : ServerView; you can change the default password using the Update DVD base.
3. Navigate to the tmp folder.
4. Download the folder created inside /tmp .
Local System Update for PRIMERGY Servers 52
5 PRIMERGY Support Packages (PSP)
A PRIMERGY Support Package (referred to here as PSP for short) is the basic element for installing or updating drivers and software kits on your PRIMERGY server running a Windows
Server operating system. PSPs are processed by the PrimeUp software tool, which you use to install or update drivers and software kits on the server components.
For installing PSPs on your PRIMERGY server, you can also use ServerView Agents System
Monitor.
A PSP contains several packages, each of which incorporates a driver or software kit.
This chapter provides information on the following topics: l l l l l l
Current versions of PrimeUp and PSPs
Installing PSPs using the PrimeUp installation tool
To allow safe resetting in the case of errors, you should perform an appropriate backup of your system before doing any updates.
5.1
Current versions of PrimeUp and PSPs
The current versions of PrimeUp and the PSPs are available for download as follows:
ISO image REPOIMAGE_<version>.iso (Update Repository Image)
You can update your server’s BIOS/firmware/drivers as follows:
1. Visit http://support.ts.fujitsu.com/Download/ .
2. Select the appropriate PRIMERGY server type and model.
3. Under Select your operating system , select OS Independent (BIOS, Firmware, etc.) .
4. Under Server Management Software ServerView Update Repository Image , select
ServerView Update Repository Image .
5. Download the DVD ISO image REPOIMAGE_<version>.iso
of the latest version from: http://support.ts.fujitsu.com/Download/ and create an Update DVD from it.
6. Use the Update DVD for the BIOS/firmware/driver update.
Local System Update for PRIMERGY Servers 53
5.2 PSPs (overview)
You will find PrimeUp and PSPs under Firmware/Tools (PrimeUp) and
Firmware/PrimSupportPack-Win (PSPs).
For details, see section
"Booting the server in Legacy mode" on page 32 .
An overview of the components and server models supported by the currently released PSPs is provided in the readme file for PSPs, which is also provided on the
Update Repository Image.
5.2
PSPs (overview)
A PSP consists of a zip archive containing the software, driver, installation tools and an XML description file. You can use a PSP to install the driver of a certain hardware component
(e.g. Intel LAN controller) or to install software products (e.g. Intel Proset, ServerView RAID,
ServerView Agents). PSPs are processed by the PrimeUp installation tool (see section
"PrimeUp installation tool" on page 58
).
PSPs are used in the ServerView Suite by all update management components
(including ServerView Update Manager).
5.2.1
Structure of a PSP
Each PSP consists of two basic components: l l
PSP description file (XML file)
ZIP archive containing the directory structure containing the driver/software kit, installation tools.
An example of a PSP for ServerView Agents software on the Update DVD is shown in figure
"Example of a repository view and the PSP contained " on page 56
.
PSPs may contain a MainPackage
A MainPackage defines global cross-package dependencies that are relevant for all subsequent component-specific packages. Cross-package dependencies may include hardware/software dependencies concerning chassis ID, systemboard ID, model ID, PCI ID, firmware version, operating system version, and required software and software version.
Therefore, the cross-component dependencies are automatically checked to be fulfilled before any of the subsequent component-specific packages will be checked e.g. for an installed incompatible (rivaling) software package.
Local System Update for PRIMERGY Servers 54
5.2 PSPs (overview)
A main package is not necessarily available. If no main package is available, PrimeUp as of version 1.17.03 automatically selects "PRIMERGY" and "PRIMEQUEST" as default model-IDs. Older of PrimeUp versions ignore main packages completely.
PSPs contain component-specific packages
A PSP provides a set of packages, each referring to a corresponding section in the PSP description file (see below). A package represents the actual product (driver or software kit) that is to be installed (e.g. driver for Windows Server 2016). Within the same PSP the individual packages contain the different versions of the same type of driver or software kit.
PSP description file (XML file)
The description file (XML file) is the basic component of the update mechanism used by
PrimeUp for updating drivers and software kits.
For each PSP the corresponding XML file contains the following information: l l l l l l l
Purpose of the PSP (i.e. PSP name), e.g.
PCI_Express_Driver K for Intel(R) Gigabit Ethernet LAN Adapter 82578DM
Current PSP version and its contents, e.g.
Version 3.00.01: Drv 11.2.19.0 (SW-Kit 14.7), W2K[3|8](x64)(R2)
In many cases: Installation priority
Description of the MainPackage, if available, of the PSP. The description provides information on overall cross-package dependencies between the individual componentspecific packages.
Description of all component-specific packages contained in the PSP. For every component-specific package, information is provided on the package version and on hardware/software dependencies such as model ID, chassis ID, system board ID, PCI ID, firmware version, operating system version, and required software and software version.
Checking instructions that evaluate hardware and software dependencies and check the availability of the required hardware and software.
Control instructions that control the processing of the PSP by PrimeUp.
This information allows PrimeUp to perform the following tasks: l l l
Evaluate whether the hardware (model, chassis and system board, or PCI ID) for which the driver is valid is present in the system,
Check hardware / software requirements and dependencies (e.g. Windows version), and,
If applicable, perform the installation, update or removal of the driver or software kit.
PSP ZIP archive
The PSP ZIP archive includes a directory structure containing all files that are needed for installing the PSP, i.e. driver/software kit, installation tools.
Local System Update for PRIMERGY Servers 55
5.2 PSPs (overview)
Release notes
The relnotes.txt
file contains the release notes on the PSP.
5.2.2
Tree structure of a PSP repository
A PSP is provided in a directory that has the name of the PSP. Different PSP versions (if available) are located in the corresponding version-specific subdirectories. Each PSP folder of each of the version-specific subdirectories comprises two basic PSP components, among others: l l
PSP description file (XML file)
ZIP archive containing the directory structure containing the driver/software kit and installation tools.
To be processed by PrimeUp, PSPs can be provided as follows: l l
Within a flat directory
In a tree structure (e.g. on the Update DVD)
The following example uses the NTAgents PSP to explain the tree structure.
Figure 19: Example of a repository view and the PSP contained
Local System Update for PRIMERGY Servers 56
5.2 PSPs (overview)
5.2.3
Scan PSP
Besides "normal" PSPs, which you use to update driver or software kits on your PRIMERGY server, there is a special PSP called the Scan PSP ( FSC_SCAN ). The Scan PSP includes a set of distinct XML files that are dedicated to normal PSPs.
Figure 20: Scan PSP and PSP.xml content
The contents of Scan PSPs are used to create initial PSP registry entries (see
("faked") PSP registry entries" on page 65
).
5.2.4
PSP versioning
PSP versioning distinguishes two different types of version numbers, both of which are part of the PSP description file (XML file). The PrimeUp installation tool uses these version numbers to decide whether a PSP is to be installed or not (see section
"PrimeUp version handling " on page 60
): l
PSP version number
The PSP version number has the following form:
<major-version>.<minor-version>.<major-build>.<minor-build>
Local System Update for PRIMERGY Servers 57
5.3 PrimeUp installation tool
PrimeUp only checks the <major-version>.<minor-version> part of the PSP version number. The <major-build>.<minor-build> part is ignored.
The semantics are as follows: o o o
A change of <major-version> reflects changes in the list of supported Windows operating systems (e.g. a new Windows version was added).
A change in <minor-version> reflects changes to the software contained by a PSP
(e.g. a new driver / software-kit version was implemented or added).
Changes to the <major-build> indicate that the PSP supports a new server system or controller device (e.g. RX100 S7 and/or LSI controller LSI SAS 3442E-R).
l
Package version number of the MainPackage and the component-specific packages.
The package version number indicates the version of a driver or software kit.
In the case of device drivers, there is also a number specifying the driver date
(e.g. Date="12/04/2015"), which is used to check how up-to-date the driver is.
MainPackages may not have a version or date.
5.3
PrimeUp installation tool
The PrimeUp installation tool is a component of the Update Management of the ServerView
Suite.
PrimeUp allows you to easily update the drivers and software kits of your PRIMERGY servers.
For this purpose, a separate installation package (PRIMERGY Support Package, PSP, see section
"PSPs (overview)" on page 54 ) is available for each component of the server,
containing the driver / software kit and a description file necessary for the installation.
An overview of the components and server models supported by the current PrimeUp version can be found in the readme file for PSPs.
5.3.1
PrimeUp functionality
With PrimeUp you can: l l
Handle PSPs within a plain directory, even if the directory contains more than one PSP.
Handle PSPs within a directory structure that features a well-defined tree structure.
Local System Update for PRIMERGY Servers 58
5.3 PrimeUp installation tool l
Find out the system board, chassis, and model information even if ServerView Agents is not installed.
If PrimeUp cannot automatically find out system board, chassis, and model information, or if you prefer to overwrite the automatically detected values, three options ( -b , -c, -m see
"-c <chassis> -b <board> -m <model>" on page 71 )
allow you to specify system-board, chassis, and model information explicitly.
l l l l l l l l l l
Generate a detailed list of PSPs that can be used for installing or updating drivers and/or software kits.
Display all currently installed PSPs.
Perform a simulated installation for testing purposes.
Install or update using PSPs.
Display the order for installing applicable PSPs.
Check whether the currently installed PrimeUp version is sufficient for handling new PSP elements and/or attributes.
Discover device drivers and software kits on a PRIMERGY server.
Check for installed incompatible (rivaling) software packages.
Check whether an appropriate PSP already exists for the driver or software kit.
Create initial registry entries for applicable PSPs, i.e. the following is written into the registry for each of the PSPs: version data of an installed driver / software kit, version of a corresponding PSP.
5.3.2
Installing PSPs using PrimeUp (overview)
This section provides general information on how PrimeUp proceeds when processing PSPs.
While it may not be needed for routinely updating drivers and software kits, this information may be useful for more sophisticated update scenarios using PrimeUp.
Requirements l
To use PrimeUp, you need administrator rights.
l
To allow safe resetting in the case of errors, you should perform an appropriate backup of your system before doing any updates.
l l
PrimeUp must be started on the server which is to be updated.
Use of PrimeUp via Terminal Services Session or Telnet Session is not allowed.
In detail, this section explains the following: l l
How to start PSP installation .
How PrimeUp handles PSP versions
.
Local System Update for PRIMERGY Servers 59
5.3 PrimeUp installation tool l l l
How PrimeUp detects the chassis ID, systemboard ID, and model ID of the server to be updated
.
How PrimeUp works in approximate steps
.
How PrimeUp interacts with the Windows registry
.
5.3.2.1 Starting PSP installation
The installation of PSPs with the PrimeUp tool is controlled on one server via command line interface using parameters and the associated options. You can also create scripts to update more than one system.
In both cases installation only occurs if the integrated control mechanism in the PrimeUp tool recognizes that installation is possible and permitted based on the detected hardware and software components.
PSPs must be accessible for PrimeUp via network. If this applies, updating drivers and software kits does not require the PSPs to be available locally on the system.
Updates can be installed which are located locally on the server, on the Update DVD, or in a storage location in your internal network which PrimeUp can reach via the network. Please also read the section
"Important notes" on page 80 .
5.3.2.2 PrimeUp version handling
PrimeUp uses an internal version-handling algorithm based on the PSP version number (see section
) to decide whether or not to install a PSP. PrimeUp version handling may lead to different results depending on the parameters ( -update ,
-force , -reginit ) you specify when calling PrimeUp (see section
"PrimeUp - Parameters and options" on page 70 ).
To decide whether or not to install a PSP, PrimeUp proceeds as follows: l l
PrimeUp ignores the <major-build>.<minor-build> part of the PSP version number.
PrimeUp checks dependencies in a MainPackage first. These dependencies must be fulfilled because otherwise normal packages will not be considered and PrimeUp treats the PSP as "not applicable".
l
PrimeUp checks for hardware and software dependencies.
At first, PrimeUP checks the cross-package dependencies defined in the MainPackage. If not all cross-package dependencies are met, PrimeUp treats the PSP as "not applicable" without considering the component-specific packages.
Only if all cross-package dependencies are met, PrimeUp checks the individual component-specific packages for dependencies.
Local System Update for PRIMERGY Servers 60
5.3 PrimeUp installation tool l
If the -force parameter is specified, PrimeUp will reinstall / update the PSP, even if the version of the new PSP is older than the version of the already installed PSP.
l
If the -update parameter is specified, PrimeUp compares the PSP version number of the new PSP with the version number of the already installed PSP. Depending on the result of the version check, PrimeUp proceeds as follows: o If the already installed PSP has a newer version than the new PSP:
No installation will be done.
o If the already installed PSP has the same version as the new PSP:
PrimeUp checks whether the new PSP provides a new package (driver / software kit).
For each package contained in both the new and the already installed PSP, PrimeUp compares the corresponding package versions (package dates in the case of drivers).
PrimeUp will only install new packages and packages whose version/date differs from the new to the already installed version.
o If the already installed PSP has an older version than the new PSP:
PrimeUp checks whether the new PSP provides a new package (driver / software kit).
For each package contained in both the new and the already installed PSP, PrimeUp compares the corresponding package versions (package dates in the case of drivers).
PrimeUp will only install new packages and packages whose version/date differs from the new to the already installed PSP.
l
If the -reginit parameter is specified, PrimeUp performs the version check as described in the case of -update .
However, PrimeUp will not install packages, but only create corresponding initial
("faked") entries in the registry.
5.3.2.3 How PrimeUp detects the chassis ID, system board ID, and model ID of your server
You can use the parameters -b and/or -c and/or -m to explicitly inform PrimeUp of the chassis ID, board ID, and model ID of the server to be updated (see section
Parameters and options" on page 70
). Otherwise, PrimeUp tries to automatically detect chassis ID, board ID, and model ID as described below:
An explicitly specified chassis ID and/or board ID and/or model ID (parameter -c and/or -b and/or -m ) has a higher priority than corresponding values that are automatically detected by PrimeUp.
Local System Update for PRIMERGY Servers 61
5.3 PrimeUp installation tool
1. PrimeUp queries WMI (Windows Management Instrumentation).
2. If step 1 fails, PrimeUp queries ServerView Agents (if running) for the server type.
3. If step 1 and step 2 fail, parameters -b and/or -c and/or -m must be specified.
5.3.2.4 How PrimeUp works
PrimeUp can handle PSPs that are provided in a plain directory or in a well-defined tree structure. The following describes how PrimeUp works in approximate steps:
1. PrimeUp generates an internal list of available PSPs that reside in a plain directory or in a directory tree structure, or are specified in the PrimeUp command line. To do this,
PrimeUp scans for the corresponding description files (XML).
2. PrimeUp defines the PSP installation sequence for updating or installing drivers and/or software kits. The installation sequence is predetermined by the value of the
Priority attribute specified in the description files (XML) of the individual PSPs.
At first, PrimeUp processes all PSPs of priority class 1, then all PSPs of priority class 2 are processed, and so on.
Within the same priority class, PSPs that require an immediate system reboot after installation are put to the end.
3. PrimeUp scans the current PSP registry entries and generates an internal list of registered PSPs.
4. PrimeUp processes the list of available PSPs (see step 1) by checking each PSP’s suitability for the current system environment. To do this, PrimeUp checks the main packages and all other packages within each PSP by applying a set of dependency checks.
To perform the dependency checks on the individual PSPs, PrimeUp proceeds as follows for each PSP: a. First, PrimeUp checks whether the description file (XML) of the PSP is valid for the current system environment (system identification).
b. If step a) is successful and a main package is available, PrimeUp performs dependency checks defined in the MainPackage (e.g. checking for rivaling installed software package, availability of a device, etc.).
c. If step a) and/or step b) is/are successful, PrimeUp performs some additional checks defined in normal packages (e.g. checking for rivaling installed software packages, checking availability of the device, operating system, availability of another PSP): o o
If none of the packages passes the check, PrimeUp skips (ignores) the PSP.
If at least one of the packages passes the check, PrimeUp initiates the desired package update/installation.
Local System Update for PRIMERGY Servers 62
5.3 PrimeUp installation tool
5. If the parameter -force or -update is specified, PrimeUp installs/updates drivers
and/or software kits according to PrimeUp version handling ( see page 60 ) and the rules
specified in the description file (XML).
For drivers and software kits that are actually installed/updated by calling PrimeUp with
-update or -force , PrimeUp modifies/creates the corresponding registry entries and sets authenticity to "real".
6. If the parameter -reginit is specified, PrimeUp creates initial PSP registry entries
(see
"Creating initial ("faked") PSP registry entries" on page 65
).
7. During processing, PrimeUp creates a log file in the directory where PrimeUp normally extracts and processes PSPs (e.g.
\Documents and Settings\<username>\
LocalSettings\Temp\PrimeUp ).
8. To detect already installed drivers and software kits, PrimeUp scans the description file
(XML) for software-kit identification data (e.g. upgrade key for MSI packages, driver date) and searches the currently installed Windows operating system for the corresponding data.
PrimeUp uses Windows functions to automatically detect the corresponding driver data for each hardware device.
5.3.2.5 How PrimeUp interacts with the Windows registry
PrimeUp can create PSP entries in the Windows registry.
By default, PrimeUp scans the Windows registry for PSP registry entries before installing a driver or software kit. If it does not find any PSP registry entries, PrimeUp assumes that PSPs and associated drivers and/or software kits are not yet installed on your server.
However, there may already be drivers and software kits on your server that have been previously installed via another installation tool. These drivers / software kits may have an older, equal, or newer version than the corresponding drivers / software kits that PrimeUp is due to install.
The behavior described above may result in unintended downgrades or updates. To avoid this problem you can call PrimeUp with the -reginit parameter (
).
Attributes of a PSP registry entry
PrimeUp writes the following data into a registry entry:
Local System Update for PRIMERGY Servers 63
5.3 PrimeUp installation tool
Name authenticity
UpgradeCode
ProductCode
Meaning
Indicates whether the PSP entry is an initial ("fake") or a "real" one.
For MSI products.
For MSI and IS products (if available).
UninstallKey For products with "uninstall command" in registry
Package_Flag_String This flag indicates the product type.
Certified
VVID
Indicates whether the driver / software kit is certified.
Software pool ID driverVersion /
SoftwareVersion packageDate
PSP version
(versionMajBuild, versionMajor, versionMinBuild, versionMinor)
Version of an installed driver / software kit; otherwise "0.0.0.0"
Date of an installed driver / software kit; otherwise "0/0/0"
Matched PSP version
Table 7: Data written into a registry entry
The authenticity attribute indicates the status of a new PSP. These are the possible authenticity values:
Authenticity value real fake,fake, fake,+ fake,unknown
Meaning
New driver /software kit installed.
Installed driver / software kit is older.
Installed driver / software kit matches.
Installed driver / software kit is newer.
driver / software kit is not installed.
Table 8: Possible authenticity values of a PSP registry entry
Calling PrimeUp using the -reginit parameter
To prevent unintended downgrades or updates, you can specify the -reginit parameter when calling PrimeUp:
Primeup -reginit <xml file> [-v]
Local System Update for PRIMERGY Servers 64
5.3 PrimeUp installation tool
This causes PrimeUp to initially perform an inventory of all of your server’s hardware components and associated drivers. PrimeUp then checks the detected hardware/driver components against the list of PSPs to be processed (i.e. new PSPs).
For each hardware/driver component and software kit that is already installed on the server,
PrimeUp scans the list of new PSPs for a corresponding PSP.
In the case of a software kit, the description file (XML) of the corresponding PSP provides identifying features (e.g. upgrade or product code of MSI packages) that allow PrimeUp to check the system for an already installed version of the software kit.
Creating initial ("faked") PSP registry entries
Each time PrimeUp detects a PSP corresponding to or matching an already installed driver or software kit, it creates a special PSP registry entry known as as an initial ("faked") registry entry.
PrimeUp proceeds as follows:
1. PrimeUp writes the actually installed component’s version (date in the case of drivers) into the initial registry entry.
2. In addition, PrimeUp writes the PSP version into the initial registry entry. Depending on the situation, PrimeUp inserts the following version value: l
If the data (e.g. version) of an already installed driver / software kit matches the data of the corresponding driver / software kit provided by the (new) PSP, PrimeUp passes the PSP version unchanged into the initial registry entry.
l
If the data (e.g. version) of the installed driver / software kit is newer than the data of the driver / software kit provided by the new PSP, PrimeUp adjusts the PSP version to:
99.99.99.99
l
If the data (e.g. version) of the installed driver / software kit is older than the data of the driver / software kit provided by the new PSP, PrimeUp adjusts the PSP version to:
<majorVersion>.<minorVersion>-1.99.99
If a PSP description file (XML) provides no identifying feature for the associated software kit, even PrimeUp -reginit cannot find the software kit. Provided that all dependencies documented in the description file are fulfilled, PrimeUp creates a
ZeroVersion entry for this PSP in the registry (see
"ZeroVersion registry entries" on page 66 ).
Local System Update for PRIMERGY Servers 65
5.3 PrimeUp installation tool
Creating initial registry entries using a Scan PSP
You can also use the contents of a Scan PSP (see section
) to create initial PSP registry entries.
Proceed as follows:
1. Call PrimeUp to install a Scan PSP, e.g.:
PrimeUp -update FSC_SCAN
2. Call PrimeUp with the -mappsp parameter:
PrimeUp -reginit -mappsp
This causes PrimeUp to take all PSPs from the installed Scan PSP and check them.
PrimeUp creates adequate initial registry entries for applicable PSPs.
ZeroVersion registry entries
If during processing of PrimeUp -reginit a PSP passes all dependency checks, but no appropriate / corresponding driver or software kit is already installed, PrimeUp creates a new
PSP registry entry known as a ZeroVersion registry entry. A ZeroVersion entry is an initial
("faked") registry entry whose version and date attributes are all set to "0.0.0.0" and "0/0/0" respectively.
How PrimeUp -reginit works
The following describes in detail how PrimeUp proceeds when called with the -reginit parameter.
1. PrimeUp scans for all hardware components available on the server (especially PCI controllers and associated device drivers), and stores the detected data in a PrimeUpinternal list.
2. PrimeUp scans the registry for all available PSP registry entries and inserts them in a
PrimeUp internal list.
3. PrimeUp deletes all ZeroVersion entries from the registry.
4. PrimeUp deletes all PSPs (registry entries, current PSP data) whose installation requirements are no longer met. This, e.g., applies if the corresponding hardware has been removed.
5. For every newly received PSP made available via CLI, via directory (parameter -D ), or via the -gftree or -tree parameter, PrimeUp checks whether the PSP’s dependencies are fulfilled: l
If a PSP fulfills all software dependencies, but no corresponding driver or software kit is installed on the server, PrimeUp creates a ZeroVersion entry for the PSP (see
"ZeroVersion registry entries" on page 66
).
Local System Update for PRIMERGY Servers 66
5.3 PrimeUp installation tool
If a PSP description file (XML) provides no identifying features for the associated software kit, even PrimeUp -reginit cannot find the software kit.
l
If a valid PSP registry entry already exists for the PSP
(i.e.
authenticity ="real"), PrimeUp proceeds as follows:
The PSP entry is deleted from the registry if the following applies: o o o
All PSP dependencies are fulfilled but at least one associated component (driver or software kit) is no longer available on the server.
Both the PSP registry entry and the PSP data are deleted if at least one prerequisite required for installing the PSP is no longer met (e.g. if the corresponding controller is no longer available on the system).
The PSP registry entry will persist if PrimeUp could actually detect the associated driver or software kit and all installation requirements (dependencies) are still met.
l
Otherwise, PrimeUp writes the corresponding version (in the case of software kits) or date (in the case of drivers) to the registry. The PSP version (modified if necessary) is also written to the registry (see section
"Creating initial ("faked") PSP registry entries" on page 65
).
6. If a PSP description file (XML) provides no identifying features for the associated software kit, even PrimeUp -reginit cannot find the software kit. Provided that all dependencies documented in the description file are fulfilled, PrimeUp creates a
ZeroVersion entry for the PSP in the registry.
5.3.3
Requirements for PrimeUp
PrimeUp and the PSPs are available for the Microsoft server operating systems Windows
Server 2012/2016.
In particular, the requirements described below should be noted.
For detailed information about the supported servers, software requirements and supported drivers, please refer to the Readme file that you will find on the Update
DVD.
5.3.3.1 Supported servers
PrimeUp is available for the server families TXnnn, RXnnn, ECnnn, BXnnn, CXnnn, and
PQnnn. Exact specifications can be found in the readme file for PSPs.
Local System Update for PRIMERGY Servers 67
5.3 PrimeUp installation tool
5.3.3.2 Software requirements
To use PrimeUp you need Windows Server 2012 or Windows Server 2016. See also the notes in the readme file for PSPs.
Use of PrimeUp via Terminal Services Session or Telnet Session is not allowed.
5.3.3.3 Supported drivers
A table showing the supported drivers can be found in the current readme file for PSPs. By default only certified driver software is updated.
5.3.4
Installing / uninstalling PrimeUp
PrimeUp is provided on the Update DVD as both the PrimeUp.msi
MSI package and the
PrimeSetUp.exe
InstallShield package.
Please use the MSI package PrimeUp.msi
only for a new installation of PrimeUp.
For upgrading from an older, already installed PrimeUp version, please use
PrimeSetUp.exe
.
5.3.4.1 Installing PrimeUp
As the administrator, you install PrimeUp locally on your server with the adequate installer.
To use PrimeUp, you need a knowledge of the system and administrator rights. To allow safe resetting in the event of errors, you should perform a backup beforehand.
Use of PrimeUp via Terminal Services Session or Telnet Session is not allowed.
You start the installation process by l selecting the PrimeUp MSI package, opening the pop-up menu with the right mouse button, and selecting from it the Install function, or l selecting the PrimeSetup package, opening the pop-up menu with the right mouse button, and selecting from it the Run as Administrator function, or l double-clicking PrimeUp.msi
or PrimeSetUp.exe
.
You will be guided through the installation with a dialog which begins with a welcome screen and ends with an installation message.
Local System Update for PRIMERGY Servers 68
5.3 PrimeUp installation tool
The default installation path is
\ProgramFiles\Fujitsu\ServerView Suite\PrimeUp .
It is recommended that you always use the same installation directory for the installation.
5.3.4.2 Uninstalling PrimeUp
PrimeUp is uninstalled via the Windows menu. Proceed as follows:
You can remove PrimeUp via the Windows menu:
1. Select Start - Control Panel - Add or Remove Software .
2. Select Fujitsu ServerView Suite - PrimeUp .
3. Click Remove .
PrimeUp is updatable, i.e. to install a new version you do not need to uninstall the existing one.
5.3.5
Starting PrimeUp
Following successful installation, as the administrator you can start PrimeUp via the input prompt without specifying the installation directory. The entry for the system path is created during the installation.
You cannot start the program by double-clicking PrimeUp.exe
because it is a command-line tool.
Example
Starting PrimeUp with the -?
parameter without specifying the installation directory.
Local System Update for PRIMERGY Servers 69
5.3 PrimeUp installation tool
Figure 21: Starting PrimeUp with the -? parameter
5.3.6
PrimeUp - Parameters and options
Syntax
You may specify the parameters in any order.
The following explanation of the parameters is arranged with regard to functional aspects.
PrimeUp [-? | -b <board> | -c <chassis> | -m <model> |
-d <infolevel> | -D <dir> | -force |
-gftree [gfroot_path] | -help | -installed |
-list | -noreboot | -reginit | -simulate |
-tree [pathname] | -uncertified | -update |
-v | -vv | -vvv | -version | -log file <filename> |
-clean | <xml>]
Local System Update for PRIMERGY Servers 70
5.3 PrimeUp installation tool
Parameters
-?, -help
Default.
Outputs a list of all parameters and options with brief descriptions .
(See example in section
"Starting PrimeUp" on page 69 .)
-c <chassis> -b <board> -m <model>
Sets or changes chassis, system board and/or model information, depending on whether
PrimeUp could automatically detect the corresponding information (see section
PrimeUp detects the chassis ID, system board ID, and model ID of your server" on page
Parameters -b , -c and -m must be specified together. However, for some systems you need not explicitly specify the chassis ID (parameter -c ) and system board ID (parameter -b ) and model ID (parameter -m ). If this applies and only the chassis ID is available, you can specify <board> and / or <model> as
"unknown" and vice versa.
Explicitly specified -b , -c , and -m parameters have a higher priority than any chassis and/or system board and/or model information automatically detected by
PrimeUp.
-c <chassis> sets or changes the chassis information (e.g. RX2540 M1).
-b <board> sets or changes the system board information (e.g. D3289).
-m <model> sets or changes the model information (e.g. CELSIUS).
Example
For RX2540 M1, you must enter D3289.
-file <pathname>
Processes a list of PSPs that are provided in the file specified by <pathname>. PSPs must be specified using the complete path name.
-D <dir>
Sets the (flat) directory containing the PSPs.
This parameter must be specified if the PSPs are not in the directory from which
PrimeUp is called (default installation source).
-tree <pathname>
Searches for PSPs in a directory that is compliant with ServerView Update Manager. In contrast to the -gftree parameter, you must explicitly specify the root directory of the tree that contains the PSPs. The root directory can have any name.
Local System Update for PRIMERGY Servers 71
5.3 PrimeUp installation tool
-gftree [gfroot_path]
Searches for PSPs in a directory that is compliant with ServerView Update Manager.
PrimeUp automatically appends the directory name PrimSupportPack-Win to the end of the path name.
-setfile <root_path>
Searches for PSPs in a directory that is compliant with ServerView Update Manager.
PrimeUp automatically appends the directory name PrimSupportPack-Win to the end of the path name.
The directory PrimSupportPack-Win must contain a file ELEMENTS_OF_
SET.txt
. Each line in ELEMENTS_OF_SET.txt
must specify a PSP using the complete path name (like with the -file parameter, see above).
That way, you can define a PSP set that represents a subset of all PSPs contained in the tree. This may be useful if you do not want to always use the most recent version (unlike in case of the -tree parameter, see above).
-list
Creates a list of all PSPs with version numbers which would be installed.
PrimeUp does not install the PSPs.
Each entry contains one of the following labels:
DO PSP will be installed.
SKIP PSP is skipped.
N/C PSP is not certified.
-simulate
Performs a simulated installation for each PSP. The processing of the packages ends before the installation command is called. It can therefore be checked for each PSP whether an installation is possible.
Each entry contains one of the following labels:
DO PSP will be installed.
SKIP PSP is skipped.
N/C
N/A
PSP is not certified.
PSP is not applicable.
-uncertified
Enforces the installation of non-certified PSPs. The parameter works in combination with
-update , -force , or -reginit .
Local System Update for PRIMERGY Servers 72
5.3 PrimeUp installation tool
-update
Default if both -update and -force are not specified.
Installs updates using the currently available PSPs.
Only certified drivers are installed. (Default)
To also install non-certified drivers the parameter -uncertified is required.
-force
Forces the installation. The specified PSP is installed even if a later or same version of the package already exists on the system.
Only certified drivers are installed. (Default)
To also install non-certified drivers the parameter -uncertified is required.
-reginit
Creates initial PSP entries in the registry. No PSPs will be installed.
Only certified drivers are considered. (Default)
To also consider non-certified drivers the parameter -uncertified is required.
PrimeUp detects drivers and software kits and creates the appropriate version entries.
For details of calling PrimeUp with the -reginit parameter, see
"How PrimeUp reginit works " on page 66 .
If you use the -reginit parameter in combination with the -mappsp parameter,
PrimeUp will take PSPs from an installed Scan PSP (see section
check them, and create the corresponding registry entries.
-mappsp
Can only be used in combination with the -reginit parameter.
Takes PSPs from an installed Scan PSP (see
"Scan PSP" on page 57 ) and checks them.
PrimeUp then processes these PSPs according to the -reginit parameter.
-noreboot
Prevents the immediate reboot called for in the description file (PSP.XML). PrimeUp outputs return code 2 and makes an entry in the OS event log file. Using this parameter only makes sense in a script with which the return code is evaluated and the reboot is script-controlled. If the parameter is not specified, PrimeUp performs the reboot itself and, once the system has restarted, continues the PrimeUp task. Which PSPs require immediate reboot can be found in the PSP list in the current readme file.
-d <infoLevel>
Determines the debugging / logging level (info level) using a hexadecimal number.
Calling PrimeUp -hh lists the available debug options.
Local System Update for PRIMERGY Servers 73
5.3 PrimeUp installation tool
The following debug options are available for <infoLevel>:
Hex value Name
1 General
2
4
8
10
Meaning
Comprehensively logs the progress of PSP installation.
Memalloc Logs the memory allocation steps (not relevant for normal
PrimeUp users).
FormatXML Informs how XML files are lowercased and formatted (not relevant for normal PrimeUp users).
XMLinfo
Registry
Shows the information extracted from the XML files.
Shows the information extracted from or written to the registry.
20
40
80
WorkSteps
FWcheck
Resume
Provides a detailed protocol of the individual work steps.
Logs the activities of the firmware check tools.
Logs the resume actions after immediate reboot.
100
200
400
800
Commands
KeepFiles
Scan
List
Logs all commands that PrimeUp itself calls.
Keeps temporary files (e.g. extracted PSP files, log files of commands)
Logs PrimeUp’s activities concerning system detection and detection of installed hardware/drivers/software kits.
Not implemented.
Table 9: Debug options
You can specify several debug options at the same time by connecting the corresponding hex values by the bitwise OR operand. Useful combinations result in e.g.
-d 1, -d 20 , -d 120 , -d 338 .
For detailed information on evaluating the PSP installation process and debugging, see
"Evaluating the installation process " on page 78
.
-hh
Outputs a list of all debug options (together with the corresponding hex values) and the list of valid return codes (see
-help
Outputs a list of all parameters and options with brief descriptions (default).
-installed
Outputs a list of all currently installed PSPs with version numbers.
Local System Update for PRIMERGY Servers 74
5.3 PrimeUp installation tool
-v
Outputs the PSP name and purpose.
Only valid for the parameters -list and -simulate .
-vv
Outputs the current contents of the PSPs, i.e. drivers and/or software kit version, in addition to the PSP name and purpose.
Only valid for the parameters -list and -simulate .
-vvv
Outputs all version numbers in addition to the PSP name and purpose. This allows you to trace the history of a PSP.
Only valid for the parameters -list and -simulate .
-version
Outputs the version number of the PrimeUp tool.
-log file <filename>
All logging is directed to the specified file.
-clean
Removes all PSP related information from Windows registry and all stored PSPs from system.
<xml>
Specifies one or more XML description files.
Only the specified PSPs are installed or viewed. All other PSPs contained in the specified/default installation source are ignored. If the specified XML description files are not contained in the installation source, nothing will be installed.
An example is shown in figure
"Parameter -list" on page 82 .
Examples
Statement Description
PrimeUp -update NTAgents.xml
Installs the packages located in the PSP
NTAgents .
PrimeUp -list Outputs a list of drivers / software kits to be installed for the PRIMERGY server.
No installation occurs.
Table 10: Sample statements
Local System Update for PRIMERGY Servers 75
5.3 PrimeUp installation tool
Statement
PrimeUp -simulate
PrimeUp -update -D driversDir
PrimeUp -update
Description
The simulation generates a list of PSPs whose drivers and software kits can be installed without errors.
The simulation ends before the drivers and software kits are installed.
Updates applicable PSPs located in the driversDir directory.
Updates applicable PSPs located in the directory from which PrimeUp was started.
Table 10: Sample statements
For further examples with outputs, see section
5.3.7
Return codes
PrimeUp -hh displays the list of return codes.
The following return codes are output to the PrimeUp log file
( %TEMP%\PrimeUp\PrimeUp_DBGlog.txt
) and to the Windows shell for checking scripts. A query in the script is also possible.
Return code
Description
0 The installation was successful.
1 Based on the information in the description file(s), the installation must be completed with a reboot (see call option -noreboot ).
2 Based on the information in the description file(s), a reboot is required immediately (see call option -noreboot ).
3 Invalid call options.
4 A syntax error was discovered in the description file of the PSP.
5 Registry access error. Registry data corrupt, or registry access failed.
6 Incorrect path specified for the directory, wrong file name, or no files in the specified directory.
Table 11: Return codes
Local System Update for PRIMERGY Servers 76
5.3 PrimeUp installation tool
Return code
Description
7 Installation is not possible due to a lack of information on the system board/chassis. Install the current ServerView Agents software or use the parameters -b and -c .
8 Errors occurred during installation of one or more PSPs.
9 The specified PSP(s) cannot be used on this system. No suitable hardware was found for the PSP, or other dependencies are not fulfilled.
10 Undefined.
Note: Do not respond to it!
11 Internal return code; please ignore.
Note: Do not respond to it!
12 The PrimeUp version currently used is out of date. Newer PrimeUp version required.
13 XML version error
14 PrimeUp (primeup.exe) already running.
15 Missing file.
55 Fatal error.
57 PSPs cannot be installed on a virtual machine (VM).
61 Invalid repository path.
Table 11: Return codes
Important notes l
When installing several PSPs in the same PrimeUp call:
In many cases the return codes provided by PrimeUp reflect the overall result of the
PrimeUp run. E.g. if at least one of the PSPs is not installable or not applicable (return code 8 or 9, respectively), PrimeUp provides returns code 8 or 9 as the overall return code.
For detailed information concerning installation of a specific PSP, transmit a PrimeUp call that installs only this PSP.
l
PrimeUp returns only one return code per call. When installing several PSPs within the same PrimeUp call please note: o o o
Reboot is required for return codes 1 and 2 to complete the installation correctly.
The log file should always be checked if return code 8 or 9 occurs. Please analyze the log file to localize the PSP(s) that caused the error.
The installation should be executed with reboot if a reboot is required for individual
PSPs.
Local System Update for PRIMERGY Servers 77
5.3 PrimeUp installation tool o o
When installing more than one PSP, return code 9 indicates that at least one of the
PSPs is not applicable due to internal dependency checks by PrimeUp.
No activity is required if return code 9 occurs because return codes 1, 2 and 8 have higher priority.
5.3.8
Evaluating the installation process
The following files provide you with information about the installation process: l l
PrimeUp log file
OS event log file
When installing several PSPs in the same PrimeUp call:
If code 1 and/or return code 2 are reported, a restart of your server is required.
PrimeUp log file
With each call, PrimeUp generates the log file
%TEMP%\PrimeUp\PrimeUp_DBGlog.txt
, which is used to log the steps and is overwritten each time the tool is called. If the file is to be used to log the updates, you will need to save it, e.g. under
C:\Users\Administrator\Appdata\Local\Temp\PrimeUp (Windows Server
2008)
OS event log file
PrimeUp writes the following messages to the OS event log file: l l l l l
PrimeUp successfully installed PSP ’%1’ %2.%3.%4.%5
PrimeUp successfully installed PSP ’%1’ %2.%3.%4.%5; Reboot required
PrimeUp successfully installed PSP ’%1’ %2.%3.%4.%5; Immediate reboot required
PrimeUp skipped PSP ’%1’ %2.%3.%4.%5
PrimeUp failed to install PSP ’%1’ %2.%3.%4.%5
The following substitutions apply for the messages: l l
%1: PSP name
%2 ... %5: PSP version
Generating debug information
For diagnostic purposes you should use the debug option -d <infolevel> with an appropriate info level (see section
"PrimeUp - Parameters and options" on page 70
). Useful info levels include -d 1 , -d 20 , -d 120 , -d 338 or -d 420 .
Local System Update for PRIMERGY Servers 78
5.3 PrimeUp installation tool
To receive comprehensive diagnostic information, it is recommended to proceed as follows:
1. Use the -d 338 info level, which comprises the debug options -d 200 , -d 100 , -d
20 , -d 10 , and -d 8 . Thus, -d 338 provides detailed debugging information on the following: o o o o
Information extracted from the XML files ( -d 8 )
Information on the registry ( -d 10 )
Detailed protocol of the work steps performed ( -d 20 )
Logs of all shell commands called by PrimeUp internally ( -d 100 ) o The -d 200 info level causes PrimeUp to keep temporary files, in particular
PrimeUp_DBGlog.txt
.
2. Combine stderr and stdout into the stdout stream, and redirect the stdout stream to file primeup_trace.out
or use the -log file primeup_trace.out
parameter.
3. Send the zipped log files to your responsible Support Partner at FUJITSU if necessary.
You will find the current telephone number at: http://ts.fujitsu.com/support/helpdesk.html
Example
The following example combines stderr and stdout into the stdout stream, and redirects the stdout stream to file primeup_trace.out
:
Figure 22: Calling PrimeUp to provide debugging information and to redirect stdout
Figure 23: File containing debugging information
Local System Update for PRIMERGY Servers 79
5.4 PrimeUp usage variants
5.3.9
Important notes
When installing PSPs using PrimeUp please note: l
To decompress the PSPs, a temporary directory ( %Temp%\PrimeUp\<PSPname>\...
) is created. This directory is deleted when the program ends.
Calling PrimeUp with option -d 200 prevents the directory from being deleted.
l l
Installing LAN drivers via a network connection can have unexpected effects because of the short-term interruption of the current LAN connection. You can avoid this problem by first identifying the PSPs to be installed with the call PrimeUp -list . You should then install the packages containing the letter combination LAN locally and individually, e.g.
PrimeUp -update localdrive:BroadCom_LAN_BCM570x.xml
.
Description files must not be renamed or changed.
5.4
PrimeUp usage variants
The PrimeUp Tool gives you two possibilities for updating drivers and software kits. You can use the parameters and options either in a script or manually at the input prompt. Both variants are explained briefly below, followed by a section with outputs for the various parameters and options.
5.4.1
Scripting
The most convenient way to perform a new installation or an update is to use a script. For an optimum and comprehensible process, it is recommended that you execute a PrimeUp call for each PSP. The switch -noreboot is mandatory in a script environment because otherwise PrimeUp performs the reboot and the script environment is no longer available after the system is restarted.
The following procedure is recommended for the scripting:
1. Call PrimeUp: PrimeUp -update -noreboot <name_of_PSP>.xml
2. Evaluate the return codes
Return code Meaning
2 A reboot must be executed immediately in the script.
1 The processing can continue in the script; the reboot must occur at the end of the script processing.
Table 12: PrimeUp return codes
Local System Update for PRIMERGY Servers 80
Return code Meaning
0 or 9 The processing can continue in the script; the next PSP is being processed.
Other An error response must occur in the script.
Table 12: PrimeUp return codes
5.4 PrimeUp usage variants
Figure 24: Sample script
5.4.2
Manual calling
To call PrimeUp manually at the input prompt, the following procedure is recommended:
1. Enter PrimeUp -simulate or PrimeUp -list .
The list on the screen should then be evaluated.
2. Enter PrimeUp -update .
The return codes from the log file must then be evaluated: o o
Return code 8 (BAD_INSTALL) requires analysis of the log files.
Return code 1 indicates that the installation will not become effective until after the next reboot.
Local System Update for PRIMERGY Servers 81
5.5
Examples
The following examples show the outputs of PrimeUp with various parameters.
5.5.1
Parameter -installed
Example using the parameter -installed
5.5 Examples
Figure 25: Example of parameter -installed
5.5.2
Parameter -list
Example 1: Parameter -list
Figure 26: Example of parameter
-list
Example 2: Parameter -list in combination with the option -v
Figure 27: Example of parameter -list with option -v
Local System Update for PRIMERGY Servers 82
Example 3: Parameter -list ; PSPs are specified in the command line
PrimeUp ignores all PSPs provided in the installation source (here: directory from which
PrimeUp is called) with the exception of the PSPs that are explicitly specified in the command line (here: ATI_Radeon.xml
, NTAgents.xml
and FSC_SCAN.xml
).
5.5 Examples
Figure 28: Example of parameter -list with a list of explicitly specified PSPs
5.5.3
Parameter -reginit
Examples using the parameter -reginit.
PrimeUp used with parameter -reginit creates only initial ("faked") registry entries. "Real" entries will only be created by calling
PrimeUp -update or PrimeUp -force .
Example 1: Parameter -reginit in combination with parameter -gftree
Figure 29: Example of parameter
-reginit in combination with parameter
-gftree
Local System Update for PRIMERGY Servers 83
Example 2: Parameter -reginit in combination with parameter -tree
5.5 Examples
Figure 30: Example of parameter
-reginit in combination with parameter
-tree
Example 3:
Registry before and after execution of PrimeUp -reginit NTAgents.xml
The example starts with the following PrimeUp registry:
Figure 31: PrimeUp registry before calling
PrimeUp -reginit
When PrimeUp -reginit NTAgents.xml
is finished executing, the PrimeUp registry entry is as follows:
Local System Update for PRIMERGY Servers 84
5.5 Examples
Figure 32: PrimeUp registry after PrimeUp -reginit NTAgents.xml
is finished
The authenticity attribute is set to "fake" because the PSP has not been installed.
Calling PrimeUp -reginit creates an initial ("faked") PSP registry entry. This entry refers to an already installed driver or software kit.
Local System Update for PRIMERGY Servers 85
5.5.4
Parameter -simulate
Example using the parameter -simulate .
5.5 Examples
Figure 33: Example of parameter -simulate
Local System Update for PRIMERGY Servers 86
5.5.5
Parameter -update
Example using the parameter -update .
Figure 34: Example of parameter
-update
Registry entry before and after execution of PrimeUp -update
The example starts with the following PrimeUp registry:
5.5 Examples
Figure 35: PrimeUp registry before calling
PrimeUp -update
When PrimeUp -update NTAgents.xml
has finished executing, the PrimeUp registry entry is as follows:
Local System Update for PRIMERGY Servers 87
Figure 36: PrimeUp registry after PrimeUp -update NTAgents.xml
is finished
The authenticity attribute is set to "real" because the PSP has been installed.
Calling PrimeUp -update creates a "real" PSP registry entry. This entry refers to the driver or software kit that was installed during execution of this PrimeUp call.
5.5 Examples
Local System Update for PRIMERGY Servers 88
5.5.6
Parameter -clean
Example using the parameter -clean .
5.6 How to get help
Figure 37: Example of parameter -clean
5.6
How to get help
Please contact your responsible FTS Support Partner or helpdesk. You will find the current telephone number at: http://ts.fujitsu.com/support/helpdesk.html
Local System Update for PRIMERGY Servers 89
6 Autonomous Support Packages (ASP)
Autonomous Support Packages (ASPs) are self-extracting and self-installing software packages that allow you to install BIOS or firmware on your server.
To install BIOS or firmware on a server component, you can call up the appropriate ASP directly.
Before performing any BIOS update: Ensure that BitLocker drive encryption is disabled.
If BitLocker drive encryption is enabled when updating the BIOS, your system normally will no longer be bootable.
Alternatively, you can use ServerView Update Manager Express to install BIOS and/or firmware on your PRIMERGY server. Both ServerView Update Manager and ServerView
Update Manager Express internally use ASPs.
To allow safe resetting in the case of errors, you should perform an appropriate backup of your system before doing any updates.
For PRIMERGY servers running Microsoft Hyper-V, Xen or VMware ESXi, updating
BIOS/firmware may be possible with restrictions. For more details refer to ASP release notes.
Updating BIOS or firmware on virtual machines (virtual guest systems) is generally not possible.
6.1
Current BIOS/firmware versions
The current versions of BIOS and firmware and of the ASPs for your PRIMERGY server are available on the Update DVD, the latest version of which is issued approximately every two months. The Update DVD is bootable. The Update Repository Image is not bootable but does contain all current PSPs and ASPs.
For details, see section
"Download Locations" on page 12 .
Creating the Update DVD from an appropriate DVD ISO image
If you do not own the current Update DVD, you can update your server’s BIOS/firmware by downloading the Update DVD ISO image UPDATE_DVD_<version>.iso
of the latest version from http://support.ts.fujitsu.com/Download/ and create a physical DVD or a bootable USB stick from it.
Local System Update for PRIMERGY Servers 90
6.2 ASPs for Windows
In detail, proceed as follows:
1. Visit http://support.ts.fujitsu.com/Download/ .
2. Select the appropriate PRIMERGY server type and model.
3. Under Select your operating system , select OS Independent (BIOS, Firmware, etc.) .
4. Under Server Management Software ServerView Update DVD , select ServerView
Update DVD .
5. Download the DVD ISO image UPDATE_DVD_<version>.iso
of the latest version from: http://support.ts.fujitsu.com/Download/ and create an Update DVD from it.
6. Use the Update DVD for the BIOS/firmware update.
6.2
ASPs for Windows
Under Windows you can call up an ASP directly as follows: l
In Windows Explorer: by double-clicking the *.exe
file of the ASP.
If you call the ASP in Windows Explorer, a wizard in the GUI of the ASP takes you through a standard installation.
When started in Windows Explorer, an ASP forces BIOS or firmware installation regardless of the corresponding BIOS or firmware version currently installed on your system. Please treat with caution if you start an ASP in Windows Explorer.
l
At the Windows input prompt: via command in the ASP CLI.
Calling the ASP via the command line interface offers you not only wizard-guided standard installation but also additional options for tailoring the installation to your specific needs.
Local System Update for PRIMERGY Servers 91
6.2 ASPs for Windows
6.2.1
Requirements
When updating a network component (e.g. LAN controller), network connections may be lost after a BIOS, firmware or driver update.
Before performing any BIOS update: Ensure that BitLocker drive encryption is disabled.
If BitLocker drive encryption is enabled when updating the BIOS, your system normally will no longer be bootable.
Installing BIOS or firmware via ASPs requires the following: l l l
To execute an ASP, you require administrator rights.
To extract and execute the installation or flash routines, you must have sufficient space
(> 1GB) on the hard disk.
When explicitly calling an ASP via the GUI or CLI, you must perform a version check for
BIOS or firmware or software kit. Make sure that all requirements for executing the ASP are fulfilled (Required drivers or software packages installed, etc.).
6.2.2
Accessing the ASPs
You can access the ASPs for the individual server components as follows:
In the directory of the Update DVD (e.g. created by means of the current DVD ISO image
UPDATE_DVD_<version>.iso
, see section
"Download Locations" on page 12
), the ASPs can be found under Firmware in the following folders (see
): o o o o o o o o o
Agent-Lx
Agent-Win
BladeSystem
FibreChannelController
LanController
ManagementController
MicroController
SystemBoard
ScsiController
The names of the ASPs for Windows consist of the following name elements:
[<server_name>_][<D_no.>_]<component>_<version>.exe
Local System Update for PRIMERGY Servers 92
6.2 ASPs for Windows
The server name and D-number are part of the name whenever the ASP provides server-specific firmware or BIOS.
Example: ASPs on the Update DVD
Figure 38: ASPs for Windows on the Update DVD (example)
6.2.3
Starting the ASP in Windows Explorer
During the installation, ASPs perform compatibility and dependency checks.
Compatibility/dependency checks normally comprise checking e.g. system ID, chassis
ID / board ID, model ID, operating system, availability of hardware, availability of required software.
In the case of unfulfilled dependencies and other discrepancies the installation process aborts with an error message and the related return code.
Local System Update for PRIMERGY Servers 93
6.2 ASPs for Windows
When started in Windows Explorer, an ASP forces BIOS/firmware installation regardless of the corresponding BIOS/firmware version currently installed on your system. Please treat with caution if you start an ASP in Windows Explorer.
To start the ASP, proceed as follows:
1. In Windows Explorer, switch to the folder of your Update DVD which contains the *.exe
file for the ASP you want.
2. Start the ASP by double-clicking this *.exe
file.
If you are executing the ASP on a server which is not supported, a corresponding error message is displayed.
Once the ASP is started, the following welcome screen is displayed:
Figure 39: Welcome screen
The welcome screen shows the descriptive and version information according to the download portal ( support.ts.fujitsu.com
).
Release Notes
Shows the release notes belonging to the BIOS or firmware.
Extract only
Copies the ASP data into a (selectable) directory.
Install
Starts the installation process.
Clicking Install always performs a forced update. Thus installation will be executed even it results in a downgrade.
Local System Update for PRIMERGY Servers 94
6.2 ASPs for Windows
6.2.3.1 Displaying the release notes
To display the release notes, click the Release Notes button in the welcome screen. The
Release Notes window is displayed:
Figure 40: Release Notes window
6.2.3.2 Extracting the data
You can extract the ASP data for the installation process into a selected directory. Proceed as follows:
1. In the welcome screen, click the Extract only button.
The Choose Destination Location window is displayed, in which you define the target directory for the extracted data:
Figure 41: Choose Destination Location window
2. A default directory is offered under Destination Directory . You can change this directory via the Browse button.
Local System Update for PRIMERGY Servers 95
6.2 ASPs for Windows
3. Click Next to extract the data. A message tells you the result of the extraction:
Figure 42: Extraction successful
4. Click OK to complete the extraction.
6.2.3.3 Starting the BIOS/firmware installation
The installation process does not distinguish between an update and a force/downgrade. The installation is performed in any case (forced), even if the version to be installed is already on the server. This distinction is only possible if you call the ASP via the CLI.
The installation process must not be interrupted under any circumstances!
To install the BIOS/firmware, proceed as follows:
1. In the welcome screen, click the Install button to start the BIOS/firmware installation.
If the ASP cannot identify your PRIMERGY server using the D-number (system board) or cabinet number, you will be told this and prompted to confirm the start of the installation.
To avoid damage to your server, only confirm the start of the installation process with Continue if you are sure that your server allows the use of ASPs.
Figure 43: Confirmation dialog after failed server identification
Local System Update for PRIMERGY Servers 96
6.2 ASPs for Windows
2. Click Continue to start the installation. The following window tells you that the installation is under way:
Figure 44: BIOS/firmware installation in progress
You can close the window with Close . This does not interrupt the installation process.
3. Wait until the installation process is complete. This may take a while (10 - 15 minutes).
Make sure that the installation process is not interrupted under any circumstances!
Once the installation process is complete, one of the following messages is shown. It informs you of the status of the installation and tells you if you need to restart the server.
Figure 45: Installation process complete
Now all files in the extraction directory (ASP target directory) except for the log file Setup.log
are deleted. Experts in handling ASPs can use this log file to analyze the executed ASP in the event of an error.
4. Click OK to confirm the message.
5. Following successful BIOS or firmware installation, restart your PRIMERGY server if this is necessary to activate the BIOS or firmware (see final status message from ASP).
Local System Update for PRIMERGY Servers 97
6.2 ASPs for Windows
6.2.4
Calling ASPs via the command line interface (CLI)
Firmware and BIOS can also be installed via the CLI. In this case, as well as using the
Windows PowerShell or the wizard-guided standard installation, you can access additional options for tailoring the installation to your specific needs.
Proceed as follows:
1. Start the command line ( cmd.exe
).
2. Switch to the directory (on your Update DVD or hard disk) containing the *.exe
file for the ASP you require.
3. Start the ASP command using the syntax described below.
To evaluate the return code, see
"ASP return codes" on page 119
.
Syntax
<ASP_name>.exe [/<option>] ...
Square brackets [ and ] in the options listed below are part of the option names and not metasymbols (option brackets).
For <option> you can specify:
/silent
Executes the ASP without user input. Dialog boxes are displayed, but normally close by themselves. Only the "installation completed" message requires explicit confirmation.
As the "installation completed" message requires explicit confirmation, do not use the /silent option for unattended installation. For unattended installation, use the /hide option instead.
/hide
Executes the ASP in the background. No dialog boxes are displayed.
The /hide option is required for unattended installation.
/InstallDir=“<directory_path>\<target-directory>”
Only in conjunction with the option /[Extract]=yes , /[Update]=yes , or /
[Force]=yes :
ASP user data is extracted to the specified directory. Both <directory_path> and <targetdirectory> must be specified.
Installation may fail if <directory_path> denotes the relative path from the current directory to the <target directory>. If you want to set a relative path, apply the following format using the CD environment variable:
/InstallDir %CD%\<target-directory>
Local System Update for PRIMERGY Servers 98
6.2 ASPs for Windows
/[Update]={yes | no}
Default value in hidden mode: [Update]=yes
Default value in GUI mode: [Update]=no
Only newer BIOS or firmware versions may be installed. This option must be used in conjunction with one of the options /silent or /hide . This function is only performed if it is supported by the actual internal flash program.
A real version check can be performed in most cases.
/[Force]={yes | no}
Default value in hidden mode: [Force]=no
Default value in GUI mode: [Force]=yes
Forces BIOS/firmware installation. Allows older BIOS or firmware versions to be installed.
/[Extract]={yes | no}
Default value: [Extract]=no
ASP user data is extracted to the directory specified by the option /InstallDir . If you do not specify the option /InstallDir , the ASP user data will automatically be extracted to the directory where the ASP is stored.
The option /[Extract]=yes cannot be combined with other extraction options (e.g.
[ExtractReleaseNotes] ) or with the options /[Force] and
/[Update] .
/[ExtractReleaseNotes]={yes | no}
Default value: [ExtractReleaseNotes]=no
The file rel_note.txt
(release notes) is extracted to the directory specified by the option /[TargetReleaseNotesPath] . If you do not specify the option /
[TargetReleaseNotesPath] , the release notes will automatically be extracted to the calling directory (e.g.
D2119_RX300S3_FLASH_DATA ) in the Windows Temp directory.
The option /[ExtractReleaseNotes]=yes cannot be combined with other extraction options (e.g.
[Extract] ) or with the options /[Force] and /
[Update] .
/[TargetReleaseNotesPath]="<directory_path>\<file_name>"
Only in conjunction with the option /[ExtractReleaseNotes]=yes :
The release notes are extracted to the specified directory. Both <directory_path> and
<file_name> must be specified.
Local System Update for PRIMERGY Servers 99
6.2 ASPs for Windows
/[KeepFiles]={yes | no}
Default value: [KeepFiles]=no
Data will be deleted / not deleted from the ASP target directory after completion of the installation or update process. The kept data can be used e.g. for evaluating logging data or testing commands etc.
In the case of a failure, please save the contents of the ASP target directory and send the zipped directory to your responsible Support Partner at FUJITSU for further analysis.
/[Help]={yes | no}
Default value: [Help]=no
Outputs a brief description of the options. Within an ASP call, this option cannot be combined with other options.
In the output text, the information under Build tells you the build of the ASP, not the version of the BIOS/firmware it contains.
/[ExpertHelp]={yes | no}
Default value: /[ExpertHelp]=no
Outputs a brief description of additional options meant for experts. Within an ASP call, this option cannot be combined with other options.
In the output text, the information under Build tells you the build of the ASP, not the version of the BIOS or firmware it contains.
/[ExternalVariable]= "<special_product_options>"
<special_product_options> denotes a string including product-specific options and the related parameters.
Once an ASP command has been submitted, the ASP internally calls the underlying installation tool (e.g.
FTASetup.exe
) that performs the actual installation. ASP options and parameters are passed automatically to the installation tool.
For some ASPs, you can additionally specify the /[ExternalVariable] option, which allows you to define software- or product-specific options. These options enable you to control the installation of the software related to the ASP, e.g. in the case of a non-standard installation.
For details on the product-specific options and parameters available for the ASP considered, please refer to the help text displayed with the /[ExpertHelp] option.
Local System Update for PRIMERGY Servers 100
6.2 ASPs for Windows
Examples:
When installing the ServerView Update Agent via ASP (i.e.
SVUpdateAgent-Win_
ASP<Version>.exe
), you can use the /[ExternalVariable] option to specify additional control parameters that are relevant for installing the ServerView
Update Agent.
Initial silent installation (with default parameters)
SVUpdateAgent-Win_ASP<Version>.exe /hide
(Default: noaccountcheck=0, -flashusergroup=GFUSER )
Initial silent installation (with non-default parameters)
SVUpdateAgent-Win_ASP<Version>.exe /hide /
[ExternalVariable]=\"-noaccountcheck=1\"
SVUpdateAgent-Win_ASP<Version>.exe /hide /
[ExternalVariable]=\"-FlashGroup <usergroup>\"
/[NoAdminCheck]={yes / no}
Default value: [NoAdminCheck]=no
No check for administrator rights.
/[NoSystemCheck]={yes / no}
Default value: [NoSystemCheck]=no . (This applies to most ASPs.)
No system check.
/[NoAgentCheck]={yes / no}
Default value: [NoAgentCheck]=yes
No check for ServerView Agents. Currently, no ASP performs an agent check.
/[NoBladeCheck]={yes / no}
Default value: [NoBladeCheck]=yes
No check for blade systems.
Currently, only the ServerView Update Agent ASP can perform a blade check.
/[NoVirtualCheck]={yes / no}
Default value: [NoVirtualCheck]=no
No check for virtual machines.
/[NoUpdateBlock]={yes / no}
Default value: [NoUpdateBlock]=no
No abortion if option /[Update]=yes was set. Some ASPs may not support option /
[Update]=yes , thus possibly aborting without performing the update. If in such cases
Local System Update for PRIMERGY Servers 101
6.2 ASPs for Windows the option /[NoUpdateBlock]=yes is set, a forced flash - even a downgrade - will be performed.
Some ASPs may not support the /[Update] option, thus aborting without performing the update. If in such cases the option /[NoUpdateBlock]=yes is set, a forced flash
- even a downgrade - will be performed
/[NoReset]={yes / no}
Default value: [NoReset]=no
Suppresses the sending of a final "reset" request to the target device (e.g. no separate reset (reboot) of an iRMC S4 will be performed after a firmware update has successfully completed.)
/[NoRivalCheck]={yes / no}
Default value: [NoRivalCheck]=no
Suppresses the check for rivaling software.
Some ASPs may check whether rivaling software packages are already installed (e.g.
ServerView Management Agents vs. ServerView Agentless Service). Rivaling software packages cannot be installed simultaneously.
/[ExtractParFile]={yes / no}
Default value: [ExtractParFile]=no
Extracts the parameter file.
/[TargetParFilePath]="<path_name_of_the_target_file>"
Only in conjunction with the option /[ExtractParFile]=yes : The parameter file is extracted to the specified directory. Both <directory_path> and <file_name> must be specified.
For examples, see section
"ASPs for Windows" on page 91 .
Return codes
To evaluate return codes, you must start the ASPs with the following call: start /wait <ASP_name>.exe [/<option>] ...
The return code is displayed by entering the following command: echo %errorlevel%
For a list of the return codes, see
"ASP return codes" on page 119
.
Local System Update for PRIMERGY Servers 102
6.2 ASPs for Windows
6.2.5
Calling an ASP via the Windows PowerShell
Firmware and BIOS can be installed via the Windows PowerShell. In this case, as well as using the CLI or the wizard-guided standard installation, you can access additional options for tailoring the installation to your specific needs.
In the Windows PowerShell, you start an ASP via the start command.
Proceed as follows:
1. Start the Windows PowerShell prompt.
2. Switch to the directory (on your Update DVD or hard disk) containing the *.exe
file for the ASP you require.
3. Start the ASP command using the syntax described below.
Syntax start –Wait <ASP_name>.exe –ArgumentList " <option> [<option>]
... "
It is very important to correctly set quotation marks, blanks, and inverted commas.
For a detailed description of the options, see section
"Calling ASPs via the command line interface (CLI)" on page 110
.
For an example of calling an ASP via the Windows PowerShell, see section
"Firmware update with return code (using Windows PowerShell)" on page 106 .
Return codes
The return code is displayed by entering the following command: echo $LastExitcode
To evaluate the return code, see section
"ASP return codes" on page 119
.
Local System Update for PRIMERGY Servers 103
6.2.6
Examples
6.2.6.1 Displaying help texts
To display help texts, enter the following command:
<ASP_name>.exe /[Help]=yes
This opens the following window:
6.2 ASPs for Windows
Figure 46: Displaying help texts
To display help texts meant for experts, enter the following command:
<ASP_name>.exe /[ExpertHelp]=yes
Local System Update for PRIMERGY Servers 104
6.2.6.2 Extracting ASP data
To extract ASP data, enter the following command:
<ASP_name>.exe /[Extract]=yes /silent
Successful extraction is indicated by the following message:
6.2 ASPs for Windows
Figure 47: Extracting ASP data
If no /InstallDir option is specified, the ASP data will be extracted into the default directory (see section
"Extracting ASP user data to the default directory" on page 117 ). The
/InstallDir option allows you to extract the ASP data into a directory of your choice.
Extraction may fail if the option /InstallDir=<directory-path><targetdirectory> is specified with <directory-path> denoting a relative path from the current directory to the <target directory>.
If you want to set a relative path, apply the following format using the CD environment variable:
/InstallDir %CD%\<target-directory>
6.2.6.3 Firmware update with return code
You start a firmware update with the following command: start /wait <ASP_name>.exe /[Update]=yes /silent
When you enter this command, the ASP starts the update process without any further dialogs or user input. A successful update is indicated by the following message:
Figure 48: Firmware update successfully finished
Local System Update for PRIMERGY Servers 105
6.2 ASPs for Windows
Click OK to confirm the message.
Once the installation is complete, by default all files in the extraction directory (ASP target directory) except for the log file Setup.log
are deleted. Experts can use this log file to analyze the executed ASP in the event of an error. You can use the option /
[KeepFiles]=yes to prevent data from being deleted from the ASP target directory after completion of the installation or update process (see section
ASP target directory " on page 107 ).
Following successful firmware/BIOS installation, restart your PRIMERGY if this is necessary to activate the BIOS/firmware.
After the reboot, check whether the relevant installation is also present on the server.
You can do this by calling the BIOS setup or using ServerView Operations Manager or
ServerView Update Manager.
6.2.6.4 Firmware update with return code (using Windows PowerShell)
In the Windows PowerShell, you start a firmware update with the following command: start –Wait <ASP-NAME>.exe –ArgumentList ‘‘ Argument_1
[Argument_2 [Argument_3]] ‘‘
Example start –Wait .\SVUpdateAgent_Win_ASP_61000.exe -ArgumentList
“ /[Update]=yes /silent /InstallDir=C:\tmp\ASP
/[ExternalVariable]=`-noaccountcheck=0 –FlashGroup Users` /
[KeepFiles]=yes “
It is very important to correctly set quotation marks, blanks and inverted commas correctly. This especially concerns the backquote (‘) characters enclosing the string
(argument) of the /[ExternalVariable] option.
When you enter this command, the ASP starts the update process without any further dialogs or user input. A successful update is indicated by the following message:
Figure 49: Firmware update successfully finished
Local System Update for PRIMERGY Servers 106
6.2 ASPs for Windows
Click OK to confirm the message. Following successful firmware/BIOS installation, restart your PRIMERGY if this is necessary to activate the BIOS/firmware.
Once the installation is complete, all files in the extraction directory (ASP target directory) except for the log file Setup.log
are deleted. You can use this log file to analyze the executed ASP in the event of an error.
After the reboot, check whether the relevant installation is also present on the server. You can do this by calling the BIOS setup or using ServerView Operations Manager or ServerView
Update Manager.
You can use the option /[KeepFiles]=yes to prevent data from being deleted from the ASP target directory after completion of the installation or update process
(see section
"Keeping the contents of the ASP target directory " on page 118
).
6.2.6.5 Keeping the contents of the ASP target directory
By default, all files in the extraction directory (ASP target directory) except for the log file
Setup.log
are deleted once the installation is complete.
The option /[KeepFiles]=yes allows you to prevent data from being deleted from the
ASP target directory after completion of the installation or update process. The kept data can be used e.g. for evaluating logging data or testing commands etc.
In the case of a failure, please save the contents of the ASP target directory and send the zipped directory to your responsible Support Partner at FUJITSU for further analysis.
Figure 50: Preventing data from being deleted from the ASP target directory
In the following figure the contents of the ASP target directory are shown:
Local System Update for PRIMERGY Servers 107
6.3 ASPs for Linux
Figure 51: Option /[KeepFiles]=yes : Keeping the contents of the ASP target directory
6.3
ASPs for Linux
Under Linux, you can call up an ASP directly via the command line interface (CLI).
6.3.1
Requirements
When updating a network component (e.g. LAN controller), network connections may be lost after a BIOS, firmware or driver update.
Installing BIOS/firmware via ASPs requires the following: l l
To execute the ASPs, you require root privileges.
You must have sufficient space (> 1 GB) on the hard disk.
6.3.2
Accessing the ASPs
You can access the ASPs for the individual server components as follows:
In the directory of the Update DVD (e.g. created by means of the current DVD ISO image
UPDATE_DVD_<version>.iso
, see section
"Download Locations" on page 12
), the ASPs can be found under Firmware in the following folders (see
o o
Agent-Lx
Agent-Win
Local System Update for PRIMERGY Servers 108
6.3 ASPs for Linux o o o o o o o
BladeSystem
FibreChannelController
LanController
ManagementController
MicroController
SystemBoard
ScsiController
The names of the ASPs for Linux consist of the following name elements:
[<server_name>_][<D_no.>_]<component>_<version>.scexe
The server name and D-number are part of the name whenever the ASP provides server-specific firmware or BIOS.
Example: ASPs on the Update DVD
Figure 52: ASPs for Linux on the Update DVD (example)
Local System Update for PRIMERGY Servers 109
6.3 ASPs for Linux
6.3.3
Calling ASPs via the command line interface (CLI)
Start the installation as follows:
1. Open a terminal.
2. Switch to the directory (on the Update DVD or hard disk) containing the *.scexe
file for the ASP you require.
3. Start the installation with the following command: sh <ASP_name>.scexe <option>
Bear in mind that the options are case-sensitive.
For <option> you can specify:
-s | --silent
Executes the ASP without user input. Logging information, notes and progress information are displayed.
-h | --hide
Executes the ASP in the background without user input and does not output any messages.
If using in a scripting, Update Manager or SMS environment, you must use the option --hide .
-I | --install-dir <directory>
Only in conjunction with the option --extract , --update , or --force :
ASP user data is extracted to the specified directory.
-e | --extract
ASP user data is copied to the directory specified by the option --install-dir .
The option --extract cannot be combined with other extraction options (e.g.
--extract-release-note ) or with the options --force or --update .
If you do not specify the option --install-dir , the ASP will extract the user data to a temporary ASP-specific directory (e.g.
sctmp<process_ID> under <$TempDir>).
Local System Update for PRIMERGY Servers 110
6.3 ASPs for Linux
-r | --extract-release-note
By default, the file rel_note.txt
(release notes) is extracted to the calling directory of the ASP. You can specify a different target directory with the option --targetfile .
The option --extract-release-note cannot be combined with other extraction options (e.g.
--extract ) or with the options --force or -update .
-t | --target-file [<path_name>/]<file_name>
Only in conjunction with the option --extract-release-note or the option
--extract-par-file . The release notes / parameters are extracted to the file <file_ name> of the specified directory.
-u | --update
Default value.
Only newer firmware versions are installed. This function is only performed if it is supported by the actual internal flash program.
-f | --force
Forces BIOS/firmware installation. Older BIOS/firmware versions are also installed
(downgrade).
-k | --keepfiles
Default value: --keepfiles is not enabled.
Data will be deleted / not deleted from the ASP target directory after completion of the installation or update process. The kept data can be used e.g. for evaluating logging data or testing commands etc.
In the case of a failure, please save the contents of the ASP target directory and send the zipped directory to your responsible Support Partner at FUJITSU for further analysis.
-nub | --no-update-block
Default value: --no-update-block is not enabled.
No abortion if option --update is set.
Some ASPs may not support the --update option, thus possibly aborting without performing the update. If in such cases the option --no-update-block is set, a forced flash - even a downgrade - will be performed.
-nrst | --no-reset
Default value: --no-reset is not enabled. (i.e. a "reset" request is sent if the option is not specified.)
Suppresses the sending of a final "reset" request to the target device (e.g. no separate reset (reboot) of an iRMC S4 will be performed after a firmware update has successfully completed).
Local System Update for PRIMERGY Servers 111
6.3 ASPs for Linux
-nrivpkg | --no-rival-pkg-check
Default value: --no-rival-package-check is not enabled.
Suppresses the check for rivaling software packages.
Some ASPs may check whether rivaling software packages are already installed (e.g.
ServerView Management Agents vs. ServerView Agentless Service). Rivaling software packages cannot be installed simultaneously.
-n3264c | --no-3264-bit-check
Default value: --no-3264-bit-check is not enabled.
Suppresses the check for 32 Bit or 64 Bit operating system. Some ASPs may not support
32 or 64 Bit operating systems.
-v<level> | --verbose-<level>
Default value: --verbose-0 (no trace) is enabled.
In case of problems you can activate trace by setting a verbose level (trace level) 1..6.
Trace level 6 outputs maximum amount of trace data.
-sr | --show-return-codes
Default value: --show-return-codes is not enabled.
Displays a list of possible return codes and their meanings.
-? | --help
Outputs a brief description. This option cannot be combined with other options.
In the output text, the information under Build tells you the build of the ASP, not the version of the BIOS/firmware it contains.
-H | --expert-help
Outputs a brief description of additional options meant for experts. Within an ASP call, this option cannot be combined with other options.
In the output text, the information under Build tells you the build of the ASP, not the version of the BIOS/firmware it contains.
-ev| --external-variable " <special_product_options>"
<special_product_options> denotes a string including product-specific options and the related parameters.
Once an ASP command has been submitted, the ASP internally calls the underlying installation tool (e.g.
FTASetup.scexe
) that performs the actual installation. ASP options and parameters are passed automatically to the installation tool.
For some ASPs, you can additionally specify the --external-variable option, which allows you to define software/product-specific options. These options enable you
Local System Update for PRIMERGY Servers 112
6.3 ASPs for Linux to control the installation of the software related to the ASP, e.g. in the case of a nonstandard installation
For details on the product-specific options and parameters available for the ASP considered, please refer to the help text displayed with the --expert-help option.
Examples:
When installing the ServerView Update Agent via ASP (i.e.
SVUpdateAgent_LX_
<Version>.scexe
), you can use the --external-variable option to specify additional control parameters that are relevant for installing the ServerView
Update Agent.
Initial silent installation (with default parameters)
SSVUpdateAgent_LX_<Version>.scexe
(Default: --noaccountcheck=0,
--flashgroup globalflash, -l 2,
-t /opt/SMAW/SMAWgfa/data/gf_agent.log
)
SVUpdateAgent
Initial silent installation (with non-default parameters)
SVUpdateAgent_LX_<Version>.scexe
--external-variable "-noaccountcheck=1"
_LX_<Version>.scexe
--external-variable "--FlashGroup
<usergroup>"
-nr | --no-admin-check
Default value: --no-admin-check is not enabled.
No check for administrator rights.
-ns | --no-system-check
Default value: --no-system-check is not enabled.
No system check.
-na | --no-agent-check
Default value.
No check for ServerView Agents.
-nxen | --no-xen-check
Default value.
No check for Linux XEN host.
-nesx | --no-esx-check
Default value.
No check for VMware ESXi host.
-npkg | --no-pkg-check
No check for installed software packages.
Local System Update for PRIMERGY Servers 113
6.3 ASPs for Linux
-nos | --no-os-check
Default value: --no-os-check is not enabled
No operating system check.
-nb | --no-blade-check
Default value.
No check for a blade system.
-nv | --no-virtual-check
Default value: --no-virtual-check is not enabled.
No check for a virtual machine running on a Hyper-V-, XEN, or VMware host.
--p | --extract-par-file
Default value.
Extracts the parameter file.
For examples, see section
.
6.3.4
Installation procedure
Once you have started the installation, the ASP informs you of its progress and status.
If you called the ASP with the option --silent , it will be executed without user input. Logging information, notes and progress information are displayed.
If you called the ASP with the option --hide , it will be executed in the background without user input and no messages will be output.
Server identification
Before the actual installation, the ASP attempts to identify the server. If the server is not supported, the ASP outputs a corresponding error message:
Figure 53: Server identification: Server is not supported
In addition, the return code returned by the ASP (“wrong system“, echo $?, 17) indicates the reason why the system identification failed (see
"ASP return codes" on page 119
).
Welcome screen
Once the system is successfully identified, the ASP opens the welcome screen, in which you can follow the installation process.
Local System Update for PRIMERGY Servers 114
6.3 ASPs for Linux
If you called the ASP with the option --silent , it will be executed without user input. Logging information, notes and progress information are displayed.
If you called the ASP with the option --hide , it will be executed in the background without user input and no messages will be output.
Figure 54: Following the installation process on the terminal
1. Before the actual installation, the ASP gives you details of the packaged firmware.
2. The ASP asks you to confirm that you want to continue with the installation. (No confirmation dialog with the options --silent or --hide !)
3. The ASP starts the actual BIOS/firmware installation.
The BIOS/firmware installation can take a while (10 - 15 minutes). Make sure that the installation process is not interrupted under any circumstances!
4. The ASP reports status of the completion of the installation and asks you to restart the server if this is necessary to activate the new BIOS/firmware version.
Return codes
The ASP also provides a return code, which you can display with the following command: echo $?
For a list of the return codes, see
"ASP return codes" on page 119
.
Local System Update for PRIMERGY Servers 115
6.3.5
Examples
6.3.5.1 Displaying help texts
To display help texts, enter the following command:
<ASP_name>.scexe --help
6.3 ASPs for Linux
Figure 55: Help on the ASPs
6.3.5.2 Extracting ASP user data
Extracting ASP user data to the default ASP target directory
To extract ASP user data to the default ASP target directory, enter the following command:
<ASP_name>.scexe --extract
The user data packaged in an ASP (firmware, Flash tools, control files etc.) is then extracted to a directory preset by the ASP. The extraction path is composed of the contents of the environment variable $TMPDIR and the process ID of the ASP:
<$TMPDIR>\sctmpdir<process_ID> .
Local System Update for PRIMERGY Servers 116
6.3 ASPs for Linux
Figure 56: Extracting ASP user data to the default directory
Extracting ASP user data to a specific target directory
To extract ASP user data to the directory <directory>, enter the following command:
<ASP_name>.scexe --extract --install-dir <directory>
6.3.5.3 Performing the installation in the background
To execute the ASP for the BIOS/firmware update in the background, enter the following command:
<ASP_name>.scexe --update --hide
Local System Update for PRIMERGY Servers 117
6.3 ASPs for Linux
Figure 57: Executing the ASP for the firmware update in the background
6.3.5.4 Keeping the contents of the ASP target directory
By default, all files in the extraction directory (ASP target directory) are deleted once the installation is complete.
The option --keepfiles allows you to prevent data from being deleted from the ASP target directory after completion of the installation / update process. The kept data can be used e.g. for evaluating logging data or testing commands etc.
In the case of a failure, please save the contents of the ASP target directory and send the zipped directory to your responsible Support Partner at FUJITSU for further analysis.
Figure 58: Preventing data from being deleted from the ASP target directory
In the following figure the contents of the ASP target directory are shown:
Local System Update for PRIMERGY Servers 118
6.4 ASP return codes
Figure 59: Option
--keepfiles
: Keeping the contents of the ASP target directory
6.4
ASP return codes
Error value
_RET_OK
_RET_REBOOT
_RET_REBOOTATONCE
_RET_BADCALL
_RET_BADFILES
_RET_INFOMISSING
_RET_BADINSTALL
No. Meaning
0 Process completed successfully.
Remarks
1 Process completed successfully, reboot required.
2 Process completed successfully, immediate reboot required
Linux only
3 Incorrect option
(s) or missing parameter(s).
Linux only
Solution Proposal
6 At least one file is not applicable.
Linux only
7 Missing information
8 Installation process failed.
Linux only
Table 13: ASP return codes
Local System Update for PRIMERGY Servers 119
6.4 ASP return codes
Error value
_RET_AC_CYCLE
_RET_NO_COMPONENT
_RET_WRONG_SYSTEM
No. Meaning
10 Process completed successfully, accycle required.
16 Target hardware not found.
17 Wrong target system.
18 Not sufficient permissions.
19
Remarks Solution Proposal
Unplug power cable for at least a minute.
_RET_NO_OVERWRITE_
PERMISSION
_RET_NOT_TERMINALSERVER_
CAPABLE
_RET_SV_AGENTS_NOT_
INSTALLED
_RET_PKG_NOT_INSTALLED
20 ServerView
Agents is not installed.
21 At least one required software package is not installed.
Install ServerView
Agents first.
Install needed software packages first.
_RET_KERNEL_MODULE_
MISSING
22 Required kernel module is not installed (ex.
driver module)
_RET_BITLOCKER_BLOCKED
_RET_TRUSTEXETEC_
BLOCKED
23 Execution prohibited due to active BitLocker.
24 Execution prohibited due to active Trusted
Execution
Technology
_RET_COMPETING_APPLICATION 25 Competing application is already installed.
Linux only Check log-files for getting more information about missing modules (ex.
tooltrace.txt).
Windows only
Disable BitLocker.
Disable Trusted
Execution Technology.
Uninstall competing application.
Table 13: ASP return codes
Local System Update for PRIMERGY Servers 120
6.4 ASP return codes
Error value
_RET_FATAL_ERROR
_RET_NO_ADMIN_RIGHTS
_RET_NOT_ON_VIRTUAL_
MACHINE
_RET_NOT_VMMS_CAPABLE
_RET_NOT_SUPPORTED_OS
_RET_NOT_SUPPORTED_
SUBSYS
_RET_NOT_SUFFICIENT_DISK_
SPACE
_RET_SHUTDOWN_VIRTUAL_
SYSTEMS
No. Meaning
55 Fatal error occurred.
56 Admin rights not sufficient.
57 Cannot be executed on a virtual machine.
Remarks
Linux only
Solution Proposal
Linux only Try again with "root" privileges.
58 ASPs cannot be used
- on PRIMERGY servers running
Hyper V, Xen or
VMware ESXi,
- on virtual machines.
60 A not-supported subsystem is attached with target controller
61 Not enough disk space.
Start Update Manager
Express by booting your PRIMERGY server from the Update DVD.
59 Operating system not supported.
Linux only Start Update Manager
Express by booting your PRIMERGY server from the Update DVD.
Please detach the storage subsystem and try again. Please note that only storage subsystems released by FTS can be attached to your host system.
Please assure that sufficient disk space is available for extracting the ASP.
62 Please shut down all virtual systems.
Please assure that no virtual system is active on the target server.
Table 13: ASP return codes
Local System Update for PRIMERGY Servers 121
6.4 ASP return codes
Error value
_RET_DOWNGRADE_
PROHIBITED
_RET_HIGHER_VERSION_
INSTALLED
_RET_UNFULFILLED_
PREREQUISITE
_RET_WRONG_PRIOR_VERSION_
INSTALLED
No. Meaning
63 Downgrade prohibited.
64 A higher version is already installed.
65 At least one unfulfilled prerequisite prohibits successful execution.
66 Wrong prior version installed.
Remarks Solution Proposal
Due to incompatibilities, downgrading
BIOS or firmware is not allowed.
Take a higher version than the one currently installed, or set option
"force" instead of
"update".
Check all conditions that must be fulfilled for successful execution.
Updating from currently installed version is not possible.
Please check whether an interim version must be installed prior to the desired version
Use the Force option instead.
_RET_ONLY_FORCED_
FIRMWARE_EXCHANGE
67 The Update option is not supported. No protection against unintended downgrades.
_RET_DRIVER_INSTALL_FAILED 68 Driver installation failed.
_RET_SOFTWARE_INSTALL_
FAILED
69 Software installation failed.
Table 13: ASP return codes
Local System Update for PRIMERGY Servers 122
Error value
_RET_POWERCYCLE
_RET_PFR_BLOCKED
6.5 Log file Setup.log (ASPs for Windows only)
No. Meaning
70 Process completed successfully, powercycle required.
71 Flash is rejected,
ASP cannot update specific version PFR model iRMC.
Remarks Solution Proposal
Update using iRMC's web interface or
Redfish interface.
Table 13: ASP return codes
6.5
Log file Setup.log (ASPs for Windows only)
After the installation, all ASP components except for the log file Setup.log
are deleted.
You can use this log file to analyze the processes within the executed ASP in the event of an error or sent it to a service partner.
Local System Update for PRIMERGY Servers 123
Download
Public link updated
The public link to your chat has been updated. You may view and manage your chat links after registration here.
Document public link
Advertisement
Key features
Update firmware and BIOS of PRIMERGY servers
Intuitive graphical user interface
Manage updates for multiple servers
PXE-based mass updates
Self-extracting and self-installing software packages (ASPs)
PRIMERGY Support Packages (PSPs) and the PrimeUp installation tool
Frequently asked questions
Update Manager Express is a GUI-based tool that allows you to easily update the firmware and BIOS of your PRIMERGY servers.
Update Manager Express provides a number of benefits, including the ability to manage updates for multiple servers, even if they are located in different locations, and support for PXE-based mass updates.
An ASP is a self-extracting and self-installing software package that can be used to update the firmware and BIOS of PRIMERGY servers.
A PSP is a PRIMERGY Support Package that can be used to update the firmware and BIOS of PRIMERGY servers.
To use Update Manager Express, you will need to download the software from the Fujitsu website and install it on your server. Once installed, you can launch Update Manager Express and begin managing updates for your servers.