User Guide - English Fujitsu Software ServerView Suite ServerView Update Management ServerView Operations Manager V6.
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 manuals@ts.fujitsu.com.
Contents Contents 3 1 Introduction 9 1.1 Concepts 10 1.2 Prerequisites 12 1.2.1 Prerequisites on managed servers 12 1.2.2 Prerequisites on connection blades 15 1.2.3 Prerequisites on systems with operating system ESXi (flash via iRMC S3 using cURL) 15 1.2.4 Prerequisites on TFTP server 16 1.2.5 Prerequisites on the Central Management Station (CMS) 17 1.2.5.1 Update Management Logon (OS=Windows) 17 1.2.5.2 Configuration of Update Management (Repository, …) 19 1.2.5.3 Update Data 19 1.
Contents 3.2.1 Updating a hardware system 3.2.2 Updating a system running a VMware ESXi operating system (flash via iRMC S3 using cURL) 3.3 Access to update data 4 Installing ServerView Update Agents 4.1 Installation on the managed server 4.1.1 Requirements for installation 4.1.2 Requirements for uninstallation 4.1.3 Installing Update Agent V6.0 (or later) 4.1.3.1 Installation under Windows 4.1.3.2 Installation under Linux or VMWare (ESX) 4.2 Installation on the TFTP server 4.2.
Contents 5.2.4.2 Import Repository Components dialog box 5.2.4.3 Import Repository Components - Results dialog box 5.2.4.4 Export Repository Components dialog box 5.2.4.5 Export Repository Components - Results dialog box 5.2.4.6 Delete Repository Components dialog box 5.2.4.7 Delete Repository Components - Results dialog box 5.2.4.8 PSP Details dialog box 5.2.4.9 Create Collection dialog box 5.2.4.10 Edit Collection dialog box 5.3 Download Manager Main Window 5.3.1 The tree structure 5.3.
Contents 6.1.4 Resetting the update agent of a server 6.1.5 Displaying the update log for a server 6.1.6 Displaying detailed information about an update 6.1.7 Managing jobs 6.1.7.1 Creating a job 6.1.7.2 Copying a job 6.1.7.3 Releasing a job 6.1.7.4 Deleting a job 6.1.7.5 Displaying detailed information about a job 6.2 Repository Manager 6.2.1 Opening Repository Manager 6.2.2 Closing Repository Manager 6.2.3 Editing updates 6.2.4 Releasing updates 6.2.5 Managing user-defined groups (Collections) 6.2.5.
Contents 7.1.1 Call Parameters 7.1.2 StartFlash (Command) 7.1.3 WaitForDone (Command) 7.1.4 Reboot (Command) 7.1.5 Cleanup (Command) 7.1.6 Cancel (Command) 7.1.7 Result Files 7.1.7.1 StartFlash (Event) 7.1.7.2 Ready (Event) 7.1.7.3 Cancel (Event) 7.1.7.4 SequenceError (Event) 7.1.7.5 ParamError (Event) 7.1.7.6 LogonError (Event) 7.1.7.7 MemoryError (Event) 7.1.8 Batch Files (Examples) 7.1.9 CLI Standalone 7.2 citfs.
ServerView Update Management
1 Introduction ServerView Update Management allows you to manage updates for the firmware and software components of PRIMERGY servers. Update Management comprises the following applications: l Update Manager provides a mechanism for managing updates and installing them on the monitored managed nodes.
1 Introduction 1.1 Concepts Update Management is based on a database concept where the GUIs and services communicate exclusively via the database: 1. The GUIs are used to define jobs for the services and write these jobs to the database. 2. The services retrieve their jobs from the database, process these in the background and write the results to the database. 3. The GUIs then display the results from the database.
1.1 Concepts The Update Service performs the following tasks: 1. It detects which updates are available for the individual PRIMERGY servers based on the inventories and repositories, and returns the result to the database so that this can be displayed in the GUI. 2. It uses the jobs you define in the GUI to transfer the updates from the repository to the PRIMERGY servers. These interrelationships are illustrated in the following graphic.
1 Introduction 1.2 Prerequisites You can get the applications ServerView Agents, ServerView Update Agent, ServerView Operations Manager from the: l ServerView Suite DVD 1 (bundled with PRIMERGY server) l Download section of the Fujitsu Technology Solutions Web server: http://support.ts.fujitsu.com 1.2.1 Prerequisites on managed servers Online server allows components to be installed only while the operating system is running. l ServerView Agents for Windows or Linux must be installed.
1.2 Prerequisites Security If you need security (configuration with AccountCheck) before performing an update on the managed server, you can either use Single Sign-On or you must specify a user group. l Single Sign-On Requirements: l o ServerView agents as of V 5.0 o ServerView update agent as of V 5.0 o The certificate from the Central Management Station (CMS) must be copied to the managed nodes.
1 Introduction If Linux was installed either manually or using ServerView Installation Manager <= 11.13.04, you have to perform the following activities: o Installing Emulex OCM package (Core or FUI) o Installing OEM drivers Ipwc, be2net, and be2scsi o In case of a 32-Bit operating system: Installing 32 Bit libHBAAPI by using HBA tools. o In case of a 64-Bit operating system: Installing 32-Bit libHBAAPI by using HBA tools Installing the 32-Bit library libnl.so.
1.2 Prerequisites 1.2.2 Prerequisites on connection blades To prepare a connection blade for update via Update Manager, configure it as follows: 1. Open the graphical user interface of the connection blade, e.g. via a browser: http:// 2. Security > Secure Shell: Set the following values: Admin Mode: Enable SSH Version 1: Disable SSH Version 2: Enable 1.2.
1 Introduction 1.2.4 Prerequisites on TFTP server A TFTP server is necessary for updating connection blades / management blades. l ServerView Agents for Windows or Linux >= V5.10 must be installed. l ServerView Update Agent (Windows >=V5.10.02, Linux >=V5.30-00) must be installed A TFTP server is also necessary for updating iRMC S3 firmware and/or BIOS on a VMware ESXi operating system.
1.2 Prerequisites 1.2.5 Prerequisites on the Central Management Station (CMS) On the central management station, ServerView Operations Manager must be installed. 1.2.5.
1 Introduction Administrative Tools – Local Security Policy – Security Settings – Local Policies – User Rights Assignment – Log on as a service The following applets use this logon and the ServerView Download Service: l Configuration Wizard l Download Manager l Repository Manager Format of the account l local account: \. recommended: .
1.2 Prerequisites 1.2.5.
1 Introduction There are two ways of maintaining the repository with the latest update data: l Automatic maintenance In the Download Manager, define a download task. The task periodically checks and downloads the latest update data via the internet for servers with inventory data. l Manual maintenance In the Repository Manager, import update data from the latest ServerView Suite - Update DVD.
1.3 Notes on management stations 1.3 Notes on management stations 1.3.1 Shutdown and restart A shutdown/restart of the management station is only permitted if there are no servers with the job status processing on the Server Details tab in the Update Manager. Jobs with the status waiting (Job Details tab) are executed after the management station has been restarted, when the Start Time is reached.
1 Introduction 1.3.3 Multiple management stations You can run multiple management stations in one network; however, these management stations must be responsible for different servers. This means that the server lists on the various management stations must be different. 1.4 Autonomous Support Packages (ASP) Autonomous Support Packages (ASPs) are self-extracting, self-installing software packages that allow you to install BIOS, firmware, agents or Addon-products on your server.
1.5 PRIMERGY Support Packages (PSP) 1.5.2 Components of a PSP Each PSP consists of the following elements: l A zip archive containing the drivers or software products as well as the files required to install the PSP l Release notes (relnotes.
1 Introduction 1.5.3 Product Detection of Primergy Support Packages Product detection is available for most PSPs. Requirements on the server: l Primergy Support Package FSC_SCAN l Tool PrimeUp >= V1.15.25 (up to Windows Server 2008) l Tool PrimeUp >= V1.17.01 (Windows Server 2012) The version of the PSP FSC_SCAN and the PrimeUp tool which comes with the repository must be installed.
1.5 PRIMERGY Support Packages (PSP) Case “Newer version installed” Example: The customer has installed a very new version of a product (perhaps beta), which is not actually produced as a PSP on the FTS site. A "fake" PSP with version "99.99.99.99" is created, to protect the customers product against accidental overwriting/ updating by Update Manager.
1 Introduction 1.5.4 Initial Installation of Primergy Support Packages Initial installation is possible for all PSPs. Requirements on the server: l Primergy Support Package FSC_SCAN l Tool PrimeUp >= V1.15.25 (up to Windows Server 2008) l Tool PrimeUp >= V1.17.01 (Windows Server 2012) The version of the PSP FSC_SCAN and the PrimeUp tool which comes with the repository must be installed.
1.6 Notes on deleting servers from the ServerList 1.6 Notes on deleting servers from the ServerList Deletion will be denied ... Deletion of servers from the ServerList will be denied if update jobs with Agent Status = busy and Job Details Status = transferring, transferred, flashing or flashed exist. Deletion will NOT be denied ...
1 Introduction 1.7 Typographic conventions The following typographic conventions are used in this manual: Convention Explanation Indicates various types of risk, namely health risks, risk of data loss and risk of damage to devices. Indicates additional relevant information and tips. bold Indicates references to names of interface elements. monospace Indicates system output and system elements for example, file names and paths.
1.8 ServerView Suite link collection 1.8 ServerView Suite link collection Via the link collection, Fujitsu Technology Solutions provides you with numerous downloads and further information on the ServerView Suite and PRIMERGY servers.
1 Introduction l Product information l Spare parts catalogue Access to the link collection You can reach the link collection of the ServerView Suite in various ways: 1. Via ServerView Operations Manager. l Select Help – Links on the start page or on the menu bar. This opens the start page of the ServerView link collection. 2. Via the start page of the online documentation for the ServerView Suite on the Fujitsu Technology Solutions manual server.
1.9 Documentation for the ServerView Suite For an overview of the documentation to be found under ServerView Suite as well as the filing structure, see the ServerView Suite sitemap (ServerView Suite – Site Overview).
ServerView Update Management
2 Overview ServerView Update Management allows you to remotely apply the latest updates of BIOS, firmware and drivers onto PRIMERGY servers. General usage 1. Configure Update Management (see also "Prerequisites on the Central Management Station (CMS)" on page 17) l The Base Configuration Wizard is used to configure Update Management.
2 Overview l The Base Configuration Wizard is not used to configure the Update Management step. o Go on to item 2 o Open one of the Update Management applets o Configuration Wizard: Configure all necessary values Note: Inventory data is collected automatically for all servers in the ServerList o Go on to item 4 and further items. 2. Add managed servers to the ServerList of ServerView Operations Manager. 3. Create Inventory data.
5. When the update job is completed, the inventory data and the repository are automatically compared again to ensure that the latest update data has been correctly applied to the managed server. When upgrading Update Management components please observe the following recommendation to prevent connection problems with the components. Recommended update sequence: 1. ServerView Update Manager 2. ServerView Update Agent on managed node 3.
ServerView Update Management
3 Update Procedures The Update Manager enables you to update drivers, ServerView agents, update agents, firmware and BIOS globally and locally on PRIMERGY servers. You can use the update procedures described below to do this. Which particular components can be updated with which procedure is described in the following files on the ServerView Suite DVD 1: Windows: SVSSoftware\Software\ServerView\Windows\GlobalFlash\Agents\ OnlineFlash\primlist_win.
3 Update Procedures 3.1 Online update This procedure allows you to update components under the control of the operating system that is currently running (Windows, Linux). In this case the Update Manager uses tools which are provided by the software vendors. Figure 2: Diagram of the update procedure (online) 1. The Inventory Manager creates inventories by collecting information on the installed software and firmware components of all servers in the server list and storing this information in a database.
3.1 Online update 4. The Update Manager fetches the update data required from the repository and defines the update jobs. In addition to the actual update data each online update job contains an update tool for the component concerned and the job control file with the required parameters. 5. The update jobs are transferred to the update agent (socket communication). 6.
3 Update Procedures 3.2 Update via TFTP server This procedure is used to update PRIMERGY system components which cannot be updated using the update tools available under Windows or Linux either at all or only with great effort, or to update autonomous hardware systems on which none of these two operating systems runs. These system components and hardware systems are updated via a ServerView Update Agent of the type TFTP Server.
3.2 Update via TFTP server 3.2.1 Updating a hardware system Updating a hardware system taking a management blade as an example Figure 3: Diagram of the update procedure (management blade via TFTP server) 1. The Inventory Manager on the management server uses SNMP commands to fetch the required inventory data from the management blade. When you are updating via the graphical user interface the data is presented on the graphical user interface. 2.
3 Update Procedures In the case of MMB BX400S1 and BX900 S1: Up to ServerView Operations Manager V6.10, communication was processed using SNMP. ssh login is evaluated as of Operations Manager V6.11. 4. The object-specific update job for the management blade is generated by the Update Manager. 5. The Update Manager transfers the update images and the update job (incl.
3.2 Update via TFTP server 3.2.2 Updating a system running a VMware ESXi operating system (flash via iRMC S3 using cURL) Updating a system running an ESXi system (flash via iRMC S3 using cURL): Figure 4: Diagram of the update (ESXi system via iRMC S3 using cURL) 1. The Inventory Manager on the management server uses CIM commands to fetch the required inventory data from the VMware ESXi host. (A pre-installed ServerView ESXi CIM provider is prerequisite.
3 Update Procedures (including the update handler and update tool) to the TFTP server and starts the update job (socket communication between the Update Manager and the update agent on the TFTP server). 5. The update agent starts the update handler, and this starts the update tool with the required parameters from the job control file supplied. 6. The update tool starts the dialog with iRMC S3 and transfers the required update images using cURL. 7.
3.3 Access to update data 3.3 Access to update data To update the managed servers the Update Manager requires the corresponding update data. This data is contained in an repository with the following subdirectories: Agent-Win Agent-Lx BladeSystem FibreChannelController LanController ManagementController PrimSupportPack-Win RemoteServiceBord ScsiController SystemBoard Tools The following options are available for accessing this data: l Via the directory Firmware on the Update DVD.
ServerView Update Management
4 Installing ServerView Update Agents To find out which servers are supported and which system components can be updated with the various update procedures please refer to the relevant files on the ServerView Suite DVD 1 under ServerView Suite – Software Products - ServerView – Maintenance & Update - Update (Supported Systems and Info columns). The ServerView Update Agent needs around 3 minutes to start up completely. 4.1 Installation on the managed server 4.1.
4 Installing ServerView Update Agents 4.1.2 Requirements for uninstallation If you want to uninstall ServerView Update Agent, ensure that all jobs on the involved systems (management server, TFTP server, managed server) are finished or deleted. Uninstallation sequence: 1. Uninstall ServerView Update Agent 2. Uninstall ServerView agents Several errors can occur if user does not use correct order of uninstallation.
4.1 Installation on the managed server 4.1.3 Installing Update Agent V6.0 (or later) 4.1.3.1 Installation under Windows The following procedures are available for installation: l Menu-Driven Installation (FTASetup.exe) l Installation via the Command Line Interface l Installation via ASP (Autonomous Support Package), SV Update Agent >=V5.50 Menu-driven Installation (FTASetup.exe) You start the installation via the FTASetup.
4 Installing ServerView Update Agents Figure 5: Security Settings Security Settings Account Check Specifies whether access authorization should be checked when the server is accessed. If this option is enabled, you can use access authorization via certificates or via standard login. User Group for Update Name of the local user group 50 l This option is mandatory for access authorization via standard login.
4.1 Installation on the managed server All users in this group are authorized to perform the update procedure. The user group GFUSER is preset. If you want to use the GFUSER group you must configure it under Windows. But you can also use any other user group. In the case of an update installation the default values are assigned to the existing configuration values. Installation via the Command Line Interface (FTASetup.
4 Installing ServerView Update Agents Installation via ASP (Autonomous Support Package), SV Update Agent >=V5.50 You start the installation via the installation package SVUpdateAgent_Win_ ASP_.exe, which you will find on the ServerView Update DVD under: Firmware - Agent-Win - SV-Update-Agent. You can install the update agent at the command level using the following command: start /wait SVUpdateAgent_Win_ASP_.exe 4.1.3.2 Installation under Linux or VMWare (ESX) Update agent version 4.
4.1 Installation on the managed server --nopreun --nopostun (only for update installations) If these options, which must always be specified together, are selected, the uninstallation routines do not run when an update installation takes place. Parameters already set in the update agent are retained. Update Agent >= V5.01 You start the installation via the installation package SVUpdateAgent_Lx_ V.
4 Installing ServerView Update Agents TraceFile= File in which the agent’s actions are logged when TraceLevel > 0. The directory must exist if given in . Default file name: /opt/SMAW/SMAWgfa/data/gf_agent.log TraceLevel= n = 0 (no tracing) n = 2 (tracing of errors) n = 3 (tracing of the commands) n = 5 (detailed tracing) Default TraceLevel = 2 Parameter changes only become effective after the /etc/init.d/globalflash restart command has been executed.
4.2 Installation on the TFTP server 4.2 Installation on the TFTP server The PXE or TFTP service should be stopped, if you use other PXE/TFTP services, because a parallel use of two services might cause problems. For how to install ServerView Update Agent, see section "Installing Update Agent V6.0 (or later) " on page 49. 4.2.1 Installation under Windows Installation sequence: 1. TFTP Server 2. ServerView Agents 3.
4 Installing ServerView Update Agents 4.2.2 Installation under Linux Installation sequence: 1. TFTP Server 2. ServerView Agents 3. ServerView Update Agent To install TFTP server l Install software package tftp l TFTP must be enabled (file /etc/xinetd.
5 User Interface The Update Management user interface comprises the interfaces of the individual applications. The Configuration wizard starts automatically the first time you open Update Management. This wizard allows you to make global settings for all applications. 5.
5 User Interface Figure 6: Update Manager Main Window The appearance of the tabs is determined by the entry you select in the tree structure.
5.
5 User Interface 5.1.1 The tree structure Figure 7: Update Manager tree structure The tree structure is on the left of the work area in the Update Manager and provides various views, divided into different groups, of the servers in a domain. You can filter these views within the groupings down to object and component level.
5.1 Update Manager Main Window Tree structure Groupings Servers Information about Servers within the domain All Servers All servers within the domain Groups Customized groups, which you created with the ServerList application The icon in front of the server or group symbol (like for Blade Servers, virtual systems, ...
5 User Interface Tree structure Groupings Servers (continued) Update mandatory Servers on which an update is urgently required Update recommended Servers on which an update is recommended In the groups Update mandatory and Update recommended, instead of update status icons, server icons are displayed, because the name of the group is the same as the name of the update status of the servers in the group. For a description of the icons, see the online help of the ServerBrowser application. 1.
5.
5 User Interface Tree structure Groupings Jobs Jobs defined for the update of the servers Root All Jobs All jobs, regardless of status Waiting Jobs Jobs that are waiting for the time to transfer the updates from the management server to the PRIMERGY servers Jobs in Progress Jobs that are currently in the update phase Ready Jobs Jobs that were executed without errors (if a restart is required after an update phase, this status is not displayed until the server has been restarted) Failed Jobs Jobs that fail
5.1 Update Manager Main Window 5.1.2 Server Details tab The Server Details tab displays information about servers, depending on what you have already selected in the tree structure. Tree structure Server Details Tab Servers Information about the selected servers Updates Servers for which the selected components are relevant Jobs Servers for which the selected jobs are relevant To open the tab, click the Server Details tab in the main window.
5 User Interface The columns in the table have the following meanings: Column Meaning Icon General update status of the server An update is not required. An update is recommended. An update is urgently required. To evaluate the General update status of server, the contents of the following groups are checked: l Unapplicable Updates l Upgrades l All Components:All newer updates present in the repository are checked.
5.1 Update Manager Main Window Column Meaning Agent Status Status of the update agent on the server ready The server is ready for the update phase. error An error occurred during the update phase. You must save the diagnostics about the failed job, then initialize the update agent with the Cleanup function. absent No update agent is installed on the server or the agent is not running. busy The server is currently in the update phase. unknown The agent status could not be determined.
5 User Interface Column Meaning Agent Access Access status of the update agent on the server granted Logon to the server has already been successfully completed. You have access to the server. restricted Access to the server is currently restricted. Log on must be performed with the appropriate user ID and password on the server. unrestricted Logon is not required to access the server.
5.1 Update Manager Main Window Column Meaning Job Status Status of the relevant jobs specified for the server Last Check done All components have been updated and the job is now completed. waiting The job is waiting to be executed (this is the status before the data transfer begins). processing The job is currently being executed. error Possible reasons: l The update of at least one component failed.
5 User Interface Buttons Complete Update Automatically establishes a list of all components that can be updated on the previously selected server. The Create Job wizard then opens, via which you start the update of the identified components. This button is only enabled if you are logged on as administrator. Logon Opens the Logon dialog box, where you can log on to selected servers. This button is only activated if you have selected one or more servers in the table.
5.1 Update Manager Main Window Show Updates Opens the Update Details tab to display update information about the selected server. 5.1.3 Update Details tab The Update Details tab contains information about updates. It comprises the following elements: l The update details list (tree structure) l A table that contains the updates that match your selection in the server list and update details list. To open the tab, click the Update Details tab in the main window.
5 User Interface The content of the update details list depends on the entry that you have already selected in the tree structure. Tree structure Update details list (Update Details Tab) Servers Displays the components belonging to the selected servers.
5.1 Update Manager Main Window Tree structure Servers (continuation) Update details list (Update Details Tab) In general, only the installed update versions contained in the underlying repository are displayed in the table. In the case of each upgrade, only the latest version is displayed in the table and, in the case of each downgrade, only the next older version found in the repository is displayed in the table.
5 User Interface Column Meaning Server Name Name of the server Category Group to which the component belongs Component Name of the component Installed Version Version of the installed update New Version Update version that is to replace the installed version Reboot Indicates whether the server is restarted after the components are updated. (Yes/No) In case of yes, it is strongly recommended to close / relocate all productive applications.
5.
5 User Interface 5.1.4 Job Details tab The Job Details tab displays information about jobs, depending on what you have already selected in the tree structure. Tree structure Job Details Tab Servers Job information for the selected servers Updates Combination not permitted Jobs Information about selected jobs To open the tab, click the Job Details tab in the main window.
5.1 Update Manager Main Window In the table, a context menu is available. To open the context menu, right-click an entry in the table. The columns in the table have the following meanings: Column Meaning Icon Status of the current jobs All components have been updated and the job is now completed. The job is waiting to be executed (this is the status before the data transfer begins). The job is currently being executed. Possible reasons: l The update of at least one component failed.
5 User Interface Column Meaning Status Current job status 78 waiting The job is waiting to be executed (this is the status before the data transfer begins). transferring The job is currently being transferred. transferred The job has been successfully transferred and is now waiting for the start of the update procedure. flashing The job is currently in the update phase. flashed The update has been performed successfully on the server.
5.1 Update Manager Main Window Column Meaning Start Time Time when the flash of the updates is started Severity Cumulated status of the updates contained in the job (the most critical status is shown in each case) recommended An update is recommended. mandatory An update is urgently required. normal An update is not required. Released Shows whether the job is released (yes) or not (no). Description Description of the job (comment).
5 User Interface 5.1.5 Dialog boxes and wizards Update Manager provides the following dialog boxes and wizards.
5.1 Update Manager Main Window 5.1.5.1 LogOn dialog box The LogOn dialog box allows you to log on to all servers that require user authentication (AgentAccess = restricted or not certified). To open the dialog box, choose any servers on the Server Details tab and click Logon. Figure 11: LogOn dialog box The table in the dialog box displays all servers you selected on the Server Details tab. All servers with restricted or not certified access status are selected automatically.
5 User Interface Column Meaning Agent Access Access status of the update agent on the server granted Logon to the server has already been successfully completed. You have access to the server. restricted Access to the server is currently restricted. Log on must be performed with the appropriate user ID and password on the server. unrestricted Logon is not required to access the server.
5.1 Update Manager Main Window check and set Password Checks the logon data and sets the access rights on the selected servers (if Manageable = yes). The password is valid for the current session. If the server is unavailable, the logon data is stored under the assumption that it is correct (if Manageable = no). Remove Server from List Removes the selected server from the displayed list.
5 User Interface 5.1.5.2 Cleanup Wizard You can use this wizard to clean up the update agent of a server if the agent status is error. Resetting the update agent may be necessary if a job stops with Job Status = error and the return text contains the message Pending Jobs. You can view the return text for a job by selecting the job on the Job Details tab and opening the Show Job Details dialog.
5.1 Update Manager Main Window The table displays all servers you selected on the Server Details tab. All servers with restricted or not certified access status are selected automatically. If you have selected servers with an access status other than restricted or not certified, Update Manager ignores attempts to log on to these servers.
5 User Interface User Authentication Login user ID and password for access control. This parameters are only required if the ServerView update agent on the managed node is configured with AccountCheck. If the server is to be updated via a TFTP server, enter user ID and password for access to the hardware (Management Blade, Connection Blade, iRMC S3 firmware / BIOS on a system running a VMware ESXi operating system).
5.1 Update Manager Main Window Enter TFTP step (Cleanup Wizard) Enter TFTP is the second step in the wizard. This step is only displayed if the cleanup runs via TFTP server (for example, in the case of a management blade or a connection blade). Figure 13: Enter TFTP step The table shows a subset of the servers selected on the tab. For the servers displayed here, cleanup will be done via the TFTP server.
5 User Interface Schedule Job step (Cleanup Wizard) Schedule Job is the last step in the wizard. Here you specify the time at which the cleanup is to be executed. Figure 14: Schedule Job step Make sure that the server on which the cleanup is to be performed is up and running at the time of execution. Job Name Unique name of the job Default: CLEANUP_ Description Description of the job as a comment (optional).
5.1 Update Manager Main Window 5.1.5.3 Server Details dialog box The Server Details dialog box provides detailed information relating to the server you selected on the Server Details tab. If you selected a server of the group Unsupported Servers or Unknown Servers, no server data will be displayed in this dialog. To open this dialog box, click Show Details on the Server Details tab.
5 User Interface Display Name Name of the server For a standalone server: For a blade server: - For a host system of a virtual system: -host For a guest system of a virtual system: - Update Type Method used to perform the update online Update is performed while the operating system is running.
5.1 Update Manager Main Window Agent Status Status of the update agent on the server ready The server is ready for the update phase. error An error occurred during the update phase. You must save the diagnostics about the failed job, then initialize the update agent with the Cleanup function. absent No update agent is installed on the server or the agent is not running. busy The server is currently in the update phase. unknown The agent status could not be determined.
5 User Interface Update Status Cumulated update status of the server (the most critical status is displayed in each case) normal An update is not required. recommended An update is recommended. mandatory An update is urgently required. Display Update Status Here you can forcibly change the value of Update Status, if necessary. For example, you can change the Update Status to normal (meaning an update is not required) if updates are recommended but you explicitly want the update job to skip this server.
5.1 Update Manager Main Window Job Status Status of the relevant jobs specified for the server done All components have been updated and the job is now completed. waiting The job is waiting to be executed (this is the status before the data transfer begins). processing The job is currently being executed. error Possible reasons: l The update of at least one component failed.
5 User Interface Operating Systems Information about the operating system Manageable Availability of the server yes The ServerView agent can be reached via SNMP. no The ServerView agent cannot be reached. Buttons Force Check A job with the name Check_xx is created (xx = sequence number). It performs another comparison (check) of the server inventory with the repository. This job is displayed on the Job Details tab. The dialog box will be closed automatically.
5.1 Update Manager Main Window 5.1.5.4 Create Job Wizard This wizard allows you to create new update jobs. The wizard comprises several dialog boxes to guide you through the individual steps. All required steps are displayed in the tree structure on the left. To open the wizard, choose any servers and updates on the Update Details tab and click Create Job. LogOn step (Create Job Wizard) LogOn is the first step in the wizard.
5 User Interface Column Meaning Server Name of the server Manageable Availability of the server Agent Access Access status of the update agent on the server granted Logon to the server has already been successfully completed. You have access to the server. restricted Access to the server is currently restricted. Log on must be performed with the appropriate user ID and password on the server. unrestricted Logon is not required to access the server.
5.1 Update Manager Main Window User Authentication Login user ID and password for access control. This parameters are only required if the ServerView update agent on the managed node is configured with AccountCheck. If the server is to be updated via a TFTP server, enter user ID and password for access to the hardware (Management Blade, Connection Blade, iRMC S3 firmware / BIOS on a system running a VMware ESXi operating system).
5 User Interface Change Version step (Create Job Wizard) Change Version is the second step in the wizard. The table displays all updates you selected on the Update Details tab.
5.1 Update Manager Main Window Enter Job Name step (Create Job Wizard) Enter Job Name is the third step in the wizard. Here you assign a name to the job. Figure 18: Enter Job Name step Job Name Unique name of the job Default: JOB_ Description Description of the job as a comment (optional) The following fields are provided for information purposes only. You cannot change the values.
5 User Interface Example: For one server entered in the job a reboot is necessary after the update (Reboot=yes), while for others no reboot is necessary (Reboot=no). In this case the Reboot field will show the string "---". If the parameters that should be displayed in the same field have the same value, this value will be displayed.
5.1 Update Manager Main Window Reboot Indicates, whether a reboot is required (Reboot=yes) after the job is executed or not (Reboot=no). auto (for components of the blade systems group only) The component itself decides whether a reboot is necessary or not. dynamic Indicates that the server can be restarted after the components have been updated. auto (for components of the blade systems group only) The component itself decides whether a reboot is necessary or not.
5 User Interface Figure 19: Enter TFTP step The table shows a subset of the servers selected on the tab. For the servers displayed here, update will be done via the TFTP server. Column Meaning Server Name of the server TFTP Address IP address of the TFTP server Temporary Flash Address Temporary IP address used for flashing the management blade (MMBS2 only) Change TFTP Address Click this button to change the IP address of the TFTP server for the selected server.
5.1 Update Manager Main Window Figure 20: Schedule Job step Make sure that the management station and the server on which the job is to run are up and running at the time of execution. Transfer Time Start time for transferring the job to the server. Immediate Starts the transfer as soon as you click Finish to exit the wizard. Later Starts the transfer at the specified time. Select date, hours and minutes.
5 User Interface Flash Time Start time of the update phase on the servers. Immediate after transfer Starts the update immediately after the transfer. Later Starts the update phase at the specified time. If the transfer phase is not finished at the specified time, the update begins immediately after the end of the transfer phase. Boot Time Start time of the server reboot (only if Reboot = yes or Reboot = dynamic).
5.1 Update Manager Main Window Immediate after flash The restart begins immediately after the end of the update phase. Later The restart begins at the specified time. If the update phase is not finished at the specified time, the restart begins immediately after the end of the update phase. The Boot Time option has no influence on the booting time of management blades and connection blades. Management blades and connection blades are booted immediately after a flash.
5 User Interface 5.1.5.5 Update Details dialog box The Update Details dialog box provides additional information about the update you selected in the table on the Update Details tab. The parameters displayed in this dialog box cannot be changed except Available Versions. If you selected a server of the group Unsupported Servers or Unknown Servers, no data will be displayed in this dialog. To open this dialog box, click Show Details on the Update Details tab.
5.1 Update Manager Main Window Component Name of the component. Installed Version The version that is currently installed. New Version The version that is to replace the installed version. Compare Installed Version Evaluates the version displayed in the New Version field: Newest The displayed version is newer than the installed version and, at the same time, is the newest version in the repository.
5 User Interface Vendor Severity Severity weighting of the update from the perspective of Fujitsu Technology Solutions. recommended An update is recommended mandatory An update is urgently required normal An update is not required Custom Severity Severity weighting of the update from your perspective. You can use this parameter to override the Vendor Severity setting.
5.1 Update Manager Main Window Applicable Text Explanation of why the component cannot be installed. Dependencies Displays dependencies that are to be noted in relation to the update. Buttons Show Relnotes Opens the predefined browser, showing the latest release notes. Show PSP Details (PSP = PRIMERGY Support Package) Displays information about the packages included in the selected update.
5 User Interface 5.1.5.6 PSP Details dialog box A PRIMERGY Support Package (PSP) is the basic element for installing and updating drivers and software products on your PRIMERGY server. A PSP comprises several packages, each containing the different versions of the same driver or software product. To open this dialog, click Show PSP Details in the Update Details dialog box or the Edit Update's Properties dialog box.
5.1 Update Manager Main Window Below this are blocks of information on the individual packages and their dependencies on other components. The packages are numbered consecutively within the PSP and are each displayed with their version. Dependencies All the dependencies together make up the requirements that have to be fulfilled before a package can be installed. For a package to be installed, ALL dependencies shown for it must be fulfilled.
5 User Interface 5.1.5.7 Copy Job Wizard You can use this wizard to copy a job to any server in the domain. The wizard comprises several dialog boxes to guide you through the individual steps. All required steps are displayed in the tree structure on the left. To open the wizard, select the job you want to copy on the Job Details tab and click Copy Job. Choose Server step (Copy Job Wizard) Choose Server is the first step in the wizard. Here you select the servers to which the job is to be copied.
5.1 Update Manager Main Window >> Copies all servers from the Possible Server list to the Destination Server list. > Copies the servers selected from the Possible Server list to the Destination Server list. < Moves the servers selected from the Destination Server list back to the Possible Server list. << Moves all servers from the Destination Server list back to the Possible Server list.
5 User Interface LogOn step (Copy Job Wizard) LogOn is the second step in the wizard. Here you log on to all servers that require user authentication (AgentAccess = restricted or not certified). Figure 24: LogOn step The table displays all servers you selected in the Choose Server step. If you have selected servers with an access status other than restricted or not certified, Update Manager ignores attempts to log on to these servers.
5.1 Update Manager Main Window Column Meaning Agent Access Access status of the update agent on the server granted Logon to the server has already been successfully completed. You have access to the server. restricted Access to the server is currently restricted. Log on must be performed with the appropriate user ID and password on the server. unrestricted Logon is not required to access the server.
5 User Interface check and set Password Checks the logon data and sets the access rights on the selected servers (if Manageable = yes). The password is valid for the current session. If the server is unavailable, the logon data is stored under the assumption that it is correct (if Manageable = no). Remove Server from List Removes the selected server from the displayed list.
5.1 Update Manager Main Window Enter Job Name step (Copy Job Wizard) Enter Job Name is the third step in the wizard. Here you assign a name to the job. Figure 25: Enter Job Name step Job Name Unique name of the job Default: JOB_ Description Description of the job as a comment (optional) The following fields are provided for information purposes only. You cannot change the values.
5 User Interface Example: For one server entered in the job a reboot is necessary after the update (Reboot=yes), while for others no reboot is necessary (Reboot=no). In this case the Reboot field will show the string "---". If the parameters that should be displayed in the same field have the same value, this value will be displayed.
5.1 Update Manager Main Window Reboot Indicates, whether a reboot is required (Reboot=yes) after the job is executed or not (Reboot=no). auto (for components of the blade systems group only) The component itself decides whether a reboot is necessary or not. dynamic Indicates that the server can be restarted after the components have been updated. auto (for components of the blade systems group only) The component itself decides whether a reboot is necessary or not.
5 User Interface Figure 26: Enter TFTP step The table shows a subset of the servers selected on the tab. Column Meaning Server Name of the server TFTP Address IP address of the TFTP server Change TFTP Address Click this button to change the IP address of the TFTP server for the selected server.
5.1 Update Manager Main Window Schedule Job step (Copy Job Wizard) Schedule Job is the last step in the wizard. Here you specify the time at which the job is to be executed. Figure 27: Schedule Job step Make sure that the management station and the server on which the job is to run are up and running at the time of execution. Transfer Time Start time for transferring the job to the server. Immediate Starts the transfer as soon as you click Finish to exit the wizard.
5 User Interface Flash Time Start time of the update phase on the servers. Immediate after transfer Starts the update immediately after the transfer. Later Starts the update phase at the specified time. If the transfer phase is not finished at the specified time, the update begins immediately after the end of the transfer phase. Boot Time Start time of the server reboot (only if Reboot = yes or Reboot = dynamic).
5.1 Update Manager Main Window Immediate after flash The restart begins immediately after the end of the update phase. Later The restart begins at the specified time. If the update phase is not finished at the specified time, the restart begins immediately after the end of the update phase. The Boot Time option has no influence on the booting time of management blades and connection blades. Management blades and connection blades are booted immediately after a flash.
5 User Interface 5.1.5.8 Job Details dialog box The Job Details dialog box provides a clear and detailed overview of information relating to the job you selected on the Job Details tab. If you selected a server of the group Unsupported Servers or Unknown Servers, no data will be displayed in this dialog. To open this dialog box, click Show Details on the Job Details tab. Figure 28: Job Details dialog box You may only change the Released parameter in this dialog box. No other parameters can be changed.
5.1 Update Manager Main Window Severity Cumulated severity weighting of the updates contained in the job. The highest severity weighting of an update is displayed (mandatory > recommended > normal).
5 User Interface transferring The job is currently being transferred. transferred The job has been successfully transferred and is now waiting for the start of the update procedure. flashing The job is currently in the update phase. flashed The update has been performed successfully on the server. rescanning The inventory of the server is being redetermined. rebooting The server is currently rebooting. done All components have been updated and the job is now completed.
5.1 Update Manager Main Window TFTP Adress IP address of the TFTP server Description Description of the job (comment) Return Text In the event of an error, this field contains the error message of the error that occurred. The error messages are described in section "Error messages in the Update Manager" on page 271.
5 User Interface Figure 29: Edit Job dialog box Job Name Name of the selected job. Released This setting specifies whether the job is released (yes) or not released (no) for execution on other PRIMERGY servers. Description Description of the job (comment).
5.1 Update Manager Main Window Transfer Time Start time for transferring the job to the server. Immediate Starts the transfer as soon as you click Finish to exit the wizard. Later Starts the transfer at the specified time. Select date, hours and minutes. Flash Time Start time of the update phase on the servers. Immediate after transfer Starts the update immediately after the transfer. Later Starts the update phase at the specified time.
5 User Interface Immediate after flash The restart begins immediately after the end of the update phase. Later The restart begins at the specified time. If the update phase is not finished at the specified time, the restart begins immediately after the end of the update phase. The Boot Time option has no influence on the booting time of management blades and connection blades. Management blades and connection blades are booted immediately after a flash. 5.1.5.
5.1 Update Manager Main Window Test Connectivity Tests if a connection can be established to the specified IP address using the "ping" function.
5 User Interface 5.2 Repository Manager Main Window Repository Manager allows you to administer the repository.
5.2 Repository Manager Main Window 5.2.1 The tree structure Figure 32: Repository Manager tree structure The tree structure, which is on the left, shows the updates that are available in the Repository Manager. In the tree structure, you select which data you want to display in the table on the Updates tab and the Collections tab. The tree structure is shown with the following groups, in which the relevant components are listed: All Updates All updates in the repository.
5 User Interface Updates By Severity All updates that are recommended (recommended) or urgently required (mandatory). Released Updates Updates that are explicitly released by the user. This group only appears if there is at least one "released" update. User Collections Customized groups, which you can create and manage on the Collections tab. This node does not appear if you have not yet defined any customized groups.
5.2 Repository Manager Main Window 5.2.2 Updates tab All entries belonging to the group you selected in the tree structure are displayed in the table on the Updates tab.
5 User Interface In the table, a context menu is available. To open the context menu, right-click an entry in the table. The columns in the table have the following meanings: Column Meaning Update status (icon) Urgency of the update An update is recommended. An update is urgently required. An update is not required. Category Name of the component group Opens the Filtering for dialog box, where you specify which rows are to be displayed in the table.
5.2 Repository Manager Main Window Column Meaning Reboot Required Shows whether server reboot is either required (yes) or not required (no) after the update. dynamic Indicates that the server can be restarted after the components have been updated. auto (for components of the blade systems group only) The component itself decides whether a reboot is necessary or not.
5 User Interface Delete Opens the Delete Repository Components dialog box, in which you can select components from your repository that you no longer need and that can be deleted. Deleting components is only possible if the current repository is located on a local HDD partition of your computer or on an external USB storage device. Deletion is only possible for components which do not belong to an update job.
5.2 Repository Manager Main Window 5.2.3 Collections tab The functions provided on the Collections tab allow you to create and manage customized update groups. The groups you create here are displayed under User Collections in the tree structure. If you have not yet created any groups, the tree structure will not contain a node for User Collections and the tab is also blank. Figure 34: Collections tab In the table, a context menu is available. To open the context menu, right-click an entry in the table.
5 User Interface Column Meaning Name Name and cumulated update status of the collection Collection contains at least one component for which an update is recommended. Collection contains at least one component for which an update is urgently required. Collection contains no components that needs updating. Name and update status of the component An update is recommended. An update is urgently required. An update is not required.
5.2 Repository Manager Main Window Column Meaning Reboot Required Indicates whether server reboot is either required (yes) or not required (no) after the update. dynamic Indicates that the server can be restarted after the components have been updated. auto (for components of the blade systems group only) The component itself decides whether a reboot is necessary or not.
5 User Interface 5.2.
5.
5 User Interface Category The group to which the component belongs. Component Name of the component. Version Update version. Operating System The relevant operating system. Version Details Details of the update version. Reboot Required Indicates whether server reboot is either required (yes) or not required (no) after the update. dynamic Indicates that the server can be restarted after the components have been updated.
5.2 Repository Manager Main Window Vendor Severity Severity weighting of the update from the perspective of Fujitsu Technology Solutions. recommended An update is recommended mandatory An update is urgently required normal An update is not required Released Releases the selected updates (yes) for execution on other PRIMERGY servers ( for example, after they have been processed without errors on a test host) or not (no). Custom Severity Severity weighting of the update from your perspective.
5 User Interface Show PSP Details (PSP = PRIMERGY Support Package) Displays informations about the packages included in the selected update. 5.2.4.2 Import Repository Components dialog box To open this dialog box, click Import on the Updates tab. If you want to replace your complete repository, do this using the Configuration Wizard.
5.2 Repository Manager Main Window Importing components is only possible if the current repository is located on a local HDD partition of your computer or on an external USB storage device. You can update your repository on the management station by importing new components from a local or remote repository, e.g. the ServerView Update DVD or another existing repository, to the current repository.
5 User Interface Import Path Absolute path of the directory to be imported. This directory may be the root of an existing repository or any subdirectory. The Browse button is only enabled, if you started the ServerView Operations Manager on the management station directly. Check for Imports Checks the directory defined in the Import Path field for available components. All found components are displayed in the Source list on the left.
5.2 Repository Manager Main Window 5.2.4.3 Import Repository Components - Results dialog box Figure 37: Import Repository Components - Results This dialog shows the result of importing components into the current repository.
5 User Interface Category Name of the component group. Component Name of the component. Version Version of the update. Result ok Component has been imported. error Import failed. ErrorMessage Explanation why the import failed.
5.2 Repository Manager Main Window 5.2.4.4 Export Repository Components dialog box To open this dialog box, click Export on the Updates tab. Figure 38: Export Repository Components dialog Exporting components is only possible if the current repository and the target directory are located on a local HDD partition of your computer or on an external USB storage device. In the Source list on the left, all components of the current repository are displayed.
5 User Interface First, select the absolute path of the directory where the desired components should be exported to. This directory may be located on a local HDD partition of your computer or on an external USB storage device. Then copy the components you want to be exported from the Source list to the Destination list. To export the selected components, click OK. While the components are exported, a progress bar is displayed.
5.2 Repository Manager Main Window 5.2.4.5 Export Repository Components - Results dialog box Figure 39: Export Repository Components - Results dialog This dialog shows the result of exporting components from the current repository to the selected export directory.
5 User Interface Category Name of the component group. Component Name of the component. Version Version of the update. Result ok Component has been exported. error Export failed. ErrorMessage Explanation why the export failed.
5.2 Repository Manager Main Window 5.2.4.6 Delete Repository Components dialog box To open this dialog box, click Delete on the Updates tab. Figure 40: Delete Repository Components dialog Deleting components is only possible if the current repository is located on a local HDD partition of your computer or on an external USB storage device. Deletion is only possible for components which do not belong to an update job.
5 User Interface In the Source list on the left, all components of the current repository are displayed. Select the components which should be deleted in the Source list and copy them to the Destination list. To delete the selected components, click OK. While the selected components are deleted, a progress bar is displayed. If you abort the process by clicking Cancel, the delete process will be stopped and the result dialog box will show all components which are already deleted.
5.2 Repository Manager Main Window 5.2.4.7 Delete Repository Components - Results dialog box Figure 41: Delete Repository Components - Results dialog This dialog shows the result of deleting components from the current repository.
5 User Interface Category Name of the component group. Component Name of the component. Version Version of the update. Result ok Component has been deleted. error Delete process failed. in use The component was not deleted, because it is used in an update job. ErrorMessage Explanation why the delete process failed.
5.2 Repository Manager Main Window 5.2.4.8 PSP Details dialog box A PRIMERGY Support Package (PSP) is the basic element for installing and updating drivers and software products on your PRIMERGY server. A PSP comprises several packages, each containing the different versions of the same driver or software product. To open this dialog, click Show PSP Details in the Update Details dialog box or the Edit Update's Properties dialog box.
5 User Interface Below this are blocks of information on the individual packages and their dependencies on other components. The packages are numbered consecutively within the PSP and are each displayed with their version. Dependencies All the dependencies together make up the requirements that have to be fulfilled before a package can be installed. For a package to be installed, ALL dependencies shown for it must be fulfilled.
5.2 Repository Manager Main Window 5.2.4.9 Create Collection dialog box In the Create Collection dialog box, you can create customized update groups, which are displayed in the Update Manager on the Update Details tab under User Collections. To open this dialog box, click Create on the Collections tab. Figure 43: Create Collection dialog box Name Name of the customized update group. Description Description of the customized update group (comment).
5 User Interface Source The component groups that are available for selection. Destination The component groups that were copied to the user-defined group. >> Transfers all component groups to the user-defined group. > Transfers the selected component groups to the user-defined group. < Deletes the selected component groups from the user-defined group. << Deletes all component groups from the user-defined group. Undo Undoes the action last performed in the dialog box.
5.2 Repository Manager Main Window 5.2.4.10 Edit Collection dialog box You can edit a selected customized update group in the Edit Collection dialog box. To open this dialog box, click Edit on the Collections tab. Figure 44: Edit Collection dialog box Name Name of the customized update group (cannot be changed) Description Description of the customized update group (comment). Source The component groups that are available for selection.
5 User Interface Destination The component groups that were copied to the user-defined group. >> Transfers all component groups to the user-defined group. > Transfers the selected component groups to the user-defined group. < Deletes the selected component groups from the user-defined group. << Deletes all component groups from the user-defined group. Undo Undoes the action last performed in the dialog box.
5.3 Download Manager Main Window 5.3 Download Manager Main Window Use the Download Manager to define download tasks, configure when and how often these are to be executed, and activate the download task by assigning selected servers to it. You can also display information on download tasks already executed.
5 User Interface The main window of the Download Manager contains the following sections, from top to bottom: l the ServerView Suite header l the ServerView Suite menu bars l the work area, with a tree structure on the left and various tabs on the right 5.3.1 The tree structure Figure 46: Download Manager tree structure The area on the left of the Download Manager contains a tree structure showing all servers in a domain and the customized groups.
5.3 Download Manager Main Window All Servers Shows the servers in a domain which are supported by the current Update Manager. Groups Shows the groups defined by the user. Server icons The icon in front of a server or group symbol (like for Blade Servers, virtual systems, ...) indicates the cumulated update status of the corresponding server / group: No updates or updates with Severity = normal are required. Updates with Severity = recommended are required. Updates with Severity = mandatory are required.
5 User Interface Figure 47: Task Management tab In the table, a context menu is available. To open the context menu, right-click an entry in the table. Active Shows whether or not at least one server is assigned to the download task. Time Unit Shows a summary of the download schedule entered for the download task. Servers Shows the names of the servers assigned to the download task.
5.3 Download Manager Main Window Buttons Add ... Starts a dialog box in which you specify a new download task. Edit ... Starts a dialog box in which you can change the download task selected in the table. Delete Deletes the download task selected in the table. However, you can only delete a download task if NO servers are assigned to it. Activate ... Starts a dialog box in which you can assign one or more servers to the download task selected in the table.
5 User Interface 5.3.3 Scheduled Tasks Tab This tab contains an overview of the servers available in a domain. The Schedule column shows whether the server was assigned to a download task, and if so, to which one. By selecting certain servers or groups in the tree structure (left), you can restrict the number of servers shown in this tab. Figure 48: Scheduled Tasks tab In the table, a context menu is available. To open the context menu, right-click an entry in the table.
5.3 Download Manager Main Window Server icons The icon in front of a server or group symbol (like for Blade Servers, virtual systems, ...) indicates the cumulated update status of the corresponding server / group: No updates or updates with Severity = normal are required. Updates with Severity = recommended are required. Updates with Severity = mandatory are required. Undefined, no existing inventory available. Name Shows the name of the server. Group Shows the name of the server group.
5 User Interface Next Run Shows when a search for updates will next be performed. Buttons Once Immediately Click this button to start a search for updates for the servers selected in the table. Deactivate Removes the server selected in the table from the assigned download task. 5.3.4 Log Files Tab This tab contains information on download tasks already completed.
5.3 Download Manager Main Window In the table, a context menu is available. To open the context menu, right-click an entry in the table. The columns in the table have the following meanings: Status icon OK - Last download task performed was successful Error - last download task performed failed Time Shows when the download task was started. Name Shows the name of the server. Result Shows when the log file was created. Group Shows the name of the server group for group tasks.
5 User Interface Buttons View Shows the log file of the download task selected in the table. Delete Deletes the log file of the download task selected in the table. Delete All Deletes all log files. This button remains inactive as long as a check or download is running.
5.3 Download Manager Main Window 5.3.5 Dialog boxes The Download Manager provides the following dialog boxes. l Add Download Server Tasks dialog box l Edit Download Server Task Settings dialog box l Activate Download Server Tasks dialog box 5.3.5.1 Add Download Server Tasks dialog box In this dialog box, you specify when and how often a download task will be executed, and whether the related log files are to be saved. You open the dialog box on the Task Management tab by clicking Add....
5 User Interface Select Date and Time to Start You specify when the download task is to be executed here. now Starts the download task as soon as it has been activated. later Starts the download task at the specified time. Select the date, hour, and minutes. Frequency You specify how often the download task is to be executed here. Once Execute download task once Hourly Execute download task hourly (This option is currently not available.
5.3 Download Manager Main Window Buttons Create Saves the values entered for the download task and closes the dialog box. Close Discards the values entered and closes the dialog box. Help Opens the help for the current dialog box.
5 User Interface 5.3.5.2 Edit Download Server Tasks dialog box In this dialog box, you change the setting that specifies when a download task is executed and how many of the related log files are to be saved. To open the dialog box for a previously selected download task, click Edit ... on the Task Management tab. Figure 51: Edit Download Server Tasks dialog box Select Date and Time to Start You specify when the download task is to be executed here.
5.3 Download Manager Main Window Frequency You can see how often the download task is to be executed here. The value can only be changed as long as no server is assigned to this download task. Once Execute download task once Hourly Execute download task hourly (This option is currently not available.
5 User Interface 5.3.5.3 Activate Download Server Tasks dialog box In this dialog box, you assign one or more servers to a download task. To open the dialog box for a previously selected download task, click Activate ... on the Task Management tab. Figure 52: Activate Download Server Tasks dialog box The output field at the top of the window shows a summary of the values specified for the download task.
5.3 Download Manager Main Window Buttons >> Copies all servers from the list on the left to the list of servers assigned to the download task on the right. > Copies the servers selected in the list on the left to the list of servers assigned to the download task on the right. < Removes the entries selected in the list on the right from the list of servers assigned to the download task. << Removes all entries from the list of servers assigned to the download task from the right-hand side of the window.
5 User Interface 5.4 Configuration Main Window The main window contains the following elements (from top to bottom): l the ServerView Suite header l the ServerView Suite menu bars l the work area with the tabs The Mail Settings and the Download Settings tab are disabled (grayed out) if you have set a remote repository for updating your software. You only need these tabs if you want to update your local repository via the Download Service (Download Manager).
5.4 Configuration Main Window 5.4.1 General Settings Tab The configuration parameters listed below are displayed on the General Settings tab. To modify the properties click Change Configuration. Figure 53: General Settings tab Repository State State of the repository ok File system repository and database table UpdateRepository are complete incomplete Copy to file system failed.
5 User Interface Repository Location Absolute path of the repository. Default TFTP Address IP address of a TFTP server (for components that are updated via TFTP server, e.g. management blades or connection blades). Default Boot Duration The length of time that Update Manager waits for an updated server to restart after reboot. The time you enter here is added to the length of time the server is unavailable during the update. If the duration is exceeded, the job is set to status error.
5.4 Configuration Main Window 5.4.2 Mail Settings Tab The Mail Settings tab is disabled (grayed out) if you have set a remote repository for updating your software. You only need this tab if you want to update your local repository via the Download Service (Download Manager). The Mail Settings tab displays the mail settings for the persons who are to be informed about new updates downloaded via the Download Service. To modify the properties click Change Configuration.
5 User Interface Mail To Recipient address(es) of the e-mail If more than one address is entered, they are separated by commas. CC Additional recipient addresses If more than one address is entered, they are separated by commas. From E-mail address of the sender SMTP Server IP address of the SMTP server Port Port number of the SMTP server User User ID for logging on to the mail server Password Password for logging on to the mail server Buttons Change Configuration Starts the Configuration wizard.
5.4 Configuration Main Window 5.4.3 Download Settings Tab The Download Settings tab is disabled (grayed out) if you have set a remote repository for updating your software. You only need this tab if you want to update your local repository via the Download Service (Download Manager). The Download Settings tab shows the details of the connection to the web server of Fujitsu Technology Solutions via which the Download Service is to download new updates.
5 User Interface Download Web Address URL of the web server use by the Download Service. Default is the web server of Fujitsu Technology Solutions. Protocol used for transferring data from web server Type of the protocol used The comment displays the current kind of connection.
5.4 Configuration Main Window 5.4.4 Configuration Wizard You use this wizard to configure the global parameters for Update Management. The wizard has several steps. All required steps are displayed in the tree structure on the left. By choosing Next or Previous, you can navigate the wizard from step to step. If a step contains mandatory parameters, Next is deactivated until you have entered the required values. This wizard opens automatically the first time you access Update Management.
5 User Interface 5.4.4.1 Start step (Configuration Wizard) Start is the first step in the wizard. Figure 56: Start step Repository Specifies whether 190 l a new repository is to be created. l an existing repository is to be used.
5.4 Configuration Main Window 5.4.4.2 Repository step (Configuration Wizard) The selection you made at the Start step (use an existing or create a new repository) determines which fields are displayed in this step. Use existing Repository Figure 57: Use Existing Repository step Repository on Management Station The repository is located on the local management station. Repository Location Absolute path of the repository on the management station. Format for Windows: :\\...
5 User Interface The Browse button is only enabled, if you started the ServerView Operations Manager on the management station directly. Repository on Network Drive The repository is located on an other system in the network. Repository Location (UNC Path) Absolute path of the repository on the network drive For Windows: UNC notation should be used \\\\ User User name on the system in the network where the repository is located.
5.4 Configuration Main Window 1. Reboot the management station. 2. In the ServerView Operations Manager open the Configuration applet . 3. Click Change Configuration. 4. In the Start step, select Use existing Repository. 5. Enable option Repository on Network Drive. 6. Enter User and Password. Important: Do not open any other applets before finishing these steps.
5 User Interface Create Repository Figure 58: Create Repository step The Browse button is only enabled, if you started the Operations Manager on the management station directly. Import from DVD Imports the repository from the ServerView Update DVD. Source Path Absolute path of the repository to be imported on the DVD. The Browse button is only enabled, if you started the ServerView Operations Manager on the management station directly.
5.4 Configuration Main Window Download from Web Server Loads the repository from the web server of Fujitsu Technology Solutions. Repository Location Absolute path of the repository on the management station. If the specified directory does not exist yet, it is created. If the specified directory already exists, a warning will be issued. If you proceed, all files and directories in the specified directory will first be deleted. Then the repository is created in the specified directory.
5 User Interface 5.4.4.3 Miscellaneous step (Configuration Wizard) Figure 59: Miscellaneous step Default TFTP Address IP address of a TFTP server (for components that are updated via TFTP server, for example, management blades or connection blades). Change Opens the Change IP Address dialog box, where you can enter a new TFTP address and test the establishment of a connection to the new TFTP address. Default Boot Duration The length of time that Update Manager waits for an updated server to reboot.
5.4 Configuration Main Window 5.4.4.4 Download Settings step (Configuration Wizard) In this step you define the proxy settings for the Download Service. Figure 60: Download Settings step HTTP / HTTPS Select the type of the protocol you want to use for transferring data from the web server. Web Server Enter the URL of the web server for the Download Service. Default is the web server of Fujitsu Technology Solutions.
5 User Interface Do not use proxy server Enable this option if you want to use the Download Manager without a proxy server. The Download Manager will then ignore all proxy settings. Use predefined proxy settings defined on Management Station Enable this option if you want to use the proxy settings defined on the Management Station. This option is only available under Windows.
5.4 Configuration Main Window Mail Service If you enable this option, the next step will be Mail Settings. The persons you define in step Mail Settings are to be informed by email about new updates that have been downloaded by the Download Service. If this option is disabled, the next step will be Activate. 5.4.4.5 Mail Settings step (Configuration Wizard) This step is only displayed if you selected the Mail Service option in the previous step.
5 User Interface Mail To Recipient address(es) of the e-mail If more than one address is entered, they are separated by commas. CC Additional recipient addresses If more than one address is entered, they are separated by commas.
5.4 Configuration Main Window 5.4.4.6 Activate step (Configuration Wizard) Activate is the last step in the wizard. Figure 62: Activate step Activate Activates parameter changes in the database. If you have changed the repository, the inventory data of all servers is recreated. The new repository data is read into the database. If you selected to use a remote repository, this can take a long time (depending on your network).
5 User Interface To use the old repository again, start the configuration wizard. In the Start step, select use existing repository In the Repository step, specify the old repository.
5.5 Filter dialog box 5.5 Filter dialog box You can specify which table entries are displayed in a table using the tabs in the Filtering for Column dialog box. Tables display all rows by default. You can filter a table based on a column and: l a specific value (Standard tab) l a value range, which may comprise several values (Customize tab) To open the dialog box, click the filter icon in a table header. A filter icon is displayed for each column that can be filtered. 5.5.
5 User Interface 5.5.2 Character strings (Filter dialog box) You can enter a character string on the Customize tab. A corresponding table row is displayed for each value in the selected column that coincides with this character string. Figure 64: Tab for character strings in the Filter dialog box column pattern The character string serves as a filter criterion.
5.5 Filter dialog box 5.5.3 Integer values (Filter dialog box) You can enter a specific number range on the Customize tab. A corresponding table row is displayed for each value in the selected columns that coincides with this number range. Figure 65: Tab for integer values in the Filter dialog box List with logical operators and an input field for the first integer in the range, which you can use to formulate a condition.
ServerView Update Management
6 Managing Updates The applications in Update Management enable effective management of updates for your servers and their components. 6.1 Update Manager Update Manager allows you to install and update firmware and software components within a domain on PRIMERGY servers using a central management station. Initial installation is possible for drivers and add-on products.
6 Managing Updates 6.1.2 Closing Update Manager You can close the Update Manager by closing the main window. l To close the Update Manager main window, click the Close icon in the browser window. 6.1.3 Logging on to the Server You must log on to servers that have restricted or not certified access status in order to obtain access to these. 1. On the Server Details tab, select the server that you want to log on to, see "Server Details tab" on page 65. 2. Click Logon. The Logon dialog box opens. 3.
6.1 Update Manager 6.1.4 Resetting the update agent of a server If the update agent of a server is terminated with an undefined status, it may be necessary to reset the agent using the Cleanup function. The update agent must be reset, for example, if a job ends with the error Pending Jobs. After a Cleanup without errors, the update agent is fully functional again and can execute new update jobs. 1. On the Server Details tab, select the relevant server, see "Server Details tab" on page 65. 2. Click Cleanup.
6 Managing Updates If a connection to the server cannot be established, this is indicated by Manageable = no. In this case, the logon data is saved under the assumption that it is correct. The access status changes from restricted (or not certified) to trusted. As soon as the server can be reached again, the status changes from trusted to granted and the password is valid for the current session. 6. Click Next. The Enter TFTP step opens. This step is only displayed if the cleanup runs via TFTP . 7.
6.1 Update Manager 6.1.5 Displaying the update log for a server 1. On the Server Details tab, select the relevant server, see "Server Details tab" on page 65. 2. Click Show Details. The Show Server Details dialog box is displeyed. 3. Click History. A web page opens with information about all jobs that have been run on the server. 6.1.6 Displaying detailed information about an update 1.
6 Managing Updates 6. You can further restrict your selection from the tab in the table on the left of this dialog box. If you have also selected servers that have an access status other than restricted, these also appear in the table. However, logging on to these servers has no effect. 7. Enter your user ID and password under User Authentication. 8. Click check and set password. l If a connection to the server can be established, this is indicated by Manageable = yes.
6.1 Update Manager 16. Check the IP address of the TFTP server in the TFTP Address field. The value that you configured using the Configuration Wizard is displayed as the default. If you want to change the TFTP address, click Change TFTP Address. The Change TFTP Address dialog box opens. Enter the IP address of the TFTP server you want to use. Click OK to confirm your changes. 17.
6 Managing Updates 3. Select a server to which the job is to be copied from the Possible Server list. 4. Click >. The selected server is copied to the Destination Server list. 5. Repeat steps 3 and 4 for each server to which you want to copy the job. 6. Click Next. The LogOn step opens. 7. Log on to all servers that require user authentication (Agent Access = restricted or not certified). 8. Click Next. The Enter Job Name step opens. 9. Assign a name to the job in the Job Name field. 10.
6.1 Update Manager 6.1.7.3 Releasing a job If you establish that jobs can be processed without errors (for example, after a test run on a test computer), you can indicate that these jobs are released. This is for information purposes only and indicates that the jobs can be executed without errors on the individual PRIMERGY servers. 1. On the Job Details tab, select the jobs that you want to release, see "Job Details tab" on page 76. 2. Click Release. The Confirmation dialog box opens. 3.
6 Managing Updates 6.2 Repository Manager The Repository Manager has the following characteristics: l It recognizes the relevant update information in the repository l It can change properties of the update information (for example, severity) l It can release updates l It can import the Firmware file directory from the ServerView Update DVD. An import of components with the same version from the DVD overwrites the contents of the repository. 6.2.
6.2 Repository Manager 6.2.3 Editing updates You can edit the individual updates. 1. Select a group in the tree structure. 2. Go to the Updates tab in the Repository Manager, see "Updates tab" on page 135. 3. Select the update you want to edit. 4. Click Edit. The Edit Update's Properties dialog box opens. 5. Change the required properties of the update. 6. Click OK to confirm your changes. The dialog box closes and the changed properties are applied to the update. 6.2.
6 Managing Updates 6.2.5 Managing user-defined groups (Collections) You can use the following procedures to manage user-defined groups. 6.2.5.1 Creating a user-defined group To create a user-defined group, follow the steps below: 1. Go to the Collections tab in the Repository Manager, see "Collections tab" on page 139. 2. Click Create. The Create Collection dialog box opens. 3. Assign a name to the new group under Name. 4. Assign a comment describing the group under Description. 5.
6.2 Repository Manager 5. Edit the group. 6. Click OK to confirm your changes. The dialog box closes and the changes are assigned to the selected component groups and components in the ServerView database. 6.2.5.3 Releasing updates in a user-defined group You can release updates once a test update has been completed with satisfactory results for the components in your user-defined group. You cannot undo this command. If you want to undo the release, you must edit each update. 1.
6 Managing Updates 4. Click Delete. The Repository Manager opens a dialog box where you must confirm deletion with Yes. 5. To confirm deletion, click Yes. The dialog box closes and the group is deleted. All assignments entered by Repository Manager in the ServerView database are also deleted. 6.2.6 Re-Initializing the Repository You can update your repository on the management station by importing new components from the ServerView Update DVD or another existing repository.
6.2 Repository Manager 6. Click OK to confirm the import. All selected update components will be added to the existing repository on the management station if they did not exist before. If an older version of a component exists the newer version is additionally added to the local repository. When the process is finished the result of importing components into the current repository is shown. 7.
6 Managing Updates 6.3 Download Manager The Download Manager provides you with a convenient way to get the latest versions of firmware, BIOS, drivers, and ServerView agents for your server. The Download Manager relieves you of the task of performing time-consuming searches for suitable update information. Information and update files are provided on the web server of Fujitsu Technology Solutions for your server update. The Download Manager first loads the information files to a download directory.
6.3 Download Manager Change the value of the ConcurrentJobsAllowed parameter. The default value is 30. The maximum value is 99. The value 0 is not advisable, as it allows an infinite number of parallel download tasks. When using a small database system with reduced concurrent access, the value should be set to 5. 4. Start the Download Service. If you upgrade the Download Manager software, the value of the ConcurrentJobsAllowed parameter will be reset to the default value. 6.3.
6 Managing Updates 6.3.3 Opening Download Manager There are two ways to open the Download Manager in the ServerView Operations Manager: l On the start page of ServerView Suite, choose Download Manager under Update Management. l In the ServerView menu bar, choose Update Management/Download Manager. The main window of Download Manager is displayed. 6.3.4 Closing Download Manager Use the Close icon in the browser window to close the main window of the Download Manager. 6.3.
6.3 Download Manager 6.3.6 Assigning servers to a download task In order to use a download task, you assign the required servers to it. 1. Go to the Task Management tab. 2. In the table, select the download task you want to use for your server(s). 3. Click Activate ... . The dialog box for assigning servers is displayed. 4. In the list on the left, select the server(s) you want to assign to the download task. 5. Click >. The servers selected in the list on the left are shown in the list on the right. 6.
6 Managing Updates 6.3.8 Deleting a download task If you no longer need the download task, you can delete it. However, you can only delete a download task if NO servers are assigned to it. 1. Go to the Task Management tab. 2. Select the download task you want to delete in the table. 3. If servers are still assigned to the download task, remove this assignment by clicking Deactivate. All the services assigned to the download task are stopped. 4. Then click Delete.
6.4 Configuration 6.3.10 Managing log files The Log Files tab shows information on download tasks already completed. Show log file l If you want to display the entire log file, select the log file in the table and click View. Delete log file 6.4 l If you want to delete log files, select them in the table and click Delete. l If you want to delete all log files, click Delete All.
6 Managing Updates 6.4.2 Closing the configuration To close the configuration, close the main window. l To close the configuration main window, click the Close icon in the browser window. 6.4.3 Setting Global Parameters This procedure allows you to configure the global parameters for Update Management. You use the Configuration wizard to do this, which opens automatically the first time you access Update Management. 1. Click Change Configuration.
6.4 Configuration Create Repository 4. Specify the location from where the new repository is to be loaded: l from the ServerView Update DVD (Import from DVD) l from the web server (Download from Web Server) 5. If you want to import the repository from DVD, select Import from DVD and enter the absolute path of the repository on the DVD in the Source Path field.
6 Managing Updates Use Existing Repository 4. Enter the location of the repository: l on the local management station (Repository on Management Station) l on a system in the network (Repository on Network Drive) 5. Enter the absolute path of the repository in the Repository Location field in UNC notation. 6. If the repository is on an other system in the network: Enter the name and password of the user on the system in the User and Password fields. 7. Click Next. The Miscellaneous step opens. 8.
6.4 Configuration 14. Click Next. If you selected the Mail Settings option, the Mail Settings step opens; otherwise the Activate step opens. In this case, skip the next steps and continue with 24. 15. Enter the recipient address(es) in the Mail To field. Multiple addresses must be separated by commas. 16. Enter the additional recipient addresses if necessary in the CC field. 17. Enter the mail address of the sender in the From field. 18. Enter the IP address of the SMTP server in the SMTP Server field. 19.
6 Managing Updates 6.5 Filtering a table You can use the values or value ranges in a specific column to filter the entries in a table. A filter icon on the right of the table header indicates which columns can be filtered: . To filter the entries in a table, follow the steps below: 1. Click the filter icon next to the column. The Filtering for Column dialog box opens with the Standard tab displayed, "Standard (Filter dialog box)" on page 203. 2.
7 Command-Line Interface The Command-Line Interface (CLI) in Update Manager provides a scripting environment for updating system components, and is part of the ServerView Operations Manager. The CLI is installed automatically with the Update Manager. The Command-line interface consists of two parts: 7.1 l GFCLI, commands and parameters l citfs.
7 Command-Line Interface Parameter Description -C (Cleanup) Checks whether all update jobs are finished. If so, the update jobs are deleted. -A (Cancel) Deletes unfinished update jobs -H (Help) Displays the command syntax If the managed server is protected by access control, you must specify the parameters -L and -P when you use the CLI. These parameters are only used for the StartFlash, Cleanup and Cancel commands, which change the status.
7.1 GFCLI (Command-Line Interface) -W (WaitForDone command) Waits for the end of the update jobs (Job Status = READY or REBOOT) -R (Reboot command) Starts an explicit restart. -C (Cleanup command) Checks whether all update jobs are finished (Job Status = READY). If so, the update jobs are deleted. -A (Cancel command) Deletes unfinished update jobs. -H Displays the command syntax. -D The StartFlash only updates Microsoft-certified system components as standard.
7 Command-Line Interface -M Specifies that the managed system is a management blade server. The parameters -T and -I must also be specified to enable communication with the TFTP server (the latter parameter is only required in the StartFlash) command. -B Specifies that the managed system is a connection blade server. The parameters -T and -Z must also be specified.
7.1 GFCLI (Command-Line Interface) When ServerView Operations Manager is installed the Inventory file can be found in the working directory of the Update Manager following the subdirectory "versionviewsav/" -K SNMP Community String if not public. -V IP address of the VMware ESXi host -u Login user ID for access control of the VMware ESXi host -p Login password for access control of the VMware ESXi host 7.1.
7 Command-Line Interface Parameter -O is risky! This parameter should only be used by persons who have detailed knowledge of the repository used and of the dependencies between the installed versions. If, for example, a version of a component in the repository is older than the installed version, the installed version is downgraded in this case. The command ends as soon as all steps to start the update are completed. The command does not wait for the update procedure to be completed.
7.1 GFCLI (Command-Line Interface) Return values 0 Update started without errors. 1 Ok, no obsolete components found. 2 Timeout (no connection to the managed server). 3 SequenceError - command is not permitted during this phase. 4 An error occurred when the update phase was started. 5 GFI error 6 The required parameters for access control do not exist. 7 Access denied 10 Parameter error 11 Memory bottleneck 12 Multiple starting of CLI denied. 13 The results file (option -F or logfile.
7 Command-Line Interface 7.1.3 WaitForDone (Command) Syntax GFCLI -W -N [-F ] [-M -T ] [-B –Z -T ] [-E -T -Y ] Description WaitForDone returns a return value of 0, 4, 8 or 9 if all update jobs have been processed (with or without errors). In contrast to the Cleanup command, the update results are not deleted on the managed server when this command is executed.
7.1 GFCLI (Command-Line Interface) Return values 0 Update Ok (job status is READY) All update jobs have been executed without errors. 1 No current job exists (connection established) 2 Timeout (no connection to the managed server) 3 SequenceError - command is not permitted during this phase (a job has PREPARED status) If a GlobalFlash Agent up to V 4.71 is installed on your system, please notice the additional description below.
7 Command-Line Interface Update job using GlobalFlash Agent up to V 4.71 When you start an update job, the following dialog is displayed on the managed server: If the dialog is answered with Cancel, the command GFCLI -W(=WaitForDone) returns the value 3. In , the message Flash Cancelled by User is logged. To cleanup the managed server, the following command has to be used: GFCLI -A -S (=Cancel, forced variant) 7.1.
7.1 GFCLI (Command-Line Interface) Return values 0 Immediate reboot initiated 1 No current job exists (connection established) 2 Timeout (no connection to the managed server) 3 SequenceError - command is not permitted during this phase. - Flash boot status is not Online Reboot required or - no job found with the status REBOOT 5 GFI error 6 The required parameters for access control do not exist.
7 Command-Line Interface 7.1.5 Cleanup (Command) Syntax GFCLI -C -N [-F ] [-L [-P ]] [-M -T ] [-B –Z -T ] [-E -T -Y ] Description Cleanup executes the same steps as WaitForDone, but also deletes the update results on the managed server and completes the update procedure. The managed server returns to its original status and the update results are no longer available on the server.
7.1 GFCLI (Command-Line Interface) Return values 0 Update Ok (job status is READY) All update jobs have been executed without errors. 1 No current job exists (connection established) 2 Timeout (no connection to the managed server) 3 SequenceError - command is not permitted during this phase (a job has PREPARED status) 4 Update with errors (job status is READY) At least one job could not be executed without errors. 5 GFI error 6 The required parameters for access control do not exist.
7 Command-Line Interface Description Cancel cancels the execution of the update jobs that have already been transferred to the managed server, and deletes the PREPARED update status. The PREPARED status may exist if another user has used the GUI to execute a Prepare Updates but has not yet executed an Execute Updates; or in the case of an exception, which only arises if an error has occurred. If a connection cannot be established, the command is terminated with a timeout after a maximum of 60 seconds.
7.1 GFCLI (Command-Line Interface) 7.1.7 Result Files All results of an update procedure are written to the specified results file. In this case, the results are added, which means that the files increase in size. You must manage (delete or rename) these results files yourself. The information is contained in the files in the form of event blocks. In the case of the StartFlash, Cleanup, and Cancel commands, the results are also written to the GFLog.txt log file.
7 Command-Line Interface Job Statuses The following statuses are documented for each individual job in the specific results file: PREPARED The update job has been transferred to the server. WORKING The update job is currently being executed. REBOOT The update job has been processed correctly. A reboot is required to become Job Status = READY READY The update job has been processed (correctly or with errors). 7.1.7.1 StartFlash (Event) The StartFlash event normally contains the Count sub-event.
7.1 GFCLI (Command-Line Interface) Event.0=StartFlash Event: StartFlash SubEvent.0=Count Sub-event: Count CompCount.0=1 Number of components (may be 0) NoError.0=0 Number of errors Event.1=StartFlash Event: StartFlash SubEvent.1=Result Sub-event: Result ObjTypeName.1=MAH3091MC Object type (component) ObjName.1=Disk:PCI1.11.1.SCSI0.0.0 Relevant object OldVersion FW.1=5207 Old FW/BIOS version of the object NewVersion FW.1=5208 New FW/BIOS version of the object LastCommand.
7 Command-Line Interface Examples Error executing AddJob; the list contains error codes for each component. Event.0=StartFlash SubEvent.0=Count CompCount.0=1 NoError.0=1 Event.1=StartFlash SubEvent.1=Result ObjTypeName.1=MAH3091MC ObjName.1=Disk:PCI1.11.1.SCSI0.0.0 OldVersion FW.1=5207 NewVersion FW.1=5208 LastCommand.1=AddJob Error.1=91 ErrorText.
7.1 GFCLI (Command-Line Interface) 7.1.7.2 Ready (Event) If the CLI detects the READY job status after it is started, the return values of all updated components appear as follows: Event.0=Ready Event: Ready SubEvent.0=Count Sub-event: Count CompCount.0=2 Number of components (may be 0) NoError.0=0 Number of errors Event.1=StartFlash Event: Ready SubEvent.1=Result Sub-event: Result ObjTypeName.1=DAC1164P Object type (component) ObjName.1=SCSIController:PCI6.8.1 Relevant object Type.
7 Command-Line Interface Error.2=0 ErrorText.2=ERROR[0] faultless execution 7.1.7.3 Cancel (Event) Event.0=Cancel Event: Cancel Error.0=0 Error number in the event of an error ErrorText.0=ERROR[0] faultless execution Description of the return value 7.1.7.4 SequenceError (Event) This event has no sub-events. This event indicates that a command cannot be executed because Update Manager has an incorrect status. Examples l An update status should not exist when StartFlash is called.
7.1 GFCLI (Command-Line Interface) 7.1.7.5 ParamError (Event) This event has no sub-events. This event indicates that an unauthorized parameter was used for the specified command. All parameters are checked each time the CLI is called. If unauthorized parameters are used, one line is used to specify where the problem occurred in each case. Event.0=ParamError Incorrect number/combination of parameters or an invalid update path. 7.1.7.6 LogonError (Event) This event has no sub-events.
7 Command-Line Interface 7.1.8 Batch Files (Examples) The following examples are based on Windows. If a Linux shell is used, the Linux variable $? must be queried instead of the %errrorlevel% Windows variables in order to test the return value of the CLI command, for example: GFCLI -S -N -U if [ $? = 0 ]; then .... File 1 @echo off rem ******************************************************** rem * cli-exa.
7.1 GFCLI (Command-Line Interface) rem rem ******************************************************* rem * WaitServerlist initialisation rem * (WaitServerList: temporary subset of Serverlist) rem ******************************************************** rem if exist svwaitls.txt del svwaitls.txt if exist oklist.txt del oklist.
7 Command-Line Interface parameters rem * of the fields in WaitServerList (subset of ServerList) rem ******************************************************** rem if not exist svwaitls.txt goto doneall :waitnxt if exist del svtmpls.txt for /F "eol=; tokens=1-3 delims=, " %%i in (svwaitls.txt) do call cliwork %%i %%j %%k if not exist svtmpls.txt goto doneall copy svtmpls.txt svwaitls.txt goto waitnxt :doneall @echo All activities done.
7.1 GFCLI (Command-Line Interface) File 2 rem ********************************************************* rem * cli-init.bat ************************ rem * **************************************************** rem * Batch File to check states of a special server rem * and to execute StartFlash if states are ok rem * -----------------------------------------------------rem * Input-parameters: rem * - cli-init server(%1) user(%2) Password(%3) rem * - File "fwpath.
7 Command-Line Interface if %errorlevel%==7 goto noaccess if %errorlevel%==10 goto parerror if %errorlevel%==11 goto memerror if %errorlevel%==0 goto old-ok @echo. @echo Undefined returncode! goto endchk rem rem ******************************************************** rem * Old Flashs (prepared) detected Cancel them rem ******************************************************** rem :statenok @echo.
7.1 GFCLI (Command-Line Interface) rem ******************************************************** rem * Old Flashs (ready) detected CleanUp them rem ******************************************************* rem :old-ok @echo. @echo Flash States "ready"(without errors) for server %1 available rem :old-nok @echo.
7 Command-Line Interface :c-oldnok @echo. @echo CleanUP - Jobs detected not all ok goto start1 rem rem ******************************************************** rem * Errors in Check phase rem ******************************************************** rem :nothtodo @echo. @echo CleanUp or cancel- No flash states ????? goto endchk rem :timeout @echo. @echo - Timeout goto endchk rem :statenok @echo. @echo CleanUp, cancel or StartFlash- Wrong state goto endchk rem :gfierror @echo.
7.1 GFCLI (Command-Line Interface) rem :nologop @echo. @echo - No logon parameters goto endchk rem :noaccess @echo. @echo - access denied goto endchk rem :parerror @echo. @echo - Parameter error goto endchk rem :memerror @echo. @echo - Memory error goto endchk rem :nostates for /F %%i in (fwpath.
7 Command-Line Interface if %errorlevel%==0 goto stflok @echo. @echo Undefined returncode! goto endchk rem :nothtodo rem rem ******************************************************** rem * "StartFlash"- nothing to do ! - All componentsare up to date rem ******************************************************** rem @echo Server %1: "StartFlash"- nothing to do ! - All components are up to date @echo %1 -Nothing to do - Actual Firmware already installed >>oklist.
7.1 GFCLI (Command-Line Interface) File 3 rem ******************************************************** rem * cli-work.
7 Command-Line Interface :timeout @echo. @echo - Timeout Server %1 - Go on waiting for a minute @echo %1,%2,%3 >>svtmpls.txt goto endwk rem rem ******************************************************** rem * In case of error after flash, no Cleanup is done rem * Error situation has to be analyzed (see return-file) rem ******************************************************** rem :readynok @echo.
7.1 GFCLI (Command-Line Interface) if %errorlevel%==11 goto memerror if %errorlevel%==0 goto cu-ok @echo. @echo Undefined returncode! goto endwk rem rem ******************************************************** rem * All component of the server were flashed without error rem * Clean up is done - the Server is set to OK-list rem ******************************************************** rem :cu-ok @echo.
7 Command-Line Interface @echo CleanUp or WaitForDone- Wrong state ??? goto endwk rem :gfierror @echo. @echo CleanUp or WaitForDone - gfi error ??? goto endwk rem :nologop @echo. @echo CleanUp or WaitForDone - No logon parameters ??? goto endwk rem :noaccess @echo. @echo CleanUp or WaitForDone - access denied ??? goto endwk rem :parerror @echo. @echo CleanUp or WaitForDone - Parameter error ??? goto endwk rem :memerror @echo.
7.2 citfs.bat (batch job) 7.1.9 CLI Standalone There is a seperate product "UpdateManagerCLI" that is deliberately meant for environments where there is no ServerView Operations Manager. But because there is no SVOM there is one major restriction, when running under Linux and intending to update a management blade or connection blade: As documented in description of the call parameters (Y option) the Inventory of the management blade or connection blade must exist as a file (VersionView.
7 Command-Line Interface To execute the tool, open a command prompt and change to specified directory (see above). citfs.bat { }[ ][force] Description of the parameters IP-Addr IP-Address of the new server. servername Name of the new server. community SNMP-community string. User / Password Login user ID and password for access control. This parameters are only required if the ServerView update agent on the managed node is configured with AccountCheck.
7.2 citfs.bat (batch job) Restrictions l The repository path might not be a network path. l Only standard PRIMARGY server can be integrated, l Blade server or ESXi systems cannot be integrated.
ServerView Update Management
8 Troubleshooting 8.1 Error messages in the Update Manager Below is an overview of the error messages displayed in the Return Text field in the Job Details dialog box (see "Job Details dialog box" on page 124). For each message there is a description of the action you can take to eliminate the error. APPL_CURRENTLY_RUNNING Internal overlap of program runs Action l In the Job Details dialog, click Show Logfile.
8 Troubleshooting add job failed Job initialization error cleanup failed Job cannot be deleted flash failed Error while updating the managed server flash timeout Timeout during completion of the job manager timeout Timings exceeded in Update Manager prepare update failed Job transfer error reboot failed Error while booting the managed server Action l In the Job Details dialog, click Show Logfile.
8.1 Error messages in the Update Manager could not transfer job(s) Job initialization error pending jobs Job is in progress or has not been cleaned up update process aborted Update process was aborted because the CMS was booted Action l Execute the CLEANUP function (see "Cleanup Wizard" on page 84). l Copy the errored job and restart it.
8 Troubleshooting Flash Cancelled by User User aborted Flash Abort dialog with Cancel Action l Restart the update (via Create Job or Copy Job) after consulting the user of the updating server. Applies: o Managed server with operating system Windows o GlobalFlash Agent Win <=V4.71.
8.1 Error messages in the Update Manager job canceled by second failover Error due to multiple switching of the high availability Cluster Action l Execute Cleanup. l Copy the job and restart it. ERROR_DC_DATA Rescanning error caused by Inventory Task Action l Within applet Inventory Manager > tab Manage Diagnostics, check the inventory log-file. o Select the corresponding server name in the tree view. o In the table, select the task Once Immediately with Description = Inventory Data.
8 Troubleshooting 8.2 Error messages in the Download Manager If the Download Service has stopped working due to missing credentials or other reasons the following will occur: l Scheduled download tasks will not be started l Once immediate tasks will remain in the status running All defined tasks will be executed automatically after the ServerView Download Service is started again. For trouble shooting, please, see "Error messages in the Configuration Wizard" on page 280.
8.2 Error messages in the Download Manager No supported and manageable server in group The group of servers that was assigned for the download task does not contain supported manageable servers. Download action is not started, logging file is not created. Task aborted The download task is aborted. Logging file may not be created. Task aborted due to timeout The download task is aborted due to a timeout. Task time not determined The task time cannot be determined.
8 Troubleshooting Initialization error The download action could not be started successfully. Logging file is not created. Possible reason: missing access permissions in the file system (for creating/removing file or directory in workdir or repository directory). Download error The file download from the web server failed. Uncompression error The uncompression of the downloaded files failed. Network problems The download from the web server failed due to network problems.
8.2 Error messages in the Download Manager 6. Check the ServerView agents on the server. Remote Access to Repository failed Remote access to the repository failed. Update Check Failed The update check failed.
8 Troubleshooting 8.3 Error messages in the Configuration Wizard The following error message can occur after activating the configuration task: Configuration task has not been started on Central Management Station. Please, check if ServerView Download Service is stopped and restart the service. For more details, check system event log messages with source 'ServerView Update Manager'. It may be that ServerView Download Service has no credentials for accessing database ServerViewDB.
8.3 Error messages in the Configuration Wizard l Check via the Task Manager if the DownloadServer.exe process is still running . The process retries several times to connect to the database and it may take up to 15 minutes until it gives up. l Stop DownloadServer.exe via the Task Manager or wait until it stops running. l Restart the ServerView Download Service using the new credentials. 3. In other error situations: l Restart the ServerView Download Service.
8 Troubleshooting Management Station with OS=RHEL6, using local DVD drive for initializing repository from DVD If you want to initialize your repository from DVD this may fail because you do not have the right permissions for reading the DVD. The mount point itself and the directories above must have read access for user svuser. When you have inserted the DVD into the local DVD drive the automounter will mount it automatically to /media/. l Check the permissions of this directory.
8.4 Error messages in the Repository Manager 8.4 Error messages in the Repository Manager The following error message can occur after activating an action in the Repository Manager: Repository task has not been started on Central Management Station. Please, check if ServerView Download Service is stopped and restart the service. For more details, check system event log messages with source 'ServerView Update Manager'.
8 Troubleshooting Solution Proceed as follows: 1. Check if the requirements are fulfilled on the system running the VMware ESXi operating system. 2. In the Release Note of SV Operation Manager > chapter 7.
8.7 Problems with entries in the tree structure 8.7 Problems with entries in the tree structure A managed server was displayed in the tree structure of the Update Manager / Download Manager. After a check run the managed server is no longer visible in the tree structure. Possible reason The management controller on the managed server is no longer working. This causes 1. The inventory has the value N/A for Chassis. This can be checked with applet Inventory Manager - Show Inventory. 2.
8 Troubleshooting 8.8 Problems with components Situation BXxxx with 2 management blades. One of these management blades is degraded. Solution Before you update the management blade firmware: 1. Repair the degraded management blade. or 1. Remove the degraded management blade from Chassis. 2. Recollect the inventory of BXxxx again.
8.9 Problems with Fibre Channel (FC) Controllers 8.9 Problems with Fibre Channel (FC) Controllers Situation Managed node with Linux operating system. Firmware-Update for Fibre Channel Controller is not offered due to missing Inventory. Solution Check whether the prerequisites on the managed server are fulfilled (see section "Prerequisites on managed servers" on page 12) . 8.
8 Troubleshooting CMS: l ServerView Update Manager Win/LX (applet of SV Operations Manager) >=V 5.0 (includes Remote Connector Service >1.06) Managed node: l ServerView Agent Win/LX >=V 5.0 (includes Remote Connector Service >1.06) l ServerView Update Agent Win/LX >=V 5.
8.11 Installation/Uninstallation of updateable components without using 8.11 Installation/Uninstallation of updateable components without using Update Manager Recommendation: Use ServerView Update Manager to update updateable components. If updateable components were updated without Update Manager, follow the instructions below to update data within the ServerView Operations Manager database (Update Manager, Inventory Manager, ...
8 Troubleshooting Firmware/BIOS 1. Update the inventory on the managed node. Windows: ServerView Agents for Windows: Restart Agents. Linux: ServerView Agents for Linux : sh /etc/init.d/SVforceVV.sh 2. Update the inventory on the management station (implicit check is executed): Inventory Manager: Recollect Asset Data from Agents. SV Update Agent Win <=V4.81.02, Linux <=V4.80-07/GlobalFlash Agent Win/Linux <=V4.71.01 1. Update the inventory on the managed node.
Index A ASP Autonomous Support Packages 22 22 B Batch File Examples (CLI) 254 C Call Parameters Cancel (Command) Cancel (Event) Change TFTP Address Cleanup (Command) Cleanup Wizard Enter TFTP Address Logon Schedule Job CLI Batch Files (Examples) Call Parameters Cancel Cleanup Reboot Result Files Standalone StartFlash WaitForDone Closing Configuration Download Manager Repository Manager Update Manager Collections Tab Column filter Command Cancel 234 245 252 130 244 84 87 84 88 254 234 245 244, 255 242 2
Index D Deleting a Job 215 Deleting a UserDefined Group 219 Display Job Information 215 Display Log File 211 Display Update Information 211 download current software versions 29 information files 29 Download Manager 222-223 Activate Download Server 180 Tasks Add Download Server Tasks 175 Assigning Servers to Task 225 Closing 224 Creating a New Download 224 Task Deleting a Download Task 226 Dialog Boxes 175 Edit Task Settings 178 Editing a Download Task 225 Log Files Tab 172 Main Window 165 Managing Log Fil
Index M Mail Settings Tab Main Window Configuration Download Manager Repository Manager Update Manager Management station Update Management Station Restart Shutdown Managing Jobs Copying a Job Creating a Job Deleting a Job Display Job Information Releasing a Job Managing Log Files Managing Updates Configuration Download Manager Repository Manager Update Manager Managing User Defined Groups Create Delete Edit Release Updates MemoryError (Event) 185 182 165 132 57 21 21 21 211 213 211 215 215 215 227 207 22
Index Ready SequenceError StartFlash 251 252 248 S Scheduled Tasks Tab SequenceError (Event) Server Details Tab Setting Global Parameters StartFlash (Command) StartFlash (Event) Status Update 170 252 65 228 237 248 60, 133 T Table filter Tabs Collections Tab General Settings Tab Job Details Tab Log Files Tab Mail Settings Tab Proxy Settings Tab Scheduled Tasks Tab Server Details Tab Task Management Tab Update Details Tab Updates tab Task Management Tab TFTP TFTP Address Tree structure Download Manager R
Index Releasing Updates 219 W WaitForDone (Command) ServerView Update Management 240 295
ServerView Update Management
