Fujitsu Software ServerView Out-of-Band Server Integration Pack for Microsoft System Center Operations Manager (SCOM) ========================================================= Version 8.5.3.0 Date 2023-06-20 Status Released Release Notes Copyright 2016-2023 Fujitsu Limited All rights reserved. Description ----------- Fujitsu Software ServerView Out-of-Band Server Integration Pack for Microsoft System Center Operations Manager (SCOM) permits PRIMERGY Servers to be monitored via SCOM using the server's on-board integrated Remote Management Controller (iRMC). The Product is released for Microsoft Products:SCOM 2022, 2019, 2016, 2012 R2 The Product supports SCOM Management Console for SCOM 2022, 2019, 2016, SCOM 2012 R2 running on MS Windows Server 2022 MS Windows Server 2019 MS Windows Server 2016 MS Windows Server 2012 R2 For detailed list of requirements see the corresponding Microsoft webpages. Supported iRMCs: --------------- - iRMC S4 FW version 8.24F or newer for SystemReport based monitoring - iRMC S4 FW version 9.06F or newer for Redfish based monitoring - iRMC S5 FW version 1.23P or newer for Redfish based monitoring - iRMC S6 FW version 1.19S or newer for Redfish based monitoring Installation ------------ The requirements specified below must be satisfied for integration. - Management station ・supported Microsoft System Center Operations Manager (SCOM) Installation steps: ------------------- ・The default installation path on the management station is: %ProgramFiles%\Fujitsu\ServerView Suite\SCOM Integration ・The installation contains multiple Management Packs as well as documentation. Make sure you have read the Fujitsu Out-Of-Band Management Pack manual for additional installation requirements. ・The discovery for Fujitsu Out-Of-Band Server will run for all Fujitsu iRMC devices as target. Therefore successful discovery of Fujitsu iRMC devices is required. ・Make sure you have username and password from a local iRMC user account. If you use an account with user only privileges some Out-Of-Band server properties will not be populated, such as the installed Operating System, or the Asset Tag. ・Make sure the iRMC of the Fujitsu PRIMERGY server can be accessed over the network from the server where SCOM is installed. ・Check with your local IT and Security department if you have installed all required certificates to access the iRMC over https, or disable Certificate checks in the template. o For troubleshooting and - if needed - how to install a CA certificate into the local machine certificate store see the Out-Of-Band Management Pack manual. ・Create a SCOM Simple 'Run As' Account with the username/password from the local iRMC account. ・Create a new template for 'Fujitsu PRIMERGY iRMC Monitoring' in the Authoring Pane of the SCOM Console. Step by step instructions with screenshots can be found in the manual for the Fujitsu Out-Of-Band Management Pack. o Note: You can group different iRMC by creating multiple 'Fujitsu PRIMERGY iRMC Monitoring' templates if needed. ・After you have successfully discovered any Fujitsu iRMC Devices the Out-Of-Band Server discovery script will run automatically every 4 hours for any Fujitsu iRMC device and will discover the Fujitsu Out-Of-Band Server instances and components. Note: The discovery interval can be changed with an override. o For discovery of Fujitsu iRMC devices the system power state is ignored, since the iRMC itself is always accessible. This is different to the Out-Of-Band Server discovery. o For initial Out-Of-Band server discovery make sure the server is powered on and not in BIOS POST or BIOS Setup. ・Install additional Out-Of-Band Management Packs as needed. Out-Of-band Performance Monitoring Management Pack -------------------------------------------------- ・All performance collection rules are disabled by default. You have to enable the desired performance collection rule(s) with an override. A sample unsealed override Management Pack for the recommended Performance Collection Rules is installed as part of the Integration Pack. You can edit this file according to your monitoring needs before importing the MP to SCOM. Note on 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 contains a newer version of the ServerView Library Management Pack this new Fujitsu ServerView Library MP can usually be imported into SCOM without impacts to any other Fujitsu ServerView Integration Management Packs. In the rare case that a new version of the ServerView Library Management Pack is not compatible with the old version, it is necessary to uninstall all Fujitsu Management Packs including their Override Management Packs and reinstall all Fujitsu Management Packs from the folder 閃anagement Packs・together with the updated ServerView Library Management Pack. Limitations and Caveats ----------------------- ・Only iRMC S5 with firmware 1.10P or newer and iRMC with FW 8.24F or newer will be discovered as Fujitsu iRMC Device. If you have older iRMC in your network an informational alert will be written to your SCOM Server. The alert will be formatted as: Fujitsu Out-Of-Band 192.168.2.1: Unsupported Firmware Version ・System has to be powered on and not in BIOS POST/Setup Phase for detailed Out-Of-Band Server component discovery since a powered down system may not report all components. Note: The Out-Of-Band server discovery actively checks for this condition. ・Restrictions on scalability 1 The product runs its discovery and monitoring PowerShell scripts on SCOM Management Station only. If you monitor many iRMC systems with this product you may face performance issue on that SCOM Management Station. We recommend adding additional SCOM Management Station to the same Resource Pool if the workload on the current SCOM MS is too high. ・Restrictions on scalability 2 The product runs its discovery and monitoring PowerShell scripts on SCOM Management Station only. If you monitor many iRMC systems where some are not reachable at the moment you may face error messages on that SCOM Management Station. You can check in the Operations Manager Event log by searching for the EventID 22411 and 1103. ・Some Celsius Workstation will be discovered and monitored If you configured a Celsius Workstation model that provides an iRMC S4 this Workstation will also appear as PRIMERGY Out-of-Band Server. The Celsius support is not officially released. You can remove this workstation from the iRMC template or you can monitor the system with SCOM without official support from Fujitsu. ・Power Monitoring Component Status may show OK while it is not actively monitored The 撤ower Level・Component Status inside the iRMC will report a Warning or Critical Status only if a Power Limit is configured and ServerView Agents are installed on the server. See the manual chapter 4 for more details. ・Operations Console keeps Management Files open after import When you uninstall the Out-Of-Band Integration Pack from the 撤rograms and Features・ directly after you have installed it and the same Console Session is still open an error messeage will be displayed. Please press Cancel, close the SCOM console within the SCOM Console itself and then try the uninstallation of the Integation Pack again. Do not press OK because this results in a error message about stopped SCOM Console. ・In rare situations it may happen that the systems are discovered but not monitored Rarely there may be a situation where discovery of Out-Of-Band systems starts fine but no monitoring is activated by SCOM. To solve this SCOM issue you can try to set these systems to maintenance mode for a certain period of time. If this does not solve the issue you should delete the Out-Of-Band MP from SCOM, restart the SCOM Console and then reimport the Out-Of-Band MP into SCOM. This solved the issue in all known cases. ・Certificate check is configurable by 'Fujitsu PRIMERGY iRMC Monitoring' template and is propagated to the Out-Of-band scripts were possible. Informational alerts will be generated on CA or CN mismatch by default. ・Certificate check site effect for environment with .NET < v4.5 .NET 4.5 allows certificate checking on a per https connection base, while older versions only support certificate checking on a per process base with a global SSL verification callback .NET object. In an older environment (.NET < 4.5) and if you have a mixed configuration (e.g. some iRMC with bypassing SSL verification and other iRMC verifying the SSL certificate) sporadically SSL handshake errors may be thrown. Also, since ServicePointManager.ServerCertificateValidationCallback is a global setting, changes to the server certificate validation process of every-single TLS stream within a given AppDomain (HttpWebRequest, TlsStream, etc.) may influence the SSL verification of the iRMC communication. Likewise the SSL verification settings for the iRMC may influence the SSL verification of other .NET code. Note: It is highly recommended to update your .NET environment to version 4.5 or later. ・Discovery and Monitoring of Out-Of-Band systems run central on Management Station The Out-of-Band MP design restricts the execution of the discovery and monitoring scripts to the SCOM Management Station system only. If you use multiple SCOM Management stations in the current Resource Pool the scripts will be distributed on these SCOM Management stations. In some configurations it is possible that you see Operations Manager Event log entries ID 29181 about the synchronization between SCOM Management stations. In this cases see the Microsoft documentation or https://blogs.technet.microsoft.com/momteam/2013/01/29/support-tip-config-service-deltasynchronization-process-fails-with-timeout-exception/ ・Password on iRMC account may not contain $-sign as part of password There is a restriction about the possible passwords. The iRMC user account password may not contain any sign with special PowerShell meaning like a $-sign. ・Error and Warning traces are enabled if you enable Logging In the Log control file 鉄VISCOM-OutOfBand.xml you can enable Logging for Server 鉄erverDiscovery・ 鉄mashDiscovery・・HardwareComponentMonitor・ ComponentStatusMonitor・and "PerformanceMonitor". If you enable at least one of them two additional log files beside the specific log file may be generated. One is called 摘rrorTrace・the other 展arningTrace・ These files contain some form of excerpt from the exhaustive log files by noting all happened warning or error entries in these files in a central short trace document.