ServerView Suite
ServerView Operations Manager V5.0
Installation ServerView Agents for Windows:
know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs.
Feel free to send us your comments by e-mail to [email protected].
Certified documentation
according to DIN EN ISO 9001:2008
To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard DIN EN ISO 9001:2008.cognitas. Gesellschaft für Technik-Dokumentation mbH www.cognitas.de
Copyright and Trademarks
Copyright © 2010 Fujitsu Technology Solutions GmbH. All rights reserved.
Delivery subject to availability; right of technical modifications reserved.
1 Introduction . . . 5
1.1 Architecture . . . 6
1.2 Target groups and objectives . . . 7
1.3 Technical requirements . . . 7
1.3.1 Management console . . . 7
1.3.2 Central management station (CMS) . . . 8
1.3.3 ServerView agents . . . 9
1.4 Changes since the previous version . . . 10
1.5 Documentation for ServerView Suite . . . 10
1.6 Notational conventions . . . 11
2 Installations on managed servers . . . 13
2.1 Configuring servers . . . 14
2.1.1 Configuring servers via the Server Configuration Manager . . . 16
2.1.2 Configuring servers via the Windows Start menu . . . 18
2.1.3 Configuring servers via the ServerView Configuration Manager 20
2.1.4 Overview of the functions . . . 23
2.2 ServerView security concept . . . 24
2.2.1 Prohibiting specific SET operations . . . 24
2.2.2 Prohibiting All SET operations . . . 25
2.2.3 SET Operations with user authentication . . . 25
2.2.4 Operating system-specific characteristics of the SNMP agents . 29 2.3 Configuring SNMP services . . . 30
2.3.1 Windows Server 2003/Windows Server 2008 . . . 32
2.3.2 For Environment in which Server Core is Installed . . . 34
3 Installation ServerView agents . . . 37
3.1 Windows 2003/2008 . . . 37
3.1.1 Installing and configuring agents . . . 37
3.3 Installing via the command line . . . . 57
3.4 Setting after installation . . . . 62
3.4.1 Setting an administrator user . . . . 62
3.4.1.1 For Environment in which Server Core is installed . . . . 63
3.5 Installing ServerView Update Agent . . . . 65
3.5.1 Requirements . . . . 65
3.5.2 Menu-driven installation . . . . 65
3.5.3 Installing via command line interface . . . . 67
3.6 Uninstallation . . . . 68
3.6.1 Windows Server 2008 . . . . 68
3.6.2 For Windows Server 2003 . . . . 69
Within the ServerView Suite, you can use the server management software ServerView Operations Manager (called simply Operations Manager below), for central administration of industry standard servers.
Operations Manager makes the data of the managed PRIMERGY server accessible via Intranet and Internet. You can view all data of the managed servers from a standard PC with Intranet or Internet access and a standard web browser.
Operations Manager monitors important server functions such as hard drives, ventilation fans, the power supply or the temperature. If the values specified for these parameters are exceeded or an error occurs, then messages are output and corrective measures are initiated, if necessary.
The Operations Manager software is organized into two parts: The "ServerView Manager" is installed on a central management station, and "agents" are available on the servers to be managed to exchange information with the manager.
1.1
Architecture
Figure 1: Architecture overview
Management console
All data of the managed server can be viewed from any standard PC with intranet or Internet access and a web browser (web-based console). Central management station (CMS)
The ServerView Operations Manager is installed on a central management station.
Managed node
1.2
Target groups and objectives
This manual is intended for system administrators, network administrators and service technicians that have a basic knowledge of hardware and software. The manual describes the installation of the ServerView agents and the ServerView Update Agent for windows.
1.3
Technical requirements
I
Any last-minute changes/corrections of the technical requirements can be found in the Readme file on the ServerView Suite DVD 1. You have the following options:– On the DVD 1 switch to the directory SVSSoftware – Software – ServerView – Windows – ServerView_S2.
– Start the DVD 1 and select in the Welcome dialog ServerView Software Products – Start; Info under ServerView – Operations Manager.
1.3.1
Management console
– Standard PC, LAN with http access
– Microsoft Windows with Microsoft Explorer V7/V8 – RedHat Linux with Mozilla Firefox 3.5/3.6
1.3.2
Central management station (CMS)
Hardware
– PRIMERGY server
– Processors with at least two cores – Main memory: at least 4 GB RAM – 100 MBit-LAN
– At least 100 GB free disk space – Graphics 1280 x 1024
Software
● Windows
– Microsoft Windows® ServerTM 2003 all editions – Microsoft Windows® ServerTM 2003 R2 all editions – Microsoft Windows® ServerTM 2008 all editions – Microsoft Windows® ServerTM 2008 R2 all editions
● Linux
– Novell SLES 10 – Novell SLES 11
– Red Hat RHEL 5.4 and 5.5 – Red Hat RHEL 6
Database
● Windows
– Local under Windows:
Additional supported:
– SQL Server 2000 Standard, Workgroup, Enterprise, each with SP4 – SQL Server 2005 Standard, Workgroup, Enterprise
– SQL Server 2008 Standard, Workgroup, Enterprise – Remote under Windows
– SQL Server 2005 Standard, Workgroup, Enterprise – SQL Server 2008 Standard, Workgroup, Enterprise
● Linux (local and remote)
– PostgreSQL 8.4.3 (included in ServerView package) Java Runtime Environment
– JRE V1.6.0_21
1.3.3
ServerView agents
Installed ServerView agents, available for: – Windows Server 2003
– Windows Server 2003 x64 – Windows Server 2008 – Windows Server 2008 x64 – Windows Server 2008 R2 – SuSE Linux SLES 10 and 11 – Red Hat Enterprise Linux 4 and 5 – Citrix XenServer as of V5.0 – VMware ESX Server as of V3.5
1.4
Changes since the previous version
This edition is valid for ServerView Operations Manager v5.0 - Installation ServerView Agents for Windows and replaces the online manual “ServerView Operations Manager v4.92 - Installation ServerView Agents for Windows“, Edition February 2010.
The manual features the following changes and enhancements:
● You can select the installation language after starting the installation program, see section “Windows 2003/2008” on page 37.
● While installing the ServerView agents in expert mode, you can also install following tools:
– ServerView System Monitor
Used for system monitoring. The tool is described in the “ServerView System Monitor“ user guide.
– Virtualization Management Agent
Provides performance data for virtual machines (Xen, Hyper-V, VMWare).
You select the features in the Custom Setup window in the installation wizard.
● For installation via the command line interface, MSIEXEC is no longer supported.
The agents are installed by calling Setup.exe. The option /w is no longer supported.
1.5
Documentation for ServerView Suite
The documentation for the ServerView Suite can be found on the ServerView Suite DVD 2 supplied with each server system.
1.6
Notational conventions
The following notational conventions are used in this manual:
If there are references to text or sections of text in this manual, then the chapter or section heading is placed in the reference, and the page stated refers to the page on which the chapter or section begins.
Screen outputs
Please note that the screen output is dependent in part on the system used and therefore some details may not correspond exactly to the output you will see on your system. You may also see system-dependent differences in the menu items available.
V
Caution This symbol points out hazards that can lead to personal injury, loss of data or damage to equipment.I
This symbol highlights important information and tips.Ê This symbol refers to a step that you must carry out in order to continue with the procedure.
italics Commands, menu items, names of buttons, options, variables, file names and path names are written in italic
letters in text.
fixed font System output is written using a fixed font.
semi-bold fixed font
Commands to be entered through the keyboard are written in a semi-bold fixed font.
<abc> Angle brackets are used to enclose variables which are to be replaced by actual values.
[Key symbols] Keys are presented according to their representation on the keyboard. If capital letters are to be entered explicitly, then the Shift key is shown, e.g. [SHIFT] - [A] for A. If two keys need to be pressed at the same time, then this is shown by placing a hyphen between the two key symbols.
Before starting Operations Manager, the following preparations must be made on the managed server:
● On each server, you must make configuration settings. This is described in section “Configuring servers” on page 14.
● ServerView offers a sophisticated security concept. Before you install the agent, you should study the information regarding the security concept thoroughly and choose the concept that best suits your security
requirements. You may need to make appropriate arrangements prior to installing the agent. This is described in section “ServerView security concept” on page 24.
● You must install and configure the SNMP services of the current operating system on each managed server and the management station. If you do not do this, the management station will be unable to monitor the servers. The SNMP services must be activated either before or after installing the agent, depending on the operating system. This is described in section
“Configuring SNMP services” on page 30.
● Agents specific to the current operating system must be installed on each server to be managed. This is described in chapter “Installation ServerView agents” on page 37.
I
For the RXI servers there are special ServerView agents which come with the server on the separate IA 64 ServerSupport CD.● ServerView Update Manager requires ServerView Update Agent to be installed on the managed servers. How to do this is described in the section “Installing ServerView Update Agent” on page 65.
Additional installations
– ServerView Online Diagnostics
During installation of the ServerView agents for Windows (as of version 4.40.04), Online Diagnostics is also installed. You can use Online Diagnostics to perform a series of hardware tests on a managed PRIMERGY server from the remote workstation.
– ServerView RAID Manager
ServerView RAID Manager offers standardized administration and management of hard disks for PRIMERGY servers.
Unless the ServerView RAID Manager is installed, no information about RAID drives and their status will be available.
The installation is described in the ServerView RAID Manager manual. – When installing the ServerView agents (for Windows) in Expert mode, you
can choose whether to install additional components, including Asset CLI, Configuration Tools, Prime Collect and ServerView System Monitor. ServerView System Monitor allows you to monitor and check server information locally on the server. For a detailed description, refer to the „ServerView System Monitor“ user guide.
2.1
Configuring servers
There are various functions available for configuring servers. Some of these functions are supported for all PRIMERGY servers and others are only available for certain servers, depending on the hardware and software installed in the PRIMERGY server.
You can configure the servers in one of the following ways:
– Locally on the managed server via the Server Configuration Manager. – Locally on managed Windows-based servers using the Start menu.
I
You can only configure servers on which the ServerView agents for Windows are installed.I
You can only configure servers on which the ServerView agents are installed.Depending on the system, some of the configured settings are written to the BIOS.
Among other things, you can do the following:
– Read the most important data of the server, the system board and the integrated management controller
2.1.1
Configuring servers via the Server Configuration
Manager
With the Server Configuration Manager you can make settings for the general system behavior of the target system and configure any remote management components (iRMC or iRMC S2) of the target system.
I
For further details please see the Installation Manager guide. You start the Server Configuration Manager via the ServerView Installation Manager, which is turn is started from the ServerView Suite DVD 1.Ê In the Installation Manager welcome screen, click the Maintenance button or click Maintenance in the menu bar.
This opens the ServerView Installation Manager Maintenance window:
Ê Select the entry Server Configuration Manager. The following window is displayed:
2.1.2
Configuring servers via the Windows Start menu
On Windows-based servers, you can call the configuration via the Windows Start menu.
Proceed as follows:
Ê On the managed server, select:
Start – All Programs – Fujitsu – ServerView Suite – Agents – Configuration Tools – System Configuration.
The System Configuration window opens:
Figure 4: System Configuration window Ê Accept the preset values.
The System Configuration window opens:
Figure 5: System Configuration window
You can scroll to the left and right through the tabs by clicking the arrows next to the tabs.
2.1.3
Configuring servers via the ServerView
Configuration Manager
You can also configure servers via the ServerView Configuration Manager, which is integrated in the graphical user interface of Operations Manager. This allows you to configure the server from the remote workstation via a web interface.
Proceed as follows:
Ê Start the ServerView Configuration Manager on the Operations Manager start page or via the menu bar by selecting Administration – Server Configuration. How to start Operations Manager is described in the ServerView Operations Manager documentation.
This opens the following window:
The following window opens if the agents are configured such that SET operations are only allowed after user ID/password authentication.
Ê Enter the user ID and click OK.
Ê The following window opens:
Figure 7: Operations Manager: Server Configuration window - Server list (2) tab Ê In the right-hand side of the window, specify the details on the selected
The window shown below appears in which the Configuration tab is activated:
Figure 8: Operations Manager: Server Configuration window - Configuration tab Ê In the navigation area of the Configuration tab, click the required function.
The associated setting options are then offered in the right-hand side of the window.
Ê Configure the settings you require and save them with Save Page or with Save all.
I
Activate the configured settings for each server either separately for each function with Save Page or after you have completed the entire configuration with Save all.I
After you have completed configuring a server, you can select further servers for configuration in the Server list tab.2.1.4
Overview of the functions
The following table describes only the general functions.
Depending on the PRIMERGY server involved, different subsets of the functions listed below are available:
Boot Watchdog Boot Watchdog monitors the start of the operating system. If the operating system is not started within the specified time period, the Boot Watchdog will initiate the set behavior when the time period has expired.
Software Watchdog Software Watchdog monitors the operation of the operating system. If the operating system doesn’t respond within the set time period the Software Watchdog will initiate the set behavior when the time period has expired.
2.2
ServerView security concept
The ServerView agents together with the ServerView Manager provide a complete security concept to prevent unauthorized SNMP SET operations on a server.
You can restrict access to SNMP SET operations on the managed server. Here you have the following options:
– Prohibit specific SET operations. – Prohibit all SET operations.
– Protect SET operations with a user authentication.
If you select the user authentication option, the system will run a user authentication routine each time you start a SET operation. If the
authentication routine is successful, the system will also check if the user belongs to one of the user groups defined by the administrator.
I
The user authentication only operates with ServerView Manager. It does not work with other SNMP tools.You can also reduce the risk of unauthorized access by changing the default configuration of the SNMP service. For further information see section “Configuring SNMP services” on page 30.
2.2.1
Prohibiting specific SET operations
Some SET operations cause the system to shutdown or restart. You can permit these special SET operations or forbid them.
2.2.2
Prohibiting All SET operations
You can prohibit all SET operations for ServerView agents. Enter these specifications during agent installation.
I
This option only applies to ServerView agents. SET operations for other SNMP agents are not affected.The specific entries you need to make during the installation in order to prohibit these SET operations depend on the operating system under which the ServerView agent is installed and on the version of the ServerView agent. For a detailed description see page 37.
2.2.3
SET Operations with user authentication
You can restrict access to SET operations and protect the execution of SET operations with a user authentication. Here you can choose between starting the user authentication routine at the beginning of each session on a managed server or starting the user authentication at the start of each new SET operation.
For user authentication, you must make the following settings on the managed server as well as on the management station.
Entity Settings
managed Server – Define user and user group – Assign user to specific user group
– State the specified user group during installation of the agent
management station
Defining user and user group and assigning users
You must define user and user group on each managed server, using the methods specific to your operating system. You may choose any name for the user or the user group (including Administrator).
You need to decide in advance, whether or not you want to create identical user and group identifications for several servers.
Example
A new user is created with the operating system-specific method. In this example the user SVUSER is created.
Figure 9: Create a new user
Figure 10: Create a new user group
In this example the user group SVUSER is created. You must assign the user, permitted to execute SET operations on the managed server, to this group. In this case you must assign the user SVUSER to the user group SVUSER. Specifying a user group during the installation of the agent
During the installation of the agent on the server you need to specify the user group to which the user, permitted to execute SET operations, must belong. In the example above this would be the user group also named SVUSER.
Specifying users on the management station
On the management station you must specify in Operations Manager the user permitted to execute SET operations on the current server. Executing a SET operation through the management station, the user is prompted to provide identification.
You define the user in the Login tab in the Server Properties window. In this example this would be SVUSER.
Figure 11: User authentication
If you have assigned a password to a user, for reasons of security, we
recommend that you enter the password here as well (Set Password). The option
Always Ask for Password allows you to specify whether user name and password are required after each change made to the settings, or only after the first alteration made after starting Operations Manager. You a achieve a higher degree of security, if you activate Always Ask for Password because in this case the password is not saved.
On the right-hand column of the property window you can select those servers to which the settings are to apply. You can also select several servers at once. This allows you to specify settings for each server individually or to apply an identical setting to several servers collectively.
2.2.4
Operating system-specific characteristics of the
SNMP agents
The following sections describe the procedures, specific to the operating system and agent versions, involved in realizing the security concept of ServerView.
ServerView security concept (ServerView agents as of version 3.0 for Windows Server 2003)
Configure the security settings under Windows (ServerView agents as of version 3.0) during installation of the agent:
– You can allow or forbid SNMP SET operations for the ServerView agents. If you forbid SET operations, all SNMP SETs are refused, regardless of the SET tool used to execute them. (Shown on the management station in Operations Manager on the tabs Restart Settings and Power ON/OFF in the settings under Set Enabled on server).
I
This option only applies for ServerView agents. SET operations for other SNMP agents are not affected.– You can turn the user authentication for SET operations on or off. You can enter the user group to which the user must belong to be allowed to carry out SET operations on the server.
Windows 2003 Server: if you do not enter a name in this field, only local system administrators will be allowed access to SET operations on the server.
– Some SET operations (e.g. Restart/Shutdown/Abort Shutdown in the Recovery
window) cause the system to shutdown or restart. You can allow or forbid these special SET operations.
2.3
Configuring SNMP services
You must install and configure the SNMP services on every server to be managed and every management station.
When you install and configure the SNMP services default values are provided. You can modify these values for the SNMP service. If you change the values you must also remember to change them on the management station.
Configure the following values:
– Community string for accepting SNMP requests
The Community name (Community string) is part of every SNMP request sent from the manager to the agent.
After installing the SNMP services, no community name is available. You can use the community name public. This default entry is used by most SNMP services. For reasons of security, we recommend that you change this entry. In principle you can define an individual community for each server or server group. Remember to make corresponding changes on the management station.
I
– Community names are case sensitive.– You can configure the community names. How to do this is described in the White Paper “Secure PRIMERGY Server Management“.
– Rights for the community
Rights can be assigned to the community (e.g. read-only, read-write). If you want to use the entire range of Operations Manager functions, you must assign read-write rights to the community. You can restrict access to certain functions by assigning (read-only) access rights to them.
The ServerView Manager only supports one community per server for SNMP requests. For this reason you cannot configure different communities with different access rights for a server.
– Accept SNMP packets from selected server/any server
– Trap Destination
IP address of the management station to which the ServerView agents send traps.
– Community string for sending traps
Here, enter the community name that is to be sent to the management station as part of a SNMP trap. The SNMP service on the management station must be configured so that it accepts traps with this community name.
2.3.1
Windows Server 2003/Windows Server 2008
I
Install service packs for Windows only after you have installed and enabled the SNMP services.When you have completed installing Windows Server 2003 or Windows Server 2008 on the server, you must perform the following steps before you install the ServerView agents, unless you have already completed them during the system installation:
Ê For installation, call up Start – Properties – Control Panel – Add/Remove Programs – Add/Remove Windows Components.
Ê In the Windows Components window, select the entry Management and Monitoring Tools.
Ê Then click Details.
Ê Select the entry Simple Network Management Protocol and then click OK.
Ê Click Next.
Ê For configuration, call Start – Properties – Control Panel – Administrative Tools – Component Service.
Ê Select the service SNMP Service and then select Properties from the context menu.
Ê On the Traps tab, enter a name under Community name or confirm the default entry public.
I
The default entry public does not exist under Windows Server 2003. You must therefore enter a name for the community.Community Name is used to control the management station access rights. Only a management station belonging to the community entered here can query the server. If you do not select public, then you must also change the community entered in the management station for the relevant server.
Ê Under Trap destination, enter the IP address of the management station for the specified community, using Add.
Traps are only sent to the management station entered here.
Ê Accept SNMP packets from selected server / any server (hosts). You can select the managed server from which SNMP packets are to be accepted, or you can select them all here.
Under Windows Server 2003, SNMP is installed with the highest level of access protection. You must therefore specify the management station, or select the option Accept SNMP packets from any hosts.
I
Since SNMP is an open protocol without password protection, you should only enter those management stations that function as such. Otherwise, unauthorized network users could alter important system parameters and thus disrupt server operation.Ê Click OK.
2.3.2
For Environment in which Server Core is Installed
In the local console environment of Server Core, the GUI based management tool of Microsoft management console (MMC) is not available. You need to start the management tool from another terminal with Windows Server 2008, Windows Server 2003, or Windows XP and connect it remotely. The procedure is shown below.
To configure the setting of SNMP Service, another Windows terminal (installed other than Server Core of Windows Server 2008) is required. Prepare it in advance.
1. On the terminal with Server Core, execute the following command. Check to see whether SNMP Service is installed and begin.
> sc query SNMP
When SNMP service is not installed execute the following command to install the SNMP service.
> start /w ocsetup SNMP-SC
2. Log in as an administrator or a user with administrator privileges. 3. Execute the following commands at the command prompt.
For Windows Server 2008, the firewall is enabled by default. It is necessary to permit the access to manage it remotely.
> netsh firewall set service remoteadmin enable
> netsh advfirewall set currentprofile settings remotemanagement enable
On another Windows terminal, follow the steps below to connect Server Core.
4. On another Windows terminal, start a command prompt and execute the following command. During the operation, you are prompt to enter Administrator password. Enter IP address of monitoring server (Server Core) in "xxx.xxx.xxx.xxx" of the following command.
net use \\xxx.xxx.xxx.xxx\c$ /u:Administrator
5. Execute the following commands.
7. Enter IP address or the machine name of the above-mentioned Server Core server to Another computer, and click OK.
Service list of Server Core server is displayed. Make sure that SNMP Service exists in the service.
I
If RBAC funtionality will be used on the managed server:Before the ServerView agents are installed, you have to import the SSL certificates of the trusted central management stations (CMS). For details refer to „User management in ServerView“ manual.
3.1
Windows 2003/2008
Before you install the ServerView agents for Windows, it is essential that you install and activate the SNMP services in the operating system. If you do not do this, the management station cannot monitor the servers (for more information, see section in section “Configuring SNMP services” on page 30). Before you start installation, you should carefully plan your security concept of ServerView. For further information, see section “ServerView security concept” on page 24.
3.1.1
Installing and configuring agents
I
Unattended installation of the ServerView agents as of V4.0 for Windows is described in the section “Installing via the command line” on page 57. Install the ServerView agents as of version 5.0 for Windows from theServerView Suite DVD 1:
Ê Place the ServerView Suite DVD 1 in the DVD-ROM drive. If the DVD does not start automatically, click the start.html file in the DVD’s root directory.
Ê Select the option ServerView Software Products.
Ê Click Start.
Ê Select the desired language in the displayed window.
Ê To install the agent for Windows, select ServerView – Agents and start the
Inst_ServerViewAgents_Win_i386.exe program.
When it starts, a window opens for you to select the language for the installation:
Ê Select the language and click OK.
Select the most suitable installation for your requirements.
Ê Follow the instructions on the screen.
Starting the Setup Wizard
When you have confirmed that you agree to the license conditions, the system setup will check if an older version of ServerView agents is already installed on the server. In this case you can perform an upgrade installation. During this, the present configuration is saved, then the old version is deleted and the new one is installed based on the previous configuration. In this case you cannot make any changes.
If no agents are present on the system, the window shown below will be opened:
The setup level window offers the four default levels for agent installation: – Standard (High security)
– Standard (Administrator account based security) – Standard (Without any security)
– Expert (Advanced users)
If you choose one of the first three default installation modes, no further entries are required. In these modes, the SNMP agents required for Operations Manager and the main tools (i.e. Configuration, Maintenance, Diagnostic) will be installed; for further information on tools, see the description at the end of the Expert mode below. In these three modes the setup uses the default values for the security level selected.
If you choose the Expert mode you must enter the installation and configuration values individually. In the Expert mode, the wizard will guide you through the installation and configuration values necessary.
Standard (High security)
The standard installation mode has the highest security level and does not permit any SNMP SET operations. SET operations are also prevented if the SNMP community used has write permissions.
You can change the configuration of the standard installation, for example by assigning read/write rights to the community, or by creating new user groups and users and reconfigure the agent accordingly.
Standard (Administrator account based security) (only useful for Windows 2003 Server)
In this standard installation mode, SNMP SET operations are permitted. Management station SET operations are password protected and have local administrator and user authentication. Local passwords and administrator access rights. However, there is no password protected security for SET operations which have been run using other SNMP tools. The SNMP
You can change the configuration of the standard installation, for example by setting up new user groups and users with operating system-specific resources or reconfigure the agent with the configuration tool Agents Configuration. Standard (Without any security)
In this standard installation mode, SNMP set operations are permitted without any password protected security further user authentication. This installation mode should only be used on secure internal networks. The SNMP community which is used requires write permissions to execute SET operations. Otherwise the SET operation will be prevented by the security mechanisms of the operating system.
Expert (Advanced user)
The expert mode provides the following options: – select other components
– Configure agent packages individually. Here you can individually configure SNMP trap forwarding, SNMP security settings and system shutdown behavior.
– Pre-configure the remote management controller. During installation can define the main settings of the remote manager controller and then transfer these to the system during setup.
If you select the Expert mode the window shown below will open:
Figure 13: Expert Settings
The Expert Settings window has the following options: – Configure ServerView agents.
– Configure server firmware.
– Restrict SNMP access to local system. This option defines the value Restrict access to these host only in the SNMP settings and enters the LOOPBACK adapter. If you select this option you will not be able to access the system from outside. This option only makes sense if the Event Manager is installed on the server and if the server is not being used as a management station. – Define the path for the configuration file Setup.pre to be used for an
The window has the following buttons:
Agents ...
Opens a window where you can change the ServerView agent configuration. For more information, see the next section below.
System ...
Opens a window where you can create a server firmware configuration (e.g. Boot Watchdog, Software Watchdog, UPS Configuration). For more information, see the section “Configuring server firmware”.
Save file ...
Opens a window where you can enter the path for saving the
configuration file Setup.pre. This file will be used for automatic installations (“unattended setup”) (see also section “Installing via the command line” on page 57).
I
The configuration file must be in the same directory as theSetup.exe.
Back
Returns you to the previous window.
Next
Displays the next window.
Cancel
Cancels the installation. Configuring ServerView agents
To start configuration of the ServerView agents, click the Agents ... button. This will open the ServerView SNMP agents settings (offline) window.
This window has three tabs. – Trap Forwarding
“Trap Forwarding” tab
All SNMP traps generated by ServerView agents can be reported to the system’s event log or forwarded as an administrator alert message. Forwarding depends on the weight assigned to the trap. The following weights are available: – critical (for critical traps)
– major (for important traps) – minor (for less important traps) – informational (for informative traps) Weighting for the event log types is as follows:
The reporting service on the server must be configured and running before a trap can be forwarded to the administrator. The message targets must already be defined in the properties of Windows Server Manager.
Trap weighting Event log type critical and major traps Error
Figure 14: “Trap Forwarding” tab
Use the Trap Forwarding tab to select which types of SNMP traps will be forwarded. In the default setting, critical and major traps will be reported to the system event log.
“System Shutdown” tab
ServerView agents can initiate a system shutdown. The shutdown can be triggered by an operation on the management station or by the occurrence of a system error.
By default, ServerView agents always initiate a “soft” shutdown, i.e. the user is asked to close any running applications and then to explicitly confirm the shutdown. After a preset time delay has elapsed, the ServerView agents will initiate a hard shutdown and shutdown the operating system even though the shutdown has not been explicitly confirmed and not all the data has been saved to the hard disk. The default value for this delay is 120 seconds. If you have to save large amounts of data to the hard drive you should increase this value accordingly.
Figure 15: “System Shutdown” tab
On the System Shutdown tab can define the following shutdown settings: – The delay that must elapse before the shutdown is started.
– The time that must elapse before a soft shutdown switches to a hard shutdown.
– Which application is still to run before a system shutdown.
Start Delay (sec)
This setting defines the delay (in seconds) which must elapse before the shutdown is started. During this delay the shutdown can be interrupted from the system console.
Timeout (sec)
This setting defines the time interval (in seconds) during which the soft shutdown (with data saving) must be completed. When this time period elapses, the system will start a hard shutdown without saving any data.
Executable Path
Path name of an executable program or script.
The path may also contain environment variables, e.g. %SystemRoot%.
Working Directory
Maximum Execution Time (sec)
Indicates the maximum duration of the job. The shutdown will be started once the maximum time set in this field has elapsed.
Security Settings” tab
The ServerView agents used in combination with management station provide a complete security concept restricting access to SNMP SET operations on the server. You can prevent access to SET operations or, using user authentication protection, enable access to these operations when performed together with management station.
If you select the user authentication option, the system will run a user
authentication routine each time you start a SET operation. If the authentication routine is successful, the system will also check if the user belongs to one of the user groups defined by the administrator.
Enable Password Protection
This checkbox enables/disables the user authentication routine protecting access to SNMP SET operations.
User Group
Indicates the user group to which the user must belong in order to perform SET operations on the server. Here, you can create a user group of your choice.
If the user group does not exist already, you need to create this group using methods specific to your operating system.
Do not assign a user to a user group at this point. Wait until later. You assign a user to a user group at the operating system level, either before or after installing the agent. For security reasons, we recommend that you enter one user only.
I
If you do not enter a name in Usergroup, only local system administrators will be allowed access to SET operations on the server.Enable ServerView SET operations on server
Enables SNMP SET operations by ServerView agents. If you forbid SET operations, this will prevent access to all SNMP SETs irrespective of the tool used to run the SET.
I
This option is for ServerView agents only. This option has no effect on other SNMP agents.Enable remote shutdown via SNMP request
Configuring the server firmware
To start configuration of the server firmware, select Expert Settings and click the
System ... button. The System Configuration (offline) window will be displayed.
Figure 17: “System Configuration” window
Click Go ... to confirm. The following window will be displayed:
Figure 18: “System Configuration” window - tabs
The tabs displayed in this window depend on the current system. Use these tabs to configure the firmware of the current system. The System Configuration is the one given by the Server Configuration Manager described in the section “Overview of the functions” on page 23. This section gives the tabs and the tab functions for the system configuration.
Click OK to confirm the changes and to return to the Expert Settings window. Click
Defining the setup type
Confirm the agent and firmware configurations in the Expert Settings window by clicking OK. Next, go to the Setup Type window to select the setup type.
Figure 19: Selecting the Setup Type
Select the setup type you require.
Complete
Select this option to start an installation where all the features are installed. This type requires the most memory space.
Custom
If you select Custom and then Next, the following window will open:
Figure 20: “Custom Setup” window
This window offers the following features for selection:
– SNMP Agents (Standard Agents, S.M.A.R.T. Support, Microsoft SMS Integration, MIB Files)
– Configuration Tools – Support Tools – Diagnostic Tools
– Windows Management Integration – Virtualization Management Agent – HP Systems Integration
– Help Files
– Remote Connector Service
– Server Control Service (always selected; standard part of the installation package)
– Single System Monitor
The table below gives a brief description of the features which can be selected.
Feature Description
Standard Agents SNMP agents required for Operations Manager. S.M.A.R.T. Support S.M.A.R.T. support for event monitoring. Microsoft SMS Integration Software for automatically creating MIF files for
Microsoft SMS V 1.2 and V 2.0. MIB Files ServerView MIB files.
Configuration Tools Tools agent and system configuration. Support Tools Tools for service technician
Diagnostic Tools Various diagnostic tools (e.g. for installation testing), for support purposes only.
Windows Management Integration
Integration into Microsoft Windows Management (WMI).
Virtualization Management Agent
Provides performance data for virtual machines (Xen, Hyper-V, VMWare). HP Systems Integration Integration into HP SIM (System Insight
Manager)
Asset CLI Custom line utility for reading system asset information
PrimeCollect Tool for collecting and storing information about the hardware and software of PRIMERGY servers.
Help Files Help files
Installed tools
After successful installation, you will find among other things the following entries under Start – Programs – Fujitsu ServerView Suite – Agents:
– Configuration Tools - Configuration Tools menu – Diagnostic Tools - Diagnostic Tools menu – Support Tools - Support Tools menu item
I
After installation it takes some time to complete the configuration. As a result you might find that when you query the configuration, the system will continue to display the old values.The tables below give an overview of the tools available under these entries. Diagnostic Tools menu
Configuration Tools menu Restart ServerView Base Services
Restarts the ServerView agents. Run ServerView
Diagnostics
Tests the installation of the ServerView features. System Identification Displays general system information.
Agents Configuration Enables configuration of the ServerView agents at a later date.
Support Tools menu item (tools for service technician) CPU State Shows the CPU overview.
Once you have selected the components, the following window is displayed:
Figure 21: “Report Folder“ window
If you use the Performance Manager, report data is stored by default in the installation directory. However, this data can easily amount to 50 Mbytes or more, depending on the application. You therefore have the option of selecting a different directory with sufficient space via the Change button.
Click Next to start the installation.
3.1.2
Configuring RAID
3.2
Windows 2003/2008 x64 agents
The ServerView agents for Windows 2003 x64 are installed via the ServerView Suite DVD 1 (as of version 5.304) as follows:
Ê Place the ServerView Suite DVD 1 in the DVD-ROM drive. If the DVD does not start automatically, click the start.html file in the DVD’s root directory.
Ê Mark the option Select ServerView Software Products.
Ê Click Start.
Ê Select the desired language in the displayed window.
Ê To install the agents for Windows, select ServerView – Agents and start the program ServerViewAgents_Win_x64.exe.
Select the most suitable installation for your requirements.
Ê Install the agents using the operating-system-specific commands.
3.3
Installing via the command line
You can install the agents via a command in the command line. Operations Manager also allows the unattended installation of agents. With the help of the unattended installation, Software sharing systems such as Microsoft System Management Server (SMS) can share software automatically. The simplest form of software sharing is the unattended execution of setups with standard configuration. You are also able to fit the installation to your needs with the help of environment variables.
Setup.exe
The ServerView agent setup is based on Microsoft Windows Installer technology. The setup data is found in the installer database, ServerView Agents.msi. The setup data are packed in Data1.cab.
The Setup.exe program contains the installation package for Microsoft Installer V2.0 and the InstallShield Script support. On running Setup.exe, these
components are updated on the system, and then the installation of the ServerView agent is executed.
Command syntax of Setup.exe
Switch to the command-line level and enter the setup command on the highest level of the installation directory as follows:
Setup.exe [/x]|[[/a][/s][/V]]
The options have the following meaning: /x
(Uninstalled mode)
The setup uninstalls the product. /a
(Administrative mode)
The setup is run in Administrator Mode. In this mode all data files are extracted and placed in a directory. No registry entries or connections are made.
/s
(Silent mode)
/V
(Microsoft Installer Option)
Allows the transfer of arguments directly to the Microsoft Installer (MSIEXEC.EXE).
Microsoft installer properties
You can influence the installation by setting properties. The name of the property is always written in capital letters. Values are case sensitive. INSTALLDIR
Resets the standard installation directory. Possible values: Valid path names: e.g.:
INSTALLDIR=C:\Programs\Fujitsu\ServerView Suite\ServerView agents
Standard: System Folder REBOOT
Influences actions when the system reboots after the installation. For example, this option prevents a system from rebooting after an automatic installation if components can only be changed after the restart. Possible values:
F
The system always reboots. R
The system never reboots. SETUP_LEVEL
Sets the Setup mode for installation. Possible values: LevelHigh
(Standard)
Installs in setup mode: Standard (High Security).
The installation with the highest level of security, allows no SNMP SET operations.
LevelAdmin
Installs in setup mode: Standard (Administrator account based security).
LevelAll
Installs in setup mode: Standard (Without any Security). ServerView SNMP SET operations are allowing without any checks. This installation mode is a sensible choice for secured internal networks.
LevelUser
Installs in setup mode: Expert (Advanced Users). ADDLOCAL
States which features are to be installed. If you do not choose any features, a standard selection is installed. If you wish to make an individual choice, you must state the variables with ADDLOCAL. The feature names are listed separated by commas.
Possible values: All
Installs all modules. ServerControl
(standard, must always be installed) Installs the ServerView Base Service. SnmpAgents
(Standard)
Installs the ServerView agents. MIBFiles
Installs the ServerView agent MIB data. SmartSupport
(Standard)
Installs ServerView S.M.A.R.T. support. Configuration
(Standard)
Installs the ServerView Configurations Tools. Diagnostic
(Standard)
Installs the ServerView Diagnostic Tools. Maintenance
(Standard)
SMS
Installs the ServerView Integration in SMS. WMI
(not possible with Windows NT4)
Installs the ServerView Integration in WMI. WCS
Installs the ServerView Remote Connector. AssetCLI
Installs the ServerView Asset CLI tool. OnlineDiagnostic
Installs the Online Diagnostic tool. PrimeCollect
Installs the PrimeCollect tool. Help
ServerView help files.
Example
Addlocal=ServerControl,MIBFiles,WMI
The program features ServerView Base Service, ServerView Agent MIB data and ServerView Integration in WMI are installed.
Installation with a configuration file
To set up a configuration file, start the Setup Wizard in Expert Mode. On theExpert Settings tab, the settings for the agents and the system
management controller can be configured. In the Save File box enter the path name where the configuration file Setup.pre will be saved. The configuration file must be saved in the same directory as the Microsoft Installer data file (ServerView Agents.msi).
The configuration data is taken from the file onto the system by a Setup.exe
Examples of Setup.exe
Setup.exe /s/V“/qn“
Automatic installation of the standard configuration. The setup mode is
Standard (High Security), i.e. no SNMP SET operations are allowed, critical traps are entered in the system log.
The installation path is the folder of the system (e.g. C:\Programs\). The following features are installed:
– ServerView Base Service – ServerView Agent
– ServerView Configuration Tools – ServerView Diagnosis Tools – ServerView Maintenance Tools – ServerView Remote Connector – ServerView PrimeCollect
Setup.exe /s/V“/qn SETUP_LEVEL=LevelAll INSTALLDIR=“C:\My Programs“
Appropriate automatic installation in setup mode: Standard (Without any security) and changed installation path.
Setup.exe /s/V“/qn ADDLOCAL=ServerControl,WMI INSTALLDIR= “C:\My Programs“
Automatic installation of the basic features for integration in the Windows Management Instrumentation (WMI) with altered installation path.
Setup.exe /s/V“/qn ADDLOCAL=ServerControl,WMI Reboot=R“
3.4
Setting after installation
After the installation of ServerView agent for Windows, perform the following settings to ensure that agent operates properly.
3.4.1
Setting an administrator user
Only users belonging to the group (FUJITSU SVUSER) that have administrator privileges for ServerView can perform operations such as configuring Automatic Server Reconfiguration & Restart (ASR) settings (e.g. fans, temperature, restart settings) for the monitored server and shutting down the server from ServerView Operations Manager. At this time, the administrative user's name and password are required to be input. Follow the steps below to set an administrative user. The FUJITSU SVUSER group and users belonging to the group are not created automatically. Create a group each monitored server and add the ServerView administrative user to the FUJITSU SVUSER group.
An administrative user in ServerView means a user who belongs to the FUJITSU SVUSER group. In Windows Server 2008/Windows Server 2003, administrative privileges are not given if the password is not set for the administrative user account. Be sure to set the password.
Even when a "global" group is added to the FUJITSU SVUSER group,
administrative privileges are not given to the users in the added group. Add only users to the FUJITSU SVUSER group. If an administrative user is set for another group than FUJITSU SVUSER, the logon immediately after starting the program may fail. In this case, click Cancel to exit the logon window. Then, set the logon settings again on the Login tab of Properties on the server.
The ServerView administrative user must belong to the Administrators group. If the administrative user does not belong to the Administrators group, the user cannot perform shutdown or ASR settings from ServerView Operations Manager.
Therefore, add the ServerView administrative user to the Administrators group. 1. Open Control Panel and double-click the Administrative Tools icon.
2. Double-click the Computer Management icon. The Computer Management
5. Enter FUJITSU SVUSER in Group name and click Create. A new group is created. Click Close to close the New Group window.
6. Select Local Users and Groups – Users from the left tree view. 7. Click the Action menu and select New User....
8. Set the necessary items and click Create. A new user is created. Click Close
to close the New User window.
9. Select the added user and click the Action menu and select Properties. 10. Click the Member of tab and click Add. The Select Groups window appears. 11. Click Properties.
12. Click Search Now.
13. Select the Administrators and FUJITSU SVUSER groups, and click OK. Hold down the Ctrl-key for multiple selections. The Select Groups window appears again.
14. Click OK. The display returns to the user Properties window. Confirm that
Administrators and FUJITSU SVUSER are added to Member of, and click OK. 15. Click OK. Close the Computer Management window.
3.4.1.1 For Environment in which Server Core is installed
In the local console environment of Server Core, the GUI based management tool of Microsoft management console (MMC) is not available. Execute the following command to set the group and administrative user.
1. Execute the following commands to create the FUJITSU SVUSERgroup.
>net localgroup "FUJITSU SVUSER" /add
2. Create an administrative user and set a password.
>net user <user name> /add *
After executing the command, you are prompted to enter a password. 3. Add the newly created user to the FUJITSU SVUSER and Administrators
group.
To refer to or delete the created group and administrative user, execute the following commands.
To refer to the group:
>net localgroup "FUJITSU SVUSER"
To refer to the administrative user:
>net user <user name> /
To delete the group:
>net localgroup "FUJITSU SVUSER" /delete
To delete the administrative user:
3.5
Installing ServerView Update Agent
3.5.1
Requirements
– Before you install the update agent on the managed server, you must first install the corresponding ServerView agents. How to install the ServerView agents for Windows is described in this chapter. How to install the
ServerView agents for Linux is described in the ServerView Agents Installation Guide for Linux.
– For an update via TFTP server, the update agent V4.80 must also be installed on the server acting as the TFTP server, or a GlobalFlash Agent V4.71 in PXE mode.
3.5.2
Menu-driven installation
Update Agent version 4.80 and higher is only installed if the server is online-update-capable, i.e. online tools for updating the firmware are available. On older systems you will need GlobalFlash Agent 4.71. For a description, see the relevant documentation on ServerView Update Manager up to V4.71.
You start the installation via the FTASetup.exe file, which you will find on the ServerView Suite DVD 1 under Firmware – Agent-Win – SV-Update Agent. Start the menu-driven installation as follows:
Ê When you have confirmed the license conditions you must define the parameters for the security settings:
Figure 22: Security settings
Security Settings Account Check
Defines whether an access authorization is to be checked when the server is accessed. If this option is activated, you must also specify a Flash User Group.
Flash User Group
Name of a local user group. All users in this group are authorized to perform the update process. The group entered here must be available under Windows. The user group
GFUSER is preset. If you want to use this group you must set it up under Windows.
3.5.3
Installing via command line interface
You can install the update agent at the command level with the FTAsetup
command:
FTAsetup -noaccountcheck {0|1}
[-flashusergroup <User_group>]
FTAsetup -GFAU
The options have the following meanings: -noaccountcheck {0 |1}
Switches the password prompt on (0) or off (1). -flashusergroup <User_group>
If the password prompt is activated, you can use this option to specify the name of a local user group. All users in this group are authorized to perform the update process. If this option is not specified, GFUSER is taken as the default.
-GFAU
3.6
Uninstallation
This section explains how to uninstall the ServerView Windows agent.
The items saved on the server's BIOS are not restored even when ServerView Windows agent is uninstalled. Restore the settings to the original state, and then uninstall ServerView Windows agent.
Make sure to do the following before uninstalling ServerView Windows agent. – Disable Software Watchdog, BOOT Watchdog and Power ON/OFF settings. – If threshold monitoring and report creation are applied by Performance
Manager, cancel these performances to the server.
– When uninstalling ServerView Windows agent, the settings that are configured using ServerView Operations Manager such as the power schedule and ASR settings are deleted. The function to take over the settings automatically is not provided, so keep a copy of settings before uninstalling it. Configure the settings again after the update installation. To uninstall ServerView Windows agent, perform the following steps.
I
You do not need to restart Windows after uninstalling ServerView Windows agent.3.6.1
Windows Server 2008
1. Log in as an administrator or a user with administrator privileges. 2. Exit all running applications.
3. Open Control Panel and click Programs – Programs and Features. 4. Select ServerView Agents and click Uninstall.
ServerView Windows Agent will be uninstalled. For Environment in which Server Core is Installed 1. Insert the PRIMERGY Startup Disc.
3.6.2
For Windows Server 2003
1. Log in as an administrator or a user with administrator privileges. 2. Exit all running applications.
3. Open Control Panel and double-click Add/Remove Programs. 4. Select ServerView Agents and click Delete.
A
ADDLOCAL 59 Administrative mode
Setup.exe 57 agent
installing agent under Windows 2003 37
B
Boot Watchdog configure 23
C
configure Boot Watchdog 23 configure Software Watchdog
menu 23
configure the server firmware 48
D
Data1.cab 57
documentation for ServerView Suite 10 documentation structure 7 E environment variables Setup.Exe 58 example Setup.Exe 61 I installation on Managed Servers 13 installation using command line 57 INSTALLDIR 58
installer database 57
M Manager
enabling Windows Server 2003 services 32
variable transfer 58 Microsoft Installer option
Setup.Exe 58
Microsoft Windows Installer 57
N
notational conventions 11
P
program module selection setup 59 R REBOOT 58 S security concept Windows 29 server enabling Windows 2003 services 32
security concepts of Windows 29 server firmware
configure 48
ServerView architecture 6
ServerView database (Windows) 37 ServerView System Monitor 14 service enabling Windows 2003 services 32 setup program module 59 Setup.Exe 57 command syntax 57 environment variables 58 example 61
Microsoft Installer option 58 Silent mode 57
Uninstalled mode 57 Setup.exe
SETUP_LEVEL 58 Silent mode Setup.Exe 57 SNMP Security Settings 46 Software Watchdog configure 23 System Shutdown 44, 45 T tab SNMP Security Settings 46 System Shutdown 44, 45 Trap Forwarding 43, 44 target groups 7 Trap Forwarding 43, 44 U Uninstalled mode Setup.Exe 57 V variable ADDLOCAL 59 INSTALLDIR 58 REBOOT 58 SETUP_LEVEL 58 W Windows security concept 29 Windows 2003 enabling services 32 installing agent 37
