FUJITSU Windows Server Integration Pack V8.0 ServerView User Manual
Below you will find brief information for ServerView Windows Server Integration Pack V8.0. This manual describes Fujitsu ServerView Windows Server Integration Pack V8.0, which enables Fujitsu PRIMERGY Windows Servers to be integrated into System Center 2012 Operations Manager (SCOM 2012). Using the monitors of hardware and software components, this integration pack provides PRIMERGY Windows Servers from Fujitsu Technology Solutions the ability to be monitored via SCOM. Monitoring of a Fujitsu PRIMERGY Windows Server is implemented using the monitors of hardware and software components and is displayed by means of icons. If errors occur during hardware monitoring of a PRIMERGY Windows Server, the ServerView Agent enters these as event entries in the Windows Event Log of the managed server. The SCOM Agent which is located on the monitored systems sends these events to the SCOM Management Station, where they are evaluated and displayed on the SCOM Console by the Management Pack in accordance with the settings. Furthermore, rules can be applied which trigger an appropriate action when a fault is detected, e.g. a mail describing the fault might be sent to hardware support. For detailed analysis the ServerView System Monitor can be started.
advertisement
User Manual - English
FUJITSU Software ServerView
Windows Server Integration Pack V8.0 for MS SCOM 2012
June 2015 Edition
© Copyright Fujitsu Technology Solutions GmbH 2015
All hardware and software names used are trademarks of their respective manufacturers.
All rights, including rights of translation, reproduction by printing, copying or similar methods, in part or in whole, are reserved.
Offenders will be liable for damages.
All rights, including rights created by patent grant or registration of a utility model or design, are reserved.
Delivery subject to availability. Right of technical modification reserved.
Contents
Updating the ServerView Library Management Pack ........................................ 11
Properties of the ServerView Windows Server Integration Pack ...................... 13
Discovering and monitoring PRIMERGY servers................................................. 14
Displayed properties of recognized PRIMERGY servers .......................................... 15
Virtual machine is recognized as a PRIMERGY server ............................................ 16
Discovering and monitoring the server components ........................................ 16
Discovering the hardware subsystems (components) .......................................... 16
SV Integration for MS SCOM
Contents
Updating the state of the hardware subsystems .................................................. 22
Windows Management Instrumentation (WMI) ............................................. 23
SCCI Management Software (ServerView Agents) ........................................... 24
Windows Management Instrumentation (WMI) ............................................. 24
Fujitsu Systems Core Library
MP .......................................... 25
Fujitsu PRIMERGY Windows Servers
MP ............................... 26
Fujitsu PRIMERGY Windows Server Tasks ........................................................... 29
Delete PRIMERGY Server Component Inventory .................................................... 30
4 SV Integration for MS SCOM
Contents
Entries in the Operations Manager’s Event Log ................................................ 33
Creating test entries in the Windows Event Log ............................................... 33
Updating older versions of the Windows Server Integration Pack.................... 35
Use ServerView System Monitor to examine a PRIMERGY Server .......................... 36
Enable / Disable Windows Installer Logging (Debug) .......................................... 37
SV Integration for MS SCOM
1.
Introduction
The PRIMERGY ServerView Suite from Fujitsu Technology Solutions offers numerous ServerView integration modules which enable PRIMERGY servers to be integrated easily into other enterprise management systems.
This manual describes the ServerView Windows Server Integration Pack V8.0, which enables
Fujitsu PRIMERGY Windows Servers to be integrated into System Center 2012 Operations
Manager (SCOM 2012). All SCOM 2012 editions up to SCOM 2012 R2 are supported.
This integration pack allows PRIMERGY Windows Servers from Fujitsu Technology Solutions to be monitored via SCOM. Monitoring of a Fujitsu PRIMERGY Windows Server is implemented using the monitors of hardware and software components and is displayed by means of icons.
If errors occur during hardware monitoring of a PRIMERGY Windows Server, the ServerView
Agent enters these as event entries in the Windows Event Log of the managed server. The
SCOM Agent which is located on the monitored systems sends these events to the SCOM
Management Station, where they are evaluated and displayed on the SCOM Console by the
Management Pack in accordance with the settings.
Furthermore, rules can be applied which trigger an appropriate action when a fault is detected, e.g. a mail describing the fault might be sent to hardware support.
For detailed analysis the ServerView System Monitor can be started.
The current ServerView Windows Server Integration Pack for SCOM 2012 is provided on the latest PRIMERGY ServerView Suite DVD from Fujitsu Technology Solutions or under:
http://download.ts.fujitsu.com/prim_supportcd/SVSSoftware/
1.1
Purpose and target groups
This manual is intended for system administrators, network administrators and service technicians who have a thorough knowledge of hardware and software. Likewise, a sound basic knowledge of the Microsoft System Center Operations Manager 2012 is required.
SV Integration for MS SCOM 1
Changes since the last edition
1.2
Changes since the last edition
The ServerView Windows Server Integration Pack V8.0 includes the following new features:
Fujitsu Management Packs in general have been re-structured to accommodate the integration of all Fujitsu Management Packs in a streamlined fashion.
For the ServerView Windows Server Integration Pack this means the following changes: o
The former monolithic Management Pack has been split into a Management Pack suite of separate MPs. o
The default installation folder was changed from
“%ProgramFiles(x86)%\Fujitsu\ServerView Suite\SCOM Integration” to
“%ProgramFiles%\Fujitsu\ServerView Suite\SCOM Integration\SVISCOM-Win”.
o
The file setup with in the installation folder was changed. See chapter 3.1.1 Installed files
o
The class and object names within the ServerView Windows Server Integration Pack had to be changed. Any customer override packs or scripts addressing MP objects
probably need to be adapted. See chapter 5.5.1 Migrating from versions before V8.0
for more details.
Component tracking was added to the ServerView Windows Server Integration Pack. See
chapter 4.7.4 Delete PRIMERGY Server Component Inventory
for details.
A task to reset the component tracking data has been added. See 4.7.4 Delete PRIMERGY
Server Component Inventory for details.
The variable ‘DebugString’ for Discovery Data Sources has been removed. Debugging is
now solely controlled via SVISCOMLog.ini. See chapter 5.4 Creating log files for details.
A new task to call web-based ServerView System Monitor was added.
Tasks calling ServerView Operations Manager have been removed.
2 SV Integration for MS SCOM
ServerView Suite link collection
1.3
ServerView Suite link collection
Via the link collection, Fujitsu Technology Solutions provides their customers with numerous downloads and further information on the ServerView Suite and PRIMERGY servers
For ServerView Suite, links are offered on the following topics:
Forum
Service Desk
Manuals
Product information
Security information
Software downloads
Training
The downloads include the following:
–
Current software versions for the ServerView Suite and additional Readme files.
–
Information files and update sets for system software components (BIOS, firmware, drivers, ServerView Agents and ServerView Update Agents) for updating the PRIMERGY servers via ServerView Update Manager or for locally updating individual servers via ServerView Update Manager Express.
–
The current version of all documentation on the ServerView Suite.
All downloads from the Fujitsu Technology Solutions web server are free of charge.
For PRIMERGY servers, links are offered on the following topics:
Service Desk
Manuals
Product information
Spare parts catalogue
SV Integration for MS SCOM 3
Documentation for ServerView Suite
Access to the ServerView link collection
You can reach the link collection of the ServerView Suite in various ways:
1. Via ServerView Operations Manager.
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.
The start page of the online documentation can be reached via the following link:
http://manuals.ts.fujitsu.com
In the selection list on the left, select x86 servers
.
Click the menu item PRIMERGY ServerView Links .
This opens the start page of the ServerView link collection.
3. Via the ServerView Suite DVD
In the start window of the ServerView Suite DVD, select the option Select ServerView
Software Products .
Click
Start
to open the page with the software products of the ServerView Suite.
On the menu bar select
Links
to open the start page of the ServerView link collection.
1.4
Documentation for ServerView Suite
The documentation can be downloaded free of charge from the Internet. You will find the online documentation at
http://manuals.ts.fujitsu.com
under the link x86 servers
.
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
).
4 SV Integration for MS SCOM
Notational Conventions
1.5
Notational Conventions
The following notational conventions are used in this manual:
Warning
This symbol is used to draw attention to risks which may represent a health hazard or which may lead to data loss or damage to the hardware
italics
<variable>
Information
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.
Commands, menu items, names of buttons, options, file names and path names are shown in italics in descriptive text.
Angle brackets are used to enclose variables which are replaced by values.
Screen output
Please note that the screen output shown in this manual may not correspond to the output from your system in every detail. System-related differences between the menu items available can also arise.
SV Integration for MS SCOM 5
2.
Integration requirements
The requirements specified below must be satisfied for integration.
Management station
Microsoft System Center 2012 Operations Manager
Windows Server 2008 R2 / 2012 / 2012 R2.
See the requirements for the relevant SCOM version
SQL Server 2008 / 2012 / 2014.
See the requirements for the relevant SCOM version
Managed PRIMERGY servers
Windows Server 2008 [R2] or Windows Server 2012 [R2]
Windows Management Instrumentation (WMI)
ServerView Agents >= V6.00.04 for Windows Server 2012 and later use Agents >= V6.12.xx (V6.20.xx excluded)
ServerView RAID for RAID monitoring
Management controller iRMC (integrated Remote Management Controller) (for power consumption monitoring)
Installed SCOM agent
SV Integration for MS SCOM 7
Setting trap severities for ServerView Agents
2.1
Setting trap severities for ServerView Agents
To permit ServerView events to be displayed in SCOM, they must be written to the Windows
Event Log. For this purpose the required trap severities must be enabled for the ServerView
Agents.
Using the start menu function
Start – [All] Programs – Fujitsu – ServerView Suite – Agents –
Agents Configuration
open the dialog box below, and in the Trap Forwarding tab enable the required trap severities under Report to system event log .
2.2
Updating ServerView Agents
When updating the ServerView Agents set the relevant PRIMERGY server in Maintenance Mode during this action.
Failure to set target servers where ServerView Agents are to be updated in maintenance mode may lead to an incomplete installation of ServerView Agents.
This may impact the monitoring capabilities of the ServerView Agents and the
ServerView Windows Server Integration Pack
8 SV Integration for MS SCOM
3.
Installation and uninstallation
3.1
Installing ServerView Integration Pack
The installation program
SVISCOM-Win.exe
is located on the ServerView Suite DVD at
<DVDroot>\SVSSoftware\Software\Integration_Solutions\SCOM or as a download on the website at
http://download.ts.fujitsu.com/prim_supportcd/SVSSoftware/
The installation program first runs some basic checks then start the Installation Wizard. Follow the instructions displayed during the installation process.
3.1.1
Installed files
The default installation path on the management station is:
-
%ProgramFiles%\Fujitsu\ServerView Suite\SCOM Integration
The following files are copied into the installation directories:
Folder Files
SVSICOM-Win sub folder
Management Packs sub folder
EULA_en.pdf
EULA_jp.pdf
PRIMERGYServerEventsSCOM_en.pdf sv-intpack-scom-win-en.pdf windows_manual_elx.pdf
Fujitsu.ServerView.Library.mp
Fujitsu.Servers.PRIMERGY.WindowsSeed.mp
Fujitsu.Servers.PRIMERGY.Windows.mp
Fujitsu.Servers.PRIMERGY.Windows.SC2MIB.Alerts.mp
(optional)
Fujitsu.Servers.PRIMERGY.Windows.RAIDMIB.Alerts.mp (optional)
After Installation start the SCOM console with the command
Microsoft.EnterpriseManagement.Monitoring.Console.exe /clearcache.
SV Integration for MS SCOM 9
3.1.2
SCOM Console only
Update to a new version
To be able to call ServerView System Monitor and iRMC Remote Management from a server which only features the SCOM Console, install the ServerView Windows Server Integration Pack on all servers with SCOM Consoles from where either of the web sites is to be called.
Close the console once after installation to make sure the console reads all new environment variables.
3.1.3
Importing Management Packs
Management packs installed by the ServerView Windows Server Integration Pack are located the folder ‘Management Packs’ within the installation folder. This folder holds all management packs from ServerView Integration Packs for System Center Operations Manager not only from the ServerView Windows Server Integration Pack.
Management packs are imported in the usual way from the SCOM Console.
To import the Management Packs SCOM administrator rights are necessary.
All Management Packs of the ServerView Windows Server Integration Pack must be imported.
See chapter 3.1.1 Installed files for details. They can be installed all at one time.
3.2
Update to a new version
Update installation is not supported by the ServerView Windows Server Integration Pack. The process is a full uninstallation of the old version followed by the installation of the new version.
Follow chapter 3.3 Uninstalling ServerView Integration Pack to uninstall the old ServerView
Windows Server Integration Pack.
Follow chapter 3.1 Installing ServerView Integration Pack to install the new ServerView
Windows Server Integration Pack.
10 SV Integration for MS SCOM
Uninstalling ServerView Integration Pack
3.3
Uninstalling ServerView Integration Pack
The ServerView Windows Server Integration Pack is uninstalled via the following steps:
Remove the corresponding override management packs if any from SCOM.
To keep existing override settings, e.g. to re-use in a new version, the override management packs should be exported and saved.
Remove the PRIMERGY Windows Server Management Packs from SCOM.
If other ServerView Integration Packs for System Center Operations Manager have been installed, the ServerView Library Management Pack should not be uninstalled.
Uninstall the ServerView Windows Server Integration Pack from the SCOM server.
To remove the Management Packs you need SCOM administrator rights.
The ServerView Windows Server Integration Pack should be removed from all SCOM
Remote Consoles.
3.4
Updating the ServerView Library Management Pack
The ServerView Library Management Pack is used and referenced by all Fujitsu ServerView
Integration Packs for System Center Operations Manager.
If a ServerView Integration Pack installs a newer version of the ServerView Library
Management Pack, it is necessary to uninstall all Fujitsu management packs including their Override management packs and reinstall all Fujitsu management packs from the folder ‘Management Packs’ together with the updated ServerView Library Management
Pack.
User Guide
11
4.
Properties of the ServerView Windows Server
Integration Pack
4.1
Management Packs
The
Fujitsu ServerView Core Library
Management Pack contains the basic definitions to manage
Fujitsu systems in a consolidated manner in SCOM. This Management Pack is distributed with all Fujitsu SCOM Integration Packs. It cannot be modified or exported.
The file name of this package is
Fujitsu.ServerView.Library.mp.
The
Fujitsu PRIMERGY Windows Servers Seed
Management Pack contains the initial Fujitsu
PRIMERGY Windows Server Discovery. It cannot be modified or exported.
The file name of this package is
Fujitsu.Servers.PRIMERGY.WindowsSeed.mp.
The Fujitsu PRIMERGY Windows Servers Management Pack contains the definitions for discovery and monitoring of Fujitsu PRIMERGY servers running Windows operating systems. It cannot be modified or exported.
The file name of this package is
Fujitsu.Servers.PRIMERGY.Windows.mp.
The Fujitsu PRIMERGY Windows Servers SC2.MIB Alerts Management Pack contains rules to catch error and warning alerts from the ServerView hardware MIB SC2.mib.
This Management Pack is not necessary to ensure full monitoring of PRIMERGY Windows servers but is provided for customers who do not only want to see status changes for hardware but want to receive all hardware events as individual alerts.
The file name of this package is Fujitsu.Servers.PRIMERGY.Windows.SC2MIB.Alerts.mp.
The
Fujitsu PRIMERGY Windows Servers
RAID.MIB Alerts Management Pack contains rules to catch error and warning alerts from the ServerView RAID.mib.
This Management Pack is not necessary to ensure full monitoring of PRIMERGY Windows server’s RAID environment but is provided for customers who do not only want to see status changes for the server’s RAID environment but want to receive all RAID events as individual alerts.
The file name of this package is
Fujitsu.Servers.PRIMERGY.Windows.RAIDMIB.Alerts.mp.
SV Integration for MS SCOM 13
PRIMERGY server computer groups
4.2
PRIMERGY server computer groups
The PRIMERGY servers are categorized in groups:
BX models (e.g. BX920)
CX models (e.g. CX122)
MX models (e.g. MX130)
RX models (e.g. RX100, RX300)
SX models (e.g. SX150, SX350)
TX models (e.g. TX150, TX300)
PRIMERGY models which do not fit in any of the above groups
Econel models are assigned to the TX model group (Econel Floorstand) or to the RX model group (Econel 230R).
For a description of the presentation of the servers and the PRIMERGY server computer groups, see section
4.3
Discovering and monitoring PRIMERGY servers
PRIMERGY servers and their components can be discovered and monitored only if they have been included in SCOM management (installed SCOM Agent on the servers to be monitored).
The (seed) initial discovery is managed by checking the target server’s registry in the
SystemInformation and Bios sections for manufacturer and system type.
The servers are then recognized and monitored using scripts and on the basis of the data supplied by WMI and ServerView CIM providers.
Only servers with the following manufacturer and model data are recognized:
–
Manufacturer: Fujitsu... or FUJITSU... or FSC
–
Model: PRIMERGY ...
The exact model is detected by means of the chassis name.
14 SV Integration for MS SCOM
Discovering and monitoring PRIMERGY servers
4.3.1
Displayed properties of recognized PRIMERGY servers
The following properties of a managed server are displayed:
Display Name:
host name of the server
Network Name: fully qualified DNS name of the server
Model:
complete model name of the server
Serial Number:
serial number of the server
Operating System:
detailed version of the OS
Manufacturer: system manufacturer
Chassis Model:
chassis name
Cabinets:
IDs of main and attached cabinets
System Firmware: version of the system firmware
Physical Memory: available memory
Total Logical Disk Space:
total capacity of the partitions configured as logical disks
Monitoring Agents:
name and version of the ServerView Agents
BMC Address: IPv4 address of the iRMC (if available)
BMC DNS name: fully qualified DNS name of the iRMC (if available)
The properties of a server which are discovered are displayed in the
Detail View
below a
Status or a Diagram view.
4.3.2
Health state of a PRIMERGY server
The health state of a PRIMERGY server is determined by the state of its hardware and software components. The component with the most severe error determines the final health state of the PRIMERGY server. This means component redundancy is not supported.
This state is also passed on to the model group and the PRIMERGY server group (roll-up monitor).
User Guide
15
Discovering and monitoring the server components
4.3.3
Virtual machine is recognized as a PRIMERGY server
Virtual machines are not designed to be used for monitoring with the Fujitsu Management
Pack.
If a virtual machine is detected as a PRIMERGY server and included in the monitoring activities
(e.g. because a physical PRIMERGY server was converted to a virtual machine), this happens because the values used to detect the PRIMERGY server are still stored in the registry.
To remove the virtual machine from SCOM monitoring, place the virtual machine into
Maintenance Mode and delete the following entry in the registry together with its entire content:
HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\ServerView Suite\SCOM Integration\SVISCOM-
Win\PYServerData or
HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\ServerView Suite\SCOM Integration\PYServerData
4.4
Discovering and monitoring the server components
The server components are discovered and monitored with scripts on the basis of data retrieved via the ServerView Agents’ CIM providers (WMI), via the ServerView RAID Agent and occasionally via other ServerView Agent APIs.
Only components which exist are displayed in Diagram View. If, for example, no fans can be detected (e.g. in a blade server where fans are managed by the chassis), the component is not displayed. Subsystems which do not contain components with a usable state at discovery time are not displayed, either. All components are shown in Health Explorer but only existing components are monitored.
Instances of the same type in a component are combined in a group and monitored together
(e.g. all CPUs of a server belong to the processor group). In the case of an error the faulty instance is displayed in the Health Explorer. The instance with the severest error determines the overall state of the group.
By default events with the severity
Critical
generate an alert and events with the severity
Warning
do not generate an alert. This default setting can be overridden.
4.4.1
Discovering the hardware subsystems (components)
The hardware subsystems of a PRIMERGY server which are listed below can be discovered and monitored.
16 SV Integration for MS SCOM
Discovering and monitoring the server components
4.4.1.1 PRIMERGY Overall State
This component is used to display and monitor the overall state of a PRIMERGY server.
Components that are not covered by the specific hardware components described below are also monitored here. Use the ServerView System Monitor task to check for details.
Icon
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
Information
PRIMERGY Overall State
<Name of the server>
<Monitored components>
None
<IPv4 address of the BMC>
<FQDN of the iRMC>
PRIMERGY Overall Communication
The PRIMERGY Overall State also comprises a communication monitor which monitors the communication between the scripts run by SCOM and the ServerView Agents service.
Problems here indicate that hardware monitoring is impaired. Restart ‘ServerView Server
Control’ service and use the ServerView System Monitor task to check for details.
4.4.1.2 Processors
Processors which physically exist are discovered, their data is displayed and their health state is monitored.
Icon Information
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
Processors
<Name of the server>
<Names of physical CPUs>
<CPU Type / Number of cores>
<IPv4 address of the BMC>
<FQDN of the iRMC>
User Guide
17
Discovering and monitoring the server components
4.4.1.3 Memory
Memory modules which are connected are discovered, their data is displayed, and their health state is monitored.
Icon Information
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
Memory
<Name of the server>
<Total Memory>
<Type of memory>: <Number of memories of type>
<IPv4 address of the BMC>
<FQDN of the iRMC>
4.4.1.4 Storage
Available volumes are discovered, their data is displayed, and their health state is monitored.
Icon Information
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
Storage
<Name of the server>
<Storage devices>
<Capacity of storage devices>
<IPv4 address of the BMC>
<FQDN of the iRMC
4.4.1.5 Networks (Ethernet)
Available Network Adapters are discovered, their data is displayed, and their health state is monitored.
Icon
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
Information
Networks (Ethernet)
<Name of the server>
<Names of Network Adapters/Interfaces>
<MAC addresses>
<IPv4 address of the BMC>
<FQDN of the iRMC>
18 SV Integration for MS SCOM
Discovering and monitoring the server components
4.4.1.6 Management Controller
The iRMC (integrated Remote Management Controller) is discovered, its data is displayed and its health state is monitored.
Icon
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
Information
Management Controller
<Name of the server>
<Type>
Firmware Version: <Version>
<IPv4 address of the BMC>
<FQDN of the iRMC>
4.4.1.7 Fans (Cooling)
Connected fan modules of PRIMERGY servers and their connected extension modules are discovered, their data is displayed and their health state is monitored.
Icon
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
Information
Fans (Cooling)
<Name of the server>
Number of Fan Devices: <number>
None
<IPv4 address of the BMC>
<FQDN of the iRMC>
4.4.1.8 Temperatures
Temperature sensors which physically exist are discovered, their data is displayed, and their health state is monitored.
Icon
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
Information
Temperatures
<Name of the server>
Number of Temperatures: <number>
None
<IPv4 address of the BMC>
<FQDN of the iRMC>
User Guide
19
Discovering and monitoring the server components
4.4.1.9 Power Supplies
Power supply modules which physically exist are discovered, their data is displayed, and their health state is monitored.
Icon Information
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
Power Supplies
<Name of the server>
<Power Supplies>
None
<IPv4 address of the BMC>
<FQDN of the iRMC>
4.4.1.10 Power Consumption
Power Consumption is monitored if the iRMC supports power consumption monitoring and if the iRMC Power Control Mode is set to Power Limit . If the iRMC Power Control Mode is set to any other mode, Power Consumption monitoring always shows OK.
Icon
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
Information
Power Consumption
<Name of the server>
<IPv4 address of the BMC>
<FQDN of the iRMC>
Total Power
None
4.4.1.11 Voltages
Voltage sensors which physically exist are discovered, their data is displayed, and their health state is monitored.
Icon
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
Information
Voltages
<Name of the server>
Number of Voltages: <number>
None
<IPv4 address of the BMC>
<FQDN of the iRMC>
20 SV Integration for MS SCOM
Discovering and monitoring the server components
4.4.1.12 RAID Subsystem
If ServerView RAID is installed, SV RAID itself and all RAID adapters are discovered, their data is displayed, and their health state is monitored.
Icon Information
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
RAID Subsystem
<Name of the server>
ServerView RAID, <RAID adapters>
<Version/Type>
<IPv4 address of the BMC>
<FQDN of the iRMC>
4.4.1.13 RAID Logical Drive
The status of the logical RAID drives from ServerView RAID is discovered and monitored via the
ServerView Agents.
Icon
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
Information
RAID Logical Drives
<Name of the server> on adapter
<x> ’<adapter name>: <logical drives>
RAID Level:
<number> <RAID level>
<IPv4 address of the BMC>
<FQDN of the iRMC>
4.4.1.14 RAID Logical Drives
The status of the logical RAID drives from ServerView RAID is discovered and monitored via the
ServerView Agents.
Icon
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
Information
RAID Logical Drives
<Name of the server> on adapter
<x> ’<adapter name>: <logical drives>
RAID Level:
<RAID level>
<IPv4 address of the BMC>
<FQDN of the iRMC>
User Guide
21
Discovering and monitoring the server components
4.4.1.15 RAID Physical Disks
The status of the physical RAID disks from ServerView RAID is discovered and monitored via the
ServerView Agents.
Icon
Display Name:
Server Name:
Devices:
Device Information:
BMC Address:
BMC DNS name:
Information
RAID Physical Disks
<Name of the server> on adapter <x> ’<adapter name>: <physical disks>
Size: <capacity>
<IPv4 address of the BMC>
<FQDN of the iRMC>
4.4.2
Updating the state of the hardware subsystems
By default, the configuration of the hardware components of a PRIMERGY server is discovered automatically every 4 hours.
Set the server in maintenance mode for a brief period. Once the maintenance mode has elapsed, SCOM automatically discovers the hardware components again. Alternatively change the hardware component discovery interval to force an update by performing a (temporary) override for all ‘Discovery Rule for Windows Server Health Collection’.
4.4.3
Discovering the required services
The services of a PRIMERGY server which are listed below are discovered and monitored.
4.4.3.1 ServerView Agents
The ServerView Server Control service is Fujitsu’s central service to monitor PRIMERGY hardware components.
Monitor class: SCCI Management Software
Icon Information
Display Name:
Version:
Server Name:
Devices:
BMC Address:
BMC DNS name:
ServerView Agent
<Version of the agent>
<Name of the server>
Service ’SrvCtrl.exe’
<IPv4 address of the BMC>
<FQDN of the iRMC>
22 SV Integration for MS SCOM
Discovering and monitoring the server components
4.4.3.2 Windows Management Instrumentation (WMI)
Monitor class: WMI Management Software
Icon
Display Name:
Version:
Server Name:
Devices:
BMC Address:
BMC DNS name:
Information
Windows Management Instrumentation
<WMI version>
<Name of the server>
None
<IPv4 address of the BMC>
<FQDN of the iRMC>
4.4.3.3 ServerView RAID
ServerView RAID manages and monitors all RAID controllers of PRIMERGY servers.
Monitor class: ServerView RAID
Icon Information
Display Name:
Version:
Server Name:
Devices:
BMC Address:
BMC DNS name:
ServerView RAID
<Version>
<Name of the server>
Service ’amService.exe
<IPv4 address of the BMC>
<FQDN of the iRMC>
4.4.4
Monitoring hardware components
Hardware components are monitored by means of VBScripts. The monitoring scripts are called at regular intervals (depending on the component every 120-180 seconds; settable) and check the state of the components.
All hardware components are collected in a Health Collection and are displayed in the Health
Explorer (see
If the monitoring function reports the
Critical
state for a component, a corresponding alert is generated. Warning alerts are per default disabled.
When the component returns to the OK state, the alert is resolved and is no longer displayed in the
Active Alerts
view (see
User Guide
23
Discovering and monitoring the server components
4.4.5
Monitoring the required services
The required services are monitored by individual monitors per service. The health state of the services can be displayed in the Health Explorer.
4.4.5.1 SCCI Management Software (ServerView Agents)
The state of this software component is determined by the following service:
–
ServerView Server Control (Service Name:
SvrCtrl.exe
)
If the monitoring function reports the
Critical
state, a corresponding alert is generated.
If the ServerView Agents are in
Critical
state, monitoring the PRIMERGY server is no longer possible.
When the component returns to the
OK
state, the alert is resolved and no longer displayed in the Active Alerts view (see
4.4.5.2 Windows Management Instrumentation (WMI)
The state of this software component is determined by the Windows Management
Instrumentation Service (Service Name: winmgmt
). If this service is not running, the state of the WMI component is set to Critical .
If the monitoring function reports the
Critical
state, a corresponding alert is generated.
If the WMI service is in
Critical
state, monitoring the PRIMERGY server is limited.
When the component returns to the
OK
state, the alert is resolved and no longer displayed in the Active Alerts view (see
4.4.5.3 ServerView RAID Manager
The state of this software component is determined by the ServerView RAID Manager Service
(Service Name: amService
). If this service is not running, the state of the ServerView RAID component is set to Critical .
If the monitoring function reports the
Critical
state, a corresponding alert is generated.
When the component returns to the
OK
state, the alert is resolved and no longer displayed in the
Active Alerts
view (see
24 SV Integration for MS SCOM
Views
4.5
Views
The health state in all views is displayed by the usual health state icons of the Operations
Manager.
4.5.1
Views defined by the
Fujitsu Systems Core Library MP
When integrating the Fujitsu ServerView Core Library Management Pack a Fujitsu ServerView
Systems
node is created in the
Monitoring
pane of the SCOM Console. The following views are displayed in this node:
–
Active Alerts
–
Health Collection State
–
Servers Diagram
–
Systems State
These views display all objects which are assigned to the class the particular view targets.
Which systems this class comprises depend on the further Fujitsu Management Packs that have been installed, e.g. the
Fujitsu PRIMERGY Windows Servers
Management Pack.
The views installed by the Fujitsu ServerView Systems Core Library Management Pack comprise all systems that are targeted by Management Packs that depend on the Fujitsu ServerView
Systems Core Library
Management Pack and aim for an easy overview of all Fujitsu systems.
User Guide
25
Views
4.5.2
Views defined by the
Fujitsu PRIMERGY Windows Servers MP
When integrating the Fujitsu PRIMERGY Windows Servers Management Pack a new node
PRIMERGY Windows Servers is created below the Fujitsu Systems node in the Monitoring pane of the SCOM Console. The following views are displayed in this node:
–
Active Alerts
–
Health Collection State
–
Servers Diagram
–
Systems State
The views installed by the
Fujitsu PRIMERGY Windows Servers
Management Pack target and display PRIMERGY Windows servers only.
4.5.3
Active Alerts Views
The Active Alerts views display all alerts which are assigned to the class the particular view targets. Only alerts which have the resolution state
Not Closed
are displayed.
The following causes can trigger an alert:
–
If a component monitor is in the
Critical
state and a corresponding alert is displayed for this component.
This alert is "auto-resolving”: As soon as the cause has been resolved, the alert is no longer displayed in the view.
–
An event for which a rule is defined in the Management Pack is entered in the Windows
Event Log of a monitored server. These alerts remain in the display until they are explicitly closed.
26 SV Integration for MS SCOM
Views
By default alerts are only generated by events which have been entered in the Windows Event
Log (Application, Operations Manager or System) with the severity
Critical
(
Error
). Events with the severity
Warning
can also be displayed if they are enabled by the user.
Alerts which are placed in the resolution state
Closed
no longer appear in the
Active Alerts view.
For some alerts Alarm Suppression is enabled. In this case, the alert is only reported once. Any next alert of this type causes the
Repeat Count
to be increased. To display the
Repeat Count column use the personalize view
setting.
4.5.4
Health State Collection Views
The
Health State Collection views display the health state of the hardware components class the particular view targets.
4.5.5
Diagram Views
Diagram
views are the graphical presentation of the Fujitsu systems infrastructure. The connection of Fujitsu systems to PRIMERGY servers to model groups and the connection of the components to the PRIMERGY servers are presented here.
When systems are included in a group, this is indicated by a non-empty circle near the computer symbol. This group can be expanded further to display the existing systems:
The state of the hardware and software components of a server is also shown in the
Servers
Diagram
view. The components are displayed graphically together with the assigned server.
Components which are in a healthy state are included in the healthy group beneath the associated server.
If more than one component is in the Warning or Critical state, these are collected in the corresponding groups and also presented (simultaneously) beneath the PRIMERGY server.
User Guide
27
Health Explorer
The discovered instances of a component and various properties are displayed in the Detail
View
below the component representation. The following properties are displayed for each component:
Display Name: Name of the component
Server Name: Name of the system to which the component belongs
Devices:
Information of discovered device instances
Device Information:
Additional information for the devices if available
BMC Address:
IPv4 address of the integrated Remote Management Controller
BMC DNS name: Fully Qualified Domain Name, if available and DNS enabled on iRMC
4.5.6
Server State Views
The
Server State
views display the state of all servers which are assigned to the class the particular view targets.
The properties of the selected PRIMERGY server are displayed in the Details View below this view.
4.6
Health Explorer
The Health Explorer can be started from various views. It shows the components and dependencies in a tree structure. When components are in the
Warning
or
Critical
state, the corresponding subdirectories are automatically expanded in the display.
Two different displays are possible in the right-hand window of the Health Explorer: and
Knowledge
State Change Events
. Information on what the monitor displays and which actions
(resolutions) are possible and recommended is provided under the
Knowledge
tab.
All state transitions ( OK <-> Degraded <-> Error ) of the component selected from the navigation window on the left are displayed under the
State Change Events
tab. The state change is only shown for the first component responsible for the state change.
28 SV Integration for MS SCOM
Fujitsu PRIMERGY Windows Server Tasks
If the state is not OK , the component is placed in the Degraded or Error state and the faulty instance(s) are listed in the Health Explorer. If two or more components show different health states, the instance with the severest error determines the overall status of the group.
<Component>_Components
Instances of the component.
<Component>_HealthState
Degraded
At least one of the component’s instances is in the Warning state.
Error
At least one of the component’s instances is in the Critical state.
<Component>_FailedComponent
When a component is in the Degraded or Error state, the faulty instance is displayed here.
4.7
Fujitsu PRIMERGY Windows Server Tasks
Tasks are actions which can be displayed and executed in different views. They are displayed in the Actions window when a PRIMERGY server is highlighted or when PRIMERGY hardware components are selected.
Tasks of the PRIMERGY servers and server components
Computer Management
Remote Desktop
Remote Desktop Console
Delete PRIMERGY Server Component Inventory
ServerView Raid Manager
ServerView Remote Management iRMC
ServerView System Monitor
4.7.1
Computer Management
This task is used to start the Microsoft Management Console (MMC application) and permits access to the data of the highlighted PRIMERGY server.
User Guide
29
4.7.2
Remote Desktop
Fujitsu PRIMERGY Windows Server Tasks
This task is used to start the Remote Desktop in order to log in on the PRIMERGY server.
4.7.3
Remote Desktop Console
This task is used to start the Remote Desktop in console mode in order to log in on the
PRIMERGY server.
4.7.4
Delete PRIMERGY Server Component Inventory
The
Fujitsu PRIMERGY Windows Servers
Management Pack keeps track of the amount of components that have been discovered for a server und the server’s registry at
HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\ServerView Suite\SCOM Integration\SVISCOM-
Win\PYServerData .
If new components are added to a server, the component inventory is increased and an informational alert is raised.
If components are missing, an alert is raised every time the component discovery script runs again (default: every 4 hours).
This task resets the server components inventory data. The next component discovery cycle generates new inventory data without raising any alerts.
Use this task if components have been removed from a server.
4.7.5
ServerView Raid Manager
This task is used to call the web console of the ServerView Raid Manager. The task is displayed for all PRIMERGY servers even if ServerView RAID Manager is not installed on the server.
4.7.6
ServerView Remote Management iRMC
This task is used to call the console of the integrated Remote Management Controller (iRMC). If a DNS name has been found for the iRMC, the DNS name is called. Otherwise the IPv4 address of the iRMC is used.
30 SV Integration for MS SCOM
Events and alerts
4.7.7
ServerView System Monitor
This task is used to start the web-based ServerView System Monitor, which can be used to examine PRIMERGY Server in detail.
The web-based system Monitor is only available for PRIMERGY servers where ServerView
Agents V7.01 or later are installed.
For PRIMERGY servers with older SV Agents versions, log on to the server (e.g. via the
Remote Desktop task) and navigate to the on-server System Monitor via ‘Start’ – ‘All
Programs’ – ‘Fujitsu’ – ‘ServerView Suite’ – ‘Agents’ – ‘System Monitor’.
4.8
Events and alerts
This section applies only to alerts for which rules are defined in the Management
Pack(s).
Alerts remain visible in the
Active Alerts
view until they are explicitly closed (assigned the resolution state
Closed
).
Alerts are independent of monitors and have no influence on the health state of the server.
They are used only to display an event.
The following event groups are integrated in the main Management Pack:
HD.MIB
NTCluster.MIB
THRESHOLD.MIB
Duplex Data Manager (DDM.MIB)
QLogic Fibre Channel Adapters
Emulex Fibre Channel Adapters (BE2NET, BE2ISCSI)
Broadcom Network Adapters
Intel Network Adapters (E1000, E100B, IE10G, ANS Miniport)
Event Log entries of VB scripts in the Management Pack
All alerts have alert suppression enabled .
User Guide
31
Knowledge Base
The following alerts have been moved to additional Management Packs for customers who want to receive even these alerts even though the components subsystem health state is fully covered by the subsystem health state monitors (e.g. Temperatures, RAID Subsystem).
SC2.MIB
ServerView-Raid
An overview of the integrated events is provided in the files
PRIMERGYServerEventsSCOM_e.pdf
and windows_manual_elx.pdf
, which are located in the Manuals subdirectory.
Only events with the severity
Warning
or
Critical
are integrated.
4.8.1
Enabling and disabling alerts
By default all the events with the severity
Critical
generate an alert, and all the events with the severity Warning generate no alert.
To change the default settings override them in the Authoring section of the SCOM Console. The overrides must then be stored in a custom Management Pack which is writable.
4.9
Knowledge Base
A Knowledge Base is provided for the events and alerts. Depending on the alert various possible resolutions / actions after error are displayed.
These resolutions are also contained in the column of the events listed.
PRIMERGYServerEventsSCOM_en.pdf
file, in the last
32 SV Integration for MS SCOM
5.
Appendix
5.1
Supported PRIMERGY servers
The ServerView Windows Server Integration Pack does not itself support PRIMERGY servers but relies on ServerView Agents installed on the server to provide server hardware data. PRIMERGY support therefore depends on the Agents installed on the monitored system.
Please refer to the ServerView Agents’ release notes for detailed information on PRIMERGY support.
5.2
Entries in the Operations Manager’s Event Log
The VBScripts for discovering and monitoring the PRIMERGY servers and their components write messages to the Operations Manager’s Event Log when an error occurs.
These entries can be found on the monitored servers under the name Health Service Script , while the message text specifies which VBScript generated the message.
Rules defined in the MP check the event log for the above mentioned entries, which, if present, are displayed in the Active Alerts view.
Entries for errors are switched on; entries for warnings are switched off.
Overrides are available in the override file for the VB script entries.
5.3
Creating test entries in the Windows Event Log
To check whether an alert is enabled, disabled, or recognized, you can create test entries for these events in the Event Log of the relevant server using PowerShell.
SV Integration for MS SCOM 33
5.4
Creating log files
Creating log files
Log files can be created for error analysis. The log files are stored in the subdirectory
SVISCOM\SVISCOM-Win
of the directory entered in the system environment variable
TEMP
.
Usually this is the
C:\Windows\TEMP
directory (where
C:
represents the system partition in this example).
Logging options are defined in the file SVSISCOMLog.ini in this folder. If the file does not exist or was created by an older version of the Management Pack, a copy of the file with the name
SVISCOMLog.in_
is generated on each server discovery in the %TEMP%\SVSCOM\SVISCOM-Win folder.
Note that changes to the logging options will only be added to the
SVISCOMLog.in_ file.
SVISCOMLog.ini
from an older version of the ServerView Windows Server Integration
Pack may need to be updated accordingly.
SVISCOMLog.in_
contains debug options for all discovery and monitoring features of the management pack. See
SVISCOMLog.in_
on any target system for details.
In the case of error analysis using log files proceed as follows.
Rename
SVISCOMLog.in_
on the target server to
SVISCOMLog.ini.
If
SVISCOMLog.ini
already exists, check that all options of
SVISCOMLog.in_ also exist in
SVISCOMLog.ini.
Check the debug options (documented in detail within the SVISCOMLog.in_ file) for each feature to be monitored and set to the desired value.
The following log files are created as required:
–
PRIMERGYServerDiscoveryTrace_<servername>.log
–
PRIMERGYComponentsDiscoveryTrace_<servername>.log
–
PRIMERGYComponentsMonitorTrace_<servername>_<component>.log
–
PRIMERGYCommunicationMonitorTrace_<servername>_<component>.log
–
PRIMERGYServerFCEvents_<servername>.log
These files must be sent to Fujitsu Support for further analysis.
If you wish to disable the creation of log files again, delete or rename
SVISCOMLog.ini or change the logging options within the file.
34 SV Integration for MS SCOM
Updating older versions of the Windows Server Integration Pack
5.4.1
Currentness of log files
When Fujitsu Management Packs are imported log files are generated promptly only if the initialization file is already available.
If the management pack already is imported log files are generated depending on the execution interval if the discovery or monitoring scripts.
In the worst case, 24 hours are necessary for all log files to be generated.
The server discovery is executed by default every 4 hours.
The component discovery is executed by default every 24 hours.
After the component discovery was successful, monitoring is run every 2-3 minutes.
Alternatively:
To create a current set of discovery log files, put the server in maintenance mode for a short time and let SCOM exit the maintenance mode. SCOM executes the server and component discovery automatically after maintenance mode has ended.
5.5
Updating older versions of the Windows Server
Integration Pack
The ServerView Windows Server Integration Pack generally does not support update.
The process is an uninstallation followed by a new installation.
5.5.1
Migrating from versions before V8.0
In version V8.0 of the ServerView Windows Server Integration Pack the road was cleared for management packs for OS other than Windows, e.g. Linux. To be able to fit all Fujitsu
Management Packs into a consolidated structure, both within the SCOM GUI and inside the management pack suite, it was necessary to change the class and object names of the old
Windows MP.
Unfortunately this means a bit of work for customers who have Override Management Packs of
their own or even scripts from a previous version. Appendix B lists the old class and object
names against the new names. Refer to the appendix to adapt old Override Management Packs or scripts.
User Guide
35
Troubleshooting
As a general rule the following actions should cover the most necessary changes:
In any (exported) Override Management Pack or Script
exchange "
Fujitsu.Servers.PRIMERGY.
" with
"
Fujitsu.Servers.PRIMERGY.Windows.
".
exchange "
Fujitsu.Servers.PRIMERGY.Components.
" with
"
Fujitsu.Servers.PRIMERGY.Windows.
"
make sure that there is no "
Fujitsu.Servers.PRIMERGY.Windows.Components.
" anywhere. If so exchange with "
Fujitsu.Servers.PRIMERGY.Windows.
".
To Override MPs add both the
Fujitsu.ServerView.Library
and the
Fujitsu.Servers.PRIMERGY
MP as reference MPs. Refer to Appendix B for classes defined in these management packs
and add the alias name to those classes.
These actions will migrate most classes within custom Override MPs or scripts to the new names. For any remaining issues refer to the messages SCOM or PowerShell throw.
5.6
Troubleshooting
5.6.1
Use ServerView System Monitor to examine a PRIMERGY
Server
If a PRIMERGY server seems to have a problem (e.g. the PRIMERGY Overall State is bad) and the cause of this problem cannot be determined via SCOM, it may help to use the System Monitor for closer examination.
Highlight the server and use the ServerView System Monitor task to start System Monitor.
The web-based system Monitor is only available for PRIMERGY servers where ServerView
Agents V7.01 or later are installed.
For PRIMERGY servers with older SV Agents versions, log on to the server (e.g. via the
Remote Desktop task) and navigate to the on-server System Monitor via ‘Start’ – ‘All
Programs’ – ‘Fujitsu’ – ‘ServerView Suite’ – ‘Agents’ – ‘System Monitor’.
36 SV Integration for MS SCOM
Hints and known issues
5.6.2
No event logging of the controller driver(s)
Not all controller drivers create events in the Windows Event Log by default. For detailed information on activating the event logging, see the manual or readme file of the controller drivers.
5.6.3
Internet Explorer has no Java Plugin
The installation address of the Internet Explorer is stored in the system environment variable
"IEXPLORERPath".
If this value directs to an MSIE that has no Java PlugIn, change this environment variable to an address of the IE with an installed Java PlugIn.
5.6.4
Enable / Disable Windows Installer Logging (Debug)
In case there are problems with the installation procedure refer to the following Microsoft knowledge base article ( http://support.microsoft.com/kb/223300 ) that describes how to enable and disable logging.
5.7
Hints and known issues
-
User Guide
37
6.
Appendix B
6.1
V8.0 class names vs. former names
V8.0 Name
Fujitsu.ServerView.AllInstanceGroup
Fujitsu.ServerView.Group
Fujitsu.ServerView.ServersGroup
Fujitsu.ServerView.System
Fujitsu.ServerView.Server
Fujitsu.ServerView.LogicalHardware
Fujitsu.ServerView.HealthCollection
Fujitsu.ServerView.ManagementSoftware
V8.0 Name
Fujitsu.Servers.PRIMERGY.WindowsSeed
SV Integration for MS SCOM
V8.0 Management Pack
Fujitsu.ServerView.Library
Fujitsu.ServerView.Library
Fujitsu.ServerView.Library
Fujitsu.ServerView.Library
Fujitsu.ServerView.Library
Fujitsu.ServerView.Library
Fujitsu.ServerView.Library
Fujitsu.ServerView.Library
8.0 Management Pack
Fujitsu.Servers.PRIMERGY.WindowsSeed
Former Name
-
Fujitsu.Servers.Group
Fujitsu.Servers.ServersGroup
-
Fujitsu.Servers.Server
Fujitsu.Servers.LogicalHardware
-
Fujitsu.Servers.ManagementSoftware
Former Name
-
39
V8.0 class names vs. former names
V8.0 Name 8.0 Management Pack Former Name
Fujitsu.Servers.PRIMERGY.Windows.ServersGroup Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.ServersGroup
Fujitsu.Servers.PRIMERGY.Windows.BXServersGroup Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.BXServersGroup
Fujitsu.Servers.PRIMERGY.Windows.CXServersGroup Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.CXServersGroup
Fujitsu.Servers.PRIMERGY.Windows.MXServersGroup Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.MXServersGroup
Fujitsu.Servers.PRIMERGY.Windows.RXServersGroup Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.RXServersGroup
Fujitsu.Servers.PRIMERGY.Windows.SXServersGroup Fujitsu.Servers.PRIMERGY.Windows -
Fujitsu.Servers.PRIMERGY.Windows.TXServersGroup Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.TXServersGroup
Fujitsu.Servers.PRIMERGY.Windows.XXServersGroup Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.XXServersGroup
Fujitsu.Servers.PRIMERGY.Windows.Server Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Server
Fujitsu.Servers.PRIMERGY.Windows.BXServer
Fujitsu.Servers.PRIMERGY.Windows.CXServer
Fujitsu.Servers.PRIMERGY.Windows.MXServer
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.BXServer
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.CXServer
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.MXServer
Fujitsu.Servers.PRIMERGY.Windows.RXServer
Fujitsu.Servers.PRIMERGY.Windows.SXServer
Fujitsu.Servers.PRIMERGY.Windows.TXServer
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.RXServer
Fujitsu.Servers.PRIMERGY.Windows -
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.TXServer
Fujitsu.Servers.PRIMERGY.Windows.XXServer
<removed>
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.XXServer
- Fujitsu.Servers.HealthCollection
Fujitsu.Servers.PRIMERGY.Windows.HealthCollection Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.HealthCollection
40 SV Integration for MS SCOM
V8.0 class names vs. former names
<removed>
<removed>
<removed>
<removed>
<removed>
<removed>
<removed>
<removed>
<removed>
<removed>
<removed>
<removed>
<removed>
<removed>
Fujitsu.Servers.PRIMERGY.Windows.Processors
Fujitsu.Servers.PRIMERGY.Windows.Memory
Fujitsu.Servers.PRIMERGY.Windows.Fans
Fujitsu.Servers.PRIMERGY.Windows.TemperatureSens
ors
-
-
-
-
-
-
-
-
-
-
-
-
-
Fujitsu.Servers.PRIMERGY.Processors
Fujitsu.Servers.PRIMERGY.Memory
Fujitsu.Servers.PRIMERGY.Fans
Fujitsu.Servers.PRIMERGY.TemperatureSensors
Fujitsu.Servers.PRIMERGY.Voltages
Fujitsu.Servers.PRIMERGY.ServerNetworks
Fujitsu.Servers.PRIMERGY.ServerStorage
Fujitsu.Servers.PRIMERGY.ManagementController
Fujitsu.Servers.PRIMERGY.PowerSupplies
Fujitsu.Servers.PRIMERGY.PowerConsumption
Fujitsu.Servers.PRIMERGY.RaidSubsystem
Fujitsu.Servers.PRIMERGY.RaidLogicalDrive
Fujitsu.Servers.PRIMERGY.RaidPhysicalDisk
- Fujitsu.Servers.PRIMERGY.PYOverallState
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Components.Processors
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Components.Memory
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Components.Fans
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Components.TemperatureSe
nsors
User Guide 41
V8.0 class names vs. former names
Fujitsu.Servers.PRIMERGY.Windows.VoltageSensors Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Components.Voltages
Fujitsu.Servers.PRIMERGY.Windows.ServerNetworks Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Components.ServerNetworks
Fujitsu.Servers.PRIMERGY.Windows.ServerStorage Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Components.ServerStorage
Fujitsu.Servers.PRIMERGY.Windows.ManagementCont
roller
Fujitsu.Servers.PRIMERGY.Windows.PowerSupplies
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Components.ManagementCo
ntroller
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Components.PowerSupplies
Fujitsu.Servers.PRIMERGY.Windows.PowerConsumptio
n
Fujitsu.Servers.PRIMERGY.Windows.RaidSubsystem
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Components.PowerConsumpt
ionPower
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Components.RaidSubsystem
Fujitsu.Servers.PRIMERGY.Windows.RaidLogicalDrives Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Components.RaidLogicalDriv
e
Fujitsu.Servers.PRIMERGY.Windows.RaidPhysicalDisks Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Components.RaidPhysicalDis
k
Fujitsu.Servers.PRIMERGY.Windows.PYOverallState
Fujitsu.Servers.PRIMERGY.Windows.ManagementClie
ntSoftware
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.Components.PYOverallState
Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.ManagementClientSoftware
Fujitsu.Servers.PRIMERGY.Windows.WMIManagemen Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.WMIManagement
Fujitsu.Servers.PRIMERGY.Windows.RaidManagement Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.RaidManagement
Fujitsu.Servers.PRIMERGY.Windows.SCCIManagement Fujitsu.Servers.PRIMERGY.Windows Fujitsu.Servers.PRIMERGY.SCCIManagement
42 SV Integration for MS SCOM
advertisement
Key Features
- Integrates Fujitsu PRIMERGY Windows Servers into SCOM 2012
- Monitors hardware and software components
- Provides error alerts and status changes for hardware
- Enables detailed analysis using ServerView System Monitor
- Supports all SCOM 2012 editions up to SCOM 2012 R2
- Provides PRIMERGY server component inventory tracking