Embed Size (px)
Citation preview
Installation and User Guide - English
FUJITSU Software ServerView Suite
ServerView Repository Server
Edition Februar 2018
Comments… Suggestions… Corrections…The User Documentation Department would like to know your opinion of this manual. Yourfeedback helps us optimize our documentation to suit your individual needs.
Feel free to send us your comments by e-mail [email protected].
Certified documentation according to DIN EN ISO 9001:2008To ensure a consistently high quality standard and user-friendliness, this documentation wascreated to meet the regulations of a quality management system which complies with therequirements of the standard DIN EN ISO 9001:2008.
cognitas. Gesellschaft für Technik-Dokumentation mbH
www.cognitas.de
Copyright and trademarksCopyright 1998-2017 FUJITSU LIMITED
All rights reserved.
Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective manufacturers.
Contents
1 Introduction 4
1.1 What's new 5
1.2 ServerView Suite link collection 6
1.3 Documentation for the ServerView Suite 7
1.4 Typographic conventions 7
2 Installing / uninstalling the Repository Server 9
2.1 Requirements for installation (Linux) 9
2.2 Installing the Repository Server 10
2.3 Uninstalling the Repository Server 11
3 Configuring the Repository Server and updating its functionality 12
3.1 Configuring the Repository Server 12
3.2 Updating the Repository Server 16
4 Working with the Repository Server 17
4.1 Running the Repository Server 17
4.2 Files needed for analyzing 18
4.3 Implementation issues 18
5 Using the Repository Server - scenarios 20
5.1 eLCM online/offline update via the iRMC S4/S5 web interface 20
5.2 ServerView System Monitor (on local node) 22
5.3 ServerView Operations Manager - Update Management 23
ServerView Repository Server 3
1 IntroductionThe ServerView Repository Server package, in the following referred to as Repository Serverfor short, provides a web server which contains the firmware repository for PRIMERGYservers and runs in your company's intranet.
The Repository Server performs the following tasks:
l The Repository Server keeps the firmware repository up-to-date by regularlydownloading the most recent updates from the Fujitsu web server(https://support.ts.fujitsu.com). Administrators may receive email messages informingthem of the download progress and error situations.
l The Repository Server enables the managed servers in your intranet to access thisregularly updated firmware repository without leaving the intranet. The (virtual)machine installed by the Repository Server software serves as a proxy server for thosemonitored managed nodes which do not have a connection to the Internet.
The download process which uses the Repository Server for maintaining the updaterepository is completely independent of the updating of the managed nodes. Themanaged nodes connect to the Repository Server to receive the necessary updates for theirfirmware components.
As an alternative to downloading the updates directly from the Fujitsu web server, theRepository Server therefore allows you to maintain a repository of firmware componentsdecentrally.
ServerView Repository Server 4
1.1 What's new
Figure 1: Repository Server
The Repository Server can also be used to provide the repository for the updatemanagement tools of the Fujitsu Software ServerView Suite, e.g. ServerViewembedded Lifecycle Management (eLCM), ServerView System Monitor, andServerView Update Manager.
With the ServerView Update Manager, the Management Station plays the role of amanaged node (see the figure above).
1.1 What's newThis edition of the manual "ServerView Repository Server" replaces the online manual"ServerView Repository Server", edition September 2017.
The manual features the following changes and enhancements:
l General optimization
l The section "Using the Repository Server - scenarios " on page 20 has been updated.
l The section "eLCM online/offline update via the iRMC S4/S5 web interface" on page 20has been updated.
l The section "ServerView System Monitor (on local node)" on page 22 has beenupdated.
ServerView Repository Server 5
1.2 ServerView Suite link collection
1.2 ServerView Suite link collectionVia the ServerView Suite link collection, Fujitsu provides you with numerous downloadsand further information on the ServerView Suite and PRIMERGY servers.
Under ServerView Suite, links are offered on the following topics:
l Forum
l Service Desk
l Manuals
l Product information
l Security information
l Software downloads
l Training
Software downloads includes the following downloads:
o Current software statuses for the ServerView Suite as well as additional Readmefiles.
o Information files and update sets for system software components (BIOS,firmware, drivers, ServerView Agents and ServerView Update Agent) forupdating the PRIMERGY servers via ServerView Update Manager or for locallyupdating 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 Service Desk
l Manuals
l Product information
l Spare parts catalogue
Access to the ServerView Suite link collection
You can reach the link collection of the ServerView Suite in various ways:
1. Via ServerView Operations Manager.
l Select Help – Links on the start page or the menu bar.
2. Via the start page of the online documentation for the ServerView Suite on the Fujitsumanual server.
ServerView Repository Server 6
1.3 Documentation for the ServerView Suite
You access the start page of the online documentation via the followinglink:
http://manuals.ts.fujitsu.com
l In the selection list on the left, select x86 Servers.
l On the right, click PRIMERGY ServerView Links under Selected documents.
3. Via the ServerView Suite DVD 2.
l In the start window of the ServerView Suite DVD 2, select the option ServerViewSoftware Products.
l On the menu bar select Links.
This opens the start page of the ServerView Suite link collection.
1.3 Documentation for the ServerView SuiteThe documentation can be downloaded free of charge from the Internet. You will find theonline documentation at http://manuals.ts.fujitsu.com under the link x86 Servers.
ServerView Sitemap
For an overview of the documentation to be found under ServerView Suite as well as thefiling structure, see the ServerView Suite Sitemap:
1. In the selection list on the left, select x86 Servers and then Software.
2. On the right, select ServerView Suite.
3. Click ServerView Suite Sitemap under Selected documents.
1.4 Typographic conventionsThe following typographic conventions are used:
Convention Explanation
Indicates various types of risk, namely health risks, risk of data lossand risk of damage to devices.
Indicates additional relevant information and tips.
bold Indicates references to names of interface elements.
monospace Indicates system output and system elements for example, filenames and paths.
ServerView Repository Server 7
1.4 Typographic conventions
Convention Explanationmonospacesemibold
Indicates statements that are to be entered using the keyboard.
blue continuoustext
Indicates a link to a related topic.
pink continuoustext
Indicates a link to a location you have already visited.
<abc> Indicates variables which must be replaced with real values.
[abc] Indicates options that can be specified (syntax).
[key] Indicates a key on your keyboard. If you need to enter text inuppercase, the Shift key is specified, for example,[Shift] + [A] for A. Ifyou need to press two keys at the same time, this is indicated by aplus sign between the two key symbols.
Screenshots
Some of the screenshots are system-dependent, so some of the details shown may differfrom your system. There may also be system-specific differences in menu options andcommands.
ServerView Repository Server 8
2 Installing / uninstalling the Repository ServerThe Repository Server is not available on Windows systems.
2.1 Requirements for installation (Linux)l This software is tested and released for the following Linux operating systems.
o RHEL 6.7 (EM64T)o RHEL 6.8 (EM64T)o RHEL 7.1 (EM64T)o RHEL 7.2 (EM64T)o CentOS 6.6 (x86, EM64T)
o CentOS 6.7 (EM64T)
o CentOS 6.8 (EM64T)
o CentOS 7.1 (EM64T)
o CentOS 7.2 (EM64T)
o Ubuntu 16.04 (EM64T)
l It is recommended to use a separate virtual machine for the installation.
l Make sure the /bin/bash directory can be found.
l User must be root.
l Free disk space requirement:o GlobalFlash repository: approximately 20 GB for LinkMode=0, 2 x 20 GB (or more)
for LinkMode=1
For LinkMode=1, additional disk space is required for the old componentversion. Therefore, more than 2 x 20 GB might be needed.
o eIM repository: approximately 7 GB per image
l The following RPM packages must be installed:
RHEL 6.7 64-Bit / RHEL 6.8 64-Bit / RHEL 7.1 64-Bit / RHEL 7.2 64-Bit/ CentOS 6.7 64-Bit/ CentOS 6.8 64-Bit / CentOS 7.1 64-Bit / CentOS 7.2 64-Bit
o libstdc++o httpd
ServerView Repository Server 9
2.2 Installing the Repository Server
o libcurl.x86_64o mod_sslo openssl.x86_64o sendmailo unzip
Ubuntu 16.04 64-bit
o libstdc++6:amd64
o sendmail
o apache2:amd64
o apache2-bin:amd64 (for mod_ssl)
o libxml2-utils (for xmllint)
Appropriate links to the necessary versions of the libraries are set in the /usr/lib64directory (for a 64-bit system) of user root.
Please install current versions of Sendmail and Apache Web Server if not yet present.
The services sendmail and httpd must be switched on for Runlevel 5.
All requirements are checked by the preinstall script.
Additional requirement for working with Repository Server via http protocol:
l ssl must be configured by the user.
This requirement is not checked by the preinstall script.
2.2 Installing the Repository ServerStart the installation of the Repository Server with the following command:
l On a 64-bit system:
rpm -i RepServer-<version>.x86_64.rpm
l Ubuntu:
sudo dpkg -i RepServer-<version>.amd64.deb
By installing the RPM package, the current Linux system becomes a Repository Server.
The /opt/fujitsu/ServerViewSuite/RepServer directory is created during the installationprocess. It contains all the executable and configuration files needed for the RepositoryServer.
After the installation process, the following configuration changes are made by thepostinstall script:
ServerView Repository Server 10
2.3 Uninstalling the Repository Server
l The rsyslog system logging interface is extended to include a new subdirectory for logfiles: /var/log/fujitsu/ServerViewSuite/RepServer
An entry is made in the /etc/rsyslog.conf file to redirect the log entries of the facilitylocal0 to the repserver.log file.
The rsyslog system logging is restarted to make the changes effective.
l Configuration changes for Apache Web Server in the /etc/httpd/conf/httpd.conf file.
l The first cron job is created and makes the following entry in the crontab of user root:
00 <installation hour + 2> * * 0-6 /opt/fujitsu/ServerViewSuite/RepServer/bin/downloadApplication.sh -t #$TAG.
The first download is scheduled to start at the earliest one hour after installationand is repeated every day at the same time.The first download may take more than 2 hours, as the complete repository isloaded.Subsequent downloads only take an average of 5 minutes, as only new andchanged versions are loaded.The required disk space for the local repository in the $RootRepPath directory is 20GB or more. Please check requirements in "Requirements for installation (Linux)" onpage 9. ($RootRepPath is defined in the configuration file, see below). For eIMrepository approximately 7 GB per image is needed.
2.3 Uninstalling the Repository ServerStart the uninstallation of the Repository Server with the following command:
l On a 64-bit system:
rpm -e RepServer-<version>.x86_64.rpm
l Ubuntu:
sudo dpkg -r RepServer
The current firmware repository remains unchanged while the package is removed.Please remove the repository manually if it is obsolete.
Reinstalling the Repository Server will restore the link from the Apache web page tothe former repository if it is left untouched! Therefore, an update installation willrenew the tools but it will update and provide the repository already present.
ServerView Repository Server 11
3 Configuring the Repository Server and updatingits functionalityOnce the installation process is complete, you must check the installation and modify theconfiguration values in the/opt/fujitsu/ServerViewSuite/RepServer/cfg/RepServer.conf configuration file to yourneeds.
If a newer Repository Server version is available, you can update your update repository'sfunctionality without any impact on the current firmware repository and Repository Serverconfiguration.
3.1 Configuring the Repository ServerOnce the installation process is complete, you must check the installation and modify theconfiguration values in the/opt/fujitsu/ServerViewSuite/RepServer/cfg/RepServer.conf configuration file to yourneeds.
The configuration file /opt/fujitsu/ServerViewSuite/RepServer/cfg/RepServer.conf consistsof two parts:
l The first section contains the parameters whose values you can change yourself.
l The second section contains internal parameters whose values should only bemodified by an expert user.
You can adjust the following parameters to your needs (see also the explanatory notes inthe configuration file):
l The Proxy settings for the download from the Fujitsu Download Server.
l The RootRepPath destination location for downloading.
l The LinkMode parameter for the download process, which allows you to set up therepository in a working directory.
o If LinkMode=1, a working directory is used for setting up the repository. Thisrequires additional storage space of more than 20 GB. At the end of the downloadprocess, the repository is switched to its destination location. Disadvantage:Required disk space is bigger than if LinkMode=0.
o If LinkMode=0, no working directory is used. Disadvantage: Repository lock is setfor a long time. Advantage: Disk space needed is lower than if LinkMode=1.
ServerView Repository Server 12
3.1 Configuring the Repository Server
l The RepositoryMode parameter for the download process, which allows you to setwhich repository you want to download:
o RepositoryMode = 0, only GlobalFlash repository
o RepositoryMode = 1, only eIM repository
o RepositoryMode = 2, GlobalFlash and eIM repository
By default, only the GlobalFlash repository is downloaded.
l LocalRepPath points to the directory where the info files from the root of the Fujitsurepository (e.g. versionTree.txt) are stored after downloading.
l LocalInstPath points to the directory where the files from the root of the eIM Fujitsurepository are stored after downloading.
l ExchangeRepPath is the location where the parameter tree (Gf_par_tree.exe)downloaded from Fujitsu server is extracted.
l ProvisioningRepPath
o If LinkMode=0, ProvisioningRepPath points to the local repository that can beaccessed from ServerView Operations Manager or from another client.
o If LinkMode=1, ProvisioningRepPath toggles between pointing to the publiclyaccessible repository and the repository the next download works on.
l ProvisioningAlternateRepPath (not used if LinkMode=0).
ProvisioningAlternateRepPath toggles between pointing to the publicly accessiblerepository and the working directory.
l The CronJob entry in crontab.
l The Email and SMTP parameter settings.It is recommended to add the SMTP server address and email recipients in order to getemail messages about the download progress.
Values in the expert section of the configuration file should be left unchanged toavoid damage (e.g. the modification of RootFujitsuRepServer may cause thefirmware download to be initialized!).
You may also modify the cron job in the crontab of root. But this will only take effect thenext time the download application is started. To make permanent changes for the cronjob, the CronJob parameter in the configuration file must be modified accordingly. This isbecause the download application will always restore the crontab entry from theconfiguration file the next time it is activated.
The configuration file is interpreted every time the download application is activatedmanually or by the cronjob scheduler.
ServerView Repository Server 13
3.1 Configuring the Repository Server
Example: RepServer.conf configuration file
An example of a RepServer.conf configuration file is shown below.
##########################################################################
# (c) Copyright 2017 FUJITSU LIMITED
# #
# Configuration file for Repository Server #
# #
# It will be read every time the Repository Server application #
# 'downloadApplication' is started. #
# #
##########################################################################
# Proxy settings for downloading from FTS server ...
ProxyServerMode=1
# flag indicating use of proxy server (0=no; 1=as defined here; 2=as predefined for Linux)
# in case of '2', the system environment variable 'http_proxy' is interpreted.
ProxyServer="proxy.pdb.fsc.net"
# IP address or name of proxy server to be used for update of repository
ProxyServerPort=81 # port of proxy server to be used for update of repository
ProxyServerUserid="" # userid for proxy server
ProxyServerPasswd="" # encrypted password for accessing proxy server
# Destination location for downloading ...
RootRepPath="/Disk2/Repository" # absolute path to base directory of local repository
# Parameter how to provide repository ...
LinkMode=0 # replace/switch accessible repository by link: 0=no; 1=yes
# Parameter what should be downloaded ...
RepositoryMode=0 # 0=only globalflash repository; 1=only eIM repository; 2=both
# Entry in crontab ...
CronJob="45 15 * * 0-6 /opt/fujitsu/ServerViewSuite/RepServer/bin/downloadApplication.sh -t
# $TAG" # Cron Job: min hour day month day_of_week command
# Emailing options...
EmailMode=2 # 0=no emails; 1=restricted to errors only; 2=all messages
EmailSender="[email protected]"
# email address of sender (if empty, use of default: "repository.server@$HOSTNAME")
ServerView Repository Server 14
3.1 Configuring the Repository Server
# Note: EmailSender must comply with the following format: "[email protected]"
# Take care that $HOSTNAME returns the full qualified name.
EmailRecipient[0]="[email protected]" # email address of recipient, e.g. "[email protected]"
#EmailRecipient[1]="" # email address of another recipient (the first empty EmailRecipient terminates the list)
SMTPHost="172.25.138.142" # IP address or name of SMTP server
SMTPPort= # SMTP port (if empty, use of default: 25)
SMTPAuthUser=""
SMTPAuthPassword=""
#########################################################################
# ATTENTION: Following parameters should only be changed by expert...
#
PKG=RepServer
RootFujitsuRepServer="/opt/fujitsu/ServerViewSuite/$PKG"
ApacheConf="/etc/httpd/conf/httpd.conf" # config file of web server
ApacheConfUbuntu="/etc/apache2/sites-available/000-default.conf" # config file of web server for Ubuntu
# FTS download server access ...
DownloadServer="support.ts.fujitsu.com" # address or name of Download Server
DownloadRepPath="DownloadManager/Globalflash" # relative path of download repository on FTS Download Server
InstallationServer="webdownloads.ts.fujitsu.com" # address or name of InstallationManager server
InstallationRepPath="InstallationManager/ImageFiles" # relative path of InstallationManager repository on FTS
InstallationManager server
# Locations ...
LocalRepPath="$RootRepPath/Download" # absolute path to root of currently downloaded repository catalog
LocalInstPath="$RootRepPath/InstallationManager" # absolute path to root of currently downloaded IM repository catalog
ExchangeRepPath="$RootRepPath/Exchange" # absolute path to root of exchange repository
ProvisioningRepPath="$RootRepPath/Provisioning" # absolute path to root of provisioning repository
ProvisioningAlternateRepPath="$RootRepPath/ProvisioningAlternate"
# absolute path to root of alternate provisioning repository
Logfile="$RootRepPath/downloadApplication.log" # path to logging of download progress
# Parameters used internally for download tasks ...
StopTxt="$RootFujitsuRepServer/cfg/Stop.txt" # lock file within repository
StopDownloadRetry=100 # number of retries for download of Stop.txt
StopDownloadWaitTime=180 # number of seconds to wait for Stop.txt to vanish
ServerView Repository Server 15
3.2 Updating the Repository Server
DownloadRetry=3 # number of retries for downloading a file from FTS repository
DownloadWaitTime=10 # number of seconds to wait for next retry of a file download
DowngradeMode=1 # how to handle downgrades (0=no downgrade; 1=downgrade)
3.2 Updating the Repository ServerThe Repository Server functionality is updated with the following command:
l On a 64-bit system:
rpm -U RepServer-<version>.x86_64.rpm
l Ubuntu:
sudo dpkg -i RepServer-<new_version>.amd64.deb
The current firmware repository and the former Repository Server configurationremain unchanged during the update.
It is not possible to update from a 32-bit version to a 64-bit version of RepositoryServer. Please uninstall the 32-bit version and install the 64-bit version.
ServerView Repository Server 16
4 Working with the Repository Server
4.1 Running the Repository ServerThe Repository Server does not have a graphical user interface.It is started periodically as a cron job by the Crontab Scheduler.
It can also be started manually from the console window using the command lineinterface:
downloadApplication [-t] [-i]
-tTrace flag on
-iInteractive flag on
downloadApplication -h displays the usage message.
The cron job can be called, for example, as follows:/usr/bin/downloadApplication.sh -t
Once correctly installed, the Repository Server does not need any monitoring ormaintenance.Any administrative actions will be done via the RepServer.conf configuration fileand the Linux operating system.
ServerView Repository Server 17
4.2 Files needed for analyzing
4.2 Files needed for analyzingThe following files are needed for analysis purposes:
l /opt/fujitsu/ServerViewSuite/RepServer/cfg/RepServer.conf (Repository Serverconfiguration file)
l /var/log/fujitsu/ServerViewSuite/RepServer/repserver.log (if configured in rsyslogconfiguration file /etc/rsyslog.conf)
l Trace files downloadApplication.log<id> and FileDownload.log<id> in the directoryspecified by $RootRepPath. The $RootRepPath variable set in the/opt/fujitsu/ServerViewSuite/RepServer/cfg/RepServer.conf configuration file.
To ensure that the trace files downloadApplication.log<id> andFileDownload.log<id> are created, proceed as follows:
1. Start the crontab editor from a terminal window:
crontab -e
2. Edit the crontab entry of downloadApplication by adding the trace option -t:
/opt/fujitsu/ServerViewSuite/RepServer/bin/
downloadApplication.sh -t
Trace files will be created as described above the next time this cron job isstarted.
4.3 Implementation issuesl The shell script downloadApplication.sh uses the (internal) FileDownload program todownload a single file from the Fujitsu web server:https://support.ts.fujitsu.com/DownloadManager/globalflash/
l The shell script downloadApplication.sh evaluates its configuration file to determinewhich update components are to be downloaded (variable DownloadVariant) to thelocal repository (variable RootRepPath).
Currently, "complete" is the only value allowed for the variableDownloadVariant.
The shell script downloadApplication.sh thereby works as follows:
1. The script evaluates the versionTree.txt file to see whether a download isnecessary. If yes, the versionAll.exe and gf_par_tree.exe files are downloaded andextracted into the location specified by $ExchangeRepPath. The gf_par_tree.exe
ServerView Repository Server 18
4.3 Implementation issues
file contains the parameter tree.
2. The script traverses the extracted parameter tree file by comparing each of itsleaves with the corresponding leaf of the local repository. Depending on thecomparison result, a leaf is deleted, downloaded, or remains unchanged in thelocal repository. A downloaded file is stored temporarily in $ExchangeRepPathand then copied to the working repository, which is $ProvisioningRepPath ifLinkMode=0 and a non-public repository if LinkMode=1.
This ensures that the newest repository changes on the Fujitsu web server aresynchronized with the local repository.
ServerView Repository Server 19
5 Using the Repository Server - scenariosA Repository Server can be used in several update management tools of the FujitsuSoftware ServerView Suite. In the scenarios described below, it is assumed that therepository URL is 172.17.167.63.
To use the Repository Server, the ports 80 and 443 are needed for access viahttp/https. Make sure these ports are open.
5.1 eLCM online/offline update via the iRMC S4/S5 webinterfaceThe iRMC S4/S5 can be configured to access an external Repository Server. eLCM updatemanagement functionality is based on the ability of the iRMC S4/S5 to automaticallydownload files from a Repository Server via the dedicated iRMC S4/S5 management LANport and store them packed as an ISO image on the iRMC S4/S5 SD card.
The user interfaces of the iRCM S4 and iRCM S5 differ from each other.
Figure 2: Repository Server used by the eLCM Update Management (example from iRCM S4)
ServerView Repository Server 20
5.1 eLCM online/offline update via the iRMC S4/S5 web interface
Figure 3: Repository Server used by the eLCM Update Management (example from iRCM S5)
See the manuals "iRMC S4 - Web Interface", "iRMC S5 - Web Interface" and "embeddedLifecycle Management (eLCM)" for details.
ServerView Repository Server 21
5.2 ServerView System Monitor (on local node)
5.2 ServerView System Monitor (on local node)In the Settings menu of the web-based ServerView System Monitor, you can define therepository path and the settings for the download and the update check.
Figure 4: ServerView System Monitor: Defining repository path and download settings
ServerView Repository Server 22
5.3 ServerView Operations Manager - Update Management
5.3 ServerView Operations Manager - Update ManagementIn the Download Settings step of the Configuration Wizard, you can define the proxysettings for the Download Service.
Figure 5: ServerView Operations Manager - Update Management: Proxy settings for the downloadservice
See the "ServerView Update Management" manual for details.
ServerView Repository Server 23
