FUJITSU Software ServerView ESXi Server Integration Pack for Microsoft System Center Operations Manager (SCOM) ========================================================= Version 8.5.2.0 Date 2019-07-02 Status Released Release Notes Copyright 2019 FUJITSU LIMITED All rights reserved. Description ----------- FUJITSU Software ServerView ESXi Server Integration Pack for Microsoft System Center Operations Manager (SCOM) permits PRIMERGY ESXi Servers to be monitored via SCOM. Both hardware and software components are monitored. The product is released for - Microsoft System Center Operations Manager 2012 R2 - Microsoft System Center Operations Manager 2016 - Microsoft System Center Operations Manager 2019 For detailed list of requirements see the corresponding Microsoft webpages. Supported Operating Systems on managed nodes (PRIMERGY Systems) - VMWare ESXi 5.1 - VMWare ESXi 5.5 - VMWare ESXi 6.0 - VMWare ESXi 6.5 - VMWare ESXi 6.7 Product requires SV CIM providers version 7.20 or newer on managed nodes. PRIMERGY Systems running with older CIM providers version will not be discovered for this product in SCOM. RAID Monitoring requires SV CIM Providers version 8.00 or newer on managed nodes. RAID components on PRIMERGY Systems running with older SV CIM Provider versions will be not be discovered for this product in SCOM. The Power Consumption Monitor is only enabled if the managed system meets the requirements: Redundant power supply iRMC Management Controller installed Power Consumption monitoring enabled on iRMC Installation ------------ The requirements specified below must be satisfied for integration. - Management station • Microsoft System Center 2012 Operations Manager or later - Host server for CIM Listener Service • Windows Server 2012 [R2], Windows Server 2016 or Windows Server 2019 • PowerShell >= 3.0 • .NET framework >= 4.0 - Managed PRIMERGY servers • ESXi 5.1 or later • ServerView CIM provider >= V7.20 • Management controller iRMC (integrated Remote Management Controller) (for power consumption) 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 ‘Management Packs’ together with the updated ServerView Library Management Pack. Limitations and Caveats ----------------------- 1. Co-existence of the SVS CIM Provider and the Emulex CIM Provider Problem (KB2114862): When ServerView and Emulex CIM Provider co-exist on the same ESXi host, the Emulex CIM Provider (sfcb-emulex_ucn) might stop responding. As a result, the CIM Provider might fails to monitor the hardware status. Fix in: • ESXi 5.1: Patch Release ESXi510-201510001 (Build 3070626) with Image Profile VMware ESXi 5.1, Patch ESXi-5.1.0-20151004001-standard • ESXi 5.5 U3b • ESXi 6.0 U1a 2. ESXi V6, crash of the CIM Providers Reason of crashes: Reduced memory for sfcb processes (250 MB / 175 MB) in ESXi V6. The sfcb-vmware_raw might fail as the maximum default plugin resource group memory allocated is not enough. Add UserVars CIMOemPluginsRPMemMax for memory limits of sfcbd plugins using the following command and restart the sfcbd for the new plugins value to take effect: Workaround: Command: esxcfg-advcfg -A CIMOemPluginsRPMemMax --add-desc 'Maximum Memory for plugins RP' --add-default XXX --add-type int -- add-min 175 --add-max XXX XXX being the memory limit you want to allocate. This value should be within the minimum (175) and maximum (500) values. It is recommend to use the maximum value (500). Afterwards reboot the ESXi Host. Also described in Release Notes of ESXi 6 U2 http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u2-release-notes.html chapter “Known Issues” > “CIM and API Issues” 3. Management problems with ESXi CIM Providers CIM providers might not response to management software due to resource constraints or other issues. In some cases the provider crashes. VMware together with all CIM Provider vendors is working to solve these issues. Workaround: Restart the sfcbd-watchdog service with “/etc/init.d/sfcbd-watchdog restart” or “services.sh restart”.